DODI 5000.75 Roles
a. The roles described in this section will be performed by OSD, MILDEP or DoD Component level leaders according to designated business system category and delegation of authority.
b. Table 1 defines business system categories based on systems covered by Section 2222 of Title 10, U.S.C., along with decision authorities.
Table 1: DoD Business System Categories
|Business System Category / Reason for Designation||Decision Authorities|
|I||• Priority defense business system Information systems that are operated by, for, or on behalf of the DoD, including: financial systems, financial data feeder systems, contracting systems, logistics systems, planning and budgeting systems, installations management systems, human resources management systems, and training and readiness systems. A business system does not include a national security system or an information system used exclusively by and within the defense commissary system or the exchange system or other instrumentality of the DoD conducted for the morale, welfare, and recreation of members of the armed forces using non-appropriated funds. expected to have a total amount of budget authority over the period of the current Future Years Defense Program (FYDP) in excess of $250,000,000; or
• DCMO designation as priority based on complexity, scope, and technical risk, and after notification to Congress.
|Requirements Validation / CMO Certification: DoD DCMO or as delegated
MDA: DAE or as delegated (not below CAE).
CCA Compliance / Cybersecurity Strategy: CCA: DoD CIO for joint systems; otherwise MILDEP or DoD Component CIO Cybersecurity: DoD CIO
|II||• Does not meet criteria for category I, and any of the following:
• Expected to have a total amount of budget authority over the period of the current FYDP in excess of $50,000,000.
• DCMO or MILDEP CMO designation as requiring CMO certification.
|Requirements Validation / CMO Certification: MILDEP CMO or as delegated; DoD DCMO or as delegated for all other DoD Components
MDA: CAE or as delegated
CCA Compliance / Cybersecurity Strategy: DoD CIO for joint systems; otherwise MILDEP or DoD Component CIO
|III||• Does not meet criteria for category II||All Decision Authorities: Same as category II, except CMO certification not required.|
|1. Transitions from lower to higher business system categories based on FYDP cost thresholds become effective no later than when the President’s Budget is submitted to Congress.
2. Business systems will not transition automatically from higher to lower business system category even if FYDP costs no longer exceed thresholds for the higher category.
3. Business systems that meet Major Automated Information System thresholds in Chapter 144A of Title 10, U.S.C., must meet the statutory requirements of Chapter 144A until its repeal takes effect.
3.2. ROLES IN BUSINESS SYSTEMS REQUIREMENTS AND ACQUISITION
a. Functional Sponsor.
(1) The functional sponsor is the DoD or Component senior leader with business function responsibility seeking to improve mission performance. The functional sponsor confirms the need for improved business operations and represents the user community interests throughout the BCAC. The functional sponsor represents the DoD organization(s) with a business problem or opportunity that may be addressed via the acquisition of a business system, business process reengineering, or related business changes.
(2) The functional sponsor leads solution analysis and change management The process of proactively preparing the user community for changes that will occur to an organization (because of the implementation of a business system, for purposes of this issuance). and creates a successful change environment. The functional sponsor:
(a) Engages stakeholders to keep them actively involved in shaping the complete future solution.
(b) Makes resources available for each phase of requirements and acquisition to include stakeholders and subject matter experts.
(c) Programs and budgets for lifecycle costs of full business spectrum solutions.
(d) Provides input, including market research, to the MDA for the development of the business system Information systems that are operated by, for, or on behalf of the DoD, including: financial systems, financial data feeder systems, contracting systems, logistics systems, planning and budgeting systems, installations management systems, human resources management systems, and training and readiness systems. A business system does not include a national security system or an information system used exclusively by and within the defense commissary system or the exchange system or other instrumentality of the DoD conducted for the morale, welfare, and recreation of members of the armed forces using non-appropriated funds..
(e) Validates that deployed capabilities meet business requirements, deliver expected benefits, and provide return on investment.
(f) Designates the functional lead who will report to the functional sponsor and collaborate with the program manager.
b. CMO. The CMO role will be performed by the DCMO or Component CMO identified as the decision authority in Table 1 depending on the DoD Business System Category and any delegation. The CMO:
(1) Determines that business requirements are valid, capability requirements are achievable, and capability development efforts have feasible implementation plans.
(2) Determines that business systems in development are aligned to processes in the BEA and meet applicable enterprise standards.
(3) Provides CMO Certification to fulfill the requirements of Section 2222 of Title 10, U.S.C.
c. Milestone Decision Authority (MDA). The MDA:
(1) Approves critical acquisition decisions for ATP decision points or concurs in contractual commitments.
(2) Oversees business system delivery within cost, schedule and performance parameters.
(3) Establishes oversight controls for programs, including procedures to report cost, schedule and performance variances and to address reported variances. The acquisition chain of command supports the MDA by leading the program manager and program execution. Specific leadership roles vary by organization but often include the CAE and Program Executive Officer.
d. CIO. The CIO role will be performed by the DoD CIO or Component CIO identified as the decision authority in Table 1 depending upon the DoD Business System Category and any delegation. The CIO:
(1) Confirms CCA compliance based on program manager input and supporting artifacts.
(2) Reviews and approves the cybersecurity strategy before decision points or contract awards for system development.
(3) Establishes standards and supports development of program IT infrastructure and hosting solutions developed by the appropriate program executive officer or service provider.
e. Functional Lead. The functional lead:
(1) Leads business process reengineering and execution of business process changes.
(2) Leads definition of functional requirements and training and deployment for business systems.
f. Program Manager. The program manager:
(1) Leads development and delivery of the business systems that support the delivery of business capabilities.
(2) Provides input to the functional sponsor on process design, requirements, training and other matters that may influence the acquisition strategy for business systems.
3.3. PROGRAM MANAGER RELATIONSHIP. The relationship between the program manager and the functional lead is shown in Table
2. The tasks each key leader performs to lead or support the activities are described by phase in Section 4.
Table 2: Functional Lead and Program Manager Interaction
|Activity||Paragraph||Functional Lead||Program Manager|
|Identify business capability A business capability is the core ability the organization needs to deliver requisite products and services and provide value. needs||4.2.a||Lead||Support|
|Design future business processes & solutions||4.2.b||Lead||Support|
|Define functional requirements||4.2.c||Co-Lead||Co-Lead|
|Define solution approach||4.2.c||Co-Lead||Co-Lead|
|Evaluate solution selection||4.2.d||Support||Lead|
|Define detailed design specifications||4.2.d||Support||Lead|
|Develop and deliver business system||4.2.d||Support||Lead|
|Support business capability A business capability is the core ability the organization needs to deliver requisite products and services and provide value.||4.2.e||Lead||Support|