MIOES Mission Engineering Task Order (07 Feb 25).pdf

PERFORMANCE WORK STATEMENT 4

MDA Information Technology Operations & Engineering Solutions (MIOES) 6

Contract Number: TBD 9

Task Order Title: Mission Engineering 12

Task Order Number: F-4000 14

Period of Performance: 2 Year Base (with 6 one-year options) 15

Contract Type: Cost Plus Award Fee 17

1.0 Background 21

The DoD Mission Engineering Guide states; “Mission engineering is a process that helps the 22 DoD better understand and assess impacts to mission outcomes based on changes to systems, 23 threats, operational concepts, environments, and mission architectures.” This task order executes 24 all MDIOC facility Mission Engineering requirements and provides the governance and 25 assurance of standard ME practices across the MIOES contract. 26

2.0 Scope 27

The purpose of this task order is to protect Missile Defense System (MDS) baseline integrity 28 while supporting the successful technical execution of all Missile Defense Agency (MDA) 29 events and mission activities performed under the MIOES contract. 30

3.0 Contract Deliverable Requirements List (CDRL) 32

The point of delivery for all CDRL products, except as noted in Exhibit C, is the MDA 33 Electronic Content and Records Tool (E-CaRT) system. The contractor shall deliver all such 34 products by saving and profiling them in E-CaRT, with the appropriate notification of delivery 35 letter transmitted electronically to the Government’s Data Management Office (DMO). 36 Reference Exhibit A for specific CDRL delivery instructions. 37

Task CDRL DID Title

8.2.1.3 A001 DI-MISC-

80368A/T Status Report, [Month Ending]

8.2.2.2 A002 DI-MGMT-

81861C

Integrated Program Management Data and Analysis Report (IPMDAR)

8.2.3.1 A003 DI-MGMT-

81453A

Data Accession List (DAL)

8.2.4.1 A004 DI-MISC-

80508B/T

Task Order Close-Out

8.3.1.15 A005 DI-SESS-81785 MIOES Systems Engineering Management Plan

8.3.2.4 A006 DI-MISC-80508B MDIOC Facility Reliability, Availability, and

Maintainability and Failure Modes Effects and Criticality Analyses (RAM/FMECA) Report

8.4.1.3 A007 DI-MISC-

80508B/T

MIOES Mission Assurance (MA) Plan

8.4.1.9 A008 DI-MISC-

80508B/T

MDIOC Incident Notification Report

8.4.3.2 A009 DI-MISC-

80508B/T

MDIOC System Description Documentation

8.4.3.5 A010 DI-MISC-

80508B/T

MDIOC Facility Sustainment Plan

8.5.1 A011 DI-SESS-80858D MIOES Configuration Management Plan

8.6.2 A012 DI-QCIC-81794 MIOES Quality Management Plan

4.0 Reserved 40

5.0 Government Property/Government Furnished Property/Government Furnished 41 Information/Contractor Acquired Property 42

The contractor is required to be in compliance with FAR 52.245-1, Government Property. The 43 Logistics and Product Support task order under the MIOES contract will provide the following 44 integrated support capabilities and requirements for all task orders under the MIOES contract: 45 warehouse operations, inspection, shipping, receiving, tagging, cataloging, packaging, handling, 46 storage, transportation (local and third party) and life cycle property management from receipt, 47 periodic inventories to disposal operations. All other activities required to be in compliance with 48 FAR 52.245-1, shall be performed under this task order. 49

6.0 Other Requirements 51

None 52

7.0 Applicable Directives/Regulations 54

In addition to the issuances identified in the Contract, the following are applicable to this task order: 55

Title Originator Date

Version

8.1 MIOES Contract Level Management (Reference Basic PWS, Task 8.1) 57

8.2 Task Order Management 58

8.2.1 Task Order Program Management and Leadership 59

The contractor shall provide task order (TO) level program management and leadership ensuring 60 execution, oversight, and administration of all TO requirements within the integrated framework 61 of the contract. The contractor shall monitor performance, manage risks, and provide quality 62 deliverables, adhering to DoD and Agency standards. 63 Standards: 65

8.2.1.1 Lead, manage, and execute TO activities in accordance with the MIOES Program 66 Management Plan. 67

8.2.1.2 Manage technical, cost, and schedule performance and associated risks and 68 provide updates at the Risk Review Boards. 69

8.2.1.3 Provide situational awareness by reporting on items such as the following: Status 70 of technical, cost, and schedule performance, significant accomplishments and customer 71 concerns, TO risks, mitigation, and remediation status, performance trends and progress 72 against Quality Assurance Surveillance Plan (QASP) metrics. (CDRL A001) 73

8.2.1.4 Operate within and follow the contract wide processes and governance models in 74 executing systems engineering, mission assurance, quality assurance, configuration 75 management requirements outlined in the PWS. 76

8.2.1.5 Participate in and deliver Integrated Product Team artifacts in preparation of TO 77 modifications and follow-on TOs. 78

8.2.1.6 Develop and deliver proposals in accordance with the RFP letter from the PCO, 79 for TO modifications and follow-on task orders. 80

8.2.1.7 Prepare for and participate in audits, such as Inspector General, IT security, cyber 81 security, physical security, GAO, property, environmental, health and safety. 82

8.2.1.8 Comply with export control requirements (e.g., ITAR, 22 CFR 120-130) and 83 technical assistance agreements. 84

8.2.1.10 Provide a cleared, cyber workforce certified IAW DoDM 8140.03, with all 85 positions documented in the Cyber Workforce Qualifications Tracker (CWQT): 86 o Position Title, Description, and DoD Cyberspace Workforce Framework (DCWF) 87 Cyber Code Alignment. 88 o Security Clearance, Sensitivity Level, and System Privilege Level. 89 o Verification and quarterly validation of contractor-filled roles in MDA CWQT. 90

8.2.1.11 Lead, manage, and execute TO activities in accordance with the approved Cyber 91 Resiliency Management Plan. 92

8.2.1.12 Explore and recommend reporting requirements outlined in the PWS that can be 93 satisfied through dashboard reporting. Recommendation to be included in the Status 94 Report CDRL. 95

8.2.2 Task Order Measurement and Control 97

The contractor shall monitor, measure, control, and report contract cost, schedule, and 98 performance metrics at the TO level. 99 Standards: 101

8.2.2.1 Implement and administer a compliant Earned Value Management System 102

(EVMS). 103

8.2.2.2 Deliver the Integrated Program Management Data and Analysis Report 104

(IPMDAR). (CDRL A002) 105

8.2.2.3 Integrate the TO Integrated Master Schedule (IMS) into the MIOES Integrated 106 Schedule (IIS) (IIS dictated in the IPMDAR) 107

8.2.2.4 Perform a Baseline Review or Integrated Baseline Review within 90 days of 108 contract award. 109

8.2.2.5 Provide subcontracting and limitation of funds oversight, and execution of TO 110 modifications and awards. 111

8.2.2.6 Provide management, oversight and quality control for program control 112 documentation, processes, and reports. 113

8.2.3 Data Accession List (TO Level) 115

The contractor shall provide a Data Accession List (DAL). 116

8.2.3.1 Deliver the DAL, providing a medium for identifying contractor internal data 118 which has been generated. (CDRL A003) 119

8.2.3.2 Provide a document reference number for each DAL item for rapid retrieval from 120 contractor data sources. 121

8.2.4 Task Order Close-Out 122

The contractor shall execute TO close out procedures, consolidate TO data, to ensure a seamless 123 closeout of TO activities. 124 Standards: 126

8.2.4.1 Perform a TO closeout that consolidates all TO data and deliver a Task Order 127 Close-Out Report. (CDRL A004) 128

8.3 Systems Engineering 130

8.3.1 The contractor shall implement, execute, and enforce a Systems Engineering (SE) 131 program IAW the MDA and MDIOC Systems Engineering Plans. The contractor shall 132 develop and implement engineering processes across the MIOES contract and MDIOC Facility 133 enabling Missile Defense System concurrent activity support. 134

Standards: 136

8.3.1.1 Execute a Digital Systems Engineering program that demonstrates consistent SE 137 process development, implementation, and repeatable performance that is in alignment 138 with the MDA/MDIOC SEP and MIOES SEMP. 139

8.3.1.2 Administer the MDIOC Engineering Review Board. Ensure proper artifacts 140 required by the applicable gate are submitted and adjudicate all milestone artifacts for 141 completeness and accuracy. Ensure all participating parties adhere to ERB governance. 142

8.3.1.3 Identify all ERB process anomalies and cooperate with MA to conduct an incident 143 investigation. Capture process escapes and deficiencies found in designs after ERB 144 implementation approval into the contractor’s corrective action program to allow for 145 trending and the capture of lessons learned. Report all ERB process escapes to the 146 government at regular intervals determined by the COTR. 147

8.3.1.4 Maintain the MDIOC Facility Technical Baseline. 148

8.3.1.5 Demonstrate the incorporation of standardized Digital Engineering/Model-Based 149 Systems Engineering (DE/MBSE) principles that are in alignment with MDA DE/MBSE 150 initiatives, shifting the focus from traditional methods and document-based deliverables 151 and artifacts to a model-centric perspective, where SE activities are performed by 152 leveraging digital artifacts and models. 153

8.3.1.6 Incorporate the requirements of the MIOES SEMP into all task order (TO) 154 planning and execution processes. 155

8.3.1.7 Populate and maintain a digital Requirements Baseline that includes: 156

8.3.1.7.1 Capturing, populating, and maintaining requirements and documenting 157 them IAW the MDIOC SEP, the MDIOC Technical Baseline Standard, and the 158

MIOES SEMP. 159

8.3.1.7.2 Populating a Requirements Traceability Matrix (RTM) with 160 requirements from contractual documentation, including: (a) Performance Work 161 Statements, (b) Mission Specific Taskings, (c) Technical Direction Letters 162 (TDLs), and (d) any other contract vehicles with customer needs or requirements. 163

8.3.1.7.3 Conforming RTMs per the MDIOC SEP, MDIOC Technical Baseline 164 Standards, and MIOES SEMP. The resulting artifacts shall be added to a 165 configuration-managed Authoritative Data Source (ADS) upon approval from a 166 respective review board (e.g., MDIOC ERB). 167

8.3.1.7.4 Documenting customer needs and annotating ownership, where 168 required, in the Requirements Baseline. 169

8.3.1.8 Populate and maintain a digital Architectural Baseline, IAW the 170 respective MDA mission requirements, the MDIOC SEP, the MDIOC Technical 171 Baseline Standard, and the MIOES SEMP that includes: 172

8.3.1.8.1 Capturing, populating, and maintaining Reference Architectures (RAs) by 173 gathering components used in existing designs. Adding the components to the System 174 Specification after approval by the appropriate review board (e.g., MDIOC ERB) to 175 ensure compliance. 176

8.3.1.8.2 Conforming design documents per the MDIOC SEP, MDIOC Technical 177 Baseline Standards, and MIOES SEMP. Adding the resulting artifacts to a 178 configuration-managed ADS upon approval from a respective review board 179 (e.g., MDIOC ERB). 180

8.3.1.8.3 Generating the service description artifacts required per the MDIOC SEP 181 and MIOES SEMP. Adding the resulting artifacts to a configuration-managed ADS 182 upon approval from a respective review board (e.g., MDIOC ERB). 183

8.3.1.9 Populate and maintain a digital Engineering Baseline, IAW MDA 184 mission requirements, MDIOC SEP, MDIOC Technical Baseline Standard, and 185 MIOES SEMP that includes: 186

8.3.1.9.1 Capturing, populating, and maintaining the assets, the as-built 187 assemblies, and the as-built services in compliance with the MDIOC SEP, 188 MDIOC Technical Baseline Standards, and MIOES SEMP. 189

8.3.1.9.2 Conforming existing as-built drawings per the MDIOC SEP, MDIOC 190 Technical Baseline Standards, and MIOES SEMP. Adding the resulting artifacts 191 to a configuration-managed ADS upon approval from a respective review board 192 (e.g., MDIOC ERB). 193

8.3.1.9.3 Populating the service catalog with approved available services and 194 their associated attributes (i.e., cost, service level agreements, etc.), as 195 applicable. 196

8.3.1.9.4 Documenting the as-built environment to populate the assets in a 197 configuration managed ADS. 198

8.3.1.10 Demonstrate a process engineering capability to ensure MIOES processes are 199 repeatable, effective, and efficient. Implement and enforce processes to efficiently 200 review and approve deviations from standard SE processes prior to execution to ensure 201 the deviations do not add unmitigated risk to the task or the enterprise as a whole, 202 allowing process tailoring to specific requirements as necessary. Report any deviations 203 to the government prior to implementation via a dashboard. 204

8.3.1.11 Identify and report on current and changing requirements of the MDA SE 205 process, including Agency- level directives, unique process interfaces, tools, and 206 implement best practices to understand all requirements early in the implementation 207 process. 208

8.3.1.12 Deliver and enforce a MIOES Systems Engineering Handbook that is aligned 209 with the published MDA/MDIOC SEP and the MIOES SEMP. The handbook should 210 target both experienced and new systems engineers in explaining the proper execution of 211 and the rationale behind the MIOES implementation of SE processes across the contract. 212

(DAL) 213

8.3.1.13 Demonstrate a DE/MBSE capability across the task order. 214

8.3.1.14 Develop, sustain, train, and enforce SE processes that are in alignment with the 215 MIOES SEMP and the MDA/MDIOC SEP. 216

8.3.1.15 Deliver and enforce a MIOES Systems Engineering Management Plan (CDRL 217 A005). 218

8.3.1.16 Develop, enforce, and conduct training covering actions needed to 219 develop/maintain the MDIOC Technical Baseline. 220

8.3.2 Reliability, Availability, and Maintainability (RAM) Engineering. The contractor shall 222 provide Reliability, Availability, and Maintainability (RAM) engineering via continuous 223 engineering services that optimize MDIOC facility and system RAM in a manner that is cost-224 effective and that meets existing and/or changing mission requirements. 225

Standards: 226

8.3.2.1 Maintenance Engineering- Demonstrate the following maintenance engineering 227 criteria during new system design or modifications to system design. 228

8.3.2.1.1 Minimization of custom equipment 229

Commonality and interchangeability of equipment 230

8.3.2.1.2 Access for performing critical maintenance 231

8.3.2.1.3 Recognition of failure modes 232

8.3.2.1.4 Proactive Preventative Maintenance (PM) and Predictive Maintenance 233 (PdM) research and understanding of warranties 234

8.3.2.2 Perform maintenance engineering on all MDIOC infrastructure items to include, 235 but not limited to: 236

8.3.2.2.1 Plumbing system, including potable water, waste water, HVAC piping, 237 natural gas piping, and steam/chilled water systems 238

8.3.2.2.2 Electrical Power Distribution System, including the 12,470 VAC 239 switchgear, Uninterruptable Power Supply (UPS), UPS substations, power 240 distribution systems, remote power panels, area lighting and emergency lighting, 241 and ground/lightning protection 242

8.3.2.2.3 HVAC systems 243

8.3.2.2.4 Fire suppression/detection systems 244

8.3.2.2.5 Roof systems 245

8.3.2.2.6 Elevator systems 246

8.3.2.2.7 Facility equipment (i.e., drinking fountains, cafeteria equipment, gym 247 equipment, government furnished appliances, and clocks) 248

8.3.2.2.8 Life safety systems 249

8.3.2.2.9 Visible architectural systems 250

8.3.2.3 Utilize equipment reliability checklists to ensure maintenance and operational 251 considerations are incorporated into system designs. The activities performed as part of 252 the Equipment Reliability Checklist include the following. 253

8.3.2.3.1 Acquiring, storing, and documenting (routine/critical) spares and other 254 unique materials, such as photos, manuals, and drawings in Maximo 255

8.3.2.3.2 Updating configuration status 256

8.3.2.3.3 Developing a supply chain map and list of authorized suppliers (critical 257 systems) 258

8.3.2.3.4 Updating the AMP to account for the additional systems 259

8.3.2.3.5 Updating System Description Documents 260

8.3.2.3.6 Adding the new or modified systems to the configuration hierarchy in 261 Maximo and populating the data fields 262

8.3.2.3.7 Transferring, documenting, and inventorying all unclassified system 263 documentation is transferred to and properly documented and inventoried in 264 Maximo 265

8.3.2.3.8 Performing maintenance training, including exercising diagnostic tools 266 and procedures 267

8.3.2.4 Failure Modes, Effects, and Criticality Analysis (FMECA). Identify and update 268 any changes to the FMECA/RAM study (CDRL A006), which is provided by the 269 government that stem from Corrective Maintenance/Preventive Maintenance actions and 270 facility improvement tasks. FMECAs are warranted based on any change to factors such 271 as criticality, mission dependency, cost to repair or replace, lead time to repair, and asset 272 performance. Ensure the design team receives the most current FMECA reports prior to 273 design completion. 274

8.4 Mission Assurance 275

8.4.1 Mission Sustainment 276

The contractor shall provide mission assurance for concurrent operations of systems and 277 services, to include event and resource de-confliction and mission/event asset protection, IAW 278 the MDIOC Mission Assurance Plan. The contractor shall develop and implement mission 279 assurance processes across the MIOES contract. 280

Standards: 282

8.4.1.1 Demonstrate a Mission Assurance (MA) program that ensures protection of mission 283 operational, test, and shared infrastructure resources on a daily basis 284

8.4.1.2 Demonstrate a capability that monitors the MA program health and status and 285 evaluates the program for effective mission assurance of MDA assets. 286

8.4.1.3 Deliver a MIOES Mission Assurance (MA) Plan defining the approach in 287 implementing mission assurance. The MA Plan will address the synchronization of 288 physical security, cybersecurity, and risk management programs IAW the MDA’s MA 289 construct. (CDRL A007) 290

8.4.1.4 Coordinate with the applicable MDA organizations for assets identified on the 291 Mission Assurance Asset List (MAAL) and any Prioritized Asset List (PAL) to apply seals 292 (physical and logical) and access restrictions to communicate and prevent unapproved 293 access or changes to establish event configuration protections for operations and test 294 resources. 295

8.4.1.5 Establish government-approved MA performance indicators, perform baseline-296 monitoring activities, and report to the COTR/ACOTR monthly on the performance 297 indicators, to include health and status of the MA program. 298

8.4.1.6 Provide Schriever Space Force Base and internal MDIOC facility project updates to 299 the MDIOC Range Integrated Schedule (MRIS) production team. Ensure Event Protection 300 Period (EPP) schedules are shown on the MRIS, as well as other available test schedules, 301 base projects, and pertinent information. 302

8.4.1.7 Report all MDIOC-impacting, real world, and event MA information to a 303 common location (e.g., MA dashboard) to enable shared and reliable situational 304 awareness with 24 hours of that information being released. 305

8.4.1.8 Participate in final planning/documentation reviews to ensure event 306 readiness for all MDA test events supported at or through the MDIOC. 307

8.4.1.9 Report incidents IAW the MDIOC Incident Notification Procedure, as required for 308 investigative activities. Deliver MDIOC Incident Notification Reports (CDRL A008). 309

8.4.1.10 Coordinate planned and emergent outages, incidents, issues, and concerns with 310 MDIOC mission partners to ensure a full understanding of how their missions are impacted 311 and to ensure there is clear communication to the customer of ongoing activities to restore 312 normal conditions. Identify and implement mitigation strategies. 313

8.4.1.11 Attend the SSFB meetings like the Mission Protection Working Group and 314 Mission Protection Board and maintain awareness for all current and proposed work as it 315 relates to mission and ongoing or upcoming concurrent activities and events and report any 316 upcoming anticipated impacts to the affected TO COTRs and ACOTRs. 317

8.4.1.12 Manage the MDIOC Utility Outage Board and maintain awareness for all current 318 and proposed work as it relates to mission and ongoing or upcoming concurrent activities 319 and events, and report any anticipated impacts to the affected TO COTRs and ACOTRs. 320

8.4.1.13 Perform planning and coordination to enable de-confliction of competing events, 321 integrated scheduling, event synchronization, and mission assurance. 322

8.4.1.14 Review Functional Configuration Audit and Physical Configuration Audit 323 (FCA/PCA) outputs provided by the CM section to assist in identifying overall 324 programmatic, event, and mission risks following the FCA/PCA. Ensure identified risks are 325 documented, reported, and adjudicated appropriately through the Risk Management 326 Program. 327

8.4.1.15 Deliver and enforce a MIOES Mission Assurance Handbook (DAL) that is aligned 328 with the published MDIOC MA Plan and the MIOES MA Plan. The Handbook shall be 329 aimed at helping MIOES contractors in the proper execution of and in understanding the 330 rationale behind the MIOES implementation of the MA processes across the contract. 331

8.4.1.16 Provide a Priority Asset List (PAL) IAW the MDIOC Facility MA Plan to allow 332 for protection of MDIOC physical assets when required by an event support plan and align 333 with the Mission Assurance Asset List (MAAL) to ensure affected Mission Essential 334 Functions (MEFs) can be identified during proposed equipment maintenance windows, or 335 conversely that individual equipment can be identified for mission protection based on a 336 real world operational need requiring MDIOC capabilities. 337

8.4.1.17 Develop and execute a proactive mission protection function for the MDIOC and 338 ensure Lessons Learned are captured, compiled, documented and delivered to the 339 government. 340

8.4.1.18 Document the MA processes that are based on the contractor’s SE model, as 341 directed through the MDIOC Facility SEP and the MIOES Program SEMP, to ensure 342 integrated and repeatable execution of MA functions. 343

8.4.1.19 Integrate all MA processes without creating or duplicating multiple architectures 344 (e.g. processes, tools, working groups, boards). 345

8.4.1.20 Facilitate government review and approval of work during Event Protection 346 Periods (EPP) to prevent adverse impacts to event execution from occurring at the 347

MDIOC. 348

8.4.1.21 Participate in Work Screening Team (WST) activities during EPPs to review and 349 understand physical work taking place at the MDIOC to prevent mission and event 350 impacts from occurring. 351

8.4.1.22 Ensure physical work is not performed at the MDIOC during EPPs without WST 352 approval. Work listed on the government approved Daily Maintenance List (DML) for 353 physical work at the MDIOC (MDIOC DML) may be performed without WST approval if 354 the workers have reasonable confidence the work will not have adverse mission or event 355 impacts. 356

8.4.1.23 Ensure application and removal of seals (physical and logical) for assets as part of 357 approved MAAL and PALs. 358

8.4.1.24 Submit changes to the MDIOC DML as required. 359

8.4.2 Risk Management 361

The contractor shall provide and administer a comprehensive Risk Management program. 363

Standards: 365

8.4.2.1 Demonstrate and administer a Risk Program that provides the government with 366 insight to mission execution and performance risk. 367

8.4.2.2 Develop and implement a MIOES RM Handbook that identifies, analyzes, plans, 368 assesses, monitors, manages and controls risks throughout a product/project life cycle 369 until the risk is either removed or accepted by the government. (DAL) 370

8.4.2.3 Manage and administer a Risk Review Board (RRB) that encompasses MDIOC 371 and MIOES organization risks and provide the presentation as a DAL. 372

8.4.2.4 Demonstrate a process to identify, analyze, plan, track, and control risks throughout 373 a product life cycle. Identify, manage, coordinate, document, and track risks, and risk 374 mitigation steps until the risk is either resolved or accepted by the government. 375

8.4.2.5 Provide the most current risk status to MDA customers on a real time basis (e.g., 376 dashboard). Provide risk reporting in MDA standard formats for individual and 377 program/activity risk summaries. 378

8.4.2.6 Perform continuous monitoring of all management system processes to identify 379 gaps or inconsistencies in the application of the risk program and ensure a common 380 approach to risk management across the MIOES contract. 381

8.4.2.7 Perform continuous monitoring of all management system processes to identify 382 gaps or inconsistencies in the application of the RM program and apply a common 383 approach to RM across the contract. 384

8.4.2.8 Develop and manage a monthly MIOES level forum to report risk summaries to 385 the government in MDA standard formats for MIOES program activities. Report MDIOC 386 level risk summaries to the government. 387

8.4.3 Facility Sustainment 390

The contractor shall develop MDIOC System Description Documentation and a MDIOC 391 Facility Sustainment Plan. 392

Standards: 393

8.4.3.1 Inspect existing equipment, drawings, and specifications for currently installed 394

MDIOC critical, non-critical, and facility systems. 395

8.4.3.2 Develop, maintain, deliver discrete system descriptions for each facility system, 396 documenting fully all known functions for the system, including the criticality of each 397 function. (CDRL A009) 398

8.4.3.3 Physically inspect and review existing drawings, and review existing 399 specification for all MDIOC infrastructure systems. 400

8.4.3.4 Maintain system information in an authoritative data source that supports 401 MDIOC technical baseline integrity. 402

8.4.3.5 Develop and deliver a MDIOC Facility Sustainment Plan (FSP) which provides 403 comprehensive documentation on the state of MDIOC facility infrastructure and provides 404 an executable replacement strategy based on a government approved ranking schema. 405

(CDRL A010) 406

8.5 Configuration Management 409

The contractor shall develop and implement a MIOES Configuration Management program 411 that ensures implementation, execution, and enforcement IAW the MDIOC Configuration 412 Management Plan. The contractor shall develop and implement configuration management 413 processes across the MIOES contract. 414

Standards: 416

8.5.1 Develop, deliver, implement and enforce a MIOES Configuration Management Plan 417 (CMP) that incorporates the five CM functions as identified in EIA-649C, with provisions 418 for digital data configuration management (CDRL). 419

8.5.2 Enforce compliance with CM processes, which are performed IAW the MIOES 420 CMP, the MDIOC Facility CMP, and MDA Manual 3500.1. 421

8.5.3 Implement all the requirements of the MDA/MDIOC CM process, including 422 Agency-level CM directives, unique process interfaces, tools, and best practices to 423 ensure integration within the MDIOC Facility. 424

8.5.4 Document and classify all engineering change requests as Class I or II for 425 consideration by the appropriate change authority. Demonstrate a consistent method 426 of identifying, controlling, and providing status of configurations across the MDIOC 427 Facility that supports the unique objectives of MDA missions. 428

8.5.5 Obtain approval by the appropriate MDA/MDIOC board (e.g., MDIOC 429 Engineering Review Board), per MDA Manual 3500.1-M, for all Class I changes that 430 affect the form, fit, or function of a baseline configuration and have the potential to 431 increase risk, decrease performance, or impact a mission-critical system. 432

8.5.6 Establish and administer a Configuration Control Board (CCB) to manage 433 configuration items and all Class I and II changes. Use a configuration/change 434 management process IAW the MDA/MDIOC CMP, MIOES CMP, to account for, 435 manage, and protect the integrity of configured items and to ensure that only authorized 436 components are used and only authorized configuration changes are made. Maintain the 437 MDIOC Facility baseline drawings. 438

8.5.7 Identify and maintain a roles-based Configuration Status and Accounting (CSA) 439 system that is accessible by authorized MDIOC government, contractor, and mission 440 partner personnel. 441

8.5.8 Report and capture in the CSA system, for CM-controlled baselines and 442 Configuration Items, information such as the following: 443

• Configuration status 444

• Configuration management documentation 445

• Current and historic baselines 446

• Change requests 447

• Change notices 448

• Maintenance actions 449

• Warranty data and history 450

• End of Life / End of Support 451

• Software documentation (if applicable) 452

• Access lists of the TO CSA databases 453

• Non-conformances 454

8.5.9 Provide the configuration history, traceability, and status of any change, waiver or 456 deviation requests, effectivity and status of approved changes, and the schedules and status 457 of configuration audits and corrective actions in CSA databases. 458

8.5.10 Organize, lead, document, and report system development internal Functional 459 Configuration Audits (FCAs) and Physical Configuration Audits (PCAs) to verify that the 460 actual performance of the CI meets the specification requirements, and to verify that the 461 related design documentation matches the design of the CI. Utilize a consistent method of 462 identifying, controlling, and providing status of configurations. 463

8.5.11 Demonstrate a program that monitors the CM program health and status and 464 evaluates the program for effective configuration control of MDA assets. Analyze and 465 report the current state of the MIOES configuration and configuration/change control 466 environment through standard monthly reporting (e.g., Status Report and Metric 467 Dashboards). 468

8.5.12 Maintain integrated, non-proprietary CM dashboard views to provide a truly 469 enterprise CM view for decision makers. 470

8.5.13 Demonstrate CM through the MDIOC ERB to protect the MDIOC Technical 471 Baseline and conduct and report CM audits. 472

8.5.14 Review, process, and validate the accuracy of change requests as part of the 473

MDIOC ERB and CCB. Support updates to changes in the MDIOC Technical Baseline 474 as part of the MDIOC ERB and CCB. 475

8.5.15 Place Technical Baseline artifacts related to changes approved by the MDIOC 476 ERB into an authoritative data repository, to include controlling who can view, edit or 477 update artifacts IAW MDA/MDIOC change procedures. 478

8.5.16 Establish government-approved CM performance indicators. Perform baseline-479 monitoring activities, and report to the COTR/ACOTR monthly on the performance 480 indicators, to include health and status of the CM program: 481

• Report process anomalies to MA/QA 482

• The number of unauthorized MDIOC Technical Baseline changes across MDIOC-483 designated authoritative data sources 484

• The number of errors found in the MDIOC-designated authoritative data sources 485 during a QA audit of CM controlled items 486

• Changes to the MDIOC TB processed during the month by type of change and 487 current backlog, with time in backlog 488

8.5.17 Ensure CM reviews, processes, change request validations and baseline updates that 489 occur in the task orders follow the overall guidance, principles, and best practices defined 490 in guidance ANSI/EIA-649C. 491

8.6 Quality Management 493

The contractor shall develop and maintain a comprehensive Quality Management program 495 for the systematic monitoring and evaluation of MIOES provided systems/services to ensure 496 that provisioned systems and services are ready and available to support the MDIOC and 497 concurrent activities and events. The contractor shall develop and implement quality 498 management processes across the MIOES contract. 499

Standards: 500

8.6.1 Demonstrate a MIOES quality engineering function to identify opportunities for 501 reducing costs and increasing efficiency, investigate the root causes of problems and 502 develop and implement corrective and preventative measures, design and implement 503 quality tests, develop documentation and test procedures, track quality standards, and 504 specify test result requirements. 505

8.6.2 Develop and enforce a MIOES Quality Management Plan. The contractor’s 507 Quality Management Program shall achieve and demonstrate compliance with the 508 applicable SAE AS9100D requirements by the end of CY1. The Quality 509 Management Program shall assist MA in conducting investigations across the 510 contract. (CDRL A012) 511

8.6.3 Demonstrate a MIOES quality assurance function to verify design, development, and 513 implementation of products and services to standards and customer requirements. Adhere 514 to quality objectives that have been developed in consultation with relevant stakeholders, 515 reviewed for relevance, and monitor standards through Key Performance Indicators (KPIs). 516

8.6.4 Demonstrate a MIOES quality control function to ensure that products and services 517 adhere to defined quality criteria, meet requirements, and are delivered IAW approved 518 changes (e.g., ERB) and to identify and report defects to the customer before they cause 519 mission impacts. 520

8.6.5 Demonstrate a comprehensive and effective Corrective Action Program across the 521 MIOES contract. 522

8.6.6 Measure, verify, and validate mission success through a collection of data and 523 metrics IAW the MDIOC Facility QM Plan. 524

8.6.7 Provide a comprehensive quality audit plan for MIOES systems/services and 525 rationale for targeted audits. Perform the associated audits to assess the current state of 526 MIOES provided systems/services, and provide a written report to the government 527 monthly (provided as a DAL). 528

8.6.8 Determine the appropriate frequency and breadth of quality audits to ensure 529 continuous confidence in the configuration items and baselines. Report the frequency and 530 breadth of quality audits to the COTR and ACOTR in the Quality Assurance (QA) Audit 531 Plan (provided as a DAL) annually and provide a QA Monthly Audit Report. Verify 532 documented and as-built configurations match, ensuring the current technical baseline is 533 available for all systems and events. 534

8.6.9 Demonstrate a quality program inclusive of quality engineering, quality assurance, 535 and quality control functions IAW the MDIOC Facility QM Plan. 536

• Demonstrate a 100% audit of Mission Assurance Asset List (MAAL) assets. 537

• Resolve findings against MAAL components before event PAL and other routine 538 work. 539

• Report MAAL findings to the government Mission Assurance Officer and COTR 540 in the monthly QA report. 541

• Demonstrate a 100% audit of event PAL assets prior to event dry runs starting. 542

• Resolve findings against event PAL components before other routine work. 543

• Report completion and findings in writing to the government Mission Assurance 544 Officer and COTR prior to event dry runs beginning. 545

• Monitor sealed assets from approved MAAL/PALs. 546

• Participate in FCAs/PCAs by conducting verification and document inspections. 547

8.6.10 Establish, report on, and maintain a quality management function that investigates 548 the root causes of problems and develop and implement corrective and preventative 549 measures, design quality tests, develop and implement documentation and test procedures, 550 track quality standards, and specify test result requirements. 551

8.6.11 Verify and validate the design, development, and implementation of products and 552 services to standards and customer requirements and adherence to quality objectives that 553 have been developed in consultation with relevant stakeholders, reviewed for relevance, 554 and monitored outcomes through key performance indicators. 555

8.7 Enterprise Architecture 557

The contractor shall demonstrate an Enterprise Assurance program that provides 558 facility/contract-wide technical baseline standards and governance (governance includes how 559 the contractor supports its mission partners in capturing and maintaining requirements, 560 architectures, and engineering baselines), as well as provides signature ready recommendations 561 for policy adjustments and government decision making in support of MDIOC and MDA 562 events. 563

Standards: 565

8.7.1 Develop, maintain, and deliver enterprise designs, standards, and technologies using a 566 standards based approach that aligns with and adheres to Federal, DoD, and MDA regulations 567 and policies. 568

8.7.2 Provide and implement EA practices that establish and sustain a MDIOC/MIOES 569 contract-wide engineering organizational construct that: 570

• Creates and applies consistent engineering standards. 571

• Ensures requirements are tracked, assigned, and aligned IAW requirements baseline 572 standards. 573

• Ensures products and services are defined with architectures and assigned technical 574 ownership IAW architectural baseline standards. 575

• Ensures assets are tracked with technical ownership IAW engineering baseline 576 standards. 577

8.7.3 Develop, maintain, enforce, and demonstrate contract-wide technical baseline standards 578 consistent with the MDA/MDIOC SEP and MIOES SEMP. Standards shall address each of 579 the component baselines and be delivered as DALs: 580

• Requirements Baseline 581

• Architectural Baseline 582

• Engineering Baseline 583

8.7.4 Mature technical baseline artifacts and provide overall enterprise oversight to contract 584 engineers, developers, project/systems engineers, solution architects, etc. 585

8.7.5 Establish, maintain, and enforce the technical baseline repository standards for 586 historical artifacts, the provenance of those artifacts, and supporting data to include 587 deliverables and artifacts created for and shared with MDA stakeholders. 588

8.7.6 Demonstrate EA expertise in support of MIOES contract-wide activities that develop, 589 maintain, and deliver enterprise designs, standards, and technologies using a standards based 590 approach that aligns with and adheres to Federal, DoD, and MDA regulations and policies. 591

8.7.7 Develop hardware and software engineering standards, publish as contract engineering 592 standards, and enforce compliance across the MIOES contract. 593

8.7.8 Lead the development, implementation, and management of a contract wide Digital 594 Engineering and Model-Based Systems Engineering program. 595

8.7.9 Using a standards based approach (for example: Federal, DoD, and Joint Information 596 Environment (JIE) guidance), develop, maintain, and deliver for government approval 597 enterprise designs, standards and technology strategies to govern MIOES business processes. 598

8.7.10 Provide EA expertise that supplies the government: 599

• Technical baseline management and process documentation in support of systems 600 engineering activities for consistent governance of the MDIOC Technical Baseline 601 Process and system engineering principals and standards documentation for consistent 602 governance. 603

• Expertise in the development and sustainment of the MDIOC ERB standards and 604 processes in order to maintain the MDIOC Technical Baseline. 605

• Recommendations/artifacts for timely decisions and actions that govern the MDIOC 606 Facility. 607

• A MDIOC facility roadmap to assist with technical and budgetary planning. 608

8.7.11 Identify process improvement opportunities to develop and implement solutions. 609

8.7.12 Provide “thought leadership” for MDIOC facility operations using government strategic 610 objectives and priorities. 611

8.7.13 Enforce standardized enterprise architecture (EA) principles, processes, and operations 612 across the contract. 613

8.8 Situational Awareness 614

The contractor shall provide a capability that provides a common operating picture to promote 615 collaboration and coordination, while facilitating integration of events and maintenance 616 activities within and affecting the MDIOC. 617

Standards: 619

8.8.1 Deliver a time-phased MDIOC Range Integrated Schedule (MRIS) to provide 621 unclassified shared situational awareness of ongoing missile defense and MDIOC 622 activities, views ranging from comprehensive (e.g., campaign length) to detailed (e.g., 623 hourly), and unambiguous insight into level of impact predicated on event scope. 624

8.8.2 Develop and maintain a list of all applicable and relevant MRIS data providers and 625 end-users, along with a battle rhythm for MRIS data input that keeps data relevant. 626

8.8.3 Provide event and event-related data, with tailorable and sufficient level of detail, to 627 provide decision makers the information they need to coordinate and make operational 628 decisions. 629

8.8.4 Incorporate external activities allowing expanded prioritization of effort, de-630 confliction of assets, and resource planning, based on access to and fidelity of non-MIOES 631 data sources 632

8.8.5 Perform the gap analysis required to (a) ascertain the correct data and data level to 633 be ingested and (b) avoid duplication of effort done on other TOs. Capture potential 634 improvements. Develop and document MRIS processes and training and deliver training 635 for stakeholders as required to ensure effective and efficient implementation of processes. 636

8.8.6 Perform review of documented standards and trainings, at a minimum but not 637 limited to, once every two years to ensure the MRIS is current with workflow, procedures, 638 and references. Utilize continuous development efforts to analyze software and 639 technology to improve the MRIS IAW the MRIS Guide. 640

8.8.7 Provide supplemental content over the classified network as necessary to fulfill the 641 requirements of this objective and associated outcomes. 642

8.8.8 Utilize government approved Plan of Action and Milestones, and Responsible, 643 Accountable, Coordinated, informed (RACI) matrices to capture project status and 644 responsibilities. 645

8.8.9 Enforce standardized situational awareness (SA) principles, processes, and 646 operations across the contract. 647

8.8.10 Ensure all task orders follow contract level situational awareness governance and 648 demonstrate adherence to and participation in contract level situational awareness 649 activities. 650

8.8.11 Demonstrate a capability that provides a common operating picture to promote 651 collaboration and coordination, while facilitating integration of MIOES supported events 652 and maintenance activities within and affecting the MDIOC. 653

8.8.12 Develop and adopt government approved templates for Plan of Action and 654 Milestones, Responsible, Accountable, Coordinated, Informed (RACI) matrices, and 655 project schedules. Incorporate these tools into daily task order operations to support 656 communications, integration, and transparency. 657