3 Foundations
Shared Vocabulary and Terminology for Understanding the Process
1.1 Built Environment Ecosystem 1.1.1 Components 1.1.2 Phases1.1.3 Steps 1.1.4 Procedures 1.1.5 Tasks 1.1.6 Techniques 1.1.7 Tools, Templates and Deliverables 1.2 Strategy and Planning 1.2.1 Strategic Planning 1.2.2 Business Process 1.3 Real Estate 1.3.1 Site Selection Requirements 1.3.2 Market Survey and Site Selection 1.3.3 Transaction 1.3.4 Approval and Contracting 1.4 Design and Construction 1.4.1 Project Planning 1.4.2 Programming 1.4.3 A&E Selection and Schematic Design 1.4.4 Design Development and Construction Documents 1.4.5 Construction and Commissioning 1.4.6 Occupancy Planning and Move Plan 1.4.7 Exit Plan 1.4.8 Decommissioning 1.4.9 Post-Occupancy Activity 1.5 Operations and Maintenance | 1.5.2 IT Support 1.8.1 Enterprise Support Systems 1.9 Digital Ecosystem 1.10 Workplace Experience Technology |
This chapter establishes a shared vocabulary for connecting property, facilities, workplace services, and the information used to make decisions. The chapter moves from strategy and business processes through real estate, design and construction, occupancy, operations, and renewal or exit. It then distinguishes data, information, knowledge, intelligence, and artificial intelligence before introducing a systems framework that combines AI, software, data, and people. The comparison of rule-based software and AI clarifies their different roles and limitations. The systems catalogue identifies resources supporting enterprise operations, real estate, facility planning and programming, project delivery, and facility operations, alongside general-purpose assistants and specialized computational applications. The concluding Digital Ecosystem section connects these resources through a common information foundation, an analysis and decision-support layer, and a lifecycle feedback loop.
The built environment ecosystem is the network of organizations, people, places, infrastructure, services, processes, and information that enables an enterprise to operate. Physical assets and workplace services must be considered alongside the activities they support. Facility decisions affect property commitments, technology, operating costs, occupant experience, and adaptability. Whole-building guidance emphasizes integrated design and collaboration rather than isolated disciplinary decisions.
Components are the principal parts of the ecosystem: strategy and planning; real estate; design and construction; operations and maintenance; and the data and systems connecting them. People, governance, finance, technology, and specialist advisers support these components. Distinguish physical assets from organizational responsibilities and enabling services. A component map records ownership, interfaces, and dependencies.
Phases are broad periods of work with a shared purpose and a defined decision boundary. A working sequence is strategic assessment, requirements definition, option evaluation, commitment, delivery, occupancy, operation, and renewal or exit. Phases may overlap and recur; this is not a universal contractual sequence. Define the evidence and authority needed to advance and the consequences of unresolved assumptions.
A step marks progression within a process. An activity is the work within a step undertaken to achieve its purpose. Evaluating a facility option may involve reviewing records, interviewing users, assessing constraints, developing alternatives, and documenting comparisons. Sequence dependent activities while allowing independent work to proceed in parallel. A process map connects activities, inputs, review points, and outcomes.
A procedure describes how to perform an activity consistently. It identifies the trigger, responsible roles, inputs, sequence, checks, exceptions, and completion record. A space-program review procedure, for example, may specify how comments are consolidated, conflicts resolved, and approvals recorded. Procedures make governance repeatable without replacing professional judgment.
A task is a bounded unit of work assigned to an accountable role, with a defined scope, dependencies, timing, and acceptance criteria. Verifying an area measurement or recording a lease deadline should produce reviewable evidence. A task register links actions to their activities and deliverables.
Techniques are methods for investigating questions, developing options, or evaluating evidence. Examples include interviews, surveys, observation, document review, adjacency analysis, scenario testing, benchmarking, and sensitivity analysis. Select methods to suit the decision and available evidence, recording sampling boundaries, assumptions, and uncertainty. Sophisticated methods cannot compensate for unrepresentative evidence.
Tools, templates, and deliverables represent distinct categories of resources and outputs. Tools and templates enable work; deliverables communicate accepted results. The instruments to do work, like spreadsheets, databases, software and AI assistants, are tools. Templates provide guidelines and reusable structures for organizing consistent inputs and outputs. Deliverables, such as a program of requirements (POR), option appraisals, approved budgets, and handover records, may be documents or presentations. Here is the breakdown of the differences between them:
|
Dimension |
Tool |
Template |
Deliverable |
|
Primary Role |
The instrument used to do the work |
The guideline/structure to organize the work |
The reviewable output issued to the client or stakeholder with identifiable status and version |
|
Nature |
Software applications or instruments used to perform work |
Static framework or pre-formatted document |
Completed output, report, or asset |
|
Lifecycle Timing |
Used as needed throughout the planning and project lifecycle |
Applied at the start of document or task creation |
Prepared and updated during work, then issued for review, decisions, or handoff |
|
Conventional Methods: |
Spreadsheet software; document editor; presentation software; flip charts; analysis cards; sticky notes; photographs |
Spreadsheet layout; report outline; presentation slide layout |
Completed spreadsheet, finalized report; stakeholder presentation |
|
Typical AI Agents |
AI agents and platforms: Microsoft Copilot Studio, Gemini, ChatGPT; Claude; Perplexity |
AI agent templates: Reusable instructions specifying source documents, summary headings, and review steps. |
|
Planning begins with defining the organization’s need, not an assumed solution. Strategy develops desired outcomes and the choices guiding resource allocation. Planning translates those choices into requirements, alternatives, actions, and review points. Strategic predesign connects organizational purpose with location, capacity, workplace arrangements, investment, and services.
Strategic planning establishes the business need, planning horizon, stakeholders, current conditions, and desired outcomes. Compare alternatives: retain existing provision, change services, adapt space, relocate, or develop new facilities. Separate mandatory requirements from preferences and identify assumptions that could change the preferred option. Key outputs include a planning brief, scenario comparison, implementation priorities, and decision record.
A business process is a connected sequence of activities that transforms inputs into an organizational outcome. Understanding it helps define space, equipment, technology, access, and service needs. Map demand, movement, interactions, handoffs, and exceptions before defining physical requirements. Distinguish current from intended practices so the facility does not preserve avoidable operational constraints.
Real estate planning determines where and under what arrangements an organization will occupy property. It connects location and space requirements with market options, tenure, cost, timing, and risk. Distinguish commercial availability from functional suitability and occupancy readiness. Project-specific legal, technical, environmental, and financial matters require qualified review; this chapter provides a planning vocabulary, not transaction advice.
Agree on requirements brief before comparing sites, distinguishing mandatory conditions from weighted preferences. Include the purpose of occupation, geographic boundaries, functional and physical needs, space-measurement basis, transport, parking, infrastructure, special constraints, budget assumptions, and availability. GSA guidance illustrates functional, performance, physical, special, and delivery requirements in public-sector leasing; its rules are not universal private-sector requirements.
A market survey identifies potentially suitable locations; site selection evaluates them against agreed requirements. GSA guidance links market surveys to locations capable of meeting stated needs. Compare shortlisted options consistently for functional fit, timing, total occupancy implications, constraints, and outstanding issues. Record sources and dates, distinguishing verified conditions from vendor statements and assumptions.
A transaction develops a commercial arrangement for the selected property, such as a lease, purchase, renewal, or other authorized occupation agreement. A negotiated proposal or preferred option is not authority to execute an agreement. Record the parties, premises, terms, costs, responsibilities, conditions, and matters requiring professional review, and align commercial terms with delivery and operational needs.
Approval brings the business case, requirements, commercial terms, costs, risks, and review findings to the designated executive. Record the decision and conditions before execution by an authorized signatory. Translate contractual obligations into implementation actions, deadlines, controlled documents, and accountable responsibilities. Approval of a property commitment does not authorize every later design change or expenditure.
Design and construction translate agreed needs into a delivered physical environment. Programming establishes requirements, design develops solutions, and construction implements approved scope. Preserve traceability between requirements, decisions, estimates, changes, verification, and handover. Activities and responsibilities depend on the delivery method and professional agreements.
Project planning defines scope, governance, stakeholders, delivery strategy, milestones, budget basis, risks, and communication. Coordinate real estate, technology, security, operations, and occupancy interfaces. Establish review points, approving authorities, and required evidence. Key outputs include a project brief, responsibility map, integrated schedule, risk register, and change-control process.
Architectural programming is the research and decision-making process that defines the scope to be designed. Engage owners, users, and operations and maintenance personnel at a level appropriate to strategic planning or an individual project. Document functions, demand, relationships, space and equipment needs, performance expectations, constraints, and unresolved decisions. Establish an approved requirements baseline and its assumptions for design evaluation.
A&E denotes architectural and engineering services. Selection considers relevant expertise, scope, coordination, resources, and procurement requirements. Schematic design develops initial responses to the program through spatial organization, concept layouts, major systems approaches, and preliminary cost and schedule review. Compare alternatives against requirements, not appearance alone. Key outputs include an agreed services scope, selected concept, and outstanding decision record.
Design development refines the selected concept and coordinates architectural, engineering, equipment, and operational needs. Construction documents communicate detailed scope for procurement and implementation under the chosen agreements. Review the evolving solution against the program, budget, interfaces, and applicable requirements. Track scope and assumption changes and distinguish documents issued for review, procurement, and authorized construction.
Construction implements approved work while controlling changes, quality, records, and interfaces. Commissioning verifies and documents conformity with the Owner’s Project Requirements across planning, design, construction, testing, and transition to operation; it is not merely a final inspection. Handover evidence includes relevant test records, unresolved issues, operating information, and staff training records.
Occupancy planning defines how people, teams, equipment, and services will use the facility. The move plan coordinates readiness checks, sequencing, communications, transport, technology activation, access, and contingencies. Confirm physical and operational readiness before occupation. Key outputs include approved allocations, a move schedule, readiness criteria, and a post-move issue process.
An exit plan coordinates withdrawal from an existing location, including notice requirements, occupancy commitments, service continuity, asset disposition, information retention, condition review, and hand back responsibilities. Verify obligations against the actual agreements through qualified review. Link responsibilities and milestones to replacement accommodation and the move schedule.
Decommissioning is the controlled withdrawal of facilities, systems, equipment, and services from use. Distinguish reuse, relocation, disposal, isolation, and hand back activities, identifying specialist work requiring competent authorization. Coordinate records, security, environmental review, and continuity. Technical isolation and disposal require asset-specific procedures and professional oversight; this chapter does not provide those instructions.
Post-occupancy review compares actual use and operational experience with original needs and intended outcomes. Combine occupant feedback, space-use evidence, service issues, and relevant building-performance records. Distinguish transition problems from persistent requirements or design issues. Assign corrective actions and capture lessons for future programs; an isolated survey or snapshot is not a complete evaluation.
Operations and maintenance encompass the services, processes, competencies, and tools needed for facilities, systems, equipment, and occupants to perform their intended functions. This chapter groups workplace services with physical asset support to show their interdependencies, not to prescribe an organization chart. Operational records inform future planning and investment.
Office management coordinates everyday workplace services and user-facing support, including space and furniture, maintenance interfaces, cleaning, mailroom services, visitors, refreshments, and venues. Define responsibilities among local teams, landlords, vendors, and enterprise functions. Key outputs include a service catalogue, contact and escalation arrangements, and service expectations.
Space and furniture services maintain usable workplace arrangements and records of allocations, inventories, condition, and changes. Review requests against approved standards, accessibility needs, operational requirements, and available provision. Coordinate with occupancy planning and technical teams. Key outputs include current allocations, furniture inventories, and approved change requests.
Maintenance sustains asset and equipment function through preventive, planned, and responsive work. A computerized maintenance management system can track work and costs. Define how users report issues and facilities teams prioritize and close them, assigning specialist work to competent personnel. Key records include work orders, inspections, asset histories, and outstanding issues.
Janitorial services provide cleaning and routine care of occupied spaces. Facility guidance includes cleaning and related general maintenance within operational support. Define areas, frequencies, access, materials, quality checks, waste interfaces, and issue reporting. Match methods to surfaces and occupancy conditions; a cleaning schedule alone does not demonstrate service quality.
Office and mailroom services cover supplies, document distribution, deliveries, shipping, and mail handling. Define intake, storage, routing, collection, and exception responsibilities. Coordinate access, confidentiality, records, and continuity. Key outputs include service instructions, route information, appropriate delivery records, and escalation procedures.
Visitor experience spans invitation, arrival, reception, wayfinding, hosting, and departure. Integrate hospitality with authorized access and privacy arrangements, assigning responsibilities to hosts, reception, and security providers. Key outputs include visitor guidance, accessible arrival information, and an exception process.
Food and beverage services include refreshments, catering, service areas, and vendor coordination. Define service expectations, capacity, equipment, cleaning, storage, waste, and responsibility for applicable food-safety requirements. Use qualified providers and project-specific controls; this chapter is not a compliance procedure. Key outputs include a service brief and vendor responsibilities.
Venue management coordinates booking and preparation of meeting, event, and shared-use spaces. Address layouts, equipment, capacity, access, catering, and reset activities, identifying technical and safety reviews for non-routine events. Key outputs include booking rules, event requirements, readiness checks, and closure records.
IT support enables occupation and business activity through connectivity, devices, collaboration systems, and support channels. Define facility infrastructure needs, service dependencies, installation readiness, support responsibilities, and authorized access. Coordinate moves and changes with IT; a completed space is not necessarily technologically ready.
Business protection brings together the protection of people, assets, information, and operational continuity. It connects physical security, workplace safety, emergency arrangements, and enterprise risk functions. Define boundaries and accountable roles rather than assigning an undefined protection remit to facilities. Key outputs include a risk-informed service scope, contact arrangements, and reviewed continuity interfaces.
At the service level, business protection coordinates authorized access, security services, incident reporting, and location-specific continuity arrangements. Align local practices with enterprise policies and landlord obligations. Record responsibilities, escalation points, and review requirements. Appropriate specialists must develop and approve security and continuity procedures.
Workplace safety services coordinate hazard identification, escalation, competent review, occupant communication, and emergency interfaces. Define scope according to actual activities and the applicable jurisdiction, including contractor work and changes of use. This chapter is not a safety manual or compliance determination. Key outputs include assigned responsibilities, reviewed local procedures, and action and follow-up records.
Travel support connects organizational activity with workplace location. Define travel needs, authorized booking and expense arrangements, accessibility, continuity, and traveler communication. Consider how distributed operations and travel demand affect facility use and meeting requirements. Key outputs include defined service interfaces and confirmed policy responsibilities.
Occupancy planning aligns people and activities with available space over time. Compare approved demand with allocations, capacity, use patterns, and upcoming changes. Distinguish assigned capacity from observed utilization and forecasts from approved requirements. Key outputs include an allocation plan, demand assumptions, change priorities, and evidence informing portfolio decisions.
Moves, additions, and changes are bounded adjustments to occupancy, equipment, or workplace arrangements. Record requests, check dependencies, confirm approval, coordinate implementation, and update space, asset, access, and technology records. Completion requires operational readiness and accurate records, not physical relocation alone.
Small projects are limited scope works managed through proportionate planning and control. Classify them using approved organizational criteria, complexity, and risk—not an invented monetary threshold. Retain requirements, budget approval, competent design and safety review, change control, and handover appropriate to the work.
Facilities operations coordinate physical assets, infrastructure, and services for ongoing use. Operational guidance covers inventory, maintenance systems, operating manuals, cleaning, and supporting infrastructure. Maintain clear interfaces with office management and enterprise functions. Key outputs include asset and service records, operating plans, issue status, and renewal evidence.
Vendor management defines service scope, contractual responsibilities, communication, records, review, and escalation. Monitor delivery against agreed requirements and document outstanding work without substituting for contractual review. Coordinate access and competent oversight of technical activities. Key outputs include contract and service registers, review records, and action logs.
Facilities budgets organize anticipated operating expenditure and capital needs under agreed classifications. Distinguish recurring services, utilities, planned maintenance, responsive work, and renewal assumptions. Track commitments, actual expenditure, forecasts, and approved changes; explain material differences rather than concealing them through reclassification. Align area definitions, periods, and scope before comparing facilities or benchmarks.
HR support and workplace communication connect workplace arrangements with people-related policies and information. Coordinate workforce planning, onboarding, accessibility arrangements, and organizational changes with the responsible functions while protecting confidentiality. Distinguish information needed for space planning from personnel information restricted to authorized people functions.
HR/Employee Experience Support connects Human Resources and employee-experience functions with facility planning; confirm the organization’s preferred terminology before adoption. Facility interfaces include onboarding and departure coordination, approved workplace arrangements, and aggregate workforce assumptions. Avoid unnecessary use of individual personnel records. Key outputs include agreed interfaces, authorized information exchanges, and documented responsibilities.
Workplace communication explains services, access, changes, disruption, moves, and support channels. Define audiences, message ownership, timing, accessible formats, feedback routes, and correction procedures. Keep messages aligned with approved decisions and distinguish confirmed arrangements from proposals. Key outputs include a communication plan, current service guidance, and feedback records.
Data is recorded observations, measurements, or statements.
Information is data organized with context, definitions, and provenance.
Knowledge combines interpreted information with experience, methods, and understanding.
Intelligence applies relevant interpretation to a decision, including alternatives, implications, and uncertainty. Moving between these categories requires interpretation, not simply accumulation.
Artificial intelligence denotes engineered systems that generate predictions, recommendations, or content for a defined purpose. It is an enabling technology, not a further level of verified knowledge. Distinguish source records, analysis, generated interpretation, and authorized decisions. Define human roles and oversight according to context and risk; converting complex observations into model inputs may remove important context.
A system is a coordinated combination of people, processes, data, software, and governance organized to achieve a defined outcome. AI may support selected activities within that system.
Building, testing, and using systems supports improvement of the strategic predesign process. An integrated approach combines digital tools with human oversight to strengthen workflows, decision-making, and productivity. Evaluate performance against defined objectives and reviewed outcomes rather than assuming that integration continuously optimizes the process.
AI + Software + Data + People: This chapter uses four complementary pillars to organize digital systems transformation. Software applications and organized information provide the operating foundation; AI supports appropriate tasks; and people provide judgment, accountability, and ethical governance. The combination depends on the purpose and risk of the system, and not every workflow requires autonomous AI.
1. AI (Agents and Agentic)
An AI agent is an application that uses AI to interpret inputs, plan steps, and take actions through available tools toward a defined goal. Conventional software can also execute automated sequences without step-by-step human direction; the distinction is the agent’s use of AI to select or revise actions. Its autonomy depends on configured permissions, tool access, and human oversight.
Agentic AI describes goal-directed workflows in which AI helps plan and execute multiple steps, use external interfaces or software tools, and coordinate with other agents or people. Unlike a single prompt-and-response exchange, these workflows can continue across several actions. Autonomy and duration depend on the implementation, permissions, and review checkpoints. Attempts to revise plans or correct errors do not guarantee successful recovery.
2. Data (Controlled, Public, and Open)
The foundational information for digital systems, categorized by access and governance:
3. Software (Integrated & Automated)
Software provides infrastructure and applications for connecting tools, reducing manual transfers, and executing routine work. Integration enables exchanges between platforms when interfaces, data definitions, and permissions are compatible. Automation executes configured actions under rules or approved AI-supported workflows. Review data transfers, exceptions, and authorization rather than assuming seamless operation.
4. Judgment and Accountability
The crucial human-led elements within any high-performance system. Human critical thinking, contextual understanding, and ethical evaluation guide goals, evidence interpretation, and decisions throughout the system’s operation. This role is especially important in strategic decisions and ambiguous situations, not only when an algorithm fails. The clear assignment of responsibility for system outcomes, ensuring that human operators oversee, validate, and take ownership of AI-driven or automated actions.
The systems framework connects strategic planning, programming, user engagement, and project scoping with AI assistance, software, structured data, and human judgment. Its aim is to reduce avoidable manual work and improve the use of evidence while retaining review and approval. The following examples show how each pillar can support strategic predesign; results depend on data quality, integration, and accountable implementation.
1. AI (Agents and Agentic)
AI tools can assist analysis of interview transcripts, workshop notes, and surveys by identifying candidate themes, conflicting spatial requirements, and cultural priorities. Preserve source references and qualifications, and have responsible reviewers check whether the synthesis represents the supplied material accurately.
AI-supported tools can draft initial spatial matrices, space programs, and adjacency options using supplied historical project parameters, relevant building-code material, and client goals. Treat these outputs as candidates for review, not approved requirements or evidence of compliance. Verify assumptions, quantities, relationships, and applicable constraints before using them to guide design.
2. Data (Controlled, Public, and Open)
Use authorized internal information—such as client organizational structures, past post-occupancy evaluations, corporate brand standards, and historical costs—to inform recommendations. Apply secure access controls and review whether the evidence is current, relevant, and consistent with the client’s objectives and requirements. Access control alone does not ensure recommendation quality.
Incorporate relevant benchmarks, zoning laws, urban demographic trends, sustainability standards, and climate data into site and building-type analysis. Check each source’s date, jurisdiction, authority, reuse terms, and applicability. Distinguish openly licensed data from other publicly accessible information.
3. Software (Integrated & Automated)
Connect collaborative workspace tools, such as Google Workspace, with CRM data and planning databases to reduce manual transfer of client inputs into the business case, project-governance documents, and requirements documents. Verify data mapping, permissions, and review status so integration preserves meaning and does not turn unreviewed inputs into approved requirements.
Use automated scripts to generate baseline predesign reports, track review milestones, and flag missing data before decision gates.
4. Judgment and Accountability
Algorithms and software can process data and generate options but experienced predesign strategists apply critical thinking to interpret nuance, navigate complex client politics, and balance competing stakeholder values.
Leaders maintain ultimate accountability for the final business case, project governance and program of requirements, ensuring that AI-assisted insights are rigorously validated against real-world constraints, ethical considerations, and client vision.
Selecting the right combination of tools requires distinguishing explicitly programmed rules from learned-model behavior. Both can operate within the same software system. The following comparison considers how these approaches produce outputs, handle inputs, change over time, and require validation.
1. How They Work (Rules vs. Patterns)
Rule-Based Software: Executes explicitly programmed instructions and logic, such as an if-then rule directing a button click to save a file to a specified folder. A deterministic function produces the same result when its inputs, configuration, and relevant state remain the same. Application behavior can still depend on changing external conditions and contain errors.
AI: Many AI systems use models trained on data to identify patterns and relationships rather than specifying every response through explicit rules. When given an input, the model generates an output based on its training, configuration, and available context. A statistically likely output is not necessarily a correct response or an appropriate action.
2. Handling Ambiguity and Unstructured Data
Rule-Based Software: Uses specified parsing, validation, search, and processing logic. It can work with structured fields and unstructured material, but interpreting unfamiliar or ambiguous inputs depends on the implemented methods. Transcripts, handwritten notes, and vague requests may require specialized processing, explicit rules, or AI components; unstructured input alone does not imply failure.
AI: Depending on the model and application, AI can assist processing of natural language, images, audio, and video, including summarization, translation, and interpretation of ambiguous requests. Supported inputs and performance vary. Review inferred intent, nuance, and source fidelity rather than treating a plausible interpretation as established meaning.
3. Adaptability and Learning
Rule-Based Software: Does not learn new behavior merely by being used. Its capabilities and outputs can change through code updates, configuration, revised rules, new data, or changed integrations. These changes require appropriate control and testing.
AI: Machine learning, retraining, and fine-tuning can change model behavior using new data or feedback. Ordinary use does not necessarily update a deployed model. Improvement is not automatic: changes require evaluation against the intended task and operating context.
4. Deterministic vs. Probabilistic Outcomes
Rule-Based Software: Deterministic calculations support repeatable results under unchanged inputs and relevant conditions. Repeatability does not establish correctness or make an entire application predictable. Logical defects, configuration problems, data errors, and integration failures still require systematic testing and correction.
AI: Outputs may vary or be incorrect, with behavior depending on the model, data, context, and configuration. Generative systems can produce plausible but unsupported content, often called hallucinations. Validate outputs and apply oversight proportionate to their intended use; statistical likelihood is not evidence of correctness.
Summary Analogy
Rule-based software is like a train operating on specified tracks: the route is defined in advance, but successful operation still depends on sound instructions, inputs, infrastructure, and conditions. The analogy illustrates an explicitly specified process, not a guarantee of error-free performance.
AI is like a navigator proposing a route through changing terrain: it weighs available information and suggests options, but its interpretation may be wrong. In a combined system, software supplies infrastructure and automation while AI can assist complex or unstructured tasks. People validate the evidence, review the proposed route, and authorize consequential actions.
Resources are grouped into enterprise support; real estate strategy and portfolio planning; portfolio analysis, facility planning, and programming; design and construction; and facility operations. General-purpose AI assistants and specialized computational applications support work across these groups. The categories describe complementary roles, not exclusive product classes or additional lifecycle stages. Platforms may appear in several groups.
Enterprise support systems maintain organizational records and workflows used in facility decisions. The Digital Ecosystem matrix groups them into finance, workforce and relationships, records and search, analytics, and IT service management. Establish permitted sources for organizational assumptions, costs, workforce demand, documents, and service dependencies. Reconcile definitions and approval status before translating records into facility requirements.
A system brief identifies accountable owners, record authority, permissions, identifiers, update practices, and interfaces. Separate analytical outputs from source records and preserve supporting evidence. An assistant summary or integrated dashboard does not become an approved requirement by combining enterprise information.
|
System / Category Name |
Core Purpose & Function |
Common Industry Examples |
|
ERP (Enterprise Resource Planning) |
Manages core business operations, supply chain, procurement, and enterprise resource tracking. |
SAP, Oracle Cloud ERP |
|
Finance & Accounting |
Handles general ledger, accounts payable/receivable, budgeting, forecasting, and compliance. |
Workday Financials, NetSuite |
|
HR / HCM (Human Capital Management) |
Manages employee records, payroll, benefits, talent acquisition, and workforce planning. |
Workday HCM, BambooHR |
|
CRM (Customer Relationship Management) |
Centralizes client/member relationship tracking, pipelines, and interaction histories. |
Salesforce, HubSpot |
|
Document Repositories / EDMS |
Securely creates, stores, versions, and archives organizational documents and content. |
SharePoint, OpenText, Box |
|
AI Search / Enterprise Search Engine |
Indexes structured/unstructured enterprise data to enable natural language information discovery. |
Azure AI Search, Glean |
|
BI & Business Analytics |
Aggregates enterprise data to build operational dashboards and executive reporting insights. |
Power BI, Tableau |
|
ITSM (IT Service Management) |
Tracks IT software licenses, hardware inventory, help-desk ticketing, and technical support. |
ServiceNow |
Real estate strategy and portfolio planning connect location and occupation choices with demand, property commitments, timing, and investment priorities. The Digital Ecosystem matrix identifies location and lease records, lease intelligence, portfolio and capital systems, and market data and advisers as complementary resources. Distinguish records from interpretations and scenarios from authorized commitments.
Compare retention, renewal, adaptation, relocation, consolidation, expansion, and exit where relevant. Record each option’s requirements, commercial assumptions, area definitions, costs, timing, and unresolved risks. Link the preferred option to its decision record and the detailed planning and programming that follows. The next section identifies supporting tools.
|
System / Service Category |
Core Purpose & Function |
Common Industry Examples |
|
GIS (Geographic Information Systems) |
Provides spatial data and location intelligence for site selection and macro planning. |
ArcGIS, Esri |
|
Lease Databases / RE Admin |
Tracks real estate contracts, critical lease dates, rent schedules, and financial compliance. Provides records for renewal, relocation, and exit comparisons. |
Lucernex, Visual Lease |
|
Portfolio Management / IWMS (Strategy) |
Delivers high-level oversight of real estate assets, occupancy costs, and long-term strategy. Supports renewal, relocation, and exit comparisons. spaciv provides portfolio decision support, with primary coverage in planning and programming. |
IBM TRIRIGA, Archibus; Trebellar; spaciv |
|
Capital Planning & Asset Strategy |
Forecasts multi-year capital expenditures (CapEx) and facility condition lifecycles. |
VFA, Brightly |
|
Lease Intelligence and Transactions |
Supports extraction and verification of clauses, amendment relationships, deadlines, and obligations for lease evidence and transaction review. |
LeaseOS; Prophia; LeaseSuite |
|
Market Data and Advisory |
Combines benchmarks, scenarios, and due diligence for market and risk interpretation. Distinguish advisory judgment from automated scoring and fund selection from facility site selection. |
MSCI Real Assets; CBRE; JLL; Cushman & Wakefield; Cresa; Macro and Mercer for investment-oriented services |
Portfolio analysis, facility planning, and programming systems connect organizational objectives with space demand, facility alternatives, and an approved requirements baseline. They support scenario comparisons, space allocations, room and equipment requirements, and checks between programmed needs and proposed designs. These systems complement real estate records, cost-estimating tools, and operational data. Their outputs depend on valid assumptions and consistent area definitions; they support, but do not replace, stakeholder agreement, professional judgment, and authorization. Platforms also listed in other tables are shown here for their planning and programming roles.
|
System / Service Category |
Core Purpose & Function |
Common Industry Examples |
|
Portfolio Analysis and Scenario Planning |
Compares current and forecast space supply, organizational demand, costs, and alternative portfolio strategies. Supports consolidation, expansion, relocation, and timing scenarios; validate source data and forecast assumptions. |
Trebellar Portfolio Planner; Archibus Space Planning / Advanced Forecasting; Spaciv—portfolio scenario analysis; Planon Portfolio Strategies / Strategic Space Planning; FM:Systems Strategic Scenario Planning |
|
Facility and Campus Space Planning |
Translates demand into building, floor, and departmental allocations; develops stack plans and identifies gaps between available space and projected requirements. Connects portfolio-scale scenarios with more detailed space plans. |
Archibus Space Planning; Planon Strategic Space Planning / Spaces and Moves Scenario Planning; FM:Systems Strategic Scenario Planning; ServiceNow Workplace Space Management—floor, department, and building scenarios; Wisp by Apex42—departmental blocking and seating scenarios |
|
Architectural Programming and Requirements Management |
Maintains functional requirements, room counts, area targets, equipment requirements, and planning standards. Compares programmed requirements with designed provision to support the Program of Requirements and subsequent review. |
dRofus |
|
Program-Based Test Fits and Adjacency Planning |
Tests required spaces and departmental relationships within candidate layouts, tracking areas and counts against the program. Supports option exploration and exchange of programmed and designed areas; review adjacencies and constraints rather than assuming automatic resolution. |
Hypar, including its dRofus integration |
|
Room Standards, Equipment Planning, and Design Validation |
Maintains reusable room templates and equipment requirements, links records to project models, and checks design development against the requirements baseline. Data validation supports professional review but does not establish comprehensive regulatory compliance. |
dRofus, with Revit, Archicad, IFC, and Hypar integrations |
|
Facility Condition and Capital Renewal Planning |
Uses condition and maintenance evidence to compare repair, replacement, deferral, and investment scenarios. Complements space planning; asset condition is not a substitute for assessment of functional suitability. |
Origin—Siemens Asset Management Software |
|
User Needs, Space Demand, and Gap Analysis |
Combines structured user input, organizational assumptions, and existing-space data to model demand, compare current provision with required space, and test workplace alternatives. Supports programming and requirements discussions; does not itself establish approval of the requirements baseline or replace detailed room and equipment requirements management. |
spaciv—decision-intelligence platform and associated services; Gensler Sandbox—experience-driven workplace programming and scenario tool used by Gensler design teams; confirm engagement and access arrangements |
Design and construction systems support the owner and project team in coordinating scope, budgets, documents, quality, and handover. They connect approved requirements with design reviews, procurement, construction records, and commissioning evidence. Consistent document control and issue tracking help preserve the basis for decisions and the information needed by future operators; the systems support, rather than replace, professional review and authorization.
|
System / Service Category |
Core Purpose & Function |
Common Industry Examples |
|
PMIS / Capital Project Software |
Centralizes project budgets, change orders, RFIs, submittals, and pay applications. |
Procore, e-Builder, Autodesk Construction Cloud |
|
BIM Viewer & Coordination Tools |
Enables collaborative 3D model review, clash detection, and constructibility checks. |
Autodesk Navisworks, BIM 360 |
|
Owner Accounting / Cost Management |
Tracks project-specific capital ledgers, cash flow forecasts, and invoice approvals. |
Oracle Unifier, Sage 300 CRE |
|
Document & Drawing Control |
Manages architectural drawings, specifications, contracts, and as-built records. |
SharePoint, ProjectWise, Box |
|
Punch List & Quality Control |
Field-management apps tracking construction deficiencies and contractor sign-offs. |
PlanGrid, Fieldwire |
|
Commissioning (Cx) Tracking |
Manages digital testing logs to verify mechanical/electrical systems meet requirements. |
Custom Cx databases, CxAlloy |
|
Construction Cost Databases and Conceptual Estimating |
Provides unit rates, assemblies, and building-cost benchmarks for early budgets and progressively detailed estimates. Adjust data for location, pricing date, building type, and project scope. |
Gordian RSMeans Data Online—U.S. and Canada; BCIS CapX—UK capital-cost planning |
|
Site Development and Civil Quantity Takeoff |
Measures earthwork, grading, paving, and utility quantities from project drawings and models. Quantities feed estimates using appropriate local rates and project assumptions; takeoff software is not itself a localized cost database. |
AGTEK Gradework, Materials, and Underground |
|
Building and Fit-Out Takeoff and Cost Planning |
Connects quantities from drawings and BIM models with rates, assemblies, estimates, and reports. Supports design-option comparisons, alternates, and estimate revisions; validate quantities, rate sources, and scope coverage. |
RIB CostX; Beck Technology DESTINI Estimator |
|
Historical Project Cost Libraries and Benchmarking |
Organizes comparable project costs to inform early estimates and validate assumptions. Normalize records for scope, date, location, area definitions, and cost classifications. A platform’s cost-history function does not necessarily include an external price database. |
Organization-controlled cost libraries; DESTINI Estimator centralized cost history; RIB CostX rate libraries |
|
Tenant Fit-Out Market Benchmarks |
Provides market-level comparisons by location, specification, and workplace type for preliminary budgets and relocation scenarios. Research guides are benchmark resources, not estimating applications or project-specific estimates; reconcile their inclusions before comparison. |
JLL Office Fit-Out Costs Guides; Cushman & Wakefield Office Fit Out Cost Guides; Turner & Townsend Global Office Fit-Out Cost Guide |
Cost-estimating basis: Record the scope, location, pricing date, area-measurement basis, inclusions, exclusions, and uncertainty of each estimate. Distinguish site development, base-building construction, and tenant fit-out from total project costs, including applicable fees, technology, furniture, escalation, contingency, and relocation costs. Reconcile allowances to avoid omissions or double counting. Published benchmarks support—but do not replace—project-specific estimating and review.
Facility operations systems support maintenance, building controls, space use, energy performance, and occupant services. Analytics and diagnostic tools complement operational systems by identifying patterns, forecasting demand, and prioritizing issues for review. Operational evidence feeds back into strategic predesign, informing future requirements, portfolio choices, and capital plans. Forecasts and diagnostic findings require validation and accountable follow-through before changes are implemented.
|
System / Service Category |
Core Purpose & Function |
Common Industry Examples |
|
CMMS / CAFM |
Manages preventive maintenance schedules, work order ticketing, and equipment lifecycles. |
Maximo, ServiceChannel, FMX |
|
IWMS (Operations Module) |
Integrates facility maintenance, space allocation, and lease management into a single platform. |
IBM TRIRIGA, Archibus, Accruent |
|
BMS / BAS (Building Automation) |
Controls and monitors mechanical, HVAC, temperature, and lighting infrastructure in real time. |
Johnson Controls Metasys, Schneider Electric |
|
Space Utilization, Occupancy Intelligence, and Predictive Planning |
Measures space use through supported sensor, badge, or other occupancy inputs to inform right-sizing. Predictive planning tools add demand forecasts and scenarios for lease exits, redesigns, headcount changes, and space allocation. Capabilities vary by product; review input coverage, benchmark relevance, and forecast uncertainty. |
FM:Systems; SpaceIQ / Eptura; VergeSense Meridian—occupancy intelligence and predictive planning |
|
Energy Management & ESG Reporting |
Tracks utility bills, carbon emissions, and sustainability metrics for compliance. |
EnergyCAP, Schneider Electric Resource Advisor |
|
Tenant / Occupant Experience Portals |
Provides service request interfaces and room-booking apps for building occupants. |
HqO, TenantCloud |
|
Building Analytics and Fault Detection and Diagnostics (FDD) |
Analyzes connected building-management and metering data to diagnose performance issues and prioritize corrective work by energy, indoor-environment, and equipment-reliability impacts. Complements BMS/BAS controls and CMMS maintenance workflows; diagnostic findings require technical review and corrective action. |
Clockworks Analytics |
Representative general-purpose assistants include ChatGPT, Gemini, Claude, and Microsoft 365 Copilot. They offer overlapping document, research, and workspace capabilities. Perplexity provides source-oriented research and enterprise search; Mistral offers customization and deployment options; and a Llama-based private assistant is an implementation approach rather than a ready-made subscription. Select tools through task-specific evaluation, not a fixed ranking. Verify current licensing, data treatment, permissions, supported inputs, and output reliability before using proprietary project material. The following examples are not an exhaustive list or a recommendation to adopt every platform.
|
Application / Platform |
Capabilities & Predesign Fit |
Evaluation Considerations |
|
ChatGPT Plus / Business / Enterprise |
Document context: Large context limits support standard documents and uploaded PDFs. Workspace integration: File imports/exports and integrations connect project information to the assistant. Custom knowledge: Custom GPTs and Projects support dedicated predesign assistants using proprietary programming standards and firm templates. Multimodal inputs: Supports analysis of site photos, napkin sketches, diagram screenshots, and handwritten program notes. |
Verify context and file limits, available integrations, and the current subscription offering. Test whether uploaded standards are retrieved accurately and whether image interpretation preserves dimensions, annotations, and uncertainty. Do not treat inferred geometry or generated requirements as verified project data. |
|
Gemini Gemini app / Google Workspace |
Document context: Large-context workflows can support municipal zoning codes, 100+ page master plans, and transcript sets, subject to model and application limits. Workspace integration: Google Docs, Sheets, and Drive support work with project briefs, space-program spreadsheets, and existing team files. Custom knowledge: Custom instructions, Gems, and reusable skills can support specialized workflows such as regulatory research and survey analysis. Availability and the transition from Gems to skills vary by account and rollout. Multimodal inputs: Supports workflows involving infographics, site plans, and stakeholder interview recordings, subject to supported input types. |
Confirm the selected model’s context capacity and the application’s upload and recording limits; 1M+ tokens is not a universal product guarantee. Test workspace permissions and output fidelity. Evaluate multimodal performance on project material rather than assuming superiority or code-compliance capability. |
|
Application / Platform |
Capabilities & Predesign Fit |
Evaluation Considerations |
|
Claude — Anthropic |
Candidate for interview synthesis, brief comparison, requirements organization, and vision narratives. Projects provide document-based knowledge spaces; Research and integrations connect web and organizational sources. |
Test preservation of conflicting stakeholder needs, qualifications, and source references. Context limits, file handling, and integrations depend on the selected model and plan. |
|
Microsoft 365 Copilot |
Relevant when project data lives in Word, Excel, Teams, Outlook, and SharePoint. Supports drafting, spreadsheet work, meeting recaps, and work-grounded retrieval in licensed experiences. |
An application/integration platform, not one foundation model. Check licensing, enabled connectors, and user permissions; work-data grounding varies by experience. |
|
Perplexity |
Research companion for precedents, building-type benchmarks, and contextual research. Enterprise search combines web and internal files with citations; project knowledge can focus research on a specific brief. |
A research platform using multiple models. Inspect primary sources and benchmark applicability; citations alone do not validate zoning or code interpretations. |
|
Mistral Vibe (formerly Le Chat) |
Alternative for document synthesis, research, and customized workflows. Document libraries, enterprise connectors, custom agents, and private deployment options support firm-specific knowledge use. |
Distinguish the hosted assistant, custom enterprise deployment, and separate document-processing services. Verify current product naming, model capabilities, data residency, and deployment effort. |
|
Meta Llama-based Private Assistant |
Open-weight model family for a firm-controlled knowledge assistant using proprietary programming standards, past projects, and templates. Private hosting and custom retrieval are implementation choices; multimodal capabilities vary by model. |
An implementation project, not a ready-made subscription. Budget for retrieval, infrastructure, access controls, evaluation, maintenance, and license review. |
Special-purpose applications use explicit spatial parameters, program targets, and design constraints to support feasibility and option development. TestFit addresses site feasibility; Hypar supports program-driven space planning; Finch explores floor-plan alternatives; and Snaptrude connects programming with massing and BIM development. These platforms combine computational methods and AI features in different ways. Their outputs depend on supplied assumptions, supported project types, and available features. Reconcile results with the approved program and applicable requirements; generated layouts and encoded checks do not establish comprehensive regulatory compliance.
|
Application / Platform |
Capabilities & Predesign Fit |
Evaluation Considerations |
|
TestFit |
Site feasibility and rapid development-option testing. Generates and compares site layouts using parameters such as unit mix, density, setbacks, and parking; provides area and quantity metrics. Supports downstream Revit, CAD, and spreadsheet workflows. |
Best evaluated for site-scale feasibility and supported building typologies rather than interview synthesis. Validate zoning inputs, terrain assumptions, quantities, and export fidelity. Generated options do not establish regulatory approval. |
|
Hypar |
Program-driven space planning and test fits. Imports spreadsheet or dRofus requirements, tracks placed spaces against target areas and counts, and supports collaborative 3D layout exploration. AI furniture and equipment suggestions assist planning; models can transfer to Revit or Rhino. |
A space-planning platform with AI features, not a general-purpose LLM. Test requirement mapping, departmental grouping, area conventions, equipment counts, and model handoff. Do not assume all layouts or adjacencies are automatically resolved. |
|
Finch / Finch 3D |
AI-assisted floor-plan generation and design-option exploration. Uses a firm's plan library, design standards, and encoded constraints to generate and refine layouts, with live area metrics and BIM geometry. Connects with Rhino, Grasshopper, Revit, and other design workflows. |
Evaluate fit for the project typology and quality of the supplied plan library. Review circulation, accessibility, structural coordination, and applicable local rules independently; encoded checks are not a comprehensive compliance guarantee. |
|
Snaptrude |
AI-assisted programming, site analysis, massing, departmental stacking, layouts, and BIM development in an editable collaborative environment. Accepts briefs and drawings; supports program tables, diagrams, and Revit interoperability. |
Review generated space requirements, dimensions, zoning sources, and stated assumptions before adopting results. Test Revit transfer with firm families and metadata. AI credits and access to BIM capabilities vary by plan. |
The digital ecosystem connects five complementary resource groups: enterprise support; real estate strategy and portfolio planning; portfolio analysis, facility planning, and programming; design and construction; and facility operations. Two cross-cutting application groups support this work: general-purpose AI assistants and platforms, and special-purpose AI and computational applications. These are enabling resources, not additional lifecycle stages.
The matrix brings together the lifecycle systems and the application groups described in the preceding tables. Software maintains records and workflows; external data and advisers supply evidence and interpretation; general-purpose assistants support research, synthesis, and drafting; and specialized applications support feasibility, programming, and design-option exploration. Capabilities depend on the application, available data, and integration. Not every analytical or computational technique uses AI, and an assistant does not replace a system of record or an approved requirements baseline.
Digital models support scenario testing and information exchange. A digital twin adds a defined connection to a real-world entity or process, with specified synchronization and fidelity. A static BIM model, requirements database, dashboard, simulation, or AI-generated layout is not automatically a twin. Natural language processing (NLP), large language models (LLMs), the Internet of Things (IoT), and critical path method (CPM) scheduling are distinct technologies or methods. All outputs require appropriate validation, access controls, and human authorization.
|
Lifecycle Stage / Focus Area |
Core Systems, Data & Services |
Analysis & AI-Assisted Capabilities |
Digital Models & Twin Applications |
|
1. Enterprise Support Systems |
• ERP and Finance: SAP, Oracle Cloud ERP, Workday Financials, NetSuite • Workforce and Relationships: Workday HCM, BambooHR, Salesforce, HubSpot • Records, Search, and Analytics: SharePoint, OpenText, Box, Azure AI Search, Glean, Power BI, Tableau • IT Service Management: ServiceNow |
• Knowledge Retrieval: Search controlled organizational records with source references. • Drafting and Synthesis: Assist report preparation, meeting summaries, and stakeholder communication. • Workflow Support: Route tasks and document review status within permissions; AI summaries do not constitute decision approval. |
• Enterprise Data Models and Process Twins: Corporate data models link financial, HR, and asset metrics across operations. They qualify as twins only where a defined real-world entity or process is represented and synchronized for a stated use. |
|
2. Real Estate: Strategy & Portfolio Planning |
• Location and Lease Records: ArcGIS/Esri, Lucernex, Visual Lease • Lease Intelligence and Transactions: LeaseOS, Prophia, LeaseSuite • Portfolio and Capital Systems: IBM TRIRIGA, Archibus, Trebellar, VFA, Brightly; spaciv—portfolio decision support, with primary coverage in planning and programming • Market Data and Advisory: MSCI Real Assets; CBRE, JLL, Cushman & Wakefield, Cresa; Macro and Mercer for investment-oriented services |
• Lease Evidence: Extract and verify clauses, amendment relationships, deadlines, and obligations. • Property and Portfolio Comparisons: Assess locations, occupancy costs, renewal, relocation, and exit options. • Market and Risk Interpretation: Combine benchmarks, scenarios, and due diligence. Distinguish advisory judgment from automated scoring and fund selection from facility site selection. |
• Portfolio Models and Digital Twins: Multi-site spatial and financial models support portfolio scenarios. A portfolio twin integrates relevant property data with defined synchronization and fidelity; aggregation alone does not create a twin. |
|
3. Portfolio Analysis, Facility Planning, and Programming |
• Demand and Scenarios: Trebellar Portfolio Planner; Archibus Space Planning / Advanced Forecasting; spaciv; Planon; FM:Systems Strategic Scenario Planning; ServiceNow Workplace Space Management; Wisp by Apex42 for blocking and seating scenarios; Gensler Sandbox for experience-driven workplace programming • Programming and Standards: dRofus • Program-Based Test Fits: Hypar, including its dRofus integration • Capital Renewal: Origin |
• Requirements Synthesis: Assist analysis of interviews, surveys, and standards while preserving sources and conflicting needs. • Planning: Compare supply and demand, allocations, adjacencies, areas, and equipment requirements. • Validation: Reconcile programmed and designed provision and evaluate renewal alternatives. Forecasting, test fits, and checks may use explicit rules rather than AI. |
• Requirements and Scenario Models: Link approved needs to rooms, equipment, space alternatives, and condition evidence. • Potential Campus or Space Twins: Connect representations to relevant real-world data with defined synchronization. A program database or test-fit model alone is not a twin. |
|
4. Design and Construction: Owner and Project Management |
• Delivery and Cost Control: Procore, e-Builder, Autodesk Construction Cloud, Oracle Unifier, Sage 300 CRE • Cost Evidence and Estimating: RSMeans Data Online, BCIS CapX, AGTEK, RIB CostX, DESTINI Estimator, historical cost libraries • Fit-Out Benchmarks: JLL, Cushman & Wakefield, Turner & Townsend guides • Models, Records, and Quality: Navisworks, Revit, BIM 360, SharePoint, ProjectWise, Box, PlanGrid, Fieldwire, CxAlloy |
• Estimate Development: Calculate quantities, apply rates and assemblies, and compare alternatives. Separate site, building, and fit-out costs from total project budgets; most takeoff and estimating functions do not inherently require AI. • Delivery Analysis: Track budget and scope changes, coordinate models, and analyze schedules using CPM and other methods. • AI Assistance: Support document comparison, issue summaries, and candidate risk identification, subject to verification. |
• Campus and Building Twins: BIM handover data, asset tags, and O&M manuals can provide a foundation for a building twin, for example in Autodesk Tandem. Relevant operational data and defined synchronization distinguish the twin from a static handover model. |
|
5. Facility Operations: Owner and Facility Management |
• Maintenance and IWMS: Maximo, ServiceChannel, FMX, IBM TRIRIGA, Archibus, Accruent • Controls and Diagnostics: Johnson Controls Metasys, Schneider Electric, Clockworks Analytics • Occupancy and Planning: FM:Systems, SpaceIQ / Eptura, VergeSense Meridian • Energy, ESG, and Occupant Services: EnergyCAP, Schneider Electric Resource Advisor, Measurabl, HqO, TenantCloud |
• Diagnostics and Maintenance: Analyze equipment performance and prioritize issues; failure prediction and automated work orders depend on configured capabilities. • Occupancy Analysis: Assess utilization and forecast space demand with explicit uncertainty. • Energy and Service Analysis: Review energy use, carbon metrics, and occupant requests. Recommendations do not authorize direct changes to building controls. |
• Occupancy Models or Twins: Use relevant badge or sensor evidence to represent space use. A twin requires a defined real-world representation and synchronization; a utilization dashboard alone is not a twin. • Energy and Sustainability Models or Twins: Thermodynamic models support energy and carbon scenarios. A twin links the model to relevant measured data with defined synchronization and calibration; simulation alone does not establish a twin or guarantee optimized performance. |
|
6. General-Purpose AI Assistants and Platforms (Cross-Cutting) |
• Assistants and Workspace Platforms: ChatGPT, Gemini, Claude, Microsoft 365 Copilot • Research and Custom Deployment: Perplexity, Mistral, Meta Llama-based private assistants • Selection: Refer to the general-purpose application tables for task fit, licensing, integration, and evaluation considerations. |
• Research and Synthesis: Assist precedent research, interview analysis, brief comparison, and requirements organization. • Documentation: Support drafting, meeting recaps, spreadsheet work, and retrieval from permitted project sources. • Review: Validate sources, calculations, qualifications, and image interpretations. Availability varies by model, plan, and permissions; citations do not establish correctness. |
• Knowledge and Interpretation: Assist explanation of project records and model outputs where supported. • Boundary: An assistant or project knowledge space is not itself a digital twin, a verified geometry model, or a system of record. |
|
7. Special-Purpose AI and Computational Applications (Cross-Cutting) |
• Site Feasibility: TestFit • Program-Based Space Planning: Hypar, including its dRofus workflow • Design Alternatives and BIM Development: Finch / Finch 3D, Snaptrude • Selection: Refer to the special-purpose application table for supported workflows and evaluation considerations. |
• Option Exploration: Test site layouts, program-based test fits, floor plans, massing, stacking, and design alternatives within supported scopes. • Metrics and Handoff: Compare areas and quantities, reconcile layouts with requirements, and transfer models to supported design tools. • Review: Verify dimensions, area conventions, zoning inputs, adjacencies, and export fidelity. AI features and explicit computational rules differ by product; generated options do not establish regulatory approval. |
• Planning and Design Models: Produce editable layouts, feasibility scenarios, and BIM geometry for evaluation and downstream development. • Boundary: These models are not automatically digital twins; a twin requires defined synchronization with relevant real-world entities or processes. |
Workplace experience technology (WXT) connects employees with the spaces, tools, and services they need to work effectively. Combined with activity-based workplace design and reliable operational data, it can help organizations understand how their environments function and where improvements are needed.
This approach brings together four complementary concepts:
Together, these concepts support decisions at three scales: interior workplaces, individual buildings or commercial real estate assets, and multi-building sites or campuses
Workplace experience technology refers to the software, hardware, and integrations that support employees’ interactions with physical workplaces and digital services. Its purpose is to reduce friction between people, spaces, and technology in on-site, hybrid, and remote work.
Related terms overlap but should not be treated as exact synonyms. A workplace experience platform (WXP) generally brings selected workplace services together through a common interface. Digital workplace experience (DWX) describes employees’ experience of their digital work environment. WXT can connect several domains, although no single platform necessarily provides all of them.
1. Interior Workplace Scale
WXT provides physical space and hybrid workplace management capabilities:
It accommodates digital employee experience and service access:
And supports communication and feedback:
WXT can make workplace services easier to access, support coordination across hybrid teams, and provide evidence for space and service planning. Better tools may also contribute to employee satisfaction, but improvements in engagement or retention should be measured rather than assumed. Technology is most effective when supported by clear workplace policies, dependable services, and responsive operational teams.
Work Points and Activity-Based Working
For physical workplace planning, a work point is a designated position equipped to support a work activity. It may be an assigned workstation, a shared desk, a position in a collaborative setting, or another suitable place to work.
Activity-based working (ABW) provides a range of settings for different activities rather than relying exclusively on one standard desk type. Shared desks are one possible component of ABW, but desk sharing alone does not create an activity-based workplace.
For capacity planning, distinguish individual work points from rooms and larger settings. A project room, for example, is a work setting that may contain several work points.
There are several types of work points and settings:
Work points may be assigned, shared, reservable, or available on a first-come basis. The appropriate policy depends on work patterns, equipment needs, accessibility requirements, confidentiality, and demand. Booking systems can help employees find suitable spaces, but policies should also address cancellations, unused reservations, peak demand, and access to specialized settings. Effective work points require more than connectivity. Depending on the activity, they may need:
A well-designed mix of work points can improve choice and make better use of space. It does not automatically reduce the amount of space required. Planning should consider peak attendance, simultaneous demand for different settings, and the suitability of available spaces—not average attendance alone. The key question is whether employees can reliably find an appropriate place to perform their work.
Insights APIs and the Data-to-Decision Process
An application programming interface (API) enables software systems to exchange data or request services. An insights API exposes metrics, analytical results, or other information produced by a platform. The term does not describe a universal technical standard. Available data, analytical methods, update frequency, and access controls depend on the provider and implementation. An API does not necessarily collect data, perform analytics, or generate predictions itself. Those functions usually belong to the systems behind the interface.
How the process works:
Insights APIs can support:
Reliable integration requires agreed metric definitions, timestamps, access permissions, update intervals, and procedures for handling missing or incomplete data. Continuous access to data does not necessarily mean that the underlying information is real-time.
2. Buildings Scale
At the building scale, the framework compares three aspects of workplace performance: what was intended, what is observed, and where demand or behavior strains the environment. It is best presented as a diagnostic framework unless its variables, units, and mathematical relationships are explicitly defined.
Planned use describes the intended activities, capacities, and operating assumptions established through architectural programming and workplace planning. It includes:
Planned use is a baseline for testing, not proof that the environment will perform as intended.
Actual use describes observed occupancy, activities, and resource use over a defined period. Evidence may include occupancy sensors, reservations, access-control records, observations, service requests, and employee feedback.
Each source has limitations:
Using several evidence sources can improve interpretation. Measures should distinguish attendance, occupancy, utilization, and demand, and should state their denominators and observation periods.
In this framework, overreach means demand or behavior that exceeds a space’s intended capacity or operating arrangements, creating strain, workarounds, or unmet needs. Examples include:
Underutilization is a different mismatch: it may indicate excess capacity, poor suitability, limited access, or demand at other times. Buffer capacity is not overreach. It is deliberately provided flexibility or spare capacity intended to accommodate variability and reduce strain.
Compare planned and actual use, identify recurring mismatches, and investigate their causes before changing the environment. Responses may include revised booking policies, service improvements, equipment upgrades, or changes to the mix of settings. Low utilization does not automatically mean a space should be removed. It may serve a specialized function, provide peak-period capacity, or be underused because it is difficult to access or poorly equipped.
Commercial Real Estate: Asset and Portfolio Decisions
For developers, landlords, and investors, the same concepts can inform asset management, tenant services, and investment analysis. Operational data supplements financial and market evidence; it does not replace them.
Planned use includes the asset’s intended function, tenant profile, capacity, and operating assumptions. Financial underwriting adds assumptions about rents, vacancies, expenses, capital expenditure, and market conditions.
Actual use provides evidence about how tenants and visitors use the property. Leased occupancy and physical occupancy are different measures: one describes contractual use of rentable area, while the other describes people that are present within a defined capacity and period.
Low physical occupancy may warrant investigation, but it does not by itself establish that leased space is unnecessary or that rental income is at risk.
Overreach may appear as elevator congestion, parking shortages, inadequate shared facilities, or infrastructure that does not meet tenant needs. These observations can guide technical investigations and capital planning, but costs and financial impacts require separate assessment.
Flexible work settings and shared amenities
Shared conference facilities, lounges, and suitably equipped outdoor areas can expand the range of settings available to tenants. They may support more flexible leasing arrangements, provided access, capacity, operating costs, and lease terms are clearly defined.
Repositioning an asset around these features may strengthen its market appeal. Rental premiums and investment returns depend on local demand, competition, implementation costs, and demonstrated tenant value.
The term shared amenity spaces is clearer here than “core-plus amenity spaces,” which can be confused with the core-plus real estate investment strategy.
Tenant experience technology
Tenant-facing platforms can integrate visitor registration, service requests, amenity reservations, parking access, and building information. Functions depend on available integrations and permissions.
These services may reduce administrative friction and support tenant satisfaction. Their effect on renewals should be evaluated alongside rent, location, building quality, lease terms, and service performance.
Insights APIs and portfolio analysis
APIs can make operational information available to asset and portfolio management systems. Potential applications include:
Valuation analysis should continue to consider income, expenses, lease obligations, market evidence, capital requirements, and risk. Telemetry is supporting evidence, not a standalone valuation method.
3. Sites and Campuses
At the site or campus scale, the focus expands from individual rooms to the relationships among buildings, outdoor areas, transport systems, and shared services.
Planned use includes building functions, capacities, circulation routes, accessible connections, parking, shared amenities, and movement between destinations.
Actual use can be assessed through appropriately governed building occupancy data, pedestrian counts, parking information, reservations, observations, and feedback. Understanding travel times or movement patterns requires data suitable for those questions; aggregate counts alone may not be sufficient.
Overreach may appear as recurring parking overflow, congested routes, overloaded shared facilities, or employees traveling between buildings because suitable settings are unavailable nearby. Campus-wide totals can conceal local shortages. A site may have spare capacity overall while buildings or settings are consistently oversubscribed.
Campuses can provide complementary settings across the site:
Outdoor suitability depends on weather, shade, acoustics, power, connectivity, accessibility, and maintenance. Not every seat or gathering place should be counted as a work point.
WXT can support cross-building wayfinding, resource booking, service access, and operational information. Accessible routes and information about outages or closures depend on reliable maps and maintained data feeds. Occupancy information may also inform building automation. Changes to heating, ventilation, air conditioning, and lighting require appropriate controls, commissioning, and safeguards for comfort, indoor air quality, and applicable requirements.
Insights-APIs and master planning
Integrated data can support comparisons among buildings, identify persistent demand imbalances, and inform maintenance, adaptation, and future development. Predictive models should be validated against observed outcomes. Automated alerts can identify conditions for investigation but should not be treated as conclusive evidence that space requires reconfiguration.
Conditions for Responsible Implementation
Across all three scales, effective implementation requires:
The objective is not simply to maximize occupancy or reduce square footage. It is to provide suitable, reliable environments while using resources responsibly. Workplace experience technology connects people to services and spaces. Work points provide settings suited to different activities. Insights APIs make operational information available for analysis. The planned-use, actual-use, and overreach framework helps identify where design intent and operational needs diverge. Their value comes from using them together: establish clear assumptions, gather reliable evidence, investigate mismatches, make proportionate changes, and evaluate the results. Applied carefully, this approach can support better workplace experiences and more informed building, asset, and campus decisions.
Prepared by Steven Parshall, with the use of AI agents. © Copyright of the Strategic Predesign Association
Feedback on this section
Click on POST to share your thoughts, ideas, comments, and constructive critiques about this section. Tell us what is unclear, what could be improved, and what additional topics we should address.
Go to Explore the Practice |