FUNCTIONAL SPECIFICATION FOR TERMINAL MANAGEMENT SYSTEM (TMS) part 5 TMS

 FUNCTIONAL SPECIFICATION FOR  TERMINAL MANAGEMENT SYSTEM (TMS) part 5TMS GENERAL REQUIREMENTS 

FUNCTIONAL SPECIFICATION FOR  TERMINAL MANAGEMENT SYSTEM (TMS) part 5

1.0           TMS GENERAL REQUIREMENTS

1.1                 Use of Standard Products

The TMS system shall be composed of the following:

 

·         Standard hardware

·         Standard operating systems;

·         Standard relational database software ,ORACLE compatible;

Standard hardware, standard operating system and standard application software shall be compliant with 34-SAMSS-050 and shall not be modified to meet any of HVACMEP.SITE's requirements

 

1.2                 System Configuration

The Vendor shall provide all configurations of the standard operating system and standard application software to make the system site specific by enabling/disabling different function and process types. Standard operating systems shall not be modified to meet any of HVACMEP.SITE's requirements.  Standard application software shall also be provided for interface to sub-systems or to the host system.

1.3                 Furniture

The provision of desks or chairs is outside the scope of the TMS VENDOR.  Dot matrix printers shall, however, be supplied with suitable stands with support and feed paths for fan fold paper.  The TMS workstations and laser jet printers shall be designed for placement on, and operation from, a standard office desk top, to be supplied by others.

The provision of console enclosures is required for TMS Workstations and is included in the scope of work of the TMS VENDOR.   The console enclosures prevent the accumulation of dust inside the equipment.  The final design and/or type of console enclosure shall be approved by HVACMEP.SITE.

The provision of lockable equipment cabinets to prevent unauthorized access and the accumulation of dust are required for TMS Servers, LAN and Communications Equipment and is included in the scope of work of the TMS VENDOR.   The final design and/or type of the equipment cabinets shall be approved by HVACMEP.SITE.

1.4                 Field Proven Systems

Reference material specifications 23SAMSS50 section on Field Proven Systems in addition to the requirements below:

Field-proven is defined as successful operation of a standard product at a field installation for six or more months. It shall be possible for HVACMEP.SITE to verify the field proven status of all systems equipment including subsystem interfaces as an integrated offering.

All hardware, standard operating systems and standard application software supplied with the system shall have been field proven. The standard operating systems and standard application software shall be the most recent field proven revisions that are applicable to the system hardware.

 

The TMS VENDOR shall guarantee that they will support all system hardware, standard operating systems and standard application software with spare parts and service for a period of 10 years from placement of the order. This support shall not be contingent on the customer upgrading to later releases of software or hardware, unless this upgrade is supplied at no additional cost.

 FUNCTIONAL SPECIFICATION FOR  TERMINAL MANAGEMENT SYSTEM (TMS) part 5 TMS

1.5                 Software Protection

This section is located in material specifications 23SAMSS50 section on Software Protection.

1.6                 Site License

The TMS VENDOR shall provide site licenses for all TMS software and all required licenses shall be issued to HVACMEP.SITE as the End User and Licensee.  Individual workstation licenses shall not be acceptable.  The TMS shall allow, as a minimum, the future addition of one server and four workstations licenses per site, without alteration to the software or license agreements.

1.7                 Distributed Architecture

Reference material specifications 23SAMSS50 , Architecture section in addition to the requirements below:

The system shall be based on a redundant client / server architecture such that the software applications can be distributed to multiple nodes on the same network, while the system database resides on a centralized file server.

1.8                 Scaleable Architecture

The system shall utilize a scaleable architecture to permit a wide range of system configurations and facilitate system flexibility and expandability.  This approach shall accommodate the terminal's sizing for which the same hardware and software components shall be used, with the terminal size dictating the type and number of TMS components needed for each site.

The TMS shall be designed to be able to add additional components or replace certain components with higher capacity/ performance units in order to increase the overall capacity of the system.

 FUNCTIONAL SPECIFICATION FOR  TERMINAL MANAGEMENT SYSTEM (TMS) part 5 TMS

1.9                 Redundancy

Reference material specifications 23SAMSS50 section on Redundancy in addition to the requirements below.

System redundancy shall be provided in the following manner:

·         Multiple workstations at each site, each with operator and engineer functionality; Failure of any TMS workstation component shall not cause the failure of more than one workstation

·         Multiple TMS Servers with redundant power supplies to assume primary and backup functions with fail over capabilities during a system failure.

·         LAN Hubs with redundant power supplies located in the Operations Control Center.

System redundancy shall include a fully redundant PLC system with redundant processors, redundant power supply module etc., excluding I/O subsystem.

Redundancy shall be implemented in a manner consistent with the industry standards and the client/ server architecture.

In the event of a complete communication failure between the host computer and the TMS, the TMS shall continue to operate.  When communications are again established, data shall be automatically transferred to synchronize databases at both locations.  No data shall be lost as a result of fail over to backup modules.

In the event of total failure of the TMS server, or communications failure between TMS and any or all subsystems, loading/ unloading shall still be possible under local control of the preset controllers.  Each preset controller shall have the capacity to store in local memory a minimum of 100 transactions that shall be automatically uploaded and processed immediately when TMS operations are re-established.

 FUNCTIONAL SPECIFICATION FOR  TERMINAL MANAGEMENT SYSTEM (TMS) part 5 TMS

1.10             Availability

1.10.1       Internal Communications

Failure of any single device that is connected to, but not a constituent part of, the data highway shall not affect the ability of the system to communicate with other devices on the network.

1.10.2       Diagnostics

Reference material specifications 23SAMSS50 section on Diagnostic Displays in addition to the requirements below:

The TMS VENDOR shall configure all standard hardware and software diagnostics to provide typically the following information:

·         Communication network loading;

·         CPU loading;

·         Module status (e.g. off-line, standby, on-line, failed).

Tools shall be available to view the software version of all modules.

1.10.3       Hardware reliability

Reference material specifications 23SAMSS50 section on Reliability in addition to the requirements below:

This section describes hardware reliability requirements for TMS hardware modules.  It specifically does not address system availability.  The Mean Time Between Failures (MTBF) figures shall be supported either by actual field data or calculated from component MTBF data.

to be continue for the next post