Live from WBF 2008-- Paul Nowicki beams up

March 25, 2008
Using slides of different generations of the Star Trek Enterprise, and with a nod to Star Wars (Long, long ago...) Rockwell Automation's Paul Nowicki began his update of ISA88.01-- Updated for Today's Best Practices. Part 1: Models and Terminology – Reaffirmed in 2005 Relevant Correct Used by the community Update Objectives Update content of S88.01 to clarify issues that have surfaced in the last 10 years When are we done? Committee ballot Spring 2008? Updates to reflect today's practices... ...
Using slides of different generations of the Star Trek Enterprise, and with a nod to Star Wars (Long, long ago...) Rockwell Automation's Paul Nowicki began his update of ISA88.01-- Updated for Today's Best Practices. Part 1: Models and Terminology – Reaffirmed in 2005 Relevant Correct Used by the community Update Objectives Update content of S88.01 to clarify issues that have surfaced in the last 10 years When are we done? Committee ballot Spring 2008? Updates to reflect today's practices... General Model Clarification Clarification of Equipment & Control Modules Collapsibility and the “Magic” better defined Provisions for Part 5 Modes and States Alignment with S95 Conformance First: more intuitive figures! Clarity on Basic Control Basic Control…where? Executed by control modules Equipment modules, units, and process cells may perform basic control because they contain or make use of control modules. Control modules can direct commands to other control modules if contained or some way referenced. Explaining the Magic! (and I don't think this means using "handwavium") "Collapsibility" = Flexibility in the Standard Defining Collapsibility Rules:

Procedural Element Level

Rules for Omitting

Process Cell Procedure

May be omitted.

Unit Procedure

May be omitted.

Operation

May be omitted

Phase

Recipe phases may be omitted

Equipment phases may not be omitted

NAME

Minimum Procedural Element Attributes

DESCRIPTION

ID

Provides unique identification.

Version

Identifies the version of the procedural element.

Version Date

Identifies the date and time that this version was created or modified.

Approval Date

Identifies the date and time that this version was approved.

Expiry Date

Identifies the date and time that this version expires and should no longer be used.

Author

Identifies the person or system that authored this version. (e.g., J. Smith).

Approved By

Identifies the person or system that approved this version.

Description

Describes the function that is achieved through execution of the procedural element.

Level

Indicates the level of the procedural element.  For example procedure, unit procedure, operation or phase.

Mode

Indicates the current mode of the procedural element.

State

Indicates the current state of the procedural element.

Procedure and Equipment  
Type of Procedural Element

Procedural element strategy options

Strategy defines lower level PE orchestration

Strategy can reference another PE

Strategy can reference a Process Task Strategy

Recipe Process Cell Procedure

Yes

Equipment Process Cell Procedure

No

Recipe Unit Procedure

Yes

Equipment Unit Procedure

No

Recipe Operation

Yes

Equipment Operation

No

Recipe Phase

No

Equipment Phase

No

Equipment Process Cell Procedure

Yes

No

No

Equipment Unit Procedure

Yes

No

No

Equipment Operation

Yes

No

No

Equipment Phase

No

No

Yes

Opening the Door for WG 5! Assessment for Conformance... Nowicki finished by giving a report card on the percentage of how many meetings the most active members of SP88 have attended, coupled with a plea to join the committee.