1 / 21

BLM Enterprise Architecture (BEA)

BLM Enterprise Architecture (BEA). Presentation for Monitoring Strategy Meeting. 28 March 2006. Principle Architect Tim Fries (IBM). IT Security eAuthentication Architect Elia Kosnoski. Architectural Governance John Cusimano (IBM) – Lead. Technology Architecture David Levstik – Lead

tawana
Download Presentation

BLM Enterprise Architecture (BEA)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. BLM Enterprise Architecture (BEA) Presentation for Monitoring Strategy Meeting 28 March 2006 BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  2. Principle Architect Tim Fries (IBM) IT Security eAuthentication Architect Elia Kosnoski Architectural Governance John Cusimano (IBM) – Lead Technology Architecture David Levstik – Lead Steve Melville (IBM) Communications Wendy Stedman – Lead BEA CM/DM & Records Trilby Hunt – Lead Heather Karlson Project Management Status Acting Chief Architect Melanie Rhinehart CTO Mike Garratt Program Manager Kevin Trujillo Ops Coordinator Manager Kathleen Campbell Business Architecture Jaimie Stone (G&B) – Lead Chris Ervin (G&B) Andrea Lesher Data Architecture Christine Hawkinson (G&B) – Lead Applications Architecture and Repository Tim Fries (IBM) – Lead Rick Mortell Fred Leibfritz (IBM) Del Linenberger Special Projects ES&R – Al Krueger – Lead GIS – Kevin Trujillo – Lead BPR – Jaimie Stone (G&B) – Lead BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  3. BEA Quality of Service to the BLM BEA Activities • BPR Lab • Data Modeling and Standards • CTAA/Blueprint • ETRM Service to the BLM BLM Needs • Alignment • Integration • Change • Time to Market • Convergence Operationsand Customer Focus Enterprise Architecting Continuous Improvement Total Participation Societal Networking Makes continuous improvement everyone’sresponsibility Ongoingactivities CPIC Integration EA GOVERNING SERVICES BEA Services “Enterprise Architecture is not a product, but a Service” BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  4. Business ArchitectureProject Status • Planning Protest Response • Purpose: Reduce planning protest response time • National Monitoring Strategy • Purpose: Enhance the efficiency and effectiveness of BLM’s assessment, inventory and monitoring efforts; establish and use limited number of indicators; standardize data collection and reporting • Human Resources Lines of Business • Purpose: Ensure the most efficient and effective processes are implemented in the conversion of the employee Official Personnel folder, which will introduce records that are accessible from electronic forms (eForms); the project will also promote a comprehensive electronic personnel data repository covering the entire life cycle of the Federal employee • Budget Effort • Purpose: Reduce the time and enhance efficiency of WO-200 personnel's involvement in the budget process BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  5. Data ArchitectureProject Status • BLM National Monitoring Strategy • Purpose: Enhance the efficiency and effectiveness of BLM’s assessment, inventory and monitoring efforts; establish and use limited number of indicators; standardize data collection and reporting • National Wildland Fire Enterprise Architecture (NWFEA) • Purpose: To create and implement the National Wildland Fire Enterprise Architecture (NWFEA) and supporting program for the national interagency wildland fire community • Emergency Stabilization & Rehabilitation (ES&R) • Purpose: To standardize the system of data collection, to share the data in a consistent and usable format and provide the ability to share data across plans • DOI Enterprise Data Architecture Support for BLM • Purpose: To support DOI in its work with the Data Reference Model BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  6. Data ArchitectureProject Status (Continued) • Weeds, RIPS, WHB and Trails Data Support • Purpose: To develop logical data models for the project to be used in database design; to develop data standards for each of the areas • Recreation (RMiS) • Purpose: To develop a logical data model to be used in the development of a new system for visitor statistics BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  7. MBT TaskProject Status • Planning and NEPA Blueprint • Benefits: Improve cross-DOI planning process and systems • Results/Activities: • Charter agreed upon, gathering signatures, DOI Secretary visibility • Business vision interviews and analysis - January – March • Blueprint now a 2006 BLM Management by Objective item • Contact: Deb Rawhouser, WO-210, Willie Taylor, DOI • Land Management Framework Blueprint • Benefits: Lead strategy for DOI land management blueprints • Results/Activities: • Planning to work with DOI EA team to structure scope in February • Planning to work with BIA to reuse DLRM effort for framework • Anticipated schedule: parallel MPN Blueprint timeframe • Contact: Deb Rawhouser, WO-210 BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  8. MBT TaskProject Status (Continued) • Human Resources Blueprint • Benefits: Lead efforts to align BLM-specific blueprint with DOI • Results/Activities: • BEA delivered BLM HR-specific blueprint 1QFY05 • DOI will be engaging Bureaus for HR MBT Blueprint 2QFY06 • Anticipating alignment/participation/positioning activities 2Q-4QFY06 • Contact: Clark Collins, WO-700 • Energy Blueprint ?? BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  9. Applications ArchitectureProject Status • Application Architecture Services • Benefits: Provide services aligned with EA best practices • Results/Activities: • Develop and offer SLA-based centralized architecture services • Re-engineering services – design, analysis, technology services • Pro-active CPIC services for Select, Control, Evaluate business cases • Maintain DEAR system inventories (BLM CIO responsible for inventory) • Contact: Melanie Rhinehart, WO-500 • Master Component Reusability Library (MACREL) • Benefits: Lead efforts to deploy shared software components • Results/Activities: • Proposal to work with WO-200 to design shared component strategy • Scope proposed to Bill Yeager 1QFY06 • Anticipating go/no-go in the 2Q-3QFY06 timeframe • Contact: Bill Yeager, WO-200 BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  10. TechnologyProject Status • BLM eTRM(Exceptions to the Technical Reference Model) • Purpose: Guidance in alignment with Federal Enterprise Architecture Technical Reference Model (TRM); released to compliment DOI TRM and address BLM specific needs • Provides guidance with respect to the following: • Security & approved platforms • Application environment / storage • Approved technologies / standards • Status: Published December 2005 • Future Work: Update will occur February 2006 based on feedback • Contact: Mike Garratt BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  11. TechnologyProject Status (Continued) • Technical Review Board (TRB) • Purpose: Technical Advisory board to the ITIB • Provides guidance with respect to: • Security & Approved Platforms • Technical Advisory Groups • Serves as an adjudication board on Information Technology Architecture (ITA) issues • Guiding the evolution of the ITA through regular input to the DOI Technical Reference Model (TRM) and updates to the BLM eTRM • Status: Meetings typically Quarterly • Future Work: Next TRB meeting scheduled January 25, 2006 • Contact: Mike Garratt BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  12. TechnologyProject Status (Continued) • Standard Operating Environment • Purpose: Guidance for applications seeking to deploy within the Internet Support Services group • Provides guidance with respect to the following: • Security & Approved Platforms • Application deployment and process requirements • Status: Published January 2006 • Future Work: Update technologies and process as necessary as a Living Document • Contact: Joan Nadeau BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  13. TechnologyProject Status (Continued) • Oracle • Purpose: Establish BLM wide implementation guidelines for Oracle as no guidelines have been accepted or proposed by BLM; all applications in process have to justify Oracle use and implementation to security and CM • Status: Working with USGS and Oracle in identifying best practices for Grid Control R2 – Will allow overlay of canned security templates • Future Work: Await release for Windows Platform - Forward results to CM and Security for review BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  14. Architectural Governance Tasks BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  15. EA Governing Policy • An integrated governance policy is the encompassing tool which correlates business needs to IT activities and controls IT expenditures from a business perspective BLM Governance Policy (Checkpoints / Controls) Information Technology BLMBusiness  TRM DRM BRM PRM SRM BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  16. GovernanceProject Status • NWFEA • Purpose:To develop a national wildland fire enterprise architecture program including (methodology, repository, as-is structure) • Status and Future Work: • NWFEA project is continuing with use of the National Wildland Fire Enterprise Architecture Organizational CONOPS, delivered in December, ’05. • Current / continued activities include: • a multi-agency review of current Capital Planning, Acquisition, C&A policies and procedures for the DOI, Forest Service • Development of the NWFEA Communications Standards and Plans • Development of a Wildland Fire Specific Methodology for Business Transformation Plan • Contact: Judy Crosby, Franklin Peters BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  17. GovernanceProject Status (Continued) • BEA Governance Integration with Change Management • Purpose: Develop an integrated BLM Change Management strategy which will incorporate CM / BEA service capabilities and needs • Status: Working with BLM CM group and BEA Technology lead, the governance activity is examining / improving current change control / waiver processes and procedures • The concept is the development of a "single point of contact " for Program / Project Managers regarding change requests needed for various BLM funded initiatives • A key goal of this activity is to streamline the various "points of entry" and develop a cohesive governance structure / policy to address the needs of BLM community • Contact: Mike Garratt / Jim Armstrong / Dave Levstik BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  18. GovernanceProject Status (Continued) • BLM Capital Planning and Investment Control (CPIC) Processes • Purpose: Identify BEA services including governance activities within the BLM CPIC Process • Status: Continuing work in assisting the BLM improve its current CPIC activities by offering evaluative / rating services for CPIC items submitted via the Investment Management group • Contact: Melanie Rhinehart, WO-500 BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  19. BEA RepositoryProject Status • Purpose • Provide information store of BLM systems and investments • Provide a uniform EA tool for modeling and analysis • Benefits • One-stop location for all systems and investments • Meet OMB, DOI, OIG requirements for systems and security • Status • Establishing local server for repository (Popkin System Architect), instead of Citrix-based DEAR tool • Developing procedures for maintenance of BLM systems inventory • DOI OIG Review of systems and C&A • Future Work • Repository update procedures integrated with CPIC and Security processes • Development of BLM-specific repository reports • BLM Contact:Melanie Rhinehart, WO570D BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  20. Special Projects • ES&R • Purpose: To standardize the system of data collection, to share the data in a consistent and usable format and to provide the ability to share data and plans across BLM district offices. • Status and Future Work: • Continue to support testing of the ES&R Pilot system at various sites in NV, UT, AK and AZ • Enhance the ES&R Pilot system using the input from lessons learned by this year’s testing • Support an introduction to the ES&R Pilot system at the Seed Processing Workshop • Re-host the Pilot system to the Linux/Apache and Oracle Servers • Evaluate adding Geospatial capabilities into the ES&R Pilot as ArcIMS is added to the Linux/Apache servers • Evaluate the extraction of inventory data from the Pacifica system used by the National Seed Warehouse in Boise • Contact: Louise Greathead and Jack Hamby, WO-220 BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

  21. WO-570 Data • Enterprise Data Quality Tool • Held basic training 2 weeks ago • FBMS participated and are ready to use tool • WHB participated and are ready to use tool • NIRMC assisting with set up today • Inquiry from DOI for direct use for FBMS Looking into licensing for them • Corporate Metadata Repository (CMR) • Just added business rules functions • Adding lines of business data standards from DOI • Support Jim Horan and policy • Data Stewards Training—continuous process • Geospatial modeling and national geo-database • Data Exchange Project Support = Oil & Gas G2B project BLM Enterprise Architecture | Edit Date: 1/19/06 FC&SC:

More Related