WO2012075485A1 - Operation scheduler for a building automation system - Google Patents
Operation scheduler for a building automation system Download PDFInfo
- Publication number
- WO2012075485A1 WO2012075485A1 PCT/US2011/063268 US2011063268W WO2012075485A1 WO 2012075485 A1 WO2012075485 A1 WO 2012075485A1 US 2011063268 W US2011063268 W US 2011063268W WO 2012075485 A1 WO2012075485 A1 WO 2012075485A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- schedule
- operational
- automation
- computer
- implemented method
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
- H04L12/282—Controlling appliance services of a home automation network by calling their functionalities based on user interaction within the home
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
- H04L12/2821—Avoiding conflicts related to the use of home appliances
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L2012/2847—Home automation networks characterised by the type of home appliance used
- H04L2012/2849—Audio/video appliances
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L2012/2847—Home automation networks characterised by the type of home appliance used
- H04L2012/285—Generic home appliances, e.g. refrigerators
Definitions
- the automation components, sensors, equipment and devices are deployed throughout the structure and provide the information necessary to control one or more environmental variables within the structure.
- the automation components, sensors, equipment and devices are often operated in a coordinated manner based on, for example, a timed schedule, detected condition, received command or other input.
- conventional building automation systems may adjust and control, for example, lighting levels and HVAC systems of an entire building according to a timed schedule and one or more detected events.
- building automation systems often utilize and incorporate automation components, sensors, equipment and devices supplied by different vendors and manufacturers. The different suppliers configure their proprietary automation components, sensors, equipment and devices according to different protocols and control schemes in order to maximize
- This patent document relates to an automation control tool configured to generate an operations scheduler that provides a unified interface or mechanism for monitoring and controlling automation components, sensors, equipment and devices operable within a building automation system. Moreover, disclosed operations scheduler and building automation control tool may interact with automation components, sensors, equipment and devices that utilize and/or are configured according to different communication and operational protocols.
- the disclosed automation control tool and operations scheduler may be configured to direct the operation of automation components, sensors, equipment and devices based on one or more operational schedules that may be designed years in advance. Similarly, the disclosed automation control tool and operations scheduler may implement and execute reporting, trending and analysis functionality based to monitor and track aspects or elements of the operational schedule. In this way, the disclosed automation control tool and operations scheduler provides a valuable mechanism with which long-term planning and control may be
- the operational schedules defined and controlled by the disclosed automation control tool and operations scheduler may be implemented to ensure coordinated interoperability with a high degree of precision and reliability between the automation components, sensors, equipment and devices operating within the building automation system.
- the disclosed automation control tool and operations scheduler may further be configured to organize equipment, devices and modules operating with the building automation system into logical groupings or zones. Multiple zones or groupings can be further combined to generate or define a group.
- Operational schedules defined or stored by the disclosed automation control tool and operations scheduler may, in an exemplary embodiment, contain a start time and a stop time for each equipment event within each zone or group of zones. Operational schedules may further define the start or initiation time at which the automation control tool begins to generate desired reports, trend collection or other analysis functions.
- a building automation control tool configured to manage and control multiple automation components couple via a building
- the building automation control tool includes a processor, a memory in communication with the processor and configured to store one or more processor implementable instructions.
- the processor implementable instructions are configured to receive a first operational schedule comprising a first start time and a first stop time related to the operation of a first automation device, receive a second operational schedule comprising a second start time and a second stop time related to the operation of a second automation device, recognize the first and second start and stop times associated with the first and second operational schedules, respectively, and generate a unified schedule that: displays the first operational schedule as a first time period that extends between the first start time and the first stop time; and displays the second operational schedule as a second time period that extends between the second start time and the second stop time, wherein the second time period is aligned relative to the first time period.
- a computer-implemented method for managing and controlling multiple automation components coupled via a building automation network includes receiving, via the building automation network, a first operational schedule detailing a first operational period of a first automation device, such that the first operational schedule is formatted according to a first protocol, receiving, via the building automation network, a second operational schedule detailing a second operational period of a second automation device, such that the second operational schedule is formatted according to a second protocol, converting the received second operational schedule from the second protocol to the first protocol, generating a unified schedule based on the first operational schedule and the converted second operational schedule, such that the unified schedule arranges the first operational time period relative to the second operational time period, and displaying the unified schedule in a user accessible manner.
- a computer-implemented method for managing and controlling multiple automation components coupled via a building automation network includes generating, at a workstation, a unified schedule that includes a first operational schedule associated with a first automation device and a second operational schedule associated with a second automation device, determining operational protocols for the first automation device and the second automation device, communicating, via the building automation network, the first operational schedule to the first automation device according to a first protocol, converting the second operational schedule to a second protocol, communicating, via the building automation network, the second
- FIG. 1 illustrates one embodiment of a building automation system configured to implement an automation control tool and operations scheduler in accordance with the disclosure provided herein;
- FIG. 2 depicts an internal functional block diagram of an exemplary computer system configured to implement an automation control tool and operations scheduler in accordance with the disclosure provided herein;
- FIG. 3 illustrates one embodiment of a unified schedule that may be generated by the operations scheduler module and the automation control tool disclosed herein;
- FIGS. 4 and 5 illustrate another embodiment of a unified schedule and process legend that may be recognized by the operation scheduler module and automation control tool implemented in accordance with the disclosure provided herein;
- FIG. 6 illustrates another embodiment of a schedule and layout generated in accordance with the disclosure provided herein.
- the disclosed automation control tool and operations scheduler may be configured to provide a unified interface or schedule display for monitoring and controlling the operations of, and generating reports related to, the devices and components operable within a building automation system.
- activity schedule and reports may be designed and implemented years in advance in accordance with a long-term control strategy to direct individual devices and equipment with a high degree of precision and reliability.
- control plans and activity schedules for a building may be defined far in advance which address seasonal changes in temperature, daylight and other long-term environmental conditions.
- the building lighting control scheme may be adjusted or controlled utilizing the disclosed operations scheduler and automation control tool to compensate for changes in the ambient lighting conditions.
- the building HVAC control scheme may be adjusted or controlled utilizing the disclosed automation control tool and operations to compensate for changes in the ambient temperature or weather conditions associated with typical seasonal variations.
- the building HVAC control scheme may further be adjusted or edited to compensate for sensed or detected conditions that deviate from the expected seasonal variations.
- the disclosed automation control tool and operations scheduler may be configured to organize equipment, devices and modules operating with the building automation system into logical groupings or zones. Multiple zones or groupings can be further combined to define a group.
- Schedules defined or stored by the disclosed automation control tool and operations scheduler may, in an exemplary embodiment, contain a start time and a stop time for the equipment and tasks within a single zone or multiple zones and/or groups.
- the schedule may further include a start time for activation of a report generation module reports, and trend collection and analysis modules. All of these disclosed activity and operation schedule, data collection and report generation routines may be gathered and recognized by the operations scheduler module portion of the automation control tool.
- the operations scheduler module may utilize the gathered activity and schedule information to generate a unified schedule that includes activity time lines or periods representing the duration of each activity and operation schedule as well as the data collection and report generation activity. Each of these elements or activities may be displayed relative to each other thereby providing a user with a holistic mechanism by which the operation of the building automation system may be overseen.
- the embodiments discussed are directed to tools, methods and devices for organizing, managing and controlling one or more environmental control devices, building automation components, and wireless devices configured for use within a building automation system.
- the devices and components may be BACNet, IEEE 802.15.4 / ZigBee-compliant devices such as, for example, one or more personal area network (PAN) coordinators implemented as a field panel (FPX or PXC); a full function device (FFD) implemented as a floor level device transceiver (FLNX); and a reduced function device (RFD) implemented as a wireless room temperature sensor (WRTS).
- PAN personal area network
- FDD full function device
- FLNX floor level device transceiver
- RFID reduced function device
- the devices and components identified herein are provided as an example of automation devices, building automation components, wireless devices that may be integrated and utilized within a structure; these examples are not intended to limit the type, functionality and interoperability of the devices and teaching discussed and claimed herein.
- One exemplary building automation system that may include and implement the tools, method and devices for organizing, managing and controlling one or more is the APOGEE® system provided by Siemens Industry, Inc., Building Technologies Division (hereinafter "Siemens").
- the APOGEE® system may further implement the automation control tool and operation scheduler module that interacts with and displays schedule and control information for, for example, a proprietary or Siemen's specific version of the BACnet protocol that maximizes the features and capabilities of building automation components and devices manufactured and provided by Siemens.
- the automation control tool and the integral operation scheduler module operable with the APOGEE® system may interact with and display schedules for objects and devices that operate according to a standardized version of the BACnet protocol.
- the APOGEE® system including the automation control tool and operation scheduler module provides a mechanism for integration of multiple building systems and devices from different manufacturers.
- an WRTS manufactured by Siemens may communicate data to an APOGEE® field panel (FPX or PXC) for utilization therein and/or distribution to one or more sensors, actuators, drives, and environmental control devices provided by a different manufacturer.
- FPX or PXC APOGEE® field panel
- FIG. 1 illustrates an exemplary building automation system or control system 100 that may incorporate and implement the automation control tool and method for operation scheduling as disclosed herein.
- the building automation system 100 includes a first network 102 such as an automation level network (ALN) or management level network (MLN) in communication with one or more INSIGHT® workstations 104 (individually identified as workstations 104a and 104b) in
- ANN automation level network
- MN management level network
- INSIGHT® workstations 104 individually identified as workstations 104a and 104b
- each of the field panels 106 may be a PXC Modular field panel provided by Siemens.
- the field panels 106 are programmable devices that may couple the first network 102 to a second network 1 10 such as a floor level network (FLN) and/or other environmental control devices and building automation
- the second network 1 10 may include a wired network 1 12 that connects to automation devices 1 14 (individually identified as automation devices 1 14a to 1 14n) to the field panel 106a.
- the second network 1 10 may further be coupled to a wireless mesh network 124 composed of automation devices 1 16 (individually identified as wireless automation devices 1 16a to 1 16n) through a wireless field panel 106c.
- the automation devices 1 16 may be wirelessly deployed within a room or space and in communication with an IEEE 802.15.4 (ZigBee) compatible field panel 106c deployed elsewhere within the structure.
- the automation devices 1 14 and 1 16 may be mixed or interspersed within a single room to form a plurality of mixed mode (i.e., both wired and wireless) connections to the field panels 106a and 106c.
- the building automation system 100 may further include automation devices 1 18 (individually identified by the reference numerals 1 18a to 1 18n) wirelessly deployed according to the IEEE 802.1 1 (Wi-Fi) standard to define a Wi-Fi network 124.
- the automation devices 1 18 may, in turn, communicate with the network 102 via a Wi-Fi compatible access point 108.
- the devices 1 18a to 1 18n such as, for example, temperature sensors, damper actuators, computing devices and other building automation components can be configured to wirelessly communicate information between each other and a wireless access point 108.
- the device 1 18a may communicate with other devices 1 18b to 1 18n within the Wi-Fi network 126 by sending a message addressed to an Internet Protocol (IP) address, a device alias, a media access control (MAC) address or other network identifier assigned to one or more of the automation devicesl 18a to 1 16n and the wireless access point 108.
- IP Internet Protocol
- MAC media access control
- the workstation 104a may, in one exemplary configuration, communicate with automation devices 120 (individually identified as automation devices 120a to 120n) via the field panel 106b and an RS-485 network 122. In this configuration, the workstation 104a may be in direct and/or multiplexed communication with the field panel 106b via a three or four wire network configuration.
- the workstation 104a may further include and store an exemplary automation control tool 200 configured to implement the included operation scheduler module 201 and the associated functionality discussed and disclosed herein.
- the automation control tool 200 may be stored in a memory and executed by a processor operable within the workstation 104a.
- the automation control tool 200 may utilize and exchange data, as discussed below, with the one or more of the automation devices 1 14, 1 16, 1 18 and 120.
- FIG. 2 illustrates a generalized and exemplary internal functional block diagram and configuration for the workstation 104a.
- the workstation 104a stores and executes the automation control tool 200, the operation scheduler module 201 , a schedule creation and editing module (not shown), and other algorithms and processor-executable instructions to cause the performance of any one or more of the methods or computer based functions discussed and disclosed herein.
- the workstation 104a may operate as a standalone device or may be connected to another workstation 104b, computer systems or peripheral devices via, for example the network 102.
- the workstation 104a (referred to hereinafter as the workstation 104) may operate in the capacity of either a server or a client computer in a server-client network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment.
- the workstation 104 may also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a personal digital assistant (PDA), a mobile device, a laptop computer, a desktop computer, or any other machine capable of executing the automation control tool 200.
- PC personal computer
- PDA personal digital assistant
- the workstation 104 includes a processor 202, such as, a central processing unit (CPU), a graphics-processing unit (GPU), or both.
- the processor 202 may be a component in a variety of systems.
- the processor 202 may be part of a standard personal computer or a controller.
- the processor hardware may incorporate one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data.
- the workstation 104 may include a memory 204 that can communicate with the processor 202 via a bus 206.
- the memory 204 can be divided or
- the memory 204 includes, but may not be limited to, computer readable storage media and various types of volatile and non-volatile storage media such as: random access memory; read-only memory; programmable read-only memory;
- the memory 204 includes a cache or random access memory for the processor 202. Alternatively, or in addition to, the memory 204 may be system memory that is separated and/or distinct from the processor 202.
- the memory 204 may be an external storage device or database for storing data. Examples include a hard drive, compact disc (“CD”), digital video disc (“DVD”), memory card, memory stick, floppy disc, universal serial bus (“USB”) memory device, or any other device operative to store data.
- the memory 204 is configured to store the automation control tool 200, the operation scheduler module 201 and one or more reduced data files 260a to 260n utilizable by the processor 202 to generate and implement the operation scheduler functionality as disclosed herein.
- the functions, acts or tasks illustrated in the figures or described herein may be performed by the programmed processor 202 executing the instructions such as the automation control tool 200 and the operation scheduler module 201 in connection with the information and/or data stored in the reduced data files 260a to 260n (shown as a dashed line when accessed by the processor 202.)
- the automation control routine 200 and the data from the reduced data files 260a to 260n may be loaded via the bus 206 from a storage location in the memory 204 for use by the operation scheduler module 201 .
- the functions, acts or tasks may be independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firm-ware, microcode and the like, operating alone or in combination.
- processing strategies may include multiprocessing, multitasking, parallel processing and the like.
- the workstation 104 includes a disk or optical drive unit 208 to accessibly interpret a computer-readable medium 210 on which software embodying, for example, a copy or backup of the automation control tool 200 (shown as a dashed line) or other processor-executable instructions are embedded and stored.
- the automation control tool 200 or other processor-executable instructions may, as shown in FIG. 2, reside completely, or at least partially, within the memory 204 and/or within the processor 202 during execution by the workstation 104.
- the workstation 104 may further include a display module 212 coupled to, and communicating with, a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device 212a for outputting determined information.
- a display module 212 coupled to, and communicating with, a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device 212a for outputting determined information.
- LCD liquid crystal display
- OLED organic light emitting diode
- flat panel display a flat panel display
- solid state display a solid state display
- CRT cathode ray tube
- projector printer or other now known or later developed display device 212a for outputting determined information.
- I/O input/output
- the input/output module 214 may be configured to allow a user to interact with any of the components of workstation 104.
- the input module 214 may be, for example, a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device 214a operative to interact with the display device 212a and the workstation 104.
- the workstation 104 may utilize a communication interface 218
- the networks 102, 1 10, 1 12, 122, 124 and 126 implemented in software or hardware to establish a connection with, for example, one or more of the networks 102, 1 10, 1 12, 122, 124 and 126, one or more of the input devices 214a, the display device 212a, or any other components.
- the computer-readable medium 210 be a single medium or may comprise multiple mediums such as a centralized or distributed database and/or associated caches and servers that store one or more sets of instructions.
- the term "computer- readable medium” is generally utilized to describe any medium that may be capable of storing, encoding or carrying an algorithm or set of instructions for execution by a processor or that may cause a computer system to perform any one or more of the methods or operations disclosed herein.
- the computer-readable medium 210 may include a solid-state memory such as a memory card or other package that houses one or more non-volatile readonly memories.
- the computer-readable medium 210 further includes or
- the computer-readable medium 210 may include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium.
- a magneto-optical or optical medium such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium.
- the present disclosure may be considered to include any one or more of a computer- readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
- dedicated hardware implementations such as application specific integrated circuits (ASIC), programmable logic arrays and other hardware devices, may be constructed to implement one or more of the methods described herein.
- Applications that include the apparatus and systems of various embodiments may broadly include a variety of electronic and computer systems.
- One or more embodiments described herein may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that may be communicated between and through the modules, or as portions of an application-specific integrated circuit. Accordingly, the present system may encompass software, firmware, and hardware implementations.
- the automation control tool 200 implements the operation schedule module 201 and associated functionality necessary to provide a unified interface or display for monitoring and controlling the system operations and reports of one or more of the automation devices 1 14, 1 16, 1 18 and 120.
- 200 may display reports designed and formatted years in advance to manage, for example, the operation and health of automation devices 1 14. These long-range control plans and schedules may direct one or more of the automation devices 1 14 to address seasonal changes in temperature, daylight and other long-term
- the automation control tool 200 In order to implement the desired environmental control, the automation control tool 200 generates a display via the operation scheduler module 201 to allow a user to visualize and control the ambient lighting conditions and schedules operable within the building automation system 100. In another embodiment, the automation control tool 200 and operation scheduler module
- 201 provides a mechanism by which a user may adjust and control a building HVAC control scheme.
- a user may interact with the automation control tool 200 and operation scheduler module 201 provides via the display 212a and input devices 214a to monitor and adjust the operation of one or more of the automation devices 1 14, 1 16, 1 18 and 120.
- the automation control tool 200 may generate commands and signals to implement a change or initiate an activity at one of the identified automation devices 1 14, 1 16, 1 18 and 120.
- the automation devices 1 14, 1 16, 1 18 and 120 operate to adjust and monitor the building HVAC control scheme based on the received commands and signals in order to control building automation system 100 and/or compensate for changes in the ambient temperature or weather conditions associated with typical seasonal variations.
- the building HVAC control scheme may further be adjusted or edited to compensate for sensed or detected conditions that may deviate from the expected typical seasonal variations.
- the disclosed operation schedule module 201 portion of the automation control tool 200 provides the desired functionality to organize each group of automation devices 1 14, 1 16, 1 18 and 120 into corresponding logical groupings or zones 1 to 4 (see FIG. 1 ) within the building automation system 100.
- the zones may include any combination of automation devices 1 14, 1 16, 1 18 and 120 based on, for example, physical location, manufacturer, operating system and version, or any other desired characteristic or variable.
- One or more of the zones 1 to 4 may be further combined to generate or define a group.
- the operation schedule module 201 portion of the automation control tool 200 may affect collective control and monitoring over multiple devices and groups of devices.
- the schedules organized and displayed by the disclosed operation scheduler module 201 may be based on information contained within a structured data file.
- the structured data file could include an automation device identifier, a zone and/or event indicator, a start time, and a stop time.
- the structured data file may be an extensible markup language (XML) file utilized to define and identify data for use by the operation schedule module 201 portion of the automation control tool 200.
- XML extensible markup language
- each of the exemplary automation devices 1 14a to 1 14n may include and store a corresponding structured data file 250a to 250n that contains the information, variables, and data structures necessary to operate any one of the devices.
- the field panel 106a can, in turn, store one or more reduced data files 260a to 260n that represent a filtered and compressed version of the structured data files 250a to 250n.
- These reduced data files 260a to 260n include the information, data and values required by the operation schedule module 201 portion of the automation control tool 200 to generate the unified schedule 300 and display (see, for example, FIG. 3).
- the data file 250n stored within, for example, the corresponding automation device 1 14n is a full and detailed structured data file containing device thresholds, controller constants, data tables, addressing
- the full data file 250n may further include the schedule identifier, the zone and/or event indicator, the start time, and the stop time as well as any other data, information and fields contained within the corresponding reduced data file 260n.
- the full data file 250n can cause manipulation and transmission difficulties. For example, transmission of the full data file 250n may require a large amount of network bandwidth and time to complete the transfer. The increased network utilization requirements may, in turn, degrade performance of the building automation system 100. Moreover, if the transmission time becomes too great, the communicated information and data may no longer be up-to-date causing a further degradation in the performance of the building automation system 100
- the automation control tool 200 may provide a mechanism or tool to segment and compress the full data file 250n into a reduced or compressed data file 260n for use by the operation scheduler module 201 .
- the automation control tool 200 may provide a mechanism by which specific elements, fields and sections of the full data file 250n may be selected or identified for inclusion in the reduced or compressed data file 260n.
- the reduced data file 260n can be designed and customized by a user to contain only the specific fields and inputs required for the generation of a unified schedule 300 (see FIG. 3).
- the reduced data file 260n represents a
- the automation control tool 200 can collect the information and data necessary for the execution of the operations scheduler module 201 without degrading the communication performance of the entire building automation system 100.
- the reduced data files 260a to 260n can be retrievably stored in each of the field panels 106 to thereby eliminate the need for the automation control tool 200 and/or the operations scheduler module 201 to directly request schedule information from each of the automation devices 1 14, 1 16, 1 18 and 120.
- the automation control tool 200 may be configured to extract specific fields and information from the structured data file 250 relating to the automation device identifier, the zone and/or event indicator, the start time, and the stop time for each of the one or more of the automation devices 1 14, 1 16, 1 18 and 120.
- the start and stop times can, in turn, be utilized by the operations scheduler module 201 determine an operation or operating window that reflect the time period over which an given device or group of device are active to control or monitor aspects of the building automation system 100. Because the automation control tool 200 only extracts and processes the specific fields necessary to generate the unified schedule 300, the structured data files 250 can be formatted according to a variety of standard and proprietary BACnet communication protocols without increasing the likelihood of a data conflict resulting from missing, corrupt and/or mislabeled information.
- Removal of extraneous information and data by the automation control tool 200 effectively compresses the amount of information required for transmission via the networks 102, 1 10, 1 12, 122, 124 and 126.
- additional compression may be achieved by substituting repetitive information with a
- the common structure and names may be ignored and the remaining information and data that defines the scheduling information can be communicated from the field panel 106 for reconstruction by the operations scheduler module 201 portion of the automation control tool 200.
- reduced data files 260 associated with each of the automation devices 1 18 may be stored in a queue defined within the access point 108.
- the reduced data files 260 associated with the automation devices 1 18 can be communicated via the network 102 to one or more of the workstations 104a and 104b for storage.
- the automation control tool 200 can query one or more of the field panels 106a to 106c and the access point 108 identified as a central collection point(s) in order to retrieve the information and data contained within the reduced data files 260 for use by the operations scheduler module 201 .
- FIG. 3 illustrates an implementation of the display generated by the operations scheduler module 201 portion of the automation control tool 200. In particular, FIG.
- the unified schedule 300 displays an exemplary multipaneled schedule in which each of the panels 302 to 314 corresponding to a day of the week (e.g., Monday, Tuesday, etc.)
- the exemplary multipaneled view of the unified schedule 300 displays a weekly view detailing the operations and actions performed by one or more of the automation devices 1 14, 1 16, 1 18 and 120.
- the exemplary multipaneled view of the unified schedule 300 further displays the data collection routines and reports generated by the operation scheduler module 201 .
- panel 304 illustrates schedules 304a to 304d indicating that four reports and/or collection routines are be initiated on Tuesday, August 31 , 2010.
- the operation scheduler module 201 generates a timeline 316 that illustrates, relative to each other, when the schedules 304a to 304d corresponding to each of the reports and/or collection routines will occur on a given day.
- the panel 304 of the unified schedule 300 illustrates via schedule 304d that a trend collection routine is initiated at approximately 0900.
- the panel 304 further illustrates via schedules 304b and 304c that two additional trend collection routines are initiated at approximately 1800.
- the schedule 304a indicates that a trend collection report 304a is generated at approximately 2200 after each of the preceding trend collection routines 304b to 304d have been completed and the data or information stored in the memory 204.
- Schedules 304e and 304f similarly indicate the operational or activity period of a device and zone, respectively, operating within the building automation system 100.
- the trend collection and report routines 304a to 304d may collect performance information and data related to two automation devices or zones controlled by schedules 304e and 304f.
- the operation schedule 304e may control the activity implemented by one of the automation components 1 14, 1 16, 1 18 and 120.
- the operation schedule 304e indicates that the controlled device is active from
- the schedule 304f may similarly control the activity of a logical group of automation devices 1 14, 1 16, 1 18 and 120 from approximately 0645 to 1645.
- the timeline 316 generated and assembled by the operation schedule module 201 portion of the automation control tool 200 provides a graphical representation of the start and stop times associated with each of the schedule 304a to 304d. Each time periods is represented as a linear bar that corresponds to the duration of each process and routine over a common time frame (e.g., a 24 hour time period representing Tuesday, August 31 , 2010).
- the unified schedule 300 generated by the operations scheduler module 201 portion of the automation control routine 200 can provide a visual mechanism through which the activity of any one of the automation devices 1 14, 1 16, 1 18 and 120 can be compared, controlled and monitored relative to other devices and schedules.
- FIG. 4 illustrates an enlarged single-day view of a portion of the unified schedule 300 related to the panel 304 (e.g., Tuesday, August 31 , 2010).
- the panel 304 includes: a category icon 400, a start time 402, an end time 404, a schedule name or identifier 406, the timeline 316 and a mode 408.
- the category icon 400 provides a visual indicator or icon representing the schedule type recognized by the operation schedule module 201 portion of the automation control tool 200 and displayed by the unified schedule 300.
- Schedule types may include: proprietary schedules that control and direct the equipment and reporting operations associated with a zone or group; and standard BACnet schedule objects which define or establish a periodic schedule of events that may repeat within a range of dates.
- BACnet schedule objects (indicated by the icon corresponding to the reference numeral 510) control and define when equipment and reporting operations are to be conducted during normal days of a week as well as exception days.
- Exceptions (indicated by the icon corresponding to reference numeral 512) provide the ability to modify and replace a single instance or day of a reoccurring schedule. For example, a schedule may be setup to run Monday through Friday 8:00 AM to 5:00 PM. However, when a holiday occurs during the week an exception or override may be used to implement a holiday schedule.
- An override (indicated by the icon corresponding to the reference numeral 514) may be used in place of an exception (see icon 512) to replace a portion of a schedule such as a particular operation or task. In effect, an override may be utilized to replace one of the schedules 304a to 304d (see FIG. 3) will an alternate schedule on one or more desired days or time periods represented by the panels 302 to 314.
- a zone icon (indicated by the reference numeral 500) may represent one or more of the logical grouping of one or more of the automation devices 1 14, 1 16, 1 18 and 120 in the zones 1 to 4 (see FIG. 1 ).
- Multiple zones 1 to 4 representing, for example, automation devices deployed on different floors within a structure can be further grouped or combined into a group (corresponding to an icon indicated by the reference numeral 502).
- execution or activation of the schedule associated with the group 502 may be used to control the lighting and temperature throughout an entire structure. The execution and activation may be determined according to a start stop time optimization (SSTO) algorithm (indicated by the icon corresponding to reference numeral 508).
- SSTO start stop time optimization
- An exemplary SSTO algorithm or operation automatically determines the best start time for equipment operating within one of the zones 1 to 4. In one example, if the schedule states that the room needs to be 70 F at 8:00AM, the SSTO algorithm will determine the optimum start time to ensure that the room is at the desired temperature at the specified time.
- Other represented schedule types could include reports (indicated by the icon corresponding to reference numeral 504) and trend collections (indicated by the icon corresponding to reference numeral 506) that indicate when data is to be collected and/or correlated by the automation control tool 200 and the building automation system 100.
- reports indicated by the icon corresponding to reference numeral 504
- trend collections indicated by the icon corresponding to reference numeral 506
- the functions, capabilities and type of a given schedule 304a to 304f can be visually represented within the unified schedule 300 generated by the operation schedule module 201 .
- the indicated start and stop times 402 and 404 identify how long a given action or control operates for each zone or group named or listed by the schedule name or identifier 406.
- the timeline 316 provides a visual indication of the duration between the identified start and stop times 402 and 404. If the schedule type is a report (see icon 504) or trend collection routine (see icon 506), then the start time 402 is used to initiate the report generation and a stop time 404 is not necessary. When a report or trend collection routine is indicated, the timeline 316 simply identifies the point in time when the report generation starts but provides no indication of how long the reporting process takes to complete.
- the operation scheduler module 201 portion of automation control tool 200 may configure each panel 302 to 314 (or any other desired number of panels) to display the information within each of the reduced data files 260 in daily, weekly, monthly or yearly, etc. views by comparing the schedule data or information to a defined date range. If the schedule is determined to fall within the date range displayed by the operations scheduler, then the automation control tool 200 extracts the appropriate schedule data from the reduced data file 260 for display in a user accessible manner as illustrated in the exemplary unified schedule shown in FIG. 3. In other embodiments, the schedule data may be displayed as a flowchart, a horizontal linear format as a list of event times and/or durations, or in any other desired format. FIG.
- the unified schedule 600 includes a number of schedules 602a to 602g operable over multiple days 604a to 604g.
- the start times for a report generation or data collection process controlled by one or more of the schedule 602a to 602g is indicated with a hash mark 606.
- the operational or activity period corresponding to a device or group of devices 1 14, 1 16, 1 18 and 120 is indicated by a time line 316.
- the disclosed automation control tool 200 and the operation scheduler module 201 may be configured to receive schedule or operation information contained within the reduced data file 260 relating to each of the automation devices 1 14, 1 16, 1 18 and 120 deployed within the building automation system 100.
- the reduced data files may be retrievably stored at the field panels 106 deployed throughout the structure and accessible via one or more of the networks 102, 1 10, 1 12, 122, 124 and 126.
- the received schedule or operation information contained in each of the reduced data files 260 may be provided by an automation device 1 14, 1 16, 1 18 and 120 formatted and operating according to a different building automation format and/or
- the disclosed automation control tool 200 and the operations scheduler provides a mechanism by which the building automation format and/or communication protocol may be stripped away and filtered out to generate a commonly formatted reduced data file 260 for each of the automation devices 1 14, 1 16, 1 18 and 120.
- the commonly formatted reduced data files 260 allow for common, centralized editing or management of the schedule and operation information by the automation control tool 200 and the operations schedule.
- connection to are defined to mean components arranged to directly or indirectly exchange information, data and commands through one or more intermediate components.
- the intermediate components may include both hardware and software based components.
- operatively coupled is defined to mean two or more devices configured to share resources or information either directly or indirectly through one or more intermediate components.
- the disclosed devices, systems and methods are highly adaptable and configurable.
- the flexible nature of the disclosed devices, systems and methods allow for a wide variety of
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Human Computer Interaction (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Testing And Monitoring For Control Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Computer And Data Communications (AREA)
- General Factory Administration (AREA)
- Selective Calling Equipment (AREA)
Abstract
Description
Claims
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201180058253.9A CN103238309B (en) | 2010-12-03 | 2011-12-05 | Operation scheduler for building automation system |
NZ61134811A NZ611348A (en) | 2010-12-03 | 2011-12-05 | Operation scheduler for a building automation system |
MX2013006231A MX2013006231A (en) | 2010-12-03 | 2011-12-05 | Operation scheduler for a building automation system. |
CA2819695A CA2819695C (en) | 2010-12-03 | 2011-12-05 | Operation scheduler for a building automation system |
KR1020137017333A KR101931833B1 (en) | 2010-12-03 | 2011-12-05 | Operation scheduler for a building automation system |
BR112013015746-1A BR112013015746B1 (en) | 2010-12-03 | 2011-12-05 | BUILDING AUTOMATION CONTROL SYSTEM AND COMPUTER IMPLEMENTED METHOD TO MANAGE AND CONTROL MULTIPLE AUTOMATION COMPONENTS |
AU2011336257A AU2011336257B2 (en) | 2010-12-03 | 2011-12-05 | Operation scheduler for a building automation system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US41937010P | 2010-12-03 | 2010-12-03 | |
US61/419,370 | 2010-12-03 | ||
US13/310,484 | 2011-12-02 | ||
US13/310,484 US9338238B2 (en) | 2010-12-03 | 2011-12-02 | Operation scheduler for a building automation system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012075485A1 true WO2012075485A1 (en) | 2012-06-07 |
Family
ID=46162971
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2011/063268 WO2012075485A1 (en) | 2010-12-03 | 2011-12-05 | Operation scheduler for a building automation system |
Country Status (9)
Country | Link |
---|---|
US (1) | US9338238B2 (en) |
KR (1) | KR101931833B1 (en) |
CN (1) | CN103238309B (en) |
AU (1) | AU2011336257B2 (en) |
BR (1) | BR112013015746B1 (en) |
CA (1) | CA2819695C (en) |
MX (1) | MX2013006231A (en) |
NZ (1) | NZ611348A (en) |
WO (1) | WO2012075485A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200232671A1 (en) * | 2017-07-14 | 2020-07-23 | Daikin Industries, Ltd. | Device control system |
Families Citing this family (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2983982B1 (en) * | 2011-12-12 | 2014-02-07 | Somfy Sas | FACTORIZATION OF SCENARIOS |
EP2668843A1 (en) | 2012-05-31 | 2013-12-04 | S-Rain Control A/S | A two-wire controlling and monitoring system for in particular irrigation of localized areas of soil |
US9100397B2 (en) * | 2012-07-23 | 2015-08-04 | Honeywell International Inc. | BACnet MS/TP automatic MAC addressing |
US9467500B2 (en) | 2012-08-09 | 2016-10-11 | Rockwell Automation Technologies, Inc. | Remote industrial monitoring using a cloud infrastructure |
US9253054B2 (en) | 2012-08-09 | 2016-02-02 | Rockwell Automation Technologies, Inc. | Remote industrial monitoring and analytics using a cloud infrastructure |
US20140274181A1 (en) * | 2013-03-15 | 2014-09-18 | Rosemount Inc. | Resource optimization in a field device |
WO2015020975A1 (en) * | 2013-08-05 | 2015-02-12 | Ameer Sami | System and method for automating electrical devices at a building structure |
US10208947B2 (en) | 2014-03-26 | 2019-02-19 | Rockwell Automation Technologies, Inc. | Cloud-level analytics for boiler networks |
US9614963B2 (en) | 2014-03-26 | 2017-04-04 | Rockwell Automation Technologies, Inc. | Cloud-based global alarm annunciation system for industrial systems |
US9971317B2 (en) | 2014-03-26 | 2018-05-15 | Rockwell Automation Technologies, Inc. | Cloud-level industrial controller loop gain tuning based on industrial application type |
US10095202B2 (en) * | 2014-03-26 | 2018-10-09 | Rockwell Automation Technologies, Inc. | Multiple controllers configuration management interface for system connectivity |
US9886012B2 (en) | 2014-03-26 | 2018-02-06 | Rockwell Automation Technologies, Inc. | Component factory for human-machine interface migration to a cloud platform |
US9825949B2 (en) | 2014-03-26 | 2017-11-21 | Rockwell Automation Technologies, Inc. | Device authentication to facilitate secure cloud management of industrial data |
US9843617B2 (en) | 2014-03-26 | 2017-12-12 | Rockwell Automation Technologies, Inc. | Cloud manifest configuration management system |
US9838476B2 (en) * | 2014-03-26 | 2017-12-05 | Rockwell Automation Technologies, Inc. | On-premise data collection and ingestion using industrial cloud agents |
US9866635B2 (en) * | 2014-03-26 | 2018-01-09 | Rockwell Automation Technologies, Inc. | Unified data ingestion adapter for migration of industrial data to a cloud platform |
US10048670B2 (en) * | 2014-05-08 | 2018-08-14 | Beet, Llc | Automation operating and management system |
US10089313B2 (en) * | 2015-02-19 | 2018-10-02 | Bank Of America Corporation | Conversion of data integration system files |
US10528013B2 (en) | 2016-05-13 | 2020-01-07 | Johnson Controls Technology Company | Systems and methods for interfacing with a building management system |
US10504070B2 (en) * | 2016-07-01 | 2019-12-10 | Crestron Electronics, Inc. | Building automation scheduling system and method |
US10764255B2 (en) | 2016-09-21 | 2020-09-01 | Rockwell Automation Technologies, Inc. | Secure command execution from a cloud monitoring system to a remote cloud agent |
US11327473B2 (en) | 2017-07-11 | 2022-05-10 | Rockwell Automation Technologies, Inc. | Dynamically reconfigurable data collection agent for fracking pump asset |
CN107300890A (en) * | 2017-08-10 | 2017-10-27 | 中冶赛迪工程技术股份有限公司 | A kind of continuous casting information confirmation method and system again |
US10482063B2 (en) | 2017-08-14 | 2019-11-19 | Rockwell Automation Technologies, Inc. | Modular control manifest generator for cloud automation |
US10416660B2 (en) | 2017-08-31 | 2019-09-17 | Rockwell Automation Technologies, Inc. | Discrete manufacturing hybrid cloud solution architecture |
US11561521B2 (en) * | 2018-01-30 | 2023-01-24 | Johnson Controls Tyco IP Holdings LLP | Building management system with instant feedback on configuration |
US11005678B2 (en) * | 2018-05-18 | 2021-05-11 | Alarm.Com Incorporated | Machine learning for home understanding and notification |
US10830479B2 (en) | 2018-05-18 | 2020-11-10 | Johnson Controls Technology Company | HVAC zone schedule management systems and methods |
US10992492B2 (en) | 2018-05-18 | 2021-04-27 | Objectvideo Labs, Llc | Machine learning for home understanding and notification |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2005091218A2 (en) * | 2004-03-16 | 2005-09-29 | Icontrol Networks, Inc | Premises management system |
US20080222565A1 (en) * | 2007-01-29 | 2008-09-11 | Johnson Controls Technology Company | Task focused user interface systems and methods for building automation systems |
WO2008141356A1 (en) * | 2007-05-21 | 2008-11-27 | Honeywell International Inc. | Systems and methods for scheduling the operation of building resources |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2658836B2 (en) * | 1993-11-18 | 1997-09-30 | 日本電気株式会社 | Group work support system |
US9325573B2 (en) * | 2008-12-09 | 2016-04-26 | Schneider Electric Buildings Ab | Building control system |
-
2011
- 2011-12-02 US US13/310,484 patent/US9338238B2/en active Active
- 2011-12-05 BR BR112013015746-1A patent/BR112013015746B1/en active IP Right Grant
- 2011-12-05 MX MX2013006231A patent/MX2013006231A/en unknown
- 2011-12-05 KR KR1020137017333A patent/KR101931833B1/en active IP Right Grant
- 2011-12-05 CN CN201180058253.9A patent/CN103238309B/en active Active
- 2011-12-05 WO PCT/US2011/063268 patent/WO2012075485A1/en active Application Filing
- 2011-12-05 AU AU2011336257A patent/AU2011336257B2/en active Active
- 2011-12-05 CA CA2819695A patent/CA2819695C/en active Active
- 2011-12-05 NZ NZ61134811A patent/NZ611348A/en unknown
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2005091218A2 (en) * | 2004-03-16 | 2005-09-29 | Icontrol Networks, Inc | Premises management system |
US20080222565A1 (en) * | 2007-01-29 | 2008-09-11 | Johnson Controls Technology Company | Task focused user interface systems and methods for building automation systems |
WO2008141356A1 (en) * | 2007-05-21 | 2008-11-27 | Honeywell International Inc. | Systems and methods for scheduling the operation of building resources |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20200232671A1 (en) * | 2017-07-14 | 2020-07-23 | Daikin Industries, Ltd. | Device control system |
EP3654174A4 (en) * | 2017-07-14 | 2021-08-18 | Daikin Industries, Ltd. | Equipment control system |
EP4036710A1 (en) * | 2017-07-14 | 2022-08-03 | Daikin Industries, Ltd. | Air conditioning management system |
EP4036709A1 (en) * | 2017-07-14 | 2022-08-03 | Daikin Industries, Ltd. | Environment control system |
EP4040288A1 (en) * | 2017-07-14 | 2022-08-10 | Daikin Industries, Ltd. | Home system |
EP4040289A1 (en) * | 2017-07-14 | 2022-08-10 | Daikin Industries, Ltd. | Device control system |
EP4040287A1 (en) * | 2017-07-14 | 2022-08-10 | Daikin Industries, Ltd. | Indoor environment control system |
US11680722B2 (en) | 2017-07-14 | 2023-06-20 | Daikin Industries, Ltd. | Device control system |
Also Published As
Publication number | Publication date |
---|---|
CA2819695A1 (en) | 2012-06-07 |
KR20130138814A (en) | 2013-12-19 |
BR112013015746B1 (en) | 2022-01-04 |
CN103238309A (en) | 2013-08-07 |
US20120143378A1 (en) | 2012-06-07 |
AU2011336257A1 (en) | 2013-06-13 |
US9338238B2 (en) | 2016-05-10 |
CA2819695C (en) | 2019-02-26 |
BR112013015746A2 (en) | 2019-12-10 |
AU2011336257B2 (en) | 2016-05-26 |
CN103238309B (en) | 2016-11-09 |
KR101931833B1 (en) | 2018-12-21 |
NZ611348A (en) | 2015-04-24 |
MX2013006231A (en) | 2013-07-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2819695C (en) | Operation scheduler for a building automation system | |
Domingues et al. | Building automation systems: Concepts and technology review | |
US20210014079A1 (en) | System and method for remote monitoring and controlling of building automation devices | |
US8229577B2 (en) | Distributed historian architecture and interfaces | |
US8965931B2 (en) | Distributed historian architecture | |
CN1755564B (en) | Enabling object oriented capabilities in automation systems | |
US7870090B2 (en) | Building automation system date management | |
US7742833B1 (en) | Auto discovery of embedded historians in network | |
US7917232B2 (en) | Building automation system data management | |
US8055386B2 (en) | Building automation system data management | |
US7930261B2 (en) | Historians embedded in industrial units | |
US20070142941A1 (en) | Historian module for use in an industrial automation controller | |
US20070055759A1 (en) | Building automation system data management | |
CA2996130A1 (en) | Building automation system data management | |
KR20120070653A (en) | Apparatus for processing user interface and build database for building information monitoring in a remote building control system and method thereof | |
US8448065B2 (en) | System and method for the editing and accessing real-time OPC data with text-based tags | |
Pandharipande et al. | IoT lighting: Towards a connected building eco-system | |
Saari et al. | Data collector service-practical approach with embedded linux | |
US20220253047A1 (en) | Methods, systems and data structures for optimizing parameter data retrieval from devices in a control system | |
Pittumbur | Front end development for building automation systems using JavaScript Frameworks | |
WO2023137074A1 (en) | Systems and methods for connecting, remotely monitoring and controlling entity systems | |
Teich et al. | Approach to develop innovative services through service networks by using ubiquitous infrastructures | |
WO2023248074A1 (en) | Infrastructure management system | |
Amft | D1. 1b: State of the art review |
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: 11813465 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2819695 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2013/006231 Country of ref document: MX |
|
ENP | Entry into the national phase |
Ref document number: 2011336257 Country of ref document: AU Date of ref document: 20111205 Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20137017333 Country of ref document: KR Kind code of ref document: A |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11813465 Country of ref document: EP Kind code of ref document: A1 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112013015746 Country of ref document: BR |
|
ENPW | Started to enter national phase and was withdrawn or failed for other reasons |
Ref document number: 112013015746 Country of ref document: BR Free format text: PEDIDO RETIRADO EM RELACAO AO BRASIL, TENDO EM VISTA A NAO ACEITACAO DA ENTRADA NA FASE NACIONAL FACE A INTEMPESTIVIDADE, POIS O PRAZO PARA A REFERIDA ENTRADA EXPIRAVA EM 03/06/2013(30 MESES CONTADOS DA DATA DE PRIORIDADE) E A ENTRADA SO OCORREU EM 04/06/2013. |
|
ENPZ | Former announcement of the withdrawal of the entry into the national phase was wrong |
Ref document number: 112013015746 Country of ref document: BR Free format text: ANULACAO DA PUBLICACAO CODIGO 1.2 NA RPI NO 2385 DE 20/09/2016, POR TER SIDO INDEVIDA. SALIENTA-SE QUE A DATA DE ENTRADA NA FASE NACIONAL FOI CADASTRADA ERRONEAMENTE, O QUE MOTIVOU A RETIRADA POR INTEMPESTIVIDADE. |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01E Ref document number: 112013015746 Country of ref document: BR Free format text: SOLICITA-SE APRESENTAR NOVAS FOLHAS REFERENTES AOS DESENHOS DO PEDIDO, COM OS SEUS TEXTOS TRADUZIDOS E SEM OS NUMEROS DE WO/PCT NO CABECALHO DAS FOLHAS. |
|
ENP | Entry into the national phase |
Ref document number: 112013015746 Country of ref document: BR Kind code of ref document: A2 Effective date: 20130603 |