Skip to main content

B-208237, APR 19, 1983

B-208237 Apr 19, 1983
Jump To:
Skip to Highlights

Highlights

PROTEST IS UNTIMELY WHERE PROTESTER LEARNED OF REQUIREMENTS TO BE IMPOSED ON BENCHMARK DURING PRE-BENCHMARK DISCUSSIONS BUT WAITED UNTIL AFTER DATE SET FOR BENCHMARK TO PROTEST. 2. SINCE IT IS NOT ALWAYS FEASIBLE TO SCHEDULE BENCHMARKING ON A DATE THAT IS COMMON TO ALL OFFERORS. THE ACTIONS COMPLAINED OF LED TO THE REJECTION OF FEDERAL DATA'S PROPOSAL WHEN IT WAS UNABLE TO INITIATE A BENCHMARK OF ITS PROPOSED EQUIPMENT BY JUNE 30. FEDERAL DATA ALLEGES THAT THE NAVY IMPROPERLY INSISTED THAT IT FURNISH VARIOUS ITEMS OF PERIPHERAL EQUIPMENT FOR THE BENCHMARK WHICH WERE NOT REQUIRED BY THE BENCHMARK PROVISIONS OF THE RFP. WERE IT TO PROPOSE A BENCHMARK DATE BEYOND JUNE 30. ADVISING THE NAVY THAT IT BELIEVED IT WAS NOT REQUIRED TO BENCHMARK SPECIFIC PERIPHERAL EQUIPMENT.

View Decision

B-208237, APR 19, 1983

DIGEST: 1. PROTEST IS UNTIMELY WHERE PROTESTER LEARNED OF REQUIREMENTS TO BE IMPOSED ON BENCHMARK DURING PRE-BENCHMARK DISCUSSIONS BUT WAITED UNTIL AFTER DATE SET FOR BENCHMARK TO PROTEST. 2. SINCE IT IS NOT ALWAYS FEASIBLE TO SCHEDULE BENCHMARKING ON A DATE THAT IS COMMON TO ALL OFFERORS, THE TIME SET FOR BENCHMARKING EACH OFFEROR'S EQUIPMENT CONTROLS THE "NEXT CLOSING DATE" FOR THE PURPOSE OF GAO BID PROTEST PROCEDURES.

FEDERAL DATA CORPORATION:

FEDERAL DATA CORPORATION PROTESTS ACTIONS OF THE DEPARTMENT OF THE NAVY AUTOMATIC DATA PROCESSING SELECTION OFFICE IN CONNECTION WITH REQUEST FOR PROPOSALS (RFP) N66032-R-0003 FOR VARIOUS COMPUTER EQUIPMENT. THE ACTIONS COMPLAINED OF LED TO THE REJECTION OF FEDERAL DATA'S PROPOSAL WHEN IT WAS UNABLE TO INITIATE A BENCHMARK OF ITS PROPOSED EQUIPMENT BY JUNE 30, 1982. WE DISMISS THE PROTEST AS UNTIMELY.

THE PROTESTER RAISES THREE SUBSTANTIVE CONCERNS. FIRST, FEDERAL DATA ALLEGES THAT THE NAVY IMPROPERLY INSISTED THAT IT FURNISH VARIOUS ITEMS OF PERIPHERAL EQUIPMENT FOR THE BENCHMARK WHICH WERE NOT REQUIRED BY THE BENCHMARK PROVISIONS OF THE RFP. SECOND, FEDERAL DATA CONTENDS THAT THE NAVY IMPROPERLY IMPOSED AN ADDITIONAL REQUIREMENT THAT IT BENCHMARK ITS PROPOSED IBM 4341 AND AMDAHL V-7 CPUS "CONCURRENTLY AT THE SAME SITE." FINALLY, FEDERAL DATA COMPLAINS THAT THE NAVY IMPOSED UNREASONABLE TIME RESTRICTIONS ON IT FOR BENCHMARK COMPLETION EVEN THOUGH THE RFP DID NOT ESTABLISH A DATE FOR COMPLETION OF BENCHMARKING.

THE RECORD SHOWS THAT, SUBSEQUENT TO EVALUATION OF INITIAL PROPOSALS, FEDERAL DATA WROTE THE NAVY ON MAY 28, 1982 REQUESTING PERMISSION TO USE FOR BENCHMARKING CERTAIN PERIPHERAL EQUIPMENT, INCLUDING DISK DRIVES, PRINTERS AND TERMINALS WHICH DIFFERED FROM THAT PROPOSED. ON JUNE 4, 1982, THE NAVY REJECTED ANY SUBSTITUTION AS INAPPROPRIATE IN VIEW OF THE LATE DATE OF THE REQUEST AND DEMANDED THAT FEDERAL DATA AGREE TO A FIRM BENCHMARK SCHEDULE BY THE CLOSE OF BUSINESS ON JUNE 8. FURTHER, THE NAVY ADVISED FEDERAL DATA THAT, WERE IT TO PROPOSE A BENCHMARK DATE BEYOND JUNE 30, 1982, IT MIGHT JEOPARDIZE ITS FURTHER PARTICIPATION IN THE PROCUREMENT.

IN RESPONSE, FEDERAL DATA WROTE THE NAVY ON JUNE 8, 1982, ADVISING THE NAVY THAT IT BELIEVED IT WAS NOT REQUIRED TO BENCHMARK SPECIFIC PERIPHERAL EQUIPMENT. THE LETTER REQUESTED NAVY CONCURRENCE IN A PROPOSED BENCHMARK SCHEDULE PREDICATED ON FEDERAL DATA'S BELIEF THAT IT HAD THE RIGHT TO USE WHATEVER PERIPHERAL EQUIPMENT IT DEEMED APPROPRIATE. IT ENCLOSED AN UNSIGNED SECOND LETTER ADDRESSED TO OUR OFFICE PROTESTING THAT THE BENCHMARK WAS TO BE CONDUCTED IN A MANNER WHICH, BECAUSE OF DIFFICULTY IN OBTAINING IBM EQUIPMENT, WAS CALCULATED TO FAVOR IBM OR A CONTRACTOR TEAMED WITH IT. WERE THE DISPUTE NOT RESOLVED BY JUNE 11, 1982, THE LETTER CONCLUDED:

"WE HAVE NO CHOICE AND MUST GO AHEAD AND FILE THIS WITH GAO. A PROTEST IS A VERY SERIOUS MATTER THAT WE AT FEDERAL DATA TAKE ONLY AS A VERY LAST RESORT, AFTER UTILIZING WHATEVER MEANS NECESSARY TO RESOLVE THE ISSUES IN A MUTUALLY AGREEABLE FASHION.

THE JUNE 8, 1982 FEDERAL DATA LETTER RESULTED IN A MEETING BETWEEN FEDERAL DATA AND NAVY PERSONNEL AFTER WHICH, ON JUNE 10, THE NAVY WROTE THE PROTESTER ADVISING IT THAT IT WOULD BE PERMITTED TO SUBSTITUTE A PRINTER, TERMINAL AND 24 DISK STORAGE MACHINES FOR THE BENCHMARK. THE NAVY INSISTED, HOWEVER, THAT ALL OTHER EQUIPMENT BE THAT PROPOSED. MOREOVER, RESPONDING TO A COMMENT MADE BY FEDERAL DATA AT THE CLOSE OF THE MEETING, THE NAVY ADVISED FEDERAL DATA THAT BOTH THE AMDAHL V-7 AND IBM 4341 "MUST BE BENCHMARKED CONCURRENTLY AT THE SAME SITE."

ON JUNE 16, FEDERAL DATA WROTE THE NAVY AGREEING TO A JUNE 29-30 BENCHMARK SCHEDULE. IT ADVISED THE NAVY THAT IT WOULD NOT BE ABLE TO FIND COLLOCATED EQUIPMENT BUT WAS ATTEMPTING TO LOCATE AN IBM MACHINE NEAR THE AMDAHL CORPORATION BENCHMARK FACILITY WHERE THE V-7 WOULD BE TESTED. JUNE 21 FEDERAL DATA HAD FOUND A WEST COAST IBM SITE BUT ONE WHICH DID NOT HAVE CERTAIN SOFTWARE REQUIRED FOR THE TEST. ALSO, FEDERAL DATA HAD ENCOUNTERED DIFFICULTY IN OBTAINING SOME OF THE EQUIPMENT WHICH THE NAVY HAD REQUIRED BE USED IN THE JUNE 10 LETTER. FEDERAL DATA PROPOSED, THEREFORE, TO MAKE FURTHER SUBSTITUTIONS OF PERIPHERAL EQUIPMENT AND ASKED THE NAVY FOR PERMISSION TO DEFER THE IBM PORTION OF THE TEST UNTIL THE SOFTWARE COULD BE OBTAINED.

THE NAVY REJECTED FEDERAL DATA'S REQUESTS IN A LETTER DATED JUNE 22, 1982, IN WHICH IT ADVISED FEDERAL DATA THAT:

"THE NAVY'S POSITION REMAINS AS STATED IN THE 10 JUNE 1982 LETTER. YOUR EXPLICIT REPLY IS REQUESTED AS TO WHETHER YOUR COMPANY CAN OR CANNOT BENCHMARK YOUR PROPOSED EQUIPMENT DURING THE WEEK OF 28 JUNE 1982. IF YOU CANNOT MEET THE CONDITIONS AGREED UPON FOR THE BENCHMARK, THEN YOUR PROPOSAL MAY NO LONGER BE CONSIDERED."

IN RESPONSE, FEDERAL DATA'S MARKETING MANAGER CALLED THE NAVY TO ADVISE THAT IT WOULD NOT BE ABLE TO PERFORM THE BENCHMARK PRIOR TO JUNE 30. THE NAVY SUBSEQUENTLY REJECTED FEDERAL DATA'S PROPOSAL WHEN THE COMPANY DID NOT INITIATE THE BENCHMARK.

OUR BID PROTEST PROCEDURES, 4 C.F.R. 21.2(B), REQUIRE THAT PROTESTS BASED ON ALLEGED IMPROPRIETIES IN A NEGOTIATED PROCUREMENT WHICH DO NOT EXIST IN THE INITIAL SOLICITATION BUT WHICH ARE SUBSEQUENTLY INCORPORATED THEREIN MUST BE PROTESTED NOT LATER THAN THE NEXT CLOSING DATE FOR THE RECEIPT OF PROPOSALS FOLLOWING THE INCORPORATION. WHEN THE ALLEGED IMPROPRIETIES CONTAIN THE GROUND RULES OR REQUIREMENTS FOR BENCHMARKING, THE "NEXT CLOSING DATE" IS THE DATE SET FOR THE BENCHMARKING. INFORMATION INTERNATIONAL, INC., 59 COMP.GEN. 640 (1980), 80-2 CPD 100. HERE WE THINK IT IS CLEAR THAT FEDERAL DATA KNEW NOT LATER THAN WHEN IT RECEIVED THE NAVY'S JUNE 22 LETTER THAT THE NAVY WAS INSISTING ON THE BENCHMARKING REQUIREMENTS IT PREVIOUSLY IMPOSED. THEREFORE, FEDERAL DATA WAS REQUIRED TO FILE A PROTEST PRIOR TO THE JUNE 30 BENCHMARKING DEADLINE. FEDERAL DATA DID NOT FILE A PROTEST, HOWEVER, UNTIL JULY 13. CONSEQUENTLY, WE CONSIDER THE PROTEST TO BE UNTIMELY.

FEDERAL DATA ARGUES THAT JUNE 30 SHOULD NOT BE CONSIDERED A CLOSING DATE SINCE IT WAS NOT GIVEN A FORMAL "NOTICE OF ESTABLISHMENT OF CLOSING DATE FOR COMPLETION OF BENCHMARKING," AND BECAUSE ALL OFFERORS WERE NOT NOTIFIED OF JUNE 30 AS A CLOSING DATE.

WE FIND NO MERIT TO FEDERAL DATA'S ASSERTIONS. THERE IS NO REQUIREMENT THAT SUCH A FORMAL NOTICE BE PROVIDED. ALL THAT IS NEEDED, WE THINK, IS THAT AN OFFEROR BE GIVEN REASONABLE NOTICE OF THE ESTABLISHMENT OF A DEADLINE. SEE THE FMI-HAMMER JOINT VENTURE, B-206665, AUGUST 20, 1982, 82-2 CPD 160 (ORAL NOTIFICATION OF A CLOSING DATE FOR BEST AND FINAL OFFERS IS SUFFICIENT, ABSENT PREJUDICE). MOREOVER, WHILE IN MOST CIRCUMSTANCES A COMMON CLOSING DATE MUST BE ESTABLISHED (E.G., IN SETTING A DATE FOR RECEIPT OF BEST AND FINAL OFFERS), THE USE OF A COMMON DATE FOR BENCHMARKING IS OFTEN NOT FEASIBLE BECAUSE BENCHMARKS MUST BE SCHEDULED ON DIFFERENT DAYS. IT FOLLOWS THAT IF BENCHMARKING IS TO BE CONSIDERED AS A CLOSING DATE FOR THE PURPOSE OF THE FILING DEADLINES SPECIFIED IN OUR BID PROTEST PROCEDURES, THE TIME SET FOR EACH INDIVIDUAL OFFEROR MUST CONTROL. FN1

FEDERAL DATA ALSO MAINTAINS THAT IT DID PROTEST TO THE NAVY PRIOR TO JUNE 30, WHEN ITS MARKETING MANAGER CALLED THE NAVY TO ADVISE IT THAT IT WOULD NOT BE POSSIBLE TO PERFORM THE BENCHMARK PRIOR TO JUNE 30. THIS CONVERSATION, IT MAINTAINS, SHOULD BE TREATED AS AN ORAL PROTEST.

WHILE ORAL PROTESTS TO A CONTRACTING ACTIVITY ARE PERMITTED, A PROTESTER'S INTENT TO PROTEST MUST BE CLEAR. JOULE TECHNICAL CORPORATION, 58 COMP.GEN. 550 (1979), 79-1 CPD 364. FEDERAL DATA'S ATTEMPT TO CHARACTERIZE THE TELEPHONE CONVERSATION AS A PROTEST IS CONTRADICTED BY CONTEMPORANEOUS NAVY RECORDS WHICH INDICATE THAT FEDERAL DATA WAS ASKED IF IT INTENDED ITS ACTIONS TO BE TREATED AS A PROTEST AND RESPONDED THAT IT DID NOT. FEDERAL DATA HAS NOT OFFERED ANY EVIDENCE TO REBUT THE NAVY'S RECORD. WE FIND THAT NO ORAL PROTEST WAS MADE.

FINALLY, WE NOTE THAT FEDERAL DATA CONTENDS THAT IF WE FIND THE PROTEST TO BE UNTIMELY, WE SHOULD CONSIDER IT UNDER SEC. 21.2(C) OF OUR BID PROTEST PROCEDURES (4 C.F.R. SEC. 21.2(C)) WHICH ALLOWS CONSIDERATION OF UNTIMELY PROTESTS THAT PRESENT AN ISSUE WHICH IS SIGNIFICANT TO PROCUREMENT PRACTICE OR PROCEDURE. THE EXCEPTION, WHICH IS INVOKED SPARINGLY, CONTEMPLATES A PROTEST CONCERNING A PROCUREMENT PRINCIPLE OF WIDESPREAD INTEREST OR AN ISSUE WHICH AFFECTS A BROAD CLASS OF PROCUREMENTS AND WHICH HAS NOT BEEN DECIDED PREVIOUSLY. KEMP INDUSTRIES, INC., B-206653, MARCH 19, 1982, 82-1 CPD 262. THE QUESTIONS RAISED HERE CONCERN THE PROPER INTERPRETATION AND APPLICATION OF SOLICITATION LANGUAGE AND THE POSSIBLE RESTRICTIVENESS OF THE NAVY'S REQUIREMENTS - ALL QUESTIONS WHICH HAVE BEEN FREQUENTLY CONSIDERED IN PRIOR DECISIONS. THE EXCEPTION, THEREFORE, DOES NOT APPLY.

THE PROTEST IS DISMISSED.

FN1 IN THIS INSTANCE, ONLY FEDERAL DATA WAS AFFECTED BY THE END OF JUNE CUT OFF DATE BECAUSE ALL OTHER BENCHMARKING HAD BEEN COMPLETED IN MAY.

GAO Contacts

Office of Public Affairs