Work Tasks and Work Packages

Bundle recurring work tasks, schedule them, and turn them into operational transactions automatically.

Purpose

Work tasks and work packages provide the planning foundation for recurring service delivery. They help define recurring activities, bundle them into reusable structures, and trigger tickets or work orders at the right time.

Prerequisites

recurring activities, intervals, and responsible roles are defined from a business perspective
required references to properties, customers, projects, or contracts are available
it is clear whether tasks should create tickets, work orders, or grouped operational transactions

Functional focus

Define work tasks

Work tasks describe individual recurring activities with a validity period, property context, and business assignments. They also define whether execution should generate a ticket or a work order.

Work tasks can be assigned specifically to a property element such as an object, installation, or component. This means the planning source already defines which concrete part of the installed base the later service activity relates to.

Bundle and control work packages

Work packages combine multiple work tasks and provide their shared planning frame. This includes interval, start and end dates, responsibility, qualifications, and contract or project references. You can also decide whether the included tasks should generate separate operational transactions or one grouped transaction.

Work packages can also carry object, installation, or component references. This makes it possible to structure recurring services not only over time, but also along a concrete property context and later execute them with the correct customer, contract, or SLA background.

Upcoming work and task queue

The upcoming work view evaluates work tasks and work packages for a selected time range. This creates a task queue from which due tickets or work orders can be generated automatically. That makes recurring service execution predictable without recreating each case manually.

Hand-off to operational execution

Actual execution happens in the generated tickets or work orders. Work tasks and work packages therefore remain the planning and rules-based source, while downstream documents handle execution, documentation, and billing.

Outcome

Work tasks and work packages standardize recurring services, schedule them reliably, and hand them off into operational processes in a repeatable way. This reduces manual effort and creates a clean transition from planning to execution.