08._Attachment_4_Security_Classification_Specification_DD254.pdf

Please wait...

If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.

You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.

For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Space and Missile Systems Center (SMC) Remote 1

Sensing Systems Directorate 2

Tools, Applications, and Processing (TAP) Laboratory and 3

Overhead Persistent Infrared (OPIR) Battlespace 4

Awareness Center (OBAC) Support Services 5

Performance Work Statement (PWS) 11

28 November 201815

TABLE OF CONTENTS 16

1.0 Overview and Background 5 17

1.1 Executive Overview 5 18

1.2 Background 5 19

1.3 Notional TAP Lab & OBAC Facility Design Overviews 8 20

1.4 TAP Lab & SEGA Infrastructure Network Overviews 9 21

1.5 Contractor Work Locations 10 22

2.0 Applicable Documents 11 23

3.0 Scope and General Definitions 12 24

3.1 Scope 12 25

3.2 General Definitions 13 26

4.0 Task Descriptions 14 27

4.1 Program Management 14 28

4.1.1 Program Manager 14 29

4.1.2 Financial Management 15 30

4.1.3 Subcontract Management 15 31

4.1.4 Schedule Management 15 32

4.1.5 Program Reviews 15 33

4.1.6 Facility Lease 16 34

4.2 Engineering 16 35

4.2.1 Chief Engineer 16 36

4.2.2 Communications and Network Engineering 17 37

4.2.3 Configuration Management 17 38

4.2.4 Training 18 39

4.2.5 Capability Identification and Analysis 18 40

4.2.6 Architecture and Design 18 41

4.2.7 Hardware Engineering 19 42

4.2.8 Software Engineering 19 43

4.2.9 Integration 20 44

4.2.10 Developmental Unit and Functional Test 20 45

4.2.11 Acceptance Testing 20 46

4.2.12 Operational Testing Support 21 47

4.2.13 Transition 21 48

4.2.14 Quality Assurance 21 49

4.2.15 TAP Lab Data Management 21 50

4.2.16 TAP Lab Website Management 22 51

4.3 Operations 22 52

4.3.1 Operations Support Subject Matter Expertise 22 53

4.3.2 System Administration 22 54

4.4 Hardware, Software, and Facility Support 23 55

4.4.1 Hardware Support 23 56

4.4.2 Software Support 24 57

4.4.3 Facility Support 24 58

4.4.4 Custodial Services 24 59

4.4.5 Logistics and Sparing 24 60

4.5 Security 25 61

4.5.1 Program Security 25 62

4.5.2 Physical Security 26 63

4.5.3 Computer Security (COMPUSEC) 26 64

4.5.4 Cyber Security – Risk Management Framework (RMF) 26 65

4.6 SOFA Specific Tasks 29 66

4.6.1 SOFA Software Support 29 67

4.6.2 SOFA Testing 29 68

4.7 Third Party Software Support 29 69

4.7.1 Third Party Software Support 29 70

4.7.2 Third Party Software Testing 30 71

4.8 Other Direct Costs 30 72

4.8.1 Procurement 30 73

4.8.2 Facility Lease 30 74

4.9 Additional Contract Requirements 30 75

4.9.1 Associate Contractor Agreement (ACA) 30 76

4.9.2 Interfacing with Aerospace Corporation Contact Support 31 77

4.9.3 Enterprise Contractor Manpower Reporting Application (ECMRA) 34 78

5.0 CDRL List 35 79

6.0 Acronym List 36 80

Table of Figures 82

Figure 1-1: Notional TAP Lab & SEGA Security Enclaves83

......................................................................................................................................................... 7 85

Figure 1-2: TAP Lab and SEGA IT infrastructure environments .................................................. 8 86 Figure 1-3: Notional TAP Lab Facility Design Overview ............................................................. 8 87 Figure 1-4: Notional OBAC Facility Design Overview ............................................................... 9 88 Figure 1-5: TAP Lab Infrastructure Conceptual Design .............................................................. 10 89 Figure 1-6: OBAC Facility and SEGA Infrastructure OV-1 & SV-1 .......................................... 10 90

1.0 Overview and Background 92

1.1 Executive Overview 93

This document is a Performance Work Statement (PWS) for a performance-based Non-A&AS 94 support services contract. The purpose of this PWS is to describe the performance objectives, 95 tasks and functions for Information Technology (IT), Facility Operations and Management, and 96 OPIR Domain Knowledge services for the Space and Missile Systems Center (SMC), Remote 97 Sensing Systems Directorate (RS), Remote Sensing Data Exploitation Division (RSX), Los 98 Angeles Air Force Base (LAAFB) CA. SMC/RSX is directed with standing up a government 99 controlled data exploitation Research, Development, Test and Evaluation (RDT&E) capability 100 called the Tools Applications and Processing (TAP) Lab, Boulder Colorado. Currently, Air 101 Force Space Command (AFSPC) has an established Overhead Persistent Infrared (OPIR) 102 Battlespace Awareness Center (OBAC) co-located with the Space Based Infrared System 103 (SBIRS) Mission Control Station located at Buckley AFB Colorado. All functions and activities 104 will be task driven, and all work performed must be in accordance with all applicable regulations 105 and guidelines IAW Section 2.0 Applicable Documents. 106

The purpose of the TAP Lab is to provide an unrestricted RDT&E innovation environment for 107 enhancing and/or developing new operational capabilities. This environment will be accessible to 108 other Department of Defense (DoD), Civil and Commercial Users to find new innovative uses of 109 remote sensing data. Capabilities enhanced or created within the TAP Lab will be tested, 110 validated and verified on the TAP Lab’s open systems architecture called Sensor Open 111 Framework Architecture (SOFA) and the follow-on framework, Future Operationally 112 Responsive Ground Enterprise (FORGE). Once applications are verified from TAP Lab for 113 operational utility, capabilities may be promoted and integrated into the Sensor Exploitation 114 Ground Architecture (SEGA), which is the operational system at the OBAC. SEGA is the IT 115 architecture that supports the mission executed within the OBAC. 116

The TAP Lab/OBAC Support Services Contractor, simply referred to as “Contractor” throughout 117 this PWS shall exercise management and operational control over, and retain full responsibility 118 for, performance requirements set forth in this PWS. The contractor is encouraged to introduce 119 new technologies and processes in partnership with the government in order to deliver the best 120 value products or services. 121

1.2 Background 122

The TAP Lab and OBAC support the AFSPC mission to provide global, persistent, infrared 123 surveillance and environmental monitoring capabilities to the warfighters and the nation for 124 Missile Warning (MW), Missile Defense (MD), Technical Intelligence (TI), Battlespace 125 Awareness (BA), and Weather missions. Although the TAP Lab and OBAC are operated by the 126 United States Air Force (USAF), the intent is not to limit the scope to only USAF requirements, 127 but also to develop technologies for other services, agencies, and non-military users, such as 128 civil, environmental, and other non-traditional OPIR and environmental (weather) users. 129

SMC/RS is charged with developing overhead persistent infrared and defense weather systems to 130 meet the needs of DoD operational elements. The Commander, Air Force Space Command 131 (AFSPC/CC), has given SMC/RS direction to pursue activities that will enable the maximization 132 of OPIR data exploitation and dissemination. To accomplish this, the TAP Lab was created in 133 Boulder, Colorado to promote competition and collaboration between algorithm developers, and 134 allow plug-and-play of different mission data processing applications. The TAP Lab and SEGA 135 framework feature an open systems architecture, called SOFA. SOFA was developed by 136 Lockheed Martin and is used in the TAP Lab and OBAC. In the TAP Lab it will be used to 137 develop plug-and-play mission data processing applications. The Government retains full rights 138 to the framework code and documentation and will continue to have full rights while the 139 contractor manages this effort. SOFA is also used in SEGA, which enables smooth transition of 140 new capabilities into the operations baseline. Although SEGA is the path for transition to 141 operations for the Battlespace Awareness mission, other products developed in the TAP Lab may 142 transition to other operational users in the appropriate location for their use. The TAP Lab is a 143 stand-alone capability separate from the OBAC and will serve as the research, development, and 144 test facility for multiple operational users. 145

The TAP Lab and OBAC are government owned and operated facilities. The configuration and 146 overall management of the two facilities are governed by the TAP Lab and OBAC government 147 boards. In facilitating the TAP Lab and OBAC missions to provide RDT&E applications and 148 related capability development and product delivery from the TAP Lab to SEGA and other 149 customers, the Contractor will perform operations and maintenance functions to ensure the TAP 150 Lab and SEGA’s integrated technical baselines remain consistently configured to ensure 151 capabilities operate nearly identically upon integration to SEGA. The Contractor will support 152 configuration management and control functions that are tightly coupled with other supporting 153 functions such as Cybersecurity-Risk Management Framework continuous monitoring, 154 vulnerability and patch implementation. The Contractor will perform directed assessments and 155 provide associated analysis, alternatives and recommendations for Government decisions based 156 on the Research and Development activities, product development, and commercial technology 157 advances to support OPIR and Defense Environmental (Weather) Systems. The TAP Lab has a 158 Secret RDT&E accredited security enclave. In the future the government will add an 159 Unclassified, and TS-SCI enclave (see Figure 1-1). SEGA currently has a Secret accredited 160 enclave. In the future, the government will add a TS-SCI enclave at the OBAC. 161

Figure 1-1: Notional TAP Lab & SEGA Security Enclaves163

The TAP Lab has both development and test environments while SEGA has an initial 165 deployment environment and a final deployment environment (see Figure 1-2). The TAP Lab 166 test environment and SEGA initial deploy environment are intended to be identical in physical 167 and logical configurations, except when directed by the government. 168

Figure 1-2: TAP Lab and SEGA IT infrastructure environments 169

1.3 Notional TAP Lab & OBAC Facility Design Overviews 171

The government has contracted with a 3rd party vendor to create the conceptual design of the 172 TAP Lab and OBAC facilities. The early design concepts are shown in Figure 1-3 and Figure 173 1-4. When the final buildout is complete in the TAP Lab, the total usable area will be 174 approximately 25,000 square feet, of which 3100 square feet will be dedicated for computer 175 room. At the OBAC, the final area will be 5300 square feet for mission operations, and 800 176 square feet for computer room. 177

Figure 1-3: Notional TAP Lab Facility Design Overview 178

Figure 1-4: Notional OBAC Facility Design Overview 181

1.4 TAP Lab & SEGA Infrastructure Network Overviews 183

The TAP Lab and SEGA infrastructure network as currently designed is shown conceptually in 184 Figure 1-5 and Figure 1-6. The FORGE and Wide Field of View environments are shown as 185 notional. In addition to a data archive, the common services environment contains security 186 logging services, user access control, and other information security services. Refer to TAP Lab 187 and SEGA detailed design documents (see applicable documents) for details for TAP Lab and 188 SEGA design. 189

Figure 1-5: TAP Lab Infrastructure Conceptual Design 191

Figure 1-6: OBAC Facility and SEGA Infrastructure OV-1 & SV-1 193

1.5 Contractor Work Locations 195

The TAP Lab is located in leased space in Boulder, Colorado. An interim SECRET TAP Lab 196 enclave was established in April 2016 and an interim Unclassified TAP Lab enclave established 197 in August 2017. The Contractor selected for this effort will transition these interim capabilities 198 (hardware, software, tools, data, and other equipment) into a final TAP Lab design consisting of 199 Unclassified, Secret and SCI enclaves. 200

The OBAC is the operational facility for the Battlespace Awareness (BA) mission and is located 201 within the SBIRS Mission Control Station (MCS) at Buckley AFB, Colorado. The BA mission 202 entered a period of “early operations” in early 2016. The OBAC is temporarily housed in a room 203 initially designed for a different mission. The Contractor will transition the current OBAC 204 capabilities, including the SEGA system into its final design configuration. This will include 205 relocating workstations within the operations area, relocating servers within the computer room, 206 and moving to a different room in the MCS. 207

Physical addresses of the facilities are: 208

TAP Lab: 6304 Spine Rd, Boulder CO 80302 209 OBAC: 18300 E. Crested Butte Ave, Buckley AFB CO 80011 210

2.0 Applicable Documents 211

In executing the tasks in this PWS, the Contractor shall be familiar with all applicable documents 212 related to the task areas. 213

SBIRS Security Classification Guide (SCG), xxx xxxx 214 OPIR Battlespace Awareness Center (OBAC) Configuration Management Plan, Rev A, 215

25 Sep 2017 216 DoDI 8510.01: Risk Management Framework (RMF) for DoD Information Technology 217

(IT), May 2016) 218 DoD 5220.22-R, National Industrial Security Program (NISPOM) Regulation, April 2014 219 DoD 5220.22-M: National Industrial Security Program Manual, February 2006 220 DoD 5220.22-M-Sup-1: National Industrial Security Program Manual, Supplement, 221

February 1995 222 DoD 8570.01M: Information Assurance Workforce Improvement Program 223 DoDI 8581.01: Information Assurance (IA) Policy for Space Systems Used by the 224

Department of Defense, 8 June 2010 225 DoDI 4630.05: Interoperability and Supportability of Information Technology and 226

National Security Systems, 5 May 2004 227 AFMAN 33-214, Emission Security Countermeasures Reviews, Volume 2, 21 Sep 2001 228 AFMAN 17-1301, Computer Security (COMPUSEC), 10 Feb 2017 229 ICD 705, Sensitive Compartmented Information Facilities 230 AFI 10-601 Operational Capability Requirements Development, 6 November 2013 231 AFI 31-101, Physical Security Program Management 232 AFI 31-601, Industrial Security Program Management 233 AFI 32-2001, Fire Emergency Services Program 234 AFI 32-7086, Hazardous Waste Materials Management Program 235 AFI 33-230, Information Protection Assessment and Assistance Program 236 AFI 91-202, US Air Force Mishap Prevention Program 237

AFI 91-203, Air Force Consolidated Occupational Safety Instruction 238 SBIRS Enterprise Systems Engineering Plan (ESEP), May 2017, July 2010 239 SMC-S-001: Systems Engineering, 13 Jun 2008 240 SMC-S-002: Configuration Management, 13 June 2008 241 SMC-S-003: Quality Assurance for Space and Launch Vehicles, 13 Jun 2008 242 SMC-S-012: Software Development, 16 Jan 2015 243 SMC-S-019: Program and Subcontractor Management, 11 August 2008 244 SMC-S-021: Technical Reviews and Audits, 15 Sep 2009 245 SMCI 63‐103: Software Acquisition Process Improvement Instruction, 30 Dec 2015 246 AFI 16‐201: Air Force Foreign Disclosure and Technology Transfer Program, June 2015 247 AFMAN 14-304: The Security, Use, and Dissemination of Sensitive Compartmented 248

Information (SCI), December 2016 249 AFMAN 63-119 Certification Of System Readiness For Dedicated Operational Testing 250 DoDI 4630.8: Procedures for Interoperability and Supportability of Information 251

Technology (IT) and National Security Systems (NSS), 30 June 2004 252 DoDD 5205.02E, DoD Operations Security Program 253 HEMI toolkit v1.3.5 254 HEMI User Guide v3.7.2 255 HEMI ICD VCDU File v1.0 256 HEMI ICD Rep Return v2.0 257 HEMI ICD Mission Products v1.1 258 HEMI ICD ILOSRT v1.0 259 HEMI Developer Guide V1.3.5 260 HEMI Admin Guide v3.7.2 261 TAP Lab Detailed Design, Rev D, 20 Nov 2018 262 OBAC System Design, Version 6, 20 Nov 2018 263

3.0 Scope and General Definitions 264

3.1 Scope 265

This solicitation is to acquire information technology support services for the Tools, 266 Applications and Processing (TAP) Lab, OPIR Battlespace Awareness Center (OBAC), and their 267 common underlying open systems SOFA. 268

The Government will neither supervise contractor employees nor control the method by which 269 the contractor performs the required tasks. Under no circumstances will the Government assign 270 tasks to, or prepare work schedules for, individual contractor employees. The contractor shall 271 manage its employees and guard against any actions that are of the nature of personal services, or 272 give the perception of personal services. If the contractor believes that any actions constitute, or 273 are perceived to constitute personal services, the contractor shall notify the Procuring 274 Contracting Officer (PCO) within 2 business days. 275

There are three components to the requirements in this PWS: 1) Enhancement and Sustainment 276 of SOFA; 2) Integration of 3rd party capabilities into quarterly SEGA deliveries and 277 enhancement, operations and maintenance of the TAP Lab and SEGA infrastructures; and 3) 278 Support for third party developed capabilities and applications. The TAP Lab in Boulder 279 Colorado and the OBAC on Buckley Air Force Base, Colorado are located approximately 50 280 miles apart. Satisfaction of this contract will require the vendor to perform several tasks and 281 functions to include; Information Technology (IT) Framework Support Services; Sensor Open 282 Framework Architecture Support; Facility Operations and Maintenance; Program Direction and 283 Management; and integration of third party capabilities into SEGA. 284

The supporting functions shall include, but are not limited to, all management support services 285 including IT network and facility operations and maintenance, management/technical direction 286 functions, logistics support, hardware and software procurement and management, data 287 management, configuration management of IT network technical baselines for both the TAP Lab 288 and OBAC. 289

3.2 General Definitions 290

(a) Information Technology Management – the activities related to managing 291 support of IT to provide information for policy development, strategic planning, 292 enterprise architecture, capital planning and investment control, resource 293 management, procurement actions, and special projects. IT management activities 294 include, but are not limited to, providing, developing, implementing, and 295 monitoring the operational availability and maintainability of the TAP Lab and 296 SEGA according to industry best practices; updating and submitting infrastructure 297 upgrade recommendations; performing resources management (monitoring 298 processing and memory utilization); producing products in response to quick-299 turnaround needs to include, but limited to, briefings, presentations, fact sheets, as 300 well as issue and reference papers. Proper IT management requires internal and 301 external coordination to include, but not limited to, working with customers, other 302 agencies, internal program management office staff, other external agencies, and 303 when requested, provide information to assist in drafting responses to inquiries 304 from Congress and other agencies. 305

(b) Systems Engineering – the activities pertaining to software development support 306 for all existing, planned, and future TAP Lab and SEGA IT systems and 307 capabilities. Typical duties include capturing both system and user requirements; 308 coordinating with appropriate government personnel regarding enterprise 309 architecture; identifying functional, security, and performance standards; 310 developing logical and physical database models; performing coding, testing, 311 quality assurance, design, and program documentation; implementation; and 312 maintaining interoperability between future and existing hardware and software 313 applications. Software applications include, but are not limited to, web applications, 314 Commercial-Off-The-Shelf (COTS) integration, Government-Off-The-Shelf 315 (GOTS) integration, and custom applications development. 316

(c) Information Technology System Administration – the activities related to 317 planning and implementing telecommunications and information technology 318 infrastructures; network administration which includes network access and security; 319 server management; emergency preparedness planning; IT disaster recovery 320 planning and execution; IT inventory control; audio, video, and web conferencing; 321 application system administration; user support; workstation management; IT 322 training and education; wireless services; and voice and data services as well as the 323 maintenance and service related activities to ensure operational availability of the 324 IT telecommunications and networks. 325

(d) Cybersecurity – the activities related to the secure transmission and storage of 326 electronic information, drafting cyber security policy and procedures, providing 327 user awareness training, risk management, and internal and/or external auditing. 328 Further cyber security activities pertain to selecting and supporting the use of 329 electronic security hardware and software tools and mechanisms including, but not 330 limited to, encryption devices, access control, user identification and authentication, 331 and malicious content detection 332

(e) Communication and Network Engineering is the planning, oversight, and 333 evaluation of network upgrades; support of integrated product installation schedules 334 and critical path analysis; evaluation of system migration; support to infrastructure 335 requirements, security analysis and implementation for personnel and computer 336 security issues. 337

(f) OBAC Subject Matter Expert (SME) personnel will assist OBAC operators with 338 Battlespace Awareness tasks. OBAC SMEs will require demonstrated expertise in 339 both the OPIR domain and Battlespace Awareness missions. SMEs create training 340 materials, administer on the job training sessions with OBAC operators, and act as 341 continuity for the government transitory operations staff to coincide with quarterly 342 deliveries of capability to the OBAC. The SMEs are heavily involved with the 343 TAP Lab capability development and testing so that they are aware and able to train 344 the operations staff upon delivery of new capabilities to OBAC. 345

(g) 3rd Party Delivered Capabilities are elements of software, hardware, and other 346 like capabilities that are delivered to the government by vendors that are not part of 347 the TAP Lab/OBAC IT Support Services team. 348

4.0 Task Descriptions 349

4.1 Program Management 350

4.1.1 Program Manager 351

4.1.1.1 The Contractor shall provide a program manager, as one of the key 352 personnel on the contract, to oversee all contract efforts in support of the tasks in this PWS. The 353 program manager shall serve as lead for execution of the contract, updating stakeholders on the 354 contract progress. The program manager shall interchange with Government leadership on daily 355 activities of contractor work efforts. The program manager shall be the single source of 356 programmatic knowledge and ownership of assigned work across the contract. At a minimum, 357 the program manager shall have a Master’s degree in Management, 10 years of industry-related 358 experience, possess a current TS Clearance with SCI Eligibility, and 5 years of experience with 359 Agile software program management. 360

4.1.1.2 The Contractor shall create and annually update a Program Management 361 Plan (CDRL A001). 362

4.1.1.3 The Contractor shall interact with OBAC operational management and 363 stakeholders and SMC/RSX program management to establish a strong understanding of TAP 364 Lab and SEGA product, operational capabilities, and development and testing objectives. 365

4.1.1.4 The Contractor shall provide appropriately cleared personnel for all 366 positions described in the PWS according to the Contractor Proposed Staffing Plan. 367

4.1.1.5 The Contractor shall travel as necessary to meet the objectives of the 368 contract. As requested by the Government, the Contractor shall travel to meetings for the purpose 369 of information gathering, information sharing, coordination and planning. The Contractor shall 370 travel using commercial air, Government air, and other conventional modes. Travel arrangements 371 will be based on individual tasks, and the cost of travel will be directly reimbursed from task 372 funding. All travel Outside Continental United States (OCONUS) and Continental United States 373 (CONUS) requires prior coordination by the COR. Additionally, all OCONUS travel must be 374 approved in advance by the PCO or COR designated by the PCO. All travel requirements 375 (including plans, agenda, itinerary, dates) must be pre-approved by the COR or PCO; and is on a 376 strictly cost reimbursable basis. Costs for travel must be billed IAW the regulatory 377 implementation of Public Law 99-234, Federal Civilian Employee and Contractor Travel Expense 378 Act of 1985 and FAR 31.205-46 Travel Costs and Joint Travel Regulations. 379

4.1.2 Financial Management 380

4.1.2.1 The Contractor shall submit monthly contract funds status reports (CFSRs) 381

(CDRL A002). 382

4.1.3 Subcontract Management 383

4.1.3.1 The Contractor shall manage the efforts of all subcontractors utilized in 384 fulfillment of tasks of this contract. 385

4.1.4 Schedule Management 386

4.1.4.1 The Contractor shall manage and coordinate agile development cadence 387 amongst development teams (including 3rd party application vendors), manage and maintain 388 delivery schedules for concurrent lab activities and provide regular updates to the government lab 389 manager based on government priorities. 390

4.1.4.2 The Contractor shall create a quarterly delivery plan that describes the 391 roadmap of capabilities to be deployed to SEGA. This plan will include the 3rd Party applications, 392 algorithms, and other capabilities (to include framework updates) that must be integrated and 393 tested prior to deployment to the operational facility. This plan will be presented during the 394 quarterly program management reviews described in 4.1.5.1. 395

4.1.5 Program Reviews 396

4.1.5.1 The Contractor shall conduct quarterly program management reviews 397

(PMRs). PMR topics shall include, but are not limited to, overall program status reporting and 398 review; program issue identification and discussion, Action Item (AI) resolution, scheduling, 399 funding, and other topics (as required). Contractor shall submit PMR artifacts NLT 72 hours prior 400 to the review (CDRL A003). 401

4.1.5.2 The Contractor shall document development status, issues, concerns, 402 monthly funds status, etc. in the Monthly Program Status Report (MSR) (CDRL A013). 403

4.1.5.3 The Contractor shall provide meeting agenda and minutes for all meetings, 404 including but not limited to the meetings described in the PWS. 405

4.1.5.4 The Contractor shall support Technical Interchange Meetings (TIMs) and 406 any other associated working groups/meetings in support of the TAP Lab and SEGA. Slides shall 407 be provided to the government 5 business days prior for review. 408

4.1.6 Facility Lease 409

4.1.6.1 The Contractor shall bid Other Direct Costs to support paying the facility 410 lease to the building lease holder for the TAP Lab. The lease cost for FY19 is $1.25M and should 411 be assumed to increase at a typical inflation rate. The current building lease is good through 31 412 October 2021; however the government expects to renew the lease through the entire contract 413 period of performance. The Contractor shall continue to support the facility lease through the 414 period of performance. 415

4.2 Engineering 416

4.2.1 Chief Engineer 417

4.2.1.1 The Contractor shall provide a chief engineer, as one of the key personnel 418 on the contract, to oversee all system engineering efforts in support of the tasks in this PWS. 419 Duties include, but are not limited to, leading an IT Working Group, conducting engineering trade 420 studies, recommending engineering courses of action based on the studies, recommending 421 technology refresh actions to keep TAP Lab and SEGA at the forefront of technological 422 advancements, and conducting studies to control the total cost of ownership of the TAP Lab and 423 SEGA environments. 424

4.2.1.2 The chief engineer shall have a master’s degree in Engineering, 10 years of 425 industry-related experience, possess a current TS Clearance with SCI Eligibility, have 5 years of 426 Agile Software Development expertise, and have experience with integration of capabilities into 427 Operational DoD locations. 428

4.2.1.3 The chief engineer shall be the primary contractor voice for all system 429 engineering decisions to include configuration management and control, network status and 430 control, and other system engineering activities as appropriate at the Configuration Approval 431 Boards at TAP Lab and OBAC. 432

4.2.1.4 The Contractor shall create and maintain a System Engineering Master 433 Plan. (CDRL A007) 434

4.2.1.5 The Contractor shall develop, update and ensure accessibility of drawings 435 depicting processing and networking components. 436

4.2.1.6 The Contractor shall create and maintain a Continuous 437 Integration/Continuous Deployment (CI/CD) pipeline for capabilities to be deployed to the SEGA 438 Initial Deploy environment. 439

4.2.1.7 The Contractor shall recommend and support implementation and testing 440 of commercial cloud computing solutions at Government direction. 441

4.2.2 Communications and Network Engineering 442

4.2.2.1 The Contractor shall provide network engineering services. This includes, 443 technical support to all network (WAN/LAN) connectivity at the TAP Lab/OBAC, throughput 444 analysis, firewall recommendations and port configurations as necessary to achieve the desired 445 connectivity to/from TAP Lab/OBAC servers. The TAP Lab and SEGA have network interfaces 446 to RTS, SBIRS Operational Sub-Element (SEGA) and Analytical Sub-Element (TAP Lab) and 447 SIPRNET. Future interfaces will include JWICS in the SCI enclave. The Contractor shall 448 provide support for the TAP Lab and SEGA up to the communications demarcation. Additional 449 communication interfaces will be directed by the government as needed. 450

4.2.2.2 The Contractor shall create and maintain documentation to support the 451 testing, installation, and operation of networks. 452

4.2.3 Configuration Management 453

4.2.3.1 The Contractor shall maintain processes and procedures to enable 454 government ownership and control of the technical baseline documentation in accordance with the 455 SMC/RS Enterprise System Engineering Plan. 456

4.2.3.2 The Contractor shall facilitate the change management boards that will be 457 chaired by the appropriate government office as defined in the TAP Lab and OBAC 458 Configuration Management Plans. 459

4.2.3.3 The Contractor shall submit and seek approval for all Configuration 460 Change Proposals (CCP) with the appropriate government approval boards. 461

4.2.3.4 The Contractor shall develop and maintain a government approved TAP 462 Lab Configuration Management Plan. The contractor shall update the plan on at least an annual 463 basis. (CDRL A005) 464

4.2.3.5 The Contractor shall maintain the government approved OBAC 465 Configuration Management Plan. The contractor shall update the plan on at least an annual basis. 466

(CDRL A006) 467

4.2.3.6 The Contractor shall maintain a software repository of all code developed, 468 used, and/or delivered to the government including the SOFA source code. The TAP Lab has 469 leveraged the Defense Intelligence Information Enterprise (DI2E) for software development tools 470 (e.g. Bitbucket, JIRA, Confluence) to maintain version control and address deficiency reports 471 (DRs). The contractor shall utilize these tools or a similar capability to manage the configuration 472 of the TAP Lab and SEGA configured baselines. 473

4.2.3.7 The Contractor shall continuously monitor, review and audit all proposed 474 IT infrastructure technical baseline changes to ensure configuration management and control 475 processes and procedures are met and architectural integrity is preserved. The contractor shall 476 assist the TAP Lab and OBAC government personnel in the improvement of the Configuration 477 Management processes and procedures to meet industry standards, as appropriate. 478

4.2.3.8 The contractor shall maintain a library of relevant documents for users of 479 the TAP Lab. Active specifications, standards, handbooks and other published documents may be 480 required to define completely the characteristics of hardware and software components. The 481 Government will expect the contractor to acquire and deliver needed active documents including 482 operational and maintenance processes, procedures and training documents. Due to the nature of 483 rapid changes in the information processing industry, inactive, out-of-date, superseded, or 484 canceled documents will likely be required to define fully the characteristics of many electronic 485 information systems. The contractor shall acquire, deliver and maintain active and inactive 486 documents such as specifications, standards, handbooks, source control, and other published 487 documents. 488

4.2.4 Training 489

4.2.4.1 The Contractor shall provide SME support to ensure that SEGA 490 requirements are met and to provide training and documentation support on current and future 491 capabilities for the open framework architecture and 3rd party developed applications. Training 492 shall include online and instructor led classes on at least a quarterly basis to coincide with 493 quarterly capability releases. 494

4.2.5 Capability Identification and Analysis 495

4.2.5.1 The Contractor shall create and maintain a Capability Needs process that 496 incorporates user/stakeholder feedback, addresses technological advances, and cybersecurity 497 needs. (CDRL A004) 498

4.2.5.2 The Contractor shall, in accordance with the SMC/RS Enterprise Systems 499 Engineering Plan, convert the Government-approved Capability Needs into system requirements 500 where appropriate. 501

4.2.5.3 The Contractor shall consult with R&D vendors performing work within 502 the TAP Lab to gather their requirements with respect to TAP Lab resources needed to perform 503 research and development; support problem identification, capacity planning, network 504 optimization and tuning, and virtual machine configurations that meet certification and 505 accreditation requirements. 506

4.2.5.4 The Contractor shall update and maintain the TAP Lab developers 507 handbook that describes the capabilities, tools, and processes to be followed for the TAP Lab. 508

(CDRL A012) 509

4.2.5.5 The Contractor shall support SEGA capability performance metric 510 collection activities. This includes but is not limited to all current and future SEGA capabilities 511 tools, SEGA system framework, data interface, and product dissemination activities. The 512 contractor shall recommend infrastructure improvements where appropriate based on these 513 performance metrics. 514

4.2.6 Architecture and Design 515

4.2.6.1 The Contractor shall be responsible for researching, testing, and making 516 recommendations for new hardware and software technologies. 517

4.2.6.2 The Contractor shall provide recommendations for development toolset 518 upgrades on a biannual basis. Purchases will be made from available ODC on this contract, as 519 GFE, or via other contract at lab director’s direction. 520

4.2.7 Hardware Engineering 521

4.2.7.1 The Contractor shall establish and execute hardware engineering functions. 522

Hardware engineering shall research required equipment, prepare procurement requisitions, 523 install, integrate, test, troubleshoot, resolve issues, and maintain the hardware suite for both the 524 TAP Lab and OBAC. 525

4.2.7.2 The Contractor shall maintain the hardware to support a sandbox 526 environment that is logically isolated from the rest of the TAP Lab. 527

4.2.7.3 The Contractor shall support a TAP Lab development environment that is 528 more tightly controlled and used to conduct vendor development of new capabilities. 529

4.2.7.4 The Contractor shall support a TAP Lab test environment that mirrors the 530 SEGA initial deployment to the greatest extent practical. Any deviations of configuration 531 between the Test Environment and the Initial Deploy environment shall be approved by the 532 government. 533

4.2.7.5 The Contractor shall support a SEGA Initial Deploy environment as 534 depicted in the SEGA Design Documents. 535

4.2.7.6 The Contractor shall support a SEGA Final Deploy environment as 536 depicted in the SEGA Design Documents. 537

4.2.7.7 When final facility buildout for the OBAC is complete (estimated in 2020), 538 the Contractor shall move the equipment currently located in the interim OBAC facility into the 539 final facility. The amount of equipment to be moved is described in the SEGA design documents 540 (see applicable documents). 541

4.2.8 Software Engineering 542

4.2.8.1 The Contractor shall establish and execute software engineering functions. 543

Software engineers shall continuously assess the Commercial off the Shelf (COTS), Government 544 off the Shelf (GOTS), Free or Open Source Software (FOSS) and other software items to ensure 545 uninterrupted operation of the lab environment. Software engineering shall also install, integrate, 546 test, troubleshoot, resolve issues, and maintain the software suite. 547

4.2.8.2 The Contractor shall develop, in coordination with the Government, a 548 Continuous Integration/Continuous Deployment (CI/CD) capability to conduct automated 549 building, testing, and deployment of prototype and experimental software. This activity will be 550 initiated with Government’s draft CI/CD pipeline. 551

4.2.8.3 The Contractor shall manage the on-boarding of new software into the TAP 552 Lab. This approach should maximize the use of automated tools for code check in, configuration 553 management, build, code quality evaluation, regression testing, and deployment to lab and other 554 environments as directed by the Government. 555

4.2.8.4 The Contractor shall produce a reference implementation of the CI/CD 556 pipeline, with required cybersecurity protection, capable of rapidly integrating capabilities and 557 deploying them into target environments. This platform will be hosted and tested within the TAP 558 Lab and should utilize open standards and maximize the use of Free and Open-Source Software 559 (FOSS). The Contractor will maximize the use of existing Government investments and facilities 560 to integrate, test and operate the capabilities in order to minimize duplication of work. 561

4.2.8.5 The Contractor shall verify delivered software is properly marked for 562 security classification and free from malicious and otherwise undesirable elements using industry 563 standard software scanning tools. 564

4.2.9 Integration 565

4.2.9.1 The Contractor shall accept delivery from development activities as 566 directed by the government and integrate the application into the TAP Lab and SEGA on at least a 567 quarterly cadence. 568

4.2.9.2 The Contractor shall manage and execute the CI/CD delivery process for 569 evaluating third party developed capabilities. This continuous process will evaluate the adherence 570 to architecture and cybersecurity standards as specified by the Government. 571

4.2.9.3 The Contractor shall integrate new services from third party developers for 572 integration onto framework baseline as appropriate. 573

4.2.10 Developmental Unit and Functional Test 574

4.2.10.1 The Contractor shall support 3rd party vendors in their development and 575 unit test campaigns in the TAP Lab. 576

4.2.10.2 The Contractor shall provide data sets for 3rd parties to conduct 577 development and test of 3rd party capabilities in the TAP Lab. 578

4.2.10.3 The Contractor shall develop a unit test plan and conduct developmental 579 unit and functional test for all SOFA deliveries. (CDRL A015) 580

4.2.11 Acceptance Testing 581

4.2.11.1 The Contractor shall manage, in cooperation with capability developers, 582 the verification of products having completed lab development and slated for transition to 583 operations. This task includes building, managing and maintaining repositories of sample and test 584 data and implementing government verification plans. 585

4.2.11.2 The Contractor shall secure and/or create and maintain acceptance test data 586 sets (Gold Standard) for validation of capabilities in both the TAP Lab and SEGA. These data sets 587 are to be used only for government acceptance testing and shall be unique to the data sets 588 described in paragraph 4.2.10.2 and should not be shared with 3rd party vendors. 589

4.2.12 Operational Testing Support 590

4.2.12.1 The Contractor shall support government operational testing for all 591 capabilities deployed to the SEGA Final Deployment environment. This will include supporting 592 government efforts to comply with Operational Test Agency or other test agencies and 593 requirements to modify the Operational Baseline at SEGA (to include AF1067 process). 594

4.2.13 Transition 595

4.2.13.1 Working with the operations and sustainment community, the Contractor 596 shall develop and execute disciplined processes for transitioning successful applications and open 597 framework modifications into operations in accordance with the OBAC Configuration 598 Management plan. 599

4.2.13.2 The Contractor shall provide hardware and software integration support for 600 applications and tools that have been generated at the TAP Lab and other development sources 601 (e.g. NASIC, AFRL, NRL) that are selected by the government for deployment to SEGA. 602

4.2.13.3 The Contractor shall deploy applications and tools that have been 603 generated at the TAP Lab or other development sources (e.g. NASIC, AFRL, NRL) that are 604 selected by the government for deployment to SEGA according to the quarterly release schedule 605 described in paragraph 4.1.4.2. 606

4.2.13.4 The Contractor shall coordinate product support agreements, installation 607 and checkout procedures and all other necessary system integration documentation in support of 608 capability transition to/from TAP Lab, OBAC, or other customer facilities. 609

4.2.14 Quality Assurance 610

4.2.14.1 The Contractor shall establish a quality assurance element within its 611 organization that ensures compliance with applicable Federal mandates, contractual performance 612 standards, and industry standards and best practices. The Contractor shall update the Quality 613 Assurance Plan on an annual basis. (CDRL A013) 614

4.2.15 TAP Lab Data Management 615

4.2.15.1 The Contractor shall actively manage the TAP Lab data repositories to 616 ensure adequate data sets for development, test, and validation are available and appropriately 617 controlled and managed for the Research and Development (R&D) efforts awarded to Broad 618 Agency Announcement (BAA), Small Business Innovative Research (SBIR), or other 3rd party 619 vendors. Each TAP Lab security enclave is expected to have its own data repository. The 620 Contractor shall participate in 3rd party scheduling meetings, kick-off meetings, and initial design 621 reviews to identify researcher data requirements, need dates, and delivery methods. If data 622 needed to fulfill the researcher's data needs is not already available within the appropriate enclave 623 repository, the contractor shall retrieve the data from other government sources (e.g. NASIC). 624 This shall include submitting data requests or directly downloading data, transferring the data to 625 the appropriate TAP Lab enclave repository, updating the data repository lists, and/or transfer of 626 data to an approved vendor's facility for initial development and test support. 627

4.2.15.2 The Contractor shall coordinate with the government to ensure R&D 628 vendor is only provided access to the data necessary to accomplish their approved R&D awarded 629 tasks. Additionally, the contractor shall log and track all data transfers and shall establish a 630 destruction notification process to enable the government’s requirement to ensure all data is 631 appropriately destroyed upon conclusion of the 3rd party vendor's approved period of performance 632 end date. All data management, integrity and transfer processes shall adhere to the requirements 633 specified by the data owners and/or the appropriate security classification guidance. 634

4.2.15.3 The Contractor shall update and manage the data repository library and 635 catalog for each enclave and ensure that raw data is being archived 24 hours per day, 7 days per 636 week. 637

4.2.16 TAP Lab Website Management 638

4.2.16.1 The Contractor shall update and maintain the government established 639 public-facing web presence at www.boulderlab.org. 640

4.3 Operations 641

4.3.1 Operations Support Subject Matter Expertise 642

4.3.1.1 The Contractor shall provide Subject Matter Expertise (SME) that supports 643

24/7 OBAC near real-time operators. The Contractor shall designate one Lead SME as a key 644 person on the contract. This Lead SME shall be the primary focal point for OBAC leadership 645 feedback. The Lead SME shall create Standard Operating Procedures that ensure all SMEs 646 conduct their support in a coordinated fashion. (CDRL A010) 647

4.3.1.1.1 The Lead SME shall have 10+ years of experience in the SBIRS or 648 OPIR domains with 5+ years of experience in OPIR Data Exploitation or Battlespace Awareness 649 mission areas. 650

4.3.1.2 The Contractor shall coordinate and support mission tasking with OBAC 651 operations crew and shall provide technical leadership to a highly skilled team, developing 652 intricate strategies satisfying operational, development and testing requirements for SEGA. 653

4.3.1.3 The OBAC SMEs and other appropriate personnel shall participate in 654 feedback sessions between OBAC operators and TAP Lab development teams. 655

4.3.2 System Administration 656

4.3.2.1 The Contractor shall be responsible for end-to-end operation of networks 657 and IT assets. The Contractor shall designate one Lead System Administrator (SA) on the 658 contract as a key person on the contract. This Lead SA shall be the primary focal point for TAP 659 Lab and OBAC leadership feedback. The Lead SA shall create Standard Operating Procedures 660 that ensure all SAs provide support to the system in a coordinated fashion.(CDRL A011) 661

4.3.2.1.1 The Lead SA shall possess a Bachelor’s Degree in Computer 662 Science with 5+ years of system administration experience. The Lead SA shall have 3+ years of 663 experience with Agile Software development methodologies and should have an in-depth 664 knowledge of VMware, Red Hat Enterprise Linux, software defined networking, and software 665 defined storage and Public and Private Cloud infrastructure. 666

4.3.2.2 The Contractor shall coordinate and schedule downtime to limit user 667 impact as necessary to incorporate new capabilities into the TAP Lab and SEGA. 668

4.3.2.3 The Contractor shall develop, revise and maintain TAP Lab operations 669 processes and procedures to meet new requirements or advances in technology. 670

4.3.2.4 The Contractor shall develop, revise and maintain procedures and 671 processes for technical support and maintenance actions for SEGA to meet new requirements or 672 advances in technology. 673

4.3.2.5 The Contractor shall provide level 1 system maintenance and assistance 674 functions to researchers and other users of the TAP lab 5 days per week from 7AM to 5PM. The 675 contractor shall be available to correct any deficiencies within one hour of discovery. The 676 Contractor shall support off hours requests for support only after authorization by the government. 677 Such support will be coordinated at least one week in advance. 678

4.3.2.6 The Contractor shall provide level 1 system maintenance and support to 679 OBAC operations, 24 hours per day, 7 days per week, 365 days per year. 680

4.3.2.7 Contractor shall develop, implement, and test a backup and recovery 681 strategy for both TAP Lab and OBAC facilities. 682

4.3.2.8 The Contractor shall provide a secure environment for applications to 683 reside by creating Virtual Machines or bare metal partitions within computing center. The 684 contractor shall ensure that computing environments for vendors utilizing the TAP Lab are 685 available for use whenever the vendor is scheduled to work in the facility. 686

4.3.2.9 The Contractor shall support installation, maintenance, repair, and 687 upgrades of all hardware, firmware, software, and associated equipment that is installed as part of 688 the network. 689

4.3.2.10 The Contractor shall provide identity management of network access to 690 authorized personnel. 691

4.3.2.11 The Contractor shall adhere to the government provided Patch 692 Management Plan for both the TAP Lab and SEGA. 693

4.3.2.12 The Contractor shall maintain storage systems to enable both a static 694 (permanent) archive of relevant data and events as well as a 30-day rolling archive of raw data. 695

4.4 Hardware, Software, and Facility Support 696

4.4.1 Hardware Support 697

4.4.1.1 The Contractor shall support level 1 hardware maintenance in support of 698 the TAP Lab and SEGA enclaves. Level 1 support includes, but is not limited to, replacing failed 699 line replaceable units, conducting vendor recommended preventative maintenance, monitoring 700 hardware…