Skip to main content

B-186983, OCTOBER 28, 1977

B-186983 Oct 28, 1977
Jump To:
Skip to Highlights

Highlights

ALTHOUGH OFFEROR CONTENDS THAT BOTH MODELS ARE FUNCTIONALLY IDENTICAL. RECORD SHOWS THAT OFFEROR HAS NOT YET PRODUCED MODEL IT PROPOSES TO FURNISH AND HENCE AGENCY REASONABLY CONCLUDED THAT BENCHMARK OF THAT MODEL RATHER THAN EARLIER VERSION OF THAT MODEL WAS REQUIRED. 2. EVALUATORS' ROLE AT BENCHMARK TEST WAS TO OBSERVE AND REPORT ON RESULTS OF OFFEROR'S BENCHMARK TO CONTRACTING OFFICER. 3. ALLEGATION OF BIAS IN EVALUATION IS NOT SUSTAINED SINCE RECORD SHOWS THAT AGENCY'S EVALUATION WAS REASONABLE. 4. CONTENTION THAT SPECIFICATIONS CONTAINED LATENT AMBIGUITIES IS DENIED. SOLICITATION NEED NOT USE WORK "MANDATORY" TO INDICATE TO OFFERORS THAT LISTED FEATURES WERE REQUIRED WITH EQUIPMENT TO BE SUPPLIED.

View Decision

B-186983, OCTOBER 28, 1977

1. OFFEROR DOES NOT MEET BENCHMARK REQUIREMENT BY DEMONSTRATING EARLIER VERSION OF MODEL IT PROPOSES TO FURNISH. ALTHOUGH OFFEROR CONTENDS THAT BOTH MODELS ARE FUNCTIONALLY IDENTICAL, RECORD SHOWS THAT OFFEROR HAS NOT YET PRODUCED MODEL IT PROPOSES TO FURNISH AND HENCE AGENCY REASONABLY CONCLUDED THAT BENCHMARK OF THAT MODEL RATHER THAN EARLIER VERSION OF THAT MODEL WAS REQUIRED. 2. AGENCY DID NOT WAIVE ITS RIGHT TO OBJECT TO OFFEROR'S USE FOR BENCHMARK TEST OF EARLIER VERSION OF MODEL IT PROPOSES TO FURNISH MERELY BECAUSE AGENCY EVALUATORS PERMITTED OFFEROR TO COMPLETE BENCHMARK TEST. EVALUATORS' ROLE AT BENCHMARK TEST WAS TO OBSERVE AND REPORT ON RESULTS OF OFFEROR'S BENCHMARK TO CONTRACTING OFFICER. 3. ALLEGATION OF BIAS IN EVALUATION IS NOT SUSTAINED SINCE RECORD SHOWS THAT AGENCY'S EVALUATION WAS REASONABLE. 4. CONTENTION THAT SPECIFICATIONS CONTAINED LATENT AMBIGUITIES IS DENIED. SOLICITATION NEED NOT USE WORK "MANDATORY" TO INDICATE TO OFFERORS THAT LISTED FEATURES WERE REQUIRED WITH EQUIPMENT TO BE SUPPLIED. MOREOVER, AGENCY'S POSSIBLE WILLINGNESS TO CONSIDER PROPOSED CHANGE FROM A LISTED FEATURE DOES NOT INDICATE THAT LISTED FEATURES WERE NOT MANDATORY.

TELEFILE COMPUTER PRODUCTS, INC.:

TELEFILE COMPUTER PRODUCTS, INC. (TELEFILE) PROTESTS THE EXCLUSION OF ITS PROPOSAL FROM THE COMPETITIVE RANGE UNDER DEPARTMENT OF THE ARMY REQUEST FOR PROPOSALS (RFP) DAAB09-76-R-0013 FOR THE PURCHASE OF 64 PROGRAMMABLE COMMUNICATIONS CONTROLELRS, MAINTENANCE AND SOFTWARE.

THE RFP WAS ISSUED ON APRIL 22, 1976, AND WAS THE SUBJECT OF A PRIOR PROTEST TO THIS OFFICE WHICH WAS DENIED. COMTEN, INC., B-186983, DECEMBER 8, 1976, 76-2 CPD 468; AFFIRMED ON RECONSIDERATION, MARCH 3, 1977, 77-1 CPD 173. BASED ON THE PROPOSALS SUBMITTED, THREE FIRMS (INCLUDING TELEFILE) WERE INITIALLY INCLUDED WITHIN THE COMPETITIVE RANGE.

TELEFILE PROPOSED A COMMUNICATIONS CONTROLLER IT DESIGNED AS THE FECP-I, AN ACRONYM FOR FRONT END COMMUNICATIONS PROCESSOR, WITH THE "I" USED TO DESIGNATE IBM COMPATIBLE EQUIPMENT. TELEFILE ALSO PROPOSED TO FURNISH SOFTWARE IT IDENTIFIED AS FROS. BOTH THE FECP-I AND FROS WERE FOUND TO BE TECHNICALLY ACCEPTABLE AS PROPOSED, SUBJECT, HOWEVER, TO THE FOLLOWING RFP PROVISIONS:

"SECTION E

"3. REQUIREMENTS.

A. HARDWARE REQUIREMENTS.

(13) PRODUCTION STATUS. TO INSURE EARLY OPERATION AND RELIABILITY OF THE SYSTEM, ONLY STANDARD PRODUCTION MODULES MAY BE PROPOSED. SUCCESSFUL PRODUCTION MODULES MAY BE PROPOSED. SUCCESSFUL INSTALLATION AT OTHER (NON -BIDDER) LOCATIONS WILL BE TAKEN AS EVIDENCE OF SUCH PRODUCTION STATUS.

"4. DEMONSTRATIONS.

A. THE GOVERNMENT WILL REQUIRE AN OPERATIONAL DEMONSTRATION, PRIOR TO SELECTION OF A VENDOR, OF ALL EQUIPMENT, SOFTWARE, AND SYSTEMS CAPABILITY PROPOSED IN SATISFACTION OF REQUIREMENTS IN THESE SPECIFICATIONS."

TELEFILE'S DEMONSTRATIONS WERE HELD AT TWO LOCATIONS-- A NATIONAL AERONAUTICS AND SPACE ADMINISTRATION (NASA) FACILITY IN LINTHICUM HEIGHTS, MARYLAND, AND IN A PRIVATE FACILITY IN IRVINE, CALIFORNIA. BOTH LOCATIONS WERE DESIGNATED BY TELEFILE, AND AT NEITHER LOCATION WAS EQUIPMENT IDENTIFIED AS "FECP-I" OR "FROS" SOFTWARE DEMONSTRATED. WHAT WAS DEMONSTRATED WAS A COMMUNICATIONS CONTROLLER MARKETED BY TELEFILE AS THE TCP-64, AND WHAT PROTESTER STATES WERE SEPARATE ELEMENTS OF THE FROS SOFTWARE.

THE PROTESTER HAS, IN OUR VIEW, APPROPRIATELY IDENTIFIED THE PRINCIPAL ISSUE WHICH IS DISPOSITIVE OF THE PROTEST. ACCORDING TO TELEFILE: "THE REAL ISSUE SHINES CLEARLY, I.E., IS TELEFILE'S * * * LONG PRODUCED TCP-64 FOR ALL INTENTS AND PURPOSES THE SAME AS THE EQUIPMENT PROPOSED BY TELEFILE AND CALLED THE FECP-I? IT IS * * * TELEFILE'S POSITION THAT THE TCP-64 AND THE FECP-I ARE THE SAME * * * AND THE ARMY KNOWS THEY ARE THE SAME."

PROTESTER ACKNOWLEDGES THAT THE TCP-64 WAS MANUFACTURED USING WIRE WRAP CIRCUITRY, WHILE THE HARDWARE PROPOSED IS TO BE MANUFACTURED WITH PRINTED CIRCUIT BOARDS INSTEAD OF THE WIRE WRAP METHOD OF CONSTRUCTION. THERE IS NOTHING IN THE RECORD TO SUGGEST THAT AT THE TIME OF THE DEMONSTRATIONS, ANY IBM COMPATIBLE FRONT END COMMUNICATIONS CONTROLLERS MANUFACTURED WITH PRINTED CIRCUIT BOARDS WERE IN REGULAR PRODUCTION BY TELEFILE OR SUCCESSFULLY INSTALLED IN ANY LOCATION. NONETHELESS, TELEFILE CONTENDS THAT THE TWO UNITS ARE FUNCTIONALLY IDENTICAL, AND THEREFORE MAINTAINS THAT THE EQUIPMENT DEMONSTRATED (TCP 64) WAS THE SAME AS THAT PROPOSED; THAT THE ARMY THEREFORE IN FACT WITNESSES THE FECP-I IN OPERATION. THIS REGARD, AT A CONFERENCE HELD AT THIS OFFICE ON JULY 20, 1977, PURSUANT TO OUR BID PROTEST PROCEDURES, TELEFILE OFFERED FOR THE RECORD WHAT IT STATED TO BE THE LOGIC DIAGRAMS FOR THE TWO SYSTEMS. IN ADDITION, TELEFILE DISPLAYED BOTH THE WIRE WRAP AND PRINTED CIRCUIT BOARDS PURPORTED TO BE USED IN THE RESPECTIVE SYSTEMS.

IN VARIOUS SUBMISSIONS TO THIS OFFICE, THE PROTESTER HAS ASSERTED (1) THAT IT CHANGED THE NAME OF THE MODEL IT PROPOSED BECAUSE IT PLANNED TO USE PRINTED CIRCUITS IN THE HARDWARE IT DELIVERED TO THE GOVERNMENT, (2) THAT THE MODEL TO BE DELIVERED (WIRE WRAP VS PRINTED CIRCUITS) WAS DEPENDENT ON WHICH WAS COMING OFF THE PRODUCTION LINE AT THE TIME DELIVERY WAS REQUIRED, (3) THAT THE PRODUCT WAS RELABELED TO DISTINGUISH IT FROM THE CONTROLLERS BUILT FOR OTHER HOST COMPUTERS (THE "I" FOR "IBM"), AND (4) THE ARMY ACTUALLY OBSERVED THE FECP-I IN OPERATION AT NASA (ALTHOUGH IT WAS THE WIRE WRAP TCP-64). THUS, THE PROTESTER STATES THAT "TELEFILE CHANGED THE NAME OF THE TCP-64 BECAUSE IT PLANNED TO USE PRINTED CIRCUIT BOARDS IN THE DELIVERED EQUIPMENT RATHER THAN THE MORE COSTLY WIRE WRAP CIRCUITS THEN IN USE." TELEFILE INSISTS THAT SUCH A CHANGE "PROVES THE PRODUCTION STATUS OF THE FECP-I, AS A WIRE-WRAP CIRCUIT IS USED BASICALLY WHILE AN ITEM IS STILL IN THE DEVELOPMENT STAGE. WIRE-WRAP CIRCUITRY CAN BE CHANGED MUST MORE READILY AND INEXPENSIVELY THAN A PRINTED CIRCUIT BOARD." THE PROTESTER STATES THAT THE MODEL TO BE DELIVERED TO THE GOVERNMENT "WAS STRICTLY A FUNCTION OF THE TIME AT WHICH THE ORDER WAS PLACED." IT ASSERTS THAT IF THE MODEL CONTAINING PRINTED CIRCUITS "WAS COMING OFF THE PRODUCTION LINE AT THE TIME DELIVERY WAS REQUIRED", THAT MODEL WOULD HAVE BEEN DELIVERED, IF NOT, THE EARLIER WIRE WRAP MODEL (TCP- 64) WOULD HAVE BEEN DELIVERED. THE PRESIDENT OF TELEFILE STATES IN PERTINENT PART THAT:

"AT NO TIME DID HE STATE THAT THE FECP-I MODEL OF THE TELEFILE COMPUTER PRODUCTS, INC. FRONT-END COMMUNICATIONS CONTROLLER WAS NOT SCHEDULED FOR PRODUCTION STATUS UNTIL JULY 1977. SINCE THE TELEFILE COMPUTER PRODUCTS, INC. FRONT-END COMMUNICATIONS CONTROLLER WAS RELABELED TO FECP-1 FROM TCP- 64 TO DISTINGUISH IT FROM OTHER FRONT-END COMMUNICATIONS CONTROLLERS BEING BUILT FOR OTHER HOST COMPUTERS, THE ARMY APPARENTLY HAS CHOSEN TO BELATEDLY CONFUSE THE FECP-1 MODEL FRONT END COMMUNICATIONS PROCESSOR WITH THE MICRO-PROGRAMMABLE VERSION OF THE FECP-1 FRONT-END COMMUNICATIONS CONTROLLER SCHEDULED FOR NORMAL PRODUCTION DELIVERIES STARTING IN JULY OF 1977. * * * THE FRONT-END COMMUNICATION CONTROLLER PROPOSED TO THE ARMY WAS FUNCTIONALLY IDENTICAL TO THE SYSTEM OBSERVED AT NASA EXCEPT THAT THE ULC AND IFUI ARE ON PRINTED CIRCUIT BOARDS AS OPPOSED TO BEING WIRE- WRAPPED IN THE NASA UNIT."

ON THE OTHER HAND, THE RECORD CONTAINS AFFIDAVITS OF ARMY PERSONNEL WHICH STATE THAT ON JANUARY 20, 1977, AND MARCH 17, 1977, TELEFILE REPRESENTATIVES ACKNOWLEDGED THAT THE FECP-I WAS A NEW MACHINE WHICH WAS NOT SCHEDULED FOR PRODUCTION UNTIL JULY 1977. MOREOVER, WE NOTE THAT THE RFP INCLUDED THE MICRO-PROGRAMMABLE FEATURE UNDER THE HARDWARE REQUIREMENTS.

IN ANY EVENT, WE CANNOT SAY THAT THE EQUIPMENT WHICH TELEFILE PROPOSED TO FURNISH WAS THE SAME AS THE EQUIPMENT WHICH IT DEMONSTRATED TO THE ARMY. WHILE IT MAY BE, AS TELEFILE CONTENDS, THAT ELECTRONIC HARDWARE CAN BE CHANGED FROM WIRE WRAP MANUFACTURE TO PRINTED CIRCUIT BOARD MANUFACTURE AND REMAIN FUNCTIONALLY THE SAME, IT IS ALSO POSSIBLE, IN OUR OPINION, THAT SUCH A CHANGE COULD AFFECT PERFORMANCE. THE TWO DIFFERENT SYSTEMS WILL HAVE SOME DIFFERENCES IN THE METHOD OF CONSTRUCTION. AS A RESULT, IT IS NOT POSSIBLE TO SAY THAT THE TWO SYSTEMS WILL BE FUNCTIONALLY IDENTICAL BASED SOLELY ON THE DOCUMENTS FURNISHED BY TELEFILE. IN ORDER TO DEMONSTRATE THAT THE TWO MODELS ARE FUNCTIONALLY IDENTICAL, WE BELIEVE IT IS NECESSARY TO CONDUCT BENCHMARK TESTS ON BOTH MODELS.

WE BELIEVE, THEREFORE, THAT THE PROPOSED "EQUIPMENT, SOFTWARE AND SYSTEMS CAPABILITY" WERE NOT DEMONSTRATED (BENCHMARKED) AS REQUIRED BY THE RFP; ALL THAT WAS DEMONSTRATED WAS EQUIPMENT ASSERTED TO HAVE BEEN "FUNCTIONALLY IDENTICAL" WITH THE PROPOSED EQUIPMENT. WE ARE OF THE OPINION THAT THE ARMY'S REFUSAL TO ACCEPT THAT THE TCP-64 AND THE FECP I WERE ONE AND THE SAME WAS A REASONABLE EXERCISE OF ITS TECHNICAL JUDGMENT. WE THINK THAT THE ARMY WAS ENTITLED TO HAVE DEMONSTRATED THE ACTUAL HARDWARE AND SOFTWARE PROPOSED TO BE DELIVERED, AND NOT SOMETHING ASSERTED TO BE FUNCTIONALLY EQUIVALENT. IT ALSO APPEARS FROM THE RECORD THAT TELEFILE'S PROPOSED SYSTEM WAS NOT A "STANDARD PRODUCTION MODEL" SUCCESSFULLY INSTALLED AT "NON-BIDDER LOCATIONS." BURROUGHS CORPORATION, B-187769, JULY 12, 1977, 77-2 CPD 16.

PROTESTER FURTHER ASSERTS THAT THE ARMY KNEW OR SHOULD HAVE KNOWN THAT THE TCP-64, NOT THE FECP-I, WAS INSTALLED AT NASA BECAUSE ALL "GOVERNMENT ADP EQUIPMENT IS COORDINATED THROUGH GSA WITH WHICH THE ARMY WAS IN CLOSE COMMUNICATION." THUS IT IS CLAIMED THAT THE ARMY KNEW OR SHOULD HAVE KNOWN THAT THE DEMONSTRATION WAS TO BE PERFORMED ON THE TCP-64. LIKEWISE IT IS CLAIMED THAT THE ARMY SHOULD HAVE OBJECTED TO THE DEMONSTRATION ONCE IT ACTUALLY BECAME AWARE OF THE EQUIPMENT TO BE USED. ACCORDINGLY, THE PROTESTER CLAIMS THAT BY NOT OBJECTING TO THE OPERATIONAL DEMONSTRATION ON THE TCP-64 THE GOVERNMENT "WAIVED ANY RIGHT IT MAY HAVE HAD TO A DEMONSTRATION ON THE FECP-I RATHER THAN THE TCP-64."

WE CANNOT ATTRIBUTE TO THE ARMY THE KNOWLEDGE WHICH GSA MAY HAVE AS TO THE EQUIPMENT AT THE NASA INSTALLATION SELECTED BY THE PROTESTER FOR THE INITIAL DEMONSTRATION, PARTICULARLY IN VIEW OF THE ARMY'S DENIAL OF SUCH KNOWLEDGE. THERE IS NO EVIDENCE IN THE RECORD TO SUGGEST THAT THE PROTESTER ACTUALLY ADVISED THE ARMY THAT IT INTENDED TO DEMONSTRATE EQUIPMENT WHICH IT CLAIMED TO BE FUNCTIONALLY EQUIVALENT TO THE EQUIPMENT PROPOSED, RATHER THAN THE ACTUAL EQUIPMENT PROPOSED. NOR DO WE AGREE THAT THE ARMY WAIVED ITS RIGHT TO OBJECT TO A DEMONSTRATION OF THE TCP-64 BECAUSE IT ALLOWED THE DEMONSTRATION TO BE COMPLETED WITHOUT COMPLAINT. BY DEMONSTRATING ITS EXISTING PRODUCTION MODEL RATHER THAN THE MODEL IT PROPOSED TO DELIVER, THE PROTESTER SHOULD HAVE KNOWN THAT THE AGENCY MIGHT ULTIMATELY CONCLUDE THAT THE DEMONSTRATION WAS NOT IN CONFORMANCE WITH THE RFP REQUIREMENT THAT "ONLY STANDARD PRODUCTION MODULES MAY BE PROPOSED", AND THAT THE "OPERATIONAL DEMONSTRATION OF ALL EQUIPMENT * * * PROPOSED" WAS NOT SATISFACTORILY COMPLETED. AS THE ARMY POINTS OUT, THE EVALUATION TEAM'S ROLE WAS TO OBSERVE THE DEMONSTRATION AND TO REPORT BACK TO THE CONTRACTING OFFICER THE RESULTS OF THEIR OBSERVATION.

THE PROTESTER ALSO CLAIMS THAT BECAUSE ITS WRITTEN PROPOSAL WAS FOUND TO BE TECHNICALLY ACCEPTABLE PRIOR TO THE DEMONSTRATION (A FACT WHICH IS NOT CONTROVERTED), IT SHOULD NOT THEREAFTER HAVE BEEN EXCLUDED FROM THE COMPETITIVE RANGE AS "NONRESPONSIVE (TECHNICALLY DEFICIENT) BECAUSE OF ANY ASSERTED DEFICIENCIES IN THE DEMONSTRATION. THE PROTESTER CITES LINOLEX SYSTEMS, INC., ET AL., 53 COMP.GEN. 895 (1974), 74-1 CPD 296 AND 47 COMP.GEN. 29 (1967) IN SUPPORT OF THAT PROPOSITION.

WE BELIEVE THAT THE CITED CASES DO NOT STAND FOR THE PROPOSITION URGED. LINOLEX, SUPRA, INVOLVED A BENCHMARK TEST IN WHICH THE OFFEROR USED ITS SUPPLIER'S EMPLOYEES RATHER THAN ITS OWN PERSONNEL TO PERFORM THE DEMONSTRATION TEST. THE AGENCY STATED THAT THE PURPOSE OF THE TEST WAS TO VALIDATE EACH PROPOSAL BY SHOWING HOW FAMILIAR THE OFFEROR WAS WITH THE EQUIPMENT IT PROPOSED TO FURNISH AS WELL AS TO DEMONSTRATE THE PERFORMANCE OF THE EQUIPMENT. WE CONCLUDED THAT THE PURPOSE OF THE TEST AS STATED IN THE RFP WAS SUSCEPTIBLE TO THE OFFEROR'S INTERPRETATION AND THAT THEREFORE THE OFFEROR SHOULD BE GIVEN THE OPPORTUNITY TO PERFORM THE TEST WITH ITS OWN EMPLOYEES. IN 47 COMP.GEN. 29, SUPRA, A PROTEST INVOLVING THE PROCUREMENT OF SUBSTANTIAL AMOUNTS OF COMPUTER EQUIPMENT, THE PROTESTER WAS EXCLUDED FROM THE COMPETITIVE RANGE FOR FAILURE TO PASS A 200 HOUR "OPERATIONAL USE TIME" TEST (ONE OF THE BENCHMARK TESTS REQUIRED). THE EXCLUSION OF THE PROTESTER (HONEYWELL) FROM THE COMPETITIVE RANGE LEFT ONLY ONE OFFEROR IN THE COMPETITION WITH A PRICE PREMIUM OVER HONEYWELL OF APPROXIMATELY $60,000,000. WE STATED:

" * * * WHEN THE BENCHMARK TEST LEFT ONLY ONE PROPOSER AS AN ELIGIBLE CONTRACTOR, WE DO NOT BELIEVE THE 200 HOUR BENCHMARK TEST, WHICH WAS THE ONLY TEST HONEYWELL FAILED, SHOULD HAVE BEEN CONSIDERED DETERMINATIVE OF WHAT CONSTITUTED A 'COMPETITIVE' RANGE WITHOUT REGARD TO PRICE."

IN BOTH CASES THE EQUIPMENT PROPOSED WAS THE EQUIPMENT DEMONSTRATED, WHICH WAS NOT THE CASE HERE. HERE, WE BELIEVE THE EXCLUSION OF TELEFILE FROM THE COMPETITIVE RANGE, AS DISCUSSED ABOVE, FOR FAILURE TO DEMONSTRATE THE PROPOSED EQUIPMENT HAD A REASONABLE BASIS.

THE PROTESTER ASSERTS, HOWEVER, THAT THE ARMY WAS MOTIVATED TO EXCLUDE TELEFILE FROM FURTHER NEGOTIATIONS BECAUSE OF ITS "DESIRE FOR MORE COMPLEX AND INHERENTLY MORE EXPENSIVE EQUIPMENT," POINTING TO CERTAIN "INCONSISTENCIES" IN THE ARMY'S STATEMENTS IN THE COMTEN PROTEST, SUPRA, VIS-A-VIS ITS STATEMENTS MADE IN THIS PROTEST. WE DO NOT BELIEVE THE "INCONSISTENCIES" ASSERTED ARE SIGNIFICANT AND CONSEQUENTLY THEY NEED NOT BE DETAILED HERE. MOREOVER, WE NOTE THAT NONE OF THE ASSERTED "INCONSISTENCIES", EVEN IF ACCEPTED AS SUCH, WOULD PROVE THE ALLEGED MOTIVE OR EVEN EXPLAIN WHY SUCH MOTIVE EXISTED. THEREFORE, WHERE, AS HERE, THE RECORD REASONABLY SUPPORTS THAT AGENCY'S ACTIONS, MERE ALLEGATIONS OF A BIASED EVALUATION PROVIDES NO BASIS FOR OUR OFFICE TO INTERFERE WITH THE AGENCY'S DETERMINATION THAT A PROPOSAL IS UNACCEPTABLE AND OUTSIDE THE COMPETITIVE RANGE. JOANELL LABORATORIES, INCORPORATED, 56 COMP.GEN. 291 (1977), 77-1 CPD 51. THE PROTESTER ALSO CLAIMS THAT THE RFP CONTAINS "LATENT AMBIGUITIES" REQUIRING CANCELLATION AND RESOLICITATION OF THE REQUIREMENT IF WE ARE UNABLE TO AFFIRM ITS POSITION WITH REGARD TO THE EQUIPMENT DEMONSTRATED. ALTHOUGH "NUMEROUS LATENT AMBIGUITIES" ARE CLAIMED, ONLY TWO ARE ASSERTED-- (1) THE "FAILURE TO IDENTIFY SPECIFICATION REQUIREMENTS AS MANDATORY OR NONMANDATORY," AND (2) THE DIFFERENCES BETWEEN THE OPERATIONAL DEMONSTRATION CRITERIA PROVIDED TO OFFERORS AND AS USED BY THE IN-HOUSE EVALUATION TEAM.

OUR EXAMINATION OF THE RFP REVEALS NO SUCH AMBIGUITIES. THE SPECIFICATIONS FOR BOTH THE HARDWARE AND THE SOFTWARE ARE CLEARLY LISTED WITH THE PREFACE "REQUIREMENTS". WE DO NOT BELIEVE THE WORD "MANDATORY" IS ESSENTIAL FOR ANY OFFEROR'S UNDERSTANDING THAT THE LISTED FEATURES AND CAPABILITIES WERE TO BE INCLUDED IN THE HARDWARE AND SOFTWARE TO BE FURNISHED.

THE PROTESTER NONETHELESS CLAIMS THAT IT PROPOSED TO INSTALL THE FRONT- END POLLING FEATURE LISTED IN THE SPECIFICATION 12 MONTHS AFTER AWARD OF THE CONTRACT WITHOUT INITIAL OBJECTION BY THE ARMY, AND THAT THE ARMY'S LATER INDICATION THAT SUCH DELIVERY MIGHT BE NEGOTIABLE, RENDERED THE SPECIFICATION AMBIGUOUS. WE DO NO BELIEVE THAT THE PROTESTER'S UNILATERAL ACT, E.G., PROPOSING TO DELAY THE DELIVERY OF A REQUIRED FEATURE TO BE INCLUDED IN THE HARDWARE, CHANGES THE PLAIN MEANING OF THE SPECIFICATIONS THAT SUCH FEATURE IS "MANDATORY", NOR DO WE BELIEVE THE ARMY'S POTENTIAL WILLINGNESS TO NEGOTIATE THAT POINT OPERATED TO THE PREJUDICE OF TELEFILE. MOREOVER, WE CANNOT CONCLUDE THAT THE REQUIREMENT TO DEMONSTRATE THAT FEATURE ON THE PROPOSED HARDWARE IN THE FACE OF THE ACCEPTABLE WRITTEN PROPOSAL OFFERING LATER DELIVERY CHANGED THE MANDATORY NATURE OF THE REQUIREMENT. LIKEWISE, TELEFILE'S CLAIM OF AMBIGUITY RELATING TO INSTRUCTIONS TO THE TECHNICAL EVALUATORS DID NOT CREATE AN AMBIGUITY IN THE SPECIFICATIONS, NOR DID THEY OPERATE TO THE PREJUDICE OF TELEFILE. CONSEQUENTLY, IN OUR VIEW, THE RECORD DOES NOT SUPPORT A FINDING OF SPECIFICATION AMBIGUITY.

INASMUCH AS WE HAVE CONCLUDED THAT THE PROTESTER FAILED TO DEMONSTRATE THE EQUIPMENT IT PROPOSED, WE NEED NOT CONSIDER ANY OF THE MATTERS RAISED WHICH RELATE TO THE QUESTION OF WHETHER OR NOT THE DEMONSTRATED EQUIPMENT PASSED THE DEMONSTRATION TEST.

THE PROTEST IS DENIED.

GAO Contacts

Edward (Ed) Goldstein
Managing Associate General Counsel
Office of the General Counsel

Kenneth E. Patton
Managing Associate General Counsel
Office of the General Counsel

Media Inquiries

Sarah Kaczmarek
Managing Director
Office of Public Affairs

Public Inquiries