Nothing Special   »   [go: up one dir, main page]

WO2019060225A1 - Système de gestion de bâtiments unifiée à profils de cas d'utilisation d'espace - Google Patents

Système de gestion de bâtiments unifiée à profils de cas d'utilisation d'espace Download PDF

Info

Publication number
WO2019060225A1
WO2019060225A1 PCT/US2018/051182 US2018051182W WO2019060225A1 WO 2019060225 A1 WO2019060225 A1 WO 2019060225A1 US 2018051182 W US2018051182 W US 2018051182W WO 2019060225 A1 WO2019060225 A1 WO 2019060225A1
Authority
WO
WIPO (PCT)
Prior art keywords
profile
job
space
use case
profiles
Prior art date
Application number
PCT/US2018/051182
Other languages
English (en)
Inventor
Sheri L. Meyer
Beth A. Ray
Radu M. Dorneanu
Rachel D.M. Ellerman
Original Assignee
Johnson Controls Technology Company
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/952,173 external-priority patent/US10156833B2/en
Application filed by Johnson Controls Technology Company filed Critical Johnson Controls Technology Company
Priority to EP18789285.6A priority Critical patent/EP3685326A1/fr
Publication of WO2019060225A1 publication Critical patent/WO2019060225A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/16—Real estate
    • G06Q50/163—Real estate management

Definitions

  • Buildings are used and experienced by people seeking to accomplish tasks and otherwise achieve goals in or around the buildings. Buildings, building systems, and the equipment and devices that affect environmental conditions of the buildings may
  • the building management system includes a plurality of devices of building equipment that operate across multiple building equipment domains. Each of the plurality of devices serve one or more of the spaces.
  • the building management system also includes a controller configured to associate the space with a first group of the plurality of devices of building equipment. The first group includes multiple devices that serve the space and that operate across the multiple building equipment domains.
  • the controller is also configured to select a space profile from a plurality of selectable space profiles. At least two of the space profiles are associated with a different type of space serving a different function.
  • the space profile includes a plurality of job profiles.
  • At least two of the job profiles are associated with a different job to be accomplished at the space.
  • Each job profile includes a first space use case profile that identifies how to accomplish at least a part of the job associated with the job profile.
  • the controller is also configured to select the first space use case profile and, in response to selecting the first space use case profile, control the first group of devices in accordance with the first space use case profile to execute a first space use case that accomplishes at least the part of the job associated with the job profile.
  • the job profile includes a first job step profile associated with a first job step of the job.
  • the first job step profile includes the first space use case profile.
  • the job profile also includes a second job step profile associated with a second job step of the job.
  • the second job step profile includes a second space use case profile.
  • the controller is configured to select the first job step profile and, in response to selecting the first space use case profile, control the first group of devices in accordance with the first space use case profile to accomplish the first job step, select the second job step profile, and in response to selecting the second job step profile, control the at least some of the first group of devices in accordance with the second space use case profile to accomplish the second job step.
  • the controller is configured to detect a first occurrence of a first trigger associated with the first job profile, detect a second occurrence of a second trigger associated with the second job profile, determine whether the first space use case profile has a higher priority than the second space use case profile, and, in response to a determination that the first space use case profile has a higher priority than the second space use case profile, control the at least some of the first group of devices in accordance with the first space use case profile.
  • accomplishing the job comprises accomplishing the first job step and accomplishing the second job step.
  • the controller is configured to control the at least some of the first group of devices in accordance with the first space use case profile by applying a mode associated with the first space use case profile.
  • the controller is configured to control the first group of devices in accordance with the first space use case profile by prompting a user to create a user-created mode and applying the user-created mode to the first group of devices. In some embodiments, the controller is configured to automatically generate the user-created mode in response to a user selection of an option to create the user-created mode.
  • the controller is further configured to instruct to a user to manually accomplish another part of the job associated with the job profile in accordance with the first space use case profile.
  • the space controller is configured to receive the plurality of selectable job profiles for the space from a profiles repository.
  • the profiles repository is configured to store available job profiles applicable to a variety of spaces and places.
  • the available job profiles include the plurality of selectable job profiles.
  • Another implementation of the present disclosure is a method for managing one or more places that include one or more spaces.
  • the method includes operating a plurality of devices of building equipment across multiple building equipment domains. Each of the plurality of devices serve one or more of the spaces.
  • the method also includes associating, for each space, the space with a first group of the plurality of devices of building equipment. The first group includes multiple devices that serve the space and that operate across the multiple building equipment domains.
  • the method also includes selecting a space profile from a plurality of selectable space profiles. At least two of the space profiles are associated with a different type of space serving a different function.
  • the space profile includes a plurality of job profiles. At least two of the job profiles are associated with a different job to be accomplished at the space.
  • Each job profile includes a first space use case profile that identifies how to accomplish at least a part of the job associated with the job profile.
  • the method also includes selecting the first space use case profile and in response to selecting the first space use case profile, controlling the at least some of first group of devices in accordance with the first space use case profile to execute a first space use case that accomplishes at least the part of the job associated with the job profile.
  • the job profile includes a first job step profile associated with a first job step of the job and a second job step profile associated with a second job step of the job.
  • the first job step profile includes the first space use case profile and the second job step profile includes a second space use case profile.
  • the method includes selecting the job step profile, in response to selecting the first job step profile, controlling the at least some of the first group of devices in accordance with the first space use case profile to accomplish the first job step, selecting the second job step profile, and, in response to selecting the second job step profile, controlling the at least some of the first group of devices in accordance with the second space use case profile to accomplish the second job step.
  • accomplishing the job includes accomplishing the first job step and accomplishing the second job step.
  • controlling the at least some of the first group of devices in accordance with the first space use case profile includes applying a mode associated with the first space use case profile.
  • the method includes automatically generating the user-created mode in response to a user selection of an option to create the user-created mode.
  • the method includes instructing a user to manually accomplish another part of the job associated with the job profile in accordance with the first space use case profile.
  • controlling the at least some of the first group of devices in accordance with the first space use case profile includes prompting a user to create a user- created mode and applying the user-created mode to the at least some of the first group of devices.
  • the method also includes detecting a second occurrence of a second trigger associated with a second space use case profile, determining whether the space use case profile has a higher priority than the second space use case profile, and in response to a determination that the first space use case has a higher priority than the second space use case, selecting the first space use case profile and preventing selection of the second space use case profile.
  • the method includes storing available job profiles applicable to a variety of spaces and places in a profiles repository.
  • the available job profiles include the plurality of selectable job profiles for the space.
  • the method also includes associating the space with the plurality of selectable job profiles.
  • Another implementation of the present disclosure is a method for configuring a controller.
  • the method includes providing a design tool that allows a user to define a job, a job step, and a space use case, generating, based on user input to the design tool, a job profile relating to the job, a job step profile relating to the job step, and a space use case profile relating to the space use case, associating the job profile with the job step profile, associating the job step profile with the space use case, and storing the job profile, the job step profile, and the space use case profile in a space profile in a profiles repository.
  • the profiles repository stores a plurality of selectable space profiles. At least two of the selectable space profiles correspond to a different type of space.
  • the method also includes receiving an assignment of the space profile to a particular space, and, in response to receiving the assignment of the space profile to the particular space, installing the job profile, the job step profile, and the space use case profile on a controller configured to control a plurality of devices of building equipment that serve the space.
  • the controller uses the job profile, the job step profile, and the space use case profile to facilitate completion of the job at the space.
  • the controller facilitates completion of the job at the space by detecting a trigger associated with a space use case profile, and, in response to detecting the trigger associated with the space use case profile, controlling the plurality of devices of building equipment in accordance with a mode associated with the space use case profile.
  • the method includes storing, by the profiles repository, a plurality of additional job profiles, a plurality of additional job step profiles, and a plurality of space use case profiles.
  • the method also includes configuring the controller by selecting a set of additional job profiles from the plurality of additional job profiles, selecting a set of additional job step profiles from the plurality of additional job step profiles, selecting a set of additional space use case profiles from the plurality of additional space use case profiles, and installing the set of additional job profiles, the set of additional job step profiles, and the set of additional space use case profiles on the controller.
  • the method includes updating the controller by replacing the space use case profile with a second space use case profile.
  • the second space use case profile relates to a second space use case.
  • the space use case profile is associated with a first mode that includes a first set of settings for the plurality of devices of building equipment that serve the space and the second space use case profile is associated with a second mode that includes a second set of settings for the plurality of devices of building equipment that serve the space.
  • the method includes customizing at least one of the job profile, the job step profile, and the space use case profile from the profiles repository and storing the at least one of the job profile, the job step profile, and the space use case profile in an instance profiles repository.
  • FIG. 1 is a block diagram of a system for creating and storing job profiles, job step profiles, space use case profiles, mode profiles, space profiles, and place profiles, according to an exemplary embodiment.
  • FIG. 2 a block diagram of a system for customizing profiles created and stored in the system of FIG. 1 for application in particular places and spaces and/or to meet the requirements of a particular customer, according to an exemplary embodiment.
  • FIG. 3 is a flowchart of a process for creating job profiles, job step profiles, space use case profiles, mode profiles, space profiles, and place profiles, according to an exemplary embodiment.
  • FIG. 4 is a flowchart of a process for creating space logic, according to an exemplary embodiment.
  • FIG. 5 is a diagram of relationships between spaces, jobs, job steps, space use cases, modes, settings, mode logic, and events, according to an exemplary embodiment.
  • FIG. 6 is an illustration of a space application path, according to an exemplary embodiment.
  • FIG. 7 is an illustration of a process for managing modes, according to an exemplary embodiment.
  • FIG. 8 is an illustration of a first example of a space profile with a job profile, job step profiles, and space use case profiles, according to an exemplary embodiment.
  • FIG. 9 is an illustration of a second example of a space profile with a job profile, job step profiles, and space use case profiles, according to an exemplary embodiment.
  • FIG. 10 is an illustration of a system for development and deployment of modes and space profiles, according to an exemplary embodiment.
  • FIG. 1 systems and methods for designing and operating building systems based on jobs that people undertake in spaces and places are shown and described.
  • the systems and methods shown and described herein rely on a unique framework, introduced by the present disclosure, which conceptualizes the design and operation of building systems for spaces and places based on jobs, job steps, use cases, and space use cases, each of which is defined below.
  • this framework may be applied in applications, tools, systems, apparatuses, and methods that facilitate the design and operation of building systems.
  • a space is a sub-unit of a place, for example a room or floor of a building.
  • a place may be considered to be a space (i.e., a space made up of spaces) as the term space is used herein. Accordingly, it should be understood that concepts, features, processes, etc. described herein with reference to spaces may also be applicable to places.
  • a "job” refers to a goal or task that a person could work to accomplish.
  • a job is solution agnostic, i.e., conceptually independent of the specific actions undertaken or the technologies used to complete the job.
  • a job may be made up of a set of "job steps," which compose the job while remaining conceptually independent of the specific actions undertaken or the technologies used to complete each job step. Completing a job may require performance of multiple job steps in a particular order, in any order, or in some combination thereof. In some cases, one job may be completed by accomplishing various combinations of various job steps. Jobs and job steps are therefore aligned with the way people understand and conceptualize the work and goals that people seek to accomplish in spaces and places without being limited by particular manual or technological implementations.
  • a use case refers to a solution-dependent action or set of actions to accomplish a job step.
  • a use case may identify a particular technology (e.g., type of device, type of equipment) or set of technologies useable to accomplish a job step.
  • a use case may also identify particular actions to be taken by automated technologies or by one or more people.
  • a use case thereby describes an implementation of a job step.
  • multiple different use cases are possible for a single job step, reflecting the notion that a solution-independent job step may be accomplished in a variety of ways (i.e., by a variety of use cases).
  • a use case may be applicable to various types of spaces (e.g., office, conference room, patient room, operating room, classroom, kitchen, restroom, etc.) for which a corresponding job step may be relevant.
  • a use case as applied to a space is a "space use case.”
  • a space use case further defines a use case based on characteristics of the relevant space or type of space.
  • a space use case unifies a use case around a variety of technologies, occupants, and purposes of the space, for example the devices of building equipment that may be commonly found in a type of space and specialty or business systems affecting the space.
  • Formulated in this space-centric way a space use case is differentiated from traditional domain-centric frameworks that approach individual building domains separately.
  • Space use cases thereby provide space-centric, unified definitions of how spaces may facilitate jobs and job steps.
  • Space use cases bridge the gap between jobs and job steps— formulated in terms of human goals and objectives— and solutions unified around spaces to describe how spaces can support completion of job steps.
  • jobs, job steps, use cases, and space use cases provide a framework that supports design and operation of building systems focused on what people seek to accomplish at a building while avoiding overwhelming low-level implementation details that have been the traditional focus of building design and operation.
  • the framework may be applied in various design tools, data repositories, installation packages and tools, building management systems, online controllers, collections of building equipment, etc., as described in this application.
  • the framework may be well suited for application in a unified building management system, for example as described in U.S. Provisional Patent Application No. 62/636,504, incorporated by reference herein in its entirety.
  • Example embodiments of various implementations are shown in the FIGURES and described in detail below.
  • the framework and implementations based thereon provide a consistent specification for modeling space use cases, provide a unified execution environment for space use cases, allow flexibility in terms of how space use cases are developed, deployed, and executed (e.g., developed and instantiated in any order and at any time), and/or offload people from resolving conflicts that may arise from combining jobs, job steps, or use cases.
  • a building management system based on the framework described herein may provide environments through the implantation of space use cases instead of individual domain use cases, for example shifting the focus from individual building domains or integrations of a few building domains to a controlling entity that can coordinate, resolve conflicts between, and execute space use cases across all building domains, business systems, and/or specialty systems relating to a space.
  • the space may thereby be made more efficient and effective in facilitating jobs done in the space.
  • FIG. 1 a block diagram of a system 100 for creating and storing job profiles, job step profiles, space use case profiles, mode profiles, space profiles, and place profiles is shown, according to an exemplary embodiment.
  • profile refers to a data object that may contain various computer code, logic, data, attributes, files, etc. for characterizing various jobs, job steps, space use cases, modes, spaces, and places.
  • a profile may include one or more other profiles. Profiles may be organized based on the use case framework described above. Accordingly, as described in detail below, the system 100 may be configured to provide for the creation and storage of job profiles, job step profiles, space use case profiles, mode profiles, space profiles, and place profiles.
  • the system 100 is shown to includes a job profiles design tool 102, a job step profiles design tool 104, a space use case design tool 106, a modes design tool 108, and a places and spaces design tool communicably coupled to a master profiles repository 112.
  • the various design tools 102-110 are highly configurable.
  • the various design tools 102-110 may include various dedicated circuits, memory, processor(s), input/output devices, etc. operable to execute or facilitate the functions attributed thereto herein.
  • the various design tools 102- 110 are provided as graphical user interfaces and/or graphical user interface components to a user on a user device (e.g., personal computer, smartphone, tablet, laptop), for example in an application or browser-based, internet-accessible format.
  • a user device e.g., personal computer, smartphone, tablet, laptop
  • the various design tools 102-110 may be hosted and operated by a cloud server.
  • a cloud server e.g., a cloud server.
  • the job profiles design tool 102 is configured to facilitate design, creation, and editing of job profiles
  • the job step profiles design tool 104 facilitates design, creation, and editing of job step profiles (e.g., by a job designer).
  • the job profiles design tool 102 and the job step profiles design tool 104 may provide one or more graphical user interfaces that allow a user to input a design of a job or job step, respectively, and may generate a job profile and/or a job step profile based on the user input design.
  • a job profile characterizes a job that a person or people do at a space while a job step profile characterizes a job step to be done at a space.
  • Job profiles and job step profiles provide the specification for space use case creation and execution.
  • job profiles and/or job step profiles may contain desired outcomes, target metrics, required environmental actions, impacted environmental conditions, priority of the job or job step, among other possible characteristics.
  • a job profile that characterizes a job may contain one or more job step profiles that characterize job steps that make up the job.
  • the job profile may specify a sequence of the job steps.
  • a job step profile may include limits on environmental actions for the job step, a sequence of environmental actions for a job step, etc.
  • a job profile captures a solution agnostic specification of a job and may be used by any space use case that provides a solution for the job.
  • Job profiles may be used both to facilitate system/building design by guiding creation of space use cases and for online runtime control to guide consistent execution of space use cases for the corresponding job.
  • a job profile may define relationships with one or more related and/or dependent jobs.
  • a job profile may be part of a space profile, including master space profiles and instance space profiles. Job profiles may be created, edited, updated, removed, added, etc. without intervention from expert users or software developers.
  • a job step profile captures a solution agnostic specification of a job step and may be used by any space use case that provides a solution for the job step.
  • Job step profiles may be used both to facilitate system/building design guiding creation of space use cases and for online run-time control to guide consistent execution of space use cases for the corresponding job step.
  • a job step profile may contain one or more space use cases that may be used to complete the job step.
  • the space use case design tool 106 is configured to facilitate design, creation, and editing of space use cases (e.g., by a space use case designer).
  • the space use case design tool 106 may provide one or more graphical user interfaces that allow a user to input a design of a space use case and may generate a space use case profile based on the user input design.
  • This tool may hide complexity of domain-specific operations such that designers/creators/managers/etc. of the space use cases do not need deep domain-specific knowledge. For example, such designer need not be a Controls Specialist, Fire Technician, Security Technician, IT Analyst, Master Integrator, etc. in order to design/create/manage space use cases.
  • a space use case profile characterizes a space use case and may facilitate the seamless execution of a job or job step across all building domains, business systems, and specialty systems for a space.
  • Space use case profiles may unify use case solutions around the space to enable coordination, conflict resolution, and execution for the space.
  • Space use case profiles hide complexity of domain-specific operations so that users (e.g., designers, creators, managers) of space use case profiles do not need deep domain-specific knowledge.
  • space use case profiles may have an open framework (e.g., open data model, open software, software development kit, etc.) that allows third parties to create space use cases. Space use case profiles may rely on other information, logic, data, etc.
  • space use case profiles are associated with space profiles that characterize spaces and identify devices, equipment, sensors, etc. for the space.
  • Space use case profiles may identify one or more triggers that may start execution of the corresponding space use case.
  • a space use case profile for "Prepare Conference Room” may be triggered by someone unlocking the space by swiping an ID card and/or by occupancy detection at the start of a scheduled meeting.
  • Triggers may be environment-related (e.g., sensor-detected conditions such as light levels, temperature, occupancy), system related (e.g., outputs of other space use cases), and/or human related (e.g., user interaction with a user interface device).
  • a space use case profile may also identify other inputs that may be used for use case execution (e.g., measurements such as air temperature, historical weather data, data from other space use cases).
  • Space use case profiles may be added, updated, and/or removed in one or more of the following ways in various embodiments: Space use case profiles may be added, updated, and/or removed at the space use case level (i.e., by directly editing a space use case profile). Space use case profiles may also be added, updated, and/or removed at the job step level, for example by adding, updating, or removing a job step profile in a job profile. The space use case profiles associated with the altered job step profile may be altered accordingly. Space use case profiles may also be added, updated, and/or removed at the job profile level, for example by adding, updating, and/or removing a job profile in a space profile. The associated job step profiles and space use case profiles may be altered accordingly.
  • space use cases are solution dependent (i.e., with multiple possible solutions for executing one job step)
  • multiple space use case profiles may be associated with a single job step profile, for example as shown in FIG. 1 and described below.
  • Various space use case profiles may characterize space use cases of varying degrees of automation (e.g., manual, fully automated, combination of manual and automated), luxury (e.g., good, better, best solutions), etc.
  • Various space use case profiles may also be associated with various points of control of the same environmental condition (e.g., a mobile app and a wall panel).
  • various other factors that may differentiate various space use case profiles for the same job step profile include varying types of people using the system (e.g., varying roles, varying expertise, varying authorizations), various types of business systems and specialty systems (e.g., various scheduling, calendaring, or email systems, a nurse call system), varying technology in a space (e.g., sensors, cameras, equipment, devices, wearable technology), among other possibilities.
  • varying types of people using the system e.g., varying roles, varying expertise, varying authorizations
  • various types of business systems and specialty systems e.g., various scheduling, calendaring, or email systems, a nurse call system
  • varying technology in a space e.g., sensors, cameras, equipment, devices, wearable technology
  • the modes design tool 108 facilitates the creation and editing of mode profiles that characterize modes.
  • a mode profile is a data object (e.g., collection of data, computer code, logic, attributes) that defines a mode.
  • a mode describes how a space is designed to operate under specific circumstances that are triggered by environmental events, human events, or system events (e.g., activating a space use case).
  • a mode specifies particular low-level settings for equipment and devices.
  • Modes may be characterized by unified logic (i.e., for multiple domains such as lighting and HVAC) unified settings (e.g., temperature and lighting setpoints) for the space across multiple domains.
  • Modes may also be characterized by triggers that determine that the mode should be executed or entered into.
  • a mode profile may also define a priority for a mode that may be used to facilitate conflict resolution between multiple active modes for a space. Modes and systems and methods relating to modes are described in detail in U.S. Patent
  • each space use case profile identifies a corresponding mode profile that characterizes a mode that provides execution of the space use case.
  • one mode profile may be associated with multiple space use case profiles. The relationship between space use cases and modes (and between space use case profiles and mode profiles) is described in detail below.
  • the places and spaces design tool 110 is configured to facilitate design and creation of space profiles and place profiles.
  • a space profile characterizes a set of requirements for the design, operation, and use of a space while a place profile characterizes a set of requirements of the design, operation, and use of a place.
  • references to space profiles herein also captures place profiles (e.g., a place profile may be thought of as a type of space profile). Space and place profiles are described in detail in U.S. Patent Application 15/952, 173 filed April 12, 2018, incorporated by reference herein in its entirety.
  • the modes design tool 108 and the places and spaces design tool 110 may include one or more circuits and/or software applications configured to provide a user (e.g., job designer, space use case designer) with one or more graphical user interfaces that allow the user to design, create, edit, etc. mode profiles and space profiles.
  • the places and spaces design tool 110 and/or the modes design tool 108 may be suitable for use by a space profile designer (e.g., a person knowledgeable in building design, building domains, and space use) to design space profiles and/or mode profiles.
  • the places and spaces design tool 110 and/or the modes design tool 108 may be suitable for use by spaces applications engineers to develop applications that are available for selection in space profiles and can be used to execute use cases (e.g., applications executable on equipment in a space). Settings, triggers, priority etc. of such applications may be exposed in a user- friendly interface for manipulation by non-expert users of the places and spaces design tool 110 and/or the modes design tool 108.
  • the job profiles design tool 102, the job step profiles design tool 104, the space use case design tool 106, the modes design tool 108, and the places and spaces design tool 110 are communicably coupled to a master profiles repository 112.
  • the master profiles repository 112 stores "master" space use case profiles, job step profiles, job profiles, space profiles, place profiles, and/or mode profiles which are independent of particular end-customer design and/or installation.
  • the master profiles repository 112 provides a starting point for profile "instances" that may be used for a particular place or space and/or for a particular customer or other entity.
  • the job profiles design tool 102 provides job profiles to the master profiles repository 112 and the master profiles repository 112 stores the job profiles.
  • the job step profiles design tool 104 provides job step profiles to the master profiles repository 112 and the master profiles repository 112 stores the job step profiles.
  • the space use case profiles design tool 102 provides space use case profiles to the master profiles repository 112 and the master profiles repository 112 stores the space use case profiles.
  • the modes design tool 108 provides mode profiles to the master profiles repository 112 and the master profiles repository 112 stores the mode profiles.
  • the places and spaces design tool 102 provides space profiles to the master profiles repository 112 and the master profiles repository 112 stores the space profiles.
  • the master profiles repository 112 may also receive associations between space use case profiles, job step profiles, job profiles, space profiles, place profiles, and/or mode profiles from one or more of the design tools 102-110. In response, the master profiles repository 112 may organize the space use case profiles, job step profiles, job profiles, space profiles, place profiles, and/or mode profiles accordingly, for example as shown in FIG. 1. As shown in FIG. 1, the master profiles repository 112 includes a place profile 114 that includes a space profile 116. The space profile 116 includes multiple job profiles, including Job Profile A 118 and Job Profile Z 120, indicating that a job associated with Job Profile A 118 and a job associated with Job Profile Z 120 may be completed at the space associated with the space profile 116. Each job profile includes multiple job step profiles.
  • Job Profile A 118 includes Job Step Profile Al 122 though Job Step Profile AN 124, indicating that Job Step Profile Al 122 though Job Step Profile AN 124 correspond to job steps that make up the job characterized by Job Profile A 118.
  • each job step profile includes one or more space use case profiles, indicating that multiple solution dependent space use cases are possible for some solution-independent job steps.
  • Job Step Profile Al 122 is shown to include two space use case profiles
  • Job Step Profile AN 124 is shown to include one space use case profile.
  • the space profile 118 is also shown to include mode profiles 126 for that space.
  • the master profiles repository 112 thereby stores a variety of profiles that may be easily selected and retrieved for application in a particular building management system.
  • the design tools 102-110 may be used to add, remove, edit, update, etc. profiles in the master profiles repository 112.
  • the data structure illustrated in the master profiles repository 112 of FIG. 1 is included for illustrative purposes and is not intended to be limiting.
  • a single place profile 114 and a single space profile 116 are shown in the master profiles repository 112, it should be understood that the master profiles repository 112 may store any number of place profiles, space profiles, job profiles, job step profiles, space use case profiles, and mode profiles in various
  • the system 200 includes the master profiles repository 112 communicably coupled to a customization tool 202 and an instance profiles repository 204.
  • the instance profiles repository 204 is shown as communicably coupled to an unified building management system 206, indicating that the unified building management system 206 may receive profiles from the instance profiles repository 204.
  • the customization tool 202 allows a planner designer to select master profiles (e.g., space profiles, job profiles, job step profiles, space use case profiles, mode profiles) from the mater profiles repository 112 and customize the profiles as needed for a particular place, space, building management system, customer, etc.
  • master profiles e.g., space profiles, job profiles, job step profiles, space use case profiles, mode profiles
  • the planner designer may be directed by a seller that works closely with a buyer/customer to determine the customer's needs for a place, determine the jobs and job steps to be completed in the space, the types of solutions (i.e., space use cases) suitable for the customer and the place, etc.
  • the planner designer may then identify a bundle (i.e., kit) of profiles from the master profiles repository 112 to offer to the customer/buyer that may satisfy the customer's needs. For example, in a case where multiple space use case profiles are included in a master job step profile, the customization tool 202 may allow the planner designer to select one of the multiple space use case profiles to be used for that
  • Bundles may be purchased to address particular outcomes for select space types and may determine which space profiles are used from the master profiles repository 112 for that place/customer. In some cases, the planner designer may select the outcomes the customer wants to achieve to create an appropriate bundle without specifying particular space profiles.
  • the customization tool 202 may facilitate the planner designer in accessing and copying the profiles in the bundle from the master profiles repository 112.
  • customization tool 202 may also facilitate the planner designer in altering any profile or element thereof to further tailor the profiles to the needs of a particular place and/or customer.
  • the customization tool 202 thereby facilitates the creation of "instance" profiles.
  • the customization tool 202 provides the instance profiles to the instance repository 204 for storage therein. In some embodiments, as illustrated in FIG. 2, the customization tool 202 may be skipped such that profiles from the master profiles repository 112 may be directly transferred to the instance profile repository 204.
  • the instance profiles may then be installed for use in online control of spaces and places.
  • the instance profiles repository 204 is communicable with a unified building management system 206 to facilitate installation/implementation of the instance profiles in the unified building management system 206.
  • the unified building management system may be a collection of equipment, devices, sensors, controllers, etc. across building domains, specialty systems, and business systems, for example as described in U.S. Provisional Patent Application 62/636,504 filed February 28, 2018, incorporated by reference herein in its entirety. It should be understood that while FIG. 2 shows a unified building management system 204, the profiles, framework, and related systems and process described herein may also be applied to various other building management systems, building equipment, etc.
  • space profiles, job profiles, job step profiles, space use case profiles, mode profiles may be installed on various devices, equipment, sensors, controllers, networks, etc. of the unified building management system 206.
  • the system 200 may also facilitate troubleshooting, configuration, verification, and validation to ensure that use cases execute successfully in online control.
  • profiles may be added, removed, edited, updated, etc. on the unified building management system 204 during online use.
  • Instance profiles may be plug-and-play such that instance profiles can be installed on the unified building management system 206 without expert intervention.
  • Various devices, equipment, sensors, controllers, networks, etc. of the unified building management system 206 may then be controlled and/or operated in accordance with the profiles to provide space use cases and facilitate execution of jobs and job steps at spaces and places.
  • Process 300 may be carried out using the design tools 102-110 of FIG. 1 in communication with the master profiles repository 112 and/or the instance profiles repository 204.
  • a usable base space profile may be a space profile with similar characteristics as a new space profile to be created using process 300 that may be edited, added to, updated, modified, extended, etc. to create a new space profile. If a usable base space profile is available, at step 304 that space profile is selected for modification in process 300. That is, a copy of base space profile may be made from the master profiles repository 112 to serve as a starting point for a new space profile at step 306 and the remainder of process 300. If no useable base space profile is available, at step 305 a new space profile may be created by a user for modification/design/etc.
  • a job is designed and a job profile for that job is created.
  • the job profiles design tool 102 may provide a user with a graphical user interface that allows the user to define a job.
  • the job profiles design tool 102 may receive the user input and generate a job profile based on the user input.
  • a job is thereby designed and a corresponding job profile created.
  • an existing job profile may be selected from the master profiles database 112 at step 306.
  • a job step is designed for the job designed at step 308.
  • a job step profile is created and included in the job profile created at step 306.
  • the job step profiles design tool 104 may profile a user with a graphical user interface that allows the user to define a job step.
  • the job step design tool 104 may receive the user input and generate a job step profile based on the user input.
  • a job step is thereby designed and a corresponding job step profile created that facilitates execution of the job designed at step 306.
  • an existing job step profile may be selected from the master profiles database 112 at step 308.
  • a space use case is designed that corresponds to the job step designed at step 308.
  • a space use case profile is created and included in the job step profile designed at step 308.
  • the space use case design tool 106 may provide a user with a graphical user interface that allows the user to define a space use case.
  • the space use case design tool 106 may receive the user input and generate a space use case profile based on the user input.
  • a space use case is thereby designed a corresponding space use case profile created that facilitates execution of the job step designed at step 308 and the job designed at step 306.
  • an existing space use case profile may be selected from the master profiles database 112 at step 310.
  • the master profiles repository 112 may store multiple mode profiles that characterize a variety of modes that may be selected and associated with various space use cases. For example, basic and/or generic modes (e.g., generic room control with occupancy settings) may be developed in advance. In such a case, process 300 may proceed to step 314 where the pre-defined mode (i.e., an existing mode profile) may be associated with the space use case profile created at step 310. In preferred embodiments, each space use case profile is associated with a single mode profile.
  • a space use case may require the development of new space logic and/or the addition of a new mode. In such a case, no existing mode exists for the space use case and the process 300 proceeds from step 312 to steps 316 and step 318 where a new mode is created.
  • a user selects space logic for the new mode.
  • the space logic may be selected from a repository of pre-defined space logics.
  • the space logic may be presented to a user as a black box, such that a user need only interact with configuration, trigger, and priority endpoints, for example.
  • a user may desire to define new space logic.
  • a process 400 for defining space logic is shown in FIG. 4 and described in detail with reference thereto.
  • space logic may be created automatically by the mode profiles design tool 108 based on one or more space use case profiles.
  • settings for the new mode are selected.
  • the relevant settings may be defined by the space logic selected at step 316.
  • the mode profiles design tool 108 generates a graphical user interface that provides the user with settings fields that allows a user to define settings for the mode (e.g., temperature setpoints, lighting levels, trigger conditions, etc.) without requiring software development or building domain expertise.
  • the mode profiles design tool 108 may create a mode profile based on the user input.
  • modes may be created automatically by the mode profiles design tool 108 based on one or more space use case profiles.
  • the new mode profile may then be associated with the space use case profile created in step 310.
  • the mode profile may also be stored independent of the space use case profile in the master profiles database 112.
  • process 300 proceeds to step 326 where a determination is made regarding whether more job steps are desired and/or required for the job defined at step 306. For example, when a job is intended to be made up of multiple job steps the process 300 may return to step 308 several times so that the multiple job steps can be defined and corresponding job step profiles created.
  • process 300 proceeds to step 328 where a determination is made regarding whether more jobs are desired and/or required for the space.
  • a space may be associated with any number of jobs (i.e., a space profile may include any number of job profiles). Accordingly, in some cases the process 300 returns to step 306 where another job is designed and a corresponding job profile is created.
  • Process 300 is therefore highly configurable and flexible to adjust to any desired combination of design and customization steps in concert with use of pre-created space, job, job step, space use case, and mode profiles.
  • the space profile is saved in the master profiles repository 112 and/or the instance profiles repository 204. That is, the job profiles, job step profiles, space use case profiles, and mode profiles created and/or selected during process 300 may be collected in a space profile and stored in master profiles repository 112 and/or the instance profiles repository 204. The new space profile may then be selected for installation and online use.
  • a process 400 for creating space and cross-space logic is shown, according to an exemplary embodiment.
  • a designer may select one or more systems, for example an HVAC system, a lighting system, a security system, a specialty system, a business system, etc.
  • the designer may define logic for the control of the selected system(s).
  • the logic may define input points (e.g., physical measurements, user inputs, etc.) and one or more algorithms or rules that determine outputs (e.g., control signals) based on the input points.
  • various settings, event endpoints, and/or other parameters of the logic are exposed.
  • the logic may be defined in a computer-programming language, various settings, event endpoints, and/or other parameters may be implemented in such a way that they can be easily modified in a user-friendly graphical user interface without knowledge of the programming language or other software development expertise.
  • the space logic is saved, for example in a space profile in the master profiles repository 112.
  • FIG. 5 a diagram 500 illustrating the relationships between spaces, jobs, job steps, space use cases, modes, settings, mode logic, and events is shown, according to an exemplary embodiment.
  • the diagram 500 may illustrate relationships, profiles, and logic defined using process 300 and/or process 400.
  • the diagram 500 may illustrated relationships, profiles, and logic created by design tools 102-110 and/or stored in the master profiles repository 112 and/or the instance profiles repository 204.
  • a space 502 supports any number of modes 504.
  • the modes 504 may be associated/dropped into the space 502.
  • Each mode 504 has priority (e.g., an integer value), logic (e.g., software code), and a trigger (e.g., an event).
  • priority e.g., an integer value
  • logic e.g., software code
  • a trigger e.g., an event
  • each mode 504 becomes operational but not necessarily active until the mode 504 is activated/triggered by an event 506.
  • the mode 504 executes mode logic 508 and provides settings 510 that realize a space use case 512. Accordingly, the event 506 may be seen as triggering the space use case 512.
  • the space use case 512 realizes a job step 514 that may be among multiple job steps 514 associated with a job 516.
  • the job 516 is associated with the space profile 502.
  • modes 504 may be temporarily disabled to prevent interference with special user activities. Disabling a mode can be a simplifying alternative to over-proliferating modes. For example, temporarily disabling an "unoccupied mode" may be a way to keep a room in an "occupied mode” for maintenance and repairs or to maintain comfort levels during short periods of absence.
  • multiple space use cases 512 may be simultaneously active, for example as a result of multiple trigger events 506. The execution of all active space use cases 512 may be coordinated in determining when and how to engage low level logic of each building domain, for example to resolve any conflicts that may arise between simultaneously active space use cases 512.
  • prioritization, coordination, conflict resolution, etc. is performed at the space use case level, the job level, the job step level, the mode level, and/or a combination thereof. Conflict resolution and coordination may therefore be achieved at these higher levels in the framework as opposed to at the lowest level of control logic for equipment and devices.
  • a space profile 502 may include an ordered series of space desired outcomes that facilitate coordination and conflict resolution (e.g., a patient room first needs to be clean, then comfortable). These preferences may be based on user-defined rules or algorithms or artificial intelligence approaches such as machine learning.
  • the prioritization strategy may be easily changed by a user at any time (e.g., by selecting between an "energy savings” strategy and a "comfort” strategy).
  • certain priorities may be locked, for example to prevent a fire emergency use case from being set to a low priority by mistake or maliciously.
  • priority may be assigned to various people and space use cases may be prioritized based on who is involved with executing or requesting a space use case. For example, a set of space use cases associated with a nurse may have a higher priority and therefore override space use cases associated with a patient.
  • plug- and-play conflict resolution modules may be applied to update, add, or otherwise alter conflict resolution rules, algorithms, machine learning, etc. without the intervention of expert users or software developers.
  • the space profile 602 may be aware of related spaces and related space use cases 512 that are active or have been active.
  • each space profile 602 may be aware of relationships between multiple spaces in a places. These relationships may include physical aspects (e.g., relative locations of spaces) as well as other information that provides an understanding of what is going on in those spaces (e.g., what assets are in those spaces, what the related spaces are, what space use cases have occurred or are occurring in the related spaces). For example, a person in a conference room may need to find the nearest portable A/V equipment located in another space.
  • the person can be directed to the closest space (conference rooms, equipment closet, etc.) where the portable A/V equipment is not in use, based on space use case activity in those spaces.
  • a person in a research lab may need to find the nearest portable spectrophotometer located in another space.
  • the person may be informed that all portable spectrophotometers are in use based on the space use case activity and lab inventory.
  • the space use case will also inform the person which spectrophotometer is likely to free up the soonest using predictive analytics based on the historical space use case activity.
  • space use case history may be one piece of space data that may be fed into analytics to provide predictive preventive maintenance and space utilization
  • FIG. 6 an illustration of a space profile application path 600 is shown, according to an exemplary embodiment.
  • the space profile application path 600 is a representation of online control based on the space use case framework described herein.
  • a space 602 has a space profile 604.
  • the space profile 604 has one or more mode profile 606 that define settings 608.
  • the settings 608 apply to space applications 610 for the space (e.g., a space application 610 for each mode 606).
  • the space applications 610 run on a space controller 612 (i.e., space applications 610 are executed by a processor of a space controller 612).
  • the space controller 612 is communicably and operably coupled to space equipment 614 and controls the space equipment 614 by executing the space applications.
  • steps 610- 614 illustrate an example of how a space use case may be realized. That is, steps 610-614 are one way to create the "realizes" link between the settings 510 and the space use case 512 in FIG. 5.
  • the space profile application path 600 thereby forms the loop shown in FIG. 6.
  • space controller may refer to any combination of circuitry, software components, hardware components (e.g., memory components, processing components) etc. configured to performed the disclosed functions.
  • a space controller may be a device positioned locally at a space or place, may manage one or more spaces or places, may be distributed across various computing devices, may be hosted on a remote server and/or cloud computing resource, etc. Accordingly, it should be understood that the space controller is highly configurable according to various embodiments.
  • FIG. 7 a diagram 700 illustrating a process for managing modes is shown, according to an exemplary embodiment.
  • the diagram 700 shows steps taken by and/or for a user 702, a space controller 704, a mode blender circuit 706, an event manager circuit, with time progressing along a vertical axis from the top of the diagram 700 to the bottom of the diagram 700.
  • the user 702 may add a mode by providing the mode and a priority for the mode to the controller 704.
  • a space use case designer 701 adds a space use case to a mode generator 703.
  • the mode generator 703 automatically generates a new mode based on the mode generator and adds the mode to the space controller 704.
  • the space controller 704 may validate the mode and provide the mode to the mode blender circuit 706 for blending with one or more other modes already associated with the space.
  • the mode blender circuit 706 is configured to determine space logic for the space based on a blending of multiple modes, for example as described in detail below.
  • the mode blender circuit 706 provides the updated space logic to the space controller 702, which may use the updated space logic to control systems, equipment, devices, etc. for the space.
  • the mode blender circuit 706 may also register the new mode as a listener with the event manager 708 to provide the event manager 708 with an indication of the trigger for the new mode (i.e., to cause the event manager 708 to monitor for the trigger).
  • the user 702 may remove a mode from the space controller 704.
  • the space controller 704 may instruct the mode blender circuit 706 to unblend the removed mode from the other modes for the space.
  • the mode blender circuit 706 may determine updated space logic for the space that does not use the removed mode.
  • the mode blender circuit 706 may provide the updated space logic to the space controller 702, which may use the updated space logic to control systems, equipment, devices, etc. for the space.
  • the mode blender circuit 706 may also communicate with the event manager circuit 708 to unregister the removed mode as a listener, i.e., to cause the event manager circuit 708 to cease monitoring for the trigger associated with the removed mode.
  • modes may be triggered by events (e.g., human events, environmental events) that are not under system control, multiple modes for a space may be active simultaneously.
  • the mode blender circuit 706 may follow a clear strategy to ensure that the system behaves deterministically when multiple modes are actively simultaneously.
  • priority may be determined by a runtime function.
  • priority is driven by an associated use case outcome. For example, if a mode is associated with a life-threatening safety feature or event, that mode may take precedence over non-life-preserving modes. Various other types of outcomes may be ranked in a similar fashion.
  • each mode is explicitly assigned a priority during a design phase.
  • a mode designer may be made aware of all possible modes that can be simultaneously active and explicitly indicate desired system behaviors for each possibility.
  • the mode designer may rank modes on a numerical priority scale (e.g., from zero to thirty). The following example for a patient room is one such example.
  • a patient room has multiple space use cases:
  • a patient comfort use case allows the patient to tweak room environment settings for different activities, within preset limits, for example temperature and lights.
  • a clean room pending space use case is applied after a patient is discharged and schedules the room for cleaning. Until the cleaning staff arrives for cleaning, the room is put in a dormant state (lights off, temperature to unoccupied settings).
  • a fire space use case allows the space to react when a fire is started in the building, for example by turning on lights, turning on a strobe light, putting
  • a system administrator may add modes incrementally to be associated with the space use cases outlined above.
  • the system e.g., the mode blender circuit 706
  • the system may ensure that the mode fits with existing modes, for example by prompting the system administrator to input a priority for the new mode. Accordingly, the result may be the same regardless of the order in which modes are added.
  • the following table provides further details relating to this example:
  • a software module is added to the room
  • Patient is control application that sets the environment
  • a software module is added to the room
  • a software module is added to the room
  • Room 10 set the room condition to dormant in the
  • a software module is added to the room
  • modes and priorities are possible in various embodiments.
  • modes may be mutually exclusive (e.g., a space may be either occupied or unoccupied but not both).
  • a generic room application is shown in the following table:
  • an occupied mode can be considered a base whose settings can be overridden or extended by other concurrent modes (e.g., a conversation mode or presentation mode).
  • a conversation mode or presentation mode e.g., a conversation mode or presentation mode.
  • applicable modes may be selected from a list of available modes based on the space profile.
  • modes may designed and developed independently from spaces and assigned priorities. An example of such a case is shown in the following table:
  • FIG. 8 an illustration of a first example of how the framework, systems, and methods described herein may facilitate completion of a job at a space is shown, according to an exemplary embodiment.
  • the space is a conference room and the job is to host a meeting.
  • FIG. 8 includes a block 800 that indicates how a human user may conceptualize the job of hosting a meeting at the conference room.
  • FIG. 8 also includes a block 802 that shows how the job is organized into a place profile, space profile, job profile, multiple job step profiles, and multiple space use case profiles in the present embodiment.
  • Conference Room system the access control system.
  • FIG. 9 an illustration of a second example of how the framework, systems, and methods described herein may facilitate completion of a job at a space or place is shown, according to an exemplary embodiment.
  • the space is a conference room and the job is to fix an HVAC environmental problem in the conference room.
  • completing this job includes both a security officer and a HVAC service technician.
  • FIG. 9 includes a block 900 that indicates how the security officer may conceptualize the job of fixing an HVAC environmental problem in the conference room.
  • FIG. 9 also includes a block 902 that indicates how the HVAC security technician may conceptualize the job of fixing an HVAC environmental problem in the conference room.
  • FIG. 9 further includes a block 904 that shows how the job is organized into a place profile, space profile, job profile, multiple job step profiles, and multiple space use case profiles in the present embodiment.
  • the HVAC Service Event The HVAC
  • Mode System normal in the HVAC system. and ensure lights go back Check use. Returns lighting to to scheduled operation.
  • FIG. 10 an illustration of a system 1000 for development and deployment of mode profiles and space profiles consistent with the framework described herein is shown, according to an exemplary embodiment.
  • a mode designer may develop multiple modes 1002 and store the modes in a space modes repository 1004.
  • modes may be developed independent of spaces.
  • modes may be development independent of any particular instance of a space but may require at least a generic space profile that facilitates development (e.g., by defining equipment, devices, etc. available to implement the mode).
  • a space designer may design multiple space profiles 1006, for example by including modes 1002 from the space modes repository 1004 in one or more of the space profiles 1008.
  • the space profiles may be stored in a space profile designs repository 1008.
  • a space use case designer may design a space use case to create a space use case profile 1009.
  • the space use case profile 1009 may be associated to an existing mode 1002 (e.g., a mode developed by the mode designer) or may cause the automatic generation of a new mode 1011.
  • the automatically-generated new mode 1011 is stored in the space modes repository 1004.
  • a system administrator may then deploy a space profile from the space profile designs repository 1008 to real (i.e., physical) spaces.
  • a space profile from the space profile designs repository 1008 to real (i.e., physical) spaces.
  • FIG. 10 also illustrates that an active mode 1018 in a space profile may determine an equipment specification 1020, applications 1022, and controller 1024. The equipment 1020 and the controller 1024 may run the applications 1022.
  • the present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations.
  • the embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system.
  • Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon.
  • Such machine- readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor.
  • machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor.
  • a network or another communications connection either hardwired, wireless, or a combination of hardwired or wireless
  • any such connection is properly termed a machine-readable medium.
  • Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
  • circuit may include hardware structured to execute the functions described herein.
  • each respective “circuit”, “repository,” “controller,” and/or “tool” may include machine-readable media for configuring the hardware to execute the functions described herein.
  • the circuit may be embodied as one or more circuitry components including, but not limited to, processing circuitry, network interfaces, peripheral devices, input devices, output devices, sensors, etc.
  • a circuit may take the form of one or more analog circuits, electronic circuits (e.g., integrated circuits (IC), discrete circuits, system on a chip (SOCs) circuits, etc.), telecommunication circuits, hybrid circuits, and any other type of “circuit.”
  • the "circuit” may include any type of component for accomplishing or facilitating achievement of the operations described herein.
  • a circuit as described herein may include one or more transistors, logic gates (e.g., NA D, AND, NOR, OR, XOR, NOT, XNOR, etc.), resistors,
  • multiplexers registers, capacitors, inductors, diodes, wiring, and so on).
  • the "circuit” "repository,” “controller,” or “tool” may also include one or more processors communicably coupled to one or more memory or memory devices.
  • the one or more processors may execute instructions stored in the memory or may execute instructions otherwise accessible to the one or more processors.
  • the one or more processors may be embodied in various ways.
  • the one or more processors may be constructed in a manner sufficient to perform at least the operations described herein.
  • the one or more processors may be shared by multiple circuits (e.g., circuit A and circuit B may comprise or otherwise share the same processor which, in some example embodiments, may execute instructions stored, or otherwise accessed, via different areas of memory).
  • the one or more processors may be structured to perform or otherwise execute certain operations independent of one or more co-processors.
  • two or more processors may be coupled via a bus to enable independent, parallel, pipelined, or multithreaded instruction execution.
  • Each processor may be implemented as one or more general-purpose processors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), digital signal processors (DSPs), or other suitable electronic data processing components structured to execute instructions provided by memory.
  • the one or more processors may take the form of a single core processor, multi- core processor (e.g., a dual core processor, triple core processor, quad core processor, etc.), microprocessor, etc.
  • the one or more processors may be external to the apparatus, for example the one or more processors may be a remote processor (e.g., a cloud based processor). Alternatively or additionally, the one or more processors may be internal and/or local to the apparatus. In this regard, a given circuit or components thereof may be disposed locally (e.g., as part of a local server, a local computing system, etc.) or remotely (e.g., as part of a remote server such as a cloud based server). To that end, a "circuit", “repository,” “controller,” or “tool” as described herein may include components that are distributed across one or more locations. The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations.
  • Embodiments of the present disclosure can be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system.
  • Embodiments within the scope of the present disclosure include program products comprising machine- readable media for carrying or having machine-executable instructions or data structures stored thereon.
  • Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor.
  • machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine- readable media.
  • Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Primary Health Care (AREA)
  • Game Theory and Decision Science (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un système de gestion de bâtiments comprenant une pluralité de dispositifs d'équipement de bâtiments et un dispositif de commande configuré pour associer un espace à un premier groupe de dispositifs qui desservent l'espace. Le dispositif de commande est également configuré pour sélectionner un profil d'espace parmi une pluralité de profils d'espace pouvant être sélectionnés. Au moins deux profils des profils d'espace sont associés à un type différent d'espace desservant une fonction différente. Le profil d'espace comprend une pluralité de profils de travail. Chaque profil de travail comprend un profil de cas d'utilisation d'espace qui identifie la manière d'accomplir au moins une partie du travail associé au profil de travail. Le dispositif de commande est également configuré pour sélectionner le profil de cas d'utilisation d'espace et pour commander au moins une partie du premier groupe de dispositifs conformément au profil de cas d'utilisation d'espace de façon à exécuter un cas d'utilisation d'espace qui accomplit au moins la partie du travail associé au profil de travail.
PCT/US2018/051182 2017-09-19 2018-09-14 Système de gestion de bâtiments unifiée à profils de cas d'utilisation d'espace WO2019060225A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18789285.6A EP3685326A1 (fr) 2017-09-19 2018-09-14 Système de gestion de bâtiments unifiée à profils de cas d'utilisation d'espace

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201762560567P 2017-09-19 2017-09-19
US62/560,567 2017-09-19
US15/952,173 2018-04-12
US15/952,173 US10156833B2 (en) 2017-04-13 2018-04-12 Building management system with space profiles

Publications (1)

Publication Number Publication Date
WO2019060225A1 true WO2019060225A1 (fr) 2019-03-28

Family

ID=65810482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/051182 WO2019060225A1 (fr) 2017-09-19 2018-09-14 Système de gestion de bâtiments unifiée à profils de cas d'utilisation d'espace

Country Status (2)

Country Link
EP (1) EP3685326A1 (fr)
WO (1) WO2019060225A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080281472A1 (en) * 2007-03-01 2008-11-13 Syracuse University Open Web Services-Based Indoor Climate Control System
US20110087650A1 (en) * 2009-10-06 2011-04-14 Johnson Controls Technology Company Creation and use of causal relationship models in building management systems and applications
US20150293508A1 (en) * 2014-04-11 2015-10-15 Johnson Controls Technology Company Systems and methods for creating and using equipment definitions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080281472A1 (en) * 2007-03-01 2008-11-13 Syracuse University Open Web Services-Based Indoor Climate Control System
US20110087650A1 (en) * 2009-10-06 2011-04-14 Johnson Controls Technology Company Creation and use of causal relationship models in building management systems and applications
US20150293508A1 (en) * 2014-04-11 2015-10-15 Johnson Controls Technology Company Systems and methods for creating and using equipment definitions

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Delta Building Management and Control System", INTERNET ARTICLE, 1 September 2016 (2016-09-01), XP055522941, Retrieved from the Internet <URL:http://www.deltaww.com/filecenter/solutions/download/05/Delta_BMCS_LDALISolutionGuide_201608_eng.pdf?CID=23> [retrieved on 20181112] *
CLAIRE ROWLAND ET AL: "Designing Connected Products: UX for the Consumer Internet of Things", 31 May 2015, O'REILLY, ISBN: 978-1-4493-7256-9, pages: ToC,Ch01-Ch04,Ch07 - Ch08, Ch10, Ch14, Ch15, Ind, XP055519815 *
JAMES M. SINOPOLI: "Smart Buildings Systems for Architects, Owners and Builders", 18 November 2009, BUTTERWORTH-HEINEMANN, ISBN: 978-1-85617-653-8, XP055522266 *
WIKIPEDIA: "Building automation", INTERNET ARTICLE, 7 September 2017 (2017-09-07), XP055522291, Retrieved from the Internet <URL:https://en.wikipedia.org/w/index.php?title=Building_automation&oldid=799424260> [retrieved on 20181108] *
WIKIPEDIA: "Building management system", INTERNET ARTICLE, 30 August 2017 (2017-08-30), XP055522287, Retrieved from the Internet <URL:https://en.wikipedia.org/w/index.php?title=Building_management_system&oldid=797980461> [retrieved on 20181108] *

Also Published As

Publication number Publication date
EP3685326A1 (fr) 2020-07-29

Similar Documents

Publication Publication Date Title
US10599115B2 (en) Unified building management system with space use case profiles
US11706161B2 (en) Building system with space use case operation
US20220350301A1 (en) Building system with semantic modeling based searching
US11394576B2 (en) Unified building management system
US8041435B2 (en) Modular object dynamic hosting
US8265775B2 (en) Modular object publication and discovery
CA2884883C (fr) Thermostat logiciel a apprentissage social pour immeubles commerciaux
US8818757B2 (en) Modular object and host matching
US6073110A (en) Activity based equipment scheduling method and system
WO2018191565A1 (fr) Système de gestion de bâtiment à profils d&#39;espace
JPH0589045A (ja) データ処理システム及び作成方法
Mokhtari et al. A reliability/availability approach to joint production and maintenance scheduling with multiple preventive maintenance services
AU2005265394A1 (en) Scenario editors and scenario rules aggregators for resource-allocation systems
CN105745585A (zh) 卸载人机交互任务
US11493893B2 (en) Integrated intelligent building management system
JP2022094315A (ja) コンピュータ実装方法、コンピュータ・プログラム、コンピュータ・システム、及びコンピュータ可読な記録媒体
CN110443529A (zh) 资源调度方法、装置、设备与计算机可读存储介质
EP3685326A1 (fr) Système de gestion de bâtiments unifiée à profils de cas d&#39;utilisation d&#39;espace
Runde et al. Integrated automated design approach for building automation systems
Guirro et al. Manufacturing operational management modeling using interpreted Petri nets
CN109896370A (zh) 一种电梯楼层权限设置方法、装置及设备
US10620919B2 (en) Creating and operating software applications
JP7542462B2 (ja) 情報処理装置、情報処理方法、サービス提供システム
JPH10320035A (ja) ビル管理システム
EP3042309A1 (fr) Gestion d&#39;un facteur sensoriel

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18789285

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018789285

Country of ref document: EP

Effective date: 20200420