PERA provides a foundation for management of Projects and Enterprise Programs (consisting of multiple projects). This foundation consists of:
These basic concepts are shown diagramatically below.
The PERA Enterprise Life Cycle is divided into 8 Phases, and each Phase is divided into People, Facilities and Systems, as indicated in the following diagram
PERA MASTER PLANNING
PERA provides a Master Planning Methodology which is used during the Study Phase at the beginning of the Enterprise or Project, and is repeated.
Management of Enterprise Integration projects requires merging expertise from many disciplines, which necessitates a naming system for these disciplines (called Roles)
Although integration projects have much in common across all industries there are differences that must be understood and accommodated, which requires a naming and definition system for industries.
Good project management practice requires strong "Phasing" of project activities, so project deliverables are well defied and their timing is coordinated, which requires clearly defined Project Phases and the Deliverables and timing for each.
Different approaches and tools are needed during each phase, beginning with Business Plans and Enterprise Master Planning in the Study Phase of the Enterprise, and continuing to Operations, and evenutally Enterprise Renewal or Dissolution, which requires the choice of consistent methods and tools if information is not to be lost and time wasted as each phase "hands off" to the next.
PERA is the only Enterprise Reference Architecture that is designed for all industries (a Type 1 Geram), and provides a structure for addressing all of the requirments above.
How do these Principles translate to real Project Execution ?
PERA Provides an coherent overall Project Strtucture. It begins with Definition
of the Facility, Human Roles(e.g. Engineering Discipline), and Control and Information
These of these 3 are in turn divided by Enterprise Phase.
1) Facility is subdivided by Area/Unit/Equipment Class.
a. Equipment Classes are associated with Disciplines Each equipment class has only one Lead Discipline. The Lead Discipline defines and manages the Specification. Specifications can be for Human Roles, Systems, or Equipment. The line of automation establishes the balance between these 3 (which is defined during Preliminary Engineering).
b. For each Facility Equipment type there may (or may not) be a narrative specification (during Conceptual Engineering), a Specification Sheet (during Preliminary Engineering and each subsequent Phase).
c. Each equipment type has a “Level” in the Enterprise Architecture (although a few can have more than one).
2) Human Roles are broken down into Work Processes, Work Flow Diagrams, Tasks, etc.
a. ISA 108 has defined a standardized breakdown for use in preparing their standards (using BPMN 2). It may be as good as any, or you may know a more authoritative one.
b. For each Position Description there should be a definition of which Roles are assigned to that Position.
c. Roles are defined by one Lead Discipline, but may be assigned to a person in any Position who has the necessary skills and certifications.
3) Control and Information Systems are broken down into Hardware and Software.
Software is sub-divided into programs, subroutines, databases, data dictionaries, etc..
a. Again there are standard terminologies and conventions. IBM’s are probably as good as any.
b. ISA 95 has defined some standard Industrial Systems, as well as Architectural Levels where these reside.
Computer and Network Hardware is organized as Equipment (see “1” above)
All of the above may be associated using “schematic” diagrams that are defined at differing degrees of detail during each Phase. For example:
a. Conceptual Engrg: PFD (Process Flow Diagram)
b. Preliminary Engrg: P&ID (Piping and Instrumentation Diagram)
c. Detail Engrg: Piping Isometrics, Installation Details
d. Construction: Shop Fabrication Drawings (e.g. spool piece drawings, weld diagrams, stress drawings)
2) Human Roles
a. Conceptual: Organization Charts
b. Preliminary: High Level BPMN “swim lane” Diagrams
c. Detail: Work Flow Diagrams
d. Implementation: BPMN 2 “executable” Diagrams (with BPM system)
a. Conceptual Engrg: Enterprise Systems Architecture Diagrams
b. Preliminary Engrg: CIAD (Control & Information System Architecture Diagrams)
c. Detail Engrg: Loop Diagrams, DCS and PLC configurations
d. Construction: Operator Display Graphics, Trend Displays
The above is not meant to be an exhaustive set, but gives an indication of the kinds of Schematic Diagrams that may be used to show how Facilities, People and Systems are related.
A structure to support all of the above exists in the Engineering Workbench, including a “starter set” of a thousand Product Classes, and several thousand Products.
by Gary Rathwell © reserved
Back to PERA Home Page