MIOES Basic PWS (Final Draft RFP 14 Feb).pdf

Missile Defense Agency (MDA) 2

MDA Information Technology Operations & Engineering 4

Solutions (MIOES) Contract 5

Basic Performance Work Statement 26

Dec 17, 2024 33

1.0 Mission 35

1.1 The Missile Defense Agency (MDA) has a continuing need for the research, development, 37 test, evaluation, and integration of Missile Defense System components. These activities rely 38 heavily on MDA Information Management (IM) systems, underlying Information Technology 39 (IT), and facility infrastructure that support rigorous Missile Defense System capability 40 development and business operations for MDA. A Research Development Test and Evaluation 41 (RDT&E) IT ecosystem is required to provide MDA with a secure development, test, digital 42 engineering and modeling environment, and continuous access to unclassified and classified 43 networks and collaboration services. 44

1.2 IM and underlying IT infrastructure is also critical to the daily operations of MDA personnel 46 to collaborate across all classification domains with each other, Senior Department of Defense 47 (DoD) and other United States (US) Government agency personnel, Combatant Commanders, 48 North Atlantic Treaty Organization (NATO) partners, allies, and industry partners. It requires 49 advanced and persistent cybersecurity vigilance that ensures daily operations and 50 communications are protected and safeguarded. 51

1.3 These activities are conducted across MDA’s worldwide enterprise and within the Missile 53 Defense Integration & Operations Center (MDIOC) mission execution platform. 54

1.4 The MDA Information Technology Operations & Engineering Solutions (MIOES) contract 56 operates within the complexities of this dynamic environment and enables MDA to 57 simultaneously conduct Missile Defense System development, testing, warfighter training, and 58 operations support for multiple MDA directorates and Combatant Command requirement owners 59 while executing the MDA enterprise communications and IT mission. This contract offers a 60 capability for government and contractor stakeholders to operate within this environment that 61 requires a continuous, real-time, compliant, cyber secure IT and facility infrastructure capable of 62 conducting concurrent event execution and continuous real world, 24x7x365 mission operations. 63 The MIOES contract enables the rapid response to evolving and emerging priorities of global 64 enterprise communications and IT, RDT&E and mission operations, and operational training in a 65 highly cohesive and collaborative mission environment. 66

2.0 MIOES Scope 68

The work that will be executed under the MIOES contract is summarized in the following 70 technical areas (TA): 71 Technical Area (TA)

Name Description

Enterprise/RDT&E

IM

Global Communications & RDT&E/Enterprise Information

1. Communications Services & Solutions. Operational planning and logistics for the provisioning, development, integration, operations, management, sustainment, and interoperability of reliable communication networks.

2. Enterprise Services & Solutions. Services, solutions and end-user support required to manage MDA’s globally dispersed network that can

Management (IM) Solutions & Integrated Architectures simultaneously support Missile Defense System RDT&E systems and operations.

3. System Architecture Solutions. Development of technical baselines and reference architectures for standard designs and solutions.

4. Mission Assurance and Configuration Management. Governance to establish and sustain effective operations, architectures, solutions, processes.

5. Cybersecurity. Provide Defensive Cyberspace Operations and robust cybersecurity solutions to protect and defend the Missile Defense System

Mission IM

Missile Defense System Mission & Event Operations:

IM Architectures & Solutions

1. Design, develop, integrate, operate, and sustain secure and reliable IM architectures and IT infrastructure, for mission systems enabling a continuous operational readiness posture.

• C2BMC mission laboratories and enclaves

• Ground-Based Midcourse Defense Operations and Training Center

• Ballistic Missile Defense System Network Operations and Security

Center

• Operations Support Center

• Missile Defense Space Enterprise Architecture

• MDA Enterprise Ground Services

• Space Test and Integration Laboratory

• Missile Defense Space Operations Center

• Engineering Web Services and Modeling and Simulation Center

• JFCC-IMD Operations Center

2. Conduct Missile Defense technology maturation, design, development, prototyping, demonstration and testing.

MDIOC Facility Operations

MDIOC Operations, Sustainment, Restoration & Modernization

1. Operate and maintain the MDIOC facility infrastructure.

• Sustainment: maintenance/ repair activities

• Restoration: restoring real property to its designated purpose

• Modernization: alteration/replacement of facilities solely to implement new or higher standards, to accommodate new functions, or replace building components

MDIOC

Integration

MDIOC Planning and Integration

1. Planning and integration to ensure MIOES activities do not interfere with real-world Missile Defense System mission and exercise/test events performed within or supported by the MDIOC range.

2. Develop and execute mission assurance and configuration management practices and alignment to ensure MIOES activities are validated, aligned and integrated with MDIOC standards and processes.

3. Develop, implement, and deliver a MDIOC Range Integrated Schedule

• MDIOC activities, facility infrastructure and maintenance projects, network modifications/projects

4. Develop and maintain the MDIOC facility infrastructure technical baseline.

5. Establish event configuration protections for mission and test assets to prevent unapproved access/changes through physical and logical seals & access restrictions.

A significant requirement of this dynamic environment is the interface, leadership, and 74 management necessary to integrate between all technical areas. Simultaneous events 75 compounded with concurrent research, development, test, and operations compete for both 76 physical assets and personnel resources. This integration and deconfliction requires coordination 77 and resource prioritization to accommodate event schedule changes, facility or IT system 78 changes, test article improvements, and contingency operations. This environment requires the 79 synchronization of capabilities, schedules, and priorities across the program. 80

3.0 MIOES Requirements (Technical Areas 1 – 4) 82

3.1 Global Communications & RDT&E/Enterprise Information Management (IM) 84 Solutions & Integrated Architectures 85

3.1.1 Develop, upgrade, operate, and maintain an RDT&E/Enterprise worldwide IM/IT 87 ecosystem that provides MDA with a secure development, test, digital engineering and modeling 88 environment. This environment serves as the integration point which facilitates the rapid 89 development and delivery of Missile Defense System capabilities and becomes the RDT&E 90 resource for daily operations that includes data analytical decision making, test events and 91 capability delivery to the Warfighter. (Note: for purposes of clarification for the RFP, data 92 analytical decision making is referring to IT service delivery and it's asscociated communication 93 architectures vice "post mission" data analysis. It should be noted that network analysis is 94 imperative to provide ontime trusted data delivery back to the Data Centers or service delivery 95 point(s) of the supported stakeholder. This note will be deleted at time of contract award.) 96

3.1.2 Provide information handling; processing, storage, monitoring, and transport. 98 Perform systems and network management; information dissemination management; and 99 cybersecurity (technical & management) functions. Provide MDA with secure environment to 100 include classified and unclassified IT systems, cloud and data centers, operations and monitoring 101 centers, telecommunications, local and wide-area network infrastructures; and customer services 102 while maintaining an integrated and comprehensive cybersecurity capability across IT systems, 103 enclaves, and networks. 104

3.1.3 Provide effective, efficient, secure, and reliable information network services for 106 critical DoD and MDA communications and information processing integrating accepted 107 industry best practices that align/meet DoD compliance requirements. 108

3.1.4 Provide cybersecurity assurance by utilizing risk management framework (RMF) to 110 establish and maintain security standards and guidance to promote the development of 111 comprehensive and balanced information security programs 112

3.1.5 Utilize a cloud first strategy that enables cloud computing on-demand access, via 114 secure network connectivity, to deliver global IT services to the warfighter and general user base. 115

3.1.6 Maintain an IT as-a-service (ITaaS) capability. Enable the MDA Cloud capabilities 117 to provide on-demand network access to a shared pool of configurable computing resources 118 which can be rapidly provisioned and released. Automate the provisioning of infrastructure-as-a-119 service (IaaS), platform-as-a-service (PaaS), and software-as-a-service (SaaS). 120

3.1.7 Manage two major data centers (Huntsville, AL and Colorado Springs, CO) that 123 provide a mix of classified and unclassified IT services, with each providing disaster recovery 124 and continuity of operations for critical services to the other. 125

3.1.8 Collaboration across multifunctional teams to formulate, plan, implement, manage, 127 track, and evaluate large scale/complex IT architecture/systems projects with an agile approach 128 to rapidly deliver capabilities to the customers. Application of creative and integrated solutions-129 based thinking to spark enduring change and adopt innovative solutions into the Enterprise. 130

3.1.9 Perform Tier III Cybersecurity Roles and Functions services across the entire 132 portfolio of systems to foster an integrated Cybersecurity Management that drives a holistic and 133 collaborative cyberspace program dedicated to delivering a secure and uncompromised Missile 134 Defense System through innovative and optimized cyber resilient initiatives focused on 135 continuously improving MDA cyber capabilities, risk-level, and mission survivability. 136

3.1.10 Analyze, investigate, respond to, and report cyber incidents. Use threat hunting 138 tools to identify cybersecurity risk to MDA Enterprise and RDT&E IT Systems. Monitor MDA 139 cyber terrain and report to DoD. Provide Tier II cybersecurity services. 140

3.1.11 Perform Global lifecycle event management, engineering services, and support for 142 MDA Missile Test Events, Mission/Real World Events, Flight Tests, Ground Tests, 143 Wargames/Exercises, Experiments, and Continuous Developmental Integration (CDI) activities. 144 Includes missile test event requirements management, coordination, planning, architecture 145 development, service solutions, execution support, resource management, asset management, 146 work activity de-confliction. Planning, integration, and execution for all IT 147 requirements/communications in support of flight test, ground test, wargames and exercises, real 148 world missile test events, and CDI. 149

3.1.12 Architectural design, development, and integration of an Enterprise-wide 151 ecosystem of digitally transformative technologies that provide rapid, continuous innovation, 152 increased resiliency, more efficient processes and workflows, and increased cyber security. This 153 ecosystem is the backbone on which all required capabilities are accessed by stakeholders using 154 a federated multi-tenant model. This ecosystem must support the parallel operation of enterprise 155 level capabilities and 24x7x365 RDT&E related capabilities. 156

3.1.13 Positioning, Navigation and Timing (PNT) Resiliency Enhancements. Provide 158

PNT enhancements to improve PNT assurance posture for the Missile Defense System. Provide 159 improved architectural delivery of time and frequency signals to the Missile Defense System 160 elements through testing and analyses associated with incremental improvements as they become 161 available technologically and programmatically. Manage coordination with PNT stakeholders 162 and stay abreast of advancements in PNT threats and capabilities. Integrate with other related 163 agency and warfighter activities and missions to capture interface management, process 164 implementation, and lifecycle management of the PNT enhancements deployed. 165

3.1.14 Provide the MDA Foreign Military Sales (FMS) office with IT administrative and 167 equipment, capabilities and services to MDA personnel supporting security assistance and MDA 168 FMS activities. 169

3.1.15 Develop, maintain, and execute an enterprise common-use IT architecture program 171 and establish governance to develop common-use IT technical baseline standards to include 172 records asset ownership, accountability, and traceability of requirements, architectures, and 173 engineering baselines. Develop technical baseline standards for common-use IT systems and 174 services. Mature the common-use IT technical baseline and ensure standardized governance to 175 engineers, developers, project/systems engineers, and solution architects. Establish technical 176 baseline repository standards for historical artifacts, the provenance of those artifacts, and 177 supporting data. 178

3.1.16 Develop, maintain, and execute an enterprise common-core IT Mission Assurance 180

(MA) program providing a disciplined application of systems engineering, risk management, 181 quality, and management principles to achieve success of IT systems design, development, 182 testing, deployment, and operations. 183

3.1.17 Develop, maintain, and execute an enterprise common-core IT Configuration 185

Management (CM) program to manage and account for consistency, continuity, and the integrity 186 of configured common core IT items and systems. Develop and maintain a technical baseline 187 (Requirements Baseline, Architectural Baseline, and Engineering Baseline) to ensure system 188 configurations are documented and accurately reflect the environment and map ownership of 189 systems to ensure timely information can be provided to impacted stakeholders. 190

3.2 Missile Defense System Mission & Event Operations: IM Architectures & Solutions 192

3.2.1 The MDIOC is host to numerous Missile Defense System operational missions 194 (e.g., Command, Control, Battle Management, and Communications (C2BMC), 100th Missile 195 Defense Brigade (MDB), Joint Functional Component Command for Integrated Missile Defense 196 (JFCC-IMD)), as well as operational test assets (e.g., satellites). Mission IM support, solutions, 197 architecture, design, and engineering must be provided in a manner to maintain an operational 198 readiness posture in order to deliver warfighter mission support and execute the Missile Defense 199 System mission. Develop, implement, integrate, operate, mature, and sustain secure and reliable 200 architectures and an IM infrastructure, while ensuring the following: 201

• Heightened level of responsiveness and the mission assurance rigor to ensure availability 202 of operational Missile Defense System assets 203

• Continuous situational awareness and mission assurance support (24/7/365) as well as the 204 ability to escalate health and status issues of critical infrastructure resources that directly 205 support the operational Missile Defense System assets 206

• Increased responsiveness and mature, technical governance to enable full operation 207

• Mandated hardware, software, interfaces, and configurations 208

3.2.2 Conduct Missile Defense requirements analysis, concept exploration, technology 209 maturation, design, development, prototyping, demonstration and testing. 210

3.2.3 Ensure an integrated, repeatable, scalable, and interoperable IM framework in 212 optimizing agile and secure capabilities to meet mission requirements, maintain full spectrum 213 cyber security resilient capabilities and maintain pace with technological advancements for the 214 following Missile Defense System mission enclaves: 215

• Ballistic Missile Defense System Network Operations and Security Center (BNOSC) 216

• Ground-Based Midcourse Defense (GMD) Operations and Training Center 217

• C2BMC mission laboratories and enclaves 218

• JFCC-IMD Operations Center 219

• Operations Support Center 220

• Missile Defense Space Enterprise Architecture (MDSEA) 221

• Space Test and Integration Laboratory 222

• Missile Defense Space Operations Center (MDSOC) 223

• Engineering Web Services (EWS) enclave and the Modeling and Simulation (M&S) 224

Center 225

• Simulation Interface Unit (SIU) hardware, software, and material 226

3.3 MDIOC Facility Operations & Sustainment 228

The MDIOC is a secure, 4-story, multi-purpose and highly reconfigurable 676,160 square foot 230 research, test, and operations complex comprised of two separate facilities. These facilities reside 231 within the Space Base Delta 1 restricted area on Schriever Space Force Base, CO. 232

3.3.1 MDIOC Facility Operations. Operate, and maintain an efficient, cost effective 234 facility infrastructure in support of MDA elements / components and designated Combatant 235 Commanders' Missile Defense System operations executing missions at the MDIOC. Provide a 236 reliable infrastructure supporting mission-critical Missile Defense System activities as well as a 237 clean, safe, and environmentally responsible infrastructure. Provide a safe and reliable building 238 infrastructure. Maintain a high level of appearance standards. Provide emergency infrastructure 239 to support operations during contingencies. Execute a preventative maintenance program. 240

3.3.2 MDIOC Facility Restoration and Modernization. Facility sustainment, restoration, 242 reconfiguration, and modernization projects required to support MDA mission activities within 243 the MDIOC and its area of responsibility. Provides facility engineering solutions to plan, design, 244 execute and transition of improved or modified facility architectures and infrastructure systems. 245 Management and execution of facility modifications and restoration. Maintain positive 246 configuration control and documentation of facility restoration and modernization activities. 247

3.3.3 Supply Chain Operations. Perform supply chain operations in Colorado Springs, 249 Huntsville, and Fort Belvoir areas in government provided facilities that includes warehouse and 250 receiving area operations such as inspection and acceptance, packaging, shipping, receiving, 251 ground handling, storage, distribution, transportation and inventory management. 252

3.4. MDIOC Planning, Integration, Operations 254

3.4.1 Process Development 256

3.4.1.1 Develop processes to ensure MDIOC facility mission assurance and configuration 258 management for facility projects that will be executed under the MIOES contract. Ensure processes 259 are integrated with each other and align with the MDIOC level plans (e.g., MDIOC Systems 260 Engineering Plan, MDIOC Mission Assurance Plan, MDIOC Configuration Management Plan). 261 Develop processes that ensure MIOES activities impacting the MDIOC facility are validated, align 262 with facility standards, and solutions are integrated across the MDIOC facility through the MDIOC 263 Engineering Review Board. 264

3.4.1.2 Develop processes to establish how change occurs to the MDIOC facility technical 266 baseline. Develop standards that can determine which baselines are impacted by a stakeholder 267 requirement and the process to update controlled baseline artifacts as a result of that requirement. 268 Identify and track configuration items through the defined engineering lifecycle to ensure a low risk 269 posture to the MDIOC Range. 270

3.4.2 Event Situational Awareness Development 272

Develop, implement, and deliver a time-phased MDIOC Range Integrated Schedule that includes 274 Concurrent Test and Training Operations (CTTO) activities, facility infrastructure and maintenance 275 projects, major network modifications/projects, and base projects with potential to impact MDIOC 276 range activities. 277

3.4.3 Operations Assessment Development 279

Monitor integrated planning and operations that will enable effective and efficient ongoing integrated 281 planning and operations activities across the MDIOC range. The method generated will be based 282 upon key priorities for ensuring risk mitigation for any impacts to the MDIOC. 283

3.4.4 MDIOC Facility Mission Assurance 285

3.4.4.1 Champion all requirements through the MDIOC Facility Boards (e.g. Engineering 287 Review Board, Configuration Control Board, Range Risk Board, Range Outage Board) by 288 coordinating and communicating the MIDIOC facility standards, board artifact submission 289 requirements, and actions required under each board charter with those stakeholders who will be 290 presenting at the MDIOC boards. Identify, track, and resolve issues. 291

3.4.4.2 Maintain the MDIOC facility technical baseline to ensure facility system 293 configurations are documented to accurately reflect the environment and map ownership of systems 294 to ensure provision of timely information to impacted stakeholders. The technical baseline consists of 295 Requirements Baseline, Architectural Baseline, Engineering Baseline. 296

3.4.5 Event Protection 298

3.4.5.1 Establish event configuration protections for mission and test assets through physical 300 and logical seals and access restrictions to prevent unapproved access or changes. Coordinate and 301 communicate planned and emergent MDIOC range outages, incidents, issues and concerns, 302 communicate mission impacts and the ongoing activities to restore normal conditions. 303

3.4.5.2 Facilitate government review and approval of work during Event Protection Periods 305 (EPPs) to prevent adverse impacts to flight/ground test events and wargame/exercise execution. 306 Participate in the MDIOC Range Work Screening Team during EPPs to review and authorize 307 physical/logical work taking place in the MDIOC range to prevent mission and event impacts from 308 occurring. 309

3.5 Contract Leadership & Management 311

3.5.1 Provide collaborative, flexible, and responsive leadership and management to 313 innovate, set standards and goals and execute and control all activities across the MIOES 314 contract. Provide workload capacity planning, monitoring, coordination, and integration and 315 program integration that results in a consistent requirements execution methodology and mission 316 assurance. 317

3.5.2 Plan, integrate, coordinate, communicate, and manage cost, schedule, and 319 performance, to enable disciplined work performance, technical direction, surveillance, resource 320 application, reporting and the management of requirements, resources, business systems, and 321 data. 322

3.5.3 Provide collaborative and agile program integration required to innovate and 324 establish MIOES contract-wide, enterprise standards to execute seamlessly all activities across 325 the MIOES contract. 326

3.6 Business Planning 328

3.6.1 Define, coordinate, and develop plans to coordinate, integrate, and align all 329 activities, projects, and solutions across the MIOES contract. 330

3.6.2 Develop overarching processes to ensure MIOES activities, projects, solutions are 332 validated and aligned and adhere to established engineering principles, processes, architectures, 333 baselines, MDA test and event governance, and MDIOC facility standards. 334

3.6.3 Develop methods to monitor and surveil MIOES integrated planning and 336 operations that enables the government and contractor to evaluate the effectiveness and 337 efficiency of ongoing integrated management, planning and operations activities across the 338 MIOES contract. 339

3.7 Business Controls 341

3.7.1 Monitor, measure, control, and report contract cost, schedule, and performance metrics 342

4.0 Other Requirements 344

4.1 Provide a workforce capable of handling, processing, and protecting critical 345 unclassified information and classified information in accordance with DoD, MDA, Program, 346 and mission/event specific security requirements. Comply with the security requirements and 347 mission/system specific security requirements outlined in the DD 254. Comply with the 348 Information Management and Control Plan. 349

4.2 Develop, implement, and maintain a procurement and government property control 350 program that ensures compliance with Federal, DoD, and MDA directives and policy for the 351 procurement, tracking and management of Government Property, Government Furnished 352 Property and Contractor Acquired Property. Property to include consumables, equipment, 353 hardware, and software. Government property necessary for accomplishment of requirements 354 will be identified within individual task orders. 355

4.3 Develop and execute supply chain risk management practices in order to identify 356 supply chain vulnerabilities, threats, and potential disruptions and implement mitigation 357 strategies to ensure the security, integrity, and uninterrupted flow of materials, products, and 358 services. 359

4.4 Develop and execute information security, personnel, operations, physical, export 360 control, and cybersecurity controls and processes in accordance with Federal, DoD, and MDA 361 regulations, policies, procedures, standards. 362

4.5 Comply with applicable federal, state, and local Environmental Safety and Health 363 laws and regulations, Executive Orders, and policies in all phases of program execution. 364

4.6 Develop, implement, and maintain systems engineering, mission assurance, 365 configuration management, enterprise architecture, quality assurance, risk management 366 programs. 367

4.7 Comply with the MIOES Performance Evaluation and Incentive Plan as tailored in 368 each task order PWS. 369

4.8 Delivery of all Contract Data Requirements List (CDRL) products as instructed in 370 each task order PWS. 371

4.9 Research, procure, develop, integrate and perform continuous monitoring/assessment of risk 372 adverse products and solutions to support the MDA's requirements. This includes designing, 373 building, securing, operating, defending and protecting MDA resources. This shall include the 374 skills and knowledge required to build and maintain a comprehensive cyber resilient program 375 that incorporates zero trust principles, ensuring the systems uphold the highest level DoD and 376 MDA cybersecurity compliance standards throughout the lifecycle of each program. 377

4.9.1 Identify, manage, verify, and validate Cybersecurity requirements in the 378 same manner as all other program requirements; 379

4.9.2 Integrate Cybersecurity considerations into program systems engineering 380 and design processes. 381

4.9.3 Provide support, source data, and analysis required to support the 382 Government in obtaining system authorization in accordance with DoD Instruction 383 8510.01, Risk Management Framework (RMF). 384

4.9.4 Provide support, analysis of the MDA Cybersecurity insider threat program, 385 computer network defense support program, and RMF efforts within the supported 386 programs. 387

4.10 Directives/regulations that are applicable to all task orders are identified in 388 Attachment 3, Compliance Documents. Tailoring, as necessary, may be done at the task order 389 level. 390

5.0 Telework and Remote Work 391

5.1 Telework 393

5.1.1 Routine Telework. Work performed at an alternate work located no further 395 than 50 miles from the Government facility on a regular/recurring basis unless 396 specifically prohibited in the Performance Work Statement (PWS). Example when this 397 may be appropriate are when the requiring activity determines a function can be 398 performed at a non-Government provided location and/or when workspace at the 399 Government facility is unavailable and the functions can be performed via a telework 400 arrangement with “as required” access to the Government facilities, e.g., hoteling 401 workspace, required meetings, etc. 402

5.1.2 Situational Telework. Situational is an arrangement where the employee 404 performs work at the primary office worksite. Telework is only approved on a short-term 405 basis for good cause. Examples of situations when situational telework may be 406 appropriate are when an employee needs to complete discrete portions of projects or 407 work assignments, recovery from a short-term illness and/or injury, when office space is 408 unavailable due to renovations, or when OPM announces the Federal Government 409 operating status, in the area of the Contractor’s regular worksite as, “Open with an Option 410 for Unscheduled Telework.” 411

5.1.3 Remote Work. Remote work is an arrangement that allows the contractor 413 employee to perform work during any part of regular, paid hour, at an alternative 414 worksite located more than 50 miles from the identified Government facility as stated in 415 Performance Work Statement (PWS). Remote Work is authorized when it meets PWS 416 requirements or contract terms and conditions unless specifically prohibited in the PWS. 417 The Contractor is wholly responsible for its employees and shall ensure that they are 418 productive and are in compliance with security and safety requirements during remote 419 work. Remote work must be supported by an advantageous business case analysis 420 coordinated with and approved by the requiring activity and IS Program Office. The 421 Government reserves the right to modify, in whole or in part, or terminate, in whole or in 422 part, any remote work authorization, if it is determined to be in the Government’s 423 interest. The Contracting Officer will provide written notice of modification or 424 termination with specifics 30 days prior to the anticipated effective date. There shall be 425 no increased cost to the Government for remote work. 426

5.1.4 In cases where the Government authorizes an alternate location, equivalent 428 workstation and collaboration/communication equipment that would normally be 429 provided in a Government-provided location will be furnished to the Contractor as 430 Government Furnished Property. The Contractor assumes, until such time it is returned, 431 responsibility for the equipment once it is assigned to its employees. The Contractor 432 and/or its employee acknowledges receipt of the property with the closure of the MDA 433 Kinetic Service Request (KSR). The Government will continue to provide network 434 connection via VPN and technical support for the equipment provided. The Government 435 will not provide internet connectivity for Contractor employees. Upon contract award, a 436 copy of the contractor's remote work policies and a sample employee agreement shall be 437 submitted to the Contracting Officer for review. 438

6.0 Predominate MDA Facilities 440

6.1 Schriever SFB, CO and MDIOC 441

Access to Schriever SFB (SSFB) is strictly controlled; to access the installation requires a 442 sponsorship by a person assigned/employed on the installation for personnel who do not possess 443 some form of current federal government issued identification. The MDIOC is located within a 444 USAF restricted area on SSFB, contractor employees require at a minimum a National Agency 445 Check Investigation (NACI) and a Visit Authorization Request (VAR) for issuance of a 446 temporary or permanent badge that allows unescorted access to the restricted area. 447 In order to qualify for issuance of a Restricted Area Badge/Automated Entry Control Card, the 448 respective member must physically enter the Restricted Area once a week for at least a 90-day 449 increment to perform official duties that warrant unescorted entry authorization, and at least once 450 a week entry into the RA after the 90-day period has surpassed. The Commander may grant 451 individuals access to the Restricted Area after the following has been completed: 1) the 452 contractor completes the Standard Form (SF) 85P and it is submitted to Office of Personnel 453 Management (OPM) for a National Agency Check Investigation (NACI); 2) a check of the 454 Defense Clearance and Investigation Index (DCII) reveals no relevant, significant information 455 which might preclude unescorted access; and 3) a check of the appropriate local records has been 456 accomplished. Since access to the MDIOC is controlled, it is important to understand the 457 potential impacts to the contractor(s) ability to accommodate/respond to requirement fluctuations 458 (e.g., surge support, competing/overlapping schedules, etc.); this potential impact must be 459 considered in all proposed solutions. 460

6.2 Redstone Arsenal, AL and MDA Controlled Space(s). 461

To gain access to Redstone Arsenal, a VAR is required and needs to be approved by a 462 Government POC in order to gain access. If an individual meets the criteria and they have a 463 CAC, then a MDA form 10 signed by their Government POC or security manager will be needed 464 to enroll them into our access control system. 465 A CAC is required to access Redstone Arsenal. Individuals that don't have a CAC can have their 467 Government POC send a request to the Redstone Visitor Center so the individual can gain 468 access. Contact MDA Security Operations Center for information and procedures pertaining to 469 MDA controlled space(s). 470

6.3 Fort Greely, AK and Missile Defense Complex Restricted Area. 472 Access to Fort Greely Army Garrison (FGA) is a Closed Post; contractor employees must have a 473 local government sponsor and will be required to pass a National Crime Information Center 474 (NCIC) Criminal Background Check review prior to unescorted entry. Contractor employees 475 that possess at least an interim Secret security clearance will not be required to submit an NCIC 476 criminal background check. Procedures and information pertaining to access is available by 477 contacting the Fort Greely Installation Visitor Control Center. Additionally, the Missile Defense 478 Complex (MDC) is a designated restricted area on FGA. Contractor employees requiring 479 unescorted entry to the MDC must have an approved VAR on file, possess an interim Secret 480 security clearance at a minimum and have local government approval. Contact MDA/GMF 481 (Ground-based Midcourse Defense Operations Support at FGA) Security Manager at for 482 additional information on FGA restricted/control area access requirements. 483

6.4 Vandenberg SFB, CA and Restricted Areas containing Ground-based 485 Midcourse Defense (GMD) assets. 486

6.4.1 Vandenberg SFB: Personnel who do not possess some form of current federal government 488 issued identification to access the installation, and those who do not possess a need to enter the 489 installation on a regular basis require sponsorship by a person assigned to or employed on the 490 installation. Contact your sponsor or the Security Forces Visitor Control Center for procedures 491 and information pertaining to installation access. 492

6.4.2 Vandenberg SFB Restricted Areas: Additionally, there are restricted areas on Vandenberg 493 SFB that contain MDA resources. Contractors are required at a minimum a National Agency 494 Check Investigation (NACI) for unescorted access to the restricted area(s). Contractors 495 operating 90 consecutive days may be issued a permanent Restricted Area badge for unescorted 496 access to the GMD site; terms will apply badges stay at VSFB with Security POC. Commanders 497 or Equivalent may grant individuals access to the Restricted Area after the following has been 498 completed: 1) completion of the Standard Form (SF) 85P and it is submitted to Office of 499 Personnel Management (OPM) for a National Agency Check Investigation (NACI); 2) a check 500 of the Defense Clearance and Investigation Index (DCII) reveals no relevant, significant 501 information which might preclude unescorted access; and 3) a check of the appropriate local 502 records has been accomplished. Since access to the GMD operational areas are restricted, it is 503 important to understand the potential impacts to the contractor(s) ability to 504 accommodate/respond to requirement fluctuations (e.g., surge support, competing/overlapping 505 schedules, etc.); this potential impact must be considered in all proposed solutions. Contact 506 Security Forces at 805-606-1853 for procedures and information pertaining to restricted area 507 access. 508

6.5 Naval Support Facility-Dahlgren, VA and MDA Controlled Space(s). 509 Access to Dahlgren is strictly controlled; to access the installation requires a visit request 510 sponsored by a person assigned/employed on the installation at the Pass & Identification (ID) 511 center for personnel who do not possess some form of current federal government issued 512 identification. A picture ID is required prior to the issuance of guest badge and a temporary car 513 pass from the Pass & ID center for installation access. Contact the Dahlgren Visitor 514 Control Office for procedures and information pertaining to installation access. MDA facilities 515 are controlled areas and require an approved Visitor Access Request (VAR) or an enrolled DOD 516 CAC to gain unescorted entrance to any of the facilities. Unescorted access is granted to cleared 517 MDA personnel and contractors and to other persons who, in the course of official business, 518 have a current security clearance on file, a need to conduct MDA business, and have a need to 519 know. Contract personnel are approved for access through CORs and Security Managers; their 520 issued DOD CACs are then enrolled for building access. Contact MDA Dahlgren Security 521 Operations Center for information and procedures pertaining to MDA controlled space(s). 522

6.6 Ft. Belvoir, VA and MDA Headquarters Command Center. 523

Access to Ft. Belvoir is strictly controlled; to access the post requires personnel with a legitimate 524 need, but without some form of current federal government issued identification, to stop at the 525 visitor center and complete paperwork for a temporary access pass. Contact the US Army 526 Garrison, Ft. Belvoir visitor center for information and procedures pertaining to post access. 527 MDA Headquarters Command Center (HQCC) is a controlled area facility and requires an 528 approved VAR or an enrolled DOD CAC to gain unescorted access. Unescorted access is 529 granted to cleared MDA personnel and contractors and to other persons who, in the course of 530 official business, have a current security clearance on file, a need to conduct MDA business, and 531 have a need to know. Contract personnel are approved for access 532 through CORs and Security Managers; their issued DOD CACs are then enrolled for building 533 access. Contact MDA HQCC Security Operations Center for information and procedures 534 pertaining to MDA controlled space(s). 535

6.7 Pacific Missile Range Facility and Aegis Facility Access. 536 Access to Pacific Missile Range Facility (PMRF) is controlled; to access the installation requires 537 a sponsorship by a person assigned/employed on the installation for personnel who do not 538 possess some form of current federal government issued identification. It is strongly 539 recommended you contact the Security Pass & ID Office for procedures and information 540 pertaining to installation access. Due to the geographical location of PMRF MDA, contractors 541 supporting missions at that location will require prior Government approval for travel due to 542 limited supporting resources. Each visit requires an MDA PMRF Arrival/Departure (A/D) Form 543 -send an unencrypted email to pmrfarrival-departure@mda.mil to request a form. 544

6.8 Outside the United States, Puerto Rico, U.S. possessions and trust territories. 546 Performance will occur at various MDA and/or other government locations as directed by the 547 Performance Work Statement. The contractor shall abide by government security requirements 548 mailto:pmrfarrival-departure@mda.mil per NISPOM Chapter 6 The cognizant security office at the performance location is MDA or the 549 host installation. 550

Attachment 1 552 Performance Work Statement (PWS) Task 8.1 553

Background: 555 Under the current IRES contract, Task Order 8002 includes IRES Program Management and 556 Program Integration for the overarching contract level requirements. This task is traditionally 557 where more senior level program and functional leaders charge their time against contract level 558 requirements that are applicable to all task orders. It represents work that is not easily severable 559 between task orders or would be burdensome to charge multiple increments of time against 560 multiple task orders. This same task order also has a requirement for MDIOC Mission 561 Engineering. 562 Under the MIOES contract, there will not be a single task order for the MIOES Program 563 Management and Integration tasks. Instead, the contractor shall create an “overhead/indirect” 564 type account that collects these costs that can then be charged against each task order. Under 565 MIOES there will still be a single task order for Mission Engineering requirements. 566 The PWS language below represents the MIOES Program Management and Integration 567 requirements which will be documented in the Basic PWS and referenced as a task in the PWS 568 for each task order. This task will be identified as 8.1 under each task order and costs shall be 569 allocated to each individual task order. 570 The Government will have a separate Contracting Officer Technical Representative that will 571 provide technical oversight and surveillance against this task. In additiona, a separate, single 572 Status Report will be required to report the performance, cost, schedule status of this task. 573 Contract Data Requirements List (CDRL) Requirements: 575

Task CDRL DID Title

8.1.1.3 A8.1.01 DI-MGMT-80004 Management Plan

8.1.1.7 A8.1.02 DI-MGMT-80368A Status Report

8.1.2.2 A8.1.03 DI-MGMT-81861 Contract Summary IPMDAR – Cost Only - DFARS

EVMS not applicable

8.1.2.3 A8.1.04 DI-FNCL-81765C Contractor Business Data Report—CCDR DD

Form 1921-3

8.1.2.3 A8.1.05 DI-MGMT-82164 Quantity Data Report—Flexfile Contractor Cost

Data Report (CCDR)

8.1.2.3 A8.1.06 DI-FNCL-82162 Cost and Hour Report (Flexfile) -- CCDR)

8.1.2.13 A8.1.07 DI-MGMT-1334D Contract Work Breakdown Structure (CWBS)

8.1.2.14 A8.1.08 DI-MGMT-81468A Contract Funds Status Report (CFSR)

8.1.9.2 A8.1.09 DI-MGMT-82256 Supply Chain Risk Management Plan

8.1.10.1 A8.1.10 DI-MGMT-82041B Small Business Participation Report 8.1.12.1.

A8.1.11 DI-MGMT-82383 Information Management and Control Plan (IMCP)

8.1.13.1 A8.1.12 DI-MISC-80508B MIOES Contract Phase-Out Plan

8.1 MIOES Contract Level Management 579

8.1.1 Program Management and Leadership 581

The contractor shall plan, integrate, coordinate, communicate, and manage cost, schedule, 582 performance, and risk to enable disciplined work performance, technical direction, surveillance, 583 resource application, reporting and the management of requirements, resources, business 584 systems, and data. 585 Standards: 587

8.1.1.1 Perform functions required to ensure proactive and sustained operational 588 excellence in providing accurate, safe, secure, timely, program integration across all 589 applicable Task Orders (TOs) to deliver capabilities and solutions. 590

8.1.1.2 Provide a Program Manager (PM) with authority to act on behalf of the entire 591 contractor team that has local autonomy and full authority to commit the corporate 592 resources to execute the MIOES contract. 593

8.1.1.3 Deliver a MIOES Management Plan and manage all activities within the plan. 594

(CDRL A8.1.01). 595

8.1.1.4 Manage Portfolio/Project Management practices in a way that enables technical 596 consistency and cost effectiveness while providing an adaptable framework for planning, 597 managing, and completing projects for a broad range of tasks and missions. 598

8.1.1.5 Adjust processes and resources in balancing risks and opportunities. 599

8.1.1.6 Implement tools, training, and processes that will foster sustainable innovation 600 into daily operations that will improve effectiveness and efficiencies and reduce costs in a 601 resource-constrained environment, while minimizing risk. 602

8.1.1.7 Deliver a Task 8.1 Status Report for all PWS paragraph 8.1 activities that reports 603 integration efforts, status, accomplishments, and issues to promote full and transparent 604 communications (8.1 activites shall not be reported in the individual task order status 605 reports) (CDRL A8.1.02). 606

8.1.1.8 Mitigate workforce surge and draw-down impacts by analyzing workforce trends, 607 forecasting workforce needs, and hiring to those requirements. 608

8.1.1.9 Maintain a qualified workforce as demonstrated by training and skills 609 certification, engineering and operations workforce experience, educational attainments 610 and security clearances. 611

8.1.1.10 In–process and out-process employees in the Program Resource Internet 612 Database Environment (PRIDE) Workforce Integration Tracking system (WITS) in 613 accordance with MDA 1400.07-INS. 614

8.1.1.11 Complete the MDA Form 14 –Out-Processing Checklist, as required by MDA 615 Instruction 1400.07-INS, and return the completed checklist, with all required signatures, 616 to the cognizant Contracting Officer’s Representative (COR) prior to the departure of the 617 employee. 618

8.1.1.12 Provide management, oversight, and quality control for program control 619 documentation, processes, and reports. 620

8.1.1.13 Implement all business systems in accordance with DCAA and DCMA 621 directives and participate in business system reviews and correct deficiencies as defined 622 in the findings. 623

8.1.1.14 Prepare for and participate in mandated audits, such as Inspector General, Cyber 624 Operational Readiness Assessment, physical security, environmental and safety, and 625 property. 626

8.1.1.15 Comply with Workplace Next manpower allocations for on-site and telework 627 positions. 628

8.1.2 Measurement and Control 630

The contractor shall monitor, measure, control, and report contract cost, schedule, and 631 performance metrics 632 Standards: 634

8.1.2.1 Implement and administer a compliant Earned Value Management System 635 (EVMS) for utilization on all applicable TOs. 636

8.1.2.2 Deliver a MIOES-level Integrated Program Management Data and Analysis 637 Report (IPMDAR (Contract Summary IPMDAR – Cost Only) (CDRL A8.1.03). 638

8.1.2.3 Systematically collect and report actual contract costs segregated by non-639 recurring and recurring, functional category, and by unit and/or lot as designated by the 640 government provided Cost Data Summary Report (CSDR) Plan (DD Form 2794) 641 (Reference Attachment 5), (CDRL A8.1.04, Contractor Business Data Report—CCDR 642 DD Form 1921-3, CDRL A8.1.05, Quantity Data Report—Flexfile Contractor Cost Data 643 Report (CCDR), CDRL A8.1.06, Cost and Hour Report (Flexfile) -- CCDR). 644

8.1.2.4 Provide one report at the IDIQ level that includes all costs of all task orders 645 represented as Order/Lot IDs. 646

8.1.2.5 Provide a list of all subcontractors on the contract in a resource distribution table 647 as outlined in the CDRL. 648

8.1.2.6 Notify the Government of all subcontractors expected to have a contract value 649 greater than $20M over the life of their subcontract as outlined in the CDRL 650

8.1.2.7 Flow down requirements contained from the prime contract to the subcontractors 651 as outlined in the CDRL. 652

8.1.2.8 Include the subcontractor’s submission with the prime contractor’s submission 653 (prime contractor submission will not be evaluated without the subcontractor 654 submission). 655

8.1.2.9 Participate in a CSDR Readiness Review which finalizes the contractor’s CSDR 656 process to satisfy the guidelines contained in the DoD 5000.04-M, CSDR Manual, and 657 the requirements in the CSDR plan. 658

8.1.2.10 Accept or propose changes to expand the Government-provided preliminary 659 WBS as provided in the CSDR Plan to represent how the contractor plans to accomplish 660 the contract scope of work consistent with the contractor’s internal organization and 661 processes. 662

8.1.2.11 Participate (prime and subcontractor) in a semi-annual Common Cost 663 Methodology Working Group (CWG) as described in MDA Directive 4250.02 – Missile 664

8.1.2.12 Defense System Cost Estimating and perform cost estimating analysis in 665 accordance with the MDA Cost Estimating and Analysis Handbook, and provide data to 666 support the CWG. 667

8.1.2.13 Deliver a Contract Work Breakdown Structure (CWBS) (CDRL A8.1.07). 668

8.1.2.14 Deliver a Contract Funds Status Report (CFSR) (CDRL A8.1.08) 669

8.1.3 Program Integration. 672

The contractor shall provide comprehensive and enforceable, collaborative and agile program 673 integration required to establish enterprise level standards, for non-mission systems and 674 networks, in order to seamlessly execute all activities across the MIOES contract. 675 Standards: 677

8.1.3.1 Implement program integration elements that enable the integration of people, 678 processes, and tools that aligns capabilities, resources, schedules, and priorities across the 679 contract. 680

8.1.3.2 Plan, schedule, organize, and report on internal process audits and evaluate 681 organizational processes at the enterprise level and across TOs that drive integration 682 across the contract. 683

8.1.3.3 Capture and maintain data to enable schedule integration and forecasting of 684 activities across the contract. 685

8.1.3.4 Discover, manage, and communicate dependencies and potential impacts to 686 critical path activities across all appropriate stakeholders and develop Courses of Action 687 and mitigation strategies for government approval. 688

8.1.3.5 Comply with the MDA and MDIOC Facility Systems Engineering Plans (SEP) 689 across all task orders. 690

8.1.3.6 Report Program Integration successes, challenges, and gaps in the Task 8.1 Status 691…