Q&A_Response_Package_-_Batch_1.pdf
PDF 126 KB Posted
- Solicitation number
- N00024-17-R-5216
About this file
Final RFP Q&A - Batch 1
View the file
Other files
Show all 26
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
DATE
FBO BATCH/
QUESTION NO. RFP REFERENCE/DISCUSSION (if necessary) QUESTION ANSWER
7/3/2017 1‐001 RFP Section M states that Past Performance will be evaluated as "Acceptable" or "Unacceptable."
Department of Defense Source Selection
Procedures (Defense Federal Acquisition
Regulation Supplement
Procedures, Guidance and Information
Subpart 215.3‐‐Source Selection, March 31, 2016) require that this methodology be used only for Lowest Price Technically Acceptable
(LPTA) procurements. See Source Selection
Procedures Appendix C, Lowest Price Technically
Acceptable Source Selection Process . For all other competitive procurements, Past
Performance is required to be evaluated for
Relevancy on a "Very Relevant / Relevant /
Somewhat Relevant / Not Relevant" scale, and for Performance Confidence on a "Substantial /
Satisfactory / Neutral / Limited / No Confidence" scale. See Source Selection Procedures section
3.1.3, Past Performance Evaluation .
Please revise RFP Section M to comply with DoD Source Selection
Procedures for Past Performance evaluation, and make any corresponding changes to Section L if needed.
The RFP requirements will not be changed. Department of Defense Source
Selection Procedures dated 31 March
2016 subpart 2.3.4.2.2 states "With appropriate parameters to assess past performance recency and relevancy, ratings of “acceptable” or
“unacceptable” may be used (see
Appendix C, Table C‐2) if past performance is not a discriminating factor in the source selection."
7/3/2017 1‐002 RFP Section L.3.1 (Solicitation Response
Requirements) states: "Text within tables, diagrams, pictorial charts, or graphic material may use 8‐point Times New Roman font ."
Engineering drawings are typically developed using sans‐serif fonts, rather than serif fonts such as Times New Roman. Sans‐serif fonts also provide greater clarity at smaller font sizes, because serifs become difficult to distinguish at
8‐point, and sans‐serif fonts such as Arial and
Helvetica are wider than Times New Roman.
Would the Government consider allowing sans‐serif fonts for text within tables, diagrams, pictorial charts, and graphic material?
As currently written, the current requirements allow Offerors to use fonts other than Times New Roman for text within tables, diagrams, pictorial charts, or graphic material. L.3.1 states "Text within tables, diagrams, pictorial charts, or graphic material MAY use 8‐point
Times New Roman font." The RFP will be updated to clarify Times New Roman font or equivalent.
7/3/2017 1‐003 Technical Manual Contract Requirement (TMCR)
No. SNIPP‐160030‐000, 18 Dec 2015 was not provided with the Competition Library . This document is necessary to Offerors in order to estimate the cost of technical manual development.
Please provide this TMCR. Technical Manual Contract Requirement
(TMCR) No. SNIPP‐160030‐000, 18 Dec
2015 was provided to all offerors that returned a DD 254 via separate AMRDEC notice. To receive a copy offerors must timely submit a DD254 which is then vetted to determine eligibility to receive the TMCR.
7/3/2017 1‐004 Clause HQ L‐2‐0017 SOFTWARE DEVELOPMENT
AND CMMI OR EQUIVALENT EXPERIENCE
(NAVSEA) (DEC 2006) states: "Offerors shall submit a description of previous relevant experience, within the past (See Section L.4.3) months ." Section L.4.3 does not specify the number of months.
Please revise Section L to specify the applicable time period.
Section L.4.3 first paragraph states "past three (3) years". The Government considers 3 years to be 36 months.
7/3/2017 1‐005 CLIN 1002 covers Travel/ODC for 0001; 0003 covers Travel/ODC for 0002; and 2001 covers
Travel/ODC for 2002
What CLIN covers Travel/ODC for
1001?
CLIN 1002 extended description states:
"Travel and ODC in support of CLIN
1001"
7/3/2017 1‐006 Clause HQ L‐2‐0017 SOFTWARE DEVELOPMENT
AND CMMI OR EQUIVALENT EXPERIENCE
(NAVSEA) (DEC 2006) states: "Offerors shall also describe any previous relevant CMMI® or equivalent model‐based process maturity appraisals performed within the past 24 months. " CMMI appraisals are valid for three years. See http://partners.cmmiinstitute.com/wp‐ content/uploads/2015/01/Period‐of‐Validity‐for‐
SCAMPI‐A‐Appraisal‐Results.pdf .
Please revise Section L to allow for documentation of relevant CMMI® or equivalent model‐based process maturity appraisals that are current and valid as of the proposal due date.
The RFP requirement remains unchanged.
7/3/2017 1‐007 C.4.1.6.9 Software Delivery states: “All licensing requirements/restrictions for each Commercial
Off‐The‐Shelf (COTS) product shall be provided as part of the SVD. This documentation requirement shall include delivery of full paid software licenses which provide sufficient rights for the Government to meet and fulfill the needed and necessary Navy ECDIS SW capabilities over its lifecycle .”
Delivery of "full paid software licenses " may not be achievable for an offer that includes commercial software and associated license pricing on optional CLIN 1003 unless the Government exercises that CLIN.
Please confirm that this is the
Government's intent.
"Full paid software licenses" is for the approved "Full Rate Production"
Software Build which will serve as the
"master" software copy. Commercial software Licenses cost for all ship and shore installations will be included in
CLIN 1003.
Navy ECDIS Software Solicitation N00024‐17‐R‐5216 Questions
File details come from the government source that posted it. Updated .