Attach F Proprietary & Confidential Form.pdf
PDF 31 KB Posted
- Solicitation number
- 59878
- Issued by
- Newport News City, Virginia
About this file
This document is the Proprietary and Confidential Information Form for a state and local contract opportunity issued by the City of Newport News, Virginia. The contract is for Professional Architect/Engineering Services under a Term Contract (242-24-00001). The form allows bidders/offerors to identify any trade secrets or proprietary information in their response that they wish to protect from public disclosure under the Virginia Freedom of Information Act. Bidders must specifically identify the sections and page numbers containing the protected information and provide justification for why the protection is necessary. The document states that classifying an entire bid/proposal or pricing as proprietary is unacceptable, and refusal to remove such a classification will result in the rejection of the bid.
The related state and local contract opportunity is a Term Contract for Professional Architect/Engineering Services, solicitation number 242-24-00001, issued by the City of Newport News, Virginia. No other details about the scope, quantities, response dates, or contract term are provided in the documentation submitted.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attach B - Small Business Participation Data Form.xlsx | XLSX spreadsheet | |
| Attach C - eVA Registration Requirements.docx | DOCX document | |
| Addendum 1 - 242-24-0001.pdf | ||
| RFP AE Term Contract dgs-30-304_07-22_rfp_ae_term (2).pdf | ||
| Attach D - Question Form dgs-30-272.doc | DOC document | |
| Attach A - AE Data Sheets AE1-AE-6.xlsx | XLSX spreadsheet | |
| Attach E - Campus Map 2022.pdf | ||
| Attach G - Terms & Conditions, AE Contract.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment
PROPRIETARY AND CONFIDENTIAL INFORMATION FORM
This form must be returned with response to solicitation
Trade secrets or proprietary information submitted by a Bidder/Offeror shall not be subject to public disclosure under the Virginia Freedom of Information Act; however, the Bidder/Offeror must invoke the protections of § 2.2- 4342F of the Code of Virginia, in writing, either before or at the time the data or other material is submitted. The written notice must specifically identify the data or materials to be protected including the section of the bid/proposal in which it is contained and the page numbers and state the reasons why protection is necessary. The proprietary or trade secret material submitted in the original and all copies of the bid/proposal must be identified by some distinct method such as highlighting or underlining and must indicate only the specific words, figures, or paragraphs that constitute trade secret or proprietary information. In addition, a summary of proprietary information submitted shall be submitted on this form.
The classification of an entire bid/proposal document, line item prices, and/or total bid/proposal prices as proprietary or trade secrets is not acceptable. If, after being given reasonable time, the Bidder/Offeror refuses to withdraw such a classification designation, the bid/proposal will be rejected.
Name of Bidder/Offeror (Firm):
invokes the protections of § 2.2-4342F of the Code of Virginia for the following portions of my bid submitted on .
No portion of this bid is to be considered confidential and/or proprietary.
Signature:
(Signature In Ink) Name:
(Please Print) Title:
Data/Material to be Protected Section No., & Page No.
Reason Why Protection is Necessary
| Name of BidderOfferor Firm: |
| submitted on: |
| No portion of this bid is to be considered confidential andor proprietary: Off |
| DataMaterial to be ProtectedRow1: |
| Section No Page NoRow1: |
| Reason Why Protection is NecessaryRow1: |
| DataMaterial to be ProtectedRow2: |
| Section No Page NoRow2: |
| Reason Why Protection is NecessaryRow2: |
| DataMaterial to be ProtectedRow3: |
| Section No Page NoRow3: |
| Reason Why Protection is NecessaryRow3: |
| DataMaterial to be ProtectedRow4: |
| Section No Page NoRow4: |
| Reason Why Protection is NecessaryRow4: |
| DataMaterial to be ProtectedRow5: |
| Section No Page NoRow5: |
| Reason Why Protection is NecessaryRow5: |
| DataMaterial to be ProtectedRow6: |
| Section No Page NoRow6: |
| Reason Why Protection is NecessaryRow6: |
| DataMaterial to be ProtectedRow7: |
| Section No Page NoRow7: |
| Reason Why Protection is NecessaryRow7: |
| DataMaterial to be ProtectedRow8: |
| Section No Page NoRow8: |
| Reason Why Protection is NecessaryRow8: |
| DataMaterial to be ProtectedRow9: |
| Section No Page NoRow9: |
| Reason Why Protection is NecessaryRow9: |
| DataMaterial to be ProtectedRow10: |
| Section No Page NoRow10: |
| Reason Why Protection is NecessaryRow10: |
| Name: |
| Title: |
File details come from the government source that posted it. Updated .