PWS18July2014.pdf

PERFORMANCE WORK STATEMENT

(PWS)

for

Data Mining, Data Loading, and Data Maintenance

429th Supply Chain Management Squadron

Air Force

Diminishing Manufacturing Sources

And

Material Shortages

(DMSMS)

Management Program

PREPARATION DATE: 18 Jul 14

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 Custom Reports

1.3.10 DMSMS Process Coordination

1.3.11 Program Management

1.3.12 Expertise/Professional Services

1.3.13 Monthly Status Reports (MSR)

1.3.14 Kick-off Meeting

1.3.15 Technical Interchange Meeting (TIM)

1.3.16 Annual Program Review

1.3.17 Meeting Agenda

1.3.18 Meeting Minutes

1.3.19 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.2 Emergency Procedures

1.9.3 Voluntary Protection Program (VPP)

1.10 Travel Requirements

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 all Air Force (AF) users located at Hill AFB, Tinker AFB, and Robins AFB hereafter to be called Air Force Sustainment Center (AFSC) to proactively reduce mission capability impacts. This effort also supports users outside the AFSC. The AF must continue to proactively improve logistics support and system sustainability. The AF users must be able to status parts across multiple weapon system platforms which require linking of the 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 AFSC 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 any delays in organic depot-level repair as well as Contractor repair, and

(4) improving 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 weapon systems technical data as managed by the AFSC 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 shall be appropriately linked in order to perform the requirements called out in this PWS. All imported data as well as all new 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 associate 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 accept status and display the items called out in this PWS.

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:

AFI 21-118, Improving Air and Space Equipment Reliability and Maintainability AFMCI 23-103, DMSMS Program 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 SD-22, DMSMS Guide Book AFI 61-204, Disseminating Scientific and Technical Information TO 00-5-1, AF Technical Order System

The contractor shall obtain the forms and publications expressly required to perform the work in this contract via internet at 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 indentured parts data in a flat file format on Computer Disks (CDs). Flat files will contain approximately 21 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 21 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 within 90 calendar days after contract award.

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 at no additional cost.

Furthermore, all new part attribute data referenced in APPENDIX B input into the Tool during this contract shall be the property of the Government and delivered at the end of the contract at no additional cost. The Government shall own and have unlimited rights to all the data listed in APPENDIX B during and at the end of the contract.

At the end of every ordering period, a copy of all APPENDIX B data shall be delivered to the Government in a flat file format easily transferrable and usable by the Government without any reverse engineering effort.

http://www.e-publishing.af.mil/

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 proposal. The contractor shall also provide engineering, technical and program support services for the effort. The requirements detailed below will be broken out by specific AFSC 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 proposal, 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 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 TO 00-5-1 and AFI 61-204. 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 systems required for contractor access is provided in APPENDIX D - Component/System Data. The contractor shall analyze the AFSC furnished 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 hardware configuration.

1.3.2 Loading of Line Items

The contractor shall perform loading of weapon system structure, including test and simulator equipment. Unless a partial data load is requested by the Government program manager, the contractor shall include all piece parts in the latest configuration.

The contractor shall use Government managed Technical Orders (T.O.) and drawings 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. Unless requested by the Government program manager, the data loaded shall reflect the full hierarchal configuration of the technical data and consist of 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).

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 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.

1.3.4 Tool Software and Access Support

The AF technical data is considered For Official Use Only (FOUO) and must be protected as such. The contractor shall have a current Certification and Accreditation (C&A) with an Authority to Operate (ATO) for the Tool at time of proposal submission.

Contractor shall submit a copy of the C&A and signed ATO with the proposal.

Contractor shall maintain the C&A and ATO as updates are released. Contractor shall maintain a current C&A and ATO throughout the period of performance of this requirement.

Contractors proposing an IT capability with multiple tools to perform this requirement shall have C&A with ATO on all tools which will contain FOUO data at time of proposal.

All tools proposed whether they contain FOUO data or non-FOUO data, shall be linked to a single login/access point in order for users to perform necessary DMSMS research required by this PWS.

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 tool/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.

Contractor shall make the Tool available, 24 hours a day, seven days a week, with an uptime of 95%.

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 (NDA) 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 data loading/data maintenance process. The Tool database structure shall mirror the full hierarchal configuration of all loaded systems. Component 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 per, Title 10 United States Code § 2222.

1.3.5 Tool Database Training

The contractor shall provide Tool training to AFSC personnel as well as AFSC contractors on contract to support obsolescence management. The contractor shall provide training for approximately 500 Tool users at time of award. Throughout the year, the contractor shall provide training to approximately 150 new AFSC personnel and AFSC 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

If requested, a copy of past technical data errors found during Tool loading will be provided to the contractor at the beginning of this effort. The contractor shall proactively identify errors within Government source documentation such as 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 changes using contractor error sheets.

Errors shall not be replicated in the Tool until source documents are formally revised.

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 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 electronic parts, as well as switches, relays and connectors.

Status of other component types shall be accomplished on a case by case basis as agreed upon by the Government program manager and the contractor. 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). 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 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.10 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.11 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.12 Expertise/Professional Services

The contractor shall provide onsite professional and technically qualified personnel to perform assigned tasking. 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. No personal services shall be performed.

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.13 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.14 Kick-off Meeting

The contractor shall host a kick-off meeting scheduled within 90 calendar days after contract award.

1.3.15 Technical Interchange Meeting (TIM)

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

1.3.16 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.17 Meeting Agenda

The contractor shall submit a meeting agenda for contractor hosted meetings 5 working days before each meeting, to the Government COR, to support any meeting under this effort. Contractor format is acceptable.

1.3.18 Meeting Minutes

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

1.3.19 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.

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

Last month of contract period of performance

1.3.13 Monthly Status Report

(MSR)

Monthly by the 10th of the following month

1.3.16 Annual Program Review Last month of contract period of performance

1.3.17 Meeting Agenda Five working days before each

meeting

1.3.18 Meeting Minutes Five working days after each

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 Government 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 Common Access Card 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 Contracting Officer (CO). 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 CO.

1.9 Safety Requirements

1.9.1 General Safety Requirements

1.9.1.1 Safety Provisions

The contractor shall comply with all safety provisions, e.g., technical specifications, technical publications, Federal Occupational Safety and Health Standards (Title 29 CFR. Part 1910). If there is no applicable Occupational Safety and Health Administration standard, use other applicable nationally recognized sources of safety, health, and fire prevention standards referenced in the work requirements of this contract.

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.

1.9.2 Emergency Procedures

Contractor employees shall follow the direction of Government employees in regards to emergency procedures, i.e. fire, tornado, active shooter, bomb threats. It is the responsibility of the contractor to provide guidance and establish procedures for responding to an emergency for their employees. It is the contractors' responsibility to account for their employees following an emergency evacuation. Contractor personnel shall participate with Government personnel in all fire and tornado drills at no additional cost to the Government.

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.

http://www.osha.gov/dcsp/vpp/index.html

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

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

Travel shall be required in support of the below requirements.

Destination No. Trips No.

Days

Contractor Kick-off Meeting 1 3

TIM 1 3

Hill AFB, UT 2 3

Robins AFB, GA 2 3

Tinker AFB, OK 2 3

The contractor may be required to travel to support the objectives of this PWS. The contractor shall obtain approval from the Government COR five (5) working days in advance before traveling. As part of the monthly report, upon completion of any travel, the contractor representative shall submit a trip report. Airfare for travel and per Diem shall be billed IAW Joint Travel Regulations and Federal Acquisition Regulation (FAR) Part 31. The contractor is responsible for making all necessary travel arrangements.

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 a reasonable time 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.13

Report submitted is complete and accurate, no more than two errors per month.

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 and Robins AFB during normal working hours (0730-1630). 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 33-200 “Information Assurance (IA) 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 CO.

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

The Tool shall denote OEM P/Ns as

“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.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

The Tool shall have existing functionality 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.3

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

The Tool shall perform both tracking and statusing magnetic parts.

magnetic parts

1.2.4

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

Radio Frequency (RF) devices

The Tool shall perform both tracking and statusing RF devices.

1.2.5

The Tool shall have existing functionality to provide tracking and statusing of all non-electronic devices

The Tool shall perform both tracking and statusing non-electronic devices.

1.2.6

The Tool shall have existing functionality 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

The Tool shall have existing functionality to provide tracking and statusing of all electromechanical parts

The Tool shall perform both tracking and statusing electromechanical parts.

1.2.8

The Tool shall have existing functionality 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) and COTS-Test Replaceable

Units (TRU)

The Tool shall perform both tracking and statusing of COTS and COTS TRU equipment.

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 all data elements 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

The Tool shall have a separate field to contain the part description

Description of the part

1.3.7

The Tool shall have separate field to 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

The Tool shall have separate field to display DLA stock & usage rate for the part

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

1.3.12 contain a (Military Specification) MIL-

SPEC number when available

The applicable MIL-SPEC governing design of the part or component.

1.3.13

The Tool shall have the capability of receiving and tracking all parts and components in the platform

To include, pneumatics, screws, nuts, bolts, washers, seals, and structural components. A full indentured BOM as contained in the OEM design data

1.3.14

The Tool shall have the capability of receiving and tracking various forms of supporting documentation (Product

Change Notices (PCN), Product

Discontinuance Notices (PDN), GIDEP notices, etc.)

This requirement gives the end user the ability to query associative part documentation

1.3.15 contain DMEA resolution cost data and a means for the user to indicate the appropriate DMEA category for the implemented solution

This allows the user to utilize DMEA data to automatically determine the cost avoidance based on the types of obsolescence resolutions being implemented.

1.3.16

The Tool shall have a separate field to contain the figure number of the record

T.O. identifier

1.3.17 contain the sheet number of the record

T.O. identifier

1.3.18 contain the P/N index for all data elements

T.O. identifier which helps show the location of the data element

1.3.19 contain the reference designator for all data elements where the reference designator is provided by the Government source data

T.O. identifier which helps show the location of the data element

1.3.20 contain the Usable On Code (UOC) for applicable data elements where the UOC is provided by the Government source data

T.O. identifier which helps show revision applicability of data elements

1.3.21 contain the P/N symbol where the P/N symbol is provided by the Government source data

T.O. identifier that is assigned/attached to a P/N

1.3.22 contain the Units Per Assembly (UPA) or quantity of a data element

T.O. identifier that displays the quantity of data elements for a given T.O. index

1.3.23

The Tool shall have a separate field to contain the Source, Maintenance, and

Recoverability (SMR) code where the

SMR code is provided by the Government source data

T.O. identifier that shows the maintenance/recoverability of a data element

1.3.24

The Tool shall have a separate field to contain the P/N indenture where the P/N indenture is provided by the Government source data

T.O. identifier that shows the structured hierarchy of the BOM

2.0

Structure Data & Display Requirements related to structure data received and displayed by the tool

2.1

BOM Types Types of Bills-of-Material which must be accepted and accurately displayed by the tool.

2.1.1

The Tool shall accept and display a full indentured BOM with an unlimited level of indenturing

Contained in the OEM design data.

Unlimited indenture levels are required to insure all AF data is structured accurately and completely.

2.1.2

The Tool shall accept and display a flat file (non-indentured) BOM

Tool displays all items within BOM on a single level of indenture (non-structured)

2.1.3

The Tool shall track and maintain all source documents and their interdependencies used to build the hierarchal configurations with unlimited levels of indenture.

Maintains hierarchical relationships of the source document BOM in accordance with OSS&E regulations

2.1.4

The Tool shall display availability flagging for equipment and/or assemblies at every level of indenture.

Tool can accept and display availability flagging assigned to structure elements

(i.e. LRUs, SRUs, etc.)

3.0

Availability Projection Capability Requirements that specifically pertain to the tools ability to predict the future availability of parts and project the full impact due to current and future obsolescence

3.1

Projecting Obsolescence The Tool’s availability projection algorithm shall be embedded within the application such that it accurately predicts the timing of future obsolescence impacts in support of proactive DMSMS management

3.1.1

The Tool’s component availability projection capability shall determine the current percentage and predicting the future percentage of obsolete components by unique OEM part number

Red components as a percentage of the total

3.1.2

The Tool’s component availability projection function shall determine the current percentage and predicting the future percentage of sole source components by unique OEM part number

Yellow components as a percentage of the total

3.1.3

The Tool’s component availability projection function shall determine the current percentage and predicting the future percentage of multi-sourced components by unique OEM part number

Green components as a percentage of the total

3.1.4

The Tool shall analyze the obsolete parts versus the Next Higher Assembly (NHA) they populate and calculate the percentage of obsolete parts versus the total count of all components indentured to the NHA.

This functionality shall have the option to distinguish those parts with any previously identified logistics solutions

This functionality will allow the user to see the obsolescence density of an assembly and compare it to other assemblies within the same level of indenture. This is critical for the AF in determining the most appropriate and cost effective means of resolving obsolescence issues.

3.1.5

The Tool component availability projection function shall forecast component manufacturing obsolescence out 20 years

The prediction should be based on the specific technology of the die and/or part as well as package type

3.1.6

The Tool component availability projection capability shall track universal effects of an obsolete part at each level of indenture up to the platform level

This allows the end user to identify the total affect to all equipment on a platform when a part goes obsolete

3.1.7

The Tool electronic component availability projection function shall track the universal effects of obsolete parts across multiple platforms within the Tool

This requirement allows the user to look across any platform within the Tool to see where an obsolete part is being used.

This aids in the prevention of reengineering the same part multiple times across different platforms with in the AF and promotes collaboration and cost-sharing when implementing common solutions.

3.1.8

The Tool component availability projection function shall forecast component manufacturing obsolescence based on a user-defined time period not to exceed period set in 3.1.5.

This requirement allows the user the flexibility to set the availability projection time period.

3.2

Identify Alternate Component

Solutions

The Tool shall have the capability of identifying alternative component solutions for forecasted component obsolescence

3.2.1

The Tool electronic component availability projection function shall identify the obsolescence status of qualified replacement parts

These are OEM qualified parts from the

OEM SCD that may not be provided by the T.O.

3.2.2

The electronic component availability projection function shall identify the obsolescence status of functional replacement parts

Parts that perform the same function but in different technology and /or package.

3.2.3

The electronic component availability projection function shall identify the obsolescence status of Die sources

Die sources are considered manufacturers who are still fabricating the silicon used in the specific part in question.

3.2.4

The electronic component forecasting availability projection shall identify the availability of DLA stock

Identifies parts which are currently available from DLA (whether or not they are currently being manufactured).

3.2.5

The availability projection function shall identify the real-time availability of commercial stock

This is any stock available from vendors and manufacturers and can be accomplished through a link that provides this type of data

3.2.6

The availability projection function shall identify the real-time availability from aftermarket resources

Approved and unapproved vendors that have bought up stock for resale.