WO-200 IT Baseline for Bureau IT Investments Background and Recommendations Summary July 25, 2006 Melanie Rhinehart.

Slides:



Advertisements
Similar presentations
Evaluation at NRCan: Information for Program Managers Strategic Evaluation Division Science & Policy Integration July 2012.
Advertisements

CPIC Training Session: Enterprise Architecture
1 Presented to Department of Information Technology Jan 28, 2009 New Mexico Department of Health ELECTRONIC REPORTING (e-Reporting) e-Reporting.
Course: e-Governance Project Lifecycle Day 1
Page 1 of 19 File: MPNBlueprint_status_ ppt Author: fries BLM Enterprise Architecture | Edit Date: 11/08/2005 FC&SC: Management Planning.
Centers for Medicare & Medicaid Services eXpedited Life Cycle (XLC) [Insert Project Name] Post Implementation Review (PIR) [Insert Date of PIR] [Insert.
Post Implementation Review (PIR) [Insert Date of PIR]
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Page 1 of 33 File: cmpld_macpherson_brf_ ppt Author: BEA Team BLM Enterprise Architecture | Edit Date: 8/24/2006 FC&SC: 1230/BEA Bureau Enterprise.
Bureau of Land Management NAIP Information Meeting July 19 th, 2006.
Reference Models مدل های مرجع معماری.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Lecture 7 Evaluation. Purpose Assessment of the result Against requirements Qualitative Quantitative User trials Etc Assessment of and Reflection on process.
CHAPTER 9 DEVELOPING BUSINESS/IT STRATEGIES. IT Planning Planning an information system doesn’t start with bits, and bytes, or a Web site. It starts with.
Considering an Enterprise Architecture for the NSDI
Information Systems Portfolio Management March 7, 2002.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Page 1 of # File: bea_pres_fieldcomm_ ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Enterprise Architecture — the.
Enterprise Architecture
The New Product and Services Development Process By SK Winning Innovations for Tomorrow (WIT)
Microsoft Office Project Portfolio Server
Chapter 6– Artifacts of the process
Proposed EA Assessment Framework 2.0 Chief Architect’s Forum (CAF) Dick Burk Chief Architect and Director of Federal Enterprise Architecture Program, OMB.
Transforming the Business of Government Through Shared Services JOHN SINDELAR Deputy Associate Administrator United States General Services Administration.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
IS 460 Notes IS Strategic Planning By Thomas Hilton.
Click to add a subtitle 1 expect the best Lemuel C. Stewart, Jr. Chief Information Officer of the Commonwealth House Appropriations.
COMMUNITY Needs Assessment Overview
Chapter 13: Developing and Implementing Effective Accounting Information Systems
U.S. Department of Agriculture eGovernment Program Select Level Business Cases Overview of Business Case Sections.
The Challenge of IT-Business Alignment
Policy Review (Top-Down Methodology) Lesson 7. Policies From the Peltier Text, p. 81 “The cornerstones of effective information security programs are.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Page 1 ISO/IEC JTC 1/SC 7/WG 7 N Summary of the Alignment of System and Software Life Cycle Process Standards The material in this briefing.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
FEA Data Quality Profile – Progress Report July 12, 2007 Presented to Federal Data Architecture Subcommittee (DAS)
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
AEW Services © Project Portfolio Management: New Opportunities for Project Managers & Business Analysts R. Max Wideman, P.Eng FCSCE, FEIC, FICE,
P1516.4: VV&A Overlay to the FEDEP 20 September 2007 Briefing for the VV&A Summit Simone Youngblood Simone Youngblood M&S CO VV&A Proponency Leader
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
FEA DRM Management Strategy Presented by : Mary McCaffery, US EPA.
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Chapter 3 Strategic Information Systems Planning.
Geospatial LoB: Lifecycle WG Update November 3, 2009.
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
1 expect the best Briefing to the IT Project Review Committee December 8, 2004 ITIB Recommended Technology Investment Projects (RTIP)
U.S. General Services Administration George Thomas, GSA OCIO Chief Architect Line of Sight = Reuse.
Strategic alignment.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
How the CDC Enterprise Architecture Development Methodology Can Help You Albert Decker, Northrop Grumman John Fitzpatrick, CDC.
Slide 1 Software Construction Software Construction Lecture 3.
Geospatial Line of Business FGDC Steering Committee Meeting October 23, 2006.
1 The USDA Enterprise Architecture Program Niles E Hewlett, PMP CEA Enterprise Architecture Team USDA-OCIO January 25, 2006.
Michael J. Novak ASQ Section 0511 Meeting, February 8, 2017
INTRORDUCTION TO IT PORTFOLIO MANAGEMENT Pertemuan 1-2
EI Architecture Overview/Current Assessment/Technical Architecture
Forest Service Geospatial Enterprise Architecture
Transforming the Business of Government Through Shared Services JOHN SINDELAR Deputy Associate Administrator United States General Services Administration.
IST421: Advanced Systems and Enterprise Integration
[Project Name] Project Report
Melanie Rhinehart Date: 21 March 2006
Enterprise Architecture—the Latest Craze
[Project Name] Project Report
The Methodology for Business Transformation
Agenda Purpose for Project Goals & Objectives Project Process & Status Common Themes Outcomes & Deliverables Next steps.
NM Department of Transportation (NMDOT) MMS/PMS Phase 2
Presentation transcript:

WO-200 IT Baseline for Bureau IT Investments Background and Recommendations Summary July 25, 2006 Melanie Rhinehart

2 Introduction Purpose Successful Team Approach Overview Recommendations Detailed Explanation of Recommendations Accept or Reject Recommendations Move Forward

3 IT Baselining Approach Methodology used to Baseline WO-200 Bureau IT Investments Actions #1: Align each IT system within a Line of Business #2: Assess system alignment to mission and priorities #6: Assess the health of each system #3: Identify system functionality duplications and overlaps #4: Assess overlapping infrastructure #5: Develop recommendations for moving forward

4 IT Baselining Approach In Contrast to IV&V Focus on business use of IT User Survey System structure Portfolio optimization Alignment with organization and Federal directions Portfolio-relative financials Focus on project mechanics Artifacts Documentation Project optimization Alignment with project projections Project-focused financials IT Baseline Approach IV&V Approach Focus on Portfolio as a whole Focus on Project-level assessment 2 different approaches ― both add value

5 IT Baselining Approach Financial Analysis Findings Reviewed MIS, PM-Tracked and Business Case Projected IT Costs To make financial information usable for IT Baselining, require more detailed MIS data and rigor in definition and collection What we did Inconsistent financial data Data validation not required for MIS Project Manager cost tracking is more detailed than MIS Financial data useful for broad conclusions only What we found Recommendation BEA working with WO-200 budget teams to identify as-is processes and developing recommendations for process improvement through BEA’s Business Process Reengineering services What the BLM Enterprise Architecture is already doing

6 IT Baselining Approach Extensive Data Collection for these Line of Business Systems Geographic Information Systems Enterprise-GIS Services (E-GIS) Range/Vegetation Rangeland Administration System (RAS) Rangeland Improvement Project System (RIPS) Rangeland Information System (RIS) Emergency Stabilization & Rehabilitation Proof of Concept (ES&R) Inventory Data System (IDS) Native Seed Network (NSN) Weeds Planning/Socioeconomics e-Planning version 1 e-Planning version 2 Economic Profile System (EPS) Wild Horse and Burro Wild Horse and Burro Information System (WHBIS) Wild Horse and Burro Program System (WHBPS) Recreation Recreation Management Information System (RMIS) Accessibility Data Management System (ADMS - DOI-mandated) Forestry Forest Vegetation Inventory System (FORVIS) Timber Sales Information System (TSIS)

7 WO-200 Business Model How Do IT Systems Fit into the Information Value Chain? Organize raw data Analyze data Create information to inform management decisions Create plans or decisions Planning and Decision Support Field Operations Work with BLM customers Collect raw data Implement plans and decisions Feeds Guides RAS, TSIS EPS, NSN EGIS IDS, FORVIS WHBIS, WHBPS RIPS, RIS, Weeds, ES&R ePlanning V1, V2 RMIS, ADMS

8 WO-200 National Portfolio Scope Source: Spending Cap Documents ― WO-200 Systems 3.0% Remaining Investments 96.7% Remaining Investments 97% FY03 Size of the WO-200 Portfolio in contrast to the IT Cap for FY03 through FY06 Remaining Investments 97.4% FY04 FY05 WO-200 Systems 3.3% WO-200 Systems 2.6% Remaining Investments 97.4% FY06 WO-200 Systems 2.6%

9 Information for current and projected project IT tasks Information Management priorities Data components User information Hardware (development, staging, and production) Software (development, staging, and production) System interfaces (current and future needs) System dependencies (current and future needs) Costs tracked by PMs Costs tracked by MIS Costs projected in business cases Collected Information Baseline Project Data Collection in Partnership with WO-200 PERFORMANCE OF IT TASKS Data Collected SYSTEM FINANCIAL USER OPINION Information Focus Areas WO-200 end user satisfaction survey

10 System Health Example 3 Perspectives to Assess the Health of the WO-200 Systems Structural Perspective Technology Alignment / Design Strategy Perspective Extent of Collection of Strategic Data / Unique Data Survey Perspective User Survey Healthier systems cover as much red and yellow as possible

11 System Health Range/Vegetation Using Survey, Structural and Strategy Perspectives In Development, Not Surveyed NOTE RIS-transitioning. IDS-data preservation. External Investment

12 System Health Planning/Socioeconomics Using Survey, Structural and Strategy Perspectives NOTE ePlanning V2 is currently in procurement External Investment

13 System Health Forestry, GIS Using Survey, Structural and Strategy Perspectives

14 System Health Recreation, Wild Horse and Burro Using Survey, Structural and Strategy Perspectives In Development, Not Surveyed Currently Being Rehosted DOI – Mandated Investment

15 Recommendations Overview Benefit / Value Business Priority Alignment HighLow High Investment / Savings Opportunities Shared data services for treatment data. Consider longer term replacement of current range/vegetation systems. IRM Strategic Plan alignment suggestions. Expanded E-GIS data strategy. Specialized IT services. Blueprints, O&M and remaining investment suggestions. Minimal IT infrastructure savings available Highest Value, Highest Priority

16 Next Steps Does this approach have sufficient merit to move on to analyze WO-300? What process shall we utilize for making WO-200 decisions on the recommendations? Next up: Detailed recommendation presentations

17 Doc StatusRev. DateAuthor/EditorDescription of editFilename/lineage Draft5/31/06T.FriesStatus Creationbea_itib_status_ ppt Draft7/7/06Stedman/ FriesUpdatesbea_itib_ ppt Draft7/13/06Stedman/ FriesUpdatesbea_itib_ ppt Draft7/24/06FriesSpeaker notes, GIS, transitionsbea_itib_overview_ ppt Key Words: Architecture, ITIB, WO200 Architecture Area: File Code(s): Subject Code(s): BRM, PRM, TRM, DRM, SRM 1230 Contract #: NBD Task Number: 4 Document description: High level presentation prepared for the July 2006 ITIB Meeting. Revision History Document Abstract