What Is JetVanguard Service Ops?
Service Ops is an aviation operations workspace for aircraft service providers. It gives a connected operational view of service work, assignments, schedules and team activity.
JetVanguard Service Ops is an aviation operations workspace for aircraft service providers and maintenance or service businesses. It organizes service work into assignments, provides an operational dashboard and an Operations Board, supports scheduling and team workload, and uses reusable checklists. It helps coordinate operational work. It is not a maintenance record, airworthiness record, aircraft logbook or regulatory record.
An operational view of service work
Aircraft service work can involve multiple assignments, technicians, schedules, locations, priorities, checklists, delays, handoffs and follow-up actions. Keeping all of that organized is an operational problem. Service Ops is an aviation operations workspace for aircraft service providers and aviation maintenance or service businesses. It gives that work a connected operational view rather than leaving it spread across separate messages, whiteboards and personal notes.
Operational dashboard
The dashboard can surface a picture of the day's operational activity. Depending on how an organization uses it, the dashboard can show: - assignments for the day - work in progress - waiting or blocked work - completed work - overdue work - people working - at-risk assignments - items waiting on something - upcoming assignments - team availability - operational alerts Not every organization will use every metric. The dashboard is a configurable operational view, not a fixed report.
Assignments
Service work can be organized into assignments or jobs. Depending on the assignment, information can include: - aircraft or tail information - aircraft type - customer reference - location or work location - assigned team member - date and time - estimated duration - priority - status - instructions - checklists - blockers - work activity - follow-up actions - completion summary - handoff notes - attachments - notes An assignment brings the relevant operational context together in one place.
Operations Board
The Operations Board provides a visual view of assignments as they move through operational stages. Assignments can move through stages such as: - Scheduled - Ready - In Progress - Waiting or Hold - Complete The board can provide views by status or by team member. This is an operational coordination tool. It is not a regulated maintenance-status system.
Scheduling
The schedule provides a resource and team view for coordinating assignments and technicians. It can help identify scheduling conflicts and organize work across team members. That makes it easier to see where capacity exists and where assignments may overlap or conflict.
Team and My Work
Service Ops distinguishes between a team view and an individual view. Managers and operations teams can see team workload and availability. Individual team members can see the work requiring their attention. That separation keeps each person focused on their own assignments while the broader team view remains available to those who need it.
Checklists
Reusable operational checklist templates can be applied to assignments. A checklist can help a team work through consistent steps for a type of assignment. These checklists are operational aids. They do not replace FAA-required maintenance procedures, inspection records, maintenance manuals or regulatory sign-offs. They help coordinate work. They are not regulatory inspection records.
Locations
Reusable aviation locations can be defined for the places where work happens. These can include facilities, airports, hangars, FBOs, customer sites and vendor sites. Having reusable locations makes assignments easier to organize and filter by where the work occurs.
History and reporting
Completed operational assignments can be searched through operational history. Reports can summarize operational activity such as team workload and aircraft activity. That gives a service business a way to review what has happened and understand patterns over time.
Service Ops is not a maintenance record
Service Ops operational activity and history are not a maintenance record, airworthiness record, aircraft logbook or regulatory record. Service Ops helps coordinate operational work. It does not replace required regulatory maintenance records or approved maintenance procedures. A service provider remains responsible for maintaining the regulatory records and approved data appropriate to the work performed.
Connected Workspace context
Service Ops exists inside JetVanguard Workspace. That means a service provider may also use broader Workspace capabilities such as client and contact management, conversations, estimates and invoices, payments, documents and related business tools. Not all of those functions are implemented directly inside the Service Ops module itself. Service Ops focuses on operational coordination, while the surrounding Workspace supports the broader business activity around the work.
An aircraft service provider has several assignments in progress across multiple technicians and locations. One assignment is waiting on a part. Another is blocked waiting on a customer decision. A third is ready to start but has not been assigned. Using Service Ops, the operations lead reviews the dashboard, sees the waiting and blocked work, reassigns the ready assignment, and updates the schedule to avoid a conflict. The team members each see their own work for the day, while the operations lead keeps the broader view. The operational coordination happens in one place, while the regulated maintenance records for the actual work remain where they belong.
