Method and system for designing human-based lighting

Abstract

A method (10) for designing human-induced lighting (HCL) for illuminating a space is provided. The method comprises providing (25) usage related information (26) to a floor plan of the space, searching (30) a database of historical lighting schemes based on the floor plan to find a scheme matching the space. The method further comprises extracting (35) a layout method from the lighting scheme matching the space, searching (40) a database of lighting devices, and selecting from the lighting devices a lighting device available for the space and layout. The method further comprises simulating (45) installation of the lighting device into the space based on the layout and calculating (50) lighting data, searching for a database of lighting criteria and checking (55) whether the calculated lighting data complies with applicable lighting criteria. The method further comprises generating (60) an HCL lighting plan if the check shows that the calculated lighting data complies with the applicable lighting criteria.

Description

Technical Field

[0001] The technical field of the present application generally relates to lighting systems. In particular, the present disclosure relates to methods and systems for designing human factors lighting (HCL) for illuminating a space. Background Art

[0002] There are known human centric lighting systems that are designed to provide lighting based on the circadian rhythm, such as the so-called melanopic equivalent daylight illuminance (MEDI).

[0003] Human Factors Illumination (HCL) is a field of illumination that has been studied for decades. In known systems, many factors that may affect circadian rhythms are not fully considered. Perhaps in part due to the complex dependence of circadian rhythms on many parameters, formal approaches are often used in which lighting design and light regulation are based primarily on system characteristics (such as the system's light curve or control options) and less on the individual biorhythms of the target application or target group. An additional challenge for lighting designers is compliance with HCL standards. Organizations such as CIE, UL, WELL, CEN, and DIN have begun to quantify and evaluate design standards for human factors lighting (HCL). Designers incorporate these standards into their designs, which requires consideration and calculation of several new parameters. Due to the repetitive nature of the standards, even professional designers often lack the time and energy to complete HCL designs, let alone semi-professional lighting professionals. Summary of the invention

[0004] The object of the present application is to provide a method for designing standard-compliant human centric lighting that better takes into account the individual characteristics of the target application and the target user group.

[0005] According to a first aspect, a method for designing human centric lighting (HCL) for illuminating a space is provided. The method comprises providing usage related information to a floor plan of the space. Basically, the space can be any type of functional space, such as an office space, a living space, a production workshop, or a space with mixed functions. The floor plan and the usage related information can be provided specifically via a user interface. The usage related information can specifically include usage conditions, usage targets, and target physiological characteristics of a user group of a target group.

[0006] The method includes searching a database of historical lighting plans based on the floor plan to find a plan that matches the space, and extracting a layout method from the lighting plan that matches the space.

[0007] The method also includes searching a lighting device database and selecting from the lighting devices a lighting device that is available for the space and layout.The lighting device or luminaire database may include substantially all luminaires that meet the HCL original licensing criteria.

[0008] Taking into account beam angle and space type, lighting equipment selection can include choosing luminaires, controllers, and accessories that meet the HCL requirements of the current space.

[0009] The method also includes simulating the installation of lighting devices to the space based on the layout, and calculating lighting data. Simulating the installation of the lighting devices may include generating a scene specifically via a scene generation module, which generates the most suitable scene based on the current user situation and physiological characteristics. Simulating the lighting of the lighting devices may also include modeling the lighting, specifically modeling the lighting in a modeling and output module.

[0010] Calculations of lighting data can be performed in the HCL Optical Auto Calculation module. Calculations can include, but are not limited to, eye level and angle illuminance calculations, table illuminance calculations, space illuminance calculations, glare calculations, and glare direction calculations.

[0011] The method also includes searching a lighting standards database or HCL optical standards library, which includes, but is not limited to, eye level and angle illuminance, desktop illuminance, wall surface reflected illuminance, glare values, and glare directions.

[0012] The method further comprises checking whether the calculated lighting data complies with applicable lighting standards or specifications. The method further comprises generating an HCL lighting plan if the checking shows that the calculated lighting data complies with applicable lighting standards.

[0013] Due to the floor plan Figure 1 The method allows comprehensive consideration of usage-related information, such as usage scenarios, usage goals, and target physiological characteristics of user groups, to generate HCL lighting solutions.

[0014] In addition, an HCL lighting plan or HCL design can be automatically generated, in which usage-related information is appropriately considered. Specifically, considering the beam angle and space type, luminaires, controllers, and accessories that meet the HCL requirements of the current space are automatically selected. In addition, the compliance of the calculated lighting data is checked before the HCL lighting plan is generated, ensuring that the generated lighting plan meets the applicable standards. Specifically, the method can ensure that the eye-level lighting is suitable for the physiological characteristics and position of the user group, and the HCL luminaires and lighting curve schemes are suitable for the user group usage. In addition, the user does not need to be familiar with all HCL metrics or repeatedly adjust luminaire selections and schemes to meet the complete HCL scheme. In addition, the entire process including providing luminaires, controllers, and scene schemes is automatically completed at one time.

[0015] The use-related information may include information about functions assigned to spaces in a floor plan. Based on the assigned functions, a historical plan suitable for the assigned functions may be specifically and efficiently searched in the database.

[0016] The usage-related information may include target group-related information. By considering the target group-related information, the HCL may be specifically customized for the target user group. Specifically, the target group-related information may include the user's age. Since age may have a substantial impact on the individual's circadian rhythm, considering the user's age may better customize the HCL for the target group. Therefore, a personalized automatic HCL design may be provided.

[0017] The method may also include modifying the search criteria and repeating the step of searching for lighting devices and all subsequent steps of the method. By this iterative adjustment of the search criteria, the chance of successfully finding a suitable lighting device may be increased.

[0018] The method may include providing dynamic change data and / or maintenance factor data, and may search a database of historical lighting plans based at least in part on the dynamic change data and / or maintenance factor data. Thus, historical lighting plans associated with the dynamic change data and / or maintenance factor data may be considered when generating the HCL lighting plan.

[0019] A database of historical lighting solutions may include historical HCL design solutions and experience data. By searching in such a historical database, a large amount of knowledge and experience may be accessed when searching for a suitable solution.

[0020] The method may also include providing data on a color rendering index (CRI), a unified glare value (UGR), flicker, and / or a dynamic requirement change, and may search for lighting devices based at least in part on the CRI, UGR, flicker, and dynamic requirement data. By providing data on additional lighting parameters, the search may be further narrowed, making it easier to find a suitable lighting solution.

[0021] The method may include providing mDER (Melanopic Daylight Efficacy Ratio) and searching for lighting devices based at least in part on the mDER data. Specifically, the mDER data may be retrieved from a lighting standards database to ensure that the HCL standards for the mDER data are met.

[0022] According to a second aspect, a system for designing an HCL for irradiating a space is provided. The system includes a server having a processor, a memory unit for storing machine-readable instructions for the processor, and an interface for receiving input data and instructions from a user, the input data including a floor plan of the space with usage-related information. The server may include more than one processor and more than one memory unit. The server may be implemented at least in part as a distributed cloud server.

[0023] The machine-readable instructions include commands to the processor to perform the following operations: search a database of historical lighting plans based on the floor plan to find a plan that matches the space, and extract a layout method from the lighting plan that matches the space. The server is also configured to, that is, the machine-readable instructions also include commands to the processor to search a lighting device database for lighting devices that can be used for the space and the layout. The server is also configured to simulate the installation of lighting devices to the space based on the layout and calculate lighting data. The server is also configured to search a lighting standards database and check whether the calculated lighting data complies with applicable lighting standards. The server is also configured to generate an HCL lighting plan if the check shows that the calculated lighting data complies with applicable lighting standards.

[0024] The system thus enables automatic selection of luminaires according to the floor plan and the individual needs of the target group.

[0025] The lighting device database or library may specifically include storage data of all available lighting devices covering substantially every country and region. The lighting device or luminaire database may typically include information such as device type, device specifications, lighting parameters, IES files, and dimensional parameters such as height, width, aperture, etc. The lighting device database may also include device installation instructions, which are specifically used to generate the final installation instructions in the report. The database may also include information about the scope of application, such as luminous efficacy, HCL compatibility, and scope of application (e.g., open office, conference room, etc.). The system can use this information to determine whether the device is suitable for a given HCL space and scheme.

[0026] The lighting standards database or HCL optical standards library may include, but is not limited to, the following standards: eye level illuminance, mDER, glare values, average lux levels, maximum / minimum lux levels, side zone lux levels, uniformity, age calibration factor / space calibration factor. For fast availability, the standards may be retrieved from the cloud library and stored as a data table in the server's memory unit.

[0027] All automatically generated HCL solutions will be enforced to comply with the mandatory standards within them, and will strive to satisfy as many non-mandatory aspects as possible.

[0028] The system can include manual approval as well as automatic approval. Manual approval can involve HCL device selections that are manually entered by the designer's maintenance. These are typically custom luminaires that are customized for a specific HCL situation and are given priority during selection.

[0029] Automatic permission selects luminaires from the current folder based on broad HCL luminaire criteria. Filtering criteria include but are not limited to CRI (Color Rendering Index) and Lumen Efficacy.

[0030] Attributes such as function, space, user age, and user preferences will go through another round of screening during the HCL selection process. This will produce a list of HCL luminaire candidates that best suit the current space and user preferences.

[0031] The system may include a scene generation module for generating scenes, a modeling and output module for simulating the installation of lighting equipment, and an HCL optical automatic calculation module for calculating lighting data. The modules may be implemented in a server on a separate cloud-based server. Due to the dedicated modules, the system can be used and updated flexibly, and if necessary, only the relevant modules can be updated instead of the entire system.

[0032] Specifically, when it is sufficient to meet the optical parameters, the scene generation module can be configured to only provide HCL illuminator solutions. The scene generation module can also be configured to provide control package generation and solution generation functions in the case of supporting controllers and lighting curve adjustment. Selecting a lighting device can include selecting a controller and sensor type that best matches the HCL illuminator.

[0033] Controller selection can be based on preset luminaire types and can be done through controller mapping. In the case where a controller can control multiple luminaires, the system can automatically group the luminaires and add data to the circuit accordingly. The grouping can be performed by, but not limited to, K-means (specifically, a refined K-means method).

[0034] The scene generation module may also be configured to automatically arrange sensors based on the shape and area of ​​the current space to cover more than 90% of the space range.

[0035] After simple spatial grouping, the system can provide the most basic HCL control curve. Specifically, all luminaires can be controlled with a uniform illumination curve.

[0036] In addition to spatial relationships, luminaire grouping can also take into account the spatial attributes of functions. For example, in a typical conference room, a row of luminaires in front of the TV can be grouped separately from the rest of the lighting fixtures, thereby generating more typical office scenes such as meeting mode and rest mode. All these modes can be predefined in the policy library and are comparable to HCL requirements. In other words, for simple requirements, the system will generate HCL lighting curve default scenes while supporting the generation of fusion scenes related to functions. Scenes can be predefined by professionals and stored in the scene generation module policy library.

[0037] The HCL optical automatic calculation module may include an illuminator spatial arrangement part and an optical result calculation part.

[0038] The spatial arrangement module places lighting equipment based on the geometry of the current space, usage attributes, functional division, and placement of key lighting facilities. Lighting equipment placement is mainly based on geometric placement methods and machine learning models. Geometric placement methods can specifically include uniform distribution, binary placement, and centerline placement.

[0039] The optical result calculation module is configured to calculate the standard parameters in the above optical standard library and provide feedback on whether the mandatory standards are met. If the standards are not met, it will provide feedback to the spatial calculation module, and based on the feedback, the solution will be adjusted and recalculated until all mandatory standards are met.

[0040] In the following description, details are provided to describe the embodiments of the present specification. However, it is clear to those skilled in the art that the embodiments can be practiced without such details.

[0041] Some parts of the embodiments have similar parts. Similar parts may have the same name or similar part numbers. Where appropriate, the description of one part is applicable to another similar part by reference, thereby reducing the repetition of text without limiting the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 An exemplary table with aging correction factors for common light sources is shown,

[0043] Figure 2 An exemplary table with mDER values ​​for common light sources is shown,

[0044] Figure 3 An exemplary lighting layout plan and optical simulation results are shown.

[0045] Figure 4 Shown according to Figure 3 Vertical illumination and mEDI correction of the optically simulated eye,

[0046] Figure 5 A sample scenario for a simple case is shown,

[0047] Figure 6 A sample scenario for an advanced case is shown,

[0048] Figure 7 shows a control interface of a system according to an embodiment,

[0049] Figure 8 shows an example of an output rendered simulation,

[0050] Fig. 9 A flowchart of a method for designing HCL according to an embodiment is shown, and

[0051] Fig.10 A system structure according to an embodiment is shown. DETAILED DESCRIPTION

[0052] Figure 1 An exemplary table with aging correction factors for common light sources is shown. Such data can be stored in the HCL Optical Standards Library and can be retrieved to check the consistency of the calculated lighting data with the standards. Common light sources are listed in the left column of the table and the user age is indicated in the top row. As can be seen in the table, for all light sources, the age correction factor is strongly dependent on the user age. Such a table can be used as a lookup table for checking the consistency of the calculated lighting data with the applicable standard.

[0053] Figure 2 An exemplary table with mDER values ​​for common light sources is shown. Figure 1 Similarly, the left side contains a list of common light sources. In the top row, the mDER parameters and the corresponding units are indicated. This table can be used as a lookup table to check the consistency of the calculated lighting data with the applicable standards.

[0054] Figure 3 An exemplary lighting layout plan and optical simulation results are shown. The layout corresponds to a rectangular space with multiple distributed lighting fixtures. Figure 3 On the left side, a top view and a perspective view of the space are shown. On the right side, the simulation results are shown. Specifically, the simulation obtained the illumination distribution as indicated in the right figure. At a measurement height of 0.8m, a maximum illumination of 820.83Lux is achieved in the central area of ​​the space, and a minimum illumination of 490.93Lux is achieved in the peripheral area or corner of the space.

[0055] Figure 4 Show according to Figure 3 The vertical illumination and mEDI correction of the optical simulation of the eye. Specifically, Figure 4A table with the values ​​of the vertical illuminance at eye level (at 1.2 m) in Lux and the mEDI correction values ​​in Lux for different calculation subjects and the average value is shown.

[0056] Figure 5 A sample scenario for a simple case is shown. Specifically, Figure 5 Three examples of living spaces with typical layouts are shown. In a simple case, the lighting arrangement comprises a luminaire 1 and an occupancy daylight sensor 2. In a simple case, no controller is supported. Therefore, satisfying the optical parameters is sufficient for the HCL luminaire solution.

[0057] Figure 6 A sample scenario for an advanced case is shown. Specifically, Figure 5 Shows something like Figure 5 An example of a living space in a connected situation with controllers and sensors supporting scenes and light curves.

[0058] exist Figure 6 In the advanced case of FIG. 5 , the lighting device further comprises a luminaire 1 and an occupancy daylight sensor 2 . The lighting device further comprises a controller 3 having a high bay sensor and a control switch 4 . The luminaire 1 , the control switch 4 and the controller 3 are functionally connected to form a network 5 .

[0059] Figure 7 A control interface of a system according to an embodiment is shown. The control or operating interface is configured as a user-friendly touch screen interface. In the central area of ​​the control interface, a spatial room plan is shown, giving a good overview of the space to be irradiated. On the left, some control buttons are provided, which have pictograms for the control interface. On the right, a menu with settings is provided. The control interface can be configured as part of a server or as part of a terminal. In some embodiments, a wearable smart device is used as a terminal for providing a control interface.

[0060] Figure 8 An example of an output rendered simulation is shown. Figure 8 Specifically shown are the results of a simulation performed for a workspace with downlights arranged above a cluster of desks. Figure 8 As can be seen in the examples in , the simulation provides a very realistic picture of the lighting in the workspace.

[0061] Fig. 9 A flow chart of a method for designing a HCL according to an embodiment is shown. The method 10 starts from a start step 20 based on a light and space algorithm.

[0062] In step 25, the user provides a floor plan and functions are assigned to the spaces within the floor plan. In step 25 or in a separate step, the user also provides usage related information 26. The usage related information 26 may specifically include user age, dynamic changes, maintenance factors, etc. The usage related information may also include usage conditions, usage goals, and target physiological characteristics of the user group of the target group. By considering the target group related information, the HCL can be specifically customized for the target user group. Specifically, the target group related information may include the age of the user. Since age can have a substantial impact on the circadian rhythm of an individual, considering the age of the user can provide personalized HCL to the target group.

[0063] In step 30, a database of historical lighting plans is searched based on the floor plan to find a plan that matches the space. Step 30 may also include searching in historical HCL design plans and empirical data 31.

[0064] In step 35, a layout method is extracted from the lighting plans in the historical lighting plans that have been matched to the spaces of the floor plan.

[0065] Step 40 includes searching for lighting equipment that can be used for the space and layout. In step 40 or in a separate step, light performance requirements 41 may be included, such as CRI, UGR, flicker, dynamic changes, etc.

[0066] Step 45 includes simulating the installation of lighting devices to the space based on the layout.Step 45 may require mDER data 46 as input for performing the simulation.

[0067] In step 50, lighting data is calculated. The calculation of lighting data may include mEDI correction 51 and / or room factor correction. Specifically, mEDI data 51 may be retrieved from a lighting standards database.

[0068] In step 55, it is checked whether the calculated lighting complies with the applicable lighting standards.

[0069] If the check in step 55 shows that the calculated lighting data complies with applicable lighting standards, then in step 60 an HCL lighting plan is generated before the process ends in end step 65 .

[0070] The method 10 may further include step 70, i.e., modifying the search criteria, specifically, modifying the search conditions and device packages, and repeating the step of searching for lighting devices and all subsequent steps in the method. Steps 45, 50, 55 and 70 may be repeated until the calculated lighting data meets the applicable criteria.

[0071] Fig.10 A system structure according to an embodiment is shown.

[0072] The system 100 includes a user area 110. The user area 110 includes a server 111 as a network server, and a user interface 112 for communicating with the server 111. The user interface 112 includes a reading interface 113 and a modeling interface 114. Via the reading interface 113, a user 115 can read a search report and a project search. Via the modeling interface 114, a user 115 can create a floor plan model of a space to be illuminated. The reading interface 113 and the modeling interface 114 are connected to the network server 111 via a network browser 116.

[0073] The system 100 also includes an administrator area 117. The administrator area 117 includes an administrator interface 118. The administrator interface 118 may include a dashboard for an administrator 119. The administrator interface 118 is connected to the server 111 via a web browser 116. The web server 111 of the admin area 117 is connected to the web server 111 of the user area 110 via a web protocol. In some embodiments, both the user 115 and the administrator 119 use the same server 111.

[0074] exist Fig.10 In the embodiment of the present invention, the administrator area 110 also includes a lighting device database 120, a space modeling unit 121 or a scene generation module, a lighting report generator 122 or a modeling and output module, a lighting standard database 123 and a rule engine 124. The server 111 of the user area 110 can be connected to the optical computer 125 via an RPC (remote procedure call) connection and to the MySQL database 126 via a JDBC (Java Database Connectivity) connection. In addition, the server 111 can be connected to a mail server 127 and a cloud file directory 128 via a simple mail transfer protocol (SMTP). In Fig.10 In the embodiment of FIG. 1 , the user area 110 includes a user session database 129 connected to the server 111 .

[0075] The management area 117 comprises a maintenance module 130 connected to the MySQL database 126 and configured to ensure maintenance of standards, portfolios and the rules engine.

[0076] By means of the system 100, the method 10 according to the first aspect can be performed. Thus, after the space and usage / user information is entered in the system, a general lighting plan with HCL support can be completed with one click. This makes the system and method particularly attractive to ordinary users and light designers.

[0077] Furthermore, it is not necessary to know professional lighting design to obtain a qualified HCL plan. The approach also considers the social division of space and user image when designing HCL.

[0078] Furthermore, the method is not limited to luminaires. In fact, a complete HCL lighting solution including controllers, sensors, control groups, schematics and preset scenes can be generated with just one click.

[0079] Although at least one exemplary embodiment has been given in the above detailed description, it should be understood that there are a large number of variations. It should also be understood that one or more exemplary embodiments are only examples and are not intended to limit the scope, applicability or configuration of the present disclosure in any way. On the contrary, the above detailed description will provide a convenient road map for implementing one or more exemplary embodiments for those skilled in the art.

[0080] Reference symbols and numbers

[0081] 1 illuminator

[0082] 2 Sensors

[0083] 3 Controller

[0084] 4 Switches

[0085] 5. Network

[0086] 20 Start

[0087] 26 Use of related information

[0088] 30 Methods and Steps

[0089] 31 Historical HCL Design Schemes and Experience Data

[0090] 35 Methods and Steps

[0091] 40 Methods and Steps

[0092] 41 Optical performance requirements

[0093] 45 Methods and Steps

[0094] 46mDER data

[0095] 50 Methods and Steps

[0096] 51mEDI Calibration

[0097] 55 Methods and Steps

[0098] 60 Methods and Steps

[0099] 65 End

[0100] 70 Methods and Steps

[0101] 100 systems

[0102] 110 User Area

[0103] 111 Server

[0104] 112 User Interface

[0105] 113 Reading interface

[0106] 114 Modeling Interface

[0107] 115 users

[0108] 116 Web browsers

[0109] 117Admin Area

[0110] 118 Administrator Interface

[0111] 119 Administrator

[0112] 120 lighting equipment database

[0113] 121 Space Modeling Unit

[0114] 122 Lighting Report Generator

[0115] 123 Lighting Standards Database

[0116] 124 Rules Engine

[0117] 125 Optical Calculator

[0118] 126MySQL database

[0119] 127 Mail Server

[0120] 128 Cloud File Directory

[0121] 129 User Session Database

[0122] 130 Maintenance Module

Claims

1. A method (10) for designing human factors lighting (HCL) for illuminating a space, the method comprising: providing (25) usage-related information (26) to a floor plan of the space, searching (30) a database of historical lighting plans based on the floor plan to find a plan that matches the space, and extracting (35) a layout method from the lighting plan that matches the space, searching (40) a database of lighting devices and selecting from said lighting devices a lighting device available for said space and layout, simulating (45) installation of lighting equipment to the space based on the layout and calculating (50) lighting data, searching a lighting standards database and checking (55) whether the calculated lighting data complies with applicable lighting standards, and If the checking shows that the calculated lighting data complies with the applicable lighting standards, an HCL lighting plan is generated (60).

2. The method of claim 1, wherein the usage-related information (26) includes information about functions assigned to the spaces within the floor plan.

3. The method according to claim 1 or 2, wherein the usage-related information (26) includes target group-related information.

4. The method according to claim 1, further comprising: The search criteria are modified (70) and the step of searching (40) for lighting devices and all subsequent steps (45, 50 and 55) of the method (10) are repeated until the calculated lighting data meets the applicable criteria.

5. A method according to claim 1, wherein the method (10) further comprises providing dynamically changing data and / or maintenance factor data, and wherein a database of historical lighting schemes is searched (30) at least partly based on the dynamically changing data and / or the maintenance factor data.

6. The method according to claim 1, wherein the database of historical lighting solutions comprises historical HCL design solutions and empirical data (31).

7. The method according to claim 1, wherein the method (10) further comprises: Data on CRI, UGR, flicker and / or dynamic requirement change is provided, and wherein lighting devices are searched (40) at least partly based on the CRI, UGR, flicker and dynamic requirement change data.

8. The method according to claim 1, wherein: The method includes providing mDER data, and wherein searching (40) for lighting devices is performed based at least in part on the mDER data.

9. A system for designing human centric lighting (HCL) for illuminating a space, comprising a server (111) having a processor, a memory unit for storing machine readable instructions for the processor, and an interface (112) for receiving input data and instructions from a user (115), the input data comprising a floor plan of the space having usage related information (26), wherein the machine readable instructions comprise commands to the processor to perform the following steps: searching (30) a database of historical lighting plans based on the floor plan to find a plan that matches the space, and extracting (35) a layout method from the lighting plan that matches the space, searching (40) a lighting device database for lighting devices that can be used in the space and layout, simulating (45) installation of lighting equipment to the space based on the layout and calculating (50) lighting data, searching a lighting standards database and checking (55) whether the calculated lighting data complies with applicable lighting standards, and If the checking (55) shows that the calculated lighting data complies with the applicable lighting standards, an HCL lighting plan is generated (60).

10. The system according to claim 9, wherein: The system comprises a scene generation module (121) for generating a scene, a modeling and output module (122) for simulating the installation of lighting equipment, and an HCL optical automatic calculation module (125) for calculating lighting data.

Images