Assistant Secretary of Defense for Homeland Defense and Global Security

Technology Solution

Related Documents

The use of existing technology and the ability to leverage existing efforts is important to the efficient implementation of a Defense Critical Infrastructure decision support system.

Currently Defense Critical Infrastructure data is maintained in disparate databases across DoD. DoD must ensure that data collected through the risk assessment process be standardized and accessible through a common visualization capability available across DoD and accessible to decision makers.

Enterprise Architecture

DCIP Integrated Enterprise Architecture

DoD Directive 3020.40, "Defense Critical Infrastructure Program," assigned OASD(HD), along with the CJCS, with developing a DCIP Enterprise Architecture to ensure a net-centric approach to promote DCIP interoperability of information systems and processes, support business needs, and facilitate critical decision making by DoD Components.

The current method of providing situational awareness is through a linear process consisting primarily of data calls. This method frequently produces inconsistent data resulting from differing interpretations of the requirements and is inefficient at best. Implementing DCIP requires the community to become fully integrated concerning process and information sharing.

The DCIP Integrated Enterprise Architecture (IEA) will replace this linear process with an enabling framework for information sharing for risk management of critical assets. It is defined as the explicit description and documentation of the current and desired relationships among business and management processes and information technology (IT). This framework captures the business requirements and information needs necessary to make astute informed decisions about technology, policy, procedures, organization, personnel training, and operations for risk management.

The IEA provides a core set of products and views that define DCIP business needs and point to solutions. These include:

  • Overview and Summary Information (AV-1)
    The AV-1 documents the assumptions, constraints, and limitations that may affect high-level decision processes involving the program's architecture.
  • Integrated Dictionary (AV-2)
    The AV-2 defines the terminology used for the DCIP IEA products.
  • High-Level Operational Concept Description (OV-1)
    The OV-1 graphically describes the mission and highlights main interaction and interesting or unique aspects of operations.
  • Operational Activity to System Function Traceability Matrix (SV-5)
    The SV-5 specifies the relationships between the set of operational activities applicable to an architecture and the set of system functions applicable to that architecture.
  • Technical Standards Profile (TV-1)
    The TV-1 delineates systems, standards, rules, and conventions that apply to architecture implementations.

Common Operating Picture

Unifying the multiple Defense Critical Infrastructure datasets that support DoD missions requires establishing a DCIP common operating picture (COP). Currently, DCI data is maintained in disparate databases across DoD. The DCIP must ensure that data collected through the risk assessment process be standardized, secure, and accessible through a common visualization capability available across DoD and accessible to decision makers in an all-hazards environment. A variety of "best of breed," Web-based geospatial capabilities are available to make this data visible and accessible. These tools may be integrated through the Knowledge Display and Aggregation System (KDAS).

Communities of Interest

As part of creating a DCIP COP, communities of interest (COIs) will be established to share information requirements and essential elements of information, along with protocols and standards for a common operating environment. These COIs serve as a collaborative group of users that must exchange information in pursuit of its shared goals, interests, missions, or business processes, and, therefore, must have shared vocabulary for the information it exchanges. In the geospatial context, this type of COI could be an effective nexus to promote shared geospatial requirements and authoritative data source identification, cost-effective data collection and sharing, development of geospatial best practices, and leveraging of Federal and other resources.

Diagram

A bridging entity, such as the Homeland Infrastructure Foundation Level Database Working Group (HIFLD), could serve as a linking function for COIs between DoD and Federal interagency geospatial leads within each of the Defense Sectors. HIFLD is an OASD(HD)-sponsored coalition of Federal, state, and local government organizations, Federally-funded Research and Development Centers (FFRDC), and supporting private industry partners who are involved with geospatial or "location awareness" issues related to Homeland Security, Homeland Defense, Civil Support, and Emergency Preparedness and Response. The primary goal of HIFLD is the identification of requirements and authoritative geospatial data sources in support of these mission areas.

In addition, the DoD's Chief Information Officer/ASD(Networks and Information Integration (NII) published a Net-Centric Data Strategy in May 2003 that introduced the concept of data management within CoIs rather than standardizing data elements across the Department. to reduce the coordination effort required to manage every data element Department-wide. The OASD(NII) CoI vision foresaw a range of CoIs, including ongoing institutional entities and ad hoc expedient CoIs, addressing functional and cross-functional issues.