🔍
GCX146_Canada_Import_train - Thematically Grouped Rules
A dual-persona matrix designed specifically for Development scoping. Requirements are hierarchically structured by Epic → Module Program → Business Theme.
Unmapped Subprogram
Module Tracker: GCX146
1872 Validations & RulesModule Objective: No description provided from architecture analysis.
⚙️ General Logic & Formats
31 logic blocks
R-GCX146-cbl-00001
1:Input Message Retrieval
Process Rules
📊 Business Logic Narrative
When the process '1:Input Message Retrieval' is invoked, and assuming that the system is ready to process train manifest requests, when the system attempts to retrieve the next input message from the queue, the desired outcome is that if a message is available, processing continues; if no message is available, processing terminates.
💻 Technical Criteria
Given
The system is ready to process train manifest requests
When
The system attempts to retrieve the next input message from the queue
Then
If a message is available, processing continues; if no message is available, processing terminates
R-GCX146-cbl-00036
Call READQ to Access Message Queue
Action Rules
📊 Business Logic Narrative
When the process 'Call READQ to Access Message Queue' is invoked, and assuming that the system needs to process train manifest requests, when a readq call is made to access the message queue, the desired outcome is that the system attempts to read the next available message from the ims message queue.
💻 Technical Criteria
Given
The system needs to process train manifest requests
When
A READQ call is made to access the message queue
Then
The system attempts to read the next available message from the IMS message queue
R-GCX146-cbl-00038
Move Message to INPUT-MESSAGE Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Move Message to INPUT-MESSAGE Buffer' is invoked, and assuming that a message has been successfully retrieved from the queue, when the message needs to be prepared for processing, the desired outcome is that the message content is moved to the input-message buffer.
💻 Technical Criteria
Given
A message has been successfully retrieved from the queue
When
The message needs to be prepared for processing
Then
The message content is moved to the INPUT-MESSAGE buffer
R-GCX146-cbl-00052
Request Type = ADD?
Decision Rules
📊 Business Logic Narrative
When the process 'Request Type = ADD?' is invoked, and assuming that an input message is received for processing, when the request type field equals 'add', the desired outcome is that the system sets the aei-train-send flag and establishes add processing mode.
💻 Technical Criteria
Given
An input message is received for processing
When
The request type field equals 'ADD'
Then
The system sets the AEI-TRAIN-SEND flag and establishes ADD processing mode
R-GCX146-cbl-00053
Request Type = VERIFY?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Request Type = VERIFY?', assuming that an input message is received for processing and request type is not add, when the request type field equals 'verify', the desired outcome is that the system sets the aei-train-send flag and establishes verify processing mode.
💻 Technical Criteria
EXCLUDING
An input message is received for processing and request type is not ADD
When
The request type field equals 'VERIFY'
Then
The system sets the AEI-TRAIN-SEND flag and establishes VERIFY processing mode
R-GCX146-cbl-00054
Request Type = NOTIFY?
Decision Rules
📊 Business Logic Narrative
When the process 'Request Type = NOTIFY?' is invoked, and assuming that an input message is received for processing and request type is neither add nor verify, when the request type field equals 'notify', the desired outcome is that the system sets the aei-train-send flag and establishes notify processing mode.
💻 Technical Criteria
Given
An input message is received for processing and request type is neither ADD nor VERIFY
When
The request type field equals 'NOTIFY'
Then
The system sets the AEI-TRAIN-SEND flag and establishes NOTIFY processing mode
R-GCX146-cbl-00059
Set Processing Flags for Request Type
Process Rules
📊 Business Logic Narrative
When the process 'Set Processing Flags for Request Type' is invoked, and assuming that a valid request type (add, verify, or notify) has been identified and aei-train-send flag is set, when the system needs to configure processing parameters, the desired outcome is that the system sets all necessary processing flags to enable the appropriate business logic flow for the request type.
💻 Technical Criteria
Given
A valid request type (ADD, VERIFY, or NOTIFY) has been identified and AEI-TRAIN-SEND flag is set
When
The system needs to configure processing parameters
Then
The system sets all necessary processing flags to enable the appropriate business logic flow for the request type
R-GCX146-cbl-00072
ETA Date Within Allowed Range?
Validation Rules
📊 Business Logic Narrative
When the process 'ETA Date Within Allowed Range?' is invoked, and assuming that user is a special user (type 's') and eta date is provided, when eta date is compared against extended date range, the desired outcome is that eta date is accepted if within minus 30 to plus 5 days range or error 25 is generated if outside this range.
💻 Technical Criteria
Given
User is a special user (type 'S') AND ETA date is provided
When
ETA date is compared against extended date range
Then
ETA date is accepted if within minus 30 to plus 5 days range OR error 25 is generated if outside this range
R-GCX146-cbl-00073
ETA Date Within Allowed Range?
Validation Rules
📊 Business Logic Narrative
When the process 'ETA Date Within Allowed Range?' is invoked, and assuming that user is a standard user (not type 's') and eta date is provided, when eta date is compared against standard date range, the desired outcome is that eta date is accepted if within minus 2 to plus 2 days range or error 35 is generated if outside this range.
💻 Technical Criteria
Given
User is a standard user (not type 'S') AND ETA date is provided
When
ETA date is compared against standard date range
Then
ETA date is accepted if within minus 2 to plus 2 days range OR error 35 is generated if outside this range
R-GCX146-cbl-00168
Validate Against Commodity Standards
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Against Commodity Standards' is invoked, and assuming that commodity code has valid format structure, when system checks commodity code against commodity standards and reference data, the desired outcome is that system confirms commodity code is valid according to standards or identifies invalid commodity codes.
💻 Technical Criteria
Given
Commodity code has valid format structure
When
System checks commodity code against commodity standards and reference data
Then
System confirms commodity code is valid according to standards or identifies invalid commodity codes
R-GCX146-cbl-00304
Validate Message Parameters
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Message Parameters' is invoked, and assuming that a message command has been added to the processing queue, when the system validates message parameters, the desired outcome is that the system checks for valid parameters, proper formatting, and required data elements, marking the message as valid or invalid.
💻 Technical Criteria
Given
A message command has been added to the processing queue
When
The system validates message parameters
Then
The system checks for valid parameters, proper formatting, and required data elements, marking the message as valid or invalid
R-GCX146-cbl-00305
Process Queued Commands
Process Rules
📊 Business Logic Narrative
When the process 'Process Queued Commands' is invoked, and assuming that message parameters have been validated successfully, when the system processes queued commands, the desired outcome is that the system executes all queued cims commands in sequence for message delivery and processing.
💻 Technical Criteria
Given
Message parameters have been validated successfully
When
The system processes queued commands
Then
The system executes all queued CIMS commands in sequence for message delivery and processing
R-GCX146-cbl-01470
Replace Spaces with Zeros in Train Number
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros in Train Number' is invoked, and assuming that a train number component has been extracted from the input message, when the train number component contains one or more space characters, the desired outcome is that all space characters in the train number component are replaced with zero characters.
💻 Technical Criteria
Given
A train number component has been extracted from the input message
When
The train number component contains one or more space characters
Then
All space characters in the train number component are replaced with zero characters
R-GCX146-cbl-01471
Replace Spaces with Zeros in Train Day
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros in Train Day' is invoked, and assuming that a train day component has been extracted from the input message, when the train day component contains one or more space characters, the desired outcome is that all space characters in the train day component are replaced with zero characters.
💻 Technical Criteria
Given
A train day component has been extracted from the input message
When
The train day component contains one or more space characters
Then
All space characters in the train day component are replaced with zero characters
R-GCX146-cbl-01474
Replace Spaces with Zeros in Consist Number
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros in Consist Number' is invoked, and assuming that a consist number component has been extracted from the input message, when the consist number component contains one or more space characters, the desired outcome is that all space characters in the consist number component are replaced with zero characters.
💻 Technical Criteria
Given
A consist number component has been extracted from the input message
When
The consist number component contains one or more space characters
Then
All space characters in the consist number component are replaced with zero characters
R-GCX146-cbl-00345
Generate ETA Range Error 25/35
Validation Rules
📊 Business Logic Narrative
When the process 'Generate ETA Range Error 25/35' is invoked, and assuming that an eta date has been provided for train processing, when the eta date is outside the acceptable range for the user type (30 days before to 5 days after for supervisors, or 2 days before to 2 days after for others), the desired outcome is that the system generates error 25 for supervisor users or error 35 for other users.
💻 Technical Criteria
Given
An ETA date has been provided for train processing
When
The ETA date is outside the acceptable range for the user type (30 days before to 5 days after for supervisors, or 2 days before to 2 days after for others)
Then
The system generates error 25 for supervisor users or error 35 for other users
R-GCX146-cbl-00356
Log Error for Audit Trail
Policy Rules
📊 Business Logic Narrative
When the process 'Log Error for Audit Trail' is invoked, and assuming that an error has been processed and distributed, when the error processing is being completed, the desired outcome is that the system logs the error details in the audit trail for compliance and tracking purposes.
💻 Technical Criteria
Given
An error has been processed and distributed
When
The error processing is being completed
Then
The system logs the error details in the audit trail for compliance and tracking purposes
R-GCX146-cbl-00721
Error 25: ETA Date Range - Special Users
Validation Rules
📊 Business Logic Narrative
When the process 'Error 25: ETA Date Range - Special Users' is invoked, and assuming that a user with supervisor privileges ('s' type) is submitting an eta date, when the system validates the eta date against the allowed range, the desired outcome is that the system generates error 25 if the eta date is not between 30 days before and 5 days after the current date.
💻 Technical Criteria
Given
A user with supervisor privileges ('S' type) is submitting an ETA date
When
The system validates the ETA date against the allowed range
Then
The system generates Error 25 if the ETA date is not between 30 days before and 5 days after the current date
R-GCX146-cbl-00722
Error 35: ETA Date Range - Standard Users
Validation Rules
📊 Business Logic Narrative
When the process 'Error 35: ETA Date Range - Standard Users' is invoked, and assuming that a standard user (non-supervisor) is submitting an eta date, when the system validates the eta date against the allowed range, the desired outcome is that the system generates error 35 if the eta date is not between 2 days before and 2 days after the current date.
💻 Technical Criteria
Given
A standard user (non-supervisor) is submitting an ETA date
When
The system validates the ETA date against the allowed range
Then
The system generates Error 35 if the ETA date is not between 2 days before and 2 days after the current date
R-GCX146-cbl-01528
Use OM01247/AEI9999 as Backup
Policy Rules
📊 Business Logic Narrative
When the process 'Use OM01247/AEI9999 as Backup' is invoked, and assuming that fallback email recipients are being configured, when the system assigns backup email addresses, the desired outcome is that om01247 and aei9999 are set as backup email recipients.
💻 Technical Criteria
Given
Fallback email recipients are being configured
When
The system assigns backup email addresses
Then
OM01247 and AEI9999 are set as backup email recipients
R-GCX146-cbl-00846
Send First Message Batch
Action Rules
📊 Business Logic Narrative
When the process 'Send First Message Batch' is invoked, and assuming that a message has been split into multiple batches, when the system transmits the first batch, the desired outcome is that the first 699 lines are sent as the initial message segment.
💻 Technical Criteria
Given
A message has been split into multiple batches
When
The system transmits the first batch
Then
The first 699 lines are sent as the initial message segment
R-GCX146-cbl-01676
Set External FAX Addressing
Process Rules
📊 Business Logic Narrative
When the process 'Set External FAX Addressing' is invoked, and assuming that copy ids for fax have been configured, when the system sets up external addressing, the desired outcome is that external fax addresses are properly configured for message delivery.
💻 Technical Criteria
Given
Copy IDs for FAX have been configured
When
The system sets up external addressing
Then
External FAX addresses are properly configured for message delivery
R-GCX146-cbl-01681
Create Message Segments
Process Rules
📊 Business Logic Narrative
When the process 'Create Message Segments' is invoked, and assuming that a message exceeds the maximum line limit, when the system creates message segments, the desired outcome is that the message is divided into multiple segments that each comply with line limit requirements.
💻 Technical Criteria
Given
A message exceeds the maximum line limit
When
The system creates message segments
Then
The message is divided into multiple segments that each comply with line limit requirements
R-GCX146-cbl-01829
Set External FAX Addressing
Process Rules
📊 Business Logic Narrative
When the process 'Set External FAX Addressing' is invoked, and assuming that fax routing has been configured with copy ids, when the system sets up external addressing, the desired outcome is that the system configures external fax addressing parameters for proper message delivery.
💻 Technical Criteria
Given
FAX routing has been configured with copy IDs
When
The system sets up external addressing
Then
The system configures external FAX addressing parameters for proper message delivery
R-GCX146-cbl-01833
Line Counter > 699?
Validation Rules
📊 Business Logic Narrative
When the process 'Line Counter > 699?' is invoked, and assuming that email content is being processed line by line, when the line counter exceeds 699 lines in the current segment, the desired outcome is that the current segment must be sent and a new segment must be started.
💻 Technical Criteria
Given
Email content is being processed line by line
When
The line counter exceeds 699 lines in the current segment
Then
The current segment must be sent and a new segment must be started
R-GCX146-cbl-01839
Increment Line Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Line Counter' is invoked, and assuming that email content lines are being processed sequentially, when a line is processed and more lines remain, the desired outcome is that the line counter is incremented by 1 to track progress within current segment.
💻 Technical Criteria
Given
Email content lines are being processed sequentially
When
A line is processed and more lines remain
Then
The line counter is incremented by 1 to track progress within current segment
R-GCX146-cbl-00954
Execute D2554A-BUNCH-BILL-RTN
Action Rules
📊 Business Logic Narrative
When the process 'Execute D2554A-BUNCH-BILL-RTN' is invoked, and assuming that the bunch bill processing module has been invoked, when core bunch bill processing needs to be executed, the desired outcome is that the system executes the d2554a-bunch-bill-rtn routine to process the bunch bill.
💻 Technical Criteria
Given
The bunch bill processing module has been invoked
When
Core bunch bill processing needs to be executed
Then
The system executes the D2554A-BUNCH-BILL-RTN routine to process the bunch bill
R-GCX146-cbl-00962
Call D2554A-BUNCH-BILL-RTN
Action Rules
📊 Business Logic Narrative
When the process 'Call D2554A-BUNCH-BILL-RTN' is invoked, and assuming that bunch bill processing has been initialized, when the system needs to process cars in a bunch bill sequence, the desired outcome is that the d2554a-bunch-bill-rtn routine is called to handle the bunch bill processing.
💻 Technical Criteria
Given
Bunch bill processing has been initialized
When
The system needs to process cars in a bunch bill sequence
Then
The D2554A-BUNCH-BILL-RTN routine is called to handle the bunch bill processing
R-GCX146-cbl-01040
Finalize Bunch Bill Processing
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Bunch Bill Processing' is invoked, and assuming that all cars in the bunch bill have been processed, when the system finalizes bunch bill processing, the desired outcome is that processing results are consolidated and prepared for final output.
💻 Technical Criteria
Given
All cars in the bunch bill have been processed
When
The system finalizes bunch bill processing
Then
Processing results are consolidated and prepared for final output
R-GCX146-cbl-01574
Add to Numeric Sequence
Computation Rules
📊 Business Logic Narrative
When the process 'Add to Numeric Sequence' is invoked, and assuming that a character has been identified as numeric, when numeric sequence processing occurs, the desired outcome is that the numeric character is added to the current numeric sequence.
💻 Technical Criteria
Given
A character has been identified as numeric
When
Numeric sequence processing occurs
Then
The numeric character is added to the current numeric sequence
R-GCX146-cbl-01868
Add to Numeric Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Add to Numeric Sequence' is invoked, and assuming that a character has been identified as numeric, when the numeric sequence building process is executed, the desired outcome is that the numeric character is added to the current numeric sequence being organized.
💻 Technical Criteria
Given
A character has been identified as numeric
When
The numeric sequence building process is executed
Then
The numeric character is added to the current numeric sequence being organized
🏷️ CCN & Waybill Identification
599 logic blocks
R-GCX146-cbl-00011
11:Waybill Lookup Processing
Process Rules
📊 Business Logic Narrative
When the process '11:Waybill Lookup Processing' is invoked, and assuming that equipment requires waybill information for processing, when the system searches for waybill data, the desired outcome is that primary lookup uses fwcarget for latest waybill by car id; if not found, secondary lookup uses fwciio for car inquiry; if still not found, tertiary lookup uses fwiqio for waybill inquiry.
💻 Technical Criteria
Given
Equipment requires waybill information for processing
When
The system searches for waybill data
Then
Primary lookup uses FWCARGET for latest waybill by car ID; if not found, secondary lookup uses FWCIIO for car inquiry; if still not found, tertiary lookup uses FWIQIO for waybill inquiry
R-GCX146-cbl-00012
43:Waybill Inquiry Database Processing
Action Rules
📊 Business Logic Narrative
When the process '43:Waybill Inquiry Database Processing' is invoked, and assuming that primary waybill lookup has failed for equipment, when the system performs inquiry database processing, the desired outcome is that the system searches fwinq inquiry records and processes waybill sequences to extract equipment and shipment information.
💻 Technical Criteria
Given
Primary waybill lookup has failed for equipment
When
The system performs inquiry database processing
Then
The system searches FWINQ inquiry records and processes waybill sequences to extract equipment and shipment information
R-GCX146-cbl-00014
13:Load/Empty Status Processing
Validation Rules
📊 Business Logic Narrative
When the process '13:Load/Empty Status Processing' is invoked, and assuming that equipment has a designated load/empty status, when the system validates waybill requirements, the desired outcome is that empty cars (le = 'e') are allowed without waybill for add operations; loaded cars without waybill generate error 21 for add operations or report 'loaded car - no waybill' for verify operations.
💻 Technical Criteria
Given
Equipment has a designated load/empty status
When
The system validates waybill requirements
Then
Empty cars (LE = 'E') are allowed without waybill for ADD operations; loaded cars without waybill generate error 21 for ADD operations or report 'LOADED CAR - NO WAYBILL' for VERIFY operations
R-GCX146-cbl-00015
15:CCN Database Lookup
Action Rules
📊 Business Logic Narrative
When the process '15:CCN Database Lookup' is invoked, and assuming that equipment requires ccn validation for customs processing, when the system performs ccn database lookup, the desired outcome is that the system searches gcccrt database using equipment id and waybill information to retrieve existing ccn records and status.
💻 Technical Criteria
Given
Equipment requires CCN validation for customs processing
When
The system performs CCN database lookup
Then
The system searches GCCCRT database using equipment ID and waybill information to retrieve existing CCN records and status
R-GCX146-cbl-00016
16:CCN Status Validation
Validation Rules
📊 Business Logic Narrative
When the process '16:CCN Status Validation' is invoked, and assuming that a ccn record exists for equipment, when the system validates ccn status, the desired outcome is that ccn status must be 'sent', 'return', 'manual', 'release', 'ack', or 'csa-dlv'; invalid status generates error 24 for add operations or reports current status for verify operations.
💻 Technical Criteria
Given
A CCN record exists for equipment
When
The system validates CCN status
Then
CCN status must be 'SENT', 'RETURN', 'MANUAL', 'RELEASE', 'ACK', or 'CSA-DLV'; invalid status generates error 24 for ADD operations or reports current status for VERIFY operations
R-GCX146-cbl-00017
17:Train Assignment Validation
Validation Rules
📊 Business Logic Narrative
When the process '17:Train Assignment Validation' is invoked, and assuming that a ccn is being assigned to a train, when the system checks for existing train assignments, the desired outcome is that if the ccn is already assigned to a different train, error 13 is generated to prevent duplicate assignments.
💻 Technical Criteria
Given
A CCN is being assigned to a train
When
The system checks for existing train assignments
Then
If the CCN is already assigned to a different train, error 13 is generated to prevent duplicate assignments
R-GCX146-cbl-00018
19:Container Processing
Process Rules
📊 Business Logic Narrative
When the process '19:Container Processing' is invoked, and assuming that a flat car is carrying containers and waybill information is available, when the system processes container information, the desired outcome is that container ids are extracted from waybill cross-reference data and formatted using gcccarfm utility for 12-character format.
💻 Technical Criteria
Given
A flat car is carrying containers and waybill information is available
When
The system processes container information
Then
Container IDs are extracted from waybill cross-reference data and formatted using GCCCARFM utility for 12-character format
R-GCX146-cbl-00019
20:Empty/Exempted Equipment Processing
Process Rules
📊 Business Logic Narrative
When the process '20:Empty/Exempted Equipment Processing' is invoked, and assuming that equipment is classified as empty or exempted from ccn requirements, when the system processes the equipment, the desired outcome is that empty cars and exempted equipment types bypass ccn validation requirements and are processed with appropriate status indicators.
💻 Technical Criteria
Given
Equipment is classified as empty or exempted from CCN requirements
When
The system processes the equipment
Then
Empty cars and exempted equipment types bypass CCN validation requirements and are processed with appropriate status indicators
R-GCX146-cbl-00024
25:Canada Customs Trip Sheet Generation
Action Rules
📊 Business Logic Narrative
When the process '25:Canada Customs Trip Sheet Generation' is invoked, and assuming that add operation completed successfully without errors, when the system generates canada customs trip sheets, the desired outcome is that trip sheets include equipment details, waybill information, shipper/consignee data, and are sent to appropriate canadian customs terminals.
💻 Technical Criteria
Given
ADD operation completed successfully without errors
When
The system generates Canada customs trip sheets
Then
Trip sheets include equipment details, waybill information, shipper/consignee data, and are sent to appropriate Canadian customs terminals
R-GCX146-cbl-00031
32:Return CCN Creation
Action Rules
📊 Business Logic Narrative
When the process '32:Return CCN Creation' is invoked, and assuming that cargo requires return processing with new ccn creation, when the system creates return ccn records, the desired outcome is that new ccn records are created with 'return' status, ccn key format includes type(6) + carrier(105) + e + equipment_id + waybill_date + sequence, and audit trail entries are created via gcx105 spawning.
💻 Technical Criteria
Given
Cargo requires return processing with new CCN creation
When
The system creates return CCN records
Then
New CCN records are created with 'RETURN' status, CCN key format includes type(6) + carrier(105) + E + equipment_id + waybill_date + sequence, and audit trail entries are created via GCX105 spawning
R-GCX146-cbl-00032
33:Broker Notification Processing
Action Rules
📊 Business Logic Narrative
When the process '33:Broker Notification Processing' is invoked, and assuming that ccn keys starting with '6105' (excluding 'i' type) require broker notification, when the system processes broker notifications, the desired outcome is that notifications are sent to brokers only if current status is not 'return' or 'manual'; multiple notification methods are supported (x12, merlin, internet, fax, paper) with primary and secondary broker handling.
💻 Technical Criteria
Given
CCN keys starting with '6105' (excluding 'I' type) require broker notification
When
The system processes broker notifications
Then
Notifications are sent to brokers only if current status is not 'RETURN' or 'MANUAL'; multiple notification methods are supported (X12, Merlin, Internet, FAX, Paper) with primary and secondary broker handling
R-GCX146-cbl-00034
35:Special Manifest Processing
Action Rules
📊 Business Logic Narrative
When the process '35:Special Manifest Processing' is invoked, and assuming that canadian border processing requires special manifest creation, when the system processes special manifests, the desired outcome is that special manifest records are created with record type 'ca' (canadian), border code and station name from train data, and ccn keys are stored for processing.
💻 Technical Criteria
Given
Canadian border processing requires special manifest creation
When
The system processes special manifests
Then
Special manifest records are created with record type 'CA' (Canadian), border code and station name from train data, and CCN keys are stored for processing
R-GCX146-cbl-00035
36:CCN Usability Validation
Validation Rules
📊 Business Logic Narrative
When the process '36:CCN Usability Validation' is invoked, and assuming that a ccn exists for equipment validation, when the system validates ccn usability, the desired outcome is that ccn is usable if equipment id matches saved equipment id and (waybill number matches or new bond created flag = 'y'); if ccn exists with same equipment but different waybill and no new bond created, it's marked unusable; for verify operations, 'ccn found not usable' status message is added.
💻 Technical Criteria
Given
A CCN exists for equipment validation
When
The system validates CCN usability
Then
CCN is usable if equipment ID matches saved equipment ID AND (waybill number matches OR new bond created flag = 'Y'); if CCN exists with same equipment but different waybill and no new bond created, it's marked unusable; for VERIFY operations, 'CCN FOUND NOT USABLE' status message is added
R-GCX146-cbl-00116
Container Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Container Equipment' is invoked, and assuming that equipment identified as container type on flat car, when processing container equipment, the desired outcome is that container cross-reference data is processed through fwiq inquiry and container ids are extracted from waybill bottom lines.
💻 Technical Criteria
Given
Equipment identified as container type on flat car
When
Processing container equipment
Then
Container cross-reference data is processed through FWIQ inquiry and container IDs are extracted from waybill bottom lines
R-GCX146-cbl-00120
Validate Load/Empty Status Against Waybill
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Load/Empty Status Against Waybill' is invoked, and assuming that equipment has load/empty status from input and waybill data is available, when validating status consistency, the desired outcome is that status is verified against waybill data and inconsistencies are flagged for loaded cars marked as empty.
💻 Technical Criteria
Given
Equipment has load/empty status from input and waybill data is available
When
Validating status consistency
Then
Status is verified against waybill data and inconsistencies are flagged for loaded cars marked as empty
R-GCX146-cbl-00121
Set Load Status Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Set Load Status Flag' is invoked, and assuming that equipment status validation confirms loaded condition, when status is consistent between input and waybill, the desired outcome is that load status flag is set to indicate loaded equipment.
💻 Technical Criteria
Given
Equipment status validation confirms loaded condition
When
Status is consistent between input and waybill
Then
Load status flag is set to indicate loaded equipment
R-GCX146-cbl-00123
Process Equipment Segment
Process Rules
📊 Business Logic Narrative
When the process 'Process Equipment Segment' is invoked, and assuming that equipment has been classified and status determined, when processing equipment segment for train consist, the desired outcome is that equipment segment data is processed including waybill lookup, ccn validation, and status determination.
💻 Technical Criteria
Given
Equipment has been classified and status determined
When
Processing equipment segment for train consist
Then
Equipment segment data is processed including waybill lookup, CCN validation, and status determination
R-GCX146-cbl-00124
Build Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Build Equipment Record' is invoked, and assuming that equipment data has been extracted, formatted, classified, and validated, when building final equipment record, the desired outcome is that complete equipment record is constructed with id, type, status, waybill information, and validation results.
💻 Technical Criteria
Given
Equipment data has been extracted, formatted, classified, and validated
When
Building final equipment record
Then
Complete equipment record is constructed with ID, type, status, waybill information, and validation results
R-GCX146-cbl-00128
Z003-GU-FWIIROOT: Primary Waybill Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Z003-GU-FWIIROOT: Primary Waybill Lookup' is invoked, and assuming that an equipment id is provided for waybill lookup, when the system searches the primary waybill database (fwiiroot) using the equipment id, the desired outcome is that the system retrieves waybill data if found or proceeds to enhanced search if not found.
💻 Technical Criteria
Given
An equipment ID is provided for waybill lookup
When
The system searches the primary waybill database (FWIIROOT) using the equipment ID
Then
The system retrieves waybill data if found or proceeds to enhanced search if not found
R-GCX146-cbl-00129
Z420-GU-SHIPROOT-CAR: Enhanced Waybill Search
Action Rules
📊 Business Logic Narrative
When the process 'Z420-GU-SHIPROOT-CAR: Enhanced Waybill Search' is invoked, and assuming that primary waybill lookup has failed to find waybill data, when the system searches the enhanced waybill database (shiproot) using fwcarget with multiple search criteria, the desired outcome is that the system retrieves waybill information if available or proceeds to inquiry database search.
💻 Technical Criteria
Given
Primary waybill lookup has failed to find waybill data
When
The system searches the enhanced waybill database (SHIPROOT) using FWCARGET with multiple search criteria
Then
The system retrieves waybill information if available or proceeds to inquiry database search
R-GCX146-cbl-00130
Z450-GU-SHIPROOT-INQ: Inquiry Database Access
Action Rules
📊 Business Logic Narrative
When the process 'Z450-GU-SHIPROOT-INQ: Inquiry Database Access' is invoked, and assuming that both primary and enhanced waybill searches have failed, when the system accesses the inquiry database (fw-iq) for waybill information, the desired outcome is that the system searches for waybill data in the inquiry database or marks waybill as not found.
💻 Technical Criteria
Given
Both primary and enhanced waybill searches have failed
When
The system accesses the inquiry database (FW-IQ) for waybill information
Then
The system searches for waybill data in the inquiry database or marks waybill as not found
R-GCX146-cbl-00131
Set WS-WAYBILL-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-FOUND Flag' is invoked, and assuming that waybill data has been found in any of the searched databases, when the system processes the successful waybill lookup result, the desired outcome is that the system sets the waybill found flag to indicate successful retrieval.
💻 Technical Criteria
Given
Waybill data has been found in any of the searched databases
When
The system processes the successful waybill lookup result
Then
The system sets the waybill found flag to indicate successful retrieval
R-GCX146-cbl-00132
Set WS-WAYBILL-NOT-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-NOT-FOUND Flag' is invoked, and assuming that all waybill database searches (primary, enhanced, and inquiry) have been exhausted, when no waybill data is found for the equipment id in any database, the desired outcome is that the system sets the waybill not found flag to indicate unsuccessful retrieval.
💻 Technical Criteria
Given
All waybill database searches (primary, enhanced, and inquiry) have been exhausted
When
No waybill data is found for the equipment ID in any database
Then
The system sets the waybill not found flag to indicate unsuccessful retrieval
R-GCX146-cbl-00133
Extract Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Information' is invoked, and assuming that waybill data has been successfully located in one of the databases, when the system processes the retrieved waybill record, the desired outcome is that the system extracts relevant waybill information and prepares it for downstream processing.
💻 Technical Criteria
Given
Waybill data has been successfully located in one of the databases
When
The system processes the retrieved waybill record
Then
The system extracts relevant waybill information and prepares it for downstream processing
R-GCX146-cbl-00134
Search FWIIROOT using Equipment ID
Process Rules
📊 Business Logic Narrative
When the process 'Search FWIIROOT using Equipment ID' is invoked, and assuming that equipment id requires waybill lookup, when the system initiates waybill search process, the desired outcome is that the system searches databases in sequence: primary (fwiiroot), then enhanced (shiproot), then inquiry (fw-iq) until waybill is found or all options exhausted.
💻 Technical Criteria
Given
Equipment ID requires waybill lookup
When
The system initiates waybill search process
Then
The system searches databases in sequence: primary (FWIIROOT), then enhanced (SHIPROOT), then inquiry (FW-IQ) until waybill is found or all options exhausted
R-GCX146-cbl-01175
Primary Waybill Lookup - Search FWIIROOT using Equipment ID
Action Rules
📊 Business Logic Narrative
When the process 'Primary Waybill Lookup - Search FWIIROOT using Equipment ID' is invoked, and assuming that an equipment id is provided for waybill lookup, when the system searches the fwiiroot waybill database using the equipment id as the search key, the desired outcome is that the system retrieves the waybill record if it exists and sets the waybill found flag, or sets the waybill not found flag if no record exists.
💻 Technical Criteria
Given
An equipment ID is provided for waybill lookup
When
The system searches the FWIIROOT waybill database using the equipment ID as the search key
Then
The system retrieves the waybill record if it exists and sets the waybill found flag, or sets the waybill not found flag if no record exists
R-GCX146-cbl-01176
Prepare Equipment ID for Search
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Equipment ID for Search' is invoked, and assuming that raw equipment id data is available, when the system needs to perform a waybill database search, the desired outcome is that the equipment id is formatted and prepared as the search key for database access.
💻 Technical Criteria
Given
Raw equipment ID data is available
When
The system needs to perform a waybill database search
Then
The equipment ID is formatted and prepared as the search key for database access
R-GCX146-cbl-01177
Waybill Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Record Found?' is invoked, and assuming that a database search has been performed using equipment id, when the system evaluates the search results, the desired outcome is that the system determines if a waybill record was found and sets the appropriate status flag.
💻 Technical Criteria
Given
A database search has been performed using equipment ID
When
The system evaluates the search results
Then
The system determines if a waybill record was found and sets the appropriate status flag
R-GCX146-cbl-01178
Set WS-WAYBILL-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-FOUND Flag' is invoked, and assuming that a waybill record exists for the equipment id, when the database search successfully locates the record, the desired outcome is that the system sets the ws-waybill-found flag to indicate successful lookup.
💻 Technical Criteria
Given
A waybill record exists for the equipment ID
When
The database search successfully locates the record
Then
The system sets the WS-WAYBILL-FOUND flag to indicate successful lookup
R-GCX146-cbl-01179
Extract Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Information' is invoked, and assuming that a waybill record has been found in the database, when the system processes the retrieved record, the desired outcome is that all relevant waybill information is extracted from the database record.
💻 Technical Criteria
Given
A waybill record has been found in the database
When
The system processes the retrieved record
Then
All relevant waybill information is extracted from the database record
R-GCX146-cbl-01180
Move Waybill Data to Work Areas
Process Rules
📊 Business Logic Narrative
When the process 'Move Waybill Data to Work Areas' is invoked, and assuming that waybill information has been extracted from the database record, when the system needs to make the data available for processing, the desired outcome is that the waybill data is moved to appropriate work areas for subsequent business operations.
💻 Technical Criteria
Given
Waybill information has been extracted from the database record
When
The system needs to make the data available for processing
Then
The waybill data is moved to appropriate work areas for subsequent business operations
R-GCX146-cbl-01181
Set WS-WAYBILL-NOT-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-NOT-FOUND Flag' is invoked, and assuming that no waybill record exists for the equipment id, when the database search fails to locate any matching record, the desired outcome is that the system sets the ws-waybill-not-found flag to indicate unsuccessful lookup.
💻 Technical Criteria
Given
No waybill record exists for the equipment ID
When
The database search fails to locate any matching record
Then
The system sets the WS-WAYBILL-NOT-FOUND flag to indicate unsuccessful lookup
R-GCX146-cbl-01182
Prepare FWCARGET Search Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Prepare FWCARGET Search Parameters' is invoked, and assuming that a waybill search request is initiated for equipment, when the system prepares fwcarget search parameters, the desired outcome is that search parameters are initialized and prepared for database query execution.
💻 Technical Criteria
Given
A waybill search request is initiated for equipment
When
The system prepares FWCARGET search parameters
Then
Search parameters are initialized and prepared for database query execution
R-GCX146-cbl-01183
Set Equipment ID as Primary Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment ID as Primary Search Key' is invoked, and assuming that equipment information is available for waybill search, when the system sets the primary search key, the desired outcome is that equipment id is assigned as the primary search criterion for fwcarget lookup.
💻 Technical Criteria
Given
Equipment information is available for waybill search
When
The system sets the primary search key
Then
Equipment ID is assigned as the primary search criterion for FWCARGET lookup
R-GCX146-cbl-01185
Execute FWCARGET Database Call
Action Rules
📊 Business Logic Narrative
When the process 'Execute FWCARGET Database Call' is invoked, and assuming that search parameters are prepared with equipment id and additional criteria, when the system executes fwcarget database call, the desired outcome is that database query is performed against shiproot shipment database to locate waybill records.
💻 Technical Criteria
Given
Search parameters are prepared with equipment ID and additional criteria
When
The system executes FWCARGET database call
Then
Database query is performed against SHIPROOT shipment database to locate waybill records
R-GCX146-cbl-01186
Waybill Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Record Found?' is invoked, and assuming that fwcarget database call has been executed, when the system checks for waybill record existence, the desired outcome is that system determines if a matching waybill record was found and proceeds accordingly.
💻 Technical Criteria
Given
FWCARGET database call has been executed
When
The system checks for waybill record existence
Then
System determines if a matching waybill record was found and proceeds accordingly
R-GCX146-cbl-01187
Extract Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Information' is invoked, and assuming that a waybill record has been found in the database, when the system extracts waybill information, the desired outcome is that relevant waybill data is retrieved from the database record for processing.
💻 Technical Criteria
Given
A waybill record has been found in the database
When
The system extracts waybill information
Then
Relevant waybill data is retrieved from the database record for processing
R-GCX146-cbl-01188
Validate Waybill Data Quality
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Waybill Data Quality' is invoked, and assuming that waybill information has been extracted from the database record, when the system validates waybill data quality, the desired outcome is that system verifies that extracted waybill data is complete and meets quality standards.
💻 Technical Criteria
Given
Waybill information has been extracted from the database record
When
The system validates waybill data quality
Then
System verifies that extracted waybill data is complete and meets quality standards
R-GCX146-cbl-01189
Data Complete?
Decision Rules
📊 Business Logic Narrative
When the process 'Data Complete?' is invoked, and assuming that waybill data quality validation has been performed, when the system assesses data completeness, the desired outcome is that system determines if waybill data is complete and suitable for processing or if it should be treated as not found.
💻 Technical Criteria
Given
Waybill data quality validation has been performed
When
The system assesses data completeness
Then
System determines if waybill data is complete and suitable for processing or if it should be treated as not found
R-GCX146-cbl-01190
Set Waybill Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Waybill Found Flag' is invoked, and assuming that waybill data is determined to be complete and valid, when the system sets the waybill found flag, the desired outcome is that waybill found indicator is set to true to indicate successful waybill location.
💻 Technical Criteria
Given
Waybill data is determined to be complete and valid
When
The system sets the waybill found flag
Then
Waybill found indicator is set to true to indicate successful waybill location
R-GCX146-cbl-01191
Populate Equipment Waybill Fields
Process Rules
📊 Business Logic Narrative
When the process 'Populate Equipment Waybill Fields' is invoked, and assuming that waybill found flag has been set indicating successful waybill location, when the system populates equipment waybill fields, the desired outcome is that equipment record is updated with waybill information for subsequent processing.
💻 Technical Criteria
Given
Waybill found flag has been set indicating successful waybill location
When
The system populates equipment waybill fields
Then
Equipment record is updated with waybill information for subsequent processing
R-GCX146-cbl-01192
Set Waybill Not Found Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Waybill Not Found Flag', assuming that either no waybill record was found or waybill data is determined to be incomplete, when the system sets the waybill not found flag, the desired outcome is that waybill not found indicator is set to indicate unsuccessful waybill location for appropriate error handling.
💻 Technical Criteria
EXCLUDING
Either no waybill record was found OR waybill data is determined to be incomplete
When
The system sets the waybill not found flag
Then
Waybill not found indicator is set to indicate unsuccessful waybill location for appropriate error handling
R-GCX146-cbl-01433
Configure Date Range Parameters
Validation Rules
📊 Business Logic Narrative
When the process 'Configure Date Range Parameters' is invoked, and assuming that equipment search is being configured with temporal constraints, when date range parameters are being set, the desired outcome is that waybill date range and system date parameters are established to define the search time window.
💻 Technical Criteria
Given
Equipment search is being configured with temporal constraints
When
Date range parameters are being set
Then
Waybill date range and system date parameters are established to define the search time window
R-GCX146-cbl-01435
Set Waybill Key Parameters
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Waybill Key Parameters' is invoked, and assuming that equipment search needs to reference specific waybill documents, when waybill key parameters are being set, the desired outcome is that primary waybill key and secondary key index are configured for document reference.
💻 Technical Criteria
Given
Equipment search needs to reference specific waybill documents
When
Waybill key parameters are being set
Then
Primary waybill key and secondary key index are configured for document reference
R-GCX146-cbl-01436
Configure Car Type Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Configure Car Type Sequence' is invoked, and assuming that equipment search requires ordered sequence processing, when car type sequence is being configured, the desired outcome is that car sequence number and type sequence id are set to define retrieval order.
💻 Technical Criteria
Given
Equipment search requires ordered sequence processing
When
Car type sequence is being configured
Then
Car sequence number and type sequence ID are set to define retrieval order
R-GCX146-cbl-01582
Call FWCARGET Module
Action Rules
📊 Business Logic Narrative
When the process 'Call FWCARGET Module' is invoked, and assuming that an equipment id is available for waybill lookup, when the system calls fwcarget module with the equipment id as search key, the desired outcome is that the system should attempt to retrieve waybill data from the shipment database.
💻 Technical Criteria
Given
An equipment ID is available for waybill lookup
When
The system calls FWCARGET module with the equipment ID as search key
Then
The system should attempt to retrieve waybill data from the shipment database
R-GCX146-cbl-01584
Set WS-WAYBILL-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-FOUND Flag' is invoked, and assuming that fwcarget search operation was successful, when valid waybill data is available from the search result, the desired outcome is that the system should set the waybill found flag to indicate successful data retrieval.
💻 Technical Criteria
Given
FWCARGET search operation was successful
When
Valid waybill data is available from the search result
Then
The system should set the waybill found flag to indicate successful data retrieval
R-GCX146-cbl-01585
Extract Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Information' is invoked, and assuming that waybill data has been successfully retrieved from fwcarget, when the system processes the retrieved waybill record, the desired outcome is that the system should extract and store the waybill information in working storage variables.
💻 Technical Criteria
Given
Waybill data has been successfully retrieved from FWCARGET
When
The system processes the retrieved waybill record
Then
The system should extract and store the waybill information in working storage variables
R-GCX146-cbl-01586
Set WS-WAYBILL-NOT-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-NOT-FOUND Flag' is invoked, and assuming that fwcarget search operation failed to find waybill data, when no valid waybill record is returned from the search, the desired outcome is that the system should set the waybill not found flag and prepare for inquiry database fallback search.
💻 Technical Criteria
Given
FWCARGET search operation failed to find waybill data
When
No valid waybill record is returned from the search
Then
The system should set the waybill not found flag and prepare for inquiry database fallback search
R-GCX146-cbl-01715
Set Search Key for FWIIROOT Lookup
Process Rules
📊 Business Logic Narrative
When the process 'Set Search Key for FWIIROOT Lookup' is invoked, and assuming that a valid equipment id is available for database search, when the system prepares to search the fwiiroot database, the desired outcome is that the equipment id is set as the search key for the waybill root database lookup.
💻 Technical Criteria
Given
A valid equipment ID is available for database search
When
The system prepares to search the FWIIROOT database
Then
The equipment ID is set as the search key for the waybill root database lookup
R-GCX146-cbl-01718
Call FWCARGET Module
Action Rules
📊 Business Logic Narrative
When the process 'Call FWCARGET Module' is invoked, and assuming that an equipment id is provided for waybill lookup, when the fwcarget module is called with the equipment id parameter, the desired outcome is that the system should retrieve enhanced waybill data from the shiproot database and return comprehensive equipment and shipment details.
💻 Technical Criteria
Given
An equipment ID is provided for waybill lookup
When
The FWCARGET module is called with the equipment ID parameter
Then
The system should retrieve enhanced waybill data from the SHIPROOT database and return comprehensive equipment and shipment details
R-GCX146-cbl-01719
Prepare Search Criteria
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Search Criteria' is invoked, and assuming that a waybill lookup request is initiated for specific equipment, when the system prepares search criteria for the fwcarget module call, the desired outcome is that all required search parameters should be properly formatted and validated before the module call.
💻 Technical Criteria
Given
A waybill lookup request is initiated for specific equipment
When
The system prepares search criteria for the FWCARGET module call
Then
All required search parameters should be properly formatted and validated before the module call
R-GCX146-cbl-01720
Set Equipment ID Parameter
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment ID Parameter' is invoked, and assuming that an equipment id is available for waybill search, when the system sets the equipment id parameter for fwcarget module, the desired outcome is that the equipment id should be properly formatted and assigned as the primary search key.
💻 Technical Criteria
Given
An equipment ID is available for waybill search
When
The system sets the equipment ID parameter for FWCARGET module
Then
The equipment ID should be properly formatted and assigned as the primary search key
R-GCX146-cbl-01721
Set Additional Search Criteria
Process Rules
📊 Business Logic Narrative
When the process 'Set Additional Search Criteria' is invoked, and assuming that primary equipment id parameter is set and additional search refinement is needed, when the system configures additional search criteria for fwcarget module, the desired outcome is that all supplementary search parameters should be properly configured to optimize waybill retrieval results.
💻 Technical Criteria
Given
Primary equipment ID parameter is set and additional search refinement is needed
When
The system configures additional search criteria for FWCARGET module
Then
All supplementary search parameters should be properly configured to optimize waybill retrieval results
R-GCX146-cbl-01722
FWCARGET Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'FWCARGET Successful?' is invoked, and assuming that fwcarget module has been called with proper search criteria, when the system evaluates the success status of the fwcarget module call, the desired outcome is that if the call is successful, the system should proceed to retrieve enhanced waybill data, otherwise set waybill not found flag.
💻 Technical Criteria
Given
FWCARGET module has been called with proper search criteria
When
The system evaluates the success status of the FWCARGET module call
Then
If the call is successful, the system should proceed to retrieve enhanced waybill data, otherwise set waybill not found flag
R-GCX146-cbl-01723
Retrieve Enhanced Waybill Data
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Enhanced Waybill Data' is invoked, and assuming that fwcarget module call was successful and returned valid data, when the system retrieves enhanced waybill data from the module response, the desired outcome is that all available waybill information should be extracted and made available for equipment processing.
💻 Technical Criteria
Given
FWCARGET module call was successful and returned valid data
When
The system retrieves enhanced waybill data from the module response
Then
All available waybill information should be extracted and made available for equipment processing
R-GCX146-cbl-01724
Extract Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Details' is invoked, and assuming that enhanced waybill data has been successfully retrieved, when the system extracts equipment details from the waybill data, the desired outcome is that all relevant equipment information should be parsed and structured for subsequent business rule processing.
💻 Technical Criteria
Given
Enhanced waybill data has been successfully retrieved
When
The system extracts equipment details from the waybill data
Then
All relevant equipment information should be parsed and structured for subsequent business rule processing
R-GCX146-cbl-01725
Set Waybill Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Waybill Found Flag' is invoked, and assuming that equipment details have been successfully extracted from enhanced waybill data, when the system sets the waybill found flag, the desired outcome is that the waybill found indicator should be set to true to indicate successful waybill retrieval.
💻 Technical Criteria
Given
Equipment details have been successfully extracted from enhanced waybill data
When
The system sets the waybill found flag
Then
The waybill found indicator should be set to true to indicate successful waybill retrieval
R-GCX146-cbl-01726
Return Enhanced Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Return Enhanced Waybill Information' is invoked, and assuming that waybill found flag has been set and equipment details are available, when the system returns enhanced waybill information, the desired outcome is that all processed waybill and equipment data should be made available to the calling business process.
💻 Technical Criteria
Given
Waybill found flag has been set and equipment details are available
When
The system returns enhanced waybill information
Then
All processed waybill and equipment data should be made available to the calling business process
R-GCX146-cbl-01727
Set Waybill Not Found Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Waybill Not Found Flag', assuming that fwcarget module call was unsuccessful or returned no valid data, when the system sets the waybill not found flag, the desired outcome is that the waybill not found indicator should be set to indicate unsuccessful waybill retrieval.
💻 Technical Criteria
EXCLUDING
FWCARGET module call was unsuccessful or returned no valid data
When
The system sets the waybill not found flag
Then
The waybill not found indicator should be set to indicate unsuccessful waybill retrieval
R-GCX146-cbl-01728
Continue to Inquiry Database
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue to Inquiry Database', assuming that waybill not found flag has been set due to fwcarget failure, when the system continues to inquiry database lookup, the desired outcome is that the process should proceed to alternative waybill lookup methods using inquiry database.
💻 Technical Criteria
EXCLUDING
Waybill not found flag has been set due to FWCARGET failure
When
The system continues to inquiry database lookup
Then
The process should proceed to alternative waybill lookup methods using inquiry database
R-GCX146-cbl-01193
Initialize FW-IQ Inquiry Search
Process Rules
📊 Business Logic Narrative
When the process 'Initialize FW-IQ Inquiry Search' is invoked, and assuming that primary waybill search has failed to locate equipment information, when the system initiates fw-iq inquiry search process, the desired outcome is that fw-iq inquiry parameters are initialized and search is prepared for equipment lookup.
💻 Technical Criteria
Given
Primary waybill search has failed to locate equipment information
When
The system initiates FW-IQ inquiry search process
Then
FW-IQ inquiry parameters are initialized and search is prepared for equipment lookup
R-GCX146-cbl-01195
Inquiry Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Inquiry Record Found?' is invoked, and assuming that fw-iq database search has been completed for equipment id, when the system evaluates the search results, the desired outcome is that if inquiry record exists, proceed with data extraction; otherwise set waybill not found flag.
💻 Technical Criteria
Given
FW-IQ database search has been completed for equipment ID
When
The system evaluates the search results
Then
If inquiry record exists, proceed with data extraction; otherwise set waybill not found flag
R-GCX146-cbl-01196
Extract Waybill Information from Inquiry
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Information from Inquiry' is invoked, and assuming that valid inquiry record has been found in fw-iq database, when the system extracts waybill information from inquiry record, the desired outcome is that waybill data including numbers, dates, and related details are retrieved for processing.
💻 Technical Criteria
Given
Valid inquiry record has been found in FW-IQ database
When
The system extracts waybill information from inquiry record
Then
Waybill data including numbers, dates, and related details are retrieved for processing
R-GCX146-cbl-01197
Data Complete?
Validation Rules
📊 Business Logic Narrative
When the process 'Data Complete?' is invoked, and assuming that waybill information has been extracted from fw-iq inquiry record, when the system validates the completeness and quality of extracted data, the desired outcome is that if data is complete and valid, set waybill found flag; otherwise treat as waybill not found.
💻 Technical Criteria
Given
Waybill information has been extracted from FW-IQ inquiry record
When
The system validates the completeness and quality of extracted data
Then
If data is complete and valid, set waybill found flag; otherwise treat as waybill not found
R-GCX146-cbl-01198
Set Waybill Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Waybill Found Flag' is invoked, and assuming that inquiry data has been validated and found to be complete, when the system confirms successful waybill information retrieval, the desired outcome is that waybill found flag is set to indicate valid waybill data is available for equipment processing.
💻 Technical Criteria
Given
Inquiry data has been validated and found to be complete
When
The system confirms successful waybill information retrieval
Then
Waybill found flag is set to indicate valid waybill data is available for equipment processing
R-GCX146-cbl-01199
Extract Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Details' is invoked, and assuming that waybill found flag has been set and inquiry record is valid, when the system extracts equipment-specific details from inquiry data, the desired outcome is that equipment type, status, dimensions, and other relevant details are retrieved for processing.
💻 Technical Criteria
Given
Waybill found flag has been set and inquiry record is valid
When
The system extracts equipment-specific details from inquiry data
Then
Equipment type, status, dimensions, and other relevant details are retrieved for processing
R-GCX146-cbl-01205
Set Waybill Not Found Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Waybill Not Found Flag', assuming that either no inquiry record was found or extracted data failed validation, when the system determines waybill information is not available, the desired outcome is that waybill not found flag is set to indicate equipment lacks valid waybill data.
💻 Technical Criteria
EXCLUDING
Either no inquiry record was found OR extracted data failed validation
When
The system determines waybill information is not available
Then
Waybill not found flag is set to indicate equipment lacks valid waybill data
R-GCX146-cbl-01206
Log Inquiry Search Failure
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Inquiry Search Failure', assuming that waybill not found flag has been set due to inquiry search failure, when the system logs the unsuccessful search attempt, the desired outcome is that inquiry search failure is recorded with equipment id and search details for audit trail.
💻 Technical Criteria
EXCLUDING
Waybill not found flag has been set due to inquiry search failure
When
The system logs the unsuccessful search attempt
Then
Inquiry search failure is recorded with equipment ID and search details for audit trail
R-GCX146-cbl-01207
Proceed with Empty Equipment Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Proceed with Empty Equipment Processing', assuming that inquiry search failure has been logged and waybill not found flag is set, when the system continues with equipment processing, the desired outcome is that equipment is processed using empty equipment business rules and validation criteria.
💻 Technical Criteria
EXCLUDING
Inquiry search failure has been logged and waybill not found flag is set
When
The system continues with equipment processing
Then
Equipment is processed using empty equipment business rules and validation criteria
R-GCX146-cbl-01446
Set Container Sequence Number
Process Rules
📊 Business Logic Narrative
When the process 'Set Container Sequence Number' is invoked, and assuming that a container id has been validated as having correct format, when the system processes the valid container, the desired outcome is that the system assigns a sequence number to the container for proper ordering and identification within the flat car's container list.
💻 Technical Criteria
Given
A container ID has been validated as having correct format
When
The system processes the valid container
Then
The system assigns a sequence number to the container for proper ordering and identification within the flat car's container list
R-GCX146-cbl-01447
Store Container Information
Process Rules
📊 Business Logic Narrative
When the process 'Store Container Information' is invoked, and assuming that a container has been validated and assigned a sequence number, when the system completes container validation, the desired outcome is that the system stores the container information including id and sequence number for subsequent processing steps.
💻 Technical Criteria
Given
A container has been validated and assigned a sequence number
When
The system completes container validation
Then
The system stores the container information including ID and sequence number for subsequent processing steps
R-GCX146-cbl-00144
Retrieve Equipment Waybill Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Equipment Waybill Data' is invoked, and assuming that an equipment record requires load/empty status determination, when the system processes the equipment for waybill data retrieval, the desired outcome is that the system attempts to locate waybill information using the equipment identifier and sets waybill availability flag accordingly.
💻 Technical Criteria
Given
An equipment record requires load/empty status determination
When
The system processes the equipment for waybill data retrieval
Then
The system attempts to locate waybill information using the equipment identifier and sets waybill availability flag accordingly
R-GCX146-cbl-00145
Waybill Data Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Waybill Data Available?' is invoked, and assuming that equipment waybill data retrieval has been attempted, when the system checks if waybill data is available for the equipment, the desired outcome is that if waybill data exists, proceed with cargo analysis; if no waybill data exists, use default empty status processing.
💻 Technical Criteria
Given
Equipment waybill data retrieval has been attempted
When
The system checks if waybill data is available for the equipment
Then
If waybill data exists, proceed with cargo analysis; if no waybill data exists, use default empty status processing
R-GCX146-cbl-00146
Analyze Cargo Origin Information
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Cargo Origin Information' is invoked, and assuming that waybill data is available for equipment, when the system processes cargo origin information from the waybill, the desired outcome is that the system extracts and analyzes origin station, shipper information, and cargo classification data for load status determination.
💻 Technical Criteria
Given
Waybill data is available for equipment
When
The system processes cargo origin information from the waybill
Then
The system extracts and analyzes origin station, shipper information, and cargo classification data for load status determination
R-GCX146-cbl-00147
Analyze Cargo Destination Information
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Cargo Destination Information' is invoked, and assuming that cargo origin information has been analyzed, when the system processes cargo destination information from the waybill, the desired outcome is that the system extracts and analyzes destination station, consignee information, and delivery requirements for load status determination.
💻 Technical Criteria
Given
Cargo origin information has been analyzed
When
The system processes cargo destination information from the waybill
Then
The system extracts and analyzes destination station, consignee information, and delivery requirements for load status determination
R-GCX146-cbl-00152
Determine Container Load Status
Computation Rules
📊 Business Logic Narrative
When the process 'Determine Container Load Status' is invoked, and assuming that equipment is identified as container type with available waybill data, when the system processes container-specific load status determination, the desired outcome is that the system analyzes container cargo content, weight information, and commodity details to determine if container is loaded or empty.
💻 Technical Criteria
Given
Equipment is identified as container type with available waybill data
When
The system processes container-specific load status determination
Then
The system analyzes container cargo content, weight information, and commodity details to determine if container is loaded or empty
R-GCX146-cbl-00153
Determine Trailer Load Status
Computation Rules
📊 Business Logic Narrative
When the process 'Determine Trailer Load Status' is invoked, and assuming that equipment is identified as trailer type with available waybill data, when the system processes trailer-specific load status determination, the desired outcome is that the system analyzes trailer cargo content, weight information, and commodity details to determine if trailer is loaded or empty.
💻 Technical Criteria
Given
Equipment is identified as trailer type with available waybill data
When
The system processes trailer-specific load status determination
Then
The system analyzes trailer cargo content, weight information, and commodity details to determine if trailer is loaded or empty
R-GCX146-cbl-00154
Determine Rail Car Load Status
Computation Rules
📊 Business Logic Narrative
When the process 'Determine Rail Car Load Status' is invoked, and assuming that equipment is identified as rail car type with available waybill data, when the system processes rail car-specific load status determination, the desired outcome is that the system analyzes rail car cargo content, weight information, and commodity details to determine if rail car is loaded or empty.
💻 Technical Criteria
Given
Equipment is identified as rail car type with available waybill data
When
The system processes rail car-specific load status determination
Then
The system analyzes rail car cargo content, weight information, and commodity details to determine if rail car is loaded or empty
R-GCX146-cbl-00158
Set EMPTY Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set EMPTY Flag' is invoked, and assuming that equipment status validation confirms empty status or status validation error occurs or no waybill data available, when the system processes empty flag assignment, the desired outcome is that the system sets the empty indicator flag to indicate equipment does not carry cargo.
💻 Technical Criteria
Given
Equipment status validation confirms empty status OR status validation error occurs OR no waybill data available
When
The system processes empty flag assignment
Then
The system sets the empty indicator flag to indicate equipment does not carry cargo
R-GCX146-cbl-00162
Use Default Empty Status
Action Rules
📊 Business Logic Narrative
When the process 'Use Default Empty Status' is invoked, and assuming that no waybill data is available for the equipment, when the system processes default status assignment, the desired outcome is that the system assigns default empty status to the equipment and proceeds with empty flag processing.
💻 Technical Criteria
Given
No waybill data is available for the equipment
When
The system processes default status assignment
Then
The system assigns default empty status to the equipment and proceeds with empty flag processing
R-GCX146-cbl-00163
Access Waybill Record
Action Rules
📊 Business Logic Narrative
When the process 'Access Waybill Record' is invoked, and assuming that equipment requires commodity code validation and waybill data sources are available, when system attempts to access waybill record using equipment identifier, the desired outcome is that system retrieves waybill data from fwiiroot, shiproot, or fw-iq inquiry database in hierarchical order.
💻 Technical Criteria
Given
Equipment requires commodity code validation and waybill data sources are available
When
System attempts to access waybill record using equipment identifier
Then
System retrieves waybill data from FWIIROOT, SHIPROOT, or FW-IQ inquiry database in hierarchical order
R-GCX146-cbl-00164
Waybill Data Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Data Available?' is invoked, and assuming that system has attempted to access waybill record for equipment, when waybill lookup is performed against available data sources, the desired outcome is that system determines if valid waybill data is available for commodity processing or proceeds with default handling.
💻 Technical Criteria
Given
System has attempted to access waybill record for equipment
When
Waybill lookup is performed against available data sources
Then
System determines if valid waybill data is available for commodity processing or proceeds with default handling
R-GCX146-cbl-00165
Extract Commodity Code from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Extract Commodity Code from Waybill' is invoked, and assuming that valid waybill data is available for equipment, when system processes waybill record for commodity information, the desired outcome is that system extracts commodity code from waybill data fields for validation processing.
💻 Technical Criteria
Given
Valid waybill data is available for equipment
When
System processes waybill record for commodity information
Then
System extracts commodity code from waybill data fields for validation processing
R-GCX146-cbl-00166
Commodity Code Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Commodity Code Present?' is invoked, and assuming that commodity code extraction has been attempted from waybill data, when system evaluates extracted commodity code field, the desired outcome is that system determines if commodity code is present and not empty or proceeds with default commodity handling.
💻 Technical Criteria
Given
Commodity code extraction has been attempted from waybill data
When
System evaluates extracted commodity code field
Then
System determines if commodity code is present and not empty or proceeds with default commodity handling
R-GCX146-cbl-00167
Validate Commodity Code Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Commodity Code Format' is invoked, and assuming that commodity code is present in waybill data, when system validates commodity code format against standard requirements, the desired outcome is that system confirms commodity code format is valid or identifies format violations for error handling.
💻 Technical Criteria
Given
Commodity code is present in waybill data
When
System validates commodity code format against standard requirements
Then
System confirms commodity code format is valid or identifies format violations for error handling
R-GCX146-cbl-00170
Set Default/Empty Commodity Code
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Default/Empty Commodity Code', assuming that waybill data is unavailable or commodity code is not present in waybill, when system cannot extract valid commodity code, the desired outcome is that system sets default or empty commodity code value and continues equipment processing.
💻 Technical Criteria
EXCLUDING
Waybill data is unavailable OR commodity code is not present in waybill
When
System cannot extract valid commodity code
Then
System sets default or empty commodity code value and continues equipment processing
R-GCX146-cbl-00172
Extract Equipment ID from Train Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from Train Manifest' is invoked, and assuming that a train manifest contains equipment records with equipment ids, when the system processes equipment for ccn lookup, the desired outcome is that the equipment id is extracted and prepared for database search key construction.
💻 Technical Criteria
Given
A train manifest contains equipment records with equipment IDs
When
The system processes equipment for CCN lookup
Then
The equipment ID is extracted and prepared for database search key construction
R-GCX146-cbl-00173
Build CCN Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Build CCN Search Key' is invoked, and assuming that equipment id and waybill data are available, when the system needs to search for ccn records, the desired outcome is that a properly formatted search key is constructed for database lookup.
💻 Technical Criteria
Given
Equipment ID and waybill data are available
When
The system needs to search for CCN records
Then
A properly formatted search key is constructed for database lookup
R-GCX146-cbl-00174
Search GCCCRT Database
Action Rules
📊 Business Logic Narrative
When the process 'Search GCCCRT Database' is invoked, and assuming that a formatted ccn search key exists, when the system performs database lookup in gcccrt, the desired outcome is that the database is searched for matching ccn records.
💻 Technical Criteria
Given
A formatted CCN search key exists
When
The system performs database lookup in GCCCRT
Then
The database is searched for matching CCN records
R-GCX146-cbl-00175
CCN Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Record Found?' is invoked, and assuming that a database search has been performed for ccn records, when the system evaluates search results, the desired outcome is that the system determines if a matching ccn record was found or not found.
💻 Technical Criteria
Given
A database search has been performed for CCN records
When
The system evaluates search results
Then
The system determines if a matching CCN record was found or not found
R-GCX146-cbl-00176
Retrieve CCN Details
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve CCN Details' is invoked, and assuming that a ccn record exists for the equipment, when the system has located a matching ccn record, the desired outcome is that complete ccn record details are retrieved from the database.
💻 Technical Criteria
Given
A CCN record exists for the equipment
When
The system has located a matching CCN record
Then
Complete CCN record details are retrieved from the database
R-GCX146-cbl-00177
Check CCN Usability Flag
Validation Rules
📊 Business Logic Narrative
When the process 'Check CCN Usability Flag' is invoked, and assuming that a ccn record has been retrieved with equipment id and waybill information, when the system validates ccn usability, the desired outcome is that the ccn is determined usable if equipment id matches and either waybill number matches or new bond created flag is set to 'y'.
💻 Technical Criteria
Given
A CCN record has been retrieved with equipment ID and waybill information
When
The system validates CCN usability
Then
The CCN is determined usable if equipment ID matches and either waybill number matches or new bond created flag is set to 'Y'
R-GCX146-cbl-00178
CCN Usable?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Usable?' is invoked, and assuming that ccn usability validation has been performed, when the system evaluates usability results, the desired outcome is that the ccn is classified as either usable or unusable for processing.
💻 Technical Criteria
Given
CCN usability validation has been performed
When
The system evaluates usability results
Then
The CCN is classified as either usable or unusable for processing
R-GCX146-cbl-00179
Validate CCN Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CCN Status' is invoked, and assuming that a usable ccn record exists with a current status, when the system validates ccn status, the desired outcome is that the ccn status must be one of: 'sent', 'return', 'manual', 'release', 'ack', or 'csa-dlv' to be considered valid.
💻 Technical Criteria
Given
A usable CCN record exists with a current status
When
The system validates CCN status
Then
The CCN status must be one of: 'SENT', 'RETURN', 'MANUAL', 'RELEASE', 'ACK', or 'CSA-DLV' to be considered valid
R-GCX146-cbl-00180
Status Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Valid?' is invoked, and assuming that ccn status validation has been performed, when the system evaluates status validation results, the desired outcome is that the ccn status is classified as either valid or invalid for business processing.
💻 Technical Criteria
Given
CCN status validation has been performed
When
The system evaluates status validation results
Then
The CCN status is classified as either valid or invalid for business processing
R-GCX146-cbl-00181
Extract CCN Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract CCN Information' is invoked, and assuming that a ccn record with valid status exists, when the system processes the ccn record, the desired outcome is that relevant ccn information is extracted and prepared for equipment record integration.
💻 Technical Criteria
Given
A CCN record with valid status exists
When
The system processes the CCN record
Then
Relevant CCN information is extracted and prepared for equipment record integration
R-GCX146-cbl-00182
Set CCN Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set CCN Found Flag' is invoked, and assuming that ccn information has been successfully extracted, when the system updates processing status, the desired outcome is that the ccn found flag is set to indicate successful ccn lookup.
💻 Technical Criteria
Given
CCN information has been successfully extracted
When
The system updates processing status
Then
The CCN found flag is set to indicate successful CCN lookup
R-GCX146-cbl-00183
Add CCN to Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Add CCN to Equipment Record' is invoked, and assuming that valid ccn information exists and ccn found flag is set, when the system updates equipment records, the desired outcome is that ccn information is added to the equipment record for customs processing.
💻 Technical Criteria
Given
Valid CCN information exists and CCN found flag is set
When
The system updates equipment records
Then
CCN information is added to the equipment record for customs processing
R-GCX146-cbl-00184
CCN Lookup Complete
Process Rules
📊 Business Logic Narrative
When the process 'CCN Lookup Complete' is invoked, and assuming that ccn has been successfully added to equipment record, when the ccn lookup process concludes, the desired outcome is that the ccn lookup is marked as complete and processing continues.
💻 Technical Criteria
Given
CCN has been successfully added to equipment record
When
The CCN lookup process concludes
Then
The CCN lookup is marked as complete and processing continues
R-GCX146-cbl-00185
Set CCN Not Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set CCN Not Found Flag' is invoked, and assuming that database search returned no matching ccn records, when the system processes the no-match condition, the desired outcome is that the ccn not found flag is set to indicate absence of ccn record.
💻 Technical Criteria
Given
Database search returned no matching CCN records
When
The system processes the no-match condition
Then
The CCN not found flag is set to indicate absence of CCN record
R-GCX146-cbl-00186
Add Status Message: CCN Not Found
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add Status Message: CCN Not Found', assuming that ccn not found flag has been set, when the system updates status messaging, the desired outcome is that a status message indicating 'ccn not found' is added to the equipment processing record.
💻 Technical Criteria
EXCLUDING
CCN not found flag has been set
When
The system updates status messaging
Then
A status message indicating 'CCN Not Found' is added to the equipment processing record
R-GCX146-cbl-00187
Set CCN Unusable Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set CCN Unusable Flag' is invoked, and assuming that a ccn record exists but fails usability validation or has invalid status, when the system processes the unusable condition, the desired outcome is that the ccn unusable flag is set to indicate the ccn cannot be used for processing.
💻 Technical Criteria
Given
A CCN record exists but fails usability validation or has invalid status
When
The system processes the unusable condition
Then
The CCN unusable flag is set to indicate the CCN cannot be used for processing
R-GCX146-cbl-00188
Add Status Message: CCN Found Not Usable
Process Rules
📊 Business Logic Narrative
When the process 'Add Status Message: CCN Found Not Usable' is invoked, and assuming that ccn unusable flag has been set, when the system updates status messaging, the desired outcome is that a status message indicating 'ccn found not usable' is added to the equipment processing record.
💻 Technical Criteria
Given
CCN unusable flag has been set
When
The system updates status messaging
Then
A status message indicating 'CCN Found Not Usable' is added to the equipment processing record
R-GCX146-cbl-00189
Continue Processing
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Continue Processing', assuming that ccn lookup process has completed with any outcome (found, not found, or unusable), when the system proceeds with equipment processing, the desired outcome is that equipment processing continues with appropriate ccn status and messaging.
💻 Technical Criteria
EXCLUDING
CCN lookup process has completed with any outcome (found, not found, or unusable)
When
The system proceeds with equipment processing
Then
Equipment processing continues with appropriate CCN status and messaging
R-GCX146-cbl-00190
Retrieve CCN Record from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve CCN Record from Database' is invoked, and assuming that a ccn number needs to be validated for processing, when the system attempts to retrieve the ccn record from the gcccrt database, the desired outcome is that the ccn record is retrieved if it exists in the database.
💻 Technical Criteria
Given
A CCN number needs to be validated for processing
When
The system attempts to retrieve the CCN record from the GCCCRT database
Then
The CCN record is retrieved if it exists in the database
R-GCX146-cbl-00191
CCN Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Record Found?' is invoked, and assuming that a ccn lookup has been performed in the database, when the system checks if a ccn record was found, the desired outcome is that if no ccn record is found, the ccn is marked as unusable and validation stops.
💻 Technical Criteria
Given
A CCN lookup has been performed in the database
When
The system checks if a CCN record was found
Then
If no CCN record is found, the CCN is marked as unusable and validation stops
R-GCX146-cbl-00192
Check CCN Usability Flag
Validation Rules
📊 Business Logic Narrative
When the process 'Check CCN Usability Flag' is invoked, and assuming that a ccn record exists in the database, when the system evaluates the ccn usability flag, the desired outcome is that the usability status is determined based on the flag value.
💻 Technical Criteria
Given
A CCN record exists in the database
When
The system evaluates the CCN usability flag
Then
The usability status is determined based on the flag value
R-GCX146-cbl-00193
Bond Created Flag = 'Y'?
Validation Rules
📊 Business Logic Narrative
When the process 'Bond Created Flag = 'Y'?' is invoked, and assuming that a ccn record is being evaluated for usability, when the bond created flag equals 'y', the desired outcome is that the ccn is marked as unusable and cannot be processed further.
💻 Technical Criteria
Given
A CCN record is being evaluated for usability
When
The bond created flag equals 'Y'
Then
The CCN is marked as unusable and cannot be processed further
R-GCX146-cbl-00194
CCN Marked as Unusable
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'CCN Marked as Unusable', assuming that a ccn fails validation criteria (record not found or bond created flag is 'y'), when the system determines the ccn cannot be processed, the desired outcome is that the ccn is marked as unusable for customs processing.
💻 Technical Criteria
EXCLUDING
A CCN fails validation criteria (record not found or bond created flag is 'Y')
When
The system determines the CCN cannot be processed
Then
The CCN is marked as unusable for customs processing
R-GCX146-cbl-00195
Check Current CCN Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Current CCN Status' is invoked, and assuming that a ccn is determined to be usable for processing, when the system checks the current ccn status, the desired outcome is that the current status is evaluated to determine the appropriate status mapping.
💻 Technical Criteria
Given
A CCN is determined to be usable for processing
When
The system checks the current CCN status
Then
The current status is evaluated to determine the appropriate status mapping
R-GCX146-cbl-00196
Status = RELEASE?
Decision Rules
📊 Business Logic Narrative
When the process 'Status = RELEASE?' is invoked, and assuming that a ccn has a current status that needs evaluation, when the ccn status equals 'release', the desired outcome is that the system proceeds to check transit status for further status refinement.
💻 Technical Criteria
Given
A CCN has a current status that needs evaluation
When
The CCN status equals 'RELEASE'
Then
The system proceeds to check transit status for further status refinement
R-GCX146-cbl-00197
Check Transit Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Transit Status' is invoked, and assuming that a ccn has release status, when the system checks the transit status, the desired outcome is that the transit status is evaluated to determine the appropriate final status.
💻 Technical Criteria
Given
A CCN has RELEASE status
When
The system checks the transit status
Then
The transit status is evaluated to determine the appropriate final status
R-GCX146-cbl-00198
Transit Status = E or Z?
Decision Rules
📊 Business Logic Narrative
When the process 'Transit Status = E or Z?' is invoked, and assuming that a ccn has release status and transit status is being evaluated, when the transit status equals 'e' or 'z', the desired outcome is that the ccn status is set to 'export'.
💻 Technical Criteria
Given
A CCN has RELEASE status and transit status is being evaluated
When
The transit status equals 'E' or 'Z'
Then
The CCN status is set to 'EXPORT'
R-GCX146-cbl-00199
Set Status to EXPORT
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to EXPORT' is invoked, and assuming that a ccn has release status and transit status of 'e' or 'z', when the system determines export status mapping is required, the desired outcome is that the ccn status is set to 'export'.
💻 Technical Criteria
Given
A CCN has RELEASE status and transit status of 'E' or 'Z'
When
The system determines export status mapping is required
Then
The CCN status is set to 'EXPORT'
R-GCX146-cbl-00200
Transit Status = S.A.R.?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Status = S.A.R.?', assuming that a ccn has release status and transit status is not 'e' or 'z', when the transit status equals 's.a.r.', the desired outcome is that the ccn status is set to 's.a.r.'.
💻 Technical Criteria
EXCLUDING
A CCN has RELEASE status and transit status is not 'E' or 'Z'
When
The transit status equals 'S.A.R.'
Then
The CCN status is set to 'S.A.R.'
R-GCX146-cbl-00201
Set Status to S.A.R.
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to S.A.R.' is invoked, and assuming that a ccn has release status and transit status of 's.a.r.', when the system determines sar status mapping is required, the desired outcome is that the ccn status is set to 's.a.r.'.
💻 Technical Criteria
Given
A CCN has RELEASE status and transit status of 'S.A.R.'
When
The system determines SAR status mapping is required
Then
The CCN status is set to 'S.A.R.'
R-GCX146-cbl-00202
Keep Status as RELEASE
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Keep Status as RELEASE', assuming that a ccn has release status and transit status is not 'e', 'z', or 's.a.r.', when no special status mapping is required, the desired outcome is that the ccn status remains as 'release'.
💻 Technical Criteria
EXCLUDING
A CCN has RELEASE status and transit status is not 'E', 'Z', or 'S.A.R.'
When
No special status mapping is required
Then
The CCN status remains as 'RELEASE'
R-GCX146-cbl-00203
Transit Status = T?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Status = T?', assuming that a ccn does not have release status, when the transit status equals 't', the desired outcome is that the ccn status is set to 'transit'.
💻 Technical Criteria
EXCLUDING
A CCN does not have RELEASE status
When
The transit status equals 'T'
Then
The CCN status is set to 'TRANSIT'
R-GCX146-cbl-00204
Set Status to TRANSIT
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to TRANSIT' is invoked, and assuming that a ccn has transit status 't', when the system determines transit status mapping is required, the desired outcome is that the ccn status is set to 'transit'.
💻 Technical Criteria
Given
A CCN has transit status 'T'
When
The system determines transit status mapping is required
Then
The CCN status is set to 'TRANSIT'
R-GCX146-cbl-00205
Transit Status = R?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Status = R?', assuming that a ccn does not have release status and transit status is not 't', when the transit status equals 'r', the desired outcome is that the ccn status is set to 'return'.
💻 Technical Criteria
EXCLUDING
A CCN does not have RELEASE status and transit status is not 'T'
When
The transit status equals 'R'
Then
The CCN status is set to 'RETURN'
R-GCX146-cbl-00206
Set Status to RETURN
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to RETURN' is invoked, and assuming that a ccn has transit status 'r', when the system determines return status mapping is required, the desired outcome is that the ccn status is set to 'return'.
💻 Technical Criteria
Given
A CCN has transit status 'R'
When
The system determines return status mapping is required
Then
The CCN status is set to 'RETURN'
R-GCX146-cbl-00207
Keep Current Status
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Keep Current Status', assuming that a ccn does not match any specific status mapping criteria, when no status transformation is required, the desired outcome is that the ccn retains its current status.
💻 Technical Criteria
EXCLUDING
A CCN does not match any specific status mapping criteria
When
No status transformation is required
Then
The CCN retains its current status
R-GCX146-cbl-00208
CCN Status Validated
Process Rules
📊 Business Logic Narrative
When the process 'CCN Status Validated' is invoked, and assuming that a ccn has been processed through status validation logic, when status mapping is complete, the desired outcome is that the ccn has a validated status for further processing.
💻 Technical Criteria
Given
A CCN has been processed through status validation logic
When
Status mapping is complete
Then
The CCN has a validated status for further processing
R-GCX146-cbl-00209
Add Unusable Status Message
Action Rules
📊 Business Logic Narrative
When the process 'Add Unusable Status Message' is invoked, and assuming that a ccn has been marked as unusable, when the system needs to communicate the unusable status, the desired outcome is that an unusable status message is added to the processing results.
💻 Technical Criteria
Given
A CCN has been marked as unusable
When
The system needs to communicate the unusable status
Then
An unusable status message is added to the processing results
R-GCX146-cbl-00210
CCN Status Validation Complete
Process Rules
📊 Business Logic Narrative
When the process 'CCN Status Validation Complete' is invoked, and assuming that a ccn has been processed through all validation steps, when all validation logic has been executed, the desired outcome is that the ccn status validation process is complete.
💻 Technical Criteria
Given
A CCN has been processed through all validation steps
When
All validation logic has been executed
Then
The CCN status validation process is complete
R-GCX146-cbl-00211
Retrieve CCN Record from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve CCN Record from Database' is invoked, and assuming that a ccn key exists for equipment being processed, when the system attempts to retrieve the ccn record from the gcccrt database, the desired outcome is that the ccn record is successfully retrieved or marked as not found for further processing.
💻 Technical Criteria
Given
A CCN key exists for equipment being processed
When
The system attempts to retrieve the CCN record from the GCCCRT database
Then
The CCN record is successfully retrieved or marked as not found for further processing
R-GCX146-cbl-00212
CCN Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Record Found?' is invoked, and assuming that a ccn retrieval operation has been performed, when the system checks if a ccn record was found in the database, the desired outcome is that if no ccn record exists, the validation process ends; if ccn record exists, proceed to check current train assignment.
💻 Technical Criteria
Given
A CCN retrieval operation has been performed
When
The system checks if a CCN record was found in the database
Then
If no CCN record exists, the validation process ends; if CCN record exists, proceed to check current train assignment
R-GCX146-cbl-00213
Check Current Train Assignment
Validation Rules
📊 Business Logic Narrative
When the process 'Check Current Train Assignment' is invoked, and assuming that a valid ccn record exists in the database, when the system checks the current train assignment field in the ccn record, the desired outcome is that the system identifies whether the ccn is currently assigned to any train and retrieves the train identification.
💻 Technical Criteria
Given
A valid CCN record exists in the database
When
The system checks the current train assignment field in the CCN record
Then
The system identifies whether the CCN is currently assigned to any train and retrieves the train identification
R-GCX146-cbl-00214
CCN Already Assigned to Different Train?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Already Assigned to Different Train?' is invoked, and assuming that a ccn record has a current train assignment, when the system compares the existing train assignment with the current train being processed, the desired outcome is that if the ccn is assigned to a different train, proceed to validate assignment conflict; if not assigned to a different train, check ccn transit status.
💻 Technical Criteria
Given
A CCN record has a current train assignment
When
The system compares the existing train assignment with the current train being processed
Then
If the CCN is assigned to a different train, proceed to validate assignment conflict; if not assigned to a different train, check CCN transit status
R-GCX146-cbl-00215
Check CCN Transit Status
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check CCN Transit Status', assuming that a ccn record exists and is not assigned to a different train, when the system examines the transit status field of the ccn, the desired outcome is that the system determines if the ccn has transit status 't' and proceeds accordingly.
💻 Technical Criteria
EXCLUDING
A CCN record exists and is not assigned to a different train
When
The system examines the transit status field of the CCN
Then
The system determines if the CCN has transit status 'T' and proceeds accordingly
R-GCX146-cbl-00216
CCN in Transit Status 'T'?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN in Transit Status 'T'?' is invoked, and assuming that a ccn record has been checked for transit status, when the ccn has transit status 't', the desired outcome is that proceed to validate assignment conflict; otherwise set ccn assignment status.
💻 Technical Criteria
Given
A CCN record has been checked for transit status
When
The CCN has transit status 'T'
Then
Proceed to validate assignment conflict; otherwise set CCN assignment status
R-GCX146-cbl-00217
Validate Assignment Conflict
Policy Rules
📊 Business Logic Narrative
When the process 'Validate Assignment Conflict' is invoked, and assuming that a ccn is either assigned to a different train or has transit status 't', when the system evaluates the combination of train assignment and transit status, the desired outcome is that determine if a business rule violation exists that prevents the assignment.
💻 Technical Criteria
Given
A CCN is either assigned to a different train or has transit status 'T'
When
The system evaluates the combination of train assignment and transit status
Then
Determine if a business rule violation exists that prevents the assignment
R-GCX146-cbl-00218
Assignment Conflict Exists?
Decision Rules
📊 Business Logic Narrative
When the process 'Assignment Conflict Exists?' is invoked, and assuming that assignment conflict validation has been performed, when the system evaluates whether a legitimate conflict exists, the desired outcome is that if conflict exists, generate assignment conflict error; otherwise set ccn assignment status and allow assignment.
💻 Technical Criteria
Given
Assignment conflict validation has been performed
When
The system evaluates whether a legitimate conflict exists
Then
If conflict exists, generate assignment conflict error; otherwise set CCN assignment status and allow assignment
R-GCX146-cbl-00219
Generate Assignment Conflict Error
Action Rules
📊 Business Logic Narrative
When the process 'Generate Assignment Conflict Error' is invoked, and assuming that a legitimate assignment conflict has been identified, when the ccn cannot be assigned to the current train due to existing assignments, the desired outcome is that generate error 13 indicating the car is already on another train and terminate the validation process.
💻 Technical Criteria
Given
A legitimate assignment conflict has been identified
When
The CCN cannot be assigned to the current train due to existing assignments
Then
Generate error 13 indicating the car is already on another train and terminate the validation process
R-GCX146-cbl-00220
Set CCN Assignment Status
Action Rules
📊 Business Logic Narrative
When the process 'Set CCN Assignment Status' is invoked, and assuming that no assignment conflicts have been detected for the ccn, when the ccn is eligible for assignment to the current train, the desired outcome is that update the ccn record with the current train assignment information.
💻 Technical Criteria
Given
No assignment conflicts have been detected for the CCN
When
The CCN is eligible for assignment to the current train
Then
Update the CCN record with the current train assignment information
R-GCX146-cbl-00221
Allow CCN Assignment to Current Train
Process Rules
📊 Business Logic Narrative
When the process 'Allow CCN Assignment to Current Train' is invoked, and assuming that ccn assignment status has been successfully updated, when all validation checks have passed without conflicts, the desired outcome is that allow the ccn to be assigned to the current train and proceed with normal processing.
💻 Technical Criteria
Given
CCN assignment status has been successfully updated
When
All validation checks have passed without conflicts
Then
Allow the CCN to be assigned to the current train and proceed with normal processing
R-GCX146-cbl-00231
Validate Container CCN
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Container CCN' is invoked, and assuming that a container is being processed, when the system checks for ccn validity, the desired outcome is that the container ccn is validated against customs database records.
💻 Technical Criteria
Given
A container is being processed
When
The system checks for CCN validity
Then
The container CCN is validated against customs database records
R-GCX146-cbl-00232
CCN Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Valid?' is invoked, and assuming that container ccn validation has been performed, when the system evaluates the validation results, the desired outcome is that processing continues with waybill data if ccn is valid, otherwise inquiry database lookup is performed.
💻 Technical Criteria
Given
Container CCN validation has been performed
When
The system evaluates the validation results
Then
Processing continues with waybill data if CCN is valid, otherwise inquiry database lookup is performed
R-GCX146-cbl-00233
Process Container Waybill Data
Process Rules
📊 Business Logic Narrative
When the process 'Process Container Waybill Data' is invoked, and assuming that a container has a valid ccn, when the system processes container details, the desired outcome is that waybill data is retrieved and processed for the container.
💻 Technical Criteria
Given
A container has a valid CCN
When
The system processes container details
Then
Waybill data is retrieved and processed for the container
R-GCX146-cbl-00234
Set Container Load/Empty Status
Decision Rules
📊 Business Logic Narrative
When the process 'Set Container Load/Empty Status' is invoked, and assuming that container waybill data has been processed, when the system evaluates container contents, the desired outcome is that container status is set as either loaded or empty based on waybill information.
💻 Technical Criteria
Given
Container waybill data has been processed
When
The system evaluates container contents
Then
Container status is set as either loaded or empty based on waybill information
R-GCX146-cbl-00240
Container Inquiry Database Lookup
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Container Inquiry Database Lookup', assuming that a container ccn is not valid in the primary system, when the system needs alternative container data, the desired outcome is that container inquiry database is accessed for additional information.
💻 Technical Criteria
EXCLUDING
A container CCN is not valid in the primary system
When
The system needs alternative container data
Then
Container inquiry database is accessed for additional information
R-GCX146-cbl-01226
Process Container Waybill Data
Process Rules
📊 Business Logic Narrative
When the process 'Process Container Waybill Data' is invoked, and assuming that container information has been validated successfully, when the system processes the container's waybill data, the desired outcome is that the system retrieves and processes all relevant waybill information for the container.
💻 Technical Criteria
Given
Container information has been validated successfully
When
The system processes the container's waybill data
Then
The system retrieves and processes all relevant waybill information for the container
R-GCX146-cbl-01591
Perform Container Waybill Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Perform Container Waybill Lookup' is invoked, and assuming that a container id has been validated as having correct format, when the system performs waybill lookup for the container, the desired outcome is that waybill information is retrieved from the waybill database for the container.
💻 Technical Criteria
Given
A container ID has been validated as having correct format
When
The system performs waybill lookup for the container
Then
Waybill information is retrieved from the waybill database for the container
R-GCX146-cbl-01592
Container Waybill Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Container Waybill Found?' is invoked, and assuming that waybill lookup has been performed for a container, when the system checks for waybill existence, the desired outcome is that if waybill is found, container details are extracted; if not found, system attempts inquiry database lookup.
💻 Technical Criteria
Given
Waybill lookup has been performed for a container
When
The system checks for waybill existence
Then
If waybill is found, container details are extracted; if not found, system attempts inquiry database lookup
R-GCX146-cbl-01593
Access Container Inquiry Database
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Access Container Inquiry Database', assuming that container waybill was not found in primary lookup, when the system accesses the container inquiry database, the desired outcome is that alternative container information is retrieved from the inquiry database.
💻 Technical Criteria
EXCLUDING
Container waybill was not found in primary lookup
When
The system accesses the container inquiry database
Then
Alternative container information is retrieved from the inquiry database
R-GCX146-cbl-01595
Extract Container Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container Equipment Details' is invoked, and assuming that container information is available from either waybill or inquiry database, when the system extracts container equipment details, the desired outcome is that complete container equipment information including specifications and characteristics is retrieved.
💻 Technical Criteria
Given
Container information is available from either waybill or inquiry database
When
The system extracts container equipment details
Then
Complete container equipment information including specifications and characteristics is retrieved
R-GCX146-cbl-01729
Access Container Record
Action Rules
📊 Business Logic Narrative
When the process 'Access Container Record' is invoked, and assuming that a waybill inquiry request is being processed, when the system needs to access container records, the desired outcome is that the system retrieves container records from the fw-iq inquiry database.
💻 Technical Criteria
Given
A waybill inquiry request is being processed
When
The system needs to access container records
Then
The system retrieves container records from the FW-IQ inquiry database
R-GCX146-cbl-01740
Access FW-IQ Inquiry Database
Action Rules
📊 Business Logic Narrative
When the process 'Access FW-IQ Inquiry Database' is invoked, and assuming that a container waybill lookup process is initiated, when the system needs to access container information, the desired outcome is that the fw-iq inquiry database is accessed to retrieve container records.
💻 Technical Criteria
Given
A container waybill lookup process is initiated
When
The system needs to access container information
Then
The FW-IQ inquiry database is accessed to retrieve container records
R-GCX146-cbl-01743
Retrieve Container Waybill Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Container Waybill Data' is invoked, and assuming that a container id has been extracted from the cross-reference records, when the system needs waybill information for the container, the desired outcome is that the associated waybill data is retrieved from the inquiry database.
💻 Technical Criteria
Given
A container ID has been extracted from the cross-reference records
When
The system needs waybill information for the container
Then
The associated waybill data is retrieved from the inquiry database
R-GCX146-cbl-01744
Waybill Data Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Data Valid?' is invoked, and assuming that waybill data has been retrieved for a container, when the system evaluates the waybill information, the desired outcome is that the system determines if the waybill data is valid and complete for further processing.
💻 Technical Criteria
Given
Waybill data has been retrieved for a container
When
The system evaluates the waybill information
Then
The system determines if the waybill data is valid and complete for further processing
R-GCX146-cbl-01745
Set Container Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Container Information' is invoked, and assuming that valid waybill data has been confirmed for a container, when the system processes the validated information, the desired outcome is that the container information is set and assigned to appropriate processing variables.
💻 Technical Criteria
Given
Valid waybill data has been confirmed for a container
When
The system processes the validated information
Then
The container information is set and assigned to appropriate processing variables
R-GCX146-cbl-01746
Mark Waybill Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Mark Waybill Found Flag' is invoked, and assuming that container information has been successfully set with valid waybill data, when the system completes the container processing, the desired outcome is that the waybill found flag is marked to indicate successful waybill retrieval.
💻 Technical Criteria
Given
Container information has been successfully set with valid waybill data
When
The system completes the container processing
Then
The waybill found flag is marked to indicate successful waybill retrieval
R-GCX146-cbl-01747
More Containers?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers?' is invoked, and assuming that a container has been processed in the waybill lookup, when the system checks for additional containers to process, the desired outcome is that the system determines if more containers exist and continues processing or completes the operation.
💻 Technical Criteria
Given
A container has been processed in the waybill lookup
When
The system checks for additional containers to process
Then
The system determines if more containers exist and continues processing or completes the operation
R-GCX146-cbl-01748
Set Waybill Not Found Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Waybill Not Found Flag', assuming that a container record was not found or waybill data was invalid, when the system cannot retrieve valid waybill information, the desired outcome is that the waybill not found flag is set to indicate unsuccessful waybill retrieval.
💻 Technical Criteria
EXCLUDING
A container record was not found OR waybill data was invalid
When
The system cannot retrieve valid waybill information
Then
The waybill not found flag is set to indicate unsuccessful waybill retrieval
R-GCX146-cbl-00244
Check Load/Empty Status
Definitional Rules
📊 Business Logic Narrative
When the process 'Check Load/Empty Status' is invoked, and assuming that equipment is being processed for customs validation, when the equipment load/empty indicator is 'e' (empty), the desired outcome is that the equipment is classified as empty and flagged to skip ccn validation requirements.
💻 Technical Criteria
Given
Equipment is being processed for customs validation
When
The equipment load/empty indicator is 'E' (Empty)
Then
The equipment is classified as empty and flagged to skip CCN validation requirements
R-GCX146-cbl-00245
Check Equipment Type Code
Definitional Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check Equipment Type Code', assuming that equipment is not classified as empty and requires type validation, when the equipment type code indicates idler equipment (specific type codes for non-revenue equipment), the desired outcome is that the equipment is classified as idler equipment and marked for exemption from ccn validation.
💻 Technical Criteria
EXCLUDING
Equipment is not classified as empty and requires type validation
When
The equipment type code indicates idler equipment (specific type codes for non-revenue equipment)
Then
The equipment is classified as idler equipment and marked for exemption from CCN validation
R-GCX146-cbl-00246
Check Exemption Rules
Policy Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check Exemption Rules', assuming that equipment is not empty and not idler equipment, when the equipment meets specific exemption criteria (certain car types, special handling codes, or regulatory exemptions), the desired outcome is that the equipment is marked as exempted from ccn validation requirements.
💻 Technical Criteria
EXCLUDING
Equipment is not empty and not idler equipment
When
The equipment meets specific exemption criteria (certain car types, special handling codes, or regulatory exemptions)
Then
The equipment is marked as exempted from CCN validation requirements
R-GCX146-cbl-00247
Set Empty Equipment Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Empty Equipment Flag' is invoked, and assuming that equipment has been determined to be empty based on load/empty indicator, when the empty classification is confirmed, the desired outcome is that the empty equipment flag is set to indicate this equipment should skip ccn validation.
💻 Technical Criteria
Given
Equipment has been determined to be empty based on load/empty indicator
When
The empty classification is confirmed
Then
The empty equipment flag is set to indicate this equipment should skip CCN validation
R-GCX146-cbl-00248
Set Idler Equipment Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Idler Equipment Flag' is invoked, and assuming that equipment has been determined to be idler equipment based on equipment type code, when the idler classification is confirmed, the desired outcome is that the idler equipment flag is set to indicate this equipment should skip ccn validation.
💻 Technical Criteria
Given
Equipment has been determined to be idler equipment based on equipment type code
When
The idler classification is confirmed
Then
The idler equipment flag is set to indicate this equipment should skip CCN validation
R-GCX146-cbl-00249
Set Exempted Equipment Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Exempted Equipment Flag' is invoked, and assuming that equipment has been determined to qualify for ccn exemption based on exemption rules, when the exemption qualification is confirmed, the desired outcome is that the exempted equipment flag is set to indicate this equipment should skip ccn validation.
💻 Technical Criteria
Given
Equipment has been determined to qualify for CCN exemption based on exemption rules
When
The exemption qualification is confirmed
Then
The exempted equipment flag is set to indicate this equipment should skip CCN validation
R-GCX146-cbl-00250
Skip CCN Validation
Process Rules
📊 Business Logic Narrative
When the process 'Skip CCN Validation' is invoked, and assuming that equipment has been flagged as empty, idler, or exempted from ccn requirements, when the equipment processing continues, the desired outcome is that ccn validation steps are bypassed and the equipment proceeds to manifest generation without ccn checks.
💻 Technical Criteria
Given
Equipment has been flagged as empty, idler, or exempted from CCN requirements
When
The equipment processing continues
Then
CCN validation steps are bypassed and the equipment proceeds to manifest generation without CCN checks
R-GCX146-cbl-00252
Generate Equipment Record for Manifest
Action Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Record for Manifest' is invoked, and assuming that equipment has been processed and flagged to skip ccn validation, when manifest generation is required, the desired outcome is that a manifest record is created for the equipment with appropriate status indicators showing it as empty, idler, or exempted.
💻 Technical Criteria
Given
Equipment has been processed and flagged to skip CCN validation
When
Manifest generation is required
Then
A manifest record is created for the equipment with appropriate status indicators showing it as empty, idler, or exempted
R-GCX146-cbl-00253
Set Equipment Type Message
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment Type Message' is invoked, and assuming that equipment has been classified and processed without ccn validation, when status reporting is required, the desired outcome is that the appropriate equipment type message is set (empty, idler, or exempted) for display in reports and status inquiries.
💻 Technical Criteria
Given
Equipment has been classified and processed without CCN validation
When
Status reporting is required
Then
The appropriate equipment type message is set (EMPTY, IDLER, or EXEMPTED) for display in reports and status inquiries
R-GCX146-cbl-00254
Add to Trip Sheet without CCN
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add to Trip Sheet without CCN', assuming that equipment has been processed and classified as not requiring ccn validation, when trip sheet generation is performed, the desired outcome is that the equipment is added to the trip sheet with appropriate status indicators but without ccn information.
💻 Technical Criteria
EXCLUDING
Equipment has been processed and classified as not requiring CCN validation
When
Trip sheet generation is performed
Then
The equipment is added to the trip sheet with appropriate status indicators but without CCN information
R-GCX146-cbl-00257
Increment TOTAL-RELEASE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-RELEASE Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the equipment has ccn status of 'release' or 'csa-dlv', the desired outcome is that the total-release counter is incremented by one.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The equipment has CCN status of 'RELEASE' or 'CSA-DLV'
Then
The TOTAL-RELEASE counter is incremented by one
R-GCX146-cbl-00259
Increment TOTAL-HELD-CCRA Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-CCRA Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the equipment has ccn status of 'hold' or 'agi-hold', the desired outcome is that the total-held-ccra counter is incremented by one.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The equipment has CCN status of 'HOLD' or 'AGI-HOLD'
Then
The TOTAL-HELD-CCRA counter is incremented by one
R-GCX146-cbl-00260
Increment TOTAL-PROCEED Counter
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Increment TOTAL-PROCEED Counter', assuming that an equipment record is being processed for status totals, when the equipment has ccn status of 'return' or the manifest from station differs from the manifest to station and the status is not error, reject, or deleted, the desired outcome is that the total-proceed counter is incremented by one.
💻 Technical Criteria
EXCLUDING
An equipment record is being processed for status totals
When
The equipment has CCN status of 'RETURN' or the manifest from station differs from the manifest to station and the status is not error, reject, or deleted
Then
The TOTAL-PROCEED counter is incremented by one
R-GCX146-cbl-00262
Update Equipment Status Report Line
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Update Equipment Status Report Line', assuming that an equipment record with valid ccn is being processed and it's not a loaded/empty car, when the equipment status totals are being compiled for a verify operation, the desired outcome is that a detailed status report line is generated including manifest station names and transit status if in-transit status is 't'.
💻 Technical Criteria
EXCLUDING
An equipment record with valid CCN is being processed and it's not a loaded/empty car
When
The equipment status totals are being compiled for a VERIFY operation
Then
A detailed status report line is generated including manifest station names and transit status if in-transit status is 'T'
R-GCX146-cbl-01232
Check CCN Current Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check CCN Current Status' is invoked, and assuming that equipment is being processed for status classification, when the system checks for ccn existence for the equipment, the desired outcome is that if ccn is found, retrieve and use the current ccn status for further classification, otherwise proceed to alternative classification logic.
💻 Technical Criteria
Given
Equipment is being processed for status classification
When
The system checks for CCN existence for the equipment
Then
If CCN is found, retrieve and use the current CCN status for further classification, otherwise proceed to alternative classification logic
R-GCX146-cbl-01233
Status = RELEASE?
Decision Rules
📊 Business Logic Narrative
When the process 'Status = RELEASE?' is invoked, and assuming that equipment has a ccn with current status available, when the ccn current status equals 'release' or 'csa-dlv', the desired outcome is that proceed to evaluate transit status for further sub-classification of release status equipment.
💻 Technical Criteria
Given
Equipment has a CCN with current status available
When
The CCN current status equals 'RELEASE' or 'CSA-DLV'
Then
Proceed to evaluate transit status for further sub-classification of RELEASE status equipment
R-GCX146-cbl-01234
Classify as EXPORT Status
Decision Rules
📊 Business Logic Narrative
When the process 'Classify as EXPORT Status' is invoked, and assuming that equipment has ccn status of 'release' or 'csa-dlv', when the transit status is 'e' (export) or 'z', the desired outcome is that classify the equipment status as 'export' for reporting purposes.
💻 Technical Criteria
Given
Equipment has CCN status of 'RELEASE' or 'CSA-DLV'
When
The transit status is 'E' (Export) or 'Z'
Then
Classify the equipment status as 'EXPORT' for reporting purposes
R-GCX146-cbl-01235
Classify as S.A.R. Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Classify as S.A.R. Status', assuming that equipment has ccn status of 'release' or 'csa-dlv' and transit status is not 'e' or 'z', when the release-by field contains 's.a.r.', the desired outcome is that classify the equipment status as 's.a.r.' for reporting purposes.
💻 Technical Criteria
EXCLUDING
Equipment has CCN status of 'RELEASE' or 'CSA-DLV' and transit status is not 'E' or 'Z'
When
The release-by field contains 'S.A.R.'
Then
Classify the equipment status as 'S.A.R.' for reporting purposes
R-GCX146-cbl-01236
Classify as RELEASE Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Classify as RELEASE Status', assuming that equipment has ccn status of 'release' or 'csa-dlv', when transit status is not 'e' or 'z' and release-by field does not contain 's.a.r.', the desired outcome is that classify the equipment status as 'release' for reporting purposes.
💻 Technical Criteria
EXCLUDING
Equipment has CCN status of 'RELEASE' or 'CSA-DLV'
When
Transit status is not 'E' or 'Z' and release-by field does not contain 'S.A.R.'
Then
Classify the equipment status as 'RELEASE' for reporting purposes
R-GCX146-cbl-01237
Classify as TRANSIT Status
Decision Rules
📊 Business Logic Narrative
When the process 'Classify as TRANSIT Status' is invoked, and assuming that equipment has ccn with status other than 'release' or 'csa-dlv', when the in-transit status equals 't', the desired outcome is that classify the equipment status as 'transit' for reporting purposes.
💻 Technical Criteria
Given
Equipment has CCN with status other than 'RELEASE' or 'CSA-DLV'
When
The in-transit status equals 'T'
Then
Classify the equipment status as 'TRANSIT' for reporting purposes
R-GCX146-cbl-01238
Classify as RETURN Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Classify as RETURN Status', assuming that equipment has ccn with status other than 'release' or 'csa-dlv' and in-transit status is not 't', when the in-transit status equals 'r', the desired outcome is that classify the equipment status as 'return' for reporting purposes.
💻 Technical Criteria
EXCLUDING
Equipment has CCN with status other than 'RELEASE' or 'CSA-DLV' and in-transit status is not 'T'
When
The in-transit status equals 'R'
Then
Classify the equipment status as 'RETURN' for reporting purposes
R-GCX146-cbl-01239
Use Current CCN Status
Decision Rules
📊 Business Logic Narrative
When the process 'Use Current CCN Status' is invoked, and assuming that equipment has ccn with status other than 'release' or 'csa-dlv', when in-transit status is neither 't' nor 'r', the desired outcome is that use the current ccn status as-is for equipment classification.
💻 Technical Criteria
Given
Equipment has CCN with status other than 'RELEASE' or 'CSA-DLV'
When
In-transit status is neither 'T' nor 'R'
Then
Use the current CCN status as-is for equipment classification
R-GCX146-cbl-01240
Classify as PROCEED Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Classify as PROCEED Status', assuming that equipment does not have a ccn record, when equipment is marked as empty (le = 'e') or is exempted from ccn requirements, the desired outcome is that classify the equipment status as 'proceed' and increment total-proceed counter.
💻 Technical Criteria
EXCLUDING
Equipment does not have a CCN record
When
Equipment is marked as empty (LE = 'E') or is exempted from CCN requirements
Then
Classify the equipment status as 'PROCEED' and increment TOTAL-PROCEED counter
R-GCX146-cbl-01241
Classify as HELD-CCRA Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Classify as HELD-CCRA Status', assuming that equipment does not have ccn and is not empty or exempted, when equipment has status 'hold' or 'agi-hold', the desired outcome is that classify the equipment status as 'held-ccra' and increment total-held-ccra counter.
💻 Technical Criteria
EXCLUDING
Equipment does not have CCN and is not empty or exempted
When
Equipment has status 'HOLD' or 'AGI-HOLD'
Then
Classify the equipment status as 'HELD-CCRA' and increment TOTAL-HELD-CCRA counter
R-GCX146-cbl-01242
Classify as HELD-DOCS Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Classify as HELD-DOCS Status', assuming that equipment does not have ccn, is not empty/exempted, and is not held by ccra, when manifest from station equals manifest to station and broker entry is empty, the desired outcome is that classify the equipment status as 'held-docs' and increment total-held-docs counter.
💻 Technical Criteria
EXCLUDING
Equipment does not have CCN, is not empty/exempted, and is not held by CCRA
When
Manifest from station equals manifest to station and broker entry is empty
Then
Classify the equipment status as 'HELD-DOCS' and increment TOTAL-HELD-DOCS counter
R-GCX146-cbl-01464
Set Status to 'EXPORT'
Decision Rules
📊 Business Logic Narrative
When the process 'Set Status to 'EXPORT'' is invoked, and assuming that equipment has ccn status of 'release' and transit status is either 'e' (export) or 'z' (export zone), when the system processes equipment status for trip sheet generation, the desired outcome is that the equipment status should be classified as 'export' on the trip sheet.
💻 Technical Criteria
Given
Equipment has CCN status of 'RELEASE' and transit status is either 'E' (Export) or 'Z' (Export Zone)
When
The system processes equipment status for trip sheet generation
Then
The equipment status should be classified as 'EXPORT' on the trip sheet
R-GCX146-cbl-01465
Set Status to 'S.A.R.'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to 'S.A.R.'', assuming that equipment has ccn status of 'release' and transit status is not 'e' or 'z' and the release is designated as s.a.r. release, when the system processes equipment status for trip sheet generation, the desired outcome is that the equipment status should be classified as 's.a.r.' on the trip sheet.
💻 Technical Criteria
EXCLUDING
Equipment has CCN status of 'RELEASE' and transit status is not 'E' or 'Z' and the release is designated as S.A.R. release
When
The system processes equipment status for trip sheet generation
Then
The equipment status should be classified as 'S.A.R.' on the trip sheet
R-GCX146-cbl-01466
Set Status to 'RELEASE'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to 'RELEASE'', assuming that equipment has ccn status of 'release' and transit status is not 'e' or 'z' and does not have s.a.r. release designation, when the system processes equipment status for trip sheet generation, the desired outcome is that the equipment status should be classified as 'release' on the trip sheet.
💻 Technical Criteria
EXCLUDING
Equipment has CCN status of 'RELEASE' and transit status is not 'E' or 'Z' and does not have S.A.R. release designation
When
The system processes equipment status for trip sheet generation
Then
The equipment status should be classified as 'RELEASE' on the trip sheet
R-GCX146-cbl-01467
Set Status to 'TRANSIT'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to 'TRANSIT'', assuming that equipment has transit status of 't' (transit) and ccn status is not 'release', when the system processes equipment status for trip sheet generation, the desired outcome is that the equipment status should be classified as 'transit' on the trip sheet.
💻 Technical Criteria
EXCLUDING
Equipment has transit status of 'T' (Transit) and CCN status is not 'RELEASE'
When
The system processes equipment status for trip sheet generation
Then
The equipment status should be classified as 'TRANSIT' on the trip sheet
R-GCX146-cbl-01468
Set Status to 'RETURN'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to 'RETURN'', assuming that equipment has transit status of 'r' (return) and ccn status is not 'release' and transit status is not 't', when the system processes equipment status for trip sheet generation, the desired outcome is that the equipment status should be classified as 'return' on the trip sheet.
💻 Technical Criteria
EXCLUDING
Equipment has transit status of 'R' (Return) and CCN status is not 'RELEASE' and transit status is not 'T'
When
The system processes equipment status for trip sheet generation
Then
The equipment status should be classified as 'RETURN' on the trip sheet
R-GCX146-cbl-01469
Maintain Current Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Maintain Current Status', assuming that equipment ccn status is not 'release' and transit status is not 't' or 'r', when the system processes equipment status for trip sheet generation, the desired outcome is that the equipment status should remain as the current ccn status on the trip sheet.
💻 Technical Criteria
EXCLUDING
Equipment CCN status is not 'RELEASE' and transit status is not 'T' or 'R'
When
The system processes equipment status for trip sheet generation
Then
The equipment status should remain as the current CCN status on the trip sheet
R-GCX146-cbl-01600
Access CCN Database Using Equipment ID
Action Rules
📊 Business Logic Narrative
When the process 'Access CCN Database Using Equipment ID' is invoked, and assuming that an equipment id is provided for ccn status lookup, when the system accesses the gcccrt ccn database using the equipment id, the desired outcome is that the system retrieves the ccn record if it exists in the database.
💻 Technical Criteria
Given
An equipment ID is provided for CCN status lookup
When
The system accesses the GCCCRT CCN database using the equipment ID
Then
The system retrieves the CCN record if it exists in the database
R-GCX146-cbl-01601
CCN Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Record Found?' is invoked, and assuming that a database lookup has been performed for an equipment id, when the system checks if a ccn record was found, the desired outcome is that the system determines whether to proceed with status retrieval or handle missing ccn scenario.
💻 Technical Criteria
Given
A database lookup has been performed for an equipment ID
When
The system checks if a CCN record was found
Then
The system determines whether to proceed with status retrieval or handle missing CCN scenario
R-GCX146-cbl-01602
Retrieve Current CCN Status
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current CCN Status' is invoked, and assuming that a valid ccn record exists for the equipment, when the system accesses the ccn record, the desired outcome is that the current ccn status is retrieved from the record.
💻 Technical Criteria
Given
A valid CCN record exists for the equipment
When
The system accesses the CCN record
Then
The current CCN status is retrieved from the record
R-GCX146-cbl-01603
Retrieve Transit Status Code
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Transit Status Code' is invoked, and assuming that a valid ccn record exists with current status retrieved, when the system accesses the transit status field in the ccn record, the desired outcome is that the transit status code is retrieved for further processing.
💻 Technical Criteria
Given
A valid CCN record exists with current status retrieved
When
The system accesses the transit status field in the CCN record
Then
The transit status code is retrieved for further processing
R-GCX146-cbl-01604
Status = RELEASE?
Decision Rules
📊 Business Logic Narrative
When the process 'Status = RELEASE?' is invoked, and assuming that a ccn record with current status and transit status code, when the system evaluates if the current status equals release, the desired outcome is that the system branches to release-specific status determination logic or continues to other status checks.
💻 Technical Criteria
Given
A CCN record with current status and transit status code
When
The system evaluates if the current status equals RELEASE
Then
The system branches to release-specific status determination logic or continues to other status checks
R-GCX146-cbl-01614
Keep Current Status
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Keep Current Status', assuming that equipment does not qualify for release, transit, or return status mapping, when the system processes the status assignment, the desired outcome is that the equipment retains its original ccn status.
💻 Technical Criteria
EXCLUDING
Equipment does not qualify for RELEASE, TRANSIT, or RETURN status mapping
When
The system processes the status assignment
Then
The equipment retains its original CCN status
R-GCX146-cbl-01616
Return Current CCN Status
Action Rules
📊 Business Logic Narrative
When the process 'Return Current CCN Status' is invoked, and assuming that the equipment status has been determined and record updated, when the system completes the ccn status retrieval process, the desired outcome is that the final ccn status is returned to the calling process.
💻 Technical Criteria
Given
The equipment status has been determined and record updated
When
The system completes the CCN status retrieval process
Then
The final CCN status is returned to the calling process
R-GCX146-cbl-01617
CCN Not Found - Set Empty Status
Action Rules
📊 Business Logic Narrative
When the process 'CCN Not Found - Set Empty Status' is invoked, and assuming that no ccn record exists for the equipment id, when the system processes the missing ccn scenario, the desired outcome is that the system sets an empty or default status and returns it.
💻 Technical Criteria
Given
No CCN record exists for the equipment ID
When
The system processes the missing CCN scenario
Then
The system sets an empty or default status and returns it
R-GCX146-cbl-01245
Increment TOTAL-RELEASE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-RELEASE Counter' is invoked, and assuming that an equipment item is being processed for status totals, when the ccn status is 'release' or 'csa-dlv', the desired outcome is that the total-release counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment item is being processed for status totals
When
The CCN status is 'RELEASE' or 'CSA-DLV'
Then
The TOTAL-RELEASE counter should be incremented by 1
R-GCX146-cbl-01247
Increment TOTAL-HELD-CCRA Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-CCRA Counter' is invoked, and assuming that an equipment item is being processed for status totals, when the ccn status is 'hold' or 'agi-hold', the desired outcome is that the total-held-ccra counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment item is being processed for status totals
When
The CCN status is 'HOLD' or 'AGI-HOLD'
Then
The TOTAL-HELD-CCRA counter should be incremented by 1
R-GCX146-cbl-01248
Increment TOTAL-PROCEED Counter
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Increment TOTAL-PROCEED Counter', assuming that an equipment item is being processed for status totals, when the ccn status is 'return' or the manifest from station is different from the manifest to station and the status is not error, reject, or deleted, the desired outcome is that the total-proceed counter should be incremented by 1.
💻 Technical Criteria
EXCLUDING
An equipment item is being processed for status totals
When
The CCN status is 'RETURN' or the manifest from station is different from the manifest to station and the status is not error, reject, or deleted
Then
The TOTAL-PROCEED counter should be incremented by 1
R-GCX146-cbl-00270
Set CCN Key for EDI Manifest
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Key for EDI Manifest' is invoked, and assuming that equipment has load/empty status assigned for edi processing, when the system prepares the edi manifest record, the desired outcome is that the ccn key is set in the edi equipment record for customs identification.
💻 Technical Criteria
Given
Equipment has load/empty status assigned for EDI processing
When
The system prepares the EDI manifest record
Then
The CCN key is set in the EDI equipment record for customs identification
R-GCX146-cbl-00271
Build EDI Equipment Record Structure
Process Rules
📊 Business Logic Narrative
When the process 'Build EDI Equipment Record Structure' is invoked, and assuming that equipment type, status, and ccn key have been determined, when the system builds the edi equipment record, the desired outcome is that a complete edi record structure is created with all required data elements populated.
💻 Technical Criteria
Given
Equipment type, status, and CCN key have been determined
When
The system builds the EDI equipment record
Then
A complete EDI record structure is created with all required data elements populated
R-GCX146-cbl-00321
Assign Status Information
Decision Rules
📊 Business Logic Narrative
When the process 'Assign Status Information' is invoked, and assuming that equipment car type description has been added, when status assignment is required, the desired outcome is that ccn status is evaluated, transit status is determined, and appropriate status is assigned (export for release with e/z transit, s.a.r. for release with s.a.r., transit for t status, return for r status, or current status otherwise).
💻 Technical Criteria
Given
Equipment car type description has been added
When
Status assignment is required
Then
CCN status is evaluated, transit status is determined, and appropriate status is assigned (EXPORT for RELEASE with E/Z transit, S.A.R. for RELEASE with S.A.R., TRANSIT for T status, RETURN for R status, or current status otherwise)
R-GCX146-cbl-01619
Check Container Load Status
Process Rules
📊 Business Logic Narrative
When the process 'Check Container Load Status' is invoked, and assuming that equipment is identified as a flat car that may contain containers, when checking container load status, the desired outcome is that system processes containers only if waybill is found for the equipment.
💻 Technical Criteria
Given
Equipment is identified as a flat car that may contain containers
When
Checking container load status
Then
System processes containers only if waybill is found for the equipment
R-GCX146-cbl-01621
Check Container Load Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Container Load Status' is invoked, and assuming that equipment is marked as loaded and operation type is add, when checking container load status, the desired outcome is that system generates error 21 if no waybill is found for loaded equipment.
💻 Technical Criteria
Given
Equipment is marked as loaded and operation type is ADD
When
Checking container load status
Then
System generates Error 21 if no waybill is found for loaded equipment
R-GCX146-cbl-01622
Check Container Load Status
Process Rules
📊 Business Logic Narrative
When the process 'Check Container Load Status' is invoked, and assuming that equipment load/empty indicator shows 'e' (empty) and operation type is add, when checking container load status, the desired outcome is that system allows processing to continue without requiring waybill documentation.
💻 Technical Criteria
Given
Equipment load/empty indicator shows 'E' (empty) and operation type is ADD
When
Checking container load status
Then
System allows processing to continue without requiring waybill documentation
R-GCX146-cbl-01623
Extract Equipment Type from Waybill Data
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Type from Waybill Data' is invoked, and assuming that equipment waybill data is available with equipment type information, when system extracts equipment type from waybill data, the desired outcome is that equipment type is classified to determine if it is a trailer requiring load status processing.
💻 Technical Criteria
Given
Equipment waybill data is available with equipment type information
When
System extracts equipment type from waybill data
Then
Equipment type is classified to determine if it is a trailer requiring load status processing
R-GCX146-cbl-01624
Is Equipment a Trailer?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Equipment a Trailer?' is invoked, and assuming that equipment type has been extracted from waybill data, when system checks if equipment type indicates a trailer, the desired outcome is that equipment is identified as trailer or non-trailer for appropriate processing path.
💻 Technical Criteria
Given
Equipment type has been extracted from waybill data
When
System checks if equipment type indicates a trailer
Then
Equipment is identified as trailer or non-trailer for appropriate processing path
R-GCX146-cbl-01625
Retrieve Waybill Load/Empty Indicator
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Waybill Load/Empty Indicator' is invoked, and assuming that equipment is identified as a trailer type, when system accesses waybill data for load/empty indicator, the desired outcome is that load/empty status indicator is retrieved from waybill record.
💻 Technical Criteria
Given
Equipment is identified as a trailer type
When
System accesses waybill data for load/empty indicator
Then
Load/empty status indicator is retrieved from waybill record
R-GCX146-cbl-01626
Compare Input Load Status vs Waybill Status
Validation Rules
📊 Business Logic Narrative
When the process 'Compare Input Load Status vs Waybill Status' is invoked, and assuming that input load status is provided and waybill load status is retrieved, when system compares input load status with waybill load status, the desired outcome is that status comparison result is determined for validation processing.
💻 Technical Criteria
Given
Input load status is provided and waybill load status is retrieved
When
System compares input load status with waybill load status
Then
Status comparison result is determined for validation processing
R-GCX146-cbl-01627
Status Match?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Match?' is invoked, and assuming that input load status and waybill load status have been compared, when system evaluates if the statuses match, the desired outcome is that status match result determines whether to proceed with cargo analysis or set validation error.
💻 Technical Criteria
Given
Input load status and waybill load status have been compared
When
System evaluates if the statuses match
Then
Status match result determines whether to proceed with cargo analysis or set validation error
R-GCX146-cbl-01628
Analyze Cargo Origin/Destination
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Cargo Origin/Destination' is invoked, and assuming that input load status matches waybill load status, when system analyzes cargo origin and destination data, the desired outcome is that origin and destination information is evaluated for load status determination.
💻 Technical Criteria
Given
Input load status matches waybill load status
When
System analyzes cargo origin and destination data
Then
Origin and destination information is evaluated for load status determination
R-GCX146-cbl-01635
Set Status Validation Error
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status Validation Error', assuming that load status is invalid or input status does not match waybill status, when system encounters validation failure, the desired outcome is that status validation error is set for the equipment.
💻 Technical Criteria
EXCLUDING
Load status is invalid or input status does not match waybill status
When
System encounters validation failure
Then
Status validation error is set for the equipment
R-GCX146-cbl-01755
Retrieve Waybill Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Waybill Data' is invoked, and assuming that a cargo equipment piece requires origin/destination analysis, when the system attempts to retrieve waybill data for the equipment, the desired outcome is that the system should locate and extract the associated waybill information from the equipment records.
💻 Technical Criteria
Given
A cargo equipment piece requires origin/destination analysis
When
The system attempts to retrieve waybill data for the equipment
Then
The system should locate and extract the associated waybill information from the equipment records
R-GCX146-cbl-01756
Waybill Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Available?' is invoked, and assuming that waybill retrieval has been attempted for a cargo equipment piece, when the system checks if waybill data is available, the desired outcome is that the system should determine if valid waybill information exists and route processing accordingly.
💻 Technical Criteria
Given
Waybill retrieval has been attempted for a cargo equipment piece
When
The system checks if waybill data is available
Then
The system should determine if valid waybill information exists and route processing accordingly
R-GCX146-cbl-01757
Extract Origin Station Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract Origin Station Code' is invoked, and assuming that valid waybill data is available for a cargo equipment piece, when the system processes the waybill to extract origin information, the desired outcome is that the system should identify and extract the origin station code from the waybill data.
💻 Technical Criteria
Given
Valid waybill data is available for a cargo equipment piece
When
The system processes the waybill to extract origin information
Then
The system should identify and extract the origin station code from the waybill data
R-GCX146-cbl-01758
Extract Destination Station Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract Destination Station Code' is invoked, and assuming that valid waybill data is available and origin station code has been extracted, when the system processes the waybill to extract destination information, the desired outcome is that the system should identify and extract the destination station code from the waybill data.
💻 Technical Criteria
Given
Valid waybill data is available and origin station code has been extracted
When
The system processes the waybill to extract destination information
Then
The system should identify and extract the destination station code from the waybill data
R-GCX146-cbl-01759
Validate Origin Code Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Origin Code Format' is invoked, and assuming that an origin station code has been extracted from waybill data, when the system validates the origin code format, the desired outcome is that the system should verify the origin code conforms to valid station code format requirements.
💻 Technical Criteria
Given
An origin station code has been extracted from waybill data
When
The system validates the origin code format
Then
The system should verify the origin code conforms to valid station code format requirements
R-GCX146-cbl-01760
Validate Destination Code Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Destination Code Format' is invoked, and assuming that a destination station code has been extracted from waybill data, when the system validates the destination code format, the desired outcome is that the system should verify the destination code conforms to valid station code format requirements.
💻 Technical Criteria
Given
A destination station code has been extracted from waybill data
When
The system validates the destination code format
Then
The system should verify the destination code conforms to valid station code format requirements
R-GCX146-cbl-01762
Determine Load/Empty Status
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Load/Empty Status' is invoked, and assuming that valid origin and destination codes exist for cargo equipment, when the system analyzes the cargo to determine load status, the desired outcome is that the system should classify the equipment as either loaded or empty based on waybill indicators and equipment characteristics.
💻 Technical Criteria
Given
Valid origin and destination codes exist for cargo equipment
When
The system analyzes the cargo to determine load status
Then
The system should classify the equipment as either loaded or empty based on waybill indicators and equipment characteristics
R-GCX146-cbl-01765
Set Default Status
Process Rules
📊 Business Logic Narrative
When the process 'Set Default Status' is invoked, and assuming that either no waybill data is available or origin/destination codes are invalid, when the system cannot complete normal cargo analysis, the desired outcome is that the system should assign default status values to allow processing to continue.
💻 Technical Criteria
Given
Either no waybill data is available or origin/destination codes are invalid
When
The system cannot complete normal cargo analysis
Then
The system should assign default status values to allow processing to continue
R-GCX146-cbl-01766
Retrieve Equipment Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Equipment Record' is invoked, and assuming that an equipment record exists in the system with waybill data available, when the system processes equipment for load status validation, the desired outcome is that the equipment record is successfully retrieved for further validation.
💻 Technical Criteria
Given
An equipment record exists in the system with waybill data available
When
The system processes equipment for load status validation
Then
The equipment record is successfully retrieved for further validation
R-GCX146-cbl-01767
Check Waybill Data Available
Validation Rules
📊 Business Logic Narrative
When the process 'Check Waybill Data Available' is invoked, and assuming that an equipment record is being processed for load status validation, when the system checks for associated waybill data, the desired outcome is that the system determines whether waybill data is available or not available for the equipment.
💻 Technical Criteria
Given
An equipment record is being processed for load status validation
When
The system checks for associated waybill data
Then
The system determines whether waybill data is available or not available for the equipment
R-GCX146-cbl-01768
Extract Load/Empty Indicator from Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Extract Load/Empty Indicator from Waybill' is invoked, and assuming that waybill data exists for the equipment, when the system processes the waybill record, the desired outcome is that the load or empty indicator is extracted from the waybill data for comparison.
💻 Technical Criteria
Given
Waybill data exists for the equipment
When
The system processes the waybill record
Then
The load or empty indicator is extracted from the waybill data for comparison
R-GCX146-cbl-01769
Compare Input Load Status vs Waybill Status
Validation Rules
📊 Business Logic Narrative
When the process 'Compare Input Load Status vs Waybill Status' is invoked, and assuming that both input load status and waybill load status are available, when the system performs load status comparison, the desired outcome is that the system determines if the input load status matches the waybill load status.
💻 Technical Criteria
Given
Both input load status and waybill load status are available
When
The system performs load status comparison
Then
The system determines if the input load status matches the waybill load status
R-GCX146-cbl-01770
Status Match?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Match?' is invoked, and assuming that input load status and waybill load status have been compared, when the system evaluates the comparison result, the desired outcome is that the system determines if the statuses match or do not match and proceeds accordingly.
💻 Technical Criteria
Given
Input load status and waybill load status have been compared
When
The system evaluates the comparison result
Then
The system determines if the statuses match or do not match and proceeds accordingly
R-GCX146-cbl-01771
Validate Load Requirements Met
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Load Requirements Met' is invoked, and assuming that either no waybill data exists or the input load status matches the waybill load status, when the system processes load requirements validation, the desired outcome is that the system validates that all load requirements are properly met.
💻 Technical Criteria
Given
Either no waybill data exists or the input load status matches the waybill load status
When
The system processes load requirements validation
Then
The system validates that all load requirements are properly met
R-GCX146-cbl-01773
Generate Load Status Mismatch Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Load Status Mismatch Error', assuming that the input load status does not match the waybill load status, when the system detects the mismatch condition, the desired outcome is that a load status mismatch error is generated to indicate the validation failure.
💻 Technical Criteria
EXCLUDING
The input load status does not match the waybill load status
When
The system detects the mismatch condition
Then
A load status mismatch error is generated to indicate the validation failure
R-GCX146-cbl-00328
Process Equipment Status Records
Process Rules
📊 Business Logic Narrative
When the process 'Process Equipment Status Records' is invoked, and assuming that equipment records exist for the train being verified, when processing equipment status records, the desired outcome is that each equipment record is processed to extract ccn status, equipment details, and manifest information.
💻 Technical Criteria
Given
Equipment records exist for the train being verified
When
Processing equipment status records
Then
Each equipment record is processed to extract CCN status, equipment details, and manifest information
R-GCX146-cbl-00340
Add Equipment Details to Report
Process Rules
📊 Business Logic Narrative
When the process 'Add Equipment Details to Report' is invoked, and assuming that equipment status lines have been formatted, when building the complete status report, the desired outcome is that formatted equipment details are added to the report output including ccn, status, and manifest information.
💻 Technical Criteria
Given
Equipment status lines have been formatted
When
Building the complete status report
Then
Formatted equipment details are added to the report output including CCN, status, and manifest information
R-GCX146-cbl-00347
Generate Waybill Lookup Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Waybill Lookup Error', assuming that equipment requires waybill validation during processing, when waybill lookup fails for loaded cars or waybill data is invalid, the desired outcome is that the system generates error 21 for loaded cars without waybills or other waybill-related error codes.
💻 Technical Criteria
EXCLUDING
Equipment requires waybill validation during processing
When
Waybill lookup fails for loaded cars or waybill data is invalid
Then
The system generates error 21 for loaded cars without waybills or other waybill-related error codes
R-GCX146-cbl-00348
Generate CCN Validation Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate CCN Validation Error', assuming that ccn validation is being performed for equipment, when ccn status is invalid, ccn is assigned to another train, or ccn validation rules are violated, the desired outcome is that the system generates error 24 for invalid status, error 13 for duplicate train assignment, or other ccn-related error codes.
💻 Technical Criteria
EXCLUDING
CCN validation is being performed for equipment
When
CCN status is invalid, CCN is assigned to another train, or CCN validation rules are violated
Then
The system generates error 24 for invalid status, error 13 for duplicate train assignment, or other CCN-related error codes
R-GCX146-cbl-00349
Generate Other Processing Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Other Processing Error', assuming that a processing error has occurred during train operations, when the error is not related to scac access, eta range, station validation, waybill lookup, or ccn validation, the desired outcome is that the system generates the appropriate general processing error code based on the specific issue encountered.
💻 Technical Criteria
EXCLUDING
A processing error has occurred during train operations
When
The error is not related to SCAC access, ETA range, station validation, waybill lookup, or CCN validation
Then
The system generates the appropriate general processing error code based on the specific issue encountered
R-GCX146-cbl-00380
Prepare Equipment and Cargo Data
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Equipment and Cargo Data' is invoked, and assuming that equipment records exist for the train, when the system processes each equipment item, the desired outcome is that equipment details, waybill information, and cargo data are extracted and formatted for customs reporting.
💻 Technical Criteria
Given
Equipment records exist for the train
When
The system processes each equipment item
Then
Equipment details, waybill information, and cargo data are extracted and formatted for customs reporting
R-GCX146-cbl-00384
Process UNIT Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process UNIT Equipment' is invoked, and assuming that equipment is classified as unit type (l, p, d, u), when the system processes the unit equipment, the desired outcome is that unit equipment is formatted with cargo details, waybill information, and customs status.
💻 Technical Criteria
Given
Equipment is classified as UNIT type (L, P, D, U)
When
The system processes the UNIT equipment
Then
UNIT equipment is formatted with cargo details, waybill information, and customs status
R-GCX146-cbl-00399
Generate Arrival Notice
Action Rules
📊 Business Logic Narrative
When the process 'Generate Arrival Notice' is invoked, and assuming that cargo has been identified as arrived at destination, when the system generates arrival notice, the desired outcome is that a gct1481e transaction is spawned with cargo details including ccn key and arrival information.
💻 Technical Criteria
Given
Cargo has been identified as arrived at destination
When
The system generates arrival notice
Then
A GCT1481E transaction is spawned with cargo details including CCN key and arrival information
R-GCX146-cbl-00404
Build Return CCN Number
Computation Rules
📊 Business Logic Narrative
When the process 'Build Return CCN Number' is invoked, and assuming that canadian goods returning from us requiring ccn creation, when the system builds the return ccn number, the desired outcome is that the ccn number is constructed using format: '6' + '105' + 'e' + equipment_id + waybill_date + sequence_number.
💻 Technical Criteria
Given
Canadian goods returning from US requiring CCN creation
When
The system builds the return CCN number
Then
The CCN number is constructed using format: '6' + '105' + 'E' + equipment_id + waybill_date + sequence_number
R-GCX146-cbl-00405
Set CCN Prefix to '6105E'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Prefix to '6105E'' is invoked, and assuming that a return ccn being created for canadian goods, when the system sets the ccn prefix, the desired outcome is that the ccn prefix is set to '6105e' to identify it as a return customs control number.
💻 Technical Criteria
Given
A return CCN being created for Canadian goods
When
The system sets the CCN prefix
Then
The CCN prefix is set to '6105E' to identify it as a return customs control number
R-GCX146-cbl-00406
Append Equipment ID to CCN
Computation Rules
📊 Business Logic Narrative
When the process 'Append Equipment ID to CCN' is invoked, and assuming that a return ccn being constructed with equipment information available, when the system appends the equipment id to the ccn, the desired outcome is that the equipment id is included in the ccn number to ensure unique identification per equipment piece.
💻 Technical Criteria
Given
A return CCN being constructed with equipment information available
When
The system appends the equipment ID to the CCN
Then
The equipment ID is included in the CCN number to ensure unique identification per equipment piece
R-GCX146-cbl-00407
Append Waybill Date to CCN
Computation Rules
📊 Business Logic Narrative
When the process 'Append Waybill Date to CCN' is invoked, and assuming that a return ccn being created with associated waybill information, when the system appends the waybill date to the ccn, the desired outcome is that the waybill date is included in the ccn number to provide temporal context and ensure uniqueness.
💻 Technical Criteria
Given
A return CCN being created with associated waybill information
When
The system appends the waybill date to the CCN
Then
The waybill date is included in the CCN number to provide temporal context and ensure uniqueness
R-GCX146-cbl-00408
Set CCN Status to 'RETURN'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to 'RETURN'' is invoked, and assuming that a ccn being created for canadian goods returning from us, when the system sets the ccn status, the desired outcome is that the ccn status is set to 'return' to indicate the cargo is returning to canada.
💻 Technical Criteria
Given
A CCN being created for Canadian goods returning from US
When
The system sets the CCN status
Then
The CCN status is set to 'RETURN' to indicate the cargo is returning to Canada
R-GCX146-cbl-00409
Set Transit Status to 'R'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'R'' is invoked, and assuming that a return ccn being created with status information, when the system sets the transit status, the desired outcome is that the transit status is set to 'r' to indicate return movement.
💻 Technical Criteria
Given
A return CCN being created with status information
When
The system sets the transit status
Then
The transit status is set to 'R' to indicate return movement
R-GCX146-cbl-00410
Populate Shipper Information from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Populate Shipper Information from Waybill' is invoked, and assuming that a return ccn being created with available waybill data containing shipper information, when the system populates shipper information, the desired outcome is that shipper name, address, and other relevant details are extracted from the waybill and stored in the ccn record.
💻 Technical Criteria
Given
A return CCN being created with available waybill data containing shipper information
When
The system populates shipper information
Then
Shipper name, address, and other relevant details are extracted from the waybill and stored in the CCN record
R-GCX146-cbl-00411
Populate Consignee Information from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Populate Consignee Information from Waybill' is invoked, and assuming that a return ccn being created with available waybill data containing consignee information, when the system populates consignee information, the desired outcome is that consignee name, address, and other relevant details are extracted from the waybill and stored in the ccn record.
💻 Technical Criteria
Given
A return CCN being created with available waybill data containing consignee information
When
The system populates consignee information
Then
Consignee name, address, and other relevant details are extracted from the waybill and stored in the CCN record
R-GCX146-cbl-00412
Insert Return CCN Record
Action Rules
📊 Business Logic Narrative
When the process 'Insert Return CCN Record' is invoked, and assuming that all return ccn information has been populated and validated, when the system inserts the return ccn record, the desired outcome is that a new ccn record is created in the customs database with all populated information and return status.
💻 Technical Criteria
Given
All return CCN information has been populated and validated
When
The system inserts the return CCN record
Then
A new CCN record is created in the customs database with all populated information and return status
R-GCX146-cbl-00413
CCN Creation Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Creation Successful?' is invoked, and assuming that a return ccn record insertion has been attempted, when the system checks the creation result, the desired outcome is that if the ccn record was successfully created, the process continues with success confirmation, otherwise error handling is initiated.
💻 Technical Criteria
Given
A return CCN record insertion has been attempted
When
The system checks the creation result
Then
If the CCN record was successfully created, the process continues with success confirmation, otherwise error handling is initiated
R-GCX146-cbl-00414
Return CCN Created Successfully
Process Rules
📊 Business Logic Narrative
When the process 'Return CCN Created Successfully' is invoked, and assuming that a return ccn record has been successfully inserted into the database, when the system processes the successful creation, the desired outcome is that the return ccn creation is marked as complete and the process proceeds to completion.
💻 Technical Criteria
Given
A return CCN record has been successfully inserted into the database
When
The system processes the successful creation
Then
The return CCN creation is marked as complete and the process proceeds to completion
R-GCX146-cbl-00415
Handle CCN Creation Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle CCN Creation Error' is invoked, and assuming that an error occurred during return ccn record creation, when the system handles the ccn creation error, the desired outcome is that appropriate error logging and recovery procedures are executed to manage the failed ccn creation.
💻 Technical Criteria
Given
An error occurred during return CCN record creation
When
The system handles the CCN creation error
Then
Appropriate error logging and recovery procedures are executed to manage the failed CCN creation
R-GCX146-cbl-01293
Set CCN Prefix to '6105E'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Prefix to '6105E'' is invoked, and assuming that a return cargo ccn needs to be created for canadian customs, when the system constructs the ccn number, the desired outcome is that the ccn must start with the prefix '6105e' followed by the equipment identifier.
💻 Technical Criteria
Given
A return cargo CCN needs to be created for Canadian customs
When
The system constructs the CCN number
Then
The CCN must start with the prefix '6105E' followed by the equipment identifier
R-GCX146-cbl-01294
Extract Equipment ID from Current Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from Current Record' is invoked, and assuming that a current equipment record is being processed for return ccn creation, when the system needs to build the ccn identifier, the desired outcome is that the equipment id must be extracted from the current record and used in ccn construction.
💻 Technical Criteria
Given
A current equipment record is being processed for return CCN creation
When
The system needs to build the CCN identifier
Then
The equipment ID must be extracted from the current record and used in CCN construction
R-GCX146-cbl-01295
Extract Waybill Date from Waybill Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Date from Waybill Record' is invoked, and assuming that a waybill record exists for the equipment being processed, when the system constructs a return ccn, the desired outcome is that the waybill date must be extracted from the waybill record and appended to the ccn identifier.
💻 Technical Criteria
Given
A waybill record exists for the equipment being processed
When
The system constructs a return CCN
Then
The waybill date must be extracted from the waybill record and appended to the CCN identifier
R-GCX146-cbl-01296
Validate CCN Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CCN Format' is invoked, and assuming that a ccn has been constructed with prefix, equipment id, and waybill date, when the system validates the ccn format, the desired outcome is that the ccn format must be valid according to customs requirements or the construction process must be rejected.
💻 Technical Criteria
Given
A CCN has been constructed with prefix, equipment ID, and waybill date
When
The system validates the CCN format
Then
The CCN format must be valid according to customs requirements or the construction process must be rejected
R-GCX146-cbl-01297
Set CCN Status to 'RETURN'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to 'RETURN'' is invoked, and assuming that a valid ccn has been constructed for return cargo, when the system sets the ccn processing status, the desired outcome is that the ccn status must be set to 'return' to indicate return cargo processing.
💻 Technical Criteria
Given
A valid CCN has been constructed for return cargo
When
The system sets the CCN processing status
Then
The CCN status must be set to 'RETURN' to indicate return cargo processing
R-GCX146-cbl-01298
Set Transit Status to 'R'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'R'' is invoked, and assuming that a ccn is being created for return cargo processing, when the system assigns transit status, the desired outcome is that the transit status must be set to 'r' to indicate return movement.
💻 Technical Criteria
Given
A CCN is being created for return cargo processing
When
The system assigns transit status
Then
The transit status must be set to 'R' to indicate return movement
R-GCX146-cbl-01299
Populate Shipper Data from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Populate Shipper Data from Waybill' is invoked, and assuming that a waybill record contains shipper information for the equipment, when the system creates a return ccn record, the desired outcome is that all relevant shipper data must be extracted from the waybill and populated into the ccn record.
💻 Technical Criteria
Given
A waybill record contains shipper information for the equipment
When
The system creates a return CCN record
Then
All relevant shipper data must be extracted from the waybill and populated into the CCN record
R-GCX146-cbl-01300
Populate Consignee Data from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Populate Consignee Data from Waybill' is invoked, and assuming that a waybill record contains consignee information for the equipment, when the system creates a return ccn record, the desired outcome is that all relevant consignee data must be extracted from the waybill and populated into the ccn record.
💻 Technical Criteria
Given
A waybill record contains consignee information for the equipment
When
The system creates a return CCN record
Then
All relevant consignee data must be extracted from the waybill and populated into the CCN record
R-GCX146-cbl-01301
Complete Return CCN Record
Process Rules
📊 Business Logic Narrative
When the process 'Complete Return CCN Record' is invoked, and assuming that ccn identifier, status, transit status, shipper data, and consignee data have been populated, when the system finalizes the return ccn record, the desired outcome is that the ccn record must be marked as complete with all required fields populated for customs processing.
💻 Technical Criteria
Given
CCN identifier, status, transit status, shipper data, and consignee data have been populated
When
The system finalizes the return CCN record
Then
The CCN record must be marked as complete with all required fields populated for customs processing
R-GCX146-cbl-01490
Construct CCN Prefix '6105E'
Definitional Rules
📊 Business Logic Narrative
When the process 'Construct CCN Prefix '6105E'' is invoked, and assuming that a return cargo ccn needs to be created, when the system constructs the ccn identifier, the desired outcome is that the ccn must start with the standard prefix '6105e'.
💻 Technical Criteria
Given
A return cargo CCN needs to be created
When
The system constructs the CCN identifier
Then
The CCN must start with the standard prefix '6105E'
R-GCX146-cbl-01491
Build Equipment ID Component
Validation Rules
📊 Business Logic Narrative
When the process 'Build Equipment ID Component' is invoked, and assuming that an equipment id from waybill data, when the equipment id is being formatted for ccn construction, the desired outcome is that the equipment id must be exactly 10 characters in length and padded with spaces if necessary.
💻 Technical Criteria
Given
An equipment ID from waybill data
When
The equipment ID is being formatted for CCN construction
Then
The equipment ID must be exactly 10 characters in length and padded with spaces if necessary
R-GCX146-cbl-01492
Equipment ID Length Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment ID Length Valid?' is invoked, and assuming that an equipment id extracted from waybill, when the system validates the equipment id length, the desired outcome is that if the equipment id is less than 10 characters, it must be padded with spaces to reach exactly 10 characters.
💻 Technical Criteria
Given
An equipment ID extracted from waybill
When
The system validates the equipment ID length
Then
If the equipment ID is less than 10 characters, it must be padded with spaces to reach exactly 10 characters
R-GCX146-cbl-01493
Format Date Component YYMMDD
Computation Rules
📊 Business Logic Narrative
When the process 'Format Date Component YYMMDD' is invoked, and assuming that waybill date components (year, month, day), when the date is being formatted for ccn construction, the desired outcome is that the date must be formatted as yymmdd with 2-digit year, 2-digit month, and 2-digit day.
💻 Technical Criteria
Given
Waybill date components (year, month, day)
When
The date is being formatted for CCN construction
Then
The date must be formatted as YYMMDD with 2-digit year, 2-digit month, and 2-digit day
R-GCX146-cbl-01494
Concatenate CCN Components
Computation Rules
📊 Business Logic Narrative
When the process 'Concatenate CCN Components' is invoked, and assuming that ccn prefix '6105e', formatted equipment id, and formatted date, when the system constructs the complete ccn, the desired outcome is that the ccn must be formed by concatenating prefix + equipment id + date in that exact order.
💻 Technical Criteria
Given
CCN prefix '6105E', formatted equipment ID, and formatted date
When
The system constructs the complete CCN
Then
The CCN must be formed by concatenating prefix + equipment ID + date in that exact order
R-GCX146-cbl-01495
Validate CCN Format Structure
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CCN Format Structure' is invoked, and assuming that a constructed ccn string, when the system validates the ccn format, the desired outcome is that the ccn must have exactly 22 characters total length, start with '6105e', contain valid equipment id, and end with valid yymmdd date.
💻 Technical Criteria
Given
A constructed CCN string
When
The system validates the CCN format
Then
The CCN must have exactly 22 characters total length, start with '6105E', contain valid equipment ID, and end with valid YYMMDD date
R-GCX146-cbl-01496
CCN Format Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Format Valid?' is invoked, and assuming that a constructed ccn with all components, when the system checks format compliance, the desired outcome is that if the ccn format is invalid, processing must stop with format error; if valid, processing continues to status assignment.
💻 Technical Criteria
Given
A constructed CCN with all components
When
The system checks format compliance
Then
If the CCN format is invalid, processing must stop with format error; if valid, processing continues to status assignment
R-GCX146-cbl-01497
Set CCN Status to 'RETURN'
Process Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to 'RETURN'' is invoked, and assuming that a valid ccn format has been constructed, when the system assigns status to the ccn, the desired outcome is that the ccn status must be set to 'return' to indicate return cargo processing.
💻 Technical Criteria
Given
A valid CCN format has been constructed
When
The system assigns status to the CCN
Then
The CCN status must be set to 'RETURN' to indicate return cargo processing
R-GCX146-cbl-01498
Set Transit Status to 'R'
Process Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'R'' is invoked, and assuming that a ccn with return status assigned, when the system sets transit status, the desired outcome is that the transit status must be set to 'r' to indicate return movement.
💻 Technical Criteria
Given
A CCN with return status assigned
When
The system sets transit status
Then
The transit status must be set to 'R' to indicate return movement
R-GCX146-cbl-01499
Assign CCN Key Fields
Process Rules
📊 Business Logic Narrative
When the process 'Assign CCN Key Fields' is invoked, and assuming that a ccn with valid format, return status, and transit status, when the system assigns key fields, the desired outcome is that all ccn key fields including equipment id, waybill date, and sequence must be properly assigned for database storage.
💻 Technical Criteria
Given
A CCN with valid format, return status, and transit status
When
The system assigns key fields
Then
All CCN key fields including equipment ID, waybill date, and sequence must be properly assigned for database storage
R-GCX146-cbl-01637
CCN Format Structure Validation Not Found
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Format Structure Validation Not Found' is invoked, and assuming that a ccn is being processed in the system, when the system attempts to validate the ccn format structure, the desired outcome is that no specific format validation logic is executed and the ccn is accepted based on existence alone.
💻 Technical Criteria
Given
A CCN is being processed in the system
When
The system attempts to validate the CCN format structure
Then
No specific format validation logic is executed and the CCN is accepted based on existence alone
R-GCX146-cbl-01302
Waybill Data Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Data Available?' is invoked, and assuming that a return ccn requires data population from waybill records, when the system accesses the waybill database for the specified equipment, the desired outcome is that the system must verify waybill data exists before proceeding with shipper and consignee information extraction.
💻 Technical Criteria
Given
A return CCN requires data population from waybill records
When
The system accesses the waybill database for the specified equipment
Then
The system must verify waybill data exists before proceeding with shipper and consignee information extraction
R-GCX146-cbl-01303
Extract Shipper Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Shipper Information' is invoked, and assuming that valid waybill data exists for the equipment, when the system processes shipper information from the waybill record, the desired outcome is that the system must extract shipper name, address, and identification details from the waybill.
💻 Technical Criteria
Given
Valid waybill data exists for the equipment
When
The system processes shipper information from the waybill record
Then
The system must extract shipper name, address, and identification details from the waybill
R-GCX146-cbl-01304
Extract Consignee Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Consignee Information' is invoked, and assuming that valid waybill data exists for the equipment, when the system processes consignee information from the waybill record, the desired outcome is that the system must extract consignee name, address, and identification details from the waybill.
💻 Technical Criteria
Given
Valid waybill data exists for the equipment
When
The system processes consignee information from the waybill record
Then
The system must extract consignee name, address, and identification details from the waybill
R-GCX146-cbl-01305
Extract Shipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Shipment Details' is invoked, and assuming that valid waybill data exists for the equipment, when the system processes shipment details from the waybill record, the desired outcome is that the system must extract commodity information, weight, origin station, destination station, and other shipment-specific data.
💻 Technical Criteria
Given
Valid waybill data exists for the equipment
When
The system processes shipment details from the waybill record
Then
The system must extract commodity information, weight, origin station, destination station, and other shipment-specific data
R-GCX146-cbl-01306
Populate CCN Shipper Fields
Action Rules
📊 Business Logic Narrative
When the process 'Populate CCN Shipper Fields' is invoked, and assuming that shipper information has been extracted from the waybill, when the system updates the return ccn record with shipper data, the desired outcome is that the ccn record must be populated with shipper name, address, and identification in the appropriate ccn shipper fields.
💻 Technical Criteria
Given
Shipper information has been extracted from the waybill
When
The system updates the return CCN record with shipper data
Then
The CCN record must be populated with shipper name, address, and identification in the appropriate CCN shipper fields
R-GCX146-cbl-01307
Populate CCN Consignee Fields
Action Rules
📊 Business Logic Narrative
When the process 'Populate CCN Consignee Fields' is invoked, and assuming that consignee information has been extracted from the waybill, when the system updates the return ccn record with consignee data, the desired outcome is that the ccn record must be populated with consignee name, address, and identification in the appropriate ccn consignee fields.
💻 Technical Criteria
Given
Consignee information has been extracted from the waybill
When
The system updates the return CCN record with consignee data
Then
The CCN record must be populated with consignee name, address, and identification in the appropriate CCN consignee fields
R-GCX146-cbl-01308
Populate Additional Shipment Data
Action Rules
📊 Business Logic Narrative
When the process 'Populate Additional Shipment Data' is invoked, and assuming that shipment details have been extracted from the waybill, when the system updates the return ccn record with shipment data, the desired outcome is that the ccn record must be populated with commodity information, weight, origin/destination stations, and other relevant shipment data.
💻 Technical Criteria
Given
Shipment details have been extracted from the waybill
When
The system updates the return CCN record with shipment data
Then
The CCN record must be populated with commodity information, weight, origin/destination stations, and other relevant shipment data
R-GCX146-cbl-01309
All Required Data Present?
Validation Rules
📊 Business Logic Narrative
When the process 'All Required Data Present?' is invoked, and assuming that ccn record has been populated with waybill data, when the system validates data completeness for the return ccn, the desired outcome is that the system must verify that all required shipper, consignee, and shipment fields contain valid data before marking the population process as complete.
💻 Technical Criteria
Given
CCN record has been populated with waybill data
When
The system validates data completeness for the return CCN
Then
The system must verify that all required shipper, consignee, and shipment fields contain valid data before marking the population process as complete
R-GCX146-cbl-01310
Set Data Population Complete Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Data Population Complete Flag' is invoked, and assuming that all required data fields have been validated as complete in the return ccn, when the system completes the data population process, the desired outcome is that the system must set the data population complete flag to indicate successful completion of the return ccn data population.
💻 Technical Criteria
Given
All required data fields have been validated as complete in the return CCN
When
The system completes the data population process
Then
The system must set the data population complete flag to indicate successful completion of the return CCN data population
R-GCX146-cbl-01311
Log Missing Data Warning
Process Rules
📊 Business Logic Narrative
When the process 'Log Missing Data Warning' is invoked, and assuming that waybill data is unavailable or required ccn data fields are incomplete, when the system encounters missing or incomplete data during population, the desired outcome is that the system must log a warning message indicating which data elements are missing and continue processing.
💻 Technical Criteria
Given
Waybill data is unavailable or required CCN data fields are incomplete
When
The system encounters missing or incomplete data during population
Then
The system must log a warning message indicating which data elements are missing and continue processing
R-GCX146-cbl-00416
W300-SEND-TO-BROKER: Primary Broker Notification
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'W300-SEND-TO-BROKER: Primary Broker Notification', assuming that a ccn key starts with '6105' and cargo type is not 'i' and current status is not 'return' or 'manual', when the system processes broker notifications for the cargo, the desired outcome is that the system should send notifications to the primary broker using their configured communication channels.
💻 Technical Criteria
EXCLUDING
A CCN key starts with '6105' and cargo type is not 'I' and current status is not 'RETURN' or 'MANUAL'
When
The system processes broker notifications for the cargo
Then
The system should send notifications to the primary broker using their configured communication channels
R-GCX146-cbl-01312
Check Broker Configuration
Validation Rules
📊 Business Logic Narrative
When the process 'Check Broker Configuration' is invoked, and assuming that a ccn record requires broker notification, when the system checks for primary broker configuration, the desired outcome is that the system should verify if a primary broker exists and is configured for notifications.
💻 Technical Criteria
Given
A CCN record requires broker notification
When
The system checks for primary broker configuration
Then
The system should verify if a primary broker exists and is configured for notifications
R-GCX146-cbl-01321
Skip Notification
Decision Rules
📊 Business Logic Narrative
When the process 'Skip Notification' is invoked, and assuming that a ccn record requires broker notification, when no primary broker is configured in the system, the desired outcome is that the system should skip the primary broker notification process and continue with other processing.
💻 Technical Criteria
Given
A CCN record requires broker notification
When
No primary broker is configured in the system
Then
The system should skip the primary broker notification process and continue with other processing
R-GCX146-cbl-01638
Prepare CCN Data for X12 Format
Process Rules
📊 Business Logic Narrative
When the process 'Prepare CCN Data for X12 Format' is invoked, and assuming that a valid ccn record exists with equipment id, status updates, and transit information, when the system needs to send broker notification via x12 edi, the desired outcome is that the ccn data is formatted according to x12 edi message structure with broker-specific routing information.
💻 Technical Criteria
Given
A valid CCN record exists with equipment ID, status updates, and transit information
When
The system needs to send broker notification via X12 EDI
Then
The CCN data is formatted according to X12 EDI message structure with broker-specific routing information
R-GCX146-cbl-01639
Call GCCS309C Module
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCS309C Module' is invoked, and assuming that ccn data has been prepared in x12 edi format, when the system is ready to transmit the broker notification, the desired outcome is that the gccs309c module is called to process the x12 edi transmission.
💻 Technical Criteria
Given
CCN data has been prepared in X12 EDI format
When
The system is ready to transmit the broker notification
Then
The GCCS309C module is called to process the X12 EDI transmission
R-GCX146-cbl-01775
Retrieve CCN Record from Database
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve CCN Record from Database' is invoked, and assuming that a ccn number exists in the system, when the system needs to prepare ccn data for x12 transmission, the desired outcome is that the system retrieves the complete ccn record from the gcccrt database.
💻 Technical Criteria
Given
A CCN number exists in the system
When
The system needs to prepare CCN data for X12 transmission
Then
The system retrieves the complete CCN record from the GCCCRT database
R-GCX146-cbl-01776
Extract CCN Number
Process Rules
📊 Business Logic Narrative
When the process 'Extract CCN Number' is invoked, and assuming that a ccn record has been retrieved from the database, when the system processes the ccn record, the desired outcome is that the system extracts the ccn number field from the record structure.
💻 Technical Criteria
Given
A CCN record has been retrieved from the database
When
The system processes the CCN record
Then
The system extracts the CCN number field from the record structure
R-GCX146-cbl-01777
Format CCN for X12 Structure
Process Rules
📊 Business Logic Narrative
When the process 'Format CCN for X12 Structure' is invoked, and assuming that a ccn number has been extracted from the database record, when the system prepares the ccn for x12 transmission, the desired outcome is that the system formats the ccn data according to x12 edi structure specifications.
💻 Technical Criteria
Given
A CCN number has been extracted from the database record
When
The system prepares the CCN for X12 transmission
Then
The system formats the CCN data according to X12 EDI structure specifications
R-GCX146-cbl-01778
Compress CCN Number
Process Rules
📊 Business Logic Narrative
When the process 'Compress CCN Number' is invoked, and assuming that a ccn number is formatted for x12 structure, when the system processes the ccn for compression, the desired outcome is that the system compresses the ccn number by removing redundant characters and formatting.
💻 Technical Criteria
Given
A CCN number is formatted for X12 structure
When
The system processes the CCN for compression
Then
The system compresses the CCN number by removing redundant characters and formatting
R-GCX146-cbl-01779
Remove Spaces from CCN
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from CCN' is invoked, and assuming that a ccn number contains spaces or padding characters, when the system compresses the ccn number, the desired outcome is that the system removes all spaces and padding characters from the ccn.
💻 Technical Criteria
Given
A CCN number contains spaces or padding characters
When
The system compresses the CCN number
Then
The system removes all spaces and padding characters from the CCN
R-GCX146-cbl-01780
Organize Numeric Sequences
Process Rules
📊 Business Logic Narrative
When the process 'Organize Numeric Sequences' is invoked, and assuming that a ccn contains numeric sequences that need organization, when the system processes the compressed ccn, the desired outcome is that the system organizes numeric sequences according to x12 format requirements.
💻 Technical Criteria
Given
A CCN contains numeric sequences that need organization
When
The system processes the compressed CCN
Then
The system organizes numeric sequences according to X12 format requirements
R-GCX146-cbl-01781
Validate CCN Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CCN Format' is invoked, and assuming that a ccn has been processed and organized for x12 format, when the system validates the ccn format, the desired outcome is that the system checks that the ccn format complies with x12 edi standards.
💻 Technical Criteria
Given
A CCN has been processed and organized for X12 format
When
The system validates the CCN format
Then
The system checks that the CCN format complies with X12 EDI standards
R-GCX146-cbl-01782
CCN Format Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Format Valid?' is invoked, and assuming that a ccn format has been validated against x12 standards, when the system evaluates the validation results, the desired outcome is that the system determines if the ccn format is valid for transmission or if format errors exist.
💻 Technical Criteria
Given
A CCN format has been validated against X12 standards
When
The system evaluates the validation results
Then
The system determines if the CCN format is valid for transmission or if format errors exist
R-GCX146-cbl-01783
Set X12 CCN Field
Process Rules
📊 Business Logic Narrative
When the process 'Set X12 CCN Field' is invoked, and assuming that a ccn format has been validated as correct for x12 transmission, when the system processes the valid ccn, the desired outcome is that the system assigns the ccn to the appropriate x12 message field.
💻 Technical Criteria
Given
A CCN format has been validated as correct for X12 transmission
When
The system processes the valid CCN
Then
The system assigns the CCN to the appropriate X12 message field
R-GCX146-cbl-01785
Format Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Waybill Information' is invoked, and assuming that waybill data is available for the ccn, when the system prepares x12 message components, the desired outcome is that the system formats waybill information according to x12 edi standards.
💻 Technical Criteria
Given
Waybill data is available for the CCN
When
The system prepares X12 message components
Then
The system formats waybill information according to X12 EDI standards
R-GCX146-cbl-01786
Set Cargo Status Code
Process Rules
📊 Business Logic Narrative
When the process 'Set Cargo Status Code' is invoked, and assuming that cargo status information is available in the ccn record, when the system prepares x12 message data, the desired outcome is that the system assigns the appropriate cargo status code for x12 transmission.
💻 Technical Criteria
Given
Cargo status information is available in the CCN record
When
The system prepares X12 message data
Then
The system assigns the appropriate cargo status code for X12 transmission
R-GCX146-cbl-01789
Log Format Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Format Error', assuming that a ccn format validation has failed, when the system encounters invalid ccn format, the desired outcome is that the system logs the format error for troubleshooting and audit purposes.
💻 Technical Criteria
EXCLUDING
A CCN format validation has failed
When
The system encounters invalid CCN format
Then
The system logs the format error for troubleshooting and audit purposes
R-GCX146-cbl-01795
Populate CCN Information
Process Rules
📊 Business Logic Narrative
When the process 'Populate CCN Information' is invoked, and assuming that a broker notification is being prepared with valid ccn data, when ccn information is available, the desired outcome is that the system populates ccn number, status, and related customs information in gcx019 parameters.
💻 Technical Criteria
Given
A broker notification is being prepared with valid CCN data
When
CCN information is available
Then
The system populates CCN number, status, and related customs information in GCX019 parameters
R-GCX146-cbl-01796
Set Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment Details' is invoked, and assuming that equipment information is available for the ccn, when equipment details are being added to the notification, the desired outcome is that the system populates equipment id, type, and status in gcx019 parameters.
💻 Technical Criteria
Given
Equipment information is available for the CCN
When
Equipment details are being added to the notification
Then
The system populates equipment ID, type, and status in GCX019 parameters
R-GCX146-cbl-01797
Add Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Waybill Information' is invoked, and assuming that waybill information exists for the equipment, when waybill details are being added to the notification, the desired outcome is that the system populates shipper, consignee, and commodity information in gcx019 parameters.
💻 Technical Criteria
Given
Waybill information exists for the equipment
When
Waybill details are being added to the notification
Then
The system populates shipper, consignee, and commodity information in GCX019 parameters
R-GCX146-cbl-01798
Set Station Codes
Process Rules
📊 Business Logic Narrative
When the process 'Set Station Codes' is invoked, and assuming that station information is available from the manifest or waybill, when station codes are being set in the notification, the desired outcome is that the system populates origin station, destination station, and border crossing codes in gcx019 parameters.
💻 Technical Criteria
Given
Station information is available from the manifest or waybill
When
Station codes are being set in the notification
Then
The system populates origin station, destination station, and border crossing codes in GCX019 parameters
R-GCX146-cbl-01801
Validate Required Fields
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Required Fields' is invoked, and assuming that gcx019 parameters have been populated, when the system validates required fields, the desired outcome is that all mandatory fields including communication method, ccn, equipment id, and contact information must be present and valid.
💻 Technical Criteria
Given
GCX019 parameters have been populated
When
The system validates required fields
Then
All mandatory fields including communication method, CCN, equipment ID, and contact information must be present and valid
R-GCX146-cbl-00453
Store CCN Key in Special Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Store CCN Key in Special Manifest' is invoked, and assuming that a ccn key exists for the cargo being processed, when a special manifest is being created, the desired outcome is that the ccn key must be stored in the special manifest record for cargo identification.
💻 Technical Criteria
Given
A CCN key exists for the cargo being processed
When
A special manifest is being created
Then
The CCN key must be stored in the special manifest record for cargo identification
R-GCX146-cbl-00454
Build Special Manifest Input
Process Rules
📊 Business Logic Narrative
When the process 'Build Special Manifest Input' is invoked, and assuming that border information, ccn key, and record type are available, when the system builds the special manifest input structure, the desired outcome is that all required data elements must be assembled into the proper input format for manifest processing.
💻 Technical Criteria
Given
Border information, CCN key, and record type are available
When
The system builds the special manifest input structure
Then
All required data elements must be assembled into the proper input format for manifest processing
R-GCX146-cbl-00456
Search GCCCRT Database
Action Rules
📊 Business Logic Narrative
When the process 'Search GCCCRT Database' is invoked, and assuming that a ccn usability validation is requested for specific equipment, when the system searches the gcccrt database using equipment id and waybill key, the desired outcome is that the system retrieves ccn records matching the search criteria.
💻 Technical Criteria
Given
A CCN usability validation is requested for specific equipment
When
The system searches the GCCCRT database using equipment ID and waybill key
Then
The system retrieves CCN records matching the search criteria
R-GCX146-cbl-00457
CCN Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Record Found?' is invoked, and assuming that a search has been performed in the gcccrt database, when the system evaluates the search results, the desired outcome is that if a ccn record is found, proceed to bond creation flag check, otherwise continue processing.
💻 Technical Criteria
Given
A search has been performed in the GCCCRT database
When
The system evaluates the search results
Then
If a CCN record is found, proceed to bond creation flag check, otherwise continue processing
R-GCX146-cbl-00458
Bond Created Flag = 'Y'?
Validation Rules
📊 Business Logic Narrative
When the process 'Bond Created Flag = 'Y'?' is invoked, and assuming that a ccn record exists for the equipment, when the system checks the bond creation flag value, the desired outcome is that if bond created flag equals 'y', mark ccn as not usable, otherwise mark ccn as usable.
💻 Technical Criteria
Given
A CCN record exists for the equipment
When
The system checks the bond creation flag value
Then
If bond created flag equals 'Y', mark CCN as not usable, otherwise mark CCN as usable
R-GCX146-cbl-00459
CCN is Not Usable
Decision Rules
📊 Business Logic Narrative
When the process 'CCN is Not Usable' is invoked, and assuming that a ccn record exists and bond created flag equals 'y', when the system evaluates ccn usability, the desired outcome is that the ccn is marked as not usable for train processing.
💻 Technical Criteria
Given
A CCN record exists and bond created flag equals 'Y'
When
The system evaluates CCN usability
Then
The CCN is marked as not usable for train processing
R-GCX146-cbl-00460
CCN is Usable
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'CCN is Usable', assuming that a ccn record exists and bond created flag does not equal 'y', when the system evaluates ccn usability, the desired outcome is that the ccn is marked as usable for train processing.
💻 Technical Criteria
EXCLUDING
A CCN record exists and bond created flag does not equal 'Y'
When
The system evaluates CCN usability
Then
The CCN is marked as usable for train processing
R-GCX146-cbl-00461
Add 'CCN FOUND NOT USABLE' Status Message
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add 'CCN FOUND NOT USABLE' Status Message', assuming that ccn is marked as not usable and request type is verify, when the system processes the unusable ccn for verify operation, the desired outcome is that the system adds 'ccn found not usable' status message to the response.
💻 Technical Criteria
EXCLUDING
CCN is marked as not usable and request type is VERIFY
When
The system processes the unusable CCN for VERIFY operation
Then
The system adds 'CCN FOUND NOT USABLE' status message to the response
R-GCX146-cbl-00462
Request Type = VERIFY?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Request Type = VERIFY?', assuming that ccn has been determined as not usable, when the system checks the request type, the desired outcome is that if request type is verify, add status message, otherwise continue processing without message.
💻 Technical Criteria
EXCLUDING
CCN has been determined as not usable
When
The system checks the request type
Then
If request type is VERIFY, add status message, otherwise continue processing without message
R-GCX146-cbl-00508
Perform Container Waybill Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Perform Container Waybill Lookup' is invoked, and assuming that a container id has been extracted and flat car processing flag is set, when the system needs to find waybill information for the container, the desired outcome is that the system performs a waybill lookup using the container id to retrieve associated shipping documentation.
💻 Technical Criteria
Given
A container ID has been extracted and flat car processing flag is set
When
The system needs to find waybill information for the container
Then
The system performs a waybill lookup using the container ID to retrieve associated shipping documentation
R-GCX146-cbl-00509
Container Waybill Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Container Waybill Found?' is invoked, and assuming that a waybill lookup has been performed for a container, when the system evaluates the lookup results, the desired outcome is that the system determines if a waybill was found and proceeds with container validation if found, or uses inquiry database lookup if no waybill is found.
💻 Technical Criteria
Given
A waybill lookup has been performed for a container
When
The system evaluates the lookup results
Then
The system determines if a waybill was found and proceeds with container validation if found, or uses inquiry database lookup if no waybill is found
R-GCX146-cbl-00510
Use Inquiry Database for Container
Action Rules
📊 Business Logic Narrative
When the process 'Use Inquiry Database for Container' is invoked, and assuming that no waybill was found for a container through primary lookup, when the system needs alternative container information, the desired outcome is that the system accesses the inquiry database to retrieve container information.
💻 Technical Criteria
Given
No waybill was found for a container through primary lookup
When
The system needs alternative container information
Then
The system accesses the inquiry database to retrieve container information
R-GCX146-cbl-00512
Validate Individual Container
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Individual Container' is invoked, and assuming that container information has been retrieved either from waybill lookup or inquiry database, when the system processes the container for train manifest inclusion, the desired outcome is that the system validates the individual container against train manifest requirements and business rules.
💻 Technical Criteria
Given
Container information has been retrieved either from waybill lookup or inquiry database
When
The system processes the container for train manifest inclusion
Then
The system validates the individual container against train manifest requirements and business rules
R-GCX146-cbl-00518
Initialize Inquiry Database Search
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Inquiry Database Search' is invoked, and assuming that primary waybill lookup has failed for equipment, when system initiates inquiry database search, the desired outcome is that initialize inquiry search parameters and clear previous search results.
💻 Technical Criteria
Given
Primary waybill lookup has failed for equipment
When
System initiates inquiry database search
Then
Initialize inquiry search parameters and clear previous search results
R-GCX146-cbl-00519
Search SHIPROOT Inquiry Database
Action Rules
📊 Business Logic Narrative
When the process 'Search SHIPROOT Inquiry Database' is invoked, and assuming that equipment requires waybill information and primary lookup failed, when system searches shiproot inquiry database, the desired outcome is that execute inquiry search using equipment identification parameters.
💻 Technical Criteria
Given
Equipment requires waybill information and primary lookup failed
When
System searches SHIPROOT inquiry database
Then
Execute inquiry search using equipment identification parameters
R-GCX146-cbl-00520
SHIPROOT Inquiry Found?
Decision Rules
📊 Business Logic Narrative
When the process 'SHIPROOT Inquiry Found?' is invoked, and assuming that shiproot inquiry database search has been executed, when system evaluates search results, the desired outcome is that if waybill record found in shiproot then proceed with data retrieval, otherwise continue to fw-iq database search.
💻 Technical Criteria
Given
SHIPROOT inquiry database search has been executed
When
System evaluates search results
Then
If waybill record found in SHIPROOT then proceed with data retrieval, otherwise continue to FW-IQ database search
R-GCX146-cbl-00521
Retrieve Waybill Data from SHIPROOT-INQ
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Waybill Data from SHIPROOT-INQ' is invoked, and assuming that shiproot inquiry database contains waybill record for equipment, when system retrieves waybill data, the desired outcome is that extract waybill details from shiproot-inq record and prepare for processing.
💻 Technical Criteria
Given
SHIPROOT inquiry database contains waybill record for equipment
When
System retrieves waybill data
Then
Extract waybill details from SHIPROOT-INQ record and prepare for processing
R-GCX146-cbl-00522
Search FW-IQ Database
Action Rules
📊 Business Logic Narrative
When the process 'Search FW-IQ Database' is invoked, and assuming that shiproot inquiry database search failed to find waybill information, when system searches fw-iq database, the desired outcome is that execute equipment inquiry search in fw-iq database using equipment parameters.
💻 Technical Criteria
Given
SHIPROOT inquiry database search failed to find waybill information
When
System searches FW-IQ database
Then
Execute equipment inquiry search in FW-IQ database using equipment parameters
R-GCX146-cbl-00523
FW-IQ Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'FW-IQ Record Found?' is invoked, and assuming that fw-iq database search has been executed, when system evaluates search results, the desired outcome is that if equipment record found in fw-iq then proceed with information extraction, otherwise return waybill not found status.
💻 Technical Criteria
Given
FW-IQ database search has been executed
When
System evaluates search results
Then
If equipment record found in FW-IQ then proceed with information extraction, otherwise return waybill not found status
R-GCX146-cbl-00526
Is Flat Car with Containers?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Flat Car with Containers?' is invoked, and assuming that equipment configuration has been evaluated, when system determines processing requirements, the desired outcome is that if equipment is flat car with containers then initiate container t/c xref processing, otherwise proceed with standard waybill processing.
💻 Technical Criteria
Given
Equipment configuration has been evaluated
When
System determines processing requirements
Then
If equipment is flat car with containers then initiate container T/C XREF processing, otherwise proceed with standard waybill processing
R-GCX146-cbl-00530
Return Waybill Information Found
Process Rules
📊 Business Logic Narrative
When the process 'Return Waybill Information Found' is invoked, and assuming that waybill information has been successfully retrieved from inquiry database, when system completes inquiry processing, the desired outcome is that return status indicating waybill information found and available for processing.
💻 Technical Criteria
Given
Waybill information has been successfully retrieved from inquiry database
When
System completes inquiry processing
Then
Return status indicating waybill information found and available for processing
R-GCX146-cbl-00531
Return Waybill Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Return Waybill Not Found' is invoked, and assuming that all inquiry database searches have failed to locate waybill information, when system completes inquiry processing, the desired outcome is that return status indicating waybill information not found in inquiry databases.
💻 Technical Criteria
Given
All inquiry database searches have failed to locate waybill information
When
System completes inquiry processing
Then
Return status indicating waybill information not found in inquiry databases
R-GCX146-cbl-00532
Extract Cargo Origin/Destination from Waybill
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Cargo Origin/Destination from Waybill' is invoked, and assuming that equipment has associated waybill data available, when system processes equipment for load/empty status determination, the desired outcome is that system extracts cargo origin and destination information from waybill to establish baseline load status.
💻 Technical Criteria
Given
Equipment has associated waybill data available
When
System processes equipment for load/empty status determination
Then
System extracts cargo origin and destination information from waybill to establish baseline load status
R-GCX146-cbl-00533
Analyze Input Load/Empty Indicator
Process Rules
📊 Business Logic Narrative
When the process 'Analyze Input Load/Empty Indicator' is invoked, and assuming that equipment input contains load/empty status specifications, when system analyzes input load/empty indicator, the desired outcome is that system captures and processes the specified load/empty status for validation against waybill data.
💻 Technical Criteria
Given
Equipment input contains load/empty status specifications
When
System analyzes input load/empty indicator
Then
System captures and processes the specified load/empty status for validation against waybill data
R-GCX146-cbl-00534
Input Status Specified?
Validation Rules
📊 Business Logic Narrative
When the process 'Input Status Specified?' is invoked, and assuming that equipment processing requires load/empty status determination, when system checks if load/empty status is specified in input, the desired outcome is that system determines if explicit status specification exists or if default waybill status should be used.
💻 Technical Criteria
Given
Equipment processing requires load/empty status determination
When
System checks if load/empty status is specified in input
Then
System determines if explicit status specification exists or if default waybill status should be used
R-GCX146-cbl-00535
Compare Input vs Waybill Status
Validation Rules
📊 Business Logic Narrative
When the process 'Compare Input vs Waybill Status' is invoked, and assuming that both input status specification and waybill status are available, when system compares input load/empty status against waybill status, the desired outcome is that system identifies matches or discrepancies between specified and waybill-derived status.
💻 Technical Criteria
Given
Both input status specification and waybill status are available
When
System compares input load/empty status against waybill status
Then
System identifies matches or discrepancies between specified and waybill-derived status
R-GCX146-cbl-00536
Status Match?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Match?' is invoked, and assuming that input status and waybill status have been compared, when system evaluates status match results, the desired outcome is that system proceeds with cargo movement validation if statuses match or generates warning if they don't match.
💻 Technical Criteria
Given
Input status and waybill status have been compared
When
System evaluates status match results
Then
System proceeds with cargo movement validation if statuses match or generates warning if they don't match
R-GCX146-cbl-00537
Validate Against Cargo Movement Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Validate Against Cargo Movement Rules' is invoked, and assuming that equipment status matches between input and waybill data, when system validates against cargo movement rules, the desired outcome is that system confirms status compliance with cargo movement regulations and business policies.
💻 Technical Criteria
Given
Equipment status matches between input and waybill data
When
System validates against cargo movement rules
Then
System confirms status compliance with cargo movement regulations and business policies
R-GCX146-cbl-00541
Generate Status Validation Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Status Validation Warning' is invoked, and assuming that input load/empty status doesn't match waybill-derived status, when system processes status mismatch, the desired outcome is that system generates status validation warning and uses default waybill status.
💻 Technical Criteria
Given
Input load/empty status doesn't match waybill-derived status
When
System processes status mismatch
Then
System generates status validation warning and uses default waybill status
R-GCX146-cbl-00542
Use Default Status from Waybill
Decision Rules
📊 Business Logic Narrative
When the process 'Use Default Status from Waybill' is invoked, and assuming that no input status specified or input status validation fails, when system needs to determine equipment load/empty status, the desired outcome is that system uses default load/empty status derived from waybill data.
💻 Technical Criteria
Given
No input status specified or input status validation fails
When
System needs to determine equipment load/empty status
Then
System uses default load/empty status derived from waybill data
R-GCX146-cbl-00543
Assign Final Load/Empty Status
Action Rules
📊 Business Logic Narrative
When the process 'Assign Final Load/Empty Status' is invoked, and assuming that status validation process is complete, when system assigns final load/empty status to equipment, the desired outcome is that system sets definitive load/empty status from validated input, default waybill data, or validation results.
💻 Technical Criteria
Given
Status validation process is complete
When
System assigns final load/empty status to equipment
Then
System sets definitive load/empty status from validated input, default waybill data, or validation results
R-GCX146-cbl-00558
Access FW-IQ Inquiry Database
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Access FW-IQ Inquiry Database', assuming that a container requires waybill information and primary waybill data is not available, when the system needs to access container waybill data, the desired outcome is that the system accesses the fw-iq inquiry database to retrieve container information.
💻 Technical Criteria
EXCLUDING
A container requires waybill information and primary waybill data is not available
When
The system needs to access container waybill data
Then
The system accesses the FW-IQ inquiry database to retrieve container information
R-GCX146-cbl-00561
Retrieve Container Waybill Data
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Container Waybill Data' is invoked, and assuming that a container id has been extracted from t/c xref records, when the system needs detailed waybill information for the container, the desired outcome is that the system retrieves container waybill data from the fwswrwr container records.
💻 Technical Criteria
Given
A container ID has been extracted from T/C XREF records
When
The system needs detailed waybill information for the container
Then
The system retrieves container waybill data from the FWSWRWR container records
R-GCX146-cbl-00562
Waybill Data Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Data Available?' is invoked, and assuming that the system has attempted to retrieve container waybill data, when the system checks for waybill data availability, the desired outcome is that the system determines if waybill data is available and proceeds with processing if available, or marks as unavailable if not found.
💻 Technical Criteria
Given
The system has attempted to retrieve container waybill data
When
The system checks for waybill data availability
Then
The system determines if waybill data is available and proceeds with processing if available, or marks as unavailable if not found
R-GCX146-cbl-00563
Process Container Information
Process Rules
📊 Business Logic Narrative
When the process 'Process Container Information' is invoked, and assuming that container waybill data is available for processing, when the system processes the container information, the desired outcome is that the system extracts and processes relevant container business information including equipment details and waybill data.
💻 Technical Criteria
Given
Container waybill data is available for processing
When
The system processes the container information
Then
The system extracts and processes relevant container business information including equipment details and waybill data
R-GCX146-cbl-00566
Validate Container Sequence
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Container Sequence' is invoked, and assuming that equipment details have been extracted for containers, when the system validates container sequence information, the desired outcome is that the system verifies that container sequence numbers are valid and properly ordered for processing.
💻 Technical Criteria
Given
Equipment details have been extracted for containers
When
The system validates container sequence information
Then
The system verifies that container sequence numbers are valid and properly ordered for processing
R-GCX146-cbl-00567
Build Container Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Build Container Equipment Record' is invoked, and assuming that container sequence has been validated successfully, when the system builds the container equipment record, the desired outcome is that the system creates a complete equipment record containing all validated container information, equipment details, and waybill data.
💻 Technical Criteria
Given
Container sequence has been validated successfully
When
The system builds the container equipment record
Then
The system creates a complete equipment record containing all validated container information, equipment details, and waybill data
R-GCX146-cbl-00568
Container Processing Complete
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Container Processing Complete', assuming that container equipment record has been successfully built or container was not found or waybill data was not available, when the container processing reaches completion, the desired outcome is that the system marks container waybill inquiry processing as complete and the container is ready for subsequent operations.
💻 Technical Criteria
EXCLUDING
Container equipment record has been successfully built or container was not found or waybill data was not available
When
The container processing reaches completion
Then
The system marks container waybill inquiry processing as complete and the container is ready for subsequent operations
R-GCX146-cbl-00570
Waybill Data Not Available
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Waybill Data Not Available', assuming that a container id has been extracted but waybill data retrieval was attempted, when waybill data is not available for the container, the desired outcome is that the system proceeds to completion without processing waybill information for the container.
💻 Technical Criteria
EXCLUDING
A container ID has been extracted but waybill data retrieval was attempted
When
Waybill data is not available for the container
Then
The system proceeds to completion without processing waybill information for the container
R-GCX146-cbl-00583
Identify Bunch Bill Waybill
Definitional Rules
📊 Business Logic Narrative
When the process 'Identify Bunch Bill Waybill' is invoked, and assuming that a waybill record is being processed, when the system checks the equipment sequence field in the waybill, the desired outcome is that if sequence field contains numeric values greater than 1, the waybill is identified as a bunch bill containing multiple cars.
💻 Technical Criteria
Given
A waybill record is being processed
When
The system checks the equipment sequence field in the waybill
Then
If sequence field contains numeric values greater than 1, the waybill is identified as a bunch bill containing multiple cars
R-GCX146-cbl-00584
Retrieve Next Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Equipment Record' is invoked, and assuming that a bunch bill waybill has been identified with multiple equipment sequences, when the system processes equipment records sequentially using fwcmsget, the desired outcome is that each subsequent equipment record in the sequence is retrieved and processed until all cars in the bunch bill are handled.
💻 Technical Criteria
Given
A bunch bill waybill has been identified with multiple equipment sequences
When
The system processes equipment records sequentially using FWCMSGET
Then
Each subsequent equipment record in the sequence is retrieved and processed until all cars in the bunch bill are handled
R-GCX146-cbl-00585
Check for Additional Cars in Bunch Bill
Validation Rules
📊 Business Logic Narrative
When the process 'Check for Additional Cars in Bunch Bill' is invoked, and assuming that an equipment record is being processed from a bunch bill, when the system checks the equipment sequence counter against the total sequence count, the desired outcome is that if the current sequence number is less than the total sequence count, more cars exist to be processed.
💻 Technical Criteria
Given
An equipment record is being processed from a bunch bill
When
The system checks the equipment sequence counter against the total sequence count
Then
If the current sequence number is less than the total sequence count, more cars exist to be processed
R-GCX146-cbl-00587
Link Car to Original Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Link Car to Original Waybill' is invoked, and assuming that multiple cars are identified in a bunch bill waybill, when each car is processed individually, the desired outcome is that each car maintains a reference to the original waybill number and sequence position for proper tracking and reporting.
💻 Technical Criteria
Given
Multiple cars are identified in a bunch bill waybill
When
Each car is processed individually
Then
Each car maintains a reference to the original waybill number and sequence position for proper tracking and reporting
R-GCX146-cbl-00588
Update Equipment Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Totals' is invoked, and assuming that cars are being processed from a bunch bill waybill, when each car is successfully processed and validated, the desired outcome is that equipment totals including car count, loaded count, and empty count are incremented for each valid car in the sequence.
💻 Technical Criteria
Given
Cars are being processed from a bunch bill waybill
When
Each car is successfully processed and validated
Then
Equipment totals including car count, loaded count, and empty count are incremented for each valid car in the sequence
R-GCX146-cbl-00589
Complete Bunch Bill Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Bunch Bill Processing' is invoked, and assuming that a bunch bill with multiple cars is being processed, when all equipment records in the sequence have been retrieved and processed, the desired outcome is that the bunch bill processing is marked as complete and the system proceeds to the next waybill or operation.
💻 Technical Criteria
Given
A bunch bill with multiple cars is being processed
When
All equipment records in the sequence have been retrieved and processed
Then
The bunch bill processing is marked as complete and the system proceeds to the next waybill or operation
R-GCX146-cbl-00590
Check Waybill for Additional Cars
Definitional Rules
📊 Business Logic Narrative
When the process 'Check Waybill for Additional Cars' is invoked, and assuming that a waybill record exists in the system, when the system checks the waybill for additional car indicators, the desired outcome is that the system identifies if there are multiple cars associated with this waybill that require bunch bill processing.
💻 Technical Criteria
Given
A waybill record exists in the system
When
The system checks the waybill for additional car indicators
Then
The system identifies if there are multiple cars associated with this waybill that require bunch bill processing
R-GCX146-cbl-00591
Additional Cars Indicated?
Decision Rules
📊 Business Logic Narrative
When the process 'Additional Cars Indicated?' is invoked, and assuming that a waybill has been checked for additional cars, when additional cars are indicated in the waybill, the desired outcome is that the system initiates bunch bill sequence processing, otherwise skips to completion.
💻 Technical Criteria
Given
A waybill has been checked for additional cars
When
Additional cars are indicated in the waybill
Then
The system initiates bunch bill sequence processing, otherwise skips to completion
R-GCX146-cbl-00592
Initialize Bunch Bill Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Bunch Bill Sequence' is invoked, and assuming that additional cars have been detected on a waybill, when bunch bill processing is initiated, the desired outcome is that the system initializes sequence counters and prepares for sequential car retrieval.
💻 Technical Criteria
Given
Additional cars have been detected on a waybill
When
Bunch bill processing is initiated
Then
The system initializes sequence counters and prepares for sequential car retrieval
R-GCX146-cbl-00597
Extract Car Load/Empty Status
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Car Load/Empty Status' is invoked, and assuming that car equipment data has been processed, when the system extracts the load/empty status, the desired outcome is that each car is classified as either loaded or empty based on waybill information.
💻 Technical Criteria
Given
Car equipment data has been processed
When
The system extracts the load/empty status
Then
Each car is classified as either loaded or empty based on waybill information
R-GCX146-cbl-00601
Complete Bunch Bill Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Bunch Bill Processing' is invoked, and assuming that all cars in the bunch bill sequence have been processed or retrieval has failed, when the system completes bunch bill processing, the desired outcome is that all cars from the waybill are properly documented and totals are finalized.
💻 Technical Criteria
Given
All cars in the bunch bill sequence have been processed or retrieval has failed
When
The system completes bunch bill processing
Then
All cars from the waybill are properly documented and totals are finalized
R-GCX146-cbl-00602
Access US Route Database
Action Rules
📊 Business Logic Narrative
When the process 'Access US Route Database' is invoked, and assuming that equipment requires us customs processing for cross-border movement, when system accesses the us route database using equipment and waybill information, the desired outcome is that us route record is retrieved if it exists in the gcsusrt database.
💻 Technical Criteria
Given
Equipment requires US customs processing for cross-border movement
When
System accesses the US Route database using equipment and waybill information
Then
US Route record is retrieved if it exists in the GCSUSRT database
R-GCX146-cbl-00618
Extract Equipment ID and Waybill Date
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID and Waybill Date' is invoked, and assuming that canadian goods identified as returning from us with valid waybill data, when the system processes the equipment for return ccn creation, the desired outcome is that the system extracts equipment id and waybill date from the waybill record for ccn key construction.
💻 Technical Criteria
Given
Canadian goods identified as returning from US with valid waybill data
When
The system processes the equipment for return CCN creation
Then
The system extracts equipment ID and waybill date from the waybill record for CCN key construction
R-GCX146-cbl-00619
Build Return CCN Number
Computation Rules
📊 Business Logic Narrative
When the process 'Build Return CCN Number' is invoked, and assuming that equipment id and waybill date extracted from return cargo, when the system creates a new ccn for return processing, the desired outcome is that the system builds ccn key with format '6105e' + equipment id + waybill date + sequence number.
💻 Technical Criteria
Given
Equipment ID and waybill date extracted from return cargo
When
The system creates a new CCN for return processing
Then
The system builds CCN key with format '6105E' + equipment ID + waybill date + sequence number
R-GCX146-cbl-00620
Set CCN Status to RETURN
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to RETURN' is invoked, and assuming that a new ccn record being created for canadian return goods, when the system populates the ccn status field, the desired outcome is that the system sets the ccn status to 'return' to indicate return cargo processing.
💻 Technical Criteria
Given
A new CCN record being created for Canadian return goods
When
The system populates the CCN status field
Then
The system sets the CCN status to 'RETURN' to indicate return cargo processing
R-GCX146-cbl-00621
Set Transit Status to R
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to R' is invoked, and assuming that a ccn record for canadian return goods being processed, when the system sets the transit status indicator, the desired outcome is that the system assigns transit status 'r' to indicate return movement.
💻 Technical Criteria
Given
A CCN record for Canadian return goods being processed
When
The system sets the transit status indicator
Then
The system assigns transit status 'R' to indicate return movement
R-GCX146-cbl-00622
Populate Shipper Information
Process Rules
📊 Business Logic Narrative
When the process 'Populate Shipper Information' is invoked, and assuming that original waybill data with shipper information and a new return ccn record, when the system populates the return ccn with shipper details, the desired outcome is that the system copies shipper name and location information from the waybill to the ccn record.
💻 Technical Criteria
Given
Original waybill data with shipper information and a new return CCN record
When
The system populates the return CCN with shipper details
Then
The system copies shipper name and location information from the waybill to the CCN record
R-GCX146-cbl-00623
Populate Consignee Information
Process Rules
📊 Business Logic Narrative
When the process 'Populate Consignee Information' is invoked, and assuming that original waybill data with consignee information and a new return ccn record, when the system populates the return ccn with consignee details, the desired outcome is that the system copies consignee name and location information from the waybill to the ccn record.
💻 Technical Criteria
Given
Original waybill data with consignee information and a new return CCN record
When
The system populates the return CCN with consignee details
Then
The system copies consignee name and location information from the waybill to the CCN record
R-GCX146-cbl-00624
Insert Return CCN Record
Action Rules
📊 Business Logic Narrative
When the process 'Insert Return CCN Record' is invoked, and assuming that complete return ccn information including status, shipper, consignee, and equipment details, when the system attempts to create the ccn database record, the desired outcome is that the system inserts the new ccn record into the gcccrt database with application type '33' for canadian customs.
💻 Technical Criteria
Given
Complete return CCN information including status, shipper, consignee, and equipment details
When
The system attempts to create the CCN database record
Then
The system inserts the new CCN record into the GCCCRT database with application type '33' for Canadian customs
R-GCX146-cbl-00625
CCN Creation Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Creation Successful?' is invoked, and assuming that an attempt to create a return ccn record in the database, when the system checks the result of the ccn creation operation, the desired outcome is that the system determines success or failure based on the database operation return status.
💻 Technical Criteria
Given
An attempt to create a return CCN record in the database
When
The system checks the result of the CCN creation operation
Then
The system determines success or failure based on the database operation return status
R-GCX146-cbl-00629
Bypass CCN Database Lookup
Process Rules
📊 Business Logic Narrative
When the process 'Bypass CCN Database Lookup' is invoked, and assuming that equipment is flagged as idler type, when the system processes equipment for ccn requirements, the desired outcome is that ccn database lookup is bypassed and not performed.
💻 Technical Criteria
Given
Equipment is flagged as idler type
When
The system processes equipment for CCN requirements
Then
CCN database lookup is bypassed and not performed
R-GCX146-cbl-00630
Bypass CCN Status Validation
Validation Rules
📊 Business Logic Narrative
When the process 'Bypass CCN Status Validation' is invoked, and assuming that equipment is flagged as idler type, when the system processes equipment for ccn status validation, the desired outcome is that ccn status validation is bypassed and not performed.
💻 Technical Criteria
Given
Equipment is flagged as idler type
When
The system processes equipment for CCN status validation
Then
CCN status validation is bypassed and not performed
R-GCX146-cbl-00635
Include in Trip Sheet without CCN
Process Rules
📊 Business Logic Narrative
When the process 'Include in Trip Sheet without CCN' is invoked, and assuming that equipment type message has been generated for idler equipment, when the system creates trip sheet reports, the desired outcome is that idler equipment is included in the trip sheet without ccn data requirements.
💻 Technical Criteria
Given
Equipment type message has been generated for idler equipment
When
The system creates trip sheet reports
Then
Idler equipment is included in the trip sheet without CCN data requirements
R-GCX146-cbl-00636
Check Transit Status Code
Decision Rules
📊 Business Logic Narrative
When the process 'Check Transit Status Code' is invoked, and assuming that a ccn record has a current status of release or csa-dlv, when the transit status code is 'e' (export) or 'z' (export zone), the desired outcome is that the cargo status should be classified as 'export' for reporting purposes.
💻 Technical Criteria
Given
A CCN record has a current status of RELEASE or CSA-DLV
When
The transit status code is 'E' (Export) or 'Z' (Export Zone)
Then
The cargo status should be classified as 'EXPORT' for reporting purposes
R-GCX146-cbl-00637
Has S.A.R. Release?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Has S.A.R. Release?', assuming that a ccn record has a current status of release or csa-dlv and transit status is not 'e' or 'z', when the release-by field contains 's.a.r.' (special administrative release), the desired outcome is that the cargo status should be classified as 's.a.r.' for reporting purposes.
💻 Technical Criteria
EXCLUDING
A CCN record has a current status of RELEASE or CSA-DLV and transit status is not 'E' or 'Z'
When
The release-by field contains 'S.A.R.' (Special Administrative Release)
Then
The cargo status should be classified as 'S.A.R.' for reporting purposes
R-GCX146-cbl-00638
Set Status to 'RELEASE'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to 'RELEASE'', assuming that a ccn record has a current status of release or csa-dlv, when the transit status is not 'e' or 'z' and the release-by field does not contain 's.a.r.', the desired outcome is that the cargo status should be classified as 'release' for reporting purposes.
💻 Technical Criteria
EXCLUDING
A CCN record has a current status of RELEASE or CSA-DLV
When
The transit status is not 'E' or 'Z' and the release-by field does not contain 'S.A.R.'
Then
The cargo status should be classified as 'RELEASE' for reporting purposes
R-GCX146-cbl-00639
Increment Release Equipment Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Release Equipment Totals' is invoked, and assuming that equipment has a ccn status of release or csa-dlv, when processing equipment for verify operation totals, the desired outcome is that the total-release counter should be incremented by one.
💻 Technical Criteria
Given
Equipment has a CCN status of RELEASE or CSA-DLV
When
Processing equipment for VERIFY operation totals
Then
The TOTAL-RELEASE counter should be incremented by one
R-GCX146-cbl-00640
Check Transit Status Code
Process Rules
📊 Business Logic Narrative
When the process 'Check Transit Status Code' is invoked, and assuming that a ccn record exists with status information, when processing the transit status field from the ccn record, the desired outcome is that the transit status code should be evaluated to determine appropriate cargo classification.
💻 Technical Criteria
Given
A CCN record exists with status information
When
Processing the transit status field from the CCN record
Then
The transit status code should be evaluated to determine appropriate cargo classification
R-GCX146-cbl-00642
Check Current Status Value
Decision Rules
📊 Business Logic Narrative
When the process 'Check Current Status Value' is invoked, and assuming that a ccn record exists with a current status value, when the system evaluates the current status code, the desired outcome is that the system classifies the status as transit, return, export, s.a.r. release, or standard release based on the status code value.
💻 Technical Criteria
Given
A CCN record exists with a current status value
When
The system evaluates the current status code
Then
The system classifies the status as Transit, Return, Export, S.A.R. Release, or standard Release based on the status code value
R-GCX146-cbl-00643
Set Transit Status to 'TRANSIT'
Decision Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'TRANSIT'' is invoked, and assuming that a ccn record has current status equal to 't', when the system processes the transit status classification, the desired outcome is that the transit status is set to 'transit' for business reporting.
💻 Technical Criteria
Given
A CCN record has current status equal to 'T'
When
The system processes the transit status classification
Then
The transit status is set to 'TRANSIT' for business reporting
R-GCX146-cbl-00644
Set Transit Status to 'RETURN'
Decision Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'RETURN'' is invoked, and assuming that a ccn record has current status equal to 'r', when the system processes the transit status classification, the desired outcome is that the transit status is set to 'return' for business reporting.
💻 Technical Criteria
Given
A CCN record has current status equal to 'R'
When
The system processes the transit status classification
Then
The transit status is set to 'RETURN' for business reporting
R-GCX146-cbl-00645
Set Transit Status to 'EXPORT'
Decision Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'EXPORT'' is invoked, and assuming that a ccn record has release status 'release' or 'csa-dlv' and in-transit status equal to 'e' or 'z', when the system processes the transit status classification, the desired outcome is that the transit status is set to 'export' for business reporting.
💻 Technical Criteria
Given
A CCN record has release status 'RELEASE' or 'CSA-DLV' and in-transit status equal to 'E' or 'Z'
When
The system processes the transit status classification
Then
The transit status is set to 'EXPORT' for business reporting
R-GCX146-cbl-00646
Set Transit Status to 'S.A.R.'
Decision Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'S.A.R.'' is invoked, and assuming that a ccn record has release status 'release' or 'csa-dlv' and release-by field contains 's.a.r.', when the system processes the transit status classification, the desired outcome is that the transit status is set to 's.a.r.' for business reporting.
💻 Technical Criteria
Given
A CCN record has release status 'RELEASE' or 'CSA-DLV' and release-by field contains 'S.A.R.'
When
The system processes the transit status classification
Then
The transit status is set to 'S.A.R.' for business reporting
R-GCX146-cbl-00647
Set Transit Status to 'RELEASE'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Transit Status to 'RELEASE'', assuming that a ccn record has release status 'release' or 'csa-dlv' and does not meet export or s.a.r. criteria, when the system processes the transit status classification, the desired outcome is that the transit status is set to 'release' for business reporting.
💻 Technical Criteria
EXCLUDING
A CCN record has release status 'RELEASE' or 'CSA-DLV' and does not meet export or S.A.R. criteria
When
The system processes the transit status classification
Then
The transit status is set to 'RELEASE' for business reporting
R-GCX146-cbl-00648
Validate CCN Assignment Conflicts
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CCN Assignment Conflicts' is invoked, and assuming that a ccn is being processed for train assignment, when the system checks existing train assignments for the ccn, the desired outcome is that the system validates that the ccn is not already assigned to a different train.
💻 Technical Criteria
Given
A CCN is being processed for train assignment
When
The system checks existing train assignments for the CCN
Then
The system validates that the CCN is not already assigned to a different train
R-GCX146-cbl-00649
Generate Assignment Conflict Error
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Assignment Conflict Error' is invoked, and assuming that a ccn is found to be already assigned to a different train, when the system detects the assignment conflict, the desired outcome is that the system generates error 13 indicating the car is already on another train.
💻 Technical Criteria
Given
A CCN is found to be already assigned to a different train
When
The system detects the assignment conflict
Then
The system generates error 13 indicating the car is already on another train
R-GCX146-cbl-00660
Increment TOTAL-RELEASE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-RELEASE Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the equipment ccn status is 'release' or 'csa-dlv', the desired outcome is that the total-release counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The equipment CCN status is 'RELEASE' or 'CSA-DLV'
Then
The TOTAL-RELEASE counter should be incremented by 1
R-GCX146-cbl-00662
Increment TOTAL-HELD-CCRA Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-CCRA Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the equipment ccn status is 'hold' or 'agi-hold', the desired outcome is that the total-held-ccra counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The equipment CCN status is 'HOLD' or 'AGI-HOLD'
Then
The TOTAL-HELD-CCRA counter should be incremented by 1
R-GCX146-cbl-00663
Increment TOTAL-PROCEED Counter
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Increment TOTAL-PROCEED Counter', assuming that an equipment record is being processed for status totals, when the equipment ccn status is 'return' or the manifest from station is different from the manifest to station and the status is not 'error', 'reject', or 'deleted', the desired outcome is that the total-proceed counter should be incremented by 1.
💻 Technical Criteria
EXCLUDING
An equipment record is being processed for status totals
When
The equipment CCN status is 'RETURN' or the manifest from station is different from the manifest to station and the status is not 'ERROR', 'REJECT', or 'DELETED'
Then
The TOTAL-PROCEED counter should be incremented by 1
R-GCX146-cbl-00666
Update Status Report Fields
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Update Status Report Fields', assuming that an equipment record has been categorized by status, when the equipment has a valid ccn and is not a loaded or empty car without proper documentation, the desired outcome is that the status report should be populated with equipment id, manifest station names, and transit status where transit status shows 'transit' if in-transit status is 't'.
💻 Technical Criteria
EXCLUDING
An equipment record has been categorized by status
When
The equipment has a valid CCN and is not a loaded or empty car without proper documentation
Then
The status report should be populated with equipment ID, manifest station names, and transit status where transit status shows 'TRANSIT' if in-transit status is 'T'
R-GCX146-cbl-00725
Check CCN Transit Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check CCN Transit Status' is invoked, and assuming that a ccn record exists with transit status information, when the system checks the ccn transit status field, the desired outcome is that if transit status equals 't', the ccn is classified as in-transit cargo, otherwise it proceeds to assignment conflict validation.
💻 Technical Criteria
Given
A CCN record exists with transit status information
When
The system checks the CCN transit status field
Then
If transit status equals 'T', the CCN is classified as in-transit cargo, otherwise it proceeds to assignment conflict validation
R-GCX146-cbl-00726
CCN Already Assigned to Another Train?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Already Assigned to Another Train?' is invoked, and assuming that a ccn exists and needs to be assigned to a train, when the system checks if the ccn is already assigned to another train, the desired outcome is that if the ccn is already assigned to a different train, generate assignment conflict error, otherwise proceed with status evaluation.
💻 Technical Criteria
Given
A CCN exists and needs to be assigned to a train
When
The system checks if the CCN is already assigned to another train
Then
If the CCN is already assigned to a different train, generate assignment conflict error, otherwise proceed with status evaluation
R-GCX146-cbl-00727
Transit Code = 'E' or 'Z'?
Decision Rules
📊 Business Logic Narrative
When the process 'Transit Code = 'E' or 'Z'?' is invoked, and assuming that a ccn has status 'release' and contains transit code information, when the transit code is 'e' or 'z', the desired outcome is that set the display status to 'export' for reporting purposes.
💻 Technical Criteria
Given
A CCN has status 'RELEASE' and contains transit code information
When
The transit code is 'E' or 'Z'
Then
Set the display status to 'EXPORT' for reporting purposes
R-GCX146-cbl-00728
Transit Code = 'S.A.R.'?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Code = 'S.A.R.'?', assuming that a ccn has status 'release' and transit code is not 'e' or 'z', when the transit code equals 's.a.r.', the desired outcome is that set the display status to 's.a.r.' for reporting purposes.
💻 Technical Criteria
EXCLUDING
A CCN has status 'RELEASE' and transit code is not 'E' or 'Z'
When
The transit code equals 'S.A.R.'
Then
Set the display status to 'S.A.R.' for reporting purposes
R-GCX146-cbl-00729
Set Status to 'RELEASE'
Decision Rules
📊 Business Logic Narrative
When the process 'Set Status to 'RELEASE'' is invoked, and assuming that a ccn has status 'release' and transit code is neither 'e', 'z', nor 's.a.r.', when no special transit code conditions are met, the desired outcome is that set the display status to 'release' for reporting purposes.
💻 Technical Criteria
Given
A CCN has status 'RELEASE' and transit code is neither 'E', 'Z', nor 'S.A.R.'
When
No special transit code conditions are met
Then
Set the display status to 'RELEASE' for reporting purposes
R-GCX146-cbl-00730
Transit Status = 'R'?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Status = 'R'?', assuming that a ccn does not have 'release' status, when the transit status equals 'r', the desired outcome is that set the display status to 'return' for reporting purposes.
💻 Technical Criteria
EXCLUDING
A CCN does not have 'RELEASE' status
When
The transit status equals 'R'
Then
Set the display status to 'RETURN' for reporting purposes
R-GCX146-cbl-00731
Set Status to 'TRANSIT'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to 'TRANSIT'', assuming that a ccn does not have 'release' status and transit status is not 'r', when no other status classification rules apply, the desired outcome is that set the display status to 'transit' for reporting purposes.
💻 Technical Criteria
EXCLUDING
A CCN does not have 'RELEASE' status and transit status is not 'R'
When
No other status classification rules apply
Then
Set the display status to 'TRANSIT' for reporting purposes
R-GCX146-cbl-00732
CCN Usable for Train?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Usable for Train?' is invoked, and assuming that a ccn exists with equipment id and waybill information, when the system validates ccn usability by checking if equipment id matches and either waybill number matches or new bond created flag is 'y', the desired outcome is that if validation fails, mark ccn as unusable and report 'ccn found not usable' for verify operations, otherwise allow ccn usage.
💻 Technical Criteria
Given
A CCN exists with equipment ID and waybill information
When
The system validates CCN usability by checking if equipment ID matches and either waybill number matches or new bond created flag is 'Y'
Then
If validation fails, mark CCN as unusable and report 'CCN FOUND NOT USABLE' for VERIFY operations, otherwise allow CCN usage
R-GCX146-cbl-00733
Identify Cargo with Specific Routing Codes
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Cargo with Specific Routing Codes' is invoked, and assuming that a cargo item with a ccn (customs control number) exists in the system, when the ccn key starts with '6105' prefix, the desired outcome is that the cargo is flagged as requiring special manifest processing.
💻 Technical Criteria
Given
A cargo item with a CCN (Customs Control Number) exists in the system
When
The CCN key starts with '6105' prefix
Then
The cargo is flagged as requiring special manifest processing
R-GCX146-cbl-00737
Store CCN Key Information
Process Rules
📊 Business Logic Narrative
When the process 'Store CCN Key Information' is invoked, and assuming that a ccn exists for cargo requiring special manifest processing, when the special manifest transaction is being prepared, the desired outcome is that the ccn key information is stored for transaction processing.
💻 Technical Criteria
Given
A CCN exists for cargo requiring special manifest processing
When
The special manifest transaction is being prepared
Then
The CCN key information is stored for transaction processing
R-GCX146-cbl-00739
Build Special Manifest Input
Process Rules
📊 Business Logic Narrative
When the process 'Build Special Manifest Input' is invoked, and assuming that border information, ccn key data, and record type are available, when a special manifest transaction needs to be created, the desired outcome is that the system builds the complete input structure with all required manifest data.
💻 Technical Criteria
Given
Border information, CCN key data, and record type are available
When
A special manifest transaction needs to be created
Then
The system builds the complete input structure with all required manifest data
R-GCX146-cbl-00755
Set CCN Keys for Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Set CCN Keys for Manifest' is invoked, and assuming that equipment records require customs tracking numbers, when processing equipment for customs manifest transmission, the desired outcome is that the system assigns valid ccn keys to each equipment record for customs identification and tracking.
💻 Technical Criteria
Given
Equipment records require customs tracking numbers
When
Processing equipment for customs manifest transmission
Then
The system assigns valid CCN keys to each equipment record for customs identification and tracking
R-GCX146-cbl-00759
Build EDI Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Build EDI Equipment Record' is invoked, and assuming that equipment data has been processed and classified, when building individual edi equipment records, the desired outcome is that the system constructs complete edi records with equipment id, type, status, ccn, and all required customs fields in proper edi format.
💻 Technical Criteria
Given
Equipment data has been processed and classified
When
Building individual EDI equipment records
Then
The system constructs complete EDI records with equipment ID, type, status, CCN, and all required customs fields in proper EDI format
R-GCX146-cbl-00786
Extract Load Status from Waybill
Action Rules
📊 Business Logic Narrative
When the process 'Extract Load Status from Waybill' is invoked, and assuming that equipment record is being processed and waybill data has been retrieved, when the waybill contains load/empty status indicator in the waybill record, the desired outcome is that extract the load/empty status from waybill and assign it to the equipment record.
💻 Technical Criteria
Given
Equipment record is being processed and waybill data has been retrieved
When
The waybill contains load/empty status indicator in the waybill record
Then
Extract the load/empty status from waybill and assign it to the equipment record
R-GCX146-cbl-00787
Use Input Load/Empty Flag
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Use Input Load/Empty Flag', assuming that equipment record is being processed and waybill does not contain load status, when input specifications contain a load/empty flag indicator, the desired outcome is that use the input load/empty flag to assign status to the equipment.
💻 Technical Criteria
EXCLUDING
Equipment record is being processed and waybill does not contain load status
When
Input specifications contain a load/empty flag indicator
Then
Use the input load/empty flag to assign status to the equipment
R-GCX146-cbl-00788
Determine Load Status from Routing
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Load Status from Routing' is invoked, and assuming that equipment record has no explicit load/empty indicators from waybill or input, when equipment has both origin and destination information available, the desired outcome is that analyze the routing information to determine if equipment is loaded or empty based on cargo movement patterns.
💻 Technical Criteria
Given
Equipment record has no explicit load/empty indicators from waybill or input
When
Equipment has both origin and destination information available
Then
Analyze the routing information to determine if equipment is loaded or empty based on cargo movement patterns
R-GCX146-cbl-00795
Access CCN Database Record
Action Rules
📊 Business Logic Narrative
When the process 'Access CCN Database Record' is invoked, and assuming that a ccn key is provided for lookup, when the system attempts to access the ccn database record, the desired outcome is that the system retrieves the ccn record from the gcccrt database if it exists.
💻 Technical Criteria
Given
A CCN key is provided for lookup
When
The system attempts to access the CCN database record
Then
The system retrieves the CCN record from the GCCCRT database if it exists
R-GCX146-cbl-00796
CCN Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Record Found?' is invoked, and assuming that a ccn database lookup has been performed, when the system checks if the ccn record was found, the desired outcome is that the system proceeds with transit status processing if record exists, otherwise handles the not found condition.
💻 Technical Criteria
Given
A CCN database lookup has been performed
When
The system checks if the CCN record was found
Then
The system proceeds with transit status processing if record exists, otherwise handles the not found condition
R-GCX146-cbl-00797
Read Current Transit Status
Action Rules
📊 Business Logic Narrative
When the process 'Read Current Transit Status' is invoked, and assuming that a valid ccn record exists in the database, when the system reads the current transit status field, the desired outcome is that the system retrieves the transit status code for further processing.
💻 Technical Criteria
Given
A valid CCN record exists in the database
When
The system reads the current transit status field
Then
The system retrieves the transit status code for further processing
R-GCX146-cbl-00798
Check Transit Status Code
Decision Rules
📊 Business Logic Narrative
When the process 'Check Transit Status Code' is invoked, and assuming that a transit status code has been retrieved from the ccn record, when the system evaluates the transit status code, the desired outcome is that the system determines the appropriate status classification based on the code value.
💻 Technical Criteria
Given
A transit status code has been retrieved from the CCN record
When
The system evaluates the transit status code
Then
The system determines the appropriate status classification based on the code value
R-GCX146-cbl-00810
Update CCN Transit Status
Action Rules
📊 Business Logic Narrative
When the process 'Update CCN Transit Status' is invoked, and assuming that a transit status has been determined and assigned, when the system updates the ccn transit status, the desired outcome is that the ccn record is updated with the new transit status in the database.
💻 Technical Criteria
Given
A transit status has been determined and assigned
When
The system updates the CCN transit status
Then
The CCN record is updated with the new transit status in the database
R-GCX146-cbl-00811
Track Cargo Movement
Action Rules
📊 Business Logic Narrative
When the process 'Track Cargo Movement' is invoked, and assuming that the ccn transit status has been updated, when the system processes cargo movement tracking, the desired outcome is that the system records the cargo movement information for tracking purposes.
💻 Technical Criteria
Given
The CCN transit status has been updated
When
The system processes cargo movement tracking
Then
The system records the cargo movement information for tracking purposes
R-GCX146-cbl-00812
Handle CCN Not Found
Action Rules
📊 Business Logic Narrative
When the process 'Handle CCN Not Found' is invoked, and assuming that a ccn lookup has been performed, when no ccn record is found in the database, the desired outcome is that the system handles the not found condition and completes processing.
💻 Technical Criteria
Given
A CCN lookup has been performed
When
No CCN record is found in the database
Then
The system handles the not found condition and completes processing
R-GCX146-cbl-01374
Add CCN Information
Process Rules
📊 Business Logic Narrative
When the process 'Add CCN Information' is invoked, and assuming that load/empty status has been added to equipment, when ccn information exists for the equipment, the desired outcome is that ccn numbers and associated customs status information are added to the equipment details.
💻 Technical Criteria
Given
Load/empty status has been added to equipment
When
CCN information exists for the equipment
Then
CCN numbers and associated customs status information are added to the equipment details
R-GCX146-cbl-01375
Format Equipment Type Messages
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Type Messages' is invoked, and assuming that ccn information has been processed for equipment, when equipment type messages need to be formatted, the desired outcome is that car type descriptions and related equipment type messages are formatted and added to the message.
💻 Technical Criteria
Given
CCN information has been processed for equipment
When
Equipment type messages need to be formatted
Then
Car type descriptions and related equipment type messages are formatted and added to the message
R-GCX146-cbl-00853
Format Equipment ID for Search
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment ID for Search' is invoked, and assuming that an equipment id is provided for waybill lookup, when the system prepares to search for waybill information, the desired outcome is that the equipment id is formatted by removing spaces and standardized to proper search format.
💻 Technical Criteria
Given
An equipment ID is provided for waybill lookup
When
The system prepares to search for waybill information
Then
The equipment ID is formatted by removing spaces and standardized to proper search format
R-GCX146-cbl-00854
Search Primary Waybill Database FWIIROOT
Action Rules
📊 Business Logic Narrative
When the process 'Search Primary Waybill Database FWIIROOT' is invoked, and assuming that a formatted equipment id is available for search, when the system searches the primary waybill database fwiiroot, the desired outcome is that the system retrieves waybill record if equipment id exists in the database.
💻 Technical Criteria
Given
A formatted equipment ID is available for search
When
The system searches the primary waybill database FWIIROOT
Then
The system retrieves waybill record if equipment ID exists in the database
R-GCX146-cbl-00855
Waybill Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Waybill Record Found?' is invoked, and assuming that a search has been performed in the primary waybill database, when the system evaluates the search results, the desired outcome is that the system determines if a waybill record was found and proceeds to extract information or searches alternative sources.
💻 Technical Criteria
Given
A search has been performed in the primary waybill database
When
The system evaluates the search results
Then
The system determines if a waybill record was found and proceeds to extract information or searches alternative sources
R-GCX146-cbl-00856
Search Enhanced Waybill SHIPROOT
Action Rules
📊 Business Logic Narrative
When the process 'Search Enhanced Waybill SHIPROOT' is invoked, and assuming that no waybill record was found in the primary database fwiiroot, when the system performs a fallback search, the desired outcome is that the system searches the enhanced waybill database shiproot using multi-criteria search parameters.
💻 Technical Criteria
Given
No waybill record was found in the primary database FWIIROOT
When
The system performs a fallback search
Then
The system searches the enhanced waybill database SHIPROOT using multi-criteria search parameters
R-GCX146-cbl-00857
Enhanced Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Enhanced Record Found?' is invoked, and assuming that a search has been performed in the enhanced waybill database shiproot, when the system evaluates the enhanced database search results, the desired outcome is that the system determines if an enhanced waybill record was found and proceeds accordingly.
💻 Technical Criteria
Given
A search has been performed in the enhanced waybill database SHIPROOT
When
The system evaluates the enhanced database search results
Then
The system determines if an enhanced waybill record was found and proceeds accordingly
R-GCX146-cbl-00858
Search Inquiry Database FW-IQ
Action Rules
📊 Business Logic Narrative
When the process 'Search Inquiry Database FW-IQ' is invoked, and assuming that no waybill records were found in both primary fwiiroot and enhanced shiproot databases, when the system performs the final fallback search, the desired outcome is that the system searches the inquiry database fw-iq as the last resort for waybill information.
💻 Technical Criteria
Given
No waybill records were found in both primary FWIIROOT and enhanced SHIPROOT databases
When
The system performs the final fallback search
Then
The system searches the inquiry database FW-IQ as the last resort for waybill information
R-GCX146-cbl-00859
Inquiry Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Inquiry Record Found?' is invoked, and assuming that a search has been performed in the inquiry database fw-iq, when the system evaluates the inquiry database search results, the desired outcome is that the system determines if any inquiry records were found or if waybill lookup has failed completely.
💻 Technical Criteria
Given
A search has been performed in the inquiry database FW-IQ
When
The system evaluates the inquiry database search results
Then
The system determines if any inquiry records were found or if waybill lookup has failed completely
R-GCX146-cbl-00860
Set Waybill Not Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Waybill Not Found Flag' is invoked, and assuming that all database searches (primary, enhanced, and inquiry) have been exhausted without finding waybill records, when the system completes the comprehensive waybill search process, the desired outcome is that the system sets a waybill not found flag to indicate unsuccessful lookup.
💻 Technical Criteria
Given
All database searches (primary, enhanced, and inquiry) have been exhausted without finding waybill records
When
The system completes the comprehensive waybill search process
Then
The system sets a waybill not found flag to indicate unsuccessful lookup
R-GCX146-cbl-00861
Extract Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Information' is invoked, and assuming that a waybill record has been found in any of the searched databases, when the system processes the located waybill record, the desired outcome is that the system extracts all relevant waybill information including shipment details and equipment data.
💻 Technical Criteria
Given
A waybill record has been found in any of the searched databases
When
The system processes the located waybill record
Then
The system extracts all relevant waybill information including shipment details and equipment data
R-GCX146-cbl-00862
Validate Waybill Data Quality
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Waybill Data Quality' is invoked, and assuming that waybill information has been extracted from a database record, when the system validates the extracted data, the desired outcome is that the system verifies data completeness, format correctness, and business rule compliance.
💻 Technical Criteria
Given
Waybill information has been extracted from a database record
When
The system validates the extracted data
Then
The system verifies data completeness, format correctness, and business rule compliance
R-GCX146-cbl-00863
Extract Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Details' is invoked, and assuming that waybill data has been validated for quality, when the system processes equipment-specific information, the desired outcome is that the system extracts equipment details including car type, status, and identification information.
💻 Technical Criteria
Given
Waybill data has been validated for quality
When
The system processes equipment-specific information
Then
The system extracts equipment details including car type, status, and identification information
R-GCX146-cbl-00865
Set Waybill Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Waybill Found Flag' is invoked, and assuming that all waybill and shipment information has been successfully extracted, when the system completes the waybill lookup process, the desired outcome is that the system sets a waybill found flag to indicate successful completion of the lookup process.
💻 Technical Criteria
Given
All waybill and shipment information has been successfully extracted
When
The system completes the waybill lookup process
Then
The system sets a waybill found flag to indicate successful completion of the lookup process
R-GCX146-cbl-00866
Return Waybill Results
Process Rules
📊 Business Logic Narrative
When the process 'Return Waybill Results' is invoked, and assuming that the waybill lookup process has been completed with either success or failure, when the system finalizes the lookup operation, the desired outcome is that the system returns the waybill lookup results including extracted data if found or failure indication if not found.
💻 Technical Criteria
Given
The waybill lookup process has been completed with either success or failure
When
The system finalizes the lookup operation
Then
The system returns the waybill lookup results including extracted data if found or failure indication if not found
R-GCX146-cbl-00874
Extract Container ID from XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from XREF' is invoked, and assuming that container id is available in t/c xref records, when the system processes container identification requirements, the desired outcome is that container id is extracted from xref records for subsequent waybill information retrieval.
💻 Technical Criteria
Given
Container ID is available in T/C XREF records
When
The system processes container identification requirements
Then
Container ID is extracted from XREF records for subsequent waybill information retrieval
R-GCX146-cbl-00875
Retrieve Associated Waybill Information
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Associated Waybill Information' is invoked, and assuming that container id has been extracted or container information is available, when the system needs waybill data for container processing, the desired outcome is that associated waybill information is retrieved for the container.
💻 Technical Criteria
Given
Container ID has been extracted or container information is available
When
The system needs waybill data for container processing
Then
Associated waybill information is retrieved for the container
R-GCX146-cbl-00876
Waybill Data Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Waybill Data Found?' is invoked, and assuming that waybill information retrieval has been attempted for the container, when the system checks for waybill data availability, the desired outcome is that if waybill data is found, process container waybill data, otherwise report container processing error.
💻 Technical Criteria
Given
Waybill information retrieval has been attempted for the container
When
The system checks for waybill data availability
Then
If waybill data is found, process container waybill data, otherwise report container processing error
R-GCX146-cbl-00877
Process Container Waybill Data
Process Rules
📊 Business Logic Narrative
When the process 'Process Container Waybill Data' is invoked, and assuming that waybill data has been found for the container, when the system processes container waybill information, the desired outcome is that container waybill data is processed according to business requirements.
💻 Technical Criteria
Given
Waybill data has been found for the container
When
The system processes container waybill information
Then
Container waybill data is processed according to business requirements
R-GCX146-cbl-00878
Set Container Processing Complete
Process Rules
📊 Business Logic Narrative
When the process 'Set Container Processing Complete' is invoked, and assuming that container waybill data has been successfully processed, when the system completes container processing operations, the desired outcome is that container processing status is set to complete.
💻 Technical Criteria
Given
Container waybill data has been successfully processed
When
The system completes container processing operations
Then
Container processing status is set to complete
R-GCX146-cbl-00879
Container Processing Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Container Processing Error', assuming that container id is not available from xref records or waybill data is not found for the container, when the system encounters container processing failures, the desired outcome is that container processing error is reported and processing terminates.
💻 Technical Criteria
EXCLUDING
Container ID is not available from XREF records OR waybill data is not found for the container
When
The system encounters container processing failures
Then
Container processing error is reported and processing terminates
R-GCX146-cbl-00881
Retrieve Current Equipment Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Current Equipment Record' is invoked, and assuming that an equipment sequence counter is set, when the system needs to access equipment data, the desired outcome is that the system retrieves the equipment record from fwiiroot database using fwcmsget call with the current sequence number.
💻 Technical Criteria
Given
An equipment sequence counter is set
When
The system needs to access equipment data
Then
The system retrieves the equipment record from FWIIROOT database using FWCMSGET call with the current sequence number
R-GCX146-cbl-00885
Call FWCMSGET for Next Record
Action Rules
📊 Business Logic Narrative
When the process 'Call FWCMSGET for Next Record' is invoked, and assuming that the equipment sequence counter has been incremented, when the system needs to access the next equipment record, the desired outcome is that fwcmsget is called with the new sequence number to retrieve the next equipment record from fwiiroot.
💻 Technical Criteria
Given
The equipment sequence counter has been incremented
When
The system needs to access the next equipment record
Then
FWCMSGET is called with the new sequence number to retrieve the next equipment record from FWIIROOT
R-GCX146-cbl-00895
Set Load/Empty Status
Validation Rules
📊 Business Logic Narrative
When the process 'Set Load/Empty Status' is invoked, and assuming that equipment record and associated waybill information, when determining equipment load status, the desired outcome is that load/empty flags are set correctly and validated against waybill data.
💻 Technical Criteria
Given
Equipment record and associated waybill information
When
Determining equipment load status
Then
Load/empty flags are set correctly and validated against waybill data
R-GCX146-cbl-00901
Bunch Bill Present?
Decision Rules
📊 Business Logic Narrative
When the process 'Bunch Bill Present?' is invoked, and assuming that waybill information with bunch bill indicators, when checking for bunch bill configuration, the desired outcome is that additional car retrieval is initiated if bunch bill is present, otherwise processing continues with single car.
💻 Technical Criteria
Given
Waybill information with bunch bill indicators
When
Checking for bunch bill configuration
Then
Additional car retrieval is initiated if bunch bill is present, otherwise processing continues with single car
R-GCX146-cbl-00902
Retrieve Additional Cars
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Additional Cars' is invoked, and assuming that bunch bill waybill with multiple associated cars, when retrieving additional cars from bunch bill, the desired outcome is that additional cars are retrieved using fwcmsget with sequential retrieval maintaining waybill association.
💻 Technical Criteria
Given
Bunch bill waybill with multiple associated cars
When
Retrieving additional cars from bunch bill
Then
Additional cars are retrieved using FWCMSGET with sequential retrieval maintaining waybill association
R-GCX146-cbl-00903
Format Sequential Car IDs
Process Rules
📊 Business Logic Narrative
When the process 'Format Sequential Car IDs' is invoked, and assuming that multiple cars from bunch bill waybill, when formatting sequential car identifiers, the desired outcome is that car sequence is formatted maintaining waybill association with proper sequential numbering.
💻 Technical Criteria
Given
Multiple cars from bunch bill waybill
When
Formatting sequential car identifiers
Then
Car sequence is formatted maintaining waybill association with proper sequential numbering
R-GCX146-cbl-00907
Search CCN by Equipment ID
Action Rules
📊 Business Logic Narrative
When the process 'Search CCN by Equipment ID' is invoked, and assuming that an equipment id is provided for ccn lookup, when the system searches the ccn database using the equipment id, the desired outcome is that the system retrieves any existing ccn records associated with that equipment.
💻 Technical Criteria
Given
An equipment ID is provided for CCN lookup
When
The system searches the CCN database using the equipment ID
Then
The system retrieves any existing CCN records associated with that equipment
R-GCX146-cbl-00908
CCN Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Record Found?' is invoked, and assuming that a ccn database search has been performed for an equipment id, when the system evaluates the search results, the desired outcome is that the system determines if a ccn record was found and routes processing accordingly.
💻 Technical Criteria
Given
A CCN database search has been performed for an equipment ID
When
The system evaluates the search results
Then
The system determines if a CCN record was found and routes processing accordingly
R-GCX146-cbl-00909
Retrieve CCN Details
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve CCN Details' is invoked, and assuming that a ccn record exists in the database for the equipment, when the system processes the found ccn record, the desired outcome is that the system extracts all relevant ccn details including status, waybill information, and customs control data.
💻 Technical Criteria
Given
A CCN record exists in the database for the equipment
When
The system processes the found CCN record
Then
The system extracts all relevant CCN details including status, waybill information, and customs control data
R-GCX146-cbl-00910
Check CCN Usability
Validation Rules
📊 Business Logic Narrative
When the process 'Check CCN Usability' is invoked, and assuming that a ccn record has been retrieved with its details, when the system validates ccn usability against current transaction requirements, the desired outcome is that the system determines if the ccn is usable based on equipment id matching and waybill consistency.
💻 Technical Criteria
Given
A CCN record has been retrieved with its details
When
The system validates CCN usability against current transaction requirements
Then
The system determines if the CCN is usable based on equipment ID matching and waybill consistency
R-GCX146-cbl-00911
CCN Usable?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Usable?' is invoked, and assuming that ccn usability assessment has been completed, when the system evaluates the usability results, the desired outcome is that the system determines if the ccn is usable and routes to appropriate processing path.
💻 Technical Criteria
Given
CCN usability assessment has been completed
When
The system evaluates the usability results
Then
The system determines if the CCN is usable and routes to appropriate processing path
R-GCX146-cbl-00912
Validate CCN Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CCN Status' is invoked, and assuming that a usable ccn record has been identified, when the system validates the current ccn status, the desired outcome is that the system confirms the ccn status is valid for customs operations (sent, return, manual, release, ack, or csa-dlv).
💻 Technical Criteria
Given
A usable CCN record has been identified
When
The system validates the current CCN status
Then
The system confirms the CCN status is valid for customs operations (SENT, RETURN, MANUAL, RELEASE, ACK, or CSA-DLV)
R-GCX146-cbl-00913
Check Bond Creation Flag
Validation Rules
📊 Business Logic Narrative
When the process 'Check Bond Creation Flag' is invoked, and assuming that ccn status validation has been completed, when the system examines the bond creation indicator, the desired outcome is that the system determines if a new bond has been created (y flag) for the ccn.
💻 Technical Criteria
Given
CCN status validation has been completed
When
The system examines the bond creation indicator
Then
The system determines if a new bond has been created (Y flag) for the CCN
R-GCX146-cbl-00915
Mark CCN as Unusable
Process Rules
📊 Business Logic Narrative
When the process 'Mark CCN as Unusable' is invoked, and assuming that a ccn has failed usability validation or bond creation requirements, when the system processes the unusable ccn, the desired outcome is that the system marks the ccn as unusable and reports 'ccn found not usable' for verify operations.
💻 Technical Criteria
Given
A CCN has failed usability validation or bond creation requirements
When
The system processes the unusable CCN
Then
The system marks the CCN as unusable and reports 'CCN FOUND NOT USABLE' for verify operations
R-GCX146-cbl-00916
Set CCN Status Values
Process Rules
📊 Business Logic Narrative
When the process 'Set CCN Status Values' is invoked, and assuming that a usable ccn with valid bond creation status has been identified, when the system processes ccn status assignment, the desired outcome is that the system sets appropriate ccn status values for customs processing.
💻 Technical Criteria
Given
A usable CCN with valid bond creation status has been identified
When
The system processes CCN status assignment
Then
The system sets appropriate CCN status values for customs processing
R-GCX146-cbl-00917
Assign Status Based on Transit
Decision Rules
📊 Business Logic Narrative
When the process 'Assign Status Based on Transit' is invoked, and assuming that ccn status values have been set, when the system evaluates transit status and release conditions, the desired outcome is that the system assigns the final status based on transit state (e/z for export, s.a.r. for special release, t for transit, r for return).
💻 Technical Criteria
Given
CCN status values have been set
When
The system evaluates transit status and release conditions
Then
The system assigns the final status based on transit state (E/Z for export, S.A.R. for special release, T for transit, R for return)
R-GCX146-cbl-00918
Transit Status?
Decision Rules
📊 Business Logic Narrative
When the process 'Transit Status?' is invoked, and assuming that ccn is ready for status assignment based on transit conditions, when the system evaluates the current transit status code, the desired outcome is that the system determines the appropriate status path based on transit conditions (e/z, s.a.r., t, r, or other).
💻 Technical Criteria
Given
CCN is ready for status assignment based on transit conditions
When
The system evaluates the current transit status code
Then
The system determines the appropriate status path based on transit conditions (E/Z, S.A.R., T, R, or other)
R-GCX146-cbl-00919
Set Status: EXPORT
Process Rules
📊 Business Logic Narrative
When the process 'Set Status: EXPORT' is invoked, and assuming that ccn has release status and transit status is e (export) or z (export zone), when the system processes status assignment, the desired outcome is that the system sets the ccn status to 'export'.
💻 Technical Criteria
Given
CCN has RELEASE status and transit status is E (export) or Z (export zone)
When
The system processes status assignment
Then
The system sets the CCN status to 'EXPORT'
R-GCX146-cbl-00920
Set Status: S.A.R.
Process Rules
📊 Business Logic Narrative
When the process 'Set Status: S.A.R.' is invoked, and assuming that ccn has release status and is released by 's.a.r.' authority, when the system processes status assignment, the desired outcome is that the system sets the ccn status to 's.a.r.'.
💻 Technical Criteria
Given
CCN has RELEASE status and is released by 'S.A.R.' authority
When
The system processes status assignment
Then
The system sets the CCN status to 'S.A.R.'
R-GCX146-cbl-00921
Set Status: RELEASE
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status: RELEASE', assuming that ccn has release status but does not meet export or s.a.r. conditions, when the system processes status assignment, the desired outcome is that the system sets the ccn status to 'release'.
💻 Technical Criteria
EXCLUDING
CCN has RELEASE status but does not meet export or S.A.R. conditions
When
The system processes status assignment
Then
The system sets the CCN status to 'RELEASE'
R-GCX146-cbl-00922
Set Status: TRANSIT
Process Rules
📊 Business Logic Narrative
When the process 'Set Status: TRANSIT' is invoked, and assuming that ccn has in-transit status code 't', when the system processes status assignment, the desired outcome is that the system sets the ccn status to 'transit'.
💻 Technical Criteria
Given
CCN has in-transit status code 'T'
When
The system processes status assignment
Then
The system sets the CCN status to 'TRANSIT'
R-GCX146-cbl-00923
Set Status: RETURN
Process Rules
📊 Business Logic Narrative
When the process 'Set Status: RETURN' is invoked, and assuming that ccn has in-transit status code 'r', when the system processes status assignment, the desired outcome is that the system sets the ccn status to 'return'.
💻 Technical Criteria
Given
CCN has in-transit status code 'R'
When
The system processes status assignment
Then
The system sets the CCN status to 'RETURN'
R-GCX146-cbl-00924
Create Return CCN
Process Rules
📊 Business Logic Narrative
When the process 'Create Return CCN' is invoked, and assuming that a status has been assigned to the ccn requiring return processing, when the system processes return ccn creation, the desired outcome is that the system creates a new ccn record with return status and populates shipper, consignee, and station data.
💻 Technical Criteria
Given
A status has been assigned to the CCN requiring return processing
When
The system processes return CCN creation
Then
The system creates a new CCN record with return status and populates shipper, consignee, and station data
R-GCX146-cbl-00925
Build CCN with 6105E Prefix
Computation Rules
📊 Business Logic Narrative
When the process 'Build CCN with 6105E Prefix' is invoked, and assuming that a return ccn needs to be created, when the system builds the ccn key, the desired outcome is that the system constructs ccn key with format: type(6) + carrier(105) + e + equipment_id + waybill_date + sequence.
💻 Technical Criteria
Given
A return CCN needs to be created
When
The system builds the CCN key
Then
The system constructs CCN key with format: type(6) + carrier(105) + E + equipment_id + waybill_date + sequence
R-GCX146-cbl-00926
Set Return Status
Process Rules
📊 Business Logic Narrative
When the process 'Set Return Status' is invoked, and assuming that a ccn key has been built with 6105e prefix, when the system sets the ccn status, the desired outcome is that the system sets the ccn status to 'return' and application type to '33' for canadian customs.
💻 Technical Criteria
Given
A CCN key has been built with 6105E prefix
When
The system sets the CCN status
Then
The system sets the CCN status to 'RETURN' and application type to '33' for Canadian customs
R-GCX146-cbl-00927
Insert New CCN Record
Action Rules
📊 Business Logic Narrative
When the process 'Insert New CCN Record' is invoked, and assuming that a new ccn record has been created with return status, when the system processes the database insertion, the desired outcome is that the system inserts the new ccn record into the gcccrt database.
💻 Technical Criteria
Given
A new CCN record has been created with return status
When
The system processes the database insertion
Then
The system inserts the new CCN record into the GCCCRT database
R-GCX146-cbl-00928
Update CCN Database
Action Rules
📊 Business Logic Narrative
When the process 'Update CCN Database' is invoked, and assuming that ccn processing has been completed with status assignments, when the system performs database updates, the desired outcome is that the system updates the ccn database with current status, train information, and transaction details.
💻 Technical Criteria
Given
CCN processing has been completed with status assignments
When
The system performs database updates
Then
The system updates the CCN database with current status, train information, and transaction details
R-GCX146-cbl-00929
CCN Operations Complete
Process Rules
📊 Business Logic Narrative
When the process 'CCN Operations Complete' is invoked, and assuming that all ccn database operations have been performed, when the system finalizes ccn processing, the desired outcome is that the system confirms successful completion of all ccn operations.
💻 Technical Criteria
Given
All CCN database operations have been performed
When
The system finalizes CCN processing
Then
The system confirms successful completion of all CCN operations
R-GCX146-cbl-00930
CCN Not Found/Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'CCN Not Found/Error', assuming that ccn record is not found or ccn is marked as unusable, when the system processes the error condition, the desired outcome is that the system handles the ccn not found condition and routes to appropriate error processing.
💻 Technical Criteria
EXCLUDING
CCN record is not found or CCN is marked as unusable
When
The system processes the error condition
Then
The system handles the CCN not found condition and routes to appropriate error processing
R-GCX146-cbl-00951
Identify Single Waybill with Multiple Cars
Definitional Rules
📊 Business Logic Narrative
When the process 'Identify Single Waybill with Multiple Cars' is invoked, and assuming that a waybill record exists in the system, when the waybill contains multiple car equipment records associated with it, the desired outcome is that the system identifies this as a bunch bill and prepares for sequential car processing.
💻 Technical Criteria
Given
A waybill record exists in the system
When
The waybill contains multiple car equipment records associated with it
Then
The system identifies this as a bunch bill and prepares for sequential car processing
R-GCX146-cbl-00956
More Cars Under This Waybill?
Decision Rules
📊 Business Logic Narrative
When the process 'More Cars Under This Waybill?' is invoked, and assuming that a car record has been processed within a bunch bill, when the system needs to determine if more cars exist under the same waybill, the desired outcome is that the system checks if additional car records remain for processing under this waybill.
💻 Technical Criteria
Given
A car record has been processed within a bunch bill
When
The system needs to determine if more cars exist under the same waybill
Then
The system checks if additional car records remain for processing under this waybill
R-GCX146-cbl-00958
Move to Next Car in Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Move to Next Car in Sequence' is invoked, and assuming that a car has been processed within a bunch bill, when more cars remain to be processed under the same waybill, the desired outcome is that the system moves to the next car in the processing sequence.
💻 Technical Criteria
Given
A car has been processed within a bunch bill
When
More cars remain to be processed under the same waybill
Then
The system moves to the next car in the processing sequence
R-GCX146-cbl-00959
Complete Bunch Bill Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Bunch Bill Processing' is invoked, and assuming that all cars under a bunch bill waybill have been processed, when no more cars remain for processing under the current waybill, the desired outcome is that the system completes the bunch bill processing and prepares to return to main processing.
💻 Technical Criteria
Given
All cars under a bunch bill waybill have been processed
When
No more cars remain for processing under the current waybill
Then
The system completes the bunch bill processing and prepares to return to main processing
R-GCX146-cbl-00961
Initialize Bunch Bill Processing
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Bunch Bill Processing' is invoked, and assuming that a waybill contains multiple cars in a bunch bill arrangement, when the system begins processing additional car sequences, the desired outcome is that the bunch bill processing parameters are initialized and ready for car sequence processing.
💻 Technical Criteria
Given
A waybill contains multiple cars in a bunch bill arrangement
When
The system begins processing additional car sequences
Then
The bunch bill processing parameters are initialized and ready for car sequence processing
R-GCX146-cbl-00963
Use FWCMSGET to Get Next Equipment Record
Action Rules
📊 Business Logic Narrative
When the process 'Use FWCMSGET to Get Next Equipment Record' is invoked, and assuming that a bunch bill contains multiple equipment records, when the system processes each car in the sequence, the desired outcome is that the fwcmsget function retrieves the next equipment record from the shiproot waybill data.
💻 Technical Criteria
Given
A bunch bill contains multiple equipment records
When
The system processes each car in the sequence
Then
The FWCMSGET function retrieves the next equipment record from the SHIPROOT waybill data
R-GCX146-cbl-00964
Equipment Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment Record Found?' is invoked, and assuming that the system attempts to retrieve an equipment record from waybill data, when the fwcmsget function is executed, the desired outcome is that the system validates whether an equipment record was found and continues processing if found, or completes processing if no more records exist.
💻 Technical Criteria
Given
The system attempts to retrieve an equipment record from waybill data
When
The FWCMSGET function is executed
Then
The system validates whether an equipment record was found and continues processing if found, or completes processing if no more records exist
R-GCX146-cbl-00965
Extract Car Identification Data
Process Rules
📊 Business Logic Narrative
When the process 'Extract Car Identification Data' is invoked, and assuming that an equipment record has been successfully retrieved from waybill data, when the system processes the equipment record, the desired outcome is that car identification data is extracted from the equipment record for validation and processing.
💻 Technical Criteria
Given
An equipment record has been successfully retrieved from waybill data
When
The system processes the equipment record
Then
Car identification data is extracted from the equipment record for validation and processing
R-GCX146-cbl-00987
Segment Message for Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Segment Message for Transmission' is invoked, and assuming that equipment status information has been compiled into trip sheet format, when the message exceeds transmission system limits, the desired outcome is that the message is segmented into multiple parts with proper continuation headers and sequence numbering to ensure complete delivery.
💻 Technical Criteria
Given
Equipment status information has been compiled into trip sheet format
When
The message exceeds transmission system limits
Then
The message is segmented into multiple parts with proper continuation headers and sequence numbering to ensure complete delivery
R-GCX146-cbl-01023
Special Processing Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Special Processing Required?' is invoked, and assuming that equipment has been assigned type and status messages, when the system evaluates special processing requirements, the desired outcome is that the system determines if equipment needs bunch bill, flat car container, return ccn, or standard processing.
💻 Technical Criteria
Given
Equipment has been assigned type and status messages
When
The system evaluates special processing requirements
Then
The system determines if equipment needs Bunch Bill, Flat Car Container, Return CCN, or standard processing
R-GCX146-cbl-01026
Assign Return CCN Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Return CCN Message' is invoked, and assuming that equipment requires return ccn special processing, when the system processes the equipment for return ccn message assignment, the desired outcome is that the system assigns the appropriate return ccn message format.
💻 Technical Criteria
Given
Equipment requires return CCN special processing
When
The system processes the equipment for return CCN message assignment
Then
The system assigns the appropriate return CCN message format
R-GCX146-cbl-01029
Initialize Bunch Bill Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Bunch Bill Sequence' is invoked, and assuming that a waybill record exists in the system, when the system begins bunch bill processing, the desired outcome is that the bunch bill sequence counter is set to 1 and processing flags are initialized.
💻 Technical Criteria
Given
A waybill record exists in the system
When
The system begins bunch bill processing
Then
The bunch bill sequence counter is set to 1 and processing flags are initialized
R-GCX146-cbl-01030
Retrieve Primary Waybill Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Primary Waybill Record' is invoked, and assuming that a waybill number is provided for processing, when the system attempts to retrieve the waybill record, the desired outcome is that the primary waybill record is retrieved from fwiiroot database.
💻 Technical Criteria
Given
A waybill number is provided for processing
When
The system attempts to retrieve the waybill record
Then
The primary waybill record is retrieved from FWIIROOT database
R-GCX146-cbl-01031
Waybill Has Multiple Cars?
Decision Rules
📊 Business Logic Narrative
When the process 'Waybill Has Multiple Cars?' is invoked, and assuming that a waybill record has been retrieved, when the system examines the waybill structure, the desired outcome is that if the waybill contains multiple cars, sequential processing is initiated, otherwise processing ends.
💻 Technical Criteria
Given
A waybill record has been retrieved
When
The system examines the waybill structure
Then
If the waybill contains multiple cars, sequential processing is initiated, otherwise processing ends
R-GCX146-cbl-01034
Validate Equipment ID
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID' is invoked, and assuming that an equipment id has been extracted from the waybill, when the system validates the equipment id, the desired outcome is that the equipment id is verified against shiproot equipment records for existence and format compliance.
💻 Technical Criteria
Given
An equipment ID has been extracted from the waybill
When
The system validates the equipment ID
Then
The equipment ID is verified against SHIPROOT equipment records for existence and format compliance
R-GCX146-cbl-01046
Format Equipment Type Messages
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Type Messages' is invoked, and assuming that an equipment record needs to be formatted for transmission, when the system processes the equipment record, the desired outcome is that equipment details are formatted according to us customs requirements including car type, waybill information, and cargo details.
💻 Technical Criteria
Given
An equipment record needs to be formatted for transmission
When
The system processes the equipment record
Then
Equipment details are formatted according to US customs requirements including car type, waybill information, and cargo details
R-GCX146-cbl-01049
Format UNIT Equipment Message
Process Rules
📊 Business Logic Narrative
When the process 'Format UNIT Equipment Message' is invoked, and assuming that an equipment record classified as unit type (l, p, d, u car types), when the system formats the equipment message, the desired outcome is that unit equipment is formatted with complete details including car id, waybill number, shipper, consignee, origin, destination, and cargo description.
💻 Technical Criteria
Given
An equipment record classified as UNIT type (L, P, D, U car types)
When
The system formats the equipment message
Then
UNIT equipment is formatted with complete details including car ID, waybill number, shipper, consignee, origin, destination, and cargo description
R-GCX146-cbl-01064
Check Transit Status = 'D' for Delivered?
Decision Rules
📊 Business Logic Narrative
When the process 'Check Transit Status = 'D' for Delivered?' is invoked, and assuming that a ccn record exists with transit status information, when the system checks the transit status field, the desired outcome is that if transit status equals 'd' (delivered), the cargo is identified as arrived, otherwise continue processing next equipment.
💻 Technical Criteria
Given
A CCN record exists with transit status information
When
The system checks the transit status field
Then
If transit status equals 'D' (Delivered), the cargo is identified as arrived, otherwise continue processing next equipment
R-GCX146-cbl-01066
Update Cargo Status to Arrived
Action Rules
📊 Business Logic Narrative
When the process 'Update Cargo Status to Arrived' is invoked, and assuming that cargo has been identified as arrived at final destination, when the system processes the arrival confirmation, the desired outcome is that the cargo status is updated to 'arrived' in the ccn database.
💻 Technical Criteria
Given
Cargo has been identified as arrived at final destination
When
The system processes the arrival confirmation
Then
The cargo status is updated to 'Arrived' in the CCN database
R-GCX146-cbl-01069
Retrieve CCN Transit Status
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve CCN Transit Status' is invoked, and assuming that a ccn record exists in the database, when the system begins cargo arrival detection processing, the desired outcome is that transit status information is retrieved from the gcccrt ccn database for evaluation.
💻 Technical Criteria
Given
A CCN record exists in the database
When
The system begins cargo arrival detection processing
Then
Transit status information is retrieved from the GCCCRT CCN database for evaluation
R-GCX146-cbl-01070
Check Manifest Codes
Validation Rules
📊 Business Logic Narrative
When the process 'Check Manifest Codes' is invoked, and assuming that ccn transit status has been retrieved, when the system processes arrival detection, the desired outcome is that manifest station codes are checked from gcsb4rt train records to identify destination information.
💻 Technical Criteria
Given
CCN transit status has been retrieved
When
The system processes arrival detection
Then
Manifest station codes are checked from GCSB4RT train records to identify destination information
R-GCX146-cbl-01072
Build Return CCN Number
Computation Rules
📊 Business Logic Narrative
When the process 'Build Return CCN Number' is invoked, and assuming that equipment id and waybill date information are available, when a return ccn needs to be created for canadian goods, the desired outcome is that the system builds ccn with format: '6105e' + equipment_id + waybill_date + sequence_number.
💻 Technical Criteria
Given
Equipment ID and waybill date information are available
When
A return CCN needs to be created for Canadian goods
Then
The system builds CCN with format: '6105E' + equipment_id + waybill_date + sequence_number
R-GCX146-cbl-01073
Set CCN Status to 'RETURN'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to 'RETURN'' is invoked, and assuming that a new return ccn record is being created, when the ccn status needs to be established, the desired outcome is that the system sets ccn status to 'return' and transit status to 'r'.
💻 Technical Criteria
Given
A new return CCN record is being created
When
The CCN status needs to be established
Then
The system sets CCN status to 'RETURN' and transit status to 'R'
R-GCX146-cbl-01074
Populate Complete Shipment Data
Process Rules
📊 Business Logic Narrative
When the process 'Populate Complete Shipment Data' is invoked, and assuming that waybill data contains shipper and consignee information, when creating a return ccn record, the desired outcome is that the system populates shipper name, consignee name, origin station, destination station, and application type '33' for canadian customs.
💻 Technical Criteria
Given
Waybill data contains shipper and consignee information
When
Creating a return CCN record
Then
The system populates shipper name, consignee name, origin station, destination station, and application type '33' for Canadian customs
R-GCX146-cbl-01075
Insert Return CCN Record into Database
Action Rules
📊 Business Logic Narrative
When the process 'Insert Return CCN Record into Database' is invoked, and assuming that all return ccn data has been prepared and validated, when the system needs to persist the return ccn information, the desired outcome is that the system inserts the ccn record into gcccrt database and spawns gcx105 transaction for audit trail creation.
💻 Technical Criteria
Given
All return CCN data has been prepared and validated
When
The system needs to persist the return CCN information
Then
The system inserts the CCN record into GCCCRT database and spawns GCX105 transaction for audit trail creation
R-GCX146-cbl-01076
CCN Creation Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'CCN Creation Successful?' is invoked, and assuming that a return ccn creation attempt has been made, when the system checks the creation result, the desired outcome is that if successful, the system continues processing; if failed, the system handles the error condition.
💻 Technical Criteria
Given
A return CCN creation attempt has been made
When
The system checks the creation result
Then
If successful, the system continues processing; if failed, the system handles the error condition
R-GCX146-cbl-01388
Valid Return Pattern?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Return Pattern?' is invoked, and assuming that a cargo shipment identified as canadian origin with us destination history, when the system validates the return movement pattern, the desired outcome is that the movement is valid for return ccn creation if it represents canadian goods that went to us and are now returning to canada.
💻 Technical Criteria
Given
A cargo shipment identified as Canadian origin with US destination history
When
The system validates the return movement pattern
Then
The movement is valid for return CCN creation if it represents Canadian goods that went to US and are now returning to Canada
R-GCX146-cbl-01389
Build Return CCN Format
Computation Rules
📊 Business Logic Narrative
When the process 'Build Return CCN Format' is invoked, and assuming that valid return cargo with equipment id, waybill date, and carrier information, when the system creates a return ccn record, the desired outcome is that the ccn key is built using format: type '6' + carrier '105' + 'e' + equipment id + waybill date + sequence number.
💻 Technical Criteria
Given
Valid return cargo with equipment ID, waybill date, and carrier information
When
The system creates a return CCN record
Then
The CCN key is built using format: type '6' + carrier '105' + 'E' + equipment ID + waybill date + sequence number
R-GCX146-cbl-01390
Set Return Status Indicators
Action Rules
📊 Business Logic Narrative
When the process 'Set Return Status Indicators' is invoked, and assuming that a return ccn record being created, when the system sets status indicators, the desired outcome is that the ccn status is set to 'return' and application type is set to '33' for canadian customs processing.
💻 Technical Criteria
Given
A return CCN record being created
When
The system sets status indicators
Then
The CCN status is set to 'RETURN' and application type is set to '33' for Canadian customs processing
R-GCX146-cbl-01391
Create Return CCN Record
Action Rules
📊 Business Logic Narrative
When the process 'Create Return CCN Record' is invoked, and assuming that valid return cargo with complete shipment details including shipper, consignee, origin and destination station data, when the system creates the return ccn record, the desired outcome is that a new ccn record is inserted with status 'return', populated shipper/consignee information, origin/destination stations, and application type '33'.
💻 Technical Criteria
Given
Valid return cargo with complete shipment details including shipper, consignee, origin and destination station data
When
The system creates the return CCN record
Then
A new CCN record is inserted with status 'RETURN', populated shipper/consignee information, origin/destination stations, and application type '33'
R-GCX146-cbl-01392
Update Transit Status to 'R'
Action Rules
📊 Business Logic Narrative
When the process 'Update Transit Status to 'R'' is invoked, and assuming that a return ccn record successfully created, when the system updates transit status, the desired outcome is that the equipment transit status is set to 'r' to indicate return movement.
💻 Technical Criteria
Given
A return CCN record successfully created
When
The system updates transit status
Then
The equipment transit status is set to 'R' to indicate return movement
R-GCX146-cbl-01393
Log Return CCN Creation
Action Rules
📊 Business Logic Narrative
When the process 'Log Return CCN Creation' is invoked, and assuming that a return ccn record successfully created, when the system logs the creation activity, the desired outcome is that an audit trail entry is created by spawning gcx105 transaction with the return ccn details.
💻 Technical Criteria
Given
A return CCN record successfully created
When
The system logs the creation activity
Then
An audit trail entry is created by spawning GCX105 transaction with the return CCN details
R-GCX146-cbl-01560
Check Equipment Waybill Data
Action Rules
📊 Business Logic Narrative
When the process 'Check Equipment Waybill Data' is invoked, and assuming that equipment identified for potential return movement, when the system checks for associated waybill data, the desired outcome is that the system retrieves waybill information including shipper, consignee, and routing details.
💻 Technical Criteria
Given
Equipment identified for potential return movement
When
The system checks for associated waybill data
Then
The system retrieves waybill information including shipper, consignee, and routing details
R-GCX146-cbl-01561
Validate Canadian Destination
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Canadian Destination' is invoked, and assuming that a destination location code from waybill data, when the destination code is checked against canadian province list (nf, pe, ns, nb, pq, on, mb, sk, ab, bc, yt, nt), the desired outcome is that the system confirms if the destination is a valid canadian location.
💻 Technical Criteria
Given
A destination location code from waybill data
When
The destination code is checked against Canadian province list (NF, PE, NS, NB, PQ, ON, MB, SK, AB, BC, YT, NT)
Then
The system confirms if the destination is a valid Canadian location
R-GCX146-cbl-01562
Valid Return Scenario?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Return Scenario?' is invoked, and assuming that cargo movement from us to canada with valid waybill and destination data, when all return movement criteria are evaluated, the desired outcome is that the system determines if this qualifies as a valid return scenario for ccn processing.
💻 Technical Criteria
Given
Cargo movement from US to Canada with valid waybill and destination data
When
All return movement criteria are evaluated
Then
The system determines if this qualifies as a valid return scenario for CCN processing
R-GCX146-cbl-01563
Extract Shipper/Consignee Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Shipper/Consignee Information' is invoked, and assuming that valid waybill data for return movement, when the system processes the waybill information, the desired outcome is that the system extracts shipper name, consignee name, and related party information for ccn record creation.
💻 Technical Criteria
Given
Valid waybill data for return movement
When
The system processes the waybill information
Then
The system extracts shipper name, consignee name, and related party information for CCN record creation
R-GCX146-cbl-01564
Build Return CCN with 6105E Prefix
Computation Rules
📊 Business Logic Narrative
When the process 'Build Return CCN with 6105E Prefix' is invoked, and assuming that valid return movement with equipment and waybill data, when a return ccn needs to be created, the desired outcome is that the system builds ccn key with format: '6' + '105' + 'e' + equipment_id + waybill_date + sequence_number.
💻 Technical Criteria
Given
Valid return movement with equipment and waybill data
When
A return CCN needs to be created
Then
The system builds CCN key with format: '6' + '105' + 'E' + equipment_id + waybill_date + sequence_number
R-GCX146-cbl-01566
Set CCN Status to 'RETURN'
Action Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to 'RETURN'' is invoked, and assuming that ccn record being created for return movement, when ccn status needs to be assigned, the desired outcome is that the system sets ccn status to 'return' to indicate return cargo processing.
💻 Technical Criteria
Given
CCN record being created for return movement
When
CCN status needs to be assigned
Then
The system sets CCN status to 'RETURN' to indicate return cargo processing
R-GCX146-cbl-01567
Populate Return Movement Data
Process Rules
📊 Business Logic Narrative
When the process 'Populate Return Movement Data' is invoked, and assuming that return ccn record structure and extracted waybill data, when return movement data needs to be populated, the desired outcome is that the system populates shipper, consignee, origin station, destination station, and sets application type to '33' for canadian customs.
💻 Technical Criteria
Given
Return CCN record structure and extracted waybill data
When
Return movement data needs to be populated
Then
The system populates shipper, consignee, origin station, destination station, and sets application type to '33' for Canadian customs
R-GCX146-cbl-01568
Create Return CCN Record
Action Rules
📊 Business Logic Narrative
When the process 'Create Return CCN Record' is invoked, and assuming that fully populated return movement data, when return ccn record needs to be persisted, the desired outcome is that the system creates the ccn database record with return status and all associated movement data.
💻 Technical Criteria
Given
Fully populated return movement data
When
Return CCN record needs to be persisted
Then
The system creates the CCN database record with return status and all associated movement data
R-GCX146-cbl-01569
Log Return Movement Pattern
Action Rules
📊 Business Logic Narrative
When the process 'Log Return Movement Pattern' is invoked, and assuming that successfully created return ccn record, when return movement processing is complete, the desired outcome is that the system creates audit trail entry via gcx105 spawning to log the return movement pattern.
💻 Technical Criteria
Given
Successfully created return CCN record
When
Return movement processing is complete
Then
The system creates audit trail entry via GCX105 spawning to log the return movement pattern
R-GCX146-cbl-01691
Primary Waybill Lookup - FWIIROOT
Action Rules
📊 Business Logic Narrative
When the process 'Primary Waybill Lookup - FWIIROOT' is invoked, and assuming that an equipment id is provided for waybill lookup, when the system searches the fwiiroot database using the equipment id, the desired outcome is that the system retrieves waybill data if it exists or marks as not found for fallback processing.
💻 Technical Criteria
Given
An equipment ID is provided for waybill lookup
When
The system searches the FWIIROOT database using the equipment ID
Then
The system retrieves waybill data if it exists or marks as not found for fallback processing
R-GCX146-cbl-01692
Enhanced Waybill Search - SHIPROOT
Action Rules
📊 Business Logic Narrative
When the process 'Enhanced Waybill Search - SHIPROOT' is invoked, and assuming that primary waybill lookup in fwiiroot has failed to find waybill data, when the system performs enhanced search in shiproot database using expanded search criteria, the desired outcome is that the system retrieves waybill data if found or proceeds to inquiry database fallback.
💻 Technical Criteria
Given
Primary waybill lookup in FWIIROOT has failed to find waybill data
When
The system performs enhanced search in SHIPROOT database using expanded search criteria
Then
The system retrieves waybill data if found or proceeds to inquiry database fallback
R-GCX146-cbl-01693
Inquiry Database Fallback - FW-IQ
Action Rules
📊 Business Logic Narrative
When the process 'Inquiry Database Fallback - FW-IQ' is invoked, and assuming that both primary fwiiroot lookup and enhanced shiproot search have failed, when the system performs fallback search in fw-iq inquiry database, the desired outcome is that the system retrieves waybill data if available or marks waybill as not found.
💻 Technical Criteria
Given
Both primary FWIIROOT lookup and enhanced SHIPROOT search have failed
When
The system performs fallback search in FW-IQ inquiry database
Then
The system retrieves waybill data if available or marks waybill as not found
R-GCX146-cbl-01694
Set Waybill Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Waybill Found Flag' is invoked, and assuming that any waybill lookup method (primary, enhanced, or inquiry) has successfully found waybill data, when the system processes the successful lookup result, the desired outcome is that the system sets the waybill found flag to indicate successful retrieval.
💻 Technical Criteria
Given
Any waybill lookup method (primary, enhanced, or inquiry) has successfully found waybill data
When
The system processes the successful lookup result
Then
The system sets the waybill found flag to indicate successful retrieval
R-GCX146-cbl-01695
Extract Waybill Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Details' is invoked, and assuming that waybill data has been successfully found and waybill found flag is set, when the system processes the retrieved waybill record, the desired outcome is that the system extracts all relevant waybill details for further processing.
💻 Technical Criteria
Given
Waybill data has been successfully found and waybill found flag is set
When
The system processes the retrieved waybill record
Then
The system extracts all relevant waybill details for further processing
R-GCX146-cbl-01696
Validate Waybill Data Quality
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Waybill Data Quality' is invoked, and assuming that waybill details have been extracted from the retrieved record, when the system validates the completeness and quality of the waybill data, the desired outcome is that the system confirms data quality meets requirements for continued processing.
💻 Technical Criteria
Given
Waybill details have been extracted from the retrieved record
When
The system validates the completeness and quality of the waybill data
Then
The system confirms data quality meets requirements for continued processing
R-GCX146-cbl-01697
Set Waybill Not Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Waybill Not Found Flag' is invoked, and assuming that all waybill lookup methods (primary, enhanced, and inquiry) have failed to find waybill data, when the system processes the failed lookup results, the desired outcome is that the system sets the waybill not found flag to indicate no waybill data is available.
💻 Technical Criteria
Given
All waybill lookup methods (primary, enhanced, and inquiry) have failed to find waybill data
When
The system processes the failed lookup results
Then
The system sets the waybill not found flag to indicate no waybill data is available
R-GCX146-cbl-01698
Log Waybill Lookup Failure
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Waybill Lookup Failure', assuming that waybill not found flag has been set after all lookup methods failed, when the system processes the complete lookup failure, the desired outcome is that the system logs the waybill lookup failure with relevant equipment and search details.
💻 Technical Criteria
EXCLUDING
Waybill not found flag has been set after all lookup methods failed
When
The system processes the complete lookup failure
Then
The system logs the waybill lookup failure with relevant equipment and search details
R-GCX146-cbl-01842
Primary Waybill Lookup - FWIIROOT
Action Rules
📊 Business Logic Narrative
When the process 'Primary Waybill Lookup - FWIIROOT' is invoked, and assuming that an equipment id is provided for waybill lookup, when the system searches the fwiiroot waybill database using the equipment id as the search key, the desired outcome is that the system retrieves the waybill record and sets the waybill found flag if successful, or sets the waybill not found flag if unsuccessful.
💻 Technical Criteria
Given
An equipment ID is provided for waybill lookup
When
The system searches the FWIIROOT waybill database using the equipment ID as the search key
Then
The system retrieves the waybill record and sets the waybill found flag if successful, or sets the waybill not found flag if unsuccessful
R-GCX146-cbl-01843
Set Equipment ID as Search Key
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment ID as Search Key' is invoked, and assuming that a waybill lookup request is initiated, when the system prepares database search parameters, the desired outcome is that the equipment id is set as the search key for the fwiiroot database query.
💻 Technical Criteria
Given
A waybill lookup request is initiated
When
The system prepares database search parameters
Then
The equipment ID is set as the search key for the FWIIROOT database query
R-GCX146-cbl-01844
Database Call Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Database Call Successful?' is invoked, and assuming that a database call to fwiiroot has been executed, when the system evaluates the database call result, the desired outcome is that if the call is successful, the system proceeds to retrieve waybill data; if unsuccessful, the system sets failure indicators.
💻 Technical Criteria
Given
A database call to FWIIROOT has been executed
When
The system evaluates the database call result
Then
If the call is successful, the system proceeds to retrieve waybill data; if unsuccessful, the system sets failure indicators
R-GCX146-cbl-01845
Set WS-WAYBILL-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-FOUND Flag' is invoked, and assuming that a waybill record has been successfully retrieved from fwiiroot database, when the system processes the successful database response, the desired outcome is that the ws-waybill-found flag is set to indicate successful waybill retrieval.
💻 Technical Criteria
Given
A waybill record has been successfully retrieved from FWIIROOT database
When
The system processes the successful database response
Then
The WS-WAYBILL-FOUND flag is set to indicate successful waybill retrieval
R-GCX146-cbl-01846
Set WS-WAYBILL-NOT-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-NOT-FOUND Flag' is invoked, and assuming that a database call to fwiiroot has failed to retrieve a waybill record, when the system processes the unsuccessful database response, the desired outcome is that the ws-waybill-not-found flag is set to indicate failed waybill retrieval.
💻 Technical Criteria
Given
A database call to FWIIROOT has failed to retrieve a waybill record
When
The system processes the unsuccessful database response
Then
The WS-WAYBILL-NOT-FOUND flag is set to indicate failed waybill retrieval
R-GCX146-cbl-01847
Extract Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Information' is invoked, and assuming that a waybill record has been successfully retrieved and the waybill found flag is set, when the system processes the waybill record data, the desired outcome is that relevant waybill information is extracted and made available for subsequent business operations.
💻 Technical Criteria
Given
A waybill record has been successfully retrieved and the waybill found flag is set
When
The system processes the waybill record data
Then
Relevant waybill information is extracted and made available for subsequent business operations
R-GCX146-cbl-01848
Set Equipment ID Search Criteria
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment ID Search Criteria' is invoked, and assuming that a request to find waybill information for specific equipment, when the system prepares to search the shipment database, the desired outcome is that equipment id is configured as the primary search criterion for fwcarget lookup.
💻 Technical Criteria
Given
A request to find waybill information for specific equipment
When
The system prepares to search the shipment database
Then
Equipment ID is configured as the primary search criterion for FWCARGET lookup
R-GCX146-cbl-01850
Waybill Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Waybill Record Found?' is invoked, and assuming that fwcarget database query has been executed for equipment id, when the system evaluates the query results, the desired outcome is that system determines if waybill record exists and routes processing accordingly - to record retrieval if found or to not-found handling if absent.
💻 Technical Criteria
Given
FWCARGET database query has been executed for equipment ID
When
The system evaluates the query results
Then
System determines if waybill record exists and routes processing accordingly - to record retrieval if found or to not-found handling if absent
R-GCX146-cbl-01851
Retrieve Waybill Details
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Waybill Details' is invoked, and assuming that a valid waybill record has been found in the shipment database, when the system processes the located record, the desired outcome is that complete waybill details are extracted from the shipment record for further processing.
💻 Technical Criteria
Given
A valid waybill record has been found in the shipment database
When
The system processes the located record
Then
Complete waybill details are extracted from the shipment record for further processing
R-GCX146-cbl-01852
Set WS-WAYBILL-FOUND Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set WS-WAYBILL-FOUND Flag' is invoked, and assuming that waybill details have been successfully retrieved from the shipment record, when the system completes waybill information extraction, the desired outcome is that ws-waybill-found flag is set to indicate successful waybill location and retrieval.
💻 Technical Criteria
Given
Waybill details have been successfully retrieved from the shipment record
When
The system completes waybill information extraction
Then
WS-WAYBILL-FOUND flag is set to indicate successful waybill location and retrieval
R-GCX146-cbl-01853
Extract Shipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Shipment Information' is invoked, and assuming that waybill record has been retrieved and waybill-found flag is set, when the system processes the waybill data, the desired outcome is that relevant shipment information is extracted and organized for business use.
💻 Technical Criteria
Given
Waybill record has been retrieved and waybill-found flag is set
When
The system processes the waybill data
Then
Relevant shipment information is extracted and organized for business use
R-GCX146-cbl-01854
Validate Waybill Data Quality
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Waybill Data Quality' is invoked, and assuming that shipment information has been extracted from the waybill record, when the system validates the extracted data, the desired outcome is that data quality is assessed to determine if the waybill information is complete and usable.
💻 Technical Criteria
Given
Shipment information has been extracted from the waybill record
When
The system validates the extracted data
Then
Data quality is assessed to determine if the waybill information is complete and usable
R-GCX146-cbl-01855
Data Complete?
Decision Rules
📊 Business Logic Narrative
When the process 'Data Complete?' is invoked, and assuming that waybill data quality has been assessed, when the system evaluates data completeness, the desired outcome is that system determines if data is complete for immediate use or requires fallback to inquiry database.
💻 Technical Criteria
Given
Waybill data quality has been assessed
When
The system evaluates data completeness
Then
System determines if data is complete for immediate use or requires fallback to inquiry database
R-GCX146-cbl-01856
Return Waybill Information
Process Rules
📊 Business Logic Narrative
When the process 'Return Waybill Information' is invoked, and assuming that waybill data has been validated as complete and usable, when the system finalizes waybill processing, the desired outcome is that complete waybill information is returned for business operations.
💻 Technical Criteria
Given
Waybill data has been validated as complete and usable
When
The system finalizes waybill processing
Then
Complete waybill information is returned for business operations
R-GCX146-cbl-01857
Set WS-WAYBILL-NOT-FOUND Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set WS-WAYBILL-NOT-FOUND Flag', assuming that fwcarget query did not locate a waybill record for the equipment id, when the system processes the unsuccessful search result, the desired outcome is that ws-waybill-not-found flag is set to indicate waybill was not located in shipment database.
💻 Technical Criteria
EXCLUDING
FWCARGET query did not locate a waybill record for the equipment ID
When
The system processes the unsuccessful search result
Then
WS-WAYBILL-NOT-FOUND flag is set to indicate waybill was not located in shipment database
R-GCX146-cbl-01858
Prepare for Inquiry Database Fallback
Process Rules
📊 Business Logic Narrative
When the process 'Prepare for Inquiry Database Fallback' is invoked, and assuming that either no waybill record was found or retrieved data is incomplete, when the system determines primary search was unsuccessful, the desired outcome is that system prepares to use inquiry database as fallback search method.
💻 Technical Criteria
Given
Either no waybill record was found OR retrieved data is incomplete
When
The system determines primary search was unsuccessful
Then
System prepares to use inquiry database as fallback search method
R-GCX146-cbl-01394
Build CCN Prefix '6105E'
Definitional Rules
📊 Business Logic Narrative
When the process 'Build CCN Prefix '6105E'' is invoked, and assuming that a return ccn needs to be created for cargo processing, when the system builds the ccn identifier, the desired outcome is that the ccn prefix must be set to '6105e' to identify it as return cargo.
💻 Technical Criteria
Given
A return CCN needs to be created for cargo processing
When
The system builds the CCN identifier
Then
The CCN prefix must be set to '6105E' to identify it as return cargo
R-GCX146-cbl-01395
Extract Equipment ID from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from Waybill' is invoked, and assuming that a waybill record exists with equipment information, when the system processes return ccn creation, the desired outcome is that the equipment id must be extracted from the waybill record and used in ccn construction.
💻 Technical Criteria
Given
A waybill record exists with equipment information
When
The system processes return CCN creation
Then
The equipment ID must be extracted from the waybill record and used in CCN construction
R-GCX146-cbl-01396
Extract Waybill Date
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Date' is invoked, and assuming that a waybill record contains date information, when the system creates a return ccn, the desired outcome is that the waybill date must be extracted and included in the ccn identifier for uniqueness.
💻 Technical Criteria
Given
A waybill record contains date information
When
The system creates a return CCN
Then
The waybill date must be extracted and included in the CCN identifier for uniqueness
R-GCX146-cbl-01397
Concatenate: '6105E' + Equipment ID + Waybill Date
Computation Rules
📊 Business Logic Narrative
When the process 'Concatenate: '6105E' + Equipment ID + Waybill Date' is invoked, and assuming that ccn prefix '6105e', equipment id, and waybill date are available, when the system constructs the return ccn, the desired outcome is that the ccn must be formed by concatenating '6105e' + equipment id + waybill date in that exact sequence.
💻 Technical Criteria
Given
CCN prefix '6105E', equipment ID, and waybill date are available
When
The system constructs the return CCN
Then
The CCN must be formed by concatenating '6105E' + equipment ID + waybill date in that exact sequence
R-GCX146-cbl-01398
Compress CCN - Remove Spaces
Validation Rules
📊 Business Logic Narrative
When the process 'Compress CCN - Remove Spaces' is invoked, and assuming that a ccn string may contain spaces from concatenation, when the system finalizes the ccn format, the desired outcome is that all spaces must be removed from the ccn string to create a continuous identifier.
💻 Technical Criteria
Given
A CCN string may contain spaces from concatenation
When
The system finalizes the CCN format
Then
All spaces must be removed from the CCN string to create a continuous identifier
R-GCX146-cbl-01399
Organize Numeric Sequences
Process Rules
📊 Business Logic Narrative
When the process 'Organize Numeric Sequences' is invoked, and assuming that a ccn contains numeric sequences from equipment id and date, when the system processes ccn formatting, the desired outcome is that numeric sequences must be properly organized to maintain ccn integrity and uniqueness.
💻 Technical Criteria
Given
A CCN contains numeric sequences from equipment ID and date
When
The system processes CCN formatting
Then
Numeric sequences must be properly organized to maintain CCN integrity and uniqueness
R-GCX146-cbl-01400
Set CCN Status to 'RETURN'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to 'RETURN'' is invoked, and assuming that a new ccn is being created for return cargo, when the system sets the ccn status, the desired outcome is that the ccn status must be set to 'return' to indicate return cargo processing.
💻 Technical Criteria
Given
A new CCN is being created for return cargo
When
The system sets the CCN status
Then
The CCN status must be set to 'RETURN' to indicate return cargo processing
R-GCX146-cbl-01401
Set Transit Status to 'R'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'R'' is invoked, and assuming that a return ccn is being processed, when the system sets transit status, the desired outcome is that the transit status must be set to 'r' to indicate return movement status.
💻 Technical Criteria
Given
A return CCN is being processed
When
The system sets transit status
Then
The transit status must be set to 'R' to indicate return movement status
R-GCX146-cbl-01402
Populate Shipper Data from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Populate Shipper Data from Waybill' is invoked, and assuming that a waybill contains shipper information, when the system creates a return ccn record, the desired outcome is that shipper data must be extracted from the waybill and populated in the return ccn record.
💻 Technical Criteria
Given
A waybill contains shipper information
When
The system creates a return CCN record
Then
Shipper data must be extracted from the waybill and populated in the return CCN record
R-GCX146-cbl-01403
Populate Consignee Data from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Populate Consignee Data from Waybill' is invoked, and assuming that a waybill contains consignee information, when the system creates a return ccn record, the desired outcome is that consignee data must be extracted from the waybill and populated in the return ccn record.
💻 Technical Criteria
Given
A waybill contains consignee information
When
The system creates a return CCN record
Then
Consignee data must be extracted from the waybill and populated in the return CCN record
R-GCX146-cbl-01404
Validate CCN Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate CCN Format' is invoked, and assuming that a ccn has been constructed with all required components, when the system validates the ccn format, the desired outcome is that the ccn must meet all format requirements including proper length, character composition, and structure.
💻 Technical Criteria
Given
A CCN has been constructed with all required components
When
The system validates the CCN format
Then
The CCN must meet all format requirements including proper length, character composition, and structure
R-GCX146-cbl-01405
CCN Format Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Format Valid?' is invoked, and assuming that a ccn has undergone format validation, when the system evaluates validation results, the desired outcome is that if ccn format is valid, proceed to store the record; if invalid, handle format error.
💻 Technical Criteria
Given
A CCN has undergone format validation
When
The system evaluates validation results
Then
If CCN format is valid, proceed to store the record; if invalid, handle format error
R-GCX146-cbl-01406
Store Return CCN Record
Action Rules
📊 Business Logic Narrative
When the process 'Store Return CCN Record' is invoked, and assuming that a return ccn has passed all format validations, when the system processes the validated ccn, the desired outcome is that the return ccn record must be stored in the database with all populated data.
💻 Technical Criteria
Given
A return CCN has passed all format validations
When
The system processes the validated CCN
Then
The return CCN record must be stored in the database with all populated data
R-GCX146-cbl-01407
CCN Format Error
Action Rules
📊 Business Logic Narrative
When the process 'CCN Format Error' is invoked, and assuming that a ccn has failed format validation, when the system processes the validation failure, the desired outcome is that a format error must be generated and the ccn construction process must be terminated.
💻 Technical Criteria
Given
A CCN has failed format validation
When
The system processes the validation failure
Then
A format error must be generated and the CCN construction process must be terminated
R-GCX146-cbl-01570
Initialize CCN Compression Variables
Process Rules
📊 Business Logic Narrative
When the process 'Initialize CCN Compression Variables' is invoked, and assuming that a ccn number needs to be compressed, when the compression process begins, the desired outcome is that all compression variables are initialized to their default values and workspace areas are cleared.
💻 Technical Criteria
Given
A CCN number needs to be compressed
When
The compression process begins
Then
All compression variables are initialized to their default values and workspace areas are cleared
R-GCX146-cbl-01571
Remove Spaces from CCN Number
Computation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from CCN Number' is invoked, and assuming that a ccn number contains space characters, when space removal processing is performed, the desired outcome is that all spaces are removed from the ccn number and the result is stored for further processing.
💻 Technical Criteria
Given
A CCN number contains space characters
When
Space removal processing is performed
Then
All spaces are removed from the CCN number and the result is stored for further processing
R-GCX146-cbl-01572
Scan CCN Character by Character
Process Rules
📊 Business Logic Narrative
When the process 'Scan CCN Character by Character' is invoked, and assuming that a ccn number without spaces exists, when character-by-character scanning is performed, the desired outcome is that each character is examined and categorized for appropriate processing.
💻 Technical Criteria
Given
A CCN number without spaces exists
When
Character-by-character scanning is performed
Then
Each character is examined and categorized for appropriate processing
R-GCX146-cbl-01573
Character is Numeric?
Validation Rules
📊 Business Logic Narrative
When the process 'Character is Numeric?' is invoked, and assuming that a character from the ccn number is being examined, when character type validation is performed, the desired outcome is that the character is identified as either numeric (0-9) or non-numeric.
💻 Technical Criteria
Given
A character from the CCN number is being examined
When
Character type validation is performed
Then
The character is identified as either numeric (0-9) or non-numeric
R-GCX146-cbl-01575
Process Non-Numeric Character
Computation Rules
📊 Business Logic Narrative
When the process 'Process Non-Numeric Character' is invoked, and assuming that a character has been identified as non-numeric, when non-numeric character processing occurs, the desired outcome is that the character is processed according to ccn compression rules for non-numeric elements.
💻 Technical Criteria
Given
A character has been identified as non-numeric
When
Non-numeric character processing occurs
Then
The character is processed according to CCN compression rules for non-numeric elements
R-GCX146-cbl-01576
Organize Numeric Sequences
Computation Rules
📊 Business Logic Narrative
When the process 'Organize Numeric Sequences' is invoked, and assuming that numeric sequences have been collected from the ccn number, when sequence organization processing occurs, the desired outcome is that numeric sequences are organized according to ccn compression algorithm requirements.
💻 Technical Criteria
Given
Numeric sequences have been collected from the CCN number
When
Sequence organization processing occurs
Then
Numeric sequences are organized according to CCN compression algorithm requirements
R-GCX146-cbl-01577
Apply CCN Formatting Rules
Computation Rules
📊 Business Logic Narrative
When the process 'Apply CCN Formatting Rules' is invoked, and assuming that numeric sequences have been organized and characters processed, when ccn formatting rules are applied, the desired outcome is that the ccn is formatted according to standard compression formatting requirements.
💻 Technical Criteria
Given
Numeric sequences have been organized and characters processed
When
CCN formatting rules are applied
Then
The CCN is formatted according to standard compression formatting requirements
R-GCX146-cbl-01578
Validate Compressed CCN Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Compressed CCN Format' is invoked, and assuming that a ccn has been compressed and formatted, when format validation is performed, the desired outcome is that the compressed ccn format is validated against business rules and either accepted or rejected.
💻 Technical Criteria
Given
A CCN has been compressed and formatted
When
Format validation is performed
Then
The compressed CCN format is validated against business rules and either accepted or rejected
R-GCX146-cbl-01579
Store Compressed CCN
Process Rules
📊 Business Logic Narrative
When the process 'Store Compressed CCN' is invoked, and assuming that a ccn has passed compression format validation, when ccn storage processing occurs, the desired outcome is that the compressed ccn is stored and made available for subsequent business operations.
💻 Technical Criteria
Given
A CCN has passed compression format validation
When
CCN storage processing occurs
Then
The compressed CCN is stored and made available for subsequent business operations
R-GCX146-cbl-01580
Set Compression Error Flag
Validation Rules
📊 Business Logic Narrative
When the process 'Set Compression Error Flag' is invoked, and assuming that a ccn has failed compression format validation, when error handling processing occurs, the desired outcome is that compression error flags are set to indicate the failure condition.
💻 Technical Criteria
Given
A CCN has failed compression format validation
When
Error handling processing occurs
Then
Compression error flags are set to indicate the failure condition
R-GCX146-cbl-01581
Complete CCN Compression
Process Rules
📊 Business Logic Narrative
When the process 'Complete CCN Compression' is invoked, and assuming that ccn compression processing has been performed, when process completion occurs, the desired outcome is that the ccn compression process is finalized with either successful compression or error status.
💻 Technical Criteria
Given
CCN compression processing has been performed
When
Process completion occurs
Then
The CCN compression process is finalized with either successful compression or error status
R-GCX146-cbl-01699
Initialize CCN Compression Variables
Process Rules
📊 Business Logic Narrative
When the process 'Initialize CCN Compression Variables' is invoked, and assuming that a ccn formatting process needs to begin, when the system starts ccn formatting, the desired outcome is that all ccn compression variables are initialized to their default values.
💻 Technical Criteria
Given
A CCN formatting process needs to begin
When
The system starts CCN formatting
Then
All CCN compression variables are initialized to their default values
R-GCX146-cbl-01700
Move CCN to Working Storage
Process Rules
📊 Business Logic Narrative
When the process 'Move CCN to Working Storage' is invoked, and assuming that a ccn value exists in the input data, when the system begins ccn formatting, the desired outcome is that the ccn value is moved to working storage for manipulation.
💻 Technical Criteria
Given
A CCN value exists in the input data
When
The system begins CCN formatting
Then
The CCN value is moved to working storage for manipulation
R-GCX146-cbl-01701
Remove Spaces from CCN
Computation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from CCN' is invoked, and assuming that a ccn contains spaces within its structure, when the system processes the ccn for formatting, the desired outcome is that all spaces are removed from the ccn value.
💻 Technical Criteria
Given
A CCN contains spaces within its structure
When
The system processes the CCN for formatting
Then
All spaces are removed from the CCN value
R-GCX146-cbl-01702
Check for Numeric Sequences
Validation Rules
📊 Business Logic Narrative
When the process 'Check for Numeric Sequences' is invoked, and assuming that a ccn has been processed to remove spaces, when the system examines the ccn structure, the desired outcome is that numeric sequences within the ccn are identified and flagged.
💻 Technical Criteria
Given
A CCN has been processed to remove spaces
When
The system examines the CCN structure
Then
Numeric sequences within the CCN are identified and flagged
R-GCX146-cbl-01703
Contains Numeric Characters?
Decision Rules
📊 Business Logic Narrative
When the process 'Contains Numeric Characters?' is invoked, and assuming that a ccn has been analyzed for numeric sequences, when the system evaluates the ccn content, the desired outcome is that the system determines whether numeric characters are present and routes processing accordingly.
💻 Technical Criteria
Given
A CCN has been analyzed for numeric sequences
When
The system evaluates the CCN content
Then
The system determines whether numeric characters are present and routes processing accordingly
R-GCX146-cbl-01704
Organize Numeric Sequences
Computation Rules
📊 Business Logic Narrative
When the process 'Organize Numeric Sequences' is invoked, and assuming that the ccn contains numeric characters, when the system processes the numeric sequences, the desired outcome is that numeric sequences are organized according to ccn formatting standards.
💻 Technical Criteria
Given
The CCN contains numeric characters
When
The system processes the numeric sequences
Then
Numeric sequences are organized according to CCN formatting standards
R-GCX146-cbl-01705
Format Equipment ID Component
Computation Rules
📊 Business Logic Narrative
When the process 'Format Equipment ID Component' is invoked, and assuming that numeric sequences have been organized within the ccn, when the system formats the equipment id component, the desired outcome is that the equipment id portion is formatted according to standard ccn structure requirements.
💻 Technical Criteria
Given
Numeric sequences have been organized within the CCN
When
The system formats the equipment ID component
Then
The equipment ID portion is formatted according to standard CCN structure requirements
R-GCX146-cbl-01706
Apply Standard CCN Structure
Computation Rules
📊 Business Logic Narrative
When the process 'Apply Standard CCN Structure' is invoked, and assuming that ccn components have been individually formatted, when the system applies standard ccn structure, the desired outcome is that the ccn is formatted according to standard structure requirements regardless of whether it contains numeric characters.
💻 Technical Criteria
Given
CCN components have been individually formatted
When
The system applies standard CCN structure
Then
The CCN is formatted according to standard structure requirements regardless of whether it contains numeric characters
R-GCX146-cbl-01707
Validate Formatted CCN Length
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Formatted CCN Length' is invoked, and assuming that a ccn has been formatted according to standard structure, when the system validates the formatted ccn, the desired outcome is that the ccn length is checked against acceptable length criteria.
💻 Technical Criteria
Given
A CCN has been formatted according to standard structure
When
The system validates the formatted CCN
Then
The CCN length is checked against acceptable length criteria
R-GCX146-cbl-01708
CCN Length Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Length Valid?' is invoked, and assuming that the formatted ccn length has been validated, when the system evaluates length compliance, the desired outcome is that the system determines whether the ccn length is valid and routes processing to either storage or error handling.
💻 Technical Criteria
Given
The formatted CCN length has been validated
When
The system evaluates length compliance
Then
The system determines whether the CCN length is valid and routes processing to either storage or error handling
R-GCX146-cbl-01709
Store Compressed CCN
Process Rules
📊 Business Logic Narrative
When the process 'Store Compressed CCN' is invoked, and assuming that the ccn has passed length validation, when the system stores the formatted ccn, the desired outcome is that the compressed ccn is stored for further processing.
💻 Technical Criteria
Given
The CCN has passed length validation
When
The system stores the formatted CCN
Then
The compressed CCN is stored for further processing
R-GCX146-cbl-01710
Set Formatting Complete Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Formatting Complete Flag' is invoked, and assuming that the ccn has been successfully stored in compressed format, when the system completes ccn formatting, the desired outcome is that the formatting complete flag is set to indicate successful processing.
💻 Technical Criteria
Given
The CCN has been successfully stored in compressed format
When
The system completes CCN formatting
Then
The formatting complete flag is set to indicate successful processing
R-GCX146-cbl-01711
CCN Formatting Error
Process Rules
📊 Business Logic Narrative
When the process 'CCN Formatting Error' is invoked, and assuming that the ccn fails length validation or other formatting requirements, when the system encounters a formatting error, the desired outcome is that an error condition is set and appropriate error handling is initiated.
💻 Technical Criteria
Given
The CCN fails length validation or other formatting requirements
When
The system encounters a formatting error
Then
An error condition is set and appropriate error handling is initiated
R-GCX146-cbl-01859
Skip Space Character
Process Rules
📊 Business Logic Narrative
When the process 'Skip Space Character' is invoked, and assuming that a ccn contains space characters within the number, when the system processes the ccn for compression, the desired outcome is that all space characters are identified and excluded from the compressed ccn output.
💻 Technical Criteria
Given
A CCN contains space characters within the number
When
The system processes the CCN for compression
Then
All space characters are identified and excluded from the compressed CCN output
R-GCX146-cbl-01860
Copy Character to Compressed CCN
Process Rules
📊 Business Logic Narrative
When the process 'Copy Character to Compressed CCN' is invoked, and assuming that a ccn contains both space and non-space characters, when the system encounters a non-space character during compression, the desired outcome is that the character is copied to the compressed ccn maintaining the original sequence.
💻 Technical Criteria
Given
A CCN contains both space and non-space characters
When
The system encounters a non-space character during compression
Then
The character is copied to the compressed CCN maintaining the original sequence
R-GCX146-cbl-01861
Scan CCN Character by Character
Process Rules
📊 Business Logic Narrative
When the process 'Scan CCN Character by Character' is invoked, and assuming that a ccn requires space removal processing, when the system begins compression, the desired outcome is that each character position in the ccn is examined individually from start to end.
💻 Technical Criteria
Given
A CCN requires space removal processing
When
The system begins compression
Then
Each character position in the CCN is examined individually from start to end
R-GCX146-cbl-01862
Format Compressed CCN
Process Rules
📊 Business Logic Narrative
When the process 'Format Compressed CCN' is invoked, and assuming that all characters in the ccn have been processed and spaces removed, when the compression process reaches completion, the desired outcome is that the compressed ccn is formatted and prepared for return to the calling process.
💻 Technical Criteria
Given
All characters in the CCN have been processed and spaces removed
When
The compression process reaches completion
Then
The compressed CCN is formatted and prepared for return to the calling process
R-GCX146-cbl-01863
Receive CCN Input Data
Process Rules
📊 Business Logic Narrative
When the process 'Receive CCN Input Data' is invoked, and assuming that a ccn input data is provided to the system, when the organize numeric sequences process is initiated, the desired outcome is that the system accepts the ccn input data for further processing.
💻 Technical Criteria
Given
A CCN input data is provided to the system
When
The organize numeric sequences process is initiated
Then
The system accepts the CCN input data for further processing
R-GCX146-cbl-01864
Remove Spaces from CCN
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from CCN' is invoked, and assuming that a ccn contains spaces within the string, when the space removal process is executed, the desired outcome is that all spaces are removed from the ccn string to create a continuous character sequence.
💻 Technical Criteria
Given
A CCN contains spaces within the string
When
The space removal process is executed
Then
All spaces are removed from the CCN string to create a continuous character sequence
R-GCX146-cbl-01865
Initialize Sequence Counter
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Sequence Counter' is invoked, and assuming that the ccn processing is about to begin, when the sequence counter initialization is performed, the desired outcome is that the sequence counter is set to its starting value for character position tracking.
💻 Technical Criteria
Given
The CCN processing is about to begin
When
The sequence counter initialization is performed
Then
The sequence counter is set to its starting value for character position tracking
R-GCX146-cbl-01866
Scan CCN Characters
Process Rules
📊 Business Logic Narrative
When the process 'Scan CCN Characters' is invoked, and assuming that a ccn string is ready for character-by-character analysis, when the character scanning process is executed, the desired outcome is that each character in the ccn string is examined in sequence.
💻 Technical Criteria
Given
A CCN string is ready for character-by-character analysis
When
The character scanning process is executed
Then
Each character in the CCN string is examined in sequence
R-GCX146-cbl-01867
Character is Numeric?
Decision Rules
📊 Business Logic Narrative
When the process 'Character is Numeric?' is invoked, and assuming that a character from the ccn string is being examined, when the character type validation is performed, the desired outcome is that the system identifies whether the character is numeric (0-9) or non-numeric.
💻 Technical Criteria
Given
A character from the CCN string is being examined
When
The character type validation is performed
Then
The system identifies whether the character is numeric (0-9) or non-numeric
R-GCX146-cbl-01869
Process Non-Numeric Character
Process Rules
📊 Business Logic Narrative
When the process 'Process Non-Numeric Character' is invoked, and assuming that a character has been identified as non-numeric, when the non-numeric character processing is executed, the desired outcome is that the non-numeric character is handled according to the ccn organization rules.
💻 Technical Criteria
Given
A character has been identified as non-numeric
When
The non-numeric character processing is executed
Then
The non-numeric character is handled according to the CCN organization rules
R-GCX146-cbl-01870
End of CCN String?
Decision Rules
📊 Business Logic Narrative
When the process 'End of CCN String?' is invoked, and assuming that characters are being processed from the ccn string, when the string completion check is performed, the desired outcome is that the system determines if there are more characters to process or if the end of the string has been reached.
💻 Technical Criteria
Given
Characters are being processed from the CCN string
When
The string completion check is performed
Then
The system determines if there are more characters to process or if the end of the string has been reached
R-GCX146-cbl-01871
Format Organized Sequence
Computation Rules
📊 Business Logic Narrative
When the process 'Format Organized Sequence' is invoked, and assuming that all characters in the ccn have been processed and organized, when the sequence formatting process is executed, the desired outcome is that the organized sequence is formatted according to the specified business format requirements.
💻 Technical Criteria
Given
All characters in the CCN have been processed and organized
When
The sequence formatting process is executed
Then
The organized sequence is formatted according to the specified business format requirements
R-GCX146-cbl-01872
Store Compressed CCN
Process Rules
📊 Business Logic Narrative
When the process 'Store Compressed CCN' is invoked, and assuming that the ccn has been organized and formatted, when the storage process is executed, the desired outcome is that the compressed ccn is stored in the designated location for further business processing.
💻 Technical Criteria
Given
The CCN has been organized and formatted
When
The storage process is executed
Then
The compressed CCN is stored in the designated location for further business processing
R-GCX146-cbl-01408
Extract Equipment ID from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from Waybill' is invoked, and assuming that a waybill record exists with equipment information, when the system processes return ccn data assembly, the desired outcome is that the equipment id is extracted from the waybill record and stored for ccn creation.
💻 Technical Criteria
Given
A waybill record exists with equipment information
When
The system processes return CCN data assembly
Then
The equipment ID is extracted from the waybill record and stored for CCN creation
R-GCX146-cbl-01409
Extract Waybill Date Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Waybill Date Information' is invoked, and assuming that a waybill record contains date information, when the system processes return ccn data assembly, the desired outcome is that the waybill date is extracted and formatted for use in ccn key generation.
💻 Technical Criteria
Given
A waybill record contains date information
When
The system processes return CCN data assembly
Then
The waybill date is extracted and formatted for use in CCN key generation
R-GCX146-cbl-01410
Build Return CCN Number
Computation Rules
📊 Business Logic Narrative
When the process 'Build Return CCN Number' is invoked, and assuming that equipment id and waybill date have been extracted, when the system builds the return ccn number, the desired outcome is that the ccn number is constructed with format '6105e' + equipment id + waybill date + sequence number.
💻 Technical Criteria
Given
Equipment ID and waybill date have been extracted
When
The system builds the return CCN number
Then
The CCN number is constructed with format '6105E' + equipment ID + waybill date + sequence number
R-GCX146-cbl-01411
Set CCN Status to 'RETURN'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set CCN Status to 'RETURN'' is invoked, and assuming that a return ccn record is being created, when the system sets the ccn status, the desired outcome is that the ccn status is set to 'return' to indicate return cargo processing.
💻 Technical Criteria
Given
A return CCN record is being created
When
The system sets the CCN status
Then
The CCN status is set to 'RETURN' to indicate return cargo processing
R-GCX146-cbl-01412
Set Transit Status to 'R'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'R'' is invoked, and assuming that a return ccn record is being processed, when the system sets the transit status, the desired outcome is that the transit status is set to 'r' to indicate return transit movement.
💻 Technical Criteria
Given
A return CCN record is being processed
When
The system sets the transit status
Then
The transit status is set to 'R' to indicate return transit movement
R-GCX146-cbl-01413
Extract Shipper Information from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Extract Shipper Information from Waybill' is invoked, and assuming that a waybill record contains shipper information in the ship segment, when the system processes return ccn data assembly, the desired outcome is that the shipper name and address information is extracted and populated in the ccn record.
💻 Technical Criteria
Given
A waybill record contains shipper information in the SHIP segment
When
The system processes return CCN data assembly
Then
The shipper name and address information is extracted and populated in the CCN record
R-GCX146-cbl-01414
Extract Consignee Information from Waybill
Process Rules
📊 Business Logic Narrative
When the process 'Extract Consignee Information from Waybill' is invoked, and assuming that a waybill record contains consignee information in the cons segment, when the system processes return ccn data assembly, the desired outcome is that the consignee name and address information is extracted and populated in the ccn record.
💻 Technical Criteria
Given
A waybill record contains consignee information in the CONS segment
When
The system processes return CCN data assembly
Then
The consignee name and address information is extracted and populated in the CCN record
R-GCX146-cbl-01415
Populate Origin Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Populate Origin Station Data' is invoked, and assuming that station codes are available from waybill or train information, when the system populates origin station data, the desired outcome is that the origin station information is populated in the ccn record using the appropriate station codes.
💻 Technical Criteria
Given
Station codes are available from waybill or train information
When
The system populates origin station data
Then
The origin station information is populated in the CCN record using the appropriate station codes
R-GCX146-cbl-01416
Populate Destination Station Data
Process Rules
📊 Business Logic Narrative
When the process 'Populate Destination Station Data' is invoked, and assuming that station codes are available from waybill or train information, when the system populates destination station data, the desired outcome is that the destination station information is populated in the ccn record using the appropriate station codes.
💻 Technical Criteria
Given
Station codes are available from waybill or train information
When
The system populates destination station data
Then
The destination station information is populated in the CCN record using the appropriate station codes
R-GCX146-cbl-01417
Set Commodity Code Information
Process Rules
📊 Business Logic Narrative
When the process 'Set Commodity Code Information' is invoked, and assuming that a waybill record contains commodity information, when the system sets commodity code information, the desired outcome is that the commodity description and code are extracted from the waybill and populated in the ccn record.
💻 Technical Criteria
Given
A waybill record contains commodity information
When
The system sets commodity code information
Then
The commodity description and code are extracted from the waybill and populated in the CCN record
R-GCX146-cbl-01418
Assign Weight and Quantity Data
Process Rules
📊 Business Logic Narrative
When the process 'Assign Weight and Quantity Data' is invoked, and assuming that a waybill record contains weight and quantity information, when the system assigns weight and quantity data, the desired outcome is that the shipment weight and quantity are extracted from the waybill and populated in the ccn record.
💻 Technical Criteria
Given
A waybill record contains weight and quantity information
When
The system assigns weight and quantity data
Then
The shipment weight and quantity are extracted from the waybill and populated in the CCN record
R-GCX146-cbl-01419
Set Return Processing Flags
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Return Processing Flags' is invoked, and assuming that a return ccn record is being assembled, when the system sets return processing flags, the desired outcome is that the appropriate flags are set to indicate return cargo processing requirements and handling instructions.
💻 Technical Criteria
Given
A return CCN record is being assembled
When
The system sets return processing flags
Then
The appropriate flags are set to indicate return cargo processing requirements and handling instructions
R-GCX146-cbl-01420
Complete CCN Record Assembly
Process Rules
📊 Business Logic Narrative
When the process 'Complete CCN Record Assembly' is invoked, and assuming that all individual data elements have been extracted and populated, when the system completes ccn record assembly, the desired outcome is that the ccn record is finalized with all required data elements populated and ready for database insertion.
💻 Technical Criteria
Given
All individual data elements have been extracted and populated
When
The system completes CCN record assembly
Then
The CCN record is finalized with all required data elements populated and ready for database insertion
R-GCX146-cbl-01421
Return CCN Data Ready for Insert
Process Rules
📊 Business Logic Narrative
When the process 'Return CCN Data Ready for Insert' is invoked, and assuming that the ccn record assembly is complete with all required data, when the system prepares the data for insert, the desired outcome is that the return ccn data is ready for database insertion with all business rules satisfied and data integrity validated.
💻 Technical Criteria
Given
The CCN record assembly is complete with all required data
When
The system prepares the data for insert
Then
The return CCN data is ready for database insertion with all business rules satisfied and data integrity validated
R-GCX146-cbl-01077
Send X12 EDI Notification via GCCS309C
Action Rules
📊 Business Logic Narrative
When the process 'Send X12 EDI Notification via GCCS309C' is invoked, and assuming that a ccn requires broker notification and primary broker exists and broker communication preference is x12 edi, when the system processes broker notification distribution, the desired outcome is that the system invokes gccs309c program to send x12 edi notification to the primary broker.
💻 Technical Criteria
Given
A CCN requires broker notification AND primary broker exists AND broker communication preference is X12 EDI
When
The system processes broker notification distribution
Then
The system invokes GCCS309C program to send X12 EDI notification to the primary broker
R-GCX146-cbl-01078
Send Merlin Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin Notification via GCX019' is invoked, and assuming that a ccn requires broker notification and primary broker exists and broker communication preference is merlin, when the system processes broker notification distribution, the desired outcome is that the system invokes gcx019 program to send merlin notification to the primary broker.
💻 Technical Criteria
Given
A CCN requires broker notification AND primary broker exists AND broker communication preference is Merlin
When
The system processes broker notification distribution
Then
The system invokes GCX019 program to send Merlin notification to the primary broker
R-GCX146-cbl-01079
Send Internet Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Internet Notification via GCX019' is invoked, and assuming that a ccn requires broker notification and primary broker exists and broker communication preference is internet, when the system processes broker notification distribution, the desired outcome is that the system invokes gcx019 program to send internet notification to the primary broker.
💻 Technical Criteria
Given
A CCN requires broker notification AND primary broker exists AND broker communication preference is Internet
When
The system processes broker notification distribution
Then
The system invokes GCX019 program to send Internet notification to the primary broker
R-GCX146-cbl-01080
Send FAX Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send FAX Notification via GCX019' is invoked, and assuming that a ccn requires broker notification and primary broker exists and broker communication preference is fax, when the system processes broker notification distribution, the desired outcome is that the system invokes gcx019 program to send fax notification to the primary broker.
💻 Technical Criteria
Given
A CCN requires broker notification AND primary broker exists AND broker communication preference is FAX
When
The system processes broker notification distribution
Then
The system invokes GCX019 program to send FAX notification to the primary broker
R-GCX146-cbl-01081
Send Paper Notification via Batch Print Call Letters
Action Rules
📊 Business Logic Narrative
When the process 'Send Paper Notification via Batch Print Call Letters' is invoked, and assuming that a ccn requires broker notification and primary broker exists and broker communication preference is paper, when the system processes broker notification distribution, the desired outcome is that the system generates paper notification through batch print call letters process.
💻 Technical Criteria
Given
A CCN requires broker notification AND primary broker exists AND broker communication preference is Paper
When
The system processes broker notification distribution
Then
The system generates paper notification through batch print call letters process
R-GCX146-cbl-01089
W400-COMPRESS-CCN: Remove Spaces from CCN
Process Rules
📊 Business Logic Narrative
When the process 'W400-COMPRESS-CCN: Remove Spaces from CCN' is invoked, and assuming that a ccn number containing space characters, when the system processes the ccn for compression, the desired outcome is that all space characters are removed from the ccn number while preserving all non-space characters in their original sequence.
💻 Technical Criteria
Given
A CCN number containing space characters
When
The system processes the CCN for compression
Then
All space characters are removed from the CCN number while preserving all non-space characters in their original sequence
R-GCX146-cbl-01090
Scan CCN Character by Character
Process Rules
📊 Business Logic Narrative
When the process 'Scan CCN Character by Character' is invoked, and assuming that a ccn number with mixed characters and spaces, when the system scans the ccn character by character, the desired outcome is that each character position is evaluated to determine if it contains a space or non-space character.
💻 Technical Criteria
Given
A CCN number with mixed characters and spaces
When
The system scans the CCN character by character
Then
Each character position is evaluated to determine if it contains a space or non-space character
R-GCX146-cbl-01091
Is Character a Space?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Character a Space?' is invoked, and assuming that a character being examined during ccn compression, when the character is identified as a space, the desired outcome is that the space character is skipped and not included in the compressed ccn output.
💻 Technical Criteria
Given
A character being examined during CCN compression
When
The character is identified as a space
Then
The space character is skipped and not included in the compressed CCN output
R-GCX146-cbl-01092
Keep Non-Space Character
Process Rules
📊 Business Logic Narrative
When the process 'Keep Non-Space Character' is invoked, and assuming that a character being examined during ccn compression, when the character is identified as a non-space character, the desired outcome is that the character is retained and included in the compressed ccn output in its sequential position.
💻 Technical Criteria
Given
A character being examined during CCN compression
When
The character is identified as a non-space character
Then
The character is retained and included in the compressed CCN output in its sequential position
R-GCX146-cbl-01096
Reorganize CCN Structure
Process Rules
📊 Business Logic Narrative
When the process 'Reorganize CCN Structure' is invoked, and assuming that a ccn with formatted numeric components and preserved characters, when the system reorganizes the ccn structure, the desired outcome is that ccn components are arranged in the standard format with proper sequencing and positioning.
💻 Technical Criteria
Given
A CCN with formatted numeric components and preserved characters
When
The system reorganizes the CCN structure
Then
CCN components are arranged in the standard format with proper sequencing and positioning
R-GCX146-cbl-01097
Build Compressed CCN Format
Process Rules
📊 Business Logic Narrative
When the process 'Build Compressed CCN Format' is invoked, and assuming that reorganized ccn components with formatted numeric sequences, when the system builds the compressed ccn format, the desired outcome is that all components are combined into a single compressed ccn string without spaces and with standardized formatting.
💻 Technical Criteria
Given
Reorganized CCN components with formatted numeric sequences
When
The system builds the compressed CCN format
Then
All components are combined into a single compressed CCN string without spaces and with standardized formatting
R-GCX146-cbl-01098
Validate Compressed CCN
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Compressed CCN' is invoked, and assuming that a compressed ccn format constructed from processed components, when the system validates the compressed ccn, the desired outcome is that the ccn format is verified against business rules for length, character composition, and structural requirements.
💻 Technical Criteria
Given
A compressed CCN format constructed from processed components
When
The system validates the compressed CCN
Then
The CCN format is verified against business rules for length, character composition, and structural requirements
R-GCX146-cbl-01099
CCN Format Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'CCN Format Valid?' is invoked, and assuming that a compressed ccn that has undergone format validation, when the ccn format validation is successful, the desired outcome is that the system returns the compressed ccn for further processing.
💻 Technical Criteria
Given
A compressed CCN that has undergone format validation
When
The CCN format validation is successful
Then
The system returns the compressed CCN for further processing
R-GCX146-cbl-01100
Handle Format Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Format Error' is invoked, and assuming that a compressed ccn that fails format validation, when the ccn format validation is unsuccessful, the desired outcome is that the system initiates error handling procedures and does not return the invalid ccn format.
💻 Technical Criteria
Given
A compressed CCN that fails format validation
When
The CCN format validation is unsuccessful
Then
The system initiates error handling procedures and does not return the invalid CCN format
R-GCX146-cbl-01153
Check Transit Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Transit Status' is invoked, and assuming that a ccn record has current status of 'release', when the transit status is 'e' (export) or 'z' (export zone), the desired outcome is that assign the trip sheet status as 'export'.
💻 Technical Criteria
Given
A CCN record has current status of 'RELEASE'
When
The transit status is 'E' (Export) or 'Z' (Export Zone)
Then
Assign the trip sheet status as 'EXPORT'
R-GCX146-cbl-01154
Has S.A.R. Release?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Has S.A.R. Release?', assuming that a ccn record has current status of 'release' and transit status is not 'e' or 'z', when the release-by field contains 's.a.r.', the desired outcome is that assign the trip sheet status as 's.a.r.'.
💻 Technical Criteria
EXCLUDING
A CCN record has current status of 'RELEASE' and transit status is not 'E' or 'Z'
When
The release-by field contains 'S.A.R.'
Then
Assign the trip sheet status as 'S.A.R.'
R-GCX146-cbl-01155
Assign Status = 'RELEASE'
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Assign Status = 'RELEASE'', assuming that a ccn record has current status of 'release' and transit status is not 'e' or 'z', when the release-by field does not contain 's.a.r.', the desired outcome is that assign the trip sheet status as 'release'.
💻 Technical Criteria
EXCLUDING
A CCN record has current status of 'RELEASE' and transit status is not 'E' or 'Z'
When
The release-by field does not contain 'S.A.R.'
Then
Assign the trip sheet status as 'RELEASE'
R-GCX146-cbl-01156
Transit Status = 'T'?
Decision Rules
📊 Business Logic Narrative
When the process 'Transit Status = 'T'?' is invoked, and assuming that a ccn record has current status other than 'release', when the transit status is 't' (transit), the desired outcome is that assign the trip sheet status as 'transit'.
💻 Technical Criteria
Given
A CCN record has current status other than 'RELEASE'
When
The transit status is 'T' (Transit)
Then
Assign the trip sheet status as 'TRANSIT'
R-GCX146-cbl-01157
Transit Status = 'R'?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Status = 'R'?', assuming that a ccn record has current status other than 'release' and transit status is not 't', when the transit status is 'r' (return), the desired outcome is that assign the trip sheet status as 'return'.
💻 Technical Criteria
EXCLUDING
A CCN record has current status other than 'RELEASE' and transit status is not 'T'
When
The transit status is 'R' (Return)
Then
Assign the trip sheet status as 'RETURN'
R-GCX146-cbl-01158
Keep Current Status
Decision Rules
📊 Business Logic Narrative
When the process 'Keep Current Status' is invoked, and assuming that a ccn record has current status other than 'release', when the transit status is neither 't' nor 'r', the desired outcome is that assign the trip sheet status as the current ccn status without modification.
💻 Technical Criteria
Given
A CCN record has current status other than 'RELEASE'
When
The transit status is neither 'T' nor 'R'
Then
Assign the trip sheet status as the current CCN status without modification
💰 Bond & Financial Auth
15 logic blocks
R-GCX146-cbl-00065
Handle Century Format for Y2K Compliance
Decision Rules
📊 Business Logic Narrative
When the process 'Handle Century Format for Y2K Compliance' is invoked, and assuming that a year value needs century determination for date processing, when the year value is greater than 70, the desired outcome is that the century is set to 19xx (1900s), otherwise the century is set to 20xx (2000s).
💻 Technical Criteria
Given
A year value needs century determination for date processing
When
The year value is greater than 70
Then
The century is set to 19xx (1900s), otherwise the century is set to 20xx (2000s)
R-GCX146-cbl-01287
Format Total Values for Display
Process Rules
📊 Business Logic Narrative
When the process 'Format Total Values for Display' is invoked, and assuming that calculated total counter values exist as numeric fields, when the system prepares totals for report display, the desired outcome is that each total value is formatted with leading zeros suppressed and right-justified in display fields.
💻 Technical Criteria
Given
Calculated total counter values exist as numeric fields
When
The system prepares totals for report display
Then
Each total value is formatted with leading zeros suppressed and right-justified in display fields
R-GCX146-cbl-01790
Initialize GCX019 Input Structure
Process Rules
📊 Business Logic Narrative
When the process 'Initialize GCX019 Input Structure' is invoked, and assuming that a broker notification needs to be sent, when the system prepares gcx019 input parameters, the desired outcome is that the gcx019 input structure is initialized with spaces and default values.
💻 Technical Criteria
Given
A broker notification needs to be sent
When
The system prepares GCX019 input parameters
Then
The GCX019 input structure is initialized with spaces and default values
R-GCX146-cbl-00432
Validate Bond Type
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Bond Type' is invoked, and assuming that bond type information has been extracted from the us route record, when the system validates the bond type, the desired outcome is that the system confirms the bond type is valid for further processing or flags it as invalid.
💻 Technical Criteria
Given
Bond type information has been extracted from the US route record
When
The system validates the bond type
Then
The system confirms the bond type is valid for further processing or flags it as invalid
R-GCX146-cbl-00433
Check Bond Types: IT/TR/TE/MT
Decision Rules
📊 Business Logic Narrative
When the process 'Check Bond Types: IT/TR/TE/MT' is invoked, and assuming that a valid bond type has been identified from the us route record, when the bond type is it (in-transit), tr (transportation), te (temporary export), or mt (merchandise transfer), the desired outcome is that the system applies specific processing rules and validations appropriate for each bond type.
💻 Technical Criteria
Given
A valid bond type has been identified from the US route record
When
The bond type is IT (In-Transit), TR (Transportation), TE (Temporary Export), or MT (Merchandise Transfer)
Then
The system applies specific processing rules and validations appropriate for each bond type
R-GCX146-cbl-00447
Generate Error Message
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error Message' is invoked, and assuming that invalid bond type, location information, or other critical data has been detected, when the system encounters validation failures, the desired outcome is that the system generates appropriate error messages indicating the specific validation failure.
💻 Technical Criteria
Given
Invalid bond type, location information, or other critical data has been detected
When
The system encounters validation failures
Then
The system generates appropriate error messages indicating the specific validation failure
R-GCX146-cbl-00449
Set Security Byte to HIGH-VALUES
Process Rules
📊 Business Logic Narrative
When the process 'Set Security Byte to HIGH-VALUES' is invoked, and assuming that a special manifest processing request is initiated, when the system begins special manifest creation, the desired outcome is that the security byte must be set to high-values to ensure maximum security level.
💻 Technical Criteria
Given
A special manifest processing request is initiated
When
The system begins special manifest creation
Then
The security byte must be set to HIGH-VALUES to ensure maximum security level
R-GCX146-cbl-00463
Initialize Customer Report Message
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Customer Report Message' is invoked, and assuming that a customer report generation request is initiated, when the system begins customer report processing, the desired outcome is that the customer report message structure is initialized with default values and proper message formatting.
💻 Technical Criteria
Given
A customer report generation request is initiated
When
The system begins customer report processing
Then
The customer report message structure is initialized with default values and proper message formatting
R-GCX146-cbl-00605
Validate Bond Type
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Bond Type' is invoked, and assuming that bond type information has been extracted from us route record, when system validates the bond type, the desired outcome is that bond type must be it (in-transit), tr (transportation), te (temporary export), or mt (merchandise in transit) to be considered valid.
💻 Technical Criteria
Given
Bond type information has been extracted from US Route record
When
System validates the bond type
Then
Bond type must be IT (In-Transit), TR (Transportation), TE (Temporary Export), or MT (Merchandise in Transit) to be considered valid
R-GCX146-cbl-00606
Bond Type Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Bond Type Valid?' is invoked, and assuming that bond type has been validated against acceptable types, when system evaluates bond type validity, the desired outcome is that processing continues with in-transit status check if valid, or generates bond type warning if invalid.
💻 Technical Criteria
Given
Bond type has been validated against acceptable types
When
System evaluates bond type validity
Then
Processing continues with in-transit status check if valid, or generates bond type warning if invalid
R-GCX146-cbl-01365
Initialize Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Message Buffer' is invoked, and assuming that a merlin message needs to be prepared for transmission, when the message preparation process begins, the desired outcome is that the message buffer is cleared and initialized with default values.
💻 Technical Criteria
Given
A Merlin message needs to be prepared for transmission
When
The message preparation process begins
Then
The message buffer is cleared and initialized with default values
R-GCX146-cbl-01823
Check GCSTBRT-AD-AUTO-FAX Setting
Validation Rules
📊 Business Logic Narrative
When the process 'Check GCSTBRT-AD-AUTO-FAX Setting' is invoked, and assuming that a station configuration record exists in gcstbrt, when the system checks the auto-fax setting in the station configuration, the desired outcome is that the system reads the gcstbrt-ad-auto-fax field value to determine if auto-fax is enabled.
💻 Technical Criteria
Given
A station configuration record exists in GCSTBRT
When
The system checks the Auto-FAX setting in the station configuration
Then
The system reads the GCSTBRT-AD-AUTO-FAX field value to determine if Auto-FAX is enabled
R-GCX146-cbl-01825
Check GCSTBRT-SC-FAX-FLAG
Validation Rules
📊 Business Logic Narrative
When the process 'Check GCSTBRT-SC-FAX-FLAG' is invoked, and assuming that auto-fax is enabled with setting 'y', when the system checks the fax flag configuration, the desired outcome is that the system reads the gcstbrt-sc-fax-flag field value.
💻 Technical Criteria
Given
Auto-FAX is enabled with setting 'Y'
When
The system checks the FAX flag configuration
Then
The system reads the GCSTBRT-SC-FAX-FLAG field value
R-GCX146-cbl-00914
Bond Created = Y?
Decision Rules
📊 Business Logic Narrative
When the process 'Bond Created = Y?' is invoked, and assuming that the bond creation flag has been checked, when the system evaluates if the bond created flag equals 'y', the desired outcome is that the system routes processing based on whether a new bond has been created.
💻 Technical Criteria
Given
The bond creation flag has been checked
When
The system evaluates if the bond created flag equals 'Y'
Then
The system routes processing based on whether a new bond has been created
R-GCX146-cbl-00931
Initialize Customer Report Message
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Customer Report Message' is invoked, and assuming that a customer report generation request is received, when the system begins customer report database operations, the desired outcome is that the customer report message structure is initialized with default values.
💻 Technical Criteria
Given
A customer report generation request is received
When
The system begins customer report database operations
Then
The customer report message structure is initialized with default values
📍 Routing, Border & Port
219 logic blocks
R-GCX146-cbl-00006
6:Merlin ID Management
Validation Rules
📊 Business Logic Narrative
When the process '6:Merlin ID Management' is invoked, and assuming that a train manifest request requires merlin communication capabilities, when the system validates merlin id configurations, the desired outcome is that public, supervisor, customs, dc-p, and system fax merlin ids must all exist in emtz table; missing ids generate specific errors (4-8, 29).
💻 Technical Criteria
Given
A train manifest request requires Merlin communication capabilities
When
The system validates Merlin ID configurations
Then
Public, Supervisor, Customs, DC-P, and System FAX Merlin IDs must all exist in EMTZ table; missing IDs generate specific errors (4-8, 29)
R-GCX146-cbl-00007
7:Train ID Construction
Definitional Rules
📊 Business Logic Narrative
When the process '7:Train ID Construction' is invoked, and assuming that train identification components are provided in the input, when the system constructs the customs train id, the desired outcome is that spaces in train number, day, from/to stations, and consist number are replaced with zeros to create a standardized format.
💻 Technical Criteria
Given
Train identification components are provided in the input
When
The system constructs the customs train ID
Then
Spaces in train number, day, from/to stations, and consist number are replaced with zeros to create a standardized format
R-GCX146-cbl-00008
8:Station Information Validation
Validation Rules
📊 Business Logic Narrative
When the process '8:Station Information Validation' is invoked, and assuming that train manifest contains origin and destination station codes, when the system validates station information, the desired outcome is that station codes must exist in the station master data and associated station names and routing information must be retrievable.
💻 Technical Criteria
Given
Train manifest contains origin and destination station codes
When
The system validates station information
Then
Station codes must exist in the station master data and associated station names and routing information must be retrievable
R-GCX146-cbl-00027
28:Email/FAX Distribution
Action Rules
📊 Business Logic Narrative
When the process '28:Email/FAX Distribution' is invoked, and assuming that reports or notifications need to be distributed electronically, when the system processes email and fax distribution, the desired outcome is that email messages are limited to 699 lines per message; larger reports create continuation messages with 'continuation of report...' header; failed emails are sent to support team (om01247, aei9999).
💻 Technical Criteria
Given
Reports or notifications need to be distributed electronically
When
The system processes email and FAX distribution
Then
Email messages are limited to 699 lines per message; larger reports create continuation messages with 'CONTINUATION OF REPORT...' header; failed emails are sent to support team (OM01247, AEI9999)
R-GCX146-cbl-00045
Extract SCAC Code from Customs Train ID
Process Rules
📊 Business Logic Narrative
When the process 'Extract SCAC Code from Customs Train ID' is invoked, and assuming that a customs train id is provided in the request, when scac validation is performed, the desired outcome is that the scac code is extracted from the customs train id for authorization verification.
💻 Technical Criteria
Given
A customs train ID is provided in the request
When
SCAC validation is performed
Then
The SCAC code is extracted from the customs train ID for authorization verification
R-GCX146-cbl-00055
Set INVALID-INPUT-FLAG
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set INVALID-INPUT-FLAG', assuming that an input message is received for processing, when the request type is not add, verify, or notify, the desired outcome is that the system sets the invalid-input-flag to indicate unsupported request type.
💻 Technical Criteria
EXCLUDING
An input message is received for processing
When
The request type is not ADD, VERIFY, or NOTIFY
Then
The system sets the INVALID-INPUT-FLAG to indicate unsupported request type
R-GCX146-cbl-00081
CUSTOMS ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'CUSTOMS ID Valid?' is invoked, and assuming that the customs merlin id needs validation and the supervisor merlin id validation has passed, when the system validates the customs merlin id against the emtz database, the desired outcome is that if the customs merlin id exists in emtz database, validation passes, otherwise validation fails with error 6.
💻 Technical Criteria
Given
The CUSTOMS Merlin ID needs validation AND the SUPERVISOR Merlin ID validation has passed
When
The system validates the CUSTOMS Merlin ID against the EMTZ database
Then
If the CUSTOMS Merlin ID exists in EMTZ database, validation passes, otherwise validation fails with error 6
R-GCX146-cbl-00082
DC-P ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'DC-P ID Valid?' is invoked, and assuming that a dc-p merlin id has been extracted from the admin table and the customs merlin id validation has passed, when the system validates the dc-p merlin id against the emtz database, the desired outcome is that if the dc-p merlin id exists in emtz database, validation passes, otherwise validation fails with error 7.
💻 Technical Criteria
Given
A DC-P Merlin ID has been extracted from the admin table AND the CUSTOMS Merlin ID validation has passed
When
The system validates the DC-P Merlin ID against the EMTZ database
Then
If the DC-P Merlin ID exists in EMTZ database, validation passes, otherwise validation fails with error 7
R-GCX146-cbl-00084
All Merlin IDs Successfully Validated
Process Rules
📊 Business Logic Narrative
When the process 'All Merlin IDs Successfully Validated' is invoked, and assuming that all five merlin ids (public, supervisor, customs, dc-p, system-fax) have been extracted from their respective tables, when all merlin id validations against the emtz database have been completed successfully, the desired outcome is that the system proceeds with customs reporting operations using the validated communication channels.
💻 Technical Criteria
Given
All five Merlin IDs (PUBLIC, SUPERVISOR, CUSTOMS, DC-P, SYSTEM-FAX) have been extracted from their respective tables
When
All Merlin ID validations against the EMTZ database have been completed successfully
Then
The system proceeds with customs reporting operations using the validated communication channels
R-GCX146-cbl-00085
Merlin ID Validation Failed
Process Rules
📊 Business Logic Narrative
When the process 'Merlin ID Validation Failed' is invoked, and assuming that one or more merlin ids are being validated against the emtz database, when any merlin id validation fails (public, supervisor, customs, dc-p, or system-fax), the desired outcome is that the system stops the validation process and reports the specific validation error without proceeding to customs reporting operations.
💻 Technical Criteria
Given
One or more Merlin IDs are being validated against the EMTZ database
When
Any Merlin ID validation fails (PUBLIC, SUPERVISOR, CUSTOMS, DC-P, or SYSTEM-FAX)
Then
The system stops the validation process and reports the specific validation error without proceeding to customs reporting operations
R-GCX146-cbl-00091
Get System Date
Process Rules
📊 Business Logic Narrative
When the process 'Get System Date' is invoked, and assuming that a train id construction request is being processed, when the system needs to build the customs train id, the desired outcome is that the current system date is retrieved and stored for inclusion in the train id.
💻 Technical Criteria
Given
A train ID construction request is being processed
When
The system needs to build the customs train ID
Then
The current system date is retrieved and stored for inclusion in the train ID
R-GCX146-cbl-00093
Construct WS-CUSTOMS-TRAIN-ID
Computation Rules
📊 Business Logic Narrative
When the process 'Construct WS-CUSTOMS-TRAIN-ID' is invoked, and assuming that all train id components have been extracted and spaces replaced with zeros, when the system constructs the customs train id, the desired outcome is that the customs train id is built by concatenating train number, day, from station, to station, consist number, and system date.
💻 Technical Criteria
Given
All train ID components have been extracted and spaces replaced with zeros
When
The system constructs the customs train ID
Then
The customs train ID is built by concatenating train number, day, from station, to station, consist number, and system date
R-GCX146-cbl-00094
Build GCWB4TL-CP-TRAIN-ID
Computation Rules
📊 Business Logic Narrative
When the process 'Build GCWB4TL-CP-TRAIN-ID' is invoked, and assuming that the customs train id has been constructed, when the system needs to create the cp train id, the desired outcome is that the gcwb4tl-cp-train-id is built using the standardized customs train id format.
💻 Technical Criteria
Given
The customs train ID has been constructed
When
The system needs to create the CP train ID
Then
The GCWB4TL-CP-TRAIN-ID is built using the standardized customs train ID format
R-GCX146-cbl-00095
Validate Train ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Train ID Format' is invoked, and assuming that the customs train id and cp train id have been constructed, when the system validates the train id format, the desired outcome is that the train id format is checked against business requirements and validation rules.
💻 Technical Criteria
Given
The customs train ID and CP train ID have been constructed
When
The system validates the train ID format
Then
The train ID format is checked against business requirements and validation rules
R-GCX146-cbl-00277
Log EDI Transmission Status
Process Rules
📊 Business Logic Narrative
When the process 'Log EDI Transmission Status' is invoked, and assuming that edi data has been transmitted to customs, when the system completes the transmission process, the desired outcome is that the transmission status is logged for audit and monitoring purposes.
💻 Technical Criteria
Given
EDI data has been transmitted to customs
When
The system completes the transmission process
Then
The transmission status is logged for audit and monitoring purposes
R-GCX146-cbl-00279
Retrieve Email User Lists from Station Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Email User Lists from Station Configuration' is invoked, and assuming that an aei train send process is initiated for a specific station, when the system needs to determine email recipients for the aei report, the desired outcome is that the system retrieves email user lists from station configuration tables (gcstbrt and aecwrktb) based on the station code.
💻 Technical Criteria
Given
An AEI train send process is initiated for a specific station
When
The system needs to determine email recipients for the AEI report
Then
The system retrieves email user lists from station configuration tables (GCSTBRT and AECWRKTB) based on the station code
R-GCX146-cbl-00281
Report > 699 Lines?
Decision Rules
📊 Business Logic Narrative
When the process 'Report > 699 Lines?' is invoked, and assuming that an aei report has been prepared for email transmission, when the report contains more than 699 lines, the desired outcome is that the system activates continuation logic to split the report into multiple email messages.
💻 Technical Criteria
Given
An AEI report has been prepared for email transmission
When
The report contains more than 699 lines
Then
The system activates continuation logic to split the report into multiple email messages
R-GCX146-cbl-00282
Prepare Standard AEI Report
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Standard AEI Report' is invoked, and assuming that an aei report contains 699 lines or fewer, when the system prepares the report for email transmission, the desired outcome is that the system formats the report as a single email message without continuation headers.
💻 Technical Criteria
Given
An AEI report contains 699 lines or fewer
When
The system prepares the report for email transmission
Then
The system formats the report as a single email message without continuation headers
R-GCX146-cbl-00283
Prepare Report with Continuation Logic
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Report with Continuation Logic' is invoked, and assuming that an aei report contains more than 699 lines, when the system prepares the report for email transmission, the desired outcome is that the system splits the report into batches of 699 lines or fewer with continuation headers.
💻 Technical Criteria
Given
An AEI report contains more than 699 lines
When
The system prepares the report for email transmission
Then
The system splits the report into batches of 699 lines or fewer with continuation headers
R-GCX146-cbl-00284
Send Current Report Batch
Action Rules
📊 Business Logic Narrative
When the process 'Send Current Report Batch' is invoked, and assuming that a batch of aei report data has been prepared for transmission, when the system processes the current batch, the desired outcome is that the system transmits the batch via emcsend3 email service to the configured recipients.
💻 Technical Criteria
Given
A batch of AEI report data has been prepared for transmission
When
The system processes the current batch
Then
The system transmits the batch via EMCSEND3 email service to the configured recipients
R-GCX146-cbl-00285
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that a batch of aei report data has been successfully sent, when the system prepares for the next batch of data, the desired outcome is that the system clears the message buffer and resets line counters for the next batch.
💻 Technical Criteria
Given
A batch of AEI report data has been successfully sent
When
The system prepares for the next batch of data
Then
The system clears the message buffer and resets line counters for the next batch
R-GCX146-cbl-00286
Add Continuation Header
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header' is invoked, and assuming that an aei report requires multiple email messages due to size, when the system prepares a continuation batch after the first message, the desired outcome is that the system adds the header 'continuation of report....' to identify the message as a continuation.
💻 Technical Criteria
Given
An AEI report requires multiple email messages due to size
When
The system prepares a continuation batch after the first message
Then
The system adds the header 'CONTINUATION OF REPORT....' to identify the message as a continuation
R-GCX146-cbl-00287
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that a batch of aei report data has been processed, when the system checks for remaining report content, the desired outcome is that the system determines if more lines exist that require additional batch processing.
💻 Technical Criteria
Given
A batch of AEI report data has been processed
When
The system checks for remaining report content
Then
The system determines if more lines exist that require additional batch processing
R-GCX146-cbl-00288
Process Next Batch
Process Rules
📊 Business Logic Narrative
When the process 'Process Next Batch' is invoked, and assuming that additional lines remain in the aei report after sending a batch, when the system processes the next batch, the desired outcome is that the system prepares up to 699 lines for the next email message with appropriate continuation headers.
💻 Technical Criteria
Given
Additional lines remain in the AEI report after sending a batch
When
The system processes the next batch
Then
The system prepares up to 699 lines for the next email message with appropriate continuation headers
R-GCX146-cbl-00289
Send AEI Report via EMCSEND3
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Report via EMCSEND3' is invoked, and assuming that an aei report batch has been prepared for transmission, when the system initiates email transmission, the desired outcome is that the system calls emcsend3 service to deliver the report to the configured email recipients.
💻 Technical Criteria
Given
An AEI report batch has been prepared for transmission
When
The system initiates email transmission
Then
The system calls EMCSEND3 service to deliver the report to the configured email recipients
R-GCX146-cbl-00290
Email Send Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Send Successful?' is invoked, and assuming that an aei report has been sent via emcsend3 email service, when the system receives the transmission response, the desired outcome is that the system evaluates the response to determine if the email was successfully delivered.
💻 Technical Criteria
Given
An AEI report has been sent via EMCSEND3 email service
When
The system receives the transmission response
Then
The system evaluates the response to determine if the email was successfully delivered
R-GCX146-cbl-00291
Use Fallback Email Recipients
Process Rules
📊 Business Logic Narrative
When the process 'Use Fallback Email Recipients' is invoked, and assuming that the primary aei report email transmission has failed, when the system needs to ensure report delivery, the desired outcome is that the system configures fallback recipients (om01247 and aei9999) for report transmission.
💻 Technical Criteria
Given
The primary AEI report email transmission has failed
When
The system needs to ensure report delivery
Then
The system configures fallback recipients (OM01247 and AEI9999) for report transmission
R-GCX146-cbl-00292
Send to OM01247/AEI9999
Action Rules
📊 Business Logic Narrative
When the process 'Send to OM01247/AEI9999' is invoked, and assuming that primary aei report email transmission has failed, when the system uses fallback recipients, the desired outcome is that the system sends the aei report to om01247 and aei9999 as backup recipients.
💻 Technical Criteria
Given
Primary AEI report email transmission has failed
When
The system uses fallback recipients
Then
The system sends the AEI report to OM01247 and AEI9999 as backup recipients
R-GCX146-cbl-00293
Handle Email Failure
Process Rules
📊 Business Logic Narrative
When the process 'Handle Email Failure' is invoked, and assuming that an aei report email transmission has failed, when the system processes the failure, the desired outcome is that the system logs the failure and initiates fallback transmission procedures.
💻 Technical Criteria
Given
An AEI report email transmission has failed
When
The system processes the failure
Then
The system logs the failure and initiates fallback transmission procedures
R-GCX146-cbl-00298
Create Error Confirmation Message
Action Rules
📊 Business Logic Narrative
When the process 'Create Error Confirmation Message' is invoked, and assuming that train processing has failed due to validation errors or system issues, when the system creates a confirmation message, the desired outcome is that the system generates either a gct1011e error message or customer report message depending on the error type.
💻 Technical Criteria
Given
Train processing has failed due to validation errors or system issues
When
The system creates a confirmation message
Then
The system generates either a GCT1011E error message or customer report message depending on the error type
R-GCX146-cbl-00309
Handle Message Errors
Decision Rules
📊 Business Logic Narrative
When the process 'Handle Message Errors' is invoked, and assuming that message processing encounters an error condition, when the system handles message errors, the desired outcome is that the system identifies the error type (invalid parameters, queue full, or system error) and routes to appropriate error handling procedures.
💻 Technical Criteria
Given
Message processing encounters an error condition
When
The system handles message errors
Then
The system identifies the error type (invalid parameters, queue full, or system error) and routes to appropriate error handling procedures
R-GCX146-cbl-00310
Initialize Trip Sheet Header
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Trip Sheet Header' is invoked, and assuming that a canada customs trip sheet needs to be generated, when the trip sheet generation process begins, the desired outcome is that the header structure is initialized with proper formatting and line counters are reset.
💻 Technical Criteria
Given
A Canada Customs trip sheet needs to be generated
When
The trip sheet generation process begins
Then
The header structure is initialized with proper formatting and line counters are reset
R-GCX146-cbl-00311
Set Report Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Set Report Parameters' is invoked, and assuming that trip sheet header has been initialized, when report parameters need to be established, the desired outcome is that maximum line limits are set and report formatting parameters are configured.
💻 Technical Criteria
Given
Trip sheet header has been initialized
When
Report parameters need to be established
Then
Maximum line limits are set and report formatting parameters are configured
R-GCX146-cbl-00312
Format Train Information
Computation Rules
📊 Business Logic Narrative
When the process 'Format Train Information' is invoked, and assuming that train data is available for processing, when train information needs to be formatted for the trip sheet, the desired outcome is that train id, date, and customs train id are formatted and added to the report header.
💻 Technical Criteria
Given
Train data is available for processing
When
Train information needs to be formatted for the trip sheet
Then
Train ID, date, and customs train ID are formatted and added to the report header
R-GCX146-cbl-00313
Add Station Details
Computation Rules
📊 Business Logic Narrative
When the process 'Add Station Details' is invoked, and assuming that train information has been formatted, when station details need to be added to the trip sheet, the desired outcome is that from station, to station, and route information are formatted and included in the header.
💻 Technical Criteria
Given
Train information has been formatted
When
Station details need to be added to the trip sheet
Then
From station, to station, and route information are formatted and included in the header
R-GCX146-cbl-00325
Format Final Report
Process Rules
📊 Business Logic Narrative
When the process 'Format Final Report' is invoked, and assuming that summary totals have been added to the trip sheet, when final report formatting is required, the desired outcome is that the complete trip sheet is formatted with proper spacing, headers, and structure for final output.
💻 Technical Criteria
Given
Summary totals have been added to the trip sheet
When
Final report formatting is required
Then
The complete trip sheet is formatted with proper spacing, headers, and structure for final output
R-GCX146-cbl-00326
Trip Sheet Complete
Process Rules
📊 Business Logic Narrative
When the process 'Trip Sheet Complete' is invoked, and assuming that final report formatting has been completed, when trip sheet generation process concludes, the desired outcome is that the completed canada customs trip sheet is ready for distribution and the generation process is marked as complete.
💻 Technical Criteria
Given
Final report formatting has been completed
When
Trip sheet generation process concludes
Then
The completed Canada Customs trip sheet is ready for distribution and the generation process is marked as complete
R-GCX146-cbl-01254
Initialize Trip Sheet Header Fields
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Trip Sheet Header Fields' is invoked, and assuming that a trip sheet report needs to be generated, when the system begins trip sheet header generation, the desired outcome is that all header fields are cleared and initialized to spaces or zeros.
💻 Technical Criteria
Given
A trip sheet report needs to be generated
When
The system begins trip sheet header generation
Then
All header fields are cleared and initialized to spaces or zeros
R-GCX146-cbl-01257
Build Customs Train ID
Computation Rules
📊 Business Logic Narrative
When the process 'Build Customs Train ID' is invoked, and assuming that individual train components have been formatted, when the system builds the customs train id, the desired outcome is that the customs train id is constructed by concatenating train number, day, from station, to station, and consist number.
💻 Technical Criteria
Given
Individual train components have been formatted
When
The system builds the customs train ID
Then
The customs train ID is constructed by concatenating train number, day, from station, to station, and consist number
R-GCX146-cbl-01259
Capture Current System Date
Computation Rules
📊 Business Logic Narrative
When the process 'Capture Current System Date' is invoked, and assuming that a trip sheet report is being generated, when the system needs to timestamp the report, the desired outcome is that current system date and time are captured and formatted for report display.
💻 Technical Criteria
Given
A trip sheet report is being generated
When
The system needs to timestamp the report
Then
Current system date and time are captured and formatted for report display
R-GCX146-cbl-01260
Set Report Type Indicator
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Report Type Indicator' is invoked, and assuming that a trip sheet report is being generated, when the system sets report identification, the desired outcome is that report type indicator is set to identify this as a trip sheet report.
💻 Technical Criteria
Given
A trip sheet report is being generated
When
The system sets report identification
Then
Report type indicator is set to identify this as a trip sheet report
R-GCX146-cbl-01262
Set Page Number and Line Counter
Process Rules
📊 Business Logic Narrative
When the process 'Set Page Number and Line Counter' is invoked, and assuming that a trip sheet report is being generated, when the system sets up report pagination, the desired outcome is that page number is set to 1 and line counter is initialized to track report lines.
💻 Technical Criteria
Given
A trip sheet report is being generated
When
The system sets up report pagination
Then
Page number is set to 1 and line counter is initialized to track report lines
R-GCX146-cbl-01263
Set Canadian Customs Header Text
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Canadian Customs Header Text' is invoked, and assuming that a trip sheet report is for canadian customs, when the system sets report headers, the desired outcome is that canadian customs header text and report title are set with appropriate description.
💻 Technical Criteria
Given
A trip sheet report is for Canadian customs
When
The system sets report headers
Then
Canadian customs header text and report title are set with appropriate description
R-GCX146-cbl-01475
Build WS-CUSTOMS-TRAIN-ID
Computation Rules
📊 Business Logic Narrative
When the process 'Build WS-CUSTOMS-TRAIN-ID' is invoked, and assuming that all train components have been extracted and formatted with spaces replaced by zeros, when building the customs train id, the desired outcome is that the customs train id is constructed by concatenating train number, train day, from station, to station, consist number, and system date components in sequence.
💻 Technical Criteria
Given
All train components have been extracted and formatted with spaces replaced by zeros
When
Building the customs train ID
Then
The customs train ID is constructed by concatenating train number, train day, from station, to station, consist number, and system date components in sequence
R-GCX146-cbl-01476
Build GCWB4TL-CP-TRAIN-ID
Computation Rules
📊 Business Logic Narrative
When the process 'Build GCWB4TL-CP-TRAIN-ID' is invoked, and assuming that all train components have been extracted and formatted with spaces replaced by zeros, when building the cp train id, the desired outcome is that the cp train id is constructed using the same concatenated components as the customs train id.
💻 Technical Criteria
Given
All train components have been extracted and formatted with spaces replaced by zeros
When
Building the CP train ID
Then
The CP train ID is constructed using the same concatenated components as the customs train ID
R-GCX146-cbl-01632
Validate Load Status Requirements
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Load Status Requirements' is invoked, and assuming that load status flag has been set based on origin/destination analysis, when system validates load status against business requirements, the desired outcome is that load status is determined as valid or invalid for further processing.
💻 Technical Criteria
Given
Load status flag has been set based on origin/destination analysis
When
System validates load status against business requirements
Then
Load status is determined as valid or invalid for further processing
R-GCX146-cbl-01292
Report Total Calculation Error
Decision Rules
📊 Business Logic Narrative
When the process 'Report Total Calculation Error' is invoked, and assuming that total calculations have been validated and found to be inconsistent, when the validation fails, the desired outcome is that an error message is generated indicating total calculation inconsistency and the summary generation continues with available totals.
💻 Technical Criteria
Given
Total calculations have been validated and found to be inconsistent
When
The validation fails
Then
An error message is generated indicating total calculation inconsistency and the summary generation continues with available totals
R-GCX146-cbl-00342
Set Error Code in WS-ERROR-NB
Action Rules
📊 Business Logic Narrative
When the process 'Set Error Code in WS-ERROR-NB' is invoked, and assuming that a processing error has been detected during train processing, when the system identifies the specific type of error that occurred, the desired outcome is that the system assigns the corresponding error code to ws-error-nb for tracking and reporting purposes.
💻 Technical Criteria
Given
A processing error has been detected during train processing
When
The system identifies the specific type of error that occurred
Then
The system assigns the corresponding error code to WS-ERROR-NB for tracking and reporting purposes
R-GCX146-cbl-00358
Check Station Configuration
Validation Rules
📊 Business Logic Narrative
When the process 'Check Station Configuration' is invoked, and assuming that a station configuration exists for the current station, when the system needs to determine distribution methods for reports, the desired outcome is that the system should identify if auto-fax is enabled for the station.
💻 Technical Criteria
Given
A station configuration exists for the current station
When
The system needs to determine distribution methods for reports
Then
The system should identify if auto-FAX is enabled for the station
R-GCX146-cbl-00362
Email Users Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Users Found?' is invoked, and assuming that email user lookup has been performed, when email addresses are found for the station, the desired outcome is that the system should proceed with aei report email distribution, otherwise proceed to merlin transmission.
💻 Technical Criteria
Given
Email user lookup has been performed
When
Email addresses are found for the station
Then
The system should proceed with AEI report email distribution, otherwise proceed to Merlin transmission
R-GCX146-cbl-00363
Send AEI Report via Email
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Report via Email' is invoked, and assuming that valid email users exist for the station, when aei report needs to be distributed, the desired outcome is that the system should send the report via email using emcsend3 utility.
💻 Technical Criteria
Given
Valid email users exist for the station
When
AEI report needs to be distributed
Then
The system should send the report via email using EMCSEND3 utility
R-GCX146-cbl-00364
Report Size > 699 Lines?
Validation Rules
📊 Business Logic Narrative
When the process 'Report Size > 699 Lines?' is invoked, and assuming that an aei report is being prepared for email distribution, when the report contains more than 699 lines, the desired outcome is that the system should split the report and send with continuation headers, otherwise send as complete report.
💻 Technical Criteria
Given
An AEI report is being prepared for email distribution
When
The report contains more than 699 lines
Then
The system should split the report and send with continuation headers, otherwise send as complete report
R-GCX146-cbl-00365
Send Complete Report
Process Rules
📊 Business Logic Narrative
When the process 'Send Complete Report' is invoked, and assuming that report size is 699 lines or fewer, when email distribution is initiated, the desired outcome is that the system should send the complete report in a single email message.
💻 Technical Criteria
Given
Report size is 699 lines or fewer
When
Email distribution is initiated
Then
The system should send the complete report in a single email message
R-GCX146-cbl-00366
Send Report with Continuation
Process Rules
📊 Business Logic Narrative
When the process 'Send Report with Continuation' is invoked, and assuming that report size exceeds 699 lines, when email distribution is initiated, the desired outcome is that the system should split the report and prepare continuation messages.
💻 Technical Criteria
Given
Report size exceeds 699 lines
When
Email distribution is initiated
Then
The system should split the report and prepare continuation messages
R-GCX146-cbl-00367
Add Continuation Header
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header' is invoked, and assuming that a report is being split into multiple email messages, when continuation messages are created, the desired outcome is that the system should add 'continuation of report....' header to each continuation message.
💻 Technical Criteria
Given
A report is being split into multiple email messages
When
Continuation messages are created
Then
The system should add 'CONTINUATION OF REPORT....' header to each continuation message
R-GCX146-cbl-00368
Send Remaining Lines
Process Rules
📊 Business Logic Narrative
When the process 'Send Remaining Lines' is invoked, and assuming that continuation header has been added, when remaining report lines need to be sent, the desired outcome is that the system should send the remaining lines in subsequent email messages with proper headers.
💻 Technical Criteria
Given
Continuation header has been added
When
Remaining report lines need to be sent
Then
The system should send the remaining lines in subsequent email messages with proper headers
R-GCX146-cbl-00371
Send to OM01247/AEI9999
Action Rules
📊 Business Logic Narrative
When the process 'Send to OM01247/AEI9999' is invoked, and assuming that fallback email has been configured, when report needs to be delivered despite email failure, the desired outcome is that the system should send the report to support team addresses om01247 and aei9999.
💻 Technical Criteria
Given
Fallback email has been configured
When
Report needs to be delivered despite email failure
Then
The system should send the report to support team addresses OM01247 and AEI9999
R-GCX146-cbl-00376
Send via Merlin System
Action Rules
📊 Business Logic Narrative
When the process 'Send via Merlin System' is invoked, and assuming that merlin transmission is configured and copy ids are set if needed, when report distribution via merlin is initiated, the desired outcome is that the system should send the report through merlin messaging system.
💻 Technical Criteria
Given
Merlin transmission is configured and copy IDs are set if needed
When
Report distribution via Merlin is initiated
Then
The system should send the report through Merlin messaging system
R-GCX146-cbl-00392
Transmit via Merlin Communication
Action Rules
📊 Business Logic Narrative
When the process 'Transmit via Merlin Communication' is invoked, and assuming that trip sheet data is properly formatted and sized for transmission, when the system initiates transmission via merlin, the desired outcome is that trip sheet data is sent through merlin communication system to designated us customs recipients.
💻 Technical Criteria
Given
Trip sheet data is properly formatted and sized for transmission
When
The system initiates transmission via Merlin
Then
Trip sheet data is sent through Merlin communication system to designated US customs recipients
R-GCX146-cbl-00400
Send Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Notification' is invoked, and assuming that an arrival notice transaction has been generated, when the system sends the notification, the desired outcome is that the gct1481e transaction is queued for transmission to customs processing system.
💻 Technical Criteria
Given
An arrival notice transaction has been generated
When
The system sends the notification
Then
The GCT1481E transaction is queued for transmission to customs processing system
R-GCX146-cbl-01802
Parameter Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Parameter Error', assuming that gcx019 parameters are being validated, when required fields are missing or contain invalid data, the desired outcome is that the system reports parameter error and does not proceed with broker notification.
💻 Technical Criteria
EXCLUDING
GCX019 parameters are being validated
When
Required fields are missing or contain invalid data
Then
The system reports parameter error and does not proceed with broker notification
R-GCX146-cbl-01658
Set FAX Routing Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Set FAX Routing Parameters' is invoked, and assuming that fax message content is prepared, when the system sets fax routing parameters, the desired outcome is that the system should configure transmission settings including destination fax number and routing information.
💻 Technical Criteria
Given
FAX message content is prepared
When
The system sets FAX routing parameters
Then
The system should configure transmission settings including destination FAX number and routing information
R-GCX146-cbl-01805
Set FAX Routing Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Set FAX Routing Parameters' is invoked, and assuming that auto-fax is enabled for the current operation, when the system sets up fax routing parameters, the desired outcome is that the system should configure destination routing, delivery options, and transmission parameters for the fax.
💻 Technical Criteria
Given
Auto-FAX is enabled for the current operation
When
The system sets up FAX routing parameters
Then
The system should configure destination routing, delivery options, and transmission parameters for the FAX
R-GCX146-cbl-00430
US Route Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'US Route Record Found?' is invoked, and assuming that the system has attempted to retrieve a us route record from gcsusrt database, when the database lookup is completed, the desired outcome is that the system determines if a valid us route record was found and proceeds with appropriate processing path.
💻 Technical Criteria
Given
The system has attempted to retrieve a US route record from GCSUSRT database
When
The database lookup is completed
Then
The system determines if a valid US route record was found and proceeds with appropriate processing path
R-GCX146-cbl-00438
Check Vessel Name
Validation Rules
📊 Business Logic Narrative
When the process 'Check Vessel Name' is invoked, and assuming that valid location information has been confirmed, when the system checks the vessel name in the us route record, the desired outcome is that the system validates the vessel name for transportation mode consistency.
💻 Technical Criteria
Given
Valid location information has been confirmed
When
The system checks the vessel name in the US route record
Then
The system validates the vessel name for transportation mode consistency
R-GCX146-cbl-00439
Vessel = 'TRAIN'?
Decision Rules
📊 Business Logic Narrative
When the process 'Vessel = 'TRAIN'?' is invoked, and assuming that vessel name has been validated from the us route record, when the system checks if the vessel name equals 'train', the desired outcome is that the system determines the transportation mode and applies train-specific or other vessel processing rules.
💻 Technical Criteria
Given
Vessel name has been validated from the US route record
When
The system checks if the vessel name equals 'TRAIN'
Then
The system determines the transportation mode and applies train-specific or other vessel processing rules
R-GCX146-cbl-00440
Generate Train-Specific Status
Process Rules
📊 Business Logic Narrative
When the process 'Generate Train-Specific Status' is invoked, and assuming that the vessel has been identified as 'train', when the system generates customs status, the desired outcome is that the system creates train-specific status information with appropriate customs codes and descriptions.
💻 Technical Criteria
Given
The vessel has been identified as 'TRAIN'
When
The system generates customs status
Then
The system creates train-specific status information with appropriate customs codes and descriptions
R-GCX146-cbl-00441
Generate Other Vessel Status
Process Rules
📊 Business Logic Narrative
When the process 'Generate Other Vessel Status' is invoked, and assuming that the vessel has been identified as something other than 'train', when the system generates customs status, the desired outcome is that the system creates vessel-specific status information appropriate for the transportation mode.
💻 Technical Criteria
Given
The vessel has been identified as something other than 'TRAIN'
When
The system generates customs status
Then
The system creates vessel-specific status information appropriate for the transportation mode
R-GCX146-cbl-00448
Set Default Status
Process Rules
📊 Business Logic Narrative
When the process 'Set Default Status' is invoked, and assuming that no us route record was found or validation errors occurred, when the system needs to assign a status, the desired outcome is that the system sets a default status indicating no us customs information is available.
💻 Technical Criteria
Given
No US route record was found or validation errors occurred
When
The system needs to assign a status
Then
The system sets a default status indicating no US customs information is available
R-GCX146-cbl-00450
Set Record Type Code to 'CA'
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Record Type Code to 'CA'' is invoked, and assuming that a special manifest is being created for canadian customs processing, when the system sets the record type for the manifest, the desired outcome is that the record type code must be set to 'ca' to identify it as a canadian manifest.
💻 Technical Criteria
Given
A special manifest is being created for Canadian customs processing
When
The system sets the record type for the manifest
Then
The record type code must be set to 'CA' to identify it as a Canadian manifest
R-GCX146-cbl-00451
Extract Border Information from GCWB4TL
Action Rules
📊 Business Logic Narrative
When the process 'Extract Border Information from GCWB4TL' is invoked, and assuming that train data exists in gcwb4tl with border information, when special manifest processing requires border details, the desired outcome is that the system must extract border code and station name from the train data.
💻 Technical Criteria
Given
Train data exists in GCWB4TL with border information
When
Special manifest processing requires border details
Then
The system must extract border code and station name from the train data
R-GCX146-cbl-00464
Set Report Format to GCT1401E
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Report Format to GCT1401E' is invoked, and assuming that a customer report message is being prepared, when the system configures the report format, the desired outcome is that the report format is set to gct1401e transaction type for customer advice processing.
💻 Technical Criteria
Given
A customer report message is being prepared
When
The system configures the report format
Then
The report format is set to GCT1401E transaction type for customer advice processing
R-GCX146-cbl-00465
Configure Message Queue Routing
Process Rules
📊 Business Logic Narrative
When the process 'Configure Message Queue Routing' is invoked, and assuming that a customer report is ready for distribution, when the system configures message queue routing, the desired outcome is that the message routing is configured to use alt-pcb2 queue for proper customer report delivery.
💻 Technical Criteria
Given
A customer report is ready for distribution
When
The system configures message queue routing
Then
The message routing is configured to use ALT-PCB2 queue for proper customer report delivery
R-GCX146-cbl-00466
Move Report Content to Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Move Report Content to Message Buffer' is invoked, and assuming that customer report content is available in gcx140-input data structure, when the system prepares the report for transmission, the desired outcome is that the report content is moved to the message buffer for processing and distribution.
💻 Technical Criteria
Given
Customer report content is available in GCX140-INPUT data structure
When
The system prepares the report for transmission
Then
The report content is moved to the message buffer for processing and distribution
R-GCX146-cbl-00467
Execute CIMS CHNG Operation
Action Rules
📊 Business Logic Narrative
When the process 'Execute CIMS CHNG Operation' is invoked, and assuming that customer report message is prepared in the message buffer, when the system executes cims change operation, the desired outcome is that the cims chng operation is performed to process the customer report message.
💻 Technical Criteria
Given
Customer report message is prepared in the message buffer
When
The system executes CIMS change operation
Then
The CIMS CHNG operation is performed to process the customer report message
R-GCX146-cbl-00468
CHNG Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'CHNG Successful?' is invoked, and assuming that cims change operation has been executed for customer report, when the system checks the operation result, the desired outcome is that if cims change operation is successful, proceed to write message; otherwise handle error.
💻 Technical Criteria
Given
CIMS change operation has been executed for customer report
When
The system checks the operation result
Then
If CIMS change operation is successful, proceed to write message; otherwise handle error
R-GCX146-cbl-00469
Execute WRITMSGL Operation
Action Rules
📊 Business Logic Narrative
When the process 'Execute WRITMSGL Operation' is invoked, and assuming that cims change operation completed successfully, when the system executes write message operation, the desired outcome is that the writmsgl operation is performed to send the customer report message.
💻 Technical Criteria
Given
CIMS change operation completed successfully
When
The system executes write message operation
Then
The WRITMSGL operation is performed to send the customer report message
R-GCX146-cbl-00470
Write Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Write Successful?' is invoked, and assuming that write message operation has been executed for customer report, when the system checks the write operation result, the desired outcome is that if write operation is successful, proceed to purge operation; otherwise handle error.
💻 Technical Criteria
Given
Write message operation has been executed for customer report
When
The system checks the write operation result
Then
If write operation is successful, proceed to purge operation; otherwise handle error
R-GCX146-cbl-00471
Execute PURG Operation
Action Rules
📊 Business Logic Narrative
When the process 'Execute PURG Operation' is invoked, and assuming that customer report message has been successfully written to queue, when the system executes purge operation, the desired outcome is that the purg operation is performed to clean up the message queue.
💻 Technical Criteria
Given
Customer report message has been successfully written to queue
When
The system executes purge operation
Then
The PURG operation is performed to clean up the message queue
R-GCX146-cbl-00472
Purge Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Purge Successful?' is invoked, and assuming that purge operation has been executed for customer report message, when the system checks the purge operation result, the desired outcome is that if purge operation is successful, customer report generation is complete; otherwise handle error.
💻 Technical Criteria
Given
Purge operation has been executed for customer report message
When
The system checks the purge operation result
Then
If purge operation is successful, customer report generation is complete; otherwise handle error
R-GCX146-cbl-00473
Customer Report Generated Successfully
Process Rules
📊 Business Logic Narrative
When the process 'Customer Report Generated Successfully' is invoked, and assuming that all customer report operations (chng, writmsgl, purg) have completed successfully, when the system finalizes the customer report generation process, the desired outcome is that the customer report is marked as successfully generated and distributed.
💻 Technical Criteria
Given
All customer report operations (CHNG, WRITMSGL, PURG) have completed successfully
When
The system finalizes the customer report generation process
Then
The customer report is marked as successfully generated and distributed
R-GCX146-cbl-00474
Handle Report Generation Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Report Generation Error' is invoked, and assuming that an error occurs during customer report generation (chng, writmsgl, or purg operation fails), when the system detects the error condition, the desired outcome is that the error is handled appropriately and the customer report generation process is terminated.
💻 Technical Criteria
Given
An error occurs during customer report generation (CHNG, WRITMSGL, or PURG operation fails)
When
The system detects the error condition
Then
The error is handled appropriately and the customer report generation process is terminated
R-GCX146-cbl-00611
Vessel is 'TRAIN'?
Decision Rules
📊 Business Logic Narrative
When the process 'Vessel is 'TRAIN'?' is invoked, and assuming that vessel name has been extracted from the us route record, when system checks if vessel name equals 'train', the desired outcome is that processing continues normally if vessel is 'train', or generates vessel warning if vessel name indicates different transportation mode.
💻 Technical Criteria
Given
Vessel name has been extracted from the US Route record
When
System checks if vessel name equals 'TRAIN'
Then
Processing continues normally if vessel is 'TRAIN', or generates vessel warning if vessel name indicates different transportation mode
R-GCX146-cbl-00614
Generate Vessel Warning
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Vessel Warning', assuming that vessel name does not indicate 'train' transportation mode, when system generates vessel warning, the desired outcome is that warning message is created indicating vessel name inconsistency with rail transportation mode.
💻 Technical Criteria
EXCLUDING
Vessel name does not indicate 'TRAIN' transportation mode
When
System generates vessel warning
Then
Warning message is created indicating vessel name inconsistency with rail transportation mode
R-GCX146-cbl-00669
Get Email User Lists from Station Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Get Email User Lists from Station Configuration' is invoked, and assuming that an aei train send operation is being processed, when the system needs to determine email recipients for the aei report, the desired outcome is that the system retrieves email user lists from the station configuration database (gcstbrt) based on the train's station information.
💻 Technical Criteria
Given
An AEI train send operation is being processed
When
The system needs to determine email recipients for the AEI report
Then
The system retrieves email user lists from the station configuration database (GCSTBRT) based on the train's station information
R-GCX146-cbl-00670
Check Report Size
Validation Rules
📊 Business Logic Narrative
When the process 'Check Report Size' is invoked, and assuming that an aei report has been generated with content lines, when the system prepares to send the report via email, the desired outcome is that the system counts the total number of lines in the report to determine if special handling is required.
💻 Technical Criteria
Given
An AEI report has been generated with content lines
When
The system prepares to send the report via email
Then
The system counts the total number of lines in the report to determine if special handling is required
R-GCX146-cbl-00671
Report > 699 Lines?
Decision Rules
📊 Business Logic Narrative
When the process 'Report > 699 Lines?' is invoked, and assuming that an aei report has been sized and line count determined, when the report contains more than 699 lines, the desired outcome is that the system initiates large report processing with continuation logic, otherwise uses standard single-message processing.
💻 Technical Criteria
Given
An AEI report has been sized and line count determined
When
The report contains more than 699 lines
Then
The system initiates large report processing with continuation logic, otherwise uses standard single-message processing
R-GCX146-cbl-00672
Process Standard AEI Report
Process Rules
📊 Business Logic Narrative
When the process 'Process Standard AEI Report' is invoked, and assuming that an aei report contains 699 lines or fewer, when the system processes the report for email transmission, the desired outcome is that the system prepares the entire report as a single email message without continuation headers.
💻 Technical Criteria
Given
An AEI report contains 699 lines or fewer
When
The system processes the report for email transmission
Then
The system prepares the entire report as a single email message without continuation headers
R-GCX146-cbl-00673
Process Large Report with Continuation
Process Rules
📊 Business Logic Narrative
When the process 'Process Large Report with Continuation' is invoked, and assuming that an aei report contains more than 699 lines, when the system processes the report for email transmission, the desired outcome is that the system splits the report into multiple email messages, each containing up to 699 lines with appropriate continuation headers.
💻 Technical Criteria
Given
An AEI report contains more than 699 lines
When
The system processes the report for email transmission
Then
The system splits the report into multiple email messages, each containing up to 699 lines with appropriate continuation headers
R-GCX146-cbl-00674
Send Current Batch via EMCSEND3
Action Rules
📊 Business Logic Narrative
When the process 'Send Current Batch via EMCSEND3' is invoked, and assuming that an aei report message batch is prepared for transmission, when the system initiates email sending, the desired outcome is that the system calls emcsend3 service to transmit the email message to the configured recipients.
💻 Technical Criteria
Given
An AEI report message batch is prepared for transmission
When
The system initiates email sending
Then
The system calls EMCSEND3 service to transmit the email message to the configured recipients
R-GCX146-cbl-00675
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that a batch of aei report lines has been sent via email, when more lines remain to be processed in a large report, the desired outcome is that the system clears the current message buffer to prepare for the next continuation segment.
💻 Technical Criteria
Given
A batch of AEI report lines has been sent via email
When
More lines remain to be processed in a large report
Then
The system clears the current message buffer to prepare for the next continuation segment
R-GCX146-cbl-00676
Add Continuation Header
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header' is invoked, and assuming that a large aei report requires multiple email messages, when the system prepares continuation messages after the first message, the desired outcome is that the system adds 'continuation of report....' header to identify the message as part of a multi-part report.
💻 Technical Criteria
Given
A large AEI report requires multiple email messages
When
The system prepares continuation messages after the first message
Then
The system adds 'CONTINUATION OF REPORT....' header to identify the message as part of a multi-part report
R-GCX146-cbl-00677
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that a batch of lines from a large aei report has been processed, when the system checks for remaining content, the desired outcome is that if more lines exist beyond the current batch, the system continues processing with the next batch, otherwise completes the report transmission.
💻 Technical Criteria
Given
A batch of lines from a large AEI report has been processed
When
The system checks for remaining content
Then
If more lines exist beyond the current batch, the system continues processing with the next batch, otherwise completes the report transmission
R-GCX146-cbl-00678
Check Email Transmission Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Email Transmission Status' is invoked, and assuming that an aei report email has been sent via emcsend3, when the system receives the transmission response, the desired outcome is that the system evaluates the response to determine if the email was successfully delivered or if fallback procedures are needed.
💻 Technical Criteria
Given
An AEI report email has been sent via EMCSEND3
When
The system receives the transmission response
Then
The system evaluates the response to determine if the email was successfully delivered or if fallback procedures are needed
R-GCX146-cbl-00679
Email Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Successful?' is invoked, and assuming that an aei report email transmission attempt has completed, when the system evaluates the transmission status, the desired outcome is that if transmission failed, the system initiates fallback email procedures, otherwise proceeds with normal aei logging activities.
💻 Technical Criteria
Given
An AEI report email transmission attempt has completed
When
The system evaluates the transmission status
Then
If transmission failed, the system initiates fallback email procedures, otherwise proceeds with normal AEI logging activities
R-GCX146-cbl-00680
Use Fallback Email OM01247/AEI9999
Action Rules
📊 Business Logic Narrative
When the process 'Use Fallback Email OM01247/AEI9999' is invoked, and assuming that primary aei report email transmission has failed, when the system needs to ensure report delivery, the desired outcome is that the system sends the aei report to fallback email addresses om01247 and aei9999 to ensure delivery to support personnel.
💻 Technical Criteria
Given
Primary AEI report email transmission has failed
When
The system needs to ensure report delivery
Then
The system sends the AEI report to fallback email addresses OM01247 and AEI9999 to ensure delivery to support personnel
R-GCX146-cbl-00681
Log AEI Transmission Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log AEI Transmission Activity' is invoked, and assuming that an aei report transmission has been completed (successfully or via fallback), when the system finalizes the transmission process, the desired outcome is that the system creates audit log entries recording the aei transmission activity, including transmission status and recipient information.
💻 Technical Criteria
Given
An AEI report transmission has been completed (successfully or via fallback)
When
The system finalizes the transmission process
Then
The system creates audit log entries recording the AEI transmission activity, including transmission status and recipient information
R-GCX146-cbl-00685
Configure Merlin Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Configure Merlin Transmission' is invoked, and assuming that trip sheet distribution is required, when the system configures merlin transmission, the desired outcome is that merlin transmission parameters are set up for report delivery.
💻 Technical Criteria
Given
Trip sheet distribution is required
When
The system configures Merlin transmission
Then
Merlin transmission parameters are set up for report delivery
R-GCX146-cbl-00686
Send Canadian Trip Sheet via Merlin
Action Rules
📊 Business Logic Narrative
When the process 'Send Canadian Trip Sheet via Merlin' is invoked, and assuming that a canadian trip sheet is ready for distribution and merlin is configured, when the system sends the trip sheet via merlin, the desired outcome is that the canadian trip sheet is transmitted to customs and authorized recipients through merlin system.
💻 Technical Criteria
Given
A Canadian trip sheet is ready for distribution and Merlin is configured
When
The system sends the trip sheet via Merlin
Then
The Canadian trip sheet is transmitted to customs and authorized recipients through Merlin system
R-GCX146-cbl-00688
Prepare US Trip Sheet Data
Process Rules
📊 Business Logic Narrative
When the process 'Prepare US Trip Sheet Data' is invoked, and assuming that us trip sheet is required, when the system prepares us trip sheet data, the desired outcome is that us-specific trip sheet data is formatted with appropriate customs and regulatory information.
💻 Technical Criteria
Given
US trip sheet is required
When
The system prepares US trip sheet data
Then
US-specific trip sheet data is formatted with appropriate customs and regulatory information
R-GCX146-cbl-00689
Send US Trip Sheet via Merlin
Action Rules
📊 Business Logic Narrative
When the process 'Send US Trip Sheet via Merlin' is invoked, and assuming that us trip sheet data is prepared and merlin is configured, when the system sends the us trip sheet via merlin, the desired outcome is that the us trip sheet is transmitted to us customs and authorized recipients through merlin system.
💻 Technical Criteria
Given
US trip sheet data is prepared and Merlin is configured
When
The system sends the US trip sheet via Merlin
Then
The US trip sheet is transmitted to US customs and authorized recipients through Merlin system
R-GCX146-cbl-00690
Check AEI Report Distribution
Decision Rules
📊 Business Logic Narrative
When the process 'Check AEI Report Distribution' is invoked, and assuming that trip sheet distribution is in progress, when the system checks for aei report distribution requirements, the desired outcome is that the system identifies if aei report distribution is needed based on train type and configuration.
💻 Technical Criteria
Given
Trip sheet distribution is in progress
When
The system checks for AEI report distribution requirements
Then
The system identifies if AEI report distribution is needed based on train type and configuration
R-GCX146-cbl-00691
Email Distribution Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Distribution Required?' is invoked, and assuming that aei report distribution is being processed, when the system evaluates email distribution requirements, the desired outcome is that the system determines if email distribution is required based on station configuration and recipient preferences.
💻 Technical Criteria
Given
AEI report distribution is being processed
When
The system evaluates email distribution requirements
Then
The system determines if email distribution is required based on station configuration and recipient preferences
R-GCX146-cbl-00693
Send AEI Report via Email
Action Rules
📊 Business Logic Narrative
When the process 'Send AEI Report via Email' is invoked, and assuming that email user lists are retrieved and aei report is ready, when the system sends the aei report via email, the desired outcome is that the aei report is distributed via email to all configured recipients with proper formatting.
💻 Technical Criteria
Given
Email user lists are retrieved and AEI report is ready
When
The system sends the AEI report via email
Then
The AEI report is distributed via email to all configured recipients with proper formatting
R-GCX146-cbl-00694
Large Report?
Validation Rules
📊 Business Logic Narrative
When the process 'Large Report?' is invoked, and assuming that an aei report is being sent via email, when the system checks the report size, the desired outcome is that the system determines if the report exceeds 699 lines requiring continuation message handling.
💻 Technical Criteria
Given
An AEI report is being sent via email
When
The system checks the report size
Then
The system determines if the report exceeds 699 lines requiring continuation message handling
R-GCX146-cbl-00695
Handle Report Continuation
Process Rules
📊 Business Logic Narrative
When the process 'Handle Report Continuation' is invoked, and assuming that a report exceeds the maximum line limit of 699 lines, when the system handles report continuation, the desired outcome is that the system creates multiple email messages with continuation headers and distributes the complete report across multiple messages.
💻 Technical Criteria
Given
A report exceeds the maximum line limit of 699 lines
When
The system handles report continuation
Then
The system creates multiple email messages with continuation headers and distributes the complete report across multiple messages
R-GCX146-cbl-00696
Setup External FAX Addressing
Process Rules
📊 Business Logic Narrative
When the process 'Setup External FAX Addressing' is invoked, and assuming that fax routing parameters are configured, when the system sets up external fax addressing, the desired outcome is that external fax addresses are configured for customs and authorized recipients based on routing parameters.
💻 Technical Criteria
Given
FAX routing parameters are configured
When
The system sets up external FAX addressing
Then
External FAX addresses are configured for customs and authorized recipients based on routing parameters
R-GCX146-cbl-00697
Route to Copy IDs
Process Rules
📊 Business Logic Narrative
When the process 'Route to Copy IDs' is invoked, and assuming that external fax addressing is set up, when the system routes to copy ids, the desired outcome is that trip sheets are routed to all configured copy recipients based on distribution configuration.
💻 Technical Criteria
Given
External FAX addressing is set up
When
The system routes to copy IDs
Then
Trip sheets are routed to all configured copy recipients based on distribution configuration
R-GCX146-cbl-00698
Transmit to Customs Systems
Action Rules
📊 Business Logic Narrative
When the process 'Transmit to Customs Systems' is invoked, and assuming that trip sheets are prepared and routing is configured, when the system transmits to customs systems, the desired outcome is that trip sheets are transmitted to appropriate customs systems (canadian and/or us) for regulatory processing.
💻 Technical Criteria
Given
Trip sheets are prepared and routing is configured
When
The system transmits to customs systems
Then
Trip sheets are transmitted to appropriate customs systems (Canadian and/or US) for regulatory processing
R-GCX146-cbl-00699
Transmit to Authorized Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Transmit to Authorized Recipients' is invoked, and assuming that customs systems transmission is complete, when the system transmits to authorized recipients, the desired outcome is that trip sheets are transmitted to all authorized recipients including brokers, agents, and other stakeholders.
💻 Technical Criteria
Given
Customs systems transmission is complete
When
The system transmits to authorized recipients
Then
Trip sheets are transmitted to all authorized recipients including brokers, agents, and other stakeholders
R-GCX146-cbl-00700
Check Distribution Configuration
Decision Rules
📊 Business Logic Narrative
When the process 'Check Distribution Configuration' is invoked, and assuming that a status report needs to be distributed, when the system checks if this is an aei train send operation, the desired outcome is that email distribution is enabled for aei train sends and disabled for regular operations.
💻 Technical Criteria
Given
A status report needs to be distributed
When
The system checks if this is an AEI train send operation
Then
Email distribution is enabled for AEI train sends and disabled for regular operations
R-GCX146-cbl-00701
Prepare Email Recipients List
Action Rules
📊 Business Logic Narrative
When the process 'Prepare Email Recipients List' is invoked, and assuming that email distribution is required for a status report, when the system looks up email addresses using the station code from cusemail table, the desired outcome is that if email addresses are found, use them for distribution, otherwise use default support addresses om01247 and aei9999.
💻 Technical Criteria
Given
Email distribution is required for a status report
When
The system looks up email addresses using the station code from CUSEMAIL table
Then
If email addresses are found, use them for distribution, otherwise use default support addresses OM01247 and AEI9999
R-GCX146-cbl-00702
Send Status Report via Email
Process Rules
📊 Business Logic Narrative
When the process 'Send Status Report via Email' is invoked, and assuming that a status report is being sent via email, when the report exceeds 699 lines, the desired outcome is that split the report into multiple email messages with continuation headers 'continuation of report....' for subsequent messages.
💻 Technical Criteria
Given
A status report is being sent via email
When
The report exceeds 699 lines
Then
Split the report into multiple email messages with continuation headers 'CONTINUATION OF REPORT....' for subsequent messages
R-GCX146-cbl-00703
Merlin Distribution Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Merlin Distribution Required?' is invoked, and assuming that a status report has been processed for email distribution, when the system checks station configuration for merlin distribution requirements, the desired outcome is that enable merlin distribution if required by customs processing rules or station settings.
💻 Technical Criteria
Given
A status report has been processed for email distribution
When
The system checks station configuration for Merlin distribution requirements
Then
Enable Merlin distribution if required by customs processing rules or station settings
R-GCX146-cbl-00704
Prepare Merlin Message Format
Action Rules
📊 Business Logic Narrative
When the process 'Prepare Merlin Message Format' is invoked, and assuming that merlin distribution is required for a status report, when the system prepares the message format using validated merlin ids from emtz table, the desired outcome is that format the report content according to merlin communication standards with proper headers and routing information.
💻 Technical Criteria
Given
Merlin distribution is required for a status report
When
The system prepares the message format using validated Merlin IDs from EMTZ table
Then
Format the report content according to Merlin communication standards with proper headers and routing information
R-GCX146-cbl-00705
Send Status Report via Merlin
Action Rules
📊 Business Logic Narrative
When the process 'Send Status Report via Merlin' is invoked, and assuming that a status report is formatted for merlin transmission, when the system sends the report through merlin communication channels, the desired outcome is that transmit the report to designated merlin terminals with proper routing and confirmation handling.
💻 Technical Criteria
Given
A status report is formatted for Merlin transmission
When
The system sends the report through Merlin communication channels
Then
Transmit the report to designated Merlin terminals with proper routing and confirmation handling
R-GCX146-cbl-00706
FAX Distribution Required?
Decision Rules
📊 Business Logic Narrative
When the process 'FAX Distribution Required?' is invoked, and assuming that a status report has been processed for merlin distribution, when the system checks station configuration for auto-fax settings, the desired outcome is that enable fax distribution if auto-fax is configured for the station.
💻 Technical Criteria
Given
A status report has been processed for Merlin distribution
When
The system checks station configuration for auto-FAX settings
Then
Enable FAX distribution if auto-FAX is configured for the station
R-GCX146-cbl-00707
Setup FAX Routing Information
Action Rules
📊 Business Logic Narrative
When the process 'Setup FAX Routing Information' is invoked, and assuming that fax distribution is required for a status report, when the system retrieves fax configuration from station settings, the desired outcome is that setup routing information including fax numbers, transmission parameters, and delivery options from station configuration.
💻 Technical Criteria
Given
FAX distribution is required for a status report
When
The system retrieves FAX configuration from station settings
Then
Setup routing information including FAX numbers, transmission parameters, and delivery options from station configuration
R-GCX146-cbl-00708
Send Status Report via FAX
Action Rules
📊 Business Logic Narrative
When the process 'Send Status Report via FAX' is invoked, and assuming that fax routing information is configured for a status report, when the system initiates fax transmission, the desired outcome is that send the status report via fax to configured recipients with proper formatting and delivery confirmation.
💻 Technical Criteria
Given
FAX routing information is configured for a status report
When
The system initiates FAX transmission
Then
Send the status report via FAX to configured recipients with proper formatting and delivery confirmation
R-GCX146-cbl-00710
Log Distribution Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log Distribution Activity' is invoked, and assuming that status report distribution has been completed to all configured recipients, when the system finalizes the distribution process, the desired outcome is that log all distribution activities including transmission methods used, recipients contacted, success/failure status, and timestamps for audit trail.
💻 Technical Criteria
Given
Status report distribution has been completed to all configured recipients
When
The system finalizes the distribution process
Then
Log all distribution activities including transmission methods used, recipients contacted, success/failure status, and timestamps for audit trail
R-GCX146-cbl-00711
Set Error Code in WS-ERROR-NB
Action Rules
📊 Business Logic Narrative
When the process 'Set Error Code in WS-ERROR-NB' is invoked, and assuming that a processing error has been detected during train processing operations, when the system identifies the specific type of error that occurred, the desired outcome is that the system assigns the corresponding error code to ws-error-nb field for tracking and reporting purposes.
💻 Technical Criteria
Given
A processing error has been detected during train processing operations
When
The system identifies the specific type of error that occurred
Then
The system assigns the corresponding error code to WS-ERROR-NB field for tracking and reporting purposes
R-GCX146-cbl-00715
Supervisor Notification Required?
Decision Rules
📊 Business Logic Narrative
When the process 'Supervisor Notification Required?' is invoked, and assuming that error distribution recipients have been identified, when the system evaluates the error severity and type against notification policies, the desired outcome is that the system determines if supervisor notification is required and routes accordingly to supervisor communication channels or proceeds to other notification methods.
💻 Technical Criteria
Given
Error distribution recipients have been identified
When
The system evaluates the error severity and type against notification policies
Then
The system determines if supervisor notification is required and routes accordingly to supervisor communication channels or proceeds to other notification methods
R-GCX146-cbl-00716
Route to Supervisor via ALT-PCB
Action Rules
📊 Business Logic Narrative
When the process 'Route to Supervisor via ALT-PCB' is invoked, and assuming that the system has determined that supervisor notification is required, when error message routing to supervisor is initiated, the desired outcome is that the system routes the error message to supervisors using the alt-pcb communication channel with supervisor contact information from gcstbrt.
💻 Technical Criteria
Given
The system has determined that supervisor notification is required
When
Error message routing to supervisor is initiated
Then
The system routes the error message to supervisors using the ALT-PCB communication channel with supervisor contact information from GCSTBRT
R-GCX146-cbl-00717
Designated Personnel Notification?
Decision Rules
📊 Business Logic Narrative
When the process 'Designated Personnel Notification?' is invoked, and assuming that supervisor notification processing has been completed or bypassed, when the system evaluates whether additional designated personnel require notification, the desired outcome is that the system determines if designated personnel notification is needed and either routes to merlin communication system or proceeds to message queuing.
💻 Technical Criteria
Given
Supervisor notification processing has been completed or bypassed
When
The system evaluates whether additional designated personnel require notification
Then
The system determines if designated personnel notification is needed and either routes to Merlin communication system or proceeds to message queuing
R-GCX146-cbl-00718
Route to Merlin Communication System
Action Rules
📊 Business Logic Narrative
When the process 'Route to Merlin Communication System' is invoked, and assuming that the system has determined that designated personnel notification is required, when error message routing to designated personnel is initiated, the desired outcome is that the system routes the error message through the merlin communication system using communication ids from emtz-root.
💻 Technical Criteria
Given
The system has determined that designated personnel notification is required
When
Error message routing to designated personnel is initiated
Then
The system routes the error message through the Merlin communication system using communication IDs from EMTZ-ROOT
R-GCX146-cbl-00736
Extract Border Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Border Information' is invoked, and assuming that train data contains border segment information in gcwb4tl, when special manifest processing requires border details, the desired outcome is that border code and station name are extracted from the train border segments.
💻 Technical Criteria
Given
Train data contains border segment information in GCWB4TL
When
Special manifest processing requires border details
Then
Border code and station name are extracted from the train border segments
R-GCX146-cbl-00741
Port Fix Message Generation Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Port Fix Message Generation Not Found' is invoked, and assuming that a request to extract business rules for port fix message generation, when the provided cobol code summary is analyzed for port fix message generation logic, the desired outcome is that no specific port fix message generation business process can be identified in the available code.
💻 Technical Criteria
Given
A request to extract business rules for port fix message generation
When
The provided COBOL code summary is analyzed for port fix message generation logic
Then
No specific port fix message generation business process can be identified in the available code
R-GCX146-cbl-00752
Initialize EDI Header Setup
Process Rules
📊 Business Logic Narrative
When the process 'Initialize EDI Header Setup' is invoked, and assuming that a train manifest requires edi transmission to customs systems, when the edi transmission process begins, the desired outcome is that the system initializes edi header with train id, timestamp, and transmission control information.
💻 Technical Criteria
Given
A train manifest requires EDI transmission to customs systems
When
The EDI transmission process begins
Then
The system initializes EDI header with train ID, timestamp, and transmission control information
R-GCX146-cbl-00763
Transmit to Customs Systems
Action Rules
📊 Business Logic Narrative
When the process 'Transmit to Customs Systems' is invoked, and assuming that edi message is finalized and ready for transmission, when transmitting to customs systems, the desired outcome is that the system sends the complete edi message to the designated customs systems using established communication protocols.
💻 Technical Criteria
Given
EDI message is finalized and ready for transmission
When
Transmitting to customs systems
Then
The system sends the complete EDI message to the designated customs systems using established communication protocols
R-GCX146-cbl-00770
Include Train Identification
Process Rules
📊 Business Logic Narrative
When the process 'Include Train Identification' is invoked, and assuming that confirmation message formatting has begun, when the system includes train identification, the desired outcome is that train id, origin station, destination station, and customs train id are included in the confirmation message.
💻 Technical Criteria
Given
Confirmation message formatting has begun
When
The system includes train identification
Then
Train ID, origin station, destination station, and customs train ID are included in the confirmation message
R-GCX146-cbl-00805
Set Status to 'EXPORT'
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to 'EXPORT'' is invoked, and assuming that the transit status code has been evaluated as 'e' or 'z', when the system processes the export classification, the desired outcome is that the system sets the status to 'export'.
💻 Technical Criteria
Given
The transit status code has been evaluated as 'E' or 'Z'
When
The system processes the export classification
Then
The system sets the status to 'EXPORT'
R-GCX146-cbl-00821
Start AEI Report Email Distribution
Process Rules
📊 Business Logic Narrative
When the process 'Start AEI Report Email Distribution' is invoked, and assuming that an aei report needs to be distributed via email, when the email distribution process is initiated, the desired outcome is that the system should prepare for email processing and set up the distribution workflow.
💻 Technical Criteria
Given
An AEI report needs to be distributed via email
When
The email distribution process is initiated
Then
The system should prepare for email processing and set up the distribution workflow
R-GCX146-cbl-00823
Initialize Report Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Report Message Buffer' is invoked, and assuming that email recipients have been identified, when the system prepares to format the report for email, the desired outcome is that the system should initialize the message buffer and prepare report content for processing.
💻 Technical Criteria
Given
Email recipients have been identified
When
The system prepares to format the report for email
Then
The system should initialize the message buffer and prepare report content for processing
R-GCX146-cbl-00824
Check Report Size
Validation Rules
📊 Business Logic Narrative
When the process 'Check Report Size' is invoked, and assuming that a report is ready for email distribution, when the system checks the report size, the desired outcome is that the system should count the total number of lines in the report to determine processing approach.
💻 Technical Criteria
Given
A report is ready for email distribution
When
The system checks the report size
Then
The system should count the total number of lines in the report to determine processing approach
R-GCX146-cbl-00825
Report Exceeds 699 Lines?
Decision Rules
📊 Business Logic Narrative
When the process 'Report Exceeds 699 Lines?' is invoked, and assuming that a report has been sized and is ready for email transmission, when the system evaluates if the report exceeds 699 lines, the desired outcome is that if the report has more than 699 lines, the system should initiate batch processing, otherwise proceed with single email transmission.
💻 Technical Criteria
Given
A report has been sized and is ready for email transmission
When
The system evaluates if the report exceeds 699 lines
Then
If the report has more than 699 lines, the system should initiate batch processing, otherwise proceed with single email transmission
R-GCX146-cbl-00826
Send Current Report Batch via Email
Action Rules
📊 Business Logic Narrative
When the process 'Send Current Report Batch via Email' is invoked, and assuming that a report batch is prepared and ready for transmission, when the system sends the current report batch via email, the desired outcome is that the system should transmit the current batch using emcsend3 email service to the configured recipients.
💻 Technical Criteria
Given
A report batch is prepared and ready for transmission
When
The system sends the current report batch via email
Then
The system should transmit the current batch using EMCSEND3 email service to the configured recipients
R-GCX146-cbl-00827
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that a report batch has been successfully sent via email, when the system needs to prepare for the next batch, the desired outcome is that the system should reset the message buffer and clear previous content to prepare for continuation processing.
💻 Technical Criteria
Given
A report batch has been successfully sent via email
When
The system needs to prepare for the next batch
Then
The system should reset the message buffer and clear previous content to prepare for continuation processing
R-GCX146-cbl-00828
Add Continuation Header Message
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header Message' is invoked, and assuming that a report has been split into multiple email batches, when the system prepares a continuation email message, the desired outcome is that the system should add the header 'continuation of report....' to indicate this is a continuation of the previous message.
💻 Technical Criteria
Given
A report has been split into multiple email batches
When
The system prepares a continuation email message
Then
The system should add the header 'CONTINUATION OF REPORT....' to indicate this is a continuation of the previous message
R-GCX146-cbl-00829
Continue Processing Remaining Lines
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing Remaining Lines' is invoked, and assuming that the initial report batch has been sent and continuation header added, when the system continues processing the remaining report lines, the desired outcome is that the system should continue processing the remaining lines from where the previous batch ended.
💻 Technical Criteria
Given
The initial report batch has been sent and continuation header added
When
The system continues processing the remaining report lines
Then
The system should continue processing the remaining lines from where the previous batch ended
R-GCX146-cbl-00830
Process Next Line Batch
Process Rules
📊 Business Logic Narrative
When the process 'Process Next Line Batch' is invoked, and assuming that there are remaining report lines to process, when the system processes the next line batch, the desired outcome is that the system should process up to 699 lines for the next email batch while maintaining report formatting.
💻 Technical Criteria
Given
There are remaining report lines to process
When
The system processes the next line batch
Then
The system should process up to 699 lines for the next email batch while maintaining report formatting
R-GCX146-cbl-00831
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that a batch of report lines has been processed, when the system checks for additional lines to process, the desired outcome is that if there are more lines remaining, continue batch processing, otherwise proceed to send the final email batch.
💻 Technical Criteria
Given
A batch of report lines has been processed
When
The system checks for additional lines to process
Then
If there are more lines remaining, continue batch processing, otherwise proceed to send the final email batch
R-GCX146-cbl-00832
Send Final Email Batch
Action Rules
📊 Business Logic Narrative
When the process 'Send Final Email Batch' is invoked, and assuming that all report lines have been processed and the final batch is ready, when the system sends the final email batch, the desired outcome is that the system should transmit the final batch using emcsend3 email service to complete the report distribution.
💻 Technical Criteria
Given
All report lines have been processed and the final batch is ready
When
The system sends the final email batch
Then
The system should transmit the final batch using EMCSEND3 email service to complete the report distribution
R-GCX146-cbl-00834
Use Fallback Email Recipients
Process Rules
📊 Business Logic Narrative
When the process 'Use Fallback Email Recipients' is invoked, and assuming that the primary email transmission has failed, when the system activates fallback email recipients, the desired outcome is that the system should prepare to use the fallback email addresses om01247 and aei9999 for report delivery.
💻 Technical Criteria
Given
The primary email transmission has failed
When
The system activates fallback email recipients
Then
The system should prepare to use the fallback email addresses OM01247 and AEI9999 for report delivery
R-GCX146-cbl-00835
Send via OM01247/AEI9999
Action Rules
📊 Business Logic Narrative
When the process 'Send via OM01247/AEI9999' is invoked, and assuming that primary email delivery has failed and fallback recipients are activated, when the system sends via fallback email addresses, the desired outcome is that the system should transmit the report to om01247 and aei9999 using the fallback email service.
💻 Technical Criteria
Given
Primary email delivery has failed and fallback recipients are activated
When
The system sends via fallback email addresses
Then
The system should transmit the report to OM01247 and AEI9999 using the fallback email service
R-GCX146-cbl-00837
AEI Report Distribution Complete
Process Rules
📊 Business Logic Narrative
When the process 'AEI Report Distribution Complete' is invoked, and assuming that all email transmissions have been completed and logged, when the aei report distribution process concludes, the desired outcome is that the system should mark the distribution as complete and finalize the process.
💻 Technical Criteria
Given
All email transmissions have been completed and logged
When
The AEI report distribution process concludes
Then
The system should mark the distribution as complete and finalize the process
R-GCX146-cbl-01335
Get Email User List from Station Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Get Email User List from Station Configuration' is invoked, and assuming that a station code is provided for email report processing, when the system looks up email configuration for the station, the desired outcome is that the system retrieves the list of email users configured for that station from the station configuration table.
💻 Technical Criteria
Given
A station code is provided for email report processing
When
The system looks up email configuration for the station
Then
The system retrieves the list of email users configured for that station from the station configuration table
R-GCX146-cbl-01337
Initialize Email Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Email Message Buffer' is invoked, and assuming that email users are configured for the station, when the system begins email report processing, the desired outcome is that initialize email message buffer, clear previous content, and prepare for new report data.
💻 Technical Criteria
Given
Email users are configured for the station
When
The system begins email report processing
Then
Initialize email message buffer, clear previous content, and prepare for new report data
R-GCX146-cbl-01338
Add Report Header Lines
Process Rules
📊 Business Logic Narrative
When the process 'Add Report Header Lines' is invoked, and assuming that email message buffer is initialized, when the system begins building the email report content, the desired outcome is that add report header lines including report identification, date, time, and relevant train or processing information.
💻 Technical Criteria
Given
Email message buffer is initialized
When
The system begins building the email report content
Then
Add report header lines including report identification, date, time, and relevant train or processing information
R-GCX146-cbl-01346
Log Successful Email Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Email Transmission' is invoked, and assuming that email has been successfully transmitted, when the system processes the successful transmission, the desired outcome is that log the successful email transmission with timestamp, recipient information, and report details for audit trail.
💻 Technical Criteria
Given
Email has been successfully transmitted
When
The system processes the successful transmission
Then
Log the successful email transmission with timestamp, recipient information, and report details for audit trail
R-GCX146-cbl-01347
Try Fallback Email Address OM01247/AEI9999
Action Rules
📊 Business Logic Narrative
When the process 'Try Fallback Email Address OM01247/AEI9999' is invoked, and assuming that primary email transmission has failed, when the system attempts fallback email delivery, the desired outcome is that send the email report to fallback support addresses om01247 and aei9999 to ensure report delivery.
💻 Technical Criteria
Given
Primary email transmission has failed
When
The system attempts fallback email delivery
Then
Send the email report to fallback support addresses OM01247 and AEI9999 to ensure report delivery
R-GCX146-cbl-01349
Log Email Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Email Failure' is invoked, and assuming that both primary and fallback email transmissions have failed, when the system processes the failed transmission attempts, the desired outcome is that log the email failure with error details, attempted recipients, and report information for troubleshooting.
💻 Technical Criteria
Given
Both primary and fallback email transmissions have failed
When
The system processes the failed transmission attempts
Then
Log the email failure with error details, attempted recipients, and report information for troubleshooting
R-GCX146-cbl-01668
Validate Email Address Structure
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Email Address Structure' is invoked, and assuming that an email address needs structural validation, when the system validates the email structure, the desired outcome is that the email must contain exactly one @ symbol and the domain portion must follow valid domain naming conventions.
💻 Technical Criteria
Given
An email address needs structural validation
When
The system validates the email structure
Then
The email must contain exactly one @ symbol and the domain portion must follow valid domain naming conventions
R-GCX146-cbl-01351
Line Counter > 699?
Process Rules
📊 Business Logic Narrative
When the process 'Line Counter > 699?' is invoked, and assuming that an email report is being generated with multiple lines of content, when the line counter exceeds 699 lines in the current email message, the desired outcome is that the system should trigger continuation processing to send the current batch and prepare for the next message segment.
💻 Technical Criteria
Given
An email report is being generated with multiple lines of content
When
The line counter exceeds 699 lines in the current email message
Then
The system should trigger continuation processing to send the current batch and prepare for the next message segment
R-GCX146-cbl-01354
Add Continuation Header Message
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header Message' is invoked, and assuming that a new continuation email message is being prepared, when the message buffer has been reset for continuation processing, the desired outcome is that the system should add the header message 'continuation of report ....' to identify this as a continuation message.
💻 Technical Criteria
Given
A new continuation email message is being prepared
When
The message buffer has been reset for continuation processing
Then
The system should add the header message 'CONTINUATION OF REPORT ....' to identify this as a continuation message
R-GCX146-cbl-01355
Reset Line Counter
Process Rules
📊 Business Logic Narrative
When the process 'Reset Line Counter' is invoked, and assuming that a continuation message is being prepared with header added, when starting to process remaining report lines for the new message, the desired outcome is that the system should reset the line counter to zero to begin counting lines for the new message segment.
💻 Technical Criteria
Given
A continuation message is being prepared with header added
When
Starting to process remaining report lines for the new message
Then
The system should reset the line counter to zero to begin counting lines for the new message segment
R-GCX146-cbl-01356
Continue Processing Remaining Lines
Process Rules
📊 Business Logic Narrative
When the process 'Continue Processing Remaining Lines' is invoked, and assuming that continuation processing has been completed with buffer reset and counter reset, when there are remaining report lines to be processed, the desired outcome is that the system should continue processing the remaining lines in the new message segment.
💻 Technical Criteria
Given
Continuation processing has been completed with buffer reset and counter reset
When
There are remaining report lines to be processed
Then
The system should continue processing the remaining lines in the new message segment
R-GCX146-cbl-01357
Add Line to Email Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Add Line to Email Buffer' is invoked, and assuming that a report line is being processed for email transmission, when the line is ready to be included in the email message, the desired outcome is that the system should add the line to the current email message buffer.
💻 Technical Criteria
Given
A report line is being processed for email transmission
When
The line is ready to be included in the email message
Then
The system should add the line to the current email message buffer
R-GCX146-cbl-01359
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that a report line has been processed and added to the email buffer, when checking for continuation of report processing, the desired outcome is that the system should evaluate whether there are more lines remaining in the report to be processed.
💻 Technical Criteria
Given
A report line has been processed and added to the email buffer
When
Checking for continuation of report processing
Then
The system should evaluate whether there are more lines remaining in the report to be processed
R-GCX146-cbl-01360
Send Final Email Batch
Action Rules
📊 Business Logic Narrative
When the process 'Send Final Email Batch' is invoked, and assuming that all report lines have been processed and no more lines remain, when the final email message batch is ready for transmission, the desired outcome is that the system should send the final email batch containing the remaining report content.
💻 Technical Criteria
Given
All report lines have been processed and no more lines remain
When
The final email message batch is ready for transmission
Then
The system should send the final email batch containing the remaining report content
R-GCX146-cbl-01530
Initialize Line Counter WS-LINE-SUB
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Line Counter WS-LINE-SUB' is invoked, and assuming that an email report processing session is starting, when the system begins processing report lines for email transmission, the desired outcome is that the line counter should be initialized to zero to start counting from the beginning.
💻 Technical Criteria
Given
An email report processing session is starting
When
The system begins processing report lines for email transmission
Then
The line counter should be initialized to zero to start counting from the beginning
R-GCX146-cbl-01531
Line Counter > 699?
Validation Rules
📊 Business Logic Narrative
When the process 'Line Counter > 699?' is invoked, and assuming that an email report is being processed with accumulated lines, when the line counter exceeds 699 lines in the current email segment, the desired outcome is that the current email batch should be sent and a new email segment should be prepared.
💻 Technical Criteria
Given
An email report is being processed with accumulated lines
When
The line counter exceeds 699 lines in the current email segment
Then
The current email batch should be sent and a new email segment should be prepared
R-GCX146-cbl-01532
Call X280-CALL-EMCSEND3 to Send Current Batch
Action Rules
📊 Business Logic Narrative
When the process 'Call X280-CALL-EMCSEND3 to Send Current Batch' is invoked, and assuming that an email report batch has reached the maximum line limit of 699 lines, when the system needs to send the current batch, the desired outcome is that the email sending service should be invoked to transmit the current batch.
💻 Technical Criteria
Given
An email report batch has reached the maximum line limit of 699 lines
When
The system needs to send the current batch
Then
The email sending service should be invoked to transmit the current batch
R-GCX146-cbl-01533
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that an email batch has been sent successfully, when the system needs to prepare for additional report lines, the desired outcome is that the message buffer should be cleared and reset for the next email segment.
💻 Technical Criteria
Given
An email batch has been sent successfully
When
The system needs to prepare for additional report lines
Then
The message buffer should be cleared and reset for the next email segment
R-GCX146-cbl-01534
Add CONTINUATION OF REPORT Header
Process Rules
📊 Business Logic Narrative
When the process 'Add CONTINUATION OF REPORT Header' is invoked, and assuming that an email report has been split into multiple segments due to line limits, when a new email segment is being prepared after the first segment, the desired outcome is that a 'continuation of report' header should be added to identify the segment as a continuation.
💻 Technical Criteria
Given
An email report has been split into multiple segments due to line limits
When
A new email segment is being prepared after the first segment
Then
A 'CONTINUATION OF REPORT' header should be added to identify the segment as a continuation
R-GCX146-cbl-01536
Reached Maximum 1981 Lines?
Validation Rules
📊 Business Logic Narrative
When the process 'Reached Maximum 1981 Lines?' is invoked, and assuming that an email report is being processed with multiple segments, when the total number of lines processed reaches 1981 lines, the desired outcome is that the maximum lines reached flag should be set and no additional lines should be processed.
💻 Technical Criteria
Given
An email report is being processed with multiple segments
When
The total number of lines processed reaches 1981 lines
Then
The maximum lines reached flag should be set and no additional lines should be processed
R-GCX146-cbl-01537
Set MAX-LINES-REACHED Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set MAX-LINES-REACHED Flag' is invoked, and assuming that the email report processing has reached the maximum limit of 1981 lines, when the system detects the line limit has been exceeded, the desired outcome is that the max-lines-reached flag should be set to prevent further line processing.
💻 Technical Criteria
Given
The email report processing has reached the maximum limit of 1981 lines
When
The system detects the line limit has been exceeded
Then
The MAX-LINES-REACHED flag should be set to prevent further line processing
R-GCX146-cbl-01538
Set NO-MORE-EMAIL Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set NO-MORE-EMAIL Flag' is invoked, and assuming that all available report lines have been processed for email transmission, when there are no more lines to process in the report, the desired outcome is that the no-more-email flag should be set to indicate completion of email processing.
💻 Technical Criteria
Given
All available report lines have been processed for email transmission
When
There are no more lines to process in the report
Then
The NO-MORE-EMAIL flag should be set to indicate completion of email processing
R-GCX146-cbl-00840
Setup FAX Routing Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Setup FAX Routing Parameters' is invoked, and assuming that auto-fax is enabled for the current station, when the system prepares for message transmission, the desired outcome is that fax routing parameters are configured including destination settings and transmission options.
💻 Technical Criteria
Given
Auto-FAX is enabled for the current station
When
The system prepares for message transmission
Then
FAX routing parameters are configured including destination settings and transmission options
R-GCX146-cbl-00842
Configure External FAX Addressing
Process Rules
📊 Business Logic Narrative
When the process 'Configure External FAX Addressing' is invoked, and assuming that copy ids are configured for fax distribution, when the system sets up external addressing, the desired outcome is that external fax addresses and routing information are configured for customs authority delivery.
💻 Technical Criteria
Given
Copy IDs are configured for FAX distribution
When
The system sets up external addressing
Then
External FAX addresses and routing information are configured for customs authority delivery
R-GCX146-cbl-00847
Add Continuation Header
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header' is invoked, and assuming that a message has remaining batches after the first transmission, when the system prepares subsequent message batches, the desired outcome is that each remaining batch is prefixed with 'continuation of report....' header.
💻 Technical Criteria
Given
A message has remaining batches after the first transmission
When
The system prepares subsequent message batches
Then
Each remaining batch is prefixed with 'CONTINUATION OF REPORT....' header
R-GCX146-cbl-01552
Add Continuation Header
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header' is invoked, and assuming that a message has been segmented due to line count exceeding 699, when the system processes continuation segments, the desired outcome is that each continuation segment includes header 'continuation of report ....' to identify it as part of original message.
💻 Technical Criteria
Given
A message has been segmented due to line count exceeding 699
When
The system processes continuation segments
Then
Each continuation segment includes header 'CONTINUATION OF REPORT ....' to identify it as part of original message
R-GCX146-cbl-01556
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that report lines are being processed for message formatting, when the system checks for remaining unprocessed lines, the desired outcome is that if more lines exist, processing continues; otherwise, message formatting is finalized.
💻 Technical Criteria
Given
Report lines are being processed for message formatting
When
The system checks for remaining unprocessed lines
Then
If more lines exist, processing continues; otherwise, message formatting is finalized
R-GCX146-cbl-01557
Finalize Message Format
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Message Format' is invoked, and assuming that all report lines have been processed and formatted, when no more lines remain to be processed, the desired outcome is that the system finalizes the message format and prepares it for transmission.
💻 Technical Criteria
Given
All report lines have been processed and formatted
When
No more lines remain to be processed
Then
The system finalizes the message format and prepares it for transmission
R-GCX146-cbl-01684
Route to Primary Merlin ID
Process Rules
📊 Business Logic Narrative
When the process 'Route to Primary Merlin ID' is invoked, and assuming that merlin transmission parameters have been set, when the system routes to the primary merlin id, the desired outcome is that the message is directed to the primary merlin id for delivery.
💻 Technical Criteria
Given
Merlin transmission parameters have been set
When
The system routes to the primary Merlin ID
Then
The message is directed to the primary Merlin ID for delivery
R-GCX146-cbl-01685
Primary Routing Success?
Validation Rules
📊 Business Logic Narrative
When the process 'Primary Routing Success?' is invoked, and assuming that a message has been routed to the primary merlin id, when the system checks primary routing success, the desired outcome is that the system determines whether the primary routing succeeded or failed.
💻 Technical Criteria
Given
A message has been routed to the primary Merlin ID
When
The system checks primary routing success
Then
The system determines whether the primary routing succeeded or failed
R-GCX146-cbl-01686
Route to Backup Merlin ID
Process Rules
📊 Business Logic Narrative
When the process 'Route to Backup Merlin ID' is invoked, and assuming that primary merlin id routing has failed, when the system routes to backup merlin id, the desired outcome is that the message is redirected to the backup merlin id for delivery.
💻 Technical Criteria
Given
Primary Merlin ID routing has failed
When
The system routes to backup Merlin ID
Then
The message is redirected to the backup Merlin ID for delivery
R-GCX146-cbl-01831
Apply Line Segmentation Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Line Segmentation Rules' is invoked, and assuming that an email report needs to be sent with multiple lines of content, when the system processes the email content for transmission, the desired outcome is that the content is segmented into batches of maximum 699 lines each with proper continuation headers for subsequent segments.
💻 Technical Criteria
Given
An email report needs to be sent with multiple lines of content
When
The system processes the email content for transmission
Then
The content is segmented into batches of maximum 699 lines each with proper continuation headers for subsequent segments
R-GCX146-cbl-01836
Add CONTINUATION OF REPORT Header
Process Rules
📊 Business Logic Narrative
When the process 'Add CONTINUATION OF REPORT Header' is invoked, and assuming that a new email segment is being prepared after the first segment, when the message buffer is reset for continuation, the desired outcome is that a 'continuation of report' header is added to indicate this is a follow-up segment.
💻 Technical Criteria
Given
A new email segment is being prepared after the first segment
When
The message buffer is reset for continuation
Then
A 'CONTINUATION OF REPORT' header is added to indicate this is a follow-up segment
R-GCX146-cbl-01838
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that email content is being processed in segments, when the system completes processing a portion of content, the desired outcome is that the system checks if more lines remain to be processed for continuation or completion.
💻 Technical Criteria
Given
Email content is being processed in segments
When
The system completes processing a portion of content
Then
The system checks if more lines remain to be processed for continuation or completion
R-GCX146-cbl-00932
Set Message Format to GCT1401E
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Message Format to GCT1401E' is invoked, and assuming that customer report message is initialized, when the system configures message format, the desired outcome is that the message format is set to gct1401e transaction type.
💻 Technical Criteria
Given
Customer report message is initialized
When
The system configures message format
Then
The message format is set to GCT1401E transaction type
R-GCX146-cbl-00933
Configure ALT-PCB2 for Message Queuing
Process Rules
📊 Business Logic Narrative
When the process 'Configure ALT-PCB2 for Message Queuing' is invoked, and assuming that message format is set to gct1401e, when the system configures message queuing, the desired outcome is that alt-pcb2 is configured for customer report message control and queuing.
💻 Technical Criteria
Given
Message format is set to GCT1401E
When
The system configures message queuing
Then
ALT-PCB2 is configured for customer report message control and queuing
R-GCX146-cbl-00934
Move Report Content to Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Move Report Content to Message Buffer' is invoked, and assuming that alt-pcb2 is configured for message queuing and report content exists in gcx140-input, when the system transfers report content, the desired outcome is that report content is moved from gcx140-input to the message buffer.
💻 Technical Criteria
Given
ALT-PCB2 is configured for message queuing AND report content exists in GCX140-INPUT
When
The system transfers report content
Then
Report content is moved from GCX140-INPUT to the message buffer
R-GCX146-cbl-00935
Execute CIMS CHNG Operation
Action Rules
📊 Business Logic Narrative
When the process 'Execute CIMS CHNG Operation' is invoked, and assuming that report content is in message buffer, when the system executes cims chng operation, the desired outcome is that database change operation is performed for customer report update.
💻 Technical Criteria
Given
Report content is in message buffer
When
The system executes CIMS CHNG operation
Then
Database change operation is performed for customer report update
R-GCX146-cbl-00937
Execute CIMS WRITMSGL Operation
Action Rules
📊 Business Logic Narrative
When the process 'Execute CIMS WRITMSGL Operation' is invoked, and assuming that chng operation completed successfully, when the system executes cims writmsgl operation, the desired outcome is that customer report message is written to the message queue.
💻 Technical Criteria
Given
CHNG operation completed successfully
When
The system executes CIMS WRITMSGL operation
Then
Customer report message is written to the message queue
R-GCX146-cbl-00940
PURG Operation Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'PURG Operation Successful?' is invoked, and assuming that cims purg operation is executed, when the system checks operation status, the desired outcome is that if purg operation is successful, customer report is successfully created, otherwise handle database operation error.
💻 Technical Criteria
Given
CIMS PURG operation is executed
When
The system checks operation status
Then
If PURG operation is successful, customer report is successfully created, otherwise handle database operation error
R-GCX146-cbl-00941
Customer Report Successfully Created
Process Rules
📊 Business Logic Narrative
When the process 'Customer Report Successfully Created' is invoked, and assuming that all database operations (chng, writmsgl, purg) completed successfully, when the system confirms report creation, the desired outcome is that customer report is marked as successfully created and process completes normally.
💻 Technical Criteria
Given
All database operations (CHNG, WRITMSGL, PURG) completed successfully
When
The system confirms report creation
Then
Customer report is marked as successfully created and process completes normally
R-GCX146-cbl-00991
Initialize Line Counter
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Line Counter' is invoked, and assuming that a merlin report needs to be processed for transmission, when the system starts processing report lines, the desired outcome is that the line counter is set to zero and message buffer is initialized.
💻 Technical Criteria
Given
A Merlin report needs to be processed for transmission
When
The system starts processing report lines
Then
The line counter is set to zero and message buffer is initialized
R-GCX146-cbl-00992
Get Next Report Line
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Report Line' is invoked, and assuming that report lines are available for processing, when the system requests the next report line, the desired outcome is that the next sequential report line is retrieved from the report data.
💻 Technical Criteria
Given
Report lines are available for processing
When
The system requests the next report line
Then
The next sequential report line is retrieved from the report data
R-GCX146-cbl-00993
Line Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Line Available?' is invoked, and assuming that the system is processing report lines, when the system checks for line availability, the desired outcome is that if lines are available, continue processing; if no lines available, finalize current message.
💻 Technical Criteria
Given
The system is processing report lines
When
The system checks for line availability
Then
If lines are available, continue processing; if no lines available, finalize current message
R-GCX146-cbl-00994
Format Line for Merlin Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Format Line for Merlin Transmission' is invoked, and assuming that a report line is available for processing, when the system formats the line for merlin transmission, the desired outcome is that the line is formatted according to merlin protocol specifications.
💻 Technical Criteria
Given
A report line is available for processing
When
The system formats the line for Merlin transmission
Then
The line is formatted according to Merlin protocol specifications
R-GCX146-cbl-00995
Check Line Length Limits
Validation Rules
📊 Business Logic Narrative
When the process 'Check Line Length Limits' is invoked, and assuming that a formatted report line is ready to be added to the message buffer, when the system checks the current line count in the message, the desired outcome is that if the message has 699 or more lines, create a continuation message; otherwise add line to current message.
💻 Technical Criteria
Given
A formatted report line is ready to be added to the message buffer
When
The system checks the current line count in the message
Then
If the message has 699 or more lines, create a continuation message; otherwise add line to current message
R-GCX146-cbl-00996
Add Line to Current Message Buffer
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Add Line to Current Message Buffer', assuming that a formatted report line is ready and message buffer has not exceeded line limits, when the system adds the line to the message buffer, the desired outcome is that the line is appended to the current message buffer.
💻 Technical Criteria
EXCLUDING
A formatted report line is ready and message buffer has not exceeded line limits
When
The system adds the line to the message buffer
Then
The line is appended to the current message buffer
R-GCX146-cbl-00997
Increment Line Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Line Counter' is invoked, and assuming that a report line has been added to the message buffer, when the system updates the line counter, the desired outcome is that the line counter is incremented by one.
💻 Technical Criteria
Given
A report line has been added to the message buffer
When
The system updates the line counter
Then
The line counter is incremented by one
R-GCX146-cbl-01000
Add Continuation Header
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header' is invoked, and assuming that a continuation message has been created, when the system adds the continuation header, the desired outcome is that the header 'continuation of report....' is added to the beginning of the new message.
💻 Technical Criteria
Given
A continuation message has been created
When
The system adds the continuation header
Then
The header 'CONTINUATION OF REPORT....' is added to the beginning of the new message
R-GCX146-cbl-01058
Send Current Message Segment
Action Rules
📊 Business Logic Narrative
When the process 'Send Current Message Segment' is invoked, and assuming that a prepared message segment ready for transmission, when the system sends the message segment, the desired outcome is that message segment is transmitted to us customs through merlin communication system.
💻 Technical Criteria
Given
A prepared message segment ready for transmission
When
The system sends the message segment
Then
Message segment is transmitted to US customs through Merlin communication system
R-GCX146-cbl-01062
Transmit Final Message to US Customs
Action Rules
📊 Business Logic Narrative
When the process 'Transmit Final Message to US Customs' is invoked, and assuming that a finalized message ready for transmission, when the system transmits the final message, the desired outcome is that complete trip sheet data is sent to us customs via merlin communication system.
💻 Technical Criteria
Given
A finalized message ready for transmission
When
The system transmits the final message
Then
Complete trip sheet data is sent to US customs via Merlin communication system
R-GCX146-cbl-01063
Log Transmission Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log Transmission Activity' is invoked, and assuming that a message has been transmitted to us customs, when the system logs the transmission, the desired outcome is that transmission details including timestamp, message count, and status are recorded for audit trail.
💻 Technical Criteria
Given
A message has been transmitted to US customs
When
The system logs the transmission
Then
Transmission details including timestamp, message count, and status are recorded for audit trail
R-GCX146-cbl-01118
Replace Spaces with Zeros
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros' is invoked, and assuming that a train identification component contains space characters, when the system processes the train component for customs id building, the desired outcome is that all space characters in the component are replaced with zero characters.
💻 Technical Criteria
Given
A train identification component contains space characters
When
The system processes the train component for customs ID building
Then
All space characters in the component are replaced with zero characters
R-GCX146-cbl-01119
Build Customs Train ID Components
Computation Rules
📊 Business Logic Narrative
When the process 'Build Customs Train ID Components' is invoked, and assuming that train number, day, from station, to station, consist number, and system date are available, when the system needs to create a customs train identifier, the desired outcome is that the system concatenates all components with spaces replaced by zeros to form ws-customs-train-id.
💻 Technical Criteria
Given
Train number, day, from station, to station, consist number, and system date are available
When
The system needs to create a customs train identifier
Then
The system concatenates all components with spaces replaced by zeros to form WS-CUSTOMS-TRAIN-ID
R-GCX146-cbl-01139
Report Exceeds Line Limit?
Validation Rules
📊 Business Logic Narrative
When the process 'Report Exceeds Line Limit?' is invoked, and assuming that an email notification is being prepared, when the system checks the report size against the line limit, the desired outcome is that the system returns true if report exceeds 699 lines, otherwise false.
💻 Technical Criteria
Given
An email notification is being prepared
When
The system checks the report size against the line limit
Then
The system returns true if report exceeds 699 lines, otherwise false
R-GCX146-cbl-01140
Send Standard Email
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Send Standard Email', assuming that email report does not exceed 699 lines, when the system processes standard email transmission, the desired outcome is that the system invokes emcsend3 module to send the complete email notification.
💻 Technical Criteria
EXCLUDING
Email report does not exceed 699 lines
When
The system processes standard email transmission
Then
The system invokes EMCSEND3 module to send the complete email notification
R-GCX146-cbl-01141
Send Email with Continuation
Action Rules
📊 Business Logic Narrative
When the process 'Send Email with Continuation' is invoked, and assuming that email report exceeds 699 lines, when the system processes large email transmission, the desired outcome is that the system sends first 699 lines and creates continuation messages with header 'continuation of report...' for remaining content using emcsend3 module.
💻 Technical Criteria
Given
Email report exceeds 699 lines
When
The system processes large email transmission
Then
The system sends first 699 lines and creates continuation messages with header 'CONTINUATION OF REPORT...' for remaining content using EMCSEND3 module
R-GCX146-cbl-01142
Line Count > 699?
Validation Rules
📊 Business Logic Narrative
When the process 'Line Count > 699?' is invoked, and assuming that an aei report is being prepared for email distribution, when the system counts the number of lines in the current email message, the desired outcome is that if the line count exceeds 699 lines, the system must send the current batch and prepare for continuation.
💻 Technical Criteria
Given
An AEI report is being prepared for email distribution
When
The system counts the number of lines in the current email message
Then
If the line count exceeds 699 lines, the system must send the current batch and prepare for continuation
R-GCX146-cbl-01143
Add Continuation Header Message
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Header Message' is invoked, and assuming that an email message has reached the 699 line limit and needs to be continued, when the system prepares the next email message segment, the desired outcome is that the system must add a continuation header message 'continuation of report....' to identify it as a follow-up message.
💻 Technical Criteria
Given
An email message has reached the 699 line limit and needs to be continued
When
The system prepares the next email message segment
Then
The system must add a continuation header message 'CONTINUATION OF REPORT....' to identify it as a follow-up message
R-GCX146-cbl-01144
Use Fallback Email Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Use Fallback Email Recipients' is invoked, and assuming that primary email distribution has failed for an aei report, when the system detects email send failure, the desired outcome is that the system must use fallback email recipients om01247 and aei9999 to ensure report delivery.
💻 Technical Criteria
Given
Primary email distribution has failed for an AEI report
When
The system detects email send failure
Then
The system must use fallback email recipients OM01247 and AEI9999 to ensure report delivery
R-GCX146-cbl-01145
Get Email User List from Station Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Get Email User List from Station Configuration' is invoked, and assuming that an aei report needs to be distributed via email, when the system determines email recipients, the desired outcome is that the system must retrieve email user lists from gcstbrt station email configuration and aecwrktb email user lists based on the station code.
💻 Technical Criteria
Given
An AEI report needs to be distributed via email
When
The system determines email recipients
Then
The system must retrieve email user lists from GCSTBRT station email configuration and AECWRKTB email user lists based on the station code
R-GCX146-cbl-01146
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that an email message has been sent due to line limit being reached, when the system needs to prepare for the next message segment, the desired outcome is that the system must reset the message buffer to prepare for additional report content.
💻 Technical Criteria
Given
An email message has been sent due to line limit being reached
When
The system needs to prepare for the next message segment
Then
The system must reset the message buffer to prepare for additional report content
R-GCX146-cbl-01147
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that the system is processing report lines for email distribution, when the system checks for remaining content after sending a message batch, the desired outcome is that if more lines exist to be processed, the system must continue adding lines to the email buffer, otherwise proceed to send the final email batch.
💻 Technical Criteria
Given
The system is processing report lines for email distribution
When
The system checks for remaining content after sending a message batch
Then
If more lines exist to be processed, the system must continue adding lines to the email buffer, otherwise proceed to send the final email batch
R-GCX146-cbl-01162
Deletion Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Deletion Successful?' is invoked, and assuming that a delete operation has been performed on an existing train record, when the system evaluates the deletion operation result, the desired outcome is that if deletion was successful, proceed to insert new train record; if deletion failed, report database operation error.
💻 Technical Criteria
Given
A delete operation has been performed on an existing train record
When
The system evaluates the deletion operation result
Then
If deletion was successful, proceed to insert new train record; if deletion failed, report database operation error
R-GCX146-cbl-01164
Insert Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Insert Successful?' is invoked, and assuming that an insert operation has been performed for a new train record, when the system evaluates the insertion operation result, the desired outcome is that if insertion was successful, complete train record operations; if insertion failed, report database operation error.
💻 Technical Criteria
Given
An insert operation has been performed for a new train record
When
The system evaluates the insertion operation result
Then
If insertion was successful, complete train record operations; if insertion failed, report database operation error
R-GCX146-cbl-01166
Database Operation Error
Process Rules
📊 Business Logic Narrative
When the process 'Database Operation Error' is invoked, and assuming that a database operation (delete or insert) has been attempted on train records, when the database operation fails to complete successfully, the desired outcome is that the system should report a database operation error and halt further processing of the train record.
💻 Technical Criteria
Given
A database operation (delete or insert) has been attempted on train records
When
The database operation fails to complete successfully
Then
The system should report a database operation error and halt further processing of the train record
R-GCX146-cbl-01167
Initialize Report Message Format
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Report Message Format' is invoked, and assuming that a customer report needs to be generated, when the system begins report message creation process, the desired outcome is that the report message format is initialized and ready to receive content.
💻 Technical Criteria
Given
A customer report needs to be generated
When
The system begins report message creation process
Then
The report message format is initialized and ready to receive content
R-GCX146-cbl-01168
Set Message Type to GCT1401E
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Message Type to GCT1401E' is invoked, and assuming that a customer report message is being prepared, when the system sets up the message structure, the desired outcome is that the message type is configured as gct1401e for proper routing and processing.
💻 Technical Criteria
Given
A customer report message is being prepared
When
The system sets up the message structure
Then
The message type is configured as GCT1401E for proper routing and processing
R-GCX146-cbl-01169
Configure Message Queue Routing
Process Rules
📊 Business Logic Narrative
When the process 'Configure Message Queue Routing' is invoked, and assuming that a customer report message type has been set, when the system configures message routing, the desired outcome is that the message queue is configured to use alt-pcb2 for proper distribution routing.
💻 Technical Criteria
Given
A customer report message type has been set
When
The system configures message routing
Then
The message queue is configured to use ALT-PCB2 for proper distribution routing
R-GCX146-cbl-01170
Move Report Content to Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Move Report Content to Message Buffer' is invoked, and assuming that customer report content exists in gcx140-input and message routing is configured, when the system prepares to queue the message, the desired outcome is that the report content is moved to the message buffer for distribution.
💻 Technical Criteria
Given
Customer report content exists in GCX140-INPUT and message routing is configured
When
The system prepares to queue the message
Then
The report content is moved to the message buffer for distribution
R-GCX146-cbl-01171
Queue Message for Distribution
Action Rules
📊 Business Logic Narrative
When the process 'Queue Message for Distribution' is invoked, and assuming that customer report content has been moved to message buffer, when the system processes the message for distribution, the desired outcome is that the message is queued in the distribution system for delivery to recipients.
💻 Technical Criteria
Given
Customer report content has been moved to message buffer
When
The system processes the message for distribution
Then
The message is queued in the distribution system for delivery to recipients
R-GCX146-cbl-01172
Process Message Queue Commands
Process Rules
📊 Business Logic Narrative
When the process 'Process Message Queue Commands' is invoked, and assuming that customer report message has been queued for distribution, when the system executes queue processing commands, the desired outcome is that the queued message commands are processed to complete the distribution.
💻 Technical Criteria
Given
Customer report message has been queued for distribution
When
The system executes queue processing commands
Then
The queued message commands are processed to complete the distribution
R-GCX146-cbl-01173
Purge Temporary Message Data
Process Rules
📊 Business Logic Narrative
When the process 'Purge Temporary Message Data' is invoked, and assuming that customer report message queue commands have been processed, when the system completes message distribution, the desired outcome is that temporary message data is purged to clean up system resources.
💻 Technical Criteria
Given
Customer report message queue commands have been processed
When
The system completes message distribution
Then
Temporary message data is purged to clean up system resources
R-GCX146-cbl-01174
Customer Report Message Ready for Distribution
Validation Rules
📊 Business Logic Narrative
When the process 'Customer Report Message Ready for Distribution' is invoked, and assuming that customer report message has been processed and temporary data purged, when the system completes all message preparation steps, the desired outcome is that the customer report message is confirmed ready for distribution to designated recipients.
💻 Technical Criteria
Given
Customer report message has been processed and temporary data purged
When
The system completes all message preparation steps
Then
The customer report message is confirmed ready for distribution to designated recipients
🔁 EDI, Status & Database
384 logic blocks
R-GCX146-cbl-00002
2:SCAC Access Validation
Authorization Rules
📊 Business Logic Narrative
When the process '2:SCAC Access Validation' is invoked, and assuming that a user submits a train manifest request with a specific scac code, when the system validates scac access permissions for the user, the desired outcome is that if scac access is invalid and the request is not an aei train send, the system generates error 36 and rolls back the transaction.
💻 Technical Criteria
Given
A user submits a train manifest request with a specific SCAC code
When
The system validates SCAC access permissions for the user
Then
If SCAC access is invalid AND the request is not an AEI train send, the system generates error 36 and rolls back the transaction
R-GCX146-cbl-00003
3:Request Type Validation
Validation Rules
📊 Business Logic Narrative
When the process '3:Request Type Validation' is invoked, and assuming that an input message is received for train manifest processing, when the system examines the request type flags, the desired outcome is that the request must be classified as add, verify, or notify; if none of these flags are set, the input is marked as invalid.
💻 Technical Criteria
Given
An input message is received for train manifest processing
When
The system examines the request type flags
Then
The request must be classified as ADD, VERIFY, or NOTIFY; if none of these flags are set, the input is marked as invalid
R-GCX146-cbl-00004
4:Date and Time Processing
Computation Rules
📊 Business Logic Narrative
When the process '4:Date and Time Processing' is invoked, and assuming that the system needs to validate estimated time of arrival dates, when date range calculations are performed, the desired outcome is that the system calculates n30 (minus 30 days), p05 (plus 5 days), n02 (minus 2 days), and p02 (plus 2 days) from current date for validation boundaries.
💻 Technical Criteria
Given
The system needs to validate estimated time of arrival dates
When
Date range calculations are performed
Then
The system calculates N30 (minus 30 days), P05 (plus 5 days), N02 (minus 2 days), and P02 (plus 2 days) from current date for validation boundaries
R-GCX146-cbl-00005
5:ETA Date Range Validation
Validation Rules
📊 Business Logic Narrative
When the process '5:ETA Date Range Validation' is invoked, and assuming that a user submits a train manifest with an estimated time of arrival, when the system validates the eta date against user-specific date ranges, the desired outcome is that for 's' type users, eta must be between n30 and p05 dates (error 25 if violated); for other users, eta must be between n02 and p02 dates (error 35 if violated).
💻 Technical Criteria
Given
A user submits a train manifest with an estimated time of arrival
When
The system validates the ETA date against user-specific date ranges
Then
For 'S' type users, ETA must be between N30 and P05 dates (error 25 if violated); for other users, ETA must be between N02 and P02 dates (error 35 if violated)
R-GCX146-cbl-00009
9:Train Record Management
Action Rules
📊 Business Logic Narrative
When the process '9:Train Record Management' is invoked, and assuming that a train manifest operation requires database record management, when the system performs train record operations, the desired outcome is that for add operations, existing train records are deleted and new records are inserted with sent status; for other operations, records are retrieved for validation.
💻 Technical Criteria
Given
A train manifest operation requires database record management
When
The system performs train record operations
Then
For ADD operations, existing train records are deleted and new records are inserted with SENT status; for other operations, records are retrieved for validation
R-GCX146-cbl-00022
23:AEI Logging
Process Rules
📊 Business Logic Narrative
When the process '23:AEI Logging' is invoked, and assuming that an aei train send operation is performed, when the system logs aei activity, the desired outcome is that aei send activity is logged regardless of processing errors for audit trail and tracking purposes.
💻 Technical Criteria
Given
An AEI train send operation is performed
When
The system logs AEI activity
Then
AEI send activity is logged regardless of processing errors for audit trail and tracking purposes
R-GCX146-cbl-00023
24:Confirmation Message Generation
Action Rules
📊 Business Logic Narrative
When the process '24:Confirmation Message Generation' is invoked, and assuming that train manifest processing has completed, when the system generates confirmation messages, the desired outcome is that successful operations generate confirmation messages to originating terminals; failed operations generate error notifications with appropriate error codes.
💻 Technical Criteria
Given
Train manifest processing has completed
When
The system generates confirmation messages
Then
Successful operations generate confirmation messages to originating terminals; failed operations generate error notifications with appropriate error codes
R-GCX146-cbl-00026
27:Error Message Processing
Action Rules
📊 Business Logic Narrative
When the process '27:Error Message Processing' is invoked, and assuming that validation errors are detected during processing, when the system processes error messages, the desired outcome is that error messages are formatted with appropriate error codes and descriptions, then distributed to supervisors and originating terminals for resolution.
💻 Technical Criteria
Given
Validation errors are detected during processing
When
The system processes error messages
Then
Error messages are formatted with appropriate error codes and descriptions, then distributed to supervisors and originating terminals for resolution
R-GCX146-cbl-00037
Message Available in Queue?
Validation Rules
📊 Business Logic Narrative
When the process 'Message Available in Queue?' is invoked, and assuming that a readq operation has been performed on the message queue, when the system checks the return code from the readq operation, the desired outcome is that if return code is zero, a message is available; if return code is non-zero, no message is available.
💻 Technical Criteria
Given
A READQ operation has been performed on the message queue
When
The system checks the return code from the READQ operation
Then
If return code is zero, a message is available; if return code is non-zero, no message is available
R-GCX146-cbl-00039
Get Message Length
Process Rules
📊 Business Logic Narrative
When the process 'Get Message Length' is invoked, and assuming that a message has been moved to the input-message buffer, when the system needs to know the message boundaries, the desired outcome is that the message length is determined and stored for processing validation.
💻 Technical Criteria
Given
A message has been moved to the INPUT-MESSAGE buffer
When
The system needs to know the message boundaries
Then
The message length is determined and stored for processing validation
R-GCX146-cbl-00040
Set Return Code to Continue Processing
Process Rules
📊 Business Logic Narrative
When the process 'Set Return Code to Continue Processing' is invoked, and assuming that a message has been successfully retrieved and prepared for processing, when the system needs to indicate processing should continue, the desired outcome is that the return code is set to zero to signal continuation of the message retrieval loop.
💻 Technical Criteria
Given
A message has been successfully retrieved and prepared for processing
When
The system needs to indicate processing should continue
Then
The return code is set to zero to signal continuation of the message retrieval loop
R-GCX146-cbl-00042
Proceed to Message Validation
Process Rules
📊 Business Logic Narrative
When the process 'Proceed to Message Validation' is invoked, and assuming that a message has been successfully retrieved and prepared, when the return code indicates continuation of processing, the desired outcome is that the system proceeds to the next phase of message validation and processing.
💻 Technical Criteria
Given
A message has been successfully retrieved and prepared
When
The return code indicates continuation of processing
Then
The system proceeds to the next phase of message validation and processing
R-GCX146-cbl-00044
Extract User ID from Input Message
Process Rules
📊 Business Logic Narrative
When the process 'Extract User ID from Input Message' is invoked, and assuming that an input message is received for processing, when the system begins scac access validation, the desired outcome is that the user id is extracted from the input message for authorization checking.
💻 Technical Criteria
Given
An input message is received for processing
When
The system begins SCAC access validation
Then
The user ID is extracted from the input message for authorization checking
R-GCX146-cbl-00046
Call GCCSCAC Module for Validation
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCSCAC Module for Validation' is invoked, and assuming that user id and scac code have been extracted, when authorization validation is required, the desired outcome is that the gccscac module is called to validate user access to the scac code.
💻 Technical Criteria
Given
User ID and SCAC code have been extracted
When
Authorization validation is required
Then
The GCCSCAC module is called to validate user access to the SCAC code
R-GCX146-cbl-00047
Check GCCSCAC-FLAG Result
Decision Rules
📊 Business Logic Narrative
When the process 'Check GCCSCAC-FLAG Result' is invoked, and assuming that gccscac module has completed validation, when the validation result flag is checked, the desired outcome is that the system determines whether scac access is valid based on the returned flag.
💻 Technical Criteria
Given
GCCSCAC module has completed validation
When
The validation result flag is checked
Then
The system determines whether SCAC access is valid based on the returned flag
R-GCX146-cbl-00048
Set Access Granted Flag
Authorization Rules
📊 Business Logic Narrative
When the process 'Set Access Granted Flag' is invoked, and assuming that scac validation has been performed, when the scac access is determined to be valid, the desired outcome is that the access granted flag is set and processing continues.
💻 Technical Criteria
Given
SCAC validation has been performed
When
The SCAC access is determined to be valid
Then
The access granted flag is set and processing continues
R-GCX146-cbl-00049
Is AEI Train Send Request?
Decision Rules
📊 Business Logic Narrative
When the process 'Is AEI Train Send Request?' is invoked, and assuming that scac access validation has failed, when the system checks the request type, the desired outcome is that if the request is not an aei train send, access is denied with error 36, otherwise processing continues.
💻 Technical Criteria
Given
SCAC access validation has failed
When
The system checks the request type
Then
If the request is NOT an AEI train send, access is denied with Error 36, otherwise processing continues
R-GCX146-cbl-00050
Generate Error 36 - Access Denied
Policy Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Error 36 - Access Denied', assuming that scac access validation has failed, when the request is not an aei train send, the desired outcome is that error 36 is generated indicating access denied due to invalid scac authorization.
💻 Technical Criteria
EXCLUDING
SCAC access validation has failed
When
The request is not an AEI train send
Then
Error 36 is generated indicating access denied due to invalid SCAC authorization
R-GCX146-cbl-00051
Set Rollback Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Rollback Flag' is invoked, and assuming that access denied error has been generated, when transaction rollback is required, the desired outcome is that the rollback flag is set to ensure no partial updates are committed.
💻 Technical Criteria
Given
Access denied error has been generated
When
Transaction rollback is required
Then
The rollback flag is set to ensure no partial updates are committed
R-GCX146-cbl-00060
Capture Current System Date and Time
Computation Rules
📊 Business Logic Narrative
When the process 'Capture Current System Date and Time' is invoked, and assuming that the date and time processing routine is initiated, when the system needs to establish current date and time, the desired outcome is that the current system date and time are captured and stored for subsequent calculations.
💻 Technical Criteria
Given
The date and time processing routine is initiated
When
The system needs to establish current date and time
Then
The current system date and time are captured and stored for subsequent calculations
R-GCX146-cbl-00061
Calculate 30 Days Before Current Date
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate 30 Days Before Current Date' is invoked, and assuming that the current system date is available, when a 30-day lookback date range is required for supervisor-level eta validation, the desired outcome is that the system calculates and stores a date that is exactly 30 days before the current date.
💻 Technical Criteria
Given
The current system date is available
When
A 30-day lookback date range is required for supervisor-level ETA validation
Then
The system calculates and stores a date that is exactly 30 days before the current date
R-GCX146-cbl-00062
Calculate 5 Days After Current Date
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate 5 Days After Current Date' is invoked, and assuming that the current system date is available, when a 5-day forward date range is required for supervisor-level eta validation, the desired outcome is that the system calculates and stores a date that is exactly 5 days after the current date.
💻 Technical Criteria
Given
The current system date is available
When
A 5-day forward date range is required for supervisor-level ETA validation
Then
The system calculates and stores a date that is exactly 5 days after the current date
R-GCX146-cbl-00063
Calculate 2 Days Before Current Date
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate 2 Days Before Current Date' is invoked, and assuming that the current system date is available, when a 2-day lookback date range is required for standard user eta validation, the desired outcome is that the system calculates and stores a date that is exactly 2 days before the current date.
💻 Technical Criteria
Given
The current system date is available
When
A 2-day lookback date range is required for standard user ETA validation
Then
The system calculates and stores a date that is exactly 2 days before the current date
R-GCX146-cbl-00064
Calculate 2 Days After Current Date
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate 2 Days After Current Date' is invoked, and assuming that the current system date is available, when a 2-day forward date range is required for standard user eta validation, the desired outcome is that the system calculates and stores a date that is exactly 2 days after the current date.
💻 Technical Criteria
Given
The current system date is available
When
A 2-day forward date range is required for standard user ETA validation
Then
The system calculates and stores a date that is exactly 2 days after the current date
R-GCX146-cbl-00066
Store Calculated Date Ranges for ETA Validation
Process Rules
📊 Business Logic Narrative
When the process 'Store Calculated Date Ranges for ETA Validation' is invoked, and assuming that all date calculations (30-day lookback, 5-day forward, 2-day lookback, 2-day forward) are completed, when the date ranges need to be preserved for eta validation, the desired outcome is that all calculated date ranges are stored in working storage variables for use in eta validation routines.
💻 Technical Criteria
Given
All date calculations (30-day lookback, 5-day forward, 2-day lookback, 2-day forward) are completed
When
The date ranges need to be preserved for ETA validation
Then
All calculated date ranges are stored in working storage variables for use in ETA validation routines
R-GCX146-cbl-00067
Calculate Date Ranges Using DATECALC
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Date Ranges Using DATECALC' is invoked, and assuming that current date is available in the system, when eta validation process is initiated, the desired outcome is that standard date range of minus 2 days to plus 2 days from current date is calculated and extended date range of minus 30 days to plus 5 days from current date is calculated.
💻 Technical Criteria
Given
Current date is available in the system
When
ETA validation process is initiated
Then
Standard date range of minus 2 days to plus 2 days from current date is calculated AND extended date range of minus 30 days to plus 5 days from current date is calculated
R-GCX146-cbl-00068
Get User Type from GCSTBRT-US-CTF-ADD
Action Rules
📊 Business Logic Narrative
When the process 'Get User Type from GCSTBRT-US-CTF-ADD' is invoked, and assuming that user is authenticated and has a profile in gcstbrt-us-ctf-add, when eta validation is performed, the desired outcome is that user type is retrieved from the user profile for date range determination.
💻 Technical Criteria
Given
User is authenticated and has a profile in GCSTBRT-US-CTF-ADD
When
ETA validation is performed
Then
User type is retrieved from the user profile for date range determination
R-GCX146-cbl-00069
User Type = 'S' Special User?
Decision Rules
📊 Business Logic Narrative
When the process 'User Type = 'S' Special User?' is invoked, and assuming that user type has been retrieved from user profile, when user type equals 's' (special user), the desired outcome is that extended date range of minus 30 days to plus 5 days is applied for eta validation.
💻 Technical Criteria
Given
User type has been retrieved from user profile
When
User type equals 'S' (Special User)
Then
Extended date range of minus 30 days to plus 5 days is applied for ETA validation
R-GCX146-cbl-00070
User Type = 'S' Special User?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'User Type = 'S' Special User?', assuming that user type has been retrieved from user profile, when user type is not equal to 's' (not special user), the desired outcome is that standard date range of minus 2 days to plus 2 days is applied for eta validation.
💻 Technical Criteria
EXCLUDING
User type has been retrieved from user profile
When
User type is not equal to 'S' (not Special User)
Then
Standard date range of minus 2 days to plus 2 days is applied for ETA validation
R-GCX146-cbl-00071
Validate ETA Date Using ISDATECV
Validation Rules
📊 Business Logic Narrative
When the process 'Validate ETA Date Using ISDATECV' is invoked, and assuming that eta date is provided in the train request, when date format validation is performed using isdatecv, the desired outcome is that eta date format is validated and confirmed as a legitimate calendar date.
💻 Technical Criteria
Given
ETA date is provided in the train request
When
Date format validation is performed using ISDATECV
Then
ETA date format is validated and confirmed as a legitimate calendar date
R-GCX146-cbl-00074
Validate Time Format HH:MM
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Time Format HH:MM' is invoked, and assuming that eta time is provided in the train request, when time format validation is performed, the desired outcome is that time format is validated as hh:mm where hours are 00-23 and minutes are 00-59 or time format error is generated for invalid format.
💻 Technical Criteria
Given
ETA time is provided in the train request
When
Time format validation is performed
Then
Time format is validated as HH:MM where hours are 00-23 and minutes are 00-59 OR time format error is generated for invalid format
R-GCX146-cbl-00075
Extract PUBLIC Merlin ID
Action Rules
📊 Business Logic Narrative
When the process 'Extract PUBLIC Merlin ID' is invoked, and assuming that the admin table segment is available in gcstbrt database, when the system processes merlin id extraction, the desired outcome is that the public merlin id is extracted from the admin table and stored for validation.
💻 Technical Criteria
Given
The admin table segment is available in GCSTBRT database
When
The system processes Merlin ID extraction
Then
The PUBLIC Merlin ID is extracted from the admin table and stored for validation
R-GCX146-cbl-00076
Extract DC-P Merlin ID
Action Rules
📊 Business Logic Narrative
When the process 'Extract DC-P Merlin ID' is invoked, and assuming that the admin table segment is available in gcstbrt database, when the system processes merlin id extraction, the desired outcome is that the dc-p merlin id is extracted from the admin table and stored for validation.
💻 Technical Criteria
Given
The admin table segment is available in GCSTBRT database
When
The system processes Merlin ID extraction
Then
The DC-P Merlin ID is extracted from the admin table and stored for validation
R-GCX146-cbl-00077
Extract SUPERVISOR Merlin ID
Action Rules
📊 Business Logic Narrative
When the process 'Extract SUPERVISOR Merlin ID' is invoked, and assuming that the terminal table segment is available in gcstbrt database, when the system processes merlin id extraction, the desired outcome is that the supervisor merlin id is extracted from the terminal table and stored for validation.
💻 Technical Criteria
Given
The terminal table segment is available in GCSTBRT database
When
The system processes Merlin ID extraction
Then
The SUPERVISOR Merlin ID is extracted from the terminal table and stored for validation
R-GCX146-cbl-00078
Extract ALTERNATE Merlin ID
Action Rules
📊 Business Logic Narrative
When the process 'Extract ALTERNATE Merlin ID' is invoked, and assuming that the terminal table segment is available in gcstbrt database, when the system processes merlin id extraction, the desired outcome is that the alternate merlin id is extracted from the terminal table and stored for validation.
💻 Technical Criteria
Given
The terminal table segment is available in GCSTBRT database
When
The system processes Merlin ID extraction
Then
The ALTERNATE Merlin ID is extracted from the terminal table and stored for validation
R-GCX146-cbl-00079
PUBLIC ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'PUBLIC ID Valid?' is invoked, and assuming that a public merlin id has been extracted from the admin table, when the system validates the public merlin id against the emtz database, the desired outcome is that if the public merlin id exists in emtz database, validation passes, otherwise validation fails with error 4.
💻 Technical Criteria
Given
A PUBLIC Merlin ID has been extracted from the admin table
When
The system validates the PUBLIC Merlin ID against the EMTZ database
Then
If the PUBLIC Merlin ID exists in EMTZ database, validation passes, otherwise validation fails with error 4
R-GCX146-cbl-00080
SUPERVISOR ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'SUPERVISOR ID Valid?' is invoked, and assuming that a supervisor merlin id has been extracted from the terminal table and the public merlin id validation has passed, when the system validates the supervisor merlin id against the emtz database, the desired outcome is that if the supervisor merlin id exists in emtz database, validation passes, otherwise validation fails with error 5.
💻 Technical Criteria
Given
A SUPERVISOR Merlin ID has been extracted from the terminal table AND the PUBLIC Merlin ID validation has passed
When
The system validates the SUPERVISOR Merlin ID against the EMTZ database
Then
If the SUPERVISOR Merlin ID exists in EMTZ database, validation passes, otherwise validation fails with error 5
R-GCX146-cbl-00083
SYSTEM-FAX ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'SYSTEM-FAX ID Valid?' is invoked, and assuming that the system-fax merlin id needs validation and the dc-p merlin id validation has passed, when the system validates the system-fax merlin id against the emtz database, the desired outcome is that if the system-fax merlin id exists in emtz database, validation passes, otherwise validation fails with error 8.
💻 Technical Criteria
Given
The SYSTEM-FAX Merlin ID needs validation AND the DC-P Merlin ID validation has passed
When
The system validates the SYSTEM-FAX Merlin ID against the EMTZ database
Then
If the SYSTEM-FAX Merlin ID exists in EMTZ database, validation passes, otherwise validation fails with error 8
R-GCX146-cbl-00086
Extract Train Number from Input
Process Rules
📊 Business Logic Narrative
When the process 'Extract Train Number from Input' is invoked, and assuming that an input message containing train identification data, when the system processes the train id construction request, the desired outcome is that the train number component is extracted from the input message and stored for further processing.
💻 Technical Criteria
Given
An input message containing train identification data
When
The system processes the train ID construction request
Then
The train number component is extracted from the input message and stored for further processing
R-GCX146-cbl-00087
Extract Train Day from Input
Process Rules
📊 Business Logic Narrative
When the process 'Extract Train Day from Input' is invoked, and assuming that an input message containing train identification data, when the system processes the train id construction request, the desired outcome is that the train day component is extracted from the input message and stored for further processing.
💻 Technical Criteria
Given
An input message containing train identification data
When
The system processes the train ID construction request
Then
The train day component is extracted from the input message and stored for further processing
R-GCX146-cbl-00088
Extract From Station Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract From Station Code' is invoked, and assuming that an input message containing train identification data, when the system processes the train id construction request, the desired outcome is that the from station code is extracted from the input message and stored for further processing.
💻 Technical Criteria
Given
An input message containing train identification data
When
The system processes the train ID construction request
Then
The from station code is extracted from the input message and stored for further processing
R-GCX146-cbl-00089
Extract To Station Code
Process Rules
📊 Business Logic Narrative
When the process 'Extract To Station Code' is invoked, and assuming that an input message containing train identification data, when the system processes the train id construction request, the desired outcome is that the to station code is extracted from the input message and stored for further processing.
💻 Technical Criteria
Given
An input message containing train identification data
When
The system processes the train ID construction request
Then
The to station code is extracted from the input message and stored for further processing
R-GCX146-cbl-00090
Extract Consist Number
Process Rules
📊 Business Logic Narrative
When the process 'Extract Consist Number' is invoked, and assuming that an input message containing train identification data, when the system processes the train id construction request, the desired outcome is that the consist number is extracted from the input message and stored for further processing.
💻 Technical Criteria
Given
An input message containing train identification data
When
The system processes the train ID construction request
Then
The consist number is extracted from the input message and stored for further processing
R-GCX146-cbl-00092
Replace Spaces with Zeros in All Components
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros in All Components' is invoked, and assuming that train id components have been extracted from the input message, when any component contains spaces, the desired outcome is that all spaces in train number, day, from station, to station, and consist number are replaced with zeros.
💻 Technical Criteria
Given
Train ID components have been extracted from the input message
When
Any component contains spaces
Then
All spaces in train number, day, from station, to station, and consist number are replaced with zeros
R-GCX146-cbl-00096
Set Train ID for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Set Train ID for Processing' is invoked, and assuming that the train id has been constructed and validated successfully, when the train id format validation passes, the desired outcome is that the train id is set as valid and ready for use in downstream processing.
💻 Technical Criteria
Given
The train ID has been constructed and validated successfully
When
The train ID format validation passes
Then
The train ID is set as valid and ready for use in downstream processing
R-GCX146-cbl-00097
Search Station Configuration Table
Action Rules
📊 Business Logic Narrative
When the process 'Search Station Configuration Table' is invoked, and assuming that a from-station code has been extracted from the input message, when the system searches the station configuration table for the station code, the desired outcome is that the system retrieves the corresponding station data if found, or proceeds to validation checks if not found.
💻 Technical Criteria
Given
A from-station code has been extracted from the input message
When
The system searches the station configuration table for the station code
Then
The system retrieves the corresponding station data if found, or proceeds to validation checks if not found
R-GCX146-cbl-00098
Station Code = '0000'?
Validation Rules
📊 Business Logic Narrative
When the process 'Station Code = '0000'?' is invoked, and assuming that a station has been found in the station configuration table, when the station code equals '0000', the desired outcome is that the system sets a station validation error indicating invalid canadian station code.
💻 Technical Criteria
Given
A station has been found in the station configuration table
When
The station code equals '0000'
Then
The system sets a station validation error indicating invalid Canadian station code
R-GCX146-cbl-00099
Request Type = VERIFY?
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Request Type = VERIFY?', assuming that a station code was not found in the station configuration table, when the request type is verify, the desired outcome is that the system continues processing despite the missing station information.
💻 Technical Criteria
EXCLUDING
A station code was not found in the station configuration table
When
The request type is VERIFY
Then
The system continues processing despite the missing station information
R-GCX146-cbl-00100
Auto-FAX Enabled?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Auto-FAX Enabled?', assuming that a valid station has been found and station code is not '0000', when the system checks the auto-fax configuration for the station, the desired outcome is that if auto-fax is enabled, the system validates fax settings; otherwise, station validation is successful.
💻 Technical Criteria
EXCLUDING
A valid station has been found and station code is not '0000'
When
The system checks the auto-FAX configuration for the station
Then
If auto-FAX is enabled, the system validates FAX settings; otherwise, station validation is successful
R-GCX146-cbl-00101
Set Station Validation Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Station Validation Error', assuming that a station code was not found in the station configuration table, when the request type is not verify, the desired outcome is that the system sets a station validation error and fails the validation process.
💻 Technical Criteria
EXCLUDING
A station code was not found in the station configuration table
When
The request type is not VERIFY
Then
The system sets a station validation error and fails the validation process
R-GCX146-cbl-00102
Check for Existing Train Records
Validation Rules
📊 Business Logic Narrative
When the process 'Check for Existing Train Records' is invoked, and assuming that a train id is provided for processing, when the system checks the train records database, the desired outcome is that the system determines whether a train record exists for the given train id.
💻 Technical Criteria
Given
A train ID is provided for processing
When
The system checks the train records database
Then
The system determines whether a train record exists for the given train ID
R-GCX146-cbl-00104
Validate Record Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Record Status' is invoked, and assuming that an existing train record is retrieved, when the system examines the record status, the desired outcome is that the system determines if the record is active, deleted, or in another status state.
💻 Technical Criteria
Given
An existing train record is retrieved
When
The system examines the record status
Then
The system determines if the record is active, deleted, or in another status state
R-GCX146-cbl-00105
Record Marked as Deleted?
Decision Rules
📊 Business Logic Narrative
When the process 'Record Marked as Deleted?' is invoked, and assuming that a train record exists with a status indicator, when the system checks the deletion status flag, the desired outcome is that the system identifies whether the record is marked as deleted or active.
💻 Technical Criteria
Given
A train record exists with a status indicator
When
The system checks the deletion status flag
Then
The system identifies whether the record is marked as deleted or active
R-GCX146-cbl-00106
Delete Existing Train Record
Action Rules
📊 Business Logic Narrative
When the process 'Delete Existing Train Record' is invoked, and assuming that a train record is marked as deleted, when the system processes the deletion request, the desired outcome is that the train record is permanently removed from the database.
💻 Technical Criteria
Given
A train record is marked as deleted
When
The system processes the deletion request
Then
The train record is permanently removed from the database
R-GCX146-cbl-00107
Deletion Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Deletion Successful?' is invoked, and assuming that a deletion operation has been attempted on a train record, when the system checks the deletion result, the desired outcome is that the system confirms whether the deletion was successful or failed.
💻 Technical Criteria
Given
A deletion operation has been attempted on a train record
When
The system checks the deletion result
Then
The system confirms whether the deletion was successful or failed
R-GCX146-cbl-00108
Create New Train Record
Action Rules
📊 Business Logic Narrative
When the process 'Create New Train Record' is invoked, and assuming that no existing train record exists or an existing record has been successfully deleted, when the system creates a new train record, the desired outcome is that a new train record is inserted with status 'sent' and all required train information.
💻 Technical Criteria
Given
No existing train record exists or an existing record has been successfully deleted
When
The system creates a new train record
Then
A new train record is inserted with status 'SENT' and all required train information
R-GCX146-cbl-00111
Handle Database Error
Action Rules
📊 Business Logic Narrative
When the process 'Handle Database Error' is invoked, and assuming that a database operation has failed during train record processing, when the system encounters the database error, the desired outcome is that the system initiates error handling procedures to manage the failure.
💻 Technical Criteria
Given
A database operation has failed during train record processing
When
The system encounters the database error
Then
The system initiates error handling procedures to manage the failure
R-GCX146-cbl-00112
Log Error and Abort
Action Rules
📊 Business Logic Narrative
When the process 'Log Error and Abort' is invoked, and assuming that a critical database error has occurred that cannot be recovered, when the system processes the error condition, the desired outcome is that the error is logged and processing is aborted to prevent data corruption.
💻 Technical Criteria
Given
A critical database error has occurred that cannot be recovered
When
The system processes the error condition
Then
The error is logged and processing is aborted to prevent data corruption
R-GCX146-cbl-01438
Validate Search Parameter Combination
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Search Parameter Combination' is invoked, and assuming that all search parameters have been configured, when parameter combination validation is performed, the desired outcome is that system verifies that the parameter combination is valid and compatible for search execution.
💻 Technical Criteria
Given
All search parameters have been configured
When
Parameter combination validation is performed
Then
System verifies that the parameter combination is valid and compatible for search execution
R-GCX146-cbl-01440
Search Configuration Error
Validation Rules
📊 Business Logic Narrative
When the process 'Search Configuration Error' is invoked, and assuming that search parameters have been configured, when parameter validation fails due to incompatible combination, the desired outcome is that system sets search configuration error status and prevents search execution.
💻 Technical Criteria
Given
Search parameters have been configured
When
Parameter validation fails due to incompatible combination
Then
System sets search configuration error status and prevents search execution
R-GCX146-cbl-01583
Search Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Search Successful?' is invoked, and assuming that fwcarget module has completed the search operation, when the system checks the search result status, the desired outcome is that the system should determine whether the search was successful or failed based on the return status.
💻 Technical Criteria
Given
FWCARGET module has completed the search operation
When
The system checks the search result status
Then
The system should determine whether the search was successful or failed based on the return status
R-GCX146-cbl-00278
Handle EDI Transmission Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle EDI Transmission Error' is invoked, and assuming that an error occurs during edi record validation or transmission, when the system encounters the error condition, the desired outcome is that appropriate error handling procedures are executed to manage the failure.
💻 Technical Criteria
Given
An error occurs during EDI record validation or transmission
When
The system encounters the error condition
Then
Appropriate error handling procedures are executed to manage the failure
R-GCX146-cbl-00294
Log AEI Train Send Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log AEI Train Send Activity' is invoked, and assuming that an aei train send process has been completed (successful or failed), when the system finalizes the aei process, the desired outcome is that the system logs the train send activity with timestamp, user information, and transmission status.
💻 Technical Criteria
Given
An AEI train send process has been completed (successful or failed)
When
The system finalizes the AEI process
Then
The system logs the train send activity with timestamp, user information, and transmission status
R-GCX146-cbl-00295
Create Audit Trail Entry
Action Rules
📊 Business Logic Narrative
When the process 'Create Audit Trail Entry' is invoked, and assuming that an aei train send operation has been logged, when the system creates audit records, the desired outcome is that the system generates detailed audit trail entries in the audit database with transaction details, user identification, and processing results.
💻 Technical Criteria
Given
An AEI train send operation has been logged
When
The system creates audit records
Then
The system generates detailed audit trail entries in the audit database with transaction details, user identification, and processing results
R-GCX146-cbl-00296
Determine Message Type
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Message Type' is invoked, and assuming that a train processing operation has completed, when the system evaluates the processing outcome, the desired outcome is that the system selects success confirmation message type if no errors occurred, otherwise selects error confirmation message type.
💻 Technical Criteria
Given
A train processing operation has completed
When
The system evaluates the processing outcome
Then
The system selects success confirmation message type if no errors occurred, otherwise selects error confirmation message type
R-GCX146-cbl-00297
Create Success Confirmation Message
Action Rules
📊 Business Logic Narrative
When the process 'Create Success Confirmation Message' is invoked, and assuming that train processing has completed successfully with no validation errors, when the system creates a confirmation message, the desired outcome is that the system generates a gct1051e success message with train processing details.
💻 Technical Criteria
Given
Train processing has completed successfully with no validation errors
When
The system creates a confirmation message
Then
The system generates a GCT1051E success message with train processing details
R-GCX146-cbl-00299
Format Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Format Message Content' is invoked, and assuming that a confirmation message type has been determined, when the system formats the message content, the desired outcome is that the system includes train identification, processing status, error details if applicable, and relevant business data in the message format.
💻 Technical Criteria
Given
A confirmation message type has been determined
When
The system formats the message content
Then
The system includes train identification, processing status, error details if applicable, and relevant business data in the message format
R-GCX146-cbl-00300
Set Message Routing
Process Rules
📊 Business Logic Narrative
When the process 'Set Message Routing' is invoked, and assuming that a formatted confirmation message is ready for delivery, when the system sets message routing parameters, the desired outcome is that the system assigns alt-pcb routing, sets message priority, and determines recipient terminals based on message type and business requirements.
💻 Technical Criteria
Given
A formatted confirmation message is ready for delivery
When
The system sets message routing parameters
Then
The system assigns ALT-PCB routing, sets message priority, and determines recipient terminals based on message type and business requirements
R-GCX146-cbl-00301
Queue Message via CSISER
Action Rules
📊 Business Logic Narrative
When the process 'Queue Message via CSISER' is invoked, and assuming that a confirmation message with routing parameters is ready, when the system queues the message via csiser, the desired outcome is that the system adds the message to the processing queue using the appropriate csiser interface methods.
💻 Technical Criteria
Given
A confirmation message with routing parameters is ready
When
The system queues the message via CSISER
Then
The system adds the message to the processing queue using the appropriate CSISER interface methods
R-GCX146-cbl-00302
Initialize CIMS Interface
Action Rules
📊 Business Logic Narrative
When the process 'Initialize CIMS Interface' is invoked, and assuming that messages need to be processed through cims, when the system initializes the cims interface, the desired outcome is that the system establishes connection to cims and prepares for message command processing.
💻 Technical Criteria
Given
Messages need to be processed through CIMS
When
The system initializes the CIMS interface
Then
The system establishes connection to CIMS and prepares for message command processing
R-GCX146-cbl-00303
Add Message Command to Queue
Process Rules
📊 Business Logic Narrative
When the process 'Add Message Command to Queue' is invoked, and assuming that a message is ready for processing through cims, when the system adds the message command to the queue, the desired outcome is that the system queues the appropriate operation (chng for changes, writmsgl for message logging, or purg for purging) based on message type and processing requirements.
💻 Technical Criteria
Given
A message is ready for processing through CIMS
When
The system adds the message command to the queue
Then
The system queues the appropriate operation (CHNG for changes, WRITMSGL for message logging, or PURG for purging) based on message type and processing requirements
R-GCX146-cbl-00306
Send Message to Recipients
Action Rules
📊 Business Logic Narrative
When the process 'Send Message to Recipients' is invoked, and assuming that queued commands have been processed successfully, when the system sends the message to recipients, the desired outcome is that the system delivers the confirmation message to all specified terminals and recipients according to the established routing.
💻 Technical Criteria
Given
Queued commands have been processed successfully
When
The system sends the message to recipients
Then
The system delivers the confirmation message to all specified terminals and recipients according to the established routing
R-GCX146-cbl-00307
Update Message Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Message Status' is invoked, and assuming that a message has been sent to recipients, when the system updates message status, the desired outcome is that the system records the delivery status, timestamp, and any delivery confirmation information.
💻 Technical Criteria
Given
A message has been sent to recipients
When
The system updates message status
Then
The system records the delivery status, timestamp, and any delivery confirmation information
R-GCX146-cbl-00308
Log Confirmation Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log Confirmation Activity' is invoked, and assuming that a confirmation message has been processed and status updated, when the system logs confirmation activity, the desired outcome is that the system creates audit trail entries with message details, processing timestamps, and delivery status for compliance and tracking.
💻 Technical Criteria
Given
A confirmation message has been processed and status updated
When
The system logs confirmation activity
Then
The system creates audit trail entries with message details, processing timestamps, and delivery status for compliance and tracking
R-GCX146-cbl-01255
Extract Train Components from Input
Process Rules
📊 Business Logic Narrative
When the process 'Extract Train Components from Input' is invoked, and assuming that an input message contains train identification data, when the system processes the train information, the desired outcome is that train number, day, from station, to station, and consist number are extracted from the input message.
💻 Technical Criteria
Given
An input message contains train identification data
When
The system processes the train information
Then
Train number, day, from station, to station, and consist number are extracted from the input message
R-GCX146-cbl-01256
Replace Spaces with Zeros
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros' is invoked, and assuming that train identification components may contain spaces, when the system formats train components, the desired outcome is that all spaces in train number, day, from station, to station, and consist number are replaced with zeros.
💻 Technical Criteria
Given
Train identification components may contain spaces
When
The system formats train components
Then
All spaces in train number, day, from station, to station, and consist number are replaced with zeros
R-GCX146-cbl-01258
Retrieve From Station Code
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve From Station Code' is invoked, and assuming that train has from and to station codes, when the system formats station information, the desired outcome is that station codes are retrieved and corresponding station names are formatted for display.
💻 Technical Criteria
Given
Train has from and to station codes
When
The system formats station information
Then
Station codes are retrieved and corresponding station names are formatted for display
R-GCX146-cbl-01261
Validate ETA Date Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate ETA Date Format' is invoked, and assuming that train has an estimated time of arrival, when the system formats eta information, the desired outcome is that eta date format is validated and formatted appropriately for trip sheet display.
💻 Technical Criteria
Given
Train has an estimated time of arrival
When
The system formats ETA information
Then
ETA date format is validated and formatted appropriately for trip sheet display
R-GCX146-cbl-01472
Replace Spaces with Zeros in From Station
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros in From Station' is invoked, and assuming that a from station component has been extracted from the input message, when the from station component contains one or more space characters, the desired outcome is that all space characters in the from station component are replaced with zero characters.
💻 Technical Criteria
Given
A from station component has been extracted from the input message
When
The from station component contains one or more space characters
Then
All space characters in the from station component are replaced with zero characters
R-GCX146-cbl-01473
Replace Spaces with Zeros in To Station
Validation Rules
📊 Business Logic Narrative
When the process 'Replace Spaces with Zeros in To Station' is invoked, and assuming that a to station component has been extracted from the input message, when the to station component contains one or more space characters, the desired outcome is that all space characters in the to station component are replaced with zero characters.
💻 Technical Criteria
Given
A to station component has been extracted from the input message
When
The to station component contains one or more space characters
Then
All space characters in the to station component are replaced with zero characters
R-GCX146-cbl-01633
Load Status Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Load Status Valid?' is invoked, and assuming that load status has been validated against requirements, when system checks load status validity, the desired outcome is that processing continues with status update if valid, or validation error is set if invalid.
💻 Technical Criteria
Given
Load status has been validated against requirements
When
System checks load status validity
Then
Processing continues with status update if valid, or validation error is set if invalid
R-GCX146-cbl-01772
Set Load Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Load Status Flag' is invoked, and assuming that load requirements validation has been completed successfully, when the system processes the validation result, the desired outcome is that the appropriate load status flag is set to indicate successful validation.
💻 Technical Criteria
Given
Load requirements validation has been completed successfully
When
The system processes the validation result
Then
The appropriate load status flag is set to indicate successful validation
R-GCX146-cbl-01774
Set Error Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Error Flag' is invoked, and assuming that a load status mismatch error has been generated, when the system processes the error condition, the desired outcome is that an error flag is set to indicate that load status validation has failed.
💻 Technical Criteria
Given
A load status mismatch error has been generated
When
The system processes the error condition
Then
An error flag is set to indicate that load status validation has failed
R-GCX146-cbl-00343
Set Rollback Flag WS-ROLB
Process Rules
📊 Business Logic Narrative
When the process 'Set Rollback Flag WS-ROLB' is invoked, and assuming that an error has been detected that requires transaction rollback, when the error processing begins, the desired outcome is that the system sets ws-rolb flag to 'y' to indicate that transaction rollback is required.
💻 Technical Criteria
Given
An error has been detected that requires transaction rollback
When
The error processing begins
Then
The system sets WS-ROLB flag to 'Y' to indicate that transaction rollback is required
R-GCX146-cbl-00344
Generate SCAC Access Error 36
Authorization Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate SCAC Access Error 36', assuming that a user is attempting to perform train operations, when the user's scac access is invalid and the operation is not an aei train send, the desired outcome is that the system generates error code 36 for scac access violation.
💻 Technical Criteria
EXCLUDING
A user is attempting to perform train operations
When
The user's SCAC access is invalid AND the operation is not an AEI train send
Then
The system generates error code 36 for SCAC access violation
R-GCX146-cbl-00346
Generate Station Validation Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Station Validation Error', assuming that station information is being validated during train processing, when station codes are invalid, missing, or fail validation rules, the desired outcome is that the system generates appropriate station validation error codes.
💻 Technical Criteria
EXCLUDING
Station information is being validated during train processing
When
Station codes are invalid, missing, or fail validation rules
Then
The system generates appropriate station validation error codes
R-GCX146-cbl-00350
Format Error Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Error Message' is invoked, and assuming that an error code has been assigned for a processing issue, when the error message needs to be prepared for distribution, the desired outcome is that the system formats the error message with error code, description, and relevant context information.
💻 Technical Criteria
Given
An error code has been assigned for a processing issue
When
The error message needs to be prepared for distribution
Then
The system formats the error message with error code, description, and relevant context information
R-GCX146-cbl-00351
Identify Distribution Recipients
Authorization Rules
📊 Business Logic Narrative
When the process 'Identify Distribution Recipients' is invoked, and assuming that an error message has been formatted for distribution, when the system needs to determine who should receive the error notification, the desired outcome is that the system identifies appropriate recipients based on error type, user roles, and notification requirements.
💻 Technical Criteria
Given
An error message has been formatted for distribution
When
The system needs to determine who should receive the error notification
Then
The system identifies appropriate recipients based on error type, user roles, and notification requirements
R-GCX146-cbl-00352
Add Supervisor IDs
Authorization Rules
📊 Business Logic Narrative
When the process 'Add Supervisor IDs' is invoked, and assuming that error distribution recipients are being identified, when the system is building the distribution list for error notifications, the desired outcome is that the system adds supervisor ids from gcstbrt configuration to the distribution list.
💻 Technical Criteria
Given
Error distribution recipients are being identified
When
The system is building the distribution list for error notifications
Then
The system adds supervisor IDs from GCSTBRT configuration to the distribution list
R-GCX146-cbl-00353
Add Designated Personnel
Authorization Rules
📊 Business Logic Narrative
When the process 'Add Designated Personnel' is invoked, and assuming that supervisor ids have been added to the error distribution list, when additional designated personnel need to be notified based on error type, the desired outcome is that the system adds designated personnel ids to the error distribution list based on operational requirements.
💻 Technical Criteria
Given
Supervisor IDs have been added to the error distribution list
When
Additional designated personnel need to be notified based on error type
Then
The system adds designated personnel IDs to the error distribution list based on operational requirements
R-GCX146-cbl-00354
Queue Error Message
Process Rules
📊 Business Logic Narrative
When the process 'Queue Error Message' is invoked, and assuming that error message recipients have been identified and the message is formatted, when the error message is ready for distribution, the desired outcome is that the system queues the error message in ims message queues for delivery to all identified recipients.
💻 Technical Criteria
Given
Error message recipients have been identified and the message is formatted
When
The error message is ready for distribution
Then
The system queues the error message in IMS message queues for delivery to all identified recipients
R-GCX146-cbl-00355
Distribute via Message Queues
Process Rules
📊 Business Logic Narrative
When the process 'Distribute via Message Queues' is invoked, and assuming that error messages have been queued for distribution, when the messaging system processes the queued messages, the desired outcome is that the system distributes error messages to all identified recipients via ims message queues.
💻 Technical Criteria
Given
Error messages have been queued for distribution
When
The messaging system processes the queued messages
Then
The system distributes error messages to all identified recipients via IMS message queues
R-GCX146-cbl-00357
Rollback Transaction
Process Rules
📊 Business Logic Narrative
When the process 'Rollback Transaction' is invoked, and assuming that the rollback flag ws-rolb has been set to 'y' due to an error, when error processing is being completed, the desired outcome is that the system executes transaction rollback to undo any partial changes and maintain data integrity.
💻 Technical Criteria
Given
The rollback flag WS-ROLB has been set to 'Y' due to an error
When
Error processing is being completed
Then
The system executes transaction rollback to undo any partial changes and maintain data integrity
R-GCX146-cbl-00359
Auto-FAX Enabled?
Decision Rules
📊 Business Logic Narrative
When the process 'Auto-FAX Enabled?' is invoked, and assuming that station configuration has been retrieved, when auto-fax flag is set to enabled in station settings, the desired outcome is that the system should proceed with fax routing setup, otherwise proceed to email user lookup.
💻 Technical Criteria
Given
Station configuration has been retrieved
When
Auto-FAX flag is set to enabled in station settings
Then
The system should proceed with FAX routing setup, otherwise proceed to email user lookup
R-GCX146-cbl-00360
Setup FAX Routing
Process Rules
📊 Business Logic Narrative
When the process 'Setup FAX Routing' is invoked, and assuming that auto-fax is enabled for the station, when fax routing needs to be established, the desired outcome is that the system should configure fax routing parameters and proceed to set copy ids.
💻 Technical Criteria
Given
Auto-FAX is enabled for the station
When
FAX routing needs to be established
Then
The system should configure FAX routing parameters and proceed to set copy IDs
R-GCX146-cbl-00361
Get Email User Lists
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Get Email User Lists', assuming that auto-fax is not enabled or fax routing is complete, when email distribution is required, the desired outcome is that the system should lookup email addresses from cusemail table using station code.
💻 Technical Criteria
EXCLUDING
Auto-FAX is not enabled or FAX routing is complete
When
Email distribution is required
Then
The system should lookup email addresses from CUSEMAIL table using station code
R-GCX146-cbl-00369
Primary Email Failed?
Decision Rules
📊 Business Logic Narrative
When the process 'Primary Email Failed?' is invoked, and assuming that email distribution has been attempted, when primary email delivery fails, the desired outcome is that the system should use fallback email addresses, otherwise proceed to merlin transmission.
💻 Technical Criteria
Given
Email distribution has been attempted
When
Primary email delivery fails
Then
The system should use fallback email addresses, otherwise proceed to Merlin transmission
R-GCX146-cbl-00370
Use Fallback Email
Process Rules
📊 Business Logic Narrative
When the process 'Use Fallback Email' is invoked, and assuming that primary email distribution has failed, when fallback email is needed, the desired outcome is that the system should configure fallback email settings.
💻 Technical Criteria
Given
Primary email distribution has failed
When
Fallback email is needed
Then
The system should configure fallback email settings
R-GCX146-cbl-00372
Setup Merlin Transmission
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Setup Merlin Transmission', assuming that email distribution is complete or not available, when merlin transmission is required, the desired outcome is that the system should setup merlin transmission parameters.
💻 Technical Criteria
EXCLUDING
Email distribution is complete or not available
When
Merlin transmission is required
Then
The system should setup Merlin transmission parameters
R-GCX146-cbl-00373
FAX Configuration Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'FAX Configuration Valid?' is invoked, and assuming that merlin transmission setup is complete, when fax configuration needs validation, the desired outcome is that the system should verify fax configuration is valid and proceed to external fax setup if valid, otherwise proceed directly to merlin system send.
💻 Technical Criteria
Given
Merlin transmission setup is complete
When
FAX configuration needs validation
Then
The system should verify FAX configuration is valid and proceed to external FAX setup if valid, otherwise proceed directly to Merlin system send
R-GCX146-cbl-00374
Configure External FAX
Process Rules
📊 Business Logic Narrative
When the process 'Configure External FAX' is invoked, and assuming that fax configuration is valid, when external fax needs to be configured, the desired outcome is that the system should configure external fax parameters.
💻 Technical Criteria
Given
FAX configuration is valid
When
External FAX needs to be configured
Then
The system should configure external FAX parameters
R-GCX146-cbl-00375
Set Copy IDs for FAX
Process Rules
📊 Business Logic Narrative
When the process 'Set Copy IDs for FAX' is invoked, and assuming that fax routing or external fax configuration is complete, when copy ids need to be assigned for fax distribution, the desired outcome is that the system should set appropriate copy ids for fax transmission.
💻 Technical Criteria
Given
FAX routing or external FAX configuration is complete
When
Copy IDs need to be assigned for FAX distribution
Then
The system should set appropriate copy IDs for FAX transmission
R-GCX146-cbl-00377
Distribution Complete
Process Rules
📊 Business Logic Narrative
When the process 'Distribution Complete' is invoked, and assuming that all distribution methods have been processed, when distribution is successful, the desired outcome is that the system should mark the distribution as complete.
💻 Technical Criteria
Given
All distribution methods have been processed
When
Distribution is successful
Then
The system should mark the distribution as complete
R-GCX146-cbl-00378
Distribution Error
Process Rules
📊 Business Logic Narrative
When the process 'Distribution Error' is invoked, and assuming that an error occurs during email or merlin distribution, when distribution fails, the desired outcome is that the system should handle the error and still complete the distribution process.
💻 Technical Criteria
Given
An error occurs during email or Merlin distribution
When
Distribution fails
Then
The system should handle the error and still complete the distribution process
R-GCX146-cbl-00390
Message Size Check
Validation Rules
📊 Business Logic Narrative
When the process 'Message Size Check' is invoked, and assuming that a formatted trip sheet message, when the system checks the message size, the desired outcome is that message is classified as either normal size for direct transmission or large message requiring segmentation.
💻 Technical Criteria
Given
A formatted trip sheet message
When
The system checks the message size
Then
Message is classified as either normal size for direct transmission or large message requiring segmentation
R-GCX146-cbl-00391
Segment Large Messages
Process Rules
📊 Business Logic Narrative
When the process 'Segment Large Messages' is invoked, and assuming that a trip sheet message exceeds maximum transmission size, when the system segments the message, the desired outcome is that message is divided into multiple segments with proper sequencing and continuation headers.
💻 Technical Criteria
Given
A trip sheet message exceeds maximum transmission size
When
The system segments the message
Then
Message is divided into multiple segments with proper sequencing and continuation headers
R-GCX146-cbl-00393
Transmission Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Transmission Successful?' is invoked, and assuming that a trip sheet transmission has been attempted, when the system evaluates the transmission result, the desired outcome is that transmission status is determined as either successful or failed based on system response.
💻 Technical Criteria
Given
A trip sheet transmission has been attempted
When
The system evaluates the transmission result
Then
Transmission status is determined as either successful or failed based on system response
R-GCX146-cbl-00394
Generate Transmission Confirmation
Process Rules
📊 Business Logic Narrative
When the process 'Generate Transmission Confirmation' is invoked, and assuming that trip sheet transmission was successful, when the system generates confirmation, the desired outcome is that confirmation message is created indicating successful transmission with timestamp and reference information.
💻 Technical Criteria
Given
Trip sheet transmission was successful
When
The system generates confirmation
Then
Confirmation message is created indicating successful transmission with timestamp and reference information
R-GCX146-cbl-00395
Handle Transmission Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Transmission Error' is invoked, and assuming that trip sheet transmission failed, when the system handles the transmission error, the desired outcome is that error is logged, appropriate notifications are sent, and retry or alternative delivery methods are initiated.
💻 Technical Criteria
Given
Trip sheet transmission failed
When
The system handles the transmission error
Then
Error is logged, appropriate notifications are sent, and retry or alternative delivery methods are initiated
R-GCX146-cbl-00401
Log Notification Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log Notification Activity' is invoked, and assuming that an arrival notification has been sent, when the system logs the notification activity, the desired outcome is that the spawn counter is incremented and transaction details are recorded for audit purposes.
💻 Technical Criteria
Given
An arrival notification has been sent
When
The system logs the notification activity
Then
The spawn counter is incremented and transaction details are recorded for audit purposes
R-GCX146-cbl-00418
X12 EDI Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'X12 EDI Channel Available?' is invoked, and assuming that a broker notification needs to be sent and broker configuration exists, when the system evaluates available communication channels, the desired outcome is that the system should use x12 edi channel if the broker has x12 edi capability configured.
💻 Technical Criteria
Given
A broker notification needs to be sent and broker configuration exists
When
The system evaluates available communication channels
Then
The system should use X12 EDI channel if the broker has X12 EDI capability configured
R-GCX146-cbl-00419
Send X12 EDI Notification via GCCS309C
Action Rules
📊 Business Logic Narrative
When the process 'Send X12 EDI Notification via GCCS309C' is invoked, and assuming that x12 edi channel is available and selected for broker notification, when the system processes the notification transmission, the desired outcome is that the system should invoke gccs309c to send the notification in x12 edi format to the broker.
💻 Technical Criteria
Given
X12 EDI channel is available and selected for broker notification
When
The system processes the notification transmission
Then
The system should invoke GCCS309C to send the notification in X12 EDI format to the broker
R-GCX146-cbl-00420
Merlin Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Merlin Channel Available?' is invoked, and assuming that x12 edi channel processing is complete and broker configuration exists, when the system evaluates remaining communication channels, the desired outcome is that the system should use merlin channel if the broker has merlin communication capability configured.
💻 Technical Criteria
Given
X12 EDI channel processing is complete and broker configuration exists
When
The system evaluates remaining communication channels
Then
The system should use Merlin channel if the broker has Merlin communication capability configured
R-GCX146-cbl-00421
Send Merlin Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin Notification via GCX019' is invoked, and assuming that merlin channel is available and selected for broker notification, when the system processes the notification transmission, the desired outcome is that the system should invoke gcx019 to send the notification through merlin system to the broker.
💻 Technical Criteria
Given
Merlin channel is available and selected for broker notification
When
The system processes the notification transmission
Then
The system should invoke GCX019 to send the notification through Merlin system to the broker
R-GCX146-cbl-00422
Internet Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Internet Channel Available?' is invoked, and assuming that merlin channel processing is complete and broker configuration exists, when the system evaluates remaining communication channels, the desired outcome is that the system should use internet channel if the broker has internet communication capability configured.
💻 Technical Criteria
Given
Merlin channel processing is complete and broker configuration exists
When
The system evaluates remaining communication channels
Then
The system should use Internet channel if the broker has Internet communication capability configured
R-GCX146-cbl-00423
Send Internet Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Internet Notification via GCX019' is invoked, and assuming that internet channel is available and selected for broker notification, when the system processes the notification transmission, the desired outcome is that the system should invoke gcx019 to send the notification via internet to the broker.
💻 Technical Criteria
Given
Internet channel is available and selected for broker notification
When
The system processes the notification transmission
Then
The system should invoke GCX019 to send the notification via Internet to the broker
R-GCX146-cbl-00424
FAX Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'FAX Channel Available?' is invoked, and assuming that internet channel processing is complete and broker configuration exists, when the system evaluates remaining communication channels, the desired outcome is that the system should use fax channel if the broker has fax communication capability configured.
💻 Technical Criteria
Given
Internet channel processing is complete and broker configuration exists
When
The system evaluates remaining communication channels
Then
The system should use FAX channel if the broker has FAX communication capability configured
R-GCX146-cbl-00425
Send FAX Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send FAX Notification via GCX019' is invoked, and assuming that fax channel is available and selected for broker notification, when the system processes the notification transmission, the desired outcome is that the system should invoke gcx019 to send the notification via fax to the broker.
💻 Technical Criteria
Given
FAX channel is available and selected for broker notification
When
The system processes the notification transmission
Then
The system should invoke GCX019 to send the notification via FAX to the broker
R-GCX146-cbl-00426
Paper Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Paper Channel Available?' is invoked, and assuming that fax channel processing is complete and broker configuration exists, when the system evaluates remaining communication channels, the desired outcome is that the system should use paper channel if the broker has paper communication capability configured.
💻 Technical Criteria
Given
FAX channel processing is complete and broker configuration exists
When
The system evaluates remaining communication channels
Then
The system should use Paper channel if the broker has Paper communication capability configured
R-GCX146-cbl-00427
Send Paper Notification via Batch Print Call Letters
Action Rules
📊 Business Logic Narrative
When the process 'Send Paper Notification via Batch Print Call Letters' is invoked, and assuming that paper channel is available and selected for broker notification, when the system processes the notification generation, the desired outcome is that the system should generate paper notification through batch print call letters system for the broker.
💻 Technical Criteria
Given
Paper channel is available and selected for broker notification
When
The system processes the notification generation
Then
The system should generate paper notification through batch print call letters system for the broker
R-GCX146-cbl-00428
Multi-Channel Distribution Complete
Process Rules
📊 Business Logic Narrative
When the process 'Multi-Channel Distribution Complete' is invoked, and assuming that all configured communication channels have been processed for broker notification, when the system completes the distribution process, the desired outcome is that the system should mark the multi-channel distribution as complete and proceed to finalize broker notification processing.
💻 Technical Criteria
Given
All configured communication channels have been processed for broker notification
When
The system completes the distribution process
Then
The system should mark the multi-channel distribution as complete and proceed to finalize broker notification processing
R-GCX146-cbl-01313
Determine Notification Channels
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Notification Channels' is invoked, and assuming that a primary broker exists and is configured for notifications, when the system evaluates available notification channels, the desired outcome is that the system should identify all configured channels including x12 edi, merlin, internet, fax, and paper based on broker preferences.
💻 Technical Criteria
Given
A primary broker exists and is configured for notifications
When
The system evaluates available notification channels
Then
The system should identify all configured channels including X12 EDI, Merlin, Internet, FAX, and Paper based on broker preferences
R-GCX146-cbl-01314
Call GCCS309C for X12
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCS309C for X12' is invoked, and assuming that primary broker has x12 edi channel configured, when the system processes x12 notifications, the desired outcome is that the system should call gccs309c program to send x12 edi notifications to the primary broker.
💻 Technical Criteria
Given
Primary broker has X12 EDI channel configured
When
The system processes X12 notifications
Then
The system should call GCCS309C program to send X12 EDI notifications to the primary broker
R-GCX146-cbl-01315
Call GCX019 for Merlin
Action Rules
📊 Business Logic Narrative
When the process 'Call GCX019 for Merlin' is invoked, and assuming that primary broker has merlin channel configured, when the system processes merlin notifications, the desired outcome is that the system should call gcx019 program to send merlin notifications to the primary broker.
💻 Technical Criteria
Given
Primary broker has Merlin channel configured
When
The system processes Merlin notifications
Then
The system should call GCX019 program to send Merlin notifications to the primary broker
R-GCX146-cbl-01316
Call GCX019 for Internet
Action Rules
📊 Business Logic Narrative
When the process 'Call GCX019 for Internet' is invoked, and assuming that primary broker has internet channel configured, when the system processes internet notifications, the desired outcome is that the system should call gcx019 program to send internet notifications to the primary broker.
💻 Technical Criteria
Given
Primary broker has Internet channel configured
When
The system processes Internet notifications
Then
The system should call GCX019 program to send Internet notifications to the primary broker
R-GCX146-cbl-01317
Call GCX019 for FAX
Action Rules
📊 Business Logic Narrative
When the process 'Call GCX019 for FAX' is invoked, and assuming that primary broker has fax channel configured, when the system processes fax notifications, the desired outcome is that the system should call gcx019 program to send fax notifications to the primary broker.
💻 Technical Criteria
Given
Primary broker has FAX channel configured
When
The system processes FAX notifications
Then
The system should call GCX019 program to send FAX notifications to the primary broker
R-GCX146-cbl-01318
Generate Print Call Letters
Action Rules
📊 Business Logic Narrative
When the process 'Generate Print Call Letters' is invoked, and assuming that primary broker has paper channel configured, when the system processes paper notifications, the desired outcome is that the system should generate print call letters for physical delivery to the primary broker.
💻 Technical Criteria
Given
Primary broker has paper channel configured
When
The system processes paper notifications
Then
The system should generate print call letters for physical delivery to the primary broker
R-GCX146-cbl-01319
All Channels Processed?
Process Rules
📊 Business Logic Narrative
When the process 'All Channels Processed?' is invoked, and assuming that multiple notification channels are configured for the primary broker, when the system processes each notification channel, the desired outcome is that the system should verify that all configured channels have been processed before completing the notification workflow.
💻 Technical Criteria
Given
Multiple notification channels are configured for the primary broker
When
The system processes each notification channel
Then
The system should verify that all configured channels have been processed before completing the notification workflow
R-GCX146-cbl-01320
Log Notification Success
Process Rules
📊 Business Logic Narrative
When the process 'Log Notification Success' is invoked, and assuming that all configured notification channels have been processed for the primary broker, when the notification process completes successfully, the desired outcome is that the system should log the successful completion of primary broker notifications for audit and tracking purposes.
💻 Technical Criteria
Given
All configured notification channels have been processed for the primary broker
When
The notification process completes successfully
Then
The system should log the successful completion of primary broker notifications for audit and tracking purposes
R-GCX146-cbl-01500
X12 EDI Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'X12 EDI Channel Available?' is invoked, and assuming that a broker notification needs to be sent and primary broker configuration is checked, when the system evaluates available notification channels, the desired outcome is that x12 edi channel is selected as the first priority if available.
💻 Technical Criteria
Given
A broker notification needs to be sent and primary broker configuration is checked
When
The system evaluates available notification channels
Then
X12 EDI channel is selected as the first priority if available
R-GCX146-cbl-01501
Send via X12 EDI - GCCS309C
Action Rules
📊 Business Logic Narrative
When the process 'Send via X12 EDI - GCCS309C' is invoked, and assuming that x12 edi channel is available and selected for broker notification, when the system initiates x12 edi transmission, the desired outcome is that gccs309c program is invoked to process the x12 edi notification.
💻 Technical Criteria
Given
X12 EDI channel is available and selected for broker notification
When
The system initiates X12 EDI transmission
Then
GCCS309C program is invoked to process the X12 EDI notification
R-GCX146-cbl-01502
X12 Transmission Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'X12 Transmission Successful?' is invoked, and assuming that x12 edi transmission has been attempted via gccs309c, when the system checks the transmission result, the desired outcome is that if successful, primary notification is marked complete, otherwise fallback to next channel.
💻 Technical Criteria
Given
X12 EDI transmission has been attempted via GCCS309C
When
The system checks the transmission result
Then
If successful, primary notification is marked complete, otherwise fallback to next channel
R-GCX146-cbl-01503
Merlin Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Merlin Channel Available?' is invoked, and assuming that x12 edi channel is either unavailable or transmission failed, when the system evaluates the next available notification channel, the desired outcome is that merlin channel is selected if available as the second priority option.
💻 Technical Criteria
Given
X12 EDI channel is either unavailable or transmission failed
When
The system evaluates the next available notification channel
Then
Merlin channel is selected if available as the second priority option
R-GCX146-cbl-01504
Send via Merlin - GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send via Merlin - GCX019' is invoked, and assuming that merlin channel is available and selected for broker notification, when the system initiates merlin transmission, the desired outcome is that gcx019 program is invoked to process the merlin notification.
💻 Technical Criteria
Given
Merlin channel is available and selected for broker notification
When
The system initiates Merlin transmission
Then
GCX019 program is invoked to process the Merlin notification
R-GCX146-cbl-01505
Merlin Transmission Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Merlin Transmission Successful?' is invoked, and assuming that merlin transmission has been attempted via gcx019, when the system checks the transmission result, the desired outcome is that if successful, primary notification is marked complete, otherwise fallback to next channel.
💻 Technical Criteria
Given
Merlin transmission has been attempted via GCX019
When
The system checks the transmission result
Then
If successful, primary notification is marked complete, otherwise fallback to next channel
R-GCX146-cbl-01506
Internet Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Internet Channel Available?' is invoked, and assuming that both x12 edi and merlin channels are either unavailable or transmissions failed, when the system evaluates the next available notification channel, the desired outcome is that internet channel is selected if available as the third priority option.
💻 Technical Criteria
Given
Both X12 EDI and Merlin channels are either unavailable or transmissions failed
When
The system evaluates the next available notification channel
Then
Internet channel is selected if available as the third priority option
R-GCX146-cbl-01507
Send via Internet - GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send via Internet - GCX019' is invoked, and assuming that internet channel is available and selected for broker notification, when the system initiates internet transmission, the desired outcome is that gcx019 program is invoked to process the internet notification.
💻 Technical Criteria
Given
Internet channel is available and selected for broker notification
When
The system initiates Internet transmission
Then
GCX019 program is invoked to process the Internet notification
R-GCX146-cbl-01508
Internet Transmission Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Internet Transmission Successful?' is invoked, and assuming that internet transmission has been attempted via gcx019, when the system checks the transmission result, the desired outcome is that if successful, primary notification is marked complete, otherwise fallback to next channel.
💻 Technical Criteria
Given
Internet transmission has been attempted via GCX019
When
The system checks the transmission result
Then
If successful, primary notification is marked complete, otherwise fallback to next channel
R-GCX146-cbl-01509
FAX Channel Available?
Decision Rules
📊 Business Logic Narrative
When the process 'FAX Channel Available?' is invoked, and assuming that x12 edi, merlin, and internet channels are either unavailable or transmissions failed, when the system evaluates the next available notification channel, the desired outcome is that fax channel is selected if available as the fourth priority option.
💻 Technical Criteria
Given
X12 EDI, Merlin, and Internet channels are either unavailable or transmissions failed
When
The system evaluates the next available notification channel
Then
FAX channel is selected if available as the fourth priority option
R-GCX146-cbl-01510
Send via FAX - GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send via FAX - GCX019' is invoked, and assuming that fax channel is available and selected for broker notification, when the system initiates fax transmission, the desired outcome is that gcx019 program is invoked to process the fax notification.
💻 Technical Criteria
Given
FAX channel is available and selected for broker notification
When
The system initiates FAX transmission
Then
GCX019 program is invoked to process the FAX notification
R-GCX146-cbl-01511
FAX Transmission Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'FAX Transmission Successful?' is invoked, and assuming that fax transmission has been attempted via gcx019, when the system checks the transmission result, the desired outcome is that if successful, primary notification is marked complete, otherwise fallback to paper notification.
💻 Technical Criteria
Given
FAX transmission has been attempted via GCX019
When
The system checks the transmission result
Then
If successful, primary notification is marked complete, otherwise fallback to paper notification
R-GCX146-cbl-01512
Generate Paper Notification
Process Rules
📊 Business Logic Narrative
When the process 'Generate Paper Notification' is invoked, and assuming that all electronic notification channels (x12 edi, merlin, internet, fax) are either unavailable or failed, when the system needs to complete broker notification, the desired outcome is that paper notification is generated as the final fallback option.
💻 Technical Criteria
Given
All electronic notification channels (X12 EDI, Merlin, Internet, FAX) are either unavailable or failed
When
The system needs to complete broker notification
Then
Paper notification is generated as the final fallback option
R-GCX146-cbl-01513
Call Batch Print Letters
Action Rules
📊 Business Logic Narrative
When the process 'Call Batch Print Letters' is invoked, and assuming that paper notification has been selected as the delivery method, when the system processes the paper notification request, the desired outcome is that batch print letters program is called to generate physical notification documents.
💻 Technical Criteria
Given
Paper notification has been selected as the delivery method
When
The system processes the paper notification request
Then
Batch print letters program is called to generate physical notification documents
R-GCX146-cbl-01514
Secondary Broker Exists?
Decision Rules
📊 Business Logic Narrative
When the process 'Secondary Broker Exists?' is invoked, and assuming that primary broker notification has been completed (successfully or via paper), when the system checks for additional broker notification requirements, the desired outcome is that if secondary broker exists, the same channel priority process is repeated for secondary broker.
💻 Technical Criteria
Given
Primary broker notification has been completed (successfully or via paper)
When
The system checks for additional broker notification requirements
Then
If secondary broker exists, the same channel priority process is repeated for secondary broker
R-GCX146-cbl-01515
Repeat Channel Priority for Secondary Broker
Process Rules
📊 Business Logic Narrative
When the process 'Repeat Channel Priority for Secondary Broker' is invoked, and assuming that secondary broker exists and requires notification, when the system processes secondary broker notification, the desired outcome is that the same channel priority sequence (x12 edi, merlin, internet, fax, paper) is applied for secondary broker.
💻 Technical Criteria
Given
Secondary broker exists and requires notification
When
The system processes secondary broker notification
Then
The same channel priority sequence (X12 EDI, Merlin, Internet, FAX, Paper) is applied for secondary broker
R-GCX146-cbl-01516
Log Failed Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Log Failed Transmission' is invoked, and assuming that any notification channel transmission fails (x12 edi, merlin, internet, or fax), when the system detects the transmission failure, the desired outcome is that the failed transmission is logged before attempting the next fallback channel.
💻 Technical Criteria
Given
Any notification channel transmission fails (X12 EDI, Merlin, Internet, or FAX)
When
The system detects the transmission failure
Then
The failed transmission is logged before attempting the next fallback channel
R-GCX146-cbl-01640
X12 EDI Transmission Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'X12 EDI Transmission Successful?' is invoked, and assuming that the gccs309c module has been called for x12 edi transmission, when the transmission process completes, the desired outcome is that the system determines if the transmission was successful or failed based on the module response.
💻 Technical Criteria
Given
The GCCS309C module has been called for X12 EDI transmission
When
The transmission process completes
Then
The system determines if the transmission was successful or failed based on the module response
R-GCX146-cbl-01641
Log Successful X12 Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful X12 Transmission' is invoked, and assuming that x12 edi transmission was successful, when the transmission completes successfully, the desired outcome is that the system logs the successful transmission details including timestamp and broker information.
💻 Technical Criteria
Given
X12 EDI transmission was successful
When
The transmission completes successfully
Then
The system logs the successful transmission details including timestamp and broker information
R-GCX146-cbl-01642
Set Broker Notification Complete Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Broker Notification Complete Flag' is invoked, and assuming that x12 edi transmission was successful and logged, when the notification process completes, the desired outcome is that the broker notification complete flag is set to indicate successful delivery.
💻 Technical Criteria
Given
X12 EDI transmission was successful and logged
When
The notification process completes
Then
The broker notification complete flag is set to indicate successful delivery
R-GCX146-cbl-01643
Handle X12 Transmission Failure
Process Rules
📊 Business Logic Narrative
When the process 'Handle X12 Transmission Failure' is invoked, and assuming that x12 edi transmission failed, when the gccs309c module returns a failure status, the desired outcome is that the system initiates failure handling procedures to manage the unsuccessful transmission.
💻 Technical Criteria
Given
X12 EDI transmission failed
When
The GCCS309C module returns a failure status
Then
The system initiates failure handling procedures to manage the unsuccessful transmission
R-GCX146-cbl-01644
Log X12 Error Details
Process Rules
📊 Business Logic Narrative
When the process 'Log X12 Error Details' is invoked, and assuming that x12 edi transmission failed, when error handling is initiated, the desired outcome is that the system logs detailed error information including failure reason and transmission details.
💻 Technical Criteria
Given
X12 EDI transmission failed
When
Error handling is initiated
Then
The system logs detailed error information including failure reason and transmission details
R-GCX146-cbl-01645
Continue to Next Notification Channel
Decision Rules
📊 Business Logic Narrative
When the process 'Continue to Next Notification Channel' is invoked, and assuming that x12 edi transmission failed and error details were logged, when the current notification attempt is complete, the desired outcome is that the system continues processing to attempt notification through the next available channel (merlin, internet, fax, or paper).
💻 Technical Criteria
Given
X12 EDI transmission failed and error details were logged
When
The current notification attempt is complete
Then
The system continues processing to attempt notification through the next available channel (Merlin, Internet, FAX, or Paper)
R-GCX146-cbl-01787
Prepare Shipper/Consignee Data
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Shipper/Consignee Data' is invoked, and assuming that shipper and consignee information exists in the system, when the system builds x12 message components, the desired outcome is that the system formats shipper and consignee data according to x12 requirements.
💻 Technical Criteria
Given
Shipper and consignee information exists in the system
When
The system builds X12 message components
Then
The system formats shipper and consignee data according to X12 requirements
R-GCX146-cbl-01788
Build X12 Message Structure
Process Rules
📊 Business Logic Narrative
When the process 'Build X12 Message Structure' is invoked, and assuming that all x12 message components have been prepared and validated, when the system builds the complete x12 message, the desired outcome is that the system assembles all components into proper x12 edi message structure.
💻 Technical Criteria
Given
All X12 message components have been prepared and validated
When
The system builds the complete X12 message
Then
The system assembles all components into proper X12 EDI message structure
R-GCX146-cbl-01646
Prepare GCX019 Input Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Prepare GCX019 Input Parameters' is invoked, and assuming that a broker notification needs to be sent via merlin system, when the system prepares gcx019 input parameters, the desired outcome is that the broker merlin id, notification message content, and message type are configured for the gcx019 module call.
💻 Technical Criteria
Given
A broker notification needs to be sent via Merlin system
When
The system prepares GCX019 input parameters
Then
The broker Merlin ID, notification message content, and message type are configured for the GCX019 module call
R-GCX146-cbl-01647
Set Broker Merlin ID
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Broker Merlin ID' is invoked, and assuming that broker configuration data exists in gcstbrt and broker merlin ids are available, when the system needs to identify the broker's merlin id for notification, the desired outcome is that the correct merlin id is retrieved from broker configuration and set for the notification.
💻 Technical Criteria
Given
Broker configuration data exists in GCSTBRT and broker Merlin IDs are available
When
The system needs to identify the broker's Merlin ID for notification
Then
The correct Merlin ID is retrieved from broker configuration and set for the notification
R-GCX146-cbl-01648
Set Notification Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Set Notification Message Content' is invoked, and assuming that broker notification data is available and message content needs to be prepared, when the system sets up notification message content, the desired outcome is that the appropriate message content is formatted and configured for broker notification.
💻 Technical Criteria
Given
Broker notification data is available and message content needs to be prepared
When
The system sets up notification message content
Then
The appropriate message content is formatted and configured for broker notification
R-GCX146-cbl-01649
Set Message Type for Broker
Decision Rules
📊 Business Logic Narrative
When the process 'Set Message Type for Broker' is invoked, and assuming that a broker notification is being prepared, when the system needs to classify the message type, the desired outcome is that the correct message type is determined and set for the broker notification.
💻 Technical Criteria
Given
A broker notification is being prepared
When
The system needs to classify the message type
Then
The correct message type is determined and set for the broker notification
R-GCX146-cbl-01650
Call GCX019 Module
Action Rules
📊 Business Logic Narrative
When the process 'Call GCX019 Module' is invoked, and assuming that all gcx019 input parameters are prepared and configured, when the system calls the gcx019 module, the desired outcome is that the gcx019 module is invoked to process the merlin broker notification.
💻 Technical Criteria
Given
All GCX019 input parameters are prepared and configured
When
The system calls the GCX019 module
Then
The GCX019 module is invoked to process the Merlin broker notification
R-GCX146-cbl-01651
GCX019 Call Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'GCX019 Call Successful?' is invoked, and assuming that the gcx019 module has been called for merlin broker notification, when the system checks the call result, the desired outcome is that the system determines if the gcx019 call was successful or failed.
💻 Technical Criteria
Given
The GCX019 module has been called for Merlin broker notification
When
The system checks the call result
Then
The system determines if the GCX019 call was successful or failed
R-GCX146-cbl-01652
Log Successful Merlin Send
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Merlin Send' is invoked, and assuming that the gcx019 call was successful, when the system processes the successful result, the desired outcome is that a log entry is created documenting the successful merlin broker notification.
💻 Technical Criteria
Given
The GCX019 call was successful
When
The system processes the successful result
Then
A log entry is created documenting the successful Merlin broker notification
R-GCX146-cbl-01653
Log Merlin Send Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Merlin Send Failure' is invoked, and assuming that the gcx019 call failed, when the system processes the failure result, the desired outcome is that a log entry is created documenting the failed merlin broker notification attempt.
💻 Technical Criteria
Given
The GCX019 call failed
When
The system processes the failure result
Then
A log entry is created documenting the failed Merlin broker notification attempt
R-GCX146-cbl-01654
Try Alternative Notification Method
Decision Rules
📊 Business Logic Narrative
When the process 'Try Alternative Notification Method' is invoked, and assuming that the merlin broker notification has failed, when the system needs to ensure broker notification delivery, the desired outcome is that an alternative notification method is selected and attempted for the broker.
💻 Technical Criteria
Given
The Merlin broker notification has failed
When
The system needs to ensure broker notification delivery
Then
An alternative notification method is selected and attempted for the broker
R-GCX146-cbl-01791
Set Merlin Parameters
Decision Rules
📊 Business Logic Narrative
When the process 'Set Merlin Parameters' is invoked, and assuming that a broker notification is configured for merlin delivery, when the communication method is merlin, the desired outcome is that the system sets merlin id and communication type to 'm' in gcx019 parameters.
💻 Technical Criteria
Given
A broker notification is configured for Merlin delivery
When
The communication method is Merlin
Then
The system sets Merlin ID and communication type to 'M' in GCX019 parameters
R-GCX146-cbl-01792
Set Internet Parameters
Decision Rules
📊 Business Logic Narrative
When the process 'Set Internet Parameters' is invoked, and assuming that a broker notification is configured for internet delivery, when the communication method is internet, the desired outcome is that the system sets internet address and communication type to 'i' in gcx019 parameters.
💻 Technical Criteria
Given
A broker notification is configured for Internet delivery
When
The communication method is Internet
Then
The system sets Internet address and communication type to 'I' in GCX019 parameters
R-GCX146-cbl-01793
Set FAX Parameters
Decision Rules
📊 Business Logic Narrative
When the process 'Set FAX Parameters' is invoked, and assuming that a broker notification is configured for fax delivery, when the communication method is fax, the desired outcome is that the system sets fax number and communication type to 'f' in gcx019 parameters.
💻 Technical Criteria
Given
A broker notification is configured for FAX delivery
When
The communication method is FAX
Then
The system sets FAX number and communication type to 'F' in GCX019 parameters
R-GCX146-cbl-01794
Set Paper Parameters
Decision Rules
📊 Business Logic Narrative
When the process 'Set Paper Parameters' is invoked, and assuming that a broker notification is configured for paper delivery, when the communication method is paper, the desired outcome is that the system sets mailing address and communication type to 'p' in gcx019 parameters.
💻 Technical Criteria
Given
A broker notification is configured for Paper delivery
When
The communication method is Paper
Then
The system sets mailing address and communication type to 'P' in GCX019 parameters
R-GCX146-cbl-01799
Add Date/Time Information
Process Rules
📊 Business Logic Narrative
When the process 'Add Date/Time Information' is invoked, and assuming that date and time information is available for the shipment, when temporal data is being added to the notification, the desired outcome is that the system populates estimated arrival date, processing date, and current timestamp in gcx019 parameters.
💻 Technical Criteria
Given
Date and time information is available for the shipment
When
Temporal data is being added to the notification
Then
The system populates estimated arrival date, processing date, and current timestamp in GCX019 parameters
R-GCX146-cbl-01655
GCX019 Module Reference Found
Action Rules
📊 Business Logic Narrative
When the process 'GCX019 Module Reference Found' is invoked, and assuming that a broker notification requires internet transmission method, when the system attempts to process internet notification, the desired outcome is that the system references gcx019 module but cannot execute the internet transmission logic due to missing implementation.
💻 Technical Criteria
Given
A broker notification requires internet transmission method
When
The system attempts to process internet notification
Then
The system references GCX019 module but cannot execute the internet transmission logic due to missing implementation
R-GCX146-cbl-01656
Check Broker FAX Configuration
Validation Rules
📊 Business Logic Narrative
When the process 'Check Broker FAX Configuration' is invoked, and assuming that a broker notification request requires fax transmission, when the system checks the broker's fax configuration, the desired outcome is that the system should verify fax number is available and valid before proceeding.
💻 Technical Criteria
Given
A broker notification request requires FAX transmission
When
The system checks the broker's FAX configuration
Then
The system should verify FAX number is available and valid before proceeding
R-GCX146-cbl-01657
Prepare FAX Message Content
Process Rules
📊 Business Logic Narrative
When the process 'Prepare FAX Message Content' is invoked, and assuming that a valid fax number is available for the broker, when the system prepares the fax message content, the desired outcome is that the system should format the notification data into appropriate fax message format.
💻 Technical Criteria
Given
A valid FAX number is available for the broker
When
The system prepares the FAX message content
Then
The system should format the notification data into appropriate FAX message format
R-GCX146-cbl-01659
Call GCX019 for FAX Transmission
Action Rules
📊 Business Logic Narrative
When the process 'Call GCX019 for FAX Transmission' is invoked, and assuming that fax routing parameters are configured, when the system calls gcx019 for fax transmission, the desired outcome is that the system should invoke gcx019 program to handle the actual fax transmission.
💻 Technical Criteria
Given
FAX routing parameters are configured
When
The system calls GCX019 for FAX transmission
Then
The system should invoke GCX019 program to handle the actual FAX transmission
R-GCX146-cbl-01660
FAX Send Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'FAX Send Successful?' is invoked, and assuming that gcx019 fax transmission has been executed, when the system evaluates the transmission result, the desired outcome is that the system should determine success or failure based on gcx019 return status.
💻 Technical Criteria
Given
GCX019 FAX transmission has been executed
When
The system evaluates the transmission result
Then
The system should determine success or failure based on GCX019 return status
R-GCX146-cbl-01661
Log FAX Transmission Success
Process Rules
📊 Business Logic Narrative
When the process 'Log FAX Transmission Success' is invoked, and assuming that fax transmission was successful, when the system logs the transmission success, the desired outcome is that the system should create audit trail entry recording successful fax delivery.
💻 Technical Criteria
Given
FAX transmission was successful
When
The system logs the transmission success
Then
The system should create audit trail entry recording successful FAX delivery
R-GCX146-cbl-01662
Update Broker Notification Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Broker Notification Status' is invoked, and assuming that fax transmission success has been logged, when the system updates broker notification status, the desired outcome is that the system should mark the broker notification as successfully delivered via fax.
💻 Technical Criteria
Given
FAX transmission success has been logged
When
The system updates broker notification status
Then
The system should mark the broker notification as successfully delivered via FAX
R-GCX146-cbl-01663
Handle FAX Transmission Error
Decision Rules
📊 Business Logic Narrative
When the process 'Handle FAX Transmission Error' is invoked, and assuming that fax transmission failed, when the system handles the transmission error, the desired outcome is that the system should process the error and determine if alternative fax methods are available.
💻 Technical Criteria
Given
FAX transmission failed
When
The system handles the transmission error
Then
The system should process the error and determine if alternative FAX methods are available
R-GCX146-cbl-01664
Alternative Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Alternative Available?' is invoked, and assuming that primary fax transmission failed, when the system checks for alternative fax methods, the desired outcome is that the system should determine if backup fax numbers or alternative transmission methods are configured.
💻 Technical Criteria
Given
Primary FAX transmission failed
When
The system checks for alternative FAX methods
Then
The system should determine if backup FAX numbers or alternative transmission methods are configured
R-GCX146-cbl-01665
Mark FAX Notification Failed
Process Rules
📊 Business Logic Narrative
When the process 'Mark FAX Notification Failed' is invoked, and assuming that fax transmission failed and no alternatives are available, when the system marks fax notification as failed, the desired outcome is that the system should update broker notification status to indicate fax delivery failure.
💻 Technical Criteria
Given
FAX transmission failed and no alternatives are available
When
The system marks FAX notification as failed
Then
The system should update broker notification status to indicate FAX delivery failure
R-GCX146-cbl-01803
Check Auto-FAX Configuration
Validation Rules
📊 Business Logic Narrative
When the process 'Check Auto-FAX Configuration' is invoked, and assuming that a station has fax configuration settings in the system, when the system checks the auto-fax configuration status, the desired outcome is that the system should verify if auto-fax is enabled based on station settings and user permissions.
💻 Technical Criteria
Given
A station has FAX configuration settings in the system
When
The system checks the auto-FAX configuration status
Then
The system should verify if auto-FAX is enabled based on station settings and user permissions
R-GCX146-cbl-01804
Auto-FAX Enabled?
Decision Rules
📊 Business Logic Narrative
When the process 'Auto-FAX Enabled?' is invoked, and assuming that auto-fax configuration has been checked and fax flag status is available, when the system evaluates if auto-fax is enabled, the desired outcome is that if auto-fax is enabled, proceed with fax routing setup, otherwise skip fax preparation.
💻 Technical Criteria
Given
Auto-FAX configuration has been checked and FAX flag status is available
When
The system evaluates if auto-FAX is enabled
Then
If auto-FAX is enabled, proceed with FAX routing setup, otherwise skip FAX preparation
R-GCX146-cbl-01806
Configure Copy IDs for FAX
Process Rules
📊 Business Logic Narrative
When the process 'Configure Copy IDs for FAX' is invoked, and assuming that fax routing parameters have been established, when the system configures copy ids for the fax transmission, the desired outcome is that the system should assign unique copy identifiers for tracking and distribution management.
💻 Technical Criteria
Given
FAX routing parameters have been established
When
The system configures copy IDs for the FAX transmission
Then
The system should assign unique copy identifiers for tracking and distribution management
R-GCX146-cbl-01807
Set External FAX Addressing
Process Rules
📊 Business Logic Narrative
When the process 'Set External FAX Addressing' is invoked, and assuming that copy ids have been configured for the fax, when the system sets up external fax addressing, the desired outcome is that the system should configure external fax numbers, recipient information, and delivery addressing.
💻 Technical Criteria
Given
Copy IDs have been configured for the FAX
When
The system sets up external FAX addressing
Then
The system should configure external FAX numbers, recipient information, and delivery addressing
R-GCX146-cbl-01808
Prepare FAX Header Information
Process Rules
📊 Business Logic Narrative
When the process 'Prepare FAX Header Information' is invoked, and assuming that external fax addressing has been configured, when the system prepares fax header information, the desired outcome is that the system should format sender information, recipient details, transmission date/time, and document identification in the fax header.
💻 Technical Criteria
Given
External FAX addressing has been configured
When
The system prepares FAX header information
Then
The system should format sender information, recipient details, transmission date/time, and document identification in the FAX header
R-GCX146-cbl-01809
Format Message Content for FAX
Process Rules
📊 Business Logic Narrative
When the process 'Format Message Content for FAX' is invoked, and assuming that fax header information has been prepared, when the system formats message content for fax transmission, the desired outcome is that the system should format the message content to meet fax layout requirements, character limitations, and transmission standards.
💻 Technical Criteria
Given
FAX header information has been prepared
When
The system formats message content for FAX transmission
Then
The system should format the message content to meet FAX layout requirements, character limitations, and transmission standards
R-GCX146-cbl-01810
Set FAX Transmission Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set FAX Transmission Flags' is invoked, and assuming that message content has been formatted for fax, when the system sets fax transmission flags, the desired outcome is that the system should configure transmission priority, delivery confirmation requirements, and retry options.
💻 Technical Criteria
Given
Message content has been formatted for FAX
When
The system sets FAX transmission flags
Then
The system should configure transmission priority, delivery confirmation requirements, and retry options
R-GCX146-cbl-01811
Validate FAX Configuration
Validation Rules
📊 Business Logic Narrative
When the process 'Validate FAX Configuration' is invoked, and assuming that fax transmission flags have been set, when the system validates the fax configuration, the desired outcome is that the system should verify that all required fax parameters are present, valid, and compatible for successful transmission.
💻 Technical Criteria
Given
FAX transmission flags have been set
When
The system validates the FAX configuration
Then
The system should verify that all required FAX parameters are present, valid, and compatible for successful transmission
R-GCX146-cbl-01812
FAX Config Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'FAX Config Valid?' is invoked, and assuming that fax configuration validation has been performed, when the system evaluates fax configuration validity, the desired outcome is that if configuration is valid, mark fax message as ready; if invalid, prepare alternative routing options.
💻 Technical Criteria
Given
FAX configuration validation has been performed
When
The system evaluates FAX configuration validity
Then
If configuration is valid, mark FAX message as ready; if invalid, prepare alternative routing options
R-GCX146-cbl-01813
Prepare Alternative Routing
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Alternative Routing' is invoked, and assuming that fax configuration is determined to be invalid, when the system prepares alternative routing, the desired outcome is that the system should configure alternative delivery methods such as email, print queue, or manual processing.
💻 Technical Criteria
Given
FAX configuration is determined to be invalid
When
The system prepares alternative routing
Then
The system should configure alternative delivery methods such as email, print queue, or manual processing
R-GCX146-cbl-01814
Skip FAX Preparation
Process Rules
📊 Business Logic Narrative
When the process 'Skip FAX Preparation' is invoked, and assuming that auto-fax is determined to be disabled, when the system processes the skip fax preparation path, the desired outcome is that the system should bypass all fax configuration steps and proceed to message completion.
💻 Technical Criteria
Given
Auto-FAX is determined to be disabled
When
The system processes the skip FAX preparation path
Then
The system should bypass all FAX configuration steps and proceed to message completion
R-GCX146-cbl-01323
X12 EDI Channel?
Decision Rules
📊 Business Logic Narrative
When the process 'X12 EDI Channel?' is invoked, and assuming that a secondary broker notification is required, when the notification channel is evaluated, the desired outcome is that x12 edi notification is sent via gccs309c if x12 edi channel is selected, otherwise check next available channel.
💻 Technical Criteria
Given
A secondary broker notification is required
When
The notification channel is evaluated
Then
X12 EDI notification is sent via GCCS309C if X12 EDI channel is selected, otherwise check next available channel
R-GCX146-cbl-01324
Send X12 EDI Notification via GCCS309C
Action Rules
📊 Business Logic Narrative
When the process 'Send X12 EDI Notification via GCCS309C' is invoked, and assuming that x12 edi channel is selected for secondary broker notification, when the notification transmission is initiated, the desired outcome is that the system invokes gccs309c program to send x12 edi notification and returns success or failure status.
💻 Technical Criteria
Given
X12 EDI channel is selected for secondary broker notification
When
The notification transmission is initiated
Then
The system invokes GCCS309C program to send X12 EDI notification and returns success or failure status
R-GCX146-cbl-01325
Merlin Channel?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Merlin Channel?', assuming that x12 edi channel is not selected for secondary broker notification, when the notification channel is evaluated for merlin, the desired outcome is that merlin notification is sent via gcx019 if merlin channel is selected, otherwise check next available channel.
💻 Technical Criteria
EXCLUDING
X12 EDI channel is not selected for secondary broker notification
When
The notification channel is evaluated for Merlin
Then
Merlin notification is sent via GCX019 if Merlin channel is selected, otherwise check next available channel
R-GCX146-cbl-01326
Send Merlin Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin Notification via GCX019' is invoked, and assuming that merlin channel is selected for secondary broker notification, when the notification transmission is initiated, the desired outcome is that the system invokes gcx019 program to send merlin notification and returns success or failure status.
💻 Technical Criteria
Given
Merlin channel is selected for secondary broker notification
When
The notification transmission is initiated
Then
The system invokes GCX019 program to send Merlin notification and returns success or failure status
R-GCX146-cbl-01327
Internet Channel?
Decision Rules
📊 Business Logic Narrative
When the process 'Internet Channel?' is invoked, and assuming that neither x12 edi nor merlin channels are selected for secondary broker notification, when the notification channel is evaluated for internet, the desired outcome is that internet notification is sent via gcx019 if internet channel is selected, otherwise check next available channel.
💻 Technical Criteria
Given
Neither X12 EDI nor Merlin channels are selected for secondary broker notification
When
The notification channel is evaluated for Internet
Then
Internet notification is sent via GCX019 if Internet channel is selected, otherwise check next available channel
R-GCX146-cbl-01328
Send Internet Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Internet Notification via GCX019' is invoked, and assuming that internet channel is selected for secondary broker notification, when the notification transmission is initiated, the desired outcome is that the system invokes gcx019 program to send internet notification and returns success or failure status.
💻 Technical Criteria
Given
Internet channel is selected for secondary broker notification
When
The notification transmission is initiated
Then
The system invokes GCX019 program to send Internet notification and returns success or failure status
R-GCX146-cbl-01329
FAX Channel?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'FAX Channel?', assuming that x12 edi, merlin, and internet channels are not selected for secondary broker notification, when the notification channel is evaluated for fax, the desired outcome is that fax notification is sent via gcx019 if fax channel is selected, otherwise check next available channel.
💻 Technical Criteria
EXCLUDING
X12 EDI, Merlin, and Internet channels are not selected for secondary broker notification
When
The notification channel is evaluated for FAX
Then
FAX notification is sent via GCX019 if FAX channel is selected, otherwise check next available channel
R-GCX146-cbl-01330
Send FAX Notification via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send FAX Notification via GCX019' is invoked, and assuming that fax channel is selected for secondary broker notification, when the notification transmission is initiated, the desired outcome is that the system invokes gcx019 program to send fax notification and returns success or failure status.
💻 Technical Criteria
Given
FAX channel is selected for secondary broker notification
When
The notification transmission is initiated
Then
The system invokes GCX019 program to send FAX notification and returns success or failure status
R-GCX146-cbl-01331
Paper Channel?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Paper Channel?', assuming that electronic notification channels (x12 edi, merlin, internet, fax) are not selected for secondary broker notification, when the notification channel is evaluated for paper, the desired outcome is that paper notification is generated via batch print if paper channel is selected, otherwise complete notification process.
💻 Technical Criteria
EXCLUDING
Electronic notification channels (X12 EDI, Merlin, Internet, FAX) are not selected for secondary broker notification
When
The notification channel is evaluated for Paper
Then
Paper notification is generated via batch print if Paper channel is selected, otherwise complete notification process
R-GCX146-cbl-01332
Generate Paper Notification via Batch Print
Action Rules
📊 Business Logic Narrative
When the process 'Generate Paper Notification via Batch Print' is invoked, and assuming that paper channel is selected for secondary broker notification, when the notification generation is initiated, the desired outcome is that the system generates paper notification via batch print process and returns success or failure status.
💻 Technical Criteria
Given
Paper channel is selected for secondary broker notification
When
The notification generation is initiated
Then
The system generates paper notification via batch print process and returns success or failure status
R-GCX146-cbl-01333
Log Notification Success
Process Rules
📊 Business Logic Narrative
When the process 'Log Notification Success' is invoked, and assuming that a secondary broker notification transmission is completed successfully, when the notification result is processed, the desired outcome is that the system logs the successful notification transmission for audit and tracking purposes.
💻 Technical Criteria
Given
A secondary broker notification transmission is completed successfully
When
The notification result is processed
Then
The system logs the successful notification transmission for audit and tracking purposes
R-GCX146-cbl-01334
Log Notification Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Notification Failure' is invoked, and assuming that a secondary broker notification transmission fails, when the notification result is processed, the desired outcome is that the system logs the failed notification transmission for audit and error tracking purposes.
💻 Technical Criteria
Given
A secondary broker notification transmission fails
When
The notification result is processed
Then
The system logs the failed notification transmission for audit and error tracking purposes
R-GCX146-cbl-00452
Increment Spawn Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Spawn Counter' is invoked, and assuming that a special manifest transaction is being created, when the system processes the manifest creation, the desired outcome is that the spawn counter must be incremented by 1 to track the transaction.
💻 Technical Criteria
Given
A special manifest transaction is being created
When
The system processes the manifest creation
Then
The spawn counter must be incremented by 1 to track the transaction
R-GCX146-cbl-00455
Queue Special Manifest Transaction
Action Rules
📊 Business Logic Narrative
When the process 'Queue Special Manifest Transaction' is invoked, and assuming that a complete special manifest input structure is built, when the system processes the special manifest, the desired outcome is that the transaction must be queued for subsequent processing.
💻 Technical Criteria
Given
A complete special manifest input structure is built
When
The system processes the special manifest
Then
The transaction must be queued for subsequent processing
R-GCX146-cbl-00477
Store Audit Trail
Process Rules
📊 Business Logic Narrative
When the process 'Store Audit Trail' is invoked, and assuming that an audit transaction has been spawned successfully, when the audit record creation process needs to be completed, the desired outcome is that the system handles message queuing operations and purges completed audit transactions to finalize the audit trail storage.
💻 Technical Criteria
Given
An audit transaction has been spawned successfully
When
The audit record creation process needs to be completed
Then
The system handles message queuing operations and purges completed audit transactions to finalize the audit trail storage
R-GCX146-cbl-00478
Check User Access Level from GCSTBRT-US-CTF-ADD
Action Rules
📊 Business Logic Narrative
When the process 'Check User Access Level from GCSTBRT-US-CTF-ADD' is invoked, and assuming that a user is processing a train with eta information, when the system needs to validate eta date ranges, the desired outcome is that the user access level is retrieved from gcstbrt user configuration to determine validation parameters.
💻 Technical Criteria
Given
A user is processing a train with ETA information
When
The system needs to validate ETA date ranges
Then
The user access level is retrieved from GCSTBRT user configuration to determine validation parameters
R-GCX146-cbl-00479
User Type = 'S' Special User?
Decision Rules
📊 Business Logic Narrative
When the process 'User Type = 'S' Special User?' is invoked, and assuming that user access level has been retrieved from gcstbrt configuration, when the system checks if gcstbrt-us-ctf-add equals 's', the desired outcome is that user is classified as special user with extended eta date range privileges.
💻 Technical Criteria
Given
User access level has been retrieved from GCSTBRT configuration
When
The system checks if GCSTBRT-US-CTF-ADD equals 'S'
Then
User is classified as Special User with extended ETA date range privileges
R-GCX146-cbl-00480
Apply Standard User Range -2 to +2 days from current date
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Apply Standard User Range -2 to +2 days from current date', assuming that user is classified as standard user (ctf add access level is not 's'), when eta date validation is performed, the desired outcome is that eta date must fall between 2 days before current date and 2 days after current date.
💻 Technical Criteria
EXCLUDING
User is classified as Standard User (CTF ADD access level is not 'S')
When
ETA date validation is performed
Then
ETA date must fall between 2 days before current date and 2 days after current date
R-GCX146-cbl-00481
Apply Special User Range -30 to +5 days from current date
Validation Rules
📊 Business Logic Narrative
When the process 'Apply Special User Range -30 to +5 days from current date' is invoked, and assuming that user is classified as special user (ctf add access level equals 's'), when eta date validation is performed, the desired outcome is that eta date must fall between 30 days before current date and 5 days after current date.
💻 Technical Criteria
Given
User is classified as Special User (CTF ADD access level equals 'S')
When
ETA date validation is performed
Then
ETA date must fall between 30 days before current date and 5 days after current date
R-GCX146-cbl-00482
Validate ETA Date using ISDATECV
Validation Rules
📊 Business Logic Narrative
When the process 'Validate ETA Date using ISDATECV' is invoked, and assuming that an eta date has been provided for validation, when date format validation is performed using isdatecv utility, the desired outcome is that eta date must be in valid date format and represent an actual calendar date.
💻 Technical Criteria
Given
An ETA date has been provided for validation
When
Date format validation is performed using ISDATECV utility
Then
ETA date must be in valid date format and represent an actual calendar date
R-GCX146-cbl-00483
ETA Date within allowed range?
Validation Rules
📊 Business Logic Narrative
When the process 'ETA Date within allowed range?' is invoked, and assuming that eta date format is valid and user-specific date range has been determined, when date range validation is performed, the desired outcome is that eta date must fall within the calculated minimum and maximum allowed dates for the user type.
💻 Technical Criteria
Given
ETA date format is valid and user-specific date range has been determined
When
Date range validation is performed
Then
ETA date must fall within the calculated minimum and maximum allowed dates for the user type
R-GCX146-cbl-00484
Validate Time Format HH:MM
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Time Format HH:MM' is invoked, and assuming that an eta time has been provided along with valid eta date, when time format validation is performed, the desired outcome is that eta time must be in hh:mm format where hh represents hours and mm represents minutes.
💻 Technical Criteria
Given
An ETA time has been provided along with valid ETA date
When
Time format validation is performed
Then
ETA time must be in HH:MM format where HH represents hours and MM represents minutes
R-GCX146-cbl-00485
Time within valid range?
Validation Rules
📊 Business Logic Narrative
When the process 'Time within valid range?' is invoked, and assuming that eta time is in proper hh:mm format, when time range validation is performed, the desired outcome is that hours must be between 00-23 and minutes must be between 00-59.
💻 Technical Criteria
Given
ETA time is in proper HH:MM format
When
Time range validation is performed
Then
Hours must be between 00-23 and minutes must be between 00-59
R-GCX146-cbl-00486
Generate Error 35 Standard User Date Out of Range
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error 35 Standard User Date Out of Range' is invoked, and assuming that user is standard user and eta date is outside -2 to +2 days range, when date range validation fails for standard user, the desired outcome is that error 35 is generated indicating date is out of range for standard user privileges.
💻 Technical Criteria
Given
User is Standard User and ETA date is outside -2 to +2 days range
When
Date range validation fails for standard user
Then
Error 35 is generated indicating date is out of range for standard user privileges
R-GCX146-cbl-00487
Generate Error 25 Special User Date Out of Range
Validation Rules
📊 Business Logic Narrative
When the process 'Generate Error 25 Special User Date Out of Range' is invoked, and assuming that user is special user and eta date is outside -30 to +5 days range, when date range validation fails for special user, the desired outcome is that error 25 is generated indicating date is out of range even for special user privileges.
💻 Technical Criteria
Given
User is Special User and ETA date is outside -30 to +5 days range
When
Date range validation fails for special user
Then
Error 25 is generated indicating date is out of range even for special user privileges
R-GCX146-cbl-00488
Retrieve Existing Train Record
Validation Rules
📊 Business Logic Narrative
When the process 'Retrieve Existing Train Record' is invoked, and assuming that a train record deletion process is initiated, when the system attempts to retrieve an existing train record from the database, the desired outcome is that the system determines whether the train record exists or not.
💻 Technical Criteria
Given
A train record deletion process is initiated
When
The system attempts to retrieve an existing train record from the database
Then
The system determines whether the train record exists or not
R-GCX146-cbl-00489
Check Record Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Record Status' is invoked, and assuming that a train record exists in the database, when the system checks the record status, the desired outcome is that the system identifies whether the record is marked as deleted or active.
💻 Technical Criteria
Given
A train record exists in the database
When
The system checks the record status
Then
The system identifies whether the record is marked as deleted or active
R-GCX146-cbl-00490
Confirm Deletion Authorization
Authorization Rules
📊 Business Logic Narrative
When the process 'Confirm Deletion Authorization' is invoked, and assuming that a train record is marked as deleted, when the system confirms deletion authorization, the desired outcome is that the system either grants or denies deletion permission based on authorization rules.
💻 Technical Criteria
Given
A train record is marked as deleted
When
The system confirms deletion authorization
Then
The system either grants or denies deletion permission based on authorization rules
R-GCX146-cbl-00491
Delete Existing Train Record
Action Rules
📊 Business Logic Narrative
When the process 'Delete Existing Train Record' is invoked, and assuming that deletion is authorized for a train record, when the system executes the deletion operation, the desired outcome is that the train record is permanently removed from the database.
💻 Technical Criteria
Given
Deletion is authorized for a train record
When
The system executes the deletion operation
Then
The train record is permanently removed from the database
R-GCX146-cbl-00492
Deletion Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Deletion Successful?' is invoked, and assuming that a train record deletion operation has been executed, when the system checks the deletion result, the desired outcome is that the system confirms whether the deletion was successful or failed.
💻 Technical Criteria
Given
A train record deletion operation has been executed
When
The system checks the deletion result
Then
The system confirms whether the deletion was successful or failed
R-GCX146-cbl-00493
Log Deletion Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log Deletion Activity' is invoked, and assuming that a train record has been successfully deleted, when the system logs the deletion activity, the desired outcome is that an audit trail entry is created with deletion details and timestamp.
💻 Technical Criteria
Given
A train record has been successfully deleted
When
The system logs the deletion activity
Then
An audit trail entry is created with deletion details and timestamp
R-GCX146-cbl-00494
Skip Deletion - Record Not Deleted
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip Deletion - Record Not Deleted', assuming that a train record exists but is not marked as deleted, when the system processes the record status, the desired outcome is that the deletion process is skipped and processing continues to new record creation.
💻 Technical Criteria
EXCLUDING
A train record exists but is not marked as deleted
When
The system processes the record status
Then
The deletion process is skipped and processing continues to new record creation
R-GCX146-cbl-00495
Deletion Error - Abort Process
Process Rules
📊 Business Logic Narrative
When the process 'Deletion Error - Abort Process' is invoked, and assuming that a train record deletion operation has failed, when the system detects the deletion error, the desired outcome is that the entire train processing operation is aborted and error handling is initiated.
💻 Technical Criteria
Given
A train record deletion operation has failed
When
The system detects the deletion error
Then
The entire train processing operation is aborted and error handling is initiated
R-GCX146-cbl-00496
Authorization Failed - Skip Deletion
Authorization Rules
📊 Business Logic Narrative
When the process 'Authorization Failed - Skip Deletion' is invoked, and assuming that a train record is marked for deletion but authorization is denied, when the system processes the authorization failure, the desired outcome is that the deletion is skipped and processing continues to new record creation.
💻 Technical Criteria
Given
A train record is marked for deletion but authorization is denied
When
The system processes the authorization failure
Then
The deletion is skipped and processing continues to new record creation
R-GCX146-cbl-00682
Update AEI Send Status
Action Rules
📊 Business Logic Narrative
When the process 'Update AEI Send Status' is invoked, and assuming that aei transmission activities have been logged, when the system completes the aei send process, the desired outcome is that the system updates the aei send status in the relevant system records to reflect the completion of the transmission process.
💻 Technical Criteria
Given
AEI transmission activities have been logged
When
The system completes the AEI send process
Then
The system updates the AEI send status in the relevant system records to reflect the completion of the transmission process
R-GCX146-cbl-00683
Check Distribution Configuration
Decision Rules
📊 Business Logic Narrative
When the process 'Check Distribution Configuration' is invoked, and assuming that a trip sheet needs to be distributed, when the system checks the distribution configuration, the desired outcome is that the system identifies whether auto-fax is enabled based on station configuration.
💻 Technical Criteria
Given
A trip sheet needs to be distributed
When
The system checks the distribution configuration
Then
The system identifies whether auto-FAX is enabled based on station configuration
R-GCX146-cbl-00684
Setup FAX Routing Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Setup FAX Routing Parameters' is invoked, and assuming that auto-fax distribution is enabled, when the system sets up fax routing, the desired outcome is that fax routing parameters are configured from station configuration data.
💻 Technical Criteria
Given
Auto-FAX distribution is enabled
When
The system sets up FAX routing
Then
FAX routing parameters are configured from station configuration data
R-GCX146-cbl-00692
Get Email User Lists from Station Config
Process Rules
📊 Business Logic Narrative
When the process 'Get Email User Lists from Station Config' is invoked, and assuming that email distribution is required, when the system retrieves email user lists, the desired outcome is that email distribution lists are obtained from station configuration data including authorized recipients.
💻 Technical Criteria
Given
Email distribution is required
When
The system retrieves email user lists
Then
Email distribution lists are obtained from station configuration data including authorized recipients
R-GCX146-cbl-00709
Additional Recipients?
Decision Rules
📊 Business Logic Narrative
When the process 'Additional Recipients?' is invoked, and assuming that primary distribution channels have been processed, when the system checks for additional recipients in the distribution configuration, the desired outcome is that if additional recipients exist, continue processing them, otherwise proceed to logging.
💻 Technical Criteria
Given
Primary distribution channels have been processed
When
The system checks for additional recipients in the distribution configuration
Then
If additional recipients exist, continue processing them, otherwise proceed to logging
R-GCX146-cbl-00712
Set Rollback Flag WS-ROLB
Process Rules
📊 Business Logic Narrative
When the process 'Set Rollback Flag WS-ROLB' is invoked, and assuming that an error has been detected and error code has been assigned, when the system determines that the error requires transaction rollback to maintain data consistency, the desired outcome is that the system sets the rollback flag ws-rolb to indicate that all changes should be reversed.
💻 Technical Criteria
Given
An error has been detected and error code has been assigned
When
The system determines that the error requires transaction rollback to maintain data consistency
Then
The system sets the rollback flag WS-ROLB to indicate that all changes should be reversed
R-GCX146-cbl-00713
Generate Error Message Content
Action Rules
📊 Business Logic Narrative
When the process 'Generate Error Message Content' is invoked, and assuming that an error code has been assigned and the error processing section is invoked, when the system needs to create a human-readable error message, the desired outcome is that the system generates error message content that describes the error condition in business terms including relevant context information.
💻 Technical Criteria
Given
An error code has been assigned and the error processing section is invoked
When
The system needs to create a human-readable error message
Then
The system generates error message content that describes the error condition in business terms including relevant context information
R-GCX146-cbl-00714
Identify Distribution Recipients
Authorization Rules
📊 Business Logic Narrative
When the process 'Identify Distribution Recipients' is invoked, and assuming that an error message has been generated with specific error content, when the system needs to determine who should receive the error notification, the desired outcome is that the system identifies the appropriate recipients including supervisors and designated personnel based on the error type and current user context.
💻 Technical Criteria
Given
An error message has been generated with specific error content
When
The system needs to determine who should receive the error notification
Then
The system identifies the appropriate recipients including supervisors and designated personnel based on the error type and current user context
R-GCX146-cbl-00719
Queue Error Message for Distribution
Process Rules
📊 Business Logic Narrative
When the process 'Queue Error Message for Distribution' is invoked, and assuming that error message routing decisions have been completed, when the system prepares to distribute the error message, the desired outcome is that the system queues the error message for distribution through the messaging infrastructure.
💻 Technical Criteria
Given
Error message routing decisions have been completed
When
The system prepares to distribute the error message
Then
The system queues the error message for distribution through the messaging infrastructure
R-GCX146-cbl-00720
Send via IMS Message Queues
Action Rules
📊 Business Logic Narrative
When the process 'Send via IMS Message Queues' is invoked, and assuming that error messages have been queued for distribution, when the system initiates message distribution, the desired outcome is that the system sends the error messages via ims message queues to ensure reliable delivery to all identified recipients.
💻 Technical Criteria
Given
Error messages have been queued for distribution
When
The system initiates message distribution
Then
The system sends the error messages via IMS message queues to ensure reliable delivery to all identified recipients
R-GCX146-cbl-00723
Error 36: SCAC Access Violation
Authorization Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Error 36: SCAC Access Violation', assuming that a user is attempting to perform an operation that requires scac access validation, when the system determines that scac access is invalid and the operation is not an aei train send, the desired outcome is that the system generates error 36 for scac access violation and initiates error distribution process.
💻 Technical Criteria
EXCLUDING
A user is attempting to perform an operation that requires SCAC access validation
When
The system determines that SCAC access is invalid AND the operation is not an AEI train send
Then
The system generates Error 36 for SCAC access violation and initiates error distribution process
R-GCX146-cbl-00724
Error 38: Processing Failures
Process Rules
📊 Business Logic Narrative
When the process 'Error 38: Processing Failures' is invoked, and assuming that a processing failure occurs during transaction execution, when the system detects that a spawned transaction or critical process has failed, the desired outcome is that the system generates error 38 for processing failures and initiates the error distribution workflow.
💻 Technical Criteria
Given
A processing failure occurs during transaction execution
When
The system detects that a spawned transaction or critical process has failed
Then
The system generates Error 38 for processing failures and initiates the error distribution workflow
R-GCX146-cbl-00735
Assign CA Record Type Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Assign CA Record Type Code' is invoked, and assuming that a special manifest transaction is being created, when the record type needs to be assigned, the desired outcome is that the record type is set to 'ca' indicating canadian processing.
💻 Technical Criteria
Given
A special manifest transaction is being created
When
The record type needs to be assigned
Then
The record type is set to 'CA' indicating Canadian processing
R-GCX146-cbl-00738
Increment Spawn Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Spawn Counter' is invoked, and assuming that a special manifest transaction is being created, when the transaction is queued for processing, the desired outcome is that the spawn counter is incremented by one to track the new transaction.
💻 Technical Criteria
Given
A special manifest transaction is being created
When
The transaction is queued for processing
Then
The spawn counter is incremented by one to track the new transaction
R-GCX146-cbl-00740
Queue Special Manifest Transaction
Action Rules
📊 Business Logic Narrative
When the process 'Queue Special Manifest Transaction' is invoked, and assuming that a complete special manifest input structure has been built, when the transaction is ready for processing, the desired outcome is that the transaction is queued in the special manifest processing queue for execution.
💻 Technical Criteria
Given
A complete special manifest input structure has been built
When
The transaction is ready for processing
Then
The transaction is queued in the special manifest processing queue for execution
R-GCX146-cbl-00765
Check Processing Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check Processing Status' is invoked, and assuming that a train has completed processing, when the system checks the processing status, the desired outcome is that the system determines if confirmation generation should proceed based on processing success.
💻 Technical Criteria
Given
A train has completed processing
When
The system checks the processing status
Then
The system determines if confirmation generation should proceed based on processing success
R-GCX146-cbl-00767
Gather Train Summary Data
Process Rules
📊 Business Logic Narrative
When the process 'Gather Train Summary Data' is invoked, and assuming that train processing completed successfully and confirmation generation is approved, when the system gathers train summary data, the desired outcome is that train identification, station information, and processing details are collected for message formatting.
💻 Technical Criteria
Given
Train processing completed successfully and confirmation generation is approved
When
The system gathers train summary data
Then
Train identification, station information, and processing details are collected for message formatting
R-GCX146-cbl-00773
Set Message Priority
Process Rules
📊 Business Logic Narrative
When the process 'Set Message Priority' is invoked, and assuming that confirmation message content has been formatted with all required information, when the system sets message priority, the desired outcome is that message priority is assigned based on confirmation message type and distribution requirements.
💻 Technical Criteria
Given
Confirmation message content has been formatted with all required information
When
The system sets message priority
Then
Message priority is assigned based on confirmation message type and distribution requirements
R-GCX146-cbl-00774
Queue Confirmation Message
Action Rules
📊 Business Logic Narrative
When the process 'Queue Confirmation Message' is invoked, and assuming that confirmation message has been formatted and priority assigned, when the system queues the confirmation message, the desired outcome is that message is placed in distribution queue for delivery to originating terminal and other designated recipients.
💻 Technical Criteria
Given
Confirmation message has been formatted and priority assigned
When
The system queues the confirmation message
Then
Message is placed in distribution queue for delivery to originating terminal and other designated recipients
R-GCX146-cbl-00775
Send to Message Distribution
Action Rules
📊 Business Logic Narrative
When the process 'Send to Message Distribution' is invoked, and assuming that confirmation message has been queued for distribution, when the system sends to message distribution, the desired outcome is that message is processed through distribution system and delivered to designated terminals and recipients.
💻 Technical Criteria
Given
Confirmation message has been queued for distribution
When
The system sends to message distribution
Then
Message is processed through distribution system and delivered to designated terminals and recipients
R-GCX146-cbl-00776
Log Confirmation Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log Confirmation Activity' is invoked, and assuming that confirmation message has been sent to distribution system, when the system logs confirmation activity, the desired outcome is that confirmation generation, message content summary, distribution status, and timestamp are recorded in system audit log.
💻 Technical Criteria
Given
Confirmation message has been sent to distribution system
When
The system logs confirmation activity
Then
Confirmation generation, message content summary, distribution status, and timestamp are recorded in system audit log
R-GCX146-cbl-00803
Set Status to 'TRANSIT'
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to 'TRANSIT'' is invoked, and assuming that the transit status code has been evaluated as 't', when the system processes the transit classification, the desired outcome is that the system sets the status to 'transit'.
💻 Technical Criteria
Given
The transit status code has been evaluated as 'T'
When
The system processes the transit classification
Then
The system sets the status to 'TRANSIT'
R-GCX146-cbl-00804
Set Status to 'RETURN'
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to 'RETURN'' is invoked, and assuming that the transit status code has been evaluated as 'r', when the system processes the return classification, the desired outcome is that the system sets the status to 'return'.
💻 Technical Criteria
Given
The transit status code has been evaluated as 'R'
When
The system processes the return classification
Then
The system sets the status to 'RETURN'
R-GCX146-cbl-00822
Get Email User Lists from Station Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Get Email User Lists from Station Configuration' is invoked, and assuming that a station code is available for email distribution, when the system needs to determine email recipients, the desired outcome is that the system should lookup email addresses from cusemail table using the station code and retrieve the configured user email lists.
💻 Technical Criteria
Given
A station code is available for email distribution
When
The system needs to determine email recipients
Then
The system should lookup email addresses from CUSEMAIL table using the station code and retrieve the configured user email lists
R-GCX146-cbl-00833
Email Send Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Send Successful?' is invoked, and assuming that an email has been sent via the primary email service, when the system checks the email transmission status, the desired outcome is that if the email was successful, proceed to log the transmission, otherwise initiate fallback email procedures.
💻 Technical Criteria
Given
An email has been sent via the primary email service
When
The system checks the email transmission status
Then
If the email was successful, proceed to log the transmission, otherwise initiate fallback email procedures
R-GCX146-cbl-00836
Log Email Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Log Email Transmission' is invoked, and assuming that an email has been successfully transmitted (either primary or fallback), when the system logs the email transmission, the desired outcome is that the system should record the transmission details including recipients, timestamp, and delivery status for audit purposes.
💻 Technical Criteria
Given
An email has been successfully transmitted (either primary or fallback)
When
The system logs the email transmission
Then
The system should record the transmission details including recipients, timestamp, and delivery status for audit purposes
R-GCX146-cbl-00838
Email Distribution Failed
Process Rules
📊 Business Logic Narrative
When the process 'Email Distribution Failed' is invoked, and assuming that both primary and fallback email transmissions have failed, when the email distribution fails completely, the desired outcome is that the system should mark the distribution as failed and handle the error condition appropriately.
💻 Technical Criteria
Given
Both primary and fallback email transmissions have failed
When
The email distribution fails completely
Then
The system should mark the distribution as failed and handle the error condition appropriately
R-GCX146-cbl-01336
Email Users Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Users Found?' is invoked, and assuming that email user lookup has been performed for a station, when the system checks if any email users were found in the configuration, the desired outcome is that if email users are found, proceed with email processing, otherwise skip email processing and mark as no users configured.
💻 Technical Criteria
Given
Email user lookup has been performed for a station
When
The system checks if any email users were found in the configuration
Then
If email users are found, proceed with email processing, otherwise skip email processing and mark as no users configured
R-GCX146-cbl-01344
Send Email via EMCSEND3
Action Rules
📊 Business Logic Narrative
When the process 'Send Email via EMCSEND3' is invoked, and assuming that email message is finalized and ready for transmission, when the system calls emcsend3 to send the email, the desired outcome is that attempt to transmit the email to configured recipients using the email service.
💻 Technical Criteria
Given
Email message is finalized and ready for transmission
When
The system calls EMCSEND3 to send the email
Then
Attempt to transmit the email to configured recipients using the email service
R-GCX146-cbl-01345
Email Send Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Email Send Successful?' is invoked, and assuming that email transmission attempt has been made via emcsend3, when the system checks the transmission result, the desired outcome is that if email send was successful, log successful transmission, otherwise attempt fallback email delivery.
💻 Technical Criteria
Given
Email transmission attempt has been made via EMCSEND3
When
The system checks the transmission result
Then
If email send was successful, log successful transmission, otherwise attempt fallback email delivery
R-GCX146-cbl-01348
Fallback Send Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Fallback Send Successful?' is invoked, and assuming that fallback email transmission attempt has been made, when the system checks the fallback transmission result, the desired outcome is that if fallback send was successful, log successful transmission, otherwise log email failure.
💻 Technical Criteria
Given
Fallback email transmission attempt has been made
When
The system checks the fallback transmission result
Then
If fallback send was successful, log successful transmission, otherwise log email failure
R-GCX146-cbl-01350
No Email Users Configured
Process Rules
📊 Business Logic Narrative
When the process 'No Email Users Configured' is invoked, and assuming that email user lookup found no configured users for the station, when the system processes the no-users scenario, the desired outcome is that skip email processing, log that no email users are configured, and proceed to complete email processing.
💻 Technical Criteria
Given
Email user lookup found no configured users for the station
When
The system processes the no-users scenario
Then
Skip email processing, log that no email users are configured, and proceed to complete email processing
R-GCX146-cbl-01517
Access Station Configuration Table
Action Rules
📊 Business Logic Narrative
When the process 'Access Station Configuration Table' is invoked, and assuming that a station code is provided for email configuration lookup, when the system accesses the station configuration table, the desired outcome is that the station's email configuration data is retrieved for processing.
💻 Technical Criteria
Given
A station code is provided for email configuration lookup
When
The system accesses the station configuration table
Then
The station's email configuration data is retrieved for processing
R-GCX146-cbl-01518
Retrieve AECWRKTB Email Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve AECWRKTB Email Configuration' is invoked, and assuming that station configuration data is available, when the system queries aecwrktb email configuration table, the desired outcome is that email user configuration data is retrieved for the station.
💻 Technical Criteria
Given
Station configuration data is available
When
The system queries AECWRKTB email configuration table
Then
Email user configuration data is retrieved for the station
R-GCX146-cbl-01519
Email Users Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Users Found?' is invoked, and assuming that email configuration data has been retrieved from aecwrktb table, when the system checks for the presence of email users, the desired outcome is that processing continues if email users are found, otherwise an email configuration error is raised.
💻 Technical Criteria
Given
Email configuration data has been retrieved from AECWRKTB table
When
The system checks for the presence of email users
Then
Processing continues if email users are found, otherwise an email configuration error is raised
R-GCX146-cbl-01520
Extract First Email User ID
Process Rules
📊 Business Logic Narrative
When the process 'Extract First Email User ID' is invoked, and assuming that email users are found in the configuration, when the system processes the email user list, the desired outcome is that the first email user id is extracted for validation.
💻 Technical Criteria
Given
Email users are found in the configuration
When
The system processes the email user list
Then
The first email user ID is extracted for validation
R-GCX146-cbl-01521
Validate Email User ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Email User ID Format' is invoked, and assuming that an email user id has been extracted from the configuration, when the system validates the email user id format, the desired outcome is that the user id is accepted if it meets format requirements, otherwise it is rejected.
💻 Technical Criteria
Given
An email user ID has been extracted from the configuration
When
The system validates the email user ID format
Then
The user ID is accepted if it meets format requirements, otherwise it is rejected
R-GCX146-cbl-01522
Add User to Email Distribution List
Process Rules
📊 Business Logic Narrative
When the process 'Add User to Email Distribution List' is invoked, and assuming that an email user id has passed format validation, when the system processes the valid email user, the desired outcome is that the user is added to the email distribution list.
💻 Technical Criteria
Given
An email user ID has passed format validation
When
The system processes the valid email user
Then
The user is added to the email distribution list
R-GCX146-cbl-01523
Check for Additional Email Users
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Additional Email Users' is invoked, and assuming that an email user has been processed (valid or invalid), when the system checks for additional email users in the configuration, the desired outcome is that processing continues with next user if available, otherwise proceeds to finalize the list.
💻 Technical Criteria
Given
An email user has been processed (valid or invalid)
When
The system checks for additional email users in the configuration
Then
Processing continues with next user if available, otherwise proceeds to finalize the list
R-GCX146-cbl-01524
Extract Next Email User ID
Process Rules
📊 Business Logic Narrative
When the process 'Extract Next Email User ID' is invoked, and assuming that additional email users are available in the configuration, when the system processes the next email user, the desired outcome is that the next email user id is extracted for validation.
💻 Technical Criteria
Given
Additional email users are available in the configuration
When
The system processes the next email user
Then
The next email user ID is extracted for validation
R-GCX146-cbl-01525
Set Primary Email Distribution
Process Rules
📊 Business Logic Narrative
When the process 'Set Primary Email Distribution' is invoked, and assuming that all email users have been processed and validated, when the system sets up the primary email distribution, the desired outcome is that a primary email distribution list is established with all valid users.
💻 Technical Criteria
Given
All email users have been processed and validated
When
The system sets up the primary email distribution
Then
A primary email distribution list is established with all valid users
R-GCX146-cbl-01526
Primary Email Failed?
Decision Rules
📊 Business Logic Narrative
When the process 'Primary Email Failed?' is invoked, and assuming that primary email distribution has been attempted, when the system checks the success of primary email setup, the desired outcome is that fallback procedures are initiated if primary email failed, otherwise processing continues normally.
💻 Technical Criteria
Given
Primary email distribution has been attempted
When
The system checks the success of primary email setup
Then
Fallback procedures are initiated if primary email failed, otherwise processing continues normally
R-GCX146-cbl-01527
Set Fallback Email Recipients
Process Rules
📊 Business Logic Narrative
When the process 'Set Fallback Email Recipients' is invoked, and assuming that primary email distribution has failed, when the system sets up fallback email recipients, the desired outcome is that alternative email recipients are configured to ensure message delivery.
💻 Technical Criteria
Given
Primary email distribution has failed
When
The system sets up fallback email recipients
Then
Alternative email recipients are configured to ensure message delivery
R-GCX146-cbl-01529
Finalize Email User List
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Email User List' is invoked, and assuming that email distribution setup is complete (either primary or fallback), when the system finalizes the email user list, the desired outcome is that the email user list is prepared and ready for message distribution.
💻 Technical Criteria
Given
Email distribution setup is complete (either primary or fallback)
When
The system finalizes the email user list
Then
The email user list is prepared and ready for message distribution
R-GCX146-cbl-01666
Retrieve Email User List from Station Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Email User List from Station Configuration' is invoked, and assuming that a station code exists in the system, when the system needs to retrieve email user configuration for that station, the desired outcome is that the system should lookup and retrieve the email user list from the station configuration table.
💻 Technical Criteria
Given
A station code exists in the system
When
The system needs to retrieve email user configuration for that station
Then
The system should lookup and retrieve the email user list from the station configuration table
R-GCX146-cbl-01667
Check Email User ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Check Email User ID Format' is invoked, and assuming that an email address is provided for validation, when the system checks the email format, the desired outcome is that the email address must contain an @ symbol and have valid domain format to be considered valid.
💻 Technical Criteria
Given
An email address is provided for validation
When
The system checks the email format
Then
The email address must contain an @ symbol and have valid domain format to be considered valid
R-GCX146-cbl-01669
Check for Fallback Email IDs
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Fallback Email IDs' is invoked, and assuming that primary email validation has failed, when the system checks for available fallback options, the desired outcome is that the system should identify if alternative email addresses are configured and available for use.
💻 Technical Criteria
Given
Primary email validation has failed
When
The system checks for available fallback options
Then
The system should identify if alternative email addresses are configured and available for use
R-GCX146-cbl-01670
Use Default Email OM01247/AEI9999
Action Rules
📊 Business Logic Narrative
When the process 'Use Default Email OM01247/AEI9999' is invoked, and assuming that no valid email addresses are found in configuration and fallback options are available, when the system needs to assign a default email for notifications, the desired outcome is that the system should use the default email addresses om01247 and aei9999 as recipients.
💻 Technical Criteria
Given
No valid email addresses are found in configuration and fallback options are available
When
The system needs to assign a default email for notifications
Then
The system should use the default email addresses OM01247 and AEI9999 as recipients
R-GCX146-cbl-01671
Mark Email ID as Invalid
Action Rules
📊 Business Logic Narrative
When the process 'Mark Email ID as Invalid' is invoked, and assuming that email validation has failed and no fallback email addresses are available, when the system processes the validation result, the desired outcome is that the system should mark the email id as invalid and prevent its use for notifications.
💻 Technical Criteria
Given
Email validation has failed and no fallback email addresses are available
When
The system processes the validation result
Then
The system should mark the email ID as invalid and prevent its use for notifications
R-GCX146-cbl-01672
Continue with Valid Email ID
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Valid Email ID' is invoked, and assuming that a valid email address has been identified through validation or fallback assignment, when the system is ready to proceed with email operations, the desired outcome is that the system should continue processing using the validated email address for notifications.
💻 Technical Criteria
Given
A valid email address has been identified through validation or fallback assignment
When
The system is ready to proceed with email operations
Then
The system should continue processing using the validated email address for notifications
R-GCX146-cbl-01815
Retrieve Email User ID from Station Configuration
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Email User ID from Station Configuration' is invoked, and assuming that a station code exists in the system, when the system needs to retrieve email user configuration for that station, the desired outcome is that the system should access the station configuration table and extract the email user id associated with the station.
💻 Technical Criteria
Given
A station code exists in the system
When
The system needs to retrieve email user configuration for that station
Then
The system should access the station configuration table and extract the email user ID associated with the station
R-GCX146-cbl-01817
Validate Email Format Structure
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Email Format Structure' is invoked, and assuming that an email user id is present in the station configuration, when the system validates the email format structure, the desired outcome is that the system should verify the email follows standard email format conventions including proper domain and address structure.
💻 Technical Criteria
Given
An email user ID is present in the station configuration
When
The system validates the email format structure
Then
The system should verify the email follows standard email format conventions including proper domain and address structure
R-GCX146-cbl-01818
Valid Email Format?
Decision Rules
📊 Business Logic Narrative
When the process 'Valid Email Format?' is invoked, and assuming that email format structure validation has been performed, when the system evaluates the validation results, the desired outcome is that the system should determine if the email format is valid based on standard email formatting rules.
💻 Technical Criteria
Given
Email format structure validation has been performed
When
The system evaluates the validation results
Then
The system should determine if the email format is valid based on standard email formatting rules
R-GCX146-cbl-01819
Set Email User ID as Valid
Action Rules
📊 Business Logic Narrative
When the process 'Set Email User ID as Valid' is invoked, and assuming that the email user id has passed format validation, when the system processes the validation success, the desired outcome is that the system should set the email user id status as valid and enable email operations for the station.
💻 Technical Criteria
Given
The email user ID has passed format validation
When
The system processes the validation success
Then
The system should set the email user ID status as valid and enable email operations for the station
R-GCX146-cbl-01820
Set Email User ID as Invalid
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Email User ID as Invalid', assuming that the email user id is either not present or has failed format validation, when the system processes the validation failure, the desired outcome is that the system should set the email user id status as invalid and prevent email operations for the station.
💻 Technical Criteria
EXCLUDING
The email user ID is either not present or has failed format validation
When
The system processes the validation failure
Then
The system should set the email user ID status as invalid and prevent email operations for the station
R-GCX146-cbl-01821
Log Format Validation Result
Action Rules
📊 Business Logic Narrative
When the process 'Log Format Validation Result' is invoked, and assuming that email validation process has been completed with either valid or invalid result, when the system logs the validation outcome, the desired outcome is that the system should record the validation result including station code and email status for audit trail.
💻 Technical Criteria
Given
Email validation process has been completed with either valid or invalid result
When
The system logs the validation outcome
Then
The system should record the validation result including station code and email status for audit trail
R-GCX146-cbl-01822
Return Validation Status
Action Rules
📊 Business Logic Narrative
When the process 'Return Validation Status' is invoked, and assuming that email validation and logging have been completed, when the system returns the validation status, the desired outcome is that the system should provide the final validation result indicating whether email operations can proceed for the station.
💻 Technical Criteria
Given
Email validation and logging have been completed
When
The system returns the validation status
Then
The system should provide the final validation result indicating whether email operations can proceed for the station
R-GCX146-cbl-01352
Send Current Email Batch
Action Rules
📊 Business Logic Narrative
When the process 'Send Current Email Batch' is invoked, and assuming that an email message has reached its maximum line capacity of 699 lines, when the continuation processing is triggered, the desired outcome is that the system should send the current email batch using the email delivery service.
💻 Technical Criteria
Given
An email message has reached its maximum line capacity of 699 lines
When
The continuation processing is triggered
Then
The system should send the current email batch using the email delivery service
R-GCX146-cbl-01358
Increment Line Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Line Counter' is invoked, and assuming that a line has been successfully added to the email message buffer, when the line addition is complete, the desired outcome is that the system should increment the line counter by one to maintain accurate count of lines in current message.
💻 Technical Criteria
Given
A line has been successfully added to the email message buffer
When
The line addition is complete
Then
The system should increment the line counter by one to maintain accurate count of lines in current message
R-GCX146-cbl-01535
Reset Line Counter
Process Rules
📊 Business Logic Narrative
When the process 'Reset Line Counter' is invoked, and assuming that a new email segment is being prepared after sending a previous batch, when the system starts processing lines for the new segment, the desired outcome is that the line counter should be reset to zero to track lines in the new segment.
💻 Technical Criteria
Given
A new email segment is being prepared after sending a previous batch
When
The system starts processing lines for the new segment
Then
The line counter should be reset to zero to track lines in the new segment
R-GCX146-cbl-00839
Check Auto-FAX Configuration
Decision Rules
📊 Business Logic Narrative
When the process 'Check Auto-FAX Configuration' is invoked, and assuming that a merlin message transmission is initiated for a specific station, when the system checks the station configuration in gcstbrt, the desired outcome is that the auto-fax capability flag is retrieved and evaluated to determine if fax routing should be enabled.
💻 Technical Criteria
Given
A Merlin message transmission is initiated for a specific station
When
The system checks the station configuration in GCSTBRT
Then
The auto-FAX capability flag is retrieved and evaluated to determine if FAX routing should be enabled
R-GCX146-cbl-00841
Set Copy IDs for FAX Distribution
Process Rules
📊 Business Logic Narrative
When the process 'Set Copy IDs for FAX Distribution' is invoked, and assuming that fax routing parameters are configured, when the system prepares copy distribution settings, the desired outcome is that copy ids are assigned based on station configuration to enable multi-recipient fax delivery.
💻 Technical Criteria
Given
FAX routing parameters are configured
When
The system prepares copy distribution settings
Then
Copy IDs are assigned based on station configuration to enable multi-recipient FAX delivery
R-GCX146-cbl-00843
Check Message Size
Validation Rules
📊 Business Logic Narrative
When the process 'Check Message Size' is invoked, and assuming that a merlin message is prepared for transmission, when the system counts the total number of message lines, the desired outcome is that if message exceeds 699 lines, it is flagged for continuation processing, otherwise it proceeds as standard transmission.
💻 Technical Criteria
Given
A Merlin message is prepared for transmission
When
The system counts the total number of message lines
Then
If message exceeds 699 lines, it is flagged for continuation processing, otherwise it proceeds as standard transmission
R-GCX146-cbl-00844
Send Standard Merlin Message
Action Rules
📊 Business Logic Narrative
When the process 'Send Standard Merlin Message' is invoked, and assuming that a merlin message is prepared and is 699 lines or fewer, when the system initiates transmission, the desired outcome is that the complete message is sent as a single transmission unit.
💻 Technical Criteria
Given
A Merlin message is prepared and is 699 lines or fewer
When
The system initiates transmission
Then
The complete message is sent as a single transmission unit
R-GCX146-cbl-00845
Split Message for Continuation
Process Rules
📊 Business Logic Narrative
When the process 'Split Message for Continuation' is invoked, and assuming that a merlin message exceeds 699 lines, when the system processes the oversized message, the desired outcome is that the message is divided into multiple batches with the first batch containing up to 699 lines.
💻 Technical Criteria
Given
A Merlin message exceeds 699 lines
When
The system processes the oversized message
Then
The message is divided into multiple batches with the first batch containing up to 699 lines
R-GCX146-cbl-00848
Send Remaining Message Batches
Action Rules
📊 Business Logic Narrative
When the process 'Send Remaining Message Batches' is invoked, and assuming that message batches with continuation headers are prepared, when the system processes remaining batches, the desired outcome is that each batch is transmitted sequentially until all message content is delivered.
💻 Technical Criteria
Given
Message batches with continuation headers are prepared
When
The system processes remaining batches
Then
Each batch is transmitted sequentially until all message content is delivered
R-GCX146-cbl-00849
Call EMCSEND3 for Transmission
Action Rules
📊 Business Logic Narrative
When the process 'Call EMCSEND3 for Transmission' is invoked, and assuming that a message or message batch is ready for transmission, when the system calls emcsend3 service, the desired outcome is that the message is transmitted through the merlin communication channel.
💻 Technical Criteria
Given
A message or message batch is ready for transmission
When
The system calls EMCSEND3 service
Then
The message is transmitted through the Merlin communication channel
R-GCX146-cbl-00850
Transmission Successful?
Decision Rules
📊 Business Logic Narrative
When the process 'Transmission Successful?' is invoked, and assuming that emcsend3 service has been called for message transmission, when the system receives transmission response, the desired outcome is that if transmission is successful, proceed to logging, otherwise handle transmission error.
💻 Technical Criteria
Given
EMCSEND3 service has been called for message transmission
When
The system receives transmission response
Then
If transmission is successful, proceed to logging, otherwise handle transmission error
R-GCX146-cbl-00851
Log Successful Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Log Successful Transmission' is invoked, and assuming that message transmission is confirmed successful, when the system processes the success response, the desired outcome is that transmission details are logged including timestamp and delivery confirmation.
💻 Technical Criteria
Given
Message transmission is confirmed successful
When
The system processes the success response
Then
Transmission details are logged including timestamp and delivery confirmation
R-GCX146-cbl-00852
Handle Transmission Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Transmission Error' is invoked, and assuming that message transmission fails, when the system receives error response from emcsend3, the desired outcome is that error details are logged and appropriate error handling procedures are initiated.
💻 Technical Criteria
Given
Message transmission fails
When
The system receives error response from EMCSEND3
Then
Error details are logged and appropriate error handling procedures are initiated
R-GCX146-cbl-01361
Check Auto-FAX Configuration Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Check Auto-FAX Configuration Flag' is invoked, and assuming that a station configuration record exists with auto-fax settings, when the system checks the auto-fax configuration flag in the station record, the desired outcome is that the system should proceed to station fax flag validation if auto-fax is enabled, otherwise skip fax configuration entirely.
💻 Technical Criteria
Given
A station configuration record exists with auto-FAX settings
When
The system checks the auto-FAX configuration flag in the station record
Then
The system should proceed to station FAX flag validation if auto-FAX is enabled, otherwise skip FAX configuration entirely
R-GCX146-cbl-01362
Check Station FAX Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Check Station FAX Flag' is invoked, and assuming that auto-fax configuration is enabled and a station configuration record exists, when the system checks the station fax flag in the station configuration record, the desired outcome is that the system should proceed with fax routing setup if the station fax flag is active, otherwise skip fax configuration.
💻 Technical Criteria
Given
Auto-FAX configuration is enabled and a station configuration record exists
When
The system checks the station FAX flag in the station configuration record
Then
The system should proceed with FAX routing setup if the station FAX flag is active, otherwise skip FAX configuration
R-GCX146-cbl-01363
Set Up FAX Routing Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Set Up FAX Routing Parameters' is invoked, and assuming that both auto-fax configuration flag and station fax flag are enabled, when the system sets up fax routing parameters, the desired outcome is that the system should configure copy ids for distribution, set external fax addressing, prepare merlin transmission parameters, and call emcsend for fax routing.
💻 Technical Criteria
Given
Both auto-FAX configuration flag and station FAX flag are enabled
When
The system sets up FAX routing parameters
Then
The system should configure copy IDs for distribution, set external FAX addressing, prepare Merlin transmission parameters, and call EMCSEND for FAX routing
R-GCX146-cbl-01364
Call EMCSEND for FAX Routing
Action Rules
📊 Business Logic Narrative
When the process 'Call EMCSEND for FAX Routing' is invoked, and assuming that fax routing parameters are properly configured with copy ids and external addressing, when the system calls the emcsend service for fax routing, the desired outcome is that the external fax routing service should be invoked to handle the transmission.
💻 Technical Criteria
Given
FAX routing parameters are properly configured with copy IDs and external addressing
When
The system calls the EMCSEND service for FAX routing
Then
The external FAX routing service should be invoked to handle the transmission
R-GCX146-cbl-01539
Check Auto-FAX Setting
Validation Rules
📊 Business Logic Narrative
When the process 'Check Auto-FAX Setting' is invoked, and assuming that a station configuration record exists in gcstbrt, when the system checks the auto-fax setting, the desired outcome is that the system reads the gcstbrt-ad-auto-fax field to determine if automatic fax is enabled.
💻 Technical Criteria
Given
A station configuration record exists in GCSTBRT
When
The system checks the Auto-FAX setting
Then
The system reads the GCSTBRT-AD-AUTO-FAX field to determine if automatic FAX is enabled
R-GCX146-cbl-01540
Auto-FAX Enabled?
Decision Rules
📊 Business Logic Narrative
When the process 'Auto-FAX Enabled?' is invoked, and assuming that the auto-fax setting has been retrieved from station configuration, when the gcstbrt-ad-auto-fax field equals 'y', the desired outcome is that the system proceeds to set fax routing flag, otherwise skips fax configuration.
💻 Technical Criteria
Given
The Auto-FAX setting has been retrieved from station configuration
When
The GCSTBRT-AD-AUTO-FAX field equals 'Y'
Then
The system proceeds to set FAX routing flag, otherwise skips FAX configuration
R-GCX146-cbl-01541
Set FAX Routing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set FAX Routing Flag' is invoked, and assuming that auto-fax is enabled (gcstbrt-ad-auto-fax = 'y'), when the system processes fax routing configuration, the desired outcome is that the system sets ws-fax-routing to 'y' to enable fax routing functionality.
💻 Technical Criteria
Given
Auto-FAX is enabled (GCSTBRT-AD-AUTO-FAX = 'Y')
When
The system processes FAX routing configuration
Then
The system sets WS-FAX-ROUTING to 'Y' to enable FAX routing functionality
R-GCX146-cbl-01542
Configure Copy Distribution IDs
Process Rules
📊 Business Logic Narrative
When the process 'Configure Copy Distribution IDs' is invoked, and assuming that fax routing flag has been set to 'y', when the system configures copy distribution parameters, the desired outcome is that the system sets up copy distribution ids for proper fax message routing.
💻 Technical Criteria
Given
FAX routing flag has been set to 'Y'
When
The system configures copy distribution parameters
Then
The system sets up copy distribution IDs for proper FAX message routing
R-GCX146-cbl-01543
Set External FAX Addressing
Process Rules
📊 Business Logic Narrative
When the process 'Set External FAX Addressing' is invoked, and assuming that copy distribution ids have been configured, when the system sets up external fax addressing, the desired outcome is that the system configures external fax address parameters for proper message delivery.
💻 Technical Criteria
Given
Copy distribution IDs have been configured
When
The system sets up external FAX addressing
Then
The system configures external FAX address parameters for proper message delivery
R-GCX146-cbl-01544
Apply Station FAX Configuration
Process Rules
📊 Business Logic Narrative
When the process 'Apply Station FAX Configuration' is invoked, and assuming that external fax addressing has been configured, when the system applies station fax configuration, the desired outcome is that the system retrieves and applies station-specific fax settings from gcstbrt configuration.
💻 Technical Criteria
Given
External FAX addressing has been configured
When
The system applies station FAX configuration
Then
The system retrieves and applies station-specific FAX settings from GCSTBRT configuration
R-GCX146-cbl-01545
Station FAX Flag Set?
Decision Rules
📊 Business Logic Narrative
When the process 'Station FAX Flag Set?' is invoked, and assuming that station fax configuration has been applied, when the system checks the station fax flag (gcstbrt-sc-fax-flag), the desired outcome is that the system determines whether to enable fax routing based on the flag setting.
💻 Technical Criteria
Given
Station FAX configuration has been applied
When
The system checks the station FAX flag (GCSTBRT-SC-FAX-FLAG)
Then
The system determines whether to enable FAX routing based on the flag setting
R-GCX146-cbl-01546
Enable FAX Routing
Action Rules
📊 Business Logic Narrative
When the process 'Enable FAX Routing' is invoked, and assuming that station fax flag is set in the configuration, when the system enables fax routing, the desired outcome is that the system activates fax routing capabilities for the station.
💻 Technical Criteria
Given
Station FAX flag is set in the configuration
When
The system enables FAX routing
Then
The system activates FAX routing capabilities for the station
R-GCX146-cbl-01547
Configure FAX Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Configure FAX Parameters' is invoked, and assuming that fax routing has been enabled, when the system configures fax parameters, the desired outcome is that the system applies final fax routing settings and completes the configuration process.
💻 Technical Criteria
Given
FAX routing has been enabled
When
The system configures FAX parameters
Then
The system applies final FAX routing settings and completes the configuration process
R-GCX146-cbl-01548
Complete FAX Configuration
Process Rules
📊 Business Logic Narrative
When the process 'Complete FAX Configuration' is invoked, and assuming that fax configuration process has been executed (either enabled or skipped), when the system completes fax configuration, the desired outcome is that the system finalizes the fax routing configuration and continues with normal processing.
💻 Technical Criteria
Given
FAX configuration process has been executed (either enabled or skipped)
When
The system completes FAX configuration
Then
The system finalizes the FAX routing configuration and continues with normal processing
R-GCX146-cbl-01549
Skip FAX Configuration
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Skip FAX Configuration', assuming that either auto-fax is disabled (gcstbrt-ad-auto-fax ≠ 'y') or station fax flag is not set, when the system processes fax configuration, the desired outcome is that the system skips all fax routing configuration steps and proceeds to completion.
💻 Technical Criteria
EXCLUDING
Either Auto-FAX is disabled (GCSTBRT-AD-AUTO-FAX ≠ 'Y') or station FAX flag is not set
When
The system processes FAX configuration
Then
The system skips all FAX routing configuration steps and proceeds to completion
R-GCX146-cbl-01366
Set Message Type and Headers
Process Rules
📊 Business Logic Narrative
When the process 'Set Message Type and Headers' is invoked, and assuming that a message buffer has been initialized for merlin transmission, when the system determines the message type and required headers, the desired outcome is that the appropriate message type identifier and standard headers are set in the message buffer.
💻 Technical Criteria
Given
A message buffer has been initialized for Merlin transmission
When
The system determines the message type and required headers
Then
The appropriate message type identifier and standard headers are set in the message buffer
R-GCX146-cbl-01367
Format Train Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Train Information' is invoked, and assuming that message headers have been established, when train information needs to be formatted for the message, the desired outcome is that train id, date/time, and operational details are formatted and added to the message content.
💻 Technical Criteria
Given
Message headers have been established
When
Train information needs to be formatted for the message
Then
Train ID, date/time, and operational details are formatted and added to the message content
R-GCX146-cbl-01368
Add Station Names to Message
Process Rules
📊 Business Logic Narrative
When the process 'Add Station Names to Message' is invoked, and assuming that train information has been formatted in the message, when station information needs to be included, the desired outcome is that from and to station codes and names are added to the message content.
💻 Technical Criteria
Given
Train information has been formatted in the message
When
Station information needs to be included
Then
From and to station codes and names are added to the message content
R-GCX146-cbl-01377
Segment Message for Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Segment Message for Transmission' is invoked, and assuming that the message line limit has been reached, when message segmentation is required, the desired outcome is that the message is divided into appropriate segments for separate transmission.
💻 Technical Criteria
Given
The message line limit has been reached
When
Message segmentation is required
Then
The message is divided into appropriate segments for separate transmission
R-GCX146-cbl-01378
Add Continuation Headers
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Headers' is invoked, and assuming that a message has been segmented for transmission, when continuation headers need to be added, the desired outcome is that appropriate continuation headers are added to indicate the message sequence and relationship.
💻 Technical Criteria
Given
A message has been segmented for transmission
When
Continuation headers need to be added
Then
Appropriate continuation headers are added to indicate the message sequence and relationship
R-GCX146-cbl-01379
Format Message Lines for Merlin
Process Rules
📊 Business Logic Narrative
When the process 'Format Message Lines for Merlin' is invoked, and assuming that message content has been prepared (with continuation headers if segmented), when final message line formatting is applied, the desired outcome is that message lines are formatted according to merlin system specifications.
💻 Technical Criteria
Given
Message content has been prepared (with continuation headers if segmented)
When
Final message line formatting is applied
Then
Message lines are formatted according to Merlin system specifications
R-GCX146-cbl-01380
Set FAX Routing Information
Process Rules
📊 Business Logic Narrative
When the process 'Set FAX Routing Information' is invoked, and assuming that message lines have been formatted for merlin, when fax routing information needs to be configured, the desired outcome is that station-specific fax routing parameters are set based on system configuration.
💻 Technical Criteria
Given
Message lines have been formatted for Merlin
When
FAX routing information needs to be configured
Then
Station-specific FAX routing parameters are set based on system configuration
R-GCX146-cbl-01381
Auto-FAX Enabled?
Decision Rules
📊 Business Logic Narrative
When the process 'Auto-FAX Enabled?' is invoked, and assuming that fax routing information has been configured, when the system evaluates auto-fax settings, the desired outcome is that if auto-fax is enabled, fax copy ids are added, otherwise external fax addressing is configured.
💻 Technical Criteria
Given
FAX routing information has been configured
When
The system evaluates auto-FAX settings
Then
If auto-FAX is enabled, FAX copy IDs are added, otherwise external FAX addressing is configured
R-GCX146-cbl-01382
Add FAX Copy IDs
Process Rules
📊 Business Logic Narrative
When the process 'Add FAX Copy IDs' is invoked, and assuming that auto-fax has been determined to be enabled, when fax copy ids need to be added, the desired outcome is that appropriate fax copy identifiers are added to enable automatic fax distribution.
💻 Technical Criteria
Given
Auto-FAX has been determined to be enabled
When
FAX copy IDs need to be added
Then
Appropriate FAX copy identifiers are added to enable automatic FAX distribution
R-GCX146-cbl-01383
Set External FAX Addressing
Process Rules
📊 Business Logic Narrative
When the process 'Set External FAX Addressing' is invoked, and assuming that fax configuration is being finalized (either after adding copy ids or when auto-fax is disabled), when external fax addressing needs to be configured, the desired outcome is that external fax numbers and addressing parameters are set based on station configuration.
💻 Technical Criteria
Given
FAX configuration is being finalized (either after adding copy IDs or when auto-FAX is disabled)
When
External FAX addressing needs to be configured
Then
External FAX numbers and addressing parameters are set based on station configuration
R-GCX146-cbl-01384
Prepare Final Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Final Message Buffer' is invoked, and assuming that external fax addressing has been configured, when the final message buffer needs to be prepared, the desired outcome is that all message components are assembled into the final transmission-ready buffer.
💻 Technical Criteria
Given
External FAX addressing has been configured
When
The final message buffer needs to be prepared
Then
All message components are assembled into the final transmission-ready buffer
R-GCX146-cbl-01385
Message Ready for Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Message Ready for Transmission' is invoked, and assuming that the final message buffer has been prepared, when message preparation is complete, the desired outcome is that the message is marked as ready for transmission with all required components properly formatted.
💻 Technical Criteria
Given
The final message buffer has been prepared
When
Message preparation is complete
Then
The message is marked as ready for transmission with all required components properly formatted
R-GCX146-cbl-01550
Line Count > 699?
Validation Rules
📊 Business Logic Narrative
When the process 'Line Count > 699?' is invoked, and assuming that an email message is being prepared for transmission, when the system counts the number of lines in the message, the desired outcome is that if line count exceeds 699 lines, the system triggers message segmentation process.
💻 Technical Criteria
Given
An email message is being prepared for transmission
When
The system counts the number of lines in the message
Then
If line count exceeds 699 lines, the system triggers message segmentation process
R-GCX146-cbl-01551
Apply Line Segmentation
Process Rules
📊 Business Logic Narrative
When the process 'Apply Line Segmentation' is invoked, and assuming that an email message exceeds 699 lines, when the system applies line segmentation, the desired outcome is that the message is split into segments of maximum 699 lines each for separate transmission.
💻 Technical Criteria
Given
An email message exceeds 699 lines
When
The system applies line segmentation
Then
The message is split into segments of maximum 699 lines each for separate transmission
R-GCX146-cbl-01553
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that a message segment has been sent for transmission, when the system prepares for the next message segment, the desired outcome is that the message buffer is reset to prepare for new content.
💻 Technical Criteria
Given
A message segment has been sent for transmission
When
The system prepares for the next message segment
Then
The message buffer is reset to prepare for new content
R-GCX146-cbl-01554
Send Current Message Batch
Action Rules
📊 Business Logic Narrative
When the process 'Send Current Message Batch' is invoked, and assuming that a message batch is ready for transmission, when the system initiates transmission process, the desired outcome is that the emcsend3 email service is invoked to deliver the message.
💻 Technical Criteria
Given
A message batch is ready for transmission
When
The system initiates transmission process
Then
The EMCSEND3 email service is invoked to deliver the message
R-GCX146-cbl-01555
Apply Merlin Transmission Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Merlin Transmission Rules' is invoked, and assuming that message content is ready for formatting, when the system applies merlin transmission rules, the desired outcome is that message is formatted according to merlin system requirements for proper transmission.
💻 Technical Criteria
Given
Message content is ready for formatting
When
The system applies Merlin transmission rules
Then
Message is formatted according to Merlin system requirements for proper transmission
R-GCX146-cbl-01673
Check Auto-FAX Configuration
Decision Rules
📊 Business Logic Narrative
When the process 'Check Auto-FAX Configuration' is invoked, and assuming that a merlin transmission is being prepared, when the system checks the auto-fax configuration settings, the desired outcome is that the system identifies whether auto-fax is enabled or disabled for routing decisions.
💻 Technical Criteria
Given
A Merlin transmission is being prepared
When
The system checks the Auto-FAX configuration settings
Then
The system identifies whether Auto-FAX is enabled or disabled for routing decisions
R-GCX146-cbl-01674
Set FAX Routing Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Set FAX Routing Parameters' is invoked, and assuming that auto-fax is enabled for the transmission, when the system prepares fax routing parameters, the desired outcome is that fax-specific routing configuration is applied to the message.
💻 Technical Criteria
Given
Auto-FAX is enabled for the transmission
When
The system prepares FAX routing parameters
Then
FAX-specific routing configuration is applied to the message
R-GCX146-cbl-01675
Configure Copy IDs for FAX
Process Rules
📊 Business Logic Narrative
When the process 'Configure Copy IDs for FAX' is invoked, and assuming that fax routing parameters are being set, when the system configures copy distribution, the desired outcome is that appropriate copy ids are assigned for fax recipients.
💻 Technical Criteria
Given
FAX routing parameters are being set
When
The system configures copy distribution
Then
Appropriate copy IDs are assigned for FAX recipients
R-GCX146-cbl-01677
Prepare Merlin Message Format
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Merlin Message Format' is invoked, and assuming that a message needs to be transmitted via merlin, when the system prepares the message format, the desired outcome is that the message is formatted according to merlin transmission specifications.
💻 Technical Criteria
Given
A message needs to be transmitted via Merlin
When
The system prepares the message format
Then
The message is formatted according to Merlin transmission specifications
R-GCX146-cbl-01678
Set Message Type and Routing
Process Rules
📊 Business Logic Narrative
When the process 'Set Message Type and Routing' is invoked, and assuming that a merlin message format has been prepared, when the system configures message type and routing, the desired outcome is that appropriate message type classification and routing information is assigned.
💻 Technical Criteria
Given
A Merlin message format has been prepared
When
The system configures message type and routing
Then
Appropriate message type classification and routing information is assigned
R-GCX146-cbl-01679
Apply Line Segmentation Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Line Segmentation Rules' is invoked, and assuming that message type and routing have been configured, when the system applies line segmentation rules, the desired outcome is that message content is properly segmented according to transmission line limits.
💻 Technical Criteria
Given
Message type and routing have been configured
When
The system applies line segmentation rules
Then
Message content is properly segmented according to transmission line limits
R-GCX146-cbl-01680
Message Exceeds Line Limit?
Validation Rules
📊 Business Logic Narrative
When the process 'Message Exceeds Line Limit?' is invoked, and assuming that line segmentation rules have been applied to a message, when the system checks if the message exceeds the line limit, the desired outcome is that the system determines whether message segmentation is required based on line count limits.
💻 Technical Criteria
Given
Line segmentation rules have been applied to a message
When
The system checks if the message exceeds the line limit
Then
The system determines whether message segmentation is required based on line count limits
R-GCX146-cbl-01682
Add Continuation Headers
Process Rules
📊 Business Logic Narrative
When the process 'Add Continuation Headers' is invoked, and assuming that message segments have been created for a multi-part transmission, when the system adds continuation headers, the desired outcome is that each continuation segment includes appropriate headers indicating it is part of a multi-part message.
💻 Technical Criteria
Given
Message segments have been created for a multi-part transmission
When
The system adds continuation headers
Then
Each continuation segment includes appropriate headers indicating it is part of a multi-part message
R-GCX146-cbl-01683
Set Merlin Transmission Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Set Merlin Transmission Parameters' is invoked, and assuming that message formatting and segmentation is complete, when the system sets merlin transmission parameters, the desired outcome is that all necessary transmission parameters are configured for merlin delivery.
💻 Technical Criteria
Given
Message formatting and segmentation is complete
When
The system sets Merlin transmission parameters
Then
All necessary transmission parameters are configured for Merlin delivery
R-GCX146-cbl-01687
Apply Message Priority Rules
Policy Rules
📊 Business Logic Narrative
When the process 'Apply Message Priority Rules' is invoked, and assuming that message routing has been established (either primary or backup), when the system applies message priority rules, the desired outcome is that appropriate priority level is assigned to the message for transmission scheduling.
💻 Technical Criteria
Given
Message routing has been established (either primary or backup)
When
The system applies message priority rules
Then
Appropriate priority level is assigned to the message for transmission scheduling
R-GCX146-cbl-01688
Set Delivery Confirmation
Process Rules
📊 Business Logic Narrative
When the process 'Set Delivery Confirmation' is invoked, and assuming that message priority rules have been applied, when the system sets delivery confirmation, the desired outcome is that delivery confirmation requirements are configured according to message priority and business rules.
💻 Technical Criteria
Given
Message priority rules have been applied
When
The system sets delivery confirmation
Then
Delivery confirmation requirements are configured according to message priority and business rules
R-GCX146-cbl-01689
Execute Merlin Transmission
Action Rules
📊 Business Logic Narrative
When the process 'Execute Merlin Transmission' is invoked, and assuming that all transmission parameters and confirmation settings are configured, when the system executes merlin transmission, the desired outcome is that the message is transmitted via merlin with the configured parameters and routing.
💻 Technical Criteria
Given
All transmission parameters and confirmation settings are configured
When
The system executes Merlin transmission
Then
The message is transmitted via Merlin with the configured parameters and routing
R-GCX146-cbl-01690
Log Transmission Activity
Process Rules
📊 Business Logic Narrative
When the process 'Log Transmission Activity' is invoked, and assuming that merlin transmission has been executed, when the system logs transmission activity, the desired outcome is that transmission details are recorded in the system log for audit trail and monitoring.
💻 Technical Criteria
Given
Merlin transmission has been executed
When
The system logs transmission activity
Then
Transmission details are recorded in the system log for audit trail and monitoring
R-GCX146-cbl-01824
Auto-FAX = 'Y'?
Decision Rules
📊 Business Logic Narrative
When the process 'Auto-FAX = 'Y'?' is invoked, and assuming that the auto-fax setting has been retrieved from station configuration, when the auto-fax setting equals 'y', the desired outcome is that the system proceeds to check the fax flag configuration, otherwise it disables auto-fax and uses standard routing.
💻 Technical Criteria
Given
The Auto-FAX setting has been retrieved from station configuration
When
The Auto-FAX setting equals 'Y'
Then
The system proceeds to check the FAX flag configuration, otherwise it disables Auto-FAX and uses standard routing
R-GCX146-cbl-01826
FAX Flag = 'Y'?
Decision Rules
📊 Business Logic Narrative
When the process 'FAX Flag = 'Y'?' is invoked, and assuming that auto-fax is enabled and fax flag has been retrieved, when the fax flag equals 'y', the desired outcome is that the system enables auto-fax functionality and proceeds with fax routing configuration, otherwise it disables auto-fax.
💻 Technical Criteria
Given
Auto-FAX is enabled and FAX flag has been retrieved
When
The FAX flag equals 'Y'
Then
The system enables Auto-FAX functionality and proceeds with FAX routing configuration, otherwise it disables Auto-FAX
R-GCX146-cbl-01827
Set Auto-FAX Enabled
Action Rules
📊 Business Logic Narrative
When the process 'Set Auto-FAX Enabled' is invoked, and assuming that both auto-fax setting and fax flag are set to 'y', when the system processes the configuration, the desired outcome is that the system sets auto-fax as enabled and prepares for fax routing configuration.
💻 Technical Criteria
Given
Both Auto-FAX setting and FAX flag are set to 'Y'
When
The system processes the configuration
Then
The system sets Auto-FAX as enabled and prepares for FAX routing configuration
R-GCX146-cbl-01828
Configure FAX Routing with Copy IDs
Process Rules
📊 Business Logic Narrative
When the process 'Configure FAX Routing with Copy IDs' is invoked, and assuming that auto-fax functionality is enabled, when the system configures fax routing, the desired outcome is that the system sets up fax routing parameters with appropriate copy ids for message distribution.
💻 Technical Criteria
Given
Auto-FAX functionality is enabled
When
The system configures FAX routing
Then
The system sets up FAX routing parameters with appropriate copy IDs for message distribution
R-GCX146-cbl-01830
Auto-FAX Disabled - Use Standard Routing
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Auto-FAX Disabled - Use Standard Routing', assuming that either auto-fax setting is not 'y' or fax flag is not 'y', when auto-fax cannot be enabled, the desired outcome is that the system disables auto-fax functionality and uses standard routing procedures.
💻 Technical Criteria
EXCLUDING
Either Auto-FAX setting is not 'Y' or FAX flag is not 'Y'
When
Auto-FAX cannot be enabled
Then
The system disables Auto-FAX functionality and uses standard routing procedures
R-GCX146-cbl-01832
Initialize Line Counter WS-LINE-SUB = 1
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Line Counter WS-LINE-SUB = 1' is invoked, and assuming that email segmentation processing is starting, when the system begins processing email content, the desired outcome is that the line counter is set to 1 to begin tracking from the first line.
💻 Technical Criteria
Given
Email segmentation processing is starting
When
The system begins processing email content
Then
The line counter is set to 1 to begin tracking from the first line
R-GCX146-cbl-01834
Call X280-CALL-EMCSEND3 to Send Current Batch
Action Rules
📊 Business Logic Narrative
When the process 'Call X280-CALL-EMCSEND3 to Send Current Batch' is invoked, and assuming that an email segment has reached the maximum line limit of 699 lines, when the segment transmission is triggered, the desired outcome is that the emcsend3 service is invoked to send the current email batch.
💻 Technical Criteria
Given
An email segment has reached the maximum line limit of 699 lines
When
The segment transmission is triggered
Then
The EMCSEND3 service is invoked to send the current email batch
R-GCX146-cbl-01837
Reset Line Counter for Next Batch
Process Rules
📊 Business Logic Narrative
When the process 'Reset Line Counter for Next Batch' is invoked, and assuming that a continuation segment is being prepared with header added, when the system starts processing the next batch of lines, the desired outcome is that the line counter is reset to account for the continuation header and begin fresh counting.
💻 Technical Criteria
Given
A continuation segment is being prepared with header added
When
The system starts processing the next batch of lines
Then
The line counter is reset to account for the continuation header and begin fresh counting
R-GCX146-cbl-01840
Send Final Batch
Action Rules
📊 Business Logic Narrative
When the process 'Send Final Batch' is invoked, and assuming that all email content has been processed and no more lines remain, when the final segment is ready for transmission, the desired outcome is that the final email batch is sent containing the remaining content.
💻 Technical Criteria
Given
All email content has been processed and no more lines remain
When
The final segment is ready for transmission
Then
The final email batch is sent containing the remaining content
R-GCX146-cbl-01841
Set NO-MORE-EMAIL Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set NO-MORE-EMAIL Flag' is invoked, and assuming that all email segments have been processed and sent, when the final segment transmission is complete, the desired outcome is that the no-more-email flag is set to indicate processing completion.
💻 Technical Criteria
Given
All email segments have been processed and sent
When
The final segment transmission is complete
Then
The NO-MORE-EMAIL flag is set to indicate processing completion
R-GCX146-cbl-00936
CHNG Operation Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'CHNG Operation Successful?' is invoked, and assuming that cims chng operation is executed, when the system checks operation status, the desired outcome is that if chng operation is successful, proceed to message write operation, otherwise handle database operation error.
💻 Technical Criteria
Given
CIMS CHNG operation is executed
When
The system checks operation status
Then
If CHNG operation is successful, proceed to message write operation, otherwise handle database operation error
R-GCX146-cbl-00938
WRITMSGL Operation Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'WRITMSGL Operation Successful?' is invoked, and assuming that cims writmsgl operation is executed, when the system checks operation status, the desired outcome is that if writmsgl operation is successful, proceed to purge operation, otherwise handle database operation error.
💻 Technical Criteria
Given
CIMS WRITMSGL operation is executed
When
The system checks operation status
Then
If WRITMSGL operation is successful, proceed to purge operation, otherwise handle database operation error
R-GCX146-cbl-00939
Execute CIMS PURG Operation
Action Rules
📊 Business Logic Narrative
When the process 'Execute CIMS PURG Operation' is invoked, and assuming that writmsgl operation completed successfully, when the system executes cims purg operation, the desired outcome is that temporary message data is purged from the system.
💻 Technical Criteria
Given
WRITMSGL operation completed successfully
When
The system executes CIMS PURG operation
Then
Temporary message data is purged from the system
R-GCX146-cbl-00942
Handle Database Operation Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Database Operation Error' is invoked, and assuming that any database operation (chng, writmsgl, or purg) fails, when the system detects operation failure, the desired outcome is that database operation error is handled and process terminates with error status.
💻 Technical Criteria
Given
Any database operation (CHNG, WRITMSGL, or PURG) fails
When
The system detects operation failure
Then
Database operation error is handled and process terminates with error status
R-GCX146-cbl-00998
Create Continuation Message
Process Rules
📊 Business Logic Narrative
When the process 'Create Continuation Message' is invoked, and assuming that the current message has reached or exceeded 699 lines, when the system needs to add more lines, the desired outcome is that a new continuation message is created to handle additional lines.
💻 Technical Criteria
Given
The current message has reached or exceeded 699 lines
When
The system needs to add more lines
Then
A new continuation message is created to handle additional lines
R-GCX146-cbl-00999
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that a continuation message needs to be created, when the system resets the message buffer, the desired outcome is that the message buffer is cleared and line counter is reset to zero.
💻 Technical Criteria
Given
A continuation message needs to be created
When
The system resets the message buffer
Then
The message buffer is cleared and line counter is reset to zero
R-GCX146-cbl-01007
Finalize Current Message
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Current Message' is invoked, and assuming that all available lines have been processed or message is complete, when the system finalizes the current message, the desired outcome is that the message buffer is prepared for transmission with proper formatting and headers.
💻 Technical Criteria
Given
All available lines have been processed or message is complete
When
The system finalizes the current message
Then
The message buffer is prepared for transmission with proper formatting and headers
R-GCX146-cbl-01008
Send Message via Merlin
Action Rules
📊 Business Logic Narrative
When the process 'Send Message via Merlin' is invoked, and assuming that a message has been finalized and is ready for transmission, when the system sends the message via merlin, the desired outcome is that the message is transmitted through the merlin system to the intended recipients.
💻 Technical Criteria
Given
A message has been finalized and is ready for transmission
When
The system sends the message via Merlin
Then
The message is transmitted through the Merlin system to the intended recipients
R-GCX146-cbl-01057
Segment Message for Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Segment Message for Transmission' is invoked, and assuming that a message buffer that has exceeded size limits, when the system segments the message, the desired outcome is that current message content is prepared for transmission as a complete segment.
💻 Technical Criteria
Given
A message buffer that has exceeded size limits
When
The system segments the message
Then
Current message content is prepared for transmission as a complete segment
R-GCX146-cbl-01082
Secondary Broker Configured?
Decision Rules
📊 Business Logic Narrative
When the process 'Secondary Broker Configured?' is invoked, and assuming that primary broker notification has been processed, when the system checks for secondary broker configuration, the desired outcome is that if secondary broker exists then proceed with secondary broker notifications else complete broker notification process.
💻 Technical Criteria
Given
Primary broker notification has been processed
When
The system checks for secondary broker configuration
Then
IF secondary broker exists THEN proceed with secondary broker notifications ELSE complete broker notification process
R-GCX146-cbl-01083
Send X12 EDI to Secondary Broker via GCCS309C
Action Rules
📊 Business Logic Narrative
When the process 'Send X12 EDI to Secondary Broker via GCCS309C' is invoked, and assuming that secondary broker is configured and secondary broker communication preference is x12 edi, when the system processes secondary broker notification distribution, the desired outcome is that the system invokes gccs309c program to send x12 edi notification to the secondary broker.
💻 Technical Criteria
Given
Secondary broker is configured AND secondary broker communication preference is X12 EDI
When
The system processes secondary broker notification distribution
Then
The system invokes GCCS309C program to send X12 EDI notification to the secondary broker
R-GCX146-cbl-01084
Send Merlin to Secondary Broker via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin to Secondary Broker via GCX019' is invoked, and assuming that secondary broker is configured and secondary broker communication preference is merlin, when the system processes secondary broker notification distribution, the desired outcome is that the system invokes gcx019 program to send merlin notification to the secondary broker.
💻 Technical Criteria
Given
Secondary broker is configured AND secondary broker communication preference is Merlin
When
The system processes secondary broker notification distribution
Then
The system invokes GCX019 program to send Merlin notification to the secondary broker
R-GCX146-cbl-01085
Send Internet to Secondary Broker via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send Internet to Secondary Broker via GCX019' is invoked, and assuming that secondary broker is configured and secondary broker communication preference is internet, when the system processes secondary broker notification distribution, the desired outcome is that the system invokes gcx019 program to send internet notification to the secondary broker.
💻 Technical Criteria
Given
Secondary broker is configured AND secondary broker communication preference is Internet
When
The system processes secondary broker notification distribution
Then
The system invokes GCX019 program to send Internet notification to the secondary broker
R-GCX146-cbl-01086
Send FAX to Secondary Broker via GCX019
Action Rules
📊 Business Logic Narrative
When the process 'Send FAX to Secondary Broker via GCX019' is invoked, and assuming that secondary broker is configured and secondary broker communication preference is fax, when the system processes secondary broker notification distribution, the desired outcome is that the system invokes gcx019 program to send fax notification to the secondary broker.
💻 Technical Criteria
Given
Secondary broker is configured AND secondary broker communication preference is FAX
When
The system processes secondary broker notification distribution
Then
The system invokes GCX019 program to send FAX notification to the secondary broker
R-GCX146-cbl-01087
Send Paper to Secondary Broker via Batch Print
Action Rules
📊 Business Logic Narrative
When the process 'Send Paper to Secondary Broker via Batch Print' is invoked, and assuming that secondary broker is configured and secondary broker communication preference is paper, when the system processes secondary broker notification distribution, the desired outcome is that the system generates paper notification through batch print process for the secondary broker.
💻 Technical Criteria
Given
Secondary broker is configured AND secondary broker communication preference is Paper
When
The system processes secondary broker notification distribution
Then
The system generates paper notification through batch print process for the secondary broker
R-GCX146-cbl-01088
Broker Communication Preference Available?
Decision Rules
📊 Business Logic Narrative
When the process 'Broker Communication Preference Available?' is invoked, and assuming that a broker notification needs to be sent, when the system evaluates broker communication preferences, the desired outcome is that the system selects the appropriate channel (x12 edi, merlin, internet, fax, or paper) based on broker configuration.
💻 Technical Criteria
Given
A broker notification needs to be sent
When
The system evaluates broker communication preferences
Then
The system selects the appropriate channel (X12 EDI, Merlin, Internet, FAX, or Paper) based on broker configuration
R-GCX146-cbl-01124
Check Broker Preferences
Decision Rules
📊 Business Logic Narrative
When the process 'Check Broker Preferences' is invoked, and assuming that a broker notification needs to be sent and broker preferences are configured in the system, when the system checks the broker's communication channel preferences, the desired outcome is that the system identifies which channels (x12 edi, merlin, internet, fax, paper, email) are available for this broker.
💻 Technical Criteria
Given
A broker notification needs to be sent and broker preferences are configured in the system
When
The system checks the broker's communication channel preferences
Then
The system identifies which channels (X12 EDI, Merlin, Internet, FAX, Paper, Email) are available for this broker
R-GCX146-cbl-01125
X12 EDI Channel Available?
Validation Rules
📊 Business Logic Narrative
When the process 'X12 EDI Channel Available?' is invoked, and assuming that a broker notification is being processed, when the system checks if x12 edi channel is available for the broker, the desired outcome is that the system returns true if x12 edi is configured and available, otherwise false.
💻 Technical Criteria
Given
A broker notification is being processed
When
The system checks if X12 EDI channel is available for the broker
Then
The system returns true if X12 EDI is configured and available, otherwise false
R-GCX146-cbl-01126
Send X12 EDI Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send X12 EDI Notification' is invoked, and assuming that x12 edi channel is available for the broker, when the system processes the notification through x12 edi, the desired outcome is that the system invokes gccs309c module to send the x12 edi notification.
💻 Technical Criteria
Given
X12 EDI channel is available for the broker
When
The system processes the notification through X12 EDI
Then
The system invokes GCCS309C module to send the X12 EDI notification
R-GCX146-cbl-01127
Merlin Channel Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Merlin Channel Available?' is invoked, and assuming that a broker notification is being processed, when the system checks if merlin channel is available for the broker, the desired outcome is that the system returns true if merlin is configured and available, otherwise false.
💻 Technical Criteria
Given
A broker notification is being processed
When
The system checks if Merlin channel is available for the broker
Then
The system returns true if Merlin is configured and available, otherwise false
R-GCX146-cbl-01128
Send Merlin Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Merlin Notification' is invoked, and assuming that merlin channel is available for the broker, when the system processes the notification through merlin, the desired outcome is that the system invokes gcx019 module to send the merlin notification.
💻 Technical Criteria
Given
Merlin channel is available for the broker
When
The system processes the notification through Merlin
Then
The system invokes GCX019 module to send the Merlin notification
R-GCX146-cbl-01129
Internet Channel Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Internet Channel Available?' is invoked, and assuming that a broker notification is being processed, when the system checks if internet channel is available for the broker, the desired outcome is that the system returns true if internet is configured and available, otherwise false.
💻 Technical Criteria
Given
A broker notification is being processed
When
The system checks if Internet channel is available for the broker
Then
The system returns true if Internet is configured and available, otherwise false
R-GCX146-cbl-01130
Send Internet Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send Internet Notification' is invoked, and assuming that internet channel is available for the broker, when the system processes the notification through internet, the desired outcome is that the system invokes gcx019 module to send the internet notification.
💻 Technical Criteria
Given
Internet channel is available for the broker
When
The system processes the notification through Internet
Then
The system invokes GCX019 module to send the Internet notification
R-GCX146-cbl-01131
FAX Channel Available?
Validation Rules
📊 Business Logic Narrative
When the process 'FAX Channel Available?' is invoked, and assuming that a broker notification is being processed, when the system checks if fax channel is available for the broker, the desired outcome is that the system returns true if fax is configured and available, otherwise false.
💻 Technical Criteria
Given
A broker notification is being processed
When
The system checks if FAX channel is available for the broker
Then
The system returns true if FAX is configured and available, otherwise false
R-GCX146-cbl-01132
Send FAX Notification
Action Rules
📊 Business Logic Narrative
When the process 'Send FAX Notification' is invoked, and assuming that fax channel is available for the broker, when the system processes the notification through fax, the desired outcome is that the system invokes gcx019 module to send the fax notification.
💻 Technical Criteria
Given
FAX channel is available for the broker
When
The system processes the notification through FAX
Then
The system invokes GCX019 module to send the FAX notification
R-GCX146-cbl-01133
Auto-FAX Enabled?
Validation Rules
📊 Business Logic Narrative
When the process 'Auto-FAX Enabled?' is invoked, and assuming that fax notification has been processed, when the system checks the auto-fax configuration setting, the desired outcome is that the system returns true if auto-fax is enabled, otherwise continues to next channel.
💻 Technical Criteria
Given
FAX notification has been processed
When
The system checks the auto-FAX configuration setting
Then
The system returns true if auto-FAX is enabled, otherwise continues to next channel
R-GCX146-cbl-01134
Setup FAX Routing
Process Rules
📊 Business Logic Narrative
When the process 'Setup FAX Routing' is invoked, and assuming that auto-fax is enabled in system configuration, when the system sets up fax routing, the desired outcome is that the system configures fax routing parameters and copy ids for automatic transmission.
💻 Technical Criteria
Given
Auto-FAX is enabled in system configuration
When
The system sets up FAX routing
Then
The system configures FAX routing parameters and copy IDs for automatic transmission
R-GCX146-cbl-01135
Send via FAX with Copy IDs
Action Rules
📊 Business Logic Narrative
When the process 'Send via FAX with Copy IDs' is invoked, and assuming that fax routing is configured with copy ids, when the system processes auto-fax transmission, the desired outcome is that the system invokes emcsend module to send fax with copy ids.
💻 Technical Criteria
Given
FAX routing is configured with copy IDs
When
The system processes auto-FAX transmission
Then
The system invokes EMCSEND module to send FAX with copy IDs
R-GCX146-cbl-01136
Paper Channel Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Paper Channel Available?' is invoked, and assuming that a broker notification is being processed, when the system checks if paper channel is available for the broker, the desired outcome is that the system returns true if paper is configured and available, otherwise false.
💻 Technical Criteria
Given
A broker notification is being processed
When
The system checks if Paper channel is available for the broker
Then
The system returns true if Paper is configured and available, otherwise false
R-GCX146-cbl-01137
Generate Paper Notification
Action Rules
📊 Business Logic Narrative
When the process 'Generate Paper Notification' is invoked, and assuming that paper channel is available for the broker, when the system processes the notification for paper output, the desired outcome is that the system generates paper notification using batch print call letters.
💻 Technical Criteria
Given
Paper channel is available for the broker
When
The system processes the notification for paper output
Then
The system generates paper notification using batch print call letters
R-GCX146-cbl-01138
Email Channel Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Channel Available?' is invoked, and assuming that a broker notification is being processed, when the system checks if email channel is available for the broker, the desired outcome is that the system returns true if email is configured and available, otherwise false.
💻 Technical Criteria
Given
A broker notification is being processed
When
The system checks if Email channel is available for the broker
Then
The system returns true if Email is configured and available, otherwise false
R-GCX146-cbl-01148
Email Send Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Email Send Successful?' is invoked, and assuming that an email message has been sent via the primary email system, when the system receives the email send response, the desired outcome is that if the email send is successful, complete the distribution process, otherwise activate fallback email recipients.
💻 Technical Criteria
Given
An email message has been sent via the primary email system
When
The system receives the email send response
Then
If the email send is successful, complete the distribution process, otherwise activate fallback email recipients
R-GCX146-cbl-01159
Retrieve Existing Train Record
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Existing Train Record' is invoked, and assuming that a train id is provided for processing, when the system attempts to retrieve the existing train record from the gcsb4rt database, the desired outcome is that the system should successfully locate and retrieve the train record if it exists, or return a not found status if no record exists.
💻 Technical Criteria
Given
A train ID is provided for processing
When
The system attempts to retrieve the existing train record from the GCSB4RT database
Then
The system should successfully locate and retrieve the train record if it exists, or return a not found status if no record exists
R-GCX146-cbl-01160
Train Record Exists?
Decision Rules
📊 Business Logic Narrative
When the process 'Train Record Exists?' is invoked, and assuming that a database retrieval operation has been performed for a train record, when the system evaluates the retrieval result status, the desired outcome is that if the train record exists, proceed to delete the existing record; if no train record exists, proceed directly to insert new record.
💻 Technical Criteria
Given
A database retrieval operation has been performed for a train record
When
The system evaluates the retrieval result status
Then
If the train record exists, proceed to delete the existing record; if no train record exists, proceed directly to insert new record
R-GCX146-cbl-01161
Delete Existing Train Record
Action Rules
📊 Business Logic Narrative
When the process 'Delete Existing Train Record' is invoked, and assuming that an existing train record has been found in the gcsb4rt database, when the system performs a delete operation on the existing train record, the desired outcome is that the existing train record should be successfully removed from the database to prepare for the new record insertion.
💻 Technical Criteria
Given
An existing train record has been found in the GCSB4RT database
When
The system performs a delete operation on the existing train record
Then
The existing train record should be successfully removed from the database to prepare for the new record insertion
R-GCX146-cbl-01165
Train Record Operations Complete
Process Rules
📊 Business Logic Narrative
When the process 'Train Record Operations Complete' is invoked, and assuming that all required database operations for train record processing have been performed, when the new train record has been successfully inserted into the database, the desired outcome is that the train record operations should be marked as complete and processing can continue to next step.
💻 Technical Criteria
Given
All required database operations for train record processing have been performed
When
The new train record has been successfully inserted into the database
Then
The train record operations should be marked as complete and processing can continue to next step
🚂 Equipment & Cargo Specs
624 logic blocks
R-GCX146-cbl-00010
10:Equipment Data Extraction
Validation Rules
📊 Business Logic Narrative
When the process '10:Equipment Data Extraction' is invoked, and assuming that a train manifest contains a list of equipment, when the system validates the equipment list, the desired outcome is that the equipment list must contain at least one entry (error 34 if none) and no more than 500 entries (error 28 if exceeded).
💻 Technical Criteria
Given
A train manifest contains a list of equipment
When
The system validates the equipment list
Then
The equipment list must contain at least one entry (error 34 if none) and no more than 500 entries (error 28 if exceeded)
R-GCX146-cbl-00013
12:Equipment Type Classification
Definitional Rules
📊 Business Logic Narrative
When the process '12:Equipment Type Classification' is invoked, and assuming that equipment information is available for classification, when the system determines equipment type, the desired outcome is that equipment is classified as unit (l,p,d,u), van (v), sbu, etu (e), or regular car based on equipment type codes.
💻 Technical Criteria
Given
Equipment information is available for classification
When
The system determines equipment type
Then
Equipment is classified as Unit (L,P,D,U), Van (V), SBU, ETU (E), or regular car based on equipment type codes
R-GCX146-cbl-00020
21:Equipment Status Totals Compilation
Computation Rules
📊 Business Logic Narrative
When the process '21:Equipment Status Totals Compilation' is invoked, and assuming that equipment has been processed and status determined, when the system compiles status totals, the desired outcome is that total-release counts equipment with 'release' or 'csa-dlv' status; total-haulage counts equipment with haulage rights; total-proceed counts equipment in transit between different stations; total-held-ccra counts equipment with 'hold' or 'agi-hold' status; total-held-docs counts equipment at same station with no broker entry.
💻 Technical Criteria
Given
Equipment has been processed and status determined
When
The system compiles status totals
Then
TOTAL-RELEASE counts equipment with 'RELEASE' or 'CSA-DLV' status; TOTAL-HAULAGE counts equipment with haulage rights; TOTAL-PROCEED counts equipment in transit between different stations; TOTAL-HELD-CCRA counts equipment with 'HOLD' or 'AGI-HOLD' status; TOTAL-HELD-DOCS counts equipment at same station with no broker entry
R-GCX146-cbl-00021
22:EDI Transmission Processing
Action Rules
📊 Business Logic Narrative
When the process '22:EDI Transmission Processing' is invoked, and assuming that train manifest data has been validated and processed, when the system transmits edi transactions, the desired outcome is that edi transactions are sent to appropriate trading partners and customs authorities with train and equipment information.
💻 Technical Criteria
Given
Train manifest data has been validated and processed
When
The system transmits EDI transactions
Then
EDI transactions are sent to appropriate trading partners and customs authorities with train and equipment information
R-GCX146-cbl-00025
26:Status Report Generation
Action Rules
📊 Business Logic Narrative
When the process '26:Status Report Generation' is invoked, and assuming that verify operation is requested for train manifest, when the system generates status reports, the desired outcome is that status report includes equipment totals by category, detailed status information, transit status indicators, and up to 90 lines of us status messages.
💻 Technical Criteria
Given
VERIFY operation is requested for train manifest
When
The system generates status reports
Then
Status report includes equipment totals by category, detailed status information, transit status indicators, and up to 90 lines of US status messages
R-GCX146-cbl-00028
29:US Trip Sheet Generation
Action Rules
📊 Business Logic Narrative
When the process '29:US Trip Sheet Generation' is invoked, and assuming that us-bound cargo requires trip sheet documentation, when the system generates us trip sheets, the desired outcome is that trip sheets include equipment type descriptions, status mappings (release with export transit becomes 'export', transit status 't' becomes 'transit', return status 'r' becomes 'return'), and are distributed to us merlin users.
💻 Technical Criteria
Given
US-bound cargo requires trip sheet documentation
When
The system generates US trip sheets
Then
Trip sheets include equipment type descriptions, status mappings (RELEASE with export transit becomes 'EXPORT', transit status 'T' becomes 'TRANSIT', return status 'R' becomes 'RETURN'), and are distributed to US Merlin users
R-GCX146-cbl-00029
30:Cargo Arrival Detection
Decision Rules
📊 Business Logic Narrative
When the process '30:Cargo Arrival Detection' is invoked, and assuming that train manifest contains cargo with destination information, when the system detects cargo arrivals, the desired outcome is that cargo is identified as arriving when manifest destination codes match station codes; only non-ocean manifest cargo is processed for arrival notifications.
💻 Technical Criteria
Given
Train manifest contains cargo with destination information
When
The system detects cargo arrivals
Then
Cargo is identified as arriving when manifest destination codes match station codes; only non-ocean manifest cargo is processed for arrival notifications
R-GCX146-cbl-00030
31:Cargo Arrival Notification
Action Rules
📊 Business Logic Narrative
When the process '31:Cargo Arrival Notification' is invoked, and assuming that arriving cargo has been detected at destination stations, when the system processes arrival notifications, the desired outcome is that arrival notices are created and sent to customs processing systems via gct1481e transactions for appropriate handling.
💻 Technical Criteria
Given
Arriving cargo has been detected at destination stations
When
The system processes arrival notifications
Then
Arrival notices are created and sent to customs processing systems via GCT1481E transactions for appropriate handling
R-GCX146-cbl-00033
34:US Customs Status Processing
Process Rules
📊 Business Logic Narrative
When the process '34:US Customs Status Processing' is invoked, and assuming that equipment has us customs records requiring status processing, when the system processes us customs status, the desired outcome is that bond types (it, tr, mt, te) are validated; warnings are generated for it bond types, train vessel mismatches, in-transit location mismatches, and tib date issues; arrival keys are tracked for specific bond types during add operations.
💻 Technical Criteria
Given
Equipment has US customs records requiring status processing
When
The system processes US customs status
Then
Bond types (IT, TR, MT, TE) are validated; warnings are generated for IT bond types, train vessel mismatches, in-transit location mismatches, and TIB date issues; arrival keys are tracked for specific bond types during ADD operations
R-GCX146-cbl-00041
Set Return Code to Stop Processing
Process Rules
📊 Business Logic Narrative
When the process 'Set Return Code to Stop Processing' is invoked, and assuming that no message is available in the queue, when the system determines the queue is empty, the desired outcome is that the return code is set to non-zero to signal termination of the message retrieval loop.
💻 Technical Criteria
Given
No message is available in the queue
When
The system determines the queue is empty
Then
The return code is set to non-zero to signal termination of the message retrieval loop
R-GCX146-cbl-00043
End Message Retrieval Loop
Process Rules
📊 Business Logic Narrative
When the process 'End Message Retrieval Loop' is invoked, and assuming that the message queue is empty or no more messages are available, when the return code indicates processing should stop, the desired outcome is that the message retrieval loop is terminated and the system exits the input processing phase.
💻 Technical Criteria
Given
The message queue is empty or no more messages are available
When
The return code indicates processing should stop
Then
The message retrieval loop is terminated and the system exits the input processing phase
R-GCX146-cbl-00056
Set AEI-TRAIN-SEND Flag for ADD
Process Rules
📊 Business Logic Narrative
When the process 'Set AEI-TRAIN-SEND Flag for ADD' is invoked, and assuming that the request type has been validated as add, when processing flags need to be established, the desired outcome is that the system sets the aei-train-send flag to enable automatic equipment identification processing.
💻 Technical Criteria
Given
The request type has been validated as ADD
When
Processing flags need to be established
Then
The system sets the AEI-TRAIN-SEND flag to enable automatic equipment identification processing
R-GCX146-cbl-00057
Set AEI-TRAIN-SEND Flag for VERIFY
Process Rules
📊 Business Logic Narrative
When the process 'Set AEI-TRAIN-SEND Flag for VERIFY' is invoked, and assuming that the request type has been validated as verify, when processing flags need to be established, the desired outcome is that the system sets the aei-train-send flag to enable automatic equipment identification processing.
💻 Technical Criteria
Given
The request type has been validated as VERIFY
When
Processing flags need to be established
Then
The system sets the AEI-TRAIN-SEND flag to enable automatic equipment identification processing
R-GCX146-cbl-00058
Set AEI-TRAIN-SEND Flag for NOTIFY
Process Rules
📊 Business Logic Narrative
When the process 'Set AEI-TRAIN-SEND Flag for NOTIFY' is invoked, and assuming that the request type has been validated as notify, when processing flags need to be established, the desired outcome is that the system sets the aei-train-send flag to enable automatic equipment identification processing.
💻 Technical Criteria
Given
The request type has been validated as NOTIFY
When
Processing flags need to be established
Then
The system sets the AEI-TRAIN-SEND flag to enable automatic equipment identification processing
R-GCX146-cbl-00103
Retrieve Existing Train Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Existing Train Record' is invoked, and assuming that a train record exists in the database, when the system accesses the train record, the desired outcome is that the complete train record details are retrieved including status and equipment information.
💻 Technical Criteria
Given
A train record exists in the database
When
The system accesses the train record
Then
The complete train record details are retrieved including status and equipment information
R-GCX146-cbl-00109
Insert Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Insert Equipment Details' is invoked, and assuming that a new train record has been created, when the system processes equipment details for the train, the desired outcome is that all equipment information is inserted and associated with the train record.
💻 Technical Criteria
Given
A new train record has been created
When
The system processes equipment details for the train
Then
All equipment information is inserted and associated with the train record
R-GCX146-cbl-00110
Insert Successful?
Validation Rules
📊 Business Logic Narrative
When the process 'Insert Successful?' is invoked, and assuming that equipment details insertion has been attempted, when the system checks the insertion result, the desired outcome is that the system confirms whether the equipment insertion was successful or failed.
💻 Technical Criteria
Given
Equipment details insertion has been attempted
When
The system checks the insertion result
Then
The system confirms whether the equipment insertion was successful or failed
R-GCX146-cbl-00113
Extract Equipment ID from Consist Data
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from Consist Data' is invoked, and assuming that consist data contains equipment information with car id and position details, when processing equipment data from consist input, the desired outcome is that equipment id is extracted and stored for further processing.
💻 Technical Criteria
Given
Consist data contains equipment information with car ID and position details
When
Processing equipment data from consist input
Then
Equipment ID is extracted and stored for further processing
R-GCX146-cbl-00114
Format Equipment Car ID
Action Rules
📊 Business Logic Narrative
When the process 'Format Equipment Car ID' is invoked, and assuming that raw equipment id from consist data, when equipment id needs to be formatted for system use, the desired outcome is that equipment id is formatted using gcccarfm utility to 12-character standard format.
💻 Technical Criteria
Given
Raw equipment ID from consist data
When
Equipment ID needs to be formatted for system use
Then
Equipment ID is formatted using GCCCARFM utility to 12-character standard format
R-GCX146-cbl-00115
Determine Equipment Type
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Equipment Type' is invoked, and assuming that equipment data with type indicators and characteristics, when equipment type needs to be determined, the desired outcome is that equipment is classified as unit (l,p,d,u), van (v), sbu (s), etu (e), or regular car based on type code.
💻 Technical Criteria
Given
Equipment data with type indicators and characteristics
When
Equipment type needs to be determined
Then
Equipment is classified as Unit (L,P,D,U), Van (V), SBU (S), ETU (E), or regular car based on type code
R-GCX146-cbl-00117
Trailer Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Trailer Equipment' is invoked, and assuming that equipment identified as trailer type, when processing trailer equipment, the desired outcome is that trailer is processed with standard equipment handling procedures.
💻 Technical Criteria
Given
Equipment identified as trailer type
When
Processing trailer equipment
Then
Trailer is processed with standard equipment handling procedures
R-GCX146-cbl-00118
Rail Car Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Rail Car Equipment' is invoked, and assuming that equipment identified as standard rail car, when processing rail car equipment, the desired outcome is that rail car is processed through standard equipment handling workflow.
💻 Technical Criteria
Given
Equipment identified as standard rail car
When
Processing rail car equipment
Then
Rail car is processed through standard equipment handling workflow
R-GCX146-cbl-00119
Extract Load/Empty Status from Input
Definitional Rules
📊 Business Logic Narrative
When the process 'Extract Load/Empty Status from Input' is invoked, and assuming that consist input data contains load/empty status indicator, when processing equipment status information, the desired outcome is that load/empty status is extracted and stored as 'l' for loaded or 'e' for empty.
💻 Technical Criteria
Given
Consist input data contains load/empty status indicator
When
Processing equipment status information
Then
Load/empty status is extracted and stored as 'L' for loaded or 'E' for empty
R-GCX146-cbl-00122
Set Empty Status Flag
Decision Rules
📊 Business Logic Narrative
When the process 'Set Empty Status Flag' is invoked, and assuming that equipment status validation confirms empty condition or detects loaded car marked as empty, when status inconsistency is detected or equipment is confirmed empty, the desired outcome is that empty status flag is set to indicate empty equipment.
💻 Technical Criteria
Given
Equipment status validation confirms empty condition or detects loaded car marked as empty
When
Status inconsistency is detected or equipment is confirmed empty
Then
Empty status flag is set to indicate empty equipment
R-GCX146-cbl-00125
Add to Equipment List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Equipment List' is invoked, and assuming that complete equipment record has been built, when adding equipment to train consist list, the desired outcome is that equipment record is added to the equipment list and equipment counter is incremented.
💻 Technical Criteria
Given
Complete equipment record has been built
When
Adding equipment to train consist list
Then
Equipment record is added to the equipment list and equipment counter is incremented
R-GCX146-cbl-00126
More Equipment in Consist?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment in Consist?' is invoked, and assuming that current equipment has been processed and added to equipment list, when checking for additional equipment in consist, the desired outcome is that if more equipment exists in consist, processing continues with next equipment item, otherwise equipment extraction is completed.
💻 Technical Criteria
Given
Current equipment has been processed and added to equipment list
When
Checking for additional equipment in consist
Then
If more equipment exists in consist, processing continues with next equipment item, otherwise equipment extraction is completed
R-GCX146-cbl-00127
Equipment Extraction Complete
Process Rules
📊 Business Logic Narrative
When the process 'Equipment Extraction Complete' is invoked, and assuming that all equipment in consist has been processed and added to equipment list, when no more equipment remains in consist, the desired outcome is that equipment extraction process is completed and control returns to main processing flow.
💻 Technical Criteria
Given
All equipment in consist has been processed and added to equipment list
When
No more equipment remains in consist
Then
Equipment extraction process is completed and control returns to main processing flow
R-GCX146-cbl-01422
Check Equipment ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Check Equipment ID Format' is invoked, and assuming that an equipment id is received from the input message, when the system checks the equipment id format for valid characters, the desired outcome is that the equipment id should contain only alphanumeric characters and be properly formatted.
💻 Technical Criteria
Given
An equipment ID is received from the input message
When
The system checks the equipment ID format for valid characters
Then
The equipment ID should contain only alphanumeric characters and be properly formatted
R-GCX146-cbl-01423
Validate Equipment ID Length
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID Length' is invoked, and assuming that an equipment id has been formatted and cleaned, when the system validates the equipment id length, the desired outcome is that the equipment id length should be within acceptable limits for database operations.
💻 Technical Criteria
Given
An equipment ID has been formatted and cleaned
When
The system validates the equipment ID length
Then
The equipment ID length should be within acceptable limits for database operations
R-GCX146-cbl-01424
Apply Padding Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Padding Rules' is invoked, and assuming that an equipment id has passed initial format validation, when the system applies padding rules to the equipment id, the desired outcome is that the equipment id should be padded with appropriate characters to meet standard length requirements.
💻 Technical Criteria
Given
An equipment ID has passed initial format validation
When
The system applies padding rules to the equipment ID
Then
The equipment ID should be padded with appropriate characters to meet standard length requirements
R-GCX146-cbl-01425
Remove Spaces and Special Characters
Process Rules
📊 Business Logic Narrative
When the process 'Remove Spaces and Special Characters' is invoked, and assuming that an equipment id contains spaces or special characters, when the system processes the equipment id for cleanup, the desired outcome is that all spaces and invalid special characters should be removed from the equipment id.
💻 Technical Criteria
Given
An equipment ID contains spaces or special characters
When
The system processes the equipment ID for cleanup
Then
All spaces and invalid special characters should be removed from the equipment ID
R-GCX146-cbl-01426
Format for Database Search
Process Rules
📊 Business Logic Narrative
When the process 'Format for Database Search' is invoked, and assuming that an equipment id has been validated and cleaned, when the system formats the equipment id for database operations, the desired outcome is that the equipment id should be formatted according to database search requirements.
💻 Technical Criteria
Given
An equipment ID has been validated and cleaned
When
The system formats the equipment ID for database operations
Then
The equipment ID should be formatted according to database search requirements
R-GCX146-cbl-01427
Compress Equipment ID
Process Rules
📊 Business Logic Narrative
When the process 'Compress Equipment ID' is invoked, and assuming that an equipment id has been formatted for database use, when the system compresses the equipment id, the desired outcome is that the equipment id should be compressed while maintaining its integrity and searchability.
💻 Technical Criteria
Given
An equipment ID has been formatted for database use
When
The system compresses the equipment ID
Then
The equipment ID should be compressed while maintaining its integrity and searchability
R-GCX146-cbl-01428
Organize Numeric Sequences
Process Rules
📊 Business Logic Narrative
When the process 'Organize Numeric Sequences' is invoked, and assuming that an equipment id contains numeric sequences, when the system organizes the numeric portions, the desired outcome is that numeric sequences should be properly aligned and formatted for consistent processing.
💻 Technical Criteria
Given
An equipment ID contains numeric sequences
When
The system organizes the numeric portions
Then
Numeric sequences should be properly aligned and formatted for consistent processing
R-GCX146-cbl-01429
Generate Format Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Format Error', assuming that an equipment id fails format validation, when the system detects invalid format, the desired outcome is that a format error should be generated indicating the equipment id does not meet format requirements.
💻 Technical Criteria
EXCLUDING
An equipment ID fails format validation
When
The system detects invalid format
Then
A format error should be generated indicating the equipment ID does not meet format requirements
R-GCX146-cbl-01430
Generate Length Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Length Error', assuming that an equipment id fails length validation, when the system detects invalid length, the desired outcome is that a length error should be generated indicating the equipment id does not meet length requirements.
💻 Technical Criteria
EXCLUDING
An equipment ID fails length validation
When
The system detects invalid length
Then
A length error should be generated indicating the equipment ID does not meet length requirements
R-GCX146-cbl-01184
Add Additional Search Criteria
Process Rules
📊 Business Logic Narrative
When the process 'Add Additional Search Criteria' is invoked, and assuming that primary search key is established with equipment id, when the system adds additional search criteria, the desired outcome is that supplementary search parameters are configured to improve search effectiveness.
💻 Technical Criteria
Given
Primary search key is established with equipment ID
When
The system adds additional search criteria
Then
Supplementary search parameters are configured to improve search effectiveness
R-GCX146-cbl-01431
Initialize Search Parameters
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Search Parameters' is invoked, and assuming that a search operation is being initiated for equipment lookup, when the system begins parameter configuration, the desired outcome is that all search parameter fields are cleared and set to initial default values.
💻 Technical Criteria
Given
A search operation is being initiated for equipment lookup
When
The system begins parameter configuration
Then
All search parameter fields are cleared and set to initial default values
R-GCX146-cbl-01432
Set Equipment Type Criteria
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Equipment Type Criteria' is invoked, and assuming that equipment search parameters are being configured, when equipment type criteria needs to be established, the desired outcome is that car type code and equipment category are set based on the search requirements.
💻 Technical Criteria
Given
Equipment search parameters are being configured
When
Equipment type criteria needs to be established
Then
Car type code and equipment category are set based on the search requirements
R-GCX146-cbl-01434
Set Station Code Filters
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Station Code Filters' is invoked, and assuming that equipment search requires geographic filtering, when station code filters are being configured, the desired outcome is that origin station code and destination station code are set to limit search to specific locations.
💻 Technical Criteria
Given
Equipment search requires geographic filtering
When
Station code filters are being configured
Then
Origin station code and destination station code are set to limit search to specific locations
R-GCX146-cbl-01437
Set Equipment ID Criteria
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Equipment ID Criteria' is invoked, and assuming that search targets specific equipment pieces, when equipment id criteria are being set, the desired outcome is that equipment id format and car number parameters are configured for precise equipment identification.
💻 Technical Criteria
Given
Search targets specific equipment pieces
When
Equipment ID criteria are being set
Then
Equipment ID format and car number parameters are configured for precise equipment identification
R-GCX146-cbl-01439
Execute Enhanced Search with FWCARGET
Action Rules
📊 Business Logic Narrative
When the process 'Execute Enhanced Search with FWCARGET' is invoked, and assuming that search parameters are validated and confirmed as compatible, when enhanced search execution is initiated, the desired outcome is that fwcarget service is called with all configured search parameters to retrieve equipment records.
💻 Technical Criteria
Given
Search parameters are validated and confirmed as compatible
When
Enhanced search execution is initiated
Then
FWCARGET service is called with all configured search parameters to retrieve equipment records
R-GCX146-cbl-01712
Extract Equipment ID from Input
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment ID from Input' is invoked, and assuming that an input message containing equipment information is received, when the system processes the equipment data from the input message, the desired outcome is that the equipment id is extracted from the input message and made available for further processing.
💻 Technical Criteria
Given
An input message containing equipment information is received
When
The system processes the equipment data from the input message
Then
The equipment ID is extracted from the input message and made available for further processing
R-GCX146-cbl-01713
Format Equipment ID for Database Search
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment ID for Database Search' is invoked, and assuming that an equipment id has been extracted from the input message, when the system needs to prepare database search keys, the desired outcome is that the equipment id is formatted and assigned to search key fields for fwiiroot, shiproot, and inquiry database lookups.
💻 Technical Criteria
Given
An equipment ID has been extracted from the input message
When
The system needs to prepare database search keys
Then
The equipment ID is formatted and assigned to search key fields for FWIIROOT, SHIPROOT, and inquiry database lookups
R-GCX146-cbl-01714
Validate Equipment ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Equipment ID Format' is invoked, and assuming that an equipment id has been extracted and formatted, when the system validates the equipment id format, the desired outcome is that if the equipment id format is valid, processing continues; if invalid, an error condition is set.
💻 Technical Criteria
Given
An equipment ID has been extracted and formatted
When
The system validates the equipment ID format
Then
If the equipment ID format is valid, processing continues; if invalid, an error condition is set
R-GCX146-cbl-01716
Set Search Key for SHIPROOT Lookup
Process Rules
📊 Business Logic Narrative
When the process 'Set Search Key for SHIPROOT Lookup' is invoked, and assuming that a valid equipment id is available for database search, when the system prepares to search the shiproot database, the desired outcome is that the equipment id is set as the search key for the shipment root database lookup.
💻 Technical Criteria
Given
A valid equipment ID is available for database search
When
The system prepares to search the SHIPROOT database
Then
The equipment ID is set as the search key for the shipment root database lookup
R-GCX146-cbl-01717
Set Search Key for Inquiry Database
Process Rules
📊 Business Logic Narrative
When the process 'Set Search Key for Inquiry Database' is invoked, and assuming that a valid equipment id is available for database search, when the system prepares to search the inquiry database, the desired outcome is that the equipment id is set as the search key for the inquiry database lookup.
💻 Technical Criteria
Given
A valid equipment ID is available for database search
When
The system prepares to search the inquiry database
Then
The equipment ID is set as the search key for the inquiry database lookup
R-GCX146-cbl-01194
Search FW-IQ Database by Equipment ID
Action Rules
📊 Business Logic Narrative
When the process 'Search FW-IQ Database by Equipment ID' is invoked, and assuming that fw-iq inquiry search is initialized with valid equipment id, when the system performs database lookup in fw-iq using equipment identifier, the desired outcome is that database search is executed and inquiry record status is determined.
💻 Technical Criteria
Given
FW-IQ inquiry search is initialized with valid equipment ID
When
The system performs database lookup in FW-IQ using equipment identifier
Then
Database search is executed and inquiry record status is determined
R-GCX146-cbl-01200
Get Container Information if Flat Car
Decision Rules
📊 Business Logic Narrative
When the process 'Get Container Information if Flat Car' is invoked, and assuming that equipment details have been extracted from inquiry record, when the system evaluates if equipment is a flat car type that may carry containers, the desired outcome is that if equipment is flat car, initiate container information lookup; otherwise continue with standard equipment processing.
💻 Technical Criteria
Given
Equipment details have been extracted from inquiry record
When
The system evaluates if equipment is a flat car type that may carry containers
Then
If equipment is flat car, initiate container information lookup; otherwise continue with standard equipment processing
R-GCX146-cbl-01201
Container Records Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Records Available?' is invoked, and assuming that equipment has been identified as flat car requiring container processing, when the system searches for associated container records, the desired outcome is that if container records are available, proceed with container processing; otherwise continue with equipment processing.
💻 Technical Criteria
Given
Equipment has been identified as flat car requiring container processing
When
The system searches for associated container records
Then
If container records are available, proceed with container processing; otherwise continue with equipment processing
R-GCX146-cbl-01202
Process Container Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Process Container Sequence' is invoked, and assuming that container records are available for flat car equipment, when the system processes container sequence information, the desired outcome is that each container in sequence is identified and prepared for detailed processing.
💻 Technical Criteria
Given
Container records are available for flat car equipment
When
The system processes container sequence information
Then
Each container in sequence is identified and prepared for detailed processing
R-GCX146-cbl-01203
Extract Container IDs from T/C XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container IDs from T/C XREF' is invoked, and assuming that container sequence processing is active for flat car, when the system accesses trailer/container cross-reference (t/c xref) data, the desired outcome is that container ids are extracted and validated for each container associated with the flat car.
💻 Technical Criteria
Given
Container sequence processing is active for flat car
When
The system accesses trailer/container cross-reference (T/C XREF) data
Then
Container IDs are extracted and validated for each container associated with the flat car
R-GCX146-cbl-01204
Set Container Processing Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set Container Processing Flags' is invoked, and assuming that container ids have been successfully extracted from cross-reference data, when the system sets container processing indicators, the desired outcome is that container processing flags are activated to enable proper handling of containerized cargo.
💻 Technical Criteria
Given
Container IDs have been successfully extracted from cross-reference data
When
The system sets container processing indicators
Then
Container processing flags are activated to enable proper handling of containerized cargo
R-GCX146-cbl-01441
Search for T/C XREF Records
Process Rules
📊 Business Logic Narrative
When the process 'Search for T/C XREF Records' is invoked, and assuming that a flat car equipment record exists in the system, when the system processes the flat car for container identification, the desired outcome is that the system searches the fw-iq inquiry database for t/c xref records matching the flat car.
💻 Technical Criteria
Given
A flat car equipment record exists in the system
When
The system processes the flat car for container identification
Then
The system searches the FW-IQ inquiry database for T/C XREF records matching the flat car
R-GCX146-cbl-01442
XREF Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'XREF Record Found?' is invoked, and assuming that the system has searched for t/c xref records for a flat car, when the search is completed, the desired outcome is that the system determines if any cross-reference records were found and proceeds with container processing if found, or handles the no-record scenario if not found.
💻 Technical Criteria
Given
The system has searched for T/C XREF records for a flat car
When
The search is completed
Then
The system determines if any cross-reference records were found and proceeds with container processing if found, or handles the no-record scenario if not found
R-GCX146-cbl-01443
Extract Container ID from XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from XREF' is invoked, and assuming that valid t/c xref records exist for a flat car, when the system processes each cross-reference record, the desired outcome is that the system extracts the container id from each xref record for further validation and processing.
💻 Technical Criteria
Given
Valid T/C XREF records exist for a flat car
When
The system processes each cross-reference record
Then
The system extracts the container ID from each XREF record for further validation and processing
R-GCX146-cbl-01444
Validate Container ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Container ID Format' is invoked, and assuming that a container id has been extracted from a cross-reference record, when the system validates the container id format, the desired outcome is that the system verifies the container id meets format requirements and is valid for processing.
💻 Technical Criteria
Given
A container ID has been extracted from a cross-reference record
When
The system validates the container ID format
Then
The system verifies the container ID meets format requirements and is valid for processing
R-GCX146-cbl-01445
Container ID Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Container ID Valid?' is invoked, and assuming that a container id has undergone format validation, when the validation process is complete, the desired outcome is that the system determines if the container id is valid and proceeds with sequence assignment if valid, or handles the invalid id error if not valid.
💻 Technical Criteria
Given
A container ID has undergone format validation
When
The validation process is complete
Then
The system determines if the container ID is valid and proceeds with sequence assignment if valid, or handles the invalid ID error if not valid
R-GCX146-cbl-01448
More Containers?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers?' is invoked, and assuming that the system has processed one container from a flat car's cross-reference records, when the system checks for additional containers, the desired outcome is that the system determines if more containers exist for the same flat car and continues processing if more exist, or completes container processing if no more exist.
💻 Technical Criteria
Given
The system has processed one container from a flat car's cross-reference records
When
The system checks for additional containers
Then
The system determines if more containers exist for the same flat car and continues processing if more exist, or completes container processing if no more exist
R-GCX146-cbl-01449
Process Next Container in Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Process Next Container in Sequence' is invoked, and assuming that multiple containers exist on a flat car and one has been processed, when the system identifies additional containers to process, the desired outcome is that the system processes the next container in sequence, extracting and validating its id following the same validation rules.
💻 Technical Criteria
Given
Multiple containers exist on a flat car and one has been processed
When
The system identifies additional containers to process
Then
The system processes the next container in sequence, extracting and validating its ID following the same validation rules
R-GCX146-cbl-01450
Handle XREF Not Found Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle XREF Not Found Error' is invoked, and assuming that a flat car is being processed for container identification, when no t/c xref records are found in the inquiry database, the desired outcome is that the system handles the no cross-reference scenario and completes processing without container data.
💻 Technical Criteria
Given
A flat car is being processed for container identification
When
No T/C XREF records are found in the inquiry database
Then
The system handles the no cross-reference scenario and completes processing without container data
R-GCX146-cbl-01451
Handle Invalid Container ID Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Invalid Container ID Error' is invoked, and assuming that a container id has been extracted from cross-reference records, when the container id fails format validation requirements, the desired outcome is that the system handles the invalid container id error and continues processing remaining containers or completes processing.
💻 Technical Criteria
Given
A container ID has been extracted from cross-reference records
When
The container ID fails format validation requirements
Then
The system handles the invalid container ID error and continues processing remaining containers or completes processing
R-GCX146-cbl-00135
Call GCCCARTP Module for Type Classification
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCCARTP Module for Type Classification' is invoked, and assuming that equipment data with equipment id and type code is available, when equipment type classification is required, the desired outcome is that gcccartp module is called to classify equipment type and return classification results.
💻 Technical Criteria
Given
Equipment data with equipment ID and type code is available
When
Equipment type classification is required
Then
GCCCARTP module is called to classify equipment type and return classification results
R-GCX146-cbl-00136
Container Type Processing
Process Rules
📊 Business Logic Narrative
When the process 'Container Type Processing' is invoked, and assuming that equipment has been classified as container type, when container type processing is initiated, the desired outcome is that container-specific processing flags are set and container handling requirements are established.
💻 Technical Criteria
Given
Equipment has been classified as container type
When
Container type processing is initiated
Then
Container-specific processing flags are set and container handling requirements are established
R-GCX146-cbl-00137
Trailer Type Processing
Process Rules
📊 Business Logic Narrative
When the process 'Trailer Type Processing' is invoked, and assuming that equipment has been classified as trailer type, when trailer type processing is initiated, the desired outcome is that trailer-specific processing flags are set and trailer handling requirements are established.
💻 Technical Criteria
Given
Equipment has been classified as trailer type
When
Trailer type processing is initiated
Then
Trailer-specific processing flags are set and trailer handling requirements are established
R-GCX146-cbl-00138
Car Type Processing
Process Rules
📊 Business Logic Narrative
When the process 'Car Type Processing' is invoked, and assuming that equipment has been classified as car type, when car type processing is initiated, the desired outcome is that car-specific processing flags are set and car handling requirements are established.
💻 Technical Criteria
Given
Equipment has been classified as car type
When
Car type processing is initiated
Then
Car-specific processing flags are set and car handling requirements are established
R-GCX146-cbl-00139
Check for Multiple Containers on Flat Car
Decision Rules
📊 Business Logic Narrative
When the process 'Check for Multiple Containers on Flat Car' is invoked, and assuming that equipment is classified as container type, when system checks for multiple containers on the same flat car, the desired outcome is that if multiple containers are detected, ws-flat-car flag is set to indicate special flat car processing requirements.
💻 Technical Criteria
Given
Equipment is classified as container type
When
System checks for multiple containers on the same flat car
Then
If multiple containers are detected, WS-FLAT-CAR flag is set to indicate special flat car processing requirements
R-GCX146-cbl-00140
Validate Car Type Code
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Car Type Code' is invoked, and assuming that equipment is classified as car type with a car type code, when car type code validation is performed, the desired outcome is that system verifies the car type code is valid and exists in the reference data.
💻 Technical Criteria
Given
Equipment is classified as car type with a car type code
When
Car type code validation is performed
Then
System verifies the car type code is valid and exists in the reference data
R-GCX146-cbl-00141
Get Car Type Description from VI Segment
Action Rules
📊 Business Logic Narrative
When the process 'Get Car Type Description from VI Segment' is invoked, and assuming that valid car type code has been confirmed, when car type description is needed for processing or reporting, the desired outcome is that system retrieves car type description from vi segment using the car type code.
💻 Technical Criteria
Given
Valid car type code has been confirmed
When
Car type description is needed for processing or reporting
Then
System retrieves car type description from VI segment using the car type code
R-GCX146-cbl-00142
Assign Type Code for Train Manifest
Definitional Rules
📊 Business Logic Narrative
When the process 'Assign Type Code for Train Manifest' is invoked, and assuming that equipment type has been classified and processing requirements determined, when train manifest requires equipment type code, the desired outcome is that system assigns the appropriate equipment type code based on the equipment classification for manifest reporting.
💻 Technical Criteria
Given
Equipment type has been classified and processing requirements determined
When
Train manifest requires equipment type code
Then
System assigns the appropriate equipment type code based on the equipment classification for manifest reporting
R-GCX146-cbl-00143
Set Load/Empty Processing Requirements
Process Rules
📊 Business Logic Narrative
When the process 'Set Load/Empty Processing Requirements' is invoked, and assuming that equipment type code has been assigned for train manifest, when load/empty status processing requirements need to be established, the desired outcome is that system sets appropriate processing requirements based on whether the equipment is loaded or empty.
💻 Technical Criteria
Given
Equipment type code has been assigned for train manifest
When
Load/empty status processing requirements need to be established
Then
System sets appropriate processing requirements based on whether the equipment is loaded or empty
R-GCX146-cbl-00148
Check Equipment Type Classification
Definitional Rules
📊 Business Logic Narrative
When the process 'Check Equipment Type Classification' is invoked, and assuming that cargo origin and destination information has been analyzed, when the system checks the equipment type classification, the desired outcome is that the system categorizes equipment as container, trailer, or rail car type for specific processing rules.
💻 Technical Criteria
Given
Cargo origin and destination information has been analyzed
When
The system checks the equipment type classification
Then
The system categorizes equipment as container, trailer, or rail car type for specific processing rules
R-GCX146-cbl-00149
Container Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'Container Equipment?' is invoked, and assuming that equipment type classification check has been performed, when the system evaluates if equipment is container type, the desired outcome is that if equipment is container type, proceed with container-specific load status determination; otherwise check for trailer type.
💻 Technical Criteria
Given
Equipment type classification check has been performed
When
The system evaluates if equipment is container type
Then
If equipment is container type, proceed with container-specific load status determination; otherwise check for trailer type
R-GCX146-cbl-00150
Trailer Equipment?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Trailer Equipment?', assuming that equipment is not container type, when the system evaluates if equipment is trailer type, the desired outcome is that if equipment is trailer type, proceed with trailer-specific load status determination; otherwise treat as rail car equipment.
💻 Technical Criteria
EXCLUDING
Equipment is not container type
When
The system evaluates if equipment is trailer type
Then
If equipment is trailer type, proceed with trailer-specific load status determination; otherwise treat as rail car equipment
R-GCX146-cbl-00151
Rail Car Equipment?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Rail Car Equipment?', assuming that equipment is not container or trailer type, when the system evaluates if equipment is rail car type, the desired outcome is that if equipment is rail car type, proceed with rail car-specific load status determination.
💻 Technical Criteria
EXCLUDING
Equipment is not container or trailer type
When
The system evaluates if equipment is rail car type
Then
If equipment is rail car type, proceed with rail car-specific load status determination
R-GCX146-cbl-00155
Validate Against Input Specifications
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Against Input Specifications' is invoked, and assuming that load/empty status has been determined for the equipment, when the system validates the determined status against input specifications, the desired outcome is that the system compares the calculated load/empty status with the input-provided status for consistency verification.
💻 Technical Criteria
Given
Load/empty status has been determined for the equipment
When
The system validates the determined status against input specifications
Then
The system compares the calculated load/empty status with the input-provided status for consistency verification
R-GCX146-cbl-00156
Status Matches Input?
Decision Rules
📊 Business Logic Narrative
When the process 'Status Matches Input?' is invoked, and assuming that load/empty status validation has been performed, when the system checks if determined status matches input specifications, the desired outcome is that if status matches input, set appropriate load flag; if status does not match, generate validation error and use empty status.
💻 Technical Criteria
Given
Load/empty status validation has been performed
When
The system checks if determined status matches input specifications
Then
If status matches input, set appropriate load flag; if status does not match, generate validation error and use empty status
R-GCX146-cbl-00157
Set LOAD Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set LOAD Flag' is invoked, and assuming that equipment status validation confirms loaded status, when the system processes load flag assignment, the desired outcome is that the system sets the load indicator flag to indicate equipment carries cargo.
💻 Technical Criteria
Given
Equipment status validation confirms loaded status
When
The system processes load flag assignment
Then
The system sets the load indicator flag to indicate equipment carries cargo
R-GCX146-cbl-00159
Assign Load/Empty Status Indicator
Action Rules
📊 Business Logic Narrative
When the process 'Assign Load/Empty Status Indicator' is invoked, and assuming that either load flag or empty flag has been set, when the system processes status indicator assignment, the desired outcome is that the system assigns the appropriate load/empty status indicator to the equipment record.
💻 Technical Criteria
Given
Either load flag or empty flag has been set
When
The system processes status indicator assignment
Then
The system assigns the appropriate load/empty status indicator to the equipment record
R-GCX146-cbl-00160
Update Equipment Record Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Record Status' is invoked, and assuming that load/empty status indicator has been assigned, when the system processes equipment record update, the desired outcome is that the system updates the equipment record with the final load/empty status for further processing.
💻 Technical Criteria
Given
Load/empty status indicator has been assigned
When
The system processes equipment record update
Then
The system updates the equipment record with the final load/empty status for further processing
R-GCX146-cbl-00161
Generate Status Validation Error
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Status Validation Error', assuming that determined load/empty status does not match input specifications, when the system processes status validation error, the desired outcome is that the system generates a status validation error and defaults to empty status processing.
💻 Technical Criteria
EXCLUDING
Determined load/empty status does not match input specifications
When
The system processes status validation error
Then
The system generates a status validation error and defaults to empty status processing
R-GCX146-cbl-00169
Set Commodity Code for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Set Commodity Code for Processing' is invoked, and assuming that commodity code has passed all validation checks, when system processes validated commodity code, the desired outcome is that system sets commodity code for equipment record and continues with processing workflow.
💻 Technical Criteria
Given
Commodity code has passed all validation checks
When
System processes validated commodity code
Then
System sets commodity code for equipment record and continues with processing workflow
R-GCX146-cbl-00171
Log Commodity Code Validation Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Commodity Code Validation Error' is invoked, and assuming that commodity code format validation fails or commodity standards validation fails, when system encounters commodity code validation errors, the desired outcome is that system logs commodity code validation error and continues with equipment processing using default handling.
💻 Technical Criteria
Given
Commodity code format validation fails OR commodity standards validation fails
When
System encounters commodity code validation errors
Then
System logs commodity code validation error and continues with equipment processing using default handling
R-GCX146-cbl-00222
Ocean vs Rail Manifest Detection - Identify and validate manifest types
Definitional Rules
📊 Business Logic Narrative
When the process 'Ocean vs Rail Manifest Detection - Identify and validate manifest types' is invoked, and assuming that a cargo manifest with manifest type code, when the manifest type code equals '9' (ocean manifest), the desired outcome is that the system sets ocean manifest flag to true and tracks ocean manifest presence.
💻 Technical Criteria
Given
A cargo manifest with manifest type code
When
The manifest type code equals '9' (ocean manifest)
Then
The system sets ocean manifest flag to true and tracks ocean manifest presence
R-GCX146-cbl-00223
Ocean vs Rail Manifest Detection - Identify and validate manifest types
Definitional Rules
📊 Business Logic Narrative
When the process 'Ocean vs Rail Manifest Detection - Identify and validate manifest types' is invoked, and assuming that a cargo manifest with manifest type code, when the manifest type code equals '6' (rail manifest), the desired outcome is that the system sets rail manifest flag to true and processes as rail cargo.
💻 Technical Criteria
Given
A cargo manifest with manifest type code
When
The manifest type code equals '6' (rail manifest)
Then
The system sets rail manifest flag to true and processes as rail cargo
R-GCX146-cbl-00224
Ocean vs Rail Manifest Detection - Identify and validate manifest types
Validation Rules
📊 Business Logic Narrative
When the process 'Ocean vs Rail Manifest Detection - Identify and validate manifest types' is invoked, and assuming that processing has completed for all equipment on a train and ocean manifest flag is set to true and rail manifest flag is set to false, when the validation check for manifest completeness is performed, the desired outcome is that the system generates error 39 indicating ocean manifest without corresponding rail manifest.
💻 Technical Criteria
Given
Processing has completed for all equipment on a train AND ocean manifest flag is set to true AND rail manifest flag is set to false
When
The validation check for manifest completeness is performed
Then
The system generates error 39 indicating ocean manifest without corresponding rail manifest
R-GCX146-cbl-00225
Ocean vs Rail Manifest Detection - Identify and validate manifest types
Process Rules
📊 Business Logic Narrative
When the process 'Ocean vs Rail Manifest Detection - Identify and validate manifest types' is invoked, and assuming that a new train processing session is starting, when the system begins processing equipment for manifest type detection, the desired outcome is that the system sets both ocean manifest flag and rail manifest flag to false as initial state.
💻 Technical Criteria
Given
A new train processing session is starting
When
The system begins processing equipment for manifest type detection
Then
The system sets both ocean manifest flag and rail manifest flag to false as initial state
R-GCX146-cbl-00226
Access Flat Car Container Records
Action Rules
📊 Business Logic Narrative
When the process 'Access Flat Car Container Records' is invoked, and assuming that a flat car equipment record is being processed, when the system needs to identify containers on the flat car, the desired outcome is that container records are accessed from the flat car container database using the equipment id.
💻 Technical Criteria
Given
A flat car equipment record is being processed
When
The system needs to identify containers on the flat car
Then
Container records are accessed from the flat car container database using the equipment ID
R-GCX146-cbl-00227
Container Records Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Records Found?' is invoked, and assuming that container record lookup has been performed for a flat car, when the system evaluates the lookup results, the desired outcome is that processing continues with container handling if records are found, otherwise container processing is skipped.
💻 Technical Criteria
Given
Container record lookup has been performed for a flat car
When
The system evaluates the lookup results
Then
Processing continues with container handling if records are found, otherwise container processing is skipped
R-GCX146-cbl-00228
Set Flat Car Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag' is invoked, and assuming that container records have been found for a flat car, when the system begins container processing, the desired outcome is that a flat car processing flag is set to track the processing state.
💻 Technical Criteria
Given
Container records have been found for a flat car
When
The system begins container processing
Then
A flat car processing flag is set to track the processing state
R-GCX146-cbl-00229
Extract Container IDs from T/C XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container IDs from T/C XREF' is invoked, and assuming that flat car container records are available, when the system processes the cross-reference data, the desired outcome is that individual container ids are extracted from the t/c xref records for further processing.
💻 Technical Criteria
Given
Flat car container records are available
When
The system processes the cross-reference data
Then
Individual container IDs are extracted from the T/C XREF records for further processing
R-GCX146-cbl-00230
Process First Container
Process Rules
📊 Business Logic Narrative
When the process 'Process First Container' is invoked, and assuming that container ids have been extracted from cross-reference records, when the system starts individual container processing, the desired outcome is that the first container in the sequence is selected for processing.
💻 Technical Criteria
Given
Container IDs have been extracted from cross-reference records
When
The system starts individual container processing
Then
The first container in the sequence is selected for processing
R-GCX146-cbl-00235
More Containers on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers on Flat Car?' is invoked, and assuming that one container has been processed on a flat car, when the system checks for additional containers, the desired outcome is that processing continues with next container if more exist, otherwise totals are updated.
💻 Technical Criteria
Given
One container has been processed on a flat car
When
The system checks for additional containers
Then
Processing continues with next container if more exist, otherwise totals are updated
R-GCX146-cbl-00236
Get Next Container in Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Container in Sequence' is invoked, and assuming that multiple containers exist on a flat car, when the system needs to process the next container, the desired outcome is that the next container in sequence is retrieved for processing.
💻 Technical Criteria
Given
Multiple containers exist on a flat car
When
The system needs to process the next container
Then
The next container in sequence is retrieved for processing
R-GCX146-cbl-00237
Process Additional Container
Process Rules
📊 Business Logic Narrative
When the process 'Process Additional Container' is invoked, and assuming that a subsequent container has been retrieved, when the system processes the additional container, the desired outcome is that the container undergoes the same validation and processing as the first container.
💻 Technical Criteria
Given
A subsequent container has been retrieved
When
The system processes the additional container
Then
The container undergoes the same validation and processing as the first container
R-GCX146-cbl-00238
Update Container Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Update Container Totals' is invoked, and assuming that all containers on a flat car have been processed, when the system finalizes container processing, the desired outcome is that container totals are updated to reflect all processed containers.
💻 Technical Criteria
Given
All containers on a flat car have been processed
When
The system finalizes container processing
Then
Container totals are updated to reflect all processed containers
R-GCX146-cbl-00239
Complete Flat Car Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Flat Car Processing' is invoked, and assuming that all containers have been processed and totals updated, when the system finalizes flat car processing, the desired outcome is that flat car processing is marked as complete.
💻 Technical Criteria
Given
All containers have been processed and totals updated
When
The system finalizes flat car processing
Then
Flat car processing is marked as complete
R-GCX146-cbl-00241
Inquiry Data Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Inquiry Data Found?' is invoked, and assuming that inquiry database lookup has been performed, when the system evaluates lookup results, the desired outcome is that primary container data is used if found, otherwise container is marked as not found.
💻 Technical Criteria
Given
Inquiry database lookup has been performed
When
The system evaluates lookup results
Then
Primary container data is used if found, otherwise container is marked as not found
R-GCX146-cbl-00242
Use Primary Container Data
Process Rules
📊 Business Logic Narrative
When the process 'Use Primary Container Data' is invoked, and assuming that container data has been found in inquiry database, when the system processes the container information, the desired outcome is that primary container data from inquiry database is used for processing.
💻 Technical Criteria
Given
Container data has been found in inquiry database
When
The system processes the container information
Then
Primary container data from inquiry database is used for processing
R-GCX146-cbl-00243
Mark Container as Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Mark Container as Not Found' is invoked, and assuming that no container data is found in either primary or inquiry databases, when the system cannot locate container information, the desired outcome is that container is marked as not found and processing continues.
💻 Technical Criteria
Given
No container data is found in either primary or inquiry databases
When
The system cannot locate container information
Then
Container is marked as not found and processing continues
R-GCX146-cbl-01208
Access Flat Car Container Records Z510-GU-FWSWRWR
Action Rules
📊 Business Logic Narrative
When the process 'Access Flat Car Container Records Z510-GU-FWSWRWR' is invoked, and assuming that a flat car equipment id is provided for container lookup, when the system accesses the flat car container records database, the desired outcome is that container records associated with the flat car are retrieved for processing.
💻 Technical Criteria
Given
A flat car equipment ID is provided for container lookup
When
The system accesses the flat car container records database
Then
Container records associated with the flat car are retrieved for processing
R-GCX146-cbl-01209
Container Records Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Records Found?' is invoked, and assuming that a flat car container database lookup has been performed, when the system checks for the presence of container records, the desired outcome is that processing continues if records are found, otherwise container processing is skipped.
💻 Technical Criteria
Given
A flat car container database lookup has been performed
When
The system checks for the presence of container records
Then
Processing continues if records are found, otherwise container processing is skipped
R-GCX146-cbl-01210
Extract Container IDs from Flat Car Records
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container IDs from Flat Car Records' is invoked, and assuming that container records exist for a flat car, when the system processes the flat car container records, the desired outcome is that individual container ids are extracted from the records for validation and processing.
💻 Technical Criteria
Given
Container records exist for a flat car
When
The system processes the flat car container records
Then
Individual container IDs are extracted from the records for validation and processing
R-GCX146-cbl-01211
Set Flat Car Processing Flag WS-FLAT-CAR = TRUE
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag WS-FLAT-CAR = TRUE' is invoked, and assuming that container records have been found for equipment, when the system identifies the equipment as carrying containers, the desired outcome is that the flat car processing flag is set to indicate special container handling is required.
💻 Technical Criteria
Given
Container records have been found for equipment
When
The system identifies the equipment as carrying containers
Then
The flat car processing flag is set to indicate special container handling is required
R-GCX146-cbl-01212
Access Container Inquiry Database Z530-GU-FW-IQ
Action Rules
📊 Business Logic Narrative
When the process 'Access Container Inquiry Database Z530-GU-FW-IQ' is invoked, and assuming that container ids have been extracted from flat car records, when the system needs detailed container information, the desired outcome is that container inquiry database is accessed to retrieve comprehensive container data.
💻 Technical Criteria
Given
Container IDs have been extracted from flat car records
When
The system needs detailed container information
Then
Container inquiry database is accessed to retrieve comprehensive container data
R-GCX146-cbl-01213
Container Inquiry Records Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Inquiry Records Available?' is invoked, and assuming that container inquiry database has been accessed, when the system checks for available container inquiry records, the desired outcome is that processing continues with record retrieval if available, otherwise container processing completes.
💻 Technical Criteria
Given
Container inquiry database has been accessed
When
The system checks for available container inquiry records
Then
Processing continues with record retrieval if available, otherwise container processing completes
R-GCX146-cbl-01214
Retrieve Next Container Record Z540-GNP-FWIQ
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Container Record Z540-GNP-FWIQ' is invoked, and assuming that container inquiry records are available in the database, when the system processes containers sequentially, the desired outcome is that each container record is retrieved in sequence for individual processing.
💻 Technical Criteria
Given
Container inquiry records are available in the database
When
The system processes containers sequentially
Then
Each container record is retrieved in sequence for individual processing
R-GCX146-cbl-01215
Extract Container ID from T/C XREF Records
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from T/C XREF Records' is invoked, and assuming that container inquiry records contain t/c xref data, when the system processes cross-reference information, the desired outcome is that container ids are extracted from the cross-reference records for validation.
💻 Technical Criteria
Given
Container inquiry records contain T/C XREF data
When
The system processes cross-reference information
Then
Container IDs are extracted from the cross-reference records for validation
R-GCX146-cbl-01216
Validate Container ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Container ID Format' is invoked, and assuming that a container id has been extracted from cross-reference records, when the system validates the container id format, the desired outcome is that container id is accepted if format is valid, otherwise marked as invalid.
💻 Technical Criteria
Given
A container ID has been extracted from cross-reference records
When
The system validates the container ID format
Then
Container ID is accepted if format is valid, otherwise marked as invalid
R-GCX146-cbl-01217
Container ID Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Container ID Valid?' is invoked, and assuming that container id format validation has been performed, when the system evaluates validation results, the desired outcome is that valid container ids are stored for processing, invalid ids are marked and processing continues.
💻 Technical Criteria
Given
Container ID format validation has been performed
When
The system evaluates validation results
Then
Valid container IDs are stored for processing, invalid IDs are marked and processing continues
R-GCX146-cbl-01218
Store Valid Container ID for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Store Valid Container ID for Processing' is invoked, and assuming that a container id has passed format validation, when the system processes valid container information, the desired outcome is that the valid container id is stored in the processing queue for further business operations.
💻 Technical Criteria
Given
A container ID has passed format validation
When
The system processes valid container information
Then
The valid container ID is stored in the processing queue for further business operations
R-GCX146-cbl-01219
Mark Container as Invalid
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Mark Container as Invalid', assuming that a container id has failed format validation, when the system encounters an invalid container id, the desired outcome is that the container is marked as invalid and excluded from further processing.
💻 Technical Criteria
EXCLUDING
A container ID has failed format validation
When
The system encounters an invalid container ID
Then
The container is marked as invalid and excluded from further processing
R-GCX146-cbl-01220
More Containers on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers on Flat Car?' is invoked, and assuming that a container has been processed from a flat car, when the system checks for additional containers on the same flat car, the desired outcome is that processing continues with next container if more exist, otherwise container processing completes.
💻 Technical Criteria
Given
A container has been processed from a flat car
When
The system checks for additional containers on the same flat car
Then
Processing continues with next container if more exist, otherwise container processing completes
R-GCX146-cbl-01221
Container Processing Complete
Process Rules
📊 Business Logic Narrative
When the process 'Container Processing Complete' is invoked, and assuming that all containers on a flat car have been processed or no containers were found, when the system reaches the end of container processing, the desired outcome is that container processing is marked as complete and control returns to main equipment processing.
💻 Technical Criteria
Given
All containers on a flat car have been processed or no containers were found
When
The system reaches the end of container processing
Then
Container processing is marked as complete and control returns to main equipment processing
R-GCX146-cbl-01222
Access Flat Car Container Records
Action Rules
📊 Business Logic Narrative
When the process 'Access Flat Car Container Records' is invoked, and assuming that a flat car equipment requires container processing, when the system initiates container sequence processing, the desired outcome is that the system accesses the flat car's container records from the container database.
💻 Technical Criteria
Given
A flat car equipment requires container processing
When
The system initiates container sequence processing
Then
The system accesses the flat car's container records from the container database
R-GCX146-cbl-01223
Container Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Record Found?' is invoked, and assuming that the system has accessed container records for a flat car, when the system checks for container record availability, the desired outcome is that the system determines if valid container records exist or if container processing should terminate with error.
💻 Technical Criteria
Given
The system has accessed container records for a flat car
When
The system checks for container record availability
Then
The system determines if valid container records exist or if container processing should terminate with error
R-GCX146-cbl-01224
Extract Container ID from Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from Record' is invoked, and assuming that a valid container record has been found for the flat car, when the system processes the container record, the desired outcome is that the system extracts the container id from the record for further validation and processing.
💻 Technical Criteria
Given
A valid container record has been found for the flat car
When
The system processes the container record
Then
The system extracts the container ID from the record for further validation and processing
R-GCX146-cbl-01225
Validate Container Information
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Container Information' is invoked, and assuming that a container id has been extracted from the container record, when the system validates the container information, the desired outcome is that the system verifies the container data meets all validation criteria and business requirements.
💻 Technical Criteria
Given
A container ID has been extracted from the container record
When
The system validates the container information
Then
The system verifies the container data meets all validation criteria and business requirements
R-GCX146-cbl-01227
More Containers on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers on Flat Car?' is invoked, and assuming that one container has been processed for a flat car, when the system checks for additional containers on the same flat car, the desired outcome is that the system determines whether more containers exist that need to be processed or if container sequence processing is complete.
💻 Technical Criteria
Given
One container has been processed for a flat car
When
The system checks for additional containers on the same flat car
Then
The system determines whether more containers exist that need to be processed or if container sequence processing is complete
R-GCX146-cbl-01228
Get Next Container Record
Action Rules
📊 Business Logic Narrative
When the process 'Get Next Container Record' is invoked, and assuming that multiple containers exist on a flat car and one has been processed, when the system needs to process the next container, the desired outcome is that the system retrieves the next sequential container record for processing.
💻 Technical Criteria
Given
Multiple containers exist on a flat car and one has been processed
When
The system needs to process the next container
Then
The system retrieves the next sequential container record for processing
R-GCX146-cbl-01229
Set Flat Car Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag' is invoked, and assuming that all containers on a flat car have been processed successfully, when the system completes container sequence processing, the desired outcome is that the system sets the flat car processing flag to indicate completion.
💻 Technical Criteria
Given
All containers on a flat car have been processed successfully
When
The system completes container sequence processing
Then
The system sets the flat car processing flag to indicate completion
R-GCX146-cbl-01230
Complete Container Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Complete Container Sequence' is invoked, and assuming that the flat car processing flag has been set, when the system finalizes container processing, the desired outcome is that the system completes the container sequence processing and prepares for next equipment processing.
💻 Technical Criteria
Given
The flat car processing flag has been set
When
The system finalizes container processing
Then
The system completes the container sequence processing and prepares for next equipment processing
R-GCX146-cbl-01231
Container Processing Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Container Processing Error', assuming that container records are not found for a flat car, when the system encounters container processing errors, the desired outcome is that the system terminates container processing and handles the error condition appropriately.
💻 Technical Criteria
EXCLUDING
Container records are not found for a flat car
When
The system encounters container processing errors
Then
The system terminates container processing and handles the error condition appropriately
R-GCX146-cbl-01452
Set Flat Car Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Flag' is invoked, and assuming that an equipment record is being processed, when the equipment type indicates it is a flat car capable of carrying containers, the desired outcome is that the system sets the flat car processing flag to enable container sequence management.
💻 Technical Criteria
Given
An equipment record is being processed
When
The equipment type indicates it is a flat car capable of carrying containers
Then
The system sets the flat car processing flag to enable container sequence management
R-GCX146-cbl-01453
Initialize Container Sequence Counter
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Container Sequence Counter' is invoked, and assuming that a flat car is being processed for container handling, when container sequence processing begins, the desired outcome is that the container sequence counter is initialized to zero to track container positions on the flat car.
💻 Technical Criteria
Given
A flat car is being processed for container handling
When
Container sequence processing begins
Then
The container sequence counter is initialized to zero to track container positions on the flat car
R-GCX146-cbl-01454
Access Container Records via Z510-GU-FWSWRWR
Action Rules
📊 Business Logic Narrative
When the process 'Access Container Records via Z510-GU-FWSWRWR' is invoked, and assuming that a flat car requires container processing, when the system needs to identify containers on the flat car, the desired outcome is that the system accesses the fwswrwr container records database using the z510-gu-fwswrwr procedure.
💻 Technical Criteria
Given
A flat car requires container processing
When
The system needs to identify containers on the flat car
Then
The system accesses the FWSWRWR container records database using the Z510-GU-FWSWRWR procedure
R-GCX146-cbl-01455
Container Record Found?
Decision Rules
📊 Business Logic Narrative
When the process 'Container Record Found?' is invoked, and assuming that the system has attempted to retrieve container records for a flat car, when the database lookup is completed, the desired outcome is that the system determines if valid container records were found and branches processing accordingly.
💻 Technical Criteria
Given
The system has attempted to retrieve container records for a flat car
When
The database lookup is completed
Then
The system determines if valid container records were found and branches processing accordingly
R-GCX146-cbl-01456
Extract Container ID from Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from Record' is invoked, and assuming that a valid container record has been retrieved from the database, when container identification is required for processing, the desired outcome is that the system extracts the container id from the container record for further processing.
💻 Technical Criteria
Given
A valid container record has been retrieved from the database
When
Container identification is required for processing
Then
The system extracts the container ID from the container record for further processing
R-GCX146-cbl-01457
Set Container Position Tracking
Process Rules
📊 Business Logic Narrative
When the process 'Set Container Position Tracking' is invoked, and assuming that a container id has been extracted from a container record, when container position management is required, the desired outcome is that the system establishes position tracking for the container including its sequential placement on the flat car.
💻 Technical Criteria
Given
A container ID has been extracted from a container record
When
Container position management is required
Then
The system establishes position tracking for the container including its sequential placement on the flat car
R-GCX146-cbl-01458
Process Current Container
Process Rules
📊 Business Logic Narrative
When the process 'Process Current Container' is invoked, and assuming that a container has been identified and positioned on the flat car, when container processing is required, the desired outcome is that the system processes the current container including status updates and detail recording.
💻 Technical Criteria
Given
A container has been identified and positioned on the flat car
When
Container processing is required
Then
The system processes the current container including status updates and detail recording
R-GCX146-cbl-01459
Increment Sequence Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Sequence Counter' is invoked, and assuming that a container has been successfully processed, when moving to the next container in sequence, the desired outcome is that the system increments the container sequence counter to maintain proper position tracking.
💻 Technical Criteria
Given
A container has been successfully processed
When
Moving to the next container in sequence
Then
The system increments the container sequence counter to maintain proper position tracking
R-GCX146-cbl-01460
Get Next Container in Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Container in Sequence' is invoked, and assuming that the current container has been processed and the sequence counter incremented, when additional containers may exist on the flat car, the desired outcome is that the system retrieves the next container record in the sequential order.
💻 Technical Criteria
Given
The current container has been processed and the sequence counter incremented
When
Additional containers may exist on the flat car
Then
The system retrieves the next container record in the sequential order
R-GCX146-cbl-01461
More Containers on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers on Flat Car?' is invoked, and assuming that a container has been processed and the next container record has been attempted, when determining if container processing should continue, the desired outcome is that the system evaluates whether more containers exist on the flat car and branches processing accordingly.
💻 Technical Criteria
Given
A container has been processed and the next container record has been attempted
When
Determining if container processing should continue
Then
The system evaluates whether more containers exist on the flat car and branches processing accordingly
R-GCX146-cbl-01462
Complete Container Sequence Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Container Sequence Processing' is invoked, and assuming that all containers on the flat car have been processed or no containers were found, when container sequence processing reaches completion, the desired outcome is that the system completes the container sequence processing and finalizes all container-related activities for the flat car.
💻 Technical Criteria
Given
All containers on the flat car have been processed OR no containers were found
When
Container sequence processing reaches completion
Then
The system completes the container sequence processing and finalizes all container-related activities for the flat car
R-GCX146-cbl-01463
Handle Container Not Found
Process Rules
📊 Business Logic Narrative
When the process 'Handle Container Not Found' is invoked, and assuming that a flat car has been identified for container processing, when no container records are found in the fwswrwr database, the desired outcome is that the system handles the container not found condition and proceeds to complete processing.
💻 Technical Criteria
Given
A flat car has been identified for container processing
When
No container records are found in the FWSWRWR database
Then
The system handles the container not found condition and proceeds to complete processing
R-GCX146-cbl-01587
Access Container Record on Flat Car
Action Rules
📊 Business Logic Narrative
When the process 'Access Container Record on Flat Car' is invoked, and assuming that a flat car is being processed for containers, when the system attempts to access container records on the flat car, the desired outcome is that container records are retrieved from the container database for further processing.
💻 Technical Criteria
Given
A flat car is being processed for containers
When
The system attempts to access container records on the flat car
Then
Container records are retrieved from the container database for further processing
R-GCX146-cbl-01588
Container Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Record Found?' is invoked, and assuming that container record access has been attempted for a flat car, when the system checks for container record existence, the desired outcome is that processing continues if container records are found, otherwise container processing terminates with error.
💻 Technical Criteria
Given
Container record access has been attempted for a flat car
When
The system checks for container record existence
Then
Processing continues if container records are found, otherwise container processing terminates with error
R-GCX146-cbl-01589
Extract Container ID from Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from Record' is invoked, and assuming that a valid container record has been found, when the system processes the container record, the desired outcome is that the container id is extracted from the record for validation and further processing.
💻 Technical Criteria
Given
A valid container record has been found
When
The system processes the container record
Then
The container ID is extracted from the record for validation and further processing
R-GCX146-cbl-01590
Validate Container ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Container ID Format' is invoked, and assuming that a container id has been extracted from the container record, when the system validates the container id format, the desired outcome is that processing continues if the container id format is valid, otherwise container processing terminates with error.
💻 Technical Criteria
Given
A container ID has been extracted from the container record
When
The system validates the container ID format
Then
Processing continues if the container ID format is valid, otherwise container processing terminates with error
R-GCX146-cbl-01594
Inquiry Data Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Inquiry Data Available?' is invoked, and assuming that container inquiry database has been accessed, when the system checks for inquiry data availability, the desired outcome is that if inquiry data is available, container details are extracted; otherwise container processing terminates with error.
💻 Technical Criteria
Given
Container inquiry database has been accessed
When
The system checks for inquiry data availability
Then
If inquiry data is available, container details are extracted; otherwise container processing terminates with error
R-GCX146-cbl-01596
Set Container Processing Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set Container Processing Flags' is invoked, and assuming that container equipment details have been extracted, when the system sets container processing flags, the desired outcome is that processing flags are assigned to indicate container status, type, and processing requirements.
💻 Technical Criteria
Given
Container equipment details have been extracted
When
The system sets container processing flags
Then
Processing flags are assigned to indicate container status, type, and processing requirements
R-GCX146-cbl-01597
Determine Container Load/Empty Status
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Container Load/Empty Status' is invoked, and assuming that container processing flags have been set, when the system determines container load status, the desired outcome is that container is classified as either loaded or empty based on cargo information and processing flags.
💻 Technical Criteria
Given
Container processing flags have been set
When
The system determines container load status
Then
Container is classified as either loaded or empty based on cargo information and processing flags
R-GCX146-cbl-01598
Assign Container to Equipment List
Process Rules
📊 Business Logic Narrative
When the process 'Assign Container to Equipment List' is invoked, and assuming that container load/empty status has been determined, when the system assigns the container to equipment list, the desired outcome is that container is added to the train's equipment list with all relevant details and status information.
💻 Technical Criteria
Given
Container load/empty status has been determined
When
The system assigns the container to equipment list
Then
Container is added to the train's equipment list with all relevant details and status information
R-GCX146-cbl-01599
Move to Next Container on Flat Car
Process Rules
📊 Business Logic Narrative
When the process 'Move to Next Container on Flat Car' is invoked, and assuming that current container has been assigned to equipment list, when the system moves to next container on flat car, the desired outcome is that processing continues with the next container on the same flat car, or completes if no more containers exist.
💻 Technical Criteria
Given
Current container has been assigned to equipment list
When
The system moves to next container on flat car
Then
Processing continues with the next container on the same flat car, or completes if no more containers exist
R-GCX146-cbl-01730
Record Type Check
Decision Rules
📊 Business Logic Narrative
When the process 'Record Type Check' is invoked, and assuming that a container record has been accessed from the database, when the system checks the record type, the desired outcome is that the system identifies if the record is a t/c xref record type or another record type.
💻 Technical Criteria
Given
A container record has been accessed from the database
When
The system checks the record type
Then
The system identifies if the record is a T/C XREF record type or another record type
R-GCX146-cbl-01731
Extract from T/C XREF Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract from T/C XREF Record' is invoked, and assuming that a t/c xref record has been identified, when the system processes the t/c xref record, the desired outcome is that the system extracts container id information from the t/c xref record.
💻 Technical Criteria
Given
A T/C XREF record has been identified
When
The system processes the T/C XREF record
Then
The system extracts container ID information from the T/C XREF record
R-GCX146-cbl-01732
Parse Container ID Field
Process Rules
📊 Business Logic Narrative
When the process 'Parse Container ID Field' is invoked, and assuming that container information has been extracted from a t/c xref record, when the system processes the container data, the desired outcome is that the system parses the container id field to extract the container identifier.
💻 Technical Criteria
Given
Container information has been extracted from a T/C XREF record
When
The system processes the container data
Then
The system parses the container ID field to extract the container identifier
R-GCX146-cbl-01733
Container ID Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Container ID Valid?' is invoked, and assuming that a container id has been parsed from the record, when the system validates the container id, the desired outcome is that the system determines if the container id is valid based on format and content requirements.
💻 Technical Criteria
Given
A container ID has been parsed from the record
When
The system validates the container ID
Then
The system determines if the container ID is valid based on format and content requirements
R-GCX146-cbl-01734
Format Container ID
Process Rules
📊 Business Logic Narrative
When the process 'Format Container ID' is invoked, and assuming that a valid container id has been identified, when the system processes the valid container id, the desired outcome is that the system formats the container id according to standard container identification format.
💻 Technical Criteria
Given
A valid container ID has been identified
When
The system processes the valid container ID
Then
The system formats the container ID according to standard container identification format
R-GCX146-cbl-01735
Store Container ID
Process Rules
📊 Business Logic Narrative
When the process 'Store Container ID' is invoked, and assuming that a container id has been formatted according to standards, when the system completes container id formatting, the desired outcome is that the system stores the formatted container id for processing.
💻 Technical Criteria
Given
A container ID has been formatted according to standards
When
The system completes container ID formatting
Then
The system stores the formatted container ID for processing
R-GCX146-cbl-01736
Set Container Found Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Container Found Flag' is invoked, and assuming that a container id has been successfully stored, when the container processing is completed successfully, the desired outcome is that the system sets the container found flag to indicate successful container identification.
💻 Technical Criteria
Given
A container ID has been successfully stored
When
The container processing is completed successfully
Then
The system sets the container found flag to indicate successful container identification
R-GCX146-cbl-01737
Set Container Not Found Flag
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Container Not Found Flag', assuming that container processing has been attempted, when the record is not a t/c xref record type or container id is invalid, the desired outcome is that the system sets the container not found flag to indicate unsuccessful container identification.
💻 Technical Criteria
EXCLUDING
Container processing has been attempted
When
The record is not a T/C XREF record type OR container ID is invalid
Then
The system sets the container not found flag to indicate unsuccessful container identification
R-GCX146-cbl-01738
Log Extraction Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Extraction Error', assuming that container id parsing has been attempted, when the container id is determined to be invalid, the desired outcome is that the system logs an extraction error for the invalid container id.
💻 Technical Criteria
EXCLUDING
Container ID parsing has been attempted
When
The container ID is determined to be invalid
Then
The system logs an extraction error for the invalid container ID
R-GCX146-cbl-01739
Container ID Format Validation Not Found
Validation Rules
📊 Business Logic Narrative
When the process 'Container ID Format Validation Not Found' is invoked, and assuming that a container processing operation is being performed, when the system attempts to validate container id format, the desired outcome is that no specific container id format validation is executed as this functionality is not implemented in the current system.
💻 Technical Criteria
Given
A container processing operation is being performed
When
The system attempts to validate container ID format
Then
No specific container ID format validation is executed as this functionality is not implemented in the current system
R-GCX146-cbl-01741
Container Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Record Found?' is invoked, and assuming that the fw-iq inquiry database has been accessed for a specific container, when the system searches for container records, the desired outcome is that the system determines if a valid container record exists and proceeds accordingly.
💻 Technical Criteria
Given
The FW-IQ inquiry database has been accessed for a specific container
When
The system searches for container records
Then
The system determines if a valid container record exists and proceeds accordingly
R-GCX146-cbl-01742
Extract Container ID from T/C XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from T/C XREF' is invoked, and assuming that a container record has been found in the inquiry database, when the system processes the container record, the desired outcome is that the container id is extracted from the t/c xref data for further processing.
💻 Technical Criteria
Given
A container record has been found in the inquiry database
When
The system processes the container record
Then
The container ID is extracted from the T/C XREF data for further processing
R-GCX146-cbl-00251
Update Equipment Status Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Totals' is invoked, and assuming that equipment has been processed and classified as empty, idler, or exempted, when the equipment processing is complete, the desired outcome is that the appropriate equipment status totals are incremented (total equipment count, empty count, exempted count) for reporting purposes.
💻 Technical Criteria
Given
Equipment has been processed and classified as empty, idler, or exempted
When
The equipment processing is complete
Then
The appropriate equipment status totals are incremented (total equipment count, empty count, exempted count) for reporting purposes
R-GCX146-cbl-00255
Initialize Status Counters
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Counters' is invoked, and assuming that a verify operation is being performed on a train, when the equipment status totals compilation process begins, the desired outcome is that all status counters (total-equip, total-release, total-haulage, total-held-ccra, total-proceed, total-held-docs, total-docs-nr) are set to zero.
💻 Technical Criteria
Given
A VERIFY operation is being performed on a train
When
The equipment status totals compilation process begins
Then
All status counters (TOTAL-EQUIP, TOTAL-RELEASE, TOTAL-HAULAGE, TOTAL-HELD-CCRA, TOTAL-PROCEED, TOTAL-HELD-DOCS, TOTAL-DOCS-NR) are set to zero
R-GCX146-cbl-00256
Equipment Record Available?
Process Rules
📊 Business Logic Narrative
When the process 'Equipment Record Available?' is invoked, and assuming that equipment status totals are being compiled for a train, when the system checks for the next equipment record, the desired outcome is that if equipment records exist, continue processing; otherwise proceed to generate totals summary.
💻 Technical Criteria
Given
Equipment status totals are being compiled for a train
When
The system checks for the next equipment record
Then
If equipment records exist, continue processing; otherwise proceed to generate totals summary
R-GCX146-cbl-00258
Increment TOTAL-HAULAGE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HAULAGE Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the equipment has haulage flag set to 'y' or manual haulage flag set to 'y', the desired outcome is that the total-haulage counter is incremented by one.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The equipment has haulage flag set to 'Y' or manual haulage flag set to 'Y'
Then
The TOTAL-HAULAGE counter is incremented by one
R-GCX146-cbl-00261
Increment TOTAL-HELD-DOCS Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-DOCS Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the equipment's manifest from station equals the manifest to station and the broker entry field is empty, the desired outcome is that the total-held-docs counter is incremented by one.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The equipment's manifest from station equals the manifest to station and the broker entry field is empty
Then
The TOTAL-HELD-DOCS counter is incremented by one
R-GCX146-cbl-00263
Calculate Running Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Running Totals' is invoked, and assuming that an equipment record has been categorized and its specific counter incremented, when the equipment processing continues to the next record, the desired outcome is that the total-equip counter is incremented by one and all category totals are maintained.
💻 Technical Criteria
Given
An equipment record has been categorized and its specific counter incremented
When
The equipment processing continues to the next record
Then
The TOTAL-EQUIP counter is incremented by one and all category totals are maintained
R-GCX146-cbl-00264
Generate Equipment Totals Summary
Process Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Totals Summary' is invoked, and assuming that all equipment records in the train have been processed and categorized, when no more equipment records remain to be processed, the desired outcome is that a summary report is generated showing total-equip, total-release, total-haulage, total-held-ccra, total-proceed, total-held-docs, and total-docs-nr counts.
💻 Technical Criteria
Given
All equipment records in the train have been processed and categorized
When
No more equipment records remain to be processed
Then
A summary report is generated showing TOTAL-EQUIP, TOTAL-RELEASE, TOTAL-HAULAGE, TOTAL-HELD-CCRA, TOTAL-PROCEED, TOTAL-HELD-DOCS, and TOTAL-DOCS-NR counts
R-GCX146-cbl-01243
Classify as HAULAGE Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Classify as HAULAGE Status', assuming that equipment does not meet other classification criteria, when manual haulage flag is set to 'y' or haulage flag is set, the desired outcome is that classify the equipment status as 'haulage' and increment total-haulage counter.
💻 Technical Criteria
EXCLUDING
Equipment does not meet other classification criteria
When
Manual haulage flag is set to 'Y' or haulage flag is set
Then
Classify the equipment status as 'HAULAGE' and increment TOTAL-HAULAGE counter
R-GCX146-cbl-01244
Update Equipment Status Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Totals' is invoked, and assuming that equipment has been classified into a specific status category, when status classification is complete, the desired outcome is that increment the appropriate total counter (total-release, total-haulage, total-proceed, total-held-ccra, total-held-docs, or total-equip) based on the classified status.
💻 Technical Criteria
Given
Equipment has been classified into a specific status category
When
Status classification is complete
Then
Increment the appropriate total counter (TOTAL-RELEASE, TOTAL-HAULAGE, TOTAL-PROCEED, TOTAL-HELD-CCRA, TOTAL-HELD-DOCS, or TOTAL-EQUIP) based on the classified status
R-GCX146-cbl-01605
Transit Status = E or Z?
Decision Rules
📊 Business Logic Narrative
When the process 'Transit Status = E or Z?' is invoked, and assuming that equipment has release status, when the transit status code is e (export) or z (export zone), the desired outcome is that the system sets the equipment status to export.
💻 Technical Criteria
Given
Equipment has RELEASE status
When
The transit status code is E (Export) or Z (Export Zone)
Then
The system sets the equipment status to EXPORT
R-GCX146-cbl-01606
Set Status to EXPORT
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to EXPORT' is invoked, and assuming that equipment has release status and transit status is e or z, when the system processes the status assignment, the desired outcome is that the equipment status is set to export.
💻 Technical Criteria
Given
Equipment has RELEASE status and transit status is E or Z
When
The system processes the status assignment
Then
The equipment status is set to EXPORT
R-GCX146-cbl-01607
S.A.R. Release?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'S.A.R. Release?', assuming that equipment has release status and transit status is not e or z, when the system checks if the release is by s.a.r., the desired outcome is that the system determines whether to set s.a.r. status or keep standard release status.
💻 Technical Criteria
EXCLUDING
Equipment has RELEASE status and transit status is not E or Z
When
The system checks if the release is by S.A.R.
Then
The system determines whether to set S.A.R. status or keep standard RELEASE status
R-GCX146-cbl-01608
Set Status to S.A.R.
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to S.A.R.' is invoked, and assuming that equipment has release status and is identified as s.a.r. release, when the system processes the s.a.r. status assignment, the desired outcome is that the equipment status is set to s.a.r..
💻 Technical Criteria
Given
Equipment has RELEASE status and is identified as S.A.R. release
When
The system processes the S.A.R. status assignment
Then
The equipment status is set to S.A.R.
R-GCX146-cbl-01609
Keep Status as RELEASE
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Keep Status as RELEASE', assuming that equipment has release status but is not export transit and not s.a.r. release, when the system processes the status assignment, the desired outcome is that the equipment status remains as release.
💻 Technical Criteria
EXCLUDING
Equipment has RELEASE status but is not export transit and not S.A.R. release
When
The system processes the status assignment
Then
The equipment status remains as RELEASE
R-GCX146-cbl-01610
Transit Status = T?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Status = T?', assuming that equipment does not have release status, when the transit status code is t (transit), the desired outcome is that the system sets the equipment status to transit.
💻 Technical Criteria
EXCLUDING
Equipment does not have RELEASE status
When
The transit status code is T (Transit)
Then
The system sets the equipment status to TRANSIT
R-GCX146-cbl-01611
Set Status to TRANSIT
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to TRANSIT' is invoked, and assuming that equipment has transit status code t, when the system processes the status assignment, the desired outcome is that the equipment status is set to transit.
💻 Technical Criteria
Given
Equipment has transit status code T
When
The system processes the status assignment
Then
The equipment status is set to TRANSIT
R-GCX146-cbl-01612
Transit Status = R?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Transit Status = R?', assuming that equipment does not have release status and transit status is not t, when the transit status code is r (return), the desired outcome is that the system sets the equipment status to return.
💻 Technical Criteria
EXCLUDING
Equipment does not have RELEASE status and transit status is not T
When
The transit status code is R (Return)
Then
The system sets the equipment status to RETURN
R-GCX146-cbl-01613
Set Status to RETURN
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to RETURN' is invoked, and assuming that equipment has transit status code r, when the system processes the status assignment, the desired outcome is that the equipment status is set to return.
💻 Technical Criteria
Given
Equipment has transit status code R
When
The system processes the status assignment
Then
The equipment status is set to RETURN
R-GCX146-cbl-01615
Update Equipment Status Record
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Record' is invoked, and assuming that a status has been determined through the status mapping logic, when the system updates the equipment record, the desired outcome is that the equipment status record is updated with the final determined status.
💻 Technical Criteria
Given
A status has been determined through the status mapping logic
When
The system updates the equipment record
Then
The equipment status record is updated with the final determined status
R-GCX146-cbl-01749
Set Status to EXPORT
Decision Rules
📊 Business Logic Narrative
When the process 'Set Status to EXPORT' is invoked, and assuming that equipment has current status of release, when the transit status is either e (export) or z (export zone), the desired outcome is that the trip sheet status is set to export.
💻 Technical Criteria
Given
Equipment has current status of RELEASE
When
The transit status is either E (Export) or Z (Export Zone)
Then
The trip sheet status is set to EXPORT
R-GCX146-cbl-01750
Set Status to S.A.R.
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to S.A.R.', assuming that equipment has current status of release and transit status is not e or z, when the equipment has s.a.r. (special administrative release) designation, the desired outcome is that the trip sheet status is set to s.a.r..
💻 Technical Criteria
EXCLUDING
Equipment has current status of RELEASE and transit status is not E or Z
When
The equipment has S.A.R. (Special Administrative Release) designation
Then
The trip sheet status is set to S.A.R.
R-GCX146-cbl-01751
Set Status to RELEASE
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to RELEASE', assuming that equipment has current status of release and transit status is not e or z, when the equipment does not have s.a.r. designation, the desired outcome is that the trip sheet status is set to release.
💻 Technical Criteria
EXCLUDING
Equipment has current status of RELEASE and transit status is not E or Z
When
The equipment does not have S.A.R. designation
Then
The trip sheet status is set to RELEASE
R-GCX146-cbl-01752
Set Status to TRANSIT
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to TRANSIT', assuming that equipment does not have current status of release, when the transit status is t (transit), the desired outcome is that the trip sheet status is set to transit.
💻 Technical Criteria
EXCLUDING
Equipment does not have current status of RELEASE
When
The transit status is T (Transit)
Then
The trip sheet status is set to TRANSIT
R-GCX146-cbl-01753
Set Status to RETURN
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to RETURN', assuming that equipment does not have current status of release and transit status is not t, when the transit status is r (return), the desired outcome is that the trip sheet status is set to return.
💻 Technical Criteria
EXCLUDING
Equipment does not have current status of RELEASE and transit status is not T
When
The transit status is R (Return)
Then
The trip sheet status is set to RETURN
R-GCX146-cbl-01754
Keep Current Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Keep Current Status', assuming that equipment does not have current status of release and transit status is not t or r, when no special status conditions are met, the desired outcome is that the trip sheet status remains as the current status.
💻 Technical Criteria
EXCLUDING
Equipment does not have current status of RELEASE and transit status is not T or R
When
No special status conditions are met
Then
The trip sheet status remains as the current status
R-GCX146-cbl-01246
Increment TOTAL-HAULAGE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HAULAGE Counter' is invoked, and assuming that an equipment item is being processed for status totals, when the equipment has haulage rights flag set or manual haulage flag is set, the desired outcome is that the total-haulage counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment item is being processed for status totals
When
The equipment has haulage rights flag set or manual haulage flag is set
Then
The TOTAL-HAULAGE counter should be incremented by 1
R-GCX146-cbl-01249
Increment TOTAL-HELD-DOCS Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-DOCS Counter' is invoked, and assuming that an equipment item is being processed for status totals, when the manifest from station equals the manifest to station and the broker entry is empty, the desired outcome is that the total-held-docs counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment item is being processed for status totals
When
The manifest from station equals the manifest to station and the broker entry is empty
Then
The TOTAL-HELD-DOCS counter should be incremented by 1
R-GCX146-cbl-01250
Increment TOTAL-TRANSIT Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-TRANSIT Counter' is invoked, and assuming that an equipment item is being processed for status totals, when the in-transit status is 't', the desired outcome is that the total-transit counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment item is being processed for status totals
When
The in-transit status is 'T'
Then
The TOTAL-TRANSIT counter should be incremented by 1
R-GCX146-cbl-01251
Increment TOTAL-EXPORT Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-EXPORT Counter' is invoked, and assuming that an equipment item is being processed for status totals, when the in-transit status is 'e' or 'z', the desired outcome is that the total-export counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment item is being processed for status totals
When
The in-transit status is 'E' or 'Z'
Then
The TOTAL-EXPORT counter should be incremented by 1
R-GCX146-cbl-01252
Increment TOTAL-RETURN Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-RETURN Counter' is invoked, and assuming that an equipment item is being processed for status totals, when the in-transit status is 'r', the desired outcome is that the total-return counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment item is being processed for status totals
When
The in-transit status is 'R'
Then
The TOTAL-RETURN counter should be incremented by 1
R-GCX146-cbl-01253
Update Equipment Status Totals
Process Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Totals' is invoked, and assuming that all status-specific counters have been evaluated for an equipment item, when the equipment processing is complete, the desired outcome is that all applicable status counters should be updated and the total equipment count should be incremented by 1.
💻 Technical Criteria
Given
All status-specific counters have been evaluated for an equipment item
When
The equipment processing is complete
Then
All applicable status counters should be updated and the total equipment count should be incremented by 1
R-GCX146-cbl-00265
Call GCCCARTP Module for Equipment Type
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCCARTP Module for Equipment Type' is invoked, and assuming that an equipment record needs to be processed for edi transmission, when the system calls the gcccartp module to determine equipment type, the desired outcome is that the equipment type is classified and returned for further processing.
💻 Technical Criteria
Given
An equipment record needs to be processed for EDI transmission
When
The system calls the GCCCARTP module to determine equipment type
Then
The equipment type is classified and returned for further processing
R-GCX146-cbl-00266
Set Container Equipment Type Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Container Equipment Type Code' is invoked, and assuming that equipment has been determined to be a container type, when the system processes the equipment for edi transmission, the desired outcome is that the equipment type code is set to container classification for edi record.
💻 Technical Criteria
Given
Equipment has been determined to be a container type
When
The system processes the equipment for EDI transmission
Then
The equipment type code is set to container classification for EDI record
R-GCX146-cbl-00267
Set Trailer Equipment Type Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Trailer Equipment Type Code' is invoked, and assuming that equipment has been determined to be a trailer type, when the system processes the equipment for edi transmission, the desired outcome is that the equipment type code is set to trailer classification for edi record.
💻 Technical Criteria
Given
Equipment has been determined to be a trailer type
When
The system processes the equipment for EDI transmission
Then
The equipment type code is set to trailer classification for EDI record
R-GCX146-cbl-00268
Set Car Equipment Type Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Car Equipment Type Code' is invoked, and assuming that equipment has been determined to be a rail car type, when the system processes the equipment for edi transmission, the desired outcome is that the equipment type code is set to car classification for edi record.
💻 Technical Criteria
Given
Equipment has been determined to be a rail car type
When
The system processes the equipment for EDI transmission
Then
The equipment type code is set to car classification for EDI record
R-GCX146-cbl-00269
Assign Load/Empty Status Indicator
Decision Rules
📊 Business Logic Narrative
When the process 'Assign Load/Empty Status Indicator' is invoked, and assuming that equipment type has been determined for edi processing, when the system evaluates the cargo content status of the equipment, the desired outcome is that the load/empty status indicator is assigned to reflect whether equipment is loaded or empty.
💻 Technical Criteria
Given
Equipment type has been determined for EDI processing
When
The system evaluates the cargo content status of the equipment
Then
The load/empty status indicator is assigned to reflect whether equipment is loaded or empty
R-GCX146-cbl-00272
Validate EDI Record Completeness
Validation Rules
📊 Business Logic Narrative
When the process 'Validate EDI Record Completeness' is invoked, and assuming that an edi equipment record has been built, when the system validates the record for completeness, the desired outcome is that the record is confirmed to contain all mandatory data elements required for customs transmission.
💻 Technical Criteria
Given
An EDI equipment record has been built
When
The system validates the record for completeness
Then
The record is confirmed to contain all mandatory data elements required for customs transmission
R-GCX146-cbl-00273
Queue EDI Record for Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Queue EDI Record for Transmission' is invoked, and assuming that an edi equipment record has been validated as complete, when the system processes the valid record, the desired outcome is that the edi record is queued for transmission to customs.
💻 Technical Criteria
Given
An EDI equipment record has been validated as complete
When
The system processes the valid record
Then
The EDI record is queued for transmission to customs
R-GCX146-cbl-00274
Prepare Next Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Next Equipment Record' is invoked, and assuming that current equipment record has been queued for edi transmission, when the system continues processing the train consist, the desired outcome is that the next equipment record is prepared for edi processing.
💻 Technical Criteria
Given
Current equipment record has been queued for EDI transmission
When
The system continues processing the train consist
Then
The next equipment record is prepared for EDI processing
R-GCX146-cbl-00275
More Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment?' is invoked, and assuming that current equipment record has been processed, when the system checks for remaining equipment in the train consist, the desired outcome is that processing continues if more equipment exists or proceeds to transmission if complete.
💻 Technical Criteria
Given
Current equipment record has been processed
When
The system checks for remaining equipment in the train consist
Then
Processing continues if more equipment exists or proceeds to transmission if complete
R-GCX146-cbl-00276
Transmit EDI Data to Customs
Action Rules
📊 Business Logic Narrative
When the process 'Transmit EDI Data to Customs' is invoked, and assuming that all equipment records have been processed and queued, when the system initiates edi transmission to customs, the desired outcome is that all queued edi records are transmitted to customs authorities.
💻 Technical Criteria
Given
All equipment records have been processed and queued
When
The system initiates EDI transmission to customs
Then
All queued EDI records are transmitted to customs authorities
R-GCX146-cbl-00280
Check Report Size
Process Rules
📊 Business Logic Narrative
When the process 'Check Report Size' is invoked, and assuming that an aei report has been generated with equipment identification data, when the system prepares to send the report via email, the desired outcome is that the system counts the total number of lines in the report to determine if continuation logic is needed.
💻 Technical Criteria
Given
An AEI report has been generated with equipment identification data
When
The system prepares to send the report via email
Then
The system counts the total number of lines in the report to determine if continuation logic is needed
R-GCX146-cbl-00314
Process Equipment List
Process Rules
📊 Business Logic Narrative
When the process 'Process Equipment List' is invoked, and assuming that station details have been added to the trip sheet, when equipment processing begins, the desired outcome is that each equipment piece is processed sequentially for inclusion in the trip sheet.
💻 Technical Criteria
Given
Station details have been added to the trip sheet
When
Equipment processing begins
Then
Each equipment piece is processed sequentially for inclusion in the trip sheet
R-GCX146-cbl-00315
Format Equipment Entry
Computation Rules
📊 Business Logic Narrative
When the process 'Format Equipment Entry' is invoked, and assuming that an equipment piece is being processed, when equipment entry formatting is required, the desired outcome is that equipment id is extracted, car number is formatted, and load/empty status is determined.
💻 Technical Criteria
Given
An equipment piece is being processed
When
Equipment entry formatting is required
Then
Equipment ID is extracted, car number is formatted, and load/empty status is determined
R-GCX146-cbl-00316
Determine Equipment Type
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Equipment Type' is invoked, and assuming that equipment entry has been formatted, when equipment type needs to be determined, the desired outcome is that car type is analyzed to classify as unit, van, sbu, or regular car for appropriate processing.
💻 Technical Criteria
Given
Equipment entry has been formatted
When
Equipment type needs to be determined
Then
Car type is analyzed to classify as Unit, Van, SBU, or regular car for appropriate processing
R-GCX146-cbl-00317
Container on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'Container on Flat Car?' is invoked, and assuming that equipment type has been determined, when container processing check is performed, the desired outcome is that if equipment is a flat car with containers, container processing is initiated, otherwise standard equipment processing continues.
💻 Technical Criteria
Given
Equipment type has been determined
When
Container processing check is performed
Then
If equipment is a flat car with containers, container processing is initiated, otherwise standard equipment processing continues
R-GCX146-cbl-00318
Process Individual Container
Process Rules
📊 Business Logic Narrative
When the process 'Process Individual Container' is invoked, and assuming that equipment is identified as a flat car with containers, when container processing is initiated, the desired outcome is that each container is processed individually with proper identification and cross-reference handling.
💻 Technical Criteria
Given
Equipment is identified as a flat car with containers
When
Container processing is initiated
Then
Each container is processed individually with proper identification and cross-reference handling
R-GCX146-cbl-00319
Format Container Details
Computation Rules
📊 Business Logic Narrative
When the process 'Format Container Details' is invoked, and assuming that individual container is being processed, when container details need formatting, the desired outcome is that container id is formatted using 12-character format and container details are prepared for display.
💻 Technical Criteria
Given
Individual container is being processed
When
Container details need formatting
Then
Container ID is formatted using 12-character format and container details are prepared for display
R-GCX146-cbl-00320
Add Equipment Car Type Description
Action Rules
📊 Business Logic Narrative
When the process 'Add Equipment Car Type Description' is invoked, and assuming that equipment or container details have been formatted, when car type description is needed, the desired outcome is that car type description is retrieved from the vi table and added to the equipment information.
💻 Technical Criteria
Given
Equipment or container details have been formatted
When
Car type description is needed
Then
Car type description is retrieved from the VI table and added to the equipment information
R-GCX146-cbl-00322
More Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment?' is invoked, and assuming that current equipment status has been assigned, when equipment processing continuation check is performed, the desired outcome is that if more equipment exists, processing returns to equipment list processing, otherwise equipment totals calculation begins.
💻 Technical Criteria
Given
Current equipment status has been assigned
When
Equipment processing continuation check is performed
Then
If more equipment exists, processing returns to equipment list processing, otherwise equipment totals calculation begins
R-GCX146-cbl-00323
Calculate Equipment Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Equipment Totals' is invoked, and assuming that all equipment has been processed, when equipment totals calculation is initiated, the desired outcome is that totals are calculated for released equipment (release/csa-dlv status), transit equipment (t status), held equipment (hold/agi-hold status), and proceeding equipment (different from/to stations).
💻 Technical Criteria
Given
All equipment has been processed
When
Equipment totals calculation is initiated
Then
Totals are calculated for released equipment (RELEASE/CSA-DLV status), transit equipment (T status), held equipment (HOLD/AGI-HOLD status), and proceeding equipment (different from/to stations)
R-GCX146-cbl-00324
Add Summary Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Add Summary Totals' is invoked, and assuming that equipment totals have been calculated, when summary totals need to be added to the trip sheet, the desired outcome is that total counts for each equipment category are formatted and added to the trip sheet with appropriate labels.
💻 Technical Criteria
Given
Equipment totals have been calculated
When
Summary totals need to be added to the trip sheet
Then
Total counts for each equipment category are formatted and added to the trip sheet with appropriate labels
R-GCX146-cbl-01264
Initialize Equipment Count Fields
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Equipment Count Fields' is invoked, and assuming that a trip sheet report includes equipment totals, when the system initializes the totals section, the desired outcome is that all equipment count fields are set to zero and status category headers are established.
💻 Technical Criteria
Given
A trip sheet report includes equipment totals
When
The system initializes the totals section
Then
All equipment count fields are set to zero and status category headers are established
R-GCX146-cbl-01265
Determine Equipment Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Determine Equipment Type' is invoked, and assuming that an equipment record is being processed for formatting, when the equipment is identified as a container type, the desired outcome is that the system sets the equipment type code to 'c' for container and applies container-specific formatting rules.
💻 Technical Criteria
Given
An equipment record is being processed for formatting
When
The equipment is identified as a container type
Then
The system sets the equipment type code to 'C' for container and applies container-specific formatting rules
R-GCX146-cbl-01266
Determine Equipment Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Determine Equipment Type' is invoked, and assuming that an equipment record is being processed for formatting, when the equipment is identified as a trailer type, the desired outcome is that the system sets the equipment type code to 't' for trailer and applies trailer-specific formatting rules.
💻 Technical Criteria
Given
An equipment record is being processed for formatting
When
The equipment is identified as a trailer type
Then
The system sets the equipment type code to 'T' for trailer and applies trailer-specific formatting rules
R-GCX146-cbl-01267
Determine Equipment Type
Definitional Rules
📊 Business Logic Narrative
When the process 'Determine Equipment Type' is invoked, and assuming that an equipment record is being processed for formatting, when the equipment is identified as a rail car type, the desired outcome is that the system sets the equipment type code to 'r' for rail car and applies rail car-specific formatting rules.
💻 Technical Criteria
Given
An equipment record is being processed for formatting
When
The equipment is identified as a rail car type
Then
The system sets the equipment type code to 'R' for rail car and applies rail car-specific formatting rules
R-GCX146-cbl-01268
Format Container Entry
Process Rules
📊 Business Logic Narrative
When the process 'Format Container Entry' is invoked, and assuming that an equipment record has been classified as container type, when the container id needs to be formatted for display, the desired outcome is that the system applies container-specific id formatting using gcccarfm utility to create 12-character standardized format.
💻 Technical Criteria
Given
An equipment record has been classified as container type
When
The container ID needs to be formatted for display
Then
The system applies container-specific ID formatting using GCCCARFM utility to create 12-character standardized format
R-GCX146-cbl-01269
Format Trailer Entry
Process Rules
📊 Business Logic Narrative
When the process 'Format Trailer Entry' is invoked, and assuming that an equipment record has been classified as trailer type, when the trailer id needs to be formatted for display, the desired outcome is that the system applies trailer-specific id formatting rules to create standardized trailer identification format.
💻 Technical Criteria
Given
An equipment record has been classified as trailer type
When
The trailer ID needs to be formatted for display
Then
The system applies trailer-specific ID formatting rules to create standardized trailer identification format
R-GCX146-cbl-01270
Format Rail Car Entry
Process Rules
📊 Business Logic Narrative
When the process 'Format Rail Car Entry' is invoked, and assuming that an equipment record has been classified as rail car type, when the rail car id needs to be formatted for display, the desired outcome is that the system applies rail car-specific id formatting rules to create standardized car number format.
💻 Technical Criteria
Given
An equipment record has been classified as rail car type
When
The rail car ID needs to be formatted for display
Then
The system applies rail car-specific ID formatting rules to create standardized car number format
R-GCX146-cbl-01271
Determine Load/Empty Status
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Load/Empty Status' is invoked, and assuming that an equipment record is being processed with load/empty indicator available, when the system evaluates the load status indicator field, the desired outcome is that the system determines if equipment is loaded or empty and sets corresponding status flags for further processing.
💻 Technical Criteria
Given
An equipment record is being processed with load/empty indicator available
When
The system evaluates the load status indicator field
Then
The system determines if equipment is loaded or empty and sets corresponding status flags for further processing
R-GCX146-cbl-01272
Set LOADED Status
Definitional Rules
📊 Business Logic Narrative
When the process 'Set LOADED Status' is invoked, and assuming that equipment has been evaluated for load status, when the equipment is determined to be carrying cargo (loaded), the desired outcome is that the system sets the equipment status to 'loaded' and applies loaded equipment processing rules.
💻 Technical Criteria
Given
Equipment has been evaluated for load status
When
The equipment is determined to be carrying cargo (loaded)
Then
The system sets the equipment status to 'LOADED' and applies loaded equipment processing rules
R-GCX146-cbl-01273
Set EMPTY Status
Definitional Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set EMPTY Status', assuming that equipment has been evaluated for load status, when the equipment is determined to be not carrying cargo (empty), the desired outcome is that the system sets the equipment status to 'empty' and applies empty equipment processing rules.
💻 Technical Criteria
EXCLUDING
Equipment has been evaluated for load status
When
The equipment is determined to be not carrying cargo (empty)
Then
The system sets the equipment status to 'EMPTY' and applies empty equipment processing rules
R-GCX146-cbl-01274
Format Equipment ID
Validation Rules
📊 Business Logic Narrative
When the process 'Format Equipment ID' is invoked, and assuming that equipment has been classified by type and load status, when the equipment id needs to be formatted for processing, the desired outcome is that the system removes spaces from the equipment id and applies standardized formatting rules based on equipment type.
💻 Technical Criteria
Given
Equipment has been classified by type and load status
When
The equipment ID needs to be formatted for processing
Then
The system removes spaces from the equipment ID and applies standardized formatting rules based on equipment type
R-GCX146-cbl-01275
Apply Car ID Formatting
Process Rules
📊 Business Logic Narrative
When the process 'Apply Car ID Formatting' is invoked, and assuming that equipment id has been initially formatted, when car-specific formatting is required, the desired outcome is that the system applies car id formatting rules to create standardized car number representation with proper spacing and character positioning.
💻 Technical Criteria
Given
Equipment ID has been initially formatted
When
Car-specific formatting is required
Then
The system applies car ID formatting rules to create standardized car number representation with proper spacing and character positioning
R-GCX146-cbl-01276
Set IDLER Message
Definitional Rules
📊 Business Logic Narrative
When the process 'Set IDLER Message' is invoked, and assuming that equipment has been formatted and classified, when the equipment is identified as idler equipment (non-revenue generating), the desired outcome is that the system sets the equipment message to 'idler' to indicate special handling requirements.
💻 Technical Criteria
Given
Equipment has been formatted and classified
When
The equipment is identified as idler equipment (non-revenue generating)
Then
The system sets the equipment message to 'IDLER' to indicate special handling requirements
R-GCX146-cbl-01277
Set UNIT Message
Definitional Rules
📊 Business Logic Narrative
When the process 'Set UNIT Message' is invoked, and assuming that equipment has been formatted and classified, when the equipment is identified as unit equipment (part of unit train), the desired outcome is that the system sets the equipment message to 'unit' to indicate unit train handling requirements.
💻 Technical Criteria
Given
Equipment has been formatted and classified
When
The equipment is identified as unit equipment (part of unit train)
Then
The system sets the equipment message to 'UNIT' to indicate unit train handling requirements
R-GCX146-cbl-01278
Set Standard Message
Definitional Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Standard Message', assuming that equipment has been formatted and classified, when the equipment is not identified as idler or unit equipment, the desired outcome is that the system sets a standard equipment message for normal processing and handling.
💻 Technical Criteria
EXCLUDING
Equipment has been formatted and classified
When
The equipment is not identified as idler or unit equipment
Then
The system sets a standard equipment message for normal processing and handling
R-GCX146-cbl-01279
Build Equipment Entry Line
Process Rules
📊 Business Logic Narrative
When the process 'Build Equipment Entry Line' is invoked, and assuming that equipment has been classified, formatted, and assigned appropriate status messages, when a complete equipment entry line needs to be constructed, the desired outcome is that the system combines equipment id, type code, load status, and status messages into a single formatted equipment entry line.
💻 Technical Criteria
Given
Equipment has been classified, formatted, and assigned appropriate status messages
When
A complete equipment entry line needs to be constructed
Then
The system combines equipment ID, type code, load status, and status messages into a single formatted equipment entry line
R-GCX146-cbl-01280
Add to Equipment List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Equipment List' is invoked, and assuming that a complete equipment entry line has been constructed, when the equipment entry needs to be added to the train's equipment list, the desired outcome is that the system adds the formatted equipment entry to the master equipment list maintaining proper sequence and organization.
💻 Technical Criteria
Given
A complete equipment entry line has been constructed
When
The equipment entry needs to be added to the train's equipment list
Then
The system adds the formatted equipment entry to the master equipment list maintaining proper sequence and organization
R-GCX146-cbl-01477
Is Container Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Container Equipment?' is invoked, and assuming that equipment record with car type and container indicators are available, when equipment is identified as container equipment, the desired outcome is that system checks container load status and assigns container-specific type code.
💻 Technical Criteria
Given
Equipment record with car type and container indicators are available
When
Equipment is identified as container equipment
Then
System checks container load status and assigns container-specific type code
R-GCX146-cbl-01478
Container Loaded?
Decision Rules
📊 Business Logic Narrative
When the process 'Container Loaded?' is invoked, and assuming that equipment is confirmed as container equipment, when container load status indicates loaded condition, the desired outcome is that system assigns loaded container type code.
💻 Technical Criteria
Given
Equipment is confirmed as container equipment
When
Container load status indicates loaded condition
Then
System assigns loaded container type code
R-GCX146-cbl-01479
Assign Empty Container Code
Decision Rules
📊 Business Logic Narrative
When the process 'Assign Empty Container Code' is invoked, and assuming that equipment is confirmed as container equipment, when container load status indicates empty condition, the desired outcome is that system assigns empty container type code.
💻 Technical Criteria
Given
Equipment is confirmed as container equipment
When
Container load status indicates empty condition
Then
System assigns empty container type code
R-GCX146-cbl-01480
Is Trailer Equipment?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Is Trailer Equipment?', assuming that equipment is not container equipment, when equipment type indicators are evaluated for trailer classification, the desired outcome is that system identifies equipment as trailer or proceeds to rail car classification.
💻 Technical Criteria
EXCLUDING
Equipment is not container equipment
When
Equipment type indicators are evaluated for trailer classification
Then
System identifies equipment as trailer or proceeds to rail car classification
R-GCX146-cbl-01481
Trailer Loaded?
Decision Rules
📊 Business Logic Narrative
When the process 'Trailer Loaded?' is invoked, and assuming that equipment is confirmed as trailer equipment, when trailer load status indicates loaded condition, the desired outcome is that system assigns loaded trailer type code.
💻 Technical Criteria
Given
Equipment is confirmed as trailer equipment
When
Trailer load status indicates loaded condition
Then
System assigns loaded trailer type code
R-GCX146-cbl-01482
Assign Empty Trailer Code
Decision Rules
📊 Business Logic Narrative
When the process 'Assign Empty Trailer Code' is invoked, and assuming that equipment is confirmed as trailer equipment, when trailer load status indicates empty condition, the desired outcome is that system assigns empty trailer type code.
💻 Technical Criteria
Given
Equipment is confirmed as trailer equipment
When
Trailer load status indicates empty condition
Then
System assigns empty trailer type code
R-GCX146-cbl-01483
Is Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Flat Car?' is invoked, and assuming that equipment is rail car type (not container or trailer), when car type indicates flat car classification, the desired outcome is that system assigns flat car type code.
💻 Technical Criteria
Given
Equipment is rail car type (not container or trailer)
When
Car type indicates flat car classification
Then
System assigns flat car type code
R-GCX146-cbl-01484
Is Tank Car?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Is Tank Car?', assuming that equipment is rail car type and not a flat car, when car type indicates tank car classification, the desired outcome is that system assigns tank car type code.
💻 Technical Criteria
EXCLUDING
Equipment is rail car type and not a flat car
When
Car type indicates tank car classification
Then
System assigns tank car type code
R-GCX146-cbl-01485
Is Box Car?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Is Box Car?', assuming that equipment is rail car type and not flat car or tank car, when car type indicates box car classification, the desired outcome is that system assigns box car type code.
💻 Technical Criteria
EXCLUDING
Equipment is rail car type and not flat car or tank car
When
Car type indicates box car classification
Then
System assigns box car type code
R-GCX146-cbl-01486
Assign General Car Code
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Assign General Car Code', assuming that equipment is rail car type, when car type does not match flat car, tank car, or box car classifications, the desired outcome is that system assigns general car type code.
💻 Technical Criteria
EXCLUDING
Equipment is rail car type
When
Car type does not match flat car, tank car, or box car classifications
Then
System assigns general car type code
R-GCX146-cbl-01487
Equipment Loaded?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Loaded?' is invoked, and assuming that equipment type code has been assigned, when equipment load status is evaluated, the desired outcome is that system sets appropriate load status flag (loaded or empty).
💻 Technical Criteria
Given
Equipment type code has been assigned
When
Equipment load status is evaluated
Then
System sets appropriate load status flag (loaded or empty)
R-GCX146-cbl-01488
Set Load Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Load Status Flag' is invoked, and assuming that equipment load status has been determined, when equipment is confirmed as loaded, the desired outcome is that system sets load status flag to indicate loaded condition.
💻 Technical Criteria
Given
Equipment load status has been determined
When
Equipment is confirmed as loaded
Then
System sets load status flag to indicate loaded condition
R-GCX146-cbl-01489
Set Empty Status Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Empty Status Flag' is invoked, and assuming that equipment load status has been determined, when equipment is confirmed as empty, the desired outcome is that system sets empty status flag to indicate empty condition.
💻 Technical Criteria
Given
Equipment load status has been determined
When
Equipment is confirmed as empty
Then
System sets empty status flag to indicate empty condition
R-GCX146-cbl-01618
Check Container Load Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Container Load Status' is invoked, and assuming that equipment record exists with load/empty indicator, when processing equipment for container identification, the desired outcome is that system categorizes equipment as loaded (l) or empty (e) based on the load/empty indicator field.
💻 Technical Criteria
Given
Equipment record exists with load/empty indicator
When
Processing equipment for container identification
Then
System categorizes equipment as loaded (L) or empty (E) based on the load/empty indicator field
R-GCX146-cbl-01620
Check Container Load Status
Process Rules
📊 Business Logic Narrative
When the process 'Check Container Load Status' is invoked, and assuming that flat car equipment record with potential multiple containers, when processing container load status, the desired outcome is that system extracts and processes each container id from cross-reference records associated with the flat car.
💻 Technical Criteria
Given
Flat car equipment record with potential multiple containers
When
Processing container load status
Then
System extracts and processes each container ID from cross-reference records associated with the flat car
R-GCX146-cbl-01629
Origin = Destination?
Decision Rules
📊 Business Logic Narrative
When the process 'Origin = Destination?' is invoked, and assuming that cargo origin and destination have been analyzed, when system compares origin location with destination location, the desired outcome is that load status flag is set to empty if origin equals destination, otherwise set to load.
💻 Technical Criteria
Given
Cargo origin and destination have been analyzed
When
System compares origin location with destination location
Then
Load status flag is set to Empty if origin equals destination, otherwise set to Load
R-GCX146-cbl-01630
Set Load Status Flag = Empty
Action Rules
📊 Business Logic Narrative
When the process 'Set Load Status Flag = Empty' is invoked, and assuming that cargo origin equals destination, when system assigns load status flag, the desired outcome is that load status flag is set to empty.
💻 Technical Criteria
Given
Cargo origin equals destination
When
System assigns load status flag
Then
Load status flag is set to Empty
R-GCX146-cbl-01631
Set Load Status Flag = Load
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Load Status Flag = Load', assuming that cargo origin does not equal destination, when system assigns load status flag, the desired outcome is that load status flag is set to load.
💻 Technical Criteria
EXCLUDING
Cargo origin does not equal destination
When
System assigns load status flag
Then
Load status flag is set to Load
R-GCX146-cbl-01634
Update Equipment Load/Empty Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Load/Empty Status' is invoked, and assuming that load status is determined as valid, when system updates equipment load/empty status, the desired outcome is that equipment record is updated with the validated load/empty status.
💻 Technical Criteria
Given
Load status is determined as valid
When
System updates equipment load/empty status
Then
Equipment record is updated with the validated load/empty status
R-GCX146-cbl-01636
Continue Equipment Processing
Process Rules
📊 Business Logic Narrative
When the process 'Continue Equipment Processing' is invoked, and assuming that load status validation is complete (either successful update or error set), when system proceeds to next processing phase, the desired outcome is that equipment processing continues to subsequent validation or processing steps.
💻 Technical Criteria
Given
Load status validation is complete (either successful update or error set)
When
System proceeds to next processing phase
Then
Equipment processing continues to subsequent validation or processing steps
R-GCX146-cbl-01761
Origin/Destination Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Origin/Destination Valid?' is invoked, and assuming that origin and destination station codes have been extracted and format validated, when the system evaluates the overall validity of origin and destination information, the desired outcome is that the system should confirm both codes are valid and complete for cargo processing or route to default handling.
💻 Technical Criteria
Given
Origin and destination station codes have been extracted and format validated
When
The system evaluates the overall validity of origin and destination information
Then
The system should confirm both codes are valid and complete for cargo processing or route to default handling
R-GCX146-cbl-01763
Set Equipment Status Flags
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment Status Flags' is invoked, and assuming that load/empty status has been determined for cargo equipment, when the system sets equipment status flags, the desired outcome is that the system should assign relevant status indicators that reflect the equipment's current operational state.
💻 Technical Criteria
Given
Load/empty status has been determined for cargo equipment
When
The system sets equipment status flags
Then
The system should assign relevant status indicators that reflect the equipment's current operational state
R-GCX146-cbl-01764
Update Cargo Classification
Process Rules
📊 Business Logic Narrative
When the process 'Update Cargo Classification' is invoked, and assuming that equipment status flags have been set based on origin/destination analysis, when the system updates cargo classification, the desired outcome is that the system should assign appropriate cargo classification categories based on the complete analysis results.
💻 Technical Criteria
Given
Equipment status flags have been set based on origin/destination analysis
When
The system updates cargo classification
Then
The system should assign appropriate cargo classification categories based on the complete analysis results
R-GCX146-cbl-01281
Initialize Total Counters
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Total Counters' is invoked, and assuming that a summary totals generation process is starting, when the system begins calculating equipment totals, the desired outcome is that all total counters (total-equip, total-release, total-haulage, total-held-ccra, total-proceed, total-held-docs, total-docs-nr) are set to zero.
💻 Technical Criteria
Given
A summary totals generation process is starting
When
The system begins calculating equipment totals
Then
All total counters (TOTAL-EQUIP, TOTAL-RELEASE, TOTAL-HAULAGE, TOTAL-HELD-CCRA, TOTAL-PROCEED, TOTAL-HELD-DOCS, TOTAL-DOCS-NR) are set to zero
R-GCX146-cbl-01282
Calculate Released Cargo Total
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Released Cargo Total' is invoked, and assuming that equipment records with various status values exist, when the system processes equipment with status equal to 'release' or 'csa-dlv', the desired outcome is that the total-release counter is incremented by one for each qualifying equipment piece.
💻 Technical Criteria
Given
Equipment records with various status values exist
When
The system processes equipment with status equal to 'RELEASE' or 'CSA-DLV'
Then
The TOTAL-RELEASE counter is incremented by one for each qualifying equipment piece
R-GCX146-cbl-01283
Calculate Haulage Rights Total
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Haulage Rights Total' is invoked, and assuming that equipment records with haulage and manual haulage indicators exist, when the system processes equipment where haulage flag is 'y' or manual haulage flag is 'y', the desired outcome is that the total-haulage counter is incremented by one for each qualifying equipment piece.
💻 Technical Criteria
Given
Equipment records with haulage and manual haulage indicators exist
When
The system processes equipment where haulage flag is 'Y' or manual haulage flag is 'Y'
Then
The TOTAL-HAULAGE counter is incremented by one for each qualifying equipment piece
R-GCX146-cbl-01284
Calculate CCRA Held Total
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate CCRA Held Total' is invoked, and assuming that equipment records with various hold status values exist, when the system processes equipment with status equal to 'hold' or 'agi-hold', the desired outcome is that the total-held-ccra counter is incremented by one for each qualifying equipment piece.
💻 Technical Criteria
Given
Equipment records with various hold status values exist
When
The system processes equipment with status equal to 'HOLD' or 'AGI-HOLD'
Then
The TOTAL-HELD-CCRA counter is incremented by one for each qualifying equipment piece
R-GCX146-cbl-01285
Calculate Proceeding Cargo Total
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Calculate Proceeding Cargo Total', assuming that equipment records with manifest from/to stations and status information exist, when the system processes equipment with status 'return' or where manifest from station differs from manifest to station and status is not error, reject, or deleted, the desired outcome is that the total-proceed counter is incremented by one for each qualifying equipment piece.
💻 Technical Criteria
EXCLUDING
Equipment records with manifest from/to stations and status information exist
When
The system processes equipment with status 'RETURN' or where manifest from station differs from manifest to station and status is not error, reject, or deleted
Then
The TOTAL-PROCEED counter is incremented by one for each qualifying equipment piece
R-GCX146-cbl-01286
Calculate Documentation Held Total
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Documentation Held Total' is invoked, and assuming that equipment records with manifest station information and broker entry data exist, when the system processes equipment where manifest from station equals manifest to station and broker entry is empty or spaces, the desired outcome is that the total-held-docs counter is incremented by one for each qualifying equipment piece.
💻 Technical Criteria
Given
Equipment records with manifest station information and broker entry data exist
When
The system processes equipment where manifest from station equals manifest to station and broker entry is empty or spaces
Then
The TOTAL-HELD-DOCS counter is incremented by one for each qualifying equipment piece
R-GCX146-cbl-01288
Generate Equipment Summary Lines
Process Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Summary Lines' is invoked, and assuming that formatted total values for all equipment categories exist, when the system generates summary report lines, the desired outcome is that summary lines are created showing 'total equipment', 'total release', 'total haulage', 'total held ccra', 'total proceed', 'total held docs', and 'total docs n/r' with their respective counts.
💻 Technical Criteria
Given
Formatted total values for all equipment categories exist
When
The system generates summary report lines
Then
Summary lines are created showing 'TOTAL EQUIPMENT', 'TOTAL RELEASE', 'TOTAL HAULAGE', 'TOTAL HELD CCRA', 'TOTAL PROCEED', 'TOTAL HELD DOCS', and 'TOTAL DOCS N/R' with their respective counts
R-GCX146-cbl-01289
Add Totals to Trip Sheet
Process Rules
📊 Business Logic Narrative
When the process 'Add Totals to Trip Sheet' is invoked, and assuming that a trip sheet report is being generated for an add operation and equipment summary lines exist, when the system adds totals to the trip sheet, the desired outcome is that equipment summary lines are appended to the trip sheet report with proper formatting and line spacing.
💻 Technical Criteria
Given
A trip sheet report is being generated for an ADD operation and equipment summary lines exist
When
The system adds totals to the trip sheet
Then
Equipment summary lines are appended to the trip sheet report with proper formatting and line spacing
R-GCX146-cbl-01290
Add Totals to Status Report
Process Rules
📊 Business Logic Narrative
When the process 'Add Totals to Status Report' is invoked, and assuming that a status report is being generated for a verify operation and equipment summary lines exist, when the system adds totals to the status report, the desired outcome is that equipment summary lines are appended to the status report with proper formatting and line spacing.
💻 Technical Criteria
Given
A status report is being generated for a VERIFY operation and equipment summary lines exist
When
The system adds totals to the status report
Then
Equipment summary lines are appended to the status report with proper formatting and line spacing
R-GCX146-cbl-01291
Validate Total Calculations
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Total Calculations' is invoked, and assuming that all equipment totals have been calculated, when the system validates the total calculations, the desired outcome is that the sum of all category totals (release + haulage + held-ccra + proceed + held-docs + docs-nr) equals or is less than total-equip.
💻 Technical Criteria
Given
All equipment totals have been calculated
When
The system validates the total calculations
Then
The sum of all category totals (RELEASE + HAULAGE + HELD-CCRA + PROCEED + HELD-DOCS + DOCS-NR) equals or is less than TOTAL-EQUIP
R-GCX146-cbl-00327
Initialize Status Report Header
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Status Report Header' is invoked, and assuming that a verify operation is being processed for a train, when the status report generation begins, the desired outcome is that the report header is initialized with train id, date, time, and column headers for equipment status display.
💻 Technical Criteria
Given
A VERIFY operation is being processed for a train
When
The status report generation begins
Then
The report header is initialized with train ID, date, time, and column headers for equipment status display
R-GCX146-cbl-00329
Populate Manifest Station Names
Action Rules
📊 Business Logic Narrative
When the process 'Populate Manifest Station Names' is invoked, and assuming that equipment has manifest from and to station codes, when processing equipment for status report, the desired outcome is that station names are retrieved and populated for manifest from and to locations using station code lookup.
💻 Technical Criteria
Given
Equipment has manifest from and to station codes
When
Processing equipment for status report
Then
Station names are retrieved and populated for manifest from and to locations using station code lookup
R-GCX146-cbl-00330
Equipment Has Transit Status?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Has Transit Status?' is invoked, and assuming that equipment has an in-transit status indicator, when the in-transit status is 't', the desired outcome is that the equipment status is set to 'transit' for display purposes.
💻 Technical Criteria
Given
Equipment has an in-transit status indicator
When
The in-transit status is 'T'
Then
The equipment status is set to 'TRANSIT' for display purposes
R-GCX146-cbl-00331
Keep Original Status
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Keep Original Status', assuming that equipment has an in-transit status indicator, when the in-transit status is not 't', the desired outcome is that the original equipment status is preserved for display.
💻 Technical Criteria
EXCLUDING
Equipment has an in-transit status indicator
When
The in-transit status is not 'T'
Then
The original equipment status is preserved for display
R-GCX146-cbl-00332
Process US Status Messages
Process Rules
📊 Business Logic Narrative
When the process 'Process US Status Messages' is invoked, and assuming that equipment has us customs status messages available, when processing status messages for the report, the desired outcome is that us status messages are processed and included in the report up to a maximum of 90 lines.
💻 Technical Criteria
Given
Equipment has US customs status messages available
When
Processing status messages for the report
Then
US status messages are processed and included in the report up to a maximum of 90 lines
R-GCX146-cbl-00333
Line Limit Reached?
Validation Rules
📊 Business Logic Narrative
When the process 'Line Limit Reached?' is invoked, and assuming that status report is being generated with multiple equipment entries, when the maximum number of report lines is reached, the desired outcome is that the max-lines-reached flag is set to prevent report overflow.
💻 Technical Criteria
Given
Status report is being generated with multiple equipment entries
When
The maximum number of report lines is reached
Then
The MAX-LINES-REACHED flag is set to prevent report overflow
R-GCX146-cbl-00334
Calculate Total Released Equipment
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Total Released Equipment' is invoked, and assuming that equipment records are being processed for status totals, when equipment has status 'release' or 'csa-dlv', the desired outcome is that the total-release counter is incremented by one.
💻 Technical Criteria
Given
Equipment records are being processed for status totals
When
Equipment has status 'RELEASE' or 'CSA-DLV'
Then
The TOTAL-RELEASE counter is incremented by one
R-GCX146-cbl-00335
Calculate Total Haulage Equipment
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Total Haulage Equipment' is invoked, and assuming that equipment records are being processed for status totals, when equipment has haulage flag set or manual haulage flag set, the desired outcome is that the total-haulage counter is incremented by one.
💻 Technical Criteria
Given
Equipment records are being processed for status totals
When
Equipment has haulage flag set or manual haulage flag set
Then
The TOTAL-HAULAGE counter is incremented by one
R-GCX146-cbl-00336
Calculate Total Held by CCRA
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Total Held by CCRA' is invoked, and assuming that equipment records are being processed for status totals, when equipment has status 'hold' or 'agi-hold', the desired outcome is that the total-held-ccra counter is incremented by one.
💻 Technical Criteria
Given
Equipment records are being processed for status totals
When
Equipment has status 'HOLD' or 'AGI-HOLD'
Then
The TOTAL-HELD-CCRA counter is incremented by one
R-GCX146-cbl-00337
Calculate Total Proceeding Equipment
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Calculate Total Proceeding Equipment', assuming that equipment records are being processed for status totals, when equipment has status 'return' or manifest from station differs from manifest to station and status is not error, reject, or deleted, the desired outcome is that the total-proceed counter is incremented by one.
💻 Technical Criteria
EXCLUDING
Equipment records are being processed for status totals
When
Equipment has status 'RETURN' or manifest from station differs from manifest to station and status is not error, reject, or deleted
Then
The TOTAL-PROCEED counter is incremented by one
R-GCX146-cbl-00338
Calculate Total Held for Documentation
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Total Held for Documentation' is invoked, and assuming that equipment records are being processed for status totals, when equipment manifest from station equals manifest to station and broker entry is empty, the desired outcome is that the total-held-docs counter is incremented by one.
💻 Technical Criteria
Given
Equipment records are being processed for status totals
When
Equipment manifest from station equals manifest to station and broker entry is empty
Then
The TOTAL-HELD-DOCS counter is incremented by one
R-GCX146-cbl-00339
Format Status Report Lines
Process Rules
📊 Business Logic Narrative
When the process 'Format Status Report Lines' is invoked, and assuming that equipment status information has been processed, when formatting the status report, the desired outcome is that equipment details are formatted into structured report lines with proper spacing and alignment.
💻 Technical Criteria
Given
Equipment status information has been processed
When
Formatting the status report
Then
Equipment details are formatted into structured report lines with proper spacing and alignment
R-GCX146-cbl-00341
Generate Final Status Report
Process Rules
📊 Business Logic Narrative
When the process 'Generate Final Status Report' is invoked, and assuming that all equipment has been processed and totals calculated, when finalizing the status report, the desired outcome is that the complete status report is generated with equipment details, status totals, and summary information.
💻 Technical Criteria
Given
All equipment has been processed and totals calculated
When
Finalizing the status report
Then
The complete status report is generated with equipment details, status totals, and summary information
R-GCX146-cbl-00379
Initialize US Trip Sheet Equipment Records
Process Rules
📊 Business Logic Narrative
When the process 'Initialize US Trip Sheet Equipment Records' is invoked, and assuming that a us trip sheet generation process is starting, when the system begins processing equipment records, the desired outcome is that equipment record counter is set to zero and data structures are cleared.
💻 Technical Criteria
Given
A US trip sheet generation process is starting
When
The system begins processing equipment records
Then
Equipment record counter is set to zero and data structures are cleared
R-GCX146-cbl-00381
Format Equipment Type Messages
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Type Messages' is invoked, and assuming that equipment data has been prepared, when the system formats the equipment information, the desired outcome is that equipment details are structured according to us customs trip sheet message format requirements.
💻 Technical Criteria
Given
Equipment data has been prepared
When
The system formats the equipment information
Then
Equipment details are structured according to US customs trip sheet message format requirements
R-GCX146-cbl-00382
Equipment Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Type?' is invoked, and assuming that an equipment record with type information, when the system evaluates the equipment type, the desired outcome is that equipment is classified as idler, unit, van, etu, or other type for specialized processing.
💻 Technical Criteria
Given
An equipment record with type information
When
The system evaluates the equipment type
Then
Equipment is classified as IDLER, UNIT, VAN, ETU, or Other type for specialized processing
R-GCX146-cbl-00383
Process IDLER Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process IDLER Equipment' is invoked, and assuming that equipment is classified as idler type, when the system processes the idler equipment, the desired outcome is that idler equipment is formatted with appropriate customs codes and status information.
💻 Technical Criteria
Given
Equipment is classified as IDLER type
When
The system processes the IDLER equipment
Then
IDLER equipment is formatted with appropriate customs codes and status information
R-GCX146-cbl-00385
Process VAN Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process VAN Equipment' is invoked, and assuming that equipment is classified as van type, when the system processes the van equipment, the desired outcome is that van equipment is formatted with container information and customs documentation.
💻 Technical Criteria
Given
Equipment is classified as VAN type
When
The system processes the VAN equipment
Then
VAN equipment is formatted with container information and customs documentation
R-GCX146-cbl-00386
Process ETU Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process ETU Equipment' is invoked, and assuming that equipment is classified as etu type, when the system processes the etu equipment, the desired outcome is that etu equipment is formatted with empty status and appropriate customs codes.
💻 Technical Criteria
Given
Equipment is classified as ETU type
When
The system processes the ETU equipment
Then
ETU equipment is formatted with empty status and appropriate customs codes
R-GCX146-cbl-00387
Process Other Equipment Types
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Process Other Equipment Types', assuming that equipment does not match idler, unit, van, or etu classifications, when the system processes the other equipment type, the desired outcome is that equipment is formatted using standard customs reporting format with available information.
💻 Technical Criteria
EXCLUDING
Equipment does not match IDLER, UNIT, VAN, or ETU classifications
When
The system processes the other equipment type
Then
Equipment is formatted using standard customs reporting format with available information
R-GCX146-cbl-00388
Build Merlin Transmission Lines
Process Rules
📊 Business Logic Narrative
When the process 'Build Merlin Transmission Lines' is invoked, and assuming that equipment data has been processed and formatted, when the system builds transmission lines, the desired outcome is that message lines are constructed in merlin format with proper headers and equipment details.
💻 Technical Criteria
Given
Equipment data has been processed and formatted
When
The system builds transmission lines
Then
Message lines are constructed in Merlin format with proper headers and equipment details
R-GCX146-cbl-00389
Format Trip Sheet Data for US Customs
Process Rules
📊 Business Logic Narrative
When the process 'Format Trip Sheet Data for US Customs' is invoked, and assuming that all equipment has been processed and transmission lines built, when the system formats the complete trip sheet, the desired outcome is that trip sheet data is structured according to us customs specifications with all required fields populated.
💻 Technical Criteria
Given
All equipment has been processed and transmission lines built
When
The system formats the complete trip sheet
Then
Trip sheet data is structured according to US customs specifications with all required fields populated
R-GCX146-cbl-00396
Cargo Arrival Detection - Identify cargo arrived at final destination
Process Rules
📊 Business Logic Narrative
When the process 'Cargo Arrival Detection - Identify cargo arrived at final destination' is invoked, and assuming that the cobol code summary is provided for analysis, when attempting to extract business rules for cargo arrival detection, the desired outcome is that no specific implementation details are available to generate business rules.
💻 Technical Criteria
Given
The COBOL code summary is provided for analysis
When
Attempting to extract business rules for cargo arrival detection
Then
No specific implementation details are available to generate business rules
R-GCX146-cbl-00397
Check Cargo Status
Decision Rules
📊 Business Logic Narrative
When the process 'Check Cargo Status' is invoked, and assuming that a cargo item exists on the train with manifest destination information, when the system processes cargo for arrival notifications, the desired outcome is that the cargo is identified for notification if manifest destination matches train destination and is not ocean manifest type.
💻 Technical Criteria
Given
A cargo item exists on the train with manifest destination information
When
The system processes cargo for arrival notifications
Then
The cargo is identified for notification if manifest destination matches train destination and is not ocean manifest type
R-GCX146-cbl-00398
Cargo Arrived at Destination?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo Arrived at Destination?' is invoked, and assuming that cargo exists with manifest from and to station codes, when the system checks if cargo has arrived at destination, the desired outcome is that cargo is considered arrived if manifest to-station matches current train location and manifest type is not ocean (type 9).
💻 Technical Criteria
Given
Cargo exists with manifest from and to station codes
When
The system checks if cargo has arrived at destination
Then
Cargo is considered arrived if manifest to-station matches current train location and manifest type is not ocean (type 9)
R-GCX146-cbl-00402
No Action Required
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'No Action Required', assuming that cargo exists but has not arrived at destination or is ocean manifest type, when the system evaluates cargo for arrival processing, the desired outcome is that no arrival notification is generated and processing continues to next cargo item.
💻 Technical Criteria
EXCLUDING
Cargo exists but has not arrived at destination or is ocean manifest type
When
The system evaluates cargo for arrival processing
Then
No arrival notification is generated and processing continues to next cargo item
R-GCX146-cbl-00403
Identify Canadian Goods Returning from US
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Canadian Goods Returning from US' is invoked, and assuming that a cargo shipment with origin and destination information, when the system evaluates the cargo movement pattern, the desired outcome is that the cargo is classified as canadian goods returning if it originated in canada and is returning from the us.
💻 Technical Criteria
Given
A cargo shipment with origin and destination information
When
The system evaluates the cargo movement pattern
Then
The cargo is classified as Canadian goods returning if it originated in Canada and is returning from the US
R-GCX146-cbl-00417
W301-SEND-TO-2-BROKER: Secondary Broker Notification
Process Rules
📊 Business Logic Narrative
When the process 'W301-SEND-TO-2-BROKER: Secondary Broker Notification' is invoked, and assuming that primary broker notification has been processed and a secondary broker is configured for the cargo, when the system continues broker notification processing, the desired outcome is that the system should send notifications to the secondary broker using their configured communication channels.
💻 Technical Criteria
Given
Primary broker notification has been processed and a secondary broker is configured for the cargo
When
The system continues broker notification processing
Then
The system should send notifications to the secondary broker using their configured communication channels
R-GCX146-cbl-01784
Prepare Equipment ID for X12
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Equipment ID for X12' is invoked, and assuming that equipment information is available in the system, when the system prepares x12 message data, the desired outcome is that the system formats equipment id according to x12 requirements.
💻 Technical Criteria
Given
Equipment information is available in the system
When
The system prepares X12 message data
Then
The system formats equipment ID according to X12 requirements
R-GCX146-cbl-01800
Set Message Priority
Decision Rules
📊 Business Logic Narrative
When the process 'Set Message Priority' is invoked, and assuming that a broker notification is being prepared, when message priority needs to be determined, the desired outcome is that the system sets priority level based on cargo characteristics and delivery requirements in gcx019 parameters.
💻 Technical Criteria
Given
A broker notification is being prepared
When
Message priority needs to be determined
Then
The system sets priority level based on cargo characteristics and delivery requirements in GCX019 parameters
R-GCX146-cbl-01322
Secondary Broker ID Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Secondary Broker ID Available?' is invoked, and assuming that a cargo notification process is initiated, when the system checks for secondary broker configuration, the desired outcome is that the process continues to notification channel determination if secondary broker id exists, otherwise completes without secondary broker notification.
💻 Technical Criteria
Given
A cargo notification process is initiated
When
The system checks for secondary broker configuration
Then
The process continues to notification channel determination if secondary broker ID exists, otherwise completes without secondary broker notification
R-GCX146-cbl-00429
Access GCSUSRT Database
Action Rules
📊 Business Logic Narrative
When the process 'Access GCSUSRT Database' is invoked, and assuming that a request to process us customs status for equipment, when the system accesses the gcsusrt database using equipment information, the desired outcome is that the system retrieves the corresponding us route record if it exists.
💻 Technical Criteria
Given
A request to process US customs status for equipment
When
The system accesses the GCSUSRT database using equipment information
Then
The system retrieves the corresponding US route record if it exists
R-GCX146-cbl-00431
Extract Bond Type Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Bond Type Information' is invoked, and assuming that a valid us route record has been found in the gcsusrt database, when the system processes the route record, the desired outcome is that the system extracts bond type, cargo status, vessel information, and location data from the record.
💻 Technical Criteria
Given
A valid US route record has been found in the GCSUSRT database
When
The system processes the route record
Then
The system extracts bond type, cargo status, vessel information, and location data from the record
R-GCX146-cbl-00434
Validate In-Transit Status
Validation Rules
📊 Business Logic Narrative
When the process 'Validate In-Transit Status' is invoked, and assuming that bond type information has been processed, when the system checks the cargo's in-transit status, the desired outcome is that the system validates whether the cargo is properly documented as in-transit or not.
💻 Technical Criteria
Given
Bond type information has been processed
When
The system checks the cargo's in-transit status
Then
The system validates whether the cargo is properly documented as in-transit or not
R-GCX146-cbl-00435
Cargo In-Transit?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo In-Transit?' is invoked, and assuming that the in-transit status has been validated, when the system evaluates the cargo's current transit state, the desired outcome is that the system determines if the cargo is in-transit and routes processing accordingly.
💻 Technical Criteria
Given
The in-transit status has been validated
When
The system evaluates the cargo's current transit state
Then
The system determines if the cargo is in-transit and routes processing accordingly
R-GCX146-cbl-00436
Validate Location Information
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Information' is invoked, and assuming that cargo has been determined to be in-transit, when the system validates location information from the us route record, the desired outcome is that the system confirms location data is accurate and complete for customs processing.
💻 Technical Criteria
Given
Cargo has been determined to be in-transit
When
The system validates location information from the US route record
Then
The system confirms location data is accurate and complete for customs processing
R-GCX146-cbl-00437
Location Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Location Valid?' is invoked, and assuming that location information has been validated for in-transit cargo, when the system evaluates location validity, the desired outcome is that the system determines if location information is valid and proceeds with appropriate processing.
💻 Technical Criteria
Given
Location information has been validated for in-transit cargo
When
The system evaluates location validity
Then
The system determines if location information is valid and proceeds with appropriate processing
R-GCX146-cbl-00442
Check Cargo Conditions
Validation Rules
📊 Business Logic Narrative
When the process 'Check Cargo Conditions' is invoked, and assuming that vessel-specific status has been generated, when the system checks cargo conditions from the us route record, the desired outcome is that the system evaluates conditions such as bond dates, cargo types, and special requirements.
💻 Technical Criteria
Given
Vessel-specific status has been generated
When
The system checks cargo conditions from the US route record
Then
The system evaluates conditions such as bond dates, cargo types, and special requirements
R-GCX146-cbl-00443
Special Conditions?
Decision Rules
📊 Business Logic Narrative
When the process 'Special Conditions?' is invoked, and assuming that cargo conditions have been assessed, when the system evaluates for special conditions such as it bond warnings, vessel mismatches, or date discrepancies, the desired outcome is that the system determines if special conditions exist and routes to appropriate warning generation or normal processing.
💻 Technical Criteria
Given
Cargo conditions have been assessed
When
The system evaluates for special conditions such as IT bond warnings, vessel mismatches, or date discrepancies
Then
The system determines if special conditions exist and routes to appropriate warning generation or normal processing
R-GCX146-cbl-00444
Generate Warning Messages
Process Rules
📊 Business Logic Narrative
When the process 'Generate Warning Messages' is invoked, and assuming that special conditions have been detected in the cargo, when the system generates warning messages, the desired outcome is that the system creates appropriate warning messages for conditions such as it bond type warnings, train vessel warnings, location mismatches, or tib date warnings.
💻 Technical Criteria
Given
Special conditions have been detected in the cargo
When
The system generates warning messages
Then
The system creates appropriate warning messages for conditions such as IT bond type warnings, train vessel warnings, location mismatches, or TIB date warnings
R-GCX146-cbl-00445
Set US Customs Status
Process Rules
📊 Business Logic Narrative
When the process 'Set US Customs Status' is invoked, and assuming that all cargo conditions have been processed and any necessary warnings generated, when the system sets the us customs status, the desired outcome is that the system assigns the appropriate customs status reflecting the cargo's current state and compliance requirements.
💻 Technical Criteria
Given
All cargo conditions have been processed and any necessary warnings generated
When
The system sets the US customs status
Then
The system assigns the appropriate customs status reflecting the cargo's current state and compliance requirements
R-GCX146-cbl-00446
Update Status Information
Process Rules
📊 Business Logic Narrative
When the process 'Update Status Information' is invoked, and assuming that the us customs status has been set, when the system updates status information, the desired outcome is that the system records the customs status, warning messages, and related information in the equipment record for reporting and further processing.
💻 Technical Criteria
Given
The US customs status has been set
When
The system updates status information
Then
The system records the customs status, warning messages, and related information in the equipment record for reporting and further processing
R-GCX146-cbl-00475
Create Audit Record
Action Rules
📊 Business Logic Narrative
When the process 'Create Audit Record' is invoked, and assuming that a cargo processing activity has occurred that requires audit logging, when the system needs to create an audit trail record, the desired outcome is that the system spawns a gct1051e audit transaction using the gcx105-input data structure and handles the transaction queuing process.
💻 Technical Criteria
Given
A cargo processing activity has occurred that requires audit logging
When
The system needs to create an audit trail record
Then
The system spawns a GCT1051E audit transaction using the GCX105-INPUT data structure and handles the transaction queuing process
R-GCX146-cbl-00476
Capture Transaction Details
Process Rules
📊 Business Logic Narrative
When the process 'Capture Transaction Details' is invoked, and assuming that an audit trail record needs to be created for a cargo processing activity, when the system prepares to log the audit information, the desired outcome is that the system populates the gcx105-input structure with transaction details including user information, timestamps, and activity data.
💻 Technical Criteria
Given
An audit trail record needs to be created for a cargo processing activity
When
The system prepares to log the audit information
Then
The system populates the GCX105-INPUT structure with transaction details including user information, timestamps, and activity data
R-GCX146-cbl-00497
Call GCCCARTP Module
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCCARTP Module' is invoked, and assuming that an equipment record with equipment id and type code is available, when the system needs to classify the equipment type, the desired outcome is that the gcccartp module is called to determine equipment classification.
💻 Technical Criteria
Given
An equipment record with equipment ID and type code is available
When
The system needs to classify the equipment type
Then
The GCCCARTP module is called to determine equipment classification
R-GCX146-cbl-00498
Set as Container Type
Decision Rules
📊 Business Logic Narrative
When the process 'Set as Container Type' is invoked, and assuming that equipment has been processed by gcccartp module, when the module classifies the equipment as container type, the desired outcome is that the system sets the equipment type as container for processing.
💻 Technical Criteria
Given
Equipment has been processed by GCCCARTP module
When
The module classifies the equipment as container type
Then
The system sets the equipment type as container for processing
R-GCX146-cbl-00499
Set as Trailer Type
Decision Rules
📊 Business Logic Narrative
When the process 'Set as Trailer Type' is invoked, and assuming that equipment has been processed by gcccartp module, when the module classifies the equipment as trailer type, the desired outcome is that the system sets the equipment type as trailer for processing.
💻 Technical Criteria
Given
Equipment has been processed by GCCCARTP module
When
The module classifies the equipment as trailer type
Then
The system sets the equipment type as trailer for processing
R-GCX146-cbl-00500
Set as Car Type
Decision Rules
📊 Business Logic Narrative
When the process 'Set as Car Type' is invoked, and assuming that equipment has been processed by gcccartp module, when the module classifies the equipment as car type, the desired outcome is that the system sets the equipment type as car for processing.
💻 Technical Criteria
Given
Equipment has been processed by GCCCARTP module
When
The module classifies the equipment as car type
Then
The system sets the equipment type as car for processing
R-GCX146-cbl-00501
Retrieve Car Type Description from VI Segment
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Car Type Description from VI Segment' is invoked, and assuming that equipment has been classified as car type, when the system needs car type description information, the desired outcome is that the car type description is retrieved from the vi segment using the car type code.
💻 Technical Criteria
Given
Equipment has been classified as car type
When
The system needs car type description information
Then
The car type description is retrieved from the VI segment using the car type code
R-GCX146-cbl-00502
Assign Equipment Type Code for Processing
Process Rules
📊 Business Logic Narrative
When the process 'Assign Equipment Type Code for Processing' is invoked, and assuming that equipment type has been determined as container, trailer, or car, when the system needs to assign processing type code, the desired outcome is that the appropriate equipment type code is assigned based on the classification.
💻 Technical Criteria
Given
Equipment type has been determined as container, trailer, or car
When
The system needs to assign processing type code
Then
The appropriate equipment type code is assigned based on the classification
R-GCX146-cbl-00503
Set Processing Requirements Based on Type
Process Rules
📊 Business Logic Narrative
When the process 'Set Processing Requirements Based on Type' is invoked, and assuming that equipment type code has been assigned, when the system needs to establish processing requirements, the desired outcome is that processing requirements are set according to the specific equipment type (container, trailer, or car).
💻 Technical Criteria
Given
Equipment type code has been assigned
When
The system needs to establish processing requirements
Then
Processing requirements are set according to the specific equipment type (container, trailer, or car)
R-GCX146-cbl-00504
Access Container Records on Flat Car
Process Rules
📊 Business Logic Narrative
When the process 'Access Container Records on Flat Car' is invoked, and assuming that a flat car equipment type is being processed for train manifest, when the system needs to identify containers loaded on the flat car, the desired outcome is that the system accesses container records from the flat car's equipment data.
💻 Technical Criteria
Given
A flat car equipment type is being processed for train manifest
When
The system needs to identify containers loaded on the flat car
Then
The system accesses container records from the flat car's equipment data
R-GCX146-cbl-00505
Container Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Record Found?' is invoked, and assuming that container records are being accessed for a flat car, when the system searches for container data associated with the flat car, the desired outcome is that the system determines if container records exist and proceeds with container processing if found, or completes flat car processing if no containers are found.
💻 Technical Criteria
Given
Container records are being accessed for a flat car
When
The system searches for container data associated with the flat car
Then
The system determines if container records exist and proceeds with container processing if found, or completes flat car processing if no containers are found
R-GCX146-cbl-00506
Extract Container ID from Record
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from Record' is invoked, and assuming that a container record has been found on the flat car, when the system needs to identify the specific container, the desired outcome is that the system extracts the container id from the container record for individual container processing.
💻 Technical Criteria
Given
A container record has been found on the flat car
When
The system needs to identify the specific container
Then
The system extracts the container ID from the container record for individual container processing
R-GCX146-cbl-00507
Set Flat Car Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag' is invoked, and assuming that a container id has been extracted from a flat car record, when the system begins processing containers on the flat car, the desired outcome is that the system sets a flat car processing flag to track the current processing state.
💻 Technical Criteria
Given
A container ID has been extracted from a flat car record
When
The system begins processing containers on the flat car
Then
The system sets a flat car processing flag to track the current processing state
R-GCX146-cbl-00511
Extract Container Information from T/C XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container Information from T/C XREF' is invoked, and assuming that the inquiry database has been accessed for container information, when the system needs to extract specific container details, the desired outcome is that the system extracts container information from the t/c xref (trailer/container cross reference) data.
💻 Technical Criteria
Given
The inquiry database has been accessed for container information
When
The system needs to extract specific container details
Then
The system extracts container information from the T/C XREF (Trailer/Container Cross Reference) data
R-GCX146-cbl-00513
Process Container for Train Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Process Container for Train Manifest' is invoked, and assuming that a container has been validated successfully, when the container needs to be included in the train manifest, the desired outcome is that the system processes the container for train manifest inclusion with all required container details.
💻 Technical Criteria
Given
A container has been validated successfully
When
The container needs to be included in the train manifest
Then
The system processes the container for train manifest inclusion with all required container details
R-GCX146-cbl-00514
More Containers on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers on Flat Car?' is invoked, and assuming that a container has been processed for train manifest on a flat car, when the system checks for additional containers on the same flat car, the desired outcome is that the system determines if more containers exist and continues processing if found, or completes flat car processing if no more containers exist.
💻 Technical Criteria
Given
A container has been processed for train manifest on a flat car
When
The system checks for additional containers on the same flat car
Then
The system determines if more containers exist and continues processing if found, or completes flat car processing if no more containers exist
R-GCX146-cbl-00515
Get Next Container Record
Process Rules
📊 Business Logic Narrative
When the process 'Get Next Container Record' is invoked, and assuming that more containers exist on the flat car being processed, when the system needs to process the next container, the desired outcome is that the system retrieves the next container record from the flat car's container data.
💻 Technical Criteria
Given
More containers exist on the flat car being processed
When
The system needs to process the next container
Then
The system retrieves the next container record from the flat car's container data
R-GCX146-cbl-00516
Complete Flat Car Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Flat Car Processing' is invoked, and assuming that all containers on a flat car have been processed or no containers were found, when the flat car processing workflow reaches completion, the desired outcome is that the system completes flat car processing and finalizes all container-related data for the train manifest.
💻 Technical Criteria
Given
All containers on a flat car have been processed or no containers were found
When
The flat car processing workflow reaches completion
Then
The system completes flat car processing and finalizes all container-related data for the train manifest
R-GCX146-cbl-00517
Container Processing Error
Process Rules
📊 Business Logic Narrative
When the process 'Container Processing Error' is invoked, and assuming that an error occurs during container record access or processing, when the system encounters a container processing error, the desired outcome is that the system handles the error appropriately and proceeds to complete flat car processing.
💻 Technical Criteria
Given
An error occurs during container record access or processing
When
The system encounters a container processing error
Then
The system handles the error appropriately and proceeds to complete flat car processing
R-GCX146-cbl-00524
Extract Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Information' is invoked, and assuming that fw-iq database contains equipment record, when system extracts equipment information, the desired outcome is that retrieve equipment details from fw-iq record for further processing.
💻 Technical Criteria
Given
FW-IQ database contains equipment record
When
System extracts equipment information
Then
Retrieve equipment details from FW-IQ record for further processing
R-GCX146-cbl-00525
Check for Container on Flat Car
Validation Rules
📊 Business Logic Narrative
When the process 'Check for Container on Flat Car' is invoked, and assuming that equipment information has been extracted from inquiry database, when system evaluates equipment configuration, the desired outcome is that check if equipment is flat car type with container loading configuration.
💻 Technical Criteria
Given
Equipment information has been extracted from inquiry database
When
System evaluates equipment configuration
Then
Check if equipment is flat car type with container loading configuration
R-GCX146-cbl-00527
Process Container T/C XREF Records
Action Rules
📊 Business Logic Narrative
When the process 'Process Container T/C XREF Records' is invoked, and assuming that equipment is flat car with containers, when system processes container cross-references, the desired outcome is that access and process t/c xref records to identify container details.
💻 Technical Criteria
Given
Equipment is flat car with containers
When
System processes container cross-references
Then
Access and process T/C XREF records to identify container details
R-GCX146-cbl-00528
Extract Container IDs from Inquiry
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container IDs from Inquiry' is invoked, and assuming that container t/c xref records are being processed, when system extracts container identifiers, the desired outcome is that retrieve container id numbers from inquiry database records.
💻 Technical Criteria
Given
Container T/C XREF records are being processed
When
System extracts container identifiers
Then
Retrieve container ID numbers from inquiry database records
R-GCX146-cbl-00529
Set Flat Car Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag' is invoked, and assuming that container ids have been extracted from inquiry records, when system sets processing indicators, the desired outcome is that set flat car processing flag to indicate container handling requirements.
💻 Technical Criteria
Given
Container IDs have been extracted from inquiry records
When
System sets processing indicators
Then
Set flat car processing flag to indicate container handling requirements
R-GCX146-cbl-00538
Movement Rules Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Movement Rules Valid?' is invoked, and assuming that equipment status has been validated against cargo movement rules, when system evaluates movement rules compliance, the desired outcome is that system sets appropriate validated load or empty status based on compliance results.
💻 Technical Criteria
Given
Equipment status has been validated against cargo movement rules
When
System evaluates movement rules compliance
Then
System sets appropriate validated load or empty status based on compliance results
R-GCX146-cbl-00539
Set Validated Load Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Validated Load Status' is invoked, and assuming that equipment status passes cargo movement rules validation, when system assigns final status for loaded equipment, the desired outcome is that system sets validated load status indicating equipment carries cargo.
💻 Technical Criteria
Given
Equipment status passes cargo movement rules validation
When
System assigns final status for loaded equipment
Then
System sets validated load status indicating equipment carries cargo
R-GCX146-cbl-00540
Set Validated Empty Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Validated Empty Status' is invoked, and assuming that equipment status fails cargo movement rules validation, when system assigns final status for equipment, the desired outcome is that system sets validated empty status indicating equipment carries no cargo.
💻 Technical Criteria
Given
Equipment status fails cargo movement rules validation
When
System assigns final status for equipment
Then
System sets validated empty status indicating equipment carries no cargo
R-GCX146-cbl-00544
Update Equipment Status Indicators
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Indicators' is invoked, and assuming that final load/empty status has been determined, when system updates equipment status indicators, the desired outcome is that system records final load/empty status in equipment data for subsequent processing.
💻 Technical Criteria
Given
Final load/empty status has been determined
When
System updates equipment status indicators
Then
System records final load/empty status in equipment data for subsequent processing
R-GCX146-cbl-00545
Access Flat Car Container Records
Action Rules
📊 Business Logic Narrative
When the process 'Access Flat Car Container Records' is invoked, and assuming that a flat car equipment record is being processed, when the system needs to process containers on the flat car, the desired outcome is that the system accesses fwswrwr container records using the flat car identification.
💻 Technical Criteria
Given
A flat car equipment record is being processed
When
The system needs to process containers on the flat car
Then
The system accesses FWSWRWR container records using the flat car identification
R-GCX146-cbl-00546
Container Records Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Records Found?' is invoked, and assuming that container records have been accessed for a flat car, when the system checks for container record availability, the desired outcome is that the system determines if container records exist and routes processing accordingly.
💻 Technical Criteria
Given
Container records have been accessed for a flat car
When
The system checks for container record availability
Then
The system determines if container records exist and routes processing accordingly
R-GCX146-cbl-00547
Extract Container ID from T/C XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from T/C XREF' is invoked, and assuming that container records exist for a flat car, when the system processes container identification, the desired outcome is that the system extracts container id from t/c xref records for further processing.
💻 Technical Criteria
Given
Container records exist for a flat car
When
The system processes container identification
Then
The system extracts container ID from T/C XREF records for further processing
R-GCX146-cbl-00548
Set Flat Car Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag' is invoked, and assuming that container id has been extracted from t/c xref, when the system begins flat car container processing, the desired outcome is that the system sets the flat car processing flag to indicate active container processing.
💻 Technical Criteria
Given
Container ID has been extracted from T/C XREF
When
The system begins flat car container processing
Then
The system sets the flat car processing flag to indicate active container processing
R-GCX146-cbl-00549
Validate Container Identification
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Container Identification' is invoked, and assuming that container id has been extracted and flat car processing flag is set, when the system validates container identification, the desired outcome is that the system verifies container id format and validity for business processing.
💻 Technical Criteria
Given
Container ID has been extracted and flat car processing flag is set
When
The system validates container identification
Then
The system verifies container ID format and validity for business processing
R-GCX146-cbl-00550
Individual Container Validation
Validation Rules
📊 Business Logic Narrative
When the process 'Individual Container Validation' is invoked, and assuming that container identification has been validated, when the system processes individual container validation, the desired outcome is that the system applies business rules specific to container processing requirements.
💻 Technical Criteria
Given
Container identification has been validated
When
The system processes individual container validation
Then
The system applies business rules specific to container processing requirements
R-GCX146-cbl-00551
Update Container Processing Status
Process Rules
📊 Business Logic Narrative
When the process 'Update Container Processing Status' is invoked, and assuming that individual container validation has been completed, when the system updates container processing status, the desired outcome is that the system records the current processing status for the container.
💻 Technical Criteria
Given
Individual container validation has been completed
When
The system updates container processing status
Then
The system records the current processing status for the container
R-GCX146-cbl-00552
Process Next Container in Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Process Next Container in Sequence' is invoked, and assuming that container processing status has been updated, when the system continues sequential processing, the desired outcome is that the system moves to process the next container in the sequence.
💻 Technical Criteria
Given
Container processing status has been updated
When
The system continues sequential processing
Then
The system moves to process the next container in the sequence
R-GCX146-cbl-00553
More Containers on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'More Containers on Flat Car?' is invoked, and assuming that a container has been processed in sequence, when the system checks for additional containers, the desired outcome is that the system determines if more containers exist on the flat car for processing.
💻 Technical Criteria
Given
A container has been processed in sequence
When
The system checks for additional containers
Then
The system determines if more containers exist on the flat car for processing
R-GCX146-cbl-00554
Complete Container Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Complete Container Sequence' is invoked, and assuming that no more containers exist on the flat car, when the system completes container sequence processing, the desired outcome is that the system finalizes all container processing for the flat car.
💻 Technical Criteria
Given
No more containers exist on the flat car
When
The system completes container sequence processing
Then
The system finalizes all container processing for the flat car
R-GCX146-cbl-00555
Container Inquiry Database Lookup
Action Rules
📊 Business Logic Narrative
When the process 'Container Inquiry Database Lookup' is invoked, and assuming that no container records were found in primary lookup, when the system performs inquiry database lookup, the desired outcome is that the system accesses fw-iq inquiry database for container information.
💻 Technical Criteria
Given
No container records were found in primary lookup
When
The system performs inquiry database lookup
Then
The system accesses FW-IQ inquiry database for container information
R-GCX146-cbl-00556
Inquiry Data Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Inquiry Data Available?' is invoked, and assuming that inquiry database lookup has been performed, when the system checks inquiry data availability, the desired outcome is that the system determines if container data exists in the inquiry database.
💻 Technical Criteria
Given
Inquiry database lookup has been performed
When
The system checks inquiry data availability
Then
The system determines if container data exists in the inquiry database
R-GCX146-cbl-00557
Use Inquiry Container Data
Process Rules
📊 Business Logic Narrative
When the process 'Use Inquiry Container Data' is invoked, and assuming that container data is available in inquiry database, when the system processes inquiry container data, the desired outcome is that the system uses inquiry database container data for validation processing.
💻 Technical Criteria
Given
Container data is available in inquiry database
When
The system processes inquiry container data
Then
The system uses inquiry database container data for validation processing
R-GCX146-cbl-00559
Container Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Record Found?' is invoked, and assuming that the system has accessed the fw-iq inquiry database for a container, when the system searches for container records, the desired outcome is that the system determines if a container record exists and proceeds with extraction if found, or skips processing if not found.
💻 Technical Criteria
Given
The system has accessed the FW-IQ inquiry database for a container
When
The system searches for container records
Then
The system determines if a container record exists and proceeds with extraction if found, or skips processing if not found
R-GCX146-cbl-00560
Extract Container ID from T/C XREF
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container ID from T/C XREF' is invoked, and assuming that a container record exists in the inquiry database, when the system processes the container record, the desired outcome is that the system extracts the container id from the t/c xref (trailer/container cross reference) data.
💻 Technical Criteria
Given
A container record exists in the inquiry database
When
The system processes the container record
Then
The system extracts the container ID from the T/C XREF (Trailer/Container Cross Reference) data
R-GCX146-cbl-00564
Set Flat Car Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag' is invoked, and assuming that container information has been successfully processed, when the system identifies equipment as a flat car with containers, the desired outcome is that the system sets the flat car processing flag to enable special container handling procedures.
💻 Technical Criteria
Given
Container information has been successfully processed
When
The system identifies equipment as a flat car with containers
Then
The system sets the flat car processing flag to enable special container handling procedures
R-GCX146-cbl-00565
Extract Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Details' is invoked, and assuming that the flat car processing flag has been set for container equipment, when the system extracts equipment details, the desired outcome is that the system retrieves detailed equipment information including container specifications and transportation data.
💻 Technical Criteria
Given
The flat car processing flag has been set for container equipment
When
The system extracts equipment details
Then
The system retrieves detailed equipment information including container specifications and transportation data
R-GCX146-cbl-00569
Container Not Found - Skip
Decision Rules
📊 Business Logic Narrative
When the process 'Container Not Found - Skip' is invoked, and assuming that the system has searched for container records in the fw-iq inquiry database, when no container record is found for the specified container, the desired outcome is that the system skips container processing and proceeds to completion without processing container information.
💻 Technical Criteria
Given
The system has searched for container records in the FW-IQ inquiry database
When
No container record is found for the specified container
Then
The system skips container processing and proceeds to completion without processing container information
R-GCX146-cbl-00571
Access VI Segment Table
Action Rules
📊 Business Logic Narrative
When the process 'Access VI Segment Table' is invoked, and assuming that an equipment record with a car type code exists, when the system needs to retrieve the car type description, the desired outcome is that the system accesses the vi segment table using the car type code and retrieves the corresponding car type description for display purposes.
💻 Technical Criteria
Given
An equipment record with a car type code exists
When
The system needs to retrieve the car type description
Then
The system accesses the VI segment table using the car type code and retrieves the corresponding car type description for display purposes
R-GCX146-cbl-00572
Car Type Code Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Car Type Code Found?' is invoked, and assuming that a car type code from equipment information, when the system looks up the car type code in the vi segment table, the desired outcome is that if the car type code is found, continue with description retrieval, otherwise flag as equipment type error.
💻 Technical Criteria
Given
A car type code from equipment information
When
The system looks up the car type code in the VI segment table
Then
If the car type code is found, continue with description retrieval, otherwise flag as equipment type error
R-GCX146-cbl-00573
Valid Equipment Type?
Validation Rules
📊 Business Logic Narrative
When the process 'Valid Equipment Type?' is invoked, and assuming that equipment information with car type details retrieved from vi segment, when the system validates the equipment type classification, the desired outcome is that if the equipment type is valid and recognized, proceed with edi code assignment, otherwise flag as equipment type error.
💻 Technical Criteria
Given
Equipment information with car type details retrieved from VI segment
When
The system validates the equipment type classification
Then
If the equipment type is valid and recognized, proceed with EDI code assignment, otherwise flag as equipment type error
R-GCX146-cbl-00574
Set Equipment Type Code for EDI
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment Type Code for EDI' is invoked, and assuming that a validated equipment type classification, when the system needs to set edi equipment type codes, the desired outcome is that the system assigns the appropriate edi equipment type code based on the car type classification for electronic transactions.
💻 Technical Criteria
Given
A validated equipment type classification
When
The system needs to set EDI equipment type codes
Then
The system assigns the appropriate EDI equipment type code based on the car type classification for electronic transactions
R-GCX146-cbl-00575
Assign Car Type to Trip Sheet Display
Action Rules
📊 Business Logic Narrative
When the process 'Assign Car Type to Trip Sheet Display' is invoked, and assuming that valid equipment type with retrieved car type description, when the system generates trip sheet displays, the desired outcome is that the system assigns the car type description to the trip sheet display fields for proper reporting.
💻 Technical Criteria
Given
Valid equipment type with retrieved car type description
When
The system generates trip sheet displays
Then
The system assigns the car type description to the trip sheet display fields for proper reporting
R-GCX146-cbl-00576
Determine Processing Classification
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Processing Classification' is invoked, and assuming that equipment with validated type information, when the system needs to determine processing classification, the desired outcome is that the system evaluates equipment characteristics to classify as container, trailer, or car type for appropriate processing workflow.
💻 Technical Criteria
Given
Equipment with validated type information
When
The system needs to determine processing classification
Then
The system evaluates equipment characteristics to classify as container, trailer, or car type for appropriate processing workflow
R-GCX146-cbl-00577
Container Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Container Type?' is invoked, and assuming that equipment undergoing processing classification, when the system evaluates if the equipment is a container type, the desired outcome is that if equipment is identified as container type, set container processing flag, otherwise continue to trailer type evaluation.
💻 Technical Criteria
Given
Equipment undergoing processing classification
When
The system evaluates if the equipment is a container type
Then
If equipment is identified as container type, set container processing flag, otherwise continue to trailer type evaluation
R-GCX146-cbl-00578
Trailer Type?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Trailer Type?', assuming that equipment that is not classified as container type, when the system evaluates if the equipment is a trailer type, the desired outcome is that if equipment is identified as trailer type, set trailer processing flag, otherwise continue to car type evaluation.
💻 Technical Criteria
EXCLUDING
Equipment that is not classified as container type
When
The system evaluates if the equipment is a trailer type
Then
If equipment is identified as trailer type, set trailer processing flag, otherwise continue to car type evaluation
R-GCX146-cbl-00579
Car Type?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Car Type?', assuming that equipment that is not classified as container or trailer type, when the system evaluates if the equipment is a car type, the desired outcome is that if equipment is identified as car type, set car processing flag, otherwise flag as equipment type error.
💻 Technical Criteria
EXCLUDING
Equipment that is not classified as container or trailer type
When
The system evaluates if the equipment is a car type
Then
If equipment is identified as car type, set car processing flag, otherwise flag as equipment type error
R-GCX146-cbl-00580
Set Container Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Container Processing Flag' is invoked, and assuming that equipment classified as container type, when the system sets processing flags, the desired outcome is that the system sets the container processing flag to enable container-specific processing and completes equipment type determination.
💻 Technical Criteria
Given
Equipment classified as container type
When
The system sets processing flags
Then
The system sets the container processing flag to enable container-specific processing and completes equipment type determination
R-GCX146-cbl-00581
Set Trailer Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Trailer Processing Flag' is invoked, and assuming that equipment classified as trailer type, when the system sets processing flags, the desired outcome is that the system sets the trailer processing flag to enable trailer-specific processing and completes equipment type determination.
💻 Technical Criteria
Given
Equipment classified as trailer type
When
The system sets processing flags
Then
The system sets the trailer processing flag to enable trailer-specific processing and completes equipment type determination
R-GCX146-cbl-00582
Set Car Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Car Processing Flag' is invoked, and assuming that equipment classified as car type, when the system sets processing flags, the desired outcome is that the system sets the car processing flag to enable car-specific processing and completes equipment type determination.
💻 Technical Criteria
Given
Equipment classified as car type
When
The system sets processing flags
Then
The system sets the car processing flag to enable car-specific processing and completes equipment type determination
R-GCX146-cbl-00586
Extract Car Identification
Process Rules
📊 Business Logic Narrative
When the process 'Extract Car Identification' is invoked, and assuming that an equipment record is retrieved from the bunch bill sequence, when the system processes the equipment data, the desired outcome is that car identification including car initial, car number, and equipment type is extracted and validated for completeness.
💻 Technical Criteria
Given
An equipment record is retrieved from the bunch bill sequence
When
The system processes the equipment data
Then
Car identification including car initial, car number, and equipment type is extracted and validated for completeness
R-GCX146-cbl-00593
Retrieve Next Car in Sequence
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Car in Sequence' is invoked, and assuming that bunch bill sequence has been initialized, when the system attempts to retrieve the next car in sequence, the desired outcome is that the system accesses equipment records to obtain the next car's data.
💻 Technical Criteria
Given
Bunch bill sequence has been initialized
When
The system attempts to retrieve the next car in sequence
Then
The system accesses equipment records to obtain the next car's data
R-GCX146-cbl-00594
Car Retrieved Successfully?
Validation Rules
📊 Business Logic Narrative
When the process 'Car Retrieved Successfully?' is invoked, and assuming that an attempt has been made to retrieve car data, when the system checks the retrieval status, the desired outcome is that if successful, proceed with car validation; if unsuccessful, complete bunch bill processing.
💻 Technical Criteria
Given
An attempt has been made to retrieve car data
When
The system checks the retrieval status
Then
If successful, proceed with car validation; if unsuccessful, complete bunch bill processing
R-GCX146-cbl-00595
Validate Car Equipment ID
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Car Equipment ID' is invoked, and assuming that a car has been successfully retrieved from equipment records, when the system validates the car's equipment id, the desired outcome is that the equipment id must meet format and business requirements for further processing.
💻 Technical Criteria
Given
A car has been successfully retrieved from equipment records
When
The system validates the car's equipment ID
Then
The equipment ID must meet format and business requirements for further processing
R-GCX146-cbl-00596
Process Car Equipment Data
Process Rules
📊 Business Logic Narrative
When the process 'Process Car Equipment Data' is invoked, and assuming that a car's equipment id has been validated, when the system processes the car's equipment data, the desired outcome is that all relevant equipment attributes are extracted and prepared for manifest inclusion.
💻 Technical Criteria
Given
A car's equipment ID has been validated
When
The system processes the car's equipment data
Then
All relevant equipment attributes are extracted and prepared for manifest inclusion
R-GCX146-cbl-00598
Update Equipment Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Totals' is invoked, and assuming that a car's load/empty status has been determined, when the system updates equipment totals, the desired outcome is that running counts for total equipment, loaded cars, and empty cars are incremented appropriately.
💻 Technical Criteria
Given
A car's load/empty status has been determined
When
The system updates equipment totals
Then
Running counts for total equipment, loaded cars, and empty cars are incremented appropriately
R-GCX146-cbl-00599
Add Car to Train Manifest
Process Rules
📊 Business Logic Narrative
When the process 'Add Car to Train Manifest' is invoked, and assuming that equipment totals have been updated for a car, when the system adds the car to the train manifest, the desired outcome is that the car becomes part of the official train consist with all required documentation.
💻 Technical Criteria
Given
Equipment totals have been updated for a car
When
The system adds the car to the train manifest
Then
The car becomes part of the official train consist with all required documentation
R-GCX146-cbl-00600
More Cars in Sequence?
Decision Rules
📊 Business Logic Narrative
When the process 'More Cars in Sequence?' is invoked, and assuming that a car has been added to the train manifest, when the system checks for more cars in the sequence, the desired outcome is that if more cars exist, continue processing; if no more cars, complete bunch bill processing.
💻 Technical Criteria
Given
A car has been added to the train manifest
When
The system checks for more cars in the sequence
Then
If more cars exist, continue processing; if no more cars, complete bunch bill processing
R-GCX146-cbl-00603
US Route Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'US Route Record Found?' is invoked, and assuming that system has attempted to retrieve us route record for equipment, when database lookup is completed, the desired outcome is that processing continues with bond validation if record exists, or skips us processing if no record found.
💻 Technical Criteria
Given
System has attempted to retrieve US Route record for equipment
When
Database lookup is completed
Then
Processing continues with bond validation if record exists, or skips US processing if no record found
R-GCX146-cbl-00604
Extract Bond Type Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Bond Type Information' is invoked, and assuming that us route record exists for the equipment, when system processes the us route record, the desired outcome is that bond type, in-transit status, location, and vessel information are extracted for validation.
💻 Technical Criteria
Given
US Route record exists for the equipment
When
System processes the US Route record
Then
Bond type, in-transit status, location, and vessel information are extracted for validation
R-GCX146-cbl-00607
Check In-Transit Status
Validation Rules
📊 Business Logic Narrative
When the process 'Check In-Transit Status' is invoked, and assuming that bond type is valid for us customs processing, when system checks the in-transit status from the us route record, the desired outcome is that in-transit status information is validated for consistency with current equipment location and movement.
💻 Technical Criteria
Given
Bond type is valid for US customs processing
When
System checks the in-transit status from the US Route record
Then
In-transit status information is validated for consistency with current equipment location and movement
R-GCX146-cbl-00608
Validate Location Information
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Location Information' is invoked, and assuming that in-transit status has been checked for the equipment, when system validates location information against current equipment position, the desired outcome is that location must be consistent with equipment routing and customs requirements.
💻 Technical Criteria
Given
In-transit status has been checked for the equipment
When
System validates location information against current equipment position
Then
Location must be consistent with equipment routing and customs requirements
R-GCX146-cbl-00609
Location Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Location Valid?' is invoked, and assuming that location information has been validated against equipment routing, when system evaluates location validity, the desired outcome is that processing continues with vessel validation if location is valid, or generates location warning if invalid.
💻 Technical Criteria
Given
Location information has been validated against equipment routing
When
System evaluates location validity
Then
Processing continues with vessel validation if location is valid, or generates location warning if invalid
R-GCX146-cbl-00610
Validate Vessel Name
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Vessel Name' is invoked, and assuming that location information is valid for the equipment, when system validates the vessel name from the us route record, the desired outcome is that vessel name is checked against expected transportation mode for the current shipment.
💻 Technical Criteria
Given
Location information is valid for the equipment
When
System validates the vessel name from the US Route record
Then
Vessel name is checked against expected transportation mode for the current shipment
R-GCX146-cbl-00612
Generate Bond Type Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Bond Type Warning' is invoked, and assuming that bond type validation has failed for the equipment, when system generates bond type warning, the desired outcome is that warning message is created indicating invalid bond type and potential customs compliance issue.
💻 Technical Criteria
Given
Bond type validation has failed for the equipment
When
System generates bond type warning
Then
Warning message is created indicating invalid bond type and potential customs compliance issue
R-GCX146-cbl-00613
Generate Location Warning
Action Rules
📊 Business Logic Narrative
When the process 'Generate Location Warning' is invoked, and assuming that location validation has failed for the equipment, when system generates location warning, the desired outcome is that warning message is created indicating location inconsistency and potential routing issue.
💻 Technical Criteria
Given
Location validation has failed for the equipment
When
System generates location warning
Then
Warning message is created indicating location inconsistency and potential routing issue
R-GCX146-cbl-00615
Set US Status Message
Process Rules
📊 Business Logic Narrative
When the process 'Set US Status Message' is invoked, and assuming that us route validation processing is complete with any applicable warnings, when system sets the us status message, the desired outcome is that status message includes validation results, warnings, and current customs status for the equipment.
💻 Technical Criteria
Given
US Route validation processing is complete with any applicable warnings
When
System sets the US status message
Then
Status message includes validation results, warnings, and current customs status for the equipment
R-GCX146-cbl-00616
Update Equipment Status
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status' is invoked, and assuming that us status message has been configured for the equipment, when system updates equipment status, the desired outcome is that equipment record is updated with us customs status, bond information, and any validation warnings.
💻 Technical Criteria
Given
US status message has been configured for the equipment
When
System updates equipment status
Then
Equipment record is updated with US customs status, bond information, and any validation warnings
R-GCX146-cbl-00617
Identify Canadian Goods from US
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Canadian Goods from US' is invoked, and assuming that a cargo shipment with origin and destination location information, when the system processes the shipment location data, the desired outcome is that the system determines if the goods are canadian goods returning from us by checking if origin is us and destination is canadian province.
💻 Technical Criteria
Given
A cargo shipment with origin and destination location information
When
The system processes the shipment location data
Then
The system determines if the goods are Canadian goods returning from US by checking if origin is US and destination is Canadian province
R-GCX146-cbl-00626
Conveying Car Validation - Validate equipment as conveying cars for intermodal processing
Validation Rules
📊 Business Logic Narrative
When the process 'Conveying Car Validation - Validate equipment as conveying cars for intermodal processing' is invoked, and assuming that a request to validate equipment as conveying cars for intermodal processing, when the system attempts to perform conveying car validation, the desired outcome is that the validation logic cannot be determined as the source code is not found in the provided cobol summary.
💻 Technical Criteria
Given
A request to validate equipment as conveying cars for intermodal processing
When
The system attempts to perform conveying car validation
Then
The validation logic cannot be determined as the source code is not found in the provided COBOL summary
R-GCX146-cbl-00627
Check Equipment Type Classification
Definitional Rules
📊 Business Logic Narrative
When the process 'Check Equipment Type Classification' is invoked, and assuming that an equipment record has been retrieved for processing, when the system evaluates the equipment type classification, the desired outcome is that the equipment is identified as idler type if it meets idler classification criteria.
💻 Technical Criteria
Given
An equipment record has been retrieved for processing
When
The system evaluates the equipment type classification
Then
The equipment is identified as idler type if it meets idler classification criteria
R-GCX146-cbl-00628
Set Idler Equipment Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Idler Equipment Flag' is invoked, and assuming that equipment has been classified as idler type, when the system processes the idler equipment classification, the desired outcome is that an idler equipment flag is set to indicate special processing requirements.
💻 Technical Criteria
Given
Equipment has been classified as idler type
When
The system processes the idler equipment classification
Then
An idler equipment flag is set to indicate special processing requirements
R-GCX146-cbl-00631
Bypass Train Assignment Validation
Validation Rules
📊 Business Logic Narrative
When the process 'Bypass Train Assignment Validation' is invoked, and assuming that equipment is flagged as idler type, when the system validates equipment train assignments, the desired outcome is that train assignment validation is bypassed for the idler equipment.
💻 Technical Criteria
Given
Equipment is flagged as idler type
When
The system validates equipment train assignments
Then
Train assignment validation is bypassed for the idler equipment
R-GCX146-cbl-00632
Set Equipment Status as IDLER
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment Status as IDLER' is invoked, and assuming that equipment has been processed as idler type, when the system assigns equipment status, the desired outcome is that equipment status is set to idler designation.
💻 Technical Criteria
Given
Equipment has been processed as idler type
When
The system assigns equipment status
Then
Equipment status is set to IDLER designation
R-GCX146-cbl-00633
Add to Equipment Totals as Idler
Computation Rules
📊 Business Logic Narrative
When the process 'Add to Equipment Totals as Idler' is invoked, and assuming that equipment status has been set as idler, when the system calculates equipment totals for reporting, the desired outcome is that the equipment is added to totals under the idler category.
💻 Technical Criteria
Given
Equipment status has been set as IDLER
When
The system calculates equipment totals for reporting
Then
The equipment is added to totals under the idler category
R-GCX146-cbl-00634
Generate Equipment Type Message IDLER
Action Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Type Message IDLER' is invoked, and assuming that equipment has been categorized and counted as idler, when the system generates equipment type messages, the desired outcome is that an equipment type message with idler designation is generated.
💻 Technical Criteria
Given
Equipment has been categorized and counted as idler
When
The system generates equipment type messages
Then
An equipment type message with IDLER designation is generated
R-GCX146-cbl-00641
Track Release Status in Trip Sheet
Process Rules
📊 Business Logic Narrative
When the process 'Track Release Status in Trip Sheet' is invoked, and assuming that equipment has been processed and status determined, when generating trip sheet details for add operations, the desired outcome is that the trip sheet should reflect the determined status (export, s.a.r., or release).
💻 Technical Criteria
Given
Equipment has been processed and status determined
When
Generating trip sheet details for ADD operations
Then
The trip sheet should reflect the determined status (EXPORT, S.A.R., or RELEASE)
R-GCX146-cbl-00650
Update Equipment Status Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status Totals' is invoked, and assuming that equipment has been processed and assigned a transit status, when the system updates operational totals, the desired outcome is that the appropriate status total counter (total-release, total-haulage, total-proceed, total-held-ccra, total-held-docs) is incremented based on the equipment's final status classification.
💻 Technical Criteria
Given
Equipment has been processed and assigned a transit status
When
The system updates operational totals
Then
The appropriate status total counter (TOTAL-RELEASE, TOTAL-HAULAGE, TOTAL-PROCEED, TOTAL-HELD-CCRA, TOTAL-HELD-DOCS) is incremented based on the equipment's final status classification
R-GCX146-cbl-00651
Retrieve Equipment SCAC Code
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Equipment SCAC Code' is invoked, and assuming that an equipment record exists in the system, when the system processes equipment for haulage rights validation, the desired outcome is that the equipment's scac code is retrieved from the equipment record for validation purposes.
💻 Technical Criteria
Given
An equipment record exists in the system
When
The system processes equipment for haulage rights validation
Then
The equipment's SCAC code is retrieved from the equipment record for validation purposes
R-GCX146-cbl-00652
SCAC Code Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'SCAC Code Valid?' is invoked, and assuming that an equipment scac code has been retrieved, when the system validates the scac code against authorized carriers, the desired outcome is that the system determines if the scac code is valid for haulage rights processing.
💻 Technical Criteria
Given
An equipment SCAC code has been retrieved
When
The system validates the SCAC code against authorized carriers
Then
The system determines if the SCAC code is valid for haulage rights processing
R-GCX146-cbl-00653
Haulage Rights Authorized?
Authorization Rules
📊 Business Logic Narrative
When the process 'Haulage Rights Authorized?' is invoked, and assuming that a valid scac code exists for the equipment, when the system checks haulage rights authorization for the scac, the desired outcome is that the system determines if haulage rights are authorized for this scac code.
💻 Technical Criteria
Given
A valid SCAC code exists for the equipment
When
The system checks haulage rights authorization for the SCAC
Then
The system determines if haulage rights are authorized for this SCAC code
R-GCX146-cbl-00654
Set Haulage Rights Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Haulage Rights Flag' is invoked, and assuming that equipment has valid scac code and authorized haulage rights, when the system processes the equipment for haulage validation, the desired outcome is that the haulage rights flag is set to indicate authorized haulage status.
💻 Technical Criteria
Given
Equipment has valid SCAC code and authorized haulage rights
When
The system processes the equipment for haulage validation
Then
The haulage rights flag is set to indicate authorized haulage status
R-GCX146-cbl-00655
Increment Haulage Total Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Haulage Total Counter' is invoked, and assuming that equipment has been validated with haulage rights authorization, when the haulage rights flag is set for the equipment, the desired outcome is that the total haulage counter is incremented by one.
💻 Technical Criteria
Given
Equipment has been validated with haulage rights authorization
When
The haulage rights flag is set for the equipment
Then
The total haulage counter is incremented by one
R-GCX146-cbl-00656
Update Equipment Status as Haulage
Action Rules
📊 Business Logic Narrative
When the process 'Update Equipment Status as Haulage' is invoked, and assuming that equipment has validated haulage rights and the counter has been incremented, when the system updates equipment processing status, the desired outcome is that the equipment status is updated to indicate haulage rights authorization.
💻 Technical Criteria
Given
Equipment has validated haulage rights and the counter has been incremented
When
The system updates equipment processing status
Then
The equipment status is updated to indicate haulage rights authorization
R-GCX146-cbl-00657
Generate SCAC Access Error
Validation Rules
📊 Business Logic Narrative
When the process 'Generate SCAC Access Error' is invoked, and assuming that equipment has an invalid scac code, when the system validates scac code for haulage rights, the desired outcome is that a scac access error is generated indicating invalid authorization.
💻 Technical Criteria
Given
Equipment has an invalid SCAC code
When
The system validates SCAC code for haulage rights
Then
A SCAC access error is generated indicating invalid authorization
R-GCX146-cbl-00658
Set Invalid Haulage Status
Action Rules
📊 Business Logic Narrative
When the process 'Set Invalid Haulage Status' is invoked, and assuming that equipment has valid scac code but lacks haulage rights authorization, when the system processes haulage rights validation, the desired outcome is that the equipment status is set to indicate invalid haulage rights.
💻 Technical Criteria
Given
Equipment has valid SCAC code but lacks haulage rights authorization
When
The system processes haulage rights validation
Then
The equipment status is set to indicate invalid haulage rights
R-GCX146-cbl-00659
Log Validation Failure
Process Rules
📊 Business Logic Narrative
When the process 'Log Validation Failure' is invoked, and assuming that equipment fails either scac validation or haulage rights authorization, when the system encounters validation failure, the desired outcome is that the validation failure is logged for audit and tracking purposes.
💻 Technical Criteria
Given
Equipment fails either SCAC validation or haulage rights authorization
When
The system encounters validation failure
Then
The validation failure is logged for audit and tracking purposes
R-GCX146-cbl-00661
Increment TOTAL-HAULAGE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HAULAGE Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the equipment has haulage flag set to 'y' or manual haulage flag set to 'y', the desired outcome is that the total-haulage counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The equipment has haulage flag set to 'Y' or manual haulage flag set to 'Y'
Then
The TOTAL-HAULAGE counter should be incremented by 1
R-GCX146-cbl-00664
Increment TOTAL-HELD-DOCS Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-DOCS Counter' is invoked, and assuming that an equipment record is being processed for status totals, when the manifest from station equals the manifest to station and the broker entry field is empty, the desired outcome is that the total-held-docs counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for status totals
When
The manifest from station equals the manifest to station and the broker entry field is empty
Then
The TOTAL-HELD-DOCS counter should be incremented by 1
R-GCX146-cbl-00665
Process Equipment Record
Computation Rules
📊 Business Logic Narrative
When the process 'Process Equipment Record' is invoked, and assuming that an equipment record is being processed, when any equipment record is encountered during processing, the desired outcome is that the total-equip counter should be incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed
When
Any equipment record is encountered during processing
Then
The TOTAL-EQUIP counter should be incremented by 1
R-GCX146-cbl-00667
More Equipment Records?
Process Rules
📊 Business Logic Narrative
When the process 'More Equipment Records?' is invoked, and assuming that equipment status processing is in progress, when the current equipment record has been processed and categorized, the desired outcome is that if more equipment records exist in the train consist, continue processing the next record, otherwise proceed to calculate final totals.
💻 Technical Criteria
Given
Equipment status processing is in progress
When
The current equipment record has been processed and categorized
Then
If more equipment records exist in the train consist, continue processing the next record, otherwise proceed to calculate final totals
R-GCX146-cbl-00668
Calculate Final Equipment Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Final Equipment Totals' is invoked, and assuming that all equipment records have been processed and categorized, when no more equipment records remain to be processed, the desired outcome is that all status counters (total-release, total-haulage, total-held-ccra, total-proceed, total-held-docs, total-equip) should be finalized for summary reporting.
💻 Technical Criteria
Given
All equipment records have been processed and categorized
When
No more equipment records remain to be processed
Then
All status counters (TOTAL-RELEASE, TOTAL-HAULAGE, TOTAL-HELD-CCRA, TOTAL-PROCEED, TOTAL-HELD-DOCS, TOTAL-EQUIP) should be finalized for summary reporting
R-GCX146-cbl-00687
US Trip Sheet Required?
Decision Rules
📊 Business Logic Narrative
When the process 'US Trip Sheet Required?' is invoked, and assuming that a trip sheet distribution is in progress, when the system evaluates if us trip sheet is required, the desired outcome is that the system determines us trip sheet requirement based on cargo destination being us territory.
💻 Technical Criteria
Given
A trip sheet distribution is in progress
When
The system evaluates if US trip sheet is required
Then
The system determines US trip sheet requirement based on cargo destination being US territory
R-GCX146-cbl-00734
Set Security Processing Flag
Action Rules
📊 Business Logic Narrative
When the process 'Set Security Processing Flag' is invoked, and assuming that cargo has been identified as requiring special manifest processing, when the special manifest processing is initiated, the desired outcome is that the security processing flag is set to active status.
💻 Technical Criteria
Given
Cargo has been identified as requiring special manifest processing
When
The special manifest processing is initiated
Then
The security processing flag is set to active status
R-GCX146-cbl-00742
Initialize Equipment Status Counters
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Equipment Status Counters' is invoked, and assuming that equipment totals summary generation process is starting, when the system begins processing equipment records for summary totals, the desired outcome is that all equipment status counters (total-release, total-haulage, total-held-ccra, total-proceed, total-held-docs, total-equip, total-docs-nr) are initialized to zero.
💻 Technical Criteria
Given
Equipment totals summary generation process is starting
When
The system begins processing equipment records for summary totals
Then
All equipment status counters (TOTAL-RELEASE, TOTAL-HAULAGE, TOTAL-HELD-CCRA, TOTAL-PROCEED, TOTAL-HELD-DOCS, TOTAL-EQUIP, TOTAL-DOCS-NR) are initialized to zero
R-GCX146-cbl-00743
Increment TOTAL-RELEASE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-RELEASE Counter' is invoked, and assuming that an equipment record is being processed for totals calculation, when the equipment status is 'release' or 'csa-dlv', the desired outcome is that the total-release counter is incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for totals calculation
When
The equipment status is 'RELEASE' or 'CSA-DLV'
Then
The TOTAL-RELEASE counter is incremented by 1
R-GCX146-cbl-00744
Increment TOTAL-HAULAGE Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HAULAGE Counter' is invoked, and assuming that an equipment record is being processed for totals calculation, when the equipment has haulage flag set to 'y' or manual haulage flag set to 'y', the desired outcome is that the total-haulage counter is incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for totals calculation
When
The equipment has haulage flag set to 'Y' or manual haulage flag set to 'Y'
Then
The TOTAL-HAULAGE counter is incremented by 1
R-GCX146-cbl-00745
Increment TOTAL-HELD-CCRA Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-CCRA Counter' is invoked, and assuming that an equipment record is being processed for totals calculation, when the equipment status is 'hold' or 'agi-hold', the desired outcome is that the total-held-ccra counter is incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for totals calculation
When
The equipment status is 'HOLD' or 'AGI-HOLD'
Then
The TOTAL-HELD-CCRA counter is incremented by 1
R-GCX146-cbl-00746
Increment TOTAL-PROCEED Counter
Computation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Increment TOTAL-PROCEED Counter', assuming that an equipment record is being processed for totals calculation, when the equipment has 'return' status or has different manifest from and to stations and the status is not error, reject, or deleted, the desired outcome is that the total-proceed counter is incremented by 1.
💻 Technical Criteria
EXCLUDING
An equipment record is being processed for totals calculation
When
The equipment has 'RETURN' status or has different manifest from and to stations and the status is not error, reject, or deleted
Then
The TOTAL-PROCEED counter is incremented by 1
R-GCX146-cbl-00747
Increment TOTAL-HELD-DOCS Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment TOTAL-HELD-DOCS Counter' is invoked, and assuming that an equipment record is being processed for totals calculation, when the equipment manifest from station equals manifest to station and the broker entry is empty, the desired outcome is that the total-held-docs counter is incremented by 1.
💻 Technical Criteria
Given
An equipment record is being processed for totals calculation
When
The equipment manifest from station equals manifest to station and the broker entry is empty
Then
The TOTAL-HELD-DOCS counter is incremented by 1
R-GCX146-cbl-00748
Calculate Summary Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Calculate Summary Totals' is invoked, and assuming that all equipment records have been processed and individual counters updated, when the system completes processing all equipment in the train, the desired outcome is that final summary totals are calculated including total-equip as the sum of all equipment processed.
💻 Technical Criteria
Given
All equipment records have been processed and individual counters updated
When
The system completes processing all equipment in the train
Then
Final summary totals are calculated including TOTAL-EQUIP as the sum of all equipment processed
R-GCX146-cbl-00749
Format Totals for Trip Sheet Display
Process Rules
📊 Business Logic Narrative
When the process 'Format Totals for Trip Sheet Display' is invoked, and assuming that equipment summary totals have been calculated, when a trip sheet report is being generated, the desired outcome is that equipment totals are formatted with appropriate labels and numeric formatting for trip sheet display.
💻 Technical Criteria
Given
Equipment summary totals have been calculated
When
A trip sheet report is being generated
Then
Equipment totals are formatted with appropriate labels and numeric formatting for trip sheet display
R-GCX146-cbl-00750
Format Totals for Status Report Display
Process Rules
📊 Business Logic Narrative
When the process 'Format Totals for Status Report Display' is invoked, and assuming that equipment summary totals have been calculated, when a status report is being generated, the desired outcome is that equipment totals are formatted with appropriate labels and descriptions for status report display.
💻 Technical Criteria
Given
Equipment summary totals have been calculated
When
A status report is being generated
Then
Equipment totals are formatted with appropriate labels and descriptions for status report display
R-GCX146-cbl-00751
Generate Equipment Summary Lines
Process Rules
📊 Business Logic Narrative
When the process 'Generate Equipment Summary Lines' is invoked, and assuming that equipment totals have been formatted for display, when report generation requires equipment summary information, the desired outcome is that formatted summary lines are generated showing totals for released, held, proceeding, and other equipment categories.
💻 Technical Criteria
Given
Equipment totals have been formatted for display
When
Report generation requires equipment summary information
Then
Formatted summary lines are generated showing totals for released, held, proceeding, and other equipment categories
R-GCX146-cbl-00753
Set Equipment Type Codes
Action Rules
📊 Business Logic Narrative
When the process 'Set Equipment Type Codes' is invoked, and assuming that equipment records exist in the train manifest, when processing equipment for edi transmission, the desired outcome is that the system invokes gcccartp module to determine and assign appropriate equipment type codes for each piece of equipment.
💻 Technical Criteria
Given
Equipment records exist in the train manifest
When
Processing equipment for EDI transmission
Then
The system invokes GCCCARTP module to determine and assign appropriate equipment type codes for each piece of equipment
R-GCX146-cbl-00754
Assign Load/Empty Status
Decision Rules
📊 Business Logic Narrative
When the process 'Assign Load/Empty Status' is invoked, and assuming that equipment records with cargo information are available, when processing equipment status for edi transmission, the desired outcome is that the system assigns 'l' for loaded equipment with cargo and 'e' for empty equipment without cargo.
💻 Technical Criteria
Given
Equipment records with cargo information are available
When
Processing equipment status for EDI transmission
Then
The system assigns 'L' for loaded equipment with cargo and 'E' for empty equipment without cargo
R-GCX146-cbl-00756
Process Container Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process Container Equipment' is invoked, and assuming that equipment type is identified as container, when processing container equipment for edi transmission, the desired outcome is that the system extracts container-specific data including container ids, cross-references, and formats them according to edi container standards.
💻 Technical Criteria
Given
Equipment type is identified as container
When
Processing container equipment for EDI transmission
Then
The system extracts container-specific data including container IDs, cross-references, and formats them according to EDI container standards
R-GCX146-cbl-00757
Process Trailer Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process Trailer Equipment' is invoked, and assuming that equipment type is identified as trailer, when processing trailer equipment for edi transmission, the desired outcome is that the system extracts trailer-specific data and formats it according to edi trailer equipment standards.
💻 Technical Criteria
Given
Equipment type is identified as trailer
When
Processing trailer equipment for EDI transmission
Then
The system extracts trailer-specific data and formats it according to EDI trailer equipment standards
R-GCX146-cbl-00758
Process Rail Car Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process Rail Car Equipment' is invoked, and assuming that equipment type is identified as rail car, when processing rail car equipment for edi transmission, the desired outcome is that the system extracts rail car specific data including car type, specifications, and formats them according to edi rail car standards.
💻 Technical Criteria
Given
Equipment type is identified as rail car
When
Processing rail car equipment for EDI transmission
Then
The system extracts rail car specific data including car type, specifications, and formats them according to EDI rail car standards
R-GCX146-cbl-00760
Add to EDI Transmission Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Add to EDI Transmission Buffer' is invoked, and assuming that edi equipment records are constructed and validated, when adding records to transmission buffer, the desired outcome is that the system adds each completed equipment record to the edi transmission buffer maintaining proper sequence and format.
💻 Technical Criteria
Given
EDI equipment records are constructed and validated
When
Adding records to transmission buffer
Then
The system adds each completed equipment record to the EDI transmission buffer maintaining proper sequence and format
R-GCX146-cbl-00761
More Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment?' is invoked, and assuming that equipment records are being processed for edi transmission, when checking for remaining equipment to process, the desired outcome is that the system continues processing if more equipment records exist, otherwise proceeds to finalize the edi message.
💻 Technical Criteria
Given
Equipment records are being processed for EDI transmission
When
Checking for remaining equipment to process
Then
The system continues processing if more equipment records exist, otherwise proceeds to finalize the EDI message
R-GCX146-cbl-00762
Finalize EDI Message
Process Rules
📊 Business Logic Narrative
When the process 'Finalize EDI Message' is invoked, and assuming that all equipment records have been processed and added to transmission buffer, when finalizing the edi message for transmission, the desired outcome is that the system adds edi trailer records, calculates control totals, and prepares the complete message for customs transmission.
💻 Technical Criteria
Given
All equipment records have been processed and added to transmission buffer
When
Finalizing the EDI message for transmission
Then
The system adds EDI trailer records, calculates control totals, and prepares the complete message for customs transmission
R-GCX146-cbl-00764
Log EDI Transmission
Process Rules
📊 Business Logic Narrative
When the process 'Log EDI Transmission' is invoked, and assuming that edi transmission to customs systems has been completed, when logging transmission activity, the desired outcome is that the system records transmission timestamp, message identifier, equipment count, and transmission status in audit logs.
💻 Technical Criteria
Given
EDI transmission to customs systems has been completed
When
Logging transmission activity
Then
The system records transmission timestamp, message identifier, equipment count, and transmission status in audit logs
R-GCX146-cbl-00766
All Equipment Processed Successfully?
Decision Rules
📊 Business Logic Narrative
When the process 'All Equipment Processed Successfully?' is invoked, and assuming that train processing has completed and equipment processing status needs verification, when the system evaluates equipment processing results, the desired outcome is that if all equipment processed successfully, proceed to confirmation generation, otherwise skip confirmation due to processing errors.
💻 Technical Criteria
Given
Train processing has completed and equipment processing status needs verification
When
The system evaluates equipment processing results
Then
If all equipment processed successfully, proceed to confirmation generation, otherwise skip confirmation due to processing errors
R-GCX146-cbl-00768
Compile Equipment Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Compile Equipment Totals' is invoked, and assuming that train summary data has been gathered successfully, when the system compiles equipment totals, the desired outcome is that equipment counts are calculated by status (released, held, proceeding, haulage, documents not required) for confirmation reporting.
💻 Technical Criteria
Given
Train summary data has been gathered successfully
When
The system compiles equipment totals
Then
Equipment counts are calculated by status (released, held, proceeding, haulage, documents not required) for confirmation reporting
R-GCX146-cbl-00769
Format Confirmation Message
Process Rules
📊 Business Logic Narrative
When the process 'Format Confirmation Message' is invoked, and assuming that train summary data and equipment totals have been compiled, when the system formats the confirmation message, the desired outcome is that message is structured with proper headers, train details, equipment summaries, and processing timestamps in standard confirmation format.
💻 Technical Criteria
Given
Train summary data and equipment totals have been compiled
When
The system formats the confirmation message
Then
Message is structured with proper headers, train details, equipment summaries, and processing timestamps in standard confirmation format
R-GCX146-cbl-00771
Include Equipment Count Summary
Process Rules
📊 Business Logic Narrative
When the process 'Include Equipment Count Summary' is invoked, and assuming that train identification has been included in confirmation message, when the system includes equipment count summary, the desired outcome is that equipment totals by status (total equipment, released, held by ccra, held for documents, proceeding, haulage, documents not required) are included in confirmation message.
💻 Technical Criteria
Given
Train identification has been included in confirmation message
When
The system includes equipment count summary
Then
Equipment totals by status (total equipment, released, held by CCRA, held for documents, proceeding, haulage, documents not required) are included in confirmation message
R-GCX146-cbl-00772
Include Processing Timestamp
Process Rules
📊 Business Logic Narrative
When the process 'Include Processing Timestamp' is invoked, and assuming that equipment count summary has been included in confirmation message, when the system includes processing timestamp, the desired outcome is that current processing date, time, and user identification are included in confirmation message for tracking and audit purposes.
💻 Technical Criteria
Given
Equipment count summary has been included in confirmation message
When
The system includes processing timestamp
Then
Current processing date, time, and user identification are included in confirmation message for tracking and audit purposes
R-GCX146-cbl-00777
Skip Confirmation - Errors Exist
Decision Rules
📊 Business Logic Narrative
When the process 'Skip Confirmation - Errors Exist' is invoked, and assuming that train processing has completed but equipment processing errors were detected, when the system evaluates confirmation generation eligibility, the desired outcome is that confirmation message generation is skipped and processing proceeds to completion without sending confirmation due to processing errors.
💻 Technical Criteria
Given
Train processing has completed but equipment processing errors were detected
When
The system evaluates confirmation generation eligibility
Then
Confirmation message generation is skipped and processing proceeds to completion without sending confirmation due to processing errors
R-GCX146-cbl-00778
Determine Equipment Category
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Equipment Category' is invoked, and assuming that equipment information is retrieved from equipment records, when the system analyzes the equipment identification and characteristics, the desired outcome is that the equipment is categorized as container, trailer, or car for subsequent type code processing.
💻 Technical Criteria
Given
Equipment information is retrieved from equipment records
When
The system analyzes the equipment identification and characteristics
Then
The equipment is categorized as Container, Trailer, or Car for subsequent type code processing
R-GCX146-cbl-00779
Container Equipment Processing
Process Rules
📊 Business Logic Narrative
When the process 'Container Equipment Processing' is invoked, and assuming that equipment is categorized as a container, when container equipment processing is initiated, the desired outcome is that container-specific type code determination logic is applied before calling gcccartp module.
💻 Technical Criteria
Given
Equipment is categorized as a container
When
Container equipment processing is initiated
Then
Container-specific type code determination logic is applied before calling GCCCARTP module
R-GCX146-cbl-00780
Trailer Equipment Processing
Process Rules
📊 Business Logic Narrative
When the process 'Trailer Equipment Processing' is invoked, and assuming that equipment is categorized as a trailer, when trailer equipment processing is initiated, the desired outcome is that trailer-specific type code determination logic is applied before calling gcccartp module.
💻 Technical Criteria
Given
Equipment is categorized as a trailer
When
Trailer equipment processing is initiated
Then
Trailer-specific type code determination logic is applied before calling GCCCARTP module
R-GCX146-cbl-00781
Car Equipment Processing
Process Rules
📊 Business Logic Narrative
When the process 'Car Equipment Processing' is invoked, and assuming that equipment is categorized as a car, when car equipment processing is initiated, the desired outcome is that car-specific type code determination logic is applied before calling gcccartp module.
💻 Technical Criteria
Given
Equipment is categorized as a car
When
Car equipment processing is initiated
Then
Car-specific type code determination logic is applied before calling GCCCARTP module
R-GCX146-cbl-00782
Call GCCCARTP Module
Action Rules
📊 Business Logic Narrative
When the process 'Call GCCCARTP Module' is invoked, and assuming that equipment has been processed according to its category (container, trailer, or car), when type code assignment is required, the desired outcome is that gcccartp module is called to determine and assign the appropriate equipment type code.
💻 Technical Criteria
Given
Equipment has been processed according to its category (Container, Trailer, or Car)
When
Type code assignment is required
Then
GCCCARTP module is called to determine and assign the appropriate equipment type code
R-GCX146-cbl-00783
Validate Type Code Assignment
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Type Code Assignment' is invoked, and assuming that an equipment type code has been assigned by the gcccartp module, when type code validation is performed, the desired outcome is that the system verifies the type code is valid according to business rules and data constraints.
💻 Technical Criteria
Given
An equipment type code has been assigned by the GCCCARTP module
When
Type code validation is performed
Then
The system verifies the type code is valid according to business rules and data constraints
R-GCX146-cbl-00784
Set Equipment Type for EDI
Process Rules
📊 Business Logic Narrative
When the process 'Set Equipment Type for EDI' is invoked, and assuming that equipment type code has been validated successfully, when edi processing is required, the desired outcome is that the validated equipment type code is set for edi transmission.
💻 Technical Criteria
Given
Equipment type code has been validated successfully
When
EDI processing is required
Then
The validated equipment type code is set for EDI transmission
R-GCX146-cbl-00785
Handle Type Code Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Handle Type Code Error', assuming that equipment type code validation fails, when an invalid type code is detected, the desired outcome is that error handling procedures are initiated to address the type code assignment failure.
💻 Technical Criteria
EXCLUDING
Equipment type code validation fails
When
An invalid type code is detected
Then
Error handling procedures are initiated to address the type code assignment failure
R-GCX146-cbl-00789
Container Load/Empty Assignment
Process Rules
📊 Business Logic Narrative
When the process 'Container Load/Empty Assignment' is invoked, and assuming that equipment has been classified as container type, when load/empty status needs to be assigned to the container, the desired outcome is that apply container-specific rules to determine and assign load or empty status.
💻 Technical Criteria
Given
Equipment has been classified as container type
When
Load/empty status needs to be assigned to the container
Then
Apply container-specific rules to determine and assign load or empty status
R-GCX146-cbl-00790
Trailer Load/Empty Assignment
Process Rules
📊 Business Logic Narrative
When the process 'Trailer Load/Empty Assignment' is invoked, and assuming that equipment has been classified as trailer type, when load/empty status needs to be assigned to the trailer, the desired outcome is that apply trailer-specific rules to determine and assign load or empty status.
💻 Technical Criteria
Given
Equipment has been classified as trailer type
When
Load/empty status needs to be assigned to the trailer
Then
Apply trailer-specific rules to determine and assign load or empty status
R-GCX146-cbl-00791
Rail Car Load/Empty Assignment
Process Rules
📊 Business Logic Narrative
When the process 'Rail Car Load/Empty Assignment' is invoked, and assuming that equipment has been classified as rail car type, when load/empty status needs to be assigned to the rail car, the desired outcome is that apply rail car-specific rules to determine and assign load or empty status.
💻 Technical Criteria
Given
Equipment has been classified as rail car type
When
Load/empty status needs to be assigned to the rail car
Then
Apply rail car-specific rules to determine and assign load or empty status
R-GCX146-cbl-00792
Validate Status Against Equipment Type
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Status Against Equipment Type' is invoked, and assuming that load/empty status has been determined for equipment, when status assignment is validated against equipment type constraints, the desired outcome is that verify that the assigned status is valid for the specific equipment type and reject invalid combinations.
💻 Technical Criteria
Given
Load/empty status has been determined for equipment
When
Status assignment is validated against equipment type constraints
Then
Verify that the assigned status is valid for the specific equipment type and reject invalid combinations
R-GCX146-cbl-00793
Set EDI Load/Empty Indicator
Action Rules
📊 Business Logic Narrative
When the process 'Set EDI Load/Empty Indicator' is invoked, and assuming that final load/empty status has been assigned to equipment, when edi transmission requires load/empty indicator, the desired outcome is that convert the internal status to the appropriate edi load/empty indicator format.
💻 Technical Criteria
Given
Final load/empty status has been assigned to equipment
When
EDI transmission requires load/empty indicator
Then
Convert the internal status to the appropriate EDI load/empty indicator format
R-GCX146-cbl-00794
Status Assignment Error
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Status Assignment Error', assuming that load/empty status assignment process encounters an error condition, when status cannot be determined or is invalid for the equipment type, the desired outcome is that generate appropriate error message and handle the equipment record according to error processing rules.
💻 Technical Criteria
EXCLUDING
Load/empty status assignment process encounters an error condition
When
Status cannot be determined or is invalid for the equipment type
Then
Generate appropriate error message and handle the equipment record according to error processing rules
R-GCX146-cbl-00799
Status = 'T' Transit?
Decision Rules
📊 Business Logic Narrative
When the process 'Status = 'T' Transit?' is invoked, and assuming that a transit status code is available for evaluation, when the transit status code equals 't', the desired outcome is that the system classifies the cargo as in transit status.
💻 Technical Criteria
Given
A transit status code is available for evaluation
When
The transit status code equals 'T'
Then
The system classifies the cargo as in transit status
R-GCX146-cbl-00800
Status = 'R' Return?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Status = 'R' Return?', assuming that a transit status code is available for evaluation and is not 't', when the transit status code equals 'r', the desired outcome is that the system classifies the cargo as return status.
💻 Technical Criteria
EXCLUDING
A transit status code is available for evaluation and is not 'T'
When
The transit status code equals 'R'
Then
The system classifies the cargo as return status
R-GCX146-cbl-00801
Status = 'E' Export?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Status = 'E' Export?', assuming that a transit status code is available for evaluation and is not 't' or 'r', when the transit status code equals 'e', the desired outcome is that the system classifies the cargo as export status.
💻 Technical Criteria
EXCLUDING
A transit status code is available for evaluation and is not 'T' or 'R'
When
The transit status code equals 'E'
Then
The system classifies the cargo as export status
R-GCX146-cbl-00802
Status = 'Z' Export?
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Status = 'Z' Export?', assuming that a transit status code is available for evaluation and is not 't', 'r', or 'e', when the transit status code equals 'z', the desired outcome is that the system classifies the cargo as export status.
💻 Technical Criteria
EXCLUDING
A transit status code is available for evaluation and is not 'T', 'R', or 'E'
When
The transit status code equals 'Z'
Then
The system classifies the cargo as export status
R-GCX146-cbl-00806
Check S.A.R. Release Flag
Decision Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Check S.A.R. Release Flag', assuming that the transit status code is not 't', 'r', 'e', or 'z', when the system evaluates the s.a.r. release flag, the desired outcome is that the system determines if cargo has special administrative release authorization.
💻 Technical Criteria
EXCLUDING
The transit status code is not 'T', 'R', 'E', or 'Z'
When
The system evaluates the S.A.R. release flag
Then
The system determines if cargo has special administrative release authorization
R-GCX146-cbl-00807
S.A.R. Release?
Decision Rules
📊 Business Logic Narrative
When the process 'S.A.R. Release?' is invoked, and assuming that the s.a.r. release flag has been evaluated, when the cargo has s.a.r. release authorization, the desired outcome is that the system classifies the cargo for s.a.r. release processing.
💻 Technical Criteria
Given
The S.A.R. release flag has been evaluated
When
The cargo has S.A.R. release authorization
Then
The system classifies the cargo for S.A.R. release processing
R-GCX146-cbl-00808
Set Status to 'S.A.R.'
Action Rules
📊 Business Logic Narrative
When the process 'Set Status to 'S.A.R.'' is invoked, and assuming that the cargo has been determined to have s.a.r. release authorization, when the system processes the s.a.r. classification, the desired outcome is that the system sets the status to 's.a.r.'.
💻 Technical Criteria
Given
The cargo has been determined to have S.A.R. release authorization
When
The system processes the S.A.R. classification
Then
The system sets the status to 'S.A.R.'
R-GCX146-cbl-00809
Set Status to 'RELEASE'
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Status to 'RELEASE'', assuming that the cargo has been determined to not have s.a.r. release authorization, when the system processes the release classification, the desired outcome is that the system sets the status to 'release'.
💻 Technical Criteria
EXCLUDING
The cargo has been determined to not have S.A.R. release authorization
When
The system processes the release classification
Then
The system sets the status to 'RELEASE'
R-GCX146-cbl-00813
Apply Standard Formatting Rules
Process Rules
📊 Business Logic Narrative
When the process 'Apply Standard Formatting Rules' is invoked, and assuming that an equipment car id is provided for processing, when the car id has a valid format, the desired outcome is that standard formatting rules are applied to normalize the car id.
💻 Technical Criteria
Given
An equipment car ID is provided for processing
When
The car ID has a valid format
Then
Standard formatting rules are applied to normalize the car ID
R-GCX146-cbl-00814
Remove Spaces and Special Characters
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces and Special Characters' is invoked, and assuming that an equipment car id contains spaces or special characters, when the car id is being formatted for train manifest, the desired outcome is that all spaces and special characters are removed from the car id.
💻 Technical Criteria
Given
An equipment car ID contains spaces or special characters
When
The car ID is being formatted for train manifest
Then
All spaces and special characters are removed from the car ID
R-GCX146-cbl-00815
Pad with Zeros if Needed
Validation Rules
📊 Business Logic Narrative
When the process 'Pad with Zeros if Needed' is invoked, and assuming that an equipment car id is shorter than the required length, when the car id is being formatted for train manifest display, the desired outcome is that the car id is padded with leading zeros to meet the standard length requirement.
💻 Technical Criteria
Given
An equipment car ID is shorter than the required length
When
The car ID is being formatted for train manifest display
Then
The car ID is padded with leading zeros to meet the standard length requirement
R-GCX146-cbl-00816
Convert to Uppercase
Validation Rules
📊 Business Logic Narrative
When the process 'Convert to Uppercase' is invoked, and assuming that an equipment car id contains lowercase characters, when the car id is being processed for train manifest, the desired outcome is that all characters in the car id are converted to uppercase.
💻 Technical Criteria
Given
An equipment car ID contains lowercase characters
When
The car ID is being processed for train manifest
Then
All characters in the car ID are converted to uppercase
R-GCX146-cbl-00817
Validate Length Requirements
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Length Requirements' is invoked, and assuming that an equipment car id has been formatted, when the length validation is performed, the desired outcome is that the car id length must meet the standard requirements for valid processing.
💻 Technical Criteria
Given
An equipment car ID has been formatted
When
The length validation is performed
Then
The car ID length must meet the standard requirements for valid processing
R-GCX146-cbl-00818
Format for Train Manifest Display
Process Rules
📊 Business Logic Narrative
When the process 'Format for Train Manifest Display' is invoked, and assuming that an equipment car id has passed length validation, when the car id is prepared for train manifest display, the desired outcome is that the car id is formatted according to train manifest display standards.
💻 Technical Criteria
Given
An equipment car ID has passed length validation
When
The car ID is prepared for train manifest display
Then
The car ID is formatted according to train manifest display standards
R-GCX146-cbl-00819
Set Equipment Type Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Set Equipment Type Code' is invoked, and assuming that an equipment car id has been formatted for train manifest display, when equipment type classification is required, the desired outcome is that the appropriate equipment type code is assigned based on car id characteristics.
💻 Technical Criteria
Given
An equipment car ID has been formatted for train manifest display
When
Equipment type classification is required
Then
The appropriate equipment type code is assigned based on car ID characteristics
R-GCX146-cbl-00820
Format Error - Use Default
Decision Rules
📊 Business Logic Narrative
When the process 'Format Error - Use Default' is invoked, and assuming that an equipment car id fails format validation or length requirements, when standard formatting cannot be applied successfully, the desired outcome is that a default format is used to ensure the car id can still be processed.
💻 Technical Criteria
Given
An equipment car ID fails format validation or length requirements
When
Standard formatting cannot be applied successfully
Then
A default format is used to ensure the car ID can still be processed
R-GCX146-cbl-01339
Process Equipment Report Lines
Process Rules
📊 Business Logic Narrative
When the process 'Process Equipment Report Lines' is invoked, and assuming that report header has been added to email message, when the system processes equipment data for the report, the desired outcome is that generate detailed report lines for each equipment item including status, location, and relevant business information.
💻 Technical Criteria
Given
Report header has been added to email message
When
The system processes equipment data for the report
Then
Generate detailed report lines for each equipment item including status, location, and relevant business information
R-GCX146-cbl-01340
Within Line Limit ≤ 699 lines?
Validation Rules
📊 Business Logic Narrative
When the process 'Within Line Limit ≤ 699 lines?' is invoked, and assuming that equipment report lines are being processed for email, when the system checks the current line count in the email message, the desired outcome is that if line count is 699 or less, continue adding equipment details, otherwise finalize current message and prepare for continuation.
💻 Technical Criteria
Given
Equipment report lines are being processed for email
When
The system checks the current line count in the email message
Then
If line count is 699 or less, continue adding equipment details, otherwise finalize current message and prepare for continuation
R-GCX146-cbl-01341
Add Equipment Details to Email
Process Rules
📊 Business Logic Narrative
When the process 'Add Equipment Details to Email' is invoked, and assuming that email message is within the 699 line limit, when the system processes equipment details for inclusion, the desired outcome is that add equipment details including car id, status, location, and other relevant business information to the email message.
💻 Technical Criteria
Given
Email message is within the 699 line limit
When
The system processes equipment details for inclusion
Then
Add equipment details including car ID, status, location, and other relevant business information to the email message
R-GCX146-cbl-01342
More Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment?' is invoked, and assuming that current equipment item has been processed, when the system checks for additional equipment in the report queue, the desired outcome is that if more equipment exists, continue processing next item, otherwise proceed to finalize the email message.
💻 Technical Criteria
Given
Current equipment item has been processed
When
The system checks for additional equipment in the report queue
Then
If more equipment exists, continue processing next item, otherwise proceed to finalize the email message
R-GCX146-cbl-01343
Finalize Email Message
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Email Message' is invoked, and assuming that all equipment processing is complete or line limit reached, when the system finalizes the email message, the desired outcome is that add any closing information, format the message properly, and prepare for email transmission.
💻 Technical Criteria
Given
All equipment processing is complete or line limit reached
When
The system finalizes the email message
Then
Add any closing information, format the message properly, and prepare for email transmission
R-GCX146-cbl-01816
Email User ID Present?
Validation Rules
📊 Business Logic Narrative
When the process 'Email User ID Present?' is invoked, and assuming that station configuration data has been retrieved, when the system checks for email user id configuration, the desired outcome is that the system should determine if an email user id is present and not empty in the configuration.
💻 Technical Criteria
Given
Station configuration data has been retrieved
When
The system checks for email user ID configuration
Then
The system should determine if an email user ID is present and not empty in the configuration
R-GCX146-cbl-01353
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that an email batch has been successfully sent, when preparing for continuation message processing, the desired outcome is that the system should reset the message buffer to empty state.
💻 Technical Criteria
Given
An email batch has been successfully sent
When
Preparing for continuation message processing
Then
The system should reset the message buffer to empty state
R-GCX146-cbl-01369
Format Equipment Details
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Details' is invoked, and assuming that station information has been added to the message, when equipment details need to be formatted, the desired outcome is that equipment ids, car types, and related information are formatted for inclusion in the message.
💻 Technical Criteria
Given
Station information has been added to the message
When
Equipment details need to be formatted
Then
Equipment IDs, car types, and related information are formatted for inclusion in the message
R-GCX146-cbl-01370
Container Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'Container Equipment?' is invoked, and assuming that equipment details are being formatted, when the system evaluates the equipment type, the desired outcome is that if the equipment is container equipment, container-specific formatting is applied, otherwise standard equipment formatting is used.
💻 Technical Criteria
Given
Equipment details are being formatted
When
The system evaluates the equipment type
Then
If the equipment is container equipment, container-specific formatting is applied, otherwise standard equipment formatting is used
R-GCX146-cbl-01371
Format Container Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Container Information' is invoked, and assuming that equipment has been identified as container equipment, when container information needs to be formatted, the desired outcome is that container-specific details including container ids and attributes are formatted for the message.
💻 Technical Criteria
Given
Equipment has been identified as container equipment
When
Container information needs to be formatted
Then
Container-specific details including container IDs and attributes are formatted for the message
R-GCX146-cbl-01372
Format Standard Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Format Standard Equipment' is invoked, and assuming that equipment has been identified as standard (non-container) equipment, when standard equipment information needs to be formatted, the desired outcome is that standard equipment details are formatted using regular equipment formatting rules.
💻 Technical Criteria
Given
Equipment has been identified as standard (non-container) equipment
When
Standard equipment information needs to be formatted
Then
Standard equipment details are formatted using regular equipment formatting rules
R-GCX146-cbl-01373
Add Load/Empty Status
Process Rules
📊 Business Logic Narrative
When the process 'Add Load/Empty Status' is invoked, and assuming that equipment information has been formatted (either container or standard), when load status needs to be added to equipment details, the desired outcome is that the appropriate load/empty indicator is added to each equipment entry.
💻 Technical Criteria
Given
Equipment information has been formatted (either container or standard)
When
Load status needs to be added to equipment details
Then
The appropriate load/empty indicator is added to each equipment entry
R-GCX146-cbl-01376
Message Line Limit Reached?
Validation Rules
📊 Business Logic Narrative
When the process 'Message Line Limit Reached?' is invoked, and assuming that equipment type messages have been formatted, when the system checks the current message line count, the desired outcome is that if the line limit has been reached, the message is prepared for segmentation, otherwise formatting continues.
💻 Technical Criteria
Given
Equipment type messages have been formatted
When
The system checks the current message line count
Then
If the line limit has been reached, the message is prepared for segmentation, otherwise formatting continues
R-GCX146-cbl-01835
Reset Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Reset Message Buffer' is invoked, and assuming that a completed email segment has been sent, when the system prepares for the next segment, the desired outcome is that the message buffer is reset to empty state for new content.
💻 Technical Criteria
Given
A completed email segment has been sent
When
The system prepares for the next segment
Then
The message buffer is reset to empty state for new content
R-GCX146-cbl-00864
Extract Shipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Shipment Information' is invoked, and assuming that equipment details have been successfully extracted, when the system processes shipment-specific data, the desired outcome is that the system extracts shipment information including shipper, consignee, origin station, destination station, and cargo details.
💻 Technical Criteria
Given
Equipment details have been successfully extracted
When
The system processes shipment-specific data
Then
The system extracts shipment information including shipper, consignee, origin station, destination station, and cargo details
R-GCX146-cbl-00867
Access Container Records via FWSWRWR
Action Rules
📊 Business Logic Narrative
When the process 'Access Container Records via FWSWRWR' is invoked, and assuming that a container equipment processing request is initiated, when the system attempts to access container records via fwswrwr database, the desired outcome is that container equipment records are retrieved for further processing.
💻 Technical Criteria
Given
A container equipment processing request is initiated
When
The system attempts to access container records via FWSWRWR database
Then
Container equipment records are retrieved for further processing
R-GCX146-cbl-00868
Container Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Container Record Found?' is invoked, and assuming that container records have been accessed from fwswrwr database, when the system checks for the existence of container records, the desired outcome is that if container records are found, proceed to extract container information, otherwise access container inquiry database.
💻 Technical Criteria
Given
Container records have been accessed from FWSWRWR database
When
The system checks for the existence of container records
Then
If container records are found, proceed to extract container information, otherwise access container inquiry database
R-GCX146-cbl-00869
Extract Container Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Container Information' is invoked, and assuming that container records exist in the fwswrwr database, when the system processes the container records, the desired outcome is that container information is extracted and made available for further processing.
💻 Technical Criteria
Given
Container records exist in the FWSWRWR database
When
The system processes the container records
Then
Container information is extracted and made available for further processing
R-GCX146-cbl-00870
Set Flat Car Processing Flag
Process Rules
📊 Business Logic Narrative
When the process 'Set Flat Car Processing Flag' is invoked, and assuming that container information has been successfully extracted, when the system processes container equipment on flat cars, the desired outcome is that the flat car processing flag is set to indicate active container processing.
💻 Technical Criteria
Given
Container information has been successfully extracted
When
The system processes container equipment on flat cars
Then
The flat car processing flag is set to indicate active container processing
R-GCX146-cbl-00871
Access Container Inquiry Database
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Access Container Inquiry Database', assuming that container records are not found in fwswrwr database, when the system needs to locate container information, the desired outcome is that the system accesses the fw-iq container inquiry database as an alternative source.
💻 Technical Criteria
EXCLUDING
Container records are not found in FWSWRWR database
When
The system needs to locate container information
Then
The system accesses the FW-IQ container inquiry database as an alternative source
R-GCX146-cbl-00872
Retrieve T/C XREF Records
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve T/C XREF Records' is invoked, and assuming that container inquiry database has been accessed, when the system processes container cross-reference requirements, the desired outcome is that t/c xref records are retrieved to establish container id relationships.
💻 Technical Criteria
Given
Container inquiry database has been accessed
When
The system processes container cross-reference requirements
Then
T/C XREF records are retrieved to establish container ID relationships
R-GCX146-cbl-00873
Container ID Available?
Validation Rules
📊 Business Logic Narrative
When the process 'Container ID Available?' is invoked, and assuming that t/c xref records have been retrieved, when the system checks for container id availability, the desired outcome is that if container id is available, extract it from xref records, otherwise report container processing error.
💻 Technical Criteria
Given
T/C XREF records have been retrieved
When
The system checks for container ID availability
Then
If container ID is available, extract it from XREF records, otherwise report container processing error
R-GCX146-cbl-00880
Initialize Equipment Sequence Counter
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Equipment Sequence Counter' is invoked, and assuming that equipment segment processing is starting, when the system begins processing equipment records, the desired outcome is that the equipment sequence counter is set to 1 to track the first equipment position.
💻 Technical Criteria
Given
Equipment segment processing is starting
When
The system begins processing equipment records
Then
The equipment sequence counter is set to 1 to track the first equipment position
R-GCX146-cbl-00882
Equipment Record Found?
Validation Rules
📊 Business Logic Narrative
When the process 'Equipment Record Found?' is invoked, and assuming that a database call has been made to retrieve equipment data, when the system checks the return status from the database call, the desired outcome is that if the return code is zero, the equipment record exists and processing continues, otherwise an equipment segment error occurs.
💻 Technical Criteria
Given
A database call has been made to retrieve equipment data
When
The system checks the return status from the database call
Then
If the return code is zero, the equipment record exists and processing continues, otherwise an equipment segment error occurs
R-GCX146-cbl-00883
Process Current Equipment Data
Process Rules
📊 Business Logic Narrative
When the process 'Process Current Equipment Data' is invoked, and assuming that a valid equipment record has been retrieved from the database, when the system processes the equipment data, the desired outcome is that equipment details are extracted and stored for further processing including equipment id, car type, and status information.
💻 Technical Criteria
Given
A valid equipment record has been retrieved from the database
When
The system processes the equipment data
Then
Equipment details are extracted and stored for further processing including equipment ID, car type, and status information
R-GCX146-cbl-00884
Increment Sequence Counter
Process Rules
📊 Business Logic Narrative
When the process 'Increment Sequence Counter' is invoked, and assuming that current equipment data has been processed and stored, when the system completes processing of the current equipment record, the desired outcome is that the equipment sequence counter is incremented by 1 to point to the next equipment position.
💻 Technical Criteria
Given
Current equipment data has been processed and stored
When
The system completes processing of the current equipment record
Then
The equipment sequence counter is incremented by 1 to point to the next equipment position
R-GCX146-cbl-00886
More Equipment in Sequence?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment in Sequence?' is invoked, and assuming that a call has been made to retrieve the next equipment record, when the system evaluates the return status from the database call, the desired outcome is that if return code is zero, more equipment exists and processing continues with the next record, otherwise check for additional cars in bunch bill.
💻 Technical Criteria
Given
A call has been made to retrieve the next equipment record
When
The system evaluates the return status from the database call
Then
If return code is zero, more equipment exists and processing continues with the next record, otherwise check for additional cars in bunch bill
R-GCX146-cbl-00887
Additional Cars in Bunch Bill?
Decision Rules
📊 Business Logic Narrative
When the process 'Additional Cars in Bunch Bill?' is invoked, and assuming that no more equipment records exist in the current sequence, when the system checks for bunch bill processing requirements, the desired outcome is that if additional cars exist in the bunch bill, processing continues with the additional car sequence, otherwise equipment segment processing is complete.
💻 Technical Criteria
Given
No more equipment records exist in the current sequence
When
The system checks for bunch bill processing requirements
Then
If additional cars exist in the bunch bill, processing continues with the additional car sequence, otherwise equipment segment processing is complete
R-GCX146-cbl-00888
Process Additional Car Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Process Additional Car Sequence' is invoked, and assuming that additional cars exist in a bunch bill arrangement, when the system processes the additional car sequence, the desired outcome is that the sequence counter is reset and processing continues with the next group of cars in the bunch bill.
💻 Technical Criteria
Given
Additional cars exist in a bunch bill arrangement
When
The system processes the additional car sequence
Then
The sequence counter is reset and processing continues with the next group of cars in the bunch bill
R-GCX146-cbl-00889
Initialize Equipment Records
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Equipment Records' is invoked, and assuming that a train processing request is received, when equipment list building begins, the desired outcome is that equipment counters are reset to zero and processing flags are initialized.
💻 Technical Criteria
Given
A train processing request is received
When
Equipment list building begins
Then
Equipment counters are reset to zero and processing flags are initialized
R-GCX146-cbl-00890
Process Equipment Segment
Process Rules
📊 Business Logic Narrative
When the process 'Process Equipment Segment' is invoked, and assuming that equipment segments exist in the train consist, when processing equipment for manifest building, the desired outcome is that each equipment segment is processed sequentially with proper error handling.
💻 Technical Criteria
Given
Equipment segments exist in the train consist
When
Processing equipment for manifest building
Then
Each equipment segment is processed sequentially with proper error handling
R-GCX146-cbl-00891
Retrieve Next Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Equipment Record' is invoked, and assuming that equipment processing is in progress, when retrieving equipment records from the database, the desired outcome is that the next equipment record is retrieved and continuation status is determined.
💻 Technical Criteria
Given
Equipment processing is in progress
When
Retrieving equipment records from the database
Then
The next equipment record is retrieved and continuation status is determined
R-GCX146-cbl-00892
More Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment?' is invoked, and assuming that equipment records are being processed sequentially, when checking for additional equipment records, the desired outcome is that processing continues if more equipment exists, otherwise moves to list completion.
💻 Technical Criteria
Given
Equipment records are being processed sequentially
When
Checking for additional equipment records
Then
Processing continues if more equipment exists, otherwise moves to list completion
R-GCX146-cbl-00893
Format Equipment Car ID
Validation Rules
📊 Business Logic Narrative
When the process 'Format Equipment Car ID' is invoked, and assuming that raw equipment car id data is available, when formatting car identifiers for manifest display, the desired outcome is that spaces are removed and standard 12-character format is applied to car ids.
💻 Technical Criteria
Given
Raw equipment car ID data is available
When
Formatting car identifiers for manifest display
Then
Spaces are removed and standard 12-character format is applied to car IDs
R-GCX146-cbl-00894
Assign Equipment Type Code
Definitional Rules
📊 Business Logic Narrative
When the process 'Assign Equipment Type Code' is invoked, and assuming that equipment record with type indicators is available, when assigning equipment type codes for manifest, the desired outcome is that appropriate type code is assigned based on equipment classification (container/trailer/car) with corresponding type messages.
💻 Technical Criteria
Given
Equipment record with type indicators is available
When
Assigning equipment type codes for manifest
Then
Appropriate type code is assigned based on equipment classification (container/trailer/car) with corresponding type messages
R-GCX146-cbl-00896
Build Equipment Line Entry
Process Rules
📊 Business Logic Narrative
When the process 'Build Equipment Line Entry' is invoked, and assuming that formatted equipment id, type code, and status information, when building equipment line for manifest display, the desired outcome is that complete equipment line entry is constructed with id, type, and status information in proper format.
💻 Technical Criteria
Given
Formatted equipment ID, type code, and status information
When
Building equipment line for manifest display
Then
Complete equipment line entry is constructed with ID, type, and status information in proper format
R-GCX146-cbl-00897
Add to Equipment List
Process Rules
📊 Business Logic Narrative
When the process 'Add to Equipment List' is invoked, and assuming that formatted equipment line entry is ready, when adding equipment to the train manifest list, the desired outcome is that equipment entry is added to the list maintaining proper sequence and format.
💻 Technical Criteria
Given
Formatted equipment line entry is ready
When
Adding equipment to the train manifest list
Then
Equipment entry is added to the list maintaining proper sequence and format
R-GCX146-cbl-00898
Container on Flat Car?
Decision Rules
📊 Business Logic Narrative
When the process 'Container on Flat Car?' is invoked, and assuming that equipment record with container indicators, when checking for container on flat car configuration, the desired outcome is that container processing is initiated if equipment is identified as container on flat car, otherwise standard processing continues.
💻 Technical Criteria
Given
Equipment record with container indicators
When
Checking for container on flat car configuration
Then
Container processing is initiated if equipment is identified as container on flat car, otherwise standard processing continues
R-GCX146-cbl-00899
Extract Container IDs
Action Rules
📊 Business Logic Narrative
When the process 'Extract Container IDs' is invoked, and assuming that flat car equipment with associated container cross-reference records, when processing container information, the desired outcome is that container ids are extracted from t/c xref records with proper sequence identification for multiple containers.
💻 Technical Criteria
Given
Flat car equipment with associated container cross-reference records
When
Processing container information
Then
Container IDs are extracted from T/C XREF records with proper sequence identification for multiple containers
R-GCX146-cbl-00900
Format Container Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Container Information' is invoked, and assuming that extracted container ids and position information, when formatting container information for display, the desired outcome is that container information is formatted with container id, position on flat car, and flat car association details.
💻 Technical Criteria
Given
Extracted container IDs and position information
When
Formatting container information for display
Then
Container information is formatted with container ID, position on flat car, and flat car association details
R-GCX146-cbl-00904
Build Comprehensive List
Process Rules
📊 Business Logic Narrative
When the process 'Build Comprehensive List' is invoked, and assuming that all individual equipment entries have been processed, when building the comprehensive equipment list, the desired outcome is that all equipment entries are compiled into a complete list maintaining proper order and associations.
💻 Technical Criteria
Given
All individual equipment entries have been processed
When
Building the comprehensive equipment list
Then
All equipment entries are compiled into a complete list maintaining proper order and associations
R-GCX146-cbl-00905
Apply Proper Formatting
Validation Rules
📊 Business Logic Narrative
When the process 'Apply Proper Formatting' is invoked, and assuming that complete equipment list with all entries, when applying final formatting standards, the desired outcome is that proper formatting is applied to ensure consistent presentation across all equipment entries.
💻 Technical Criteria
Given
Complete equipment list with all entries
When
Applying final formatting standards
Then
Proper formatting is applied to ensure consistent presentation across all equipment entries
R-GCX146-cbl-00906
Validate List Completeness
Validation Rules
📊 Business Logic Narrative
When the process 'Validate List Completeness' is invoked, and assuming that formatted equipment list ready for validation, when validating list completeness, the desired outcome is that equipment list completeness is verified ensuring all required equipment is included and properly formatted.
💻 Technical Criteria
Given
Formatted equipment list ready for validation
When
Validating list completeness
Then
Equipment list completeness is verified ensuring all required equipment is included and properly formatted
R-GCX146-cbl-00943
Remove Spaces from Car ID
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from Car ID' is invoked, and assuming that an equipment car identifier contains spaces, when the system processes the car identifier for formatting, the desired outcome is that all spaces are removed from the car identifier.
💻 Technical Criteria
Given
An equipment car identifier contains spaces
When
The system processes the car identifier for formatting
Then
All spaces are removed from the car identifier
R-GCX146-cbl-00944
Remove Spaces from Car ID
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from Car ID' is invoked, and assuming that a train number contains spaces, when the system builds the customs train identifier, the desired outcome is that all spaces in the train number are replaced with zeros.
💻 Technical Criteria
Given
A train number contains spaces
When
The system builds the customs train identifier
Then
All spaces in the train number are replaced with zeros
R-GCX146-cbl-00945
Remove Spaces from Car ID
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from Car ID' is invoked, and assuming that a day component contains spaces, when the system builds the customs train identifier, the desired outcome is that all spaces in the day component are replaced with zeros.
💻 Technical Criteria
Given
A day component contains spaces
When
The system builds the customs train identifier
Then
All spaces in the day component are replaced with zeros
R-GCX146-cbl-00946
Remove Spaces from Car ID
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from Car ID' is invoked, and assuming that a from station code contains spaces, when the system builds the customs train identifier, the desired outcome is that all spaces in the from station code are replaced with zeros.
💻 Technical Criteria
Given
A from station code contains spaces
When
The system builds the customs train identifier
Then
All spaces in the from station code are replaced with zeros
R-GCX146-cbl-00947
Remove Spaces from Car ID
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from Car ID' is invoked, and assuming that a to station code contains spaces, when the system builds the customs train identifier, the desired outcome is that all spaces in the to station code are replaced with zeros.
💻 Technical Criteria
Given
A to station code contains spaces
When
The system builds the customs train identifier
Then
All spaces in the to station code are replaced with zeros
R-GCX146-cbl-00948
Remove Spaces from Car ID
Validation Rules
📊 Business Logic Narrative
When the process 'Remove Spaces from Car ID' is invoked, and assuming that a consist number contains spaces, when the system builds the customs train identifier, the desired outcome is that all spaces in the consist number are replaced with zeros.
💻 Technical Criteria
Given
A consist number contains spaces
When
The system builds the customs train identifier
Then
All spaces in the consist number are replaced with zeros
R-GCX146-cbl-00949
Apply Standard Formatting Rules
Action Rules
📊 Business Logic Narrative
When the process 'Apply Standard Formatting Rules' is invoked, and assuming that equipment is identified as a container, when the system processes the container for formatting, the desired outcome is that the container identifier is formatted to 12-character standard format using gcccarfm utility.
💻 Technical Criteria
Given
Equipment is identified as a container
When
The system processes the container for formatting
Then
The container identifier is formatted to 12-character standard format using GCCCARFM utility
R-GCX146-cbl-00950
Validate Car ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Car ID Format' is invoked, and assuming that an equipment identifier is provided for processing, when the system validates the identifier format, the desired outcome is that the identifier must meet the required format standards to proceed with processing.
💻 Technical Criteria
Given
An equipment identifier is provided for processing
When
The system validates the identifier format
Then
The identifier must meet the required format standards to proceed with processing
R-GCX146-cbl-00952
Initialize Sequential Car Processing
Process Rules
📊 Business Logic Narrative
When the process 'Initialize Sequential Car Processing' is invoked, and assuming that a bunch bill has been identified with multiple cars, when sequential processing needs to be established, the desired outcome is that the system initializes the car processing sequence to handle each car record systematically.
💻 Technical Criteria
Given
A bunch bill has been identified with multiple cars
When
Sequential processing needs to be established
Then
The system initializes the car processing sequence to handle each car record systematically
R-GCX146-cbl-00953
Call Z980-PROCESS-BUNCHBILL
Action Rules
📊 Business Logic Narrative
When the process 'Call Z980-PROCESS-BUNCHBILL' is invoked, and assuming that a bunch bill requires processing, when sequential car processing has been initialized, the desired outcome is that the system calls the z980-process-bunchbill module to execute bunch bill processing logic.
💻 Technical Criteria
Given
A bunch bill requires processing
When
Sequential car processing has been initialized
Then
The system calls the Z980-PROCESS-BUNCHBILL module to execute bunch bill processing logic
R-GCX146-cbl-00955
Use FWCMSGET to Retrieve Next Car Record
Action Rules
📊 Business Logic Narrative
When the process 'Use FWCMSGET to Retrieve Next Car Record' is invoked, and assuming that a bunch bill processing routine is active, when the next car record needs to be retrieved for processing, the desired outcome is that the system uses fwcmsget to retrieve the next sequential car equipment record.
💻 Technical Criteria
Given
A bunch bill processing routine is active
When
The next car record needs to be retrieved for processing
Then
The system uses FWCMSGET to retrieve the next sequential car equipment record
R-GCX146-cbl-00957
Process Current Car Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Process Current Car Equipment Record' is invoked, and assuming that a car equipment record has been retrieved from the bunch bill, when the car record requires processing, the desired outcome is that the system processes the current car equipment record applying all standard equipment processing rules.
💻 Technical Criteria
Given
A car equipment record has been retrieved from the bunch bill
When
The car record requires processing
Then
The system processes the current car equipment record applying all standard equipment processing rules
R-GCX146-cbl-00960
Return to Main Equipment Processing
Process Rules
📊 Business Logic Narrative
When the process 'Return to Main Equipment Processing' is invoked, and assuming that bunch bill processing has been completed, when all cars under the bunch bill have been processed, the desired outcome is that the system returns control to the main equipment processing flow to continue with overall train processing.
💻 Technical Criteria
Given
Bunch bill processing has been completed
When
All cars under the bunch bill have been processed
Then
The system returns control to the main equipment processing flow to continue with overall train processing
R-GCX146-cbl-00966
Validate Car ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Car ID Format' is invoked, and assuming that car identification data has been extracted from an equipment record, when the system validates the car id format, the desired outcome is that the car id format is checked against required standards and marked as valid or invalid.
💻 Technical Criteria
Given
Car identification data has been extracted from an equipment record
When
The system validates the car ID format
Then
The car ID format is checked against required standards and marked as valid or invalid
R-GCX146-cbl-00967
Car ID Valid?
Decision Rules
📊 Business Logic Narrative
When the process 'Car ID Valid?' is invoked, and assuming that a car id has been validated against format requirements, when the system evaluates car id validity, the desired outcome is that the system determines if the car id is valid for processing or requires error handling.
💻 Technical Criteria
Given
A car ID has been validated against format requirements
When
The system evaluates car ID validity
Then
The system determines if the car ID is valid for processing or requires error handling
R-GCX146-cbl-00968
Process Car in Sequence
Process Rules
📊 Business Logic Narrative
When the process 'Process Car in Sequence' is invoked, and assuming that a car id has been validated as meeting format requirements, when the car id is determined to be valid, the desired outcome is that the car is processed as part of the bunch bill sequence.
💻 Technical Criteria
Given
A car ID has been validated as meeting format requirements
When
The car ID is determined to be valid
Then
The car is processed as part of the bunch bill sequence
R-GCX146-cbl-00969
Increment Car Sequence Counter
Computation Rules
📊 Business Logic Narrative
When the process 'Increment Car Sequence Counter' is invoked, and assuming that a car has been successfully processed in the bunch bill sequence, when the car processing is completed, the desired outcome is that the car sequence counter is incremented to track the number of processed cars.
💻 Technical Criteria
Given
A car has been successfully processed in the bunch bill sequence
When
The car processing is completed
Then
The car sequence counter is incremented to track the number of processed cars
R-GCX146-cbl-00970
More Cars in Bunch Bill?
Decision Rules
📊 Business Logic Narrative
When the process 'More Cars in Bunch Bill?' is invoked, and assuming that a car has been processed and the sequence counter has been incremented, when the system checks for remaining cars in the bunch bill, the desired outcome is that the system determines whether more cars exist for processing or if the bunch bill is complete.
💻 Technical Criteria
Given
A car has been processed and the sequence counter has been incremented
When
The system checks for remaining cars in the bunch bill
Then
The system determines whether more cars exist for processing or if the bunch bill is complete
R-GCX146-cbl-00971
Log Invalid Car ID Error
Process Rules
📊 Business Logic Narrative
When the process 'Log Invalid Car ID Error' is invoked, and assuming that a car id has been extracted from an equipment record, when the car id fails format validation, the desired outcome is that an invalid car id error is logged for tracking and audit purposes.
💻 Technical Criteria
Given
A car ID has been extracted from an equipment record
When
The car ID fails format validation
Then
An invalid car ID error is logged for tracking and audit purposes
R-GCX146-cbl-00972
Skip Invalid Car Record
Process Rules
📊 Business Logic Narrative
When the process 'Skip Invalid Car Record' is invoked, and assuming that a car id has been determined to be invalid and an error has been logged, when the system continues bunch bill processing, the desired outcome is that the invalid car record is skipped and processing continues with the next car in the sequence.
💻 Technical Criteria
Given
A car ID has been determined to be invalid and an error has been logged
When
The system continues bunch bill processing
Then
The invalid car record is skipped and processing continues with the next car in the sequence
R-GCX146-cbl-00973
Complete Additional Car Processing
Process Rules
📊 Business Logic Narrative
When the process 'Complete Additional Car Processing' is invoked, and assuming that all cars in the bunch bill have been processed or no more equipment records are available, when the bunch bill processing reaches completion, the desired outcome is that the additional car processing is completed and the system is ready for the next processing step.
💻 Technical Criteria
Given
All cars in the bunch bill have been processed or no more equipment records are available
When
The bunch bill processing reaches completion
Then
The additional car processing is completed and the system is ready for the next processing step
R-GCX146-cbl-00974
Initialize US Trip Sheet Equipment Records
Process Rules
📊 Business Logic Narrative
When the process 'Initialize US Trip Sheet Equipment Records' is invoked, and assuming that a us trip sheet generation process is starting, when the system begins processing equipment records, the desired outcome is that equipment counters are reset to zero and processing flags are initialized.
💻 Technical Criteria
Given
A US trip sheet generation process is starting
When
The system begins processing equipment records
Then
Equipment counters are reset to zero and processing flags are initialized
R-GCX146-cbl-00975
Extract Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Extract Equipment Information' is invoked, and assuming that a train consist record exists with equipment information, when the system processes each equipment entry, the desired outcome is that equipment id, type, status, and associated data are extracted for further processing.
💻 Technical Criteria
Given
A train consist record exists with equipment information
When
The system processes each equipment entry
Then
Equipment ID, type, status, and associated data are extracted for further processing
R-GCX146-cbl-00976
Determine Equipment Type
Decision Rules
📊 Business Logic Narrative
When the process 'Determine Equipment Type' is invoked, and assuming that equipment information has been extracted from train records, when the system analyzes equipment characteristics, the desired outcome is that equipment is classified as idler, unit, van, etu, or other type based on its properties.
💻 Technical Criteria
Given
Equipment information has been extracted from train records
When
The system analyzes equipment characteristics
Then
Equipment is classified as IDLER, UNIT, VAN, ETU, or Other type based on its properties
R-GCX146-cbl-00977
Process IDLER Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process IDLER Equipment' is invoked, and assuming that equipment is classified as idler type, when the system processes the idler equipment, the desired outcome is that idler equipment data is formatted according to us customs requirements with appropriate status indicators.
💻 Technical Criteria
Given
Equipment is classified as IDLER type
When
The system processes the IDLER equipment
Then
IDLER equipment data is formatted according to US customs requirements with appropriate status indicators
R-GCX146-cbl-00978
Process UNIT Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process UNIT Equipment' is invoked, and assuming that equipment is classified as unit type (locomotives, power units), when the system processes the unit equipment, the desired outcome is that unit equipment data is formatted with proper identification and status information for us customs reporting.
💻 Technical Criteria
Given
Equipment is classified as UNIT type (locomotives, power units)
When
The system processes the UNIT equipment
Then
UNIT equipment data is formatted with proper identification and status information for US customs reporting
R-GCX146-cbl-00979
Process VAN Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process VAN Equipment' is invoked, and assuming that equipment is classified as van type, when the system processes the van equipment, the desired outcome is that van equipment data is formatted with cargo information and customs status for trip sheet reporting.
💻 Technical Criteria
Given
Equipment is classified as VAN type
When
The system processes the VAN equipment
Then
VAN equipment data is formatted with cargo information and customs status for trip sheet reporting
R-GCX146-cbl-00980
Process ETU Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process ETU Equipment' is invoked, and assuming that equipment is classified as etu type, when the system processes the etu equipment, the desired outcome is that etu equipment data is formatted with appropriate technical specifications and status for customs reporting.
💻 Technical Criteria
Given
Equipment is classified as ETU type
When
The system processes the ETU equipment
Then
ETU equipment data is formatted with appropriate technical specifications and status for customs reporting
R-GCX146-cbl-00981
Process Other Equipment Types
Process Rules
📊 Business Logic Narrative
When the process 'Process Other Equipment Types' is invoked, and assuming that equipment is classified as other type (not idler, unit, van, or etu), when the system processes the other equipment type, the desired outcome is that equipment data is formatted using standard default rules for us customs trip sheet reporting.
💻 Technical Criteria
Given
Equipment is classified as Other type (not IDLER, UNIT, VAN, or ETU)
When
The system processes the other equipment type
Then
Equipment data is formatted using standard default rules for US customs trip sheet reporting
R-GCX146-cbl-00982
Format Equipment Data for US Customs
Validation Rules
📊 Business Logic Narrative
When the process 'Format Equipment Data for US Customs' is invoked, and assuming that equipment has been processed according to its type classification, when the system formats the equipment data for us customs, the desired outcome is that equipment information is structured in compliance with us customs trip sheet format requirements including proper field positioning and data validation.
💻 Technical Criteria
Given
Equipment has been processed according to its type classification
When
The system formats the equipment data for US customs
Then
Equipment information is structured in compliance with US customs trip sheet format requirements including proper field positioning and data validation
R-GCX146-cbl-00983
Build Merlin Transmission Lines
Process Rules
📊 Business Logic Narrative
When the process 'Build Merlin Transmission Lines' is invoked, and assuming that equipment data has been formatted for us customs requirements, when the system builds merlin transmission lines, the desired outcome is that message lines are constructed with proper formatting, sequencing, and transmission headers for merlin system delivery.
💻 Technical Criteria
Given
Equipment data has been formatted for US customs requirements
When
The system builds Merlin transmission lines
Then
Message lines are constructed with proper formatting, sequencing, and transmission headers for Merlin system delivery
R-GCX146-cbl-00984
Prepare Equipment Type Messages
Process Rules
📊 Business Logic Narrative
When the process 'Prepare Equipment Type Messages' is invoked, and assuming that merlin transmission lines have been built for equipment, when the system prepares equipment type messages, the desired outcome is that messages are customized with equipment-specific information, status codes, and regulatory data appropriate for each equipment type.
💻 Technical Criteria
Given
Merlin transmission lines have been built for equipment
When
The system prepares equipment type messages
Then
Messages are customized with equipment-specific information, status codes, and regulatory data appropriate for each equipment type
R-GCX146-cbl-00985
Format Equipment Car IDs
Validation Rules
📊 Business Logic Narrative
When the process 'Format Equipment Car IDs' is invoked, and assuming that equipment type messages have been prepared, when the system formats equipment car ids, the desired outcome is that car identification numbers are standardized with proper length, character formatting, and validation according to railroad and customs standards.
💻 Technical Criteria
Given
Equipment type messages have been prepared
When
The system formats equipment car IDs
Then
Car identification numbers are standardized with proper length, character formatting, and validation according to railroad and customs standards
R-GCX146-cbl-00986
Compile Equipment Status Information
Process Rules
📊 Business Logic Narrative
When the process 'Compile Equipment Status Information' is invoked, and assuming that equipment car ids have been formatted, when the system compiles equipment status information, the desired outcome is that complete status records are created including customs status, transit information, cargo details, and regulatory compliance data.
💻 Technical Criteria
Given
Equipment car IDs have been formatted
When
The system compiles equipment status information
Then
Complete status records are created including customs status, transit information, cargo details, and regulatory compliance data
R-GCX146-cbl-00988
More Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment?' is invoked, and assuming that current equipment record has been processed and segmented for transmission, when the system checks for additional equipment in the train consist, the desired outcome is that if more equipment exists, processing continues with the next equipment record; otherwise, processing moves to finalization.
💻 Technical Criteria
Given
Current equipment record has been processed and segmented for transmission
When
The system checks for additional equipment in the train consist
Then
If more equipment exists, processing continues with the next equipment record; otherwise, processing moves to finalization
R-GCX146-cbl-00989
Finalize US Trip Sheet Data
Process Rules
📊 Business Logic Narrative
When the process 'Finalize US Trip Sheet Data' is invoked, and assuming that all equipment records have been processed and no more equipment remains, when the system finalizes the us trip sheet data, the desired outcome is that trip sheet is completed with summary totals, final formatting, and all required regulatory information for us customs submission.
💻 Technical Criteria
Given
All equipment records have been processed and no more equipment remains
When
The system finalizes the US trip sheet data
Then
Trip sheet is completed with summary totals, final formatting, and all required regulatory information for US customs submission
R-GCX146-cbl-00990
Ready for Merlin Transmission
Action Rules
📊 Business Logic Narrative
When the process 'Ready for Merlin Transmission' is invoked, and assuming that us trip sheet data has been finalized with all equipment and summary information, when the system prepares for merlin transmission, the desired outcome is that trip sheet is formatted for merlin system delivery with proper transmission headers, routing information, and delivery confirmation requirements.
💻 Technical Criteria
Given
US trip sheet data has been finalized with all equipment and summary information
When
The system prepares for Merlin transmission
Then
Trip sheet is formatted for Merlin system delivery with proper transmission headers, routing information, and delivery confirmation requirements
R-GCX146-cbl-01001
Process Equipment Type Messages
Process Rules
📊 Business Logic Narrative
When the process 'Process Equipment Type Messages' is invoked, and assuming that equipment data is available for processing, when the system processes equipment type messages, the desired outcome is that each equipment type (idler, unit, van, etu) is processed according to its specific requirements.
💻 Technical Criteria
Given
Equipment data is available for processing
When
The system processes equipment type messages
Then
Each equipment type (IDLER, UNIT, VAN, ETU) is processed according to its specific requirements
R-GCX146-cbl-01002
Process IDLER Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process IDLER Equipment' is invoked, and assuming that idler equipment data is available, when the system processes idler equipment, the desired outcome is that idler equipment information is formatted and included in the report.
💻 Technical Criteria
Given
IDLER equipment data is available
When
The system processes IDLER equipment
Then
IDLER equipment information is formatted and included in the report
R-GCX146-cbl-01003
Process UNIT Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process UNIT Equipment' is invoked, and assuming that unit equipment data is available, when the system processes unit equipment, the desired outcome is that unit equipment information is formatted and included in the report.
💻 Technical Criteria
Given
UNIT equipment data is available
When
The system processes UNIT equipment
Then
UNIT equipment information is formatted and included in the report
R-GCX146-cbl-01004
Process VAN Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process VAN Equipment' is invoked, and assuming that van equipment data is available, when the system processes van equipment, the desired outcome is that van equipment information is formatted and included in the report.
💻 Technical Criteria
Given
VAN equipment data is available
When
The system processes VAN equipment
Then
VAN equipment information is formatted and included in the report
R-GCX146-cbl-01005
Process ETU Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process ETU Equipment' is invoked, and assuming that etu equipment data is available, when the system processes etu equipment, the desired outcome is that etu equipment information is formatted and included in the report.
💻 Technical Criteria
Given
ETU equipment data is available
When
The system processes ETU equipment
Then
ETU equipment information is formatted and included in the report
R-GCX146-cbl-01006
More Lines to Process?
Decision Rules
📊 Business Logic Narrative
When the process 'More Lines to Process?' is invoked, and assuming that equipment type processing has been completed for current line, when the system checks for more lines to process, the desired outcome is that if more lines exist, continue processing; if no more lines, finalize the current message.
💻 Technical Criteria
Given
Equipment type processing has been completed for current line
When
The system checks for more lines to process
Then
If more lines exist, continue processing; if no more lines, finalize the current message
R-GCX146-cbl-01009
Equipment Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Type?' is invoked, and assuming that an equipment record with a specific car type code, when the system evaluates the equipment type for message assignment, the desired outcome is that the system classifies the equipment as idler, unit, van, etu, container, trailer, or standard car based on the car type code patterns.
💻 Technical Criteria
Given
An equipment record with a specific car type code
When
The system evaluates the equipment type for message assignment
Then
The system classifies the equipment as IDLER, UNIT, VAN, ETU, Container, Trailer, or standard Car based on the car type code patterns
R-GCX146-cbl-01010
Assign IDLER Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign IDLER Message' is invoked, and assuming that equipment has been classified as idler type, when the system processes the equipment for message assignment, the desired outcome is that the system assigns the appropriate idler equipment message format.
💻 Technical Criteria
Given
Equipment has been classified as IDLER type
When
The system processes the equipment for message assignment
Then
The system assigns the appropriate IDLER equipment message format
R-GCX146-cbl-01011
Assign UNIT Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign UNIT Message' is invoked, and assuming that equipment has been classified as unit type with car type codes l, p, d, or u, when the system processes the equipment for message assignment, the desired outcome is that the system assigns the appropriate unit equipment message format.
💻 Technical Criteria
Given
Equipment has been classified as UNIT type with car type codes L, P, D, or U
When
The system processes the equipment for message assignment
Then
The system assigns the appropriate UNIT equipment message format
R-GCX146-cbl-01012
Assign VAN Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign VAN Message' is invoked, and assuming that equipment has been classified as van type with car type code v, when the system processes the equipment for message assignment, the desired outcome is that the system assigns the appropriate van equipment message format.
💻 Technical Criteria
Given
Equipment has been classified as VAN type with car type code V
When
The system processes the equipment for message assignment
Then
The system assigns the appropriate VAN equipment message format
R-GCX146-cbl-01013
Assign ETU Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign ETU Message' is invoked, and assuming that equipment has been classified as etu type with car type code e, when the system processes the equipment for message assignment, the desired outcome is that the system assigns the appropriate etu equipment message format.
💻 Technical Criteria
Given
Equipment has been classified as ETU type with car type code E
When
The system processes the equipment for message assignment
Then
The system assigns the appropriate ETU equipment message format
R-GCX146-cbl-01014
Assign Container Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Container Message' is invoked, and assuming that equipment has been identified as a container type, when the system processes the equipment for message assignment, the desired outcome is that the system assigns the appropriate container equipment message format.
💻 Technical Criteria
Given
Equipment has been identified as a container type
When
The system processes the equipment for message assignment
Then
The system assigns the appropriate container equipment message format
R-GCX146-cbl-01015
Assign Trailer Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Trailer Message' is invoked, and assuming that equipment has been identified as a trailer type, when the system processes the equipment for message assignment, the desired outcome is that the system assigns the appropriate trailer equipment message format.
💻 Technical Criteria
Given
Equipment has been identified as a trailer type
When
The system processes the equipment for message assignment
Then
The system assigns the appropriate trailer equipment message format
R-GCX146-cbl-01016
Assign Car Message
Action Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Assign Car Message', assuming that equipment does not match idler, unit, van, etu, container, or trailer classifications, when the system processes the equipment for message assignment, the desired outcome is that the system assigns the standard car equipment message format.
💻 Technical Criteria
EXCLUDING
Equipment does not match IDLER, UNIT, VAN, ETU, Container, or Trailer classifications
When
The system processes the equipment for message assignment
Then
The system assigns the standard car equipment message format
R-GCX146-cbl-01017
Equipment Status?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Status?' is invoked, and assuming that equipment has been assigned a type classification, when the system evaluates the equipment status for message assignment, the desired outcome is that the system determines if the equipment is load, empty, transit, release, or held status.
💻 Technical Criteria
Given
Equipment has been assigned a type classification
When
The system evaluates the equipment status for message assignment
Then
The system determines if the equipment is Load, Empty, Transit, Release, or Held status
R-GCX146-cbl-01018
Assign Load Status Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Load Status Message' is invoked, and assuming that equipment status indicates loaded condition, when the system processes the equipment status for message assignment, the desired outcome is that the system assigns the appropriate load status message.
💻 Technical Criteria
Given
Equipment status indicates loaded condition
When
The system processes the equipment status for message assignment
Then
The system assigns the appropriate load status message
R-GCX146-cbl-01019
Assign Empty Status Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Empty Status Message' is invoked, and assuming that equipment status indicates empty condition, when the system processes the equipment status for message assignment, the desired outcome is that the system assigns the appropriate empty status message.
💻 Technical Criteria
Given
Equipment status indicates empty condition
When
The system processes the equipment status for message assignment
Then
The system assigns the appropriate empty status message
R-GCX146-cbl-01020
Assign Transit Status Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Transit Status Message' is invoked, and assuming that equipment status indicates transit condition, when the system processes the equipment status for message assignment, the desired outcome is that the system assigns the appropriate transit status message.
💻 Technical Criteria
Given
Equipment status indicates transit condition
When
The system processes the equipment status for message assignment
Then
The system assigns the appropriate transit status message
R-GCX146-cbl-01021
Assign Release Status Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Release Status Message' is invoked, and assuming that equipment status indicates released condition, when the system processes the equipment status for message assignment, the desired outcome is that the system assigns the appropriate release status message.
💻 Technical Criteria
Given
Equipment status indicates released condition
When
The system processes the equipment status for message assignment
Then
The system assigns the appropriate release status message
R-GCX146-cbl-01022
Assign Held Status Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Held Status Message' is invoked, and assuming that equipment status indicates held condition, when the system processes the equipment status for message assignment, the desired outcome is that the system assigns the appropriate held status message.
💻 Technical Criteria
Given
Equipment status indicates held condition
When
The system processes the equipment status for message assignment
Then
The system assigns the appropriate held status message
R-GCX146-cbl-01024
Assign Bunch Bill Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Bunch Bill Message' is invoked, and assuming that equipment requires bunch bill special processing, when the system processes the equipment for bunch bill message assignment, the desired outcome is that the system assigns the appropriate bunch bill message format.
💻 Technical Criteria
Given
Equipment requires bunch bill special processing
When
The system processes the equipment for bunch bill message assignment
Then
The system assigns the appropriate bunch bill message format
R-GCX146-cbl-01025
Assign Flat Car Container Message
Action Rules
📊 Business Logic Narrative
When the process 'Assign Flat Car Container Message' is invoked, and assuming that equipment requires flat car container special processing, when the system processes the equipment for flat car container message assignment, the desired outcome is that the system assigns the appropriate flat car container message format.
💻 Technical Criteria
Given
Equipment requires flat car container special processing
When
The system processes the equipment for flat car container message assignment
Then
The system assigns the appropriate flat car container message format
R-GCX146-cbl-01027
Format Equipment Information
Process Rules
📊 Business Logic Narrative
When the process 'Format Equipment Information' is invoked, and assuming that equipment has been assigned appropriate type, status, and special processing messages, when the system formats the equipment information, the desired outcome is that the system creates properly formatted equipment information message ready for storage.
💻 Technical Criteria
Given
Equipment has been assigned appropriate type, status, and special processing messages
When
The system formats the equipment information
Then
The system creates properly formatted equipment information message ready for storage
R-GCX146-cbl-01028
Store Message Assignment
Process Rules
📊 Business Logic Narrative
When the process 'Store Message Assignment' is invoked, and assuming that equipment information has been properly formatted, when the system stores the message assignment, the desired outcome is that the system saves the equipment message assignment data for subsequent processing steps.
💻 Technical Criteria
Given
Equipment information has been properly formatted
When
The system stores the message assignment
Then
The system saves the equipment message assignment data for subsequent processing steps
R-GCX146-cbl-01032
Set Sequential Car Counter
Process Rules
📊 Business Logic Narrative
When the process 'Set Sequential Car Counter' is invoked, and assuming that a bunch bill with multiple cars has been identified, when sequential processing begins, the desired outcome is that the car counter is initialized to track each car in the sequence.
💻 Technical Criteria
Given
A bunch bill with multiple cars has been identified
When
Sequential processing begins
Then
The car counter is initialized to track each car in the sequence
R-GCX146-cbl-01033
Process Current Car Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Process Current Car Equipment' is invoked, and assuming that a car position in the bunch bill sequence is identified, when the system processes the current car, the desired outcome is that equipment details for the current car are extracted and prepared for validation.
💻 Technical Criteria
Given
A car position in the bunch bill sequence is identified
When
The system processes the current car
Then
Equipment details for the current car are extracted and prepared for validation
R-GCX146-cbl-01035
Extract Car Details
Process Rules
📊 Business Logic Narrative
When the process 'Extract Car Details' is invoked, and assuming that an equipment id has been validated successfully, when the system extracts car details, the desired outcome is that complete car information including type, status, and specifications are extracted from the equipment records.
💻 Technical Criteria
Given
An equipment ID has been validated successfully
When
The system extracts car details
Then
Complete car information including type, status, and specifications are extracted from the equipment records
R-GCX146-cbl-01036
Store Car Information
Process Rules
📊 Business Logic Narrative
When the process 'Store Car Information' is invoked, and assuming that car details have been successfully extracted, when the system stores the car information, the desired outcome is that car information is stored in the processing queue for subsequent operations.
💻 Technical Criteria
Given
Car details have been successfully extracted
When
The system stores the car information
Then
Car information is stored in the processing queue for subsequent operations
R-GCX146-cbl-01037
Increment Car Counter
Process Rules
📊 Business Logic Narrative
When the process 'Increment Car Counter' is invoked, and assuming that a car has been successfully processed, when the system completes processing of the current car, the desired outcome is that the car counter is incremented to move to the next car in the sequence.
💻 Technical Criteria
Given
A car has been successfully processed
When
The system completes processing of the current car
Then
The car counter is incremented to move to the next car in the sequence
R-GCX146-cbl-01038
Retrieve Next Car in Sequence
Action Rules
📊 Business Logic Narrative
When the process 'Retrieve Next Car in Sequence' is invoked, and assuming that the car counter has been incremented, when the system retrieves the next car in sequence, the desired outcome is that the next car record is retrieved from fwiiroot database using the sequential position.
💻 Technical Criteria
Given
The car counter has been incremented
When
The system retrieves the next car in sequence
Then
The next car record is retrieved from FWIIROOT database using the sequential position
R-GCX146-cbl-01039
More Cars in Bunch Bill?
Decision Rules
📊 Business Logic Narrative
When the process 'More Cars in Bunch Bill?' is invoked, and assuming that a car has been processed and counter incremented, when the system checks for more cars, the desired outcome is that if additional cars exist in the bunch bill, processing continues with the next car, otherwise processing finalizes.
💻 Technical Criteria
Given
A car has been processed and counter incremented
When
The system checks for more cars
Then
If additional cars exist in the bunch bill, processing continues with the next car, otherwise processing finalizes
R-GCX146-cbl-01041
Update Equipment Totals
Computation Rules
📊 Business Logic Narrative
When the process 'Update Equipment Totals' is invoked, and assuming that bunch bill processing has been finalized, when the system updates equipment totals, the desired outcome is that total equipment counts, status summaries, and processing statistics are updated with bunch bill results.
💻 Technical Criteria
Given
Bunch bill processing has been finalized
When
The system updates equipment totals
Then
Total equipment counts, status summaries, and processing statistics are updated with bunch bill results
R-GCX146-cbl-01042
Handle Equipment Error
Process Rules
📊 Business Logic Narrative
When the process 'Handle Equipment Error' is invoked, and assuming that an equipment id fails validation, when the system handles the equipment error, the desired outcome is that error handling procedures are initiated and the invalid equipment is flagged for review.
💻 Technical Criteria
Given
An equipment ID fails validation
When
The system handles the equipment error
Then
Error handling procedures are initiated and the invalid equipment is flagged for review
R-GCX146-cbl-01043
Log Invalid Equipment
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Log Invalid Equipment', assuming that invalid equipment has been identified, when the system logs the invalid equipment, the desired outcome is that equipment details and error information are logged for subsequent review and correction.
💻 Technical Criteria
EXCLUDING
Invalid equipment has been identified
When
The system logs the invalid equipment
Then
Equipment details and error information are logged for subsequent review and correction
R-GCX146-cbl-01044
Initialize US Trip Sheet Equipment Records
Process Rules
📊 Business Logic Narrative
When the process 'Initialize US Trip Sheet Equipment Records' is invoked, and assuming that a us trip sheet transmission is being prepared, when the system begins processing equipment records, the desired outcome is that equipment counters are reset to zero and processing flags are initialized.
💻 Technical Criteria
Given
A US trip sheet transmission is being prepared
When
The system begins processing equipment records
Then
Equipment counters are reset to zero and processing flags are initialized
R-GCX146-cbl-01045
Build Equipment List for US Customs
Process Rules
📊 Business Logic Narrative
When the process 'Build Equipment List for US Customs' is invoked, and assuming that equipment records exist for the train, when the system processes each equipment record for us customs reporting, the desired outcome is that valid equipment records are added to the trip sheet processing list.
💻 Technical Criteria
Given
Equipment records exist for the train
When
The system processes each equipment record for US customs reporting
Then
Valid equipment records are added to the trip sheet processing list
R-GCX146-cbl-01047
Equipment Type?
Decision Rules
📊 Business Logic Narrative
When the process 'Equipment Type?' is invoked, and assuming that an equipment record with car type information, when the system evaluates the equipment type, the desired outcome is that equipment is classified as idler, unit, van, etu, or other based on car type codes.
💻 Technical Criteria
Given
An equipment record with car type information
When
The system evaluates the equipment type
Then
Equipment is classified as IDLER, UNIT, VAN, ETU, or Other based on car type codes
R-GCX146-cbl-01048
Format IDLER Equipment Message
Process Rules
📊 Business Logic Narrative
When the process 'Format IDLER Equipment Message' is invoked, and assuming that an equipment record classified as idler type, when the system formats the equipment message, the desired outcome is that idler equipment is formatted with car identification and basic details without cargo information.
💻 Technical Criteria
Given
An equipment record classified as IDLER type
When
The system formats the equipment message
Then
IDLER equipment is formatted with car identification and basic details without cargo information
R-GCX146-cbl-01050
Format VAN Equipment Message
Process Rules
📊 Business Logic Narrative
When the process 'Format VAN Equipment Message' is invoked, and assuming that an equipment record classified as van type, when the system formats the equipment message, the desired outcome is that van equipment is formatted with van identification and cargo details appropriate for van shipments.
💻 Technical Criteria
Given
An equipment record classified as VAN type
When
The system formats the equipment message
Then
VAN equipment is formatted with van identification and cargo details appropriate for van shipments
R-GCX146-cbl-01051
Format ETU Equipment Message
Process Rules
📊 Business Logic Narrative
When the process 'Format ETU Equipment Message' is invoked, and assuming that an equipment record classified as etu type, when the system formats the equipment message, the desired outcome is that etu equipment is formatted with tank unit identification and empty status indication.
💻 Technical Criteria
Given
An equipment record classified as ETU type
When
The system formats the equipment message
Then
ETU equipment is formatted with tank unit identification and empty status indication
R-GCX146-cbl-01052
Format Other Equipment Message
Process Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Format Other Equipment Message', assuming that an equipment record that does not match idler, unit, van, or etu classifications, when the system formats the equipment message, the desired outcome is that equipment is formatted using standard formatting rules with available car and cargo information.
💻 Technical Criteria
EXCLUDING
An equipment record that does not match IDLER, UNIT, VAN, or ETU classifications
When
The system formats the equipment message
Then
Equipment is formatted using standard formatting rules with available car and cargo information
R-GCX146-cbl-01053
Add Equipment to Merlin Message Buffer
Process Rules
📊 Business Logic Narrative
When the process 'Add Equipment to Merlin Message Buffer' is invoked, and assuming that a formatted equipment message, when the system adds the equipment to the message buffer, the desired outcome is that equipment information is appended to the current message buffer and line counters are updated.
💻 Technical Criteria
Given
A formatted equipment message
When
The system adds the equipment to the message buffer
Then
Equipment information is appended to the current message buffer and line counters are updated
R-GCX146-cbl-01054
More Equipment?
Decision Rules
📊 Business Logic Narrative
When the process 'More Equipment?' is invoked, and assuming that equipment processing is in progress, when the system checks for remaining equipment records, the desired outcome is that processing continues if more equipment exists, otherwise proceeds to message finalization.
💻 Technical Criteria
Given
Equipment processing is in progress
When
The system checks for remaining equipment records
Then
Processing continues if more equipment exists, otherwise proceeds to message finalization
R-GCX146-cbl-01055
Check Message Size Limits
Validation Rules
📊 Business Logic Narrative
When the process 'Check Message Size Limits' is invoked, and assuming that equipment has been added to the message buffer, when the system checks the current message size, the desired outcome is that message line count and size are validated against maximum transmission limits.
💻 Technical Criteria
Given
Equipment has been added to the message buffer
When
The system checks the current message size
Then
Message line count and size are validated against maximum transmission limits
R-GCX146-cbl-01056
Message Size Exceeded?
Decision Rules
📊 Business Logic Narrative
When the process 'Message Size Exceeded?' is invoked, and assuming that a message buffer with accumulated equipment data, when the system evaluates the message size against limits, the desired outcome is that message segmentation is triggered if size exceeds limits, otherwise processing continues normally.
💻 Technical Criteria
Given
A message buffer with accumulated equipment data
When
The system evaluates the message size against limits
Then
Message segmentation is triggered if size exceeds limits, otherwise processing continues normally
R-GCX146-cbl-01059
Initialize New Message Segment
Process Rules
📊 Business Logic Narrative
When the process 'Initialize New Message Segment' is invoked, and assuming that a message segment has been transmitted, when the system initializes a new message segment, the desired outcome is that message buffer is reset and prepared for additional equipment data with appropriate headers.
💻 Technical Criteria
Given
A message segment has been transmitted
When
The system initializes a new message segment
Then
Message buffer is reset and prepared for additional equipment data with appropriate headers
R-GCX146-cbl-01060
Continue with Remaining Equipment
Process Rules
📊 Business Logic Narrative
When the process 'Continue with Remaining Equipment' is invoked, and assuming that a new message segment has been initialized, when the system continues equipment processing, the desired outcome is that remaining equipment records are processed and added to the new message segment.
💻 Technical Criteria
Given
A new message segment has been initialized
When
The system continues equipment processing
Then
Remaining equipment records are processed and added to the new message segment
R-GCX146-cbl-01061
Finalize Complete Message
Process Rules
📊 Business Logic Narrative
When the process 'Finalize Complete Message' is invoked, and assuming that all equipment has been processed and message size is within limits, when the system finalizes the message, the desired outcome is that message is prepared for final transmission with appropriate headers and footers.
💻 Technical Criteria
Given
All equipment has been processed and message size is within limits
When
The system finalizes the message
Then
Message is prepared for final transmission with appropriate headers and footers
R-GCX146-cbl-01065
Current Station = Final Destination?
Validation Rules
📊 Business Logic Narrative
When the process 'Current Station = Final Destination?' is invoked, and assuming that cargo has transit status 'd' and manifest contains destination station information, when the system compares current station location with final destination station from manifest, the desired outcome is that if current station matches final destination station, cargo is confirmed as arrived at correct location, otherwise skip arrival processing.
💻 Technical Criteria
Given
Cargo has transit status 'D' and manifest contains destination station information
When
The system compares current station location with final destination station from manifest
Then
If current station matches final destination station, cargo is confirmed as arrived at correct location, otherwise skip arrival processing
R-GCX146-cbl-01067
Trigger Arrival Notification Process
Action Rules
📊 Business Logic Narrative
When the process 'Trigger Arrival Notification Process' is invoked, and assuming that cargo status has been updated to arrived, when the system completes the arrival status update, the desired outcome is that arrival notification process is triggered to send notifications to brokers, customs, and other stakeholders.
💻 Technical Criteria
Given
Cargo status has been updated to arrived
When
The system completes the arrival status update
Then
Arrival notification process is triggered to send notifications to brokers, customs, and other stakeholders
R-GCX146-cbl-01068
Log Arrival Detection
Process Rules
📊 Business Logic Narrative
When the process 'Log Arrival Detection' is invoked, and assuming that cargo arrival has been detected and processed, when the system completes arrival notification triggering, the desired outcome is that an audit log entry is created recording the arrival detection event with timestamp and relevant cargo details.
💻 Technical Criteria
Given
Cargo arrival has been detected and processed
When
The system completes arrival notification triggering
Then
An audit log entry is created recording the arrival detection event with timestamp and relevant cargo details
R-GCX146-cbl-01071
Identify Canadian Goods Returning from US
Decision Rules
📊 Business Logic Narrative
When the process 'Identify Canadian Goods Returning from US' is invoked, and assuming that a cargo shipment with origin and destination information, when the system analyzes the cargo movement pattern, the desired outcome is that the system determines if the cargo represents canadian goods returning from us territory.
💻 Technical Criteria
Given
A cargo shipment with origin and destination information
When
The system analyzes the cargo movement pattern
Then
The system determines if the cargo represents Canadian goods returning from US territory
R-GCX146-cbl-01386
Is Cargo Canadian Origin?
Decision Rules
📊 Business Logic Narrative
When the process 'Is Cargo Canadian Origin?' is invoked, and assuming that a cargo shipment with origin province/state information, when the system evaluates the origin location, the desired outcome is that the cargo is classified as canadian origin if the origin province code matches any canadian province (nf, pe, ns, nb, pq, on, mb, sk, ab, bc, yt, nt), otherwise it is classified as non-canadian origin.
💻 Technical Criteria
Given
A cargo shipment with origin province/state information
When
The system evaluates the origin location
Then
The cargo is classified as Canadian origin if the origin province code matches any Canadian province (NF, PE, NS, NB, PQ, ON, MB, SK, AB, BC, YT, NT), otherwise it is classified as non-Canadian origin
R-GCX146-cbl-01387
Has US Destination History?
Decision Rules
📊 Business Logic Narrative
When the process 'Has US Destination History?' is invoked, and assuming that a canadian origin cargo shipment with destination information, when the system checks the destination province/state codes, the desired outcome is that the cargo is identified as having us destination history if the destination province/state code is not in the canadian province list (nf, pe, ns, nb, pq, on, mb, sk, ab, bc, yt, nt).
💻 Technical Criteria
Given
A Canadian origin cargo shipment with destination information
When
The system checks the destination province/state codes
Then
The cargo is identified as having US destination history if the destination province/state code is not in the Canadian province list (NF, PE, NS, NB, PQ, ON, MB, SK, AB, BC, YT, NT)
R-GCX146-cbl-01558
Analyze Cargo Movement Patterns to Identify Valid Return Scenarios from US to Canada
Decision Rules
📊 Business Logic Narrative
When the process 'Analyze Cargo Movement Patterns to Identify Valid Return Scenarios from US to Canada' is invoked, and assuming that a cargo shipment with origin and destination information, when the system analyzes the movement pattern, the desired outcome is that the system determines if this represents a valid us to canada return movement based on origin/destination codes.
💻 Technical Criteria
Given
A cargo shipment with origin and destination information
When
The system analyzes the movement pattern
Then
The system determines if this represents a valid US to Canada return movement based on origin/destination codes
R-GCX146-cbl-01559
Cargo Moving from US to Canada?
Validation Rules
📊 Business Logic Narrative
When the process 'Cargo Moving from US to Canada?' is invoked, and assuming that cargo with origin and destination location codes, when the origin is a us state code and destination is a canadian province code, the desired outcome is that the system identifies this as a us to canada movement eligible for return processing.
💻 Technical Criteria
Given
Cargo with origin and destination location codes
When
The origin is a US state code and destination is a Canadian province code
Then
The system identifies this as a US to Canada movement eligible for return processing
R-GCX146-cbl-01565
Set Transit Status to 'R' for Return
Action Rules
📊 Business Logic Narrative
When the process 'Set Transit Status to 'R' for Return' is invoked, and assuming that valid return movement scenario, when transit status needs to be set for the cargo, the desired outcome is that the system assigns transit status 'r' to indicate return movement.
💻 Technical Criteria
Given
Valid return movement scenario
When
Transit status needs to be set for the cargo
Then
The system assigns transit status 'R' to indicate return movement
R-GCX146-cbl-01849
Call FWCARGET with Equipment ID
Action Rules
📊 Business Logic Narrative
When the process 'Call FWCARGET with Equipment ID' is invoked, and assuming that equipment id search criteria is established, when the system calls fwcarget function with the equipment identifier, the desired outcome is that database query is executed against shiproot shipment database using multi-criteria search capabilities.
💻 Technical Criteria
Given
Equipment ID search criteria is established
When
The system calls FWCARGET function with the equipment identifier
Then
Database query is executed against SHIPROOT shipment database using multi-criteria search capabilities
R-GCX146-cbl-01093
W400A-COMPRESS-EQUIP: Organize Numeric Sequences
Process Rules
📊 Business Logic Narrative
When the process 'W400A-COMPRESS-EQUIP: Organize Numeric Sequences' is invoked, and assuming that an equipment identifier containing numeric sequences, when the system processes the equipment number for compression, the desired outcome is that numeric sequences are identified, formatted, and reorganized according to standard equipment numbering conventions.
💻 Technical Criteria
Given
An equipment identifier containing numeric sequences
When
The system processes the equipment number for compression
Then
Numeric sequences are identified, formatted, and reorganized according to standard equipment numbering conventions
R-GCX146-cbl-01094
Identify Numeric Sequences
Validation Rules
📊 Business Logic Narrative
When the process 'Identify Numeric Sequences' is invoked, and assuming that an equipment identifier with mixed alphanumeric characters, when the system analyzes the identifier structure, the desired outcome is that all consecutive numeric character sequences are identified and marked for formatting.
💻 Technical Criteria
Given
An equipment identifier with mixed alphanumeric characters
When
The system analyzes the identifier structure
Then
All consecutive numeric character sequences are identified and marked for formatting
R-GCX146-cbl-01095
Format Numeric Components
Computation Rules
📊 Business Logic Narrative
When the process 'Format Numeric Components' is invoked, and assuming that identified numeric sequences within an equipment identifier, when the system formats the numeric components, the desired outcome is that numeric sequences are formatted according to equipment numbering standards with proper padding and alignment.
💻 Technical Criteria
Given
Identified numeric sequences within an equipment identifier
When
The system formats the numeric components
Then
Numeric sequences are formatted according to equipment numbering standards with proper padding and alignment
R-GCX146-cbl-01101
Access US Customs Route Information
Action Rules
📊 Business Logic Narrative
When the process 'Access US Customs Route Information' is invoked, and assuming that a cargo shipment requires us customs validation, when the system attempts to access us route data using the cargo's customs control number, the desired outcome is that the system retrieves us customs route segment data if it exists.
💻 Technical Criteria
Given
A cargo shipment requires US customs validation
When
The system attempts to access US route data using the cargo's customs control number
Then
The system retrieves US customs route segment data if it exists
R-GCX146-cbl-01102
US Route Data Found?
Decision Rules
📊 Business Logic Narrative
When the process 'US Route Data Found?' is invoked, and assuming that the system has attempted to access us route data for a cargo shipment, when the system checks if us route segment data was successfully retrieved, the desired outcome is that if us route data exists, proceed with bond type validation, otherwise skip us customs validation.
💻 Technical Criteria
Given
The system has attempted to access US route data for a cargo shipment
When
The system checks if US route segment data was successfully retrieved
Then
If US route data exists, proceed with bond type validation, otherwise skip US customs validation
R-GCX146-cbl-01103
Validate Bond Type
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Bond Type' is invoked, and assuming that us route data exists for a cargo shipment, when the system examines the bond type field in the us route data, the desired outcome is that the bond type must be one of: it (in-transit), tr (transportation), te (temporary export), or mt (merchandise in transit).
💻 Technical Criteria
Given
US route data exists for a cargo shipment
When
The system examines the bond type field in the US route data
Then
The bond type must be one of: IT (In-Transit), TR (Transportation), TE (Temporary Export), or MT (Merchandise in Transit)
R-GCX146-cbl-01104
IT Bond Type
Policy Rules
📊 Business Logic Narrative
When the process 'IT Bond Type' is invoked, and assuming that a cargo shipment has us route data with bond type 'it', when the system processes the it bond type cargo, the desired outcome is that generate appropriate warning messages for in-transit bond requirements and restrictions.
💻 Technical Criteria
Given
A cargo shipment has US route data with bond type 'IT'
When
The system processes the IT bond type cargo
Then
Generate appropriate warning messages for in-transit bond requirements and restrictions
R-GCX146-cbl-01105
TR Bond Type
Process Rules
📊 Business Logic Narrative
When the process 'TR Bond Type' is invoked, and assuming that a cargo shipment has us route data with bond type 'tr', when the system processes the tr bond type cargo, the desired outcome is that apply transportation bond specific validation rules and generate appropriate status messages.
💻 Technical Criteria
Given
A cargo shipment has US route data with bond type 'TR'
When
The system processes the TR bond type cargo
Then
Apply transportation bond specific validation rules and generate appropriate status messages
R-GCX146-cbl-01106
TE Bond Type
Process Rules
📊 Business Logic Narrative
When the process 'TE Bond Type' is invoked, and assuming that a cargo shipment has us route data with bond type 'te', when the system processes the te bond type cargo, the desired outcome is that apply temporary export bond validation rules and generate export-related status messages.
💻 Technical Criteria
Given
A cargo shipment has US route data with bond type 'TE'
When
The system processes the TE bond type cargo
Then
Apply temporary export bond validation rules and generate export-related status messages
R-GCX146-cbl-01107
MT Bond Type
Process Rules
📊 Business Logic Narrative
When the process 'MT Bond Type' is invoked, and assuming that a cargo shipment has us route data with bond type 'mt', when the system processes the mt bond type cargo, the desired outcome is that apply merchandise in transit bond validation rules and generate transit-related status messages.
💻 Technical Criteria
Given
A cargo shipment has US route data with bond type 'MT'
When
The system processes the MT bond type cargo
Then
Apply merchandise in transit bond validation rules and generate transit-related status messages
R-GCX146-cbl-01108
Cargo In-Transit?
Decision Rules
📊 Business Logic Narrative
When the process 'Cargo In-Transit?' is invoked, and assuming that a cargo shipment has valid us route data with a recognized bond type, when the system checks the in-transit status indicator in the us route data, the desired outcome is that if cargo is marked as in-transit, proceed with location validation, otherwise proceed with vessel validation.
💻 Technical Criteria
Given
A cargo shipment has valid US route data with a recognized bond type
When
The system checks the in-transit status indicator in the US route data
Then
If cargo is marked as in-transit, proceed with location validation, otherwise proceed with vessel validation
R-GCX146-cbl-01109
Location Valid?
Validation Rules
📊 Business Logic Narrative
When the process 'Location Valid?' is invoked, and assuming that a cargo shipment is marked as in-transit in us route data, when the system validates the current location information against expected transit locations, the desired outcome is that if location is valid, proceed with vessel validation, otherwise generate location warning message.
💻 Technical Criteria
Given
A cargo shipment is marked as in-transit in US route data
When
The system validates the current location information against expected transit locations
Then
If location is valid, proceed with vessel validation, otherwise generate location warning message
R-GCX146-cbl-01110
Vessel = 'TRAIN'?
Decision Rules
📊 Business Logic Narrative
When the process 'Vessel = 'TRAIN'?' is invoked, and assuming that a cargo shipment has completed location validation (if applicable), when the system examines the vessel name field in the us route data, the desired outcome is that if vessel name equals 'train', generate train-specific warning, otherwise generate other vessel warning.
💻 Technical Criteria
Given
A cargo shipment has completed location validation (if applicable)
When
The system examines the vessel name field in the US route data
Then
If vessel name equals 'TRAIN', generate train-specific warning, otherwise generate other vessel warning
R-GCX146-cbl-01111
Generate Train Vessel Warning
Policy Rules
📊 Business Logic Narrative
When the process 'Generate Train Vessel Warning' is invoked, and assuming that a cargo shipment has vessel name designated as 'train', when the system processes train vessel cargo, the desired outcome is that generate train-specific warning messages related to rail transportation requirements and restrictions.
💻 Technical Criteria
Given
A cargo shipment has vessel name designated as 'TRAIN'
When
The system processes train vessel cargo
Then
Generate train-specific warning messages related to rail transportation requirements and restrictions
R-GCX146-cbl-01112
Generate Other Vessel Warning
Policy Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Other Vessel Warning', assuming that a cargo shipment has vessel name that is not 'train', when the system processes non-train vessel cargo, the desired outcome is that generate vessel-specific warning messages appropriate for the transportation method.
💻 Technical Criteria
EXCLUDING
A cargo shipment has vessel name that is not 'TRAIN'
When
The system processes non-train vessel cargo
Then
Generate vessel-specific warning messages appropriate for the transportation method
R-GCX146-cbl-01113
Generate Bond Type Warning Message
Policy Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Generate Bond Type Warning Message', assuming that a cargo shipment has us route data with an invalid or unrecognized bond type, when the system encounters a bond type that is not it, tr, te, or mt, the desired outcome is that generate a warning message indicating invalid bond type and potential compliance issues.
💻 Technical Criteria
EXCLUDING
A cargo shipment has US route data with an invalid or unrecognized bond type
When
The system encounters a bond type that is not IT, TR, TE, or MT
Then
Generate a warning message indicating invalid bond type and potential compliance issues
R-GCX146-cbl-01114
Generate Location Warning Message
Policy Rules
📊 Business Logic Narrative
When the process 'Generate Location Warning Message' is invoked, and assuming that a cargo shipment is marked as in-transit but has invalid location information, when the system detects location validation failure, the desired outcome is that generate a warning message indicating location mismatch or invalid transit location.
💻 Technical Criteria
Given
A cargo shipment is marked as in-transit but has invalid location information
When
The system detects location validation failure
Then
Generate a warning message indicating location mismatch or invalid transit location
R-GCX146-cbl-01115
Generate In-Transit Warning Message
Policy Rules
📊 Business Logic Narrative
When the process 'Generate In-Transit Warning Message' is invoked, and assuming that a cargo shipment has in-transit status issues or validation failures, when the system processes in-transit cargo with identified problems, the desired outcome is that generate comprehensive warning messages covering all in-transit related issues and compliance requirements.
💻 Technical Criteria
Given
A cargo shipment has in-transit status issues or validation failures
When
The system processes in-transit cargo with identified problems
Then
Generate comprehensive warning messages covering all in-transit related issues and compliance requirements
R-GCX146-cbl-01116
Compile All Warning Messages
Process Rules
📊 Business Logic Narrative
When the process 'Compile All Warning Messages' is invoked, and assuming that the system has processed us customs validation and generated various warning messages, when all individual warning messages have been created, the desired outcome is that compile all warning messages into a single comprehensive report for the cargo shipment.
💻 Technical Criteria
Given
The system has processed US customs validation and generated various warning messages
When
All individual warning messages have been created
Then
Compile all warning messages into a single comprehensive report for the cargo shipment
R-GCX146-cbl-01117
No US Route Data - Skip Validation
Decision Rules
📊 Business Logic Narrative
When the process 'No US Route Data - Skip Validation' is invoked, and assuming that a cargo shipment has no us route data available, when the system attempts to perform us customs validation, the desired outcome is that skip all us customs validation processes and proceed with normal cargo processing.
💻 Technical Criteria
Given
A cargo shipment has no US route data available
When
The system attempts to perform US customs validation
Then
Skip all US customs validation processes and proceed with normal cargo processing
R-GCX146-cbl-01120
Format Equipment Car Identifier
Action Rules
📊 Business Logic Narrative
When the process 'Format Equipment Car Identifier' is invoked, and assuming that an equipment car identifier needs to be formatted, when the system processes the car identifier for display or storage, the desired outcome is that the system applies standard 12-character formatting using gcccarfm utility.
💻 Technical Criteria
Given
An equipment car identifier needs to be formatted
When
The system processes the car identifier for display or storage
Then
The system applies standard 12-character formatting using GCCCARFM utility
R-GCX146-cbl-01121
Validate Car ID Format
Validation Rules
📊 Business Logic Narrative
When the process 'Validate Car ID Format' is invoked, and assuming that a formatted equipment car identifier, when the system validates the car id format, the desired outcome is that the system confirms the car id meets required format standards or flags format errors.
💻 Technical Criteria
Given
A formatted equipment car identifier
When
The system validates the car ID format
Then
The system confirms the car ID meets required format standards or flags format errors
R-GCX146-cbl-01122
Store in Equipment Record
Process Rules
📊 Business Logic Narrative
When the process 'Store in Equipment Record' is invoked, and assuming that a validated and formatted car identifier, when the system completes car id formatting process, the desired outcome is that the formatted car id is stored in the equipment record and made available for processing.
💻 Technical Criteria
Given
A validated and formatted car identifier
When
The system completes car ID formatting process
Then
The formatted car ID is stored in the equipment record and made available for processing
R-GCX146-cbl-01123
Set Formatted Car ID for Display
Process Rules
📊 Business Logic Narrative
When the process 'Set Formatted Car ID for Display' is invoked, and assuming that a validated car identifier, when the system prepares the car id for display purposes, the desired outcome is that the car id is formatted according to display standards and stored in appropriate display fields.
💻 Technical Criteria
Given
A validated car identifier
When
The system prepares the car ID for display purposes
Then
The car ID is formatted according to display standards and stored in appropriate display fields
R-GCX146-cbl-01149
Equipment Car Type Description Retrieval
Action Rules
📊 Business Logic Narrative
When the process 'Equipment Car Type Description Retrieval' is invoked, and assuming that a piece of equipment with a car type code needs to be displayed on a trip sheet, when the system processes the equipment for trip sheet generation, the desired outcome is that the system should lookup the car type description from the equipment type reference table and populate it in the trip sheet detail, or use a default description if lookup fails.
💻 Technical Criteria
Given
A piece of equipment with a car type code needs to be displayed on a trip sheet
When
The system processes the equipment for trip sheet generation
Then
The system should lookup the car type description from the equipment type reference table and populate it in the trip sheet detail, or use a default description if lookup fails
R-GCX146-cbl-01150
Access GCSTBRT VI Segment
Process Rules
📊 Business Logic Narrative
When the process 'Access GCSTBRT VI Segment' is invoked, and assuming that a car type code exists for equipment being processed, when the system needs to retrieve the corresponding car type description, the desired outcome is that the system should access the vi segment of the gcstbrt table using the car type as the lookup key.
💻 Technical Criteria
Given
A car type code exists for equipment being processed
When
The system needs to retrieve the corresponding car type description
Then
The system should access the VI segment of the GCSTBRT table using the car type as the lookup key
R-GCX146-cbl-01151
Move Description to Trip Sheet Detail
Process Rules
📊 Business Logic Narrative
When the process 'Move Description to Trip Sheet Detail' is invoked, and assuming that a car type description has been successfully retrieved from the reference table, when the description data is available for assignment, the desired outcome is that the system should move the retrieved description to the appropriate field in the trip sheet detail record.
💻 Technical Criteria
Given
A car type description has been successfully retrieved from the reference table
When
The description data is available for assignment
Then
The system should move the retrieved description to the appropriate field in the trip sheet detail record
R-GCX146-cbl-01152
Set Default Description
Validation Rules
📊 Business Logic Narrative
<EXCLUSION LOGIC> For the process 'Set Default Description', assuming that a car type code does not have a corresponding description in the reference table, when the car type description lookup fails to find a match, the desired outcome is that the system should assign a default description value to ensure the trip sheet field is populated.
💻 Technical Criteria
EXCLUDING
A car type code does not have a corresponding description in the reference table
When
The car type description lookup fails to find a match
Then
The system should assign a default description value to ensure the trip sheet field is populated
R-GCX146-cbl-01163
Insert New Train Record with Equipment Details
Action Rules
📊 Business Logic Narrative
When the process 'Insert New Train Record with Equipment Details' is invoked, and assuming that either no existing train record was found or existing record was successfully deleted, when the system performs an insert operation for the new train record with equipment details, the desired outcome is that a new train record should be created in the gcsb4rt database with status set to sent and all equipment details included.
💻 Technical Criteria
Given
Either no existing train record was found or existing record was successfully deleted
When
The system performs an insert operation for the new train record with equipment details
Then
A new train record should be created in the GCSB4RT database with status set to SENT and all equipment details included