Text Size

IT Infrastructure Integration Program (I3P) FAQs
I3P is NASA's IT Infrastructure Integration Program which will transform NASA's IT Infrastructure services from a Center-based model to an enterprise-based management and provisioning model.  The scope of I3P is broad, entailing consolidation and central management of IT services in the areas of Tier 1 service desk and ordering, web services and technologies, enterprise business and management applications, integrated network/communications services, end user services, and data center services.
In 2007, there was a convergence of circumstances that led to the development of the IT Infrastructure Integration Program, or I3P, and subsequent approval through the appropriate Agency governance bodies.

First, two separate studies, one from the Office of Management and Budget, and one from NASA's Program Analysis and Evaluation Office, indicated that NASA spends more than peer organizations on IT infrastructure (Networks, Data Centers, Computer Hardware, etc). We had to find a way to become more efficient in providing IT services, which pointed towards consolidation of services at the Agency level to gain economies of scale.

Second, execution of the Constellation Program was reliant on sending work packages across the NASA Centers to accomplish program requirements. There was a very critical need for the IT infrastructure to support the collaboration required under this distributed work model (10 healthy NASA Centers). Instead of acting as separate business units, Centers needed to be able to share program data and applications across a more robust and integrated network. Projects to increase network bandwidth and replace obsolete equipment, as well as implement collaborative tools to enable the mission, were needed.

Third, IT security at NASA was deemed a material weakness under NASA internal control processes due to various vulnerabilities and documented security incidents associated with how the IT infrastructure was designed, provisioned, and managed. We had to become more disciplined in controlling system access, patching vulnerabilities and monitoring/securing network boundaries.

Fourth, several large Agency IT contracts were on the verge of expiring and in need of replacement, such as the Outsourcing Desktop Initiative for NASA (ODIN) contract. Rather than recompete contracts in kind, a fresh look was given at customer pain points, lessons learned, service requirements, technology possibilities, and government/industry best practices in developing the new I3P procurements. In conjunction, NASA is implementing a disciplined IT Service Management capability that aligns with the IT Infrastructure Library (ITIL) V.3 framework for service strategy, design, transition, operation, and continuous improvement.

Finally, the Agency needed to implement improved Identity, Credential and Access Management to meet federal mandates under Homeland Security Presidential Directive – 12 (HSPD-12). This required several critical projects be executed and managed at the Agency level to enable use of smart cards for logical access and authorization to systems, such as NASA Consolidated Active Directory (NCAD), NASA Account Management System (NAMS), etc. Single sign-on is now becoming more prevalent as a result of these initiatives.
A service is a means of providing value to customers by facilitating the outcomes customers wish to achieve without customers taking on the ownership of costs and risks. I3P is comprised of six IT service areas that deliver IT services to Agency customers. The six IT service areas and corresponding contracts are:

Business and Management Applications - EAST (Enterprise Applications Service Technologies)
Web Sites and Applications - WEST (Web Enterprise Service Technologies)
End-User Services - ACES (Agency Consolidated End User Services)
Tier 0 and Tier 1 Service Desk and Ordering System – ESD/ESRS (Enterprise Service Desk and Enterprise Ordering System)
Networks and Communications Services - NICS (NASA Integrated Communications Services)
Data Center Services - NEDC (NASA Enterprise Data Center)

Services under existing contracts will transition to the identified I3P service contracts.
To a large degree, we expect services under I3P to be transparent to the majority of Agency personnel. That said, there are some things users will notice. Most noticeable, as a default, return to service for most desktops and laptops will be within 8 hours across all Centers. Also, for those ordering services provided by I3P, a central ordering system and service desk operated at the NSSC will be used. No more trying to figure out whether to call ODIN, a Center help desk, or the IEMP help desk. Of course, if the selected vendor under the ACES procurement decides to provide all new hardware, all current ODIN users will be provided new desktops or laptops, as well as BlackBerry and cell phones, which will require significant coordination and planning.

Names of services will be different as well. Instead of GP-1 and SE-1 seats under ODIN, ACES will provide an S (Standard) Seat, an M (Modified) Seat, and a B (Build) Seat. These options should satisfy the majority of Agency end-user computing requirements.

For the resource management community, processes for funding IT services will change due to the Agency contracting approach. Currently every Center has a different way of funding IT services. In the future, there will be common processes across the Agency.

Also, since there will be one contractor providing end to end network services across the Agency under a cost type contract, we will not be charging customers for each network attached device, as was the practice under ODIN. Instead, each Center will pay for a portion of networking costs based on apportionment of resources required to support their requirements.
IT Services will transition in waves, over a period of phased dates. For example, many centers will transition to new contracts over a period of several months, followed by another set of Centers transitioning in subsequent months, etc. We believe this approach minimizes risk. Specific dates regarding when centers are phasing into new contracts will be made available once contracts are awarded and transition plans are finalized.
New processes for funding and invoicing the new contracts are being developed in close coordination with the resource management community. We expect common processes to result in streamlined ordering and payment, potentially including the use of purchase cards for some services.
Training will be available specific to user role. For example, end users will need to be made aware that new services will be available and be trained to know how to order these services. NASA employees who will provide service may require more involved training so they are able to perform responsibilities as a service provider, or in a role that works closely with contractor service providers. Training will likely entail both online and in-person delivery mechanisms, depending on training requirements and appropriateness. Further information about training per Service area will be provided once respective contractors per Service area are engaged.
Yes, although these services will satisfy the vast majority of Agency users, a process will be defined to request a waiver based on valid rationale. With appropriate justification, approval of most waivers is expected. Each Center Chief Information Officer will be involved in the waiver process.
Depending on the vendor selected for the ACES contract, users may receive a new computer in the July – November 2011 timeframe or may retain existing hardware, depending on the successful offer or's approved approach. More information about this will be made available after ACES is awarded and transition plans are approved.
There are some preliminary plans to conduct road shows at each Center in 2011. Road shows may be service specific in order to brief impacted stakeholders about a particular service or a road show may provide information pertaining to integrating multiple I3P services. Please check this site to hear more about upcoming activities.
Yes. Although services are being consolidated and managed centrally, a hosting center will be responsible for overseeing particular services. The following is a mapping of host centers to service areas:

GSFC will host WEST services in partnership with ARC
MSFC will host NICS services in partnership with ARC and GSFC
MSFC will host EAST services
NSSC will host ACES and ESD services
KSC will host NEDC services
Yes. There is a Communications plan being executed at the program level by a team of communications points of contact at each Center and service area. This team, lead by Eldora Valentine of the NASA Office of the CIO, is providing support to each of the Service Area Communications teams that are executing detailed communications plans for each service area.