Copy of 2nd DRFP Posting CRM Government Responses.xlsx

XLSX spreadsheet 119 KB Posted

Attached to
Rocket Systems Launch Program Mission Assurance (RSLP MA) Federal contract opportunity
Solicitation number
FA8818-18-R-0003
Issued by
Department of the Air Force Space Command Space and Missile Systems Center

About this file

This is a final request for proposal notice for the Rocket Systems Launch Program Mission Assurance indefinite delivery/indefinite quantity contract. The notice seeks proposals for mission assurance services to support launch planning and execution activities. Key details include that the Air Force Space Command Space and Missile Systems Center will award a single IDIQ contract with a maximum value of $990M over 11 years. Interested vendors must request a copy of the bidders library containing necessary reference documents by May 13, 2020 to be eligible to submit a proposal. Proposals are due by May 27, 2020 and shall be submitted electronically. The notice incorporates responses to industry comments on the draft RFP and provides the final RFP documents and sample mission task orders. Services required include engineering analysis, independent verification and validation, mission risk assessments, and subject matter expertise for various launch missions.

View the file

Other files for this federal contract opportunity

Other files attached to Rocket Systems Launch Program Mission Assurance (RSLP MA), newest first.
File Type Posted
Amend1_FA8818-18-R-0003 Model Task Orders 01-06_11May.pdf PDF
Amendment 0001 SF30_FA8818-18-R-0003_RSLP MA.pdf PDF
CRM Responses_Final_7May2020.xlsx XLSX spreadsheet
FA8818-18-R-0003 Final RSLP MA Solicitation SF33.pdf PDF
FA8818-18-R-0003 Model Task Orders 01-06.pdf PDF

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

Comment Resolution Matrix

Comment Resolution Matrix (CRM)
Instructions:

1. Review the Rocket Systems Launch Program Mission Assurance (RSLP MA) draft RFP.

2. Complete CRM columns (B - G only) to provide feedback and recommended edits.

Comment Type (Column C):

A - Administrative: Comments that address minor items such as typographical, format, and/or grammatical errors.

S - Substantive: Comments of a less serious nature that have noticeable impact on the document’s quality or content. The document appears to be incorrect, misleading, confusing, or inconsistent with other sections.

C - Critical: Comments that address contentious issue(s) that will cause non-concurrence with the publication.

Gov't Decision (Column H):

A - Accept: Agree with comment.

R - Reject: Disagree with comment; rationale required for rejection.

M - Accept with modification: Partially agree with comment; rationale required for modification.

Item #Source DocumentComment Type
A/S/CPage
#Para / Section #Comment

Provide original language and proposed change

Rationale
Provide concise, objective explanation of the rationale for the commentDecision
A/R/MNotes
1Section MC102.5.4Original: "NOTE: The Government will be evaluating travel in the Total Evaluated Price (TEP) in order to normalize this element in the cost evaluation."
Proposed Change: "NOTE: The Government will NOT be evaluating travel in the Total Evaluated Price (TEP) in order to normalize this element in the cost evaluation."The Government has indicated in their response to comments and in verbal discussions that travel will not be evaluated as part of the Total Evaluated Price. The statement in the revised Section M should be modified to be consistent with this previous guidance.MParagraph 2.5.4 has been modified as follows.

"NOTE: The Government will be evaluating travel related to TOID 001 in the Total Evaluated Price (TEP); however, the Government will NOT be evaluating travel related to TOIDs 0002-0006 in the TEP."

2Section MS62.3.1Original: "Combined Technical/Risk Subfactors - Each subfactor (Core/DXBM and Launch IV&V) will receive a Combined Technical/Risk rating as described in Table 2A below. This rating uses the risk descriptions defined in Table 2B below. If, after the Government’s consideration of correction potential (as discussed in paragraph 1.7), a proposal is rated Unacceptable in either subfactor, that proposal will not be evaluated further for the Cost Factor. Such a proposal may result in the Offeror not being considered for the Competitive Range."
Proposed Change: Government intent is not clear.The previous version of Section M had a paragraph 1.7 entitled Correction Potential of Proposals. This paragraph was removed from the latest Section M draft. Therefore, the highlighted text refers to a paragraph that was removed in the last revision to Section M. The Government's intent regarding correction potential for proposals is not clear.ASect M Paragraph 2.3.1 has been changed

FROM: ""Combined Technical/Risk Subfactors - Each subfactor (Core/DXBM and Launch IV&V) will receive a Combined Technical/Risk rating as described in Table 2A below. This rating uses the risk descriptions defined in Table 2B below. If, after the Government’s consideration of correction potential (as discussed in paragraph 1.7), a proposal is rated Unacceptable in either subfactor, that proposal will not be evaluated further for the Cost Factor. Such a proposal may result in the Offeror not being considered for the Competitive Range."

TO: "Combined Technical/Risk Subfactors - Each subfactor (Core/DXBM and Launch IV&V) will receive a Combined Technical/Risk rating as described in Table 2A below. This rating uses the risk descriptions defined in Table 2B below. If a proposal is rated Unacceptable in either subfactor, that proposal will not be evaluated further for the Cost Factor. Such a proposal may result in the Offeror not being considered for the Competitive Range."

3Section LA82.2.2.3Original: "Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems, layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than 12 point. These limitations shall apply to both electronic and hard copy proposals."
Proposed Change: "Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems, layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size and are counted as 2 pages towards the page limitations. For tables, charts, graphs and figures, the text shall be no smaller than 12 point. These limitations shall apply to both electronic and hard copy proposals."Clarifies ambiguity for all Offerors to prepare their proposals consistently.ASect L para 2.2.2.3 has been changed

FROM: "Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems, layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than 12 point. These limitations shall apply to both electronic and hard copy proposals."

TO: "Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems, layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 x 17 inches in size and are counted as 2 pages towards the page limitations. For tables, charts, graphs and figures, the text shall be no smaller than 12 point. These limitations shall apply to both electronic and hard copy proposals."

4PWSA313.3.2.28.7Original: "3.3.2.28.7. ."
Proposed Change: "3.3.2.28.7. Attend and provide technical support to the Mission Manager at post-flight review(s) held by LSC and other mission stakeholders."Missing PWS text in revised draft replaced with text from previous draft PWS.RThe original text of 3.3.2.28.7 stated, "Attend and provide technical support to the Mission Manager at post-flight review(s) held by LSC and other mission stakeholders." This text was intentionally deleted since paragraph 3.3.2.28.3 now reads, " Same as CAT 1". The corresponding CAT 1 paragraph, 3.3.1.28.3 states, "Attend post-mission review(s) held by LSC and other mission stakeholders to provide the Mission Manager with technical support and advice, inform lessons learned and possible anomaly/failure recommendations/resolutions." Therefore, it is not necessary to duplicate essentially the same scope in 3.3.2.28.7.
5Draft Section LS32TOID 0004The initial draft RFP included a requirement to “Provide Knowledge Development Gap Analysis support of a new launch provider” under TOID 0004 2b. We suggest keeping this requirement.This requirement provides an opportunity for offerors to discuss how they will support RSLP in evaluating the state of new launch providers, assessing their current progress relative to SMC flight worthiness requirements, identifying potential risks, and the opportunity to support a more efficient process for ensuring these providers cost effectively meet the required Mission Assurance standard.RTOID 0004 remains unchanged.
6Draft Section LS32TOID 0004TOID 0004, paragraph 3.1 states:

Payload Customer: The payload for this Task Order will be multiple 3U and 6U CubeSat’s and 2-3 ESPA-class smallsats, all totaling less than 1,000 kg.

This conflicts with the STP-XS1 Mission Requirements Document, which lists the four SV Complements that are baseline on the four launches. Each of those has one ESPA-class SV in addition to cubesats, making a total of four ESPA-class smallsats to be launched under this TOID. Please clarify.

Clarification required M For clarity, TOID 004 paragraph 3.1 has been revised FROM: "Payload Customer: The payload for this Task Order will be multiple 3U and 6U CubeSat’s and 2-3 ESPA-class smallsats, all totaling less than 1,000 kg."

TO: " Payload Customer: The payload for this Task Order will be multiple 3U and 6U CubeSats and 4 ESPA-class smallsats. The total mass of this entire group of payloads is less than 1,000 kg."

7 Draft Section L S 34 TOID 0005 The initial draft RFP included a requirement to “The MAC shall provide Concept Analysis (IAW PWS paragraph 3.5) for this activity to identify lessons learned in the execution of the RSCD mission, with specific application to the mission assurance function for future rapid launch activities” under Tsk Order 0005 5.1.

We suggest keeping this requirement.

This requirement provides an opportunity for offers to discuss how they will implement a Lesson Learned program which can significantly vary between offer’s solutions and will likely become a more important risk mitigation portion of future Mission Assurance activities as new launch provides with alternative designs are brought in to the certification process. Identifying and capturing Lesson’s learned from these new providers will be essential in reducing the risk and developing a through understanding of these system as they begin to operate on a more regular schedule.RTOID 0005 remains unchanged.
8Draft Section LS44Appendix BWhich testing requires Motor Plugging/dissection before it can be accomplished? Is required before "Propellant Properties Test and Analysis" and "Propellant Hazards Sensitivity"?Additional information requiredMAdded the following note to table B-1: "Plugging/Dissection needs to occur prior to any property testing. Assume no previously-obtained samples are available."
9Draft Section LS44Appendix BAppendix B Table B-2 shows separate "GG" and "System" rows for both the "Thrust Vector Actuator/LITVC" and "Roll Control". What are the differences between these and which testing addresses each?Additional information requiredN/AMM Propulsion Handbook and SR19 manuals are found in the Bidders Library and describe the systems in detail.
10Draft Section LS134.2.5.5
Subpara 3The RFP asks the offeror to include three residual risks in the HVTI mission final briefing. Risk #3 concerns discrepancies in the structural integrity of the second stage oxidizer tank. TOID 0006 and the HVTI MRD describe the vehicle as a three stage Minuteman stack with an SR19 second stage, which is a solid propellant stage and thus has no oxidizer tank. Should we assume that the residual risk actually refers to the LITVC tank on that stage?Clarification requiredASection L paragraph 4.2.4.5.(3) has been changed to: "The third residual risk is for the results of a Mission Assurance Contractor-run Monte Carlo simulation for structural integrity of the second stage SR19 Liquid Injection Thrust Vector Control (LITVC) tank. MAC results don’t agree with the LSC’s analysis for the same component and indicate less margin."
11PWSS313.3.2.28.7Original: No content
Revised: Attend and provide technical support to the Mission Manager at post-flight review(s) held by LSC and other mission stakeholders.Is the intent to retain the content of 3.3.2.28.7 as was previously shown in 3.3.2.28.3? Or is this PWS requirement deleted?MSee CRM Question 4.
12Section LA134.2.4.4Original:….Ground Test Motor processing for the M55 and SR73 motors as described in PWS paragraphs 3.3.5.1, 3.3.5.14, 3.3.5.15, 3.3.5.18, 3.3.6.1, and 3.3.6.6.
Revised:….Ground Test Motor processing for the M55, SR19, and SR73 motors as described in PWS paragraphs 3.3.5.1, 3.3.5.14, 3.3.5.15, 3.3.5.18, 3.3.6.1, and 3.3.6.6.TOID 0006 now includes a SR19 GTM.ASection L paragraph 4.2.4.4 has been changed to now include reference to the SR19, as well as internally driven changes to the PWS paragraph references.

FROM: "Ground Test Motor processing for the M55 and SR73 motors as described in PWS paragraphs 3.3.5.1, 3.3.5.14, 3.3.5.15, 3.3.5.18, 3.3.6.1, and 3.3.6.6."

TO: "Ground Test Motor processing for the M55, SR19, and SR73 motors as described in PWS paragraphs 3.3.5.5, 3.3.5.13, 3.3.5.14, 3.3.5.15, 3.3.6.5, and 3.3.6.6."

13Section LC29Appendix A, TOID 0003, 2.0.C and 4TOID 0003, paragraph 2.0 c) states” Provide DXBM motor preparation support, test support, and final report for static fire testing of one each M55, SR19, M57, SR118, SR119, and SR120 DXBM motors” yet paragraph 4, Schedule identifies 2 each SR118 static fires. Do we price one or two SR118 static fires?The two paragraphs are conflicting. Need to resolve the difference.MThe second SR 118 static fire has been removed from the schedule. Offeror's should only price one(1) SR118 static fire.
14Section LS72.2Original: "Core Effort (TOID 001) - 8 pages. Revised: Core Effort (TOID 001) - 10 pagesThe addition of a "overarching program management approach" and additional PWS elements in Section L 4.2.3.1 increases the amount of content to be provided.ASect L Table 2 Core Effort page limit has been changed from 8 to 10. In addition, page limits for STP-XS1 Mission IV&V, RSCD Mission IV&V, and HVTI Mission IV&V have been changed from 5 to 10.
15PWSS22-263.3.2.16.5, 3.3.2.17.3, 3.3.2.19.x, 3.3.2.20.x, 3.3.2.21.x,The Government has made multiple changes to the PWS, both changing "models and analysis" to just "analysis" in PWS 3.3 Cat 2 and at the same time invoking CDRL B004 (requiring models delivery), which appears to be inconsistent.The change from references of "modelling" to "analysis" appears to require the renaming of certain sections as well as the invoked CDRLs. Where appropriate the Government should also consider CDRLs B002 and B003 for these sections instead.MThe title of paragraph 3.3.2.19.1 has been changed from Aerodynamic models" to "Aerodynamic analysis" CDRL B004 has been clarified to apply to analysis and to models if used to support the analysis.
16Section LS45Appendix B, Table B-2Table B-2, AS Data and Useful Life Estimates appears to be inconsistent. M55, Motor - Test Asset Current Age listed as 641 months. Per the instructions in Paragraph 'e', the ULE should be 677 months (641 +36). SR19AJ Motor - Test asset Current Age listed as 462 months. Per the instructions in Paragraph 'e', the ULE should be 498 months (462+36).For the two motor line items, request clarification on the ULE values.MTable B-2 provides information as of the date given. This date is not necessarily the same as the real-world last test data. To further clarify the table headings have been changed.

FROM: "Test Asset Current Age (months), ULE (months), ULE (years), Estimated ULE in FY25" TO: "Test Asset Age (months since manufacture) (as of 1 Nov 19), ULE (months since manufactuer), ULE (years since manufacture), ULE at ILC" 17 Section L S 16 5.3.3 This question pertains to the Question 28 previously submitted and considered by the government and is provided below.

Original: Provide direct and indirect costs to support fully burdened labor rates, for each labor category, for each year of the initial five-year ordering period (CY1-CY5) and each of the four option years, plus an additional two years to complete execution of all issued task orders, CY6, CY7, CY8, CY9, CY10, and CY11 using the format specified in Table D-1 in Appendix D, for the Prime Contractor as well as any teaming partners or applicable subcontractors.

Revised: Provide direct and indirect costs to support fully burdened labor rates, for each labor category, for each year of the initial five-year ordering period (CY1-CY5) and each of the four option years, plus an additional two years to complete execution of all issued task orders, CY6, CY7, CY8, CY9, CY10, and CY11 using the format specified in Table D-3 in Appendix D, for the Prime Contractor as well as any teaming partners or applicable subcontractors.

In response to this question, the government removed the requirement for Table D-3 as it was determined to be duplicative of Table D-2. This question was not intended to remove Table D-3, we were only suggesting that the reference to table D-1 in Section 5.3.3 should be to Table D-3 rather than Table D-1. If the original table D-3 is removed, it will be much more difficult for the Government to trace the direct and indirect costs that support the fully burdened labor rates provided in Table D-1. Table D-2 shows the aggregate indirect costs, not by labor category and may only reflect those categories being priced in the particular TOID, rather than the full range of labor categories proposed by the Offeror. We respectfully suggest leaving the original Table D-3 showing the labor rate buildup in the final RFP to allow the government to easily evaluate the full range of labor rates proposed. A “The government has reviewed the tables to be provided in Section L. After further review, Table D-3 has been added back into Appendix D and Total Proposed Price becomes Table D-4, as originally released in the DRFP. The reference to Table D-1 in 5.3.3 has been changed to Table D-3. Finally, the following language has been added to the end of 5.3.3 to account for Table D-1: "In addition, using Table D-1 in Appendix D (Table for Prime/Teaming Partners/Major Subcontractors Task Order Rates), please provide the total labor rate for each labor category provided in Table D-3, for each year of the initial five-year ordering period (CY1-CY5) and each of the four option years, plus an additional two years to complete execution of all issued task orders, CY6, CY7, CY8, CY9, CY10, and CY11. These rates will be incorporated into the resultant contract as Attachment 3."

It is also important to note that the rates should be provided for each Contract Year (CY). This has now been changed for Tables D-1 & D-3.”

18Section LS165.3.3Original: Provide direct and indirect costs to support fully burdened labor rates (less target or fixed fee and COM), for each labor category, for each year of the initial five-year ordering period (CY1-CY5) and each of the four option years, plus an additional two years to complete execution of all issued task orders, CY6, CY7, CY8, CY9, CY10, and CY11 using the format specified in Table D-1 in Appendix D, for the Prime Contractor as well as any teaming partners or applicable subcontractors expected to be regularly included as labor on task order cost proposals.For the prime contractor submission, please clarify whether the rates for the teaming partners/subcontractors provided in Table D-1 should include the applicable prime contractor burdens. We recommend that the teaming partner/subcontractor rates in the prime contractor submission of Table D-1 should NOT include applicable prime contractor burdens to allow for better traceability to the subcontractor submissions.APrimes should NOT include applicable prime contractor burdens to allow for better tracebility to the teaming partner/major subcontractor submissions. The following asterisk is now included under Tables D-1 and D-3: "***Rates should not include Prime Fee, nor should rates include applicable Prime Burdens on Teaming Partners/Major Subcontractor Rates. Teaming Partners/Major Subcontractor rates may include Teaming Partners/Subcontractor Fee & COM.***" For Table D-1, "Please identify the Teaming Partners/Major Subcontractor rates that Primes intend to additionally burden in response to Task Order RFPs."
19Section LA165.3.3Original: Provide direct and indirect costs to support fully burdened labor rates (less target or fixed fee and COM), for each labor category, for each year of the initial five-year ordering period (CY1-CY5) and each of the four option years, plus an additional two years to complete execution of all issued task orders, CY6, CY7, CY8, CY9, CY10, and CY11 using the format specified in Table D-1 in Appendix D, for the Prime Contractor as well as any teaming partners or applicable subcontractors expected to be regularly included as labor on task order cost proposals.For those teaming partners/subcontractors that are proposed on a FFP or T&M basis, should the rates shown in Table D-1 include their fee and COM? As fee/profit is not identified separately when proposing T&M/FFP rates, we suggest that the rates provided in Table D-1 for any T&M/FFP teaming partner/subcontractorinclude both fee/profit and COM, with appropriate modifications made to the column headings.AWe understand that in some circumstances, teaming partners/major subcontractors will include fee/profit and COM within their Fixed Price rates provided to the prime. If this is the case, the government does not require the subcontractor to break out fee/profit and COM for their submissions to Table D-1. There is now an asterisk underneath Table D-1 denoting this: "***Rates should not include Prime Fee, nor should rates include applicable Prime Burdens on Teaming Partners/Major Subcontractor Rates. Teaming Partners/Major Subcontractor rates may include Teaming Partners/Subcontractor Fee & COM. Please identify the Teaming Partners/Major Subcontractor rates that Primes intend to additionally burden in response to Task Order RFPs.***"
20Section LS165.3.3Original: Provide direct and indirect costs to support fully burdened labor rates (less target or fixed fee and COM), for each labor category, for each year of the initial five-year ordering period (CY1-CY5) and each of the four option years, plus an additional two years to complete execution of all issued task orders, CY6, CY7, CY8, CY9, CY10, and CY11 using the format specified in Table D-1 in Appendix D, for the Prime Contractor as well as any teaming partners or applicable subcontractors expected to be regularly included as labor on task order cost proposals.Are teaming partners/subcontractors proposed on a T&M or FFP basis required to provide the direct labor rate buildup showing both direct and indirect costs or should they only show the fully burdened rate?ANow that Table D-3 has been added back into Section L, the Teaming Partners/Major Subcontractors may send their cost buildups to the PCO directly by email by the proposal due date. We understand that in some circumstances, teaming partners/major subcontractors will include fee/profit and COM within their Fixed Price rates provided to the prime. If this is the case, the government does not require the subcontractor to break out fee/profit and COM for their submissions to Table D-3, but please identify this somewhere within the cost proposal.
21Section LS82.2.2.3Original: "For tables, charts, graphs and figures, the text shall be no smaller than 12 point.”Please clarify the applicability of this paragraph. Does it apply to both "pages" and "slides" as defined in the previous paragraphs.AThis paragraph does apply to both pages and slides. Paragraph 2.2.2.3 has been modified

FROM: "For tables, charts, graphs and figures, the text shall be no smaller than 12 point.”

TO: "For tables, charts, graphs and figures, (in both pages and slides) the text shall be no smaller than 12 point.”

22 Bidders Library: Mission Managers Handbook S N/A General The Mission Managers Handbook (MMH), lays out generic mission flow, various reviews, IPTs, WG, etc. Is significant MAC involvement is in FRR required (since not mentioned in RFP)? Also, how important is IRR to the government? Requirements clarification N/A The MAC's involvement with FRR is discussed in PWS paragraph 3.3.2.16 Space Flight Worthiness Certification, which states, "Review the LSC's SFWC assessment (when applicable) and assist the Mission Manager in SFWC checklist completion in preparation for the FRR. At the FRR, the MAC will present an independent assessment of residual mission risks. The MAC will also provide a letter to the SMC/CC certifying their performance of independent verification and validation efforts to the SMC/CC in support of the FRR. (CDRLs B002, B005)"

An Internal Readiness Review (IRR) is not a requirement under this RFP.

23Section L: Appendix A (TOID 6)S40GeneralFor TOID 6 (the Hypersonic Mission), the PoP is 51 months. This seems to be very long, what is driving this PoP?Requirements clarificationN/AThe PoP is driven by payload availability. There are no requirements or restrictions related to the launch vehicle that drive this timeline.
24Bidders LibrarySN/AGeneralOne of the docs in bidders library calls out a Systems Engineering Functional Team, hoping for some clarification on who is on it and is it synonymous with any IPT?Requirements clarificationN/AThe Systems Engineering Functional Team (SEFT) is led by the RSLP Chief Engineer and supported by another contractor. The purpose of this team is to create and manage RSLP command media and other engineering support. The SEFT is not synonymous with any IPT.
25PWSSN/AGeneralIn general and consistent with the mission TOIDs in the RFP, the MAC POP starts before LSC contract award. Does the MAC have any involvement with developing the Mission Requirements Documents (MRD) or assisting in the source selection of a Launch Services Contractor? If so, where is this captured in the PWS?Requirements clarificationN/APWS Paragraph 3.2.4 Planning Support, requires the MAC to "Provide management, engineering, and Subject Matter Expert (reach-back) support to RSLP planning activities related to the determination of feasibility, requirements, early integration or other support necessary for RSLP to execute planning activities related to new or modified work."

MRD development would be part of support to RSLP planning activities.

Contractor participation in LSC task order competitions would be required only if the Gov't could not otherwise obtain specific subject matter expertise and if approved by SMC.

26 Section L A 6 2.2 The Offeror shall submit all volumes in hard copy (physical printed paper) as well as electronic format. Only one hard copy of the proposal shall be submitted. Does the Government anticipate the requirements changing to just electronic format requirement in Final RFP because of COVID-19? Possible requirement change A In light of Kirtland AFB being mandated that all non-mission-essential personnel telework, the Government is not requiring hard copies of the proposal at this time, as those copies may not be received. A hard copy may be requested at a later date. If a hard copy is requested, the request will only be made prior to the proposal submission date and will be made to offerors at least 10 calendar days in advance of the required delivery date. If the proposal due date has passed, the government will not be requiring a hard copy submittal. As a result, changes have been made to paragraphs 2.2, 2.2.8, and 2.3 of Section L to reflect that, at this time, only electronic proposal submissions shall be made by the proposal due date.

&D &F Page &P of &N image1.png

File details come from the government source that posted it. Updated .