Technology (including existing and new technologies )
Layers of the Enterprise Architecture Business Application Data Technology Current federal guidance suggests thinking about “layers” of the enterprise architecture. Business processes and activities use … Applications such as custom or off-the-shelf software tools that run on … Data that must be collected, organized, safeguarded, and distributed using … Technology such as computer system and telephone networks.
Practical Guide Circle as a Common Reference Obtain Executive Buy - In and Support Establish Management Structure and Control Define an Architecture Process and Approach Develop Baseline Enterprise Architecture Develop Target Enterprise Architecture Develop the Sequencing Plan Use the Enterprise Architecture Maintain the Enterprise Architecture
Current Architecture Business Processes Applications/ Services/ Data Technology Agency Common Enterprise-Wide External/ Government-Wide Agency Common Enterprise-Wide External/ Government-Wide Target Architecture
Establish department-wide EA configuration controls and strategies.
Identify and recommend changes regarding new enterprise-wide standards.
Work with the CIO to improve the maturity level of the architecture discipline within USDA.
Ensure department transition plans are aligned with changing business needs and strategic priorities.
Identify opportunities for Enterprise-wide
USDA EA Governance Model Agency External Common Enterprise Wide E-Board (Oversight) USDA ECCB E-SCCB’s (e.g., CFMS) EA Forum CIO Deputy CIO Fed Arch Groups (e.g., FM LoB, Fed Health, Nat’l Wildland Fire) Ext Standards Groups (e.g.,SAFECOM) Assoc. CIO’s/IO IT Domain Arch. Tech Rev Board (e.g., UTN) Enterprise Arch. Div. Assoc. CIO/ IRM IT Leadership Council Agency CIO’s Agency Staff Off Architects LOB and Program Mgt Program Managers Project Teams Fed CIO Council AIC FEA PMO Direct Authority EA Governance Governance Boards EA Guidance & Support Agency CCB EAR Users Group
Agency Architectures Agency architectures are part of the USDA architecture (They will be regularly imported into central USDA architecture repository). Agency architectures must include cross references to FEA framework (OMB reference models) for Federal decision making.
To develop system requirements aligned to the USDA Strategic Plan & Agency Plans
To identify similar systems – current/future
To develop project level architectures aligned with USDA’s EA.
To obtain information to support the projects business case.
CPIC 300 Process and Enterprise Architecture Business Need Identified and Documented Enterprise Repository Tool (Holds Project Arch. Plans) Project Offices performs Initial architecture check for possible redundancy with existing systems/data, compliance with enterprise plans, and identification of relevant standards Project Office develops business case (300) – prepares justifications for any proposed exceptions to architecture Enterprise Architecture Updated (including approved exceptions) OCIO Review of Business Case –Includes review of Project Architecture Plan by EAD and preparation of Impact Analysis E-Board Decision Investment Approved Start Here Project Office develops Architecture Plan for Project within Repository (Plan includes proposed applications and systems, standards to be used, explanation of why proposed technologies were selected, etc.)
How Does EA Support the Capital Planning Process?
Pre-select (Business Alignment)
Does investment fit the USDA target architecture?
Does the investment duplicate other USDA/Agency functions or processes?
Select (Business Alignment)
Are data design, hardware and software selections, security planning, and telecommunications design in alignment with existing standards and the target architecture?