140 likes | 290 Views
8/27/2012 7:37:52 PM. . 2.1 Purpose
E N D
1. 8/27/2012 8:04:14 PM Maryland CVISN Program PlanTable of Contents 1 Executive Summary
2 Introduction
3 Program Objectives & Project Descriptions
4 Program Requirements and Design
5 Program Work Breakdown Structure
6 Organization Structure
7 Work Assignments
8 Procurement Strategy
9 Program Processes
10 Phases and Critical Milestones
11 Funding Resources and Program Budget
12 Products
13 Program Issues to be Resolved
Appendix A: Point of Contact List
Appendix B: CVISN Acronyms & Program Definitions
Appendix C: COACH Part 2 Checklist 2.1 Purpose & Scope
2.2 CVISN Overview
2.3 Maryland’s Role in CVISN
2.4 CVISN Benefits
2. 8/27/2012 8:04:14 PM 2.1 Purpose & Scope Purpose, scope, and objectives
High level system design baseline
Supporting organizations
Work breakdown and responsibility
Program management processes
Deliverables and schedule
Estimated costs and resources required
Issues to be resolved
Project personnel and external contacts
3. 8/27/2012 8:04:14 PM 2.1 Purpose & ScopeThis plan provides a management framework to achieve the objectives of the MD CVISN Prototype Program Maryland is using a multi-level planning approach:
4. 8/27/2012 8:04:14 PM
5. 8/27/2012 8:04:14 PM 2.1 Purpose & ScopeCVISN Projects will Transition to the TARIS 2 Program
6. 8/27/2012 8:04:14 PM 2.2 Commercial Vehicle Information Systems and Networks (CVISN)
7. 8/27/2012 8:04:14 PM
8. 8/27/2012 8:04:14 PM
9. 8/27/2012 8:04:14 PM
10. 8/27/2012 8:04:14 PM 1-9-97. Added ASAP MCDC to Carrier column. Added ASAP Admin Mgt/CAPRI to Core Infrastructure (FHWA area). Removed ASAP from State column.
1-16-97. START OF 970116 CHANGE REQUEST...Changed SAFETYNET to SAFETYNET/AVALANCHE.
1-20-97. Changed IRP to Registration. Changed ASAP Admin Mgt to ASAP Analysis Mgt per Volpe (Mitchell) advice. Rearranged boxes to put Pilot systems at top of each list. Changed CVIEW to CVIEW/Data Mailbox. Sorted communication service examples in alphabetical order. Greyed out ASAP, since not really part of Pilot.
2-4-97. Added CAPRI Compliance Reviews) to State column. Clarified ASPEN function by adding (Inspections).
2-5-97. Corrected spelling of “Register”. Added LSI/LM to Titling. Changed Registration back to IRP.
2-20-97. Based on comments from KER, changed roadside block to be RES [instead of Electronic Clearance], Citation & Accident System [instead of Citation & Accident]. Also added LSI/LM boxes to RES & ASPEN.
2-28-97. Reworked roadside systems, after review with KSS, JAS. Changed caps on HazMat. END OF 970116 CHANGE REQUEST BASELINE CHANGE...
3-7-97. START of 970307 CHANGE REQUEST... Added “/Intrastate” to IRP box. END of 970307 CHANGE REQUEST
3-18-97. START OF 970318 CHANGE REQUEST ... Group Core Infrastructure Systems into Multi-State and FHWA. END OF OF 970318 CHANGE REQUEST.
6-5-97. START OF 050297 CHANGE REQUEST...Add Internet & GUI to Carrier Systems block. END OF 050297 CHANGE REQUEST.
7-10-97 START OF 970710 CHANGE REQUEST...Add Treasury System to State Systems block; shift ASPEN & Citation & Accident to safety segment of State Systems. END OF 970710 CHANGE REQUEST
8-20-97. should have been part of 050297 Change SAFER/CVIEW GUI to SafeVUE.
19990225 (and earlier)
CRF 285 - Remove SafeVUE and State Safety information System. Change Internet Applications to Internet Tools. Drop “/Data Mailbox” from both SAFER and CVIEW. Add WebCAT.
CRF 311. Add categories for each group of systems. Remove many carrier systems. Change Taxnet to FTS 2000.
CRF 529 - Add E-Screening Enrollment.
CRF 530 - Remove UCR. Add RSPA HazMat, Licensing & Insurance, and SSRS.
19990226 - KER requests changing “CAT” to something less specific. Accordingly, changed to “Credentialing System (e.g., CAT) 1-9-97. Added ASAP MCDC to Carrier column. Added ASAP Admin Mgt/CAPRI to Core Infrastructure (FHWA area). Removed ASAP from State column.
1-16-97. START OF 970116 CHANGE REQUEST...Changed SAFETYNET to SAFETYNET/AVALANCHE.
1-20-97. Changed IRP to Registration. Changed ASAP Admin Mgt to ASAP Analysis Mgt per Volpe (Mitchell) advice. Rearranged boxes to put Pilot systems at top of each list. Changed CVIEW to CVIEW/Data Mailbox. Sorted communication service examples in alphabetical order. Greyed out ASAP, since not really part of Pilot.
2-4-97. Added CAPRI Compliance Reviews) to State column. Clarified ASPEN function by adding (Inspections).
2-5-97. Corrected spelling of “Register”. Added LSI/LM to Titling. Changed Registration back to IRP.
2-20-97. Based on comments from KER, changed roadside block to be RES [instead of Electronic Clearance], Citation & Accident System [instead of Citation & Accident]. Also added LSI/LM boxes to RES & ASPEN.
2-28-97. Reworked roadside systems, after review with KSS, JAS. Changed caps on HazMat. END OF 970116 CHANGE REQUEST BASELINE CHANGE...
3-7-97. START of 970307 CHANGE REQUEST... Added “/Intrastate” to IRP box. END of 970307 CHANGE REQUEST
3-18-97. START OF 970318 CHANGE REQUEST ... Group Core Infrastructure Systems into Multi-State and FHWA. END OF OF 970318 CHANGE REQUEST.
6-5-97. START OF 050297 CHANGE REQUEST...Add Internet & GUI to Carrier Systems block. END OF 050297 CHANGE REQUEST.
7-10-97 START OF 970710 CHANGE REQUEST...Add Treasury System to State Systems block; shift ASPEN & Citation & Accident to safety segment of State Systems. END OF 970710 CHANGE REQUEST
8-20-97. should have been part of 050297 Change SAFER/CVIEW GUI to SafeVUE.
19990225 (and earlier)
CRF 285 - Remove SafeVUE and State Safety information System. Change Internet Applications to Internet Tools. Drop “/Data Mailbox” from both SAFER and CVIEW. Add WebCAT.
CRF 311. Add categories for each group of systems. Remove many carrier systems. Change Taxnet to FTS 2000.
CRF 529 - Add E-Screening Enrollment.
CRF 530 - Remove UCR. Add RSPA HazMat, Licensing & Insurance, and SSRS.
19990226 - KER requests changing “CAT” to something less specific. Accordingly, changed to “Credentialing System (e.g., CAT)
11. 8/27/2012 8:04:14 PM 2.3 Maryland’s Role in CVISN Work in a partnership with the FHWA & Virginia
Be an early adopter of CVISN concepts & technologies
Implement operational systems that meet MD’s needs & are also useful as national models/examples
Show that CVISN concepts & technologies can work in real operational environments
Provide a “typical” state environment as a test bed
Part of a major traffic corridor (I-95)
Multiple agencies involved
Significant CVO activity, but still a manageable size for a prototype
Provide feedback on costs & benefits
Champion lessons learned to CVISN Pilot States & others
12. 8/27/2012 8:04:14 PM 2.4 CVISN BenefitsBenefits of MD CVISN Program to State Administrators Data interchange among states, carriers, financial institutions, and insurance companies will be electronic
Administrators and enforcement personnel will have electronic access to required data
Credentials issuance, tax filing, interstate reconciliation, and audits will be automated to proceed more effectively and efficiently
Enforcement resources can be focused on non-compliant carriers and drivers
Better enforcement of registration, licensing, weight, size, and tax regulations
13. 8/27/2012 8:04:14 PM 2.4 CVISN BenefitsBenefits of MD CVISN Program to Motor Carriers Reduced administrative burden in regulatory compliance
Electronic Credential Application / Electronic Tax Filing
Electronic access to credential, tax, & safety data
Vehicles of safe & legal carriers will incur less delay
Mainline clearance
Automated inspections
Technology investment can support multiple services
Tag
On-board Computer & Sensors
Fleet Management Software
Uniformity of services across North America
Clearance - Toll - Traffic Management - Traveler Information
Focus on unsafe carriers will “level the playing field”
14. 8/27/2012 8:04:14 PM 2.4 CVISN BenefitsBenefits of MD CVISN Program to Shippers Improved motor carrier safety
More efficient & effective motor carriers
Fewer delays & more predictable schedules
Improved access to motor carrier safety information