SECTION_L_MTE_450_VPS_AMENDMENT_02.pdf

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1.0 PROGRAM STRUCTURE AND OBJECTIVES

1.0.1 The Governement intends to award a contract for an adjustable (200-450V), regulated power supply, with over-voltage over-current protection along; 1 first article, 21 power supplies, and the associated data package. As presently configured, the MTE is vulnerable to major system damage resulting from AC line voltage fluctuations. The new power supplies will correct this problem.

1.0.2 This requirement is being set aside for Small Businesses. The PCO has determined there is a high probability of adequate price competition in this acquistion. Upon examination of the intital offers, the PCO will review this determination and if, in the PCO’s opinion, adequate price competition exists, no additional cost information will be requested. However, if at any time during this competition, the PCO deteremines that adequate price competition no longer exists, offers may be required to submit information to the extent necessary for the PCO to determine the reasonableness and affordability of the price.

2.0 GENERAL INSTRUCTIONS

2.0.1 The offeror's proposal must include all data and information requested by this Instructions to Offerors (ITO) and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Statement of Work (SOW), System

Specification, and Contract Data Requirements List (CDRL). Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

2.0.2 The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. 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. Offerors shall assume that the

Government has no prior knowledge of their facilities or experience and will base its evaluation on the information presented in the offeror's proposal.

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

2.0.4 The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

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

2.1 General Information

2.1.1. Point of Contact

The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition.

Electronic exhanges of source selection information between the Government and offerors will be controlled by the PCO. Source selection information may also be transmitted via the mail system or in person. The PCO may determine to conduct telephone communications when deemed appropriate by the Government. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the address below:

AFMC/PZZKC

Wade Pilcher

6039 Wardleigh Ave, Bldg 1206

Hill AFB UT 84056

E-mail: wade.pilcher@us.af.mil

801-586-1229

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

Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection 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. 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. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

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 PCO in writing with supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business

Opportunities (FedBizOpps) website at https://www.fbo.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.2 Proposal Organization/Number of Copies/Page Limits

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 in Table 2.2.

The attachments identified in the table shall 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 below:

Table 2.2 - Proposal Organization

VOLUME ITO Paragraph

Number

VOLUME TITLE Hard

COPIES /

Disk

Copies

PAGE LIMIT

I Price / Contract

Documentation Proposal

3/2 UNLIMITED

II Technical Proposal 3/2 30

2.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 excess paper copies will be returned to the offeror as soon as practicable. 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 the following: cover pages, tables of contents, glossaries, charts, tables, and matricies.

2.2.2 Page Size and Format

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 single spaced. Except for the reproduced sections of the solicitation document, the text font shall be Times New Roman and the text size 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 ¾-inch side margins. Pages shall be numbered sequentially by volume.

These page size and format restrictions shall apply to responses to ENs.

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 count as a single 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. These limitations shall apply to both electronic and hard copy proposals.

2.2.3 Pricing Related Data

All pricing information shall be addressed in the Contract Documentation volume, in Section B of the Schedule of the Request for Proposal (RFP). Information shall be limited to Contract

Line Item Number (CLIN), SubCLIN, or ELIN-level pricing, including unit and extended pricing, as specified in Section B of the RFP.

2.2.4 Cross-Referencing

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. The offeror shall provide a Solicitation Cross Reference Matrix indicating by ITO, SOW, and specification paragraph number, the corresponding proposal paragraph in that section which addresses the referenced item. See the following sample matrix:

Section L Section M SOW Spec. CLIN CDRL Volume Proposal

2.2.5 Indexing

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

2.2.6 Glossary of Abbreviations and Acronyms

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

2.2.7 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, 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. 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.3 Electronic Offers

Electronic Offers – The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and electronic copy, the hard copy shall take precedence. For electronic copies, indicate on each CD the volume number and title. Use separate files for each volume to permit rapid location of all portions, including subfactor required plans, exhibits, annexes, and attachments, if any. The Offeror shall submit volumes I through III in electronic format, using read only CDs (i.e. CD-R). In no case, shall the Offeror use re-writable CDs (i.e. CD-RW). Each volume shall be on a separate CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Word 2007, MS

Excel 2007, MS-Project 2003, and MS-Power Point 2007, as applicable and not in PDF format.

2.4 Distribution

The "original" proposal shall be identified. Proposals shall be addressed to the PCO and mailed or hand carried to:

AFMC/PZZKC

Wade Pilcher

6039 Wardleigh Ave, Bldg 1206

Hill AFB UT 84056

2.5 Volume Summary – Identified Evaluation will be based on the following factors and subfactors:

Volume I – Price / Contract Documentation

Volume II – Technical

Subfactor 1 – Program Management

Subfactor 2 – Technical Orders and Technical Data

Subfactor 3 – Testing

Subfactor 4 – Engineering Design

3.0 VOLUME I – PRICE / CONTRACT DOCUMENTATION

3.1 Model Contract

3.1.1 The purpose of this volume is to provide information to the Government for preparing the contract document and support file. The offeror shall complete the blocks of the RFP as required on the Standard Form (SF) 1447. In doing so the offer accedes to the contract terms and conditions as written in the RFP sections A through K. These sections constitute the model contract.

3.2 Section A Solicitation/Contract Form

3.2.1 The offeror shall complete blocks 13 and 15, then sign and date block 27 of the Standard

Form (SF) 1447, Solicitation/Contract. For any amendments to the RFP (SF 30) the offeror must complete blocks 8, 15A, 15B (Signature), and 15C. Signature of the Offeror on the SF 1447/SF

30 constitutes an offer, which the Government may accept. In signing the SF 1447/SF 30, the

Offeror accedes to the contract terms and conditions as written in the RFP Sections A through

K.

3.3 Section B – Supplies or Services and Prices

3.3.1 Unit and extended prices for Section B shall be completed by the offeror. Offeror shall fill-in unit price and extened amount for each Contract Line Item Number (CLIN) in Section B. The extended amount must equal the whole dollar unit price multiplied by the number of units.

The Cost/Price evaluation factors are Price Reasonableness and Balance. A Total Evaluated

Price (TEP), as defined in section M of this RFP, will be computed and provided to the Source

Selection Authority for award purposes only. It is the offeror’s responsibility to provide enough information in the Cost/Price proposal to support the evaluation factors.

3.4 Section F – Deliveries or Performance

3.4.1 Deliveries or Performance schedules shall be in accordance with the SOW.

3.5 Section I – Contract Clauses

3.5.1 The Offeror shall complete necessary fill-ins in Section I and submit as part of their Model

Contract/Solicitation. The Offeror shall comply with the clauses specified within Section I of the

Model contract/Solicitation. Furthermore, any reference of a clause and/or provision in the solicitation will be adhered to and included in the resulting contract. All laws, regulations, and statuory authorities will also be applied within the model Contract/Solicitation.

3.6 Section K – Representations, Certifications, and other Statements of Offerors

3.6.1 The Offeror shall provide completed representations, certifications, acknowledgments, and statemets.

3.7 Exceptions to Solicitation Requirements

3.7.1 Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. 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, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 3.3.

Table 3.7 - Solicitation Exceptions

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

SOO, SOW, SPEC,

Model Contract, ITO, etc.

Applicable

Page and

Paragraph

Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

3.8 Other Information Required

3.8.1 Authorized Offeror Personnel – Provide the name, title, and telephone number of the company/division POC 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. Additionally, provide the name, title, and telephone number of the Chief

Executive Officer, Division President, and/or Vice President.

3.8.2 Company/Division Address, Identifying Codes, and Applicable Designations – Provide company/division’s street address, county and facility code; CAGE code; DUNS code; Taxpayer

Identification Number (TIN); 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.

4.0 VOLUME II – TECHNICAL

4.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in

Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

Evidence which clearly demonstrates and supports the offeror’s claims is essential.

4.2 Format and Specific Content

4.2.1 Technical

In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor.

4.2.2 Volume Organization

The Technical volume shall be organized according to the following general outline:

(1) Table of Contents

(2) List of Table and Drawings

(3) Glossary

(4) Cross Reference Matrix

(5) Subfactor One

(6) Subfactor Two (etc.)

4.3 Subfactor 1, Program Management

4.3.1 Integrated Master Schedule (IMS)

The Offeror shall provide a Gantt Chart depicting the start and end points of all events required to complete the production and testing for each end item delivery (i.e. PRA, production, spares).

The IMS shall include the procurement of long-lead material, a site survey, production of spares measured from the notional contract award date of 01 September 2019. The offeror shall provide a IMS that identifies proposed schedule dates for all events, reviews, accomplishments and criteria as outlined in SOW para 4.2. The offeror shall include the Technical Data Package

(TDP) delivery as a part of the IMS.

4.3.2 Data Management

The offeror shall describe how they will manage generating, tracking, maintaining DID compliance and delivery of the data products described in Section 3.2, 3.3, and 4.2 of the SOW.

4.4 Subfactor 2, Technical Orders and Technical Data

4.4.1 Technical Orders

The offeror shall describe how they will meet the requirement to develop, prepare and deliver technical order (TO) change pages and commercial manuals as outlined in CDRL A013 and

A014. This description shall include how the offeror will meet the criteria described in SOW

3.1.1 and CDRL A013 and A014.

4.4.2 Technical Data

The offeror shall describe what data rights, relative to CDRL item A016 and as described in

Section 3.1.1 & 3.2.1.1 of the SOW, they propose to satisfy the governments need for data suitable for manufacture or repair activites by other sources.

4.5 Subfactor 3, Testing

The offeror shall provide an approach that describes testing efforts necessary to validate all requirements described in the System Requirements Document (SRD) and described in the testing Section of the SOW section 3.2.1. The offeror’s approach shall include an explanation on how the offeror will meet the SRD specifications, environmental requirements, and system reliability requirements. Tests shall comply with those defined is Section 3.2.1.7 of the SOW.

The offeror shall use the sequence (not format) of Test Plan, Test Procedure and Test Report as outlined CDRLs A004 - A008.

4.6 Subfactor 4, Engineering Design

4.6.1 In the design of the MTE 450 Volt Power Supply (VPS), the offeror shall convey to the

Government how several engineering aspects will or are incorporated into their product. The aspects shall include shielding, filtering, built-in-test, and obsolescence mitigation. The offeror shall describe how their design will meet the contract requirements for compliance with Section

3.2.1 of the SOW, and the SRD. The offeror shall prove to the Government how their design will be supportable for ten years. For example, this could be shown by designing in redundancy, identifying multiple sources for every component, or recommending a lifetime buy to the

Government for sole source components. The lifetime buy is based on the offeror's reliability model and estimated allocation hours for each component. The offeror shall reference SOW

3.2.1 and ISO 9001:2015 [or an equivalent Quality Assurance Program Plan (QAPP)] while detailing the VPS design.

4.6.2 As a part of demonstrating long term reliability and supportablity, the contractor must submit proof of ISO 9001:2015 certification or submit an equivalent quality assurance program plan, in accordance with Section 5.0 of the SOW.

4.6.3 For operation and maintenance (including installation, removal, and testing) only common tools shall be required; no special or unique tools will be required. The offeror shall include this while addressing the maintenance concept. The offeror shall describe all of the testing methods including qualification testing, built-in-test, and operational and maintenance testing. The offeror shall describe their complete technical data package to be delivered after inspection and acceptance of the Production Representative Article (PRA). The offeror shall describe their maintenance concept to show how easily and safely the power supply can be restored to full operation.