HC104719R0007A12.pdf
PDF 338 KB Posted
- Solicitation number
- HC1047-19-R-0007
- Issued by
-
Defense Information Systems Agency
About this file
This request for proposal solicits a single-award indefinite delivery/indefinite quantity contract for Command and Control Portfolio Systems Engineering support services. The Defense Information Systems Agency intends to issue the solicitation with an estimated release date in the mid to late third quarter of fiscal year 2019. The resultant contract would have a five-year ordering period to provide support through task orders ending no later than two years after the close of the ordering period. Task orders may include fixed price and cost reimbursement contract line items. Services include systems engineering, architecture and design, configuration management, cybersecurity, laboratory administration, research and development experimentation, process improvement, and capability planning support. The response due date is anticipated to be in the fourth quarter of fiscal year 2019.
View the file
Other files
Show all 28
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83)
Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of this Amendment 12 is to:
1. Answ er Vendor Q&A, see red font.
2. Revise RFP Section L.9.2.3, see red font.
3. Extend the RFP Due date to October 30, 2019 at 10AM EST.
1. CONTRACT ID CODE PAGE OF PAGES
S 1 15
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 24-Oct-2019
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X
HC104719R0007
X
9B. DATED (SEE ITEM 11)
27-Aug-2019
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
24-Oct-2019
CODE
DEFENSE INFORMATION SYSTEMS AGENCY
P.O. BOX 549
FT. MEADE MD 20755
HC1047 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
HC104719R0007
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
SECTION L INSTRUCTIONS
INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS
Attachments relevant to Section L are listed in Section J and are identified as LX where X is the number of the attachment.
L.1. INFORMATION TO OFFERORS
L.1.1. Contract Information. For consideration in developing your proposal, the following information is provided.
This Request for Proposal (RFP) solicits for a single award Indefinite Delivery/Indefinite Quantity (IDIQ) contract through a total Small Business set-aside, utilizing a best-value trade-off evaluation method. The first task order is being solicited in conjunction with this RFP. Future task orders will be issued using FAR Part 16.505.
L.2. General Instructions.
L.2.1. This section of the Information to Offerors provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. The offer shall address all requirements as stated in the Performance Work Statement (PWS). Non-conformance with the instructions provided in this Information to Offerors may result in removal of the proposal from further evaluation.
L.2.2. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their capabilities and experience and will base its evaluation on the information presented in the offeror's proposal.
L.2.3. Within 10 calendar days of the posting of the solicitation, offerors shall indicate their intent to propose as a prime contractor to the email address cited in Section L.3.1.
L.2.4. Elaborate brochures or documentation, binding, detailed art work, internet hyperlinks, or other embellishments are unnecessary and are not desired.
L.2.5. The offeror shall make a clear statement in Volume I cover page that the proposal is valid for a minimum of 180 calendar days from the proposal due date.
L.2.6. In accordance with (IAW) FAR Subpart 4.8 (Government Contract Files), the Government will retain one digital copy of all unsuccessful proposals.
L.2.7. Portions of the successful offeror’s proposal may be incorporated into the contract as an attachment in
Section J.
L.3. General Information.
L.3.1. Point of Contact. The contracting officer (KO) and the contract specialist (CS) are the sole points of contact for this procurement. Address any questions or concerns to the KO and CS. Written requests for clarification must be sent to the KO and CS at the following email address, disa.meade.PLD.mbx.qas62-acquisition@mail.mil, and must contain the solicitation number in the subject line. Oral communications are not permissible.
L.3.2. Debriefings. The KO will notify unsuccessful offerors of the source selection decision in accordance with
FAR 15.503. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.
Excluded offerors are only entitled to one debriefing for each proposal.
L.3.2.1. If a competitive range is established, the KO will notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The KO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.
L.3.3. Discrepancies. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the KO in writing with supporting rationale.
L.3.4. Electronic Reference Documents. All referenced documents for this solicitation are available on the
Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. The Government will communicate all formal information regarding this solicitation via the
FedBizOpps website. This is the only mechanism by which offerors will have access to this solicitation documentation released by the Government. Any and all technical, connectivity, or other access-related issues
(electronic or physical) regarding FedBizOpps must be directed to the FedBizOpps systems administrators, Federal
Service Desk (FSD) by phone at 1-866-606-8220. The Contracting Officer for this solicitation has no influence over
FedBizOpps regulations, policy and protocol. Furthermore, the Government is not responsible for the accuracy of any information related to this acquisition posted to third-party websites.
L.3.5. Communications. The KO or CS will control exchanges of source selection information between
Government and offerors. Evaluation notices and responses will be transmitted as emails and will be treated as source selection information. The subject line of the email will be titled: “RFP HC1047-19-R-0007, Contractor
Name, Source Selection Information See FAR 2.101 and 3.104.” Exchanges shall be sent to the following email address, disa.meade.PLD.mbx.qas62-acquisition@mail.mil.
L.3.6. Award without Discussions. The Government reserves the right to award this effort based on the initial proposal, as received, without discussion, therefore, the offeror’s initial proposal should contain the offeror’s best terms from a price and technical standpoint. However, the Government may conduct discussions if the Source
Selection Authority (SSA) determines they are necessary. If the SSA determines that discussions are necessary, a competitive range will be established. In the event issues pertaining to a proposed contract cannot be resolved to the
SSA's satisfaction, the Government reserves the right to withdraw and cancel the solicitation. In such event, offerors will be notified in writing.
L.3.6.1. In the event a competitive range is established, and the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition. In accordance with FAR Part 15.306(c) (2), Offerors are advised that the competitive range may be further reduced for purposes of efficiency.
mailto:disa.meade.PLD.mbx.qas62-acquisition@mail.mil mailto:disa.meade.PLD.mbx.qas62-acquisition@mail.mil http://www.fedbizopps.gov/ mailto:disa.meade.PLD.mbx.qas62-acquisition@mail.mil
L.3.7. Organizational and Consultant Conflict of Interest (OCCI). Each offeror shall specifically identify in its proposal whether or not any potential or actual OCCI, as described in Federal Acquisition Regulation (FAR)
Subpart 9.5, exists for this procurement. If the offeror believes that no OCCI exists, the OCCI response shall set forth sufficient details to support such a position. If an offeror believes that an actual or perceived OCCI does exist on this procurement, the offeror shall submit an OCCI plan with the proposal, explaining in detail how the OCCI will be mitigated and/or avoided. If submitted, the OCCI plan shall be included in Volume VI.
L.3.8. DD Form 254, DoD Contract Security Classification Specification. Offerors must complete Block 6 of the DD254 provided in Section J, Attachment C3, with the appropriate information for their companies. Completed
DD254’s must be submitted with proposals and shall be included in Volume VI. Security classification requirements must be met at time of proposal submission.
L.3.9. Joint Venture/Partnership Agreement (if applicable). Contractor Team Arrangements (“CTA”), as defined in FAR 9.601(1), may submit a proposal in response to this RFP. While the CTA is its own unique entity distinct from the member companies, for the purpose of evaluation, each member of the CTA is considered the prime offeror.
For example purposes only: Company A and Company B form a CTA as a Joint Venture named Company C.
Experience and past performance from either Company A or Company B may be used to satisfy the requirements in the Technical/Management Approach (Evaluation Factor 1), Experience (Factor 2), and/or Past Performance (Factor
3). It is not necessary that Company C have the required experience or past performance. Similarly, either
Company A or Company B can possess the required certifications outlined in the PWS.
An unpopulated Joint Venture cannot receive a facility clearance as there are no personnel attached to the Joint
Venture through which the facility clearance can be awarded. This contract requires possession of a Secret Facility
Clearance in accordance with Section C.11.1 of the IDIQ PWS. The clearance must be possessed at the time of proposal submission.
An offeror may submit a proposal as a CTA in response to the solicitation subject to the following conditions:
The Joint Venture or Partnership is registered in the System of Award Management (SAM.gov) and has a corresponding DUNS Number.
The Joint Venture or Partnership meets the definition of a Joint Venture for size determination purposes (FAR
19.101(7)(i)).
The offeror must submit a complete copy of the Joint Venture or Partnership agreement that established the
CTA relationship.
L.4. Organization/Number of Copies/Page Limits.
L.4.1. Proposal Organization. The offeror shall prepare the proposal as set forth in the Proposal Organization
Table (Table L1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits as specified in Table L1. The contents of each proposal volume are described in the information to offerors paragraph as noted in the table below.
Table L1 – Proposal Organization.
VOLUME
RFP Paragraph
Number VOLUME TITLE PAGE LIMIT
I L.5 Executive Summary
Part A L.5.1 Narrative Summary 3 pages
Part B L.5.2 Table of Contents No Limit
Part C L.5.3 Glossary/Acronym List No Limit
Part D L.4.5.1 Cross-Reference Matrix No Limit
II L.6 Technical/Management Volume
Part A L.6.2.2.1 Table of Contents No Limit
Part B L.6.2.2.2 List of Tables and Drawings No Limit
Part C L.6.2.2.3 Technical Approach 30 pages
Part D L.6.2.2.4 Management Approach 5 pages
III L.7 Experience
Part A L.7.2 Subfactor 1 - Systems Engineering 3 pages per example
Part B L.7.3 Subfactor 2 - Cybersecurity 3 pages per example
Part C L.7.4 Subfactor 3 - Laboratory and Systems Administration 3 pages per example
IV L.8 Past Performance
Part A L.8.4.1 Past and Present Performance Reference Sheets 3 pages per effort
Part B L.8.4.2 Past Performance Questionnaires
4 pages per cover letter and questionnaire
Part C L.8.4.3 Consent Letters 1 page per letter
V L.9 Cost/Price
Part A L.9.2.1 Introduction 2 pages
Part B L.9.2.2 Cost/Price Narrative No Limit
Part C L.9.2.3 Cost/Price Summary Spreadsheet No Limit
VI L.10 Contract Documentation No Limit
L.4.2. Page Limitations. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation
Notices (ENs). The specified page limits for EN responses, if applicable, will be identified in the letters forwarding the ENs to the offerors. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered part of the proposal. Each page shall be counted except cover pages, tables of contents, glossaries, OCCI mitigation plans, SCRM plans, Section 508 compliance, blank pages, or those identified in Table L1, Proposal Organization, as having no limit.
L.4.3. Page Size and Format.
L.4.3.1. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts.
Pages shall be single spaced with space between paragraphs. Except for the reproduced sections of the solicitation document, the text size shall be no less than 11 point Arial or Times New Roman font for all text. The technical volume of the proposal shall be submitted as an MSWord 2007 or newer file or an Adobe PDF document. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals. It is the sole responsibility of the Offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. Proposal submissions shall not be locked, encrypted, or otherwise contain barriers to opening. The Government is under no obligation to seek clarification regarding electronic proposal submissions if submissions cannot be opened or accessed.
L.4.3.2. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. For tables, charts, graphs and figures, the text shall be no smaller than 10-point Ariel, Times New Roman, or Courier New font for all text included in a table.
L.4.4. Cost or Pricing Information. All cost or pricing information shall be addressed ONLY in the Cost/Price
Proposal Volumes. Cost trade-off information, work-hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.
L.4.5. Cross-Referencing. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal.
Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.
L.4.5.1. Cross-Reference Matrix. The offeror shall prepare a Cross Reference Matrix cross referencing all RFP requirements to the location of the offeror’s responses in their proposal. The Cross Reference Matrix provides reference information but is not evaluated. The offeror’s format is acceptable.
L.4.6. Indexing. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.
L.4.7. Labeling. Each volume of the proposal should be separately labeled. A cover sheet should be provided in each volume, clearly marked as to the volume number, title, copy number, solicitation identification, and the offeror’s name. The Contractor shall apply all appropriate markings including those prescribed in accordance with
FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection
Information.
L.4.8. Glossary of Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each.
L.4.9. Questions. Questions/comments regarding this RFP shall be submitted using the blank Questions and
Responses template, Attachment L1. Questions/comments will only be responded to if received via email (subject line: “Questions HC1047-19-R-0007”) and only when submitted on Attachment L1. The questions shall be addressed to the KO and CS at the following email address, disa.meade.PLD.mbx.qas62-acquisition@mail.mil.
Questions/comments regarding this RFP are due no later than 14:00 (ET) on Sep 4, 2019. Questions submitted after the deadline may not be answered. The timeframe for submitting inquiries will not be extended as a result of an extension to the due date for the receipt of offers unless authorized by the KO. All questions and answers will be published to the FedBizOpps portal once addressed.
L.4.10. Electronic Offers. In order to respond to this solicitation, the offeror shall email a copy of its proposal to the KO and CS not later than the time and date specified in this solicitation. The maximum size of each email transmission to the Contracting Officer and Contract Specialist shall not exceed 20 MBs. In accordance with FAR
52.215-1, Instructions to Offerors, the offeror's proposal submission will be considered complete when all volumes are received.
L.4.10.1. All proposal volumes shall be submitted in Adobe Acrobat, Portable Document Format (Adobe PDF), Version XI; or Microsoft (MS) Office Word 2007 or newer; except the Pricing Proposal, which shall be submitted in
MS Excel 2007 or newer. Note: There shall be no page markings with restrictive legend prohibiting the copying and pasting of text for Government use specific to this acquisition.
L.4.10.2. Submit each volume as a separate electronic .zip file with the name of the volume from the table L1. Each individual file within the .zip file must be autonomous and complete.
L.4.10.3. Virus Check. Offerors shall perform a virus check prior to proposal submittal and certify they have done so in the proposal’s Cover Pages.
L.4.10.4. Use of the software and procedures described in this part will reduce the amount of time and effort needed by the Government to receive and install proposals into an electronic evaluation system and will help to ensure that proposals are suitable for reading electronically. Information regarding electronic products listed herein should not be construed as Government endorsement for such products.
L.4.10.5. Due Date/Time. The time specified on the SF-33, Block 9, is in Eastern Time (ET). Any proposal, modification, or revision that is received after the exact time specified for receipt of proposals in Block 9 is “late” and will be handled in accordance with FAR 15.208(b) and subparagraphs thereto.
L.4.10.6. The offeror’s proposal submission will be considered complete when all volumes have been received.
L.4.10.7. Efforts by the Government to clarify or expedite installation of electronic proposal submissions, in accordance with FAR 15.207(c), will not be considered discussions.
L.4.11. Distribution. Proposals shall be addressed to the KO and CS at the following email address, disa.meade.PLD.mbx.qas62-acquisition@mail.mil. The subject line of the email shall include the RFP number.
L.5. Volume I – Executive Summary. In the executive summary volume, the offeror shall provide the following information:
L.5.1. Narrative Summary. The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.
L.5.2. Table of Contents. Include a master table of contents of the entire proposal.
L.5.3. Glossary. Include a master glossary/acronym list defining all acronyms utilized throughout the proposal.
L.6. Volume II – Technical/Management Volume (IDIQ and Task Order 1).
L.6.1. General. The Technical/Management Volume should be specific and complete. Responses will be evaluated against the technical/management subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology to be used for accomplishing/satisfying these subfactors. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.
L.6.2. Format and Specific Content.
L.6.2.1. Technical/Management. In the Technical/Management volume, address the proposed approach to meeting or exceeding the minimum performance or capability requirements of each technical/management subfactor, as well as the risks in the proposed approach in terms of technical/performance, cost, and/or schedule. The offeror shall include in this technical/management proposal the technical/management approach for the IDIQ contract, as well as
Task Order 1. The proposal for Task Order 1 will be evaluated in conjunction with the IDIQ proposal for the purpose of making best value determination. The Government intends to award Task Order 1 at the same time as the issuance of the IDIQ. The PWS for Task Order 1 is provided as Attachment L2.
L.6.2.2. Volume Organization. The Technical/Management volume shall be organized according to the following general outline:
Part A Table of Contents
Part B List of Tables and Drawings
Part C Technical Approach (IDIQ and Task Order 1)
Part D Management Approach (IDIQ and Task Order 1)
L.6.2.2.1. Part A – Table of Contents. Submit a Table of Contents for Volume II.
L.6.2.2.2. Part B – List of Tables and Drawings. Include a list of the Tables and Drawings utilized throughout
Volume II.
L.6.2.2.3. Part C – Technical Approach. The offeror’s Technical Capabilities proposal should describe their capabilities to execute all tasks specified in Section 6 of the IDIQ and Task Order 1 PWS. It should clearly describe their approach to fully meet or exceed the requirements of the IDIQ and Task Order 1 PWS. This subfactor should also describe where the offeror sees risk and how they would solve, mitigate or reduce risks. Proposals should clearly show how the offeror will accomplish the tasks and why they have chosen that particular course.
L.6.2.2.3.1. Subfactor 1 – Technical Approach to Systems Engineering Support. The offeror shall submit a proposal that demonstrates their approach to executing Section C.6.2 of the IDIQ PWS. The offeror shall propose system engineering support for C2 policies, processes, procedures, and reporting structures needed to plan, execute mobilize, deploy, employ, sustain, redeploy, and demobilize activities associated with Joint Operations. Proposals shall clearly describe their capabilities, and their solution/approach, including any software they plan to utilize, in order to fully meet or exceed the performance requirements of Section C.6.2 of the IDIQ PWS.
L.6.2.2.3.2. Subfactor 2 – Technical Approach to C2 Laboratory and Systems Administration Support. The offeror shall submit a proposal that demonstrates their approach to executing Section C.6.6 in the IDIQ PWS and
Section C.6.2 in the attached Task Order PWS. Proposals shall clearly describe the offeror’s capabilities and the proposed solution/approach, including any software they plan to utilize, in order to fully meet or exceed the performance requirements of Section C.6.6 in the IDIQ PWS and Section C.6.2 in the Task Order PWS.
L.6.2.2.3.3. Subfactor 3 – Technical Approach to Cybersecurity Support. The offeror shall submit a proposal that demonstrates their approach to executing Section C.6.5 in the IDIQ PWS and Section C.6.4 3 of the attached
Task Order PWS. Proposals shall clearly describe the offeror’s capabilities and the proposed solution/approach, including any software they plan to utilize, in order to fully meet or exceed the performance requirements of Section
C.6.5 in the IDIQ PWS and Section C.6.4 3 of the attached Task Order PWS.
L.6.2.2.4. Part D – Management Approach.
L.6.2.2.4.1. Subfactor 4 – Management/Staffing Approach for First Task Order. The offeror’s management approach shall address how the contractor will track and manage resources to support the efforts outlined in the attached Task Order PWS, Section C.6. The offeror shall provide a matrix showing the mix of labor categories, and the labor hours for each labor category, to meet or exceed the requirements described in Section C.6 of the attached
Task Order PWS. The offeror’s management approach shall describe workload assumptions made, how the proposed mix of labor categories and labor hours will be utilized to meet or exceed the requirements described in
Section C.6 of the Task Order PWS, and the anticipated level of risk.
L.7. Volume III – Experience.
L.7.1. General. The offeror shall provide examples of experience performed by the proposing company, not individuals, under a contract or a subcontract. Only examples demonstrating support of Government C2 systems will be considered as examples of experience. Private sector contracts will not be considered as examples of experience.
The examples provided must include the relevant contract/subcontract number or order number, point of contact, program(s) supported, classified/unclassified network requirements, and references to corresponding sections of the
IDIQ PWS and Task Order PWS where applicable.
Offerors shall submit no more than eight (8) total examples of experience for evaluation, and examples of experience shall not exceed three (3) pages. Offerors are advised that the Government will use data provided by each offeror in this volume and may use data obtained from other sources in the evaluation of experience.
If the offeror’s experience is through a subcontracting, teaming, joint venture arrangement, or other entity, the offeror must be specific as to what tasks were accomplished by the other entity and the nature of the organizational relationship with the offeror.
Offerors are not permitted to propose the corporate experience of subcontractors or teammates.
Experience is defined as those contracts presently being performed by the offeror, or which have been performed by the offeror in the past, that the offeror chooses for evaluation by the Government, without limitation of the dates of performance.
The following Experience Subfactors are of equal importance.
L.7.2. Part A – Subfactor 1 – Systems Engineering. The Offeror shall provide examples of demonstrated experience corresponding to IDIQ PWS Task C.6.2, Systems Engineering Support.
L.7.3. Part B – Subfactor 2 – Laboratory and Systems Administration. The Offeror shall provide examples of demonstrated experience corresponding to IDIQ PWS Task C.6.6, Laboratory and Systems Engineering Support.
L.7.4. Part C – Subfactor 3 – Cybersecurity. The Offeror shall provide examples of demonstrated experience corresponding to IDIQ PWS Task C.6.5, Cybersecurity Support.
L.8. Volume IV – Past Performance.
L.8.1. General. Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment L3, Past and Present Performance
References. Offerors shall submit no more than three (3) total recent past/present performance efforts for evaluation, and each cited past performance shall not exceed three (3) pages. Offerors are advised that the
Government will use data provided by each offeror in this volume and may use data obtained from other sources in the evaluation of past performance.
L.8.2. Recent Contracts. Recent efforts are those that have been performed during any portion of the last three
(3) years from date of issuance of this RFP, including those efforts currently being performed. For those efforts currently being performed, the offeror must have been performing for at least six (6) months from the date of issuance of this RFP. Past performance information that fails this condition will not be further evaluated.
L.8.3. Relevant Contracts. Include rationale supporting the assertion of relevance in relation to the technical/management subfactors.
L.8.4. Specific Content. Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a limited or no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. Categorize the relevant information into the specific technical/management subfactors used to evaluate the proposal.
L.8.4.1. Part A - Past and Present Performance Reference Sheets. Information on up to two (2) recent contracts performed by an Offeror’s significant teaming partners/subcontractors and significant subcontractors considered most relevant in demonstrating their ability to perform the proposed effort may be submitted. The Government considers a significant subcontractor and/or teaming partner to be a company who provides 20% or more of the support required, and/or company who provides a critical portion of the effort required and/or influences the results of performance. The maximum number of past performance efforts submitted by the prime Offeror and its teaming partners may not exceed three (3) total. Therefore, if two (2) subcontractor efforts are submitted, then maximum number of efforts submitted by the prime would be one (1) effort.
Note: Individual task orders or call orders under an IDIQ contract, GSA Schedule contract, or Blanket Purchase
Agreement (BPA) are each considered to be one past/present performance effort. IDIQ contracts, GSA Schedule contracts, or BPAs submitted as references without an associated task order, or with multiple task/call orders, will not be considered in the past performance evaluation.
L.8.4.2. Part B – Past Performance Questionnaires. The Offeror shall provide the Past Performance
Questionnaire and Cover Letter, Attachment L4, to each of the customer Points of Contact identified for each of the relevant past performance efforts. In order to expedite the assessment process, the Offeror may complete Sections 1, 2, and 3 of the Past Performance Questionnaire for the convenience of the Points of Contact. The Offeror shall not, however, complete any other section of the Past Performance Questionnaire. Once the questionnaires are completed by the POCs, the information contained therein shall be considered Source Selection Information in accordance with
FAR 2.101 and 3.104 and shall not be released to the Offeror. Past Performance Questionnaires submitted for any
Offeror’s team member shall clearly indicate the name of the Offeror within the questionnaire. Early submission of the Past Performance Questionnaires is encouraged. Questionnaires shall be sent directly via email to the KO and
CS at the following email address, disa.meade.PLD.mbx.qas62-acquisition@mail.mil, no later than the proposal due time and date from the customer filling out the form. However, offerors should provide a copy of the sent questionnaires with their proposal.
L.8.4.3. Part C – Consent Letters. The offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of past performance information to the offeror so the offeror can respond to such information. Consent letters should not exceed more than one page. The consent letter template is included as Attachment L5.
L.8.5. Organizational Structure Change History. Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this procurement. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes affect the relevance of any efforts identified for past performance evaluation/confidence assessment.
Since the Government intends to consider past performance information provided by other sources as well as that provided by the offerors, the "roadmap" should be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.
L.9. Volume V – Cost/Price.
L.9.1. General Instructions.
L.9.1.1. Cost/Price Reasonableness, Realism, and Completeness. The Government will verify that all solicitation requirements have been priced, figures are correctly calculated, and prices are presented in a clear and useful format.
Note that unrealistically low or high proposed costs, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Additionally, unbalanced cost/pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Cost/price submissions should be sufficiently detailed to demonstrate their reasonableness and be adequate enough to support and sustain a DCAA audit.
L.9.1.2. Price Information. Pricing submitted for the first task order’s base period and all option periods, including option pricing for an additional six-month period that may be authorized IAW FAR 52.217-8, Option to Extend
Services, and surge pricing if requested in Section M will be evaluated. See FAR 52.217-8 which authorizes the
Government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal should include separate line items by CLIN for the additional six-month period IAW
FAR 52.217-8. These prices shall be identical to the proposed pricing in the six months prior to expiration of the base period, or the final option period, if option periods are present. The total evaluated price will consist of the proposed price for the base period, all option periods, and the option pricing for the additional 6-month period, inclusive of Surge pricing. Pricing will be incorporated into Schedule B and related B-Tables upon contract award and used for all fixed-price orders placed post-contract award.
Should the Government determine the need to perform cost analysis, the Government may require additional other than certified cost or pricing data to include: direct labor rates, indirect rates including fringe, overhead, G&A, and any other indirect rates applicable to offeror’s standard business practices or, if applicable, CAS. Offeror shall ensure that all cost elements included in the total price of individual line items are provided in sufficient detail to allow the government to evaluate the reasonableness and, as applicable, realism. All formulas by which individual cost elements and line items sum to subtotals or total prices shall remain intact in offeror’s Excel workbook.
Submission of a hard numbered workbook may result in the offeror’s cost and price submission being determined defective and eliminated from further consideration.
L.9.1.3. Estimating Techniques and Methods. When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships, commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the Work Breakdown Structure (WBS).
L.9.1.4. Cost/Price Information. Information beyond that required by this instruction shall not be submitted, unless considered essential to document or support the cost/price position. All information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.
L.9.1.5. Cost or Pricing Information and Requirements. In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support price or cost reasonableness and, if applicable, cost realism. Information shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the KO determines the required conditions of adequate competition do not exist that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror may be required to certify its submitted cost or pricing data (see: FAR 15.406-2 -- Certificate of Current
Cost or Pricing Data).
L.9.2. Volume Organization. The Cost/Price volume shall consist of the following sections:
L.9.2.1. Part A – Introduction. The offeror shall provide a table of Contents; Summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, accounting practices, or Cost Accounting Standards
(CAS) Disclosure Statement.
L.9.2.2. Part B – Cost/Price Narrative. Offerors and any subcontractor(s) shall provide whatever information is necessary to help the Government understand why the proposed costs are reasonable and realistic in the Cost/Price
Narrative. Each Offeror's cost proposal shall contain sufficient quantitative and narrative documentation necessary to adequately support and explain the costs proposed, to include subcontractor proposed costs. The offeror shall describe their methodology used to establish their price. The Offeror shall provide information describing and detailing the evaluation it performed to determine the reasonableness of subcontractor prices on hourly labor rates.
The prime contractor shall specify what type of contract (firm-fixed-price, cost-reimbursement etc.) is proposed for each subcontractor. For any subcontractor proposed at or above the Truth In Negotiations Act (TINA) threshold, the
Offeror shall provide, or instruct the subcontractor to provide evidence of accounting system adequacy if the subcontractor is performing on any basis other than Firm Fixed Price (FFP) or Time and Materials (T&M).
Offerors and any subcontractor(s) shall be responsible for ensuring compliance with the Service Contract Act (SCA) for all applicable labor categories. If offerors believe that labor categories are subject to the SCA, they shall identify such labor categories as “SCA Labor” on their proposal. Offerors shall also disclose the state and county in which the proposed SCA labor categories will be performing its effort, the Wage Determination Schedule used for its proposed SCA labor rates, and the Occupation Code and Title for each proposed SCA labor category.
In support of proposed direct labor and indirect expense rates, offerors and any subcontractor(s) shall provide documentation to include at least one of the following: 1) a copy of the most recent Forward Pricing Rate
Agreement (FPRA), 2) Forward Pricing Rate Recommendation (FPRR), 3) a DCAA or DCMA report or memorandum containing the most recent finalized DCAA/DCMA audit or review, or 4) Forward Pricing Rate
Proposal (FPRP) or other statement of current rates to include documentation to validate the proposed direct labor rates and indirect expense rates.
L.9.2.3. Part C – Cost/Price Summary Spreadsheet. Offerors may modify the Cost and Pricing Template in accordance with their disclosed business practices and/or CAS. An offeror may substitute a proprietary excel workbook; offeros must ensure that the submission provides at least the same level of detail as the Government-provided Template Microsoft Excel Workbook, Attachment L6. Offerors are required to use the Government-provided Microsoft Excel Workbooks to submit the cost and pricing data supporting its proposed price, Attachment
L6.
Each offeror's and subcontractor’s cost proposal shall be broken out by cost element as specified in FAR 15.408, Table 15-2, and in further supporting detail as shown in the Government Provided Pricing Template. The Prime
Contractor and each subcontractor’s Cost Proposal shall be submitted in Excel format (.xlsx) with all formulas visible in each cell with a value. Do not submit hard numbers. If an offer submits hard numbers it may be found non-responsive and may not be eligible for award. If a subcontractor’s cost data is proprietary, the subcontractor may submit its data directly to the Government in the same format that is required of the Prime contractor.
Descriptions of the Labor Categories are provided in Attachment C1. The offeror shall input direct labor rates and indirect rates to include profit/fee. Indirect rates will be in accordance with Cost Accounting Standards. Rates will be calculated for both Government-site and Contractor-site personnel. Offerors will insert rates into the Government provided Excel Workbook to calculate it’s proposed fully burdened labor rate for each labor category. Offerors shall apply their indirect rates in accordance with its Cost Accounting Disclosure Statement. DO NOT place hard coded numbers in the spreadsheet to calculate the fully burdened labor rates. See the “Instructions” tab in the Government provided Excel Workbook. The spreadsheet will calculate the total proposed price for the Offeror. The total fully burdened rate for each labor category will be the capped ceiling for that labor category for firm-fixed-priced type
Task Orders. This is the maximum rate for the labor category for use when proposing on FFP Task Orders. Offerors may propose less than these rates on Task Orders.
The Offeror’s spreadsheet shall also include option pricing for an additional six-month period that may be authorized IAW FAR 52.217-8.
The Offeror is required to submit prices for all labor categories proposed in accordance with the Performance Work
Statement. The Offeror shall complete a labor rate tab in the workbook that encompasses fully-loaded/burdened labor rates for all labor categories proposed for all contract years. For Task Order 1 pricing, the labor rates and indirect loadings rates for the six-month option period shall be the same as those in effect for the final option period for evaluation purposes.
For the first Task Order, the Offeror must propose a CLIN 9999, Surge. The Government may require surge support during the base or any option period of the first Task Order. The Government is providing a percentage value to be used by all offerors when proposing surge: surge support will not exceed 25% of the offeror’s total proposed cost/price for the base and all option periods of the first task order, excluding the six-month extension of services pursuant to FAR 52.217-8. Offerors are instructed to propose this EXACT percentage for Surge CLIN 9999. In the event the Government does elect to exercise the Surge Option, surge support will be realigned under new or existing
CLINs for the relevant task areas identified in the PWS, and an equal amount will be deducted from Optional Surge
CLIN 9999. The Government will not conduct a cost realism analysis on Optional Surge CLIN 9999 if all other labor CLINs under the contract/task order are determined to be realistic.
For the first Task Order, the offeror shall use the estimated Other Direct Costs (ODCs) figures provided by the
Government under the Pricing Summary tab as a plug amount in its price proposal for evaluation purposes only.
Travel ODCs
Base Year $10,000.00
Option Year 1 $10,000.00
Option Year 2 $10,000.00
Option Year 3 $10,000.00
Option Year 4 $10,000.00
Six-Month Extension $5,000.00
All travel shall be authorized by the Task Order Contracting Officer’s Representative (COR) in writing prior to travel, and will be paid in accordance with FAR Part 31.205-46. The Contractor will be authorized to invoice monthly for all incurred travel costs approved by the Task Order COR.
L.9.3. Estimating Methodology.
L.9.3.1. Estimating System. Provide a summary description of the standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, G&A). Also, identify any deviations from the standard estimating procedures in preparing this proposal volume. Indicate whether the Government has approved your system and if so, provide evidence of such approval.
L.9.3.2. Purchasing System. Provide a summary description of the purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from the standard procedures in preparing this proposal. Indicate whether the Government has approved your system and if so, provide evidence of such approval.
L.9.3.3. Accounting System. Task orders issued under this contract may include cost type or incentive type line items. As such, the successful offeror is required to have an adequate accounting system in accordance with FAR
16.301-3(a)(3) and DFARS Subpart 242.75. The offeror shall indicate whether the Defense Contract Audit Agency
(DCAA) has determined their accounting system to be adequate and if so, provide evidence of such determination.
It is the offeror’s responsibility to inform the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .