1 / 12

The SALE Architecture and the Missing Link - The Pathfinder Pilot

The SALE Architecture and the Missing Link - The Pathfinder Pilot. Presented to: OASIS PLCS Technical Committee Face to Face meeting, Huntsville, AL Oct 31 – Nov 1, 2006. Single Army Logistics Enterprise. Motivation.

bart
Download Presentation

The SALE Architecture and the Missing Link - The Pathfinder Pilot

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. The SALE Architecture and the Missing Link- The Pathfinder Pilot Presented to: OASIS PLCS Technical Committee Face to Face meeting, Huntsville, AL Oct 31 – Nov 1, 2006

  2. Single Army Logistics Enterprise

  3. Motivation • SALE needs accurate/validated technical data from authoritative sources to feed various logistics business processes • Need to address total lifecycle data management and master data management for the Army enterprise • Need for end to end configuration management of weapon system and data across the extended Army enterprise • Need to address heterogeneous systems and data formats across Army and OEMs • Need for standardized delivery and access to product data from OEMs SALE/ PLM+ is viewed as an immediate, primary and ultimate beneficiary of the results of this pathfinder.

  4. Strategic Objective To validate a set of interoperability requirements for the Army and Industry partners to exchange product data based on a standard lifecycle data model as defined in STEP PLCS for implementation by PM SALE

  5. Pathfinder Objectives • Demonstrate the use of ISO 10303-239 STEP Product Life Cycle Support (PLCS) standard as an integrated lifecycle data format for managing products • Demonstrate the use of Service Oriented Architecture (SOA) using PLCS web services for federating data across multiple enterprise systems • Demonstrate the Product Variant Structure (PVS) approach to support the multiple BOM approach (currently used within SAP SALE) • Preposition and import PLCS data into an out of the box Army SAP ERP (full scope will include all current and future ERP’s) • Demonstrate “to-be” OEM-Army data exchange business processes using “golden” data • Identify gaps and limitations in the PLCS standard or COTS product implemented

  6. USD Kenneth Krieg, June 23 2005 memorandum recommends: Implementing an approach for managing digital product/technical data across DOD Ensure product model data meets ISO STEP requirements Adoption of ISO 10303 to enhance interoperability Ensure procuring activities plan, purchase and accept delivery of product/technical data only in digital formats specified by the Guidance on contracts awarded ISO 10303 appears to have the most breadth and depth of coverage for product lifecycle data. ISO 10303-239 (Product Lifecycle Support, PLCS) is currently the only international standard available that covers the entire lifecycle spectrum. NIST believes that PLCS has great potential to handle the Army’s PLM requirements, but recommends the Army resolve certain challenges before firmly committing to its adoption. - NISTIR 7339 – Analysis of standards for lifecycle management of systems for US Army – A preliminary investigation Why ISO 10303 STEP?

  7. It Takes More Than PLCS Federated SALE Architecture SAP Netweaver/ XI Web services execution Mapping PLCS to IDOCS OASIS PLCS Web Services 1.0 Access control/ Security Synchronization Rules Enterprise search and retrieve Change management Event Management Subscriptions ISO 10303-239: PLCS Standard Semantic interoperability Common dictionary Data representation Data Exchange Sets (DEX) Reference Data Library (RDL)

  8. Pathfinder Process Flow (Phase 1) 3D CAD Assy. Structure As-designed BOM As-built configuration MRP AM General TACOM LCMC Future DEX SAP PLM Windchill PDMLink STEP AP214 Export XML Export Data consolidation Data consolidation Change request SAP XML-> PLCS Mapper Drawings Config. Management Version history Specifications Tech Data Packages Problem Reports ECP, ERR, RFD Associated Docs Serial Numbers Baselines M1151 3D CAD Models Notification and MonitoringServices Future DEX Design Changes Future DEX 13882B->PLCS Mapper Share-A-Space Web Client Access Control Data views Power LOG -J Validation & Correction Data Selection Source identification 13882B-> Export Configurations Consolidated BOMs Web services and file transfer LAISO SAP Test Bed LSAR IETM Maintenance Level Plan RPSTLs NMWR MWO Netweaver/XI PLCS->IDOC Mapper

  9. Implementation Plan • Phase 1 (9 months after contract award): • Leverage current TACOM/HMMWV pilot project • Integrate data into PLCS format using currently available exchange translators (non-DEX approach) • Demonstrate change management across systems (Windchill, AM General SAP, Army SAP) and functional domains (engineering, logistics) • Push pre-positioned data into out of the box Army SAP • Phase 2 (21 months after contract award): • Implement concurrently with Phase 1 • Develop and publish DEX’s and RDL’s for LSAR (based on GEIA-0007) and Configuration Management (EIA-836) • Phase 3 (6 months after contract award): • Integrate DEX’s developed with Phase 1 implementation • Plug in CECOM’s KonfigCM PDM into Pathfinder to show how product data on radios can be integrated with HMMWV (M1152) to demonstrate a platform view of the weapon system

  10. Cost Estimates

  11. Next Steps • Brief Process Executive on Pathfinder and obtain approval to proceed • Submit proposal to BTA (G3-EI) • Setup project team – identify roles and responsibilities • Finalize project implementation details with Eurostep • Conduct site visits to UKMOD, Swedish FMV, BAE Systems Hagglunds and Volvo to study their PLCS implementations • Arrange PLCS training for Pathfinder participants • Present DEX development plan to OASIS PLCS Technical Committee for endorsement • Meet with AM General to brief detailed project plan

  12. What do we need from OASIS • Need to work DEX’s important to the Army through OASIS • Product Structure DEX (DEX1) – ensure it is completed through OASIS • LSAR DEX – based on business rules developed through GEIA-0007 • Configuration Management DEX (multiple) – based on business rules developed through EIA-836 • Generic Maintenance DEX – based on Aviation Maintenance DEX being developed through Army/NAVAIR ELITE project • Generic UID DEX – based on DOD UID schema for the exchange of UID between systems • Need to ensure that PLCS Web Services is reviewed and approved as a standard through OASIS • Need to ensure integration between PLCS and S1000D (Ver. 3) – how can we integrate CAD geometry with IETMs through PLCS? • How do we integrate ISO 22745 (eOTD) cataloging at source with PLCS? • How does PLCS interface with Condition Based Maintenance / Sense & Respond standards such as OSA-CBM/ MIMOSA?

More Related