At a glance
The challenge
OptiSystems' teams work in remote, high-risk and tightly regulated locations, and take responsibility from installation and testing through to ongoing support. That means tickets, site visits, safety sign-offs, vehicle checks and spare parts all have to be recorded, and recorded the same way every time.
What we built
Fieldproxy built the system on the company's own forms: a ticket and visit flow with check-in and check-out locations, an on-site hazard and risk assessment signed by the supervisor, a daily vehicle inspection checklist with a cross-check signature, and spare part requests linked to the job.
The results
- Site safety assessment recorded before work starts
- Daily vehicle checks with driver and cross-check signatures
- Weekly vehicle inspection report generated as a PDF
- Spare parts and equipment tracked against each ticket
Want yours built around how you work, the same way?
Get DemoCritical infrastructure, demanding sites
OptiSystems is an ICT systems integrator. According to its website, it designs, deploys and maintains critical ICT infrastructure in three areas: aviation systems for airports and aviation facilities, enterprise infrastructure such as structured cabling, networking and security, and telecom infrastructure covering RF, fibre and wireless networks.
The company describes delivering projects in remote, high-risk and tightly regulated locations, and owning the full lifecycle from design and permitting to installation, testing and ongoing support. For a field team, that means a lot has to be captured on every job: who went, when they arrived and left, whether the site was safe to work on, what equipment was involved, which parts were needed, and whether the vehicle that got them there was roadworthy.
What we built: their forms, not a template
Rather than fitting OptiSystems into a standard job form, the system was set up around the checklists the company already used. The questions on the technician's phone are its own, from the hazard assessment to the individual vehicle checks.
Tickets and visits
Tickets with type, assignee, scheduled date and manager approval, and visits under each ticket with start and end times, check-in and check-out locations, photos, remarks and customer signature.
On-site safety checklist
Before work starts: the hazard and its risks, potential harm, controls in place, PPE, tools and equipment pre-checks, safe access to the work area, simultaneous operations and who to contact in an emergency, signed by the direct supervisor.
Close-out checks
After the work: tools and equipment checked, waste disposed of, materials safely stacked, and plant and machinery verified.
Daily vehicle inspection
Their roadworthiness list, from licence plates, hooter, lights and brakes to tyres, fluids, mirrors, seatbelts, the fire extinguisher and emergency kit, plus service kilometres and licence expiry, signed by the driver and cross-checked.
Spare parts and assets
Spare part requests raised from a visit and tracked to completion, and an asset register with product, serial number and customer, linked to tickets.
Reports that match how they check vehicles
Vehicle checks are only useful if someone can review them. The inspection is turned into a PDF report for each check, with the vehicle, driver, service details, every checklist item and both signatures. In September 2025 the report was rebuilt with a weekly view that lays out each checklist item against each day of the week for a vehicle, so gaps and failed items stand out at a glance.
The same approach runs through the rest of the system: tickets, visits, safety assessments and spare part requests are held together, so the office can see the full record of a job in one place instead of across separate forms.
How it went
Today
Vehicle inspections produce a ready PDF report.
