Consulting Services

Pre-Engineering Phase - Project Kick-off
ITmatic' unique consulting division will be responsible for the design and specifications for the project.
For the specific project the following services have been offered:
- • Develop user requirements document
- • Generate plant hierarchy
- • S88 Plant Modeling
- • Physical Plant to Device Modeling
- • Generate device list
- • Develop standards and specifications
- • Group Control and Function Development
- • OEM Specification Documentation
- • OEM FAT and Quality Management
- • Generate FDS
- • Specifications and Procurement
- • Panel Design
- • C1 to C5 Documentation
- • Quality control
However the concept behind the following offering is that on the first project ITmatic will develop a generic standards and specifications document which can then be re-used on future projects or OEM multi project environment. Should this approach be accepted it will reduce costs and design time on future projects as the standards and specifications only need to be reviewed and not re-invented. The figure below demonstrates the process of standards determination. When doing standards review it can quite easily be determined what effect if any the input needs will have on the outcome.

The generic standards and specifications document will specify to the level that another company will be able to design a future plant to the same standards and specifications as previous projects. Advantages of developing a common project standard Developing the standards and specifications for a plant helps to reduce costs by:
- • Shortening project development
- • Extending the products competitive life time
- • Increasing the value through the life time of the product

Additionally if a common standard is applied to all projects it is easier and cheaper to upgrade the different sites control systems when new versions are released or if new concepts have been developed and need to be implemented.
Generic documentation Assumptions:
- • PIDs are available
- • GA drawings are available
- • HAZOP is complete and safety requirements have been determined
Generate device list:
- • Using naming convention create device list with required fields
S88 model Constant:
- • Explanation of procedural & physical model
- • Explanation of relationship between physical & procedural model
- • Explanation of how S88 relates to PCS7
Functional Design Specification:
- • Narratives
- • Sign off requirements for FATs, Hot & Cold commissioning
- • C1 to C5 Process Documentation
- • Minimum information requirements for devices and other S88 physical model levels
Standards Review and Design:
- • FB & Templates To be reviewed with End User and Client
- • Basic FBs & Templates
- • Auto/manual philosophy
- • Minimum display requirements on face plates
- • Generic symbols
- • OEM Interfaces
- • Group control philosophy
- • Generic alarms philosophy
- • Generic trending philosophy
Standard KPI & OEE reporting PLC Hardware requirements:
- • Generic network architecture
- • PLC hardware specifications
- • Communication protocols
Electrical information to be reviewed:
- • Develop generic drawings for buckets (If this is done by the client the interface between the FBs and the IO of the bucket must be verified)
- • Local stop/start specifications
- • Wiring specifications
Panel Design:
- • PLC Cabinet design (Wiring diagrams and GA’s)
- • Cabinet Supply
- • Field Junction Box design (Wiring diagrams and GA’s)

QC:
- • OEM FAT & Quality Management
- • Specification implementation
- • Installation
- • Commissioning
Other Deliverables:
RFI Process for Vendor Management
In terms of the future state we envisage various workshops will be required to ensure we capture all requirements. In these workshops a blue print will be developed as to what is needed in terms of the automation environment. It will be difficult not to review supplier offerings at this stage.
- • Full Clarifying and Integration to all third Party Vendor Systems
- • Envisage process followed will be by means of various workshops to discuss requirements and to simulate its working to client (Thin Slice)
Once standards, typicals and architecture have been developed in future it should only be required to specify the scope of works i.e. to define how many devices of respective types are required to be engineered which will result in significant savings to the client.


