Status
- Current Project Stage: Pending PLD completion / TAC presentation
- Website:
- Wiki:
- TAC Sponsor(s):
Project Proposal - Project Introduction:
Required Information | Responses |
Name of Project | |
Project Description (what it does, why it is valuable, origin and history) What does FogLAMP do? FogLAMP is an Industrial Internet of Things (IIoT) open source project and an essential Fog Computing component. FogLAMP uses a pluggable modular architecture to easily connect any/all sensors, machines and IIoT devices, manage their data and forward it to historians (like OSIsoft’s PI), enterprise systems and the cloud. Why it is valuable? FogLAMP’s modern architecture eliminates the expensive proprietary DCS, PLC, SCADA, sensor silos that make integrating and analyzing data from multiple systems so difficult for industrial manufacturers and plants. By using a consistent set of RESTful APIs to develop, manage and secure all your IIoT applications, FogLAMP is the vendor unifying solution. Developers and operators no longer face complexity and fragmentation issues when building their IIoT applications as they gather and process more sensor data to automate and transform business. Origin/History? The company Dianomic was conceived by Pat Kennedy (OSIsoft) and Dave Mount (Kleiner Perkins) then founded by Bill Hunt and Tom Arthur in 2017. Dianomic believes that existing software solutions do not meet the needs of today’s IIoT developer for building fast, easy, scalable, secure systems from sensors to clouds for industrial applications and data. | FogLAMP |
Statement on alignment with Foundation Mission Statement Create a unified community for Open Source Edge that:
FogLAMP is conceived, architected and licensed to “create a unified open source community for edge computing”. Specifically, FogLAMP is focused on the industrial edge found in manufacturing and plant operations with a go-to-market focus starting with “Process Manufacturing” including industries like oil and gas, energy, pharma, transmission -distribution, water and waste. The architecture has the developer in mind using microservice modularity and plugins for quick adoption. Developers familiar with Python or C should be able to rapidly learn, utilize and contribute to FogLAMP. | |
| High level assessment of project synergy with existing projects under LF Edge, including how the project compliments/overlaps with existing projects, and potential ways to harmonize over time. Responses may be included both here and/or in accompanying documentation. | |
Link to current Code of Conduct | |
Sponsor from TAC, if identified (a sponsor helps mentor projects) | |
Project license | |
Source control (GitHub by default) | |
Issue tracker (GitHub by default) | |
External dependencies (including licenses) | |
Release methodology and mechanics | |
Names of initial committers, if different from those submitting proposal | |
| Current number of code contributors to proposed project | |
| Current number of organizations contributing to proposed project | |
| Briefly describe the project's leadership team and decision-making process | |
| Preferred maturity level (see stages here) | |
| For Projects applying at the Growth (Phase 2) or Impact Stage (Phase 3), please outline how your project successfully meets/exceeds the requirements as defined under each category. Responses may be included both here and/or in accompanying documentation. | |
| List of project's official communication channels (slack, irc, mailing lists) | |
| Link to project's website | |
Links to social media accounts | |
| Existing financial sponsorship | |
| Infrastructure needs or requests | |
| Project logo in svg format (see https://github.com/lf-edge/lfedge-landscape#logos for guidelines) | |
| Trademark status | |
| Does the project have a Core Infrastructure Initiative security best practices badge? (See: https://bestpractices.coreinfrastructure.org) | |
| Any additional information the TAC and Board should take into consideration when reviewing your proposal? |
Project Proposal - Taxonomy Data:
| Functions | Does Proposed Project Currently Address? (Yes, No or Planned/Roadmap) |
|---|---|
| APIs | |
| Cloud Connectivity | |
| Container Runtime & Orchestration | |
| Data Governance | |
| Data Models | |
| Device Connectivity | |
| Filters/Pre-processing | |
| Logging | |
| Management UI | |
| Messaging & Events | |
| Notifications & Alerts | |
| Security | |
| Storage |
| Deployment Type | Does Proposed Project Currently Include? (Yes, No or Planned/Roadmap) |
|---|---|
| Customer Devices (Edge Nodes) | |
| Customer Premises (DC and Edge Gateways) | |
| Telco Network Edge (MEC and Far-MEC) | |
| Telco CO & Regional | |
| Cloud Edge & CDNs | |
| Public Cloud | |
| Private Cloud |
| Industry/Verticals | Does Proposed Project Currently Target? (Yes, No or Planned/Roadmap) |
|---|---|
| Automotive | |
| Chemicals | |
| Cloud Operators | |
| Cloud Service Provider | |
| Data Centers & IT | |
| Enterprise | |
| Facilities | |
| Home Edge | |
| Manufacturing | |
| Metal & Mining | |
| Oil & Gas | |
| Pharma | |
| Power & Utilities | |
| Pulp & Paper | |
| Telco Operators | |
| Telco/Communications Service Provider | |
| Transportation | |
| Water Utilities |
| Use Cases | Does Proposed Project Currently Address? (Yes, No or Planned/Roadmap) |
|---|---|
| Fixed placement edge constellations | |
| Gateways (to Cloud, to other placements) | |
| Mobile deployments, static services, intermittent connectivity | |
| NFV Infrastructure | |
| On-demand events | |
| Wearables |
| Compute Stack Layers | Does Proposed Project Currently Include (Yes, No or Planned/Roadmap) |
|---|---|
| APIs | |
| Applications | |
| Firmware | |
| Hardware | |
| Orchestration | |
| OS | |
| VM/Containers |
| Cloud Stack Layers | Does Proposed Project Currently Include (Yes, No or Planned/Roadmap) |
|---|---|
| Applications | |
| Configuration | |
| Content | |
| IaaS | |
| PaaS | |
| Physical Infrastructure | |
| SaaS |
Attachments (LF Edge PPT template is below):