Configuration & Change management. 8.9.1 The Customer is able to perform network security configuration and changes using the self-service ICON Secure portal described in paragraph 9.4, the Customer ownership for implementing such changes is recommended by Maintel
8.9.2 Configuration changes can also be made remotely and managed by the SOC Team, access to equipment will be centrally controlled via Authentication, Authorisation and Accounting (AAA) based services. This may incur a Charge to the Partner.
8.9.3 The Services will be provided to each Site as stated in the Order. Support shall be delivered as described below.
8.9.4 Subject to paragraph 8.9.10 of this Schedule, Maintel will provide support to the Services Levels set out in paragraph 12 the Core Services.
8.9.5 The Customer (and Maintel where the Proactive Monitoring Service has been purchased by the Customer) will be able to log Support Requests at any time with the Service Desk, however the issue will only be worked on during the Supported Hours for the relevant Site.
8.9.6 Upon receipt of a Support Request Maintel shall at its sole option: carry out remote diagnostic checks of the Customer Equipment and/or Software; or provide telephone advice; or visit the Customer’s site to diagnose the Incident in the Customer Equipment and/or Software.
8.9.7 Maintel shall take whatever actions it deems necessary to repair or replace any part of the Customer Equipment and/or the Software. Any Customer Equipment (excluding Software) or parts thereof provided to the Customer in order to rectify the Incident, shall become Maintel’s property.
8.9.8 The Partner shall use, and ensure that the Customer uses the Customer Equipment in accordance with the relevant manufacturer's instructions and any other requirements and recommendations that Maintel has notified to the Partner in writing from time to time.
8.9.9 Where any Customer Equipment becomes End of Sale or End of Support, the Partner agrees that Maintel shall at its option: (a) cease support on such Customer Equipment after serving reasonable notice to the Partner; or (b) continue to provide support on a reasonable endeavours basis. Where such support continues replacement Customer Equipment will only be provided where Maintel has such Customer Equipment in stock and that no enhancements, upgrades or new software shall be provided on such Customer Equipment, unless otherwise agreed. The Partner agrees that the Service Levels shall not apply to such Customer Equipment.
8.9.10 The levels set out ...
Configuration & Change management. The Technical Management Plan shall include a Configuration Change Management Plan, covering:
(a) activities to fulfil all the requirements of RailCorp’s configuration management process, including
(i) preparation of documentation and submission of changes to the configuration and operation of RailCorp’s assets prior to and at the completion of each track possession;
(ii) procedures to ensure that construction, including temporary or staged works, will not commence until there is configuration change approval and notice;
(iii) preparation of documentation and submission of changes to the configuration and operation of RailCorp’s assets prior to final commissioning and handover Notice:- where the works include tunnelling, details of specific measures in relation to design practices and design review to maintain safety during tunnelling works and to demonstrate compliance with Coroner’s recommendations coming out of the inquiry into the tunnelling fatality that occurred during the construction of the Cross City Tunnel project in SydneyAuthority Liaison and Approval Management Plan
Configuration & Change management. Configuration and Change Management (CCM) is the process of maintaining the integrity of hardware, software, firmware, and documentation related to the configuration and change management process. CCM is a continuous process of controlling and approving changes to information or technology assets or related infrastructure that support the critical services of an organization. This process includes the addition of new assets, changes to assets, and the elimination of assets. Cybersecurity is an integral component to information systems from the onset of the project or acquisition through implementation of: • Application and system security • Configuration management • Change control procedures • Encryption and key management • Software maintenance, including but not limited to, upgrades, antivirus, patching and malware detection response systems As the complexity of information systems increases, the complexity of the processes used to create these systems also increases, as does the probability of accidental errors in configuration. The impact of these errors puts data and systems that may be critical to business operations at significant risk of failure that could cause the organization to lose business, suffer damage to its reputation, or close completely. Having a CCM process to protect against these risks is vital to the overall security posture of the organization.
Configuration & Change management. Configuration and Change Management (CCM) is the process of maintaining the integrity of hardware, software, firmware, and documentation related to the configuration and change management process. CCM is a continuous process of controlling and approving changes to information or technology assets or related infrastructure that support the critical services of an organization. This process includes the addition of new assets, changes to assets, and the elimination of assets. Cybersecurity is an integral component to information systems from the onset of the project or acquisition through implementation of: • Software maintenance, including but not limited to, upgrades, antivirus, patching and malware detection response systems As the complexity of information systems increases, the complexity of the processes used to create these systems also increases, as does the probability of accidental errors in configuration. The impact of these errors puts data and systems that may be critical to business operations at significant risk of failure that could cause the organization to lose business, suffer damage to its reputation, or close completely. Having a CCM process to protect against these risks is vital to the overall security posture of the organization.
Configuration & Change management. 4.3.1 Configuration management is based on standard working hours of 08:00 – 18:00 Mon-Fri excluding Public Holidays.
4.3.2 All requests for changes to the service configuration should be made in the first instance to the Net Support UK Ltd Support Services Team by either telephone to 000 000 00 000 or by email to xxxxxxx@xxxx.xxx. This will raise a unique Request Number. Following this Net Support UK Ltd will use best endeavours to process the Request without undue delay.
4.3.3 No changes will be made to either Registration Details or DNS Records until we have received approval from an authorised contact, in writing or via email, of a completed Change Request form.
4.3.4 The Net Support UK Ltd Support services team have a specific SLA in place for helpdesk services. Please refer to Net Support UK Ltd Support Services SLA for more detail. Typical lead times for specific change types are given below: Modify Registrant Details 2 Business Days Add \ Amend DNS Records 1 Business Day Domain Transfers 2 business Days1 Modify Name Servers 1 Business Day2 1: Domain transfer requests are dependent on third parties and registry processes. Domain transfers for some domains can take several weeks to complete. Our lead times refer to time taken for us to respond at each stage of the process.
Configuration & Change management. 4.3.1 Configuration management is based on standard working hours of 08:00 – 18:00 Mon-Fri excluding Public Holidays.
4.3.2 All requests for changes to the service configuration should be made in the first instance to the Ogi Business Service Desk by either telephone to 000 000 00 000 or by email to mailto:xxxxxxxx.xxxx@xxx.xxxxx. This will raise a unique Request Number. Following this Ogi will use best endeavours to process the Request without undue delay.
4.3.3 No changes will be made to either Registration Details or DNS Records until we have received approval from an authorised contact, in writing or via email, of a completed Change Request form.
4.3.4 The Ogi Business Service Desk have a specific SLA in place for helpdesk services. Please refer to Ogi Pro Support Services SLA for more detail. Typical lead times for specific change types are given below: Modify Registrant Details 2 Business Days Add \ Amend DNS Records 1 Business Day Domain Transfers 2 business Days1 Modify Name Servers 1 Business Day2 1: Domain transfer requests are dependent on third parties and registry processes. Domain transfers for some domains can take several weeks to complete. Our lead times refer to time taken for us to respond at each stage of the process. 2: Name Server records can take up to 72 hours to fully propagate following a change. Our lead time refers to the time taken for us to complete the change following approval of a formal Change Request.
