Notes
Slide Show
Outline
1
 
2
"LCV and HGV vehicle inclusions"
  • LCV and HGV vehicle inclusions


  • CAP amended the structure upon which they deliver new vehicle data in their LCV file from October.
  • This resulted in HGV vehicles being included where the majority of vehicles in an LCV model range were LCV.
3
"LCV and HGV vehicle inclusions"
  • LCV and HGV vehicle inclusions


  • A new FNVTYP record – H – allows users to EXCLUDE HGV vehicles from their offerings despite the file delivery adopted by CAP for LCV file sets
  • There is generally no extant ability to be able to exclude them, other than by onerous, manual intervention.
4
"LCV and HGV vehicle inclusions"
  • LCV and HGV vehicle inclusions


  • The  new FNVTYP record has been added – H – specifically to deal with HGV vehicles now being produced within the FleetNet Codes, SOLELY to match the file delivery by CAP LCV file sets.
  • THERE IS NO INTENTION to extend the range of HGV’s on offer within the codes beyond this derogation.
5
"The FleetNet User Group"
  • The FleetNet User Group


  • FleetNet is a Company Limited by the Guarantee of its Members.


  • All members have combined rights to the intellectual property of the Code
6
"The FleetNet User Group"
  • The FleetNet User Group


  • Every Member has equal rights and an effective, proportional, ownership of the Code.


  • Every Member has an obligation to ensure the security and rights of the other Members’ use of the Code.
7
"The FleetNet User Group"
  • The FleetNet User Group


  • An organization can be a Member without taking or using the Codes


  • Codes are delivered on behalf of, and to, the Code user Members by the Code Manager (CAP in the UK, FleetData in Portugal)
8
"The FleetNet User Group"
  • The FleetNet User Group


  • A Code User Member gains access to the 40 Character codes and their attendant tables and content.


9
"The FleetNet User Group"
  • The FleetNet User Group


  • A Code User Member has no automatic right to access    cross-reference files other than those for Data providers with whom they have a relationship.


10
"The FleetNet User Group"
  • The FleetNet User Group


  • The Codes are complied and delivered by a Code Manager for each Territory who will normally be a Data Provider to ensure access to sufficient Manufacturer information to be able to compile the Code for the users.
11
"The FleetNet User Group"
  • The FleetNet User Group


  • Data Provider Members have the right to link their own Vehicular codes to the EDi (which links to the 40 Character code in user systems).
12
"The FleetNet User Group"
  • The FleetNet User Group


  • Data Provider Members have the right to distribute their own codes with a cross-reference link file to FleetNet EDi ONLY, and the 40 Character codes MUST NOT be distributed.
13
"The FleetNet User Group"
  • The FleetNet User Group


  • Any Data Provider Member can supply Code User Members a cross-reference link file from FleetNet EDi to their own data, as they see fit.
14
"The FleetNet User Group"
  • The FleetNet User Group
  • Why only the EDi?
15
"The FleetNet User Group"
  • The FleetNet User Group


  • It will always be possible for a NON-Member to be able to        De-Compile the 40 Character code to some degree.
16
"The FleetNet User Group"
  • The FleetNet User Group


  • The 40 Character code is DYNAMIC, and as such, should it NOT be updated by a provider or user to the latest version, link errors will occur.
17
"The FleetNet User Group"
  • The FleetNet User Group
  • ANY references to prior 23 Character codes MUST BE REMOVED from all DATA Providers systems and not distributed onward to users.
18
"The FleetNet User Group"

  • The FleetNet User Group


  • JUST WHAT DOES THIS MEAN TO THE USERS WITHIN THE GROUP?


19
"The FleetNet User Group"
    • The FleetNet User Group
  • End user Members require to dynamically update their systems to reflect any changes in the 40 Character code to be sure they have the most “correct” information in place.
  • Nothing other than the EDi should be existentiated – sealed into - end user systems.
20
"The FleetNet User Group"
  • The FleetNet User Group
  • Repercussions  - core information remains incorrect throughout the vehicles’ life on fleet.
  • Permanent loss of data due to FleetNet Code table content – elements such as engine types, bodies or any other – being changed or retired.
21
"The FleetNet User Group"
  • The FleetNet User Group


  • Loss of cross-referencing to Data Providers’ Codes.


  • Inability for System providers to run functionality such as automated sale price/auction reserves.
22
"The FleetNet User Group"
  • The FleetNet User Group


  • Lack of integrity for periodic financial reviews and Re-Valuations.


  • Potential for LARGE scale code mismatching.
23
"The FleetNet User Group"

  • The FleetNet User Group


  • The impacts for the User Group ongoing.


24
"The FleetNet User Group"
  • The FleetNet User Group


  • FleetNet as an entity and a user group requires to protect our collective interests by ensuring the IP of the code is protected.
  • New User agreements will put due emphasis on a range of issues.
25
"The FleetNet User Group"
  • The FleetNet User Group
  • A contractual requirement to protect the code by ensuring only EDi’s are used for passage of electronic data within the User Group
  • A limitation of Liability, capped to the then current value of the Code Usage subscription as a maximum.
26
"The FleetNet User Group"
  • The FleetNet User Group
  • Every Member has equal rights and an effective, proportional, ownership of the Code.
  • Every Member has an obligation to ensure the security and rights of the other Members’ use of the Code.
27
"The FleetNet User Group"
  • The FleetNet User Group
  • Members must check that other users with whom they may be exchanging data via EDi, are current Members in their own right.
  • The FleetNet website will carry an Alphabetical reference list of all current members from January 2008.
28
"The FleetNet User Group"
  • The FleetNet User Group


  • Member agreements will be refreshed for 2008, and a web acceptance will be required to be completed by EVERY user without fail, by a duly authorised member of staff for the user.
29
"The FleetNet User Group"
  • The FleetNet User Group


  • Members who have not completed the Web controlled agreements by the end of January 2008 may have their download service withdrawn.
30
"The FleetNet User Group"
  • The FleetNet User Group
  • It is your code – use it effectively, and protect its integrity to ensure its continued value to your business.