# Presentation: 186720

## I-MANAGE Program Approach

**I-MANAGE Historical Timeline**
**I-MANAGE Program Administration**
**I-MANAGE Program / Projects Timeline**
**I-MANAGE Integration Approach**
**Overview Individual I-MANAGE Projects**

## I-MANAGE Program Approach

- The “Business Management Information System – Financial Management” (BMIS-FM) contract was awarded after a competitive bidding process.
- Included a live test demonstration by 3 different bidders.
-  Contract award based on 557 business/technical requirements.**  **
- The scope of work for this contract included core financials, budget execution, and financial reporting.
- JFMIP certified software and required hardware to support.
- Optional performance objectives within the contract included budget formulation, project management, inventory, property, purchasing, travel, executive information, acquisition (procurement), and customer relationship management.

**Historical Timeline for I-MANAGE**

## I-MANAGE Program Approach

- BMIS-FM Business Case completed

- BMIS-FM RFQ Released

- BMIS-FM Contract Awarded, Team IBM begins work in Germantown with DOE counterparts

- BMIS-FM renamed to BMIS Phoenix

- Complete Prepare Phase.

**Contract awarded on September 5, 2000.**
- Team IBM resources were assigned to an integrated project team with federal counterparts from DOE.
- Team IBM business partners included Oracle Consulting, SAIC, Arthur Andersen, and 8A businesses
**IBM RS/6000 hardware was installed in November 2000.**
**Oracle Federal Financials v11.03 was loaded and made available in early December, 2000.**

**Historical Timeline for I-MANAGE**

## I-MANAGE Program Approach

- As part of the Phoenix Project, two CRPs were held to test proposed configuration settings for the Oracle software based on the original 557 requirements provided during the RFQ.
- I-MANAGE addressed issues raised by OMB, the IG, and the Mitre study.
- The I-MANAGE Program superseded the Phoenix Project which became the I-MANAGE STARS Project within I-MANAGE.

- Completed  2 Conference Room Pilots (CRPs)

- Complete Focus Phase

- Complete Design Phase

- Upgrade to Oracle V11i, fully web-based

- Successful test of Integrated Contractor Interface

- BMIS Phoenix slowdown for Mitre Study

- IG report issued, Mitre study completed, **I-MANAGE Vision created by Dr. Carnes **

- Briefings for DOE Exec. Steering Committee, OMB, Congress

- JRC Conference

**Historical Timeline for I-MANAGE**

## I-MANAGE Program Approach

**Chris Simpson**
**Program Manager**

- Ed Golden
- Deputy Program Mgr

- Rob Briede
- Testing / QA

- TBD
- Program Control

- TBD
- Architect/Data Modeler

- TBD
- Reqmts/Config Mgmt

- TBD
- Org Transition

- Don Cox
- Team IBM Proj Exec

- Warren Huffer
- DOE Proj Exec

- Laura Kramer
- STARS Project

- Steve  Baker
- Data Whse Project

- Jo Buxton
- Standard Budget

- Doug Baptist
- E-Procurement

- Michael Fraser
- CHRIS / HR

- TBD
- Cyber Security

- Functional
- Consultants

- Software
- Engineering

- Systems / DBA /
-  Security Support

- Project / Program
- Mgmt Support

- Organization Chg /
- BPI-BPR / Training

- Testing / QA
- Consulting

**I-MANAGE** **Program Administration**

## I-MANAGE Program Approach

**Chris Simpson**
**Program Manager**

- Ed Golden
- Deputy Program Mgr

- Rob Briede
- Testing / QA

- TBD
- Program Control

- TBD
- Architect/Data Modeler

- TBD
- Reqmts/Config Mgmt

- TBD
- Org Transition

_**Program Office**_
- Umbrella organization over all projects in I-MANAGE Portfolio.
- Program staff provide oversight, guidance to all projects.
- Establishes “enterprise” vision by coordinating multiple projects to achieve the I-MANAGE vision.
- Allows individual Project Managers to focus on their specific scope, mission.

- Earned value oversight
- Testing guidance / verification / validation
- Program requirements baseline
- Enterprise architecture alignment
- Integrated I-MANAGE Data Model
- Coordinated communications

**I-MANAGE** **Program Administration**

## I-MANAGE Program Approach

**Chris Simpson**
**Program Manager**

- Warren Huffer
- DOE Proj Exec

- Laura Kramer
- STARS Project

- Steve  Baker
- Data Whse Project

- Jo Buxton
- Standard Budget

- Doug Baptist
- E-Procurement

- Michael Fraser
- CHRIS / HR

- TBD
- Cyber Security

_**I-MANAGE Project Portfolio**_
- Individual project initiatives with specific mission, defined scope.
- Temporary lifetime – once system is transitioned to production, project teams disband.
- Will need support from various groups, individuals throughout the organization.
- In many cases, the same people will be asked to support two or more projects.

- Project planning, initiation, execution, control, closing
- Individual POAMs, detailed project plans using MS Project
- Earned value management for each project
- Bi-weekly project status reports
- Common deliverables across projects
- Deliverables specific to single projects

**I-MANAGE** **Program Administration**

## I-MANAGE Program Approach

**Chris Simpson**
**Program Manager**

- Don Cox
- Team IBM Proj Exec

- Functional
- Consultants

- Software
- Engineering

- Systems / DBA /
-  Security Support

- Project / Program
- Mgmt Support

- Organization Chg /
- BPI-BPR / Training

- Testing / QA
- Consulting

_**Team IBM Support**_
- Grouped by domain areas of expertise, with support provide by various business partners.
- IBM, as the prime contractor, provides a single point of control for the Department.
- Provides expertise in each of the areas displayed.
- Focused on knowledge transfer, turnover to Federal co-team members.

- Project planning, initiation, execution, control, closing
- Leverage business partners to provide resources based on discounted GSA rates
- Bring resources to bear as needed, then release
- Based on IBM’s Method Blue, Oracle’s AIM using an SEI CMM-I approach

**I-MANAGE** **Program Administration**

## I-MANAGE Program Approach

**I-MANAGE Program Approach**

- Chris Simpson
- Program Manager

- Don Cox
- Team IBM Proj Exec

- Warren Huffer
- DOE Proj Exec

- Individual Projects
-  Issues / Decisions

- Team IBM
- Issues / Decisions

- I-MANAGE
- Steering Committee

- DOE stakeholders provide subject matter expertise and input for individual project initiatives

- Integrated project teams attempt to make design decisions for their project.  When a decision can’t be made, escalate to the DOE Project Executive.

- Issue

- Issue

- Issue

**HINT**:  When raising issues, each group should provide background, alternatives, and a recommendation.

- Decision

- Decision

- Decision

- Decision

- DOE Project Executive will address issue.  When necessary, escalate to I-MANAGE Program Manager.

- I-MANAGE Program Manager will address issue.  When decision requires consensus of programs, or when necessary, escalate to the I-MANAGE Steering Committee.

**I-MANAGE** **Program Administration – Decision Framework**

## I-MANAGE Program Approach

** **
- Project management best practices embodied in this approach
- Add quality control and visibility to each activity and step

**I-MANAGE** **Program Administration – Closed Loop Process**

## I-MANAGE Program Approach 

- STARS Requirement Baseline
- April 11, 2003

- STARS Design Baseline
- May 30, 2003

- STARS Testing Baseline
- April 30, 2004

- STARS Approved for Ops Baseline
- Aug. 16, 2004

- STARS / Data Warehouse Production Start-up
- Sep. 30 / Oct. 1, 2004

- I-MANAGE Data Warehouse / Standard Budget System Requirements Baseline
- Aug. 1, 2003

- I-MANAGE Data Warehouse Design Baseline & eProcurement Requirements Baseline
- March 31, 2004

- I-MANAGE Data Warehouse Testing Baseline
- June 30, 2004

- I-MANAGE Data Warehouse Approved for Ops Baseline
- Aug. 26, 2004

**I-MANAGE** **Program / Projects Timeline**

- The STARS Project will continue, with a target implementation date of October 1, 2004.
- Big bang approach on fiscal year-end boundary.
- Will replace DISCAS / MARS, and as an interim measure, integrate FDS.
- The Data Warehouse Project and Standard Budget System Project  will begin detailed requirements analysis in 3rd quarter, FY03.
- The I-MANAGE Data Warehouse is also schedule to go live on October 1, 2004; by its nature, a data warehouse continues to grow and evolve.

## I-MANAGE Program Approach

- I-MANAGE Standard Budget System Design Baseline
- Sep. 30, 2004

- I-MANAGE Standard Budget System Testing Baseline
- Mar. 31, 2005

- I-MANAGE Standard Budget System Approved for Ops Baseline
- Aug. 26, 2005

- I-MANAGE Standard Budget System Production Start-up
- TBD

- eProcurement Design Baseline
- Feb. 15, 2005

- eProcurement Testing Baseline
- Aug. 1, 2005

- eProcurement Approved for Ops Baseline
- Oct. 31, 2005

- eProcurement System Production Start-up
- Dec. 31, 2005

**I-MANAGE** **Program / Projects Timeline**

- The I-MANAGE Standard Budget System will ramp up in FY 04, running in parallel with the STARS and I-MANAGE Data Warehouse project.
- Careful design will be necessary to ensure that the planned integration takes place as smoothly as possible.
- This is accomplished by a proper architectural model and approach, the use of standard application programming interfaces (APIs), selection of open technology architectures (e.g. Oracle on a UNIX based platform), and an enterprise data dictionary.

## I-MANAGE Program Approach

**What is Project Management?**
- Project management balances competing demands of:

- Cost (resources)

- Scope (work)

- Time (duration)

- Quality

- Equation for Project Management Formula:
- work = duration * resources

**Project Management Realities**

## I-MANAGE Program Approach

**I-MANAGE Program Approach**

** ****Project management balances competing demands of:**
**Stakeholders with differing needs, expectations**
- _Identified_ requirements (needs)
- _Unidentified_ requirements (expectations)
**Hint:** expectations *should* be translated to needs

- EM, Science, EERE

- NNSA, SO, NE, FE

**Project Management Realities**

## I-MANAGE Program Approach

**I-MANAGE Integration Approach – Putting the Pieces Together**

***Business Transformation***

***Package Selection & Implementation***

***IT Infrastructure***

**To Gain Maximum Benefit in Deploying ERP Systems, You Combine:**

***Consistent policies and procedures across the enterprise******	******; applied strategies for organizational change; strong communications management plans for both projects and program; design and deployment of technical and end-user help desk as individual systems come on line***

***Common database, tools, web-based architecture on centralized servers; EA based approach for application / systems integration, integrity; cyber-security planned from the outset; performance and stress testing planned at the beginning of each project***

***Oracle Federal Financials V11i, PeopleSoft HR v8, Standard Budget System TBD, eProcurement TBD; all packages align with a common architecture; rigorous, multi-level testing throughout each project***

***End-User Training***

***Early core team training, orientation; ***
***class-room training using a “train the trainers” model; computer based instruction; post-implementation followup to ensure quality of training, conduct retraining as required***

**Technology**

**People**

- +

- +

- +

## I-MANAGE Program Approach

**I-MANAGE Program Approach**

**I-MANAGE Integration Approach Using Team IBM’s Method Blue**

**Engagement        ****Manage Relationship, Project, Risk, Quality and Communication**

**IT Infrastructure   ****Specify Requirements, Redesign, Install and Train IS Resources**

**Organization         ****Redesign Organization and Roles, Manage Changes, Train**

**Application           ****Design, Configure, Integrate, Document, Test and Migrate Data**

**Business               ****Define Best Practice, Select Package, Redesign Processes, Define ROI**

**Prepare**

**Focus**

**Deploy**

**Configure**

**Select**

**Validate**

**Redesign**

**Design**

**Develop and utilize a consistent, repeatable approach based upon a repository of reusable intellectual capital artifacts, work products.**

- Domains:
- Categories of applied knowledge and specified deliverables. This allows experts in each area to apply their skills and abilities as needed.  Domain activities span all project phases.

**Project Phases – Time sequenced project activities with exit points**

## I-MANAGE Program Approach

**STARS Project (Oct. 2004)**
- In progress – but must revise current design baseline
- Implementing Oracle Federal Financials version 11i
**I-MANAGE Data Warehouse (Oct. 2004)**
- Will incorporate existing FDW capabilities
- Significantly enhanced to support President’s Management Agenda
**Cost Accounting & Performance  Measurement / Management (Oct. 2004)**
- Grouped separately, but part of STARS, I-MANAGE Data Warehouse, I-MANAGE Standard Budget
- Functionality will be incorporated in the software used for those integrated systems

**I-MANAGE Project Initiatives**

## I-MANAGE Program Approach

**I-MANAGE Standard Budget (FY 2005)**
- Will build on work of original Phoenix Budget Formulation Team
- Analysis activities, requirements development will occur in parallel with STARS, I-MANAGE Data Warehouse, Cost Accounting & Performance  Measurement / Management
- Seeking DOE-wide solution for integrated budget formulation, budget execution, and performance metrics
**I-MANAGE E-Procurement / Contracts Management (Dec. 2005)**
- Tightly integrated with other I-MANAGE Systems
- COTS / GOTS solution

**I-MANAGE Project Initiatives**