OpenBridge Joint Industry Project (JIP)

Development of an open-source implementation of the OpenBridge Design System. Jointly financed by industry partners through the Innovation Norway Company Network. The project is scheduled to start in January 2025, with components being delivered on a continuous basis until the allocated funding is expended. The components are compatible with all web frameworks.

Key Personnel

Torstein Aarseth Bø
torstein@openbridgecomponents.no

Torstein Aarseth Bø will serve as the lead developer for the project. He is the primary developer behind the existing OpenBridge web components GitHub project. Torstein holds a PhD in Engineering Cybernetics from NTNU, Norway, and has worked at SINTEF from 2018 to 2024.

Kjetil Nordby
kjetil.norby@aho.no

Kjetil Nordby will oversee the connection to the OpenBridge research projects (OpenAR, OpenRemote, and OpenZero). He will also ensure effective knowledge transfer from the Ocean Industries Concept Lab and make resources available for quality assurance, verifying that all components strictly follow the guidelines. Additionally, Kjetil will establish a feedback loop to identify and address any weaknesses discovered during implementation. He is a professor of interaction design, the manager of the Ocean Industries Concept Lab, and the founder of OpenBridge.

Main Objectives and Background

The main objective of the project is to implement the OpenBridge Design System using web components and make it available as open source. This will serve as the foundation for a sustainable open-source infrastructure, featuring high-quality implementations of the components. The system will provide an excellent developer experience through developer-focused documentation and tooling.

The GitHub project openbridge-webcomponents has started implementing some of the OpenBridge components. This is the only open-source implementation of the latest release of the OpenBridge guideline (6.0). The existing resource is a strong foundation that has been developed together with industry participants over three iterations. However, most of the components and their variations are still missing from the library. There are 6000+ variants in the current design guideline. At the same time, the need for a web-based implementation of OpenBridge is evident among many industry partners who are currently developing them independently. The OpenBridge JIP seeks to distribute the cost of developing this resource, since the industry is essentially developing identical components.

By using web components, the library is compatible with all JavaScript frameworks. Wrappers for Vue and React are established to increase developer experience. Similar wrappers can be made for other JavaScript frameworks by request from partners.

The OpenAR project has funding for one developer from January 2025 to May 2025. From June 2025, the project will be financed by a Company Network project, supported by Innovation Norway if accepted.

Scope of the Resource

OpenBridge is an industry-oriented design guideline and front-end library adaptable to most industrial settings. It is most developed for maritime purposes such as ship bridges, engine rooms, and ROC centers. However, it can be applied to a much wider set of use cases. It follows design standards from the maritime industry, land-based industries, and public services. It is currently industry-proven in many industrial cases.

OpenBridge can be divided into three main parts:

  1. A generic application framework that defines the user experience for general maritime applications (includes features such as page navigation, alerts, dimming, settings, and help system).

  2. An extensive set of the most typical generic interaction components necessary for making modern applications (e.g., buttons, menus).

  3. A series of content modules supporting specialized applications (e.g., maritime instruments, 1500+ icons, bars and graphs, AR overlays, map components, dashboard components, automation components, etc.).

Together, OpenBridge is by far the most extensive open design guideline for industrial systems that exists.

Benefits of the JIP

There are systemic benefits of helping realize the resource that will differ from partner to partner depending on their size, structure, and needs. Among possible benefits are:

  • Reduce costs and increase efficiency by applying an off-the-shelf, complete, high-quality front-end resource for advanced industrial user interfaces.

  • Improve user interface quality by using an open standard that benefits from continuous, iterative, and transparent research-driven development and draws directly on the combined competence of a global group of industry experts.

  • Improve multi-vendor collaboration by being able to integrate user experience with other OpenBridge-compliant suppliers and customers.

  • Improve academic collaboration by being able to collaborate more efficiently with the growing number of academic institutions using OpenBridge in their innovation. Currently, institutions such as RISE, Marin, NTNU, UiB, and KRISO are already applying OpenBridge in their research.

  • Collaborate better with students by having an open-source front-end available.

  • Increase production by in-house design teams, by standardizing core interaction and GUI components so in-house teams can focus on advanced user experiences and streamline design processes.

  • Increase innovation by leveraging components with novel user interface features delivered by the OpenBridge research projects.

  • Influence industry by participating in developing the leading open standard for modern maritime user interfaces.

Deliverables

The components will be made available continuously, through regular releases to npm as is done today. However, for the first 12 months the repositories (npm and GitHub) will be exclusively available to the project partners. After the 12-month embargo, the code and packages will be made publicly available (open source).

The members of the JIP will have the possibility to send in a list of prioritized components. The work will then be prioritized based on these lists.

The target of the project is to implement all current components in the design system based on the prioritization list. However, the completeness depends on the funding of the project. Our goal is to reach a point where code development and new guideline developments are in sync.

As illustrated in the figure below, the foundation of the library is completed. "Level 1: Design" is established through the designers at AHO. The OpenBridge design system 6.0 is soon to be available. The code framework (Level 2) is established, after two earlier implementations of the framework. The implementation of the components (Level 3) has already started; this project targets financing the remaining work.

The library is already documented, but a good documentation web page for developers using the library is still missing. If the funding is large enough, remaining funds will be used to increase the developer experience through documentation and tooling.

Tasks

  • Development of components, as described earlier.

  • Administration of in-kind contributions. In addition to the membership fee, the partners can contribute with in-kind (development of components). The project will therefore fund the organization of in-kind work, such as introduction to the code, guidance on the development of components, and work to merge contributions.

  • Code introduction and guidance to partner developers.

  • Administrative work for the project.

Organization and Budget

The first 5 months of the project will be funded by AHO directly. We accept contributions from both Norwegian and international companies. Norwegian partners will be part of a Company Network (Bedriftsnettverk) supported by Innovation Norway. Innovation Norway can support such a network with up to 1 million NOK per year, for up to three years. All participating companies must be Norwegian with a healthy economy. At least 50% of the companies must be small or medium-sized. The application is only valid for the first year of the project, and a new application must be submitted each year. An extension of the project will be discussed with the project partners at the end of the project.

The project will be organized by OpenBridge Components AS, a company owned by Torstein Aarseth Bø. He is the main developer of the GitHub library and will be the main developer in the project. The board of OpenBridge Components AS consists of Torstein Aarseth Bø and Kjetil Nordby.

Timeline

The project start in January 2025, with funding from OpenAR for the first five months. An application for a Company Network project will be submitted to Innovation Norway at the beginning of 2025. The goal is to ensure the project continues beyond the end of OpenAR funding (May 2025) and extends for an additional year, until May 2026.

Contributions

The level of cash contribution will depend on the number of participants. We believe that the contributions should be based on the value the project provides to the company. The project will deliver a code library and support for developers. Therefore, the contributions from each company should align with their needs for the library and support.

The cash contribution is divided into three categories:

  • Small (20,000 – 50,000 NOK / 1,760 – 4,400 EUR): For companies that primarily wish to support the project without expecting direct benefits. These might include companies where the library strengthens their ecosystem.

  • Medium (50,000 – 150,000 NOK / 4,400 – 13,200 EUR): For companies with a limited number of users for the upcoming library. This could include start-ups where OpenBridge forms part of their core value or medium-sized companies where OpenBridge is a minor part of their offerings.

  • Large (150,000 – 250,000 NOK / 13,200 – 22,000 EUR): For companies with multiple development teams that will actively use the upcoming library.

Participants may also contribute through in-kind work. It is required that the contributing developers have a basic understanding of web development. Additionally, the in-kind contribution must consist of at least four components to ensure that excessive time is not spent on training and administration.

Invoicing

The membership fee will be invoiced by OpenBridge Components AS and must be paid before joining as a member.