Amendment_0012.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, 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.)

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)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

W91CRB

ACC-APG - DIVISION D (W91CRB)

6515 INTEGRITY COURT

APG, MD 21005-3013

REM D NGO

EMAIL: REM.D.NGO.CIV@MAIL.MIL

W91CRB-19-R-5001

2018NOV07

X

X

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 10

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: REM D NGO

Buyer Office Symbol/Telephone Number: CCAP SCD/(410)306-2667

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

3.3.2.6 Proposed Backup Transmitting Equipment

Reference: The contractor shall supply and install a fiber (terrestrial) or space (VSAT) backup service route.

Q 95:

Question: Will the Government confirm the backup service route is between the primary hub in Iraq and the contractors proposed back up hub?

Answer:

Yes, it is.

Q 96:

Question: Will the Government explain the services that must be able to use the back up service route?

Answer:

The services that are on the primary iDirect hub located in Baghdad are the services which will use the backup service route. This includes all TDMA and SCPC links, inclusive of all voice and data networks.

Q 97:

Question: Will the Government confirm that the backup service route is an always-on requirement?

Answer:

This is for the offeror to propose.

Q 98:

Question: If the backup service route is space (VSAT) based, does the required space segment bandwidth come from the proposed contract

CLINs for the fixed sites?

Answer:

Yes, the bandwidth will be provisioned from the CLINS in the pricing spreadsheet. However, the offeror shall indicate the bandwidth increment which is required to be procured based on their backup service route solution. This is in addition to the base bandwidth/space segment which will be required under the PWS and contracted for in a Delivery Order.

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

3.1.2 Configuration Management

Reference: The system baseline configuration shall be established at Critical Design Review (CDR), after which the Contractors

Configuration Management Plan shall incorporate a change control process that includes submittal of the Contractor shall procure and provide a Configuration Status Accounting System software releasable to the Government and customer, throughout the life of the contract.

Q 99:

Question: Will the Government clarify the requirements for the schedule and content of the Critical Design Review?

Answer:

This will be required as needed and contracted for in a Delivery Order but only pertains to the acquisition of equipment that will be integrated and installed under this contract, ie the backup service route.

Q 100:

Question: Will the Government provide additional details for the Configuration Status Accounting System software releasable to the

2 10

W91CRB-19-R-5001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Government and customer including which CLIN will be used and end user licensing requirements?

Answer:

Refer to VSATPRICE_28_November_2018.xlsx, PWS Reference Column, Column C for each year for the PWS paragraph number which corresponds to the scope required under PWS Paragraph 3.1.2 Configuration Management. This column references all the applicable PWS paragraph(s) to be priced for each corresponding CLIN.

The offeror shall propose their end user licensing requirements as part of their solution for the Configuration Status Accounting System software.

VSATPRICE_28_November_2018.xlsx

Q 101:

Question: What CLIN= should be used to price the backup service route in Year 1 and Year 5?

Answer:

The backup service route is not required for Years 1 and Year 5. Pricing and scope are only required for years 2, 3, and 4.

Q 102:

Question: Will the Government confirm that CLINs 0005ae Backup Service Route Installation and 0005af Backup Service

Route Installation are not installation but 1 week or 1 month respectively of the backup service route?

Answer: SLINS 0005ae and 0005af are for the installation of the backup service route equipment which will be procured/ordered from SLIN

0004bv and is required under PWS paragraph 3.3.2.6.

Q 103:

Price Evaluation Approach states that failure to price all requirements of this solicitation in the excel pricing spreadsheet will result in the offerors proposal being eliminated and not considered for award. However, for the mobile network, contractors are given the option of bidding the IS20 MHz CLINs or an alternative satellite option. Therefore, one of the mobile network CLIN sections will not be proposed/valued. Does this mean the contractors price proposal will be eliminated and not considered for award since not all CLINs were proposed?

Answer:

Refer to page 3 of the solicitation, CLIN 0002, Under VSATPRICE.xls, Pricing only required for 1 Satellite, IS-20 or Alternative

Satellite. Since the pricing spreadsheet was updated and renamed in Amendment 0007, this reference is now

VSATPRICE_28_November_2018.xlsx. Using this spreadsheet, pricing is only required for the SLINs under CLIN 0002 which correspond to the offerors proposed mobile satellite IS20 OR Alternative. The offerors proposal will not be eliminated from consideration if pricing is not provided for the SLINs associated with the satellite not being used or proposed. Offerors shall input NSP for the mobile satellite

SLINs under CLIN 0002 they do not intend to propose. For example, if the offeror proposes IS-20 satellite, the offeror is only required to input/provide pricing for the IS20 SLINs 0002aa-0002at and shall input NSP for the Alternative Satellite SLINs 0002au-

0002bm and vice versa.

Q 104:

Section L, Volume IV states an authorized official must sign the SF1449, but the Solicitation was released on the SF33. Shall we assume the SF1449 comment was incorrect and complete/sign the SF33? (SF1449 also referred to in

Section L-6

Answer:

Answer: Section L,. Volume IV and Section L-6 are now corrected to state "An authorized official of the firm shall sign the SF 33".

Revision 2. See Section L of this amendment.

Q 105:

Section L, Volume IV states each offeror shall complete the solicitation sections indicated below provided with the solicitation (A, G, and K).

* Section G - There is not a requirement area to be completed or signed. What do we do with Section G?

* Section K As we are registered/updated in SAM.Gov, we are only responsible to complete paragraph (b) and there is not a requirement to sign the Section K, so what are we to do with the entire Section K that is not applicable?

Answer:

3 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Section G Please review all the information provided in Section G, this is the Contract Adminstrative section and the information provided is to assist in the preparation of your proposal and future planning if an award is made to your firm.

Section K , Please review all the information provided in Section K and return only the information required.

*** END OF NARRATIVE A0013 ***

4 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

Revision 2

D. PROPOSAL SUBMISSION (Section L)

1. INTRODUCTION. ____________

a. The offerors proposal shall be submitted electronically via email to rem.d.ngo.civ@mail.mil and victoria.m.dorsey.civ@mail.mil. The offerors proposal shall consist of four volumes. The Volumes are I -Technical, II Past Performance, III Excel Pricing Spreadsheet, VSATPRICE 28 November 2018.xls, and IV - Solicitation, Offer and Award Documents and Certifications/Representations. Files shall not contain classified data. The use of hyperlinks in proposals is prohibited. WARNING: Please do not wait until the last minute to submit your proposals! To avoid submission of late proposals, we recommend the transmission of your proposal file 24 hours prior to the required proposal due date and time. Offerors are encouraged to practice submitting proposals in the DEMO section of the FBO portal in order to gauge the length of transmission via the Internet.

(1)Offerors are advised that employees of the firms identified below may serve as nongovernment advisors in the source selection process. These individuals will be authorized access only to those portions of the proposal data and discussions that are necessary to enable them to perform their respective duties. Such firms are expressly prohibited from competing on the subject acquisition.

Bowhead Technical Services

Dimitra Bairaktaris and Steven Cooper

4900 Seminary Rd. Suite 1200

Alexandria, VA 22311

ACSYES Inc.

Frank Vento, Jennifer Connell, Jason Graham and John Arsenault

6170 Guardian Gateway, Ste 118

Aberdeen Proving Grounds, MD 21005

(2) In accomplishing their duties related to the source selection process, the aforementioned firms may require access to proprietary information contained in the offeror proposals. Therefore, pursuant to FAR Part 9.5054, these firms must execute an agreement with each offeror that states that they will (1) protect the offerors information from unauthorized use or disclosure for as long as it remains proprietary and (2) refrain from using the information for any purpose other than that for which it was furnished.

The Government intends to make a single contract award without discussions in accordance with FAR 52.212-1(g). However, the Government reserves the right to conduct discussions if later determined by the Contracting Officer to be necessary.

2. PROPOSAL FORMAT. _______________

a. Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly ______ identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents should be created using the Table of Contents feature in MS Word. MS Word (.doc) files shall use the following Page Setup parameters:

Margins Top, Bottom, Left, Right - 1

Gutter 0

From Edge Header, Footer - 0.5

Page Size, Width 8.5

Page Size, Height 11

The following additional restrictions apply:

Each paragraph shall be separated by at least one blank line. A standard, 12-point

5 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

minimum font size applies. Arial or Times New Roman fonts are required. Tables and illustrations may use a reduced font size not less than 8-point and may be landscape.

Proposal page limits are as follows:

a. Technical Proposal 75 pages maximum

b. Past Performance Proposal - no page limit

c. Price Proposal no page limit

Pages that exceed the page limits above will be deleted and will not be evaluated. Page numbers, headers and footers may be within the page margins ONLY, and are not bound by the font requirements. Company logos are prohibited with the exception of the Title Page. Pages that exceed the margin, font or total page limit will not be evaluated. Pages deleted due to violation of the margin or font restrictions will not count against the page limitation. Page count will NOT be based upon the numbers of pages, printed but rather dictated by the number of pages in a print layout view in the application based upon the above-prescribed document settings. Counting pages in the order they appear for viewing will make up the page count. The page limits are applicable to graphs, tables, drawings and any other attachments submitted with the proposals and not specifically excluded by the solicitation. Any index, table of contents, glossary or integrated master schedule will not be included in the maximum page limitation.

b. File Packaging. All of the proposal files shall be compressed (zipped) into one file entitled proposal.zip _______________ using WinZip version 6.2 or later, or as separate uploads in their native format, i.e. doc, xls, ppt, etc. **Please note

Selfextracting.exe files are no longer accepted.**

c. Content Requirements. All information shall be confined to the appropriate file. ____________________

The offeror shall confine submissions to essential matters, sufficient to define the proposal and provide an adequate basis for evaluation. Offerors are responsible for including sufficient details, in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The

Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. The following shall be included in the proposal text:

3. VOLUMES TO BE SUBMITTED. _______________________

VOLUME TITLE

Volume I TECHNICAL

Volume II PAST PERFORMANCE

Volume III PRICE

Volume IV REPRESENTATIONS AND

CERTIFICATIONS,

SIGNED COVER PAGE

4. PROPOSAL CONTENT. ________________

Offeror(s) are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Each

Volume of the proposal shall consist of a Table of Contents, Summary Section and the Narrative discussion. The Summary Section shall contain a brief abstract of the Volume. Proprietary information shall be clearly marked. The following shall be included in the Narrative discussion:

(i) VOLUME I TECHNICAL (75 pages maximum). ______________________________________

(1) Subfactor 1: Provide a paragraph by paragraph response to the PWS.

The offeror shall provide a paragraph by paragraph response to the PWS addressing how they will meet the requirements for each of the following paragraphs and their subparagraphs:

a. Paragraph 4: Support

b. Paragraph 5: Contract Requirements

c. Paragraph 6 Requirements for Final Inspection

d. Paragraph 7: Warranty

e. Paragraph 8: Equipment

6 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The offeror shall also complete and submit a Verification Cross Reference Matrix (VCRM) or Compliance Matrix that maps each PWS and System Requirements Document to the Offerors applicable proposal PWS paragraph number and identifies the methods (analysis, demonstration, inspection, test, etc.) to be used to verify each requirement. The offeror shall submit an Excel table format which lists the PWS paragraph number, the PWS paragraph title heading, and the offerors response.

The offeror MUST NOT MERELY REPEAT BACK the requirements stated in the PWS, but must provide narrative evidence in support of any conclusive statements relating to promised capabilities or performance.

(2) Subfactor 2: Bandwidth and Hub Services. PWS paragraph 3.2 and all sub paragraphs.

The Offeror shall provide details on the satellite vendor/operator proposed to meet the requirements of the PWS, to include but not limited to satellite name, location, end of life, look angles. The Offeror shall provide details on how their help desk will interface to the satellite provider, location of the satellite provider help/support desk, location of the satellite corporate office and primary language spoken. The Offeror shall provide the levels of contracting for the satellite provider

(i.e. direct contract to satellite vendor or through multiple layers of third tier vendors.)

(3) Subfactor 3: Local Internet and Public Internet Protocol (IP) Addresses

PWS paragraph 3.3.1/3.3.1.1

The Offeror shall provide details on the Iraqi Internet Service Providers proposed to meet the requirements of the PWS. The

Offeror shall provide years in service, available plans above the requirements and how the connections will be physically provided to the US Government Customer. The offeror shall provide their plan for delivering the required IP addresses. The offeror shall provide verification that the IPs are usable and indicate the source of the IPs.

(4) Subfactor 4: Remote Technical Support. PWS Paragraph 3.4 and all sub-paragraphs

The Offeror shall provide details on how the Remote Technical Support requirements will be met. The Offeror shall list their corporate experiences, their approach to the helpdesk support and their success factors. The Offeror shall specify the location of the help desk and provide pictures of the help desk operating center and the screens/monitors which will be dedicated to supporting the Iraq VSAT Program. The Offeror shall also specify what software monitoring programs will be displayed during remote monitoring and also specify the alert and notification procedures for reporting outages. The Offeror must indicate how many years of experience it has in using the proposed software application(s) and in which other programs or contracts it has deployed and used the software. Offerors shall propose the labor mix which is associated with the remote technical support to include all labor categories and labor hours. Do not propose labor rates under this section.

(5) Subfactor 5: Satellite Transition Plan. PWS Paragraph 3.3.2 and all 3.3.2.1

The offeror shall provide a satellite transition plan which details all program, technical and logistical factors related to the transition from the existing satellite to the offerors proposed satellite. The Offeror shall identify potential risks and risk mitigation factors. The Transition Plan must include a Gantt chart which details a schedule. The Transition Plan must also propose a labor mix reflecting both CONUS and OCONUS labor and all the proposed labor hours required to perform the

Satellite Transition. Offerors shall not propose pricing as part of the labor mix; only labor categories and labor hours. All assumptions related to the transition should also be stated.

(6) Subfactor 6: Backup Hub Interconnection and Failover Plan: PWS

Para, 3.3.2.3, 3.3.3, 3.3.3.1, 3.3.3.2

The offer shall propose a backup hub plan which shows the interconnection and simultaneous communications between the primary and backup hubs during cutover. The Offeror shall provide details on locations, weather, look angles to the satellite, number of current customers, and yearly average downtimes due to factors outside of satellite unavailability. The plan shall detail the offerors cutover procedures from the primary to the backup hub. The offerors shall demonstrate how it intends to run the two hubs in tandem in order to ensure a transition with thirty (30) minutes or less of downtime.

(7) Subfactor 7: Link Budgets: PWS Para 3.3.2.2, 3.3.3.3

The offeror shall propose link budgets for all terminals identified in Appendix E to the solicitation. Appendix E contains all the minimum technical information the offeror requires to close the satellite links. This enclosure represents a sample of the terminals which need to have link budgets in the Iraq MoD VSAT network. The offeror is to note that a complete link budget analysis for all terminals in the network will be required after contract award as per CDRL C003. Link Budgets must demonstrate that the offeror can close each link and meet the link availability stated in the PWS. The offeror must submit all required Link Budgets identified in the enclosure. The offeror shall take into account all of the following factors when calculating link budgets: the uplink power amplifier gain and noise factors, transmit antenna gain, slant angles and corresponding atmospheric loss over distance, satellite transponder noise levels and power gains, receive antenna and amplifier gains and noise factors, cable losses, adjacent satellite interference levels, and climatic attenuation.

(8) Subfactor 8: Satellite Availability Reports: PWS Para 3.2.1.6

The offeror shall propose and provide its satellite availability report. The offeror must submit a Satellite Availability

Report for each proposed satellite. The Satellite Availability Report must be addressed to the offeror, must be from the

Satellite Operator on the Satellite Operators Letterhead and contain a Satellite Operator point of contact which includes name, email address and phone number. Offerors shall submit a Satellite Availability Report demonstrating satellite transponder

7 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

service with availability of equal or greater to 99.999% within the last 12 months of service.

(9) Subfactor 9: CDRLs Compliance: Section J of the Solicitation

The Offeror shall propose how it will comply with each CDRL and how will the Offeror keep track of the suspense for each CDRL and ensure timely submission.

(10) Program Management Plan: PWS Para 3.1 and all sub paragraphs.

The offeror shall propose a Program Management Plan, to include labor mix of OCONUS and CONUS management and all other staff personnel proposed, to include resumes for key personnel, iDirect and Cisco CCNA Certification documents as required in the

PWS. Offerors shall indicate where the iDirect and CCNA certified personnel will be working during the contract period of performance. The program management plan must indicate by name, and a summary of skills, which personnel will be supporting the Iraq VSAT Program in CONUS and which personnel will support the program in Iraq. If there are plans to rotate personnel, especially in Iraq, the plan must also specify these plans. The Program Management Plan must also indicate if personnel already have Passports and Visas for Iraq and provide Passport and Visa documentation. Key personnel must possess valid

Passports with expirations beyond 1 January 2021.

(11) Corporate Experience

The offeror shall provide evidence of at least three (3) years of corporate experience, providing services relevant to the services identified in this solicitation and PWS. This includes the Offeror and any proposed sub-contractors. Corporate experience must have occurred within the past three (3) years. Offerors shall submit a narrative identifying a minimum of two

(2) examples of corporate experience: one of which shall be an example of the Offeror acting as the prime contractor, and one

(1) example for each proposed subcontractor, if applicable and proposing subcontractors. Offerors must have provided these types of services to either a Government or Commercial entity for at least a two-year period, within the past 3 years. There is no substitution for Corporate Experience if it is not relevant to the PWS.

(ii) VOLUME II Past Performance ___________________________

Past Performance Factor: The Offeror shall submit a description of all Government and industry contracts (prime and major subcontracts) in performance during the past three (3) years, which are relevant to the efforts required by this solicitation.

This includes the Offeror and any proposed subcontractor. For purposes of this solicitation, a relevant contract is defined as any contract requiring performance during the three (3) years prior to the release date of this solicitation which required operations of a primary and backup VSAT system of complexity similar to the products required by this solicitation. Data concerning the prime Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. The

Offeror shall submit similar descriptions for contracts of major subcontractors who will be providing critical hardware or services such as satellite broadband and Ku band services or whose subcontract exceeds 20% of the total proposed contract price. No substitution for Corporate Experience if it is not relevant to the requested services or equipment in the PWS. This volume shall be organized into the following sections:

(1) Section 1 Contract Descriptions. This section shall include the following information in the following format:

(a) Contractor/Subcontractor place of performance, CAGE Code and DUNS Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, email address, and telephone and fax numbers).

(b) Government contracting activity, and current address, Procuring Contracting Officer's name, email address, telephone and fax numbers.

(c) Governments technical representative/COR, and current email address, telephone and fax numbers.

(d) Government contract administration activity and the Administrative

Contracting Officer's name, and current email address, telephone and fax numbers.

(e) Government contract administration activity's Pre-Award Monitor's name, and current email address, telephone and fax numbers.

(f) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase

Agreements, include Delivery Order Numbers also.

(g) Contract Type (specific type such as Fixed Price (FP), Cost Reimbursement (CR), Time & Materials (T&M), etc.) In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc)).

8 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

(h) Awarded price/cost.

(i) Final or projected final price/cost.

(j) Original delivery schedule, including dates of start and completion of work.

(k) Final, or projected final, delivery schedule, including dates of start and completion of work.

(l) Final or projected final delivery schedule

(2) Section 2 -- Performance. Offerors shall provide a specific narrative explanation of each contract listed in Section 1 describing the objectives achieved and detailing how the effort is similar to the requirements of this solicitation.

(a) For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All

Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The Offerors shall also provide a copy of any Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror or proposed subcontractor. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

(3) Section 3 Subcontracts. Offerors shall provide an outline of how the effort required by the solicitation will be assigned for performance within the Offerors corporate entity and among the proposed subcontractors. The information provided for the prime Offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government SOW subparagraph number. This includes all subcontractors who will be providing critical hardware/services or whose subcontract is for more than 20% of the total proposed price.

(4) Section 4 New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the Offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

(5) Past Performance Questionnaire. For all contracts identified in Section 1 above, Past Performance Questionnaire, file named PPQ.doc (See Section J/Appendix D) shall be completed and forwarded electronically to the Government/commercial contracting activity and Government/commercial technical representative responsible for the past/current contract. The Offeror shall complete Part I of the Past Performance Questionnaire and e-mail the Questionnaire to the Government/commercial contracting activity and the Government/commercial technical representative responsible for the past/current contract. (There shall be One (1) Point of Contact (POC) and one (1) contract per questionnaire). The Offeror shall instruct the

Government/commercial POCs to electronically complete Part II of the Questionnaire and e-mail the completed questionnaire to the Contract Specialist, rem.d.ngo.civ@mail.mil, within seven (7) calendar days of receipt. The Offerors shall also e-mail to the Contract Specialist a list of all the POCs who were sent the questionnaires. Receipt of this list by the Government is requested within twenty-one (21) calendar days of the release of the Request for Proposal. The POC list shall be submitted in

Word for Windows Table Format to include the following fields: Solicitation Number, Offeror Company Name, Contract Number, Government Agency, POC Last Name, First Name, POC Title, POC Telephone Number, POC e-mail address, and date e-mailed to POC

(Month/Day).

(iii) VOLUME III PRICE. _________________

The offeror shall submit a price proposal in the Excel Pricing Spreadsheet, VSATPRICE 28 November 2018.xls provided with the solicitation. The evaluated prices for each FFP Contract Line Item Numbers (CLINs) shall be calculated in accordance with the formulas in the Excel Pricing Spreadsheet. Offerors shall follow the instructions in the Excel Pricing Spreadsheet and shall not change the formulas in the Excel Pricing Spreadsheet.

All Offerors must provide pricing for all CLINs/Sub-Line Item Numbers (SLINs), which includes range pricing for orders.

The Offeror is to propose a unit price for each CLIN/SLIN and each range quantity. The evaluation quantities and percentages in the spreadsheet file VSATPRICE 28 November 2018.xls are used for evaluation purposes only.

(iv) VOLUME IV - SOLICITATION, OFFER AND AWARD DOCUMENTS AND _______________________________________________________

CERTIFICATIONS / REPRESENTATIONS.________________________________

9 10

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Certifications and Representations- Each offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the solicitation. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.

Section A Standard Form 33 (SF33), Solicitation, Offer and Award

Section G Contract Administration Data

Section K Representations, Certifications and Other Statements of Offerors

*** END OF NARRATIVE L0002 ***

10 10