Fledge - Stage 2 - 2021-07-28


Completed by:  Tom Arthur and Mark Riddoch, Dianomic

Submitted to TAC Mail List:  YYYY/MM/DD

Presented on TAC Weekly Call:  2021/07/28 (Meeting Recording)




Below is a self-assessment submitted by TSC Chair/Maintainers of the Project. Comments/questions/feedback is welcome either a) in the Comments at the bottom of the page or b) during the TAC call when information is presented

Stage 1: At Large Projects 

Stage 2 and Stage 3 Projects also requested to complete this section, as PLD acceptance criteria requires meeting current as well as prior stage requirements

Stage 1 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Stage 1 Criteria (from the PLD)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

2 TAC Sponsors, if identified (Sponsors help mentor projects) - See full definition on Project Stages: Definitions and Expectations

Meets

@Mark Riddoch(Dianomic)

@Daniel Lazaro (OSIsoft)

The typical IP Policy for Projects under the LF Edge Foundation is Apache 2.0 for Code Contributions, Developer Certificate of Origin (DCO) for new inbound contributions, and Creative Commons Attribution 4.0 International License for Documentation. Projects under outside licenses may still submit for consideration, subject to review/approval of the TAC and Board.

Meets

Apache 2.0, DCO, CCA4.0 -

Technical Charter

Upon acceptance, At Large projects must list their status prominently on website/readme

Meets

Fledge



Stage 1 Projects, please skip to Additional Information Requested from All Projects

Stage 2: Growth Stage

Stage 3 Projects also requested to complete this section

Stage 2 Criteria (from the PLD)

Fledge - Mature to Stage Three (Impact)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Stage 2 Criteria (from the PLD)

Fledge - Mature to Stage Three (Impact)

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Development of a growth plan (to include both roadmap of projected feature sets as well as overall community growth/project maturity), to be done in conjunction with their project mentor(s) at the TAC.

Meets

See Roadmap 2020/2021 for the projected feature sets.

The  community growth and project maturity are discussed in the goals below.

Document that it is being used in POCs.

Show

Meets

There have been many PoCs and several commercial deployments using Fledge, some are stated publicly. Some of the PoCs can be gleaned from various public commitments and event participation such as:

Fledge has had 3 public use cases fully deployed and announced in 2020.

  • JEA

  • General Atomics

  • Honda Pro Racing

  • Some commercial deployments that can be mentioned by name but not yet announced include:

    • BRP/Rotax - OPC-UA Robots and CNC machines connected to MS Azure and OSIsoft PI for realtime part quality inspections with track and trace

    • Neuman Aluminum

    • FLIR - embedded Fledge in FLIR Bridge connected up to 10 IR cameras with integrated UI.

  • Some commercial deployments that went through vigorous PoV process and since got deployed but are not yet public include:

    • A major US Food Processor using vibration and PLC data on the edge to optimize centrifuge operations

    • A major Oil, Chemical and Paper company using Fledge to:

      • Connect data streams from 2 different cloud service offers back to historians/plant

      • Connect MQTT LoRa Wan infrastructure to historians/plant

  • Interesting PoCs underway

    • Top 5 pharma company connecting S7 PLCs to historians using the HA failover of fledge to ensure no data loss. 

    • Major OIl Pipeline company using Fledge to monitor remote battery operated measuring stations. 

    • Major glass manufacturer using FLIR, Google and Fledge for "hot" quality inspection using computer vision techniques.

The Fledge Growth stage announcement also outlined partner, contributor and user activity

  • Google has contributed IoT Core Plugin, completing AutoML and Edge ML plugins.   

  • Google will be offering a Fledge  QwikLAB in August, training users on how to use Fledge as an Industry 4.0 Edge to Google cloud.

  • Nokia has completed a Fledge  NDAC integration for private LTE.

  • Wago has completed a Fledge Wago PLC integration/offer.

  • Nexcom offers a Fledge preloaded gateway  and has contributed two south plugins to the project







Demonstrate a substantial ongoing flow of commits and merged contributions.

Meets



Demonstrate that the current level of community participation is sufficient to meet the goals outlined in the growth plan.

Meets

We are thrilled to say Fledge's community is scaling out and up.  The Fledge project is maintained under LF Edge with a single TSC, branch and roadmap.  However, the marketing and use of Fledge has expanded to two new open source communities.

  • LF Energy

    • Fledge has been adopted to be their IIoT 4.0 Edge Project

    • Over 30 energy companies

    • Fledge has a new LF Energy project name  - Fledge Power

    • RTE and Swissgrid are contributing to Fledge

  • OSDU - part of the Open Group

    • OSDU has over 167 Oil, Gas and supply chain members

    • Fledge and EVE have been adopted as the OSDU 4.0 Edge solution

    • The combined edge is under testing now

      • Show OPC-UA to OSDU cloud

      • Show edge based vibration data signal processing

      • Show edge based ML

      • Show multi-pipeline egress each with different roots of trust

      • Show EVEOS - container, vm and hw mgt

      • Show HW root of trust

Demonstrate evidence of, or a plan for, interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).





Meets

Joint Demo with Fledge and Akraino Blueprint family and Blueprint(s)

See OSDU above

Outreach EVE to LF Energy PoCs

Completed EdgeX South plugin and testing



Stage 2 Projects, please skip to Additional Information Requested from All Projects

Stage 3: Impact Stage

Criteria

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Criteria

Meets / Needs Improvement / Missing / Not Applicable

Supporting Data (if needed, include links to specific examples)

Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer.





Have a documented and publicly accessible description of the project's governance, decision-making, and release processes.





Have a healthy number of committers from at least two organizations. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.





Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).





Adopt the Foundation Code of Conduct.





Explicitly define a project governance and committer process. This is preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and OWNERS.md file showing the current and emeritus committers.





Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).





Additional Information Requested from All Projects

Additional Information Requested from All Projects

Supporting Data (if needed, include links to specific examples)

Additional Information Requested from All Projects

Supporting Data (if needed, include links to specific examples)

Intention for the upcoming year (Remain at current stage OR advance towards the next Stage)

Advance to Stage 3

Include a link to your project’s LFX Insights page. We will be looking for signs of consistent or increasing contribution activity. Please feel free to add commentary to add color to the numbers and graphs we will see on Insights.

https://insights.lfx.linuxfoundation.org/projects/lfedge%2Ffledge/dashboard;subTab=technical













Total commits 11.532, 50 submitters and 93 Repos. 

Significant to the community are major industrials and their system integrators contributing for their own operations.

Raesmann Associates - JEA

Kapsch - BRP/Rotax

Sebastion (Austrian Center for Digital Production) - Neuman Aluminum

RTE and Swissgrid for themselves and LF Energy

Nexcom for their transportation IoT solution

Teledydne/FLIR for their IIoT gateway

OSIsoft for their  Pi historian

OSDU will soon be added by contribution from several oil/gas companies





How many maintainers do you have, and which organizations are they from? (Feel free to link to an existing MAINTAINERS file if appropriate.)

Maintainers

@Mark Riddoch - Dianomic

@Bill Hunt - Dianomic

@Ashwin Gopalakrishnan - Dianomic

@Daniel Lazaro - OSISoft

Sebastian Kropatschek - Austrian Centre for Digital Production

Praveen Garg - Noida Labs

Massimiliano Pinto - Dianomic

Stefano Simonelli - Dianomic



What do you know about adoption, and how has this changed since your last review / since you joined the current Stage? If you can list companies that are end users of your project, please do so. (Feel free to link to an existing ADOPTERS file if appropriate.)



Underlined = new in last year.

There have been many PoCs and several commercial deployments using Fledge, some are stated publicly. Some of the PoCs can be gleaned from various public commitments and event participation such as:

Fledge has had 3 public use cases fully deployed and announced in 2020.

  • JEA

  • General Atomics

  • Honda Pro Racing

  • Some commercial deployments that can be mentioned by name but not yet announced include:

    • BRP/Rotax - OPC-UA Robots and CNC machines connected to MS Azure and OSIsoft PI for realtime part quality inspections with track and trace

    • Neuman Aluminum

    • FLIR - embedded Fledge in FLIR Bridge connected up to 10 IR cameras with integrated UI.

  • Some commercial deployments that went through vigorous PoV process and since got deployed but are not yet public include:

    • A major US Food Processor using vibration and PLC data on the edge to optimize centrifuge operations

    • A major Oil, Chemical and Paper company using Fledge to:

      • Connect data streams from 2 different cloud service offers back to historians/plant

      • Connect MQTT LoRa Wan infrastructure to historians/plant

    • A major theme park is using to monitor their solar array trackers

  • Interesting PoCs underway

    • Top 5 pharma company connecting S7 PLCs to historians using the HA failover of Fledge to ensure no data loss. 

    • Major OIl Pipeline company using Fledge to monitor remote battery operated measuring stations. 

    • Major glass manufacturer using FLIR, Google and Fledge for "hot" quality inspection using computer vision techniques.

The Fledge Growth stage announcement also outlined partner, contributor and user activity

  • Google has contributed IoT Core Plugin, completing AutoML and Edge ML plugins.   

  • Google will be offering a Fledge  QwikLAB in August, training users on how to use Fledge as an Industry 4.0 Edge to Google cloud.

  • Nokia has completed a Fledge  NDAC integration for private LTE.

  • Wago has completed a Fledge Wago PLC integration/offer.

  • Nexcom offers a Fledge preloaded gateway  and has contributed two south plugins to the project

  • ACDP have contributed an Azure north plugin





How has the project performed against its goals since the last review? (We won't penalize you if your goals changed for good reasons.)

This is our first review

What are the current goals of the project? For example, are you working on major new features? Or are you concentrating on adoption or documentation?

Goals for 2021

  1. Graduate to Stage 3

  2. Grow the number of project maintainers

  3. Grow the ecosystem of Cloud North support  (beyond MQTT, REST, KAFKA)

    1. AWS - Sitewise

    2. Google - Pub/Sub, AutoML and EdgeML

    3. MS Azure IoT 

  4. Provide full integration with existing:

    1. LF Edge Projects - EVE, Open Horizon, EdgeX North and South, SDO?, Akraino IIoT blueprint

    2. LF Energy - IEC104, IEC61850, RTU Server Control

    3. OSDU - KAFKA, OPC-UA and Native OSDU N

  5. Fledge roadmap

    1. Set Point Control

    2. HA capabilities

How can LF Edge help you achieve your upcoming goals?

Market to industrial companies the virtues of open source in general.

Market the virtues of Multi-cloud, Hybrid-cloud solutions to the OT market. 

Cooperate with LF Energy and OSDU in marketing and messaging

Bring in more edge application and industrial equipment providers as members of LF Edge



Do you think that your project meets the criteria for the next Stage?



  1. Have a defined governing body of at least 5 or more members (owners and core maintainers), of which no more than 1/3 is affiliated with the same employer. In the case there are 5 governing members, 2 may be from the same employer.

  2. Have a documented and publicly accessible description of the project's governance, decision-making, and release processes.

  3. Have a healthy number of committers from at least two organizations. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.

  4. Demonstrate evidence of interoperability, compatibility or extension to other LF Edge Projects. Examples may include demonstrating modularity (ability to swap in components between projects).

  5. Adopt the Foundation Code of Conduct.

  6. Explicitly define a project governance and committer process. This is preferably laid out in a GOVERNANCE.md file and references a CONTRIBUTING.md and OWNERS.md file showing the current and emeritus committers.

  7. Have a public list of project adopters for at least the primary repo (e.g., ADOPTERS.md or logos on the project website).

Project Stages: Definitions and Expectations

  1. Have a TSC- want more diversity of companies

  2. Done

  3. Need to expand diversity of companies - With LF Energy and OSDU now involved we think this will occur shortly/naturally.  Most exciting; most of these organizations are large industrials themselves intending to deploy Fledge.

  4. Done- Currently working with multiple projects

  5. Done

  6. The CONTRIBUTING.md file in the main repository has the process for both adding update/features to the core and to plugins. 

  7. Done - need to add JEA, GA, RTE, BRP and Neuman to Adopers.md  

Please summarize Outreach Activities in which the Project has participated in (e.g. Participation in conferences, seminars, speaking engagements, meetups, etc.)

Sample Project had a kiosk at IOT SWC as well as ONES NA. Also participated in the LF Edge "On the Edge" webinar series.

Speakers at conferences about OSS, IoT, and IIoT such as:

  • PI World 2019

  • Zededa Transform

  • OSS EU 2019 

  • ONES 2020

  • LF Energy

  • OSDU

Work on the LF Edge user groups creation

The LF Edge White paper

Are you leveraging the Technical Project Getting Started Checklist? If yes, please provide link (if publicly available).

No, we came in before it existed

Please review, and update if needed, your Project entry on the Existing Project Taxonomy page, modifying the Last Updated / Reviewed date in the header.

Reviewed & awaiting updates