PWSrevision1.docx

Performance Work Statement

For

Product Lifecycle Management (PLM) Data Cleansing Requirements for

Tinker Air Force Base

24 Aug 2011

Prepared by:

OC-ALC/ENSN PLM Team Lead Jim Wallin 3001 Staff Drive. Suite 2AG69A Tinker AFB, OK 73145 Phone: (405) 736-2603

Table of Contents

Attachment 1 - Contract Data Requirements Lists (CDRLs) Attachment 2 - Expected Heavy IPB Cleansing Errors in Milspec Technical Orders Attachment 3 - IPB Data Cleansing Process Flow Attachment 4 - List of Commodities & Weapon System IPB’s Attachment 5 - Acceptance Group Categories Attachment 6 - IPB Standard Common Error Codes Attachment 7 - PCMS Heavy Cleanup Tool User Manual Attachment 8 - Business Rules Attachment 9 - Customer Complaint Record Appendix B – Government Furnished Equipment List (GFE) (this is appendix B of the contract)

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 COR Contracting Officer Representative COTS Commercial Off the Shelf DAC Days after Contract DART Data Accuracy and Review Tool DCC Data Competency Center

DLIS Defense Logistics Information System ECSS Expeditionary Combat Support 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 QASP Quality Assurance Surveillance Plan

1. INTRODUCTION

1.0 Purpose

The purpose of this effort is 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 (Acquisition Streamlining and Standardization Information System “ASSIST” will be utilized for reference only). This requirement is to hire contractors to clean the configuration baseline product structure data identified as Illustrated Parts Breakdown (IPB). The contractors shall utilize established processes, procedures and tools to aid the AF in Illustrated Parts Breakdown (IPB) heavy cleansing.

1.1 Scope

The scope of this effort is to research, verify and/or correct missing, incomplete or incorrect part information derived from commodities and weapon systems IPB technical orders and other sources of technical data. The contractor shall work in conjunction with Technical Content Managers (TCM) and other personnel representing the Cognizant Engineering Authority (CEA) for commodity IPB’s. The AF will provide the contractor access to the information systems necessary to identify and document corrective actions for errors. The AF will provide IT infrastructure and .mil access to information sources to be used to identify and correct these errors. Attachment “2” contains Expected Heavy IPB Cleansing Errors in Milspec Technical Orders from USAF pilot efforts. The 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, Parts Configuration Management System (PCMS), PCMS Heavy Cleanup Tool, and PLM Data Vault. The AF will provide on base facilities at Tinker AFB for max total of 3 contractors if required to be on base working along-side equipment specialists and engineering. The contractors shall utilize developed procedures and tools documented during previous USAF IPB cleansing projects to aid the AF in IPB heavy clean up requirements in support of cleansing product structures (IPB’s).

1.2 Background

The AF 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 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 AF vision of PLM as a single source of product data, including M-BOM, across the AF 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. The AF has initiated data cleansing pilots to establish M-BOM’s for PLM Transformation initiative. These pilots have aided the AF in establishing security and Scientific/Technical Information (STINFO) policies and procedures for capturing AF technical data IAW AF regulations. Additionally, data cleansing process and procedures have been established under the previous USAF IPB cleansing projects.

The contractor shall provide engineering/technical services for the efforts described within Section 2.0 and 3.0 below

The contractor shall 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. The contractor shall work in conjunction with TCMs and other personnel representing the CEA for the assigned system/data. The contractor shall utilize heavy cleansing developed procedures and tools to aid the AF (Tinker AFB) in IPB heavy clean up requirements in support of cleansing Tinker AFB IPB’s. The contractor shall identify verified and validated errors and recommended AFTO 252 changes, AFTO 22, and AF Form 3925 & AF Form 3927 when engineering drawings impacted by cleansing utilizing established IPB cleansing processes, tools and past IPB cleansing projects technical document folders/binders processes for IPB heavy clean up requirements in support of cleansing Tinker AFB IPB’s. These folders/binders will consist of a PCMS heavy cleansing tool clean up file (7 - PCMS Heavy Cleanup Tool User Manual), JEDMICS information clean up file, AFMC form 252, AFTO 22, AF Form 3925 & 3927 action recommendations. The contractor shall assist the AF TCM’s to clearly define recommended AFTO 252 changes with AFTO 22 documentation and AF Form 3925 & AF Form 3927 when engineering drawings impacted by IPB cleansing activities. Contractor shall track and report by cleansing contractor representative name, monthly number of IPB’s cleansed by IPB number, number of records reviewed for each IPB, number of records cleansed by IPB, minutes to review each record by IPB, minutes to cleanse each record by IPB, total IPB cleansing errors by type and rate, engineering drawing proprietary/missing error rate by IPB/drawing number, actual records/IPB cleansed per month compared to planned records/IPB per month, IPB & drawing AFTO22, AFTO252, AF Form 3925 and AF Form 3927 working and submitted per month by IPB number and drawing number and number of IPB validation packages in work per month, validation packages submitted to Tinker AFB per month and total validation packages worked and submitted to Tinker AFB over the contract period of performance. Contractor shall provide engineering services to research, verify, and assist with implementation and provide technical deliverables identified as Technical Report -Study/Service. CDRL’s A003, A004, A006, A010, A012 & A013.

2.1.2 Data cleanup.

The contractor shall research D043, G005M, D200, G004L, Haystack® and other cataloging systems (Acquisition Streamlining and Standardization Information System “ASSIST” will be utilized for reference only), JEDMICS Full Text Search (FTS) search the JEDMICS production system to ensure currency when using the FTS engine to ensure the accuracy of part number(s) for the assembly referred to in the IPB. Contractor shall document/identify corrections as necessary to the source system and also document these required changes in tools for tracking requirements.

The contractor shall work with the CEA, the Original Equipment Manufacturer (OEM) and TCM to identify corrective actions. Additionally, the contractor shall be required to access both AF and OEM tools to assist in the analysis. As corrections are identified, the contractor shall update part information using tools and processes provided by the AF. 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. Attachment”2” lists examples of errors that the AF expects to be encountered during IPB cleansing activities. Attachment “5” Acceptance Group Categories contains list of error category to be utilized to report errors. “8” lists business rules implemented over cleansing pilots that shall be followed. New business rules will be documented during period of performance clarifying processes that shall be implemented. Any tool contractor utilizes outside USAF issued/identified that defines IPB cleansing business rules will be documented and provided to USAF. The contractor shall update this list of errors and time to correct as additional types of errors are identified. Contractor may encounter proprietary data/drawings and shall require assistance from CEA for resolution.

When reviewing a TO, the contractor shall verify linkages to the lower level T.O.s identified directly in parent T.O. (the T.O. being reviewed) or when a lower level T.O. is indicated through symbology in the parent T.O. If the part number in the T.O. being reviewed, and the part number in the lower level T.O.do not match, and the lower level T.O. is part of the contracted cleansing effort, the contractor shall investigate and recommend a resolution to the error. When the lower level T.O. is not available the contractor will report that the linkage could not be verified and recommend investigation by PLM program office (OC-ALC/ENSN, COR). This type of error may require reporting under a new error code not currently part of the error codes listed in attachment 6 (IPB Standard Common Error Codes). The contractor shall produce and provide a single list of all IPB T.O.s cleansed and the T.O.s corresponding top-level part number(s) (Identify this to USAF as TO Number to Top-Level Part Number Cross Reference) Contractor shall also have knowledge and utilized Teamcenter Enterprise 2007, be able to configure parts, has conducted data cleansing activities utilizing Teamcenter Enterprise 2007, BOM entries and modify parts utilizing Teamcenter Enterprise 2007 (or other like COTS product) in order to support USAF equipment specialists cleansing BOM’s (5 USAF equipment specialists). Contractor shall also be required to provide USAF troops at Tinker over the shoulder Teamcenter Enterprise 2007(or other COTS like product) training and conference room type training as USAF equipment specialists (8 troops) update requirements. Product Lifecycle Management System (PLMS) Teamcenter (or other COTS like product) requirement will require close working relationship with USAF PLMS program office at Gunter AFB.

CDRL ‘s A003, A004, A006, A010, A012 & A013

2.1.3 Estimated Effort.

The commodities IPBs, ranging from 150 records an IPB up to 1200 records an IPB. See Attachment ‘4” for commodities and weapon system IPB Listing (IPB’s are listed in order of importance and this is a living document to be updated at contract kick off meeting). Weapon System IPB’s range from 4000 to 8000 records an IPB. Estimated error rate based upon past IPB cleansing projects is 47% and estimated time to review IPB errors is 4 minutes and estimated time to correct per IPB error is 4 minutes (documenting AFTO 252, AFTO 22 actions and AF Form 3925 & AF Form 3927 when engineering drawings impacted by IPB cleansing activities) these 4 minutes estimates were based upon past USAF cleansing projects.

a) IPB’s records cleansed breakdown is as follows

- Commodities (IPB’s) records 955,000

- Weapon System (IPB’s) records 120,000 to align with commodities IPB’s that are being cleansed. Example: Cleansing B1 related commodity IPB’s will require cleansing B1 weapon system level IPB.

b) Bill of Material (BOM) F101, F110, F108, F118, TF39, F100, T56, J85, TF33 and TF34 engine updated in Product Lifecycle Management System (PLMS) data base, assisting USAF in document business rules, drafting Tinker AFB PLMS Roadmap and loading BOM structure utilizing cots tool identified as Teamcenter Enterprise 2007. Contractor (2 contractor representatives) shall have knowledge and utilized Teamcenter Enterprise 2007, be able to configure parts, has conducted data cleansing activities, BOM entries and modify parts. Contractor shall also be required to provide USAF engines equipment specialists and engineers at Tinker over the shoulder Teamcenter Enterprise 2007 (or other COTS like product) training as engines PLMS data cleansing/updating requirements are implemented, roughly 6 to 10 equipment specialists and engineers over length of contract. This will require close working relationship with USAF PLMS program office at Gunter AFB. Gunter AFB PLMS PMO office will also provide contractor (2 contractor representatives working PLMS cleansing requirements) PLMS Engines Teamcenter Enterprise 2007 (or other COTS like product) specific training in order to support PLMS engines cleansing requirements. As contractor cleansing of one type, model series in PLMS is completed, it will be handed off to the equipment specialist to maintain and the contractor will move on to the next engine for PLMS cleansing requirements.

· 185,000 records (F101, F110, F118, TF33, F107, TF34, F108, TF39, T56, J85 and F100 engines)

Note: Rough Order of total records information provide in section 2.1.3 (Estimated Effort).

a) 1,260,000 records to cleanse

b) Of number of records listed in “a” above, 100,800 records could be defined as no data available for contractor to provide recommendations after researching. This would align with attachment 5 (acceptance group categories), Group IV statement.

Record: A collection of one or more fields relating to a specific piece of information.

· Collection of data elements describing or identifying one or more units treated as one logical entity.

· Product data is defined as all data that specifies one or more aspects of a product throughout its life cycle.

2.1.4 Corrections to source data.

The contractor shall submit recommended changes/corrections to IPB part data utilizing established processes. See Attachment “3” for detailed process flow. During the course of IPB cleansing activities, the contractor shall 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 PCMS heavy clean up file, JEDMICS information clean up file, PCMS heavy clean up manual/tool file, AFMC form 252, AFTO 22, AF Form 3925 & 3927 action recommendations. Contractor shall submit Folder/binders to the assigned Tinker AFB TCM for validation and AFMC Form 252, AFTO 22, AF Form 3925 and 3927 incorporation. CDRL’s A003, A004, A006, A010, A012 & A013.

2.1.5 Use of AF, DOD and commercial tools and databases.

The AF will provide the contractor access to information sources (JEDMICS, PDM Gateway, PCMS, Data Accuracy and Review Tool (DART) to be used to identify and correct errors in technical data. The contractor shall 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. Paragraph 2.1.8 of this document identifies tracking requirements.

2.1.6 Data Validation/Approval.

The contractor shall work with the CEA at both Global Logistic Supply Chain Center and AF Materiel Command Air Logistics Center PLM focal points. The contractor shall communicate corrective actions identified and validated to the assigned TCM for approval and concurrence. The contractor shall also 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. The contractor shall use current processes and implement new processes to prevent redundant research on common parts.

2.1.7 Quality Assurance.

The contractor shall 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 95% 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 Contracting Officer Representative.

2.1.8 Metrics and Reporting.

The contractor shall provide a monthly status report. This report shall include detail errors corrected by attribute category, amount of technical orders processed, PLMS deficiencies (deficiency reports if warranted). No more than 2 errors per month shall be committed while validating/verifying technical data. The contractor shall compile initial tech order statistics and initial complexity factors utilizing past USAF PLM IPB cleansing statistics and complexity factor process deliverables. The contractor shall compile types of tech orders processed, i.e. PDF Files, SGML. The contractor shall provide tracking information on IPB validation data packages processed to equipment specialists (E.S.) after cleansing. Tracking information will include E.S. signature acceptance of validation package, IPB number, E.S. name, phone number, E.S. code, email address and office symbol, AFTO 252 & AFTO 22 tracking number, AF Form 3925 and 3927 actions tracking information if implemented for the IPB cleansing action, identification of missing engineering drawing and date. The contractor shall deliver data within 95% on time in compliance with the established burn down plan. The contractor shall 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 and 3927 actions and other USAF representatives in cleansing activities and any issues associated with meeting contractual requirements as outlined in; CDRL’s A003, A004, A005, A006, A010, A012 & A013

2.1.9 Customer Satisfaction

The contractor shall ensure that job performance meets government standards and criteria during contracting period. The contractor shall have no more than three valid customer complaints per month per Contractor Manpower Equivalent (CME). Reference Customer Complaint Record Template, Feb 11 (OC-ALC/ENSN)

2.1.9.1 CUSTOMER COMPLAINT PROCEDURES:

When the contractor’s performance becomes unsatisfactory, the commodities, PLM IPB Data Cleansing Objects Customers shall either contact the COR with the relevant information, or provide the COR an email with relevant information. Reference Customer Complaint Record Template, Feb 11 (OC-ALC/ENSN)

a. The COR will review the information and validate the complaint.

b. When validated, the COR will notify the Contract Administrator and request corrective action. The customer complaint will be used to document/seek resolutions to problems and serve as evidence of unsatisfactory service.

2.2 Project Management/Reports.

The contractor shall document task, schedule, risk management and expenditure plans in Management Plan, Master Schedule, Cost/Schedule Status report, Contractor 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 and submit documents to the government technical program manager within 45 calendar days after contract award. The established documents shall be considered a living document and will routinely be updated to reflect the current status of program activities. Documents shall be completed on time and updated to reflect changes as they occur. Completed on time and updated to reflect changes as they occur 99% of the time. Comments to these documents from the Government shall be incorporated, and the updated document shall be resubmitted to the Government for approval within 15 calendar days of receipt of Government comments. CDRL’s A005, A006, A007, A008, A009 & A011.

2.3 Weekly work plan.

Each week the contractor shall conduct an analysis of the list of cleansing activities to be corrected and prepare/update a work plan. The contractor shall provide a copy of the weekly work plan upon the request of the COR. The contractor shall maintain and refine the work plan as needed for cleaning configuration data. The contractor shall access other ALC’s data bases, data cleansing Community of Practice (CoP) sites or any site that may replace them as required.

2.4 Support Meetings/Conferences.

The contractor shall provide written communications and briefings to ALCs, and other government customers. The contractor shall attend meetings and conferences to support data cleansing efforts and strategies. The contractor shall schedule weekly meetings with applicable Equipment Specialist, Engineers and Logistic Managers to resolve any issues related to IPB, data cleansing efforts. Contractor shall conduct quarterly program management reviews with USAF program manager. Due to the frequency of weekly required meetings, contractor shall locate within 10 mile radius of Tinker AFB.

The contractor will be required to prepare and submit documents associated with meetings and program management reviews conducted or attended. Refer to the following CDRLs for document requirements (CDRL A001- Meeting agenda and A002 – Meeting Minutes). Weekly meetings between contractor, E.S. and engineer for each weapon system and/or commodities will be required to work each IPB issue “252 actions, AFTO 22, AF Form 3925 and 3927, drawings, etc.). AF has identified that the contractor must be within a 10 mile radius of Tinker AFB. CDRL’s A001 & A002.

2.5 Final Summary Report of Cleaning Activities and Effort.

Contractor shall submit final report detailing the types and occurrence rates of errors encountered during this effort, number of occurrences of each error type, number of IPB’s and drawing corrected (to include drawing and T.O. numbers), 252 actions, AFTO 22 actions, AF Form 3925 and AF Form 3927 technical packages processed (folder/binders) and the average time it took to correct each technical data. CDRL A003 – Final report.

DELIVERY SCHEDULE AND PERIOD OF PERFORMANCE

3.0 Period of Performance

The initial period of performance for the commodities IPB’s cleansing, verified and validated documented errors and recommended AFTO 252 changes, AFTO 22, and AF Form 3925 & AF Form 3927 when engineering drawings impacted by cleansing utilizing established IPB cleansing processes is 12 months.

A004 A006 A010 A012 A013

Monthly on 15th of month, included in Monthly status report

A004 A006 A010 A012 A013 Monthly on 15th of month, included in Monthly status report

A003 A004 A006 A010 A012 A013 Monthly on 15th of month, included in Monthly status report

A004 A006 A010 A012 A013 Monthly on 15th of month, included in Monthly status report

A004 A005 A006 A010 A012 A013 Monthly on 15th of month, included in Monthly status report

3 valid documented

A006 A007 A008 A009 A011 45 days after contract awarded. Living documents updated as required

The contractor shall provide, for Government review, all agendas, meeting minutes, and handouts for each proposed review and working group meeting. Microsoft Professional Applications Electronically delivered (email)

A001

5 Business Days. The Contractor shall plan and support reviews to allow the Government to examine the Contractor's chosen approach and establish the requirements baseline.

The contractor shall provide, for Government review, all agendas, meeting minutes, and handouts for each proposed review and working group meeting. Microsoft Professional Applications Electronically delivered (email)

A002

5 Business days. The Contractor shall plan and support reviews to allow the Government to examine the Contractor's chosen approach and establish the requirements baseline, and document action items and each meetings notes.

Contractor shall provide detail report with all deliverables throughout contract (included on external hard drive), recommendations, and lessons learned and tracking information.

A003

30 days before contract ends

A004 A005 A006 A010 A012 A013 45 days after contract awarded. Living documents updated as required

A006 A007 A008 A009

45 days after contract awarded. Living documents updated as required

Reviews/Technical Interchange Meetings Program Management Reviews A001 A002 A004 A010 A012 A013

As Required & 45 days after contract awarded. Living documents updated as required

Note: Should 15th of the month fall on Saturday or Sunday, deliverables shall be delivered to AF on the following Monday. Should Monday be a holiday, deliverables shall be delivered to AF on Tuesday.

3.2 Program Management

Contractor shall provide progress of the previous month against the errors corrected and data capture for month being reported status of contract milestones. Resource expenditures for the project, Metrics on: number of errors corrected, technical data packages (folders/binders), 252 actions, AFTO 22, AF Form 3925 and 3927 actions, recommended drawing change request, schedule and rate to completion, and any issues associated with meeting contractual requirements. Standard common Error Code in Attachment “6” shall be utilized for monthly status report requirements. Contractor shall also track and report by cleansing contractor representative name, monthly number of IPB’s cleansed by IPB number, number of records reviewed for each IPB, number of records cleansed by IPB, minutes to review each record by IPB, minutes to cleanse each record by IPB, total IPB cleansing errors by type and rate, engineering drawing proprietary/missing error rate by IPB/drawing number, actual records/IPB cleansed per month compared to planned records/IPB per month, IPB & drawing AFTO22, AFTO252, AF Form 3925 and AF Form 3927 working and submitted per month by IPB number and drawing number and number of IPB validation packages in work per month, validation packages submitted to USAF per month and total validation packages worked and submitted to AF over contract period of performance. This report shall be delivered in a Microsoft Office document, 45 days after contract awarded CDRL’s A003, A004, A005, A006, A010, A012 & A013

3.2.1 Management Plan

Management Plan, Master Schedule, Cost/Schedule Status Report, Contractor Risk Management Plan and Risk Management Report CDRL Sequence Number A005, A006, A007, A008 & A009 Management Plan, Master Schedule, Cost/Schedule Status report, Contractor Risk Management Plan and Risk Management Report, 45 days after contract awarded.

These plan’s shall contain:

1) Major Milestones

2) Expected Resource expenditures for the project

3) Issues/Concerns/Risk and associated recommendations

4) These reports shall be delivered in Microsoft Office Professional Documents

3.2.2 Program Status Reviews/Technical Interchange Meetings

The contractor shall attend regular (monthly) program status reviews, weekly equipment specialists (E.S.) and engineering reviews, as approved by the COR. The purpose of these meetings shall be to brief the progress of each assigned task, and to solicit input and concurrence of work performed. The contractor shall generate presentation materials as required to aid in the discussion of technical issues and shall support Technical Interchange Meetings/Reviews. The contractor shall provide conference agendas, meeting minutes, and track Action Items associated with the aforementioned meetings/reviews. This report shall be delivered in a Microsoft Office document, Monthly & 45 days after contract awarded CDRL’s A001, A002, A004, A010, and A012 & A013

3.2.3 Expertise/Professional Services

In support of this Product Data Cleansing, the contractor shall possess working knowledge of technical cleansing solutions and processes in support of these requirements. The contractor shall possess comprehensive skills on the following:

· Reading and interpreting technical drawings/models (10 years experience within the last 15 years)

· Reading and interpreting milspec and/or commercial IPBs

· Experience as an equipment specialist, engineer, engineering technician, or other technical areas working on AF or other military data objects/elements.

· 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)

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

· Familiar with and interpreting information from AF developed cleansing tools

· Familiar with AF developed data cleansing processes

· Experience with Microsoft Products

· Experience with Teamcenter Enterprise 2007 (or other COTS like product)

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

In support of the data cleansing management task, the contractor shall possess working knowledge of transitional program management tools and processes.

Documented deliverables shall be delivered in accordance with this PWS, unless otherwise specified by the COR.

3.3 Government Inspection and Acceptance of Deliverables

The COR will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Contractor will be notified in writing by the Government Program Manager of the specific reasons why the deliverable was rejected. The Contractor shall have 7 calendar days to correct the rejected deliverable and resubmit to the Government Program Manager for re-inspection. If no comments are provided within 7 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the Government.

3.4 Configuration Management.

The Contractor shall implement a 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) Data Objects Cleansing requirements processes, 45 days after contract awarded, no more than 2 errors are identified per month. Living documents updated as required (DI-CMAN-80858B, CDRL A011, Contractors Configuration Management Plan).

SPECIAL CONSIDERATIONS

4.0 Security

4.0.1 Contractor personnel shall not release or remove system documentation, data, or reports generated by or through use of Government systems. All requests for information shall be forwarded to OC-ALC/ENSN.

4.0.2 The efforts required for this task are expected to be UNCLASSIFIED and should not require the contract personnel to obtain a security clearance. However, if the tasking performance requires access to classified data, a security clearance of SECRET will be required for all personnel having access to the classified data and a DD Form 254 will be submitted. Only United States persons, as defined by 22CFR Part 120.15 are eligible to perform on this contract. Due to the sensitive nature of the technology involved in this program, the Contractor agrees that foreign persons, as defined by 22 CFR Part 120.16 are not eligible to work on this program.

4.0.3 OC-ALC/ENSN or the COR will assist contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to Government facilities. Contractor employees performing services under this order will be controlled, directed, and supervised at all times by management personnel of the contractor. Contractor management shall ensure that employees properly comply with the performance work standards outlined in the statement of work. Contractor employees shall perform their duties independent of, and without the supervision of, any Government official. The tasks, duties, and responsibilities set forth in the task order may not be interpreted or implemented in any manner that results in any contractor employee creating or modifying Federal policy, obligating the appropriated funds of the United States Government, overseeing the work of Federal employees, providing direct personal services to any Federal employee, or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government will control access to the facility and will perform the inspection and acceptance of the completed work.

4.0.4 The contractor shall not divulge any information regarding files, data, processing activities/functions, user ID's, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct. Contractors requiring access to Government Automated Information Systems (AIS) shall have background investigations and security awareness training completed, after task order award but prior to AIS access. When the period of performance is complete or and contractor personnel leave work on this project they will have 5 working days to terminate all their network user account and to return all access cards and base identification badges to base security and notify the COR and AF contracting official.

4.0.5 The following sections describes the approach contractor shall implement to assure the Product Data Cleansing source documents derived from distribution “E” technical orders will be maintained with the required level of security IAW Defense Security Systems guidelines.

4.0.5.1 Controls

a) All source documents shall be handled according to the “E” distribution instructions identified in paragraph 4.0.5.2, subparagraph (i) below.

b) The dedicated computer used for the program will display a Distribution E Statement upon logon.

c) Contractor shall have an active Defense Logistics Information System (DLIS) Certificate authorizing receipt of unclassified technical data disclosing military critical technology.

d) Approved contractor personnel will use Common Access Card (CAC) for access to all government computers, servers and AF Portal/AFKN site where Tinker Managed weapon system source documents reside; contractor will identify to USAF representatives approved for access.

e) Contractor will utilize 128 BIT encrypted dedicated computer with password protection, restricted access to retire/store Tinker Managed weapon system source data.

f) Contractor will establish a dedicated and restricted access computer for receipt and storage of the Tinker Managed weapon system source documents; access to this dedicated drive is authorized to the contractor network security manager and contractor personnel working the Tinker Managed weapon system as highlighted in 1d above. The computer will be located in the controlled access IT server room at contractor facility.

g) All back up CDs/DVDs will be maintained in contractor secure backup file safe and will be returned to the Government Contracting Activity (GCA) or destroyed IAW instructions from the Cognizant Security Agency (CSA).

h) At the conclusion of the contract the dedicated hard drive will be wiped in order to destroy the Tinker Managed weapon system data per COTR/National Industrial Security Program direction.

i) Once all Tinker Managed weapon system data has been distributed/destroyed as required, contractor will schedule a day and time with local DCMA representative to assure the deletion of the Tinker Managed weapon system data on the dedicated computer.

j) Contractor will obtain a signed letter from DCMA attesting to the destruction of Tinker Managed weapon system data on the dedicated computer. This official letter shall be processed to contracting official and COR.

4.0.5.2 Process

a) The Tinker Managed commodities, WR-ALC/PCMS or PLM office COR representatives will place Non-11N source documents (Technical Orders, Manuals, etc.) as well as stripped data from the 11N source documents on the external hard drive or WR-ALC/PCMS Cop Clean up files for cleansing.

b) Approved contractor personnel shall use a USAF CAC to gain entry to COP or provided media with data and download source documents to the restricted access computer located at the contractor’s facility.

c) Approved contractor personnel shall strip relevant data from the source documents and export it into data base tools application which is installed on the contractors restricted access computer.

d) Should reports be generated from contractor COTS application, analysis shall be provided to PLM office by email or external hard drive containing data for AF cognizant engineering authority (CEA).

e) Approved contractor personnel working on site at Tinker AFB OK, shall process contractors commercial off the shelf (COTS) application reports from email or external hard drive and store on AF networked computers.

f) Reports generated from the approved contractor personnel working at Tinker AFB shall be uploaded to PLM focal point by email or processed back onto external hard drive for CEA.

g) Approved contractor personnel working at contractor’s facility will be notified by email from PLM focal point or WR-ALC PCMS CoP or external hard drive to the dedicated computer using same procedures as identified in subparagraph b above.

h) Updated reports generated from the contractors COTS application shall be uploaded to the PLM focal point or external hard drive containing data will be the process. Note: This is iterative process that will require updates throughout the contract POP.

i) DISTRIBUTION STATEMENT - E - Distribution authorized to DoD Components only, (12 November 2009). Other requests for this document shall be referred to appropriate weapon system and commodity managers at Tinker AFB. If unknown contact COR identfied on page 23 of this document (CONTRACTING OFFICER REPRESATIVE/CONTACTS).

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act

(Title 22, U.S.C. 2751 et seq.) or Executive Order 12470. Violation of these export control laws is subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

HANDLING AND DESTRUCTION NOTICE – the contractor shall Handle in compliance with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

4.1 Access to Facilities and Property

Access to Government facilities is limited. Therefore, the contractor shall coordinate required access/usage times and dates through COR at least fifteen working days prior to the need date. Control of the facilities shall remain with the Government. Government COR working hrs of operation is from 0715 hrs to 1600 hrs, Monday thru Friday accept for all official government holidays. Government representatives will not be available and government facilities will be closed for operation on Official government holidays (listed below)

New Year’s Day

Birthday of Martin Luther King, Jr.

Washington’s Birthday

Memorial Day

Independence Day

Labor Day

Columbus Day

Veterans Day

Thanksgiving Day

Christmas Day

4.3 Data Rights

All equipment or software acquired by the contractor, developed by the contractor, or licensed to facilitate processes or meet production requirements will transfer to the Government at contract termination or completion.

All software developed for this project will become the property of the Government; therefore, source code for all systems, scripts, tools, etc., developed for this contract effort must be provided unencumbered at contract completion or within 30 calendar days after receipt of request from the Government’s technical program manager. All development efforts must be approved by the Government’s technical program manager prior to start of development.)

All custom developed software shall be properly documented using industry standard techniques. All business rules utilized in any contractor tool utilized for PLM IPB cleansing shall be documented and provided to the USAF for approval of use.

All documentation necessary to operate, maintain, enhance, utilize, or provide training on any process or system component used in the performance of this contract must be provided to the Government within 30 calendar days after receipt of request.

Any software owned by the contractor and used in support of this effort will remain the property of the contractor and will not become the property of the Government.

No briefings or marketing material concerning this project will be created, delivered, or distributed by the contractor without explicit permission from the Contracting officer.

4.4 Nondisclosure Requirements

Contractor personnel will be exposed to information covered under the Privacy Act of 1974, and shall comply with all applicable safeguarding and handling requirements associated with Privacy Act information. Contractor personnel shall be required to access or come into contact with proprietary information or sensitive Government information, including financial account records or source sensitive information as necessary. Contractor personnel shall not use such information for any purpose other than the performance of this order. The Contractor shall not release or remove system documentation, data, or reports generated by or through use of any government systems. All requests for information shall be forwarded to the technical program manager or contracting officer.

The following shall apply to Contractor personnel performing in support of requirements:

Contract personnel shall act as trusted agents. The performance chain for contract personnel assigned to support requirements will not fall under their company’s Business Development or Proposal Management organizational structures.

Contractor personnel assigned to support requirements shall NOT divulge any competition sensitive Government information that they have access to as a result of their positions. Furthermore, contractor personnel assigned to support requirements shall NOT work as representatives for their company for other contract solicitations issued in association with this contract. Contractor personnel including subcontractors shall not engage in any activities that could be deemed a conflict of interest during the period of performance of this contract. Non-Disclosure Agreement required for each contractor working this project.

4.5 Government Furnished Property and Services

4.5.1. Government Furnished Property (GFP) is required in the performance of this contract in accordance with FAR Parts 45 and 52.245 plus supplements. See appendix D for Laptop’s. docking stations, screens and printers will be purchased by the USAF and become the proprietary of the USAF in support of this effort. This equipment will be required to be loaded onto USAF & contractors hardware tracking and management account.

4.5.2. Government Furnished Services are applicable to this requirement. Virtual Private Network (VPN) software will be a requirement and installed on USAF purchased computers by Tinker AFB admin personnel in order to gain access to Tinker Network. IPB heavy cleansing software tool will be provided to contractor and must be installed by USAF administrators also.

4.5.2.1. The Government will provide documented processes (attachments to this PWS 2, 3, 4, 5, 6, 7 & 8).

4.5.2.2. Government provided system access will include but are not limited to D043, D200, D220, G005M, JEDICS, Haystack®, JCALS, CTOR, CITOMS, TOVL, IDM and IETM databases, PCMS, DART, AVCOM, AFTOC, FLIS, TAS, FEMS, PDMSS, DMAPS, ETIMS, GACP, DLDDS, PDM-Gateway, ETIMS, IMPRESA, JEDMICS Plotter and the CAD/CAM Repository.