Maintaining Services Sample Clauses

Maintaining Services. Developer is advised that Work is to be performed in spaces regularly scheduled for instruction. Interruption and/or periods of shutdown of public access, electrical service, water service, lighting, or other utilities shall be only as arranged in advance with the District. Developer shall provide temporary services to all facilities interrupted by Developer’s Work.

Maintaining Services. 12.1 The Participant will be responsible for maintaining the following information for it’s Services (unless it is self-maintaining – see 12.2 below for details) - Service name and description - Address details - Contact details - Linked documents (inspection reports/brochures etc.) - External links (e.g. to service provider websites) - Approval status 12.2 Services can become self-maintaining by establishing at least one 3rd party contact and associating them with the service. The responsibility for establishing this contact lies with the Participant in which the Service resides (in the case of migrated services), or the Participant who imported/entered the Service if it was not present in the initial migration. Once established, the system will contact the 3rd party user every 6 months and request them to verify/update the data. Any service that has a 3rd party user associated with them will not feature in the data verification/update report that is presented to the Participant every 6 months. 12.3 For self-maintained services, there are some fields that cannot be updated without approval by the responsible participant. These include: - Service name - Description - Images - Categorisation (although these should be auto-categorised in virtually all cases so this should not be a consideration) 12.4 A report will be created that displays change requests that are currently awaiting approval. The Participant must respond to the requests by approving or rejecting them within a locally agreed deadline.