1. Page 1 of # File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Enterprise Architecture — the Latest Craze Presentation to the Field Committee 9 May 2006

2. Page 2 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Business Process Reengineering (BPR)  Radical redesign of business processes to dramatically improve an organization’s ability to:  Meet increased performance measures - Cost - Quality - Timeliness - Service  Leads to best business practices  Leads easily to defining a Most Efficient Organization (MEO)  Captures business processes across the enterprise  Connects to “Select” phase in Capital Planning  Compliments National Leadership Forum assignments  NOT an IT function, but can lead to better built systems and eliminate redundancies we now have

3. Page 3 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Responding to Business Challenges Document Current Business Processes Evaluate Potential Improvements Document Recommended Processes and Data Requirements Develop Short- and Long- Term Recommendations Business Process Recommendations Technology Recommendations Technology Recommendations Monitor Progress Transition ITIB evaluates technological solutions Transition to CPIC Process Application development requires OMB Exhibit 300 Implement process improvements Document policy changes Document/Update SOPs, BLM manuals, training guides Identify and track performance measures and targets 4 main processsteps     A challenge to: Reduce cost… Increase quality… Reduce cycle time… Improve customer service

4. Page 4 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Response Example Supporting the Land Use Planning Protest Response Process Document Current Business Processes Evaluate Potential Improvements Document Recommended Processes and Data Requirements Develop Short- and Long- Term Recommendations Business Process Recommendations Technology Recommendations Technology Recommendations Monitor Progress Transition Automate standard response templates Investigate searchable response database Standardize protest intake process Establish dedicated protest team Document clear guidance and provide training Develop and track performance measures and targets A challenge to: Reduce cost… Increase quality… Reduce cycle time… Improve customer service GOAL Reduce protest response time from 4-6 months to 90 days Document current process flow Utilize BLM Subject Matter Experts Evaluate strengths and weaknesses Brainstorm improvements SME session to develop consensus Diagram recommended process flow

5. Page 5 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Recent / Ongoing EA Activities  Business Architecture  Planning Protest Response  National Monitoring Strategy  Human Resources Lines of Business  WO-200 Budget Review  Data Architecture  BLM National Monitoring Strategy  DOI Enterprise Data Architecture Support for BLM  Weeds, RIPS, Wild Horse and Burro, Trails Data Support  Recreation (RMiS)  Methodology for Business Transformation (MBT)  Planning and NEPA Blueprint  Land Management Framework Blueprint  Human Resources Blueprint  Applications Architecture Task  Application Architecture Services  Master Component Reusability Library (MACREL)  Technology  BLM Exceptions to the Technical Reference Model (E-TRM)  Technical Review Board  Standard Operating Environment  Oracle  Governance  BEA Governance Integration with Change Management  CPIC Processes  Repository  Establishing Local Server for Repository (Telelogic System Architect)  BLM Systems Inventory Procedures  DOI OIG Review of Systems and C&A  Special Projects  Emergency Stabilization & Rehabilitation (ES&R)  National Wildland Fire Enterprise Architecture (NWFEA)

6. Page 6 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Schedule for Baselining WO-200 Bureau IT Investments  Actions  #1: Align each IT system within a Line of Business;  #2: Assess system alignment to mission and priorities;  #3: Identify system functionality duplications and overlaps;  #4: Assess overlapping infrastructure  April – May; Develop and conduct joint data call with Bill Yeager to include the above plus workforce planning for WO-200  May – June; Perform initial analyses and document initial findings and recommendations  #5: Develop recommendations for moving forward  Late May – June; Work with WO-200 Reps to review and refine recommendations  June-July – Finalize recommendations, present to ITIB

7. Page 7 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Redundant and Parallel Systems Looking out for Field Users  Question : I'm doing a weed treatment, what systems should I enter the data in? Answer : You should enter the data in RIPS, and you will need to enter the data in the Weeds application when it comes on line, and in NIFPORS if you are using fire as a tool.  Question : I'm using prescribed fire to open the canopy cover in a PJ area, increase ground cover, and reduce erosion; what system should I enter the data in? Answer : You should enter your data in RIPS and in NIFPORS and you will need to enter it in the fire rehab system when it comes on line.  Question : I'm working in the fuels program and we are using various methods to reduce hazardous fuels in the wildland/urban interface, what system should I enter the data in? Answer : You should enter the data in RIPS and........  Question : I'm working on a fire rehab project, what system should I enter the data in? Answer : You should enter the data in RIPS and in NIFPORS and in the fire rehab system when it comes on line.

8. Page 8 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Master Component Reusability Library (MACREL) Identify system functionality overlaps within and across buckets Example Example  WO-200 and BEA effort to identify redundancies among systems (i.e.,MACREL)

9. Page 9 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Upcoming Activities  Data Standardization Procedure, OCIO Directive 2006-011, April 2006  A request that BLM identify data stewards to the department  WARNING! this is coming and you should be thinking of who your data stewards are NEXT UP   Testimonial by Jack Hamby, Project Sponsor for Emergency Stabilization and Rehabilitation (ES&R) DOI E-Gov Team DOI Data Architect BLM Data Architect Data Advisory Committee Leads Member of Sponsors

10. Page 10 of 10 File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: Doc StatusRev. DateAuthor/EditorDescription of editFilename/lineage DRAFT 4/20/06mrhinehart/cervinInitial documentbea_pres_fieldcomm_060509.ppt Key Words:BPR, architectureArchitecture Area: File Code(s): Subject Function Code(s): MD 1230 Contract #: NBD020221 Task Number: 8 Document description: This presentation was created for the Field Committee meeting on 5/9/06. Revision History Document Abstract