160 likes | 306 Views
EPA Geospatial Segment United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Segment Architecture training April 28, 2008 May 5, 2008. Briefing Purpose.
E N D
EPA Geospatial Segment United States Environmental Protection AgencyOffice of Environmental InformationEnterprise Architecture Program Segment Architecture trainingApril 28, 2008May 5, 2008
Briefing Purpose • Drivers and Goals for EPA Geospatial Segment • Component of the Geospatial Segment • Issues and deficiencies identified in the Geospatial Segment Analysis • Geospatial Segment target recommendations • Using EPA Architecture Standards and Guidance to begin the process of building segments • Question and Answer Session and Next Steps
Drivers for the EPA Geospatial Segment • EPA Strategic Plan • EPA Geospatial Baseline ( 2001) and EPA Gesoaptial blueprint ( 2003) • EPA Enterprise Architecture • Federal Enterprise Archticture • OMB Circular A-16 and associated Federal Geographic Coordinating Committee guidance • Geospatial Line of Business • (Increased effectiveness of short and long-term planning and investing)
Goals for the EPA Geospatial Segment Improve EPA decision-making by incorporating location-based approaches, data, tools and knowledge into EPA business processes. Provide EPA, its partners, and the public with the geospatial data they need to carry out EPA business processes and make environmental decisions Provide EPA staff, partners, and the public with applications and web-services to access, manage, use, analyze, present, and interpret geospatial data to conduct business and make environmental decisions. Establish an effective governance structure for setting priorities for geospatial investments, coordinating geospatial efforts, and communicating how geospatial data and technologies are used within the Agency. Design and implement an enterprise-wide technical infrastructure that supports access, use, management, and delivery of distributed geospatial data and web-services in a seamless manner. • (Increased effectiveness of short and long-term planning and investing)
How the Geospatial Segment was built Focus on Stakeholder needs Each layer of the segment is focused on specific information that EPA geospatial stakeholders need to analyze and make decisions from Requirements Analysis • Align to Architecture Standards and Guidance • Information Flows and System Interfaces for Segment Systems • Overall Segment Performance • Alignment to external Federal geospatial investments
Issues being addressed with the Geospatial Segment • Governance • Need for Senior level champion • Need for policies and procedures for all layers • Data layer • Information redundancy and the inability to use shared resources • Inability to discover, access, and use many existing geospatial data sets • Quality assurance and control procedures for developing and documenting EPA geospatial holdings • Services Layer • Lack of resources and infrastructure to develop shared resources with external partners • Inability to share knowledge and technology across programs and regional offices • Technology layer • Difficulty in ensuring the reliability, performance and sustainability of a robust suite of geodata and services components. • Perception that Geospatial technologies are complex which intimidate use by traditional business managers. • Inadequate bandwidth and telecommunications functionality to support transfers of large geospatial data sets • Rapidly changing technolgy • Training for the use of tools and skills development at all levels
Geospatial Segment – a Slice of Enterprise Services Strategy Business Security Data Applications Technology Strategy Strategy Business Business Data/Databases Data Applications Applications OEI OECA ORD OWSER OEM OPPTS OARM OCFO Technology Technology Geospatial Services Common Solution Common Solution Common Solution UniqueSolution UniqueSolution UniqueSolution UniqueSolution UniqueSolution UniqueSolution UniqueSolution UniqueSolution Enterprise Tools EPA Geospatial Geospatial Users EPA Geospatial Stakeholders EPA Geospatial Segment Architecture 7
Target Recommendation – Use Data Architecture to identify interoperability opportunities • Capturing information used to analyze possibilities for reuse and refinement in the Geospatial target • Stakeholders • Data Stores • Interfaces • Exchanges • Geospatial segment analyzed the baseline environment prior to building their target and noted an inability to analyze geospatial data in a high performance manner
High Level Depictionof the Geospatial Segment Commercial Sector Federal Agencies Common Acquisition Capability Business Driven Applications Governance Common Catalog Data Access Services Service to Citizens Lifecycle Management Services Geo- processing Services Academic, Not-for-profit Institutions, NGO State/Local Government
Target Recommendation – Align Geospatial services to knowledge community stakeholders • Aligning geospatial solutions to desired EPA geospatial mission responsibilities and target capabilities
Target Recommendation – Managing Change through key priorities • Alignment to Segment Business Transformation Framework • Using relevant, timely priorities to capture segment-specific performance information • Is the segment producing outcomes desired by stakeholders?
Successes identified using the Geospatial Segment • Enterprise Licensing • GeoData Gateway and Geospatial Portal Community • Geospatial Budget Coding • Geospatial governance and segment architectures • Compliance with e-Gov initiatives
Using the EPA Architecture Standards and Guidance to begin the process of building segments The EPA Architecture Standards and guidance provides value in building a segment by delivering the following main benefits: • Provide a process and toolset so that segments can successfully capture the information they need to analyze and stakeholders can review captured information for potential recommendations. • Provide a common way of providing architecture services so that all program offices within EPA can capture and share standardized information and methods. • Enable architects to deliver an “analytical architecture” – enables analysis and recommendations for stakeholders issues and problems • Improve analysis of information prior to investment/solution development • Ensure that recommendations are not just IT-focused. • Address all dimensions of a segment and its business functions from its stakeholders to its strategy to its processes to its systems and services
Next Steps • Complete population of standardized metadata within the Geospatial Data Gateway • Complete the Data Architecture and centrally managed geospatial data repository • Continue data development partnerships • Document, improve, and optimize central geospatial business processes • Work with National Program Offices to expand use of core services that enalbe increase use of geospatial information in business • Collaborative management of geospatial investments will be made more adaptable, proactive, and inclusive • Continue to identify enterprise business needs and agency core mission requirements with specific Geospatial context for joint planning and budgeting
Questions and Answer Session • Questions? • Contact: Wendy Blake-Coleman 202-566-1709 Blake-Coleman.wendy@epa.gov