210 likes | 712 Views
DoD Authoritative Data Source Activities. Office of the DoD Chief Information Officer (DoD CIO)/ Enterprise Services & Integration (ES&I) Directorate Ms. Oma Cox oma.cox@osd.mil 703-602-1090. Authoritative Data Source (ADS)*.
E N D
DoD Authoritative Data Source Activities Office of the DoD Chief Information Officer (DoD CIO)/ Enterprise Services & Integration (ES&I) Directorate Ms. Oma Cox oma.cox@osd.mil 703-602-1090
Authoritative Data Source (ADS)* DoD CIO volunteered to champion enterprise ADS solutions. Actions fall into two distinct but related areas: Policy Guidance A material solution for an enterprise ADS registry service The DoD CIO extensively leverages the good work of C2ADSWG recommendations to resolve enterprise ADS issues and will continue to dialogue with C/S/As and other domains to ensure the enterprise services meet their needs and respect their equities * Authoritative Data Source (ADS). A recognized or official data production source with a designated mission statement or source/product to publish reliable and accurate data for subsequent use by customers. An authoritative data source may be the functional combination of multiple, separate data sources. 2 2
Authoritative Data Source (ADS)Policy Guidance Policy guidance to resolve ambiguity about: ADS definition - collaborated with AT&L Data Sources registration issues Both Authoritative and other data sources worthy of registration Quality of data metadata IA issues (e.g. ABAC) Governance Respect, leverage and capture Component governance processes Provide for resolution when there is contention Process to include roles, responsibilities and some key terms of reference as recommended by the C2 ADS WG Authoritative Data Producer Authoritative Data Asset Authoritative Data Feed (Expanded from initial briefing) 3 3
Authoritative Data Source (ADS)Material Solution A material solution for an enterprise ADS registry service Registry support tools Capture elements related to implementation of the policy Details about the Material Solution are detailed in following slides 4 4
Why Provide an Enterprise ADS Registry? Promote the CIO’s Vision: • “Provide one stop access to DoD data source directories to improve search, access, consistency, and integration of data services as well as to increase collaboration amongst data producers and consumers” ADS Enterprise Registry will promote this vision by: • Acting as a key enabler to make data “visible, accessible, and understandable” • Providing greater data visibility and accessibility by implementing an Enterprise service • Reducing cost and improving timeliness through the consolidation of ADS; eliminating the need to standup and manage individual registries • Streamlining search and access; providing a set of tools to register and discover data services across the Department 5 5
Material Solution - Enterprise ADS Registry DoD CIO asked DISA to propose and develop a near-term baseline capability that complements the other registry services closely connected to ADS such as: DoD Metadata Registry NCES Service Registry Enterprise Catalog COI Directory DISR, DITPR, E-ISP, Blue Sheets, etc. Adopt C2 CPM ADS Directory as the baseline for the Joint ADS Registry 6 6
Enterprise ADS Registry Goals 7 7 Enable data consumers to discover all relevant information about capabilities which meet their needs Address both authoritative and other data sources worthy of registration Maintain the lowest possible barrier of entry for data providers to register that information • Draw from existing data (e.g. Component ADS Directories, DITPR, Blue Sheets, etc.) • Link to other enterprise capabilities (e.g. COI Directory, Metadata Registry, Service Registry, DISR, E-ISP, etc.)
Benefits of the Selected ApproachEnterprise ADS Registry Reduced cost & shortened implementation schedule by leveraging existing accreditation, hardware, etc. Simplifies integration with existing enterprise registries where related ADS information originates Single Sign-on (e.g. DKO) Integrated with NCES Enterprise Search capability 8 8
Operational View Unanticipated User DITPR DISR Service Registry COI Directory MDR Authoritative Data Source FBCB2 CC/JTF GCCS-M Designates CCIC2S As ADS For Blue Track CC/S/A GCCS-J NCES Enterprise Search Searches Blue Track Data URL for User Access Unit UIC UTC GEOLOC Accesses Operator 9 9 The ADS Registry will enable operators to discover authoritative and other registered sources to meet their data needs
Operational View Developer DITPR Authoritative Data Source Registry Access Mechanism Authoritative Data Source FBCB2 DISR CC/JTF GCCS-M Service Registry Designates CCIC2S As ADS For Blue Track CC/S/A GCCS-J COI Directory Searches MDR Developer Resources • WSDLs • XSDs • Web Service EndPoints • Service Metrics Accesses Developer 10 The ADS Registry will enable developers to fuse data from other registered sources into new applications which are then discovered by the operators
Key Information in the Registry Who declared a source authoritative and for what? Context, Priority Service Metrics Accuracy, Timeliness, Availability, Response Time, Quality Controls Access controls as appropriate Data source and data steward POCs Linkages to other registries Visualization tool identifying relationships Report life-cycle changes such as phasing out a capability, major upgrades, non-availability of data, or change in availability The publishing capability in the registry enforces consistency, quality, and completeness of the entries 11 11
Initial POA&M for the Joint ADS Registry 12 12 Contract award: 9 September 2009 Phase 1, Prototype ADS Registry: DEC 09 • Sufficient to gather feedback from stakeholders • Target easiest ‘relevant information’ • Initial deployment on NIPR MDR Test Suite User Review and Feedback: DEC 09 - FEB 10 Incorporate User Feedback in Initial Release: FEB - APR 10 Phase 2, Migrate prototype to Production: MAY 10 • Deployment on production MDR (NIPR,SIPR) Phase 3, O&M • Tier 2 & 3 support, minor enhancements to production system • Will become integral component of the NCES Metadata Environment
Next Steps for the Joint ADS Registry 13 13 Kickoff Meeting with C2 ADS Working Group and DoD CIO to discuss • Initial Operational and Technical Requirements • Maintenance Concept • Prototype ADS Registry • Schedule, Milestones, etc. Recommend week of 28 SEP • Will coordinate with principals and stakeholders