1 / 14

Enterprise Authoritative Data Source Registry Interim Progress Review

Enterprise Authoritative Data Source Registry Interim Progress Review. Ken Fagan Chief, Data Services Office DISA PEO-GES 17 NOV 2009. Agenda. Operational Concept Base Requirements Deployment Model Interfaces Initial Prototype (Screenshots) Deployment Schedule. Operational Concept.

silver
Download Presentation

Enterprise Authoritative Data Source Registry Interim Progress Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Authoritative Data Source RegistryInterim Progress Review Ken Fagan Chief, Data Services Office DISA PEO-GES 17 NOV 2009

  2. Agenda Operational Concept Base Requirements Deployment Model Interfaces Initial Prototype (Screenshots) Deployment Schedule

  3. Operational Concept Basic Operational Concept is based on the following resources: C2 Data Needs Matrix and associated coordination activities Analysis of database schemas and data provided by the C2 ADS WG Information gathered from the C2 ADS Registry Wiki Initial Operational and Technical Requirements for Joint Authoritative Data Sources (ADS), USJFCOM, 18 SEP 2009 C2 CPM Joint Authoritative Data Source (ADS) Directory Maintenance Concept, USJFCOM, 18 SEP 2009 Initial Prototype will be populated with a subset of data from the C2 Data Needs Matrix, co-developed by DISA JPMO and J87. Primary objectives are to: Provide visibility of Enterprise Authoritative Data Sources Implement a governance construct for the establishment of ADSs Provide insight into the progress Data Owners are making in providing data services through NCES SOAF capabilities and standards

  4. Operational Concept 2) Candidate Authoritative Data Source Identification Process 1) Data Needs Identification Process works with works with Authoritative Body CC/S/A CC/S/A (Stakeholders) Authoritative Body identifies identifies Candidate Authoritative Data Sources Data Needs to fulfill a set of 3) Candidate Authoritative Data Source Access Timeline Process 4) Authoritative Data Source Designation Process works with works with Authoritative Body Authoritative Body CC/S/A CC/S/A designates Identifies planned date for making data available via data services. Candidate Authoritative Data Sources Authoritative Data Sources to fulfill a set of Note: COCOMS, Services, Agencies, CPMs and COIs may also be authoritative bodies.

  5. Operational ConceptUnanticipated User (Use Case) Enterprise Authoritative Data Source Registry DITPR Authoritative Data Sources DISR C2 CPM SESS designates Service Registry works with identifies candidate ADSs CCIC2S CC/S/A (AF) Space Task Orders COI Directory MDR NCES Enterprise Search STO Data Searches URL for User Access Task Desc. … Accesses Operator 5 5 The ADS Registry will enable operators to discover authoritative and other registered sources to meet their data needs

  6. Operational ConceptDeveloper (Use Case) Enterprise Authoritative Data Source Registry DISR Systems/Tools Data stores/ Databases Access Mechanism Service Registry C2 CPM SESS designates works with COI Directory CC/S/A (AF) Space Tasking Orders CCIC2S identifies candidate ADSs MDR Searches Developer Resources • WSDLs • XSDs • Web Service EndPoints • Service Metrics Accesses Developer 6 The ADS Registry will enable developers to fuse data from other registered sources into new applications which are then discovered by the operators

  7. Primary Requirements • Based on the Operational Concepts • To provide a registry allowing for the registration, designation, and discovery of Authoritative Data Sources • To provide a workflow for the specification and registration of: • Data Needs • Candidate Authoritative Data Sources, including • Systems and Tools through which data is currently exposed • Data stores and Databases from which data is exposed through identified Systems or Tools • To provide an ability to bind a Candidate Authoritative Data Source to a registered Data Need • To allow for the specification of timelines (QQ/YYYY) in which Candidate Authoritative Data Sources will expose data through data services • To provide the ability to bind Systems, Tools, Data stores, and Databases to registrations in the DoD Metadata Registry, NCES Service Registry. • To provide a workflow for an Authoritative Body, or delegate thereof, to formally designate a given Candidate Authoritative Data Source as Authoritative for one or more registered Data Needs.

  8. Primary Registration Workflow creates new chooses to Register Data Need Data Need executes processes Register Data Producer Data Producer Data Collection User logs into the ADS Registry via DKO SSO. Register System or Tool System or Tool Register Data store or Database Data store or Database binds/proposes Specify/Propose Candidate ADS Data Association reviews ADS Approval Designate ADS Candidate ADS ADS (Approved) approves Data Need Data Need Authoritative Bodies that have approved this ADS will be notified of any changes. Data Producer Data Producer yes no remains candidate, marked as unapproved candidate ADS becomes approved ADS System or Tool System or Tool Data store or Database Data store or Database Can be changed at any time. 8 Privileged User (Authoritative Body or delegate)

  9. Deployment Model Metadata Registry Application Server Enterprise ADS Registry Web Application Metadata Registry Web Application Net-Centric Publisher Web Application NCES Service Discovery Web Application Metadata Registry ebXML Web Services ( OMAR v 3 . 0 ) Tomcat Server (v.5.5.28) Database Tier Enterprise ADS Registry Database Net-Centric Publisher Database Metadata Registry Database ebXML RIM Database Oracle ( v 10 g ) • Deployment Footprint • - NIPR Primary (DECC - COLS) • - NIPR Backup (DECC - SATX) • - SIPR Primary (DECC - COLS) • - SIPR Backup (DECC - SATX) • Continuity of Operations Plan (COOP) • - Piggyback on the MDR COOP • - MDR COOP successfully exercised and observed by JITC • NIPR 11 May 2009 • SIPR 05 May 2009

  10. Interfaces • User Interface • Web-based User Interface • Standard Web Technologies • HTTP • HTML • Javascript • Support for common web browsers • Internet Explorer 7, Internet Explorer 8 • Firefox 3 • Machine Interfaces • Internal • Leverage NCES UDDI Interface for service information • Leverage internal MDR interfaces for COI Directory and MDR Governance Namespace information • External Developer Facing • TBD • Anticipate Web Services interfaces to support discovery • Anticipate Web Services interfaces to support registration & workflows

  11. Initial PrototypeScreenshot (Home) Demonstration 11

  12. Questions? ? 12

  13. Deployment Schedule • 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 • Incremental improvements to NIPR MDR Test Suite will occur during this period • Incorporate User Feedback in Initial Release: FEB - APR ’10 • Phase 2, Migrate prototype to Production: MAY ‘10 • Deployment on production MDR (NIPR,SIPR) • Includes backup sites to effect immediate COOP ability • Phase 3, O&M • Tier 2 & 3 support, minor enhancements to production system • Will become integral component of the NCES Metadata Environment 14

More Related