Scribd Logo
Upload

Welcome to Scribd!

  • 343 views

    BE-WI-203-08-F15 Technical Checklist For Instrumentation - Control Systems

    Uploaded by

    mika cabello
    This checklist is for reviewing instrumentation and control system projects. It contains over 100 items to check across various categories including general project details, hardware, networks, supervision/controls, application software, system software/licenses, and miscellaneous items. The checklist ensures key aspects are defined such as the client's standards, system architecture, I/O requirements, networks, application functionality, testing plans, and more. Completing the checklist verifies all essential information is specified before proceeding with installation and commissioning of the control system.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd

    BE-WI-203-08-F15 Technical Checklist For Instrumentation - Control Systems

    Uploaded by

    mika cabello
    343 views4 pages
    This checklist is for reviewing instrumentation and control system projects. It contains over 100 items to check across various categories including general project details, hardware, networks, supervision/controls, application software, system software/licenses, and miscellaneous items. The checklist ensures key aspects are defined such as the client's standards, system architecture, I/O requirements, networks, application functionality, testing plans, and more. Completing the checklist verifies all essential information is specified before proceeding with installation and commissioning of the control system.

    Original Description:

    Original Title

    BE-WI-203-08-F15 Technical Checklist For Instrumentation - Control Systems.xlsx

    Copyright

    © © All Rights Reserved

    Available Formats

    XLSX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This checklist is for reviewing instrumentation and control system projects. It contains over 100 items to check across various categories including general project details, hardware, networks, supervision/controls, application software, system software/licenses, and miscellaneous items. The checklist ensures key aspects are defined such as the client's standards, system architecture, I/O requirements, networks, application functionality, testing plans, and more. Completing the checklist verifies all essential information is specified before proceeding with installation and commissioning of the control system.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Download as xlsx, pdf, or txt
    343 views4 pages

    BE-WI-203-08-F15 Technical Checklist For Instrumentation - Control Systems

    Uploaded by

    mika cabello
    This checklist is for reviewing instrumentation and control system projects. It contains over 100 items to check across various categories including general project details, hardware, networks, supervision/controls, application software, system software/licenses, and miscellaneous items. The checklist ensures key aspects are defined such as the client's standards, system architecture, I/O requirements, networks, application functionality, testing plans, and more. Completing the checklist verifies all essential information is specified before proceeding with installation and commissioning of the control system.

    Copyright:

    © All Rights Reserved
    Download as XLSX, PDF, TXT or read online from Scribd
    Download as xlsx, pdf, or txt
    of 4

    Checklist for Instrum.

    Control Systems
    Client init. sign date
    Project Originator
    Project no. Checker
    Drawing/doc. no. Lead Eng
    Item/tag/line no. Vendor/Contractor

    Checked by Remark no.


    (Y/N/NA) (see below)
    No. Description of item to be checked Orig. Check
    1. General
    1.01 - Are the client's standards and recommendations respected?
    1.02 - Extension to an existing control system or New control system ?
    1.03 - Control system migration project ?
    - Interfaces defined ?
    - Field survey conducted ?
    1.04 - Client's preference for PLC or DCS control system ?
    1.05 - Client's Preferred Vendor's available ?
    1.06 - Is the architecture of the system presented and approved by the client?
    1.07 - Is the complete architecture specified? (Packaged Units, Weighing systems, serial links
    to PLC's, SIS, Fire & gas, badge reader, barcode reader, MES, Custody Transfer systems,
    Tank gauging Systems, CCTV systems, …) ?

    1.08 - Does the control system require telecom and/or Internet connection for remote access
    and maintenance ?
    1.09 - Is the control system a part of a safety system?
    1.10 - Is the safety system integrated with the control system / same brand ?
    1.11 - Is the redundancy in line with the client requirements ?
    - I/O; controller; network; ...

    2. Hardware
    2.01 - Customer standard materials defined if any ? I/O cards; controllers ….
    2.02 - I/O counted for field instruments, MCC, VFD, …. SIS
    2.03 - Amount of Eex and Non-Eex control system I/O defined ?
    2.04 - Galvanic isolation requirements ? per channel, per card , …
    2.05 - Pulse input requirements ?
    2.06 - Conventional and/or remote I/O for Controls / Conventional hardwired for SIS ?
    2.07 - Are all analog field instruments powered by the control system?
    2.08 - Are the contact inputs active or passive ?
    2.09 - Are the digital outputs powered by the control system or by an other external power
    supply?
    2.10 - EEx galvanic isolators/barriers part of control system or separate ? SIL and/or HART
    compliant ?
    2.11 - Interposing relays part of control system or separate ?
    - relays connected to DCS / SIL compliant relays
    - relays to field devices (solenoids)
    - relays to MCC / VFD
    - relays to other control systems

    2.12 - Marshalling cabinets part of control system ?


    2.13 - System cables part of control system ? Connector, screw, ... type defined?
    2.14 - Signal types defined per make/type of instrument ?
    E.g. level switch Eexi Namur in field OR
    signal converter in I/O room Non Eex dry contact to control system
    2.15 - Wiring block diagram available ?

    ________________________________________________________________________________________ Page 1 of 4
    BE-WI-203-08-f15-rev0
    2.16 - Location and sizes of cabinets defined and agreed with Customer ?
    - Double access; wall mounted ? Side panels or not ? Plinth ?
    2.17 - Spare defined ? Installed spare and spare space
    - Hardware: I/O ; I/O cards; barriers, terminals, crosswiring ducts, cabinets; ...
    - Controller processing spare capacity
    - Licenses - installed spare

    2.18 - Power requirements defined ? 220Vac; 24Vdc; conventional & UPS ; redundancy…
    2.19 - Power distribution by Control system Vendor ?
    2.20 - Defined site location and environmental conditions ?
    2.21 - Defined HVAC requirements ? Separate or part of control cabinets ?
    2.22 - Defined wire color coding and wire tagging standards ?
    2.23 - Defined cable entry (top/bottom ) ?

    3. Networks
    3.01 - Connection with bus systems ? Fieldbus, Profibus, …. Remote I/O
    3.02 - Connection with Safety System ?
    3.03 - Connection with other systems ? Barcode scanners, MMI, …
    3.04 - Connection with other control systems ? PLC, Batching controller, … (Profibus,
    Modbus, Ethernet …)
    3.05 - Connection with Tank gauging systems ?
    3.06 - Connection with Analyzer systems ?
    3.07 - Network cabling in field and I/O rooms defined ? Conventional and/or Fiber Optic ?
    3.08 - Network Topology defined ? Ring or star ; redundancy requirements defined ?
    3.09 - Fiber Optic cable routing defined ?
    3.10 - In case of existing FO guard tube : Surveyed if still free to pull extra fibers ?
    3.11 - Fiber Optic cable; splice boxes; ...: material and services incl. testing : by third party or
    control system Vendor ?
    3.12 - Delivery of patch panels, patch cords, network switches, CAT5 network cabling
    defined ?
    3.13 - Amount and type of data exchange defined per communication link ?

    4. Supervision & Controls / System software


    4.01 - Identified amount and location of system supervision and controls?
    - Field operation (MMI and/or full functional supervision)
    - Control room operations
    - Maintenance

    4.02 - Computer cabinet(s) ? KVM extenders and cabling ? Delivery by ?


    4.03 - Configuration station(s) specified ?
    4.04 - Configuration software and licenses specified ?
    4.05 - Sufficient configuration Stations for project duration of project ?
    4.06 - Control system furniture ?
    4.07 - Shutdown panels and/or MOS, start-up and bypass switches ?
    4.08 - Time synchronization required ?
    4.09 - Printers ?
    4.10 - AMS ?

    5. Application Software
    5.01 - Amount and type of graphics defined ?
    5.02 - Delivery of source code application software ?
    5.03 - Populating of databases included ?
    5.04 - Man Machine Interface functional requirements defined ?
    5.05 - SIS philosophy, overrides, emergency shutdown, F&G defined ?
    5.06 - Reporting requirements defined ?
    5.07 - Case PLC / SCADA :
    - Alarm philosophy and reset requirements defined ? In controller or by SCADA
    - Signal characterization requirements defined ? In controller or by SCADA

    ________________________________________________________________________________________ Page 2 of 4
    BE-WI-203-08-f15-rev0
    5.08 - (Multi-) language requirements defined ? Operator interface language ?
    5.09 - (Pharma/Food) Validation requirements ?
    5.10 - Case Batch application - Check requirements and complexity:
    - Definition of complexity / custom made or use of standard batch software
    - Definition of amount and type operations and parameters

    5.11 - Case Batch application


    - Equipment scheduler & claim mechanisms ?
    - Recipe scheduling system ?

    5.12 - Case Batch application


    - Master recipe resizing to control recipe ?
    - Reporting per batch?

    5.13 - Line-Up and contamination check ? Within Control system or separate ?


    5.14 - Pigging ? Within Control system or separate ?

    5.15 - Case existing AMS: Who updates the AMS data for the project ?

    6. System Software & Licenses


    6.01 - Is the system software proven or contain custom made developments?
    6.02 - User and password management system specific of maybe by Customer server?
    6.03 - Does the system allow virus scanner and automatic software updates?
    6.04 - Sequence of Events and time stamping SIS & DCS defined?
    6.05 - Are the software versions of new control system (extension) compatible with existing
    system(s) ? Should the existing system require migration ?
    6.06 - Should the existing system require migration ?
    6.07 - Can existing licenses be (partly) used for the project or license cost to be fully
    supported by the project budget.?

    7. Miscellaneous
    7.01 - Are the legal and required certificates available ?
    7.02 - Are the acceptance tests described in detail?
    7.03 -FAT, SAT - x% checking ; simulation ; …
    7.04 - Config and testing of communication links ; availability of third party controllers - x
    % checking ; simulation ; integration testing …
    7.05 - Intermediate FAT sessions of structural parts?
    7.06 - Services/Unit rates for Pre-commissioning, Commissioning and start-up
    7.07 - Availability of data and hardware for legacy control systems which should be modified ?

    7.08 - Project planning and milestones for documents, hardware and software?
    7.09 - Modification on control systems in service:
    - hardware can be modified in service or needs shutdown ?
    - loops can be connected in service on spare channels or needs shutdown ?

    7.10 - Training services?


    7.11 - Maintenance services?
    7.12 - Software backup for complete duration of project?
    7.13 - Skilled key resources ?
    7.14 - Meetings and MOM included by control system vendor ?
    7.15 - MTBF and reliability requirements defined ?
    7.16 - Life cycle data available for control system and parts?

    8. Documents
    8.01 - SIL classification available ? Made by ?
    8.02 - Safeguarding philosophy available ? Made by ?
    8.03 - Cause & Effect matrix available ? Made by ?
    8.04 - Process control philosophy available ? Made by ?

    ________________________________________________________________________________________ Page 3 of 4
    BE-WI-203-08-f15-rev0
    8.05 - Is the required functionality known, included and specified in the system description?

    8.06 - Is the required functionality and safety known for packaged unit instruments connected
    to the control / SIS system.? Made by ?
    8.07 - List of documentation by control system Vendor ?
    8.08 - Compliance and deviation list by control system Vendor ?
    8.09 - Reference documents list updated and attached to specification ?
    8.10 - Control system specification updated for purchase according to quote/order ?

    Lessons learned previous projects


    9.01
    9.02
    9.03
    9.04
    Please define special items to be checked
    10.01
    10.02
    10.03
    10.04
    Note: this sheet shall be stapled to the check print and filed in the appropriate hardcopy folder
    REMARKS & HOLDS
    Released
    No. Description Date By

    ________________________________________________________________________________________ Page 4 of 4
    BE-WI-203-08-f15-rev0

    You might also like