TEXAS PERMITTING & ROUTING OPTIMIZATION SYSTEM ACCEPTANCE TEST TxDOT Motor Carrier Division

Transcription

1 TEXAS PERMITTING & ROUTING OPTIMIZATION SYSTEM ACCEPTANCE TEST TxDOT Motor Carrier Division Author: Kristy Schultz Creation Date: August 7, 0 Version:.0 Approvals: Ray Hutchinson, Project Manager Carol Davis, Project Sponsor

2 Introduction The purpose of the acceptance test was to test the Texas Permitting & Routing Optimization System in a production environment and verify that the new system meets the predefined acceptance criteria for the TxDOT Motor Carrier Division. The acceptance test took place on August 7, 0. Ray Hutchinson acted as the quality assurance manager and orchestrated the activities. The objectives of the acceptance test were: validate application extensions validate the data conversion and application setup confirm the system performance meets or exceeds performance requirements certify that the system can adequately support the future business needs of the TxDOT Motor Carrier Division. In summary, the acceptance test produced positive results for all items tested, with exception of a few minor items outlined under Open Issues on page 6 of this document. Implementation of the system on August 9, 0 should take place as scheduled. Acceptance Test Summary Number of s 4 Person Days to Revise Configuration Impact on Project Schedule 60 days No impact on implementation schedule; revisions will be completed as part of the warranty work.

3 Acceptance Test Method Scripts, scenario, and ad libitum business process tests were utilized in acceptance testing. One group of testers utilized scripts to test each permit type. The same group also performed ad libitum amendments to permits issued from the scripts in order to test the amendment functionality of the system. Scripts are on file with the TxDOT Motor Carrier Division. A second group of testers utilized scripts to test system flagging. For example, if a field if a mandatory field is left blank, does the user receive a flag notifying they must make an entry in that field. A third group of testers performed scenario tests to test the various unique situations that occur when the Motor Carrier Division issues specialty permits. The following outlines items tested: User account set-up and editing: Functions: TxDOT employee set-up including user rights to issue, view queues and reports. TxDOT employee cash office employees including rights to process cash permits and reports. Customer set-up including user rights to issue, view queues and reports, and self-issue parameters. Route Survey Bid Route Amendments Permit Types: 30 Day Length 60 Day Length 90 Day Length 30 Day Width 60 Day Width 90 Day Width Concrete Beam/Girder (HB093) Crane (Annual) Crane (S/P Mileage) Cylindrical Bales of Hay (Annual) Envelope Company Specific (Annual) Envelope - Truck Specific (Annual) Exempt (TxDOT Agency Only) Fracing Trailer (Annual) General 3

4 General Housemove HUB Implement of Husbandry (Annual) Manufactured Housing Manufactured Housing (Annual) Over-Axle (547) Portable Building Rig-Up Truck / Unladen Lift (Annual) Self-Propelled Off-Road Equipment Super Heavy Temporary Registration Utility Pole (Annual) Water Well Drilling Machinery & Related Equipment Well Servicing Unit (Annual) Well Servicing Unit (S/P mileage) Western Regional Acceptance Test Environment Testing was performed on server the Test and Training environment for the Production system. It was the same version as the production system at the time of testing. It is a single server (with multiple processors) that serves all functions (application, tile service, routing and data base management). 4

5 Test Participants Name Carol Davis Ray Hutchinson Lois Johnson Kristy Schultz Scott McKee Trinea Moreno Charles Landers Cliff Nelson Carl Cave Sandy Klesel Arian Rostami Charity Rehder Patricia Johnston Marie Stembridge Don Witwer Mark Lupercio Lance New Susan Price-Lasalle Roseanne Graham David Baughier Brandon Alford Rose Villarreal Roxanne Boggs Bryan Elliott Evan McGehee Elizabeth Morris Carolyn Wirth Role/Responsibility Project Sponsor Project Manager Project Contract Administrator Project Coordinator/document test results 5

6 Open Issues The following list identifies the items requiring resolution. All items listed are to be completed by the vendor, ProMiles Corp., as a part of the warranty work. Issue Resolution *Level Axle spacing: When user attempts to set axle weights, system will only accept a two-digit spacing. This is a minor item because a three digit (00 feet and over) spacing is very rare. Account set-up: When setting up cash office employees as TxDOT employees, the system will not save the cash office ID number upon initial set-up. User must return to the employees account, edit that field and re-save it. Fracing trailer and Hub trailer only permits should not receive pop-up questioning absence of truck information when on the vehicle information screen. (Permits can still be processed as trailer only by clicking OK neither is a selfissue permit type.) Need coding change to prevent Hub renewal notifications from being sent to the wire service that ordered original permit (if applicable); Renewal notices should go to the motor carrier holding the permit. Lowboy checkbox should not be on the Annual Envelope Truck Specific permit type. Lowboy checkbox and non-divisible load checkbox should not be on the Annual Envelope Company Specific permit type. Western Regional Permit template issue? The route summary prints off the bottom of page and does not roll to next, routing lost and covers fee summary and signature. The ability to issue permit types that do not require a moving authority as exempt- no fee is lost because we don t need a moving authority screen for them and that is the only place where the exempt marking is available. Customer submits application for $5 single trip temp tag to queue and clicks on unladen checkbox, when pulled up by PAS the unladen checkbox is unchecked. Vendor will change to three digits. 3 *Levels: - critical, immediate fix necessary - secondary to critical items, fix as soon as critical fixes in place 3- post launch fix, can be fixed as a part of the warranty work 6