U.S. General Services Administration George Thomas, GSA OCIO Chief Architect Line of Sight = Reuse

U.S. General Services Administration

George Thomas, GSA OCIO Chief Architect

Line of Sight = Reuse

George Thomas, GSA OCIO Enterprise Architecture Group

May 4, 2023

2

Topics

• Levels of abstraction• Recursive decomposition• Specifying external boundaries• Deployment decisions• Discovery of commonality


May 4, 2023

3

VCA + MDA on SOA = Executable EA• What we want -

– Process centric and Service Oriented executable models with FEA associations to automate artifact generation for a variety of end users

• What we need -– Formal grammar expressing collaborative role interactions

• Our Approach - EDOC/ECA/CCA– Enterprise Distributed Object Computing (EDOC) – Enterprise

Collaboration Architecture (ECA) – Component Collaboration Architecture (CCA)

• Open Standard – Object Management Group (omg.org) ratified Unified Modeling Language (UML) Profile

• The Result– PIM - Data driven (Data Reference Model - DRM)

conversations between roles (Service Component Reference Model - SRM) in the context of a business process (Business Reference Model - BRM)

– PSM - specializations mapped to deployment decisions (Technical Reference Model - TRM)

– Performance Reference Model (PRM) metrics pervade PIM and PSM models


May 4, 2023

4

(EDOC/ECA) CCA Grammar

Implementation

Net

Hardware

OperatingSystem

Framework,Middleware& Container

Interaction Path

Component in Role

Interaction(With Information)

Role

Collaboration


May 4, 2023

5

Order to Payment Process Diagram

Notificationof Order

Completion

PaymentNotification

DeliverySchedule

Goods andServices

PurchaseOrder

AwardNotificationRFQs ow

Pegasys/Near

Order to Payment (Future State) - Involves only Purchases viaSchedules

Sup

plie

r:Fi

nanc

ial

Offi

cer

Sup

plie

r:C

ontra

ctO

ffice

r

FSS

:Fi

nanc

ial

Offi

cer

Info

rmat

ion

Con

tract

ing

Cus

tom

er:

Pro

ject

Man

ager

Sup

plie

r:P

roje

ct M

anag

erFS

S:

Ord

er M

anag

erS

yste

ms

Cus

tom

er:

Fina

ncia

l O

ffice

r

Issue RFQ

Review RFQ

SubmitResponse

Conduct initialevaluation

eBuy (GUI interface)

Scheduleinformation(e-Library)

Processpurchase orders

Scheduledelivery ofgoods andservices

Accept Goods/Services

ProcessPayment

Dev elopPurchasing

Request (SOW,SLA, pricing,

timeline)

Adv antage DB

Customer financialsystems

Determine itemprice/

availability/contract

Notif ication oforder completion

Determineproject need for

products andservices

CombineProject

requirements

Conductresearch usinge-Library/eBuy

Record funding

Evaluatevendor

responses

Prepare Order

Obligate funds

Check orderstatus

ReceivePayment

Realize revenue

Close out order

Receive invoice

Funds

CustomerProcurement

Systems

Supplier Catalogs FSS-19

A B C D E

H

I JK L M N O P

A, F, I, L

E-Library

F

B, O

A, I,L

A, J A, D, J

A, J

A, J, L

A, J, L

B, E, O, S

A, D, G, M

A, E, L, M, S A, E, L, M, S

A, J, L

A, E, L, S

B, Q, S

B, C,T

B, D, Q, S

G, O, Q

Supplier FinancialSystems

G

Q

Bill Customer

R

I, R

S

Create Invoice

DevelopEvaluation

criteria/provideinput

ConductMarket

Research/Survey

Respond?Develop

response toRFQ

RFQ via eBuy

Yes

Responses via eBuy

Request review of responses

Answerquestions/

provide inputDistribute POs

POvia eBuyNo interest, Customer w ill

review other quotesNo

QuestionsAnswers

ReceivePurchase

Orders

Customer Invoice

Notif ication ofpayment received

Delivery Schedule

Receive RFQ

RFQ

RFQresponse

Review POs

POs

I

I

A, J

A, D, J

A, E, L, M, S

K A, D, G, P

D, G, M, P, Q D, G, M, P, Q

E, R, S

Inspect/Receivegoods andservices

B, C, N, P

DeliveryReceipt

T

DeliveryReceipt

ReceiveDeliverySchedule

B, C, N, P

Provideschedule

updates to FSSShip Goods

ReceiveDeliveryReceipt

Close outOrder

Goods/Services

Delivery Receipt

Payment orFunds Transfer

A, D, G, P A, D, G, N A, D, G, T A, D, G

Request fundavailability

Funding validated

DevelopAcquisition

Plan

CoordinateAcquisitionPlanning

Acquisition Plan Input

Receivepurchase

request datafrom PM

Assign contractspecialist

SOW

Evaluate PastPerformance

Aw ard Decision

Obligation

Monitor anddocument

performance

Close out order

A, K, L

Issue Aw ardNotices

Check orderstatus

B, C, SA, I, K,L

Final factf inding w ithsuppliers

VerifyFunds

Acceptance

ReceivePOs

POs via eBuy

Build RFQ

Market Research

Answerquestions/

provide input

Receivedeliveryschedule/updates

Receivedeliveryreceipts

Delivery scheduleupdates

Providecopy ofreceipt to

FSS

Delivery Receipts

Perform 3-w ayMatch

POs


May 4, 2023

6

Identifying Roles


May 4, 2023

7

Finding Roles and Inner Roles

Customer Project Manager

Customer Contracting

Customer Financial Officer

Supplier Financial Officer

Supplier Project Manager

Supplier Contracting Officer

FSS: Order Manager

FSS: Financial Officer

“Swim Lanes”

Order to Payment

Customer ProcurementBroker

Supplier

ProjectManager

ContractingOfficer

FinancialOfficer

ProjectManager

ContractingOfficer

FinancialOfficer

FinancialOfficer

OrderManager

RFQManager

CatalogManager

Roles in a Collaboration


May 4, 2023

8

Highest Level Roles in Procurement Collaboration

Order to Payment

Customer ProcurementBroker

Supplier


May 4, 2023

9

Identifying High Level Protocols

Interactions


May 4, 2023

10

Attach Protocols to Roles as ‘Ports’

Group transitions together into logical

units


May 4, 2023

11

Specifying Interactions


May 4, 2023

12

Inner Protocols• Protocols represent

conversations between roles

• Conversations frequently have sub-conversations, detail about a specific subject

• These sub-conversations are inner protocols

• Inner protocols can also be reused in other protocols or even as top-level protocols

• Protocols can “nest” to any level of detail


May 4, 2023

13

Fully Elaborated Protocols• This is an example

of a protocol with the inner-protocols, document flows and types specified

• This level of detail is specified when we know it and visible when we need it


May 4, 2023

14

Co-managed Service Collaboration Specification


May 4, 2023

15

Summary High Level Collaboration Specification

Simplified View - Level of detail is optional


May 4, 2023

16

Drilling Down into Customer Details

Customer

ProjectManager

ContractingOfficer

FinancialOfficer


May 4, 2023

17

Choreography of Process


May 4, 2023

18

Modeling Collaboration Data• Fill in details of

documents• Focus on business

information - not technology

• Interoperability Data Model (DRM) - Not an ODS information model

• May be derived from existing sources

• Includes– Composition– Type– Cardinality

• Document<->Object


May 4, 2023

19

Multiple Implementations of a Role

CustomerRole

(Logical)

DOL CustomerComponent

(Implementation)

DOI CustomerComponent

(Implementation)

Internal CustomerComponent

(Implementation)

The “Inside” can change as long as the external “contract” is satisfied


May 4, 2023

20

GSA FSS O2P ‘Punch Out’ Demo• Benefits

– Easy to compose collaborative alternatives, reusing roles and protocols in new scenarios

– Provides an open standard BPR/SOA formal object model for recursive component decomposition (SRM granularity)

– Stakeholders understand and provide feedback on the proposed process• Communicates intent and validates correctness prior to

budget/procurement• Provides framework for optimizing metrics and

generating EA artifacts, views, reports, docs, etc.– Technology platform is a deployment decision,

adapting interface specifications to whatever – WS, EAI/MOM, J2EE/.NET, etc.• Model simulation specifies how existing and planned

systems interoperate (multiple heterogeneous), collapsing SDLC

Documents

U.S. General Services Administration George Thomas, GSA OCIO Chief Architect Line of Sight = Reuse