AMENDMENT_002.pdf
PDF 2 MB Posted
- Solicitation number
- SB1341-16-RP-0025
About this file
Amendment 002
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Amendment_001.pdf | ||
| ISSUED_RFP.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
NSN 7540-01-152-8070 STANDARD FORM 30. (Rev. 10-83) Previous Edition unusable Prescribed by GSA FAR (48 CFR) 53.243
Page of Pages AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code
2. AMENDMENT MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (if applicable)
6. ISSUED BY CODE 7. ADMINISTERED BY (If other than item 6) CODE
(x) 9A. AMENDMENT OF SOLICITATION NO.
9B. DATED (SEE ITEM 11)
10A. MODIFICATION OF CONTRACT/ORDER NO.
8. NAME AND ADDRESS OF CONTRACTOR (NO., Street, Country, State and ZIP Code)
CODE FACILITY CODE
10B. DATED (SEE ITEM 13)
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of offers is extended, is not extended.
Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:
(a) By completing items 8 and 15, and returning ______ copies of amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OR OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment your desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
Check One
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return _______ copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible)
Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
15B. CONTRACTOR/OFFEROR 16B. UNITED STATES OF AMERICA
(Signature of person authorized to sign)
15C. DATE SIGNED
(Signature of Contracting Officer)
16C. DATE SIGNED
Continuation Page
PAGE 2 OF 7 SB1341-16-RP-0025/002
Continued from Block 14...
The due date for proposals remains unchanged by reason of this amendment.
Attachment Page
PAGE 3 OF 7 SB1341-16-RP-0025/002
1. Section 1 Statement of Work, Section III General Requirements, is hereby amended to incorporate Federal Information Technology (IT) requirements that are applicable to this contract:
-Federal Information Technology (IT) Requirements. In addition to Sections V. and VI.
herein, the following IT requirements shall apply to this contract:
Internet Protocol Version 6 (IPv6). The Contractor services shall be accessible through both Internet Protocol Version 6 (IPv6) and IPv4.
Hypertext Transfer Protocol Secure (HTTPS) and HTTPS Strict Transport Security (HSTS).
The Contractor shall ensure that the publicly accessible Federal website(s) and web service(s) provide services only through a secure connection through use of HTTPS, and must have HSTS enabled.
Trusted Internet Connections (TIC). The Contractor shall provide the ability to restrict government access to the cloud service from government specified networks, in accordance with the Office of Management and Budget (OMB) Memorandum M-08-05, “Implementation of
Trusted Internet Connections (TIC),” and the Department of Homeland Security’s “Trusted
Internet Connections (TIC) Reference Architecture Document Version 2.0.”
Section 508. The Contractor shall create and maintain a system that complies with Section
508 of the Rehabilitation Act.
Authentication. The Contractor shall configure its system or application to be compliant with:
Homeland Security Presidential Directive 12 (HSPD-12): Policy for a Common
Identification Standard for Federal Employees and Contractors.
National Strategy for Trusted Identities in Cyberspace (NSTIC)
The preferred user authentication methods are through integration with Connect.gov and application issued credentials. Connect.gov can provide both PIV card and approved third party credentials. Users shall be given the option of using an acceptable PIV, third party credential or establishing a credential with the Contractor provided solution.
Applications that cannot integrate with Connect.gov will implement user authentication via Government issued PIV cards, approved third party credentials and Contractor solution-provided credentials. Third party authentication must be consistent with NSTIC;
with providers and protocols approved by the Federal Identity, Credential, and Access
Management (FICAM) Trust Framework Solutions (TFS) Program. In all cases a Contractor solution-provided credential must also be supported to allow access by external collaborators that do not have or do not wish to use a trusted third party credential.
All credentials shall be consistent with NIST Special Publication 800-63, Electronic
Authentication Guideline, and the system’s accessed Level of Assurance (LOA). The required minimal LOA is Level 2.
Incident Response. The Contractor shall be able to provide to NIST the qualifications and contact information of their security and incident response team. The Contractor shall notify NIST within three (3) hours of any possible malicious activity, providing a unique incident reference number and contact information for further details. The Contractor shall provide any application and operating system logs associated with an incident as well as a file system timeline for potentially compromised hosts and any additional files referenced during forensic analysis upon request. If possible the Contractor shall provide memory dumps and forensic images of any NIST systems that were possibly compromised.
PAGE 4 OF 7 SB1341-16-RP-0025/002
2. The following questions and responses are hereby provided.
QUESTION 1: Page 1 (the 1449), Section 10: Since this is a set-aside for small businesses, must the winning small businesses do at least 50% of the total revenue of the contract or of 50% of the fully burdened labor revenue?
RESPONSE 1: Please reference the Federal Acquisition Regulation (FAR) clause 52.219-14
(Nov 2011), incorporated by reference under FAR clause 52.212-5. The full text of this clause can be accessed at www.acquistion.gov and will provide the response to the question.
QUESTION 2: Page 15 and 16 para 2(a) 2nd sentence: It says the small business size standard is 500 employees yet in block 10 on the 1449 it says the size standard is $15M. Please confirm.
RESPONSE 2: Pages 15 and 16, paragraph 2(a) references the two points: (1) The NAICS code and size standard for this acquisition appear in block 10 of the Standard
Form 1449; AND (2) the small business size standard for a concern who proposes an item it did not itself manufacture is 500 employees.
Reference the size standard in Block 10 of the Standard Form 1449.
QUESTION 3: Page 19 (a) General Instructions: The RPF states that “Offerors shall submit one original of their proposal, marked as such, and four copies of the technical and price proposals. Only one copy of the business portion of the proposal is required to be submitted.” As well as “Only one copy of the complete proposal is required to be submitted via email.” Is it acceptable to submit one complete proposal by mail to Carol Wood at carol.wood@nist.gov?
RESPONSE 3: Assuming the question is asking if it is acceptable to submit one complete copy of the proposal via email, not mail as the question reads, the answer confirms the instructions in the solicitation, yes.
QUESTION 4: Page 19 (a) General Instructions: Is there any size limitation on the electronic file size or size of emails that can be submitted to Carol Wood at carol.wood@nist.gov?
RESPONSE 4: There is not a size limitation on the electronic file size or size of emails that can be submitted via email.
QUESTION 5: Page 19(b)(1)(a)(iv): Do you follow SBA’s Interpretation on limitation on subcontracting where the limitation on subcontracting applies only to that portion of the requirement identified by the NAICS code (in this case
Professional Scientific and Technical Services)?
RESPONSE 5: Only one NAICS code applies to this solicitation. All work under this contract applies to that NAICS code. Additionally, reference the response to
Question 1.
QUESTION 6: Page 20, (4): Past performance project descriptions to ½ page. However, page
21 under the evaluation discussion of past performance requires substantial information that is difficult to provide in ½ page. Can past performance project descriptions be limited to 1 page vice ½ page?
RESPONSE 6: The page limitation for documentation required for past performance references has historically been ½ page per project and has been adhered to by offerors successfully.
QUESTION 7: Page 20 (2) TECHNICAL PROPOSAL – BASE CONTRACT (B) Specific areas to be addressed, Writing samples: Is the government expecting the offerors to submit writing samples or to discuss examples of their writing experience? If examples are expected do they count toward the overall page count of the technical proposal?
PAGE 5 OF 7 SB1341-16-RP-0025/002
RESPONSE 7: Please revisit the discussion on Page 20, under “For the Purpose of
Evaluation of Capability”, the paragraph beginning “Writing samples…”. The required documentation is clearly described.
Writing samples are not included in the 25-page limitation for the technical proposal.
QUESTION 8: Page 21 Resumes: Do the resumes for the proposed Project Manager and Forensic
Science subject matter experts count towards the page limit of the Technical proposal?
RESPONSE 8: This question is answered in the request for proposal, Section 3, Addendum to
52.212-1. Please reference that section.
QUESTION 9: Page 21 (3) Price Proposal Base Contract: Is there a page limit for the
Price proposal Base Contract? If yes, what are the number of pages?
RESPONSE 9: No.
QUESTION 10: Pages 19 and 22: Technical and Price Quotations for the Mock Task Orders:
Should these be submitted as individual documents or combined together in
Volume 4: Mock Task Orders? Are there page number restrictions on the price quotations for the two task orders? If so, what are the page limits?
RESPONSE 10: Offerors must submit a technical quotation for each mock task order and a separate price quotation for each mock task order.
There are not page number restrictions on the price quotations for the two mock task orders.
QUESTION 11: Page 23 (4) Evaluation: In the fourth paragraph the RFP states that
“Capability, Experience and Past Performance shall be equal in importance to each other. Capability, Experience, and Past Performance, when combined, shall be equal in importance to price.” The next paragraph states “In determining best value, stronger consideration shall be given to the
Capability and Experience evaluation factors as stated herein.” The last paragraph states: “The proposed labor rates and prices will be evaluated but not scored. The price evaluation will determine whether the proposed prices are complete and fair and reasonable in relation to the labor categories proposed and the solicitation requirements.” Can you please clarify the proposal evaluation and scoring criteria?
RESPONSE 11: The request for clarification is not sufficiently clear to provide a response.
QUESTION 12: Page 24 (5) Evaluation of Compensation for professional Employees
Compensation Plan: The RFP states that “As part of their proposals, offeror will submit a total compensation plan setting forth salaries and fringe benefits proposed for the professional employees who will work under the contract.” Should the Compensation Plan be included in the Base Price
Proposal?
RESPONSE 12: Yes.
QUESTION 13: Do attachments such as writing samples, project examples/descriptions, past performance, resumes, reps & certs, client references, etc. count towards the
25‐page technical proposal page limitation? Or, can they be included an appendix?
RESPONSE 13: This question is answered in the request for proposal, Section 3, Addendum to 52.212-1 and the response to question 7.
Representations and certifications accessible from
PAGE 6 OF 7 SB1341-16-RP-0025/002
www.SAM.gov do not need to be submitted with proposals.
QUESTION 14: Resumes are limited to 4 pages. Is this per resume or a collective page limit for all resumes?
RESPONSE 14: Per resume.
QUESTION 15: …If we engage with a subcontractor…that is FedRAMP certified, will that be sufficient for the purposes of the proposed project? Must the prime be
FedRAMP certified, or only the subcontractor offering…?
RESPONSE 15: Reference Section I, Statement of Work, paragraph VI, Meet Moderate Level
FedRAMP Requirements After Award, Background Information – FedRAMP:
“The requirement for FedRAMP approval and/or the Authorization to Operate applies when the Contractor, and possibly their subcontractors, will have access to NIST data and/or personally identifiable information. This process of assessing the
Contractor’s (and subcontractor’s) processes and procedures with respect to the handling and securing of PII is not limited to electronic data, but also applies to data that is or will be maintained in hard copy as well.”
QUESTION 16: Please confirm that the low and moderate level FedRAMP certification requirements apply to the service provider of the cloud service, and not the contractor itself since the contractor is a third party and will not host the cloud. Sections V and VI, pages 9-10.
RESPONSE 16: Not confirmed. Please revisit the statement of work and the response to question 15.
QUESTION 17: Are the writing samples requested in Addendum to 52.212-1, Section
(b)(2)(B), first bullet under "For the purpose of evaluation of Capability" included in the 25 page limit for the Technical Proposal? Addendum to 52.212-
1, Section (b)(2)(B), page 20
RESPONSE 17: Reference response to question 7.
QUESTION 18: Will the Government provide a standard fee/rate for the Hyatt Regency New
Orleans and PSAV pricing for all offerors to include for their proposals?
Evaluation for Mock Task Orders, page 22
RESPONSE 18: No.
SCHEDULE Continued
ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
PAGE 7 OF 7 SB1341-16-RP-0025/002
BASE PERIOD
0001 The Contractor shall perform services for the
Organization of Scientific Area Committees (OSAC) in accordance with the statement of work, the terms herein, and task orders issued.
The OSAC is a collaborative body of more than 600 forensic science practitioners and other experts who represent all levels of the government, academia and industry.
Negotiated labor rates and labor categories shall be incorporated at the time of award.
1.00 YR
OPTION PERIOD I
0002 The Contractor shall perform services for the Organization of Scientific Area Committees (OSAC) in accordance with the statement of work, the terms herein, and task orders issued.
The OSAC is a collaborative body of more than 600 forensic science practitioners and other experts who represent all levels of the government, academia and industry.
OPTION PERIOD II
0003 The Contractor shall perform services for the Organization of Scientific Area Committees (OSAC) in accordance with the statement of work, the terms herein, and task orders issued.
The OSAC is a collaborative body of more than 600 forensic science practitioners and other experts who represent all levels of the government, academia and industry.
OPTION PERIOD III
0004 The Contractor shall perform services for the Organization of Scientific Area Committees (OSAC) in accordance with the statement of work, the terms herein, and task orders issued.
The OSAC is a collaborative body of more than 600 forensic science practitioners and other experts who represent all levels of the government, academia and industry.
Descript: The above referenced solicitation is hereby amended to incorporate information technology (IT) requirements into the statement of work, and respond to questions submitted.
Reference the attached pages for amendment details. ...See Continuation Page
| Descript1: |
| AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT: |
| IDCode: |
| pdfpage1: 1 |
| Pages: 7 |
| DocNo: 002 |
| EffDate: JUL 26, 2016 |
| ReqNo: NB602000-16-01516 |
| ProjNo: |
| IssuedByCode: 000SB |
| IssuedBy: NATIONAL INST OF STDS AND TECHNOLOGY |
100 BUREAU DRIVE STOP 1640
BUILDING 301 ROOM B129
GAITHERSBURG MD 20899-1640
| AdminByCode: |
| AdminBy: See Block 6 |
| ContractorCode: |
| FacCode: |
| SolChg: Yes |
| AwdChg: Off |
| SolNo: SB1341-16-RP-0025 |
| SolDate: JUL 08, 2016 |
| AwdNo: |
| AwdDate: |
| NoCopies: 1 |
| Amended: Yes |
| OffrExt: Off |
| OffrNoEx: No |
| ApprData: See Schedule |
| ChgeOrd: Off |
| ChgeOrder: |
| Modify: Off |
| B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).: |
| SuppAgre: Off |
| SuppAuth: |
| ModOthr: Off |
| OthrSpec: |
| NoReq: Off |
| Require: Off |
| Copies: |
| SignName: |
| SignTitl: |
| ContDate: |
| ContrOfficerInfo: |
| CODate: |
| Contractor Info: |
| ContractorPOC: |
| Contractor: |
| ModAmount: |
| Header: |
| 15B. CONTRACTOR/OFFEROR: |
| Footer1: |
| signature: |
File details come from the government source that posted it. Updated .