WO2020252534A1

WO2020252534A1 - Facilities management access control methods, systems and apparatus

Info

Publication number: WO2020252534A1
Application number: PCT/AU2020/050621
Authority: WO
Inventors: Thomas Walkley; Anthony Mazzei
Original assignee: Erin IP Pty Ltd
Priority date: 2019-06-19
Filing date: 2020-06-19
Publication date: 2020-12-24
Also published as: AU2020295068A1; GB2600063A

Abstract

A server for facilities management and control, the server including a database, a resident interface, a service provider interface and a processor. The database is configured to store associations between registered residents, access control devices, residential spaces, access cards and registered service providers. The resident interface is configured to receive request messages regarding services to be provided at a designated time. The service provider interface is configured to transmit service request messages to provider device(s) and receive responses thereto. The processor is configured to, inter alia, access the database to determine an appropriate access card, determine the relevant access control device, and transmit access control messages to the access control device to provide access to a residential space.

Description

FACILITIES MANAGEMENT ACCESS CONTROL METHODS, SYSTEMS AND APPARATUS

FIELD

[0001 ] The present invention relates to facilities management access control methods, systems and apparatus.

BACKGROUND

[0002] A facility manager of residential buildings is oftentimes tasked with, among other responsibilities, maintaining a building’s security. Generally, a facility manager implements one or more systems that prevent unauthorised individuals from entering. In some instances, a building designer may design the access control system. However, as more service providers offer in-home services, a facility’ manager’s job becomes increasingly difficult due to the management of keys allowing access to the building. In addition to traditional in-home service providers such as cleaners and handypersons, service providers are increasingly providing unique services for pick-up dog walking, pet grooming, personal care, personal training, medical care, dry cleaning pick up, chef services, and in-home package delivery/set-up.

[0003] On one hand, a facility manager can provision a system that enables easy access to the building for service providers. However, such systems are prone to intrusions from unauthorised individuals, or at the least, provide service providers almost unlimited or unchecked access to the building. For example, keys and access code systems can be used anytime by service providers without the knowledge of residents. While some access code systems prevent access after certain hours, these systems generally permit access to the service provider anytime during normal hours and can easily be abused. On the other hand, the facility manager can provision a system that provides restrictive assess. However, these systems tend to frustrate service providers and are generally service-intensive, thereby burdening the facility manager and the other management staff. For example, doormen and security staff are expensive to maintain and often have to accompany a service provider to the requested residential unit after verifying the servicer provider’s credentials.

[0004] In addition to building security, a facility manager is responsible for providing access to certain building amenities, such as a cinema room, rooftop entertainment area, and penthouse lounge. To prevent overuse, the amenities are only available upon request of a tenant/resident of the building, and usually for a security deposit or refundable fee/bond. Again, the facility manager and the management staff can implement security measures that are permissive, thereby creating access vulnerabilities, or measures that are restrictive and consume their time in managing. For example, a simple lock could be added to the amenity rooms. However, a facility manager or other management staff would have to be at the building to unlock the room at the requested time and relock the room when the requested time has elapsed. On the other hand, a resident could be given a key to the room or access code to a lock, but until the key is collected or the access code is changed, the resident can continue to have access to the room, or provide others access to the room.

SUMMARY

[0005] In one embodiment of the present invention, there is provided a server for facilities management and control, the server including a database configured to store: associations between registered residents and access control devices associated with residential space associated with the registered residents, and associations between access cards and registered service providers; a resident interface configured to receive a request message from an application on a resident device of a registered resident, the request message including information that is indicative of a registered service provider to provide a service at a designated day and time; a service provider interface configured to: transmit a service request message to a provider device of the requested service provider, the request message including information that is indicative of the requested service and designated day and time, and receive a response message from the provider device that is indicative of an acceptance of the requested service; and a processor configured to: create a record indicative of the requested service provider, the requesting resident, and the designated day and time, determine the designated day and time has approached, access the database to determine an access card associated with the requested service provider; determine at least one access control device that provides access to a residential space associated with the resident; transmit an access control message to the at least one access control device causing the at least one access control device to provide access to residential space associated with the resident for the access card of the requested service provider.

[0006] Another embodiment of the present invention provides a server for facilities management and control, the server including: a database configured to store: associations between access control devices and spaces of a registered building ; and associations between access cards and registered users; an interface configured to receive a request message from an application on a user device of a registered user, the request message including information that is indicative to reserve a space in the registered building at a designated day and time; and a processor configured to: create a record indicative of the requested space, the requesting user, and the designated day and time, determine the designated day and time has approached, access the database to determine an access card associated with the requested user; determine at least one access control device that provides access to the requested space; transmit an access control message to the at least one access control device causing the at least one access control device to provide access to the requested space for the access card of the registered user.

[0007] The present disclosure is directed to a system, method, and apparatus configured to provide for interactive, automated facilities management. The example system, method, and apparatus includes, for example a resident application (e.g., app) for building tenants/residents and facilities management system for building operators. The resident application is configured to enable building residents to reserve services from third-party service providers that require access to the building/unit. The resident application is also configured to enable building residents to reserve certain building spaces/amenities and provides an overall communicative interface with facilities management. In some embodiments, the resident application may be used by a resident to obtain access to certain spaces/amenities at reserved times based on electronic permission messages transmitted by the automated facilities management to the resident application.

[0008] The example facilities management system is configured to coordinate access to one or more locations in a building or other facility. The facilities management system receives reservation messages from devices operating the resident application. The reservation messages identify, for example, the third-party requested to have access to the building/unit, a date/time of the access, a length of the access, a resident/tenant requesting the access, and/or a type of service associated with the access. For building amenities, the reservation messages identify, for example, the room to be accessed, a date/time of the access, a length of the access, a resident/tenant requesting the access, and/or any special requests. The facilities management system maintains a data structure of access requests. In some embodiments, the data structure may identify certain residents that are blocked from having access to an space/amenity and/or service providers that are blocked from having access to the building. [0009] The facilities management system may provide access to the building and/or spaces/amenities through a number of different mechanisms. In some embodiments, the facilities management system is communicatively coupled to smart locks, where each resident and service provider has a digital key card or fob. The digital key or fob is coded with a unique serial number or identifier. The facilities management system transmits access messages to the smart locks of identifiers associated with digital keys and/or fobs for whom access is granted. In instances where the smart locks include date/clock functionality, the access messages may include a time duration or date/time for which access is granted. In instances where a smart lock does not include a date/time feature, the facilities management system may transmit an access message to the appropriate smart lock indicative of which identifiers are to be removed from having access. The facilities management system may transit access messages to smart locks provided at entrances to spaces/amenities, building entrances, and/or unit entrances.

[0010] In other instances, the resident application may receive an access message from the facilities management system. In these embodiments, the access message may include a code for unlocking a lock to an access room. To access, for example, a space/amenity, the resident application may display an access code to enable a resident to enter the code into a lock. The resident application may also display a quick-response (“QR”) or bar code that is read by a scanner at a door lock. In yet other embodiments, the resident application may also communicate via, for example, Bluetooth or NFC to provide the unlock code electronically.

[001 1 ] The example service providers may have a provider application for their devices that provides access to the building and/or individual units in the same manner. For instance, the facilities management system may transmit an access message to the service provider device to provide temporary access to the building during the date/time specified by the resident. In some instances, the facilities management system may transmit an SMS, email message, or push notification with an attachment that enables a service provider to access the building. Depending on the system configuration, the service providers may use a service provider application to access the building using the SMS, email message, or push notification. In other instances, the system is configured to provide access to a service provider device using native controls without having a provider application installed. For example, an SMS message and/or an email message may have a link to the facilities management system, which when accessed, provider an electronic access code for accessing a building and/or a unit of a resident. [0012] The advantages discussed herein may be found in one, or some, and perhaps not all of the embodiments disclosed herein. Additional features and advantages are described herein, and will be apparent from the following Detailed Description and the figures.

BRIEF DESCRIPTION OF DRAWINGS

[0013] Embodiments of the invention will now be described by way of example only, with reference to the accompanying drawings, in which:

Fig. 1 shows an example facilities management system, according to an example embodiment of the present disclosure.

Fig. 2 shows an example of a facility of Fig. 1 , according to an example embodiment of the present disclosure.

Figs. 3 and 4 show diagrams of data structures for storing access control information, according to example embodiments of the present disclosure.

Figs. 5 to 15 show diagrams of user interfaces of a resident application of Fig. 1 , according to example embodiments of the present disclosure.

Fig. 16 shows a diagram of an example procedure for reserving an amenity, according to an example embodiment.

Fig. 17 shows a diagram of an example procedure for reserving a service provider, according to an example embodiment.

Fig. 18 shows a diagram of a management server of the facilities management system of Fig. 1 , according to an example embodiment of the present disclosure.

DESCRIPTION OF EMBODIMENTS

[0014] The present disclosure relates in general to a method, system, and apparatus configured to provide access to a building and/or rooms/units in a building through a facility management system. In particular, the example method, system, and apparatus include a resident application (e.g., a resident interface) that enables residents to schedule access to the building for a service provider or request access to a space/amenity. The example method, system, and apparatus are configured to process requests from resident applications for providing temporary access to a building, unit, space and/or amenity for the resident or specified third-party service provider. [0015] The example method, system, and apparatus are provided via an online interactive environment in which access may be requested from one or more residents of a building. The example method, system, and apparatus automatically schedule and provide access to designated individuals at designated times, thereby restricting third parties from accessing a building/unit at unauthorised times and restricting residents from a space/amenity at unrequested times. In some embodiments, the method, system, and apparatus are configured to provide smart locks with identifiers of individuals with access for certain designated times. Additionally or alternatively, the method, system, and apparatus are configured to provide access control at designated times to smart devices of residents and/or service providers for user with specified locks at the building.

[0016] Reference is made herein to residents. As discussed below, residents include individuals that occupy space in a building or other facility. Residents may own or rent a unit, apartment, or condominium in a residential building. Residents may also include commercial entities that may own or rent office or work space in a building. In the embodiments discussed below, residents request services to be performed in a building and/or request access to one or more access-controlled rooms (such as amenity rooms).

[0017] Reference is also made herein to buildings. A building may include any residential, commercial, or public building that has one or more individual units occupied by one or more residents. A building can include, for example, a 50-unit apartment building, an office building, a single house, an entertainment space, etc. It should be appreciated that the example method, system, and apparatus may be configured within any building that has access control. Further, a building is not limited to a single structure. Instead, the method, system, and apparatus may be provisioned in a residential complex, an office park, a commercial/residential campus, and/or a gated community.

[0018] Reference is further made herein to facilities management. A facility manager is responsible, among other tasks, for maintaining the security/access control of a building. For relatively large buildings, a facility manager may include doorpersons, security staff, and building staff. In other buildings, a facility manager may be offset and provide access remotely through, for example, passive or smart access control devices. Further, a facility manager may collectively be a board of an association or owner of a building/home that is responsible for installing and/or maintaining active and/or passive access control devices. [0019] The disclosure also makes reference to service providers. As discussed herein, service providers are third-parties that are unrelated to a building and/or resident. Generally, service providers provide a service that requires access to a building and/or unit. Services can include maid services, handyman/contractor services, pet services, personal care services, personal training services, medical care services, child care services, dry cleaning pickup, chef/catering services, package delivery services, home designer services, etc. It should be appreciated that there is no limit to the number and/or types of services providers that may benefit from and/or use the example method, system, and apparatus.

[0020] The example method, system, and apparatus may provide for automated access control using different types of configurations. For example, the method, system, and apparatus may provide digital keys or fobs to residents and/or registered service providers. Each digital key or fob is provided a unique identifier. In these examples, the example method, system, and apparatus are configured to program access control devices to grant access to certain identifiers at designed times. Programming may include sending one or more access messages via a wired or wireless connection to the appropriate access control device. In some instances, the access control devices may be connected to a Wi-Fi network or Bluetooth device of a building, in which access messages are transmitted via the Wi-Fi network or Bluetooth device to the appropriate access control device.

[0021 ] In some embodiments, access messages are instead transmitted to devices of residents and/or service providers. The messages may utilise a communicative feature on the device for transmitting or otherwise providing, for example, an access code to an access control device. The message may, for example, cause a device to display a code to enable a resident to enter a code into a keypad of an access control device. The message may cause a device to display a code that is scannable by a scanner on an access control device. The message may further cause a device to transmit an access code electronically, via NFC, RFID, infrared transmitted, etc., to an access control device.

[0022] The example method, system, and apparatus are configured to provide an application that enables a resident to schedule access for a service provider and/or access to an amenity room. The application may include an interface for a user device that transmits data to one more APIs of a facility management system. The application may also provide a status of accesses that have been scheduled. In some embodiments, the application may operate with the facility management system for booking a service with the service provider and providing payment for completed/reserved services. In some instances, the application may be replaced and/or used in conjunction with a website associated with the facilities management system. Further, in some instances, service providers may be provided an application for viewing reserved access/services and/or operating in conjunction with their devices as a key for access control devices at a building of a requesting resident.

[0023] Fig. 1 shows an example system 100 that provides for access control management, according to an example embodiment of the present disclosure. The system includes a management server 102 configured to provide access control management for one or more facilities 104. In the illustrated example, the management server 102 provides access control for facilities 104a and 104b. In other embodiments, the management server 102 provides access control for fewer or additional facilities.

[0024] Fig. 2 shows an example of a facility 104 of Fig. 1 , according to an example embodiment of the present disclosure. In the illustrated example, the facility 104 includes a building with a front door 202 and an amenity door 204. The front door 202 provides access to the facility 104, while the amenity door 204 provides access to an amenity room 206. The facility 104 may also include units of residents with respective doors. Each of the doors 202 and 204 is associated with a respective access control device 210 and 212. The access control device 210 and 212 controls a lock to the respective door 202 and 204. The access control devices 210 and 212 may include, for example, a digital key, a smartcard reader, a fob reader, an NFC reader, a QR/bar code reader, a Bluetooth transceiver, a camera, a keypad, etc. In some embodiments, the access control devices 210 and 212 are communicatively coupled to the management server 102 of Fig. 1 to receive access messages. In other embodiments, the access control devices 210 and 212 are programmed with one or more access codes, that when received, cause the access control devices 210 and 212 to unlock access to the respective door 202 and 204.

[0025] Returning to Fig. 1 , the example system 100 includes a resident device 1 12, which includes an application 120. The resident device 1 12 may include any type of device including a smartphone, a cellular phone, a tablet computer, a laptop computer, a workstation, smart- eyewear, smartwatch, etc. The application 120 may be a software program specified by one or more instructions in a memory of the device 1 12, that when executed by a processor of the device 1 12, cause the device to display one or more interfaces for receiving inputs related to scheduling a service provider/amenity room and or viewing information related to scheduled services and/or the facility in general. The application 120 may also provide an access code for use with one or more of the access control devices of Fig. 2. The application 120 may also include a web browser configured to navigate electronically to a webpage hosted or managed by the management server 102.

[0026] The example provider device 1 14 is configured to communicate with the management server 102 to receive messages indicative of a service request. Similar to the resident device 1 12, the provider device 1 14 may include any type of device including a smartphone, a cellular phone, a tablet computer, a laptop computer, a workstation, smart-eyewear, smartwatch, etc. In some embodiments, the provider device 1 14 may include a provider application 130 configured to display information indicative of a requested service. A service provider may respond to the request with an acceptance message or decline message, which is transmitted to the management server 102. If an acceptance message is transmitted, the provider device 1 14 may receive in some embodiments, from the management server 102, an access code or digital key to one or more access control devices associated with the requesting resident. In other instances, the provider device 1 14 may receive a confirmation message including an identification as to which access control devices of a building will be configured to provide access to a service provider at a designated time using, for example, their digital key, smartcard, fob, or device 1 14.

[0027] The devices 1 12 and 1 14 are communicatively coupled to the management server 102 via a network 1 18. As discussed herein, the network 1 18 may include any wired or wireless network including the Internet, an Ethernet, a Wi-Fi network, a cellular telephone network, or combinations thereof. In the illustrated example, the facilities 104 are also communicatively coupled to the management server 102 via the network 1 18. In other embodiments, the facilities 104 (e.g., access control devices of the facilities) may be hardwired or directly communicatively coupled to the management server 102 outside of the network 1 18.

[0028] In the illustrated example of Fig. 1 , the management server 102 is communicatively coupled to a memory device 150. The example memory device 150 may include any physical device configured for storing data, including RAM, ROM, flash memory, etc. The example memory device 150 is configured to store data structures that are related to access control provided by the management server 102. The data structures may include, for example, registration files for each resident and/or service provider. For a resident, a registration file may include a name, an address, a username/identifier associated with the application 120, an access control identifier for a access control device associated with their unit, payment/banking information, an amenity block flag, a device identifier, an email address, etc. For a service provider, a registration file may include an employee name, a company name, a service type, a username and password associated with the application 130, an address, a building block flag, a device identifier, an email address, etc. The management server 102 may organise registered service providers into a hierarchy based on service type for selection by a resident using the application 120.

[0029] The example database 150 also includes access control data structures, as shown in Figs. 3 and 4. Data structure 300 corresponds to embodiments where identifiers of residents/service providers are provided to access control devices. The data structure 300 shows entries made by a resident to request access control. In a first entry, labelled Ί 8432”, a resident has requested a dog walking service for June 15 at 2:00 PM for 30 minutes. The management server 102 determines the resident is associated with Unit 3H, and the service also requires entry of a front door 1 A. Accordingly, the management server 102 stores identifiers of the access control devices to the data structure 300.

[0030] At the appropriate time, or a predefined time (e.g., 10 minutes) before the specified time, the management server 102 is configured to determine the access control identifiers and an identifier of the dog walking service provider. The management server 102 then transmits, before or at 2:00 PM on June 15, an access message with an identifier of the dog walking service provider to the access control devices associated with Door 1 A and unit 3H. As such, when the dog walking service provider places a digital key, smartcard, fob, or device 1 14 into a reader of the smart access device, the smart access device reads an identifier and makes a match to the identifier received from the management server 102. After a match is made, the access control device permits entry through the corresponding entryway.

[0031 ] A second entry in the data structure 300 corresponds to an amenity request. In this instance, a resident requested Amenity Room 1W for themselves. Before and/or at the requested time, the management server 102 transmits an access message to the access control device of the amenity room to provide the resident access via the digital key, smartcard, fob, or device 1 12.

[0032] Data structure 400 of Fig. 4 corresponds to embodiments where digital keys or access codes are provided to devices 1 12 and 1 14 of residents and/or service providers. In this example, the digital keys and/or access codes are configured to operate with access control devices needed to gain access to the appropriate location. For the first entry in the data structure 400, the management server 102 selects digital key 23, which may provide access to access control devices located at front door 1 A and unit door 3H. In comparison, the management server 102 selects digital key 90 to provide a resident access to amenity room 1 W.

[0033] In this embodiment, the digital key or access code may be programmed to expire after the specified time. After expiration, the devices 1 12 or 1 14 may be instructed to delete the digital key or access code. Alternatively, after expiration the applications 120 or 130 may delete the access code or digital key. In yet other embodiments, the digital key or access code may be programmed to only operate with the specified access control devices at specified times, where the access control devices may have algorithms that provide for encrypted-type access that periodically changes over time, and the digital key only works with the encrypted access code as a public key during the times set by the management server 102.

[0034] The entries in the data structures 300 and 400 may be created after a resident creates a request. In some instances, the management server 102 may store the entries in a temporary structure until a service provider provides a confirmation of a service. After a confirmation is received, the management server 102 creates an entry in the data structure 300 or 400.

[0035] In some embodiments, the management server 102 may enable a resident to create re occurring entries. In these examples, an entry may be created for each occurrence. Alternatively, multiple days may be provided in the entry.

[0036] In some embodiments, the provider application 130 may be configured to enable service providers to reserve an amenity and/or space in a building to provide a service. In an example, the application 130 is configured to display available days/times for amenities, rooms, and/or spaces for buildings in which a service provider is registered. A service provider 130 uses the application 130 to reserve an amenity, room, and/or space for a desired time/day (e.g., a yoga instructor may reserve a space in a building to lead a yoga class). The server 102 then reserves the amenity, room, and/or space for the service provider and makes it available to the service provide during the requested time. For instance, the server 102 may cause one or more access control devices to accept a digital key, fob, code, etc. from the service provider at the designed time to enable the service provider to enter the building/amenity/room to provide their service.

[0037] In some examples, the application 130 is configured to only enable a service provider to reserve an amenity or space after a resident has requested the service from the service provider. In the example above, a resident has to use application 120 to request a yoga service, which is sent to the service provider. In response, the application 130 enables the service provider to reserve the space or amenity for yoga. The application 130 may only enable the service provider to reserve the space or amenity for the building/day/time requested by the resident. If multiple spaces are available in the building, the application 130 may be configured to enable the service provider to select the space or amenity.

[0038] In yet other embodiments, the application 120 may be available for any registered user that desires to reserve an amenity or building space. For instance, a building manager may create or designate certain spaces in a building as open co-working space or space for a pop up merchant. In these instances, the application 120 is configured to display to registered users information that is indicative of the availability of the designated amenities or spaces that are available to non-residents. The application 120 is configured to enable the user to reserve an amenity or space at a designated date/time. In some instances, the application 120 is configured to receive payment information from the registered user for reserving the amenity or space. Then, at the requested date/time, the management server 102 is configured to cause one or more access control devices to accept an access card, code, etc. from the registered user to provide entry for the requested amenity or space. In some embodiments, the server 102 may transmit one or more messages to the application 120 of the registered user that enable access of the one or more access control devices at the requested date/time.

[0039] Figs. 5 to 15 show diagrams of user interfaces of the resident application 120 of Fig. 1 , according to example embodiments of the present disclosure. The interfaces may be displayed via the resident device 1 12. Fig. 5 shows an interface 500 related to resident registration. During registration, the interface 500 prompts a resident for their date they will be moving in for creating a resident entry. An interface may also be provided when a resident plans to move out. Registration enables a resident to be associated with a particular building such that the application 120 is configured to provide service access requests for access control devices associated with the building of the resident. Further, registration of move in/move out dates enables the management server 102 to prevent the resident from making requests when they are not a resident of a building.

[0040] Fig. 6 shows a user interface 600 of a dashboard of the application 120. The user interface 600 includes a list of upcoming bookings and building amenities that can be reserved. Fig. 7 shows a user interface 700 of a service booking feature of the application 120. The user interface 700 includes a list of available services that have registered with the management server 102 for receiving access to the building of the resident. Selection of a service category may cause service types for that category to be displayed, and/or individual service providers. After a resident selects a provider, the application 120 may enable a resident to select a date/time. In some instances, the management server 102 may interface with systems of service providers to access availability schedules for display. Fig. 8 shows a user interface 800 that enables a user to select a time duration for a desired service as part of the request process. Fig. 9 shows a user interface 900 indicative that a request has successfully been made and indicates an acceptance/decline message has been transmitted from the management server 102 to the requested provider. To transmit the acceptance/decline message, the management server 102 uses the registration information provided by the provider.

[0041 ] Fig. 10 shows a user interface 1000 for selecting amenities of a building of a registered resident. Selection of an amenity from the user interface 1000 causes the resident application 120 to provide interfaces for selecting a date/time and/or special requests. In some instances, a facility operator may require payment or a security deposit for reserving an amenity room. Fig. 1 1 shows a user interface 1 100 for enabling a resident to make a payment for reserving an amenity room. In some instances, the credit card may be on file, as provided in a lease agreement/registration with the application 120. In some instances, payment may include an agreement to add the cost the monthly rent change.

[0042] Fig. 12 shows a user interface 1200 dashboard for a building. The dashboard includes amenities, defect reporting, move in/out options, and a news feature. Fig. 13 shows a user interface 1300 provided when a user selects the defect reporting in the dashboard of interface 1200. The interface 1300 displays a list, and corresponding status of defects or other building issues reported by the resident and/or other residents in the building. Selection of a defect causes the resident application 120 to display more information related to the defect, such as information submitted to report the defect and/or information from facilities management regarding resolution of the defect. Fig. 14 shows a user interface 1400 of the resident application 120 to enable a user to submit information for a newly identified defect. The interface 1400 includes a title field, a message field, and a flag for making the request public to other residents of the building. In the message field, a resident may insert images and/or video recorded by the device 1 12. Fig. 15 shows a user interface 1500 shows news related to the building, which is selectable from the user interface 1200.

[0043] Fig. 16 shows a diagram of an example procedure 1600 for reserving an amenity room, according to an example embodiment. The example procedure begins when the management server 102 receives a request message 1601 , from the resident application 120, for example, indicative of an amenity booking (block 1602). The request message 1601 may include an identifier of then resident, an identifier of the amenity room, and/or a time/data. The server 102 determines if the amenity is available (block 1604). If the amenity is not available, the server 102 transmits a response message to the resident, via the application 102 indicative that the selected date/time is not available and a new date/time is to be selected (block 1606). In some embodiments, the application 120 may discolor dates/times (or otherwise make the dates/times un-selectable) when the amenity room is booked by accessing a schedule of the server 102.

[0044] If the amenity is available, the server 102 is configured to store the reservation and process the reservation (blocks 1608 and 1610). The server 102 may store the reservation by creating an entry in the data structure 300 or 400. The server 102 may process the reservation by sending any notifications to facility managers, connecting to a payment gateway to process the payment, connect to a digital key API with the resident/unit and booking window information. After the reservation is processed, the server provides access to the amenity room to the resident at the designated date/time (block 1612). In some instances, this includes transmitting a digital key or access code to the device 1 12 of the user, where the key/code is only valid or available during the reservation period. In other instances, this includes transmitting an access message to one or more access control devices for the amenity room at times related to the reservation date/time with an identifier of the resident or the resident’s smartcard, fob, device 1 12. During the designated time, the resident may access the amenity room using, for example, the application 120 or a digital key/smartcard/fob/key to gain entry. The example procedure of Fig. 16 then ends.

[0045] Fig. 17 shows a diagram of an example procedure 1700 for reserving a service provider, according to an example embodiment. The example procedure begins when the management server 102 receives a request message 1701 , from the resident application 120, for example, indicative of a service provider booking (block 1702). The request message 1701 may include an identifier of the resident, an identifier of the service provider, and/or a time/data. The server 102 determines if the service provider is available (block 1704). If the service provider is not available, the server 102 transmits a response message to the resident, via the application 102 indicative that the selected date/time is not available and a new date/time is to be selected (block 1706). In some embodiments, the application 120 may discolor dates/times (or otherwise make the dates/times un-selectable) when the service provider is not available by accessing, via the server 102, a schedule of the service provider. In some embodiments, the server 102 does not check if the service provider is available and instead proceeds to confirming if the service can be provided by the provider.

[0046] The procedure 1700 of Fig. 17 continues by creating or storing an entry to a data structure for the service reservation (block 1708). The server 102 may also transmit a confirmation message to the selected provider (block 1710). The confirmation message may include the resident name, address, payment information, and requested date/time. At a later time, the server 102 receives a response from the provider (block 1712). The server 102 determines if the provider accepted or declined the reservation (block 1714). If the provider declined, the server 102 prompts the resident, via the resident application 120, to select another provider and/or another date/time (block 1716). In some instances, the provider may decline and provide one or more alternative times for a reservation.

[0047] If the service provider accepted the reservation the server 102 processes the reservation (block 1718). After the reservation is processed, the server provides access to the building/unit of the resident at the designated date/time (block 1720). In some instances, this includes transmitting a digital key or access code to the device 1 14 of the service provider, where the key/code is only valid or available during the reservation period. In other instances, this includes transmitting an access message to one or more access control devices for the building/unit at times related to the reservation date/time with an identifier of the service provider or the provider’s digital key, smartcard, fob, device 1 14. During the designated time, the service provider may access the building/unit room using, for example, the application 130 or a digital key, smartcard/fob/key to gain entry. The example procedure of Fig. 17 then ends.

[0048] Fig. 18 shows a diagram of the management server 102 of Fig. 1 , according to an example embodiment of the present disclosure. In the illustrated example, the management server 102 is included within an example system 1800 that is configured for access control management. The system 1800 includes at least one resident device 1 12 connected to the server 102 via a mobile public API 1802. The example API 1802 provides one or more interfaces or defined fields for receiving information provided by the resident application 120.

[0049] The server 102 also includes load balancers and auto-scalers for respective operational groups. The server 102 may include a load balancer and/or scaler for products, bookings, messaging, user account and authentication (“UAA”), and server hardware. The server 102 may include additional or fewer load balancers and/or auto-scalers in other embodiments.

[0050] As shown in Fig. 18, the products group of the server 102 communicates with a products database 150a for providing access to lists of available products, amenities, resources, and/or services that are available for booking. The bookings group of the server 102 communicates with a bookings database 150b that includes data structures of requested and/or confirmed bookings of products, amenities, and/or services. The bookings group may communicate with a payment gateway for processing payment related to a booked service and/or amenity. The UAA group of the server 102 communicates with a UAA database 150c to provide restricted access for the access control bookings to only registered residents. The messaging group of the server 102 operates with a message broker to provide, for example, email notifications and/or SMS push notifications to registered users, building management, and/or requested service providers. The notifications may include, for example, a request from a user to book a service and/or amenity. The hardware group 102 of the server 102 is configured to enable administrators of the server 102 to add, delete, and/or modify the other groups, the API, and/or other provided features.

[0051 ] It will be appreciated that each of the systems, structures, methods and procedures described herein may be implemented using one or more computer program or component. These programs and components may be provided as a series of computer instructions on any conventional computer-readable medium, including random access memory (“RAM”), read only memory (“ROM”), flash memory, magnetic or optical disks, optical memory, or other storage media, and combinations and derivatives thereof. The instructions may be configured to be executed by a processor, which when executing the series of computer instructions performs or facilitates the performance of all or part of the disclosed methods and procedures. [0052] It should be understood that various changes and modifications to the example embodiments described herein will be apparent to those skilled in the art. Such changes and modifications can be made without departing from the spirit and scope of the present subject matter and without diminishing its intended advantages. It is therefore intended that such changes and modifications be covered by the appended claims. Accordingly, the claims are not meant to be limited to the corresponding structure, material, or actions described in the specification or equivalents thereof.

[0053] For the purpose of this specification, the word "comprising" means "including but not limited to," and the word "comprises" has a corresponding meaning.

Claims

1. A server for facilities management and control, the server including:

a database configured to store:

associations between registered residents and access control devices associated with residential space associated with the registered residents, and

associations between access cards and registered service providers;

a resident interface configured to receive a request message from an application on a resident device of a registered resident, the request message including information that is indicative of a registered service provider to provide a service at a designated day and time; a service provider interface configured to:

transmit a service request message to a provider device of the requested service provider, the request message including information that is indicative of the requested service and designated day and time, and

receive a response message from the provider device that is indicative of an acceptance of the requested service; and

a processor configured to:

create a record indicative of the requested service provider, the requesting resident, and the designated day and time,

determine the designated day and time has approached,

access the database to determine an access card associated with the requested service provider;

determine at least one access control device that provides access to a residential space associated with the resident;

transmit an access control message to the at least one access control device causing the at least one access control device to provide access to residential space associated with the resident for the access card of the requested service provider.

2. The server of Claim 1 , wherein the processor is configured to:

determine the designated day and time has elapsed; and

transmit a second access control message to the at least one access control device causing the at least one access control device to remove the access to residential space associated with the resident for the access card of the requested service provider.

3. The server of any preceding claim, wherein the access control message includes the designated day and time for the at least one access control device to provide access to the residential space associated with the resident for the access card of the requested service provider.

4. The server of any preceding claim, wherein the at least one access control device includes a first access control device that is located at a front door of a building of the resident and a second access control device that is located at a front door of the residential space associated with the resident.

5. The server of any preceding claim, wherein the access card includes at least one of a digital card, a smartcard, a fob, or a smartphone.

6. A server for facilities management and control, the server including:

a database configured to store:

associations between access control devices and spaces of a registered building; and

associations between access cards and registered users;

an interface configured to receive a request message from an application on a user device of a registered user, the request message including information that is indicative to reserve a space in the registered building at a designated day and time; and

a processor configured to:

create a record indicative of the requested space, the requesting user, and the designated day and time,

determine the designated day and time has approached,

access the database to determine an access card associated with the requested user;

determine at least one access control device that provides access to the requested space;

transmit an access control message to the at least one access control device causing the at least one access control device to provide access to the requested space for the access card of the registered user.