The access control system of Figure 3 shall be operated to demonstrate the security classification dependent functions as listed in the requirements of Table 2. Using the programmed credentials (codes, cards, etc.), present them to the access point, monitor that the input has been processed within the required time period and that the correct indication and notification(s) occur (see Table 2). The laboratory shall check the manufacturer’s documentation for the support of mandatory and optional functionalities described in Table 2 for the grade that is assigned to the access control unit.

  1. Procedure

    1. Access point interface - Release timing (ref. Table 2, lines 1 to 4)

To demonstrate the ability of the access control unit to comply with requirements in Table 2, lines 1 to 4, perform the following steps:

  1. The system shall be programmed for one valid user information (credential), and in normal condition.

  2. Verify the manufacturer’s documentation and determine whether the release time is system defined or configurable for each access point (portal).

  3. Enter the user information, access shall be granted.

  4. Measure the release time and record result, functionality shall be as per Table 2, lines 1 to 4.

  1. Access point interface - Access control (ref. Table 2, lines 5 to 19)

To demonstrate the ability of the access control unit to comply with requirements in Table 2, lines 5 to 19, perform the following steps:

  1. The system shall be programmed for one valid user information (credential) and in normal condition. The system shall be provided with two access points, one programmed as entry and another one programmed as exit from a controlled area.

  2. Verify the manufacturer’s documentation and determine if the anti-passback rule is implemented and what options of this rule are supported (hard, soft, timed, global, override/disable, and anti-passback times). Enable one supported anti-passback function at the time.

  3. Enter the user information at the entry access point and verify that access is granted. Functionality shall be as per Table 2, line 5.

  4. Enter the same user information again at the entry access point (before and after the programmed anti-passback time) and record the result.

  5. Enter the user information at the exit access point and verify that access is granted. Functionality shall be as per Table 2, line 6.

  6. Enter the same user information again at the exit access point (before and after the programmed anti-passback time) and record the result.

  7. Repeat the test for each anti-passback option supported by the access control system.

  8. Functionality for supported anti-passback options shall be as per Table 2, lines 7 to 11.

  9. Program an effective date/expiry date for the user information.

  10. Enter the user information at the access point within the effective date/before expiry date set for this credential, access shall be granted.

  11. Enter the user information at the access point after the effective date/expiry date set for this credential, access shall be denied. Functionality shall be as per Table 2, lines 12 and 13.

  12. Program two users information with the same access levels.

  13. Program an access point to allow entry only when two sequential authorized access requests are made within a programmable limited time period. Program allowed window to 2 minutes.

  14. Present one user information, access shall not be granted.

  15. Present the first and second user information within 2 minutes, access shall be granted

  16. Present the first user information, wait for 2 minutes, present the second user information, access shall not be granted. Functionality shall be as per Table 2, line 17.

  1. Access point interface - Access point status monitoring (ref. Table 2, lines 20 to 23)

To demonstrate the ability of the access control unit to comply with requirements in Table 2, lines 20 to 23, perform the following steps:

  1. The system shall be programmed for one valid user information (credential), and in normal condition.

  2. Verify the manufacturer’s documentation and determine whether the access point open time is system defined, programmable for each access point/portal.

  3. Enter the user information, access shall be granted.

  4. Measure the open time of the portal and record the result. Functionality shall be as per Table 2, lines 20 to 22.

  1. Access point interface - Input signals processing (ref. Table 2, line 24)

Apply an input signal (e g. tamper) with an active duration of minimum 400 ms and record whether the event is annunciated at the monitoring console. Functionality shall be as per Table 2, line 24.

  1. Criteria for compliance

The status of the access point actuation and monitoring shall be in accordance with the security classification dependent requirements of Table 2.

  1. Functional tests for indication/annunciation (displaying, alert and logging)

    1. Object of the test

To demonstrate by inspection and test that the access control system can meet the indication/annunciation functionalities of 6.3 and Table 3.

  1. Principles

The access control system of Figure 3 shall be operated to demonstrate the security classification dependent functions of display, alert and logging functions as listed in the requirements of Table 3.

  1. Test procedure

    1. Portal indications (ref. Table 3, lines 1 to 4) and monitoring console

annunciation (ref. Table 3, lines 17, 18, 26 and 32)

To demonstrate the ability of the access control unit to comply with requirements in Table 3 lines 17, 18, 26 and 32 perform the following steps:

  1. Where the option is provided verify that an indication of portal locked status is displayed until an access is granted. Functionality shall be as per Table 3, line 3.

  2. Present valid credentials to an access point to create an access granted condition. Record the response of the annunciation outputs at the portal. Functionality shall be as per Table 3, line 1.

  3. Present invalid credentials to an access point to create an access denied condition and record the response of the annunciation outputs. Ensure that the cause of access denial is placed in the event log. Functionality shall be as per Table 3, lines 2 and 18.

  4. For system defined operation, present valid credentials to an access point to create an access granted condition and simulate the portal being open. Keep the portal open until the system defined pre-alert time starts and record the response of the annunciation outputs at the portal. Keep the portal further open until the system-defined allowed open time expired and confirm an alert is generated at the monitoring console. Functionality shall be as per Table 3, lines 4 and 32.

  5. Close the portal and record the time taken for the alert to cease. Functionality shall be as per Table 3, lines 4 and 26.

  1. Monitoring console (Ref. Table 3, lines 5 to 47)

To demonstrate the ability of the access control unit to comply with requirements in Table 3, lines 5 to 47, perform the following steps:

  1. Present valid credentials to an access point to create an access granted condition and simulate the portal being opened and closed. Record the response of the annunciation outputs at the monitoring console. Functionality shall be as per Table 3, lines 6, 15 and 27.

  2. Where the option is provided, confirm there is visual annunciation when access is granted. Functionality shall be as per Table 3, line 5.

  3. Where the option is provided, check the operation of the card usage counter annunciation. Functionality shall be as per Table 3, line 8.

  4. Create a duress condition and record the response of the annunciation outputs at the monitoring console. Functionality shall be as per Table 3, line 7.

  5. Present a token with an expired validity period to an access point and record the response of the annunciation outputs. Functionality shall be as per Table 3, line 9.

  6. Present a valid token together with valid memorized information (e.g. PIN) to a suitably configured access point to create an access granted condition and simulate the portal being opened and closed. Confirm correct operation as per Table 3, lines 1,6, 15 and 27.

  7. Repeatedly present a valid token together with invalid memorized information (e g. wrong PIN) at the same portal. Monitor the response of the annunciation outputs and record the number of attempts until an alert indication is given. Functionality shall be as per Table 3, line 10.

  8. Present valid memorized information (e.g. PIN) to a suitably configured access point to create an access granted condition and simulate the portal being opened and closed. Confirm correct operation as per Table 3, lines 1,6, 15 and 27.

  9. Repeatedly present invalid memorized information (e.g. wrong PIN) at the same portal. Monitor the response of the annunciation outputs and record the number of attempts until an alert indication is given. Functionality shall be as per Table 3, line 11.

  10. Subject to security classification, confirm by inspection that the system has provision to display a map of the controlled area and access points for which an alert was generated. Functionality shall be as per Table 3, line 13.

  11. Subject to security classification, confirm by inspection that the system has provision to display instructions following an alert condition. Functionality shall be as per Table 3, line 12.

  12. Commencing with the simulated portal closed, present valid credentials to an access point to create an access granted condition but keep the portal closed, simulating a failure to entry condition. Record the response of the annunciation outputs at the portal and confirm the uncompleted transaction is recorded in the event log and an alert indication is provided as per Table 3, line 16.

  13. Confirm by test that changes to time scheduled and/or manual (via manual override release) portal locked/unlocked status are displayed and the event is recorded in the log. Functionality shall be as per Table 3, linel9.

  14. Remove the primary power source (e.g. mains supply) to the system under test. Record the response of the annunciation outputs. Functionality shall be as per Table 3, lines 20, 27 and 28.

  15. Reinstate the primary power source and confirm the event is recorded in the log. Functionality shall be as per Table 3, line 21.

  16. Create a condition of low standby power supply by either introducing a discharged battery or by substituting the normal standby power source with a variable power supply adjusted slowly from the nominal standby voltage to the low power condition. Record the response of the annunciation outputs when the low power condition is reached. Functionality shall be as per Table 3, lines 22, 27 and 28.

  17. With the normal standby power supply reinstated and the access control system functioning normally completely remove the standby power source. Record the response of the annunciation outputs. Functionality shall be as per Table 3, lines 22, 27 and 28.

  18. Confirm by test that the action of entering and the action of leaving the programming mode is displayed and is recorded in the event log. Functionality shall be as per Table 3, line 23.

  19. Interrupt the following communication links in turn whilst monitoring the annunciation outputs and measuring the time taken for the alert to be annunciated:

  1. the link between the access point user interface and the access control unit;

  2. the link between the access control unit and the monitoring console.

  1. Upon the interruption of the link between the access point user interface and the access control unit, measure and record the duration from the moment of interruption to the moment the alert is indicated at the monitoring console. Functionality shall be as per Table, 3 lines 24, 27, 28, 35 and 38.Where the option of displaying text instructions is provided following an alert, also measure and record the duration from the moment that the alert is indicated at the monitoring console to the moment that the text instructions associated with the alert message are displayed at the monitoring console. Functionality shall be as per Table 3, line 39.

  2. Where the option of displaying images and/or graphics is provided following an alert, also measure and record the duration from the moment that the alert is indicated at the monitoring console to the moment that the images and/or graphics associated with the alert message are displayed at the monitoring console. Functionality shall be as per Table 3, line 40.

  3. Create system alerts at items that are off-line. Note the time and wait at least 5 minutes.

  4. Each communication link shall be reinstated and correct operation shall be demonstrated between the interruption attempts. Functionality shall be as per Table 3, lines 14 and 27.

  5. Check that the system alerts are received in the log with date stamps of the time the alert occurred, not the time it was received at the monitoring console. Functionality shall be as per Table 3, line 27.

  6. Present five sets of valid credentials to one or more access points in turn, creating an access granted condition and simulating the portal being opened and closed each time. Then remove one set of credentials from the controlled area by implementing an appropriate exit procedure.

  7. Monitor and record the response of the annunciation outputs and confirm that:

  1. the event log roll call reflects the correct number of credentials recorded as still being “IN” the area controlled by the system. Functionality shall be as per Table 3, line 25;

  2. the credentials that were removed from the controlled area by implementation of the exit procedure are correctly identified as being outside the controlled area;

  3. the event log shall have recorded the identity of specific reader(s) to which the credentials were presented.

  1. With the access control system operating normally and with all portals in a secured condition apply the appropriate inputs to simulate the action of a forced opening, i.e. without access being granted. Record the response of the annunciation outputs. Functionality shall be as per Table 3, line 31.

  2. Open an enclosure fitted with a means to detect tampering and record the response of the annunciation outputs. Functionality shall be as per Table 3, line 30.

  3. Simulate a locking device abnormal condition by application of the appropriate input signal(s) and record the response of the annunciation outputs. Functionality shall be as per Table 3, line 36.

  4. With reference to the manufacturer's documentation create a sufficient number of events to fill the event log to 90 % of logging capacity. Functionality shall be as per Table 3, line 37.

  5. Confirm by test that priorities can be assigned to specific alert events. Select at random, at least three configurable alert events. Functionality shall be as per Table 3, lines 28, 29 and 41.

  6. Generate multiple (minimum three) configurable alert events that have assigned specific priorities. Record the response of the annunciation outputs. Acknowledge each alert event and again record the response of the annunciation. Confirm that alerts were displayed in the order of priorities as specified by the access control manufacturer. Functionality shall be as per Table 3, line 29.

  7. Exercise the access control system to generate one of the selected alert events. Record the response of the annunciation outputs. Acknowledge the alert event and again record the response of the annunciation outputs. Functionality shall be as per Table 3, line 42.

  8. Where the option is provided for the operator to include comments in response to alerts, confirm also that the system generates an entry in the event log. The entry shall include a time and date stamp, the alert event to which the comments relate and the identity of the operator. Functionality shall be as per Table 3, line 45.

  9. Present five sets of valid credentials to one or more access points in turn, creating an access granted condition and simulating the portal being opened and closed each time. Then remove four sets of credentials from the controlled area by implementing the appropriate exit procedures. Monitor and record the response of the annunciation output and confirm that a warning associated with the minimum number of persons not present is displayed together with an alert and an entry in the event log. Functionality shall be as per Table 3, line 43.

  10. Confirm by test that operator initiated changes are recorded in the event log. Functionality shall be as per Table 3, line 44.The record shall include the following:

  1. type of parameter changed;

  2. operator identification;

  3. time and date stamp.

  1. Creation, printing and exporting of management reports shall be checked against the manufacturer’s specification. Functionality shall be as per Table 3, line 46.

At minimum, reporting for Grade 3 and Grade 4 systems shall include:

  1. details of all circuit activities;

  2. summary of all or any selected circuit activity including individual alarms within a chosen time period. (E.g. the system shall be capable of searching for all circuit activity or a single circuit within for example the last hour, even if there have been no alarm events);

  3. circuit and reader related operator actions within a chosen time period;

  4. access control alarms;

  5. access control reader activity on a per user basis;

  6. access control user information;

  7. circuit information: full point detail for every configured input and output point;

  8. user database changes;

  9. system availability: a log of all parts of the system, which details periods when each individual part is on-line and off-line;

  10. database files and system configurations.

  1. By inspection of the manufacturer's documentation confirm that the monitoring console has the provision to meet the security classification dependent requirements for the minimum event logging capacity of the system. Functionality shall be as per Table 3, line 47.

  2. Present three valid credentials at three different readers. Functionality shall be as per Table 3, line 33.

  3. Present three different valid credentials at one reader and two non-valid credentials at the same reader. Functionality shall be as per Table 3, line 34.

  1. Criteria for compliance

The status of the annunciation outputs shall be in accordance with the security classification dependent requirements of Table 3.

  1. Test methods for recognition functionalities

    1. Object of the test

To demonstrate by inspection and test that the access control system can meet the recognition functionalities of 6.4 and Table 4.

  1. Principles

The access control system of Figure 3 shall be operated to demonstrate the security classification dependent functions of recognition operate as listed in the requirements of Table 4.

  1. Test procedure

    1. Access levels (ref. Table 4, lines 1 to 12)

To demonstrate the ability of the access control unit to comply with requirements in Table 4 lines 1 to 12, perform the following steps:

  1. At the beginning of all tests set the real time clock to the correct time. After one day check whether the real time clock differs from the correct time by not more than the allowed value calculated as per Table 4, line 1.

  2. Set the date to date of change from the normal time to daylight saving time and the time to 2 minutes before the expected change. Record whether the change from the normal time to daylight saving time occurs at the official changing time as per Table 4, line 1.

  3. Set the date to date of change from daylight saving time to the normal time and time to 2 minutes before the expected change. Record whether the change from daylight saving time to normal time occurs at the official changing time as per Table 4, line 1.

  4. Set the date to February 28th of a next leap year and the time to 23:58. Record whether at midnight the date changes to February 29th as per Table 4, line 1.

  5. Set the date to February 28th of a non-leap year and the time to 23:58. Record whether at midnight the date changes to March 1st as per Table 4, line 1.

  6. Set the master clock to the correct time and date. Set the slave real time clock to the wrong time and wrong date. Set the time of the master clock to 2 min before synchronization time (given by the manufacturer). Record whether after the synchronization time the slave real time clock is synchronized to the same date and time as the master clock. By reviewing the accompanying documentation confirm that the synchronization time is repeated every day (i.e. with no input of date). Functionality shall be as per Table 4, line 3.

  7. Set master clock of the access control unit to the wrong time and wrong date. Connect the master clock of EACS to the official master clock of the premises, which gives the official time. After a maximum period of 15 minutes confirm that the master clock of the EACS has synchronized to the official time as per Table 4, line 4.

  8. Confirm the real time clock is set to display the correct time. Disconnect the mains power supply and the standby batteries (data retention batteries shall remain connected). After the periods defined by the appropriate system grade, reconnect the mains power supply and the standby batteries. The order of reconnection shall be in accordance with the equipment manufacturer’s recommendations. Confirm by inspection of the real time clock that the access control system displays the correct time. Functionality shall be as per Table 4, line 5.

  9. Review the manufacturer’s documentation and determine that the number of user access levels and the number of time zones meet or exceed the requirements of Table 4, lines 6 and 7.

  10. Verify whether the input of day, week, hour and minute, or the date, year, month and day, or hour and minute, respectively, is possible for the access levels required by Table 4, lines 8 and 9.

  11. Verify whether the given number of configurable days (i.e. special days) is handled correctly by the electronic access control system as per Table 4, line 10.

  1. Equipment and methods of recognition (ref. Table 4, lines 13 to 27)