crlms implementation overview crlms tag october 7, 2008 saratoga springs, ny
Post on 04-Jan-2016
212 Views
Preview:
TRANSCRIPT
CRLMS Implementation Overview CRLMS Implementation Overview
CRLMS TAG October 7, 2008
Saratoga Springs, NY
Topics …Topics …Implementation Plan - Structure Overview
Scope of Work & Deliverables - Implementation Tasks
Schedule & Work Breakdown Structure - Team & Responsibilities
Data Population - Data Identification & Validation
Assumptions & Constraints
Implementation PlanImplementation Plan
• Contents at a Glance
Implementation PlanImplementation Plan
• Define critical implementation areas
– Scope and objectives – define tasks, deliverables and acceptance criteria
– Project management – define structure and process
– Procedure – define constraints, risks and monitoring
– Work breakdown – define subcommittee tasks and procedure
– Schedule – define major tasks and milestones by subcommittee
Scope of Work & DeliverablesScope of Work & Deliverables
• Tasks
– Business analysis– Best Practice adaptation of
business processes (Fit Gap)– Network, hardware, software and interface
requirements– System security processes
Scope of Work & DeliverablesScope of Work & Deliverables
• Tasks (continued)
– Data population and interfaces– Use case development and testing– Pilot project planning– Training– Application support– Report development– Documentation
• Deliverables– Equal Employment Opportunity and
Affirmative Action (EEO/AA) monitoring
– Wage and labor monitoring– DBE/MBE/WBE program monitoring– Civil rights, labor, on-the-job training (OJT), and
DBE/MBE/WBE reporting– Integration with other Trns•Port functional components– Data migration from existing Trns•Port modules– Base data for DBE/MBE/WBE data analysis
Scope of Work & DeliverablesScope of Work & Deliverables
Scope of Work & DeliverablesScope of Work & Deliverables
• Acceptance Criteria– All applicable business analysis, process
adaptation, policies and procedures have
been addressed, documented and approved– Reference/Code table information has been
entered, tested and approved– All personnel expected to access CRLMS are trained in system
use, policies and procedures– Required hardware and software has been delivered to end-users– CRLMS has successfully completed all testing requirements and
can be accessed and operated by end-users– CRLMS support system is complete and accessible by end-users
Work Breakdown Structure & Schedule Work Breakdown Structure & Schedule
• Team structure– Define stakeholders– Define subcommittees by functional area
• Work Breakdown Structure– Define basic subcommittee tasks (Analyze,
define and document current business processes)– Define CRLMS implementation related tasks (Fit Gap analysis,
custom reports and interfaces identification, reference data, code table data and generic field use definition)
– Durations, predecessor and successor relationships lead to a project schedule
Work Breakdown Structure & ScheduleWork Breakdown Structure & Schedule
• Schedule– Define major tasks, milestones and project
deliverables for each functional area (Subcommittee)
– Establish timelines for tasks, milestones and project deliverables
Data Population and InterfacesData Population and Interfaces
• The Big Question -
To populate historical data or not?– Determine what data will be
populated– Consider the form of the data (spreadsheet, database, paper, pdf, docs …)– Determine the ROI on population of historical data– Consider the workload of the individuals required to
populate the data
Use Cases, Training & PilotUse Cases, Training & Pilot– Use Case Development
– Use Case Testing
– New Process Validation
– Custom Training Manuals
– Custom Training Database
– Pilot Training
– Pilot Process Validation
Assumptions, Constraints & RisksAssumptions, Constraints & Risks
• Assumptions– Minimum hardware/software specs are in place.
See (https://www.cloverleaf.net/sys_arch/wt/)
– All Client/Server applications are upgraded to
latest version, to ensure interfaces work
properly.
• Constraints– Applications Servers, and most current database software must be in
place.
• Risks– Data population is not completed on schedule or worse, is inaccurate.
And remember…And remember…
……or something like that!or something like that!
• We’ll tackle that bridge when we come to it…
• You’ve just got to bite the elephant one at a time…
• It’s all about connecting the lines…
• Ask for the moon and you might get green cheese…
• Let’s not re-invent a dead horse…
• Change is inedible…
• You need to think outside the dots…
• Whatever floats your goat…
• Well…That’s it in a nut!
top related