Interoperability in DoD acquisition programs through enterprise "architecting" - Tutorial

Acquisition Review Quarterly,  Summer, 2002  by Mary Linda Polydys

• E-mail
• Print
• Link

Joint Vision (JV) 2020 guides the continuing transformation of America's Armed Forces toward information superiority in the ongoing "information revolution." JV 2020 states that information superiority "is a key enabler to this transformation," and that interoperability facilitates information superiority. This article discusses the role of enterprise architecture in the acquisition of interoperable systems in the Department of Defense.

**********

Joint Vision (JV) 2020 guides the continuing transformation of America's armed forces toward a goal of information superiority. (1) JV 2020 states that "the ongoing 'information revolution' is creating not only a quantitative, but qualitative change in the information environment that by 2020 will result in profound changes in the conduct of military operations" (Chairman Joint Chiefs of Staff [CJCS], 2000, June, p. 8). Because information, information processing, and communications networks are at the core of every military operation. JV 2020 acknowledges the major role of information and information technology in achieving information superiority.

The JV 2020 discussion on information superiority is followed by a discussion on interoperability (2) and its role in achieving information superiority. JV 2020 states that "Interoperability is a mandate for the joint force of 2020 -- especially in terms of communications, common logistics, and information sharing" (CJCS, 2000, p. 15). With respect to interoperability, JV 2020 states that "Information systems and equipment that enable a common relevant operational picture must work from shared networks that can be accessed by any appropriately cleared participant" (CJCS, 2000, P. 15). JV2020 further acknowledges that interoperability goes beyond technical interoperability and includes a focus on procedures or organization. "Although technica1 interoperability is essential, it is not sufficient to ensure effective operations. There must be a suitable focus on procedural and organizational elements, and all decision-makers at all levels must understand each other's capabilities and constraints" (CJCS, 2000, p.1 5).

This article addresses the role of enterprise architecture in documenting interoperability requirements and to some extent, procedural and organizational interoperability requirements in the Department of Defense (DoD) system acquisition. More specifically, this article addresses the use of enterprise architecture products (3) in creating interoperability key performance parameters (4) (KPPs) for Capstone and Operational Requirements Documents (CRDs and ORDs) and documenting interoperability and supportability requirements for the Command, Control, Communication, Computers, and Intelligence (C41) Support Plan. However, before these subjects are covered, it is useful to briefly review the concepts of enterprise architecture as mandated in law and regulation.

"ARCHITECTING" AS A MANDATE

The requirement for enterprise architecture is mandated in the ClingerCohen Act of 1996. This act requires that all Federal Government chief information officers "develop maintain, and facilitate the implementation of a sound and integrated information technology architecture" [40 U.S.C. 1425 [paragraph](b) (2)]. The act further defines information technology architecture (often called enterprise architecture) as "an integrated framework for evolving or maintaining existing information technology and acquiring [emphasis added] new information technology to achieve the agency's strategic goals and information resources management goals" [40 U.S.C. [sections]1425 [paragraph](d)].

The Clinger Cohen Act architecture mandates are implemented in Office of Management and Budget (0MB) Circular A-130 (2000). 0MB Circular A-130 (2000) states that an enterprise architecture must include a description of the business or operational processes, information flows and relationships, data descriptions and relationships, applications, and technology infrastructure. The enterprise architecture must also include a technical reference model and standards profile (including a security standards profile). This circular requires that federal agencies establish an architecture framework that woul provide specific agency direction on developing enterprise architectures.

The DoD developed their architecture framework in 1997, titled Command, Control, Communication, Intelligence, Surveillance, and Reconnaissance (C4ISR) Architecture Framework (future editions to be renamed DoD Architecture Framework; see DoD, 2001b, [paragraph]C6.3.2). This framework organizes DoD's enterprise architecture into three views (e.g., operational architecture view, systems architecture view, and technical architecture view) and provides a set of rules for DoD organizations to follow in creating their architecture descriptions.

The purpose of the operational architecture view is to provide a clear operational picture for decision-making. At the heart of this view are the operational concept, operational processes, and information exchanges. This view contains graphical and textual descriptions (architecture products) defining the tasks/activities/processes, operational nodes (5) or elements, and information exchange requirements (IERs) (6) between nodes. The process and IERs descriptions may be supplemented by business rules, data descriptions, and sequencing and timing descriptions.