Attachment 0019 SECTION L INSTRUCTIONS CONDITIONS AND NOTICES TO OFFERORS.pdf

Section L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 Proposal Submission Requirements. These provisions specify the content, format and quantity constraints required in all proposal submissions. Proposals shall be valid for 270 calendar days after the date of the required proposal submission.

ENFORCEABLITY OF PROPOSAL: The proposal must set forth full, accurate and complete information as required by this solicitation. By submission of the offer, the offeror agrees that all items proposed (if applicable e.g., key personnel, subcontractors, etc.) will be utilized for the duration of the contract and any substitutions require prior Contracting Officer’s approval.

L.1.1. There will be one request for Proposal (RFP) from which two contracts will be awarded. One contract will be for the East Region (AFM-East) and one for the West Region (AFM-West). Offerors must submit a proposal for each desired regional contract effort. Regional proposals will be evaluated independently.

L.1.1.1. Electronic Submission. Failure to meet this requirement may result in a proposal being eliminated and not being evaluated by the Government. Electronic files of each volume shall be submitted through the Department of Defense (DOD) Secure Access File Exchange (SAFE) and must be submitted prior to the submission deadline. All proposals received after the exact time specified for receipt shall be treated as late submissions and will not be considered for award. Submission packages can be multiple files up to 8 GB per file. Due to system capabilities large files may take additional time to upload. The Offeror shall submit its proposal using DOD SAFE application at https://safe.apps.mil/ utilizing the below directions for Offerors with and without a Common Access Card (CAC). For instructions on how to use, please refer to the DoD SAFE Help Guide: https://safe.apps.mil/help/dod-safe-help.html. The Government will confirm receipt of the DOD SAFE submission.

Instructions for Offerors with a CAC:

1. Select "Drop Off" from the main menu

2. Under Add Recipients, use the following name for AFM-East proposals "AFM III East Solicitation" and email usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil and the following name for AFM-West proposals “AFM III West Solicitation” and email usarmy.redstone.acc.mbx.acc-rsa-afm-iii.west@army.mil.

3. Select “Add & Close”

4. Select “Click to Add Files or Drag Them Here”

Attachment 0019

W58RGZ-26-R-0008

https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fsafe.apps.mil%2F&data=05%7C02%7Cantionette.r.mcclinton.civ%40army.mil%7C1a3e40b3604c49edf09008deaa07fa94%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C639135148393974536%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Kc9l%2BeJTOcQVwoPXnZ9JkWlkMgCL0kh%2BbZ9YMmHSw6M%3D&reserved=0 https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fsafe.apps.mil%2Fhelp%2Fdod-safe-help.html&data=05%7C02%7Cantionette.r.mcclinton.civ%40army.mil%7C1a3e40b3604c49edf09008deaa07fa94%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C639135148393991589%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=k7U3EEbHAGBeZ0FGJo0fS%2FikpvpWeOYTPWAlTkvitX8%3D&reserved=0 mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii.west@army.mil

5. Select all files for submission

6. Once files are populated select “Send Drop-off”

Instructions for Offerors without a CAC:

1. Submit a DoD SAFE Drop-Off Request to usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil for AFM-East proposals and usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil for AFM-West proposals No-Later-Than (NLT) 72 hours prior to the proposal submission deadline. Requests for drop-off codes only need to be submitted once. Requests must include at least two, but no more than three POC at the company. No generic company mailbox addresses will be allowed. The POCs will be the only recipients of the drop-off codes throughout the evaluation process.

2. A DoD SAFE Drop-Off Request Code will be sent to the identified POCs. Drop-off codes are valid for 14 days and one submission package.

Any portion of the proposal that is changed (due to negotiations/clarifications or proposal revisions) should be annotated and dated. Each volume shall be clearly labeled with its Title.

L.1.1.2. Alternate Submission Procedures. In the event the DOD SAFE is not operational, experiences technical difficulty, or the Offeror is temporarily unable to access or to use the system, the Offeror shall immediately notify the Procuring Contracting Officer (PCO) using the email address usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil for AFM-East proposals and usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil for AFM-West proposals. This notification must occur NLT two hours prior to the proposal submission deadline.

The alternate method for proposal submission is via email to:

usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil for AFM-East proposals and usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil for AFM-West proposals for which the file size is limited to 12MB total. The Offeror must obtain PCO approval to utilize the alternate submission method. Offerors are responsible for ensuring electronic copies are virus-free and shall run an anti-virus scan before submission. Submissions that are flagged for virus concerns will not be accepted by the system and will result in a delivery failure. Delivery failures not corrected by the submission deadlines will be the fault of the Offeror and will not be considered for award.

L.1.1.3. Non-Compliant Proposal Transmittal Methods. Proposal submitted by mail, by hand-delivery, or through proprietary third part File Transfer Protocol (FTP) sites will not be evaluated.

Attachment 0019

W58RGZ-26-R-0008

mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil

L.1.2. Proposal Files. Failure to meet this requirement may result in a proposal being eliminated and not being evaluated by the Government.

L.1.2.1 Content Requirement. All information shall be confined 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, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. No cost/price information shall be presented in any part of the past performance or technical proposal.

All information shall be presented in the appropriate volume shown below:

Volume Title Digital Copies Maximum Pages I Entry Gate Criteria 2 N/A II Technical 2 115* III Past Performance 2 25** IV Cost/Price 2 No page limit V Small Business Participation 2 25

VI

Solicitation, Offer and Award Documents, and Certifications / Representations

2 No page limit

Table 1 Volume Page Counts

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

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

*The Technical Volume maximum page count (115 pages) includes responses for the Comprehensive Management Plan (maximum 100 pages) and accompanying three scenarios (maximum 5 pages per scenario).

**The Past Performance volume shall consist of up to 25 pages for the prime, and up to 5 pages for each major subcontractor.

The page limit does not include the following documents:

• Past Performance Questionnaire Forms

• All letters (including but not limited to Letters of Commitment, Consent, Cure Notices and Show Cause letter)

• Table of Contents

• List of Abbreviations & Acronyms, and/or Figures

Attachment 0019

• Manning Tables

• Small Business commitment documentation

• Small Business Subcontracting Plan (for large business Offerors)

L.1.2.2. Format. Each paragraph should be single spaced and shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial font is required. Tables and illustrations may use a reduced font size no less than 10-point and may be produced in landscape mode. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and solicitation number in the header and/or footer. A Table of Contents should be created using the Table of Contents feature in MS Word.

MS Word (doc) 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”

Note: Organizational diagram(s), detailed schedules, concept of operation graphics, and information required to support proposed prices (included in Volume IV – Cost/Price) may be submitted on page size 11 X 17.

L.1.2.3 File Packaging. Complete electronic volumes shall be submitted written in Microsoft (MS) Office formats readable by MS Word, MS Excel, MS PowerPoint, and/or Adobe Acrobat (PDF). Electronic copies shall not be password protected.

All the proposal files shall be compressed into a single ZIP file named “proposal.zip” using WinZip version 6.2 or later, or submitted as separate uploads in their native formats (e.g., .doc, .xls, .ppt). Files should be in read-only format, preferably as PDFs.

Each file name shall begin with a three-to-five-letter prefix indicating the offeror’s name.

For example, a submission from XYZ Corporation would include:

• XYZPastPerf.pdf

• XYZTech.pdf

• XYZPrice.pdf

• XYZSolicitation.pdf

Subcontractor submission shall identify both the subcontractor’s and the prime contractor’s name.

Visible Text Only: All proposal content must be presented as visible text. The inclusion of any concealed text is strictly prohibited. Concealed text includes but is not limited to:

• Micro-text (text with a font size below 8 pt)

• White text on a white background

• Text utilizing colors that render it indistinguishable from the background

• Text hidden within images or graphics

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

All cost/price proposal documents shall be submitted in accordance with (IAW) Section L.3.3 Cost/Price.

L.1.2.4 Prohibition of Concealed or Manipulated Text

L.1.2.4.1 Offerors shall submit proposals that are clear, concise, and readily readable.

To ensure accurate analysis by automated evaluation tools and maintain the integrity of the source selection process, the following restrictions apply:

L.1.2.4.2 Formatting Consistency: All text must apply uniform formatting throughout the proposal. Variations in font size, color, or style that the Government deems manipulate or obscures the readability of content are prohibited.

L.1.2.4.3 Compliance Verification: The Government may conduct technical verification to ensure compliance with these requirements. Proposals found to contain concealed or manipulated text will be considered non-compliant and may be rejected.

L.1.2.5 Use of Artificial Intelligence in (AI) tools in Proposal Evaluation

L.1.2.5.1 Use of AI tools in Support of Evaluations: The Government may employ AI as a tool to assist in the analysis and review of offeror proposals. AI tools may be used to support tasks such as summarizing proposal content, identifying compliance with request for solicitation requirements, and highlighting areas of potential strength, weakness, or risk.

L.1.2.5.2 Maintaining Inherently Governmental Functions: Notwithstanding the use of AI tools to support the evaluation process, all final evaluation judgements, including the assignment or assessment of adjectival ratings, best value determinations, and source selection decisions, will be made exclusively by duly appointed Government personnel.

The Government retains sole responsibility for all inherently governmental functions and will not delegate decision making authority to any AI tool.

L.1.2.5.3 Offeror Confidentiality and Data Protection: The AI tools utilized by the Government will be employed in a manner consistent with applicable regulations that

Attachment 0019 govern the protection of proprietary and source selection sensitive information. The AI tool will be an output-only system. Any generated report data is not saved. No proposal data will be transmitted to or processed by external, non-Government systems without appropriate safeguards and authorizations in place.

L.2 Entry Gate Criteria. To be eligible for evaluation of Factors 1,2,3 and 4, the Offeror must first demonstrate it meets the entry gate criteria within the five-year period immediately preceding the initial proposal submission date.

If proposing as a Joint Venture (JV) or Team, the Teaming or Joint Venture Agreement and Formal Commitment letters should be provided for Entry Gate to also be used during the Technical factor evaluation.

L.2.1 The Offeror shall provide the following documentation (copy of the contract, Performance Work Statement (PWS), appropriate certificates (example AS9110 Rev.C), and Government Flight Representative (GFR) approval letters (Flight Operation Procedures/Ground Operation Procedures (FOP/GOP))) in electronic format ONLY as standard of proof the entry gate criteria has been met:

• ENTRY GATE CRITERION 1. The Offeror must have GFR approved procedures performing and managing DoW flight and ground operations IAW DCMA Instruction 8210.1, AFI 10-220, NAVAIRSINST 3710.1, COMDTINST M13020.3, or AR 95-20, dated 5 APR 2017 or later.

• ENTRY GATE CRITERION 2. The Offeror must have experience within the timeframe specified in Section L.2 (as a prime or subcontractor) performing and managing field level rotary wing maintenance while certified AS 9110 Revision C.

The offeror shall provide current copies of its certificate as evidence.

• ENTRY GATE CRITERION 3. The Offeror must have experience within the timeframe specified in Section L.2 performing and managing United States Government (USG) or DoW aviation maintenance at multiple geographic locations, simultaneously, and dispersed greater than 500 miles apart.

• ENTRY GATE CRITERION 4. The Offeror must have experience within the timeframe specified in Section L.2 managing single or multiple USG or DoW contracts having aviation maintenance sites that include CONUS/OCONUS and OCONUS-Foreign locations.

L.3 Factors

L.3.1 Factor 1: Technical. The Offeror’s proposal shall include a Comprehensive Management Plan (CMP) for AFM III – East and West Aviation Maintenance services.

The Offeror’s Comprehensive Management Plan shall include:

~COMPREHENSIVE MANAGEMENT PLAN~

1. Organizational Approach (Program Management)

a. Organizational diagrams inclusive of management, execution levels, key functions (additional duties), locations and areas of coverage. Identify who is direct labor (Labor Category) hourly vs. Overhead (Management/Exempt).

The Offeror shall identify any program oversight, management, lead or critical positions and their qualifications as identified in Section 1 of RFP Attachment 0007, Qualifications and Job Descriptions and required in CDRL 0002, Contractor Personnel & Manning. RFP Attachment 0007, Section 1 identifies overhead type personnel as well as duties that need a designee, appointee or individual to be assigned.

b. Identify a proposed plan to mitigate the following three (3) risks associated with contract performance:

1. Surge to accommodate mission increase and decrease (both up and down);

2. Proper flow-down of procedures, written guidance, and enforcement of such;

3. Mission completion and notice to Government of safe de-obligation of financials.

c. Identify one additional risk and proposed mitigation strategy within the Offeror’s power to mitigate under this Aviation Maintenance contract.

2. Business Management

a. The approach for managing subcontractors, requirements flow-down, funding and CLIN management, cost accounting, cost estimating, cost control, timely vouchers, timely de-obligation of funds, cost overruns, and notification of ceiling price risks.

b. Map the requirements from EIA 748 (current version at time of proposal submission) Standard for Earned Value Management System (paragraphs 2.2-h, 2.4-b, 2.4-c, and 2.4-e) to the cost management approach based on objective evidence and provide a description of compliance.

c. The approach to systematically and continuously partner with the USG to improve program and reduce the annual cost of program management to the USG. Include in the response an approach to collective bargaining agreement negotiations and Service Contract Act changes or updates.

d. The approach to providing timely and accurate contract deliverables and Enterprise Resource Planning/Material Requirements Planning (ERP/MRP) System automation tool reports to meet the PWS reporting requirements.

3. Personnel Management

a. Approach to recruiting, hiring, retaining and improving management team

(Overhead-Program Manager to site supervisor level).

b. Approach to recruiting, hiring, retaining and improving a qualified workforce to accomplish all PWS tasks (Direct hourly labor).

c. Approach to an ongoing training and cross-training program for personnel specific to the scope of the PWS.

d. Approach to planning, executing, reporting overtime required to meet on-going mission requirements and new priority efforts given less than 48-hour notice.

4. Logistics and Government Furnished Property (GFP) Management

a. Approach for managing supply operations and supply shortages for missions within the scope of the PWS.

b. Approach to acquiring, inventorying, maintaining, and disposing of Government Furnished Property (GFP).

c. Approach to taking responsibility for and timely resolution of contractor caused damage to aircraft and GFP.

d. Approach to GFP control during Transition-In and Transition-Out.

5. Performance Management

a. Unique corporate strengths and capabilities for managing field and sustainment level maintenance to accomplish all PWS mission sets.

b. Approach for satisfying performance metrics per the PWS and RFP

Attachment 0008, Contractor Performance Metrics.

c. Approach to managing resources across multiple sites and missions simultaneously: personnel, workloads/workflow, production, and cost.

d. Approach to reducing and reporting in real-time the risks associated with rework, workarounds, escapes and causes of less-than-optimal quality in all maintenance, and support/office processes and operations provided onsite and offsite, CONUS and OCONUS.

e. Describe working knowledge and understanding of Government GCSS-Army and other ERP/MRP systems per the PWS.

f. Approach to new site startup after contract award for CONUS and OCONUS (not during transition-in).

6. Management of Transition

a. Transition In – Detailed approach with milestones to assume control of a region and all sites in the region per PWS.

b. Transition Out – Detailed approach to exit a region and all sites in the region per PWS.

7. Management of Security/Safety/Environmental Management Requirements

a. Approach to meeting Security requirements within DD Form 254 across the region (CONUS and OCONUS) per the PWS.

b. Approach to meeting Safety requirements across the region (CONUS and

OCONUS) per the PWS.

c. Approach to meeting Environmental Management requirements across the region (CONUS and OCONUS) per the PWS.

8. Management of Quality/Best Practices

a. Describe the approach to Quality Assurance and Quality Control within the

PWS that assures a successful final product and customer satisfaction.

b. Describe the approach to verifying compliance at multiple sites and the approach to tracking and analyzing trends over time.

c. Approach to identifying and standardizing best practices across the region.

Total Pages: 100

~SCENARIOS~

L.3.1.1 The Offeror shall apply its CMP to the following AFM-East and AFM-West region-specific scenarios.

1. The Offeror’s responses to the scenarios shall include the step-by-step approach and methodology for accomplishing the work requirements in response to the scenarios provided below. The Offeror will provide written responses to the scenarios below to include its understanding of and capability to perform appropriate maintenance/service/logistics actions to support the Aviation Field Maintenance Program. The response will be no longer than five (5) pages in length per scenario. The Offeror’s scenario responses will be evaluated on its overall interpretation of the PWS requirements and the approach to accomplish each scenario’s effort, identification of appropriate resources, and application of processes and resources to provide timely and cost-effective solutions to the presented problems. Offeror will respond to the AFM-East scenarios if submitting for the AFM-East regional award and the AFM-West scenarios if submitting for the AFM-West regional award.

2. AFM-East Scenarios

a. AFM-East Scenario #1: FMS OCONUS Effort. AMCOM Security Assistance Management Directorate (SAMD) the Apache Helicopter Project Office (AH PO) and the Utility Helicopter Project Office (UH PO) have an un-forecasted mission requirement to establish an AH-64E and UH-60M training location in Poland that must be fully operational within three months after funding is placed on contract. Both the AH and UH project offices can resource the aircraft and required tooling/PGSE/AGSE for the mission. SAMD requested that AFMD provide a Maintenance Augmentation Team (MAT) that will be responsible for all field level maintenance requirements to include maintenance test pilot support for 18 UH-60M and 12 AH-64E aircraft with a monthly training flying hour operational tempo of 25 hours a month per UH- 60M and 30 hours a month per AH-64E. The Polish government will provide all necessary aircraft repair parts and consumables, but the contractor must provide full manning for supply operations. The contractor is responsible for all maintenance tasks to include all aircraft daily inspections, calendar inspections and phase maintenance inspections. The contractor will man and support all aviation field maintenance level back shop operations. All sustainment level maintenance (depot) will be done by non-contractor Depot Field Teams as required. As this is a high threat operational environment, the Polish government will provide an airfield location, secured by military forces, with billeting and meals for US government and contractor personnel. Due to the urgency of this mission, the contractor is expected to provide manning for 24-hour operations seven days per week for a period of six months with an option to extend no more than six additional months.

b. AFM-East Scenario #2: CONUS US Modification Work Order (MWO) travel team. The South Carolina National Guard has requested a MWO travel team at its location to install multiple modifications on six UH-60Ms. The following modifications will be installed to each airframe, and the published team complement and man-hours for each has been provided for reference:

MWO Name/Title Published MH Team Complement

MWO 1-1520-280-50-03 Tail Position Light Switch

15 hours 8.00hr - Aircraft Electrician 2.50hr - Aircraft Mechanic 4.50hr - Aircraft Technical Inspector

MWO 1-1520-280-50-5

Common Infrared Countermeasures (CIRCM)

450 hours 75.00hr - Sheet Metal Mechanic x 2 (37.5hr) 250.00hr - Aircraft Electrician x 2 (125hr) 65.00hr - Aircraft Mechanic 30.00hr - Aircraft Technical Inspector 30.00hr - Team Lead

MWO 1-1520-280-50-27 IR

Searchlight Switch

66 hours 8.00hr - Sheet Metal Mechanic 40.00hr - Aircraft Electrician x 2 (20hr) 8.00hr - Aircraft Mechanic 10.00hr - Aircraft Technical Inspector

MWO 1-1520-280-50-32 FANS

DECON

173 hours

3.00hr - Sheet Metal Mechanic 80.00hr - Aircraft Electrician x 2 (40hr) 80.00hr - Aircraft Mechanic 10.00hr - Aircraft Technical Inspector

MWO 1-1520-280-50-34 ESH 14 hours 13.00hr - Aircraft Electrician 1.00hr - Aircraft Technical Inspector

The government has verified the published direct install hours for each MWO.

The unit will provide hangar space with power for two aircraft lanes for the induction of two aircraft at a time. The contractor shall provide personnel and tooling to complete the effort. The contractor shall be responsible for shipping and inventory of MWO kits from the HUB site. The contractor team will travel from Ft. Campbell, KY. Contractor personnel will work a regular 40-hour work week and will not have hangar access on weekends or holidays. The COR requests that along with the step-by-step approach and methodology, the contractor shall include its surge and drawdown process for this one-time effort.

c. AFM-East Scenario #3: CONUS Level of Effort for Downed Aircraft

Recovery Team (DART). The 82nd CAB had an AH-64E that had a precautionary landing due to an engine problem while enroute to the Joint Readiness Training Center at Fort Polk, Louisiana. The determination is that an engine requires replacement. The aircraft is located in a field next to a major highway 15 miles west of Dothan, Alabama. The aircraft is not close to

Attachment 0019 any available hard stand. The 82nd CAB requests that AMCOM provide support to repair the aircraft on site. The 82nd CAB cannot provide the required MTP support because of numerous other operational and training requirements. The Fort Bragg COR requested the contractor provide the listing of equipment/tools, contractor skill sets/man-hours and repair parts to accomplish the engine change at the aircraft’s current location.

3. AFM-West Scenarios

a. AFM-West Scenario #1: FMS OCONUS Effort. AMCOM Security Assistance Management Directorate (SAMD) the Apache Helicopter Project Office (AH PO) and the Utility Helicopter Project Office (UH PO) have an un-forecasted mission requirement to establish an AH-64E and UH-60M training location in Taiwan that must be fully operational within three months after funding is placed on contract. Both the UH and AH project offices can resource the aircraft and required tooling/PGSE/AGSE for the mission. SAMD requested that AFMD provide a Maintenance Augmentation Team (MAT) that will be responsible for all field level maintenance requirements to include maintenance test pilot support for 18 UH-60M and 12 AH-64E aircraft with a monthly training flying hour operational tempo of 25 hours a month per UH- 60M and 30 hours a month per AH-64E. The Taiwanese government will provide all necessary aircraft repair parts and consumables, but the contractor must provide full manning for supply operations. The contractor is responsible for all maintenance tasks to include all aircraft daily inspections, calendar inspections and phase maintenance inspections. The contractor will man and support all aviation field maintenance level back shop operations. All sustainment level maintenance (depot) will be done by non-contractor Depot Field Teams as required. As this is a high threat operational environment, the Taiwanese government will provide an airfield location, secured by military forces, with billeting and meals for US Government and contractor personnel.

Due to the urgency of this mission, the contractor is expected to provide manning for 24-hour operations seven days per week for a period of six months with an option to extend no more than six additional months.

b. AFM-West Scenario #2: CONUS US Modification Work Order (MWO) travel team. The Montana National Guard has requested a MWO travel team at its location to install multiple modifications on six UH-60Ms. The following modifications will be installed to each airframe, and the published team complement and man-hours for each has been provided for reference:

MWO 1-1520-280-50-03 Tail Position Light Switch

15 hours 8.00hr - Aircraft Electrician 2.50hr - Aircraft Mechanic

Attachment 0019

4.50hr - Aircraft Technical Inspector

MWO 1-1520-280-50-5

Common Infrared Countermeasures (CIRCM)

450 hours 75.00hr - Sheet Metal Mechanic x 2 (37.5hr) 250.00hr - Aircraft Electrician x 2 (125hr) 65.00hr - Aircraft Mechanic 30.00hr - Aircraft Technical Inspector 30.00hr - Team Lead

MWO 1-1520-280-50-27 IR

Searchlight Switch

66 hours 8.00hr - Sheet Metal Mechanic 40.00hr - Aircraft Electrician x 2 (20hr) 8.00hr - Aircraft Mechanic 10.00hr - Aircraft Technical Inspector

MWO 1-1520-280-50-32 FANS

DECON

173 hours

3.00hr - Sheet Metal Mechanic 80.00hr - Aircraft Electrician x 2 (40hr) 80.00hr - Aircraft Mechanic 10.00hr - Aircraft Technical Inspector

MWO 1-1520-280-50-34 ESH 14 hours 13.00hr - Aircraft Electrician 1.00hr - Aircraft Technical Inspector

The government has verified the published direct install hours for each

MWO. The unit will provide hangar space with power for two aircraft lanes for the induction of two aircraft at a time. The contractor shall provide personnel and tooling to complete the effort. The contractor shall be responsible for shipping and inventory of MWO kits from the HUB site. The contractor team will travel from Ft Hood, TX. Contractor personnel will work a regular 40-hour work week and will not have hangar access on weekends or holidays. The COR requests that along with the step-by-step approach and methodology, the contractor shall include its surge and drawn down process for this one-time effort.

c. AFM-West Scenario #3: CONUS Level of Effort for Downed Aircraft Recovery Team (DART). The 1AD CAB had an AH-64E that had a precautionary landing due to an engine problem while enroute to the National Training Center (NTC), Ft. Irwin, California. The determination is that an engine requires replacement. The aircraft is located in a field next to a major highway 15 miles south of Tucson, Arizona. The aircraft is not close to any available hard stand. The 1AD CAB requests that AMCOM provide support to repair the aircraft on site. The 1AD CAB cannot provide the required MTP support because of numerous other operational and training requirements.

The Fort Bliss COR requested the contractor provide the listing of equipment/tools, contractor skill sets/man-hours and repair parts to accomplish the engine change at the aircraft’s current location.

L.3.2 Factor 2: Past Performance. Offerors shall submit a maximum of five relevant Government and/or commercial contracts for the prime offeror and NO MORE THAN

Attachment 0019

SECTION II - SOLICITATION PROVISIONS

Section L - PROPOSAL SUBMISSION

L.1 Proposal Submission Requirements. These provisions specify the content, format and quantity constraints required in all proposal submissions. Proposals shall be valid for 270 calendar days after the date of the required proposal submission.

ENFORCEABLITY OF PROPOSAL: The proposal must set forth full, accurate and complete information as required by this solicitation. By submission of the offer, the offeror agrees that all items proposed (if applicable e.g., key personnel, subcontractors, etc.) will be utilized for the duration of the contract and any substitutions require prior Contracting Officer’s approval.

L.1.1. There will be one request for Proposal (RFP) from which two contracts will be awarded. One contract will be for the East Region (AFM-East) and one for the West Region (AFM-West). Offerors must submit a proposal for each desired regional contract effort. Regional proposals will be evaluated independently.

L.1.1.1. Electronic Submission. Failure to meet this requirement may result in a proposal being eliminated and not being evaluated by the Government. Electronic files of each volume shall be submitted through the Department of Defense (DOD) Secure Access File Exchange (SAFE) and must be submitted prior to the submission deadline. All proposals received after the exact time specified for receipt shall be treated as late submissions and will not be considered for award. Submission packages can be multiple files up to 8 GB per file. Due to system capabilities large files may take additional time to upload. The Offeror shall submit its proposal using DOD SAFE application at https://safe.apps.mil/ utilizing the below directions for Offerors with and without a Common Access Card (CAC). For instructions on how to use, please refer to the DoD SAFE Help Guide: https://safe.apps.mil/help/dod-safe-help.html. The Government will confirm receipt of the DOD SAFE submission.

Instructions for Offerors with a CAC:

1. Select "Drop Off" from the main menu

2. Under Add Recipients, use the following name for AFM-East proposals "AFM III East Solicitation" and email usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil and the following name for AFM-West proposals “AFM III West Solicitation” and email usarmy.redstone.acc.mbx.acc-rsa-afm-iii.west@army.mil.

3. Select “Add & Close”

4. Select “Click to Add Files or Drag Them Here”

W58RGZ-26-R-0008

https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fsafe.apps.mil%2F&data=05%7C02%7Cantionette.r.mcclinton.civ%40army.mil%7C1a3e40b3604c49edf09008deaa07fa94%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C639135148393974536%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Kc9l%2BeJTOcQVwoPXnZ9JkWlkMgCL0kh%2BbZ9YMmHSw6M%3D&reserved=0 https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fsafe.apps.mil%2Fhelp%2Fdod-safe-help.html&data=05%7C02%7Cantionette.r.mcclinton.civ%40army.mil%7C1a3e40b3604c49edf09008deaa07fa94%7Cfae6d70f954b481192b60530d6f84c43%7C0%7C0%7C639135148393991589%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=k7U3EEbHAGBeZ0FGJo0fS%2FikpvpWeOYTPWAlTkvitX8%3D&reserved=0 mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii.west@army.mil

5. Select all files for submission

6. Once files are populated select “Send Drop-off”

Instructions for Offerors without a CAC:

1. Submit a DoD SAFE Drop-Off Request to usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil for AFM-East proposals and usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil for AFM-West proposals No-Later-Than (NLT) 72 hours prior to the proposal submission deadline. Requests for drop-off codes only need to be submitted once. Requests must include at least two, but no more than three POC at the company. No generic company mailbox addresses will be allowed. The POCs will be the only recipients of the drop-off codes throughout the evaluation process.

2. A DoD SAFE Drop-Off Request Code will be sent to the identified POCs. Drop-off codes are valid for 14 days and one submission package.

Any portion of the proposal that is changed (due to negotiations/clarifications or proposal revisions) should be annotated and dated. Each volume shall be clearly labeled with its Title.

L.1.1.2. Alternate Submission Procedures. In the event the DOD SAFE is not operational, experiences technical difficulty, or the Offeror is temporarily unable to access or to use the system, the Offeror shall immediately notify the Procuring Contracting Officer (PCO) using the email address usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil for AFM-East proposals and usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil for AFM-West proposals. This notification must occur NLT two hours prior to the proposal submission deadline.

The alternate method for proposal submission is via email to:

usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil for AFM-East proposals and usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil for AFM-West proposals for which the file size is limited to 12MB total. The Offeror must obtain PCO approval to utilize the alternate submission method. Offerors are responsible for ensuring electronic copies are virus-free and shall run an anti-virus scan before submission. Submissions that are flagged for virus concerns will not be accepted by the system and will result in a delivery failure. Delivery failures not corrected by the submission deadlines will be the fault of the Offeror and will not be considered for award.

L.1.1.3. Non-Compliant Proposal Transmittal Methods. Proposal submitted by mail, by hand-delivery, or through proprietary third part File Transfer Protocol (FTP) sites will not be evaluated.

mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-east@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil mailto:usarmy.redstone.acc.mbx.acc-rsa-afm-iii-west@army.mil

L.1.2. Proposal Files. Failure to meet this requirement may result in a proposal being eliminated and not being evaluated by the Government.

L.1.2.1 Content Requirement. All information shall be confined 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, Summary Section, and the Narrative discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. No cost/price information shall be presented in any part of the past performance or technical proposal.

All information shall be presented in the appropriate volume shown below:

Volume Title Digital Copies Maximum Pages I Entry Gate Criteria 2 N/A II Technical 2 115* III Past Performance 2 25** IV Cost/Price 2 No page limit V Small Business Participation 2 25

VI

Solicitation, Offer and Award Documents, and Certifications / Representations

2 No page limit

Table 1 Volume Page Counts

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

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

*The Technical Volume maximum page count (115 pages) includes responses for the Comprehensive Management Plan (maximum 100 pages) and accompanying three scenarios (maximum 5 pages per scenario).

**The Past Performance volume shall consist of up to 25 pages for the prime, and up to 5 pages for each major subcontractor.

The page limit does not include the following documents:

• Past Performance Questionnaire Forms

• All letters (including but not limited to Letters of Commitment, Consent, Cure Notices and Show Cause letter)

• Table of Contents

• List of Abbreviations & Acronyms, and/or Figures

Attachment 0019

• Manning Tables

• Small Business commitment documentation

• Small Business Subcontracting Plan (for large business Offerors)

L.1.2.2. Format. Each paragraph should be single spaced and shall be separated by at least one blank line. A standard, 12-point minimum font size applies. Arial font is required. Tables and illustrations may use a reduced font size no less than 10-point and may be produced in landscape mode. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and solicitation number in the header and/or footer. A Table of Contents should be created using the Table of Contents feature in MS Word.

MS Word (doc) 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”

Note: Organizational diagram(s), detailed schedules, concept of operation graphics, and information required to support proposed prices (included in Volume IV – Cost/Price) may be submitted on page size 11 X 17.

L.1.2.3 File Packaging. Complete electronic volumes shall be submitted written in Microsoft (MS) Office formats readable by MS Word, MS Excel, MS PowerPoint, and/or Adobe Acrobat (PDF). Electronic copies shall not be password protected.

All the proposal files shall be compressed into a single ZIP file named “proposal.zip” using WinZip version 6.2 or later, or submitted as separate uploads in their native formats (e.g., .doc, .xls, .ppt). Files should be in read-only format, preferably as PDFs.

Each file name shall begin with a three-to-five-letter prefix indicating the offeror’s name.

For example, a submission from XYZ Corporation would include:

• XYZPastPerf.pdf

• XYZTech.pdf

• XYZPrice.pdf

• XYZSolicitation.pdf

Subcontractor submission shall identify both the subcontractor’s and the prime contractor’s name.

Visible Text Only: All proposal content must be presented as visible text. The inclusion of any concealed text is strictly prohibited. Concealed text includes but is not limited to:

• Micro-text (text with a font size below 8 pt)

• White text on a white background

• Text utilizing colors that render it indistinguishable from the background

• Text hidden within images or graphics

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

All cost/price proposal documents shall be submitted in accordance with (IAW) Section L.3.3 Cost/Price.

L.1.2.4 Prohibition of Concealed or Manipulated Text

L.1.2.4.1 Offerors shall submit proposals that are clear, concise, and readily readable.

To ensure accurate analysis by automated evaluation tools and maintain the integrity of the source selection process, the following restrictions apply:

L.1.2.4.2 Formatting Consistency: All text must apply uniform formatting throughout the proposal. Variations in font size, color, or style that the Government deems manipulate or obscures the readability of content are prohibited.

L.1.2.4.3 Compliance Verification: The Government may conduct technical verification to ensure compliance with these requirements. Proposals found to contain concealed or manipulated text will be considered non-compliant and may be rejected.

L.1.2.5 Use of Artificial Intelligence in (AI) tools in Proposal Evaluation

L.1.2.5.1 Use of AI tools in Support of Evaluations: The Government may employ AI as a tool to assist in the analysis and review of offeror proposals. AI tools may be used to support tasks such as summarizing proposal content, identifying compliance with request for solicitation requirements, and highlighting areas of potential strength, weakness, or risk.

L.1.2.5.2 Maintaining Inherently Governmental Functions: Notwithstanding the use of AI tools to support the evaluation process, all final evaluation judgements, including the assignment or assessment of adjectival ratings, best value determinations, and source selection decisions, will be made exclusively by duly appointed Government personnel.

The Government retains sole responsibility for all inherently governmental functions and will not delegate decision making authority to any AI tool.

L.1.2.5.3 Offeror Confidentiality and Data Protection: The AI tools utilized by the Government will be employed in a manner consistent with applicable regulations that

Attachment 0019 govern the protection of proprietary and source selection sensitive information. The AI tool will be an output-only system. Any generated report data is not saved. No proposal data will be transmitted to or processed by external, non-Government systems without appropriate safeguards and authorizations in place.

L.2 Entry Gate Criteria. To be eligible for evaluation of Factors 1,2,3 and 4, the Offeror must first demonstrate it meets the entry gate criteria within the five-year period immediately preceding the initial proposal submission date.

If proposing as a Joint Venture (JV) or Team, the Teaming or Joint Venture Agreement and Formal Commitment letters should be provided for Entry Gate to also be used during the Technical factor evaluation.

L.2.1 The Offeror shall provide the following documentation (copy of the contract, Performance Work Statement (PWS), appropriate certificates (example AS9110 Rev.C), and Government Flight Representative (GFR) approval letters (Flight Operation Procedures/Ground Operation Procedures (FOP/GOP))) in electronic format ONLY as standard of proof the entry gate criteria has been met:

• ENTRY GATE CRITERION 1. The Offeror must have GFR approved procedures performing and managing DoW flight and ground operations IAW DCMA Instruction 8210.1, AFI 10-220, NAVAIRSINST 3710.1, COMDTINST M13020.3, or AR 95-20, dated 5 APR 2017 or later.

• ENTRY GATE CRITERION 2. The Offeror must have experience within the timeframe specified in Section L.2 (as a prime or subcontractor) performing and managing field level rotary wing maintenance while certified AS 9110 Revision C.

The offeror shall provide current copies of its certificate as evidence.

• ENTRY GATE CRITERION 3. The Offeror must have experience within the timeframe specified in Section L.2 performing and managing United States Government (USG) or DoW aviation maintenance at multiple geographic locations, simultaneously, and dispersed greater than 500 miles apart.

• ENTRY GATE CRITERION 4. The Offeror must have experience within the timeframe specified in Section L.2 managing single or multiple USG or DoW contracts having aviation maintenance sites that include CONUS/OCONUS and OCONUS-Foreign locations.

L.3 Factors

L.3.1 Factor 1: Technical. The Offeror’s proposal shall include a Comprehensive Management Plan (CMP) for AFM III – East and West Aviation Maintenance services.

The Offeror’s Comprehensive Management Plan shall include:

~COMPREHENSIVE MANAGEMENT PLAN~

1. Organizational Approach (Program Management)

a. Organizational diagrams inclusive of management, execution levels, key functions (additional duties), locations and areas of coverage. Identify who is direct labor (Labor Category) hourly vs. Overhead (Management/Exempt).

The Offeror shall identify any program oversight, management, lead or critical positions and their qualifications as identified in Section 1 of RFP Attachment 0007, Qualifications and Job Descriptions and required in CDRL 0002, Contractor Personnel & Manning. RFP Attachment 0007, Section 1 identifies overhead type personnel as well as duties that need a designee, appointee or individual to be assigned.

b. Identify a proposed plan to mitigate the following three (3) risks associated with contract performance:

1. Surge to accommodate mission increase and decrease (both up and down);

2. Proper flow-down of procedures, written guidance, and enforcement of such;

3. Mission completion and notice to Government of safe de-obligation of financials.

c. Identify one additional risk and proposed mitigation strategy within the Offeror’s power to mitigate under this Aviation Maintenance contract.

2. Business Management

a. The approach for managing subcontractors, requirements flow-down, funding and CLIN management, cost accounting, cost estimating, cost control, timely vouchers, timely de-obligation of funds, cost overruns, and notification of ceiling price risks.

b. Map the requirements from EIA 748 (current version at time of proposal submission) Standard for Earned Value Management System (paragraphs 2.2-h, 2.4-b, 2.4-c, and 2.4-e) to the cost management approach based on objective evidence and provide a description of compliance.

c. The approach to systematically and continuously partner with the USG to improve program and reduce the annual cost of program management to the USG. Include in the response an approach to collective bargaining agreement negotiations and Service Contract Act changes or updates.

one contract for each major subcontractor PROPOSED ON THIS REQUIREMENT, along with the record of performance, during the past five years from the issue date of this RFP. A major subcontractor is identified as a member of the offeror’s overall team who is expected to perform fifteen (15) percent or more of the overall proposed effort.

Relevant efforts are defined as services/efforts that are the same as or similar to the effort (as compared to North American Industry Classification System (NAICS) code 488190 required by the RFP). 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. In addition, letters of commitment shall be included for all major subcontractors for their past performance to be considered.

L.3.2.1 Data concerning the Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. It shall be organized in the following sections.

L.3.2.1.1 Contract Descriptions

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

L.3.2.1.1.2 Government’s technical representative/COR and current email address, telephone and fax numbers.

L.3.2.1.1.3 Government contract administration activity and the Administrative Contracting Officer’s name, and current e-mail address, telephone and fax number.

L.3.2.1.1.4 Government contract administration activity’s Pre-Award Monitor’s name, and current e-mail address, telephone and fax numbers.

L.3.2.1.1.5 Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, include Delivery Order Numbers.

L.3.2.1.1.6 Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Material (T&M), etc.).