User Guide. RACER Date 09/29/17

Transcription

1 User Guide RACER Date 09/29/17 1

2 Table of Contents Table of Contents... 2 RACER... 4 Home Page...5 RACER Requester... 6 Basic Information...6 Location Information...7 Change Information...8 Review and Submit...9 Contacts Tool Help Tool Useful Links RACER Generated Notifications Log In RACER Resolver Getting Started Requestor Resolution Tool Tracking Report Tool RACER Administrator Getting Started Managing Application Access Setting Up the RACER Box Assigning Work Request Assignment Manager Update Team Members Editing Automatic RACER s Template Management

3 Modifying RACER Lists Menu Administration RACER System Generated Error Messages

4 RACER The Roadway And Characteristic Electronic Request (RACER) application assists in the entry and execution of change requests for roadway and characteristic changes to the State of Minnesota's Linear Referencing System (LRS). RACER application allows both MnDOT staff and external users to submit requests for changes and errors or omissions to the LRS roadways and characteristics. The Submit Request screen does not require the submitter to have an AD login account. To access RACER from within MnDOT simply type RACER into the address bar of your web browser and press enter. From outside the department, type into the address bar of your browser. This will bring you to the default RACER screen. Internal users of the application (primarily MNDOT Office of Transportation System Management) login to the application to assign, process, resolve and track the submitted requests. Internal users must have an AD logon account assigned to one of the application s AD Groups: Pubic RACER USER or Public RACER ADMIN. The login area in the upper right corner of the application is color coded to let you know if you are in the production or test version of the application. Blue is production, red is test. There is additional text above the login button specifying the version and instance of the application you are accessing. The green bar below the login area has general links to the MnDOT website. The black area contains RACER menus and tools. The Public RACER USER role allows the internal app user to access the Request Resolution Screen to process the requests assigned to them. It also allows them to access the Tracking Report to see all requests and performance metrics. The Public RACER ADMIN role allows the administrative user the same access as the Public RACER USER role (Request Resolution, Tracking Report) and includes an additional menu option of ADMIN. The ADMIN functions include 1. Request Assignment Management where they can assign submitted requests to the Resolution Team 2.Update Team Members where they determine if persons are Active users in the application 3. Menu Administration where they can change the values of drop down functions in the application 4. Template Management where they can change or update the text of the s sent to the submitters when a request is submitted, being worked on, or resolved. Link to RACER Application: The application will open to the RACER Home Page. 4

5 Home Page Home Page screen When you select the Home Page tool, the application will take you back to the Splash page of the application, clearing any queries or work you have done. This does not cancel any work performed it just moves the application back to the start screen. Menu options: Home Page: Main page for the application Submit Request: Clicking on the Submit Request Menu begins the process of making a request for a change to data in the LRS. Contacts: Clicking on the Contacts Menu opens an to the MNIT@MNDOT IT Service Desk Help: Clicking on the Help Menu, gives the user the option to view Links to other useful applications 5

6 RACER Requester User credentials are not required to submit a request. To begin, Click on the Submit Request tab. The system will guide the user through a sequence of steps: Step 1. Step 2. Step 3. Step 4. Basic Information Location Information Change Information Review and Submit This is the main request function of the application. Clicking the Submit Request tool opens a series of forms which help you create a RACER support ticket. On the first page you enter your contact info. Make sure to fill it out completely and accurately. This is the information the person who will resolve your ticket uses to contact you and let you know the work was done. Basic Information Basic Information screen Step 1. Basic Request Information Enter basic request information. Any field marked with an asterisk (*) is a required field. Enter: First Name Last Name Phone Number Affiliation, select from the menu provided Address Request Type, select the appropriate option from those provided o Roadway o Roadway Characteristic 6

7 Only one Roadway or Roadway Characteristic change is allowed per request. If additional Roadway or Roadway Characteristic are being requested, each will require a request. All entries are required in this page. If unsure what to enter for Affiliation, choose Other. Most request types (including any relating to street name) will be for Roadway Characteristic. Roadway is only for cases where a road or segment of a road is: missing, assigned to the wrong route system (jurisdiction), realigned, retired, or has bad calibrations. If your request involves anything else, use Roadway Characteristic. If you select a Roadway Characteristic edit, another dropdown list will appear asking you to select which characteristic needs to be fixed. You can only select one. If you have multiple characteristics that need fixing in the same area, select the one most critical to you. There will be an opportunity later to write a description of other characteristics that also need fixing.. Click Next when you are ready to move on. When the form is complete Click on the Next button, in the lower right corner of the screen, to advance to Step 2. Location Information Location Information screen: Step 2. Request Location Information. Enter as much location information as possible, at least one entry must be made to enable the user to advance to the next step. Entry fields: County, select from the list provided City, enter the first letters and then select from the list Route System, select from the list provided 7

8 Route Number Street Name Reference Post and Offset Mileage State Project Number When entry is complete, Click on the Next button, in the lower right corner of the screen, to advance to Step 3. At least one field must be complete to advance to the next step. These inputs should be self-explanatory. If the field does not make sense to you, it most likely does not relate to your line of work and should not be used. At least one (1) field must be entered to proceed. The more information provided, the easier it will be for the resolver to locate the fix. Once you have entered your location, click Next. The third step is to enter why the data was bad. What changed to require it being fixed? For each box you check, an input will appear to describe how that location changed. If it is either: a. an overlay where nothing on the route changed, or b. data was entered incorrectly and nothing about the location changed, then select Other and explain that in the input field. To return to the previous entry screen, Click on the Back button, in the lower left corner of the screen. Change Information Change Information screen: Step 3. Requested Change Information. 8

9 Select the type or types of change you are requesting. At least one selection must be made to advance to the next step. Options are: Route System Route Number Route Extended Route Realigned Route Removed New Route Filled a Gap Other As a selection is made a text field will open. The user should enter a detailed description of the requested change. 500 character limit. When complete, Click on the Next button, in the lower right corner of the screen, to advance to Step 4. At least one selection must be made to advance to the next step. To return to the previous entry screen, Click on the Back button, in the lower left corner of the screen. Review and Submit Review and Submit screen: Step 4. Review and Submit. 9

10 Review the information entered for the request. If there is something you wish to change, use the Back button(s) to navigate to the previous screens and make changes as desired. If you wish to delete the request, Click on the Cancel Request button to delete the entry. Warning, once the Cancel Request button has been selected, all data in the request is deleted and a new request must be initiated. o Once cancelled, the application will display a cancelation message. Cancelation Message: If satisfied with all data in the entry, Click on the Submit button to submit the request. o Once submitted a message will display indicating the submission was successful. The message will include a reference number for the submission. Successful Submission Message: o o An will be sent to the address specified in the request. The will include a summary of the request for reference. Instructions will display for uploading or including documentation with the submitted request. Up to 3 attachments may be made Upload Attachments screen: o Click on the Choose button to browse for the document to select Once a document has been selected, it will be added to the Uploaded Attachments pane 10

11 Uploaded Attachments pane: If there is another attachment, repeat the previous step. Up to 3 attachments may be made. When complete, Click on the Done with Attachments button. A message will display indicating you have selected Done with Attachments: Done with Attachments Message: You should receive an immediately letting you know that the ticket was submitted and is in our system. You will receive additional s when the resolver has started working on the ticket, and again when the work is completed. There is the possibility that you may receive a request denied note if the request did not meet our business rules, or if there was insufficient information to resolve it. Contacts Tool The Contacts tool will open an window for you to submit an IT ticket requesting help with an error in the application itself. Simply fill out the required inputs and send the ticket in. Make sure to include your contact information so IT can reach you if there are questions, or to notify you when the ticket has been resolved. Help Tool Useful Links Clicking the Help tool will open a page listing additional related MnDOT applications that may help you view the data or answer some of your questions. Click the links on this page to open the other MnDOT applications or web pages. 11

12 RACER Generated Notifications RACER generates notifications to request submitters alerting them to the current status of their request(s). Submission Request Received: o Address: address entered on the change request o From: MN_DOT_RACER o To: First and Last Name entered on the change request o Subject: RACER Request #XX has been Received o Body: Thank you for your input, we have received your data suggestion and will review it shortly. We appreciate your efforts in helping us make the data as good as possible. Once it is assigned to staff they may contact you with further questions or for more information. You will receive another notice informing you when the suggestion has been processed. Status Change to In Process: o Address: address entered on the change request o From: MN_DOT_RACER o To: First and Last Name entered on the change request o Subject: RACER Work Started for Request ID o Body: This notice is to inform you that Editor Name has been assigned to review the suggestion you provided us on MM/DD/YYYY. They may contact you if they have questions or if they need more information on this suggestion. You will receive another notice when the work has been completed. Thank you for your help in making our products better. Please contact the MnDOT Transportation Data and Analysis Program at and ask for the LRS supervisor if you have questions. Status Change to Denied: o Address: address entered on the change request o From: MN_DOT_RACER o To: First and Last Name entered on the change request o Subject: RACER Request ID is not able to be completed o Body: We greatly appreciate the suggestion you submitted on MM/DD/YYYY. Our staff have reviewed the suggestion and have determined that it either does not meet our business policies or we have not been able to confirm its validity. Although we will not be implementing this particular suggestion, we appreciate your concern and welcome other thoughtful suggestions in the future. Please contact the MnDOT Transportation Data and Analysis Program at and ask for the LRS supervisor if you have questions. Status Changed to Completed: o Address: address entered on the change request 12

13 o o o o From: MN_DOT_RACER To: First and Last Name entered on the change request Subject: RACER Request ID has been Completed Body: Thank you for helping us make our products timelier and of better quality, your support is greatly appreciated. Your suggestion on MM/DD/YYYY has been processed and you should see it in our product within 7 days. Please contact us again with any issues or missing data you notice. Please contact the MnDOT Transportation Data and Analysis Program at and ask for the LRS supervisor if you have questions. Log In Resolution Team Members and RACER Administrators must Log in to the RACER application to access Menu tabs specific to their roles in the RACER application. To navigate to the Log in screen, on the Home Page, Click on the Login button in the upper right corner of the screen. The system will advance to the Log in Screen. Login Screen Log in by entering your User Name and Password in the fields and Click on the Login button below. 13

14 RACER Resolver Getting Started Roadway and Characteristic Edit Request (RACER) is a web based application. It allows users to submit requests for corrections or additions to LRS routes and data. For more background information, refer to the RACER Requestor section. To access RACER from within MnDOT simply type RACER into the address bar of your web browser and press enter. From outside the department, type into the address bar of your browser. This will bring you to the default RACER screen. The login area in the upper right corner of the application is color coded to let you know if you are in the production or test version of the application. Blue is production and red is test. There is additional text above the login button specifying the version and instance of the application you are accessing. The green bar below the login area has general links to the MnDOT website. The black area contains RACER menus and tools. There are three (3) levels of users in the RACER application: requestor, resolver, and administrator. Each role (level) has its own manual. This manual is for the resolver functions of the application. If you want to access other tools you may need to refer to the requestor manual. Resolvers do not have access to the functions granted to the administrator role. There are two (2) tools that get added to the menu/tool bar (black portion of the application) when you log in with a resolver account. These menus let you perform all of the resolver functions. Requestor Resolution Tool When you select the Request Resolution tool, the application will open the Request Resolution Manager screen for the logged in resolver or administrator. 14

15 The top portion of the screen lets you enter values to help refine the list displayed in the bottom portion of the screen. You can use the following fields to limit the results returned: Request Status limits the tickets displayed to only those in a certain status(s); Type limits to only route edits or only characteristic edits; County only edits within a selected county; System limits to routes from a selected route system; or Route# for a specific route number or comma separated list of numbers. Once the parameters are set to your preferences, press the search button. To clear the selections, press the Clear button. Some things to remember as using the search tools is that if the Requestor did not enter the information (such as not entering the route number) then it will not be searchable by that aspect of the data. If you enter its part of your search any record missing it will be omitted from the search results. You can sort the table of records meeting your search requirements by clicking on the column header for: ID Status Date Type The other columns are not sortable. To see the details of any row of the results simply click the Magnifying glass icon in the right most column, this will open a dialog window with more details and where you may edit some of the attributes. You may change the status of the request either in this details window or back in the previous list be changing the Status Drop Down box to the desired status. Once you change the status an will automatically go out notifying the Requestor of the ticket s change in status. 15

16 Tracking Report Tool The Tracking Report is a tool for a resolver or administrator to review and sort data through various filters. You can view the status of tickets from all resolvers and in all statuses. The page will automatically open showing all tickets currently assigned, regardless of the user. You can sort the report by clicking on the arrows in the column header of any of the following columns: ID Submitted Date Status Assigned To Type (Roadway vs Roadway Characteristic) Rte Sys Change* Rte Number Change* Rte Extended Change* Rte Realigned Change* Rte Removed Change* New Rte Change* Filled Gap Change* Other Change* County City Rte Sysa Rte Nbr Str Name Ref Post Mileage Proj Nbr Requestor Name Requestor Requestor Phone Affiliation Assigned Dt In Progress Dt Resolved Dt Submitted to Assigned Assigned to in Progress In Progress to Resolved 16

17 Total Days *= Free form entry fields so sorting may be unexpected. All fields, except Requestor Phone, may also be filtered. Simply enter a value or date range in the input box(es) in the column header, or select a value(s) from the built in lists. Navigation buttons at the top and bottom of the page allow you to jump forward or back by one page, or to the end of the list. There is a button in the top right and bottom right corners of the page titled Columns. When pressed it provides a list of columns on the page. Unchecking any number of these columns will remove them from your view, making for easier reading of the data you are interested in. The tool allows you to export the table to Excel, where Excel s full functionality is available. To export to Excel, click its symbol at the top or bottom of the page. 17

18 RACER Administrator RACER Administrator Home Page RACER Administrators have all of the application capabilities of the RACER Resolution Team Member with the addition of the Admin Menu tab. The Admin Menu tab gives the RACER Administrator the ability to perform the following tasks: Request Assignment Manager Update Team Members Menu Administration Template Management Getting Started This is a web based application which allows users to submit requests for corrections or additions to LRS routes and data. For more background information, please refer to the RACER User section. To access RACER from within MnDOT simply type RACER into the address bar of your web browser and press enter. The browser will bring you to the default RACER screen. The login area in the upper right corner of the application is color coded to let you know if you are in production or a test version of the application. Blue is production and red is test. There is also text above the login button specifying the version and instance of the application you are accessing. 18

19 The green bar below the login area has general links to the MnDOT website and the black area contains RACER menus. There are three (3) levels of users of the RACER application: User (Submitter), Resolver, and Administrator. Each role has its own manual. This set of directions is for the administrative functions of the application. If you want to access other tools, you may need to refer to the other manuals. Managing Application Access Before you can perform any administrative task in RACER you must have access rights and then login. If you are a new administrator, you must get an existing administrator to grant access using a two-step process. First, the administrator must grant application rights. To do this, go into the Forefront Identity Manager application. Click on the Public RACER Admin or Public RACER User link. In the dialog window that opens, click on the Members tab. In the box labeled Members To Add, type the first four digits of the new user s last name then click the (Validate and Resolve) button. A list of possible users, whose names match the string you entered, will appear. Check the box next to the name of the person you want to add and click OK. In the next box click OK again. 19

20 After the user has been added in Forefront Identity Manager you must add them in the RACER application as well. To do this, click the login button in the upper right corner of the application. Login using your system (AD) username and password. The menu bar should change showing you more options, including the Admin menu. Select this menu, then the Update Team Members option. In the resulting table click on the Add New Team Member tool at the top. In the dialog window, start typing the last name of the user you wish to add in the MnDOT Employee input box. As you type, a list of users will appear. Select your new user from the list and click the Add User button. To remove users, follow the same process in the Forefront Identity Manager application, except use the Members to Remove box. In RACER, under the Update Team Members option, find the user s name and click Remove on the right side of the table. 20

21 Setting Up the RACER Box In order to view created by the RACER application that is undeliverable, you must map the application account in Outlook. To do this, open Outlook and click the File tab at the top of the page. Directly under Account Information should be your account. Click the Add Account button under your account. Fill in your name in the resulting dialog and enter under the Address input box. Do not do anything with the password boxes. Click Next. Once the next window has completed adding the account, click the Finish button. You will most likely not see the new mailbox until you restart Outlook. This mailbox should be checked at least once per week to make sure that no application communications have failed to send. Assigning Work At least once per day you should check the ADMIN>Request Assignment Management screen to make sure that no tickets are sitting unattended. It is best to add a recurring, all day appointment in Outlook with Show As set to Free. By having it occur every work day, you will automatically be reminded to check RACER each morning when you first logon. When you open the ADMIN>Request Assignment Management screen, any tickets submitted but not assigned will be listed in the application window by default. To assign a ticket, simply click the Assigned To box in the ticket row and select the name of the Resolver to assign it to. Once selected, it will automatically be assigned and that Resolver will receive an notifying them of their new ticket. If you want view tickets in a different status, use the Request Status drop down list near the top of the page. Select the status you wish to view. You can refine your search by county, Roadway or Characteristic, or tickets assigned to a specific team member. Once your parameters are chosen, click the Search button and results matching your criteria will appear in the application window. You can then sort the results by clicking on the field name of the column you wish to sort. Sorting can be done on any of the ID, Status, Date, Assigned To, or Type columns. To clear all options and start over simply click Clear. Request Assignment Manager The Request Assignment Manager functionality allows the RACER Administrator to View, Assign, and Reassign requests to Resolution Team Members. 21

22 Request Assignment Manager Screen When selected the Request Assignment Manager opens, defaulting to display a search of all requests with a status of Submitted and no Team Member assigned. The Assignment Manager contains the following search criteria: Request Status: o All o Submitted (default) o Assigned o In Progress o Resolved o Denied Request Type: o All o Roadway o Roadway Characteristic County: o No Selection (default) o Specific County selected from the list Team Member: o Blank (default) o Specific Team Member selected from the list 22

23 User can use on one, two, three, or all criteria to perform a search. At least one search criteria must be selected. Make search selections and Click on the Search button to perform a search. To Clear your search and return to the default settings, Click on the Clear button. Search results are displayed in a table format with the following columns: ID- Request ID number, results can be sorted by ID Status- Status of the request, results can be sorted by Status Date- Date of the request, results can be sorted by Date Assigned To- Team member to whom the request is currently assigned, results can be sorted by team member Type- Type of request, results can be sorted by Type What Changed Location of Change Requestor Info RACER Administrators use the Assigned To column and the associated dropdown list to assign a Submitted request or to reassign an Assigned request. Note: The Team Member search criteria selector only allows for the selection of a specific team member. Once a Team Member has been selected, the only way to clear this criteria is to Click on the Clear button, which will clear all search criteria previously selected and return to the default settings. Update Team Members The Update Team Members opens to display a table listing all Resolution Team Members and RACER Administrators. By default the table is sorted in alphabetical order by Last Name. Update Team Members Screen 23

24 Add New Team Member To add a new Resolution Team member, Click on the Add New Team Member button located on the left side directly above the table. A RACER Application - Add Team Member window will open. Add Team Member window Search for the person by entering the first few characters of their las name in the MnDOT Employee field. A list of employees with last names beginning with the characters entered will be displayed, Select the correct person from the list. Note: Only individuals in the Active Directory group will be displayed. If the individual you are looking for does not appear in the list, they will need to be added to the Public RACER User Active Directory group before they can be added as a new user or log in to the RACER application. When you have selected a name, Click on the Add User button to add the individual as a Resolution Team Member or click the Cancel button to close the window. Edit Team member The following changes can be made to a current Resolution Team Members information Change Active/Inactive Status, a check in the box indicates the team member status is Active Remove a Team Member from the application 24

25 To make a change, find the appropritate team member in the list: To change Active/Inactive, go to the Active column; check the box if the team member is currently Inactive to make them Active or remove the check if the team member is currently Active to make them Inactive To remove/delete a team member from the application, click on the Remove link in the last column of their information. When removing a team member from the system, a pop-up will display prompting for confirmation that you wish to remove the team member, Click OK to continue and remove the team member or Click Cancel to discontinue. Confirmation Request Editing Automatic RACER s Template Management If you need to modify the text of the automatic s the RACER application sends out, use the ADMIN> Template Management option. This will display a table of the five (5) types of s the application sends, and an additional row for the account used by the application. The first column of the table is the name of the , which is descriptive of when the is sent. The second column is the text that will appear in the subject line of the . The third column contains the actual text in the body of the . The final column is an icon. When you click the icon, it opens up a dialog which allows you to alter the text in the subject or body of the . To edit a row, click the pencil icon on the rightmost column and edit the resulting dialog. When finished, click the pencil again (it may be hard to see against the dialog background). If you miss the pencil icon when clicking, the dialog will not close and no updates will apply. Within some of the text are variables. These variables are identified, before and after, by double less than << and double greater than >> symbols (i.e. <<resolution-team_member>>). Be careful when editing around 25

26 these variables as they are set in the application code and cannot be altered. New variables cannot be added without altering the application code. Modifying RACER Lists There are multiple lists contained within the RACER application. Many are controlled by system settings. For example, when selecting a Resolver to assign a ticket to, that list is controlled by the process to add or remove a Resolver s permissions to the application. Some menus can be edited by the administrators. These will be accessed by the ADMIN>Menu Administration option. Once you ve opened this portion of the application, you can choose which menu to adjust from the Modify Menu drop down list. Once a menu is chosen, you have several options. You may: 1. View/Edit an existing row of the list. Select it in the item drop down list and alter the components you wish from the resulting dialog. Remember to click Save Changes when done. You can remove an item from the list by clicking Deactivate this item button. 2. Add a new item to the menu. Fill in the resulting dialog and click Add this item when done. 3. Reactivate an item. Select it from the Inactive Item drop down list. 4. Sort the list. Use the arrows on either side of the table to move items up or down the list. Inactive items may appear on this list but will not display in the application. Once you have completed your edits, you will need to restart the RACER application before any of the menu changes will be visible. Menu Administration Menu Administration enables the the RACER Administrator to update or edit the following menus in the application: Affiliation Characteristic RACER_Links Requested_Change Request_Status Select the Menu to be edited from the list. All menu lists are modified using the same procedures. 26

27 The screen will change and display the Menu to be modified and tabs indicating the types of modifications allowed. View/Edit Add Reactivate Sort Directly below the tabs is a link to open instructions for using each of the tabs. Instruction Link Click on the link to view tab specific instructions Menu Modification Screen Do not know what the Select Admin Function link does. The following error is displayed when I click on the Select Admin Function link on the Admin Menu Administration careen: 27

28 Menu Administration Screen RACER System Generated Error Messages Do we want a section for all of the possible error messages the system may display? Message for upload error? Message for submission error? Error message displayed when no detail is added for the type of change selected: 28