Section L 8Feb10.docx

SECTION L

INFORMATION to OFFERORS (ITO) and INSTRUCTIONS for PROPOSAL PREPARATION

February 08, 2010

1.0 General Instructions

(a) This section 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 ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance-Based Work Statement (PWS), Contract Data Requirements List (CDRL), and Section B Schedule. Non-conformance with the instructions provided in the ITO may result in a technically unacceptable proposal evaluation and the Offeror may be ineligible for award.

(b) The proposal shall be clear, concise, and shall include sufficient detail for an effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements and objectives, but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements and objectives. Offeror shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience, and will base its evaluation on the information presented in the Offeror’s proposal.

(c) 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. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

(d) Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

(e) The proposal acceptance period is specified in Section A of the solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid until this date.

(f) 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.

(g) The Offeror does not need to submit past performance information in response to this RFP. The PCO will make a determination of acceptable past performance in accordance with FAR part 15.101-2(b)(1). The PCO will make a determination of contractor responsibility based on information obtained from government sources.

1.1 General Information

1.1.1. Point of Contact

The Procurement Contracting Officer and the Contract Specialist are the sole points of contact for this acquisition. Written requests for clarification may be sent by mail or email to the Contract Specialist at: OO-ALC/84 CBSG/PKB, ATTN: Ms. Mary Crowther, 6029 Wardleigh Road/Bldg 1207, Hill AFB, UT 84056-5838, Mary.Crowther@hill.af.mil, 801-586-1233. As an alternate, written requests may be sent to the PCO at: OO-ALC/84 CBSG/PKB, ATTN: Ms. Patricia L. Hunka, 6029 Wardleigh Road/Bldg 1207, Hill AFB, UT 84056-5838, Patricia.Hunka@hill.af.mil, 801-586-3360. All questions and answers shall be electronically mailed through the prime Offeror.

1.1.2 Pre-Proposal Conference

A pre-proposal conference will be scheduled at Hill Air Force Base, Utah approximately two weeks following solicitation release. Questions must be submitted to the PCO in advance via electronic mail. The names of all attendees must be submitted in writing to the PCO via electronic mail. Each Offeror is permitted to bring no more than 5 people, including sub-contractors.

1.1.3. Debriefings

The PCO 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. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offeror desiring debriefing must make a request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

1.1.4. 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 PCO 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.

1.1.5. Electronic Reference Documents

The solicitation and answers to solicitation questions can be found in FedBizOpps, the Government point of entry, at: https://www.fbo.gov/.

1.2 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). The volumes identified in the table should be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table. In addition to the “Hard Copies” requested in Table 1 below, please submit one (1) complete electronic copy of your entire proposal on CD IAW PWS Section 2.5.

Table 1 - Proposal Organization Table

Number

* One (1) complete electronic copy of your entire proposal is also required.

1.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and (for paper copies) will be returned to the Offeror as soon as practicable. Page limitations shall be placed on responses to Evaluation Notices (EN). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors. When both sides of a sheet display printed material, it shall be counted as 2 pages. Each page shall be counted except cover pages, tables of content, tabs, and glossaries.

1.2.2 Cost or Pricing Information

All cost or pricing information shall be addressed ONLY within the Cost and Pricing and Contract Documentation Volumes.

1.2.3 Classified Information

No classified information is required in your response to this RFP.

1.2.4 Indexing

Each volume shall contain a detailed table of contents delineating the subparagraphs within that volume. Tab indexing shall be used to identify sections. In addition, to the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

1.2.5 Glossary of Abbreviations and Acronyms

Submit one glossary within the Technical Volume of all abbreviations and acronyms used with an explanation for each. The glossary does not count against the page limitations.

1.3 Page Size and Format

(a) A page is defined as: 8.5 by 11 inches, white, standard office paper printed with 1.5 line spacing. The text size shall be no less than 12 point in Times New Roman typeface. 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 3/4 inch side margins. Pages shall be numbered sequentially by volume. These page format standards shall apply to responses to Evaluation Notices (ENs) in both electronic and hard copy format.

(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 8.5 by 11 inches in size. For tables, charts, graphs and figures, the text shall be no smaller than 8 point Arial typeface in both electronic and hard copy format.

1.4 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet should preface each volume, clearly marked as to volume number, title, copy number, solicitation identification and the Offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and 3.104-5, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

1.5 Electronic Submissions

The electronic copy shall be submitted on a single, virus free, ISO formatted read-only CD-ROM compatible with a standard Windows PC. File compression will not be used. Each disk will be clearly labeled. Paper and electronic copies must be identical in all respects. The electronic copy of the proposal shall be submitted in a format readable by Microsoft (MS) Office 2007 Suite of Applications (Word, Excel, and Power Point) as applicable. To facilitate evaluation and for ease of editing word documents, scanned documents and/or read only documents/files, especially PDF files are NOT acceptable for the Cost and Pricing Volume of the proposal. Please do not “read protect” submitted Excel worksheets. Provide all formulas (evident within the spreadsheet) and links used. Do not embed electronic files within other electronic files.

1.6 Distribution

The "original" proposal shall be so designated. All five copies (four printed and bound hard copies plus one electronic copy on Compact Disk as instructed in Paragraph 1.2) of the proposal shall be addressed and mailed to:

Place in the header and/or footer of each page of each volume the words "For Official Use Only" and "Source Selection Sensitive Information".

2.0 Volume I Executive Summary

In the executive summary volume, the Offeror shall provide the following information:

2.1 Narrative Summary

Provide a concise narrative summary of the entire proposal, including significant risks and a highlight of any key strengths or unique features, excluding cost/price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented in the Executive Summary shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

2.2 Table of Contents

Provide a master table of contents for the entire proposal and a cross reference matrix indicating, by ITO and Government PWS paragraph number, the corresponding paragraph that addresses the referenced item. The table of contents and cross reference matrix will not count against the page limitation for this volume.

3.0 Volume II - Technical Volume

3.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the factors and sub-factors defined in Section M (Evaluation Factors for Award). Using the instructions provided below, provide as specifically as possible a description of the actual administrative/organizational methodology you would use for accomplishing/satisfying these sub-factors.

3.1.1 Adequate Responses

(a) Cursory responses or content which merely reiterates or reformulates Section L, Section M or the PWS will not be considered as being responsive to the requirements of the solicitation. Certifications (which clearly demonstrate and support the Offeror’s claims) are essential. The absence of such evidence may result in a technically unacceptable proposal.

(b) The sub-factors listed are comprised of elements which are either a Critical Requirement - C (Offeror must meet all) or Non-Critical Requirement – NC (If Offeror does not meet, they must provide a plan to meet requirement within 30 days after contract award). Offeror shall provide in their proposal a plan for how they are going to meet Non-Critical Requirements and become acceptable to performing the AN/TMQ-53 program requirements.

3.2 Format and Specific Content

3.2.1 Factor 1 – Technical

The proposal shall address Offeror’s proposed approach to meeting the requirements of each of the following sub-factors according to the Performance-Based Work Statement (PWS).

3.2.1.1 Sub-Factor #1 - Technical Approach

Offeror shall address technical capabilities, corporate knowledge, and experience with the key elements listed: Levels of Certification, Systems Engineering- integration test plans, Technical Orders, Familiarization Training with the AN/TMQ-53 or similar Tactical, Deployable, Weather Systems (TDWS).

3.2.1.1.1 Levels of Certification (C): IAW PWS Sections 1.6 and 3.1 Offerors shall provide evidence of Level III SEI-CMMI, and ISO 9000/9001 certification.

3.2.1.1.2 Modification-Integration Test Plans Process – Systems Engineering (C): IAW PWS Paragraphs 3.2.7.4 – 3.2.7.17

(a) Offeror shall provide two (2) examples (one software, one hardware: both within last 5 years) of successful Integration Test Plans and Test Reports as part of Systems Engineering which evidences competence in performing modifications and integration into a system of similar size and complexity as a Tactical Deployable Weather System (TDWS) (e.g., AN/TMQ-53). The sample Integration Test Plans and Test Reports will not be included in the 200 count page limitation or formatting requirements of paragraphs 1.2 and 1.3 above.

(b) Offeror shall submit a proposed Systems Engineering process plan to investigate potential enhancements, upgrades, technical refresh, obsolete components, and diminished manufacturing source. The Offeror’s plan shall addresses each element in the Contractual Engineering Task (CET) detailing how they plan to apply their Systems Engineering process to a potential awardable task (CET); The CET involves modification and integration to the AN/TMQ-53 involving the Handheld Display Unit.

3.2.1.1.3 Technical Orders – (NC): IAW PWS Section 4.1, Paragraphs 4.1.1 – 4.1.8

(a) Offeror shall describe their proposed methodology for distribution of technical manuals and Time Compliance Technical Orders (TCTOs). Proposed methodology shall include packaging, shipping and handling, updates, integration and approval process. (NOTE: This requirement is for global locations; the proposed approach must address global distribution).

(b) Offeror shall provide one (1) electronic/CD copy of an existing, Offeror developed, technical manual. Note: This technical manual CD does not count against the page limitation in paragraph 1.2.

3.2.1.1.4 Computer Based Familiarization Materials (Training) (NC): IAW PWS Section 4.2, Paragraph 4.2.1

(a) Offeror shall describe their proposed methodology for distribution of computer based training (CBT). (NOTE: This requirement is for global locations; the proposed approach must address global distribution).

(b) Offeror shall provide one (1) electronic/DVD copy of a Computer Based Training (CBT). Note: This CBT DVD does not count against page limitation in paragraph 1.2.

3.2.1.2 Sub-Factor #2 - Management Approach

3.2.1.2.1 Transition Plan from Incumbent (C): IAW PWS Section 3.2.1 Offeror shall provide a Transition Plan to take ownership of the AN/TMQ-53 program from incumbent; transition shall not exceed 30 days. Offeror shall provide a detailed 30 day plan, to include methodology, staffing, continuation of system support, and proposed schedule required to perform all logistics support requirements. It shall capture the core activities (identified in the PWS) and processes necessary to implement the overall AN/TMQ-53 program. Transition plan package shall include detailed provisions for:

(a) Contractor Helpdesk. Offeror shall detail helpdesk support to users during transition.

(b) Training. Offeror shall detail provisions for scheduling and attendance at the required AFWA ARS Helpdesk training. Training is a two-day training, on-site at Offutt AFB, NE, required for all helpdesk employees.

(c) GFP/GFE/GFI. Offeror shall detail plans to incorporate receipt of the mockup systems, and assume responsibility for the globally fielded AN/TMQ-53 systems in accordance with the PWS and attachments to include all shipping, handling, and packaging requirements to the Offeror’s facility.

(d) Customs and Global Shipping. Offeror shall detail customs and global shipping required during transition. This will include all shipping, handling, and packaging required to support the globally fielded systems, and transfer responsibility for any in-transit assets.

(e) Active Military Operations Support. Offeror shall detail plans to support the Overseas Contingency Operations mission to include AF, Army, Joint Task Force, CENTAF, USAFE, PACAF, and ACC specific requirements during transition.

3.2.1.2.2 Integrated Master Plan – (C): IAW PWS Section 3.2.3, Paragraphs 3.2.3.1 – 3.2.3.8

(a) Offeror shall provide an Integrated Master Plan (IMP) which details the proposed processes and programs by which the contractor plans to effectively execute the tasks and requirements of this PWS. The plan shall include (as a minimum):

(b) Proposed Organization Chart

(c) Proposed methodology to retain qualified personnel

(d) Proposed plan to support program reviews at various locations

(e) Acknowledge requirement to provide agenda and minutes

(f) Acknowledge requirement to provide monthly status reports

(g) Provide plan to establish and sustain relationships with key original equipment vendors required for successful completion of this effort including; Vaisala (Cage: 63653), Raytheon (Cage: 072E5), General Dynamics (Cage: 3CX96), NAL Research (Cage: 1SZL2), and ARWest Communications (Cage: 4G8Z1).

(h) Offeror shall provide evidence of experience in integration, sustainment and logistics support within the past five years.

3.2.1.2.3 Configuration Management Plan – (C): IAW PWS Section 3.2.7, Paragraphs 3.2.7.15 – 3.2.7.17

(a) Offeror shall provide a Configuration Management Plan (CMP) to ensure configuration control of the system hardware, software and documentation.

(b) Offeror shall provide evidence of experience in configuration management within the past five years.

3.2.1.3 Sub-Factor #3 – Experience Approach.

3.2.1.3.1 Experience

Offeror shall evidence corporate knowledge and experience to implement the following services using core personnel. Core personnel are defined as a team of stable, permanent employees maintained to ensure continuity of the program. Offeror shall provide evidence of one year of continuous experience within the last 5 years in each of the following areas: (One year of continuous experience will exhibit continuity and fluency in the process)

(a) Logistics Maintenance Supply Management (C): IAW PWS Section 3.2.5 Paragraphs 3.2.5.1 – 3.2.5.8

1) Maintaining database to track part numbers

2) Managing and supplying spares

(b) Global Shipping/Customs (C): IAW PWS Section 3.2.5, Paragraphs 3.2.5.9 – 3.2.5.15

1) Experience shipping highly technical, fragile components to remote locations, such as forward operating bases.

2) Experience in compliance with all necessary Customs and State Department directives/procedures to prevent loss or delays of shipments to OCONUS sites.

(c) Contractor Maintenance Logistics Helpdesk Support (i.e. AFWA REMEDY Action Request System (ARS) Database) (C): IAW PWS Section 3.2.4, Paragraph 3.2.4.1 – 3.2.4.13 Experience in providing helpdesk support on a previous project.

(d) Support of Active Military Operations (C): IAW PWS entirety Experience in providing support during a military contingency

(e) Line Replaceable Unit (LRU) Repair (NC): IAW PWS Section 3.2.6, Paragraphs 3.2.6.1 – 3.2.6.8 Experience in managing a repair process whether repair is done in house or contracted to another source

(f) DoD Information Assurance Certification and Accreditation Process (DIACAP) (formerly Defense Information Technology Security Certification and Accreditation Process (DITSCAP)) (C): IAW PWS Section 3.2.7, Paragraph 3.2.7.20 – 3.2.7.34 Provide samples of unclassified Offeror generated/maintained DIACAP documentation. As a minimum, a current System Identification Profile (SIP), DIACAP Implementation Plan (DIP), Ports, Protocols and Services (PPS) Worksheet, DIACAP Scorecard, and IT Security Plan of Action and Milestones (POA&M). The sample DIACAP documentation will not be included in the 200 count page limitation or formatting requirements of paragraphs 1.2 and 1.3 above.

(g) Integration Software Support Requirements (C): IAW PWS Section 6, Table VI-4, Section 3.2.7, Paragraphs 3.2.7.13 and 3.2.7.19 Provide evidence of successful software integration efforts

3.2.1.4 Sub-Factor #4 - Quality Control Approach, Reliability and Maintainability (R/M) Plan (C): IAW PWS Section 3.1, Paragraphs 3.1.1 – 3.1.6

(a) Offeror shall provide a Reliability and Maintainability (R/M) plan, which demonstrates experience with system and sensor component performance and maintainability applicable to a TDWS program.

(b) Offeror shall evidence corporate knowledge and experience to implement the plan using core personnel. Offeror shall provide evidence of one year of continuous experience within the last 5 years.

(c) Offeror shall provide a proposed quality control plan.

3.2.2 Volume Organization

The Technical Volume shall contain the following proposal content sections and address the following evaluation Factor 1 – Technical and the corresponding sub-factors shown below:

Table of Contents * List of Tables and Drawings * Glossary (see Par. 2.2.5)* Four Sub-Factors:

Technical Approach Management Approach Experience Approach Quality Control Approach

* These sections of Volume II will not be counted as part of the 200 page limit.

4.0 Volume III Cost and Pricing Volume

4.1 Factor 2 – Cost and Pricing

Completion of the RFP, Section B Schedule (Volume IV), will represent a model contract.

4.1.1 Price Proposal (To facilitate analysis on adequate competition)

(a) All pricing information shall also be provided in Volume III. Insert proposed units in the attached Excel worksheet: TMOS Pricing Worksheet, Section B for each Contract Line Item Number (CLIN) for all ordering/pricing periods. All proposed FFP unit prices shall be rounded to the nearest whole dollar. The Cost Rates shall be rounded to two decimal places.

(b) Travel in support of the baseline shall be on a Cost-Reimbursable – No Fee CLIN and will not be included in the Total Evaluated Price.

(c) Modifications of TMOS Systems shall be on a Cost Plus Fixed Fee CLIN. Due to the unknown nature of the work to be performed under CLINs 0009, 1009, 2009, 3009, and 4009, Cost Rates will be proposed in the basic contract and will be evaluated by the Government. Cost Rates will be utilized on future proposal submissions for task orders when the requirements are known. Labor hours and material will be evaluated and negotiated at time of issuance of each Task/Delivery Order.

(d) Transition to an organic provider (CLINs 1012, 2012, 3012, and 4012) will not be evaluated as part of the proposal. The Government will negotiate this effort with the Awardee and will award this effort on a subsequent Task/Delivery Order.

4.1.2 Price Reasonableness, Balance, and Cost Realism on Cost Rates

(a) In accordance with FAR 15.403-1(b) ,15.403-3(a), and 15.404-1(d) information other than cost or pricing data is required to support price reasonableness and realism of Offerors’ negotiated cost and price. Information shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the contracting office determines that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the Offeror shall be required to submit certified cost and pricing data.

(b) Compliance with these cost/price instructions is mandatory and failure to comply may result in rejection of the Offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness and realism. The burden of proof for credibility of proposed costs and prices rests with the Offeror.

4.1.3 Estimating Techniques and Methods

When responding to the Cost and Pricing Volume requirements in the solicitation, the Offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships (CERs), commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the work breakdown structure (WBS).

4.2 Volume Organization

The Cost and Pricing volume shall be logically organized in the contractor’s format and include the following:

(a) Provide a Table of Contents. Provide abbreviations and acronyms used in the cost/price volume.

(b) Provide explanation and rationale for all significant assumptions, scope limitations and/or qualifications of the price proposal. Proposal validity period shall be explained.

(c) Complete the attached Excel Worksheet, “TMOS Pricing Worksheet.xlsx”. This includes Section B and four attachments. See this worksheet for additional instructions.

(d) Accounting/Purchasing/Estimating Systems - Indicate whether you have Government approval, if so, provide evidence of such approval. Also, identify any deviations from your standard procedures in preparing this proposal.

(e) It will be necessary to provide detailed computations for your proposed Cost Rates. This will include cost breakdowns showing how the Cost Rates were developed. Provide substantiating rationale.

5.0 Volume IV - Contract Documentation

5.1 Model Contract/Representations and Certifications

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

5.1.1 Section A - Solicitation/Contract Form

Completion of blocks 13 and 15 and signature and date for block 27 of the SF 1447. Signature by the Offeror on the SF1447 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes.

5.1.2 Section B - Supplies or Services and Costs and Pricing

All pricing information shall be addressed in Section B Schedule of the RFP. Information shall be limited to Contract Line Item Number, (CLIN), Sub-CLIN or ELIN level pricing, including unit and extended pricing as specified in Section B.

5.1.3 Section F – Deliveries or Performance

Alternate delivery schedules are not acceptable as this is an Indefinite Delivery/Indefinite Quantity award. Failure to meet the solicitation’s required delivery will result in ineligibility for award. Delivery requirements shall be addressed in each resulting Task/Delivery order placed under the resulting contract.

5.1.4 Section K - Representations, Certifications, and other Statements of Offerors Completed representations, certifications, acknowledgments, and statements from Offeror.

5.2 Exceptions to Terms and Conditions

Offerors are required to meet all solicitation requirements such as, terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or sub-factors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 5.2.

Table 5.2 - Solicitation Exceptions Solicitation Document

Portion Rationale

SPEC

RFP, Section L, etc.

Applicable Page and Paragraph Numbers

5.3 Other Information Required

5.3.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

5.3.2 Government Offices

Provide the mailing address, telephone numbers, fax numbers, and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name, telephone and fax number for the Administrative Contracting Officer (ACO).

5.3.3 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county, and facility code; CAGE code; DUNS code; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

5.3.4 Attachments to the Solicitation

The Offeror shall provide the following as attachments to the solicitation:

5.3.4.1 Subcontracting Plan - Participation of Small Businesses (SB), Historically Black Colleges and Universities, or Minority Institutions (HBCU/MI) If the Offeror is other than a small business, the Offeror shall submit a Small Business Subcontracting Plan in accordance with FAR 52.219-9 that also identifies and specifies the extent of Offeror's commitment to the participation of small businesses (SB), historically black colleges or universities (HBCU), and minority institutions (MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of your approved Master Plan. In the event the Offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the Offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI. In accordance with AFFARs 5319.704, Subcontracting Plan Requirements, (a)(1) Small Business subcontracting goals will be expressed in terms of percent of contract value in addition to percent of subcontracted amount.

5.3.4.2 GFP/GFE/GFI and no Base Support Requirements

The contractor will be provided two (2) complete AN/TMQ-53 Tactical Deployable Weather Systems (GFP/E) for system mockups to aid technical personnel in troubleshooting, testing and problem resolution outlined in the PWS. Additional GFP/GFE/GFI included are two hundred ninety seven (297) AN/TMQ-53 globally fielded systems (PWS Attachment VI-1), Spares (PWS Attachment VI-2), AN/TMQ-53 Software (PWS Attachment VI-5), AN/TMQ-53 Technical Orders, and all AN/TMQ-53 assets in transit at time of award.

Base support is not authorized for use under this requirement.

5.3.4.3 Associate Contractor Agreements

Associate Contractor Agreements are not applicable as part of this solicitation.

5.3.4.4 Professional Employee Compensation Plan

Offeror shall submit a Professional Employee Compensation Plan in accordance with FAR 52.222-46. The plan shall include, but not be limited to:

· Salaries

· Fringe benefits to include insurance, vacation time, holidays, etc.

Specify the percentage of the proposed fringe benefits to the proposed annual salary.

· Supporting documentation for numbers 1 and 2 listed above. Include data such as recognized national and regional compensation surveys and studies of professional, public, and private organizations, used in establishing the proposed total compensation structure.

· Any other information deemed necessary.

L-13 (of 14)