IOP Alliance

Council calls June 2021

Call 2021.1 - June 14th

Agenda

Overall objective: getting us onto the same page, preparing for a call n2 where we plan ahead.

​

17.30-18.15 CET - A round of: “how are you doing & what have you been up to?”

​

18.15-18.30 - IOPA Update: Mission/vision/website. Initiatives: OKH/OKW updates

18.30-18.45 - IOPA Update: fundraising

​

18.45 - 18.55 - Discussing voting in new members.

18.50 - 19.00 - Wrap-up incl. Potential action points for call 2.

IOPA Updates

Communication:

• Website (see next slide)
• Visual identity (by Kaspar. See next slide)
• Talk proposals submitted/to submit:
• Linux Foundation Open Source Summit: panel + talk
• Fabcity (todo. OKW focus)
• Fab16 (todo. OKH focus)

Initiatives:

• OKH
• OKW

Sloan bid (as submitted)

1. Open Standards: building Internet of Production infrastructure

• Open Know-How discoverability standard maintenance.
• Open Know-How portability/interactivity standard community scoping, design and collaborative technical authoring to establish an open digital infrastructure enabling the re-use of hardware designs across hardware platforms. �
• Open Know-Where data standard maintenance.
• Open Know-Where digital infrastructure established with launch of a data trust with user interface on OpenStreetMap (e.g.: find ‘machines near me’ or ‘where can this design be made’ features) with open-source APIs to share data across hardware and mapping platforms. �
• Community scoping, design and collaborative technical authoring of people & skills open standard(s) for open, hardware and maker skills by building upon existing badging initiatives and educational mutual recognition accords.
• Community scoping, design and collaborative technical authoring of materials & components open standard(s) likely focused on launching a database/ontology by building on emerging initiatives and key industry conventions.
• Community scoping of contracts & business models standard(s) and associated fundraising for future development, including engagement with Open Chain and GitLaw on contracting standards, traceability and quality assurance.
• Business models for distributed manufacturing of hardware codified, including distributed quality control steps and recommendations for ensuring ‘virtuous circle’ (avoiding platform economy pitfalls), ready for contracting standard.

​

Sloan bid (as submitted)

2. Adoption: promotion and uptake of the standards

• Launch for Open Know-Where data standard, and associated follow-up activities.
• Communications materials and digital tools for makers, organizations and platforms to adopt and use standards (including promotion of the Open Know-How manifest creator and an Open Know-Where ODK-based survey tool).
• Active outreach by staff to makers, organizations and platforms to encourage adoption of Open Know-How and Open Know-Where, including ongoing engagement and support.
• Support to web crawler development initiatives to search Open Know-How manifests, enabling open hardware search.
• Open Know-Where data gathering awards to volunteers to incorporate data from existing large datasets.
• Launch, communications materials and promotion of the people & skills and the materials & components open standard(s).

​

​

Sloan bid (as submitted)

3. Growth: Sustainability of the Alliance community

• Registration of an Internet of Production legal entity with appropriate governance structures agreed.
• Communications, fundraising and materials development and support, including Theory of Change workshop, simple user journeys, standards slide decks and help to alliance members in outreach.
• 20 new members of the alliance.
• Online IOP conference, community development activities, working groups.
• Launch of research on governance issues in distributed manufacturing.
• Support to processes needed for verifying designs and ground-truthing mappings.
• Contributions to NIST and NIH policy processes taking place in the USA, to inform possible future policy work.
• Participation in Linux Foundation Open Manufacturing Partnership and World Economic Forum initiatives.

​

Sloan bid (as submitted)

Budget lines:

• IoP Alliance Chair, part-time: outreach to private sector and industry organizations.
• IoP Alliance coordinator, part-time: secretariat, actions coordination; promotion/adoption support; fundraising
• IoP technical coordinator, part-time: technical strategy, guiding the consultants and working groups
• IoP Operations officer: logistical and administrative support, communications
• Data Standard Support Specialist, full-time: adoption support, “help-desk” and hands-on support.
• Open Know-Where Specialist, full-time: adoption support, development & maintenance of data system, “help-desk” and hands-on support.
• Consultants: business model codification; electronics components data standard, new standard technical authoring for portability/interactivity Open Know-How standard, new standard technical authoring for standards for people and skills and for materials and components.
• Annual conference (online) & Data gathering volunteer awards.
• Membership to networks/partnerships (Including Linux Foundation Open Manufacturing Platform).
• Travel

​

Scenario 3 - a.k.a next in fundraising

• Open Know-Where data trust launched with single user interface (e.g.: find ‘machines near me’ or ‘where can this design be made’ features) and with open-source APIs to link to existing platforms that have adopted this standard.
• Hosting and updating of the ‘Atlas of Innovation’ dataset as part of wider open hardware enabling environment.
• Open Know-How enabled hardware designs search engine developed using web crawler tool.
• Community development support for a fully open platform for open hardware designs, potentially based on the (already funded and open-sourced) Welder.app platform and the DocuBricks tool, among others, incorporating Open Know-How.
• Community development support for an open source makerspace management system (based upon existing systems, including MakerNet.work and FabManager), incorporating of Open Know-Where and the people and skills standard.

Voting in members

• Reach / Followers / ….

Self-selected, anyone who is interested to know what we’re up to.

​

• Members

People or organizations who want to sign up as supporting our mission, and who we (council members, currently) wish to accept as members.

​

• Council (or other governance body)

Made up of members. Currently self-appointed and we can vote in other members to join us. We may want to think about ways to make it more democratic down the line.

​

• Working Groups

Will include anyone who wants to join - no requirement that they are members, though we would probably invite them to be.

Thanks and see you next week!

Council call 2021.2 - June 25th

Agenda

Overall objective: planning ahead.

​

17.30-17.45 CET - Welcome & Check-in: 1 minute / participant

17.45-18.05 - Discussion and vote on new members

18.05 - 18.30 - Review of action points

18.30 - 18.55 - Looking forward, open discussion

18.50 - 19.00 - Wrap-up

Action points update

1. OKH: Andrew to share OKH next phase & fundraising target updates
2. OKW: Anna, Tom Bartley and Andrew to have a call on materials and materials standards
3. PoC: All to share links on materials and resources on how we talk about materials on Slack
4. PoC: All to discuss what we want to do around materials to bring to the next meeting - the feasibility of it, How much they might cost, and where the money can come from
5. Governance: Nathan, Andrew and Anna to have a call in the next few weeks to discuss the proposal of moving Makernet.Work's 50132 to the home of IoP, develop ideas and share on Slack so everyone can contribute on that - one pager proposal for the next call
6. Governance: Cecilia to create a private member council (done)
7. Governance: Tom, Andrew to have a call on picturing what will be a desirable place for iop, how memberships can support, prepare a short document
8. ToC: Andrew to catch up with Doc and Anna: so that before talking to IDEO, we can get some strategies and inputs from members of the group
9. Comms: Cecilia to represent all the groups/channels to IoP websites
10. Comms: Everyone to share feedback on the website, use the website channel on Slack to share feedback https://internet-of-production.webflow.io/

​

New members to vote in

• Xxx
• Xxx
• xxx

IOPA

Membership Proposal June 2021

Notes

• Lay out objectives - breadth & action
• How democratic?
• Diagram with tiers and working groups
• Tiers definition
• Membership routes & process
• Individuals vs organisations?
• Council options - entity, rotation, et cetera
• Look at Open Questions

​

2019 - IOM Summit

Interim Governance Proposal

Contents

• Principles
• Overview
• Member Council - Initial Membership
• Taskforces - Initial Membership
• Driver Role
• Chair of Member Council Role
• Coordination Mechanism - Monthly Calls Proposal
• Open Questions

​

Design Principles

1. Action-oriented - The objective of having a governance structure is to enable action in the direction of building open infrastructures that enable anyone, everywhere to participate in production.
2. Lightweight - We need a non-bureaucratic governance structure that enables people to drive forwards on the topics they are passionate about, with minimum impediment
3. Better together - We are working as a group because we believe that no one person, project, or organization has all of the answers - we want to involve many actors and perspectives
4. Transparent - Decision-making should be transparent and there should be an opportunity for dissenting voices to be heard
5. Flexible - Everyone has other things going on that will keep them busy at times, we need to be able to move forwards with whoever is available to participate

​

Overview

The proposed interim structure has three elements:

1. A member council - this is the overall governance body made up of one representative from each organisation (or individual) who was in the room in Warsaw. It governs the strategic direction of all common activities.
2. A set of taskforces - one per strategic goal - made up of volunteers, who can be on the member council or can be anyone else who wants to contribute. Each taskforce has one named driver who is responsible to make sure effective progress is being made at an appropriate pace towards the goals set by the Council.
3. A coordination team, made up of the drivers for each of the taskforces plus the chair of the member council. It coordinates action across the taskforces and reports on progress to the member council.

​

​

Member Council - Initial Membership

Proposal: Andrew Lamb to Chair the Member Council

Member Council

Pierre-Alexis Ciavaldini / MakerNet.org

Doc Martens / UNUM

Tom Salfield / Wikifactory

Nathan Parker / MakerNet.work

John Gershenson / Kijenzi

Anna Sera Lowe / Manufacturing Change

Andrew Lamb /

Field Ready

Anna Waldman-Brown

Barbara Kieslinger /

Centre for Social Innovation

Voting

​

Votes in the Member Council are taken by simple majority and are valid if more than half of the council has voted (i.e. 5+ people).

​

Votes may be taken:

​

(1) Synchronously, in person or on pre-arranged calls (where provision has been made for people unable to attend who want to vote)

​

(2) Asynchronously, by whatever means the group decides (e.g. Discord / WhatsApp / …) where the topic to be voted on is displayed for at least 72 hours

​

In either case, if a simple majority of the council (5 people) vote one way, the vote is completed.

Membership is a voluntary position and we envisage it always being so

Taskforce Members

Theory of Change

Funding

Open Infrastructures

Governance

Driver:

Doc Martens

Driver:

John Gershenson

Driver:

Tom Salfield

Driver:

Anna Lowe

Anna Lowe

Anna Lowe

Andrew Lamb

Andrew Lamb

Pierre-Alexis Ciavaldini

Vivien Roussel

John Gershenson

Tom Salfield

Nathan Parker

Anna Waldman-Brown

Audrey Fox

Andrew Lamb

John Gershenson

Pierre-Alexis Ciavaldini

Barbara Kieslinger

Doc Martens

Tom Salfield

Pierre-Alexis Ciavaldini

Nathan Parker

Anna Waldman-Brown

Brynmor John

Vivien Roussel

Doc Martens

Anna Lowe

Driver Role

• Responsible to ensure progress is being made at an appropriate pace towards the strategic goal
• Recruit members to the taskforce, from the Member Council and elsewhere if appropriate
• Coordinate input from all members of the taskforce
• Keep all (contributing) members of the taskforce aware of what is going on and what needs to be done
• Coordinate with other drivers to ensure that dependencies between goals are considered
• Report on the progress of the taskforce to the Member Council, and ensure that the council is aware if progress is not happening at a good pace so that resourcing can be considered.
• The driver is responsible to ensure the role is adequately covered if he/she/they are unable to perform it for any length of time
• Declare any conflicts or convergence of interests with other roles they may have. All workstreams that require money will need to be brought to the council for a vote.
• Be a public face for this element of the Alliance’s work

​

Chair of Member Council Role

• Convenes the council, chairs meetings, and ensures voting rules are followed
• Coordinates with the Drivers to ensure progress is being made and dependencies between goals are discussed - point of contact for operations
• Able to act as the public face of the (group/alliance/ whatever we are)
• If at any time there is an even number of members of the council, the chair would have the casting vote (this does not apply at the moment)
• Help operationalise & gather resources that are needed for the different taskforces / workstreams

​

​

Coordination Mechanism: Regular Calls Proposal

Drivers plus Chair of Member Council

It is suggested that we schedule monthly calls (at least for the time being - frequency may reduce later) with the following objectives:

• Drivers will update everyone on progress in their taskforce and plans for the coming month (If a driver can’t make a monthly call, they are requested to nominate someone from the taskforce who can make it to give the update)
• Dependencies between taskforces will be discussed
• This mechanism also acts as the check that the overall direction of each taskforce stays in alignment with the common vision

Each taskforce can decide its own way of working - some may decide to schedule their own calls, others may work asynchronously.

Open Questions...

• What do we call ourselves?
• How do we structure ourselves longer term?
• How does the group of people who attended the summit bring in all the other people who we need to work with to achieve our common goal, including big companies?
• How does this group (of people who attended the Warsaw summit) relate to the group of people who are previously signed up members of the MakerNet Alliance (which includes some people who were at the summit, and more who were not)?
• How does this group relate to the Internet of Production Alliance that Wikifactory were already planning to set up?

​