Standard profits: Make2Pack and ISA88 
Recent Posts
- European events, opportunities, review ISA88 series
- PackML ISA Technical report from Make2Pack is finally available!
- Skills gap: Standards, workforce development, and Automation Federation
- Proposed 2009 calendar for Make2Pack Part 5, related meetings
- Dayton Day 3 and OPC: Data integration, instruments, pharmaceuticals
- Dayton Day 2: Interactions with ISA88 Part 1, more rework, glad we didn’t wait
- Dayton meeting Day 1: More help, churning through automation models, beverage
- Sneak peak at Dayton from last week: Automation object discussion, synonyms
- Next Dayton meeting agenda: ISA88 Working Draft 5, phase interface, automation object, more
- ISA88 Part 1 meeting update: A stronger “Batch” standard, good for other industries, too
Recent Comments
- Willie Lötz on PackML ISA Technical report from Make2Pack is finally available!
- Francis on Dayton Day 3 and OPC: Data integration, instruments, pharmaceuticals
- Francis on ISA88 Technical report discussion uncovers new ground for future standards update, Part 1 of 4
- Francis on Is that a Sequence or is that a Recipe? The answer is YES!
- Francis on What is Recipe Control?
Most Commented On
- Mode is a many-splendored thing (6)
- It’s elemental Mr. Watson: control system terms (2)
- Dayton Day 3 and OPC: Data integration, instruments, pharmaceuticals (1)
- ISA88 Technical report discussion uncovers new ground for future standards update, Part 1 of 4 (1)
- PackML ISA Technical report from Make2Pack is finally available! (1)
Archives
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
Blog
Link This | Email this | Blog This | Comments (0)
Standards comments: A few tips to help get your point across
Here are a few ways to help increase the chances that your voice will get heard in a standards committee comment and review process.
I’ve been involved in standards efforts for a long time. As stated previously, standards can be a great way to encourage best practices, efficiencies, and ultimately interoperability. I have a huge amount of respect for those who devote their time and energies to standards formation and comments, even if or when I don’t exactly agree with what they’re saying.
Here a few observations that may help next time you offer a standards committee some advice on something that’s out for comment:
-PARTICIPATE!
-Use forms provided, following rules and meeting deadlines.
-Be as specific as possible about the change and why it is needed.
-Do not provide open-ended comments with no resolutions.
-Highlight the text that you’d like changed.
-Offer exact replacement text in the language of standards, if possible.
-Offering a marked up document for wider changes (in addition to forms) may help.
-Match the degree of changes offered to the time in the process. (More toward the end, changes are likely to be more clean-up of smaller details. Broader changes are better addressed earlier, if you can find someone involved on the committee to work with, if you’re not on the committee yourself.)
If your views are rejected, or accepted only in part, those involved should give a brief explanation of why. Please don’t ever take any of it personally (a lot goes on that you may have missed), but do ask those involved for more explanation, if you don’t understand why. Doing so may mean that next time your comments may be more useful. And again, and as always, thanks for everyone’s efforts.
Here are a few ways you can get involved in various efforts.
Get involved with ISA standards
WBF working groups
Here is a list of some of the other ISA standards now in development.
Have you ever offered advice in a standards process? Have you ever made comments to a standard? Do you have additional advice? Please comment below.
Standards comments: A few tips to help get your point across
July 6, 2008
Here are a few ways to help increase the chances that your voice will get heard in a standards committee comment and review process. I’ve been involved in standards efforts for a long time. As stated previously, standards can be a great way to encourage best practices, efficiencies, and ultimately interoperability. I have a huge amount of respect for those who devote their time and energies to standards formation and comments, even if or when I don’t exactly agree with what they’re saying.
Here a few observations that may help next time you offer a standards committee some advice on something that’s out for comment:
-PARTICIPATE!
-Use forms provided, following rules and meeting deadlines.
-Be as specific as possible about the change and why it is needed.
-Do not provide open-ended comments with no resolutions.
-Highlight the text that you’d like changed.
-Offer exact replacement text in the language of standards, if possible.
-Offering a marked up document for wider changes (in addition to forms) may help.
-Match the degree of changes offered to the time in the process. (More toward the end, changes are likely to be more clean-up of smaller details. Broader changes are better addressed earlier, if you can find someone involved on the committee to work with, if you’re not on the committee yourself.)
If your views are rejected, or accepted only in part, those involved should give a brief explanation of why. Please don’t ever take any of it personally (a lot goes on that you may have missed), but do ask those involved for more explanation, if you don’t understand why. Doing so may mean that next time your comments may be more useful. And again, and as always, thanks for everyone’s efforts.
Here are a few ways you can get involved in various efforts.
Get involved with ISA standards
WBF working groups
Here is a list of some of the other ISA standards now in development.
Have you ever offered advice in a standards process? Have you ever made comments to a standard? Do you have additional advice? Please comment below.
Posted by David Chappell on July 6, 2008 | Comments (0)
Advertisement
Advertisements
