Know what is installed
Discover devices and establish an inventory of the infrastructure in scope.
Your fleet’s IT. Managed from shore.
Monitor devices, investigate faults and manage updates across your fleet. abela IT gives your team the tools and specialist support to keep the work moving.
Talk to an expertabela IT / Infrastructure managementThe estate.
The work. The record.
The work. The record.
- Discover
Identify the devices and software in scope.
- Maintain
Coordinate access, patches and maintenance windows.
- Report
Review the inventory and the state of the managed estate.
Capabilities
Know your systems. Keep them maintained.
Device discovery and inventory
Discovers the servers, workstations, network devices and software running across vessels and sites, and keeps that inventory current.
Bandwidth-aware remote access
Shore engineers connect to onboard systems over the vessel’s link to investigate faults and remediate them.
Patch and policy management
Patch deployment, approval rules and reboot windows are set centrally and applied across the fleet.
Estate reporting
Reports on inventory, patch state and IT policy across vessels and sites from one platform.
Inside the service
What’s included in abela IT.
abela automate brings remote, centralised management to abela IT: monitoring, access and maintenance. Its central management tools give shore engineers a consistent way to discover devices, investigate issues and apply IT policies across the vessels in scope.
Discovery, inventory and early warning
Network discovery keeps a record of installed hardware and software. Monitoring brings device health, changes and faults into the same working view, so maintenance can start with evidence from the vessel.
- Device discovery and network maps help keep the asset inventory current.
- Alerts and automatically generated tickets flag faults and unexpected devices for investigation.
- Hardware, software and estate-health reports support preventive maintenance and planning.
Remote access and remediation
Engineers can adjust session quality for a limited satellite connection and work in the background where the task allows. Access permissions define which systems they can reach and what changes they may make.
- Remote commands and file transfers support investigation and repair.
- Background sessions allow appropriate maintenance without taking over the user’s desktop.
- Windows Deployment Services supports workstation and server reconfiguration; prerequisites are reviewed for each installation.
Patch approvals and deployment
Central patch management brings Microsoft operating-system updates, approvals and reboot policies into one process. Fleet and vessel views show deployment status, helping the team identify systems still awaiting attention.
- Custom rules determine which patches are approved before deployment.
- Schedules and reboot windows are agreed around the vessel’s work.
- Bandwidth-aware scripts and planned deployment reduce avoidable use of the ship’s connection.
Virtual machines, backup and policy
The service can cover virtual-machine management, backup status and fleet IT policies alongside the physical estate. One Net reviews these responsibilities with the existing IT team rather than assuming that every system is included.
- Review hosted workloads, storage and recovery requirements.
- Establish who checks backup results and carries out recovery tests.
- Record access rights, change approvals, escalation routes and the reporting required by your organisation.
Choose the service relationship
A plan for the team you have.
Fully Managed places the agreed management work with One Net. Tier 2 gives your ICT team specialist escalation and additional capacity. Toolkit provides central tools for a team that retains operational control.
Compare monitoring, remote work and on-site support, with service hours and response commitments set out in your proposal.
Compare support plansDefine the service boundary
Give each maintenance task an owner.
Choose which tasks your team retains and where One Net provides tools or specialist support.
Before a change
Identify the affected assets, the approval owner and the permitted maintenance window.
Record restart restrictions and the route back if a change fails.
During the work
Confirm who performs remote actions and who coordinates any work on board or with another vendor.
Separate remote support from parts, licences, travel and on-site attendance.
After the change
Review completed tasks, failed updates and assets still awaiting intervention.
Close the work against an agreed result and give deferred actions a named owner.
Connected services
Connect abela IT to the wider operation.
Maintain Zwana’s onboard systems, add Sentrify protection and choose how One Net works alongside your own ICT team.
Plan your deployment
Your systems. A clear support plan.
Choose the systems to manage, the access engineers need and the changes your team approves. The support model follows those decisions.
Can our own ICT team stay involved?
Yes. IT Partnering includes fully managed, Tier 2 and toolkit approaches. The right model depends on the work your team wants to retain.
How is maintenance scheduled?
One Net reviews operating constraints, patch approvals and suitable maintenance windows with your team.
What is needed to begin?
An overview of your servers and devices, current access arrangements, known issues and management responsibilities.
Where responsibility sits
IT Partnering covers fully managed, Tier 2 and toolkit models. You choose how much your own ICT team retains, and the split is recorded before work begins.
Change is approved, not assumed
Patch approvals, deployment schedules and reboot policies are set with your team, so an update lands in a window the operation can absorb.
Talk to One Net
Put your fleet’s IT plan in place.
Bring your device inventory and the issues taking up your team’s time. We’ll help you choose the right mix of tools, remote maintenance and specialist support.
Discuss abela ITWhat to bring to the conversation
- The installed estate
- Servers, devices, virtual machines and backup arrangements.
- The operating windows
- Connectivity constraints, access permissions and maintenance schedules.
- The retained responsibilities
- What your own team manages and where One Net provides the expertise.