To implement Tachyon you need to design, install and verify your installation. Full details can be found in Implementing Tachyon.
Broadly speaking, installing Tachyon is done in two steps:
Using the Tachyon administration console, import Instruction Definitions into Tachyon. An Instruction Definition Administrator can load Instructions by dragging and dropping one or more Instruction Definition files onto the interface. The Instruction Definitions may also be grouped together in a zip file, known as a Product Pack, and added in a single operation. Tachyon provides a whole range of 1E and community maintained Product Packs, available from the Tachyon forums.
Full details of adding Instruction Definitions into Tachyon can be found in Instruction sets page.
Following on from installation you then assign permissions to particular users corresponding to the Tachyon administration roles and product pack questioner, actioner, approver and viewer roles.
Using the Tachyon Explorer, questions can be asked of the Tachyon Agent devices by users with the questioner or actioner roles . The responses can be viewed by viewers, questioners and actioners.
Details on asking questions can be found in Explorer Home page, questions and responses.
You can use coverage and filters to reduce the amount of network traffic caused by asking a question. They are also useful in reducing the amount of data that is presented to the Tachyon users. Tachyon provides coverage, question filters and view filters.
For more information see Coverage, question filters and view filters.
Before an action is performed a question must be asked. This identifies the set of devices the action will be performed on, after the coverage, question and view filters have been applied.
Using the Tachyon Explorer, actions can be performed on the Tachyon Agent devices by users with the actioner role on a product pack subject to the following:
Details on performing actions and the approval workflow can be found in The action approval workflow.
Tachyon works in real-time, so not all of the devices may be connected at the time a question is asked. Tachyon questions have a configurable duration that they will gather data for - allowing devices that connect later, within the gather data for duration, to respond.
Questions also have a configurable keep answers for duration - given that the answers from a live network can potentially get stale quickly and Tachyon questions are fast enough that you can simply ask the question again rather than relying on old answers.
The picture opposite shows the basic flow of Tachyon Instructions between the Tachyon components. For simplicity the workflow section, where the Instruction is authenticated and verified, has been omitted.
The basic Instruction flow is:
The Tachyon Architecture has been designed to the sending of Instructions and gathering of responses for thousands of devices in seconds.
To maximize the speed of Instruction delivery and gathering responses from the Tachyon Agents, Tachyon keeps the size of Instructions to a minimum fixed size. If you want to run an Instruction that requires a script or other sizable resource in order to carry out its functionality, this is made available via an alternative mechanism using the Tachyon Background Channel.
The first step in the content delivery process actually occurs before the Instruction is used, when the Instruction containing the resource is first loaded into Tachyon:
After the Instruction has been loaded into Tachyon: