Service Projects in IFS Cloud are intended for managing service-oriented work that is project-like in nature but does not require the full overhead of traditional project management. They are suitable for handling grouped service scopes such as installations, refurbishments, upgrades, or recurring service packages that need coordination across time, resources, and finances.
A Service Project acts as a parallel header that groups services and scopes originating from one or more Request Quotations and Requests. The services and tasks remain managed within their respective quotations or requests, while the Service Project provides a single coordination point for overview, planning, and monitoring. This approach enables cross-quotation and cross-request visibility without invoking full IFS Projects functionality.
Service Projects support planning at multiple levels, including the Service Project header, quotations, requests, and individual services or scopes. Both requested dates and planned dates can be defined, allowing organizations to distinguish between customer expectations and internal delivery plans.
During the quotation phase, resource demands can be defined as tentative and evaluated against available capacity by resource group or skill. These tentative demands are visible in capacity views and support early feasibility assessments without committing named resources. Upon customer acceptance, tentative demands are converted into confirmed demands, ensuring a controlled transition from planning to execution. Named resource allocation is performed closer to execution, allowing planners to balance flexibility with delivery certainty.
Financial and operational data is rolled up from tasks to services and further to the Service Project level. This provides consolidated visibility of planned and actual cost, revenue, and margin across all related work. The Service Project also enables monitoring of progress, exceptions, and overall delivery status for the grouped service scopes.
Service Projects are fully integrated with existing Request and Quotation processes in IFS Cloud. Services can be linked to a Service Project through a Request Quotation or directly through a Request when no quotation is required. When a quotation is accepted, the system generates the corresponding request structures while maintaining the Service Project linkage, ensuring continuity across planning and execution phases. This integration ensures that organizations can adopt Service Projects incrementally, extending their current service management workflows with enhanced planning, coordination, and visibility capabilities without disrupting established processes.
The status of a Service Project reflects the overall execution state of the connected services and is primarily driven by the status of the underlying requests. A Service Project is initially created in New status while work is being prepared. When execution starts on at least one connected request scope, the Service Project moves to Started. Once all connected request scopes are completed and no pending quotations remain, the Service Project is set to Completed, and can then be Closed when all related requests are fully closed.
A Service Project can be Cancelled before execution is finalized, provided that no invoice previews have been created. When cancelled, the Service Project is disconnected from the associated scopes. This status handling ensures that the Service Project always represents the consolidated and accurate state of the grouped service work.