Sensor Identifiers Sample Clauses

Sensor Identifiers. In CITI‐SENSE a large number of sensing devices are deployed, ranging from static stations, mobile devices and wearable sensors, delivered by a variety of different suppliers. Each supplier applies its unique and often optimised methodology for uniquely identifying individual devices within their sensor network. To avoid duplication of identifiers from the various sensor data providers, and therefore avoid the risk of misidentification, it is advisable to agree on a common specification to uniquely identify any sensing device. A unique identifier can be defined as a numeric or alphanumeric string that is associated with a single entity within a given system. In CITI‐SENSE, we define a single entity as a sensing device within the CITI‐ SENSE context, such as a static monitoring stations or a mobile device.
AutoNDA by SimpleDocs

Related to Sensor Identifiers

  • Indirect Identifiers Any information that, either alone or in aggregate, would allow a reasonable person to be able to identify a student to a reasonable certainty Information in the Student’s Educational Record Information in the Student’s Email Provider: For purposes of the DPA, the term “Provider” means provider of digital educational software or services, including cloud-based services, for the digital storage, management, and retrieval of pupil records.

  • Product Identification Before removal from Sale Area, unless Contracting Officer determines that circumstances warrant a written waiver or adjustment, Purchaser shall:

  • User Identification 6.2.5.1 Access to each Party’s corporate resources will be based on identifying and authenticating individual users in order to maintain clear and personal accountability for each user’s actions.

  • Act Identifier Title Shoulder note Iron Ore (Robe River) Agreement Xxx 0000 First Schedule Iron Ore (Robe River) Agreement Second Schedule First variation agreement Third Schedule Second variation agreement [s. 3B] Fourth Schedule Third variation agreement [s. 2] Fifth Schedule Fourth variation agreement Sixth Schedule Fifth variation agreement

  • If Identified If the HSP is Identified it will:

  • Customer Identification Unless Elastic has first obtained Customer's prior written consent, Elastic shall not identify Customer as a user of the Products, on its website, through a press release issued by Elastic and in other promotional materials.

  • Client identification 9.1. The Company has the right to require the Client to confirm his/her registration information specified when opening a trading account. To do so, the Company may ask the Client at its own discretion and at any time to provide a notarized electronic copy of his/her identification document, bank statement or public utilities xxxx as a proof of residence. In particular cases, the Company may ask the Client to provide a photo of him/her holding his/her ID near his/her face. The detailed client identification requirements are set out in the “AML policies” section on the Company’s official site.

  • Non-Identification Approved Users agree not to use the requested datasets, either alone or in concert with any other information, to identify or contact individual participants from whom data and/or samples were collected. Approved Users also agree not to generate information (e.g., facial images or comparable representations) that could allow the identities of research participants to be readily ascertained. These provisions do not apply to research investigators operating with specific IRB approval, pursuant to 45 CFR 46, to contact individuals within datasets or to obtain and use identifying information under an 2 The project anniversary date can be found in “My Projects” after logging in to the dbGaP authorized-access portal. IRB-approved research protocol. All investigators including any Approved User conducting “human subjects research” within the scope of 45 CFR 46 must comply with the requirements contained therein.

  • Vendor Identity and Contact Information It is Vendor’s sole responsibility to ensure that all identifying vendor information (name, EIN, d/b/a’s, etc.) and contact information is updated and current at all times within the TIPS eBid System and the TIPS Vendor Portal. It is Vendor’s sole responsibility to confirm that all e-correspondence issued from xxxx-xxx.xxx, xxxxxxx.xxx, and xxxxxxxxxxxxxxxx.xxx to Vendor’s contacts are received and are not blocked by firewall or other technology security. Failure to permit receipt of correspondence from these domains and failure to keep vendor identity and contact information current at all times during the life of the contract may cause loss of TIPS Sales, accumulating TIPS fees, missed rebid opportunities, lapse of TIPS Contract(s), and unnecessary collection or legal actions against Vendor. It is no defense to any of the foregoing or any breach of this Agreement that Vendor was not receiving TIPS’ electronic communications issued by TIPS to Vendor’s listed contacts.

  • User ID and Password You will be assigned a personal User ID and a Password that you will use to obtain access to the Online Banking. You authorize us to follow any instructions entered through the Service using your User ID and Password. Because your User ID and Password can be used to access your Accounts and to access information about these Accounts, you should treat your User ID and Password with the same degree of care and secrecy that you use to protect your ATM security code and other sensitive financial data. We may ask you to change your User ID and Password from time to time for security reasons. You agree not to use any language that is abusive, harassing, libelous, defamatory, obscene, or threatening when defining your Password or any other personalization of your Accounts.

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