MIDIH Specific developments Sample Clauses

MIDIH Specific developments. The platform has an option to communicate via 5g network (xxxxx://0xxxx.xx/) in the facilities of VTT. VTT IoT client. This client communicates with OCB and Beckhoff PLC. It is a proprietary component developed by VTT in another project and modified to be used in this MIDIH application.
Sample 1
AutoNDA by SimpleDocs
MIDIH Specific developments. During the experimentation at POLIMI premises, the OPC UA agent was tested and validated. The validation process allowed to define new requirements mainly related to the OPC UA session parameters being able to register variable changes in the order of 50ms. Here a short description of the most relevant parameters: • samplingInterval defines, for each monitored item, the interval used by the server to evaluate changes in the value of the variable. The actual value chosen by the server depends on the underlying hardware capabilities. • publishingInterval defines the interval that has to elapse to notify possible changes to the client. Whenever the server discovers a change in the value of a variable, this new value is stored into the queue. When publishing interval expires the entire queue is sent to the client. In this way, the client can receive even very fast changes that otherwise would not have been detected. • queueSize defines, for each monitored item, the size of the queue within which to store changes in the variable. When samples are sent to the client the queue is emptied. Moreover, it was introduced the dynamic configuration, full supporting the IDAS API, a common set of services in order to manage devices dynamically. For that reason, the user can configure the agent: • statically, creating manually or via Mapping Tool the configuration file (config.json as described in the D4.3) • dynamically, configuring devices using the common IDAS API layer. Furthermore, the Mapping Tool was enhanced. The Mapping Tool is a facilitation tool to support the manual (static) configuration. During the experimentation, it was introduced new configuration parameters for improving the filtering (in and out) and obtain a configuration file tailored to the user needs. Finally, it was increased the test coverage, improved documentation and fixed bugs in order to end the incubation period of the agent and make it an official IDAS agent in the FIWARE Catalogue.
Sample 1
MIDIH Specific developments. During the MIDIH project, a Smart Industry DAta Model was defined (XXXXX) starting from FIWARE Data Models related to the Industry domain. For that reason and in order to obtain a high level of interoperability, the FI-MIND bridge was improved, making it able to process automatically data described in standard data models. In this way, the FI-MIND bridge is ready to be “plug-and-play” for every scenario using FIWARE lane and supported FIWARE Data Models.
Sample 1
MIDIH Specific developments. The FIWARE OPC UA Agent connects the OPC UA world and the NGSI Context Broker using two libraries: on one side NodeOPCUA SDK12 is used for dialogue with devices, on the other IotAgent Node Lib13 (part of IDAS) that allows the communication with the OCB. The main functionalities of the component are: • Connect physical devices to FIWARE-based systems. Supports devices that use the OPC UA standard API and connects them to an instance of FIWARE Orion Context Broker (OCB). • Manage NGSI Context Entities. Automatically creates one Context Entity per physical connected device. Each device will be mapped as a Context Entity following some rules. Basically, the user will provide an Entity Name and an Entity Type for a given device. The Entity Type will define some named Entity Attributes. Individual fields of an OPC UA device’s AddressSpace will be mapped to specific Entity Attributes of the matching Entity Type. The agent could provide a graphical tool in order to facilitate the user experience during the addresses configuration; in this way the configuration of the agent should run easily and intuitively. Fields can have the following different behaviors: • Active attributes. Fields that are pushed from the device to the Agent. This field’s changes will be sent to the Context Broker as updateContext requests over the device entity. • Lazy attributes. Some sensors will be passive and will wait for the Agent to request for data. For those fields, the Agent will register itself in the Context Broker as a Context Provider (for all the lazy fields of that device), so if any component asks the Context Broker for the value of that sensor, its request will be redirected to the Agent. Updates over this field will be transformed into commands over the device by the Agent. 12 xxxx://xxxx-xxxxx.xxxxxx.xx/ 13 xxxxx://xxxxxx.xxx/telefonicaid/iotagent-node-lib • Commands: In this case, the interaction will begin by setting an attribute in the device's entity, for which the IoT Agent will be registered as Context Provider. The IoT Agent will return an immediate response to the Context Broker and will be held responsible of contacting the device to perform the command itself, updating special status and info attributes in the entity as soon as it has any information of the command progress. It is worth to notice that firstly the implementation will focus on active attributes, since they fit the needs to implement a publish/subscribe model. Further developments (currently out of ...
Sample 1
MIDIH Specific developments. The MIDIH MindSphere Custom Agent comprises several developments that will allow the MIDIH platform interoperate with commercial solutions. For this purpose, the overall workflow and the components to achieve interoperability has been identified, and then it has proceeded to the implementation. The functionalities provided by the component are: - connect IoT and OPC UA devices to FIWARE-based systems - capture data from these devices - preprocess the collected data in order to clean and detect incorrect data before transforming it into NGSI Context Entities - Publish this information in a Message Broker, the Orion Context Broker (RabbitMQ) - retrieve the information and map it with the aspects (variables) defined for the specific Asset (device) in MindSphere - inject them into the MindSphere for further analysis. In order to retrieve the information from the Message Broker (RabbitMQ), translate this information to the MindSphere data models and inject them into MindSphere, the MindSphere Custom Agent Connector has been developed from scratch. This component is responsible for acting as an intermediary between the MIDIH platform and MindSphere, and to integrate the connectivity library provided by Siemens, the MindConnect LIB.
Sample 1
MIDIH Specific developments. The main functions of the MIDIH Collaboration Portal have been decomposed in the following Docker containers and configurations (even if in the future releases the decomposition could change): • Docker containers o portal: this container implements the core PORTAL application and the related data documents that are persisted in a specific docker volume. o mariadb: this container implements the DBMS storage, namely MariaDB6, used by the portal container to store its data and configurations; this container make use of docker volumes for ensure data persistence. o libreoffice: this container implements a headless LibreOffice7 service used by the portal container to convert documents (e.g. from .doc to .pdf).
Sample 1

Related to MIDIH Specific developments

  • Economic Development 1. The Parties aim to promote balanced economic growth, poverty reduction and the reduction of social-economic disparities.

  • Staff Development ‌ The County and the Association agree that the County retains full authority to determine training needs, resources that can be made available, and the method of payment for training authorized by the County. Nothing in this subsection shall preclude the right of an employee to request specific training.

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Curriculum Development This includes the analysis and coordination of textual materials; constant review of current literature in the field, some of which are selected for the college library collection, the preparation of selective, descriptive materials such as outlines and syllabi; conferring with other faculty and administration on curricular problems; and, the attendance and participation in inter and intra-college conferences and advisory committees.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Project Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement.

  • Design Development An interim step in the design process. Design Development documents consist of plans, elevations, and other drawings and outline specifications. These documents will fix and illustrate the size and character of the entire project in its essentials as to kinds of materials, type of structure, grade elevations, sidewalks, utilities, roads, parking areas, mechanical and electrical systems, and such other work as may be required.

  • PHASED DEVELOPMENT 15.1 The Seller reserves to itself, and to its successors in title as Developer, all such rights as are provided for in section 25 of the STA, to erect and complete a phased development on the Land from time to time, but no later than 15 (fifteen) years from the date of opening of the Sectional Title Register, for its personal account.

  • Workforce Development MPC’s technical training program is having a major impact in the region. Online modules, short courses, webinars, and on site/videoconferencing events are reaching state and local transportation department employees and tribal transportation planners. By harnessing the capabilities of the four LTAP centers located at the MPC universities and the multimedia capabilities of the Transportation Learning Network (which was founded and is partly funded by MPC) more than 76 technical training events were offered in the second half of 2015. These training modules and short courses are critical to transportation agencies that need to improve or renew the skills of engineering technicians and other frontline workers. Many MPC courses or training events result in the certification of workers. Even when certification is not required, TLN’s online learning management systems allow employees and employers to set learning goals and monitor progress towards these goals. MPC is making another major impact in workforce development. Altogether, 57 graduate students are working on MPC research projects under the tutelage of faculty researchers. These graduate students represent the researchers and technical analysts of tomorrow. Without the MPC program and the stipend funds that it provides, these students may not be specializing in transportation; but, instead would be seeking career opportunities in other fields. The MPC research program allows faculty to mentor graduate students while allowing the students to work on projects for federal and state transportation agencies—thereby, gaining valuable practical experience.

  • Faculty Development Faculty who develop and/or teach Distance Education courses shall be provided with reasonable technical support and opportunities for Faculty development, consistent with the needs of the Faculty and availability of Board resources and services for that purpose. In the event that a Faculty member develops and/or teaches a Distance Education course for the first time, the Faculty member shall receive reasonable and appropriate professional development and technical support assistance, consistent with the needs of the Faculty and availability of Board resources and services for that purpose. In instances of succeeding assignments to teach Distance Education courses, the Faculty member is expected to demonstrate a level of technical competence sufficient to teach the course. Ongoing technical support assistance may be available to Faculty who teach succeeding offerings of the same course.

Time is Money Join Law Insider Premium to draft better contracts faster.