Attachment_0018_Amendment_0016_Questions_and_Answers.xlsx
XLSX spreadsheet 15 KB Posted
- Solicitation number
- W52P1J-16-R-0172
About this file
Amendment 0016 Questions and Answers
View the file
Other files
Show 40 more
Latest 50 of 57 listed here. See the rest on GovTribe.
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
Sheet1
| ADDITIONAL QUESTIONS/COMMENTS AND ANSWERS - REQUEST FOR PROPOSAL (RFP) UC SOFT CLIENT (W52P1J-16-R-0172) | ||||||||
| RFP Section | VOLUME | ATTACHMENT | PAGE | PARAGRAPH | QUESTION/COMMENT | RESPONSE | ||
| 4 | Att 0002 Sec 2.2.1 | All | Attachment_0002_Instructions_Conditions_and_Notices_to_Offerors | 6-7 | Volume I - Security and Experience through Volume VI - Factor 4 Price | |||
| Item b Page Limitation (for each volume) | The USG has indicated that some sections of the Offeror’s proposal submission are subject to page limit requirements, while other sections have no page limit. For example, Volume III - Factor 1 Technical Approach Sub-factor II: Service Capability has a page limit of 30 pages; however, the PWS, SLA, and Milestone Schedule to be submitted as part of Volume III have no page limit. | As provided in Attachment 0002 Section 2.1 these items are not subject to the page limitations of a particular volume. They shall be submitted with the Volume identified, but will not be counted as part of the overall page count. | ||||||
| 5 | Q1a: To avoid the potential confusion that might result from a single document with alternating sections that are/are not subject to page limit requirements, may the Offeror attach the PWS, SLA, and Milestone Schedule as appendices (with separate page numbering) to Volume III? | As provided in 2.1.1 these are attachments to subfactor II of Volume III. They are not oulined within the 30 page limit, so it should not be intertwined. | ||||||
| 6 | Q1b: If documents that are excluded from page limits may be submitted as appendices, may each file comprising an appendix be submitted as a standalone file on the volume CD? | As provided in 2.1.1 a single file should be submitted for each subfactor. | ||||||
| 7 | Att 0002 Sec 2.2.1 | All | Attachment_0002_Instructions_Conditions_and_Notices_to_Offerors | 6-7 | Volume I - Security and Experience through Volume VI - Factor 4 Price | |||
| Item c File Naming Structure (for each volume) | Q2a: The file naming structure stipulated for Volumes I-III ends with a suffix: ".XXX". Could the USG please clarify whether the .XXX at the end of the file naming structure should be used to indicate file type extension? For example: "CompanyName-Technical-Subfactor2.docx" for a file in Microsoft Word. | It would be the document format noted elsewhere in Attachment 0002, on how proposals shall be submitted. | ||||||
| 8 | Q2b: Also, there is no ".XXX" stipulated for the file names for Volumes IV-VI. Could the USG confirm that the omission of the ".XXX" suffix is an oversight? | This was an oversight | ||||||
| 9 | Att 000 Sec 3.2 | Attachment_0002_Instructions_Conditions_and_Notices_to_Offerors | 14 | Sub-factor 2: Service Capability | ||||
| Item d | Q3: Could the USG also please specify the file format required for the Milestone Schedule to be submitted as part of Volume III? Specifically, would the USG accept this file in Microsoft Project (.mpp) format? For its own convenience, would the USG also like the Offeror to provide this file in additional formats as well? For example, Microsoft Excel (.xlsx) and/or Adobe Portable Document Format (.pdf)? | Please see section 2.1 of Attachment 0002. The preferred format is microsoft project that is compatiable with Microsoft version noted in the proposal. | ||||||
| 10 | Att 0002 | All | Attachment_0002_Instructions_Conditions_and_Notices_to_Offerors | 6-7 | Volume I - Security and Experience through Volume VI - Factor 4 Price | |||
| Item c File Naming Structure (for each volume) | Q4: In light of the above, could the USG please indicate whether the sample file organization shown below accurately conforms with the USG’s requirements? If not, could the USG please provide further clarification as soon as possible? |
CD 3: Volume III - Factor 1 Technical Approach
– CompanyName-Technical.docx (Title Page, Table of Contents, and Acronym List) (Word format)
– CompanyName-Technical-Subfactor1.docx (System Architecture response) (35 pages, Word format)
– CompanyName-Technical-Subfactor2.docx (Service Capability response) (30 pages, Word format)
– CompanyName-Technical-PWS.docx (Performance Work Statement) (no limit, Word format)
– CompanyName-Technical-SLA.docx (Service Level Agreement) (no limit, Word format)
– CompanyName-Technical-IMS.mpp (Integrated Master Schedule) (no limit, Microsoft Project format)
– CompanyName-Technical-IMS.xlsx (Integrated Master Schedule) (no limit, Microsoft Excel format)
| – CompanyName-Technical-IMS.pdf (Integrated Master Schedule) (no limit, Adobe PDF format) | Please see response above on how a single file should be submitted for each subfactor, but attachments are allowed within that file. | |||||||
| 11 | Att 0002 | All | Attachment_0002_Instructions_Conditions_and_Notices_to_Offerors | 3 | 2.1 Structure | |||
| Item a | Q5: The USG has stipulated the use of Arial font exclusively. However, some solicitation documents required for submission with the proposal (e.g., Attachment_0004_Small_Business_Participation_Plan, Attachment_0005_Pricing_Model) were provided in other fonts. Should the Offeror convert these documents to Arial? Or leave in the original font? | Please do not alter documents that have been supplied by Government (Price Model, Small Business, Past Performance). Offeror shall use fonts and formats provided in those documents. | ||||||
| 12 | Att 0006 | All | Attachment_0006_Form_PPI_002_M_Past_Performance_for_UC_Soft_Client | 1 | All | Q6: Attachment_0006_Form_PPI_002_M_Past_Performance_for_UC_Soft_Client is formatted in Arial 12 point font. However, since this form consists of a table and Arial 8 point in tables is allowed, the Offeror would like to reduce the font size in some table fields to allow items to fit on a single line for the purpose of saving space and enhancing legibility. Will the USG accept Attachment_0006 with the font size reduced as described? | Offeror shall use fonts and formats provided in this document, and not alter it. | |
| 13 | ||||||||
| 14 | ||||||||
| 15 | ||||||||
| 16 | ||||||||
| 17 | ||||||||
| 18 | ||||||||
| 19 | ||||||||
| 20 | ||||||||
| 21 | ||||||||
| 22 | ||||||||
| 23 | ||||||||
| 24 | ||||||||
| 25 | ||||||||
| 26 | ||||||||
| 27 | ||||||||
| 28 | ||||||||
| 29 | ||||||||
| 30 |
File details come from the government source that posted it. Updated .