Middle East SMEC Oil & Gas Solutions LLC info@smecong.com +971 54 549 6420

India SMEC Automation Pvt Ltd sales@smecong.com +91 86060 47714

Resource Centre

Engineering Checklists

Checklists turn technical content into buyer-ready inputs. Each checklist should reduce missing information before quotation or engineering starts.

Explore the relevant engineering page or send a technical requirement. Recommended RFQ inputs: project/asset, existing OEM/model, scope, drawings or specification, required date, site location, and any shutdown/mobilization constraint.

E-House enquiry checklist

What an estimator needs before an E-House or modular electrical room can be priced. Send what exists; a partial list is still worth reviewing.

Electrical scope

  • Single line diagram, or the intended distribution arrangement
  • Voltage classes and system earthing
  • Fault level and duration at the incomer
  • Equipment list: switchgear, MCC/PCC, drives, UPS/DC, transformers
  • Load list, with duty and starting method for motor loads
  • Control and automation scope inside the building

Building and environment

  • Internal arrangement or space envelope, and access requirements
  • Ambient temperature range and solar loading
  • Area classification, if any part is in a hazardous zone
  • Ingress protection, fire and blast requirements
  • HVAC duty, redundancy and control philosophy

Transport and site

  • Transport route limits: weight, width, height, lifting arrangement
  • Site location and installation interfaces (cable entries, earthing, foundations)
  • Whether site installation, termination and commissioning are in scope

Project

  • Project stage: FEED, tender, execution, operating, shutdown
  • Required delivery date and any shutdown or mobilization window
  • Applicable standards and client specifications
  • Documentation, FAT and witness requirements

Gathered what you can? Send it with the enquiry — an engineer reviews the scope and replies.

Control system migration readiness checklist

Before a PLC, SCADA or DCS migration can be scoped, these are the things that decide whether the existing installation can be kept and how the cutover is planned.

Existing system

  • Make, model and firmware of the existing controllers and HMI/SCADA
  • Application backup: program, tags, graphics, historical configuration
  • Spare-parts position and known obsolescence notices
  • Fault and downtime history, with the events that triggered the review

Field and I/O

  • I/O list with signal types, ranges and locations
  • Condition and age of field wiring, marshalling and terminations
  • Whether existing cabinets, racks and field wiring are to be retained
  • Instrument and final-element list, with anything already scheduled for replacement

Interfaces

  • OEM packages and third-party systems that must remain connected
  • Protocols in use, and which are available on the new platform
  • Safety system boundary, and whether it is in or out of scope
  • Historian, reporting and any remote-monitoring interfaces

Cutover

  • Available window: shutdown, turnaround, phased or hot cutover
  • Acceptable loss of view and loss of control durations
  • Fallback and rollback plan, and who authorises it
  • FAT scope, site acceptance criteria and operator training needs

Gathered what you can? Send it with the enquiry — an engineer reviews the scope and replies.

01

Related pages

Submit RFQ