Risk and Issue Identification and Registration Sample Clauses

Risk and Issue Identification and Registration. 388 All parties to this Agreement ensure that the appropriate risk and issue management functions as 389 well as operational processes are in place for the registration of identified risks and issues, 390 potentially affecting the various programme deliverables and milestones. All parties to this 391 Agreement commit to share risks and issues in the appropriate forums, as defined hereafter in the 392 Sections “T2S Monitoring of Client Readiness Framework” and “Processes”.
AutoNDA by SimpleDocs
Risk and Issue Identification and Registration. 380 All parties to this Agreement ensure that the appropriate risk and issue management functions as 381 well as operational processes are in place for the registration of identified risks and issues, 382 potentially affecting the various programme deliverables and milestones. All parties to this 383 Agreement commit to share risks and issues in the appropriate forums, as defined hereafter in the 384 Sections “T2S Monitoring of Client Readiness Framework” and“Processes”. 385 6.2.4 Risk Assessment 386 The party to this Agreement identifying a risk (risk owner) shall evaluate the risk, basedon: 387  the impact on the T2S Programme; and 388  the probability of the riskmaterialising.

Related to Risk and Issue Identification and Registration

  • Contractor’s Staff Identification Contractor shall provide, at Contractor’s expense, all staff providing services under this Contract with a photo identification badge.

  • 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.

  • 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.

  • 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.

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

  • Review Procedures for Identifying Entity Accounts With Respect to Which Reporting Is Required For Preexisting Entity Accounts described in paragraph B of this section, the Reporting Finnish Financial Institution must apply the following review procedures to determine whether the account is held by one or more Specified U.S. Persons, by Passive NFFEs with one or more Controlling Persons who are U.S. citizens or residents, or by Nonparticipating Financial Institutions:

  • Accessibility of Web-Based Information and Applications For State Agency Authorized User Acquisitions: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08-005, Accessibility of Web-Based Information and Applications as follows: Any web-based information and applications development, or programming delivered pursuant to the contract or procurement, will comply with New York State Enterprise IT Policy NYS-P08- 005, Accessibility of Web-Based Information and Applications as such policy may be amended, modified or superseded, which requires that state agency web-based information and applications are accessible to persons with disabilities. Web-based information and applications must conform to New York State Enterprise IT Policy NYS-P08-005 as determined by quality assurance testing. Such quality assurance testing will be conducted by the State Agency Authorized User and the results of such testing must be satisfactory to the Authorized User before web-based information and applications will be considered a qualified deliverable under the contract or procurement.

  • 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.

  • CAUTIONS FOR GLOBAL USE AND EXPORT AND IMPORT COMPLIANCE Due to the global nature of the internet, through the use of our network you hereby agree to comply with all local rules relating to online conduct and that which is considered acceptable Content. Uploading, posting and/or transferring of software, technology and other technical data may be subject to the export and import laws of the United States and possibly other countries. Through the use of our network, you thus agree to comply with all applicable export and import laws, statutes and regulations, including, but not limited to, the Export Administration Regulations (xxxx://xxx.xxxxxx.xxx.xxx/bis/ear/ear_data.html), as well as the sanctions control program of the United States (xxxx://xxx.xxxxxxxx.xxx/resource- center/sanctions/Programs/Pages/Programs.aspx). Furthermore, you state and pledge that you:

  • 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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!