__________________________________________________________________________

GSA Financial ManagementEnterprise Architecture

May 24, 2006

__________________________________________________________________________

Agenda

• Why Financial Management Enterprise Architecture (FMEA)– Purpose – Objectives

• EA Approach

• Model Driven Architecture• MDA to SOA

• Items for Discussion

__________________________________________________________________________

Why FMEA• Business Efficiencies

– Reduce IT Portfolio Duplication– Utilize existing applications– Build out standard business processes

• President’s Management Agenda – eGov– Plan the revolving and appropriations fund core

accounting systems for a Financial Management Line of Business (FM LoB) serving GSA and other agencies.

• Address immediate need to transform legacy applications into a cohesive financial management suite

__________________________________________________________________________

FMEA Objectives• The FMEA product will accommodate Statutory, Office of

Management and Budget (OMB), and GSA Functional requirements, such as tying to FEA reference models, and the goals of the FM LoB initiative, including:– achieving process improvements and cost savings;– standardizing business processes and data for customers and across GSA;– meeting business needs through ability to have standard interface with

acquisition;– promoting seamless data exchanges among clients; – strengthening internal controls through interoperability; and– be consistent with the emerging GSA enterprise architecture.

Be understandable and useable for Federal customers and GSA

__________________________________________________________________________

__________________________________________________________________________

PEGASYS

ExternalSystemsTMR (6 D-N-P-V)FedPay (5 D-L-Q-K)PAR (3K-P-M-L)Labor Distribution (JL)FMS (9F-I)Bulkload (BK, BN, B*)

Forms Import

SV/PA/RCAE/ CX/ MI

N.R.P Daily/Bi-monthly

BILLINGSFAIM-FEDBIL(VL,UL, UQ, UJ)CSC-(LE)AUTOBILL(WQ, WJ, WL, WK ) TIRES (XL)TAP (8D-L-Q-J-I)RWA (QL, QJ, QQ)TOPS (HK)RENT (ZL)CBG (YL, YK, YJ)Manual Input (K*, DL, DQ)159-459 (SL)GSAP(2J, H, G, N)RECEIVABLE128-165-465 (FL)420-488411 (EL)

MonthlyCost AllocationGSF (ML) 158-258-958 ITSTIRES148536RPADS (GL)

BuildingRent

ProjectFDDS07

STAR IRIS TOOLBOX

.TRs

FDBX,RWA, FR2130, FDGSF,FR53FRIT

VITAP

DATA STORE

FMISDetail and Summary

Query Tool

FEDEX

PAR Ref

Citibank

VAT Extracting Process

VATPROCEdit

Conversion

131

InfoWizard

Performance Measurement

Tool (PMT)

Data Elem Conversio

n145

FTSIFD

GSAP

Financial Reports OnlineITOMS/OMIS

(2B, 2C, 2E)

TOPS(HB, HC, HE)

Comprizon(1B, 1C, 1E)

UPPS(UE, UD)

VCPC(1B,IE)

TransformationBox

Batch ControlEdit

BudgetingPlanningPurchasingAccounts PayableAccounts ReceivableAutomated DisbursementsGeneral SystemGeneral LedgerCredit CardVendorExternal Reports>

INVOICES(M7)

VAT Splitter Process

Business Object for Pegasys,

FMIS

__________________________________________________________________________

Enterprise Components in a Service Oriented Architecture

• Enterprise Components must be independent & loosely coupled

• While being able to interoperate with each other using services

• Making the information system a lattice of cooperating components

• Simulated or real

Service

Service

Serv

ice

Ser

vice

__________________________________________________________________________

• So why is this important?

Shared Services Value Chains

I.T. Services

Financial Management Services

Human Capital Services

Plan and Design Develop and

Deliver Provide

After Care

Acquisition Value Chain

Marketing

Development of Government-wide Policy

__________________________________________________________________________

Architectural Approach

MDA, ADM and Executable Architecture

__________________________________________________________________________

Architecture Driven Modernization (ADM)

FMEA: MDA Top Down - ADM Bottom Up

Model Driven Architecture (MDA)

Discovery of System Details and

generation of Technology

Specifications is largely automated

__________________________________________________________________________

What is Executable Enterprise Architecture?

• Moves past a static process diagram to an organic model that is aligned with agency’s business and IT planning and existing infrastructure.– Model Driven Architecture (MDA)– EDOC – Enterprise Collaboration Architecture

(ECA)

__________________________________________________________________________

What does Executable EA Accomplish?

• Aligns business cases with systems design/development within existing IT infrastructure

• Collapses CPIC and SDLC cycles– Significantly reduces resource burden – ‘JIT’ 300 generation

• Integrates metric analysis – prior to procurement or development effort– Performance Reference Model ‘line of sight’ from model

simulation trace• Leverages open standards to build your EA

– The end of modeling fatigue and paper tiger extinction!• Ensures agile, business driven IT management

__________________________________________________________________________

Why Use MDA?

• Framework for structuring business and technology specifications expressed as models– Separates platform independent models and

technology specific models– Allows applications to be integrated by

explicitly relating their models

__________________________________________________________________________

Model Driven Architecture

• Computation Independent Model (CIM)– The business model

• Platform Independent Model (PIM)– Technology independent system specification– Conforms to the business model (CIM)

• Platform Specific Model (PSM)– Technology specific (e.g., middleware, application

platform, etc.) system design– Conforms to the system specification (PIM)

__________________________________________________________________________

Business Process

Architecture

AutomatedModel Driven Architecture

SimulatorSimulator

EnterpriseEnterpriseArchitecture Architecture

ModelModel(PIM)(PIM)

Live Process Simulation

Refine/Iterate

ECA Standard“Meta-Model”

__________________________________________________________________________

Models

__________________________________________________________________________CIM: “One GSA” Disciplines

Financial Management

Policy

Acquisition

Human Resources Marketing

Property ManagementSolutions

Business Intelligence

Focus of FMEA

__________________________________________________________________________CIM: Financial Management Enterprise Roles

Receivables Accounting

Funds Management Payables Accounting

Asset Accounting

Financial Planning

General Ledger

Cost AllocationCash Management

Financial Reporting

Financial Reporting collects financial data from all other enterprise roles.

__________________________________________________________________________

GSA’s FMLoB: CIM Decomposition Conventions

Enterprise Role. A major area of functional responsibility within the discipline of financial management

Enterprise Role. A major area of functional responsibility within the discipline of financial management

Work Role. A role responsible for a specific functional area within an enterprise role, such as might be assigned to a single worker and supported by an IT system

Work Role. A role responsible for a specific functional area within an enterprise role, such as might be assigned to a single worker and supported by an IT system

Protocol. A defined conversation between two roles that may be extended over time. One role initiates and the other responds to the protocol, but information may flow both ways across the protocol

Protocol. A defined conversation between two roles that may be extended over time. One role initiates and the other responds to the protocol, but information may flow both ways across the protocol

Activity. A specification of a business function carried out in the context of a work roleActivity. A specification of a business function carried out in the context of a work role

Subactivity. A specification a sub-function necessary to carry out an Activity

Subactivity. A specification a sub-function necessary to carry out an Activity

Information Flow. An individual flow of information across a protocol or into or out of an Activity or Subactivity

Information Flow. An individual flow of information across a protocol or into or out of an Activity or Subactivity

__________________________________________________________________________

CIM: FMLoB Enterprise Roles

__________________________________________________________________________

CIM: Enterprise Role Composes Work Roles

__________________________________________________________________________

Example of Data Included in Processes:Receivable Establishment

Message Model

__________________________________________________________________________

Protocol WSDL Representation (PSM/SA, TRM)

<portType name=“ChargeEstablishmentRequestInterface"><operation name=“sendChargeEstablishment">

<input name=“ChargeEstablishment" message="tns:ChargeEstablishment" />

</operation></portType>

<portType name=“ChargeEstablishmentResponseInterface"><operation name=“sendChargeEstablished">

<input name=“ChargeEstablished" message="tns:ChargeEstablished" />

</operation><operation name=“sendChargeRejected">

<input name=“ChargeRejected" message="tns:ChargeRejected" /> </operation>

</portType>

__________________________________________________________________________

Moving From Business Process to System Specifications

__________________________________________________________________________

PIM/PSM: Service-Oriented Component Architecture

Presentation Tier Application Tier Data Tier

Each Work Component in the PIM implements a Work Role from the CIMEach Work Component in the PIM implements a Work Role from the CIM

Presentation Manager components provide user access to application services

Presentation Manager components provide user access to application services

Service Manager components provide transactional implementation of application services defined in the CIM

Service Manager components provide transactional implementation of application services defined in the CIM

Data Manager components persist data between application transactions

Data Manager components persist data between application transactions

Work Module

__________________________________________________________________________

PIM/PSM: Service-Oriented Component Architecture

Presentation Tier Application Tier Data Tier

Each Work Component in the PIM implements a Work Role from the CIMEach Work Component in the PIM implements a Work Role from the CIM

Presentation Manager components provide user access to application services

Presentation Manager components provide user access to application services

Service Manager components provide transactional implementation of application services defined in the CIM

Service Manager components provide transactional implementation of application services defined in the CIM

Data Manager components persist data between application transactions

Data Manager components persist data between application transactions

Subsystem

System Assembly

__________________________________________________________________________

PIM: Receivables Management Work Role

Provided services

Used services

Presentation Manager Service ManagersService Managers Data Managers

Role for human participation in the process

Explicit cross-transactional coupling via the data tier

__________________________________________________________________________

Putting it All Together

__________________________________________________________________________

ROLE 1ROLE 1

P1

ROLE 2

P2

ROLE 3

P4P3

Community Process (CoP)

• Recursive decomposition for ‘systems of systems’ modeling– Business processes described as a composition of services

• Collaborative Role Interactions (CRI), service choreography

– Services are realized by (a composition of) components

__________________________________________________________________________

CollaborationsContextualizeRoles = Service Providers

Buyer

Enterprise

GSA

Enterprise

Seller

Enterprise

__________________________________________________________________________

RolesRoles Compose Inner RolesInner Roles = Service Granularity

__________________________________________________________________________

Protocols Organize ConversationsConversations Choreographed by Roles

__________________________________________________________________________

Summary of FMEA Project

• Developed a standard set of business processes for financial management, including the core functions, plus fixed asset accounting, inventory, and – Standard processes are compliant with FSIO – Standard processes are compliant with FM LOB– Standard processes show interactions of functions

• Developed data objects relevant to each business function and activity– Flow of data activity aligns with processes developed– Provides relationships among the data objects

• Documented requirements and business rules– Requirements are compliant with FSIO – Requirements are compliant with FM LOB– Business rules include Federal rules, plus GSA specific rules

• Generated Function Requirements and Interface Specifications

__________________________________________________________________________

Key Thoughts

• An agreed upon approach and methodology is the key, tools help

• Utilize existing knowledge bases to cut down on rework and modeling/study fatigue

• Business Drivers/Business Outcomes

__________________________________________________________________________

Questions?

Thank You to our Partners:

GSA OCIO

Logistics Management Institute

Data Access Technologies