Presentation on theme: "CPIC Training Session: Enterprise Architecture 2007."— Presentation transcript:
CPIC Training Session: Enterprise Architecture 2007
2 Enterprise Architecture and CPIC Whats Important? CPIC and EA are mutually supportive processes which, when integrated, create the ideal environment for effective IT governance. Enterprise View of Agency IT Portfolio –What is your investment business alignment? –What technologies are you using? –What enterprise services are you using? Moving toward the Target Architecture –Are DMEs updating milestones documented in the Transition Strategy & Sequencing Plan?
3 FY07 Proposed EA Compliance Certification Criteria for majors in DME and selected Lites
4 Basic Solution EA Requirements EA Requirements for CPIC Integration Coordinated with READ Population
5 Complete READ Record Step 01. Complete READ Record. Who: Program architects What: All CPIC Majors and Lites When: June 20, 2007 All CPIC Major and CPIC Lite applications need to be accurately captured within the READ system. The EA requirement for this step is to complete basic descriptive data and key EA-related information about your application. This data entry into READ allows the Agency two key understandings: 1) clear inventory of Agency applications; and 2) relationship of its applications to Agency business objectives. Required READ record information: General, Organization, Point of Contact, Interfaces to other Resources, Strategic Plans, Federal and EPA BRM, Federal SRM, Federal TRM, Life Cycle.
6 CPIC Lites, Complete the Investment Proposal Form Step 02: Complete business justification and BRM in CPIC Lite Investment Proposal Form Who: Program Project Managers and architects What: All CPIC Lites When: August 1, 2007 The requirement for this step is to complete the CPIC Lite Investment Proposal Form. This information allows the Agency to understand: 1) the justification of the application; and 2) alignment of the application to the business reference model (BRM). Much of the information captured in the CPIC Lite Investment Proposal form can be derived from the completed READ record. In this step, the EA team will verify critical EA information in the CPIC Lite Investment Proposal form against the information collected through READ and advise the Program architects on how to resolve any discrepancies. Required information includes: Part I: Background and Budget Information, Part II: Justification (BRM mapping)
7 Complete EA-related information in E300 Step 03: Complete business justification and reference models in OMB Exhibit 300. Who: Program Project Managers, and architects What: All CPIC Majors When: July 18, 2007 The EA requirement for this step is to complete the E-300 EA section. This information allows the Agency to understand: 1) the justification of the application; and 2) alignment of the application to the FEA reference models. Much of the information captured in the CPIC Business Case/E-300 can be obtained from the completed READ record (Step 1). In this step, the EA team will verify critical EA information in the E- 300 form against the information collected through READ. The EA team will identify any discrepancies and will resolve these in coordination with the architects.
8 Part I.F: Enterprise Architecture 1. Is this investment included in your agencys target enterprise architecture? Yes___No___ a. If no, please explain why? 2. Is this investment included in the agencys EA Transition Strategy? Yes___ No___ a. If yes, provide the investment name as identified in the Transition Strategy provided in the agencys most recent annual EA Assessment. b. If no, please explain why? 3. Identify the service components……(SRM mapping) 4. How the investment aligns with the TRM….(TRM mapping) 5. Will the application leverage existing components and/or applications across the Government (i.e., FirstGov, Pay.Gov, etc)? Yes____ No____ a. If yes, please describe. 6. Does this investment provide the public with access to a government automated information system? Yes___ No___ a. If yes, does customer access require specific software (e.g., a specific web browser version)? Yes___ No___ b. If yes, provide the specific product name(s) and version number(s) of the required software and the date when the public will be able to access this investment by any software (i.e. to ensure equitable and timely access of government information and services). YES …describe the reason adequately, referencing retirement and/or migration dates.* If yes, identify what existing components or applications within EPA, or across the Government, that the investment is currently using. Please include EPA enterprise services as well as external components/services. There must be at least one entry in the TRM table for each Component listed in the SRM. All columns are completed including the service specification field.
9 Detailed Solution Architecture Requirements Additional EA Requirements For E300s in DME (and specifically identified additional investments)
10 Aligning the Performance Measures Step 01: Align Performance Information. Who: Program Solution Architects What: All CPIC Majors and selected CPIC Lites in Planning/DME When: July 18, 2007 New Federal emphasis on Connecting the Dots centers on aligning performance measures throughout the enterprise. This enables system owners to better justify their systems in relation to larger Agency objectives, but also for the enterprise to ensure that system development efforts and investment dollars are contributing to the overall progress of the organization. The EA requirement is to align system performance measures to external goals and objectives (specifically GPRA, PAR, and other key Agency objectives). This expands upon the alignment of performance measures to EPA strategic goals and objectives achieved in basic solution inventory activities. The Connecting the Dots information should complement the PRM information submitted in the E300.
11 Connecting the Dots Sample Enterprise Architecture Exhibit 53 Objective 1: Improve effectiveness Performance goal 1: Increase X by 10% Objective 1: Improve effectiveness Performance goal 1: Increase X by 10% Exhibit 300 OMB Budget PART Deficiencies Agency Strategic Plan
12 Completed High-Level Business Model Step 02: Model the Business. Who: Program Solution Architects What: All CPIC Majors and selected CPIC Lites in Planning/DME When: July 31, 2007 All CPIC Major and selected CPIC Lite applications currently in Planning or Development need to model the high-level solution business process. Use of Business Process Modeling Notation (BPMN) in modeling/mapping this process is preferred. The intention of this criterion is not to require extensive process mapping or modeling. Rather, it focuses on the importance of capturing how the system aligns with Program/Agency services, and specifically how it is used/involved with core business service delivery.
13 Business Process Model Sample
14 Completed Conceptual Data Model Step 03: Describe the Core Data. Who: Program Solution Architects What: All CPIC Majors and selected CPIC Lites in Planning/DME When: July 31, 2007 An understanding of data is critical to any application. While we recommend maintaining a data model for all applications and data stores, the EA requirement for 2007 is that only CPIC Majors and selected CPIC Lites in Planning or Development complete a conceptual data model. Integrating the conceptual data models across the Agency will enable EPA to take enhance its data class model and ensure a clear understanding of the information that it maintains and manages as a critical asset.
15 Conceptual Data Model Samples
16 System Interface Model Step 04: Diagram Solution Interfaces. Who: Program Solution Architects What: All CPIC Majors and selected CPIC Lites in Planning/DME When: July 31, 2007 All CPIC Major and selected CPIC Lite applications currently in Planning or Development need to provide a diagram of the solutions interface(s) with other Agency or Partner Organization solutions AND with all EPA enterprise tools. The interface information is important to gain an enterprise view of the applications dependencies on each other and the utilization of the core enterprise tools. The application dependency knowledge helps build complete transition and sequencing plans. The utilization of core enterprise tools will help ensure changes to the enterprise tools are well coordinated across all interfacing applications.