Start with one building decision
Choose the use case. Define the building workflow, the decision AI could support, and the result worth measuring.
Check readiness. Review the systems, data, and evidence gaps before promising automation.
Set the controls. Decide who approves, overrides, and reviews outcomes, then plan a bounded pilot.
For a building team, a credible AI pilot starts with a defined operational or sustainability question. We review the systems and data behind the decision, record gaps and controls, and measure results against a baseline. Energy and carbon benefits are goals to test, not outcomes to assume.
System context
System inventory. List the building systems, owners, access paths, and workflow handoffs involved in one use case.
Decision boundary. Name what AI may observe, recommend, or do, and what stays with a person.
Evidence quality
Source quality. Identify which readings, records, and documents support the use case, how current they are, and who can correct them.
Baseline and test. Record the current outcome before piloting AI, then compare results with a defined review method.
Human controls
Approval and override. Decide which actions need a named human approver and how staff can stop or reverse an AI recommendation.
Review and accountability. Log evidence, exceptions, and outcomes so the pilot can be assessed before wider use.
Build confidence before expanding AI
Start with one operational question and a named decision owner. Map the system inputs, test whether the evidence is reliable, and set review and override rules. Then run a bounded pilot, measure it against the current baseline, and decide what to change before expanding.
01
Choose the use case
Define one building workflow, the AI-supported decision, and a result worth measuring before selecting tools.
02
Check readiness
Review the systems, data, access, and evidence gaps that must be resolved before a pilot.
03
Set the controls
Specify approval, override, and review. Run a bounded pilot and compare results with the baseline before expanding.
For a proposed building project, review how design decisions, system information and operational responsibilities will carry through construction and handover. Define one AI-supported use case, check the available evidence and agree on human oversight before planning a pilot.
Governed AI agents
for selected building workflows
Start with one workflow, the people responsible for it and the evidence needed to assess whether AI can help.
For a proposed AI agent, define the information it may use, the recommendations it may make and the actions that require human approval.
Building and facility teams can begin with a limited use case, such as preparing maintenance information or checking project handover records. Confirm data quality, access permissions and responsibility for exceptions before testing.
Test before expanding.
Compare the pilot with a baseline. Report changes in staff effort, accuracy or service quality only when supported by measured results. Scope and suitability depend on the systems and evidence available for the project.
Cognitive AI Enabled Architecture and Interior Design
About
For an architecture or interior-design project, begin with the decisions the design team needs to make and the information available to support them.
A proposed AI-supported task might organize approved project information or help compare documented requirements. Confirm the sources, assumptions and limits before using its output in a design review.
Architects, engineers and project leaders remain responsible for professional judgments and approvals. Define who checks recommendations and how conflicts or incomplete records are resolved.
For energy or sustainability questions, identify the baseline, relevant building records and the method used to assess a change. Do not present modeled opportunities as achieved savings.
For project handover, review whether the required records are complete, current and assigned to an owner. Confirm how design information will reach the facility team and how missing or conflicting records will be resolved.
Include the people who use and operate the space. Treat occupant feedback as evidence to review with the project team, with clear ownership of any resulting action.
Start with a bounded review or pilot.
Agree on acceptance criteria, handoff information and responsibilities before expanding the work.
AI-Supported Project Management
Start with a defined project-management task, such as preparing a status summary, organizing approved records or reviewing an action log. Decide which information is authoritative and who owns the final decision.
AI-supported reviews depend on the completeness and quality of project records. Treat possible risks as items for a qualified team member to investigate, with the evidence and uncertainty visible.
Agree on the source systems, update frequency and access permissions before proposing an integration. Assign responsibility for checking summaries and communicating approved changes to stakeholders.
Use recommendations to support the project team. People remain responsible for validating the underlying information, resolving conflicts and approving decisions about scope, cost and delivery.
For a limited pilot, compare the output with representative source records. Review accuracy, missed exceptions and the staff effort required to check the work.
Define acceptance criteria and support responsibilities before expanding a workflow. Report benefits only when measured against a baseline.
Bring one project workflow and its current challenges to a readiness discussion.
In the Fast-Paced World of Facility Management, Your Future Awaits with Cognitive Corp
AI Readiness for Facility Management
Assess One Facility Workflow
Facility teams balance service quality, resources and building performance. An AI readiness review starts with the current process and the evidence needed to judge a proposed change.
Leadership and Strategy: Define the Decision
Connect a proposed AI use case to an operational decision, a responsible owner and a measurable objective. Agree on what a limited assessment or pilot should establish.
Project Information: Review the Evidence
Review the completeness, currency and ownership of project and maintenance records. Resolve missing information and define handover responsibilities before using those records in a proposed workflow.
Human Factors: Include Occupant Needs
Include occupant feedback and the needs of facility staff in the review. Confirm privacy requirements and how feedback will be assessed before using it to guide a change.
Technology: Check Readiness
Review source systems, integration requirements, data ownership and permissions. Define which actions require human approval and how exceptions will reach the responsible team.
Finance and Business: Define Cost and Responsibility
Compare implementation, licensing, review and support costs with the current process. Agree on scope and delivery terms before work begins; report savings only when measured.
Operations and Maintenance: Start with One Workflow
Select a bounded task, such as preparing maintenance information for review. Check source records, escalation rules and recovery from errors before testing the workflow.
Communication and Risk: Assign Ownership
Identify who checks the information, approves changes and communicates decisions. Record unresolved risks and evidence gaps so they remain visible to the project team.
Discuss a Defined Assessment
Bring one facility-management question and the records available to support it. Agree whether a scoped review or pilot is the appropriate next step.
The Brain Trust Behind Cognitive Corp's AI Revolution
Corporate Advisory Board // Core Team
Ted Ritter, IFMA fellow - CMO
Principal, Lead Management Institute
Global Co-Chair, Technology Community of IFMA
Past Chair, IFMA Americas Advisory Board
Corporate Advisory Board // Core Team
Amanda Muzzarelli
Principal, AM Consulting
Director Facilities Management State Farm (past)
Corporate Advisory Board // Core Team
Jonathan Lett - CFO
Principal: Griffith, DeLaney, Hillman & Lett
PCAOB, CPA
Corporate Advisory Board Chair // Core Team
James C. Waddell - Svp
Managing Director, Cognitive Corp
Previous: CannonDesign
Previous: Plantronics
Corporate Advisory Board
Antony Slumbers
Founder: antonyslumbers.com
Leadership Board: CREtech
Advisory Board: Equiem
Corporate Advisory Board
Henry Massey
Co-Founder & CMO: ELORA
Head of Emerging Tech, IFMA: Workplace Evolutionaries
Sr. Director of Enterprise Solutions, NavigatorCR
Corporate Advisory Board
Vik Bangia, MCR
CEO: Verum Consulting
VP Global Real Estate: Ameriprise (past)
SVP Global Client Solutions: Realogy Holdings (past)
Corporate Advisory Board
Gordon Wright
Senior Principal, Firmwide Director of WorkPlace, HOK
Senior Vice President, Global Services: Nelson (past)
Senior Manager, Real Estate Technology: KPMG (past)
_edited.jpg)
Corporate Advisory Board
Adam Wilbrecht, AIA
Chief Product Officer: CONCERT
Director of Design Technology : Cunningham (past)
Corporate Advisory Board
Stan Gibson
Principal, Oxygen Plus
Sr. Vice President CRE: Wells Fargo (past)
Sr. Vice President: Trellis Real Estate Group (past)
Corporate Advisory Board
Hunter Fleshood, MCR
CBRE, Global Lead - Workplace Technologies
Head of Sales: Siemens (past)
Enterprise Sales: WeWork (past)
AI Association Advisory Board
Arthur Alter
Chief Commercial Officer, Buildings IoT
Advisor, Checkhub
Advisor, TopHat
AI Association Advisory Board
Joya Scarlata, MBA
Director Digital Marketing: InterralIT
AI Association Advisory Board
Chris Daigle
CEO + Co-Founder: ChiefAIOfficer.com
Founder: Daygull Strategic