The Future of XML at the IRS and Building Partnerships for Collaboration. Agenda

Transcription

1 FTA Technology Conference August 8 10, 2005 The Future of XML at the IRS and Building Partnerships for Collaboration Dynamic The Internal Revenue Service John A. Triplett john.a.triplett@irs.gov Sol Safran sol.safran@irs.gov Agenda IRS Enterprise Architecture IRS XML Transition Strategy IRS XML Framework XML Registry XML Components Data Exchanges 1

2 Much has been accomplished... The IRS has deployed several high impact applications that make life easier for American Taxpayers Where s My Refund Internet Refund, Fact of Filing (IRFOF) CADE version ez filers moved to new system e-services Self service applications for practitioners Modernized e-file Electronic filing of business returns Web Services interface being introduced Use of the Internet to enable a new value proposition for taxpayers and software developers and meet rising expectations Much Remains To Be Done We need to Shorten our development cycles Reducing our cycle times Simplify our infrastructure and the relationships between systems Modernize our data strategies So we can Enhance self service opportunities Enable taxpayer account access Publish XML based Application Programming Interfaces Retire the Master File 2

3 It s all About the Data The lack of ability to move data hobbles an organization s flexibility It s not lack of data, but lack of ability to get the data where it s needed Data needs to be moved and combined to turn it into information and get it to authorized consumers The ultimate goal: The zero latency enterprise Latency is our enemy Move from weekly cycles to daily, then instantaneous settlement The IRS Service Based Architecture (IRS/SBA) The IRS/SBA is the IRS implementation of a Service Oriented Architecture Loosely coupled. Places XML translators in front on existing IRS systems Provides quicker time to market as software resources are reused Shortens maintenance cycles by using XML as the wire and interface formats XML will protect software developer investment Event driven Publish and subscribe Provides data convergence Data from multiple sources is combined on the fly to turn it into information 3

4 IRS/SBA Adapters Applications Orchestration Integration Broker Web Services Interface XML Native formats IRS/SBA IRS ELDM Web Services Interface Schema Simple & Complex Elements (common components) Integration Broker Doc Types Ex: TaxpayerAddressCreate, TaxpayerAddressUpdate, etc. Repository DocTypes (IRS XML XSD) Flow Services Business Processes Service Input/Output 4

5 Benefits of the Service Based Architecture Services allow developers to focus on business logic and user friendly displays instead of where to get the data from and how to get it Hides the complexity of the infrastructure One entry point into the IRS External interfaces governed by standards Each application or service has exactly one interface to everything else Serves up authoritative information Developers deal with business information instead of data Reliable service delivery Stable interfaces through XML Faster time to market less code to write Each service can be upgraded and scaled independently (loose coupling) Transition Strategy to Modernized Data Stores IRS Internal Data Architecture Modernized Data Stores Legacy Data Stores Majority of IRS systems and infrastructure components have transitioned to the Modernized Architecture Remaining Legacy Data replicated in Modernized Format Majority of IRS data centric systems and infrastructure components have not transitioned to the Modernized Architecture Initial Modernized Data replicated in Legacy Format (e.g., CADE => IMF) Technology and Standards 5

6 Transition Strategy to XML Data Exchange Legacy Data Exchanges XML Standards and Technology maturing And/or Tax Administration sector adoption of Standards and Common Vocabularies not yet mature Modernized Data Exchange XML Standards and Technology stable (though still evolving) And Tax Administration sector adoption of Standards and Common Vocabularies mature (and growing) IRS External Data Exchange Drivers Technology and Standards IRS Transition Strategy Legacy Data Modernized Data IRS Internal Data Architecture Legacy Format Modernized Format Use Adaptors to translate from Modernized format to Legacy. Current State Target State Use Adaptors to translate Legacy formats to Modernized format Optimal Path Outpace Standards Trail Standards Where we are Today IRS External Data Exchange 6

7 What This Means The vertical line, IRS modernization progression, is a driver for how the IRS manages data internally The horizontal line, maturity of XML technology and standards in the industry, is a driver for how the IRS will exchange data with our external partners This is a principle, some data exchanges may transition prior to others. Prototypes/pilots will be strategies for discussion. Overview IRS XML Framework Objective: Identify the target state of XML technology implementation for the IRS Assess and adopt appropriate standards, practices, and tools for the IRS and its trading partners Strategically transition current systems and legacy formats to modernized XML data exchange formats Adapted from a Department of Education, Federal Student Aid briefing. XML: A Beginners Guide Presented at the 2003 Electronic Access Conference in San Diego, CA. 7

8 Current IRS XML Standards and Governance Initiatives IRS XML Community of Practice (Chartered) Organize internal activity Collaborate on adoption of industry standards Form and vet IRS responses to external communities of practice Naming and Design Rules (NDR) Draft UBL based NDR circulating for comment XML Registry, Repository and Registration process Concept of Operations and alternatives analysis Common component schema Building blocks for composing IRS schema Integral to IRS/SBA Tax Filing vocabulary derived from existing MeF schema XML Registry Concept 8

9 Common Component Building Blocks The Common Component Approach is in a design phase. This is one concept, borrowed from Federal Student Aid. IRS NDR, Common Components, and MeF IRS NDR is in a comment and review period Federal NDR is in an earlier comment phase UBL 2.0 is close to draft release IRS NDR will align with Federal NDR and UBL 2.0 Approach to MeF Capture vocabulary into common component schema from existing MeF schema Prototype NDR conformant schema for MeF Assess impact and feedback to Federal WG and UBL TC Publish common component schema for Tax Filing Target MeF Release 5.0 for NDR conformance 9

10 Some xmlcop & Working Group Issues XML Performance and Size Standards Interoperability Naming & Design Rules Schema Versioning and Governance XML Registry Transition XBRL Many Others! IRS Partners for XML Policy and Standards Federal CIO s Council Working Groups XML Community of Practice (xmlcop) Semantic Interoperability CoP Federation of Tax Administrators (FTA) TAG TIGERS OASIS Tax XML TC UBL TC Universal Business Language (UBL 1.0) ebxml Registry TC 10

11 Data Exchange Scope Current IRS/State Exchanges No Format Changes Pending! There are no immediate plans to change the format of existing files. The future state and how we get there will be designed with close communication and collaboration between the IRS and our external partners. New exchanges will be standards driven. 11

12 Beyond MeF The IRS has worked closely with the TIGERS on MeF. MeF is just one of many taxpayer data exchanges. As a new system, it was one of the first to implement XML on a large scale. As legacy systems transition and new data exchanges are created, the IRS will continue to partner with the FTA and TIGERS to plan and manage this change. For example: E-Services, GLDEP & EODAD. XML vocabularies, policy and standards will be harmonized with Federal, state and local, industry and International communities. Contact John Triplett Doug Peterson Sol Safran Enterprise Data Management Office (EDMO) John.A.Triplett@IRS.Gov Electronic Tax Administration (ETA) Doug.E.Peterson@IRS.Gov Prime Enterprise Data Management (EDM) Sol.Safran@IRS.Gov

13 Back-Up Slides Some slides with examples of issues under discussion IRS Governmental Liaison Data Exchange Program (GLDEP) Data Extracts from various IRS master files and databases Shared with state and local tax administrations Currently 15 GLDEP data extracts Agencies enroll annually and select which extracts they wish to receive 13

14 Current Extracts 1099 Misc BMF/BRTF Corporate Affiliations CP 2000 Exam/Appeals FEIN (Federal Employer ID Number) IMF/IRTF IRMF Levy Military Combat Zone Non-Itemizer PTIN (Preparer Tax ID Number) TAR (Taxpayer Address Request) Examination Operational Automation Database EOAD is a relational database using different files within one database for different purposes Data is separated first by type of return (Form 1040, 1120, 1065, and 1120S) and then by type/purpose of records (Entity, Issue, Other, and Partners) 14

15 Compressibility of XML translate XML 11,421,822 bytes 674,062 bytes txt WinZip 148,294 bytes 94,369 bytes The compressed version of the XML document is smaller than the compressed version of the original document! Ref: Dan Winkowski MITRE XML Intro for Managers 15