the different sub systems and implement the required functionalities.
Documentation of all implemented software, including the custom-developed
software codes shall be supplied to the Government after formal system
acceptance, but prior to the endurance tests. The Government shall have
the right of use for the provided software for future enhancements and
additions to the installed system.
2.3.2 Load and Adjust Software
Load software required for an operational control and processing system,
including databases, operational parameters, and system, command, and
application programs. Adjust, tune, debug, and commission all software and
parameters for controlled systems to assure proper operation in accordance
with the sequences of operation and database tables.
2.3.3 Display Information
The TCU shall display information necessary to support all requirements
specified, including: guard control commands; alarm notification; status
point changes; and report generation
2.3.4 TCU Utility Programming
All utility programs shall be object oriented with a mouse driven or touch
screen graphical user interface (GUI). The graphical user interface shall
include a set of desktop utilities including the following: file
management, shell tool, calculator, text editor, and icon library. Program
elements shall be able to be combined into a custom template which can then
be used as a standard function. Program checkout and debug facilities
shall include display of dynamic and/or simulated system variables and
points on the programming screens. The user shall be able to fix or force
values of variables to enable program checkout during debugging. The
programming shall allow for the use of a portable tester for loading files
directly into the TCU and uploading and downloading control programs and
2.3.5 Command Software
The software shall provide for defining and selecting I/O, parameters, and
all other functions associated with operation. The operator commands shall
be usable from keyboards with individual operator passwords as specified.
2.3.6 Command Input and Errors
Command menus shall utilize full words and acronyms selected to allow
programmers/technicians to use the TCU without extensive training or data
processing backgrounds. The TCU shall prompt the programmer/technician.
The TCU shall supervise programmer/technician inputs to ensure they are
correct for proper execution. Programmer/technician input assistance shall
be provided whenever a command cannot be executed because of input errors.
2.3.7 Special Functions
The TCU shall support the following special functions by using a mouse, in
addition to all other commands specified:
a. Help shall produce a display of all commands available to the
operator. The help command, followed by a specific command, shall
produce context sensitive listing with a short explanation of the
SECTION 34 41 26.00 10 Page 29