Access to Personnel File Each employee shall have reasonable access to his/her personnel file for the purpose of reviewing any evaluations or formal disciplinary notations contained therein, in the presence of the Director of Personnel or designate. An employee has the right to request copies of any evaluations in this file.
Data Necessary to Perform Services The Trust or its agent shall furnish to USBFS the data necessary to perform the services described herein at such times and in such form as mutually agreed upon.
Access to Personnel Records Upon written request to the Chief of Police, an employee shall have access to the employee's records during normal office hours of the records custodian. Such access to personnel records shall be within a reasonable time of said request. Such request shall not interfere with the employee's regularly scheduled working hours. Review of the records shall be made in the presence of the Chief or the Chief’s designated representative.
Review Systems; Personnel It will maintain business process management and/or other systems necessary to ensure that it can perform each Test and, on execution of this Agreement, will load each Test into these systems. The Asset Representations Reviewer will ensure that these systems allow for each Review Receivable and the related Review Materials to be individually tracked and stored as contemplated by this Agreement. The Asset Representations Reviewer will maintain adequate staff that is properly trained to conduct Reviews as required by this Agreement.
Authorization to Perform Services The Consultant is not authorized to perform any services or incur any costs whatsoever under the terms of this Agreement until receipt of a written Notice to Proceed from the City.
Access to Personal Information by Subcontractors Supplier agrees to require any subcontractors or agents to which it discloses Personal Information under this Agreement or under any SOW to provide reasonable assurance, evidenced by written contract, that they will comply with the same or substantially similar confidentiality, privacy and security obligations with respect to such Personal Information as apply to Supplier under this Agreement or any SOW. Supplier shall confirm in writing to DXC that such contract is in place as a condition to DXC’s approval of use of a subcontractor in connection with any SOW. Upon request of DXC, Supplier will provide to DXC a copy of the subcontract or an extract of the relevant clauses. Supplier shall ensure that any failure on the part of any subcontractor or agent to comply with the Supplier obligations under this Agreement or any SOW shall be grounds to promptly terminate such subcontractor or agent. If during the term of this Agreement or any SOW, DXC determines, in its exclusive discretion, that any Supplier subcontractor or agent cannot comply with the Supplier obligations under this Agreement or with any SOW, then DXC may terminate this Agreement in whole or in part (with respect to any SOW for which such subcontractor or agent is providing services), if not cured by Supplier within the time prescribed in the notice of such deficiency.
Access to Personnel Files All employees shall be allowed access to their personnel files during normal working hours for inspection and/or copies of documents which will be provided by the Employer. Such inspection shall be made subject to prior arrangement with the Employer.
Policies and Temporary Policies Registry Operator shall comply with and implement all Consensus Policies and Temporary Policies found at <xxxx://xxx.xxxxx.xxx/general/consensus-policies.htm>, as of the Effective Date and as may in the future be developed and adopted in accordance with the ICANN Bylaws, provided such future Consensus Polices and Temporary Policies are adopted in accordance with the procedure and relate to those topics and subject to those limitations set forth in Specification 1 attached hereto (“Specification 1”). Data Escrow. Registry Operator shall comply with the registry data escrow procedures set forth in Specification 2 attached hereto (“Specification 2”).
Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes
Temporary Policies Registry Operator shall comply with and implement all specifications or policies established by the Board on a temporary basis, if adopted by the Board by a vote of at least two-‐thirds of its members, so long as the Board reasonably determines that such modifications or amendments are justified and that immediate temporary establishment of a specification or policy on the subject is necessary to maintain the stability or security of Registry Services or the DNS (“Temporary Policies”). 2.1. Such proposed specification or policy shall be as narrowly tailored as feasible to achieve those objectives. In establishing any Temporary Policy, the Board shall state the period of time for which the Temporary Policy is adopted and shall immediately implement the Consensus Policy development process set forth in ICANN’s Bylaws.
