IV.0Constraints IV.1.Project Constraints

IV.2.1.Hardware Standards and Preferences

Solutions based on other hardware may be acceptable, but must be identified, justified, and approved at the earliest possible point within the project. Conformance to project standards is verified as part of Design Qualification and/or Acceptance Testing and/or Installation Qualification.

IV.2.2.COTS Software Standards and Preferences

The following table identifies corporate and/or site and/or process area and/or project standards for Process Control System Commercial Off-The-Shelf (COTS) software:

Role	Standard(s)	Comments
I/O Bus Configuration
Controller Configuration and Programming
OIT Configuration and Programming
PC Operating System
Controller-SCADA Interface
SCADA
HMI
Process Simulation
Batch/Recipe Management
Process Historian
Manufacturing Execution System
Relational Database
Custom Application Programming

{Complete the above table. Clearly indicate which roles are, and are not, applicable to the current project.}

Solutions based on other COTS software may be acceptable, but must be identified, justified, and approved at the earliest possible point within the project. Conformance to project standards is verified as part of Design Qualification and/or Acceptance Testing and/or Installation Qualification.

IV.2.3.PCS Configuration and Integration Standards

To help reduce validation, training, and maintenance costs, a set of corporate and/or site and/or process area and/or project standards are employed. Standards for Process Control System (PCS) configuration and integration include:

• 
  Basic design principles for Process Control Systems,
  
• 
  PCS terminology and naming conventions,
  
• 
  PCS documentation principles,
  
• 
  Basic configuration of PCS hardware and software components, and
  
• 
  General network and IT standards.
  

PCS Configuration and Integration Standards are {NOTE: If Configuration and Integration standards do not exist, development and approval of project-specific standards may be part of PCS Functional Specifications.}. Application of alternate standards may be acceptable, but must be identified, justified, and approved at the earliest possible point within the project. Conformance to project standards is verified as part of Design Qualification and/or Acceptance Testing and/or Installation Qualification.

IV.2.4.PCS User Interface Standards

To help reduce validation, training, and maintenance costs, a set of corporate and/or site and/or process area and/or project standards are employed. Standards for Process Control System (PCS) User Interfaces include:

• 
  Basic design principles for PCS User Interfaces,
  
• 
  PCS display libraries, symbols, fonts, and colors,
  
• 
  PCS display classes (e.g., Overview, Process Unit, Control Popup), standard layouts, and navigation,
  
• 
  Alarm Management and Annunciation, and
  
• 
  User Interface security.
  

PCS User Interface Standards are {NOTE: If User Interface standards do not exist, development and approval of project-specific standards may be part of PCS Functional Specifications.}. Application of alternate standards may be acceptable, but must be identified, justified, and approved at the earliest possible point within the project. Conformance to project standards is verified as part of Design Qualification and/or Acceptance Testing and/or Installation Qualification.

IV.2.5.PCS Programming Standards

To help reduce validation, training, and maintenance costs, a set of corporate and/or site and/or process area and/or project standards are employed. Standards for Process Control System (PCS) Programming include:

• 
  Basic design principles for PCS Programming,
  
• 
  Program identification and version control,
  
• 
  PCS object naming conventions,
  
• 
  PCS code format and commenting,
  
• 
  Program flow control,
  
• 
  User Interface, and
  
• 
  Error Handling.
  

Application of alternate standards may be acceptable, but must be identified, justified, and approved at the earliest possible point within the project. Conformance to project standards is verified as part of Design Qualification and/or Acceptance Testing and/or Installation Qualification.

IV.2.5.1.Controller Programming

PCS Controller Programming Standards are {NOTE: If programming standards do not exist, development and approval of project-specific standards may be part of PCS Functional Specifications. Project-specific standards may be based on Systems Integrator internal quality control standards.}.

IV.2.5.2.SCADA Scripts and Custom Applications

PCS SCADA Scripts and Custom Applications Programming Standards are {NOTE: If programming standards do not exist, development and approval of project-specific standards may be part of PCS Functional Specifications. Project-specific standards may be based on Systems Integrator internal quality control standards.}.

Download 396.6 Kb.

Share with your friends: