The Issue The issue to be resolved in this proceeding concerns whether the rejection of Petitioner Compaq Computer Corporation's (Compaq) submission in response to an invitation to negotiate #01/02-31 for the Child Support Enforcement (CSE) Automated Management Systems (CAMS) case management informational technology system is "clearly erroneous, contrary to competition, arbitrary or capricious." Embodied within that general issue are the considerations of whether the proposal by Compaq was responsive and whether the submittal by Compaq of a "Form 7105," with the absence of the vendor certification purportedly required on the front, or first page of that form, and the signature by the representative of Compaq in a signature area designated for an agency representative is a material irregularity.
Findings Of Fact The Petitioner, Compaq, is a Texas Corporation. It is authorized to do business in the State of Florida. The Respondent, DOR is a state agency charged with the responsibility of administering the Child Support Enforcement Program for the State of Florida in accordance with Section 20.21(h), Florida Statutes. The DOR issued an Invitation to Negotiate (ITN) for the CAMS compliance enforcement implementation on February 1, 2002. This procurement is designed to give the DOR a "state of the art system" that will meet all Federal and State regulations and policies for Child Support Enforcement, improve effectiveness of collections of child support and automate enforcement to the greatest extent possible. It will automate data processing and other decision support functions and allow rapid implementation of changes in regulatory requirements resulting from updated Federal and State regulation policies in Florida initiatives, including statutory ones. The ITN provided for a multi-phased process to be followed by negotiations with the selected proposers. The first phase of review consisted of a review of mandatory items. There followed evaluations of key proposal topics, management and technical and cost items. The top scoring proposers would then be invited to make oral presentations which would also be scored and which would then be followed by negotiations. The Department of Management Services has promulgated several forms with the designation "PUR" followed by a numerical reference. The numerical reference corresponds to the procurement methodology being used for the particular procurement at issue. For instance, the PUR 7105 is for invitations to negotiate. The other PUR forms identified in Rule 60A-1.002(7), Florida Administrative Code, are PUR 7028 for invitations to bid for commodities, PUR 7031 for invitations to bid for contractual services, PUR 7051 for requests for proposals for commodities, and PUR 7033 for requests for proposals for contractual services. Section 7.2.1.3 of the ITN advises proposers that the State of Florida invitation to negotiate acknowledgement form, PUR 7105 must be signed and included with the original of a proposer's package. It also notified the proposers that this form would be provided with the ITN on the DMS Vendor Bid System (the internet). "DMS" refers to the State of Florida Department of Management Services which maintains the Vendor Bid System referred to by the ITN. Form PUR 7105 is a purchasing form developed and produced by the Department of Management Services. When downloading the form PUR 7105 from the Vendor Bid System (VBS) on the internet, the first page containing the vendor information, certification and signature space, is not identified as being the first portion of form PUR 7105. The second and third pages, with the title "General Conditions" are the only ones denoted as being part of form PUR 7105. Compaq became aware that the procurement was going to proceed and began assembling a staff in order to be prepared to respond to the procurement and submit a proposal. Michael Angeley was designated project manager of the Global Services Division of Compaq to head the evaluation of the ITN for Compaq and to be in charge of preparation of Compaq's response to the ITN. As indicated above, the availability of the ITN was posted on the internet and made available on the VBS of the DMS. When accessing the ITN by computer, the applicable computer screen, which first becomes available, advises the viewer to "click here to view the bid specifications." If the viewer clicks "here," the first document which comes up on the screen is an unnumbered form, identified by its Universal Resource Locator (URL) line as follows: http://fen.state.fl.us.owa_vbs/owa/vbs_www.boiler_plate.show? boiler_plate_key_str=1129. At the bottom of the unidentified form, is the direction to "click here for additional required files." If the viewer clicks for additional required files at the bottom of the unidentified form, a document identified as "Downloadable Files for ITN-CAMS Compliance Enforcement Implementation" appears on the screen. The "Downloadable Files" screen provides a list of filed documents, and an indication of their type, with a check mark beside each file and a notation at the bottom of the page which states that a check mark "indicates required file." The first file document on the "Downloadable Files" screen is described as "General Conditions," with the "Type" indicated as PUR 7105, and a check mark indicating that it was a required file. If the viewer clicks to download the file designated as PUR 7105, a two-paged document entitled "General Conditions" appears in the Adobe Acrobat format with the statement at the bottom of each page that it is "PUR7105Rev.6/1/98." Michael Angeley, as Project Manager for Compaq, journeyed to Tallahassee to a pre-proposers conference. In response to statements by DOR representatives at the pre- proposers conference, Mr. Angeley went directly to Compaq's office in Tallahassee and downloaded the PUR 7105 form which was identified as such on the list of required files. In doing so, Mr. Angeley followed the procedure set forth in paragraphs 9-13 above. The Petitioner's Exhibit three, which the Respondent asserts is the first page of form PUR 7105, is not part of the "Downloadable Files for ITN-CAMS" which is listed as "required" on the VBS screen. Compaq did not download the first page or include it in its proposal response. Compaq perceived the downloaded document entitled "General Conditions" as the correct form based on its designation as such on the form and from the URL which reads: "http://fcn.state.fl.us/fcn/centers/purchase/vbs/ pur7105.pdf." After downloading the files indicated as required on the VBS, Mr. Angeley placed the entire document in a separate system file on his local network, and thereafter did not have to access the documents through the original process. Mr. Angeley, along with four other Compaq representatives, attended the mandatory pre-proposers conference that was held in Tallahassee on February 13, 2002. At the pre-proposers conference, which was attended by over 100 persons, questions which had been previously asked of DOR in writing, were answered in writing and a hand-out containing the answers was provided to each attendee. No additional questions were permitted at the pre-proposers conference. At that conference a DOR representative (Ms. Phillips) held up a document in front of the audience and advised the attendees that the form, identified by her as PUR 7105, needed to be included in the proposal. The document held up to the audience was not handed out, nor was it clearly visible to all attendees at the pre-proposers conference. Compaq representatives in attendance at the pre-proposers conference understood that form PUR 7105 was required to be included in the proposal package and, therefore, made no further inquiry regarding the form. Compaq's belief was that it was following the directions provided by DOR with regard to form PUR 7105, including those received at the pre-proposers conference and as contained in the ITN and the other computer accessible documents. That belief has been shown to reasonable under the circumstances. Compaq Vice President Kevin French signed the signature line on the only signature line available on the downloaded portion of form PUR 7105 in Compaq's possession. Mr. French had the authority to bind Compaq to the terms and conditions listed on the form. The signature of Mr. French on form PUR 7105 and in three other places in the submittal, including the transmittal letter, was intended by Compaq to and did bind it to the terms and conditions of the ITN. No unfair or competitive advantage was obtained by Compaq by signing the last page of form PUR 7105 by mistake, instead of the first page which it had not downloaded, consisting of the "Acknowledgement Form." The Evaluation Process The evaluation of proposals submitted in response to the ITN was designed to be a multi-stepped process. The evaluation was conducted by a review committee comprised of representatives from DOR's Purchasing Division and from the CSE Division as well as from DMS. The relevant portions of the evaluation process consist of the following steps: 8.1 Evaluation Process Proposers are responsible for thoroughly reviewing all ITN requirements to ensure that the proposal and the proposed approach are fully compliant with ITN requirements and approach are fully compliant with ITN requires and thereby avoid the possibility of being ruled non-compliant. FDOR will evaluate and score proposals with the following methodology that is more fully described in the following subsections. FDOR will: Perform Mandatory Items Compliance Evaluation to validate proposals against the mandatory items listed in Table 8-1. Proposals that do not respond to all mandatory items will be rejected and not considered further. Score Key Proposal Topics to ensure a proposal achieves the minimum acceptable score for these key topics before the effort is expended to fully evaluate it. Proposals that fail to achieve a minimally acceptable score for these key topics will be rejected and not considered further. (Emphasis supplied) The minimum score for the second step of the evaluation process was 150 points out of a possible 230. Section 8.1.1. of the ITN, "Table 8-1 (Selected Mandatory Items) lists 24 separate items in question format, with a reference to the ITN setting forth the location of the requirement. The Steering Committee selected the 24 items listed as mandatory but did not rank the items as to importance because all were considered mandatory. Section 2.3.8 of the ITN states as follows: 2.3.8 Rejection of Proposals FDOR will reject a proposal that FDOR deems to have a material defect. A material defect is any part of the proposed solution that violates a mandatory requirement and results in an unacceptable system or unacceptable risk. FDOR will reject proposals that fail to pass the Mandatory Items Compliance Evaluation (see Section 8.1.1). FDOR will reject proposals that include, in proposal Volume 3 (Contract), contract wording identified as mandatory by the proposer that is unacceptable to FDOR (see Section 7.4.1.2). FDOR will reject proposals that fail to achieve the minimum acceptable score for Key Proposal Topics (see Section 8.1.2). FDOR reserves the right to reject any and all proposals received if FDOR determines such action is in the best interest of the State of Florida or FDOR. Item 12 on Table 8-1 queries, "Did the proposer submit a PUR 7105 form signed by an authorized representative?", with a reference to ITN 7.2.1.3. Section 7.2.1.3 of the ITN states as follows: 7.2.1.3 State of Florida Invitation to Negotiate Acknowledgement Form, PUR 7105 The proposal shall include a form PUR 7105, completed and signed. The form will be provided with the ITN and the DMS Vendor Bid System. The original form PUR 7105 must be included with the Original/Master Copy (copy one) of Volume 1 of the proposal. Ms. Barbara Phillips, a purchasing specialist with DOR who was assigned to duties as an initial evaluator of the proposals, created a check list for the initial screening process and selected items 1, 2, 6, 8, 11, and 12, from the list of 24 "Mandatory Items" on Table 8-1. If a proposal received a negative ranking, indicated by an "N" as to one of the items on the check list, no further evaluation was done on the proposal. Seven proposals were submitted to DOR in response to the ITN. Compaq's proposal was the only proposal rejected as not responsive by DOR. Compaq's proposal was rejected on the basis of Compaq's failure to include a complete form PUR 7105 as part of its proposal and for signing the last page of form PUR 7105 on the line marked for the "Authorized Agency Signature" instead of on the first page. The confusing manner in which the information regarding form PUR 7105 was presented in the VBS substantially contributed to Compaq's inclusion of only two of the three pages of form PUR 7105 in its proposal. Once the decision was made to reject Compaq's proposal on the basis of form PUR 7105, evaluation of the proposal was stopped. Compaq's proposal was not scored in the second step of the evaluation process relating to Key Proposal Topics, therefore, it is not known whether it would have received the minimum score of 150 in order to proceed further in the process. Covansys Corporation submitted a proposal which was deemed responsive by DOR even though only the first unnumbered page of what DOR refers to as an "Acknowledgement Form" was included in its proposal and not the "General Conditions" which are listed as "Required" in the VBS system. Accenture, LLP submitted a proposal which was deemed responsive by DOR even though it made a notation on the Acknowledgement Form: "Subject to Accenture's Exceptions and Reservations in Volume 3, Section 1." The only difference between signing at the end of the two page "General Conditions" document listed in the VBS system as: "PUR FORM 7105" and not signing the "Acknowledgement Form" is that the vendor does not make a representation of non- collusion. However, the agency's representative made it clear that this provision is subject to negotiation and that the signature did not actually bind the vendor to that certification. When Accenture was deemed responsive and moved to the next stage of the evaluation process, the DOR reviewers did not check and did not know how many of the General Conditions were subject to Accenture's exceptions and reservations, nor the extent of the exceptions and reservations. In fact, they did not know whether or not Accenture agreed to any or all of the terms and conditions provided on form PUR 7105. Unisys submitted a proposal which was deemed responsive by DOR even though several Mandatory Items including Volumes 1 and 2 of the electronic copy (CD) of its proposal, as well as the Microsoft Project Plan, were not submitted. TIER submitted a proposal which was deemed responsive by DOR even though the reviewers found that Mandatory Items were not submitted in accordance with the directions in the ITN and despite the reviewers' determination that the documentation submitted from the Secretary of State's Office regarding its corporate status had expired. KPMG submitted a proposal which was deemed responsive by DOR even though the reviewers stated on the evaluation form that KPMG did not comply with certain Mandatory Items listed on Table 8-1.
Recommendation RECOMMENDED that a final order be entered by the State of Florida Department of Revenue deeming Compaq's proposal to be responsive to the Invitation to Negotiate and entitled to proceed to the next step in the evaluation process. DONE AND ENTERED this 23rd day of September, 2002, in Tallahassee, Leon County, Florida. P. MICHAEL RUFF Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 SUNCOM 278-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with Clerk of the Division of Administrative Hearings this 23rd day of September, 2002. COPIES FURNISHED: O. Earl Black, Esquire Department of Revenue Post Office Box 6668 Tallahassee, Florida 32399-0100 David W. Moye, Esquire Fowler, White, Gillen, Boggs, Villareal, and Banker, P.A. Post Office Box 11240 Tallahassee, Florida 32302 Bruce Hoffman, General Counsel Department of Revenue 204 Carlton Building Tallahassee, Florida 32399-0100 James Zingale, Executive Director Department of Revenue 104 Carlton Building Tallahassee, Florida 32399-0100
The Issue The issues to be resolved in this proceeding are delineated with particularity in the Joint Pre-hearing Stipulation executed by all parties; however, the issues generally are as follows: Whether Experior has standing to challenge the RFP Process. Whether Promissor was a qualified or responsive proposer. Whether Experior's cost proposal was entitled to the maximum points if Promissor's proposal is determined to be unqualified or non-responsive. Whether the scoring of the proposals by Evaluator three was affected by his bias or was so aberrant as to be unsupportable or illogical or in violation of the RFP. Whether DBPR's award of MBE/WBE preference points to Experior and PSI was inappropriate and should be eliminated. Whether Experior suffered an unfair competitive disadvantage.
Findings Of Fact The Department first decided to seek proposals for computer-based testing (CBT) services on March 29, 2002, when it issued RFP 01-02-001. General Condition Number Seventeen of that RFP stated that any material submitted in response to the Request for Proposal will become a public document pursuant to Section 119.07, including any material which a responding proposer might consider confidential or a trade secret. Any claim of confidentiality was waived upon submission. Experior never protested that General Condition Number Seventeen in that first RFP. The cost proposals submitted by all proposers in response to that first RFP became public record after the Department posted the notice of intent to award the contract to Experior on September 17, 2002. Promissor and PSI filed notices of intent to protest and formal written protests. In response to those protests, however, the Department decided to reject all proposals. Experior then challenged the rejection of all proposals by filing a notice of intent to protest on October 24, 2002, but ultimately withdrew that protest on October 31, 2002. Thereafter on January 13, 2003, the Department issued requests for proposal RFP 02-03-005 (the RFP), seeking proposals for the provision of computer-based testing services for several professions regulated by the Department. That is the RFP with which this case is concerned. Questions arose by potential vendors at a Pre-Proposal Conference, which was held on January 21, 2003. Representatives of the Department, Experior, Promissor, and PSI attended. Amendment One to the RFP grew out of that conference and was issued on February 3, 2003. This amendment contained the written questions and the Department's answers and the minutes of the Pre-Proposal Conference. The Department appointed certain employees to serve on the evaluation committee. The employees who were appointed were Karen Campbell-Everett; Steven Allen; Mollie Shepard; Alan Lewis; Milan Chepko (alternate) and Joe Muffoletto (alternate). Additionally, Department employee Valerie Highsmith was appointed to evaluate proposer references. Ultimately, alternate evaluator Joe Muffoletto replaced evaluator Steven Allen due to the death of Mr. Allen's father. Amendment One to the RFP then identified the evaluators and informed all proposers that the educational and professional background of each evaluator could be obtained by making a public records request. The protest filed by Experior alleges that evaluator Joe Muffoletto was not appropriately qualified. Experior did not file a challenge to the evaluators within 72 hours after they were identified in RFP Amendment One. Realistically this would have been difficult to do unless they already knew what the objections to qualifications might be, since Amendment One, in identifying the evaluators, informed the proposers that they would need to make a public records request to obtain the educational and professional background of each evaluator. In any event, preponderant evidence shows that Mr. Muffoletto's experience is sufficient to constitute "experience and knowledge in program areas and service requirements" for the CBT contract within the meaning of Section 287.057(17)(a) (which only requires that evaluators "collectively" have such experience). Mr. Muffoletto has a bachelor's degree, with a major in English and a minor in psychology. He holds a master of science degree in education and master of arts degree in multi- disciplinary studies and has completed the graduate level course called "assessment of learning outcomes" at Florida State University. Before working for DBPR, in 1996, he was a junior high and high school English teacher for 30 years. He has worked as a computer trainer for students taking the New York State Regents Competency Exam. In 1996-1997 he was an OPS test editor with DBPR and from 1997 to 1999 worked for the Florida Department of Education as a coordinator of test development, where he trained consultants on how to write test items, review test items, and amend test content outlines and blue prints. While in that position, he also wrote an RFP and developed a set of exams. Since 1999 he has been a psychometrician with DBPR and currently develops computed-based examinations for landscape architects and auctioneers and regular examinations for electrical contractors. Promissor, Experior and PSI each submitted responses to the second RFP. The technical proposals were distributed to members of the evaluation committee for review sometime after a standardization session for evaluators was conducted on February 11, 2003. The members of the evaluation committee separately conducted an analysis of each proposal and awarded points based on their review. Each evaluator submitted his or her completed technical evaluation guides or score sheets to Lyra Erath, who then forwarded the score sheets to the lead evaluator, Molly Shepard. The evaluation of the proposer references was completed by Valerie Highsmith and her score sheets for such evaluations were submitted to Bobby Paulk. On February 27, 2003, the Department opened the cost proposals, which reflected the following prices proposed per hour: Promissor: $9.00; Experior: $10.50; PSI: $11.35; and NCS Pearson: $14.75. The score for each cost proposal was calculated in accordance with a mathematical formula set out in the RFP. Promissor proposed the lowest cost and thus received the maximum cost score of 175 points. Experior received 150 points, PSI 138.77 points, and NCS Pearson 106.79 points. Upon concluding the evaluation process established by the RFP, Promissor's proposal was ranked first with 490.08 points out of a maximum available 555 points. PSI was second place, being awarded 461.40; Experior was awarded 440.03 points and NCS Pearson, 305.16 points. The bid/proposal tabulation was posted by the Department on March 12, 2003. Therein it indicated its intent to award the contract for CBT Services to Promissor. On March 17, 2003, Experior and PSI filed notices of intent to protest the intended award to Promissor. Experior thereafter timely filed a formal written protest, although PSI did not. ISSUES TO BE RESOLVED The Time Period for Contract Implementation Experior's protest alleges that the time period for contract implementation was allegedly "too aggressive" (short). The RFP however, repeatedly notified all proposers that they would waive any protest of the terms and specifications of the RFP unless they filed such protest within 72 hours of receiving notice of the specifications, as provided in Section 120.57(3). Similarly, RFP Amendment One informed the proposers that the RFP was amended to include "changes and additions" and that failure to file a protest within the time specified in Section 120.57(3) would constitute a wavier of Chapter 120 proceedings. RFP Section V, states "A. DBPR estimates that the contract for the RFP will be effective on or about March 17, 2003, and the testing services begin May 19, 2003." The 30- day periods the protest claims were "too aggressive" (i.e. too short) were specifically disclosed in RFP Section X concerning "scope of services." The time period of which Experior now complains was apparent on the face of the RFP. Indeed, when Experior's personnel first read the RFP, they had a concern that the time period might give Promissor a competitive advantage. At the Pre-Proposal Conference on January 21, 2003, Mark Caulfield of Experior even expressed concern that the 60 days allowed for implementation was a very aggressive schedule and asked the Department to reconsider that time period. The concern over the implementation schedule was documented in written questions which DBPR answered in Amendment One, telling all proposers that the implementation schedule was fair, in its view, and would not be changed. Experior did not protest the RFP's implementation time period within 72 hours of first reading the RFP and never filed a protest to any term, condition or specification of RFP Amendment One, including the Department's notice that it felt that the implementation schedule was fair and that it would not be amended. Thus, any challenge to the implementation schedule was waived. Even had Experior not waived its challenge to the implementation schedule, there is no persuasive evidence that the schedule would give Promissor an unfair competitive advantage over Experior and PSI. The DBPR tests are already finalized and would simply have been transferred to a new vendor if a new vendor had been awarded the CBT Services Contract. Experior failed to adduce persuasive evidence to show that any proposer was advantaged or disadvantaged by the implementation schedule which applied to all proposers. Evaluation of the MWBE Submittals RFP Section XIV.Q. encouraged minority and women-owned businesses (MWBE) to provide work goods, or services associated with services contemplated by the RFP. Proposers were to be awarded additional points for committing to use MWBEs, based on the percentage of the business under the contract the MWBE would perform. Experior, Promissor and PSI each proposed to use MWBEs to supply goods or services needed to perform the CBT contract. Promissor indicated that it would use one MWBE for 30 percent of the contract value. Resultingly, the Department awarded Promissor 16.5 MWBE preference points (30 percent x 55 maximum points). Experior presented no persuasive evidence showing how the Department interpreted and applied the MWBE provisions of the RFP or showing that the Department acted in excess of its authority in determining the award of MWBE points, as described in Amendment One. Experior offered no evidence concerning whether the Department considered or applied the "two subcontractor" limitation in RFP Section VI.5 ("no more than two subcontractors may be used") when it evaluated the Experior and PSI MWBE proposals, nor how it applied that limitation. Experior and PSI both indicated they would use three MWBE vendors. Experior proposed to use JR Printers (Printing Services); Colamco, Inc. (computer equipment for testing centers); and Workplace Solutions, Inc. (furniture for testing centers). (Furniture is a commodity, not a service.) PSI proposed to use Victoria and Associates (staffing services); Franklin's Printing (printing/mailing services); and National Relocation Services, Inc. (furniture, computers, delivery and installation [commodities, not services]). Based on the proposals, the Department awarded Experior 7.15 points and awarded PSI 17.48 points. Although Experior claims that it and PSI each exceeded the two subcontractor limitation by proposing to use three MWBEs, RFP Section XIV.Q. did not specifically require that proposed MWBEs be subcontractors, but rather only required that MWBEs be utilized by the primary vendor (contractor) to provide work, goods or services. Thus a vendor of goods or a supplier of services could qualify as an MWBE (and, implicitly, not necessarily be a subcontractor). Experior did not prove that any of the MWBEs proposed by PSI or Experior were actually subcontractors on an ongoing basis. The parties stipulated that the companies that each proposed to use were vendors. Moreover, when questioned about the provisions of Section VI regarding sub- contracting of services under the RFP, Jerome Andrews, chief of purchasing and human resources, differentiated the purchase of services from the purchase of commodities as being defined by statute. (See Sections 287.012(4) and 287.012(7).) Experior did not explain or offer persuasive evidence relating to its allegation that PSI's proposal for MWBE services was misleading. Experior did not show that PSI's MWBE proposal did not conform to the RFP requirements or, if there were a defect, how many points, if any, should be subtracted from PSI's total. Moreover, to the extent that Experior claims that the proposal was defective because PSI's proposed suppliers would not provide services over the course of the entire contract, Experior's proposal suffers the same defect, as Experior's proposal admits that "[c]omputer equipment and furniture services will be performed during the implementation phase of the contract." Thus, if PSI's MWBE point award had to be reduced, so would Experior's. Experior fail to carry its burden to show any error in the scoring of the PSI MWBE proposal. It did not establish that these vendors were subcontractors and thus did not establish that the relevant vendors were of a number to exceed the subcontractor limitation in the RFP. It did not persuasively establish that such would have been a material defect, if it had been exceeded. Completion of Evaluation Sheets Some of the RFP's evaluation criteria identified the number of points available and state that such points would be "awarded as a whole and not broken down by sub-sections." In contrast, the remainder of the evaluation criteria simply stated that a specific number of points was available for each specified criterion. In each instance where the evaluation criteria stated that points are "awarded as a whole and not broken down by subsections," the corresponding section of the RFP was broken down into two or more subsections. In each instance where the evaluation criteria simply listed the number of points available, the corresponding section of the RFP was not broken down into subsections. Experior alleged that the evaluators did not properly score Experior's proposal in instances where the evaluation sheet indicated "points are to be awarded as a whole and not broken down by subsections." Experior offered no proof regarding how the Department interpreted that provision or the manner in which the scoring was actually conducted, however. The score sheets reflect that the evaluators actually did award points "as a whole," not broken down by subsections, for those evaluation criteria where that was required. The record does not support any finding that the Department or its evaluators violated the requirements of the RFP, Department policy or controlling law and rules in this regard. Issue of Bias on the Part of Evaluator Three Experior contends that Evaluator Three, Mr. Muffoletto, was biased against Experior. The persuasive evidence does not support that allegation. During his employment with the Department, Mr. Muffoletto interacted with Experior on one occasion regarding reciprocity of an out-of-state examination. This experience left him with the impression that Experior was "proprietary" because it was protective of the content of its examinations. The evidence did not show he had any other impressions, positive or negative, concerning Experior or misgivings about Experior being selected in the first RFP. The mere fact that his total score for Experior was lower than those awarded by other evaluators does not establish bias or irrationality in scoring. The evidence shows that Mr. Muffoletto scored the proposals in a rational manner. He appeared to evaluate criteria comparatively and gave a proposer more points if that proposer was more convincing than another on a particular criteria or point of evaluation. He gave lower scores when the proposer simply copied the text of the RFP and then stated that the proposer would meet or exceed the criteria; in accordance with instructions that evaluators could give lower scores in such cases, so long as the scoring was consistent between proposals. Mr. Muffoletto gave higher scores when the proposers gave more individualized responses, provided more thorough statistics and ways to interpret those statistics, gave numerous specific examples and had a more attractive presentation. Even if Mr. Muffoletto had been biased, it has not been persuasively shown that such would have a material impact on the outcome of the evaluation. If the scores of Evaluator Three were completely eliminated for both PSI and Experior, which is not justified, PSI's point total would be 459.12 and Experior's point total would be 453.54. If Evaluator Three were deemed to give Experior scores equivalent to the highest scores awarded to Experior by any other evaluator, PSI's total would be 461.42 and Experior's point total would be 458.87. Even if Evaluator Three had given Experior the maximum points for each criterion, PSI's point total would have been 461.42 and Experior's point total would have 461.12. Issue of Prior Knowledge of Experior's Prior Cost Proposal Experior contends that Promissor's knowledge of Experior's cost proposal submitted in response to the first RFP in 2002 gave Promissor an unfair competitive advantage. Experior waived that challenge, however, when it withdrew its protest to the rejection of all bids submitted in response to the first RFP. Experior knew when it filed and withdrew its protest to the first RFP decision that all cost proposals had become public record and so it was incumbent on Experior to have challenged the issuance of a second RFP, if it had a legal and factual basis to do so. At the latest, Experior should have challenged the second RFP specifications when issued (within 72 hours) as Experior had already obtained the other proposers' cost proposals and so it knew then that the prior cost proposals were available to all for review. Even if Experior had not waived that challenge, the evidence does not support a finding that Promissor gained any competitive advantage. Although Experior attempted to show, through the testimony of Mark Caulfield, that Promissor could not perform the CBT Services Contract at a profit at the $9.00 per hour price it proposed, Mr. Caulfield actually testified that it would be possible for a company to perform the services for $9.00 per hour, and he did not know what Promissor's actual costs were. Moreover, there is no persuasive evidence that Experior's prior cost proposal played any role in Promissor's determination of its bid for the second RFP or, if it did, that such consideration would have violated any provision of the RFP, governing statutes or rules or Department policies, under the prevailing circumstances, if it had occurred. Alleged Improper Scoring of Experior's Proposal with Respect to Criterion VII.A. Experior alleged that Evaluator One should have awarded 15 points instead 11 points for Experior's proposal format, criterion VII.A., but Experior did not offer the testimony of Evaluator One or any other evidence supporting that allegation. Experior failed to carry its burden of showing that the award of 11 points to Experior for criterion VII.A., was irrational or violated the requirements of the RFP or controlling policies, law or rules of the Department. Even if Evaluator One had awarded 15 points for that criterion, Experior admitted it would have no material impact on the outcome of the procurement, given the more than 21 point advantage PSI enjoyed over Experior. Responsiveness and Qualification The preponderant evidence does not establish that Experior was entitled to but did not receive the additional 21.38 points that it would have to earn to score higher than PSI and move into second place. Experior did not establish error in the evaluation or scoring of its proposal or PSI's proposal that alone, or collectively, would be sufficient for Experior to overtake PSI. As a result, Experior could only prove its standing ahead of PSI by having the Promissor proposal disqualified, which would move it to the first-ranked position because of accession of the full 175 points for having what, in that event, would be the lowest cost proposal. Experior's objection to the Promissor proposal is not meritorious. Its protest alleges that "because Promissor will [allegedly] subcontract for services representing more than 33 percent of contract value, Promissor is disqualified from submitting its proposal and its proposal must be stricken from consideration." Experior did not allege any error in the scoring of Promissor's proposal and so Promissor's highest score cannot be changed. Indeed, even if Experior were awarded the maximum technical score of 325 points, Experior's score would be 482.15 points, still less than Promissor's score of 490.08 points. Experior, as a practical matter, cannot earn enough points because of the disparity in final cost proposal scores to overtake Promissor, unless it can prove Promissor should be disqualified. Experior's proof did not amount to preponderant, persuasive evidence that the Department erred in determining that Promissor's proposal was responsive and that Promissor was a qualified proposer. The Department did an initial review of the proposals to determine if they were responsive to all mandatory requirements, and any proposer determined non-responsive would have been excluded at that point. Promissor's proposal contained all required information in the required format and was deemed responsive. The preponderant evidence shows that the Department's determination that Promissor was responsive and qualified comported with the requirements of the RFP and controlling policy, rules and law. Promissor expressly stated that it would comply with the RFP's subcontracting guidelines upon performing the contract wherein it stated "Promissor agrees and commits to meet the requirement of the RFP." Promissor's proposal stated its intent to subcontract less than 33 percent of the contract value, and that was all that was required for the proposal to be responsive. There is nothing in the Promissor proposal that indicated that Promissor would not comply with the subcontracting guidelines. Experior's entire challenge to the Promissor proposal is based on the contention that Promissor intended to use a subcontractor to provide call center services under the Florida contract but did not say so in its proposal. The Promissor proposal actually stated that Promissor would use its "proprietary scheduling system" or "proprietary reservation system" to service the Department's contract as it was currently doing, not that it would use any particular call center. These representations appear to be true, as Promissor's "scheduling system" or "reservation system" (the proprietary software Promissor uses to take reservations) that it said it would use for the new Florida contract is the same system used under the prior contact with the Department. Ordinarily, whether or not Promissor would actually comply with the subcontractor guidelines could not be determined until Promissor actually performs the contract. It is an issue of contract compliance and not responsiveness or qualification. Here the evidence shows that Promissor was in compliance with the 33 percent maximum subcontracting requirement before the originally scheduled contract implementation date. Since Promissor wished to obtain the maximum points for minority participation, Promissor decided to subcontract to the maximum possible extent with an MWBE. In doing so, Promissor wanted to assure that the use of Thompson Direct, Inc., for call center services did not make it exceed the 33 percent subcontractor standard. Thus, Promissor decided, before it submitted its proposal, to perform the call center services from one of its three regional centers and this decision was communicated internally before Promissor prepared its proposal. Promissor initially intended to perform the call center services from its regional offices in Atlanta, Georgia. In order to implement that decision, senior executives of Promissor, including its president, toured that office in early March, before the Department posted its notice of intent to award to Promissor. After the notice of award was posted on March 12, 2003, Promissor promptly posted an employment advertisement on its website seeking persons to act as call center representatives to service the Florida contract from the Atlanta office. That advertisement was posted on March 14, 2003, a day before Experior filed its notice of intent to protest. In early to mid-April, the manager of the Georgia regional office prepared a project plan that revealed that the Georgia regional office might not be ready to perform call center services by the May 20th contract implementation date. Promissor then decided to use its Maryland regional office to perform the call center services. Regardless of the location of the call center, the scheduling system used by Promissor would be the same as under the prior contract and the same as Promissor promised in its proposal. The Scranton call center and the three regional offices use the same proprietary scheduling system provided by Promissor and run from servers located at Promissor's headquarters in Bala Cynwyd, Pennsylvania. Even at the Scranton call center that was previously used, Promissor trained all of the employees, who handle calls only for Promissor, wrote the scripts for their use and provided the proprietary scheduling software. The Maryland call center was actually accepting all calls for the Florida programs to be serviced pursuant to the RFP by May 19th, before the May 20th contract implementation date. Since the call center services were actually being provided by Promissor's Maryland regional office before the contract implementation date, Experior's claim that Promissor would provide those services through a subcontractor is not supported by preponderant evidence. Allegations that Promissor Made Misrepresentations Regarding Subcontractors In light of Promissor's actual provision of call center services from its regional office before the contract implementation date, Experior's contention that alleged misrepresentations occurred in the Promissor proposal are without merit. Even if Promissor had not actually performed, however, Experior failed to prove that Promissor made any misrepresentations or was unqualified. In support of its claim that Promissor was unqualified, Experior introduced into evidence three proposals that Promissor or ASI (a corporate predecessor to Promissor) had submitted to agencies in other states in the past three years. Experior argues that Promissor/ASI made misrepresentations in the other proposals and, therefore, Promissor made misrepresentations in the proposal at issue in this proceeding. Its basis for alleging that Promissor made misrepresentations in the Florida proposal at issue is its contention that Promissor/ASI made misrepresentations in other proposals to other states. No evidence was offered that Promissor had made a misrepresentation to the Department as to this RFP, however. In light of Promissor's actual performance in accordance with its proposal and the RFP requirements, the proposals from the other states have little relevance. Experior did not prove that Promissor made misrepresentations in the other proposals, particularly when considering the timing of those proposals and Promissor's corporate history. Promissor's corporate history must be considered in evaluating the claim of misrepresentation to the other state agencies in other states. In 1995, Assessment Systems, Inc., or "ASI," was acquired by Harcourt Brace Publishers. In June of 2001, ASI was sold with a number of other Harcourt companies, including a company called Harcourt Learning Direct, to the Thompson corporation. Harcourt Learning Direct was re-named Thompson Education Direct. Soon after, the federal government required, for anti-trust reasons, that Thompson divest itself of ASI. Accordingly, ASI was acquired by Houghton Mifflin Publishers in December 2001, and its name was later changed to Promissor. Up until December 2001, the entity now known as Promissor and the entity now known as Thompson Education Direct were corporate affiliates under the same corporate umbrella. The Kansas Proposal Experior's Exhibit five was ASI's Proposal for Agent Licensing Examination Services for the Kansas Insurance Department dated May 8, 2000. A letter that accompanied the proposal stated that ASI would not engage a subcontractor for examination development or administration services. Mark Caulfield testified that he did not know whether or not what was said in this letter was true on the date it was written. He testified that he did not know if ASI was using any subcontractors or any outside contractors for any purpose in May of 2000. In fact, as of May 2000, ASI did not subcontract for any call center services; at the time that the letter was written, all of the representations in the letter were true. ASI was awarded the Kansas contract and Experior did not protest. Experior did not offer any evidence related to the requirements in the Kansas RFP and is not aware of any issues between Kansas and Promissor regarding the contract. There is no evidence that the Kansas request for proposals had any subcontracting limitations in it. The proposal that ASI submitted to Kansas in May 2000 listed a phone number for ASI's call center. In preparation for the hearing, witness Mark Caulfield called that phone number and claimed that a person answered the phone "Promissor," and said she was located in Scranton, Pennsylvania. Experior did not show that the person that answered the phone was an employee of Promissor. Whether or not the person who answered the phone in that example was or was not an employee of Promissor and could or could not bind Promissor with any statement as a party admission, is beside the point that it has not been shown who would have answered the phone in May 2000, or where they would have been located, as to whether or not that person was the employee of Promissor or its immediate corporate predecessor in interest or whether that person was employed by some subcontractor. That is immaterial, however, in the face of the fact that it has not been proven that the Kansas request for proposals had any subcontracting limitations in the first place and, therefore, no misrepresentation in the Kansas situation has been proven on the part of Promissor. The Maine Proposal Experior's Exhibit seven is ASI's proposal to provide real estate examination administration and related services for the Maine Department of Professional Regulation and is dated August 1, 2001. As of August 1, 2001, ASI did not subcontract for call center services. On pages 2-10 of the Maine proposal, there is a reference to ASI having an extensive network of program-specific, toll-free telephone lines and program-dedicated customer care representatives. This statement was shown to be accurate and was an accurate statement when made on August 1, 2001. The statement refers to the monitoring of the reservation process done by ASI management. Experior admitted that it had no reason to believe that in August of 2001, ASI did not have an extensive network or program-specific toll-free telephone lines and program-dedicated customer care representatives, and Experior did not prove that to be currently untrue. Experior's Exhibit eight is Promissor's Real Estate Candidate handbook regarding the Maine procurement dated April 2003. As of April 2003, the statements made in the handbook were accurate and correct. The handbook listed on page 11 a customer care phone number of 877-543-5220. Experior provided no evidence as to the location where that phone number rang in April of 2003. Experior did not show persuasive evidence regarding the requirements in the Maine RFP and there is no evidence that the Maine RFP had any subcontracting limitations as are in question in the instant case. The Oklahoma Proposal Experior's Exhibit nine was Promissor's response to Bid No. N031354 for License Testing Services for the Oklahoma Insurance Department. It is dated December 18, 2002. Promissor did not state in the proposal that it would not use subcontractors. There is no need to reference subcontractors in the Oklahoma proposal as the Oklahoma RFP did not contain subcontracting limitations. Oklahoma has approved the manner in which Promissor is performing under that contract and Experior did not establish that the statements in Promissor's proposal were false when made or now. The Texas Proposal Experior's Exhibit twelve is Promissor's press release titled "Texas Selects Promissor as Exclusive Provider for Insurance License Testing," dated October 1, 2002, in which Promissor referred to "the Promissor Call Center." Experior did not establish that Texas was not served by a Promissor call center or that Promissor was not performing in the manner its Texas proposal promised. In fact, Texas has approved Promissor's performance under the Texas contract. Even if the proposals Promissor offered had stated that Promissor would provide call center services through a specified entity (which they did not do), and then Promissor later performed such services through another entity, such evidence would be insufficient to prove that Promissor would not comply with the Florida RFP's subcontracting guidelines, especially given Promissor's actual performance in accordance with its proposal. Experior did not establish with preponderant evidence a "routine business practice" of Promissor to make misleading or false promises in proposals to evade subcontracting guidelines. There is no evidence in any of the four states concerning which Experior provided evidence, that they had any subcontracting limitation in their RFPs. The evidence showed that the statements in each of these proposals were undoubtedly accurate at the time they were made; to the extent that the provision of call center services differs from what was promised (although the evidence does not establish that), such difference is explained by the changes in corporate structures that have occurred since the proposals were submitted. Additionally, the evidence established that Promissor has submitted between 70 and 120 proposals since the beginning of 2000 across the nation. The documents relating only to other proposals to other states that were not even proved to have requirements similar to Florida's are insufficient to establish that Promissor had a "routine" practice of making misleading promises about its call center services. Accordingly, the Petitioner has not offered preponderant, persuasive evidence that Promissor is unqualified as a proposer.
Recommendation Having considered the foregoing Findings of Fact, Conclusions of Law, the evidence of record, the candor and demeanor of the witnesses and the pleadings and arguments of the parties, it is, therefore, RECOMMENDED that a final order be entered by the Department of Business and Professional Regulation denying the Petition and approving the intended award of the contract to Promissor, Inc. DONE AND ENTERED this 22nd day of August, 2003, in Tallahassee, Leon County, Florida. S P. MICHAEL RUFF Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 SUNCOM 278-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with Clerk of the Division of Administrative Hearings this 22nd day of August, 2003. COPIES FURNISHED: Wendy Russell Weiner, Esquire Mang Law Firm, P.A. 660 East Jefferson Street Tallahassee, Florida 32301 Joseph M. Helton, Jr., Esquire Michael J. Wheeler, Esquire Department of Business and Professional Regulation 1940 North Monroe Street Tallahassee, Florida 32399-2022 Paul R. Ezatoff, Esquire Katz, Kutter, Alderman & Bryant, P.A. 106 East College Avenue, Suite 1200 Tallahassee, Florida 32301 Michael P. Donaldson, Esquire Carlton Fields Law Firm 215 South Monroe Street, Suite 500 Tallahassee, Florida 32301 Hardy L. Roberts, III, General Counsel Department of Business and Professional Regulation 1940 North Monroe Street Tallahassee, Florida 32399-2202
The Issue This is a bid protest proceeding pursuant to Section 120.53, Florida Statutes. The basic issue in this case is whether the Petitioner's bid was responsive.
Findings Of Fact 1 . By Request For Proposal Number RFP-DOT-Ps-89-6000, the Department solicited proposals for the performance of work related to the identification and assessment of hazardous waste. The subject request for proposal document was available from December 4, 1989, until the closing date of January 4, 1990. The Petitioner requested a copy of the subject request for proposal and it was duly sent by the Department via certified bail addressed as follows: Enviro-Haz of Florida, Inc., 825 Parkway Street, Suite 14, Jupiter, Florida. The U.S. Postal Service receipt for that delivery was signed by Ms. Kerry Brougham. Ms. Brougham is employed by Force Equipment, located at 825 Parkway Street, Suite 13, Jupiter, Florida. The copy of the subject request for proposal received by Ms. Brougham was ultimately delivered to the Petitioner in time for the Petitioner to file a timely proposal. Ms. Brougham has a friendly relationship with the people at the Petitioner's office and routinely accepts mail addressed to the Petitioner when the mail arrives at a time when the Petitioner's office is closed. Ms. Brougham's regular practice is to place the Petitioner's mail on a separate place on her desk and to then carry the mail to the Petitioner's office when someone returns to that office. When delivering mail to the Petitioner's office, Ms. Brougham either hands it to the receptionist or places it on the receptionist's desk in the Petitioner's office. The subject request for proposal includes the following language under the caption "Responsiveness of Proposals:" All proposals must be in writing. A responsive proposal is an offer to perform, without condition or exception, the scope of services called for in this Request for Proposal. Non-responsive proposals shall not be considered. Proposals may be rejected if found to be irregular or not in conformance with the requirements and instructions herein contained. A proposal may be found to be irregular or non-responsive by reasons, including, but not limited to, failure to utilize or complete prescribed forms, conditional proposals, incomplete proposals, indefinite or ambiguous proposals, improper or undated signatures. (Emphasis added). The subject request for proposal contains several forms each potential vendor was required to use in the submission of its bid. Among these forms was "Form A," consisting of six pages on which each potential vendor was asked to provide extensive pricing information. It is also clear from the subject request for proposal that the Department sought both a technical proposal and a price proposal, the two to be separately submitted. For purposes of evaluation, 90 potential points were assigned to the technical proposals and 10 potential points were assigned to the price proposals. On December 20, 1989, a pre-bid conference was held. Mr. Coleman attended the pre-bid conference on behalf of the Petitioner. All potential vendors at the pre-bid conference were given a copy of Addendum No. 1 to the subject request for proposal. (There is no dispute in this case regarding Addendum No. 1.) Following the pre-bid conference, the Department distributed Addendum No. 2 to all potential vendors. The distribution was accomplished by certified mail. A copy of Addendum No. 2 was mailed to the Petitioner. The envelope containing Addendum No. 2 was received by Ms. Brougham at the office next door to the Petitioner's office. As with the earlier mail sent to the Petitioner by the Department, Ms. Brougham signed the U.S. Postal Service receipt for the mail containing Addendum No. 2 addressed to the Petitioner. Ms. Brougham delivered the mail containing Addendum No. 2 to the Petitioner's office. 1/ Addendum No. 2 instructed potential vendors to remove the six pages comprising "Form A" in the original request for proposal and to insert a new "Form A" consisting of six revised pages. The new "Form A" requested additional pricing information that was not requested on the original "Form A." Specifically, the new "Form A" requested pricing information for the years 1990, 1991, and 1992, while the original "Form A" requested pricing information for only the first year. When the Petitioner submitted its proposal, it used the original "Form A," rather than the revised "Form A" that was part of Addendum No. 2. The Petitioner's proposal did not include the pricing information for the years 1991 and 1992 required by the revised "Form A." The Department received five proposals in response to the subject request for proposal. When Department personnel evaluated the five technical proposals, the Petitioner's proposal was ranked fifth. When Department personnel evaluated the five price proposals, the Petitioner's proposal was deemed to be non- responsive due to the Petitioner's failure to provide pricing information for the years 1991 and 1992 as required by revised "Form A."
Recommendation For all of the foregoing reasons, it is RECOMMENDED that the Department of Transportation issue a final order in this case concluding that the Petitioner's proposal is non-responsive and dismissing the Petitioner's formal written protest. DONE AND ENTERED in Tallahassee, Leon County, Florida, this 27th day of March 1990. MICHAEL M. PARRISH Hearing Officer Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-1550 (904) 488-9675 Filed with the Clerk of the Division of Administrative Hearings this 27th day of March, 1990.
The Issue The issue in this case is whether Respondent's intended award of a contract to Intervenor pursuant to Request for Proposals No. 10-DC-8200 is contrary to Respondent's governing statutes, Respondent's rules and policies, and the specifications of the Request for Proposals.
Findings Of Fact The State of Florida has, by legislative enactment, developed programs to electronically supervise offenders sentenced under a community control alternative to prison, and to supervise, register, and monitor designated sexual offenders and predators under the Jessica Lunsford Act. The Department of Corrections is the agency charged with the implementation of the electronic monitoring program, and to ensure that probation officers and other community supervision personnel have access to offender monitoring data. Pro Tech and BI are both well-recognized and established providers of electronic monitoring devices and monitoring and reporting services to federal, state, and local law enforcement and correctional agencies in Florida and across the United States. Pro-Tech is the incumbent vendor to the Department for electronic monitoring services. RFP 10-DC-8200 On August 30, 2010, the Department issued RFP 10-DC- 8200, the purpose of which was to select a contractor to provide active Global Positioning Satellite (GPS) electronic monitoring services for supervision of offenders sentenced under a community control alternative to prison, and to monitor designated sexual offenders and predators under the Jessica Lunsford Act. As of June 30, 2010, the Department was utilizing approximately 2,538 active GPS units to monitor offenders. The Department projected that within three years, as many as 3,015 offenders would be on active GPS monitoring. The scope of work for the contract was detailed in section 3 of the RFP. Briefly, the winning vendor is expected to ?provide active [GPS] services 24 hours a day, 7 days a week, which shall include a monitoring system that is capable of being accessed through a secure internet connection and fully supported by a secure database for transactional records.? Provisions of the RFP that are material to this proceeding include, by section number, the following (all emphasis is in the original): 1.13 Mandatory Responsiveness Requirements: Terms, conditions or requirements that must be met by the proposer to be responsive to this RFP. The responsiveness requirements are mandatory. Failure to meet the responsiveness requirements will cause rejection of a proposal. Any proposal rejected for failure to meet mandatory responsiveness requirements will not be evaluated. Material Deviations: The Department has established certain requirements with respect to proposals to be submitted by Proposers. The use of shall, must or will (except to indicate simple futurity) in this RFP indicates a requirement or condition which may not be waived by the Department except where any deviation therefore is not material. A deviation is material if, in the Department's sole discretion, the deficient response is not in substantial accord with this RFP's requirements, provides an advantage to one Proposer over other Proposers, or has a potentially significant effect on the quantity or quality of items or services proposed, or on the cost to the Department. Material deviations cannot be waived and shall be the basis for rejection of a response. Because this is an RFP, the Department will apply this definition liberally in reviewing responses in regard to service delivery. Minor Irregularity: A variation from the RFP terms and conditions which does not affect the price proposed or gives the proposer an advantage or benefit not enjoyed by the other proposers or does not adversely impact the interests of the Department. 5.2.9 The Proposer shall provide for both the Contractor and Contractor‘s personnel, copies of any and all documents regarding complaints filed, investigations made, warning letters or inspection reports issued, or any disciplinary action imposed by Federal or State oversight agencies within the past five (5) years. Narrative/Record of Past Experience As indicated in Section 2.2 and Attachment 1, it is a mandatory responsiveness requirement that the Proposer has at least three (3) years of business/corporate experience within the last five (5) years relevant to providing electronic monitoring services and equipment similar to the services described in this RFP, to correctional, criminal justice or law enforcement agencies. Details of the Proposer‘s experience that meet this requirement shall be provided in narrative form and in sufficient detail so that the Department is able to judge its complexity and relevance. Specifically include: provide a description of past years‘ experience providing electronic monitoring equipment and services. provide a description of past experience and the specific length of time providing Active GPS services (as identified in this RFP). identify all current and/or past (or within three (3) years) federal, state or government contracts for the provision of electronic monitoring services, and the number of active GPS units utilized for each. provide a narrative summary of contract performance in the above-identified contracts, including any major adverse findings. provide the name and telephone number and address for the specified federal, state, or government contract manager. provide a summary of any exemplary or qualitative findings, recommendations, or other validations, demonstrating operational experience. (i.e., specialized accreditation, grant awards, etc.). The proposer shall provide a detailed description of the General Equipment specifications that meets or exceeds all requirements in Section 3.7.2 and specifically: provide manufacturer‘s specifications and literature on all equipment proposed, including equipment which is acquired from any other source than the proposer; describe the process utilized to notify the Department and/or the offender when a low battery condition exists in any component of the equipment (transmitter or receiver dialer); describe and list the tools necessary for installation of any of the monitoring unit equipment; and provide copies of required licensing by the Federal Communications Commission for the equipment proposed. The proposer shall provide a detailed description of the Contractor‘s method and approach for meeting or exceeding all Monitoring Center requirements in Section 3.13, and specifically: provide a copy of the staffing plan for monitoring services twenty four (24) hours a day, seven (7) days a week, including holidays; and provide a copy of the Disaster Recovery plan. The proposer shall provide a detailed description of the approach to meeting or exceeding all Training requirements in Section 3.16, and specifically: provide a description of the method(s) for securely sizing and installing the transmitter securely to offenders; provide a copy of the training curriculum; and provide a copy of proposed course/instructor evaluation form. Please note - final evaluation form to be approved by Contract Manager and/or designee. As part of the RFP process, each interested vendor was allowed to submit questions regarding the terms of the RFP, and the services being sought. The Department responded to each of the 72 questions submitted. On November 2, 2010, the responses, along with revised RFP pages resulting therefrom, were provided to each prospective vendor as RFP #10-DC-8200 Addendum #1. Among the questions for which the Department provided answers were the following: Question #11: Sections 5.3.2.3 & 5.3.2.4 on Page 38 requires that we: ?identify all current and/or past (or within (3) years) federal, state or government contracts for the provisions of electronic monitoring services, . . . .? And that we ?provide a narrative summary of contract performance in the above identified contracts,. . .? In the case of Pro Tech, this would amount to more than a hundred contracts resulting in a voluminous response. Perhaps a more reasonable requirement would be to provide the information for our 10 largest or 10 most similar contracts. Answer #11: These requirements remain as stated in the RFP. Question #16:5.3.2. Narrative/Record of Past Experience identify all current and/or past (or within three (3) years) federal, state or government contracts for the provision of electronic monitoring services, and the number of active GPS units utilized for each. Question: Since it is feasible that Proposers could have several hundred current/past contracts, will Florida Department of Corrections consider revising the requirement to be “Provide the total number of current and/or past (or within 3 years) federal, state or government contracts?” Answer #16: This requirement remains as stated in the RFP. Question #17: provide a narrative summary of contract performance in the above-identified contracts, including any major adverse findings. Question: Since it is feasible that Proposers could have several hundred current/past contracts, will Florida Department of Corrections consider revising the requirement to be “Provide a performance summary of all contracts past/present?” Answer #17: This requirement remains as stated in the RFP. Question #28: Should respondents view ?shall? and ?must? language as mandatory requirements? Answer #28: This question is confusing different terms. See Section 1.13 that defines ?Mandatory Responsiveness Requirements?. See Section 1.15 that defines ?Material Deviations? which explains the terms ?shall and must?, and should not be confused with Section 5.1 Mandatory Responsive Requirements/ Fatal Criteria. Each proposed vendor signed an Addendum Acknowledgement Form for RFP #10-DC-8200 Addendum #1, and included it as part of its proposal. By signing and submitting the Addendum Acknowledgement Form, the vendors understood that the changes reflected in the Addendum ?are applicable to the original specifications of the above-referenced RFP? and that ?this addendum now becomes a part of the original RFP.? No prospective vendor filed a protest of any of the terms, conditions, or specifications of the RFP or Addendum #1. Proposals in Response to the RFP Proposals were submitted on November 22, 2010, by Pro Tech and BI, as well as five other electronic monitoring vendors, G4S Justice Services, LLC, iSecureTrac Corporation, Satellite Tracking of People, LLC, SecureAlert, and SOS International. BI proposed using its ExacuTrack One monitoring device to monitor offenders in Florida. The ExacuTrack One is a single piece device that is affixed to the offender‘s ankle. The unit contains a GPS signal receiver, a transmitter, cellular capability to transmit data to the monitoring center, a speaker for transmitting warnings, a device for the offender to transmit acknowledgement signals, and a rechargeable battery. The ExacuTrack One device meets the specifications of the RFP. When offenders go into prohibited areas, or when tracking capabilities are interrupted, either through shielding of the GPS signal or unauthorized tampering with the device, an alert is transmitted to the monitoring center. Each customer has a time interval set by contract by which a notification is sent to the customer, which may vary based on the nature of the alert. For example, if an offender strays into a prohibited area, an alert is transmitted to the monitoring center. If the offender exits the area before the contractual time interval is exceeded, a violation report is not required. The ExacuTrack One device has the ability to transmit an audible alert to the offender when the offender enters into an exclusion zone or otherwise violates the terms of his or her release. When an audible alert is given, the offender is required to acknowledge receipt of the alert, and to exit the area. The ExacuTrack One units are fully capable of meeting the requirements of the RFP operating on their own. However, in order to provide an option to conserve battery life of the ankle device, BI proposed to use a radio frequency ?Beacon.? When an offender is in range of his or her Beacon, generally being within the perimeter of the offender‘s home, the GPS feature goes into a low power state, and data is transmitted through the Beacon, thus extending the battery charge. BI considered the Beacon to be an optional device that exceeded the requirements of the RFP, and that could be provided at no additional cost at the discretion of the Department. Monitoring of the ExacuTrack One device may be accomplished in one of two ways. The monitoring system and devices can be sold to an agency which then provides its own monitoring, referred to as a ?local host? facility. The more commonly used system and that proposed for Florida, is one in which the monitoring devices are provided to the agency, with the resulting data sent to the BI monitoring center. The data is then stored and made available through the TotalAccess case management system. Department staff, correctional and probation officers, and other authorized users can access the system to perform a number of tasks, and are notified according to contract when monitoring alerts are transmitted to the monitoring center. The BI monitoring center has fully redundant capabilities, with all data being replicated both at the primary monitoring center in Boulder, Colorado, and at the backup center in Anderson, Indiana. Review of the Proposals Mandatory Responsiveness Requirements Review The Department initially reviewed each of the proposals to determine if Mandatory Responsiveness Requirements were met. Pursuant to section 5.1 of the RFP, the only Mandatory Responsiveness Requirements/Fatal Criteria were: a) that the complete proposal be submitted on time; and b) that the certification and cover sheet be signed. No prospective vendor was determined to be non-responsive for either of the Mandatory Responsiveness Requirements. Material Deviations/Minor Irregularities Review The procedure by which the Department was to begin the process of review of those proposals that survived the Mandatory Responsiveness Requirements/Fatal Criteria review was for procurement staff to review the proposals ?for compliance with the items required in the . . . Proposal Submissions outlined in Section 5 of the RFP.? The purpose of the compliance review was to determine whether the proposals contained any deviations from the terms, conditions, and specifications of the RFP, and whether such deviations were material deviations requiring rejection of a response, or whether they were waivable minor irregularities. If a deviation was determined to be a minor irregularity, the Department reserved the right to require additional information prior to the contract award. Kelly Wright was the Department staff person who was directly, and almost exclusively, responsible for the RFP. Ms. Wright was, in consultation with the Department‘s subject matter experts, the primary drafter of the RFP. She was responsible for vendor questions and for preparing the Addendum #1 in which those questions were answered. She prepared the evaluation manual, trained the evaluators, and compiled their scores. She performed the review of the proposals for compliance with the mandatory requirements/fatal criteria, and reviewed the executive summaries and transmittal letters. It was also Ms. Wright‘s responsibility to identify deviations from the RFP requirements and initiate the process by which such deviations were resolved. Gail Hillhouse, who is Ms. Wright‘s supervisor, and is an active participant in the decision-making process for other procurements, was not materially involved in Request for Proposals No. 10-DC-8200. She did not assist Ms. Wright in the review of responses, nor was she involved in the process of resolving deviations of the proposals from the terms of the RFP. Ms. Hillhouse never reviewed the BI proposal at any time prior to the posting of the award. If during the course of the pre-evaluation review of the proposals, or otherwise during the selection process, a deviation from the terms, conditions, and specifications was discovered, Ms. Wright was to take it directly to her bureau chief, Robert Staney. Mr. Staney‘s practice was to consult with the Department‘s legal staff, and then make a determination as to whether the deviation was a non-waivable material deviation under section 1.15 of the RFP, or a waivable minor irregularity under section 1.16 of the RFP. The Department appointed an Evaluation Committee to evaluate the proposals. The evaluators were charged with scoring the proposals as they were provided to them. The evaluators were not asked to determine whether any provision of the responses constituted a material deviation from the terms, conditions, or specifications of the RFP, and none did so. The evaluators were provided with scoring sheets that established the factors, referred to as ?considers,? that were to go into each individual score by section. Most sections contained multiple ?considers? that were to be evaluated to determine the overall score for that section. In the event a proposal was ?completely utterly unresponsive? as to the ?considers? listed for a particular section, a score of zero could be assigned. A zero would generally be an indication that some item had been omitted, thus triggering a ?material deviation? review. The scoring was to be performed as a composite, and the ?considers? within a section were not to be scored individually. Therefore, even if an element of a section was omitted in its entirety, a score of greater than zero would be required as long as there was information provided regarding the other ?considers.? That was so even if the omitted ?consider? would -- standing alone -- constitute a material deviation from the terms, conditions and specifications of the RFP. Only if an evaluator assigned an overall section score of zero would a review be undertaken to determine whether that section of the proposal materially deviated from the requirements of the RFP. Neither Pro Tech nor BI scored a zero for any section. Since there were no zeros, no ?material deviation? review was made. Ms. Wright did not review the BI proposal from beginning to end until the evaluation and scoring was completed, and the award to BI was ready to be posted. The evidence in this case demonstrates that, except as related to the financial documentation discussed herein, no one in the Department reviewed the proposals to determine if they contained deviations, material or not, from the terms, conditions or specifications of the RFP, nor was any such determination made prior to the posting of the intended award. Financial Documentation Review Each prospective vendor was required to submit financial documentation of its ability to perform the contract pursuant to section 5.4 of the RFP. The financial documentation was not a Mandatory Responsiveness Requirement/Fatal Criteria pursuant to section 1.13. Rather, section 5.4.4 provided that the ?proposer shall provide financial documentation that is sufficient to demonstrate its financial viability,? and listed the items to be included in the proposal. The RFP further provided that ?[f]ailure to provide any of the aforementioned financial information may result in proposal disqualification.? The financial documentation for each proposal was reviewed by an independent Certified Public Accountant, who determined its sufficiency under section 5.4 of the RFP. Three of the responses, those of iSecureTrac Corporation, SecureAlert, and SOS International, failed to pass the Financial Documentation review, and were disqualified from further review and consideration. The CPA determined that the G4S Justice Services, LLC financial statement had several deficiencies, including the omission of items required by section 5.4.1 of the RFP. The information was provided by the CPA to the Department‘s procurement office. After consultation with legal staff, the Department determined the deficiency to be a minor irregularity, and it was therefore waived. Evaluation Each member of the evaluation committee had experience in the field of electronic monitoring. There are no disputed issues of fact regarding the qualifications or training of the evaluation team, the procedures by which the RFP scoring was performed, or of any individual score. Therefore, further findings or conclusions regarding the evaluators or the scoring of the proposals are unnecessary. Proposed Award As a result of the process of evaluating and scoring the proposals, the Department determined that BI was the highest scoring proposer. Pro Tech was the second highest scoring responsive proposer. Satellite Tracking of People, LLC and G4S Justice Services, LLC were ranked third and fourth, respectively. The final scores were calculated, and the proposers were ranked as follows: Proposers Actual points received by Proposers (X) Highest points received by any Proposal (N) Awarded Points (Z) CATEGORY 1 - Business/Corporate Experience - Maximum 300 Points - (X/N x 300 = Z) BI 209.64 253.39 248.20 G4S 186.07 253.39 220.30 Pro Tech 253.39 253.39 300 STOP 196.43 253.39 232.56 CATEGORY 2 - Technical Specs & Service Delivery Approach - Maximum 400 Points - (X/N x 400 = Z) BI 241.96 285.54 338.95 G4S 246.96 285.54 345.96 Pro Tech 285.54 285.54 400 STOP 248.57 285.54 348.21 Proposers Proposed Per Diem Unit Price (X) Lowest Verified Per Diem Unit Price of All Proposals (N) Awarded Points (Z) CATEGORY 3 - Cost Proposal - Maximum 300 Points - (N/X x 300 = Z) BI $3.00 $3.00 300 G4S $6.88 $3.00 130.81 Pro Tech $5.20 $3.00 173.08 STOP $4.15 $3.00 216.87 Total Proposal Points and Ranking Proposers Total Proposal Points Ranking BI 887.15 1 G4S 697.07 2 Pro Tech 873.08 3 STOP 797.64 4 On December 17, 2010, the Department posted its intent to award the contract to BI. The ?October 5, 2010 Incident? BI has contracts with the Department of Homeland Security, several states, and numerous political subdivisions under which persons are monitored with BI-supplied equipment. The data from the monitoring devices is transmitted to a centralized monitoring location. All of the BI GPS devices, as well as a number of radio frequency and alcohol monitoring devices, were monitored through BI‘s ?TotalAccess? system. On October 5, 2010, at approximately 7:30 a.m. MDT, the number of records contained in the ?identity column? field in the TotalAccess database, which operated on a 32-bit platform, exceeded the capacity of that field. As a result, the monitoring center could no longer receive data from any of the 16,000 devices using the TotalAccess system, which included all of BI‘s almost 9,000 GPS devices. The ?outage? lasted approximately 12 hours. Although the monitoring devices continued to collect and store data on the whereabouts of the offenders during that period, the data could not be sent to the monitoring center or accessed by officers. Offenders had no direct way of knowing that the monitoring devices were not transmitting data. When the system came back on-line at approximately 7:25 p.m. MDT, the data was transmitted from the affected devices to the monitoring center. No data was permanently lost as a result of the outage. Officers were notified of any activities that would have triggered an alert during the period of the outage. If any questions arose as to the movements of an offender during the outage, that data could be retrieved and examined after the fact. During the outage, BI customers were alerted, either by e-mail or by telephone, and advised of the problem. The customers were updated throughout the outage period. The resolution of the issue was achieved by rewriting the ?identity column? data file from 32-bit, with a capacity of 2.1 billion records, to a 64-bit file, with a capacity of 9 quintillion records. In addition, a customized monitor was developed and installed so that a warning will be provided in the future if the system nears capacity. Thus, it is unlikely that this particular problem will recur. The October 5, 2010, incident was, by BI‘s own admission, the single worst event in BI‘s operational history. Protest Issues Petitioner, Pro Tech, timely filed a protest of the award of the contract to BI. The January 3, 2011, protest petition identified the issues that formed the basis for its protest of the award of the contract to BI.1/ The issues alleged by Petitioner are: Whether BI failed to comply with section 5.3.2 of the RFP by failing to: identify all of its federal, state or government contracts under which it provided electronic monitoring services and the number of active GPS units utilized for each; and provide a narrative summary of contract performance for each contract so identified, including major adverse findings; Whether BI failed to comply with section 5.2.9 of the RFP by failing to disclose ?complaints filed, investigations made, warning letters or inspection reports issued, or any disciplinary action? by governmental entities, specifically related to the outage of service that occurred on October 5, 2010; Whether BI failed to comply with section 5.5.13 of the RFP by refusing to provide a copy of its Disaster Recovery Plan. Whether BI failed to comply with section 5.5.15 of the RFP by failing to provide a copy of its training curriculum; and Whether BI failed to comply with section 5.5.5 of the RFP by failing to provide a copy of the FCC Grant of Authorization for the ?Beacon? device identified in its proposal. Pro Tech alleged that each of the deficiencies identified in its protest petition constituted a Material Deviation from the terms, conditions, and specifications of the RFP that, pursuant to section 1.15 of the RFP, could not be waived and that warranted rejection of the BI response. On November 15, 2011, BI filed its Petition for Leave to Intervene, in which it raised, as a disputed issue of fact and law, ?[w]hether Pro Tech‘s RFP reply met all of the requirements of the RFP and/or was materially non-responsive.? The responsiveness of Pro Tech‘s proposal was not preserved as an issue remaining for disposition in the Joint Pre-Hearing Stipulation.2/ Issue 1: Failure to comply with past experience requirements Section 5.3.2. requires that details of the proposed vendors‘ experience ?shall be provided in narrative form and in sufficient detail so that the Department is able to judge its complexity and relevance,? and as part of that directive, the proposed vendor was required, in part, to ?identify all current and/or past (or within three (3) years) federal, state or government contracts for the provision of electronic monitoring services, and the number of active GPS units utilized for each,? and to ?provide a narrative summary of contract performance in the above-identified contracts, including any major adverse findings.? (emphasis added). The subsections directing the vendors to provide supportive information, including 5.3.2.3. and 5.3.2.4., can be reasonably read in no way other than to be inclusive of the requirement that such information ?shall be provided in narrative form and in sufficient detail . . .? As part of the scheduled process of refining and clarifying the terms, conditions, and specifications of the RFP, potential responding vendors were allowed to submit questions to the Department. The requirement that prospective vendors provide information regarding all government contracts was worrisome to two vendors, including Pro Tech, due to the fact that such a requirement would involve at least a hundred, and up to ?several hundred? contracts. As a result of its concern with the extent of the work necessary to identify all of its electronic monitoring contracts, Pro Tech made the specific inquiry as to whether it would be allowed to ?provide the information for our 10 largest or 10 most similar contracts.? Similarly, another vendor sought to limit the scope of the specification by requesting to ?provide the total number of current and/or past (or within 3 years) federal, state or government contracts,? rather than identifying them individually, and to provide an aggregated, rather than an individual, narrative summary of contract performance. To each question, the Department responded that ?[t]hese requirements remain as stated in the RFP.? The answers were posted by the Department, and became part of the RFP‘s terms, conditions, and specifications. The only reasonable construction of the Department‘s response is that it remained ?a requirement or condition? of the RFP for vendors to identify all electronic monitoring contracts, specify the number of GPS units utilized in each contract, and provide a narrative summary of contract performance. While that requirement may appear to be burdensome, it nonetheless is the requirement. If a proposed vendor believed the requirement to be overly broad or unnecessary, it was obligated to challenge the specification. The specification was not challenged. Failure to identify all contracts In response to section 5.3.2.3, BI responded as follows: ?While BI currently has contracts for EM equipment and services with approximately 1,000 customers, as directed by the requirements in Section 5.3.2 we are providing contracts that are similar in size and scope to those specified in this RFP only.? BI thereupon listed seven contracts, the largest of which used approximately 3,500 ExacuTrack One GPS units, and the smallest of which used 100 ExacuTrack One GPS units. BI believed that listing all of its contracts was not necessary for it to show that it had the requisite experience to perform the Florida contract. Mr. Murnock testified that ?[i]t was clear we did not respond with all one thousand contracts,? and that BI‘s deficient response was made with ?[t]he risk of being scored lower, yes, is one of the risks.? The decision to limit the information to be provided in response to what is an objectively clear requirement was made with considerable forethought and calculation. With regard to the decision to identify seven of its approximately 1,000 customers, Mr. Murnock testified that ?there's certain things that we did not put in this response. We provided our answers to that because we knew, at the risk of getting a lower score, it was a risk-risk situation, you know, where do I expose contracts, do I expose my customer list that could -- while being protected by confidentiality we don't trust, we have seen that breached in other jurisdictions, we've seen that breached here in Florida, I was not going to expose information that we feel to be protected. I answered the specification as I defined it.? (emphasis added). Mr. Murnock stated that BI‘s decision to limit contract disclosure was, in part, the result of a desire to avoid the risk of exposing its customer list because ?[t]here are some customers that don‘t like their information being disseminated.? The suggestion that BI‘s decision was driven by an altruistic concern for the interests of its customers is unconvincing. The Department requested only ?federal, state or government contracts.? No explanation was offered as to why the existence of a government contract would be confidential, or a narrative of BI‘s performance under that contract would be a problem. Regardless of the purported reasons for non-compliance, the options when faced with a clear, direct, and unambiguous requirement of a public procurement to disclose ?sensitive? information are to: a) protest the specification; b) submit the information under the procurement‘s confidential information provisions; or c) choose not to submit a proposal. Picking and choosing what required information to provide, and what not to provide, is not among the acceptable or competitive options. Section 5.2.3 of the RFP is clear and unambiguous. BI‘s response was not in substantial accord with the RFP's requirements. The suggestion that vendors are free to unreasonably ?define? terms so as to meet their subjective desires is contrary to a fair and even-handed procurement process. All vendors are expected to comply with the terms, conditions, and specifications in the same way so as to present an equal playing field. BI‘s decision to provide only a tiny percentage of its government contracts tilted the field in its favor by allowing it to devote the time saved by not compiling the required information -- time spent by the other complying vendors -- to other sections of its proposal, a result that is contrary to competition. BI‘s representation that it provided contracts ?similar in size and scope? is itself questionable. The contract with the Wisconsin DOC was described as an Electronic Home Detention Program. Wisconsin uses the BI 9000, the HomeGuard 200, and the Sobrietor systems. Those systems were not described in the proposal. There was no indication of whether they are active GPS units or whether they are comparable to the ExacuTrack One system proposed for Florida. In short, the proposal failed to provide any information that would allow the reader to conclude that the Wisconsin DOC contract is similar in scope to the services being sought by the Florida DOC. The contract with the Delaware DOC does not include monitoring of the field units, as is called for in the Florida contract. The lack of a monitoring component makes the Delaware contract dissimilar in scope from the proposed Florida contract. The information provided with regard to the Broward County, Florida contract failed to indicate whether that contract utilizes BI monitoring services. Furthermore, the Broward County narrative indicated that the Broward Pretrial Services Division ?uses BI ExacuTrack AT, HomeGuard 200, GroupGuard Plus, and BI VoiceID,? but failed to describe those units or indicate their comparability to units proposed for the Florida contract. The undersigned will presume that the ?ExacuTrack AT? is a version of the ExacuTrack One. However, the narrative failed to list the ?number of active GPS units? as required by the specification, so it is unknown how many are in service. There was little information provided that would allow a determination that the Pennsylvania contract is ?similar in size and scope? to the proposed Florida contract. The RFP proposal states that ?the Pennsylvania Office of Probation and Parole Services have been operating its own offender monitoring center . . . .? Mr. Murnock confirmed that Pennsylvania was not affected by the October 5, 2010, incident because it used its own local host monitoring system. The lack of a monitoring component makes the Pennsylvania contract dissimilar in scope from the proposed Florida contract. The proposal also indicated that Pennsylvania ?has 450 HomeGuard units and 649 BI 9000‘s units, operating through a GuardServer 750 system.? None of those units, or the GuardServer 750 system, are described in the proposal, and they are not the devices or services proposed for the Florida contract. As such, the proposal fails to provide any information that would allow the reader to conclude that the Pennsylvania contract is similar in scope to the services being sought by Florida. In addition to the fact that Wisconsin, Delaware, Broward County, and Pennsylvania contracts are not, based on the information provided in the RFP, of the same scope as the Florida proposal, the Delaware DOC contract (175 ExacuTrack One units), the Broward County, Florida contract (an unknown number of ExacuTrack AT units), the Fayette County Adult Probation contract (120 ExacuTrack One units), and the City and County of Denver contract (100 ExacuTrack One units, along with 300 radio frequency and 70 alcohol monitoring units) do not approach the size of the Florida contract. As a result of BI‘s decision to forego its duty to identify all of its contracts, as required by the RFP, the Department was left with precious few contracts ?similar in size and scope? to that proposed for Florida with which to compare. BI was a party to other contracts that included BI monitoring and the use of the GPS device proposed for Florida that it elected not to disclose. BI has a contract with the state of Missouri that includes BI monitoring services and, in part, the ExacuTrack One field device. BI failed to list its contract with the state of Missouri in its response to section 5.3.2, purportedly because it consisted predominantly of alcohol and radio frequency monitoring, with ?a few GPS, but I couldn‘t tell you the count.? However, at section 5.5.19 of its proposal, BI noted that the Missouri Department of Corrections ?awarded BI with a contract for GPS, alcohol monitoring and radio frequency? that included the use of the same ExacuTrack One unit proposed for Florida. BI touted the Missouri contract as an example of its ability to rapidly implement the Florida contract. By tucking away information regarding the Missouri contract (along with contracts with agencies in California and Illinois) in section 5.5.19, BI was not obligated to provide a narrative summary of contract performance, or contact information that would allow the Department to follow up if it so chose. The reasoning for excluding the Missouri contract is disingenuous, considering that BI listed its contract with the City and County of Denver, in which GPS monitoring is a small percentage of the total monitoring devices in that contract. Because of BI‘s failure to disclose, it is not known how many other contracts among the 1,000 include features proposed for Florida, and which may have been of value to the evaluators. BI made a calculated decision not to disclose all of its contracts. Petitioner‘s allegations that BI ?cherry-picked? the contracts it chose to disclose is a harsh assessment, but it is an assessment that is supported by the evidence of this proceeding. BI made similar decisions to limit disclosure of its contracts in past procurements, with other agencies, without the consequence of disqualification. Therefore, BI decided to stay with its practice, in the words of Mr. Murnock, to ?disseminate it as we see fit? and chose not to disclose all government electronic monitoring contracts ?at the risk of being scored low.? The fact that BI was ?allowed?3/ to proceed, despite the fact that its response was not in substantial accord with the RFP's requirements, provided a competitive advantage to BI over other proposers. The first advantage is the immeasurable advantage conferred by withholding information on its contracts, and possible problems related thereto. The more direct advantage is the time saved by BI as a result of its decision to forego the work necessary to compile the contracts, and provide a narrative summary of their performance. The competitive advantage conferred on BI was, in this case, significant. Petitioner‘s President, Mr. Chapin, testified that Pro Tech devoted two full- time employees for approximately two weeks to collect the data necessary to fully respond to section 5.2.3, in addition to the time devoted by contract account managers in verifying contract performance matters. That was time not expended by BI –- and was time that BI could use to bolster and enhance other sections of its proposal. In addition to the direct competitive advantage conferred on BI, the Department‘s failure to enforce the clear and unambiguous requirements, especially when its ?decision? was made after the preliminary results of the evaluation were known, and when the deviation benefitted the vendor proposing a lower price, fosters an appearance and opportunity for preferential treatment that compromises the integrity of the competitive process.4/ The response to section 5.2.3.3. of the RFP provided by BI is clearly deficient, is not in substantial accord with the RFP's requirements, and is a material deviation from the terms, conditions, and specifications of the RFP. The Department‘s failure to enforce the requirement in accordance with the terms of section 1.15 was clearly erroneous, contrary to competition, arbitrary, and capricious. Failure to provide a narrative summary of contract performance Section 5.3.2.4 of the RFP required proposed vendors to provide a narrative summary of their contract performance, including major adverse findings. The summaries were not limited to major adverse findings. Rather, contract performance goes beyond adverse findings, and includes the manner and efficiency in which the contract services are accomplished, whether good or bad. BI provided narrative summaries of the few contracts it chose to identify, but little information as to contract performance. The evidence in this case demonstrates that the October 5, 2010, incident was, without question, the worst single operational event in BI‘s history, and among the two or three most significant failures in the history of the electronic monitoring industry. It affected at least one of the contracts identified by BI, that being with the state of Wisconsin. It occurred while the RFP proposal was being prepared, and approximately six weeks prior to its submission. It is absurd to believe that the October 5, 2010, incident was not a significant element that should have been disclosed in any discussion of contract performance. It may well be, as asserted by BI, that its customers were satisfied with its response to the October 5, 2010, incident. If so, it would have been a simple matter to provide an assessment of the satisfaction of BI‘s customers with its response, and with a description of the remedial measures taken to ensure that it would never recur. BI did not. Although several customers, including the state of Wisconsin, expressed their concern with the situation in writing, and BI offered credits to its customers, there do not appear to have been any ?major adverse findings? as that term may be narrowly construed. As a measure of ?contract performance,? Mr. Murnock testified that the October 5, 2010, incident ?is certainly not a good incident to occur. But when you look at the specifications, we interpreted them exactly the way they were listed.? That is not the case. Rather, the decision to withhold any mention of the incident came about by a careful and measured parsing of words. BI witnesses testified that the October 5, 2011, incident was no secret, and that it had put out media coverage and press releases because it ?wanted to be an open book? regarding the incident. However, as to the ?threshold? of the items that would have to be disclosed as a significant issue of contract performance, Mr. Murnock testified that ?that would be a very long list of performance items, whether it be from a billing issue that may have been raised, to this October 5th issue.? The equation of a simple ?billing issue? with the October 5, 2010, incident -- the single worst event in BI‘s history -- serves to highlight the attitude that allowed BI to willingly avoid disclosure of a direct, material, and significant element of contract performance that affected the very goods and services being proposed for Florida. The incident was enough of a secret that no evaluator was aware of it. The evaluators acknowledged that the event was significant, and could have affected their scores on the performance section of the RFP, though none could state whether the effect would have been positive or negative. It may well be that the explanation of the prompt remedial measures would have been well received by the evaluators, and that no reduction in scores would have resulted. It may also be that the event, given its severity, would have negatively affected their scores.5/ The testimony of Department witnesses that the October 5, 2010, incident was not necessarily something that it would have wanted to know about rings hollow. There is absolutely no reason why that information would not be pertinent and material to this RFP. The suggestion that the October 5 incident was something the Department viewed with ambivalence goes more to its desire to support the contract award than it does to the sufficiency of the BI narrative of contract performance.6/ Despite what is clearly a designed and calculated effort on the part of BI to withhold information regarding the incident from the Department -- and the Department‘s inexplicable lack of concern regarding the withholding of material information regarding subject matter of the RFP -- the fact is that BI‘s proposal included ?narrative summaries,? thereby meeting the minimal requirement established in section 5.3.2.4. Despite a lack of candor on the part of BI that raises significant concern, the undersigned cannot conclude that the deficiencies in the narrative summaries constituted an issue of basic responsiveness. Therefore, the undersigned cannot find that BI‘s omission of information regarding the goods and services proposed for Florida is a material deviation from section 5.3.2.4. of the RFP. Issue 2: Failure to disclose ?complaints? related to the October 5, 2010 event Section 5.2.9. of the RFP requires proposed vendors to provide ?any and all documents regarding complaints filed, investigations made, warning letters or inspection reports issued, or any disciplinary action imposed by Federal or State oversight agencies within the past five (5) years.? Pro Tech asserts that an October 7, 2010, ?deficiency notice? from the Missouri Department of Corrections regarding the October 5, 2010, incident, and follow-up correspondence through December 23, 2010, fell within the class of governmental action that should have been disclosed, but was not. The October 7, 2011, letter from the Missouri DOC identifies itself as a ?letter of notification to BI of a deficiency notice,? and requested of BI ?a written response within 7 calendar days identifying the problem area(s) which led to the failure and what steps BI intends to initiate to ensure that the system failure is not repeated.? BI witnesses testified that a ?deficiency notice? was not one of the specific items listed in section 5.2.9 of the RFP, and that it was therefore not obligated to disclose the Missouri letter under its very narrow reading of the items requested. BI‘s candor with regard to the October 5, 2010, incident as expressed in its response to section 5.2.9. is roughly approximate to that evident from its response to section 5.3.2.4.7/ Section 5.2.9. uses very specific terms. It is doubtful that the Department intended potential vendors to disclose only those documents with the words ?complaint,? ?investigation,? ?warning letter,? ?inspection report,? or ?disciplinary action? splashed prominently across the document. Rather, a fair reading of the requirement, coupled with an interest in being open and forthright regarding performance -- an ?open book? as stated by Mr. Murnock -- would clearly include a ?deficiency notice? to be within the class of items being requested. However, since the specific RFP language listed specific items, without a more inclusive descriptor, such as ?including but not limited to,? or ?in the nature of,? the undersigned will not broaden the specific RFP requirement. Since the Missouri letter did not include the words ?complaint,? ?investigation,? ?warning letter,? ?inspection report,? or ?disciplinary action? within the body of the correspondence, despite its being plainly within the general class of those documents, the response provided by BI to section 5.2.9. was not a material deviation from that requirement of the RFP. Issue 3: Failure to provide a copy of the Disaster Recovery Plan The RFP, at section 5.5.13., provides that ?[t]he proposer shall provide a detailed description of the Contractor‘s method and approach for meeting or exceeding all Monitoring Center requirements in section 3.13, and specifically . . . provide a copy of the Disaster Recovery plan.? The requirement is clear, direct, and unambiguous. BI did not file a protest of the specification, nor did it question the submission of its Disaster Recovery Plan during the process that resulted in the issuance of Addendum #1. In response to section 5.5.13. of the RFP, BI responded as follows: ?Because of security reasons, the Disaster Recovery Plan is not included with this response. For an outline of the Disaster Recovery Plan, see „3.13.4? beginning on page 148.? BI‘s refusal to provide the Disaster Recovery Plan is reiterated in its response to section 3.13.10. There is no industry standard as to what constitutes a Disaster Recovery Plan. However, BI clearly understood what constituted its Disaster Recovery Plan, and made the calculated decision that it was not going to submit it. The response provided by BI is clearly deficient, and is not in substantial accord with the RFP's requirements. BI decided that it would not provide its Disaster Recovery Plan to the Department ?because it has always been a practice that we not provide that unless it is outside of the production of the RFP, upon request.? The decision to ignore the requirement was made with calculated and matter-of-fact intent, relying on the assumption that it would entail at most a scoring reduction. In lieu of providing the Disaster Recovery Plan as required, Ms. White testified that elements of the plan were ?listed within the RFP itself in several different sections, about 30 different pages.? Thus, according to BI, various elements of what one might expect to find in a Disaster Recovery Plan lay flung about in unrelated sections of its RFP proposal, awaiting the efforts of the intrepid evaluators to uncover their existence and significance. BI‘s assertion that it intended those far-flung elements to meet the RFP‘s requirement that it provide its Disaster Recovery Plan is belied by its express statement that, with knowledge of its action, it elected to omit the Disaster Recovery Plan. The evaluation of a procurement proposal is not akin to a game of hide-and-seek. It is unreasonable to expect evaluators to scour each proposal to glean information scattered throughout, when there is a clear, unmistakable, and mandatory direction to provide the Disaster Recovery Plan as a single, stand-alone document. Compliance with a mandatory item of a public procurement, particularly one designed to ensure that the proposing vendor can adequately reply to a disaster scenario when its services are arguably most needed, cannot be left to the chance that an evaluator might be able to sift through the proposal, and to thereby piece together an understanding of what disaster preparedness measures are proposed. The fact that the Disaster Recovery Plan contains confidential and proprietary information does not lessen the obligation to provide that information. Section 4.3.20. of the RFP provides the procedure by which confidential, proprietary, or trade secret material may be subject to protection under the Constitution and laws of Florida. If a proposed vendor believes the protections to be insufficient, it has a hard decision to make as to whether to submit or not submit a proposal. That decision does not include whether to ignore a mandatory requirement of the RFP on the chance that the consequence would be insignificant. It is clear that the Department never determined whether BI‘s admitted failure to disregard the Disaster Recovery Plan requirement was a material deviation from the terms, conditions, and specifications of the RFP. When Ms. Wright finally reviewed the BI proposal immediately before the posting of the award of the contract, she noted that BI had not submitted a copy of its Disaster Recovery Plan as required by the RFP. Ms. Wright did not follow the established procedure of discussing the issue with Mr. Staney, nor was legal staff consulted. Rather, Ms. Wright called Douglas Smith, who was an evaluator. Ms. Wright indicated that, despite BI‘s express statement that it was not submitting a copy of its Disaster Recovery Plan as required, she wanted ?to check with Mr. Smith on if he felt comfortable with what they had shared about the Disaster Recovery Plan, and was it sufficient.? Mr. Smith recalled his conversation with Ms. Wright, and indicated that ?it wasn‘t so much the Disaster Recovery Plan specifically, she was asking about the elements we reviewed. Are you comfortable with the score that was given? Are they adequate, satisfactory to be able to perform the services based on the contract?? Based on her discussion with Mr. Jones, Ms. Wright unilaterally determined that she did not need to take the issue of the omission of the Disaster Recovery Plan to Mr. Staney or to legal staff. Notably, Ms. Wright admitted that she did not make a determination of whether BI‘s admitted failure to provide a copy of its Disaster Recovery Plan, as required by the RFP, was a material deviation or a minor irregularity. Vendors with an interest in the Florida contract may have been discouraged from submitting proposals because of similar concerns with the security of their Disaster Recovery Plans, or because they did not have a stand-alone Disaster Recovery Plan. It generally cannot be known how many, if any, potential proposers may have been dissuaded from submitting a proposal because of one project specification or another. However, although the effect of an agency choosing to ignore a clear and unambiguous requirement for one proposer that is applicable to all other proposers confers a competitive advantage that is difficult to calculate, it is nonetheless real. Furthermore, withholding its Disaster Recovery Plan until after the posting of the award gave BI the opportunity to review the other proposals. If it then determined that its proposal was less than advantageous, it could effectively pull itself from the procurement by maintaining its refusal to submit its Disaster Recovery Plan when requested by the Department. Thus, the failure to submit the Disaster Recovery Plan when required was a material deviation that conferred a competitive advantage on BI that was not enjoyed by the other compliant proposers. In addition to the foregoing, the refusal to enforce the clear and unambiguous requirement that BI submit a copy of its Disaster Recovery Plan, particularly when such a waiver has occurred outside of the Department‘s normal practice of evaluating deviations from the requirements of the RFP, and after the preliminary outcome of the evaluation was known, raises the distinct appearance of favoritism and preferential treatment towards BI. BI‘s failure to provide a copy of its Disaster Recovery plan is not in substantial accord with the RFP‘s requirements, and is a material deviation from the terms, conditions, and specifications of the RFP. The Department‘s failure to enforce the requirement in accordance with the terms of section 1.15 was clearly erroneous, contrary to competition, arbitrary, and capricious. Issue 4: Failure to provide a training curriculum The RFP, at section 5.5.13, provides that ?[t]he proposer shall provide a detailed description of the approach to meeting or exceeding all Training requirements in section 3.16, and specifically: . . . provide a copy of the training curriculum.? In response to section 5.5.15 of the RFP, BI provided a summary of the topics to be covered in its course for training officers and other employees in the use of the monitoring system. The summary described the outline for the training to be provided, but did not go into detail as to manner in which the training would be provided. The RFP does not define the term ?curriculum.? In general, a curriculum is defined as ?the courses offered by an educational institution? or ?a set of courses constituting an area of specialization.? MERRIAM-WEBSTER DICTIONARY, at http://www.merriam-webster.com. In this case, there is a single training course. The information provided by BI described the basic course that it intended to provide. What appears to be the subject of Pro Tech‘s complaint is that BI did not provide a complete syllabus, or the complete set of materials, for the training course that was to be provided. A syllabus or training materials were not required. The RFP, at section 3.16, provided that: [t]he training curriculum . . . [is] hereby adopted as the approved curriculum . . . to be utilized for all training purposes under this Contract. Said curriculum . . . [is] incorporated herein as if fully stated. Any changes to these documents shall be approved in writing by the Department‘s Contract Manager. Based on that provision of the RFP, a credible argument can be made that the intent of the provision was for the proposer to submit a document far more comprehensive than provided by BI. The Department‘s proffered explanation that the ?curriculum? provided by BI was what was intended by the RFP is not convincing, and generally runs contrary to the requirements of section 3.16. However, the description of what was to constitute a curriculum was imprecise and ambiguous. The information provided by BI describes the training course offering, and may reasonably be construed -- in a broad sense of the term -- to be a curriculum. The response provided by BI to section 5.5.15 is in substantial accord with the RFP's requirements as stated, and was not a material deviation from those requirements. Issue 5: Failure to provide the FCC license for the ?Beacon? Section 5.5.5 of the RFP requires the proposed vendors to provide the Department with ?a detailed description of the General Equipment specifications that meets or exceeds all requirements in section 3.7.2,? and ?provide copies of required licensing by the Federal Communications Commission for the equipment proposed.? The equipment proposed by BI as responsive to the general equipment specifications of section 3.7.2 consists of the ExacuTrack One single piece GPS tracking unit. The ExacuTrack One meets or exceeds all requirements established in section 3.7.2. The FCC grant of equipment authorization was provided for the ExacuTrack One unit. The ?Beacon? was identified in section 5.5.21 of the RFP as a value-added service that was above and beyond the RFP‘s minimum service delivery requirements and specifications. The Beacon is not a necessary component of the equipment for tracking offenders as established in section 3.7.2, but serves as a home-base unit to transmit location and data, and conserve battery power. Section 5.5.5, is reasonably construed to require that the FCC ?license? be provided only for the general equipment proposed pursuant to section 3.7.2 of the RFP. BI complied with that requirement. Based on the terms, conditions and specifications of the RFP, the response provided by BI to section 5.5.5 is in substantial accord with the RFP's requirements, and was not a material deviation from those requirements. Ultimate Findings of Fact Based on the foregoing, the BI response to Request for Proposals, Solicitation Number 10-DC-8200, materially deviated from the mandatory terms, conditions, and specifications of sections 5.3.2.3. of the RFP, as supplemented by Addendum #1, and section 5.5.13 of the RFP. The items that rendered the BI proposal non-responsive, and that materially deviated from the terms, conditions, and specifications of the RFP, gave BI an advantage or benefit not enjoyed by the other proposers, were not minor irregularities, and could not be waived under the terms of the RFP. Based on the foregoing, Pro Tech demonstrated by a preponderance of the evidence that the award of the contract to BI was clearly erroneous, contrary to competition, arbitrary, and capricious. The undersigned is not unmindful of the fact that BI proposed the lowest cost, and that the rejection of the BI proposal will result in a higher overall cost for offender monitoring services to the state. Perhaps the fact that Pro Tech proposed a system that was scored higher based on its business experience and technical merits will offset any concerns. Regardless, the decision as to whether BI met the clear and unambiguous requirements of RFP 10-DC-8200 cannot, in the interests of fair and open competition, be the result of preferential treatment afforded to BI based on one element of a multi-factored RFP.
Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that Respondent, Department of Corrections, enter a final order that adopts the Findings of Fact and Conclusions of Law set forth herein. It is further recommended that the contract issued in response to Request for Proposals, Solicitation Number 10-DC-8200, entitled "Global Positioning Satellite Electronic Monitoring Services" be awarded to Petitioner, Pro Tech Monitoring, Inc. as the highest scoring responsive vendor. DONE AND ENTERED this 4th day of April, 2012, in Tallahassee, Leon County, Florida. S E. GARY EARLY Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 4th day of April, 2012. 1/ The protest petition initially alleged that the evaluation team members did not meet the experience and knowledge requirements of section 287.057(16)(a), and that the price proposed by BI was unrealistically low, thereby jeopardizing the ability of BI to provide service under the contract. Both of those issues were withdrawn prior to the final hearing. 2/ If the issue of the responsiveness of the Pro Tech proposal had not been waived, the undersigned would have found and concluded that BI failed to demonstrate that the Pro Tech proposal was not responsive to the terms, conditions, and specifications of the RFP. The responsiveness issue was related solely to whether Pro Tech identified its contracts, provided narrative summaries, and disclosed complaints related thereto, in violation of sections 5.3.2. and 5.2.9. of the RFP. The only evidence of such non-responsiveness was related to a contract between G4S Justice Services, LLC, and the state of Connecticut, for which Pro Tech was a subcontractor. The RFP contained no requirement that a proposer disclose or discuss its subcontracts with other vendors, but rather required only the disclosure of ?all current and/or past (or within three (3) years) federal, state or government contracts.? Therefore, Pro Tech‘s failure to disclose its subcontract with G4S -- despite its disclosure of a different subcontract to which it was a party in Missouri - - was not a deviation from the terms, conditions, and specifications of the RFP. 3/ The suggestion that the Department ?allowed? the BI proposal to pass through the review process, or that the Department made such a decision, is a bit inaccurate. The evidence clearly demonstrates that the Department made no decision as to whether BI‘s proposal contained material deviations until faced with the issue in the context of litigation. However, for ease of reference, the terms ?allowed? and ?decision? will be used when describing the effect of BI‘s decisions to submit less information than required under the terms, conditions, and specifications of the RFP, and the Department‘s after-the-fact litigation strategy to support its determination to award the contract to BI. 4/ In Syslogic Technology Servs., Inc. v. So. Fla. Water Mgmt. Dist., Case No. 01-4385BID, at 61, n.19, (Fla. DOAH Jan. 18, 2002; SFWMD Mar. 6, 2002), Judge Van Laningham was similarly faced with a situation in which the agency failed to make a determination as to whether a deviation from the procurement specifications was material until after the proposals were scored and ranked, and the preliminary outcome known. His analysis is instructive and well-written, and is adopted, with full attribution, by the undersigned. The reason for this should be clear: If the decision on materiality were made from a post facto perspective based on extrinsic factors, then the temptation would be great to base the determination on reasons that should not bear on the issue. In particular, the materiality of a deviation should not depend on whether the deficient proposal happens to be highest ranked. To see this point, imagine a close football game in which, at the start of the fourth quarter, one team scores a go-ahead touchdown -- if the receiver came down in bounds. Would anyone think it fair if the referees awarded the points provisionally and reserved ruling on whether the touchdown should count until after the end of the game? Of course not. In a contest, potentially determinative decisions involving a competitor's compliance with the rules need to be made when the outcome is in doubt, when the effect of the decision is yet unknown; otherwise, the outcome may be manipulated. 5/ The Department would treat the failure to disclose the October 5, 2010, incident as a minor irregularity, thus allowing it to be treated as a scoring issue. However, the October 5, 2010, incident cannot be treated as a scoring issue due to BI‘s failure to disclose. Captain Yossarian would have made an appropriate evaluator of Request for Proposals No. 10-DC-8200. 6/ Again, with a tip of the hat to Judge Van Laningham: When an agency asserts for the first time as a party litigant in a bid protest that an irregularity was immaterial, the contention must be treated, not with deference as a presumptively neutral finding of ultimate fact, but with fair impartiality as a legal argument; in other words, the agency is entitled to nothing more or less than to be heard on an equal footing with the protester. Phil‘s Expert Tree Service v. Broward Co. Sch. Bd., Case No. 06- 4499BID at 42, n.13, (Fla. DOAH Mar. 19, 2007; BCSB June 11, 2007). 7/ To BI‘s credit, it did disclose an investigation by the state of New Jersey into its billing practices which, not surprisingly, ?concluded that BI was not at fault,? and for which BI included 23 pages of supportive information. COPIES FURNISHED: J. Stephen Menton, Esquire Rutledge, Ecenia, and Purnell, P.A. 119 South Monroe Street, Suite 202 Post Office Box 551 Tallahassee, Florida 32301 smenton@reuphlaw.com Christopher Ryan Maloney, Esquire Foley and Lardner Suite 1300 1 Independent Drive Jacksonville, Florida 32202 cmaloney@foley.com Benjamin J. Grossman, Esquire Foley and Lardner, LLP Suite 900 106 East College Avenue Tallahassee, Florida 32301 bjgrossman@foley.com Jonathan P. Sanford, Esquire Florida Department of Corrections 501 South Calhoun Street Tallahassee, Florida 32399 sanford.jonathan@mail.dc.state.fl.us Ken Tucker, Secretary Department of Corrections 501 South Calhoun Street Tallahassee, Florida 32399-2500 Jennifer Parker, General Counsel Department of Corrections 501 South Calhoun Street Tallahassee, Florida 32399-2500
The Issue Whether the Petitions for Formal Administrative Proceeding should be dismissed.
Findings Of Fact In July of 1997 a notice of an application for an environmental resource permit (ERP) was issued in conjunction with a project identified as 4-061-0164A-ERP. This project proposed to develop six single-family homesites and required the filling of 5.79 acres of wetlands. The project was reviewed by the permitting authority, the District, and was recommended for approval. On February 20, 1998, the District sent a written notice of Intended District Decision on permit application 4-061-0164A- ERP to interested persons. Such persons include those who have requested notice of all District ERP projects or those who have requested notice of District ERP projects by county which, in this instance, is Indian River County. Additionally, on February 25, 1998, a notice of the District's intended agency action appeared in a newspaper published at Vero Beach, Indian River County, Florida. Such notice provided, in pertinent part: The District gives notice of its intent to issue a permit to the following applicant(s) on March 10, 1998: HORSE'S HEAD, LTD. ATTN: CHARLES M. BAYER, JR., 1 JOHN ISLAND DRIVE, VERO BEACH, FL 32963, application #4-0610164A-ERP. The project is located in Indian River County, Section 13, Township 32 South, Range 39 East. The ERP application is for CONSTRUCTION OF FIVE RESIDENTIAL LOTS, WHICH WILL RESULT IN THE FILLING OF 5.79 ACRES OF MANGROVE SWAMP WITHIN THE EXISTING JOHN'S ISLAND DEVELOPMENT (LTVC PROPERTY). The receiving waterbody is the INDIAN RIVER LAGOON * * * The District will take action on each permit application listed above unless a petition for administrative proceeding (hearing) is filed pursuant to the provisions of sections 120.569 and 120.57, F.S., and section 40C- 1.511, F.A.C. A person whose substantial interests are affected by any of the Districts [sic] proposed permitting decisions identified above may petition for an administrative hearing in accordance with sections 120.569 and 120.57, F.S. or all parties may reach a written agreement on mediation as an alternative remedy under section 120.573. Choosing mediation will not adversely affect the right to a hearing if mediation does not result in a settlement. The procedures for pursuing mediation are set forth in section 120.573, Florida Statutes, and rule 28-106.111 and 28-106.401-.405 Florida Administrative Code. Petitions must comply with the requirements of Florida Administrative Code Rule 40C-1.521 and be filed with (received by) the District Clerk, located at District Headquarters, Highway 100 West, Palatka, Florida 32177. Petitions for administrative hearing on the above application(s) must be filed within fourteen (14) days of publication of this notice or within nineteen (19) days of the District depositing notice of its intent in the mail for those persons to whom the District mails actual notice. Failure to file a petition within this time period shall constitute a waiver of any right such person may have to request an administrative determination (hearing) under sections 120.569 and 120.57, F.S., concerning the subject permit application. Petitions which are not filed in accordance with the above provisions are subject to dismissal. Because the administrative hearing process is designed to formulate final agency action, the filing of a petition means that the Districts [sic] final action may be different from the position taken by it in this notice of intent. Persons whose substantial interests will be affected by any such final decision of the District to become a party to the proceeding, in accordance with the requirements set forth above. (Emphasis added) On February 27, 1998, the District sent Horse's Head, Ltd., the permit applicant, a notice of intended agency action to issue the ERP to fill approximately 5.79 acres of wetlands on John's Island in the Town of Indian River Shores, Indian River County, Florida, to create five residential lots in an existing residential development commonly known as "John's Island." Subsequent to the foregoing, a group of homeowners whose properties are adjacent to the applicant's site timely challenged the intended agency action. This group, designated in this record as the Prosser petition, sought an administrative hearing and the matter was forwarded to the Division of Administrative Hearings for formal proceedings. The Prosser petition was assigned to Administrative Law Judge Linda Rigot as DOAH Case No. 98-1784. The Prosser challengers and Horse's Head eventually reached an amicable resolution. Horse's Head agreed to modify the subject application by reducing the filling of wetlands on the project site; by reducing the number of proposed residential lots; by undertaking additional mitigation activities on Hole-in- the-Wall Island, which is owned by Horse's Head; and by placing additional acreage under a conservation easement previously created for the subject permit application. Pursuant to the stipulated settlement agreement referred to in the previous paragraph, Horse's Head agreed to request, and did request, the District to modify its ERP application as follows: Reduce the wetland impacts for Parcel A (see composite Exhibit "A" to Exhibit "4") from ? 2.45 acres to ? 1.03 acres. Reduce the wetland impacts to Parcel B (see Exhibit "B" to Exhibit "4") from ? 3.34 acres to ? 1.63 acres. Eliminate the northernmost of the proposed lots in Parcel B, thus reducing the total number of lots proposed for development in Parcel B from 4 to 3 lots. Create an additional 1.77 acres of wetlands by removing the Florida Power & Light ("FP&L") roadbed/power line easement on Hole-in-the-Wall Island and scraping down 0.6 acres of spoil banks within the conservation easement. Perform the rotational impoundment management "RIM" mitigation plan previously proposed for Hole-in-the-Wall Island, with the exception that clearing of nuisance exotic species on the perimeter dike has been deleted. Incorporate the majority of the northernmost of the four lots originally proposed in Parcel B into the revised and expanded area subject to a conservation easement for that parcel. Place approximately 78 acres under a conservation easement consistent with the terms and provisions of the conservation easement previously created for this application. Pursuant to the stipulated settlement agreement, the Prosser petition was voluntarily dismissed on or about February 25, 1999, and Case No. 98-1784 was closed by Judge Rigot on or about March 1, 1999. Prior to the dismissal of DOAH Case No. 98-1784, Petitioner, Edna Wieler, sent a letter to the District to contest the instant application. The Wieler letter, dated October 1, 1998, included a collection of signatures of those who reportedly opposed the applicant's proposed development. Petitioner Wieler had not timely filed a petition to challenge the applicant's project in March of 1998. Moreover, Petitioner Wieler had not sought to intervene in the proceeding which had been timely filed (DOAH Case No. 98-1784). Petitioner Wieler sent a second letter to protest the instant ERP on October 20, 1998. Because of the Wieler letters in opposition to the project, the District added Petitioner Wieler's name to the data base of those persons claiming an interest in the subject permit application. Mark Gronceski is an environmental specialist employed by the District responsible for reviewing ERP applications for projects located in Indian River County. As such he was instrumental in the agency's review of the instant project. On December 15, 1998, Kenneth Oertel wrote to Mr. Gronceski with regard to the subject project. Mr. Oertel's letter provided: On behalf of the Town of Indian River Shores I would request that you send me a copy of the final staff report prepared for the above-referenced application and any notice that this matter will be placed on the Governing Board agenda. I would like to be furnished with these documents in sufficient time to evaluate whether a petition, pursuant to Chapter 120, F.S., will be filed. On February 12, 1999, the District sent a written notice of Intended District Decision on Permit Application 4-061- 0164A-ERP to Interested Parties including Petitioners Wieler and Kenneth Oertel. On February 18, 1999, a second notice of the District's intended action in this case was published in the Vero Beach Press-Journal. This notice mirrored the first notice published. It did not reference the modifications to the permit application which had been reached through the settlement of DOAH Case No. 98-1784. On March 2, 1999, the District staff sent the applicant a notice of intended agency action to approve the Horse's Head ERP permit as modified pursuant to the above-referenced stipulated settlement agreement. On March 5, 1999, the Town of Indian River Shores and Wieler filed Petitions for Formal Administrative Proceeding challenging the District's intent to approve the Horse's Head ERP permit as modified by the stipulated settlement agreement. The District uses three forms of notice regarding ERP applications. When an ERP application is submitted, notice of receipt of such application is posted in each District service center. Further, a copy of the posted notice is provided by mail to persons or organizations who have requested notice of ERP applications. These "interested persons" receive notice based upon District-wide interests or for a requested county interest. The District is aware that some persons simply want notice of all ERP applications. Organizations in this category include the Florida Audubon Society and the Pelican Island Audubon Society as well as others. The District considered Petitioner Wieler and Mr. Oertel "interested persons" to whom notice of the application should be sent. When the District is prepared to agenda an ERP application for Board intended action, the District publishes a notice for the public of the proposed action and sends a second notice to the interested persons in its data base. This second type of notice provides a point of entry for interested persons to contest the proposed action. A third type of notice used by the District is termed a "sunshine notice." This notice makes interested persons aware of items on a Board agenda. It is sent to all persons in the data base but does not offer a point of entry for agenda items. It merely lets interested persons know what topics will be on the Board agenda. In this case, the District erroneously issued the second type of notice to the interested persons in its data base. Consequently, instead of the sunshine notice which should have been issued to Petitioners, they received the second type of notice. Petitioners claim a point of entry based upon the language of the second notice. The District Board did not formally determine Petitioners are entitled to be "parties" to an administrative review of the subject project. The issuance of the notice to Petitioners was no more than a clerical oversight. None of the Prosser group who timely challenged the applicant's project have supported Petitioners' efforts in this matter. The modified permit application as currently endorsed by the District and requested by Horse's Head does not constitute a substantial deviation from the original permit application noticed in February 1998. Petitioners have stipulated that the modified permit application is less impacting than the original design.
Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that the St. Johns River Water Management District issue a enter a final order dismissing the instant Petitions. DONE AND ENTERED this 7th day of June, 1999, in Tallahassee, Leon County, Florida. J. D. PARRISH Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 SUNCOM 278-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 7th day of June, 1999. COPIES FURNISHED: Mary Jane Angelo, Esquire Charles A. Lobdell, III, Esquire St. Johns River Water Management District Post Office Box 1429 Palatka, Florida 32178-1429 Timothy P. Atkinson, Esquire Kenneth G. Oertel, Esquire Oertel, Hoffman, Fernandez & Cole, P.A. 301 South Bronough Street Fifth Floor Post Office Box 1110 Tallahassee, Florida 32302-1110 William L. Hyde, Esquire Gunster, Yoakley, Valdes-Vauli & Stewart, P.A. 215 South Monroe Street, Suite 830 Tallahassee, Florida 32301 Henry Dean, Executive Director St. John's River Water Management District Post Office Box 1429 Palatka, Florida 32178-1492
The Issue The issue in this case is whether the proposed award by the Division of Emergency Management (DEM) of the contract referenced herein to Everbridge, Inc. (Everbridge) is contrary to DEM’s governing statutes, rules or policies, or to the solicitation specifications.
Findings Of Fact On September 1, 2015, DEM posted RFP-DEM-15-16-037 (RFP), titled ”Florida Statewide Emergency Alert and Notification System,” on the state’s Vendor Bid System (“VBS”). The purpose of the RFP is to procure a statewide emergency alert and notification system as mandated by section 252.35(2)(a)(6) Florida Statutes, which requires the DEM to “[e]stablish a system of communications and warning to ensure that the state’s population and emergency management agencies are warned of developing emergency situations and can communicate emergency response decisions.” DEM is a separate budget entity established within the Executive Office of the Governor. Tara Walters, the purchasing manager for DEM, was responsible for the RFP and the procurement process. According to the RFP, the system is to be “vendor- hosted” and capable of proving “mass notification” of “imminent or sudden hazards” through voice telephone calls, text messages, emails, social media, and “Telecommunications Device of the Deaf/TeleTYpewriter (TDD/TTY)” systems. ECN and Everbridge are vendors of mass notification systems. Section 5 of the RFP provided, in relevant part, as follows: RESPONSIVENESS Vendor. In order to qualify as a responsive vendor as that term is defined by section 287.012(27), Florida Statutes, a Proposer must submit a proposal that conforms in all material respects to this solicitation. Proposal. In order to qualify as a responsive proposal as that term is defined by section 287.012(26), Florida Statutes, a proposal must conform in all material respects to this solicitation. The Division shall not consider any proposal that contains a material deviation from the terms of this solicitation. However, the Division reserves the right to consider a proposal that contains a minor deviation or irregularity so long as that minor deviation or irregularity does not provide a competitive advantage over the other proposers. The Division shall not permit a vendor to amend a proposal after the due date for submissions – even if to correct a deviation or irregularity. * * * A proposal may fail to qualify as responsive by reasons that include, but are not limited to: Failure to include a material form or addendum; Failure to include material information; Modification of the proposal specifications; Submission of conditional proposals or incomplete proposals; and, Submission of indefinite or ambiguous proposals. Section 28 of the RFP included specific proposal format instructions. Each proposal was to contain two parts: a “Technical Proposal” (Part I) and a “Price Proposal” (Part II). The RFP explicitly identified the contents to be set forth within each part. The Technical Proposal was to include multiple sections, including a table of contents, an executive summary, and a “Management Plan.” According to the RFP, the Management Plan was required to include four elements: the vendor’s relevant experience; significant examples of the vendor’s other clients and pertinent references; a project staffing plan; and a completed “data sheet,” the form for which was included in the RFP. The RFP also required that the Technical Proposal include a section identified as “Technical Plan/Minimum System Requirements” related to the “Scope of Work” necessary to implement the system. The referenced minimum requirements were explicitly set forth at Exhibit “A” to the RFP. Finally, the RFP required that the Technical Proposal include the vendor’s financial statements for the prior three years as follows: The Proposer shall provide information regarding its financial status in order to demonstrate that it is financially stable and has the resources necessary to perform the services outlined in this RFP on a statewide basis. Proposers are to include financial statements created in accordance with Generally Accepted Accounting Principles for the last three years. (Financial documentation may be combined into one file and are not included in the page count). The Division reserves the right to evaluate the financial status of any or all Proposers before making an award decision. The Price Proposal was to be submitted separately from the Technical Proposal by using the “Price Proposal Form” included in the RFP. According to the Schedule of Events set forth in the RFP, proposals were due on September 30, 2015. DEM received five proposals in response to the RFP. DEM determined that three of the proposals were not responsive, and they received no further evaluation. The two proposals that advanced into the evaluation process were those submitted by ECN and Everbridge. The RFP identified the process by which each proposal would be evaluated, including the formulas by which some scores would be calculated. Technical Proposals and Price Proposals were separately evaluated. The Technical Proposals were reviewed by a group of six evaluators, several of whom had extensive experience in emergency management and notification systems. The evaluators subjectively scored the three Management Plan elements pertaining to relative experience, examples/references, and staffing plan. Based on the evaluation, proposals could be awarded up to 30 points allocated between the referenced elements. The scores assigned by the evaluators to ECN and Everbridge for the three Management Plan elements were as follows: Evaluator ECN Everbridge Danny Hinson 13 30 Scott Nelson 30 30 Brian Misner 24 29 Phil Royce 29 27 Kevin Smith 24 25 Scott Warner 20 26 The fourth element of the Management Plan, the data sheet, was worth up to 20 points, and was scored through a formula included in the RFP. The data sheet required a vendor to identify a “guaranteed minimum number of concurrent recipient contacts” obtainable by various methods and timeframes. Using this formula, Everbridge received a data sheet score of 20 and ECN received a data sheet score of 3.99. An assertion by ECN that Everbridge cannot achieve the guaranteed minimums set forth on its data sheet was unsupported by evidence. The RFP specifically provided that the “Technical Plan/Minimum System Requirements” section of the Technical Proposal section would be evaluated on a pass/fail basis as follows: The minimum requirements of the system are broken down in to five (5) sections in the Exhibit “A”, Scope of Work, and are as follows: Minimum System Requirements, Minimum Geographical Information System Requirements, Minimum Notification Requirements, Minimum Security Requirements, and Minimum Support Requirements. Vendor’s responses shall state each requirement and detail how the system they are proposing meets or exceeds that requirement. This portion of your response is very important as proposed systems that do not meet each of the minimum requirements shall fail the Responsibility Requirements of the RFP and shall not be considered for additional review or scoring. Three of the six evaluators determined that ECN’s proposal failed to comply with all of the minimum requirements and accordingly failed to comply with the “Responsibility Requirements” of the RFP. Nonetheless, DEM completed the review and scoring of the ECN proposal. Price Proposals were reviewed and scored by Ms. Walters according to a formula specified in the RFP. Pricing was worth up to 10 points. Everbridge received a price score of 7 points. ECN received a price score of 10 points. There is no evidence that Ms. Walter’s review of the Price Proposals failed to comply with the applicable requirements of the RFP. At the conclusion of the evaluation process, Everbridge’s total score was 54.83 and ECN’s total score was 37.32. On October 19, 2015, DEM posted its Notice of Intent to Award the contract under the RFP to Everbridge. ECN filed a Notice of Protest on October 20, 2015. ECN filed a Formal Written Protest on October 30, 2015. ECN asserts that at least some of the Management Plan scoring deviated from the RFP and the instructions provided to the evaluators. ECN specifically asserts that the evaluations conducted by three of the evaluators included consideration of information extrinsic to the RFP and the vendor proposals, that the information was flawed, and that the scores awarded were therefore inappropriate. The evidence fails to establish that the evaluation of the Management Plan materially failed to comply with procedures or criteria set forth in the RFP. The evidence establishes that the individuals selected to evaluate the proposals understood the requirements of the RFP, and that they conducted their evaluations according to their understanding of the evaluation criteria at the time the evaluations were performed. The evidence further fails to establish that any alleged deficiencies in the evaluation process, even if established, would have altered the total scores sufficiently to change the intended award of the contract as set forth in the DEM Notice of Intent. ECN asserts that the Question and Answer process employed by DEM was irrational and materially impaired the competitiveness of the procurement process. Pursuant to the RFP, vendors were permitted to submit questions to DEM. On September 21, 2015, DEM posted the questions and the DEM responses, including this question submitted by ECN: If a prospective bidder utilizes third parties for completing the RFP requirements, shall the bidder’s service level agreements (SLAs) with those third parties be submitted within the proposal response? DEM’s posted response to the question was “Yes.” Everbridge did not include SLAs within its proposal. ECN asserts that DEM should have rejected the Everbridge proposal as nonresponsive because Everbridge failed to include SLAs in its proposal. ECN submitted SLAs within its proposal, although the SLAs submitted by ECN were unexecuted or incomplete. There is no requirement in the RFP that vendors submit SLAs as part of a response to the RFP. Section 15 of the RFP (titled “Oral Instructions/Changes to the Request for Proposal (Addenda)”) provided in material part as follows: No negotiations, decisions, or actions will be initiated or executed by a proposer as a result of any oral discussions with a State employee. Only those communications which are in writing from the Division will be considered as a duly authorized expression on behalf of the Division. Notices of changes (addenda) will be posted on the Florida Vendor Bid System at: http://vbs.dms.state.fl.us/vbs/main_menu. It is the responsibility of all potential proposers to monitor this site for any changing information prior to submitting your proposal. All addenda will be acknowledged by signature and subsequent submission of addenda with proposal when so stated in the addenda. DEM’s response to the question posed by ECN did not amend the RFP. DEM did not issue any notice of change or addenda to the RFP that required a vendor to include SLAs within a response to an RFP. ECN asserts that Everbridge is not a responsible vendor because Everbridge failed to comply with Section 18 of the RFP (titled “Qualifications”), which provided, in relevant, part as follows: The Division will determine whether the Proposer is qualified to perform the services being contracted based upon their proposal demonstrating satisfactory experience and capability in the work area. * * * In accordance with sections 607.1501, 608.501, and 620.169, Florida Statutes, foreign corporations, foreign limited liability companies, and foreign limited partnerships must be authorized to do business in the State of Florida. “Foreign Corporation” means a corporation for profit incorporated under laws other than the laws of this state. Such authorization should be obtained by the proposal due date and time, but in any case, must be obtained prior to posting of the intended award of the contract. ECN, a Delaware-incorporated limited liability company, complied with the referenced requirement. Everbridge, a Delaware-incorporated corporation, did not. Although Everbridge asserts that the statutes referenced in the requirement did not require it to be registered prior to the posting of the intended award, the issue is not whether Everbridge complied with state law, but whether Everbridge met the RFP’s qualification requirements. The RFP specifically provided that in order to qualify as a responsive vendor “as that term is defined by section 287.012(27) Florida Statutes,” proposals were required to conform in all material respects to the solicitation. The RFP provided as follows: The Division shall not consider any proposal that contains a material deviation from the terms of this solicitation. However, the Division reserves the right to consider a proposal that contains a minor deviation or irregularity so long as that minor deviation or irregularity does not provide a competitive advantage over the other proposers. The issue is whether the registration requirement was “material” to the RFP. It was not. The foreign corporation registration requirement was “boiler plate” language, apparently included by DEM in the RFP with little thought. Neither Ms. Walters, nor any other DEM employee, made any effort to determine whether the vendors that submitted proposals in response to the RFP complied with the requirement. The evidence fails to establish that the failure to comply with the registration requirement constituted a material deviation from the terms of the RFP. Everbridge obtained no competitive advantage over ECN or any other vendor through noncompliance with the registration requirement. ECN asserts that the Everbridge proposal was nonresponsive to the RFP because the Everbridge proposal included the following language: Legal Disclosure Everbridge's RFP response is provided for informational purposes and is not meant to form a binding contract for the provision of our critical communications suite. Upon request, Everbridge will engage in contract negotiations to execute a service agreement tailored to appropriately capture each party's applicable rights and obligations. ECN asserts that the cited language rendered the Everbridge proposal as conditional. The RFP provided that submission of a conditional proposal could result in a proposal being deemed nonresponsive. The evidence fails to establish that Everbridge submitted a conditional proposal in response to the RFP. Section 20 of the RFP (titled “Agreement Document”) provided as follows: The Division’s “Contract” document is attached hereto and made a part hereof. The terms and conditions contained therein will become an integral part of the contract resulting from this RFP. In submitting a proposal, the proposer agrees to be legally bound by these terms and conditions. One of the three submitted proposals rejected by DEM prior to evaluation was considered to be a conditional proposal, in part because the vendor struck through portions of the RFP in its response. Unlike that vendor, Everbridge unequivocally acknowledged, on page 127 of its response, the DEM’s “instructions regarding the terms and conditions that will ultimately form the service agreement between the state and its selected vendor.” Everbridge asserts that the ECN proposal failed to comply with the requirement that the Technical Proposal include “financial statements created in accordance with Generally Accepted Accounting Principles for the last three years,” and that the failure renders the ECN proposal nonresponsive. The evidence supports the assertion. The phrase “Generally Accepted Accounting Principles” (GAAP) refers to a set of financial reporting standards and procedures adopted by the Financial Accounting Standards Board (FASB), a private organization, and adopted throughout the accounting profession. Financial statements prepared in accordance with GAAP include what are commonly identified as “notes” that disclose extensive and relevant information supporting the financial analysis reported in the statements. The financial statements submitted by ECN did not meet the requirements of the RFP. Although ECN asserted at the hearing that the financial statements it submitted were prepared in accordance with GAAP, the financial statements submitted by ECN were incomplete because they failed to contain the requisite notes. The RFP required that the financial information provided by each vendor “demonstrate that it is financially stable and has the resources necessary to perform the services outlined in this RFP on a statewide basis.” The notes to ECN’s financial statements should properly have disclosed that the ECN statements contained financial information related to ECN subsidiaries, in addition to that of ECN. The absence of notes impeded determination of the reporting entity’s financial stability and resources. The Everbridge proposal fully complied with the requirement to submit financial statements prepared in accordance with GAAP and included the notes. ECN’s failure to submit financial statements meeting the RFP requirement is a material deviation from the terms of the solicitation that may not be waived because it provided a competitive advantage over other proposers who complied with the requirement. Everbridge also asserts that the ECN proposal is nonresponsive because three of the six evaluators determined that, for various reasons, ECN’s technical plan failed to meet the minimum requirements set forth in the Scope of Work. The RFP specifically provided that a failure to meet each of the minimum requirements would result in a proposal not being further reviewed or scored. Nonetheless, the ECN proposal was reviewed and scored.
Recommendation Based on the foregoing Findings of Fact and Conclusions of Law, it is RECOMMENDED that the Department of Emergency Management enter a final order dismissing the First Amended Formal Written Protest and Petition for Formal Administrative Hearing filed by Emergency Communications Network, LLC, and awarding the contract to Everbridge, Inc. DONE AND ENTERED this 28th day of January, 2016, in Tallahassee, Leon County, Florida. S WILLIAM F. QUATTLEBAUM Administrative Law Judge Division of Administrative Hearings The DeSoto Building 1230 Apalachee Parkway Tallahassee, Florida 32399-3060 (850) 488-9675 Fax Filing (850) 921-6847 www.doah.state.fl.us Filed with the Clerk of the Division of Administrative Hearings this 28th day of January, 2016.
