Pipeline, zone, and location (PZL) FAQs

This page answers frequently asked questions about PZL.

1. What is a pipeline in nGenue?

   A pipeline in nGenue represents a physical or contractual natural gas transportation system through which gas flows from receipt points to delivery points. Pipelines form the backbone of scheduling, nominations, capacity tracking, pricing, and settlement processes. Every physical deal, nomination, or transportation activity in nGenue is associated with a configured pipeline.

2. Why is pipeline configuration mandatory in nGenue?

   Pipeline configuration is mandatory because it establishes the physical and commercial structure required for downstream processes such as deal creation, nominations, scheduling, imbalance management, and reporting. Without a properly configured pipeline, users cannot associate deals or locations correctly, which would break the operational workflow.

3. Who typically configures pipelines in nGenue?

   Pipelines are typically configured by system administrators or implementation teams during initial system setup. In some organizations, senior schedulers or operations leads may also be granted access to maintain pipeline configuration data, depending on governance policies.

4. Where do users configure pipelines in the application?

   Users can configure pipelines by navigating to Getting Started → Configure Pipeline from the nGenue administration or configuration menu. This screen acts as the master setup area for defining pipelines, zones, and associated locations.

5. Can multiple pipelines be configured in nGenue?

   Yes, nGenue supports configuring multiple pipelines, including interstate, intrastate, and regional pipelines. Each pipeline is maintained as a separate entity with its own zones, locations, and operational rules.

6. Are pipelines shared across all modules in nGenue?

   Yes, once configured, pipelines are shared across multiple modules such as Deal Management, Nominations, Scheduling, Settlements, and Reporting. Any change to pipeline configuration can impact multiple downstream workflows.

7. Can a pipeline be edited after it is created?

   Yes, pipeline details can be edited after creation. However, changes should be made cautiously, especially if the pipeline is already linked to active deals or historical data. Some critical attributes may be restricted from editing to preserve data integrity.

8. Can a pipeline be deactivated instead of deleted?

   Yes, pipelines can typically be marked inactive rather than deleted. Deactivation prevents new transactions from using the pipeline while preserving historical data for reporting and audit purposes.

9. What is a zone in the context of a pipeline?

   A zone represents a logical or operational subdivision within a pipeline. Zones are commonly used to group locations based on geography, pricing, operational constraints, or tariff definitions. They help simplify management of large pipelines with many receipt and delivery points.

10. Why are zones important in pipeline configuration?

    Zones are important because they:

    • Enable zone-based pricing and rate calculations
    • Support nomination and capacity constraints
    • Improve reporting and aggregation
    • Simplify deal and location selection

11. Can a pipeline have multiple zones?

    Yes, a single pipeline can have multiple zones, each representing a distinct segment of the pipeline. This is common for large interstate pipelines that span multiple regions or market areas.

12. Are zones mandatory for pipeline configuration?

    In most implementations, at least one zone is required for a pipeline. Even if a pipeline does not have formal zones operationally, a default or single zone is often created to maintain structural consistency.

13. How are zones used in deal creation?

    When creating physical deals, zones help determine:

    • Valid receipt and delivery locations
    • Applicable pricing points or indices
    • Transportation and tariff logic
      

14. Can zones be shared across different pipelines?

    No, zones are pipeline-specific. Each zone belongs to a single pipeline and cannot be reused across other pipelines. This ensures clear ownership and avoids configuration conflicts.

15. Can a zone be edited or renamed after creation?

    Yes, zone names and descriptions can typically be edited. However, renaming zones that are already in use should be done carefully, as it can impact reporting clarity and user understanding.

16. Can zones be deactivated?

    Yes, zones can be marked inactive if they are no longer used. Inactive zones are hidden from selection in transactional screens but remain available for historical reference.

17. What is a pipeline location in nGenue?

    A pipeline location represents a physical receipt point, delivery point, meter point, or interconnect on a pipeline. Locations are where gas physically enters or exits the pipeline system and are essential for scheduling and nominations.

18. Why are locations critical in pipeline configuration?

    Locations define the exact points of gas flow. They are used for:

    • Nominations and scheduling
    • Volume measurement and balancing
    • Deal association
    • Settlement and reporting

19. How are locations linked to pipelines and zones?

    Each location is:

    • Assigned to a specific pipeline
    • Mapped to a specific zone within that pipeline. This hierarchical relationship ensures accurate routing and aggregation.

20. Can the same location exist under multiple pipelines?

    No, a location is typically associated with only one pipeline. However, interconnects between pipelines are modeled as separate locations under each respective pipeline.

21. What types of locations can be configured?

    Common location types include:

    • Receipt points
    • Delivery points
    • City gates
    • Interconnects
    • Storage injection/withdrawal points

22. Are locations mandatory for creating physical deals?

    Yes, for physical deals and nominations, selecting a valid pipeline location is mandatory. Financial deals, such as swaps or futures, typically do not require locations.

23. Can locations be used in retail transactions?

    Yes, locations are frequently used in retail and LDC workflows, especially for city gates, meters, and delivery points serving end customers.

24. Can locations be edited after they are created?

    Yes, descriptive fields can be edited. However, changing core attributes such as pipeline or zone assignment may be restricted once the location is actively used.

25. Can locations be inactivated?

    Yes, locations can be marked inactive if they are no longer operational. Inactive locations cannot be selected for new deals or nominations but remain available for historical data.

26. What is the hierarchy between pipeline, zone, and location?

    The hierarchy is: Pipeline → Zone → Location A pipeline contains one or more zones, and each zone contains one or more locations.

27. Why is this hierarchy important?

    This hierarchy ensures:

    • Logical organization of physical assets
    • Accurate nomination and scheduling
    • Correct pricing and tariff application
    • Consistent reporting across modules

28. Can a location exist without a zone?

    No, locations must always belong to a zone. Even if zones are not operationally distinct, a default zone must exist.

29. Can deals reference zones directly?

    In most cases, deals reference locations, and zones are derived implicitly. However, zones may appear in reporting and filtering to group deals logically.

30. How does this configuration affect nominations?

    During nominations, the selected pipeline and location determine:

    • Valid flow paths
    • Capacity constraints
    • Scheduling timelines

31. How are pipelines used in nominations?

    Pipelines define the transportation path for gas movement. Nominations are submitted against specific pipelines and locations to communicate scheduled volumes.

32. How do zones impact pricing?

    Zones are often tied to:

    • Index pricing
    • Basis differentials
    • Tariff structures

33. How do locations affect settlement?

    Settlement calculations rely on actual metered volumes at locations. Accurate location configuration ensures correct volume reconciliation and billing.

34. Can pipeline configuration impact reporting?

    Yes, pipeline, zone, and location fields are commonly used in operational and financial reports. Misconfigured data can lead to incorrect aggregation or misleading reports.

35. Are pipelines visible in the Deal Management screen?

    Yes, pipelines appear as filters and columns in Deal Management for physical and retail deals. They help users quickly identify transportation paths.

36. What happens if a pipeline is deleted accidentally?

    In most setups, deletion is restricted. Instead, pipelines are deactivated to avoid breaking historical data and references.

37. Should pipelines be configured before deals are created?

    Yes, pipelines, zones, and locations should always be configured before creating deals, nominations, or retail setups.

38. How often should pipeline configuration be reviewed?

    Pipeline configuration should be reviewed:

    • During new pipeline onboarding
    • When zones or locations change operationally
    • During major releases or data migrations

39. Who can edit pipeline configuration?

    Access is controlled by roles and permissions. Typically, only administrators or authorized configuration users can modify pipelines, zones, and locations.

---