Go to main content

Plugins

NOD Plugins implements business rules for modifying the Ticket Media's "Image". If the Plugin changes this Image, NOD will calculate the difference between old and new Image and deliver this as a series of client commands to the NOD client. Each Order in an Order Group is executed by an individual Plugin that alters together Image with the desired content. Several Plugins can thus be combined to realize an Order Group and the change is delivered together from NOD to the NOD Client. A Plugin owns the definition of what an Order should contain; The NOD platform has no dependencies on the contents of an Order. This means that new Orders can be distributed via NOD by registering a new Plugin in NOD that can read this Order. A PTO can even develop a Plugin that will not necessarily be used by other PTOs. The NOD platform therefore supports the distribution of private orders with execution on associated private plugins.

At the NOD Platform, the following plugins are currently running:

  • Plugin V821_18 (NSD card)

  • PLugin V821-18 DFContents (NSD card content)

  • Plugin V821_18UL (Ultralight card)

  • plugin V821-18ULContents (Ultralight card content)

  • Plugin V821_25 (Mobile Single & Periodic Ticket)

  • Plugin V821-25 RContents (Mobile Single & Periodic Ticket content)

  • Plugin INSPECTION (for checking tickets)

  • Plugin Account (Account tickets)

When executing an Order for a Travel Card, NOD will first read the entire contents of the card before it is submitted to the Plugin. In the case of mobile tickets, it is not necessary to read previous content on the ticket media, as a mobile ticket is always posted on a new Ticket medium (a new image).