1 / 5

MCESA IIS T-ODCT Manual vs Automatic Error Reporting

This presentation discusses the current manual process of information error reporting within the MCESA IIS T-ODCT framework and proposes an automatic solution. The manual method involves multiple steps, including manual ticket creation by MCESA ITS. In contrast, the proposed automatic system allows for direct creation of Remedy tickets through an evaluators' email and the system itself. Future steps include solutions for verifying technological feasibility and potential cost implications for transition to an automated process.

allen-kerr
Télécharger la présentation

MCESA IIS T-ODCT Manual vs Automatic Error Reporting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MCESA IIS T-ODCT Manual vs Automatic Error Reporting Presented to: Al Dullum August 20, 2012 Fahria Nelson Project Manager Marina Stover Technical Writer

  2. Current method: Manual processing of Information Error Report information 3. ODCT generates and stores a text log on the server. 1. Evaluator Clicks Report Information Error Button 2. Evaluator fills out form, clicks Submit. 4. ADE resource retrieves text log daily, emails log to MCESA ITS. 5. MCESA ITS extracts each Evaluator-reported error and manually creates individual Remedy tickets. 6. MCESA ITS begins Level 1 Support for each reported error. 2

  3. Future Method: Automatic processing of Information Error Report information Evaluator Garcia Error Report Details 1. Evaluator Clicks Report Information Error Button 2. Evaluator fills out form, clicks Submit. 3. ODCT uses the email address in the ticket to generate an email to Remedy on behalf of that Evaluator. 4. Remedy receives the email and automatically creates a Remedy ticket in the system for that Evaluator. 5. MCESA ITS begins Level 1 Support for that Evaluator. 2

  4. Next StepsPossible Solutions Solution 1: Remedy to confirm that the solution explained in slide 3 is technologically possible. Remedy will charge $4500 for this assessment. MCESA has to decide to pursue this or not. Effort and Cost Estimate to implement the Automatic Solution in Previous Slide Solution 2: Maintain Current Manual Solution utilizing MCESA Resource (Slide 2). Solution 3: ADE to hire (MCESA funded) a dedicated part time person to collect the error log and enter issues directly to Remedy as they come in. This will streamline the process by removing the extra email log communication between MCESA and ADE. (see slide 2 for current process).

  5. MCESA IIS T-ODCT Manual vs Automatic Error Reporting

More Related