Pilot implementation and validation reports:
- Pilot Specification (D5.1), 19 December 2017
Charts the development of the OpenAIS live pilot specification, the search for the pilot location and the final selection of White Lady location in Eindhoven in cooperation with the tenant GGD-BZO.
- Report on selected scenarios and use cases (D1.1), updated 19 July 2016
Describes the results and process of collecting the user scenarios for the 2020's from the perspective of the different stakeholders in the lighting value chain. The scenarios were summarized in 3 super scenarios.
- Value Chain Impact Analysis Report (D1.5)
The Internet of Lighting is expected to have a significant impact on the lighting value chain as we know it today. This report explores how the OpenAIS solution can potentially have impact on the value network. First, the current lighting value network, including stakeholders and their added value, is analysed according to four phases. Secondly, the potential short term impact of OpenAIS is explored. Finally, the role of OpenAIS in future society is explored according to four perspectives.
- Final Reference architecture of OpenAIS system (D2.7), final update 13 Mar 2018
The related "OpenAIS Object Model“ that shows the API structure and is essential for interoperable systems, is also part of this document.
OpenAIS is an open service oriented IP-based lighting architecture that allows system designers in the professional lighting domain the freedom to design the systems they want to offer, while simultaneously ensuring interoperability between the components from different vendors by specifying minimum application and infrastructure layer requirements.
Please note that this reference architecture is is not a system design in itself but a template for multiple concrete system designs. The document also includes notes to guide example implementations well.
The previous version Reference architecture of OpenAIS system (D2.3), updated 19 July 2016, is now depreciated.
- Final architecture for Low Power Radio Access Point (D2.6)
Defines a reference architecture that allows vendors to build Low Power Radio Access Points using COTS hardware and open-source software. Primary goal of LPR AP is to enable easy integration of the OpenAIS network into existing IT infrastructure with minimal overhead. The dual-board architecture of LPR AP abstracts the complexities involved with low power wireless networks based on different PHY/MAC technology by providing a unified interface to IT backbone networks.
- State of the art overview in solid state lighting (D2.1)
Povides an overview of the state of the art in terms of technologies, system architectures, standards and running initiatives relevant for the scope of the OpenAIS project: to enable the Internet of Lights for office buildings of 2020 and beyond, incorporating Solid State Lighting and Internet of Things (IoT) concepts and technology. The document is available on request.
- Implementation & verification guidelines for the architecture (D2.2)
Explains and justifies the decision making process how the OpenAIS architecture deals with the functional and non-functional requirements for different stakeholders in the lighting value chain.
System Integration reports:
- FMEA and Hazard analysis report (D4.2)
It reports the result of the Failure Modes and Effect Analysis (FMEA) and hazard analysis activities conducted on an example system designed out of the OpenAIS reference architecture. For hazard identification, Hazard and Operability (HAZOP) Studies has been adopted. The main outcomes - the FMEA analysis report and the HAZOP study report, will be used for system design reviews and risk mitigation activities.
- Risk analysis report and definition of required test-ups (D4.3), updated 19 July 2016
Explains the risk assessment methods and provides a risk analysis report highlighting the risks identified from FMEA analysis. Defines a test methodology based on a test architecture that allows for continuous integration and testing, using test automation frameworks.
If you have any questions or remarks please read the FAQ first.
Your feedback is welcome to