Project Management COE Helen Schmitz, Chief IT Architect (Acting) June 10, 2009

Project Management COEHelen Schmitz, Chief IT Architect (Acting)

June 10, 2009

Website: http://EnterpriseArchitecture.nih.govContact: [email protected] Page 2

Agenda

• What Enterprise Architecture (EA) is• The components and how they are used• What we do• How to work with us


What is Enterprise Architecture?


What is Enterprise Architecture?

• “Enterprise Architecture is the strategic plan & design for IT.”

• “Enterprise Architecture at the NIH uses technology to extend the capability of the NIH to save lives. It creates a holistic vision or model of systems, processes and components to ensure that they interoperate like the different systems in a healthy body.”

– EA elevator speeches created by members of the Office of the Chief IT Architect (OCITA),12/04/2006


NIH Enterprise ArchitectureMission and Vision

• Mission– To develop a comprehensive plan for IT support at the NIH which

acknowledges the need for both conforming and diverse business processes.

• Vision– The National Institutes of Health (NIH) Enterprise Architecture (EA) will

enable efficient business processes and information access for all NIH Institutes and Centers (IC) by providing the necessary:

• Common models • Frameworks• Standards

– by which to build and plan:• Shared NIH enterprise systems• A secure and robust core IT infrastructure.


Enterprise Architecture is Analogous to City Planning

- Supports the mission - Long range- Over-arching - Can be modified

City Planning Enterprise Architecture

City Council IT Working Group (ITWG)

Zoning Board Architecture Review Board (ARB)

Master plans Business models and conceptual data models

Utilities Common infrastructure

Building Application

Building Code Standards & Interfaces

Building Permit Process

Exception Process

L’Enfant’s Plan of Washington DC (1791)


What are the Benefits of EA?

The overall NIH Enterprise Architecture offers many benefits to the enterprise. These desired benefits, along with Federal regulations and legislation, drive the development of the enterprise architecture program.

The six most important benefits include:1. Links information technology (IT) to the mission of

NIH2. Improves interoperability and integration3. Enables agility4. Reduces costs5. Improves security 6. Reduces technical risk


NIH Enterprise ArchitectureFramework

Used to structure the EA effort and to classify the EA components:– Business Architecture– Information Architecture– Technology Architecture

Architecture is a process, not a one-time event


Business Architecture

» You can understand how important and common activities are completed at NIH.

» You don’t need to redefine or discover the process for the same or similar activities

» You are defining requirements for a new IT project.

» You are planning revisions to existing application.

» IT project managers» “Business people”

working closely with leadership and ground level operations.

Why it matters ... when ... and you are ...

Activity Actor Asset Time Location

using which resources ...Who does what ... when and where.

Activities are supported by Application Assets are generalized and defined as Data Models


Value of HPSD-12 Personal Identity Verification (PIV) Business Process Models

New PIV Application

INITIATION

1.ANIH Badged Applicant(Non-PIV)

1.B.1FTE

1.B.2Contractor

1.B.3Non-FTE

1.B.4Summer Employee

2.0Sponsor NIHApplicant

3.0 Determine Investigation Requirement

4.0Perform Pre-RegistrationActivities

6.0Register Applicant

5.0Initiate PersonnelSecurity Investigation8.0AdjudicatePersonnel SecurityInvestigation

7.0AdudicateSpecial Agreement Check

9.0Perform Pre-IssuanceActivities

10.0Issue NIH PIVCard11.0Issue Parking Permitand Transhare

12.0EstablishPhysical Access

SecurityAwarenessTrainingand Assign ITAccountsAssign NIHPhysicalResources & Services

X/OR

AND

AND

Establish ITASand EHRPProfiles

SPONSORSHIP ENROLLMENTADJUDICATION ISSUANCE ACTIVATION O & M

OPM

OPM

X/ORAppealsProcess AND

AppealsProcess

X/OR

AND

13.0RevokePIV Badge

14.0Renew

LEGEND

IndividualApplicant AdministrativeOfficer(AO)DPSAC IT Administrator & ISSODPSACand AO

Outside ProcessSync orInformationSourceAND

Inclusive And: Process must flow in all possible connected paths simultaneously

AND/OR

Inclusive And/Or: Process may flow in one or many of possible connected pathsExclusive Or: Process must flow in one and only one of possible connected paths

X/OR

Indicator of Level III How Model

1

Other ActorsNot Specified

End Process

AND/OR If no PSI on record or inadequate

If PSI on record and adequate

Unfavorable SAC Adjudication

10.1Update Facial Image

Sub-Process

15.0Reissue

Results<= 5 daysReceive SAC

Submit NAC(Fingerprints)

1.B.5NED Record Activation Process

Version 52_08.23.07

Applicant/DPSAC

Terminate

• Provides view of end-to-end NIH Personal Identity Verification (PIV) business process

• Identifies and communicates roles are responsibilities to all stakeholders

• Shows integration with/linkages to existing NIH people processes

• Provides functional requirements for IT PIV support system design

• Establishes an agreed upon baseline from which to manage future changes

• NIH HSPD-12 models used to brief Congress on the value of business process models


Information Architecture

» You can identify existing design for all or part of your system.

» You can understand environment around you, and participate in the enterprise plan.

» You can achieve efficiency at the global level.» You can share data more easily because

data are represented in standardized way.

» You are making decisions about how to manage information to maximize its value to NIH.

» You are defining technical design specification.

» You are working through the detailed design.

» Business owners of Information

» Technology stewards (CIOs, and others)

» IT project managers» Solution architects


by standardized representation of data ... and relate to each other.

Application Data Model Integration


Data ArchitectureNIH Enterprise Conceptual Data Model


Technology Architecture

Applications relate to each other ... and are supported by infrastructure.

Pattern Brick

User contribution enhances the overall content.Com

mun

ity C

onte

nt

Best Community PracticeCase StudiesSample Code and Technical DocumentationVendor Documentation

» You don’t need to spend time figuring out viable technical components and solutions used at NIH now and in the future.

» You can reduce time and improve quality of proposal.

» You can reduce variants in solutions, and save money on development and training.

» You are selecting a specific technical components to support the design.

» Solution architects» Developers and

designers» Contractors



How Standards are Developed

Domain Team process• http://enterprisearchitecture.nih.gov/About/Appro

ach/DomainTeamProcess.htm

NIH Request for Comments (NIHRFC) • http://enterprisearchitecture.nih.gov/About/Appro

ach/NRFC.htm

http://enterprisearchitecture.nih.gov/About/Approach/DomainTeamProcess.htm

http://enterprisearchitecture.nih.gov/About/Approach/DomainTeamProcess.htm

http://enterprisearchitecture.nih.gov/About/Approach/NRFC.htm

http://enterprisearchitecture.nih.gov/About/Approach/NRFC.htm


Technology ArchitectureArtifacts

• PatternsDesign ideas that can be reused and leveraged

across NIH.

Example: http://enterprisearchitecture.nih.gov/ArchLib/AT/TA/NIHFederatedIdentityPattern.htm

• BricksNIH standards that specify products, technologies, or

protocols in use or planned, as well as those earmarked to be retired or contained.

Example: http://enterprisearchitecture.nih.gov/ArchLib/AT/TA/NIHFederateIdentityAuthenticationAuthorization.htm

The Enterprise Architecture Program has established 61 bricks and 50 patterns to date through the NIH EA standards process.


Technology Transformations

OCITA has coordinated the implementation and planning of innovative technologies and handed them off to CIT to manage for O&M.– NIH Login– Service Oriented Architecture (SOA)– Business Process Management software– Federated Authentication


Current Integration Service Center Web Services

ISC Web Service Usage

0

20000

40000

60000

80000

100000

120000

140000

Oct07

Nov07

Dec07

Jan08

Feb08

Mar08

Apr08

May08

Jun08

Aug08

Sept08

Oct08

Nov08

Dec08

Jan09

Feb09

Mar09

Apr09

May09

Month

Serv

ice

Invo

catio

ns

SendWordNow

Other

Ned Person

POservices

LookupProjects

CheckFunds

Create Requisition

Security Training

Commons Person


What does OCITA do?

• Defines EA Components – Standards, models, designs, plans and governance to support

them– Provides a library of: Bricks/patterns, published NIHRFCs,

business process models, data models, case studies, and more• Provides consultative advice

– Provides advice and guidance to PMs at the concept and design stage of the project to ensure solid architectural decisions

– Validates alignment to existing infrastructure• Ensures EA is available to anyone at anytime and is

easy to use


How can OCITA help me?

• What will OCITA do for me?– Communicate to project teams the EA products that will be useful

to you– Provide information about similar systems or services that can be

of use– Provide guidance on data and business processes that should be

used

• When should I contact OCITA?– If you are creating a new system or updating the current system

• At the concept stage of an IT project• At the design stage of an IT project

– If you have a system you are modifying which requires data from other ICs or other systems

– If you are putting out an RFP/RFC


Contact Information

• Website: http://EnterpriseArchitecture.nih.gov• The NIH Enterprise Architecture Community in

the NIH Portal• Email: [email protected]• Subscribe to the EA LISTSERV:

http://list.nih.gov/archives/enterprise_architecture.html• Integration Service Center Website:

http://isc.nih.gov

http://enterprisearchitecture.nih.gov/

mailto:[email protected]

http://list.nih.gov/archives/enterprise_architecture.html

http://isc.nih.gov/

Documents

Project Management COE Helen Schmitz, Chief IT Architect (Acting) June 10, 2009