Senior DevOps Engineer

dhl

Chennai, India NM Years Exp Posted 1h ago

Job Description

  • SLA: Participate in alignment calls and meetings; provide required service information to the Service Delivery Manager (SDM).
  • Support Model: Conduct alignment with business and support teams; verify that risks, PARs, and ELRs are approved; update the Support Model in eSM; initiate and track RFC voting; incorporate stakeholder comments and repeat the update cycle when required.
  • Authorization Concept: Maintain ownership and ensure the document is kept current as part of the service governance framework.
  • Standard Change Catalogue: Align with business and support teams; update the catalogue; create a significant RFC based on existing minor RFCs; support CAB approval; prepare an RFC template where needed.
  • Disaster Recovery Plan (DRP): Review the DRP document; update the DRP repository with the new version and related RFC details; revise SLA references; update the DRP link and next test date in GSN CMDB; raise the required RFC for configuration management.
  • Disaster Recovery Test Procedure: Verify that the latest DRP template is used; review hardware and software changes; create a significant RFC from the template; inform the ITSCM team of the outcome.
  • Monitoring Concept: Maintain ownership and ensure the document remains aligned with service monitoring requirements.
  • Service Specifications Form (SSF): Review monitoring transactions, thresholds, scripts, and screenshots with application support; validate monitoring locations with the Topaz team and business; revise contact information; ensure the SLA is updated accordingly.
  • External Link Requests (ELR): Renew ELRs upon expiration alerts; coordinate changes with Application, Basis, Infrastructure, Business, and third-party teams; use the ELM request process for expedited handling where necessary.
  • Risks: Collect risk modification requests and submit them to the risk manager for processing.
  • Privilege Access Requests (PAR): Ensure the request is rejected for editing when updates are needed; review validity with users and stakeholders; update the PAR; secure approval from the Service Owner and impacted groups.
  • Service Improvement Plan: Hold periodic alignment meetings with support teams and record improvement updates in GSN.
  • Internal Control Self-Assessment: Collect detailed control-level information for each service; coordinate with support teams; update the corresponding information in GSN.
  • Application Capture Sheet: Gather detailed service information from support teams and ensure completeness of the document.
  • Transport Procedure: Maintain ownership and ensure the procedure remains current and aligned with operational requirements.
  • Archiving Concept: Maintain ownership and ensure the concept remains current and aligned with retention and operational requirements.
  • Emergency User Concept: Maintain ownership and ensure the concept remains current and aligned with access control requirements.
  • GURU Support Entry: Obtain detailed information from support teams and manually verify alignment with the SLA and Support Model.
  • Orders Maintenance: Obtain new and renewed order information from BPM; update eProject accordingly; recreate renewed orders from scratch where copy transfer is not possible.
  • Review of User Access Rights: Initiate the review through a GSN ticket; send user lists to business and ITS managers; coordinate required access changes; store all supporting evidence in iShare.
  • Service Performance Review Presentation: Update the presentation with additional data and request information on an ad hoc basis where automatic delivery is unreliable.

Control Expectations:

  • Ensure document updates are accurate, complete, and aligned with business, support, and governance stakeholders.
  • Maintain evidence of reviews, approvals, changes, and communications in the designated systems or repositories.
  • Trigger related RFCs, approvals, and system updates whenever document changes affect governed service processes.
    • Revisit and rework documents when stakeholder comments, approval outcomes, or operational changes require further revision.

Similar Openings for You