|
Some of the reports available in
The Re*Cure Reporting
System© Version 1.60 Include:
Hardware - Physical Device Reports
- Full I-Star Device Report
This report results in a listing of all devices configured to an
I-Star and the connection points to which they are connected.
- Customer Reader Report
This reports yields an I-Star by I-Star report with Reader
Name Filter to provide a simple report of reader assignments.
- Input Reports (ACM and I8/RM4)
These reports yields reports that outline Inputs per I-Star and give
indication of where alarms and other input points are connected.
Logical - Event Reports
- Events Offline
Events Administratively OFFLINE
Provides Report of Events Programmed as OFFLINE in Administration
Client.
- Events In-Test
Provides Report of Events Programmed as OFFLINE AND that have the
label "In-Test" typed into the Event Instructions.
- Events Not Monitored By
On-Line Event Group
Provides Report of Events NOT Assigned to On-Line Events Group and
Subordinate Monitoring Privilege.
Activity Based Reports - Top Active
Items
- Enhanced Reporting INPUT
Report
Provides a list of Inputs that have entered the history database in
descending order of activation count; selectable by activation count
threshold.
This report can be
invaluable to identify Input Points that either need service attention,
or may need to be reprogrammed to avoid nuisance alarms and operator
distraction.
- Enhanced Reporting EVENT
Report
Provides a list of Inputs that have entered the history database in
descending order of activation count; selectable by activation count
threshold.
This report can be
invaluable to identify Events that either need service attention, or may
need to be reprogrammed to avoid nuisance alarms and operator
distraction.
- Enhanced Reporting DOOR Report
Provides a list of Inputs that have entered the history database in
descending order of activation count; selectable by activation count
threshold.
This report can be
invaluable to identify Door Open/Held, REX Devices and configuration
issues that either need service attention, or may need to be
reprogrammed to avoid nuisance alarms and operator distraction.
-
Device Communication Failure Report
Provides a report
outlining devices that are experiencing communication problems and may
require service attention.
-
24 Hour (S) Sensitive
Area Event Activity Report
This report generates a report outlining the new activation of Events
that carry the text (S) in them; these Events are tagged to indicate
sensitive area and are of extreme concern. This report will (when
automated)
-
24 Hour Tamper
Report
Provides a report of
devices that have registered a tamper signal over the last 24 hours.
Misc. Reports
- CCTV Action Detail Report
Provides a list of programmed CCTV Actions and their respective
parameters.
- Events the Call CCTV Actions
Provides a list of Events that Call CCTV Actions and their
respective parameters.
-
Group Definition
Detail Report
Provides
a listing of Objects Assigned to C*Cure 800/8000 Groupings (such as Door
Groups or Event Groups) as well as indicating if these respective events
are assigned to be downloaded to an I-Star controller. This report is
searchable by Group Name and can be very useful to determine system
loading and Group Relationships
-
Group Record Count
Report
Provides
a count of assigned C*Cure Objects Assigned to “Groups”. Useful
to determine system loading and database table sizes.
NEW IN VERSION 1.60 –
ReSpect – Inspection and Testing Database
New
in Re*Cure version 1.60 and above is the addition of “ReSpect” Testing
and Commissioning Database. This database can be used to generate simple blank
Door and Input testing reports to linked C*Cure 800/8000 Doors and Inputs as
well as offering a database linkage to register and track testing results.
Additionally, the ReSpect system can allow configuration details of the physical
equipment in the field to be recorded and stored for reference (such as lock
type and voltage, power circuit numbers, etc…). This could be helpful not only
to establish as-built records, but also to direct technicians in the field
(lessen service and downtime).
1
- Example Door Detail and Testing Form
ReSpect Feature Overview
Blank Report Generation
Produce
detailed blank report documentation for field testing and reference. These
blank forms can also be used as an inspection and acceptance hardcopy as
performed in the field. Installing agents as well as owners could take these to
the area and test with individuals to later be used as the formal record of the
testing in written form.
Door Testing Form (as shown above)
Utilized
in ReSpect to add details to doors regarding the physical installation as well
as to record testing results and generate selectable door testing history
reports.
Input Testing Form
Utilized
in ReSpect to record input (that are linked to C*Cure Events that Require
Acknowledgement) testing results. Also used to generate selectable input
testing history reports.
ReSpect History Reports
Generate
reports that outline the history recorded into the ReSpect testing and
commissioning system.
Sort by and filter by date range, controller name and even door or input name.
The example below outlines how you could produce a report on only “Sensitive
Doors” (Doors that name contain “(S)”) that are attached to any I-Star
Controller with “P1” in its name.
2 - Testing History Form
Microsoft Windows™, Access™ and
Excel™ are Registered Trademarks of the Microsoft Corporation.
C*Cure 800/8000 System™ is a Registered Trademark of the Software House / TYCO
Corporation.
| 
Global
Implementation Group
