the sale architecture and the missing link - the pathfinder pilot
Post on 14-Jan-2016
27 Views
Preview:
DESCRIPTION
TRANSCRIPT
Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
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
2Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
End-to-End Technical Data IntegrationEnd-to-End Technical Data Integration
PLM +
Enterprise IntegratedData Environment - EIDE
(DLA)
TRANSCOM
OEM
PDM
Weapon SystemProgram Office
Engine
Module
Bld. Grp
Locator
Part
Bld. Grp
Locator
Part
Locator
Part
Mobile PlatformOptimized System Environment
Objective: Single set of technicaldata for all Army equipment- also used by DLA & other
external constituents!
Field - GCSS Army
National - LMP
Provides an opportunity for
joint Interoperability
Collaborative ProductDevelopment
One Set of Technical Data
Single Army Logistics Enterprise
3Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
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.
SALE/ PLM+ is viewed as an immediate, primary and ultimate beneficiary of the results of this pathfinder.
4Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
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
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
5Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
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
6Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
Why ISO 10303 STEP? USD Kenneth Krieg, June 23
2005 memorandum recommends:
u Implementing an approach for managing digital product/technical data across DOD
u Ensure product model data meets ISO STEP requirements
u Adoption of ISO 10303 to enhance interoperability
u 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
7Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
It Takes More Than PLCS
ISO 10303-239: PLCS StandardSemantic interoperability
Common dictionary
Data representation
Data Exchange Sets (DEX) Reference Data Library (RDL)
OASIS PLCS Web Services 1.0Access control/ Security
Synchronization Rules
Enterprise search and retrieve
Change management
Event Management
Subscriptions
SAP Netweaver/ XIWeb services execution
Mapping PLCS to IDOCS
Federated SALE Architecture
8Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
AM GeneralAM General TACOM LCMCTACOM LCMC
SAP
PLM
Power LOG -J
LAISO SAP
Test Bed
Windchill
PDMLink
Share-A-Space Web Client
Pathfinder Process Flow (Phase 1)
M1151
3D CAD
Models
XML
Export
SAP XML->
PLCS Mapper
13882B->
Export
13882B->PLCS
Mapper
Data Selection
Netweaver/XI
PLCS->IDOC Mapper
Web servicesand file transfer
Access ControlData viewsValidation & CorrectionSource identificationConfigurationsConsolidated BOMs
Future DEX
Future DEX
Future DEX
LSARIETMMaintenance Level PlanRPSTLsNMWRMWO
DrawingsConfig. ManagementVersion historySpecificationsTech Data PackagesProblem ReportsECP, ERR, RFDAssociated DocsSerial NumbersBaselines
3D CAD Assy. StructureAs-designed BOMAs-built configurationMRP
Notification and MonitoringServices
Change request
STEP
AP214
Export
Design Changes
9Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
Implementation Plan Phase 1 (9 months after contract award):
u Leverage current TACOM/HMMWV pilot projectu Integrate data into PLCS format using currently available exchange
translators (non-DEX approach)u Demonstrate change management across systems (Windchill, AM
General SAP, Army SAP) and functional domains (engineering, logistics)
u Push pre-positioned data into out of the box Army SAP
Phase 2 (21 months after contract award):u Implement concurrently with Phase 1u 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):u Integrate DEX’s developed with Phase 1 implementationu 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
10Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
Cost EstimatesCost Element Phase 1 Phase 2 Phase 3
Software purchase $100,000 N/A N/A
Software installation & configuration services
$200,000 N/A N/A
Hardware $20,000 N/A N/A
Training $20,000 N/A N/A
System integration & consulting services $400,000 N/A N/A
Testing $100,000 $80,000 $200,000
DEX development services N/A $400,000 N/A
Software development services N/A N/A $250,000
In-house salaries $80,000 N/A $40,000
Travel, reporting, misc. $20,000 $20,000 $10,000
Sub Total $940,000 $500,000 $500,000
TOTAL $1,940,000
11Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
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
12Integrated Logistics Enterprise = Common Operating PictureIntegrated Logistics Enterprise = Common Operating Picture
What do we need from OASIS Need to work DEX’s important to the Army through OASIS
u Product Structure DEX (DEX1) – ensure it is completed through OASISu LSAR DEX – based on business rules developed through GEIA-0007u Configuration Management DEX (multiple) – based on business rules developed
through EIA-836u Generic Maintenance DEX – based on Aviation Maintenance DEX being developed
through Army/NAVAIR ELITE projectu 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?
top related