130 likes | 257 Views
External. Business & Technical. May 2008. eGovernment Interoperability. E-Government and the ebXML Registry A Framework Overview Metadata Forum Sydney, May 2008. INTRODUCTION.
E N D
External Business & Technical May 2008 eGovernment Interoperability E-Government and the ebXML RegistryA Framework OverviewMetadata ForumSydney, May 2008
INTRODUCTION • Intent: To provide a business and technical overview of a registry-centric e-Government interoperability framework. • Agenda • Scope of the business problem – 5 min • The communication challenge – 5 min • Developing the community language – 5 min • Building the integrated community – 5 min • Role of ebXML – 5 min • Example – 5 min • Questions – 10 min
TYPICAL SCENARIO : STARTING A BUSINESS Introducing Dave… • Wants to open a specialist manufacturing business in the Sydney suburb of Brookvale. • Is obliged to understand and navigate local, state, and federal regulations and complete dozens of registration, licensing, and permit processes. • Plans to hire about a dozen staff and service customers across Australia • ABN Registration • ACN Registration • Name Registration x 8 • Trademark registration • Development approval • A dozen State licenses • Workplace safety certificates • Import/ Export licenses • Grants & concessions • Etc, etc • I want: • Government to tell me what registrations, permits, licenses and certification I need • Government to tell me what grants & concessions are available • To give government my information once, not repeated across 50 forms. Australian government projects like “Business Names” (ABN-BN) and “Standard Business Reporting” (SBR) aim to give Dave what he wants. Many other governments around the world have similar initiatives to deliver “outcomes based e-government services”.
SOME CURRENT AUSTRALIAN e-GOVERNMENT PROJECTS And this is just a small sample – a few that I have had some participation
WORKING ACROSS THE SILOSOF GOVERNMENT • Integrated service delivery requires: • Integration across the silos of government. • Consistency in many-to-many scenarios. • Co-operation, collaboration & standards. • This is hard because they are used to working independently and must legally maintain independence (FMAA).
INTRODUCING THE“ALIGNMENT DOMAIN” For agencies (G2G), businesses (B2B) or both (B2G) to integrate processes they must align at several levels. Standards apply at every level. They must talk the same language. But, at the process and information level, that language is community specific. Many-to-many scenarios require a standards based “outside-in” approach.
DEVELOPING THECOMMUNITY LANGUAGE The “Government Information Exchange Methodology” (GIEM) provides the tools and methods to define the community standard. GIEM draws on best practices from UN/CEFACT, ISO-20022, 11179, HL7, RosettaNet and OMG A Metadata repository is a central component.
USING THE REPOSITORY The project team member re-uses a subset of repository meta data, adds local extensions, and then delivers technology specific product to the user community.
BUILDING THEINTEGRATED COMMUNITY The community standard schema (XSD, WSDL, etc) are published to the Services Registry. A test service is configured in the test harness. Agencies & businesses test their implementations, register their services, bindings & policies. Partners discover, bind & transact.
GOVERNANCE IS KEY • Without some governance, this all turns to chaos. • Development of standards: • Ownership of data domains (tax, Finance, Health, etc) • Development process, version control • Extensions & contributions • Deploying standards based services • Testing service interfaces • Interface policy & security • Change control
WHERE IS ebXML IN THIS? • The development method (GIEM) borrows from the CEFACT Core Component Technical Specification (CCTS) – one of the original ebXML specifications. • The meta-data repository is based on the ebXML Registry Model. • The services registry is built on the ebXML Registry Model. • Key Technical Issues: • Mapping between meta-models - ebRIM3.0, XSD, WSDL, CCTS, 11179, UML2.0 • Interchange standards – between modelling tools and repository. • Key Business Issues: • Marketing & Communication • Governance
EXAMPLE & QUESTIONS • AS4590 EXAMPLE • As a paper document • As a UML model • As an XML Schema • As Repository Meta-data • QUESTIONS ?