The objective of this work package is to update the state of the art at the start of the project, globally re-evaluate the desired scope for the project and define the requirements that each work package must meet to guarantee final success. These tasks will be carried out during the first six months of the project and will be generated guide documents and deliverables, for the coordinated development of the remaining work packages.
The different FIWARE enablers will be analyzed for their cataloging within the needs of the project.
The design of an architecture that constitutes the technological core of the SAINWEP project will be carried out. The design will be carried out based on the requirements and specifications obtained in WP1.
The design will be traslated to several prototypes that will be based on the architecture designed and that will serve to validate the general concept as well as test its application in specific use cases.
Work will be undertaken to develop a set of algorithms that will include business logic and intelligence in the insertion of the variety of data exchanged between devices, applications, system to system (S2S), machine to machine (M2M), between operating systems, etc.
The objects library that will be developed will include those related to various systems and architectural layers of the ecosystem of sensor-based devices. Objects related to the security layer, data exchange layer, data engine, data objects specific to the operating systems, data objects specific to manufacturers, data access and visualization, objects for data exchange, objects, interoperability objects, sensor specific objects, programming language specific programming language and other relevant objects will be developed.
APIs that can support the data exchange parameters for sensor-based devices will be developed.
The objective of this work package is the definition of the standards that will cover the planning, implementation and support of the standards section that includes the election of the management members, the standards committee, the development of the standards, the control of versions, team management and related tasks.
The collaborative tests will include the complete testing of applications, concepts, prototypes, objects, APIs, semantics, etc. Collaborative testing develops techniques and procedures to test, demonstrate and validate the results of previous activities.
As such, it is in part a continuation and refinement of the results of the use cases in more generic concepts and extrapolating the results to specific use cases in other application areas.