ATT_3_RVA_CLS_PWS.pdf

Attachment 3 i of iv

REMOTE VISUAL ASSESSMENT (RVA)

CONTRACTOR LOGISTIC SUPPORT (CLS)

PERFORMANCE WORK STATEMENT (PWS) FOR

AFNWC

1 May 2014

DRAFT

ii of iv

Table of Contents

1 Performance Work Statement Introduction

1.1 Purpose

1.2 Background

1.3 RVA CLS Overview:

2 Applicable Documents

3 Contract Requirements

3.1 Performance Requirements

3.1.1 Reliability (IAW CDRL A019)

3.1.2 Availability (IAW CDRL A019)

3.1.3 Maintainability (IAW CDRL A019)

3.2 Sustainment of the RVA system

3.2.1 RVA System Troubleshooting and Failure Analysis

3.2.1.1 Organizational Notification of RVA System Failure (IAW CDRL A024)

3.2.1.2 Failure Determination (IAW CDRL A024)

3.2.1.3 Failure Resolution

3.2.1.3.1 Immediate Restoration of Service

3.2.1.3.2 Manual Updates (IAW CDRL A029 and A032)

3.2.1.3.3 Verification (IAW CDRL A025)

3.2.1.3.4 Government Coordination (IAW CDRL A010)

3.2.1.3.5 Improve RVA System Performance (IAW CDRL A014 and A026)

3.2.1.3.6 Maintenance Database Update (IAW CDRL A026)

3.2.1.3.7 Software Maintenance (IAW CDRL A020)

3.2.1.3.8 RVA Operations Center (IAW CDRL A018)

3.2.1.3.9 Contractor Statement of Work (CSOW) (IAW CDRL A004)

3.2.1.3.10 Fault Tree Analysis (IAW CDRL A017)

3.2.2 RVA System Assessment (IAW CDRL A027)

3.2.3 RVA System Programmed Maintenance

3.2.4 Hours of Operation

3.2.4.1 Hours of Operation

iii of iv

3.2.4.2 Down Day/Base Closure/Exercises/Inspections

3.2.4.3 Recognized Holidays

3.2.4.4 Rapid On-Site Technical Support

3.2.4.5 On-Site Response

3.2.4.6 RVA System Supply Chain Management (IAW CDRL A016 and A010)

3.2.4.7 Spares Use & Inventory (IAW CDRL A027)

3.2.4.8 Supply Chain Risks (IAW CDRL A016)

3.2.4.9 RVA Facility Security Requirements

3.2.5 Program Protection

3.2.6 Information Security / Information Assurance (IAW CDRL A022)

3.2.6.1 Information Security Posture (IAW CDRL A022)

3.2.6.2 Certification & Accreditation (C&A) (IAW CDRL A022)

3.2.6.3 Certified Personnel

3.2.6.3.1 Information Assurance Officer

3.2.7 Configuration Management

3.2.7.1 Controlled Documents (IAW CDRL A029)

3.2.7.2 Non-Configuration Controlled Items (IAW CDRL A008)

3.2.8 Risk Management

3.2.8.1 Risks (IAW CDRL A028)

3.2.8.2 Risk Management Plan (IAW CDRL A007)

3.3 System Modifications

3.3.1 Change Request Evaluation

3.3.2 Feasibility Study (IAW CDRL A015)

3.4 ICBM Systems Directorate Processes (IAW CDRLs A011, A012, A013, and A021) 16

3.5 Administration

3.5.1 Program Management Plan (PMP) (IAW CDRL A005)

3.5.2 Quality Assurance Program Plan (QAPP) (IAW CDRL A006)

3.5.3 Contracting Officer Representative (COR)

3.6 Meetings and Reviews (IAW CDRLs A001, A002, and A003)

3.6.1 Sustainment Reviews

3.6.2 RVA Integrated Product Team

iv of iv

3.7 Trainers

3.8 Government Furnished Property (GFP) (IAW CDRL A023)

3.8.1 GFP Inventory

4 CONTRACT DATA REQUIREMENT LISTING (CDRL)

5 ABBREVIATIONS & ACRONYMS

6 FOR OFFICIAL USE ONLY (FOUO)

1 Performance Work Statement Introduction

1.1 Purpose

This document provides a description of the types of services that the Remote Visual Assessment (RVA) Contractor Logistics Support (CLS) contractor shall perform, not to specify to the contractor how to perform the required services.

This document is in no way intended to suppress innovative ideas or approaches for performing the required services.

1.2 Background

The current RVA Interim Contractor Support (ICS) contract expires on December 31, 2014. The RVA Contractor Logistics Support contract will replace the ICS contract. The RVA CLS contract will sustain and maintain the current RVA System and sustain and maintain any of the below mentioned options that the government decides to exercise. The system includes the RVA Surveillance System, Monitoring System, Data Transmission System and Infrastructure System. The system is made up of 525 sites at Malmstrom, AFB, MT (Wing I), Minot AFB, ND, (Wing III), and FE Warren AFB, WY (Wing V), and the Strategic Missile Integration Complex (SMIC) at Hill AFB, UT.

The RVA CLS will provide efficient and effective depot level maintenance for: 1) Physical interfaces at the launch facility (LF), 2) Physical interfaces at monitoring stations, 3) RVA surveillance system, 4) RVA monitoring system, and 5) RVA data transmission system.

The contractor will also provide contracts’ support, subcontracts’ support, program control and scheduling support, quality assurance support, and engineering support for RVA.

Included in the RVA CLS contract are six options that the government can exercise at any year of the contract if determined necessary. The options will be priced according to the Fixed-Price-Labor-Rate Matrix (see RFP Section J). Two of the options, Options 4 and 5 on the next page, will be priced as Awardable Sample Tasks in the initial proposal, and they may be awarded at the prices bid at the government’s sole discretion. The remaining options, if exercised, will be negotiated after award utilizing the Fixed-Price-Labor-Rate Matrix (see RFP Section J). Hours, labor mix, and any other direct costs would need to be negotiated with the contractor prior to award of the option. For additional information, please reference the Technical Requirement Document (TRD). The options are as follows:

Option 1: Development of a SiteCommanderTM software tablet application

Option 2: Providing a RVA viewing feed to ground security forces vehicles with the following requirements:

a. Tablet based system

b. Eight hour battery life

c. Display 8 x 10

d. Internal GPS in tablet, 32 bit

e. Night Vision Goggle (NVG) compatible, ruggedized

f. System must be < 5 lbs. (portable)

g. Line of sight, view only

h. Connection time refresh rate of three frames per second (fps)

i. Able to support a vehicle speed of 55 mph

j. Antenna requirements that do not interfere with turret operations

k. 60 vehicles per wing

l. Operational test of Option 2 at customer location utilizing ground security forces vehicle supplied as Government Furnished Equipment (GFE)

m. Contractor will develop and submit for customer review and approval an operational test plan and associated procedures

n. Electro-magnetic Interference (EMI) / Electro-magnetic Compatibility (EMC) testing of proposed solution to access impact on current ground security forces vehicle electronics

o. Environmental testing of proposed solution, to include the following: shock, vibration, temperature, dust, and rain

Option 3: Providing a RVA viewing feed to airborne security forces with the following requirements:

a. Tablet based system

b. Eight hour battery life

c. Display 8 x 10

d. Wireless interface on Helicopter

e. Internal GPS in tablet, 32 bit

f. NVG compatible, ruggedized

g. System must be < 5 lbs. (portable)

h. RVA viewing feed to be received by four tablets simultaneously

i. Be able to support a max speed of 150 mph

j. Operational test of Option 3 at customer location utilizing airborne security forces platform supplied as GFE

k. Contractor will develop and submit for customer review and approval an operational test plan and associated procedures

l. EMI / EMC testing of proposed solution to access impact on current airborne security forces platform electronics. Existing certifications can be provided for consideration.

m. Environment testing of proposed solution to include the following: shock, vibration, temperature, dust, rain, and crash safety. Existing certifications can be provided for consideration.

n. Assume eight helicopters at Wing III, eight at Wing I and nine at Wing V

Option 4: Providing RVA display feed into TF214 / Head Quarters (HQ) 20 AF Tactical Operations Center with the following requirement:

a. View capability only

Option 5: Providing RVA display feed to the Wing Command Post at each wing

Option 6: 24/7 responses in terms of troubleshooting and telephone support. Refer to PWS

3.2.4.1 for more information.

1.3 RVA CLS Overview:

The RVA CLS will provide efficient and effective field and depot level maintenance for the following:

RVA installed equipment and software at Launch Facilities (LF) RVA (RVA Integration of Closed Circuit Television) installed equipment and software at Missile Alert Facilities (MAF), Flight Security Control (FSC) Trainer and Wing 3 (only) Standard Evaluator Simulator (SES).

RVA installed equipment and software at Missile Security Center (MSC) and training facilities on each base

RVA installed equipment at repeater sites RVA installed equipment and software at the SMIC RVA feed to the Launch Control Capsule (LCC) RVA options (as outlined above) that are exercised by the government.

Maintenance on any fiber-optic communications segments used by the RVA System RF transmission tower maintenance and all other associated tower maintenance for

RVA System Point-to-point radio installation, maintenance, and repair for RVA System Fixed and Pan-Tilt-Zoom camera installation, maintenance, and repair for RVA

System

The contractor will also provide contracts’ support, subcontracts’ support, program control and scheduling support, quality assurance support, equipment, tools, labor, materials, supervision, other items, and engineering support for RVA.

All travel by the RVA CLS contractor shall be approved in advance by the contracting officer.

The RVA CLS will provide the following support for the RVA system to meet the requirements of Section 3:

Windows 7 System Administration SiteCommanderTM software updates and all other RVA System software maintenance RVA system monitoring RVA edge video recorder and associated software (BB) at each LF site RVA network video recorder and associated software at each MAF site Provide over-the-air and on-site troubleshooting and repair of the RVA system

IP Network Administration (Cisco equipment) User Account Administration Performance feedback of the complete RVA system Manage host domain network equipment Provide Technical Expertise on routers, switches, servers, Digital Video Recorder

(DVRs), cameras, radios, and etc.

Operate & maintain the RVA Operations Center Video transmission, compression, and recording

2 Applicable Documents

Doc. No. Doc. Title Applicability Notes

Northrop Grumman Prime # 112500 Rev B

Remote Visual Assessment Increment I System Specification For Wing III (Minot)

System specifications.

Will be made available on Bidder’s Library.

Northrop Grumman Prime # 96744 Rev 002

Remote Visual Assessment Increment I System Specification For Wing I (Malmstrom)

System specifications.

Will be made available on Bidder’s Library.

Northrop Grumman Prime # 103259

Remote Visual Assessment Increment I System Specification For Wing V (FE Warren)

System specifications.

Will be made available on Bidder’s Library.

DoDI 8500.02

Feb 6, 2003

Information Assurance (IA) Implementation

Identification of IA controls for

DIACAP

DoDI 8510.01 Assurance Certification and Accreditation Process (DIACAP)

DoD 5200.08r Physical Security Program Physical Security Guidelines

DoD 5220.22- M

National Industrial Security Program Operating Manual

Physical Security Guidelines

AFI33-200

23 Dec 2008

Information Assurance (IA) Management

AFI33-

210_AFGM2.3

20 Sept 2012

Air Force Certification & Accreditation (C&A) Program

(AFCAP)

Air Force specific instructions for the Certification & Accreditation of Information Systems

68P81089E50- B

Motorola R56 Standards and Guidelines for Communication Sites

Communication

/ COTS

equipment

Will be made available on Bidder’s Library.

FAA-STD-003

June 11, 1965

Federal Aviation Agency Standard:

Paint Systems for Structures

Radio Towers.

Will be made available on Bidder’s Library

ICBMSD 62-

CMP

ICBM Configuration Management Plan (CMP) 62-CMP

N/A Applicable Installation / System Drawings – JEDMICS

Will be made available on Bidder’s Library.

25-94176 Drawing Tree – RVA Terrestrial Radio System

Shows relationship of all individual drawings

N/A RVA GFP Report Will be made available on Bidder’s Library.

NG-RVA-

Terrestrial Network, Remote Visual Assessment, Wing I – Link Layout

Wing I layout

NG-RVAW3-

LINKS

Wing III Terrestrial Link Layout Wing III layout

RVA Wing 5

LINK

LAYOUT

RVA Wing5 Link Layout _Retrofit_Link_Layout_12May2011

Wing V layout

3 Contract Requirements

3.1 Performance Requirements

The RVA CLS shall maintain the following performance requirements for the RVA system:

3.1.1 Reliability (IAW CDRL A019)

The system shall include labeling of all cables and ports, plug and play subsystems, where practical, and over-the-air, remote, software upgrade or reload, and reset wherever practical. The reliability objective for this contract is 4,000 hours measured by Mean Time Between failure (MTBF).

Failure is defined as the failure of the RVA system to display the image frames from the selected site(s) to the monitoring workstations from at least one of the two cameras in accordance with (IAW) the following requirements:

Location Document Number

Document Title

Wing III Northrop Grumman Prime

RVA

Increment I System

# 112500 REV B Specification For Wing III

Wing I Northrop Grumman Prime # 96744 Rev 002

RVA

Increment I System Specification For Wing I

Wing V Northrop Grumman Prime # 103259

RVA

Increment I System Specification For Wing V

3.1.2 Availability (IAW CDRL A019)

The Availability Objective (AO) for this contract is 95.0% to minimize zero down time and repeat failures. Unavailability due to commercial power outages is not counted against the AO.

3.1.3 Maintainability (IAW CDRL A019)

The Mean Time to Repair (MTTR) objective for this contract is 100 hours to restore video and/or network connectivity to operability. MTTR is defined as the time from which a failure is identified to the time operability is restored.

Operability is defined as the RVA displaying live image frames to at least one of the monitoring workstations to which the LF is designed to report.

The MTTR is based on the RVA CLS having access to the site where the failure occurred, as needed, to make repairs. The period of denied access will not be counted against the MTTR, and it shall immediately be brought to the attention of the contracting officer (CO).

If an RVA system end item or items are unavailable due to part obsolescence, end-of-life or end-of-sale, then the MTTR requirement of 100 hours to restore video and/or network connectivity to operability will not apply until replacement end item(s) become(s) available for installation.

3.2 Sustainment of the RVA system

The RVA CLS contractor shall perform the following functions in support of the performance requirements of Section 3.1.

3.2.1 RVA System Troubleshooting and Failure Analysis

3.2.1.1 Organizational Notification of RVA System Failure (IAW CDRL A024) The RVA CLS contractor shall provide a process for wing / field sites to notify the CLS of an RVA system failure that will support the recovery requirements of Section 3.1.

3.2.1.2 Failure Determination (IAW CDRL A024)

The RVA CLS contractor shall perform necessary hardware failure analysis to determine the cause and resolution of the failure based on the pre-negotiated fixed hourly over and above labor rate. Such work is only authorized after permission of the RVA CLS contracting officer. This report should include root causes, trends, actions, and other recommendations to the government. All failures, regardless of origin, shall be included. Analysis shall extend to the shop replaceable unit (SRU) level. The contractor shall keep this information current and make it readily available to the government via electronic methods.

3.2.1.3 Failure Resolution

3.2.1.3.1 Immediate Restoration of Service

Based on the results of the failure analysis, the RVA CLS contractor shall restore the system to operability IAW the definition in 3.1.3.

3.2.1.3.2 Manual Updates (IAW CDRL A029 and A032)

The RVA CLS contractor shall create and/or modify maintenance manuals to be delivered to the government on the maintenance procedures of the RVA System.

The RVA CLS contractor shall deliver applicable COTS manuals IAW CDRL A029.

3.2.1.3.3 Verification (IAW CDRL A025)

The RVA CLS contractor shall develop, document, and provide the government with procedures that verify the system is fully operable as defined in Section 3.1.3.

3.2.1.3.4 Government Coordination (IAW CDRL A010)

For failures and repairs not covered by existing and/or created maintenance manuals, the RVA CLS contractor shall provide Engineering Change Proposals (ECPs) with supporting data to the government program manager for coordination and approval on the resolution.

3.2.1.3.5 Improve RVA System Performance (IAW CDRL A014 and A026) The RVA CLS contractor shall identify opportunities to the government PM to improve the reliability, availability, and maintainability of the system through a change in procedures or a modification to system hardware and software

The contractor shall prepare and deliver an inventory management plan (IMP) to the government monthly. This plan shall include current inventory and usage status for each Wing.

The RVA CLS contractor shall implement these improvements / modifications, including the approval process, IAW Section 3.3.

3.2.1.3.6 Maintenance Database Update (IAW CDRL A026)

The RVA CLS contractor shall provide regular updates and track failures and repairs through a government database, or a database agreed upon by the program office and the contractor. The program office shall have access to this database. Reportable information shall include, system operability, availability, failures, repair actions, etc.

3.2.1.3.7 Software Maintenance (IAW CDRL A020)

The RVA CLS contractor shall provide support to software / operating systems through updates and administration to meet RVA performance requirements outlined in Section 3:

SiteCommanderTM Software Licenses All current RVA software RVA edge video recorder and associated software at each LF site RVA network video recorder and associated software at each MAF site WindowsTM Server 2008 rev 2 RedHat 6 EnterprisesTM’ Licenses Any other relevant RVA software or operating systems that become relevant to meet RVA software requirements

3.2.1.3.8 RVA Operations Center (IAW CDRL A018)

The current RVA Operations Center is located in Bldg. 1575 at Hill AFB. The RVA Operation Center is used to support day-to-day RVA system integration, testing, as well as troubleshooting of fielded systems at all three wings. The RVA Operation Center must be connected to the SMIC by dedicated landline or line-of-sight radio link. The RVA Operation Center shall have the capability to support multiple phone lines, internet access, operator work and documentation storage space, with sufficient power and cooling to support integrated RVA components, as well as multiple work stations. The RVA Operation Center shall have sufficient room to support both the integration and test activities while simultaneously supporting the troubleshooting of deployed RVA systems. The RVA CLS contractor shall follow the most current versions of both the National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22M and Physical Security Program DoD 5200.08r.

The RVA CLS contractor shall provide a transition plan IAW CDRL A018 or a continuation plan for current location in Bldg. 1575 at Hill AFB. Bldg. 1575 is owned and maintained by Sunset Ridge Development Partners (SRDP) as part of the Enhanced-Use-Lease Falcon Hill Project. If the plan consists of keeping the RVA Operations Center at its current location, please contact Travis Lish at (801) 244-7328 or Gary Stewart at (801) 870-2701 to discuss specifics. If the plan involves moving the lab to another location, please provide a cost and transition plan.

3.2.1.3.9 Contractor Statement of Work (CSOW) (IAW CDRL A004) After award, the RVA CLS contractor shall provide a Contractor Statement of Work (CSOW) that includes the following plans:

Transition Strategy: The transition plan shall include the plan to work closely with the incumbent contractor to ensure adequate transition of all relevant data to the RVA system.

Software Maintenance Plan: An integrated plan to support software / operating systems IAW PWS 3.2.1.3.7 through updates and administration to meet RVA performance requirements as outlined in Section 3 of the PWS.

Performance Requirement Plan: A detailed plan of an effective approach to meet the performance requirements in accordance with Section 3.1 in the PWS.

RVA Lab Transition Plan: Plan should include all items as outlined in IAW PWS 3.2.1.3.8.

3.2.1.3.10 Fault Tree Analysis (IAW CDRL A017)

The RVA CLS contractor shall provide a fault tree analysis down to the Shop Replaceable Unity (SRU) level to assist in maintaining and troubleshooting based on the pre-negotiated fixed hourly over and above labor rate. Such work is only authorized after permission of the RVA CLS contracting officer.

3.2.2 RVA System Assessment (IAW CDRL A027)

The RVA CLS contractor shall provide an assessment of the RVA system that addresses the following items based on the pre-negotiated fixed hourly over and above labor rate.

Such work is only authorized after permission of the RVA CLS contracting officer:

Available spares and conditions Calculated reliability of parts Trend analysis of part failures

3.2.3 RVA System Programmed Maintenance

The RVA CLS contractor shall perform regular required inspections and maintenance to ensure equipment remains operational and functioning. This shall include, but is not limited to:

Network administration Operating system upgrades Annual tower inspections Inspection(s) of all equipment

Equipment cleaning and servicing

3.2.4 Hours of Operation

3.2.4.1 Hours of Operation

Standard hours of operation are Monday through Friday, 0700-1600. The contractor shall at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this CLS performance work statement, except the recognized holidays mentioned in 3.2.4.3. Repairs to restore system functionality shall be performed during standard hours of operation, as needed, to maintain the system and desired performance requirements IAW Section 3.1.

The option of a 24/7 response in terms of troubleshooting and telephone support, if exercised, will be negotiated after award utilizing the Fixed-Price-Labor-Rate Matrix (see RFP Section J). Hours, labor mix, and any other direct costs would need to be negotiated with the contractor prior to award of the option. If this option is exercised, the contractor shall respond on a 24/7 basis to any and all RVA calls regarding issues / failures. This 24/7 response shall be activated through the use of a single contact number (pager / cellphone) that shall be maintained by the contractor’s representative at that wing.

3.2.4.2 Down Day/Base Closure/Exercises/Inspections

Unless mitigating circumstances require the government to provide oversight, contractor personnel shall report for corporate supervision. All chargeable work shall be directly attributable to the task under which the individual works under. Government oversight applies in cases where the base is closed due to inclement weather, Presidential declaration of a Federal office closure day, etc. Contractor personnel are not to be affected and/or participate in exercises and formal inspections. The contractor shall not be held liable for lost time due to government’s decision to delay or deny base or facility access for reasons to include, but not limited to: inclement weather, Force Protection / THREATCON levels, Presidential, Air Force or Major Command (MAJCOM) down days, or energy savings initiatives.

3.2.4.3 Recognized Holidays

The contractor is not required to provide service on the following days: New Year’s Day, Thanksgiving Day, Memorial Day, Independence Day, Labor Day, Christmas Eve Day, and Christmas Day.

3.2.4.4 Rapid On-Site Technical Support

The RVA CLS contractor shall provide service outside of the normal duty hours, as described above, at the request of the customer to support an activation or exercise of contingency plans.

3.2.4.5 On-Site Response

The RVA CLS contractor shall perform all required maintenance and repairs on the equipment within the scope of the contract, whether at field sites or over the network.

The government currently does not perform any of the maintenance activities for the RVA system and does not plan on doing so in the future. The contractor shall maintain one team per each of the three Missile Wings to provide timely response in order to meet the performance requirements spelled out in Section 3.0 of this specification. The contractor shall acquire and maintain a storage facility at locations near each of the three Missile Wings to securely store all spare parts, materials and equipment used to maintain the RVA system IAW DoD Instruction 4161.02. The RVA CLS contractor shall follow the most current versions of both the National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22M and Physical Security Program DoD 5200.08r.

The RVA CLS contractor shall coordinate activities with each individual Wing’s Security Forces Group (SFG) to obtain Entry Authority List (EAL) access. EALs shall be processed in accordance with Wing policy. The contractor is responsible for the accuracy of all information they provide for the EAL. Any delays caused by submission of incorrect information shall be at no cost to the government. It is suggested that the contractor maintain a log and uniquely number their EAL requests. It is suggested that the contractor retain a copy of their EAL requests as this information cannot be returned.

The contractor shall provide complete, current, and legible data to produce the initial EAL prior to their initial commencement of work at sites for this project. This may include scanned copies of the documents to be presented for entry. Thirty working days are required to process, issue, make additions to, make corrections to, or reissue an EAL. This data must be submitted to the Wing RVA point of contact (POC). EALs remain in effect until that are replaced or until they expire. When an EAL expires, all information for all entries must be resubmitted.

Contractor submitted visit request(s) shall include the project name and the contract number, the individual’s name as it appears on the identification document, the type of identification and identification control number, duty title, security clearance status, company name, and mission-essential hand carried items for each individual requiring work at or near a LF and/or MAF. Valid authentication must include a photo and the ID needs to be government issued.

Only vehicles essential for the contractual obligations shall be permitted on a MAF or LF. Vehicle authorization shall be processed in accordance with Wing policy. Company identification must be displayed on each side of all vehicles authorized entry onto the MAF or LF, as applicable. Ignition keys shall be removed and/or vehicle immobilized when unattended. Authorized contractor vehicles and equipment shall be placed so as not to interfere with gates, emergency escape routes, antennas, and any other above ground structures. All vehicles, personnel, and items are subject to inspection by Security Forces at any time. The primary contractor shall submit the required information for all subcontractor vehicles.

3.2.4.6 RVA System Supply Chain Management (IAW CDRL A016 and A010) The RVA CLS contractor shall manage the supply chain for RVA system components to include:

Maintaining depot and organizational spares at the levels required for system supportability. The contractor shall request government authority to replace expendable items when they drop below 10% for electronic equipment spares at each Wing’s storage location, and under 5% for all other spare equipment at each Wing’s storage location that were used for maintenance repairs.

Identification of risks to supply chain due to parts’ obsolescence and unsupported hardware, diminishing materials sources, and material shortages (DMSMS).

Submit an ECP (IAW CDRL A010) to request approval for the use of a specific suitable form / fit / function replacement for unsustainable components.

As RVA end items reach obsolescence or end-of-life / end-of-sale, then replacement end items will need to comply with appropriate testing and qualifications outlined in ICBMSD 62-CMP and in all other applicable documents as referenced in the Technical Requirements Document such as the Minuteman Weapon System Specification (S-133-128D).

3.2.4.7 Spares Use & Inventory (IAW CDRL A027)

The RVA CLS contractor shall deliver to the government a spares inventory and spares usage listing.

The RVA Spares CLIN consists of all RVA end items. Examples of this would include electronic equipment spares when they drop below 10% or other spare equipment at each Wing’s storage location used for maintenance repairs when they drop below 5%.

The RVA Incidental Material CLIN requires all unforeseen items that will require contracting officer approval. Examples of this would include other equipment needed for maintenance repairs beyond spare equipment stored at each Wing’s storage location.

3.2.4.8 Supply Chain Risks (IAW CDRL A016)

The RVA CLS contractor shall deliver to the government the identified risks to the supply chain in a technical report IAW CDRL A016 based on pre-negotiated fixed hourly over and above labor rate. Such work is only authorized after permission of the RVA CLS contracting officer.

3.2.4.9 RVA Facility Security Requirements

Warehouses near each Wing and the Hill AFB Lab have sensitive (not classified) spares, equipment, manuals, computer files, and access to network equipment that require a level of security at those facilities consistent with IA requirements. The contractor shall acquire and maintain a storage facility at locations near each of the three Missile Wings to securely store all spare parts, materials and equipment used to maintain the RVA system IAW DoD Instruction 4161.02. The RVA CLS contractor shall follow the most current versions of both the National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22M and Physical Security Program DoD 5200.08r.

3.2.5 Program Protection

The RVA CLS contractor shall protect program critical information as “For Official Use Only” (FOUO) such as single points of failure, network recovery, times, outages, and scheduled outages IAW Section 6 of the PWS. The RVA CLS contractor shall follow the most current versions of both the National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22M and Physical Security Program DoD 5200.08r. The contractor shall be flexible in providing protection outlined in Section 6 of the PWS as the RVA system matures.

3.2.6 Information Security / Information Assurance (IAW CDRL A022) The RVA system is MAC III certified and the RVA CLS contractor is required to maintain that certification. Please refer to Bidders’ Library for MAC III information.

3.2.6.1 Information Security Posture (IAW CDRL A022)

The RVA CLS contractor shall verify that modifications to the RVA system do not degrade its information security posture.

3.2.6.2 Certification & Accreditation (C&A) (IAW CDRL A022)

The RVA CLS contractor shall maintain the C&A of the RVA subsystem by performing the following:

Maintaining the currency of RVA system information for all Air Force (AF) Information Assurance databases (EITDR, eMASS) as per DODI 8500.1 and 8500.2

For more information regarding EITDR and eMASS see below:

(http://www.disa.mil/Services/Information-Assurance/EMASS) (https://acc.dau.mil/adl/en-US/509421/file/63729/SWGD027.doc)

In sufficient time, prior to the expiration of the RVA system C&A, update the IA package and submit the package through the Intercontinental Ballistic Missile Systems Directorate (ICBMSD) Information Assurance Manager (IAM) to the appropriate Designated Approving Authority (DAA) for reaccreditation.

The RVA CLS contractor shall continue to respond to, and coordinate with, the IAM and the DAAs office through to awarding of the Authority-To- Operate (ATO) by the DAA.

3.2.6.3 Certified Personnel

Personnel performing the Information Security / Information Assurance work shall meet the minimum certification standards as defined in Department of Defense (DoD)

8570.01 for IA professionals.

3.2.6.3.1 Information Assurance Officer

The RVA CLS contractor shall perform the functions of an Information Assurance Officer (IAO), coordinating with the Information Assurance Manager (IAM) at the ICBMSD, IAW DOD 8570.01-M, Section 5.9 of DOD Instruction 8500.02 and AFI 33-210. RVA is certified as a MAC III Sensitive system, and the CLS contractor is required to maintain that certification.

3.2.7 Configuration Management

The RVA CLS contractor shall comply with the ICBMSD 62-CMP configuration management plan.

3.2.7.1 Controlled Documents (IAW CDRL A029)

The RVA CLS contractor shall maintain and update baseline and other technical documents per the request of the government program office which include the following:

RVA System Wing I Drawings RVA System Wing III Drawings RVA System Wing V Drawings RVA System Wing I Layout RVA System Wing III Layout RVA System Wing V Layout Other documents IAW CDRL A029

3.2.7.2 Non-Configuration Controlled Items (IAW CDRL A008)

The RVA CLS contractor shall document and bring under configuration management the following items:

RVA network node configurations held in firmware Custom test and maintenance network software

3.2.8 Risk Management

In coordination with the government program manager, the RVA CLS contractor shall manage risks to the RVA system using a database decided upon by the program office and the contractor.

3.2.8.1 Risks (IAW CDRL A028)

The RVA CLS contractor shall deliver to the government proposed risk items to be considered by the RVA Integrated Product Team (IPT).

3.2.8.2 Risk Management Plan (IAW CDRL A007)

The RVA CLS contractor shall deliver to the government a plan that addresses how the contractor will manage risks to the RVA system. This plan shall be used to monitor management, cost, and schedule of the RVA system and risk data for all the associated risks with the system. All program related risks shall be reviewed monthly during one of the weekly IPT teleconference calls.

3.3 System Modifications

3.3.1 Change Request Evaluation

The RVA CLS contractor shall review change requests submitted against the RVA system and provide a recommended course of action to the government that addresses the change request.

3.3.2 Feasibility Study (IAW CDRL A015)

The RVA CLS contractor shall conduct feasibility studies for system modifications to identify impacts, issues and risks as well as improvement opportunities for the RVA system based on the pre-negotiated fixed hourly over and above labor rate. Such work is only authorized after permission of the RVA CLS contracting officer.

The RVA CLS contractor shall utilize sustainment funds to purchase third party maintenance contracts for hardware and software, to purchase materials in support of RVA CLS sustainment tasks, to conduct tests, to maintain the RVA equipment, to design and install replacements / upgrades, and to develop and maintain operations and quality of the program.

3.4 ICBM Systems Directorate Processes (IAW CDRLs A011, A012, A013, and A021) The RVA CLS contractor shall perform all modifications to the RVA subsystem IAW the ICBMSD approved processes. Specifically for the RVA system, the following processes are applicable:

Process Number Process Title

ICBMSD OI 62-01 Configuration Control Board

ICBMSD OI 99-103 Test (H/W & S/W) & Evaluation

AFI 33-210 Air Force Certification and Accreditation Process

The contractor shall report all contractor labor hours, including subcontractor labor hours, required for performance of services provided under this contract for the RVA CLS 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 shall be for the labor executed during the period of performance for each government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

3.5 Administration

The RVA CLS contractor shall deliver a contract summary (IAW CDRL A009) that includes an overview of:

1. The contract performance for applicable cost and schedule parameters

2. Tasks completed under the contract

3. The status of the RVA system

3.5.1 Program Management Plan (PMP) (IAW CDRL A005)

The RVA CLS contractor shall deliver a Program Management Plan for the RVA CLS effort. The PMP shall include proposed hours of work, number of personnel, communication plan with government, configuration control, engineering changes, and all other relevant program status in reference to the RVA Program.

3.5.2 Quality Assurance Program Plan (QAPP) (IAW CDRL A006)

The RVA CLS contractor shall deliver a Quality Assurance Program Plan (QAPP) for the RVA CLS effort. This is a detailed plan on how to meet the performance and system requirements outlined in this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The QAPP is the means by which the contractor assures its work complies with the requirements of the contract. The contractor shall implement a complete QAPP that identifies potential and actual problem areas throughout the life of the contract.

3.5.3 Contracting Officer Representative (COR)

The government will assign a Contracting Officer Representative (COR) in writing to oversee contract execution and interact daily with the contractor in the performance of all contract requirements. The COR will be identified by a separate letter. The COR monitors all technical aspects of the contract and assists in contract administration.

3.6 Meetings and Reviews (IAW CDRLs A001, A002, and A003)

The RVA CLS contractor shall support sustainment reviews and integrated product team meetings.

3.6.1 Sustainment Reviews

The RVA CLS contractor shall provide the following input to sustainment reviews:

Monthly report on performance requirements (IAW CDRL A009) Program Management Review held semi-annually (IAW CDRLA001, A002, and

A003). Program management reviews shall be held at six month intervals with the first being held at the contractor’s facility and the second at the government’s facility.

Each program management review will be approximately one day in duration.

Agendas for each meeting will be coordinated in advance between the government’s program office and the contractor’s management team.

The semi-annual Program Management Reviews shall include a review and analysis of repairs / failures, inventory, cost, repair turn-around times, training, parts and obsolescence issues, software concerns, customer concerns, contract status, performance metrics, and other related installation and sustainment efforts.

Program Management Reviews shall also address monthly Integrated Program Management Reports (IPMR) IAW CDRL A031. IPMR is the primary means of communicating program cost and schedule information between the prime contractor and the Government.

3.6.2 RVA Integrated Product Team

The RVA CLS contractor shall support the RVA IPT teleconference meetings held once per week with the necessary program and technical personnel. These meetings shall be of a sufficient duration to allow for adequate coverage of programmatic issues, status, risks, and other pertinent program information. It is anticipated that these meetings will last no longer than one hour per week.

3.7 Trainers

The RVA CLS contractor shall maintain the RVA trainers at each of the three Wings.

3.8 Government Furnished Property (GFP) (IAW CDRL A023)

3.8.1 GFP Inventory

The RVA CLS contractor shall deliver to the government a GFP inventory and status.

4 CONTRACT DATA REQUIREMENT LISTING (CDRL)

Data Item # Description Paragraph DID A001 Conference Agenda 3.5, 3.6.1 DI-ADMN-81249A A002 Briefing Material 3.5, 3.6.1 DI-MGMT-81605 A003 Report, Record of

Meeting/Minutes

3.5, 3.6.1 DI-ADMN-81505

A004 Statement of Work 3.2.1.3.9 DI-MGMT-81606 A005 Program Management Plan 3.5.1 DI-MGMT-81797 A006 Quality Assurance Program

Plan

3.5.2 CI-QCIC-81794

A007 Contractor’s Risk Management Plan

3.2.8.2 DI-MGMT-81808

A008 Contractor’s Configuration Management Plan

3.2.7.2 DI-CMAN-80858B

A009 Contract Summary Report 3.6.1 DI-ADMN-80447A A010 Engineering Change Proposal 3.2.1.3.4, 3.2.4.6 DI-CMAN-80639C A011 Test Plan (Acceptance, Qualification, Integration for both H/W & S/W)

3.4 DI-NDTI-80566A

A012 Test Procedure (Acceptance, Qualification, Integration)

3.4 DI-NDTI-80603A

A013 Test/Inspection Report (Acceptance, Qualification, Integration)

3.4 DI-NDTI-80809B

A014 Technical Report- Study/Services (Opportunities to improve reliability, availability and maintainability)

3.2.1.3.5 DI-MISC-80508B/T

A015 Technical Report- Study/Services (Feasibility Studies)

3.3.2 DI-MISC-80508B/T

A016 Technical Report- Study/Services (Risks to the Supply Chain)

3.2.4.6 3.2.4.8

DI-MISC-80508B/T

A017 Technical Report- Study/Services (Fault Tree Analysis)

3.2.1.3.10 DI-MISC-80508B/T

A018 Technical Report- Study/Services (Transition Plan)

3.2.1.3.8 DI-MISC-80508B/T

A019 Performance Analysis Report 3.1.1, 3.1.2, 3.1.3 DI-SESS-81938

A020 Computer Software Product 3.2.1.3.7 DI-ISPC-81488 A021 Man Hours Expenditure Chart 3.4 DI-FNCL-80003 A022 Information Systems

Accreditation Documentation 3.2.6.2, 3.2.6, 3.2.6.1, 3.2.6.3

DI-ADMN-80239

A023 Government Furnished Materiel (GFM) Consumption Report

3.8 DI-MGMT-80438B

A024 Failure Analysis and Corrective Action Report

3.2.1.1, 3.2.1.2, 3.2.1.3.2

DI-SESS-81315B

A025 Verification Analysis Record 3.2.1.3.3 DI-QCIC-80207 A026 Maintenance Service Report 3.2.1.3.5 DI-MGMT-80995A A027 Spare Parts Usage Report 3.2.2, 3.2.4.7 DI-ILSS-80483 A028 Risk Management Status

Report

3.2.8.1 DI-MGMT-81809

A029 Commercial Off-The-Shelf (COTS) Manuals

3.2.7.1, 3.2.1.3.2 DI-TMSS-81815

A030 Data Accession List (DAL) 3.2.7.1 DI-MGMT-81453A A031 Integrated Program

Management Report

3.6.1 DI-MGMT-81861/T

A032 Operating Procedures Manual 3.2.1.3.2 DI-MISC-81418

5 ABBREVIATIONS & ACRONYMS

AF Air Force

AFB Air Force Base

AFGSC Air Force Global Strike Command

AFNWC Air Force Nuclear Weapon Center

ANNLY Annually

AO Availability Objective

ASREQ* As Required

ATO Authority to Operate

ATP Acceptance Test Procedure

BI-WE Each 2 weeks

CDRL Contract Data Requirements List

CI Configuration Item

CLS Contractor Logistics Support

CMRP Contractor Manpower Reporting Application

COR Contracting Officer’s Representative

CPD Capability Production Document

CSOW Contractor Statement of Work

DA Days after

DAA Designated Approving Authority

DAC Days after contract award

DIACAP DOD Information Assurance Certification and Accreditation

DOD Department of Defense

DVR Digital Video Recorder

EAL Entry Authority List

ECP Engineering Change Proposal

EMC Electro-magnetic compatibility

EMI Electro-magnetic Interference

FOUO For Official Use Only

FY Fiscal Year

GFE Government Furnished Equipment

GFP Government Furnished Property

GIDEP Gov. Industry Data Exchange Program

I&CO Installation and Check-Out

IA Information Assurance

IAM Information Assurance Manager

IAW In Accordance With

ICBM Intercontinental Ballistic Missile

ICBMSD Intercontinental Ballistic Missile Systems Directorate

ICD Interface Control Drawing

ICS Interim Contractor Support

IMP Inventory Management Plan

IMS Integrated Master Schedule

IPIC ICBM Prime Integration Contract

IPT Integrated Product Team

ISO International Standards Organization

JCS Joint Chiefs of Staff

LCC Launch Control Center

LF Launch Facility

LRU Line Replaceable Unit

MAF Missile Alert Facility

MAJ COM Major Command

MM III Minuteman III

MM Minuteman

MP Management Plan

MSC Missile Security Center

MTBF Mean Time between Failures

MTHLY Monthly

MTTR Mean Time To Repair

MXG Maintenance

NISPOM National Industrial Security Program Operating Manual

NLT Not later than

NVG Night Vision Goggle

OG Operations Group

OPR Office of Primary Responsibility

PM Program Manager

PMP Program Management Plan

POC Point of Contact

PWS Performance Work Statement

QAPP Quality Assurance Program Plan

QDR Quality Deficiency Reporting

QRTLY Quarterly

REQD Required

RVA Remote Visual Assessment

RVA CLS Remote Visual Assessment Contractor Logistics Support

RVA System Remote Visual Assessment at all Wings and SMIC

SFG Security Forces Group

SMIC Strategic Missile Integration Complex

SRDP Sunset Ridge Development Partners

SRU Shop Replaceable Unit

T.O.s Technical Orders

TM Technical Manual

USAF United States Air Force

WEKLY Weekly

6 FOR OFFICIAL USE ONLY (FOUO)

FOUO is not a classification. Originators mark records when they create them to call attention to FOUO content. An FOUO marking does not mean you must withhold a record under the FOIA.

You still need to review requested records. Examine records with and without markings to identify information that needs protection and is exempt from public release or to decide whether discretionary release is appropriate.

Information in a technical document that requires a distribution statement per AFI 61-204, Disseminating Scientific and Technical Information, must show that statement. The originator may also mark the information FOUO, if appropriate.

Mark an unclassified document containing FOUO information “For Official Use Only” at the bottom, on the outside of the front cover (if any), on each page containing FOUO information, on the back page, and on the outside of the back cover (if any).

In unclassified documents, the originator may also mark individual paragraphs that contain FOUO information to alert users and assist in review.

In a classified document, mark: An individual paragraph that contains FOUO, but not classified information, by placing “(FOUO)” at the beginning of the paragraph.

The top and bottom of each page that has both FOUO and classified information, with the highest security classification of information on that page. “FOUO” at the bottom of each page that has FOUO but not classified information.

If a classified document also contains FOUO information or if the classified material becomes FOUO when declassified, place the following statement on the bottom of the cover or the first page, under the classification marking: NOTE: If declassified, review the document to make sure material is not FOUO and not exempt under DOD 5400.7, AF Supplement before public release.

Mark other records, such as computer printouts, photographs, films, tapes, or slides, “For Official Use Only” or “FOUO” so the receiver or viewer knows the record contains FOUO information.

Mark FOUO material sent to authorized persons outside the DOD with an explanation typed or stamped on the document.

Transmitting FOUO:

DOD components, officials of DOD components, and authorized DOD contractor consultants, and grantees send FOUO information to each other to conduct official DOD business. Tell recipients the status of such information, and send the material in a way that prevents unauthorized public disclosure. Make sure documents that transmit FOUO material call attention to any FOUO attachments. Normally, you may send FOUO records over facsimile equipment. When deciding whether to send FOUO records over facsimile equipment, balance the sensitivity of the records against the risk of disclosure. To prevent unauthorized disclosure, consider attaching special cover sheets (i.e. AF Form 3227, Privacy Act Cover Sheet, for Privacy Act Information), the location of sending and receiving machines, and ensure authorized personnel are available to receive FOUO information as soon as it is transmitted.

FOUO information may be passed to officials in other departments and agencies of the executive and judicial branches to fulfill a government function. Mark the records “For Official Use

Only,” and tell the recipient the information is exempt from public disclosure under the FOIA and whether it needs special handling. Electronically and Facsimile Transmitted Messages. Each part of electronically and facsimile transmitted messages containing FOUO information shall be marked appropriately. Unclassified messages containing FOUO information shall contain the abbreviation “FOUO” before the beginning of the text. Such messages and facsimiles shall be transmitted in accordance with communications security procedures whenever practicable.

Transporting FOUO:

Records containing FOUO information shall be transported in a manner that prevents disclosure of the contents. When not commingled with classified information, FOUO information may be sent via first-class mail or parcel post. Bulky shipments, such as distributions of FOUO Directives to testing materials, that otherwise qualify under postal regulations may be sent by fourth class mail. Mark each part of a message that contains FOUO information. Unclassified messages containing FOUO information must show the abbreviation “FOUO” before the text begins.

Safeguarding FOUO Information:

During normal duty hours: During normal working hours, records determined to be FOUO shall be placed in an out-of-sight location if the work area is accessible to non-DoD personnel. During Non-duty Hours: At the close of business, FOUO records shall be stored so as to prevent unauthorized access. Filing such material with other unclassified records in unlocked files or desks, etc., is adequate when normal U.S. Government or Government-contractor internal building security is provided during non-duty hours. When such internal security control is not exercised, locked buildings or rooms normally provide adequate after-hours protection. If such protection is not considered adequate, FOUO material shall be stored in locked receptacles such as file cabinets, desks, or bookcases. FOUO records that are subject to the provisions of the National Security Act of 1959 (reference (aa)) shall meet the safeguards outlined for that group of records.

Termination, Disposal and Unauthorized Disclosures:

Termination: The originator or other competent authority; e.g., initial denial and appellate authorities, shall terminate “For Official Use Only” markings or status when circumstances indicate that the information no longer requires protection from public disclosure. When FOUO status is terminated, all known holders shall be notified, to the extent practical.