Open Platforms Portal

This page documents the Open Platforms Portal (the website you're currently looking at). The Open Platforms Portal is an initiative of the BUTLER European project (FP7) and the Internet of Things European Research Cluster activity chain 1 (architecture models and open platforms). The objective of the portal is to reference the open technologies that can be used to create Internet of Things applications but also to document their interoperability, relationships, and reference to existing use cases, infrastructures and deployments. For now most of the components documented here originate from European research projects, but the initiative isn't limited to this scope. The Open Platforms portal can be seen as a tentative map of the Open Internet of Things Ecosystem.

  • Latest version ID: 1.0.0
  • Tags: ,
  • Latest update: July 16, 2014
  • Developed by: inno for the BUTLER project and IERC AC1
  • Contact name: Bertrand Copigneaux
  • Intellectual property rights (IPR)

    The Open Platform is an open platform and its key component will be made available as Open Source as much as possible.
    Current copyright: @BUTLER

Overview

This page documents the Open Platforms Portal (the website you’re currently looking at). The Open Platforms Portal is an initiative of the BUTLER European project (FP7) and the Internet of Things European Research Cluster activity chain 1 (architecture models and open platforms). The objective of the portal is to reference the open technologies that can be used to create Internet of Things applications but also to document their interoperability, relationships, and reference to existing use cases, infrastructures and deployments. For now most of the components documented here originate from European research projects, but the initiative isn’t limited to this scope. The Open Platforms portal can be seen as a tentative map of the Open Internet of Things Ecosystem.

Why Open Platforms for the IoT?

The availability of technical platforms, including not only standard communication protocols but also reference architectures, and key component implementations is a critical need to answer to the Internet of Things need of interoperability at different level (technical, syntactic and semantic).

Many initiatives have been started toward the creation of Internet of Things platforms, but given the broad potential reach of the IoT, it can be hardly imagined that a single platform will fully fit all potential scenario and use cases. The open approach of a “platform of platforms” proposed here is a guarantee to address not only current foreseen IoT scenarios but also to be able to adapt to emerging needs.

The purpose of the portal is to enable technology choices and as such should document not only the technical whereabouts of the open platforms components but also and more importantly all the information that enable their reuse (IPR, Service Level, Security … ). The eventual objective of the portal is to be able to answer complex queries for IoT enabling technologies and reusable components.

gimme

What do the Open Platforms Portal provides?

The open platforms initiative can neither be a standalone initiative neither a simple information repository, it is viewed as a hub that aggregates and references the information essential to the IoT ecosystem. The Open Platform documents and references:

  • Technical components at the heart of IoT applications
  • The standards, protocols and references they use
  • The use cases, applications and business models where they are applied

In addition it documents the relationships between these components and identifies the IPR and licensing schemes associated to enable you to rapidly reuse them in your applications.

Who is behind this and whom does it address?

This initiative originated from the European Project BUTLER (FP7), and is now a joint initiative part of the Internet of Things European Research Cluster activity chain 1: Architectures approaches and open platforms. The contributors to the initiative include numerous high profile European industrials, research centres and innovative SMEs at the heart of the IoT Ecosystem.

The initiative is open for anyone to make use of the components documented in this portal. If you’d like to contribute to the initiative and document your libraries, use cases, standards or applications on this portal please contact us, we’re always looking to expand our initiative.

Categories of components documented

Different categories of components can be documented on the Open Platforms Portal:

  • Use Cases: This category documents scenarios of use of IoT technologies. This can include high level application domains (Smart Home) or individual detailed scenarios (controlling home multimedia system based on user location). See more
  • Libraries: This category documents software libraries made available as Open Source or web services made available as Open API (and possibly Open Source), that provides reusable components that can be used for developing IoT applications or other enablers. See more
  • Tools: This category documents Open Sources software tools that can be used to facilitate the development of IoT applications and enablers (example: IDE, debugger and diagnostic tools…).See more
  • Tutorials and Reviews: This category represents tutorials on how to use the different components (Libraries, APIs, Tools, Applications, Models…) of the platforms; or third party reviews of one or more component(s) documented in the portal. Third parties reviews (of a single component) or comparison between different components are important to validate the quality of the components documented and to provide alternative views by independent actors. See more
  • Standards, Protocols, Models: This category documents standards, protocols and models that can be used in the design of IoT applications and enablers. (Communication protocols, architecture models, ontologies…). See more
  • Applications and Deployments: This category documents IoT deployment, or open source or closed source applications using some of the components documented in the portal in a use case documented on the portal. See more
  • Relationships: It is equally important for the portal to document the relationships between the different components to give a relevant view of the Open Platforms environment, several type of relationship can be documented : requirement, re-use, interoperability or reference, each identifying the validation methodology and completness of the relationship See more

Back Office of the Portal

General Information

The Open Platform Portal has been developped using wordpress version 3.9.1 and the wordpress custom content type manager.

The back office of the portal is available at this address

To join the initiative and get credentials to loggin, please contact us through the contact form, indicating the organization you work for and/or the project(s) you’re involved in.

documenting components in the portal

Once in the back office of the portal, participant to the Open Portal initiative only have to create and modify posts in the custom content types defined by the initiative and corresponding to the categories defined here.

Open Platforms Portal Back Office

Open Platforms Portal Back Office

Each category is defined by a set of custom fields, different type of field can be found:

  • General information fields: such as the Author of the component documented, the latest version, an abstract description or the Intelectual Property Rules associated with the component.
  • Specific information fields: such as the full specification or specific examples of use of the component
  • Service Level information fields: such as the level of support provided or the technology readiness level.

In the back office, the description of the content expected for each field is described below each custom field. Make sure to document your component as accurately as possible as it will facilitate it’s reuse and adoption by third parties

CustomFieldsPortal

Referencing the component documented

To correctly reference the component you documented, and ease it’s identification it is important to define both tags and relationships.

Tags

Tags provide a useful way to group related component together and to quickly tell readers what a component is about. Tags also make it easier for people to find your content. You can define tags, either by choosing from the most used tags or by defining your own if you need to. The size of the tags in the list indicate how often it appears in other component descriptions

tags_portal

Relationships

Relationships are an other useful way to document relations between component and to ease the discovery of your component. The principle of relationships is based on a social media like paradigm (think of component being “friend” with each other). Each component can have relations with each other, some relationships are close (re-use) some more distant (reference), the relationship make it easy for the end user to jump from one related component to another.

To enable a high level of reusability of your component it is very important to well document its relationships. It not only provide a useful way to discover your components, but also provide additional information necessary for the reuse of your component: such as which other component it is interoperable with, what use case or architecture model it is based upon and how it will fit in the end user ecosystem.

Relations are defined by a specific Custom Field in the description of each component, and we have created a tutorial to present in detail how to create one.

Supporting Documentation

The following ressources provide additional background and information on the Open Platform initiative:

Service level

management of the initiative

The Open Platforms Portal initiative is currently developed and administrated by inno TSD for the BUTLER project. This version is the first public version of the portal and regular updates and improvements are planned.

updates and planned evolutions of this page

This documentation is a first version, it is planned to be expended with a description of each custom field, mapping between custom field and categories, and examples

Technology Readiness Level

4 - technology validated in lab

Reuse Readiness Levels

4 - Reuse is possible; the software might be reused by most users with some effort, cost, and risk.