06-001916BID
Mic Development, Llc vs.
Department Of Transportation
Status: Closed
Recommended Order on Thursday, January 18, 2007.
Recommended Order on Thursday, January 18, 2007.
1Case No. 06-1916BID
4STATE OF FLORIDA
7DIVISION OF ADMINISTRATIVE HEARINGS
11MIC DEVELOPMENT, LLC, ) ) ) ) ) ) ) ) ) )
24Petitioner, RECOMMENDED ORDER
27vs.
28DEPARTMENT OF TRANSPORTATION,
31Respondent.
32__
33This case came before Administrative Law Judge John G. Van
43Laningham for final hearing on October 30 and 31, 2006, in Miami,
55Florida.
56APPEARANCES
57For Petitioner: Joseph M. Goldstein, Esquire
63Shutts & Bowen, LLP
67Wachovia Center, Suite 2100
71200 East Broward Boulevard
75Fort Lauderdale, Florida 33301
79For Respondent: Thomas Barnhart, Esquire
84Office of the Attorney General
89The Capitol, Plaza Level 01
94Tallahassee, Florida 32399
97STATEMENT OF THE ISSUE
101The issue in this bid protest is whether Respondent acted
111illegally, arbitrarily, dishonestly, or fraudulently when it
118decided to reject the sole proposal it had received in response
129to a solicitation asking "master developers" to submit
137competitive proposals for the development of various commercial
145projects that Respondent plans to make part of the Miami
155Intermodal Center, a complex of major transportation facilities
163being built near the Miami International Airport.
170PRELIMINARY STATEMENT
172On November 26, 2002, Respondent Department of
179Transportation issued a request for proposals that solicited
187offers from qualified developers interested in designing,
194constructing, financing, and managing the "joint development"
201component of a major transportation project being built adjacent
210to the Miami International Airport. On March 3, 2003, Petitioner
220MIC Development LLC submitted the only proposal that the
229Department received in response to this solicitation.
236On June 14, 2005, MIC Development LLC filed a notice of
247intent to protest Respondent's preliminary decisionwhich had
254been communicated via letters dated May 31, 2005to reject "all"
264proposals. On June 23, 2005, Petitioner filed its formal written
274protest. The Department referred the matter to the Division of
284Administrative Hearings ("DOAH") on August 11, 2005, for the sole
296purpose of litigating the issue of whether Petitioner's notice of
306intent to protest had been timely filed. This maneuver, which
316effectively severed the Department's affirmative defense (waiver)
323from Petitioner's protest of the agency's decision to reject all
333bids, went unchallenged, and a final hearing on the narrow issue
344of timeliness followed.
347The undersigned, who heard the previous case, entered a
356Recommended Order on April 20, 2006, which urged the Department
366to refer the matter to DOAH for a final hearing on the merits of
380Petitioner's protest. See MIC Development, LLC v. Department Of
389Transportation , 2006 Fla. Div. Adm. Hear. LEXIS 156 (Fla. Div.
399Adm. Hear. 2006). The Department complied, returning the protest
408on May 22, 2006.
412The final hearing on the merits of Petitioner's protest took
422place as scheduled on October 30 and 31, 2006. At the hearing,
434Joint Exhibits 1-26 and 28-37 were admitted into evidence. In
444addition, MIC Development LLC called the following witnesses:
452David C. Garrett, III of MIC Development LLC; Nick Serianni, a
463consultant to the Department; Steven E. Thompson, also a
472consultant to the Department; Gary Donn, Korouche Mohandes, and
481John Martinez, each of whom is an employee (or former employee)
492of the Department; and (by deposition) Department employees Gus
501Pego and Javier Rodriguez.
505During its case, the Department presented the testimony of
514Mr. Serianni, who was re-called as a witness. The Department
524also offered Respondent's Exhibits 1-17, which were received in
533evidence.
534The final hearing transcript was filed on November 29, 2006.
544Thereafter, the parties timely filed proposed recommended orders,
552which have been considered.
556Unless otherwise indicated, citations to the Florida
563Statutes refer to the 2006 Florida Statutes.
570FINDINGS OF FACT
5731. On November 26, 2002, the Florida Department of
582Transportation (the "Department" or "FDOT") issued a Request for
592Proposals for Joint Development (the "RFP"), the purpose of which
603was to solicit competitive proposals from "nationally recognized
611Master Developers" interested in participating in certain aspects
619of the ongoing Miami Intermodal Center project (the "MIC"). The
630MIC is a complex of major transportation facilities being built
640adjacent to the Miami International Airport ("MIA"). It is
651envisioned that, eventually, all of the various means of ground
661transport (e.g. private vehicle, rental car, bus, train, taxi,
670shuttle, etc.) will converge at the MIC.
6772. The "joint development" component of the MIC, with which
687the RFP was concerned, focuses on certain commercial (i.e. money-
697making) facilities ancillary to what is referred to as the "MIC
708Core." The MIC Core constitutes the "hub" of the MIC, to which
720all the roads (and tracks) will lead. The RFP described the MIC
732Core as follows:
735At full build-out, the MIC Core will become a
744major transportation hub and accommodate a
750variety of transportation modes, including
755rail, bus, and other vehicular traffic
761. . . . The MIC Core will accommodate
770extensions of the Metrorail, become the
776future terminus for AMTRAK and ultimately
782house a future East-West rail line. It will
790likewise provide station facilities for
795existing and future Tri-Rail commuter rail
801service. The MIC/MIA Connector station,
806serving the RCF [that is, the Rental Car
814Facility] and the MIC Core, will link MIC
822Core facilities and services to the main
829terminal at MIA. Bus terminal facilities
835will accommodate local (MDTA) and intercity
841(Greyhound) bus services, as well as a
848variety of courtesy buses/vehicles (rental
853car companies, hotels, cruise lines, etc.).
859Selected MIA related terminal functions are
865also proposed to be relocated to the MIC Core
874in the future (ticketing, baggage handling,
880etc.).
881RFP at 8. As the above description makes clear, the joint
892development component, though significant in its own right, is
901nevertheless only a piece of the MIC; it is not the entire
913project, by any means. Other important pieces of the MIC include
924such transportation components as the MIC Core, a Rental Car
934Facility ("RCF"), the MIC/MIA Connector (a light-rail "people
944mover"), and the MIC Terminal Access Roads ("MTAR").
9553. The goal which the Department sought to realize through
965the RFP was to negotiate and enter into a long-term lease
976agreement with a master developer who would design, finance,
985build, and manage the commercial elements of the MIC, paying rent
996to FDOT for the right to use and occupy the public property on
1009which the joint development project will be situated. To make
1019the joint development project economically sustainable,
1025interested developers were required to submit plans for such
1034revenue generating facilities as a hotel/conference center,
1041retail establishments, and commercial office buildings. The
1048RFP's approach to the scope of the undertaking was flexible,
1058giving proposers leeway in the following respects:
1065!" Proposers may offer to finance,
1071construct and manage the transportation
1076facilities, as well as commercial
1081development, as an integrated overall
1086project;
1087!" Alternatively, FDOT may provide funding
1093for, construct and own distinct
1098transportation components of the MIC
1103Core, or the Proposer may offer to
1110finance and build the entire project and
1117lease the transportation facilities back
1122to FDOT.
1124!" Proposers may modify the mix of
1131commercial uses contemplated for the MIC
1137based upon their own experience and
1143market information, as long as the
1149proposed program remains within the
1154parameters set by the MIC Record of
1161Decision and related development
1165agreements obtained for the MIC . . . .
1174RFP at 5.
11774. At the time it issued the RFP, the Department expected
1188that "landside" operations currently being conducted in the MIA
1197terminal would be moved to the MIC Core. Landside operations
1207include ticketing, passenger check-in, and baggage handling. The
1215RFP explained:
1217Spatial planning to date has been premised on
1225the future relocation to the MIC Core of
1233selected MIA terminal/land-side functions.
1237The MIC Core Pre-Schematic Program Analysis
1243(Exhibit IV) contains an analysis of site
1250alternatives and a preferred pre-schematic
1255proposal for the MIC Core site organization
1262that optimizes the integration of surface
1268transportation modes, MIA land-side functions
1273and a MIC joint development program.
1279RFP at 9. The upshot is that FDOT envisioned that a substantial
1291amount of the MIC Core's square footage would be given over to
1303landside functions, based on the premise that such functions one
1313day would be carried out in the MIC Core.
13225. Proposers were required to submit a "base plan"
"1331providing for hotel, office, parking, and ancillary retail"
1339uses. The RFP instructed further that the base plan needed to
1350conform to the pre-schematic proposal (referenced in paragraph 4
1359above). Thus, in their base plans, proposers had to accommodate
1369the Department's premise that landside functions requiring
1376substantial square footage eventually would be moved to the MIC
1386Core. Proposers were allowed, additionally, to submit one
"1394alternative plan" that could deviate from the base plan "both as
1405to site organization and mix of proposed uses."
14136. To choose a developer for the joint development
1422component of the MIC, the RFP called for a multi-step selection
1433process involving two formal committees: a Technical Review
1441Committee ("TRC") appointed by FDOT, and a Selection Committee
1452consisting of FDOT management. In the initial, "feasibility
1460determination" phase, the TRC would determine whether each
1468proposal met "threshold criteria" for "feasibility." After
1475making its feasibility determination with regard to each of the
1485proposals, the TRC would recommend to the Selection Committee
1494which proposals should be deemed feasible and which infeasible
1503(without ranking them). Then the Selection Committee, taking
1511into account the TRC's recommendations, would decide which
1519proposals were feasible and responsive to the RFP, and which were
1530not one or the other (or were neither). Any proposal deemed by
1542the Selection Committee to be infeasible, non-responsive, or both
1551would be dropped from further consideration at that point.
1560Feasible and responsive proposals would be returned to the TRC
1570for the next level of review.
15767. During the ensuing "evaluation" phase of the selection
1585process, the TRC would invite each proposer whose proposal was
1595deemed feasible and responsive to make an oral presentation to
1605the committee. Following the oral presentations, the TRC would
1614evaluate, score, and rank the competing proposals. The TRC's
1623recommended ranking of the proposals would be submitted to the
1633Selection Committee, which would make the "final selection" and
1642determine the "official ranking" based on the TRC's
1650recommendation.
16518. After the completion of the evaluation phase, the
1660selection process would proceed to the negotiation phase, during
1669which FDOT would
1672negotiate a lease agreement with the first
1679ranked Proposer. If negotiations [could] not
1685be concluded in a reasonable period of time,
1693then FDOT [would] have the option to cease
1701negotiations with the first ranked Proposer
1707and begin to negotiate with the second ranked
1715Proposer. The process [could] continue until
1721a contract [were] successfully negotiated, or
1727FDOT [could] re-advertise for proposals or
1733use a different procurement process.
1738RFP at 27-28.
17419. In the RFP, the Department reserved "all rights
1750available to it by law." Among the rights specifically reserved
1760were
1761the rights to reject any and all proposals at
1770any time, to request or retain additional
1777information for any proposals, to require
1783reasonable changes in the selected proposal
1789to more fully achieve the purposes and
1796objectives of [the] RFP, and to elect not to
1805enter into a lease agreement, unless FDOT is
1813fully satisfied that all conditions precedent
1819have been fully met.
1823RFP at 7. In addition, prospective proposers were notified that
1833the
1834RFP is solely a request for expressions of
1842interest and statements for feasible
1847proposals. . . . No contractual or other
1855legal obligations or relations between FDOT
1861and any Proposer shall be created except by
1869and through, in the sole discretion of FDOT,
1877a negotiated and fully executed lease
1883agreement between a proposer and FDOT.
1889In considering any proposals submitted in
1895response to this RFP, FDOT reserves the
1902absolute and unfettered discretion to:
1907* * *
1910!" Receive and review proposals in
1916accordance with this RFP, without being
1922obligated in any way to select the
1929Proposer or proposal.
1932!" Request clarification after the dates
1938and times set out in this RFP from any
1947one or more of the Proposers with
1954respect to proposals submitted.
1958RFP at 28.
196110. On March 3, 2003, Petitioner MIC Development LLC
1970("MDL") timely submitted a proposal in response to the RFP.
1982MDL's proposal was the only one that FDOT received.
199111. MDL is a joint venture between Mallory & Evans
2001Development LLC and Codina Group, Inc. that was formed
2010specifically for this procurement. In preparing its proposal,
2018MDL assembled a team of professionals that possess the necessary
2028experience and expertise to develop a project of the nature and
2039magnitude contemplated by the RFP.
204412. MDL offered both a base plan, as required, and an
2055alternative plan, as the RFP permitted. Though its base plan
2065conformed to FDOT's premises, MDL doubted that landside
2073operations requiring a substantial amount of space would ever be
2083moved to the MIC Core, as FDOT had directed proposers to assume.
2095MDL stated in its response that the prospect was "unlikely that
2106actual terminal ticketing would occur at the MIC."
211413. MDL also expressed in its proposal a desire to assume
2125overall responsibility for managing the development of the MIC:
2134The current planning calls for independent
2140development of MIC-related facilities. We
2145believe, from both a publicas well as
2152privatesector perspective, the project
2156would benefit from having a single point of
2164responsibility: a Master Developer
2168responsible for delivering the entire project
2174on-schedule and within budget. Both the
2180schedule and the budget would be approved by
2188FDOT prior to entry into the Master Lease.
2196. . .
2199* * *
2202Therefore, our proposal provides for Master-
2208Developer funding for the following project
2214elements: MTAR, RCF and MIC/MIA Connector.
2220Each of these projects would be turned over
2228to FDOT upon completion.
2232Though authorized under the RFP's specifications, MDL's offer to
2241take control of the management of the entire project, including
2251pieces outside of the joint development component (e.g. the MTAR,
2261RCF, and the MIC/MIA Connector), would have expanded the role of
2272the "master developer" beyond that for which FDOT had planned
2282when it issued the RFP.
228714. Regarding the potential for the project to generate
2296revenue for the Department, MDL's response was guarded:
2304After substantial and intense analysis, the
2310[MDL] team has concluded that the RFP's
2317approach, while admirable in many ways,
2323contemplates a project that may not be viable
2331without substantial, long-term government
2335subsidies. Why? Because, the "joint
2340development" elements of the project require
2346an extraordinary amount of time to develop
2353into positive revenue generators. The
2358project economics will not allow for payments
2365to FDOT until the construction has been
2372completed; even then, it will be necessary to
2380ramp up payments over time.
238515. MDL's proposal for the base plan was conditioned on
2395several assumptions, namely:
2398 Relocation of terminal ticketing and
2404baggage claim from MIA to the MIC;
2411 Restriction of access to current airport
2418terminal areas to official MIA or public
2425safety-related vehicles or vehicles
2429entering on-airport decks;
2432 Verification of market demand for full
2439build-out of the MIC Hotel/Conference
2444Center and the MIC Office Buildings;
2450 Acceptance by FDOT of the Master
2457Developer-financed and managed,
2460comprehensive project delivery, as set
2465forth above, or agreement by FDOT to
2472assume responsibility for all damages to
2478Master Developer arising out of delays
2484associated with currently proposed
2488project delivery method;
2491 No Ground Rental payments due to FDOT
2499until completion of Construction.
250316. MDL's alternative plan proposed to re-organize the
2511joint development uses in ways that MDL believed would make the
2522project more conducive to commercial endeavors, while at the same
2532time enhancing the utility and convenience of the transportation
2541elements. Consistent with its skepticism concerning the putative
2549need to devote huge amounts of space to landside operations, MDL
2560offered in its alternative plan to scale down the size of the
2572area set aside for such purposes. Like the base plan, MDL's
2583alternative plan was subject to several conditions, to wit:
2592 Relocation of terminal ticketing and
2598baggage claim from MIA to the MIC or
2606mutually acceptable re-planning of the
2611facility to remove this function and its
2618associate space from the MIC Core
2624project scope;
2626 Restriction of access to current airport
2633terminal areas to official MIA or public
2640safety-related vehicles or vehicles
2644entering on-airport decks;
2647 Acceptance by FDOT of the Master
2654Developer-financed and managed,
2657comprehensive project delivery, as set
2662forth above or agreement by FDOT to
2669assume responsibility for all damages to
2675Master Developer arising out of delays
2681associated with currently proposed
2685project delivery method;
2688 No Ground Rental payments due to FDOT
2696until completion of Construction.
270017. On or about April 2, 2003, the Department sent MDL an
2712extensive request for clarification of its proposal, which
2720consisted of 43 numbered questions, some entailing many subparts.
2729A few days later, MDL informed FDOT that it would submit a formal
2742written response to the request for clarification on or before
2752May 2, 2003.
275518. Meantime, by letter dated April 22, 2003, an FDOT
2765district manager reminded the Miami-Dade Aviation Department
2772("MDAD") that the Department had "initiated the procurement
2782process for the selection of a Master Developer" with a view
2793toward "negotiat[ing] a lease agreement with the selected Master
2802Developer and begin[ning] in earnest the design process for the
2812MIC Core/transportation hub." In light of that, to "reconfirm
2821[FDOT's] planning assumptions," MDAD was asked to answer the
2830following questions regarding its plans for the relocation of
2839landside functions to the MIC:
28441. Does the County/MIA still plan to
2851relocate selected airport landside facilities
2856to the MIC Core/transportation hub?
28612. If so, what type of landside facilities
2869would be relocated?
28723. What is the approximate timeframe for
2879this relocation to occur?
288319. MDAD's response, delivered via letter dated May 5,
28922003, was noncommittal, to say the least. Mostly, the letter
2902recounted the history of the "MOVE Committee" that had been
2912appointed by the mayor in 1998 to study, and make recommendations
2923concerning, the development and financing of the MIC. In this
2933regard, the letter stated, in pertinent part, as follows:
2942[V]arious alternatives for transferring
2946baggage between the MIC and Miami
2952International Airport (MIA) [were studied].
2957. . . [A]ll options studied were not
2965logistically feasible and/or [were] cost
2970prohibitive. Most importantly, the airlines
2975expressed no desire to relocate these
2981functions from the MIA terminal. . . .
2989[Ultimately, in late 1999, it was] resolved
2996to allow users and planners to continue to
3004develop future baggage handling plans for the
3011short-term and long-term scenarios.
3015After providing this historical background, the letter concluded:
3023To date, there has [sic] been no baggage
3031handling solutions submitted to [MDAD],
3036airlines, or the Transportation Security
3041Administration for review and approval.
3046Furthermore, MDAD's approved Capital
3050Improvement Program does not provide for the
3057relocation of landside functions to the MIC.
3064Please keep us informed as the MIC Core
3072design progresses.
307420. The Department interpreted MDAD's letter as expressing
3082MDAD's final decision that landside operations would never be
3091relocated to the MIC Core; throughout these proceedings, the
3100Department has adhered to this interpretation. The undersigned,
3108having only MDAD's letter as proof of MDAD's intentions (for no
3119one from MDAD testified at the hearing), does not detect as much
3131decisiveness in the text; rather, as the undersigned reads the
3141letter, MDAD gave an ambiguous, non-responsive answer to FDOT's
3150specific questions, expressing no enthusiasm for moving landside
3158operations to the MIC, to be sure, but not quite saying no, thank
3171you eitherat least not forthrightly. Given the importance that
3180FDOT had attached to the relocation of landside functions to the
3191MIC Core, and because MDAD's supposed "decision" upset FDOT's
3200assumptions about MDAD's plans, it puzzles the undersigned that
3209the Department passively accepted the May 5, 2003, letter as a
3220definitive position-statement, without aggressively following up
3226to find out what exactly MDAD had in mind with regard to this
3239issue. At any rate, the parties have stipulated that MDAD
3249decided not to move landside functions to the MICand so the
3260undersigned finds that to be the case.
326721. There is conflicting evidence regarding the extent to
3276which MDAD's change of heart concerning landside functions caught
3285the Department off guard. Yet, whether the letter of May 5,
32962003, came as a genuine surprise or not, the Department can
3307fairly be criticized for having failed to nail down this
3317important matter before issuing the RFP, an oversight for which
3327the undersigned can find no explanation in the record. But such
3338criticism cannot change the fact that, as of May 5, 2003, a major
3351premise on which the RFP was based had been discredited, making
3362obsolete the base plan's site organization of the MIC Core.
3372Without landside functions, the MIC Core probably would not need
3382to be as large as FDOT had thought, and the planned mix of uses
3396for the hub would need to be reconsidered.
340422. On May 2, 2003, MDL submitted its lengthy, formal
3414response to FDOT's first request for clarification. The TRC
3423then met on May 28, 2003, to determine the feasibility of MDL's
3435proposal, as clarified. At that meeting, the TRC voted in favor
3446of recommending to the Selection Committee that MDL's proposal be
3456found feasible.
345823. Shortly thereafter, the Selection Committee accepted
3465the TRC's recommendation. The Department notified MDL of this
3474decision via an email dated May 30, 2003, which provided in
3485pertinent part as follows:
3489On behalf of the [Department], this formal
3496notification addresses FDOT's determination
3500of feasibility of [MDL's] proposal . . . .
3509The Selection Committee, in accordance with
3515the RFP . . . , has determined that [MDL's]
3524response and clarification is feasible,
3529subject to the reservations stated below. In
3536accordance with the RFP, the proposal will be
3544evaluated and an oral presentation/interview
3549will be convened.
3552This letter also requests that [MDL] provide
3559clarification of its proposal in response to
3566the May 5, 2003, letter from [MDAD] . . . .
3577Specifically, please describe the impact on
3583your proposal, if any, of the lack of any
3592airport landside functions being located at
3598the MIC and any changes that you would make
3607to the [MDL] proposal.
361124. Although the formal notification of feasibility did not
3620explicitly say so, the Selection Committee's determination
3627necessarily implied a finding that MDL's proposal was responsive
3636as well as feasible, because the selection process established
3645under the RFP required the Selection Committee to determine both
3655feasibility and responsiveness following the TRC's initial
3662feasibility determination. The Selection Committee's duty to
3669determine responsiveness arose from the RFP's prescriptions that
3677(a) only feasible and responsive proposals would be further
3686evaluated after the feasibility determination phase (RFP at 25),
3695and (b) the opportunity to make an oral presentation to the TRC
3707would be provided, not to all proposers, but to proposers
"3717receiving notice that their proposals have been determined to be
3727responsive and feasible" (RFP at 27). 1
373425. On June 13, 2003, MDL submitted a response to FDOT's
3745request for clarification relating to the likely absence of
3754landside operations at the MIC. Given that its alternative plan
3764took account of this contingency, MDL naturally viewed MDAD's
3773decision as "not unexpected" and urged that the situation be
3783embraced as a positive opportunity to place additional revenue
3792generating, commercial uses in and around the MIC Core.
380126. The TRC met on July 9, 2003, to consider this second
3813clarification of MDL's response to the RFP. By this point, FDOT
3824had a number of concerns about moving forward with the
3834procurement, concerns that were making the Department reluctant
3842to proceed with formal negotiations. Instead of strictly
3850following the prescribed multi-step evaluation process, which
3857contemplated that formal negotiations with the first ranked
3865proposer would commence after (a) the TRC had evaluated, scored,
3875and ranked the feasible, responsive proposals, and (b) the
3884Selection Committee had established the official ranking thereof
3892based on the TRC's recommendation, the Department, acting through
3901the TRC as its agent, effectively engaged in informal
3910negotiations with MDL, conflating the evaluation and negotiation
3918phases. In retrospect, it can be seen that a de facto
3929negotiation phase had begun with FDOT's initial request for
3938clarification on April 2, 2003, which was the first of several
3949such requests that were tantamount to bargaining.
395627. These negotiations were decidedly one-sided. Because
3963FDOT evidently was in no hurry at that time to complete the joint
3976development component of the MIC, it was prepared to tolerate, as
3987an alternative to accepting conditions in MDL's proposal that
3996were believed to be disadvantageous, the uncertainty and delay
4005that would follow from rejecting all proposals and starting over
4015with a new RFP, a course of action which, despite its drawbacks,
4027at least held out the hope of securing a better deal. As the
4040only proposer, moreover, MDL was forced to compete, in effect,
4050not against any actual proposal, but against a hypothetical one
4060more to the Department's liking, which might (or might not)
4070materialize in a future procurement. Occupying the superior
4078bargaining position, the Department was able to ask MDL
4087repeatedly for more information, and MDL had no choice (if it
4098wanted to remain under consideration for the contract) but to
4108comply.
410928. It is no surprise, therefore, that the Department's
4118requests "for clarification" were in essence demands that MDL
4127make concessions regarding aspects of its proposal that the
4136Department was not inclined to accept. Broadly speaking, the
4145major sticking points stemmed from: (1) the apparent need to
4155consider a wider variety of commercial uses for the MIC Core, to
4167compensate for the absence of landside functions (and attendant
4176loss of passenger traffic therefrom); (2) MDL's desire to be in
4187charge of managing the construction of entire project, including
4196the transportation elements; and (3) disagreements regarding the
4204amount and timing of ground rental payments.
421129. To give a flavor of the parties' disagreements without
4221going into great detail, the following is a very brief sketch.
4232Regarding the mix of uses, MDL believed that, in the interest of
4244making the joint development a financial success, it was
4253necessary to explore such commercial options as residential
4261apartments and "big box" retail, which could potentially bring
4270people (i.e. customers) to the MICan especially critical need
4279if landside operations would not be the draw. For its part, FDOT
4291was skeptical about the market demand for these particular uses
4301and believed that they might be inconsistent with the overall
4311concept, if not legally impermissible.
431630. MDL consistently maintained that, in order to make
4325reasonable projections regarding the timing and amount of income
4334expected to flow from the commercial elementsprojections which
4342were necessary, among other reasons, to secure project
4350financinga schedule for completing the various phases of the
4359MIC would need to be drawn up and adhered to; furthermore, if the
4372construction schedule were not met, MDL would be exposed to
4382liability for damages caused by the delay. MDL was unwilling to
4393assume the risks of loss arising from any delays whose causes it
4405could not control. MDL's solution was to take control of the
4416entire MIC construction project, which would put MDL in a
4426position to bring about the timely completion of the various
4436phasesor be directly responsible for any delays.
4443Alternatively, MDL wanted FDOT to give performance guarantees,
4451effectively putting the risk of loss from construction delays on
4461FDOT. FDOT, however, was reluctant to surrender complete control
4470of the project to MDL, and it refused to assume the risk of loss
4484from delays.
448631. On the matter of ground rents, the parties were never
4497able to agree on the amounts MDL would pay. Probably the bigger
4509point of contention, though, concerned the timing of the
4518payments. MDL held that rents could not become due and payable
4529until various phases of the construction were completed, when
4538anticipated income streams would begin to flow. FDOT, in
4547contrast, insisted that ground rent be payable from the date of
4558the execution of the lease, including during the "holding period"
4568when the joint development component would not be generating
4577revenue for the lessee.
458132. These points were not resolved at the TRC meeting on
4592July 9, 2003; to the contrary, more questions were raised,
4602resulting in FDOT sending yet another request for information to
4612MDL, to which the latter responded by memorandum dated
4621September 19, 2003. The TRC met againand for the last timeon
4632October 27, 2003, to consider MDL's latest submission. The TRC
4642reached no conclusions and made no recommendations, leaving the
4651still unresolved points of concern unresolved. Practically
4658speaking, the selection process had stalled.
466433. After that, there would be a couple of meetings,
4674scheduled at the instance of MDL, between the principals of MDL
4685and public officials who had not been directly involved in the
4696selection process as members of either the TRC or the Selection
4707Committee. At the first of these, which occurred on November 4,
47182003, FDOT management and MDL representatives discussed the
4726Department's concerns and considered ways to jump start the
4735procurement. Agreeing that an independent appraisal of the
4743property might help bring the parties together on the issue of
4754ground rent, it was decided at this meeting that such an
4765appraisal would be conducted.
476934. For reasons not entirely clear, however, the appraisal
4778process did not begin straightaway, and consequently MDL arranged
4787through the Governor's Office to meet with Secretary Simon of the
4798Department of Management Services. This meeting took place
4806sometime in February 2004. Two months later, in April 2004, the
4817Department initiated an appraisal process that continued through
4825the end of the year, resulting in a pair of appraisal reports,
4837one that was issued in December 2004, another in February 2005.
484835. The appraisals did not resolve the outstanding issues
4857relating to ground rent. Nor, between November 2003 and February
48672005, had the parties been able to reach agreement on the other
4879points of contention. At the risk of oversimplifying some fairly
4889complex issues, it is reasonably accurate to say that, as of
4900February 2005, the Department remained unconvinced that, among
4908other things: (1) MDL's proposed mix of uses for the MIC Core
4920was appropriate; (2) placing MDL in overall control of
4929construction management would add value to the project; and (3)
4939the economics of the joint development project required that
4948ground rents not become due and payable until after the
4958completion of various phases of the construction. In short, the
4968parties had reached an impasse.
497336. On September 20, 2005, the Selection Committee met and
4983determined, by a unanimous vote, to reject all proposals.
4992Ultimate Factual Determinations
499537. MDL argues that the process by which FDOT arrived at
5006its decision to reject all bids was arbitrary and flawed. MDL
5017complains, in part, that the TRC actively worked against MDL
5027because some of the TRC's members were (and as of the final
5039hearing continued to be) private consultants to FDOT on the MIC
5050project who have earned substantial fees for providing the
5059Department with construction management services and are in line
5068to continue receiving such feesunless a firm such as MDL is
5079chosen to take control of the entire project or portions thereof.
5090In other words, MDL alleges that the TRC had a conflict of
5102interest that prevented it from fairly and objectively analyzing
5111MDL's proposal.
511338. MDL contends, additionally, that in rejecting all
5121proposals, the Section Committeewhich did not act on a
5130recommendation of the TRCrelied on false or incomplete
5138information concerning MDL's proposal, and hence behaved
5145irrationally or capriciously. In furtherance of this argument,
5153MDL points outcorrectlythat the minutes of the Selection
5161Committee's relatively brief (less than 30 minutes) meeting are
5170silent as to the grounds for rejecting all proposals.
517939. MDL's criticisms of the process, though ultimately not
5188decisive, are not trivial either. For instance, FDOT in fact has
5199paid its consultants nearly $60 million in fees for work on the
5211MIC. While it is understandable that, in carrying out the joint
5222development project, the Department would desire and solicit the
5231advice of its trusted and knowledgeable consultants, it is also
5241true that placing some of these consultants on a review panel
5252responsible for selecting a developer who might propose to assume
5262some portion of the consultants' responsibilities gives rise to
5271the appearance, at least, of a potential conflict of interest.
5281To avoid even the appearance of such a conflict, the Department,
5292in exercising its wide discretion over procurement decisions,
5300could have used an independent "board of advisors" for the
5310technical review of proposals, as permitted under Section
5318337.251(3), Florida Statutes, and Florida Administrative Code
5325Rule 14-109.0011(4)(d)1. While the undersigned believes that, as
5333a general proposition, relying on an outside board of advisors is
5344a wise approach, which is no doubt why the legislature authorized
5355the use of boards of advisors in this type of procurement, it is
5368nevertheless determined that the Department's appointment of
5375private consultants to serve on the TRC was not an abuse of
5387discretion, but a legally permissible policy decision; there is
5396no persuasive evidence that FDOT acted dishonestly, fraudulently,
5404or arbitrarily in this regard. 2
541040. There is some truth as well in MDL's charge that the
5422selection process did not unfold in strict conformity to the RFP.
5433What the evidence fails to establish, however, is that the
5443process was so compromised as to produce an arbitrary (or
5453otherwise impermissibly founded) decision, the purpose or effect
5461of which was to defeat the object and integrity of competitive
5472procurement. As the undersigned sees it, the selection process
5481was not undone by malfeasance or misfeasance, as MDL posits;
5491instead, the process was modified somewhat in consequence of
5500FDOT's receipt of just one proposal. Because there was only one
5511proposal to review, some elements of the evaluation process, e.g.
5521scoring and ranking, were essentially superfluous. Indeed, once
5529feasibility and responsiveness were decided, the real question
5537became whether FDOT and MDL could come to a meeting of the minds
5550with regard to the lease agreement pursuant to which the joint
5561development would occur. Accordingly, in an honest attempt to
5570answer the salient question, the TRC engaged in negotiations with
5580MDL over the points of the latter's proposal that the Department
5591considered most problematic. While this deviated from the RFP,
5600the TRC's conduct of de facto negotiations was not unfair to MDL,
5612even though FDOT clearly had the upper hand in the exchange,
5623because the informal bargaining kept the process alive at times
5633when the alternative would have been simply to reject all
5643proposals and start over. There is no persuasive evidence that
5653the selection process, though imperfect, was illegal, arbitrary,
5661dishonest, or fraudulent.
566441. As for the Selection Committee's decision to reject all
5674proposals, while the grounds therefor should have been better
5683documented (in the minutes, for example), the record as a whole
5694makes clear the numerous reasons behind the committee's action.
5703In a nutshell, FDOT was dissatisfied with certain elements of
5713MDL's proposal, as set forth above, and believed that a more
5724attractive offer might be elicited if another request for
5733proposals were issued. Being under no apparent time-pressure to
5742do the deal, the Department took hard bargaining positions and
5752basically refused to budge. Whether the Department will later
5761regret releasing a bird in the hand, time will tell. But on
5773business decisions regarding matters such as the mix of uses for
5784the MIC Core, the timing and amount of ground rent, and control
5796of the construction management, the Department has wide
5804discretion, to which the undersigned must defer, lest he
5813substitute his judgment for the agency's. The wisdomand even,
5822to a large degree, the reasonablenessof the Department's
5830judgments in these matters is not subject to review. The issue,
5841rather, is whether the ultimate decision was illegal, arbitrary,
5850dishonest, or fraudulent. Here, the evidence fails to persuade
5859that it was.
586242. To the contrary, the evidence establishes that FDOT had
5872several honest and rational grounds for rejecting all proposals.
5881The firstand simplestreason was that only one response to the
5891RFP had been received. By itself, that fact was sufficient to
5902warrant the decision not to proceed. Beyond that, however, the
5912Department articulated legitimate reservations about MDL's
5918proposalreservations grounded in logic and reason, not whim
5926which caused the Department to conclude in good faith that MDL's
5937proposal failed to meet its (FDOT's) expectations. Now, it might
5947turn out that the Department's logic is flawed, or that its
5958present expectations are unrealisticindeed, the day might come
5966when FDOT regrets having turned MDL down. But nothing in the law
5978or the RFP compelled the Department to accept, for example, MDL's
5989condition that responsibility for overall construction management
5996be ceded to MDL, or MDL's offer to begin paying ground rent, not
6009upon the signing of a lease, but only as various phases of the
6022construction were completed. MDL's business decision to re-
6030advertise the joint development project in hopes of finding a
6040better deal might prove to be brilliant, or it might someday be
6052thought ill-advised, but it was not illegal, arbitrary,
6060dishonest, or fraudulent.
6063CONCLUSIONS OF LAW
606643. DOAH has personal and subject matter jurisdiction in
6075this proceeding pursuant to Sections 120.569 and 120.57(1),
6083Florida Statutes, and the parties have standing.
609044. Section 120.57(3)(f), Florida Statutes, provides that
6097in a proceeding brought to protest the intended rejection of all
6108competitive proposals, the standard of review shall be whether
6117the proposed agency action is "illegal, arbitrary, dishonest or
6126fraudulent." This standard derives from Department of
6133Transportation v. Groves-Watkins Constructors , 530 So. 2d 912,
6141914 (Fla. 1988), a case in which the Florida Supreme Court held
6153that the administrative law judge's "sole responsibility [in
6161reviewing a decision to reject all bids] is to ascertain whether
6172the agency acted fraudulently, arbitrarily, illegally or
6179dishonestly."
618045. The burden of proof rests with the party opposing the
6191proposed agency action. See State Contracting and Engineering
6199Corp. v. Department of Transportation , 709 So. 2d 607, 609 (Fla.
62101998). As the protesting party, MDL must sustain its burden of
6221proof by a preponderance of the evidence. Department of
6230Transportation v. J.W.C. Co., Inc ., 396 So. 2d 778, 787 (Fla. 1st
6243DCA 1981).
624546. In Scientific Games, Inc. v. Dittler Brothers, Inc .,
6255586 So. 2d 1128, 1131 (Fla. 1st DCA 1991), the First District
6267Court of Appeal described the deference to be accorded an agency
6278in connection with a competitive procurement:
6284The Hearing Officer need not, in effect,
6291second guess the members of the evaluation
6298committee to determine whether he and/or
6304other reasonable and well-informed persons
6309might have reached a contrary result.
6315Rather, a "public body has wide discretion "
6322in the bidding process and "its discretion,
6329when based on an honest exercise" of the
6337discretion, should not be overturned "even if
6344it may appear erroneous and even if reasonable persons
6353may disagree."
6355(Citations omitted; emphasis in original).
636047. In Gulf Real Properties, Inc. v. Department of Health
6370and Rehabilitative Services , 687 So. 2d 1336, 1338 (Fla. 1st DCA
63811997), the court upheld an agency's intended rejection of all
6391bids, stating that "an agency's rejection of all bids must stand,
6402absent a showing that the 'purpose or effect of the rejection is
6414to defeat the object and integrity of competitive bidding.'"
642348. An arbitrary decision is one that is not supported by
6434facts or logic, or is despotic. Agrico Chemical Co. v.
6444Department of Environmental Regulation , 365 So. 2d 759, 763 (Fla.
64541st DCA 1978). Under the arbitrary and capricious standard, "an
6464agency is to be subjected only to the most rudimentary command of
6476rationality. The reviewing court is not authorized to examine
6485whether the agency's empirical conclusions have support in
6493substantial evidence." Adam Smith Enterprises, Inc. v. State
6501Department of Environmental Regulation , 553 So. 2d 1260, 1273
6510(Fla. 1st DCA 1989). Still,
6515the reviewing court must consider whether the
6522agency: (1) has considered all relevant
6528factors; (2) has given actual, good faith
6535consideration to those factors; and (3) has
6542used reason rather than whim to progress from
6550consideration of each of these factors to its
6558final decision.
6560Id.
656149. The second district has supplied the following test for
6571determining whether a decision was arbitrary: "If an
6579administrative decision is justifiable under any analysis that a
6588reasonable person would use to reach a decision of similar
6598importance, it would seem that the decision is neither arbitrary
6608nor capricious." Dravo Basic Materials Co., Inc. v. State
6617Department of Transportation , 602 So. 2d 632, 634 n.3 (Fla. 2d
6628DCA 1992). As the court observed, this "is usually a fact-
6639intensive determination." Id. at 634.
664450. The undersigned believes that a reasonable person,
6652seeking competitive proposals on a major construction project,
6660could reasonably decide, after receiving just one proposal, that
6669he would prefer, as an alternative to entering presently into a
6680contract with the sole proposer, to repeat the solicitation
6689process in hopes of obtaining a wider selection of proposals from
6700which to choose, even though doing so will cause delay, not to
6712mention put at risk the only proposal he has, while offering no
6724guarantee that he will wind up with a better deal. Thus, the
6736undersigned has concluded that FDOT's decision to reject all
6745proposals in this instance was justifiable, if for no other
6755reason, on the ground that MDL's proposal was the only one
6766received. See Rosiek Construction Co., Inc., v. Department of
6775Transportation , 2005 Fla. Div. Adm. Hear. LEXIS 1110, *24 (Fla.
6785Div. Adm. Hear. 2005)("DOT did not act illegally or arbitrarily
6796when it rejected the [protester's] bid solely on the basis that
6807it was the only bid received.").
681451. Moreover, the evidence shows, as found above, that FDOT
6824considered other relevant factors and determined, not
6831whimsically, but on the basis of logic and reasoning, that MDL's
6842proposal was insufficiently attractive under the circumstancesa
6849decision that falls squarely within the agency's wide discretion.
6858Accordingly, as set forth in the Findings of Fact, the trier has
6870determined as matter of ultimate fact that FDOT's decision was
6880not illegal, arbitrary, dishonest, or fraudulent.
6886RECOMMENDATION
6887Based on the foregoing Findings of Fact and Conclusions of
6897Law, it is RECOMMENDED that the Department enter a final order
6908affirming that its decision to reject all proposals was not
6918illegal, dishonest, fraudulent, or arbitrary.
6923DONE AND ENTERED this 18th day of February, 2007, in
6933Tallahassee, Leon County, Florida.
6937S
6938___________________________________
6939JOHN G. VAN LANINGHAM
6943Administrative Law Judge
6946Division of Administrative Hearings
6950The DeSoto Building
69531230 Apalachee Parkway
6956Tallahassee, Florida 32399-3060
6959(850) 488-9675 SUNCOM 278-9675
6963Fax Filing (850) 921-6847
6967www.doah.state.fl.us
6968Filed with the Clerk of the
6974Division of Administrative Hearings
6978this 18th day of February, 2007.
6984ENDNOTES
69851 / In its Proposed Recommended Order, the Department argues at
6996length that MDL's proposal was non-responsive and hence subject
7005to rejection on that basis. As far as the undersigned can tell,
7017however, this rationale was not invoked during the run-up to the
7028instant litigation, nor was it raised previously herein.
7036Tellingly, the parties' Joint Pre-Hearing Stipulation does not
7044identify any issues of law or fact concerning the alleged non-
7055responsiveness of MDL's proposal. Doubting the propriety of
7063taking up this issue, of which MDL had no advance notice, the
7075undersigned will not discuss the subject of responsiveness in
7084detail. Suffice it to say that there is no persuasive evidence
7095that the Selection Committee's implicit determination regarding
7102the responsiveness of MDL's proposal was in error, much less
7112illegal, arbitrary, dishonest, or fraudulent.
71172 / As an aside, if the instant procurement were as thoroughly
7129tainted by the consultants' participation as MIC contends, one
7138permissible (though not the only conceivable) remedy for that
7147would beironicallyto scuttle the procurement and start anew.
7155COPIES FURNISHED :
7158Joseph M. Goldstein, Esquire
7162Shutts & Bowen, LLP
7166Wachovia Center, Suite 2100
7170200 East Broward Boulevard
7174Fort Lauderdale, Florida 33301
7178Thomas Barnhart, Esquire
7181Office of the Attorney General
7186The Capitol, Plaza Level 01
7191Tallahassee, Florida 32399
7194James C. Myers, Agency Clerk
7199Department of Transportation
7202Hayden Burns Building
7205605 Suwannee Street, Mail Station 58
7211Tallahassee, Florida 32399-0450
7214Pamela Leslie, General Counsel
7218Department of Transportation
7221Hayden Burns Building
7224605 Suwannee Street, Mail Station 58
7230Tallahassee, Florida 32399-0450
7233Stephanie Kopelousos, Interim Secretary
7237Department of Transportation
7240Hayden Burns Building
7243605 Suwannee Street
7246Tallahassee, Florida 32399-0450
7249NOTICE OF RIGHT TO SUBMIT EXCEPTIONS
7255All parties have the right to submit written exceptions within 10
7266days from the date of this Recommended Order. Any exceptions to
7277this Recommended Order should be filed with the agency that will
7288issue the Final Order in this case.
- Date
- Proceedings
- PDF:
- Date: 01/18/2007
- Proceedings: Recommended Order cover letter identifying the hearing record referred to the Agency.
- PDF:
- Date: 01/18/2007
- Proceedings: Recommended Order (hearing held October 30 and 31, 2006). CASE CLOSED.
- PDF:
- Date: 12/12/2006
- Proceedings: Petitioner`s Notice of Filing Proposed Recommended Order; Petitioner`s Proposed Recommended Order filed.
- Date: 11/29/2006
- Proceedings: Transcript of Proceedings (October 31, 2006) filed.
- Date: 11/29/2006
- Proceedings: Transcript of Proceedings (October 30, 2006) filed.
- PDF:
- Date: 11/03/2006
- Proceedings: Letter to Judge Van Laningham from J. Goldstein enclosing Proposed Hearing Exhibits filed (exhibits not available for viewing).
- Date: 10/30/2006
- Proceedings: CASE STATUS: Hearing Held.
- PDF:
- Date: 09/12/2006
- Proceedings: Order Granting Continuance and Re-scheduling Hearing (hearing set for October 30 through November 2, 2006; 1:00 p.m.; Miami, FL).
- PDF:
- Date: 09/08/2006
- Proceedings: Response to Petitioner`s First Request for Production to Respondent filed.
- PDF:
- Date: 08/09/2006
- Proceedings: Notice of Taking Deposition Duces Tecum (of Kouroche Mohandes) filed.
- PDF:
- Date: 08/09/2006
- Proceedings: Notice of Taking Deposition Duces Tecum (of Steve Thompson) filed.
- PDF:
- Date: 06/09/2006
- Proceedings: Notice of Hearing (hearing set for September 25, 26, 28, and 29, 2006; 1:00 p.m.; Miami, FL).
Case Information
- Judge:
- JOHN G. VAN LANINGHAM
- Date Filed:
- 05/26/2006
- Date Assignment:
- 05/26/2006
- Last Docket Entry:
- 02/21/2007
- Location:
- Miami, Florida
- District:
- Southern
- Agency:
- ADOPTED IN TOTO
- Suffix:
- BID
Counsels
-
Tom Barnhart, Esquire
Address of Record -
Joseph M. Goldstein, Esquire
Address of Record -
Stephen K Tilbrook, Esquire
Address of Record