1. Enterprise Architecture—the Latest Craze
Presentation to the Field Committee
9 May 2006
BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:

2. 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
BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:

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

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

5. 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)
BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:

6. 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
The goals of this effort are to develop a baseline and recommendations for approximately sixty national BLM systems – this baseline will examine these systems to a greater depth than the Enterprise Architecture team has performed in the past.
The actions we will take to develop the baseline are:
We will group or align the systems within common Lines of Business – these will correspond to Federal and DOI/BLM guidelines;
We will examine each of the systems in the LOB and identify functionality in the systems that might be duplications or overlaps;
We will then align the systems to BLM’s mission and priorities;
Examine the infrastructure upon which the systems run to determine overlaps in their infrastructure, and
Finally, develop and present to the ITIB recommendations for moving forward to address any issues uncovered.
The scope for this effort is assumed to be the BLM National Applications as defined by the ITIB and the infrastructure on which the applications run.
The next five slides will go into more detail on each of the actions.
BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:

7. 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.
BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:

8. BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:
Master Component Reusability Library (MACREL) Identify system functionality overlaps within and across buckets
Example  WO-200 and BEA effort to identify redundancies among systems (i.e.,MACREL)
Once the systems are grouped within Lines of Business, we can start to examine the functions that the systems perform in greater detail and to compare those functions within LOB buckets.
Our approach here will be to examine existing sources of information to see what additional information is needed to perform the comparison. We will then work with the system owners to capture any additional information needed, perform the overlap analysis and develop findings and recommendations that can be presented to the ITIB.
An example of this type of analysis is the proposed project between WO-200 and the Enterprise Architecture team called MACREL (Master Data Reusability Library). This project will perform this type of comparison among selected WO-200 systems. such as Rangeland Improvement Project System, the Emergency Stabilization and Recovery pilot, and the Weeds system in development, to identify data and functions overlaps. These are some of the systems shown on the left side of the picture.
The goal here is to identify redundancies in critical non-Geospatial data (“Master” data) in much the same way the eGIS system has identified “Master” geospatial data like “allotments”. The box in the middle of the picture shows this two-pronged approach. Once the redundancies are identified, a course of action can be developed to reduce the redundancies and improve the quality of the data that is collected. One approach for addressing the issues is shown on the right side of the picture. On the next slide, we will look at an approach on how to assess the importance of the systems from mission needs and business priorities.
BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:

9. Data Advisory Hierarchy
Upcoming Activities
Data Standardization Procedure, OCIO Directive , 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 Advisory Hierarchy
DOI
Data
Architect
Sponsors
Leads
Data
Advisory
Committee
BLM
Data
Architect
Member of
BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC: