EARNED RECOGNITION IT SYSTEM REQUIREMENTS
Earned RecognitionRequirements DocumentDVSA/ERSR/1EARNED RECOGNITION IT SYSTEM REQUIREMENTSPage 1 of 26
Requirements -03-1704-05-1711-05-1702-08-17Author15-12-17Philip LapczukAndy FordAndy FordAndy Ford / Dave WoodAndy FordAndy FordAndy Ford / Dave Wood / Howard ForresterAndy FordDave WoodAndy FordAF, DW, Phil L, Howard FAndy FordAndy FordAndy Ford / Dave WoodAndy Ford / Dave WoodSJ. DW PL HFReferenceDraft1.af.V1 0Draft1.af.V2 0Draft1.af.V3 0Draft1.af.V4 0Draft1.af.V5 0Draft1.af.V6 0Draft1.af.V7 0Draft1.af.V7 0DWDraft1.af.V8 0Draft1.af.V9 0Wolves12.12.16Draft1.af.V10 0Draft1.af.V11 0Draft1.af.V12 0Final.V1 0Final.V1-1Steve JoyceSteve JoyceSteve JoyceSteve Joyce/Howard Forrester/Phil LapczukSteve JoycePhilip Lapczuk / Howard ForresterExternal Providers RequirementsDrivers Hours dashboard updatedUpdate from System ProvidersKPIs updatedVersion 1-5 Clarification & errorrectification as detailed belowKPI updates, text updates detailedbelowUpdates in this releasePage 3Explanation for appendix 6 & 7Page 9Amendment to ‘wipe the slate clean’ for M5Page 9Additional requirements for D7, D8 & D9Page 9Added text in paragraph 12 for amended drivers hours dataPage 9Additional requirements for M5Page 13Updated chart reflecting changes for D7, D8 & D9Page 13Updated chart reflecting changes for M5Page 15Updated text reflecting changes for ‘repeat offenders’, ‘unaccounted mileage’ & ‘MSI’Page 16Updated text for ‘Safety Inspections are within the stated frequency’Page 25Updated dashboard template for reporting drivers hours triggersPage 26Updated dashboard template for reporting maintenance triggersPage 2 of 26
Earned RecognitionRequirements DocumentTerms of Reference (ToR) / Background informationDVSA Business Plan deliverable We’ll make sure that vehicles on our roads are safe, and drivers and Operators are doing what theyshould by moving to more targeted enforcement checks on the seriously and serially non-compliantWe’ll minimise disruption to the most compliant, offering operators the opportunity to demonstratetheir level of compliance through an earned recognition scheme.Therefore, we shall develop the operator earned recognition scheme further to enableimplementation following the pilot.DVSA Earned Recognition is a scheme which aims to reduce the burden of enforcement on Operators witha strong track record of compliance and adherence to standards.Operators will ‘earn recognition’ by maintaining audited compliance systems, and meet high levels ofcompliance standards.This may prevent the need to pull them in at the roadside or carry out other means of frontlineinterventions and frees up DVSA resource to concentrate on targeting the seriously and serially noncompliant operators. This will be achieved by introducing KPIs, monitoring performance and periodicsystems auditsDVSA will validate an operator’s electronic systems to ensure the data is recording correctly and providedto DVSA in the correct format.An operator could attempt to manipulate their data but this would risk fraud prosecutions and potentialloss of operator licence. The DVSA will make random spot checks of data and the systems audit will alsocheck that the operator’s systems are correctly capturing all the required driver and vehicle data.High Level Requirements – for the SchemePlease note these requirements relate to the scheme.1. Ability to monitor via electronic triggers from Operators systems (see High Level System Design,pg5)2. Ability to send an e-mail, with no attachment, on the required day of each reporting period if noKPIs have been triggered3. Ability to supply agreed KPI data, should any triggers occur, via a reporting dashboard (SeeAppendix 6 & 7)* as a pdf attachment to an e-mail on the required day of the relevant reportingperiod.*Appendix 6 & 7 has been updated. Where systems have been ‘accepted in principle’ you may continueto use your existing reporting dashboard until ‘system validation’ providing it follows the format detailedin previous versions of this document.Page 3 of 26
Earned RecognitionGlossary of termsTermANPRBAUBF (date)CLODDRDVSAE.R.ECMSEUEx.REx.R PDFFBCFCCIn Scope VehiclesISO weekKPIKPI periodMCMSIOCRSOIPROTCRAGREOS.PsSafety RepTachograph VU / TachoVehicle AssetsVOLVORWIMSRequirements DocumentDefinitionAutomatic Number Plate RecognitionBusiness As UsualBrought ForwardCentral Licensing OfficeDriver Defect ReportDriver and Vehicles Standards AgencyEarned RecognitionElectronic Case Management SystemEuropean UnionException ReportException Report PDFFull Business CaseFleet Compliance CheckIn scope for operator licensing requirementsThe ISO week date system is effectively aleap week calendar system that is part ofthe ISO 8601 date and time standardissued by the International Organization forStandardization. It has 52 or 53 full weeks.That is 364 or 371 days instead of the usual365 or 366 days.Key Performance IndicatorA period of 4 weeks used to measure thedata for the key performance indicatorsMobile ComplianceMost Serious InfringementOperator Compliance Risk ScoreOperator Information & Performance ReportOffice of the Traffic CommissionerRed, Amber, GreenRemote Enforcement OfficeSystem Providers (providing the KPImonitoring information into the DVSA)Safety Inspection ReportVehicle UnitUp to date fleet list of ‘in scope’ vehiclesand trailers (incl’ hired) the operator (legalentity) is responsible forVehicle Operator LicensingVehicle off the roadWeigh in Motion SensorPage 4 of 26
Earned RecognitionRequirements DocumentHigh level system designOPERATOROPERATOR rnedRecognitionMaintenanceSystemsOPERATOR /SYSTEMPROVIDERKPItriggersPage 5 of 26
Earned RecognitionRequirements DocumentEarned Recognition – Application ProcessOperatorDVSA Earned Recognition – Application ProcessOperator supplies 3periods KPI data withapplicationOperator confirms Auditcontract to DVSAEarned Recognition ApplicationYesApplication Review(14 calendar day SLA)DVSAApplication successful?NoSystem ProviderDVSA inform Operator thatapplication is unsuccessfulProvide KPI data in PDFformatPage 6 of 26
Earned RecognitionRequirements DocumentEarned Recognition Scheme – Scheme OperationDVSA Earned Recognition Scheme – Scheme OperationOperatorOutputs from monitoring systemsSystem Provider/OperatorEvery 4ISOweeksKPI AnalysisEndKPI TriggerYesSend KPI ExceptionReport to DVSANoDVSAE-mail with no attachmentreceivedImprovement action planagreed with operatorPage 7 of 26
Earned RecognitionRequirements DocumentScheme Rules1.Each operator will have a specific individual ID number in the following format 0000-0000.There will be further identifiers used on all returns; these will identify the operator, the periodbeing reported and will be applicable to both maintenance and drivers hours. Examples of therequired format are shown below and must form the subject line of the e mail returns.[maintenance or driver hours identifier nil or kpi trigger] unique operator id, reporting period andyear:a.b.c.d.[MTnil]0000-0000 p01y2017[MTkpi]0000-0000 p01y2017[DHnil]0000-0000 p01y2017[DHkpi]0000-0000 p01y2017i.e. no maintenance KPI trigger, no attachmenti.e. maintenance KPI trigger, attachment expectedi.e. no drivers hours KPI trigger, no attachmenti.e. drivers hours KPI trigger, attachment expected2. Systems need to be validated by DVSA, and system providers will be issued a unique id number fortheir validated system.3. For each KPI reporting period DVSA must be sent two e-mails (to: er@dvsa.gsi.gov.uk): one relatingto Drivers Hours, the other to Safety Inspections/Maintenance Activities. If no KPIs have beentriggered no attachment should be included with the e-mail, if there are any KPI triggers a pdf ofthe DVSA Dashboard should be attached to the e-mail. There must be no other attachmentsincluded on the email.4. Reporting period(s)i.4 ISO weekly reporting periodii.The operator’s chosen system (which must be validated by DVSA) will report on thelast complete 4 week KPI periodiii.KPI reporting emails must be sent to DVSA on the first Monday of each reportingperiod.iv.13 rolling KPI periods for monitoring the KPIs i.e. Jan to Jan (N.B: on joining the E.Rscheme the previous 12-week period will be provided prior to being accepted ontothe scheme)v.Reported data will be four weeks in arrears e.g. data for period 1 will be reported inperiod 3. Refer to KPI ISO Weeks Reporting Schedule 2017-2018 document for thereporting dates.vi.Operators will join the scheme at the beginning of the next reporting period.There will be a DVSA administrative process to allow the KPI thresholds, or reporting periods, to bereviewed/amended, if required5. Safety inspections must be carried out, as a minimum, according to the latest version of Guide toMaintaining Roadworthiness6. Any vehicle declared “Vehicle off road” (VOR) must be suppressed from the reporting period.7. Drivers Hours and Vehicle Maintenance/Safety Inspections will be reported every 4 week period, ona 13 period basis. KPIs and triggers for Driver Activities are measured independently from those forVehicle Maintenance/Safety InspectionsPage 8 of 26
Earned RecognitionRequirements Document8. Following a KPI trigger the system should “wipe the slate clean” for all previous reporting periodsfor M1, M2, M3 and M4 maintenance requirements , and for D1 to D6 for drivers hours.9. D7, D8 and D9 will not independently trigger, however following any triggers for D1 to D6 thedetails of D7 and D9 will be included in the KPI email attachment10. The requirements for D7, D8 and D9 will be included in an ‘Operator Performance’ report which willbe available from the operator for audit purposes.11. All records relating to Drivers Hours and Vehicle Maintenance must be included in the report. Theremust be no records removed by the system provider12. An operator may be given the opportunity to amend tachograph data following analysis only whenthis relates to genuine errors recorded by the driver and only in the following circumstances: a. If a driver card is left in a tachograph instrument and records ‘other work’ if the driver istaking their daily or weekly restb. If an error is made when a driver completes a manual entryAmendments must be recorded including the date, who made the changes and the reasons why.Amendments made under the above mentioned circumstances will be removed from the incorrectfixed penalty band and recorded under fixed penalty band 1.No other amendments will be allowed.A report identifying the amendments must be available for audit purposes.13. When an application is made by an operator to join the scheme the system supplier will record theprevious thirteen period history for M5 measured as a percentage. This percentage will be updatedwhen the operator is accepted onto the scheme and will be used as the starting figure for M5. Oneach subsequent anniversary a report will be produced indicating the current percentage for M5based on the previous 13 period’s data. This will be included on the appropriate email attachmentand reported to DVSA only if the result is below 95%.14. M5 will not independently trigger however following any triggers for M1, M2, M3 or M4 the detailsfor M5 will be included in the KPI email attachment.15. KPI triggers must be identified by code – see Appendix 116. There will be a DVSA administrative process to allow the KPI thresholds, or reporting periods, to bereviewed/amended if requiredPage 9 of 26
Earned RecognitionRequirements DocumentHigh Level Summary of RequirementsFunctional Requirements – Drivers HoursIDDescriptionAcceptanceEXCEPTION REPORTINGERF1Rolling year of 13 periods which arethemselves 4 weeks in duration (ISOweek)E-mail received on first Monday of eachreporting period with no attachment if there are no KPItriggersIf any KPI is triggered in the reportingperiod a DVSA dashboard detailing theKPI trigger will be attached to the emailSee Scheme Rule 4Driver ActivitiesERF2DVSA to receive email from system toindicate no trigger of drivers hours KPIs.E-mail received on first Monday of eachreporting period with no attachment.ERF3DVSA to receive email from systemdetailing any trigger of drivers hoursKPIsE-mail received on first Monday of eachreporting period with a DVSA dashboarddetailing the trigger/s. This should include anyMSI triggers, or repeat offenders.Unaccounted MileageERF4Ensure mileage information on theTachograph VU matches that of theDrivers Card. DVSA notified of anyunaccounted mileage.Included on Operators performance reportonlyReporting RequirementsERF6Returns will be automatically sent toDVSAE-mail received on first Monday of eachreporting periodERF7DVSA will be alerted of any nil returnfrom an operator.E-mail notification to be received on the firstMonday of each reporting period if anyinstance of nil return occursPage 10 of 26
Earned RecognitionRequirements DocumentFunctional Requirements – Vehicle Maintenance/Safety InspectionsIDDescriptionAcceptanceEXCEPTION REPORTINGERF9Rolling year of 13 periods which arethemselves 4 weeks in duration (ISOweek)E-mail received on first Monday of eachreporting period with no attachment if there are no KPItriggers.If any KPI is triggered in thereporting period a DVSAdashboard detailing the KPItrigger will be attached to thee-mailVehicle Maintenance/SafetyInspectionsERF10DVSA to receive email from system toindicate no KPI triggers of vehiclemaintenance/safety inspection KPIs.E-mail received on first Monday of eachreporting period with no attachment.ERF11DVSA to receive email from systemdetailing any trigger of vehiclemaintenance/safety inspection KPIsE-mail received on first Monday of eachreporting period with a DVSA dashboarddetailing the KPI trigger/sReporting RequirementsERF12Returns will be automatically sent toDVSAE-mail received on first Monday of eachreporting periodERF13DVSA will be alerted of any nil returnfrom an operator.E-mail notification to be received on thefirst Monday of each reporting period ifany instance of nil return occursPage 11 of 26
Earned RecognitionRequirements DocumentThe following references detail the criteria for the KPI1.) Offences split into four bands refer to the legislation document (Section 96 (11) transport act 1968table 1 & 2 and the Road Safety (financial penalty deposit) (appropriate amount) order 20092.) WTD – these are detailed in the Road Transport (Working Time) Regulations 20053.) The DVSA “Guide to Maintaining Roadworthiness" can be downloaded from the following ide-to-maintaining-roadworthinessPage 12 of 26
Earned RecognitionRequirements DocumentAppendix 1CodeDrivers Hours Requirements(Based on tachograph days)KeyPerformanceIndicatorTrigger1 2% Trigger21% 2%Trigger3 1%D1Fixed Penalty band 11.30%3.30%2.30%1.31%D2Fixed Penalty band 21.20%3.20%2.20%1.21%D3Fixed Penalty band 30.80%2.80%1.80%0.81%D4Fixed Penalty band 40.70%2.70%1.70%0.71%D5Overall Infringements4%6%5%4.10%D6Working Time4%6%5%4.10%Operator Performance ReportNotes - Where an operator reports less than25 tachograph days in a KPI period the KPIwill be set at no more than 1 offence in thereporting periodD7, D8 & D9 will not trigger independentlyD7Repeat Offenders *0111See KPI explanation listD8Unaccounted Mileage **0111See KPI explanation listD9Most Serious Infringements *0111See appendix 2* included in Operator Performance report and additionally in KPI report following a trigger for D1, D2, D3, D4, D5 or D6** included in Operator Performance report only (available for audit purposes)CodeM1M2M3M4Maintenance RequirementsComplete set of safety inspectionrecordsSafety inspection records arecompleted correctly including allrelevant sections and signed off asbeing roadworthySafety inspections are within thestated frequencyDriver defect reports where roadsafety related items have beenreported are appropriately actionedReported on acceptance to the schemeand each subsequent anniversaryM5KeyPerformanceIndicatorTrigger1 2% Trigger21% 2%Trigger3 100%98%99%99.99%Notes - For fleets less than 20 vehiclesincluding trailers the KPI will be set at nomore than 1 breach in the reporting periodVOR reports will be validated against drivershours records during the periodic auditVOR reports will be validated against drivershours records during the periodic auditM5 will not trigger independentlyVehicle & trailer MOT initial passrates*Where the fleet size is 20 or less the KPI is no95%93%94% 94.99% more than one failure in 13 rolling periods*will be reported to DVSA yearly on the anniversary of acceptance to the scheme, additionally will be included in KPI report following atrigger for M1, M2, M3 or M4Page 13 of 26
Earned RecognitionRequirements DocumentAppendix 1 (cont.)Examples of trigger calculations based on the information above2% or over Over three rolling periods Over thirteen Rolling Periodsor or Any combination for example or Page 14 of 26
Earned RecognitionRequirements DocumentKPI explanations for drivershoursDrivers HoursTachograph dayFixed penalty bandsWorking timeRepeat offendersUnaccounted mileageMost serious infringementsAny day from 00:00 to 23:59 where duty has beenrecorded. Where continuous duty extends over23:59 this will be recorded as two daysReference to section 96(11) Transport Act 1968table 1 & 2 and the Road Safety (Financial PenaltyDeposit) (Appropriate Amount) order 2009Systems should identify where agreements are inplace for night time workers and reportaccordingly. The validity of any agreements will bechecked during the periodic audit.Where a driver has any infringement 3 times inthree rolling reporting periods. The action takenwill be checked during the periodic auditIf an operator can satisfactorily account for anymissing mileage this should be validated throughthe system. The missing mileage may be groupedor reported individually depending on thepreference of the operator. For example theoperator may be satisfied that any distance lessthan 5km that can be explained by driving onprivate land may choose to group that mileage.This validation will be checked during the periodicaudit.These are included in appendix 2 and are subjectto review from time to time. Any amendments willbe notifiedPage 15 of 26
Earned RecognitionRequirements DocumentKPI explanations formaintenanceMaintenanceComplete set of safetyinspection recordsSafety Inspection recordsare completed correctlyincluding all relevantsections and signed off asbeing roadworthySafety Inspections arewithin the stated frequencyDriver defect reports whereroad safety related itemshave been reported areappropriately actionedAll planned vehicles due an inspection within the 4 week period havean inspection job within that periodSafety inspection records should be appropriate to the vehicle andshould include all the requirements stated in the Guide toMaintaining Roadworthiness. These sections should be marked as perthe Guide to Maintaining Roadworthiness, removal of these sectionsby the operator must not be allowed. Any additional requirementsthe operator wishes to add to the records should not count towardsthis requirement. The document must contain two signatures one forthe person carrying out the work and the second of the personverifying the vehicle or trailer is in a roadworthy condition, the twosignatures could be the same.This is dictated by the requirements of the operator’s licence and it isthat period that should be measured. For example if the operator’slicence states 8 weekly inspections but the operator decides to carrythese out at 6 weekly intervals the KPI will only be breached if there ismore than 8 weeks between any inspection. The safety inspection canoccur at any point before or during the ISO week when it is due. Thesystem should either dynamically re-calculate the subsequentinspection periods or notify the operator that an additional inspectionis due if they wish to keep their planned checks.The system needs to identify that a driver defect report has beenactioned, this may be a declaration from the operator. It is up to theoperator to decide what is safety related and what is the mostappropriate action, this will be checked during the periodic auditVehicle & trailer MOT initialpass ratesThe system needs to identify whether the MOT is pass, PRS or fail.This is only applicable for the initial test, retests should not beincluded in the figuresVehicle off the road (VOR)If a vehicle is off the road when an inspection is due the data shouldbe suppressed to prevent a failed kpi, but the system shouldrecognise that because the frequency has been exceeded aninspection must be carried out prior to the vehicle re-entering service.Page 16 of 26
Earned RecognitionRequirements DocumentAppendix 2 – Most Serious Infringement (MSI) details:PDF 2 – Drivers Hours & Tachograph Most Serious Infringements:Page 17 of 26
Earned RecognitionRequirements DocumentAppendix 3 – Examples showing where drivers’ hours KPIs are not met:KPIs that are exceeded, but not sufficiently to trigger an alert to the scheme manager are highlighted in yellow and amber.KPIs that trigger an alert to the scheme manager are highlighted in red.Example 1In period 1 the operator will be aware that they have a yellow alert for exceeding a KPI, during period 2 no KPIs are exceeded. In period 3 and period 4 the operatorreceives two further yellow alerts indicating KPIs have been exceeded by less than one percentage point, DVSA will not be alerted because the three yellow alerts arenot in consecutive rolling periods. However, in period 5 the operator receives a red alert indicating DVSA have now been made aware of the exceeded KPIs for thefollowing reason:In measurement period 5 - the KPIs have been exceeded three times in three rolling measurement periodsBandKPI %Period 1Period 2Period 3Period 4Period 5Band 11.300.751.200.801.601.05Band 21.200.351.001.601.050.90Band 30.800.780.790.500.500.75Band 703.85W / time4.003.803.703.903.953.85Page 18 of 26
Earned RecognitionRequirements DocumentExample 2In period 3, 4, 7 & 9 the operator will be aware that they have an yellow alert for exceeding a KPI, during periods 1, 2, 5, 6, 8, 10 no KPIs are exceeded. All of theseyellow alerts indicate KPIs have been exceeded by less than one percentage point but because alerts are not in consecutive rolling periods DVSA will not be alerted.However, in period 11 the operator receives a red alert indicating DVSA have now been made aware of the exceeded KPIs for the following reason:In measurement period 11 – The KPIs have been exceeded five or more times in thirteen rolling measurement periods.BandKPI %Period 1Period 2Period 3Period 4Period 5Period 6Period 7Period 8Period 9Period10Period11Band and and and 3.25W/ 70Page 19 of 26
Earned RecognitionRequirements DocumentExample 3In period 1 the operator will be aware that they have both yellow and amber alerts for exceeding KPIs. These alerts indicate KPIs have been exceeded, the ‘overallfigure’ by less than one percentage point and the ‘working time’ by more than one percentage point but less than two percentage points. As the operator is allowedto exceed the KPIs three times by less than one percentage point and two times by more than one percentage point but less than two percentage points, in threerolling measurement periods, DVSA will not be alerted. However, in period 1 & 2 the operator receives a trigger indicating DVSA have now been made aware of theexceeded KPIs for the following reasons:In measurement period 1 – The KPI for band 4 has been exceeded by more than two percentage pointsIn measurement period 2 – The KPI for working time has been exceeded by more than one percentage point but less than two percentage points. The previoustriggers will not count towards the five or more times in thirteen rolling measurement periods because a red alert was triggered period 1BandKPI %Period 1Period 2Band 11.300.100.15Band 21.201.101.00Band 30.800.100.15Band 40.702.902.40Overall4.004.203.70W / time4.005.505.45Page 20 of 26
Earned RecognitionRequirements DocumentAppendix 4 – Examples showing where maintenance KPI’s are not met:KPIs not met, but not sufficiently to trigger an alert to the scheme manager are highlighted in yellow and amber.KPIs that trigger an alert to the scheme manager are highlighted in red.Please noteWithin the tables shortened titles, have been used but appear in the same order as the list below, Complete set of safety inspection recordsSafety Inspection sheets are completed correctly including all relevant sections and signed off as being roadworthySafety Inspections are within the stated frequencyDriver defect reports where road safety related items have been reported are appropriately actionedVehicle & trailer MOT initial pass ratesPage 21 of 26
Earned RecognitionRequirements DocumentExample 1In period 2 the operator will be aware that they have a yellow alert for failing to meet a KPI, during periods 1 & 3 all KPIs were met. In period 4 and period 5 theoperator receives two further yellow alerts indicating KPIs have not been met by less than one percentage point. DVSA will not be alerted because the three yellowalerts are not in consecutive rolling periods. However, in period 6 the operator receives a red alert indicating DVSA have now been made aware of the failure to meetKPIs for the following reason:In measurement period 6 - the KPIs have not been met three times in three rolling measurement periodsMeasureKPI %Period 1Period 2Period 3Period 4Period 5Period 6Complete d & y100100.0099.25100.00100.00100.00100.00Driver 5096.0095.5097.5097.2597.50MOTPage 22 of 26
Earned RecognitionRequirements DocumentExample 2In period 2, 4, 5 & 8 the operator will be aware that they have an yellow or amber alert for not meeting a KPI, during period 1, 3, 6, 7 & 9 all KPIs have been met. All ofthese alerts indicate KPIs have not been met because the operator is allowed to fail to meet the KPIs three times by less than one percentage point and two times bybetween one percentage point and two percentage points in three rolling measurement periods DVSA will not be alerted. However, in period 10 the operatorreceives a red alert indicating DVSA have now been made aware of failure to meet KPIs for the following reason:In measurement period 10 – The KPIs have not been met five or more times in thirteen rolling measurement periods.MeasureCompletesetKPI %Period 1Period 2Period 3Period 4Period 5Period 6Period 7Period 8Period 9Period10Period 095.5094.2595.50100Completed& signed100Frequency100Driverdefect100MOT95Page 23 of 26
Earned RecognitionRequirements DocumentExample 3In period 1 the operator receives a red alert indicating DVSA have now been made aware of the failure to meet KPIs for the following reason:In measurement period 1 – The KPI for complete set of safety inspection records has not been met by more than two percentage pointsMeasureKPI %Period 1Complete set100Completed & signed100Frequency100Driver defect100MOT95Period .5097.00Page 24 of 26
Earned RecognitionRequirements DocumentAppendix 6 – DVSA Drivers Hours DashboardOperator ID0000-0000System Provider IDZZ0000DateProducedReporting Period (00)CodeYear (0000)DescriptionD1Band 1D2Band 2D3Band 3D4Band 4D5OverallD6Working timeRecord D7 & D9 using numericvaluesOnly report D7 & D9 following any D1 to D6 triggerD7D9Repeat offendersMost seriousinfringementsPage 25 of 26
Earned RecognitionRequirements DocumentAppendix 7 – DVSA Maintenance/Safety Records DashboardOperator ID0000-0000System Provider IDZZ0000DateProducedReporting Period (00)CodeYear (0000)DescriptionM1Full SetM2CompletedM3FrequencyM4Driver defectsRecord M5 as a percentageOnly report M5 following any M1 to M4 triggerM5MOTPage 26 of 26
[maintenance or driver hours identifier nil or kpi trigger] unique operator id, reporting period and year: a. [MTnil]0000-0000 p01y2017. i.e. no maintenance KPI trigger, no attachment. b. [MTkpi]0000 -0000 p01y2017 . i.e. maintenance KPI trigger, attachment expected. c. [DHnil]0000 -0000 p01y2017. i.e. no drivers hours KPI trigger, no .
The Ultimate Guide to Employee Rewards & Recognition v1.0. Table of contents INTRODUCTION 3 EVOLVING ROLE OF HR 5 REWARDS VS RECOGNITION 8 BENEFITS OF REWARDS AND RECOGNITION 10 TECHNOLOGY IN REWARDS AND RECOGNITION 15 A CULTURE OF PEER TO PEER RECOGNITION 26 SELECTING A REWARDS AND RECOGNITION PLATFORM 30
18-794 Pattern Recognition Theory! Speech recognition! Optical character recognition (OCR)! Fingerprint recognition! Face recognition! Automatic target recognition! Biomedical image analysis Objective: To provide the background and techniques needed for pattern classification For advanced UG and starting graduate students Example Applications:
Earned Value Exercise 6 3 B C Earned 4 B C Earned 5 B C Earned 6 B C 7 B C 8 B C Earn Value Analysis: The table below shows on day 8th, with the baseline schedule following the Network Diagram above (Appendix E), the Cost Variance is -900, Schedule Variance is -700, CPI is 0.36 and SPI is 0.42.
The method and its variations have been used under several names, such as earned value project management, earned value method, earned value analysis, and cost/schedule summary report (Fleming & Koppelman, 2003, 2010; Kim, 2000; Kim et al., 2003). 4.2 Earned Value Management Best Practicesxiv
Annex A (informative) Cost and performance measurement analysis using earned value management data Annex B (informative) Schedule Analysis using earned value management data (Earned Schedule) Annex C (informative) Integrating other project management processes with earned value management Annex D (informative) Bibliography EV Management
What is Earned Schedule? A New Metric Lipke devised a new metric to combat SV and SPI limitations and created Earned Schedule - A measure of work completed in a designated increment of time Added Value without extra data collection Additional calculation based on data collected for ANSIAdditional calculation based on data collected for ANSI-748 Compliant Earned Value748 .
earned value analysis. The goal for implementing the earned value and earned schedule methods on an actual construction project is to determine the validity of those methods to the industry. In order to gather the cost and schedule data in a more organized manner a database is created through various scheduling and spreadsheet based systems.
In the Earned Value Analysis node (Earned Value Manager Earned Value Analysis), perform earned value analysis corresponding to an activity sheet. 1. Activity sheet data (WBS, CBS, and all projects) is consolidated, rolled up, and displayed in summary tables in an EV scenario. 2.
