Problem & Enhancement Tracking System (PETS)

Overview

This is an overview of the subsystem within ECMS for reporting problems and requesting enhancements to the software.

Fields

*	Mandatory when the issue is first logged.
**	Mandatory when the issue is being closed.

Field Name	State	Description
Issue #	Protected – System Generated	The system will generate the next available number when the document is submitted for the first time.
System	* Editable – Mandatory	The system field is selected by the authorized user when logging a problem or enhancement. The system field contains the PennDOT system that the issue is being logged against. Once the issue has been logged this field cannot be changed.
Region	* Editable – Mandatory	Authorized user must select the region they are logging the problem or enhancement against. Once the issue has been logged this field cannot be changed. The default value for this field is Production".
Window Title	* Editable – Mandatory	The window title is a descriptive name that identifies where the error occurred or where the enhancement needs to take place. The developer will use this information to determine what look at when making their assessment of the change request. Once the issue has been logged this field cannot be changed.
Originator	* Editable – Pre-Populated, Mandatory	This field is pre-populated with the users name who is logging the issue. The persons name that displays in this field should be the person that identified the issue. Therefore that logger of the issue can change the name to that persons name so that the developer or Workgroup can identify the originator of the issue if they need to contact them for additional information. Once the issue has been logged this field cannot be changed.
Phone Number	* Editable – Mandatory	The phone number enter here is to be the number to the person that is displayed in the originator field. Once the issue has been logged this field cannot be changed.
Description	* Editable – Mandatory	The user is to enter a detail description of the issue in this field. This is what the developer will use to determine that course of action. If the information in this field is vague then a proper estimate of hours to fix the problem or perform new enhancements might not be approved by the Workgroup. Critical problems might take longer to fix because the developer needs to contact the originator to determine what is really being asked for. Clear description here will speed the process along for quicker response to the issue. Once the issue has been logged this field cannot be changed.
Approval Authority	Populated	This field is populated with the approvers name when the status field (approve or reject") is selected.
Approval Date	Populated	This field is populated with the system date when the status field (approve or reject") is selected.
Status	Editable – Optional	An authorized approval user selects approved or reject from this field. Once the issue is approved the issue is looked at by the development team and sent to the Workgroup for their approval. Rejected ones are stored but do not continue on in the process.
Severity	Editable – Optional	A severity field is the ranking of the issue from low priority to critical being the highest a issue can receive.
Priority Nbr		A priority number can only be applied to a high severity, the list box stays hidden until the authorized user selects high from the severity field. A priority number is to only be applied to high severity if the problem is to supersede other highs.
Comments	Editable – Optional	The authorized approval user enters any comments that they have about the issue.
Time, Manpower & Savings	Editable – Optional	Issues logged for enhancements are required to describe how the enhancement will benifit PENNDOT. Any enhancement that does not have this field filled out will be moved into production.
Classification	** Editable – Mandatory	The classification field is a drop down box that the development staff member selects from to display what type of issue it is. There are different classification and more that can be added later, some of the standard ones are Bug, Enhancement, Documentation, etc..
Assigned To	Editable – Optional	One or more development staff members can be assigned to a issue. If more then one staff member is assigned to a issue one will be designated the primary contact person.
Reviewed	Editable – Optional	If the issue needs to be reviewed than "Yes" is selected to show a review process had to be performed. There are times that the developer will immediately no what the issue is and not need to review.
Due Date	Editable – Optional	The day the issue is due to be completed and rolled into production. Sometimes there will not be a set Due Date if the issue is a problem that is holding up users work. This type of issue is immediately worked on and move to production when completed.
Workgroup Estimate Hrs	Editable – Optional	This field contains a approximate estimate of hours that it will take the development team to perform the work. This estimate is then presented to the Workgroup for approval, only low level problems and all enhancements will go through this estimate process. Any critical problems that effect users work will be assigned, worked and completed and then presented to the Workgroup notifying them of the critical problem.
Workgroup Approval	Editable – Optional	All noncritical problems and enhancements must first be approved by the Workgroup before they can be worked on. This field will display the Workgroups approval or rejection of a issue.
Platform	** Editable – Mandatory	Developer will select and display what platform the issue falls in. This can range from what type of software was used to build the application to what hardware the user was using. This is informational for the development team to track where most of the problem issues are occurring.
Application	** Editable – Mandatory	Developer enters the application that the issue was against for tracking purposes.
Est Hrs to Complete	** Editable – Mandatory	Developer enters the hours that they need to start and complete an issue.
Start Date	** Editable – Mandatory	Developer enters the actual date they started working on the issue.
Code Type	** Editable – Mandatory	Developer enters what the issue deals with an on-line application (being Web), batch application or its not applicable to an application. More codes can be added a another date but these are the standard ones.
Used Hrs	** Editable – Mandatory	Devloper keeps track of the hours they work on an issue within this field.
Target Completion Date	** Editable – Mandatory	Developer enters the date that the issue will be completed.
Documentation Required	Editable – Optional	Developer selects "Yes" or "No" depending if any documentation needs to be changed or added.
Build Number	Editable – Optional	Developer enters a production release number if one is applicable, critical problems would not have one since they are released back into production right after completion. Others like enhancements and low level problems will be grouped and given a build number so that they can be migrated on a preset date to production.
Actual Hrs to Complete	Populated	This field is populated with data from the Used Hrs field.
Estimate Hrs Overage	Populated	This field is populated by subtracting the Est Hrs to Complete from the Used Hrs.
Resolution	** Editable – Mandatory	Developer enters in the resolution to the issue. This field will be used to pre-populate the sign-off for approval by the Bureau Directors.
Date Resolved	** Editable – Mandatory	Developer enters the date the issue was completed.
Date sent for user testing	Editable – Optional	Developer enters the date the issue was sent to the user to user acceptance test.
Date user completed testing	Editable – Optional	The date the developer is notified by the user that they are finished testing and found no problems.
Date signoff sent user	Editable – Optional	Developers enter the date that the sign-off sheet was sent to the Directors for their approval.
Date signoff received back	Editable – Optional	The date that the developer received the sign-off sheet back from the Directors.
Date migrated to production	Editable – Optional	The date the issue was put into production.
File Upload	Editable – Optional	This control can be used by anyone that has authorization to attach files to an issue. There are no limits on how many attachments that can be placed on an issue.
Notes	Editable – Optional	This field is for any addition iformation or comments that a authorized user wants to add.

Actions

Action	Description
Back	Returns user to previous screen.
Submit	Button display's only when a new issue is being logged. A unique issue number is generated, the issue is saved and the user is returned to the Problem & Enhancement Tracking System (PETS) homepage.
Save	This button appear when the authorized user is editing a pre-existing issue. Pressing this button saves the changed issue information and returns the user to the screen.
Save & Exit	This button appear when the authorized user is editing a pre-existing issue. Pressing this button saves the changed issue information and returns the user to the Problem & Enhancement Tracking System (PETS) homepage.
Delete	This button appear to an authorized users that have rights to delete a pre-existing issue and then returns the user to the Problem & Enhancement Tracking System (PETS) homepage.
Edit	This button will only appear to an authorized user that has the right to edit a issue that was already created.

Created by
Joseph D Howe/PennDOT on 03/16/2005 at 10:54:57 AM