Project

General

Profile

Issues #7182

Inconsistency in sBrN10 reference to PIXIT-Rp13

Added by Nestor Orozco about 2 months ago. Updated 11 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Richard Schimmel
Due date:
06/10/2025 (11 days late)
Discuss in Upcoming Meeting:
No
Clause Reference:
61850 Standard:
Triggering Tissue:
Final Decision:
Initial Test Document:
Updated Test Document:
Test Case ID:
Closed Reason:
--Not Set---
Triggering Tissue 2:
Triggering Tissue 3:

Description

PIXIT-Rp13 is consistently utilized across all referring test cases where the RCB is pre-assigned (ResvTms = -1), with the exception of sBrN10.

Since sBrN10 exclusively involves BRCBs that are not pre-assigned, referencing Rp13 appears inconsistent.

sBrN10 addresses the scenario where ResvTms > 0 and the association is lost. Therefore, the test procedure should be updated to account for this scenario within ID Rp13 or a new PIXIT ID should be created.

Alternatives to fix PIXIT:

  1. Rp13: Does the server accept any client to configure/enable an RCB with:
    -BRCB.ResvTms = -1, or
    -URCB.Resv = T, or
    -BRCB.ResvTms > 0 AND loss of association?
  1. Create a new PIXIT ID entry and modify sBrN10 to reference it to

Also available in: Atom PDF