Horticultural Lighting Scenario Management System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for managing horticultural lighting scenarios lack the ability to share, search, and classify lighting scenarios effectively between users, as they do not allow for the acquisition of runtime data generated during execution, limiting user selection and trading of suitable lighting scenarios.
Innovation Solution
A system comprising a horticultural lighting scenario data storage, a publishing module for deploying lighting scenarios, a runtime data acquisition module for storing execution data, a search module for identifying matching scenarios, and a trading module for enforcing trading policies, along with a classification engine for categorizing scenarios based on similarities, enables sharing, searching, and trading of lighting scenarios.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If lighting scenarios are exported to horticultural light sources without sharing capabilities, then the lighting scenario can be executed on the light sources, but users cannot share, search and trade lighting scenarios with one another
Solution Approach 1:
The patent introduces a centralized server as an intermediary between users and horticultural lighting systems. This server hosts a database of lighting scenarios that users can access, search, and retrieve. The server acts as a mediator that enables scenario sharing across multiple users without interfering with the local execution capability of individual lighting systems.
Solution Approach 2:
The patent adds a network dimension to the traditionally local lighting control system. By implementing web-based interfaces and database connectivity over a network, users can access lighting scenarios from any location, transforming the system from a closed local environment to an open distributed system with enhanced sharing and collaboration capabilities.
2Device complexity
If lighting scenarios are managed without runtime data acquisition, then the system remains simple, but users cannot search, sort and classify scenarios based on execution performance
Solution Approach 1:
The patent implements feedback mechanisms where runtime data from lighting scenario executions is automatically captured, stored in the database, and made available for future searches. This feedback loop enables users to search and select scenarios based on actual performance data from previous executions, improving decision-making without significantly increasing system complexity.
Solution Approach 2:
The system performs preliminary data collection and organization by automatically capturing runtime information during scenario execution and pre-processing it for searchability. This preliminary action ensures that when users need to search for scenarios, the data is already structured and ready for efficient querying, eliminating the need for complex real-time analysis.
3Device complexity
If no trading module is implemented, then the system architecture remains simple, but users cannot trade or exchange lighting scenarios with each other
Solution Approach 1:
The server acts as a trading intermediary, managing scenario exchanges between users. The trading module on the server handles scenario requests, validates user permissions, and facilitates transfers without requiring direct peer-to-peer communication between users. This intermediary approach enables complex trading functionality while maintaining a relatively simple client-side architecture.
Solution Approach 2:
The trading system is designed to be self-service oriented, where users can independently browse, search, and request scenarios through web interfaces. The automated trading module processes these requests according to predefined rules, reducing the need for manual intervention and keeping the system architecture simple while providing versatile trading capabilities.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
A computer implemented method for managing horticultural lighting scenarios including the steps of receiving lighting scenarios and storing lighting scenario attributes thereof in a data storage; transmitting the lighting scenarios to a horticultural structure for deployment on at least one horticultural lighting apparatus; acquiring runtime data generated during the execution of the lighting scenarios and storing the runtime data on the data storage. The method also comprises: receiving search parameters relative to user defined lighting scenario attributes, generating a scenario data inquiry relative to the user defined lighting scenario attributes and querying the data storage to identify and retrieve lighting scenarios having lighting scenario attributes matching the searched parameters; and receiving a trading request for one of the retrieved lighting scenarios, retrieving the trading policies of the corresponding lighting scenario and enforcing the trading policies of the corresponding lighting scenario. A system for managing horticultural lighting scenarios is also provided.