1 / 50

Treasury’s FACTS II MAF Master Appropriation File Subset

Meeting: May 14 th 2002 - Treasury’s FACTS II MAF - XML - ‘What’ Not ‘How’ Importing - SFC; Standard Fiscal Code - Next Steps. Treasury’s FACTS II MAF Master Appropriation File Subset. STAR – Treasury System Feed. Treasury’s Direction.

griffin-watson
Télécharger la présentation

Treasury’s FACTS II MAF Master Appropriation File Subset

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. Meeting: May 14th 2002- Treasury’s FACTS II MAF- XML - ‘What’ Not ‘How’ Importing - SFC; Standard Fiscal Code- Next Steps

  2. Treasury’s FACTS II MAFMaster Appropriation File Subset STAR – Treasury System Feed

  3. Treasury’s Direction 1. Current environment is built upon processes that require burdensome, after-the-fact reconciliations. 2. Scores of forms and multiple computer systems to transfer data between themselves The GWA Project is examining existing business processes and recommending fundamental changes so that FMS can produce more timely, accurate and reliable financial reports …

  4. Why XML Technology is an Ingredient of GWA Lowers the Bar- easy to read for business users and technologist alike – providing a common ground for communicating information. Available labor pool is large due to the fact that XML parallels HTML education and XML doesn’t require large amounts of specific training to leverage. Machines can easily parse XML and align with data in a robust manner. Independence- from Operating Systems, Applications, Databases, Software Language, Presentation, etc. XSL stylesheets describe how to render data on different devices (monitors, printers, palm pilots, WebTV, voice and agent interactions). Universal Clipboard- implemented as hierarchical nodal trees XML can accommodate entity-relationships, freeform, and network data representations. Any application can validate information prior to internal processing. With XML, all nodes can use the same methods for simplifying and automating processes. End-tagging and consistent syntax enables enhance detection of incomplete information packages. Granularity - XML tagging provides high-resolution access to data enabling context-based searching and delta updates. Contextual information improve the ability to retrieve relevant information from total pool of information. Favors reusable nodes. eXtensible - domain-specific vocabularies, that enable tag names to be specific business needs of a community (e.g., finance and accounting, human resources). Need not be limited to “standard” transactions, and many initiatives which to choose. Semantic References - minimal prior knowledge of sender application is necessaryto process information. Not positional or delimiter defined, thus allowing flexible packaging based on business needs. Context Views – any application can extract and separate information it needs to satisfy business functions from other facilitation types of information (e.g., routing, security, archiving). Users (or applications) can on-demand select data views(e.g., one record or all, sort by different attributes, various details) based on business needs/rules.

  5. Import Import Filter Filter Treasury FACTS II MAF Vision Treasury DFAS All Agencies XML XML Downstream Agency Specific Edit XSLT Filter Example Other Agencies XML

  6. DFAS Vision: Data Sharing from Single Source Treasury DFAS Customers Services 121130D01 1319C-41,2 1010D34,507,584,4721 121130D01190D145,6 1310D688,542,592131 1319C-41,291,4191320 As Is 121130D01 1319C-41,2 Convert 121130D01 1319C-41,2 121130D01 1319C-41,2

  7. DFAS Vision: Data Sharing from Single Source (con’t) Treasury DFAS Customers Services * Opportunity to simplify Convert* Convert* XML MAF XML Digested with value-add XML Digested with value-add Value-chain After

  8. Effort To Date MS-Word Specification <SFC> <TreasuryCode versionId="0.01"> <DepartmentId>17</DepartmentId> <TransferFromDepartmentId>21</TransferFromDepartmentId> <FiscalYearId>0203</FiscalYearId> <BasicSymbolCode>0040</BasicSymbolCode> <SubClassificationCode>62</SubClassificationCode> <SubAccountSymbol>951</SubAccountSymbol> </TreasuryCode> </SFC> XML

  9. Treasury Effort - Exporting from Database Before Database Query MAF: 0203 After Database Query MAF: <FiscalYearId>0203</FiscalYearId> Write <FiscalYearId> Just add literals to your database query

  10. Viewing FACTS II MAF Internet Explorer  XML Editor: XML Spy

  11. Edit Filter for DFAS Specific Requirements XSLT Filter Add/Change/Delete In XML speak, this file is called a “Stylesheet”; carry over from its document-centric past

  12. Run With Edited Filter to Create DFAS Specific FACTS II MAF Treasury All Agencies Filter * XML XML Edit XSLT Filter Example Agency Specific - DoD/DFAS * Open Source Program: XSL Tester

  13. Import Into DFAS Specific Data Store ‘What’ Not ‘How’ Importing Import * DFAS desired format, database, etc. XML Agency Specific - DFAS * GoXML Transform, Oracle XDK, or other means

  14. Discussion • Low hanging fruit (terms not entered in Registry) • Tag Length (allow short tag names to accommodate tool limitations) • Query with ‘Distinct’ (unique records only) • Record Type 7 • Other

  15. FACTS II MAF Relationship to SFC STAR SFC is MAF A B C D . . O P

  16. SFC - Standard Fiscal Code BACC - Budget Accounting Classification Code

  17. Premise • SFC has been determined to be the vehicle • SFC is important artifact for DFAS • Yet, its use outside DFAS isn’t wide-spread • SFC needs to be ‘marketed’ • Technology can assist communication • - Delivery mechanism • - Encapsulate complexity • - Provide for lower cost validation

  18. Background: Why is SFC an important DFAS artifact for business?

  19. External Users DFAS Internal SFC A B SFC is an important view into DFAS’ ontology C D . . O Managed Business Artifact P

  20. What is DoD’s strategy for marketing similar items to Standard Fiscal Code?

  21. One Mile Ahead...

  22. How can Technology Assist in Communication? Put it on today’s billboard - the Web Business Users & Developers

  23. ‘Marketing’ of SFC FIN - Finance and Accounting ACQ - Acquisition Logistics AOP - Aerospace Operations CFM - Configuration Management COE - COE CSS - Combat Support CXP - Controlled Exports ENT - DoD Enterprise GEO - Geospatial and Imagery GMI - General Military Intelligence GOP - Ground Operations LOG - Logistics MET - Meteorological and Oceanographic MSG - Messages PDT - Product Data PER - Personnel SEG - System Engineering SUP - Supply TAR - Tracks and Reports TBD - To Be Determined TRP - Transportation SFC A B C D . Business Users & Developers . O P

  24. MyTransaction SFC <MyStuff> <MoreMyStuff> <…> A B A C D B . Business Users & Developers . D O P

  25. MyTransaction

  26. SFC SFC SFC Communication Today Documentation Instance DFAS PROCESS One or more trading partners

  27. SFC SFC SFC SFC Communication Objective Complement Documentation with artifacts for automation Documentation Schema Instance DFAS PROCESS One or more trading partners And validate earlier in the information chain

  28. Work to date SFC As Defined By DoD 7000.14-R https:dfas4dod.dfas.mil/library/sfc.htm Treasury Code Fields A B A1 C A2 D A3 . A4 . A5 O A6 P

  29. Scope - Beyond just SFC SFC Additional Information Treasury Code Fields A B Name A1 C Other A2 D A3 . A4 For internal DFAS processing . A5 O A6 P

  30. Our Business Rules in a Format for Automated Validation DCR Business Users & Developers Harness the business domain in a ‘declarative’ template - vs. ‘procedures’

  31. Use-dependent Resolution The following example depicts how we can handle the challenge of exposing various levels of resolution: 1. For simple case 2. More fields (additional information) Global Local

  32. Use-dependent Resolution: View Instances 1 SFC as one code 2 SFC Fielded 3 SFC Fielded including DFAS internals 4 SFC Fielded including DFAS internals & Metadata

  33. Scope - Overloading SFC Additional Information Treasury Code Fields A B Name A1 C Other A2 D A3 . Much of the other information are overloaded valuesi.e. “Generally numeric with one exception.” A4 . A5 O A6 P

  34. Scope - Schema Definition SFC Additional Information Treasury Code Fields Registry A DCR B Name A1 C Ref A2 D Enumeration A3 . A4 . A5 O A6 P

  35. Why a Registry? Multi-field Requirements 1. Linking additional information, i.e. code list 2. Multi-fields to extend a field Just like relational databases, when serializing data we loose important linkage information which we usually document via a paper trail. It would be nice to have a better mechanism.

  36. Why a Registry? Multi-field Requirements - “ help from above ” In addition to enumeration, we include a reference to a Registry. DCR

  37. Registry UID VI304 Dollars Collaboration Partner #1 Collaboration Partner #2 X12 UnitPrice EDIFACT ListPrice Currency Schema or Template <Rep href= “http://www.DISA.mil”>SHADE</Rep> <ELEMENTname=‘ListPrice’uid =‘VI304’ > <Rep href= “http://www.DISA.mil”>SHADE</Rep> <ELEMENTname=‘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

  38. Q&A • Is the SFC approach an important artifact to expend additional resources and market? • If so, what does it cost? What do we get? • Is the return of investment sufficient to support the SFC at this time? • Are there other items in our pipeline of greater priority? Short term? Long term?

  39. Role of the DFAS DCR Put it on today’s billboard - the Web Workflow & Collaboration + DCR DoD Data Emporium Business Users & Developers

  40. Next Steps Where do we go from here?

  41. Fundamental Changes – Underlying Data Model SFC STAR A MAF ??? B C D . . . O . P No overloading of values! .

  42. Summary • Discussed MAF and changes required • Tools required for XML processing • Revisited rationale for SFC • Potential of wide-spread use of SFC • DoD Data Emporium as a marketing channel • How technology can assist communication • Discussed next steps Thank you

  43. XML Background

  44. XML Provides Leveling and Varying Types We can take great advantage of the ability to hold any type and structure… we can include metadata for describing this... UID Classword Legacy

  45. Choice • Set • Details XML Provides Leveling and Varying Types We can take great advantage of the ability to hold any type and structure… we can include metadata for describing this... Classword Three additional classwords to assist in describing XML tree structure:

  46. Choice • Set • Details Details Collection of differing types to describe a concept or logical unit. One concept Different attributes / types The least restrictive of the three

  47. Choice • Set • Details Set Collection of children that are of same type - equivalent to a rowset query result from a relational database.

  48. Choice • Set • Details Choice Where the tree branches for different child types (structures) or differing default values. Schema Instance A Selected B B C D The most restrictive of the three

  49. Versioning 1. Roll per component (UID) 2. Libraries / Files

  50. Substitution Group Synonym mechanism

More Related