FIGURE 1


POLICY & MANDATES


AFFORDABILITY


Adhere to Better Buying Power


• Lowers life cycle costs. • Increases competition and recompetes. • Reduces vendor lock. • Can be fielded faster. • Enables cross-


platform alignment. Get to the Warfighter Faster More Affordable


• Lowers life cycle cost. • Minimizes


obsolescence/diminish- ing manufacturing sources.


• Reduces duplicative development.


KEY BUSINESS DRIVERS


The FACE Consortium approach uses business processes, technical practices and a software standard that enable modularity, portability and interoperability. Reusing software across multiple platforms reduces development costs, integration costs and fielding time. (Source: The Open Group)


• Reduces development and integration timelines, primarily through software reuse. • Facilitates quick and efficient mission payload changes.


TIME TO FIELD


CAPABILITY Capability Reuse


• Expands common capability reuse across services and coalition partners.


Capabilities-Based Improvements


• Maintains technology superiority.


• Spurs innovation.


• Enhances interoperability of software components within a computing environment.


REUSE


in closed, proprietary systems, typically it’s only the vendor who has access. Open systems promote competition precisely because they are open and therefore can lead to better access to cutting-edge technology. Figure 1 provides an overview of the multiple benefits of open systems.


Te Open Group Future Airborne Capability Environment (FACE) Consortium, a partnership of more than 90 govern- ment, academic and defense industry organizations, has defined an open-system avionics architecture for all military airborne platform types. (See related article, “About ‘FACE’,” Army AL&T magazine, April – June 2015.)


With more than 1,300 members, the FACE Consortium is a consensus-based organization—that is, all documents and pub- lications are developed through committees, subcommittees, standing committees and working groups, then reviewed by the membership and approved by a steering committee. Tis ensures that the architectures, technical standards and other documents are developed and agreed to by all of the major stakeholders


in airborne systems. Because the development is a bottom-up approach by subject matter experts from both industry and DOD, the documents include well-understood and acceptable tools and procedures.


Te FACE Consortium’s approach is designed to advance modularity, portability and interoperability through consistent business processes, technical practices and a software standard. Te reuse of software across multiple platforms reduces develop- ment costs, integration costs and time to field.


Software suppliers develop capabilities that meet the require- ments of the FACE technical standard and allow the exchange of data between FACE components. Te FACE technical stan- dard contains requirements for architectural segments and their software components; it defines key interfaces that link the segments together. Te FACE conformance program then certi- fies that the requirements of the FACE technical standard have been met and allows the software vendor to legitimately claim the product to be FACE-conformant. Tis provides prospective


ASC.ARMY.MIL 33


ACQUISITION


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156