![]() |
| Home | Statistics | Documents | Catalog | StratEdit | XSLTForms | DNAOS | About | Portal | Glossary | Contact [!?] |
| Documents/DoDNCSS/3: Govern the Infrastructure and Services |
3: Govern the Infrastructure and Services Establish the policies and processes for a single set of common standards, rules, and shared secure infrastructure and services throughout the DoD Enterprise to ensure interoperability. Other Information: Governance means establishing and enforcing how DoD Components and mission partners, on behalf of the Mission Areas, agree to provide, secure, use, and operate services. There are three elements to governance: 1. Identifying the attributes for providing, securing, using, and operating services that have to be governed and what level of governance is required 2. Establishing lines of responsibility, authority, and communication for making decisions about services across the lifecycle of services 3. Establishing the measurement, policy, and incentive/control mechanisms to ensure that individuals and organizations carry out their responsibilities. Governance of a single set of common standards, rules, shared secure infrastructure, and services throughout the DoD Enterprise requires governance at various levels in the DoD. This layered approach is analogous to the approach used to govern sports leagues. In a sporting league, each team maintains its own governance (e.g., training regime, coaching, concessions, and some elements of the venue); however, when teams compete, there is a set of rules and responsibilities that all teams agree to follow (i.e., specifics of the field of play and permissible equipment to ensure a fair competition). Similarly, under the net-centric services vision, each DoD Component or program will maintain its own governance for things such as commercial middleware choices or contract management; however, when services are shared, the provisioning, securing, use, and operation will be governed in accordance with an additional set of attributes. It is the intent of the DoD CIO to develop an enterprise governance process and to limit enterprise governance to those attributes critical to the realization of interoperable, shared services throughout the DoD and mission partners. There will be specific capabilities that require additional governance. One specific example is an enterprise capability delivered through a federation of services; in other words, a federated capability. In this strategy, a federated capability is defined as one that has the following characteristics: It is implemented using information sources or capabilities from a variety of service providers who are distributed across the enterprise and All service providers contributing to the federated capability agree to the definition of the service (i.e., the functionality being provided), the service interfaces, the service security properties, the semantics and structure of its payload, and the operational performance characteristics. The additional governance required by the federation of services is defined by, agreed to, and mutually enforced by the distributed set of providers across the enterprise. The Enterprise White Pages is a specific example of a federated capability. Each of the DoD Components and mission partners maintains an authoritative directory of users who will become part of the federation. Each member of the federation participates in defining the service interfaces, data items, and data quality for the directory, and enforces those definitions locally. As a result of this federation, users on the GIG will be able to search for locator information on any individual in the GIG. The DoD CIO will govern the use of federation in the DoD Enterprise services environment to ensure that the various federation management models are consistently applied and understood. Key Action: Update appropriate policies and provide implementation guidance to codify use of services and SOA. Outcome: Establish DoD services and SOA governance through policy and guidance (e.g., DoDD 8100.1 and DoDD 8115.1; GIG Architecture Framework; Net-Centric Implementation Documents) Objective(s):
|
| sitemap | Copyright 1971-2012 01 COMMUNICATIONS INC. ALL RIGHTS RESERVED. - Powered by DNAOS | contact |