# Presentation: 047915

## DOI IT Governance

- June 2005

## DOI IT Governance should strive to meet the same objectives that are identified by private sector companies:

- Alignment of IT with the enterprise
- Realization of the promised benefits of IT
- Use of IT to enable the enterprise by exploiting opportunities and maximizing benefits
- Responsible use of IT resources
- Appropriate management of IT-related risks

***IT Governance Institute, ***_***Board Briefing on IT Governance***_***, Second Edition, 2003***

## We can summarize the DOI IT Governance objectives into four focus areas:

_***Strategic Alignment***_:  focus on aligning with the business and collaborative solutions.
_***Value Delivery***_:  focus on optimizing expenses and proving the value of IT.
_***Risk Management***_:  focus on safeguarding IT assets, disaster recovery, and continuity of operations.
_***Performance Measurement***_:  focus on tracking project delivery and monitoring IT services.

***IT Governance Institute, ***_***Board Briefing on IT Governance***_***, ***
***Second Edition, 2003***

## Currently, DOI Governance (business & IT) is performed by the following teams:

_***Core Modernization Blueprint Team***_: Blueprint creation
_***Core Modernization Implementation Team***_: Blueprint implementation
_***Architecture Review Board:***_  Technology Architecture Oversight and Enterprise Infrastructure CCB.
_***CTO Council***_*:*  Technology standards and TRM
_***Domain Advisory Teams***_: Teams focused on technology domains
_***Interior Architecture Working Group***_: Oversees EA within Bureau and Office; Maintains DEAR.
_***DEAR IPT:***_  CCB for DEAR.

_***Interior Business Architecture Team***_: Oversees business architecture
_***Data Advisory Committee: ***_Oversees data architecture
_***Investment Review Board***_: Investment reviews
_***E-Government Team***_: PMA e-government
_***Interior Technology Management Council***_: IT policy & governance
_***Management Excellence Committee***_: DOI strategic leadership
_***Management Initiatives Team***_: DOI business focused teams

## DOI IT Governance Team Options for Discussion

## The as-is DOI governance structure has too much redundancy and complexity.

**IAWG**

**DEAR IPT**

**PRM**

**BRM**

**SRM**

**TRM**

**IBAT**

**e-Gov**

**ITMC**

**IRB**

**DRM**

**DAC**

**CTOC**

_**DATs:**_

- TAG

- RMC

- ITST

- RADIO

- DWC

- CPWT

**ARB**

**CMBT**

- Info Security

- Infrastructure

- Data Mgmt

- App Devel /Acquisition

- Geospatial

- Platform

- Distributed Sys Mgmt

- Record Mgmt

## There are several reasons to move from the current IT governance structure to a new governance structure.

_**The current governance structure**_:
- Has too many standing technology teams
- Has too much overlap between the ARB and CTOC
- Has redundancy in architecture coordination with the IAWG and the DEAR IPT
- Lacks project level IPTs and CCBs that are part of the governance structure.

## The preferred option for DOI IT Governance has fewer teams and more defined relationships.

## The preferred option for DOI IT Governance has fewer teams and more defined relationships.

**The IAWG and DEAR IPT are combined so that architecture coordination is in one team.  This team coordinates and integrates all EA layers.  **

## The preferred option for DOI IT Governance has fewer teams and more defined relationships.

**The ARB no longer exists as technology issues are coordinated through the CTOC.  This team also has reference model responsibilities (TRM/SRM).**

## The preferred option for DOI IT Governance has fewer teams and more defined relationships.

**The many standing domain architecture teams (DATs) have been eliminated and replaced with Technology Evaluation Teams (TETs) that are created as needed.**

## The preferred option for DOI IT Governance has fewer teams and more defined relationships.

**Core Modernization Teams are supported by Project IPTs and Project CCBs (as needed) that are integrated with governance.**

## The preferred option for DOI IT Governance has fewer teams and more defined relationships.

**A Technology Control Board is introduced to provide an enterprise-level CCB for  infrastructure projects and also perform risk management functions (i.e. project reviews/assistance).**

## The preferred option supports all four of the DOI IT Governance objectives. 

- The preferred option supports all four of the DOI IT Governance objectives.

**Strategic Business Alignment**

**Value Delivery**

**Risk Management**

**Performance Measurement**

## There are several reasons why the preferred option is the right option for DOI

_**The preferred governance structure**_:
- Leveraged ad-hoc technology teams instead of standing teams.
- Combines the ARB and CTOC into a single technology focused entity.
- Combines the DEAR IPT and IAWG into a single team focused on architecture.
- Introduces project IPTs and CCBs that are integrated into the governance process.
- Introduces the Technology Control Board in order to provide CCB functions for infrastructure projects and risk management functions across DOI (i.e. project reviews/assistance).

## An alternative to the preferred option is a governance structure without the Technology Control Board

## X

- This option is less desirable as the lack of the Technology Control Board increases risks across the OCIO.

**Strategic Business Alignment**

**Value Delivery**

**Performance Measurement**

**Risk Management**

**Risk Management should be a key objective of any IT governance structure.**

## Overview of Governance Teams

## e-Government Team (e-Gov)

_***Purpose of Team***_:
- Drive business requirements including approving priorities for blueprints and oversight on blueprint efforts.
- Define business priorities
- Provide ongoing coordination including communications with bureaus ad externals regarding E-Government activities
_***Who is on the Team***_:
- Senior level managers from DOI program areas, Up to two Bureau CIOs (elected by the ITMC), Representative from the DOI Office of Planning and Performance Management, Representative from the DOI Office of Budget.
** Items in red are proposed for addition to the charter. *

## Technology Control Board

_***Purpose of Team***_:
- “No Project Left Behind”
- Provides Project Reviews/Assistance for Major IT Investment Projects in Red/Yellow Status.
- CCB for Enterprise Infrastructure change requests.
- A standing board that meets quarterly or more frequently, as needed
_***Who is on the Team***_:
- DOI DCIOs
** Items in red are proposed for addition to the charter. *

## Chief Technology Officer Council (CTOC)

_***Purpose of Team***_:
- A standing board that serves the Interior CIO (Chief Information Officer) and ITMC (Information Technology Management Council) on issues related to technical compliance with the IEA and operational use of technology within DOI.
- Responsible for maintaining Interior's TRM and SRM.
_***Who is on the Team***_:
- DOI CTO, Bureau CTOs or equivalent representative
** Items in red are proposed for addition to the charter.** *

## Technology Evaluation Team (TET)

_***Purpose of Team***_:
- TETs are not standing bodies, but are commissioned by the TRB for the duration of a technology review mission.
- Evaluate the use and classification of technology for a specific domain
- Update and expand the technology standards in the TRM for use in new system specification
_***Who is on the Team***_:
- Members are drawn from standing Bureau groups that deal with specific aspects of the technology in focus for the TET.
** Items in red are proposed for addition to the charter. *

## Data Architecture Committee (DAC)

_***Purpose of Team***_:
- Engages DOI's data community to define data architecture layer of the IEA.
- Serves as liaison between Department and Bureaus/Offices on data and information priorities.
- Performs data related tasks during the creation of Modernization Blueprints.
_***Who is on the Team***_:
- The Data Steering Group is chaired by the Interior Data Architect and is composed of 11 voting members consisting of one member per bureau/office
** Items in red are proposed for addition to the charter. *

## Business Transformation Team (BTT) (was Interior Business Architecture Team - IBAT)

_***Purpose of Team***_:
- Oversees the development of the Interior Modernization Blueprints and makes recommendations to the e-Gov team
- Oversees the development of methodologies, practices and procedures for creating the Interior Modernization Blueprints.
- Maintains the DOI PRM and BRM.
_***Who is on the Team***_:
- One business representative from each bureau and major office, DOI Chief Architect, DOI Business Architect, DOI Data Architect, DOI E-Gov Program Manager, Representative from PPP, ABC Program Manager, Representative form the Office of Budget.
** Items in red are proposed for addition to the charter. *

**Notes:**
Change IBAT to BTT

## Architecture Control Team (ACT)(was IAWG and DEAR IPT)

_***Purpose of Team***_:
- Oversees Enterprise Architecture within their respective Bureaus/Offices consistent with Office of the Secretary and OCIO EA Guidance.
- Responsible for populating all parts of the BEAR/DEAR Repositories
- Facilitates development of Modernization Blueprints for respective bureau.
- Ensures Bureau Architecture leverages all Reference Models to document Bureau portfolio and recommend cross-cutting opportunities to DCIOs
- Serves as Change Control Board for DEAR.
_***Who is on the Team***_:
- Comprised of the chief/lead enterprise architects in the DOI bureaus and offices and the chairs from IBAT, DAC, and CTOC.
** Items in red are proposed for addition to the charter.*

## Interior Technology Security Team (ITST)

_***Purpose of Team***_:
- The Information Technology Security Team (ITST) is charged with the mission of ensuring the successful implementation of Office of Management and Budget (OMB) Circular A-130, Appendix III.
_***Who is on the Team***_:
- The ITST is chaired by the Department IT Security Manager (DITSM) with membership comprised of Bureau IT Security Managers (BITSMs) and representatives from the Inspector General’s office.
** Items in red are proposed for addition to the charter. *

## Capital Planning Working Team (CPWT)

_***Purpose of Team***_:
- Communicate the status and information needs of CPIC to the bureaus.
- Review bureau and office project proposals for compliance with established capital planning and asset management policy.
- Interact with strategic planning and enterprise architecture partners in bureaus and offices.
_***Who is on the Team***_:
- Individuals from the CPIC community.
** Items in red are proposed for addition to the charter. *

## Acronyms

**ABC**: Activity Based Costing
**ACT**: Architecture Control Team
**ARB**: Architecture Review Board
**BEAR**: Bureau Enterprise Architecture Repository
**BITSM**: Bureau IT Security Manager
**BRM**: Business Reference Model
**BTT**: Business Transformation Team
**CIO**: Chief Information Officer
**CMBT**: Core Modernization Blueprint Team
**CPIC**: Capital Planning and Investment Control
**CPWT**: Capital Planning Working Team
**CTO**: Chief Technology Officer
**CTOC**: CTO Council
**DAC**: Data Advisory Committee
**DAT**: Domain Advisory Teams
**DCIO**: Deputy Chief Information Officer
**DEAR IPT**: DOI Enterprise Architecture Repository Integrated Project Team
**DEAR**: DOI Enterprise Architecture Repository
**DITSM**: Department IT Security Manager

**DRM**: Data Reference Model
**DWC**: Department Web Council
**E-Gov**: DOI e-Government Team
**IAWG**: Interior Architecture Working group
**IBAT**: Interior Business Architecture Team
**IEA**: Interior Enterprise Architecture
**IRB**: Investment Review Board
**ITMC**: Interior Technology Management Council
**ITST**: Interior Technology Security Team
**MEC**: Management Excellence Committee
**MIT**: Management Initiatives Team
**OCIO**:  Office of the Chief Information Officer
**PPP**: Office of Planning and Performance Management
**PRM**: Performance Reference Model
- Radio: Radio Infrastructure Team
**RMC**: Records Management Council
**SRM**: Service Reference Model
**TAG**: Telecommunications Advisory Group
**TRM**: Technology Reference Model

## Open Discussion of Other Options