# Orlando OMAC HMI Meeting Notes: January-20-04

## Attendees:

Bill Flere Siemens

Bob Tain Okuma

Brian Sides Okuma

David Brown ROY-G-BIV

David Odendahl Boeing

Gene Moss GE Fanuc

Jerry Yen GM Power Train

John Michaloski NIST

Nat Frampton Real Time Development

Sid Venkatesh Boeing

Terry Gustafson LCMS

## Announcement:

**A new Yahoo! Group "omachmi" has been created, so please sign up!**

\* Yahoo! omachmi group information:

Group name: omachmi

Group home page: <http://groups.yahoo.com/group/omachmi>

Group email address: <omachmi@yahoogroups.com>

These meeting notes will be posted to this web site.

## Minutes:

The meeting discussed the data specification, Style Guide, end user
input, and OPC update.

1)  **Data Item Definition Specification**

```{=html}
<!-- -->
```
a.  The groups main goal in the short run is to produce a Data Item
    Definition Specification deliverable.

b.  The Data Item Definition Specification should clearly define the set
    of OMAC endorsed data items expected to be produced from OMAC
    compliant controls.

> *There should be a OMAC Stamp of Approval for compliance*. HOW?

c.  This specification defines what the data items are but NOT how to
    actually get those data items or how those data items are
    represented in a technical manner. For example, \'Absolute Axis
    Position (X,Y,Z\...) - the Absolute Position is defined as\... The
    units of this data item are either mm or inch.\'

d.  The previous XML effort has not been abandoned, but is on hold until
    we can produce the Data Item Definition document.

e.  The Data Item Definition Specification is to be completely
    technology agnostic as there are many unresolved issues that are
    associated with the technology side.

> **Action Items:**
>
> John Michaloski complete Data Item Definition Specification by March
> 1.
>
> Jerry Yen to determine how OMAC Stamp of Approval can be done, by next
> telcon.

2)  **Style Guide**

```{=html}
<!-- -->
```
a.  Using the Data Item Definition Specification, a style guide should
    be produced that associates each data item to screen configurations
    with the idea being that if HMI\'s support the recommended OMAC
    screen style guide, then operators will at a minimum be guaranteed
    that they will have a given set of screens and that each screen will
    contain a given set of data items.

b.  However, the actual visual layout WILL NOT be specified as this may
    move us onto the religious battle field which we do not want to do.

c.  Leverage existing work. GM will document, based on OSACA style
    guide, for evaluation and discussion.

> **Action Items:**
>
> Jerry Yen provided GM style guide. Post to omachmi Yahoo group.

Sid V. donate Boeing simple HMI spec.

3)  **Garner More End-User Participation**

> This is an extremely important action item to meet for if it is not
> met, action items #1 and #2 will be a waste of time and effort. We
> need to solicit end users and machine tool builder user-groups for
> participation in the OMAC group. Several machine tool groups to
> approach are AMT and a Japanese Builder Group (did not get the name on
> this).
>
> **Action Items:**
>
> Volunteers to lobby and market, after we have something to market .

4)  **Discussion on OPC**

> OPC now has command API. After completion of Data Item Definition
> Specification, OMACHMI Group needs to investigate whether the whole
> HMI can be implemented with OPC.

## Next Meeting

John Michaloski will schedule a telecon will be scheduled for the March
2004 time-frame. Agenda TBA.