1 / 11

The EIA-836 Project A Model for Government –Industry Standardization Synergy

2001 Standardization Symposium. The EIA-836 Project A Model for Government –Industry Standardization Synergy. 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

said
Download Presentation

The EIA-836 Project A Model for Government –Industry Standardization Synergy

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. 2001 Standardization Symposium The EIA-836 ProjectA Model for Government –Industry Standardization Synergy 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 The EIA-836 ProjectA Model for Government –Industry Standardization Synergy • EIA-836 “CM Data Exchange and Interoperability” • EIA-836 Background/Objectives • Industry-Government Partnership • The Leveraging Effect • Current Status • Lessons Learned – Keys to Success

  3. EIA-STD-836 CM Data Exchange and Interoperability • A web-based voluntary industry consensus standard • Configuration Management Business Objects • CM Data Element and Attribute definitions • XML Reference Schema graphically illustrating data element relationships • Enable CM data exchange, sharing, and access within electronic business (e-business) environments • Satisfy industry and government needs

  4. 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

  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. The Leveraging Effect Maximum Industry Participation and Exposure Minimum DoD Investment   Approved Standards Process 836 Oversight Committee AIA, LMBoeing, Raytheon ANSI SSTC ITI G-33 CM/DM Committee EIA-836Working Group GEIA G-47 SE/SW GEIA Member Company Representatives Funded Core Group DoD ManTech WVA Other AssociationsNDIA, ACDM, SOLE, INCOSE, AIA-ECWG LMI Interfaces/HarmonizationPLCS, STEP, DEBPO/PDML, EXOSTAR MLR SAIC

  7. 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

  8. Lessons Learned –Keys To Success • Believe in the Value-Added Nature of the Project • Find others who agree (some of them may even have funding!) • Work at Building Team Trust and Confidence • Find common ground and build on it • Be Open, Honest and Supportive • Value the expertise and experience of all participants • Work to Consensus • Build support early through coordination with others • Endure the slings and arrows of outrageous review meetings • Admit error; compromise; iterate; revise • Results must be BOTH right AND accepted

  9. Back-up Slides

  10. 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.

  11. 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 • DEBPO • PDML Demo using EIA-836 Business Objects

More Related