The OpenFog Consortium work is done by committees and workgroups focused on specific tasks aligned to our mission. This work includes technical work; influencing standards development through liaisons with other organizations; testbed; promoting innovation and industry interest in fog computing; and industry education.
Working Groups and Committees
The goal of the OpenFog Consortium is to create an open reference architecture for fog computing, build operational models and testbeds, define and advance technology, educate the market and promote business development through a thriving OpenFog ecosystem.
The work of the OpenFog Consortium is done by its members, with specific deliverables organized by the Working Committees and Working Groups. Currently, we have the following active teams:
Technology Working Committee
The Technical Committee is the governing body responsible for the oversight of technical deliverables by the OpenFog consortium. It is responsible to vet technical collaborations with other standards bodies, special interest groups, and other collaborative alliances. It will accomplish this via the following:
- The Technical Committee will meet bi-weekly.
- It will collaborate with the various OpenFog technical working groups as required.
- Its members shall include at least one representative from each of the OpenFog technical working groups.
- It shall evaluate and respond to proposed technical collaborations, MoUs, strategic alliances, etc. as proposed by the OpenFog Board of Directors (BoD), Marketing team, or the Executive Director.
- It will recommend and approve liaison relationships with other organizations.
- After approval, the liaisons will be handled out of the Liaison working group.
- It shall review all OpenFog Consortium technical publications prior to final presentation to the OpenFog BoD, marketing, etc. prior to public release.
- It will recommend creation or discontinuation of technical working groups to the BoD. The BoD will still be responsible for final approval for charters and working groups.
- It shall provide a quarterly report on working groups and overall progress to the BoD.
Architecture Working Group
The Architecture Framework Working Group is the governing body responsible for the creation, maintenance, and adoption of an OpenFog reference architecture. The group will achieve this via the following activities including:
- Evaluate, classify, and recommend standards, practices, and technologies that are aligned with the OpenFog architecture pillars to address use cases provide by the OpenFog Board of Directors and Technical Committee.
- Identify technology gaps that should be addressed by the architecture.
- Analyze use cases and generate common requirements to drive the reference architecture.
- Define and recommend the architecture patterns capturing key elements, description, components and interfaces of representative deployments.
- Continually refine the OpenFog architecture by engaging with the OpenFog Testbed Working Group to ensure any “learnings” are adopted by the reference architecture and they are interoperable.
- Develop the Total Cost of Ownership (TCO) model for determination of business adoption of the architecture.
- Other workgroups will own different aspects of TCO (e.g. reliability model will fall under the domain of the Manageability Working Group).
- Author and publish the OpenFog reference architecture. Ensure that output from other OpenFog Working Groups is consistent with the reference architecture in both structure and content.
- Develop the common vocabulary of the OpenFog architecture
- Assume ownership of all key concerns not currently included in an existing or formed workgroup as directed by the Technical Committee.
- Engage with academia and industry to develop an open reference implementation of the OpenFog architecture for a software-defined world.
Communications Working Group
The Communications WG is a sub-group of the Technical Committee WG in the OpenFog consortium. The roles and responsibility of this group include:
- Evaluate and recommend standards, practices and technologies necessary to enable Communications part of the use cases provided by BoD and architecture pillars specified by the Technical Committee and Architecture workgroups.
- Identify the key OpenFog architecture pillars that relate to the Communications architecture and the related use cases.
- Identify and recommend solutions to enable end-to-end communication paradigms necessary to ensure interoperability and the connectivity of billions of end devices with variety of bandwidth, latency and jitter considerations to Core networks and data centers using OpenFog centric network elements.
- Identify technology gaps that should be addressed by OpenFog WG’s and/or work with other industry consortia to address them.
- Analyze use cases and generate common requirements across these use cases to a manageable set of representative network profiles.
- Ensure proposed solution incorporates plethora of realistic legacy communication infrastructures that exist as opposed to ideal clean-slate approaches.
- Incorporate protocol agnostic interfaces and remove assumptions related to traditional backhaul, fronthaul and midhaul networks to more of a software defined APIs that traverse across any communication interface.
- Define software defined Scalability and Orchestration technologies necessary to build and operate OpenFog centric networks. This necessitates distributing and managing end-to-end network congestion, forwarding databases, security policies and other network management objects.
- Ensure communication architecture enables the distributed and hierarchical processing model defined by the OpenFog architecture WG.
- Continually develop the Total Cost of Ownership (TCO) model for determination of business adoption of the Communication recommendations on a use-case by use-case basis.
- Author and publish communications sections of the OpenFog reference architecture. Ensure that output from other workgroups is compliant and consistent with the underlying communication paradigms defined in this WG.
- Engage with academia and industry to develop an Open reference implementation of the OpenFog Communications architecture for a software defined world.
Manageability Working Group
Security Working Group
The Security WG is the governing body responsible for the creation, maintenance, and adoption of the OpenFog Reference Architecture’s Security Pillar aspects and the associated security architecture. The group will achieve this via the following activities including:
- Recommend the comprehensive set of OpenFog Security Pillar aspects, requirements, and best practices.
- Analyze the BoD use cases in light of the OpenFog RA to understand and identify the associated potential security risk exposures and recommended remediation.
- Evaluate, classify, and recommend security standards, practices, and technologies appropriate for the use cases and aligning with the Security Pillar aspects.
- Ensure alignment with the other OpenFog architecture pillars. As security is a cross-cutting architectural concern, provide guidance facilitating secure-by-design practices across the entire architecture.
- Identify security related technology gaps that should be addressed to fulfill the security aspects.
- Define and recommend security architecture patterns, capturing key elements, descriptions, components, and interfaces of representative deployments.
- Continually refine the OpenFog security architecture patterns by engaging with the OpenFog Testbed WG to comprehend any “learnings” adopted by the reference architecture and the associate security impacts.
- Develop a security lifecycle model and supporting recommendations appropriate for the security architecture and its intended use cases.
- Author and publish the OpenFog security architecture and best practices recommendations. Ensure that output from other workgroups is consistent with the security architecture and recommendations in both structure and content.
- Leverage the common vocabulary of the OpenFog architecture
- Assume ownership of all key crosscutting security concerns of the other WGs.
- Engage with academia and industry to develop an Open reference implementation of the OpenFog security architecture for a software defined world.
Software Infrastructure Working Group
The Software Infrastructure WG is responsible for the definition of the Fog Node software composition model that will allow the creation of OpenFog computational infrastructure that is secure, elastic, adaptive, portable and interoperable. The group will achieve this with via the following activities:
- Define the vision/scope of the OpenFog software infrastructure that is required to enable the systemic qualities expected by OpenFog architecture implementations.
- Define common usage scenarios in the context of a select representative subset of the OpenFog domains in collaboration with other working groups
- Identify the software as well as services that are required by each OpenFog deployment in the context of the selected OpenFog business domains
- Rationalize the identified software as well as service requirements with the other consortia and OpenFog working groups so as to eliminate redundancies
- Evaluate standards, technologies, frameworks and internal facing interfaces to come up with a prescriptive reference architecture model
- Define external facing interfaces for a secure, safe and interoperable OpenFog deployments
- Create and maintain domain specific architecture views for the identified software architecture viewpoints per applicable standards
- Contribute content to the OpenFog reference architecture and create whitepapers and presentation material
- Create implementation guidance to help with the realization of the OpenFog test beds
Testbed Working Group
The OpenFog Testbed Workgroup reports to the OpenFog Technical Committee. This workgroup is the governing body responsible for the creation, operation, and maintenance of the OpenFog testbed framework. The Testbed Workgroup works with OpenFog member organizations to apply the OpenFog reference architecture and its implementation to testbeds, in form of OpenFog Ready Technology and Solution. The Testbed Workgroup also defines the test requirements of OpenFog Technologies and Solutions and defines the methodology for evaluating the result of testbed trials.
Marketing Working Committee
The Marketing Committee is responsible for growing the market awareness of, and interest in, fog computing and the OpenFog Consortium. We also manage the brand and messaging of the OpenFog Consortium. We will achieve this via the following activities:
- Establish the OpenFog Consortium as the place to go for fog computing leadership
- Educate the market on what fog computing is, why it’s important and the need to establish an interoperable, common approach
- Prove the value of fog computing by highlighting real-world implementations by OpenFog members leveraging the OpenFog Reference architecture when available
- Stimulate interest in fog by showcasing existing and future innovation
- Communicate progress and availability of OpenFog deliverables and facilitate forums for education and discussion
- Establish consistency of message and look and feel of the OpenFog Consortium
- Show the value of being a member of the OpenFog Consortium and help drive recruitment of new members