Generating S1000D Illustrated Product Data (IPD) Data Modules, with Applicability, from the GEIA STD 0007 Logistics Product Data (LPD)

Transcription

1 Generating S1000D Illustrated Product Data (IPD) Data Modules, with Applicability, from the GEIA STD 0007 Logistics Product Data (LPD) Rick Phillips Chief Logistician Boeing Rotorcraft Support Parker Owen Vice President, Technical Operations Integrated Support Systems, Inc. September 21 23, 2015

2 AGENDA Business Case S1000D IPD data modules sourced from LPD data Generating accurate/consistent applicability expressions in support of programs that have existing LPD data and those that do not Synchronizing Common Data Leverage existing data (with minor extensions) Lessons Learned Changes in Business Processes Changes in Data Authoring Processes 2

3 Opportunity: Generate consistent and accurate S1000D Illustrated Parts Data (IPD) data modules with applicability in support of varying program requirements from LPD 3

4 Generate S1000D IPD data modules from LPD Standard provisioning data exists on most platforms Most programs have an illustrated parts list to support their fielded product Often, the linkage between the two is cumbersome Multiple hand offs between organizations Out of sync ground rules Platforms often support multiple customers with minor configuration differences 4

5 Boeing Rotorcraft Support Strategy Reuse of data across Functions Customers To drive Higher data quality Lower cost To better support customers and manage the supply chain Via PBL contracts 5

6 Boeing Rotorcraft Common Source Database (CSDB) and Logistics Product Data (LPD) CSDB LPD Version: S1000D, Issue Supports multiple viewers Uses applicability to manage multiple customers and configurations Version: GEIA STD 0007, Rev B Process uses standard provisioning data currently developed to support DCN processes. Processes built to import legacy IPD data from an existing legacy publication, or a start from scratch development program Platforms using this approach AH 6 Little Bird and CH 47 Chinook Helicopter 6

7 Challenge: How to define and manage LPD source data in conjunction CSDB to enable IPD Generation 7

8 IPD Source Data Parts and related data (example, SMR Codes, NSNs) Parts Numbers and instances are defined/maintained in the LPD along with NSNs and SMR Codes Alternate Part relationships are defined/maintained in the LPD database Extended Nomenclatures for Part (DFP and DFL) are not typically defined or maintained in the LPD IPD Indenture, Quantity per Figure, Interchangeability, UOC have related data in LPD Identifiers DMCs and CSN/ISNs are not defined or maintained in the LPD 8

9 IPD source data, cont d ICNs and Graphic Files ICNs and Graphic Files representing the Figure can be referenced in the LPD, but are not defined or maintained in the LPD Graphic Hotspot Ids Related to Part Applications Graphic Hotspot Ids related to the Part Applications are not defined or maintained in the LPD Applicability Attributes and Identifiers Applicability attributes and identifiers (Product Attributes, Condition Attributes, Applicability Ids) are not defined or maintained in the LPD 9

10 Schema Extension of LPD Data elements not present in the LPD that were added to support the generation and maintenance of the IPDs and the interface to the CSDB Data Module Code (DMC) Illustration Control Number (ICN) and the ICN related to the Customer, the End Item Serial Number Effectivity and the Modification Identifier & End Item Serial Number Effectivity Graphic Hotspot Id to Part Application Applicability Identifiers Modification Identifier related to Change Authority Number association CSN/ISN specific data 10

11 CSDB and LPD Interfaces Required Identifier Synchronization with the CSDB Data Module Code (DMC) Illustration Control Number (ICN) Applic Ids Data Synchronization with the CSDB Applicability Cross Reference Table (ACT): Product attribute Id and enumerated values Product Attributes for Customer and End Item Serial Number Condition Cross Reference Table (CCT): Condition attribute Id and enumerated values Condition Attribute for Modification 11

12 S1000D and LPD Source Data Used in Applicability Generation Customer Association ACT Product Attribute that represents the customer System End Item (SEI) related to the Part Application *** End Item Serial Number ACT Product Attribute that represents the end item Serial Number System End Item Serial Number related to the Part Application *** Modification Number CCT Condition Attribute that represents the Modification Change (with End Item Serial Number Range) related to the Part Application *** *** Existing data in LPD 12

13 S1000D IPD DM Generation with Applicability LPD Viewer of IPD CSDB Viewer of IPD 13

14 S1000D IPD DM Generation with Applicability Benefits Gained With the source data in place, well formed DMs are able to be generated The content is able to be validated against the IPD schema and the BREX file(s) The applicability expressions generated are accurate and usable in the IETP Applicabilities generated are consistent and based on product and condition data that is synchronized between the LDP and CSDB The provisioning data in the IPD is in sync with the LPD IPD data is managed in LPD and data integrity rules enforced Aliasing to some identifiers (examples, customer, end item serial numbers, etc.) is defined in data and incorporated in the generation process. Some peculiar program requirements for data content/presentation (example, upper case vs. mixed case of specific nomenclatures), are handled in a standard way 14

15 Lessons Learned: 15

16 Lessons Learned Shared data requires common ground rules and agreed to update cycles Part data rules Applicability rules Change management rules Authoring Lessons Were able to create general use scripts to populate data to LDP that was scraped from existing Tech Pubs documents DM Generation Lessons All program variations could not be handled via customization attributes. A post processing script capability was created, so it could be applied to program specific requirements. Example, changing mixed case text to upper case. 16

17 Questions? 17