David Webber, NIEM Team, Oracle Public Sector NIEM Test Model Data Deploy Requirements Build Exchange Generate Dictionary Exchange Development Taking a

<Insert Picture Here>

David Webber, NIEM Team, Oracle Public Sector

NIEMTest Model Data

Deploy Requirements

Build Exchange

GenerateDictionary

Exchange Development

Taking a Business-centric Approach to Enterprise / Federal Standards, Validation, & Deployment

Copyright ©2011, Oracle. All rights reserved. Oracle Draft Materials – Limited Circulation

The following is not intended to outline Oracle general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.

The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Disclaimer Notice

Slide 2


Agenda

tandards• SFIS 9.0 Types library Schema• How CAM can work using managed data dictionary for value sets (ala SFIS Values library

service)• SLOA XML Core Schema (SLOA is a subset of SFIS types)• ‘Complete PDS' showing how a transaction schema (PDS) can link in SLOA (currently PDS has

a blob space, so users can use one or the other)

onformance• CAM report on ‘Complete PDS’ • Transactions (instance of the ‘Complete PDS') can be validated by a CAMV webservice

(testing and collecting metrics)• Evaluate how a system (ERP, etc) conforms (how well it maps) to the ‘Complete PDS' instance

(SQL drag and drop mapping)

eployment and NIEM• Open-XDX (Open Data Exchange) - http://www.youtube.com/watch?v=oVXtJIZVvRA• Deployment Architecture with CAM• NIEM Considerations

Slide 3

S

C

D

NIEM / CAM (Content Assembly Mechanism)

http://www.youtube.com/watch?v=oVXtJIZVvRA



NIEM (National Information Exchange Model)

• NIEM provides technical guidelines for

developers of information exchanges with XML

• How does PDS schema compare to NIEM?

• What does a NIEM IEPD (Information Exchange

Package Documentation) consist of?

• How can the IEPD approach be applied to PDS

schema?

• What are other considerations when using

NIEM?

Slide 4


Applying NIEM/CAM tools to PDS

• Building SLOA components• Ingesting existing PDS schema• Extending PDS schema• Providing deployment components• Aligning with NIEM

Slide 5


CAM toolkit for NIEM• Minimal learning curve for practitioners• Deliver the NIEM domain and core component sets in

format that can be quickly adapted and reused• Provide technology neutral methods, tools and techniques• Leverage visual metaphors – WYSIWYG• Business Rule Validation• Conformance Test Suites• SQL data mapping / XML generation (code-free methods)• Creates technical artifacts needed for a NIEM IEPD

Slide 6


CAMeditor.ORG Project Statistics

‹#›

SNAPSHOT OF PROJECT

ACTIVITIES

50,000 CAMeditor.org page

visits in one year

140 countries have downloaded tools; 25% of visitors are

from U.S.;600+ downloads

weekly

1000+ video training minutes viewed

monthly

6 languages now available


SFIS XML Schema Types Library – Version 9.0

Slide 8

S

Demo


Managed Dictionaries – Authoritative Sources

Slide 9

SCentralized

Distributedschema

schema

schema

SQL

SFIS Values Library Service, NIEM, Metadata Registry

AL

LO

WE

D V

AL

UE

Sschema

Managed Dictionaries

Publish


SLOA – Standard Line of Accounting – uses SFIS types

Slide 10

S

SFIS.SLOA

Demo


Slide 11

S

<choice BLOB or LOA or SLOA/>

‘Complete PDS’ – PDS transaction + SLOA

Source: http://www.acq.osd.mil/dpap/pdi/eb/docs

Procurement Data Standard XML SchemaSFIS.SLOA

<xs:import … schemaLocation=“SFIS.v9.2012-11-14.xsd/>


CONFORMANCE

• CAM report on ‘Complete PDS’ • Transactions (instance of the ‘Complete PDS') can be validated by a CAMV webservice (testing and collecting metrics)• Evaluate how a system (ERP, etc) conforms (how well it maps) to the ‘Complete PDS' instance (SQL drag and drop mapping)


CAM Runtime Validation Framework

CAMVXML instance

Template (compiled)

Database Lookup

(optional)

Results XML

Java Handler Errors and Warnings

Structure

Rules

Code Lists

SQL Query

C- Data Exchanges

Demo

‘Complete PDS’



CAMVXML instance

Template (compiled)

Database Lookup

(optional)

Results XML


Structure

Rules

Code Lists

SQL Query

C

Deployed as a service

System Requesting

- Data Exchanges



CAMVXML instance

Template (compiled)

Database Lookup

(optional)

Results XML


Structure

Rules

Code Lists

SQL Query

C

System Under

Evaluation

- System Validation

Conformance Test Suites


DEPLOYMENT AND NIEM

• Open-XDX (Open Data Exchange)• Deployment Architecture with CAM• NIEM Considerations

D


CAM Open-XDX Deployment

Open-XDXSQL

Template (compiled)

Database Lookup

Diagnostics and Metrics

XML Instance

Structure

Rules

Code Lists

SQL Query

D

SQL Mapping

System

- Data Exchanges

Demo




Integration Conceptual ViewOpen XDX / CAMV deployment

• Visual Editor

• SQL Browser

• Dictionaries

• Drag and Drop

• Generate Data

• Validate Data

• Send Data

• Open XDX

• Web Services

• FMW / BPM

Design Test Deploy

DB

Web

Open XDX

CAMV

CAM Editor

Open XDX

• Device

• Browser

• Server

Data Delivery

SQL

XML

XML

SQL

FMW

D

CAMV


Officially - What is NIEM?

Components of NIEM

• Joint DOJ / DHS / HHS program created to promote standardization of information exchange for cross jurisdictional information sharing.

• Provides the tools for enabling interoperability at the data layer within and across systems supporting information sharing, while preserving investments in current technology and optimizing new technology development.

• Going International – Canada, Mexico, EU

Common Language(Data Model Lifecycle)

Built and governed by the business users at Federal, State, Local, Tribal and Private Sectors

Repeatable, Reusable Process(Exchange Specification Lifecycle)

D


NIEM Governing Structure

NIEM’s governing structure is comprised of Federal, State, Local, Tribal and private organizations

NIEM is managed at an executive level by the Department of Homeland Security (DHS), Department of Justice (DOJ), and Department of Health and Human Services (HHS)

Executive Steering Council

ESC

Executive Director

Deputy Director

NIEM PMO

NIEM Technical Architecture Committee

NTAC

NIEM Business Architecture Committee

NBAC

NIEM Communications & Outreach Committee

NC&OC

D


Information Sharing Components Stack

Privacy and Policy Automation

Identity and Access

Management

Routing / Process Flow

Standardized Metadata

Common Vocabulary

Information Exchange Alignment

Business Process,

Enrichment, Routing

Identity, Access Control,

Classifications

Privacy and Policy

Automation Rules

D


The 8 “D”s and NIEM

• Design• Develop• Deploy• Document• Dictionaries• Discovery• Differentiate• Diagnose

Repeatable, Reusable Process(Exchange Specification Lifecycle)

NIEM IEPD Process

*IEPD - Information Exchange Package Documentation

D


NIEM IEPD Reports

DictionariesDiscovery

Exchange Delivery Lifecycle

Diagnose

Differentiate

Design

Develop

Validated

Templates /

Schema

XSD Schema

XML Samples

XMI / UML Models

Production

Results

Requirements

Updates

Documentation

Drag and Drop Visual

Designer

DocumentDeploy

Exchange

Templates

D

1

2

3

4

5

Required IEPD artifacts


24

IEPD Delivery Tasks / Tools Matrix

CAM CAMVOpen-XDX

(OPX)Exchange Schema Development X

Canonical Model Development / Generation X

Exchange Schema Generation X

NIEM Compliance Checking / Reporting X

WSDL / JAXB Binding Generation X

Operation Message Test Case Generation X

Production Services Message Generation X

SQL Schema Mapping X X

NIEM IEPD Artifact Generation X

- Cross-reference spreadsheet X

- UML model X

- Business Rules Report X

- XSD schema package X

Conformance Test Suite X

Run time XML instance validation X

In order to be NIEM-conformant, the IEPD must adhere to:

1. NIEM Conformance Document

2. NIEM Naming and Design Rules (NDR) v1.3

3. NIEM Model Package Description (MPD) Specification v1.0

D


Formal NIEM IEPD Packaging Details

IEPD Artefact Description

Exchange Files

Subset Schema (SSGT) Subset of the full NIEM schema—a compressed directory of schemas to distinguish from other schema sets.

Wantlist User requirements -distinguishes user-required data components from components they depend on for conformance. Generated by and up-loaded to the Schema Subset Generation Tool (SSGT). This is an open specification and the SSGT is not required to create a wantlist, though it is easier.

Exchange Schema Base document schema that defines the XML root element and is generally named after the IEPD itself. Also known as the document schema, reference schema, or root schema.

Constraint Schema Constraints for separate constraint validation path—a compressed directory of schemas to distinguish from other schema sets.

Extension Schema Specification for extended components—separate local name-spaces of components not contained in NIEM.

Sample XML Instance Example instance(s) – may reference optional stylesheet.

Stylesheet (generic) Example stylesheet for display of instance(s).

Documentation

Master Documentation The Master Document is the main document for which all of the context and details around the exchange are explained. This document includes, the overview, as well as details surrounding the exchange, business drivers and requirements

Exchange model XMI Exchange model in standard open format (xmi, vsd, zargo) and standard open graphic (jpg, pdf, etc.) preferably a Unified Modeling Language (UML) model.

Business Rules Business rules in one of the following formats: (1) plain or structured English, (2) written into master documentation, (3) Schematron or other formal business rule language, or (4) generated by a development tool.

Mapping to NIEM Mapping of domain components, tagged with constraints (i.e., cardinality, etc.) to NIEM components ; preferably the Component Mapping Tool (CMT).

Extended Components Components created because they were not in NIEM—may be part of mapping spreadsheet and include structure and definitions of new components. Prefer CMT.

Change log Record of cumulative changes from previous IEPD versions. The initial IEPD simple records its creation date.

Catalog

Catalog XML file A machine-readable list of artifacts in the IEPD in an open, portable and browser-displayable format (simple manual edit).

Metadata XML file All metadata of owner and domain to be registered with the IEPD (simple manual edit).

Generated using CAM

Never Used

Word Document

Manual Entry

D


CAM / NIEM IEPD functions coveredD


Reality – NIEM is still improving…

• Collections of complex XML Schema• Verbose components• Embedded context in names• Currently facing significant scaling challenges

• Inconsistencies; too much manual management; slow lifecycles

• Dictionary technology incubating• Enhanced code lists mechanism incubating• UML profile is evolving initiative with OMG

• Attempt to marry modelling techniques and XSD Schema syntax

• Policy and Security mechanisms incubating• Need to embrace enabling tools for rapid expansion of

domains and community collaboration

D


Links and References

DOWNLOADS -

http://cameditor.org

NIEM MATERIALS -Oracle NIEM website

http://www.oracle.com/goto/niem Oracle XMLOrb blog site

http://blogs.oracle.com/xmlorb Online NIEM tutorials

http://www.youtube.com/user/TheCAMeditor

Slide 28

D

http://www.oracle.com/goto/niem

http://blogs.oracle.com/xmlorb

http://blogs.oracle.com/xmlorb

http://www.youtube.com/user/TheCAMeditor

Documents

David Webber, NIEM Team, Oracle Public Sector NIEM Test Model Data Deploy Requirements Build Exchange Generate Dictionary Exchange Development Taking a