Description
Harris Global are currently recruiting for a Solaris Systems Administrator for massive transformation and change project in the North East.
Profile
- Minimum of 2 years working experience within IT UNIX Operations, infrastructure services support
- Ability to relate technical applications to business environment, processes and organization.
- Must be able to demonstrate excellent troubleshooting and problem solving skills
- Demonstrated team working skills in a collaborative working environment.
- Fluency in conversational and technical English, written and spoken.
- Excellent understanding of problem, change, and incident management processes
Description
The Systems Administrator is an expert in a designated or multiple OS technology, and the context in which that technology is implemented in the supported client(s) environment, or a specific subset of the environment. As such, the System Administrator also needs to have a strong understanding of:
- the underlying infrastructure (enclosures, SAN, storage arrays, network, load-balancers, BUR, etc)
- the tools infrastructure
The Systems Administrators are accountable to ensure the environment is stable and recoverable. They are responsible for identifying Single-Points-of-Failure within the environment, assessing risk, notifying the ADM/CCL with recommendations to remediate or downgrade SLA's. They are expected to interface directly with the relevant Account Service Manager/Account Delivery Manager/Delivery Leads to discuss and resolved any issues.
Furthermore, the Systems Administrators are responsible for ensuring Engineering and Project activity does not introduce new risk into the environment.
The Systems Administrator is a hands-on delivery role, involved in the day-to-day operation of the client, and typically participating in both the change execution and Rapid-Response Teams. The SMEs also provide support for the other AAT Leads, particularly where a deep understanding of the technology or its deployment within the customer environment is required. For instance, the SME may be involved in the evaluation of change implementation, verification and backout plans, or interfacing with vendors for root-cause analysis.
Core Deliverables
The below core deliverables are, but not limited to:-
- The Systems Administrator is an expert in a designated technology, and the context in which that technology is implemented in the client's environment, or a specific subset of the environment
- Has a clear understanding of Client's Business and application requirements, and how these relate to the technology implemented
- May be required to interfaces with the client for technical and/or operational issues, and in support of the ADM/Delivery Lead/Account Chief Architect
- Provides Interlock with Engineering and Project teams to ensure Delivery standards are met, and implementations do not cause unplanned service disruptions
- As required for the specific technology be involved in day-to-day operations for the client environment; part of the Rapid-Response teams
- Use their specific technology knowledge to assist/work with all roles within AAT team
- Install and upgrade Operating System Level software, in accordance with the appropriate Change Management Procedure
- Ensure procedures are maintained in accordance with ISO standards and requirements
- Where designated, work in accordance with the Midrange Account Focus
- Ensure Software Licences are correctly maintained
- Ensure that team members work in accordance with all appropriate HPE and customer security and Quality policies and standards
- Process changes to Operating System level software, in accordance with the appropriate Change Management Procedure
Detailed Responsibilities
Configuration Management
- Has a clear understanding of the Client's business and application requirements, and how these relate to the technology implemented in the Client's environment (Safe Pair of Hands/trust)
- Interlocks with Engineering. Provides technical input for Aldea requests, Service Requests, NSSR and small enhancement work from an Operational perspective. Reviews Engineering designs prior to proposal to customer
- Interlocks with Project and Server Build teams. Reviews proposed project activity for potential impact to systems or environments already under Ops support, including reviews of implementation, verification testing, and backout plans, as required
- Responsible for identifying Single-Points-of-Failure on systems and environments under the SME's scope of responsibility. Presents these to the Team Leads/Capability Lead, along with associated risk, makes recommendations and works with relevant teams to remediate. (Particularly important for transitioned Legacy Servers)
- Responsible for ensuring systems are recoverable:
- Responsible for ensuring all systems under the SME's scope of responsibility have an OS Restore process in place and up-to-date
- Maintains a repository of all system-level software and firmware currently installed in the client's environment and required for server rebuild (particularly important for non-standard or Legacy Servers with software version dependencies).
- For environments with Disaster Recovery (DR) in-scope, responsible for maintaining the Capability portion of the DR plan and maintaining any external config information required by the DR process.
- Reviews Security, OS and Hardware flashes. Assesses potential impact to the environment, makes recommendations to Capability Lead and implements as required, in conjunction with Change Leads
- Feeds into the Technical Configuration Plan for the Capability and works closely with the Technical Configuration Lead
Service Level Management
- Ensure KPEs as defined by the client SLA's are adhered to maintaining the availability of services to meet these requirements
Capacity/Performance Management
- Works with Technical Capacity Lead to identify underlying performance issues and consult on capacity recommendations
Operations Management
- Works with the Technical Config Lead in analysing critical Security, OS and Hardware flashes and preparing instructions for rollout where appropriate
Incident Management
- Part of the Rapid Response Team, providing 7x24 standby technical support to resolve P1/P2 incidents (RtOP and non-RtOP)
- Provides technical support for non-RtOP incidents that cannot be resolved by the RST
- Investigate and resolve incidents and problems according to the appropriate Incident Management procedure. Liaise with hardware and software suppliers to resolve issues where appropriate