enterprise architecture — the l atest craze

of #BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart

Enterprise Architecture—the Latest Craze

Presentation to the Field Committee

9 May 20069 May 2006

of 10BLM Enterprise Architecture | Edit Date: 4/21/06 FC&SC:File: bea_pres_fieldcomm_060509.ppt Author: mrhinehart

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


Responding to Business Challenges

Document Current Business Processes


Evaluate Potential Improvements


Document Recommended Processes and Data

Requirements


Requirements

Develop Short- and Long- Term Recommendations


Business ProcessRecommendations


TechnologyRecommendations


Monitor ProgressMonitor Progress

Transition

ITIB evaluates technological solutionsTransition to CPIC ProcessApplication development requires OMB Exhibit 300

Implement process improvementsDocument policy changesDocument/Update SOPs, BLM manuals,

training guidesIdentify and track performance

measures and targets

4 main4 mainprocessprocessstepssteps

A challenge to:Reduce cost…Increase quality…Reduce cycle time…Improve customer service


Response ExampleSupporting the Land Use Planning Protest Response Process






Requirements


Requirements







Monitor ProgressMonitor Progress

Transition

Automate standard response templatesInvestigate searchable response database

Standardize protest intake processEstablish dedicated protest teamDocument 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

GOALReduce 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


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)


Schedule for Baselining WO-200 BureauIT 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 forwardLate May – June; Work with WO-200 Reps to review and refine

recommendationsJune-July – Finalize recommendations, present to ITIB


Redundant and Parallel SystemsLooking 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.


Master Component Reusability Library (MACREL)Identify system functionality overlaps within and across buckets

ExampleExample WO-200 and BEA effort to identify redundancies among systems (i.e.,MACREL)

Define CommonData Standards

Define DataManagement Tools

Define CommonGeospatial Standards

Define DataManagement Tools

Potential WO220 Standardization into the Master Component Reusability Library

ES&R

ES&R Functionality

Unique Functionality

Sign-on

Organization data

Treatment data

Geospatial Needs

Species data

Project data

Person data

Location data

Allotment data

Weeds

Weeds Functionality


Sign-on

Organization data

Treatment data

Geospatial Needs

Species data

Project data

Person data

Location data

Allotment data

WHB

WHB Functionality


Sign-on

Organization data

Treatment data

Geospatial Needs

Species data

Project data

Person data

Facility data

Location data

Allotment data

RIS

RIPS Functionality


Sign-on

Organization data

Treatment data

Geospatial Needs

Species data

Project data

Person data

Facility data

Location data

Allotment data

RIS Functionality


Sign-on

Organization data

Treatment data

Geospatial Needs

Species data

Project data

Person data

Plant data

Location data

Allotment data

RIPS

ES&R

Weeds

WHB

Geospatial Layer Components - Points. Lines, Polygons

Management Areas

Facilities

Treatments

Study Sites

Allotment/Pastures

Data Management Components

Sign-on

Organization

Treatment

Species

Project

Person

Monitoring

Allotment

RIPS

RIS

ES&R Functionality


RIPS Functionality


Weeds Functionality


RIS Functionality


WHB Functionality


Potential Shared Components for WO200 Systems - Allotments/Pastures geospatial project is a great start

WO200 systems have many instances of similar overlapping business logic and data management

Systems in the future could maintain their unique logic and share components

+ Other National/Regional/Local Systems such as RAS, TSIS, FORVIS, VMAP …

Monitoring data


Upcoming ActivitiesData 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 NEXT UP Testimonial by Jack Hamby, Project Sponsor for Emergency Stabilization and

Rehabilitation (ES&R)

DOIE-GovTeam

DOIData

Architect

BLMData

Architect

DataAdvisory

Committee

Leads

Member of

Sp

on

sors

enterprise architecture — the l atest craze

Documents