And Service Oriented Architecture SOA Larry Schillberg RTV 5E

1
And Service Oriented Architecture(SOA)Larry
SchillbergRTV 5E
2
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

3
COMPASSFMCSA 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

4
COMPASSHow 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 FMCSAs
  Enterprise Architecture of the future.
• Generate new Enterprise Database for new systems.

5
IT Division Management
FMCSA Leadership
Senior IT Leadership System Ownership
Program Office Management
Governance ESC, CPB, ECCB ARB, IMA
Program Direction
Internal Programs CAG CSA 2010 FITSG NTC Legacy
COMPASS Program Organizational Chart 4/3/2006 v10
Program Management Jeff Hall
External Programs CVISN PRISM ACE/ITDS DOT IT
Consolidation
Security Management Bill Few
Organizational Change Management Bill Coleman
Contract Management TBD
Development Management Ed Dunne
Business Management Denise Baker
Stakeholders FMCSA HQ FMCSA Field States Industry
Public
Budget Finance Management Angeli Sebastian
Communications Management Bill Coleman
Infrastructure Management Steve Erlitz
Application Support Management Janet Curtis
OST/OMB Reporting Management Angeli Sebastian
Knowledge Transfer/Training Management Bill
Coleman
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
6
Component Partners of Compass
7
FMCSA Application Architecture
Connection Type Key
Federal Infrastructure Systems
Distributed to State, Roadside, and/or Federal
Facilities
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)
1 4
Central Systems
ProVu
7, 8
7 8 10
CASERITE
Office Systems
5 6 7
10
8, 10
CAPRI
Field Systems
UFA
1 5
Web Sites
Pay.Gov Website
9
VUU
External Systems
S Determined by State
Key is located nearest to system initiating data
exchange
7, 10
4
7, 8
FMCSA Websites
EMIS
8
8
FMCSA Home
10
ASPEN
PIQ
Info Sys
1 2 3 4 6
1 2 3 4 6
Tech Support
1 2 3 4 5 6
10
2 3 4 5 6
Nat Trng Ctr
Gotham
ISS
CVISN
Mgmt Info Portal
Query Central
HMPIP Client
7
SAFE Home Page
2, 4, 5, 6
8
4
8
Share Road Safely
SAFETYNET 2000 Blizzard
S
4
8
MX MC Info
1, 2, 4, 5, 6
1 2 4 6
State Unique Systems
CVIEW
EDMS
2 6
CDLIS Access
1 2 3 4 6
1
2 6
Federal Infrastructure Systems
A I
8
7
8
TML / CDLIS Software Pointer System
HMPIP Central Site
SAFER / PRISM Central Site
MCMIS
8
8
8
4
CDLIS
Mexican SCT
L I
SAFER
PRISM
6
4
FARS
8
Support to FMCSA Systems
9
COMPASS High Level Architecture
10
Volpes 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.

11
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 SAICs 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 (OM Future, QA/UAT, Production).
• Provide a secure and efficient computing
  platform.
• Provide FMCSA and SAIC with whatever support is
  requested.

12
Volpe Staff
13
COMPASS Roadmap
YEAR 1
YEAR 2
R7
R7
Enforcement
EMIS
R8
R8
SafeStat
Prioritization
R1
Release 1
Remove Selection Assign MCMIS SAFETYNET
R9
ISS, ASPEN, PIQ, Query Central, CDLIS Access and
Inspections in MCMIS/SAFETYNET
R9
Inspection
R2
Full Public Access
R2
Remove Public Facing web (except Registration
site)
R3
Build Streamline Registration
R3
R10
R10
Reviews
Remove Registration in MCMIS and LI
Sync. Data from COMPASS to MCMIS/LI
R11
R11
Crash
MCMIS SAFETYNET retired
Load data to COMPASS
R12
R4
R4
R12
SAFER PRISM
LI and monitoring from MCMIS
Data Exchange
Regulatory Compliance Monitoring
R13
R13
Business Monitoring
R5
CRM
R5
R6
R6
Reporting in legacy systems, Gotham and AI
Data Warehouse
R14
R14
Challenge Data
DataQs
R15
HM Package Inspection
Wireless Pilot
14
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 Volpes future involvement in the COMPASS
  project.

15
The Goal of Service Oriented Architecture
The Goal of Service Oriented Architecture
Make I.T. more flexible
And enable application re-use.
16
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 servicesand 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

17
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

18
How Does COMPASS use SOA?

Internet
User
FMCSA Portal
19

• QUESTIONS?