1 / 50

Miller / Coors

Miller / Coors. System Criteria. Server Redundancy.

elpida
Télécharger la présentation

Miller / Coors

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Miller / Coors System Criteria

  2. Server Redundancy • The DSX-RMS1076 Redundant Monitoring System provides continued availability of System Communications and Control through the implementation of Primary and Backup Communication Server PCs. Available only with WinDSX SQL the Hot-Swap Supervisor program runs on the Backup Comm Server PC and monitors the Primary Comm Server. When the Primary fails all communications are redirected to the Backup (Redundant) Comm Server. • LAN connected locations are transparently transferred to the Backup Server and with the use of a DSX-SPS Serial Port Switcher all direct serial port connected Locations are also switched automatically. WinDSX SQL Workstations automatically switch to the Backup Server and continually display which Comm Server they are talking to. This feature requires the purchase of the Hot Swap Comm Server software and optionally the DSX-SPS Serial Port Switcher. • Both Comm Servers are defined in the system as either the Primary or Backup Comm Server and both PCs have static TCP/IP addresses. Both PCs are running at all times. The Backup Comm Server PC runs the Hot Swap Supervisor software. The Supervisor Software polls the Primary Comm Server. Once the polls have failed for a predetermined amount of time the Supervisor Program starts an instance of Comm Server on the Backup PC. The Supervisor Software also initiates any hardware switch over that needs to take place (direct connects) by sending the appropriate commands out a serial port to the DSX-SPS Serial Port Switcher. The Workstation program on all PCs in the system will automatically switch to the Backup Comm Server when the Primary Comm Server fails. The Workstation program has a real time status display that shows which Comm Server is on line. The Hot Swap Supervisor Software has a Stop button that allows the Backup Comm Server to be shut down, the Primary Comm Server to be restarted, and the serial port connected communications to be returned to the Primary Comm Server. • LAN connected Location Master Controllers must have a Dynamic IP Mode connection that automatically communicate with the Backup Comm Server PC.

  3. Server Redundancy System Software Operational Diagram Redundant Comm Servers

  4. Archiving inactive profiles • Card Holders can be quickly deactivated shutting off access with all credentials that person may hold. Cards can be shut down by deactivate date, number of uses or a lack of use. Cards can also have their access level removed. Cards that are made inactive by any of these methods are still accountable and reportable in the History report writer. • Card Holder Reports can be sorted by company and active / inactive status. UDF: De-activate Date • UDF Fields can be used in place of the de-activate date field found under Card Holder / Card #. When the date entered for the card holder becomes current the Comm Server performs a download and de-activates that card. This automatic task is performed after midnight each day. • Multiple De-activate Dates can be deployed allowing multiple dates to control use of the card. This could be training, safety or other certifications that must be renewed by a certain date.   Number of Uses Allowed • This sets the number of uses this Code will be allowed. This is the total number of uses at all readers in the Location Group. 9999 is unlimited number of uses. By setting a lower number, the code will only operate that number of uses. Once the limit is set, this field will decrement each time the code is used and will show the remaining number of uses. When the limit has been reached and the field shows 0 the Comm Server de-activates the code and initiates an incremental download to the controllers. • The "Cards expire when used at the reader" feature enabled under Device sets the number of uses to 0 when implemented. Company General Tab Use it or Lose it Days • Enter the number of days a card holder can go without using their card before their card is deactivated. This applies to all card holders assigned to this company. If this Location is part of a Location Group this is the number of days the card is not used in any location in the group. As long as the card holder uses their card in any location in the group within this specified number of days their card will stay active unless the card is de-activated by some other means.

  5. Partitioning / ability to customize viewing and control at each site Password Profiles In Password Profiles there are 7 categories that can each be customized detailing exactly what the operator, with that profile, could do. All Locations: If selected you will have permissions to all locations, deselect this category and choose the locations an operator with this profile should have permissions for. Only selected locations will be displayed in Database and Workstation. Further restrictions may be placed on what the Operators may do within each of those displayed locations. All Menus: If selected the operator with this profile will have permissions to all menus with full capability. If not selected you can determine add, edit, and delete capability to all items in the database. This includes "Operator Comment, Operator Password, Password Profile, Reports, Setup, System Parameters, Database Path, Comm Ports, Event Filters, Image Source, Backup Database, Backup History, or Restore/Repair Data. Under Locations you can limit which locations can be Viewed, Added, Edited, or Deleted. When expanded under Locations, Workstation and Database access can be limited. Guards typically use the Workstation only, and Supervisors and Data entry personnel typically use the Database. This is also the area where Hidden UDF fields are enabled and Alarm Acknowledgement is restricted. All IO and Device Overrides: If customized this can determine which doors (readers and locks) and alarm points the operator can manipulate in Workstation. This section includes all inputs, outputs, devices, and cameras viewable in Workstation. You can customize exactly how they can manually manipulate each door. This keeps the user from unlocking high security doors that they may not have privileges to. This also can determine which floors an operator can assign to a card holder when assigning access in elevator control. All Companies: This category limits the user access to only specific companies. A company is a group or department of card holders. Companies selected here allow the operator visibility and control over the card holder in those companies. These are the only card holders the operator with this profile will be able to see. All Card Fields: This category determines what Card Holder data can be viewed or edited in the Database program. The profile can limit access to "Code #, Imprinted Card #, P.I.N #, Start Date, Stop Date, # of Uses Allowed, Guard Tour, Notes, Access Level, or Linking Level.” Access Level All Devices: This category defines what doors and access levels can be assigned to a card holder by an operator with this profile. This include adding new or editing existing card holders. Restricted To Visitors Only: This option can be selected to limit the operator with this profile to only managing visitors.

  6. Partitioning / ability to customize viewing and control at each site Password Profiles determine what the operator can add, edit, and delete. It determines what doors they can control through the workstation program. Operators can each have their own individual profile or they can share profiles with others that need the same permissions. Event Filters determine what events the operator can see in the Workstation Real Time scrolling window. This includes all card reads and alarms. The event filter can be very specific and has a granularity of each reader and alarm point on each controller in each location.

  7. Hardware upgrade capabilities / adaptive to technology • DSX Intelligent Controllers are independent processing 2 door packages designed to be cost effective building blocks that allow expansion in a scalable manner. Up to 8 doors can be controlled from 1 enclosure for an efficient space saving package. Each Controller operates as a fully intelligent and independent control panel that retains all data necessary for system operation in its own RAM. With its integral real-time Clock and Calendar it performs Time Zone control with Holiday overrides for inputs, outputs, and cards even when communication to the PC or other controllers is not available. We have engineered one of the finest controllers in the industry. Each of these controllers has been designed for a specific purpose and tested to meet those needs. All DSX Controllers are designed and built for commercial and industrial use and carry a UL 294 and 1076 listing. • The intelligence in these controllers allows them to be compatible to over 250 different card/reader and keypad formats allowing many of them to be used in the system at the same time. New reader/keypad formats can easily be downloaded without touching the controllers. • The panels can also be field upgraded (flashed) to add new features and functions. The latest panel flash code is available at no charge and comes with the latest software. • The DSX-NV Processor is a replacement processor with nonvolatile memory that provides a layer of resiliency to any existing DSX system. The processor will retain its memory and allow a controller to be immediately operational upon power up without the need for a download from the WinDSX Communications Server. The DSX-1040NV Processor can be installed on all DSX-1040 Series and all DSX-1022 Controllers. Once this retrofit processor is installed on the Master Controller, it will become operational on power up and if called upon, will download any subsequent Slave Controllers providing them with the data required to make them fully operational. In addition, this processor can be installed on any or all Slave Controllers in the same Location to provide even further operational resiliency.

  8. Hardware upgrade capabilities / adaptive to technology DSX-1040NV Non Volatile Flash Memory upgrade processor. These processors have non volatile memory and retain the database download and will allow a controller to be fully operational upon power up Wireless Receivers are just one more device that works seamlessly with the DSX Controllers. Integrated Wireless Locksets contain the reader/keypad, lock, door position switch, and exit request in a single wireless package. • Bluetooth • Near Field Communication

  9. Hardware upgrade capabilities / adaptive to technology • Technology Partners

  10. System status (health) monitoring • The Workstation program shows all Devices (doors/Readers) in each Location and their real time condition. If a controller is offline the Red Not Symbol will be shown for that Device. • The Device Summary Screen shows the communication status and version of each controller. This screen also show the number of missed communication polls and which panel last missed a poll. • The Device Details screen shows a snap shot of a Device and the state of its power and all of its inputs and outputs.

  11. System status (health) monitoring • Workstation: Location Operations – Print System Exceptions • From Workstation a System Exception Report can be run (especially at shift change) that will notate anything that is not normal. • This report is typically performed at shift change for a quick accountability of the overall system status. The report will print a list of any input that is in alarm or has been bypassed. It also shows any door or output that has been manually unlocked or overridden, any reader that has been disabled, and all controllers that are off-line and not communicating.

  12. User Monitoring • The Operator Actions can be tracked through three different Reports: Starting at the top right: • The DataBase History Report will show what the operator changed. • The Scheduled Override Report which will show the override schedules of all doors. • History Report which will show what interactions the Operator has had such as unlocking doors or acknowledging alarms. History reports can be preconfigured and saved and can even be scheduled to run automatically.

  13. Compatibility with current architecture (CCURE, fiber, panel etc.) as possible • DSX is compatible to over 250 card reader/keypad and card formats. DSX Controllers will work with any wiegand output device. • DSX Controller communication will work with most protocol independent communication devices such as fiber transceivers, LAN serial servers, USB to RS-232/RS-485 and RS-232 to RS-485 converters.

  14. Administrator control of badge templates • Badge Templates are the predefined badge layouts. The layouts are easily constructed and viewed. • These layouts can contain any card holder data field, images, graphics, static text, variable text, bar codes, magnetic stripe encoding, and 2 sided options. • The Badge Templates can be assigned to a Company so when a Card Holder is assigned a company the appropriate badge template is automatically selected. When printing, the template selection can be overridden and a different template chosen.

  15. Door Monitoring Input Status (door position open or closed) • Doors Status is monitored in real time. You can see the status of all Locks, Door Positions and Readers (devices) from the Workstation Client program. The Icons will change in real time to show a door open, unlocked, or a reader offline. Output Status (door locked / unlocked)

  16. Door Monitoring • Device Details is a real time dash board that displays the state of all inputs and outputs, ac power, backup battery, and the controller make, model, and revision. Device Status (reader/controller comm) Device Details (full door and controller status) • Remember to run the System Exceptions Report from the Location Operations Menu in Workstation at Shift Change. This report provides a quick accountability of the overall system status. The report will print a list of any input that is in alarm or has been bypassed. It also shows any output that has been manually overridden, any reader that has been disabled, and all controllers that are off-line and not communicating.

  17. Alarm Monitoring When a door or other input goes into alarm the Workstation can annunciate the alarm visually and audibly and provide instructions for the operator to take as a result. Alarm Monitoring is an integral part of WinDSX. Each input alarm has the following configurable attributes that can be individually assigned. Circuit Type – electrical configuration and wiring Priority – is it more or less important than other alarms Abort Delay Time – how long does it have to be faulted for alarm Action Message – instructions for operator to follow for alarm Audio File - WAV file to play when it goes into alarm Display Order – the order it is displayed in Workstation Map – graphical map to display with interactive ICON Camera – associated video camera to display on alarm Requires Restoral to clear – input must return to normal to clear alarm Requires an Operator Comment – must enter comment to clear alarm Icons - interactive Icons for normal and abnormal state Time zone – up to 4 time zone schedules to arm and disarm Linking – Can initiate a link to inputs, outputs, and time zones on alarm or just abnormal condition Notification – Can cause email or text message notification

  18. Automatic control of doors and schedules • Most functions in DSX are controlled by "Time". Time Zones are the automatic time of day/day of week schedules where start and stop time parameters are defined to perform automatic functions such as lock/unlock doors, arm/disarm alarm monitor points, enable/disable readers, granting/denying card holder access, enable/disable image recall, and enable/disable alarm echo. • Enter the Start Time and Stop Time For each day including holidays. Create different Time Zones for each particular use such as Inputs (alarm points), Outputs (locks/gates), Access Levels (allowed times and readers), Devices (readers/keypads), Image Recall (display card holder photo), Alarm Echo (retransmit alarms off-site). • The Start Time is when the Inputs - Arm, Outputs - Secure, Access Levels - Grant Access, Devices - operate and become required for entry, Image Recall - displays card holder photo, Alarm Echo - retransmits alarms off-site. The Time Zone in the example below would Lock the Door at 5pm and Unlock it at 8AM Mon-Fri and keep the door locked all day on Saturday and Sunday and Holidays. • Scheduled Overrides can be programmed to force an input and or output to a particular state by date and time and can automatically return it to its normal time zone state by date and time.

  19. Manual control of doors and schedules All inputs and outputs in the system can be monitored in real time and manually controlled through the workstation program. Each input and output has two icons that automatically change to reflect the true real time state of the point. Right click on the point to see the command menu available to the operator for that point. From the command menu select the manual state you want the point to go to or select scheduled override to manipulate the point on a date and time basis. Override Groups are comprised of either Inputs or Outputs. These inputs or outputs would have a single set of Icons for the normal and abnormal state of all the points in the group and allow for single action control. The groups can be expanded for individual control and status. You can program a scheduled override on an override group for multi point control. The Operator’s password profile determines exactly which of the options seen on the command menus, in the screenshots below, are available for each device (reader), input, output, and camera.

  20. Creation and Assigning access levels to badges • Access Levels are the describing elements that determine what readers or keypads the card or code will work at and when. These selected doors are assigned up to four time zones that describe which days and at what times on those days, the card or code with this access level will allow entry. One time zone per device is typical. Two to four time zones can be assigned in situations where it is desirable to have an access level that allows access up to four distinct time periods in the same day. Access Levels can be one door or multiple doors and even doors in different locations. • The Edit Access Level Tab is where the Devices and Time Zones are joined to form the Access Level. The List Access Levels that Contain Device Tab is where you can go to find all of the access levels the selected Device is In. • Under Card Holder / Cards / you can assign one or many access levels to the card. Drag the levels from the left to the right side of the screen. Temporary Access Levels can be assigned to start and stop on a date. • Operators can only assign access levels that contain doors they have permissions to assign.

  21. Access monitoring Workstation: Monitor Window • The Monitor Window is the scrolling window that displays all location activity as it occurs with a time and date stamp. Use the Scroll Bar to page back through the last 100 lines of up to 100 events. The events scroll from top to bottom. All events including alarms are displayed here. • The Event Message Format is Month/DayYear – Hours:Minutes:Seconds – Location Number – Event Description – Device/Point name – Card Holder Name • Click on an Access Granted message or an Access Denied message in this Monitor Window to have the system display the Card Holders primary image. The image will be displayed until another image is requested or until the display is closed. The Image Recall Window is closed by de-selecting it under the Customize Menu at the top of the screen.

  22. Customizable Reporting History allows the user to view and print the event logs and historical data currently stored on the SQL Server. The history report may include all activity for a location or all locations, a door or combination of doors, all events or just specific events, all card holders or combinations of card holders. This is accomplished by answering a series of questions on what is to be included in the report. The report can be viewed, printed or saved to a file in one of many different file formats. Any History report that has been defined and saved, can be set to run automatically at predetermined times. Each Report can be set to run twice a day by entering the times to the nearest half-hour. Reports can be saved with a date offset for weekly or monthly reports. Each Report can be set to run on any or all days of the week. Automatic Scheduled Reports can also be configured to be sent as Email.

  23. Customizable Reporting

  24. Panic alarm integration Activating • Activating the Emergency Response plan can be from the use of wired or wireless panic buttons or holdup type devices. It could also be as subtle as opening or closing a particular door, entering a PIN code into a keypad, or presenting a card to a predetermined card reader. It could even be clicking on an Icon in the WinDSX workstation program running on a PC. Any number of items can be used as a trigger. These activations can be customized to fit your specific needs and environment. Action / Lockdown • Upon activation, the system can quickly lock all or selected doors. It can activate gates, roll down barriers and release door holders. It can turn “on" or "off” any electrical device, beacon, lights, or sounder. Card Readers can be disabled or just restricted. General Access can be restricted disallowing most cards to get through all or selected doors. Administration Cards could continue to work everywhere or just where determined. First Responders could have cards that don't work at all and as a response to the threat, are automatically given full access. Access to doors can be restricted and altered in a moment to make areas inaccessible to possibly compromised cards while giving access to emergency personnel cards. Communication / Notification • While the system is actively locking down and reconfiguring, notification can be sent to all or selected Staff onsite as well as offsite via email and text messages. Digital communicators can be activated to notify a 24 hour Monitoring Center for notification of authorities. Intercom and PA systems can be configured to play an emergency warning or set of instructions.

  25. Elevator access control Floor Select Elevator Control • WinDSX fully supports Floor Select Elevator Control and is capable of providing full elevator security. There are two ways the WinDSX System can secure the Elevator. • The simplest method is to disable the Car-Call Buttons on the common level or ground floor so that the Elevator cannot be accessed until a valid card is used that enables the car-call button. The upper or secured floors have free access to the elevators. This requires just one reader and one relay output for each car-call button on the floors that need to be individually secured. • The next method is to disable all or particular Floor Select Buttons in each Cab. A reader is placed in those cabs and presenting a valid card enables the Floor Select Buttons the user is authorized for. This restricts all passengers to the floors that their access code allows. • The typical system utilizes a card reader in each elevator cab. The DSX System can be configured and programmed to automatically secure and unsecure any or all Floor Select Buttons in a cab individually, by time and day. Once a Floor Select Button is secure, it requires the passenger to use their access code or card at the reader in the cab before the select button will operate and light when pressed. • The passenger's access code determines which Floor Select Buttons are to be enabled for them to press. This restricts the passenger from selecting buttons that correspond to floors they are not authorized for. The floors enabled can be different based on which reader the card is read at.

  26. Holiday schedule management Time Zones are the automatic time of day/day of week schedules where start and stop time parameters are defined to perform automatic functions such as lock/unlock doors, arm/disarm alarm monitor points, enable/disable readers, granting/denying card holder access, enable/disable image recall, and enable/disable alarm echo. A specific date can be defined as a holiday so that all time zones will follow a different time schedule on that day. This feature is used to override normal time zone parameters on a specific date. When a date is defined as a holiday, all time zones will follow the time schedule assigned for their holiday. All Time Zones have a day of week schedule with three holiday overrides. If a time zone has a holiday schedule of 0-2400 when a date that is defined as a holiday becomes active, all items using that time zone will be active all day. That is, outputs will secure, inputs will arm, and access levels will be valid. A time zone that has a holiday schedule from 0-0 will be inactive on a holiday. That is, outputs will open, inputs will disarm, and access levels will be invalid. Holidays can be imported through the ASCII import text file. See the software installation manual for details.

  27. Scalable to allow additional large and small sites to be added • The WinDSX System is scalable from a single PC to an Enterprise solution. A single PC and single Controller can grow into 999 PCs with thousands of Controllers. With its wide variety of features the WinDSX system is flexible enough to fit almost any application. • DSX Intelligent Controllers are independent processing 2 door packages designed to be cost effective building blocks that allows expansion in a scalable manner. Up to 8 doors can be controlled from 1 enclosure for an efficient space saving package. • Symmetrical Scalability allows the system to grow location by location. Each Location can be a single door or up to 128 doors. In applications requiring more than 128 doors multiple locations can be grouped together to form a larger system. • There are no software fees to add a door, a location or a workstation. You are free to grow and change your system as you see fit without constant up charges.

  28. Integration into other systems DSX Advanced Integration Partners • Que Accounting Inc. – is a long time partner of DSX and has developed several advanced applications that integrate with the DSX system. Advanced Applications include: Time and Attendance, Job Costing, Visitor Management, Gatehouse Management, Parking Garage Monitor and Count, Trackit Suite, Day Care Security, Session Attendance, and Inventory. • Identity One is a global biometric solution provider whose solutions are tailored to Access Control, Time & Attendance, Electronic Key Management and Criminal Justice. Identity One now offers a seamless interface with DSX. This new integration delivers a simple and secure way to migrate DSX users from traditional card based access control to biometric access control. • EasyLobby®, the industry leader in secure visitor management solutions, has an integration module that seamlessly integrates DSX access control and EasyLobby's SVM (Secure Visitor Management) software • Integrated Biometrics can seamlessly integrate the TRU650 biometric fingerprint reader with the DSX enterprise access control system. • The Lobby Track solution streamlines the registration and credentialing process for a visitor who needs to be issued an access card. Selected visitors are simply assigned an access card and activated. Lobby Track automatically creates an account for these visitors in the DSX system and assigns the appropriate access level and expiration date. Records that need to be deactivated and removed are also managed through Lobby Track.  • DSX is compatible to almost 20 different DVR/NVR Systems: Avigilon, Cascadia, Video Products, LLC Prowler Sentry, Dividia Technologies, Exacq Technologies, Inc., HIKVision, I Watch LPM / XP, JDS, Milestone Systems, NUUO VMS, ONSSI, OpenEye, Panasonic HD300 DVR, PelcoEndura, Salient Systems, Say Security Group USA LLC, Sigmax, Strand, ViconNet, VideoInsight SDK and Test program available at no charge. • DSX DataBase Management API is available to developers at no charge.

  29. SAP data import Database Management API • This Database Management API can be used by anyone that wants to develop an interface to add/edit/delete data in a WinDSX or WinDSX SQL system. It can be used to place the initial data into the system and it can be used as a real time interface for ongoing data manipulation. • The API is designed to insulate other systems from future changes in the DSX database structure by providing a consistent interface. Regardless of changes made to the DSX software or database schema your interface stays the same. • Building this interface requires teaching the other system to save the data into a text file formatted to the DSX Markup Language (DML) specification. In the API document there will be clear examples of adding a person to the system, giving that person a card, changing and deleting cards, assigning access levels and more.

  30. SAP data import • Below are the Four main points of Interest when developing this API. The entire API contains the DSX Markup Language and it special commands accompanied with many examples covering different situations. • 1. Unique ID - When trying to coordinate card holder data between 2 separate systems there must be a unique identifier for each person that both systems can agree on. The unique ID (UID) could be anything that is guaranteed to be unique, such as an employee ID number. This UID will be the key that both systems use to identify the card holder records. Further manipulation of the card holder information will require the use of this number. The UID is stored in a User Defined Field (UDF) in the DSX system. User Defined Fields are used in the DSX software to store custom data of a card holder. • 2. Method - The Card holder information including the “Identifying Number” is written in a text file according to the DSX Markup Language Specifications and placed into the WinDSX shared database folder. Multiple records could be included in a single DML text file. It is acceptable to create a file that makes multiple changes such as add 5 people, edit two cards, and delete 3 people. The best method is to create the text file locally and then copy it into the shared directory. Each file can have an incrementing number in the file name so that many files can be placed in the “Shared Folder” at the same time. Once the file is placed in the shared folder Do Not Append data to the file! Place new or additional data into a new file. Once the data has been read from the file by the DSX system the file is deleted. For example file names such as the following could be used: ^Imp01.txt, ^Imp02.txt, ^Imp03.txt • 3. Integration Responsibility - The Comm Server PC typically processes the DML text files. The processing of the files on the comm server PC is intentionally slowed down so that it does not interfere with the comm servers other duties. For most systems the performance is acceptable. Systems that will be repeatedly sending a large number of records in a single file can specify a DSX Workstation on the system to process the DML text files at a much higher rate. Refer to the Daily Ops page in the software installation manual. at the end of this document. • 4. Required and Coordinated fields - There are specific DSX database fields used in the Interface. The names and numbers of these fields must be coordinated between the two systems. The Coordinated Fields section of the API document explains this in depth.

  31. Centralized SQL DB Centralized databases. • DSX has two different versions of the WinDSX software. Our traditional WinDSX software and a version called WinDSX SQL. The difference between the two is the type of database used to store the system information. The WinDSX software uses Microsoft Access files to store data and the WinDSX SQL software uses Microsoft SQL Server™ to store data. • There are several differences between storing data in Access files and SQL Server. In order to define these differences I have to talk a little about how each one works. When using Access to store the data we have a centralized shared set of database files that reside on a file server. Each of the WinDSX workstations is capable of reading and writing data to and from the shared files. Each workstation is responsible for looking up data on it’s own as well as it is responsible for writing any changes into the database. With this type of a system you can see that there is a possibility for several different workstations to be reading and writing to the database at the same time. Also each workstation is pulling and pushing all of the database info through the LAN, which uses up bandwidth. • When using SQL Server to store the data we have a centralized set of database files that reside on the SQL Server PC. Each of the WinDSX workstations uses TCP/IP to make requests to the SQL Server. The SQL Server program executes the request and returns the results. This is very different than how things happen in the shared Access database. When you use the Access version each workstation actually “touches” the database. With SQL Server only the SQL Server program touches the database. This results in a database that is much less susceptible to corruption. The risk of database corruption is decreased in two different ways. First the liability of a network error causing corruption is eliminated as the only program that touches the database is the SQL Server which is running on the same PC with the database. Second the possibilities of simultaneous or conflicting writes to the same records are eliminated, as the SQL Server program will only service one request at a time. • Additionally SQL Server is designed to handle very large database files and a high number of users. Increasing resources (speed, RAM) to the SQL Server PC without making any hardware changes to the Workstations can enhance your systems overall performance. SQL Server also provides more security for the system data, as it is much harder to get to the data.

  32. Centralized SQL DB • Basically SQL Server stands between the world and the data. Its job is to protect the data from unauthorized access, maintain the health of the database, and respond to requests from the workstations. However this additional robustness and security comes at a price. There needs to be a PC dedicated to running SQL Server. Microsoft SQL Server has to be purchased, and someone will have to administrate it. Setting up and maintaining a SQL Server PC is a profession; people who do it are called Data Base Administrators (DBA). • SQL Clustering or high availability configuration can be used for maximum up time and seamless fail over. A Primary and Backup SQL Server can be used for a manual switch over.

  33. Granular admin controls: user permissions, PC permissions • 999 Operators with 999 Password Profiles Each Operator can have their own profile that determines what permissions they have in the DSX Software. Operators can also share password profiles. • Active Directory Authentication can allow operators to use their PC user name and password to login to WinDSX conforming to the companies complexity and change rules. Once logged in the operator permissions are based on their password profile. • Each Operator must have access to the two databases in the SQL Server, to the local windsx folder where the software is installed, and the shared folder where images (optional) are stored. The Shared folder contains maps, images and badge graphics and other configuration files. • A Profile can give the operator admin control over a specific group of card holders and could allow them to lock and unlock one door and only lock another. Complete granular control over each door can be assigned to each operator.

  34. Multilayered time periods being assigned to badges (temp access / contractor) A Card holder can be assigned one or many access levels. One access level can provide access during 4 different spans of time in the same day for each door. Date driven Temporary Access Levels can be assigned to a card. When the assignment expires the card can revert to a permanent level or it can end up with no access level.

  35. Multilayered time periods being assigned to badges (temp access / contractor) • Access Levels and Temporary Access Levels can be assigned to more than one Card Holder at a time using the Bulk Load tool that is an integral part of the DSX software. • Multiple Card Holders can be selected based on Company, Name or Card Number, or UDF and can have a Date Driven Temporary Access Level Assigned. • An Output Icon in the Workstation program can be used to enable or disable a time zone(s) used in an access level. In just a click any group of cardholder could be given access or have access restricted at any or all doors. This can be part of an emergency lockdown or panic situation. • This same output which gives access level control, without downloads or database changes, can have a scheduled override assigned to automate the action by time and date.

  36. Customizable UDF fields • Up to 99 User Defined Fields per Card Holder • When defining these UDF fields there are • Data is Required – forces operator to enter data • De-Activate Date - to provide a way to disable cards for training or drug testing. • Auto Incrementing Number – for incrementing a badge printed number on an ID Badge. • Data choices to be selected from a list. Allows for uniformity when entering data chosen from a pre-populated list. • Only select data from a list. – Locks in the UDF field to only accepting the data from the pick list. • Data is Email Address – provides a place to enter an email address for email or text message alarm notification • Data Must be Unique – Forces the Operator to make a unique entry that is different from all other card holders. • Name ID – used with DSX Card Holder Mgmt API. This API is a way for other systems to manipulate card holder data. • UDF is hidden – prevents unauthorized Operators from seeing the Data entered.

  37. Integration into FLS alarms nodes (fire, chemical detection) • DSX can integrate and monitor any system with dry contact outputs. Input Monitoring can be performed with any DSX controller. The DSX-1044 is an input controller with 32 inputs. • DSX has the ability to integrate with various different external devices through serial data streams. This integration allows other systems such as elevators, intercom, HVAC, fire alarm, etc., to interact with the DSX network of controllers through a serial data or TCP/IP link between the systems. • Supports Virtual Inputs and Outputs • User Defined Command Strings – In and Out • Supports open and proprietary protocols • RS-232/485 / TCP/IP Communications • What Can It Do? • The DSX Soft I/O product will allow you to integrate DSX Access Control with different systems exchanging input and output status with an open protocol data stream. • Now you can use one software package to monitor and control multiple building systems. You can even program action/reaction linking events between diverse systems. • The DSX Soft I/O can be thought of as a universal translator. It can speak to multiple systems simultaneously and control interaction between those systems based on logic that you define.

  38. Advanced alarm graphics or GUI interface capable of importing CAD drawings Graphic Maps can be imported into WinDSX. CAD drawings can be used along with other file formats. The Map imported should be close to the size it should be displayed as. Inputs, Outputs, Cameras, and Override Groups Icons can be placed on the Maps to give real time status and control of those hardware items.

  39. Integrate floor plans / interactive maps • Graphic Alarm Maps can be imported into the system for alarm annunciation, Input, Output, and Camera Control. • Several different graphic file formats can be imported into the system. The General Tab is where the graphic alarm maps are imported into the system. The I/O Points Tab is where the desired inputs, outputs, and Cameras are placed on the Map. • Once the graphic file is imported it is saved in a .bmp format in the Maps subfolder under WinDSX. It is saved in 24 bit color at the size of the original file. • The Width and Height of how the Map is to be displayed in Workstation can be defined for each map.   • It is possible to have to have a Startup Map that is always on display with the interactive Icons showing real time status and allowing real time control.

  40. Intrusion alarm integration • DSX Can integrate with intrusion alarms systems in several different ways. • Reader controlled doors can be monitored by DSX and when the door is in alarm, DSX notifies the intrusion system of the alarm. This allows the door to be bypassed by DSX for normal card and door traffic. • Another method is when a particular person cards in a preselected door the intrusion system is disarmed. Subsequent reads to not rearm the system. The intrusion system is rearmed with the intrusion system keypad. • DSX can monitor the alarms of multiple intrusion systems through the SIA output of a digital receiver using the DSX-SIO program. All of the alarms that would be processed by the digital receiver would handled in WinDSX like alarms from a DSX controller. All of the different attributes allowed to DSX inputs would also be available to these intrusion inputs.

  41. Integrate man down buttons • Man Down buttons can cause an alarm on the WinDSX Workstation program. This could initiate email or text messages and could active horn strobe devices to alert others and assist in pinpointing where the person is. • Cameras in the area of the button alarm could display video for that area. • A DSX Output could be activated by the Man Down Alarm and this output could be used to suspend or terminate a process or piece of machinery.

  42. Emergency Assembly areas / headcount readers • Who Is In Report • The "Who is In" is a Life Safety report that provides a list of Cardholders that are shown to be In a selected area or premise. The inclusion of the cardholder in the report is based on their Zone 1 APB status as being IN for the Location of their last card read. The report can be sorted by Company or by Device (In Reader) location. The report is conveniently initiated from the Who Is In Report Button (factory) in the toolbar located at the top of the DataBase program or can be run from the Who is In Report in the reports list. (APB stands for Antipassback) (device represents reader). • The Who Is In report only displays people whose last card read was within 48 hours of when the report is run. This will exclude people who never card out. • Who Is In requires at least 2 Readers. • Wireless Readers could also be used to help facilitate who is still “in” at the Muster site.

  43. Integration into business operationsEquipment checkout - PPE Vending machines In/out bound truck lotsTime & Attendance • DSX can work with any “one card” solution that will work with these systems. WinDSX Time and Attendance • Time and Attendance (T&A) is an integral feature of the WinDSX System. WinDSX gathers clock “In” and “Out” times for each user. The operator can then run reports based on the clock “In” and “Out” times of each employee. These reports provide the total number of hours worked per day for each employee and a total number of hours worked for the report period. Reports can be printed or saved to a file. • Any reader or keypad in the system can be defined as Time and Attendance / clock “In” or “Out”. Two readers or keypads are required for this function. One reader is defined as Time and Attendance “In” and one as “Out”. These could theoretically be any two readers in the system, but the system works best when there are two readers dedicated for this purpose. These two readers would most likely be placed in a common or centralized location such as employee entrances or break room. It is possible to have more than one set of Clock In/Out Readers. • These two readers coincide with a DSX Time Display Module (TDM). This Time Display Module is a seven-segment LED continuous display with one-inch numbers. This synchronized clock or Time Display Module would be placed next to the clock “In” and “Out” readers and connected to the same panel.

  44. Asset / Key tracking WinDSXKey Tracking • Key Tracking provides the ability to create a database that catalogs each key in the location. (We are referring to the conventional metal keys used to unlock doors). Each Key has a name, door description, key type, pinning, and notes field. These Keys are then assigned to the cardholders to record who has keys to which doors. There is a special Key Holder Report that prints a list of everyone that has possession of the specified key. Key Defining • Below is a look at the screen where Keys are defined. Any Key can be selected from the list and a report printed showing all card holders that have been given that same key. Key Assignment • Under Card Holders is where the Keys are assigned to people. One or more keys are selected from a list and assigned to a card holder. Card Holder reports can be configured to show keys assigned to each person in the report. Key Return • When a Card Holder returns a Key, the Key Name is double clicked on and the Key Returned field reflects it has been returned. Card Holder Reports and Key Reports are a great way to keep up with who has what key that works in which doors.

  45. Notification/ linking logic internal to site (based off of predefined events) • Controllers can perform Local (within a controller) as well as Global (throughout a Location) I/O linking. Linking is very flexible with many capabilities. With this flexibility it is simple to perform I/O interlocking without the use of PLCs, timers, and external relays. This powerful new linking logic provides DSX the ability to fulfill applications such as Man Traps, Do Not Unlock Door Until First Card Read, and other assorted interlocking functions. • Inputs can link to other inputs, outputs and/or to time zones. Linking to an input allows for control of its armed state. Inputs can initiate links when they go into alarm or when they go from a normal to abnormal (non-alarm) state. • Outputs can link to other outputs, inputs and/or to time zones. Linking to an output allows for control of its on/off state. Outputs can initiate links to inputs and/ or other outputs when they energize or de-energize. • Linking to a Time Zone forces it to be active (on) or inactive (off) thereby controlling anything it is assigned to. • Codes can link to inputs, outputs, and/or time zones to control their armed and on/off states. • The standard linking responses are Pulse, Follow, Latch, Toggle, and Time Zone. • Pulse is a link for a predetermined amount of time. • Follow is a link that mirrors the state of an input or an output. • Latch is a link that is indefinite until a Time Zone command or link is received. • Time Zone is a link that sets the input, output or time zone that is being linked, to its preprogrammed schedule. • Toggle is a link that causes the armed state or the on/off state to change to the opposite position each time the toggle link is received. • Inputs, Outputs and Codes initiate or activate Linking Groups. Linking Groups contain a single input, output or time zone and/or multiple inputs, outputs and time zones. Each component (input, output and/or time zone) in the group has its own response to the link. The group makes it possible to link to multiple components with each point responding differently. • Linking Groups can be triggered by inputs changing state from normal to abnormal and by inputs going into alarm. • Linking Groups can also be triggered by Outputs going from either open to secure or from secure to open. • Linking Groups can also be activated by a card read or keypad entry with the use of a Linking Level.

  46. SMART card capabilities One Card Solutions. Smart Cards can be used with DSX and other systems. Over 250 Card Compatibilities. iCLASS®& mutliCLASS® standard smart card readers with enhanced security while still being user-friendly, convenient and affordable SmartID® MIFARE®/DESFire®Contactless smart card reader product line provides open architecture that is both flexible and secure aptiQ™ Multi-Technology Readers interface with aptiQ™ smart cards (MIFARE® Classic and MIFARE DESFire™ EV1), are NFC compatible, and can read the card serial numbers of a variety of smart cards from other manufacturers, making your next upgrade in technology simple and seamless.

  47. Mobile technology Integration • WinDSX combines innovation with standard building blocks to create a flexible and dynamic system that can be deployed and used in many settings and configurations. From single computer systems to enterprise wide solutions the WinDSX System is scalable and adaptable to many different PCs, networks, and operating systems. Built with Microsoft™ tools, WinDSX harnesses the power of the Windows™ operating systems and resources. • Deployments can include Workstation and Server operating systems, FAT Clients, and with today’s technology a wide range of Remote Connection and Control applications. Window’s built-in Remote Desktop™ capability is a great way to control a PC running WinDSXfrom another location. Terminal Services™ provides an even more robust solution for multiple users in other places without having to load software everywhere it is required. This is a major factor for traveling employees, flexible work areas, system oversight, maintenance, and upgrades. • WiFiallows tablet devices such as the iPad2™ to be used to administer and control the WinDSX System. There are remote control software packages, such as iTapRDP™ and TeamViewer™, that allow an iPad2™ to control a WinDSX client workstation. This freedom could allow a roaming guard to stay in touch with what is going on and stay alert to alarms and Card Holder traffic within the facility. • The Workstation program operates the same on a tablet device providing real time status and control of every Input and Output. Alarms can be handled and Images verified with Image Recall.

  48. Guard Tour DSX Real Time Guard Tour • The DSX Guard Tour feature is a great addition to any proprietary guard service. It allows the user to define specific routes, or tours, for the guard to take with time restrictions. The guard, in making his rounds, must check-in at predetermined Tour Stations within specified times. If the guard fails to check-in at the specified time, an alarm is generated at the PC. All activity is automatically logged to the computer's hard disk for later reporting. • The Tour is initiated at the PC when the guard is ready to begin his rounds. The guard must check-in at the predefined Tour Stations in the order and time specified by the Guard Tour. If the guard arrives early, the system reports he checked in early. If the guard fails to check-in or is late to a Tour Station, an alarm message appears at the PC that indicates which station he failed to check in at. Along with the “Failed to Check-In” Alarm an optional user defined response plan (Action Message) can be displayed for the operator or security personnel to follow. This type of real-time system ensures a quick response if the guard is compromised or incapacitated by alerting the operator or guard at the PC to the first sign of a problem. • Guard Tour is an integral part of the WinDSX System. It allows user controlled systems to make use of existing Access System hardware to perform guard tour management in a real-time fashion. The user simply defines a tour in the database and at anytime can start or stop the tour from the Workstation program. If there is an exception, the PC will beep and alert the operator that a guard has failed to arrive at a Tour Station, or simply display that he arrived early. • There are 999 possible Guard Tour definitions with each Tour having up to 99 Tour Stations. A Tour Station is a physical location a guard must reach and perform an action showing that he has arrived. This action, performed at the Tour Station, can be one of 13 different events with any combination of events in the same Tour.

  49. Guard Tour A Tour Station can be one of the following event types: • Access Granted • Access Granted Passback Violation • Access Denied Code • Access Denied PIN • Access Denied Time Zone • Access Denied Level • Access Denied Facility • Access Denied Code Timer • Access Denied Anti-Passback • Input Alarm / Input Alarm Restoral • Input Abnormal / Input Normal • Combinations of these events allow Tour Stations to be defined according to specific situations and needs or equipment available. In some cases, the guard may be checked-in by using his card or PIN to enter a door. In other situations it may not be necessary for the guard to gain entry but use his card or PIN just to check-in without the door unlocking. Another possibility would be for the guard to turn a maintained key switch to one position at one point in the tour and later, in the same tour, turn the same switch back to its original position. • This flexibility allows the user to construct the tours to meet their specific application utilizing existing access control and security hardware. By assigning the same minimum and maximum times to all stations in the tour the Guard has to check in at all stations in the defined order but without specific minimum and maximum times for each station. The Tours can also be defined for Random Station Order, which allows the Guard to perform the Tour in any order as long as all of the Station requirements are fulfilled within the overall time limit set.

  50. Trace Alert Any Card Holder can be selected for Trace. Any Reader can be selected for Trace. When a Card Holder that is set for Trace uses their card at a reader set for Trace the Workstation Program will beep once and display the "Access Granted Message" in a special color other than what is used for normal card traffic. A card holder marked for Trace can automatically invoke Image Recall when their card is used at any "Trace“ reader.  

More Related