HID iCLASS SE Encoder User Guide - Manual (Page 12)

Overview Page 1-6
PLT-01067, Version: A.3 April 2014
1.1.8 Plugin Architecture
The CP1000 includes a plugin architecture which makes it highly configurable with minimal
maintenance and few releases. There are two types of plugins:
• Technology
• Configuration
Technology plugins are a packaged bundle that includes an applet which is loaded to the encoder
device and a UI plugin for the desktop application that is customized for the associated applet.
• Applets are small C# applications designed to run on the .NET framework that is native to the
encoder device. These applets manage the interface to the smart card and provide an API to the
desktop application. Applets can be tailored for a specific use case.
• The UI plugin manages the interface to the encoder device and provides the user with inputs
and information specific to the applet loaded on the device. For example, each technology
applet comes with a unique set of wizard pages gathering user input for work order creation.
Configuration plugins expose a UI for gathering inputs and creating reader configuration cards.
Reader configuration plugins are released as groups that organize parameters.
Things to know about plugins:
• Each plugin is digitally signed by a key managed by HID and known by all encoder devices
(global key). This identifies the applet as Genuine HID. Only Genuine HID plugins are recognized
by the encoder device.
• Initially, one applet/plugin is created for each of the four supported technologies (iCLASS,
MIFARE Classic, MIFARE DESFire EV1, Prox, and Seos).
• Custom plugins can be created on a CPO basis.
1.1.9 Work Orders
All credential encoding activity is managed through Work Orders. Each Work Order includes a set of
Work Instructions to be executed on every card or token presented to the encoder.
• Work orders execute a work flow that you design
• Work Orders are technology independent
• Work Orders can be limited in scope or open-ended
1.1.10 Work Instructions
Each Work Instruction represents one step of an overall work flow that is executed on every card or
token presented to the encoder.
• Work Instructions are analogous to scripts
• Work Instructions are technology specific
• Work Instructions are wholly independent operations
1.1.11 Custom Applications
Custom Applications can be written to cards. The iCLASS SE Encoder supports two types of custom
application; Custom Host and Data Mapper.