1 / 13

EIA-836 CM Data Exchange and Interoperability

NDIA TID Conference ~ Panama City ~ FL Dec. 3-4, 2001. EIA-836 CM Data Exchange and Interoperability. 2801 Park Center Drive, #A1612, Alexandria, VA 22302, Voice: 703 567 3280; 703 624 8857(Cell) Fax: 703 567-3279 E-Mail: alan_e_lager@email.msn.com http://www.mlrassociates.com.

chul
Download Presentation

EIA-836 CM Data Exchange and Interoperability

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. NDIA TID Conference ~ Panama City ~ FL Dec. 3-4, 2001 EIA-836CM Data Exchange and Interoperability 2801 Park Center Drive, #A1612, Alexandria, VA 22302, Voice: 703 567 3280; 703 624 8857(Cell) Fax: 703 567-3279 E-Mail: alan_e_lager@email.msn.com http://www.mlrassociates.com Alan E. Lager, MLR Associates

  2. Agenda EIA-836 CM Data Exchange and Interoperability • Introducing EIA-836 • EIA-836 Goals • Industry-Government Partnership • EIA-836 Background • Elements of Information Exchange • Harmonization • EIA-836 Current Status • EIA-836 Work to be Accomplished • EIA-836 Table of Contents • Live View of EIA-836 Document and XML Schema • EIA-836 Websites

  3. Introducing EIA-STD-836 • A web-based voluntary industry consensus standard • CM Data Element and Attribute definitions • Comprehensive CM “Reference Vocabulary” • XML Reference Schema graphically illustrating data element relationships • Context for CM data definitions • Basis for future Data Models • Content Templates for CM Business Objects • Documents, Transactions, Messages, Inquiries

  4. EIA-836 Goals • Enable CM data exchange, sharing, and access within electronic business (e-business) environments • Satisfy industry and government needs • Data transport technology neutral • Database neutral • Large corporation and small business compatible • Scalable, extensible, and adaptable • Open access to the standard • Efficient process for maintenance of the standard

  5. Industry-Government Partnership DoD Replace MIL-STD-2549 with Industry Standard Leverage Industry Practices Standardize and Streamline DoD Data Interfaces GEIA Support Acquisition Reform Provide Modernized Capability Broaden Scope to include all Industry Domains Government/ Contractor  Trading Partners

  6. EIA-836 Background Industry Practices Based on Sound Principles DoD Mandated Standards Evolution of CM Standards MIL-STD-973 and MIL-STD-2549 ANSI/EIA-649 and EIA-836 Leverage the latest information technologies and systems, e.g., XML “Harmonize” with related programs, e.g, EDI, STEP, PDM, IDE,etc. Broaden applicability to include the commercial sector GEIA EIA-836 Objectives

  7. Elements of Information Exchange Business Process ANSI/EIA-649 CM Business Objects being exchanged Business Objects EIA-836 Focus CM Data Elements and Data Element Definitions Data Elements Transport Mechanism

  8. Harmonization • Multi-View Project, Trident Systems • Common Systems Info Schema will use 836 • PLCS CM Working Group Collaboration • Consistent data element definitions • Leverage 836 CM Business Objects • AIA EC Working Group • Harmonize Data Element Overlaps EDI/STEP/PLCS/836 • DoD Systems Engineering Namespace • DEBCO • PDML Demo using EIA-836 Business Objects

  9. EIA-836 Current Status Requirements Analysis A Work-in-Process Data Dictionary & Schema Development Integration and Packaging EIA-836 Draft 0.1 Review We are here Additional Schemasand Text EIA-836 Draft 0.3 Review EIA/ANSI Ballot, Approval, Deployment and Maintenance Draft 0.4, 0.5. AdditionalBusiness Object Development

  10. EIA-836 Work To Be Accomplished • GEIA Ballot Process/ANSI Review • Comment Review and Revision • Continue Harmonization PLCS, STEP, EXOSTAR, etc. • Packaging and Publication • Web, PDF, Registration of schemas • Beta Site/Testing • Maintenance/Continuous Improvement

  11. EIA-836 Table of Contents Foreword Introduction 1. Scope 2.Normative References 3. Definitions 4. Symbols & Abbreviations 5. CM Business Objects 5.1 CM Planning & Management 5.2 Configuration Identification 5.3 Configuration Change Management 5.4 Configuration Status Accounting 5.5 Configuration Verification & Audit 5.6 Data-Document Management 5.7 General Business Objects 6.CM Data Dictionary 7. CM Reference Schemas 7.1 Core Components 7.2 Business Relationships 7.3 Product Detail 7.4 Product Configuration 7.5 Document 7.6 CM Actions 8. Application Notes AnnexesA EIA-836 User GuidanceB Data Element – Alias Cross-RefC EIA-836 to EIA-649 Principles Cross-RefD Data Element – UDEF Cross-Ref.

  12. Live View of EIA-836 Document and XML Schema • View of EIA-836_Draft04.doc • Business Object • Text Description • DTD • Viewed with XML Editor • Schema Diagram Representation • User View Representation • CM Data Dictionary • EIA-836.dtd – Reference Schema

  13. EIA-836 Websites • GEIA EIA-836 Home Page: http://www.geia.org/836/default.htm or http://www.geia.org/sstc/index.html • EIA-836 Working Group Site: http://acet.saic.hcst.net:8080/eia836/main.htm • ManTech hosted Document Automated Comment System for EIA documents:http://dcnicn.com/custcomm/eia649 • Comment to EIA-649A, MIL-HDBK-61A and EIA-836 • MLR Associates Home Page:http://www.mlrassociates.com

More Related