epa ea governance procedure

8/7/2019 EPA EA Governance Procedure

1/32

U.S. Environmental Protection Agency

ENTERPRISE ARCHITECTUREGOVERNANCE PROCEDURE

April 4, 2006

CIO 2122-P-01.0 (no former number)


2/32

Table of ContentsPurpose ..................................................................................................................................... 3Audience ................................................................................................................................... 3Background ............................................................................................................................. 3Procedure ................................................................................................................................. 4

1. Overview .......................................................................................................................... 41.1 Overview of the EA Governance Procedure ..............................................................4 1.2 Enterprise Architecture Framework ..........................................................................6

2. Segment Architecture ..................................................................................................... 8 2.1 Segment Architecture Development, Review and Approval ......................................8 2.2 Segment Architecture Compliance Certification Process .......................................10

3. Solution Architecture .................................................................................................... 12 3.1 Solution Architecture Development, Review and Approval ....................................12 3.2 Solution Architecture Compliance Certification Process ........................................13

4. Enterprise Architecture ................................................................................................ 16 4.1 Integration of Segment and Solution Architectures ................................................16 4.2 Enterprise Baseline Maintenance ............................................................................16 4.3 Annual EA Review ....................................................................................................16 4.4 Target Architecture Review and Approval ...............................................................17 4.5 Transition Strategy Review and Approval ...............................................................18 4.6 Sequencing Plan Review and Approval ...................................................................19

5. EA Program Management Document Review and Approval Process ..................... 21Waivers .................................................................................................................................. 23Roles and Responsibilities .................................................................................................... 23Definitions .............................................................................................................................. 29Additional Information ........................................................................................................ 30APPENDIX A: RELATED DOCUMENTS ....................................................................... 31

2 EA Governance Procedure


3/32

Approval Date 4/4/06

Review Date 4/09

Subject The Environmental Protection Agency (EPA) Enterprise Architecture (EA) is astrategic information asset base that describes the Agencys business, theinformation necessary to operate the business, the technologies necessary tosupport the business operations, and the transitional processes necessary forimplementing new technologies in response to changing business needs.

Purpose The purpose of the Enterprise Architecture Governance Procedure (the EAProcedure ) is to address how the business processes of the EPA Enterprise

Architecture Policy (the EA Policy ) are implemented (see also section 1.1.1).

Audience The primary audience for the EA Procedure is individuals who have directresponsibility for the strategic planning of EPAs business, data, applications,and technology including, but not limited to: members of the Quality andInformation Council (QIC), Quality Technology Subcommittee (QTS) andInformation Investment Subcommittee (IIS), Senior Information Officials (SIOs),Information Management Officers (IMOs), National Program and RegionalManagers, Segment Architects, members of the Enterprise ArchitectureCoordination Workgroup (EAWG), System Owners, Project Managers, SolutionArchitects, and the EA Team.

Background

The Clinger-Cohen Act of 1996, Executive Order 13011, Office of Managementand Budget (OMB) Circular A-130 and OMB Circular A-11 require that eachfederal agency establish an EA program that focuses on the results achievedthrough capital investments, enhances collaboration, and ultimately enablestransformation of the federal government into a citizen-centered, results-oriented,market-based organization.

EPA has developed an EA that must be maintained and updated under formaldirection and governance in alignment with the Federal Enterprise Architecture



4/32

(FEA) to support Presidential Initiatives and Executive Orders, and to assist inthe Agencys execution of its mission.

The EPA EA provides a performance-oriented framework for documenting thecross-cutting and mission-specific business activities of the Agency, fromalignment of strategic objectives to flow of processes and the technologies thatsupport them. The EPA EA also provides a federally compliant approach todeveloping documentation in a manner that is consistent across EPA. Ultimately,the EA leads to the creation of a strategic information base that provides EPAmanagers with the enterprise-wide knowledge needed to make more informedbusiness decisions.

Authorities The Clinger-Cohen Act of 1996 (also known as the Information TechnologyManagement Reform Act of 1996) (Pub. L. 104-106, Division E);

Executive Order 13011, Federal Information Technology, FR 61-140, July 19,1996;

OMB Circular A-11, Preparation, Submission, and Execution of the Budget(revised November 2, 2005);

OMB Circular A-130, Transmittal Memorandum #4, Management of InformationResources (November 28, 2000);

EPA Enterprise Architecture Policy, Directive 2120.3

Procedure

1. Overview

1.1 Overview of the EA Governance Procedure

1.1.1 Purpose

The purpose of the EA Procedure is to institute the business processes forimplementing the EA Policy . The EA Policy establishes the high-levelgovernance of the EPA EA program, sets direction for how the EA will bedeveloped and maintained, and establishes how information technology(IT) investments will be evaluated for compliance with the EA.

The EA Procedure accomplishes its objectives in a number of ways:

1. Expands on the EPA EA Programs existing governancestructure established in the EA Policy and documented in the

EPA Enterprise Architecture (EA) Governance Framework inorder to:

i. define in detail the roles and responsibilities for developingand approving the EPA EA and its artifacts,



5/32

ii. ensure Agency participation throughout the entire EAdevelopment, review and approval cycle, and

iii. ensure Agency review and approval at formal levels whenissuing the Agencys authoritative EA.

2. Directs readers to the supporting EPA procedures, standards,guidance, and tools for developing and maintaining the EA inconformance with the FEA, utilizing a common framework andmethodology agency-wide (including EA standards, guidance,tools, and templates, the authoritative architecture repository,the Capital Planning and Investment Control (CPIC)Procedures , and the System Life Cycle Management (SLCM)Procedure 1 ).

3. Establishes and documents the review and approval processesfor ensuring the development of a compliant architecture at alllevels (enterprise, segment, and solution) including:

i. review and approval of segment architectures, and

certification of compliance with the Agencys EA,ii. review and approval of solution architectures, and

certification of compliance with the Agencys EA,

iii. maintenance, review, and approval of the enterprisebaseline and target architectures, transition strategy, andsequencing plan, including integration of certifiedcompliant solution and segment architectures, andcoordination of the Annual EA Review, and

iv. review and approval of EA program managementdocuments.

4. Establishes the process for evaluating conformance of ITinvestment solution architectures with the Agency EA andapplicable requirements of the CPIC Procedures and SLCM Procedure .

1.1.2 Content and Organization

The table below lists and describes the sections of the EA Procedure andhow they correspond to sections of the EA Policy :

EA Procedure Section Description EA PolicySection

1. Overview Provides an overview of the EA Procedure , includingits purpose, contents, and organization.

I

1 EPAs Interim Systems Life Cycle Management (SLCM) Policy and Interim SLCM Procedure have beenextended until superseded. However, this EA Procedure references updated versions which are currently inreview, therefore, references are contingent on Agency approval of final SLCM Policy and SLCM Procedure .



6/32

EA Procedure Section Description EA PolicySection

2. Segment Architecture Establishes and documents the process fordeveloping, reviewing and approving segmentarchitectures, and for certifying their compliance withthe Agency EA.

II, III

3. Solution Architecture Establishes and documents the process fordeveloping, reviewing, and approving solutionarchitectures, and for certifying their compliance withthe Agency EA.

II, III, IV

4. EnterpriseArchitecture

Establishes and documents the processes fordeveloping, maintaining, reviewing, and approvingthe Agency EA, including integration of solution andsegment architectures, and conduct of the Annual EAReview.

II, III

5. EA ProgramManagement DocumentReview and Approval

Establishes and documents the process for reviewingand approving EA program management documents.

I, II, III

The EA Procedure also includes sections covering the process forobtaining waivers from the procedure, roles and responsibilities, anddefinitions of EA terms and concepts. Also included in the EA Procedure are an appendix for related documents and related attachments.

1.2 Enterprise Architecture Framework

The EPA EA Framework, as depicted in Figure 1 , is consistent with bestpractices as defined by the Federal Enterprise Architecture Framework (FEAF). The framework includes 1) a baseline architecture, 2) a targetarchitecture, and 3) a transition architecture that describes the migrationfrom the baseline to the target and includes the transition strategy andsequencing plan. As shown, the framework also describes all five layersof the architectural pyramid (strategic, business, data, application, andtechnology). In accordance with best practices as specified by OMB,federal agencies should have the ability to integrate the architecturalcontent of all of an agencys constituent organizational units at all layersof the architecture. Consistent with this best practice, the EPA has furtheradopted the concept of architecture tiers . As shown in Figure 1, the EAFramework now includes enterprise, segment, and solution tiers.

Federal Enterprise Ar chitectureFEA

Baseline Architecture Target ArchitectureTransition Architecture

EPA Non-Federal Partner Architectures

Enterprise Tier

Solution Tier

Segment Tier

Enterprise Tier

Solution Tier

Segment Tier

EPA Enterprise Architecture Framework

Transition Strategy

Sequencing Plan

Performance

ImprovementPlan

Federal Enterprise Ar chitectureFEA

Baseline Architecture Target ArchitectureTransition Architecture

EPA Non-Federal Partner Architectures

Enterprise Tier

Solution Tier

Segment Tier

Enterprise Tier

Solution Tier

Segment Tier

EPA Enterprise Architecture Framework

Transition Strategy

Sequencing Plan

Performance

ImprovementPlan

Transition Strategy

Sequencing Plan

Performance

ImprovementPlan

Figure 1. EPA Enterprise Architecture Framework



7/32

The Agency EA Team is responsible for development and maintenance of the enterprise tier of the architecture. The enterprise tier enables theintegration of multiple segment architectures. Segment architectures 2 areindividual architecture programs within the EA that are developed aroundgroups of business or service functions supporting a common goal. InEPA, these groups can be: 1) programmatic, based on business or servicefunctions within a program (e.g., Drinking Water Protection architecture);2) organizational, based on business or service functions within a ProgramOffice (e.g., Office of Water architecture); and 3) cross-cutting, based onbusiness or service functions performed across multiple Agencyorganizations and programs (e.g., Geospatial architecture). Segment

Architects are responsible for developing segment architectures. Howevereach segment may use a team of architects to assist in the effort. Thesevarious segment architectures comprise the segment tier as depicted inFigure 1 above.

Governance structures within segment architectures can be tailoredaccording to the size and complexity of the segment. An example of anexisting governance structure is the Administrative Systems Architecture(ASA). The ASA Steering Committee is the standing governancestructure which encompasses the segments of the architecture that relateto activities within the management of government resources and supportdelivery of services areas of the FEA Business Reference Model (BRM).The common underpinnings for these business areas are the federalstatutes that require appropriate financial and administrative systemscontrols in place to ensure compliance with the requirements to providesound financial and other administrative services. This governancestructure also ensures an integrated approach to identifying and buildingsolutions that require cross organizational collaboration to deliver value tothe agency while meeting legislative requirements. SIOs responsible for

segment architectures under their purview are encouraged to establishgovernance structures within their segments to ensure synergy betweenother segments, particularly in cross-cutting segments that involvemultiple program offices.

The final tier of the EPA EA Framework is the solution tier. A segmentarchitecture may contain one or more solutions. Solution architectures arespecific investments or initiatives that solve a particular business problem(typically technology-based solutions). Solutions, if they are investments,are subject to the Agencys CPIC Procedures and SLCM Procedure . It isimportant to note that, while a single segment may contain a solution,multiple segments may use that solution. In this manner, the Agencys EAFramework seeks to support the objective of reuse while ensuring clearlines of responsibility for the architecture and implementation of solutions. Solution Architects are responsible for developing solutionarchitectures.

In order to ensure the development and ongoing maintenance of the EPAEA at all levels in conformance with the EPA EA Framework utilizing a

2 The EA Policy uses the term Component Architectures.



8/32

common methodology, two supporting documents have been developed:1) the Architecture Development Content Standard , which establishes therequired contents of the EA (i.e., the what), and 2) the Architecture

Development Methodology , which provides guidance on a methodologyfor developing the EA (i.e., the how). The Architecture DevelopmentTools and Templates have also been developed, which unite the twodocuments and facilitate the implementation of the EA developmentmethodology and the population of the architecture repository via easy-to-use tools and templates. Additional standards and guidance may beprepared as deemed necessary.

2. Segment Architecture

2.1 Segment Architecture Development, Review and Approval

This section of the EA Procedure establishes and describes the roles fordeveloping and the process for reviewing and approving segment architectures

(see Figure 2).

Who: Assistant Administrator (AA), Regional Administrator (RA),Laboratory Director, CIO, QIC, CTO, SIO, Chief Architect, SegmentArchitect

What: EA standards, tools and templates, authoritative architecture repository(see Appendix A).

How: EA Guidance, tools and templates, authoritative architecture repository (see Appendix A).

When: As determined by the QIC

Process:

1. Each year, the Chief Architect, in conjunction with the EAWG,develops recommendations for segment architecture priorities. TheChief Architect recommends list of priorities to the QIC SC forreview. The QIC SC then recommends segment architecture prioritiesand suggested programmatic leads to the QIC, which in turn,recommends to the CIO for approval.

2. SIOs, or designees, assume accountability for segment architecturesunder their purview.

NOTE: SIOs are encouraged to establish governance structures

within their segment architectures. For example, the ASA andResearch and Science Architecture (RSA) segments have establishedgovernance bodies including a workgroup and steering committeecomprised of cross-office representatives.

3. SIO assigns development responsibility for each of their segmentarchitectures to a Segment Architect and structures governance of their segment architectures based on the size and complexity of thesegments.



9/32

4. Segment Architect develops the segment architecture, using EAstandards, EA guidance, tools and templates, to accurately address thebusiness needs of the segment.

5. Segment Architect provides segment architecture to the SIO, ordesignee, for validation.

NOTE: Segment Architects are to submit their segment architecturesto the SIO throughout the year as significant portions of them aredeveloped. This ensures segment architectures are properlymaintained in the Agency EA. Segment Architects are notified by theChief Architect four weeks prior to beginning of Annual EA Review(see section 4.3) so as to allow time for them to update theirarchitecture information prior to analysis.

6. SIO, or designee, reviews segment architecture. SIO validates thatsegment architecture accurately addresses segments business needsOR indicates areas needing modification to Segment Architect.

7. SIO submits segment architecture submission to the Chief Architect

for EA compliance certification (to Section 2.2).8. Once segment architecture is certified EA compliant (or appropriate

waivers have been obtained), SIO forwards segment architecture tohis/her AA, RA, or Laboratory Director (or a designee) for finalapproval.

9. AA, RA, or Laboratory Director approves segment architecture anduses it to better inform budget and capital planning decisions ORrequests modifications from the SIO (return to Step 6).

10. Once AA, RA or Laboratory Director approves segment architecture,EA Team integrates it with the Agency EA (see Section 4.1 below)following change management procedures (See EA Configuration

Management Plan ).

Transition: Chief Architect, in conjunction with the EAWG, developsrecommendations for segment architecture priorities. The Chief Architectrecommends list of priorities to the QIC SC for review. The QIC SC thenrecommends segment architecture priorities and suggested programmaticleads to the QIC, which in turn, recommends to the CIO for approval. SIOidentifies Segment Architects to develop segment architectures under theirpurview. Segment Architects become members of the EAWG and work incollaboration with EA Team. The EA Team releases standards, guidance,tools and templates in a phased approach, working closely with the SegmentArchitects phase by phase to 1) assist with architecture development and 2)

fine-tune the standards, guidance, tools and templates in response to SegmentArchitect feedback. The EA Team coordinates with the Segment Architectsto set appropriate timelines for collecting architecture information.



10/32


2.2 Segment Architecture Compliance Certification Process

This section of the EA Procedure establishes and documents the process forcertifying segment architecture compliance conducted by the Chief Architect(see Figure 2).

Who: SIO, Chief Architect, Segment Architect, EA TeamWhat: EA standards, tools and templates, authoritative architecture repository(see Appendix A).

How: EA guidance, tools and templates, authoritative architecture repository (see Appendix A).

When: As significant portions of the segment architecture are developed.

1. Segment Architect provides segment architecture to the SIO, ordesignee, for validation.

NOTE: The Segment Architect is to submit segment architectures to

the SIO throughout the year as they are developed. This ensuressegment architectures are properly maintained in the Agency EA.Segment Architects are notified by the Chief Architect four weeksprior to beginning of Annual EA Review (see section 4.3) so as toallow time for them to update their architecture information prior toanalysis.

2. SIO, or designee, reviews segment architecture. SIO validates thatsegment architecture accurately addresses segments business needsOR indicates areas needing modification to Segment Architect

3. SIO submits the segment architecture to the Chief Architect.

4. Prior to integration with the Agency EA, the Chief Architect (ordesignee) conducts a compliance certification review to assesssegment architecture alignment with the Agency EA usingpredetermined criteria defined in EA standards.

5. If segment architecture is compliant, the Chief Architect certifies it assuch and provides EA certification documentation to the SIO.

6. If segment architecture is not compliant, the Chief Architect indicatesareas of non-compliance to the SIO. The SIO submits revised segmentarchitecture OR applies for a waiver (see the Waivers section of thedocument for a description of the waiver process).

Transition: Segment Architects develop their segment architectures incollaboration with EA Team. The EA Team releases standards, guidance,tools, and templates in a phased approach, working closely with the SegmentArchitects phase by phase to 1) assist with architecture development and 2)fine-tune the standards, guidance, tools, and templates in response toSegment Architect feedback. The EA Team coordinates with the SegmentArchitects to set appropriate timelines for collecting architecture information.

The segment architecture compliance certification process will beimplemented once CIO, or a designee, approves and issues EA standards.


11/32



12/32

3. Solution Architecture

3.1 Solution Architecture Development, Review and Approval

This section of the EA Procedure establishes and documents the roles fordeveloping, and the process for reviewing and approving solutionarchitectures (see Figure 3).

Who: Chief Architect, Segment Architect, Solution Architect, EA Team


How: EA guidance, tools and templates, authoritative architecture repository,SLCM Procedure, authoritative information resource inventory and EPAregistries and repositories (see Appendix A).

When: SLC phases, project-level reviews and Control Gates 1 and 2 (seeSLCM Procedure ).

Process:

1. Solution Architect develops solution architecture to accuratelyaddress segments business needs using EA standards, EA guidance,tools, and templates and the SLCM Procedure for the solutiondevelopment process. Solution architectures are required for anysolution meeting CPIC or CPIC Lite criteria (see CPIC Policy andCPIC Procedures ).

2. The solution architecture (created during the Definition Phase of theSLC) is evolved through the SLC with more detail added at eachphase. Solution architectures are used by the Chief Financial Officer(CFO), CIO, IIS, and System Owners to better inform budget andcapital planning decisions throughout the SLC.

NOTE: As part of the Agencys CPIC process, Solution Architectsattach solution architectures to their CPIC and CPIC Lite businesscases to better inform budget and capital planning decisions made bythe CFO, CIO, IIS, and SIOs. Chief Architect uses solutionarchitecture to certify IT portfolio as EA compliant as part of theannual CPIC cycle.

3. Throughout the SLC, the solution architecture is reviewed after eachphase of the SLC. There are two types of reviews:

i. Project-level Review: The System Owner and SegmentArchitect(s) ensure 1) solution architecture accurately addressessegments business need and 2) checks for compliance with theEA. Project-level reviews occur at the end of every SLC phase (seeSLCM Procedure ).

ii. Control Gate Review: The SIO and Chief Architect certify solutionarchitecture as EA compliant twice during the SLC at Control Gate1: System Selection and Control Gate 2: EA ComplianceCertification Review. Control Gate 1 occurs at the end of the



13/32

Definition Phase and Control Gate 2 occurs at the end of Acquisition/Design sub-phase. For details of the compliancecertification process, see Section 3.2 below.

4. Solution Architect submits the solution architecture to the EA Team atthe successful completion of each review described above (both

project-level and control gate).5. EA Team integrates solution architecture with the Agency EA (see

Section 4.1 below) following change management procedures (See EA Configuration Management Plan ).

Transition: Solution Architects develop their solution architectures usingcurrent EA and SLCM standards relevant to SLC phase. To successfullycomplete a project-level or control gate review and move to the next SLCphase, Solution Architects must complete their solution architectures to thestandard required for the particular SLC phase.

3.2 Solution Architecture Compliance Certification Process

This section of the EA Procedure establishes and documents the process forsolution architecture compliance certification conducted by the Chief Architect at Control Gate 1: System Selection and Control Gate 2: EACompliance Certified Review of the SLCM Procedure (see Step 3ii in Section3.1 above and Figure 3).

Who: SIO, QTS, Chief Architect, Solution Architect, EA Team

What: EA standards, tools and templates, authoritative architecturerepository, authoritative information resource inventory and EPA registriesand repositories (see Appendix A).

How: EA guidance, tools and templates, authoritative architecture repository,SLCM Procedure (see Appendix A).

When: SLC Control Gates 1 and 2 (see Attachment 2)

Process:

1. Solution Architect provides the solution architecture to the SystemOwner and Segment Architect for EA compliance check during allSLC reviews. Solution architectures are required for any solutionmeeting CPIC or CPIC Lite criteria (see CPIC Policy and CPIC Procedure ).

2. As part of Control Gates 1 and 2, System Owner forwards solution

architecture to SIO, or designee, for review.3. SIO, or designee, reviews solution architecture and conducts a

compliance certification review to assess solution architecturealignment with the Agency EA using predetermined criteria definedin EA standards. SIO validates that the solution architectureaccurately addresses segments business needs and is EA compliantOR indicates areas needing modification to Solution Architect.



14/32


4. If solution is following Full Sequential Work Pattern (determined bySLCM Procedure ), SIO forwards the solution architecture to the Chief Architect for additional EA compliance review during Control Gates1 and 2 (proceed to step 7)

5. If solution is not following Full Sequential Work Pattern (determined

by SLCM Procedure ), SIO certifies solution architecture as EAcompliant and issues documentation of compliance certification toChief Architect and Solution Architect.

6. Solution Architect submits the solution architecture to the EA Team atthe successful completion of the control gate review (proceed to step11).

7. Chief Architect, or designee, conducts a compliance certificationreview to assess solution architecture alignment with the Agency EAusing predetermined criteria in EA standards. As part of Control Gate2: EA Compliance Certification review, the Chief Architect alsoforwards solution architecture to QTS for concurrent technicalfeasibility review (For Control Gate 1: System Selection reviews, skipStep 9).

8. QTS reviews the solution architecture for technical feasibility andCTO either approves technical feasibility OR indicates areas needingmodification to Chief Architect.

9. If the solution architecture is EA compliant, the Chief Architectcertifies it as such and provides EA certification documentation to theSIO.

10. If the solution architecture is not EA compliant, the Chief Architectindicates areas of non-compliance to SIO. The SIO resubmits therevised solution architecture OR applies for a waiver (see the

Waivers section of the document for a description of the EA Waiverprocess).

Transition: The solution architecture compliance certification process willbe implemented once CIO, through consultation with the QIC SteeringCommittee (QIC SC), approves and issues EA standards. Until such time, theChief Architect will continue to use the CPIC business cases to certifysolutions as EA compliant as part of the annual EA certification of the ITPortfolio.

Solution architectures that are developed prior to development of their parentsegment architecture must demonstrate alignment with the EA duringcompliance certification reviews.


15/32



16/32

4. Enterprise Architecture

4.1 Integration of Segment and Solution Architectures

This section of the EA Procedure establishes and documents the process forintegrating certified segment and solution architectures with the Agency EA(see Sections 2.2 and 3.2 above).

Who: EA Team

What: EA standards, tools and templates, authoritative architecturerepository, authoritative information resource inventory and EPA registriesand repositories (see Appendix A).


When: Throughout the year as certified submissions are received

1. EA Team performs a quality assurance (QA) check on released EA-compliant solution and segment architectures

2. EA Team integrates quality-approved, EA-compliant segment andsolution architectures with the Agency EA by enabling population of the architecture repository with the solution and segment artifacts(bottom-up management of EA).

3. EA Team updates and maintains the Agency EA architecture asneeded.

4.2 Enterprise Baseline Maintenance

The baseline EA is maintained through periodic segment and solutionarchitecture submissions (see sections 2, 3, and 4.1). As the segment andsolution baseline architectures are incorporated into the enterprise model, thebaseline EA is populated with up-to-date information.

Architecture information that is inherent to the enterprise tier (i.e. EPAreference models) is incorporated by the EA Team following the EA ProgramManagement Document Review and Approval Process (see section 5.0).

4.3 Annual EA Review

This section of the EA Procedure establishes and documents the annualAgency EA review process.

Who: Chief Architect, EAWG, EA Team

What: EA Baseline, EA Target, EA standards, tools and templates,authoritative architecture repository, authoritative information resourceinventory and EPA registries and repositories (see Appendix A).

How: EA guidance, tools and templates, authoritative architecture repository(see Appendix A).



17/32

When: Annually, beginning in October

1. Chief Architect, EAWG, and EA Team use decisions made during theAgencys strategic planning process (Agencys strategic architecture)to perform a review of the integrated Agency EA, including thebaseline as is architecture and the target to be architecture. EAreview includes analysis across all baseline and target segmentarchitectures. As a result of the Annual EA Review, the Chief Architect may or may not elect to update the target enterprisearchitecture in response to new Agency Strategic Plan, GovernmentPerformance and Results Act (GPRA) goals, Agency initiatives,legislation, OMB mandates, FEA guidance, data and metadatastandards, records management requirements, security requirements,and emerging technologies.

2. Chief Architect, EAWG, and EA Team re-visit and refine Agencytarget architecture for business, data, applications, and technologies(top-down management of the EA).

4.4 Target Architecture Review and Approval

This section of the EA Procedure establishes and documents the process forreviewing and approving the enterprise target architecture (see Figure 4).

Who: CIO, QIC, QTS, CTO, Chief Architect, National Program and RegionalManagers, Segment Architects/EAWG, and EA Team

What: EA standards, tools and templates, authoritative architecturerepository (see Appendix A)


When: As appropriate based on 1) the importance and impact of the changessubmitted by the Segment Architects and 2) the results of the analysisconducted during the Annual EA Review (see Section 4.3 above).

1. EA Team works with Segment Architects in conjunction with theEAWG and National Program and Regional Managers to redefine andupdate the Agency target architecture based on the analysis conductedduring the Annual EA Review (see Section 4.3 above).

NOTE: The target EA refers to the target enterprise, target segmentand target solution architectures collectively. Target segment andsolution architectures 1) are developed in alignment with the

Agency target EA and 2) serve to populate the target EA. The TargetArchitecture Review and Approval process manages change at theenterprise level the target to which all segment and solutionarchitectures will be built. This process is driven by analysisperformed across segment and solution architectures and by theAnnual EA Review which serves to identify external and internalinitiatives that necessitate a change in the target EA.



18/32

2. Chief Architect reviews target EA and concurs OR indicates areasneeding modification to the EAWG and EA Team.

3. Chief Architect presents target EA to QTS and CTO.

4. QTS and CTO review technology and security architecture.

5. QTS and CTO concurs with technology and security architecture ORindicates areas needing modification to Chief Architect.

6. Chief Architect presents target EA to QIC.

7. QIC reviews the target architecture.

8. QIC concurs with the target architecture and recommends to the CIOOR indicates areas needing modification to Chief Architect.

9. CIO reviews, approves, and issues the authoritative target architectureOR indicates areas needing modification to Chief Architect.

10. Target Architecture is used to better inform Agency budget andcapital planning decisions.

4.5 Transition Strategy Review and Approval

This section of the EA Procedure establishes and documents the process forreviewing and approving the Agency transition strategy (see Figure 4).

Who: CIO, QIC, QTS, CTO, Chief Architect, National Program and RegionalManagers, EAWG, EA Team


How: EA guidance, tools and templates, authoritative architecture repository

(see Appendix A).When: As appropriate based on the Annual EA Review (see Section 4.3above) and the issuance of the authoritative Agency target architecture (seeSection 4.3 above).

1. EA Team works with Segment Architects and National Program andRegional Managers to redefine and update the Agency transitionstrategy based on the analysis conducted during the Annual EAReview (see Section 4.3) and the redefinition of the Agency targetarchitecture (see Section 4.4 above).

2. Chief Architect reviews transition strategy and concurs OR indicatesareas needing modification to EAWG and EA Team

3. Chief Architect presents transition strategy to QTS and CTO.

4. QTS and CTO review transition strategy for technical feasibility.

5. QTS and CTO concurs with transition strategy OR indicates areasneeding modification to Chief Architect.

6. Chief Architect presents transition strategy to QIC.

7. QIC reviews the transition strategy.



19/32


8. QIC concurs with the transition strategy and recommends to the CIOOR indicates areas needing modification to Chief Architect.

9. CIO reviews, approves, and issues the transition strategy OR indicatesareas needing modification to Chief Architect.

10. Transition strategy is used to better inform Agency budget and capitalplanning decisions.

4.6 Sequencing Plan Review and Approval

This section of the EA Procedure establishes and documents the process forreviewing and approving the Agency sequencing plan (see Figure 4).

Who: CIO, IIS, QTS, CTO, Chief Architect, EAWG, EA Team

What: EA standards, tools and templates, authoritative architecturerepository (see Appendix A).


When: As appropriate based on 1) issuance of transition strategy (see Section4.5 above) and 2) significant changes affecting sequence of milestones.

Process:

1. As appropriate (see When above), EA Team works with SegmentArchitects on the EAWG to revise sequencing plan.

2. Chief Architect reviews sequencing plan and concurs OR indicatesareas needing modification to EAWG and EA Team.

3. Chief Architect presents sequencing plan to QTS and CTO.4. QTS and CTO review sequencing plan for technical feasibility.

5. CTO concurs with sequencing plan OR indicates areas needingmodification to Chief Architect.

6. Chief Architect presents sequencing plan to the IIS.

7. IIS reviews the sequencing plan.

8. IIS concurs with sequencing plan and recommends to the QIC ORindicates areas needing modification to Chief Architect.

9. QIC reviews the sequencing plan

10. QIC concurs with sequencing plan and recommends to the CIO ORindicates areas needing modification to Chief Architect.

11. CIO reviews, approves, and issues the sequencing plan OR indicatesareas needing modification to Chief Architect.

12. Sequencing Plan is used to better inform Agency budget and capitalplanning decisions.


20/32



21/32


5. EA Program Management Document Review and Approval Process

This section of the EA Procedure establishes and documents the process forreviewing and approving EA Program documents (see Figure 5). EA Program

Management documents include EA Governance (policies, procedures,standards and guidance), EPA Reference Models and the EA Program Management Plan .

Who: QIC, QIC SC, QTS, Chief Architect, EAWG, EA Team

What: EA Program Management Documents

How: EA Program Configuration Management Plan

When: Ongoing as needed

1. As it receives FEA guidance, senior management direction, andchange requests, the EA Team develops new or updates existing EA

program management documents.2. EA Team submits EA documents to the EAWG for review and

recommendation of approval.

3. EAWG reviews EA documents and submits them to the Chief Architect with its recommendation OR indicates areas needingmodification to EA Team.

4. Chief Architect reviews EA documents and either concurs or non-concurs. If Chief Architect concurs, he or she may decide to elevatedocuments for additional review. If Chief Architect non-concurs, heor she indicates areas of non-concurrence to EAWG (Step 1).

5. If Chief Architect does not elevate document for additional review,Chief Architect approves and issues document.

6. If Chief Architect elevates the document for further review, he or shesubmits the document to either the QIC SC, QTS, or other governingbody depending on the nature of the document (i.e. EA policies andprocedures go to the QIC SC, technology standards go to the QTS andall other governance documents follow a review and approval processset forth by the CIO).

7. QIC SC, QTS or other governing body reviews the documents andeither concurs OR indicates areas needing modification to Chief Architect.

8. QIC SC, QTS or other governing body submits approved documentsto the QIC for review (unless otherwise directed by CIO in Step 5).

9. QIC reviews the documents and concurs OR indicates areas needingmodification to Chief Architect.

10. CIO reviews the documents and approves OR indicates areas needingmodification to Chief Architect. The CIO may also choose to notapprove the document.


22/32


EA Program Management Document Review and Approval Process

C I O

I I S / Q T S /

Q I C S C

C h i e f

A r c

h i t e c t

E A W G

E A T e a m

Update/DevelopProgram Mngmt

Document

Review Document Concur?

Yes

Review Document Concur? Yes

Review Document Concur?

Yes

Review Document Yes Yes

Elevatedocument for

additionalreview?

Yes- Elevate to Appropriate Body

Approveand IssueDocument

No

New orUpdates to

ProgramMngmt

Document

Approveand IssueDocument

Approve?

No


23/32


WaiversRequests for waivers from the EA Procedure are addressed to the CIO or his/herdesignee through the IT Waiver Process (See Attachment). Offices have the right toappeal a CIO decision to the Deputy Administrator as outlined in the QIC Charter .

When a solution or segment architecture is determined to be non-compliant with theEA, the Solution or Segment Architect may apply for a compliance waiver via the ITWaiver Process. If the waiver is not approved, the Solution Architect or SegmentArchitect develops an EA compliance plan for approval by the Chief Architect ordesignee.

Waivers are not permanent. Waiver terms are documented for each waiver specifying1) a time period after which the solution or segment architecture must comply withthe Agency EA, 2) the modifications that shall be made to the Agency EA toaccommodate the solution, or 3) some combination of the two approaches specified.

Whenever an EA requirement is waived, the Chief Architect and EAWG willdetermine if a change to the Agency architecture is necessary. If such a change isnecessary, the Chief Architect initiates measures as may be necessary toaccommodate the non-compliant architecture. The changes are subsequentlyapproved by the CIO during the next annual update of the Agency architecture.

Roles and Responsibilities

The Chief Information Officer (CIO) (who also is the AA for the Office of Environmental Information (OEI)) is responsible for:

Approving and issuing the EA Procedure , EA technical standards, andguidance.

Ensuring Agency compliance with the EA Policy and EA Procedure .

Approving and issuing the enterprise architecture, transition strategy, andsequencing plan.

Approving waivers to the EA Policy , EA Procedure , and standards.

The Assistant Administrators (AAs), Chief Financial Officer (CFO), GeneralCounsel, Inspector General (IG), Deputy Chief of Staff to the Administrator,Associate Administrators, and Regional Administrators (RAs) and LaboratoryDirectors are responsible for:


24/32


Ensuring compliance, within their organizations, with EA policy, procedures,and standards.

Providing business expertise to target enterprise architecture and transitionstrategy development efforts.

Approving segment architecture submissions and using architecture to betterinform budget and capital planning decisions.

The Chief Technology Officer (CTO) is responsible for:

Approving technical feasibility of solution architectures following FullSequential Work Pattern during Control Gate 2: EA Compliance CertifiedReview.

Approving technical feasibility of transition strategy and sequencing plan.

Concurring on technology and security layers of the target EA.

Concurring on EA technology standards.

The Chief Architect is responsible for:

Leading the development, maintenance, review, and approval of theAgencys EA, including the baseline architecture, target architecture,transition strategy, and sequencing plan.

Notifying Segment Architects of upcoming Annual EA Review four weeks

prior to commencing. Facilitating the Annual EA Review.

Certifying and providing documentation of EA compliance for segmentarchitectures.

Certifying and providing documentation of EA compliance for solutionarchitectures following Full Sequential Work Pattern during Control Gate 1:EA Compliance Review and System Selection and Control Gate 2: EACompliance Review.

Certifying IT Portfolio as EA compliant during annual CPIC cycle. Providing templates, guidance, and toolsets to support segment and solution

architecture submissions.

Ensuring timely response to OMB annual assessments and quarterly progressreports.


25/32


Approving EA program management documents (except for EA policies,procedures, and standards).

Developing segment architecture priorities, in conjunction with EAWG, andrecommending priorities to the QIC SC.

Communicating and implementing approved EA documents.

The Chief Acquisition Officer (CAO) is responsible for:

Ensuring the EA Policy and the EA Procedure are incorporated, asappropriate, in requests for proposals (RFPs) and contracts.

The Senior Information Officials (SIOs) are responsible for:

Ensuring compliance with the EA Policy and the EA Procedure .

Maintaining segment architectures under their purview and validating thatsegment architectures accurately address the business needs of the segment.

Validating that solution architectures accurately address the business needsof the segment.

Ensuring EA compliance of segment and solution architectures (duringControl Gates 1 & 2 of the SLC) prior to inclusion in the Agency EA.

Forwarding solution architectures to the Chief Architect for EA compliance

review during Control Gates 1 & 2 of the SLC ( SLCM Procedure ). Certifying and providing documentation of EA compliance for solution

architectures not following Full Sequential Work Pattern during Control Gate1: EA Compliance Review and System Selection and Control Gate 2: EACompliance Review.

Assigning Segment Architects to segment architectures.

The Information Management Officers (IMOs) are responsible for:

Supporting SIOs in ensuring compliance with the EA Policy and the EA

Procedure

Coordinating with Senior Budget Officers (SBOs) to ensure consistency of IT Portfolio during the annual CPIC process.

The Quality and Information Council (QIC ) is responsible for:


26/32


Reviewing and concurring on the EA, including, but not limited to the targetarchitecture, transition strategy and sequencing plan.


Recommending segment architecture priorities and suggesting programmaticleads to the CIO for approval.

The Quality and Information Council Steering Committee (QIC SC) isresponsible for:

Reviewing and concurring on the EA Policy and the EA Procedure .

Reviewing and concurring on EA compliance standards.

Reviewing and recommending segment architecture priorities and suggestingprogrammatic leads to the QIC.

The Information Investment Subcommittee (IIS) is responsible for:


Ensuring projects are certified EA compliant before approving inclusion intothe IT investment portfolio.

Reviewing and concurring on the Agencys sequencing plan.

The Quality Technology Subcommittee (QTS) is responsible for:

Reviewing and concurring on EA technical standards.

Reviewing and concurring on technical feasibility of solution architecturesfollowing Full Sequential Work Pattern during Control Gate 2: EACompliance Certified Review.

Reviewing and concurring on technical feasibility of technology and securitylayers of the target EA.

Reviewing and concurring on technical feasibility of the transition strategyand sequencing plan.

The Enterprise Architecture Coordination Workgroup (EAWG) is responsiblefor:


27/32


Leading segment architecture efforts, including developing and maintainingbaseline and target segment architectures, and transition strategies using EAstandards and EA guidance.

Reviewing and concurring on EA management documents.

Analyzing across segment architectures during the Annual EA Review andreviewing and recommending solutions to issues identified during the AnnualEA Review as appropriate.

Assisting Chief Architect in the Annual EA Review; evaluating internal andexternal business drivers that may influence change in the target EA.

Reviewing and recommending segment architecture priorities to Chief Architect.

Communicating and implementing approved EA management documents.

The Segment Architects are responsible for:

Developing and maintaining their segment architecture using EA standardsand EA guidance and ensuring alignment with the EA..

Reviewing solution architectures with System Owners during project-levelreviews (see SLCM Procedure) and ensuring solution architectures reflect thebest practical solution to serving the business needs of the segment whileremaining in alignment with the Agency EA.

Participating as a member of the EAWG. Assisting Chief Architect in the Annual EA Review; evaluating internal and

external business drivers that may influence change in the target EA.

Providing their segment architecture to the SIO for periodic validation andEA compliance check.

Obtaining waivers from the EA Procedure and the EA as appropriate.

The Solution Architects are responsible for:

Developing and maintaining their solution architecture using EA standardsand EA guidance and ensuring solution architectures reflect the best practicalsolution to serving the business needs of the segment while remaining inalignment with the segment architecture and Agency EA.

Providing their solution architecture for EA compliance check during SLCproject-level and control gate reviews.


28/32


Forwarding their solution architecture to the EA Team upon completion of project-level and control gate reviews.

Obtaining waivers from the EA Procedure where appropriate.

NOTE: Solution Architects are responsible for developing solutionarchitectures; however Project Managers can also be designated as having theresponsibility for solution architecture.

The System Owners are responsible for:

Assigning Solution Architects.

Ensuring solution architectures reflect the best practical solution to servingthe business needs of the segment.


Performing EA compliance checks (with Segment Architect) on solutionarchitectures during project-level reviews.

The Enterprise Architecture Team (EA Team) is responsible for:

Day-to-day functions of managing the EA Program including developing,updating, and facilitating review of EA management documents.

Integrating segment and solution architectures with the Agency EA followingchange management procedures.

Maintaining EPAs EA using EA standards and EA guidance.

Providing templates and tools to support architecture submissions forintegration with the Agency EA.

Facilitating and managing Agency EA business processes (including theAnnual EA Review), and development of and updates to the Agency targetarchitecture, transition strategy, and sequencing plan.

Performing analysis across segment architectures and evaluating internal andexternal business drivers that may influence change in the enterprise targetarchitecture.

Responding to OMB annual assessments.


29/32


Communicating and implementing approved EA program managementdocuments.

Definitions Architecture: 1) A structure representing an orderly arrangement of parts; 2) amethod of design and construction; 3) a blueprint for design and construction (i.e., adescription of structure and method); 4) a discipline dealing with the principles of design and construction.

Architecture Repository and Tool: ART is the authoritative reference for the EPAEA, comprising the baseline, target, and transition (transition strategy and sequencingplan) architectures for the Agency. ART supports development and maintenance andcan be accessed at http://intranet.epa.gov/architec/art.html .

Baseline: The current or as-is state of the architecture.

Baseline Architecture: Representation of the current state or as is for thearchitecture.

Enterprise: An organization supporting a defined business scope and mission. Anenterprise is composed of interdependent resources (people, organizations, andtechnology) that should coordinate their functions and share information in support of a common mission (or set of related missions).

Enterprise Architecture: A strategic information asset base; which defines thebusiness, the information necessary to operate the business, the technologiesnecessary to support the business operations, and the transitional processes necessaryfor streamlining business processes and implementing new technologies to improveservice to citizens. It is a representation or blueprint.

Enterprise Lifecycle: The integration of management, business, and engineering lifecycle processes that span the enterprise.

External Partners: Entities, external to EPA, with relationships within EPAs EA.Examples of external partners include: the FEA, other federal departments andagencies, states, tribes, industry and academia.

Federal Enterprise Architecture Framework: An organizing mechanism formanaging development, maintenance, and facilitated decision making of a FederalEA. The Framework provides a structure for organizing Federal resources and fordescribing and managing Federal EA Activities.

Methodology : A documented approach for performing activities in a coherent,consistent, accountable, and repeatable manner.
http://intranet.epa.gov/architec/art.htmlhttp://intranet.epa.gov/architec/art.html


30/32


Segment: Individual architecture programs within the EA that are developed aroundgroups of business or service functions that supporting a common goal. In EPA, thesegroupings can be: 1) organizational, based on business or service functions within aProgram Office (e.g., Office of Water architecture); 2) programmatic, based onbusiness or service functions within a program (e.g., Drinking Water Protectionarchitecture); and 3) cross-cutting, based on business or service functions performedin multiple organizations and programs across the Agency (e.g., Geospatialarchitecture).

Segment Architecture: An architecture that represents a selected portion (i.e., asegment) of the enterprise. A segment architecture provides the business andtechnical context for one or more related solution architectures. A segmentarchitecture represents an independently developed architecture. Rather thannecessarily representing an organization, it represents functions and processes thatcross multiple organizations.

Solution: An answer to part or all of a specific business problem. A solutiongenerally, but not necessarily, involves IT Solutions are funded through investmentsto solve a designated business problem or performance gap.

Solution Architecture: Specific investments or initiatives that solve a particularbusiness problem (typically technology-based solutions). Solutions, if they areinvestments, are subject to the Agencys CPIC Procedures and SLCM Procedure . Itis important to note that, while a single segment may contain a solution, multiplesegments may use that solution.

Target: The future or to-be state of the architecture

Target Architecture: Representation of a desired future state or to be built for thearchitecture within the context of the strategic direction.

Transition Strategy: Identifies the gaps between the baseline and target architecture,specifies alternative approaches to fill the gaps, establishes priorities, assessesdependencies, and includes the sequencing plan.

Recertification Date

Additional Information

For further information about this procedure refer to http://intranet.epa.gov/architec/ or contact the Chief Architect in the EPA Office of Environmental Information(OEI), Office of Technology Operations and Planning (OTOP), Mission InvestmentSolutions Division (MISD).
http://intranet.epa.gov/architec/http://intranet.epa.gov/architec/


31/32


APPENDIX A: RELATED DOCUMENTSUpdated: March 2006

Federal Laws and Guidance

a) The Government Performance and Results Act of 1993 (GPRA) (Pub. L. 103-62);

b) The Chief Financial Officers Act of 1990 (31 U.S.C. 3512 et seq.);

c) The Federal Information Security Management Act of 2002 (which amends the ComputerSecurity Act of 1987 (Pub. L. 100-235);

d) The Paperwork Reduction Act of 1995 (Pub. L. 104-13);

e) The Government Paperwork Elimination Act of 1998 (Pub. L. 105-277, Title XVII);

f) The E-Government Act of 2002 (Pub. L. 107-347);

g) The Rehabilitation Act of 1998 (Pub. L. 105-220);

h) The Federal Managers Financial Integrity Act (FMFIA) of 1989 (Pub. L. 97-255);

i) The Federal Financial Management Improvement Act (FFMIA) of 1996 (Pub. L. 104-208);

j) The Privacy Act, as amended (5 U.S.C. 552a);

k) The Budget and Accounting Act, as amended (31 U.S.C. Chapter 11);

l) The Federal Acquisition Streamlining Act (FASA) of 1994;

m) The Chief Financial Officers Act of 1990;

n) The Presidents Management Agenda, Office of Management and Budget, Fiscal Year2002;

o) OMB Circular A-94, Guidelines and Discount Rates for Benefit-Cost Analysis of FederalPrograms, revised January 22, 2002;

p) OMB Circular A-123, Management Accountability and Control, dated June 21, 1995;

q) OMB Circular A-127, Financial Management Systems, dated July 23, 1993;

r) OMB Circular A-119 Federal Participation in the Development and Use of VoluntaryConsensus Standards and in Conformity Assessment Activities

s) Federal Enterprise Architecture Program EA Assessment Framework 2.0


32/32


Agency Plans, Policies and Procedures:

t) EPA Strategic Plan

u) EPA Capital Planning and Investment Control (CPIC) Policy & Procedures

v) EPA System Life Cycle Management (SLCM) Policy & Procedures

EA Standards 3 :

w) Enterprise Architecture Development Content Standard

EA Guidance:

x) EPA Reference Models

y) Federal Enterprise Architecture (FEA) Reference Models

z) Architecture Repository and Tool (ART) Metamodel Training and Guidance Materials

aa) Enterprise Architecture Procedure Flow Integration Diagram

bb) Enterprise Architecture Program Configuration Management Plan

Charters:

cc) Charter of the Quality Information Council (QIC)

dd) Charter of the Information Investment Subcommittee (IIS)

ee) Charter of the Quality Technology Subcommittee (QTS)

ff) Charter of the Enterprise Architecture Coordination Workgroup (EAWG)

Waivers:

gg) OEI Waiver Process (Obtaining a Waiver from an EPA IT Requirement Procedure)

Authoritative Repositories and Registries:

hh) Architecture Repository and Tool (ART)

ii) Electronic Capital Planning and Investment Control (eCPIC)

jj) Registry of EPAs Applications and Databases (READ)

kk) Extensible Mark-up Language Registry (XMLR)

ll) Environmental Data Registry (EDR)

3 Additional standards and guidance are in development and this section will be updated as necessary.