17-32041_SOO_100_kW_PTMLB_20170413_(TRB_approved).docx

13 Apr 2017

STATEMENT OF OBJECTIVES (SOO)

FOR

REVISION OF TO 33AA7-56-31

FOR

Portable Trailer Mounted Load bank (PTMLB)

NSN 6625-01-539-5683RH, P/N 102500, A/M24T-16

Table of Contents

Purpose The purpose of this program is to provide revision to the technical content of Air Force (AF) Technical Order (TO) 33AA7-56-31, Operation Instructions and Intermediate Maintenance with Illustrated Parts Breakdown for the 100 kW Portable Trailer Mounted Load Bank (PTMLB), Part Number 102500, A/M 24T-16 that was delivered on contract FA8533-05-D-0003.

Scope/Objectives The Government requires a contractor to revise technical content of TO 33AA7-56-31 to reflect two (2) different configurations of the fielded PTMLB’s hardware and software and improve the PTMLB troubleshooting. The revised TO content and troubleshooting guidance shall enable AF operators/maintainers to properly operate, maintain, and sustain 2 configurations of the PTMLBs hardware and software delivered to the AF on contract FA8533-05-D-0003. The contractor shall be responsible to identify all areas of the TO that need to be updated to ensure that the revised TO content is accurate, complete, adequate, and concise and considers all or most probable fault conditions that PTMLB’s operators/maintainers are experiencing in the field. The contractor shall be responsible for revising diagnostic software required for maintaining/troubleshooting both PTMLB configurations and provide complete software installation instructions.

Period and Place of Performance It is estimated that the total effort will take no more than 24 months from contract award: 6 months for completion and validation/verification of the TO and diagnostic software updates as well as shipment of the software media (CD-ROMs/DVD-ROMs) with revised software to the AF sites and 18 months for the technical support by the contractor’s engineering team.

It is anticipated that the most of work will be accomplished at the contractor’s facility and performing validation/verification of the TO and diagnostics software updates with contractor personnel present at USAF installation(s).

Background The TO 33AA7-56-31 delivered and accepted by the Government on contract FA8533-05-D-0003 contains vague, incomplete, and inaccurate troubleshooting instructions. Moreover, the provided troubleshooting guidance in the TO and diagnostics in the software are very limited and don’t resolve all or the most probable fault conditions that operators and maintainers are experiencing in the field. Additionally, several modifications to the PTMLB software and hardware approved by the AF were implemented by Testek Inc. into production PTMLBs with serial numbers 086 and onward, but have never been incorporated into PTMLBs with serial numbers 001 to 085 that were already delivered to the AF at the time the modifications were approved. As a result, the AF has 2 different configurations of the fielded PTMLBs hardware and software, but TO 33AA7-5-31 only reflects configuration of the PTMLBs with serial numbers 001-085. As such, the AF’s ability to properly sustain, operate, maintain, or troubleshoot the PTMLBs is very limited. Additionally, the OEM, Testek Inc., stopped providing free technical support to the AF. Testek Inc. requested to establish a technical support contract with the AF for hourly support and invoice on actual hours spent on answering any field/program office questions regarding troubleshooting guidance/deficient TO content.

Performance Objectives

5.1 The contractor shall prepare and provide a statement of work (SOW) that comprehensively, logically, and in plain language chronologically details and describes the actual work required, by the contractor, and how the contractor will be accomplishing this work to attain the objectives of this SOO. The SOW shall be submitted to the Government for review and approval 14 business days prior to start of the TO validation/verification event.

5.2 The contractor shall provide a revised TO 33AA7-56-3. This TO revision shall include, but not to be limited to the following updates to the operational, maintenance, troubleshooting, adjustments, and parts listing content of TO 33AA7-56-3:

· Updates to reflect two (2) different configurations of the fielded PTMLB’s hardware and software: first configuration for serial numbers 001-085 and second configuration for serial numbers 086 and onward;

· Updates to correct vague, incomplete, and inaccurate troubleshooting instructions;

· Updates to correct incomplete Integrated Parts Breakdown (IPB) to include missing components;

· Updates to the IPB to replace obsolete components/part numbers with current part numbers (see 7.2);

· Updates to the IPB to include a breakdown for all parts in components/subassemblies that can be replaced/repaired at the filed level;

· Updates to include all applicable drawings (except the contractor’s proprietary drawings) for the wiring diagrams/schematics while ensuring all part numbers are indicated in diagrams/schematics;

5.3 The contractor shall provide revised diagnostic software for both PTMLB configurations to improve the PTMLB troubleshooting/fault diagnostics. The contractor shall modify the software and create adequate number of the software media (CD-ROMs/DVD-ROMs), as requested by the Government, with two different software versions for the two different configurations of the PTMLBs. The contractor shall ship these software media along with complete software installation instructions to respective AF locations as indicated in the contract.

5.4 The contractor shall provide all required support and appropriate and adequate number of personnel necessary to perform the TO and fault diagnostics/troubleshooting validation/verification at the AF installation for both configurations of the PTMLB’s hardware and updated software.

5.5 The contractor shall provide a 6-month, free of charge technical support to be conducted over the phone/via e-mail correspondence to the AF users/program office after CD-ROMs/DVD-ROMs with the revised software(s) shipped to the AF sites. The contractor shall pledge and be responsible to notify the Government program office engineer and equipment specialist of any requests for technical support from the AF users and report how these requests were resolved.

5.6 The contractor shall provide additional 12-month technical support as priced in the contract over the phone/via e-mail correspondence to the AF users/program office after the 6-month free technical support is ended. The contractor shall pledge and be responsible to notify the Government program office engineer and equipment specialist of any requests for technical support from the AF users and report how these requests were resolved.

Government Property and Services Government property will not be provided.

All Department of Defense (DD) Form 1423-1 Contract Data Requirements List (CDRL) deliverables, the data and information therein, become the property of the Government upon receipt.

Access to the Government PTMLBs (both configurations) and one type of the -86 or B809 generator sets will be required and provided by the Government to perform the TO and fault diagnostics/troubleshooting validation/verification.

Program Management/Programmatic Objectives

7.1 Program manager. The contractor shall identify to the Government and maintain a single point of contact (Program Manager) for all matters under this contract. The contractor shall also ensure that all program management personnel assigned to the program shall be available, as required, to meet program objectives.

7.2 Monthly status report. The contractor shall track program progress and document such via monthly status reports. The contractor shall submit a monthly status report that shall cover the actions to date performed to attain the objectives of this SOO as well as a projection of planned work for the remaining effort. Reports shall document tasks, issues, actions, and deliverables. Problem areas shall be identified with proposed solutions and outcomes.

7.3 Program Management Review support. The contractor shall participate in and support all reviews, audits, and meetings as requested by the PCO or the contractor. Program Management Reviews shall be conducted quarterly or as required at a mutually agreeable location or via teleconferences.

7.4 Meeting agendas. The contractor shall publish an agenda for all meetings required on this contract. The contractor shall request from the Government any items or issues to be discussed or presented at the meetings, and shall include such items in the agenda. Agendas shall be submitted not less than 5 business days prior to any meeting.

7.5 Meeting minutes. The contractor shall provide a written record of the discussions, decisions, and action items identified at each meeting. Minutes shall include presentation material. The contractor shall submit meeting minutes no later than 10 business days after the meeting.

7.6 Integrated Master Schedule (IMS). A baseline IMS shall be developed at the start of the program in accordance with DI-MGMT-81861A, Format 6. The contractor shall implement and maintain the IMS using the original baseline schedule as an unchanging reference. The IMS shall be provided in both Microsoft Project and PDF formats as an attachment to the monthly status report (see 7.2).

Contract Data Deliverables

8.1 SOW. The contractor shall prepare and provide a SOW in accordance with 5.1 herein. (A001, DI-MGMT-81606, Statement of Work (SOW))

8.2 Engineering Change Proposals (ECPs). Notwithstanding any other provision in the contract no contractor or subcontractor's change in design, fabrication, assembly, part, material, process, or source of supply shall be made to the PTMLB (both configurations) product baselines (hardware or software) unless such change is submitted in writing by ECP and approved by the procuring activity. Any request for change shall be accompanied by complete documentation supporting the need for the change. A system safety impact statement shall be provided as part of the submittal; it shall quantify and qualify the system safety risk identified and how it impacts the system safety risk already identified for the system. A Notice of Revision (NOR) shall be submitted with each ECP. Additionally, for any identified obsolete part/component listed in the IPB (see 5.2), the contactor shall submit an ECP along with the NOR prior to updating the IPB for the Government review and approval. The NOR shall include all necessary supporting data such as applicable OEM drawing(s), OEM catalog data sheet(s), etc. to support the part number and/or Commercial and Government Entity (CAGE) code change. Otherwise, the Government will deny verification of any updates to the IPB. (A002, DISESS80639D, Engineering Change Proposal (ECP); A003, DISESS80642D, Notice of Revision (NOR))

8.3 Technical Manual/Technical Order.

8.3.1 Technical Manual (TM)/Technical Order (TO) requirements. The contractor shall develop and deliver updates to the TO 33AA7-56-31 in accordance with TM-86-01P. (TM-86-01P, Air Force Technical Manual Contract Requirements (TMCR))

8.3.2 TO schedule and status report. TO schedule and status report shall be in accordance with TM-86-01P. (TM-86-01P, Air Force Technical Manual Contract Requirements (TMCR))

8.3.3 TO validation/verification. The updated TO shall be validated/verified by the Government prior to final acceptance. The TO validation/verification shall be conducted at the USAF installation(s) specified at a later time. The Government will provide both PTMLB configurations and all supporting equipment necessary to conduct the validation/verification. The TO validation/verification shall take no more than 4 days. The contractor personnel shall be available during all time of the TO validation/verification. The AF personnel will be available to make power connections from the PTMLB to the generator asset(s), operate the generator set(s), and conduct TO validation/verification. The contractor personnel shall be responsible for uploading/installing updated software versions into the PTMLBs. The contractor shall be responsible for simulating PTMLB fault conditions to enable Government’s validation/verification of the updates to the troubleshooting guidance in the TO. The contractor shall provide all needed assistance to the Government during the TO validation/verification process. The contractor shall schedule the TO validation/verification to be conducted at the USAF installation(s) and notify the Government engineer of the date of the TO validation/verification no later than 14 business days prior to start of the TO validation/verification.

8.3.4 Damage to the Government property. The contractor shall be responsible for any damage to the Government property(s) during the TO validation/verification resulting from improper software updates or software installation.

8.4 Monthly status report. The contractor shall provide a monthly status report in accordance 7.2. (A004, DIMGMT80227, Contractor's Progress, Status and Management Report)

8.5 Meeting agendas. The contractor shall provide meeting agendas in accordance with 7.4. (A005, DI-ADMN-81249B, Conference Agenda)

8.6 Meeting minutes. The contractor shall provide meeting minutes in accordance with 7.5. (A006, DI-ADMN-81250B, Conference Minutes)

8.7 Integrated Master Schedule (IMS). The contractor shall provide IMS in accordance with 7.6. (A007, DI-MGMT-81861A, Integrated Program Management Report (IPMR)) Quality

9.1 The quality of the delivered product (updates to TO 33AA7-56-31 and revised software(s)) is controlled in accordance with applicable AF TOs and the contractor’s established quality program. If the problem exists with the delivered product, a Product Quality Deficiency Report (PQDR) or a negative Performance Assessment Report (PAR) will be issued by the Government and a Corrective Action Plan (CAP) shall be submitted by the contractor via a Corrective Action Report (CAR).

9.2 The contractor’s quality program shall be established and maintained in accordance with contract clauses.

9.3 With exception to the TMCR, the contractor shall deliver all data/reports associated with all CDRL deliverables listed in 8.0, with no more than one rejection of each deliverable. There shall be no more than one total rejection(s) of deliverables per 6 months. The Government will reject a deliverable if one or more technical errors or one or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with CDRL, SOO, or contract. A minor error is defined as a typographical or grammatical error. The rejected deliverable shall be corrected and resubmitted within five business days of notification of Government rejection or in accordance with the associated DD Form 1423 instructions/requirements.

9.4 With exception to the TMCR, the contractor shall deliver all required CDRLs with no more than one late submission of deliverables per 6 month. The contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery data and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

TABLE I. Summary of required CDRLs with delivery schedules.

Travel and Access to the Government Facility/Military Installations

10.1 Travel. Travel request for contractor personnel for TO validation/verification event/trip at the USAF installation(s) shall be submitted for approval to the procuring contracting officer (PCO) prior to costs being incurred and a minimum of five (5) business days in advance of departure. Travel by contractor personnel shall be conducted in accordance with the Federal Acquisition Regulations (FAR) and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract. The number of reimbursed trips to the USAF installation(s) for the TO validation/verification shall be limited to one (1) trip per location of the USAF installation.

10.2 Access to the Government facility or military installation. The contractor shall ensure contractor personnel who require access to a Government facility or military installation comply with the security requirements of the facility or installation. The contractor shall ensure contractor personnel who require access to a USAF installation comply with the FAR and applicable supplements and shall be in compliance with all applicable guidance and clauses listed in the contract.

DISTRIBUTION STATEMENT C: Distribution is authorized to US Government agencies and their contractors. Other requests for this document shall be referred to AFLCMC/WN-SEV.