Data in Motion Processing Sample Clauses

Data in Motion Processing. The component responsible for the real-time data processing, in this context called Data-in- motion, in FIWARE is Orion Context Broker. Orion Context Broker is in charge of manage all the lifecycle of context information including queries, registrations and deletions. Furthermore, Orion Context Broker allows the consumer to subscribe itself to a context information. Xxxxx Xxxxxxx Xxxxxx will notify the consumer when any modification occurs. More information about the component can be found in the following link (xxxxx://xxxxxx- xxxxx.xxxxxxxxxxx.xx/xx/xxxxxx/). This context information is structured following the formats of FIWARE data models. These data models aim to achieve portability among applications. More information about data models can be found in the following link (xxxxx://xxx.xxxxxx.xxx/developers/data-models/).
Sample 1
AutoNDA by SimpleDocs
Data in Motion Processing. Data representation An entity represents any identified physical entity. An entity is formed by set of attributes following a data model FIWARE format. These attributes have a specific value that can be updated at any time. Orion Context Broker is in charge of create, update, retrieve and delete an entity or list of entities. Furthermore, it allows managing entities by their type, attributes or geographic position. Data isolation Orion Context Broker stores data separating it into services providing a lightweight multiservice model. We can define in which service the entities will be stored by using HTTP header 'Fiware- Service' in the request. If we don't define the service in the header, the default service '/' will be used. Orion Context Broker also supports defined scopes. From the 'Fiware-ServicePath' sent to Orion Context Broker as a header in the HTTP request, we can define the scope in which we are going to work. Those scopes can be hierarchical. Component configuration A set of options are allowed when launching the Orion Context Broker in command line for the management of the database, activating the log, managing the connection with Orion Context Broker, among others. We can see the different options in the following link (xxxxx://xxxxxx- xxxxx.xxxxxxxxxxx.xx/xx/xxxxxx/xxxxx/xxx/xxxxx.xxxx). In addition, Orion Context Broker can be launched as a Docker service. To launch it, Orion Context Broker needs to be connected to a MongoDB database, which can be added of two ways: - We can launch a MongoDB image together with Orion Context Broker from a Docker Compose. - Orion Context Broker can be launched as a docker container independently to MongoDB database. The database may be running on localhost, located in another docker container or running on a different host.
Sample 1
Data in Motion Processing. Orion Context Broker could be launched using Docker. For this, there are three possibilities: • from a Docker Compose file declaring a MongoDB container, • launching Orion Context Broker in a container connecting to a MongoDB instance independent of the container, • and building a Docker image to have more control over the Orion Context Broker container. For more information about the launch you can access the following link: Once Orion Context Broker is launched, it is possible to make a set of requests to the REST API. Some of these requests are depicted in the figure above in this section. In this diagram, a consumer can create, update or delete a subscription to Orion Context Broker. In case a consumer creates a subscription to Orion Context Broker to receive information about the creation and update of a specific type of entities, when a creation or update of an entity by a provider occurs, Orion Context Broker will send the consumer a notification with the changes. Two actors are commonly to illustrate the Orion Context Broker’s flow: consumer and provider. The provider will be in charge of create, update or delete entities. On the other side, the consumer will receive notification if its subscripted to the entities modified or can request the entities in a synchronous way through the REST API. In addition, Orion Context Broker offers the possibility of returning the response in different formats regarding the two version of OMA NGSI currently implemented.
Sample 1

Related to Data in Motion Processing

  • Transaction Processing All orders are subject to acceptance by us and by the Fund or its transfer agent, and become effective only upon confirmation by us. If required by law, each transaction shall be confirmed in writing on a fully disclosed basis and if confirmed by us, a copy of each confirmation shall be sent to you if you so request. All sales are made subject to receipt of shares by us from the Funds. We reserve the right in our discretion, without notice, to suspend the sale of shares of the Funds or withdraw the offering of shares of the Funds entirely. Orders will be effected at the price(s) next computed on the day they are received if, as set forth in the applicable Fund’s current Prospectus, the orders are received by us or an agent appointed by us or the Fund prior to the close of trading on the New York Stock Exchange, generally 4:00 p.m. eastern time (“Close of Trading”). Orders received after that time will be effected at the price(s) computed on the next business day. All orders must be accompanied by payment in U.S. Dollars. Orders payable by check must be drawn payable in U.S. Dollars on a U.S. bank, for the full amount of the investment. If you have entered into a FundSERV Agreement with us to effect transactions in Fund shares through FundSERV, you are hereby authorized to act on our behalf for the limited purpose of receiving purchase, exchange and redemption orders for Fund shares executed through FundSERV. You represent and warrant that all orders for the purchase, exchange or redemption of Fund shares transmitted to FundSERV for processing on or as of a given business day (Day 1) shall have been received by you prior to the Close of Trading on Day 1. Such orders shall receive the share price next calculated following the Close of Trading on Day 1 .You represent and warrant that orders received by you after the Close of Trading on Day 1 shall be treated by you and transmitted to FundSERV as if received on the next business day (Day 2). Such orders shall receive the share price next calculated following the Close of Trading on Day 2. You represent that you have systems in place reasonably designed to prevent orders received after the Close of Trading on Day 1 from being executed with orders received before the Close of Trading on Day 1.

  • Grievance Processing Union stewards or Union officials shall be permitted to have time off without loss of pay for the investigation and processing of grievances and arbitrations. Requests for such time off shall be made in advance and shall not be unreasonably denied. The Union will furnish the Employer with a list of Union stewards and their jurisdictions. The Union shall delineate the jurisdiction of Union stewards so that no xxxxxxx need travel between work locations or sub-divisions thereof while investigating grievances. Grievants shall be permitted to have time off without loss of pay for processing their grievances through the contractual grievance procedure, except that for class action grievances no more than three (3) grievants shall be granted such leave.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • Data Processing In this clause:

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Sub-processing 1. The data importer shall not subcontract any of its processing operations performed on behalf of the data exporter under the Clauses without the prior written consent of the data exporter. Where the data importer subcontracts its obligations under the Clauses, with the consent of the data exporter, it shall do so only by way of a written agreement with the sub-processor which imposes the same obligations on the sub-processor as are imposed on the data importer under the Clauses. Where the sub-processor fails to fulfil its data protection obligations under such written agreement the data importer shall remain fully liable to the data exporter for the performance of the sub-processor’s obligations under such agreement.

  • Claims Processing BCBSM will process Provider's Clean Claims submitted in accordance with this Agreement in a timely fashion.

  • Rules of Grievance Processing 1. Time limits of any stage of the grievance procedure may be extended by written mutual agreement of the parties at that step.

  • Induction Procedures a) The parties to this Agreement acknowledge that it is in the interests of the industry that all new employees and employers on a building project understand their obligations to this Agreement and are introduced to their jobs in a manner which will help them work safely and efficiently.

  • Processing Grievances The grievant shall be granted reasonable time off with pay from regularly scheduled duty hours to process a grievance, provided that the time off will be devoted to the prompt and efficient investigation and handling of grievances, subject to the following:

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