Process Standards for the Defense Industry
Standards are the foundation for business process interoperability between information systems and platforms. Defense-specific standards define a common business language, which is required to cost-effectively enable business process integration, both inside defense organizations and across the value chain.
Within defense organizations, numerous internal business process standards have been developed over the years by various elements within or across arms of service within a country or alliances members such as the North Atlantic Treaty Organization (NATO) to foster interoperability within the ecosystem. These standards are typically supported by both the defense organization as well as by distinct elements of the defense ecosystem. The following country- or alliance-specific communities produce standards or promote best practices that SAP customers in the defense industry have found to be most useful in enabling business processes between internal systems as well as the systems of their ecosystem.U.S. Financial Systems Integration Office
The U.S. Financial Systems Integration Office (FSIO) (formerly the Joint Financial Management Improvement Program (JFMIP)) is responsible for core financial systems requirements development, testing and product certification, supporting the U.S. Federal financial community on priority projects, and conducting outreach through an annual financial management conference and other related activities. The U.S. Office of Management and Budget (OMB) has set forth general policy guidelines for financial management systems - OMB Circular A-127. This circular requires agencies to establish and maintain a single, integrated financial management system. A-127 further requires agencies replacing financial system software to acquire an off-the-shelf commercial product that has been certified by FSIO. As part of the product certification process, FSIO has certified SAP ERP 2005 as conformant through the full core and P224 testing process.US DoD 5015.2 - STD Design Criteria Standard for Electronic Records Management Software Applications (DOC)
This U.S. Department of Defense (DoD) standard identifies mandatory baseline functional requirements, and identifies non-mandatory features deemed desirable for Records Management Application (RMA) software. The DoD components will use this standard in the implementation of their records management programs. This standard describes the minimum records management requirements that must be met in accordance with 44 U.S.C. 2902 (reference (o)) and guidance and implementing regulations promulgated by the National Archives and Records Administration (NARA). SAP Public Sector Records Management V2.1 is fully certified by the U.S. DoD Joint Interoperability Test Command as conformant to this standard.MIL-STD-2525B Change 1
This U.S. DoD standard describes how military symbols should behave and display on maps and in plotting – both automated and hand drawn. Its purpose is to eliminate conflicts across symbol sets (such as those for the land, sea, and air services) and to define a core set of common warfighting symbology with a methodology for symbol hierarchy and symbol identifiers. The core set enables interoperability across the U.S. DoD Command, Control, Communications, Computer, and Intelligence (C4I) systems development, operations, and training.Multilateral Interoperability Programme (MIP)
The aim of the Multilateral Interoperability Programme (MIP) is to achieve international interoperability of Command and Control Systems (C2IS) at all levels from corps to battalion, or lowest appropriate level, in order to support multinational (including NATO), combined and joint operations and the advancement of digitization in the international arena. The MIP provides a materiel/Combat developer forum, mature process, consensus-based technical specification, a venue for international interoperability testing, system independent capability based on information interoperability, and coordinated synchronization of materiel fielding plans. For communication with C2IS systems, message text formats are enabled by using SAP Defense 2005.2 in accordance with MIP Block 2, C2IEDM 6.1.5f.NATO APP-6A
This NATO standard is based on MIL-STD-2525A, the predecessor to MIL-STD-2525B. Also known as "NATO Standardization Agreement (STANAG) APP-6A", it is used throughout NATO. Concept of NATO Message Text Formatting System (CONFORMETS) - ADatP-3
This is the NATO standard for formatted messages, and can be viewed as the military version of the syntax rules of Electronic Data Interchange (EDI). This standard prescribes the syntax and semantics of structured alphanumerical messages, most of which were originally designed for teletypewriters or TELEX. The standard encodes the agreements on information exchange for everything from logistics to intelligence reports. They are the key to interoperability between national and NATO systems. For communication with Command and Control Information Systems, message text formats are supported by using SAP Defense 2005.2 in accordance with the NATO AdATP-3 Baseline 11 and 12.2.
SAP specially developed interfaces in compliance with ADatP-3, the NATO standard format for data exchange. This high level of integration delivered by SAP technology enables the timely transfer of information, which is critical to “net-centric” warfare – in other words, strategies and tactics used to successfully deploy, operate, and support networked forces. The distribute, but logically integrated, network of systems and applications enables soldiers and commanders to seamlessly carry out their tasks, whether they are working in online mode via secure Internet and satellite connections or temporarily disconnected from the command centers.NATO Codification System
The NATO Codification System is the method used by NATO countries to codify each equipment component and part in the military supply system to ensure uniform name, description, and classification through a NATO Stock Number (NSN). Overseen by The Group of National Directors on Codification Allied Committee (AC/135), the NATO codification system manages the data related to 16 million items of supply and over 32 million part numbers. Its key advantages are a single supply language, accurate information on the identity and characteristics of an item of supply, and avoidance of duplicate codification. Items are codified through assignment of the NSN by the National Codification Bureau (NCB) of the nation that produces the item; regardless of which nation is the end user. The US Defense Logistics Information Service acts as both the US NCB and principal advisor to the other NATO NCBs. For defense organizations, it often does not matter from which supplier an item of supply is supplied if it has the same characteristics (form, fit and function), it will be assigned one NATO Stock Number (NSN). That NSN will then be used by Logisticians of all NATO nations and Armed Forces to manage that item. The governing document in the codification process is the NATO Manual on Codification - ACodP-1. SAP enables tracking of items of supply against the assigned NSNs.