Providing Business Agility through Enterprise Information Services

Providing Business Agility through Enterprise Information Services Eric Okin Assistant Deputy Director Policy and Architecture; DFAS - DTB Mike Lubash XML Team Leader DoD Finance and Accounting Namespace Manager

Objectives of the Meeting For you to take away… • an understanding of the proposed DFAS XML Strategy • food for thought as how to best leverage the Strategy’s underlying technologies • You are instrumental in laying the technical groundwork to enable DFAS to become a world-class financial services provider.

Agenda • Communication • Context – Information Metrics • Strategy • Benefits • How did we get here? • Questions

Business Operational View Domain aspects of business transactions Its All About Effective Communication… Using the same mechanism to communicate with our trading partners Improving communication between business domain experts (‘what’) and technologist (‘how’) to maximize new exciting opportunities. Technology Service View IT aspects of business transactions

Context - Critical Metric for Communication Communication Levels Packaged Solutions Management Level = Degree of Control Minimum Level Metadata Management SEMANTICS

Strategy - Principles Business Operational View Domain aspects of business transactions • Adopt Holistic Framework • Leverage Inherent Features of XML Technology • Implement Business Information Objects • Establish Registry-Centric Concept of Operations • Services-based Infrastructure • It is not just about technology Technology Service View IT aspects of business transactions

Adopt Holistic Framework - Evolution OMG Modeling CALS IDEF UMM UML Queuing SGML EDI Business Rules MOM Mappers Repositories Templates ebXML UDEF DFAS XML Implementation BSR Architecture XML/edi Framework Zachman XML XSL DCII Agents JTA SOAP HTML Java UDDI Web Services

Adopt Holistic Framework - Proposed Tasks

Leverage Inherent Features of XML Technology • Direct descendent of SGML; XML is a meta-languages & a family of specifications to define business vocabularies for our information exchanges • DoD is mandating the use of XML (e.g., JTA, GIG) and has started a DoD-wide XML registration effort as part of DII COE SHADE initiative • DFAS appointed namespace manager for DoD Finance and Accounting StrengthsWeakness • Broad support as format and mechanism for future • Open standards bodies and industry consortiums • Open environment - language & platform independence • Specified with the Internet in mind, and expanded into many areas, wireless, knowledge mgmt., workflow, etc. • Simple – easy to learn, develop a skilled labor force <CellPhone>800.555.1212< /CellPhone> • Technology is widespread, easily available, and at lower cost than alternatives • Universal data structures supports focused content search needs, personalization, and automation • Open metadata exchange for validation and convey greater context and business constraints • If not properly implemented could uses additional computing resources • Advanced specifications are new and thus not mature and tested • If uncontrolled, the extensibility of XML could result in multiple, conflicting data semantics (meaning) and syntax (structure) conventions

Implement & Register Our Business Information Objects Collaboration Partner Agreements 5 Contract Collaboration Partner Profiles Business Integration 4 Workflow Process Specifications Schema 3 Technology Integration Messages Artifact relationships Controls: 2 Motivation Time People Presentation Rules Events Roles Directory Services Inputs, Outputs: Touchpoints Data/Codes Services/Functions Network 1 Nouns Verbs Transport Routing, Packaging Leverage our information assets for emerging eBusiness-centric world

Establish Registry-Centric Concept of Operations SHIFT SHIFT Ad Hoc Hub n’ Spoke Information Services Layer Distributed data processing Simple Pt.-to-Pt. No Metadata Strategy Reuse: Little Opportunity End-to-End Tracking: Low Integration at Point of Use Lookup Info: Kept at Domain Mapping: Only Once Bandwidth Required: Lowest Computing: Distributed Load Impact of Changes: Low Pt.-to-Pt. Real-time: Yes Immediate Solution Centralized data processing only Virtual Pt.-to-Pt. Broker-based Metadata Strategy Reuse: High Central End-to-End Tracking: Yes, Central Integration at Broker Lookup Info: Must publish to Broker Mapping: Two or more Bandwidth Required: Highest Computing: Central; Big Iron Impact of Changes: High Pt.-to-Pt. Real-time: No Technology Solution Central & Distributed data processing Common Pt.-to-Pt. Mechanism Enterprise Metadata Strategy Reuse: Much Opportunity End-to-End Tracking: Services Integration at Point of Use Lookup Info: Kept at Domain Mapping: Once Bandwidth Required: Lowest Computing: Distributed Load Impact of Changes: High Pt.-to-Pt. Real-time: Yes Business Solution

Registry: Supporting the Challenge of Business Communication Business Collaboration Partner #1 Collaboration Partner #2 XML Instance XML Instance Data <ListPrice>9.99</ListPrice> <UnitPrice>9.99</UnitPrice> Machine-to-Machine <Currency>$</Currency>

DCRegistry Context Everywhere!UIDs VI304 Dollars Collaboration Partner #1 Collaboration Partner #2 X12 UnitPrice EDIFACT ListPrice Currency <Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENTrep= ‘DISA’name=‘ListPrice’uid =‘VI304’ > Schema or Template <Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENTrep= ‘DISA’name=‘UnitPrice’uid =‘VI304’ > Schema or Template XML Instance XML Instance Data <ListPrice>9.99</ListPrice> <UnitPrice>9.99</UnitPrice> <Currency>$</Currency> UIDs allow for domain crosswalks and light transactions

Services-based Infrastructure - EISL Components User Interface - Presentation Apps Web Browser Email Client Telephone Wireless Front-End Common Services Oracle9i WSF Web Services Framework 1 Assurance DCR Registry Workflow Access Enterprise Information Services Layer - EISL DCW DCD Exchange Common Exchange SOAP-based Envelope HTTP 2 Collaboration Gateway Business Applications and Functions Back-End Finance Account Project Mgmt HR Procure

EISL - EnterpriseInformation Services Layer

Transition: Shift in Focus of DCII Strategy Initial DCII Focus Current DCII Focus • Most F&A functions are implemented in Type III Applications • Direct access to DCD/DCW enable robust information exchange • Type II/I applications (e.g., DPPS) are the exceptions • “Cross-walking” would be used for information exchange between Type II/I applications and DCD/DCW • Most F&A functions are implemented in ERP/COTS solutions as Type II/I Applications (e.g., BMR, DDRS, SMAS, DIMHRS) • Type III applications (e.g., DSDS) are the exceptions • “Cross-walking” to/from DCD/DCW to exchange information between Type I/II applications is not efficient • Shared services DCII Focus Need DCII Enterprise Information Service Layer (EISL) to connect heterogeneous Type II applications across the DoD F&A domain!

Can’t Get to the Higher Level Constructs… without Building upon a Solid Foundation • Behavior integration { } • Context Everywhere Enterprise Agility #3 Business Process • Reusable Knowledge bases Hard • Full-compliant Architecture (e.g., JTA, GIG, DCII, FFMIA) Domain Knowledge DCII • DFAS Registry #2 Infrastructure Difficult Enterprise Information • Enterprise Information Services Services #1 Heterogeneous Interoperability XML Technology • Improve the delivery, timeliness, and accuracy of Finance and Accounting services in key areas Easy • Define and start implementing compliant architecture • Start enterprise management of information and knowledge assets

Modeling an EISL Enabled Environment Maximizing business benefits requires operating at the higher levels of the pyramids Information Value Chain World-class services providers operate at the high end of the information value chain

It is Not Just About Technology Functionally-based Services; not System- centric Use Non-proprietary Standards and Tools Manage Business Artifacts at Appropriate Levels Loosely-Coupled Architecture Compliance With Policy Education Long-Term Commitment to Strategy Principles Take Ownership Responsibility for Artifacts Modify Procedures to Assure Integrity and Outcomes

Background - How Did We Get Here? • ‘As is’ Business Assessment • Business Opportunity Analysis

Summary • Free DFAS Infrastructure from Proprietary Shackles • Manage Our Business Information Assets • Construct an Architecture for Enabling an Enterprise Information Services Layer (EISL) • Implement XML Strategy based on business opportunity

Questions ? Thank you Eric Okin Assistant Deputy Director Policy and Architecture; DFAS - DTB Mike Lubash 703.607.1166 Mike.Lubash@DFAS.mil XML Team Leader DoD Finance and Accounting Namespace Manager

‘As is’ - Assessment of Current Business Environment • DBE - DFAS Business Evolution • Solid “To Be” Architecture • DCD and DCR - Repository • Good Infrastructure Base • Inability to provide CFO compliant Financial Statements • Disparate Financial Architecture and Systems • Convoluted Business Practices • Useful Information is Hard to Extract • Unable to Provide Reliable Information • Overly Complex Data Requirements • System-Centric Solutions + -

Business Opportunity Survey (1 of 2) Purpose:Assess XML as an enterprise enablerSource:DoD, Industry and DFAS on going initiativesScope:DFAS’ organization requirementsTasks: - Derive requirements through a series of Proof of Principles: - Wireless; WAP and VoiceXML - STANFINS & Transformation Tool Evaluation - SGL to Treasury (Balance sheet) - Working with industry initiatives (ebXML, HR-XML, XBRL, etc.) - Working with standard initiatives (DoD SHADE & DISA.org DRIve) - Member of EMall RIT - defining best practice for component identification and classification

Business Opportunity Survey (2 of 2) Results:- Tower of Babel - Technology is sound - Still need to define business semanticsConclusions: - XML initiatives must be managed to maximize benefits - Need to shift our strategy from homogenous to heterogeneous integration mechanisms Recommendations: - Execute ‘DFAS XML Implementation Strategy’ - Manage business artifacts atomic level to assure enterprise agility, quality and integrity

Activities/Accomplishments Oversight & Planning Registry • Developed Draft DFAS XML Implementation Strategy • Identifying Registry requirements Education & Awareness Methodology • Using Registry-centric ebXML methodology as start point • Formulating E&A strategy • Established XML training course Architecture Business Information Objects • Updated DCII-CE Specification Version 5.0 to include Enterprise Information Service Layer (EISL) • Developed draft EISL Specification • Identifying core and domain components and associated development requirements Utilities & Tools • Sponsored and participated in evaluation of Enterprise Application Integration tools Domain Collaboration • Collaboration with XBRL, ARAP XML, Hr-XML, SHADE, OASIS • Working with Treasury for ebXML proof of principle

Why we are here? DFAS-DT Responsibilities • Data and Metadata Management:DFAS-DT/CIO has the responsibility to ensure the Agency is following a standard corporate approach to data and metadata management • If uncontrolled, the Agency’s use of XML technology could result in non-interoperability due to multiple, conflicting data formats and naming conventions • Information and Information Technology Assets -In support of Clinger-Cohen legislation, DFAS DT/CIO has the responsibility to ensure the Agency uses its information and information technology assets effectively and efficiently in support of mission accomplishment • DCII Architecture -In support of Clinger-Cohen legislation, DFAS DT/CIO has the responsibility for establishing and maintaining a sound integrated IT architecture • DoD Control Point for Finance & Accounting -DFAS DT/CIO has the responsibility to meet DoD requirements and register F&A domain nomenclature within the DoD “DCII COE Data Emporium” XML Registry - SHADE

Providing Business Agility through Enterprise Information Services