Scope-based deployment

Scope-based contracts describe a project methodology typically used in projects where the technical & functional goals are known & the technical path is clear. Good for more traditional deployments with design phase, project plan, execution plan, etc.


Scope-based contracts describe a project methodology typically used in projects where the technical and functional goals are known and the technical path is clear.



We start by creating a matrix in which all the responsibilities for all involved parties are clarified.


In the SOW (Scope Of Work) document, we then describe the system from the point of view of a user.

  • High-level description of the main functionality andUI from a user point of view
  • Includes project time plan aligning the main deployment goals and dependencies
  • Designed by a DataMiner System Architect
  • Requires final approval and forms the basis for the next stage


In a scope-based type of engagement, the scope and cost are determined during the sales cycle. A project time plan is set up in order to plan the delivery date. Delivery dates are guaranteed as long as all dependencies and prerequisites are fulfilled. If these are breached, the planned delivery date is no longer guaranteed. There is also very little room to change the scope of the project during its deployment. Functional changes during deployment are documented as change requests and could be subject to an extra cost and time impact compared to the original plan.

Project flow

In case not all variables are sure at the start of a project, you may wish to consider going for an Agile-based deployment instead.Note that during deployment it is not possible to mix scope-based and Agile-based methodologies.

Functional Design Specifications (FDS)

At the start of larger project deployments, a full FDS (Functional Design Specifications) document is designed by a Skyline team of experts together with the involved stakeholders at the integrator and/or user side.

  • Detailed description of how the solution will be configured in the DataMiner System, and of the architecture of the overall platform
  • Includes end-to-end user workflows, detailed visualizations and information on interfaces, the interaction between DataMiner and the different data sources, corner cases, etc.
  • Designed by a DataMiner System Architect
  • Requires final approval from the enduser for user-facing specifications (e.g. operator UI layout)
  • Basis for detailed project plan managed by dedicated DataMiner Project Manager
Workflow Description (WFD)

To describe the operational system in full detail, a WFD (Workflow Description)is drawn up, which can be compiled by Skyline, by a third-party system integrator or by the end user.

  • Detailed step-by-step description of how a service can be identified and subsequently tracked end to end throughout the operational ecosystem
  • Iterations go from component to component, and include routing/translations within the components
  • Available information is extracted in real time from underlying systems, and optionally complemented with auxiliary information (e.g. from a file, input from the user, from a database, etc.)
  • Defined independently of DataMiner and requires no knowledge of DataMiner
  • Includes all corner cases, bearing in mind devices that no longer respond, fallback scenarios, etc.
  • Requires final validation from the end user


The Acceptance Test Plan describes in detail how the implemented solution will be tested and validated and is clearly defined at the start of a project.

  • Typically based on the WFD
  • Provides detailed test cases that will be executed during final acceptance in order to determine compliance with the planned deliverables
  • Includes well-defined unambiguous success criteria to establish the test result
  • Drafted by Skyline, a third-party system integrator or the end user
  • Requires final approval from the end user and Skyline


Skyline’s Project Management is supported by a professional secured Collaboration Platform, where any involved stakeholder can follow up on the project deliverables, from a high-level birds-eye overview down to the tiniest detail of a dedicated task. This is an inclusive DataMiner Cloud-based service and can be accessed through the DataMiner Cloud Platform.

What can you do as an end user or system integrator?

If you are looking to be involved in the rollout of a DataMiner System, the following are typically responsibilities that you can assume:


In the WFD you can describe the operational system and how it should be controlled and behave, irrespective of DataMiner. You can for instance detail the exact steps to add a new service to your operational platform, including what to check and cross-check, the configuration settings that should be applied, the sequence in which these should be applied, etc. Make sure to include sufficient detail so that anyone can successfully execute the workflow, even without any knowledge about the operational platform. Also make sure to include possible corner cases, e.g. what if a device no longer responds, a device setting fails, an invalid setting is configured, etc.).


In the ATP you can describe in detail how the implemented solution should be tested and validated. Include all the tests and use cases that are required for a proper validation and to check operational readiness of the solution. For each test, you should provide a summary description of the test case, a step-by-step description of how to execute the test case, a detailed description of the expected outcome at any stage of the execution, and a clear, unambiguous description, in very tangible and measurable terms, of how success or failure of the test case is determined.


Your assistance with testing and validation throughout the implementation of the project can be key to successful final end-to-end acceptance testing. The testing and validation should cover all the software and its configuration, both on a micro/component level (e.g. a specific interface driver that is finished, a partial workflow, a specific use case, etc.) and on a macro/system level (e.g. end-to-end workflow testing, pre-testing of ATP test cases, etc.). However, keep in mind that to maintain the projected timeline, it is essential that all testing is done in a timely fashion and completed as thoroughly as possible in a single iteration. Full regression testing is also required at regular and reasonable time intervals.


  • We resource a vast number of world-class experts within the rollout of advanced end-to-end network management and orchestration solutions
  • We use seasoned streamlined procedures, methodology and tools to ensure a smooth delivery of the most complex solutions
  • We have unique industry expertise, specifically related to the management of broadcast and media ecosystems
  • We have a strong global presence to create strategic long-term partnerships with end users
  • DataMiner is 100% developed in-house, resulting in full ownership and commitment towards deliverables
  • We are a fully independent organization, eliminating any conflicts of interest with all involved parties, including system integrators and technology vendors