§228.203. Program components. — Inbound Citations

(1) The system used to generate the electronic record meets all requirements of this paragraph (a) of this section and all requirements of §§ 228.203 and 228.205;

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(11) Disallow any manipulation of the tie-up process that precludes compliance with any of the requirements specified by paragraphs (c)(1) through (c)(10) of this section.

(2) The data fields are searchable as described in § 228.203(d) and yield access to all records matching criteria specified in a search.

(d) The program must contain sufficient search criteria to allow any record to be retrieved through a search of any one or more of the following data fields, by specific date or by a date range not exceeding 30 days for the data fields specified by paragraphs (d)(1) and (d)(2) of this section, and not exceeding one day for the data fields specified by paragraphs (d)(3) through (d)(7) of this section:

(1) Employee, by name or identification number;

(2) Train or job symbol;

(3) Origin location, either yard or station;

(4) Released location, either yard or station;

(5) Operating territory (i.e., division or service unit, subdivision, or railroad-identified line segment);

(6) Certified records containing one or more instances of excess service; and

(d) The program must contain sufficient search criteria to allow any record to be retrieved through a search of any one or more of the following data fields, by specific date or by a date range not exceeding 30 days for the data fields specified by paragraphs (d)(1) and (d)(2) of this section, and not exceeding one day for the data fields specified by paragraphs (d)(3) through (d)(7) of this section:

(1) Employee, by name or identification number;

(2) Train or job symbol;

(3) Origin location, either yard or station;

(4) Released location, either yard or station;

(5) Operating territory (i.e., division or service unit, subdivision, or railroad-identified line segment);

(6) Certified records containing one or more instances of excess service; and

(d) The program must contain sufficient search criteria to allow any record to be retrieved through a search of any one or more of the following data fields, by specific date or by a date range not exceeding 30 days for the data fields specified by paragraphs (d)(1) and (d)(2) of this section, and not exceeding one day for the data fields specified by paragraphs (d)(3) through (d)(7) of this section:

(1) Employee, by name or identification number;

(2) Train or job symbol;

(3) Origin location, either yard or station;

(4) Released location, either yard or station;

(5) Operating territory (i.e., division or service unit, subdivision, or railroad-identified line segment);

(6) Certified records containing one or more instances of excess service; and

(d) The program must contain sufficient search criteria to allow any record to be retrieved through a search of any one or more of the following data fields, by specific date or by a date range not exceeding 30 days for the data fields specified by paragraphs (d)(1) and (d)(2) of this section, and not exceeding one day for the data fields specified by paragraphs (d)(3) through (d)(7) of this section:

(1) Employee, by name or identification number;

(2) Train or job symbol;

(3) Origin location, either yard or station;

(4) Released location, either yard or station;

(5) Operating territory (i.e., division or service unit, subdivision, or railroad-identified line segment);

(6) Certified records containing one or more instances of excess service; and

(d) The program must contain sufficient search criteria to allow any record to be retrieved through a search of any one or more of the following data fields, by specific date or by a date range not exceeding 30 days for the data fields specified by paragraphs (d)(1) and (d)(2) of this section, and not exceeding one day for the data fields specified by paragraphs (d)(3) through (d)(7) of this section:

(1) Employee, by name or identification number;

(2) Train or job symbol;

(3) Origin location, either yard or station;

(4) Released location, either yard or station;

(5) Operating territory (i.e., division or service unit, subdivision, or railroad-identified line segment);

(6) Certified records containing one or more instances of excess service; and