RFI Requirement Document final.docx

Product Lifecycle Management (PLM) and Data Competency Center (DCC) Data Objects Cleansing Logistics Transformation

For

Tinker Air Force Base

ACRONYM LIST

ACO Administrative Contracting Officer APS Advanced Planning and Scheduling AF Air Force

CAC Common Access Card

CSA Cognizant Security Agency CoP Community of Practice COTS Commercial Off the Shelf DAC Days after Contract DART Data Accuracy and Review Tool DCC Data Competency Center

DLIS Defense Logistics Information System eLOG21 Expeditionary Logistics for the 21st Century ERP Enterprise Resource Planning FAR Federal Acquisition Regulation GCA Government Contracting Activity

JEDMICS Joint Engineering Data and Management Information Control System JTR Joint Travel Regulations LogEA Logistics Enterprise Architecture MBOM Master Bill of Material MRO Maintenance, Repair, and Overhaul NO Number OEM Original Equipment Manufacturer OSS&E Operational Safety, Suitability, and Effectiveness

PCMS Parts Configuration Management System PM Program Manager PLM Product Lifecycle Management

TO Technical Order

Purpose

The purpose of this request for information is to gain feedback from industry possessing capabilities to provide engineering services to research Air Force (AF) product data to create an indentured product structure with required part and drawing attributes. AF product data is contained in systems such as; D043, G005M, D200, G004L, Haystack®, Joint Engineering Data and Management Information Control System (JEDMICS), PDM Gateway, Parts Configuration Management System (PCMS) and other cataloging systems. This requirement also supports Data Competency Center activities to attain the level of preserving the overall baseline performance characteristics required for logistics transformation management responsibilities. Requirement is to clean the configuration baseline product structure data in the Product Lifecycle Management (PLM) system, cleansing of Data Competency Center Data Objects and support logistics transformation. Utilize established processes, procedures and tools to aid the Air Force in Illustrated Parts Breakdown (IPB) light/heavy cleansing, Data Competency Center Data Objects deficiencies cleansing, Maintenance Bill & Material cleansing and Data Object Logistical transformational deficiencies cleansing requirements.

Scope

The scope is to research, verify and/or correct missing, incomplete or incorrect part information derived from commodities and weapon systems Illustrated Parts Breakdown (IPB) technical orders and other sources of technical data. Work in conjunction with Technical Content Managers (TCM) and other personnel representing the Cognizant Engineering Authority (CEA) for commodity and weapon systems. The AF will provide access to the information systems necessary to identify errors and document corrective actions to these errors. The AF will provide IT infrastructure and .mil access to information sources to be used to identify and correct these errors. These information sources may be managed within the AF, another government agency, or a private/commercial source. All information sources shall be accessed electronically via .mil networks. Software tools to be used/accessed for data research and clean up include JEDMICS, PDM Gateway, PCMS, Data Accuracy and Review Tool (DART), and PLM Data Vault. USAF will also provide end to end PLM IPB training tool. Utilize developed procedures and tools documented during previous PLM IPB projects to aid the Air Force in Illustrated Parts Breakdown (IPB) heavy clean up requirements in support of cleansing commodities and weapon system product structures (IPB’s). Support OC-ALC Data Competency Center (DCC) team in analysis and technical deliverables by specific variances outlined in appendix D identified as DCC Data Objects. AF provides access to the information systems necessary to work defined deficiencies and to support documenting corrective actions to these deficiencies. These variances are represented by each data objects ability to meet Elog21 established Product Lifecycle Management (PLM) goals for the USAF.

Background

The Air Force is currently engaged in a logistics enterprise transformation initiative known as Product Lifecycle Management (PLM). One of the primary data requirements is the Master Bill of Materials (M-BOM). The M-BOM defines all of the part items within AF systems and their relationship to one another. The M-BOM along with engineering data provides the configuration baseline for all AF managed systems. Configuration management is vital to the requirements driven by the Operational Safety, Suitability, and Effectiveness (OSS&E) in accordance with Air Force Instruction (AFI) 63-1201. The M-BOM data will also be the primary source to develop other bills of materials utilized. This initiative will utilize data in Illustrated Part Breakdown (IPB) Technical Orders (TO) as its primary source of M-BOM data. The M-BOM data supporting today’s AF data systems will require significant cleanup to meet the functional requirements necessary to manage configuration and to derive the multiple bills of material required. The Air Force vision of PLM as a single source of product data, including M-BOM, across the Air Force enterprise is a key enabler in supporting the Logistics Enterprise Architecture (LogEA) future state and as foundational data for other Expeditionary Logistics for the 21st Century (eLog21) initiatives.

Requirements

Data cleansing for commodities and weapon systems PLM IPB cleansing process with AFTO 252, AFTO 22 action generation & AF Form 3925 & AF Form 3927 when engineering drawings impacted by cleansing requirements. Support DCC Data Objects cleansing, deficiencies resolution, implementation and logistics transformation requirements.

Description Interested parties should be able to provide engineering services to research, verify and/or correct missing, incomplete or incorrect component information derived from IPB technical orders and other sources of technical data. Interested parties should be able to work in conjunction with TCMs and other personnel representing the CEA for the assigned system/data. The Interested parties will utilize IPB data capture and light/heavy cleansing developed procedures and tools to aid the Air Force in Illustrated Parts Breakdown (IPB) light and heavy clean up requirements in support of to aid the Air Force in Illustrated Parts Breakdown (IPB) heavy clean up requirements in support of cleansing commodities and weapon system product structures. Interested parties should be able to provide verified and validated errors and recommended AFTO 252 changes & AFTO 22 & AF Form 3925 & AF Form 3927 when engineering drawings impacted by cleansing. Interested parties should be able to assist the commodity and weapon systems Technical Content Managers (TCM) to clearly define recommended AFTO 252 changes with AFTO 22 documentation & AF Form 3925 & AF Form 3927 when engineering drawings impacted by cleansing. Interested parties should be able to provide engineering services to research, verify, assist with implementation and provide DCC technical deliverables identified as Technical Report -Study/Service by specific data objects outlined in Appendix D identified as DCC data objects.

Data Cleansing.

Interested parties should be able to research D043, G005M, D200, G004L, Haystack® and other cataloging systems and engineering drawings for the commodities and weapon system IPB’s to ensure the correct part number(s) for the assembly referred to in the IPB are accurate. Interested parties should be able to document/identify corrections as necessary to the source system and also document these required changes in tool for tracking.

To identify corrective actions, interested parties should be able to work with the CEA, the Original Equipment Manufacturer (OEM) and TCM. Additionally, the potential vendors may be required to access both AF and OEM tools to assist in the analysis. As corrections are identified, interested parties should be able to update part information using tools and processes provided by the AF, to track AFMC forms 252 & AFTO 22 & AF Form 3925 & AF Form 3927 when engineering drawings impacted by cleansing actions. The AF will provide the prioritized IPB’s schedule. The AF reserves the right to modify the schedule prior to its introduction into the production cleanup process. It is expected that any single attribute will not require more than 4 minutes of research to correct. Any attribute that clearly would require more than 4 minutes in establishing corrective actions will be identified within the tools provided, IPB package updated with history and researched information and referred to the CEA for resolution.

a) Appendix A lists examples of errors that the AF expects to be encountered during IPB cleansing activities.

b) Appendix B Air Force IPB Cleansing Process.

c) Appendix D IPB Acceptance Group Categories.

d) Appendix E IPB Standard Common error codes.

Interested parties should be able to update this list of errors and time to correct as additional types of errors are identified. Potential vendors may encounter proprietary data/drawings and will require assistance from CEA for resolution. Working with OC-ALC DCC team assess the DCC data objects identified in appendix D to detect onset of deficiencies for research, document correct actions and assistance with implementation of solution and provide OC-ALC DCC team Technical Report identifying deficiency and recommend correction action. DCC data object is defined as technical deliverables from HQ AFMC/DCC identifying corrections, analysis required and/or assistance on implementation of correction on identified DCC data objects in question.

Estimated Effort.

The commodities group has approximately 6635 Commodity IPBs, ranging from 150 records an IPB up to 1000 records an IPB. Additionally, there are approximately 355 weapon system IPBs and 2,840,000 records for the weapon systems that require light and heavy clean-up processing. Estimated Error rate based upon USAF cleansing projects has established error rate at 47% and estimated time to review IPB errors is 4 minutes and time to correct per IPB error is 4 minutes (documenting AFTO 252,AFTO 22 actions, AF Form 3925 & AF Form 3927).

Any DCC data object and Master Bill and Material (MB&M) deficiency record that clearly would require more than 4 minutes to research and 4 minutes in establishing corrective actions to one record will be identified (Technical Report -Study/Service, package updated with history/research data and referred to the CEA for resolution.

a) IPB’s cleansed per year breakdown is as follows

- FY11 (Commodities IPB’s) 880

- FY12 (Commodities IPB’s) 2333

- FY13 (Commodities IPB’s) 3013

- FY14 (Commodities IPB’s) 469

- FY12 (Weapon System IPB’s) 53

- FY13 (Weapon System IPB’s) 117

- FY14 (Weapon System IPB’s) 160

- FY 15 (Weapon System IPB’s) 25

b) DCC data object technical deliverables is defined as report generated by HQ AFMC/DCC office that identifies deficiency in one data object identified in appendix C requiring problem resolution be conducted, document technical solution and support implementation technical solution. Technical Report -Study/Service is estimated not to exceed;

· FY12 Total DCC records 214,000

· FY13 Total DCC records 327,600

· FY14 Total DCC records 286,000

· FY15 Total DCC records 328,900 Note: One deficiency is defined as 2150 records for FY12, one deficiency is defined as 3275 records for FY13, one deficiency is defined as 3275 records for FY14 and one deficiency for FY15 is defined as 3275 records.

c) Technical Documents (IPB, drawing, commercial manual, spreadsheet) cleansed and Master Bill and Material (MB&M) data delivered electronically (CD and backup hard drive) utilizing PCMS/light DART format outlined in appendix E.

Note: One deficiency is defined as 1950 records for FY13, one deficiency is defined as 2875 records for FY14, and FY15 one deficiency is defined as 3250.

d) DCC Data Object Logistical transformational deficiency record data object resolution is defined as report generated by DCC Program Management Office (PMO) that identifies deficiency in one data object identified in appendix D requiring problem resolution be conducted, document technical solution and support implementation of technical solution.

· FY11 Total deficiency resolution 947,779 records.

· FY12 Total deficiency resolution 1,184,724 records.

· FY13 Total deficiency resolution 565,500 records.

· FY14 Total deficiency resolution 819,000 records.

· FY15 Total deficiency resolution 1,285,700 records.

Note: One deficiency is defined as 11300 records for FY11 and FY12 one deficiency is defined as 12400 records for FY14 and FY15 one deficiency is defined as 14450.

e) Bill of Material (BOM) F101, F110, F108, F118-100, TF39, T56, J85, F107 & TF34 engines engine) updated in Product Lifecycle Management System (PLMS) data base utilizing cots tool identified as Teamcenter Enterprise 2007. Knowledge and utilized Teamcenter Enterprise 2007, be able to configure parts, has conducted data cleansing activities, BOM entries and modify parts. Required to provide engines and weapon systems troops over the shoulder Teamcenter Enterprise 2007 training and conference room type training as we update these PLMS requirements (not to exceed 40 troops for each engine and weapon system, roughly 50 troops over time). This will require close working relationship with USAF PLMS program office at Gunter AFB.

Corrections to Source Data.

Interested parties should be able to submit recommended changes/corrections to IPB part data utilizing established processes. See Appendix B for detailed process flow and End to End PLM IPB cleansing training tool. During the course of IPB cleansing activities, interested parties should be able to identify errors in drawings and/other technical documents. These errors shall be recorded and tracked. Each validated IPB will have a project folder/binder containing the minimum of a cover page of the IPB being worked. These folders/binders will consist of a DART light & heavy clean up file, JEDMICS information clean up file, heavy clean up manual/tool file, AFMC form 252, AFTO 22, AF Form 3925 & 3927 action recommendations. Folder/binders will be submitted to the assigned USAF TCM for validation and AFMC Form 252, AFTO 22, AF Form 3925 and 3927 incorporation. DCC data object technical deliverables is defined as report generated by HQ AFMC/DCC office that identifies deficiency in one data object identified in attachment requiring problem resolution be conducted, document technical solution and support implementation technical solution.

Use of AF, DOD and Commercial Tools and Databases.

The AF shall provide access to information sources (JEDMICS, PDM Gateway, PCMS, Data Accuracy, Review Tool (DART), and End to End PLM IPB cleansing training (CBT) to be used to identify and correct errors in technical data. DCC Data Objects, MB&M, PLMS and DCC Data Object Logistical transformational deficiencies will be provided along with .mil access to application/data bases containing information to work these issues. Document and track all corrective actions to these errors. Information sources may be managed within the AF, other government agencies, or private/commercial sources. All information sources shall be accessed electronically via .mil networks.

Data Validation/Approval.

Work with the CEA at both Global Logistic Supply Chain Center and AF Materiel Command Air Logistics Center Data Competency Centers (DCC) PLM focal points. Communicate corrective actions identified and validated to the assigned TCM for approval and concurrence. Assist assigned TCM with documenting recommended changes through the cleanup process to the appropriate published engineering and technical data. This includes generating change packages for technical orders and drawings/models in accordance with prescribed AF policies and procedures. Utilize current processes and implement new processes to prevent redundant research on common parts and deficiencies.

Quality Assurance.

Utilize an approved statistical sampling technique to ensure compliance with the Quality Assurance Surveillance Plan (QASP). Validation of corrective actions to part attributes shall be at least 99% accurate as independently validated utilizing the authoritative source for the specific part item attribute (e.g. an engineering drawing). Customer satisfaction will be measured through formal complaints issued between the customer and quality assurance personnel.

Metrics and Reporting.

Provide a monthly status report. This report shall include detail errors corrected by attribute category, amount of technical orders processed, DCC data objects, DCC Data Object Logistical transformational deficiency, PLMS deficiencies and MB&M deficiencies worked (deficiency reports if warranted). No more than 2 errors per month shall be committed while validating/verifying technical data. Compile initial tech order statistics and initial complexity factors utilizing USAF cleansing projects statistics and complexity factor process Compile types of tech orders processed, i.e. PDF Files, SGML. DCC data objects, MB&M, PLMS and DCC Data Object Logistical transformational deficiencies worked. Deliver data within 99% on time in compliance with the established burn down plan. Provide reports of source data corrections, projected schedule, rate to completion, time to assist USAF equipment specialists in approving recommend AFTO 252, AFTO 22 ,AF Form 3925 & AF Form 3927 actions and other USAF representatives in cleansing activities and any issues associated with meeting contractual requirements as outlined in;

a) DI-MGMT-80368A (Monthly Status Report).

b) DI-ALSS-8153 ( Deficiency Report)

Project Management/Reports.

Document task, schedule, risk management and expenditure plans in Management Plan, Master Schedule, Cost/Schedule Status report, Risk Management Plan and Risk Management Report as outlined in DI-MGMT-80004, DI-MISC-81650, DI-MGMT-81467, DI-MGMT-81809, DI-MGMT-81808.

Expertise/Professional Services

In support of this Product Data Cleansing, interested parties should be able to possess working knowledge of technical cleansing solutions and processes in support of these requirements. Interested parties should be able to possess comprehensive skills on the following:

a) Reading and interpreting technical drawings/models

b) Reading and interpreting milspec and/or commercial IPBs

c) Experience as an equipment specialist, engineer, financial, maintenance planner, logistic manager, engineering technician, production work leader, or other technical areas working on AF or other military data objects/elements.

d) Experience/Familiarity with systems providing technical information related to parts including D043, G005M, D200, G004L, Haystack® and other cataloging systems, and Joint Engineering Data and Management Information Control System (JEDMICS)

e) Familiarity in accessing PCMS and PDM-Gateway (.mil computer access required)

f) Familiar with and interpreting information from AF developed cleansing tools

g) Familiar with AF developed data cleansing processes

h) Experience with Microsoft Products

i) Experience with Teamcenter Enterprise 2007

j) DCC Data Objects familiarity

k) MB&M experience/familiarity

l) Experience with drafting and processing AFTO 22, AFTO 252, AF Form 3925, AF Form 3927 and technical reports.

Configuration Management.

Configuration Management (CM) process to: identify methods, procedures, and controls used to assure effective configuration identification, change control, status accounting and audits of Product Lifecycle Management (PLM) and Data Competency Center (DCC) Data Objects Cleansing Logistics Transformation requirements processes.

Appendix A

Missing SMR code

Appendix B

Air Force IPB Data Cleansing Process

1/18/2011

Appendix C

DCC Data Objects

AP = Accounts Payable BOM = Bill and Materail ECO = Enterprise Change Order ECR = Enterprise Change Request EAM = Enterprise Asset Management ETAR = Engineering Technical Assistance Request Mx = Maintenance ECN’s = Engieering Change Notice

Appendix D

IPB Acceptance Group Categories

Acceptance Group Categories

· Group I – No Discrepancies

· Group II – High Confidence with Recommended Changes

· IPB Error Validated to Source of Truth

· Group III – Suspect Records with Recommended Changes

· IPB Error with Conflicting Support Data

· Group IV – ES Input Required

· Time Limit Exceeded

· Proprietary Information

Appendix E

IPB Standard Common Error Codes image1.emf

Microsoft_Office_Excel_Worksheet1.xlsx Sheet1

Error Code Error Description

E0 No Known Error

E1 Index Reference in Error

E2 Part Number in Error

E3 CAGE Code Missing or in Error

E4 Indenture Error

E5 Description Missing or in Error

E6 UPA Missing or in Error

E7 UOC Missing or in Error

E8 SMR Code Missing or in Error

E9 Other

E10 JEDMICS Drawing has Errors

Sheet2

Sheet3