Sources_Sought_Synopsis_PWS_-_1_Feb_18.pdf

LAUNCH AND EARLY ORBIT, ANOMALY RESOLUTION AND

DISPOSAL OPERATIONS (LADO)

SUSTAINMENT

PERFORMANCE WORK STATEMENT (PWS)

1 February 2018

Prepared by:Ogden Air Logistics Complex

Hill Air Force Base, Utah 84056

2 | P a g e

TABLE OF CONTENTS

SECTION TITLE PAGE

1.0 GENERAL INFORMATION

2.0 APPLICABLE DOCUMENTS

3.0 CONTRACTOR TASKING / REQUIREMENTS

4.0 GENERAL REQUIREMENTS

5.0 PLACE / PERIOD OF PERFORMANCE SCHEDULE

6.0 SERVICE SUMMARY (SS)

APPENDIX A: ACRONYM LIST

APPENDIX B: GOVERNMENT FURNISHED PROPERTY

APPENDIX C: SAFETY

APPENDIX D: POTENTIAL INDIVIDUAL TASK ORDER LIST

3 | P a g e

1.0 GENERAL INFORMATION

1.1 Introduction

1.1.1 This Performance-Based Work Statement (PWS) outlines the tasks and duties required of the contractor to support the OO-ALC 517th SMXS. The intent of this PWS is to obtain engineering services for existing

(known), and future (unknown) activities needed in support of Launch and early orbit, Anomaly Resolution, and Disposal Operations (LADO) sustainment until its replacement, the Next Generation Operational Control

System (OCX) is fully operationally.

1.2 Scope of Services

This PWS describes the technical requirements necessary to create and implement a sole-source Indefinite

Delivery Indefinite Quantity Contract (IDIQ) contract that provides engineering services in support of existing and future 517th SMXS requirements. The objectives and requirements identified within this PWS are described in general terms. Each individual task order will address specific task requirements, project scheduling, and other related performance criteria, as applicable. This requirement will not include personal services or inherently governmental functions. The contractor shall comply with this basic PWS and each individual task order PWS(s) in their entirety.

1.3 Background

Global Positioning System (GPS) is a space-based radio navigation, time distribution and Nuclear Detonation

(NUDET) Detection System (NDS). Its mission is to provide precise, continuous, all weather, three dimensional (3-D) position, velocity, timing and NUDET information to properly equipped air, land, sea, and space-based users. GPS serves both military and civilian users.

GPS consists of three segments: Space Segment (SS) which nominally consists of 31 operational satellites in 6 orbital planes with up to 6 satellites appropriately spaced in each plane; User Segment which consists of the

NUDET Detection users and Navigation users; and the Control Segment (CS) which consists of the LADO system and the Operational Control Segment (OCS).

LADO sustainment consists of three major functions: 1) Telemetry, Tracking and Commanding (TT&C), 2)

Mission Planning, and 3) LADO Simulation. The TT&C provides the commanding of the satellite(s), sending and receiving telemetry as well as tracking data. Mission Planning is responsible for the planning and execution of satellite maneuvers during launch and early orbit (LEO), anomaly resolution and disposal activities. The LADO Simulator provides a simulation of telemetry, commanding and selected subsystems functionality for the different block type satellites forming the GPS constellation. It also provides simulation of specified maneuvers and anomalies, as well as ground facilities utilized for the LADO mission.

In 2010, the Air Force awarded a contract to deliver a modernized GPS command and control system called

OCX. OCX will add many new capabilities to the GPS control segment, including the ability to fully control the modernized civil signals (L2C, L5, and L1C) as well as command and control GPS III satellites. OCX

4 | P a g e provides a more robust cyber security infrastructure as well as improved position, navigation, and timing

(PNT) performance. GPS OCX will lift the cap on the number of satellites in the GPS constellation, allowing more satellites and better geometry in hard-to-reach areas such as urban canyons and mountainous terrain. The

OCX program has experienced delays in which OCX Block 1/2 delivery is not expected until Objective 2022 and Threshold 2023.

2.0 APPLICABLE DOCUMENTS

2.1 Mandatory Compliance

2.1.1 The following documents are part of this PWS and subject to change without notice. The contractor shall obtain any forms and publications expressly required to perform the work in this contract via internet at: www.e-publishing.af.mil or www.dtic.mil/whs/directives. In the event that a form or publication is not available online, the Air Force program office or Contracting office will provide the form, instruction, or publication to the contractor upon written request (e-mail is acceptable). In the event that laws, regulations, Technical Orders, Air Force Instructions, Air Force Material Command Instructions, or documents listed below change during the term of this contract, the contractor is required to comply as such changes come into effect. In the event a conflict is found between document revisions, the contractor shall seek Government direction.

Document Title Publication Date

2 SOPS Instruction 10-5 Current Version

AFI 63-131; Modification Program Management 6 Nov 2009

AFPD 63-17 Technology and Acquisition Systems Security Program Protection

26 November 2001

DCID 6/3 Manual 11 December 2003

DoD 5220-22M National Industrial Security

Program Operations Manual

28 Feb 2006

DoDI 8500.01 Cybersecurity 14 March 2014

DoDI 8510.01; Risk Management Framework

(RMF) for DoD Information Technology (IT)

12 March 2014

DoDI 8530.01 Cybersecurity Activities Support to DoD Information Network Operations

7 March 2016

DoD 8570.01-M Information Assurance

Workforce Improvement Program

10 November 2015 http://www.dtic.mil/whs/directives

5 | P a g e

GPOI 63-1101 Technical Baseline Configuration

Management Process (TBCMP)

29 October 2014

GPS Security Classification Guide 30 September 2008

ICD-GPS-601; NAVSTAR GPS Space to

Control Segment Interface

Rev C dated 28 August 2014 with

IRN-601C-001 dated 14 April

ICD-GPS-804; NAVSTAR GPS Architecture Evolution Plan (AEP) Operational Control Segment (OCS)/Launch and Early Orbit, Anomaly Resolution and Disposal (LADO) to NAVSTAR GPS Next Generation Operational Control Segment (OCX)

Rev B, dated 14 August 2014

MIL STD 130N; Identification Marking of U.S.

Military Property

Rev N dated 17 December 2007

MIL STD 882E; Department of Defense

Standard Practice, System Safety

11 May 2012; Tasks 101, 102, 105, 204, 205, 206, 301, and 303

SMC/GPL OI 63-131 Modification Management and Technical Baseline Control of GPS OCS

28 June 2016

2 SOPS OI Training updates, schedule requests Current Version

2 SOPS MCB Format Presentation products Current Version

Braxton Configuration Management Plan Current Version

SAFB Form 19, AF 332 (construction and facility upgrade forms)

Current Version

SMC Standard SMC-S-001; Systems Engineering

12 July 2010

SMC Standard SMC-S-002; Configuration Management

13 June 2008

SMC Standard SMC-S-003; Quality Systems 13 June 2008

SMC Standard SMC-S-012; Software Development for Space Systems

13 June 2008

SMC Standard SMC-S-019; Program and Subcontractor Management

11 August 2008

6 | P a g e

SMC Standard SMC-S-021; Technical Reviews & Audits for Systems, Equipment and Computer Software

15 September 2009

2.2 Other Documents

Additional compliance documents may be cited in each individual task order as it applies.

3.0 CONTRACTOR TASKING / REQUIREMENTS

3.1 Task Order Requirements

The contractor shall perform tasks in accordance with separately issued task orders providing engineering, technical, and support services, as specified therein. All products developed under task orders resulting from this basic IDIQ contract shall be considered Government work and shall have no license encumbrances. All data shall be developed and provided in accordance with the data right clauses in the basic IDIQ contract and as identified in the individual task order. Unless the contractor has expressed a claim to providing data to the

Government with less than unlimited data rights, the Government will assume unlimited data rights (see

DFARS clause 252.227-7013 of the individual task order for definition of data rights). See section 3.3(r) for additional required task order technical data rights certifications. The contractor shall not include proprietary markings on any deliverables and updates. One page is authorized denoting the “Prepared by” contractor name and address. Task orders issued may include one or more of the following engineering services:

3.1.1 Technical Configuration Management

The Contractor shall, as required by individual task order, support configuration specialists in the design and development of existing and future software, hardware, systems, and subsystems to include any required performance criteria, parameters, characteristics, interrelationships, and operational requirements; while adhering to applicable guidelines, policies, and regulations. Activities include, but are not limited to, complex and comprehensive analysis, tests, data production, design criteria formulation, and process development and execution, construct standards and test plans, develop established models, and identify shortcomings in design and/or performance; develop and implement systematic, disciplined, and quantifiable approaches; generate documents and presentations for both formal and informal reports, and briefings.

3.1.2 Technical Writing/Technical Orders/Technical Data Package

The Contractor shall, as required by individual task order, support technical writing and editing requirements.

Technical writing and editing may require contractor support for publication review, photographic documentation (e.g., mission event and system description). Technical writing activities include, but are not limited to, developing user manuals, training materials, installation guides, proposals, and graphics. Technical editing activities include, but are not limited to, development and publication of technical manuals, reports, papers, briefings, and documentation packages. Technical Order and Technical Data Package activities

7 | P a g e include: Technical Orders (T.O.s), manuals, and/or Technical Data Packages (TDPs), system specificiations, including engineering drawings, associated lists, and the preparation and/or review of new or existing drawings and specifications.

3.1.3 Technical Illustration & Drafting

The Contractor shall, as required by individual task order, support technical illustration and drafting requirements. Contractor illustration and drafting will range from basic to complex tasks supporting new, recurring, and revision work generated from various sources of information and precedents. Certain tasks may require further illustration and drafting support from the contractor to generate plans, layouts, drawings, and models from basic layouts, established references, and standard data. Activities include, but are not limited to, computer-aided drafting (CAD), developing drawings, schematics, graphics, 3-D models, drafting, graphic design, photographic editing, charts, and graphs.

3.1.4 Configuration/Data Management

The Contractor shall, as required by individual task order, provide configuration and data management support, to apply sound program practices. The contractor should support applicable objectives in establishing and maintaining the consistency, attributes, and requirements of a product or system through the evolvement of a mature technical baseline and lifecycle. Activities include, but are not limited to configuration identification, configuration control, configuration status accounting, configuration auditing, data control and management, data auditing, and product release.

3.1.5 Installation

The Contractor shall, as required by individual task order, install, or assist the government in installing, component or system hardware and software as specified by individual task orders. When such installation is required, the Contractor shall assist the Government in identifying all equipment, utilities, and associated activities required prior to and during installation at the installation site. The Contractor may be tasked to assist the government in identifying required Government Furnished Equipment (GFE) and Government Furnished

Material (GFM) necessary for installation.

If limited incidental / minor construction is required for installation of equipment, coordination between the government program manager/requiring activity and Base Civil Engineering (BCE) will be required and shall involve use of an AF Form 332 or equivalent before work can begin. The contactor may be required to participate in the coordination and approval process.

3.1.6 Technology Insertion

The Contractor shall, as required by individual task order, integrate new technologies into existing system architectures. Hardware and software redesign and software automation tasks supported by the contractor

8 | P a g e should consider the latest technologies available to increase lifecycle capability effectiveness. Contractor shall perform analysis of current system impact of technology insertion, incorporate new software or hardware components as the result of additional system capability requirements or advanced development. Activities include, but are not limited to, the design/redesign, assembly/reassembly, and re-certification of systems, sub-systems. To the greatest extent possible, the Government will provide known information on applicable technologies available for the projects as described at the task order level.

3.1.7 System Engineering

The Contractor shall, as required by individual task order, support systems engineering activities using an interdisciplinary approach to evolve and verify activities. Contractor support may require an integrated, total life-cycle approach, including but not limited to, development, production, verification, operations, support, and disposal for systems and subsystems. Activities include, but are not limited to, providance and/or application of requirements management processes, system design, interface design techniques; and work breakdown structures for detailed investigation, diagnostic testing, repair/resolution, installation, configuration and upgrading on hardware, software, networked, and standalone systems, and subsystems.

3.1.8 Software Engineering

The Contractor shall, as required by individual task order, provide software engineering support for the implementation of repeatable, defined, and documented software and firmware development processes, including the performance of requirements management, project planning, project tracking and oversight, quality control, quality assurance, and software process capability improvements. Related support functions may include, but are not limited to software development processes, integrated software management, and software product engineering. The contractor should utilize best practice design and coding standards (e.g., interoperability, modularity, portability, reusability, readability, sustainability, maintainability, reliability, availability, and securability). The contractor shall utilize government systems in place for controlling software documentation and code, including software requirements languages and program design descriptions.

Activities include, but are not limited to: analysis, documentation, evaluation, design, execution, integration, isolation, modification, maintainenance, reconfiguration, planning, preparation, technical advisement, removal, replacement, reverse engineering, testing, and verifications of existing software utilizing multiple platforms, creation/re-creation design guidance, computer system design, model simulations, software code and binaries, and legacy software sustainment, refactoring, migration, modernization and transformation.

3.1.9 Hardware Engineering

The Contractor shall, as required by individual task order, provide hardware engineering support for the research, design, development, and test of computer systems, non-computer devices that incorporate processors, and other computer components; while assuring computer hardware components work together with applicable software. Activities include, but are not limited to: design/creation of System Integration Labs

(SILs), Line Replaceable Units (LRUs), Interface Test Adapters (ITAs), test stand and test stand Graphical

9 | P a g e

User Interfaces (GUIs), computer programming in a hardware description language (HDL), and other hardware design/re-design and development.

3.1.10 Test Engineering

The Contractor shall, as required by individual task order, provide test engineering support to define and develop test programs, plans, and procedures, conduct testing, evaluate and/or document the results of testing and evaluation. Types of testing may include, but are not limited to, component, development, system compatibility, acceptance, functional, integration, qualification, and beta on hardware, software systems and subsystems. In the event that testing requires a phased approach, contractor support may be required for implementation of corrective actions discovered in previous testing, before retesting, and other associated activities. Activities include, but are not limited to, defining, documenting, analyzing, conducting, providing technical support, and interpreting tests for software, firmware, hardware and related systems, components, or modifications.

3.1.11 Process Modeling, Analysis, and Re-Engineering

The Contractor shall, as required by individual task order, provide support for process modeling, analysis, and re-engineering of software, hardware, systems and subsystems. Contractor support may require the development of a structured approach, utilizing process characterization, to develop a baseline model defining current operation performance, success, and areas for improvement; other baseline models may require analysis to measure process improvement over a period of time. Activities include, but are not limited to, generating evaluations for adequacy, and potential contributions; and the development of process improvement plans for process modeling and improvement/re-engineering tasks, such as, process baseline, stochastic simulation modeling (when appropriate), and providing analysis and recommendations.

3.1.12 Cybersecurity

The Contractor shall, as required by individual task order, perform system/network functions in support of information assurance and cyber security activities. Contractor support may involve the elimination of identified cyber vulnerabilities to networks, attached processing and user networks, and test and development networks; and utilizing DoD Information assurance/cyber security compliant standards and requirements for software, hardware, systems, and subsystems. Activities include, but are not limited to, migrate, modernize, transform design, develop, and implement policy and procedure in support of technical security systems, information assurance, and cyber security efforts; user identification, authentication and auditing.

The contractor shall develop and update on an annual basis mission criticality analysis(-es); vulnerability assessment(s); risk evaluation(s); and identification and counter measurement implementation(s) for Mission-

Critical Functions the failure of which would result in either (catastrophic) (Level I) or unacceptable compromise of mission capability or significant mission degradation(critical) (Level II). Adapting the MIL-

STD- 882 System Safety Program definitions of criticality to mission criticality, the contractor shall define the following criticality levels (CDRL A012):

10 | P a g e

a. Level I (Catastrophic) protection failure that results in total compromise of mission capability

b. Level II (Critical) protection failure that results in unacceptable compromise of mission capability or significant mission degradation

c. Level III (Marginal) protection failure that results in partial compromise of mission capability or partial mission degradation

d. Level IV (Negligible) protection failure that results in little or no compromise of mission capability.

For each Level I and Level II Mission-Critical Function identified by the contractor in the criticality analysis, the contractor shall identify the associated logic-bearing system components (e.g hardware, firmware, and software) that implement, protect, or introduce vulnerability, to that function (hereafter referred to collectively as the “critical components”).

In coordination with the Government, the contractor shall design, develop and implement secure applications and configurations through applying applicable DoD STIGs, checklists, vendor security guidance, industry best practices, and applicable vendor product security patches. The contractor shall ensure applications are in compliance with DODI 8500.01 Cybersecurity (current version) and DODI 8551.1 Ports, Protocols, and

Services Management (PPSM) (current version) and free of all of the Common Weakness Enumeration/System

Administration, Networking, and Security Institute (CWE/SANS). The contractor shall leverage, to the maximum extent possible, automated tools to identify and remediate vulnerabilities or weaknesses in the application design/coding, such as those described in the CWE/SANS TOP 25 Most Dangerous Software

Errors http://www.sans.org/top25-software-errors/. The contractor shall submit a Software Quality Assurance

Analysis report (CDRL A004) containing how static analyisis is used within the contractor’s development lifecycle in writing and in a diagrammatic form for illustrative purposes. The contractor shall also provide details relating to the output from a minimum of two software static analysis tools used by the contractor according to the following table:

Table 1. Example Software Static Analysis Tool http://www.sans.org/top25-software-errors/

11 | P a g e

The contractor shall assist the Government cybersecurity personnel with the following activities related to the contractor’s hardware/software:

a. Provide required cybersecurity artifacts for all assigned cybersecurity controls for inclusion in the Government assessment and authorization packages for all LADO systems.

b. Provide support (e.g., system administration, database administration, data analysis) to

Government cybersecurity team for successful completion of Security Test and Evaluations

(ST&Es).

c. Perform network vulnerability scans in support of Government validation checks annually.

d. This support requires qualified and certified personnel (IAW DOD Directive 8140.01,) for both

IA and computing environments.

3.1.13 Software Assurance

The Contractor shall, as required by individual task order, provide support to assure software functions as intended and is free of vulnerabilities, either intentionally or unintentionally designed or inserted as part of the software. Utilizing current government policy and/or operating procedures the contractor may be required to assit in the investigation and application of risk mitigation proceedures and to exploit vulnerabilities at the system and sub-system level. Activities include, but are not limited to, improvements in software assurance through the development of tools and techniques; strengthining software partitioning and modularity capabilities; and theoretical and practical application of enhanced vulnerability discovery. The contractor shall demonstrate that the contractor has visibility into its supply chain for critical components, understands how supply chain risk can be introduced through those components, and has implemented or plans to implement countermeasures to mitigate such risks.

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.

3.1.14 Studies

The Contractor shall, as required by individual task order, conduct analysis to assist in the determination of requirements to cover the full spectrum of LADO sustainment, from conceptual system studies, through planning for actual equipment installs. Requirements shall be structured to encourage the use of existing tools and equipment; and the application of commercial-off-the-shelf equipment. Activites include, but are not limited to, order, design, redesign, modernize, purchase, refurbish and/or test equipment as applicable; and studies such as, levels of maintenance, support equipment, training, technical orders, configuration/commonality/refurbishment of equipment, and modification accountability. Studies may also include research, evaluation, verification, and validation of capabilities; sustainment, refactoring, migration, 12 | P a g e modernization, transformation; identifcation and assessment of relative metrics; and theoretical and applied courses of action retirement for legacy software.

3.1.16 Support Legacy Translation and Transformation

The Contractor shall, as required by individual task order, support the conversion of source code, servers, databases, and applications to modern software languages and formats to enable reuse, efficient sustainment, and transformation using. Activities include, but are not limited to, architecture, design, and implementation;

modernize source code into open and service oriented architectures; provide for enhanced functionality, interoperability, and performance.

3.1.17 On-Call Support/On-Site Support

The Contractor shall, as required by individual task order, provide support for ongoing operations that warrant extended representation as an integral part of a problem resolution and/or task assignment process at Schriever

AFB, Peterson AFB, or other locations as necessary. Activities include, but are not limited to, physical observation, monitoring, and evaluation of system performance; collect data, provide on-site assistance for operational problems, and/or perform as a liaison between Government, Contractor, and/or Subcontractor representatives.

3.1.19 Database Administration

The contractor shall provide analysis, diagnostics, and resolution assistance to LADO GPS Government

LADO Level 1 and Level 2 support personnel as required when Government personnel determine abnormalities indicate a database issue has been encountered.

The contractor shall provide all documentation and installation instructions/procedures (to include all software scripts or installation software) necessary to deliver and make functional any Oracle LADO database upgrades. The contractor shall ensure all DoD Security Technical Implementation Guides (STiGs) concerning Oracle Security are adhered to, and each Oracle patch update delivery is installed. That each

Oracle patch, or STiG compliance modification is forwarded to the 517th L1/L2 personnel with full installation documentation and procedures. The contractor shall develop and deliver procedures, (to include any scripts, batch files, or executables), to preserve legacy operational (L1)/ Test (L2) data upon the implementation of any Oracle of LADO driven database modification. This data transferal will be limited to only the immediate prior delivered version. The contractor shall provide to the Level 1/Level 2 Government support personnel documentation on all delivered Oracle procedures developed by Braxton on the function, purpose, and interdependencies that are intended as normal or maintenance scripts. The contractor shall provide to the Government a full data dictionary, and data model diagram of the existing LADO database.

This diagram will show structure and table relationships as well as a description of the purpose/intent of each table.

3.1.20 Transition/Phase-Out

13 | P a g e

The Contractor shall submit a Transition Plan that describes the process, details, and schedule for providing an orderly transition during the Contract’s Transition Term outlined in the individual task order. The objectives of the Transition Plan are: to minimize the impacts on continuity of operations; maintain communication with staff and affected communities; identify key issues and overcome barriers to transition.

The contractor is responsible for performing due diligence to ensure that all the transition activies are identified , negotiated, and completed during the Transition term. The Government will make the determination of when transition is completed and will provide formal acceptance indicating such.

Transition activities include, but are not limited to: hardware decommissioning (both GFE and contractor owned equipment), knowledge transfer, creating and maintaining collaborative and cooperative environment with other Government contractor, if applicable. The contractor shall facilitate accomplishment of a seamless transition from the current Contractor to the incoming Contractor and/or Government personnel at the expiration of the contract. The Contractor shall identify a plan and schedule for how and when it will coordinate with the incoming Contractor or Government personnel to transfer knowledge.

3.1.21 Additional Emerging Support Requirements

The contractor, as required by the individual task order, shall provide support relating to the below listed emerging support requirements that are not fully defined at this time. These requirements will be more defined in the task order work statement.

a) Hardware Procurement

b) Cybersecurity Updates or Upgrades

c) Obsolescense/Tech Refresh Upgrades

d) License Purchases/Maintenance Support Agreements

e) Operating System Updates

f) Space Vehicle Integration Support

g) GPS Launch Activities

h) LADO Technology Enhancements

i) Ground Segment Integration

3.2 Example of Potential Individual Task Orders / Projects List

For Contractor consideration, Appendix D of this PWS provides a list of examples of potential projects / task orders that may result from this basic IDIQ contract. This list of examples requirements is being provided to help the Contractors gain an understanding of the scope, type of engineering services and the level of effort

14 | P a g e involved in performing the engineering support duties anticipated under this basic IDIQ contract, specifically in support of section 3.1 of this PWS.

It should be noted that this list is for information and planning purposes only and does not constitute a

Request for Order Proposal (RFOP), an invitation for bids, a solicitation and/or an indication the Government will contract for the services contained in Appendix D nor does it restrict the Government as to the ultimate acquisition approach.

4.0 GENERAL REQUIREMENTS

These general requirements apply to all task orders issued under this basic IDIQ contract(s) unless otherwise stated in the individual task order.

4.1 Personnel Qualification

The contractor shall ensure professional and technically qualified personnel to perform assigned tasking. The

Contractor shall provide total task management and supervise contractor personnel. The Contractor’s

Technical Lead shall serve as the primary point of contact for all technical aspects of the required work. No personal services shall be performed. The Contractor shall have current working knowledge/experience of the

GPS LADO system to include TT&C development and testing procedures.

4.1.2 Performance-Based Services

Task orders issued under this basic IDIQ are considered performance-based services, not personal services;

therefore, the PWS applicable to the individual task order shall describe the work to be performed – not specific labor categories and/or number of contractor personnel. The offeror’s proposal in response to an RFOP shall include their proposed solution in terms of technical approach and the combination of skill sets from the range of approved labor categories/hours. Upon receipt of offerors’ proposals, the Government shall perform a technical evaluation that determines if the offeror’s proposed technical approach and labor categories/hours is acceptable with its associated risk rating or unacceptable/not-awardable. Therefore, the PWS applicable to the individual task order should not list specific labor categories.

4.1.3 Information Assurance Training and Workforce Management.

The Contractor shall comply with all computer and network access requirements and instructions including

DoD Directive 8570.1. Information Assurance Training, Certification and Workforce Management.

4.2 Documentation / Data / Reporting Requirements

4.2.1 Basic IDIQ Contract Data / Reporting Requirements

The contractor shall submit the following deliverables with their proposal in response to the Basic IDIQ solicitation/RFP. These documents shall support all individual task orders that result from this Basic IDIQ contract; therefore, they will not be required at the task order level. With the exception to these documents

15 | P a g e submitted prior to award, additional deliverables and/or CDRL requirements to be delivered in support of the

Basic IDIQ contract are not anticipated. All work to be performed/performance will be at the task order level.

Table 2. Basic IDIQ Contract Deliverables

PWS

Paragraph Description

DID

CDRL

Data

Item

No.

Frequen cy

As of

Date

Date of

First

Submission

Date of

Subse quent

Submi ssion

4.10

Equipment

Inventory

Records

DI-ILSS-

81251 A002

Within 120 Days of contract award

Annua l

5.11.5 Quality Control

Plan

DI-QCIC-

81379 A003 Within 180 Days of contract award

4.2.2 Task Order Data / Reporting Requirements

4.2.2.1 Contract Data Requirements List (CDRLs) (DD Form 1423s)

Specific data requirements shall be cited in the individual task order PWS.

Table 3. Data Item Descriptions (DIDs)

CDRL Number Title Document ID

A001 Contractor's Progress, Status and Management

Report

DI-MGMT-80227

A002 Equipment Inventory Records DI-ILSS-81251

A003 Quality Control Plan DI-QCIC-81379

A004 Software Quality Assurance Report DI-QCIC-81795

A005 Air Force -Technical Manual Contract

Requirements (TMCR)

TM86-0IN

A006 Manuals, Technical - Time Compliance

Technical Orders

MIL-DTL-38804D1

A007 Product Drawing And Associated List DI-SESS-81000D

A008 Commercial Off-The Shelf Manuals DI-TMSS-80527C

A009 Techinical Report - Study Services DI-MISC- 80508B

16 | P a g e

A010 Security Test Plan DI-NDTI-81351

A011 Test Procedures DI-NDTI-80603A

A012 Software Development Plan DI-IPSC-81427

A013 Database Design Description DI-IPSC-81437A

A014 Software User Manual DI-IPSC-81443A

A015 Engineering Change Proposal DI-SESS-80639D

A016 Computer Software Product End Items DI-AVCS-80700

A017 Software Test Plan (STP) DI-IPSC-81438

4.2.3 Contract Data Requirements List (CDRLs) – Basic IDIQ Contract

Documentation shall be delivered in accordance with the PWS and CDRLs, unless otherwise specified by the

Government Program Manager and Contracting Officer through a contract modification or PCO letter.

4.2.4 Contract Data Requirements List (CDRLs) – Task Order

Shall be cited in the PWS applicable to individual task order.

4.2.5 Contract Data Requirements List (CDRLs) – Basic IDIQ Contract

Documentation shall be delivered in accordance with the PWS and CDRLs, unless otherwise specified by the

Government Program Manager and Contracting Officer through a contract modification or PCO letter.Hardware / Non-CDRL Deliverables. Hardware and non-CDRL deliverables shall be delivered in accordance with the individual task order PWS and CDRLs, (if applicable).

4.2.6 Inspection / Acceptance of Services & Deliverables – Basic IDIQ Contract

The Government has the inherent right to disapprove any data deliverables. Therefore, the Government

Program Manager will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the Government Program Manager, with coordination with the

Contracting Officer, will notify the Contractor in writing of the specific reasons why the deliverable was rejected. The Contractor shall have 10 calendar days, or unless designated otherwise through a CDRL, PCO letter or contract modificaiton, to correct the rejected deliverable and resubmit to the Government Program

Manager for re-inspection. The Government must approve final versions of data deliverables.

17 | P a g e

4.2.7 Inspection / Acceptance of Services & Deliverables – Task Order

Shall be cited in the PWS and CDRLs (DD Form 1423) applicable to individual task order.

4.3 Contractor Full-Time Equivalent Reporting (eCMRA)

Contractors have the inherent responsibility to track personnel performing on each individual task order;

therefore, the Government does not expect additional costs associated with this reporting requirement.

However, if the Contractor determines additional costs will be incurred on task orders as a result of this reporting they may include those costs in their price proposal volume in support of their proposal submitted in response to the task order RFOP.

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of EACH individual task order via a secure data collection site**. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for the engineering services task orders 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 CMRA help desk**.

*Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

**User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link.

However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

Non-CDRL data / reporting requirements in addition to eCMRA Full Time Equivalent Reporting shall be cited in the PWS applicable to the individual task order.

4.4 Option To Extend Services up to Six (6) Months IAW FAR 52.217-8

It is anticipated individual task orders may include an option to extend services up to six (6) months IAW FAR

52.217-8, Option To Extend Services. In the event this option is exercised, the Contractor shall provide the support delineated in the individual task order PWS for up to six (6) months. Per FAR 52.217-8, the

Government may require continued performance of any services up to six (6) months within the limits and at the rates specified in the Task Order. Period of performance for this additional support shall be IAW Section B, The Schedule, of the task order (i.e. established and identified under the individual Option To Extend Services

CLIN of the order).

http://www.ecmra.mil/

18 | P a g e

4.5 Period of Performance

The period of performance shall be IAW Section B, The Schedule, of the task order (i.e. established and identified under the individual CLINs of the task order).

4.6 Contract Holidays (if work to be performed at Government location)

The prices/costs in Section B, The Schedule, of the task order shall include holiday observations; accordingly, the Government will not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday. Holidays falling on a Saturday will be observed on the preceding Friday.

Holidays falling on a Sunday will be observed on the following Monday. The following days are contract holidays.

New Year’s Day 1 January

Martin Luther King’s Birthday Third Monday in January

President’s Day Third Monday in February

Memorial Day Last Monday in May

Independence Day 4 July

Labor Day First Monday in September

Columbus Day Second Monday in October

Veteran’s Day 11 November

Thanksgiving Day Fourth Thursday in November

Christmas Day 25 December

Unless otherwise required by the Government, the contractor shall not have access to Government facilities on the following federal holidays: New Year’s Day, Martin Luther King’s Birthday, President’s Day, Memorial

Day, Independence Day, Labor Day, Columbus Day, Veterans’ Day, Thanksgiving Day, and Christmas Day.

4.7 Days and Hours of Operation (if work to be performed at Government location)

4.7.1 Accomplishment of the results contained in this PWS requires work at Peterson AFB, Schriever AFB and at various contractor and Government facilities in the continental United States. Normal workdays are

Monday through Friday, Government workers typically work 80 hours per two weeks. Flextime workers start not earlier than 0600 and not later than 0900. Core hours of work are from 0900 to 1500 daily. All employees are expected to be available during core hours. Contractors are not authorized compensation for attendance at base functions unless directly related to project assignments as authorized by the project manager.

4.7.2 If the holiday falls on Sunday, it is observed on Monday. If the holiday falls on Saturday, it is observed on Friday.

4.7.3 In addition to these days designated as holidays, the Government observes the following days: Any day designated by federal statute, any day designated by executive order, any day designated by a President of the

United States proclamation.

19 | P a g e

4.8 Security

4.8.1 General Information / Standards of Conduct

The Contractor shall not divulge any information regarding files, data, processing activities/functions, user

ID's, passwords, or other knowledge they may have gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all government rules, policies, procedures, and standards of conduct.

4.8.2 Release/Removal of Documentation

The Contractor shall not release or remove system documentation, data, or reports generated by or through use of any government systems. All requests for information shall be forwarded to the Contracting Officer who will request approval from the Government Program Office.

4.8.3 Automated Information Systems (AIS) Security

Contractors requiring access to Government AIS shall have background investigations and security awareness training completed prior to the start of contract performance. Peterson AFB security office will be responsible to verify the appropriate background investigations are performed. When the period of performance is complete or contractor personnel leave work on this project, the contractor personnel shall terminate all their network user accounts and return all access cards and base identification within 5 working days, unless authorized to retain them.

4.8.4 Safeguarding Covered Defense Information and Cyber Incident Reporting

The following DFARS clauses are applicable to orders issued under this basic IDIQ contract. Contractor shall control information IAW these clauses, other sections of this PWS and terms and conditions of the task order.

252.204-7008 Compliance with Safeguarding Covered Defense Information Controls

252.204-7009 Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber

Incident Information

252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting

252.239-7009, Representation of Use of Cloud Computing

252.239-7010, Cloud Computing Services

4.8.5 Access to Confidential, Proprietary and/or Sensitive Information

Contractor personnel may be required to access Confidential, Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under the individual Task Orders. This information may belong to other contractors, other third parties, or the USAF. Contractor personnel shall provide a completed copy of the Nondisclosure Agreement (NDA) provided below to the Government Program Manager, Contracting Officer Representative (COR) and Contracting Officer prior to performing work that involves

20 | P a g e

Confidential, Proprietary and/or Sensitive Information held by the USAF relating to the tasks to be performed under the individual Task Orders.

It should be noted that Confidential, Proprietary and/or Sensitive Information shall not include information that the Contractor personnel or the Contractor can demonstrate:

(A) was known by the Contractor personnel or the Contractor without restriction as to further disclosure when received or was developed independently by the Contractor by individuals who had no direct or indirect access to such information,

(B) was obtained from a source other than the USAF, its employees, agents, or contractors through no breach of confidence,

(C) was in the public domain when received or thereafter enters the public domain through no breach of confidence by Contractor or Contractor personnel, or

(D) was used or disclosed with the prior written approval of the USAF.

Information made available to the contractor by the Government for the performance or administration of this effort shall be used only for those purposes and shall not be used in any other way without the written agreement of the CO. The contractor agrees to assume responsibility for protecting the confidentiality of

Government records, which are not public information. Each contractor or employee of the contractor to whom information may be made available or disclosed shall be notified in writing by the contractor that such information may be disclosed only for a purpose and to the extent authorized herein.

4.8.6 Security Clearance

A security clearance of SECRET will be required for all personnel performing in support of individual task orders that result from this Basic IDIQ contract.

Although the work itself might be classified or unclassified and performed both on-base (on-site) and off-base

(off-site) locations, a security clearance of SECRET will be required. The DD Form 254 attached to the basic

IDIQ contract(s) shall support individual task orders up to the minimum security requirement of SECRET;

however, some individual task orders may have security requirements that exceed those of the DD Form 254 included in the basic IDIQ contract. In those cases, task order specific DD Form 254 will be included in the

Request For Order Proposal (RFOP) and resultant task order. In such an event, only those contractors who meet the proper security requirements will be considered for award of that specific task order. The Government program office will be responsible for initiating and coordinating DD Form 254. Refer to the DD Form 254 attached to the basic IDIQ contract(s) and task order specific DD Form 254s for additional security instructions, guidance, policies and restrictions.

Contractor employees must be US Citizens and able to obtain a security clearance. Contractor employees hired in support of the individual task orders will require a security clearance at-or-above the level established in this

21 | P a g e basic IDIQ contract PWS or specified in the individual task order prior to starting performance in support of the task order.

The contractor shall comply with all security policies and regulatory requirements. Contractor employees must be US Citizens and able to obtain a security clearance. Contractor employees hired for working with classified information will require a security clearance at-or-above level of classified information to be worked, prior to starting performance on the individual task order.

4.8.7 Common Access Cards

In the event a Common Access Card (CAC) is required in support of work to be performed under this contract, the following instructions shall apply. It should be noted that this process may take a minimum of four (4) weeks to complete; so it is critical that Contractors consider these instructions before award of a task order (i.e.

when preparing a proposal in response to a RFOP) and prior to changing contractor personnel after award. If a

Contractor is required to get an email address (john.smith.ctr@us.af.mil) it may increase the approval time for network access by an additional 2-3 weeks.

4.9 Base or Area Badges and Access to Facilities

The Government Program Manager will assist contractor personnel in processing the necessary DoD forms to obtain base or area badges for access to government facilities. Access to government facilities is limited.

Therefore, the Contractor shall coordinate required access/usage times and dates through the Government

Program Manager in a timely manner. Control of the facilities shall remain with the Government.

4.10 Government Furnished Property (GFP)

The GFP list shall be cited in the IDIQ basic PWS. If any additional GFE is needed at the task order level, it shall be cited in the individual task order PWS, as applicable. The contractor shall provide an equipment inventory record within 180 days after contract award (CDRL A002). The individual task order CDRL will identify any subsequent equipment inventory record deliveries.

4.11 Program and Contract Management

4.11.1 Contractor Program Management Requirements

The Contractor shall be responsible for managing all aspects of the Basic IDIQ contract and awarded task orders, to include cost, schedule, performance and contract management. The Contractor shall act as the task integrator, ensuring all technical and program elements of a task order provide a fully integrated approach.

The contractor shall provide all qualified personnel in support of individual task orders. The contractor shall be responsible for the selection, recruitment, hiring, assignment of duties, and reassignment of duties, transfer, supervision, management, control, and termination of contractor employees in performance of this contract.

Contractor personnel are employees of the contractor and under its administrative control and supervision. The

22 | P a g e contractor and its employees shall not supervise, direct or control the activities of Government personnel or the employees of any other contractor.

4.11.2 Contractor Single Managers – Basic IDIQ Contract Level

The Contractor shall establish a single manager point of contact (POC) for program management, and one POC for contracting, having authority and responsibility for the overall…