| CONFIGURATION MANAGEMENT PROFILE at remote at Remote, Remote, USA |
| Email: [email protected] |
| From: Raj Khan, Convextech inc. [email protected] Reply to: [email protected] Hi, Hope you are doing good.!! Please let me know if you are interested in the below position.!! Position: CONFIGURATION MANAGEMENT PROFILE Location: remote Duration: long-term contract (3 years initially and 2 possible extensions for a total of 5 years). Visa: Only USC/GC/EAD Interview: Video Job Description: Degree Requirements University Degree (high) in a technical subject (f. ex: Computer Science, Telecommunications, Mathematics, etc.) Demonstrable Experience Demonstrable experience of at least 5 years in team, project and decision-making management tasks within its technological perimeter. Technical Areas Experience Demonstrable experience of at least 3 years in the technical areas, platforms, tools and languages of its technological perimeter. Number of Profiles 1 Service Hours Service coverage from 7:00 am to 6:00 pm. Service coverage will be managed globally by team members. On Call There is a possibility that the service may require on-call. Specific knowledge CyberArk Expert. Other knowledge Valuable Microsoft PKI Infrastructure, Microsoft Intune for Mobile Application Management (MAM) and Mobile Device Management (MDM), Privileged Access Management (PAM), Microsoft System Center Configuration Manager (SCCM), Ansible Automation Platform, Staff working on CyberArk in the UK are required to be screened and compliant to BS5878 standard MAIN FUNCTIONS AND TASKS Incident Management Incident Reception: The service is designed to receive and register incidents promptly. Problem Analysis: The team conducts a thorough analysis of the issue to identify its root cause. Resolution: The service ensures efficient problem resolution to minimize downtime. Annotation and Closure: Every incident is documented in detail, and the case is closed only after confirming the resolution. Proactive Backlog Analysis: The service prioritizes incidents and develops contingency plans to manage the backlog effectively. Recurrent Incident Analysis: The team investigates recurring incidents to prevent future occurrences. Remediation Procedure Documentation: The remediation process is documented to ensure consistency and efficiency. Process Improvement Definition, Planning, and Execution: The service continually seeks to improve its processes for better performance. Automate Remediation: The service leverages automation to expedite the remediation process. Change and Request Management: Change Data Gathering: The service collects comprehensive information about the proposed change. Execution: The team implements the change meticulously to ensure minimal disruption. Annotation and Closure: The change is documented, and the case is closed post-implementation. Improved Information for Requesters: The service strives to provide detailed information to requesters to bridge any information gaps. Migration to Technical Platforms: The service facilitates the transition to technical platforms that enhance data retrieval and integration with CMDB. Change Execution Documentation: The execution of the change is documented for future reference. Recurrent Change Analysis: The team analyses recurring changes to optimize the process. Process Improvement Definition, Planning, and Execution: The service continually refines its change management process. Automating Change Execution: The service employs automation to streamline change execution. Proactive Backlog Management with Prioritization: The service proactively manages the backlog with a focus on prioritization. Support Cases Management: Opening and Managing Support Cases with the Manufacturer: The service opens and manages support cases with the manufacturer to expedite resolution. Scheduling Technical Sessions with the Manufacturer: The team schedules technical sessions with the manufacturer to monitor and resolve cases. Scheduling a Session to Improve Infrastructure and Functionality: The service schedules sessions aimed at enhancing infrastructure and functionality. Documentation of All Cases and Adaptation of Problem Resolution Guides: All cases are documented, and problem resolution guides are adapted as needed. Critical Infrastructure Support in 24x7: 24x7 On-Call Support for Infrastructure and Critical Services: The service provides continuous on-call support for infrastructure and critical services. Guaranteeing the Availability and Functionality of the Systems: The service ensures the availability and functionality of the systems at all times. Coordinating Actions with 24x7 Support for Problem Resolution: The team coordinates with 24x7 support to resolve problems efficiently. Documentation of All Cases and Adaptation of Problem Resolution Guides: All cases are documented, and problem re solution guides are updated as necessary. Planned Outside Hours Interventions: Planning and Execution of Planned Interventions Outside of Hours: The service plans and executes interventions during off-peak hours to minimize impact. Requests Management: The service attends to requests from various groups, projects, and companies for the execution of interventions in windows of minimum impact. Analysis of Interventions and Recurring Actions: The team analyzes interventions and recurring actions to implement automation or improvements that reduce intervention times. Project Assistance: Analysis of Monitoring Requirements for Implementation or Evolution Projects of Infrastructure, Applications, Services: The service analyzes monitoring requirements for implementation or evolution projects of infrastructure, applications, services. Plan Tasks and Effort: The service plans tasks and effort. Assign Resources to Projects: The service assigns resources to projects. Design of the Monitoring Solution: The service designs the monitoring solution. Testing the Solution: The service tests the solution. Construction and Deployment: The service constructs and deploys the solution including new integration models based in the managed monitoring applications. Documentation: The service documents the solution. Publication and Maintenance of the Configuration of the Applications Monitoring Roles for the Global Query. Configuration Disclosure: The service publishes and maintains the configuration of the applications monitoring roles (scope) for the global query and discloses the configuration. Third Party Assistance: Assistance in Resolving Doubts of Users and Technical Teams: The service assists in resolving doubts of users and technical teams. Mail Queue Management and Response to Users: The service manages the mail queue and responds to users. Provide Information on Monitoring, Operational Procedures, Change Templates, Requests, Incidents, Projects: The service provides information on monitoring, operational procedures, change templates, requests, incidents, projects Schedule and Attend Meetings with Users, Technical Teams, Suppliers, etc.: The service schedules and attends meetings with users, technical teams, suppliers, etc. Proactive Management of Queries Made by Email and Teams: The service proactively manages queries made by email and Teams. Procedure and Document the Teams Usual Processes for Their Efficient Disclosure to Third Parties: The service documents the teams usual processes for their efficient disclosure to third parties. Security Patching of the Infrastructure: Critical Updates Due to Vulnerability Reported with the Manufacturer or Cybersecurity Group: The service applies critical updates due to vulnerabilities reported by the manufacturer or cybersecurity group. Proactive Security Analysis of Managed Infrastructure: The service conducts proactive security analysis of the managed infrastructure. Submit CRITICAL Vulnerability Reports and Mitigation Plans: The service submits CRITICAL vulnerability reports and mitigation plans. Plan CRITICAL Security Patching and Update Plans: The service plans CRITICAL security patching and update plans. Security or Defect Patching (Minor Update) at Least Once a Year: The service patches security or defects (minor updates) at least once a year. Product Maintenance: This process is integral to ensuring the correct functioning of the product. The Configuration Management service is responsible for keeping the product active and running optimally. This involves: Infrastructure Upgrade: Product Version Updates Before End of Support: The service updates product versions before the end of support. Updates on Current Infrastructure (Over-the-Top) That Do Not Require New Infrastructure or Product Changes: The service updates the current infrastructure (over-the-top) that do not require new infrastructure or product changes. Plan Infrastructure Upgrades Without New Architecture Changes or Product Changes at Least Once Every 2 Years: The service plans infrastructure upgrades without new architecture changes or product changes at least once every two years. Operations Requirements: Backup and Recovery Process: The elements of the product must be included in the backup procedure. In the event of a disaster, it should be possible to restore them using the backups. Monitoring Process: The main elements must be monitored regularly to ensure optimal performance. In the event of a disaster, these elements should be recoverable from the backups. Operational Menus: The Operations team should have the necessary capabilities to perform scheduled maintenance and address issues as they arise. Service Modelization: Production services must be modelled and included in the Configuration Management Database (CMDB). Change and Incident Templates: Templates for requesting changes and maintenance to the product should be readily available. Automatic Request: If feasible, recurrent tasks should be automated using automatic requests in ITNow. Security Integration: Integration with Active Directory: This is required to secure user access to the product. Integration with Security Monitoring Products: When possible and deemed relevant by the Security team, the product should be integrated with security monitoring tools. Security Reporting: If applicable, reports should be generated to monitor the use of the product and ensure its security. Disaster Recovery: Customization of the DR Solution: The services with Disaster Recovery must be correctly configured to ensure that the service can be recovered in a DR test. Maintenance of the DR Procedures: Collaboration is required in drafting the procedures to test the services in a DR scenario and to activate the services in the event of a real disaster. Planned DR Test: Participation is required in the testing of the products or architectures involved in the test. Auditory and Reporting: Auditory: For the product involved in the auditory process, the extraction of evidence requested by auditors is required. Security Reporting: Reports should be generated to detect any potential security issues. License Reports: Reports should be generated to monitor the use of licenses and their evolution. Thanks and Regards MD. Raj Khan Technical Recruiter ConvexTech Inc. Email id- [email protected] LinkedIn - linkedin.com/in/md-raj-khan-9b1498204 Keywords: access management information technology green card Idaho Maryland CONFIGURATION MANAGEMENT PROFILE at remote [email protected] |
| [email protected] View all |
| Wed Oct 30 21:20:00 UTC 2024 |