Autopass Beskrivelse av forundersøkelse for IST langtidstesting

Transkript

1 Statens vegvesen Vegdirektoratet langtidstesting Versjon 0,4 Autopass Beskrivelse av forundersøkelse for langtidstesting Referansedokument 4.1 AutoPASS specification Charging point equipment s for automatic charging points, version AutoPASS specification Charging point equipment Test strategy, version 2 Angrepsmåte og praktisk utførelse -testingen legges opp med gjennomføring i to faser: Forundersøkelse skal gi overordnet status om kvaliteten og skal gi indikasjoner på forhold som må undersøkes nærmere. Spesialtester videre testing og undersøkelser på forhold indikert i forundersøkelsen. Testmetoder vil avhenge av tema og vil følge testmetodene angitt i kravspesifikasjoner og kontrakter. -testingen skal først og fremst handle om kvalitetsmåling av vegkantutstyret (CPE). en for å få fram indikasjoner på feil og kvalitetsavvik vil forundersøkelsen dekke flere tema og berøre flere kontraktsområder. Oppfølging av forhold som berører andre avtaler enn utstyrleveranser må plasseres hos riktig avtaleparter (CS, vedlikehold, driftstjenester). Forundersøkelsens plass i hele -testingen vil være: Kravtabell og testprosedyre for Forundersøkelse Analyse Rapport forundersøkelse Undersøkelser og spesialtester Analyse av enkelttester Samlet rapportering Oversikt over aktiviteter og hvem som er ansvarlig for å gjennomføre disse for en langtidstest, hvor tidsfrister utfylles for hver enkelt -test: Aktiviteter Ansvarlig Tidsfrist Organisering av testing. Vegdirektoratet skal holdes informert. SVV region Avklare finansiering for gjennomføring av langtidstest SVV region med bompengeselskap

2 Kartleggingsrapport for anlegget, som inneholder eventuelle spesielle forhold/problemer for det gjeldende anlegget Bestilling av langtidstest hos vegkantleverandør, inkludert definisjon av testprosedyre Bestilling av forundersøkelse hos driftsselskap, inkludert definisjon av testprosedyre Innhenting av rådata fra vegkant ved behov Utarbeidelse av rapport, inkludert tilbakemeldinger fra SVV og utstyrsleverandør, på forundersøkelse fra driftsselskap. Rapport skal være levert før utstyrsleverandør setter i gang med forundersøkelsen. Definere forundersøkelse for utstyrsleverandøren. evering av rapport på forundersøkelse fra utstyrsleverandør, inkludert tilbakemeldinger. Rapporten skal inneholde oppfølgingspunkter. Avdekke nasjonale fellessaker for flere anlegg. Skal videreformidles til Vegdirektoratet for felles oppfølging overfor utstyrsleverandør. Funn/erfaring som gjelder CS, driftskontrakt, brikke skal videreformidles til VD for felles oppfølging overfor utstyrsleverandør. Forhold som har med endring spesifikasjon skal videreformidles til VD for oppfølging (i forbindelse med revisjonsarbeidet av kravspesifikasjonen) Oppfølging og gjennomføring av tiltak av punkter avdekket under -testingen Godkjenning SVV region SVV region SVV region Utstyrsleverandør Driftsselskap SVV region Utstyrsleverandør VD VD VD SVV region SVV region Forundersøkelsen Tabellen under gir en overordnet oversikt over den samlete forundersøkelsen oppdelt i tema. Nærmere instruksjoner for rapport fra driftsselskap og utstyrsleverandør er beskrevet under. Tema Datakilde Data Ressurs for utførelse, oppgaver Værdata Driftsselskap, SVV/VTS, Datoer, værhistorikk, Driftsselskap Statens vegvesen meteorolog, VegVær værtype, temperatur CS - Bildekvalitet CS OCR-statistikk Driftsselskap Slettekoder Bilder av ikke-bil Belastningsmåter: brikke, bilde/abonnement, bare bilde Easygo CPE - Bildekvalitet CPE OCR-resultater Utstyrsleverandør Transaksjoner CPE Statistikk over all Utstyrsleverandør

3 informasjon i transaksjonene. Signalkoder Flagg AC Bilder Avstemmingstellere Exceptions Easygo Statusfil CS Oppdatert statusfil, logg Driftsselskap CS-leverandør Brukere ogger hos driftsselskap ys Saldo Brikker som ikke virker Biltype, montering Driftsselskap Utstyrskvalitet Vedlikeholdsrutiner Vedlikeholdsrapporter Feilmeldinger, logger TBF TTR Oppetid Kritisk/ikke kritisk komponent Vedlikeholdsleverandør Driftsselskap Overvåking og feilmelding ogger hos driftsselskap Vedlikeholdstjeneste logger Feilmeldinger, logg CPE-saker CS-saker Driftsselskap Der det foreligger datagrunnlag i et stort omfang (bilder, slettekoder, transaksjoner, signalkoder, tellere, exceptions, feillogger) skal den statistiske bearbeidingen resultere i for hver type/enhet: Antall og andeler av forekomster for hver parameter Variasjonskurver over tid, med dagsoppløsning aksimumsverdi og minimumsverdi der det er relevant Gjennomsnittsverdier der det er relevant OCR-statistikken, både for CPE og CS skal gi: Parametrene som er angitt i kravtabellen (foran, bak, match, hele utvalget, lesbart utvalg, etc). Variasjonskurve for OCR-rate (nøkkeltall) Analysen i forundersøkelsen skal forklare hva som er utført, beskrive situasjonen om kvaliteten, forholdet til krav og avvik. Det skal konkluderes med hvilke spesialtester og

4 undersøkelser som må gjøres videre for å avdekke fakta over kvaliteten i bompengeanlegget. Konklusjoner skal oppsummeres i rapport med grunnlagsdata og statistikk i vedlegg. Instruksjon til rapport fra driftsselskap: Driftsselskapet leverer en rapport ut fra en forundersøkelse, og bør synliggjøre anleggsspesifikke problemer. En kartleggingsrapport utarbeidet før oppstart av -arbeidet kan være et utgangspunkt. Generelle punkter som skal rapporteres (i tillegg rapporteres det som er anleggsspesifikt eller som driftsselskapet ønsker å belyse): - Vedlikeholdsrutiner, overvåkning og feilmeldinger o Oversikt over avviks- og feilmeldinger. Oversikt sammenlignes med oversikt fra utstyrsleverandør/leverandør av service og vedlikehold. - Bildekvalitet o Antall bilder som slettes og sletteårsaker. Et representativt utvalg av bilder gjennomgås i forbindelse med sletteårsaker. o Årsakssammenheng mellom slettede bilder og værdata. o OCR-statistikk o Antall bildetransaksjoner av passeringer uten brikke (kode 22-passeringer) som knyttes til avtale. Ved stor andel av dette kan man videre Sjekke om brikke som knyttes til kjøretøyet leses i enkelte felt/stasjoner eller om det gis kode 22 på alle passeringer til kjøretøyet Hente ut brikkenummer på de brikkene som ikke leses for å sjekke om det er noen sammenheng med produksjonsserie og alder på brikkene. - Transaksjoner o Undersøke om det oppstår flere transaksjoner per passeringer, hvor samme bil er registrert samtidig i to ulike felt o Analyse av signalkodestatistikk o Antall passeringer av brikker som ikke er autentisert (kode 25). Oversikt over brikker som gir denne koden, for å se etter indikasjoner på om det er sammenheng mellom produksjonsserie og kode Oppdatering av statusliste - Brukere o ogging av kundehenvendelser, for å se om henvendelse indikerer feil på utstyr (for eksempel lyssignal, brikker som ikke virker, saldo, montering av brikke/biltype) - okale forhold/problemer Instruksjon til rapport fra utstyrsleverandør: Testingen tar utgangspunkt i kravspesifikasjon for vegkantutstyret, dokument 4.1 AutoPASS specification Charging point equipment s for automatic charging points, for kontrakter inngått etter mai For kontrakter inngått før dette tidspunktet vises det til kravspesifikasjonen for den enkelte kontrakt. everandøren skal selv beskrive testprosedyren, og den skal være basert på de aktuelle kravene for -testing i de enkelte kontraktene. En kravtabell, hvor disse kravene er opplistet, skal defineres for hver enkelt -test. For kontrakter hvor dokumentet 4.1 AutoPASS specification Charging point equipment s for automatic charging points inngår, vises det til vedlegg 1 for listen med aktuelle krav.

5 Vedlegg Vedlegg 1: langtidstesting krav til utstyrsleverandør, versjon 1

6 Vedlegg 1 langtidstesting krav til utstyrsleverandør Referansedokument 4.1 AutoPASS specification Charging point equipment s for automatic charging points, version 2.1 Krav - og - Kravene under er tatt fra dokument 4.1 AutoPASS specification Charging point equipment s for automatic charging points, og viser de kravene som utstyrsleverandøren skal inkludere i en long-term (-) og/eller maintenance (- ). For referanser til dokumenter, tabeller og figurer i kravene, se 4.1 AutoPASS specification Charging point equipment s for automatic charging points. CPE Overall System s [R 12] For each CP there shall daily for each lane be generated statistics registering percentage of all occurring Signal Codes to the total number of passages in the specific lane. Signal Codes are described in [6]. [R 19] The CP shall for each lane at the Charging Area have counters for reconciliation for detected vehicles. The reconciliation counters are transferred in the Transaction as described in [6]. CPE Capability s [R 20] The CP shall register the vehicle subjected to toll within the Charging Area, this includes vehicles driving between the lanes or on the hard shoulder. See figure 4. There shall be only one register for each vehicle passing the Charging Area. Objects not identified as a vehicle subjected to toll are for example; motorcycles, bicycles, persons and animals. [R 21] The CP register vehicles that are in the Charging Area irrespectively of whether they are driving particularly fast, very slowly or in a stop and go environment (queue). [R 23] The CP shall separate between two vehicles that are driving with a separation distance of more than 0.7 meter (along driving direction and across driving direction). [R24] The CP shall detect the presence of a trailer based on detecting the presence of a tow-bar between the pulling vehicle and the connected trailer. inimum width of tow bar is assumed to be 0.05 meter. [R 26] The CP shall measure the vehicle's height, width and length. [R 27] A vehicle with a trailer shall be classified as one vehicle and the presence of a

7 trailer shall be part of the classification data in the Transaction. [R 36] The CP shall communicate with an OBU entering the Charging Area even if the corresponding vehicle has not been detected. [R 42] The ED signal lights shall be used for feedback to the AutoPASS OBU Customer: White plus-sign: Passage approved as a valid passage with OBU, but OBU Statuslist indicates that the contract must be renewed. Green plus-sign: Approved passage. [R 48] The CP shall measure the quality of the Vehicle Images and send automatically an Exception essage indicating the reason when the measured quality of the Vehicle Images is below a critical level. The reason shall be correct in 95 % of the cases covering at least: Cleaning needed for the camera/light source, Camera/light source out of position. Camera/light source covered (snow, paint etc), Defect light source [R 49] The CP shall generate status/alarm events and send Exception essage for the types given in Table 8. CP Payment s [R 55] The validation of the OBU, see Table 9, shall determine the behaviour regarding: validity of vehicle passage vehicle classification status light to give to the AutoPASS OBU Customer whether Vehicle Images shall be collected special information to be written in the Transaction as specified in [6]. Note: OS in Table 9 refers to OBU Statusfile. The SignalCode written in the Transaction shall correspond with the applicable code for the Status light. [R 56] The status light feedback to the AutoPASS OBU Customer shall: make it possible for the driver to easily observe the correct sign for his vehicle when driving through the Charging Area, be extinguished so that it does not confuse (give wrong sign) to other drivers entering the Charging Area. onitoring Data and Functionality [R 70] The CP shall detect, time-stamp, categorise, log, translate and convey statuses and alarms from CP equipment and network. External Interface s [R 80] When passing the CP s Charging Area an AutoPASS OBU Customer shall be given feedback via the status light in accordance with Table 9. [R 83] The CPE shall receive, check and process from the Toll Charger's Central System the Payment Related Data given in [6]:

8 OBU Statusfile OBU Blacklist OBU Issuer list Price file Image Text File [R 85] The CPE shall generate and present to the Toll Charger's CS in accordance with [6]: Vehicle Passage Data: consisting of Transactions and if applicable Vehicle Image files, Exception essages: information of status/alarms from the CPs. Privacy [R 95] All Vehicle Passage Data for the vehicle passage shall be deleted from the CPE: When transferred to the Toll Charger's Central System: no later than 72 hours, When not transferred to the Toll Charger's Central System: No later than 5 days. The time period shall be configurable onitoring and Control System [R 99] The CPs shall be monitored through an Customer selected location for a common onitoring and Control Centre (CC) for all Toll Systems by the same vendor. The CC shall also include error-logs, service logs and exception messages and document events to calculate the Key Performance Indicators, see section 19 [R 101] The CS shall perform the following main functions: onitoring of CPE status, data exchange and network, Receiving, processing and presenting Exception essages, onitoring of Vehicle Passage Data, Configuration of the CP Configuration Data, Control of the CPs including setting CP ain State, Collect and present CP Quality Indicators and Signal Code statistics. [R 118] Through the CS UI it shall be easy to define levels for quality warnings with respect to Vehicle Image quality. The quality warnings shall be statistically based on continuous checking of the image quality for each separate lane. [R 127] For the common list of Exception essages for all Toll Systems delivered by the Contractor the CS UI shall: as default only display Exception essages with priority fatal and alarm, allow for list of arbitrary selection of the Exception essage priorities, allow for sorting of Exception essages. [R 128] The CS UI shall for all Toll Systems delivered by the Contractor: allow for filtering Exception essages based on Exception essage priority, and clearly indicate when such filtering of Exception essages is active.

9 [R 130] The CS UI shall allow for sorting the list of Exception essages from a Toll System based on selection/sorting criteria: essage priority: an arbitrary selection of the priority, Time interval: From date and time to date and time, CPs: an arbitrary selection of CPs, Unit type: an arbitrary selection of unit types, Subunit type: an arbitrary selection of subunit types, ane: an arbitrary selection of lanes. System Quality [R 132] The CP shall handle an On Board Unit (OBU) quota from 0 100%. [R 133] The CP shall communicate and register compliant OBUs passing at speeds from 0 km/h to 140 km/h, when the OBU mounting height is ranging from 0.5m to 2.5m. [R 134] The CP shall register Vehicle Image of the vehicle s front and rear vehicle licence plate for vehicle speeds from 0 km/h to 140 km/h. [R 135] For passages of a AutoPASS OBU Customer, the CP shall via the status light give perceivable feedback to the driver for vehicles driving below and up to at least 30% above the maximum allowed speed at the CP. [R 136] The CP shall simultaneously for each lane handle the loads given in Table 11. [R 137] Vehicles subjected to toll that pass through the Charging Area shall be registered in at least 99.9% of the cases. (I.e. out of 1000 cases the CP maximum fails to register 1 vehicle). This includes vehicles driving between the lanes or on the hard shoulder. See figure 4. There shall be only one detection for each vehicle passing the Charging Area. Note: Objects not identified as a vehicle subjected to toll are for example; motorcycles, bicycles, persons and animals. [R 138] The probability for the CP to store Vehicle Images without a vehicle or equally sized object being present in the Charging Area shall be less than 0.1%. [R 139] For AutoPASS OBU Customers with a correctly mounted and compliant OBU in accordance with the vendor s specification 1 the read accuracy shall be at least 99.5%. (I.e. out of 1000 cases the CP maximum fails to produce reading of the OBU 5 times). Note: This include all types of compliant OBUs within EasyGo. [R 140] On a weekly basis the vehicle passage s Vehicle Images shall for each CP have a quality that ensures manually reading of the PN and in addition identification of vehicle type and make for a minimum of 92% of the vehicles subjected to Charging by PR. Note: The requirement is independent of weather, sun position and road conditions. Vehicles with missing PN, damaged PN or PNs too dirty to be identified are discarded. The same is valid when the imaging sensor is out of 1 The OBU shall for passenger cars be mounted in the centre of the windscreen behind the front mirror and for trucks at the bottom of the windscreen. Excluded are OBU mounted behind the metalized part of the windscreen.

10 position and it is not the responsibility of the Contractor. [R 141] During normal weather conditions the vehicle passage s Vehicle Images shall for each CP have a quality that ensures manually reading of the PN of in minimum 98% of the vehicles subjected to charging by PR. Note: Very dense fog or the combination of strong wind and snow are not regarded as normal weather conditions. Vehicles with missing PN, damaged PN or PNs too dirty to be identified are discarded. The same is valid when the imaging sensor is out of position and it is not the responsibility of the Contractor. [R 142] The probability of storing a Vehicle Image of a trailer shall be less than [R 143] The probability of storing more than one front Vehicle Image or more than one rear Vehicle Image for a vehicle passage shall be less than [R 144] For vehicles subjected to charging by PR with visible front VP and belonging to the pre-defined set of recognisable nationalities (Norwegian, Swedish and Danish), the front ANPR accepted shall for each CP: Exceed 87 % on average. Exceed 95 % during normal weather conditions. and ANPR error shall be less than 0.5 % Note: Very dense fog or the combination of strong wind and snow are not regarded as normal weather conditions. ANPR accepted and ANPR error are defined in Figure 10. [R 145] For vehicles subjected to charging by PR with visible rear VP and belonging to the pre-defined set of recognisable nationalities (Norwegian, Swedish and Danish), the rear ANPR accepted shall for each CP: Exceed 82 % on average. Exceed 95 % during normal weather conditions. and ANPR error shall be less than 0.5 % Note: Very dense fog or the combination of strong wind and snow are not regarded as normal weather conditions. ANPR accepted and ANPR error are defined in Figure 10. [R 146] Of all vehicle passages subjected to charging by PR and with the vehicle PN belonging to the pre-defined set of recognisable nationalities (Norwegian, Swedish and Danish), the ANPR accepted shall for each CP: Exceed 75 % on average. Exceed 90 % during normal weather conditions. and ANPR error shall be less than 0.01 % Note: Very dense fog or the combination of strong wind and snow are not regarded as normal weather conditions. ANPR accepted and ANPR error are defined in Figure 10. [R 147] Of all Vehicle Images VP unreadable shall for each CP be less than 10 % Note: Very dense fog or the combination of strong wind and snow are not regarded as normal weather conditions. VP unreadable is defined infigure 10. Vehicles with missing PN, damaged PN or PNs too dirty to be identified are discarded. [R 148] The AutoPASS OBU Customer s OBU shall for each CP: be correlated to the AutoPASS OBU Customer s vehicle with erroneous correlation in less than in 1 of cases.

11 maximum be uncorrelated to the AutoPASS OBU Customer s vehicle in 1 of 100 cases. Note: Synonyms for correlated are paired or matched. Synonyms for uncorrelated are unpaired or unmatched. The reference between the vehicle and the OBU shall be in the Transaction and cross-reference to more than one vehicle from an OBU is not allowed. This implies that then the process at the CP makes the decision of correlating the vehicle and OBU such that the overall result is fulfilled by the requirement. [R 149] If unsuccessful time synchronisation via NTP the maximum deviation of the CP s master clock shall be less than 5 seconds in a 24 hours period. [R 151] The CP shall be designed such that vulnerability for single-point-of-failure is minimized and at least fulfil the criteria in Table 12. [R 152] The CP lane shall be available 99.9% of the time Availability is calculated by the total amount of hours where the system (or parts of it) does not suffer degradation or interruption in its service during an observed period, divided by the total number of hours of the same observed period. The period is set to 3 months. Availability is reset to 100% at the start of each period. The lane is not available if one of the following functions is not operating: OBU reading Image taking (video system) Detection system Data storing of transactions. Not availability implies less income or more costs for the Toll Charger. Environmental and Electrical [R 164] The outdoor mounted CPE shall operate flawlessly and be in accordance with IEC , with environmental conditions as specified in Table 15 [R 165] The performance of the CP shall not be reduced as a consequence of collection on the equipment or on the road of : Dust, snow, ice or dew, ixture of salt, snow and water splashing from the wheels of passing vehicles due to the use of salt to clean away the snow, Snow being piled up along the road/lane by snowploughs. [R 166] The camera, camera lens or other optical equipment shall be designed such that it does not experience temporary condensation on the inside or on the outside during rapid cooling/change of temperature in the surroundings. Note: The outdoor temperature may vary from -40 C in the winter to +35 C in the summer [R 167] The outdoor installation shall withstand the wind pressure and vibrations which could be expected at the CP. Design and construction

12 [R 173] The CPE shall, including availability of functionally equivalent spare parts and consumables, have a lifetime that is at least 15 years when maintained in line with the supplier specifications. [R 174] To reduce the need for cleaning to a minimum, the outdoor equipment shall have a design that avoids collection of dirt, snow, ice, water on the sensing surfaces. Key Performance Indicators s to be verified during - and - easured per unit No 157 Response time for user support and error handling All incidents 152 ane Availability/up-time ane 151, 152 TBF critical components Component type 151, 152 TTR - critical components Component type 146 OCR hit-rates during different time periods and All images per lane weather conditions 12, 19, 101, 132 Statistical distribution of different data content of the transactions (signal codes, flags, image information, security certificate, reconciliation parameters, etc.) Data element type, transaction records per lane 49, 83 Status files, black list update to the Charging point equipment Incidents type per CP 49, 70, 85 Exceptions messages from the Charging point equipment Exception type per CP 70, 99 aintenance and service logs All incident per type 49, 70 Error logs All errors per type