This is an old revision of the document!
The Civil Infrastructure Platform (CIP) aims to establish a “base layer” of industrial-grade tooling using the Linux kernel and other open source projects. This base layer will be available for use by developers creating software building blocks that meet safety, security, reliability and other requirements that are critical to industrial and civil infrastructure projects.
CIP is an open, collaborative project where you are welcome to contribute. Please join us:
The CIP Project uses the Linux Foundation Developer Certificate of Origin (DCO). Contributors to the CIP Project should adhere to the Linux Foundation's DCO and include a sign-off in their contributions.
You can follow our progress and news by visiting our website.
The first action taken by the CIP project is to select and maintain Linux kernels for a very long time (+10 years). To achieve this goal we have a group of experts. All the actions and decisions related to the maintenance of the Linux kernels selected by the CIP project are available at CIP Kernel maintenance.
Civil infrastructure industry has high stability, reliability and security standards in order to ensure safety-critical systems. A working group has been created to address this reality.
So far CIP have created B@D - This is a virtual machine that allows developers to easily run automated testing on a local Beaglebone Black or Renesas RZ/G1M iwg20m platform. Further information can be found here.
The next goal for CIP is to centralise testing, so that developers can run tests without having local access to a platform. This work is explained further in the Centralised Testing wiki page.
The CIP Core project aims to create reference minimal file system images that allow testing the CIP Core packages: a set of industrial-grade components that require super long-term maintenance. For more information, go to the CIP Core wiki page, follow the quickstart or check out the source code.
Spending efforts to maintain a kernel and operating system base layer makes little sense unless you have a software update mechanism in place. However, updating software is not an easy task. For example, random power outages can severely interfere with an update. Besides, update software can have bugs just like any other software. The CIP Software Update Working Group has been born to fill that gap by providing a robust software update mechanism suitable to the industrial-grade open source base layer.
For more information, go to the CIP Software Updates wiki page.
In order to deal with evolving cyber attacks, the CIP Security working group is working to support the adoption of IEC 62443 across the entire industry and are working to roll out solution as soon as possible as part of an all out effort to support users’ effort to acquire certification.
As the first step, we are working to solve issues for certification using capabilities of component packages and some guidelines to make industry secure by actively supporting suppliers of industrial products so that they can certify using the IEC 62443-4-2 standard.
For more information, go to the CIP Security working group wiki page.
About the IEC 62443-4 series, go to the past investigation on IEC62443-4 page.
The CIP project has selected a few hardware platforms as reference platforms for testing the project's software. More information avaialund in the CIP Reference Hardware wiki page.
CIP group is developing other actions:
Use of the names and logos for “CIP” / “Civil Infrastructure Platform” and other LF projects (i.e. Real-Time Linux) is acceptable to describe those projects and your involvement in them, as long as your manner of usage complies with the LF's Trademark Usage Guidelines (available at https://www.linuxfoundation.org/trademark-usage/). Although you will likely want to consult with your trademark legal counsel for legal advice regarding the Usage Guidelines, here are a couple, in particular, we would highlight: