Run
Operational support
Structured support for your users and your applications: requests logged, incidents handled, continuous service.
01Approach
Scope of work
- First- and second-line support
- Incident and request management
- Technical monitoring of applications
- Application support for users
- Remote maintenance and remote interventions
- IT estate management
02Expertise
User support
- Reception and qualification of requests
- Resolution of routine cases
- Controlled escalation to level 2
Monitoring and incidents
- Monitoring of availability and performance
- Alerts and intervention procedures
- Root-cause analysis and incident report
Operations and estate
- Inventory and tracking of the estate
- Updates and compliance of workstations
- Secure remote maintenance
03Methods & tools
Support backed by tools from end to end
We work in your tools when you have them, or we set up our own.
Ticketing
Every request is logged, prioritised and measured.
- Jira
- Redmine
- Prioritisation by criticality
- Tracking of response times
Monitoring
Detect problems before the user reports them.
- Grafana
- Alerts
- Dashboards
- Availability probes
Cloud & virtualisation
Reliable, reproducible environments.
- AWS
- OVH
- Docker
- Kubernetes
- Portainer
- Rancher
Knowledge & communication
Build up knowledge with every incident.
- Confluence
- Knowledge base
- Slack
- Periodic report
04Why iones
Support that reduces the number of incidents
Our goal is not to handle ever more tickets, but to make sure there are fewer of them.
Fast handling
Agreed response times according to criticality, and a French-speaking team reachable during your working hours.
Technical skills
Second-line support made up of developers and administrators, in direct contact with our development teams.
Service continuity
Documented procedures, a team working in pairs and a knowledge base: the service does not depend on a single person.
Continuous improvement
Analysis of recurring requests and underlying actions to address their cause, with figures tracked over time.
05Method
Our process for operational support
Step 01 Takeover
- Inventory of applications and estate
- Gathering existing procedures
- Definition of service levels
- Setting up secure access
Step 02 Setup
- Configuration of the ticketing tool
- Deployment of monitoring
- Writing the knowledge base
- Training the team on your context
Step 03 Day-to-day support
- Reception and qualification of requests
- Level 1 and level 2 resolution
- Remote maintenance and interventions
- Communication to users
Step 04 Steering and progress
- Periodic report and indicators
- Analysis of recurring causes
- Preventive action plan
- Follow-up committee