1 In Process Review 18 Jan 2006 DoD Net-Centric Data Strategy Community of Interest (COI) Management Defense Logistics Management Standards Office (DLMSO)

1

In Process Review 18 Jan 2006 DoD Net-Centric Data Strategy &

Community of Interest (COI) Management

Defense Logistics Management Standards Office (DLMSO)

2

AGENDA

• Issue / Problem Description• Importance of Issue• Proposed Solution / Course of Action• Progress to Date / Timeline• Recommendations / Innovations

3

Issue Problem DescriptionDoD Net-Centric Data Strategy, DoD NII / CIO, 9 May 2003

“The DoD Net-Centric Data Strategy provides a key enabler of the Department’s Transformation by establishing the foundation for managing the Department’s data in a net-centric environment. … “The strategy introduces management of data within communities of interest (COIs) rather than standardizing data elements across the Department.”

Problem• The DUSD (LM&R) Logistics Data Strategy Working Group (DSWG) initiative to create a Logistics Domain Data Strategy and COI to complement and comply with the DoD Net-Centric Data Strategy failed to produce a coherent data strategy.

• In early 2005, the DoD Business Domain BMMP Transformation initiative was restructured with AT&L assuming leadership and the Logistics DSWG initiative was discontinued.

• The DoD Logistics Community does not yet have a Logistics COI for managing Logistics data assets and resources and there does not seem to be anyone in DoD at any level taking the initiative to create one.

4

DoD Net-Centric Data Strategy

“A Key Enabler of DoD Transformation”• Key Attributes:

Ensuring data are visible, available, and useable when needed and where needed to accelerate decision-making.

“Tagging” of all data (intelligence, non-intelligence, raw, and processed) with metadata to enable discovery of data by users.

Posting of all data to shared spaces to provide access to all users except when limited by security, policy, or regulations.

Advancing the Department from defining interoperability through point-to-point interfaces to enabling the “many-to-many” exchanges typical of a net-centric data environment

-Source: “DoD Net-Centric Data Strategy, DoD NII/CIO, 9 May 2003

5

Net-Centric Enterprise Services

Finance, Accounting Operations

CollaborationServices

Messaging

Application Enterprise Service

Management

Storage Discovery Security

MediationUserAssistant

Collaboration

Acquisition/Procurement

Human Resource

Business Domains Warfighter Domains

COI’s

Force Application

Protection

Focused Logistics

Command & Control

Strategic Planning & Budget

Logistics

Installations&

Environment

Expedient COI’s

Cross Domain COI’s (e.g. Situational Awareness, M&S)

GIG Network

Domain/ Community-of-Interest (COI) capabilities

Levels of services above

core level

Core Enterprise Services (CES)

National Intel DomainBattlespace

Awareness

UsersUsers

DoD Net-Centric GIG Environment

6

Enable Data to beTrusted

Enable DataInteroperability

Make DataAccessible

Enable Data to beUnderstandable

Make Data Visible

Key Goals From theNet-Centric Data Strategy

Metadata is a building block for achieving Net-

Centric Data Strategy goals

Examples:

Discovery search capabilities makes data known and visible through the use of registered

metadata.

Metadata is used by Discovery and mediation tools to help

control access to data.

Metadata used by the Discovery enterprise capability tells what

the data is about enabling Mediation to put data in terms understood by different users.

Net Centric Data Management Fundamentals

Communities of Interest are the entities that will manage DoDData resources and assets to achieve the Net-Centric key goals.

7

Summary of Guiding Principles

1. Producers must post data such that it is accessible on the network by moving data from internal organizational private space to shared spaces.

2. Producers are the responsible source for defining their data content and providing the metadata.

3. Users determine when data is pulled, what data is needed, and the value of that data for their application.

4. Data Management must be flexible enough to support a wide variety of missions, a changing organizational structure and the diverse needs of the Department’s users.

5. Measures must be used to evaluate the success of achieving the DM component of net-centricity, as reflected in these guiding principles.

Source: Dr Margaret Meyers, DoD NII/ Deputy CIO, Sep 2002

8

Community of Interest (COI)

Definitional Concepts• “A collaborating group of users who must exchange information in pursuit of their shared goals, interests, mission, or business processes and who therefore must have shared vocabulary for the information they exchange.”• COI focus is to gain semantic and structural agreement on shared information in order to achieve the capability for interoperable data and information sharing among sending and receiving automated information systems.• The scope of the set of COI agreements for creating an interoperable data and information sharing environment among COI members should be as narrow as reasonable, but as brad as necessary to meet COI data sharing requirements.• COIs are most likely to be representative of functional domains or joint activities that cross traditional organizational boundaries.• COI members will include both producers and consumers of data as well as developers of systems and applications.

-Source: “DoD Net-Centric Data Strategy, DoD NII/CIO, 9 May 2003 DoD 8320.2-G, “Guidance for Implementing Net-Centric Data Sharing”, November 2005

9

Types of COIs

• Organizational

• Functional

• Mission

• Task

Institutional - standing, long-lived, semi-permanent

Expedient - dynamic, specific task, short-lived, temporary

-Source: “DoD Net-Centric Data Strategy, DoD NII/CIO, 9 May 2003

10

Key COI Attributes

• Formed to meet a specific data sharing mission or fulfill a task.

• Composed of stakeholders cooperating on behalf of various organizations, with emphasis on cross-Component activities.

• Members are committed to actively sharing information in relation to their mission and/or task objectives.

• Recognizes the potential for authorized, but unanticipated users and therefore, strive to make their data visible, accessible, and understandable to those inside and outside their community.

-Source: DoD 8320.2-G, “Guidance for Implementing Net-Centric Data Sharing”, November 2005

11

COI Primary Responsibilities

• Identify data assets and capabilities that must conform to DoD Net-centric data strategy goals. (operational & developmental)• Identify approaches to enable those assets and capabilities.

• Develop and maintain required semantic and structural agreements to ensure data assets can be understood.• Register appropriate metadata for use by COI members and other users.

• Extend the DoD Discovery Metadata Specification (DDMS) to ensure COI-specific metadata is available and understandable.• Partner with the appropriate governing authority (e.g., Component or portfolio manager) to ensure that COI recommendations are adopted and implemented through programs, processes, systems, and organizations.


12

Key COI Management Roles

• COI Lead: May be known as the COI Data Manager, or Data Steward, or Data Administrator, etc. Should be filled by a functional expert rather than an IT specialist.

• COI Governing Authority: Typically filled by a Component, Agency, or COCOM activity or IT portfolio manager. Charters and provides oversight and resource support for the COI as well as guidance and direction.

• COI Stakeholders: People, organizations, entities that have an interest in the outcome of the COI effort; those who stand to benefit, and those whose processes and/or systems may be affected by COI activities.

• COI Capability Developers: Personnel/organizations for developing technical approaches that turn COI agreements and objectives into live capabilities.


13

Operationalizing a COI• Identify COI mission, members, and desired information sharing capabilities.

• Identify related COIs that may exist.

• Prioritize information sharing requirements and capabilities.

• Advertise the COI.

• Identify measures of success.

• Identify governing/chartering authority and select a COI Lead.

• Establish a governance process

• Assess reusability of existing IT and logistics data resources.

• Identify the approach for delivering technical capabilities.

• Create a COI management and technical capability plan.


14

Implementing COI Capabilities• Identify, define and register COI extensions to DDMS discovery metadata.

• Gather existing semantic artifacts and structural schemas.

• Develop agreement on a shared vocabulary, conceptual schema, and a COI taxonomy for data assets and resources.

• Maintain and manage data asset discovery metadata.

• Define and develop data asset access mechanisms.

• Define data asset mediation requirements and capabilities.

• Define data asset trust elements of pedigree (source and lineage), security labels to ensure protection, and rights protection metadata.


15

Net-Centric Data Management Imperatives

• Data assets/resources will be managed by COIs. Managing data for interoperable sharing is accomplished by managing the metadata that identifies and describes the data content. • Creators/producers of data assets must tag their assets with metadata in compliance with the Net-Centric DoD Discovery Metadata Specification (DDMS) with COI extensions as needed.

• All data assets must be made available and accessible on the DoD GIG (consistent with security classification and access authority) by publishing their discovery metadata in a data asset catalog connected to the GIG registered with the DoD Discovery service.

16

DoD Logistics COI Responsibilities

• Programmatic Planning, programming and budgeting Resourcing and management infrastructure development Governance and assessment

• Technical Data asset metadata configuration management (Metadata Repository) Data asset registration for search and discovery (Data Asset Catalog) Logistics COI web portal development and management

• Operational (“Customer” Support) Serve as Logistics Domain Data Management center of Excellence Provide Data Management training Perform data management quality audits Assist customers in conduct data analysis tasks

17

DoD Logistics Domain“Data Champion”

Materiel ManagementCommunity of Interest

“Data Champion”

MovementCommunity of Interest

“Data Champion”

MaintenanceCommunity of Interest

“Data Champion”

Service & SupportCommunity of Interest

“Data Champion”

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOISubordinate

COI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

Notional COI Decomposition

Level 0

Level 1

Level 2

Level 3& Below(Dynamic)

DLMSO USTC TBDMilitaryComponents

A Notional Logistics COI Infrastructure

18

DoD Logistics Domain“COI Data Manager”

DoD Financial Domain“COI Data Manager”

DoD Personnel Domain“COI Data Manager”

DoD “Medical” Domain“COI Data Manager”

LOGISTICS FINANCIAL PERSONNEL HEALTH AFFAIRS

DoD EnterpriseData Management

Strategy

DoD Chief Information OfficerDoD

Data Asset/ElementMetadataRegistry

DoDData AssetCatalog Registry

DoD “Business” Domains

DomainMetadataRegistry




DomainData Asset

Catalog

Institutional COIs

Dynamic COIs

Institutional COIs

Dynamic COIs

Institutional COIs

Dynamic COIs

Institutional COIs

Dynamic COIs

COIMetadataRegistry

COIData

Catalog

COIData

Catalog

COIMetadataRegistry

???? COI

MetadataRegistry

COIData

Catalog

???? ???? ???? COI

MetadataRegistry

COIData

Catalog

DomainData Asset

Catalog

DomainData Asset

Catalog

DomainData Asset

Catalog

DoD GIG IT Components

COI IT Components

Notional COI Technical Infrastructure

19

Director “COI Data Manager”

(1 PE)

Budget, Policiesand Procedures

PROGRAMMATIC(1 PE)

TECHNICAL(3 PEs)

Metadata ManagerXML ManagerCOI Webmaster

OPERATIONAL(2 PEs)

Audit AnalystTraining Coordinator

Office of the COI Data Lead Manager

Total Staffing- 7 PEs

Notional “Large” COI

Director“COI Data Manager”

(1 PE)

Budget, Policiesand Procedures

PROGRAMMATIC(1 PE)

TECHNICAL(1 PE)


OPERATIONAL(1 PE)




Notional “Medium” COI

COI Lead Data CoordinatorTECHNICAL

“COI Lead Data Coordinator”(1 PE)


Notional “Small” (Dynamic) COI

Total Staffing- 1 PE

Director“COI Data Lead Manager”

(1 PE) PROGRAMMATIC

Budget, Policies, Procedures

TECHNICAL(1 PE)


OPERATIONAL(1 PE)




Another Notional “Medium” COI

Example COI Management Structures

20

Description and Objective: This initiative uses only one level of the functional capability of the Metabase Repository System to solve a particular problem that is pervasive throughout Logistics and DoD- the failure of systems to be able to communicate interoperably because of differences in standard transaction formats and in the data elements that compose those transactions. This initiative will focus on defining transaction based enterprise level data elements and their many disparate representations in systems to create the automated transaction transformations that will allow seamless and transparent interoperable communication.

Approach:• Identify all Defense Logistics Management System (DLMS)

standard transactions and create metadata that defines their structure and their enterprise data element content.

• Populate the Metabase Repository System with transaction and data element metadata and define metadata describing alternative structural formats for standard transactions.

• Create the transformation maps for each DLMS standard transaction that relates alternative structural formats to their respective common DLMS standard transaction format.

• Develop the web interface and automated processes for real-time resolution of disparate transaction formats between sending and receiving information systems.

Deployment Phases:• Phase I: Install Metabase Repository System; Populate with

metadata for Standard Logistics Transactions and Data Elements; Develop web interface and query and reporting system; Demonstrate Phase I functionality. (28-32 weeks; $516K)

• Phase II: Develop metadata models of information systems X12 and XML transaction formats; Engineer transaction transformation engine design; Develop transformation algorithms; Demo Phase II functionality. ( 26-36 wks; $600K)

• Phase III: Test, tune, validate and demo automated data element semantic reconciliation function and the standard transaction transformation function; Begin population of additional Metabase modules such as Mission, Organization, Business Function, Business Event, and Information System. (32-36 wks; $600K)

Benefits:• Creates a single authoritative source for standard Logistics transactions and

standard enterprise data elements.• Will reduce dramatically the need for custom engineered point-to-point

interface systems and also permit business areas to employ preferred terms for their application data elements.

• Will lower cost of IT operations; greatly reduce transaction rejects; improve timeliness and accuracy of asset visibility; reduce instances of lost or misdirected cargo.

• Warfighter benefits from reduced wait time for materiel support, more timely, accurate and trusted logistics information for decision making- all translating to higher operational readiness.

Impacted Core Logistics Capabilities:

Directly Impacted by Initiative Indirectly Impacted by Initiative

Ent

erpr

ise

LOG

Cor

e B

usin

ess

Cap

abili

ties

Materiel Transaction Visibility

E

nter

pris

e LO

G P

riorit

y

Forecast and Plan for Materiel Resources

Manage MaterielSupply Sources

Procure MaterielResources

Prioritize andAllocate Materiel

Resources

Distribute andDeliver Materiel

Resources

Analyze Report on & Resolve Logistics

Operations

Common Supplier Engagement

Initiative #34: DoD Logistics Metabase Repository System

[Formerly – DoD Logistics Metadata Repository System for Shared Enterprise Level Data Elements (ELDE)]

21

Data Elements

Transactions

Processes

BusinessFunctions

Compose

Execute

Accomplish

Achieve

Enterprise Mission

TransTrans

Trans

Trans

Trans

TransTrans Trans

Trans

LogisticsProcesses

AcquisitionProcesses

FinancialProcesses

DoDMission

AcquisitionFunctional Area

LogisticsFunctional Area

ComptrollerFunctional Area

Accomplished Thru

Activate

Trigger

Employ EnterpriseData Element

EnterpriseData Element



This chart illustrates the relationships/interdependencies that exist between and among the business and technology artifacts that make possible automatedbusiness operations in support of DoD Enterprise Mission, Goals and Objectives.

DLMSO AT&L Initiative #34Logistics Metadata Repository

22

Data Element Metadata Relationshipsto Multiple Categories of Metadata

DoD LogisticsEnterprise

InteroperabilityMetadata Repository

Core DoD Logistics Enterprise

Data ElementMetadata

Repository

The PayoffSeamless & Transparent

Information Interoperability

DoD Logistics Metadata Repository

23

DoD CORE DATA ELEMENT METADATA

REPOSITORY

Implemented Model Layer

Operational DBMS Layer

Application View Layer

Specified Model Layer

ISO 11179 Model Layer

DoDEnterprise

InteroperabilityMetadata Repository

Core DoD Enterprise

Data ElementMetadata

Repository

Proposed DoD Logistics Metadata Repository Complete Representationsof Data Element Metadata

Data Element Metadata Relationshipsto Multiple Categories of Metadata

Today

The Future

The PayoffSeamless & Transparent

Information Interoperability

24

Whitemarsh Knowledge Worker Framework

25

CONCEPT CONCEPT STRUCTURE

CONCEPT STRUCTURE TYPE

VALUEDOMAIN

VALUE DOMAINSTRUCTURE

VALUE DOMAINSTRUCTURE TYPE

DATA ELEMENT CONCEPT STRUCTURE TYPE

DATA ELEMENT CONCEPT STRUCTURE

DATA ELEMENT CONCEPT

DATAELEMENT

VIEW

ATTRIBUTE

COLUMN

DBMS COLUMN

VIEW COLUMN

ENTITYSUBJECT

TABLESCHEMA

DBMS TABLE DBMS SCHEMA

ISO 11179BUSINESS CONTEXT INDEPENDENTDATA ELEMENT REPRESENTATION

FUNCTIONALLY DEPENDENT & TECHNOLOGYINDEPENDENT DATA MODEL TEMPLATESATTRIBUTE INHERITS DATA ELEMENT

“SPECIFIED” DATA MODEL (DoD FDAd Domain)

TECHNOLGY DEPENDENT &DBMS INDEPENDENT MODEL / SCHEMA

COLUMN INHERITS ATTRIBUTE“IMPLEMENTED” DATA MODEL)

(Data Architects / Modelers Domain)

DBMS DEPENDENT &APPLICATION VIEW INDEPENDENT

DBMS COLUMN (Oracle, DB2, etc) INHERITS COLUMN“OPERATIONAL” DATA MODEL

(Domain of Database Administrators (DBAs))

BUSINESS INFORMATION APPLICATION

SYSTEM

VIEWCOLUMN

STRUCTURE

VIEW COLUMNSTRUCTURE

PROCESS

VIEWCOLUMN

STRUCTURETYPE

APPLICATION VIEWS OF DBMS TABLES & COLUMNS

(Domain of Application System Managers (SMs and/or PMs)

Functionally Independent Business Fact Semantic Templates (Globally Shared Data Elements)

(Domain of DoD Data Administration)

META MODEL ARCHITECTURE SUPPORTING ENTERPRISE WIDE SHARED DATA

Data interoperability occurs at the “operational and application” view layers. Made possible throughthe relationships between all layers represented by metadata in a repository that enables relating syntax and semantics from any layer to a common ISO 11179 standard representation.

METADATAREPOSITORY

Implemented Model Operational DBMS

Application View

Specified Model ISO 11179

CONCEPTUAL VALUE DOMAIN

CONCEPTUAL VALUE DOMAIN STRUCTURE

CONCEPTUAL VALUE DOMAIN STRUCTURE TYPE

26

All of these various representations of an ISO 11179 Data Element may have different names, but they all inherit the semantics of the Data Element and are thus semantically equivalent.

Materiel Resources Quantity

Resources

Materiel Resource Quantity

ISO 11179 Fundamental Data Element Metamodel

Materiel Inventory Quantity(for a logical data model

Entity attribute)

Mat -Inv-Qty(for a DDL database schema

Column)

Mat-Itm-Inv-Qty(actual internal physical name

of a database column)

Stocked Item Quantity(for a data system output

Report or screen field name)

Materiel Item Quantity(XML tag name represented in

XML schemas, style sheets, etc)

Supply Item Quantity(View column of an application

system )

All of these various representations of an ISO 11179 Data Element may have different names, but they all inherit the semantics of the Data Element and are thus semantically equivalent.

Data Element Concept Value Domain

Conceptual Domain

Data Element (Name)


Attribute Name(of a logical data model

Entity)

Schema Column Name(of a DDL database schema

Column)

Database Column Name(actual internal physical name


Report Field Name(of a data system output report)

XML Element Tag Name(of Data Elements represented inXML schemas, style sheets, etc)

View Column Name(of an application system )

EXAMPLE

27

Data Element Concept Value Domain

Conceptual Domain

Data Element (Name)


Attribute Name(of a logical data model

Entity)

Schema Column Name(of a DDL database schema

Column)

Database Column Name(actual internal physical name


Report Field Name(of a data system output report)

XML Element Tag Name(of Data Elements represented inXML schemas, style sheets, etc)

All of these various representations of an ISO 11179 Data Element may have different names, but they all inherit the semantics of the Data Element and are thus semantically equivalent. Therefore, all of the possible paths depicted above are “legal” relationships for depicting the migration of semantically equivalent representations of an ISO 11179 Data Element template.

View Column Name(of an application system )

Data Element Representations

28

Mat_Itm_Inv_Qt

MaterielInventoryQuantity

Materiel ItemInventoryQuantity

Mat_Inv_Qty

Materiel UnitInventoryQuantity

Supply UnitQuantity

Stocked MaterielQuantity Ships Stores

Quantity

Functional/OrganizationalContext Dependent

“Specified” Data Model

Army LogisticsManagement

Navy LogisticsManagement

Technology Dependent“Implemented” Data Model

ANSI SQL

ANSI SQL

Vendor DependentSQL DBMS

“Operational” Data Model

“Oracle” DBMS

“Sybase” DBMS

Business ApplicationInformation System (AIS)

“View” Data Model

Navy UADPS (AIS)

Army SAMS (AIS)

Concepts

Data Element Concept

ValueDomain

Data Element

CORE METADATAREPOSITORY

Implemented Model

Operational DBMSApplication View

Specified Model

ISO 11179 Model

View ColumnNames

DBMS ColumnNames

SQL ColumnNames

AttributeNames

Business Fact SemanticTemplate Name

Metadata Repository Architecture of RelatedRepresentations of DoD Enterprise Shared Data Elements

in Support of Data and Information Sharing

The quantity of each type ofFederal Supply System materielitem contained in an identifiableinventory of materiel objects.

Data Element Definition:

Additional Data Element Structural Metadata:

Supply ItemResourceQuantity

MaterielResource

Physical ItemBalance

Quantity

PhysicalMeasure

ConceptualValue Domain

Data type characteristics,local definition, enumerated values ( if specific ), etc.

ISO 11179 Context Inde pendent Data Element Representation Meta Model

Metadata Repository Example

29

1

METABASEREPOSITORY SYSTEM

30

Critical Data Associated with the cells of this KW Framework is contained in the Metabasesystem which is designed and engineered to capture and maintain the data relationships inherent among the cells of the Framework.

2

31

3

32

33

6

34

DATA ELEMENT CONCEPT STRUCTURE TYPE

DATA ELEMENT CONCEPT STRUCTURE

DATA ELEMENT CONCEPT

DATAELEMENT

CONCEPT CONCEPT STRUCTURE

CONCEPT STRUCTURE TYPE

CONCEPTUAL VALUE DOMAIN

CONCEPTUAL VALUE DOMAIN STRUCTURE

CONCEPTUAL VALUE DOMAIN STRUCTURE TYPE

VALUEDOMAIN

VALUE DOMAINSTRUCTURE

VALUE DOMAINSTRUCTURE TYPE

ISO 11179BUSINESS CONTEXT INDEPENDENTDATA ELEMENT REPRESENTATION

Functionally Independent Business Fact Semantic Templates (Globally Shared Data Elements)

(Domain of DoD Data Administration)

8

35

9

36

10

37

• Create a single Authoritative Source for Shared Logistics Enterprise Level Data Element Metadata.• Create capability for Domain and Local (COI) Data Asset Managers to manage and maintain configuration control over their respective Enterprise

and Application Level Data Element Metadata. • Reduce instances of misinterpreted or rejected transactions due to data element

semantic impedance by registering the equivalencies between Application Level and Enterprise Level Data Elements.

• Improve accuracy, reliability, and trustworthiness of Logistics data and information provided to operational users and decision makers. • Greatly improve timeliness and quality of logistics support to Warfighters and

Operational customers by improving quality of Logistics Operations.• Reduce the cost of Logistics Information Technology requirements by reducing

need for complex point-to-point system interfaces.

Why Is This ImportantKey Benefits:

38

Progress to Date

• Co-chair of DUSD(L&MR) DSWG for 2003 and 2004

Produced a Logistics Data Management Strategy CONOPSo Completed one round of coordination when AT&L abandoned the initiative.o Produced a draft set of DLMSO Logistics COI policies and procedures that are still current and ready for use.o At request of DLMSO Director produced a draft DoD Directive designating DLMSO as the Executive Agent for DoD Logistics Data Management. It never got out of DLA.

Responded to March 2005 AT&L call for “quick hitter” IT project initiatives with a proposal for a Logistics Enterprise Level Metadata Repository. Did not make first cut for funding and are still waiting. Succeeded in establishing an Action Item for the JSJ4 hosted data Quality Summit to develop justification for a DoD Data Management Program Office. Action still pending.

39

Proposed Solution / Recommendations

• Work to have DLMSO declared/designated as the DoD Executive Agent for DoD Enterprise level Logistics Data Management and Lead Activity for a DoD Logistics COI.

• Support funding request for DLMSO AT&L Initiative #34 to develop and deploy a DoD Logistics Metadata Repository.

• Support creation of a DoD Directive describing roles, duties, and responsibilities for a DoD Logistics COI.

40

Backups

DoD Net-Centric Data Strategy &Community of Interest (COI) Management

41

IDE

IDE

IDE

IDE

IDE

MATERIEL MANAGEMENT

DISTRIBUTION

MAINTENANCE

TRANSPORTATION

ENGINEERING

1

2

Data InterfaceTranslator=

3

4

5

Interoperability via IDE Interfaces

42

Schema D

System N

Schema N

System M

Schema M

System L

Schema L

System A

Schema ASystem P

Schema PSystem O

Schema O

System D

Schema D

System C

Schema C

System B

Schema B

System H

Schema H

System G

Schema G

System F

Schema F

System E

Schema E

System K

Schema K

System J

Schema JSystem I

Schema I

ENTERPRISE IDESchema C

Schema BSchema A

Schema ISchema H

Schema G

Schema F

Schema ESchema M

Schema L

Schema KSchema J

Schema P

Schema O

Schema N

IDE – SDESCHEMA

Enterprise Interoperability

43

AcquireMateriel

ManageMateriel

DistributeMateriel

MaintainMateriel

RetireMateriel

Materiel Requirements Determination

Materiel Sourcing

Materiel Specifications

Materiel Procurement

CatalogMateriel

Receive & Store Materiel

Fill Materiel Requisitions

Replenish Materiel Inventory

Materiel Release Order

Pick & Pack Materiel

Move Materiel

Track Materiel Movement

Schedule MaterielMovement

Determine Materiel Condition

MaterielLogistics

Determine Maintenance

Action

Perform Maintenance

Action

Evaluate Materiel

Condition

Make MaterielDisposition

ReceiveMateriel

DetermineMateriel

Condition

Make DispositionDecision

Dispose Materiel

Notional Log Functions

44

COISystem B

COIData Asset/

ElementMetadataRegistry

COISystem A

XML Transaction

COI/DoD?XML

Registry

EDI/X12 Transaction

Return XMLComponent(Schema, DTD, etc)

Data ElementName (Tag Name),Definition, Value domain,Etc, etc

Query/selectXML Component(Schema, DTD, etc)

MetadataDatabaseA

DatabaseB

Metadata

Web Portal

Web PortalWeb Portal

Web Portal

Web Portal

Web Portal[COI Data Asset / Element

Metadata Manager]

[COI Web Master] [COI XML Namespace Manager]

Notional Registries/Transaction Graphic

SendingSystem

ReceivingSystem

45

DoD Logistics DomainCommunity of Interest“Lead Data Manager”

Materiel ManagementCommunity of Interest“Lead Data Manager”

MovementCommunity of Interest“Lead Data Manager”

MaintenanceCommunity of Interest“Lead Data Manager”

In Service & SupportCommunity of Interest“Lead Data Manager”

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOISubordinate

COI

SubordinateCOI

SubordinateCOI

SubordinateCOI Subordinate

COI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

SubordinateCOI

A Notional DoD Logistics “Community of Interest” Management Infrastructure

Notional COI Decomposition

QUESTIONS: Who can authorize creation of a Subordinate COI? Should every Subordinate COI have a “Lead Data Manager”? If not, then where is the cutoff and who decides? What about COIs that are intersections of other COIs?

Supply Chain COI ?

DLMSO ??

??

TRANSCOM TBDMilitaryServices ??

46

DatabaseLayer

AIS Layer

Application Layer Data Elements

Enterprise Level Data Element Template (Standard)

Domain Layer

Subject Area (Process) Layer

47

48

49

Documents

1 In Process Review 18 Jan 2006 DoD Net-Centric Data Strategy Community of Interest (COI) Management Defense Logistics Management Standards Office (DLMSO)