1. WCR 12/2002

2. What is NexSentry Manager?
An access control and alarm management system
powerful and flexible
makes complex tasks easy
NexWatch quality
Microsoft Windows NT / 2000 power
NexSentry Manager is an Access Control and Security Management system that brings both power and flexibility easily manage your access control system.
NexSentry Manager incorporates the quality and flexibility of a NexWatch security management program with the power and usability of a native Windows NT/2000 application.
Revision 3.11, released in December 2002, is the latest version. It incorporates the CHIP (Star II) interface and dramatically enhanced Report generating, storage and execution features. 3

3. Modular Components for Easy Configuration
NSM Client/Server
Ethernet
Dial-UP
Hardwired
HUB
Report
Log
NSM Client
Typical NexSentry Manager example with:
4 - Star I and/or Star II ACUs. The Controllers can be connected to the host via Direct wiring (RS_232 or RS-485), Ethernet (using CoBox and Micro CoBox) and Dial Up connections.
2 - Client Application User Stations
1 - Report Printer on Network
1 - Log Printer on PC LPT port
NSM Client

4. Flexible Client/server design
Open Database Connectivity (ODBC Database) Access
Conforms to most standard networking protocols: TCP/IP, PPP, IPX/SPX and NETBIOS
NexSentry Manager’s client/server design easily accommodates the addition of controllers and doors to a growing facility -- while maintaining maximum performance.
It is SQL compliant and provides Open Database Connectivity Access. This allows users the flexible option of using their own applications for manipulating and reporting data.
NexSentry Manager conforms to most standard networking protocols, including: TCP/IP.

5. Interactive maps Visual status of any location in a system
Accepts standard graphic formats
Bit Map
Auto Cad output to .bmp .jpg .gif
Control through the map
Unlock/Lock Doors
Operate Cameras
Control Equipment
NexSentry Manager’s powerful interactive maps feature allows visual status of any location in a system using maps generated from Auto-Cad or other graphics applications.
Operators can also Unlock and Lock doors, Shunt and Unshunt Input points and manipulate Relay Outputs through the map.

6. NSM Is Compatible With:
818SC (and upgraded 818SX)
4100 Family (4102, 4104, 4108)
Star I Controllers
Star II (CHIP Protocol)
and
Analog Prox, Digital Prox, Magnetic Stripe and Wiegand protocol Readers
For any new sales of NexSentry Manager as part of the Fighter Models, this compatibility is moot.
If, however, you happen to come across a potential customer with existing Schlage, WSE or NexWatch controllers, this information is important.
Each ACU has a specific set of Readers/Sensors and/or Keypads that may be used with it.
NSM is not compatible with:
708P
708S
Any 804/808 Model
SE 902 or 422
818SX until the EEPROMS have been changed to SC

7. NSM Can Support Up To 32 Access Control Units (ACU)
256 Readers of any combination
256 Keypads (Alone or with Readers)
1024 Input Points (DS, REX, General)
4 Windows NT / 2000 Clients
and
DataCard Photo ID Integration
The copy of NSM in the Fighter Model kits is limited to 16 Readers and two concurrent Client stations. It can be easily upgraded by re-installing the NSM program with a new CD Key that carries expanded limits. Contact NexWatch Inside Sales for details and costs.
The ultimate quantity of Readers, Inputs, etc. that can be handled by the NSM is mostly dependent on the PC itself. A late model Pentium 4 with plenty of RAM and Disk space could handle a fully loaded NSM based on the quantities posted above. It’ll never happen, however, in the real world.
If Star II controllers are used, the maximum theoretical number of Inputs and Outputs increases dramatically, but the max Readers remains at Again, PC performance is the principal limiting factor in the maximum size system that could be realistically supported.
Any number of Clients can be installed, but only two can run at any one time! This can be increased to four concurrent clients.
If the system capacity gets large enough to raise these questions, it is time to move to an EBI!

8. Easy Installation - 3 Questions
TCP/IP - Yes or No (for Remote Clients)
Display PINs - Yes or No (Keypad Only)
Enter CD-Key (Printed on CD Box)
No complex SQL or other Database Set-up or manipulation
Familiar Windows Install Interface
No Fooling!!!
If the PC isn’t under-spec or somehow corrupted, the program loads like a dream.
TCP/IP - Answer NO if there will be no additional Operator stations (Clients) other than the primary NSM PC. If you answer YES, the installer will need to provide IP Addresses for the Host and any remote Clients.
Display Pins. ALWAYS ALLOW PINs TO BE DISPLAYED unless the system is KEYPAD ONLY and very high security. (Isn’t that an oxymoron?)
The CD-Key makes the software work. It also dictates the number of Readers and Clients.

9. Cardholder Configuration
Cardholder Name and Address
Card / PIN Data
Access Privilege Information
Company Demographic Information
Personal Information Text Fields
Captured Photo ID
The Cardholder data can be as skimpy or complete as is desired by the user. Some systems use none of the 17 data fields between the Address, Look-Up and Text fields. Other customers are unhappy because there aren’t enough fields.
The only fields that are required to make a card work are General, Access and Credentials. Everything else is just data. That data, if used wisely, can be extremely beneficial to the system owner for categorizing lists of Cardholders. It can also apply extremely well in the generation of carefully filtered reports. It is all up to the system owner.
It should be obvious that the more fields that are used, the more administrative time will be required. Adequate administration manpower must be available to make use of these data fields a practical adventure.

10. Cardholder ID # and Full Name
The Cardholder ID is the master link to which all other Cardholder data is attached. You can change names, Card numbers (and even types), Access Codes, etc. without compromising the integrity of the Cardholder’s transaction history.
The Download Immediately box should be checked if only one record is being added. If a whole bunch of Cardholder records are being entered at one time, don’t check the box. Save them up and do a “Download Cards” command from the ACU Override screen to make the download far faster and more efficient.
Cardholder ID # and Full Name

11. Three Address Lines (Can be used for other data)
Purely informational. Not required to make the card work.

12. Card Type, Card Number (9 digit) and PIN
CARD - is a combo box listing all possible types of cards. Two interesting choices are “None” for a person who is only in the database for record keeping purposes, and “Keypad Only” for systems that have no cards or readers, only Keypads.
CARD NUMBER - is the actual number that the reader will send to the controller.
PIN - is the number that will be entered into the Keypad when BOTH Readers AND Keypads are used together.
For those rare, Keypad Only applications, the Cardholder’s PIN number is entered in the Card Number field, not the PIN field. This is due to the fact that the Card Number is always used for the primary credential for the individual.
Card Type, Card Number (9 digit) and PIN
PIN (Personnel Identification Number) is needed for applications with Reader and Keypad only.

13. Access Code Assignments
ACCESS CAN be the most complex dialog box in NSM. In most applications, it is very straight forward. In another window, you will have already created your Access Codes. These are simply a list of doors that will be accessible, and the hours and days for each door. Here in the Cardholder Access box, you will just select which Access Code(s) will be assigned to the individual.
For all systems using and Star I (SEEP Protocol) controllers, only 1 Code should be assigned for each cardholder.
For systems using Star II (CHIP Protocol) ACUs, up to 4 Codes may be assigned.
If a system is using a mixture of both, great care must be used to insure that multiple Access Codes, if assigned, do not include the same SEEP panel in two or more Codes.
Access Code Assignments
(Up to 4 Access Codes per Cardholder when using Star II ACUs.)

14. Configuring Cardholder Data Lookup Fields
Lookup Fields are extremely valuable for accurately categorizing your Cardholders. Lists of selections are created by the System Administrator for each of 6 possible fields. Anyone creating a Cardholder record will be able to select from the protected list. This eliminates the possibility of having six different spellings and abbreviations for Accounting that could destroy Cardholder data integrity.
Each one of the 6 available fields should be designed for use in identifying Cardholders by useful business-related characteristics.
The LABEL (10 characters) defines the category
As shown above, the System Administrator can also create a HELP TEXT that will appear at the bottom of the Cardholder Dialog box for this data tab. See next page for an example.
I started my message with the word SELECT in all caps to clearly inform the operator that they are choosing from a list, not typing data in to the field.
Configuring Cardholder Data Lookup Fields

15. These fields CAN be used for report filtering and generation purposes.
Four of the six Lookup data fields in use. The other two could be implemented at any time in the future.
Warsteiner is my favorite, but Grolsch is a close second! {:-)
These fields are usually used for data that defines a Cardholder within the workplace. Items like Company, Department, Location, Job Description, Trade Class, etc. are common Beer Choice is not.
These fields CAN be used for report filtering and generation purposes.

16. Configuring Cardholder Data Text Fields
The 8 Text Fields are just that. You give them a Label (10 characters) and a Help message, but there is no corresponding list.

17. These fields CAN NOT be used in report filtering.
Type in any desired data based on the instructions in the HELP field at the bottom of the dialog box.
Text Fields are commonly used for more personal and individual information. There are no drop-down lists, just a space in which to type a data entry.
These fields CAN NOT be used in report filtering.

18. Photo ID from DataCard Integration
Photographs can also be imported from a file. Once saved, they are kept as part of the Cardholder database in the NexSentry Manager. The images are then included in any database backup and restore utility you may ever use.
Photo ID from DataCard Integration
(Hopefully, none of your personnel resemble this guy!)

19. Intuitive Operator Permissions
Select Available System Functions
View DB Windows only or
View and Edit DB Windows
Security Levels are created and/or modified by the System Administrator. When an Operator is created, a Security Level will be selected from a Combo box.

20. To create (or modify) a Security Level, simply select the desired Operator permissions from the left-hand column and move them to the right. It is worth going through the complete list of Available Permissions at least once to become familiar with the options that exist. Armed with that knowledge, you can analyze what a given class of Operators really needs to do and build Security Levels accordingly.

21. Simplified Database Entry
Logical Data Field Descriptions
Convenient Data Entry Shortcuts
Links Between Related Tables
Many practical shortcuts exist throughout NexSentry Manager.

22. Shortcuts here are the three buttons in the Lower right corner
Shortcuts here are the three buttons in the Lower right corner. Weekdays, Check All and Uncheck All do exactly what they appear. Furthermore, the Start and Stop Time fields can be adjusted by typing directly in the Hour and Minute fields, or simply typing in the desired value.
Many parts of the Database entry function have equally clever and logical shortcuts.

23. The Door Switch Dialog boxes are typical of all hardware entry Dialogs.

24. Custom Window Configuration
Select Data Columns to Display
Customize Column Order and Size
Save Settings as a Repeatable Style Every Time You Log On
The windows are extremely flexible in arriving at the arrangement within each window, and the layout of multiple windows within the NSM Parent Window. See following examples.

25. The ability to view the data items by the usual choice of viewing styles makes it easy for the user to tailor the system to their personal tastes. Items like Time Codes are displayed well by Large Icons because the name of the Time Code is usually enough information. Readers, Input Points, Cardholders and the like are best displayed as details.

26. Monitor Window Column Selection and Sequence
Using a configuration window like this one, you can easily select which data field columns to display, and click on the header of any column to sort Ascending or Descending on that element.
In some of the data windows like Monitor, you can even arrange the order of the columns to suit your own priorities
Monitor Window Column Selection and Sequence

27. Star II Doors Table with Selected Columns Shown
The end result of a custom-tailored database window.

28. Server Performance Monitoring
Manual or Automatic Server Start on PC Boot-up
Manual Start DOS Window Follows Server Activity.
Automatic Operation State Shown In Services Window
Communication Icon in Task Bar
Diagnostics and troubleshooting are superior in NexSentry Manager due to your ability to directly view traffic between the Client and Server, and a summary of the traffic between the Server and the ACUs.

29. If you manually start the server, this DOS window opens every time
If you manually start the server, this DOS window opens every time. You can minimize it to the Taskbar, but restore it at any time to monitor Server activity. Normal polling traffic is not displayed, but all downloads and critical transfers are.

30. Clear, Convenient Monitoring
Customized Monitoring Window Format
Click on Alarm Logs to Open Alarm Servicing Window
Scroll Monitor Window and Lock in Place
User Definable Monitor Window Capacity
Whenever you first start NSM, the Monitor window opens empty. If you have saved a window arrangement, then the Monitor window will always open in the exact location and with the exact column arrangement as before.

31. Monitor Window with Customized Column Configuration
A typical Monitor window arrangement. A wise modification might be to relocate the Time and Date next to the Description column at the left side of the window.
Monitor Window with Customized Column Configuration

32. Logical Alarm Servicing
Separate Alarm Servicing Window Accessible from Menu or Task Bar
User Defined Alarm Handling Instructions
User Defined Alarm Responses for Common Alarm Events.
Custom Alarm Responses in addition to canned
Separate Alarm Servicing and/or Clearing Permissions
The two biggest issues in Alarm Servicing are:
What constitutes an Alarm? I have seen dozens of systems choking with Access Denied and Door Held Open events coming in as alarms. Nobody handled them in any way because they were so numerous and trivial. Care should be given to what is considered serious enough to be an alarm.
Who is going to service the alarms? If there is no regular system Operator, then what difference does an Alarm make? If the owner/Administrator isn’t going to invest the time and corresponding cost in a regular operator, then the alarm feature should remain unused. Exception events can always be developed in a report for after-the-fact viewing.

33. Alarm Servicing Window
All Alarm events will appear in the Alarm Servicing window. The color, text, and left-hand Icon are all user definable. Each Alarm can also have a .wav file sound associated. This sound can be from Windows Media, an external file source, or even a recorded instructive message.

34. Standardized Alarm Response for Frequent Alarm Events
Even in the most well-managed system, there are many recurrent alarms that aren’t a real security threat. People leaving doors open while the finish a smoke or wait for their ride to drive up cause any number of Door Left Open events. People still using mechanical keys instead of cards cause Door Forced Open events, ad do people who catch the door just before it latches and yank it open again.
NSM allows the System Administrator to create standardized alarm responses for these non-threatening events. Typically, only 5 or 6 are needed to cover the usual spectrum of false alarms, but the table will allow as many as the owner can dream up.
Standardized Alarm Response for Frequent Alarm Events

35. The Alarm Acknowledgement window includes a field for the Instructions that have been linked to the event. They inform the Operator as to how to handle the event.
The Acknowledgement portion includes a field to select one of the stock responses seen on the previous page. It also includes a blank field for typing a unique and specific Operator action.
The “Mark As Read” button allows the window to be closed, but leaving the alarm still active. You can come back to it later and finish the report. “Clear” closes the Alarm and removes it from the Alarm Servicing window.
Alarm Acknowledgment Dialog with Custom Instruction, Description field for canned response and Notes box for unique Operator comments.

36. Powerful Report Queries
Stored, Executable Queries
Public or Personal Saved Queries
Manually Executed Queries
Automatic Queries Daily or Weekly at User-specified Time
Simple One-step Queries for Simple Reports
One of the weaknesses in the NSM up through Revision 3.0 was the limitations of its Report feature. Revision 3.1 and later have corrected that oversight in a big way. As described in the slide above, you can now make:
Stored Reports for repeated execution
Private Reports usable by the writer only
Public Reports usable by any Operator with permissions
Automatically executed reports, daily or weekly
Quick reports for simple requirements
Let us not oversimplify the feature; building a query can be a complex and challenging exercise. Once a good Query has been created and saved, however, it can be run over and over again with exactly predictable results every time.

37. Transaction History Report Creation Example
Select
Field = Transaction Type
Operator = Equal To
Value = DOOR FORCED OPEN
Then click on Add Condition to Query
The combination of choices will be moved to the Query box.
A Report consists of one or more Query elements created in the three fields at the top of the screen. Every Query element will require some combination of the three fields.
The Saved Queries, and Auto-executable queries only apply to Transaction Logs and Cardholders. The rest of the database reports are usually much simpler and are run far less often. They do not require the sophistication and complexity represented it Log History and Cardholder data.
Transaction History Report Creation Example

38. In the example above, a second element is added to the Query to further narrow, or filter the search parameters.
Repeat the selection process for the second set of conditions.
Use the And Clause, then click Add Conditions to Query.

39. Repeat the selection process for the third set of conditions.
Use the And Clause, then click Add Conditions to Query.
When the query is complete:
Click Execute to run the completed report one time or
Click Save to keep the query for future repeated use
Yet a third element is added to the query giving the creator an exact set of limits as to what will be in the Report.
Once completed, you can Save it if you expect to run it repeatedly, or simply Execute it to run it one time only.
I would recommend saving the report if it was complex to create until you are sure it yielded the results you wanted. Once created and saved, the Query can be modified to further tailor it to your exact requirements. It can always be deleted if it is no longer needed.

40. Running a Saved Query Report
The Dialog box above allows configuration of an automatically executing report. This permits you to generate, for example, a Report of all Access Granted Transactions over the weekend to be run and waiting for the Security Manager at 08:00 Monday morning.
As shown above, the Report can be routed to any or all of the following:
Screen
Printer
Selected PC file, either on the PC itself or anywhere on the accessible network.
Running a Saved Query Report

41. Filtered Cardholder Query Report Example
Cardholder Data can also be carefully filtered in a Report and the Report can be saved for future use. This is where that data in the Lookup tables is so valuable.
With good data, you can filter a report down to all Cardholders who are in the Accounting Department in Topeka Kansas and favor Oertels 92 beer. That aughta be a short list!
Filtered Cardholder Query Report Example

42. Monitor Operator Actions
Overrides (Unlock, Shunt) Shown as Part of Transaction Log
Database Changes Shown in Separate Operators’ Audit Log
Audit Log can be Archived and Recovered
Remember, Overrides like Unlock, Shunt, Etc. are part of the Transaction Logs.
Database changes like adding a Cardholder, modifying an Access Code or Deleting a Reader are in the Audit Trail Log.

43. Operator Database Additions, Changes and Deletions
Typical section of an unfiltered Audit Trail. You can apply filters here, too, such as a specific Operator,and a specific type of database action.
Operator Database Additions, Changes and Deletions

44. Audit Log Archiving Dialog Saves Old Audit Log Info
Like the Transaction Log file, the audit Log file will grow over time. It can be archived between a specific set of dates and times and placed on any file that is accessible from the Server PC.
Audit Log Archiving Dialog Saves Old Audit Log Info

45. Easy Database Backup
The NSM Database can be copied and pasted to any folder that is accessible from the Host. If the NSM working database becomes lost or corrupted, the backup can simply be copied from its safe location and pasted back into the NSM file.
Make Backup by clicking Copy on current DB, then Paste into a Backup Folder with a Specific File Date

46. Brought to You By:
Doug LaVenture - Regional Sales Manager 510/
Bill Richardson - Chief Explainer 510/
Jim Thompson - Man Behind the Curtain 720/
What more can I say???

47. WCR 12/2002