--- title: "Digital Servitization and DPS: the implementation cycle" slug: "digital-servitization-and-dps-implementation-cycle" updated: 2026-05-19T09:17:22Z published: 2026-05-19T09:17:22Z canonical: "learn.servitly.com/digital-servitization-and-dps-implementation-cycle" --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.servitly.com/llms.txt > Use this file to discover all available pages before exploring further. # Digital Servitization and DPS: the implementation cycle Digital Servitization is a long-term journey. So is building the DPS system that supports it. To approach it effectively, you need to: - Break the journey into distinct segments - Address each segment with a lean, continuous improvement approach This is why we designed a **cyclical implementation process**. --- ## The implementation cycle ![Digital Servitization implementation cycle](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/Digital%20Servitization%20implementation%20cycle.png) The cycle has five steps: ### 1. Pathway definition Chart your pathway by: - Choosing which segments to address - Deciding how to implement each one - Setting milestones We identified 11 proven segments you can select and combine. See [The segments to build your Digital Servitization pathway](/v1/docs/segments-to-build-your-digital-servitization-pathway) for the full list and description of each one. ### 2. Configuration Configure your DPS system to support the next milestone. This is where you use the Servitly Console to set up the features, rules, and interfaces you need. ### 3. Roll out Roll out your updated product-service system to: - Your internal organization - Channel partners (distributors, dealers) - End customers ### 4. Analysis Analyse the results of the rollout: - What worked well? - What did not work as expected? - Where can you improve? ### 5. Refinement Adjust your pathway based on what you learned: - Revise segments if needed - Update implementation choices - Move milestones Then return to **step 2** and start the next cycle. --- Why a cycle and not a linear project? Digital Servitization is not a one-time deployment. It is a long-term transformation, and the context around you changes continuously: markets evolve, customer needs shift, and competitors move. As you collect more data from your connected products and service operations, you also gain new perspective. You start to see things you could not see before, and this opens opportunities you were not aware of at the start. The cyclical approach lets you make progress steadily while staying flexible. --- ## Summary | Step | What you do | | --- | --- | | Pathway definition | Choose segments, implementation choices, and milestones | | Configuration | Configure your DPS in the Servitly Console | | Roll out | Deploy to your organization, partners, and customers | | Analysis | Review results and identify improvements | | Refinement | Adjust your pathway and restart the cycle |