Section L_Attachment 2.pdf

PDF 128 KB Posted

Attached to
AFLCMC ON-SITE DEPOT SUPPORT (OSDS) FOR AFSOC C-130WEAPONS SYSTEMS and SUB-SYSTEMS
Solicitation number
FA8509-20-R-0007
Issued by

About this file

This performance work statement and solicitation describe requirements for on-site depot support contractor services. The contractor will provide depot-level maintenance, modification, fabrication, inspection, and technical evaluation services for all Air Force Special Operations Command C-130 aircraft, components, and support subsystems. The performance period is nine months with four additional one-year options. Services will be performed primarily at the 1st Special Operations Maintenance Group but may occur at other AFSOC bases or worldwide locations. The response deadline is April 6, 2020, with anticipated award by July 1, 2020 using lowest price technically acceptable procedures. This is a total small business set-aside reserved for small, small disadvantaged, women-owned, HubZone, veteran-owned, or 8(a) businesses. Foreign participation is prohibited.

View the file

Other files

Show all 19

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

SSP Attachment 2 Section L - Instructions, Conditions, and Notices to Offerors

Section L

L-900. INSTRUCTIONS TO OFFERORS

I. Proposal Format

A. General: The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation.

Offerors must follow the instructions contained herein. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the OSDS effort as the Government will review only one proposal per offeror. Proposals must be received by AFLCMC/WIUKA, 235 Byron Street, Suite 19A, Robins AFB 31098-1670, Attention: Bryan Canady, bryan.canady@us.af.mil and Victoria Willis, victoria.willis@us.af.mil, no later than the date and time specified in Block 8 on the face page of the RFP.

B. Communications: Exchanges of source selection information between Government and offerors will be controlled by the Contracting Officer through the Contracting Specialist. Email may be used to transmit such information, only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. Otherwise, source selection information will be transmitted via direct mailing or facsimile. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit your source selection information via encrypted email, you will need to contact the Buyer/Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange certificates used for encryption. To insure the process is working correctly, send a test encrypted message first (without including any source selection information). Otherwise, source selection information will be transmitted via direct mailing or DOD SAFE at https://safe.apps.mil/. When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

II. Volume Organization

A. General: Proposals shall be submitted to the Government in three (3) separate volumes as set forth below:

PAGE NUMBER

VOLUME LIMITS OF COPIES DESCRIPTION

I N/A 1 Electronic/ 1 Paper Completed RFP II 40 1 Electronic/ 1 Paper Written Technical Proposal III N/A 1 Electronic/ 1 Paper Cost/Price Proposal

*The Completed RFP, Technical and Cost/Price proposal information shall be submitted in written form (1 copy) and CD-R or DVD-R (write once/read only) (1 copy) that is “closed” so that no further writes can be made to the media. CD-R/W or DVD- R/W media types are not acceptable. Media must be virus scanned by the offeror prior to submitting to the Government.

In addition to the page limitations set forth above, proposal volumes shall comply with the following format:

1. The sealed package used to submit the proposal package must show the time and date specified for receipt. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume, i.e. I, II, III, etc.

Proposals shall be in the English language and all monies shall be proposed in United States dollars.

2. Print shall be no smaller than a font size of 12 and in Times New Roman. Paper size should be 8 1/2 x 11 inch, excluding any charts, graphs, drawings, diagrams, supporting illustrations, or spreadsheets, etc. Charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc. shall not be greater than 8 1/2” x 14”. Each volume within the proposal notebook shall be separately tabbed and identified. Margins shall be no smaller than 1 inch and each page within a volume shall be numbered consecutively. Elaborate formats, bindings, or color presentations are not desired or required. In order to verify the font size and margins utilized, the offeror shall provide an electronic copy of the technical proposal in Word format and searchable PDF format.

3. Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each.

Glossaries do not count against the page limitations for their respective volumes.

4. The page limitation for Volume II, Written Technical Proposal, is 40 pages. The page limitation includes any charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, etc., but excludes any cover page, table of contents or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitations shall not be read but shall be removed and either retained in the contract file without being considered in the evaluation, or, sent back to the offeror.

5. Page limitations may be placed on Evaluation Notices (ENs), if issued. The specified limits for EN responses will be identified in the letters forwarding the ENs to the offerors or on the EN form itself.

6. Each page containing proprietary information should be so marked.

7. Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

8. Submission of the initial proposal packages via electronic mail will not be accepted. Initial proposal packages shall either be DOD SAFE, mailed or hand-delivered. Offerors are cautioned that Warner Robins Air Logistics Complex has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

B. Volume I, Completed RFP

1. General: Volume I, Completed RFP shall consist of the completed and signed RFP, to include any amendments issued, with a cover letter delineating any exceptions taken to the RFP terms and conditions with accompanying rationale. However, offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible for award. Offerors shall ensure that all clauses and provisions that require “fill-in” information are appropriately completed, including the proposed prices associated with the contract line items in the Schedule of the

RFP.

C. Volume II, Written Technical Proposal

1. General: The technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. Work product attachments in the PWS shall be utilized as applicable to the task scenarios below. 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. The offeror will demonstrate task understanding and their ability to meet the PWS requirements. To merely paraphrase the specification, instructions or parts thereof is considered inadequate. Offerors shall assume the Government has no prior knowledge of their capabilities, work processes, and experience and will base its evaluation on the information presented in the offeror’s technical proposal.

2. Mission Essential Services: A Mission Essential Plan from the contractor has been deemed required for this effort. The contractor’s plan shall be IAW CDRL A00H, DI-MGMT-80004A, Mission Essential Plan, attached to the RFP. The contractor's written plan, including any prices/cost, shall be considered and evaluated in conjunction with the technical evaluation of offers.

3. Format and Specific Content: The following information shall be provided in the technical proposal and will be evaluated to assess technical acceptability (which includes the consideration of technical risk) in accordance with Section M-900, Evaluation Basis for Award. The offeror’s technical proposal will be evaluated based on the four subfactors to determine if the offeror provides a sound, compliant approach that meets the requirements of the solicitation and demonstrates a thorough knowledge and understanding of requirements as outlined in the Performance Work Statement (PWS).

For each subfactor, the offeror shall identify risks, if any, associated with the proposed approach and actions the offeror will be prepared to take to mitigate the identified risks. If no risks/mitigations are identified in the offeror’s proposal, it indicates the offeror does not consider there to be any risk associated with their proposed approach.

a. The technical proposal shall make no reference to price. Only one technical proposal from each offeror will be considered.

Each of the two scenarios will be utilized to evaluate two each of the four subfactors.

b. The technical proposal, being complete in every way, but not overly elaborate, shall describe the offerors capability of and proposed approach to performing the requirements for each of the scenarios identified with the subfactors below.

c. The technical proposal encompassing the two task scenarios and four subfactors should not exceed 40 pages total.

Scenario 1, UDLM Repair Fuselage Sloping Longeron, Fuselage Stations 737 through 1040 Replacement at Hurlburt Field, FL.

Nomenclature Part Number Sloping Longeron 342986-13

Defects:

During Isochronal Inspection workers identified left hand sloping longeron gouges beyond existing organizational repair limitations at approximately FS 771 on an MC-130H.

A Technical Assistance Request (TAR) was submitted to the System Program Office, Structural Engineering Section, AFLCMC/WLNEB, for assessment. Engineering directed that the left hand sloping longeron be replaced in accordance with TO 1C-130A-3 (DEPOT LEVEL REPAIRS) 53-199-00, AF (Optional Method). The longeron and all necessary hardware is procurable in DOD supply.

Subfactor One, UDLM Planning. Using UDLM Repair, Scenario 1 and PWS UDLM Planning attachments A and G (para 4.2.5 and 4.3.4.1), (No WFP required for this scenario) provide a technical proposal that includes a detailed narrative which should be in sufficient detail to convince the government engineering and technical management reviewers that your company understands the repair issues involved, and that your company has the experience and adequate depot maintenance and modification prowess to recommend repairs or methods which may be outside the scope of 1C-130A-3 (Structural Repair Instructions USAF Series ALL C-130 Aircraft). The narrative and completion of PWS Attachments A and G (para 4.2.5 and 4.3.4.1) should provide a logical work flow execution plan that maximizes quality, safety, and work efficiency (para 4.3.3). Identify and describe your assumptions and any risks associated with your approach. Include all applicable technical orders (figure and indexes), inspection, material and process specifications used for the repairs. Consider all aspects of making the aircraft safe and ready to accomplish the task. Identify any part-specific (or otherwise special) tooling and/or processes required. The narrative and PWS Attachment G should identify all items required to complete the task.

Subfactor Two, UDLM Execution Schedule Development. Using the PWS (para 4.3.4.1.7) and Attachments A and G, break the task down into discrete substeps with estimated execution hours for each substep, then apply manpower loading based on the requirements of each substep. Identify the labor skills found in the PWS Attachment A to identify your task team composition. Based on a 5-day per week, three shift (24-hour) work coverage, provide the government with a total direct labor hour estimate and a calendar day, start-to finish estimate, for task completion.

Scenario 2, Aircraft Modification Comply with Time Compliance Technical Orders (TCTO) 1C-130-2068 and 1C-130-2161 and subsequent TCTO changes on all AC-130W aircraft

OSDS CDMT has been tasked to complete subject TCTOs on AFSOC C-130s. The aircraft, an AC-130W, will be turned over to OSDS once the aircraft maintenance unit completes pre-modification systems operational checks. The aircraft will be turned over to OSDS on the flight line parking ramp and Eason Hangar, East Bay is available for completion of the TCTOs. In addition to the TCTOs, OSDS is responsible for all aircraft ground handling. Based on the TCTOs provided and Attachments A. and I. in the PWS provide your Work Flow Package for execution (para.4.3.4.1).

Since these TCTOs will be completed on all AC-130W aircraft, the offerors WFP will be reviewed and revised, as needed, then issued by the Aircraft Mechanic III, Technical Point of Contact (TPoC), for team execution on each subsequent AC-130W aircraft (para 4.3.4.1.4).

Subfactor Three, Work Flow Package (WFP) Development. The offeror shall fully develop a WFP IAW PWS (para 4.3.4.1) instructions and in the format found in PWS Attachment I. and provide a narrative to comply with

TCTOs on AC-130W aircraft. The WFP and narrative shall capture all aspects of the task including, team composition, ground handling, aircraft preparation for modification maintenance, documentation, and discrete work breakdown that supports a reasonable total man-hour and work-day estimate.

Subfactor Four, WFP Update/Control. The offeror shall provide a detailed narrative describing their processes and controls to ensure WFPs for repetitive tasks have a review, revision and issue control process IAW the PWS (para 4.3.4), their standard operating procedures (SOP) and their proposed local operating instruction to ensure an AS9001 compliant process is realized. This process should ensure new updates are incorporated into the master WFP document prior to release for the next scheduled modification. This should not be a restatement of government requirements from the PWS but describe your technical approach to realize quality WFPs for every task.

D. Volume III, Cost/Price Proposal

1. General: The Offeror shall complete and submit Attachment: OSDS Vol 3 Price Summary as its Volume III, Cost/Price Factor Proposal Submission:

OSDS Vol 3 Price Summary (Attachment to the RFP)

a. The contractor shall review, complete and submit the above attachment. Instructions on what information to include is included on the form. Do not adjust or alter any of the pre-populated information, such as labor categories, hours, CLINs, etc.

b. Proposed unit/CLIN prices shall be rounded to the nearest whole dollar. If any proposed unit/CLIN price does not meet this rounding requirement, the Government will round that price to the nearest whole dollar. The Government adjusted unit/CLIN price will become the offeror’s proposed amount.

c. Data beyond what is required by this instruction and form shall not be submitted. Under no circumstances shall this data be included within the technical volume.

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