United States Federal Government Technology Guide

s

Effective designs for IT shared services begin with meeting the business requirements of customersI. Overview

The Need to Innovate with Less

II. Definitions, Concepts, and Critical Success Factors

Definitions and Concepts

Critical Success Factors

III. Implementation Strategy

Implementation Milestones for 2012

Migrate Two Areas in 2012

Agency Enterprise Roadmap / Shared Service Plan

Improving IT Lines of Business

Line of Business Service Plans

Online IT Services Catalog

IV. Policy Considerations

New Policies

Other Policy Considerations

V. Federal Governance for IT Shared Services

Shared Services Sub-Committee

VI. Design Principles

General Service Principles

Design Principles

Summary

Appendix A: Definition of Terms

VI. Design Principles

General Service Principle,

but must also include the use of common methods to lower costs. In designing and implementing IT

shared services, the following planning elements need to be taken into consideration:

 Moving existing and new services to the cloud (government or commercial hosting) to

increase service elasticity, reduce system equipment footprints, and free IT organizations

from the expensive work of data center storage, maintenance, backup and recovery burdens;

 Partnering within and between agencies to co-develop and/or share the applications,

systems, and networks that enable a shared service.

 Transforming one’s own agency systems and expertise into a shared service–a center of

excellence—to become a provider of IT shared services to other agencies.

 Complexity of the service must be taken into account.

The following general design principles must also be taken into consideration for each service area:

 Standardization. IT shared service providers must leverage public and private sector

standards to streamline similar functions and lower delivery costs.

 Visibility. A government-wide shared services catalog helps agencies be aware of the wide

array of IT shared services that are available.

 Reusability. Shared-First principles support the development of future-ready architecture

solutions through component re-use in applications, systems, networks, and clouds.

 Platform Independence. IT shared services should strive to maintain platform independence

for applications, systems, networks, and cloud computing environments. This supports more

efficient migrations as new innovative IT solutions become available, and may lower costs.

 Extensibility. The basic shared services of a provider can be used as building blocks for other

services that consumer agencies need. Services can be scaled up or down, based on demand.

 Location Transparency. Users can access services anywhere, using risk-based login methods.

 Reliability. Services provided are robust and stable with service continuity capabilities to

minimize critical system outages to levels established by Service Level Agreements.

Office of E-Government & Information Technology: Strategies and Guides

Strategies

  • Digital Government Strategy (May 23, 2012) PDF (17 pages, 0.8 mb)
    • This document provides the Federal Government with the strategies to innovate more with less, and enable entrepreneurs to better leverage government data to improve the quality of services to the American people.
  • Federal Information Technology Shared Services Strategy (May 2, 2012) (17 pages, 0.8 mb)
    • This document provides organizations in the Executive Branch of the United States Federal Government (Federal Agencies) with policy guidance on the full range and lifecycle of intra- and inter-agency information technology (IT) shared services, which enable mission, administrative, and infrastructure-related IT functions.
  • Federal Cloud Computing Strategy (February 8, 2011) (43 pages, 0.9 mb)
    • This document provides information to help agencies modify their IT portfolios to fully take advantage of the benefits of cloud computing in order to maximize capacity utilization, improve IT flexibility and responsiveness, and minimize cost.
  • 25 Point Implementation Plan To Reform Federal Information Technology Management (December 9, 2010)(40 pages, 0.6 mb)
    • This document is divided into two sections: Achieving Operational Efficiency and Managing Large-Scale IT Programs Effectively. The first section outlines the steps being taken to adopt cloud solutions and leverage shared services. The second section covers the structural areas that impact the success rates of large IT programs across government.

Guides

Guides (Archive)

  • FY15 Guidance on Exhibits 53 and 300 (July 1, 2013) (48 pages, 449 kb)
    • This document provides reporting requirements for an agency's IT Investment Portfolio.
  • FY14 Guidance on Exhibits 53 and 300 (August 3, 2012) (45 pages, 1.0 mb)
    • This document provides reporting requirements for an agency's IT Investment Portfolio.
  • FY13 Guidance for Exhibit 300 A-B
    • This document provides budget justification and reporting requirements for major IT investments.
  • FY13 Guidance for Exhibit 53 A-B
    • This document provides reporting requirements for an agency's IT Investment Portfolio.
  • Agency Public Exhibit 300s FY10 & FY09
    • These documents are the Agency Public Exhibit 300s posted by the Major Federal Agencies.Section 300 of the Circular provides background information regarding what should be included and provides the structure for the Exhibit 300s, to be submitted by agencies to OMB. Each year within two weeks of the release of the President's Budget, agencies are required to make public version of the Exhibit 300s available on the agency's website (Section 300.7).
  • Exhibit 300 Schema, Version 3.07 (for BY11)
    • This document is used to describe and define the type of content including the entities, attributes, elements and notation used for the submission of Exhibit 300s for the BY11 budget cycle.
  • Exhibit 300 Schema, Version 3.07 – Field List (for BY11)
    • This document is used to describe and define the type of content including the entities, attributes, elements and notation used for the Exhibit 300 Schema for the BY11 budget cycle.
  • Exhibit 53 Template (for BY2011)
    • This document is used to describe and define the type of content including the entities, attributes, elements and notation used for the Exhibit 53 for the BY11 budget cycle.
  • Launch of the IT Investment Dashboard
    • The purpose of this document is to provide information on the launch of the IT Investment Dashboard.
  • IT Web - Quick Reference Guide (Version 1.5.01)
    • The purpose of this document is to provide users of IT Web with screenshots and instructions for common activities when preparing their IT budget submissions on the IT Web system.