Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Email list addresses (new info)

As of , emails to the OAGi email distribution list may use *@oagi.simplelists.com or *@i16.io with i16.io being the default. That means that any email sent to oagi.simplelists.com will be distributed with the corresponding i16.io address as the “from” address. Why the change?

  • Shorter (20 → 6 characters)

  • No Simplelists branding: We don’t care about this (as much as we may appreciate the service).

  • No OAGi branding: While OAGi branding would be appropriate, an unbranded domain allows for lists to be created for collaborating organizations (e.g., potentially KGA). By the way, Jim Wilson checked with Simplelists (the company) about this being appropriate. It is.

Key resources

Overview

Info

In this document group refers to one of OAGi’s organizational units (e.g., working groups, committees, boards) as well as any other specified set of people (e.g., IOF leaders).

OAGi staff creates, configures, and maintains email lists for groups. OAGi staff adds people to email lists (i.e., makes them a “subscriber”) as part of onboarding to a new group. OAGi’s email list service provides a way for list subscribers to see the names of other list subscribers. This enables group leaders to determine if a list is up to date. If a list is not up to date, email Member.Services@OAGi.org or fill out the email subscription form with details about how to correct the discrepancy.

Email lists

Info

Status Legend

  • Status
    colourGreen
    titlein use
    : The list is populated with subscribers and in used.

  • Status
    colourYellow
    titlepending USE
    : The list will transition to
    Status
    colourGreen
    titlein use
    once the associated group’s leader confirms that their group is ready to use it. In this state, the list “works”, but is not declared to be in use.

  • Status
    colourRed
    titlehold
    : The list is on hold.

List

Status

Authorized subscribers and senders; Notes

IOF Lists

General

iof@i16.io

Status
colourGreen
titlein use

  • Anybody may subscribe to this list, regardless of their organization’s membership in OAGi / IOF.

  • Authorized senders:

    • IOF Governance Board members

    • Will Sobel

    • Jim Logan

    • Melinda Hodkiewicz

    • Evan Wallace

    • Jinzhi Lu

    • OAGi staff.

  • This is an OAGi IOF announcement list (not a discussion list). This list shall not be used to announce group meetings. Working groups may want to offer a meeting applicable to a wider audience than their working group, in which case the meeting is not a working group meeting but an OAGi IOF meeting and therefore appropriate for

Discussion

iof-discuss@i16.io

Status
colourYellow
titlepending USE

  • See Notes 1 and 2

Governance Board

iof-gb@i16.io

Status
colourGreen
titlein use

  • Members are subscribers.

  • See Note 2

Technical Oversight Board

iof-tob@i16.io

Status
colourYellow
titlePENDING USE

  • Members are subscribers.

  • See Note 2

Architecture TG

iof-arch@i16.io

Status
colourGreen
titlein use

  • Members are subscribers.

  • See Note 2

Core WG

iof-core@i16.io

Status
colourYellowGreen
titlePENDING USEin use

  • See Notes 1 and 2

Maintenance WG

iof-maintenance@i16.io

Status
colourYellow
titlePENDING

  • See Notes 1 and 2

Production Planning and Scheduling WG

iof-pps@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

MTConnect WG

iof-mtc@i16.io

Status
colourYellow
titlePENDING USE

  • See Notes 1 and 2

Product Service System WG

iof-pss@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

Systems Engineering WG

iof-se@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

Supply Chain WG

iof-sc@i16.io

Status
colourYellow
titlePENDING USE

  • See Notes 1 and 2

Zero Defect Manufacturing WG

iof-zdm@i16.io

Status
colourRed
titlehold

  • See Notes 1 and 2

Material Science and Engineering WG

iof-mse@i16.io

Status
colourYellow
titlePENDING USE

  • See Notes 1 and 2

Connect Lists

Architecture Committee

c-arc@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

Mapping WG

c-map@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

Smart Manufacturing WG

c-sm@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

Score WG

c-score@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

connectSpec Review Team

c-cs@i16.io

Status
colourGreen
titlein use

  • See Notes 1 and 2

General

connect@i16.io

Status
colourGreen
titlein use

  • Anybody may subscribe to this list, regardless of their organization’s membership in OAGi Connect.

  • OAGi staff members are authorized to send to this list.

  • This is a OAGi Connect announcement list (not a discussion list). This list shall not be used to announce group meetings. Working groups may want to offer a meeting applicable to a wider audience than their working group, in which case the meeting is not a working group meeting but an OAGi / IOF / Connect meeting.

Other Lists

OAGi Policy Board

pb@i16.io

Status
colourGreen
titlein use

  • Members are subscribers.

  • See Note 2

U.S. TAG for ISO/TC 154

tag@i16.io

Status
colourGreen
titlein use

  • Members are subscribers.

  • See Note 2

🗒️ Note 1: Employees of organizations that have joined OAGi may subscribe. Note that working group participation is restricted to employees of organizations that have joined the working group with a couple of specific exceptions. An implication is that some may want to subscribe to a working group list even though their organization may not have joined the working group for the purpose of being kept informed about the working group’s activities.

🗒️ Note 2: A person is authorized to send to this list when sending from an email address they used for a subscription. For example, if Chester Nimitz is a subscriber with email address chester.nimitz@abc.com only, then Chester can send email to the list using that email address but not the email address chester.nimitz@gmail.com. Note that IOF participants are welcome to subscribe with multiple email addresses. So, in this example, Chester could subscribe with chester.nimitz@gmail.com as well.