Technical Requirements (23-423)_Revision 01.pdf

NOAA PASCAGOULA ACCESS CONTROL SYSTEM UPGRADE

TECHNICAL REQUIREMENTS

GENERAL DESCRIPTION

These Security Management System (SMS) upgrades, which are also known as – the system migration process from the current SoftwareHouse CCURE 800 software to the most current version of SoftwareHouse CCURE 9000, shall become part of a powerful, flexible, multi-function and object oriented security and event management system that features a variety of customizable interfaces for maintaining the system and for monitoring the desired secure sites. These SMS upgrades shall provide an option to display these management and monitoring interfaces in the native languages of the people using the system. The security and event management system shall maintain flexibility in order to meet specific requirements and quickly respond to evolving security challenges.

The SMS upgrades shall maintain a scalable platform, simple and economical enough to support a single site, yet upgradeable enough to manage a multi-site network. The SMS upgrades shall use an open, distributed architecture, where database servers could reside in geographically separate locations.

The SMS upgrades shall provide extensive information management capability using Microsoft .NET Framework latest version. They shall operate in a Client/ Server configuration on personal computers with a Windows-based platform. Its distributed client-server architecture shall be capable of supporting up to 128 simultaneous clients, multiple types of controllers, and over 10,000 input devices, including cameras and multiple types of card readers. The SMS upgrades shall be constructed to be database independent and shall support at a minimum Microsoft SQL Server 2005 (Express, Standard, Data Center, or Enterprise), and Oracle 10g Databases for data protection, redundancy and manageability.

The SMS upgrades shall have true multi-tasking, multiprocessor and remote client support; allowing independent activities and monitoring to occur simultaneously at different locations. The operator workstation (Client) shall be user friendly, employing icon-based menus and providing a mouse-driven interface for system operation and the creation of color graphic maps. The user interface shall be customizable, capable of delivering a unique look and feel without a unique version release.

The SMS upgrades shall integrate with the existing intuitive user interface similar to Microsoft's Outlook and Explorer with its easy navigation and tree structures. A practical application layout editor allows users to drag and drop any application onto one screen and create a customized hub for all activities via a single "command and control" center.

Field devices such as card readers, alarm inputs, control points, etc. shall be connected to fully distributed intelligent field controllers or directly through a Software Development Kit or Web Services, and be capable of operating without host computer intervention. All objects within the SMS upgrades, i.e. doors, readers, time intervals, etc. shall be addressed by a unique name as opposed to point numbering or mnemonics.

It should be notedThe NOAA Pascagoula SMS is a stand-alone system and not connected to the internet/www. WiFi service should be available at the project location, for updates, etc., but is not guaranteed.

Server Requirements -

The Contractor shall provide a computer server for the installation of the CCURE 9000 SMS program:

- This computer server shall meet all specifications/requirements listed in Attachment 1, Software House CCURE 9000 Data Sheet for proper operation of the installed SMS. For this application, it is believed to be listed under SERIES "N". Contractor shall confirm the correct server is provided for proper operation of the SMS

Manuals

The Contractor shall provide copies of the manuals as described herein. Each manual's contents shall be identified on the cover. The manual shall include names, addresses, and telephone numbers of each security system integrator installing equipment and systems and the nearest service representatives for each item of equipment for each system. The manuals shall have a table of contents and labeled sections.

The manuals shall include all modifications made during installation, checkout, and acceptance. The manuals shall contain the following:

Software Manual

The software manual shall describe the functions of all software and shall include all other information necessary to enable proper loading, testing, and operation. The manual shall include:

a. Definition of terns and functions.

b. Use of system and applications software.

c. Initialization, start-up, and shut down.

d. Alarm reports.

e. Reports generation.

f. Data base format and data entry requirements.

g. Directory of all disk files.

Operators Manual

The operator's manual shall fully explain all procedures and instructions for the operation of the system including:

a. Computers and peripherals.

b. System start-up and shut down procedures.

c. Use of system, command, and applications software.

d. Recovery and restart procedures.

e. Graphic alarm presentation.

f. Use of report generator and generation ofreports.

g. Data entry.

h. Operator commands.

1. Alarm messages and reprinting formats.

J. System access requirements.

Maintenance Manual

The maintenance manual shall include descriptions of maintenance for all equipment including inspection, periodic preventive maintenance, fault diagnosis, and repair or replacement of defective components.

QUALITY ASSURANCE

Manufacturer Qualifications

The manufacturers of all hardware and software components employed in the SMS upgrades shall be established vendors to the access control/security monitoring industry for no less than five (5) years and shall have successfully implemented at least 5 systems of similar size and complexity.

Contractor/ Integrator Qualifications

∙ The security system integrator shall have been regularly engaged in the installation and maintenance of integrated access control systems and have a proven track record with similar systems of the same size, scope, and complexity.

∙ The security system integrator shall supply information attesting to the fact that their firm is an authorized product integrator certified with the SMS upgrades. A minimum of one technician shall be a Certified C•CURE 9000 installer.

∙ The security system integrator shall supply information attesting to the fact that their installation and service technicians are competent factory trained and certified personnel capable of maintaining the system and providing reasonable service time.

∙ The security system integrator shall provide a minimum of three (3) references whose systems are of similar complexity and have been installed and maintained by the security system integrator in the last five (5) years.

∙ There shall be a local representative and factory authorized local service organization that shall carry a complete stock of parts and the capability of providing 24/7 /365 maintenance for these systems.

Testing Agencies

• The SMS upgrades shall be tested and listed by Underwriters Laboratories (UL) for UL/cUL 294 for Access Control System Units (Pending)

• The SMS upgrades shall be tested and listed by Underwriters Laboratories (UL) for UL/cUL 1076 for Proprietary Alarm Units (Pending)

• The SMS upgrades shall employ a FIPS 197-listed AES 256-bit encryption between C•CURE 9000 Servers, Clients, and iSTAR eX Controllers

• The SMS upgrades shall include full support for FIPS 201 initiative:

- Ability to customize a system-wide Card Holder Unique IDentification number (CHUID) - Ability to configure custom, extended card formats, including the GSA 75-bit Wiegand Standard and also especially the Federal government/DoD Common Access Cards (CAC), and to download them to the local card access panels

- Ability to use Hashed Message Authentication Codes (HMAC) for medium assurance profile - Enhanced data fields per the FIPS 201 standard, including Agency Code, System Code, Credential Series mid Credential Issue Code

• The SMS upgrades hardware (as applicable) shall comply with the following regulatory requirements:

- FCC Class A

- FCC Class B

- CE

- Canadian Radio Emissions requirements

- Restriction ofHazm-dous Substances Directive (RoHS) 2002/95/EC

- FIPS 140-2 encryption (certified for the iSTAR eX controller)

• The SMS upgrades shall support Americans with Disabilities Act (ADA) compliance in door and access operation

Licensing

Licensing shall be required for the SMS upgrades software. The licensing shall include:

- Series (Model)

- Number of online readers

- Number of online inputs

- Number of online outputs

- Number of cm-d holders

- Number of simultaneous clients

- Number of simultaneous badging stations

- Digital Video Integration option

WARRANTY

The Security Management System (SMS upgrades) shall be provided with a 14-month product warranty 1 year from date of functional installation

Software version upgrades shall be available for no charge during this warranty. The software media warranty shall be per the SoftwareHouse C•CURE software licensing agreement.

PRODUCTS

MANUFACTURERS

The Security Management System (SMS upgrades) shall be the SoftwareHouse C•CURE 9000 system

PRODUCTS, continued

DESCRIPTION

The Security Management System (SMS upgrades) upgrades shall become part of a fully integrated system that utilizes a single, industry-standard relational database management system for the storage and manipulation of related data. The existing SMS includes a server with operating system and applications software, and operator/administrator terminals with appropriate software. The security devices communicate with the field panels via a dedicated cable network. The field panels communicate to the server via a Fast Ethernet 10/100, TCP/IP network or a serial (RS-232, RS-485) connection.

The SMS upgrades shall allow for growth and scalability from a low-end or entry level system to a high end or enterprise system by increasing CPU power, memory and database. The SMS upgrades shall be modular in nature, allowing system capacities to be easily expanded without requiring major changes to system operation. All defined system data as well as historical information shall be maintained.

Customizable user interfaces shall allow management of system information and activity for administrators and operators.

SMS Upgrades Functionality

Partitioning

The SMS upgrades shall allow system administrators to separate the creation and viewing of objects into partitions. SMS upgrades operators shall be associated with partitions and this shall determine which objects operators have the ability to create and or view. The SMS upgrades shall support an unlimited number of partitions.

The SMS upgrades partitions shall include but not be limited to the following objects:

• Personnel

• Clearances

• Doors

• Controllers with all associated hardware (readers, inputs, outputs, etc)

• Video servers with all associated objects (cameras, tours, views, etc)

• Application layouts

• Events

• Dynamic views

• Maps

• Reports, forms, results

• Holidays

• Badge layouts

• Queries

• Images

Through the use of privileges, the SMS upgrades System Administrator shall be able to determine which objects are associated with a particular partition. These objects shall then be assigned to System Operators with the appropriate privilege.

The SMS upgrades shall support a super-user assigned the 'System All' privilege who shall have full access to all objects in all partitions.

∙ Any operator shall have the ability to be assigned access rights to any partition. Individual Access rights shall be created and have the ability to be assigned to any users of the SMS upgrades. ∙ The SMS upgrades shall allow objects to be created in any partition. The SMS upgrades shall have the ability to grant or remove permission from any object in any partition ∙ The SMS upgrades shall provide the ability to move objects from one partition to another ∙ partition without the requirement of deleting and recreating ∙ Partitions shall have the ability to be moved between application servers by way of drag and drop control ∙ The SMS upgrades shall provide the ability to import/export any configured object ∙ including partitions and privileges ∙ The SMS upgrades shall support the display of all associated objects contained within a Partition

Application Server Architecture

The SMS upgrades shall support Multiple Application Servers. Application Servers shall provide the ability to distribute d1iver communication to user defined SMS upgrades hardware. Strategically placed applications servers shall provide a flexible, scalable SMS upgrades solution. These regionalized Application Servers shall be flexible to accommodate various network design models. Application Servers shall support the following features:

∙ The assignment of hardware via an SMS upgrades partition(s) ∙ Locally or regionally group application servers and incorporate a communication failover subsystem ∙ The SMS upgrades shall allow for a manual transfer of selected partitions between application servers ∙ Automatic failback shall apply to Client applications whereby when the primary application server is put back on line, the client application will automatically reconnect to the Primary application server ∙ Manual failback shall apply to Field Controllers to ensure that communication to field panels is properly maintained and facilitated ∙ The system shall allow for the designation of a specific application server to a specified task such as reporting, importing, hardware communication such as controller communication and or any driver ∙ The system shall support enterprise-wide administration of personnel and reporting

Graphical User Interface (GUI)

The existing SMS upgrades employs a standard Windows XP™ Professional graphical user interface (GUI). A mouse and keyboard are the primary operator interface with the system. Operator screens utilize all standard Windows-style functions such as drop-down menus, context menus, radio buttons, and lists, as appropriate. The interface utilizes a 'tree structure' similar to Windows Explorer.

LDAP Interface with role support

The system shall have the ability to connect to a directory service source via the Lightweight Directory Application Protocol (LDAP). The connection to the LDAP source shall be user-configurable directly from the SMS upgrades and shall not require custom code. The LDAP interface shall also support tbe automatic assignment of SMS upgrades clearances based on data contained in the LDAP record. The LDAP feature shall support the following features:

∙ LDAP server name and user-defined port number ∙ A base distinguished name for the root of searches ∙ A user-definable LDAP search filter to refine object search ∙ User-defined mapping of attributes to SMS upgrades personnel fields ∙ The use of a Distinguished Name (DN) entry for the SMS upgrades to authenticate to LDAP ∙ Option to search all sub-levels of the directory from the base DN ∙ Preview sample-data based on SMS upgrades LDAP import settings ∙ Automatic roles-based SMS upgrades clearance(s) based on two fields of source data ∙ Automatic import of directory entries from the LDAP source ∙ Authentication via a user-definable LDAP user account and SSL ∙ Automatic SMS upgrades clearance assignment

Information Storage, Backup and Transfer

• All programmed info1mation, as well as transactional history, shall be automatically stored in the database for later retrieval and backup. The SMS upgrades shall support configurations where the SMS upgrades database(s) may be installed on a hard drive on the SMS upgrades server, on an independent database server, or in an existing corporate database server.

• The SMS upgrades shall be capable of backing up and restoring all card holder and system configuration data and transactional history. The server shall be capable of transferring all programmed system and cardholder data and transactional history to USB thumb drive or external USB Hard Drive (including networked drives) for use in a “system restore” capacity in the event of server crash or similar.

• The SMS upgrades shall allow activity history to be written to a database. The system shall have the capacity to store a minimum of 50 million transactions. There shall be a method of backing up the activity history on external media and then restored and replayed.

• The SMS upgrades shall support AES 256-bit encrypted communications between server and user client.

• The SMS upgrades shall support AES 256-bit encrypted communications between server and controller.

The encryption shall support both local and third pa11y digital certificates.

Communication Ports

• The SMS upgrades shall be able to support multiple serial devices. In addition to COM1 and COM2, up to [8, 16, 32, to 256] additional ports may be configured through the use of a port expander or its equivalent. These serial ports may be used for connection to CCTV matrix switchers, or apC panels.

• The SMS upgrades shall support the use of Ethernet networks as the communications path between the host computer and field devices such as ETHERL'\/ET ISC, iSTAR, apC, apC 8/x, ApC Lite controllers, and CCTV matrix switchers. This communications path shall be the same network used for communications between the host server and the operator workstations. The communications between the host computer and the field devices shall be encapsulated in a TCP/IP network/transport layer.

Inputs

• The SMS upgrades shall monitor both supervised and unsupervised hardware inputs as well as virtual inputs such as predefined system messages. These inputs include door / elevator inputs and monitor points. The SMS upgrades shall also monitor controller inputs such as tamper, AC fail, and low battery

• The SMS upgrades shall have the ability to nan1e and allow for user defined descriptions for individual inputs, outputs, and readers as well as input and output modules

• There shall be three separate and distinct states for inputs which can be defined on the input configuration screen: Disabled, Enabled/ Disarmed and Enabled/ Armed

• The SMS upgrades shall allow configuration to link the state of an input to an output. The system shall allow multiple inputs to activate a single output or group of outputs

Outputs

• The SMS upgrades shall have outputs, also known as Control Points that associate an input or event action with a relay. These output uses include doors / elevators, alarms and industrial control

• There shall be two types of outputs available: dry contact / Form C relays and Open Collectors. Outputs shall be configured such that they can be activated, deactivated or pulsed by system actions.

Card and Reader Support

The SMS upgrades shall be designed to support multiple card formats and card reader types. The SMS upgrades shall support the following features for directly connected readers:

∙ Federal government/DoD Common Access Cards (CAC) ∙ User defined card formats up to 256 bits ∙ Unlimited number of SMS upgrades card formats ∙ The ability to assign up to 10 card formats per reader ∙ The ability to show reader status on RM LCD ∙ Support Wiegand and 3x4 matrix keypads ∙ The enrollment of biometric templates to smartcards ∙ Custom CHUID FIPS201-compliant supporting full 256-bit data

The SMS upgrades shall support readers that provide Wiegand signaling and magnetic signaling to include:

∙ Software House RM readers ∙ Software House Multi-technology readers ∙ Wiegand swipe/insert readers ∙ Proximity readers ∙ Biometric readers ∙ Smart card readers ∙ Magnetic readers

Door Configurations / Elevator Control

The SMS upgrades shall allow doors to be configured to operate in any of the following access control modes:

∙ Unlocked ∙ No Access (Secure mode)

∙ Any combination of the following, as defined by schedule, event: card only, PIN only, Card+ PIN, Card entry through keypad.

The SMS upgrades shall allow a door to be configured to operate using the following functions:

∙ Readers shall read cards while the door is in the open position ∙ Door lock relay shall automatically lock upon the door being opened ∙ Allow for a user-defined delay relock time period ∙ Allow for a user-defined door unlock time and door held open time ∙ A separate (alternate) shunt timer for ADA flagged cardholders ∙ The operator shall be able to specify a shunt expiration output to be trigered for a configurable time

(in hh:mm:ss) before the expiration of the door open or alternate shunt. Can be enabled for ADA only, or all the time.

∙ Allow for a user-defined door unlock and door held time, in seconds

∙ PIN-only access (keypad) ∙ PIN-entry on the reader keypad shall be required during a specified schedule after a card access

(unless a manual action or event has disabled PIN) ∙ Card entry through keypad

The SMS upgrades shall allow each door to be configured to cause a variety of events such as alarms to occur based on activity at that door

The SMS upgrades shall support an extended unlock function initiated via two valid card presentations to a single reader or a 'double swipe'. The double swipe feature provides the ability to designate doors at which cardholders with double swipe privileges may perform an extended lock or unlock of the door.

The double swipe feature shall support the following:

∙ Modified reader beeper pattern to reflect the extended unlock mode ∙ Individual card access privileges to perform double swipe action ∙ Unique parameters assignable to any door ∙ Reset of a double swipe unlock (relock) via scheduled event ∙ Event activation to reflect double swipe state (Lock, Unlock)

Schedules

The SMS upgrades shall support unlimited operator configurable schedules. Each schedule shall allow unlimited individual time intervals.

Each system controller shall support a minimum of 128 schedules and a minimum of 18 time intervals per schedule.

Each schedule shall consist of operator-defined time segments. Each time segment shall be day(s) of the week and include holidays and starting and ending times. The system shall provide grouping of days.

Holidays

The SMS upgrades shall support unlimited holidays

The SMS upgrades shall support holiday type designations as Recurring Day of Month, Recuning Relative Monthly, Non-Recurring or Day of Week.

The SMS upgrades shall allow assignment of duration to each holiday. Holiday groups can be assigned to a Schedule.

Time Zones

The SMS upgrades shall maintain time zones to be used when configuring certain system objects. A time zone shall adhere to standard international Time Zone behavior, and the system shall support all time zones supported by the Windows OS

The SMS upgrades shall allow time zones to be assigned to IP devices, controllers, CCTV matrix switchers, DVRs, and scheduled Manual Actions

Clearances

The SMS upgrades shall support configuration of unlimited Clearances

The SMS upgrades shall support up to 20 clearances per person

The SMS upgrades shall support clearance activation and expiration date and time.

Events

The SMS upgrades shall support unlimited operator configurable events, including the scheduling of events, and action-based trigger of events.

The system shall provide 8 configurable event priority levels with a total of 200 numbered event priorities. The system shall allow the operator to define custom colors and labels per individual priority level

The system shall allow an event to be configured to:

∙ Be sortable by event name, date/time, priority, state, and any other displayable information ∙ Be routed to operators by operator privileges, including support for the routing by time of day feature ∙ Require or not require operator acknowledgment ∙ Require or not require a log message to be entered by the system operator responding to the event ∙ Display or not display the event activation ∙ Require the object(s) causing the event activation to reset before the operator may acknowledge the event ∙ Display au operator-defined text message upon event activation ∙ Display an operator-defined text message when the event is deactivated ∙ Be associated with a map so the map opens automatically on the monitoring station when the event activates ∙ Activate a second event when the first event activates and is unacknowledged for a specified period of time ∙ Allow the operator to associate an audio wave file with the event ∙ Allow for minimum activation time and delayed activation time for events ∙ Download events to the iSTAR controllers ∙ Run imports and exports ∙ Run reports and remove report results Integrated E-mail

The e-mail system shall have the ability to interface directly to an SMTP-compliant e-mail system supplied and configured by the user

Import/ Export

The SMS upgrades shall provide a means for manually importing and exporting selected data in XML format. This mechanism shall support the impmi and export of any and all classes or types of data in the system. Specific data validation and logging requirements shall be met. The system shall also support importing from CSV files.

The SMS upgrades shall provide an automated import mechanism (preferably XML-based).

This mechanism shall support the import of most classes or types of data into the system.

Specific data validation and logging requirements shall be met.

The SMS npgrades shall provide a Data Mapper feature that provides field mapping information using the XSLT file based on the input data or an external XSLT file.

Objects

Each object within the SMS upgrades shall be addressed by a unique operator-defined name.

Object names shall be w1ique within object types.

The SMS upgrades shall provide the ability to add description text to each object definition.

Reports

The SMS upgrades shall provide configurable data reports for database configuration, historical activity (Journal) and audit tracking. Pre-defined reports shall be available for download and import into the system

The SMS upgrades report function shall perform the following:

∙ Create reports about any object ∙ Create report templates to simplify report design ∙ Run reports on demand ∙ Save report results for sharing between different users of the application ∙ Export reports into formats such as PDF, RTF, TXT, TIFF, Excel (XLS), and MHTML ∙ Specify a query to select and filter the records on which to report ∙ Specify the data fields to be included in a report ∙ Specify a design for the report layout ∙ Design a report form to be used as a layout for headers/footers for multiple reports ∙ Access and use system predefined report forms ∙ Select tabular, multi-line, or free form report layouts ∙ Report on objects linked together with parent/ child relations ∙ Schedule reports to run automatically on a customized schedule ∙ Send exported report files to the printer or to external recipients via e-mail Dynamic Views

The system shall support a grid format displayable report which will be usable to display homogeneous lists of objects within the system. This display shall be configurable both at configuration time and also at run time

The Dynamic views shall have the following features:

∙ Real-time updating and display of property values ∙ The display shall be sortable ∙ Groupable by any number of columns ∙ Filterable based on user selectable criteria ∙ Printable ∙ Exportable in either XML or CSV file formats ∙ The export file shall be viewable in Excel (Excel must be installed separately) ∙ The export file shall be able to be emailed ∙ The user shall be able to add and remove columns from the grid at runtime to enhance the user experience even if displaying a preconfigured view ∙ The view shall be capable of pre-configuration so that repeatable displays of objects are possible ∙ The view shall support in-place editing of properties of the object ∙ Bulk operations shall be performed via multi-selection. The operations shall consist of (but are not limited to) setting a property to a value and deletion

Query

The SMS upgrades shall provide a Query engine to be useful for users without any knowledge of SQL or any other specific query language. It shall allow user to make requests against data sets with preconfigured relations between tables. The relations shall reflect the actual relations between database objects and the user shall he able to put conditions on any available field in the selected object type and its subordinate objects.

The user shall be able to construct a proper query expression selecting all available operations, column names, and table names from prompted lists. It shall eliminate the necessity to memorize any particular expression syntax. References to existing configuration objects shall also be prompted through a list of existing objects where applicable, eliminating the necessity of memorizing names. The Query feature also supports complex logic, such as AND/OR.

System Parameters

The Security Management System (SMS) shall have a minimum capacity of:

• 50 online card readers

• 64 online inputs

• 64 online outputs

• 7,000 credentials

• 6 simultaneous Clients

The SMS shall have a maximum capacity of:

• 75 online card readers

• 10,000+ online inputs

• 10,000+ online outputs

• 100,000 credentials

• 256 simultaneous Clients

• 2 Badging Clients

OPERATION

The SMS migration from C-CURE 800 to C-CURE 9000 shall provide the following operational functionality upon completion:

∙ The system shall control access to a designated area(s)

∙ The system shall validate cardholder credentials by use of downloaded personnel records, card formats, PINs, biometric enrollment and multiple active cards. The system shall compare the time, location, and unique credential number of an attempted entry with information stored in memory

∙ Access to a designated area will be validated only when a user's credential has a valid number for its facility and the number is valid for the current time and for the reader where it is used

∙ The system will have an option to notify police upon detection of an unauthorized or forced entry

∙ The system shall access the hardware that validates the person and monitor the security of a building by use of controllers, doors, readers, elevators, inputs and outputs. When access has been validated, a signal to the door locking device shall be activated to enable alarm-free access at that location

∙ The system shall configure itself as required by use of an Administrative application, and shall provide Configuration templates

∙ The system shall be capable of monitoring access control activities by use of Monitor Station, Alarm ∙ configuration, NetVue, CCTV, and dynamic Graphical Maps display of alarm, door, and event activity (Maps based on CAD data)

∙ The system shall restrict administrative and Monitoring Station activity by use of Privileges and Authentication (User Password) using Microsoft Windows OS Password Function

∙ The system shall report on various aspects of the system by use of Reports (canned and configurable).

Reports shall be able to export to a printer

∙ The system shall have the capability to report off-normal security device conditions both audibly and visually

∙ The system shall control hardware from the monitoring station by use of Manual actions, Events, and cause lists

∙ The system shall provide Record and Data Management by use of Historical Journal (archive and replay), Full Audit Trail and automated and manual import and export (data and images)

∙ The system shall allow for data to be imported from other products by use of database migration tools (Card Holder data and configuration data) from iSecure, C CURE 800/8000 and 3rd party applications via XML formatted data exchange

Controllers

The SMS shall support the following controller hardware at a minimum:

Note: For additional information please refer to individual A&E specifications for the controllers listed below:

∙ Software House iSTAR Classic ∙ Software House iSTAR Pro ∙ Software House iSTAR eX ∙ Software House apC, apC/8X, apC/L ∙ SimplexGrinnell Ethernet ISC

Clustering

The SMS shall support a user-defined grouping of iSTAR controllers defined as a cluster. iSTAR controllers with-in a cluster shall be able to communicate in a peer-to-peer scheme should the SMS server lose communication with the cluster.

Clustering shall support the following features:

∙ Assignment of Master and alternate master controllers for cluster communication to the SMS server

∙ Primary and backup communication paths to the SMS server ∙ Encrypted communications ∙ Up to 16 controllers per cluster ∙ Logical event linking between controllers in a cluster independent of SMS server communication ∙ Asynchronous communication via TCP/IP (Polled devices shall not be acceptable)

EXECUTION

TESTING

The software shall be entered into the SMS computer systems and debugged. The Contractor shall be responsible for documenting and entering the initial database into the system. The Contractor shall provide the necessary blank forms with instructions to fill-in all the required data information that will make up the database. The database shall then be reviewed by the Contractor and entered into the system. Prior to full operation, a complete demonstration of the computer real-time functions shall be performed. A printed validation log shall be provided as proof of operation for each software application package. ln addition, a point utilization report shall be furnished listing each point, the associated programs utilizing that point as an input or output and the progran1s which that point initiates.

Upon satisfactory on-line operation of the system software, the entire installation including all subsystems shall be inspected. The Contractor shall perform all tests, furnish all test equipment and consumable supplies necessary and perform any work as required to establish performance levels for the system in accordance with the specifications. Each device shall be tested as a working component of the completed system. All system controls shall be inspected for proper operation and response.

Tests shall demonstrate the response time and display format of each different type of input sensor and output control device. Response time shall be measured with the system functioning at full capacity. Computer operation shall be tested with the complete data file.

The Contractor shall maintain a complete log of all inspections and tests. Upon final completion of system tests, a copy of the log records shall be submitted as part of the as-built documentation.

TRAINING

The Contractor shall provide a competent trainer who has extensive experience on the installed CCURE 9000 SMS and in delivering training to provide the instruction. As an alternate, the Contractor may propose the use of factory training personnel and coordinate the number of personnel to be trained.

MAINTENANCE

The Contractor shall offer a Software House Software Support Agreement (SSA) in order for Software House Technical Support Specialists to reactively troubleshoot system problems.

As part of the agreement, 5x9 telephone support (Standard and Enhanced SSA) will be provided to the Contractor by Certified Technicians. An option of 7x24 Standby telephone support (Enhanced SSA) shall be offered.

As part of the agreement, Flashable and Non-Flashable (Chips) firmware and documentation shall be provided.

As part of the agreement, access to C•CURE patches and software release updates shall be provided.

The SSA shall cover the current C•CURE 9000 release one full version back, and associated controller hardware.