Downloaded from https://www.everyspec.com MIL-HDBK-502: A MIL-HDBK-502: A CQUISITION CQUISITION L OGISTICS OGISTICS investigation results. The strategy is developed in line with the acquisition decision and the associated systems engineering and other program activity requirements associated with the type of acquisition decision. These requirements are further tailored based upon specific program needs and constraints. Traditional DoD acquisition environments, based primarily upon proprietary products and isolated data processing systems have resulted in a costly, poorly integrated, and closed (rather than open ) infrastructure in most organizations.
The open systems approach mandated by current DoD policy (reference DoD 5000.2-R, paragraph 4.3.4) encompasses the selection of specifications and standards adopted by industry standards bodies or de facto standards for selected system interfaces, products, practices, and tools. Open systems standards define interfaces which support portability, interoperability, and scaleability (i.e., expansion); and are available to the public. Potential benefits realized from the use of open systems standards include reduced costs, increased competition, and increased interoperability.
Note, however, that an open system standard IS NOT SYNONYMOUS with the use of commercial and non-developmental items (C/NDI) . An open systems standard is primarily concerned with interface compatibility to promote interoperability between multiple suppliers’ equipment Ideally, open systems represent a transparent environment in which users can intermix hardware, software, and networks of different vintages from different sources to meet differing needs. In reality, systems are not purely open or closed.
Because industry standards do not generally meet all military needs, trade-offs must be made between performance, cost, supportability, availability of standards- based products, and the ability to upgrade. The result is that for any given system, the degree of openness may have many interpretations. As with any integrated effort, supportability analysis activities must be aligned with the related systems engineering disciplines whose activities provide essential support planning information relative to the hardware and software designs.
4.2.3 Design Flexibility The degree of flexibility in the total system hardware, software, and support system designs is a basic consideration in deciding what supportability analyses can and should be performed. The objective of most support system design activities is to identify support considerations (e.g., constraints) which may influence selection of system hardware and software design and support alternatives to improve 4-7