View Presentation
Upcoming SlideShare
Loading in...5

View Presentation






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Discuss the interaction amongst all providers and FMCSA. Stress the cooperation and respect between all staff.
  • MCMIS New MCMIS (AAC) (Volpe)
  • PROVIDE Whatever we can to support COMPASS success.
  • Discuss the need to start the training for OPS and technical support staff for O&M implementation.

View Presentation View Presentation Presentation Transcript

  • And Service Oriented Architecture (SOA) Larry Schillberg RTV 5E
  • FMCSA Mission
    • Federal Motor Carriers Safety Administration (FMCSA) Mission: Reduce highway deaths, crash injuries, and injury severities by collecting crash data and disseminating a statistically accurate database to be used (1) by Government in creating regulations and legislation and (2) by industry to improve the crashworthiness of vehicles and increase the ability of vehicles to avoid crashes
  • COMPASS FMCSA Objectives
    • FMCSA Objective :
    • The Federal Motor Carrier Safety Administration (FMCSA) has identified a significant need to transform the way the agency collects, manages, and conveys information.
    • Develop and support a system that (1) allows motor vehicle safety information accessible to FMCSA staff as well as motor carriers. To modernize its current information technology portfolio
  • COMPASS How will COMPASS help?
    • Technical Approach : Five-year project:
    • Implement modernization enhancements to all FMCSA Legacy systems.
    • Provide technical support to the system and to all motor carrier field and headquarters staff.
    • Implement new technology to allow FMCSA staff to conduct business. The new technology will utilize Service Oriented Architecture (SOA) web portal technology.
    • COMPASS Architecture will become FMCSA’s Enterprise Architecture of the future.
    • Generate new Enterprise Database for new systems.
  • COMPASS Program Organizational Chart 4/3/2006 v10 IT Division Management FMCSA Leadership Senior IT Leadership System Ownership Program Office Management Governance ESC, CPB, ECCB ARB, IMA Internal Programs CAG CSA 2010 FITSG NTC Legacy Program Management Jeff Hall Budget Finance Management Angeli Sebastian Security Management Bill Few Communications Management Bill Coleman Infrastructure Management Steve Erlitz Application Support Management Janet Curtis OST/OMB Reporting Management Angeli Sebastian Organizational Change Management Bill Coleman Contract Management TBD Development Management Ed Dunne Business Management Denise Baker External Programs CVISN PRISM ACE/ITDS DOT IT Consolidation Stakeholders FMCSA HQ FMCSA Field States Industry Public COMPASS Program Manager, IT Development Team, IT Business Requirements Team, IT Security Team IT Planning Division, IT Project Management Division, IT Operations Division IT Service Providers – SAIC, RSIS, Volpe, NDSU, COTS Program Coordination / Input Program Direction Knowledge Transfer/Training Management Bill Coleman
  • Component Partners of Compass
  • CASERITE CAPRI UFA ISS CVIEW SAFETYNET 2000 Blizzard HMPIP Client FMCSA Application Architecture CDLIS Access EMIS TML / CDLIS Software Pointer System L & I Federal Infrastructure Systems Distributed to State, Roadside, and/or Federal Facilities Federal Infrastructure Systems FMCSA Websites Pay.Gov Website A & I SAFER / PRISM Central Site SAFER PRISM ProVu PIQ Query Central 1 2 3 4 6 2 6 1 2 3 4 6 1 2 3 4 6 1 2 4 6 7, 8 9 1 4 1 HMPIP Central Site 2, 4, 5, 6 8 8 5 6 7 2 6 S 7, 8 8 Connection Type Key* 1 - Dial-up 2 - AAMVANet Frame-Relay 3 – Wireless to Volpe Direct 4 - FTS 2001/WAN 5 – Internet via VPN/IPSec Client 6 - Internet via Persistent VPN 7 - CD-ROM/Diskette/File Copy 8 - LAN 9 - Written Report/Verbal 10 – Machine Local 11 – Internet HTTP(S) 6 4 4 1 5 7 8 CDLIS Mexican SCT 4 8 8 8 7, 10 1, 2, 4, 5, 6 10 10 7 8 10 8, 10 VUU 10 = Field Systems = Office Systems ASPEN EDMS MCMIS = Central Systems = Web Sites = External Systems State Unique Systems S – Determined by State FMCSA Home Info Sys Tech Support Nat Trng Ctr Gotham CVISN Mgmt Info Portal SAFE Home Page Share Road Safely MX MC Info 7 FARS 4 8 4 8 8 *Key is located nearest to system initiating data exchange 2 3 4 5 6 1 2 3 4 5 6 I I I I I I I = Web Site or Web-enabled application I I I
  • Support to FMCSA Systems SYSTEM Appl Dev & Maint Infrast. Hosting Tech. Help Desk A&I   X X ASPEN     X CAPRI X X CaseRite     X CDLIS     X COMPASS   X X E-Auth X X X EDMS X X X EMIS X X X FMCSA (web sites)   X   GOTHAM   X X HMPIP X X X INFOSYS   X X ISS     X L&I X X X MCMIS X X X MSPROJECT   X   PIQ     X ProVu     X QC   X X SAFER X X X SAFETYNET X   X UFA     X         TOTALS 8 15 21
  • COMPASS High Level Architecture
  • Volpe’s Role on Compass
    • Provide FMCSA with quality technical assistance, CM Control, Help Desk functions, and knowledge support of the Existing Systems.
    • Analyze and recommend technical solutions.
    • Host a secure and efficient computing platform.
    • Manage the COMPASS repository for all code, files, scripts, etc.
    • Analyze, generate, and implement an integrated Configuration Management plan working with SAIC and other FMCSA service providers.
    • Work with SAIC to implement the new technology.
    • Provide liaison capabilities to the Existing Systems development team.
  • Volpe Objectives
    • Manage the Compass Integration Environment (CIE) to provide FMCSA and the System Integrator (SAIC) with controlled access to the current operational environments and the documentation and software that underlie that environments.
    • Design, develop, and implement (as part of the CIE) all necessary environments to be used to integrate new capabilities developed by SAIC and to maintain the existing COMPASS systems.
    • Review SAIC’s planning and technical products and advise the FMCSA Program Manager as to their quality, completeness, and adequacy.
    • Generate an integrated Configuration Management (CM) plan for the entire project.
    • Host and manage the Compass technical platform (development (O&M – Future, QA/UAT, Production).
    • Provide a secure and efficient computing platform.
    • Provide FMCSA and SAIC with whatever support is requested.
  • Volpe Staff Larry Schillberg Program Manager Infrastructure 2 FTE’s Tom Truong Kun Wang Luke Ho Michelle Bonugli Srini Configuration Management 2 FTE’s Jeff Mullen Wei Gao Existing Systems Coding and Analysis 1 FTE Howard Bailey
  • COMPASS Roadmap Release 1 Remove Selection & Assign – MCMIS & SAFETYNET Full Public Access Remove Public Facing web (except Registration site) R2 Build Streamline Registration Remove Registration in MCMIS and L&I Sync. Data from COMPASS to MCMIS/L&I Load data to COMPASS Regulatory Compliance Monitoring R3 R4 L&I and monitoring from MCMIS CRM R5 Data Warehouse R6 Reporting in legacy systems, Gotham and A&I Enforcement R7 EMIS Wireless Pilot Inspection ISS, ASPEN, PIQ, Query Central, CDLIS Access and Inspections in MCMIS/SAFETYNET R9 Prioritization R8 SafeStat Reviews R10 Crash MCMIS & SAFETYNET retired R11 Data Exchange R12 Business Monitoring R13 Challenge Data R14 DataQs HM Package Inspection R1 R2 R3 R4 R5 R6 R7 R8 R9 R10 R11 R12 R13 R14 R15 SAFER & PRISM YEAR 1 YEAR 2 Qtr1 Qtr2 Qtr3 Qtr4 Qtr1 Qtr2
  • The Future of Compass
    • Continue to work with FMCSA and SAIC on tasks associated with the Compass Road Map.
    • Work with the FMCSA systems providers to implement the CM Plan.
    • Build more efficient systems capabilities and retire the existing systems based on road map.
    • Implement COMPASS Release 1 including the enterprise database.
    • Secure Volpe’s future involvement in the COMPASS project.
  • The Goal of Service Oriented Architecture The Goal of Service Oriented Architecture … And enable application re-use . Make I.T. more flexible …
  • What is …..? … a service? A repeatable business task – e.g., check customer credit; open new account … service orientation? A way of integrating your business as linked services and the outcomes that they bring … service oriented architecture (SOA)? An IT architectural style that supports service orientation … a composite application? A set of related & integrated services that support a business process built on an SOA
  • COMPASS Service Oriented Architecture (SOA)
    • CURRENT SOA Service
    • COMPASS utilizes SOA to provide services for Single Sign-ON to existing systems.
    • Future Services
    • Depending upon Business needs
    • Work with CSA 2010 project team to define COMPASS requirements
  • How Does COMPASS use SOA? Internet User FMCSA Portal