Bruce Oakley NMDOT IT NMDOT AO-II (505) 827-5391 Joseph Valdez Bridge NMDOT Data Analyst 505-827-5540 David Robbins Administrative TRD ASD Director 505-827-0368 Anthony Haas Administrative TRD Budget Bureau Chief 505-476-4728 Brandi Harrison Financials Grants Management Financial Specialist 505-827-3427 Kathy Griego Administrative DPS ASD Director 505-827-9029 Diana Dejarnette Administrative DPS ASD Deputy Director 505-827-9035 Travis Lee SME NM Motor Transportation Police Permitting Transportation Inspector 575-576-2461 Matt Sena SME NM Motor Transportation Police Permitting MTD Tax Exam Coll Rev 505-476-2472 Trisha Herrera DPS IT Resources IT Generalist Kim Valenzuela MTD IT Resources MTD IT Specialist 575-542-8811 Elizabeth (Karana) Haring Contracts SME Purchasing 505-827-9626 Tim Pilcher Vendor ProMiles Software Development Corporation President 409.697.2587 Michelle Hudson Vendor ProMiles Software Development Corporation Director of Special Projects and Finance 409.697.2587 ext 235 Brandy Ashworth Vendor ProMiles Software Development Corporation State Projects & Grant Documentation (409) 697-2587 ext 235
Sub 2 The Procuring Agency will assign one of four levels of priority to each request: Priority 1 is the most severe program error and represents a situation where mission critical features and functions of the Commercial Vehicle Oversize/Over Weight Permitting and Routing System are unavailable and no practical alternate mode of operation is available. Priority 1 problems will be corrected or a solution will be provided by Contractor for corrective action within two (2) hours. Priority 2 indicates a problem in which certain features and functionality are not available and no practical alternate mode of operation is available. Priority 2 problems will be corrected or a plan will be provided by the Contractor for corrective action within one (1) Business Day. Priority 3 is the normal “next-in-line” problem priority assignment. At this level, requests are worked on in the order in which they are received. Priority 3 problems will be corrected or a plan will be provided by Contractor for corrective action within ten (10) Business Days. Priority 4 is the Release assignment. At this level, requests are worked on as deemed appropriate by Procuring Agency. Priority 4 issues will be incorporated into specific releases, documented in an Application Deployment Package, which will be scheduled for delivery at the discretion of the Procuring Agency after time and cost estimates are provided by the Contractor and approved by the Agency, if applicable. As such, priority 4 issues will be due at the time the specific Release is delivered. Deliverable 11: Year 2 Hosting, Support and Maintenance Deliverable Name Due Date Compensation Year 2 Hosting, Support and Maintenance Begins 24 Months after Acceptance of Deliverable #6, and Ends 36 Months after Acceptance of Deliverable 6. Not to exceed $140,541.34 including Receipts Tax.
4.2.3 Complete the following table to identify the deliverables this project is to produce, and to name the person or persons who have authority to approve each deliverable. See 4.1.2 4.2.4 Signed document stating formal acceptance. 5.0 5.1 (WBS) A WBS is a deliverable-oriented grouping of project elements that organizes and defines the total work scope of the project. Describe the work activities that comprise the work breakdown structure (WBS) or the work packages within the WBS. Identify the WBS element or other work package identifier and provide a general description of the tasks or activities, the definition or objectives, and the milestones and deliverables of each work package. Use the chart below for highest level presentation, and provide a more detailed WBS as an attachment to this project plan. Identifier Work Package Description Definition/Objective Milestone/Deliverable See project schedule, detailed will be defined with the vendor. 5.2 New Mexico Commercial Vehicle OS/OW Permitting and Routing System Project Schedule No. Task Name Duration Start - Days after NTP End - Days after NTP Pred Resource
Planning P-R07 Maps No maps for dispatchers, a must for CAD Darrel/Marco Work with Gar on his consolidated mapping project 2/4/2014 2/27/2014 Planning P-R11 Moving the contract through the approval process could take longer than wanted. Project delays, loss of Kim,Cesario Kim and Karana wil move the contracts through the process 2/25/2014 2/25/2014 Planning P-A29 Data Requirements assessment - meet and provide DPS with a template and help with a survey Meet and provide DPS with a template and help with a survey 3/6/2014 3/24/2014 P - Planning A - Action R - Risk I- Issue IM - Implementation Risks are mitigated - mitigated by reducing its probability of happening to zero Risk - an uncertain event that may or may not happen, that will impact your project adversely (positive or negative) affecting the outcome of the project Issues are resolved - taking action Issue - an issue is a matter in question or dispute that is disruptive to the smooth execution of a project as planned. There is no probability attached, it is a certitude. An Issue will happen, is happening now, or has already happened.
Test Plan Quality Testing Business owner, and Stakeholders review Requirements Traceability to test results and signed Production version Quality Production Baseline Technical Lead review of configuration and signed Schedule Project Time Milestones Milestone dates, status reports Budget Project Budget Milestones Budget reports, status 6.6.2 6.7 QUALITY CONTROL 6.7.1 No. Quality Standard Tracking Tool or Measure 1 Certification to proceed to next phase by DoIT Approval from DoIT Project Certification Committee and release of funds 2 Project issues/risks documented, tracked, and worked to resolution Log 3 Project budget Weekly budget review 4 Project Schedule Weekly Schedule update and review 5 Verification and Validation Scheduled reviews Issue tracking and resolution Reports 6 Project completed within budget, schedule, and scope Project Management Plan Project Change Control Process Management Steering Committee Meeting Decisions
6.7.2 AND ASSESSMENTS Review Type Quality Standard Reviewer Reports Requirements Approved and signed Requirements document Meetings, MS Word, MS Visio, other tools as needed Project Team, Project Stakeholders, Steering Committee Status Plans Input from team, Stakeholders, SMEs, vendors Meetings, MS Project, Visio, other tools as needed Project Team, Sponsor(s) Status Milestones Scheduled MS Project Project Team, Project Sponsor Status Testing Test results in alignment with Requirements Test scripts, user input, test tracking SMEs, Project Team, Project Manager Test plan, User acceptance Training All training delivered to at planned time and users Vendor dependent Business owner, SMEs Training Plan 6.7.3 of feedback When How Often MTPD s Anytime Anytime Project quality of communications Meetings Project Team meetings Manages project Meetings Monthly Productive Meetings Anytime Anytime