The core IoT Domain Model Sample Clauses

The core IoT Domain Model. The generic IoT scenario can be identified with that of a generic User that needs to interact with a (possibly remote) Physical Entity (PE) of the physical world (see Figure 11). In this short description we have already introduced the two key actors of the IoT. The User is a human person or some kind of a Digital Artefact (e.g., a Service, an application, or a software agent) that has an interest in interacting with a Physical Entity. In the physical environment, interactions can happen directly (e.g., by moving a pallet from A to B manually). In the IoT though, we want to be able to interact indirectly or mediated, i.e., by calling a service that will either give information about the Physical Entity or actuate on it. When a Human User is accessing a service, he does so through a service client, i.e., some software with an accessible user interface. For simplicity reasons, the service client is not shown in Figure 12. For the scope of the domain model, the interaction is usually characterized by a goal of the user. The Physical Entity is a discrete, identifiable part of the physical environment which is of interest to the user for the completion of his goal. Physical Entities can be almost any object or environment; from humans or animals to cars; from store or logistic chain items to computers; from electronic appliances to closed or open environments. * * Physical Entity interacts with User Figure 11: Basic abstraction of an IoT interaction. Physical Entities are represented in the digital world via a Virtual Entity. This term is also referred to as „virtual counterpart“ in the literature [28], but using the same root term „entity“ in both concepts clearer shows the relationship of these concepts. There are many kinds of digital representations of Physical Entities: 3D models, avatars, data-base entries, objects (or instances of a class in an object-oriented programming language), and even a social-network account could be viewed as such a representation. However, in the IoT context, Virtual Entities have two fundamental properties: • They are Digital Artefacts. Virtual Entities are associated to a single Physical Entity that they represent. While generally there is only one Physical Entity for each Virtual Entity, it is possible that the same Physical Entity can be associated to several Virtual Entities, e.g., a different representation per application domain or per IT system. Each Virtual Entity must have one and only one ID that identifies it univoc...
AutoNDA by SimpleDocs

Related to The core IoT Domain Model

  • Contract Database Metadata Elements Title: Whitesville Central School District and Whitesville Central School Educational Support Staff Association (2003) Employer Name: Whitesville Central School District Union: Whitesville Central School Educational Support Staff Association Local: Effective Date: 07/01/2003 Expiration Date: 06/30/2006 PERB ID Number: 10699 Unit Size: Number of Pages: 23 For additional research information and assistance, please visit the Research page of the Catherwood website - xxxx://xxx.xxx.xxxxxxx.xxx/library/research/ For additional information on the ILR School - xxxx://xxx.xxx.xxxxxxx.xxx/ AGREEMENT BETWEEN WHITESVILLE CENTRAL SCHOOL EDUCATIONAL SUPPORT STAFF ASSOCIATION AND THE WHITESVILLE CENTRAL SCHOOL DISTRICT JULY 1, 2003 THROUGH JUNE 30, 2006 TABLE OF CONTENTS ARTICLE TITLE PAGE Preamble 1 I Recognition 1 II Collective Bargaining U n i t 1 III Dues/Agency Fee Ckoffand Payroll Deduction 1 IV Rights of Employees 2 V Rights of Employer ------------- 2 VI Personnel F i l e 2 VII Employee Definitions 3 VIII Permanent Status/Seniority 4 IX Wages 5 X Overtime 7 XI Vacation 7 XII Holidays 8 XIII Sick Leave and Leavesof A b s e n c e 8 XIV Conference, Workshops,Required Courses 10 XV Meal Allowance and M i l e a g e 11 XVI Retirement 11 XVII Insurance 12 XVIII Cafeteria P l a n 14 .XIX Uniform Allowance------------------ 14 XX Hours of W o r k 14 XXI Transfers/Promotions 15 XXII Job Descriptions 15 XXIII Grievance Procedure 15 XIV Copies of the Contract 18 XV Zipper C x x x x x 18 XXVI Legislative Clause 18 XXVII Duration 19 SIGNATURES 19 APPENDIX A Grievance F o r m 20 APPENDIX B Dues Authorization F o r m 21

  • Security of All Software Components Supplier will inventory all software components (including open source software) used in Deliverables, and provide such inventory to Accenture upon request. Supplier will assess whether any such components have any security defects or vulnerabilities that could lead to a Security Incident. Supplier will perform such assessment prior to providing Accenture with access to such software components and on an on-going basis thereafter during the term of the Agreement. Supplier will promptly notify Accenture of any identified security defect or vulnerability and remediate same in a timely manner. Supplier will promptly notify Accenture of its remediation plan. If remediation is not feasible in a timely manner, Supplier will replace the subject software component with a component that is not affected by a security defect or vulnerability and that does not reduce the overall functionality of the Deliverable(s).

  • Solicitations for Subcontractors, Including Procurements of Materials and Equipment In all solicitations either by competitive bidding or negotiation made by the contractor for work to be performed under a subcontract, including procurements of materials or leases of equipment, each potential subcontractor or supplier shall be notified by the contractor of the contractor's obligations under this contract and the Regulations relative to nondiscrimination on the grounds of race, color, or national origin, sex, age, and disability/handicap.

  • JOINT WORK PRODUCT This Agreement is the joint work product of H-GAC and the Contractor. This Agreement has been negotiated by H-GAC and the Contractor and their respective counsel and shall be fairly interpreted in accordance with its terms and, in the event of any ambiguities, no inferences shall be drawn against any party.

  • RE-WEIGHING PRODUCT Deliveries are subject to re- weighing at the point of destination by the Authorized User. If shrinkage occurs which exceeds that normally allowable in the trade, the Authorized User shall have the option to require delivery of the difference in quantity or to reduce the payment accordingly. Such option shall be exercised in writing by the Authorized User.

  • Third Party Technology The Company makes use of third party technology to collect information required for traffic measurement, research, and analytics. Use of third party technology entails data collection. We therefore would like to inform clients the Company enables third parties to place or read cookies located on the browsers of users entering the Company’s domain. Said third parties may also use web beacons to collect information through advertising located on the Company’s web site. Please note that you may change your browser settings to refuse or disable Local Shared Objects and similar technologies; however, by doing so you may be disabling some of the functionality of Company’s services.

  • Product ACCEPTANCE Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User(s) shall have thirty (30) days from the date of delivery to accept hardware products and sixty (60) days from the date of delivery to accept all other Product. Where the Contractor is responsible for installation, acceptance shall be from completion of installation. Failure to provide notice of acceptance or rejection or a deficiency statement to the Contractor by the end of the period provided for under this clause constitutes acceptance by the Authorized User(s) as of the expiration of that period. The License Term shall be extended by the time periods allowed for trial use, testing and acceptance unless the Commissioner or Authorized User agrees to accept the Product at completion of trial use. Unless otherwise provided by mutual agreement of the Authorized User and the Contractor, Authorized User shall have the option to run testing on the Product prior to acceptance, such tests and data sets to be specified by User. Where using its own data or tests, Authorized User must have the tests or representative set of data available upon delivery. This demonstration will take the form of a documented installation test, capable of observation by the Authorized User, and shall be made part of the Contractor’s standard documentation. The test data shall remain accessible to the Authorized User after completion of the test. In the event that the documented installation test cannot be completed successfully within the specified acceptance period, and the Contractor or Product is responsible for the delay, Authorized User shall have the option to cancel the order in whole or in part, or to extend the testing period for an additional thirty (30) day increment. Authorized User shall notify Contractor of acceptance upon successful completion of the documented installation test. Such cancellation shall not give rise to any cause of action against the Authorized User for damages, loss of profits, expenses, or other remuneration of any kind. If the Authorized User elects to provide a deficiency statement specifying how the Product fails to meet the specifications within the testing period, Contractor shall have thirty (30) days to correct the deficiency, and the Authorized User shall have an additional sixty (60) days to evaluate the Product as provided herein. If the Product does not meet the specifications at the end of the extended testing period, Authorized User, upon prior written notice to Contractor, may then reject the Product and return all defective Product to Contractor, and Contractor shall refund any monies paid by the Authorized User to Contractor therefor. Costs and liabilities associated with a failure of the Product to perform in accordance with the functionality tests or product specifications during the acceptance period shall be borne fully by Contractor to the extent that said costs or liabilities shall not have been caused by negligent or willful acts or omissions of the Authorized User’s agents or employees. Said costs shall be limited to the amounts set forth in the Limitation of Liability Clause for any liability for costs incurred at the direction or recommendation of Contractor.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

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