1 / 28

CBP IT Enterprise Architecture

CBP IT Enterprise Architecture. Brian Burch Information Management Subcommittee September 16, 2003. Topics. Architecture Example Definitions Approach Framework. ARCHITECTURE EXAMPLE: Winchester House. Winchester House. Sarah Winchester 22 million inheritance

halden
Download Presentation

CBP IT Enterprise Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CBP IT Enterprise Architecture Brian Burch Information Management Subcommittee September 16, 2003

  2. Topics • Architecture Example • Definitions • Approach • Framework

  3. ARCHITECTUREEXAMPLE: Winchester House

  4. Winchester House • Sarah Winchester • 22 million inheritance • Psychic – move west, build to keep spirits away • 38 years of continuous construction (1884-1922) • 22 full time carpenters • Architectural “marvel” • 160 rooms (40 bedrooms, 6 kitchens) • 40 staircases • 47 fireplaces • 1200+ windows, 900+ doors • Blueprints • None! • Sarah sketched out individual rooms on paper, napkins and even tablecloths

  5. Result

  6. Result

  7. Current Operating Mode • Much like Winchester House: • Continually building (since mid-80’s) • Functional products (rooms) • Blueprints for individual products • Often individual blueprints don’t consider big picture

  8. Results • Operational individual products • Issues: • No overall blueprint • Duplicative applications, databases • Limited metadata • Don’t know how/if systems fit together

  9. DEFINITIONS

  10. Enterprise • Enterprise is CBPO and partners • Unique, complex FEDERAL EA’S STATE EA’S CBP EA

  11. Enterprise • Requires strong partnerships • Revisit/revise MOA’s • Revisit IMS membership • Requires commitment to enterprise • Benefits to enterprise • Remove state dual submissions • Implementation of distributed systems • Data managed once in enterprise, shared • Reusable components/code

  12. Architecture • Blueprint • High-level • Comprehensive • Key concepts • Based on business practices • Technology not driver, but implementer

  13. Enterprise Architecture • Architecture • Evolves as business changes • Key concepts of Architecture • No major changes • Ex. distributed systems, metadata

  14. APPROACH

  15. Approach • Evaluate other architecture efforts • OMB Federal Enterprise Architecture • EPA Target Architecture • Develop an operational framework for the architecture

  16. Other Efforts • Office of Management and Budget • Federal Enterprise Architecture (FEA) • Reference models • Performance Reference Model (PRM) • Business Reference Model (BRM) • Service Component Reference Model (SRM) • Data Reference Model (DRM) • Technical Reference Model (TRM)

  17. Other Efforts • EPA – Target Architecture • Enterprise Architecture • Approach, practice and proposed policy, principles and drivers • Strategic Architecture (C2K) • Business Domain Architectures • Environmental Health & Protection • Administrative Systems • Component Architectures • Geospatial Blueprint • Security Architecture • Technology Architecture • Technical Reference Model • Sequencing Approach

  18. Framework for Architecture • Business model • Current Architecture (CA) • Limitations of CA/Drivers • Target architecture (TA) concepts • TA governing policies, practices • Implementation plan

  19. Business • Define our business • C2K, Keystone Commitments, FEA, EPA • Business functions (monitor, analyze, etc.) • Detail our organizational structure

  20. Current Architecture • Document databases • Document data flows • Document technologies • Document applications • Map data to technology, data to application, technology to application

  21. LOGIC LOGIC LOGIC DATA DATA DATA INTERFACE INTERFACE INTERFACE Current Architecture APPLICATIONS: PARTNERS: WEB-BASED MDDNR CBPO STANDALONE PADEP NETWORKED SUBMISSIONS EPA VADEQ APPLICATIONS: APPLICATIONS:

  22. Limitations/Drivers • Limitations of current architecture • Not scaleable • Not distributed • Limited documentation • Proprietary technologies • Process improvements • Inefficient practices

  23. Key Concepts • Integrated data and application • Partner information exchange • CBP and national data streams • GIS and relational databases • Web navigation • CBP databases • Code libraries • Standards-based architecture • Ontological information organization • Non-proprietary data delivery system • Metadata: Infrastructure, content, registry • Common standards and data dictionaries • Standard information modeling techniques • Role-based resources • Task specific hardware/software • Multi-tier services development model • Developer specialties • Component-based resource deployment

  24. Target Architecture? APPLICATIONS: PARTNERS: MDDNR L O G I C M E T A D A T A INTERFACE CBPO RETRIEVAL INTERFACE PADEP RETRIEVAL INTERFACE EPA CDX VADEQ

  25. Governing Principles, Practices • Project plans • Role-based approach • CIMS standards • Project management techniques • Firm partnerships

  26. Related Activities • Strategic Plan for CIMS 2005 • Objectives: • Integrated Data and Application • Standards-based Architecture • Role-based Resources • Goals: • Reengineer CBP Website into reusable components • Develop a standardized navigational model • Institutionalize data processing algorithms • Spatially enable CBP relational databases • Expand use of metadata • Improve organization of database infrastructure

  27. Keys to Success • Robust, cooperative partnerships • Recognition of benefits

  28. QUESTIONS?

More Related