FUNCTIONAL SPECIFICATION FOR TERMINAL MANAGEMENT SYSTEM (TMS) part 7

FUNCTIONAL SPECIFICATION FOR TERMINAL MANAGEMENT SYSTEM (TMS) part 7 TMS ServersHardware requirements Database and Configuration Local update capability Host computer update capability Tag Parameters Tag descriptor Engineering Units

FUNCTIONAL SPECIFICATION FOR TERMINAL MANAGEMENT SYSTEM (TMS) part 7 TMS Servers Hardware requirements Database and Configuration Local update capability Host computer update capability Tag Parameters Tag descriptor Engineering Units

TMS SYSTEMS SPECIFICATIONS

This section defines the specified practicality for the things of apparatus among the scope of the TMS merchandiser.

TMS Servers

Hardware needs

TMS server hardware shall be supported current HVACMEP.SITE info Technology (IT) approved makers.

TMS merchandiser shall give primary and backup servers for the TMS system in an interior and lockable instrumentation cupboard. to boot, an ardent server shall be provided for the TMS business system info.

Display monitors shall contains as a minimum; 15” viewing space, liquid show (LCD) with TFT, with monitor and keyboard switchbox.

One (1) Gb of Random Access Memory (RAM) shall be provided on every TMS Server. 

Data device like audiotape transport or removable disk drive shall be put in to permit the archiving of knowledge.  A CDR/CDRW recording drive shall even be put in to permit loading of computer code and information and to produce another methodology of archiving of knowledge.  

FUNCTIONAL SPECIFICATION FOR TERMINAL MANAGEMENT SYSTEM (TMS) part 7 

Hard disk storage shall be provided in an exceedingly Redundant Array of freelance Disks (RAID) level one configuration, with a minimum individual disk drive capability of forty GB and a minimum rotation speed of seven,200 rpm’s.

Memory and storage capability shall be optimally sized for the process needs of every Bulk Plant.  Initial server memory and storage size configuration shall embrace a protein of fifty.

The TMS servers shall monitor their power offer and manage their conclusion within the case of breakdown specified all files, applications, etc. fold in associate orderly manner, while not loss of knowledge, or ulterior issues throughout start-up.

Database and Configuration

The TMS shall have a worldwide, relative period info with a period (Oracle or equivalent) management system.  The TMS shall conjointly allow:

• Direct access to I/O name and descriptor by any application computer code within the system while not information of the physical address;

• Data security (protection from unauthorized access and modifications) shall be configurable right down to the field/ record level and therefore the TMS merchandiser shall assign access levels to those as outlined by HVACMEP.SITE;

• Real-time access in an exceedingly distributed environment;

• Query capability (search and retrieval supported condition requests) of the period distributed info.

The info shall hold all plant operational, engineering and dealings information.  This information shall be accessible to the user and be exported to alternative systems and file formats, if needed.  The TMS shall support a Structured search language (SQL) interface that allows alternative pc systems to access information pro re nata for accounting, money or technical applications.

Specific info fields maintained by the TMS shall embrace those that area unit needed to trace product receipt, loading and movement; alarms, operator actions, event history, and alternative needs of this specification.  Business connected information shall be downloaded and updated from the host pc.  It shall embrace client profiles, tank truck descriptions, account details and alternative connected information.

FUNCTIONAL SPECIFICATION FOR TERMINAL MANAGEMENT SYSTEM (TMS) part 7 

Additionally, the TMS shall give all necessary options and computer code tools to allow the creation of recent web site specific info fields that area unit integral to the system.

The TMS shall give a info to support plant operations with:

• Local update capability;

• Host pc update capability.

The following info fields shall generally be provided:

FUNCTIONAL SPECIFICATION FOR TERMINAL MANAGEMENT SYSTEM (TMS) part 7 

• Driver • Hauler • Shipper

• Blends • Customer • Hazard messages

• Account • Blanket orders • Product

• Allocation • Stock • Order

• Tank Truck • Trailer • System defaults

• System profiles (load/ unload bays, gates, BOL Rooms, tank farm, SIB, P/L receive, meter prover, tank gauging, pipeline shipping);

• Meter Factors

Configuration

Only one digital computer shall be necessary to perform all configuration, info generation, graphics builder and archiving history.

An editor shall be supplied with the subsequent features:

• To generate or modify info and configuration data;

• Employs informal, fill-in-the-blanks, or graphical format;

• Step-by-step prompts to guide successive actions followed by validation responses on  completion of the actions;

• It shall request solely applicable info supported previous responses.

• Configuration displays shall be provided to help in system configuration.  These shall embrace displays to show:

• All tags within the system;

• All parameters for every tag, as well as (as applicable) tag ID, tag descriptor, the hardware address, standardization constants, method related to the tag, rule with reference to the tag, and input/output details;

• All configurable (or soft) keys and their function;

• All hardware modules within the system and therefore the configuration parameters for every.

A facility like copy/ paste or a model shall be provided to facilitate making multiple tags that have common parameters (except for minor changes like tag ID and I/O address).  This model may be outlined once then used because the basis for every tag.  It shall be attainable to outline and store multiple templates. a straightforward methodology of occupation every model shall be accessible.

It shall be attainable to put together a series of keystrokes which will be initiated by one operator action.

Configuration modifications shall mechanically update all modules and tags littered with the change.

Configuration modifications shall follow a prompt-validation sequence requiring a final acknowledgement step before the change is accepted; invalid configuration entries shall be known and therefore the parameters affected shall be indicated.

The system shall verify that affected management blocks area unit in either manual or inactive mode before configuration changes area unit created.  If not, either the modification shall be prevented or a warning message displayed.

It shall be attainable to avoid wasting all info and configuration information on each removable and non-removable media for duplicate functions while not taking the system off-line.

It shall be attainable to produce redundant on-line storage media for the configuration info.

It shall be attainable to put together tags for a minimum of sixteen plant areas among one plant and to assign any tag to anybody of the plant areas.

Tag Parameters

All tags shall be outlined with a minimum of the subsequent parameters:

• Tag ID;56

• Tag descriptor;

• Tag type;

• Alarm needs.

Tag IDs shall be unique throughout the system; and access to all tag parameters for configuration shall be available directly by tag ID.

A tag ID shall consist of a minimum of 10 free-format alphanumeric characters.

The system shall support tag descriptors of 16 characters.

The system shall provide the capability to define free-format alphanumeric descriptors for each state of a multi-state device.  Four states shall be allowed for each multi-state device (for example, open, closed, in-between, and fault for an MOV).

Engineering Units

Each analog input, output, control and calculated block shall be assigned an engineering unit designation. It shall be possible to automatically display this designation with the value when the input, output, or algorithm is accessed.

 Engineering units shall be a minimum of six free-format alphanumeric characters.