98-002172BID Florida Overland Express, L.P. vs. Department Of Transportation
 Status: Closed
Recommended Order on Thursday, August 6, 1998.


View Dockets  
Summary: FOX protested Request For Proposal to co-locate another rail system in the Beeline Expressway right-of-way, saying it would interfere with FOX`s high-speed rail project. Recommended Order: premature to invalidate Request for Proposal.

1STATE OF FLORIDA

4DIVISION OF ADMINISTRATIVE HEARINGS

8FLORIDA OVERLAND EXPRESS, L.P., )

13)

14Petitioner, )

16)

17vs. ) Case No. 98-2172BID

22) DOT Case No. 98-80

27DEPARTMENT OF TRANSPORTATION, )

31)

32Respondent, )

34)

35and )

37)

38BEE LINE MONORAIL SYSTEM, INC., )

44)

45Intervenor. )

47___________________________________)

48RECOMMENDED ORDER

50On June 16 and July 2, 1998, a formal administrative hearing

61was held in this case in Tallahassee, Florida, before J. Lawrence

72Johnston, Administrative Law Judge, Division of Administrative

79Hearings.

80APPEARANCES

81For Petitioner: Martha Harrell Chumbler, Esquire

87Carlton, Fields, Ward, Emmanuel,

91Smith & Cutler, P.A.

95Post Office Drawer 190

99Tallahassee, Florida 32302

102Betty J. Steffens, Esquire

106210 South Monroe Street

110Tallahassee, Florida 32301

113For Respondent: John C. Bottcher

118Assistant General Counsel

121Department of Transportation

124605 Suwannee Street

127Tallahassee, Florida 32399-0450

130For Intervenor: Peter Antonacci, Esquire

135Rumberger, Kirk & Caldwell, P.A.

140Post Office Box 10507

144Tallahassee, Florida 32392-2507

147STATEMENT OF THE ISSUES

151The issues in this case are whether the specifications

160included in the Request for Proposals for Lease of Right-of-Way,

170S.R. 528 (Bee Line Expressway)("the RFP") are contrary to

181governing statutes and rules, clearly erroneous, contrary to

189competition, arbitrary, or capricious.

193PRELIMINARY STATEMENT

195The Respondent, the Department of Transportation (the

202Department), issued the RFP on April 17, 1998. The Petitioner,

212Florida Overland eXpress, L.P. ("FOX") filed a written protest of

224the RFP's specifications on May 4, 1998.

231On May 13, 1998, the Bee Line Monorail System, Inc.

241("BLMS"), moved to intervene in support of the Department and the

254RFP's specifications and filed a Motion to Dismiss Formal Written

264Protests and Petitions for Formal Administrative Hearing in Case

273Nos. 98-2171BID and 98-2172BID. A Voluntary Dismissal was filed

282in the former case on May 19, 1998.

290On May 20, 1998, BLMS was allowed to intervene, and final

301hearing was scheduled for June 11, 1998.

308A hearing was held on BLMS' Motion to Dismiss on May 26,

3201998. Later that day, FOX filed an unopposed Motion for Leave to

332Amend and Proposed Amended Written Protest and Petition for

341Formal Administrative Hearing. Anticipating leave to amend, BLMS

349filed a Motion to Dismiss the Amended Written Protest and

359Petition for Formal Administrative Hearing on May 27, 1998.

368Later on that day, FOX filed a Response to Motion to Dismiss.

380The Motion to Dismiss the Amended Written Protest and

389Petition for Formal Administrative Hearing asserted that FOX had

398no standing to protest the specifications of the RFP because FOX

409is not a prospective bidder.

414On May 29, 1998, an Order Granting Leave to Amend and

425Denying Motion to Dismiss was entered grant; however, FOX's

434protest was limited to its interest in refining the RFP's

444specifications and was not allowed to extend to efforts to enjoin

455or cancel the RFP.

459On June 3, 1998, BLMS' agreed Motion to Amend Prehearing

469Order was granted, and final hearing was rescheduled for

478June 16-17 and July 2, 1998, to accommodate witnesses.

487The parties' Joint Prehearing Stipulation was filed on

495June 15, 1998. On June 16, 1998, FOX called two witnesses and

507had Petitioner's Exhibits 1 through 3 admitted in evidence.

516Joint Exhibits 1 through 6 were then received in evidence. The

527Department called one witness and had Department Exhibits 1 and 2

538admitted in evidence. BLMS called one witness and had BLMS

548Exhibits 1 and 2 admitted in evidence. On July 2, 1998, FOX

560called one additional witness, and the parties rested their

569cases.

570The parties ordered the preparation of a transcript of the

580final hearing and were given ten days from the filing of the

592transcript in which to file proposed recommended orders. The

601transcript was filed on July 15, 1998.

608FINDINGS OF FACT

611The Bee Line Expressway

6151. The Bee Line Expressway, which carries the number

624designation of State Road 528, extends from its western terminus

634at Interstate 4 in Orange County, easterly across the St. Johns

645River into Brevard County; it then extends slightly southerly

654across Interstate 95, the Banana River, Indian River, and Merritt

664Island; it ends at its eastern terminus at Port Canaveral in

675Brevard County.

6772. The portion of the Bee Line Expressway from Interstate 4

688to approximately the Florida Turnpike is owned by the Respondent,

698the Florida Department of Transportation ("the Department" or

"707DOT"). The portion from approximately the Turnpike to the

717vicinity of State Road 520, is owned by the Orlando-Orange County

728Expressway Authority (the "Expressway Authority") and is subject

737to a lease/purchase agreement between DOT and the Expressway

746Authority. The portion from the vicinity of State Road 520 to

757the center of the Intracoastal Waterway is owned by DOT. The

768portion from the center of the Intracoastal Waterway to Port

778Canaveral is owned by the Canaveral Port Authority (the "Port

788Authority.")

7903. Since the late 1980s there has been consideration of a

801fixed guideway transportation system linking Orlando and the

809Space Coast along the Bee Line Expressway. There were at least

820two proposals prior to June 1997 to co-locate transportation

829facilities along the Bee Line right-of-way. Such a system would

839be in accordance with and advance Department policies and

848responsibilities to develop new transportation systems to keep

856pace with Florida's growth.

860Bee Line Rail Unsolicited Proposal

8654. In June 1997, the Department received an unsolicited

874proposal titled "Proposal of Bee Line Rail System, Inc., for the

885Development of a Monorail System along the Bee Line Expressway."

895Since that time, the name of Bee Line Rail System, Inc. has been

908changed to Bee Line Monorail System, Inc. ("BLMS"). BLMS

919proposed the lease of certain Department properties along the Bee

929Line Expressway (S.R. 528) for the construction and operation of

939a rail system connecting a terminal at Cape Canaveral on the

950eastern coast of Florida, a terminal at the Orlando International

960Airport, and a terminal to be located near International Drive

970adjacent to Interstate 4.

9745. The BLMS unsolicited proposal became the impetus for the

984Department's Request for Proposals ("RFP"), which is the subject

995of this proceeding. Knowing that a rail line connecting the

1005Orlando area with the Space Coast had merit and would further

1016Department policies and responsibilities, the Department formed a

1024team of experts to write the RFP including the evaluation

1034criteria to be used in reviewing proposals submitted in response

1044to the RFP. The team worked together to develop the evaluation

1055criteria and to formulate the RFP in accordance with the

1065governing statute and rules. In the process of formulating the

1075RFP, the Department had discussions with the Expressway

1083Authority, the Canaveral Port Authority, and Florida Overland

1091eXpress (FOX), the Petitioner in this case. Each of these

1101entities' concerns were considered in the formulation of the RFP.

1111Specifically, DOT held several discussions with FOX and made

1120modifications to the RFP as a result. The RFP is substantially

1131different from the BLMS unsolicited proposal.

1137The Bee Line Expressway RFP

11426. On April 17, 1998, DOT issued the RFP pursuant to

1153Section 337.251, Florida Statutes (1997). It consists of the

1162Request for Proposal Cover Page, the Evaluation Criteria for

1171Lease of S.R. 528 (Bee Line Expressway) Right of Way (the

"1182Evaluation Criteria"), and the Bee Line Lease Agreement. Each

1192part of the RFP contains specifications that describe the

1201information a proposer must provide in order to be responsive, as

1212well as the criteria by which the submitted information will be

1223evaluated. Responses to the RFP are due October 19, 1998.

12337. The RFP solicited proposals for lease of the right-of-

1243way within the Bee Line Expressway (State Road 528) for the

1254purpose of establishing a transportation system (excluding

1261pipelines) connecting terminals and stations in Orange and

1269Brevard Counties, with an option to also lease right-of-way owned

1279by DOT along portions of State Road 407. Among other things,

1290proposals responsive to the RFP would have to clearly identify

1300the route for the proposed transportation system on aerial

1309photographs. (Evaluation Criteria, Part III, page 7) Proposals

1317would have to specify the services to be provided, whether they

1328would be for passengers, for freight, or for both, and the

1339locations of stations would have to be identified. (Evaluation

1348Criteria, Part V, page 9.) Proposers would have the option to

1359describe the specific technology to be deployed or to identify

1369the performance specifications to be achieved for a technology to

1379be specified at a later time. (Evaluation Criteria, Part VI,

1389pages 10-11.) Safety of proposed systems would have to be fully

1400explained including the identification of applicable federal and

1408state safety regulations. (Evaluation Criteria, Part VII, page

141611; Bee Line Lease Agreement, Paragraph 5.) Proposed systems

1425would have to be in compliance with all applicable environmental

1435and land use requirements. (Evaluation Criteria, Part IX, page

144413 and Part XII, page 15; Bee Line Lease Agreement, Paragraph 2.)

1456Constructability and maintenance of the proposed facilities would

1464have to be described. (Evaluation Criteria, Part X, page 13 and

1475Part XI, page 14.)

14798. The RFP requires that proposals include the information

1488designated in the Department's Florida Administrative Code Rule

149614-109.0011(4)(c). Among other things, the RFP requires that

1504proposals include:

1506The proposed design for the use of the space,

1515including facilities to be constructed, as

1521well as maps, plans and/or sketches as are

1529necessary to set out pertinent features in

1536relation to the transportation facility are

1542required by the RFP. (Evaluation Criteria,

1548Part III, page 7.)

1552A three -dimensional drawing and legal

1558description of the space to be leased is

1566required by the RFP. (Evaluation Criteria,

1572Part III, page 7.)

1576An explanation of all planned uses of the

1584property to be leased as well as all

1592activities to be conducted on the property is

1600required by the RFP. (Evaluation Criteria,

1606III, page 7 and V, page 9.)

1613Clarification Of The RFP

16179. The RFP provides two methods of obtaining a

1626clarification about its requirements. A potential proposer is

1634required to attend a "Mandatory Pre-proposal Conference." (RFP

1642Cover page, 2.) (This conference had been scheduled for May 5,

16531998, but was canceled due to the filing of the protests.) At

1665this meeting the attendees would be given the opportunity to ask

1676questions, and the Department would answer the questions, either

1685orally at the meeting, or in writing. In addition, any person

1696can submit a written request for clarification by a specified

1706date, which was to be July 6, 1998; within 21 days, the

1718Department would provide a written response. The request for

1727clarification and the Department's response would be provided to

1736all persons who attended the pre-proposal conference. (RFP Cover

1745page.)

1746Florida High Speed Rail Project

175110. FOX's witnesses did not testify that the specifications

1760in the RFP were invalid. Indeed, David S. Gedney, chief project

1771executive for the FOX project, testified that FOX was not opposed

1782to the RFP, just the timing of its issuance. FOX focused on the

1795timing of the RFP and the way in which it might complicate FOX's

1808planning efforts in establishing and locating the Florida High

1817Speed Rail Project.

182011. On February 28, 1995, the Department issued the High

1830Speed Rail Transportation System Request for Proposals that

1838solicited applications for a franchise for a high speed rail

1848transportation system to provide service to four designated

1856service areas--Tampa Bay (Hillsborough and Pinellas Counties),

1863Lakeland (Polk County), the Orlando area (Seminole, Orange, and

1872Osceola Counties), and Southeast Florida (Dade, Broward, and Palm

1881Beach Counties).

188312. In April 1996, the Department awarded FOX the franchise

1893for a high-speed rail system to connect the four service areas

1904identified in the High Speed Rail Transportation System Request

1913for Proposals. Brevard County is not in one of the service areas

1925identified.

192613. The award of the franchise was conditioned upon FOX and

1937the Department entering into certain post-franchise agreements

1944that would establish a solid foundation for the development of

1954the high-speed rail project. These agreements included a Finance

1963Post-Franchise Agreement (FPFA) to establish successful financing

1970for the endeavor and the Pre-Certification Post-Franchise

1977Agreement (PCPFA) to ensure the ultimate development and

1985certification of the project. The Department's Final Order

1993Awarding Franchise To Overland eXpress, L.P. - Franchise and

2002Terms and Conditions and the post-franchise agreements

2009collectively are referenced as the "Franchise."

201514. In accordance with Section 341.3338, Florida Statutes

2023(1997), and the Final Order that awarded the Franchise, FOX has

2034the exclusive right to establish, and upon issuance of

2043certification, to locate, construct, operate, and maintain a high

2052speed rail transportation system that serves the geographical

2060areas identified. These exclusive rights only apply to high

2069speed rail transportation systems.

207315. The Franchise does not grant to FOX an exclusive right

2084to provide high speed rail service to Brevard County, since that

2095county is not listed as a service area in the Franchise.

210616. In addition to the exclusive rights granted by the

2116Final Order, the Department agreed to seek legislatively

2124additional provisions to secure the exclusivity of the FOX

2133Franchise and to protect the state's financial investment in the

2143project. These are contained in the Finance Post-Franchise

2151Agreement (FPFA). Specifically, the FPFA, provides, starting on

2159page 3:

2161§2.2 Exclusivity. Pursuant to § 341.3338,

2167Florida Statutes, and Article III, Section A

2174of the Franchise Document, FOX has the

2181exclusive right to plan, establish,

2186construct, operate and maintain the System

2192serving the service areas identified in the

2199Franchise Document. Subject to the enactment

2205of any necessary State legislation, as set

2212forth in Section 12.21 , the Department agrees

2219as set forth in Sections 2.2(a) through (e)

2227below:

2228(a) No Competing System. The Department

2234shall not permit any new or substantially

2241renovated fixed-guideway, inter-city

2244passenger transportation system (including

2248any high-speed rail transportation system)

2253which competes with the System and any

2260extensions thereof, it being understood that

2266such legislation should not limit the

2272development of feeder distribution systems.

2277* * *

2280(e) New Fixed-Guideway Inter-City Systems

2285In Florida. FOX (or, at the election of FOX,

2294any of the Sponsors or one or more Affiliates

2303of FOX or any of the Sponsors) shall have a

2313right of first refusal with respect to the

2321design, engineering, procurement,

2324construction, testing, commissioning,

2327operation and maintenance of any high-speed

2333rail transportation system in the State of

2340Florida other than the System in accordance

2347with terms and conditions to be agreed in the

2356Fixed-Guideway Development Post-Franchise

2359Agreement to be entered into by the

2366Department and FOX.

236917. To ensure that the Department fully complied with the

2379Franchise, including the above agreement, the RFP included

2387specific protections for the FOX project in Part IV of the

2398Evaluation Criteria, titled "High Speed Rail Project."

2405(Evaluation Criteria, pages 8-9.)

240918. To safeguard the Department's agreements with FOX, and

2418in particular Subsection 2.2(a) of the FPFA, relating to the

2428protection from competing systems, the RFP included information

2436requirements designed to protect the FOX Franchise and

2444specifically stated:

2446. . . The Department must ensure that this

2455proposed lease of the Bee Line expressway

2462right of way does not compete with or

2470otherwise adversely impact the FOX franchise.

2476(Evaluation Criteria, page 8.)

248019. No proposal responsive to the RFP could compete with

2490the FOX project. While any reliable existing technology or

2499performance specifications that can be met by existing technology

2508are allowed to be proposed, the system proposed must not be

2519capable of operating in excess of 120 miles per hour.

2529(Evaluation Criteria, Part VI, pages 10-11.)

253520. The Department also is in compliance with the terms of

2546Subsection 2.2(e) of the FPFA, relating to FOX's right of first

2557refusal. Subsection 2.2(e) only applies to a new high-speed rail

2567transportation system, and by definition a high-speed rail

2575transportation system must be capable of operating in excess of

2585120 miles per hour. Section 341.322(16), Florida Statutes

2593(1997). The RFP solicits a system that will not be capable of

2605operating in excess of 120 miles per hour. In any event,

2616Subsection 2.2(e) is not, as yet, effective because FOX and the

2627Department have not entered into the Fixed-Guideway Development

2635Post-Franchise Agreement.

263721. A rail system proposed in response to the RFP would

2648complement the FOX system by providing passenger transportation

2656to specific destinations along the Bee Line Expressway, for

2665example to the Port of Canaveral, a destination not within a

2676service area to be served by FOX, or to the Orange County

2688Convention Center. Such feeder distributor functions of a Bee

2697Line rail system are specifically allowed by the FOX Franchise to

2708be developed by entities other than FOX.

271522. At present, the physical alignment of the FOX project

2725is not known. FOX is currently in the preliminary phase of

2736developing the high-speed rail project. DOT has retained

2744consultants who are presently engaged in the early stages of

2754evaluating the potential environmental and socioeconomic effects

2761of the FOX project.

276523. Under the National Environmental Policy Act (NEPA),

277342 U.S.C. Sections 4321, et seq ., the Florida High Speed Rail

2785Project must undergo an extensive review of all aspects of the

2796proposed system. This review produces the Environmental Impact

2804Statement (EIS). NEPA mandates analyses of the need for the

2814project, a comparison of all reasonable alternatives and routes,

2823including the alternative of not doing anything, as well as the

2834impacts on the human environment for each alternative. The

2843review is anticipated to take more than two years. The

2853alternative routings undergoing NEPA review include alignments

2860co-locating with portions of the Bee Line Expressway.

286824. Simultaneously with the NEPA review, the project will

2877be undergoing environmental review pursuant to a certification

2885process established by the Florida High Speed Rail Transportation

2894Act. This process, which is expected to take two to three years,

2906will result in the denial or approval of certification for the

2917project. The certification, which approves the final location of

2926the project, and which becomes the sole license and authority for

2937the project, is required prior to the construction and operation

2947of the system. The alignments for the high-speed rail

2956transportation system do not become final until the NEPA review

2966is completed and certification granted.

297125. On December 12, 1997, the United States Department of

2981Transportation, Federal Railroad Administration (FRA), published

2987notice of a proposed rule setting safety standards for the FOX

2998High Speed Rail Project. These proposed safety standards, which

3007are premised on accident and collision avoidance, contain various

3016requirements to ensure that high-speed rail tracks remain free of

3026any intrusion that could cause a wreck, including the

3035requirements that the right-of-way be fenced, that physical

3043barriers be built where the line is adjacent to other

3053transportation systems, and that a detection and alarm system be

3063installed to alert and stop the train should any intrusion occur.

307426. The proposed FRA rule would require FOX to develop a

3085system safety plan, which would describe FOX's system safety

3094program. FOX cannot finalize the design of its system until it

3105has developed its safety plan and completed the analysis required

3115by that plan. Since the system safety program established by the

3126plan will be a determining factor in deciding the exact right-of-

3137way for the FOX project, the exact right-of-way cannot be

3147determined until the at least the design portion of the system

3158safety plan is approved.

316227. Alternatives for collision avoidance can be costly. A

3171berm, including the cost of additional land needed for such a

3182structure, could cost $300,000 per linear foot. A concrete

3192barrier would cost $1.8 million per mile. Elevation of the FOX

3203guideway would add $10 million per mile to the cost of

3214constructing the guideway.

321728. If increased distance between FOX and another system

3226required FOX to diverge from the Bee Line right-of-way, resulting

3236in the need to purchase additional land, increased costs to the

3247project would be significant. Required eminent domain

3254proceedings also would be time-consuming. Increased

3260environmental permitting and mitigation also might result, at

3268additional costs in money and time. It was estimated that a year

3280of delay in the project would reduce FOX's bottom line by $200

3292million.

329329. While the final alignment of the FOX Project may not be

3305known for years, there was no evidence that a rail system

3316constructed along the Bee Line Expressway in response to the RFP

3327would make it impossible for FOX to comply with FRA safety

3338standards. A separate transportation system using part of the

3347Bee Line right-of-way can be planned simultaneously with the FOX

3357system with proper coordination. It is not necessary to delay

3367the Bee Line Expressway RFP until after FOX has its alignment

3378fixed.

337930. Planning the FOX Project and the Bee Line Expressway

3389RFP simultaneously may, but would not necessarily, increase the

3398construction cost of the FOX Project. Meanwhile, it might not be

3409possible to plan and implement a rail system along the Bee Line

3421Expressway after final alignment of the FOX project; if still

3431possible, logically, the costs of a rail system along the Bee

3442Line Expressway could increase if it had to be planned and

3453implemented after the final alignment of the FOX Project is

3463determined. Finally, delaying the Bee Line Expressway RFP until

3472after the FOX final alignment may only postpone, without totally

3482eliminating, additional costs to the FOX project. Whether nearby

3491transportation systems are in place initially or come after the

3501FOX project, the FRA will require FOX to take the measures

3512necessary to avoid collisions.

351631. Delay in the issuance of the RFP delays the opportunity

3527for the establishment of a complementary system along the Bee

3537Line Expressway. It is in the public interest for both systems

3548to go forward in a coordinated matter. The sooner the systems

3559are implemented, the sooner the needs of Florida's traveling

3568public will be served.

357232. It also is noted that the RFP does not set a date of

3586decision on proposals (except that the proposed Bee Line Lease

3596Agreement form is designed to accommodate a date before the turn

3607of the century.) In addition, the RFP Cover Sheet provides that

3618the Department can reject all proposals if they are not

3628satisfactory.

3629Property Not Owned By The Department

363533. The RFP allows proposers to include in the proposal the

3646use of right-of-way owned by the Port Authority and Expressway

3656Authority. (Evaluation Criteria, Part I, page 1.) This is

3665allowed to give a proposer the opportunity to develop a rail

3676system along the Bee Line Expressway that has meaningful station

3686locations, and such locations may well be on, or require the use

3698of, a portion of the Bee Line Expressway owned by another agency.

3710There is merit for the system to connect the Port of Canaveral

3722with the Orlando International Airport, and the RFP gives the

3732proposer the opportunity to propose these as stations. It will

3742be up to the proposer to suggest the property ownership

3752relationship for those portions of the alignment not owned by the

3763Department and to obtain approval of the land owners for such

3774relationship. (Evaluation Criteria, Part I, page 1.) These

3782other agencies agreed to issuance of the RFP and are willing to

3794work with the Department to effectuate a rail system that both

3805the Department and the agencies can approve. The RFP clearly

3815requires that the land owners approve any proposal affecting

3824their ownership rights. (Evaluation Criteria, Part I, page 1.)

3833Compliance With Zoning and Land Use Plans

384034. Part XII of the RFP's Evaluation Criteria requires

3849proposers to "demonstrate consistency to the maximum extent

3857feasible" with the applicable land use plans and "indicate the

3867extent of compatibility with existing and proposed land uses and

3877transportation systems." (Evaluation Criteria, Part IX, page 13

3885and Part XII, page 15.) The proposed lease agreement which is

3896part of the RFP specifies that the lessee is required to "conform

3908to and obey any present and future ordinances and/or rules,

3918regulations, requirements and orders of governmental authorities

3925or agencies respecting the use and occupation of said premises."

3935(Bee Line Lease Agreement, Paragraph 2.)

394135. As drafted, the RFP simply recognizes that certain

3950aspects of local comprehensive plans may need to be modified,

3960since a proposed transportation facility may not have been

3969considered during plan development. A proposal may require a

3978comprehensive plan amendment to be in compliance; alternatively,

3986it is possible that a necessary variance could be obtained.

3996Milestones

399736. The RFP allows for what it terms "milestones," which

4007are events and critical decisions that need to occur in

4017accordance with a schedule, because the Department recognizes:

4025Many requirements for system implementation

4030such as the total financing package, station

4037location selection, technology selection,

4041permitting, etc., probably will not be

4047finalized upon execution of a lease

4053agreement.

4054(Evaluation Criteria, Part I, pages 1-2.)

406037. This milestone concept is necessary to ensure the

4069orderly development of the facilities on the leased premises.

4078The "milestones" are conditions precedent and conditions

4085subsequent that will become part of the business arrangement for

4095the lease.

409738. The RFP gives proposers wide latitude to propose a

4107schedule for implementation of a proposal. The schedule will

4116include specific milestones for various activities. The

4123activities for which milestones are expected are identified in

4132the RFP. (Evaluation Criteria, Part I, pages 1-2; Part III, page

41437; Part V, page 9; Part VI, page 11; Part VII, page 11; Part

4157VIII, page 12; Part IX, page 13; Part X, page 13, Part XI, page

417114; Part XII, page 15; Part XIII, page 22; Part XIII, Subpart H,

4184page 23.) Proposers are to include in the proposal a schedule to

4196comply with the milestones. The Department would use this

4205information in evaluating the proposals. For the proposal

4213selected, the Department would also use this information to

4222establish a reasonable schedule for implementing the proposal.

4230The Department would use the "team approach" to ensure the

4240reasonableness of schedule, i.e. an expert in each milestone

4249subject area would be consulted.

425439. Part I. A. of the Evaluation Criteria refers to

"4264technology selection" among items of milestone information

4271required for system implementation that "probably will not be

4280finalized upon execution of a lease agreement." FOX suggests

4289that this reference makes the RFP confusing as to whether the

4300technology proposed should be in the RFP response and subject to

4311evaluation in the proposal selection process.

431740. Part I.B. of the Evaluation Criteria provides that:

4326[i]n determining whether to select or reject

4333a proposal the Department will consider and

4340balance all information required to be

4346submitted by the Request for Proposal and to

4354this extent each item of information

4360solicited is to be considered an evaluation

4367criterion. In its assessment of submitted

4373application, the Department will analyze the

4379information submitted in relation to the

4385information requirements of this RFP, the

4391provisions of Section 337.251, Florida

4396Statutes (1997), and Florida Administrative

4401Code Chapter 14-109, and will compare each

4408proposal to the other proposals submitted.

4414Under this provision, all information--including proposed

4420milestone schedules--will be subject to evaluation in the

4428proposal selection process.

443141. The evidence was reasonably clear that the RFP was not

4442intended to defer the technology proposal to milestone

4450information. Part VI of the Evaluation Criteria is reasonably

4459clear that the technology proposed should be included in the RFP

4470response and not deferred to milestone information. See Finding

44797, supra . In addition, it is implied throughout Part VIII of the

4492Evaluation Criteria, on "Operating Certification," that responses

4499to the RFP would include the actual technology proposed. Also,

4509while the RFP gives proposers flexibility in the selection of the

4520technology to be used, it specifies that "new" and "untried"

4530technologies are not to be proposed. (Evaluation Criteria, Part

4539VI, pages 10-11) The RFP is reasonably clear that it does not

4551defer the technology proposal to milestone information; rather,

4559it should be construed at most to afford the option of proposing

4571a milestone schedule for the "finalization" of the technology

4580selection.

458142. FOX also suggests that the requirement of a milestone

4591schedule for ridership and revenue estimates in Part XIII.H. of

4601the Evaluation Criteria makes the RFP confusing as to whether the

4612ridership analysis should be included in the RFP response and not

4623deferred to milestone information. But Part IV of the Evaluation

4633Criteria clearly requires proposers to provide an "[a]nalysis of

4642the ridership of the proposed system by year and

4651origin/destination pair to identify potential diversion of

4658ridership and associated revenue from FOX." Part XIII.H

4666requires, in addition, milestone information for "ridership and

4674revenue estimates that are current (no more than six months old)

4685and certified by a nationally recognized consulting firm."

469343. Part I.B. of the Evaluation Criteria should not cause

4703confusion as to whether information should be submitted at the

4713time of a response to the RFP in the form of milestones. Rather,

4726it simply makes clear that all information, including proposed

4735milestone schedules, will be considered as part of a proposal.

4745Logic and Fair Competition

474944. The Department RFP and its specifications, which were

4758developed by a team of experts, are designed to further the

4769Department's transportation policies and are based upon sound

4777transportation concepts. Within the framework of the governing

4785statute and rules, the specifications are logical in that they

4795provide for the selection of a lessee who will use the leased

4807premises for a much-needed transportation system.

481345. The specifications of the RFP apply to any entity

4823wishing to lease the Bee Line Expressway to develop a

4833transportation system that has a maximum speed capability of less

4843than 120 miles per hour. The specifications do not favor any

4854particular vendor of equipment or otherwise contain any

4862requirement that would be adverse to open competition by all

4872potential proposers desiring to respond to the RFP.

4880CONCLUSIONS OF LAW

488346. Section 120.57(3)(b), Florida Statutes (1997), provides

4890in pertinent part:

4893Any person who is adversely affected by the

4901agency decision or intended decision shall

4907file with the agency a notice of protest in

4916writing within 72 hours after the posting of

4924the bid tabulation or after receipt of the

4932notice of the agency decision or intended

4939decision and shall file a formal written

4946protest within 10 days after filing the

4953notice of protest. With respect to a protest

4961of the specifications contained in an

4967invitation to bid or in a request for

4975proposals, the notice of protest shall be

4982filed in writing within 72 hours after the

4990receipt of notice of the project plans and

4998specifications or intended project plans and

5004specifications in an invitation to bid or

5011request for proposals, and the formal written

5018protest shall be filed within 10 days after

5026the date the notice of protest is filed.

5034FOX filed its protest of the RFP's specifications under this

5044statute.

5045Standing

504647. The case law is clear that standing to protest agency

5057decisions concerning a contract award arising from the contract

5066bidding process under Section 120.57(3), Florida Statutes (1997),

5074is limited to bidders except in "exceptional circumstances." See

5083Ft. Howard v. Dept. of Management Services , 624 So. 2d 783, 785

5095(Fla. 1st DCA 1993)(bidder's supplier had no standing to protest

5105award to another bidder with a different supplier); Westinghouse

5114Elec. v. Jacksonville Transp. Authority , 491 So. 2d 1238, 1241

5124(Fla. 1st DCA 1986)(submission of ruse, instead of good faith

5134proposal, did not confer standing.) See also Brasfield & Gorrie

5144General Contractor, Inc., v. Ajax Construction Company, Inc., of

5153Tallahassee , 627 So. 2d 1200 (Fla. 1st DCA 1993)(non-bidder

5162construction company would have had no standing to protest award

5172and likewise had no standing to seek injunction of bidding

5182process.)

518348. In principle, there would not seem to be any reason why

5195standing to protest agency decisions concerning bid solicitations

5203or requests for proposals (and their specifications) should be

5212treated any differently. In practice, however, since the bidding

5221has not yet taken place when these early agency decisions are

5232being made, it can be difficult if not impossible to ascertain

5243whether such a protester will be a bidder.

525149. In this case, FOX initially did not allege that it

5262intended to respond to the RFP. After the Motion to Dismiss

5273FOX's original petition (and while maintaining that its

5281allegations were sufficient for standing,) FOX added the

5290allegation in paragraph 24 of the Amended Written Protest and

5300Petition for Formal Administrative Hearing that "FOX is a

5309potential respondent to the RFP." Prehearing, BLMS discounted

5317this additional allegation because, it contended, not only is

"5326potential" bidder status insufficient but also FOX's other

5334allegations ruled out all "potential" that FOX would respond to

5344the RFP.

534650. While it seemed from the face of the Amend ed Written

5358Protest and Petition for Formal Administrative Hearing as well as

5368from FOX's Response to Motion to Dismiss improbable that FOX

5378would respond to the RFP, it could not be said that all

"5390potential" was ruled out at that time. It was not clear until

5402final hearing that FOX has no intention to respond to the RFP.

541451. Nonetheless, it is concluded that FOX had standing to

5424protest the RFP specifications even though FOX is not a potential

5435bidder. The Ft. Howard and Westinghouse decisions contained

5443dicta that there can be "exceptional circumstances" that would

5452confer standing on a non-bidder to protest a bid award. But

5463neither defined the "exceptional circumstances," finding only

5470that they were not present in those cases. It is concluded that

5482FOX has a substantial interest in the RFP specifications because

5492they could affect FOX's statutory and contract rights as

5501Florida's exclusive high-speed rail transportation system

5507provider. It is concluded that this interest is the kind of

"5518exceptional circumstance" that is sufficient to support FOX's

5526standing in this case.

553052. FOX also contended that the decision in Fairbanks,

5539Inc., v. Dept. of Transp. , 635 So. 2d 58 (Fla. 1st DCA 1994),

5552supports its standing in this case under the "exceptional

5561circumstances." But the Fairbanks court was careful to

5569distinguish that the case before it arose from a request for a

5581formal administrative proceeding under Section 120.57(1), not

5588from a bid protest under Section 120.53(5) [now 120.57(3),

5597Florida Statutes (1997)], Florida Statutes (1991). The court

5605implied that the result may have been different had the case

5616arisen from a bid protest. In addition, the Fairbanks court

5626distinguished the Ft. Howard decision, stating that the protester

5635in Ft. Howard would not have had standing under either Section

5646120.53(5) [now 120.57(3), Florida Statutes (1997)], or Section

5654120.57(1), Florida Statutes (1991). Fairbanks , at 61.

566153. While it has been concluded that FOX has standing to

5672protest the RFP specifications, that does not mean FOX has

5682standing in this case to attempt to cancel the RFP altogether.

5693It is concluded that the purpose of bid protests under Section

5704120.57(3), Florida Statutes (1997), is to facilitate the contract

5713bidding process, not to enjoin it. (Even the ultimate rejection

5723of all bids as a result of a bid protest must be seen as

5737facilitating the contract bidding process, not enjoining it, as

5746it often results in re-bidding.) As a result, FOX's protest is

5757limited to its interest in refining the RFP's specifications; any

5767efforts to enjoin or cancel the RFP would have to take place in

5780some other proceeding.

5783Burden and Standard of Proof

578854. Section 120.57(3)(f), Florida Statutes (1997),

5794Unless otherwise provided by statute, the

5800burden of proof shall rest with the party

5808protesting the proposed agency action. In a

5815competitive-procurement protest, other than a

5820rejection of all bids, the administrative law

5827judge shall conduct a de novo proceeding to

5835determine whether the agency's proposed

5840action is contrary to the agency's governing

5847statutes, the agency's rules or policies, or

5854the bid or proposal specifications. The

5860standard of proof for such proceedings shall

5867be whether the proposed agency action was

5874clearly erroneous, contrary to competition,

5879arbitrary, or capricious.

5882In this case, FOX had the burden of proving that the RFP's

5894specifications are contrary to the Department's governing

5901statutes, rules or policies; in so doing, FOX must show that

5912specifications are clearly erroneous, contrary to competition,

5919arbitrary, or capricious.

5922Timing of the Lease

592655. Section 337.251(1), Florida Statutes (1997), provides

5933in pertinent part:

5936Leases under this section are subject to any

5944reservations, restrictions, or conditions

5948necessary to ensure adequate protection for

5954the safe and efficient operation and

5960maintenance of all transportation and utility

5966facilities, the adequacy of traffic flow, and

5973the full use of existing and future state

5981transportation facilities. Such joint

5985public-private use or commercial use of

5991property may not interfere with the primary

5998state transportation needs or present or

6004future utility needs for that property nor be

6012contrary to the best interests of the public.

6020FOX contends that the RFP is clearly erroneous, as contrary to

6031this statute, because FOX's right-of-way alignment and operating

6039envelope cannot be ascertained prior to submission of responses

6048to the RFP or a resulting lease.

605556. While it does appear that the precise impact of a

6066resulting lease on FOX cannot be ascertained prior to submission

6076of responses to the RFP or a resulting lease, that does not

6088necessarily mean that the Department will be unable to proceed

6098with the RFP in a way that will meet the requirements of Section

6111337.251(1), Florida Statutes (1997).

611557. While an adverse impact on the FOX Project may be

6126enough to support FOX's standing, Section 337.251(1) only

6134prohibits a lease that would "interfere with" the FOX project.

6144One of the express purposes of the RFP is to obtain proposals

6156that would not "interfere with" the FOX Project. It would be

6167premature at this time to conclude that the Department cannot and

6178will not receive a proposal that would enable the Department to

6189proceed with both projects in a way that would meet the

6200requirements of the statute.

620458. FOX similarly also contends that the RFP's

6212specifications are clearly erroneous, arbitrary or capricious

6219because Parts III and IV of the Evaluation Criteria contain

6229requirements that cannot be met prior to submission of responses

6239to the RFP or a resulting lease. But, again, it is premature at

6252this time to conclude that the Department cannot and will not

6263receive a proposal that meets the RFP's requirements.

627159. Part III of the RFP requires each proposer to describe

6282the proposed operating envelope and vertical alignment "within

6290the lease limits and at any point where this system crosses or

6302encroaches on any existing or proposed transportation

6309facilities." Clearly, it may not be possible to specify where a

6320proposed system would cross or encroach on the FOX system at this

6332time because the FOX system has not yet been "proposed" with

6343specificity. But just as clearly, a proposer could specify

6352crossing and encroachments with any existing systems and

6360specifically proposed systems (as well as with the FOX system to

6371the extent possible at this time), which is all the RFP requires.

638360. Part IV of the RFP requires responses to contain "[a]n

6394analysis of the land to be leased showing it does not adversely

6406impact the potential physical alignment of the FOX system," as

6416well as "[a]n analysis of the ridership of the proposed system."

6427Certainly, such analyses are possible although they might be

6436limited by the uncertainty of the FOX system. Part IV simply

6447states that, using the analyses, the "Department must ensure that

6457[the lease] does not compete with or otherwise adversely impact

6467the FOX franchise." It is premature at this time to conclude

6478that the Department will not be able to "ensure that [the lease]

6490does not compete with or otherwise adversely impact the FOX

6500franchise."

650161. FOX suggests that, to correct alleged deficiencies in

6510the timing of the lease, either the proposal submission date or

6521the date of decision must be postponed. However, it is noted

6532that the RFP does not set a date of decision on proposals. In

6545addition, the RFP Cover Sheet provides that the Department can

6555reject all proposals if they are not satisfactory.

6563Property Not Owned By The Department

656962. Section 337.251(1), Florida Statutes (1997), also

6576provides in pertinent part:

6580The department may lease to public agencies

6587or private entities, for a term not to exceed

659699 years, the use of department property,

6603including rights-of-way, for joint public-

6608private transportation purposes to further

6613economic development in this state and

6619generate revenue for transportation.

6623Florida Administrative Code Rule 14-109.001(2)(e) contains the

6630definition:

"6631Joint Public/Private Development" means the

6636leasing of Department-owned property,

6640including airspace, on which major

6645improvements will be constructed by the

6651lessee, the term of which shall not exceed 99

6660years, and the Department may accept cash,

6667goods, or services for rent, or a combination

6675of cash and goods or services for rent.

6683FOX contends that the RFP is clearly erroneous, as contrary to

6694this statute and rule, because the RFP covers property now owned

6705by the Orlando-Orange County Expressway Authority and by the

6714Canaveral Port Authority.

671763. Neither the statute or rule prohibits the RFP as

6727issued. The statute and rule simply authorize the Department to

6737lease property it owns. Clearly, the Department cannot lease

6746land owned by others without the owners' consent. It is clear

6757that the Orlando-Orange County Expressway Authority and the

6765Canaveral Port Authority have participated in the formulation of

6774the RFP; the leasing entities logically have sought proposals

6783integrating leases from all three into a single proposed project,

6793and the Department initiated the RFP process on behalf of all

6804three. Part I.A. of the Evaluation Criteria of the RFP specifies

6815and makes clear that the Orlando-Orange County Expressway

6823Authority and the Canaveral Port Authority must approve any

6832proposed lease selected by the Department.

683864. As the RFP is presently formulated, at some point after

6849the selection of a proposal, the Orlando-Orange County Expressway

6858Authority and the Canaveral Port Authority would have to convey

6868to the Department an interest in their property that the

6878Department could in turn lease (or perhaps sub-lease) to the

6888successful proposer. Proposals are expected to suggest how this

6897should be done. It is premature to invalidate the RFP at this

6909time.

6910Compliance With Zoning and Land Use Plans

691765. Section 337.251(1), Florida Statutes (1997), also

6924provides in pertinent part:

6928The department may not lease any such

6935property if the proposed use conflicts with

6942zoning or land development codes of any

6949affected local government.

6952FOX contends that the RFP is clearly erroneous, as contrary to

6963this statute, because Part XII of the RFP's Evaluation Criteria

6973requires proposers to "demonstrate consistency to the maximum

6981extent feasible" with the applicable land use plans and "indicate

6991the extent of compatibility with existing and proposed land uses

7001and transportation systems." While the statute does not permit

7010the Department to lease property in conflict with local zoning

7020and land use planning, the RFP does not suggest that it will

7032result in a lease in violation of the statute. To the contrary,

7044the proposed lease agreement which is part of the RFP specifies

7055that the lessee is required to "conform to and obey any present

7067and future ordinances and/or rules, regulations, requirements and

7075orders of governmental authorities or agencies respecting the use

7084and occupation of said premises." The RFP appropriately and

7093logically requires information from which the impact of a

7102proposal on local zoning and land use planning can be assessed.

7113This information would let the Department know if a variance or

7124amendment from existing or proposed local zoning or land use

7134plans would be required.

7138Milestones

713966. FOX makes several arguments with respect to alleged

7148flaws in the RFP's solicitation of milestone information. It

7157contends that the milestones inappropriately defer information

7164that should be provided at the time of the responses to the RFP;

7177allegedly, this results in the exclusion of evaluation criteria,

7186in violation of Florida Administrative Code

7192Rule 14-109.0011(4)(a)3. and Section 287.057(2), Florida Statutes

7199(1997).

720067. Rule 14-109.0011(4)(a)3. provides that "[e]valuation

7206criteria for proposals shall be included in each Request for

7216Proposals pursuant to Section 287.057(2), Florida Statutes."

7223Section 287.057(2) requires that requests for proposals include:

"7231all contractual terms and conditions applicable to the

7239procurement . . ., including criteria . . . ."; it also requires

7252selection of the proposal "determined in writing to be the most

7263advantageous to the state, taking into consideration the price

7272and the other criteria set forth in the request for proposals."

728368. FOX contends that parts of the RFP inappropriately

7292suggest that the selection of technology may be deferred and just

7303be milestone information. But it has been found that the RFP is

7315reasonably clear that this is not so. At most, the RFP merely

7327affords the option of proposing a milestone schedule for the

"7337finalization" of the technology selection.

734269. Similarly, FOX contends that a part of the RFP

7352inappropriately suggests that the ridership analysis may be

7360deferred. But it has been found that this clearly is not so.

7372The RFP merely requires, in addition to the ridership analysis

7382required to be submitted with responses to the RFP, milestone

7392information for "ridership and revenue estimates that are current

7401(no more than six months old) and certified by a nationally

7412recognized consulting firm."

7415RECOMMENDATION

7416Based upon the foregoing Findings of Fact and Conclusions of

7426Law, it is

7429RECOMMENDED that the Department of Transportation enter a

7437final order denying FOX's protest and upholding the RFP's

7446specifications.

7447DONE AND ENTERED this 6th day of August, 1998, in

7457Tallahassee, Leon County, Florida.

7461___________________________________

7462J. LAWRENCE JOHNSTON

7465Administrative Law Judge

7468Division of Administrative Hearings

7472The DeSoto Building

74751230 Apalachee Parkway

7478Tallahassee, Florida 32399-3060

7481(850) 488-9675 SUNCOM 278-9675

7485Fax Filing (850) 921-6847

7489Filed with the Clerk of the

7495Division of Administrative Hearings

7499this 6th day of August, 1998.

7505COPIES FURNISHED:

7507Martha Harrell Chumbler, Esquire

7511Carlton, Fields, Ward, Emmanuel,

7515Smith & Cutler, P.A.

7519Post Office Drawer 190

7523Tallahassee, Florida 32302

7526Betty J. Steffens, Esquire

7530210 South Monroe Street

7534Tallahassee, Florida 32301

7537John C. Bottcher

7540Assistant General Counsel

7543Department of Transportation

7546605 Suwannee Street

7549Tallahassee, Florida 32399-0450

7552Peter Antonacci, Esquire

7555George N. Meros, Jr., Esquire

7560Rumberger, Kirk & Caldwell, P.A.

7565Post Office Box 10507

7569Tallahassee, Florida 32392-2507

7572Thomas F. Barry, Secretary

7576Attention: Diedre Grubbs

7579Department of Transportation

7582Haydon Burns Building

7585605 Suwannee Street, Mail Station 58

7591Tallahassee, Florida 32399-0450

7594Pamela Leslie, General Counsel

7598Department of Transportation

7601Haydon Burns Building

7604605 Suwannee Street, Mail Station 58

7610Tallahassee, Florida 32399-0450

7613NOTICE OF RIGHT TO SUBMIT EXCEPTIONS

7619All parties have the right to submit written exceptions within 15

7630days from the date of this Recommended Order. Any exceptions to

7641this Recommended Order should be filed with the agency that will

7652issue the final order in this case.

Select the PDF icon to view the document.
PDF
Date
Proceedings
Date: 08/27/1998
Proceedings: Final Order filed.
PDF:
Date: 08/24/1998
Proceedings: Agency Final Order
PDF:
Date: 08/24/1998
Proceedings: Recommended Order
PDF:
Date: 08/06/1998
Proceedings: Recommended Order sent out. CASE CLOSED. Hearing held 07/02/98.
Date: 07/27/1998
Proceedings: Department of Transportation`s Proposed Recommended Order; Disk filed.
Date: 07/23/1998
Proceedings: (Bee Line Monorail System, Inc.) Proposed Recommended Order filed.
Date: 07/23/1998
Proceedings: Notice of Filing Petitioner`s Proposed Recommended Order; Proposed Recommended Order filed.
Date: 07/15/1998
Proceedings: Amended Notice of Filing; Volume 2 Transcript Title Page (Corrected) filed.
Date: 07/13/1998
Proceedings: Notice of Filing; (Volume 2 of 2) DOAH Court Reporter Final Hearing Transcript filed.
Date: 07/08/1998
Proceedings: Notice of Filing; Transcript filed.
Date: 07/02/1998
Proceedings: CASE STATUS: Hearing Held.
Date: 06/16/1998
Proceedings: CASE STATUS: Hearing Partially Held, continued to 7/2/98; 9:00am; Tallahassee.
Date: 06/16/1998
Proceedings: The Department of Transportation`s Response to Intervenor`s Motion in Limine (filed w/judge at hearing) filed.
Date: 06/15/1998
Proceedings: (Bee Line) Motion in Limine filed.
Date: 06/15/1998
Proceedings: Joint Prehearing Stipulation filed.
Date: 06/09/1998
Proceedings: Subpoena ad Testificandum (M. Chumbler) filed.
Date: 06/08/1998
Proceedings: (Bee Line) 2/Notice of Taking Deposition (filed via facsimile).
Date: 06/04/1998
Proceedings: (Bee Line) Notice of Deposition (filed via facsimile).
Date: 06/03/1998
Proceedings: Order Rescheduling Final Hearing sent out. (hearing set for June 16-17 & July 2, 1998; 9:00am)
Date: 06/02/1998
Proceedings: (P. Antonacci) Motion to Amend Prehearing Order (filed via facsimile).
Date: 05/29/1998
Proceedings: Order Granting Leave to Amend and Denying Motion to Dismiss sent out.
Date: 05/28/1998
Proceedings: (Petitioner) Motion for Leave to Amend; Amended Written Protest and Petition for Formal Administrative Hearing filed.
Date: 05/27/1998
Proceedings: (Petitioner) Response to Motion to Dismiss filed.
Date: 05/27/1998
Proceedings: (P. Antonacci) Motion to Dismiss the Amended Written Protest and Petition for Formal Administrative Hearing filed.
Date: 05/26/1998
Proceedings: (Petitioner) Motion for Leave to Amend (filed via facsimile).
Date: 05/20/1998
Proceedings: Order Granting Leave to Intervene sent out. (for Bee Line Monorail System, Inc.)
Date: 05/20/1998
Proceedings: (Respondent) Notice of Taking Deposition filed.
Date: 05/20/1998
Proceedings: Notice of Final Hearing sent out. (hearing set for 6/11/98; 9:00am; Tallahassee)
Date: 05/20/1998
Proceedings: Prehearing Order sent out.
Date: 05/12/1998
Proceedings: Agency Referral Letter; Letter to DOT from M. Chumbler (re: notification of intent to protest); Formal Written Protest and Petition for Formal Administrative Hearing (w/att`s) filed.

Case Information

Judge:
J. LAWRENCE JOHNSTON
Date Filed:
05/12/1998
Date Assignment:
05/13/1998
Last Docket Entry:
08/27/1998
Location:
Tallahassee, Florida
District:
Northern
Agency:
ADOPTED IN TOTO
Suffix:
BID
 

Related DOAH Cases(s) (2):

Related Florida Statute(s) (4):

Related Florida Rule(s) (1):