320 likes | 482 Views
Business-Centric Approach to Enterprise/ Federal Standards, Validation, & Deployment. Exchange Development. Deploy. Requirements. NIEM. Mo del Data. Test. David Webber, NIEM Team, Oracle Public Sector. Build Exchange. Generate Dictionary.
E N D
Business-Centric Approach to Enterprise/ Federal Standards, Validation, & Deployment Exchange Development Deploy Requirements NIEM Model Data Test David Webber, NIEM Team, Oracle Public Sector Build Exchange Generate Dictionary
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. DisclaimerNotice
Agenda S B C D ackground • Extensible Markup Language (XML) • National Information Exchange Model (NIEM) • Content Assembly Mechanism (CAM) Toolkit tandards • SFIS 9.0+ Types library Schema • Managed and scalable data dictionaries for code values (e.g. SFIS Values Library Service) • SLOA Core XML Schema • ‘Complete PDS' - Transaction example that includes SLOA Core onformance • Transaction validation • Using cloud services to scale validation across the Enterprise • Leveraging the approach to simplify system validations eployment • Open-XDX (Open Data Exchange) • Deployment Architecture with CAM
Extensible Markup Language (XML) B Cloud Virtual Choreographies Software as a Service NIEM Industry-based Methodologies eProcessing XML Semantic Search Lightweight Collaboration World Wide Web HTML Portals Social Networking • Adoption; but not Centralized • Speed vs Standardization • Stds: Simple Complex eCommerce Linked Model Hyperlinking SQL Websites ERPs Search Commerce Enterprise Databases EDI Relational Databases Industry Data Standards eMail Hierarchical Data Stores Mainframes • More robust / adaptable than EDI • Speed to define Transactions • Machine and People readability • Rich structure to carry Semantic Information • Wider Labor Pool • Pervasive Software and Device support • Resulting in Widespread Adoption
National Information Exchange Model (NIEM) B Centralize - Joint DOJ / DHS / HHS program 1 • Adoption; but not Centralized • Speed vsStandardization • Stds: Simple Complex Repeatable, Reusable Methodology (Exchange Specification Lifecycle) 2 Toolsfor enabling interoperability 3
National Information Exchange Model (NIEM) B Centralize - Joint DOJ / DHS / HHS program • Created a centralized organization to promote standardization of information exchange for cross jurisdictional information sharing. • 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) 1
National Information Exchange Model (NIEM) B Repeatable, Reusable Methodology (Exchange Specification Lifecycle) 2 • Design • Develop • Deploy • Document • Dictionaries • Discovery • Differentiate • Diagnose IEPD - Information Exchange Package Documentation
National Information Exchange Model (NIEM) B Toolsfor enabling interoperability 3 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. COMPLEXITY multiple disconnected components + closed coded
CAM Toolkit B SIMPLICITY integrated components + visual metaphors + open source Minimal learning curve for practitioners 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 Deliver the NIEM domain and core component sets in format that can be quickly adapted and reused
CAMeditor.ORG Project Statistics B • SNAPSHOT OF PROJECT ACTIVITIES50,000 CAMeditor.org page visits in one year • 140 countries have downloaded tools; • 27% of visitors are from U.S.; • 600+ downloads weekly • 1000+ video training minutes viewed monthly • 6 languages now available ‹#›
S SFIS 9.0+ Types library Schema Managed and scalable data dictionaries for code values SLOA Core XML Schema ‘Complete PDS' - Transaction example that includes SLOA Core Standards
Managed Dictionaries – Authoritative Sources S Centralized SFIS Values Library Service, NIEM, Metadata Registry schema Distributed schema ALLOWED VALUES Publish schema SQL schema Managed Dictionaries
SLOA– Standard Line of Accounting – uses SFIS types S SFIS.SLOA Demo
‘Complete PDS’ – PDS transaction + SLOA S SFIS.SLOA Procurement Data Standard XML Schema <xsd:import … schemaLocation=“SFIS.v9.2012-11-14.xsd/> <LOAtype… <choice BLOB or SLOA/> <element name="LOA" type="sfis:LOAtype" Import SLOA components to PDS Align PDS schema with SFIS.SLOA business requirements Source: http://www.acq.osd.mil/dpap/pdi/eb/docs
C Transaction validation Using cloud services to scale validation across the Enterprise Leveraging the approach to simplify system validations Conformance
CAM Runtime Validation Framework C - Data Exchanges ‘Complete PDS’ Demo
CAM Runtime Validation Framework C - Data Exchanges Deployed as a service System Requesting
CAM Runtime Validation Framework C - System Validation System Under Evaluation Conformance Test Suites
D Open-XDX (Open Data Exchange) Deployment Architecture with CAM Deployment
CAM Open-XDX Deployment D - Data Exchanges SQL Mapping System Demo http://www.youtube.com/watch?v=oVXtJIZVvRA
Integration Deployment ViewOpen XDX / CAMV architecture Design Test Deploy Data Delivery D SQL CAM Editor DB XML Open XDX Open XDX FMW SQL XML CAMV CAMV • Device • Browser • Server Web • Generate Data • Validate Data • Send Data • Visual Editor • SQL Browser • Dictionaries • Drag and Drop • Open XDX • Web Services • FMW / BPM
Exchange Delivery Lifecycle D Dictionaries Discovery Requirements Updates Design Drag and Drop Visual Designer Diagnose Develop XML Samples Exchange Templates Differentiate 1 Production Results XSD Schema Deploy Document 2 NIEM IEPD Reports 3 Validated Templates / Schema XMI / UML Models 4 Required IEPD artifacts Documentation 5
Summary Applying CAM/NIEM tools to PDS • NIEM provides technical guidelines for developers of information exchanges with XML • Technical Solution Demonstrated • Building SLOA components • Ingesting existing PDS schema • Extending PDS schema • Providing Deployment Components and Delivery • Future NIEM Alignment • How does PDS schema compare to NIEM? • How can the IEPD approach be applied to PDS schema? • Short term low impact gains from NIEM analysis / fixes • Extracting semantic value from existing PDS / SLOA • Using NIEM tools to accelerate PDS / SLOA delivery
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
Formal NIEM IEPD Packaging Details Generated using CAM Never Used Word Document Manual Entry
Information Sharing Components Stack Privacy and Policy Automation Privacy and Policy Automation Rules Identity and Access Management Business Process, Enrichment, Routing Routing / Process Flow Standardized Metadata Identity, Access Control, Classifications Common Vocabulary Information Exchange Alignment
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
IEPD Delivery Tasks / Tools Matrix • In order to be NIEM-conformant, the IEPD must adhere to: • NIEM Conformance Document • NIEM Naming and Design Rules (NDR) v1.3 • NIEM Model Package Description (MPD) Specification v1.0