Project Cost

425 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
425
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Even internal DCMA clients look like this--just move the firewall.
  • Even internal DCMA clients look like this--just move the firewall.
  • 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.
  • Project Cost

    1. 1. 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 06/03/10
    2. 2. Contents <ul><li>UN/CEFACT Project </li></ul><ul><ul><li>Background </li></ul></ul><ul><ul><li>Timeline </li></ul></ul><ul><ul><li>Current Status (EVG3) </li></ul></ul><ul><li>DCMA Web Services </li></ul><ul><ul><li>Registry (coming soon) </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>DCMA Web Services Compatibility Profile 1.0 </li></ul></ul><ul><li>How to Get Started </li></ul>
    3. 3. UN/CEFACT Background Timeline Current Status
    4. 4. UN/CEFACT Data Standardization <ul><li>Enhancement to DoD Earned Value Standards for EDI </li></ul><ul><ul><li>XML-based </li></ul></ul><ul><ul><li>Includes ANSI X12 806 & 839 transaction sets </li></ul></ul><ul><ul><li>Adds many new fields to support entire lifecycle of Project Cost and Schedule Management data (from Contract Initiation to Closeout) </li></ul></ul><ul><ul><li>Based on Core Components Technical Specification (CCTS) </li></ul></ul><ul><li>First Implementation Verification 90% complete </li></ul><ul><ul><li>Must complete two additional Implementation Verifications by September 06. </li></ul></ul><ul><li>UN/CEFACT adoption scheduled for September 06 </li></ul><ul><li>Working with Earned Value software vendors </li></ul>
    5. 5. 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
    6. 6. 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
    7. 7. DCMA Web Services Registry Security DCMA WSCP 1.0
    8. 8. 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
    9. 9. 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
    10. 10. 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
    11. 11. 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 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 MS .NET Client (S&S – Sealy)
    12. 12. Notional SOA Model for EV Data Service Registry (.xsd + .wsdl) Web Service Consumer Web Service Providers 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
    13. 13. Contact Information
    14. 14. DCMA Web Services Contacts <ul><li>Chris Hassler – UN/CEFACT Project Editor - DCMA </li></ul><ul><ul><li>Chris.hassler.ctr@dcma.mil </li></ul></ul><ul><ul><li>310-900-6005 </li></ul></ul><ul><li>Scott Larson – Web Services Team Lead – DCMA </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>415-577-9872 </li></ul></ul><ul><li>Peter Amstutz – Chief of Network Design - DCMA </li></ul><ul><ul><li>[email_address] </li></ul></ul><ul><ul><li>310-900-6138 </li></ul></ul>

    ×