H92241-15-R-0012-0003.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of the amendment is as follow s:

1. CLIN 0004 is hereby changed to include the Technical Tasking Directive (TTD).

2. CLIN 0006 Travel is hereby renumbered to CLIN 0005 Travel.

3. Statement of Work is hereby revised to add TTD instructions.

4. Addition of FAR Clauses. See Summary of Changes for details.

5. Section H is hereby changed to add Sections H.2 and H.3. See summary of changes for details.

6. Sections J, K, L and M are modified. See Summary of Changes for details.

7. All other terms and conditions remain the same.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 18

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 02-Jun-2016

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X H92241-15-R-0012

X 9B. DATED (SEE ITEM 11)

20-Jul-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

01-Jun-2016

CODE

TECHNOLOGY APPLICATIONS CONTRACTING OFFI

BUILDING 401, LEE BLVD

ATTN: ANDREW DAVIS

FORT EUSTIS VA 23604

H92241 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

H92241-15-R-0012

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0004

The CLIN extended description has changed from:

The contractor shall provide engineering support for RRU integration into the platform IAW Section 6.0 of the SOW.. Support may include, but is not limited to, addressing system integration issues such as physical installation and cabling, and software integration topics such as system interface, definition file format and load, and system initialization.

To:

The Contractor shall furnish all labor, material, and facilities, except as otherwise specified herein, to provide engineering and technical service support as defined in Section C-6.0 of the Performance Work Statement (PWS) and clause H.2, Technical Tasking Directives..

The unit of issue Lot has been added.

CLIN 0006

This CLIN has been renumbered to CLIN 0005.

The CLIN extended description has changed from:

The Contractor will be required to travel to support technical meetings and activity in support of RRU integration during the engineering support period IAW section 7,1 of the SOW

To:

The Contractor will be required to travel to support technical meetings and activity in support of RRU integration during the engineering support period IAW section 7.1 of the SOW.

The unit of issue has changed from Each to Lot.

SECTION G - CONTRACT ADMINISTRATION DATA

The following have been added by full text:

5652.216-9000 Fixed Fee Information (2003)

Subject to the requirements of FAR 52.216-8 and all other withholding requirements of this contract, the fixed fee stated in Section B shall be paid to the contractor at the same percentage rate as the percentage of incurred and allowable costs proportionate to the total estimated cost.

(end of clause)

SECTION H - SPECIAL CONTRACT REQUIREMENTS

The following have been modified:

GENERAL CONTRACT CONDITIONS

H-1. AUTHORIZED ORDERING OFFICES

a) Only Government Contracting Officers with current warrants at the office listed below may issue Task and Delivery Orders under this contract.

Authorized Ordering Offices Technology Application Contracting Office (TAKO)

ATTN: AMSAM-SPK

401 Lee Blvd.

Ft. Eustis, VA 23604

b) The Contract Administration Office and Payment Office designated on the cover sheet of this contract and/or Section G shall be used for all task/delivery orders issued under this contract.

c) A copy of all task/delivery orders and task/delivery order modifications shall be sent via email or fax to the following persons within one business day of issuance:

Technology Application Contracting Office (TAKO) ATTN: AMSAM-SPK (Andrew Davis) 401 Lee Blvd.

Ft. Eustis, VA 23604 Email: Andrew.l.Davis2.civ@mail.mil

FAX: (757) 878-2717

d) Authority of Procuring Contracting Officer and Ordering Officers

1) Procuring Contracting Officer: The Procuring Contracting Officer (PCO), identified on the cover page of this contract, has the overall responsibility for this contract and, except for functions delegated to the Administrative Contracting Officer (ACO), has sole authority to take actions on behalf of the Government to amend, modify or deviate from the contract terms, conditions, and requirements. The PCO has sole authority to grant and revoke ordering authority under this contract. The PCO retains the authority to stop work, cancel, terminate and/or modify any delivery order issued by any Ordering Officer that is determined to be outside the scope of this contract or otherwise improper.

e) The Contractor shall notify the PCO via fax or email within three business days of receipt of a task/delivery order or modification that appears to be outside the scope of the contract or contains terms and conditions that conflict with the basic contract. The Contractor shall not incur any cost in fulfilling a questioned order until the PCO renders a decision. The PCO’s decision as to whether or not a questioned task order is within the scope of the contract and otherwise proper is final.

H.2. TECHNICAL TASKING DIRECTIONS (TTDs) The Government requires the contractor to provide technical and/or programmatic support under Section B, contract line item number 0004, and Section C, Performance Work Statement (PWS), paragraph C-6.0. The Government will authorize work using technical tasking directives (TTDs) (Attachment 4). The COR shall prepare TTDs. Upon receipt of the TTD, the Contractor shall respond with the following data for attachment to the TTD:

(a) A description of work required, and method of execution, to demonstrate understanding of scope and task intent;

(b) An estimate of hours, materials, and other direct costs (ODCs) associated with the TTD using the rates negotiated at time of contract award;

(c) A budget for the hours with overhead, G&A, and the fee applied;

(d) A statement that sufficient funding remains on CLIN 0004 to cover this estimated cost;

(e) A period of performance.

(f) Travel is proposed under CLIN 0005.

The Contractor shall sign the TTD and return it to the COR with a copy to the Government Procuring Contracting Officer (PCO). Upon Government approval of the TTD and return of the signed TTD to the Contractor, the Contractor shall perform the TTD. If at any time during performance of the TTD, the Contractor anticipates exceeding the TTD estimate, the Contractor shall obtain approval from the COR to exceed this estimate. The Contractor shall notify via electronic mail the COR of completion of the TTD. The Contractor will use the negotiated rates for estimating costs for TTDs, but will be reimbursed for those costs in accordance with 52.216-7, Allowable Cost and Payment, incorporated into this contract. The Contractor must use the fixed fee rate agreed upon at the time of the award of this contract.

If at any time during performance of the TTDs, the Contractor anticipates exceeding funding obligated on the CLIN 0004, the Contractor shall provide notice to the Contracting Officer in accordance with FAR clause 52.232-22, Limitation of Funds. The issuance of TTDs exceeding available funding does not authorize the Contractor to exceed the amount of Government funding obligated to CLINs 0004/0005 or extend the period of performance for CLIN 0004/0005.

H.3 COSTS FOR TRANSPORTATION, LODGING, MEALS, AND INCIDENTAL EXPENSES.

Travel costs will be determined reasonable and allowable to the extent that the costs comply with the requirements in FAR 31.205-46.

(End of Clause)

5652.216-9004 Procedures for Issuing Task/Delivery Orders under Single Award, Indefinite Delivery-Indefinite Quantity Contracts (2003)

(a) Soliciting Task/Delivery Order Proposals: When the Government has a requirement for services/supplies to be performed/delivered under this contract that have not been previously priced, the Contracting Officer will issue a request for task/delivery order proposal either in writing or electronic transmission. Each request for an order proposal will include, but not necessarily be limited to, the following:

1) Request for proposal number and/or title;

2) Contract Number;

3) Statement of Work;

4) Instructions to Offerors;

5) Items to be delivered and delivery schedule/performance period; and

6) A listing of Government furnished property to be provided to the Contractor, if required.

(b) Urgent Requirements: In the event of an urgent requirement, the Contractor shall provide a written proposal within the timeframe specified by the Contracting Officer in the specified format.

(c) Submission of Proposals: The Contractor's proposal must comply with the Instructions to Offerors included in the request for task order proposal. The Contractor shall have no more than 30 days to submit their proposals, unless:

1) A longer timeframe is specified in the request for task order proposal, or

2) It is an urgent requirement.

(d) Upon receipt of the proposal, the Contracting Officer may:

issue a task/delivery order based upon the proposal furnished;

negotiate with the Contractor prior to issuing a task order/delivery, or, reject the proposal and cancel the requirement.

Task/delivery orders shall be issued on DD Form 1155 "Order For Supplies and Services;" (or similar form)

Task/delivery orders shall be consecutively numbered, dated and shall include supporting documents as applicable.

(e) For items that the Government and Contractor have previously agreed upon either to cost or price, the Government has the right to issue orders on a unilateral basis.

(f) to Section H, clause 5652.216-9004, Procedures for Issuing Task/Delivery Orders: When an order includes contract line item number (CLIN) 0004, the Government will provide a statement of work as part of the request for task/delivery order proposal that the Contractor propose its anticipated level of effort to accomplish the SOW using the rates contained in Attachment 4, including, direct labor rates, indirect rates, overhead, general and administrative rate, and fixed fee. As part of the evaluation of the task/delivery order proposal, the Government will conduct a cost realism analysis of CLIN 0004.

The Government will, however, reimburse the Contractor for its actual rates based upon its final agreed rates with the Defense Contract Management Agency Administrative Contracting Officer.

SECTION I - CONTRACT CLAUSES

The following have been added by reference:

52.216-7 Allowable Cost And Payment JUN 2013 52.216-8 Fixed Fee JUN 2011 52.230-2 Cost Accounting Standards OCT 2015 52.230-3 Disclosure And Consistency Of Cost Accounting Practices OCT 2015 52.230-6 Administration of Cost Accounting Standards JUN 2010 52.232-22 Limitation Of Funds APR 1984 52.242-1 Notice of Intent to Disallow Costs APR 1984 52.242-3 Penalties for Unallowable Costs MAY 2014 52.242-4 Certification of Final Indirect Costs JAN 1997 52.243-2 Changes--Cost-Reimbursement AUG 1987 252.216-7006 Ordering MAY 2011 252.242-7004 Material Management And Accounting System MAY 2011 252.244-7001 Contractor Purchasing System Administration MAY 2014 252.246-7007 Contractor Counterfeit Electronic Part Detection and

Avoidance System

MAY 2014

The following have been added by full text:

5652.216-9005 Government Down Time for Various Reasons (2005)

From time to time Government installations may be closed in response to an unforeseen emergency or similar occurrence, or by order of the President, Secretary of Defense, or installation commander. Designated emergencies include, but are not limited to, adverse weather such as snow or flood, an act of God such as a tornado or earthquake, acts of war or terrorism, computer failures, or a base disaster such as a natural gas leak or fire.

(a) Under such designated emergencies or other ordered base closures, contractor personnel will not be allowed on the Government installation unless specifically approved by the Contracting Officer in accordance with installation policies and procedures. If an emergency requiring installation closure occurs while contractor personnel are on the installation, contractor personnel shall promptly secure all government furnished property appropriately and evacuate in an expedient but safe manner unless otherwise directed by the Contracting Officer.

(b) If the installation closure causes a delay in the work required by the contract, the Government may:

(i) grant a time extension in each task order delayed by the closure equal to the time of the closure, subject to the availability of funds.

(ii) terminate the work or a portion of the work.

(iii) reschedule the work on any day satisfactory to both parties.

(iv) permit the contractor to perform at an off-site location during the period of installation closure if meaningful work can be accomplished. Contractor shall certify to the government by letter within 5 business days of returning to work the nature and scope of the work completed off-site. There shall be no adjustment to the contract labor rates for work performed off the installation.

(v) require that the Contractor continue on-site performance during the installation closure period in accordance with installation procedures.

The following have been deleted:

52.243-1 Alt I Changes--Fixed Price (Aug 1987) - Alternate I APR 1984

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

LIST OF ATTACHMENTS

Exhibit/Attachment Table of Contents:

Pages: Date:

Attachment 1 Statement of Work 9 26 May 16 Attachment 2 Specifications 19 6 Jan 15 Attachment 3 CDRLs 7 19 Sept 14 Attachment 4 Technical Tasking Directive (TTD) 1 26 May 16

SECTION K - REPRESENTATIONS, CERTIFICATIONS AND OTHER STATEMENTS OF OFFERORS

The following have been added by reference:

52.230-1 Cost Accounting Standards Notices And Certification OCT 2015 52.230-7 Proposal Disclosure--Cost Accounting Practice Change APR 2005

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

PROPOSAL INSTRUCTIONS

L.1 General Instructions to Offerors. The contractor's proposals shall become the basis for evaluation by the Government. The proposal must be precise, factual and complete, as well as legible, clear and responsive to the solicitation. In the event the offeror takes any exception to or sets any conditions for its proposal under the subject solicitation, such an exception or condition shall be set forth in a cover letter to offeror's proposal.

L.1.1 This is an all electronic solicitation release. No hard copies will be mailed. The solicitation and amendments to the solicitation will be posted to the Federal Business Opportunities website at www.fedbizopps.gov.

It is the responsibility of each offeror to review the webpage for notice of amendments, updates, or changes to current information. The following instructions must be followed when preparing the proposal. To be considered for award, a complete response to the RFP is required. Each proposal and response/acknowledgment of any amendment(s) must be submitted to the issuing office. The Government will consider how well the offeror complied with these instructions when evaluating each offer. Failure to follow these instructions may be considered indicative of the type of conduct that it may expect from the offeror during contract performance. The offeror should clearly state how it intends to accomplish the work called for in the contract. Mere acknowledgement or restatement of a requirement or task is not acceptable. The information in the proposal should be presented in a clear, coherent and concise manner. The proposal shall include all the information requested in the instructions below.

L.1.2 All proposals must be complete, self-sufficient, and respond directly to the requirements of the solicitation.

Any commitments made in the proposal shall become part of the resultant contract. Any significant inconsistency, if unexplained, raises a fundamental issue of the offeror’s understanding and/or ability to perform under a contract.

This may be a basis for rejection of the proposal. In no case shall words like “we will comply with the requirements of the contract,” or equivalent statements, be acceptable to meet the requirements of this RFP. Failure to comply with these instructions may result in an offeror’s proposal being excluded from further consideration for award.

Offerors shall submit with their proposals a list of names and telephone numbers of persons authorized to conduct negotiations.

L.1.3 Proposals should not contain classified information.

L.1.4 Volume I/Program Management/Technical/Factor 1 shall be prepared IAW these instructions and will be evaluated IAW the evaluation criteria in Section M, Evaluation Factors for Award. The proposal shall articulate the proposed technical solution and how it meets the performance and qualification requirements set forth in the RRU Performance Specification.

The proposal shall also address the requirements stated in the Statement of Work. Proposals shall include necessary information to enable the evaluators to form a definitive conclusion concerning the offeror’s ability to perform the required program. The Program Management/Technical proposal shall be organized in Tab format in the order listed in Section L and submitted IAW L.1.9.

L.1.5 Volume II/Price/Factor 2 shall be prepared IAW these instructions and will be evaluated IAW the evaluation criteria in Section M and submitted IAW L.1.9.

L.1.6 Volume III/Past Performance/Factor 3, shall be prepared IAW these instructions and will be reviewed IAW the evaluation criteria in Section M and submitted IAW L.1.9.

L.1.7 Delivery Instructions:

a. Hand Carrying Instructions. Hand delivery is permitted by a person from an offeror’s/teaming partner’s staff. A messenger service delivering a package is not considered a hand delivery. All hand-carried proposal documents, to include CD-ROMs/DVDs, shall be delivered to the address below. Offerors are requested to provide a 24-hour notice to the Point of Contact (POC) at the telephone number below to provide notification of pending arrival:

Technology Applications Contracting Office ATTN: Contract Specialist:Lee Davis, AMSAM-SPK Lee Blvd., Building 401 Ft. Eustis, VA 23604 Primary Telephone: (757) 878-0730 x243

b. Mailing Instructions. Submit clearly marked proposals to:

Technology Applications Contracting Office ATTN: Contract Specialist:Lee Davis, AMSAM-SPK Lee Blvd., Building 401 Ft. Eustis, VA 23604 Telephone: 757-878-0730 x243

L.1.8 Proposal Format. Format of the proposal volumes (and any resulting responses to Evaluation Notices (ENs)) shall be as follows:

a. Text size shall be no smaller than what is equivalent to Microsoft Word, Times New Roman, 10 point, uncompressed font.

b. Pages shall be single sided, singled spaced, with a minimum of one inch margins on all sides. Pages shall be dated and numbered sequentially by volume. A cover sheet should be bound in each book, clearly marked as to volume number, title, “original” or copy number, solicitation identification, and the offeror’s name.

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

d. Pages shall be dated and numbered sequentially by volume.

Elaborate format, color representations, and bindings are not desirable. Three-ring binders are preferred. The pages in the binders shall be easily removed and replaced to facilitate page changes. Any pages that are changed (as the result of negotiations) should be of a different color (as specified by the Contracting Officer) and have changed information clearly marked by a vertical line in the right margin of the page and/or circling if changing data in a chart. The offeror shall indicate the new date on revised pages.

e. Legible tables, charts, graphs and figures shall be used when necessary 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 one 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 equivalent to Microsoft Word 8 point, Times New Roman. All cells in the cost proposal on the CD ROM must contain “open” cells in Microsoft Office 2007 or later spreadsheet product.

f. Electronic copies must be provided on CD-ROMs/DVDs, read-only memory. Microsoft Office 2007 or later, presentation and spreadsheet products are preferred. Changes, as a result of negotiations, will be conformed on CD-ROMs/DVDs and have changed information clearly marked by a vertical line in the right margin.

L.1.9 Proposal Submission Requirements

Proposal Volume / Purpose / Factor Proposal Volume Quantities Page Limitation / Instructions Volume I, Part 1 / Program Management/ Technical / Factor 1

One Original Three copies One Electronic Version

Volume I shall be VOID of proposal cost information. Volume I shall not exceed 60 pages, inclusive of any drawings, charts, etc., and section dividers, table of content list of figures/tables, glossary of terms and cross-referencing indices (which are not considered content pages). The evaluators will read only up to the maximum number of pages specified.

Pages shall be standard 8 ½” by 11” paper and type shall be Times New Roman, 10-pitch or larger font size, single spaced with margins at least 1 inch, except for text embedded in tables and illustrations. Fold-out illustrations required for reader ease are allowed, however, illustration shall be counted in 8 ½” by 11” increments (e.g. a 11”x17” document will count as one (1) page).

Volume II / Price /Factor 2 One Original Three Copies One Electronic Version

No Limit

Vol III / Past Performance / Factor 3 One Original Three Copies One Electronic Version

15 pages or less

L.2 QUALIFYING CRITERIA. Provide documentation under separate cover from the volumes, as required below, in order for the Government to determine if appropriate information is provided for the offeror to be responsive to the requirements. The proposal must be valid until, at a minimum, 120 days after proposal submission.

L.2.1 Proposal cover letter or proposal cover page include names, office phone and facsimile numbers, if applicable, cell phone numbers, and e-mail addresses for proposal points of contact.

L.2.2 A copy of the RFP with the original signature of an official authorized to contractually bind the offeror in Block 17 of the SF 33. The offeror must complete the following sections within the RFP for these criteria:

o Solicitation, Offer and Award (Standard Form 33), Blocks 12- 18 o Include all Solicitation Amendments (Standard Form 30), if applicable.

o All Section K, Representations, Certifications and Disclosures

L.2.4 Small Business Subcontracting Plan Small Business Subcontracting Plan and Small Business Participation. FAR 52.219-9 and DFARS 252.219-7003 (FAR 52.219-8 will also be required) clauses are included in this solicitation and will be incorporated into any resultant contract. A subcontracting plan is required from all offerors other than small business concerns for proposals exceeding $650,000 which contain subcontracting opportunities. The plan shall be submitted to meet published annual USSOCOM small business goals with the initial proposal and will be concurrently reviewed and either approved or disapproved. If a cost proposal is required by this solicitation, it must relate to, and substantiate, the submissions under FAR 52.219-9(d). The offeror’s submission must provide sufficient information to support the Contracting Officer’s review of the subcontracting plan to determine if it is acceptable (otherwise an offeror will be ineligible to receive the contract award).

Small Business Subcontracting Plan. Offerors must comply with all sections of FAR 19.704. This includes:

a. Each offeror shall describe their corporate commitment in providing subcontracting opportunities for small business, small disadvantaged business, women-owned small business, HUBZone small business (no mandated minimum but should still be addressed), veteran-owned small business, and service disabled veteran-owned small business concerns.

b. Describe the strength and specificity of each corporate commitment (i.e., what type of commitment, how binding is the commitment, how specific is the commitment to this proposed effort, and what type of work will be included in these subcontracting opportunities from the overall corporate level).

c. Each offeror shall include a listing of their subcontractors (large and small). For Small Businesses, list the socio-economic category (ies) for each entity.

Small Business and Socio-Economic Program Participation. The offeror shall describe how their subcontracting plan meets or exceed the mandatory small business participation minimum of 23% of total estimated contract dollars. The offeror’s Small Business Subcontracting Plan shall indicate how the subcontracting plan will meet or exceed each category as follows:

CATEGORY MINIMUM REQUIREMENT

A. Total small business concerns 23% B. Small disadvantaged business 5% C. Women-Owned Small Business 2% D. HUBZone Small Business 3% E. Disable Veteran own-ed Small Business 1%

L.3 VOLUME I –PROGRAM MANAGEMENT/TECHNICAL

L.3.1 Executive Summary. This section is limited to five (5) pages, but is not included in the page limit for Volume I. It should contain, in no more than five (5) pages, a concise summary of the offeror’s proposed approach and ability to meet the requirements as described in the A/MH-6M RRU Request For Proposal (RFP). The offeror may cite use of the RRU in commercial or military applications. The table of contents, title page, acronym lists, and tab dividers are not included in the page count. The Executive Summary shall include a declaration statement that acknowledges all Statement of Work (SOW) and Performance Specification requirements, providing high level description(s) of any exceptions where the proposed solution does not meet the SOW or Performance Specification.

The executive summary shall include a statement of license rights granted to the Government for the deliverable items. The Government desires unlimited rights for CDRL items A001, A003, and A011.

L.3.2 Volume I, Part 1 – Factor 1 – Program Management/ Technical. The offeror shall describe how their overall proposed technical solution meets the RRU requirements. The Program Management/ Technical Factor has three subfactors: System Performance, Life Cycle Support and Program Management. The System Performance subfactor is more important than the Life Cycle Support subfactor. The Life Cycle Support subfactor is more important than Program Management. In each subfactor, the offeror may identify any risk mitigation factors for Government consideration.

L.3.2.1 Subfactor 1.1: System Performance. The offeror shall articulate their proposed technical solution and explain how the proposed system meets the performance requirements in the RRU Performance Specification Paragraph 3.0 and SOW, including the provision of a specification compliance matrix. This specification compliance matrix shall define the level to which the technical solution complies to each performance requirement in the RRU Performance Specification and SOW. Failure to include the cross reference matrix may render a proposal non-responsive. The offeror shall identify the extent to which the design solution meets the requirements and how the design fulfills the requirements. The matrix shall list the spec paragraph number; state the requirement; list the offeror's capability and/or refer to the paragraph in the offeror’s proposal that demonstrates how, or provides compliance evidence towards, the proposed solution meeting the requirement; and detail the rationale/verification for the offeror's capability. The compliance matrix shall also identify any non-compliance or deviation with requirements of the RRU. For any deviations from or non-compliance with the detail specification requirements, the offeror shall describe how their proposed solution will meet the performance objectives. The offeror's response shall provide the verification data and documentation that shows the extent to which the offeror has demonstrated compliance to the performance requirements set forth in the specification document. Separately, the offeror shall provide two (2) copies of all recorded (raw) data generated during the conduct of verification tests/events. The raw data sheets shall be excluded from the page count requirement for the Technical Volume. For requirements which the offeror does not have supporting test data, the offeror shall provide analytical design data that supports fulfilling the requirement. The substantiating data shall be cross-referenced to the specification compliance matrix. The offeror shall identify any risk mitigation efforts for government consideration.

The offeror shall describe his plans for completing the qualification of the RRU in accordance with the RRU Performance Specification and SOW. The offeror shall describe potential test facilities; describe the test to include setup and test/support equipment where the offeror's test may differ from what is required by specification; models or simulations being used; quantity of RRUs and flow through the test events to include the sequencing of test events. The offeror shall describe their software development process and provide a detailed plan for how they will develop and test the software resident in the RRU to ensure that the ARINC 661 interface is stable and cannot be corrupted. The offeror shall identify their development tools and if they support generation of ceritification artifacts compliant with DO-178B/C safety objectives and to what level. The offeror shall note if the Cockpit Display System (CDS) kernel, the binary definition file (DF), and/or the user application (UA) have been previously certified and to what level.

L.3.2.3 Subfactor 1.2: Life Cycle Support. The offerors should demonstrate a sound plan to address Diminishing Manufacturing Sources and Material Shortages (DMSMS) and an overview of their obsolescence management approach. The offeror shall provide an estimate of the Mean Time Between Failures (MTBF) and the supporting analysis for the MTBF estimate.

L.3.2.4 Subfactor 1.3: Program Management. The offeror shall describe management approach/ to support the RRU acquisition, teaming arrangements (if any), systems engineering expertise, and the Manufacturing Readiness Level (MRL). The offeror shall provide a preliminary program schedule thru prototype deliveries.

L.4 VOLUME II – FACTOR 2 –Price The contractor shall provide price information in accordance with Section B of the solicitation.

Cost or pricing data is not required, except for contract line item number (CLIN) 0004. However, the contracting officer reserves the right to request other than cost and pricing information should it be necessary to allow the Government to make a fair and reasonable price determination.

Directions for preparation of cost proposal for CLIN 0004, Technical Tasking Directives (TTDs), and CLIN 0005, Travel. The offeror shall submit a cost proposal for CLINs 0004 and 0005 with supporting information for each cost element consistent with offeror's cost accounting system. The supporting breakdown should include such elements as materials, direct labor, indirect cost, and other costs such as travel for support of the three Technical Interchange Meetings (TIMs) described in the Statement of Work, paragraph C.6.0. The offeror will include a basis of estimate and rationale for the labor categories and quantities proposed for the support used based upon the SOW. The offeror shall provide exhibits as necessary to substantiate each cost element. Should rates be used in the proposal which are not DCAA approved, the offeror shall provide complete documentation and the rationale for their use at time of proposal submission. However, offerors are advised to use actual labor rates of proposed personnel as the basis for estimating labor costs when practicable. In addition to the cost for support of the TIMs, the offeror must provide a composite engineering labor rate for on call support in the amount of 270 hours. The offeror must propose a total cost for the TIMs and the 270 hours of engineering support, with overhead, G&A, and fee separately applied to support Government evaluation. The CLIN 0004 proposal must be detailed enough to support a Government cost analysis and cost realism analysis of this proposed cost. The proposal must also include a proposed fee for the TTDs and Section B, CLIN 0004 completed with the estimated cost and fixed fee entered.

L.5 VOLUME III – FACTOR 3 – Past Performance

L.5.1 Contents. The offeror shall submit a Past Performance Proposal (Volume III) containing the following:

a. Table of Contents.

b. Summary Page describing the role of the offeror and each subcontractor, teaming partner, and/or joint venture partner that the offeror is required to provide Past Performance Information Sheets IAW paragraph L.5.1.1 below.

c. Past Performance Information Sheets, paragraph L.5.1.1 below.

d. Consent Letters executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information so the offeror can respond to such information.

L.5.1.1 Past Performance. When addressing past performance the offeror shall provide references from Government and private industry sources that are not prohibited from furnishing information to the Government.

Offerors may include with their proposal information on problems encountered on the identified contracts and the offeror’s corrective actions. In selecting the references, offerors should consider the currency and relevancy of the past performance information. In determining relevancy and currency to the solicitation requirement, offerors should make every effort to submit references that are similar in scope, nature and complexity to this solicitation, i.e.

development, qualification, and production of avionics components with emphasis on MFDs or similar displays.

The offeror shall submit separately, with the proposal, a list of current contracts of similar scope, nature, and complexity, with contract number, contract office point of contact, program office point of contact, contract value, and products or services. Contact information must include both telephone number and electronic mail address.

The Government will consider this information as well as information obtained from any other sources when evaluating the offeror’s past performance.

Offerors lacking relevant past performance information may submit data from subcontractors and predecessor companies who have relevant experience. In this case, offerors shall provide relevant information to allow Government evaluators to conduct a Past Performance evaluation on the predecessor companies and subcontractors.

If offeror is listing performance for a predecessor companies, offeror shall address relationship of current organization to the predecessor. Such information shall, as a minimum, include:

a. Name(s) of Predecessor Company/Subcontractor and include:

Complete Address Telephone & Fax Number Employment Relationship or Agreement Brief synopsis of relevant experience E-mail address

b. Provide a minimum of three (3) to a maximum of five (5) references for each Predecessor Company or Subcontractor and include for each reference:

Complete Address;

Point of Contact;

Telephone & Fax Number; and email address Contract Number;

Contract Type;

Project Title;

Contract Period of Performance;

Brief description of work;

c. Offerors shall submit with their proposal a Reference List identifying all businesses and Federal, State or Local government agencies for which the offeror has been awarded a contract during the past three (3) years through this solicitation’s release date. If an offeror has more than five awarded contracts during the past 3-year period, then identify only the most recent five consecutive awarded contracts. For each reference on the list of awarded contracts, identify the following:

Company/Government Agency name;

Complete address;

Point of Contact;

Telephone & Fax number; and email address Contract Number;

Contract Type;

Project Title;

Period of performance;

Brief description of the work.

SECTION M - EVALUATION FACTORS FOR AWARD

BASIS OF AWARD

M.1 Best Value Introduction. The Government will compare each offeror’s capabilities and proposal elements against the predetermined evaluation criteria related to the Government’s requirement defined herein. This acquisition is a competitive, best value source selection that will be conducted in accordance with (IAW) Federal Acquisition Regulation (FAR) Part 15, Defense Federal Acquisition Regulation Supplement (DFARS) Part 215 and

SOFARS 5615.

M.1.1 Best Value Evaluation/ Relative Importance of the Evaluation Factors. The Government will award to the offeror whose proposal offers the best value in accordance with the evaluation criteria stated in this section.

Within the best value continuum, the Government will employ a tradeoff analysis of price and non-price factors (FAR 15.101-1) in evaluating the proposals submitted. The Government will evaluate all proposals against Program Management/Technical, Price, and Past Performance factors. A color/adjectival and risk rating technique, described below in Section M.2, will be used to evaluate the Program Management/Technical Factor. The Program Management/Technical Factor will also be evaluated for risk. The Price Factor will not be given a color rating or scored. Program Management/Technical, Price and Past Performance factors are in descending order of importance.

The subfactors within the Program Management/Technical Factor are listed in descending order of importance. The Program Management/Technical factor is significantly more important than the Past Performance factor. In accordance with FAR 15.304 (e)(1), all evaluation factors other than price, when combined, are significantly more important than price.

Program Management/ Technical Factor 1.0 Evaluation Rating System Performance Subfactor 1.1 Color/Adjectival Risk Life Cycle Support Subfactor 1.2 Color/Adjectival Risk Program Management Subfactor 1.3 Color/Adjectival Risk

Price Factor 2.0 Total Price

Past Performance Factor 3.0 Relevancy/Confidence Level

Factor 1.0 – Program Management/Technical Volume I Subfactor 1.1: System Performance Subfactor 1.2: Life Cycle Support Subfactor 1.3: Program Management

Factor 2.0 – Price Volume II

Factor 3.0 - Past Performance Volume III

M.2 FACTOR 1: Program Management/Technical. Under the Program Management/Technical Factor, the offeror will be evaluated on how well the overall proposed technical solution meets the A/MH-6M Block 3.0 RRU Specification. Consideration will be given to the offeror’s engineering approach, systems engineering expertise, and anticipated reliability and maintainability. The Program Management/Technical Factor has three subfactors:

System Performance, Life Cycle Support and Program Management. The System Performance subfactor is more important than the Life Cycle Support subfactor that is more important than the Program Management subfactor.

Evaluation of this Factor will focus on the strengths, deficiencies, significant weaknesses, and weaknesses of the offeror’s proposal. The risks associated with the offeror’s technical plan and their ability to execute their plan will be evaluated. The Government will assign a color/adjectival rating with a risk rating at the subfactor level. The Government will then consolidate, “roll up”, the subfactor ratings into an overall, single color/adjectival with a separate risk rating for this Factor (addressed below), as determined by consensus of the SSEB. If one subfactor is evaluated as Unacceptable, “Red”, the technical rating will be assessed as Unacceptable. The color/adjectival and risk ratings will use the following will use the definitions in Tables 1 and 2:

The Government's A/MH-6M Block 3.0 RRU requirements are articulated in Attachment 1,the RRU Performance Specification. Failure to meet the requirements defined in Section 3.2.1.2 Display Resolution, Section 3.1.2.2.1 Ethernet, and Section 3.2.12 ARINC 611, will result in a deficiency. Failure to meet other system or subsystem requirements, will be deemed a weakness or significant weakness by the Government, depending on the extent of the requirements deviation. Failure to address a requirement in the compliance matrix as instructed in Section L.3.2.1 will also be considered as a weakness. Also, as stated in Section L.1.1, mere acknowledgement or restatement of a requirement or task is not acceptable. The Offeror may propose a revision to RRU Performance Specification requirement provided that they submit data as part of their proposal which justifies/substantiates their proposed solution meets the performance objective. Note that if an offeror’s proposal fails to meet a Government requirement that is not satisfactorially justified, it is a weakness in the offeror’s proposal. Conversely, proposal elements that exceed threshold requirements or partially meet objective requirements may be characterized as strengths and documented in the SSEB Evaluation Report.

Table 1 - Technical/Program Management Ratings

Color Rating Description Blue Outstanding Proposal meets requirements and indicates an exceptional approach and understanding of the requirements. The proposal contains multiple strengths and no deficiencies.

Purple Good Proposal meets requirements and indicates a thorough approach and understanding of the requirements. Proposal contains at least one strength and no deficiencies.

Green Acceptable Proposal meets requirements and indicates an adequate approach and understanding of the requirements. Proposal has no strengths or deficiencies.

Yellow Marginal Proposal does not clearly meet requirements and has not demonstrated an adequate approach and understanding of the requirements.

Color Rating Description Red Unacceptable Proposal does not meet requirements and contains one or more deficiencies and is unawardable.

Table 2 - Technical/Program Management Risk Ratings

Rating Description Low Has little potential to cause disruption of schedule, increased cost or degradation of performance. Normal contractor effort and normal Government monitoring will likely be able to overcome any difficulties.

Moderate Has little potential to cause disruption of schedule, increased cost or degradation of performance. Normal contractor effort and normal Government monitoring will likely be able to overcome any difficulties.

High Is likely to cause significant disruption of schedule, increased cost or degradation of performance. Is unlikely to overcome any difficulties, even with special contractor emphasis and close Government monitoring.

M.2.1 Subfactor 1: System Performance. The System Performance subfactor covers: RRU Performance Specification Paragraph 3.0 Requirements. The areas under the System Performance subfactor will be carefully reviewed to ensure that the proposed system can meet the Government’s threshold technical requirements as articulated in the RRU Performance Specification. The closer the offeror is able to demonstrate achievement of the Objective value, the more favorably the proposal will be evaluated.

Under this subfactor, the Government will evaluate how the offeror’s proposal defines a sound, complete, and realistic broad spectrum approach to analyzing requirements, system design, and development. The Government will assess each offeror’s technical plan and design maturity. Each offeror’s proposal will be assessed to determine if the proposed approach indicates a thorough understanding of the RRU requirements per the RRU Specification.

The evaluators may award a strength to an offeror who provides an RRU solution that has a previously certified/qualified Cockpit Display System (CDS) kernel, binary definition file (DF), and User Application. They may also award a strength to offeror’s whose Graphical User Interface (GUI) development tools support generation of DO-178B/C artifacts or to offerors who provide a detailed plan for development and testing of the software supporting the ARINC 661 interface. Previously qualified or certified solutions may receive a “Low” risk rating.

M.2.2 Subfactor 2: Lifecycle Support. The Life Cycle Support subfactor includes an assessment of the predicted Reliability, Sustainability and Maintainability, as well as the proposed Obsolescence/ Diminishing Manufacturing Sources and Material Shortages (DMSMS) Approach.

The proposals will be evaluated for demonstration of a sound plan to address DMSMS and the robustness of their obsolescence management approach. This evaluation will include the reasonableness of the Mean Time Between Failures (MTBF) estimate.

M.2.3 Subfactor 3: Program Management. Under the Program Management subfactor, the Government will evaluate the offeror’s management approach to support the RRU acquisition, systems engineering expertise, schedule, and the approach to achieving production of RRUs.

M.3 FACTOR 2: Price Factor Evaluation. Price will be evaluated to determine that it is fair and reasonable IAW FAR 15.404-1 (b) (2) (iii). In addition, a price realism analysis will be used to determine if the proposed price is unrealistically low without valid explanation. An unrealistically low price may demonstrate the Offeror does not fully understand the requirements. In such circumstances, an assessment of an unrealistically low price may affect the Program Management/Technical rating of the proposal. The Price Evaluation will also compare proposed costs to the Independent Government Cost Estimate (IGCE). IAW FAR 15.404-1(b), the Government will conduct a price analysis of proposals. The total evaluated price includes price information in accordance with Section B of the solicitation including the estimated production quantities as described in SOW paragraph 4.2. The evaluated price will not include any quantity price breaks. Price will not receive a color rating or score. The Government will conduct a cost analysis and cost realism evaluation of CLINs 0004 and 0005 proposed cost.

M.4 FACTOR 3: Past Performance. Offeror’s Past Performance - Past performance is a measure of the degree to which an offeror satisfied its customers in the past and complied with Federal, state, and local laws and regulations. The evaluation will be based on the offeror’s most recent contracts for similar requirements for the past three years, as well as data from independent sources. Past Performance will assess the relevancy and the risk associated with performing the current effort based upon the offeror’s prior performance.

a. Based on the evaluation results, the Government will assign a performance confidence rating to the past performance volume. The evaluation will consider the factors as described in paragraph

(d) below. Based on the evaluation results, the Government will assign one of five confidence ratings as defined in paragraph (g) below. An offeror may receive a rating based on the evaluation of its predecessor companies or subcontractors.

b. In assessing performance confidence, the evaluator may: (1) use data independently obtained from other sources; (2) rely upon personal business experience with the offeror; (3) consider any information the offeror submits which explains…