
    CIRCUIT COURT OF THE CITY OF RICHMOND
    Fortran Corporation v. Commonwealth of Virginia
    July 16, 1997
    Case No. HI-68-3
   By Judge T. J. Markow

This case is before the court on cross motions for Summary Judgment The parties have stipulated to die facte and exhibits. The Court has considered the arguments and briefs and renders the following opinion.

The Commonwealth of Virginia, through the Division of General Services (DGS), issued a Request for Proposal (RFP) to procure a telephone system for die Virginia Senate and House of Delegates. The RFP was issued on September 6, 1996. The RFP was amended by Addendum No. 1 to the RFP on September 24, 1996. The two documents together make up the entire solicitation. For convenience, unless the context requires otherwise, the Court will refer to the two documents collectively as die RFP.

The RFP required proposals to be submitted by October 4, 1996. Several vendors submitted proposals, including Mitel Corporation and Plaintiff Fortran Corporation. After evaluating all of the proposals received, the Commonwealth entered into negotiations only with Mitel and Fortran. There were three negotiation meetings between the Commonwealth and each of die two potential vendors. On December 16,1996, die Commonwealth announced its intention to award the contract to MiteL Fortran filed a timely letter of protest to the DGS.

DGS denied Fortran's protest and continued with its intent to award the contract to Mitel. Fortran then filed the Bill of Complaint that brings the case before finis court

Fortran presents a four part argument three of them are interrelated.

1. Mitel’s proposal, as accepted by the Commonwealth, is not compliant with the Minimum Mandatory Requirements, as set forth in the RFP, concerning redundancy in critical system components.

2. Mitel’s proposal, as accepted by the Commonwealth, is not compliant with fiie Minimum Mandatory Requirements, as set forth in the RFP, concerning live monitoring of General Assembly sessions.

3. Mitel never properly disclosed its functions and specifications showing how it would meet file Minimum Mandatory Requirements concerning live monitoring of the General Assembly sessions.

4. By negotiating with a vendor which was not, at the time of negotiations, in compliance with the Minimum Mandatory Requirements concerning live monitoring of the General Assembly Sessions, the Commonwealth has acted in an arbitrary and capricious manner, and the negotiations were improper.

The Commonwealth argues that Fortran is misreading the requirements of the RFP and that it did nothing improper. Furthermore, the Commonwealth contends, the Mitel proposal is in compliance, and file award was made cm a fair and impartial basis. The Court will address file specific arguments concerning each of the issues separately.

Redundancy of Critical Systems

According to the RFP, “[a]!! items listed in Section III 'Statement of Needs’ and Section III 'General Terms and Conditions' are minimum mandatory requirements." Addendum to RFP ¶ B(11). “Mandatory requirements are those required by law or regulation or are such that they cannot be waived and are not subject to negotiation." RFP, Section IV, ¶ A(2).

One of file provisions of Section IB, and therefore, by its own terms, a minimum mandatory requirement of the RFP, reads as follows:

The system’s architecture shall provide redundant critical system components that would allow the system to remain fully operational during a failure of a like component

RFP, Section III, ¶ 2(g). This requirement was again mentioned in tbe addendum as follows:

ha tire event of a major system Mure, tire system should remain fully operational. The Offeror should explain how there is redundancy throughout the system....

Addendum to RFP ¶ B(7). Fortran argues that these provisions mean that, at a minimum, any component falling within the category of critical components, must have a built-in redundancy. The Commonwealth and Mitel admit that tire Mitel system which was accepted by the Commonwealth is not completely redundant However, the Commonwealth argues that the provisions quoted above require that the system have at least some critical component redundancy to meet the minimum and that the actual redundancy in the system, if greater than the minimum, would allow the system to score higher during the evaluation process. Furthermore, the Commonwealth argues that there is redundancy in the Mitel system for components that it (the Commonwealth) considers to be critical.

That is a summary of the arguments on this issue. What is apparent from this summary is that the contentions of Fortran on this issue are focused on Mitel’s compliance or noncompliance with the minimum requirements. They do not, in any way, argue that the Fortran system was not awarded all of the points it deserved based on how redundant it is or that the Mitel system was awarded too many points for its relative level of redundancy. The Commonwealth points out this distinction and then points to the issues raised at the administrative level.

In its administrative protest, Fortran addressed the issue of redundancy under the heading "Over Allocation of Technical Evaluation Points to Mitel” The thrust of the protest on this subject is that Mitel's score, as calculated by DGS, was incorrectly higher than it should have been. There is an explanation in this section of tire protest as to why Fortran believed Mitel’s system to be less than completely redundant. Thera is also a statement within the protest on this subject that, in referring to the claim that Mitel did not disclose how lacking in redundancy its system was, “[fjull disclosure would have lowered Mitel’s technical score and perhaps even rendered the offer unacceptable...." Protest, pp. 9-10.

The Commonwealth argues that the claim that Mitel’s system is so lacking in redundancy that it is not in compliance with the minimum mandatory requirements is new in court. The Commonwealth argues that Fortran did not give the agency the opportunity to consider this position and act upon it before being taken to court As such, the Commonwealth concludes that Fortran should not be allowed to bring ¿is action now.

The Court cannot agree. By alerting foe Commonwealth to possible problems concerning foe redundancy, Fortran brought foe issue to foe forefront. The agency knew of its requirements and it saw foe assertions of foe protest If the agency, faced with foe factual claims made by Fortran during foe protest did not investigate them then, it cannot claim that it was not given an opportunity. Fortran has properly raised this issue.

lire Court returns to foe merits of this claim. The appropriate standard of review is articulated in Va. Code § 11-70(C). That section specifies that the award shall be reversed only if, among other things, it is “not in accordance with... foe terms and conditions of the... Request for Proposal." This law was designed around foe public policy of promoting foir competition in foe government procurement process. If foe agency is allowed to accept a proposal that is not in compliance with foe terms of foe RFP, foe other vendors making proposals were not given foe same opportunity as foe prevailing vendor to propose a system with different, mid potentially reduced, minimum requirements. Therefore, foe Court will overturn any award which is to a vendor offering a product which does not comply with foe requirements of foe RFP. See, e.g., Qualicon Corp. v. City of Norfolk, 36 Va. Cir. 83 (Norfolk Cir. Ct. 1995) (sustaining protest where contracting agency improperly made award to bidder whose proposal did not include submittals describing technical equipment); Government Micro Resources, Inc. v. Department of Justice et al., GSBCA No. 12493-P, 94-3 BCA 26965 (Sept. 13, 1993) (sustaining protest where contracting agency improperly made award to offeror whose proposal did not include foe mandatory requirement to identify at least two instructors having three months working experience with computer system). It only remains to examine what those requirements are in this case.

A reading of foe plain language of foe RFP leads foe Court to conclude that all of foe critical components of foe system must he redundant A reasonable vendor, preparing its proposal, would not read foe above quoted sections ami conclude that it is in compliance if at least one critical component is redundant As quoted above, foe Addendum states that foe system should remain fidly operational mid that this should be accomplished with redundancy “throughout foe system.” Addendum to RFP ¶ B(7). The Commonwealth might have meant that only one critical component must be redundant while foe rest may be, or may not be, redundant but it did not say so in its RFP.

There is much argument between foe parties as to what constitutes a critical component Fortran has brought to foe Court’s attention several elements of foe Mitel system which are not redundant. The Commonwealth argues (hat each of tibíese is not critical. The Court finds that, at a minimum, any component which, if it Ms, causes a failure in the operation of a substantial part of die system, is a critical component Fortran has pointed to one such component in die Mitel system, the Control Resource Card (CRC). The parties agree that if this card were to fail in its entirety, the system would go down in its entirety. The parties also agree that there is no redundant card in this system hacking up the CRC. The Commonwealth argues that for each computer chip on die card, there is a second backup chip on tibe same card, and therefore, it concludes, the card has tibe redundancy necessary. This argument ignores (he possibility of the card itself not the computer chips which it houses, Ming. The Mitel system lacks this redundancy. Therefore, it does not comply with the Mandatory Minimum Requirements of tibe RFP. The award of the contract to Mitel must be set aside.

Live Monitoring

The RFP, as a minimum mandatory requirement, demands die following:

The system proposed shall include the capability to allow for die “live” monitoring of tibe House and Senate proceedings, @.g. each digital telephone shall have access to tibe House and Senate proceedings.

RFP, Section III, ¶ C(2)(e) Fortran argues dial the Mitel system only allows a limited number of tibe telephones to have access to the House or Senate proceedings at any one time. Fortran contends that the language requiring that “each digital telephone” have such access actually means drat the system should allow for the simultaneous access of the proceedings by all of the digitel telephones. Fortran continues by pointing out that, not only does Mitel’s system lack in the ability to allow for simultaneous access, but it also only allows the monitoring of either die House or the Senate at any given time.

Apparently, the Mitel system uses a feature referred to as music-on-hold. This audio channel would be receiving input from the sound system of the House or the Senate. As a result, any user at a handset on the system could press a button and hear whichever proceeding was being monitored. However, there is only one music-on-hold channel in the system, so only one of die legislative bodies sessions could be monitored at any one time. As such, if the system were monitoring the House, and a listener wished to monitor tibe Senate, the entire system would have to be switched over, so that every listener would hear the Senate.

The Commonwealth argues that Mitel’s proposal is m compliance. This is so, it claims, because the RFP only requires that each telephone have access. The RFP does not require simultaneous access of all phones to each system. Furthermore, they say, Mitel has represented to tire Commonwealth that it will be in compliance.

Originally, Mitel proposed a "work-around” using an ancillary hardware device, which was neither described nor detailed. Later, they claimed to have developed an upgraded system, which they would provide at no extra charge, which would solve the problem by having two music-on-hold channels. Based on this claim, the Commonwealth argued that this issue had been rendered moot. However, it In» since come to light that the dual channel music-on-hold feature is still not available. As such, the Commonwealth has withdrawn the mootness argument. Presumably returning to the position of expecting a hardware work-around again. One way or die other, tire Commonwealth is relying on that assertion by Mitel that all telephones will have access.

Based on the Commonwealth’s argument, a vendor would be in compliance if every telephone had a button that would connect it to one or the other of the sessions, but only one handset could use that feature at a time. While there is certainly a conspicuous lack of language to die effect diet simultaneous access must be available, the Commonwealth’s reading of the language present does not comport with what a reasonable vendor would interpret that to mean. More to die point, die language explicitly requires access to the House and Senate proceedings. Under the system proposed by Mitel, each phone would have access (if one accepts the Commonwealth’s definition of access as being synonymous with potential capability) to either the House or the Senate proceedings. The Court does not here make a finding of how many phones should have access simultaneously. It is not necessary to do so in light of the fact dud die Mitel system does not comply due to its inability to monitor both the House and die Senate. For this reason, the award of the contract should be reversed.

Remaining Issues

The remaining issues, failure of Mitel to adequately disclose die details of its system and improper negotiations, become insignificant in light of the above findings. The Court does not, at this time, pass on the merits of diese claims.

Conclusion

The Court need only conclude that the proposal accepted by the agency failed to meet the requirements on any one issue to reverse the award. See, e.g., Qualicon, 36 Va. Cir. at 85. In this case, the Court has determined that die Mitel system is deficient in two important respects: it does not meet the mandatory minimum requirements for redundancy or for live monitoring. Therefore, summary judgment will he entered in favor of Fortran Corporation, and the award to Mitel will be reversed.

As the Commonwealth could have chosen not to make any award at all, the Court will not order that the Commonwealth make the award to the next compliant offeror, Fortran, as requested in the prayer for relief. The Commonwealth may do so, however. 
      
       Actually, Acre was a third vendor who participated in the negotiations, but it was dropped after die first round. Its involvement in the process has no bearing on the issues before tie court.
     