Components in the DHS EA

2,885 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,885
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
233
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Enterprise architecture is the master plan for enabling the business through information technology EA describes: The business The data needed to perform that business The applications that deliver the data The basic enabling technology infrastructure It is A set of principles, goals and objectives, and standards that guide the EA process, and A specific methodology and approach for implementing that process, that provides A set of documents and/or products that describe the enterprise A common language and frame of reference for understanding and organizing that description, and A tool that both stores that information and assists the user in developing and analyzing that information
  • We facilitated the development of the CURE matrix relating the INS Business Activities to their data entities. We have even identified the “who” that performs the activity. This includes external organizations. In fact we will be supporting the EICMIM counter-terrorism project (which is adopting our products and methodology) to identify external data sources that will increase INS access to data. Applications are then groupings of business activities and data entities (simplistic view).
  • Service Area Domain Service Framework -       Presentation -       Business Logic -       Application Infrastructure -       Integration/Exchange Services -       Data Management   Service Platform -       Computing Platform -       Networking / Communications   Cross Cutting -       Security -       Management & Operations **   ** includes tools for Systems Assurance and Managed Systems management
  • At a high level, conceptual projects address the challenges and objectives outlined in the transition strategy. This “conceptual” sequence displays the approximate distribution of conceptual projects, required to meet the objectives.
  • The illustrated sequence diagram shows (above) applications and components that are implemented as part of conceptual projects over time. The horizontal axis contains the conceptual projects and the vertical axis displays phases and time. Projects are color coded to indicate the various objectives they address. The lines and arrows represent applications and components that use and consume other applications and components. Investments (300s) were aligned to conceptual projects using a “readily apparent” criteria. If an investment (300) appeared to have capabilities that were similar to the capabilities being enabled by a conceptual project it was aligned accordingly. One investment (300) can align to multiple conceptual projects.
  • The Homeland Security roadmap portrays, at a high-level, the conceptual projects and their sequence as shown on the detailed sequencing diagram.
  • Key Points: Page 13, National Strategy for Homeland Security How EA facilitates the Homeland Security Critical Mission Areas The EA will highlight and provide an understanding of the business and data to a level that will identify the appropriate policies and technologies to implement to support the needs of the homeland security mission.
  • Components in the DHS EA

    1. 1. Homeland Security Enterprise Architecture Intergovernmental Partnership Forum (IPF) Presented by: George Brundage January 6, 2004
    2. 2. Unprecedented Challenges <ul><li>Multiple stovepipes within stovepipes </li></ul><ul><li>Complex and diverse mission </li></ul><ul><li>Diverse set of merging cultures </li></ul><ul><li>Intense public scrutiny </li></ul><ul><li>Real time, dynamic situational awareness </li></ul><ul><li>Need to leverage valuable IT resources </li></ul><ul><li>Large decentralized resource footprint </li></ul>$37B Budget 22 Disparate Agencies and Entities Presence in 50 States 5 Directorates 177,000 Employees Integration of Civilian, Intelligence, Law Enforcement and Military Agency Components Coordination of DOE National Labs Engaging National Research Capabilities of University-Based Centers Creation of HSARPA Intel and Law Enforcement Communities State and Local Coordination Detect Prepare Protect Respond Recover Unprecedented Scale, Complexity, Scope, and Oversight!
    3. 3. DHS Mission <ul><li>Secure America against terrorist attacks; </li></ul><ul><li>Ensure an effective response in the event of crises and natural disasters; </li></ul><ul><li>Administer our immigration system; </li></ul><ul><li>Facilitate legitimate trade and travel; and </li></ul><ul><li>Guard the safety of America’s water ways. </li></ul>Identify threats to and vulnerabilities of the Homeland Manage Technology Manage Budget & Finances Manage Grants, Procurements, and Acquisitions Manage Human Resources Develop Policy Manage Knowledge and Intelligence Information “ Secure the Homeland, its People, Assets, and Interests” Manage Facilities and Property Respond to incident Recover from incident Perform Research and Development Develop Plans and Performance Measures Prepare for incidents Manage Legal Activities Prevent incidents Disseminate Information Facilitate the Flow of People and Goods
    4. 4. EA Overview <ul><li>Informed the FY05 budget formulation process (Phase I) and will impact the FY06 investments (Phase II) </li></ul><ul><li>Produced a conceptual-level Homeland Security EA </li></ul><ul><ul><li>Develop a business model for the newly formed Department </li></ul></ul><ul><ul><ul><li>Value Chain and Activities </li></ul></ul></ul><ul><li>Developed a realistic Transition Strategy </li></ul><ul><ul><li>Identify integration opportunities </li></ul></ul><ul><li>Incorporated State, Local, Tribal perspectives </li></ul>Baseline inventory of technology resources and business processes Technology Application Data Business “ As-Is” “ To-Be” Architecture “ Transition Plan” How to move the Enterprise toward the evolving “To-Be” state
    5. 5. HLS Enterprise Architecture Features <ul><li>Framework Driven </li></ul><ul><ul><li>Different views and perspectives – Zachman Framework and OMB Federal Enterprise Architecture Reference Models (FEA RMs) </li></ul></ul><ul><ul><li>Disciplined architecture process – Enterprise Architecture Planning (EAP), </li></ul></ul><ul><ul><li>which contributes to portfolio analysis, as defined in the Federal Enterprise Architecture Framework (FEAF) followed by other architecture analysis </li></ul></ul><ul><li>Model Driven </li></ul><ul><ul><li>Separates the business from the technology </li></ul></ul><ul><ul><li>Applications and components are derived from the business activities </li></ul></ul><ul><ul><li>Platform independent functional and service components </li></ul></ul><ul><li>Component-Based </li></ul><ul><ul><li>Isolates functionality </li></ul></ul><ul><ul><li>Contains multiple implementations to support many technology platforms </li></ul></ul><ul><ul><li>Promotes customization and personalization </li></ul></ul><ul><li>Solution Oriented </li></ul><ul><ul><li>Focus on the Target description </li></ul></ul><ul><ul><ul><li>Conceptual Projects (composed of applications and components) </li></ul></ul></ul>
    6. 6. Framework Based EA* * Based on Zachman EA Framework Strategy Schedule Organization Network Rule Specification Timing Definition Security Architecture Network Architecture Description Rule Design Control Structure Presentation Architecture Business Rule Model Processing Structure Human Interface Architecture Distributed System Architecture Focus Perspective Technology Architecture Function Data Program Data Definitions System Design Physical Data Model Logical Applications Architecture Logical Data Model Functioning Enterprise System Model (Logical) Designer Technology Model (Physical) Builder Detailed Representations (Out-of-context) Sub-contractor Performance Plans (Reference Model) Transition Strategy Organization Chart Workplace Environment& Location Conceptual Business Functions Conceptual Data Model Motivation Why Laws, Strategic Plans Time When Business Mandates People Who Major Organization Units Network Where Location Types Function How Mission & Focus Data What Scope (Contextual) Planner Enterprise Model (Conceptual) Owner Subject Areas
    7. 7. As-IS Baseline Framework Mission Areas Technology Application Data Business Information Security Readiness & Recovery Infrastructure Enterprise Solutions Intelligence Information Targeting Reduce vulnerability of the United States Prevent terrorist attacks Monitor illegal drug trafficking and terrorism Ensure economic security is not diminished by programs Ensure functions are not diminished or neglected Carry out all department functions Minimize damage and assist in attack recovery Focus Areas
    8. 8. Business Model Value Chain and Business Model Value Chain Business Model Value Stream Establish Credentials (HLS094) Categorize People and Things (HLS093) Examine People and Things (HLS010) Notification of Release Post Liquidated Entry List Trade Inspection Receive Non-appropriated Funds (HLS078) Identify threats to and vulnerabilities of the Homeland Manage Technology Manage Budget & Finances Manage Grants, Procurements, and Acquisitions Manage Human Resources Develop Policy Manage Knowledge and Intelligence Information “ Secure the Homeland, its People, Assets, and Interests” Manage Facilities and Property Respond to incident Recover from incident Perform Research and Development Develop Plans and Performance Measures Prepare for incidents Manage Legal Activities Prevent incidents Disseminate Information Facilitate the Flow of People and Goods
    9. 9. Data Architecture Conceptual Data Model Data Objects Communication Correspondence Outreach Content Warning Benefit Commercial Benefit Immigration Benefit Medical Benefit Relief Benefit Asset Capital Asset Critical Infrastructure Custodial Property Emergency Response Stockpile Incident Response Materials and Equipment Key Asset Law Enforcement Asset (Weapon) Operational Materials and Equipment Record Case Case Conveyances Conveyance Employment Employment Entitlement Position Skill Event Incident Occurrence Financial Resource Account Appropriated Fund Budget Non-Appropriated Fund Goods Cargo Governance Credential Mandate Location Physical Location Virtual Location Party Organization Person Plan Goal/Objective Performance Measure Plan Risk Threat Vulnerability Weapon Technology Applied Technology Information Technology Training Resource Training Exercise Training Material Agreement Contract Grant MOU
    10. 10. CURE Matrix Example <ul><li>CURE = “Create”, “Update”, “Reference”, or “Eliminate” </li></ul><ul><li>Relates the Business to the Data </li></ul>Conceptual Projects ------- Applications Components Data Activities Organization
    11. 11. Target EA Workflow Analysis Synthesis Target Architecture Business Model Conceptual Data Model Conceptual Projects/ Application Architecture Value Chain/Activities Data Subject Areas/Entities CURE First Cut Conceptual Projects/Applications Component Architecture Components Map Technical Patterns to Components Conceptual Projects/ Application Characteristics Technical Architecture Enhanced TRM Technology Patterns Geo-Technical Graphic
    12. 12. Application / Component Architecture Domain Independent Components (Data) Domain Specific Components (Activities) User Classes
    13. 13. Component Architecture <ul><li>Components </li></ul><ul><ul><li>A self contained business process or service with predetermined functionality that may be exposed through a business or technology interface </li></ul></ul><ul><ul><li>are independently deployable software units that integrate easily to compose larger systems-applications </li></ul></ul><ul><ul><li>may contain multiple implementations to support many technology platforms </li></ul></ul><ul><li>Each Component is characterized by: </li></ul><ul><ul><li>Support of business activities </li></ul></ul><ul><ul><li>Encapsulation of data objects and business rules </li></ul></ul><ul><ul><li>Consistency of services they offer </li></ul></ul><ul><ul><li>Ability to replace implementations </li></ul></ul><ul><ul><li>Extensibility of functionality </li></ul></ul>
    14. 14. Domain Independent Components <ul><li>Address </li></ul><ul><li>Alert Management </li></ul><ul><li>Application Processing </li></ul><ul><li>Background Checking </li></ul><ul><li>Case Management </li></ul><ul><li>Correspondence Management </li></ul><ul><li>Decision Support </li></ul><ul><li>Event Management </li></ul><ul><li>Geospatial Location </li></ul><ul><li>Global Positioning </li></ul><ul><li>Location Management </li></ul><ul><li>Organization </li></ul><ul><li>Outreach Management </li></ul><ul><li>Party Management </li></ul><ul><li>Pattern Matching </li></ul><ul><li>Person Identification </li></ul><ul><li>Person Information </li></ul><ul><li>Physical Location </li></ul><ul><li>Risk Management </li></ul><ul><li>Scheduling </li></ul>
    15. 15. Domain Specific Components <ul><li>Account Management </li></ul><ul><li>Asset Inventory </li></ul><ul><li>Background Checking </li></ul><ul><li>Budget Tracking </li></ul><ul><li>Compliance Management </li></ul><ul><li>Contract Administration </li></ul><ul><li>Credentialing </li></ul><ul><li>Custodial Property Administration </li></ul><ul><li>Domestic Licensing </li></ul><ul><li>Employee Benefits </li></ul><ul><li>Employee Management </li></ul><ul><li>Evidence Management </li></ul><ul><li>Facilities Management </li></ul><ul><li>Financial Accounting </li></ul><ul><li>Funds Receipt Management </li></ul><ul><li>Import Declarations </li></ul><ul><li>Import Export Documentation </li></ul><ul><li>Import Export Licensing </li></ul><ul><li>Incident Tracking </li></ul><ul><li>Investment Management </li></ul><ul><li>Logistics Management </li></ul><ul><li>Mandate Administration </li></ul><ul><li>Payment Processing </li></ul><ul><li>Payroll </li></ul><ul><li>Physical Property Management </li></ul><ul><li>Proposal Management </li></ul><ul><li>Records Management </li></ul><ul><li>Seized Property </li></ul><ul><li>Tracking </li></ul><ul><li>Travel Document Management </li></ul>
    16. 16. Application Architecture <ul><li>Applications </li></ul><ul><ul><li>are enablers of business workflows within the enterprise </li></ul></ul><ul><ul><li>are structured of smaller independent functional parts called components </li></ul></ul><ul><ul><li>components are assembled to achieve overall application functionality </li></ul></ul><ul><li>Each Application is characterized by: </li></ul><ul><ul><li>Workflow that it supports </li></ul></ul><ul><ul><li>User Classes </li></ul></ul><ul><ul><li>Components comprising the applications </li></ul></ul>
    17. 17. Applications <ul><li>Command and Control Center </li></ul><ul><li>Communications Management </li></ul><ul><li>Contract and Acquisition Management </li></ul><ul><li>Detainee Management </li></ul><ul><li>Financial Management </li></ul><ul><li>Geographic Information Systems </li></ul><ul><li>Grants Management </li></ul><ul><li>Homeland Security Collaboration Zone </li></ul><ul><li>Immigration Request Management </li></ul><ul><li>Incident Response Management </li></ul><ul><li>Intelligence Analysis Toolset </li></ul><ul><li>International Trade Management </li></ul><ul><li>Investigation Management </li></ul><ul><li>Legal Activities Management </li></ul><ul><li>Non-US Citizen Stay Status Management </li></ul><ul><li>Personnel and Payroll Management </li></ul><ul><li>Physical Security Management </li></ul><ul><li>Planning and Performance Management </li></ul><ul><li>Port of Entry/Exit Management </li></ul><ul><li>Property Management </li></ul><ul><li>Public Relations Management </li></ul><ul><li>Removals Management </li></ul><ul><li>Research and Development Administration </li></ul><ul><li>Technology Management </li></ul><ul><li>Water Navigation Management </li></ul>
    18. 18. Homeland Security Collaboration Zone Homeland Security Collaboration Zone Application Collaborate/ Coordinate w/ Federal, State, Local Governments, and Private Sector Goal/ Objective Outreach Content Plan Occurence Correspondence Organization Performance Measure Person Incident Tracking Party Management Mandate Administration Compliance Management Outreach Management Alert Management
    19. 19. Technical Architecture What are Patterns? <ul><li>Reusable generalization (or abstraction) that can be used as a solution to a repeating problem in a specific context </li></ul><ul><li>Encapsulation of particular knowledge collected from experience in a domain </li></ul><ul><li>Architectural-level patterns that define best practices in architectural design to address specific technology issues or objectives </li></ul>
    20. 20. Technical Architecture Application Patterns Application Control Interface Service Component Service Component Service Component Portal Personalization Pervasive Device Support Content Management Broker Decomposition Router Agent Workflow/BPM Rules Engine Integration/ Interoperability Business Intelligence/ Data Warehouse Data Access Application Configuration Pattern: N-Tier, Dynamic Web Primary Patterns Web Services Message-Oriented Middleware Secondary Patterns Pattern Matching Security Performance and Reliability Cross-Cutting Patterns Collaboration Asynchronous Access
    21. 21. Technical Architecture Patterns/Technical Reference Model/Standards Profiles Enterprise Reporting Tools Metadata Services Data Access Services DBMS Data Transformation Services Structured Telephony Computer Hardware NOS Enterprise Storage Shared Special Purpose Hardware Operating System End User Special Purpose Hardware Web Portal GIS Server Web Servers and Plug-ins CRM/Helpdesk Server Search Engines Application Server Transaction Processing Server Mail Server Collaboration Server Enterprise Application Integration Inter-application Messaging Services Web Services Directory Services Narrowband Wireless Remote Access LAN Broadband Wireless WAN Desktop Interface GIS Client Software Terminal Emulators Web Clients Pervasive Device interfaces Collaboration Client Narrow Band Wireless Access Office Suite CRM/Helpdesk Client Document Management Access Control Cryptography Security Operation Network Security Applications and System Security Physical Security Program Management Tools Development Tools SA Tools Network Admin Tools Operations Management Tools Release Management Tools Content Management Office Suite CRM Agent Business Intelligence Components Workflow Server Mission Specific Application Components Rules Engine N-Tier Dynamic Web Application Architecture Pervasive Device Support Portal - Personalization - Content Management Workflow / Business Process Management Broker - Decomposition - Router - Agent Business Rules Engine Integration and Interoperability - Web Services - Message Oriented Middleware Business Intelligence / Data Warehouse - Pattern Matching Data Access - Asynchronous Access Collaboration Security Performance and Reliability Presentation Layer Business Logic Application Infrastructure Integration Services Data Management Computing Platform Network Communications Maintenance and Operations Security
    22. 22. Transition Strategy Proposed Sequence <ul><li>Conceptual projects and their associated capabilities are enabled over time </li></ul><ul><li>Classifications of conceptual projects – Different Colors </li></ul><ul><li>Rationalize – Understand what must be done/Move on the Quick Hits </li></ul><ul><li>Stabilize – Begin to roll out consolidated projects/Do no harm/Start to make changes while the car is moving </li></ul><ul><li>Optimize – Create the vision through a series of releases adding capabilities </li></ul>Chart Displays, at a High-level, the Sequence of the types of Conceptual Projects As Shown on the Detailed Sequence Diagram
    23. 23. Transition Sequence Diagram <ul><li>Conceptual Projects Enable Specific Components And Applications (Positioned In Swim Lanes) </li></ul><ul><li>The Phases Are On The Vertical Axis. The Color Of Each Project Visually Relates The Project Back To The Objective It Addresses </li></ul>
    24. 24. Transition Strategy Enterprise Architecture Roadmap
    25. 25. EA as an Enabler of the National Strategy for Homeland Security <ul><li>Business Architecture </li></ul><ul><ul><li>Identify common activities that facilitate the collaboration and exchange of homeland security information </li></ul></ul><ul><ul><li>Implement policy related to the homeland security community </li></ul></ul><ul><li>Data Architecture </li></ul><ul><ul><li>Identify and adopt common “meta-data” standards for electronic information relevant to homeland security </li></ul></ul>Intergovernmental Coordination - … the Department of Homeland Security will simplify the process which governors, mayors, and county leaders interact with the federal government. Technology Architecture Application Architecture Data Architecture Business
    26. 26. Information Sharing Architecture Common Applications Storage Collaboration DHS Internal Space DHS Shared Space Community Space Organizational Shared Applications Organizational Shared Data F I R E W A L L Full Service Directory Webmail LAN F I R E W A L L Local Directory Servers Workstations Private Data Conversion
    27. 27. Application Solution Framework Infrastructure
    28. 28. DHS EA Mapping to Federal Guidance Baseline (“As Is”) (Legacy) DHS Technical Reference Model Patterns, Standards and Products Target (“To Be”) (Modernization) Clinger-Cohen Act, PRA, GPRA, Chief Financial Officers Act, OMB Circular A-130 Federal Reference Models PRM BRM TRM Desired Outcomes Business Needs SRM Department of Homeland Security Strategic Plan Business Results Process Customer People Technology President’s National Strategy for Homeland Security Services To Citizens Support Delivery of Services Management of Government Resources Department of Homeland Security Mission and Support Areas Facilitate Flow of People & Goods Prevent Incidents Disseminate Information Prepare for Incidents Respond to Incidents Recover from Incidents Identify Threats & Vulnerabilities Homeland Security Conceptual Data Model DRM Homeland Security Target Architecture Target Applications Service and Component Architecture
    29. 29. FEA BRM (FBRM) Alignment <ul><li>Each activity in the DHS Business Model maps to at least one sub-function of the FBRM </li></ul>DHS Business Activities FBRM Sub-Functions <ul><li>Applying the FBRM </li></ul><ul><li>Identified relationships to 23 Lines of Business in the FBRM </li></ul><ul><li>Identified relationships to 71 FBRM sub-functions </li></ul><ul><li>Identified budget requests that support duplicative business functions </li></ul><ul><li>Work with other Federal Agencies, State and Local Governments to improve the Homeland Security & Disaster Management Business Lines </li></ul>Technology Architecture Application Architecture Data Architecture Business
    30. 30. Aligning HLS Data to the DRM <ul><li>Used Zachman’s approach to stage development of HLS Data Architecture </li></ul><ul><ul><li>Subject Areas (17) </li></ul></ul><ul><ul><li>Data Objects (48) </li></ul></ul>Data Data Definitions Physical Data Model Logical Data Model Perspective Functioning Enterprise Designer Builder Sub-contractor Conceptual Data Model Data What Owner Subject Areas Planner Business Objects XML Specs Entity-Relationships Enterprise Data Dictionary Data Flow Diagrams Technology Architecture Application Architecture Data Architecture Business
    31. 31. Aligning HLS Applications to the SRM <ul><li>The HLS Application Architecture is constructed to leverage reusable components </li></ul><ul><li>Applying the SRM </li></ul><ul><li>Identified 5 component architecture layers </li></ul><ul><li>Business components defined by HLS activities, data, and user classes </li></ul><ul><li>Structured EA Application Architecture as a set of internetworking components that tie back to the SRM </li></ul><ul><li>Applied a technology patterns approach that is derived from the technology aspects of the SRM </li></ul>*Number of HLS Applications and Components to the FEA Service Types Technology Architecture Application Architecture Data Architecture Business DHS Business and Technology Components SRM Service Types and Components
    32. 32. Aligning the HLS TRM to the FEA TRM DHS TRM Tier 3 FEA TRM <ul><li>Applying the TRM </li></ul><ul><li>Incorporates the taxonomy, technical services, protocols and interfaces </li></ul><ul><li>Extended and refined to reflect additional functional and technical requirements </li></ul><ul><li>Adjusted technology categories </li></ul>Technology Architecture Application Architecture Data Architecture Business
    33. 33. Performance Reference Model <ul><li>Application of PRM accomplished by those in the best position </li></ul><ul><ul><li>Specific and established programs </li></ul></ul><ul><ul><li>Supports line of sight from business through technology </li></ul></ul><ul><li>EA has best appreciation of how line of sight aligns with OMB, HLS, and DHS goals and objectives </li></ul><ul><li>EA provides guidance that can be used by programs to develop (tailor) specific performance measures </li></ul>Technology Technology Strategic Outcomes Value Customer Results • Customer Satisfaction • Service Coverage • Timeliness & Responsiveness • Service Quality • Service Accessibility Customer Results • Customer Satisfaction • Service Coverage • Timeliness & Responsiveness • Service Quality • Service Accessibility Processes and Activities • Financial • Productivity and Efficiency • Cycle and Resource Time Processes and Activities • Financial • Productivity and Efficiency • Cycle and Resource Time • Quality • Management & Innovation Technology • Financial • Quality & Efficiency • Information & Data • Reliability & Availability • User Satisfaction Technology • Financial • Quality & Efficiency • Information & Data • Reliability & Availability • User Satisfaction Other Fixed Assets • Financial • Quality, Maintenance, & Efficiency • Security & Safety • Utilization Other Fixed Assets • Financial • Quality, Maintenance, & Efficiency • Security & Safety • Utilization People • Employee Satisfaction & Quality of Worklife • Recruitment & Retention • Employee Development • Employee Ratios People • Employee Satisfaction & Quality of Worklife • Recruitment & Retention • Employee Development • Employee Ratios Mission and Business Results • Services for Citizens • Support Delivery of Services • Management of Government Resources • Financial Mission and Business Results • Services for Citizens • Support Delivery of Services • Management of Government Resources • Financial
    34. 34. Version 1.0 Statistics <ul><li>Length: 4 Months </li></ul><ul><ul><li>May 2003 through Sept 2003 </li></ul></ul><ul><li>People/Groups involved: </li></ul><ul><ul><li>CIO’s office </li></ul></ul><ul><ul><ul><li>Applied Technology Board; EA Team </li></ul></ul></ul><ul><ul><li>DHS Architecture Working Group </li></ul></ul><ul><ul><ul><li>Directorates Represented: S&T, IAIP, CBP, ICE, EP&R, TSA, FLETC </li></ul></ul></ul><ul><ul><ul><li>Organizational Elements Represented: USSS, USCG; CIS </li></ul></ul></ul><ul><ul><ul><li>Mitre </li></ul></ul></ul><ul><ul><li>Financial / Resource Management </li></ul></ul><ul><li>Business Model </li></ul><ul><ul><li>Activities: 80 </li></ul></ul><ul><ul><li>Workplace Types: 15 </li></ul></ul><ul><ul><li>Work Zones: 4 </li></ul></ul><ul><li>Target Enterprise Architecture </li></ul><ul><ul><li>Data </li></ul></ul><ul><ul><ul><li>Subject Areas: 17 </li></ul></ul></ul><ul><ul><ul><li>Data Objects: 47 </li></ul></ul></ul><ul><ul><li>Application </li></ul></ul><ul><ul><ul><li>Applications: 25 </li></ul></ul></ul><ul><ul><ul><li>Reusable Components: 66 </li></ul></ul></ul><ul><ul><li>Technology </li></ul></ul><ul><ul><ul><li>Technology Patterns: 12 </li></ul></ul></ul><ul><ul><ul><li>Technical Reference Model Technology Categories: 60 </li></ul></ul></ul><ul><li>Transition Strategy </li></ul><ul><ul><li>Conceptual Projects: 29 </li></ul></ul>
    35. 35. FY04 Plans <ul><li>Outreach </li></ul><ul><ul><li>Briefed the Hill, Deputy Secretary and Under Secretaries </li></ul></ul><ul><ul><li>Briefed the staff of the Undersecretary for Management </li></ul></ul><ul><ul><li>Raise awareness of the EA and its products within DHS </li></ul></ul><ul><ul><li>Provide EA consulting to on-going efforts </li></ul></ul><ul><ul><ul><li>US-VISIT and other priority mission investments </li></ul></ul></ul><ul><ul><ul><li>Financial/Resource Management </li></ul></ul></ul><ul><ul><ul><li>FY04 conceptual projects identified in the transition strategy </li></ul></ul></ul><ul><li>Engage Business Units (DHS and external partners) </li></ul><ul><ul><li>Vet the Transition Strategy </li></ul></ul><ul><ul><li>Develop more granular business and data architectures </li></ul></ul><ul><li>Mature the EA </li></ul><ul><ul><li>Add greater detail to all EA models </li></ul></ul><ul><ul><li>Develop a Transition PLAN </li></ul></ul><ul><li>Define and establish EA Governance </li></ul><ul><ul><li>Integrate with existing and evolving DHS processes (e.g., strategic planning, capital planning, budgeting) </li></ul></ul><ul><ul><li>Integrate with CIO disciplines (e.g., infrastructure, systems development) </li></ul></ul>

    ×