HC1019-24-R-0004 AMD 0001.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

See Amendment 01 Description below .

1. CONTRACT ID CODE PAGE OF PAGES

J 1 41

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

16C. DATE SIGNED

BY 10-Sep-2024

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 HC101924R0004

X 9B. DATED (SEE ITEM 11)

03-Sep-2024

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

10-Sep-2024

CODE

DISA/DITCO-PACIFIC

477 ESSEX STREET

BUILDING 77, ROOM 129

PEARL HARBOR HI 96860-5815

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HC101924R0004

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 01 DESCRIPTION

The purpose of Amendment 01 is to:

1. Extend the solicitation due date to September 23, 2024, 1000 HST.

2. Update PWS:

1. to correct paragraph 6.2.2.4(c)(ii), to read “The closest point between two cables shall never be less than 50 meters,” instead of “50 feet”

2. paragraph 12, Security Requirements

3. Remove provision 252.204-7012 and clause 252.204-7019

4. Update Exhibit 3, DD254 with filled in copy

5. Update Addendum:

1. to rename reference in Addendum to 52.212-1(b)(12)((ix)(D) paragraph 6) Representations, Certifications, and other Statements of Offerors from "Mission-Essential Contractor Services Plan" to "Continuation of Essential Contractor Services Plan", and to move that sentence to Paragraph 11) Continuation of Essential Contractor Services. In that reference, updated the reference from "DFARS 252-237-7024" to "DFARS 252.237-7024"

6. Update Exhibit 1, Price Schedule:

1. CLINS X001-X008 tab, CLIN X001 (rows 5 and 7) description to “CEG Gateway Build” and

CLIN X002 (rows 6 and 8) description to “CEG Gateway Service”.

2. to adjust diversity CLINs to TBN (to be negotiated) on CLINS X001-X008 tab.

7. Allow for feedback on missing circuit locations on Attachment A and Exhibit 1 (see Q&A answer to question #28). Feedback and details must be received within 2 business days of the Q&A posting, for consideration for removal from Attachment A and Exhibit 1 for the purpose of this solicitation.

8. Update Attachment A, CEG-DISN Node and Customer Access Site List, to revise the LAT/LONG for HI- S20 and HI-S21

9. Replace Exhibit 6, Solicitation Questions Template with Solicitation Questions and Answers.

**Please be sure to download all Attachments and Exhibits from the solicitation and solicitation amendments. All pervious versions are not valid. ***

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 16-Sep-2024 08:00 AM to 23-Sep-2024 10:00 AM.

The following have been modified:

ADDENDUMS

ADDENDUM TO 52.212-1

Addendum to 52.212-1(b), Submission of Offers is tailored as follows:

(b) Submission of offers:

(12) Other Instructions

(i) General Information

(A) Points of Contact: The contracting officer (KO) and contract specialists (CS) are the sole points of contact for this procurement. Address any questions or concerns you may have to the KO/CS. Written requests for clarification must be sent to the KO/CS at ryan.g.lee.civ@mail.mil and jodie.s.onaga-nuttall.civ@mail.mil.

(B) Debriefings: The KO will notify unsuccessful offerors of the source selection decision IAW FAR 15.503. Upon such notification, unsuccessful offerors may request and received a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable. Excluded offerors are only entitled to one debriefing for each proposal.

(C) Discrepancies: If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the KO in writing with supporting rationale. The Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

(D) Electronic Reference Documents: All referenced documents for this solicitation are available on the Official U.S. Government System for Contract Opportunities website at https://sam.gov, excluding the PWS Attachment A CEG DISN Node and Customer Access Site List. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. To obtain a copy of the PWS Attachment A, offerors shall submit a request to ryan.g.lee.civ@mail.mil and jodie.s.onaga-nuttall.civ@mail.mil.

(E) Communications: Exchanges of source selection information between Government and offerors will be controlled by the KO and CS. Email will be used to transmit such information to the offeror and will include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

(ii) Offerors are requested to submit a written technical proposal and a price proposal in response to the solicitation.

(A) Performance Work Statement (PWS)

(B) Attachments A-F

(C) Exhibits 1-6

(D) Offerors must complete Blocks 6 and 7 of Attachment 5 - DD Form 254 with the appropriate companies information for their and any subcontractors (when applicable). The completed DD Form 254 must be submitted with your proposal.

(E) Offerors are requested to not use proposal background graphics on any of the Proposal Volumes.

(iii) Information on submission of technical and price proposals is provided below.

(A) The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of statements asserted in the proposal.

(B) The proposal shall not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements.

(C) The proposal should sufficiently address the requirements as stated in the PWS.

(iv) Offerors shall assume the Government has no prior knowledge of their facilities and capabilities;

thereby basing proposal evaluation on the information presented in the offeror's proposal. The offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. Non-conformance with these instructions may result in removal of the proposal from further evaluation.

(v) OCCI. IAW DISA Special Contract Requirement H1, each offeror shall specifically identify in its proposal whether or not any potential or actual Organizational and Consultant Conflicts of Interest (OCCI), as described in Federal Acquisition Regulation (FAR) Subpart 9.5, exists for this instant procurement. If the offeror believes that no OCCI exists, the OCCI response shall set forth sufficient details to support such a position. If an offeror believes that an actual or perceived OCCI does exist on the instant procurement, the offeror shall submit an OCCI plan with the proposal, explaining in detail how the OCCI will be mitigated and/or avoided.

(vi) Page Limitations. Page limitations, if applicable, are identified below and will be treated as maximums. Page size shall be 8.5 x 11 inches. Page limitations are identified below under each evaluation factor and will be treated as maximums. If exceeded, excess pages will not be read or considered in evaluation of the proposal. The following items will not be considered when calculating page limits: cover page, table of contents, glossary, OCCI mitigation plans, DD Form 254, any provided Sanitized copies, and Section 508 compliance. In the event any evaluation notices are issued, page limitations may also be placed on those. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and will not be considered part of a proposal. The Government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this

RFP.

(vii) Organization/Number of Copies/Page Limits. The offeror shall prepare the proposal as set forth in the Proposal Organization Table below. The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified. The contents of each proposal volume are described in the information to offerors paragraph as noted in the table below. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

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

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

Table 1 Proposal Organization

VOLUME 52.212-1

Paragraph Number

VOLUME TITLE PAGE LIMIT

I (b)(12)(ix)(A) Executive Summary 5 Pages II (b)(12)(ix)(B) Technical/Management 50 Pages III (b)(12)(ix)(C) Price No page limit IV (b)(12)(ix)(D) Contract Documentation No page limit

(viii) Electronic Offers. The offeror shall submit proposal volumes I through IV in electronic format via email and must include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Each volume shall be a separate file. The total size of email (including all attachments) shall not exceed 20MB. If files are compressed, the file must be a .zip file. Offeror shall email a copy of its proposal to the CS and KO no later than the time and date specified in the solicitation. IAW FAR

52.215-1, Instructions to Offerors, the offeror’s proposal submission will be considered complete when all volumes are received. Proposals shall be submitted to the KO/CS identified below:

Jodie Onaga-Nuttall (CS) – jodie.s.onaga-nuttall.civ@mail.mil Ryan Lee (KO) – ryan.g.lee.civ@mail.mil

(ix) Proposal Organization:

(A) Volume I - Executive Summary. In the executive summary volume, the offeror shall provide the following information:

1) Narrative Summary. The narrative summary of the entire proposal shall be concise, to include addressing any significant risks, and highlighting any key or unique features, excluding price. Any summary material presented in the Executive Summary shall not be considered as meeting or exceeding the requirements for any portions of other volumes of the proposal, nor will it be considered under any of the Evaluation Factors.

2) Table of Contents. Include a master table of contents for the entire proposal.

(B) Volume II – Technical/Management.

1) General. The technical/management volume should be specific and complete; and will be evaluated against the technical/management subfactors defined in FAR 52.212-2, Evaluation – Commercial Items, and the addendum to this clause. The technical portion of the proposal is to be submitted as a Microsoft (MS) Word 2010 or newer or as an Adobe PDF document. The page format shall have a 1-inch margin using no smaller than an 10 point font, either Arial, Times New Roman, or Courier New font for all text, to exclude any text contained in a table or graphic.

Using the instructions provided below, provide as specifically as possible the actual methodology being used for accomplishing / satisfying the factors / subfactors.

2) Format for Specific Content

a. Technical/Management. In the Technical/Management volume, address the proposed approach to meeting or exceeding the minimum performance or capability requirements of each technical/management factor/subfactors, as well as any risks in your proposed approach in terms of technical/performance, price, and/or schedule. Address any technical/management risk by identifying those aspects of the proposal you consider to have the potential for disruption of schedule, increased cost, poor performance, the need for increased Government oversight, and/or the likelihood of unsuccessful contract performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (e.g., PWS/SOW or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic "work-around" or risk mitigation for identified risks that will eliminate or reduce risk to an acceptable level. Identify any new risks introduced by such risk mitigation.

b. Volume Organization. Technical/Management shall be organized as follows:

1) Table of Contents

2) List of Table and Drawings (Excluded from the page limits)

3) Glossary

4) Subfactor 1: Comprehensive Implementation Plan, PWS Section

6.1.1

5) Subfactor 2; Network Service Capabilities, PWS Section 6.2

6) Subfactor 3: Network Service Management, PWS Section 6.3

7) Sanitized version of the offeror’s technical volume without any identifying company letterhead, logos or insignia.

(C) Volume III – Price.

1) General. Price submissions should be sufficiently detailed to demonstrate their reasonableness, as well as Offeror’s methodology to meet all PWS tasks. Offerors should ensure price proposals include detailed information regarding the resources required to accomplish the task. Exhibit 1, Price Schedule, shall be submitted in MSExcel 2016 format or newer. All formulas shall remain present in the spreadsheet for verification. The total size of the email (including all attachments) shall not exceed 20MB.

2) Price Reasonableness and Completeness. Price proposals shall be submitted using the Price Schedule Worksheet, Exhibit 1. The price proposal will be evaluated using one or more of the techniques defined in FAR Part 15.404 in order to determine if it is reasonable and complete. Reasonableness is established through cost and price analysis techniques as described in FAR 15.404.

For a price proposal to be complete, all solicitation requirements must be priced, figures correctly calculated, and prices presented in a clear and useful format.

Note that unreasonably high-proposed prices, initially and subsequently, may be grounds for eliminating a proposal from competition. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be reason to reject an offeror’s proposal.

3) Price Information. Offeror shall submit pricing for the base period and all option periods, including pricing for an additional 6-month extension period that may be authorized IAW FAR 52.217-8. See FAR 52.217-8 which authorizes the Government to require continued performance of any services within the limits and at the rates specified in the contract. Exhibit 1, Price Schedule, shall include a separate line item for the additional 6-month extension period IAW FAR 52.217-8.

These prices shall be identical to the proposed pricing in the 6 months prior to expiration of the base period, or the final option period, if option periods are present.

4) Cost/Price Information. Information beyond that required by this instruction shall not be submitted, unless considered essential to document or support the cost/price position. All information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall the information and documentation from the Price Volume be included elsewhere in the proposal.

5) Cost or Pricing Information Requirements. IAW FAR 15.403-1(b) and 15.403- 3(a), data other than certified cost or pricing data may be required to support price reasonableness. Information shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the KO determines the required conditions of adequate competition do not exist that there is insufficient information available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror may be required to certify its submitted cost or pricing data (see FAR 15.406-2).

6) Volume Organization. Price shall be organized as follows:

a. Table of Contents

b. Exhibit 1, Price Schedule

c. Price Narrative - to include relevant pricing information such as supporting pricing data or data other than cost or pricing information, if necessary.

*CLIN Pricing may be included in the narrative of Volume III – Price as a graphic illustrating the completed Exhibit 1 or the offeror may choose to reference Exhibit 1, Price Schedule in Volume III – Price. However, regardless of the reference in the narrative, Exhibit 1 must be provided as a completed stand-alone excel file.

(D) Volume IV - Contract Documentation.

1) General. The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. Any proposal failing to meet the instructions in volume IV may be reason to reject an offeror’s proposal.

2) Solicitation/Contract Form. Offerors must complete blocks 17a and signature and date for blocks 30 a, b, and c of the Standard Form (SF) 1449. Signature by the offeror on the SF1449 constitutes an offer, which the Government may accept.

3) Supplies or Services and Costs/Prices. Offerors must complete pricing information in Exhibit 1, Price Schedule Worksheet, as a stand-alone excel file.

4) Contract Administrative Data. Offerors must complete “Contractor Point of Contact” of the RFP.

5) Lists of Documents, Exhibits and Other Attachments. The offeror shall provide a Subcontracting Plan (if identified as a large business), a Mission-Essential Contractor Services Plan, and an OCCI Mitigation Plan (or a statement that OCCI does not exist) to be incorporated within the resulting contract.

6) Representations, Certifications, and other Statements of Offerors. The offeror must comply with FAR 52.204-7 entitled “System for Award Management.”

Offerors who are not registered in SAM will be advised of the need to register. An offeror may be determined ineligible for contract award if not registered within SAM at time of award. Offerors are also required to complete additional representations, certifications, acknowledgments and statements. Completed representations, certifications, acknowledgements, and statements are required.

7) Authorized Offeror Personnel. Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. Contractor Point of Contract information will be used for the Contract Administration Data Item G1, Points of Contact.

8) Company/Division Address, Identifying Codes, and Applicable Designations.

Provide company/division's street address, county and facility code; CAGE code;

Unique Entity Identifier (UEI); TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other locations. List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

9) Small Business Subcontracting. A Small Business Subcontracting Plan is also required (FAR 52.219-9) for Other than U.S. Small Businesses ONLY (i.e., Large Businesses). ONLY OTHER THAN SMALL BUSINESS OFFERORS ARE

REQUIRED TO SUBMIT.

A DISA OSBP Subcontracting Plan Checklist is included as Exhibit 4. The document is required to be filled out by the Offeror and submitted with the Subcontracting Plan.

Firms other than U.S. Small Business Offerors, shall submit a Subcontracting Plan meeting the requirements of FAR 52.219-9 and DFARS 252.219-7003 (or DFARS 252.219-7004 if the Offeror has a Comprehensive Subcontracting Plan). Firms other than U.S. Small Businesses shall submit acceptable Subcontracting Plans to be eligible for award. The plan, at a minimum shall address the elements set forth in FAR Clause 52-219-9(d)(1) through (15). Subcontracting Plans shall reflect and be consistent with the commitments offered in the Small Business Participation Plan.

Note: Subcontracting Plans will only be reviewed for acceptability for those Offeror(s) deemed to be apparent awardee(s). If the apparent awardee’s Subcontracting Plan is not initially acceptable, the Contracting Officer may engage in clarifications in regard to the Subcontracting Plan and this shall not be deemed discussions.

Goals for this requirement are:

Small Business: 24% of the total contract value;

Small Disadvantaged Business (SDB) to include 8(a): 14.78% of the total contract value;

Women-Owned Small Business (WOSB): 5% of the total contract value;

Historically Underutilized Business Zone (HUBZone) SB: 3% of the total contract value;

Service-Disabled Veteran-Owned Small Business (SDVOSB): 5% of the total contract value.

A subcontracting plan is required (FAR 52.219-9) for Other than U.S. Small Businesses only (i.e. Large Businesses). ONLY OTHER THAN U.S. SMALL

BUSINESS OFFERORS ARE REQUIRED TO SUBMIT A SUBCONTRACTING

PLAN. Offerors are required to submit either an individual subcontracting plan, an approved commercial plan, or a negotiated DoD Comprehensive Test Program subcontracting plan. In addition, offerors are required to complete the DISA Subcontracting Review Checklist (Exhibit 4) by inserting dollar values and percentages from your subcontracting plan as applicable for items 1 and 2, and also items 3 through 19 by completing the paragraph and page number columns.

The subcontracting plan is the organization’s business plan for the inclusion of small businesses within their capture/contracting processes. An individual subcontracting plan highlights the general potential for subcontracting opportunities within a specific procurement. The contract awardee has the life of the contract to make a good faith effort to ensure that subcontracted dollars will go to small businesses.

Other than U.S. Small Business Offerors (i.e., Large Businesses) must submit a subcontracting plan that meets the requirements of FAR 19.704, FAR Clause 52.219- 9 (Alternates and Deviations) and DFARS 252.219-7003 (or DFARS 252.219- 7004 if the Offeror has a DoD Comprehensive Test Program subcontracting plan).

The contracting officer will review subcontracting plans on an acceptable or unacceptable basis for compliance with FAR 19.704, FAR Clause 52.219-9 (Alternates and Deviations), and the applicable DFARS clause. A subcontracting plan is unacceptable if it does not clearly meet the requirements of FAR 19.704, FAR Clause 52.219- 9 (Alternates and Deviations) and DFARS 252.219-7003 (or DFARS 252.219- 7004 if the Offeror has a DoD Comprehensive Test Program subcontracting plan). Subcontracting plans will only be reviewed for acceptability for those Offeror(s) deemed to be an apparent awardee(s).

The subcontracting plan shall be included in the offer, and the approved subcontracting plan shall be incorporated into the contract.

10) DD254. Complete Block 6, and 7 of the DD Form 254 and return with your proposal.

11) Continuation of Essential Contractor Services. Offerors must submit a written plan in accordance with DFARS 252.237-7023 and DFARS 252.237-7024.

The Continuation of Essential Contractor Services Plan required by DFARS 252.237-7024 will be evaluated for acceptability based on the requirements of DFARS 252.237-7024(2)(i-v).

52.212-1(c), Period for Acceptance of Offers is tailored as follows:

(c) Period for acceptance of proposals. The offeror agrees to hold the prices in its offer firm for 150 calendar days from the date specified for receipt of proposal, unless otherwise withdrawn. The offeror shall make a clear statement in the proposal documentation volume that the proposal is valid through this date. There is no obligation on the part of the Government to make an award to any contractor in response to this request.

(End of provision revisions)

ADDENDUM TO 52.212-2(a)

Addendum to 52.212-2(a), Evaluation-Commercial Items is tailored as follows:

A. Basis for Contract Award

Award will be made to the responsible offeror whose proposal conforming to the solicitation will be most advantageous to the Government, using a lowest price technically acceptable (LPTA) evaluation process.

The below evaluation factors and subfactors will be used in the LPTA analysis. Section 508 Accessibility Standards do apply to this requirement. Section 508 requirements are listed in the PWS. Compliance with Section 508 standards will be considered prior to evaluating any of the selected criteria listed below. Any proposal failing to meet the Section 508 Accessibility Standards, as listed in the PWS, shall be eliminated from consideration of award.

B. Evaluation Factors and Subfactors

(1) The following evaluation factors and subfactors will be used to evaluate each proposal.

Factor 1: Technical/Management Approach. Offeror shall explain how the selected elements of each subfactor below will be accomplished. The technical subfactors will be evaluated based on an acceptable or unacceptable basis, assigning one of the ratings described below in Table 1. Proposals, including any addendums, must address all the criteria in Factor 1 to be rated “Acceptable.” Additional consideration will not be given for Technical/Management proposals that exceed the stated standard. Any subfactor under Factor 1 evaluated as “Unacceptable” will render the entire proposal unacceptable. Only those proposals determined to be technically acceptable will be considered for award. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions.

Table 1. Technical/Management Ratings Rating Description Acceptable Proposal/quotation clearly meets the minimum requirements of the solicitation.

Unacceptable Proposal/quotation does not clearly meet the minimum requirements of the solicitation.

Acceptable/Unacceptable ratings for all subfactors will be provided at the subfactor level.

Factor 1: Technical/Management

a. Subfactor 1: Comprehensive Implementation Plan, PWS Section 6.1.1. For this subfactor to be rated Acceptable, the Offeror’s proposal must present a program management approach to include an Initial Comprehensive Implementation Plan (CIP) that provides:

1) The offeror’s proposed design that meets the requirements of the PWS Section 6.1.1.

This shall include diagrams showing the technical architecture proposed at both the CEGs (PWS Section 6.1.1.1) and Access Sites (PWS Section 6.1.1.2) and provide in detail the technical solution for providing Ethernet Gateways from the Commercial Service Provider (CSP).

2) A description of the offeror’s proposed Implementation (PWS Section 6.1.1.3), Data Delivery (PWS Section 6.1.1.4) and Operations and Maintenance (PWS Section 6.1.1.5) processes that address all of the requirements described in the referenced sections of the PWS.

b. Subfactor 2: Network Service Capabilities, PWS Section 6.2. For this subfactor to be rated

Acceptable, the proposal must demonstrate an approach that provides network services meeting the required service performance specifications of the Commercial Ethernet Gateway (PWS Sections 6.2.1) and DODIN Customer Access Sites (PWS Section 6.2.2) as defined in the referenced sections of the PWS.

c. Subfactor 3: Network Service Management, PWS Section 6.3. For this subfactor to be rated

Acceptable, the proposal must demonstrate an approach that provides the ability to interface with the DISA-Enterprise Operations Center (EOC) network monitoring tools and provide near real time network situational awareness as described in PWS Section 6.3 paragraphs 1 through 4.

Factor 2: Price

(a) The Offeror’s firm-fixed price proposal will be evaluated for award purposes based upon the total evaluated price which consists of the offeror’s proposed prices for the base period, all option periods, option pricing for an additional 6-month extension period that may be authorized IAW FAR 52.217-8.

Evaluation of the options shall not obligate the Government to exercise such options. The offeror’s price proposal will be evaluated, using one or more of the techniques defined in FAR 15.404, in order to determine if it is reasonable and complete. Normally, price reasonableness is established through cost and price analysis techniques as described in FAR 15.404. For a price to be complete, all solicitation requirements must be priced, figures correctly calculated and prices presented in in a clear and useful format.

C. Evaluation of Options

The offeror shall submit pricing for the base period, all option periods, and pricing for an additional 6-month period that may be authorized IAW FAR 52.217-8. See FAR 52.217-8 which authorizes the Government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal should include a separate line item for the additional 6-month period IAW FAR 52.217-8. These prices shall be identical to the proposed pricing in the 6 months prior to expiration of the base period, or the final option period, if option periods are present. Evaluation of options shall not obligate the Government to exercise the option(s).

D. Discussions

The Government intends to evaluate proposals and award a contract without exchanges. However, the Government reserves the right to conduct exchanges or seek clarifications if the KO determines they are necessary. If the KO determines that discussions are necessary, a competitive range will be established.

E. Questions

Questions should be address to ryan.g.lee.civ@mail.mil and jodie.s.onaga-nuttall.civ@mail.mil. Please provide any questions, in writing, using the provided template (See Exhibit 6), no later than 09 September 2024 at 8:00 AM

Hawaii Standard Time. The Government reserves the right to not answer any further questions submitted after this time.

No information concerning this solicitation or requests for clarification will be provided in response to offeror initiated telephone calls. All such requests must be made in writing and submitted as directed above. All questions provided in a timely manner will be answered in writing and provided to all offerors. The timeframe for submitting inquiries will not be extended as a result of an extension to the due date for the receipt of proposals, unless authorized by the KO.

(End of provision revisions)

LIST OF ATTACHMENTS & EXHIBITS

PERFORMANCE WORK STATEMENT

Commercial Ethernet Gateway – Hawaii (CEG-HI) Performance Work Statement (PWS)

10 Sep 2024

Defense Information Systems Agency

Enterprise Operations and Infrastructure Center (IE) 6910 Cooper Ave

Ft Meade, MD

Controlled by: DCSC-IE Controlled by: DISA CEG PMO

PWS ATTACHMENTS (ATCH)

SOLICITATION EXHIBITS (EX)

A CEG-DISN Node and Customer Access Site List 1 Price Schedule B CEG Design Document 2 Quality Assurance Surveillance Plan (QASP) C CEG Technical Implementation Standards 3 DD Form 254 D CEG Notice of Completion Template 4 DISA Subcontracting Plan Review Checklist E CEG GFI and Contract Deliverable Timeline 5 Mission-Essential Contractor Services F CEG Demarcation Definitions 6 Solicitation Questions and Answers

CUI Category: CTI, OPSEC, PROCURE Distribution/Dissemination Control: FEDCON POC: Juan Rivas, MAJ, SC (301) 225- 2407 juan.r.rivas6.mil@mail.mil

PERFORMANCE WORK STATEMENT

Commercial Ethernet Gateway – Hawaii (CEG-HI)

10 Sep 2024

Table of Contents

1. (U) Contracting Officer Representative (COR)

2. (U) Contract or Task Order Title

3. (U) Background

4. (U) Objectives

5. (U) Scope

6. (U) Performance Requirements

6.1 (U) Task 1 - Program Management:

6.1.1 (U) Subtask 1 - Comprehensive Implementation Plan

6.1.2 (U) Subtask 2 - Project Status and Reporting

6.2 (U) Task 2 - Network Service Capabilities

6.2.1 (U) Subtask 1 - Commercial Enterprise Ethernet Gateways (CEG)

6.2.2 (U) Subtask 2 - DODIN Customer Access Site Services

6.3 (U) Task 3 - Network Service Management

6.4 (U) Task 4 - Security - Reserved

6.5 (U) Task 5 - Site Implementation Services (Optional)

6.5.1 (U) Subtask 1 - Service Delivery Point (SDP) Extension Provisioning

6.5.2 (U) Subtask 2 - Demarc Infrastructure Modifications

6.5.3 (U) Subtask 3 - VLAN Modifications

6.5.4 (U) Subtask 4 - Customer Access Service (EVC) Upgrade Modifications

6.5.5 (U) Subtask 5 – Onsite Site Surveys

6.6 (U) Additional Services and Requirements

6.6.1 - (U) Temporary Service

6.6.2 - (U) Expedited Service

6.6.3 - (U) Telecommunications Service Priority (TSP)

6.6.4 - (U) National Security and Emergency Preparedness (NS/EP)

6.6.5 - (U) Circuit Cessation and Disconnection

6.6.6 – (U) Task Order Cancellation

7. (U) Performance Standards. (Unless otherwise stated, all time is in Calendar Days)

8. (U) Incentives

9. (U) Place of Performance

9.1 (U) Alternate Place of Performance - Contingency Only

10. (U) Period of Performance

11. (U) Delivery Schedule

12. (U) Security Requirements

12.1 (U) Facility Security Clearance

12.2 (U) Security Clearance and Information Technology (IT) Level

12.3 (U) Investigations Requirements

12.4 (U) Visit Authorization Letters (VAL)

12.5 (U) Security Contacts

12.6 (U) Information Security and other miscellaneous requirements

13. (U) Government Furnished Property (GFP)/Government-Furnished Equipment (GFE)/ Government-Furnished Information (GFI)

14. (U) Other Pertinent Information or Special Consideration

15. (U) Section 508 Accessibility Standards

16. (U) Attachments

(U) Attachment A - CEG -DISN Node and Customer Access Site List

(U) Attachment B - CEG Design Document

(U) Attachment C - CEG Technical Implementation Standards

(U) Attachment D - CEG Notice of Completion Template

(U) Attachment E - CEG GFI and Contract Deliverable Timeline

(U) Attachment F - CEG Demarcation Definitions

PERFORMANCE WORK STATEMENT (PWS)

As of 10 Sep 2024

Award/Mod Effective Version Date

Contract Number: TBD Contractor Name: TBD Tracking Number: HC101924R0004 Follow-on to Previous Contract and Task Order Number:

N/A

1. (U) Contracting Officer Representative (COR).

a. (U) Primary COR. See DITCO Additional Text G1 - Points of Contact

b. (U) Alternate COR. See DITCO Additional Text G1 - Points of Contact

2. (U) Contract or Task Order Title.

(U) Commercial Ethernet Gateway – Hawaii (CEG-HI)

3. (U) Background.

(U) In May 2016 the Department of Defense (DOD) Chief Information Officer directed the DOD to migrate to Ethernet-based services to reduce telecommunications costs. Since that time the Defense Information Systems Agency (DISA) has been modernizing the DOD Information Network (DODIN) to facilitate Ethernet connections to that network and enable the replacement of legacy point-to-point Public Switched Telephone Network, time division multiplexing-based circuits. In 2020 the first Commercial Ethernet Gateway (CEG) contract was awarded for Regions 1 and 2 and subsequently 5 more contracts have been awarded. These contracts have resulted in significantly lower circuit costs and massive increases in bandwidth.

4. (U) Objectives.

(U) The objectives of this contract are to:

1. (CUI) Establish CEGs from the Commercial Service Provider’s (CSP) owned, leased, and operated network(s) to the DODIN in accordance with the instructions shown in Attachments A and B for the CEG DISN Core Sites. CEGs shall employ virtualization using virtual local area network (VLAN) (802.1Q) between the DISN Joint Provider Edge Router (J-PE) and the CSP’s Provider Edge (PE) routers using diverse, high bandwidth links. The CSP’s CEG design must meet the performance and availability requirements of this PWS.

2. (CUI) For the Customer Access Sites, provision > 1 GB connections to the CSP’s Ethernet Network.

Perform functional and performance testing to demonstrate compliance with PWS requirements.

Attachment A – CEG-DISN Node and Customer Access Site List provides a list of potential Access Site locations.

3. (U) Provide additional Customer Access Sites and/or move or upgrade service for Customer Access Sites within Hawaii.

(U) Figure 4-1 CEG Hawaii Map

5. (U) Scope.

U) The Government intends to award Indefinite Delivery Indefinite Quantity (IDIQ) contracts for Hawaii shown in Table 4-1. The Government requires commercially provided network solutions and services where the Contractor designs, furnishes, installs, tests, maintains, and sustains the CEG and Customer Access Site capabilities described in Attachment B – CEG Design Document for both DOD and authorized non-DOD operations at various locations representatively shown in Attachment A – CEG-DISN Node and Customer Access Site List. Figure 5-1 provides an overview of a notional CEG Regional architecture.

(CUI) Figure – 5-1 Notional CEG Hawaii Architecture

(CUI) Scope.

Customer Access Sites not listed in Attachment A – CEG-DISN Node and Customer Access Site List may be added during the life of the contract and sites listed on Attachment A – CEG-DISN Node and Customer Access Site List may or may not be ordered. All CEGs and Customer Access Sites will be awarded by individual task orders (TOs) and assigned a command communications service designator (CCSD) and a communications service authorization (CSA). The Contractor will deliver services per the prices defined in Exhibit 1 – Price Schedule of the contract for all TOs awarded. TOs will be awarded utilizing Integrated Defense Enterprise Acquisition System (IDEAS).

Contractor shall register with the DISA Global Service Desk for access to IDEAS. The Contracting Officer (CO) will assist with coordination for access. Once registered, Contractor can access IDEAS to download orders and modifications sent directly to the Contractor, and to upload jeopardy notices and completion notices. An order or modification sent to the Contractor in IDEAS is considered the official issuance of the order or modification by the Government.

(CUI) Payment for service provided under this contract shall be made using the Delivery Ticket Invoice (DTI) payment method. Payments will be provided automatically by the Government. Outage credits will be collected using the DTI method. The Contractor shall not submit separate invoices for services provided under this contract to Defense Information Technology Contracting Organization (DITCO).

6. (U) Performance Requirements.

6.1 (U) Task 1 - Program Management:

(U) Task 1 provides the Program Management requirements for the delivery of the services described in Tasks 2-5.

Contractors are encouraged to use existing designs, systems, and processes if they meet the requirements described in this Task. Contractor may require access to classified information, to review classified design information and to communicate with classified IT systems (SIPRNET and WWOLS) as well as access to buildings and rooms where open storage up to the SECRET level is approved.

6.1.1 (U) Subtask 1 - Comprehensive Implementation Plan

(U) The Contractor shall provide a Comprehensive Implementation Plan (CIP), a living document that shall be maintained by the Contractor throughout the Period of Performance (PoP) of the contract. An Initial CIP shall be provided as part of the Contractor’s proposal and will be evaluated to determine the technical acceptability of the Contractor’s design, as well as their implementation and support (also called Operations and Maintenance (O&M)) approaches. The CIP format is Contractor determined but the proposed CIP approach must demonstrate the Contractor’s capability to plan and manage the contract requirements throughout the PoP. The Contractor’s ability to manage life-cycle CIP revisions and provide design data, implementation status, and operational performance data to the Government will also be evaluated. The Government understands that certain types of data (e.g., actual schedule dates, actual access site names/locations) cannot be provided in the initial CIP. In those instances, sufficient notional data shall be used to describe the offeror’s proposed approach. For those parts of the CIP where the data is under the offeror’s control (e.g., proposed CEG and Access Site Design, Test Plans/Procedures, O&M Processes, etc.), the Government requires that the offeror include data that shows the approach and methods that will be used in the performance of the work.

(U) Upon award, the Government will provide feedback to the Contractor during the initial In-Process Review (IPR) and the Contractor shall deliver a Final CIP not later than 30 days after contract award. CIP updates shall be provided to the Government not less than monthly and whenever changes are made to the Gateway or Access Site design, when new sites are added, or when sites are disconnected. The Contractor’s CIP change process should be described in their proposal and should specifically address how updates will be provided. The following paragraphs provide additional information about the CEG requirements, and the data required in the CIP.

6.1.1.1 (U) Gateway Design There shall be a minimum of two (2) gateways installed in Hawaii. Gateways can be installed at the Government Gateway locations listed in Attachment A – CEG-DISN Node and Customer Access Site List or on the Contractor’s site if the Network-to-Network Interface (NNI) meets the requirements of Attachment B – CEG Design Document.

If an onsite survey is required of the Government location prior to the installation of the Gateway, the Contractor shall state this in their proposal and include pricing if applicable for this survey(s) in their cost proposal as a non-recurring cost (NRC). Note that if the Government facility does not have infrastructure needed to support the CEG installation, the Contractor shall be required to provide the infrastructure and may include this cost in their cost proposal as an NRC. Infrastructure is defined as any material that is not part of the proposed gateway design but that is required for the proposed gateway to meet the operational and performance requirements of the PWS. Examples include, inside and outside plant cabling required to connect the Contractor's installed gateway equipment to the Contractor's commercial network, inside plant cabling and jumpers, media converters, etc. required to connect the Contractor's installed gateway equipment to the Government's J-PE router (i.e. the NNI connection), any racks/cabinets to hold the Contractor's gateway equipment, any power conditioning or backup power supplies required to support the Contractor's installed gateway equipment. The following data shall be provided in the Initial CIP showing the logical and physical architecture proposed at the gateway sites:

a. (U) Diagrams showing where the equipment will be installed, what demarcation point (demarc) infrastructure will be needed (e.g., electrical power connections, rack space, HVAC load, etc.) and how the equipment will be connected to the DOD equipment in accordance with Attachment B – CEG Design Document. If the Contractor proposes to install CEG equipment in their owned or leased facility, so state and provide the address and a description of the facility including physical security information.

b. (U) Tables showing the make and model number of all equipment that will be installed as well as operating system versions and its configuration for each device. If the Contractor intends to use more than one configuration at a Gateway, they shall provide drawings and data for each configuration to be used that can be correlated back to each as-built data provided per subparagraph a. above.

c. (U) Contractor shall show how the equipment used on this contract meets the requirements outlined in the Contractor’s Supply Chain Risk Management (SCRM) Plan outlined in paragraph 14.g.

6.1.1.2 (U) Access Site Design and Ordering Access Sites are connected to Gateways via the Contractor’s proposed e-line service (also referred to herein as an Ethernet Virtual Circuit (EVC)). The following data shall be provided in the Initial CIP and all subsequent updates showing the logical and physical architecture proposed at the Access Sites:

a. (U) Diagrams showing how the equipment will be installed (e.g., Rack Elevation and Cabling), what demarc infrastructure will be needed (e.g., electrical power connections, rack space, etc.) and how the equipment will be connected to the DOD customer site equipment in accordance with Attachment B – CEG Design Document to the Initial CIP. The diagrams should clearly show this connection. These diagrams shall represent the proposed Access Site design in the Initial CIP, but the Contractor shall be responsible for providing as-built data for every Access Site in the monthly CIP updates that indicate the rack locations and connection details for every installed device.

b. (U) Contractor will terminate each Access Site EVC and Gateway E-NNI to the site-specific fiber demarcation point identified in the TO. Fiber extension beyond the fiber demarcation point will be supported in accordance with the Section 5.1 (Subtask 1 - Service Delivery Point (SDP) Extension Provisioning). Contractor will provide infrastructure modifications using the Demarc Infrastructure Modification CLIN.

c. (U) The Gateway location to which the Contractor is proposing to home the Access Site. The Government requires this information as a prerequisite to issuing the TO for any/all Access Sites to make the VLAN assignments described in paragraph 6.2.1.4. If the Contractor can make this assignment as part of the initial/final CIP, they are encouraged to do so. If the Gateway homing assignment cannot be made at that time it should be made as early as possible in the design process but in every instance the homing assignment is required prior to the issuance of the TO.

d. (U) Tables showing the make and model number of all equipment that will be installed as well as operating system versions and its configuration for each device. If the Contractor intends to use more than one configuration at Access Sites, they shall provide drawings and data for each configuration to be used that can be correlated back to each as-built data provided per subparagraph a. above.

e. (U) Contractor shall show how the equipment used on this contract meets the requirements outlined in the Contractor’s Supply Chain Risk Management (SCRM) Plan outlined in paragraph 14.g.

(U) After contract award, the Government may order, and the Contractor shall provide Access Services for locations included in Attachment A – CEG-DISN Node and Customer Access Site List. All orders will be issued via a TO at the firm fixed price defined in Exhibit 1 – Price Schedule of the contract. When requested by the COR, the Contractor shall provide, at no additional cost, the CIP information described in paragraph 6.1.1.5 that is required by the Government to develop the TO for the new service. This information shall be provided within 5 business days of the request, but Contractors are encouraged to provide the Access Site homing information per paragraph 6.1.1.3b as soon as possible. Contractor shall communicate and manage existing and new circuit orders to the Government via a Government assigned platform (I.E. Smartsheet). Requests for this information does not obligate the Government to order the service.

(U) Additionally, the Government may order additional…