PWS.doc

AN/FMQ-19

Automatic Meteorological Station (AMS) Performance Work Statement (PWS)

8 December 2011 Table of Contents

INTRODUCTION

41.1 Scope

41.2 Performance Objectives

SERVICES SUMMARY

42.1 Services Summary

62.2 References

PROGRAM MANAGEMENT

73.1 Program Management Plan

73.1.1 Contractor Personnel

73.2 Meetings

73.2.1 PMRs

83.2.2 TIMs

83.2.3 CCBs

83.3 Monthly Status Reporting

83.4 Quality Assurance

83.4.1 QAPP

83.5 Travel

93.6 Safety

93.7 Transition

93.7.1 Transition Plan

93.7.2 Ramp-up (Transition) Phase

103.8 AN/FMQ-19 Third Parties

103.9 Environmental Management Systems (EMS)

LOGISTICS SUPPORT

114.1 Contractor Performance

124.1.1 Definitions

124.2 Helpdesk Requirements

124.2.1 Helpdesk Initial Call

134.2.2 Helpdesk Contact

134.2.3 Helpdesk Management

134.2.4 Helpdesk Hours

134.2.5 Helpdesk Performance

144.2.6 Tracking

144.2.7 Mock-Up

144.2.8 On-site Maintenance

144.3 Reliability and Maintainability (R&M)

144.3.1 Revised Maintenance Philosophies/Impacts

154.3.2 Obsolescence

154.3.3 System Design Changes, Enhancements and Upgrades

164.3.4 Deficiency Reporting (DR) Process

174.4 Spares

174.5 Support Equipment (SE)

184.6 Repair

194.6.1 Commercial Warranties

194.6.2 Item Unique Identification (IUID)

194.7 Configuration Management

194.7.1 Systems Engineering

204.7.2 Systems Engineering/CCB Participation

204.7.3 CCB Participation Requirements

214.8 System Manuals/TOs

224.8.1 System Manuals/TO Updates

234.8.2 Addressing Technical Publications

234. 9 Site Installation Physical Design

234.10 Government Furnished Property (GFP) Management

244.11 Special Projects

254.11.1 System design changes, enhancements, and upgrades

254.12 Training/Training Materials

254.13 Packaging, Handling, Storage, and Transportation (PHS&T)

COMPUTER RESOURCES SUPPORT

275.1 Computer Resource Support

285.2 Security Accreditation

295.3 Time Compliance Network Orders (TCNOs)

CONTRACT DATA REQUIREMENTS LIST (CDRLs)

296.1 CDRLs

31APPENDIX A SAFETY, FIRE PROTECTION AND HEALTH SPECIFICATION INDUSTRIAL SAFETY REQUIREMENTS

35APPENDIX B FOUO/OPSEC DESCRIPTION

1 INTRODUCTION

1.1 Scope

This Performance Work Statement (PWS) establishes the requirements to provide Contractor Logistics Support (CLS) necessary to sustain the AN/FMQ-19 AMS in its current configuration worldwide in accordance with the requirements as stated in the AN/FMQ-19 Technical Requirements Document (TRD). This includes, but is not limited to the Program Management, Logistics Support [Helpdesk Support, Maintenance, Spares and Repair Management, Configuration Control Board (CCB) support, Obsolescence, Systems Engineering, Government Furnished Property (GFP) Management, materials, shipping, travel, etc.], Computer Resource Support, Engineering/Contract Change Proposals (ECP/CCP), Special Projects (materials, shipping, and travel), Information Assurance (IA), 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. AN/FMQ-19 AMS were installed from January 2003 through November 2007. Any need for the contractor to travel to an overseas location to complete CLS efforts (the travel portion), will be done under a Special Project. The contractor will not perform services in or provide shipments to warzones (i.e. Iraq and Afghanistan). The Government may require the performance of special projects. Special projects may include, but are not limited to complex outages, site surveys, relocations, de-installations and engineering support. All requirements throughout this document shall apply to both CLS and Special Projects as applicable unless otherwise identified; if a requirement is not specifically identified as a Special Project requirement, it shall be accomplished as part of the CLS CLIN X001 effort, and a more specific application of the requirement may also be defined as part of any Special Project task order under X003.

1.2 Performance Objectives

The Contractor shall achieve the performance objectives in accordance with Table 2.1 of this PWS. The Contractor shall provide labor and materials necessary to plan, manage, and execute in accordance with the requirements of this PWS and the AN/FMQ-19 TRD. Requirements described in this PWS apply to the 110 fixed AN/FMQ-19 AMS systems (including any field sensor groups or discontiniuities) located on 106 Air Force (AF) and Army bases worldwide, including all site expansions, modifications and upgrades underway or scheduled for the current fielded systems. If the Mockup is relocated to another Contractor location, the Contractor shall be required to update the software to the current configuration. These services are not mission essential in accordance with the DODI 3030.37, dated 1/26/1996.

2 SERVICES SUMMARY

2.1 Services Summary

DCMA is the administrative office for this contract and DCMA will utilize input from the Program Manager before making quality assurance decisions (including inspection and acceptance). There will also be a Contracting Officer’s Representative (COR), assigned by the Procuring Contracting Officer (PCO), for any Special Project Tasks that may have inspection/acceptance at destination. Defense Contract Management Agency (DCMA) will audit the contractor’s processes to ensure they are in-place and will use the data from the contractor inspection reports to assess contractor performance. If the contractor does not have processes in place or meet the standards listed, then the contractor shall establish a corrective action plan to correct the deficiency in the manner identified by DCMA. A Contracting Officer’s Representative (COR) assigned by the Procuring Contracting Officer (PCO) may also assist if there are any Special Project tasks which have inspection/acceptance at destination.

Table 2.1

2.2 References

Air Force (AF) Policy Directive 33-2 C4 Systems Security

Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013-5(d)

DOD Directive 8500.1 Information Assurance

DOD Directive 8510.01 DOD Information Assurance Certifcation and Accrediation Process (DIACAP)

DOD Instruction 8581.01 Information Assurance for Space Systems

Federal Acquisition Regulations (FAR) Part 31.205-46

MIL-STD-130N DOD Standard Practice for Identification Marking of US Military Property

MIL-STD-38784 Standard Practice for Manuals, Technical: General Style and Format Requirements

Technical Order (TO) 00-5-3 AF Technical Order Lifecycle Management

Technical Order (TO) 00-5-15 Air Force Time Compliance Technical Order Process

TO 00-25-195 Source, Maintenance, and Recoverability Coding

TO 00-35D-54 USAF Defiency Reporting, Investigation, and Resolution

Table 2.2

3 PROGRAM MANAGEMENT

3.1 Program Management Plan

The contractor shall prepare and maintain a Program Management Plan (PMP) which will detail the processes and programs by which the contractor will effectively execute the requirements of this PWS. The PMP will include an organizational chart of all contractor employees, consultants and subcontractors involved in the effort. (CDRL A001)

3.1.1 Contractor Personnel - The contractor shall at all times staff a work force for the uninterrupted performance of all requirements of this PWS. The PMP shall contain a personnel section that lists key personnel, their roles/responsibilities, and experience. (CDRL A001)

3.2 Meetings

The contractor shall conduct and/or attend meetings in performance of this contract to include, but not limited to, Integrated Product Team (IPT) meetings (by teleconference), Technical Interchange Meetings (TIMs), Program Management Reviews (PMRs), Configuration Control Boards (CCBs), site surveys, and on-site support between contractor and the government to resolve complex system issues or deficiencies. The FMQ-19 IPT will meet (by phone) weekly for one hour unless the Government deems these meetings not required or required less frequently. While PMR and TIM locations may vary, the contractor will be prepared to host all PMRs and TIMs at the contractor’s facility and attendees shall include Government and may include Government contractor personnel.

For all face-to-face meetings, the contractor shall provide the meeting invitation and agenda to the Government via electronic mail (e-mail) at least five business days in advance of scheduled meetings (draft invitation and agenda shall be submitted 10 business days in advance for Government comment/revision). The contractor shall also deliver meeting minutes via e-mail to the Government. For weekly IPT meetings, the contractor shall track and provide action items that will serve as minutes from each meeting. (CDRL A003, A009)

3.2.1 PMRs - The Contractor shall hold PMRs quarterly during the first two years of the contract. If after the first year of the contract the Government determines that semi-annual PMRs will suffice, then the Contractor may only hold semi-annual PMRs in the second year. After that, the Contractor shall hold PMRs twice a year unless deemed not required by the Government. Post-Award Conference that the Administrative Contracting Officer (ACO) holds in accordance with FAR 42.302(a)(3) and initial Guidance Conference shall be held no later than two weeks following contract award (see paragraph 4.8). The contractor shall present program status, parts status, technical and programmatic issues at PMRs in Microsoft PowerPoint format with hard copies of the slides provided to each person in attendance. An accumulation of the monthly status reports shall be briefed at the PMR for the period preceeding the PMR (since the last PMR). The PMRs are co-chaired by the Government and Contractor’s Program Manager (PM). The date(s) of PMRs shall be agreed upon by the Government and the Contractor. (CDRL A015)

3.2.2 TIMs - The contractor shall hold TIMs twice a year unless deemed not required by the Government. TIMs are used to discuss technical issues regarding equipment and parts support issues. The date(s) of TIMs shall be agreed upon by the Government and the Contractor.

3.2.3 CCBs - CCBs may be held in conjunction with a PMR, TIM, or as a stand alone meeting, which may be conducted face-to-face or by teleconference (as deemed appropriate by the Government). The System Program Management (SPM) office currently leads the CCB, see paragraph 4.7; however, this may be delegated by the SPM to the System Sustainment Management (SSM) office during the contract period.

3.3 Monthly Status Reporting

The contractor shall maintain and report program status data to include: monthly location/ operational status of all FMQ-19 Systems and shall provide detail of the availability UTR rates [i.e., Fully Mission Capable (FMC), Partially Mission Capable (PMC), or Not Mission Capable (NMC) as defined in this PWS at paragraph 4.1], Spares Usage, Repair Status, Response Metrics, Schedule, Spending Plan, breakdown of labor category hours expended, open ticket duration/aging tickets to support monitoring of program status with updates delivered to the government via monthly status reports following the month for which the data represents. Spares usage report shall contain spare parts ordered during reportable month including: requisition status (Open, Closed), location/site, tracking status (i.e., date and time ordered, date and time delivered). All open requisitions will be reported. (CDRL A002, A005)

3.4 Quality Assurance

The Contractor shall deliver a Quality Assurance Program Plan (QAPP) within 30 days of contract Award and 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. (CDRL A013)

3.4.1 QAPP - 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 matrix shall be kept current. The contractor shall provide assistance during Government quality assurance inspections and audits upon request. The contractor shall report corrections for all discrepancies found during Government inspections, audits and surveillances. The contractor shall provide, implement, and maintain a tracking system to record and track audits, surveillances, inspections, testing schedules, and results. The contractor shall track corrective actions, analyze trends, and maintain quality assurance records and data (CDRL A013). Defense Contract Management Agency (DCMA) shall oversee Quality Assurance for all services except any Special Project Tasks that may have inspection/acceptance at destination.

3.5 Travel

As part of the day-to-day CLS effort under CLS CLIN X001 (which excludes Special Projects that may be awarded as tasks under CLIN X003), the contractor may travel as they deem necessary to sustain the AN/FMQ-19 AMS. The determination to travel and the associated costs of day-to-day travel are the Contractor’s responsibility. Such CLS travel may include efforts such as getting a Common Access Card for the IA or helpdesk personnel at the closest Air Force Base as they begin IA network support, or a Contractor decision to travel to a base for what is regarded as routine helpdesk assistance and is currently handled by telephone. Technical assistance (i.e. complex outage requiring on-site maintenance) or other on-site visits not related to the day to day CLS effort under CLIN X001 (i.e. site survey or unique training requirements) may be required as part of a Special Project Task Order as identified in the Special Project paragraph 4.11 of this PWS. Travel for Special Project Task Orders will be negotiated separately for each specific Task Order. Travel for CCB test efforts or validation/verification of a TO update may be required as listed in the CCB and TO paragraphs of this PWS, and any related costs shall be part of the CLS CLIN X001 firm fixed price. The contractor shall be responsible for ensuring that the proper procedures for contractor personnel access to travel locations are adhered to by the contractor to include but not limited to completion of Letters of Introduction, Visit Requests and other travel documentation necessary for access. (CDRL A001)

3.6 Safety

The contractor shall comply with all safety provisions, in Appendix A. (CDRL A017, A018)

3.7 Transition

3.7.1 Transition Plan - The Contractor shall have up to 30 days from date of contract award to transition, ensuring an orderly transition from the incumbent(s) without impact on system operations. No other interface with the incumbent(s) is required by the Government beyond what is stated in paragraph 3.8. This transition shall be accomplished in accordance with the Transition Plan, which is incorporated into the contract. The Transition Plan shall include a Staffing Sub-Plan. It shall detail how employees meet the technical requirements of this PWS. The Staffing Plan shall reflect strategy regarding personnel recruiting, retention, and clearances. 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 FMQ-19 CLS program. The Contractor shall reiterate as part of the PMP, the CLS Transition Plan which is contractually incorporated. (CDRL A001)

3.7.2 Ramp-up (Transition) Phase - At a minimum, the following tasks shall be accomplished within the initial ramp-up phase of the program:

a. Upon contract award the contractor shall implement the CLS Transition Plan. Transition from each incumbent shall be completed no later than 30 days following contract award, as identified in the contractor’s transition plan. Access to each incumbent’s facilities (for GFP pick-up) must be coordinated with the Program Manager (who will interface with the Contractor’s ACO and with the incumbents’ ACOs). The Contractor shall then notify the Program Manager when arrangements have been made for retrieval of the GFP with a commercial shipping company and the Program Manager will in turn notify DCMA. The GFP may be shipped in incremental shipments. Within the 30-day ramp-up, the contractor will receive all GFP available. If there are any repair or spare parts that the incumbent contractor(s) owe to (but have not yet delivered to) the Government by the end of the 30-day ramp up period, the Contractor may coordinate (with the Program Manager and DCMA) to have such parts available for Contractor pickup/shipment (utilizing commercial shipping company) after the 30-day period. Such parts may include quantities of items that were not identified on the GFP list (e.g., parts that the Government acquired from the incumbent contractors after the GFP list was created). The Contractor shall perform and verify a complete inventory of the Government Furnished Property (GFP) after the Contractor obtains the GFP from the incumbent’s facility. Contractor is responsible for all efforts and material related to making the property available for use, such as payment of all transportation, installation or rehabilitation costs. The inventories shall be reported to the Government: DCMA, Administrative Contracting Officer (ACO), PCO, and PM. The contractor shall schedule inventories with the PM and DCMA in advance. Cutover date is date the Contractor shall assume all CLS and this begins after this 30 day ramp-up/transition phase. Prior to cutover date the contractor shall make all necessary efforts to provide a seamless transition to the user.

b. Receive REMEDY( training at Air Force Weather Agency (AFWA) to train employees that will staff the Contractor’s Helpdesk.

c. IA personnel receive Common Access Cards (CAC) from nearest military base (OO-ALC sponsored). Personnel must be eligible for a CAC and have CompTIA Security + certification. IA personnel will be guided through establishing BOMGAR (or whatever system the Government is using for remote maintenance and Internet connection) accounts.

d. Conduct an AN/FMQ-19 Post Award Conference

e. The Contractor will not be performing CLS during the ramp up period; the incumbents will be performing CLS during this time.

3.8 AN/FMQ-19 Third Parties

The contractor shall interface with other AN/FMQ-19 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 FMQ-19, such as Joint Environmental Toolkit (JET). The current FMQ-19 information is displayed on observer and forecaster monitors via a MOXA box attached to the Terminal Data Acquisition Unit. The MOXA box is currently managed under a separate contract with the JET provider; however, it may fall under the FMQ-19 portfolio at some point in the future; at such time the changes clause may be used to add MOXA CLS effort to this contract. (CDRL A001)

3.9 Environmental Management Systems (EMS)

The contractor shall provide the below listed EMS information before access to federal property will be considered:

A. The individual data elements required from the contractor: a list of hazardous material to be brought on the installation.

B. The specific format and method by which the contractor should deliver the data: Contractor shall provide (email is acceptable) the Material Safety Data Sheets (MSDS) for hazardous material brought on the installation.

C. The interval (e.g. monthly, quarterly, annually, etc.) at which the contractor must report data: The contractor shall provide the MSDS 7 calendar days in advance, but in all cases, the MSDS must be provided before entering the installation.

D. The installation office (if applicable) to which the contractors must deliver the specified EMS support data: The MSDS sheets must be provided to the Program Office and if specifically requested, a copy will be provided to the installation.

E. EMS training requirements: The contractor personnel working on a Government installation must complete Government provided initial EMS awareness level training prior to beginning work on a Government installation. The EMS training requirement is further explained below.

F. The Government installation office responsible for providing the EMS training: The Program Office is responsible for ensuring compliance and providing the training at PMRs. On a case by case basis, the Program Office may delegate the responsibility of giving this training to the Government installation to be visited.

G. The amount of time the training requires: The Contractor shall anticipate that training will require 15-30 minutes.

H. The specified time period after either the training requirement is placed on contract or a new contract employee begins work on the Government installation by which the employee will require initial EMS awareness level training: Once the requirement of EMS training is placed on contract, all contractor’s employees shall require the training before beginning work on a Government installation in conjunction with this program.

I. The method and by which the delivery of the awareness level training shall be made (i.e. on-line, mass briefing(s), individual review of slides, etc.) and the manner by which the contractor will document the employee initial EMS awareness level training will be made: Refer to letter F above for the method and format by which delivery of the awareness level training will be made. The Contractor will maintain a record of employees that have received the EMS training in a format of their choosing.

J. The EMS training requirement may also be met if the contractor employee has received EMS training for a Government installation access in conjunction with a different program and documentation is provided to the Program Office.

4 LOGISTICS SUPPORT

4.1 Contractor Performance

The contractor shall sustain the AN/FMQ-19 in its current configuration worldwide at an availability UTR for the critical path of 96% or 85%* depending upon which tier is identified in each specific CLS Task Order. The UTR is expressed as:

Availability UTR = (total operating hours – total down-time)/(total operating hours) *Note: Availablility will be tiered in accordance with the following table:

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

4.1.1 Definitions –

4.1.1.1 The critical path is defined as that data most important to the Meteorological Aviation Report (METAR). That data includes: temperature, dew point, wind speed and direction, present weather, cloud cover and heights, visibility, barometric pressure, lightning, and runway visual range (RVR).

4.1.1.2 If an automated observing system is reporting all critical, usable METAR data, report system as FMC (green).

4.1.1.3 If an automated observing system is reporting some critical, usable METAR data, report system as PMC (amber).

4.1.1.4 If an automated observing system is reporting no critical, usable METAR data, report system as NMC (red).

4.1.1.5 If an automated observing system is operating at PMC or NMC, this shall be calculated as downtime in the availability UTR expression as identified in paragraph 4.1 of this PWS.

4.1.1.6 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, i.e. a separate contract with the base makes a change that has an effect on METAR data reporting or Airfield Maintenance is unable to make repairs due to other priorities, then the Contractor shall not include those operating hours as part of the availability formula above. The Contractor shall report this as part of the Monthly Status Report. The event may become a Special Project as part of the Government’s corrective action. (CDRL A002)

4.2 Helpdesk Requirements

The Contractor shall provide a help desk which shall be manned during regular business hours, Monday through Friday, eight (8) hours per day within the hours of 6:00 a.m. to 6:00 p.m. local standard time at the Contractor's facility, to provide the AFWA’s Field Systems Support Center (FSSC) with technical support on an as needed basis.

4.2.1 Helpdesk Initial Call - The initial trouble call should be received at the AFWA FSSC REMEDY( Action Request System (ARS®). AFWA maintains 24/7 customer support. The FSSC REMEDY( is for receipt of initial trouble call and pass-through to Contractor for complete resolution. If assistance by the AFWA FSSC is not possible, the AFWA FSSC will direct the field to the appropriate CLS contractor helpdesk (i.e. FMQ-19 CLS Contractor or Joint Environmental Toolkit (JET) CLS provider). Once the field contacts the FMQ-19 AMS Contractor’s helpdesk, the helpdesk will attempt to troubleshoot with the on-site Government maintainer. Troubleshooting will lead to a failed component or software issue, requiring the FMQ-19 AMS Contractor to either ship a replacement part and accomplish the repair or to provide the appropriate software patch or repair. It is not expected that the FMQ-19 AMS 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. As mentioned in paragraphs 3.5 and 4.2.8, the Contractor shall travel as they deem necessary to sustain the AN/FMQ-19 AMS, given that the Contractor shall perform on-site maintenance in the event that helpdesk troubleshotting is not sufficient to resolve the helpdesk ticket. The contractor shall interface with the REMEDY( database.

4.2.2 Helpdesk Contact - The Contractor shall ensure that all contact between the user and the Contractor is recorded in the AFWA FSSC REMEDY( trouble ticket database system regardless of whether the contact is originated through the AFWA FSSC or direct from the user to the contractor. The Contractor shall work in cooperation with the FSSC REMEDY( database, to receive, respond and report on call logs, equipment/parts deliveries and user support issues.

4.2.3 Helpdesk Management - The Contractor shall maintain a REMEDY( Database Manager and an adequate number of subject matter experts to ensure complete asset tracking and troubleshooting for all systems and spares, and to interface with the FSSC database personnel for total asset visibility of the AN/FMQ-19 system.

4.2.4 Helpdesk Hours - Contractor support beyond eight (8) hours per day, five (5) days per week, shall be provided on an as needed basis by Contractor representative(s) who are familiar with the AN/FMQ-19 weather components. The Contractor shall establish both an email account and a toll free telephone number for FSSC personnel to use in contacting the Contractor’s Help Desk. Upon receiving a request for service during regular business hours, the Contractor shall provide a response back to the FSSC by email or phone call within three (3) hours after receipt of the request with the intended action to be taken to resolve the stated problem(s). A message received outside the regular business hours, shall be responded to within twelve (12) hours by email or phone call with the intended action to be taken to resolve the stated problem(s). The Contractor shall provide system administration services to FSSC personnel on an as needed basis. System administration support shall be provided upon AFWA FSSC or Program Manager request to aid on-site operator/maintenance personnel in reloading software after failures occur in the data processing subsystem and/or when new software must be loaded to add capabilities and/or to provide additional virus protection.

4.2.5 Helpdesk Performance - The Contractor shall provide spares for all FMQ-19 parts to operating locations within 2 business days of receiving a requirement for military installations in the continental United States (CONUS) and within 4 business days to installations outside the continental United States (OCONUS). For spares required by MILAIR site locations, the Contractor shall deliver spares in response to helpdesk tickets within 2 business days from receipt of MILAIR shipment clearance to AF aerial ports (see PWS para 4.13 for shipping). The Contractor shall provide (as necessary) spares on an off-the-shelf basis for shipment to worldwide locations upon request from the Government. The contractor shall provide instructions for return shipments from all FMQ-19 locations.

4.2.6 Tracking - The Contractor shall utilize the FSSC provided REMEDY( trouble ticket management system, via web-based login, to maintain the maintenance database “call log”.

The Contractor shall interface with the AFWA FSSC to maintain call/contact logs to include as a minimum: contact information, date of contact, subject, a reference (i.e., service ticket number), description of problem, description of action taken, action taken date, and status (Open/Closed) information. The Contractor shall document all technical assistance and maintenance actions tracked through to complete resolution, to include the delivery, installation and system functional check of replacement parts if required. The helpdesk tracking information shall be reported in the monthly status report. (CDRL A002)

4.2.7 Mock-Up - The Contractor shall utilize a scaled (mock-up) replication of an AN/FMQ-19 AMS to support Helpdesk analysis and troubleshooting of server and application software and sensor problems. The contractor shall maintain the mock-up AN/FMQ-19 in accordance with the common fielded systems standards, to include the current software version and standard hardware configuration.

4.2.8 On-site Maintenance - The Contractor shall perform on-site maintenance in the event that helpdesk troubleshooting is not sufficient to resolve the helpdesk ticket. If it is determined by the PCO that the Contractor has exhausted all measures to provide helpdesk support, and that both helpdesk support and CLS on-site maintenance is no longer appropriate for the situation, then the Government will determine if this situation is a result of the Contractor not being able to meet a CLS requirement or if a Special Project Task (e.g. in accordance with paragraph 3.2, 4.1.1.6, 4.2.1, or 4.3.3) is required. Refer to PWS para 3.5 for Travel Authorization.

4.3 Reliability and Maintainability (R&M)

The Contractor (by using data available via REMEDY( or like data system provided by Air Force, or contractor data) shall provide reliability and maintainability data (such as parts usage) for the AN/FMQ-19 LRUs supported under this contract. This includes tracking operational availability of the FMQ-19 and Critical Mean Time between Failure (MTBF) along with other specified failure factors. If new or revised hardware components are suggested for introduction to the AN/FMQ-19, impacts to R&M will be evaluated and reported to the Government for review by the CCB, as identified in paragraph 4.3.3. (CDRL A002)

4.3.1 Revised Maintenance Philosophies/Impacts - The Contractor shall scrutinize spare parts usage, user input, help desk data and/or other reliable R&M data as discussed above to determine if changes are required to the maintenance philosophies of the AN/FMQ-19 AMS Systems. The Contractor may make recommendations to the Government about Line Replaceable Unit (LRU) or component replacement, but should expect that only obsolescence will drive a change or modification to the system. (CDRL A004) In addition, if new or revised hardware components are suggested for introduction to the AN/FMQ-19 AMS Systems, resulting impacts to the maintenance philosophies shall be examined and reported immediately to the Government for review by the CCB. (CDRL A002, CDRL A007)

4.3.2 Obsolescence - The Contractor shall identify all obsolescence for the AN/FMQ-19 AMS for review/approval by the CCB, see paragraph 4.7.1 for Engineering Change Proposal (ECP) process. Obsolescence originates from the Contractor as part of their configuration management responsibility under CLS (not a Special Project). As part of the CLS CLIN X001, the Contractor shall provide the Government an ECP for all proposed configuration changes; this includes ECPs that identify special project type of effort, which may result in a special project task requirement. The Government will then conduct a CCB to discuss and accept, modify, or reject the change. The coordination and concurrence of the CCB shall be required for all configuration changes and modification actions. Upon CCB approval (including any necessary demonstration/acceptance tests as required in the CCB paragraph(s) of this PWS) of a change or modification due to obsolescence, the Contractor shall procure and integrate proposed commercial items for obsolescence and distribute to the various sites based on defined priorities for availability. The contractor shall provide data for technical identification of items for maintenance support considerations; preparation of item identification for the purpose of assigning Part Numbers and/or National Stock Numbers (NSNs), as needed; review for item entry control; standardization review for potential interchangeability and substitutability; item management coding; preparation of allowance/issue lists; and Source, Maintenance, and Recoverability (SMR) coding (TO 00-25-195). The Contractor shall provide all necessary TO updates that arise from the change or modification of the system due to the obsolescence (including requirements as listed in the TO paragraph of this PWS). The Contractor has the ability to choose to replace through attrition or through complete field replacement of an obsolete item, as long as the Government’s identified minimum availability/FMC rates are met for the period. Although the government will provide parts shipping history and known obsolescence issues (as identified in the Deficiency Reporting documentation), the Contractor should understand that obsolescence and catastrophic repairs can occur. Special projects CLIN X003 includes scope for deficiency report corrective actions that don’t fall under the scope of CLS CLIN X001 (such as lightning detection sensor relocation). At the beginning of the contract period, LRUs are expected to only be replaced with an alternate part (approved by CCB) only as a result of obsolescence, not as upgrades or modifications. (CDRL A004, A006, A014, A016)

4.3.2.1 Obsolescence Replacement - The Contractor shall, as part of the CLS sustainment effort, present to the CCB any recommendation of replacing obsolescence through attrition or if a system-wide replacement is more appropriate to maintain FMC availability rates. Most obsolescence parts are assumed to be able to be replaced in the field by attrition. The visibility sensor is the only known part known at this current time, operating below the MTBF rate.

4.3.3 System Design Changes, Enhancements and Upgrades - As part of the CLS CLIN X001 effort, the Contractor shall identify potential system design changes, enhancements and upgrades for the AN/FMQ-19 System for review by the CCB through an ECP. Potential system design changes, enhancements and upgrades can originate by the Contractor or the Government. This applies to both hardware and software. These would be potential special project tasks, not obsolescence issues. The coordination and concurrence of the CCB shall be required before any such changes, enhancements, and upgrades (including resulting configuration changes and modifications) are identified as a Special Project Task Requirement by the Government; such resulting Special Project Task Requirements will become contractual only upon negotiation and award of a Special Project Task Order under CLIN X003. An awarded Special Project Task Order may include the requirement for the contractor to furnish and integrate items for system/program enhancement and distribute to the various sites based on defined priorities that are identified in the specific task order. See paragraph 4.11. (CDRL A004, A007).

Also as part of the CLS CLIN X001 effort, the contractor shall provide data for technical identification of items for maintenance support considerations; preparation of item identification for the purpose of assigning Part Numbers and/or National Stock Numbers (NSNs), as needed; review for item entry control; standardization review for potential interchangeability and substitutability; item management coding; preparation of allowance/issue lists; and Source, Maintenance, and Recoverability (SMR) coding (TO 00-25-195). The contractor shall provide all necessary TO updates and assist with TCTOs that arise from the change or modification of the system due to the system design change, enhancement, or upgrade (including requirements as listed in the TO paragraph of this PWS). TCTOs have a specific format and distribution process and must be coordinated and routed through the OO-ALC program office. (CDRL A004, A006, A014, A016)

4.3.4 Deficiency Reporting (DR) Process - The Contractor shall be a member of a joint Contractor and Government team which identifies, defines, and collects the data required for entry into the Joint Deficiency Reporting System (JDRS). The Contractor shall research the cause and present potential solutions for each DR. A DR can originate from a field unit, AFWA, or the program office inputing data in JDRS. Each DR gets assigned to a Government action point for resolution. The joint team will assume the responsibility for collecting and categorizing the types of deficiencies, issues and problems that impact the program. The contractor shall utilize its own internal DR tracking system. The Government will have the final authority and responsibility for DR data collected by the team and input in the JDRS. The team shall also have the capacity to submit suggestions for program deficiency improvements to include technology insertion initiatives. The Contractor shall brief DRs at the PMRs and report status of open DRs in the Monthly Status Report. (CDRL A002)

4.3.4.1 Existing DRs - As part of this effort, the Contractor assumes responsibility for resolving or assisting to resolve the existing FMQ-19 AMS DRs.

1. JM4885-10-0001 False Precip Reports, Corrective Action: Special Project

2. JM4885-11-0001 Visibility Output Data Too High during dust storms at Al Udeid, Corrective Action: Special Project

3. JM4885-11-0002 Remote Maintenance Monitoring not accessible, Corrective Action: Expect BOMGAR to correct

4. JM4885-11-0003 Autodetect Runway Lights, Corrective Action: Special Project

5. JM4885-11-0004 Multiple Runway Switch, Corrective Action: Special Project

6. JM4885-11-0005 AC Power Supply, Corrective Action: Special Project

7. JM4885-11-0006 Prevailing Visibility Does Not Match Observer, MTBF does not meet TRD, Corrective Action: Obsolescence replacement by FMQ-19 CLS provider under CLIN X001

8. JM4885-11-0007 False Tips from Precip Bucket, Corrective Action: Special Project

9. JM4885-11-0008 Lightning Sensor Under Reports Lightning, Corrective Action: Special Project

4.4 Spares

The Contractor shall develop and maintain a support concept and implement a spares management program. As part of transition, the current FMQ-19 spares inventory shall be obtained (by the Contractor) from each incumbent contractor’s site and relocated to the Contractor’s facility as Government Furnished Property (GFP); access to the incumbent’s facilities (for GFP pick-up) must be coordinated with the Program Manager (who will interface with the Contractor’s ACO and with the incumbents’ ACOs). If the Contractor is an incumbent and any portion of the spares are already located at the work site for this contract, then the spares shall remain at that site. The contractor shall ensure that sufficient spares are available to issue to field users in response to system failures to meet required availability as specificed in PWS para 4.1. Contractor is responsible for all efforts and materials related to keeping the property available for use, including rehabilitation costs. The spares management program shall be documented in the PMP. The Contractor shall comply with all contractual clauses related to GFP. The contractor shall maintain a listing of all spares accountable to the contractor. The Contractor shall be responsible for managing all spares and consumables and shall determine proper inventory levels needed to meet Government operational availability/FMC rates. All shipments of spares (unless the spare is a consumable that doesn’t require a return shipment) shall include pre-paid shipping labels and reusable packaging to allow the users to return the spares to the contractor in the same reusable container packaging. Spares which fail upon initial installation will be returned to the contractor for repair (as part of the existing CLS X001 effort); this report of failure will be sent to the Government for record and Product Quality Deficiency Reporting (PQDR) if required. Any additional spares acquired by the Contractor shall be managed by the Contractor as part of the spares management program within the CLS CLIN X001 (and not as a Special Project Task); this includes all spares ordering and procurement activity, as well as the procurement and integration of CCB approved commercial items (due to obsolescence). The Contractor is allowed to maximize performance by being empowered to use a best value approach to meet (through sparing and/or repairing) contract demands. See paragraph 4.10. The contractor shall also provide a running summary of total spares costs incurred since inception of the contract. The purpose of the attached Configuration Parts List (attachment 1) is to identify the parts that make up the current configuration that shall be sustained under this contract. If any transferred GFP is identified on the attached Configuration Parts List, it may be used in the performance of this contract without CCB approval even if it is not marked with the Original Equipment Manufacturer’s (OEM) part number or OEM’s name (as long as it has the same nomenclature and incumbent part number). For such components and for any other components not highlighted on the attached Configuration Parts List, a specific OEM is not required for performance of the CLS effort, since the item is a common, commercial item available from many commercial sources, and the description on the parts list is a commercial item description, which includes the details that the contractor must comply with during performance of the effort without need for going through the CCB. (CDRL A002, A005)

4.5 Support Equipment (SE)

The Contractor shall develop and maintain a support concept and implement a support equipment management program. As part of transition, the current FMQ-19 SE inventory shall be obtained from each incumbent contractor’s site and relocated to the Contractor’s facility as GFP; access to incumbents’ facilities (for GFP pick-up) must be coordinated with the Program Manager (who will interface with the Contractor’s ACO and with the incumbents’ ACOs). If the Contractor is an incumbent and any portion of the SE is already located at the work site for this contract, then the SE shall remain at that site. Contractor is responsible for all efforts and materials related to keeping the property available for use, including rehabilitation costs. The support equipment management program shall be documented in the PMP. The Contractor shall comply with all contractual clauses related to GFP. The Contractor shall be responsible for managing all SE. The Contractor shall maintain a listing of spare common and peculiar support/test equipment required to maintain the AN/FMQ-19. If new or revised hardware or software components are introduced to the AN/FMQ-19, the impact to support equipment requirements will be examined, quantified and reported to the Government for review by the CCB. All shipment of support equipment shall include pre-paid shipping labels and reusable packaging to allow the users to return the support equipment to the contractor in the same reusable container packaging. Any and all support equipment received (from the field, OEMs, etc.) shall be inspected for serviceability and disposition for deficiency reporting, repair, or disposal. All SE ordering and procurement activity, including repairs shall be performed and managed by the contractor. One full complement of SE will remain with the Government furnished mock-up. This set will also be provided as GFP.

4.6 Repair

The Contractor shall establish a process for managing the repair of all AN/FMQ-19 AMS repairables. The Contractor shall be responsible for managing all repairs needed to meet Government operational availability/FMC rates. The Contractor shall manage this process for all operational AN/FMQ-19 AMS locations. The repair management process shall be documented in the PMP. If new or revised hardware components are introduced to the FMQ-19, the contractor shall develop a repair process for these items, as necessary. Physical repair and maintenance is primarily at the component level, since Government personnel will conduct the actual removal and replacement of the components of the system, unless the Contractor deems it a complex outage needing their assistance. Special tools and/or test equipment necessary to accomplish maintenance and ensure serviceability of items shall be furnished by the contractor. Special tools and/or test equipment shall not be furnished by the Government. The contractor shall also provide a running summary of total repair costs incurred since inception of the contract. (CDRL A001) The Contractor shall determine when, through maintenance troubleshooting efforts, it is necessary to issue replacement parts for the repair of an AN/FMQ-19. Upon determination that spare parts are required, the Contractor shall ship part(s) to the user’s location. No fees shall be charged to the user since shipping is part of the CLS effort. All shipments of replacement parts shall include pre-paid shipping labels and reusable packaging to allow the users to return the failed part(s) to the Contractor in the same reusable container packaging. Any and all parts received (from the field, OEMs, etc.) shall be inspected for serviceability and disposition for deficiency reporting, repair, or disposal; disposition cannot occur unless approved by DCMA. In addition, if new or revised hardware components are introduced to the AN/FMQ-19 AMS, impacts to supply support channels and sparing dynamics shall be examined and reported to the Government for review by the CCB. (CDRL A002)

4.6.1 Commercial Warranties - The Contractor shall pass any commercial warranties obtained from the OEM and/or vendors on to the Government for all repair components; but as a minimum, the warranty shall not be in contravention to Federal acquisition law (including the prohibition against indemnification by the Federal Government). The contractor shall support and investigate Product Quality Deficiency Reports (PQDR) in accordance with T.O.