Our design methodology will adopt industry best practice for programmable electronic systems. The software will be developed around the standard ‘V’ development lifecycle, as depicted below:

 

The distinct stages of our system design methodology are outlined below

This stage involves the issue of the User Requirements Specification (URS) by the client. This document will detail the user requirements in terms of overall system functionality, operational requirements, maintainability and performance requirements. It will also identify any specific safety requirements. Typically the client’s tender documents will constitute a significant part of the URS. This will be supplemented with any detailed functional, operational, performance or safety requirements such that work can commence on the Functional Design Specification

The Functional Design Specification (FDS) translates User Requirements into a functional description of how the System will operate. The FDS establishes the functional baseline for the system. It lays out the basic description of how the SCADA system will monitor and control plant equipment.

System Architecture including Hardware, Software, OS and Communications.

High Level description of all functions to be provided by the system.

Performance Requirements for the system.

Identification of redundancy provisions to be made in the system.

Identification of failure modes to be catered for within system design.

Human Interface requirements.

Generation of System I/O Schedule.

Definition of interface requirements.

Details of Fault Logging Requirements.

Details of User Definable Parameters.

Details of user security and control priority mechanisms.

Review of System Maintainability Requirements.

System design requirements to meet any specific safety requirements.

The Functional design Specification will be submitted to the client for approval, prior to commencement of any detailed design works.

The Software Design Specification (SDS) will expand on the high level design issues covered in the Functional Design Specification, in order to produce a detailed software design for the overall system. The SDS will cover:

Structured Software Analysis and Design.

Software Architecture / Identification of software modules required.

Definition of system variables and data structures / address allocation.

Detailed definition of system interfaces and data to be exchanged.

Production of detailed fault log design requirements.

The SDS is not normally issued to the client for formal approval, but can be inspected by the client on request

Software Module Design will involve the design of the various software modules as directed by the SDS. The breakdown of the system into modules makes the design more flexible, easier to troubleshoot and easier to maintain / modify in the future.

Each module will then be coded and tested as far as possible in isolation prior to software integration.

Software integration will involve the integration of the software modules to form the complete software programs for the various sub-systems. The completed programs will be loaded on the target hardware and the software engineers will complete their own integration tests prior to commencement of IFAT.

IFAT will involve an internal test of the completed system against the approved Factory Acceptance Test schedule. This will allow system functionality to be proven prior to commencement of FAT. Any faults found will be logged as Observation Reports and will be subjected to Software Change Control procedures. Faults / non conformances will be rectified prior to commencement of FAT.

Factory Acceptance Testing will involve witnessed testing of the completed system by the Client. A FAT Test Specification will be produced containing the necessary test exercises to demonstrate system functionality. The FAT Test Specification will be approved by the Client prior to commencement of FAT.

FAT will involve as much of the target hardware as possible i.e. including the PLC's, Remote I/O, Communications network, intelligent relays.

If required, I/O simulators will be used during FAT. These may take the form of test boxes with switches and indicator lamps or may take the form of external software packages used to simulate I/O signals over the various communications networks.

Any tests not possible due to lack of availability of hardware / suitable simulation technique will be deferred until the installation and commissioning phase.

Successful completion of FAT will be the permissive for the delivery of the system to site. Any faults found during FAT will be logged as Observation Reports and will be subjected to Software Change Control procedures. Faults / non conformances will be rectified prior to commencement of Installation and Commissioning. If required, a re-FAT may be scheduled to witness the correct functionality of any modifications / changes made.

Following completion of FAT, the system will be delivered to site for installation and commissioning. Method statements and full risk assessments will be produced for installation and commissioning.

Safety is very important to Ematics, and all personnel will receive the appropriate safety induction training prior to the commencement of any site works.

On successful completion of installation and commissioning, and any confidence period required by the client, the system will undergo SAT. This will involve a repeat of the tests performed during FAT, but with the actual equipment on site.

On successful completion of SAT, the system will be handed over to the client and the warranty period will commence.

Operations and Maintenance Manuals will be produced for all aspects of the system under Ematics Limited scope of supply. These will contain all the necessary operating instructions for the system, and the necessary as built drawings, system configuration details and supplier datasheets in order to maintain the system. Recommended maintenance schedules will also be provided.

At the time of handover, all software licenses procured for the project and backups of all application code and source code produced by Ematics will be handed over to the client.

We will deliver on-site training tailored to meet the needs of the various system users such as Operators, Maintenance Technicians, Engineers, Administrators. Full Training documentation will be provided.

Ematics engineers will also be on hand during commissioning and SAT and would suggest end user involvement in these activities in order to gain familiarity with the system operation and maintenance requirements.

 

 Back to Top