1 / 14

Appendix I: solutions for expected data issues

Appendix I: solutions for expected data issues. Prepared 10/14/11 for F.A.S.T. Automation Reports v4.0. Potential Data Issues with FAST Automation Reports v4.0:. FAST Vehicle Type Field (all) “BLANK” results Unreported vehicles solution Invalid vehicle solution “ ” results

naomi
Download Presentation

Appendix I: solutions for expected data issues

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. Appendix I: solutions for expected data issues Prepared 10/14/11 for F.A.S.T. Automation Reports v4.0

  2. Potential Data Issues with FAST Automation Reports v4.0: • FAST Vehicle Type Field (all) • “BLANK” results • Unreported vehicles solution • Invalid vehicle solution • “ ” results • FAST Fuel Type Field (all) • “BLANK” results • “XXX” results • “ ” results • FAST EISA Field (sec I – actual acquisitions only) • “BLANK” results • “XXX” results • “ ” results • Emergency Response Field (all) • “BLANK” results • Problematic Data • Missing costs (sec II & III) • Missing fuel (sec III) • Negative miles (sec II) Prepared for F.A.S.T. Automation Reports v4.0

  3. FAST Vehicle Type Field • “BLANK” results are the result of a vehicle not having been assigned a FAST Type in the “Status” area of FA. (See instructions on slide 7) • “BLANK” results may appear for the same reason on vehicles that are part of a maintenance class that should not be FAST reportable (ex.: a trailer or generator, etc). If this is the case, make note of the class type and any other identifying information. We will refine the class exclusion list at the next CMT Meeting (skip to step 6 on slide 7). • “ ” Results in this field that are left blank but not displayed as “BLANK” are anomalies and need to be investigated further. Please contact Robert High at r.high@stanleyassociates.com to report this bug. Prepared for F.A.S.T. Automation Reports v4.0

  4. FAST EISA Field • “BLANK” results are the result of a vehicle having no assigned value for the FAST type or GHG score fields used to calculate EISA compliance. Correct this in “Status” area of the “Fleet Equipment” screen in FA by running the “FAST Reports (Vehicle Mapping)” for the correct FAST value or selecting a GHG score (n/a,0-10) for the desired vehicle type found here: http://www.epa.gov/greenvehicles/Download.do • “XXX” results are the result of a vehicle having no reported delivery date entered into the database. Correct this in “Acquisitions” area of the “Fleet Equipment” screen in FA. • “ ” Results in this field that are left blank but not displayed as “BLANK” are anomalies and need to be investigated further. Please contact Robert High at r.high@stanleyassociates.com to report this bug. Prepared for F.A.S.T. Automation Reports v4.0

  5. FAST Law Enforcement Field • Accepted results for this field include “Y” or “ ” any other value are anomalies and need to be investigated further. Please contact Robert High at r.high@stanleyassociates.com Prepared for F.A.S.T. Automation Reports v4.0

  6. Problematic Data • The automation reports are a reflection of your ability to report and provide correct data from FA. Please strive to maintain complete and accurate data for all work order and labor costs, fuel consumption/costs, and mileage numbers for the fleet. Failure to do so can results in errors that will prevent you from uploading your files to the FAST interface as well as incorrectly reporting valuable information to HQMC and the United States Congress. • Please contact Daniel Robinson, 703-695-7010/6965, daniel.robinson2.ctr@usmc.mil and Robert High at r.high@stanleyassociates.com regarding: • Missing costs (sec II & III) • Missing fuel (sec III) • Negative miles (sec II) Prepared for F.A.S.T. Automation Reports v4.0

  7. FAST Vehicle Type Field • Run the FAST Reports (Section 1) – Inventory Report (slide 9) • Once the report is generated, click on any field in the record in question for details (slide 10) • Print out or make note of the equipment number • Go to “Fleet Equipment” (under FA Portal || Equipment Units) and update the vehicle record in question by entering the equipment number in the filter area and clicking the Get Data button (slide 11). • Once the record is displayed you may enter the FAST vehicle type in the Status area by clicking the drop down box next to the “FAST Type” label (image 1/slide 12) • Re Run the report and see if the issue has been resolved? • Once all known issues are correctly resolved for reportable items, the user may manually remove lines concerning issues that occur for non-reportable classes or vehicles once the data import has been created in Excel format (after step 13/slide 13 of Instructions Brief). • 8. If the issue was not resolved or an anomaly has been discovered in the data, please report it as previously mentioned (slides 3 through 6). Prepared for F.A.S.T. Automation Reports v4.0

  8. FAST Fuel Type Field • Run the FAST Reports (Section 1) – Inventory Report (slide 9) • Once the report is generated, click on any field in the record in question for details (slide 10) • Print out or make note of the equipment number and fuel fields (“fuel_type” and “fuel_type_2”) (slide 13). • Go to “Fleet Equipment” (under FA Portal || Equipment Units) and update the vehicle record in question by entering the equipment number in the filter area and clicking the Get Data button (slide 11). • Once the record is displayed you may enter/change the fuel type value(s) in the “Codes” area (image 2/slide 12). • Re Run the report and see if the issue has been resolved? • Once all known issues are correctly resolved for reportable items, the user may manually remove lines concerning issues that occur for non-reportable classes or vehicles once the data import has been created in Excel format (after step 13/slide 13 of Instructions Brief). • 8. If the issue was not resolved or an anomaly has been discovered in the data, please report it as previously mentioned (slides 3 through 6). Prepared for F.A.S.T. Automation Reports v4.0

  9. Data Validation Report Flags • Run the FAST Data Validation Report from the government FAST website. • Flags that appear as a result of discrepancies between vehicle inventory, please insert a comment similar to the following: “Reflects actual inventory numbers for this vehicle type.” Then select the box to show that the flag has been reviewed/justified. • Flags that appear as a result of discrepancies between actual acquisitions vs. planned acquisitions for a given year, please insert a comment similar to the following: “Reflects actual acquisitions approved by HQMC for this vehicle type versus suggested inventory replacement values.” Then select the box to show that the flag has been reviewed/justified. • All other flags will need comments before submitting the FAST report. • Be prepared to discuss any FAST reportable items, especially flagged items, with HQMC once your report has been reviewed.. • Remember, a flagged item does not mean that the data is wrong but that in many cases it requires additional info. Flags will appear for mostly all sites as our data collection methods get increasingly more accurate. • Questions on the Data Validation report should be directed to Daniel Robinson at 703-695-7010/6965, daniel.robinson2.ctr@usmc.mil Prepared for F.A.S.T. Automation Reports v4.0

  10. ‘USMC Custom Reports’ || ‘FAST Reports’ reports view Image 1. Prepared for F.A.S.T. Automation Reports v4.0

  11. Record Drill Down for more information • Once the report loads, sites may review and print the data prior to exporting the report. If there is data that needs to be examined further, clicking on any of the data in a row will open up a drill down version of that group with more detailed information. WARNING: The FAST interface will not accept the format of the drill down report. Only the summary report form (Image 3) view can be uploaded. The drill down is merely for resolving any data issues in which additional information is needed. Prepared for F.A.S.T. Automation Reports v4.0

  12. “FAST Type” Field in “Status” area of FA • Select “Fleet Equipment” under “FA Portal..” (image Left) • Click Filter icon and specify equipment in the “Equipment ID” field. • Click “Get Data” to populate the FA fleet equipment window. Prepared for F.A.S.T. Automation Reports v4.0

  13. Data update areas • Scroll down to “Status” area; assign the FAST Vehicle Type by clicking the drop down box next to “FAST Type” (image 1) • Scroll down to “Codes” area; assign fuel type(s) in the “Supported fuel/fluids types” area (image 2) • Scroll down to the “Assignments” area; designate/modify if the vehicle is Emergency Response by clicking the drop down box next to “Emergency Vehicle?” and choosing “Yes” or “No” (image 3) Image 1 Image 2 Image 3 Prepared for F.A.S.T. Automation Reports v4.0

  14. Record Drill Down for more information • In the Drill Down View of the report, make note of the equipment number field (left) and FA fuel types (fuel_type and fuel_type_2 left to right). WARNING: The FAST interface will not accept the format of the drill down report. Only the summary report form (Image Left/ Slide 10) view can be uploaded. The drill down is merely for resolving any data issues in which additional information is needed. Prepared for F.A.S.T. Automation Reports v4.0

More Related