1 / 9

Joint DFAS & Treasury Collaborative XML Strategy: Standards-based Data Interchange Among US Government Entities

Joint DFAS & Treasury Collaborative XML Strategy: Standards-based Data Interchange Among US Government Entities. Mike Lubash : DFAS Nauman Malik : XMLCG. July 2002. As I See It!.

ianthe
Download Presentation

Joint DFAS & Treasury Collaborative XML Strategy: Standards-based Data Interchange Among US Government Entities

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Joint DFAS & Treasury Collaborative XML Strategy:Standards-based Data Interchange Among US Government Entities Mike Lubash : DFAS Nauman Malik : XMLCG July 2002

  2. As I See It!... “Talking with and listening to our customers and understanding their mission and challenges is key to being creative in offering solutions.” -- Robert McNamara, Director for Accounting The Communication Enabler Strategy • Define a sound, collaborative, XML-based, financial reporting mechanism for DFAS, Treasury, and their trading partners

  3. “By themselves, though, technology and tools won’t enhance our competitive advantage if we don’t use them to share our knowledge and insights willingly with our colleagues.” -- Edward T. Grysavage, Business Integration Executive Presentation Objectives • Debrief results of XML reporting initiative • Demonstrate competitive advantage to DFAS and expeditious sharing of financial information with its trading partners • Obtain approval to register XML artifacts in DoD XML Registry (Data Emporium) • Decide whether to XML-ize DFAS FACTS Reporting

  4. “The fact is many tasks we perform today could be eliminated if things were done correctly at each critical step in the end-to-end process.” -- Lee Krushinski, Director, Accounting Services Today’s Situation Tomorrow’s Opportunities • Reuse was not a design consideration in the development of reporting components • Automated Trial Balance • Not easily interpreted in plain text format (ASCII) • Data quality determined after submission • XML-based reporting components are designed for use and reuse across the federal government • Automated Trial Balance • Human and machine readable • Data quality achieved before submission (early error detection)

  5. What is easier to understand and search? ARMY 1010D34,507,584,4721110D436,9881120D12,112,353 1130D01190D145,618,8071195D01200D57,747,632 1310D688,542,5921310D357,282,8391319C0 1319C-41,291,4191320D01320D01330D0 <?xml version="1.0"?> - <SGLAccounts> <ReportingDept>Department of the Army</ReportingDept> <Account Number="1010" BalanceCode="D">34504472</Account> <Account Number="1110" BalanceCode ="D">436988</Account> <Account Number="1120" BalanceCode ="D">1211233</Account> <Account Number="1130" BalanceCode ="D">0</Account> <Account Number="1190" BalanceCode ="D">1451807</Account> <Account Number="1195" BalanceCode ="D">0</Account> <Account Number="1200" BalanceCode ="D">5774632</Account> <Account Number="1310" BalanceCode ="D">6882592</Account> . . . If XML… If Flat File... If EDI...

  6. “And, as some of our most experienced co-workers retire, they take their knowledge with them. If our employees’ expert knowledge is not continually refreshed and willingly shared with DFAS colleagues, our competitive advantage in meeting customer needs will be lost.” -- Edward T. Grysavage, Business Integration Executive (continued)Today’s Situation Tomorrow’s Opportunities • Notes • Institutional knowledge locked in one or few key human resources • Access requires proprietary applications on every desktop • Brute programming required for data interchange & display • Technology limits business capability • Notes • Maps / rules documented in human readable and enforceable form • Browser-based access to XML-ized reports • Decreases need for brute programming • Business functionals empowered by using “black-boxing” XML components

  7. “World-class organizations understand that eliminating redundant or unnecessary processes and procedures not only helps their bottom line, but it also gives them a competitive advantage.” -- Lee Krushinski, Director, Accounting Services Summary of XML Business Benefits • XML is the most efficient mechanism for achieving DFAS’s mission • A move to an open, non-proprietary environment • Customer and functional empowerment Provide responsive, professional finance and accounting services for the people who defend America Why wouldn’t you use it?

  8. “Our vision of providing the best value to our customers by being a trusted, innovative financial partner means building a consultative relationship with our customers.” -- Robert McNamara, Director for Accounting Where do we go from here? • Collaborate with Treasury and other trading partners • Register the XML artifacts • XML-ize reporting

  9. “Undoubtedly, changes involve or identify problem areas, systems issues, customer complaints, new regulations, and new technology - all of which typically need ‘solutions.’ ” “The search for these solutions is the challenge that faces DFAS today.” -- Robert McNamara, Director for Accounting Thank You

More Related