Introduction

In Omega 365, structuring and connecting scope items effectively is essential. To facilitate this, Omega 365 offers three distinct methods for linking scope items: Sub Scope, Related Scope Items, and Parent/Child relationships. Each approach has a unique purpose and can be used to create a clear, organized organized structure for manage the scope.

Sub Scope

Sub Scope creates a hierarchical connection by linking a main scope item to its smaller, related tasks or components. This method is particularly useful for breaking down an overarching item into actionable parts that can be tracked individually while still being tied to the primary goal.

For instance:

• Inspection Activity: Each finding or punch item discovered during the inspection can be registered as a sub-scope item, making it easier to address each detail within the main inspection scope.
• Interface Point: All interface queries related to a specific interface point are organized as sub-scope items, ensuring that every query is recorded and connected to the relevant interface.
• Ready for Commissioning Hand-Over: Each activity required for the hand-over is registered as a sub-scope item, providing a structured overview of all steps needed to complete the commissioning.

By using Sub Scope, teams can maintain visibility into every element within a larger task, making it easier to manage details without losing sight of the bigger picture.

Related Scope Items

Related Scope Items provide a flexible, non-hierarchical way to associate different scope items that might influence or support each other. Unlike Sub Scope and parent/child, this connection is not hierarchical; instead, it helps team members understand relationships across different areas. 

For instance: 

• Finding or punch items: Findings or punch items can be related to each other. E.g. when someone identifies a bug in the software, there could be similar bugs that are relevant to connect. 
• Overalapping tasks: For example, , electrical and mechanical installations may need to coordinate timing without being in a strict hierarchy. Marking them as related keeps all teams aligned on these connections.
• Risk Mitigation Measures: When certain tasks are designed to reduce project risks, marking them as related scope items can improve coordination and oversight. For instance, if there’s a risk mitigation plan involving safety checks and equipment maintenance, linking these as related scope items ensures that both measures are tracked and managed together, helping to address potential risks more effectively.
• Queries: Queries from different organisations, contractors and others, may be related - having them connected may improve the ability to provide consistent and good responses

Parent/Child Relationship

The Parent/Child relationship is used when a strong hierarchical connection is needed, with a clear dependency between items. The parent scope item represents a broader goal or task, while child scope items detail the necessary components or steps required to complete it. This setup provides visibility into dependencies, which can be particularly useful for managing projects with critical paths or sequential steps.
Example: When procuring some advanced equipment. 

• Parent: "Procuremnt of Equipment X"
  • Child scope items
    • Prepare technical specifications and requirements
    • Supplier evaluation and selection
    • Contract negotiation
    • Inspection and quality assruance
    • Devliery and installation planning

Choosing the Right Connection Method