A Unified Platform for the ACU STEM Centre for Education and Engagement

1.0 Executive Summary

1.1 Introduction

ACU's vision for the STEM Centre for Education and Engagement is clear: a space that is not only technologically advanced, but coordinated, responsive, and unified in how it operates. The goal is to create an environment that inspires curiosity, supports research and teaching, and provides seamless access to equipment and space — without requiring users to understand the systems behind it.

Today, the challenge is not the absence of good technology — ACU has invested in excellent building systems, enterprise Wi-Fi infrastructure, and AV environments. The challenge is that these systems operate independently, requiring manual effort to bridge the gaps between teaching, research workflows, visitor experience, compliance, and safety. In environments where hands-on learning and equipment usage are critical, these gaps create friction — and friction impacts participation.

PlaceOS is designed to remove that friction.

PlaceOS is a unified integration and automation platform that sits above existing building, AV, research lab, access, security, scheduling, and workflow systems. Rather than replacing infrastructure, we connect it — enabling one system to inform and trigger another, and creating configurable workflows that match how ACU wants the space to function. This provides a consistent, reliable experience for students, staff, researchers, industry partners, outreach visitors, and administrators.

Crucially, the platform aligns with ACU's goals for:

PlaceOS becomes the operating system of the built environment, ensuring all systems, data, and workflows support the shared purpose of the STEM CEE: to encourage participation, curiosity, and a sense of welcome.

1.2 The PlaceOS Vision: Beyond Siloed Solutions

The RFP outlines eight critical technology applications to be supported in the new facility. While these solutions can be sourced individually, this approach invariably creates data silos, exponential management overhead, and a disjointed user experience.

PlaceOS provides a superior alternative. Our solution is a single, open platform that serves as the "central nervous system" for the building. It is an integration and automation layer that connects all other systems, allowing them to communicate and act in concert.

1.3 A Single Platform, Multiple Core Applications

Our solution is comprised of three main components that work together to meet all RFP requirements:

1.4 Key Benefits for ACU

Occupancy-Based Cost Savings

One of the most compelling benefits of PlaceOS is the ability to drive significant operational cost savings through intelligent, occupancy-driven automation. By fusing real-time occupancy data from multiple sources (Wi-Fi, sensors, cameras), PlaceOS enables the STEM CEE to optimize HVAC, lighting, and other building systems based on actual usage rather than static schedules.

2.0 The PlaceOS Solution: Platform Architecture and Integration

2.1 The PlaceOS Abstraction Layer

The primary challenge of the RFP is not simply finding a room booking application; it is finding a platform that can make a room booking application, a Building Management System (BMS), an access control system, and an academic timetabling system all speak the same language.

ACU has specified several best-in-class, disparate systems: a Tridium Niagara AX BMS for HVAC and lighting, Gallagher for access control, Microsoft O365 for ad-hoc meetings, and TimeEdit for academic timetabling. Individually, these systems are unaware of each other.

PlaceOS acts as the "abstraction layer" that unifies them.

Example Automation Workflow:

1. WHEN a booking is made in O365 or TimeEdit for a specific lab;
2. THEN PlaceOS checks the real-time occupancy data from Cisco Wi-Fi to confirm the lab is empty;
3. THEN PlaceOS tells the Gallagher module to grant the booker's mobile credential access for the duration of the meeting;
4. AND PlaceOS tells the Tridium module to activate the "Meeting" HVAC and lighting scene 10 minutes prior.

2.2 Key Solution Components

• PlaceOS Core: The on-premise or private cloud integration engine that houses the drivers, logic, and core APIs.
• PlaceOS Applications: The user application for building users (staff, students, visitors), providing the unified mobile and web interface.
• PlaceOS Digital Signage: The platform for creating, managing, and scheduling content on all digital displays.

2.3 Off-the-Shelf Platform Applications

While PlaceOS is a platform first, it includes a suite of ready-to-deploy applications designed specifically for environments like ACU — where buildings serve many stakeholders with different modes of use.

2.3.1 Workmate — User Experience App

This solution is used extensively by global workplaces and can be tweaked for student experiences (and of course, be used by professional staff on campus).

2.3.2 Stagehand — Real-Time Support & Operations

Designed for IT, AV, Facilities, and Operations teams.

• Real-time monitoring of rooms, devices, and building systems
• Remote AV control and reset
• First-level support troubleshooting tools
• System health, uptime, fault logging, and reporting

This reduces on-site technician workload, and increases uptime of shared facilities.

2.3.3 Backoffice — The Administration & Configuration Layer

A secure configuration and automation environment for:

• Automation rules and workflows
• Integration and driver management
• System logs, alerts, and administration including remote debugging
• Building and campus-wide configuration templates

This ensures consistency across rooms, buildings, and campuses, while maintaining flexibility where needed.

2.3.4 Studio — Any PlaceOS input to any output

Studio allows ACU to create new workflows in minutes, without software development. It allows you to directly connect PlaceOS drivers in a system - for example, occupancy with automation.

2.3.5 Build Your Own — Custom Interfaces

Beyond our turnkey applications, PlaceOS provides comprehensive APIs that enable you to create custom-built interfaces tailored to specific user groups and stakeholders.

Example: ACU STEM Centre Custom Dashboard

Below is an interactive mockup demonstrating a custom-built interface designed specifically for the STEM Centre. This example shows real-time space occupancy, equipment availability, booking functionality, wayfinding, and visitor management — all powered by PlaceOS APIs and tailored to ACU's brand and workflows.

This mockup demonstrates how PlaceOS APIs can be used to create custom interfaces that integrate real-time building data, calendaring systems, access control, and environmental sensors into a unified experience designed specifically for ACU's needs.

2.4 ACU Technology Integration Strategy

To provide immediate, clear confirmation of our integration capabilities, the following table details our solution for every technology specified in the RFP.

3.0 Detailed Response to RFP Requirements

This section provides a detailed, point-by-point response to every functional and technical requirement.

3.1 Section 2: Occupancy Sensing

PlaceOS Approach:

Instead of relying on a single sensor type, PlaceOS delivers a "fused data" solution that leverages all available infrastructure as requested in Section 2.2.4 of the RFP. We will ingest and "fuse" data from:

• Cisco Wi-Fi Network: To provide broad, anonymized location and count data.
• Tridium BMS: To pull "occupied/unoccupied" data from existing mechanical and lighting (PIR) sensors.
• AV Cameras: To provide highly accurate, granular "people counting" data via API integration.

Any single data source has flaws: Wi-Fi is not precise to a single seat, PIR sensors only detect motion (not count), and cameras can have privacy implications. By fusing all three, the PlaceOS logic engine can determine true occupancy with high accuracy.

3.2 Section 3: Journey Mapping and Analysis

PlaceOS Approach:

This is a direct extension of our Occupancy solution. By leveraging our native integration with the Cisco Spaces platform, we ingest the real-time, anonymized location data from ACU's Wi-Fi access points. This allows for powerful analysis of movement, dwell time, and congestion.

3.3 Section 4: Visitor Management

PlaceOS Approach:

Visitor Management is a core, out-of-the-box feature of our PlaceOS Workmate application. It is fully integrated with O365 and MS Teams to provide a seamless journey from pre-registration to host notification.

3.4 Section 5: Wayfinding

PlaceOS Approach:

We deliver a best-in-class wayfinding experience within the PlaceOS Workmate app by integrating MapsIndoors, a world-leading indoor mapping provider. This solution is built on Google Maps, providing a familiar user experience, and leverages the Cisco Wi-Fi network for real-time indoor positioning.

3.5 Section 6: Resource Management

PlaceOS Approach:

This functionality is provided by the Asset Manager and booking modules within PlaceOS Workmate. It allows ACU to digitize its entire library of bookable resources (equipment, studios, 3D printers, cameras) and manage them through a single, reportable system.

3.6 Section 7: Space Management

PlaceOS Approach:

This is a cornerstone of the PlaceOS platform. The primary challenge for any university is the "dual-calendaring" problem: the official academic timetable (in TimeEdit) and the ad-hoc staff meeting calendar (in O365) are separate, leading to booking conflicts.

PlaceOS is uniquely positioned to solve this at the integration layer.

• Our TimeEdit driver will pull all academic bookings from the TimeEdit API.
• Our O365 driver will pull all staff bookings from the Microsoft Graph API.
• The PlaceOS Logic Engine fuses these two calendars into a single, unified availability view for every room.

3.7 Section 8: Building Experience

PlaceOS Approach:

This section is the PlaceOS solution. The PlaceOS Workmate app is the "Building Experience" solution the RFP describes. It is the single, unified mobile/web application that provides the interface for Wayfinding, Booking, Visitor Management, and all the advanced integrations.

3.8 Section 9: Content Management System

PlaceOS Approach:

We will deliver our dedicated PlaceOS Digital Signage platform. This is a modern, web-based CMS designed for creating, managing, and scheduling content across a large and diverse network of displays.

The RFP mandates support for Samsung Tizen and LG WebOS System-on-Chip (SoC) platforms. Our playback is via standard HTML, so as long as these platforms support this, our content can display. Each display gets a unique URL. For ChromeOS-based players, we can manage this via a Google Sheet or MDM software. For your Samsung and LG platforms, we would need you to test deploying the URLs and that web playback works fine on these devices.

4.0 Integration, Management, and Support

PlaceOS confirms our ability to meet all requirements for integration, management, and support.

4.1 Interfacing with ACU Infrastructure

Our driver-based architecture is designed specifically to interface with a complex, multi-vendor environment like ACU's.

4.2 Multi-Tiered User Permissions

The PlaceOS platform provides granular, multi-tiered Role-Based Access Control (RBAC) across all modules. We will configure roles as specified (e.g., User, Staff, Researcher, Operational IT Support, Administrator) with distinct permissions for viewing data, booking resources, and configuring systems.

4.3 SSO/LDAP Integration

PlaceOS fully supports SAML 2.0 and LDAP integration. We will configure the platform to authenticate against ACU's Active Directory, providing a seamless and secure single sign-on experience for all staff and students.

4.4 Support and Maintenance Plan

PlaceOS provides a comprehensive support agreement.

4.5 Cybersecurity Adherence

PlaceOS confirms our adherence to all ACU cybersecurity policies. We welcome and will fully cooperate with the client security team's evaluation as requested. Our architecture is flexible and can conform to your requirements, including deployment in your environment. For more info please review our tech docs at https://docs.placeos.com/placeos/reference/security-compliance/faq/

5.0 Proven Success: The PlaceOS Smart Campus

5.1 Addressing the RFP Requirement

Section 10 of the RFP requests "Case studies or references from existing clients, particularly those based in Australia or with Australian support teams". We are uniquely positioned to meet this.

5.2 The University as a "Smart City"

PlaceOS is uniquely suited for the higher education environment. A university campus is a complex ecosystem of diverse stakeholders (staff, students, researchers, visitors, facilities managers, IT) and diverse spaces (workplaces, labs, lecture halls, public venues, retail). The PlaceOS "Smart Campus" blueprint is designed to unify this complexity.

5.3 Flagship Higher Education Case Study: UCLA

PlaceOS has a multi-year strategic product development alliance with UCLA. We are working with their audiovisual design and support division (Digital & Technology Solutions) to transform how students, faculty, and visitors interact with UCLA's physical spaces. This collaboration focuses on creating intelligent, data-driven, and highly personalized experiences—a vision that directly aligns with ACU's goals for the STEM CEE. This reference provides irrefutable proof of our capability in a world-class university setting.

5.4 Australian Presence and Support

PlaceOS is an Australian company, headquartered in Sydney. Our office is located at the Sydney Knowledge Hub, University of Sydney. We are not just an Australian reseller; we are an Australian technology partner embedded within the local university ecosystem. This provides ACU with unparalleled local access to our core engineering and support teams.

6.0 Implementation, Commercials, and Proof of Concept

6.1 Implementation Timeline

We propose a collaborative, phased implementation to de-risk the project and ensure a successful launch, based on our proven 6-8 week deployment model.

6.3 Availability for Proof of Concept (POC)

PlaceOS confirms our availability to provide a proof of concept as requested.

We can host a PoC environment and connect, provide our turn-key interfaces and existing integration drivers for the PoC project. Then use this project to scope any required customisations.

6.2 Pricing Model (CAPEX and OPEX)