Attachment1PWS.pdf

PERFORMANCE WORK

STATEMENT (PWS)

for

Data Mining, Data Loading, and Data Maintenance th

Supply Chain Management Squadron

Air Force

Diminishing Manufacturing Sources

And Material Shortages (DMSMS) Management

Program

RFP: FA8109-20-R-0002

PREPARATION DATE: July 2019

Prepared by:

429 SCMS

Tinker AFB, Oklahoma

3001 Staff Drive

TINKER AFB OK 73145

i

TABLE OF CONTENTS

SECTION TITLE

TABLE OF CONTENTS ................................................................................................... i

1 SECTION I –DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.0 Purpose

1.1 Scope

1.2 Reference Documents

1.3 Contractor Requirements

1.3.1 Technical Data Identification

1.3.2 Loading of Line Items

1.3.3 Updating Line Items

1.3.4 Tool Software and Access Support

1.3.5 Tool Database Training

1.3.6 Tool Data Export to the, Applications, Programs and Indentures (API)

1.3.7 Source Document Loading Accuracy

1.3.8 Tool Parts Component Status Verification and Tracking

1.3.9 DMSMS Case Tracking Support………………………………………………6

1.3.10 Custom Reports

1.3.11 DMSMS Process Coordination

1.3.12 Program Management

1.3.13 Expertise/Professional Services

1.3.14 Monthly Status Reports (MSR)

1.3.15 Kick-off Meeting

1.3.16 Technical Interchange Meeting (TIM)

1.3.17 Annual Program Review

1.3.18 Meeting Agenda

1.3.19 Meeting Minutes

1.3.20 Contractor Manpower Reporting

1.4 Government Inspection and Acceptance of Deliverables

1.5 Delivery Schedule and Period of Performance

1.5.1 Delivery Schedule

1.6 Special Consideration

1.7 Security

1.7.1 Government Systems

1.7.2 Security Clearance

1.7.3 Base/Area Badges

1.7.4 Automated Information Systems

1.8 Government Program and Contract Management

1.8.1 Government DMSMS Program Management

1.8.2 Government Project Managers

1.8.3 Government Contract Management

1.9 Safety Requirements

1.9.1 General Safety Requirements

ii

1.9.1.1 Safety Provisions

1.9.1.2 Accident Investigation

1.9.1.3 Applicable Regulations and Air Force Instructions

1.9.2 Emergency Procedures

1.9.3 Voluntary Protection Program (VPP)

1.10 Travel Requirements

1.10.1 Travel Anticipated……………………………………………………………….13

1.10.2 Travel – Over & Above…………………………………………………………….13

1.10.3 Travel Pre-Approval……………………………………………………………..13

1.10.4 Travel Expenses…………………………………………………………………14

1.10.5 Post-Trip Documentation……………………………………………………….14

1.10.6 Post-Trip Report………………………………………………………………

1.10.7 Passport and Visa Requirements……………………………………………...14

1.11 Contracting Officer Representative/Contacts

1.12 Continuation of Essential Services

2 SECTION II - SERVICE SUMMARY

3 SECTION III - GOVERNMENT FURNISHED PROPERTY/SERVICES

3.0 Security Police

3.1 Fire and Emergency Services

3.2 Emergency Medical Services

3.3 Special Access to Facilities and Property

3.4 Government Furnished Equipment, Materials, and Software

3.5 Location/Office Space

APPENDIX A: Tool Requirements Matrix APPENDIX B: Government Owned Part Attributes APPENDIX C: Contractor Supplied Part Data APPENDIX D: Component/System Data APPENDIX E: Acronyms APPENDIX F: Definitions APPENDIX G: Contractor Manpower Reporting

1 SECTION I –DESCRIPTION OF SERVICES/GENERAL INFORMATION

1.0 Purpose

The purpose of this effort is to provide DMSMS support for Air Force (AF) users to proactively reduce mission capability impacts. Additionally, this effort supports users outside the AF. The AF must continue to evolve and proactively improve weapon system acquisitions, logistics support and sustainability. The AF users must be able to see the availability and commonality of parts across multiple weapon system platforms which requires linking of the Bill of Material (BOM) data in order to run necessary queries and reports from a single access point. This effort will help assure all required parts and materials to support AF managed weapon systems are available within acceptable production lead times. In addition, the effort will reduce the overall cost of ownership of the weapon systems by, (1) facilitating economical DMSMS resolution costs, (2) reducing the number of reactive solutions, (3) minimizing delays in organic depot-level repair as well as contractor repair, and (4) improving weapon system availability.

The contractor shall provide services for the management of the AF owned parts data.

The contractor shall furnish an Information Technology (IT) capability that can perform the requirements of this PWS. The contractor’s IT capability, combined with the AF owned parts data, shall hereafter be called the “Tool”.

1.1 Scope

The contractor shall identify and load new weapon systems technical data managed by the AF into the Tool to perform the requirements listed in this PWS. In addition, all government-owned part attribute data (APPENDIX B) shall be imported to the Tool. All government-owned part attribute data and contractor supplied part attribute data (APPENDIX C) shall be appropriately linked in order to perform the requirements called out in this PWS. All imported data as well as all new technical data loaded into the Tool shall be maintained as applicable source documents change.

As referenced in this document, weapon systems refers to those Line Replaceable Units (LRUs); test systems and associated LRUs; and simulators and associated LRUs.

The respective List of Applicable Publications (LOAPs) for each weapon system can be used as a baseline for determining the associated weapon system LRUs, test equipment LRUs, and simulator LRUs. The Tool structure shall mirror the structure of the respective systems (i.e. weapon systems), to include all applicable and obtainable technical orders (T.O.s), manuals, and associated drawings. Test equipment shall be aligned with the associated system. The contractor shall be responsible for maintaining proper system structure and part configuration data. The Tool users shall not be allowed to add, delete, or otherwise modify any structure or part configuration data. The Tool shall status and display all component parts called out in the T.O.s, manuals and associated drawings.

1.2 Reference Documents

The following documents are considered as reference manuals for the purpose of interpreting the requirements of this PWS, but are not contractual requirements:

AFMCI 63-1201, Implementing Operational Safety, Suitability, and Effectiveness (OSS&E) and Life Cycle Systems Engineering T.O. 00-5-1, AF Technical Order System, Chapter 4 AFMCI20-105 Diminishing Manufacturing Sources and Material Shortages (DMSMS) SD-22, DMSMS Guide Book AFI 61-201, Management of Scientific and Technical Information

The contractor shall obtain the forms and publications expressly required to perform the work in this contract via the internet at http://www.e-publishing.af.mil/. In the event that a form or publication is not available, the Contracting Officer Representative (COR) will provide the form, instruction, or publication to the contractor upon written request (e-mail is acceptable) by the contractor. In the event that laws, regulations, T.O., AF Instructions, and AF Materiel Command Instructions change during the term of this contract, the contractor shall reference the latest version for interpretations of this PWS.

1.3 Contractor Requirements

At the beginning of this effort, the contractor will be provided the AF owned indentured parts data in a flat file format on Compact Disks (CDs). Flat files will contain approximately 30.1 million line items populated with government-owned part attribute data listed in APPENDIX B. Contractor shall import all government-owned part attribute data into their Tool and link as required by this PWS.

In addition to the government-owned part attribute data, the contractor shall populate the same 30.1 million line items with the contractor supplied part attribute data listed in APPENDIX C. Contractor shall have all part attribute data populated, appropriately linked and made available for use to all AF users after award and issuance of a task/delivery order, within 90 days of receipt of App B flat file from the government, contractor tool must be fully functional.

All government-owned part attribute data provided at the beginning of this effort for input and processing using the DMSMS Tool shall remain the property of the government and shall be returned at the end of the contract in accordance with CDRL A005 at no additional cost. All new part attribute data referenced in APPENDIX B input into the Tool during this contract shall be the property of the government and shall be delivered in accordance with CDRL A005 at no additional cost. All case work performed by Analysis and Resolution contract located within the Tool shall be the property of the government and shall be delivered in accordance with CDRL A005 at no additional cost. The government shall own and have unlimited rights to all the data listed in APPENDIX B and case work during and at the end of the contract

The contractor shall provide the necessary capabilities required to support the 448 Supply Chain Management Wing (SCMW) obsolescence management initiatives as described in this PWS. The contractor’s Tool shall meet all requirements of this PWS at time of award. The contractor shall also provide engineering, technical and program support services for the effort. The requirements detailed below will be broken out by specific AF requirements, as applicable.

This requirement is considered Sustainment and does not allow for development or modernization of a contractor’s IT capability. This requirement does not allow for the government purchase of software modifications or software enhancements. This requirement does not allow for the government purchase of computer hardware. At time of award, the contractor shall have a complete IT capability which has the ability to perform the requirements as stated in this PWS.

1.3.1 Technical Data Identification

The contractor shall perform technical data identification on the weapon systems identified and prioritized by the government program manager. In order for the contractor to obtain access to Air Force technical orders a DD Form 2345 must be completed. The contractor shall submit an approved DD Form 2345 in accordance with AF guidance T.O. 00-5-1 and AFI 61-201. AFSC will facilitate/grant access for the contractor to obtain technical data and other documents as needed and approved by the AFSC Project Managers in the performance of this effort. A listing of the information systems required for contractor access is provided in APPENDIX D - Component/System Data. Contractor is responsible for accessing new data systems and the following list is subject to change The contractor shall analyze the AF furnished weapon system technical data documentation and all approved T.O. change information to determine the indentured assembly tree structure and associated BOM information to be incorporated into the Tool to reflect the current weapon system configuration.

1.3.2 Loading of Line Items

The contractor shall perform loading of weapon system structure, including test and simulator equipment. The contractor shall include all piece parts in the latest configuration. The contractor shall use government-managed Technical Orders (T.O.), drawings and flat files as the primary source for loading new data into the tool. The contractor shall assist the government in identifying and prioritizing specific data for loading into the Tool, determine the actual distribution of line items between program areas, and identify any data for priority loading over the course of the contract. The data loaded shall reflect the full hierarchal configuration of the technical data and consist of, but not limited to, non-electronic components (i.e. hardware, mechanical, structural, optical, organic, software etc.) as well as electronic components (i.e. integrated circuits, discretes, hybrids, passives, radio frequency, crystals, oscillators, electronic switches, tubes, transformers, solid state relays, resistor networks, custom devices, etc.) and COTS equipment (i.e. oscilloscopes, power supplies, spectrum analyzers, etc). Data shall be structured to distinguish system level from LRU to the Shop Replaceable Unit (SRU) and maintain the indentured structure formatting.

1.3.3 Updating Line Items

The contractor shall research any “unknown” Original Equipment Manufacturer (OEM) part numbers within the Tool, including the retrieval and review of Source Control Documents (SCDs) where applicable. Line item updates are required as formal weapon system source document revisions are released. All data loaded into the Tool shall be maintained at the current source document revision level. The Contractor shall establish a Technical Order Distribution Office (TODO) assignment account in order to receive T.O. revisions and updates where applicable and set up a process to receive regular updates for those weapon systems without available electronic T.O.s.

1.3.4 Tool Software and Access Support

The AF Technical data used for this requirement is considered Critical Technology and typically marked with Distribution Statement D: Releasable to DoD and DoD contractors only. AF technical data must be protected at all times therefore the contractor shall have an IT capability that is authorized for use on the AF Network (AFNET) and maintains a current and full Risk Management Framework (RMF) Assessment and Authorization (A&A) package with an Authority to Operate (ATO). At a minimum, the ATO must meet the Confidentiality, Integrity, and Availability (CIA) categorization of “Low-Low-Low”. After proposal submission, upon request of the contracting officer, the offeror has three business days to provide a DoD Security Authorization Decision document validating current A&A with an ATO. If not provided by the offeror by the third business day the government will exclude such offeror(s) and proceed with the next qualified offeror(s) who can provide a current A&A with an

ATO.

Contractors proposing an IT capability with multiple IT platforms to perform this requirement shall submit ATOs for each IT platform which house AF technical data after proposal submission, upon request of the contracting officer, the offeror has three calendar days to provide a DoD Security Authorization Decision document validating current A&A with an ATO on all IT platforms which house AF technical data. If not provided by the offeror by the third business day the government will exclude such offeror(s) and proceed with the next qualified offeror(s) who can provide a current A&A with an ATO, on all IT platforms which will have AF technical data loaded into it. All IT platforms proposed whether they contain AF technical data or not shall be linked to a single login/access point in order for users to perform necessary DMSMS research required by this PWS.

No government hardware, software or server space will be provided during the performance of this requirement.

Contractor shall provide an IT capability with a single login/access point that gives the user the ability to run queries automatically without any further manipulation of the data.

The user shall be able to perform all requirements of this PWS without having to pull data from multiple IT platforms /locations to build the desired output.

Contractor shall establish a secondary (backup) Tool system which will perform as the primary system in the event the primary system is taken offline. The secondary system will be located at an alternate location from the primary system to prevent both systems from being impacted from same event.

Contractor shall make the Tool available, 24 hours a day, seven days a week, with an uptime of 95%. Contractor shall immediately work to remedy any issues occurring between the Tool and AF computer systems preventing user access to the Tool;

examples being SDC updates, cybersecurity patches, etc. and contractor shall report troubles and remedies in the MSR.

The contractor shall provide Common Access Card (CAC) access as well as other secure logon methods for Tool access. The contractor shall maintain compatibility with the AF Standard Desktop Configuration (SDC) throughout the period of performance and as the SDC changes. All government-provided data input and processed using the Tool must at all times be maintained in a readable and readily retrievable format, which requires no additional software or tools to read and retrieve beyond those already installed on the AF SDC computers.

The contractor shall maintain compatibility with Section 508 of the Rehabilitation Act throughout the period of performance. Sections (1194.21), (1194.22), (1194.31) and (1194.41) of the 508 Standards for Electronic and Information Technology apply to this

PWS.

The contractor shall maintain the Tool application software to ensure proper functionality in support of the AF DMSMS processes. The contractor shall provide a single login/access point to the AF and all authorized users as designated by the government, for use in the analysis of DMSMS issues. Contractor shall not allow access to the Tool until a completed and approved DD Form 2875 “System Authorization Access Request (SAAR)” is received from the government program manager. Where applicable, the contractor shall execute any Non-Disclosure Agreements (NDAs) required to ensure appropriate personnel have access to the tool.

The Tool shall be made available to all authorized users who have access to the internet. The Tool shall be updated daily with changes and updates in the structural configuration and content of systems as contractor completes the weapon system data loading/weapon system data updating process. The Tool database structure shall mirror the full hierarchal configuration of all loaded weapon systems. Component…aka piece part status updates shall be provided on a daily basis or as data is made available via real-time access.

The contractor shall provide the government program manager DMSMS Tool documentation (e.g. Architecture views, Operational views and Plan of Action & Milestones) as required to support the annual certification of defense business systems as required by, Title 10 United States Code § 2222.

1.3.5 Tool Database Training

The contractor shall provide Tool training to Air Force personnel as well as Air Force contractors on contract to support obsolescence management. The contractor shall provide training for approximately 1000 Tool users at time of award. Throughout the year, the contractor shall provide training to approximately 300 Air Force personnel and Air Force contractors on contract to support obsolescence management. Training manuals shall be provided as hardcopy in contractor format to each student in the class.

The contractor training shall be conducted locally at the contractor’s facilities or government-provided facilities.

1.3.6 Tool Data Export to the, Applications, Programs and Indentures (API)

The contractor shall provide electronic API formatted files to applicable Project Managers. The contractor shall assist in validating the Tool API export files against any existing API full range listing from the D200F database to ensure proper updating of the D200F database.

1.3.7 Source Document Loading Accuracy

The contractor shall proactively identify errors within government source documentation such as but not limited to administrative errors, incorrect part numbers (P/N), military standard updates, CAGE Code changes, description errors, quantity errors, etc.

discovered during the Tool data identification and loading process. The contractor shall document errors using contractor error sheets. The contractor shall submit the error sheets in conjunction with the Monthly Status Report (MSR).

1.3.8 Tool Parts Component Status Verification and Tracking

The contractor shall review OEM SCD (Source Control Drawing) and/or D043 Interchangeability and Substitutability (I&S) data to identify those manufacturer parts which have been previously qualified as an alternate part. The contractor shall determine the current manufacturing status for all parts loaded and updated per this PWS. The contractor shall determine the OEM P/N flag status in the Tool (i.e. red, yellow, green) based solely on qualified manufacturer parts in support of OSS&E compliance. The contractor shall flag all unknown parts (contractor suggested color).

The contractor shall flag all logistically solved parts (contractor suggested color) based on DLA / D200 and User defined Logistics Solution End Dates. The Tool shall also have the ability for the user to turn all logistically solved part information off when necessary.

The contractor shall flag all Build to Print (BTP) and Common Industrial Item (CII) parts (contractor suggested color). The contractor shall proactively monitor the manufacturing status and provide alerts via the Tool when the manufacturing status of a part changes.

1.3.9 DMSMS Case Tracking Support

The Tool shall provide a means for AF personnel as well as AF contractors to request and track Cases for the resolution of DMSMS issues. The Tool shall track each Case from submission to closure and allow for the uploading of documentation in support of each Case. The Cases shall be made visible to all AF users in order to facilitate the sharing and collaboration of DMSMS resolutions. The Tool shall provide a means to associate SD-22 resolution categories to each Case.

1.3.10 Custom Reports

Primary delivery of reports is by users accessing the Tool and running their own reports.

The contractor shall perform specialized queries of the Tool as requested by the government. Reports shall be returned to the government via e-mail within two (2) working days from receipt of request.

1.3.11 DMSMS Process Coordination

The contractor shall establish a working relationship with other contractors supporting a government contract for activities such as custom reports, process changes, updates, issues, questions, Tool administration (usernames/passwords), data interpretation and data gathering.

1.3.12 Program Management

The contractor shall provide program management oversight to ensure effective, efficient, and timely satisfaction of all tasks called out in this PWS.

1.3.13 Expertise/Professional Services

The contractor shall provide onsite professional and technically qualified personnel to perform assigned tasking at Hill AFB, Warner Robins AFB, Wright Patterson AFB and Tinker AFB. The contractor shall provide total task management and supervise contractor personnel. The contractor’s technical lead shall serve as the primary point of contact for all technical aspects of the required work. This person shall also be a prime provider of the required technical services. It should be further noted that the contractor’s program manager shall serve as the primary point of contact for all programmatic issues including cost, schedule and performance. Additionally, the contractor’s contract manager shall serve as the primary point of contact for all contractual issues.

Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and formal/informal written correspondence.

1.3.14 Monthly Status Reports (MSR)

The contractor shall provide to the government, on a monthly basis, a MSR. This MSR shall detail the current program status to include: work completed to date and future program plans. A written status report for each action item shall be included in the MSR. The MSR shall be divided into sections, as designated by the government.

Applicable metrics shall be collected and reported monthly employing a standardized reporting format to be agreed upon by the government and contractor. The DMSMS program MSR will be subject to quality control measures to ensure accuracy of the information therein before delivery to the government COR. The first MSR will be due 45 calendar days after contract award.

1.3.15 Kick-off Meeting

The contractor shall host a kick-off meeting, at Tinker AFB, scheduled within 90 calendar days after contract award. No kick-off meeting required for award of option years.

1.3.16 Technical Interchange Meeting (TIM)

The contractor shall host a TIM annually to discuss progress, achievements and outstanding technical DMSMS issues requiring the attention of the AF.

1.3.17 Annual Program Review

The contractor shall host an Annual Program review in the last month of the period of performance with the government at Tinker AFB. The contractor shall host this meeting to discuss progress and achievements made during the contract period of performance, as well as any outstanding DMSMS issues requiring the attention of the AF. The contractor shall provide this information in a final report. This report will include individual breakouts for all government DMSMS issues. Final report shall be submitted to the government COR.

1.3.18 Meeting Agenda

The contractor shall submit a meeting agenda to the government COR 5 working days before each contractor hosted meeting, outlining the intended topics for discussion in support of this effort. Contractor format is acceptable.

1.3.19 Meeting Minutes

The contractor shall submit meeting minutes to the government COR 5 working days after each contractor hosted meeting, summarizing the events and actions from meetings supported under this effort. Contractor format is acceptable.

1.3.20 Contractor Manpower Reporting

Contractor shall comply with the “Contractor Manpower Reporting” process as described in APPENDIX G.

1.4 Government Inspection and Acceptance of Deliverables

The government COR will have the right to reject or require corrections of any deficiencies found in deliverables. In the event of rejection of any deliverable, the contractor will be notified in writing by the COR of the specific reasons why the deliverable was rejected. The contractor shall have 30 calendar days to correct the rejected deliverable and resubmit to the government COR for re-inspection. If no comments are provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the government. The government will use standard inspection process in accordance with FAR 52.246-2,-3,-4,-5, or -6 as applicable to contract.

1.5 Delivery Schedule and Period of Performance

1.5.1 Delivery Schedule

Section Description Due Date

1.3 and

APPENDIX B

Government Owned Part Attribute Data

In accordance with CDRL A006, delivery to COR

1.3.4 Tool Software and Access

Support

In accordance with CDRL A005, as requested

1.3.9 DMSMS Case Tracking

Support

In accordance with CDRL A007, as requested

1.3.14 Monthly Status Report

(MSR)

In accordance with CDRL A003, NLT then 10th of the following month 1.3.17 Annual Program Review In accordance with CDRL A004, NLT than last month of PoP

1.3.18 Meeting Agenda In accordance with CDRL A001, five working days before each meeting

1.3.19 Meeting Minutes In accordance with CDRL A002, five working days after meeting

1.6 Special Consideration

In the event of an environmental spill or release of substance on base, the contractor shall call the Command Post at 911 who in turn will contact Environmental Management Spill Response Team.

1.7 Security

1.7.1 Government Systems

Other than what is required to perform the requirements of the contract, 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 the government program manager. The contractor shall not use or disclose the data provided by the U.S. Government for any purpose or in any manner not specifically authorized or required by the contract and this PWS.

1.7.2 Security Clearance

The efforts required for this task are expected to be UNCLASSIFIED and should not require the contractor personnel to obtain a security clearance.

1.7.3 Base/Area Badges

The COR/Program Manager will assist contractor personnel in processing the necessary Department of Defense (DoD) forms to obtain base or area badges for access to government facilities.

1.7.4 Automated Information Systems

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 contract award but prior to AIS access. When the period of performance is complete and/or contractor personnel leave work on this project they will have 5 working days to terminate all their network user accounts and to return all access cards and base identification badges.

All contractor personnel who will be issued a CAC shall successfully complete Information Assurance (IA) training prior to obtaining access to the network.

All contractor personnel shall comply with IA policies and revisions. The contractor shall ensure terminated employees network access is removed within 2 hours of termination notice. The AF Communications Squadron reserves the right to terminate the contractor’s access to the network at any time to preserve the integrity of the local network.

1.8 Government Program and Contract Management

1.8.1 Government DMSMS Program Management

Overall program management for this contract resides at the 429 SCMS located at Tinker AFB. The government COR will be approval/disapproval authority of all deliverables listed in this PWS.

1.8.2 Government Project Managers

The government project managers will be located at Hill AFB and Robins AFB. Project Managers are responsible for site specific day to day non-contractual activities to include assisting contractor personnel with local facility and system access request and assisting government program manager with review of applicable deliverables.

1.8.3 Government Contract Management

Responsibility for contracting activities rests solely with the government Procuring Contracting Officer (PCO). No conversation, recommendations, or direction, whether given directly by or implied by government personnel, that will affect the scope, schedule, or price of the program covered by this PWS, shall be acted upon by the contractor unless specifically approved by the government PCO.

1.9 Safety Requirements

1.9.1 General Safety Requirements

1.9.1.1 Safety Provisions

While performing work under this contract the contractor shall comply with all applicable federal, state, and local and the specific Air Force regulations (as applicable) regarding occupational safety and health addressed in the PWS/SOW. The contractor shall notify the PCO, as soon as possible but notification will not exceed; eight (8) hours for any damage to government property where the dollar value exceeds $500,000.00 and within two workdays, for any damage to government property less than $500,000.00 during the execution of the contract. The contractor shall notify the (PCO) as soon as possible but notification will not exceed; eight (8) hours of any death or injury to contract personnel which occur while on a government installation.

1.9.1.2 Accident Investigation

If the government elects to conduct an investigation of the accident, the contractor shall cooperate fully and assist government personnel until the investigation is completed.

Mishap notifications shall contain, as a minimum, the following information:

a. Contract, Contract Number, Name and Title of Person(s) Reporting

b. Date, Time and exact location of accident/incident

c. Brief Narrative of accident/incident (Events leading to accident/incident)

d. Cause of accident/incident, if known

e. Estimated cost of accident/incident (material and labor to repair/replace)

f. Nomenclature of equipment and personnel involved in accident/incident

g. Corrective actions (taken or proposed)

h. Other pertinent information

If requested by the designated PCO, the contractor shall immediately secure the mishap scene/damaged property and impound pertinent maintenance and training records, until released by the Procuring Safety Office. Contractors will not dispose of contract data related to a mishap until notified to do so by the PCO.

1.9.1.3 Applicable Regulations and Air Force Instructions

29 CFR 1910 OSHA Standards for General Industry

AFM 91-203; AIR FORCE OCCUPATIONAL SAFETY, FIRE, AND HEALTH

STANDARDS

AFI 91-207; THE US AIR FORCE TRAFFIC SAFETY PROGRAM

AFI 31-218; MOTOR VEHICLE TRAFFIC SUPERVISION

1.9.2 Emergency Procedures

While on a government installation the contractor will be required to follow applicable installation traffic safety regulations and any applicable safety requirements required by the work center supervisor as it pertains to execution of the contract while in the work center; these may include but are not limited to general personal protective equipment such as safety glasses, hearing protection, and hard hats. The contractor will comply with base/shop emergency procedures for fire, tornado etc.

1.9.3 Voluntary Protection Program (VPP)

All three complexes are in the process of pursuing VPP recognition or have already been recognized under the Occupational Safety and Health Act (OSHA) Voluntary Protection Plan (VPP). VPP impacts all "applicable contractors" operating on Air Force Installations. (Applicable contractors are contractors that have completed 1000 hours or more at all three sites within 3 months on the same contract.) It is the contractor's responsibility to ensure its employees and managers have a comprehensive understanding of VPP as well as full compliance with OSHA requirements. Contractor shall follow the safety and health rules of the installation, OSHA and this PWS/SOW.

Detailed information on VPP is available on the OSHA website at http://www.osha.gov/dcsp/vpp/index.html.

The contractor shall provide their Total Case Incidence Rate (TCIR), their Days Away Restricted and/or Transfer Case Incident rate (DART) rates and their OSHA Form 300A annually to the Contracting Officer and/or the COR for consolidation and submission as part of the installation's annual VPP Self and Health management report. TCIR and DART rates are due by the 15th of January of each year or by the end of the period of performance of the contract.

The contractor is responsible for compliance with the OSHA (Public Law 91-596). The contractor shall submit a Safety and Health Plan and corresponding site safety checklist to the contracting officer 10 work days after contract award. The contractor's Health and Safety plan shall include appropriate measures to ensure the contractor reacts promptly to investigate, correct and track alleged safety and health violations and uncontrolled hazards in the contractor work areas.

The contractor's Safety and Health Plan shall identify the processes and procedures the contractor shall use to track compliance with the Safety and Health Plan, and the process and procedures that shall be used to correct violations.

The contractor's Safety and Health Plan shall demonstrate a management commitment to employee safety and health and shall identify the application of the safety and health plan to subcontractors. (If applicable) http://www.osha.gov/dcsp/vpp/index.html

The contractor's Safety and Health Plan shall identify the roles and responsibilities of the following individuals; management, supervisors, employees and safety coordinator.

The contractor's Safety and Health Plan shall identify applicable safety rules and regulations, and shall include a worksite hazard analysis to include base-line hazard identification and required control measures.

The contractor's Safety and Health Plan shall include a job site analysis to include hazard of tasks required to control measures, identify employee safety and health training requirements and the documentation process.

1.10 Travel Requirements

1.10.1 Travel Anticipated

Contractor personnel shall be required to travel on an “as needed basis” to support the objectives of this PWS.

1.10.2 Travel – Over & Above

The items set forth below are not included in the scope of the basic work items X001 and X002. The work called for under these items shall be accomplished when, and as directed, by the PCO/ACO in accordance with DFARS 252.217-7028, Over and Above Work. When this CLIN is used to support all other CLINs, a firm fixed price shall be negotiated prior to performance of the work. Payment shall be in accordance with FAR 31.205-46. All reimbursable travel costs shall be billed in accordance with Joint Federal Travel Regulations (JFTR)and the Fixed General & Administration (G&A) rates in CLIN X003.

1.10.3 Travel Pre-approval

The contractor is responsible for making all necessary travel arrangements. The contractor shall obtain written approval to travel from the Contracting Officer and coordinate with the COR at least five (5) business days in advance before traveling. Any travel not approved in advance by the CO shall be at the contractor’s own risk. Contractor personnel are responsible for coordinating with the government employee with whom they are traveling for making their own travel arrangements.

Request for approval shall include the following:

o Date of Travel o Event (Purpose of Travel) o Number of Travelers o Name and Title of Travelers o Goals and Desired Outcomes of Trip o Why Alternate Methods are not Viable Options (i.e. VTC, telecom, etc. are not options to accomplish purpose and goals of trip) o Total Estimated Cost of Trip o Anticipated Itinerary with Associated Estimated Costs (i.e. airfare, hotel, rental car, etc.)

1.10.4 Travel Expenses

Contractor travel policies and procedures must be best business practices IAW FAR 31.205-46. Contractor must use FAR 31.205-46 and the DoD Joint Travel Regulation (JTR) as a guide regarding air fares, per diem, allowances and reimbursement of travel expenses. First class air travel is not authorized. Costs incurred must be in accordance with FAR 31.205-46. The government reserves the right to disallow unreasonable travel costs. Travel must be billed as a separate line item on all invoices.

1.10.5 Post-Trip Documentation

The contractor shall present travel vouchers and supporting documents for payment via invoice to the COR and CO after the completion of any travel.

1.10.6 Post-Trip Report

As part of the monthly report, upon completion of any travel, the contractor representative shall submit a trip summary.

1.10.7 Passports and Visa Requirements

Passports and Visa Requirements are not required unless the contractor shall travel to Canada to support a Site Survey.

1.11 Contracting Officer Representative/Contacts

The overall program management responsibilities for this contract reside within the 429 SCMS located at Tinker AFB, Oklahoma.

1.12 Continuation of Essential Services

This requirement is not considered mission essential.

2 SECTION II - SERVICE SUMMARY

The contractor service requirements are summarized into performance objectives that relate directly to the mission essential items. The performance threshold describes the minimum acceptable levels of service for each requirement. The contractor shall be aware that the absence of contract requirements from the service summary does not detract from its enforceability nor limit the rights or remedies of the government under any other provision of the contract. The government will use the surveillance methods contained in the Quality Assurance Surveillance Plan (QASP) to evaluate the contractor's performance for the performance objectives listed below. In the event the performance objective is not met, the contractor will be given 30 days after notification to correct the unacceptable performance, if such correction is possible. The contractor shall immediately take corrective action in accordance with the performance threshold(s). In cases where the contractor fails to implement corrective action, the CO will take appropriate measures.

The government COR assigned to the office listed in paragraph 1.11 will inspect the services listed in the services summary.

Services Summary

Performance Objective

PWS Section Performance Threshold

Monthly Status Reports

1.3.14 Report submitted is complete and accurate, no more than two errors per month. An error is defined as a rejected data submittal which is returned to the contractor for rework due to non-compliance with contract requirements.

Loading of Line Items

1.3.2 100% of contract new data load requirement within the 12 month period.

Updating Line Items

1.3.3 100% of contract line item maintenance requirement within the 12 month period.

Tool uptime/availability

1.3.4 24 hours a day 7 days a week with up time of 95%.

Health and Safety Plan, to include mishaps reporting

1.9.3 The contractor shall comply with all applicable

federal, state and local regulations regarding occupational safety and health.

3 SECTION III - GOVERNMENT FURNISHED PROPERTY/SERVICES

3.0 Security Police

The government will provide general on-base security police service. Security police telephone numbers are 911 for emergencies. There are numbers available in the base phone books for a crime in progress and non-emergencies calls.

3.1 Fire and Emergency Services

The government will provide general on-base fire protection services. The contractor shall comply with fire protection rules and regulations enforced by base. Call 911 for emergencies. For routine fire protection matters; numbers are available in the base phone book.

3.2 Emergency Medical Services

The government will provide on-site emergency medical treatment for contractor personnel who are injured or become seriously ill while on base. The telephone number for emergencies is 911. The contractor shall be responsible for any associated costs.

3.3 Special Access to Facilities and Property

Access to government facilities is limited. Therefore, the contractor shall coordinate required access/usage times and dates through the applicable government Project Manager at least 15 working days prior to the need date. Control of the facilities shall remain with the government.

3.4 Government Furnished Equipment, Materials, and Software

All Government Furnished Equipment (GFE), Government Furnished Software (GFS), and Government Furnished Material (GFM) shall be returned to the Government upon completion of this contract. At the end of contract Period Of Performance, the contractor shall return the GFE, GFS, and GFM to the government.

3.5 Location/Office Space

Day to day efforts shall be performed onsite at Hill AFB, Tinker AFB, Robins AFB and Wright-Patterson AFB during normal working hours (0730-1630). Telework is not authorized; however, the COR may approve situational telework on a case-by-case basis and shall be provided advanced ample time by the Contractor to permit planning and preparation. Any telework must be approved in advance and in writing by the COR.

For contractor onsite support personnel, the government shall furnish office space, desk, chair, file cabinet, telephone, e-mail, and internet access. The contractor will be provided access to primary sources for component/system data including, but not limited to the systems listed in APPENDIX D (Sources for Component/System Data) and other data systems as necessary, plus drawings and other data from parts manufacturers. The contractor will also be provided access via the AF Instruction 17- 130 “Air Force Cybersecurity Program Management” document to automated systems used to log and track DMSMS data. The government will furnish a computer with the standard desktop configuration and a connection to a color printer on the local area network for onsite personnel only.

The contractor shall not duplicate any keys issued to them by the Government. The contractor shall prohibit the use of government issued keys by any persons other than the contractor's employees. The contractor shall prohibit the opening of locked areas by contractor employees to permit entrance of persons other than contractor's employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the PCO.

APPENDIX A: Tool Requirements Matrix

REQ#

Requirements

Definitions

1.0

Part Data & Display

Requirements related to part data received and displayed by the tool

1.1

Part Availability Flags These requirements provide specific guidelines for determining part availability flagging and specifically define each color flag in support of AF processes

1.1.1

The Tool shall base OEM Part Number (P/N) flagging strictly on the current manufacturing status of the qualified manufacturer part(s) based on the sources listed per the OEM Source Control Document (SCD).

This supports compliance with the AF mandated Operational Safety, Suitability and Effectiveness (OSS&E) guidelines.

1.1.2

The Tool shall denote OEM P/Ns as “green” when two or more qualified manufacturer part numbers are currently in production by the qualified manufacturers.

The AF has current ability to procure qualified parts from two or more qualified manufacturing sources.

1.1.3

“yellow” when only one qualified manufacturer P/N is currently in production by a qualified manufacturer.

The AF has current ability to procure qualified parts from only one qualified manufacturing source.

1.1.4

The Tool shall denote OEM P/Ns as “red” when no qualified manufacturer P/Ns are currently in production by a qualified manufacturer.

The AF does not have the current ability to procure qualified parts from any qualified manufacturing source. While not currently in production, qualified parts for red OEM P/Ns may be available from aftermarket suppliers.

1.1.5 having a “logistics solution”, contractor’s color of choice, when no qualified manufacturer P/Ns are currently in production by a qualified manufacturer but DLA and/or D200 have existing stock of qualified manufacturer P/Ns available.

The AF does not have the current ability to procure qualified parts from any qualified manufacturing source but DLA and/or D200 have existing stock available for purchase

1.1.6

“Build to Print” (BTP), contractor’s color of choice, when replacement of the component requires it to be manufactured utilizing the Source Control Drawing.

The AF’s only means of procuring the qualified part is to have it manufactured or possibly locate existing stock.

1.1.7

“Common Industrial Item” (CII), contractor’s color of choice, when the component is considered Bench or Shop Stock.

The AF has the ability to procure qualified parts locally.

1.1.8

“Unknown” or “Proprietary”, contractor’s color of choice, when the Source Control Drawing is unavailable or not releasable to contractors thus no qualified manufacturing P/N can be determined.

The AF would have to locate or review the Source Control Drawing to obtain the qualified manufacturing source and then determine its manufacturing or procurable status.

1.2

Part Category Tracking & Statusing

(Standard and Non-standard)

These are various categories of parts the AF finds necessary to track and status.

1.2.1

The Tool shall have existing functionality to provide tracking and statusing of all electronic components.

The Tool shall perform both tracking and statusing all electronic parts.

1.2.2 to provide tracking and statusing of all custom and hybrid components.

The Tool shall perform both tracking and statusing all custom and hybrid components. Including the ability to identify and display the Die that make-up hybrid components and custom devices.

1.2.4 to provide tracking and statusing of all

Radio Frequency (RF) devices.

statusing RF devices.

1.2.5 to provide tracking and statusing of all non-electronic devices.

statusing non-electronic devices.

1.2.6 to provide tracking and statusing of all materials.

Materials refer to chemicals, paints and metals, etc. The Tool shall perform both tracking and statusing all materials.

1.2.7 to provide tracking and statusing of all electromechanical parts.

statusing electromechanical parts.

1.2.8 to provide tracking and statusing of all lead and lead-free components.

Restriction of Hazardous Substances (RoHS). The Tool shall perform both tracking and statusing lead and lead-free components.

1.2.9

The Tool shall perform tracking and statusing of Commercial off the Shelf (COTS).

statusing of COTS.

1.2.10

The Tool shall perform tracking and statusing of all procurable/critical statusing of all procurable/critical

1.3

Part Attribute Data These are various attributes of parts the AF finds necessary to capture and display.

1.3.1

The Tool shall have a separate field to contain the Work Unit Code (WUC) for LRUs, SRUs and Assemblies where WUC is provided in the government source data.

USAF unit identifier

1.3.2

The Tool shall have a separate field to contain the Original Equipment

Manufacturer (OEM) part identification number.

OEM identifying P/N as specified on SCDs.

1.3.3

The Tool shall have separate field to contain the Commercial and Government Entity (CAGE) codes for all data elements where the CAGE Code is provided in the government source data.

CAGE identification

1.3.4 contain the Weapon System Designator Code (WSDC) code for all data elements where WSDC is provided in the government source data.

WSDC

1.3.5 contain the approved vendor P/N per the

SCD.

Approved vendor P/N identified as meeting all of the OEM performance requirements and contained in the OEM design data.

1.3.6 contain the part description.

Description of the part.

1.3.7 contain part specific notes (in addition to any notes that may be entered by tool users).

Notes associated to the part such as acquisition notes.

1.3.8 contain the National Stock Number

(NSN).

Government provided stock ID.

1.3.9 identify whether a part is Radiation Hardened (Rad Hard), a Hardness Critical

Item (HCI) or a Critical Safety Item

(CSI).

Descriptors of a part as noted in the SCD.

1.3.10 identify the environmental classification of the part.

RoHS compliant, RoHS exempt, Lead- Free, etc.

1.3.11 display DLA stock & usage rate for the part.

Stock-on-hand and latest usage rate provided by DLA.

1.3.