What s What Ahead For Architectures in the DoD? Mr. Dav Da e v DeVr DeV ies Mr. Martin Westphal

(1)

What’s Ahead For

Architectures

What’s Ahead For

Architectures

in the DoD?

Architectures

in the DoD?

Mr Dave DeVries

Mr.

Dave

DeVries

Mr.

Martin

Westphal

(2)

What Has Happened

• Organization

changes

and

declining

budgets

• _Progress

_made

_in

• Electronic

Health

Record

• Data

Center

Consolidation

• Revised JCIDS and NR KPP policy

• Revised

JCIDS

and

NR

KPP

policy

• Agile

IT

Acquisition

reform

• Joint

Information

Environment

(JIE)

Engagement

• FMN

Framework

(3)

What We Have Heard This Week

• Secure

Information

Sharing

g

with

Mission

Partners

• _{Interoperability}

• _Data

• Securityy

• _Identity

_Management

_and

_Access

_Management

Th

P

i

(O

PfM

A hi

)

• Three

Perspectives:

(Operator,

PfMgmt,

Architect)

(4)

DoD Enterprise

DoD

Enterprise

Business

Warfighting

Intelligence

Business

Warfighting

Intelligence

Information Enterprise Architecture

g

te ge ce

Enabling Information Enterprise

g

te ge ce

Dept

of

Air

Force

C

OMS

DIS

A

DLA

NSA

NR

O

NGA

DIA

Army

DON

Air

Force

Information Enterprise Architecture

DoD

IEA

v2.0

Dept

of

Air

Force

C

OMS

DISA

DLA

NSA

NRO

NGA

DIA

Army

DON

Air

Force

Enabling Information Enterprise

DoD

IEA

v2.0

CO

C

CO

C

4 Tech

Stds

DISR

Arch

Guidance

DODAF

Reference

Models

OMB

FEA

Laws,

Regs,

and

Policy

Laws

Regs

Policy

Tools

DITPR

DARS

4 Tech Stds

DISR

Arch Guidance

DODAF

Reference

Models

OMB

FEA

Laws, Regs, and Policy

Laws

Regs

Policy

Tools

DITPR

DARS

(5)

Partnering for Success

Joint

Staff

DoD

CIO

DoD Mission Areas

Warfighting

Business

C/S/A

Intelligence

C/S/A

_IC

(6)

JC2 Objective Architecture Efforts

Data Cloud Services

• Redirection

• Dynamic allocation

• C2 services integration with ESM

Enterprise Services

• E2E security services

E2E f d

ti

f

•Crypto Binding

• REST Security

• E2E federation of messages

• Unified approach for mediation

• Federated Collaboration

• Widget Framework

Further define

Info Exchange

Patterns

Data Cloud

• Data sync &

Cross Domain

access control &

info exchange

(non-DoD partners)

Data sync &

distribution

• Federation

• Caching

(7)

DI2E

Architectures

(8)

Architecture

Architecture –

– Driving Change

Driving Change

Presentation

(Common GUI)

Presentation

Common DoD-VA Requirements: HL7 EHR-S Functional Model with DoD and VA vetted Extensions (SV-4)

Common DoD-VA Integrated Health Business Reference Model (OV-5)

Common DoD-VA “To Be” Process Flow Model (OV-6C)

(Common GUI)

Presentation

Layer Team

Systems

Capabilities

Pharmacy

Health Record

Personal

Laboratory

Nursing

Home

Long Term

Care

DoD Unique (16)

Common (Joint) Applications & Services (30)

VA Unique (6)

Battlefield

Care

Pediatrics

Blood Mgmt

Applications and Services

Common Interface Standards

p

Team

Mission

Requirements

& Performance

Outcomes

Team

Disability

Evaluation

Dental Care

Inpatient

Orders Mgmt

Consult &

Referral Mgmt

Immunization

Emergency

Dept Care

Rehabilitative

Care

Transient

Outreach

Military

Readiness

Obstetrics

Enroute

Care

Veterinary

Operating

Room Mgmt

Document

Mgmt

Occupational

Health (VA)

Pharmacy

Mail Order

Common Interface Standards

Co

o

te ace Sta da ds

C

D t C t

Common Services Broker

(includes Enterprise Service Bus (ESB) and Infrastructure Services)

Enterprise

Architecture

Team

Business

Process

Common Data Centers

Data

Inter-operability

Team

Common Information Interoperability Framework (CIIF)

Common Information Model, Common Terminology Model,

Information Exchange Specifications, Translation Service

C

D t St d d SNOMED CT d E t

i

LOINC d R N

8 Common Data Standards: SNOMED CT and Extensions, LOINC and RxNorm

DoD Only

VA Only

Joint DoD/VA

(9)

iEHRWF

iEHRWF Potential Architecture

Potential Architecture

cmp ESB Interface

Clinical Serv ices

Behavioral Health Services

Inpatient Surgery Sevices

Outpatient Surgery

Services Labor and Delivery Primary Care Services Laboratory Services Pathology Services

iEHRWF

iEHRWF Potential Architecture

Potential Architecture

ESB Interface ESB Interface ESB Interface ESB Interface ESB Interface ESB

Interface ESB Interface ESB

Interface ESB_Interface ESB_Interface

TBI/Behav ioral Health Services Service Requests Surgery (Inpatient) Sevices Service Requests Surgery (Outpatient) Services Service Requests Labor and Deliv ery Services Service Requests Primary Care y Service Requests Laboratory y Service Requests Pathology Pathology Services Service Requests M M Pharmacy Service Requests Pharmacy Services Radiology Service Requests Radiology Services Others Service Requests

Enterprise Serv ice Bus

ESB Interface ESB Interface ESB Interface ESB Interface ESB

Interface ESB Interface ESB Interface ESB

Interface ESB Interface

ESB Interface ESB ESB Interface Interface

ESB Interface

Infrastructure Serv ices Administrativ e Serv ices Clinical WorkflowClinical_{Communication} Security Services I/F Registry and Directory Services I/F Mediation Mediated Message Process Message Translation Process Message

Send Translated Message Message

Routing

Message

Send Message

Care Management Serv ices

A Record Management Patient History Summary Lists Assessments Orders/Refs Docs Preferences Patient_Instructions

Health InformationPlansMeds

Orders Health Main Pop HealthAccess Operations Management & Communications Serv ices

Clinical Support Serv ices

Analyis Admin/Financial

Security Serv ices

I/F

Health Record Information and Management Serv ices

Health Record I&M Services I/F

Registry and Directory Serv ices Standard Terminologies and Terminology Serv ices Terminology Services I/F Interoperability S i I/F Business Rules Management Serv ices

Business Rules Management Services I/F Workflow S Utiliites

Clinical Decision Support Serv ices Standards-based Interoperability Serv ices Services I/F Workflow Management Serv ices Management Services I/F

Utility Serv ices

Medical Situational Aw areness Tool

MSAT Data

HAIMS

HAIMS Data

Common reusable Infrastructure enables integration of services

9 Common, reusable Infrastructure enables integration of services.

(10)

Continuing Focus

• Mature

lexicon

for

architecture

development

• _Increase

_access

_to

_Architecture

_data

• _{Revise/update policy and guidance}

_{Revise/update}

_policy

_and

_guidance

• Incorporate

architectures

into

operations,

governance and investment decisions

governance

and

investment

decisions

• Deliver

‘good

enough’

architectures

(11)

Architectures

Support

JCIDS

Process

Architectures

Support

JCIDS

Process

2

3

5

6 V

-7)

V

-1

1)

1

2

3

4 a

b

C

_S

vcV

-S

vcV

-S

vcV

-o

r

5 S

vcV

-T

V-1

)

T

V-2

)

Architectural

Artifacts

per

CJCSI

6212.01F

AV

-1

AV

-2

CV

-2

CV

-3

CV

-5

CV

-6

DIV

-2 (O

V

DIV

-3 (S

V

OV

-1

OV

-2

OV

-3

OV

-4

OV

-5

a

OV

-5

b

OV

-6

C

SV

-1 or

S

1 SV

-2 or

S

2 SV

-4 or

S

4 SV

-5a

o

SvcV

-SV

-6 or

S

6 StdV

-1 (

T

StdV

-2 (

T

ICD

2 X

X

O

CDD

2 X

X

3

3 CDD

2 X

X

3

3 CPD

2 X

X

1

1 X

X

3

3 ISP

2 X

X

1,4 1,4

X

3

3 TISP

2 X

X

1

1 X

X

3

3 Legend

X - Required O - Optional

Note 1

Required only when IT and NSS collects, processes, or uses any shared data or when IT and NSS

exposes, consumes or implements shared services.

Note 2

The AV-1 must be registered, and must be public and released at the lowest classification level possible in

DARS for compliance.

Th t

h i

l

ti

f th StdV 1

d StdV 2

b ilt

i

DISR

li

d

t b

t f

22 Total

DoDAF

Products

•

16 Required

Note 3

The technical portion of the StdV-1 and StdV-2 are built using DISRonline and must be current for

compliance.

Note 4

Not required for JROC approved Operational Requirements Documents.

X

- Indicates new requirement in CJCSI 6212.01F

•

6 Conditional

More

context

and

understanding

earlier

in

the

(12)

Common Language

Warfighter

• Secure

or

Seize

Warfighter

Example

• Clear

or

Attack

in

Zone

Warfighter

Example

Need to Clarify

Need

to

Clarify

to

Clarify

• _{Mission Architecture?}

y

• Mission

Architecture?

• Joint Mission Threads?

• _{Joint Mission Threads?}

• _{Command Enterprise Architecture?}

Joint

Mission

Threads?

• Enterprise

Architecture?

• Capability and Requirements?

Capability

_•

_{Command Enterprise Architecture?}

and

Requirements?

(13)

Summary

• Its

not

about

the

architecture

– its

about

the

architectural analysis

architectural

analysis

• _We

_need

_to

_speak

_{“Warfighter”}

_‐

clearly

quantify

and

articulate

the value

quantify

and

articulate

the

value

• _Much

_more

_than

_materiel

_solutions

• Repository/availability

of

Architectural

products

and

artifacts

being

developed

– a

team

sport

• _{More important in today’s environment than}

_More

_important

_in

_{today s}

_environment

_than

(14)

Questions

Mr.

Dave

DeVries

Mr.

Martin

Westphal

(15)

BACKUPS

(16)

Acronyms

C2OTM

Command

and

Control

(C2)

On

The

Move

CBA

Capabilities

‐

Based

Assessment

CDD

Capability

Development

Document

CPD

Capability

Production

Document

DARS

D

t

t f D f

A hit t

R i t

S t

DARS

Department

of

Defense

Architecture

Registry

System

DOD

IEA

Department

of

Defense

Information

Enterprise

Architecture

DODAF

Department

of

Defense

Architecture

Framework

ICD

Initial

Capabilities

Document

ISP

Information

Support

Plan

JCIDS

J i

C

bili i

I

i

d D

l

S

JCIDS

Joint

Capabilities

Integration

and

Development

System

JMT

Joint

Mission

Thread

JROC

Joint

Requirements

Oversight

Council

NR

‐

KPP

Net

‐

Ready

Key

Performance

Parameter

(17)

Joint Information Enterprise

End State

Coalition Forces

Deployed Environment

• Defensibility/Redundancy/Resiliency

Federation/Shared Infrastructure

“Enterprise

Information

Environment”

Data

Computing

Mission

Applications

• Federation/Shared Infrastructure

• Enterprise Services

• Identity Access Management

Computing

Data

Applications

AT21

Navy ERP

DCO

iEHR

Enterprise

Email

Enterprise

Email

Defense

Travel

Defense

Travel

APEX

AFATDS

Airman

Fundamentals

Airman

Fundamentals

Close

Combat

TM

Close

Combat

TM

“Enterprise

Information

Environment”

Applications

??

Work

Mobile

(TDY/Deploy)

Home

Future

devices

Access

at

the

Point

of

Need

1

7