# Presentation: 157144

## Chris Hassler

**Presented By:**
**Chris Hassler**
**Project Editor – UN/CEFACT TBG6 Team for**** ****Project Cost and Schedule Management**
**Feb 2006**

***UN/CEFACT TBG6 Team for Project Cost and Schedule Management:***
***Project Status Report  & Data Model Review***

**Rev. 1.0**

## Contents

- UN/CEFACT Project
- Background
- Timeline
- Current Status (EVG3)
- DCMA Web Services
- Registry (coming soon)
- Security
- DCMA Web Services Compatibility Profile 1.0
- How to Get Started

## UN/CEFACT

**UN/CEFACT**

**Background**
**Timeline**
**Current Status**

## UN/CEFACT Data Standardization

**Enhancement to DoD Earned Value Standards for EDI**
**XML-based**
**Includes ANSI X12 806 & 839 transaction sets**
**Adds many new fields to support entire lifecycle of Project Cost and Schedule Management data (from Contract Initiation to Closeout)**
**Based on Core Components Technical Specification (CCTS)**
**First Implementation Verification 90% complete**
**Must complete two additional Implementation Verifications by September 06.**
**UN/CEFACT adoption scheduled for September 06**
**Working with Earned Value software vendors**

## UN/CEFACT Timeline

**Sept 05 - Project Proposal Accepted by  UN/CEFACT, DCMA Named Project Editor**
** **

**March 05 - Project Proposed to UN/CEFACT: Project Cost and Schedule Management**

**Jan 06 - UN/CEFACT TBG6 Interim Meeting in Paris**
** **

**Mar 06 - UN/CEFACT Forum in Vancouver; Implementation Verification Begins**

**Sept 06 - UN/CEFACT Forum in New Delhi; Implementation Verification scheduled to be complete; expect UN/CEFACT to approve data standard for international usage.**
** **

**Jun 06 - UN/CEFACT TBG6 Interim meeting**

## UN/CEFACT Implementations

**First Implementation Verification 90% complete**

**Transfer**
**EV**
**Data**

**Convert **
**UN/CEFACT XML**
**to wInsight XML**

**Notify**
**DCMA **
**User**

**EV Data**
**Submission**
**Application**

**Service Consumer **
** ****(Contractor)**

**Service Provider **
**(DCMA)**

**Boeing User Prepares EV Data in Welcom**

**DCMA User Analyzes EV Data in wInsight**

## DCMA 

**DCMA **
**Web Services**
**Registry**
**Security**
**DCMA WSCP 1.0**

## DCMA SOA Next Step: Systinet Registry

**Enablement**

**Register &**
**Discover**

**Coordinate &**
**Compose**

**Apps, App Servers, **
**Legacy, MOM/EAI**

**UDDI,**
**Governance**

**BPM & composite applications**

**Introduce Web Service**
**Technology; enable legacy app integration; provide data access**

**Scale the number of interoperable participants**

**Create, link and adapt business rules and**
**processes in a loosely coupled manner**

**SOA Maturity over Time**

**DCMA is **
**here**

## DCMA Web Services Security: Basic Authentication

***DCMA Web Services Security: Basic Authentication***

**Client Web Application**

**DCMA **
**App Server**
**or SOA**

**Web Service**

**Business Partner**
**App Server**

**User Browser**

**DB**

- Internet

**Service****Consumer**

**Service****Provider**

**User Authentication**
**& Authorization**

**Notes:**
Even internal DCMA clients look like this--just move the firewall.

## DCMA Web Services Security: SSL

***DCMA Web Services Security: SSL***

**Client Web Application**

**DCMA **
**App Server**
**or SOA**

**Web Service**

**Business Partner**
**App Server**

**User Browser**

**DB**

- Internet

**Service****Consumer**

**Service****Provider**

**Server-side**
**SSL Cert**

**Client-side**
**SSL Cert**

**Notes:**
Even internal DCMA clients look like this--just move the firewall.

## DCMA WS Compatibility Profile 1.0

**JAX RPC Client**
**(Boeing)**

**DCMA Web Service Compatibility Profile 1.0 **
- _[https://evg3.dcma.mil/docs/dcma-wscp-1.0.doc](https://evg3.dcma.mil/docs/dcma-wscp-1.0.doc)_
**Required standards for interoperability with DCMA Web Services**

**SOAP 1.1**

**HTTP 1.1**

**WSDL 1.1**

**UDDI 2.0**

**SSL 3.0**

_**DCMA WSCP 1.0**_

**DCMA SOA**

**Notes:**
Both Design Team and SkunkWorks can use JAX RPC--follow same industry-standard SOAP protocol.
Design Team implementation of JAX RPC uses Axis.  SkunkWorks implementation uses Oracle/J2EE (both are J2EE).
.Net has been tested (by SkunkWorks) as a client.  Still needs testing as web service.
Some .Net web services may not be callable using JAX RPC, but it looks like .Net can call JAX RPC web services OK.
JAX RPC is not the only protocol being investigated.  Next Design Team Pilot will utilize messaging web services.

## Notional SOA Model for EV Data Service

- Registry
**(.xsd + .wsdl)**

- Web ServiceConsumer

- Web ServiceProviders

- Web Service Client

- EV Data Web Service

**Discover (UDDI)**

**Publish (UDDI)**

**XSD**

**Consume (SOAP)**

**Gov’t Agencies**

**Contractors**

**WSDL**

- EV Data XML Schemas

**Send (XML Data)**

**Vendors will consume the EV publishing service to send monthly data**

## Contact 

**Contact **
**Information**

## DCMA Web Services Contacts

**Chris Hassler – UN/CEFACT Project Editor - DCMA**
**Chris.hassler.ctr@dcma.mil **
**310-900-6005**
**Scott Larson – Web Services Team Lead – DCMA**
**Scott.larson.ctr@dcma.mil**
**415-577-9872**
**Peter Amstutz – Chief of Network Design - DCMA**
- _[Peter.amstutz@dcma.mil](mailto:Peter.amstutz@dcma.mil)_
**310-900-6138**