Waybill_SOW.doc

SUPPLIES OR SERVICES AND PRICES/COSTS

Schedule of items and Prices – Firm Fixed-Price.

a. The Contractor shall provide all qualified personnel, facilities, equipment, logistical support and other materials and/or services necessary to perform the effort.

b. In consideration thereof, the Contractor shall be paid the respective firm fixed-price for each exercised performance period identified below for successful performance of the waybill processing services.

CARLOAD WAYBILL LOT I

0001 - PHASE I

Period of Performance: January 1, 2015 – May 31, 2016 Collection and editing of the Waybill File excluding field numbers 18, 24, 89, 97-119, 122-131, 134, 138-141, 145-152, 155-156, and 180-191.

0002 - PHASE II

Period of Performance: January 1, 2015 – May 31, 2016 Miling and modifying the waybill sample adding fields 24, 113 through 123, and 145 through 156 using the Princeton Transportation Network Model (PTNM)

Generating the Public Use Waybill File.

CARLOAD WAYBILL LOT II

1001 - PHASE I

Period of Performance: January 1, 2016 – May 31, 2017 Collection and editing of the Waybill File excluding field numbers 18, 24, 89, 97-119, 122-131, 134, 138-141, 145-152, 155-156, and 180-191.

1002 - PHASE II

Period of Performance: January 1, 2016 – May 31, 2017 Miling and modifying the waybill sample adding fields 24, 113 through 123, and 145 through 156 using the Princeton Transportation Network Model (PTNM)

CARLOAD WAYBILL LOT III

2001 - PHASE I

Period of Performance: January 1, 2017 – May 31, 2018 Collection and editing of the Waybill File excluding field numbers 18, 24, 89, 97-119, 122-131, 134, 138-141, 145-152, 155-156, and 180-191.

2002 - PHASE II

Period of Performance: January 1, 2017 – May 31, 2018 Miling and modifying the waybill sample adding fields 24, 113 through 123, and 145 through 156 using the Princeton Transportation Network Model (PTNM)

CARLOAD WAYBILL LOT IV

3001 - PHASE I

Period of Performance: January 1, 2018 – May 31, 2019

Collection and editing of the Waybill File excluding field numbers 18, 24, 89, 97-119, 122-131, 134, 138-141, 145-152, 155-156, and 180-191.

3002 - PHASE II

Period of Performance: January 1, 2018 – May 31, 2019

Miling and modifying the waybill sample adding fields 24, 113 through 123, and 145 through 156 using the Princeton Transportation Network Model (PTNM)

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT tc " SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT "

GENERAL

Background.

SEQ CHAPTER \h \r 1The Carload Waybill Sample is a sample of waybills for terminated shipments by rail carriers. The Government requires that railroads submit waybill sample data if, in any of the three preceding years, the railroad terminated at least 4,500 revenue carloads on its line or if it terminates at least 5% of the revenue carloads terminating in any state in any of the preceding years. These railroads may file waybill sample information by using either: (1) authenticated copies of a sample of audited revenue waybills (the manual system); or (2) a computer generated sample containing specified information (the computerized system or MRI), or (3) submitting the information via FTP/MQ. The waybill submissions from these methods are combined in a 900 byte Master Record File.

Scope The Federal Railroad Administration and Surface Transportation Board are soliciting offers from contractors with the expertise necessary to build the Government a complete, accurate and confidential Master Waybill File and Public Use File. This Statement of Work (SOW) separates the required tasks into two distinct phases. In first phase, the contractor shall collect and process waybill data from the railroads; draw the sample for certain railroads and edit and correct waybill data. The contractor shall provide this information to the Government on a quarterly basis so that the Government can monitor the data for errors and obtain resolution prior to the completion phase one of the Master Waybill File. In phase two, the contractor takes the Master Waybill File and computes the mileage for specific movements and makes additional modifications to the waybill file so that it is useable to the Government and other users.

The Waybill Sample identifies originating and terminating freight stations, the names of all railroads participating in the movement, the point of all railroad interchanges, the number of cars, the car types, and movement weight in hundredweight, the commodity and the freight revenue. The names of the shipper and consignee may be part of the railroad’s data submission, but are not included in the final sample data. However, other data in the sample such as the origin and destination Freight Station Accounting Code (FSAC) and seven-digit Standard Transportation Commodity Code (STCC) may permit the identification of a shipper and consignee. Thus, the data in this raw form is considered proprietary and must be treated as highly confidential because it can disclose each railroad's significant customers and the rate at which it transports the traffic. The Government has a stringent set of guidelines referenced in Section H of the contract as to who may access the data and in what form. The Public Use File, created from the Master File, aggregates the data to protect the confidentiality of specific shipper and railroad information.

Data from the Waybill Sample are used to carry out the regulatory responsibilities of the Board and as input to other Board projects, analyses and studies. Other Federal agencies (Department of Transportation, U.S. Department of Agriculture, etc) use the Waybill Sample as part of their information base. The Waybill Sample is also used by States as a major source of information for developing state transportation plans. In addition, non-government groups seek access to waybill sample data for such uses as market surveys, development of verified statements in Board and State formal proceedings, forecast of rail equipment requirements, economic analysis and forecasts, academic research, etc.

Applicable Documents and Specifications The following waybill specifications and industry reference files are applicable to this SOW.

2.1 Waybill Specifications.

2.1.1 Requirements for drawing the Sample (Appendix A)

2.1.2 Waybill Specifications for the Master Waybill File (Appendix A)

2.1.3 Waybill Specifications for the Public Use File (Appendix A)

2.1.4 Princeton Transportation Network Model (PTNM) (See 2.3)

2.1.5 Code of Federal Regulations 49 Part 1244 (See 2.3)

2.2 Industry Reference Files.

2.2.1 Standard Transportation Commodity Code (STCC)

2.2.2 Directory of Hazardous Material Shipping Descriptions

2.2.3 The Official Railway Equipment Register

2.2.4 Official Railroad Station List (OPSL 6000)

2.2.5 Centralized Station Master (CSM)

2.3 Availability of Waybill Specifications. Except for the contractor provided PTNM, the rest of the waybill specifications are included in the appendices to this solicitation. Code of Federal Regulations can be downloaded from http://www.access.gpo.gov/nara/cfr/waisidx_04/49cfr1244_04.html. The PTNM is available through ALK Technologies Inc, www.alk.com.

2.4 Availability of Industry Reference Files. Requests for STCC, Directory of Hazardous Material Shipping Descriptions and OPSL 6000, may be ordered from RAILINC Business Services Department, 7001 Weston Parkway, Cary, NC 27513. The Official Railway Equipment Register may be ordered from Commonwealth Business-Media, 400Windsor Corporate Park, 50 Millstone Road, Suite 200, East Windsor, NJ 08520-1415.

Requirements

3.1 General. The work required by this contract shall be performed in accordance with this SOW.

SEQ CHAPTER \h \r 1The waybill processing cycle covers a 17-month period. The 2015 waybill sample processing cycle starts January 1, 2015 and ends May 31, 2016. This cycle covers those movements entered into the railroad’s accounting system on or before December 31, 2014 and that have not been reported in a previous waybill sample. Movements that fall within this period are included as long as they terminate and are reported by the railroad by December 31, 2015. The contractor then has until May 31, 2016 to complete the waybill data processing. Subsequent years follow the same cycle, starting on January 1 and ending 16 months later on May 31. For three months of each year the contractor will be working on two different waybill sample years. The contract period shall extend approximately three months beyond the end of each processing cycle, and will end with the delivery and acceptance by the Government of the Public Use Waybill File.

The railroad waybill sample to be processed under this statement of work may be delivered to the contractor by the railroads by means of secure File Transfer Protocol (FTP) or Message Queues (MQ).

There are six railroads that submit their waybill data on a monthly basis and 45 railroads that submit 100% of their terminating waybills on a quarterly basis.

The contractor shall provide program management, quality control, and error correction procedures in accordance with the detail requirements of 3.2.2 below.

3.1.1 Personnel, Materials, Facilities and Automation.

3.1.1.1 Personnel. The contractor shall designate a single individual as Project Manager who is responsible for cost, schedule and technical performance. Further, SEQ CHAPTER \h \r 1the contractor shall ensure that the required level of expertise is applied to this effort. To be accepted for this contract, the contractor must offer key personnel with the following minimum requirements:

3.1.1.2 Material. SEQ CHAPTER \h \r 1The contractor shall furnish all material required to process the waybill data submitted by the railroad industry. This includes equipment, copies of forms OPAD-1 and OPAD-2 as required by certain railroads, and all other items necessary for the collection, maintenance, control, and processing of the sample. SEQ CHAPTER \h \r 1The contractor is responsible for making all arrangements necessary for access to the required Industry Reference Files (IRF). The contractor assumes all costs of obtaining the required Industry Reference Files and any other copyrighted materials. Government Furnished Equipment (GFE) is not required for this contract.

3.1.1.3 Facilities. All work associated with this contract will be performed at the contractor’s facilities.

3.2 Phase I

3.2.1 Collection of Waybill Data. The contractor shall collect waybill data from railroads using the format described in the 900 Byte STB Waybill File Layout in Appendix C excluding field numbers 18, 24, 89, 97-119, 122-131, 134, 138-141, 145-152, 155-156, and 180-191. To facilitate the identification of individual waybills, the contractor will assign a unique waybill serial number to each waybill. This waybill number will be the means for identifying that individual waybill throughout the remainder of the process.

3.2.2 Drawing the Sample. The contractor will also be responsible for drawing the sample from those railroads that report 100% of their terminating waybills using the sampling method listed in Appendix A. Currently, there are 45 railroads that report 100% of their terminating waybills.

3.2.3 Editing and Correcting Waybill Data. To facilitate the identification and the correction of data errors, the contractor will maintain an attribute transaction file. This file will track changes made to the Master File after the data is received from the railroads. After the initial load of the railroad’s data, every change made to an attribute in the Master File will be logged into this transaction file. For example, the file starts with the unique waybill serial number followed by the attribute number being modified (See Appendix C for these numbers). The old value and the new value of the data are then added. An explanation can be applied to the end of the record if necessary. Certain adjustments may require an explanation, and these explanations can be as simple as numeric codes agreed upon by the contractor and the Government. The data in this transaction file can be either in a fixed format or be delimited by a standard delimiter character.

This transaction file will help the Government identify the changes the contractor has made to the Master Waybill File. This file will be submitted quarterly along with the waybill data.

The contractor is expected to assist the Government to identify and correct data errors. This requires the contractor to establish and maintain a close working relationship with all railroads that submit waybill data. When data errors are discovered, the contractor should notify the reporting railroad to take corrective action. If the Government discovers the error as part of its review, then the Government will decide whether the contractor or the Government will initiate corrective action. In either case, the objective is to correct the data as quickly as possible to ensure a smooth flow of waybill data from the railroads through the contractor to the Government. The Government has 10 working days after each quarterly submission to notify the contractor to take action to correct the data. The contractor then has 15 working days to obtain the corrected data or advise the Government as to why the correction has not been made.

3.2.3.1 Required Edits.

SEQ CHAPTER \h \r 13.2.3.1.1 Car Initial - The car initial must be validated. The car initial must be a valid code. An invalid car initial will be counted against the 1% error limit. A list of all valid car initials with car initial owner will be provided to the STB on a CD-ROM.

3.2.3.1.2 Trailer or Container Initial - The trailer or container initial must be validated. A list of all valid initials with initial owner will be provided to the STB on a CD_ROM.

3.2.3.1.3 Intermodal Service Code - Intermodal service code will be checked against ownership of trailer or container.

3.2.3.1.4 Billed Weight - The billed weight and actual weight will be checked against the UMLER file to verify that the weight is less than or equal to the maximum lading possible for the car used.

3.2.3.1.5 Freight Revenue - The contractor will develop a table of revenue per ton-miles by STCC classes by distance from the best sources available. Reported freight revenue will checked against this table.

3.2.3.1.6 Reporting Railroad v. Terminating Railroad - The contractor will maintain a list of valid reporting railroads and terminating railroad pairs. The reporting railroad and terminating railroad pair will be checked against this list.

3.2.3.1.7 The delivered waybill sample record will be edited against the file description printed the in Carload Waybill Sample User Guide. For example, if field 28 is shown in the User Guide as having defined values of "0", "1", "2", and "3", then a blank, any letter, or any other number would be an error. The waybill sample as delivered is expected to be free of this type of error. Any errors in this area will be counted against the 1% maximum error rate.

3.2.3.1.8 Car Type must be valid. The STB Car Type must be valid.

The definition of the STB Car Type is as follows: “The STB car type is inferred from the AAR Equipment Type, as described in item 70, and corresponds to the line number on STB Form 710 for type of car.” (This definition is on page 58, field 90) The STB Car Type is used in URCS.

3.2.3.1.9 INVALID CARLOAD FIELD: The carload field must be numeric and greater than zero.

3.2.3.2.0 Car ownership must have a value Railroad owner; (P) Privately owned; or (T) Trailer Trains The definition of the Car Ownership Category is as follows: “Alpha/numeric code which identifies the owner of the car: (R) Railroad owned; (P) Privately Owned; (T) Trailer Train.” (This definition is on page 58, field 93) The Car Ownership Category is used in URCS. In both 2011 and 2012, the waybill sample has blank Car Ownership Category fields.

3.2.3.2.1: The contractor will demonstrate that the waybill sample aligns with aggregate, industry-wide data to ensure overall reasonability and that data errors related to seasonality have been removed.

3.2.3.2.2 INVALID WAYBILL DATE: The waybill date must fall before December 31, 2015. The waybill was not processed for the current waybill year if the date was out of bounds.

3.2.3.2.3 INVALID CARLOAD FIELD: The carload field must be numeric and greater than zero.

3.2.3.2.4 INVALID TOFC/COFC LOAD COUNT: If a TOFC/COFC move is indicated, the number of TOFC/COFC units (load count) must be numeric, and either (1) less than the sum of waybill carloads multiplied by three, or (2) identified as a valid stack train movement.

3.2.3.2.5 BILLED WEIGHT STCC: The billed weight ton equivalent, divided by the number of waybill carloads, cannot be less than or greater than the range specified in the table look-up (by two-digit STCC). The range represents positive values plus and minus 4 standard deviations from the mean. Make sure the value is not larger than 143 tons per car, which is the maximum weight on rail.

3.2.3.2.6 INVALID FREIGHT REVENUE: The freight revenue must be numeric. If the freight revenue amount is zero, the transit code must be either ‘1’ or ‘9’. The freight revenue amount, divided by the number of waybill carloads, cannot be less than 1 or greater than the table look-up value (by two-digit STCC). The range represents positive values plus and minus 4 standard deviations from the mean.

3.2.3.2.7 REVENUE AMOUNT IS ZERO: If the revenue amount is zero, the transit code must be ‘1’ or ‘9’.

3.2.3.2.8 REVENUE PER TONMILE: The revenue per ton mile is not in the range established for the 2-digit STCC. 8. Waybills which list high freight revenues are verified individually (e.g., trans-continental movements of hazardous materials); if the revenue is valid for the waybill, the revenue error flag is removed after the final edit procedure.

3.2.3.2.9 BILLED WEIGHT CAPACITY: Billed weight is greater than load limit. Waybills which list very high or low billed weights are individually verified (e.g., heavy load capacity cars, or intermodal shipments with weights below one ton); if the weight is valid for the waybill, the billed weight error flag is removed after the final edit procedure.

3.2.3.3.0 WAYBILL DATE STAMP: Date stamps must be provided on each waybill and must include the date the waybill is submitted, the originating date, terminating date, and time of arrival and departure from intermediate junctions.

3.3 Phase II

3.3.1 Miling and Modifying the Waybill. Two weeks after receiving the final quarterly submission, the Government will return the total Master Waybill File to the contractor to add fields 24, 113 through 123, and 145 through 156 (Appendix C) using PTNM. Modifications made to the waybill as part of this process include:

3.3.1.1 Factoring of cars, tons, and revenue by stratum. The contractor will evaluate expansion factors (field 88) , especially for traffic with greater than 1/3 sampling rate. It is very important for traffic assignment purposes for the Federal Government to have accurate representation of this traffic, which includes unit crude oil and ethanol trains.

3.3.1.2 Correction of incorrect FSACs, SPLCs, carriers and Rule 260 junction alphas.

3.3.1.3 Translation of SPLCs and Rule 260 junction alphas to the node numbers of the Princeton Transportation Network Model (PTNM), so that traffic may be assigned to the network model for analysis.

3.3.1.4 Compilation of individual and total route mileage for each waybill through the ALKFLOW Traffic Assignment Model by routing traffic on railroad networks between on-points and off-points using a routing formula designed to model actual operations.

3.3.1.5 Correction of invalid reported routes.

3.3.1.5.1 Missing Rule 260 junction alphas.

3.3.1.5.2 A missing overhead carrier between railroads with no common interchanges, e.g., a move originating on Texas Mexican and terminating on Birmingham Southern uses Kansas City Southern and Norfolk Southern as overhead carriers.

3.3.1.5.3 Redundant overhead carriers and interchanges, e.g., a move originating and terminating on Providence & Worcester does not use CSX Transportation as overhead carrier.

3.3.1.5.4 Incorrect junction, e.g., Coutts, AB is not a valid junction between Canadian Pacific and Elgin Joliet & Eastern.

3.3.1.5.5 Incorrect origin or termination FSAC.

3.3.1.5.6 Other data entry errors.

3.3.1.6 Calculation of short-line miles using the ALKFLOW Traffic Assignment Model by routing traffic on railroad networks between on-points and off-points using a minimum distance routing formula.

3.3.1.7 Division of waybill revenue between participating carriers based on a modified mileage prorate.

3.3.1.8 Translation of the Standard Transportation Commodity Classification (STCC) code containing hazardous materials codes (49 series) and bulk commodity codes (50 series) to the product class STCC code (excluding the 49 and 50 series codes). Both versions of the code are output.

3.3.1.9 Translation of SPLC codes to state, province or Mexican estado (state) alphas, Bureau of Economic Analysis (BEA) areas, freight territories, freight rate areas, Standard Metropolitan Statistical Areas (SMSA), and Federal Information Processing Standard (FIPS) codes.

3.3.1.10 Addition of state through flags, indicating the states through which a waybill route traveled.

3.3.1.11 Enhancement of intermodal and potential intermodal records.

3.3.1.12 Determination of service type codes (intermodal, bulk/coal, auto rack and general merchandise).

3.3.1.13 Disaggregation of CN and CPRS in the sample in to US and Canadian portions. For easy identification, the railroad alphas for the US portions are changed to CNUS and CPUS respectively. The reported routes are modified to include junctions between the US and Canadian portions.

The contractor then has 15 working days to complete this portion of the waybill and return it to the Government to cost.

3.4 Costing the Waybill. Once the Government has received a complete and corrected waybill file from the contractor, the Government will have 15 working days to add costs to the waybill. At the end of this period, the Government will return the costed waybill sample to the contractor to create the Public Use Waybill File.

3.5 The Public Use Waybill File. The Public Use Waybill File is created from the larger Master File. The information needed for the Public Use Waybill is identified in the 247 Byte Public Use Record Layout in Appendix C. The contractor has 15 working days to create this file and submit it to the Government. The Government has 10 working days to accept the Public Use Waybill File. Once the Government has officially accepted the File, the processing of the waybill for the previous year is complete.

Deliverables SEQ CHAPTER \h \r 1The deliverables for this contract are divided by specific CLINS 0001 and 0002 and all option CLINs.

4.1 Quarterly Deliverables. SEQ CHAPTER \h \r 1The contractor shall provide to the COTR, a quarterly waybill submission excluding the data in fields numbered 18, 24, 89, 97-119, 122-131, 134, 138-141, 145-152, 155-156, and 180-191 (Appendix C). The contractor will submit this data on the first day of the second month after the end of the quarter. (For example if the end of the reporting quarter is March 31, then the contractor submits the quarterly data to the Government on May 1.) Along with the waybill data, should be the attribute transaction file as described in 3.2.3 above. The contractor must submit a quarterly report containing the following (See Appendix B):

4.1.1 Summary of waybill processing by individual railroad This section documents the volume of waybills received for the month or quarter, the number of these waybill processed a list of waybills received and not processed as well as the reason for not processing them and the cumulative number waybills processed to-date.

4.1.2 Delinquent Railroads This section lists those railroads which are technically late with their initial or corrected submissions. The Government expects the contractor to work closely with their railroad points of contact to collect this information. The contractor is expected to identify the steps taken to correct the problem; including copies of all correspondence. The Government will intervene with those railroads not in compliance with waybill reporting requirements.

4.1.3 Problems Requiring STB Action This section permits the contractor to advise the STB of problems or potential problems in collecting the waybill sample.

4.1.4 Error Analysis and Corrective Action This section explains the contents of the attribute transaction file described in 3.2 above.

4.1.5 Process Improvement Update This section contains the status of any project that the contractor is undertaking to improve the process of the waybill sample.

4.2 Reserved

4.3 Annual Deliverables. The following reports, tables and files are annual deliverables associated with this CLIN.

4.3.1 SEQ CHAPTER \h \r 1The Final Report delivered with the last quarterly waybill submission must contain at a minimum the following: (See Appendix B as the example)

4.3.1.1 Summary of waybill processing - This section documents by railroad the volume of waybills received and each railroad’s submission method.

4.3.1.2 Delinquent Railroads - This section lists those railroads which are technically late with their initial waybill submissions or corrections. If the contractor has been unable to collect the data, it is the contractor's responsibility to notify the STB of the problem in time for the STB to take action to ensure that all required data is received before the Master Waybill File is produced.

4.3.1.3 Data Exceptions

4.3.1.4 Error Analysis and Corrective Action – This should include a summary of the waybill attribute file broken down by individual railroad.

4.3.1.5 Error Codes and Messages

4.3.1.6 Waybill Contact/Mailing List - This section contains an updated list of those railroads officials (by railroad) responsible for submitting the waybill sample. This list will also be provided to the STB on a CD-R. The Government expects the contractor to keep this list current by contacting each submitting railroad at least once per year to confirm the railroad’s point of contact.

4.3.1.7 Final Waybill Record Layout and Data Element Descriptions - This section details the final waybill record, describes the data elements, and defines the error flags. Each item in the Master Waybill File is numbered. All numbered items must match the item number used in the data element description.

4.3.2 SEQ CHAPTER \h \r 1Documentation and Industry Reference Files SEQ CHAPTER \h \r 1The contractor shall also provide to the Government all documentation necessary to use the files. The documentation is required in both hard copy and computer readable form. The required documentation includes but is not limited to the following:

4.3.2.1 Standard Transportation Commodity Code Directory

4.3.2.2 Directory of Hazardous Material Shipping Descriptions

4.3.2.3 Freight Station Accounting Code Directory

4.3.2.4 Official Railroad Station List

4.3.2.5 The Official Railway Equipment Register

4.3.2.6 Centralized Station Master (CSM)

4.3.2.7 A list of all railroads in the sample (originating, terminating, or bridge) with the reporting marks used by these carriers.

4.3.2.8 Railway Accounting Rules (Including ISS Rules)

4.3.2.9 User’s Guide – See Appendix C.

4.4 Annual Deliverables.

4.4.1 Miling and modifying the waybill sample The contractor supplies the remaining information to the waybill sample by adding fields 24, 113 through 123, and 145 through 156 (Appendix C) using Princeton Transportation Network Model (PTNM).

4.4.2 Costing the Waybill File The Government has 15 working days to cost the waybill file after receiving the miled and modified waybill sample.

4.4.3 The Public Use Waybill File. The contractor has 15 working days after receiving the costed waybill to create the Public Use Waybill File and submit it to the Government for acceptance.

4.4.4. OPTIONS TASK: The FRA and STB can exercise options tasks to conduct additional modeling, data collection and data analysis. Option tasks will not exceed 100 hours of additional work per year.

4.5 Delivery Schedule Contract base period and all options.

No later than 30 days after the end of the quarter.

May 1, August 1, November 1, February 1

4.1

4.2 Quarterly Report

May 1, August 1, November 1

February 1

March 1

April 1

As Soon As Available

5.0 Delivery Instructions All COTR copies of reports, documentation, and/or other deliverables required under the contract shall be delivered F.O.B. Destination, under transmittal letter to:

Surface Transportation Board

395 S Street, S.W.

Washington, D.C. 20423

Attn: Paul Aguiar, STB COTR

All FRA copies of reports, documentation and/or other deliverables required under the contract, not specifically identified for submission to the Contracting Officer, shall be delivered F.O.B. Destination, under transmittal letter to:

Federal Railroad Administration

Office of Policy and Program Development, RPD-20

1200 New Jersey Avenue, SE

Washington, DC 20590

Attn: Raquel Hunt, FRA COTR

All Contracting Officer copies of invoices, reports, documentation, and/or other deliverables required under the contract shall be delivered F.O.B. Destination, under transmittal letter to:

Keith Boyea

Federal Railroad Administration

Office of Acquisition & Grants Services, RAD-30

1200 New Jersey Avenue, SE

Washington, DC 20590

6.0 Project Review Meetings and Travel Requirements The contractor shall conduct in-depth briefings on the technical status of the waybill processing for Government personnel. These meetings shall be scheduled at the request of the STB, FRA or the contractor(s) and will be held at the STB. The STB anticipates four meetings each calendar year, but may call more (or less) with contractor(s) as the need arises. These briefings shall cover:

6.1 Any key events occurring since the last review meeting.

6.2 Any problem area and the contractor's proposal for resolving the problems including any previous actions by the contractor, and any actions that the contractor feels should be taken by the STB.

6.3 A review of all railroads that are delinquent and/or are failing to submit data under the required sampling procedures. The contractor shall outline the specific steps it has taken to collect this data, and provide recommendations for correcting reporting problems, including any action that should be taken by the STB.

6.4 Other items as may be required to assure the success of the waybill processing.

7.0 Project Review Meetings

The contractor shall conduct in-depth briefings on the technical status of the waybill processing for STB and FRA personnel. These meetings shall be scheduled at the request of the STB, FRA or the contractor. The STB anticipates four meetings each calendar year, but may call more (or less) if the need arises. These briefings shall cover:

1.

Any key events occurring since the last review meeting.

2.

Any problem area and the contractor's proposal for resolving the problems including any actions the contractor feels should be taken by the STB.

3.

A review of all railroads that are delinquent and/or are failing to submit data under the sampling procedures specified in Ex Parte No. 385, 49 C.F.R. 1244. The contractor shall provide recommendations for correcting any reporting problem, including any action that should be taken by the STB.

4.

Other items as may be required to assure the success of the waybill processing.

8.0 Period of Performance

(a) The effective periods of performance under this contract are as follows:

Contract Period

Effective Period

Base Period

01 JAN 2015 – 31 MAY 2016

Option Period I

01 JAN 2016 – 31 MAY 2017

Option Period

II

01 JAN 2017 – 31 MAY 2018

Option Period

II

01 JAN 2018 – 31 MAY 2019

9.0 Release of Waybill Data by Contractor The Commission’s waybill data release procedures (Ex Parts No. 385 (Sub-No. 2), 49 C.F.R.1244.8, govern the terms for release of confidential waybill data to Commission approved users. In accordance with these procedures the Contractor must have a copy, received from the Commission, of the confidentiality agreement the approved user executed with the Commission. Section C-1 gives a discussion of the various subsets of the Master Waybill File that the Contractor may be required to provide. The Contractor shall extract and provide from the Master Waybill File the confidential waybill data approved for release at a cost consistent with the fee structure set forth in this Section H.

The Contractor shall not produce any reports or make any special computer runs which require use of the confidential Waybill Master File, without prior ICC approval. The Contractor is responsible for taking all necessary security procedures to assure that the Waybill Master File and all files and reports produced from this file are not released without prior ICC written approval. The security procedures to be used by the Contractor will be evaluated as part of the selection criteria.

With respect to the non-confidential Public Use File, the Contractor may release this file to the public without prior ICC approval and any restrictions on its use. Also, the Contractor may produce and sell any report that can be extracted from the non-confidential PUF without prior ICC approval. The Contractor shall provide the non-confidential PUF or any data extracted from this file at cost consistent with the fee structure set forth in this Section H.

10.0 Copy of Algorithm and Table If a contractor uses the model provided by the government, the contractor shall provide the ICC and FRA with a copy of the proper miling algorithm used and the SPLC to node assignment table used within 30 days after the award date.

FRA will provide the contractor with corrections to network in cases when waybill records cannot be miled.

PAGE