ATLAS_3_-_Section_L.pdf

PDF 433 KB Posted Nov 21, 2017

Attached to: ATLAS 3 RFP Federal contract opportunity
Solicitation number: FA8203-18-R-0002
Issued by: Department of the Air Force Materiel Command Lifecycle Management Center Hill Air Force Base

About this file

From the source

ATLAS 3 Section L: Proposal Preparation and Submission Instructions

View the file

Other files for this federal contract opportunity

Other files attached to ATLAS 3 RFP, newest first.
File	Type	Posted
FA8203-18-R-0002_ATLAS_3Ref_Reports.pdf	PDF	Dec 13, 2017
FA8119-16-D-0008_Boeing_Rights_Guard_Agreement_Sign_Last_Two_Pages.pdf	PDF	Dec 13, 2017
FA8203-18-R-0002_ATLAS_3_Drawings.pdf	PDF	Dec 13, 2017
FA8203-18-R-0002_ATLAS_3_TDP_Docs.pdf	PDF	Dec 13, 2017
ATLAS_3_-_KC-135_MLG_USS_Redesign_SOO_Amendment_01.pdf	PDF	Dec 5, 2017
ATLAS_3_-_CDRLS.pdf	PDF	Nov 21, 2017
ATLAS_3_-_KC-135_MLG_USS_Redesign_SOO.pdf	PDF	Nov 21, 2017
FA820318R0002-ATLAS_3_RFP.pdf	PDF	Nov 21, 2017
ATLAS_3_-_PWS.pdf	PDF	Nov 21, 2017
ATLAS_3-Section_M.pdf	PDF	Nov 21, 2017
FA8203-18-R-0002_ATLAS_3_TDP_Docs.pdf	PDF	Nov 21, 2017

Show all 11

On GovTribe

Work with this file on GovTribe

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

ATLAS 3

Section L’s - Proposal Preparation and Submission Instructions

Section Content:

1.0 - Program Structure Objectives

2.0 - General Instructions

3.0 - Volume I, Contract Documentation

4.0 - Volume II, Technical

5.0 - Volume III, Past Performance

6.0 - Volume IV, Price Proposal

7.0 - Required Attachments

1.0. Program Structure and Objectives

ATLAS’s program structure and objectives can be discovered in the Performance Work Statement (PWS) para. 1.0 – 1.2.

2.0. General Instructions

(a) This section of the Instructions provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information requested by the Instructions and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Request for Proposal (RFP), CDRL’s, SOO (for the initial task order) and PWS. Offerors are advised that submissions that DO NOT conform to the instructions provided herein may result in a proposal evaluation score of unacceptable, or exclusion from further consideration.

(b) The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. IAW section L, para 2.2.2, Contractor shall provide cross-reference matrices to facilitate traceability. The proposal should not simply rephrase or restate the Government's requirements, but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Air Force has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the offeror's proposal.

(c) Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

(d) The proposal acceptance period is specified in Section A (SF 1447, blk. 11) of the Solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

(e) In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

(f) Questions regarding this solicitation should be e-mailed to Christian.Barwick@us.af.mil and Savard.Boone.1@us.af.mil.

2.1. General Information

2.1.1 Contact Information: Christian Barwick is the main POC for this acquisition and the Contracting Officer (CO).

Capt Savard Boone is the alternate POC. Any questions or concerns you may have should first be addressed in writing to the main POC at (748 SCMG, ATTN: Christian Barwick, 6050 Gum Lane, Bldg 1215, Hill AFB, UT 84056- 5820), or e-mailed to Christian.Barwick@us.af.mil; if he cannot be reached the alternate POC should then be contacted at (748 SCMG, ATTN: Capt Savard Boone, 6050 Gum Lane, Bldg 1215, Hill AFB, UT 84056-5820), or e-mailed to Savard.Boone.1@us.af.mil; unless otherwise directed in the applicable provision. Responses will be publicized unless notified that the information is contractor sensitive.

2.1.2. Debriefings: The CO will promptly notify offerors of any decision to exclude them from the competitive range;

whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection mailto:Christian.Barwick@us.af.mil mailto:Savard.Boone.1@us.af.mil mailto:Christian.Barwick@us.af.mil mailto:Savard.Boone.1@us.af.mil http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR15.DOC#b15505 decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable. Debriefings will utilize a written format, rather than being conducted in person.

2.1.3. Discrepancies: If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the Contracting Officer 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. This reservation includes matters of additional or substitute pages of the initial proposal.

2.1.4. Electronic Reference Documents: All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at (http://www.fedbizopps.gov). Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.5. Oral Presentations: Oral presentations will not be allowed.

2.1.6. Communications: Exchanges of source selection information between the Air Force and offerors will be controlled by the Contracting Officer. Email may be used to transmit such information to offerors and should include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

2.2. Proposal Organization

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2) below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The contents of each proposal volume are described in this Section (L) and summarized in the table below:

Table 2.2 - Proposal Organization

VOLUME TITLE COPIES PAGE LIMIT

I Contract Documentation

(a) SF 1447 Reps & Certs

(b) Small Business Sub-contracting Plan

1 E-copy

(a) Unlimited

(b) 4 pages

Technical/Technical Risk – Factor One

(a) Technical Capabilities

(b) KC-135 MLG Upper Side Brace Redesign Task

(a) 25 pages

(b) 25 pages

III Past Performance – Factor Two

(a) Project Submissions

(a) 1-pg./project

Price – Factor Three

(a) Price Schedule

(a) 2 pages

(b) 3 pages

2.2.1. Page Limitations: Page limitations are identified in Table 2.2—Proposal Organization and explained below.

Offerors are advised that the limitations shall be treated as maximums. If exceeded, the excess pages will not be evaluated and they will be discarded, not returned to the contractor. If discussions are held page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except cover/title pages, cross-reference matrices, tables of contents, tabbed dividers, acronym lists and glossaries unless other exceptions are stated within these instructions.

2.2.1.1 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be typed using single spacing , except for the reproduced sections of the solicitation document, the text size http://www.fedbizopps.gov/ http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/Far02.doc#T2101 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR03.DOC#b3104 shall be no less than 12-point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 1-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs.

(b) Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and each surface of a foldout shall be counted as a separate page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 point font

2.2.2. Cross Referencing: Each Volume (I – IV) of a proposal addresses a specific factor, and therefore shall be submitted, evaluated, and considered based solely on the information contained therein (i.e. each volume “stands alone”). Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. The offeror shall provide a cross reference matrix/table/note (e.g., exhibited below) in a clear and similar format to the exhibit shown below. The effect of the cross reference is to draw (at the beginning of a Section) the evaluators’ attention to the criteria the Offeror’s addressing, indicating the proposal information as it relates to Sections L and M, PWS, KC-135 TO, CLIN numbers, and CDRL references.

Section L Section M Proposal PWS SOW CLIN CDRL

2 sub factor 1 Para. X.x. Para. X.x. Para. X.x. Para. X.x. 0001 A001

2.2.3. Indexing: Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

2.2.4. Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

2.2.5. Labeling: A cover sheet should be included with each volume, clearly marked as to volume number, title, solicitation identification, and the offeror's name. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.2.6. Each page within a section shall be numbered consecutively.

2.2.7. Each page that contains proprietary information shall be marked inside the header and footer of each page with the following statement “SOURCE SELECTION INFORMATION (FAR 3.104-4 and 2.101)”

2.3. Electronic Offers: The electronic copies of proposal Volumes I, II, III, shall be submitted in a format readable by Adobe’s Portable Document Format (PDF) Version 11. Electronic copies of Volume IV shall be submitted using Microsoft’s Excel format.

2.4. Distribution: Proposals shall be delivered to:

Christian.Barwick@us.af.mil

Savard.Boone.1@us.af.mil

Include Solicitation Number FA8203-17-R-0012 on the address label.

3.0 Volume I. – Contract Documentation

3.0.1 The purpose of this volume is to provide information to the Air Force for preparing the contract document and supporting file.

VOLUME TITLE COPIES PAGE LIMIT

http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR52.215.doc#b522151 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/af_afmc/far/FAR03.DOC#b31044 mailto:Christian.Barwick@us.af.mil mailto:Savard.Boone.1@us.af.mil

I Contract Documentation

(a) SF 1447/ R&C

(b) Small Business Sub-contracting Plan

(a) Unlimited

(b) 4 pages

3.1 Solicitation and Representation/Certifications:

The offeror's proposal documentation volume shall include (a) a signed copy of the Solicitation, and Sections A through K;

3.1.1. Section A: Offerors shall complete blocks 11, 13, 15, & 27. Offerors shall complete price proposal in accordance with Sections J, L, & M; therefore, blocks 21 & 22 don’t apply to this Solicitation. Signature by the offeror on SF 1447, blk. 27 constitutes an offer, which the Air Force may accept.

3.1.2. Section B: Do not complete Section B; pricing information is submitted in the Pricing Volume.

3.1.3. Section C: N/a

3.1.4. Section E: N/a

3.1.5. Section F: Delivery schedules will be identified on subsequent orders. However, for KC-135 MLG Upper Side Brace Redesign the delivery schedule identified in the SOW’s Master Schedule (and/or RFOP) will be utilized.

3.1.6. Section G: N/a.

3.1.7. Section H: N/a.

3.1.8. Section I: N/a.

3.1.9. Section K: Complete representations, certifications, acknowledgments, and statements. Note: if the Offeror has previously registered with the Online Representations and Certifications (ORCA) database, a referral to a current record is sufficient.

3.2 Sub-contracting Plan

3.2.1. All offerors other than Small Business shall submit a complete subcontracting plan in accordance with FAR 19.7, 52.219-09, DFARS 252.219-7003 and the following instructions. If the offeror has an approved master subcontracting plan (DFARS 219.702), it shall submit an addendum with its proposal covering any additional information required by this solicitation. The addendum will be incorporated into any resulting contract along with incorporation by reference of the master or comprehensive plan. No plan is required for those that are part of the Comprehensive Subcontracting Plan Test Program. The enhanced small business requirement is not intended to obtain two plans from offerors, only a single enhanced plan. Note: the 4-page limit applies to ATLAS specific sub-contracting plan or addendums that may be offered. In the event an offeror has an “approved master subcontracting plan”, it can be submitted without affecting the page limit for the applicable section.

3.2.2. Prime contractors are to assign a NAICS code to each subcontract, based on the nature of the work being subcontracted, using the 2007 North American Industrial Classification System coding manual and the footnotes in 13 CFR 121. Be advised that the contracting officer established NAICS 541330 for the basic contract. Subcontracted work similar to the basic contract should use NAICS 541330. While offerors are not bound to use the same NAICS code for all subcontracted effort that is similar in nature to the NAICS code assigned for the prime contract, deviations must clearly fit the NAICS description chosen.

4.0 Volume II. – TECHNICAL

4.0.1 The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important.

The offeror’s responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, the offeror will provide as specifically as possible the actual methodology they would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

Technical– Factor One

Technical Subfactors

(a) Technical Capabilities

1 E-copies

(a) 25 pages

(b) 25 pages

4.1. Factor 1 –Technical / Technical Risk (Volume II, a & b)

In the technical volume, address your technical solution to the Government’s minimum performance or capability requirements of each technical subfactor. Address any Technical Risk associated with the aspects of your proposed technical approach considered to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance.

Classify each risk in accordance with risk ratings outlined in Table M2 (refer to section M). Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (for example: SOW or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic "work-around" or risk mitigators for identified risks that potentially eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

4.1.1. Sub-factor 1 “Technical Capabilities

4.1.1.1. Submit for consideration Technical Capabilities (limit 25 pages) that address: (a) the requirements identified in ATLAS’s Performance Work Statement (PWS) Para 3.2, and Tables 1 and 2, identifying the Offeror’s capability to satisfy the Labor Category Qualifications to accomplish the work identified in PWS Paragraphs 1.1. and 1.2; and (2) the Offeror’s teaming arrangements to achieve ATLAS’s objectives. In this section, also address associated program risks and quality standards; ISO 9001-2000 or equivalent.

4.1.2. Sub-factor 2 “KC-135 MLG Upper Side Brace Redesign Statement of Work (SOW)” Task

4.1.2.1. Submit the proposed technical solution (limit 25 pages) to address the problems identified in the KC-135 MLG Upper Side Brace Redesign Statement of Objectives.

4.1.2.2. Offeror’s responses shall address: (a) Proposed solution; (b) Deliverables; (c) Implementation approach; (d) Key resources; (e) Risk; (f) Integrated Master Schedule. (Refer also to ATLAS PWS para. 1.4.)

4.1.2.3 Offerors are advised to submit reasonable and achievable responses to the SOO since the Air Force reserves the right to accept a particular Offeror’s SOW and KC-135 Task Pricing Schedule as a basis to issue a Task Order without further discussion. For award criteria for the Task Order: KC-135 MLG Upper Side Brace Redesign see Section M, para 1.1.2.

4.1.2.4 Offeror’s Integrated Master Schedule shall not be included in the 25 page limit.

4.1.3. The summary exhibit (below) is provided to aid the offeror in preparing its Technical Volume.

Technical Subfactor

Area of Interest PWS Citation Explanation

One

Two

(a) Technical Capabilities

KC-135 MLG Upper Side Brace Redesign

Para. 3.2 Tables 1 & 2 Para. 1.1

Para. 1.4

The offeror’s capabilities, consistent with the staffing standard, shall be in the landing gear categories identified in para. 1.1

Submit a SOW for the Air Force’s consideration utilizing PWS Para. 1.4, solicitation SOO, and RFOP

5.0 Volume III. – Past Performance

III Past Performance – Factor Two

(a) Project Submissions

(a) 1-pg./project

5.0.1. Offerors shall submit (utilizing Section L, Attachment - ONE—Project Submissions) past performance information (one-page per project) for each of the categories described in the PWS:

1. Landing Gear Structures – Integration, concept, design, analysis, manufacture, qualification, airworthiness certification, implementation, and sustainment

2. Rolling Stock (Wheels, Brakes, and Tires) – Integration, design, qualification, airworthiness certification, implementation, and sustainment

3. Antiskid – Integration, design, qualification, Hardware-In-The-Loop simulation, antiskid software, hydraulic components, and implementation

4. Materials - Materials development/characterization, technology insertion, and manufacturing technology

5. Processes – Repair and overhaul concepts, process improvement, technology insertion, and manufacturing technology

6. Business/Data – Program management, configuration management, technical data revision, maintenance strategies, feasibility analysis, information systems, and logistics planning/provisioning

All offerors will receive a rating for the each of the categories listed above. In addition to the submitted information the Government reserves the right to use both the past performance information provided by the offeror and information obtained from any other sources available to the Government, to include, but not limited to, the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), or other databases; the Defense Contract Management Agency; and interviews with Program Managers, Contracting Officers, and Fee Determining Officials, and commercial sources. The evaluation of the offeror's past performance information shall consider recency, relevancy (similarity in technical capability) and overall performance.

Past Performance evaluations will occur on an annual basis following the initial award if new submittals are received from the awardee or if information previously submitted falls out of recency. The Contracting Officer will remove past performance information that has fallen out of recency and a new rating will be applied using the remaining information and that rating will be communicated to the awardee. Awardees will also have the opportunity to submit up-to-date past performance information on an annual basis which will be 365 days after the basic contract award date. If an awardee has determined that their past performance has changed they can choose to submit new information during the annual submittal process. Awardees are cautioned that the past performance information submitted has the potential to increase or decrease the initial rating received for each specific category. Also, for any given task order the Government may elect to request task order-specific past performance, if desired.

5.1 Projects

5.1.1. Information (projects) submitted in response to Section L, Para. 5.0.1. must be for those efforts that the Offeror considers most relevant to demonstrating its ability to perform the proposed effort. Submit projects utilizing Section L, Attachment - ONE—Project Submissions Form. Responses should be succinct, go directly to objective, problems encountered/corrective actions, relevance, and limited to the space provided. For a description of the characteristics or aspects the Government will consider in determining recency and relevancy, refer to Section M.

5.1.2. Complete Blocks on the Project Submissions Form as indicated. Modify Area “B” such that it’s clear which category a project is submitted for, and if the offeror (your firm) performed as a prime or sub-contractor for the project.

If a project submission represents work performed on a non-government contract, complete the Form (in area C) utilizing the commercial “equivalent” to the extent possible. If a project was completed under a “multiple-award contract”, as outlined in FAR 16.504, use one submission to demonstrate its relevance and separate submission(s) (noting both the parent award and TO in “C2”) to demonstrate a TO’s relevance (note that different “multiple-awards” may be submitted separately). Otherwise, complete the “(fill-in)” blocks with the appropriate response (offerors may chose to delete the “(fill-in)” prompt).

5.1.3. Offerors representing large business (reference Small Business Administration’s Small Business Size Standards by NAICS publication) concerns shall complete “Block E” on the Project Submissions Form for those projects where a Small Business Subcontracting Plans (SBSP) have been required. If the Offeror is a small business or if no SBSP was required indicate “no.”

5.2 Specific Content

5.2.1 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.

6.0 Volume IV. – Price Proposal

Price – Factor Three

(a) Price Schedule

(b) KC-135 Task Order Pricing Schedule

1 E-copies

(a) 2 pages

(b) 3 pages

6.1. General Information

6.1.1. The primary purpose of the price proposal is to provide the Air Force with prices and labor rates so it can perform analysis (in accordance with FAR—Part 15) and consider price reasonableness and balance. Compliance with these instructions is mandatory and failure to comply will result in an unacceptable rating. Unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness and balance. The burden of proof for credibility of proposed costs/prices rests with the offeror.

6.1.2. All pricing information shall be addressed ONLY in the Price Proposal Volume. Cost trade-off information, (e.g., material kinds and quantities) may be used in other volumes (e.g. KC-135 MLG Upper Side Brace Redesign SOW, “key resources”) only as appropriate for presenting rationale for alternatives for trade-off decisions.

6.2. Contract Labor Hour Rates

6.2.1. Offerors are required to submit Fixed Price & Cost labor rates using the Labor Hour Pricing worksheet. Rates included on the Labor Hour Pricing worksheet will be utilized throughout the term of the contract. The Fixed Price rates represent an all inclusive rate (all possible costs, overhead, G&A, profit, et cetera) excluding direct material and travel costs associated with manufacturing and testing material (e.g. a prototype) for the years identified. For the purposes of evaluation, offerors shall assume that no other labor categories exist outside of the labor categories on the Labor Hour Pricing worksheet. Offerors are cautioned that prices submitted in some other method can not be evaluated or considered; and again reminded that incomplete, or amended pricing will result in an unacceptable rating.

6.3. KC-135 Task Order Pricing Schedule

6.3.1. Offerors are advised to submit KC-135 task order price proposal based on the KC-135 SOO sufficient to accomplish the work described in the Offeror’s KC-135 MLG Upper Side Brace Redesign SOW. The Price Proposal shall include the total prices for each CLIN. The offeror shall propose labor categories and rates in alignment with the Labor Hour Pricing Worksheet. The offeror’s price proposal will be utilized for price evaluation purposes (refer Section M) and may represent the basis upon which the Air Force will issue a Task Order. Pricing shall be in accordance with the CLINs outlined in the attached “Pricing Table KC-135 Task”, Attachment 4.

6.3.2. Recognize that an offeror’s KC-135 MLG Upper Side Brace Redesign SOW and KC-135 Task Order Pricing Proposal constitute a response upon which the Air Force may unilaterally issue, without further discussion, a Task Order; therefore, the offerors are advised to submit their most competitive approach.

7.0. Section L –Attachments

Section L, Attachment – ONE, Project Submissions

Section L, Attachment - ONE: Project Submissions

Provide the information requested in this attachment for each contract/program (limit of four) being described. Provide frank, concise comments regarding the contracts you identify. The “(fill in)” text may be deleted; otherwise limit responses to the space provided.

A. Offeror Information

1. Offeror Name: (fill in)

2. Cage Code: (fill in) 3. DUNS: (fill in)

4. Offeror’s ATLAS Rep.: (fill in name) 5. Rep.’s email: (fill in) 6. Rep.’s phone: (fill in)

B. Project category*

1. Title of Program: (fill in)

C. Project Contract Specifics**

1. Contracting Agency: (fill in) 2. Contract #: (fill in)

3. Contract Type: (fill in)

4. Period of Per.: (fill in)

5. Org. Contract Value (exclude un-ex. options): (fill in)

6. Current Contract Value (exclude un-ex. options) (explain if diff. from “C5”): (fill in)

7. Program Manager (COR) Contact Info. 7a. Name: (fill in)

7b. Telephone: (fill in)

7c. Email: (fill in)

8. Contracting Officer (PCO or ACO) Contact Info.

8a. Name: (fill in)

8b. Telephone: (fill in)

8c. Email: (fill in)

9. Alternate (often COs & PMs re-locate;

provide an org. POC who can be contacted w/ certainty, in the event the CO, or PM cannot be contacted.)

9a. Name: (fill in)

9b. Telephone: (fill in)

9c. Email: (fill in)

D. Project Description***

1. Project Narrative (objectives, relationship to ATLAS’s, problems encountered/corrective actions.): (fill in)

2. Size. (ATLAS task orders historically range from $100K up to $15M.)

2a. (fill in)

3. Scope. (ATLAS’s scope includes engineering improvements for AF landing gear assets in six categories, PWS Para. 1.0.

& 1.1.)

3a. (fill in)

E. Project Sub-contracting Plan (if applicable)

1. Plan required (FAR 52.219-9): (Y/n) (If yes, complete data for two most recent periods)

1a. Goal ($/%): (fill in) 1b. Actual (S/%): (fill in)

2a. Goal ($/%): (fill in) 2b. Actual (S/%): (fill in)

3. If actual is less than goals explain: (fill in)

* I.e., Structures, Rolling Stock, Antiskid, etc.

** If project’s a Multiple Award KT use “parent” KT as one project & note KT# and TO# for separate TO submissions.

*** Portray the relevance of your project to ATLAS’s objectives, size, and scope.

Section L, Attachment – TWO, Pricing Table Cost

Labor