CN Rail
/
Rail Carrier Waybill Interchange
  • Specification
  • EDI Inspector
Import
Stedi maintains this guide based on public documentation from CN Rail. Contact CN Rail for official EDI specifications. To report any errors in this guide, please contact us.
Go to EDI Guide Catalog
CN Rail logo

X12 417 Rail Carrier Waybill Interchange

X12 Release 7030

This X12 Transaction Set contains the format and establishes the data contents of the Rail Carrier Waybill Interchange Transaction Set (417) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the rail carrier with detailed movement instructions pertinent to a rail carrier shipment and is used by all Class I rail carriers in the United States and Canada.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build free EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    0100
    Transaction Set Header
    Max use 1
    Required
    BX
    0300
    General Shipment Information
    Max use 1
    Optional
    BNX
    0400
    Rail Shipment Information
    Max use 1
    Optional
    N9
    0500
    Bill of Lading Number
    Max use 30
    Optional
    N9
    0500
    Weight Agreement Number
    Max use 30
    Optional
    N9
    0500
    Purchase Order Number
    Max use 30
    Optional
    N7 Loop
    F9
    2000
    Origin Station
    Max use 1
    Required
    D9
    2100
    Destination Station
    Max use 1
    Required
    R2
    4700
    Route Information
    Max use 13
    Required
    LX Loop
    LX
    5400
    Transaction Set Line Number
    Max use 1
    Required
    L5
    5500
    Description, Marks and Numbers
    Max use 15
    Required
    L0 Loop
    SE
    8100
    Transaction Set Trailer
    Max use 1
    Required
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

    To start and identify an interchange of zero or more functional groups and interchange-related control segments

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code identifying the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code identifying the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I65
    Repetition Separator
    Required
    Min 1Max 1

    Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

    ^
    Repetition Separator
    ISA-12
    I11
    Interchange Control Version Number Code
    Required

    Code specifying the version number of the interchange control segments

    00703
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2014
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested Code
    Required
    Min 1Max 1

    Code indicating sender's request for an interchange acknowledgment

    0
    No Interchange Acknowledgment Requested
    1
    Interchange Acknowledgment Requested (TA1)
    2
    Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors"
    3
    Interchange Acknowledgment Requested only when Interchange is "Rejected Because Of Errors" or "Accepted but Errors are Noted"
    ISA-15
    I14
    Interchange Usage Indicator Code
    Required
    Min 1Max 1

    Code indicating whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    Min 1Max 1

    Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

    >
    Component Element Separator

    Functional Group Header

    RequiredMax use 1

    To indicate the beginning of a functional group and to provide control information

    Example
    GS-01
    479
    Functional Identifier Code
    Required

    Code identifying a group of application related transaction sets

    WB
    Rail Carrier Waybill Interchange (417)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission; codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

    007030
    Standards Approved for Publication by ASC X12 Procedures Review Board through October 2015

    Heading

    ST
    0100

    Transaction Set Header

    RequiredMax use 1

    To indicate the start of a transaction set and to assign a control number

    Example
    ST-01
    143
    Transaction Set Identifier Code
    Required

    Code identifying a Transaction Set

    • The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    417
    Rail Carrier Waybill Interchange
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    BX
    0300

    General Shipment Information

    OptionalMax use 1

    To transmit identification numbers and other basic shipment data

    • BX05 contains the Standard Carrier Alpha Code (SCAC) of the original roadhaul carrier receiving the shipment.
    Usage notes

    Example: BX00RPP**CNL*B

    Example
    BX-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BX-02
    91
    Transportation Method/Type Code
    Required

    Code specifying the method or type of transportation for the shipment

    R
    Rail
    BX-03
    146
    Shipment Method of Payment Code
    Required

    Code identifying payment terms for transportation charges

    CC
    Collect
    PP
    Prepaid (by Seller)
    BX-05
    140
    Standard Carrier Alpha Code
    Optional

    Code identifying the Standard Carrier Alpha Code

    CN
    CN Rail
    BX-06
    188
    Weight Unit Code
    Optional

    Code specifying the weight unit

    K
    Kilograms
    L
    Pounds
    BX-07
    147
    Shipment Qualifier
    Optional

    Code specifying relationship of this shipment with respect to other shipments given to the carrier at the same time

    B
    Bill of Lading for Individual Shipment
    BNX
    0400

    Rail Shipment Information

    OptionalMax use 1

    To transmit rail-specific shipment data

    Usage notes

    Example: BNX*R**S

    Example
    BNX-01
    460
    Shipment Weight Code
    Optional

    Code indicating the way by which weights are obtained for a particular shipment

    A
    Shipper's Weight Agreement
    N
    Per Car Charge
    R
    Carrier Scale Weight
    BNX-03
    11
    Billing Code
    Optional
    Min 1Max 1

    Code indicating type of Bill

    N9
    0500

    Bill of Lading Number

    OptionalMax use 30

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Allows Reference Numbers to be sent to CN. At least one N9 containing a Bill of Lading number must be included. This number will be included on all other documents such as Freight Invoice and Remittance/Payment.

    Example: N9BM1257*201807101336

    Example
    Variants (all may be used)
    N9Weight Agreement NumberN9Purchase Order Number
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code identifying the Reference Identification

    BM
    Bill of Lading Number
    N9-02
    127
    Reference Identification
    Optional
    Min 1Max 15

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    N9-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    N9-05
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    N9
    0500

    Weight Agreement Number

    OptionalMax use 30

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Allows Reference Numbers to be sent to CN. At least one N9 containing a Bill of Lading number must be included. This number will be included on all other documents such as Freight Invoice and Remittance/Payment.

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code identifying the Reference Identification

    WM
    Weight Agreement Number
    N9-02
    127
    Reference Identification
    Optional
    Min 1Max 80

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    N9-04
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    N9-05
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    N9
    0500

    Purchase Order Number

    OptionalMax use 30

    To transmit identifying information as specified by the Reference Identification Qualifier

    Usage notes

    Allows Reference Numbers to be sent to CN. At least one N9 containing a Bill of Lading number must be included. This number will be included on all other documents such as Freight Invoice and Remittance/Payment.

    Example
    N9-01
    128
    Reference Identification Qualifier
    Required

    Code identifying the Reference Identification

    PO
    Purchase Order Number
    N9-02
    127
    Reference Identification
    Optional
    Min 1Max 80

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    N9-04
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

    N9-05
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    N7 Loop
    RequiredMax >1
    N7
    0800

    Equipment Details

    RequiredMax use 1

    To identify the equipment

    Usage notes

    Example: N7CN123456213360N*******RR

    Example
    If either Weight (N7-03) or Weight Qualifier (N7-04) is present, then the other is required
    N7-01
    206
    Equipment Initial
    Optional
    Min 1Max 4

    Prefix or alphabetic part of an equipment unit's identifying number

    • N701 is mandatory for rail transactions.
    N7-02
    207
    Equipment Number
    Required
    Min 1Max 15

    Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

    N7-03
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    N7-04
    187
    Weight Qualifier
    Optional

    Code specifying the type of weight

    E
    Estimated Net Weight
    N
    Actual Net Weight
    N7-11
    40
    Equipment Description Code
    Optional

    Code identifying type of equipment used for shipment

    RR
    Rail Car
    F9
    2000

    Origin Station

    RequiredMax use 1

    To identify the rail origin of the shipment

    Usage notes

    Indicates the origin of the shipment, the point from which it is shipped. The spelling should be in accordance with that listed in the Standard Point Location Code (SPLC) standard available from the National Motor Freight Tariff Association (USA) or the National Transportation Agency (Canada). CN can provide spellings for your stations.

    Example: F9*WATSONSK

    Example
    F9-02
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    • F902 is the origin station for movement.
    F9-03
    156
    State or Province Code
    Required
    Min 2Max 2

    Code specifying the Standard State/Province as defined by appropriate government agency

    D9
    2100

    Destination Station

    RequiredMax use 1

    To identify the rail destination of the shipment

    Usage notes

    Indicates the destination of the shipment, the point at which it will be unloaded or where the transportation responsibility reverts to the consignee. The spelling should be in accordance with that listed in the
    Standard Point Location Code (SPLC) standard available from the National Motor Freight Tariff Association (USA) or the National Transportation Agency (Canada). CN can provide spellings for your stations.

    Example: D9*VANCOUVERBC

    Example
    D9-02
    19
    City Name
    Required
    Min 2Max 30

    Free-form text for city name

    • D902 is the destination station of movement.
    D9-03
    156
    State or Province Code
    Required
    Min 2Max 2

    Code specifying the Standard State/Province as defined by appropriate government agency

    N1 Loop
    RequiredMax >1
    Usage notes

    Associated to the N3 and N4 segments below. N1, N3 and N4 segments are repeated for the Consignee and any other Additional Parties to the shipment.

    Example:
    N1SHGENERIC CARLOAD INC
    N3123 ROAD
    N4
    WATSONSKS0K 4V0
    N1CNGENERIC CONSIGNEE CO
    N312 SMITH STREET
    N4
    VANCOUVERBCV5K 1P7
    N1PFGENERIC CARLOAD INC
    N3123 ROAD
    N4
    WATSONSKS0K 4V0

    N1
    2200

    Party Identification

    RequiredMax use 1

    To identify a party by type of organization, name, and code

    Example
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    C1
    In Care Of Party no. 1
    CN
    Consignee
    PF
    Party to Receive Freight Bill
    SH
    Shipper
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N3
    2300

    Party Location

    OptionalMax use 2

    To specify the location of the named party

    Example
    N3-01
    166
    Address Information
    Required
    Min 1Max 55

    Address information

    N3-02
    166
    Address Information
    Optional
    Min 1Max 55

    Address information

    N4
    2400

    Geographic Location

    OptionalMax use 1

    To specify the geographic place of the named party

    Example
    N4-01
    19
    City Name
    Optional
    Min 2Max 30

    Free-form text for city name

    • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
    N4-02
    156
    State or Province Code
    Optional
    Min 2Max 2

    Code specifying the Standard State/Province as defined by appropriate government agency

    N4-03
    116
    Postal Code
    Optional
    Min 3Max 15

    Code specifying international postal zone code excluding punctuation and blanks (zip code for United States)

    • N403 contains the postal code in an unstructured format. N408 contains the postal code in a structured format. When a postal code data field is used, the parties shall agree as to which data element (N403 or N408) shall be used in the transaction set.
    PER
    2500

    Administrative Communications Contact

    OptionalMax use 2

    To identify a person or office to whom administrative communications should be directed

    Usage notes

    Example: PERICCONTACT NAMETE123-123-1234

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    IC
    Information Contact
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Optional
    Min 1Max 2048

    Complete communications number including country or area code when applicable

    R2
    4700

    Route Information

    RequiredMax use 13

    To specify carrier and routing sequences and details

    Usage notes

    One R2 segment for each railroad in the route. CN can provide route information for your shipments (ie: Railroad SCAC's and junctions).

    Example: R2CNS****R

    Example
    R2-01
    140
    Standard Carrier Alpha Code
    Required

    Code identifying the Standard Carrier Alpha Code

    CN
    CN Rail
    R2-02
    133
    Routing Sequence Code
    Required

    Code specifying the relationship of a carrier to a specific shipment movement

    S
    Origin Carrier, Shipper's Routing (Rail)
    R2-06
    91
    Transportation Method/Type Code
    Optional

    Code specifying the method or type of transportation for the shipment

    R
    Rail
    LX Loop
    RequiredMax >1
    LX
    5400

    Transaction Set Line Number

    RequiredMax use 1

    To reference a line number in a transaction set

    Usage notes

    Example: LX*1

    Example
    LX-01
    554
    Assigned Number
    Required
    Min 1Max 6

    Number assigned for differentiation within a transaction set

    L5
    5500

    Description, Marks and Numbers

    RequiredMax use 15

    To specify the line item in terms of description, quantity, packaging, and marks and numbers

    Usage notes

    CN can provide Standard Transportation Commodity Codes (STCC) for your commodities. The commodity code is required only on the first L5 segment. Additional L5 segments can be used to provide additional description of lading.

    Example: L51WALLBOARD3275440T

    Example
    If either Commodity Code (L5-03) or Commodity Code Qualifier (L5-04) is present, then the other is required
    L5-01
    213
    Lading Line Item Number
    Optional
    Min 1Max 6

    Sequential line number for a lading item

    L5-02
    79
    Lading Description
    Optional
    Min 1Max 50

    Description of an item as required for rating and billing purposes

    • L502 may be used to send quantity information as part of the product description.
    L5-03
    22
    Commodity Code
    Optional
    Min 1Max 30

    Code describing a commodity or group of commodities

    Usage notes

    7 digit Standard Transportation Commodity Code (STCC).

    Example: WALLBOARD = 3275440

    L5-04
    23
    Commodity Code Qualifier
    Optional

    Code identifying the commodity coding system used for Commodity Code

    T
    Standard Transportation Commodity Code (STCC)
    L0 Loop
    OptionalMax >1
    L0
    5700

    Line Item - Quantity and Weight

    RequiredMax use 1

    To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data

    Usage notes

    Example: L01213360N1*CLD

    Example
    If either Weight (L0-04) or Weight Qualifier (L0-05) is present, then the other is required
    If either Lading Quantity (L0-08) or Packaging Form Code (L0-09) is present, then the other is required
    L0-01
    213
    Lading Line Item Number
    Optional
    Min 1Max 6

    Sequential line number for a lading item

    L0-04
    81
    Weight
    Optional
    Min 1Max 10

    Numeric value of weight

    L0-05
    187
    Weight Qualifier
    Optional

    Code specifying the type of weight

    E
    Estimated Net Weight
    N
    Actual Net Weight
    L0-08
    80
    Lading Quantity
    Optional
    Min 1Max 7

    Number of units (pieces) of the lading commodity

    • L008 is the number of handling units of the line item tendered to the carrier.
    L0-09
    211
    Packaging Form Code
    Optional

    Code specifying the packaging form of the lading quantity

    CLD
    Car Load, Rail
    SE
    8100

    Transaction Set Trailer

    RequiredMax use 1

    To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

    Total number of segments included in a transaction set including ST and SE segments

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    Functional Group Trailer

    RequiredMax use 1

    To indicate the end of a functional group and to provide control information

    Example
    GE-01
    97
    Number of Transaction Sets Included
    Required
    Min 1Max 6

    Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

    GE-02
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    ST*417*988260001
    BX*00*R*PP**CN*L*B
    BNX*R**S
    N9*BM*1257**20180710*1336
    N7*CN*123456*213360*N*******RR
    F9**WATSON*SK
    D9**VANCOUVER*BC
    N1*SH*GENERIC CARLOAD INC
    N3*123 ROAD
    N4*WATSON*SK*S0K 4V0
    PER*IC*CONTACT NAME*TE*123-123-1234
    N1*CN*GENERIC CONSIGNEE CO
    N3*12 SMITH STREET
    N4*VANCOUVER*BC*V5K 1P7
    N1*PF*GENERIC CARLOAD INC
    N3*123 ROAD
    N4*WATSON*SK*S0K 4V0
    R2*CN*S****R
    LX*1
    L5*1*WALLBOARD*3275440*T
    L0*1***213360*N***1*CLD
    SE*27*988260001

    Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.