N0003918R0006-0002.pdf

1300655035

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 this Amendment is to revise the maximum page allow ance for Volume I, Technical, stated under paragraph (a) of provision L-317 SUBMISSION OF PROPOSALS (COMPLEX) (JUL 1999) in response to Q&A.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 12

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

16C. DATE SIGNED

BY 03-Jan-2018

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 N0003918R0006

X 9B. DATED (SEE ITEM 11)

20-Nov-2017

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, X 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

03-Jan-2018

CODE

COMMANDER, SPACE AND NAVAL WARFARE

SYSTEMS COMMAND

02 CONTRACTS

4301 PACIFIC HIGHWAY

SAN DIEGO CA 92110-3127

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0003918R0006

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The standard size code $27,500,000 has been added.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L-317 SUBMISSION OF PROPOSALS (COMPLEX) (JUL 1999)

(a) The proposal shall be prepared as follows and submitted electronically IAW Provision L-349. All correspondence shall be addressed to the Contract Specialist, Mary C. Kopa at mary.kopa@navy.mil and copy PCO, Editha Y. Bredesen at editha.bredesen@navy.mil.

“GO/NO GO Criteria” as required below (No more than 2 Pages)

VOLUME I, Technical (No more than 56 Pages) Section A - Technical/Management Approach for Potential Technical Direction Letters (PTDLs)

Subfactor 1 PTDL #1: NILE Software/Hardware Maintenance, Systems Engineering and NILE Configuration/Data Management Subfactor 2 PTDL #2: LLC 7M Independent Verification and Validation (IV&V) Subfactor 3 PTDL #3: Wideband HF/Independent Sideband Modulation Implementation

Section B - Past Performance

Section C - Qualifications of Key Personnel

VOLUME II, Cost/Price (No Page Limit)

VOLUME III, Contractual (No Page Limit) Section A - Proposal Cover Letter Section B - Contract Forms Section C - Representation and Certifications Section D - Exceptions to RFP

(b) Format, Organization and Content

(1) Format

(A) Each volume shall be a separate file and contain sufficient information to permit a detailed evaluation.

Data previously submitted, if any, will not be used in the evaluation of your response to this Request for Proposal.

Previously submitted data shall not therefore be included in your proposal “by reference.”

(B) Electronic Proposals. Electronic proposals shall be prepared so that, if printed, the proposal meets the following format requirements: 8.5 x 11 inch paper; single-spaced typed lines; 1 inch margins; 12-point Times New Roman font for text (does not apply to tables contained within the Technical Proposal or to required attachment submittals); The use of native font on all forms is permitted but not on non-form continuation pages. For Microsoft Office (MS) compatible format; all non-cost files named with .doc or .pdf file extension; hyperlinks are not allowed;

graphics and pictures are allowed. Descriptive file names shall be used for all files and attachments (e.g., “ABC

Technical Proposal,” “ABC Attachment 6, Prime Pricing Model,” “ABC Subcontractor XYZ Attachment 7, Subcontracting Pricing Model”).

(C) The technical volume shall be provided in a “searchable” PDF format (i.e. Optical Character Recognition (OCR) turned on).

(2) Organization

(A) Proposals shall be organized into the volumes, sections and page limitations shown above:

(B) Pages shall be numbered consecutively within each Section, showing volume, section, and page. As an example, page 19 of Section B of Volume I would be numbered I-B-19. Pages in the Cost Volume shall be numbered consecutively. There are no sections in the Cost Volume. As an example, page 62 of the cost volume would be numbered “II-62.” Tables, figures and charts also shall be numbered consecutively in each section and volume using the scheme shown above, with the exception that “Table,” “Figure,” or “Chart” will precede the number where appropriate.

(3) Content

(A) GO/NO-GO CRITERIA: The following requirements are considered Go/No-Go criteria. Offerors shall provide documentation demonstrating compliance with each of these criteria. Offerors that are interested in this solicitation but are unable to demonstrate compliance with all requirements below are encouraged to participate as subcontractors.

a. Offerors shall demonstrate the ability to comply with all U.S. Department of Defense (DoD) security requirements for the handling, storing, testing, and transfer of COMSEC devices and material, including COMSEC devices that are not converted to Controlled Cryptographic Items (CCI), and are therefore U.S. SECRET.

b. Offerors considered to be foreign-controlled in the U.S. shall demonstrate their ability to achieve successful completion of a National Interest Determination (NID) in accordance with the applicable requirements of the U.S. Committee on National Security Systems (CNSS).

c. Offerors shall demonstrate compliance with all applicable requirements of the National Industrial Security Program Operating Manual (NISPOM), and shall specifically demonstrate compliance with all the security requirements contained in the DD254, RFP Attachment 2.

d. Offerors shall demonstrate compliance with all of the following:

i. CAGE CODE (NATO CAGE CODE for foreign companies)

ii. Current System for Award Management (SAM) account (https://www.sam.gov/portal/SAM/#1)

iii. Offeror’s accounting system is adequate for determining costs applicable to the proposed cost-reimbursement contract

(B) Volume I, Technical: The technical proposal shall demonstrate the Offeror’s understanding of the requirements. The proposal shall provide an explanation of the techniques and processes to be used. The Offeror’s discussion in each section must include sufficient detail to allow the Government to adequately evaluate the Offeror’s ability to accomplish the proposal requirements. Wherever relevant, Offerors are encouraged to use cross-references to the essential processes described in any other applicable sections of the proposal, rather than repeating that information in the several sections of this volume. Offerors shall address the following technical evaluation factors:

FACTOR 1: TECHNICAL/MANAGEMENT APPROACH FOR POTENTIAL TECHNICAL

DIRECTION LETTERS (PTDLs) (total 45 pages maximum; 15 pages per subfactor)

Subfactor 1 PTDL #1: NILE Software/Hardware Maintenance, Systems Engineering and NILE Configuration/Data Management (15 pages). The response to this subfactor may be issued as Technical Direction Letter (TDL) #1 to the Offeror who is awarded the contract. See RFP Attachment 1(b) for the

PWS for this prospective TDL. Offerors shall propose their technical/management solution to prospective TDL #1. The solution shall include a technical and management approach as follows:

Technical Approach: The Technical Approach shall contain a description of how the solution will:

Deliver the technical outputs required by TDL #1 PWS.

Meet or exceed NILE requirements for any modification/improvement to the NILE Products.

Safeguard the current system requirements during requested modifications.

Minimize logistics requirements and enhance operations throughout the lifetime of the project.

Support NILE Nations system implementation and maintenance needs.

Support a Lab environment for Link 22 system requirements and integration tests.

Provide tested SW “Block Cycle” releases which are suitable for operational deployment by the NILE Nations.

Management Approach: The Management Approach shall include:

A description of how the solution will deliver the outputs required by TDL #1.

A description of how the solution will deliver support to the NILE PMO ISS effort, in terms of Project and Configuration Management A description of how the solution will deliver support to Link 22 related international meetings providing Link 22 subject matter expertise.

A list of any additional Government Furnished Property, Information, Software and Facilities above and beyond what is included in Attachment 5 to the solicitation, including any equipment to be purchased to support the delivery of the technical and management objectives of TDL #1 .

A schedule for completion of tasks and delivery of outputs.

The Offeror’s approach to risk management in satisfying the project requirements. Offerors shall identify critical risks and issues, and shall describe their overall approach to identifying and managing all significant technical risks. Critical risks/issues and proposed mitigations shall be described.

Subfactor 2 PTDL #2: LLC 7M Independent Verification and Validation (IV&V) (15 pages). The response to this subfactor may be issued as Technical Direction Letter (TDL) #2 to the Offeror who is awarded the contract. See RFP Attachment 1(c) for the PWS for this prospective TDL. Offerors shall propose their technical/management solution to prospective TDL #2. The solution shall include a technical and management approach as follows:

Technical Approach: The Technical Approach shall contain a description of the how the Offeror will:

Validate the LLC 7M against the Link 22 system requirements (excluding requirements relating to the encryption/decryption algorithm).

Verify that the LLC 7M meets the requirements of the Link 22 community.

Deliver the technical outputs required by TDL #2 PWS.

Management Approach: The Management Approach shall include:

A description of the methodology to be used by the Offeror to undertake the IV&V tasks.

Any requirements for Government Furnished Property, Information, Software and Facilities including any equipment to be purchased to support the delivery of the technical and management objectives of TDL #2.

A schedule for completion of tasks and delivery of outputs.

The Offeror’s approach to risk management in satisfying the project requirements. Offerors shall identify critical risks and issues, and shall describe their overall approach to identifying

Subfactor 3 PTDL #3: Wideband HF/Independent Sideband Modulation Implementation (15 pages).

The response to this subfactor may be issued as Technical Direction Letter (TDL) #3 to the Offeror who is awarded the contract. See RFP Attachment 1(d) for the PWS for this prospective TDL. The Offeror shall propose its technical/management solution to prospective TDL #3. The solution shall include a technical and management approach as follows:

Technical Approach: The Technical Approach shall contain a description of how the solution will:

Meet or exceed current Link 22 system performance and requirements Fit within the existing system architecture supporting Media Setting Number (MSN) transition.

Minimize cost impacts of potential interoperability issues.

Minimize cost associated with future capability enhancements to the system.

Minimize logistics requirements and enhance maintenance and operations throughout the lifetime of the project.

Management Approach: The Management Approach shall contain:

A description of how the solution will support backward compatibility.

A description of how the solution will support conformance and interoperability tests.

Any requirements for Government Furnished Property, Information, Software and Facilities including any equipment to be purchased to support the delivery of the technical and management objectives of TDL #3.

A schedule for completion of tasks and delivery of outputs.

A list of equipment which must be purchased in order to deliver the requirement of TDL #3.

The Offeror’s approach to risk management in satisfying the project requirements. Offerors shall identify critical risks and issues, and shall describe their overall approach to identifying

FACTOR 2: PAST PERFORMANCE (total 9 pages maximum; 3 pages maximum (form plus 2 pages for each experience))

Offerors shall provide a description of those recent efforts by their organization or by major subcontractors (last three years) that best demonstrate management, cost, schedule, and technical past performance.

Offerors shall provide information on up to three (3) previous Government contracts whose effort was most relevant to the effort required by this solicitation using the Relevant Experience Form (See Attachment 8;

three page maximum to describe each experience). (Government contracts may be a contract with any NILE Nation.) Relevant Experience Forms shall be for either the Offeror (Prime) or a major subcontractor, which is defined as a subcontractor that is proposed to perform at least 25% of the total proposed value of all labor CLINs. (The labor CLIN total includes proposed indirect costs and proposed fee. If there are differences between the prime offeror’s proposed subcontractor value for a subcontractor and the proposed subcontractor’s value submitted separately with all proprietary rates, the lesser value will be considered in determining if a subcontractor meets the definition of major subcontractor.) Relevant Experience Forms completed by subcontractors that do not meet the definition of a major subcontractor will not be evaluated.

Offerors shall provide a full description of the proposed subcontractor(s) relevant experience, the division of PWS tasks, and the percentage of work performed. The contracts provided should have been performed, but not necessarily completed, within the last three (3) years. If the Offeror has not had Government contracts within the last three (3) years, information on relevant subcontracts may be submitted instead.

If available, Offerors shall attach Contractor Performance Assessment Reporting System (CPARS) evaluations (or equivalent) for each experience identified and performed under U.S. contracts. If CPARS evaluations are unavailable, or for contracts with other NILE Nations, Offerors shall provide one Past Performance Questionnaire (PPQ) (See Attachment 8), to the references listed in Block 9a/9b of the Relevant Experience Forms, for each experience identified. Offerors shall request that the references complete the form and send it as an email attachment to Mary Kopa at mary.kopa@navy.mil. The completed PPQs shall be received by the Government no later than the proposal due date and time. However, the Government evaluation team may consider past performance information received after this date and time. The Government evaluation team reserves the right to contact references for verification and/or additional information.

The following types of experience are considered to be relevant to this solicitation. (listed in descending order of relevance):

Link 22 and other Tactical Data Links (operational and testing software), particularly in the area of In-Service or System Integration/Implementation Support

Data Link Processors within Tactical Data Systems for NILE Nations applications Command, Control, Communications, Computers and Intelligence (C4I) systems for NILE

Nations military applications.

Experience with large software development efforts for NILE Nations military applications

FACTOR 3: QUALIFICATIONS OF KEY PERSONNEL (2 pages maximum)

Certain experienced, professional and technical personnel are essential for successful accomplishment of the work to be performed under this contract. These are defined as “Key Personnel.” Offerors shall propose personnel demonstrating relevant education, qualifications and experience, and expertise. Offerors shall submit one (1) resume for each of the (2) Key Personnel (Program Manager and Principal Systems Architect). Resumes shall contain sufficient detail to demonstrate that proposed personnel possess the qualifications and experience to enable successful performance of the PWS. Offerors shall demonstrate how the proposed Program Manager and Principal Systems Architect meets or exceeds the following desired experience and qualifications:

Program Manager

i) Project Management Professional (PMP) or Association for Project Management Practitioner

Qualification (APM PQ) or equivalent

ii) Minimum of 5-years of experience within the last 8 years in Project/Program

iii) Bachelor and/or Master's degree in Project Management, Business Management or in a relevant discipline

Principal Systems Architect

i) Minimum of 3 years of experience within the last 5 years in Tactical Data Links

ii) Software Design experience

iii) Communications Engineer experience

iv) Test Engineer experience

v) Bachelor and/or Master's degree in computer science or other IT-related field

(C) Volume II, Cost: Provide information described below:

(1) General Instructions for the contract cost proposal –

a. Information relating to the Cost Proposals shall not be included in Volume I, Technical Proposal.

Information provided must be consistent with the Offeror’s disclosed accounting practices. Cost proposals shall be complete and detailed cost breakdowns and shall include all elements of cost and such other data as considered appropriate to support your proposal. See FAR Part 15 Table 15-2. Offerors shall use Solicitation Attachment 6 – “Prime Pricing Model” for the cost proposal. The file shall be submitted in Microsoft Excel (compatible with 2010) with formulas and computations intact. All Subcontractors shall submit cost proposals using Solicitation Attachment 7 – “Subcontractor Pricing Model”. The file shall be submitted in Microsoft Excel (compatible with 2010) with formulas and computations intact. The cost proposals and accompanying narrative shall address the following:

Labor costs shall be detailed by labor categories, hours by category, direct and indirect rates, costs and factors. Information provided shall be consistent with the Offeror’s disclosed accounting practices and shall identify how the direct and indirect rates were derived. Offerors shall identify the basis for the various cost elements for which each rate is applied. The base to which each indirect rate/factor is applied shall be identified. Formulas showing the application of each indirect rate shall be included.

b. Direct Labor. In preparing the Cost Proposal, Offerors must identify the labor category and either a named current employee, a named intended employee, or state “TBD” in the direct labor category column.

The straight time hourly rates shall use a forty-hour week for the conversion of salaried employees to the hourly basis and shall be exclusive of loading factors; e.g., vacation, sick leave, holidays, overhead, G&A, and fee. Offerors shall ensure that they utilize the annual salary divided by 2,080 hours to equal the unloaded direct hour labor rate. Offerors (Prime and all Subcontractors) shall identify on Attachments 6 and 7 (Prime Pricing Model and Subcontracting Pricing Model) the Current Actual Labor Rates. Offerors shall specify whether or not uncompensated overtime is included in their proposal for the Prime and all Subcontractors. (See Sections L-X and M-X).

In order to verify the realism of the Offeror’s proposed direct labor rates, Offerors (including proposed subcontractors) who do not have current fiscal year direct labor rate information as a Forward Pricing Rate Agreement (FPRA) on file with DCAA shall submit, as part of their Cost Proposal, documentation substantiating the accuracy of their proposed direct labor rates. Acceptable documentation may include the following:

(1) Payroll data (if proposing current, named employees);

(2) Recent CDRL Monthly Status Reports (MSR) including names and rates (if proposing current, named employees);

(3) Copies of signed Letters of Intent that indicate agreed upon annual salary (if proposing named, new hires);

(4)Forward Pricing Rate Recommendation (FPRR), or Forward Pricing Rate Proposal (FPRP) with supporting documentation explaining the methodology for deriving the FPRPs;

(5) If labor category averages are used consistent with the Offeror’s accounting practice and approved by DCAA, provide a detailed narrative and include the calculation used to establish the category average. For example, provide a list of the current salaries for all employees working in that labor category, divided by the number of current employees in that labor category. If job classification tables or blended rates between job titles are used, provide a detailed explanation to crosswalk the Government’s labor category and the Offeror’s proposed rate for that labor category;

(6) A comprehensive description of the methodology used to establish the proposed direct labor rate (if proposing rates that do not fall within one of the above criteria). This comprehensive description shall include both the source from where the rate was obtained and a description of how the resulting rate was calculated. Merely stating that a “salary survey” or “market survey” was used in insufficient, but rather the Offeror shall detail the recognized national/regional compensation surveys and studies of professional, public, and private organizations used in establishing the total compensation structure.

c. Direct Labor Escalation. If the Offeror (prime and subcontractors) proposes direct labor rates in the base period that are different than the rates specified in Attachment 5 for the Prime and Attachment 6 for the Subcontractors under the column heading “Actual Current Labor Rate”, an explanation (i.e. how the actual current labor rates were escalated by a specific percentage) and calculation methods shall be provided for the difference to equal the direct labor rates proposed in the base period. Annual escalation rates shall be proposed at a minimum of 2.0% for each option year after the base year unless an Offeror has a current FPRR/FPRA on file with DCAA that dictates an escalation rate lower than 2.0%. Offerors shall not propose lower direct labor rates in the option years.

d. Indirect Rates. This data shall include the Offeror’s fringe benefit, overhead (100% at contractor site), General and Administrative (G&A), and Materials and Subcontracts (M&S) handling rates, as applicable, to the Offeror’s accounting system. If proposing indirect rates significantly different from current or prior fiscal year DCMA Forward Pricing Rate Agreement (FPRA) or Forward Pricing Rate Recommendation (FPRR), the Offeror shall include a detailed explanation and supporting cost data (including budget information).

(1) Fringe Benefits. If applicable and in accordance with the Offeror’s normal accounting procedures, identify the fringe benefit rate(s) and total fringe benefit cots being proposed and identify the cost elements for which the fringe benefit rate is being applied. Additionally, provide a narrative listing/description of the fringe benefits applicable to the professional employees proposed to be employed under the resulting contract.

(2) Overhead. Identify the current and projected overhead rate(s) and total overhead cost being proposed under this solicitation and identify the cost element for which overhead is being applied.

Separately identify Government-site and Contractor-site rates, if applicable.

(3) Material & Subcontactor (M&S) Handling. If applicable, identify the rate, cost proposed, and cost elements to which the M&S Handling rate is applied.

(4) General & Administrative Expense. Identify the G&A rate(s) and the total G&A cost proposed and identify the various cost elements for which the G&A rate is being applied.

e. Other. If Facilities Capital Cost of Money (FCCOM) is proposed, Offerors shall submit a completed DD Form 1861 entitled "Contract Facilities Capital Cost of Money" and Form CASB-CMF “Facilities Capital, Cost of Money Factors Computation.” Documentation supporting the computations shall be submitted with the forms. Data is not separately priced; however, the costs associated with producing the Contract Data Requirements List (CDRL) items shall be included in the supporting CLINS.

f. Identification and Type of Subcontract. Subcontractor costs (if applicable) shall be identified in the proposal. The prime’s proposal shall provide a list of subcontractors by name, specify the type of contract (e.g. CPFF, FFP, or T&M), and include and itemize the cost for each subcontractor. If the prime has a DCMA approved Purchasing System, the cost proposal shall contain documentation of the prime’s evaluation of the sub’s cost/technical proposal. If the prime does not have an approved Purchasing System, or does not submit the aforementioned evaluation, a fully-disclosed cost proposal shall be submitted for each subcontractor proposed by the prime. Subcontractors may submit their proposal with the prime’s proposal or directly to the Government. All proposed subcontractors without an adequate accounting system as determined by DCAA for use on a cost reimbursement contract shall be proposed as a FFP or Time and Material (T&M) proposal.

g. Accounting System. Offerors are advised that they must have an adequate accounting system for determining costs applicable to this cost reimbursement contract in order to be eligible for award. If available, the Offeror shall provide a copy of the report from the cognizant DCAA or DCMA office stating that the Offeror’s accounting system is adequate for accumulation, reporting, and billing of costs under a cost reimbursement contract.

h. Purchasing and Estimating System. Offerors shall provide a status of their purchasing and estimating system. Offerors shall provide a copy of the report from the cognizant DCAA or DCMA office as supporting documentation, if available.

i. Fee. Fee may be proposed on both prime and subcontracted costs. All components of proposed fee shall be itemized and the base to which each component is applied shall be identified. Do not propose fee on FCCOM, Other Direct Costs (ODCs), or any indirect costs that are applied to ODCs.

j. Totals. Sum of all the above cost elements and fee. Offerors (Prime and all Subcontractors) shall provide spreadsheets for each of the following: Base year, Option 1, Option 2, Option 3, and Option 4 and a spreadsheet of the total for all five (5) years. Offerors shall round to two (2) decimal places and shall ensure that MS Excel files, when printed, are legible (i.e., not tiny print).

Offerors (Prime and Subcontractors) are specifically cautioned NOT to provide their cost proposal (or their subcontractor’s cost proposal) in a format such that each direct labor rate is loaded with the indirect rates and fixed fee, to equal fully loaded rates for individual labor categories. Offerors are required to ensure that both the prime and subcontractors utilize the format provided in Attachment 6 for the Prime and Attachment 7 for Subcontractors to present their cost proposal in the specified format (with formulae intact).

k. Other Direct Costs (ODCs). Offerors shall propose ODCs EXACTLY as specified in paragraph 3(b) below.

l. Other Hardware. Offerors shall propose exactly the amounts for Other Hardware as specified in paragraph 3(d) below. Offerors shall submit supporting price information as to enable the Government to determine the overall price proposed for the FFP CLINs to be fair and reasonable.

(3) Basic Contract Cost Proposal – The Offeror shall breakout its cost proposal for the Basic Contract by CLIN. The Offeror shall propose the following CLINs:

a) CLINs X001 and X004 – (Cost Plus Fixed Fee). This contract is predominately for the acquisition of services. CLINs X001 and X004 are for services required under this Contract, which shall be further defined via Technical Direction Letters (TDLs). Offerors shall propose labor costs in accordance with the Government estimate of future Level of Effort (LoE) by labor category. Costs shall be totaled or ‘rolled up’ to the CLIN level. The LoE provided is for proposal purposes only and represents the Government’s current best estimate of requirements. Actual contract performance may vary from this estimate. Accordingly, the Government cannot guarantee the contractor will perform either the estimated quantities of staff hours shown for individual labor categories or the total estimated staff hours. In the event that the Offeror's labor category designations do not align precisely with the Government labor category designations, Offerors may use their own labor category designations and provide a cross reference to the Government labor categories. The Government's estimate of annual LoE, by labor category, is provided in the table below.

Labor Category Base OY1 OY2 OY3 OY4 Total

CLIN (NILE PMO) 0001 1001 2001 3001 4001

Program Manager 1,460 1,460 1,460 1,460 1,460 7,300

Principal Systems Architect 1,000 1,000 1,000 1,000 1,000 5,000

Applications Programmer (Sr) 1,000 1,000 1,000 1,000 1,000 5,000

Software Systems Engineer (Sr) 2,500 2,500 2,500 2,500 2,500 12,500

Applications Programmer (Mid) 2,500 2,500 2,500 2,500 2,500 12,500

Computer Security Systems Specialist (Mid) 1,000 1,000 1,000 1,000 1,000 5,000

Applications Programmer 2,000 2,000 2,000 2,000 2,000 10,000

Quality Assurance Manager 200 200 200 200 200 1,000

Web Architect 200 200 200 200 200 1,000

Mgmt/Contracts/Financial Specialist 200 200 200 200 200 1,000

Test Engineer (Mid) 2,000 2,000 2,000 2,000 2,000 10,000

Configuration Management Specialist (Mid) 500 500 500 500 500 2,500

Network Engineer 1,000 1,000 1,000 1,000 1,000 5,000

Subject Matter Expert (Sr) 500 500 500 500 500 2,500

Total 16,060 16,060 16,060 16,060 16,060 80,300

Labor Category Base OY1 OY2 OY3 OY4 Total

CLIN (NATION-SPECIFIC) 0004 1004 2004 3004 4004

Program Manager 146 146 146 146 146 730

Principal Systems Architect 100 100 100 100 100 500

Applications Programmer (Sr) 100 100 100 100 100 500

Software Systems Engineer (Sr) 250 250 250 250 250 1,250

Applications Programmer (Mid) 250 250 250 250 250 1,250

Computer Security Systems Specialist (Mid) 100 100 100 100 100 500

Applications Programmer 200 200 200 200 200 1,000

Quality Assurance Manager 20 20 20 20 20 100

Web Architect 20 20 20 20 20 100

Mgmt/Contracts/Financial Specialist 20 20 20 20 20 100

Test Engineer (Mid) 200 200 200 200 200 1,000

Configuration Management Specialist (Mid) 50 50 50 50 50 250

Network Engineer 100 100 100 100 100 500

Subject Matter Expert (Sr) 50 50 50 50 50 250

Total 1,606 1,606 1,606 1,606 1,606 8,030

b) CLINs X002 and X005 – (Cost-Only, Non-fee Bearing). It is anticipated that travel and incidental materials will be required under this contract. For the purpose of establishing the CLIN ceiling, the Offeror shall propose a ‘lump sum’ cost exactly in accordance with the Government estimate;

however, Offerors shall include applicable burdens i.e. G&A, in accordance with the Offeror’s disclosed accounting practices. ODC costs shall not be fee bearing, i.e. this is a cost only CLIN This estimate is for proposal purposes only and the Government cannot guarantee the total estimated amount will be utilized during contract performance. Failure of ODC amounts to materialize during actual contract performance, or conversely if exceeded, shall not constitute a constructive change or breach of the contract. ODC costs shall not be fee bearing, i.e. this is a cost only CLIN. The Government’s best estimate of ODC items is set forth in the table below.

Base OY1 OY2 OY3 OY4 TOTAL 135,000$ 137,700$ 140,454$ 143,263$ 146,128$ 702,545$

X002

25,000$ 25,500$ 26,010$ 26,530$ 27,061$ 130,101$

X005

c) CLIN X300 – This CLIN is Not Separately Priced (NSP). Hence, the cost proposal shall not list costs for this CLIN. Any costs associated with producing the CDRL items shall be included in the other supporting CLINS.

d) CLIN X006 – (Cost Plus Fixed Fee, Optional Base Period and Four (4) One-Year Option CLINs).

It is anticipated that during performance of the contract, additional hardware may be required to support the NILE Compatibility Laboratory. The exact items are unknown at this time. For the purpose of establishing the CLIN ceiling, the Offeror shall propose a ‘lump sum’ cost exactly in accordance with the Government estimate. Offerors shall include applicable burdens and fee, not-to-exceed 3%.

This estimate is for proposal purposes only. This is an optional requirement and the Government cannot guarantee it will be exercised, or if it is excerised, that the total estimated amount will be utilized during contract performance. Failure of the amount of the additional hardware to materialize during actual contract performance, or conversely if exceeded, shall not constitute a constructive change or breach of the contract. Other hardware costs shall have limited fee, not-to-exceed 3%. The Government’s best estimate of other hardware items is set forth in the table below.

100,000$ 100,000$ 100,000$ 100,000$ 50,000$ 450,000$

X006

e) CLIN X007, X008, X009, X010 – (Firm Fixed Price, Optional Five (5) Year Ordering Period). It is anticipated that UHF EPM radios in accordance with Section 5.2.4 of the PWS may be required during performance of this contract. Offerors shall propose a Firm Fixed Price for the radios at a quantity of 1 each or propose Economic Pricing Quantity per the table in Section B. This is an optional requirement and the Government cannot guarantee it will be exercised.

(C) Volume III, Contractual:

(1) Proposal Cover Letter. The proposal shall be accompanied by a letter of transmittal prepared on the Offeror’s letterhead stationery and signed by an executive of the company who possesses actual authority to contractually bind the Offeror. The cover letter shall be provided by the Offeror (Prime) and all Subcontractors and shall identify all enclosures being transmitted as part of the proposal, shall acknowledge receipt of all RFP amendments (if any are issued), and shall indicate that no exceptions are taken to the terms and conditions of the RFP. In addition, the Prime Contractor shall provide a list of all Subcontractors by name and shall specify the type of subcontract (e.g. CPFF or Labor Hour). The letter shall reference the RFP number and acknowledge that it transmits an offer in response to the RFP. The Offeror shall indicate in the cover letter that the proposal is in compliance with each requirement of the RFP. The letter must provide the Offeror’s point of contact for questions or clarifications regarding the proposal. The cover letter shall state that the proposal will remain valid for no less than 180 calendar days from the date the proposal is submitted.

(2) Signed SF 33 with acknowledgement of all amendments in blocks 12 through 18. The SF33 is used to solicit written offers which, when accepted in writing by the Government, will create a binding contract without further action. Amendments, if any, shall be signed and returned to the Government.

(3) Sections C- K Filled in by Offeror. Fill-in clauses shall be completed and returned with the proposal.

Special attention is directed to Section K Clause 252.227-7017 Identification and assertion of use, release or disclosure restrictions (JUN 1995). In addition to the other Section K provisions to be filled in, this provision must be signed and returned to the Government even if no rights are asserted.

(4) Responsibility Information. Offerors shall submit the following information as part of their proposals:

A. Offerors currently being audited, or that have been audited by the Defense Contract Audit Agency (DCAA), shall provide the address, current telephone number, and current point of contact for the cognizant DCAA and the cognizant Defense Contract Management Agency (DCMA) office. Offerors shall include the most recent FPRP audit status (e.g., date of most recent audit, findings.) and the most recent financial capabilities audit, if performed by

DCAA.

B. A summary of the Offeror’s:

(1) Accounting procedures and controls: Identify the fiscal year for direct and indirect rate computation purposes. Identify the date the Accounting System was determined to be adequate by the cognizant ACO/DCAA. Identify the date the Offeror’s Disclosure Statement as approved by the cognizant ACO.

(2) Property control system: Identify the date the property system was approved by the cognizant ACO.

(3) EEO and VETS-4212: Provide evidence of compliance (FAR subpart 22.8 and

22.13)

(4) Equipment and facilities relative to this effort.

(5) Purchasing System and Estimating System: Identify the date the Purchasing System and Estimating System were approved by the cognizant ACO.

(6) Name and address of the cognizant Defense Security Service (DSS) office.

(7) DUNS Number, Tax Identification Number, and Cage Code (Offeror only).

C. Time and Date for Receipt of Proposals.

Refer to Block 9 of the SF33 for the time and date for receipt of proposals

(End of Summary of Changes)