KONE Bidding- Central Point Building

Upgrade to Hybrid DCS System

Overview of the Upgrade

• The project involves upgrading from a conventional controller to a hybrid DCS system with four lifts. This upgrade will include touch screens installed on basement floors and floor one.

Access Control Features

• A turnstile will be implemented at floor one, requiring solutions for face ID and QR code access at both the basement and floor one levels. Face ID will automatically open the turnstile and call the lift upon recognition.

• The existing card access system will remain as a backup alongside the new face ID feature, which is primarily intended for tenants, while QR codes are designated for visitors.

Lift Cabin Modifications

• Inside the lift cabin, users can still use card access to select their desired floors; however, there is a plan to replace current systems with Delta Frontier software integration. Existing card readers in cabins will also be retained or upgraded as part of this transition.

Detailed System Requirements

• The requirements specify that each lobby (DP) must have card readers, face ID systems, and QR code scanners installed. However, only card readers are needed inside each lift cabin. Each DP area should have two installations per level where applicable.

• There is an emphasis on maintaining traditional button controls in other areas while modernizing specific locations like basement one and lobby level one with touch screens instead of buttons.

Options for Implementation

• Two options were proposed: either completely replacing existing systems with new technology or retrofitting current turnstiles with face ID equipment while assessing motor compatibility for upgrades. Integration with existing parking systems was also discussed as necessary for seamless operation across different access points.

Visitor Management System Discussion

• A visitor management system is required to facilitate guest entry efficiently through reception lists and other means of tracking visitors within the building's security framework. Further details on implementation were suggested but not fully outlined in this segment of discussion.

Visitor Management System Proposal Discussion

Overview of the Proposed System

• The discussion begins with a proposal for visitor management software that includes QR code generation for visitors, emphasizing accessibility and ease of use.

• The system features both a self-service kiosk for visitor registration and a workstation for receptionists to assist visitors with check-in.

• Visitors are encouraged to use QR codes instead of cards, aligning with client preferences; face ID is also mentioned as an alternative method for tenant access.

Registration Process

• Each tenant can generate their own QR codes through the system, which can be accessed via kiosks or receptionist workstations.

• Receptionists can register visitors directly using webcams or cameras at their workstations, streamlining the check-in process.

• A recent project in Singapore serves as a reference point, showcasing similar implementations and upgrades to existing systems.

User Journey and Approval Workflow

• The proposed user journey allows visitors to self-register or have their information entered by receptionists. After registration, they scan their faces for access.

• There is an approval process where receptionists or admins must grant access before generating QR codes, ensuring security protocols are followed.

• Pre-registration options allow visitors to register online prior to arrival; this requires internet access for data submission.

Data Management Considerations

• The system supports pre-registration links sent out days in advance, allowing tenants to manage visitor data effectively while maintaining security measures.

• Both centralized management by property management and individual tenant portals are available; each tenant only sees their own data while property management oversees overall records.

Best Practices in Visitor Management

• Discussions highlight best practices regarding who manages visitor data—property management versus individual tenants—ensuring clarity on responsibilities related to employee changes and access control.

Facial Recognition and Access Management Solutions

Overview of Facial Recognition Implementation

• The implementation of facial recognition technology in property management is discussed, highlighting a 90% onboarding rate for the system deployed at Millennia Tower.

• Card access remains as a backup option alongside facial recognition to ensure reliability if the face ID fails.

• Visitors have the choice to register their faces or generate a QR code for entry, promoting a paperless process.

Kiosk Features and Functionality

• Self-check-in kiosks are utilized in two projects in Singapore, allowing users to check themselves in and print or generate QR codes for access.

• The kiosk integrates multiple functions: QR code scanning, facial recognition, and card reading capabilities.

• A visual description of the kiosk setup includes an embedded camera for facial recognition above the screen displaying QR codes.

Technical Specifications and User Experience

• The camera's wide-angle capability allows it to recognize individuals from 1.3 meters up to 2 meters away, enhancing user experience by reducing touchpoints.

• Concerns about camera placement are addressed; adjustments can be made based on user feedback regarding visibility and accessibility.

Visitor Journey and Access Flow

• The user flow for tenants involves preconfigured settings that allow them to scan their faces upon entering without needing to press buttons.

• Additional measures are in place for missed scans; alternative methods like QR codes will still grant access through designated points.

• Each turnstile displays lift information corresponding with the user's scanned credentials, streamlining navigation within the building.

Visitor Registration Process Overview

Face ID and Floor Destination Display

• The Face ID screen can display the lift name and floor destination, eliminating the need for a separate DGD display from Con.

• This feature allows visitors to see their destination clearly upon arrival.

Ad Hoc Visitor Registration

• Visitors will use a self-registering kiosk to fill in necessary information; however, free access registration is not preferred.

• A notification process is established where hosts receive an email for approval before visitors can enter.

Streamlined Return Visits

• For repeat visitors, data retention policies allow retrieval of previous visit information based on valid time periods.

• Upon entering their ID or mobile number, returning visitors can quickly update only necessary fields like office level or company name.

QR Code Utilization

• A QR code will be generated for return visits, simplifying entry processes by categorizing flows and allowing scanning at various points.

• The QR code is typically valid for same-day use but can be customized based on customer needs.

Pre-registration Process

• Pre-registration is recommended via a web portal rather than a mobile app due to ease of access; links are sent via email.

• Once pre-registration is completed, visitors receive a QR code that facilitates entry through designated areas.

Approval Workflow

• Approval for visitor access depends on property management decisions; either tenants or receptionists may handle approvals.

• After approval, visitors receive their QR codes which they can use to gain entry into the building.

Validity of QR Codes

• The validity period of the QR code can be flexible, often set according to meeting times or general visitor policies.

Discussion on Visitor Management System Setup

Initial Setup and Client Interaction

• The working hours for the system setup are discussed, indicating a need for flexibility based on customer requirements.

• A meeting with the client is necessary to confirm preferences regarding authentication methods—either approval to the tenant or receptionist.

• Pre-registration options are highlighted, emphasizing that it can be done by either tenants or administrators, but mobile applications may not be user-friendly for visitors.

Software Configuration and Equipment Requirements

• There is a recommendation against using a mobile application for pre-registration due to its complexity for visitors.

• Discussion about necessary equipment includes firewalls and internet provision; clients may need to supply their own internet connection.

• Clarification on costs indicates that charges for value-added services (VAS) are typically one-time fees.

Advanced Features and Integration

• An overview of access control systems (ACS), including features like QR codes and facial recognition, is presented as part of the solution architecture.

• The speaker invites collaboration in experiencing the ACS features firsthand at their office, suggesting an interactive demonstration.

Technical Specifications and Protocol Discussions

• Confirmation of DCS upgrades related to turn style set integration is made, noting a shift from RCGF protocol to API-based communication (DCS 920).

• The discussion touches upon previous projects completed in Singapore using similar protocols, highlighting successful integrations with API connections.

Testing and Compatibility Considerations

• Emphasis on testing new versions of software before deployment is reiterated; compatibility with existing systems must be ensured.

• Clarification about low-level integration capabilities suggests ongoing development efforts to enhance system functionality.

Access Control Solutions Discussion

Proposal for Access Control Solution

• The discussion revolves around whether the proposed access control solution requires a new card or if clients prefer to use their existing cards, particularly in relation to car parking.

• It is noted that current users are utilizing two different types of cards for access and car parking, indicating a potential need for integration into a single card system.

Current Card Usage

• Clarification is made that the existing card used for car parking is separate from the one used for turnstile access, highlighting the fragmentation in card usage among services.

• There’s an intention to check with clients regarding specifications and possibly borrow a sample card from the car parking service to better understand requirements.

Project Timeline and Proposal Process

• A floor map will be shared along with a summary proposal based on today’s discussions. A questionnaire may also be sent out to gather further insights.

• The project timeline is set for Q4 of this year, indicating urgency in finalizing proposals and clarifications with building management.

Client Engagement

• The conversation confirms that they are proposing directly to end-users rather than property management, emphasizing direct client engagement in the proposal process.