Project generation
At deployment stage, the IoT System integrator follows a specific pattern to build the project and assign the particular characteristics that will define how data is sent to the blockchain
When all IoT devices have been added to the platform and identities for current project’s to-be-deployed IoT devices have been issued, it is the moment to work on the IoT network generation, deployment and ownership transfer (if requested by the end-client). The generation phase involves the project setup, deployment configuration, and spot definition. In order to understand the data model regarding the objects project, deployment and spot, let us have an initial look at the diagram below:
A project is the highest-level entity that represents a semantic unity as a whole (e.g. an IoT network infrastructure to be deployed in a hospital facility) that involves several deployments, defined as the mid-level organizational units inside a project that possess some characterizing self-determining patterns (e.g. the several medical areas, or floors of a hospital). Each deployment will have, at the same time, what we have denoted as spots, i.e. the specific geo-located unit where IoT devices will be eventually deployed (e.g. a spot is a specific location inside room A1 in floor 4 for project “Local Hospital”, this spot having one or more IoT devices attached to it).
All the projects category endpoints, implement the necessary CRUD operations to operate with any of the three entities shown above. Please, check out Tutorial section to understand how to make use of this data level hierarchy. For more information on each particular endpoint, you can have a look at the API section.
Last updated