ManTech Enterprise Integration Center - PowerPoint PPT Presentation

Loading...

PPT – ManTech Enterprise Integration Center PowerPoint presentation | free to view - id: c7e1b-ZDc1Z



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

ManTech Enterprise Integration Center

Description:

XML lends itself to Internet/Web-centric. E-Business applications ... AIAG (auto) Aviation Industry. OTA (travel) Government. Food. Finance. Banking. etc. 8/7/2000 ... – PowerPoint PPT presentation

Number of Views:120
Avg rating:3.0/5.0
Slides: 115
Provided by: mike260
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: ManTech Enterprise Integration Center


1
ManTech Enterprise Integration Center
www.mantech-wva.com
www.dcnicn.com
  • DoD Logistics XML/EDI Support Task Robert S.
    Kidwell, V.P. Sr. Tech Director
  • by Michael Evanoff (evanoffm_at_mantech-wva.com),
    Task Lead,
  • and
  • Debora Parker, EB/EC Analyst
  • Presentation for Scottie Knott, Director JECPO
  • August 7th, 2000

2
2000
1994
Information Technologist(s)
Our Principal Mission is to Provide the U.S.
Department of Defense (DoD) with a Range of
Advanced Information Technology Strategies
Coupled with Business Case Modeling Techniques,
Functional Application Design and
Development, and the use of Information Exchange
Standards that Contribute to the Concept of a
Shared Integrated Environment (Data/Information/Kn
owledge) Between the DoD and their Industrial
Partners
www.dcnicn.com
www.mantech-wva.com
Concept Formulation Requirements Definition
Business Process/Models Pilot Demonstrations
3
Work Products Completed (1/2)
  • XML INDUSTRY PROFILE AND RECOMMENDATIONS
  • EDI (X12 TO UN/EDIFACT) MAPPING CONCEPT PAPER
  • UN/EDIFACT U.S. INDUSTRY ANALYSIS
  • APPLICABILITY OF USING XML FOR EDI VIA THE
    INTERNET -- A WHITE PAPER
  • INTRODUCTION TO MERCATOR

4
Work Products Completed (2/2)
  • INTRODUCTION TO EDI (ANSI X12 AND UN/EDIFACT)
  • INTRODUCTION TO MERCATOR FOR EDI
  • XML/EDI PURCHASE ORDER DEMO SYSTEM PRESENTATION
  • UN/EDIFACT ORDERS MESSAGE TASK DELIVERABLES

5
Outline for Today
  • What is XML?
  • Task / SOW Overview
  • DoD Logistics EDI Support Task
  • Subtask 1 Overview
  • XML/EDI Standardization An Industry Profile
  • Subtask 2 Status Overview
  • XML DOD Concept of Operations Framework /Roadmap
  • Closing Remarks

6
What is XML?
  • The Extensible Markup Language (XML) is a subset
    or restricted form of SGML, the Standard
    Generalized Markup Language (ISO 8879), that has
    been optimized for use of the Internet and World
    Wide Web
  • XML eliminates several syntactic and lexical
    quirks in SGML that complicate processing
  • XML lends itself to Internet/Web-centric
    E-Business applications
  • Portable, human and/or machine consumable,
    extensible, and multi-language capable

7
XML in a Nutshell
Presentation
CSS, XSL
Apps
XML Content
Databases
Servers
8
XML Schemas
  • XML Schemas a critical success factor
  • A better way for developing DTDs
  • Expresses shared vocabularies and allows machines
    to carry out rules made by people
  • Provides a standard means for defining the
    structure, content and semantics of XML documents
  • XML Schemas is a work in progress
  • Currently 222 outstanding issues with XML Schemas
    at W3C
  • The core of XML Schemas is already defined

9
Task Overview
  • ManTech is assisting DOD (in particular the
    Defense Logistics Management Standards Office -
    DLMSO) in evaluating the applicability of
    existing and future XML-based standards for use
    within the DOD logistics systems
  • Defense Logistics Management System
  • See DOD Manual 4000.25-M (a.k.a. DLMS Manual)
  • Note DLMS is replacing DLSS (Defense Logistics
    Standard Systems)
  • DLMS comprises about 25 unique ANSI X12
    Transaction Sets
  • DLSS is based on 80-column card 1960s proprietary
    technology
  • High Volume of Transactions 2.5 - 3 Billion
    Transactions per year

10
Tasking Defined
  • 1. XML/EDI Industry Standardization Profile
  • 2. XML DOD Concept of Operations Framework
    /Roadmap
  • 3. Support DAASC AIS Migration efforts
  • 4. Develop XML/EDI Prototype Demonstration
    System
  • 5. Perform independent assessment of key product
    data exchange tools and / or technologies
  • denotes subtasks that are designated as
    Optional

11
DOD ManTech Collaboration
  • Meeting 1 - Spring 1999 at Ft. Belvoir
  • Initial DRID 48 IPT assistance with XML EDI
  • Meeting 2 - February 11th, 2000 at Ft. Belvoir
  • Set the stage for the XML/EDI Industry Profile
  • Meeting 3 - May 25th, 2000 in West Virginia
  • IPR for Subtask 1, Review of SOW, Discussed
    future direction of this task
  • Meeting 4 - August 7th, 2000 at Ft. Belvoir
  • Todays brief on completed and planned work items
    for this task

12
XML/EDI StandardizationAn Industry Profile
Subtask
  • Purpose
  • Identify and evaluate the current myriad of
    bodies and / or business standardization
    initiatives potentially applicable to DODs (in
    particular DLMSOs) emerging XML / EDI planning
    efforts
  • Status
  • This deliverable has been completed and will soon
    be posted on the DCNICN.Com site at
  • http//www.dcnicn.com/xmledicentral/

13
Enter XML / EC Frameworks and Repositories
  • ebXML, BizTalk, RosettaNet, OASIS, eCo
    Framework, xCBL, etc.

14
DOD XML Related Efforts
  • Federal CIO XML Working Group
  • GSA - Mary Mitchell / Marion Royal
  • DOD/DISA COE XML Registry Project
  • Dr. Glenda Hayes (MITRE)
  • DOD/DISA Center for IT Standards (Jerry Smith)
  • DOD XML Guidelines (Jerry Smith)
  • DOD Fed EDI Standards Management Committee (?)
  • NIST / OASIS Conformance Testing
  • GCCS XML Text Messaging (USMTF)
  • Mark Heller (MITRE)
  • Air Force XML User's Group
  • Steve Holloway (WPAFB - PDSM PO)

15
DOD COE XML Registry (1/3)
  • The main thrust of the 'XML Registry' work is to
    provide visibility and awareness of XML data
    elements in use within various functional areas
    within DOD (esp. in the GCCS arena).
  • The utility of providing this awareness is to
    ease the job of application integrators in
    developing system interfaces.
  • Defense Information Systems Agency (DISA) and
    U.S. Army Communications Electronics Command
    involvement

16
DOD COE XML Registry (2/3)
  • Current DOD Namespaces include
  • 1. Aerospace Operations,
  • 2. COE Enterprise,
  • 3. Combat Support,
  • 4. General Military Intelligence,
  • 5. Ground Operations,
  • 6. Messages,
  • 7. Meteorological and Oceanographic, and
  • 8. Tracks Reports
  • The latest Namespace to be announced is Finance
    Accounting - (Who will be next?)
  • Managed by Mike Lubash, DFAS

17
DOD COE XML Registry (3/3)
  • Commercial standards and services are evolving in
    this area for e-Business exchanges - why is COE
    Registry creating their own?
  • Industry Registries and Repositories will rely on
    XML Schemas - implementing this type of registry
    this early in the game may be premature.
  • XML is a syntax that can be applied to widely
    varying data in widely varying situations -
    having a single DOD registry for all types of XML
    data is not scalable and doesnt follow the
    distributed Web model.

18
XML/EDI Standardization An Industry Profile
Report
  • Report Outline
  • Traditional EDI Standards Bodies
  • DISA / ANSI X12, UN/CEFACT
  • XML and the Internet Standards Bodies
  • W3C, IETF
  • Emerging Industry Frameworks / Repositories
  • ebXML, RosettaNet, BizTalk, etc.
  • DoD Related XML/EDI Standardization Efforts
  • COE XML Registry, Federal CIO XML Working Group
  • Closing Observations Recommendations

19
XML/EDI Standardization Areas
Registries
Security
Repositories
Transport Routing
Services
Content Definition
Integration
XML/EDI Standardization Activities
20
Traditional EDI vs. XML EC/EDI Comparison
Intelligent Business Information
Syntax
Semantics
Integration



TraditionalEDI
  • ICs
  • DEDs
  • ISO 9735
  • X12.6,x
  • Mapper / Translator
  • XML
  • Schemas
  • RDF
  • Repository
  • Namespace
  • Addressing
  • XSLT, DOM, Links,JDBC, Agents, middleware, etc.

Web EC
XML RPC SOAP XMI CWMI WIDL APIs
21
A Definitive Need for Standardization
Hello?
Bonjour?
XML
  • Common Global Standards will enable
  • Minimized the need for training personnel in use
    and maintenance of EDI standards
  • Eliminating the costs associated with
    duplication of functionality
  • Minimizing the need for multiple translation
    softwares, and
  • A harmonization of semantic, which in turn will
    smooth the flow of data among different but
    interconnected applications

22
ebXML Introductionhttp//www.ebxml.org
  • What is ebXML?
  • tech spec / develop as they go
  • Why did ebXML form?
  • natural way to bring next generation EDI to the
    Web
  • When did it get started / when will it finish?
  • 8 months into 18 month project
  • How is it being developed?
  • 3 step process, requiring two-thirds approval
  • via open meetings proof-of-concept systems

23
ebXML Industry Support
  • Industry Associations represented
  • AIAG (auto)
  • Aviation Industry
  • OTA (travel)
  • Government
  • Food
  • Finance
  • Banking
  • etc.

24
ebXML Government Participation
  • U.S. Government
  • JECPO
  • NIST
  • MTMC
  • DOD Contractor Support
  • ManTech
  • LMI
  • MITRE

25
ebXML Stds Bodies Represented
  • ISO
  • International Organization for Standardization
  • http//www.iso.ch/
  • CEN ISSS
  • The European Committee for Standardization
    Information Society Standardization System
  • http//www.cenorm.be/
  • ANSI X12 / DISA
  • Accredited Standards Committee (ASC) X12
  • http//www.disa.org/

26
ebXML Stds Bodies Represented
  • UN/CEFACT
  • UN Centre for Trade Facilitation and E-Business
  • http//www.unece.org/cefact/
  • W3C and IETF (non-accredited)
  • See XML/EDI Standardization An Industry Profile
    Report
  • http//www.w3.org
  • http//www.ietf.org
  • OMG
  • Object Management Group
  • http//www.omg.org/

27
ebXML Organization
  • ebXML Requirements, Mike Rawlins
  • Business Process Methodology, Paul Levine
  • Technical Architecture, D. Nickull/A.
    Grangard
  • Core Components, Lisa M. Shreve
  • Transport/Routing and Packaging, Rik Drummond
  • Registry and Repository, Scott Nieman
  • Technical Co-ordination and Support, Dick Raman
  • Proof-of-Concept Dev. Demo, Sun Microsystems
  • Marketing, Awareness, Education, Ann Bullen

28
ebXML Work Flow
Where all the action is!
29
ebXML Requirements
  • The foundation for which all of the ebXML
    specifications will be built
  • Voted on, and approved the requirements document
  • Requirements doc was treated procedurally as a
    specification document

30
ebXML Business Process Methodology
  • XML-based business process integration.
  • application-to-application, application-to-person
    and person-to-person application environments
  • Focus is on defining current process
    requirements, specifications and issues.
  • UML meta-models for defining syntactically
    neutral, semantically rich business model

31
UML Model to XML Data Concept
32
ebXML Registry and Repository
  • Defining the functional requirements and
    specifications for XML-based interfaces to a
    registry and repository concept that facilitates
  • the software development life cycle,
  • the ebXML standards process, and
  • runtime semantic lookups from within business
    applications
  • Part 1 Final Specification recently released
    (Reg. / Rep. Business Domains)

33
ebXML Registry Repository Concept Example
2
Return list of hits plus all repositories that
were not accessed. From there the user could link
to the document of choice.
Search App
OASIS or other official site
Registry of Registries
A global search may go through potentially
thousands of registries each of which may in turn
have thousands of repositories.
3
Registry
Repository
1
Registry

Registry

Repository
Repository
Repository

Repository
Repository
Repository
Original document in intended format including
multimedia attachments
Drawing by John Petit, KPMG
34
ebXML Transport/Routing and Packaging
  • Business Quality Messaging
  • Reliability, Security, Audit-ability
  • Transport Agnostic
  • Choose your own transport HTTP, SMTP, etc.
  • Currently developing specifications for six
    distinct areas

35
ebXML Core Components
  • Library of Smart Core Components
  • Modeling syntax-neutral data structures at all
    levels of the message hierarchy
  • Classification of Content
  • Describe conditions of reuse
  • Defining what is Context
  • Extension Methodology
  • Develop ways components are reused

36
ebXML Technical Coordination and Support
  • The purpose of this workgroup is support and
    facilitate the cross-coordination across the
    various other workgroups.
  • Boundary Identification between work groups
  • Developing a common glossary of terms

37
ebXML Upcoming Meetings
  • August 7-11, 2000
  • San Francisco Bay Area, CA
  • November 6-10, 2000
  • Tokyo, Japan
  • February, 2001
  • Vancouver

38
ebXML Critical Success Factors
  • Taxonomies for Content and Context
  • Catch-22, need these for advanced info.
    processing like searching and agents, but who
    decides what these should be and how do we cross
    cultures / languages?
  • Will UML provide enough rigor to easily
    generate ebXML compliant business documents?
  • How/who will ensure the fair secure management
    of the registries and repositories?

39
ebXML Summary Remarks
  • Based on good guiding principles
  • Global Reach (developing nations)
    Interoperability
  • Use best of breed foundation technologies
  • Will be turned over to an accredited stds body
  • Good traction with great IT companies
  • IBM, Sun, Commerce One, Vitria, I2, etc.
  • Get involved!
  • Suggest proof of concept ideas in the Registry
    Repository area or Core Components area

40
  • RosettaNet (1/3)http//www.rosettanet.org
  • Founded in June 1998, RosettaNet is an
    independent, self-funded, non-profit consortium
    dedicated to the development and deployment of
    standard electronic commerce interfaces to align
    the processes between IT supply chain partners on
    a global basis.
  • RosettaNets global initiative is to adopt and
    deploy open and common business interfaces,
    enabling small and large buyers and sellers of
    computer technology to do electronic business
    more efficiently.
  • More than 200 companies representing 1 trillion
    in annual information technology and electronic
    components revenues currently participate in
    RosettaNet's standards development, strategy and
    implementation activities.

41
RosettaNet (2/3)
  • RosettaNets mission is to develop a standard set
    of parameters under which e-commerce can be
    conducted in real time over the Web.
  • RosettaNets Development Process includes
    Business Process Modeling and Analysis, PIPs
    (partner interface process), and Data
    Dictionaries all implemented within a set of
    related architectural components termed a
    framework.
  • RosettaNets pilot phase, eConcert, concluded
    its development cycle in February of 2000 and
    focused on the development of RosettaNet
    frameworks for catalog information, and software,
    memory and laptop technical specifications.

42
  • RosettaNet (3/3)
  • European activity will be a goal for
    implementation in the year 2000 for RosettaNet
    along with the development of
  • Catalog Properties v.2 - define the properties
    for price, marketing information, and associative
    properties.
  • Business Properties - normalize or create
    baseline EDI properties from ASC X12, UN/EDIFACT,
    and CompTIA.
  • Implementation Framework - define an exchange
    protocol that will enable IT supply chain members
    to rapidly and efficiently implement RosettaNet
    PIPs.
  • Catalog Update PIP/001 - define the XML
    documents, UML Model and validations tool for
    updating a catalog with a new SKU.
  • Logistical Properties - identify, select and
    define all data elements - data fields to
    represent proper and distinctive logistics
    information to be used during all processes of
    the IT supply chain.
  • EC Technical Dictionary - define the product
    classifications, as well as data properties and
    values.

43
BizTalk (1/3)http//www.biztalk.org
  • BizTalk was announced in March of 1999 and is
    Microsofts attempt to take over the XML and EDI
    business exchange/integration marketplace
  • BizTalk includes
  • BizTalk Framework
  • BizTalk Tools and Server
  • Targeting providing a complete solution for both
    traditional EDI (X12 EDIFACT) and XML business
    integration

44
BizTalk (2/3)http//www.biztalk.org
  • BizTalk Framework is a set of guidelines for how
    to publish schemas in XML and how to use XML
    messages to easily integrate software programs
    together in order to build new solutions. The
    Framework consists of a technical specification
    that defines a way to use XML in a consistent
    way, a code set that defines a small number of
    mandatory and optional XML tags, and the
    www.biztalk.org web portal.
  • This industry initiative was started by Microsoft
    and is supported by technology vendors and users
    like SAP, CommerceOne, Boeing and BP/Amoco and is
    ran by Microsoft appointed boards. BizTalks goal
    is to drive the rapid, consistent adoption of XML
    to enable electronic commerce and application
    integration.

45
BizTalk (3/3)
  • Since its inception, BizTalk has developed the
    following items
  • BizTalk Framework XML Tags Specification -
    defining a common way to use XML to accomplish
    identification and routing.
  • BizTalk Framework Guidelines - defines a set of
    design guidelines for the Microsoft BizTalk
    Framework documents.
  • www.biztalk.org has been created as a place for
    BizTalk users and developers to read information
    on the initiative, discuss development ideas and
    concerns, and download BizTalk related tools.
  • BizTalk Jumpstart kit was release in the last
    quarter of 1999 and a Technical Preview edition
    of Server 2000 was available for download only in
    the first quarter of 2000.
  • Current efforts focused on the development of
    the Microsoft BizTalk Server 2000, currently
    scheduled for release in the fall of 2000.

46
Three Summary Questions
  • Do we, DOD, care about XML governance, or are we
    content to let the standards we work with be
    defined by big corporations?
  • Are we, the DOD, a special case that necessitates
    unique standards and specifications above
    beyond what industry uses?
  • Have we, the DOD, taken stock of our current and
    future system needs and requirements with respect
    to XML and XML/EDI (next generation EDI)?

47
XML/EDIObservations Recommendations
  • Traditional EDI is still alive, however
  • It is the growth of EDI that is slowing down
  • The percentage of EDI traffic carried by VANs
    (vs. the Internet) is also drastically slowing
    down
  • XML is gaining ground
  • SMEs are coming up to speed as fast as the large
    ones
  • XML will be the syntax for EC over the Internet
  • Pandoras Box or Panacea? Get involved!
  • XML/EDI is still immature, but rapidly evolving

48
DODObservations Recommendations
  • DOD is similar in size to other industries
  • Behave as an industry association with respect to
    these IT standardization efforts (auto,
    healthcare, insurance, etc.)
  • Provide an intellectual contribution to these
    standardization efforts
  • Change management
  • Anticipate that there will be people reluctant to
    change in order to protect their turf

49
DODObservations Recommendations
  • Standards management
  • Develop a cross-department team of DOD functional
    and IT reps for both awareness / adoption, and
    embracing / extending both existing and new
    emerging standards
  • Identify Opportunities for Legacy Migration
  • Enhanced DOD system integration
  • Add additional value

50
XML DOD Concept of Operations Framework / Roadmap
- SubTask 2
  • Purpose
  • Assess the impact of next generation EDI to the
    existing DOD processes for governance,
    management, and publication of electronic
    business transactions
  • Provide a high-level roadmap that depicts the
    migration path from traditional EDI, as it is
    used today, to future XML based standards for
    next generation EDI.
  • Status
  • This deliverable is scheduled to be completed by
    December - February timeframe.

51
Schedule for Subtask 2 (1 of 2)
  • Perform baseline characterization of AS-IS
    processes for the management of EDI documents /
    ICs
  • Monitor the ebXML organization and their
    development of an evolving suite of
    standards-based technical specifications
  • Assess various short and medium term industry
    trends and XML framework alternatives that are
    potentially applicable to the DOD's future
    logistics business operations
  • Identify some of the major efforts underway in
    DoD and how can they be leveraged to take
    advantage of XML capabilities

52
Schedule for Subtask 2 (2 of 2)
  • Identify how this framework will give rise to new
    processes for the governance, management, and
    publication of electronic business transactions
  • From previous steps, identify and recommend the
    most suitable XML framework alternative
  • Develop a roadmap (steps DoD should be taking in
    the near and midterm future) for DoD to take in
    light of industry trends
  • Submit Preliminary Draft Deliverable to JECPO /
    DLMSO for comment

53
Governance / Management / Publication Taxonomy
54
Baseline Characterization
  • Baseline the "Existing Architecture" by reviewing
    the current management processes (governance, CM,
    publication) within the Government
  • Who is currently responsible for the EDISMC?
  • What is the status of the Federal EDI Secretariat
    and Federal EDI Standards Management Coordinating
    Committee (FESMCC)? -- (see next slide)

55
Who is minding the shop?at http//www.antd.nist.g
ov/fededi
56
DoD Directive 8190.1 (5May00)
  • Use only FIPS 161-2 EDI stds and
    FESMCC/EDISMC-approved ICs
  • The DLMS is the basis for new, replacement, and
    major modification to logistics business
    processes
  • USD ATL shall provide policy direction through
    DLA Director to DLMSO, who as the Dept.s
    Executive Agent for logistics data interchange,
    shall
  • Serve as logistics configuration manager for
    development of business rules and ICs supporting
    process improvements
  • Develop, publish, document, and maintain
    logistics data interchange business rules and ICs
  • Coordinate representation on all industry
    logistics EDI standards groups with the
    FESMCC/EDISMC for the purpose of ensuring a
    common face to industry

57
DoD Directive 8190.2 (23June00)
  • Establish and use electronic business operations
    that employ EB/EC principles, concepts and
    technologies in the entire range of DoD ops
  • Employ EB/EC concepts and technologies in the
    conduct of all process improvement and
    reengineering efforts
  • Facilitate global data sharing, appropriate
    security measures and integration of
    cross-functional business processes between the
    Department and those with whom it does business
  • Implement flexible, interoperable, open
    solutions that allow the use of new or competing
    technology solutions
  • Use commercial EB/EC standards and COTS
    solutions
  • Utilize end-to-end standards-based solutions for
    EB/EC security that are compatible and
    interoperable with publicly available security
    solutions

58
Generic Methodology for DoD ICs
  • DLMS Processes for ICs
  • DoD Project Proposal Registration
  • DoD IC Development and Submission
  • DoD IC Approval
  • Federal IC Review and Approval
  • ANSI X12 Interaction
  • DoD Implementation

59
Next Steps
  • Assess the applicability of leading Registry and
    Repository specifications and best practices
  • Configuration Management
  • Distribution Publication
  • Trading Partner Awareness
  • Automatic Discovery Process
  • Assess impact to existing DOD processes
  • Develop recommendations and roadmap for DoD

60
XML/EDI Timeline
61
Closing Questions
  • Has DOD taken stock of their current and future
    system needs and requirements with respect to XML
    and XML/EDI?
  • Is there criteria in place for prioritizing the
    preferred order of the DLSS systems to be
    migrated?
  • Has the transition to DLMS reached the point
    where any part(s) of the DLSS have been replaced?
  • Point of view on the DISA COE Registry project?
  • Plans to get more involved with industry
    standardization efforts?
  • FESMCC, EDISMC, et. al.?

62
Thank you!
  • For more information visit
  • http//www.dcnicn.com/xmledicentral/
  • http//www.mantech-wva.com/

63
Supplemental Slides
DoD Logistics EDI Support
64
XML/EDI Demonstration System(Slides 65 - 78)
See Demo at http//ec-testing.mantech-wva.com/tas
k3/md1combo.html
65
XML/EDI Hybridization Demo System Functional
Description
  • Web and Internet enabled EDI Systems
  • Use of COTS Tools and System Integration -
    Mapping Data Any-to-Any and Many-to-Many -
    Routing Documents Any Trading Partner,
    Anywhere
  • XML, UN/EDIFACT, and ANSI X12 compliance
  • Open, Extensible, Standards-based Architecture
  • Streamlined Form Generation via back-end
    Database

66
XML/EDI Hybridization Demo System Functional
Description
  • Compatible with DOD Systems (new and old)
  • Provides both Computer Human consumable
    data - XML / XSL for Human Consumption - X12
    and EDIFACT for Electronic Processing
  • Security and Risk Management - Audit Trails,
    Authentication, Extensible Architecture
  • To learn more visit our EDI Central Website
    at - www.dcnicn.com/edifact_central/

67
Demonstration System Configuration
  • COTS Web System
  • Apache Web Server
  • Perl CGI Programs, XSLT scripts
  • Oracle 8i
  • Internet Enabled - XML, Java, FTP, etc.
  • COTS EDI Tool
  • Mercator Mapping Translation
  • ANSI X12, UN/EDIFACT, and XML Support
  • Trading Partner PC Communication
  • Supports both the Internet and VAN communications

68
Demonstration System Scenario
  • Two DOD and Two Industry Trading Partner
    relationships established
  • DOD POs issued via the Web can be translated to
    any desired data format
  • ANSI X12, UN/EDIFACT, XML, or etc
  • Can be routed to any trading partner anywhere
    via
  • Internet FTP or SMTP
  • Traditional VANs

69
Trading Partner Relationships(Hub Spoke
Architecture)
70
System Functional Diagram
DoDPurchasing
Mapper / Translator
Map
Order Processing (Industry)
issue orders
Industry Trading Partner 1
receive 997s
Browse
Industry Trading Partner 2
Browse
View Purchase Order Functional Ack.
71
Streamlined Order Preparation
Oracle 8i Database Query
72
System Generated Purchase Order
73
Resulting EDIFACT ORDER Computer Consumable
74
Resulting ANSI X12 Purchase Order (a.k.a. 850)
Computer Consumable
75
XML / XSL Human Consumable PO
76
XML Source Document Instance
77
XSL Style Sheet Source
78
Functional Acknowledgement (997) Computer
Consumable
79
XML Database Integration ExampleSlides 80 - 84
80
XML Database Integration Example
  • Querying one or more Database Instances anywhere
    in the world
  • Return results in a single XML file
  • Validate data against DTD
  • Transform the results from XML source to desired
    XML destination form using standard or custom
    XSLT map
  • Consume XML destination file
  • Human Consumption Web Browser
  • Machine Processing UDF, EDI, etc.

81
XML Database Integration Example
  • lt?xml version"1.0"?gt
  • lt?xml-stylesheet type"text/xsl"
    href"xmltest2.xsl"?gt
  • ltxsqlquery xmlnsxsql"urnoracle-xsql"
    connection"demo"gt
  • SELECT initcap(lower(ename)) as "Name",
    initcap(lower(job)) as "Job" from emp
  • lt/xsqlquerygt

82
XSLT Mapping Example
  • ltxslstylesheet
  • xmlnsxsl"http//www.w3.org/1999/XSL/Transform
    version"1.0"gt
  • ltxsltemplate match"ROWSET"gt
  • lthtmlgt lttitlegtCompany Employeeslt/titlegt
  • ltbodygtlth1gtEmployees With Job Descriptionlt/h1gt
  • lttable width"640"gt
  • ltxslapply-templatesgt
  • ltxslsort select"Name" order"ascending"/gt
  • lt/xslapply-templatesgt
  • lt/tablegtlt/bodygtlt/htmlgt
  • lt/xsltemplategt

ltxsltemplate match"ROW"gt lttrgtlttdgtltxslnumber/gt
lt/tdgt ltxslapply-templates/gtlt/trgt lt/xsltemplate
gt ltxsltemplate match"Job"gt ltxslif
test"string(.)'President'"gtlttdgtltbgtPresidentlt/bgt
lt/tdgtlt/xslifgt ltxslif test"not(string(.)'Presi
dent')"gt lttdgtltxslvalue-of select"."/gt
lt/tdgtlt/xslifgt lt/xsltemplategt ltxsltemplate
match"Name"gt lttdgtltigtltxslvalue-of
select"."/gtlt/igtlt/tdgt lt/xsltemplategt lt/xslstyles
heetgt
83
XML Example Final Output
84
XML Example Functional Flow
HTTP Request (URI)
Validate XML Data (DTD)
Run Java Servlet
Transform XML Data
Execute SQL Statement
Process XML Data - Human - Machine
Return Query Results
85
Additional ManTech XML/EDI Related Project
Slides 86 - 90
86
U.S. TRANSCOM Customs Technology Support
  • Conducted an analysis of Military Service and
    Defense Agency foreign customs clearance
    processes.
  • Developing a Web-based system for military
    customs information dissemination and
    collaboration.
  • The system will serve as a central information
    repository for U.S. military customs clearance
    information and issues.

87
Improving Foreign Customs Processes
  • Working with USTRANSCOM, mapping and modeling the
    current foreign customs clearance processes for
    military cargo and personal property for
    high-priority countries
  • Applying initial automation (selectively)
  • Standardizing the processes
  • Based on lessons learned from the selective
    automation

88
Selective Automation
  • Initial automation Working initially with
    USEUCOM in developing a Web/XML-based system for
    shipments to Germany and the United Kingdom
  • Automating a decades old U.S. military European
    customs form (AE Form 302)
  • Interfacing with the Global Transportation
    Network (GTN) system for automated extraction of
    data for customs forms

89
XML, UN/EDIFACT, and Signatures
  • XML will be a data exchange option
  • May include transmission of UN/EDIFACT customs
    messages to German and U.K. customs systems
  • Issues include alternatives to hand-written
    signatures and customs stamps

90
Customs Points of Contact (POC) Website
Contains POCs for Bahrain, Belgium, Germany,
Israel, Italy, Hungary/Bosnia, Japan, Okinawa,
Korea, Netherlands, Panama, Spain,
Portugal/Azores, Turkey, U.K., Norway, and the
U.S.
91
Additional Topics Covered in the XML/EDI
Industry Standardization Profile ReportSlides
92 - 108
92
Organization for the Advancement of Structured
Information Standards (1/2)
http//www.oasis-open.org/
  • A nonprofit, international consortium dedicated
    to accelerating the adoption of
    product-independent formats based on public
    standards including SGML, XML, HTML and others.
  • Members of OASIS are providers, users and
    specialists of the technologies that make
    structured information standards work in practice
    and there are more than 100 member organizations
    dedicated in supporting the application of XML
    including
  • Provides an open forum where members discuss
    market needs and directions and recommend
    guidelines for product interoperability. The
    consortium creates, receives, coordinates, and
    disseminates information describing
    methodologies, technologies and standards
    implementations.
  • OASIS complements the work of standards bodies,
    focusing on making them easy to adopt, practical
    to use and seeks to help achieve supportive
    industry consensus.

93
OASIS (2/2)
  • The XML Conformance Subcommittee or Working
    Group - a joint development effort between OASIS
    and NIST (National Institute of Standards
    Technology) where XML vendors, content providers
    and users can discuss issues pertinent to XML
    conformance.
  • OASIS recently advised the North Atlantic Treaty
    Organization (NATO) on the impact of XML on
    information technology development and its
    potential for NATOs information systems.
  • Sponsors the XML Cover Pages - widely regarded as
    the most comprehensive online reference work for
    XML and its parent, SGML.
  • Joined with UN/CEFACT - The United Nations body
    for Trade Facilitation and Electronic Business in
    development of the ebXML, the vendor-neutral
    Electronic Business XML Initiative to establish a
    global technical and semantic framework that will
    enable XML to be used in a consistent manner for
    the exchange of electronic business data.
  • Advisable for anyone with XML prospective goals
    to closely watch, listen and learn from leading
    edge technological organizations such as OASIS
    and its sponsoring members.

94
XML.ORG
http//www.xml.org/
  • XML.ORG is an industry web portal designed to
    provide a credible source of accurate, timely
    information about the application of XML in
    industrial and commercial settings and to serve
    as a reference repository for XML specifications
    such as vocabularies, DTDs, schemas, and
    namespaces.

95
  • eCo Framework (1/2)http//eco.commerce.net
  • eCo Interoperability Framework consists of the
    Architecture and the Semantic Recommendation
    which define 7 layers of information allowing
    prospective trading partners to learn the
    requirements for interoperating by simply
    browsing the structured document on the Trading
    Partners website.
  • The Architecture defines the way businesses
    describe themselves and their commerce services,
    as well as the markets or trading communities to
    which they belong.
  • The Semantic Recommendations describe best
    practices for developing XML based e-commerce
    documents. The recommendations also define a set
    of XML building blocks and document definitions
    that will let future XML specifications to
    interoperate easily with existing ones.
  • Through this information, Trading Partners can
    locate the system, understand what it is for,
    recognize what markets it participates in,
    identify protocols the system uses to
    communicate, discover what documents the system
    uses to conduct business, and learn how to
    interoperate with the system.

96
  • eCo Framework (2/2)
  • An initiative of CommerceNet, an industry
    consortium with over 500 members, with Commerce
    One as the primary corporate sponsor. It does
    not require implementing new standards for a
    company's e-commerce systems, nor does it compete
    with transaction protocols or business semantic
    languages.
  • Participation by CommerceNet and Commerce One is
    partly funded by a grant from U.S. Department of
    Commerce (NIST) Advanced Technology Program
    Advanced Technology Program.
  • The eCo Specification was designed by industry
    for industry
  • Public release of eCo Interoperability
    Specification working draft was made May 1999
    with Public release of final Specifications in
    August 1999.

97
XML Common Business Library - xCBL (1/3)
http//www.xcbl.org
xCBL 2.0 is the first open XML specification for
the cross-industry exchange of business documents
such as product descriptions, purchase orders,
invoices, and shipping schedules. xCBL version
2.0 is a set of XML building blocks created to
provide the schema document framework that is
needed for robust, reusable XML document exchange
in e-commerce and quick development of XML
applications. Some of these building blocks come
from well established international standards
such as xCBL 2.0 has a goal to harmonize
these standards as much as possible. Veo Systems,
acquired by Commerce One (1999) was chosen in
September of 1997 by the U.S. Governments
Advanced Technology Program (ATP) of the National
Institute of Standards and Technology (NIST) to
conduct research and development on XML
foundations for e-commerce. Commerce Ones
XML-based Common Business Library is an
innovative framework for enabling
interoperability among online trading
communities. The ATP has been partly funding the
underlying xCBL research since 1997 because we
believed in its potential to have a major impact
on e-commerce and the nations economy. -
Shirley Hurwitz, Program Mgr., ATP
98
xCBL (2/3)
  • xCBL 2.0 relates to other commerce
    specifications
  • It is not a single standard, rather a collection
    of common business elements that underlie all EDI
    and Internet commerce products
  • Developed and modeled after EDI semantics such
    as X12 and UN/EDIFACT in order to preserve and
    extend the EDI investments of trading partners
  • xCBL 2.0 will use the joint IETF/W3C digital
    signature standard to protect and insure the
    integrity of xCBL documents and data
  • Reusable components speed the implementation of
    standards
  • Facilitates standards interoperability by
    providing a common semantic framework
  • xCBL 2.0, not a proprietary effort, provides a
    transition path for companies wanting to move
    from EDI systems to open Internet-based commerce
    systems.
  • It is noteworthy that Commerce Ones purpose in
    developing xCBL is to accelerate the adoption of
    XML based e-commerce. xCBL 2.0 is available free
    of charge through the registries and repositories
    operated by XML.ORG, BizTalk.Org and others, as
    well as from Commerce One.

99
xCBL (3/3)
  • As a demonstration of its commitment to
    interoperability, xCBL 2.0 is available in XML
    DTD form and in two different schema languages
  • Microsofts XML Data Reduced Schema (XDR)
  • Commerce Ones Schema for Object-Oriented XML
    (SOX)
  • xCBL 2.0 was designed to model the information
    requirements of B2B e-commerce. A first step in
    this direction was the identification of a small
    set of core documents that could be used to
    conduct the majority of business transactions.
    xCBL 2.0 provides schemas to represent the
    following business documents

100
Commerce XML (cXML)http//www.cxml.org/home/
  • Supports supplier content and catalog models
  • including buyer-managed, supplier-managed and
    Internet marketplaces.
  • Mainly backed by Ariba Microsoft

101
OAG - Open Applications Group (1/4) http//www.
openapplications.org
The OAG is a non-profit consortium of leading
enterprise application software developers
focusing on best practices and process based XML
content for e-business and application
integration. As the largest publisher of XML
based content for business software
interoperability in the world, the OAG also
builds and publishes the detail specifications
necessary to use the XML content as well as
publishing a common middleware API
specification. The OAG was formed in 1995 by the
leading worldwide enterprise software vendors. To
date nearly 50 members comprise the OAG
including
102
OAG - Open Applications Group (2/4)

The vision of the membership of the OAG is to
make plug and play business software a reality
and may best be described by visualizing the way
a laptop computer will accept a new PC Card with
comparatively little effort. Imagine if you could
buy two software applications, plug in a driver,
and then do the final configuration for your
unique requirements!
The OAG believes that with all of the
stakeholders in the IT community working together
in adopting a common, best practices based model
for interoperability, this kind of solution is
possible.
103
OAG - Open Applications Group (3/4)
  • The focus of the OAG is primarily associated with
    their two specifications
  • OAGIS - Open Applications Group Integration
    Specification and the
  • OAMAS - Open Applications Group Common
    Middleware API Specification

The OAGIS contains the largest and richest set of
XML DTD files and schemas in the world which
defines a set of components, processes and
interfaces for use in e-Business, Supply
Chain, Manufacturing, Financials, and Human
Resources applications. Since XML is database
neutral, operating system neutral, language
neutral, and device neutral, it is an effective
tool for defining interoperability among
disparate systems. XML is also in complete
alignment with the OAGs stated technology
strategy, which is to be technology aware, but
not technology specific. The OAGIS defines the
common business interoperability content model
and the OAMAS defines the tie from that common
business content model to a common technical
interoperability mechanism.
104
OAG - Open Applications Group (4/4)
OAMAS - Open Application Middleware API
Specification The OAG and the constituency it
represents, require a common single middleware
API to connect Enterprise Business Application
software components and are interested in working
with organizations that are attempting to address
this need. The OAG recognizes that technology,
and particularly the middleware segment is a key
piece to achieve the overall goals of the
interoperability effort and are relying on
middleware transport mechanisms to provide
necessary infrastructure to enable the goal of
heterogeneous business application
interoperability. The OAG has set out to go the
farthest towards defining the digital dial tone
organizations require to do business in the
emerging e-commerce world.
105
Enter XML and Emerging Technology
XML enables the requirements for real-time,
multilingual, IP-centric solutions, as it
provides businesses an environment that is
affordable, flexible, extensible and dynamic in
achieving an integrated, interoperable exchange
of data.
106
XML Digital Signatures http//www.w3.org/Signature
The XML Signature Working Group is tasked with
developing an XML compliant syntax used for
representing the signature of Web resources and
portions of protocol messages and procedures for
computing and verifying such signatures. The
specification dictates an XML tagset structure
that defines the components of the signature and
their occurrences. The structure has been defined
by the working group by both DTDs and
XML-Schema.
107
  • XML Digital Signatures
  • This is a joint effort between the IETF and the
    W3C.
  • Draft specifications are currently available for
  • The XML Signature Syntax and Processing Document,
    dated 5/10/2000 - specifies the syntax and
    processing rules for the encoding of digital
    signatures using XML. Will be submitted in July
    2000 for W3C Recommendation.
  • The Requirements Document, dated 10/14/1999 -
    lists the design principles, scope, and
    requirements for the XML Digital Signature
    specification.

108
Web Internet Standards Bodies
  • The Extensible Markup Language (XML)
  • The Document Object Model (DOM),
  • XSL Transformations (XSLT)
  • The XML Path Language (XPath)
  • Namespaces in XML
  • XML HyperText Markup Language (XHTML)
  • EDIINT, SMTP, FTP, etc.

109
Additional Topics to be Covered in the XML DOD
Concept of Operations Framework / Roadmap
Slides 110 - 114
110
DoD IC Process (1 of 3)
  • Project Proposal Registration Phase
  • EDISMC assigns a Primary Functional Working
    Group (FWG)
  • Development and Submission Phase
  • FWG ensures proposal fulfills a valid business
    need and that no other IC meets the requirement
  • FWG Chair submits Draft DoD IC to EDISMC
    Secretariat for technical analysis
  • Draft Review Phase (EDISMC)
  • Draft IC distributed electronically to EDISMC
    membership for review and comment
  • Comment(s) addressed by Primary FWG and comment
    submitter with changes documented in the IC
    Record of Changes (ROC)
  • Draft IC with ROC (if applicable) upgraded to
    DoD Proposed IC

111
DoD IC Process, (2 of 3)
  • DoD Approval Phase
  • EDISMC Secretariat distributes DoD Proposed IC
    to EDISMC voting members to approve or disapprove
    the IC
  • EDISMC tallies vote, announces result (75
    consensus voting members)
  • Approved IC becomes DoD Approved IC and is
    forwarded to FESMCC for Federal review
  • Disapproved IC forwarded to FWG for disagreement
    resolution, revote
  • Federal Review and Approval Phase
  • DoD Approved IC becomes Proposed Federal IC and
    assigned to FFWG
  • After FFWG review, Proposed Federal IC made
    available for public review and comment in
    Commerce Business Daily (CBD)
  • Public Review comments addressed
  • FESMCC Chair prepares voting package for formal
    vote on IC

112
DoD IC Process, (3 of 3)
  • Federal Review and Approval Phase (continued)
  • EDISMC Secretariat circulates the Federal Voting
    Package among EDISMC members to establish DoD
    voting position.
  • DoD representative to the FESMCC votes position
    of the EDISMC members in the Federal process
  • FESMCC tallies vote of FESMCC voting members
  • Approved vote establishes the proposed IC as an
    Approved Federal IC
  • Disapproved vote with comments returned to FFWG
    for comment resolution and official approval of
    FESMCC Chair
  • Approved Federal IC proceeds into the DoD
    Implementation Phase
  • DoD Implementation Phase
  • Federally Approved IC becomes production
    version, records updated
  • IC posted in Federal IC Registry and prepared
    for testing by the Compliance Certification
    Facility with VANs, trading partners, and
    Government sites

113
Generic Federal IC Process
  • New IC Presented at FESMCC
  • FESMCC assigns to FWG
  • Draft for Interagency Review
  • Working Group resolves comments/issues
  • FESMCC Secretariat issues to Commerce Business
    Daily for comments
  • Working Group resolves public comments/issues
  • FESMCC approval - issued and posted as approved
    Federal IC

114
Federal IC Registry Structure
XML/EDI ?
About PowerShow.com