Questions and Responses 2-24-2026.docx
DOCX document 26 KB Posted
- Attached to
- CNSP Financial Analyst Support - SEAPORT Federal contract opportunity
- Solicitation number
- N0024426RS005
About this file
This is a Questions and Responses document from a federal solicitation for CNSP Financial Analyst Support services. The document addresses 30 clarification questions submitted by potential offerors and provides corresponding government responses, many of which reference updates made via Amendment 001.
Key clarifications include: personnel must be based in San Diego and available for onsite support at CNSP Coronado as needed, though some remote work may be authorized; the Performance Work Statement (PWS) in Section C has been updated and should serve as the basis for technical responses addressing financial management support, PBE analysis, and financial analyst services; only key personnel resumes are required (non-key resume requirement was removed); Volume III Past Performance is limited to 2 pages per OPPD/CPARS reference; alternative labor mixes may be considered beyond the government's 1912-hour annual estimate; compensation plans are required per FAR clause 52.222-46 with page limits updated via amendment; travel funding is available for personnel based outside San Diego requiring periodic onsite support, estimated at up to 15% of total effort for applicable personnel; contractors may recommend automation and AI solutions compatible with DoD-approved platforms such as Advana and UiPath; past performance evaluation accepts a maximum of 3 contracts; Letters of Intent for key personnel must include salary information but non-key LOIs need only include salary if required; and the contract start date is expected to be March 13, 2026, upon award. The document also clarifies staffing requirements, page limits for various proposal volumes, internal hyperlink acceptability, and DCAA point-of-contact formatting requirements.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Solicitation Amendment N0024426RS0050003 SF 30.pdf | ||
| Solicitation Amendment - N0024426RS0050003.pdf | ||
| Solicitation Amendment - N0024426RS0050002.pdf | ||
| Solicitation Amendment N0024426RS0050002 SF 30.pdf | ||
| Price Format Template.xlsx | XLSX spreadsheet | |
| (Amend 02) Questions and Responses 2-26-2026.docx | DOCX document | |
| DD254 CNSP Budgeting Solicitation.pdf | ||
| Price Format Template.xlsx | XLSX spreadsheet | |
| Solicitation Amendment N0024426RS0050001 SF 30.pdf | ||
| Solicitation Amendment - N0024426RS0050001.pdf | ||
| OPPD.docx | DOCX document | |
| Solicitation - N0024426RS005.pdf |
Show all 12
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
1. Place of performance is listed as CNSP Coronado. Please confirm that all staff must be located in San Diego and able to perform onsite services at CNSP Coronado.
The primary place of performance is Commander, Naval Surface Force Pacific (CNSP) in Coronado, CA. Personnel are expected to support onsite requirements at CNSP Coronado as needed. While some tasks may be performed remotely (if authorized), staff must be able to perform onsite services in San Diego when required to meet mission needs.
2. The solicitation includes a SOW. The prior pre-solicitation included a separate PWS. Please confirm if the separate PWS is intended to be included in the solicitation and will be used to define the work to be performed.
PWS in Section C has been updated via Amendment 001.
3. Should Volume I only contain the requested information and the signed SF33 or should signed amendments/modifications be included as well?
Yes, include any signed amendments government issues as part of Volume 1
4. The instructions state, "Offerors must demonstrate a sufficient understanding of and approach to the various requirements identified in the Performance Work Statement (PWS)." The solicitation instructions list several items like PPBE analysis, financial analysis, and Financial Analyst, that aren't directly referenced in the PWS. Please clarify what our Technical response should address.
Offerors should base their technical response on the requirements identified in the Performance Work Statement (PWS). In doing so, responses should clearly demonstrate understanding and approach to all functional areas described, including financial management support, PBE (Planning, Budgeting, and Execution) analysis, financial analysis, and related advisory services.
Although certain roles or functions (e.g., Financial Analyst support) may not be listed verbatim in the PWS headings, they are inherent within the financial management and analytical support requirements. The Technical proposal should address how your team will execute these requirements, staffing approach, methodologies, internal controls, and quality assurance processes.
5. The instructions state, "The Offeror shall also provide a chart that links the experience of the proposed personnel to the specific PWS paragraph." Please confirm that our chart should link to and reference the tasks in the PWS provided as part of the pre-solicitation.
PWS in Section C has been updated via Amendment 001.
6. The instructions state, "This section shall include a list of two key personnel and non-key personnel clearly identified (prime and subcontractor) whom the offeror proposes to assign to the contract." This statement is not consistent with the key personnel specified in the SOW. Please clarify what is being requested and how many key personnel are to be presented.
Update provided via Amendment 001
7. There are additional inconsistencies about what resumes should be presented throughout this section. The instructions state, "As stated above, resumes are required for Key and Non-Key Personnel and the staffing list shall include qualifications for ALL proposed personnel including non-key personnel." Please confirm that only key personnel resumes are required to be submitted.
Amendment 001 provides update to remove non key personnel resume requirement
8. Volume III Past Performance is limited to 2 pages. Please clarify how OPPD or CPARS for 3 projects are to be provided within the 2 page limitation.
Page limit has been update to 2 Pages per OPPD/CAPRS reference via Amendment 001
9. The Labor Hours table includes 1912 hours for each position. Please confirm this amount is annual across all performance periods. Further, please clarify is bidders are permitted to deviate from the Government's annual estimate of hour for each FTE or are we specifically required to bid the 1912 hours for each FTE.
Alternative labor mixes may be considered (language added via Amendment 001)
10. The instructions state, "In addition, see FAR clause 52.222-46, included in Section M, for compensation plan requirements." Please clarify if bidders are required to include a compensation plan within Volume IV and, if so, please clarify the specific information we are required to include in our compensation plan. Lastly, please consider expanding the 5 page limitation for the explanatory word document in Volume IV to accommodate an adequate compensation plan along with other price supporting documentation.
Yes. Refer to clause for specific information. Page limit will be updated via Amendment 001.
11. The solicitation states, "For each person proposed who is not currently on the contractor or subcontractor's payroll, the Offeror shall provide a signed "Letter of Intent" which includes the offered salary." The solicitation also makes mention of a compensation plan being required (page 30) but does not explicitly request salaries or salary ranges for ALL team members, not just contingent personnel. It is unclear how the Government would evaluate a compensation plan that does not require salaries or salary ranges for all positions. Further, only requiring salary information from contingent employees allows for the incumbent contractor, since they already employ all current staff, to have a strategic advantage by not disclosing compensation information consistent with other bidders.
Incumbent does not have access to this information
12. There are inconsistencies around travel requirements. On page 9 of the solicitation mentions 4 trips a year with duration of 5 days, page 12 references having two FTEs traveling; PWS Part 6 references 15% of total effort may be required for half of FTEs. Please clarify the travel expectations.
Travel expectations are as follows:
• Travel may be required up to approximately 15% of total effort for applicable personnel.
• Travel estimates (e.g., four trips per year, approximately five days per trip) are planning estimates and may apply to specific FTEs depending on mission needs.
• Not all FTEs will necessarily travel; however, certain positions may require periodic travel in support of site visits, assessments, training, or mission requirements.
Offerors should propose travel consistent with these estimates and demonstrate flexibility to support evolving mission needs.
13. The travel chart shows travel to San Diego however the place of performance is in San Diego, please clarify. Is the travel funding intended to have certain team members periodically travel to San Diego from some other location? If so, please clarify which project positions this applies to.
Travel funding is intended for:
• Personnel based outside San Diego who provide periodic onsite support at CNSP.
• Attendance at required training, classes, or professional development necessary to execute contract requirements.
14. The PWS discusses Automation and AI solutions, but what is the availability with the current environment and infrastructure to recommend AI solutions (either proprietary or built within the CNSP network) to enhance the current business processes?
CNSP operates within existing DoD enterprise systems and infrastructure. Contractors may recommend automation and AI-enabled solutions that are compatible with DoD-approved platforms and security requirements.
Current DoD enterprise tools that support automation and AI initiatives include platforms such as Advana and UiPath, among others authorized within the DoD environment. Proposed solutions must align with DoD cybersecurity policies, data governance requirements, and approved enterprise architectures.
Offerors should describe how they would leverage existing approved tools to enhance business processes, data analytics, reporting efficiency, and decision support capabilities.
15. Will the Government please confirm that non-key resumes are exempt from the Volume II page limits?
We’re removing the requirement for non-key resumes
16. Does this mean that non-key personnel resumes will not be evaluated?
We’re removing the requirement for non-key resumes
17. How will evaluation of non-key personnel resumes be different from the evaluation for Key Personnel resumes?
We’re removing the requirement for non-key resumes
18. Could the Government please confirm that it is acceptable to include this salary information in Volume II in the Letters of Intent, even though price or cost information is prohibited in Volume II?
This is Acceptable. Language updated via Amendment 001
19. Does the Government instruction mean that the section shall include a list of three key personnel clearly identified? Will the Government please conform the RFP sections L and M to reflect the quantity of Key Personnel?
Update provided via Amendment 001
20. Will the Government clarify whether the Past Performance volume requires a maximum of 3 contracts or exactly 3 contracts?
Maximum of 3
21. Will the Government confirm that the CPARS document(s) are exempt from the Volume III page limits?
Confirming
22. Will the Government please confirm that past performance reference contracts will be evaluated for relevance in accordance with the scope specified in Section C, paragraph 1.4 Scope?
Confirming
23. What is the correct title for Volume I?
Offer
24. Will the Government clarify that the explanatory document for Volume IV may be submitted in PDF format?
PDF is for cost narrative, actual pricing should be submitted as Excel Spreadsheet
25. Will the Government confirm that it is external hyperlinks to the internet that are prohibited, and that the navigation links within the document created by Word (such as the Table of Contents ability to jump to specific document headings) are acceptable?
Internal hyperlinks are acceptable
26. in section L, page 27, under the Sub-factor (2) Staffing/Key Personnel, the requirement for a 2-page resume for Senior Financial Analyst (key), Financial Analyst III (key), Financial Analyst III (non-key), and Financial Analyst II (non-key). Can the government clarify if the requirement is for a 2-page resume for all 7 FTEs, key and non-key? Will the government consider increasing the page count for this volume if requiring a 2-page resume for ALL FTEs?
Only key
27. in section C, page 8, the Senior Financial Analyst III is listed as a level III, however, on page 27 SubFactor (2) Staffing/Key Personnel, it is listed as Senior Financial Analyst. Can the government provide clarification for this LCAT level?
Updated to level III via Amendment 001
28. for each person proposed who is not currently on the contractor or subcontractor's payroll, the Offeror shall provide a signed 'Letter of Intent' which includes the offered salary. Can the government please remove the requirement for the salary to be included in the Letter of Intent?
Amendment 001 changes language to only include salary if LOI is for key personnel.
29. in Section C, page 5, the period of performance shows as 09-Mar-2026, however, in Section F, page 14, the delivery period shows a start date of 06 Mar 2026. Can the government please provide the correct contract start date?
Will start on date of award, which is now expected to be 3/13
30. Reference Section L, Volume IV - Price, page 29. The solicitation specifies, "Prime and subcontractors shall identify relevant DCAA point-of-contact, phone number, and email address in the form of dcaafao####@dcaa.mil vice john.smith@dcaa.mil."
Will the Government please confirm that in the event that the offeror's DCAA point of contact is unable to provide an email address in the specified format, a @dcaa.mil email that contains the person's name will be acceptable?
That would be acceptable
File details come from the government source that posted it. Updated .