Guardian IMS

Guardian IMS, QIT Plus and a future Aura connection

Council integration · Council plan crosswalk · Questions · Evidence

AI-generated public-source research and partnership proposals · checked 21 October 2026. Official records, published customer arrangements and vendor descriptions are identified separately below. Proposed Aura connections describe a development path. This research has involved no contact with Council or QIT Plus and no access to customer accounts or protected systems.

Guardian IMS is incident-management software made by QIT Plus. The vendor describes it as helping organisations organise information and work during incidents and everyday operations. Think of the working desk behind a public notice: people record what happened, locate it on a map, assign work, report progress and hand over to the next shift. A public disaster dashboard is a related product with a different audience and access level. QIT product descriptions

The working scenario requested by Luke: if Guardian continues as Council's contracted system and develops well, people with Auras could eventually interact with it through supported connections. This is a promising partnership direction: Guardian continues its agreed operational role, while Aura of Intelligence helps people understand information, communicate a need and learn the next step. Redland's plan documents Guardian use; the public material reviewed here does not establish its current contract term or renewal.

The company behind the software

What we can establish publicly	Source and meaning
QIT PLUS PTY LTD, ABN 95 128 637 598, ACN 128 637 598. ABN Lookup lists an Australian private company, with active ABN and GST registration from 1 December 2007, main business location QLD 4802.	Australian Business Register: ABN Lookup. This identifies the entity and published registration record; it does not establish shareholding or a customer contract.
The company says it was founded in 2007 by Chris Madsen and Phill Glindemann, following council experience. Its About page names Madsen as CEO and Glindemann as Chairman.	QIT Plus About. These are company-published history and roles, checked on the research date.
Its public pages list Australian locations including Brisbane and Cannonvale, alongside Canadian and Pacific operations.	About and Contact. Lists differ between pages, so we retain their published scope without inferring a corporate ownership structure or exact office count.
A public NSW supplier profile lists the same legal entity and ABN, with cloud support and software-development services.	buy.nsw supplier profile, marked updated 20 October 2025. Service categories are supplier-identified; the listing is distinct from approval of a particular procurement.

Understand the different products

Offering	Publicly described role	What matters for an Aura connection
Guardian IMS	The vendor describes multi-agency workflows, roles, tasks, maps, reports, requests for assistance, logistics and action/cost histories. It also advertises cloud and mobile access, training and two-factor authentication. IMS product	Establish the Council configuration, permitted actions and supported exchange. Its use of AIIMS refers to the Australasian Inter-Service Incident Management System, an incident-management framework.
Guardian Disaster Dashboards	A public-information product covering warnings, maps, resources and contacts, with optional notification features. Dashboard product	A natural place to begin public information discovery. Agree reuse, caching, accessibility and correction rules with the information owner and supplier.
Flood Intelligence Dashboard / BRIDGE	The vendor describes observed, historical and predictive flood information and a connection with Guardian IMS. Flood product	Keep an observation, forecast, model scenario and official warning identifiable. Confirm local data, configuration and validation before using an output for a particular decision.
Guardian IMS mobile app	App-store descriptions present mobile tasks, requests and road-closure functions as part of the larger IMS service. Apple Australia · Google Play	An app listed free does not establish free server access or integration rights. Confirm the supported platform, account, permissions and offline behaviour for the actual deployment.

The IMS page advertises an offline capability in its roads/maintenance description. That is a specific vendor claim to investigate: what can be captured, viewed and queued; what needs a connection; and how transmission and conflicts are handled later. It establishes neither complete offline operation nor the absence of useful offline features. Redland's documented cloud/paper continuity arrangements describe its plan and configuration at that edition. IMS source · Redland crosswalk

Public evidence of use and development

Redland: the supplied December 2025 management plan describes Guardian tasking, mapped work and reports at §6.2.8, printed p.75 / PDF76; information management and fallback appear at §6.2.4, printed p.74 / PDF75. These are documented local arrangements. The Council plan crosswalk connects them to the kiosk design.

Queensland Reconstruction Authority (QRA): its property-level flood-portal page identifies QIT Plus as the awarded supplier and says the Guardian/dashboard framework will support that solution. It also reports dashboard adoption separately from IMS use. The page is marked updated 23 September 2026. This is official procurement/program evidence, with delivery status and local configuration still specific to the program. QRA-led portal solution

Independent operational learning: IGEM's 2025 Significant Weather Events Summary Report, based on evidence to 14 October 2025, describes benefits from common Guardian use and assisting other councils. It also records cross-system information-sharing concerns involving Guardian, district and state platforms during the reviewed events. See printed/PDF pp.59–60. These are dated findings across the arrangements, rather than a current test of every product or installation. They give a practical reason to test a complete handover between systems. IGEM report

Vendor development direction: QIT's News page advertises a 28 October 2026 NSW user-group event, including Guardian V2 Dashboard, a mobile dashboard app and an update on future AI capabilities. This signals a published development conversation; it does not specify deployed AI functions or superintelligence. Its stated RSVP date was 16 October, already past on this research date. QIT News

Existing integration experience and the partnership opening

QIT publicly lists Office 365 email, a DocuSign API for situation reports, and connections between dashboards and its Roads Closed App. An API is an agreed way software exchanges information. These examples establish integration experience; they do not publish a general Guardian developer contract. Its Partners page also exists, but the reviewed pages did not provide developer-program terms, an open interface specification or test environment. QIT integrations

The vendor's linked 2025 newsletter describes configurable packages, ReadSpeaker accessibility support, StoryMaps, training and support during activated disaster coordination. It describes scalable AWS hosting for dashboards. These are useful questions for a discussion, with the purchased configuration, hosting region, recovery promises and support terms to establish for the actual service. QIT newsletter

AI-generated partnership proposal: develop a connection with Council as the service/information owner, QIT Plus as the platform supplier, prospective Ready S.E.T. Co-op participants as the community service team, and people choosing how their Auras assist them. Include the relevant cultural custodians, receiving services and qualified reviewers for each scope. Ready S.E.T. Co-op means Ready Sustainable Employment and Training Cooperative; its formation and operating mandate remain development milestones.

Potential working arrangements to explore include a Council-sponsored extension, a commissioned supported connector, a joint research/pilot agreement, or a supplier-supported integration partnership. These are proposed options; the reviewed public material does not establish their availability or commercial terms. Establish how each party contributes, gets support and maintains the connection as both platforms evolve.

How people with Auras could connect

The following levels are AI-generated design proposals, to develop through agreed information and service interfaces. Aura of Intelligence is Luke's personal AI operating system in development, from light to ultra high definition. A person chooses what context to share; public information and assistance remain available through guest and assisted routes.

Proposed level	Useful experience	Agreement or evidence needed
Find and understand public information	An Aura helps someone find a relevant notice, hear or read an explanation, and follow the issuer's action. The original source, area, time and correction remain visible.	Approved public source or feed; reuse and accessibility conditions; clear separation of source content and AI explanation.
Prepare and send a person's request	With the person's choices, an Aura helps describe the need and sends the permitted information to an agreed receiving service. It shows locally saved, received and accepted as distinct states.	Supported submission route, minimum required information, receiving duty, consent or other applicable basis, receipts, escalation and correction. A personal profile need not be a condition of assistance.
Assist an authorised worker	A worker's Aura could prepare a draft task, retrieve an approved procedure, assemble a source-linked report or support a shift handover.	Actual staff identity, supported delegation and role permissions, review/publishing rules, audit trail and revocation. Personal use of an Aura does not create staff privileges.
Coordinate continuing community services	The proposed kiosk network connects permitted needs, offers, learning and resource readiness across everyday service and recovery.	Agreed ownership and referrals, qualified cover, current availability and a maintained exchange contract. Sensitive records retain their appropriate access.
Grow AI/SI, twins, XR and robotics capability	More capable assistants could compare dependencies, rehearse an event and prepare better options; supervised equipment could perform agreed inspection or delivery tasks.	Demonstrated capability and authorised scope for the specific task. Preserve observations, model assumptions, human decisions and results. A tool's greater intelligence does not itself appoint an operational decision-maker.

One practical example is a cancelled ferry: an Aura explains the checked cancellation, helps a person state an accommodation or assistance need if they choose, and shows the receiving service's real response. A disconnected kiosk can preserve the request with a clear local status. The agreed service controls acceptance, allocation and response; a later connection reconciles the record and its receipts.

A practical route to seeking a partnership

1. Prepare a shared problem brief. Use the Council integration evidence template: people served, existing arrangement, proposed Aura contribution, sample journey, information needed and measurable benefit. The existing JOB-15 can carry this work.
2. Seek Council's sponsorship for discovery. Through the Council approach route, ask the appropriate service owner to confirm Guardian's role, contract/interface permissions and relevant reviewers. Prepare the material now; actual outreach is a separate recorded action.
3. Invite a joint technical and service discussion with QIT Plus. Use its published contact/demonstration route when authorised. Ask which supported feed, export, API, webhook or commissioned connection fits the use case. A webhook is a message sent when something changes. Agree a suitable user-group or roadmap contribution route rather than assuming membership or access.
4. Choose the partnership and support arrangement. Identify the actual applicant/operator and parties, information custody, licences, intellectual property, accessibility, fees, liability/insurance, procurement requirements and ongoing maintenance. Keep ownership of a person's Aura context separate from an incident record's lawful custodianship.
5. Build with fictional data in a test environment. Agree the exchange format, identifiers, dates, permissions and receipts. Test a changed warning, duplicate request, withdrawn permission, interrupted connection, failed component and relief handover. Compare outcomes and staff effort with an agreed baseline.
6. Review a bounded pilot and then extend it. Record the exact site, service, configuration, support and responsible decisions. Demonstrated benefits can support broader integration while Council, QIT Plus and community participants continue improving their parts.

This pathway works under the user's scenario of Guardian continuing and evolving. It also encourages documented, portable exchanges so a person's Aura and the community service can remain useful as suppliers and software editions change.

Questions for a supported connection

Area	What to establish together
Interface and permissions	Which modules, fields and actions are available? What authentication, user delegation, test environment, change notifications, limits and compatibility promises apply? Public visibility, a user account and permission for an automated connection are distinct scopes.
Disconnected operation	Which functions work without which connection? Where are queued records held, how are they protected, and what confirms receipt after reconnection? Preserve issuer-supplied validity/expiry, review dates, corrections and unresolved conflicts.
Data and AI use	Who holds which records, for what purpose and duration? What can an Aura retain, retrieve or explain? Which model providers may process it, under what restrictions, and how are correction, withdrawal and training-data choices handled?
Security and hosting	Request applicable certification scope/current certificates, hosting and backup locations, access controls, incident procedures, independent assurance and restoration evidence for the chosen service. QIT's site states ISO 27001/9001 certification; certificate-level and deployment coverage were not independently established here. Vendor statement
Privacy and commercial support	QIT's public privacy policy displays 07/01/20 and covers website/business information. Establish the current customer data arrangements and service/support agreement. A public policy, app-store declaration or marketing description cannot specify every Council deployment. Privacy policy
Shared success and continuity	Who maintains the connector, explains a failed exchange and pays continuing costs? Which measures show better comprehension, correct handovers, less duplicate entry and useful outage performance? How are records exported and responsibilities handed over if the connection ends?

Use professional review to record evidence, reasonable improvements and deficiencies in either approach. Human review records the people deciding the actual scope. This page provides a researched starting point for partnership development; agreements and measured results follow as the work progresses.

Research trail

The Guardian research record preserves the user's request and partnership clarification, source identities, dates, limited findings and review boundaries. Sources retain their rights; this page uses short paraphrases and links rather than republishing complete vendor sites. Product descriptions are vendor statements, official customer/program records have their stated scope, and future Aura connections are explicitly AI-generated proposals.