Attch2_Exh_M_MDIOC ERB Charter.pdf

MISSILE DEFENSE AGENCY

Missile Defense Integration and Operations Center Engineering Review Board Charter

Version 1.0

02 July 2021

MDIOC Engineering Review Board Charter

A. PURPOSE: This charter establishes the Missile Defense Integration and Operation Center (MDIOC) Engineering Review Board (ERB) and sets forth its functions, membership, and reviews.

The MDIOC ERB is the forum for review of projects impacting the MDIOC facility. The MDIOC ERB provides reviews to ensure requests are validated, align with facility standards, and solutions are integrated across the MDIOC facility.

B. APPLICABILITY: Missile Defense Agency (MDA) Director MDIOC (MDA/DM) and MDA Mission Support Facility Operations (MDA/MSF) are responsible to the MDA Director for the overall development and integration of MDIOC resources. MDA Programs, non-MDA government organizations, and contractors performing work affecting MDIOC architecture, systems, facilities baseline, or space utilization must be approved by the MDIOC ERB.

The facility control activities of the MDIOC ERB do not duplicate or fall within the scope of MDA Directive 5000.05 Single Technical Authority, MDA Instruction 5000.20 Engineering Technical Review Process, and the MDA Systems Engineering Plan because the facility work covered by the MDIOC ERB process does not change or control any Element or Component of the Missile Defense System (MDS) as defined in those three documents.

C. MDIOC ERB ENTRANCE CRITERIA: The MDIOC ERB will review all projects that meet any of the following criteria:

1. Efforts that require an MDA Form 80 within the MDIOC and an installation or modification effort that would affect any aspect of the MDIOC architecture, systems, or facilities baselines.

2. Any installation or modification effort that would affect any aspect of the MDIOC architecture, systems, or facilities baselines. 2-Letter space allocation falls within this criteria.

D. ORGANIZATION

1. Membership: MDIOC ERB membership is comprised of a chair and board members.

a. Board Chair: The MDIOC ERB Chair is the MDIOC Deputy Director, who may delegate Chair responsibilities to the MDIOC Chief Engineer.

b. Board Members: Serve as the working-level government core of the MDIOC ERB.

Membership is composed of the government representatives from MDA Office of the CIO (MDA/IC), DM, MSF, and the customer government lead for the project/effort. The chair makes the final decision when the board members cannot reach a consensus agreement. Board members include government representatives from:

i. MDA MDIOC Director (DM) Chief Engineer

ii. MDA/DM members

iii. MDA Network Operations (ICN) members

iv. MDA Information Technology Services (ICS) members

v. MDA MSF members assigned to the MDIOC

vi. MDA IC Architecture & Engineering (ICE) members

vii. The customer government lead for the project/effort

2. Chair Responsibilities: DM is responsible for ensuring the MDIOC successfully provides a mission platform to support the MDS via concurrent test, training, and operations activities. The Chair is responsible for providing final approval of MDIOC ERB projects before they progress to the design and to the implementation stages (full maturity Systems Design Reviews (SDR) and Implementation Readiness Reviews (IRR)). The Chair may determine if in-person meetings are needed for particular reviews. The Chair will request other MDIOC government tenants, as required, be included in a particular review.

3. DM Chief Engineer Responsibilities: The Chief Engineer is responsible for providing final approval of MDIOC ERB artifacts and may determine if in-person meetings are needed for particular reviews. The Chief Engineer will request other MDIOC government tenants, as required, be included in a particular review. The chair approves all architectural baseline artifact standards.

4. ERB Member Responsibilities: Each board member is responsible for vetting the technical aspects of each review that applies to their specific organization. All board members are empowered to comment on each MDIOC ERB review with questions, statements or suggestions.

5. MDIOC ERB Secretariat: The Secretariat performs an initial check for accuracy and completeness on all MDIOC ERB review requests. The Secretariat acts on the direction of the MDIOC ERB Chair and DM Chief Engineer. The Secretariat notifies the appropriate government and contractor reviewers their input is needed. The Secretariat also coordinates virtual reviews with all board participants, schedules in-person meetings if needed, and captures disposition and standards in a defined repository for MDIOC ERB artifacts. The Secretariat records formal actions from reviews and ensures requestors are notified of their actions.

6. Requestor Responsibilities: A Requestor represents the team responsible for completing an effort or project that meets the MDIOC ERB entrance criteria. A Requestor can be any government or contractor personnel with access to the MDA network. The Requestor will submit briefings and supporting documentation to the MDIOC ERB and must be familiar with the published instructions and standards that govern the MDIOC ERB. Once the secretariat has accepted the artifacts, the board members will be notified to provide their input and final concurrence. If at any time, the board determines artifacts need re-work, action items can be issued to the Requestor. It is the Requestor’s responsibility to reconcile these action items in their artifacts. The Requestor has the responsibility to include all classification markings on artifacts for appropriate handling. It is the Requestor’s responsibility to understand any changes to previously approved ERB requests which would affect the MDIOC baseline and to submit a new ERB request if the new changes meet the MDIOC ERB entrance criteria. Formats and examples to use for submission are posted at https://mko.mda.mil/sites/ires/sepi/CM/MDIOC_ERB/SitePages/Home.aspx. Questions on the process can be directed first to the ERB Secretariat at mdioc-erb-secretariat@mda.mil or to the MDIOC Chief Engineer at MDIOCChiefEngineer@mda.mil.

7. ERB Quorum: For a review to have a quorum, the 1) MDIOC ERB Chair or the Chief Engineer and

2) one other board member must participate. When a quorum is not met, the review is either suspended or cancelled. Review and approval for facility centric requests requires the participation of at mailto:mdioc-erb-secretariat@mda.mil mailto:MDIOCChiefEngineer@mda.mil least one MDA/MSF Board Member assigned to the MDIOC. Quorum requirements apply whether the review is held virtually or in person.

8. Non-Member SME Reviewer: Input from Subject Matter Experts (SMEs) will be collected on a regular basis for MDIOC ERB reviews. As non-voting contributors to ERB reviews, their comments and concerns are valued. If a SME reviewer does not have access to the MDA Network, their comments need to be submitted in text format so they can be archived with the rest of the review.

9. Customer Government Lead for Project/Effort: The government requirement owner for the effort or project will be included on all reviews which correspond to their requirements. They will be able to provide input as the project progresses through its lifecycle.

BOARD OPERATION

10. Gate Reviews: The MDIOC ERB has four Systems Engineering gate reviews; Systems

Requirements Review (SRR), System Design Review (SDR), Implementation Readiness Review (IRR), and Closeout.

a. A SRR validates the need and specific requirement for the proposed work and determines if interim design reviews (ex. 25%, 75% maturity) may be needed depending on complexity and customer need.

b. At least one SDR is performed to ensure the submitted 100% design meets the requirements and that government stakeholders are satisfied the design will meet their needs at implementation.

c. The IRR verifies that the completed design can be implemented and operated in the MDIOC facility by ensuring coordination and de-confliction with various stakeholders.

d. The Closeout reviews completed work and retroactive requests.

An ERB request review or a specific requirement may be waived by the ERB Chair at any point within the gate reviews due to variance of standards or demonstration of non-impact. Given the demonstration of sufficient evidence by the Requestor that the work will not affect the Operational Capacity of the MDIOC, further reviews may be waived, pre-approved, or delegated to contractor representatives. Any waived or pre- approved work has the expectation that baseline documentation is still updated. The only approved method to waive/delegate reviews is through an ERB waiver form signed by the ERB Chair or through being listed in ERB Charter Appendix F.

All MDIOC ERB review artifacts, drawing standards, and work instructions will be kept in a central repository for accessibility (https://mko.mda.mil/sites/ires/sepi/CM/MDIOC_ERB/SitePages/Home.aspx ). This repository acts as the central location for approved artifacts and therefore should be used in conjunction with data architectures defined by the Integrated Research and Development for Enterprise Solutions Configuration Management Plan.

11. Review Format: Typically artifacts under review by the MDIOC ERB can be approved through an automated workflow tool which allows for users to provide inputs as their schedules allow. This tooling, along with existing communications tools (email and Skype), allows for adjudication of the majority of the items reviewed. Requestors can submit complete artifacts for review at any time. An in-person meeting can be coordinated at the discretion of the MDIOC ERB Chair. Artifacts and comments from the reviews are documented and stored in the same manner regardless of virtual or in-person.

12. Action Items and Disposition: During the review, if re-work is needed, action items will be issued to the Requestor to make the needed changes. Requestors must be responsive to the action item by the due date or risk extending their approval timeline. Once artifacts are accepted, the disposition will be captured using the MDA Public Key Infrastructure CAC signature of the MDIOC ERB Chair or delegate.

13. Technical Conflicts: Technical conflicts, both within the engineering community and between the engineering and programmatic communities will be resolved at the lowest level. Technical issues may be resolved, following either the programmatic or technical chains of command, depending on the nature of the issue. If a technical issue cannot be resolved as part of the normal ERB review process, the issue may be appealed to the MDIOC Chief Engineer, then the MDIOC ERB Chair for further adjudication.

In the exceptional event of a technical issue not resolved at the MDIOC ERB, the first flag officer or SES in either the programmatic or technical chains of command may appeal to the Director MDIOC for a final determination.

E. AUTHORIZATION: This board is constituted under the authority of the Director MDIOC.

Changes to the ERB charter and appendixes are approved by the MDIOC Deputy Director.

F. EFFECTIVE DATE: This charter is effective upon approval by the MDIOC Deputy Director.

G. SUNSET CLAUSE: This charter will be reviewed every five years and rescinded when no longer needed.

APPROVED:

WALTER S. CHAI

Director of MDIOC

REFERENCES

1. MDA Directive 5000.05 Single Technical Authority, September 25, 2013.

2. MDA Instruction 5000.20 Engineering Technical Review Process, October 26, 2020.

3. MDA Systems Engineering Plan, July 17, 2018.

4. MDA Form 80.

5. Integrated Research and Development for Enterprise Solutions Configuration Management Plan