System Outages. Work, which requires any existing building utility system (including fire protection) to be taken out of service, shall be scheduled and performed so that the length of time the utility is out of service is held to a minimum. All material for the alteration and tie-in work shall be on hand when each utility service interruption is scheduled. The Contractor shall notify Battelle not less than five (5) working days prior to each required utility shutdown. All tie-in work shall be scheduled and performed so that the shutdown time will not exceed four (4) hours for water and two (2) hours for electrical or fire alarm. Battelle shall approve methods of performing the tie-in work prior to any utility system outage. Prior approval must be obtained for connection to and use of existing fire hydrants.
System Outages. Each Party shall use its best efforts to avoid unscheduled System Outages in the performance of each Party's respective rights and obligations under this Agreement.
System Outages a. CONSULTANT shall review and evaluate the CONTRACTOR’s system outage requests (SOR) in conjunction with the CITY. CONSULTANT shall assess the reasonableness of the duration of the requested shutdown.
b. The SORs shall be reviewed and approved at least two weeks ahead of the actual outage/shutdown.
c. CONSULTANT shall facilitate/coordinate shutdowns with the CONTRACTOR, CITY and ENGINEER.
i. CITY is responsible for reviewing and approving system outage request and duration, confirming the outage is properly planned, implementing the outage, and bringing services back online after the outage.
System Outages. (a) Pricing In the event of unavailability of systems, e.g. FireAnt, the Coverholder will continue to underwrite business insofar as is possible without system support using manual processes.
(b) Capital management and reserving In the event of unavailability of systems, e.g. FireAnt, Tyche, the Coverholder will temporarily cease activities insofar as data from these systems is required. The Coverholder will continue to operate other aspects of these processes on a best-efforts basis, using EUC solutions. If system outages persist and outputs from the service are expected to be required before the service is restored (e.g. past quarter close), the Coverholder will produce the required actuarial information at the most recently available reporting date, and begin work to meet the existing deadline as soon as practical. The Underwriter will then perform an assumption-based roll-forward exercise to the reporting date.
System Outages. In the event of unavailability of systems, e.g. FireAnt, the Coverholder will temporarily cease activities insofar as data from these systems is required. The Coverholder will continue to operate other aspects of the management reporting process on a best-efforts basis, using EUC solutions. If system outages persist and outputs from the service are required (e.g. past quarter close), the Coverholder will make commercially reasonable efforts to produce required information, using the most recent backed-up data rolled forward to the reporting date.
System Outages. In the event of unavailability of systems, e.g. Oracle, Anaplan, Prequel, the Coverholder will use best efforts and alternative data sources (such as back-ups or an alternative system than is typically used) to produce a cash flow forecast using a working paper process occurring.
System Outages. In the event of unavailability of systems, e.g. Oracle, Anaplan, Prequel, the Coverholder will use best efforts and alternative data sources (such as back-ups or an alternative system than is typically used) to produce collateral management reporting using a working paper process. The Coverholder will enter the data maintained off-system during the outage into the relevant system within one week of the system outage event occurring.
System Outages. In the event of unavailability of systems, e.g. Oracle, Anaplan, the Coverholder will temporarily cease activities insofar as data from these systems is required. The Coverholder will continue to operate other aspects of the annual planning process on a best-efforts basis. If system outages persist and outputs from the service are required, the Underwriter may instruct the Coverholder to either: ● Prepare an annual plan using Excel ● Operate using the prior-year’s annual plan, adjusted for known events ● Prepare an updated plan on the basis of the most recently available back-up data, adjusted for known events
System Outages. In the event of unavailability of systems, e.g. Oracle, GTreasury, the Coverholder will temporarily cease BAU payment activities insofar as data from these systems is required. The Coverholder will continue to operate critical payments manually via a working paper process, which the Coverholder will pay directly from online banking systems. If system outages persist beyond one week, the Coverholder will make commercially reasonable efforts to resume processing via a working paper process. The Coverholder will subsequently enter transactions processed manually during the down-time into the system once service is restored, within one week of the system outage event occurring.
System Outages. In the event of unavailability of systems, e.g. Prequel, DXC Xchanging (ECF2), Xxxxxxx Xxxxxx (TRAX), the Coverholder will continue to service claims by utilising each system’s disaster recovery solution wherever possible. If this is not a viable option, the service will continue without system support and manually record the key information. The Coverholder will enter the data maintained off-system during the outage into the relevant system within one month of the service being restored.
