CDPH PCI Backup Plan Sample Clauses

CDPH PCI Backup Plan. Contractor shall have a documented, tested, accurate, and regularly scheduled full backup process for systems and devices holding CDPH PCI.
AutoNDA by SimpleDocs

Related to CDPH PCI Backup Plan

  • Data Backup Plan Contractor must have established documented procedures to backup DHCS PHI to maintain retrievable exact copies of DHCS PHI or PI. The plan must include a regular schedule for making backups, storing backups offsite, an inventory of backup media, and an estimate of the amount of time needed to restore DHCS PHI or PI should it be lost. At a minimum, the schedule must be a weekly full backup and monthly offsite storage of DHCS data.

  • Provision for Generation Compensation Grid unavailability in a contract year as defined in the PPA: (only period from 8 am to 6 pm to be counted): Generation Loss = [(Average Generation per hour during the Contract Year) × (number of hours of grid unavailability during the Contract Year)] Where, Average Generation per hour during the Contract Year (kWh) = Total generation in the Contract Year (kWh) ÷ Total hours of generation in the Contract Year. The excess generation by the SPD equal to this generation loss shall be procured by the Buying Utility at the PSA tariff so as to offset this loss in the succeeding 3 (three) Contract Years.

  • International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Transition Plan In the event of termination by the LHIN pursuant to this section, the LHIN and the HSP will develop a Transition Plan. The HSP agrees that it will take all actions, and provide all information, required by the LHIN to facilitate the transition of the HSP’s clients.

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