{"id":867,"date":"2018-04-23T18:51:29","date_gmt":"2018-04-23T18:51:29","guid":{"rendered":"https:\/\/kerisys.com\/?p=867"},"modified":"2021-01-27T21:04:55","modified_gmt":"2021-01-27T21:04:55","slug":"quick-tutorial-time-schedules-and-access-groups","status":"publish","type":"post","link":"https:\/\/kerisys.com\/2018\/04\/23\/quick-tutorial-time-schedules-and-access-groups\/","title":{"rendered":"Quick Tutorial: Time Schedules and Access Groups"},"content":{"rendered":"

Who Can Go Where, and When<\/span><\/h1>\n

Keri\u2019s products do much more than just what the moniker \u201caccess control system\u201d suggests; providing the ability to create complex hardware input\/output or software procedures that are initiated by designated trigger events, automating these procedures and other functions, designing and printing ID badges, integration with various subsystems such as video surveillance, biometrics, wireless locks, and graphic maps, etc.<\/p>\n

At its core, an access control system\u2019s most important functions are to limit who can go where and when and track the person\u2019s use of their credential (\u201ccomings and goings\u201d) for later reporting.<\/p>\n

Creating Time Schedules<\/h2>\n

In order to allow\/restrict an individual\u2019s access around one or more facilities, parameters must be configured that make this an easy process when enrolling people into the system, whether it be for a brand new system with thousands of people, or one individual at a time as new hires are brought on board.\u00a0 Typically with most access control systems and as with Keri, this is done by creating time schedules (sometimes called zones) that are later associated with readers\/doors to create \u00a0\u201caccess groups.\u201d People are ultimately assigned to an access group when enrolled into the system.\u00a0 These predefined access groups are what gives or denies access privileges by location and time of day.<\/p>\n

Example A Example B<\/h2>\n

The creation of time zones seems simple enough, but this is where we often observe customers make it difficult to use their access groups, as demonstrated in the illustrations A and B.<\/p>\n

 <\/p>\n

When using schedules to create access groups, some types of names make it difficult to know exactly when a scheduled starts and ends.<\/p>\n

We find it preferable to name the time schedules for exactly what they are so that when viewed in a list during system configuration, there is no question as to what the schedule really is.\u00a0 Something like Illustration C would be more appropriate:<\/p>\n

 <\/p>\n

Example C<\/p>\n

That way, it is much easier to know exactly what the schedules are when creating the access groups which will be used to assign to cardholders.\u00a0 Then, the types of names we describe as inappropriate for time schedules can be used for the access group names, making it simple and straightforward to assign cardholders to one or more for their specific access privileges.\u00a0 Illustrations D and E show a list of access groups we\u2019ve created, with the Day Shift expanded to expose the detail.<\/p>\n

 <\/p>\n

It then becomes a simple matter to assign cardholders to an access group, which defines where they can go and when.<\/p>\n

Example D<\/strong>Example E<\/strong><\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

Dennis Geiszler is a 30+ year veteran of the access control industry, serving in various sales and marketing executive positions for both Indala Corporation and Keri Systems.<\/p>\n","protected":false},"excerpt":{"rendered":"

Who Can Go Where, and When Keri\u2019s products do much more than just what the moniker \u201caccess control system\u201d suggests; providing the ability to create complex hardware input\/output or software […]<\/p>\n","protected":false},"author":18,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[1],"tags":[],"industries":[],"is_legacy":[],"related_product":[],"class_list":["post-867","post","type-post","status-publish","format-standard","hentry","category-article"],"acf":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/posts\/867","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/comments?post=867"}],"version-history":[{"count":0,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/posts\/867\/revisions"}],"wp:attachment":[{"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/media?parent=867"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/categories?post=867"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/tags?post=867"},{"taxonomy":"industries","embeddable":true,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/industries?post=867"},{"taxonomy":"is_legacy","embeddable":true,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/is_legacy?post=867"},{"taxonomy":"related_product","embeddable":true,"href":"https:\/\/kerisys.com\/wp-json\/wp\/v2\/related_product?post=867"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}