Attachment 3 NGT Section L.pdf
PDF 175 KB Posted
- Attached to
- Next Generation Transponder Federal contract opportunity
- Solicitation number
- W52P1J-19-R-0139
About this file
This solicitation requests proposals for Next Generation Transponder equipment and services. The Army Contracting Command-Rock Island seeks commercial cellular and satellite communications hardware, training, technical engineering services, and warranty support for asset tracking, locating, and health monitoring. Required products include transponders, data collection and processing equipment, and storage retrieval systems. Proposals are due by January 15, 2022 and must follow the specified five-volume format covering technical approach, management, past performance, price, and administrative information. The Department of the Army Materiel Command Joint Munitions Command will award a fixed-price contract for an initial period of one year with four one-year options.
View the file
Other files for this federal contract opportunity
Show all 22
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SECTION L – INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS
L.1. PROPOSAL SUBMISSION INSTRUCTIONS
L.1.1. GENERAL. The Offeror’s Proposal shall be signed and submitted by an individual possessing authority to enter into a contract based on the submitted Proposal on behalf of the Offeror. Each Offeror's Proposal shall be written in English and conform to the instructions below. The Proposal shall be valid for a period of not less than 120 days from the required submission date. Adherence to Proposal instructions is required. Any Proposal found to be missing required elements will not be further evaluated and will not be considered for award.
L.2. PROPOSAL PREPARATION & ORGANIZATION
L.2.1. INTRODUCTION
L.2.1.1. Instructions are in accordance with Federal Acquisition Regulation (FAR) clause 52.212-1, Instructions to Offerors – Commercial Items (Oct 2018).
Notwithstanding FAR clause 52.212-1(e), each Offeror shall submit only one, unique Proposal that addresses all Government requirements outlined in the solicitation, including, but not limited to, the Performance Work Statement (PWS). The Government will not evaluate more than one Proposal from each Offeror. The Offeror's Proposal shall consist of five (5) volumes, as outlined below:
VOLUME FACTOR 1: TECHNICAL
VOLUME FACTOR 2: MANAGEMENT
VOLUME FACTOR 3: PAST PERFORMANCE
VOLUME FACTOR 4: PRICE
VOLUME FACTOR 5: SOLICITATION, OFFER and AWARD DOCUMENT (FORM SF33), and CERTIFICATIONS/REPRESENTATIONS
L.2.1.2 Files shall not contain classified data. The use of hyperlinks in Proposals is prohibited.
L.2.1.3. Proposals shall be submitted electronically, via email, to Julie Lawrence, Procuring Contracting Officer (PCO), at Julie.l.lawrence.civ@mail.mil, and Luke Welling, Contract Specialist, at Luke.m.welling.civ@mail.mil. The Government can only accept individual emails up to 20 MB in size, including the email itself and all attachments. If an Offeror’s Proposal is larger than 20 MB, separate emails are permitted. When submitting multiple emails, the Offeror shall sequentially number each email (e.g., 1 of 3, 2 of 3, etc.). It is incumbent on the Offeror to ensure that the Government has received the complete Proposal BEFORE the solicitation due date and time.
L.2.1.4. LATE SUBMISSIONS. Offerors are responsible for submitting Proposals, and any modifications or revisions to their Proposals, so as to reach the Government office designated in the solicitation by the date and time specified in the solicitation. All late mailto:Julie.l.lawrence.civ@mail.mil mailto:Luke.m.welling.civ@mail.mil submissions, modifications, revisions, and/or withdrawals of offers will be addressed IAW 52.212-1(f).
L.2.1.5. COMMUNICATIONS
L.2.1.5.1. FORMAL COMMUNICATIONS. The solicitation, amendments, notices, and other information will be made available on beta.SAM.gov at https://beta.sam.gov.
L.2.1.5.2. Offerors are advised to monitor the beta.SAM.gov website continuously for any new information regarding this solicitation. Offerors are deemed to have knowledge of all documents related to this solicitation that are posted to beta.SAM.gov.
L.2.1.5.3. SOLICITATION AMENDMENT. Should an amendment be issued against the solicitation, the Offeror shall acknowledge the amendment by signing the Standard Form (SF) 30, Amendment of Solicitation/Modification of Contract, and including it in Volume 5 of the Proposal submission.
L.2.1.5.4. SOLICITATION QUESTIONS. All questions pertaining to this solicitation shall be addressed to the PCO, Julie Lawrence, at Julie.l.lawrence.civ@mail.mil, and to the Contract Specialist, Luke Welling, at luke.m.welling.civ@mail.mil, and shall be submitted not later than seven days after release of the solicitation. The Government is not obligated to provide responses to all questions submitted by Offerors, but will consider them and incorporate changes into the solicitation as the Government deems necessary in its sole discretion. Government responses to questions will be posted at https://beta.sam.gov for review by all Offerors. Therefore, questions/comments shall not be marked with a restrictive legend, and shall not include proprietary information.
When submitting questions and comments, please reference the specific text of the Request for Proposal (RFP) in the following format:
Subject: Solicitation No. W52P1J-19-R-0139 Reference: RFP Section ___, Paragraph(s) ____, Page(s) ____.
It is preferred that only one set of questions be submitted by each Offeror, instead of multiple sets of questions.
L.2.1.5.5. A separate tool, the ASSIST2Industry, may be used in conjunction with ASSIST to accomplish all exchanges with Offerors after receipt of Proposals pursuant to FAR 15.306. ASSIST2Industry provides the ability for the Government to issue, and the Offerors to receive and respond to, all Evaluation Notices (ENs) in a secure online environment. If ASSIST2Industry is utilized, instructions will be provided to Offerors on how to obtain access to ASSIST2Industry prior to the issuance of any EN.
L.2.1.5.6. Offerors may receive questions seeking clarification, or they may receive questions as part of ENs if the Government decides to conduct discussions and the https://beta.sam.gov/ mailto:Julie.l.lawrence.civ@mail.mil mailto:luke.m.welling.civ@mail.mil https://beta.sam.gov/
Offeror remains in the competitive range. Responses to ENs, and any resulting Proposal revisions, must be provided IAW the following instructions:
The Offeror must provide a complete response within the EN response field, and include an explanation of any revisions to the Offeror’s Proposal. The Offeror may not simply provide references to the revisions in the Offeror’s Proposal. If a response to an EN requires a revision to the Offeror’s Proposal, the Offeror must provide a reference in the EN response to the location (e.g., Volume#, Section#, Paragraph#) of the revision in the Offeror's Proposal. NOTE: To be considered and evaluated as part of the Offeror's Proposal, revisions must be made in the Offeror's Proposal submission, and the Offeror must still conform to the page format/limitation requirements.
The Offeror must attach the complete resubmission file, containing all the Proposal revisions for each volume, as an attached file with the Offeror’s reply to the last EN for the respective volume (i.e., the Offeror may submit only one attached file per volume, using the same file structure as the Offeror’s initial submission). The Offeror may not submit change pages or multiple copies of the Offeror's revised Proposal. Offerors are requested to limit changes to items identified in the EN. For clarity purposes, Offerors are required to clearly identify changes/additions in the Offeror's resubmission Proposal (e.g., by using track changes to the show date, a vertical line in the margin, bolded or underlined text, and/or redline and strikeout features).
Each revision on each revised page shall be identified by date (DD/MM/YY) and by revision number, which shall be done by adding a footer to indicate such revision (i.e., date of submission of the revision) for each file affected. Offerors shall also place their name within the header or footer of each page, along with the section number.
L.2.1.5.8. After all ENs have been issued and responses submitted, Offerors shall submit Final Proposal Revisions (FPRs) in accordance with the PCO’s FPR request letter.
L.3. PROPOSAL FILES
L.3.1. FORMAT
L.3.1.1. The submission shall be clearly indexed, logically assembled and comply with the instructions contained in Section L.
Each volume shall be clearly identified, and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and solicitation number in the header and/or footer.
Each volume shall consist of a Title Page, a Table of Contents, and the respective volume’s submission. The Table of Contents shall be created using, or compatible with, the Microsoft (MS) Word 2013 Table of Contents feature. The Title Page and Table of
Contents are excluded from the page limitations specified in Table 1.1. Electronic files shall use the following page set-up parameters:
Margins Top, Bottom, Left, Right 1” Gutter 0” From Edge Header, Footer 1” Page Size, Width 8.5” Page Size, Height 11”
The Government will upload the electronic version of each Proposal into the ASSIST tool. Members of the Source Selection Team will use the Proposal version in the ASSIST tool to conduct evaluations. The Government reserves the right to adjust the electronic version of an Offeror’s Proposal to conform to the guidelines listed throughout Section L.3.1. Information that exceeds the authorized page counts following any adjustment will be disregarded, and will not be evaluated.
L.3.1.2. The following additional restrictions apply:
(a) Paragraphs shall be separated by at least one blank line.
(b) A standard, 12-point minimum font size is required, except as noted in subsection (d), below.
(c) Arial font is required.
(d) Tables, Figures, and Illustrations may be landscape layout, and may use a reduced font size (not less than 8-point font).
(e) Tables, Figures, and Illustrations should be labeled/titled and referenced.
(f) Tables, Charts, Figures, etc. should be used for tabular type data only, and should not include narratives. Narratives are more appropriately placed in the body of the Proposal.
(g) Any text, table, chart, figure, etc. that does not comply with the above restrictions will not be evaluated.
(h) Offerors shall ensure that the print for the entire Proposal is easily readable, without magnification. If it is unreadable, it will not be evaluated.
L.3.1.3. Digital files shall be compatible with MS Office 2013, and PDF files shall be compatible with Adobe Acrobat DC (version 2019 or later). Each Offeror shall add its respective company name to the file names listed in Table 1.1 (i.e., Company Name V1A1.docx). For purposes of printing the Proposal, charts and foldouts shall conform to L.3.1.4 and L.3.1.5.
L.3.1.4. MS Excel worksheets are considered one page each for page count purposes.
MS Project GANTT/PERT charts are excluded from the page count restrictions.
L.3.1.5. Foldouts (pages larger than 8 1/2" x 11", but not greater than 11 x 17), not including MS Excel worksheets, may be included within the volumes, if needed for clarification, and will not be included in the page counts. Foldouts shall not exceed five per volume. Any foldouts exceeding this limit will not be considered. Foldouts (i.e., diagrams, charts, graphs) shall not be used as a substitute for narrative text.
L.3.2. FILE PACKAGING.
L.3.2.1. To be considered for selection, the Offeror must submit a complete response to this solicitation, using the sequence and format instructions provided in this section. The Proposal shall be divided into separate volumes and provided in the format specified below in Table 1.1.
L.3.2.2. Table 1.1 Volume No. / Title File
Name File Format Maximum # of Pages
Volume 1 – TECHNICAL V-1 Searchable
Title Page and Table of Contents V-1-1 Excluded from page limit.
Hardware Table V-1-2 See L.5.1.1.
Hardware Narrative V-1-3 See L.5.1.2.
Hardware Technical Data Sheets V-1-4 See L.5.1.3. (Excluded from page limit.)
Relevant Assurances – Technical V-1-5 See L.5.1.4.
Volume 2 – MANAGEMENT V-2 Searchable
Title Page and Table of Contents V-2-1 Excluded from page limit.
Management Support Plan V-2-2 See L.5.2.1.
Customer Support V-2-3 See L.5.2.2.
Warranty V-2-4 See L.5.2.3.
Volume 3 – PAST PERFORMANCE V-3 Searchable
No page limit; submit pages (i.e., PPQs), as required.
Title Page and Table of Contents V-3-1 Excluded from page limit.
References V-3-2 See L.5.3.
Volume 4 – PRICE V-4 No page limit; submit pages (i.e., Matrix), as required.
Title Page and Table of Contents V-4-1 Searchable
Excluded from page limit.
Price Matrix V-4-2 MS Excel See L.5.4.
Volume 5 – ADMINSTRATIVE V-5 MS
Searchable Format
No page limit; submit pages, as required.
Title Page and Table of Contents V-5-1 Excluded from page limit.
Volume No. / Title File Name
File Format Maximum # of Pages
Cover Letter V-5-2 See L.5.5.1.
Standard Form 33 (SF33) V-5-3 See L.5.5.2.
Contract Data Administration V-5-4 See L.5.5.2.
Fill-in Contract Clauses V-5-5 See L.5.5.2.1.
Reps./Certs./Disclosures V-5-6 See L.5.5.2.
Solicitation Amendments V-5-7 See L.5.5.2.
Additional Information V-5-8 See L.5.5.3.
L.4. PROPOSAL CONTENT
L.4.1. GENERAL
Each Offeror is required to submit Technical, Management, Past Performance, and Price Proposals, as outlined below. The Offeror shall be held responsible for the validity of all information supplied in its Proposal, including information provided by potential Subcontractors. The Government does not assume the duty to search for data to cure problems it finds in the Offeror’s Proposal. The burden of providing thorough and complete information remains with the Offeror.
L.4.2. WRITTEN PROPOSAL PREPARATION & ORGANIZATION.
L.4.2.1. The Offeror's Proposal shall be submitted in separate volumes, as set forth in Section L.2.1.1. and Table 1.1. All information pertaining to a particular volume shall be confined to that volume to facilitate independent evaluations.
The Government will evaluate the information contained in each volume separately. Therefore, each volume must stand on its own.
To minimize Proposal size, duplication of statements within a Proposal volume may be avoided by referencing that statement's location after it appears in full text for the first time. Offerors should confine their submissions to essential matters, sufficient to define the Proposal and provide an adequate basis for evaluation. Offerors must not merely re-state the requirements stated in the RFP. Narratives must establish demonstrable evidence in support of any statements relating to promised capabilities or performance.
Unsupported statements to comply with the contractual requirements will not be adequate. Offerors shall provide information by addressing the Factors in the format and sequence identified in the solicitation.
L.4.2.2. No classified material shall appear anywhere within the Proposal.
L.4.2.3. No price information shall be presented in any part of the Proposal, except Volume 4 (Price).
L.5. VOLUMES
L.5.1. VOLUME 1 – TECHNICAL
L.5.1.1. HARDWARE.
The hardware offered shall demonstrate the Offeror’s technical capability and understanding of the hardware requirements specified in the PWS. The Offeror must demonstrate the ability to provide the hardware identified for active Next Generation Transponder (NGT) equipment for the Department of Defense (DoD), the U.S. Coast Guard (USCG), the North Atlantic Treaty Organization (NATO), Coalition Partners, and other Federal Agencies in dynamic, global NGT environments, as stated in the PWS (reference Section J, Attachment 0001).
For all Hardware, the Offeror shall provide a Table, in MS Excel format, listing all proposed equipment. The Hardware Table column headings shall be labeled as follows:
(a) Contract Item Line Number (CLIN). Each row of the table shall list CLINs in the same sequence as found in the "Price Model" (reference Section J, Attachment 0002)
(b) Make and Model Number(s)
(c) Hardware Description
(d) Hardware – PWS Reference
(e) Hardware – Meets Requirements*
(f) Hardware – Exceeds Requirement*
(g) Operating Environment – PWS Reference (Additional Columns can be added as necessary)
(h) Operating Environment – Meets Requirement*
(i) Operating Environment – Exceeds Requirement*
* The Offeror shall indicate in the Table that all proposed hardware meets and/or exceeds the Hardware requirements contained within the PWS.
L.5.1.2. For each proposed Hardware item or Operating Environment (see PWS Section 3.4) exceeding a requirement, the Offeror shall provide, a separate narrative explaining exactly how the requirement is exceeded, and how exceeding the requirement is of value to the Government. Narratives shall reference the associated CLIN(s) and Table line item(s).
L.5.1.3. Separate from the Table, the Offeror shall provide Technical Data Sheets for all hardware offered. Each Technical Data Sheet shall be labeled with its associated hardware CLIN(s).
L.5.1.4 RELEVANT ASSURANCES – TECHNICAL
The Offeror shall provide information regarding their experience providing equipment for CLINs 0001, 0002, 0003, and 0007 by providing the following:
1. Number (quantity) of each transponder the Offeror has in use.
2. Location(s) where the Offeror’s transponders are in use.
3. Problems encountered with the Offeror’s transponders, and the Offeror’s corresponding resolution(s).
4. The Offeror’s technical acumen with each transponder.
L.5.2. VOLUME 2 – MANAGEMENT
L.5.2.1. MANAGEMENT SUPPORT PLAN. The Offeror shall provide a detailed Management Support Plan, outlining its management approach and understanding of the PWS requirements. The Offeror must demonstrate that their management methodology and processes are sufficient to ensure that contract oversight will be maintained for DoD, the USCG, NATO, Coalition Partners, and other Federal Agencies in dynamic, global NGT environments, and the requirements stated in the PWS will be met. The Offeror shall cite specific examples of project management practices, beyond standard project management practice models, that are beneficial and specific to DoD, the USCG, NATO, Coalition Partners, and other Federal Agencies.
The Offeror’s management approach shall demonstrate a sound and workable management concept that is capable of meeting the requirements of the PWS. A strong Proposal shall demonstrate a high degree of thoroughness, soundness, and comprehension of the requirements, indicating a high likelihood of success.
L.5.2.2. CUSTOMER SUPPORT. The Offeror shall describe how they plan to ensure the customer support requirements in Sections 15.2 and 15.3 of the PWS will be met.
Specifically, the Offeror shall describe their proposed customer support processes, including their proposed processes for implementing and managing the required help desk and website portal.
L.5.2.3. WARRANTY. The Offeror shall describe how they plan to meet the warranty support requirements specified in Section 16 of the PWS, to include their procedures for addressing warranty issues and communicating with end-users worldwide.
L.5.3. VOLUME 3 – PAST PERFORMANCE
L.5.3.1. CONTRACT REFERENCES: The Offeror shall submit no more than three contract references with its initial Proposal. Each reference must demonstrate the Offeror’s recent, relevant performance under a Government (Federal, state, local) and/or commercial contract. Contract references shall be submitted on the Past Performance Questionnaire (reference Section J, Attachment 0006).
NOTE: It is recommended that Offerors limit references to those involving its performance as a prime or first tier Subcontractor, unless the Offeror has no other references.
L.5.3.1.1. Recent definition (reference Section M.7.3.2).
L.5.3.1.2. Relevant definition (reference Section M.7.3.3).
L.5.3.1.3. The following information is required with respect to each contract reference:
(a) Project Name,
(b) Awarding Agency/Organization,
(c) Award Date,
(d) The One to Two-Year Period of Performance to be reviewed,
(e) Total Annual Contract Value for the Period of Performance to be reviewed,
(f) Contract Number (include task/delivery order number in the case of Indefinite
Delivery, General Service Administration (GSA), or Blanket Purchase Agreement (BPA) type contracts),
(g) Whether the Offeror performed as the Prime Contractor or as a Subcontractor,
(h) The Offeror’s primary responsibilities,
(i) The nature of the work, to include a description of the contract’s relevance to the current requirement,
(j) Contract Type (fixed price, cost reimbursable, time and materials, etc.), and
(k) Place of Performance.
L.5.3.1.4. Provide Point of Contact (POC) information for each reference, to include:
(a) Name of Procuring Contract Officer (PCO) and Technical POC (TPOC) to whom services are/were provided,
(b) Current phone numbers for PCO and TPOC, and
(c) Email addresses for PCO and TPOC.
L.5.3.2. The contract information to be provided with each contract reference is on the "Past Performance Questionnaire" (reference Section J, Attachment 0006). The Offeror is required to complete a separate questionnaire for each contract reference. Only the stated information is to be completed by the Offeror. The remaining information will be completed by the questionnaire respondent. The questionnaire respondent(s) shall be requested to submit questionnaires directly to the Government POCs (reference L.2.1.3.) for this requirement no later than the Proposal submission due date.
L.5.3.3. ADVERSE GOVERNMENT CONTRACT PERFORMANCE – In addition to the Offeror’s submitted contract references, the Offeror shall identify every recent and relevant Government contract it was awarded that experienced any performance problems related to deliverables or services, and every recent contract that was terminated (except those contracts terminated for the convenience of the Government), in whole or in part within the three (3) years prior to the issuance of the RFP. The number of contract references provided in response to this section is unlimited. If there are no contracts meeting the adverse performance description, the Offeror must state that there are no contracts meeting the adverse performance description.
For any contract falling under the adverse performance description, provide all of the information listed in Sections L.5.3.1.3. and L.5.3.1.4., plus:
(a) Provide a copy of any cure notices or show cause letters received,
(b) Provide a copy of any Contract Deficiency Report (CDR),
(c) Identify the reason for the termination (except those contracts terminated for the convenience of the Government),
(d) State any corrective actions taken to avoid recurrence,
(e) Describe the extent to which the corrective action was successful, identifying
POCs who can confirm the success of the corrective measures, and
(f) Describe, in detail, any performance problems that included internal/external customer complaints and/or CDRLs.
L.5.3.4. New Corporate Entities – New corporate entities may submit data on prior contracts involving its officers and employees. In addition to the other requirements in this section, however, the Offeror shall discuss, in detail, the role performed by such persons in the prior contracts cited. Information shall be included, as described in the Sections L.5.3.1.3. and L.5.3.1.4.
L.5.4. VOLUME 4 – PRICE PROPOSAL
L.5.4.1. Offerors shall submit their Price Proposal using the "Price Model" (reference Section J, Attachment 0002).
L.5.4.2. Offerors shall not add any CLINs/Sub-CLINs to the “Price Model.”
L.5.4.3. The prices shall be provided with no more than two (2) decimal places. An Offeror's Proposal may be rejected if the proposed prices are provided with more than two (2) decimal places.
L.5.4.4. There is no page limit for the Price Proposal, as the Offeror’s completed Price Matrix is the Price Proposal. Offerors shall not submit a narrative of any kind with their Price Proposal.
L.5.4.5. The proposed pricing for the incidental material, expedited delivery, and travel is Cost Reimbursable and Non-Fee bearing.
L.5.5. VOLUME 5 – SOLICITATION, OFFER AND AWARD (Form SF 33)
DOCUMENT AND CERTIFICATIONS/REPRESENTATIONS
L.5.5.1. The Offeror shall provide a Cover Letter, which clearly states that: (1) the individual signing the certifications and representations listed below has the authority to enter into a contract on the Offeror’s behalf; and (2) the Offeror’s Proposal validity date, which shall be for a period of not less than 120 days from the required submission date.
L.5.5.1. Certifications and Representations: Each Offeror shall complete (fill in and sign) the solicitation sections indicated below using the file provided with the solicitation, without modification. An authorized official of the Offeror shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission. The format specified in Section L.3.1.1 does not apply to Volume 5.
(a) Section A – "Solicitation, Offer and Award" – Standard Form 33 (SF 33)
(b) Section G – Contract Administration Data
(c) Section I – Fill-in clauses only
(d) Section K – Representations, Certifications and Other Statements of Offerors
(e) All solicitation amendments issued, if any
L.5.5.2. Additional information for Volume 5:
L.5.5.2.1.The Offeror shall provide any certifications/corporate agreements it has with participating commercial firms.
L.5.5.2.2.The Offeror shall provide letters of commitment between the prime and its major Subcontractors, as well as joint venture agreements if the prime is a joint venture.
L.5.5.2.3. Any Contractor (or member of its team and/or Subcontractor) having a Conflict of Interest, as defined under FAR Part 9.5, must identify the conflict as soon as it is known and provide a recommended mitigation plan. The Offeror shall submit a mitigation plan (no page limit) for any potential conflicts of interest known by the Offeror at the time they submit their Proposal.
L.5.5.2.4. Offerors are advised that employees of Engility Corporation may serve as non-government advisors in the submission evaluation process. These individuals will be authorized access only to those portions of the submission data and discussions that are necessary to enable them to perform their respective duties. This firm is expressly prohibited from competing on the subject acquisition.
Engility Corporation 35 New England Business Center Drive, Suite #200 Andover, MA 01810-1071 Cage Code: 4A457
In accomplishing their duties related to the submission evaluation process, the aforementioned firm may require access to proprietary information contained in an Offeror's submission. The identified support Contractor will be required to protect an Offeror's information from unauthorized use or disclosure for as long as it remains proprietary, and refrain from using the information for any purpose other than that for which it was furnished.
All Contractor personnel included in the submission evaluation process are required to sign a Nondisclosure Agreement (NDA), Conflicts of Interest Statement, and Rules of Conduct Certificate. The agreement requires the participating individuals to protect source selection and proprietary information IAW the Procurement Integrity Act.
IAW FAR 9.505-4(b), each Offeror shall enter into a written agreement with Engility Corporation to permit disclosure of the Offeror's Proposal to the identified support Contractor for the purpose of evaluation, and shall submit the executed agreement with their Proposal.
***END OF NARRATIVE L0001***
Title Regulatory Cite Title Date
L-1 52.215-1 INSTRUCTIONS TO OFFERORS—COMPETITIVE
JAN/2004
L-2 52.233-2 SERVICE OF PROTEST
SEP/2006
(a) Protests, as defined in section 33.101 of the Federal Acquisition Regulation, that are filed directly with an agency, and copies of any protests that are filed with the Government Accountability Office (GAO), shall be served on the PCO (addressed as follows) by obtaining written and dated acknowledgment of receipt from PCO.
(b) The copy of any protest shall be received in the office designated above within one day of filing a protest with the GAO.
(End of Provision)
L-6 52.215-4583 DISCLOSURE OF UNIT PRICES (ACC-RI)
FEB/2004
Unless the Offeror notifies the PCO, prior to submission of its initial Proposal, of an objection to disclosure of its unit price, it is the Government's intent to publicly release (which would include, but is not limited to, a public award synopsis, Contractor debrief, procurement history web posting, or Freedom of Information Act (FOIA) request) the unit price(s) stated in the contract awarded under this solicitation. Any objection must be submitted in writing, providing a detailed explanation of how release of the awarded unit price would result in a substantial competitive harm to the Contractor.Objections will be reviewed to determine whether harm has been substantiated. Failure to timely notify the PCO waives any objection to disclosure of the unit price. A "unit price" is defined as the specified amount to be paid by the Government for the goods or services stated per unit, contract line item, or separately identified contract deliverable. The term "unit price" does not include any information on how the unit price was determined. This constitutes notification pursuant to Executive Order 12600.
(End of provision)
File details come from the government source that posted it. Updated .