Leveraging XML

1
Leveraging XML
Eric Okin Assistant Deputy Director Policy and
Architecture DFAS - DTB
Mike Lubash XML Team Leader DoD Finance and
Accounting Namespace Manager
2
Objective of the Presentation...

• Setting the Tone...
• Why XML?
• Atomic Identifiable Content Actions
• Structural Transactions Processes
• Contextual Context Defined Business Constraints
• Impact on Our Organization

How are we going to approach the topic?
3
Change favors the prepared mind.
Louis Pasteur
Why should I learn how to be positioned to
leverage XML for eBusiness?
4
Setting the Tone Why Has Interoperability Been
Elusive?

• Proprietary we have been shackled
• data, metadata, applications, database,
  operating systems, and user interface
• Strategy based on one size fits all
• DCII focus on homogenous (type III) systems
• standards without good mechanisms for allowing
  for context
• Absence common services and exchange
• example ANSI X12 Electronic Data Interchange
  (EDI) restrictive scope, door-to-door,
  difficult to repurpose, not real-time, not for
  web, long turn-around to add to standard,
  messages are extensible thus a decline in usage

Why has it taken 20 years for the right solution?
5
Setting the Tone Business-driven Information
Architecture

• Agility to meet customers evolving needs
• Interoperability ease of integration enabled
  by open technology
• Reusability data in usable form and
  repurposable
• Understandability declarative semantics of
  the business
• Quality exact exchange of information

What architectural qualities are required to
address the challenge?
6
Setting the Tone Electricity Analogy
Explaining XML technology today is much like
explaining electricity during the era of
gaslights
Why do I need electricity, my gaslights work
fine?
Computers Light bulb Electrons
Joseph Priestley's Laboratory, c. 1775
How does one explain the benefits of
business-driven information architecture?
7
Setting the Tone XML Provides Key Basic Benefits

• Agility pervasive, easy to learn, large
  labor pool, business defines message semantics
• Interoperability simple open portable
  format ltItemNogt41358lt/ItemNogt
• Reusability open transformations XSL, on the
  web in real-time
• Understandability extensible tags defined by
  users and developers, searching
• Quality open mechanism for defining and
  validating exchanged data - schemas

Why XML?
8
Setting the Tone Achieving Advanced Business
Constructs

• 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
XML Technology
1 Heterogeneous Interoperability
Easy

• Improve the delivery, timeliness, and accuracy of
  Finance and Accounting services in key areas

• Define and start implementing compliant
  architecture

• Start enterprise management of information and
  knowledge assets

What are the foundation components which to build
success?
9
Setting the ToneEnterprise XML Implementation
Strategy

• Agility declarative approach identify
  impact of change and provide gap analysis
• Interoperability Enterprise Information
  Services Layer - EISL
• Reusability common services, common
  information artifacts (reusable components)
• Understandability discovery via
  collaborative ontology (registry-centric)
• Quality concept-based transformations with
  explicit logical context-root derivations

What mechanisms do we need to move to an
enterprise strategy?
10
Setting the Tone XML alone is not enough
to provide us a complete eBusiness solution

• XML, by itself, does not solve interoperability
  problems, yet it is an important tool for doing
  so
• XML does not provide instant semantics, yet its
  tagging structure assists with parsing the data
• XML does not eliminate mapping and the No single
  standard can be imposed rule still applies, yet
  with a framework built around open declarative
  processes the amount of integration resources
  required are reduced
• XML by itself is not the magic bullet
• but a business-driven information
  architecture gives us a chance

What XML is Not?
11
Setting the Tone XML is Here To Stay

• There will be no more new versions of HTML
• W3C states XML with HTML-type tagging XHTML
  is the future
• Very few, if any, new EDI Transaction Sets will
  be added to X12/EDIFACT
• Since introduction of the idea of exchanging
  business documents by the XML/edi Group in 1997,
  an unprecedented number of exchange definitions
  and uses have been developed and a plethora of
  tools have appeared on the market.
• "The market for Web Services tools, comprised of
  Web Services Platforms, Application Development
  and Delivery Suites, and Operations Management is
  expected to grow to over 15.5 Billion by the end
  of 2005."
• ZapThink
  Research

Is XML another flying by technology?
12
The Lowest LevelAtomic Identifiable Content
Actions
What is unique with XML and what do I gain by
tagging my information?
13
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. Context Views
What are the characteristics of native XML which
makes it an enabler?
14
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. Context Views
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 doesnt require large amounts
of specific training to leverage.
How easy is it to work with and assimilate into
my organization?
15
1. Lowers the Bar alternative to over the
fence
Business Operational View Domain aspects of
business transactions
Improving communication between business domain
experts (what) and technologist (how) to
maximize new exciting opportunities.
Technology Service View IT aspects of business
transactions
Does XML help in communications between business
and technical staff?
16
1. Lowers the Bar Easy To Read
ltItemNogt41358lt/ItemNogt
What does example XML look like?
17
1. Lowers the Bar Easy To Read (cont)
lt?xml version"1.0" encoding"UTF-8" ?gt -
ltSGLAccountsgt ltReportingDeptgtDept. of the
Armylt/ReportingDeptgt ltAccount Number"1010"
NBI"D"gt34507584472lt/Accountgt ltAccount
Number"1110" NBI"D"gt436988lt/Accountgt
ltAccount Number"1120" NBI"D"gt12112353lt/Accountgt
ltAccount Number"1130" NBI"D"gt0lt/Accountgt
ltAccount Number"1190" NBI"D"gt145618807lt/Accou
ntgt ltAccount Number"1195"
NBI"D"gt0lt/Accountgt ltAccount Number"1200"
NBI"D"gt57747632lt/Accountgt ltAccount
Number"1310" NBI"D"gt688542592lt/Accountgt
. .
Back ARMY 1010D34,507,584,4721110D436,988112
0D12,112,353 1130D01190D145,618,8071195D01200D57
,747,632 1310D688,542,5921310D357,282,8391319C0
1319C-41,291,4191320D01320D01330D0
If XML
If Flat File...
If EDI...
What is easier to understand and search?
18
1. Lowers the Bar Example
lt?xml version "1.0" encoding
"UTF-8"?gt ltEmailgt lt/Emailgt
So what does an XML document or report structure
look like?
19
1. Lowers the Bar Example
lt?xml version "1.0" encoding
"UTF-8"?gt ltEmailgt ltHeadgtlt/Headgt ltBodygtlt/Bodygt
ltAttachmentsgtlt/Attachmentsgt lt/Emailgt
So the structure is hierarchical?
20
1. Lowers the Bar Example
lt?xml version "1.0" encoding
"UTF-8"?gt ltEmailgt ltHeadgt ltDategtlt/Dategt ltFrom
gtlt/Fromgt ltTogtlt/Togt ltCCgtlt/CCgt ltBCCgtlt/BCCgt lt
Subjectgtlt/Subjectgt lt/Headgt ltBodygtlt/Bodygt ltAttac
hmentsgtlt/Attachmentsgt lt/Emailgt
So can I group information anyway my business
needs it?
21
1. Lowers the Bar Example
lt?xml version "1.0" encoding
"UTF-8"?gt ltEmailgt ltHeadgt ltDategt02/05/02lt/Dategt
ltFromgtBruce.Johnson_at_dfas.millt/Fromgt ltTogtAtten
deesListlt/Togt ltCCgtMike.Lubash_at_dfas.millt/CCgt ltB
CCgtBruce.Johnson_at_aol.comlt/BCCgt ltSubjectgtThank
Yoult/Subjectgt lt/Headgt ltBodygtThank you for
making our meeting a great success!lt/Bodygt ltAttac
hmentsgtd\notes.txtlt/Attachmentsgt lt/Emailgt
So what does the XML document or report look like
with information?
22
1. Lowers the Bar Skills Across Organization

• Our available labor pool for tasking is
  increased, as base technology is common between
  capabilities

• Skills learned can be applied to many different
  areas. Reduction in education requirements
  specific to tasking,

Labor Pool
Other impacts are discussed later in the
presentation
What impact does Easy to Read have on my
organization?
23
1. Lowers the Bar Invoice Example
EDI - 30
XML- 50 ?
Web - 20
How do we lower the bar to reach to automate
additional trading partners?
24
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. Context Views
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).
What impact does XML have to do with my
infrastructure?
25
2. Independence
Oh, Freedom!
DFAS information is now free from Operating
Systems, Applications, Databases, Software
Language, Presentation, etc.
How does XML remove the proprietary shackles from
important?
26
2. Independence Triad
platform
Internet / HTTP
HTML
XML
presentation
data
XML Makes Information Portable
What happened in the past with HTML/HTTP when
shackles were removed?
27
3. Independence - Allows Reuse
ltWAP / WMLgt
XML/edi ltSOAPgt
So XML is like having a cut and paste
capability for automation?
28
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. Context Views
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.
What types of information does XML support?
29
3. Universal Clipboard Tables More!

• XML support information housed in
• databases, and other organizations stores,
  etc.
• Allows for flexible structures
• Faster no time consuming RDBMS table joins
• Fastest able to be memory-based
• No installation required, eases deployment
• Low or No cost to deploy
• Remember non-proprietary, vendor neutral

Plus more!
How does XML complement my RDBMS?
30
3. Universal Clipboard Common Access
Common nodal access/viewpoint allows for common
parsing mechanisms So even though content of
XML can be any information, access is kept to a
very simple document model.
Structure Integrity at two levels 1
Well-formed and 2 Validated via schema
How easy is it to use and manipulate XML?
31
3. Universal Clipboard Persistence Use Cases
Tactical

• Workflow
• Transactional at application server

• XML usage increase
• Typically legacy DB
• RDBMS in the past

Operational

• Knowledge rich structures
• Information mining
• Complex searching

Warehouse

• Metadata
• Constraints
• Crosswalk relations
• Varied info structure

Registry

• Application persistence
• Complex searching
• Packaging / serialization

Configuration

• Personalization
• Role-based security
• BizID exchange

Profile
Queue

• Message middleware
• End-to-end statusing
• Loose-coupling architectures

What are the use for storing my information in
XML?
32
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. Context Views
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.
What are the limits of XML structure to describe
my business?
33
4. Granularity - Indenture Levels
EDI
XML
Very Rich Unlimited Number of Levels
Restricted 3-4 levels only
Can be extended via complex Hierarchical
Looping (HL) mechanism
How does XML compare to EDI for model resolution?
34
4. Granularity - Indenture Levels
Able to filter, query, extract, and manipulate
information anywhere
XML
without having to map transaction to RDMS
fields.
How does XML compare to EDI for model resolution?
35
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. Context Views
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.
Sounds like standard tags to me, how is XML
specific to my needs?
36
5. eXtensible Have It My Way

• XML is a meta-language
• XML standard doesnt define the tagnames.
  XML allows for the organization to define its own
  set of tags based on its business need.

• How does this differ from other standards in
  the past, e.g. EDI?

EDI standards define the tagnames and transaction
structures based on committee if this
worked then why are only 10 or less of the
exchange types in the organization standard?
XML is a meta-language, What is a meta-language?
37
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. Context Views
minimal prior knowledge of sender application is
necessary to process information. Not positional
or delimiter defined, thus allowing flexible
packaging based on business needs.
How does XML assist in understanding the message
my semantics?
38
6. Semantic References Machine Interchange
Fixed Width - Version 1
1010D34,507,584,4721110D436,9881120D12,112,353
1130D01190D145,618,8071195D01200D57,747,632324545
4721110D436,9881 0D357,282,8391319C0319C-41,291,41
91320D01320D013300 4721110D436,9881120D12,112
Delimited - - Version 2
1010D34507,58 4,4721110D4369881120D12112,
3531130D01190D145,618,8071195D012003233
D57,747,632324545 4721110D436,9881
0D357,282,8391319C0319C-1,291,4191320D013
20D0
If the sender adds one other field the receiving
program needs to be modified or the interchange
breaks
What is wrong on how we are doing it today?
39
6. Semantic References Version 3 Segmented
EDI X12
New data elements dont break the exchange
To interpret the fields the EDI parser needs to
reference the EDI standards to field the data
STD
What about EDI?
40
6. Semantic References v.4 Smart Delimiters
XML
ltDategt02/05/02lt/Dategt ltFromgtBruce.Johnson_at_dfas.mil
lt/Fromgt ltTogtAttendeesListlt/Togt ltCCgtMike.Lubash_at_dfa
s.millt/CCgt ltBCCgtBruce.Johnson_at_aol.comlt/BCCgt ltSubje
ctgtThank Yoult/Subjectgt
The XML parser will not break if a field is added
to the exchange and knows immediately context of
the information -more later
Is there a transaction expression format that
gives us integrity?
41
6. Semantic References EDI Comparison
Declarative Processing ltFromgt ltTogt
ltSubjectgt
XML
DoA
ltDategt02/05/02lt/Dategt ltFromgtBruce.Johnson_at_dfas.mil
lt/Fromgt ltTogtAttendeesListlt/Togt ltCCgtMike.Lubash_at_dfa
s.millt/CCgt ltBCCgtBruce.Johnson_at_aol.comlt/BCCgt ltSubje
ctgtThank Yoult/Subjectgt
DoB
DoC
EDI the semantics is positional based on
delimiters, how is XML different?
42
6. Semantic References
Declarative Processing ltFromgt ltTogt
ltSubjectgt
XML
DoA
ltDategt02/05/02lt/Dategt ltFromgtBruce.Johnson_at_dfas.mil
lt/Fromgt ltTogtAttendeesListlt/Togt ltCCgtMike.Lubash_at_dfa
s.millt/CCgt ltBCCgtBruce.Johnson_at_aol.comlt/BCCgt ltSubje
ctgtThank Yoult/Subjectgt
DoB
DoC
But this is only half the story, more later on
interpreting message semantics
Isnt semantics based on greater context than the
tagname?
43
Why XML?Atomic Features of XML Technology
1. Lowers the Bar 2. Independence 3.Universal
Clipboard 4. Granularity 5. eXtensible 6.
Semantic References 7. 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.
So the tags provide semantics, how does this help
in my processing?
44
7. Context Views Multiple levels of Resolution
give multiple views of the information.
High Resolution
Low Resolution
e.g. External Organization Viewpoint
External Organization Viewpoint

XML provides multiple views (high and low
resolutions) which allow for additional
constraints for processing where as RDBMS
tables, no views are not included in the
structure. With RDBMS tables, the relationships
give a hint as to the possible views
Internal Organization Viewpoint
Can XML provide view constraints for processing?
45
7. Context Views Users Choice
Response delays accessing database, and table
joins may not be offer scalable solution
Users can choose to slice n dice the information
on their browser without constantly returning to
backend servers for more data.
Web Server
Relational Database
Slow
X
Web Browser
XML Store
Fast
Design Option rendering at server or client
Content Server
How can XML speed processing for my customers
web experience?
46
The Intermediate Level Structural Transaction
Processes
What do I gain if I add structure and processes
around my XML?
47
Why XML?Structural Processing Features of XML
Technology
8. Schema 9. Stylesheets 10. Processing 11.
Web Services 12. Workflow
How does XML assist in understanding the message
my semantics?
48
Why XML?Structural Processing Features of XML
Technology
8. Schema 9. Stylesheets 10. Processing 11.
Web Services 12. Workflow
Mechanism for expressing technical aspects of XML
Instances, e.g. structure
How does XML assist in understanding the message?
49
8. Schema Metadata Instance
ltxselement name"Head"gt ltxscomplexTypegt
ltxssequencegt ltxselement name"Date"
type"xsstring"/gt ltxselement name"From"
type"xsstring"/gt ltxselement name"To"
type"xsstring"/gt ltxselement name"CC"
type"xsstring"/gt ltxselement name"BCC"
type"xsstring"/gt ltxselement name"Subject"
type"xsstring"/gt lt/xssequencegt
lt/xscomplexTypegt lt/xselementgt
SCHEMA Open format to indicate the meaning of the
fields, data types, optionally and structure
INSTANCE Must adhere to the business rules
defined in the Schema
ltDategt02/05/02lt/Dategt ltFromgtBruce.Johnson_at_dfas.mil
lt/Fromgt ltTogtAttendeesListlt/Togt ltCCgtMike.Lubash_at_dfa
s.millt/CCgt ltBCCgtBruce.Johnson_at_aol.comlt/BCCgt ltSubje
ctgtThank Yoult/Subjectgt
Is XML Schema open like XML?
50
8. Schema Treasury Reporting Example
Treasury
DFAS
Including Notes
Valid
XML Schema
Shared Rules
Other Agencies
Defines message implementation in format for
automation
XML
Valid
How do we reduce errors and exchange data and
document type information?
51
Why XML?Structural Processing Features of XML
Technology
8. Schema 9. Stylesheets 10. Processing 11.
Web Services 12. Workflow
Open transformation specification and
availability of open tools
How do we transform my XML information?
52
9. Stylesheets Capabilities
XML
HTML

1
XML Any XML application (e.g. WML, XHTML)
XML
XML
2

1010D34,507,584,4721 121130D01190D145,6 1310D688,5
42,592131 1319C-41,291,4191320
XML
Flat File Comma Delimited, Fixed-Width, Special
(e.g. printer file)

3
What can a stylesheet do for me?
53
9. Stylesheets Mechanics Overview
Source Building Oracle XML Applications By
Steve Muench
What can a stylesheet do for me?
54
9. Stylesheets Past Paper Documents
Documentation
Instance (transaction/report)
App
App
What other information do I share?
55
9. Stylesheets Validation / Interpretation
Automation!
Stylesheets ltIfgt ltthengt
Documentation
Instance (transaction/report)
App
App
Low Cost Check for some errors at the sender
and receiver
What other information do I share?
56
9. Stylesheets Package
Stylesheets ltIfgt ltthengt
4
2
Stylesheets, maps validation programs
Structure for each document/ message and/or
language component
Documentation
Overview, Use Cases, Sequences, Data Dictionary
3
Instance (transaction/report)
1
Examples, Test Programs
Standards
5
Standards, notes on mappings, subsets and
deviations
What other information do I share?
57
Why XML?Structural Processing Features of XML
Technology
8. Schema 9. Stylesheets 10. Processing 11.
Web Services 12. Workflow
Moving XML Instance information in and out of
messages and data stores
How does XML get in and out of my database,
messages, etc.?
58
10. Processing - Exporting from Database
Just add literals to your database query
How do I extract XML from my database?
59
10. Processing Tools Export in XML
Database
Export
Report
ltItemNogt41358lt/ItemNogt
Spreadsheet
How do I extract XML from my database?
60
10. Processing - Inbound

• Web Browser
• - Stylesheet
• Import
• XML Store/Query
• Translation
• - Stylesheet
• - Software Program
• - Mapping Product

App
How to process my XML document/report into my
database?
61
10. Processing Reducing the Mapping Alternative

• want a data mart of transaction data, but all
  current options require further map development

• desire a capability for XML-based communications
  and processing, without requiring more map
  development

Option A Translation
Fielded (RDBMS)
EDI or XML Feed
Reports
Mapping
Query
Option B XML Store/Query
Reports
Simple Conversion
XML Indexed
Query
How do Translation and XML Store/Query
alternatives compare?
62
10. Processing Universal Clipboard Hybrid
Reduce mapping by using clipboard technique
reduces DBA efforts
Format 1
Buffer
Relational Database
Reports
Query
Query for only Required Elements
Query
Format 2
Archive
Format 3
Retain Transactions in Exact State for Auditing
How do I use the Universal Clipboard aspect of
XML for integration?
63
10. Processing Translation
Tools to express what not how
How do easily map XML into other formats and
databases?
64
10. Processing Web-to-Legacy Example
Past
App
X12 or legacy process
Web
Tform
Web
HTML
Front-ending legacy processes with the Web brings
a distributed user interface, but we need more
Tform Transformation
How do I automate my current Web interfaces?
65
10. Processing Web-to-Legacy Example
Reuse Today
App
X12 or legacy process
Web
Tform
Web
HTML
Front-end any legacy process with XML to extend
the process life by allowing automation in
addition to the Web interface
Adaptor
App

• XML
• WML (Wireless XML)
• SOAP (Web Service XML)

How do I automate my current Web interfaces?
66
10. Processing Posting Example
Reuse Today
App
X12 or legacy process
Web
App
Tform
XML
First Web Services
What if I want to interface through my Web
interfaces?
67
Why XML?Structural Processing Features of XML
Technology
8. Schema 9. Stylesheets 10. Processing 11.
Web Services 12. Workflow
Remote procedure calls over HTTP, to invoke
processes, making truly distributed processing
across the enterprise
How does XML assist in understanding the message
my semantics?
68
11. Web Services Exchanging Information
Prior to XML, each application interface used
different transport protocols. With tightened
security, setting firewall parameters were
usually difficult, especially when
troubleshooting multiple routes and through
multiple levels
App
App
What is going on to simplify the exchange?
69
11. Web Services XML Interfaces
Most enterprises let HTTP-based messaging through
their enterprise for Web access, XML riding on
HTTP eliminates firewall problems
App
App
XML
XML
HTTP
Simple common reusable protocol
What is going on to simplify the exchange?
70
11. Web Services Simple Object Access Protocol
App
App
XML
XML
Service
Service
SOAP
Simple common reusable protocol and service
definition
What is going on to simplify the exchange?
71
11. Web Services Major Vendor Participation
Oracle Dynamic Services Framework
e-Services
What Web Services support can I expect?
72
11. Web Services Making sense of the offerings
So we have implementation options?
73
11. Web Services Other Protocols
Where does Web Services fit from a protocol
viewpoint?
74
Why XML?Structural Processing Features of XML
Technology
8. Schema 9. Stylesheets 10. Processing 11.
Web Services 12. Workflow
XML ability to address the persistence issues
with workflow within the enterprise pipeline and
the impact XML brings on business
How does XML assist higher level business
processes?
75
12. Workflow
Messages can be extended build per pipeline
requirements. No database management headaches,
information can be both data-or
document-oriented, with componentized Stylesheet
per unique view.
Station 1 Station 2 Station 3
Station/user specific information about the
message may be kept in the message, e.g.
transaction key, which each node is unique
How does processing and metadata help with my
workflows?
76
12. Workflow Smart Documents
Transactions/Documents can include rich metadata
such as business rules, routing, statusing,
triggering, signatures, presentation, validation,
etc. World is becoming more
document-centric
How can additional metadata can assist automation?
77
12. Workflow XForms

• Draft describes the architecture, concepts,
  processing model, and terminology underlying the
  technology that can be used with a wide variety
  of platforms of varying capabilities
• desktop computers,
• television sets,
• personal digital assistants,
• cell phones,
• computer peripherals
• The XForms User provides a standard set of visual
  controls that are targeted toward replacing
  today's XHTML form controls. Other groups, such
  as the Voice Browser Working Group, are
  independently developing user interface
  components for XForms. Workflow, auto-fill, and
  pre-fill form applications are supported through
  the use of instance data.

Is there a standard for complex user interfaces?
78
12. Workflow XForms

• PL 105-220, 1998 HR 1385PL 105-220, enacted on
  August 7, 1998, 112 Stat 936codified as Section
  504 of the Rehabilitation Act, 29 U.S.C. 794d
• WORKFORCE INVESTMENT ACT OF 1998

SEC. 508. ELECTRONIC AND INFORMATION TECHNOLOGY.
(a) REQUIREMENTS FOR FEDERAL DEPARTMENTS AND
AGENCIES.-- (1) ACCESSIBILITY.-- (A)
DEVELOPMENT, PROCUREMENT, MAINTENANCE, OR USE OF
ELECTRONIC AND INFORMATION TECHNOLOGY.--When
developing, procuring, maintaining, or using
electronic and information technology, each
Federal department or agency, including the
United States Postal Service, shall ensure,
unless an undue burden would be imposed on the
department or agency, that the electronic and
information technology allows, regardless of the
type of medium of the technology-- (i)
individuals with disabilities who are Federal
employees to have access to and use of
information and data that is comparable to the
access to and use of the information and data by
Federal employees who are not individuals with
disabilities
Can XML help with 508 compliance?
79
12. Workflow Impact Yesteryear
Treasury
DFAS
DoD
So how does XML effect collaboration for my
organization?
80
12. Workflow - Impact with XML Technology
Treasury
DFAS
DoD
Door-to-Door No More so XML reduces
reformatting, right?
81
12. Workflow - Key Support
Value Chain
1
2
3
n
.. .




1. Function Requests Tracking Number
3. Function Submits Status With Alias
4. Function Submits Status Using Alias
6. Query for more additional information
2. Service Returns Generated Number
Function ID Alias Type
1 Gen 2 2332
3 2332
End-to-End Tracking Service
Function ID Tracking Alias Type Alias
Timestamp
7. Query service network (if required)
1 123456
01911000 2 123456
2332 888888 01911011 3 2332
888888 01913761
5. User submits Query
Can you give an example how Web Services can
support workflow ?
82
The Highest Level Contextual Context Defined
Business Constraints
So how does XML enable my organization to be more
intelligent and agile?
83
Why XML?Contextual Context Defined Business
Constraints
13. Registry 14. Semantics 15. Context 16.
Templates 17. XML Strategy 18. Architecture
What is the upper scope of this presentation?
84
Why XML?Contextual Context Defined Business
Constraints
13. Registry 14. Semantics 15. Context 16.
Templates 17. XML Strategy 18. Architecture
The registry coupled with a repository allows
those business artifacts deemed to have value to
be registered and managed more easily than
alternate methods
How does a Registry enable my business users and
developers?
85
13. Registry Requirement for Services
Registry is used to assist users at design time
and runtime to provide help from above.
Information contained is data that supplements
the transaction/document based on context
Registry
App
App
XML
XML
Service
Service
SOAP
Where is the metadata stored for levels above the
exchange?
86
13. Registry Universal Description Discovery and
Integration

• White Pages -
• DUNS - Data Universal Numbering System
• Thomas Registry
• Yellow Pages -
• SIC Standard Industrial Classification
• NAICS North American Industry Classification
• UN/SPC Standard Products and Services Code
• Green Pages
• Information on APIs and EDI

Version 3.0
What Web Services support can I expect?
87
13. Registry Store of Zachman Framework Artifacts
What support does the Registry give to
development?
88
13. Registry Metadata Management
         
 
Collaboration Partner Agreements
Collaboration Partner Profiles
5
Contract
Business Integration
Workflow
4
BP Specification
Process
XForms
Specifications Schema
3
Messages
Assemblies
Artifact relationships
Motivation Time People
2
Presentation
Rules
Events
Roles
Directory Services
Technology Integration
Data/Codes Services/Functions
Network
1
MSH/SOAP
Verbs
Transport Routing, Packaging
Nouns
Leverage our information assets for emerging
eBusiness-centric world
What are the business artifacts we need to manage?
Source Lubash Pyramid
89
13. Registry Registry / Repository
Repository
Registry
Registry Entry UID Common Name Submitting
Organization Description Object
Type Version Status
External Links
Classifications NAICS/UNSPSC Country Gov't
agency Sport category Org. type
Associations UID Validates to UID Contains Superce
des Uses
Alternatives Name Description
What type of information is stored in the
Registry vs. Repository?
90
13. Registry Business Artifact Associations
How do I develop my business ontology?
91
13. Registry People Associations
Query the DoD XML Registry to contact those
associated with business artifacts to obtain
additional information
DoD XML Registry
Who?
1
Contact Info
2
3
Users in community of interest groups are
notified upon registry updates
How does the registry assist with collaboration?
92
Why XML?Contextual Context Defined Business
Constraints
13. Registry 14. Semantics 15. Context 16.
Templates 17. XML Strategy 18. Architecture
The meaning of the document / message and
described here, why assuring understanding is the
real challenge in integration
How does XML assist in understanding the message
my semantics?
93
14. Semantics - Critical Communication Metric
Communication Levels
Packaged Solutions
Management Level Degree of Control
Minimum Level
Metadata Management SEMANTICS
So why do I need to manage my metadata?
94
14. Semantics - The Ever Changing Enterprise
Content
Some of our artifacts are more stable than others
Vocabularies
Interfaces
Enabling Technologies
Services
Need to build on solid base
Navigation Systems
Portal Effort
Ontology Full Business Semantics
What happens if my metadata isnt well managed?
95
14. Semantics Strategy Model
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
How intelligent is our organization?
How does metadata management lead to business
intelligence?
96
Why XML?Contextual Context Defined Business
Constraints
13. Registry 14. Semantics 15. Context 16.
Templates 17. XML Strategy 18. Architecture
Semantics requires context for full understanding
How does context assist in understanding my
message?
97
15. Context - Business Layers Physicalization
CoI Community of Interest
2
1
Conceptual Architectural
CIQ
USPS

CPP
3
Constraints, Context, Structure
Logical
CPA
5

• AssemblyDocs
• Spreadsheet

4
Physical Implementation

• transaction
• schema
• instance

How does levels of indirection built upon
business context work?
98
15. Context - Conceptual Layer
Classification grouping
Alignment Mapping
Business Concept
Business Codelists
CoI Community of Interest
Association structure

Generic Assembly e.g. invoice
Generic Subassembly e.g. address
Logical

• AssemblyDocs
• Spreadsheet

Physical Implementation
Relationship
What are the major conceptual components?
99
15. Context - Logical Layer

• Trading Partner IDs
• Service Parameters
• Environment
• Security

Conceptual
ECCMA
OASIS CIQ
DoD Registry
USPS
CPA

• Mandatory vs Optional
• Subsetting Codelists
• Resolution / Indenture

Logical
Business
Business
Business
Business
Process BPSS
Technology
Technology
Technology
Workflow Sequence Set
Technology
Physical Implementation

• Elements vs Attributes
• Length, Datatyping Masking
• Routing Packaging

• Process ID
• Workflow Step

What are the drivers, and types of definitions
that make up the logical layer?
100
15. Context - Physical Layer
Conceptual
ECCMA
OASIS CIQ
DoD Registry
USPS
CPA
Logical Business Layers

• AssemblyDocs
• Spreadsheet

• Instance
• Business Content

Document / Transaction Schema
Physical
Payload
Payload
Interchange / Header / Control

• Environment

How are Physical messages defined, and instance
information carried?
101
15. Context Supporting Communication
Business (Logical)
Collaboration Partner 1
Collaboration Partner 2
Registry Metadata Management
XML Instance
XML Instance
Data
ltPartNogt999lt/PartNogt
ltPartNumbergt999lt/PartNumbergt
ltTypegtAutolt/Typegt
Machine-to-Machine (Physical)
How does a registry provide help from above?
102
15. Context Metadata-driven User Interfaces
User interface e.g. Browser
Disparate data sources
Linked and dynamically generated

Registered components
User interface component assignments
How do I use XML to drive dynamic and
personalized Web interfaces?
103
Why XML?Contextual Context Defined Business
Constraints
13. Registry 14. Semantics 15. Context 16.
Templates 17. XML Strategy 18. Architecture
Templates let both collaboration partners
understand and digest a message manifest
What can I do to assure we are inline with
understanding a message?
104
16. Templates What is harder sending or
receiving?
Hint An analogy is playing catch with a ball
105
16. Templates - What is harder sending or
receiving?
Mapping (Version 1)
Template (Version 2)
App
App
Domain
Std
Trans
Trans
Map
IC
Instance
IC
Instance
Template
Specific
Across Domain
Trans
Map
Registry Preferred
App
App
So, the Template provides the receivers desired
format and structure??
106
Why XML?Contextual Context Defined Business
Constraints
13. Registry 14. Semantics 15. Context 16.
Templates 17. XML Strategy 18. Architecture
Rolling it all up XML Implementation Strategy
How does XML assist in understanding the message
my semantics?
107
Proposed DFAS Implementation Strategy
Lieberman Government needs plan for adopting
XML By Gail Repsher Emery Staff Writer Sen.
Joseph Lieberman, D-Conn., called on the Bush
administration April 10 to develop a plan that
would enable information sharing through
governmentwide adoption of extensible markup
language, or XML. XML facilitates data sharing
by tagging information so it can be read easily
by different computer systems. Lieberman,
chairman of the Senate Governmental Affairs
Committee, made the recommendation in response to
a General Accounting Office report that analyzed
the challenges of implementing XML.

• "We have at our fingertips technology that will
  greatly improve communication among the federal,
  state and local government agencies and among all
  Americans

• Work with Federal and industry groups
• Work with DoD XML Namespace / Registry

Do we have a strategy for implementing XML?
108
17. XML 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

Technology Service View IT aspects of business
transactions
What are the principles of our Strategy?
109
17. XML Strategy
XML Implementation Strategy
Hasnt this been done before?
110
EDI Weak Points Specific to Where XML Strategy
Plays Strong
17. XML Strategy Extend the Past
How does EDI and our XML Implementation
Strategy compare?
111
17. XML Strategy - Adopt Holistic Framework
OMG
Modeling
CALS
IDEF
UMM
UML
Queuing
SGML
EDI
Business Rules
MOM
Mappers
Repositories
Templates
ebXML
UDEF
XML Implementation
BSR
Architecture
XML/edi Framework
Zachman
XML
XSL
DCII
Agents
JTA
SOAP
HTML
Java
UDDI
Web Services
What were the technologies which help our
strategy solidify?
112
Why XML?Contextual Context Defined Business
Constraints
13. Registry 14. Semantics 15. Context 16.
Templates 17. XML Strategy 18. Architecture
Pathways and components which provide for
business success Services-Oriented Architecture
(SOA)
Does XML bring a revolution or evolutional change
to our architecture?
113
18. Architecture EISL - Enterprise Information
Services Layer
User Interface - Presentation
Apps
Web Browser
Email Client
Telephone
Wireless
Front-End
Common Services Oracle9i WSF Web
Services Framework
Assurance
1
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
HR
Project Mgmt
Procure
What are the Enterprise ISL components, and why?
114
18. Architecture XML Strategy EISL
SHIFT
SHIFT
Hub n Spoke
Information Services Layer
Ad Hoc
Centralized data processing only Virtual
Pt.-to-Pt. Physical Artifacts 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 Logical Physical
Artifacts 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 Low Pt.-to-Pt. Real-time Yes Business
Solution
Distributed data processing Simple
Pt.-to-Pt. Physical Artifacts 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
Leveraging XML in my enterprise, what choices do
I have?
115
18. Architecture Patterns

• Business patterns identify the interaction
  between users, businesses, and data. Business
  patterns are used to create simple, end-to-end
  e-business applications.
• Integration patterns connect other Business
  patterns together to create applications with
  advanced functionality. Integration patterns are
  used to combine Business patterns in advanced
  e-business applications.
• Composite patterns are combinations of Business
  patterns and Integration patterns that have
  themselves become commonly used types of
  e-business applications. Composite patterns are
  advanced e-business applications.
• Custom designs are similar to Composite
  patterns, as they combine Business patterns and
  Integration patterns to form an advanced,
  end-to-end solution. These solutions, however,
  have not been implemented to the extent of
  Composite patterns, but are instead developed to
  solve the e-business problems of one specific
  company, or perhaps several enterprises with
  similar problems.
• Application and Runtime patterns are driven by
  the customer's requirements and describe the
  shape of applications and the supporting runtime
  needed to build the e-business application.
• Product mappings to populate the solution. The
  product mappings are based on proven
  implementations.

With EISL, can common processes derived?
116
Impact on our Organization
How do we best leverage XML?
117
Todays Development Tools
What impact does independence have on my
development tools direction?
118
Transition Shift in Focus of DCII Strategy
Initial DCII Focus
Current DCII Focus

• Most FA 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 FA 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 FA domain!
How is DCII evolving, and what are the drivers?
119
Yesterday
Workflow
Purchase Orders - EDI
Status - Web
Feeds - Flat Files
API
ERP, SCM SAP,etc.
Apps
Catalogs
Invoices - EDI
Settlement - Receipts
How does XML change my model?
120
Today - Trend
Workflow
Purchase Orders - XML/EDI
Status - Web - XML
Feeds - XML
XML
XML
API XML
ERP, SCM PDM,etc.
Apps
Catalogs - XML
Invoices - XML/EDI
Settlement - Receipts - XML
How does XML change my model?
121
MAF Master Appropriations File FACTS II Example
Treasury
DFAS
Customers Services
121130D01 1319C-41,2
1010D34,507,584,4721 121130D01190D145,6 1310D688,5
42,592131 1319C-41,291,4191320
Before
Convert
121130D01 1319C-41,2
121130D01 1319C-41,2
121130D01 1319C-41,2
XML MAF
XML Digested with value-add
XML Digested with value-add
Value-chain
After
How do reduce the number of transformations, at
DFAS and downstream?
122
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
Take Ownership Responsibility for Artifacts
Long-Term Commitment to Strategy Principles
Modify Procedures to Assure Integrity and Outcomes
123
Answer XML Information Services
XML is different, do we handle XML differently
than past technologies?
124
XML is a Collaboration Catalyst
Spreadsheets
SQL
XML
There isnt any other technology that can span
the entire organization and trading partners
Web
Document Content
EDI
Cobol
I get it, my labor pool actual becomes broader,
and talks together, right?
125
FA Modernization Shift Driver
DFAS Response
How will DFAS support FA Modernization?
126
Summary
From what we have learned where to we go?
127
Summary Atomic Features of XML
Technology
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 doesnt 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. 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 necessary to 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.
How does XML play into our Strategy?
128
Summary...

• Evolution XML technology builds on prior
  efforts
• XMLs pervasiveness allows for commonality,
  variety of tools on the market, active standards,
  communities of interest, labor pool and reuse at
  various levels
• Frees implementers from proprietary shackles
• XML technology offers the opportunity for greater
  participation, greater accuracy of information
  and reduction of effort to implement
• Organization to..
• Manage Our Business Information Assets
• Construct an Architecture for Enabling an
  Enterprise Information Services Layer (EISL)
• Implement XML Strategy based on business
  opportunity

From what we have learned where to we go?
129
Summary

• Provide world class collaborative mechanisms for
  true integration and partner exchange to meet
  DFAS mission.
• Higher Quality - accuracy
• Higher Agility quick response
• Higher Value outcome/cost
• Higher Competence workforce
• Higher Availability up time
• Higher Customer Satisfaction

DFAS Productivity
Innovation
Mainframe

• Services

Client - Server
Internet
Centralized
Distributed
What is our ROI on XML?
130
Summary...
Change favors the prepared mind.
Louis Pasteur

• We need to be thinking 1, 3, 5 and 10 years out

Looks like we have a plan, what do I need to do
to be part of it?
131
Questions ?
Thank you
Eric Okin Assistant Deputy Director Policy and
Architecture DFAS - DTB
Mike Lubash 703.607.1166 Mike.Lubash_at_DFAS.mil XML
Team Leader DoD Finance and Accounting Namespace
Manager
?
132
Cost / Savings Ratio
Cost Benefits
?
133
Why we are here? DFAS-DB 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
Agencys 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 FA domain nomenclature within the DoD
DCII COE Data Emporium XML Registry - SHADE
134
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 EA strategy
• Established XML training course

Business Information Objects
Architecture

• 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

135
Proposed Tasks