W9124J20R00050003, IMCOM SBS RFP Amendment 3, 13 Feb 20.pdf

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 solicitation amendment is to incorporate new language referencing On-Ramping and Off-Ramping procedures (paragraph 2.12) into Section L, Proposal Preparation Instructions.

POC: Michael T. Bilicki, Contract Specialist, 210-466-2267, e-mail: michael.t.bilicki.civ@mail.mil

1. CONTRACT ID CODE PAGE OF PAGES

J 1 12

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

16C. DATE SIGNED

BY 13-Feb-2020

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 W9124J20R0005

X 9B. DATED (SEE ITEM 11)

23-Jan-2020

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

13-Feb-2020

CODE

MICC - FSH

ATTN: MICC - FSH

2205 INFANTRY POST RD

210-466-2145

FORT SAM HOUSTON TX 78234-1361

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W9124J20R0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been added by full text:

PROPOSAL PREPARATION INSTRUCTI

L-I - PROPOSAL PREPARATION INSTRUCTIONS

1. Proposal Submittal and Inquiries.

1.1. Proposals shall be submitted prior to the closing date and time identified on the SF33, addressed to the both of the following individuals:

Contracting Officer: Mr. Stephen D. Noethen, e-mail: stephen.d.noethen.civ@mail.mil Contract Specialist: Mr. Michael T. Bilicki; e-mail: michael.t.bilicki.civ@mail.mil

1.2. Submissions via mail (paper copies), hand delivered, or fax will not be accepted. Offerors shall submit their offers electronically via the DOD SAFE file exchange website (safe.apps.mil). Offerors must state their intention to propose by 4:00 p.m. (Central Time), 10 February 2020 by submitting an email to the Contracting Officer and Contract Specialist. Offerors will then be provided a password to upload their electronic files on the DOD SAFE file exchange website NLT 4:00 p.m. (Central Time), 18 February 2020. DOD SAFE file exchange website passwords will not be provided prior to 18 February 2020. Proposals can be uploaded to the DOD SAFE file exchange website at any time after the Offeror receives their password, up to the proposal submission deadline.

Offerors are responsible for verifying that the Government has received the files electronically before the proposal due date and time. NOTE: No DOD SAFE file exchange website passwords will be provided to any Offeror who does not provide an e-mail to the Contracting Officer and Contract Specialist no later than 4:00 p.m. (Central Time), 10 February 2020, stating their intent to propose. The Government strongly encourages Offerors to ensure they can access the DOD SAFE website as soon as possible.

1.3. All inquiries during the solicitation phase shall be directed to the Contract Specialist, Mr. Michael T. Bilicki, and the Contracting Officer (KO), Mr. Stephen D. Noethen via email only. Offerors are requested to review the solicitation and submit only written questions and/or comments with email subject line reference: Questions and/or Comments Support Base Services, W9124J-20-R-0005. The deadline for the submittal of all questions and/or comments is 12:00 (noon), Central, Tuesday, 4 February 2020. All questions shall be submitted using the format provided in Section J, Attachment 2.

1.4. Time for Acceptance. The Offeror’s proposal shall remain valid for a period of 180 days from date of solicitation closing date identified on the SF33.

2. General Instructions

2.1. The selection of sources for award purposes will be conducted utilizing the OSD Class Deviation 2018-O0006 Evaluation Factors for Certain Multiple Award Task or Delivery Order Contracts and source selection procedures in accordance within FAR 15.3, as supplemented by the DoD Source Selection Procedures referenced in DFARS 215.300, and AFARS mandatory procedures in 5115.3 to make an award decision. Offers will be evaluated using the criteria under Section M, “Evaluation Factors for Award.” Noncompliance with the solicitation requirements may hamper the Government's ability to properly evaluate the proposal and may result in elimination of the proposal from further consideration for contract award. An Offeror is considered a qualifying Offeror when the Offeror is determined to be a responsible source, submits a technically acceptable proposal that conforms to the requirements of the solicitation, and the Contracting Officer has no reason to believe would be likely to offer other than fair and reasonable pricing.

2.2. The Offer. The submission of the documentation specified below will constitute the Offeror's acceptance of the terms and conditions of the solicitation, concurrence with the Performance Work Statement, and the proposed contract type.

2.3. It is the Government’s intention to award without discussions. Offerors are encouraged to present their best technical capability proposal in their initial proposal submission. However, IAW FAR 15.306, should discussions become necessary, the Government reserves the right to hold them. If this occurs, a competitive range will be established and Offerors notified.

2.4. These instructions prescribe the format for the proposal and describe the approach for the development and presentation of proposal data. These instructions are designed to ensure the submission of necessary information to provide for the understanding and comprehensive evaluation of proposals.

2.5. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one electronic copy of all unsuccessful proposals. The Government will destroy extra copies of such unsuccessful proposals. No destruction certificate will be issued.

2.6. If an Offeror believes that the requirements in these instructions contain an error, an ambiguity, omission, or are otherwise unsound, the Offeror shall immediately notify the KO in writing with supporting rationale. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.7. All referenced documents for this solicitation are available on the Government Point of Entry web site at http://beta.sam.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.8. Debriefings. The KO will promptly notify Offerors of any decision to exclude them from the competitive range, if one is established, whereupon they may request and receive a debriefing in accordance with FAR 15.505.

The KO will notify unsuccessful Offerors of the source selection decision in accordance with FAR 15.503(b). Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.9. Team Member(s)/Teaming Partner(s). For the purpose of performance and technical capability, the Government will consider the Offeror and all subcontractors a “team” when evidence of a signed Teaming Arrangement (TA) or Letter of Intent (LOI) is provided. This solicitation will refer to the Offeror and all identified teaming subcontractors as a “team,” “team members” or “teaming partners.” However, for the purpose of financial capability and financial resources, the Government will only consider information from the prime contractor, whose CAGE code is found on the SF33.

2.10. Teaming Arrangement or Letter Of Intent. To be valid under this solicitation, all team members shall have a signed TA or LOI that commits the parties to performance under this contract, should it be awarded to the Offeror.

(a) A subcontractor without a TA or LOI with the Offeror is not considered as part of the “team” and will not be evaluated as such.

(b) Technical Capability proposal information and Past Performance Information, submitted for subcontractors without a TA or LOI will not be evaluated.

(c) The Government will consider the Offeror and all subcontractors a “team” when evidence of a signed TA or LOI is provided in Volume I, General.

(d) A Joint Venture (JV) will be considered a sole business entity.

(e) Mentor-Protégé (M-P) is a relationship and not a business entity. M-Ps require formal TAs or LOIs to qualify for consideration as a team member.

(f) The proposal shall present a complete, coherent presentation of team abilities as applicable.

2.11. Continuation of Essential Contractor Services. In accordance with Defense Federal Acquisition Regulation Supplement 252.237-7024, Continuation of Essential Contractor Services:

With each respective task order, Offerors shall provide with its offer a written plan describing how it will continue to perform the essential contractor services listed in the Performance Work Statement during periods of crisis. The offeror shall–

(1) Identify provisions made for the acquisition of essential personnel and resources, if necessary, for continuity of operations for up to 30 days or until normal operations can be resumed;

(2) Address in the plan, at a minimum—

(i) Challenges associated with maintaining essential contractor services during an extended event, such as a pandemic that occurs in repeated waves;

(ii) The time lapse associated with the initiation of the acquisition of essential personnel and resources and their actual availability on site;

(iii) The components, processes, and requirements for the identification, training, and preparedness of personnel who are capable of relocating to alternate facilities or performing work from home;

(iv) Any established alert and notification procedures for mobilizing identified “essential contractor service” personnel; and

(v) The approach for communicating expectations to contractor employees regarding their roles and responsibilities during a crisis.

The Continuation of Essential Contractor Services Plan is not required at the Multiple Award Indefinite Delivery/Indefinite Quantity (MA ID/IQ) contract level, but will be required for each respective task order written from this MA ID/IQ contract.

2.12. On-Ramp/Off-Ramp Procedures:

2.12.1. On Ramp: The Government reserves the right the re-open the solicitation for the purpose of adding additional SBS MA ID/IQ contract holders (On-Ramp). On-Ramp procedures may be implemented prior to expiration of the base five-year ordering period by reopening the competition and utilizing the same basis of award established in the initial solicitation. This includes keeping the same set-aside (SDVOSB) outlined in this acquisition strategy. On-Ramp notification procedures will include publicizing a notice on the Beta.Sam.Gov website, issuing a conformed copy of the solicitation, and conducting a source selection. Any resulting contracts awarded will include the same terms and conditions as the basic contract minus the base five-year period. Neither the overall period of performance nor the maximum of the basic contract will be changed as a result of implementing On-Ramp procedures. Any pre-award protest of the solicitation during On-Ramping shall be considered untimely since this is a continuation of the evaluation criteria and methodology already established under initial solicitation.

2.12.2. Off-Ramp: The Government reserves the right to implement Off-Ramp procedures, which will result in the removal of MA ID/IQ contract holders. The criteria for Off-Ramping may include, and is not limited to:

2.12.2.1. MA ID/IQ contract holders not having at least one task order (TO) award (excluding the guaranteed minimum award);

2.12.2.2. Contractors having less than satisfactory Contractor Performance Assessment Reporting System (CPARS) ratings specific to TOs awarded under the SBS MA ID/IQ contract;

2.12.2.3. Debarment, Suspension, or Ineligibility as defined in FAR Subpart 9.4;

2.12.2.4. Termination as defined in FAR Part 49; and,

2.12.2.5. Contractors prior to five-year mark that recertify as other than SBs under NAICS code 561210 or by a MA ID/IQ contract holder not submitting a proposal for three or more Request for Task Order Proposal (RTOPs) over a two-year period without a satisfactory explanation.

2.12.2.6. If implemented, the administrative method of Off-Ramping would be accomplished by not exercising the option (additional five-year ordering period) for any MA ID/IQ contract holders that re-certify as other than SB, or meet one or more of the above listed criteria, if it is in the Government's best interest to do so.

3. Proposal Preparation Instructions

3.1. Offeror’s proposal shall consist of three (3) separate volumes: General, Technical Capability, and Past Performance.

3.2. Proposal Format.

3.2.1. Offerors shall submit proposals through electronic means through the DOD SAFE website (safe.apps.mil).

3.2.2. Page limitations for the volumes are as follows:

VOLUME TITLE Maximum Page Limits

Section Evaluated?

I General No limit No

Executive Summary 3 No II Technical Capability

Management Approach for Sample Task Order Scenario

Subfactor 1A

Yes

Staffing and Training Approach

Subfactor 1B

Yes

Expertise Subfactor 1C 10 Yes III Past Performance Past Performance 30 Yes Consent Letters Unlimited No

3.2.3. Copies. Only one (1) electronic copy of each volume is required.

3.2.4. Page format. Page size shall be 8 ½” X 11”, (when/if printed). All pages shall have a 1” margin on all sides and shall be typed with at least single line spacing. No condensed fonts allowed. Times New Roman, Arial, or similar font preferred. Text shall be a minimum font size of 10 (ten), to include all tables and charts. Page numbers, company logos, headers and footers may be outside the page margins and are not bound by the 10 (ten) font size, but shall be no smaller than 8-point. Each paragraph shall be separated by at least one blank line. All text pages shall be oriented in portrait, and printed black on white paper (black and white requirement does not apply to graphics, photos, tables, charts, section headings, etc., Company stationary and logos are acceptable). Landscape orientation is acceptable for tables and/or charts if required to properly present the information.

3.2.5. What Counts As A Page? A page shall be an 8 ½” X 11” sheet of paper (when/if printed). Letter size and spacing requirements for illustrations and tables can be at the discretion of the Offeror but must be easily readable.

The Offeror shall number each page in order to eliminate any confusion. In the event the Offeror creates an ambiguity in their numbering of pages, the Government may exercise its own discretion in counting pages, which may result in information not being evaluated.

3.2.6. Volume Labels. All volumes shall have cover sheets that identify volume number, title, solicitation number, and the Prime Contractor’s cage code.

3.2.7. Electronic submissions.

(a) Electronic submission of each volume shall be compatible with the following available Government equipment and software products:

(1) Adobe Acrobat Reader

(2) Microsoft Office 2013

(b) Sound or video (e.g. MPEG) files shall not be embedded into the proposal files.

3.2.8. Page Limit Includes: All appendices, charts, graphs, diagrams, tables, photographs, drawings, etc.

3.2.9. Page Limit does not include cover sheets for volumes, tables of contents, glossary of abbreviations and acronyms, indices, title pages, and section dividers/tabs if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. (NOTE: They will be counted if they contain any other information, i.e., diagrams, extraneous data, etc.) Pages marked “This page intentionally left blank” will not be counted.

3.2.10. Indexing. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume.

3.2.11. Glossary of Abbreviations and Acronyms. Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each.

3.2.12. Proposal Limitation. The proposal shall not exceed the limits stated above. Pages that exceed the margin, character, or total page limitations will not be evaluated. The Government will not accept any changes to the Offeror’s proposal after the closing date of the solicitation (See FAR 15.208 for further information regarding late proposals). If discussions become necessary, page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for ENs responses will be identified in the letters forwarding the ENs to the Offerors.

4. Proposal Content.

4.1. Volume I – General. Offerors are required to submit a completed SF 33 (including acknowledgment of all Amendments), and Section K. Failure to follow the below Contract Proposal preparation instructions may cause your proposal to be deemed unacceptable by the Government. The General Volume shall be organized as follows and contain the identified information.

4.1.1. Executive Summary – Provide an executive summary that describes the significant attributes and theme of its proposal and introduces the Offeror’s team. The offer shall clearly state the Offeror’s business size with respect to NAICS code 561210 and their certification as a Service Disabled Veteran Owned Small Business. The offer shall state whether or not the prime has a facility clearance, and what level of clearance.

4.1.2. Exceptions/Assumptions - Identification and explanation of any exceptions or deviations. Any assumptions used in the proposal preparation must be identified. Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors (Sections A through M). Failure to meet a requirement may result in an offeror being ineligible for award. If the Offeror finds it necessary to take exception to any of the requirements specified in this solicitation, clearly indicate in the applicable Volume each such exception with a complete explanation of why the exception was taken, what benefit accrues to the Government (if any), and its impact (if any) on performance, schedule and cost. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. This information shall be provided in the format below.

Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion

Rationale & Impact

Section B, PWS, Section L&M, etc.

Applicable Page and

Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe the rationale and impact of the exception

4.1.3. SF 33 - The Offeror shall submit the SF 33 fully completed. The Offeror is cautioned that the SF 33 must contain an original signature in block 17 of the form (electronic signatures are acceptable). The Offeror shall acknowledge all amendments to the solicitation in accordance with the instructions on the SF 33 and with Section L, FAR 52.215-1, Instruction to Offerors—Competitive Acquisition.

4.1.4. Contact Information. The Offeror shall include a contact list (with phone numbers, fax numbers, mailing addresses, e-mail addresses, etc.) of all key personnel. Specifically, the contact list shall identify those personnel authorized to negotiate on behalf of their company, as well as a single point of contact for all correspondence.

Furthermore, the list shall indicate the person to contact in the event the Offeror is awarded a contract (provide, at a minimum, contact’s title, phone number, and e-mail address); typically the person to notify in the event of award is a senior professional of the corporation.

4.1.5. Section K (Representation, Certifications, and Other Statements of Offerors) – The Offeror shall ensure that this information is correctly stated in the beta.sam.gov website unless the offeror chooses to provide a copy of this information to the Government. Information received/provided will be reviewed for a compliance check, but will not be evaluated for the purpose of determining technical competency.

4.1.6. Joint Ventures (JVs), Teaming Arrangements, and/or Letters of Intent. Provide all Joint Venture Agreements, TAs and LOI for subcontractors to receive credit for performing as a team, in accordance with Section L. In the General Volume, provide a list of Team Partners for which a signed TA or LOI was submitted. Teaming Arrangements and/or Letters of Intent will not count against the total page count for the General Volume (Volume 1).

4.1.7. Financial Responsibility.

(a) The Prime Contractor must demonstrate that it has or can obtain adequate financial resources to perform the contract in accordance with FAR 9.104-1(a) and DFARS 232.072. State whether the Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA) or the Small Business Administration (SBA) has conducted a financial assessment within the 12-month period prior to proposal submission; and if so, provide evidence of the assessment results. If results of a DCMA, DCAA, or SBA financial assessment in the last 12 months is not available, follow instructions in paragraph 4.1.7(d).

(b) The Prime Contractor shall fully demonstrate adequate financial resources. If the Offeror intends to rely on internally available working/operating capital, evidence of $3M in availability shall be submitted. If the Offeror plans to rely on financial support from other sources, the Offeror shall submit a single letter of credit from a financial institution. The line of credit must be on the financial institute’s letterhead and shall show a minimum of $3M in line of credit.

(c) The information in paragraphs (a) and (b) shall be provided for the Offeror, including JVs. If the Offeror is a combination of firms (for example, a partnership or joint venture), discuss the financial responsibilities among the companies.

(d) Offerors that have not had a financial assessment within the 12-month period prior to proposal submission shall request a Financial Capability Risk Assessment by submitting the following information by email to the Contracting Officer and Contract Specialist. The email subject line should read, “SBS #W9124J-20-R-0005, Financial Capability Risk Assessment.” This request should be accomplished upon receipt of the solicitation, but no later than 15 days after release of the solicitation.

(1) Company’s Full Name

(2) DUNS Number and Cage Code

(3) Address (where accounting records are held)

(4) Company Point of Contact

(5) POC Phone Number

(6) Cognizant DCAA Office (address, phone number, DCAA POC, email address (if available))

(7) Indicate if you are proposing as a stand-alone prime or JV

(e) Include a copy of the email requesting a Financial Capability Risk Assessment in the General Volume.

Copy(s) of the Financial Capability Risk Assessment e-mails do not count against the total page count listed for the General Volume (Vol 1).

(f) Financial responsibility is not an evaluation criterion. It is a basic contract requirement with a pass/fail determination. A contract may be awarded to the Offerors who are deemed responsible in accordance with the FAR Subpart 9.1.

4.1.8. DCAA/DCMA Information. Offerors shall provide the name and address of their cognizant DCAA and DCMA office, DCAA and DCMA POC and phone numbers, and last DCAA audit date and copy of audit.

4.1.9. Continuation of Essential Services Plan: As indicated in paragraph 2.11., the Continuation of Essential Services Plan shall not be required at the MA ID/IQ contract level, but may be required for each respective task order.

4.1.10. Volume I Page Count: Pages utilized for Exceptions/Assumptions (paragraph 4.1.2.), SF 33 (4.1.3.), Contact Information (4.1.4.), Section K (4.1.5.), Joint Ventures (4.1.6.), Financial Responsibility (4.1.7.), and DCAA/DCMA Information (4.1.8.) do not count against the page count for Volume I - General.

4.2. Volume II - Technical Capability Volume

4.2.1. General. The Technical Capability Volume shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims. Legibility, clarity, and coherence are very important.

Your responses will be evaluated against the Technical Capability subfactors defined in Section M, Evaluation Factors for Award. 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. Statements that the Offeror understands, can, or will comply with the PWS (including referenced publications, technical data, etc.);

statements paraphrasing the PWS or parts thereof (including applicable publications, technical data, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable. Offerors shall assume that the Government has no prior knowledge of their facilities and expertise, and will base its evaluation on the information presented in the Offeror's proposal. Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

4.2.2. At a minimum, the Technical Capability Volume shall be prepared in a form consistent with the PWS and the evaluation criteria for award set forth in Section M of this solicitation. This volume shall be prepared in an orderly format and with sufficient detail to enable the Government to make a thorough evaluation of the Offeror’s technical competence and ability to comply with the contract task requirements specified in the PWS. The Offeror shall address, as specifically as possible, the actual methodology that will be used for accomplishing the PWS tasks. The Offeror shall organize the Technical Capability volume in accordance with the following general outline:

- Table of Contents

- List of Table and Drawings

- Cross Reference Matrix (if applicable)

- Provide a list of Team Partners for which a signed Teaming Arrangement or Letter Of Intent was submitted with this proposal in accordance with paragraph 2.10. (Note: Team Partner listing is not counted against the page count).

- Technical Capability

- Subfactor 1A: Management Approach for Sample Task Order Scenario

- Subfactor 1B: Staffing and Training Approach

- Subfactor 1C: Expertise

4.3. Subfactor 1A – Management Approach for Sample Task Order Scenario: This subfactor is only applicable to the sample task order scenario (hereafter referred to as the scenario). This scenario is representing services that may be required by the Government. The scenario will be based on a cost-plus-fixed-fee (CPFF) type task order. The Offeror shall describe its technical approach to developing a solution based on the information presented in the Scenario in Section J, Attachment 3. The offeror shall state all assumptions made when providing its solution to the scenario.

4.3.1. The Offerors will provide a narrative that includes:

4.3.1.1. A phase-in plan for the scenario that conveys a reasonable approach for assumption of full responsibility at the end of the phase-in period. The phase-in approach shall identify the actions to be accomplished, transition risk(s), effective measures to mitigate the risks, and realistic timelines associated with the following areas:

(a) Hiring qualified personnel to meet the proposed staffing solution by the first day of task order performance

(b) Identifying teaming member assignments

(c) Transferring and distributing Government-furnished property

(d) Conducting employee orientation/training: contractor-specific and government-specific requirements (i.e. safety, security)

(e) Transferring, activating, and validating security clearances (key positions) and background checks

(f) Identifying methods for developing/submitting Task Order Deliverables

4.3.1.2. The Offeror’s solution to handling fluctuating workloads for the scenario must include an adequate understanding and approach of the surge environment and provides for contractor manpower adjustments to meet the mobilization/demobilization/readiness requirements for soldiers, brigades, and units. The approach shall include a complete narrative on the anticipated effects of the surge on each Branch/Section identified in Attachment 3, Paragraph 2.0.

Offerors shall use the scenario information presented when developing a realistic solution to mobilize and deploy the unplanned surge of 4,236 Reserve Component Soldiers.

4.4. Subfactor 1B – Staffing and Training Approach: This subfactor is applicable to the entire PWS. The Offeror shall outline its approach for the entire SBS Multiple Award Indefinite Delivery / Indefinite Quantity (MA ID/IQ) contract under this subfactor. The proposal shall contain narrative and supporting material (e.g., matrices, charts, other graphics, etc.) determined necessary for the Government to fully understand the Offeror’s approach.

The Offeror’s staffing and training approach shall demonstrate:

(a) The ability to recruit, hire, and retain personnel with the knowledge, skills, education, expertise, and training to successfully execute each task area outlined in the SBS PWS.

(b) The ability to hire and retain qualified personnel in the following hard to fill positions:

(1) Weapons repair personnel

(2) Mechanical technical inspectors

(c) The Offeror’s approach to successfully executing a feasible training plan that indicates how all personnel are trained, qualified/certified prior to assuming a position. Approach must address:

(1) Cross training and retraining as applicable, and refresher training procedures.

(2) Evaluation and monitoring of training requirements to include certification/licensing.

(3) Tracking the completion of the Army-specific training (initial, recurring, and one-time) to include environmental, safety and occupational health training.

4.5. Subfactor 1C - Expertise: The Offeror shall demonstrate expertise which conveys specific knowledge and expertise in the critical fields identified below:

(a) Area 1: maintaining and repairing weapons and vehicles similar to Army field-level maintenance standards in accordance with appropriate Army Technical Manual (TM) 10-series and TM 20-series tasks.

Equipment is similar to the type and complexity of those contained in this requirement, Section J, Attachment 6, for deploying and resetting units.

(b) Area 2: controlling Arms, Ammunition & Explosives (AA&E) in issuing, handling, storing and maintaining full accountability of AA&E.

4.5.1. The Offeror shall specifically describe its technical expertise in Area 1 and Area 2 by submitting the following, and demonstrating a minimum of three (3) years of expertise:

(a) provide a description of the specific knowledge, skills, and abilities your team has acquired in providing the specified services to the military in the last ten (10) years and describe how this specific knowledge is directly related to the critical performance areas;

(b) provide the date(s) in which this technical knowledge, skills and abilities were gained;

(c) provide the size, complexity and length of the contract action, including contract number(s) in which you gained this technical knowledge, skills and abilities (size is defined by dollar value, and complexity is defined by functions performed, location(s) and type of contract); and

(d) identify specific equipment types and estimated quantities of items controlled/repaired/maintained, broken down by year, shall be provided for each project

4.6. Volume III – Past Performance The Past Performance evaluation will be accomplished by reviewing aspects of an Offeror's recent and relevant Past Performance, focusing on and targeting performance which is relevant to the effort which is defined as:

(a) Contracts >$700,000 (Awarded Value/Ceiling)

(b) Contracts covering SBS tasks areas in the Subfactor 1A scenario at Section J, Attachment 3.

4.6.1 Offerors shall submit no more than ten (10) past performance references. The Offeror (prime) shall select the composition of its past performance references (including teaming partners, sub-contractors, etc).

4.6.2. Past Performance information described herein is required on the Offeror and all teaming partners and/or joint venture partners. The Offeror shall submit, along with the information required in this paragraph, a consent letter, executed by each teaming partner and/or joint venture partner, authorizing release of past performance information to the Offeror so the Offeror can respond to such information.

4.6.2.1. The Offeror shall include documentation regarding their relevant past performance as it directly relates to the work being procured under this solicitation. The Offeror SHALL NOT go back any farther than five (5) years for the submitted data. The past performance data shall document a successful history of past contract performance.

4.6.2.2. In conducting the Past Performance evaluation, the Government reserves the right to use both the information provided in the Offeror’s Past Performance Volume and information obtained from other sources, such as the Contractor Performance Assessment Reporting System (CPARS) or similar systems, Defense Contract Management Agency (DCMA), or direct knowledge from the Government evaluators. Offerors are reminded that both independent data and data provided by Offerors in their proposals may be used by the Government to evaluate Offeror past performance. However, the burden of providing thorough, complete, and current past performance information as requested in this paragraph remains with the Offerors. Proposals that do not contain the information requested by this paragraph risk rejection or a less than acceptable performance rating by the Government. All past performance comments received will be taken into account and could affect the overall rating. The overall past performance evaluation is a subjective decision based on the whole of all data received. In the case of an Offeror without a record of relevant past performance or for whom information on past performance is not available or so sparse that no meaningful past performance rating can be reasonably assigned, the Offeror may not be evaluated favorably or unfavorably on past performance (see FAR 15.305 (a)(2)(iv)). Therefore, the Offeror shall be determined to have unknown past performance. In the context of acceptability/unacceptability, “unknown” shall be considered “acceptable.”

4.6.2.3. Submission Requirements. The Offeror shall submit a Past Performance Volume containing the following:

Note: Table of Contents, Summary Page, Consent Letters, and Organizational Structure Change History pages do not count against the page limit for Volume III – Past Performance

(a) Table of Contents

(b) Summary Page describing the role of the Offeror and each teaming partner, and /or joint venture partner that the Offeror is required to provide Past Performance Specific Relevant Contract Reference Sheets for the past performance expertise in accordance with Section J, Technical Exhibit B.

(c) Consent Letters executed by each teaming partner and/or joint venture partner, authorizing the release of past performance information so the Offeror can respond to such information. A sample consent letter is available in Section J, Technical Exhibit A.

(d) Organization Structure Change History— 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 present or 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 acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation. Since the Government intends to consider present and past performance information provided by other sources as well as that provided by the Offeror(s), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

(e) Specific Relevant Contracts Format - The Offeror shall provide documentation outlining the Offeror’s and teaming partners’ past performance with contracts, as a prime or major subcontractor, which is the same or similar in nature, size, and complexity to the services being procured under this

Solicitation. See specific information on relevancy for this solicitation at paragraph 4.6. The submittal shall include rationale supporting your assertion of relevance and how it was determined that the work performed previously was the same or similar in nature, size, and complexity to the work specified by this solicitation. 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. An example of the format required is available in Section J as Technical Exhibit B.

The following have been deleted:

PROPOSAL PREPARATION INSTRUCTI

(End of Summary of Changes)