01Available
Field jobs
Field jobs is handled inside the Field Service record model with ownership, permission checks and a traceable state history.
Service operations
Field Service
Run Field Service work in one governed workspace.
Manage field jobs, technicians, routes, assets, checklists, parts, signatures and service evidence.
This application uses the shared İş Zamanı identity, permission and audit contracts. Acceptance conditions for provider- or regulation-dependent capabilities are stated separately on its detail page.
field service operating scopeSample view
Sample view
Field Service operating scope
Field jobs
Technicians
Contains no real customer data; generated to represent the application scope.
- Record
- Field jobs
- Workflow
- Technicians
- Control
- Routes
What it does
Field Service coverage
Listed capabilities follow the managed catalogue status and the plan, provider and acceptance conditions confirmed during activation.
02Available
Technicians
Technicians is handled inside the Field Service record model with ownership, permission checks and a traceable state history.
03Available
Routes
Routes is handled inside the Field Service record model with ownership, permission checks and a traceable state history.
04Available
Assets
Assets is handled inside the Field Service record model with ownership, permission checks and a traceable state history.
Workflow
Field Service operating scope
- 01
Prepare the operating context
Define ownership, permissions and the records needed for field jobs and technicians.
- 02
Run the work and decisions
Manage field jobs, technicians, routes, assets, checklists, parts, signatures and service evidence.
- 03
Verify the outcome
Field visits keep a continuous service record from planning through customer acceptance. Exceptions, approvals and resulting activities remain available for reporting and audit.
Who is it for?
Who is it for?
For teams that want to run daily work in one shared record system.
Service operations teams
Manage field jobs, technicians, routes, assets, checklists, parts, signatures and service evidence. The application keeps day-to-day records in the same governed context.
Team and process leaders
Field visits keep a continuous service record from planning through customer acceptance. Managers can review ownership, progress and exceptions without rebuilding the story from separate files.
Frequently asked questions
Frequently asked questions
What does Field Service cover?
Its published scope covers Field jobs, Technicians, Routes, Assets, Checklists and Parts. The exact limits and provider-dependent conditions are confirmed during activation.
Does it work with the other İş Zamanı applications?
Yes. It uses shared identity, permissions, activities, notifications, documents and audit contracts; record links are enabled where the business workflow requires them.
Field Service
See Field Service with your own workflow.
Share the roles, records, volume and connections in your target scenario; we will confirm the activation scope and acceptance steps together.