MCO 5230.20.pdf

DEPARTMENT OF THE NAVY

HEADQUARTERS UNITED STATES MARINE CORPS

3000 MARINE CORPS PENTAGON

WASHINGTON, DC 20350·3000

MCO 5230.20

C4 22 Aug 2011

MARINE CORPS ORDER 5230.20

From:

To, Subj, Ref:

Encl, Commandant of the Marine Corps Distribution List

MARINE CORPS ENTERPRISE ARCHITECTURE

(a) 40 U.S.C. 1401(3)

(b) Public Law 108-375

(c) OMB Circular A-130 Management of Federal Information Resources

(d) MCO 5400.52

(e) DOD Directive 7045.14, uThe Planning, Programming, and Budgeting

System (PPBS)," July 28, 1990

(f) DOD Directive 8000.1, "Management of the Department of Defense

Information Enterprise," February 10, 2009

(9) DOD Directive 8115.01, "Information Technology Portfolio

Management," October 10, 2005

(h) DOD Directive 4630.05, "Interoperability and Supportability of

Information Technology (IT) and National Security Systems (NSS) ," May 5, 2004

(i) DOD Instruction 4630.8, "Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS) ," June 30, 2004

(j) CJCSI 3170.01G, "Joint Capabilities Integration and Development System," March I, 2009

(k) CJCSI 6212.01E, "Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS) ," December 15, 2008

(1) Marine Corps Vision and Strategy 2025

(m) DOD Instruction 5000.02, "Operation of the Defense Acquisition

System," December 8, 2008

(n) SECNAVINST 5000.2D

(0) SECNAVINST 5000.36A

(p) SECNAV memo of 21 Nov 06, "Designation of DON Deputy Chief

Information Officers and Command Information Officers" (NOTAL)

(q) MARCORSYSCOM C4I Interoperability and Integration Management Plan

(C4I I&IMP) of 2 Sep 05

(r) MCO 5231.3

(s) USMC Enterprise Architecture Work Group (EAWG) Charter of

14 May 05 (NOTAL)

(t) MCO 5220.12

(u) SECNAV M-5210.1

(v) Marine Air Ground Task Force (MAGTF) Architecture Working Group

(MAWG) Charter of Dec 2010 (NOTAL)

(w) Charter for the Marine Corps Net-Centric Data Strategy Working

Group (NCDWG) of Jul 19, 2007 (NOTAL)

(1) Abbreviations

DISTRIBUTION STATEMENT A, Approved for public release; distribution is unlimited.

MCO 5230.20

22 Aug 2011

1. Situation. The Marine Corps requires a unifying framework for strategic planning, enterprise level decision making, and continuous process optimization to deliver improved organizational performance, effectiveness, and efficiency. This Order establishes roles, responsibilities, relationships, and architecture policy necessary to ensure that architectural design documentation and data is authoritative, standardized, and reusable across the enterprise. References (a) through (w) provide guidance and direction, and identify the responsibility for development of an Enterprise Architecture (EA). Both statutory and regulatory mandates have directed the Marine Corps to establish an integrated EA as stated in references (a) through (d).

2. Mission. To develop the integrated Marine Corps EA, all Marine Corps commands, organizations, and activities will develop, maintain, and use architectures in accordance with this Order.

3. Execution

a. Commander's Intent and Concept of Operations

(1) Commander's Intent

(a) The Marine Corps EA is a single, integrated architecture that encompasses all activities of the Marine Corps and supports key decision making processes within the Marine Corps.

(b) The purpose of the Marine Corps EA:

1. Support and enhance capability development using the Marine Corps as-is and to-be EA, depicting the Marine Corps activities and associated solutions, in the context of Marine Corps missions, planning scenarios, and concepts.

2. Provide information to the Marine Corps acquisition community for decisions via gap analysis, strategic planning, investment management, modernization, and transformation to enable solution developers to meet current and future operational needs.

~. Serve as the vehicle to align Marine Corps strategic planning with the current warfighting and business capability portfolio management activities of human capital planning, budget, acquisition, capital investments, and organizational structures. This alignment will support the Marine Corps mission, goals, objectives, and core competencies in accordance with references (e) through (0).

4. Support changes and enhancements to all aspects of Marine Corps Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, and Facilities (DOTMLPF), as directed by higher headquarters and in response to the Commandant's priorities and initiatives.

(2) Concept of Operations

(a) This Order establishes the governance, roles, ,and responsibilities for Marine Corps EA entities which develop and manage architectures. The governance structure is comprised of the Enterprise

Architecture Executive Steering Group (EAESG), the Enterprise Architecture Advisory Board (EAAB) , the Enterprise Architecture Working Group (EAWG), the

Marine Air Ground Task Force (MAGTF) Architecture Working Group (MAWG) ,. and the Net Centric Data Working Group (NCDWG).

(b) The Marine Corps EA governance bodies set the direction for development, compliance, and maintenance of the Marine Corps EA to fulfill its mission. These actions support decision making, provide integration with the Department of the Navy (DON) EA, and allow federation with Joint architectures and others as directed.

(3) Roles and Responsibilities. This Order applies to any Marine Corps entity developing the EA, segment architectures, solution architectures, mission thread architectures, or re-engineering processes/value streams. The Marine Corps Chief Information Officer (CIa) provides overall policy guidance for and oversight of all Marine Corps EA efforts per reference (d) and in accordance with the guidelines of reference (f). Marines Corps EA efforts include the following roles and responsibilities from organizations as designated in the Tasking section of this Order.

(a) Chief Architect

1..

of Marine Corps EA maintenance of the

Provide policy guidance and standards for, efforts to include governance, development, EA.

and oversight and

2. Certify that segment, solution, and mission thread architectures are aligned with and conform to the Marine Corps EA and to the Department of the Navy (DON) Enterprise Architecture (EA).

~. Integrate the capstone, segment, solution, and mission thread architectures to produce the Marine Corps EA.

4. Appoint a Chair for the EAAB.

5. Chair the EAESG and brief architecture status and issues to the CIa.

6. Advise the Marine Requirements Oversight Council (MROC), Deputy Commandants, and the CIa on architecture status and issues.

2. Coordinate with external partners such as the DON and other related Department of Defense (DoD) and Federal agencies, as well as state, local and foreign governments, and academia.

8. Fulfill DoD and Federal EA reporting requirements for the Marine Corps.

~. Advocate for appropriate resources to fulfill architecture responsibilities across the Marine Corps.

10. Ensure that appropriate configuration management is applied to the EA.

11. Lead development of, sustain, and provide the Marine Corps central" architecture repository.

12. Establish and maintain educational criteria and practical performance standards for Marine Corps EA certification.

(b) Chief Operational Architect

1. Advise the Deputy Commandant for Combat Development and Integration (CD&I) on operational architecture (OA) status and issues.

2. Develop the Marine Corps OA to include mission thread architectures.

3. Advise the Chief Architect on OA status to include coordination with external agencies.

4. Certify that OAs developed and maintained by the Marine Corps are compliant with Marine Corps, DON, DoD, and Federal policy on EA.

5. Participate in the EAAB and the EAWG.

~. Provide direction, management, oversight, governance, development, and use of OA efforts across all domains, functions and capability areas (e.g. Business Enterprise Architecture (BEA)).

2. Coordinate with external partners such as the DON and other related DoD and Federal agencies, as well as state, local and foreign governments, and academia on OA.

8. Ensure that appropriate configuration management is applied to all OA data and products.

(c) Chief Systems Architect

1. Advise the Commander, Marine Corps Systems Command (MARCORSYSCOM) and Program Executive Office (PEO) Land Systems on systems architecture (SA) and technical architecture status and issues.

2. Advise the Chief Architect on SA status to include coordination with external partners.

3. Develop the Marine Corps SA in accordance with reference

(q) .

!. Certify that systems and technical architectures developed and maintained by the Marine Corps are compliant with Marine Corps, DON, DoD, and Federal policy on EA.

~. Certify Information Support Plans (ISP) and Network Ready Compliance documents are developed in accordance with reference (k).

~. Provide direction, management, oversight, governance, development, and use of SA efforts across all domains, functions, and capability areas.

7. Participate in the EAAB and the EAWG.

8. Coordinate with external partners such as the DON and other related DoD and Federal agencies, as well as state, local and foreign governments, and academia on system engineering, SA, and interoperability issues.

9. Ensure that appropriate configuration management is applied to all SA data and products.

(d) Chief Business Architect

1. Advise the Chief Architect on Marine Corps BEA status and issues related to the MROC approved Core Value Streams (CVS) identified in reference (t).

2. Participate in the EAAB and the EAWG.

3. Integrate Marine Corps BEA practices with the Continuous Process Improvement methodologies outlined in reference (t), and ensure CVS architectures are integrated with the Marine Corps EA.

4. Coordinate with the Chief Operational Architect and the Chief Systems Architect on the development of integrated architecture products and processes within the business domain (e.g. CVS).

5. Coordinate with the DON, DoD, Deputy Chief Management Officer (DeMO), and Federal agencies on business architecture.

~. Ensure that appropriate configuration management is applied to all business architecture data and products.

(e) Chief Data Architect

!. Develop and direct policies, practices, processes, and guidance for enterprise data management, metrics, and strategy.

~. Prescribe Information Technology (IT) and National Security Systems (NSS) data exchange and information standards per reference

(0) .

3. Ensure compliance of Marine Corps data with Federal, DoD, and DON regulations and policies.

(f) Functional Area Managers (FAM)

1. Ensure required data from the functional area is provided to the EA.

2. Verify content and accuracy of rendered architecture data and coordinate with the EAWG and the MAWG as appropriate.

3. Advise the Chief Architect on segment architectures related to the functional area.

4. Take direction from the EAWG and participate as needed for coordination of architecture development.

~. Comply with EA directives with respect to the development of architecture products by the FAM and within the respective functional portfolio.

(4) Goyernance. Governance of the Marines Corps EA is performed by the following bodies with their relationships shown in Figure 1.

(a) Enterprise Architecture - Executive Steering Group (EAESG).

The EAESG is chaired by the Chief Architect and comprised of general officer/Senior Executive Service (GO/SES) members from Command, Control, Computers, and Communications Department (C4) ; MARCORSYSCOM, CD&I, Marine Corps Business Enterprise Office (MCBEO), Manpower and Reserve Affairs Department (M&RA) i Plans, Policies, and Operations Department (PP&O), Aviation Department (AVN) , Installations and Logistics Department (I&L) , and the Programs and Resources Department (P&R). The primary focus of the EAESG is to provide executive decisions, guidance, and direction to the EA efforts of the Marine. Corps. The EAESG resolves Marine Corps, cross-Program Evaluation Board (PEB), and interdisciplinary EA related policy issues. The EAESG meets semi-annually or as necessary. to address issues and recommendations made by the EAAB, EAWG, or subcommittees and to approve target architecture changes.

(b) Enterprise Architecture Advisory Board (EAAB). The EAAB is comprised of the Marine Corps Chief Architects (Chief Architect, Chief Business Architect, Chief Systems Architect, Chief Operational Architect, and Chief Data Architect) and representatives from FAMs, as required. The EAAB coordinates architecture efforts and develops and recommends strategic plans and vision for the EA aligned with the strategy and vision of the Marine Corps to the EAESG.

(c) Enterprise Architecture Working Group (EAWG). The EAWG is chaired by the Chief Architect in accordance with reference (u). The EAWG follows the direction of and reports to the EAESG. It comprises Chief Architect representatives (Chief Architect, Chief Business Architect, Chief Systems Architect, Chief Operational Architect, and Chief Data Architect) and architecture community action officers from the Deputy Commandants, Directors, and MARCORSYSCOM. The EAWG ensures the coordination of policy, guidance, and decision making for development and- maintenance of the Marine Corps EA and architecture processes.

(d) MAGTF Architecture Working Group (MAWG). Per reference (v), the MAWG is co-chaired by the Chief Operational Architect and the Chief Systems Architect. It comprises representation from the operating forces, capabilities development, and solution developers. The MAWG provides the direction and procedural guidance needed to define, standardize, clarify, and publish integrated architectural depictions of MAGTF Segment and Solution Architectures. The MAWG coordinates with and informs the EAWG on OAs and SAs with respect to integration into the Marine Corps EA.

(e) Net-Centric Data Strategy Working Group (NCDWG). Per reference (w), the NCDWG is established to lead the coordinated implementation of the Marine Corps Net-Centric Data Strategy. NCDWG will inform the Chief Architect and EAWG on data architecture development and advise on data strategy and authoritative data sources to be used in the Marine Corps EA per reference (r).

MROC

Advises cra

(DIR C4)

Advises

EAESG

Advises p-------------------7-------~ : DJ.rects I

"t ~'____E_AT;-G-------'I~·..·..·..··· ··..·~'----N_CD_W_G _

Coordinates with Coordinates with

I

EAAB

MAWG

Figure 1.--EA Governance Structure

(5) Tasking

(a) Director, C4. Appoint a Chief Architect and a Chief Data Architect for the Marine Corps responsible for performing the roles and responsibilities outlined in this Order.

(b) Deputy Commandant for CD&I. Appoint a Chief Operational Architect for the Marine Corps responsible for performing the roles and responsibilities outlined in this Order.

(c) Commander, MARCORSYSCOM. Appoint a Chief Systems Architect for the Marine Corps responsible for performing the roles and responsibilities outlined in this Order.

(d) Deputy Commandant for I&L (Director, MCBEO). Appoint a Chief Business Architect for the Marine Corps responsible for performing the roles and responsibilities outlined in this Order.

(e) Deputy Commandants and Directorates. All architecture developers use the appropriate architecture repositories as directed by the Chief Architect and Enterprise Services FAM of the Marine Corps. Links to EA policies and repositories are maintained at the C4 Department homepage.

4. Administration and Logistics

a. The Deputy Commandants, Directors, Commanding Generals, Commanders, and Program Executive Offices shall ensure all agencies/entities under their sponsorship or direction comply with the provisions of this Order.

b. Organizations responsible for formulating policy, writing requirements, developing and sustaining systems/applications, and validating systems performance must do so in accordance with the instructions and policies set forth in this Order.

c. Developers, owners, and users of all Marine Corps information systems have the responsibility to establish and implement adequate operation and information technology controls including records management requirements to ensure the proper maintenance and use of records, regardless of format or medium, to promote accessibility and authorized retention per the approved records schedule and reference (u).

5. Command and Signal

a. Command. This Order is applicable to the Marine Corps Total Force.

b. Signal.

Corps Staff

DISTRIBUTION: PCN 10207711600

ACMC

BEA

C4

CIO

CVS

DC AVN

DC CD&I

DC I&L

DC M&RA

DC PP&O

DC P&R

DCMO

DoD

DON

DOTMLPF

EA

EAAB

EAESG

EAWG

FAM

GO/SES

HQMC

I&IMP

ISP

IT

MARCORSYSCOM

MAWG

MCO 5230.20

22 Aug 2011

ABBREVIATIONS

Assistant Commandant of the Marine Corps

Business Enterprise Architecture

Command, Control, Communications and Computers Department

Chief Information Officer

Core Value Stream

Deputy Commandant for Aviation

Deputy Commandant for combat Development and Integration

Deputy Commandant for Installations and Logistics

Deputy Commandant for Manpower and Reserve Affairs

Deputy Commandant for Plans, Policy, and Operations

Deputy Commandant for Programs and Resources

Deputy Chief Management Officer

Department of Defense

Department of the Navy

Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, and Facilities

Enterprise Architecture

Enterprise Architecture Advisory Board

Enterprise Architecture Executive Steering Group

Enterprise Architecture Working Group

Functional Area Manager

General Officer/Senior Executive Service

Headquarters Marine Corps

Interoperability and Integration Management Plan

Information Support Plans

Information Technology

Marine Corps Systems Command

MAGTF Architecture Working Group

Enclosure (1)

MROC

NCDWG

NOTAL

NSS

OA

PEB

PPBS

SECNAV

SA

Marine Requirements Oversight Council

Net-Centric Data Strategy Working Group

Not to All addressees

National Security Systems

Operational Architecture

Program Evaluation Board

Planning, Programming, and Budgeting System

Secretary of the Navy

Systems Architecture

MCO 5230.20

Enclosure (1)