05._Attachment_1_PWS_TAP_and_OBAC_Support_Services_v9.1.pdf

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 (TLOSS) 5

Performance Work Statement (PWS) 11

7 January 201915

TABLE OF CONTENTS 16

1.0 Overview and Background 4 17

1.1 Executive Overview 4 18

1.2 Background 4 19

1.3 Notional TAP Lab & OBAC Facility Design Overviews 7 20

1.4 TAP Lab & SEGA Infrastructure Network Overviews 8 21

1.5 Contractor Work Locations 9 22

2.0 Applicable Documents 10 23

3.0 Scope and General Definitions 11 24

3.1 Scope 11 25

3.2 General Definitions 12 26

4.0 Task Descriptions 13 27

4.1 Program Management 13 28

4.1.1 Program Manager 13 29

4.1.2 Financial Management 14 30

4.1.3 Subcontract Management 14 31

4.1.4 Schedule Management 14 32

4.1.5 Program Reviews 14 33

4.1.6 Facility Lease 15 34

4.2 Engineering 15 35

4.2.1 Chief Engineer 15 36

4.2.2 Communications and Network Engineering 16 37

4.2.3 Configuration Management 16 38

4.2.4 Training 17 39

4.2.5 Capability Identification and Analysis 17 40

4.2.6 Architecture and Design 17 41

4.2.7 Hardware Engineering 18 42

4.2.8 Software Engineering 18 43

4.2.9 Integration 19 44

4.2.10 Developmental Unit and Functional Test 19 45

4.2.11 Acceptance Testing 19 46

4.2.12 Operational Testing Support 20 47

4.2.13 Transition 20 48

4.2.14 Quality Assurance 20 49

4.2.15 TAP Lab Data Management 20 50

4.2.16 TAP Lab Website Management 21 51

4.3 Operations 21 52

4.3.1 Operations Support Subject Matter Expertise 21 53

4.3.2 System Administration 21 54

4.4 Hardware, Software, and Facility Support 22 55

4.4.1 Hardware Support 22 56

4.4.2 Software Support 23 57

4.4.3 Facility Support 23 58

4.4.4 Custodial Services 23 59

4.4.5 Logistics and Sparing 23 60

4.5 Security 24 61

4.5.1 Program Security 24 62

4.5.2 Physical Security 25 63

4.5.3 Computer Security (COMPUSEC) 25 64

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

4.6 SOFA Specific Tasks 28 66

4.6.1 SOFA Software Support 28 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 29 71

4.8 Other Direct Costs 29 72

4.8.1 Procurement 29 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 Contract Support 31 77

4.9.3 Enterprise Contractor Manpower Reporting Application (ECMRA) 33 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 Enclaves .......................................................... 6 83

Figure 1-2: TAP Lab and SEGA IT infrastructure environments .................................................. 7 84

Figure 1-3: Notional TAP Lab Facility Design Overview ............................................................. 7 85

Figure 1-4: Notional OBAC Facility Design Overview ............................................................... 8 86

Figure 1-5: TAP Lab Infrastructure Conceptual Design ................................................................ 9 87

Figure 1-6: OBAC Facility and SEGA Infrastructure OV-1 & SV-1 ............................................ 9 88

1.0 Overview and Background 90

1.1 Executive Overview 91

This document is a Performance Work Statement (PWS) for a performance-based Non-A&AS 92 support services contract. The purpose of this PWS is to describe the performance objectives, 93 tasks and functions for Information Technology (IT), Facility Operations and Management, and 94

OPIR Domain Knowledge services for the Space and Missile Systems Center (SMC), Remote 95

Sensing Systems Directorate (RS), Remote Sensing Data Exploitation Division (RSX), Los 96

Angeles Air Force Base (LAAFB) CA. SMC/RSX is directed with standing up a government 97 controlled data exploitation Research, Development, Test and Evaluation (RDT&E) capability 98 called the Tools Applications and Processing (TAP) Lab, Boulder Colorado. Currently, Air 99

Force Space Command (AFSPC) has an established Overhead Persistent Infrared (OPIR) 100

Battlespace Awareness Center (OBAC) co-located with the Space Based Infrared System 101

(SBIRS) Mission Control Station located at Buckley AFB Colorado. All functions and activities 102 will be task driven, and all work performed must be in accordance with all applicable regulations 103 and guidelines IAW Section 2.0 Applicable Documents. 104

The purpose of the TAP Lab is to provide an unrestricted RDT&E innovation environment for 105 enhancing and/or developing new operational capabilities. This environment will be accessible to 106 other Department of Defense (DoD), Civil and Commercial Users to find new innovative uses of 107 remote sensing data. Capabilities enhanced or created within the TAP Lab will be tested, 108 validated and verified on the TAP Lab’s open systems architecture called Sensor Open 109

Framework Architecture (SOFA) and the follow-on framework, Future Operationally 110

Responsive Ground Enterprise (FORGE). Once applications are verified from TAP Lab for 111 operational utility, capabilities may be promoted and integrated into the Sensor Exploitation 112

Ground Architecture (SEGA), which is the operational system at the OBAC. SEGA is the IT 113 architecture that supports the mission executed within the OBAC. 114

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

1.2 Background 120

The TAP Lab and OBAC support the AFSPC mission to provide global, persistent, infrared 121 surveillance and environmental monitoring capabilities to the warfighters and the nation for 122

Missile Warning (MW), Missile Defense (MD), Technical Intelligence (TI), Battlespace 123

Awareness (BA), and Weather missions. Although the TAP Lab and OBAC are operated by the 124

United States Air Force (USAF), the intent is not to limit the scope to only USAF requirements, 125 but also to develop technologies for other services, agencies, and non-military users, such as 126 civil, environmental, and other non-traditional OPIR and environmental (weather) users. 127

SMC/RS is charged with developing overhead persistent infrared and defense weather systems to 128 meet the needs of DoD operational elements. The Commander, Air Force Space Command 129

(AFSPC/CC), has given SMC/RS direction to pursue activities that will enable the maximization 130 of OPIR data exploitation and dissemination. To accomplish this, the TAP Lab was created in 131

Boulder, Colorado to promote competition and collaboration between algorithm developers, and 132 allow plug-and-play of different mission data processing applications. The TAP Lab and SEGA 133 framework feature an open systems architecture, called SOFA. SOFA was developed by 134

Lockheed Martin and is used in the TAP Lab and OBAC. In the TAP Lab it will be used to 135 develop plug-and-play mission data processing applications. The Government retains full rights 136 to the framework code and documentation and will continue to have full rights while the 137 contractor manages this effort. SOFA is also used in SEGA, which enables smooth transition of 138 new capabilities into the operations baseline. Although SEGA is the path for transition to 139 operations for the Battlespace Awareness mission, other products developed in the TAP Lab may 140 transition to other operational users in the appropriate location for their use. The TAP Lab is a 141 stand-alone capability separate from the OBAC and will serve as the research, development, and 142 test facility for multiple operational users. 143

The TAP Lab and OBAC are government owned and operated facilities. The configuration and 144 overall management of the two facilities are governed by the TAP Lab and OBAC government 145 boards. In facilitating the TAP Lab and OBAC missions to provide RDT&E applications and 146 related capability development and product delivery from the TAP Lab to SEGA and other 147 customers, the Contractor will perform operations and maintenance functions to ensure the TAP 148

Lab and SEGA’s integrated technical baselines remain consistently configured to ensure 149 capabilities operate nearly identically upon integration to SEGA. The Contractor will support 150 configuration management and control functions that are tightly coupled with other supporting 151 functions such as Cybersecurity-Risk Management Framework continuous monitoring, 152 vulnerability and patch implementation. The Contractor will perform directed assessments and 153 provide associated analysis, alternatives and recommendations for Government decisions based 154 on the Research and Development activities, product development, and commercial technology 155 advances to support OPIR and Defense Environmental (Weather) Systems. The TAP Lab has a 156

Secret RDT&E accredited security enclave. In the future the government will add an 157

Unclassified, and TS-SCI enclave (see Figure 1-1). SEGA currently has a Secret accredited 158 enclave. In the future, the government will add a TS-SCI enclave at the OBAC. 159

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

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

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

1.3 Notional TAP Lab & OBAC Facility Design Overviews 169

The government has contracted with a 3rd party vendor to create the conceptual design of the 170

TAP Lab and OBAC facilities. The early design concepts are shown in Figure 1-3 and Figure 171

1-4. When the final buildout is complete in the TAP Lab, the total usable area will be 172 approximately 25,000 square feet, of which 3100 square feet will be dedicated for computer 173 room. At the OBAC, the final area will be 5300 square feet for mission operations, and 800 174 square feet for computer room. 175

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

Figure 1-4: Notional OBAC Facility Design Overview 179

1.4 TAP Lab & SEGA Infrastructure Network Overviews 181

The TAP Lab and SEGA infrastructure network as currently designed is shown conceptually in 182

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

SEGA design. 187

Figure 1-5: TAP Lab Infrastructure Conceptual Design 189

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

1.5 Contractor Work Locations 193

The TAP Lab is located in leased space in Boulder, Colorado. An interim SECRET TAP Lab 194 enclave was established in April 2016 and an interim Unclassified TAP Lab enclave established 195 in August 2017. The Contractor selected for this effort will transition these interim capabilities 196

(hardware, software, tools, data, and other equipment) into a final TAP Lab design consisting of 197

Unclassified, Secret and SCI enclaves. 198

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

Physical addresses of the facilities are: 206

TAP Lab: 6304 Spine Rd, Boulder CO 80302 207

OBAC: 18300 E. Crested Butte Ave, Buckley AFB CO 80011 208

2.0 Applicable Documents 209

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

SBIRS Security Classification Guide (SCG), 22 April 2016 212

OPIR Battlespace Awareness Center (OBAC) Configuration Management Plan, Rev A, 213

25 Sep 2017 214

DoDI 8510.01: Risk Management Framework (RMF) for DoD Information Technology 215

(IT), May 2016) 216

DoD 5220.22-R, National Industrial Security Program (NISPOM) Regulation, April 2014 217

DoD 5220.22-M: National Industrial Security Program Manual, February 2006 218

DoD 5220.22-M-Sup-1: National Industrial Security Program Manual, Supplement, 219

February 1995 220

DoD 8570.01M: Information Assurance Workforce Improvement Program 221

DoDI 8581.01: Information Assurance (IA) Policy for Space Systems Used by the 222

Department of Defense, 8 June 2010 223

DoDI 4630.05: Interoperability and Supportability of Information Technology and 224

National Security Systems, 5 May 2004 225

AFMAN 33-214, Emission Security Countermeasures Reviews, Volume 2, 21 Sep 2001 226

AFMAN 17-1301, Computer Security (COMPUSEC), 10 Feb 2017 227

ICD 705, Sensitive Compartmented Information Facilities 228

AFI 10-601 Operational Capability Requirements Development, 6 November 2013 229

AFI 31-101, Physical Security Program Management 230

AFI 31-601, Industrial Security Program Management 231

AFI 32-2001, Fire Emergency Services Program 232

AFI 32-7086, Hazardous Waste Materials Management Program 233

AFI 33-230, Information Protection Assessment and Assistance Program 234

AFI 91-202, US Air Force Mishap Prevention Program 235

AFI 91-203, Air Force Consolidated Occupational Safety Instruction 236

SBIRS Enterprise Systems Engineering Plan (ESEP), May 2017, July 2010 237

SMC-S-001: Systems Engineering, 13 Jun 2008 238

SMC-S-002: Configuration Management, 13 June 2008 239

SMC-S-003: Quality Assurance for Space and Launch Vehicles, 13 Jun 2008 240

SMC-S-012: Software Development, 16 Jan 2015 241

SMC-S-019: Program and Subcontractor Management, 11 August 2008 242

SMC-S-021: Technical Reviews and Audits, 15 Sep 2009 243

SMCI 63‐103: Software Acquisition Process Improvement Instruction, 30 Dec 2015 244

AFI 16‐201: Air Force Foreign Disclosure and Technology Transfer Program, June 2015 245

AFMAN 14-304: The Security, Use, and Dissemination of Sensitive Compartmented 246

Information (SCI), December 2016 247

AFMAN 63-119 Certification Of System Readiness For Dedicated Operational Testing 248

DoDI 4630.8: Procedures for Interoperability and Supportability of Information 249

Technology (IT) and National Security Systems (NSS), 30 June 2004 250

DoDD 5205.02E, DoD Operations Security Program 251

HEMI toolkit v1.3.5 252

HEMI User Guide v3.7.2 253

HEMI ICD VCDU File v1.0 254

HEMI ICD Rep Return v2.0 255

HEMI ICD Mission Products v1.1 256

HEMI ICD ILOSRT v1.0 257

HEMI Developer Guide V1.3.5 258

HEMI Admin Guide v3.7.2 259

TAP Lab Detailed Design, Rev D, 20 Nov 2018 260

OBAC System Design, Version 6, 20 Nov 2018 261

3.0 Scope and General Definitions 262

3.1 Scope 263

This solicitation is to acquire information technology support services for the Tools, 264

Applications and Processing (TAP) Lab, OPIR Battlespace Awareness Center (OBAC), and their 265 common underlying open systems SOFA. 266

The Government will neither supervise contractor employees nor control the method by which 267 the contractor performs the required tasks. Under no circumstances will the Government assign 268 tasks to, or prepare work schedules for, individual contractor employees. The contractor shall 269 manage its employees and guard against any actions that are of the nature of personal services, or 270 give the perception of personal services. If the contractor believes that any actions constitute, or 271 are perceived to constitute personal services, the contractor shall notify the Procuring 272

Contracting Officer (PCO) within 2 business days. 273

There are three components to the requirements in this PWS: 1) Enhancement and Sustainment 274 of SOFA; 2) Integration of 3rd party capabilities into quarterly SEGA deliveries and 275 enhancement, operations and maintenance of the TAP Lab and SEGA infrastructures; and 3) 276

Support for third party developed capabilities and applications. The TAP Lab in Boulder 277

Colorado and the OBAC on Buckley Air Force Base, Colorado are located approximately 50 278 miles apart. Satisfaction of this contract will require the vendor to perform several tasks and 279 functions to include; Information Technology (IT) Framework Support Services; Sensor Open 280

Framework Architecture Support; Facility Operations and Maintenance; Program Direction and 281

Management; and integration of third party capabilities into SEGA. 282

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

3.2 General Definitions 288

(a) Information Technology Management – the activities related to managing 289 support of IT to provide information for policy development, strategic planning, 290 enterprise architecture, capital planning and investment control, resource 291 management, procurement actions, and special projects. IT management activities 292 include, but are not limited to, providing, developing, implementing, and 293 monitoring the operational availability and maintainability of the TAP Lab and 294

SEGA according to industry best practices; updating and submitting infrastructure 295 upgrade recommendations; performing resources management (monitoring 296 processing and memory utilization); producing products in response to quick-297 turnaround needs to include, but limited to, briefings, presentations, fact sheets, as 298 well as issue and reference papers. Proper IT management requires internal and 299 external coordination to include, but not limited to, working with customers, other 300 agencies, internal program management office staff, other external agencies, and 301 when requested, provide information to assist in drafting responses to inquiries 302 from Congress and other agencies. 303

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

Commercial-Off-The-Shelf (COTS) integration, Government-Off-The-Shelf 313

(GOTS) integration, and custom applications development. 314

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

IT telecommunications and networks. 323

(d) Cybersecurity – the activities related to the secure transmission and storage of 324 electronic information, drafting cyber security policy and procedures, providing 325 user awareness training, risk management, and internal and/or external auditing. 326

Further cyber security activities pertain to selecting and supporting the use of 327 electronic security hardware and software tools and mechanisms including, but not 328 limited to, encryption devices, access control, user identification and authentication, 329 and malicious content detection 330

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

(f) OBAC Subject Matter Expert (SME) personnel will assist OBAC operators with 336

Battlespace Awareness tasks. OBAC SMEs will require demonstrated expertise in 337 both the OPIR domain and Battlespace Awareness missions. SMEs create training 338 materials, administer on the job training sessions with OBAC operators, and act as 339 continuity for the government transitory operations staff to coincide with quarterly 340 deliveries of capability to the OBAC. The SMEs are heavily involved with the 341

TAP Lab capability development and testing so that they are aware and able to train 342 the operations staff upon delivery of new capabilities to OBAC. 343

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

4.0 Task Descriptions 347

4.1 Program Management 348

4.1.1 Program Manager 349

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

Agile software program management. 358

4.1.1.2 The Contractor shall create and annually update a Program Management 359

Plan (CDRL A001). 360

4.1.1.3 The Contractor shall interact with OBAC operational management and 361 stakeholders and SMC/RSX program management to establish a strong understanding of TAP 362

Lab and SEGA product, operational capabilities, and development and testing objectives. 363

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

4.1.1.5 The Contractor shall travel as necessary to meet the objectives of the 366 contract. As requested by the Government, the Contractor shall travel to meetings for the purpose 367 of information gathering, information sharing, coordination and planning. The Contractor shall 368 travel using commercial air, Government air, and other conventional modes. Travel arrangements 369 will be based on individual tasks, and the cost of travel will be directly reimbursed from task 370 funding. All travel Outside Continental United States (OCONUS) and Continental United States 371

(CONUS) requires prior coordination by the COR. Additionally, all OCONUS travel must be 372 approved in advance by the PCO or COR designated by the PCO. All travel requirements 373

(including plans, agenda, itinerary, dates) must be pre-approved by the COR or PCO; and is on a 374 strictly cost reimbursable basis. Costs for travel must be billed IAW the regulatory 375 implementation of Public Law 99-234, Federal Civilian Employee and Contractor Travel Expense 376

Act of 1985 and FAR 31.205-46 Travel Costs and Joint Travel Regulations. 377

4.1.2 Financial Management 378

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

(CDRL A002). 380

4.1.3 Subcontract Management 381

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

4.1.4 Schedule Management 384

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

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

4.1.5 Program Reviews 394

4.1.5.1 The Contractor shall conduct quarterly program management reviews 395

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

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

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

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

4.1.6 Facility Lease 407

4.1.6.1 The Contractor shall bid Other Direct Costs to support paying the facility 408 lease to the building lease holder for the TAP Lab. The lease cost for FY19 is $1.25M and should 409 be assumed to increase at a typical inflation rate. The current building lease is good through 31 410

October 2021; however the government expects to renew the lease through the entire contract 411 period of performance. The Contractor shall continue to support the facility lease through the 412 period of performance. 413

4.2 Engineering 414

4.2.1 Chief Engineer 415

4.2.1.1 The Contractor shall provide a chief engineer, as one of the key personnel 416 on the contract, to oversee all system engineering efforts in support of the tasks in this PWS. 417

Duties include, but are not limited to, leading an IT Working Group, conducting engineering trade 418 studies, recommending engineering courses of action based on the studies, recommending 419 technology refresh actions to keep TAP Lab and SEGA at the forefront of technological 420 advancements, and conducting studies to control the total cost of ownership of the TAP Lab and 421

SEGA environments. 422

4.2.1.2 The chief engineer shall have a master’s degree in Engineering, 10 years of 423 industry-related experience, possess a current TS Clearance with SCI Eligibility, have 5 years of 424

Agile Software Development expertise, and have experience with integration of capabilities into 425

Operational DoD locations. 426

4.2.1.3 The chief engineer shall be the primary contractor voice for all system 427 engineering decisions to include configuration management and control, network status and 428 control, and other system engineering activities as appropriate at the Configuration Approval 429

Boards at TAP Lab and OBAC. 430

4.2.1.4 The Contractor shall create and maintain a System Engineering Master 431

Plan. (CDRL A007) 432

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

4.2.1.6 The Contractor shall create and maintain a Continuous 435

Integration/Continuous Deployment (CI/CD) pipeline for capabilities to be deployed to the SEGA 436

Initial Deploy environment. 437

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

4.2.2 Communications and Network Engineering 440

4.2.2.1 The Contractor shall provide network engineering services. This includes, 441 technical support to all network (WAN/LAN) connectivity at the TAP Lab/OBAC, throughput 442 analysis, firewall recommendations and port configurations as necessary to achieve the desired 443 connectivity to/from TAP Lab/OBAC servers. The TAP Lab and SEGA have network interfaces 444 to RTS, SBIRS Operational Sub-Element (SEGA) and Analytical Sub-Element (TAP Lab) and 445

SIPRNET. Future interfaces will include JWICS in the SCI enclave. The Contractor shall 446 provide support for the TAP Lab and SEGA up to the communications demarcation. Additional 447 communication interfaces will be directed by the government as needed. 448

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

4.2.3 Configuration Management 451

4.2.3.1 The Contractor shall maintain processes and procedures to enable 452 government ownership and control of the technical baseline documentation in accordance with the 453

SMC/RS Enterprise System Engineering Plan. 454

4.2.3.2 The Contractor shall facilitate the change management boards that will be 455 chaired by the appropriate government office as defined in the TAP Lab and OBAC 456

Configuration Management Plans. 457

4.2.3.3 The Contractor shall submit and seek approval for all Configuration 458

Change Proposals (CCP) with the appropriate government approval boards. 459

4.2.3.4 The Contractor shall develop and maintain a government approved TAP 460

Lab Configuration Management Plan. The contractor shall update the plan on at least an annual 461 basis. (CDRL A005) 462

4.2.3.5 The Contractor shall maintain the government approved OBAC 463

Configuration Management Plan. The contractor shall update the plan on at least an annual basis. 464

(CDRL A006) 465

4.2.3.6 The Contractor shall maintain a software repository of all code developed, 466 used, and/or delivered to the government including the SOFA source code. The TAP Lab has 467 leveraged the Defense Intelligence Information Enterprise (DI2E) for software development tools 468

(e.g. Bitbucket, JIRA, Confluence) to maintain version control and address deficiency reports 469

(DRs). The contractor shall utilize these tools or a similar capability to manage the configuration 470 of the TAP Lab and SEGA configured baselines. 471

4.2.3.7 The Contractor shall continuously monitor, review and audit all proposed 472

IT infrastructure technical baseline changes to ensure configuration management and control 473 processes and procedures are met and architectural integrity is preserved. The contractor shall 474 assist the TAP Lab and OBAC government personnel in the improvement of the Configuration 475

Management processes and procedures to meet industry standards, as appropriate. 476

4.2.3.8 The contractor shall maintain a library of relevant documents for users of 477 the TAP Lab. Active specifications, standards, handbooks and other published documents may be 478 required to define completely the characteristics of hardware and software components. The 479

Government will expect the contractor to acquire and deliver needed active documents including 480 operational and maintenance processes, procedures and training documents. Due to the nature of 481 rapid changes in the information processing industry, inactive, out-of-date, superseded, or 482 canceled documents will likely be required to define fully the characteristics of many electronic 483 information systems. The contractor shall acquire, deliver and maintain active and inactive 484 documents such as specifications, standards, handbooks, source control, and other published 485 documents. 486

4.2.4 Training 487

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

4.2.5 Capability Identification and Analysis 493

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

4.2.5.2 The Contractor shall, in accordance with the SMC/RS Enterprise Systems 497

Engineering Plan, convert the Government-approved Capability Needs into system requirements 498 where appropriate. 499

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

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

(CDRL A012) 507

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

4.2.6 Architecture and Design 513

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

4.2.6.2 The Contractor shall provide recommendations for development toolset 516 upgrades on a biannual basis. Purchases will be made from available ODC on this contract, as 517

GFE, or via other contract at lab director’s direction. 518

4.2.7 Hardware Engineering 519

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

Hardware engineering shall research required equipment, prepare procurement requisitions, 521 install, integrate, test, troubleshoot, resolve issues, and maintain the hardware suite for both the 522

TAP Lab and OBAC. 523

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

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

4.2.7.4 The Contractor shall support a TAP Lab test environment that mirrors the 528

SEGA initial deployment to the greatest extent practical. Any deviations of configuration 529 between the Test Environment and the Initial Deploy environment shall be approved by the 530 government. 531

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

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

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

(see applicable documents). 539

4.2.8 Software Engineering 540

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

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

4.2.8.2 The Contractor shall develop, in coordination with the Government, a 546

Continuous Integration/Continuous Deployment (CI/CD) capability to conduct automated 547 building, testing, and deployment of prototype and experimental software. This activity will be 548 initiated with Government’s draft CI/CD pipeline. 549

4.2.8.3 The Contractor shall manage the on-boarding of new software into the TAP 550

Lab. This approach should maximize the use of automated tools for code check in, configuration 551 management, build, code quality evaluation, regression testing, and deployment to lab and other 552 environments as directed by the Government. 553

4.2.8.4 The Contractor shall produce a reference implementation of the CI/CD 554 pipeline, with required cybersecurity protection, capable of rapidly integrating capabilities and 555 deploying them into target environments. This platform will be hosted and tested within the TAP 556

Lab and should utilize open standards and maximize the use of Free and Open-Source Software 557

(FOSS). The Contractor will maximize the use of existing Government investments and facilities 558 to integrate, test and operate the capabilities in order to minimize duplication of work. 559

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

4.2.9 Integration 563

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

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

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

4.2.10 Developmental Unit and Functional Test 572

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

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

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

4.2.11 Acceptance Testing 579

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

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

4.2.12 Operational Testing Support 588

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

4.2.13 Transition 593

4.2.13.1 Working with the operations and sustainment community, the Contractor 594 shall develop and execute disciplined processes for transitioning successful applications and open 595 framework modifications into operations in accordance with the OBAC Configuration 596

Management plan. 597

4.2.13.2 The Contractor shall provide hardware and software integration support for 598 applications and tools that have been generated at the TAP Lab and other development sources 599

(e.g. NASIC, AFRL, NRL) that are selected by the government for deployment to SEGA. 600

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

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

4.2.14 Quality Assurance 608

4.2.14.1 The Contractor shall establish a quality assurance element within its 609 organization that ensures compliance with applicable Federal mandates, contractual performance 610 standards, and industry standards and best practices. The Contractor shall update the Quality 611

Assurance Plan on an annual basis. (CDRL A013) 612

4.2.15 TAP Lab Data Management 613

4.2.15.1 The Contractor shall actively manage the TAP Lab data repositories to 614 ensure adequate data sets for development, test, and validation are available and appropriately 615 controlled and managed for the Research and Development (R&D) efforts awarded to Broad 616

Agency Announcement (BAA), Small Business Innovative Research (SBIR), or other 3rd party 617 vendors. Each TAP Lab security enclave is expected to have its own data repository. The 618

Contractor shall participate in 3rd party scheduling meetings, kick-off meetings, and initial design 619 reviews to identify researcher data requirements, need dates, and delivery methods. If data 620 needed to fulfill the researcher's data needs is not already available within the appropriate enclave 621 repository, the contractor shall retrieve the data from other government sources (e.g. NASIC). 622

This shall include submitting data requests or directly downloading data, transferring the data to 623 the appropriate TAP Lab enclave repository, updating the data repository lists, and/or transfer of 624 data to an approved vendor's facility for initial development and test support. 625

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

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

4.2.16 TAP Lab Website Management 636

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

4.3 Operations 639

4.3.1 Operations Support Subject Matter Expertise 640

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

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

4.3.1.1.1 The Lead SME shall have 10+ years of experience in the SBIRS or 646

OPIR domains with 5+ years of experience in OPIR Data Exploitation or Battlespace Awareness 647 mission areas. 648

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

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

4.3.2 System Administration 654

4.3.2.1 The Contractor shall be responsible for end-to-end operation of networks 655 and IT assets. The Contractor shall designate one Lead System Administrator (SA) on the 656 contract as a key person on the contract. This Lead SA shall be the primary focal point for TAP 657

Lab and OBAC leadership feedback. The Lead SA shall create Standard Operating Procedures 658 that ensure all SAs provide support to the system in a coordinated fashion.(CDRL A011) 659

4.3.2.1.1 The Lead SA shall possess a Bachelor’s Degree in Computer 660

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

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

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

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

4.3.2.5 The Contractor shall provide level 1 system maintenance and assistance 672 functions to researchers and other users of the TAP lab 5 days per week from 7AM to 5PM. The 673 contractor shall be available to correct any deficiencies within one hour of discovery. The 674

Contractor shall support off hours requests for support only after authorization by the government. 675

Such support will be coordinated at least one week in advance. 676

4.3.2.6 The Contractor shall provide level 1 system maintenance and support to 677

OBAC operations, 24 hours per day, 7 days per week, 365 days per year. 678

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

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

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

4.3.2.10 The Contractor shall provide identity management of network access to 688 authorized personnel. 689

4.3.2.11 The Contractor shall adhere to the government provided Patch 690

Management Plan for both the TAP Lab and SEGA. 691

4.3.2.12 The Contractor shall maintain storage systems to enable both a static 692

(permanent) archive of relevant data and events as well as a 30-day rolling archive of raw data. 693

4.4 Hardware, Software, and Facility Support 694

4.4.1 Hardware Support 695

4.4.1.1 The Contractor shall support level 1 hardware maintenance in support of 696 the TAP Lab and SEGA enclaves. Level 1 support includes, but is not limited to, replacing failed 697 line replaceable units, conducting vendor recommended preventative maintenance, monitoring 698 hardware performance, and recommending upgrades/updates based on supportability challenges. 699

4.4.1.2 The Contractor shall implement, at Government direction, maintenance 700 agreements with commercial vendors where appropriate. 701

4.4.1.3 The Contractor shall maintain and update cryptologic equipment in support 702 of TAP Lab requirements. 703

4.4.2 Software Support 704

4.4.2.1 The Contractor shall document deficiencies via the government directed 705 issue tracking system in all currently fielded systems and capabilities and interact with TAP Lab 706 to prioritize and adjudicate corrective actions within future releases. 707

4.4.3 Facility Support 708

4.4.3.1 The Contractor shall modify, upgrade and maintain the facility for the TAP 709 lab. The Contractor shall ensure proper power, heating, cooling, ventilation, lighting, space 710 management, construction, security, and maintenance as…