W900KK-23-R-0009 (SF 30) Amendment 0002.pdf

PDF 796 KB Posted

Attached to
Amendment 0002, Battle Command Training Equipment (BCTE)
Solicitation number
W900KK-23-R-0009RFP
Issued by

View the file

Other files

File Type Posted
Attachment 4 BCTE Notational Schedule.xlsx XLSX spreadsheet
Attachment 0002 BCTE Amendment 0002 Letter Updated BCTE responses.xlsx XLSX spreadsheet
Attachment 8 - BCTE L M PWS References.xlsx XLSX spreadsheet
BCTE Amendment 0002 Letter.pdf PDF
Attachment 7 BCTE Past Performance Questionnaire.docx DOCX document
Attachment 2 BCTE - TO 0001 PWS.pdf PDF
Attachment 10 BCTE Cost-Pricing Workbook FINAL rev 3 5-9-2023.xlsx XLSX spreadsheet
W900KK-23-R-0009 Amendment 0002.pdf PDF
Attachment 3 BCTE QASP.pdf PDF
Attachment 1 BCTE -IDIQ_PWS.pdf PDF
Attachment 9 - BCTE Pre-Award Survey.pdf PDF
Attachment 12 - BCTE PWS Crosswalk.xlsx XLSX spreadsheet
Attachment 11 - BCTE Proposal Adequacy Checklist.pdf PDF
Attachment 0001 BCTE Amendment 0002 Letter additional responses to Questions.xlsx XLSX spreadsheet
Attachment 5 - DD-254 BCTE.pdf PDF
Attachment 6 - BCTE Question Comment Form.xlsx XLSX spreadsheet
Exhibit A-2 BCTE TO 0001 CDRLs.pdf PDF
Exhibit A-1 BCTE IDIQ CDRLs.pdf PDF
Attachment 3 BCTE QASP.pdf PDF
W900KK-23-R-0009 (SF 30) Amendment 0001.pdf PDF
Attachment 4 BCTE Notational Schedule.xlsx XLSX spreadsheet
Exhibit A-1 BCTE IDIQ CDRLs.pdf PDF
Attachment 7 - BCTE Past Performance Questionnaire.docx DOCX document
BCTE Amendment 0001 Letter.pdf PDF
Attachment 10 BCTE Cost-Pricing Workbook.xlsx XLSX spreadsheet
Attachment 5 - DD-254 BCTE.pdf PDF
Attachment 2 BCTE TO 0001 PWS.pdf PDF
Attachment 12 - BCTE PWS Crosswalk.xlsx XLSX spreadsheet
Attachment 9 - BCTE Pre-Award Survey.pdf PDF
Attachment 8 - BCTE L and M PWS References.xlsx XLSX spreadsheet
Exhibit A-2 BCTE TO 0001 CDRLs.pdf PDF
BCTE Amendment 0001 Letter Attachment 0001 Responses to Questions.xlsx XLSX spreadsheet
Attachment 11 - BCTE Proposal Adequacy Checklist.pdf PDF
Attachment 1 BCTE IDIQ_PWS.pdf PDF
W900KK-23-R-0009 Amendment 0001.pdf PDF
Attachment 6 - BCTE Question Comment Form.xlsx XLSX spreadsheet
BCTE Update 0001 Letter.pdf PDF
Consolidation Determination for CBCSE_BCTC-ES.pdf PDF
Attachment 10 BCTE Cost-Pricing Workbook.xlsx XLSX spreadsheet
Exhibit A-2 BCTE TO 0001 CDRLs.pdf PDF
Attachment 4 BCTE Notational Schedule.xlsx XLSX spreadsheet
Attachment 9 BCTE Pre-Award Survey of Prospective Contractor Accounting System Checklist.pdf PDF
Attachment 13 BCTE PWS Crosswalk.xlsx XLSX spreadsheet
Attachment 3 BCTE QASP.pdf PDF
Attachment 1 BCTE IDIQ_PWS.pdf PDF
Exhibit A-1 BCTE IDIQ CDRLs.pdf PDF
Attachment 5 BCTE DD 254.pdf PDF
Attachment 8 BCTE L and M PWS References.xlsx XLSX spreadsheet
W900KK-23-R-0009 (BCTE Solicitation).pdf PDF
Attachment 10 BCTE Cost-Pricing Workbook.xlsx XLSX spreadsheet
Show 40 more

Latest 50 of 56 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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 is to make revisions to Section L and M of the solicitation Document.

POC: Keith Adams Keith.l.adams3.civ@army.mil

1. CONTRACT ID CODE PAGE OF PAGES

S 1 31

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 16-May-2023

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 W900KK23R0009

X 9B. DATED (SEE ITEM 11)

30-Mar-2023

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 is extended, X 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 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

16-May-2023

CODE

ARMY CONTRACTING COMMAND - ORLANDO

ATTN: CHARLIE DIVISION

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

W900KK 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W900KK23R0009

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

L. PROPOSAL SUBMISSION (Section L) L.1. Proposals for the Basic ID/IQ and Delivery/Task Order 0001 shall be compliant with the full solicitation requirements and instructions contained within this section. Proposal submissions for the Basic ID/IQ, and Delivery/Task Order 0001 will be evaluated for consistency to ensure the Offeror’s understanding of the entire BCTE requirement. The Government will evaluate each proposal in accordance with this solicitation; Offerors are required to comply with all requirements stated herein. Any statement that the Offeror does not intend to meet all of the requirements, the proposal & Offeror will not be evaluated, deemed non-compliant, and will be ineligible for award.

The Government will determine that an Offeror's proposal is noncompliant, and therefore ineligible for award, if the proposal indicates that: it cannot or will not meet all the requirements; provides an approach that clearly does not meet any of the requirements; or includes data which prompts the Government to question the Offeror's compliance with any of the requirements.

Introduction. The requirement is a Small Business Set Aside, to be competed among companies qualifying under NAICS 541519 (Exception – Information Technology Value Added Resellers) which sets the small business size standard at 150 employees. The technical requirements and the details for the ID/IQ contract and DO/TO 0001 are defined within section J of this solicitation.

L.1.1.a An Offeror’s submission of a proposal in response to this solicitation constitutes approval for disclosure of proprietary information contained within the proposal to non-government participants involved in the source selection. If the contractor is not willing to provide this consent, written notification to the Procuring Contracting Officer (PCO) is required no later than 15 days prior to the proposal due date.

L.1.1.b Offerors shall demonstrate their capability, understanding, and willingness to satisfactorily perform the effort described in the Base ID/IQ Performance Work Statement (PWS), and the efforts outlined in the PWS for Delivery/Task Order 0001 located in Section J of this solicitation, for the resultant Single Source ID/IQ contract and Delivery/Task Order 0001.

L.1.1.c The POCs for this solicitation are identified below:

Primary Keith Adams Contract Specialist

Phone: (407) 208-3338 Email: keith.l.adams3.civ@army.mil U.S. Army Contracting Command – Orlando 12211 Science Drive Orlando, FL 32826-3224

Cara Borowski Contract Specialist Phone: (407) 208- 3412 Email: Cara.l.borowski2.civ@army.mil U.S. Army Contracting Command – Orlando 12211 Science Drive Orlando, FL 32826-3224

Marvin Hagan Procuring Contracting Officer (PCO) Phone: (407) 208-3349 Email: marvin.j.hagan.civ@army.mil U.S. Army Contracting Command – Orlando 12211 Science Drive Orlando, FL 32826-3224

Capabilities may be established within either the Offeror’s corporate structure or through contractor teaming arrangements. The Government is neither encouraging nor discouraging teaming arrangements and will focus on the Offeror's proposed approach to perform the full scope of work. The proposal shall be valid for 365 calendar days from date of initial proposal submission. The Offeror shall insert the validity date in Block 12 of the SF 33.

L.1.1.e. Unless otherwise specifically stated, the term contract will be synonymous with the words contract, project or effort, when used in reference to information required in association with this solicitation.

L.1.1.f. Any Offeror that submits any OCI plan, shall submit IAW C.2 of the solicitation to the POCs in section L.1.1.c.

L.1.2 The Offeror’s proposal shall be submitted in digital copies, as set forth below:

L.1.2.a The Offeror’s proposal shall consist of four (4) volumes. The Volumes are:

Volume I – Program Management/Technical Volume II – Past Performance Volume III – Cost/Price Volume IV – Solicitation, Offer and Award Documents and Certifications/Representations.

**Files shall not contain classified data.

**The use of hyperlinks in proposals is prohibited.

L.1.3. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the entire requirement and associated risks, and is able, willing, and competent to devote resources necessary to meet the requirement and has a valid and practical solution for the requirement. Statements that the prospective Offeror understands, can, or will comply with the requirements, and statements paraphrasing the requirements or parts thereof without supporting information/narrative are considered inadequate and unsatisfactory. Mere reiteration of the requirement or standard reference material is discouraged and is considered inadequate and unsatisfactory. The Offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. In presenting material in proposals, the Offeror’s proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. Clarity and readability are very important. The Government will not infer meanings from vague or ambiguous language. Offerors are cautioned that while the Government will not evaluate every PWS requirement for the purposes of the source selection evaluation, the awardee/Contractor will be required to comply with all PWS requirements during performance of the contract. The Offeror’s proposal shall describe its approach to implementing PWS requirements that are being evaluated. The proposal shall reference the related paragraphs of the PWS (e.g. 3.1.2), Section J, Attachment 8, L+M PWS Reference, and provide the detail necessary to substantiate the proposed approach and methodology for performance. Attachment 8, L+M PWS Reference will be used for informational purposes to facilitate evaluation, but it will not be evaluated. The proposal should identify any unique or innovative approaches, which ensure successful performance. The Government will determine that an Offeror's proposal is non-compliant, and therefore ineligible for award, if the proposal indicates that: it cannot or will not meet all the requirements; provides an approach that clearly does not meet any of the requirements; or, includes data which prompts the Government to question the Offeror's compliance with any of the requirements. The Source Selection Authority may reject all proposals received in response to a solicitation, if doing so is in the best interest of the Government. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked in accordance with FAR 52.215-1.

L.1.4. The proposed approach should be specific, detailed, and contain sufficient information to clearly and fully demonstrate the Offeror’s understanding of the requirements and the inherent risks associated with this procurement. It is inadequate to simply state that the Offeror understands and will comply with the requirements, or to paraphrase the requirements. The proposal shall comprehensively explain how the Offeror proposes to comply with the applicable requirements, as well as describe the techniques and procedures the Offeror proposes to implement its proposed approach.

L.1.5. Information previously submitted to the Government should be assumed unavailable during this proposal evaluation and source selection process. Proposal data shall not be incorporated into the proposal by referring to another proposal or other source. Proposals submitted will not be returned. Alternate proposals will not be evaluated or accepted. If an alternate proposal is provided the Offeror will be deemed ineligible and removed from the competition.

L.1.6. The portions of the successful Offeror’s (Awardee’s) proposal that have merit or exceeds specified performance or capability requirements in a way that will be advantageous to the Government during contract performance will be incorporated into Section C of the resulting contract and resulting delivery/task orders.

L.1.7. The Offerors shall ensure that each proposal volume submitted contains only the information relevant to that specific volume. The Offerors are cautioned that each volume of the proposal is evaluated standalone against the criteria set forth in Section M and the evaluators for one volume may be different than the evaluators of another volume. It is incumbent upon the Offerors to ensure they properly submit their proposals. If the data is not contained in the appropriate volume of the proposal, it will not be evaluated. For example, if Past Performance narratives (as specified in L.3.2) are submitted under the Cost/Price Volume rather than the volume specified, the proposal will be evaluated as if no Past Performance narratives were submitted at all. No cost information shall be included in the Program Management/Technical and Past Performance Volumes of the Offerors proposal. The volumes will be evaluated in accordance with the Evaluation Criteria provided in Section M. Failure of an Offeror to provide all requested proposal information will render the Offeror’s proposal as non-compliant and as such, the Offeror’s proposal will not be evaluated. If determined to be non-compliant, the PCO will notify the Offeror as soon as practicable.

L.1.8. If an Offeror believes that the requirements or the solicitation contain an error, omission, or are otherwise unsound; the Offeror shall immediately notify Contract Specialists Keith Adams at Keith.l.adams3.civ@army.mil, Cara Borowski at Cara.l.borowski2.civ@army.mil, AND the Contracting Officer Marvin J. Hagan at Marvin.j.hagan.civ@army.mil with supporting rationale, prior to the solicitation due date

L.1.9. Solicitation Questions: All questions regarding the solicitation shall be submitted in writing to the Contract Specialist Keith Adams at Keith.l.adams3.civ@army.mil , and Cara Borowski at Cara.l.borowski2.civ@army.mil Contracting Officer Marvin J. Hagan at Marvin.j.hagan.civ@army.mil no later than 12pm EDT on 12 April 2023. Offerors shall submit questions using solicitation Section J, Attachment 6, BCTE Question Comment Form located in Section J. No phone inquiries, questions, or comments regarding the solicitation will be received or acknowledged. Offerors will receive an acknowledgement of their question via response to the email submission. All inquiry items will be answered via an Amendment to the Solicitation and posted to sam.gov website under the solicitation number. Answers will be posted without Offeror identification. The Government will not provide responses to questions that would reveal a potential Offeror’s confidential business strategy, technical solution, or any information that is considered unique to a particular Offeror. Offeror’s are responsible for notifying the Government if any information provided as part of a question is considered proprietary or confidential information. The Government reserves the right to decline addressing questions received after 12pm EDT on 12 April 2023.

L.1.10. In accordance with FAR Subpart 52.215-1, Instructions to Offerors – Competitive Acquisition, the Government intends to evaluate proposals and award a contract without discussions with Offerors (except clarifications as described in FAR 15.306(a)). Therefore, the Offeror’s initial proposal should contain the Offeror’s best terms from a cost or price and technical standpoint. However, the Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary. The Contracting Officer will schedule the discussion sessions, and each Offeror within the competitive range will be notified of the date and time at least three (3) business days prior to their discussion session. The Contracting Officer will provide additional instructions with the notification.

If 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 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 among the most highly rated proposals. Clarifications are not discussions. Offerors may be given the opportunity to clarify certain aspects of the proposal or resolve minor or clerical errors (see FAR 15.306(a)(1) and (2)). Clarifications shall be documented on, and conducted via transmittal of, Evaluation Notices (EN) to the applicable Offeror.

L.1.11. Any legally organized offeror may submit a proposal. Contractor Team Arrangements are considered as an arrangement in which (1) two or more companies form a partnership or joint venture to act as a potential prime contractor, or (2) a potential prime contractor agrees with one or more other companies to have them act as its subcontractor under a specified Government contract or acquisition program. In accordance with FAR Subpart 9.6, the Government will recognize the integrity and validity of contractor team arrangements; provided, the arrangements are identified, and company relationships are fully disclosed in the offer. The prime contractor will be held fully responsible for contract performance, regardless of any team arrangement between the potential prime contractor and its subcontractors. Where the use of subcontractors is proposed, the proposal shall clearly distinguish between the prime and the major subcontractor’s work and responsibilities. Major subcontractors are defined as members of an Offeror’s overall team who will provide support or whose subcontract is for more than fifteen (15) percent of the total proposed cost/price.

A small business joint venture offeror must submit, with its offer, the representation required in paragraph (c) of FAR solicitation provision 52.212-3, Offeror Representations and Certifications-Commercial Products and Commercial Services, and paragraph (c) of FAR solicitation provision 52.219-1, Small Business Program Representations, in accordance with 52.204-8(d) and 52.212-3(b) for the following categories:

(A) Small business;

(B) Service-disabled veteran-owned small business;

(C) Women-owned small business (WOSB) under the WOSB Program;

(D) Economically disadvantaged women-owned small business under the WOSB Program;

or

(E) Historically underutilized business zone small business.

L.1.12. Any proprietary information shall be submitted directly to the CS and PCO separately for major subcontractors and shall be furnished in the same format, level of detail, and submission due date as prescribed for the prime Offeror. Subcontractor proposals submitted separately are considered part of the Offeror’s proposal, including the page count. If subcontractor proposals are submitted separately, directly to the CS and PCO and are late, the entire proposal will be considered late.

L.2. PROPOSAL SUBMISSION REQUIREMENTS

L.2.1. Page Size and Format: A page is defined as each face of a sheet of paper containing information. Page size shall be 8.5 x 11 inches. Each paragraph shall be separated by at least one blank line. Pages shall be single spaced with portrait orientation. Except for the reproduced sections of the solicitation document (Section A-K), Arial font shall be used with no less than 12 point size. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software.

All pages of each volume shall be appropriately numbered (X of Y) and shall contain the company name, date and solicitation number in the header and/or footer.

Pages shall be numbered sequentially by volume. All pages shall be marked: “SOURCE SELECTION INFORMATION -- SEE FAR 2.101 AND 3.104” in the footer. Additional data use restrictions, as specified in FAR 52.215-1(e), shall be located in the header/footer area of each page where applicable.

The submission shall be clearly indexed and logically assembled. A Table of Contents shall be created for each volume using the Table of Contents feature in Microsoft (MS) Word.

The Table of Contents shall delineate the subparagraphs within the volume. Table of Contents do not count against the page limitations for their respective volumes. The signed Standard Form (SF) 33, SF30 and Section K – Certifications and Representations may be submitted in Adobe.pdf file format. MS Word files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right – 1” Gutter – 0” From Edge – Header, Footer – 0.5” Page Size, Width – 8.5” Page Size, Height – 11” The following additional restrictions apply:

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and may utilize: 1) 10 point Arial or Times New Roman font;

2) landscape orientation; and/or 3) an alternate paper size of 11x17, if necessary.

Note: Any 11X17 inch page counts as two pages.

Landscape pages may only be used for legible tables, charts, graphs and figures; not for pages of text. For legible tables, charts, graphs and figures, text shall be no smaller than 10 point.

L.2.2. File Packaging: Offerors shall submit, as per Table 1, Section L.4, entire proposal (5 volumes) in electronic format. Each proposal volume shall consist of separate electronic file(s). All files shall be clearly identified with a filename appropriate to the content (e.g., Volume-I, Technical Appendix-A). Use separate files to permit rapid location of all portions, exhibits, annexes, and attachments, if any.

Offerors shall follow these instructions:

i. All files on shall be directly supported by MS Office 2016 or newer and verified to be free of any virus or malware. Failure to submit in the correct format is grounds for non-compliance determination, at the sole discretion of the PCO.

• Word documents – Set "Save as type" to "Word Document (*.docx)" only.

• Excel spreadsheets – Set "Save as type" to "Microsoft Excel Workbook (*.xlsx)." All formulas present and no cells locked.

• PowerPoint presentations – Set "Save as type" to "Microsoft PowerPoint 2013 Presentation (*.pptx)."

• Microsoft Project – There are no special “save” functions required.

ii. All of the proposal files shall be separate documents in their native format; i.e. xls, doc, ppt. Submit PDF documents using only Adobe Acrobat 9.0 or later. Do NOT submit any documents in PDF format that are copied as “images.”e.g. Teaming Agreements, Letters of Commitment, or other types of signature pages may be submitted in an image format.

iii. All submitted files (MS Office and PDF) shall be created with textual search and copy functions enabled. Non-searchable signature pages are acceptable, but other submitted materials that are not searchable may not be evaluated, and the Offeror may be determined non-compliant, at the sole discretion of the PCO.

** Please note – self-extracting .exe files will not be accepted.

L.2.3. Submitting Proposals: The required method of proposal delivery is via the DoD Secure Access File Exchange (SAFE) located at https://safe.apps.mil/. Hard copy proposals will not be accepted. Offerors shall ensure the recipients receiving the proposal submitted via DoD SAFE are the BCTE solicitation Primary POC, Alternate POC, and the PCO, identified in Section L.1.9. and shall be received no later than by 12pm EDT 25 May 2023.

Standard access to DoD SAFE requires personnel to have a Government Common Access Card (CAC). If the Offeror does not have any personnel with a CAC, the Offeror shall contact the aforementioned POCs at least 72 hours prior to the proposal due date/time. The Government will then provide a DoD SAFE link that does not require CAC access within one business day.

Offerors are encouraged to test the DoD SAFE proposal exchange methodology by sending a copy of the BCTE PWS to the aforementioned POCs at least 72 hours prior to the proposal due date/time. The Government will confirm receipt, via email, within one business day. If confirmation email is not received, please coordinate directly with the solicitation’s POCs to resolve issue.

If there are any technical difficulties with DoD SAFE, the Offeror shall coordinate an alternate method of BCTE proposal submittal with the Primary POC, no less than 72 hours prior to the due date and time. It is the Offeror’s responsibility to ensure that the entire proposal is received by the Government prior to the proposal due date and time. All proposals submitted must be in compliance with the full solicitation.

L.2.4. OFFERORS ARE HEREBY ON NOTICE THAT FAILURE TO SUBMIT ALL THE

REQUIRED PROPOSAL INFORMATION IN EXACTLY THE MANNER (TIMELINESS

AND FORMAT) AS SPECIFIED IN THE SOLICITATION WILL CONSTITUTE A BASIS

FOR THE GOVERNMENT TO REJECT A PROPOSAL AS NON-COMPLIANT AND

THEREFORE INELIGIBLE TO BE CONSIDERED FOR AWARD.

L.2.5. Each volume shall be submitted in Microsoft Office 2016 or newer. Any pages that are changed (as a result of discussions or proposal revisions) should have changed information clearly marked by a vertical line in the right margin of the page. The revised pages shall be dated. Each volume shall be clearly labeled with its Title and a copy number (i.e., sequentially number the required copies with the original being labeled as Copy No. 1).

L.2.6. Paragraphs should be single spaced. Each paragraph shall be separated by at least one blank line. A standard, 12-point minimum Arial font size is required. Tables shall be no less than 10-point font and may be landscape. Illustrations (e.g. images or diagrams) shall use a font size of no less than 10-point and may be landscape. The Integrated Master Schedule (IMS) and Integrated Master Plan (IMP) (submitted in Volume I-Program Management) shall be submitted using Adobe Acrobat Reader (PDF) export (maximum page size is 11 inches x 17 inches). The Risk Management Plan (RMP) (submitted in

Volume I-Program Management) and the Configuration Management (CM) shall be submitted using Microsoft Office Word and shall follow the paragraphs requirements above.

L.2.7. The following volumes of material shall be submitted:

VOLUME TITLE DIGITAL COPIES

MAXIMUM PAGES

I Program Management / Technical

Original

Breakdowns: Program Management/Technical as 20* + IMP (10) + IMS (10) (max. page size is 11 inches x 17 inches) + RMP (10) + CM (10) for total page count of 60 pages for Vol I.

II Past Performance

35*

III Cost/Price

Unlimited

IV – Solicitation, Offer and Award Documents and Certification/ Representations

Original Unlimited

NOTE: Pages that exceed the required page limitations will not be evaluated.

Additional pages over the maximum allowed will be removed and will not be evaluated by the Government.

*Table of Contents, Title Pages, Divider/Blank Pages, Teaming Arrangements, and PWS References (Section J, Attachment 8) are excluded from the page count.

Content Requirement. All information shall be confined to the appropriate file. The Offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents and the Narrative discussion. Proprietary information shall be clearly marked. Proposals shall be marked Controlled Unclassified Information.

L.3 VOLUMES AND FACTORS

L.3.1 VOLUME I – Factor 1: Program Management/Technical This volume shall demonstrate the Offeror’s understanding of the requirements of the basic ID/IQ and TO 0001. This factor, to include subfactors, shall not exceed 60 pages. The work outlined in TO 0001 is representative of the Program Management requirements of this ID/IQ effort;

therefore, this volume shall demonstrate the Offeror’s understanding of the entire Program Management requirement through the Offeror’s DO/TO 0001 proposal submission under the program management volume. Relevant PWS sections that will be evaluated are provided under each Subfactor; however, Offerors may include additional material to the extent that it is necessary to describe the proposed approach for meeting the requirements being evaluated. All referenced PWS sections are inclusive of sub-paragraphs and sections unless specific sub-paragraphs are listed (e.g. a reference to paragraph 3.1 implicitly includes all 3.1.x and other nested paragraphs unless specific sub-paragraphs are also listed). The Government may consider the impact of the Offerors proposed approach on the ability to meet all solicitation requirements, even if not being specifically evaluated, in the evaluation of each subfactor. The Offeror shall complete, and attach to Volume I, the Section I, Attachment 8 table to provide the specific PWS subparagraphs (e.g. 3.1.3.x) and proposal references to each subfactor element in the Program Management, Technical Volumes of the Offerors proposal. Attachment 8 is for informational purposes only and will not be evaluated.

The volume shall be organized sequentially into the following sections:

L.3.1.a Factor 1 - Subfactor 1, Management Approach The Offeror shall provide an Integrated Master Plan (IMP) and a resource loaded Integrated Master Schedule (IMS), on 11x17, that details the effective planning, critical paths, scheduling, execution, monitoring and controlling of the work effort. The IMS and IMP shall cover the base period (36 months) to include DO/TO 0001. The Offeror's IMP shall be an event-driven plan that documents the significant accomplishments necessary to complete the work and ties each accomplishment to a key program event. The Offeror's IMS shall be an integrated and networked multi-layered schedule of program tasks required to complete the work effort captured in the IMP. The Offeror may reference Department of Defense, October 21, 2005, Integrated Master Plan and Integrated Master Schedule: Preparation and Use Guide, version 0.9 as a guide.

The Offeror shall provide their organizational structure to manage the BCTE program that will meet the requirements of the effort. The Offeror shall describe their overall management approach for performing within cost, schedule and performance parameters, to include effective coordination with teaming partners and subcontractors. The Offeror shall describe their management approach in performing responsibilities as a Prime contractor and interacting with the Government Program Office (GPO). The Offeror shall describe their processes to facilitate socialization and integrated working relationships with the BCTE program and their respective contractors to achieve program objectives and to ensure excellent communication and thorough understanding of issues.

The Offeror shall describe how the Offeror’s organization will adapt to rapidly changing program requirements and provide the required agility, flexibility, and responsiveness to meet customer and technical requirements, constraints, and priorities.

Relevant PWS sections include IDIQ PWS all of 1.6 and all of 5, DO/TO 0001 PWS all of 8.

L.3.1.b Factor 1- Subfactor 2, Delivery/Task Order 0001 The Offeror shall describe their approach for meeting the requirements of Delivery/Task Order 0001. The offeror shall provide the Labor Categories, skill mix, hours, and job descriptions deemed necessary to accomplish the requirements of Delivery/Task Order 0001. The Delivery/Task Order 0001 proposal approach shall be consistent with the Basic ID/IQ proposal to ensure the Offeror’s understanding and application of its approach to meet the BCTE requirements.

The Offeror shall describe their proposed approach to control, secure, inventory, record and audit procured property. The Offeror shall describe their approach to effectively and efficiently manage their Resources, Events/Tasks, Phase In activities and Time/Schedule regarding program performance and staffing in support of multiple, simultaneous and complex efforts (i.e. exercises, test events, software version upgrades, help desk responsiveness, and technology/site refreshes), without negatively impacting development and activities.

The Offeror shall also address how this approach addresses software configuration management of multiple software baselines, assuming 2 fielded versions and 1 development version. The Offeror shall discuss in detail their proposed approach to meeting Army Cyber Security/OPSEC requirements to maintain cyber security accreditation. The Offeror shall describe their proposed approach to identify, collect, analyze, and present technical metrics to assess the OPSEC and RMF postures of BCTE. Relevant PWS sections include but not limited to IDIQ: All of 1.6 and all of 5 DO/TO 0001: all of 8.

L.3.1.c Factor 1 - Subfactor 3, Configuration Management Plan

The Offeror shall provide a Configuration Management Plan (CMP). The Offeror shall describe their approach to effectively and efficiently manage their Resources, Events/Tasks, Integration activities and Time/Schedule regarding program performance and staffing in support of multiple, simultaneous and complex efforts (i.e. exercises, test events, software version upgrades, held desk responsiveness, integration events and technology refreshes), without negatively impacting activities. The Offeror shall also address how this approach addresses software configuration management of multiple software baselines.

The offeror shall describe their CMP approach and process to establish and maintain the configuration baseline of COTS Products deployed at each location. The offeror shall describe their approach to trace the procurement of COTS products back to decision points and track COTS hardware and software products status on the DoD Unified Capabilities (UC) Approved Product List (APL). The offeror shall describe how they will satisfy CM data requests from the Government. Relevant PWS sections include IDIQ: 5.1.7 and DO/TO 0001: 8.1.7, 11, 12, 23, 24

L.3.1.d Factor 1 - Subfactor 4, Risk Management Plan

The Offeror shall provide a Risk Management Plan (RMP). These plans shall address at a minimum: overall risk approach; methods; top BCTE risks; risk levels; mitigations; and tracking measures relative to cost, schedule, and performance.

The Offeror may reference Department of Defense Risk, issue, and Opportunity Management Guide for Defense Acquisition Programs, January 2017, as a guide. Relevant PWS sections include IDIQ: 5.1.7.1 and DO/TO 0001: 8.1.8

L.3.2 VOLUME II – Factor 2: Past Performance

This volume shall contain past performance information regarding similar contracts. This volume with all subfactors shall not exceed 35 pages excluding Cure Notices, Show Cause Letters, and Past Performance Questionnaire Forms. Offerors shall submit no more than three (3) recent Government and/or commercial contracts for the prime offeror and no more than three (3) recent Government and/or commercial contracts for each major subcontractors which were awarded or in performance during the past five (5) years from the issue date of this solicitation (with at least a year performance during the five-year period). Major subcontractors are defined as members of an Offeror’s overall team who will provide support or whose subcontract is for more than fifteen (15) percent or more of the total proposed cost/price.

The Offeror shall describe their experience(s) in the following area(s): Training support package plan for New Equipment Training, Instructor/Operator Training, and ESS Maintenance Training. The Offeror shall describe their experience(s) in the following area(s): Control, secure, inventory, record and audit procured property. The Offeror shall describe their experience(s) in the following area(s): Procuring Information Technology hardware through Computer Hardware, Enterprise Software and Solutions (CHESS) and/or similar procurement avenues that distribute worldwide. The Offeror shall describe their experience(s) in the following area(s): Supporting site fielding’s and/or site refreshes at multiple sites concurrently, for both CONUS and OCONUS.

Relevant efforts are defined as follows:

• Similarity of service/support (for example: Ability to reach out and surge resources, when needed; ability to manage resources effectively and efficiently across multiple, simultaneous, and complex efforts to include quote development, fielding an upgrade, help desk support and integration events without impacting performance).

• Complexity (for example: experience with integration of complex standalone systems into an integrated-type training/operational environment through a closed architecture and infrastructure; related Cybersecurity and Risk Management Framework (RMF) experience.)

The Offeror shall describe their past examples of hardware procurement, software licenses, methodologies, processes, and technical approach to meet the BCTE requirements.

The Offeror shall discuss their proposed process and documentation developed to reproduce, operate, maintain, install, and control total system support and operation.

If an Offeror is utilizing past performance information of subcontractors, the proposal shall clearly demonstrate that the subcontractors will have meaningful involvement in the performance of the contract. The Offeror shall clearly identify and describe the work that the subcontractors will be performing under the BCTE effort. Furthermore, Offerors shall explain how the past performance work specifically relates to the work that will be performed under the BCTE effort. The description of the work performed by the subcontractors will be considered in determining the relevancy of the past performance information provided for the subcontractors. If the Offeror fails to demonstrate the subcontractor’s meaningful involvement in the performance of the resultant contract, the contract or effort will not be considered relevant and will not be evaluated. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, Unique Entity Identification (UEI) and type of work to be performed by citing the applicable Government PWS subparagraph number. This includes all subcontractors who will be providing support or whose subcontract is for more than fifteen

(15) percent or more of the total proposed cost/price. This section will further include written consent of major subcontractors to allow the disclosure of their subcontractor’s past performance information to the Offeror.

Data concerning the offeror shall be provided first under contract description listed below, followed by each proposed major subcontractor, in alphabetical order. Major subcontractors are defined as members of an Offeror’s overall team who will provide support or whose subcontract is for more than fifteen (15) percent or more of the total proposed cost/price. The Offeror shall also submit the written consent of its major subcontractors to allow the disclosure of its subcontractor’s past performance information to the Offeror.

Offerors shall provide a specific narrative explanation of each contract listed in below Contract Description, describing the general description, abbreviated scope, and objectives achieved; detailing how the effort is relevant to the requirements of this solicitation and are similar in scope and magnitude of effort and the complexities of BCTE.

L.3.2.a Factor 2 - Subfactor 1, Contract Description

a. Contractor/Subcontractor place of performance, CAGE Code and Unique Entity Identification (UEI). If the work was performed as a subcontractor, also provide the name and prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e- mail address, and telephone and fax numbers).

b. Government contracting activity, and current address, Procuring Contracting Officer’s name, e-mail address, telephone and fax numbers.

c. Government’s technical representative/COR, and current e-mail address, telephone, and fax numbers.

d. Government contract administration activity and the Administrative Contracting Officer’s name, address and current email address, telephone, and fax numbers.

e. Contract Number and, in the case of Indefinite Delivery type contracts GSA contracts and Blanket Purchase Agreements, include delivery/task order numbers as well.

f. Contract Types (specific type such as Firm-Fixed Price (FFP), Cost Reimbursement (CR), Time and Material (T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (requirements, Definite Quantity, and Indefinite Quantity) and secondary contract types (FFP, CR, T&M, etc.)).

g. Awarded price/cost.

h. Final or projected final price/cost.

i. Original Delivery schedule, including dates of start and completion of work.

j. Final or projected final, delivery schedule, including dates of start and completion of work.

The offeror shall submit to the Contracting Officer and Contract Specialist a list of all the POC’s who were sent a questionnaire (refer to Section 5 below). The POC List shall be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-mail Address; and Date E-Mail to POC (month/day).

L.3.2.b Factor 2 - Subfactor 2, Performance/Quality If any firm has multiple functions or divisions, the Offeror shall limit the records of Past Performance to those performed by the division, unit or team member submitting the offer. If an Offeror is utilizing past performance information of affiliate/subsidiary/parent company, the proposal shall clearly demonstrate that the affiliate/subsidiary/parent company will have meaningful involvement in the performance of the contract. The Offeror shall clearly identify and describe the work that the affiliate/subsidiary/parent company will be performing under the effort. Furthermore, Offerors shall explain how the past performance work specifically relates to the work that will be performed under the effort. The description of the work performed by the affiliate/subsidiary/parent company will be considered in determining the relevancy of the past performance information provided for the affiliate/subsidiary/parent company. If the Offeror fails to demonstrate the affiliate/subsidiary/parent company’s meaningful involvement in the performance of the resultant contract, the contract or effort will not be considered relevant and will not be considered in the evaluation of Past Performance.

Offerors shall provide a specific narrative explanation of each contract listed in Section 1 Contract Description, describing the general description, abbreviated scope, and objectives achieved; detailing how the effort is relevant to the requirements of this solicitation and are similar in scope and magnitude of effort and the complexities of BCTE.

L.3.2.c Factor 2 - Subfactor 3, New Corporate Entities In accordance with FAR 15.305(a)(2)(iii), the evaluation shall take into account past performance information regarding predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or aspects of the requirement when such information is relevant to the instant acquisition. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

L.3.2.d Factor 2 - Subfactor 4, Past Performance Questionnaire For all contracts identified in Section 1, Contract Descriptions, the Offeror shall forward a copy of the Attachment 7, Past Performance Questionnaire located in Section J to the cognizant PCO and Technical Representative/COR (or equivalents for commercial contracts/efforts) related to the effort that is being submitted as a past performance entry.

The Offeror shall instruct them to send completed questionnaires via email to the Contracting Officer, no later than the proposal due date, to Marvin.j.hagan.civ@army.mil, Contract Specialists, Keith.l.adams3.civ@army.mil, and Cara.l.borowski2.civ@army.mil.

The cognizant PCO and Technical Representative/COR (or equivalents for commercial contracts/efforts) shall not send their questionnaires back to the Offeror. Questionnaires received late may be accepted and reviewed at the discretion of the PCO, if the PCO determines that it will not cause an undue delay to the procurement process. It is the

Offeror’s responsibility to request timely delivery of the completed questionnaire(s) to the proper email addresses.

The PCO will have discretion to determine whether questionnaires that are returned late will be used as part of the past performance evaluation. Questionnaires that are not returned at all, will not be evaluated favorably or unfavorably on the past performance evaluation. The Government reserves the right to send additional questionnaires as necessary or contact individuals identified by the Offeror that have not completed or submitted questionnaires for evaluation. The Government reserves the right to contact and use information provided by the references and any other sources available to conduct a performance risk evaluation.

To ensure inclusion of all references in the evaluation process, the Offeror is encouraged to provide the Government with the most current data on each reference. Please note that any references provided on classified contracts cannot be verified. To the extent possible, limit references to contracts performed as either a prime, a first-tier subcontractor or a joint venture.

L.3.2.e Factor 2 - Subfactor 5, Adverse Past Performance In accordance with FAR 15.306, the Offeror may be given the opportunity to discuss adverse past performance information obtained from any questionnaire if they have not previously responded through Contractor Performance Assessment Reporting System (CPARS) or similar system. However, the names of individuals providing the information shall not be disclosed. Adverse past performance is defined as past performance information that supports a less than satisfactory rating from sources where the information is from other than formal rating systems such as CPARS and Federal Awardee Performance and Integrity Information System (FAPIIS).

L.3.3 VOLUME III – Factor 3: COST/PRICE

The Cost/Price Volume shall be submitted in a separate, detachable, and unclassified form for the purpose of evaluation independent of the other volumes. There is no page limit for this volume. All information relating to cost or pricing must be included in this section of the proposal and defined as cost data. This volume shall stand alone in supporting the offeror’s approach to reasonableness, and completeness, of this effort. The information submitted in response to this section shall be in a format compatible with Microsoft Office 2016 or newer.

It is expected that this contract will be awarded based upon a determination that there is adequate price competition; therefore, the offeror is not required to provide certified cost or pricing data with its proposal. If, after receipt of the proposals, the Contracting Officer determines that adequate price competition does not exist in accordance with FAR 15.403- 1, the offeror shall provide certified cost or pricing data as requested by the Contracting Officer.

Any additional files contained in the Cost/Price Volume shall not be password protected and all cell formulas and cell references shall be intact, and the worksheet shall be unprotected, not locked. All Excel workbooks shall include formulas that are executable and traceable to allow the Government to test and evaluate the Offeror’s and supporting Major Subcontractor’s proposed labor rates.

L.3.3.a Factor 3 - Subfactor 1, Unbalanced Pricing Offerors shall avoid presenting unbalanced pricing information. Unbalanced pricing exists when, despite an acceptable total evaluated price, the price of one or more price element is significantly over or understated, as indicated by the application of cost or price analysis techniques per FAR 15.404(g). Offerors are cautioned that a proposal may be rejected, if unbalanced pricing exists and the contracting officer determines that the lack of balance poses an unacceptable risk to the Government.

L.3.3.b Factor 3 - Subfactor 2, Cost Proposal Adequacy Checklist The Offeror shall complete the Cost Proposal Adequacy Checklist (See Attachment 11) and provide with their proposal as an appendix to Offerors Cost/Price Volume.

L.3.3.c Factor 3 - Subfactor 3, Price Workbook The Offeror shall complete Attachment 10-Cost-Pricing Workbook provided with this solicitation (to include all Worksheets related to labor descriptions and the buildup of the labor rates, including indirect rates within the Workbook), and to submit prices for all unpriced CLINs for the ID/IQ and Task Order 01 highlighted in yellow in the Basic ID/IQ and TO 01 tabs for the entire period of performance. Offerors may not alter pre-existing formulas within the workbook except as noted in the instructions, or the Not to Exceed (NTE) values provided.

The proposed Contract Line Item Number (CLIN) prices within Section B and Attachment 10 are binding and will be utilized for the life of the contract.

The fully burdened labor rates presented in the Labor Rates tabs of Attachment 10 will be incorporated into the contract as not-to-exceed caps for each labor category throughout the contract term and reflected for each year to include all Option periods. Narratives regarding the Cost/Price Volume may be submitted in MS Word 2016 or newer format.

NOTE: Do not propose Labor to the Travel CLINs.

The Offeror shall not propose travel to any non-travel ID/IQ or T.O.01 CLINs.

Offerors shall provide all pricing associated with the remaining FFP CLINs in the Cost Price Workbook attachment 10 and the CPFF CLINs for Installation Services Labor and Material, Equipment and ODC.

Labor Categories and fully burdened Cap Rates:

The Offeror must clearly show the fully burdened hourly rate for each proposed labor category.

For all proposed labor categories, Offerors were provided, Description of Work Performed, Education Level, Minimum Years of Experience in Attachment 10 for the development of the Labor Rates.

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 .