Attachment 9_SAMPLE TO_R and D Amendment 0001.docx

SAMPLE TASK ORDER – RESEARCH & DEVELOPMENT

Railroad Policy and Development (RPD)

STATEMENT OF WORK

SAMPLE TASK ORDER – R&D

Contract XXXXXXXXXXXX:

Transportation Technology Center at Pueblo, Colorado

XXXXXXXXXXX, 2020

1 INTRODUCTION

This proposal describes Personnel and Material support activities necessary to support the FRA Office of Research, Development & Technology (RD&T) at the Transportation Technology Center (TTC) in Pueblo, CO. Under this task order (TO), the contractor will provide labor hours, equipment charges and associated materials purchases in support of the FRA RD&T Division.

2 OBJECTIVE

The objective of this TO is to provide necessary labor, equipment and associated materials to support FRA R&D at TTC. Provide management, supervision, personnel, equipment, and materials necessary to accomplish the work described in this proposal.

3 LOCATION

U.S. Department of Transportation Federal Railroad Administration Transportation Technology Center 55500 DOT Road Pueblo CO. 81001

4 PERIOD OF PERFORMANCE

The following period of performance is aligned for each part of the task order.

Part 1: 12-24 months Part 2: 12 Months Part 3: 12 Months Part 4: 24 Months

5 WORK BREAKDOWN

5.1 PART 1: FULL MOVING BLOCK

The intent of the project is to advance the development of an interoperable Full Moving Block (FMB) method of train control by analyzing critical issues and developing key technical documents that will be needed for system development.

5.1.1 Background

As part of the FRA-sponsored research on Higher Reliability/Capacity Train Control (HRCTC), a number of enhanced methods of operation, leveraging elements of current Positive Train Control (PTC) systems, have been identified and shown to provide benefits over conventional methods of train control. The stages of train control defined on the HRCTC program are:

· Overlay PTC (currently being deployed to comply with the Rail Safety Improvement Act of 2008 [RSIA’08]),

· Enhanced Overlay PTC (EO-PTC),

· Quasi-Moving Block PTC (QMB), and

· Full Moving Block PTC (FMB).

Each of the above train control modes builds upon its predecessor. Consequently, each successive enhanced mode incorporates the benefits of its predecessor and increases those benefits or provides additional benefits. A railroad may employ one of these train control modes in one area and a different mode in a different area. The FMB architecture and design can leverage significantly off of the QMB architecture and design.

In FMB (as well as in QMB), non-overlapping movement authorities, known as PTC Enforceable Authorities (PTCEA), are issued for every train operation. This offers safety improvements over current overlay PTC, including the ability to provide rear-end collision protection and collision protection within a joint authority. Additionally, FMB offers greater capacity and reliability than QMB and other train control methods. FMB employs the train control architecture necessary to approach the theoretical minimum headways and maximum capacity on railroad main lines. It achieves this by eliminating unnecessary constraints associated with fixed block train control systems.

FMB leverages off of existing Overlay PTC and planned QMB architecture and infrastructure, with some modifications. This includes the potential reuse of onboard PTC hardware (with modified software), interoperable train control messaging (ITCM), and 220 MHz radio communications. The back office segment will require modifications to include FMB Office functions. FMB also requires train integrity monitoring (e.g., vital rear-of-train location determination as may be used with QMB) and an alternative to conventional track circuits for detection of broken rails at closer train spacing, and unauthorized occupancies (e.g., roll-outs).

5.1.2 Objectives

The objectives of this projects are to develop Full Moving Block requirements for railroad operations.

5.1.2.1 Task 1 – Project Management

Provide Project Management and System Engineering Support Services. This includes application of resources (knowledge, skills, tools, techniques, and funding) to project activities to complete the objectives of the project on time and within budget. The primary sub-tasks are:

· Manage budgets, schedules, and subcontractors;

· Conduct regular status meetings with the Project Team and Advisory Group;

· Organize and lead preliminary and critical design review meetings with the Project Team and Advisory Group.

5.1.2.2 Task 2 – Assemble Advisory Group (AG) that will include, at a minimum:

· The Federal Railroad Administration;

· Representatives from Class I Railroads;

· Representatives from Short Line Railroads (e.g. American Short Line Railroad Association, etc.);

· Representatives from Commuter/Passenger agencies (e.g. American Public Transportation Agency, Amtrak, etc.).

5.1.2.3 Task 3 – Develop a Concept of Operations (ConOps) for FMB along with the following sub tasks:

5.1.2.3.1 Develop a communications feasibility analysis;

5.1.2.3.2 Develop an incremental safety analysis;

5.1.2.3.3 Define assumptions and considerations for methods to be used to detect broken rail, rollout (i.e. unauthorized occupancies) detection and train integrity monitoring in a full moving block scenario.

5.1.2.4 Task 4 – Develop Migration Considerations.

In conjunction with the advisory group develop all considerations and requirements for migrating a railroad from an existing method of operation to FMB.

5.1.2.5 Task 5 – Develop Incremental System Requirements Specifications based upon the concepts developed under QMB to include:

· System level requirements

· Segment level requirements

· Interface requirements

· Messaging requirements

TTCI shall document the following through a development of a FMB System Requirements documentation.

5.1.2.6 Task 6 – Develop Incremental Interface Control Documents. Develop a full set of incremental ICDs to support FMB, as well as develop interoperable FMB specific requirements.

5.1.2.7 Task 7 – Develop a Preliminary Safety Analysis to include:

· Preliminary Hazard Analysis

· Operating and Support Hazard Analysis

· System Hazard Analysis

5.2 PART 2: AUTOMATED TRAIN OPERATIONS (ATO) SEGMENT AND SUBSYSTEM REQUIREMENTS DEVELOPMENT

5.2.1 INTRODUCTION

The project includes multiple tasks to define, develop, and document segment-level requirements for onboard safety systems and back office systems that support the interoperable functions of the Automated Train Operations (ATO) concept. Need knowledge of communication and train control.

5.2.2 OBJECTIVES

The objectives of this project are to:

5.2.2.1 Develop systems engineering documentation necessary to define interoperable requirements for new back office subsystems and Back Office Decision Support required for ATO

5.2.2.2 Develop systems engineering documentation necessary to define interoperable requirements for onboard ATO state indicators

5.2.2.3 Develop systems engineering documentation necessary to define interoperable requirements for ATO train arming and disarming mechanisms

5.2.3 REQUIREMENTS AND TASK OVERVIEW

5.2.3.1 Project Management

Provide Project Management and System Engineering Support Services. This includes application of resources (knowledge, skills, tools, techniques, and funding) to project activities to complete the objectives of the project on time and within budget.

5.2.3.1.1 Develop draft requirements for ATO Back Office Server (BOS)

5.2.3.1.2 Develop draft requirements for ATO Back Office Decision Support

5.2.3.1.3 Develop draft requirements for ATO internal and external state indicators

5.2.3.1.4 Develop draft requirements for ATO arming switches

5.3 Part 3: BROKEN RAIL AND ROLLOUT PROTECTION FOR QUASI-MOVING BLOCK RESEARCH AND DEVELOPMENT PROJECT This document describes minimum work for a project to continue R&D efforts on a method for broken rail and rollout detection that may enable network capacity benefits of Quasi-Moving Block (QMB) operations. A concept was previously developed to support future methods of train control, such as QMB or variants thereof, that is intended to be a simple, reliable, and cost-effective modification to existing track circuit technology, but provides substantive benefits.

The Next Generation Track Circuit (NGTC) Concept of Operations (CONOPS) described a broken rail detection method that allows a train, in a close following move in QMB territory, to enter an occupied block at higher speed without increased risk of encountering a broken rail, compared to operations in conventional CTC/overlay PTC territory today.

5.3.1 BACKGROUND

In 2018 and 2017, TTCI performed a study funded by the FRA to determine if an alternative track circuit method may exist that would alleviate some of the restrictions of the current track circuits that have been in existence since the 1870s. This project is a follow-on to the Next Generation Track Circuits project, with intentions to use the technology in QMB operations.

5.3.2 OBJECTIVE

The specific objectives of this project are to:

5.3.3 Determine the extent to which electrical current can be used to reliably detect a broken rail (i.e., electrical open) with a shunting axle in the same track circuit under nominal circumstances

5.3.4 Identify technical challenges associated with fail-safe implementation of the CONOPS design

5.3.5 Develop additional analyses and requirements documentation to advance the NGTC concept to support a future product development and evaluation phase

5.3.6 REQUIREMENTS AND TASK OVERVIEW

The work is divided into nine (9) major tasks described in detail below:

5.3.6.1 Task 1 – Project Management

5.3.6.1.1 Provide Project Management and System Engineering Support Services. This includes application of resources (knowledge, skills, tools, techniques, and funding) to project activities to complete the objectives of the project on time and within budget. Organizing an industry stakeholder AG to project oversite and review. The AG shall have representatives from:

· Federal Railroad Administration

· Class I freight railroads

· Commuter/passenger railroads (if possible)

5.3.6.2 Task 2 – Develop Use Cases, Test Cases and Test Plans

5.3.6.2.1 Coordinate with the AG to develop the Use Cases necessary for the increases in Track Circuit capabilities of this project

5.3.6.2.2 Coordinate with the AG to develop the simulation test cases to be used to test the concepts developed

5.3.6.2.3 Coordinate with the AG to develop the test plan.

5.3.6.3 Task 3 – Configuration of the TTC Testbed for testing

5.3.6.3.1 Configure the TTC testbed to enable testing of the test plan.

5.3.6.4 Task 4 – Perform Testing at TTC

5.3.6.4.1 Perform tests according to the AG approved test plan. This may include both static and dynamic tests as approved by the AG.

5.3.6.5 Task 5 – Analyze Results of Testing

5.3.6.5.1 Perform an evaluation of the test results.

5.3.6.5.2 Provide the AG with the results of the performed tests for review and approval.

5.3.6.6 Task 6 – Capacity Analysis

5.3.6.6.1 Perform a capacity benefit analysis to determine if the expanded track circuit can potentially increase capacity without reduction to the overall safety.

5.3.6.6.2 Provide the AG with written results of the Capacity Analysis for review and approval.

5.3.6.7 Task 7 – Hazard Analysis

5.3.6.7.1 Perform a Hazard Analysis to determine if the expanded track circuit will provide sufficient protection to railroad operations.

5.3.6.7.2 Provide the AG with written results of the Hazard Analysis for review and approval.

5.3.6.8 Task 8 – Requirements Specification

5.3.6.8.1 Coordinate with the AG to develop a requirements specification sufficient for development of a Track Circuit to assist in QMB operations.

5.3.6.8.2 Garner approval of the Requirements from the AG.

5.3.6.9 Task 9 – Final Report

5.3.6.10 A final summary report describing the research methods and findings shall be submitted to the FRA prior to the end of contract term. The report will detail the results of the testing and shall identify any technical challenges identified during the testing. Deliver a four-page “Research Results” report highlighting the project work and findings conforming to standard FRA format.

5.4 PART 4: IMPROVED COMPOSITE TIE PERFORMANCE

In recent years, the railroad industry has expressed an increased interest in composite railroad ties. Various trends have served as drivers for this interest including higher cost and lower availability of hardwood lumber, potential for gains in the lifecycle in areas of high rot and high decay (particularly the southeastern U.S., tunnels, or at-grade crossings), and concerns over potential creosote regulations limiting wood tie usage or disposal options in the future. Composite railroad ties may offer a feasible alternative to creosote treated wood ties, which represent approximately 95 percent of the ties purchased by Class I railroads in the U.S. Railroad adoption of composite tie technology has increased recently, however, composite ties currently make up less than one percent of tie market share.

Engineered-polymer composite (EPC) railroad ties, which are composed primarily of post-consumer recycled plastic, have been used sparingly in North American revenue service for about two decades. Two EPC tie designs tested at the Federal Railroad Administration’s (FRA) Transportation Technology Center (TTC), namely the Facility for Accelerated Service Testing (FAST), have accumulated 1.7 and 2.1 billion gross tons of traffic, respectively, before being removed from service recently. However, the railroad industry, through numerous trials and tests in revenue service track, has experienced quite varied quality and performance from EPC ties. Concerns regarding long-term performance and safety include, among others, tie-center cracking and warping (i.e., center bending), tie-plate failures, spike-hole cracks, and increases in gage due to thermal expansion of the tie itself. These topics continue to drive the research needs and are focused on implementing design recommendations in the AREMA Manual for Railway Engineering to improve performance and safety of EPC ties in revenue service.

A recent collaborative research initiative between FRA and the Association of American Railroads (AAR) and participation in AREMA Committee 30, Subcommittee 6 (Composite Ties), under Task Order 48 has focused on the following:

· Evaluation of EPC ties in track at FAST, the Western Mega Site, and a test zone in Chester, IL;

· Augmented and accelerated laboratory testing for spike insertion/extraction and tie bending fatigue;

· Preliminary development of a center-bending fatigue testing method for EPC ties;

· Finite element and NUCARS modeling of EPC tie-behavior/loading environment;

· Updates to AREMA Manual for Railway Engineering regarding EPC modulus of elasticity (MOE) /modulus of rupture (MOR) recommendations, overhaul of the table for design considerations, lateral resistance recommendations, and fire/heat testing considerations.

This proposed new project phase addresses continued research necessary to better understand the loading environment, the failure modes, and the improvements needed in design and testing recommendations for EPC ties, namely understanding thermal effects on EPC tie, the implications on track safety and track class, and implementation of improved recommendations related to this topic.

5.4.1 OBJECTIVE

The overall goal of this multi-year collaborative project is to augment testing and modeling currently being conducted to develop enhanced design, testing, and performance guidelines and criteria for EPC ties to improve the safety and reliability of composite ties. Specifically, the area of thermal expansion will be addressed.

Improved understanding of the combined effects of temperature variation, thermal expansion, and ballast degradation on EPC ties with regard to maintaining proper gage.

5.4.2 REQUIREMENTS AND TASK OVERVIEW

5.4.2.1 Phase 1: Management

TTCI will manage all aspects of the task to realize the task goals and objectives in a cost-effective and timely manner. Under this subtask, the TTCI will provide all regular monthly reporting requirements as stipulated by the CCC contract DTFR53-11-D-00008, Section F.5; provide recommendations to all aspects of the research approach; and develop meeting materials, presentations, specifications, and schedules.

The Contractor will also prepare and deliver a Task Management Plan (TMP) to manage the execution of the task. The TMP will address the following:

· Clear definition of scope for each of the subtasks presented;

· Work Breakdown Structure (WBS) and assignment of tasks;

· Project schedule;

· Resource Management Plan, including details on required stakeholders, industry partners, and any subcontractors that may be required;

· Communications plan, including regularly scheduled project communication with FRA and other stakeholders (e.g., Union Pacific Railroad, or “UP”);

· Technology Transfer Plan that will clearly detail how the results of the research effort will be made available for use by FRA.

5.4.2.2 Phase 2: Thermal Effects on EPC Tie Performance – Maintenance of Track Gage

Preliminary in-track testing has previously been conducted that suggests that EPC ties can thermally expand and generate measurable gage widening, especially when center-binding support conditions are present. This subtask will seek to better understand this mechanism, how it relates to standardized ASTM coefficient of thermal expansion (CTE) laboratory testing, and what improved recommendations can be generated for EPC ties as it relates to:

· Gaging of ties outside of intended installation environment/temperature;

· Environment in which EPC ties are to be installed;

· Track safety and applicable track classes; and

· An appropriate CTE value based on track class/acceptable gage widening Testing is to be conducted by installing a comprehensive system of thermocouples and remote track gage monitoring instrumentation to track the gage measurements throughout different environmental and thermal conditions. Additionally, a thermal expansion model will be built that simulates the properties of EPC ties and induced thermal loads to model expected behavior. The results of these tests and modeling will be compared with CTE values for the EPC tie materials to generate improved recommendations for EPC ties. Current AREMA criteria for the CTE of EPC ties appears to be based on the CTE value for high-density polyethylene (HDPE) and does not appear to have been studied in relation to track gage or track safety.

5.4.2.3 Phase 3: Thermal Effects on EPC Tie Performance – Stress/Load Environment

The temperature in EPC ties is not a uniformly distributed field. Preliminary tests show that the top surface can have a much higher temperature under direct sunlight than the bottom, sides, and likely within an EPC tie, which all remain relatively insulated (both by the polymer itself as well as the ballast surrounding the tie). The induced thermal load, particularly when combined with dynamic loading from passing trains and center-binding support conditions underneath the tie, may cause higher-stress amplitudes, particularly in the center of EPC ties and near the spike holes where stress concentrations are believed to contribute to failures. This may affect the center cracking and spike-hole cracking failure modes commonly observed in EPC ties, ultimately affecting the in-track performance and safety of EPC ties. Previous research has looked at short-term bending strain measurements (under a single passing train, for example). As part of this project, TTCI will investigate the strain/stress change due to temperature change over the long term and how this load environment is augmented under dynamic train traffic. The testing and modeling results from this task will relate to the work described in phase 2. The objective of this task is to improve understanding of the combined effects of temperature variation, thermal expansion, and ballast degradation on EPC ties with regard to changes to the load environment.

6 DELIVERABLES

The deliverables for this research effort will be Test Plans from load environment testing and demonstration test. Also, submission of Research Result and Final Report summarizing the test results and findings, and outlining the methods developed. The results will also be presented as a paper at an appropriate industry conference or similar venue.

The contractor shall submit final reports to the FRA Program Manager for review and comment at least thirty (30) calendar days before the end of the period of performance. The contractor shall incorporate comments and deliver a new version of the submitted document within five (5) business days of receiving comments from FRA or by the agreed upon next delivery date. The final reports shall be presented to the Program Manager for verification and acceptance before publication. The contractor shall exercise due diligence in quality control of deliverables to minimize the number of review cycles and comments.

Final reports shall be prepared in accordance with ANSI/NISO Z39.18-1995 (Scientific and Technical Reports—Elements, Organization, and Design), except for the cover which shall be in accordance with the current FRA format. Final reports shall be prepared in camera-ready format to FRA for approval and shall also be supplied in PDF format for inclusion on the R&D report web page.

To ensure adequate project planning and facilitate appropriate project monitoring the following reports are required:

6.1 Project Plan/Schedule

Within fifteen (15) days of the task award, the contractor shall provide a project plan to the program manager for approval. This plan should contain an overview of the purpose and objectives of the project as well as all contract milestones and deliverables for the full duration of this effort. The approved plan establishes the cost and schedule base used to manage project execution for the scope defined within this Statement of Work. The cost and schedule base of this plan shall be the basis for the planned figures in the Monthly Progress Report, detailed below in the Monthly Progress Report Deliverable. The plan at a minimum shall detail the high-level tasks required to complete the milestones and deliverables described in the SOW, industry marketing plans and associated time and cost to complete these tasks. Once approved, the project plan will be considered the basis for measuring performance. It is unchangeable without approval from the FRA COR.

6.2 Monthly Progress Reports

Within fifteen (15) days following the end of each month, the contractor shall submit a monthly progress report via email to the COR. Each progress report will include, for each FRA-sponsored research project, concise statements describing:

· A financial status to include accumulated cost, both planned and actual, and breakdown of cost by major categories.

· Work performed during the previous month and a summary of work to be performed in the next month, along with a comparison of planned vs. actual work performed.

· Identification of problems and recommended solutions.

Monthly progress reports shall be submitted prior to or along with invoice submissions. The report shall describe the following: current status; significant accomplishments; planned vs. actual completion of milestones and deliverables; planned vs. actual cost status; technical/cost/schedule problems and recommended remedial activities; work planned for the next period; meetings and significant events planned/held; and relevant pictures of project progress. This report shall include details on all tasks awarded under this contract.

6.3 Quarterly Program Briefings

Once per quarter, the contractor shall present a program briefing to the COR and other FRA personnel as prioritized by the COR. This briefing should address the technical progress of the project including preliminary results and status as well as the financial status of the project including funds spent vs. technical progress and potential cost differences. These program reviews may be held in person or via conference call/web meeting.

6.4 Program Information Slides

Periodically throughout the fiscal year, at the discretion of the COR, the contractor shall provide program summary slides or information to the FRA for periodic FRA program reviews. The requests will likely be made in January, March, April and September but may be made at other times in the year. The format of the slides may vary by request and may be provided by the FRA. The format may include program status in the “4-block” Quad (1 slide with 4 blocks of information: project description, current status, Railroad Impact, Contact information) or similar format, written summaries, updated pictures or other similar updates.

6.5 PART 1 DELIVERABLES

6.5.1 Prepare Final Reports

Produce a 508-compliant final summary report describing the research methods and findings shall be submitted to the FRA prior to the end of contract term. A second 508-compliant four-page “Research Results” report highlighting the project work and findings conforming to standard FRA format.

6.5.2 Task 1 – Project Management

· Prepare and deliver Monthly Progress Reports in standard one-page FRA format

· Preliminary design review

· Critical design review

6.5.3 Task 2 – Assemble Advisory Group

· Meeting Minutes to be published to AG

6.5.4 Task 3 - Develop a Concept of Operations (ConOps) for FMB

· Concept of Operations Document

6.5.5 Task 4 - Develop Migration Considerations

· Technical memo containing all the considerations needed for migrating a Train Control System to FMB

6.5.6 Task 5 - Develop Incremental System Requirements Specifications

· Technical memo detailing the incremental system requirements at the system, segment, interface and messaging levels.

6.5.7 Task 6 – Develop Interface Control Documents

· Technical memo detailing the required ICD documents.

6.5.8 Task 7 – Develop a Preliminary Safety Analysis

· Technical Memo detailing the hazard, operating and support, and system hazard analysis.

6.5.9 Task 8 – Final Reports

· A Final Summary Report describing the research methods and findings, to include the knowledge transfer plan, shall be submitted to the FRA prior to the end of contract term.

· A four-page “Research Results” report highlighting the project work and findings conforming to standard FRA format.

6.6 PART II DELIVERABLES

6.6.1 A final summary report describing the research methods and findings shall be submitted to the FRA prior to the end of the contract term. The report will detail the results of the research and shall identify any technical challenges identified. The Technical Report to be submitted to the FRA shall pass Section 508 compliance at 100%, which includes images and tables holding alternative text. The final report will include copies of draft requirements.

6.6.2 Research Results Report. A four page report highlighting the project work and findings conforming to standard FRA format.

6.7 PART III DELIVERABLES

6.7.1 Develop Use Cases, Test Cases and Test Plan for Part III, Task 2.

6.7.1.1 Status briefed to the AG and recorded in AG meeting minutes

6.7.1.2 AG approved copies provided to COR for:

· Use Cases

· Test Cases

· Test Plan

6.7.2 Analyze Results of Testing

6.7.3 Results briefed to the AG and recorded in AG meeting minutes Copy of results delivered to the COR

6.7.4 Capacity Analysis

6.7.4.1 Copy of AG approved results delivered to the COR

6.7.5 Hazard Analysis

6.7.5.1 Copy of AG approved results delivered to the COR

6.7.6 Requirements Specification

6.7.6.1 Copy of AG approved specifications delivered to the COR

6.7.7 Final Report

6.7.7.1 Final Deliverable - A Final Summary Report describing the research methodology, analysis and results shall be submitted to the FRA prior to the end of contract term and a four-page “Research Results” report highlighting the project work and findings conforming to standard FRA format.

6.7.7.2 Final report shall contain the technical challenges identified during the testing.

6.8 PART 4 DELIVERABLES

6.8.1 Phase 1: Deliverables expected

6.8.1.1 TMP submitted for approval no more than 30 days after contract award.

6.8.1.2 Work plan describing the modeling matrix to be simulated and the proposed augmentation of AAR-funded laboratory and/or in-track testing as they relate to the investigation of the thermal effects on EPC tie performance, to be submitted to the FRA COR/TM for approval within 90 days of award;

6.8.1.3 Biweekly highlights, monthly reports, and quarterly project review briefings;

6.8.1.4 Meeting materials, presentations, specifications, and schedules as needed.

6.8.2 Phase 2: Deliverables Expected

6.8.2.1 In-track testing of instrumented EPC ties at FAST and/or revenue service;

6.8.2.2 Development of a validated thermal expansion model for EPC ties;

6.8.2.3 Interim report on the in-track testing and modeling results at the end of Year I;

6.8.2.4 Support the development of improved performance guidelines and criteria for EPC ties related to the thermal effects on gage widening.

6.8.3 Implementation of Results into Final Report

6.8.3.1 Evaluation of the stress/load environment of instrumented EPC ties in track at FAST and/or revenue service;

6.8.3.2 Support the development of improved performance guidelines and criteria for EPC ties related to the thermal effects on the stress/load environment.

6.8.3.2.1 The results of this research will continue to be shared and discussed within AREMA Committee 30 (Subcommittee 6). Participation and leadership on Subcommittee 6 will continue to be an objective of this research project. The project will produce a final FRA Technical Report, and a comprehensive journal/conference paper and presentation on the results of this work. The Technical Report to be submitted to the FRA COR/TM must pass Section 508 compliance at 100%, which includes images and tables holding alternative text.

6.8.3.2.2 A final technical report to be submitted to the FRA COR/TM for approval no less than 30 days prior to the end of the period of performance;

6.8.3.2.3 Preparation of professional papers and presentation of research results and findings at suitable conferences within the United States. These will be coordinated between FRA and AAR, as this is a jointly funded research project.

7 WRITTEN PROPOSAL CONTENTS

Page limitations for each volume if any, are specified in the table below; title and table of contents pages do not count towards page limit. Proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation. Volume contents and limits are described in the table:

Each volume shall contain a table of contents with sufficient detail to enable easy location of important elements.