Attachment_1_-_SCDS_II_DRAFT_PWS.pdf

Performance Work Statement (PWS) Solicitation No. FAxxxx-10-x-xxxx Space Control Depot Support (SCDS) II Contract No. FAxxxx-10-x-xxxx 1 Page of 39

UNCLASSIFIED

PERFORMANCE WORK STATEMENT (PWS)

FOR

SPACE CONTROL DEPOT SUPPORT (SCDS) II

SPACE & MISSILE SYSTEMS CENTER

SPACE SUPERIORITY SYSTEMS

DIRECTORATE (SMC/SY)

(10 JUN 2016)

2 Page of 39

Table of Contents

1. BACKGROUND

2. SCOPE

3. DESCRIPTION OF SERVICES

3.1. PROGRAM MANAGEMENT

3.1.1. Kickoff Meeting

3.1.2. Integrated Support Plan

3.1.3. Monthly Status Report

3.1.4. Contractor Program Management Reviews (PMR)

3.1.5. Technical Interchange Meetings (TIM)

3.1.6. Working Group (WG) and Conference Support

3.1.7. Teleconferences and Informal Working Group Meetings

3.1.8. Technical Assistance Agreement (TAA)

3.1.9. Cost Management

3.1.9.1. Cost Information

3.1.9.2. Cost/Schedule Control System

3.1.9.3. Integrated Program Management Report

3.1.9.4. Small Business

3.1.9.5. Organic Partnering

3.2. SYSTEMS ENGINEERING

3.2.1. Risk and Opportunity Management

3.2.2. Configuration Management

3.2.2.1. Operational Baseline

3.2.2.2. CM for System and Equipment Upgrades

3.2.2.3. CM Library

3.2.2.4. Configuration Control

3.2.2.5. Configuration Audits

3.2.3. System Safety

3.2.4. System Changes, System Upgrades, and System Procurement

3.2.4.1. Integration, Test, & Installation

3.2.4.2. System Procurement

3.2.5. Software Maintenance

3.2.5.1. Depot Level Software Maintenance

3.2.5.2. Software Configuration Control

3.2.6. Quality Control (QC)

3.2.6.1. Contractor Quality Control Plan

3.2.6.2. Inspection Files

3.2.6.3. Deficiency Reporting

3.2.6.4. Quality Assurance

3.2.6.5. Scope Changes

3.2.7. Configuration Status Accounting

3.3. CYBERSECURITY

3.4. DEPOT SUPPORT AND SUSTAINING ENGINEERING (DS&SE)

3.4.1. Engineering Support

3 Page of 39

3.4.2. DS&SE Functional Interface Control

3.4.3. Depot Support Facility (DSF)

3.4.4. DSF Support Equipment

3.4.5. Engineering Assistance

3.4.6. Depot Level Inspections (DLIs)

3.4.7. Emergency Depot Level Maintenance

3.4.8. Failure Analysis Corrective Actions Report (FACAR)

3.4.9. Diminishing Manufacturing Sources and Material Shortages (DMSMS)

3.4.10. Software Licensing

3.4.11. System Reliability, Availability and Maintainability (RAM)

3.4.12. Item Management

3.4.12.1. General Overview

3.4.12.2. Item Unique Identifier (IUID)

3.4.12.3. Forward Supply Point

3.4.12.4. Spares Management

3.4.13. List of Repairables

3.4.14. Spares Testing

3.4.14.1. Spares Procurement

3.4.14.2. Supply Chain Risk Management (SCRM)

3.4.15. Hardware Repair and Maintenance

3.4.16. Disposition

3.4.17. Packaging, Handling, Shipping and Transportation (PHS&T)

3.4.17.1. Packaging

3.4.17.2. Handling

3.4.17.3. Storage

3.4.17.4. Shipment

3.4.17.4.1. Classified/Sensitive Shipments

3.4.17.5. Transportability

3.4.18. Training

3.4.18.1. Training Material

3.4.19. Technical Data Package

3.4.20. Maintenance Data Collection

3.4.21. Contractor Travel

3.5. STUDIES AND ANALYSIS

3.6. TRANSITION TO SUSTAINMENT

3.7. SUPPORT TO OPERATIONS

4. SERVICE SUMMARY (SS)

4.1. GENERAL

4.2. PERFORMANCE EVALUATION

5. GENERAL INFORMATION

5.1. CONTRACTOR PERSONNEL

5.1.1. Contract Manager

5.1.2. Contractor Employees

5.1.2.1. Employee Training

5.1.2.2. Employee Certifications

5.1.2.2.1. Contractor Required Cybersecurity Certifications

4 Page of 39

5.1.2.3. Government Security Instructions

5.1.2.4. Critical Program Information

5.1.2.5. Physical Security

5.1.2.6. Employment of Government Employees

5.2. SAFETY

5.3. CONTRACT CLOSEOUT

5.4. DATA RIGHTS DOCUMENTATION

5.5. CERTIFICATION AND ACCREDITATION SUPPORT

APPENDIX A - GOVERNMENT FURNISHED PROPERTY/SERVICES/EQUIPMENT

APPENDIX B – CDRL AND INSTRUCTIONS

APPENDIX C - APPLICABLE PUBLICATIONS AND FORMS

APPENDIX D - ACRONYMS, ABBREVIATIONS AND DEFINITION

5 Page of 39

1. Background

The Space Superiority Systems Directorate (SMC/SY) is responsible for sustaining and upgrading all space control systems and all associated support and infrastructure systems within its portfolio to include Offensive Space Control (OSC) and Defensive Space Control (DSC) weapon systems and infrastructure assets. Modeled to adhere to the tenants and principles of Performance Based Logistics (PBL), SMC/SY seeks to find a Product Support Integrator (PSI) responsible for the total life-cycle support of SY systems from a programmatic and functional perspective, to include coordinating sustainment support through both industry and organic partnerships. The SCDS II PSI will provide sustainment support for the growing and evolving SMC/SY space control enterprise.

2. Scope

This Performance Work Statement (PWS) describes the proposed effort to sustain and modify existing, emerging, and prototype SMC/SY Space Control capabilities. The scope includes five (5) major categories: Depot Support and Sustainment Engineering (DS&SE), System Upgrade and Modifications, Studies and Analysis, Transition of Future Systems, and Support to Operations. Additionally, all tasks associated with the program management, cyber security, program protection, systems engineering, software engineering, and life-cycle sustainment of SMC/SY space control portfolio, including Offensive Space Control (OSC) weapon systems and Defensive Space Control (DSC) weapon systems along with any associated OSC/DSC infrastructure support assets, are included.

A significant portion of the equipment and data processed under this PWS is classified.

Therefore a basic requirement is the contractor’s ability to retain an existing or obtain proper credentials/accreditations needed to properly store and operate classified material, equipment, and data as identified in the DD254.

At a minimum, the SCDS II program will include the geographically dispersed systems as identified in Table 2-1.

6 Page of 39

Table 2-1: SCDS II SYSTEMS

3. Description of Services

This section describes tasks the contractor shall perform on the SCDS II contract.

3.1. Program Management

The contractor shall establish management processes to ensure sustainment support services for the SMC/SY systems sustained under this contract currently and in the future.

3.1.1. Kickoff Meeting

The contractor shall conduct a kickoff meeting within 45 calendar days of contract award and within 30 days of the start of each subsequent contract year. The contractor shall discuss the plan to meet Government objectives, performance requirements and shall identify any constraints, risks and issues. Security procedures shall be discussed and any required security in-briefings shall be accomplished. (Presentation Material, Conference Agenda & Minutes CDRL, A016)

3.1.2. Integrated Support Plan

The contractor shall deliver and maintain an Integrated Support Plan (ISP) that addresses all programs sustained under this contract consistent with all PWS requirements. The ISP shall document the contractor’s approach to satisfying the tasks listed in this PWS. The ISP shall detail how each PWS objective will be accomplished, System Number of Systems

Counter Communications Systems (CCS)

Multiple systems, multiple configurations

Space Test and Training Range (STTR)

Fixed location w/multiple deployable assets

Big Top Data repository w/multiple deployable assets

Standardized Process for Interference Recognition and Targeting (SPIRIT)

Three (3) fixed locations

RAIDRS Deployable Ground Segment

(RDGS)

One (1) fixed location

Other Classified Systems

Reference SCGs

Emerging Programs TBD

7 Page of 39 managed, and integrated into a comprehensive sustainment plan. (Integrated Support Plan, CDRL A002)

3.1.3. Monthly Status Report

The contractor shall deliver a Monthly Status Report (MSR) detailing progress and identifying any concerns. The MSR shall be organized and report contractor activities in accordance with the Work Breakdown Schedule (WBS). Subsystems may require different levels of WBS breakdown in which case exceptions to baseline level will be provided. (Monthly Status Report, CDRL A011)

3.1.4. Contractor Program Management Reviews (PMR)

The contractor shall host and support one PMR per quarter. PMRs shall cover overall program management organizational structure, overall program status, cost and schedule reporting, teaming agreements, program risks/issues and associated mitigations. PMR locations will alternate between contractor and SMC/SY facilities.

Products shall be submitted in accordance with CDRL A016, Presentation Material, Conference Agenda & Minutes. For efficiency purposes, the contractor may combine PMRs with Technical Interchange Meetings (TIM) (see PWS 3.1.5). (Presentation Material, Conference Agenda & Minutes, CDRL A016)

3.1.5. Technical Interchange Meetings (TIM)

The contractor shall conduct to support systems on the SCDS II contract. The TIM provides a chance for the Government to interact with the contractor to discuss technical and programmatic issues in detail and to resolve program issues. Products shall be submitted in accordance with CDRL A016, Presentation Material, Conference Agenda & Minutes. TIMs are less formal than PMRs and depending on the nature of the issue, may involve multiple working groups. (Presentation Material, Conference Agenda & Minutes, CDRL A016).

3.1.6. Working Group (WG) and Conference Support

The contractor shall host and/or support Government-chaired WG meetings annually at either Government or contractor facilities. Examples include, but are not limited to, sparing conferences, cybersecurity working groups, Integrated Logistics Support (ILS) working groups and test working groups. The hosting contractor shall serve as the meeting/WG secretariat, shall collect meeting action items, and shall develop and distribute Government-approved meeting minutes. (Presentation Material, Conference Agenda & Minutes, CDRL A016)

3.1.7. Teleconferences and Informal Working Group Meetings

Informal teleconferences and working group meetings may be held as required, or as mutually agreed upon, to cover more limited/specific subject areas.

3.1.8. Technical Assistance Agreement (TAA)

Upon Government direction, the contractor shall obtain a Technical Assistance Agreement from the Department of State to allow for direct interface with foreign nationals. The TAA will comply with the International Traffic in Arms Regulation, section

124. No information will be provided to or shared with a foreign government/national until the TAA is properly approved by the Department of State.

8 Page of 39

3.1.9. Cost Management

3.1.9.1. Cost Information

The contractor shall develop and maintain cost accounting data consistent with the Contractor Work Breakdown Structure (CWBS) for products and services performed.

3.1.9.2. Cost/Schedule Control System

The contractor shall establish, maintain, and use in the performance of this contract a Cost/Schedule control system. The cost/schedule control methods implemented by the contractor shall use existing resources, while maintaining the security requirements of the program. The cost control system shall result in a single formal, integrated system serving both contractor-internal management and Government cost reporting requirements. (Contract Funds Status Report, CDRL A003)

3.1.9.3. Integrated Program Management Report

The contractor’s financial reporting in the Integrated Program Management Report (IPMR) for this contract shall reference applicable CWBS elements. The contractor shall report cost data to a level showing allocated costs to each individual program sustained under this contract.

The contractor shall develop and maintain an Integrated Master Schedule (IMS) of planned activities and shall ensure the Government has adequate notice and program status information to address activities requiring coordination without impacting program schedules. The IMS shall be organized in accordance with the Work Breakdown Structure (Integrated Program Management Report, CDRL A015)

3.1.9.4. Small Business

The contractor shall provide total dollars with corresponding percentages and direct contract cost scheduled for Small Business (SB) and Small Disadvantaged Business (SDB). This shall be provided in the Small Business Contractor Report. (Small Business Contractor Report, CDRL A018)

3.1.9.5. Organic Partnering

The contractor shall provide an analysis of organic opportunities with corresponding percentages and direct contract costs scheduled for public-private partnering with organic DoD Depots. The contractor shall ensure 1% of the annual sustainment budget is allocated within the first two years and up to 5% by the end of the seven year contract to organic depots. It shall be reported in the Service Summaries no later than six quarters after contract award. Work can be allocated to organic depots through either “direct sales” or “work share” opportunities. This information shall be provided in the Public Private Partnering Report IAW CDRL A026. (Public Private Partnering, CDRL A026)

3.2. Systems Engineering

3.2.1. Risk and Opportunity Management

The contractor shall implement a risk and opportunity management process for the depot support program, the security program, management and information processes, upgrades and modifications, the transition to sustainment processes, organization level

9 Page of 39 support system procurement and any additional efforts approved by the Government.

Risk status/updates and burndown plans shall be briefed at the Kickoff Meeting and at least quarterly. Risk/status updates at the program level and above shall be presented during PMRs. Risk/status updates may be required more frequently if the contractor or PM deems necessary. Such issues and/or risk reporting are in addition to previous requirements and will continue until contractor and PM agree that the risk and/or issue(s) are mitigated to a level that quarterly reporting is sufficient. (Risk and Opportunity Management Plan, CDRL A027)

3.2.2. Configuration Management

The contractor shall establish and implement a formal Configuration Management (CM) program as documented in a contractor-developed, Government-approved CM Plan.

Among the specific items of interest are a) change control process and b) problem reporting, tracking and resolution process. The contractor shall maintain a configuration management staff throughout the period of performance capable of developing and maintaining an accurate list of system hardware and software changes, via the AF Form 1067 (Modification Proposal) process, and other Depot Support and Sustaining Engineering (DS&SE) issues showing their current status. Furthermore, the contractor shall maintain and control the established technical baseline for each system and the engineering and programmatic documentation produced under this effort. The Data Management activity employed by the contractor shall be capable of producing and distributing current versions of documentation and managing the changes with review comments and implemented changes.

3.2.2.1. Operational Baseline

The contractor shall maintain a Government approved operational baseline of the fielded systems. This baseline will be represented in as-built drawings (e.g., hardware configuration items), Software Management Plan and Version Description Documents (VDD) (e.g., software configuration items) and other similar documents. For Engineering Change Notices/Engineering Change Orders (ECN/ECOs) and/or changes requested by the Government, the contractor shall develop, update, maintain and deliver the engineering data set used to define the Operational Baseline in accordance with CDRL A008 for Product Drawings, Associated Lists and Technical Data Package.

(Product Drawings/Models and Technical Data Package, CDRL A008)

The contractor shall identify, recommend and provide updated technical orders and supplemental training program for complex operations and maintenance changes. The contractor shall develop and provide systems operations and maintenance training IAW with the system’s Technical Orders or manuals. The contractor shall deliver this supplemental information in the form specified in the CDRL. (Training Material, CDRL A021)

3.2.2.2. CM for System and Equipment Upgrades

For upgrades, the contractor shall establish, implement and maintain CM practices and procedures as defined in its corporate command media. The contractor shall maintain and update the operational baseline level Configuration Item (CI) data for each configuration released to and/or installed in the field. The contractor shall label each configured item (installed or on the shelf, media included) according to the DoD and

10 Page of 39

SMC/SY Unique Identification (UID) guidance provided as compliance documents for this effort.

3.2.2.3. CM Library

The contractor shall establish and maintain a CM library function.

3.2.2.4. Configuration Control

The contractor shall provide configuration control of class 1 Engineering Change Proposals (ECPs) related to the Government's configuration control of the operational baseline of SCDS II systems. The contractor shall not make any changes to the approved operational baseline without formal Government approval. All changes to system baseline shall be approved by SMC/SY CCB Processes. (Engineering Change Proposal, CDRL A012)

3.2.2.5. Configuration Audits

The contractor shall use Quality Assurance (QA) personnel to accomplish configuration audits to include upgrades and other changes and/or as directed by the Government.

Procedures shall be documented in the Contractor's CM Program.

3.2.3. System Safety

The contractor shall emphasize safety management throughout the life-cycle of the system. The contractor shall investigate safety risk reduction options for any identified safety hazards and/or safety concerns. The contractor shall develop and deliver a SCDS II Systems Safety Management Plan. (Systems Safety Management Program, CDRL A025)

3.2.4. System Changes, System Upgrades, and System Procurement

3.2.4.1. Integration, Test, & Installation

The contractor shall develop, integrate, test and install system upgrades. The contractor shall accomplish system changes and upgrades through:

Systems engineering: the application of a systems engineering approach that optimizes total system performance and minimizes total ownership costs. A modular, open-systems approach shall be employed, where feasible

Design reviews and audits (Presentation Material, Conference Agenda & Minutes, CDRL A016)

Software/Hardware: Integrated hardware and software must meet established system requirements

Developing ECNs, and ECOs to change the product and operational baseline configurations (Product Drawings/Models and Associated Lists and Technical Data Package, CDRL A008)

Developing engineering drawings, specifications, QTPs and ATPs (Technical Data Package, CDRL A008)

11 Page of 39

Accomplishing and delivering upgrade provisioning (Technical Data Package, CDRL A008)

Upgrade and deliver all Technical Orders (TOs), contractor written operation and maintenance manuals, maintenance plans, training material and other miscellaneous technical data as directed by the Government in accordance with Operator and Maintainer Tech Order/Manuals. (Technical Order/Manuals-Operator, CDRL A019; Technical Order/Manuals-Maintenance, CDRL A020)

Support installation, integration, testing, activation, and operational acceptance in support of system turnover to the user.

3.2.4.2. System Procurement

The contractor shall perform system procurement as directed by the Government.

In all cases, the contractor shall leverage existing/previously designed technical data.

The contractor shall perform minimal non-recurring expense (NRE) design work as part of the procurement activity. In the instance where NRE is required, it shall be used to provide form, fit, function and interface replacements to address obsolete HW or to address similar type issues.

3.2.5. Software Maintenance

3.2.5.1. Depot Level Software Maintenance

The contractor shall perform PM-coordinated depot-level software maintenance as required. Depot-level software maintenance is defined as software maintenance performed on software packages as part of system changes to include: software anomaly resolution and patch updates. The contractor shall have the capability to support the development and modification of system software and conduct regression testing prior to the installation of the software onto operational systems. The contractor shall develop and implement a Software Development and Sustainment Plan (SDSP) for the overall SCDS II contract IAW CDRL A024. The SDSP shall be a generalized PSI-level process/approach to managing SW and will describe the standards, specifications, military material (e.g., weapon system and their components, space control systems and their components, automated test equipment and test program, sets, and systems integration laboratories). Software maintenance includes activities necessary to: correct errors in the software; add incremental capability improvements (or delete unneeded features) through software changes; and adapt software to retain compatibility with hardware or other systems with which the software interfaces. The contractor shall provide updates to plans and procedures for SW management on the SCDS II contract. System specific SW Development Plans and similar SW related documents shall be incorporated into the SCDS II SDSP. (Software Development and Sustainment Plan, CDRL A024)

3.2.5.2. Software Configuration Control

The contractor shall maintain configuration control of the operational software and document the process in the configuration management plan. (Configuration Management Plan, CDRL A009)

12 Page of 39

3.2.6. Quality Control (QC)

3.2.6.1. Contractor Quality Control Plan

The Contractor shall develop and provide a Quality Control Plan (QCP) to the Government per the CRDL Data Item Description. The contractor’s QCP shall clearly define the activities and processes the contractor will use to provide quality services/products/performance throughout the SCDS II contract PoP. The contractor’s QCP shall establish measures of effectiveness that directly correlate to the Service Summaries of the PWS (See section 4). At a minimum, the QCP shall contain the following items:

a) A description of the inspection system to cover all services. Description shall include specifics as to the areas to be inspected on a scheduled and unscheduled basis, frequency of inspections, and the title and organizational placement of the inspector(s).

b) A description of the methods to be used for identifying and preventing defects in the quality of service performed.

c) A description of how the records will be kept. Records must document all inspections and corrective or preventive actions taken.

The contractor shall identify a single point of contact for quality. (Quality Control Plan, CDRL A004)

3.2.6.2. Inspection Files

The Contractor shall electronically maintain records to document inspections, corrective or preventative actions taken, and the results of such actions.

3.2.6.3. Deficiency Reporting

The contractor shall perform deficiency reporting in accordance with TO 00-35D-54 and shall submit deficiency reports to the Government in accordance with CDRL A004, Quality Control Plan. (Quality Control Plan, CDRL A004)

3.2.6.4. Quality Assurance

The Government will periodically evaluate the Contractor’s performance in accordance with its Quality Assurance Surveillance Plan (QASP). The Government may inspect each task as completed and increase or decrease the number of quality assurance inspections if deemed appropriate depending on what performance dictates. The Government shall also receive and investigate complaints from customers. The Contractor shall be responsible for initially validating customer complaints; however, the Government representative shall make the final determination of the validity of customer compliant(s) in the cases of a disagreement between the Contractor and the customer.

3.2.6.5. Scope Changes

Any matter concerning a change to the scope, prices, terms or conditions of this contract shall be referred to the Contracting Officer.

13 Page of 39

All contractor personnel requiring privileged accounts or access to the system (lab or operational) requires, at a minimum

Successfully passing a background investigation equal to the classification of the highest system they will be working on

Training/Certifications

Signed User Agreements/Training Records

Signed appointment letters from the SMC ISSM

3.2.7. Configuration Status Accounting

The contractor shall document the configuration of fielded units and shall include retrofit/modification history. The contractor shall provide tracking and status for all operational baseline configuration changes.

3.3. Cybersecurity

The tailored security controls are identified in program specific documentation. Based on these designations, the contractor shall provide Body of Evidence (BoE) artifacts to show compliance with the Continuous Monitoring Plan (CMP). (CDRL A030)

The contractor shall document their cybersecurity process in the Systems Engineering Management Plan (SEMP). (CDRL A028)

The contractor shall establish a cybersecurity process to plan, organize, and manage program efforts and work with the Government on identifying contractor process controls to achieve maximum security and survivability of the system in accordance with NIST SP 800-53, Joint Special Access Program (SAP) Implementation Guide (JSIG), CNSSI No. 1253, CNSSI No. 1253 Classified Overlay, RMF Knowledge Service (website) including assessment procedures, DoD Instruction (DoDI) 8500.01, DoDI 8510.01, and the SMC/SY Cyber Security Standard Operating Procedures (SOP). For systems that are initially under the DoD Information Assurance Certification and Accreditation Process (DIACAP), the contractor shall transition the system to the Risk Management Framework (RMF) in accordance with DODI 8510.01.

Contractors must provide descriptive Plan of Objectives and Milestones (POAM) for resolving findings as required for sustainment of the system authorization. (CDRL 030)

The contractor shall configure all system components IAW DISA Security Technical Implementation Guides (STIGs). Custom code software components shall meet the requirements of the Application Security and Development STIG. Open source software use shall be approved by ISSM. (CDRL 030)

3.4. Depot Support and Sustaining Engineering (DS&SE)

Includes all required engineering and logistics tasks to ensure continued system operation and maintenance

Tasks include:

14 Page of 39

Hardware and software maintenance and repairs.

Item management consisting of equipment stock, storage, issue, and delivery. It includes an annual re-assessment of sparing levels and adjusting accordingly (upon Government approval) to include re-procurement actions.

Failure analysis of safety hazards, failure causes and effects, reliability and maintainability trends, and maintenance data collection analyses.

Root cause analysis of in-service problems to include operational hazards, deficiency reports, parts obsolescence, corrosion effects, and reliability degradation.

Develop and recommend required design changes to resolve operational issues.

Other activities necessary to ensure cost-effective support to achieve readiness and performance requirements.

Technical surveillance of critical safety items, approved sources for these items, and system configuration baseline oversight such as basic design engineering for the overall configuration including design packages, operations and maintenance procedures for fielded systems to ensure continued certification compliance.

Conduct periodic reviews of system performance against baseline requirements, analysis of trends, and development of management options and resource requirements for resolution of operational issues.

3.4.1. Engineering Support

The contractor shall maintain a sustaining engineering capability, a depot repair and test capability, perform spares repair and integration testing, perform system (internal and external) interface control, perform timely emergency site repairs/problem resolution, and support basic System Problem Request (SPR) resolution. There may be unique subsystem requirements within the Family of Systems (FoS) in which emergency site repair/problem resolution requirements will be defined. When directed by the PCO, other systems may be added. Contractor personnel assigned must have skills and training commensurate with the position necessary to support SMC/SY systems.

3.4.2. DS&SE Functional Interface Control

The contractor shall:

1) Identify, document and control all functional and physical external interfaces/specifications of the systems

2) Establish mechanisms that allow the exchange of information and data for items and issues pertinent to systems and depot operations

3.4.3. Depot Support Facility (DSF)

The contractor shall establish and maintain DSFs, as required, to support space control activities within the scope of this contract. The contractor shall establish and maintain DSF equipment and conduct item analysis, repair and conduct tests in relation to program specifications. The contractor shall have the capability to modify system SW and conduct regression testing prior to the installation of any SW or changes to any HW

15 Page of 39 onto the operational system. The contractor shall leverage, as appropriate, the DSF for cybersecurity support and management, technical order development/maintenance, and technical documentation management. The contractor shall obtain and provide facility space, at the appropriate protection levels required to facilitate execution of the aforementioned tasks. The contractor shall implement a DSF preventative maintenance program.

3.4.4. DSF Support Equipment

The contractor shall maintain the support equipment necessary to operate and maintain the DSF and meet the support requirements of this contract. The contractor shall develop and maintain a list of support equipment to include the following information:

a) Item description

b) Quantity (required and available)

c) Government Furnished Property (GFP) and Contractor Furnished Property (CFP)

d) This information shall be maintained in an appropriate database as required for the appropriate SMC/SY space control systems

3.4.5. Engineering Assistance

The contractor shall provide telephone support in accordance with system requirements. If a noncritical issue cannot be resolved at the organizational level, the discrepancy will be corrected the following business day or deferred to the next scheduled site visit. Critical failures will be addressed and approved separately by the Government program manager. During real world contingencies and scheduled/approved exercises, the contractor shall maintain a 24-hour telephone number and establish a mechanism for on-call support. The contractor shall provide verbal technical telephone support within one hour of the initial telephone call. When telephone conversations fail to resolve the issue, the contractor shall immediately notify the Government that potential fly-away support is required.

3.4.6. Depot Level Inspections (DLIs)

Contractor will conduct maintenance to include scheduled depot level maintenance at CONUS and OCONUS sites on systems identified in Table 2-1 IAW appropriate system technical orders or DLI procedures.

3.4.7. Emergency Depot Level Maintenance

The contractor shall provide specialized maintenance and/or engineering support as the Government program manager and mission requirements dictate. The Government will task the contractor for on-site support and will identify the requested response time. As directed by the Government, the contractor shall provide supplies and services necessary for flyaway assistance to be on site within 24 hours for CONUS support and 72 hours for OCONUS support to analyze the problem and resolve the issue. The contractor shall provide a report to the Government within five working days after issue resolution outlining the problem, action to resolve, and any recommended

16 Page of 39 changes/follow-on actions. (Emergency Depot Level Maintenance Resolution Report, CDRL A010)

3.4.8. Failure Analysis Corrective Actions Report (FACAR)

The contractor shall establish and maintain a failure tracking and investigation program.

Upon system component and/or sub-component failure to mission, system safety, or security, the contractor shall perform a failure analysis. The contractor shall notify the Government when the analysis begins and provide a written report of the results as well as corrective actions that need to be taken. Failure Analysis Reports in contractor format shall be submitted. (Failure Analysis Corrective Action Reporting, CDRL A006)

3.4.9. Diminishing Manufacturing Sources and Material Shortages (DMSMS)

The contractor shall establish and implement a parts obsolescence mitigation program.

The contractor shall provide a vanishing vendor resolution service to ensure no gaps in the basic supply support for the program and allow the Government time to make an end-of-life purchase, if necessary. The contractor shall conduct an annual LRU review and publish those results IAW CDRL A005 (Diminishing Manufacturing Sources & Material Shortages List).

3.4.10. Software Licensing

The contractor shall establish a software licensing database that includes number of licenses, expirations and planned purchases. A snapshot may be requested for reporting at PMR.

3.4.11. System Reliability, Availability and Maintainability (RAM)

The contractor shall analyze maintenance actions, to include those in the approved AFSPC Maintenance Data Collection (MDC) system, and recommend additional or changed maintenance procedures, substitute parts or other actions to maintain RAM specifications or improve system RAM. Calculations for system availability (Ao) operational requirements and dependability (Do) will be done IAW AFPAM 63-128.

3.4.12. Item Management

3.4.12.1. General Overview

The contractor shall stock, store, issue, ship and track (Item Management) program spares and Government property using a government approved supply tracking system.

The contractor shall maintain existing supply databases to the extent necessary to track supply activity.

Emergency shipments of in-stock spares shall be processed and shipped within 24 hours of notification. Routine shipment of spares shall be processed and shipped within five (5) working days of notification or arrival from vendor. If the items to be shipped are classified refer to paragraph 3.5.17.4.1.

3.4.12.2. Item Unique Identifier (IUID)

The contractor shall develop and execute an IUID implementation plan for hardware procured and maintained under this contract. The contractor shall deliver the plan as an annex under CDRL A002, Integrated Support Plan. The contractor shall implement IUIDs on all legacy hardware that fall within the DoD guidance and the most recent

17 Page of 39 approved SMC/SY IUID Plan. The contractor shall deliver IUIDs in accordance with DFARS clause 252.211-7003, if there are any disparities between the DFARS clause and the SMC/SY plan the former shall prevail. For classified hardware and software, the contractor shall deliver IUIDs to approved Government database. (Integrated Support Plan, CDRL A002)

3.4.12.3. Forward Supply Point

At Government request, the contractor shall establish a forward supply point in compliance with AFI 21-116. The forward supply point shall be located as directed by the Government. The contractor shall, as part of system changes or when directed by the Government, identify, list and provide updates to the forward supply point spares list hand in accordance with the Parts List/List of Repairables, CDRL A007. (Parts List/List of Repairables, CDRL A007)

For Foreign Military Sales (FMS) cases, the contractor will maintain an inventory control and accounting system adequate to reflect the usage and disposition of all U.S.

Government and contractor-owned property that has entered the country duty-free under any Letters of Agreement.

3.4.12.4. Spares Management

The contractor shall establish and maintain a depot level test, check out, repair, and product assurance service for field, depot, and DSF repairable equipment items and spares (for both critical and non-critical spares). The contractor shall establish a process to allow Government visibility into individual item repair costs (both local and vendor) and to acquire Government approval of repair costs that exceed the 75 percent of estimated replacement costs or $25,000, whichever is less. The contractor shall establish a repair cost accounting system that can specifically identify individual item costs (e.g. individual item repair charge numbers).

3.4.13. List of Repairables

The contractor shall develop and maintain a list of repairable items in the operationally fielded systems and DSF. The Government will approve and use this list to direct the contractor on repair actions. If the depot receives requests for items not on the approved repairable list, the contractor shall provide the Government with an item disposition recommendation within five (5) working days and subsequently proceed as directed by the Government. (Parts List/List of Repairables, CDRL A007)

3.4.14. Spares Testing

The contractor shall establish, maintain and implement a spares testing program as part of the quality and product assurance program. The contractor shall document the processes and procedures to be implemented to accomplish required spares testing in the Government approved Quality Assurance Program Plan. The contractor shall ensure that processes are in place and depot spares function properly and are ready to be placed in service when needed. (Quality Control Plan, CDRL A004)

3.4.14.1. Spares Procurement

The contractor shall provide item procurement services for all spares replenishment requirements. To the greatest extent possible, the contractor shall use the program Life Cycle Sustainment Plan (LCSP) and Logistics Planning Document (LPD) for new

18 Page of 39 systems (or Logistics Management Information (LMI) summaries where LMI is already implemented).

3.4.14.2. Supply Chain Risk Management (SCRM)

The contractor shall plan for and implement countermeasures that mitigate the risk of foreign intelligence or foreign influence, technology exploitation, supply chain and battlefield threats, and vulnerabilities that result in Level I and Level II protection failures of the system. Foreign end items - including hardware, software, and firmware – shall not be selected unless there is no technical US equivalent. If foreign products are selected, the contractor shall justify product selection and support government risk assessment activities including software review and intelligence assessment.

The contractor shall develop and implement a Counterfeit Prevention Plan (CDRL A029) Counterfeit Prevention Plan, DI-MISC-81832) to describe how they will prevent procurement of counterfeit materials and parts, including mechanical piece/parts and electronics components procured for sustainment of those systems and assemblies.

Counterfeit material is defined in DoDI 4140.67.

3.4.15. Hardware Repair and Maintenance

The contractor shall perform depot-level hardware repair and maintenance. Depot-level hardware repair and maintenance is defined as material maintenance or repair requiring the overhaul, upgrading or rebuilding of end items (including weapon systems), subsystems, parts, assemblies or subassemblies and the testing and reclamation of equipment as necessary for maintenance or repair. The contractor shall document all repair actions in a sufficient manner to allow analysis that shows hours spent on repair, nature of the failure, corrective action taken and any administrative or logistical delays.

3.4.16. Disposition

The contractor shall establish a plan for the reutilization or disposal of all system inventories, to include site remediation as required in accordance with contractual requirements, environmental, safety, and occupational health (ESOH) plans, and compliance documents established for each system sustained under the SCDS II contract when directed by the PCO.

3.4.17. Packaging, Handling, Shipping and Transportation (PHS&T)

The contractor shall establish and maintain a PHS&T program to ensure necessary resources are identified, and used to adequately package/preserve, handle, store and transport equipment. The PHS&T program will protect equipment and material by preventing deterioration and damage during storage, handling and shipping activities.

Each LRU considered for use will be evaluated for risk of inducing failure during cargo handling and transportation processes. If risk cannot be abated or controlled through normal packaging and preservation techniques, the item should be afforded appropriate special packaging. All unique or special packaging will be documented in the system TO to ensure equipment is protected. PHS&T processes and procedures should be addressed in the Integrated Support Plan (CDRL A002).

3.4.17.1. Packaging

The contractor shall package all shipments consistent with industry standards.

Packaging of equipment and spare parts for shipment or storage at the depot is handled

19 Page of 39 using best commercial practices based on American Society for Testing Material (ASTM) Designation D3951-98. The contractor will provide a packaging plan that identifies any unique component packaging requirements. Packaging should protect internal components from exposure to water, humidity, electrostatic discharge (ESD) and chemicals. Packaging considerations should include environmental elements and minimize size, and ensure all shipments and documents are marked and labeled with correct security and release statements as appropriate. All ESD sensitive equipment will be identified in the TO and packaging and handling material will be initially provided to the site.

3.4.17.2. Handling

The depot will provide instructions in the packaging plan to prevent damage during handling operations. The instructions will consist of any unique handling procedures, and identify any required material handling equipment. The contractor will identify all system components that have volatile and non-volatile internal components and document the appropriate sanitization/handling procedures in the applicable technical order. All hazardous materials shall be identified IAW AFMAN 24-204 and documented in the system technical order and the packaging plan. Equipment handling procedures will comply with Occupational Safety and Health Agency (OSHA), Air Force Occupational Safety and Health (AFOSH), classified handling procedures, and MIL- STD-1472G, items requiring multi-person lift, Safety Data Sheets (SDS) items that require special handling/certification.

3.4.17.3. Storage

The contractor shall ensure that security requirements are followed for the storage of classified and unclassified materials. The contractor shall also ensure that Safety Data Sheets (SDS) are available to all personnel as required.

3.4.17.4. Shipment

The contractor shall provide the necessary shipment and transportation products and services. The contractor shall include an estimate for all transportation and shipping expenses in the cost of a change. The contractor shall notify the Government with sufficient lead time as to not impact schedule requirements when commercial transportation is seen as inadequate or when commercial delivery cannot be accomplished (transportation strikes, natural disasters, etc.). Depending on cost and schedule constraints, the contractor shall utilize either commercial shipping or military airlift.

3.4.17.4.1. Classified/Sensitive Shipments

Shipments of classified or sensitive equipment shall be handled, transported, transmitted, and protected in accordance with the JAFAN 6/0, the Contract Security Specification, DD Form 254 and the program security classification guide. The contractor shall coordinate with the Government before release of classified material for shipment.

3.4.17.5. Transportability

For baseline changes and/or as requested by the Government, the contractor shall ensure that transportability design parameters are considered during all phases of

20 Page of 39 design development. As required, deployable components shall be capable of fixed-wing transport in accordance with MIL HDBK-1791, designing for Internal Aerial Delivery in Fixed Wing Aircraft, and semi-improved roads via a GFE prime mover or shipper. The system design is based on using military aircraft for worldwide transport.

3.4.18. Training

3.4.18.1. Training Material

The contractor shall archive training data to include training requirements for changes to the design, operation, and maintenance of the system, units and DSFs. The contractor shall deliver all changes to training data in accordance with the Training Material CDRL.

The contractor shall provide training and associated materials for Government personnel and contractors on system hardware and software intricacies, operational procedures and maintenance. (Training Material, CDRL A021)

3.4.19. Technical Data Package

The contractor shall establish and maintain a technical data package comprised of the following types of data: configuration identification data (engineering drawings), performance data (specifications), design qualification test plans and procedures (QTPs), production acceptance test plans and procedures (ATPs), provisioning data (supply support and LMI/LPD), reports and other program data. The contractor shall deliver updated technical packages prompted by upgrades and/or as directed by the Government. The contractor shall make all technical data available for Government review and/or audit and shall assist the Government in locating and retrieving any data as requested. The contractor shall make and deliver copies of any technical data requested by the Government for retrieval and reproduction efforts.

3.4.20. Maintenance Data Collection

The contractor shall collect maintenance data IAW TO-00-20-2 using any Government-approved system or process to calculate system down time due to scheduled or unscheduled maintenance actions. Upon Government direction, the contractor shall revise the maintenance data collection elements as required to reflect the operational system. (Maintenance Data Collection; CDRL A022)

3.4.21. Contractor Travel

The contractor shall travel world-wide in support of this program as directed and approved by the Government on an individual trip basis. The contractor shall use administrative orders for overseas travel as provided by the Government. All personnel traveling overseas shall have current training and Government-required approvals prior to departure. These activities may include training such as Survival, Evasion, Resistance, and Escape (SERE) 100, country-specific training, Aircraft and Personnel Automated Clearance System (APACS), and Synchronized Pre-Deployment and Operational Tracker (SPOT).

3.5. Studies and Analysis

The contractor shall conduct studies and analysis projects in support of the basic program mission and deliver study results to the Government in accordance with the Technical Report-Studies CDRL. This includes, but is not limited to, analyses to:

reduce life-cycle costs; improve availability and maintainability; replace obsolete or

21 Page of 39 unsupportable equipment; evaluate the potential impact from other activities by other related programs such as battle management and command, control and communications; performance requirement definition, technical capabilities analysis;

electronic attack effectiveness; assessment of sister programs; the evaluation of future capability enhancements; and emerging capabilities. When conducting studies and analysis the contractor shall leverage pre-negotiated wrap rates. Studies that are deemed high risk or have high technical complexity may be awarded via a SOW and a RFP provided by the Government. (Technical Report – Studies/Services, CDRL A023)

3.6. Transition to Sustainment

The contractor shall, at the request of the Government, transition emerging systems and capabilities along with the infrastructure and system support tools required to meet operational and maintenance requirements, into sustainment under the SCDS II contract. Depot and Sustaining Engineering Support Services for each transitioned system shall be provided. All formal transitions shall be initiated via formal direction from the Government Procurement Contracting Officer (PCO). The contractor shall submit a proposal establishing transition and anticipated sustainment costs (both labor and material) for the contract year or as directed by the PCO.

The contractor will execute transitions to include but is not limited to the performance of the following: (1) analysis of existing program documentation, (2) spares analysis/provisioning, (3) technical order (TO) development (operator, maintainer, system administrator, etc.), (4) technical data package development and (5) training consistent with the functional areas in this PWS.

3.7. Support to Operations

The contractor shall provide support to operations when directed by the Government.

The contractor shall support the Government in performing operations, maintenance, and/or training as required in place of Government maintainers at garrison and/or operational/field locations. This may include CONUS and OCONUS locations. All activities performed under contractor maintenance shall be performed IAW a Government directed Statement of Work (SOW) and shall reflect established agreements between the Government program office and the operational unit.

4. Service Summary (SS)

4.1. General

The contractor shall meet all service summaries in accordance with the associated performance threshold to ensure minimum essential services are provided to sustain contract systems. The contractor shall also work with the Government to establish Performance Based Agreements (PBAs) with user organizations. PBAs shall capture the lower level responsibilities of both the contractor and the user organizations to ensure the contract services, including those captured in service summaries and those that are above and beyond the established scope of service summaries, are successfully delivered.