CBP IT Enterprise Architecture

Brian BurchInformation Management Subcommittee

September 16, 2003

Topics

■ Architecture Example■ Definitions■ Approach■ Framework

ARCHITECTUREEXAMPLE:

Winchester House

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

Result

Result

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

Results

■ Operational individual products■ Issues:

► No overall blueprint► Duplicative applications, databases► Limited metadata► Don’t know how/if systems fit together

DEFINITIONS

Enterprise

■ Enterprise is CBPO and partners■ Unique, complex

FEDERALEA’S

STATEEA’S

CBPEA

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

Architecture

■ Blueprint■ High-level■ Comprehensive■ Key concepts■ Based on business practices■ Technology not driver, but implementer

Enterprise Architecture

■ Architecture► Evolves as business changes

■ Key concepts of Architecture► No major changes► Ex. distributed systems, metadata

APPROACH

Approach

■ Evaluate other architecture efforts► OMB Federal Enterprise Architecture► EPA Target Architecture

■ Develop an operational framework for the architecture

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)

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

Framework for Architecture

■ Business model■ Current Architecture (CA)■ Limitations of CA/Drivers■ Target architecture (TA) concepts■ TA governing policies, practices■ Implementation plan

Business

■ Define our business► C2K, Keystone Commitments, FEA, EPA► Business functions (monitor, analyze,

etc.)► Detail our organizational structure

Current Architecture

■ Document databases■ Document data flows■ Document technologies■ Document applications■ Map data to technology, data to

application, technology to application

Current Architecture

MDDNR

PADEP

VADEQ

CBPO

EPA

SUBMISSIONS

DATALOGIC INTERFACE

DATALOGIC INTERFACE

DATALOGIC INTERFACE

WEB-BASED

STANDALONE

NETWORKED

APPLICATIONS:

APPLICATIONS:APPLICATIONS:

PARTNERS:

Limitations/Drivers

■ Limitations of current architecture► Not scaleable► Not distributed► Limited documentation► Proprietary technologies► Process improvements► Inefficient practices

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

Target Architecture?

MDDNR

PADEP

VADEQ

CBPO

EPACDX

RETRIEVAL

INTERFACE

INTERFACE

INTERFACE

APPLICATIONS:PARTNERS:

RETRIEVAL

LOGIC

METADATA

Governing Principles, Practices

■ Project plans■ Role-based approach■ CIMS standards■ Project management techniques■ Firm partnerships

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

Keys to Success

■ Robust, cooperative partnerships► Recognition of benefits

QUESTIONS?