3. TMQ53 CLS PWS-RFP.pdf

UNCLASSIFIED // FOR OFFICIAL USE ONLY

Aerospace Management Systems Division Air Force Life Cycle Management Center Weather

Systems / Weather Systems Branch

(AFLCMC/HBAW)

Performance Work Statement (PWS) for the

AN/TMQ-53 Tactical Meteorological Observing System (TMOS) Contractor Logistics Support (CLS)

Solicitation Number: FA8730-20-D-0005

04 June 2020 Prepared by: AFLCMC/HBAW, 75 Vandenberg Drive, Building 1630

Hanscom AFB MA 01731 Distribution Statement C: Distribution authorized to U.S. Government Agencies and their Contractors (Administrative or Operational Use) (June 2020). Other requests shall be referred to AFLCMC/HBAW, 75 Vandenberg Drive, Building 1630, Hanscom AFB, MA 01731-2103.

HANDLING AND DESTRUCTION NOTICE. For classified documents, DoD civ ilians or military personnel will follow procedures outlined in DoDM 5200.01, Volume 3, and Enclosure 3: DoD Contractors will follow procedures outlined in DoDM 5220.22, Sections 11-19. For sensitive unclassified documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

ii

THIS PAGE INTENTIONALLY LEFT BLANK.

iii

REVISION HISTORY

Revision Date Description Pages / Sections Affected Rev01 05 September 2014 Baseline publication.

Rev02 01 November 2019 Revamped FBWS PWS to reflect needs specific to the TMQ-53.

Changes throughout made in conjunction with original TMQ-53 PWS.

Rev 03 30 December 2019 Review of CDRLs and Logistics verbiage Changes made in section 7

Rev 04 04 June 2020 Industry Questions responses/revisions Entire document iv

THIS PAGE INTENTIONALLY LEFT BLANK.

v

Table of Contents

1 INTRODUCTION

2 SCOPE

3 SERVICES SUMMARY

3.1 PERFORMANCE OBJECTIVES

3.2 SERVICES SUMMARY

4 COST REPORTING

5 TRANSITION REQUIREMENTS

5.1 TRANSITION PHASE IN

5.1.1 Transition Plan

5.1.2 Transition of Government Furnished Property (GFP)

5.1.3 Transition Phase-In Status Reporting

5.2 TRANSITION PHASE-OUT

6 PROGRAM MANAGEMENT

6.1 PROGRAM MANAGEMENT PLAN

6.1.1 Risk Management

6.1.2 Security Management

6.2 CONTRACTOR PERSONNEL

6.2.1 TMOS Third Parties

6.3 MEETINGS

6.3.1 PMRs

6.3.2 TIMs

6.3.3 Interface Control Working Group (ICWG)

6.3.4 CCBs

6.3.5 Post-Award Conference

6.4 STATUS REPORTING

6.5 QUALITY ASSURANCE

6.5.1 Quality Management System (QMS)

6.5.2 Quality Assurance Program Plan (QAPP)

6.6 TRAVEL

6.7 SAFETY REQUIREMENTS

6.8 CONTRACTOR MANPOWER REPORTING APPLICATION (CMRA)

7 LOGISTICS SUPPORT

7.1 DEFINITIONS

7.1.1 Fully Mission Capable (FMC)

7.1.2 Partially Mission Capable (PMC)

vi

7.1.3 Stock Availability

7.1.4 Mission Capable (MC)

7.2 CONTRACTOR PERFORMANCE

7.3 EXCEPTIONS

7.4 HELPDESK REQUIREMENTS

7.4.1 Helpdesk Initial Call

7.4.2 Helpdesk Management

7.4.3 Helpdesk Response Time

7.4.4 Troubleshooting

7.4.5 Helpdesk Performance

7.4.6 Trouble Call Tracking

7.4.7 Mock-Ups

7.4.8 Iridium

7.5 SPARES MANAGEMENT

7.5.1 Government Furnished Material-Accountability (GFM-A)

7.5.2 REPAIR MANAGEMENT PROGRAM

7.6 WARRANTIES

7.7 Item Unique Identification (IUID)

7.8 PACKAGING, HANDLING, STORAGE, AND TRANSPORTATION (PHS&T)

7.8.1 Preservation, Packaging, and Marking Requirements

7.8.2 International Standards for Phytosanitary Measures (ISPM NO. 15) Requirements 22

7.8.3 Electrostatic Material (When Applicable)

7.8.4 Palletized Unit Loads

7.8.5 Hazardous Materials (When Applicable)

7.8.6 Reporting Discrepancies

7.8.7 Applicable Government Packaging Documents

7.8.8 Shipping/Transportation

7.9 REPORT.GREEN PROCUREMENT PROGRAM (GPP)

8 SYSTEMS ENGINEERING

8.1 MODIFICATION

8.1.1 Obsolescence Management

8.1.2 System Design Changes, Enhancements and Upgrades

8.1.3 Deficiency Reporting (DR) Process

8.1.4 Ozone Depleting Substances (ODS)

8.2 RELIABILITY AND MAINTAINABILITY (R&M)

8.2.1 Revised Maintenance Philosophies/Impacts

vii

8.3 CONFIGURATION MANAGEMENT

8.3.1 Configuration Management Plan (CMP)

8.3.2 CCB Participation

8.3.3 Configuration Status Accounting Information (CSAI)

8.4 OBSOLESCENCE RISK MANAGEMENT AND DIMINISHING

MANUFACTURING SOURCES AND MATERIEL SHORTAGES (DMSMS)

PROGRAM

8.4.1 DMSMS Responsibilities

8.4.2 DMSMS Management Plan

8.4.3 Government Industry Data Exchange Program Alert/Safe-Alert Reports

8.4.4 DMSMS Surveillance

8.4.5 DMSMS Impact Assessment

9 SOFTWARE MAINTENANCE AND CYBERSECURITY

9.1 COMPUTER RESOURCE SUPPORT

9.1.1 Software Sustainment

9.1.2 Air Force Standard Desktop Configuration (SDC) and Host-Based Security System

(HBSS)

9.1.3 Restoration Hard Disk Drives (HDD)

9.2 INFORMATION ASSURANCE VULNERABILITY ALERTS (IAVA), BULLETINS

(IAVB), AND SECURITY TECHNICAL IMPLEMENTATION GUIDES (STIGS) .. 35

9.3 SECURITY ASSESSMENT AND AUTHORIZATION

9.3.1 Assessment and Authorization (A&A) Documentation

9.3.2 Air Force Electronic Mission Assurance Support System (eMASS) Database

9.3.3 Vulnerability Testing and Management

9.3.4 Sustainment of Security Documentation

9.4 PROGRAM PROTECTION

9.4.1 Program Protection Planning and Implementation

9.4.2 Critical Program Information (CPI) Identification/Protection

9.4.3 Supply Chain Risk Management (SCRM)/Counterfeit Prevention

9.4.4 Software Assurance

10 TECHNICAL ORDER

10.1 CONTENT

10.2 DATA RIGHTS

10.3 QUALITY ASSURANCE (QA)

10.4 TO REVIEWS

10.5 CONTRACTOR CERTIFICATION/VALIDATION PROCESS

10.6 GOVERNMENT VERIFICATION

viii

10.7 TECHNICAL ORDER UPDATES

10.8 DELIVERY OF TECHNICAL ORDERS

10.9 TCTOS

11 APPLICABLE PUBLICATIONS

11.1 APPLICABLE DOCUMENTS

12 ACRONYMS

13 APPENDIX A – LIST OF FEDERAL HOLIDAYS OBSERVED

14 APPENDIX C - INDUSTRIAL SAFETY AND HEALTH REQUIREMENTS

List of Tables

Table 3-1. Services Summary Table 7-1. Acts Outside of Contractor Control Table 11-1. DoD Publications

1 INTRODUCTION

The TMOS Contractor Logistics Support (CLS) effort will provide the necessary support to sustain the currently fielded TMQ-53 systems in their approved configurations worldwide, in accordance with (IAW) the requirements, as stated in this PWS and the TMQ-53 TRD.

These systems are capable of accurately sampling, measuring, and reporting temperature; wind speed, and direction; visibility; cloud base height and amount of coverage; pressure; liquid equivalent precipitation accumulation; and freezing precipitation. These measurements will be used to derive elements that are required to create properly formatted, fully automated observations that comply with applicable reporting requirements. The systems detect, collect, and publish/deliver this information, which is then ingested by Air Force Weather Weapon System (AFWWS) weather forecast systems.

The effort outlined in this PWS will provide a single prime Contractor to sustain the AN/TMQ- 53 Tactical Meteorological Observing Systems. In order to meet these requirements the Air Force (AF) Life Cycle Management Center (AFLCMC) Weather System Branch (AFLCMC/HBAW) developed a Performance Work Statement (PWS) and the TMQ-53 system’s Technical Requirements Document (TRD), for the Contractor to adhere to under the TMOS contract.

The TMOS Contractor Logistics Support (CLS) effort will provide the necessary support to sustain the currently fielded TMQ-53 systems in their approved configurations worldwide, in accordance with (IAW) the requirements, as stated in this PWS and the TMQ-53 TRD.

The AN/TMQ-53 is an automated, tactical suite of weather sensors that provides immediate local weather conditions worldwide, including austere locations, forward operating locations, and remote sites. The AN/TMQ-53 TMOS is capable of measuring or calculating cloud coverage, cloud base height, surface visibility, present weather and precipitation detection (type, intensity, accumulation, and rate of fall), and lightning detection (direction and range), as well as Iridium satellite communications capability. The AN/TMQ-53 TMOS system supports flight operations, combat missions, and emergency and medical evacuations in strategic locations. It is networked to Overseas Contingency Operations (OCO) Commanders, operational weather squadrons, and the 557th Weather Wing (557th WW) for combat mission planning and support. Currently there are 346 fielded systems worldwide. The number of systems fielded may fluctuate.

2 SCOPE

This Performance Work Statement (PWS) defines the requirements for the Contractor Logistics Support (CLS) necessary to sustain the currently fielded TMQ-53 systems, in their baseline configuration worldwide IAW the requirements.

This includes, but is not limited to Program Management; Logistics Support (Helpdesk Support, Maintenance, Spares and Repair Management); Operational, Safety, Suitability, and Effectiveness (OSS&E) impact analysis; Test and Evaluation support; Configuration Control Board (CCB) support; and Obsolescence and Systems Engineering. Further, all system performance data, such as System Availability rates, Mission Capable rates, and Mean Time between Failure (MTBF) rates, shall be collected and reported. Additionally, program data shall be collected and reported, such as Government-Furnished Materiel-A (GFM-A) Management, materials, shipping, travel, etc., Computer Resource Support, Engineering Change Proposals (ECP), Cybersecurity, Technical Manual development and maintenance, and Contract Data Requirements List (CDRL) deliverables. The Contractor shall also support and/or perform system design changes, upgrades, and enhancements due to technical refresh of component capability, obsolescence, and diminishing sources. Any travel directed by the Government, not specified under the CLS Contract Line Item Number (CLIN), will be completed under the Travel CLIN. The Contractor shall provide worldwide support, however there is no requirement for the Contractor to travel to an overseas location in the performance of this contract.

3 SERVICES SUMMARY

3.1 PERFORMANCE OBJECTIVES

The Contractor shall plan, manage, organize, direct, schedule and control all resources, processes, activities and tasks necessary to accomplish the requirements of this PWS and of the TMQ-53 TRD. The Contractor shall provide a timely, accurate, and complete Integrated Master Schedule (IMS) program schedule (Microsoft Project Government actual version MS Project) in the Program Management Plan (PMP) and performance status in the Status Report. The Government will evaluate Contractor performance, focusing on objectives in the Services Summary and on the Contractor’s ability to fulfill overall PWS and TMQ-53 TRD requirements.

CDRL A010 DI-MGMT-81797 Program Management Plan; A008 DI-MGMT-80368A Status Report.

3.2 SERVICES SUMMARY

Table 3-1 includes performance standards (metrics) the Government will use for monitoring daily Contractor performance. These metrics are a meaningful measure of Contractor performance. This PWS is based upon the premise that the Contractor is responsible for management and quality control actions to meet the terms of the contract. Government Representatives (e.g., COR, Defense Contract Management Agency (DCMA) will audit the Contractor’s processes and will use data such as the Status Reports to aid in assessing and verifying the Contractor’s performance. If it is determined that the Contractor lacks processes to meet the standards listed in this PWS and contract, then the Contractor shall be required to establish a corrective action plan to correct identified deficiencies. The absence of any contract requirement from the Services Summary shall not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract. The Government will track all information, including correctable actions, and may use it for reporting purposes. CDRL A008 DI-MGMT-80368A Status Report; CDRL A014 DI-MGMT-80501/T Contractor’s Corrective Action Plan.

Table 3-1. Services Summary

Performance Objective PWS Section Performance Threshold

a. The Contractor shall plan, manage, organize, direct, schedule and control all resources, processes, activities, and tasks to accomplish the requirements of this PWS and of the TMQ- 53 TRD efficiently and effectively, and provide the level of support required to sustain the TMQ-53 at 96% Operational Availability

(AO).

5, 6, 7, 8, 9, 10, 11

Performance is acceptable when TMQ-53 systems are sustained at 96% AO worldwide during any month under contract or correctable to 96% within 10 business days during any month under contract (with a report showing the correction provided within 10 business days at no additional cost to the Government). The Contractor shall always report the actual AO.

b. The Contractor shall meet all Helpdesk requirements and Helpdesk performance, including staffing, hours, trouble calls, and logging.

6.4 Helpdesk requirements and Performance

requirements are met 90% of the time and are correctable to 100% within 10 business days at no additional cost to the Government.

c. The Contractor shall provide spares to operating locations within 24 hours of receiving a requirement for installations in the continental United States (CONUS) and within 72 hours to port of embarkation and/or military installation as required for destinations outside of continental United States (OCONUS).

6.4.5, 6.9 On-time deliveries are achieved 90% of the time and correctable to 100% within 10 business days at no additional cost to the Government.

d. The Contractor shall plan and execute an orderly transition.

4 Transition activities adhere to plan 95% of the time and are correctable to 100% within three business days at no additional cost to the Government.

e. The Contractor shall deliver quality data submittals IAW the CDRL.

12 Deliverable items received on-time with no more than two errors corrected to error free within 10 business days at no additional cost to the Government.

f. The Contractor shall determine proper inventory levels and repair recommendations to ensure that requisitions are filled immediately from stock on-hand.

6.5, 6.6 Performance is acceptable when the percentage of requisitions that are filled immediately from stock on-hand meets or exceeds 98%.

4 COST REPORTING

The Contractor shall provide monthly cost and hours reporting. CDRL A022 DI-MGMT- 80368A/T Status Report (Finance Report) – See Attachment on the last page of Exhibit A for detailed report.

5 TRANSITION REQUIREMENTS

5.1 TRANSITION PHASE IN

The Contractor shall have up to 90 calendar days from date of contract award to transition to full operational sustainment, ensuring an orderly transition from the incumbent(s) without impact on system operations. This transition shall be accomplished IAW the Transition Plan, which is incorporated into the contract. The Transition Plan shall include a Staffing Plan. It shall detail how employees meet the technical requirements of this PWS. The Staffing Plan shall reflect strategy regarding personnel recruiting and retention. If recruiting includes employees not currently employed by the Contractor, the plan shall support the intent to hire. The Staffing Plan shall describe not only staffing during the transition period, but maintaining staff throughout the contract. As part of the transition, the Contractor shall maintain a staff of core personnel. Core personnel include the personnel working the day-to-day support and engineering issues to maintain the program for the TMQ-53 CLS activities. Upon contract award the Contractor shall implement the CLS Transition Plan, reference Section 4.1.1. Transition from incumbents shall be completed no later than 90 calendar days following contract award, as identified in the Contractor’s transition plan. Cutover date is date the Contractor shall assume all tasks and requirements without reliance on incumbent. Contractor is responsible for all efforts and material related to making the property available for use, such as payment of all transportation, installation and/or rehabilitation costs. Prior to cutover date the Contractor shall work with the incumbent in order to provide a seamless transition to the user.

The total transition phase-in period for the TMQ-53 shall be no more than 90 calendar days from the date of contract award. The Contractor shall interact professionally to plan, and execute an orderly transition from the previous incumbent Contractors. During the transition period, the Contractor shall execute the Transition Plan, taking all actions required to achieve full performance of this PWS. The awardee shall not be required to perform CLS during the transition phase-in period of 90 calendar days; as the previous incumbent will be performing CLS during this time. The new Contractor assumes full responsibility for all CLS activities on day 91 after contract award. Cutover date is date the Contractor shall assume all tasks and requirements without reliance on incumbent. Prior to cutover date the Contractor shall work with the incumbent in order to provide a seamless transition to the user. CDRL A027 DI- MGMT-81948 Management Plan (Transition Plan).

5.1.1 Transition Plan

Upon contract award the Contractor shall execute the Transition Plan. The Contractor shall deliver the draft plan as part of the proposal. The Contractor shall use the Transition Plan to track completion of milestones documenting Contractor readiness to assume the TMQ-53 Contractor Logistics Support. The Contractor will receive all Government Furnished Equipment (GFE) available during the transition period. The Contractor shall coordinate the property acceptance with the Government in advance, in order to be present for the property transfer. An inventory list shall be provided to the Government: DCMA, Administrative Contracting Officer (ACO), PCO, and Program Manager (PM).

The Contractor shall be required to accomplish the following tasks within the transition timeframe and IAW this PWS and the TMQ-53 TRD:

• Hire trained and/or train personnel to meet necessary certifications defined in this PWS, and shall provide aforementioned certifications upon request

• Establish material and logistics support, including overseas shipping arrangements

• Execute any required sub-contract agreements

• Obtain Remedy Action Request System (ARS)® or equivalent system training to train employees that will staff the Contractor’s helpdesk—training will be provided by the Government

• Receive Common Access Cards (CAC)/applicable identification from nearest military base

• Transition all GFP

• Perform and verify a complete inventory of the GFE

• Develop a spares plan and for purchasing sensors from Original Equipment Manufacturer

(OEM) as required and a OEM membership agreement in order to support all fielded systems

• Coordinate all transition phase-in matters associated with the Contractor's take-over of the CLS maintenance and logistics functions to enable the Contractor's personnel to perform the requirements specified in this contract

CDRL A027 DI-MGMT-81948 Management Plan (Transition Plan).

5.1.2 Transition of Government Furnished Property (GFP)

The Contractor shall notify the AF PM when they have made arrangements for retrieval of the GFP (pickup/load and transport) with a commercial shipping company. The incumbent Contractor shall be responsible for preparing (packaging, palletizing, etc.) GFP in their possession for shipment. Access to the previous incumbent’s facility by the commercial shipping company must be coordinated with the AF PM. The Government may direct incremental shipments since the previous incumbent will be performing CLS during this time. If there is any repair or spare parts that the previous incumbent Contractor owes to the Government, but has not yet delivered by the end of the transition phase-in period, the Contractor may coordinate with the AF PM to have such parts available for Contractor pickup and shipment, utilizing a commercial shipping company, after the transition period. The Contractor shall perform and verify a complete inventory of the GFP after the transfer of GFP from the incumbent Contractor. The Contractor shall report inventories to the AF PM. The Contractor is responsible for all efforts and material related to making the property available for use, such as payment of all transportation and installation costs, etc. CDRL A023 DI-MGMT- 80259/T Physical Inventories Report.

5.1.3 Transition Phase-In Status Reporting

During the transition phase-In, the Contractor shall conduct, at a minimum, a weekly status teleconference (day of week to be directed by PM) with the Program Management Office (PMO) and submit weekly updates to the initial Transition Plan until the transition has concluded.

Status shall include successful completion or failure to complete the transition plan milestones due during the previous week. If the Contractor fails to meet any milestones, the Contractor shall state remedial measures it is taking to ensure the transition shall not be delayed or post transition performance affected. CDRL A027 DI-MGMT-81948 Management Plan (Transition Plan).

5.2 TRANSITION PHASE-OUT

The transition phase-out period is defined as the last 90 calendar days of contract performance.

Within 90 calendar days of termination or completion of the contract, if the contract is awarded to other than the incumbent, the incumbent Contractor shall cooperate to the extent required to permit an orderly change over to the successor Contractor or organic facility, provide reasonable support to the Government and the new Contractor to ensure an orderly transition and minimize disruption to mission activities. The Contractor shall submit a Phase-Out Transition Plan. The Contractor shall continue to perform CLS through the last day of the contract. During the 90-day phase-out transition, the incumbent Contractor shall continue to manage and maintain accountability of material in the pipeline until transferred over and delivered to the awarded Contractor and accepted by the Government. The Contractor shall maintain all engineering data developed to support the requirements of this PWS and the TMQ-53 TRD, and shall include it as GFP to the follow-on Contractor or the Government. At the conclusion of the transition phase-out period, the Contractor shall provide an accounting of all GFP to the AF PM, Property Manager, DCMA, and PCO IAW applicable contractual clauses to ensure that accountability of all property has been successfully transferred to the new CLS provider IAW PCO/AF PM directions. CDRL A027 DI-MGMT-81948 Management Plan (Transition Plan); CDRL A023 DI-MGMT-80259 Physical Inventories Report.

6 PROGRAM MANAGEMENT

6.1 PROGRAM MANAGEMENT PLAN

The Contractor shall prepare and maintain a Program Management Plan (PMP) for the TMOS program which shall detail the approach and plan by which the Contractor will effectively execute all of the requirements of this PWS and the TMQ-53 TRD. The PMP will include a support concept and Spares Management Program, Repair Management Process, Transportation Plan, a Risk Management Plan, and a Staffing Plan. The Contractor shall establish a management process to ensure high quality sustainment support services throughout the term of this contract. Contractor personnel shall not divulge any information regarding files, data, reports, processing activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. CDRL A010 DI- MGMT-81797 Program Management Plan.

6.1.1 Risk Management

As part of the PMP, the Contractor shall develop, implement, and maintain a risk management process to manage technical risks (e.g., performance, requirements stability/traceability, externally imposed requirements) and management risks (e.g., cost, schedule, staffing). The Contractor shall describe processes for the following: identification of risks, proactive planning for risks, assessing risks, monitoring of risks to identify deviations from planned events, management of risk (including implementation of mitigation actions), and reporting. The Contractor shall consistently use established risk management processes to manage, mitigate, and report risks in areas where the Contractor is responsible for management activities. CDRL A010 DI-MGMT-81797 Program Management Plan; A008 DI-MGMT-80368A Status Report.

6.1.2 Security Management

The Contractor shall apply Operations Security (OPSEC) in their management of the TMOS CLS program IAW S 10-701 Operations Security, the TMOS CLS OPSEC Plan, Security Classification Guide (SCG), and the program’s Critical Information List. The Contractor shall provide OPSEC and Cybersecurity (CS) training as part of its overall training requirements for protecting sensitive unclassified information, activities, and operations during the course of the contract. The Contractor shall provide evidence of a program to be in compliance with NIST 800-171 in accordance with DFARS Subpart 204.73. CUI / For Official Use Only (FOUO) data will be processed under this contract, how data is classified will be handled by the Government on a case by case basis.

6.2 CONTRACTOR PERSONNEL

The Contractor shall identify to the Government and maintain a single point of contact (Program Manager or equivalent) with sufficient corporate authority to direct, execute and control all elements of this contract. The Contractor shall also ensure that program management personnel assigned to the program shall be available, as required, to meet program objectives. The Contractor shall at all times staff a qualified work force for the uninterrupted performance of all requirements of this PWS and the TMQ-53 TRD. The PMP shall contain a staffing plan that lists key personnel, their roles/responsibilities, certifications, qualifications, and experience. The plan shall include any cross utilization, an employee retention plan, and all subcontractor participation. This plan will be required annually, however any personnel updates and/ or changes should be submitted by email within 72 hours as an amendment to the staffing plan.

Any changes to key personnel must include equivalent qualifications and credentials of the same or substantially similar background experience. Key personnel are defined as individuals who will have a primary responsibility in accomplishing the elements of this PWS, and who are anticipated to provide the stability necessary to ensure continuity during the contractual time period of the program.

Employees who require a CAC/applicable identification to perform duties under the TMQ-53 PWS, TRD, and Sensor Specification Document (SSD), shall submit the appropriate documentation in order to obtain a CAC/applicable identification. The Contractor shall be responsible for obtaining all hardware and software required to perform duties as they relate to accessing CAC enabled content, such as Government websites. Contractor personnel shall abide by all USAF rules, procedures, and standard of conduct. CDRL A010 DI-MGMT-81797 Program Management Plan; A024 DI-MGMT-82001A/T D.O.D. Risk Management Framework (RMF) Package.

6.2.1 TMOS Third Parties

The Contractor shall interface with other TMQ-53 Contractor(s), vendors, and Original Equipment Manufacturers (OEMs) as needed to provide system parts. The Contractor shall interact with Contractors of systems that are connected to the TMQ-53 such as Joint Environmental Toolkit (JET). Also, the Contractor shall enter into an Associate Contractor Agreement (ACA) within 60 days after contract award for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the TMQ-53 which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. CDRL A010 DI-MGMT-81797 Program Management Plan.

6.3 MEETINGS

The Contractor shall conduct and/or attend any Government requested meetings in performance of this contract to include, but not limited to Integrated Product Team (IPT) meetings and helpdesk ticket meetings by teleconference, Technical Interchange Meetings (TIMs), Program Management Reviews (PMRs), Configuration Control Board (CCB) meetings, and Technical Order IPT meetings, including Validation/Verification events (see Section 10). The AN/TMQ- 53 IPT will meet (by phone) weekly for one hour and the helpdesk ticket meeting will also be held weekly (by phone) for one hour, unless the Government deems these meetings not required or required less frequently. The Contractor shall establish a call-in number. While PMR and TIM locations may vary, the Contractor shall be prepared to host all PMRs and TIMs at the Contractor’s facility and attendees shall include Government personnel and may include Government Contractor personnel. If Government personnel are unable to travel to the Contractor facility due to funding constraints or other reasons, the Contractor shall support Video Teleconferencing (VTC) through Defense Collaboration Services (DCS) or any other Government collaboration website.

For all face-to-face meetings, including VTC, the Contractor shall provide the meeting invitation and Conference Agenda to the AF PM (with a cc: to the PCO) via electronic mail (e-mail) at least 10 calendar days in advance of scheduled meetings (draft invitation and conference agenda shall be submitted 30 calendar days in advance for Government comment/revision). The Contractor shall also deliver Conference Minutes with action items identified, via e-mail to the AF PM. The final Conference Minutes shall include an attendee list and a soft-copy of any Presentation Materials. In addition, the Contractor shall provide hard copy Presentation Materials for up to ten attendees for all face-to-face meetings. For weekly IPT meetings, the Contractor shall track and provide action items that will serve as minutes from each meeting.

CDRL A001 DI-ADMN-81249B Conference Agenda; CDRL A002 DI-ADMN-81250B Conference Minutes; CDRL A003 Presentation Material; CDRL A017 DI-ILSS-80483 Spare Parts Usage Report.

6.3.1 PMRs

During the first year of the contract there will be two PMR meetings at USG CONUS locations and two at the Contractor's location, per AF PM’s directive. During the remaining years of the contract there will be one PMR each year at a USG CONUS location and one PMR each year at the Contractor's location. The Government reserves the right to move the location of any PMR from a USG CONUS location to the Contractor's location. The Contractor shall present program status, parts obsolescence issues and remedies, future year planning, current modification efforts, technical and programmatic issues, Contractor performance, deficiency reports, quality issues and risks, and any special interest items identified by the Government at PMRs in Microsoft PowerPoint format. The Contractor shall formally address the Technical Order and any applicable Time Compliance Technical Orders (TCTO). In addition, the Contractor shall brief an accumulation of the monthly Status Reports for the period preceding the PMR (since the last PMR). The Contractor’s management shall address quality issues and risks at all PMRs. The AF PM and the Contractor’s PM shall co-chair PMRs. The Government and the Contractor shall agree upon the date(s) of PMRs. Attendees may include Government and third party Contractor personnel. CDRL A008 DI-MGMT-80004A Status Report; A001 DI-ADMN-81249B Conference Agenda; A002 DI-ADMN-81250B Conference Minutes; A003 DI-ADMN-81373 Presentation Material; A013 DI-QCIC-81794A Quality Assurance Plan; A009 TM-86-01P/T Technical Order and Associated Supplemental Data.

6.3.2 TIMs

The Contractor shall support twenty-four (24) TIMs per year by teleconference. Additionally, the Contractor shall attend two (2) in person TIMs per year at a Government facility or host at their facility unless deemed not required by the Government. TIMs may be held in conjunction with PMRs if directed by AF PM. Attendees at TIMs may include Government and third party Contractor personnel. TIMs are used to discuss any technical topics related to the program (e.g.

equipment, parts support, and test/IA issues). The Contractor shall formally address Technical Orders and any applicable TCTOs. The Government and the Contractor shall agree upon the date(s) of TIMs. A001 DI-ADMN-81249B Conference Agenda; A002 DI-ADMN-81250B Conference Minutes; CDRL A003 DI-ADMN-81373 Presentation Material; A017 DI-ILSS- 80483 Spare Parts Usage Report; A009 TM-86-01P/T Technical Order and Associated Supplemental Data.

6.3.3 Interface Control Working Group (ICWG)

The Contractor shall hold ICWG meeting once a quarter unless deemed not required by the Government. The Contractor shall discuss and maintain the external and internal interfaces necessary for system operation across both systems. The Contractor shall formally address Technical Orders and any applicable TCTOs. The Government and the Contractor shall agree upon the date(s) of ICWG meetings. A001 DI-ADMN-81249B Conference Agenda; A002 DI- ADMN-81250B Conference Minutes; CDRL A003 DI-ADMN-81373 Presentation Material;

A017 DI-ILSS-80483 Spare Parts Usage Report; A009 TM-86-01P/T Technical Order and Associated Supplemental Data.

6.3.4 CCBs

The CCB consists of Government personnel from various functional areas, including a CCB Chairperson who is the approval authority for any configuration changes to the system. Upon

Government request, the Contractor shall participate in the CCB process as a technical advisor and shall attend CCB meetings. See paragraph 7.3.2 for more detail.

6.3.5 Post-Award Conference

The Contractor shall schedule and host a post award conference at its facility no later than 15 business days following contract award. The purpose of the meeting is for the Contractor to demonstrate to the Government their management procedures, provide progress assessments, discuss data delivery, review of technical and other specialty area status (including Technical Order sustainment), to introduce the Contractor team to the Government, and to establish schedule dates for near term critical meetings and actions. The Contractor shall present its PMP at the post-award meeting which defines the planned work, including all requirements established in this PWS. The Contractor shall discuss the Government’s objectives, performance requirements, contract constraints and program risks. CDRL A010 DI-MGMT-81797 Program Management Plan; A001 DI-ADMN-81249B Conference Agenda; A002 DI-ADMN-81250B Conference Minutes; CDRL A003 DI-ADMN-81373 Presentation Material; A017 DI-ILSS- 80483 Spare Parts Usage Report.

6.4 STATUS REPORTING

The Contractor shall maintain and report program status to include, but not limited to:

performance status of all AN/TMQ-53 systems, Repair Status, Product Quality Deficiency Reporting (PQDR), description of warranty work (including part numbers, quantity, date, description of failure, and estimated delivery date), impacts to maintenance philosophies, Response Metrics, Schedules, Spending Plan, status of all outstanding Information Assurance Vulnerability Alerts (IAVAs)/Time Compliance Network Orders (TCNOs), breakdown of labor category hours expended, total repair costs to date, all other costs incurred by category (including itemized shipping costs), safety incidents, shipping or customs issues, open ticket duration/aging tickets to support monitoring of program status, user feedback, Stock Availability, Mean Time To Restore Function (MTTRF) and detail of the Operational Availability rates [i.e., Fully Mission Capable (FMC), Partially Mission Capable (PMC), or Non Mission Capable (NMC), as defined in this PWS in Section 7.2]. The Contractor shall deliver the metrics, including all updates, in accordance with the CDRL for Status Reports within the first 15 calendar days of the month after the data was recorded. The Spare Parts Usage Report shall contain spare parts ordered and shipped during the reportable month, including requisition status (Open/Closed), location/site, tracking status (i.e., date and time ordered, date and time delivered). The Contractor shall report all requisitions. Additionally, the Contractor shall report breakdown of labor category hours expended for CLINs which encompass Contractor Logistics Support.

CDRL A008 DI-MGMT-80368A Status Report; CDRL A017 DI-ILSS-80483 Spare Parts Usage Report.

6.5 QUALITY ASSURANCE

6.5.1 Quality Management System (QMS)

The Contractor shall be International Organization for Standardization (ISO) 9001 certified or obtain ISO certification within six months following contract award. The Contractor shall maintain ISO certification throughout the term of the contract. The Contractor shall implement and maintain a QMS that is compliant with the ISO 9001 standard for quality management. The QMS shall apply to all activities and functions performed under this contract. The QMS shall establish policies and procedures that the Contractor shall follow and control in the performance of all work. For ISO 9001 the Contractor is responsible to maintain equivalency if standards change or are updated (e.g., ISO 9001:2015). The Government will audit the Contractor’s Quality Management System and the Contractor shall support each audit. CDRL A008 DI-MGMT- 80368A Status Report; CDRL A013 DI-QCIC-81794A Quality Assurance Plan.

6.5.2 Quality Assurance Program Plan (QAPP)

Under the tenants of the QMS, and the guidance provided under ISO 9001, the Contractor shall develop and document a QAPP. The Contractor shall deliver the QAPP within 30 calendar days of contract award and update annually thereafter. The Contractor’s quality organization shall have the autonomy and independence to implement the quality plan. The Contractor’s management shall regularly review the quality assurance plan and address quality issues and risks at all PMRs. As part of the QAPP, the Contractor shall develop, deliver, and maintain a cross-reference matrix of contract requirements to Contractor operating instructions/work instructions. The Contractor shall keep the matrix current. The Contractor shall cooperate with and provide assistance during Government quality assurance inspections and audits upon request.

The Government may provide results and findings. The Contractor shall report corrections for all discrepancies found during Government inspections, audits and surveillances in the Status Report. The Contractor shall provide, implement, and maintain a tracking system to record and track audits, surveillances, inspections, testing schedules, quality issues, and results. The Contractor shall track corrective actions, analyze trends, maintain quality assurance records/data, and any other applicable information as needed by the Government. CDRL A013 DI-QCIC- 81794 Quality Assurance Plan; CDRL A008 DI-MGMT-80368A Status Report.

6.6 TRAVEL

The Contractor shall be required to travel in support of meetings, test events, technical assistance or other on-site visits as deemed necessary. The Contractor shall submit a travel estimate, and obtain AF PM and/or PCO Authorization for specific travel on a funded line item. Authorization to travel is not an assurance of funds. The Contractor must ensure that the appropriate amount of funds are available prior to requesting authorization to travel. Travel reimbursement will be in accordance with Federal Acquisition Regulation (FAR) 31.205-46. The Contractor shall adhere to the proper procedures for Contractor personnel access to travel locations, including completion of Letters of Introduction, Visit Requests and any other travel documentation necessary for access. The Contractor shall follow all security procedures with regard to the conduct and entry of contract personnel at Government sites or any Government Contractor facility.

6.7 SAFETY REQUIREMENTS

The Contractor shall comply with all safety provisions in Appendix C. The Contractor shall protect Government property to prevent damage during the period of time the property is in the possession of the Contractor. The Contractor shall report promptly (within 1 business day of occurrence) to the PCO, ACO, and COR all available facts relating to each instance of damage to Government property. If the Government elects to conduct an investigation of the accident/incident, the Contractor shall cooperate fully and assist Government personnel until the investigation is completed. The Contractor shall submit their System Safety Program Plan (SSPP) and Accident/Incident Report IAW Appendix C and the CDRLs. CDRL A026 DI- SAFT-81626 System Safety Program Plan; A025 DI-SAFT-81563 Accident/Incident Report.

6.8 CONTRACTOR MANPOWER REPORTING APPLICATION (CMRA)

The Contractor shall report all Contractor labor hours (including subContractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance for each fiscal year (FY), which runs 1 October through 30 September. While it is possible to report any time during the FY, the Contractor shall report all data no later than 31 October of each calendar year. Contractors may direct e-mail questions to the AF ECMRA helpdesk at DoD.ECMRA.Support.Desk@mail.mil.

7 LOGISTICS SUPPORT

7.1 DEFINITIONS

7.1.1 Fully Mission Capable (FMC)

(Green) – Report FMC (Green) when system is operating normally. IAW AFI 21- 103_ACCSUP Attach. 15.

7.1.2 Partially Mission Capable (PMC)

(Amber) If any sensor necessary to report visibility, winds, altimeter setting and/or discontinuity group sensor is inoperable, report the system as PMC (Amber).Non Mission Capable (NMC) (Red) If the data acquisition unit (data logger) is inoperative, report system NMC (Red). IAW AFI 21-103_ACCSUP Attach. 15.

(Red) If any sensor necessary to report ceilings is inoperable, report the system as NMC (Red).

IAW AFI 21-103_ACCSUP Attach. 15.

(Red) If all system meteorological sensors or modems are inoperative such that the system is not providing any usable data, report the system as NMC (Red). IAW AFI 21-103_ACCSUP Attach. 15.

http://www.ecmra.mil/

7.1.3 Stock Availability

Stock Availability is the percentage of requisitions that is filled immediately from stock on hand.

7.1.4 Mission Capable (MC)

Includes FMC and PMC.

7.2 CONTRACTOR PERFORMANCE

The Contractor shall sustain the TMQ-53 in its approved configuration worldwide at an AO of 96%. The Contractor shall use the following expression in calculating the AO:

𝑨𝑨𝑶𝑶 =

𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻 𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯

(𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻 𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯+ 𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻𝑻 𝑵𝑵𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯)

Mission Capable (MC) – Includes FMC and PMC time. The formula for MC hours:

𝑀𝑀𝑀𝑀 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻 = 𝐹𝐹𝑀𝑀𝑀𝑀 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻+ 𝑃𝑃𝑀𝑀𝑀𝑀𝑀𝑀 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻+ 𝑃𝑃𝑀𝑀𝑀𝑀𝑃𝑃 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻 + 𝑃𝑃𝑀𝑀𝑀𝑀𝑃𝑃 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻 The formula for MC rate: is determined by FMC hours + PMCM hours + PMCB hours + PMCS hours/Possessed hours.

𝑴𝑴𝑴𝑴 𝑹𝑹𝑻𝑻𝑻𝑻𝑹𝑹=

𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯

𝑷𝑷𝑻𝑻𝑯𝑯𝑯𝑯𝑹𝑹𝑯𝑯𝑯𝑯𝑹𝑹𝑷𝑷 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯

Non Mission Capable (NMC) – NMC is defined as the total number of hours mission critical sensors are inoperable, as defined in 6.1.3.

Fully Mission Capable (FMC) –The formula for FMC rate: = FMC hours/Possessed hours.

𝐹𝐹𝑀𝑀𝑀𝑀 𝑅𝑅𝑅𝑅𝑅𝑅𝑅𝑅 =

𝐹𝐹𝑀𝑀𝑀𝑀 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻

𝑃𝑃𝐻𝐻𝐻𝐻𝐻𝐻𝑅𝑅𝐻𝐻𝐻𝐻𝑅𝑅𝑃𝑃 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻

All PMC and NMC hours are excluded in this formula.

Partially Mission Capable (PMC) –The formula for PMC rate:

𝑷𝑷𝑴𝑴𝑴𝑴 𝑹𝑹𝑻𝑻𝑻𝑻𝑹𝑹=

𝑷𝑷𝑴𝑴𝑴𝑴 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯

𝑷𝑷𝑻𝑻𝑯𝑯𝑯𝑯𝑹𝑹𝑯𝑯𝑯𝑯𝑹𝑹𝑷𝑷 𝑯𝑯𝑻𝑻𝑯𝑯𝑯𝑯𝑯𝑯

Stock Availability-The Contractor shall maintain a Stock Availability of 98%.

𝑃𝑃𝑅𝑅𝐻𝐻𝑆𝑆𝑆𝑆 𝐴𝐴𝐴𝐴𝑅𝑅𝐴𝐴𝐴𝐴𝑅𝑅𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝐴𝑅𝑅𝐴𝐴 = 100− (

𝑃𝑃𝑅𝑅𝑆𝑆𝑆𝑆𝐻𝐻𝐻𝐻𝑃𝑃𝑅𝑅𝐻𝐻𝐻𝐻

𝑁𝑁𝑅𝑅𝑅𝑅 𝐷𝐷𝑅𝑅𝐷𝐷𝑅𝑅𝐷𝐷𝑃𝑃𝐻𝐻

Contractor performance shall be reported in the Monthly Status Report and briefed at all PMRs.

CDRL A008 DI-MGMT-80368A Status Report.

7.3 EXCEPTIONS

If an automated observing system is operating at PMC or NMC due to an event outside the scope of the CLS provider as identified in this PWS, then the Contractor shall not include those operating hours as part of the availability formula above. The Contractor shall report actual Ao and revised AO with exceptions listed in the Monthly Status Report. Table 7-1 lists acts outside of Contractor control.

Table 7-1. Acts Outside of Contractor Control

Acts Outside Contractor Control Natural disaster (earthquake, tornado, hurricane and flooding), does not include lightning if system is properly employing lightning ground system. Acts of war (damage from weapons) Government travel time before troubleshooting begins. Government delay in implementing parts replacement/field repairs.

Government loss/destruction of the Line Replaceable Unit (LRU), does not include normal wear and tear/PMI CDRL A008 DI-MGMT-80368A Status Report A lack of available spare and/or repair funding provided by the Government.

7.4 HELPDESK REQUIREMENTS

The Contractor shall maintain and staff a helpdesk in support of the AN/TMQ-53. The purpose of the helpdesk is to provide the 557 Weather Wing (WW) Fielded Systems Support Cell (FSSC) or Program of Record (PoR) with technical support on an as needed basis and to assist users in troubleshooting, repairing and returning their system to full mission capability, including shipping spare parts when necessary. Helpdesk access shall be available 24 hours a day, 7 days a week, without cost or toll to the user or the FSSC. The Contractor shall provide helpdesk access via a single phone number and a single email address. Users or the FSSC have the discretion to either call or email the Contractor for support. The Contractor shall staff the helpdesk for live, on demand technical support during normal CONUS working hours (as a minimum, Monday through Friday, eight (8) hours per day within the hours of 6:00 a.m. to 6:00 p.m. local time at the Contractor's facility) These hours will define the regular business hours. Helpdesk personnel shall be available after working hours including weekends and holidays. The single phone access number will provide the FSSC or the user the ability to leave a voice mail message and the single email address will provide the ability to leave an email message at any time if helpdesk personnel are not available to answer immediately. CDRL A008 DI-MGMT-80368A Status Report.

7.4.1 Helpdesk Initial Call

The Contractor shall respond to trouble calls/emails referred from the FSSC or Program of Record (PoR) ie; IMDS/DPAS or from the on-site user directly. The FSSC normally receives the initial trouble call and, if necessary, will refer the call to the Contractor for complete resolution.

If assistance by the FSSC is not possible, the FSSC will direct the field to the appropriate CLS Contractor helpdesk (i.e. AN/TMQ-53 Contractor or Joint Environmental Toolkit (JET) CLS provider). Once the trouble call is referred to the Contractor, helpdesk personnel shall begin troubleshooting with the on-site user. If troubleshooting leads to a failed component or software issue, the Contractor shall either ship a replacement part or provide the appropriate software patch or image disk. Prior to issuing spare parts to a user, the Contractor shall query the TAC number database to ensure that the TAC number is under contract and that it is assigned to the unit requiring parts (see section 6.5). It is not expected that the AN/TMQ-53 Contractor will need to travel to perform troubleshooting or repair/replacement, since the on-site maintainer would perform the removal/replacement of the component based on adequate helpdesk support.

If helpdesk troubleshooting is not sufficient, on-site Contractor maintenance may be required.

The Contractor shall interface with the REMEDY or PoR. The Contractor shall ensure that Remedy/PoR contains the most up-to-date information available on all AN/TMQ-53 systems and serialized components. CDRL A008 DI-MGMT-80368A Status Report.

7.4.2 Helpdesk Management

The Contractor shall be able to obtain and maintain access to the REMEDY ARS®, or PoR system via Common Access Card (CAC) or web based access for trouble call tracking. The Contractor shall provide subject matter experts to ensure complete asset tracking and troubleshooting for all systems, spares, and to communicate with FSSC or Program of Record(PoR) (to include IMDS, DPAS) personnel and users. CDRL A008 DI-MGMT-80368A Status Report.

7.4.3 Helpdesk Response Time

The Contractor, upon receiving a trouble call (from the FSSC or the on-site user) for support during regular business hours, shall provide a response by email or phone call within two (2) hours after receipt of the request with the action the Contractor intends to take to resolve the stated problem(s). The Contractor shall respond to a message received outside the regular business hours within eight (8) hours by email or phone call with the action the Contractor intends to take to resolve the stated problem(s).

7.4.4 Troubleshooting

The Contractor shall begin troubleshooting and diagnosing the reported problem upon initial contact with the site. The Contractor shall annotate troubleshooting activity and diagnosis of the cause of the reported problem in the FSSC trouble ticket.

The Mean Time To Restore Function (MTTRF) for a fielded system shall not exceed 15 business days. MTTRF is the average elapsed time, as a result of a critical failure, required to restore a system to full operating status. MTTRF includes administrative and logistics delay times associated with restoring function following a failure.

MTTRF is defined as follows:

𝑀𝑀𝑀𝑀𝑀𝑀𝑅𝑅𝐹𝐹 =

𝑁𝑁𝑀𝑀𝑀𝑀𝑀𝑀𝑁𝑁 𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻𝐻

𝑁𝑁𝑀𝑀𝑀𝑀𝑀𝑀𝑁𝑁 𝐸𝐸𝐴𝐴𝑅𝑅𝐷𝐷𝑅𝑅𝐻𝐻

Not mission capable unscheduled (NMCU) refers to those times when the system is not mission capable because of unscheduled maintenance and associated delays.

Government delays due to tickets referred to the Government do not count towards the 15 business days.

7.4.5 Helpdesk Performance

Upon determination that spare parts are required, the Contractor shall ship parts to the user to arrive at user’s facility within 36 hours of receiving a requirement for military installations in

CONUS and within 96 hours of receiving a requirement for military installations OCONUS that accept commercial shipments. For spares required by Military Air (MILAIR) site locations, the Contractor shall deliver spares in response to helpdesk tickets within 72 hours from receipt of MILAIR shipment clearance to Aerial Ports of Embarkation (APOE)…