So what can ISA-95 do for ME?

I had a conversation the other day, in which somebody made the comment “well there is the S95 standard, but it really doesn’t do anything for end users…” [I think I just heard screams of pain].

It is true that the ISA-95 Standard is, well a standard… as such, it is geared to bring commonality to the way that we do things.  Furthermore it is broad to allow for flexibility within the space (because not all manufacturers are the same).  As a standard it has been adopted [or used as a marketing point] for Vendors that sell/develop software products, which allow for open systems that can/should be able to communicate to other systems.

However, there are additional ways that end users can benefit or use the standard directly.  First, make use of the Hierarchy Model outlined in Part 1.  Use this model to determine ownership of systems and dividing lines between groups within your organization (such as Engineering and IT).  Second, use the standard to help define user requirements for software design or specifications.  The standard provides a good listing of all activities and definitions that can help identify what might be needed and in scope verses not needed [or needed yet].  In the next posts I will go deeper into each of these.

Quick Overview of the Parts of The ISA-95 Standard

The ANSI/ISA-95 Standard is currently divided among 5 parts with plans for a 6th part. Each of these “Parts” has a different focus, and with roughly 300 pages each, that can seem confusing. I put together a quick video that will [hopefully] give you a taste for the contents of each and how they relate to each other.  Over the next several weeks, I will dive deeper into each Part and give more detail on the contents and why you should become familiar with the Standard.