QA v2.docx

PMO Recompete M67854-26-R-3007 Q&A Q1. RFP Section L, Paragraph L.1: Section L specifies that NAICS Code 541330 with a size standard of $25,500,000 applies to this RFP. However, per the SeaPort NxG MAC, the $47M exception for military and aerospace equipment & military weapons applies to all task orders issued under SeaPort NxG. We request the Government modify the RFP to indicate that the $47M exception to NAICS Code 541330 applies to this task order.

A1. The Government will modify the solicitation to reflect the changes made to the SeaPort MAC SOW on 6 August 2026 which changed the size standard to $47M.

Q2. RFP Section L, Paragraph L.5.3: The Government did not include an Excel pricing template in the RFP documents. Was this an oversight, or should bidders submit pricing in their preferred format, within the constraints provided in Paragraph L.5.3 of the RFP?

A2. Offerors are free to use their preferred format within the constraints provided in Section L of the RFP.

Q3. We saw the subject line effort has been released. Section L.1 of the SF33 states, " This is an unclassified requirement, and no classified information shall be submitted in response to the solicitation. Program Manager, Marine Air-Ground Task Force Command & Control (PM MAGTF C2) - Portfolio Acquisition Executive Marine Corps (PAE MC) will provide a fair opportunity to small business concerns under North American Industry Classification System (NAICS) code 541330 with a size standard of $25,500,000. The task order is a 100% Service Disabled Veteran Owned Small Business (SDVOSB) set-aside." Could you please confirm this was the correct and intended size standard (25.5M) for NAICS 541330?

A3. See A1.

Q4. Please advise who the incumbent is.

A4. This is a new requirement. Services of similar nature were/are provided by Alexandria Insights, Inc (CAGE Code 6W3T6) and Skylla Engineering LTD. (CAGE Code 32ZH5), under multiple Task Orders.

Q5. Please clarify whether performance under M67854-26-R-3007, either as the prime contractor or as a subcontractor, would preclude or otherwise restrict that entity from competing as a prime contractor or subcontractor on a subsequent PM MAGTF C2 Logistics and Engineering requirement (M67854-26-R-3008), or whether the future contracting restriction applies only when the entity performs specific activities under this task order that create an organizational conflict of interest, such as providing systems engineering and technical direction or developing specifications or statements of work for the subsequent acquisition.

A5. Proposing on M67854-26-R-3007 does not restrict the ability to propose on M67854-26-R-3008 or vice versa.

Q6. The Staffing Matrix Example states that it is "for informational purposes only" and that the information provided should not be viewed as prescriptive. Can the Government clarify whether the example staffing matrix reflects: (1) the current staffing/FTE levels supporting similar efforts, (2) the Government's estimated staffing/FTE expectations for this requirement, or (3) a notional example provided solely to illustrate the format and level of detail expected in the staffing matrix submission?

A6. The example staffing matrix reflects (3) a notional example provided solely to illustrate the format and level of detail expected in the staffing matrix submission. Vendors can modify the content and structure to clearly articulate the staffing approach. After modifications, staffing matrix must still meet page count.

Q7. Section L.5.2 requires past-performance efforts to be ongoing or completed within 36 months of solicitation issuance, while Section M.4.2 defines recent performance as any 12-month period performed within the past five calendar years. Please clarify which recency standard governs the acceptability and evaluation of submitted past-performance references.

A7. Past five calendar years, solicitation will be amended to clarify.

Q8. For a past-performance reference performed as a first-tier subcontractor, will the Government assess relevance, magnitude, and complexity based on the Offeror's actual scope, staffing, and value of work performed rather than the total value and scope of the prime contract?

A8. The Government will consider all relevant information regarding past performance including actual work scope, staffing, and value in addition to the total value and scope of the prime contract. The Government reserves the right to use any and all information that might accurately reveal the “scope and complexity” of any referenced effort.

Q9. Does the staffing level, labor-category mix, and projected labor hours reflected in Attachment 04 represent the Government's current planning assumptions used in developing its independent Government estimate and/or evaluating price realism?

A9. See A6 Q10. If Attachment 04 does not represent the Government's anticipated level of effort, please provide the Government's estimated annual FTE or labor-hour level by PWS functional area: Operations Services, Program Management, Software License Management, Data and System Management, and Financial Analysis.

A10. Pursuant RFO 37.102(a)(2) that information is outside the purview of a PWS which provides required outcomes. Interested offerors should develop their own unique staffing approach to the requirement as described in the PWS.

Q11. Please confirm whether the 1,880 annual hours identified in Attachment 04 represent the Government's intended productive labor-hour assumption for one FTE for staffing and price-realism purposes.

A11. See A6.

Q12. May an Offeror propose fewer total FTEs than reflected in Attachment 04 if its technical and staffing approach demonstrates that all PWS requirements can be fully performed?

A12. See A6.

Q13. For price-realism evaluation, will the Government assess the adequacy of proposed staffing primarily against the Offeror's technical approach or against an independent Government FTE/labor-hour estimate?

A13. The Government will evaluate staffing against the technical approach IAW Section M of the solicitation.

Q14. Does the requirement to be "fully staffed" within 15 calendar days after award mean that every proposed FTE must be onboarded, cleared as applicable, and available to perform assigned duties by the fifteenth calendar day?

A14. Yes, Government expectation is that all personnel are available to perform assigned duties by the 15th calendar day after award. The PWS has been amended to reflect the expectation that the Contractor “be fully . . . prepared to execute all tasks under this PWS.” Section C.4. Additionally, “[t]he Contractor shall be solely responsible for ensuring that it hires personnel who are capable of attaining and maintaining security and facility access as needed to perform the work described in this PWS” as described in Section 11.4 of the PWS.

Q15. Will the Government permit personnel access processing, credentialing, account establishment, and other transition/onboarding activities prior to the December 1, 2026 start of performance?

A15. Government will work with the Vendor to establish building access, credentialing, and other onboarding activities starting on first day of Period of Performance.

Q16. PWS C.5.1.1 requires the contractor facility to support meetings of 10–20 personnel, meetings of up to 40–50 personnel, and classified meetings of 10–20 personnel. Please confirm whether the contractor facility is required to provide permanent workspaces for contractor FTEs, or whether the facility requirement may be satisfied through office and meeting/conference space sufficient to support the stated meeting requirements.

A16. The Contractor should be prepared to provide workspace for its personnel supporting this effort.

Q17. May the Prime Contractor satisfy the classified-meeting facility requirement through an appropriately cleared leased, shared, or otherwise authorized facility located within the required 15-mile radius?

A17. Yes, provided that the facility is held directly by the Prime Contractor or an approved subcontractor, meets the required facility security clearance and safeguarding level at the time of proposal/award as specified in the RFP, and is located within the designated 15-mile radius. Informal, ad hoc, or non-contractual sharing arrangements are not permitted.

Q18. Please identify which PWS functions or labor categories the Government anticipates will routinely perform at the Government site rather than the Prime Contractor's facility.

A18. PWS C.4.2.1/C.4.2.2, Operations and Administrative are the support personnel the Government expects to provide space within Government facilities.

Q19. For proposed Financial Analyst personnel, is prior hands-on experience with each Government financial system identified in the PWS and CDRLs a mandatory qualification, or may equivalent DoD financial-system experience satisfy the requirement?

A19. Section M.4.1, "the Government will evaluate the extent to which the staffing plan demonstrates qualified, experienced, and suitable staffing criteria for performing the requirements." "Prior hands-on experience with each Government financial system," would be a part of " demonstrated qualified, experienced, and suitable," but not mandatory.

Q20. Several CDRLs state that the initial submission shall occur during "pre-award"; however, Section L does not identify these CDRLs as proposal deliverables. Please confirm that no B001–B007 CDRL submission is required with the Offeror's proposal unless specifically identified in Section L.

A20. No CDRLS are due prior to the first day of performance. No "AS REQUIRED" CDRLs will be assigned earlier than the first day of performance. Due date on any CDRL assigned on first day of performance will be negotiated with Vendor appropriately based on complexity. Block 16 of the CDRLs will be updated to eliminate the “pre-award” requirement.

Q21. Given that the primary service CLINs are Firm-Fixed-Price while Attachment 04 is identified as informational and non-prescriptive, please identify the historical workload data, transaction volumes, deliverable quantities, labor hours, or other measurable workload assumptions the Government used to establish the FFP requirement.

A21. Historical data would not be representative, as prior PMO support TO's included requirements not present on this solicitation and vice versa. The Government based its decision to utilize FFP labor CLIN's on the Market Research performed and IAW EO 14402, which directs the use of Fixed-Price Contracting to the maximum extent.

Q22. PWS C.5.1.1 requires the contractor to establish an on-site rate, while Section B provides one monthly firm-fixed-price unit-price field for each task CLIN. Please specify the required price-proposal structure for the on-site rate.

A22. See A2.

Q23. In order for all offerors to submit a consistent price proposal, will the Government provide a Price Workbook for all submissions?

A23. See A2.

Q24. The text of the above referenced section refers to the titles and contents of the “volumes”, however the referenced table does not include “volumes” but only “Factor”. Are Offerors to presume that Factor 1, Factor 2, and Factor 3, refers to Volume 1, Volume 2, and Volume 3?

A24. Per the Offer Template the volumes are not numbered, rather they are named- Factor 1 – Technical Approach, Factor 2 – Past Performance, and Factor 3 – Price Proposal.

Q25. What is the name(s) of the AI tools that the Government may use for proposal evaluation?

A25. The US Army’s Fostering Acquisition Streamlining Through Technology, Rapid Automation, and Contracting Knowledge (FAST TRACK) Evaluation Tool Q26. The Government does not refer to figures/illustrations for the font size, only body text, and tables. Will the Government accept 10-point Times New Roman for figures/illustrations?

A26. Yes, 10-point font for figures/illustrations is acceptable.

Q27. Section L.3 requires proposal submission through PIEE, while DFARS 252.215-7012 directs submission of the cost portion through electronic mail (e-mail). Please confirm the required submission method for the Factor 3 Price Proposal.

A27. Clause and Section L text updated, Offerors may submit through either PIEE SOL or e-mail.

Q28. Section L.5.2 limits offeror-submitted summaries to efforts that are ongoing, currently active, or completed within 36 months of solicitation issuance, while Section M.4.2 defines recent performance as any 12-month period of effort performed within the past five calendar years. Please confirm the controlling recency window for offeror-submitted past-performance references.

A28. See A7 Q29. Please confirm whether the 1,880-hour work-year value shown in the Staffing Matrix Template is a mandatory full-time-equivalent conversion assumption for all Offerors.

A29. See A6 Q30. Please confirm whether the one on-site FTE shown for each of PWS C.4.2.1 Operations Services and PWS C.4.2.2 Administrative Services in the Staffing Matrix Example represents a minimum or exact staffing requirement.

A30. See A6 Q31. The requirement is for a SECRET FCL and for a facility for meetings the may require handling sensitive and/or CUI marked documents. A CMMC Level 2, C3PAO certification reduces cybersecurity risk before award, provides independently validated cybersecurity maturity, better protects the Government, reduces post-award compliance issues, and aligns with the DoD/DoW’s long-term cybersecurity objectives. Therefore, will the Government add the requirement for all Offerors to hold a CMMC Level 2 (C3PAO) certification at time of proposal submission?

A31. The Government will not add that requirement at this time.

Q32. Please confirm that, except where the PWS specifically requires on-site performance or identifies a specific personnel qualification, the Government does not require a minimum number of FTEs or specific labor-category mix, and Offerors may propose the staffing approach they determine sufficient to meet all PWS requirements and performance standards.

A32. Confirming the Government does not require a minimum number of FTEs or specific labor-category mix, and Offerors may propose the staffing approach they determine sufficient to meet all PWS requirements and performance standards.

Q33. PWS C.9.1 requires contractor and subcontractor personnel to sign the nondisclosure agreement identified as Section J Attachment 8, while Section J lists only Attachments 01 through 05. Please provide or identify the applicable nondisclosure agreement.

A33. NDA’s will be provided post award, language in C.9.1 has been updated to reflect this change.

Q34. Are the LCATS and associated FTEs the staffing solution that the Government requires?

A34. See A6 Q35. Without the Government specifying the labor categories (LCATS) and the number of hours (FTEs), the incumbent contractor is the only offeror with knowledge of the required staffing model. In order for a fair competition amongst all offerors, will the Government provide the required LCAT titles and associated FTEs?

A35. Historical data would not be representative, as prior PMO support TO's included requirements not present on this solicitation and vice versa. Offerors should adjust the details of the staffing matrix to match their business approach as they see fit to meet the requirements of the PWS.

Q36. RFP, paragraph L.5.1 Staffing Plan: Is it permissible for offerors to add columns to the Staffing Matrix, as long as the page count limitation is not exceeded?

A36. Offerors may add columns so long as the page count limitations are not exceeded.

Q37. PWS C.4.3.4.1 requires the Contractor to create JIRA dashboards and manage Portfolio Kanban metrics across all ARTs, and PWS C.5.2.1 requires the Contractor to procure IT assets connecting to the MCEN under the ODC CLIN. Is the Government providing the JIRA instance and licenses, or does the Contractor procure JIRA under the ODC CLIN?

A37. Government will provide JIRA instance access and licenses.

Q38. PWS C.4.3.4.1 requires the Contractor to create JIRA dashboards and manage Portfolio Kanban metrics across all ARTs, and PWS C.5.2.1 requires the Contractor to procure IT assets connecting to the MCEN. Approximately how many MCEN-connected IT assets (e.g., computers) does the Government anticipate the Contractor will need to procure over the period of performance?

A38. Any contractor personnel that need access to Controlled Unclassified Information (CUI) material or access to government systems will require MCEN-Connected IT. Exact quantities will be solidified at kickoff brief.

Q39. PWS C.5.3.1 requires CONUS and OCONUS travel priced as a Cost-No-Fee CLIN. Will the Government provide a Time and Material plug (not-to-exceed) figure for the travel CLIN for pricing purposes?

A39. Government will provide Travel/ODC NTE amounts upon award.

Q40. PWS C.4.5.1 requires SharePoint development, administration, and maintenance support. Please identify whether the current PM MAGTF C2 SharePoint environment is on-premises or SharePoint Online (Microsoft 365), its approximate scale (site collections/sites, data volume), and whether migration from legacy capabilities (e.g., SharePoint Designer 2013, InfoPath) is anticipated during the period of performance.

A40. Microsoft O365 SharePoint administration for 8 groups within the PMO. No legacy migration. Primarily data management/organization and workflow development.

Q41. Is a transition or overlap period planned with the incumbent contractors, or does full performance begin 1 December 2026? PWS C.4.1.1 requires the Contractor to be “fully staffed” within 15 calendar days after award. Please clarify whether this means 100 percent of proposed FTEs must be performing within 15 calendar days, or whether the Government will permit a phased onboarding schedule for personnel awaiting CACs, MCEN access, system accounts, badges, or other Government-controlled access.

A41. See A14.

Q42. PWS C.3.1.1 identifies support across seven Agile Release Trains/functional teams (PMT, SIT, MCA, CCA, CSA, Hardware & Infrastructure, Product Support & Sustainment), and states work will otherwise be performed at the Contractor's facility while select tasks are designated on-site at Government facilities. Please identify the Government's anticipated on-site versus off-site FTE split, by PWS functional area/ART, including which ARTs or functions are expected to require the greatest level of Contractor support.

A42. See A18 (on-site) See A10 (breakout of FTE) Q43. Please provide the approximate size and complexity of the current MAGTF C2 COTS software portfolio to be managed under PWS C.4.4 (e.g., approximate number of software products/vendors, licenses, or annual license actions), and identify the Government-approved tracking tool currently used for software utilization and accounting.

A43. Current license portfolio includes dozens of different licenses, with various license structures (enterprise, annual renewals) all on different timelines. Government will provide tracking software and/or tool which will be treated as Controlled Unclassified Information (CUI) data.

Q44. Section L.4.1 states the Government may employ AI to assist in the analysis and review of Offeror proposals, including summarizing content, assessing compliance, and highlighting strengths, weaknesses, and risks. To help Offerors prepare submissions that are properly read by any automated tool beyond summarization and compliance/strength-weakness identification, what specific functions will the tool perform, and at what stage(s) of the evaluation (initial compliance screen, technical evaluation, past performance assessment, price analysis) will it be used?

A44. The Government will not expand beyond the wording in Section L.4.1: “The Government may employ AI as a tool to assist in the analysis and review of Offeror proposals.”

Q45. Please provide the approximate magnitude of the financial-management workload anticipated under PWS C.4.6 (e.g., number of programs/product teams supported, funding lines, annual funding actions, or approximate annual portfolio value), to enable realistic staffing and pricing for this FFP scope (formulation, execution, DAI/SABRS/CERBERUS, POM, and reporting).

A45. PWS Para C.3.1 describes the teams supported. Resources are managed at the PM MAGTF C2 level and executed by the various teams within Para C. 3.1 with a total authorization of approximately $400M in current year funding.

Q46. Section L.5.2 requires past performance references to be currently active or completed within 36 months of solicitation issuance, while Section M.4.2 defines a “Recent” effort as any 12-month period of performance within the past five calendar years from solicitation release. Please clarify the controlling recency period for past performance references submitted with the proposal.

A46. See A7 Q47. Section L.5.3 requires Offerors to price every CLIN in the model contract but does not prescribe a format for the supporting cost/price backup data (labor categories, hours, rates, escalation) used to derive those prices, and Amendment 1 Q&A (Q2/A2) confirmed no Excel pricing template will be issued. Given that Section M.4.3 requires the Government to evaluate price realism and reasonableness across all Offerors, will the Government reconsider issuing a standardized pricing backup template (e.g., a workbook organized by CLIN, labor category, and period of performance)?

A47. Government has reconsidered and will provide a standardized pricing template.

Q48. Section L.5.3 requires Offerors to price every CLIN in the model contract but does not prescribe a format for the supporting cost/price backup data (labor categories, hours, rates, escalation) used to derive those prices, and Amendment 1 Q&A (Q2/A2) confirmed no Excel pricing template will be issued. Does the Section L.5.3 requirement that unit prices be priced to the nearest whole dollar and evenly divisible by quantity apply only to the final Section B CLIN entries, or also to supporting pricing backup detail (e.g., burdened labor rates, escalation factors)?

A48. Requirement applies at the CLIN level.

Q49. CDRLs B001 through B007 each state the initial submission “shall be delivered during pre-award.” Please clarify which of these deliverables, if any, are required to be submitted with the Offeror's proposal, and where they should be included, as Section L does not expressly identify them as proposal submission requirements.

A49. See A20 Q50. PWS C.10.2 specifies compliance with NIST SP 800-171 Revision 1. Please confirm the NIST SP 800-171 revision and associated DoD cybersecurity/CMMC requirements that will apply at contract award and throughout performance and identify any minimum SPRS assessment score or CMMC status required for award.

A50. NIST SP 800-171 Rev 3. Specific controls and directions are identified in PWS C.10.2.

Q51. The Government-provided sample staffing matrix template is an Excel workbook. The SF 33 document, Section L.3.1 establishes a two-page limitation for the Staffing Matrix. Will the Government permit Offerors to submit the completed staffing matrix template in landscape?

A51. Offerors may submit the completed staffing matrix template in landscape Q52. Section L.5.2 submitted past performance efforts to those ongoing, currently active, or completed within 36 months of solicitation issuance, while Section M.4.2 defines recent efforts as any 12-month period of performance within the past five calendar years from solicitation release. Which recency period will govern the evaluation of submitted past performance references?

A52. See A7 Q53. In M.4.2, the RFP states that the Government may access Contractor Performance Assessment Reporting System (CPARS). Can the offeror provide CPARS information as an appendix in the Technical Volume for the convenience of the government?

A53. Information pertaining to Past Performance should not be included in the Technical Approach and vice versa. Per L.3.1. Past Performance is to be addressed in Past Performance Summaries.

Q54. Would the Government provide an editable version of the Model Contract (SF33, section L.5.3) to facilitate uniform completion of all required fill-ins and representations by offerors?

A54. Offerors are free to edit the PDF or convert the document into Word and make the changes in that manner.

Q55. SF33, L.5.3, Factor 3 cites, "The Offeror shall submit a completed, signed original copy of Sections A, B and Section K". Are offerors required to submit a signed SF 33 as part of the completed Model Contract to satisfy this signature requirement?

A55. Yes.

Q56. SF 33 (Amendment 0001), Section M, Paragraph M.1, and SeaPort-NxG MAC Paragraph C.10.2: Paragraph M.1 requires proposals to comply with this solicitation and with the SeaPort-NxG basic IDIQ MAC. MAC Paragraph C.10.2 allows an affiliated company to propose through the SeaPort portal account of a Prime MAC holder, as long as the proposal clearly identifies the affiliate as the prime. Please confirm that a joint venture may propose on this solicitation through the SeaPort portal account of a joint venture member that holds a SeaPort-NxG MAC, with the joint venture identified as the prime.

A56. SeaPort Portal has sunset and is no longer in use. Please review the latest SeaPort MAC Section C.10.3 – Joint Ventures (JVs) for more information pertaining to Joint Ventures.

Q57. SF 33 (Amendment 0001), Section L, Paragraph L.1: Paragraph L.1 states that the required Secret Facility Clearance will be verified using the Prime Offeror's registered CAGE code. Where a joint venture proposes through a member's SeaPort-NxG MAC under MAC Paragraph C.10.2, please confirm that the Government will verify the Secret Facility Clearance against the CAGE code of that Prime MAC holder.

A57. Facility Clearance will be verified against the contractor that owns the facility to be used. The contractor that has the facility must be contractually proposed as part of this effort. Informal, ad hoc, or non-contractual sharing arrangements are not permitted.

Q58. SF 33 (Amendment 0001), Section L, Paragraph L.3.1: Paragraph L.3.1 lists the contents of all three proposal volumes and does not include a joint venture agreement. We understand the 13 CFR 125.8(d) certification of compliance is due before performance, not with the offer. For a joint venture Offeror, is the joint venture agreement itself a required proposal submission, and if so, in which volume should it be placed?

A58. No, however, should the winning Offeror be a Joint Venture, that documentation shall be provided and included in the subsequent Contract.

Q59. SF 33 (Amendment 0001), Section L, Paragraph L.5.2: Paragraph L.5.2 requires at least one past performance summary for an effort the Offeror performed as a prime contractor. Whichever recency period the Government confirms, must that prime contractor summary also fall within it, or may an older prime contract be submitted only to meet the prime contractor requirement?

A59. Past Performance must be within the past five calendar years from solicitation release date.

Q60. SF 33 (Amendment 0001), Section L, Paragraph L.5.2: Paragraph L.5.2 calls for past performance summaries and does not mention Past Performance Questionnaires. Where a submitted reference does not yet have a final CPARS evaluation, will the Government accept a Past Performance Questionnaire completed by that customer?

A60. Offerors shall provide a Past Performance Cover Letter (1 page) and 3 Past Performance Summaries (max 6 pages).

Q61. Performance Work Statement, Paragraph C.5.1.1: Paragraph C.5.1.1 requires the Contractor to provide a meeting facility within 15 miles of the Government site, able to hold 40 to 50 people, with network and conference calling capability and cabled internet for at least twenty computers. Must the Offeror have this facility under lease by the proposal due date, or is a commitment to have it in place before the start of performance acceptable?

A61. Government expectation is that facilities are in place and available on the first day of performance.

Q62. Performance Work Statement, Paragraph C.5.2.1 and SF 33 (Amendment 0001), Section L, Paragraph L.5.3: Paragraph C.5.2.1 requires the Contractor to buy all IT assets that connect to the Marine Corps Enterprise Network (MCEN) through the ODC CLIN, and Paragraph L.5.3 has Offerors price ODC at $0.00, with amounts added by the Government at award. Separate from travel, please provide the estimated number of MCEN-connected computers and the ODC amount the Government intends to incorporate at award.

A62. See A38 Q63. Section J, Attachment 05 (Staffing Matrix Template), Note 2, and SF 33 (Amendment 0001), Section L, Paragraph L.5.1: The Staffing Matrix Template requires minimum education and experience for each labor category, and Note 2 states the Government intends to incorporate the proposed qualifications into the resulting contract. May Offerors include substitutions within a labor category definition, such as additional years of experience in place of a degree, or a degree in place of experience?

A63. See A6 Q64. Performance Work Statement, Paragraphs C.2.2.2 and C.2.2.5: Paragraphs C.2.2.2 and C.2.2.5 describe work performed within the Scaled Agile Framework, including Program Increment planning and system demonstrations. Does the Government require a specific SAFe certification, for example SAFe Agilist, SAFe Scrum Master, or SAFe Program Consultant, for any labor category on this effort?

A64. No.

Q65. DD Form 254, Block 1a, and Performance Work Statement, Paragraph C.10: The DD Form 254 requires a Secret Facility Clearance, but neither the DD Form 254 nor Paragraph C.10 addresses individual personnel eligibility at the start of performance. Will personnel holding interim Secret eligibility be allowed to begin performance on 1 December 2026, or must all personnel hold final adjudicated Secret eligibility on that date?

A65.Interim Secret is acceptable.

Q66. SF 33 (Amendment 0001), Section L, Paragraph L.5.1: Paragraph L.5.1 asks Offerors to show which positions will be filled by readily available personnel, contingent hires, or subcontractors, but also says not to identify specific individuals and that resumes will not be reviewed. Are letters of intent or other individual-specific documents permitted, or does the Government expect a narrative statement of availability by position?

A66.See A14.

Q67. DD Form 254, Block 10k, and Performance Work Statement, Paragraph C.5.2: Block 10k of the DD Form 254 indicates SIPRNet access is required. Please identify approximately how many positions will need SIPRNet access, and confirm that this access will be provided at Government facilities rather than at the Contractor's facility.

A67. SIPRNET access will be provided at Government facilities. Access requirements will be addressed at kickoff brief.

Q68. PWS C.5.1.1 and C.7.1 require the Contractor’s facility to be within 15 miles of 105 Tech Parkway, Stafford, VA 22556. Is the 15-mile distance measured as a straight-line radius or as driving distance?

A68. Driving distance.

Q69. PWS C.5.1.1 requires the Contractor’s facility to accommodate meetings ranging from 10 to 20 people up to 40 to 50 people. Approximately how many times per year does the Government anticipate requiring the 40 to 50 person meeting capacity at the Contractor’s facility?

A69. Approximately 15-20. Standard battle rhythm calls for once a month with remainder being ad hoc.

Q70. L.5.2 defines recent past performance as efforts that are ongoing, currently active, or completed within the last 36 months from the date of solicitation issuance. M.4.2 states that recent efforts are any 12-month period performed within the past five calendar years from the date of solicitation release. These definitions differ. Which will the Government apply when assessing recency?

A70. See A7 Q71. The Staffing Matrix Example at Attachment 2 reflects 19 full-time equivalents in the base period and in each option period. Does this represent the Government’s expected level of effort for this requirement, and will a proposal reflecting a materially different total FTE count be evaluated adversely under Factor 1?

A71. See A6 Q72. Section B establishes separate firm-fixed-price CLINs aligned to PWS C.4.2 through C.4.6. May an Offeror distribute labor categories and FTEs across those CLINs differently than shown in the Attachment 2 Staffing Matrix Example, provided all PWS requirements are met?

A72. See A6 Q73. Section B shows the unit for each labor CLIN as “12 Months” and does not populate the Quantity column. Please confirm that the Offeror shall enter a quantity of 12, a monthly unit price, and an extended amount equal to twelve times the unit price for each of these CLINs.

A73. Confirming “Quantity” is 12, “Unit Price” is “Months”, and “Amount” is the extended amount equal to twelve times the unit price for each of these CLINs Q74. PWS C.5.1.1 states that the Contractor shall establish an on-site rate and bill only that rate for on-site individuals. Separate on-site and off-site rates for each labor category are not required in the price proposal. Section B directs the Offeror to provide a monthly price for each SLIN which is escalated at a rate determined by the contractor. As a FFP bid, please clarify what rates are required by the Offeror to submit?

A74. Requirement to establish an on-site rate has been removed from PWS. Prices will be evaluated at the CLIN level.

Q75. PWS C.5.1.1 states that selected tasks will be performed on-site at the Government’s facility with Government-furnished workspace. Which PWS tasks or labor categories does the Government consider on-site positions for this purpose?

A75. See A18 Q76. Section B identifies a 12-month base period and four 12-month option periods but does not state calendar dates. What is the Government’s anticipated award date, and what are the anticipated start and end dates of the base period of performance?

A76. Section F of the SF33 reflects those dates.

Q77. Approximately how many contractor personnel does the Government anticipate will require SIPRNet access, and will the Government furnish SIPRNet laptops / terminals and accounts at a Government facility for those personnel?

A77. See A67 Q78. PWS C.4.5.1 identifies Coras Works, SharePoint Designer 2013, and InfoPath as tools to be used. Please confirm that these products remain in the current production environment, and state whether the Government anticipates a migration to SharePoint Online or the Power Platform during the period of performance.

A78. Current environment is SharePoint via Microsoft O365. See A40.

Q79. PWS C.5.1.1 states that C.4.2.1 and C.4.2.2 are "on-site" and that "the Contractor shall establish an on-site rate and bill only that rate for those on-site individuals." However, Section B provides only one FFP CLIN per functional area (e.g., CLIN 5000 for all of C.4.2 Operations Services, which includes both on-site and off-site work). Should the Offeror propose a single blended rate per CLIN, or does the Government expect separate on-site and off-site rates within a single FFP CLIN?

A79. See A74.

Q80. PWS C.5.1.1 requires the contractor facility to be "capable of hosting both unclassified and classified meetings of 10-20 people." Please clarify the classification level for the classified meeting capability. Specifically, does the facility require a Sensitive Compartmented Information Facility (SCIF) or an accredited Secret-level conference space? Is a Government-accredited facility required at contract award, or can the contractor utilize a Government facility or alternate accredited space for classified meetings while establishing accreditation?

A80. PWS will be amended to only require the 40-50 people Unclassified Space. There is no requirement for classified meeting space.

Q81. PWS C.5.1.1 states "ODCs do not include Reimbursement for the Prime Contractor's facility costs." Please confirm that all contractor facility costs (lease, classified space, internet cable link for 20+ computers, Wi-Fi, conference calling, and bridge telephone numbers for all Team Leads and APMs) should be included in the FFP CLINs and not billed as ODCs under CLINs 7000–7400.

A81. Correct.

Q82. Section B does not include a separate FFP CLIN for C.4.1 Contract Maintenance and Execution (PM/single POC). Should the cost of the Contractor's PM (the single POC required by C.4.1.1) be distributed across CLINs 5000–5004, or should it be included in a specific CLIN? If distributed, does the Government have a preferred allocation methodology?

A82. Offeror discretion.

Q83. PWS C.5.2.1 requires the Contractor to "procure all IT assets that connect to the Marine Corps Enterprise Network (MCEN)...via the applicable Contract Other Direct Cost (ODC) Contract Line Item Number (CLIN)." Please confirm whether the Government expects the Contractor to procure laptops/computers for all 19 FTEs, or only for contractor personnel not working on-site at the Government facility (where the Government provides "connection to the Marine Corps network" per C.5.1.1). Additionally, please confirm whether the Government will provide the current MCEDS Supported Models list to the awardee.

A83. See A38. Per PWS C.5.2.1 “the Contractor shall procure only those makes and models listed on the Marine Corps Enterprise Desktop Standardization (MCEDS) Supported Models list.”

Q84. The Staffing Matrix identifies two separate positions under C.4.5 Data and Systems Management: "SharePoint Management" and "JIRA Management." PWS Section C.4.5.1 describes SharePoint-related tasks in detail but does not contain a separate subsection for Jira-specific tasks. Jira dashboard and Portfolio Kanban responsibilities appear in C.4.3.4.1 (IPT Services). Please clarify: (a) Should the Jira Management Specialist perform the Jira-related tasks described in C.4.3.4.1, the SharePoint/data management tasks in C.4.5.1/C.4.5.2, or both? (b) Is the Jira Management Specialist expected to work on-site at the Government facility or at the Contractor's facility?

A84. JIRA support is described in C.4.3.4.1 and work site will be contractor’s facility.

Q85. PWS C.3.1.1 states "The Contractor shall have personnel located in the Quantico, VA area and will be either on Government site or at the Contractor's facility." C.4.2.1 and C.4.2.2 are explicitly designated as "on-site." For the remaining task areas (C.4.3, C.4.4, C.4.5, C.4.6), please clarify: (a) Are these personnel expected to work primarily on-site at the Government facility, primarily at the Contractor's facility, or at a mix determined by the COR? (b) Does the Government have an estimated percentage split between on-site and off-site work?

A85. C.4.3, C.4.4, C.4.5, and C.4.6 personnel are at contractor’s facility.

Q86. CDRLs B001 (Tier 1 Suppliers of Covered Defense Info), B006 (Status Report Security), B007 (System Security Plan), and B008 (Cyber Incident Reporting) all reference "PWS, Section C.10.5" as the contract reference. However, the PWS provided with the solicitation does not appear to contain a Section C.10.5. Please clarify: (a) Will a Section C.10.5 be provided via amendment? (b) Should Offerors assume that standard DFARS 252.204-7012 cybersecurity requirements apply in lieu of a specific C.10.5?

A86.C.10.5 in the PWS includes sub paragraphs C.10.5.1-3 included in the PWS.

Q87. Section B CLINs 7000–7400 reference "Travel and Other Direct Costs - the Contractor shall perform IAW PWS C.5.2, C.5.3, and their subsections." However, the PWS provided with the solicitation does not appear to contain a Section C.5.3. Please clarify: (a) Will a Section C.5.3 be provided via amendment? (b) What categories of Other Direct Costs (beyond IT assets per C.5.2 and travel per Section G.3) does the Government anticipate under these CLINs?

A87.C.5.3 in the PWS includes sub paragraph C.5.3.1.

Q88. Please confirm whether submission of solicitation questions through the PIEE Solicitation Module satisfies L.2, or whether questions must instead be submitted by email to all three listed Government points of contact.

A88. Offerors may use either method.

Q89. Please confirm the required submission channel for the Cost/Price Proposal when the complete proposal is submitted through PIEE, in light of DFARS 252.215-7012 stating that the cost portion shall be submitted by electronic mail.

A89. See A27 Q90. Please identify the transition and onboarding requirements the Government expects Offerors to address, including the assumed transition duration and any incumbent overlap, because M.4.1 expressly evaluates onboarding but L.5.1 does not provide a separate onboarding instruction.

A90. See A14 for Government onboarding expectations.

Q91. Please confirm which FFP CLIN or CLINs should include the cost of PWS C.4.1 Contract Management and Execution, since Section B contains CLINs for PWS C.4.2 through C.4.6 but no separate CLIN for C.4.1.

A91. See A82 Q92. For CDRL CLINs 8000, 8100, 8200, 8300, and 8400, please confirm whether Offerors should enter “NSP,” enter $0, or leave the unit-price and amount fields blank.

A92. Leave blank, however, Offerors will not be penalized should they put NSP or $0.

Q93. Please identify the specific price-support information Offerors must submit to permit the price-realism evaluation described in M.4.3, beyond the completed CLIN pricing in Section B.

A93. Competition will determine realism.

Q94. Please confirm that Attachment 05 is the required Staffing Matrix submission template and state whether the completed matrix must be submitted in its native spreadsheet format or rendered within the two-page proposal limit.

A94. See A6 Q95. Because proposed staffing qualifications will be incorporated into the resulting contract, please confirm whether post-award personnel substitutions may satisfy the requirement through qualifications that are equal to or greater than those proposed.

A95. Yes, qualifications that get incorporated into the contract will be minimum requirements.

Q96. Please define the specific systems, components, services, and future procurements that would be subject to the G.5 limitation on future contracting, and confirm whether the restriction applies only where the Contractor actually performs the specification-development or systems-engineering work that creates the conflict.

A96. Per Section G.5, “If the Contractor, under the terms of this task order, or through the performance of tasks pursuant to this task order, is required to provide systems engineering and technical direction for a system or helps to develop specifications or statements of work to be used in a competitive acquisition, the Contractor shall be ineligible to supply the system or major components of the system as a prime Contractor and shall be precluded from being a Subcontractor or consultant to a supplier of the system or any of its major components under an ensuing Government contract.” This is a blanket obligation imposed by regulation and cannot be limited by the Government defining specific future system, components, services, and future procurements in this PWS.

Q97. Please confirm whether the positions or functional areas identified in the PWS as “on site” under Operations and Administrative represent the full set of Contractor personnel expected to work at Government facilities, and identify any other roles requiring routine or recurring Government-site presence.

A97. See A18. All roles are expected to be available for routine and ad hoc government site presence based on team being supported.

Q98. The DD254 identifies a Secret-level requirement, and the PWS requires the Contractor to support Secret discussions at its facility for approximately 10–20 participants. Please confirm whether Contractor personnel, including developers, will be required to create, receive, retain, or otherwise possess classified notes, action items, technical artifacts, or other records from those discussions. If so, will the Government revise the DD254 to authorize the applicable receiving, generating, and/or possessing requirements and associated safeguarding capability?

A98. The contractor will only be expected to access classified at another contractor or government spaces. There is no requirement for safeguarding. PWS will be amended to reflect.

Q99. Please confirm whether every individual performing under the contract must hold an active Secret clearance, or only personnel assigned to classified tasks or requiring access to classified information, SIPRNet, or controlled Government spaces. If clearance requirements vary by labor category or task, please identify the applicable positions.

A99. Government expects all personnel to have secret eligibility except administrative support (PWS C.4.2.2).

Q100. Please confirm whether SIPRNet access will be provided exclusively at Government facilities or whether the Government expects a SIPRNet connection or approved remote-access capability to be installed at the Contractor facility. If Contractor-facility access is required, please identify which party is responsible for installation, accreditation, equipment, recurring service, physical safeguards, and associated costs.

A100. SIPRNet access will only be required at Government facilities.

Q101. The Government stated in Question and Answer No. 4 that these or similar services are currently being provided by multiple vendors. Please provide the contract and task order numbers associated with the incumbent efforts supporting these requirements.

A101. M67854-21-F-3008, M67854-22-F-3004, and M67854-23-F-3003 Q102. Please clarify the controlling past-performance recency standard. Section M.4.2 defines recent efforts as any 12-month period performed within the five calendar years preceding solicitation release, while Section L.5.2 requires efforts that are ongoing, active, or completed within 36 months of solicitation issuance. Should Offerors apply the five-year standard or the 36-month standard when selecting references?

A102. See A7 Q103. Is there an incumbent? If so, can you please provide the associated contract number and value?

A103. See A101 Q104. RFQ L.3.1: Please confirm that each proposal factor is intended to be a separate volume.

A104. Confirming each proposal factor is intended to be a separate volume.

Q105. PWS C.5.1.1, C.7.1: Would the contractor facility within 15 miles of the government location solely be for the purpose of conducting conferences/meetings?

A105. Requirement is to allow government and contractor personnel be readily available for ad hoc in person collaboration. Given the volume of work, the number of Government personnel, the high volume of traffic in the Northern Virginia area, and the scarcity of time, the mileage distance represents a reasonable commuting expectation for ad-hoc in-person meetings as may be needed during the period of performance. This distance limit ensures that Government and contractor personnel can quickly travel between facilities as needed to facilitate ad-hoc meetings within a single workday. This is the agency requirement.

Q106. PWS C.5.1.1, C.7.1: Would the government be willing to remove the requirement for the contractor facility to be within 15 miles, as it is highly unusual for classified meetings to take place at a contractor facility.

A106. See A98.

Q107. RFQ Section L.3 states that proposals can be submitted via email to prevent late submissions in the event of PIEE outage. Can proposals only be submitted via email if PIEE is down, or are email submissions allowed in either case?

A107. See A27.

Q108. RFQ L.5.3: Please confirm that the SF-30 is required to be submitted as Section A of the model contract. If not, where should it be included, and what should go in Section A?

A108. Confirming that the SF33 is required to be submitted as Section A of the model contract.

Q109. RFP Sections L.5.2 and M.4.2: Section L.5.2 limits past performance summaries to efforts ongoing, active, or completed within 36 months of solicitation issuance, while Section M.4.2 defines recent performance as any 12-month period performed within the past five calendar years. Please clarify which recency criterion governs past performance references.

A109. See A7 Q110. PWS C.4.4.1: Please identify the current PMO-approved tool(s) used to track the COTS software portfolio.

A110. There is no current tool. Effort is currently being standardized.

Q111. PWS C.4.4.1: Please provide the approximate size of the current COTS software portfolio, such as the number of software products, licenses, or active procurements/renewals managed annually.

A111. See A43 Q112. Please confirm whether submitted past performance must satisfy the 36-month window in L.5.2, or whether the five-calendar-year recency standard in M.4.2 governs.

A112. See A7 Q113. Sections L.1 and M.1 cite different fair-opportunity authorities. Please confirm the correct authority governing this procurement.

A113. RFO 16.507-2

Q114. Please confirm whether the CAS provisions (FAR 52.230-1, 52.230-7) and Cost Estimating System Requirements clause (DFARS 252.215-7002) apply to this commercial FFP requirement or were incorporated in error.

A114. Clauses will be deleted Q115. Please confirm whether FAR 52.217-8 (Option to Extend Services) is incorporated and, if so, how the 6-month extension will be priced and evaluated.

A115. FAR 52.217-8 is not incorporated Q116. Please confirm whether a site visit will be offered under FAR 52.237-1 and, if so, provide the date, location, and registration instructions.

A116. Clause will be removed, Site Visits are not possible at this time.

Q117. For this FFP effort, please confirm how a price found “unrealistically low” will be treated — specifically whether it may render a proposal ineligible for award without an opportunity to revise the price.

A117. See Section M.4.3 Factor 3 Price Q118. For price realism, will the Government assess the relationship between proposed staffing/FTE levels (Factor 1) and the corresponding FFP pricing, or evaluate price realism independently of the staffing model?

A118. Technical Eval Team and Pricing Team are different entities.

Q119. Must a…