Final RFQ 090825.pdf

STATEMENT OF WORK

This project consists of two parts, the first of which is the statement of work and hardware list for network switch installation, cable management, and switch configuration. The items on the hardware list on page 15 is to be provided by the vendor. The second part of the project is a statement of work for the Cisco ISE portion of the installation. The work is to be performed at the U.S. Court of International Trade, located at 1 Federal Plaza, New York, N.Y., 10278.

PROJECT DESCRIPTION

PROJECT SCOPE

This statement of work outlines the scope of services to support the Customer switch and wiring closet cable management project. Subject to the other provisions of this Statement of Work, the Vendor will perform the following services. The Vendor will replace the Customer’s existing aging Cisco 3850 access switches with a mix of new Cisco 9300s in both forty-eight (48) and twenty-four (24) port models. This work will include stacking the switches in the courts ten (10) IDF closets, labeling the ethernet cables and creating a port diagram for each closet. Once the switches have been installed the vendor will import the new switches into the customer’s existing DNA Center. The vendor will also replace the existing jumble of pre-terminate ethernet cables to clean up the connections from the patch panel to the new switches using the cable management and the correct cable lengths. The vendor will label the new cables and create a cable diagram to show the patch panel port to switch port connections. The new switches will also be added to the courts’ existing Cisco Catalyst center. The cutover to implement the new switches will be broken into two (2) phases to accommodate the court’s schedule to reduce consecutive hours of extended network downtime. After each cutover the vendor will provide an engineer for the first day’s support, eight

(8) hours per post cutover, for a total of sixteen (16) hours. This work will include up to eight (8) hours of knowledge transfer from the vendors engineer to the customer’s engineer when configuring and installing the new equipment.

TECHNICAL OVERVIEW

As part of the core switch refresh, Vendor will configure, stage, place, and test the hardware listed above based on the following parameters as agreed upon by the design phase of the project:

• Configure Unicast Routing Interior Gateway Protocol (IGP)

• Configure Protocol Independent Multicast (PIM)

• Configure Spanning Tree Protocol (STP)

• Configure VLANs

• Configure Switched Virtual Interfaces (SVI)

• Configure Quality of Service (QoS)

• Configure First Hop Redundancy (FHR)

• Configure Physical or Virtual Switch Stacking

• Configure Link Aggregation Group (LAG)

• Configure Virtual Route Forwarding (VRF)

• Configure Flow Export (Netflow/IPFIX)

• Configure Simple Network Management Protocol (SNMP)

• Configure IP Service Level Agreements (IPSLA)

• Configure applicable physical network interfaces

• Configure applicable network addressing

• Configure secure access to devices

• Configure network management parameters

• Other configuration parameters as necessitated by the environment

Replacing the existing pre-terminated ethernet cables with the correct length pre terminated ethernet cables to clean up the wiring closets. Tasks will include:

• The Vendor will NOT run any new ethernet cables in walls, ceilings, in in anyway other than listed below or terminating any cables or patch panels. The cable replacement is only scoped to replace existing pre-terminated ethernet cables with new pre-terminated cables from the patch panel in the ten (10) customers closets to the new switches being replaced in this statement of work.

• Prior to the services the Vendor will identify the correct pre-terminated ethernet cable length and sell the client the length and quantity to replace existing cables with new cables for the switches listed in this statement or work.

• Prior to the services the Vendor will identify any existing cable management or identify new cable management and sell it to the client to be used during the services for the switches the vendor is replacing in the ten (10) customers closets.

• The Vendor will identify the pre-terminated ethernet cables port on the patch panel and on the existing switch in each of the customers closets.

• The vendor will label the new pre-terminated ethernet cables with the patch panel port and switch port of the new switches being installed.

• The vendor will identify which customer closets will be upgraded and the pre-terminated ethernet cables will be replaced during phase one (1) and phase (2) of the project.

• The vendor will create a port diagram containing each of the customers ten (10) closets with the patch panel and switch port on the new switch it is connected to.

The project team will execute a defined test plan to verify implementation and configuration of the hardware and software, to test specific functionality, and to document the system configuration before turning the system over to the Customer. The testing phase will consist of the following items:

• Test Plan Creation - The project team will develop a mutually agreed upon test plan for the new hardware configurations to create baseline testing information.

o Test Plan will include items such as IP reachability tests, configuration verification, and hardware failure scenarios directly related to equipment implemented in this project.

• Baseline Testing – Customer will create a baseline test, using created test plan, to ensure proper operation prior to integration and cutover.

• Test Plan Execution – After integration and cutover, the project team will execute the test for the new hardware configurations and review the Test Plan results with the Customer technical staff.

Once the system implementation activities are complete, production cut-over to the new system will take place and Vendor will provide First Day Support for the production system, track, and resolve incidents for 1 days ( 8 hours) at the Customer location.

TECHNICAL COMPONENTS

The proposed solution is comprised of the following hardware/software components:

Item / Part Description Quantity

C9300-48P-E Catalyst 9300 48-port POE+ Network Essentials 17

C9300-24P-E Catalyst 9300 24-port POE+ Network Essentials 3

TECHNICAL DESIGN

The following diagram is not included for security reasons.

PROJECT SERVICES

Vendor is to conduct the following services ("Services") under the terms and conditions of this SOW: Phase

1: Project Kickoff

• Conduct Project Kickoff meeting and activities.

Phase 2: Requirements Gathering

• Conduct Requirements Gathering Workshops – (2) workshops, up to (16) hours total

• Inventory equipment

• Determine the location of the new switches in the customers closet

• Determine clients schedule for phase one (1) and (2) cutovers for the project

Phase 3: Design Planning

• Collect and review clients’ existing switch configuration files for the following:

• VLANs

• Switch virtual interfaces

• Quality of Service

• First Hop Redundancy

• Switch stacking

• Link Aggregation Group

• VRFS

• Flow Exports

• SNMP

• IPSLAs

• Network interfaces and addressing o Management parameters

Phase 4: Implementation & Validation

• Configure Unicast Routing Interior Gateway Protocol (IGP)

• Configure Protocol Independent Multicast (PIM)

• Configure Spanning Tree Protocol (STP)

• Configure VLANs

• Configure Switched Virtual Interfaces (SVI)

• Configure Quality of Service (QoS)

• Configure First Hop Redundancy (FHR)

• Configure Physical or Virtual Switch Stacking

• Configure Link Aggregation Group (LAG)

• Configure Virtual Route Forwarding (VRF)

• Configure Flow Export (Netflow/IPFIX)

• Configure Simple Network Management Protocol (SNMP)

• Configure IP Service Level Agreements (IPSLA)

• Configure applicable physical network interfaces

• Configure applicable network addressing

• Configure secure access to devices

• Configure network management parameters

• Other configuration parameters as necessitated by the environment.

• Replace existing pre-terminated ethernet cables with new pre-terminated cables

• Create port document with patch port to switch port information

• Provide knowledge transfer – Knowledge transfer includes both "over the shoulder" and time-based training sessions. The overall time for this training will not exceed eight (8) hours.

• Provide post-go-live support – This support will not exceed sixteen(16) hours (eight (8) hours per cutover).

Phase 5: Project Close Out

• Conduct Project Closeout meeting and activities.

PROJECT ASSUMPTIONS & CONDITIONS

1. All WAN and PSTN circuits will be terminated, provisioned, and functioning properly.

2. Cabling will be functioning and terminated.

3. The installation location has the required power circuits for the new switches.

4. The current network must be functioning properly (no adverse conditions) prior to the implementation of the new equipment.

5. DNAC is installed and working correctly without any adverse conditions

a. DNAC has the credential of the devices if they are using passwords for SNMP

ITEMS PROVIDED TO CUSTOMER

ITEMS PROVIDED TO CUSTOMER FORMAT

The Vendor will submit Items Provided to Customer in electronic form and will produce reports using Microsoft Office Professional Suite (Word, Excel, Access, and PowerPoint), Microsoft Project, and/or Visio. All Items Provided to Customer and their acceptance criteria for this SOW includes:

Phase Items Provided to Customer Acceptance

1. Project Kickoff Project Schedule Final after five (5) day review period

2. Requirements Gathering

Requirements Gathering Document Final after five (5) day review period

Pre-Implementation Checklist Signature required two (2) weeks prior to implementation

3. Design Planning

Design Document Signature required

Implementation Plan Submittal

Test Plan Submittal

4. Implementation Executed Test Plan Acceptance Signature required

5. Project Closeout

As-Built Document & Port Document

Final after five (5) day review period

Project Closeout Document Final after five (5) day review period

ITEMS PROVIDED TO CUSTOMER REVIEW AND ACCEPTANCE CRITERIA

For any document identified above as Final after five (5) Day Review Period, stakeholders will have five (5) business days from submission of these Items Provided to Customer to review and provide comments and/or feedback. If the Customer does not provide any feedback after the five (5) day review timeframe, Vendor will consider the Items Provided to Customer final and will be used to progress to the next phase of the project.

The Vendor will consider incorporating comments and/or feedback provided by the Customer within the five (5) day review timeframe. Any resulting revision to the Items Provided to Customer will be considered final. Any further comments and/or revisions to the Items Provided to Customer will be subject to the Change Management Procedures included in this SOW.

ITEMS PROVIDED TO CUSTOMER SIGNATURES

Phase gate reviews will be held for the Design Planning and Staging and Implementation Phases. The Design Document, Pre- Implementation Checklist, and Executed Test Plan will require a Customer signature in order to pass the phase gate and progress into the next phase of the project. If signature of the Design Document is delayed for longer than fifteen (15) business days, Vendor reserves the right submit a Change Order to rework the previously completed Items Provided to Customer. If signature of the executed Test Plan is delayed for longer than five (5) business days, Vendor will assume the Customer accepts the system as operationally ready and will invoice for implementation and proceed to project closeout.

Figure:

Phased Project Methodology

Phase 1: Project Kick Off

Following contract execution, the Vendor will conduct a Project Kick Off meeting with the Customer. The agenda for this meeting includes:

• Team Introductions

• Project Objectives and Success Criteria

• Project Scope, Items Provided to Customer, and Assumptions Review

• Project Timeline and Cadence Discussion

• Project Administration Overview o Escalation o Roles and Responsibilities Overview o Risk and Change Management o Security Requirements (Physical, Network, and Certification)

Phase 1.1 – Project Schedule

A Project Schedule is critical for completing a project on time and clearly identifies milestones and associated due dates and task holders. The Vendor will work with Customer personnel to develop and approve a Project Schedule. During the Project Kick Off Phase, a schedule that includes proposed dates for both the Requirements Gathering and Design phases, as well as estimated timelines for the Implementation and Closeout phases will be presented to the Customer Project Team.

As the project team looks to wrap up the planning phases with the distribution and approval of the design, the project schedule will be updated and baselined for Implementation. This baseline will be used to track the project to completion.

Throughout the project, the Vendor Project Manager (PM) will be responsible for updating the project schedule with actual progress and/or changes, measuring progress, and managing variances to the schedule.

Phase 1.2 – Risk Register

A project risk register is pertinent to identifying, planning for, and tracking risks that could affect the project. The Vendor will work with the entire project team to identify any risks or issues throughout the life of the project, develop and execute plans to address risk, and keep the team informed by sending out an updated risk register as needed.

Phase 2: Requirements Gathering

During Phase 2, the Vendor will perform a detailed requirements analysis that will be used to develop the Pre-Implementation Checklist, Requirements Gathering Document, and the Design Document.

Phase 2.1 – Workshops

The Vendor will conduct workshops to compile the Requirements Gathering Document based on the topics and sessions specified in the Scope of Work.

Phase 2.2 – Requirements Gathering Document

The Requirements Gathering Document provides a detailed overview of the Vendors understanding of the expected features and functionality for the proposed solution, as well as system and infrastructure requirements for successful implementation.

The Requirements Gathering Document serves as the foundation for the design and to assist in identifying gaps that may require remediation prior to the Staging and Implementation Phase. While we do our best to gather all relevant technical information prior to the start of the SOW, post-award validation and further discovery are essential to a successful project.

Phase 2.3 – Pre-Implementation Checklist

The Pre-Implementation Checklist details the tasks that must be completed by the Customer to prepare their environment to receive the solution, including:

• Site readiness tasks (construction or access constraints, etc.)

• Network readiness tasks (interconnections and configurations, proper version check, etc.)

• Staging readiness tasks (adequate power/cooling, completed cabling, location prepped for equipment, etc.)

rack/stack area cleared, and proper cooling)

• Service Assurance (scheduling of required downtimes/maintenance windows)

The Vendor will review the required tasks with the responsible Customer stakeholder by conducting remote sessions to validate completeness and address questions. The checklist must be signed by the Customer two (2) weeks prior to the start of implementation. The signed checklist signifies that all tasks are complete. Any scheduled deployments will be delayed if all essential tasks on the checklist are not completed.

Phase 3: Design Planning

The Vendor will send the Design Document, or sections of the Design Document to the Customer and a team review meeting will be held following the submission. If the document is completed in its entirety the document will be reviewed, in full, during (1) review session. If working iteratively, several sessions will be held to review each release, with a final review of the entire document for signoff. This meeting will have three (3) possible outcomes:

1. Approval of the document

2. Approval of the document following the update of the identified minor changes

3. No approval of the document until all recommended major changes are implemented

NOTE: Minor changes will be defined as changes that are editorial in nature which do not alter the timeline, scope, or cost of the project. Major changes will be defined as design updates deviating from the solution defined in the SOW. Major changes that substantially affect the project timeline will require a Change Order. Additionally, any deviations from the previously gathered requirements necessitating changes to the Bill of Materials (BOM) or the Level of Effort (LOE) will constitute a major change and a Change Order will be required. Upon approval of the Change Order (and funding if applicable), Vendor will proceed to the next phase after the project is re-baselined according to the approved Change Orders.

The Vendor will evaluate the requested changes and may incorporate those changes into the Design Document. Once the Design Document is deemed complete and satisfactory by all project stakeholders, it must be signed and returned to the Vendor PM before the project can move into the Staging and Implementation Phase.

At this point, the Design Document becomes the authoritative document in regard to scope of work and will be what the Vendor team uses to complete the project.

Phase 3.1 – Implementation Plan

The Vendor engineers will develop an Implementation Plan outlining the activities that will be completed during implementation to help the customer understand the timeline. The Implementation Plan will include estimated outage windows and rollback plans to verify all pieces are in place as we execute the plan.

Phase 3.2 – Test Plan

The Vendor will create the Test Plan based on the finalized Design Document. The Test Plan is developed to verify that the solution satisfies stated requirements, and that needed functionality works as designed. The Test Plan is executed in Phase 4b of deployment. The Test Plan may include validation for the items jointly agreed upon between Vendor and the customer.

Phase 4: Staging & Implementation

The objective of the Staging and Implementation Phase is to successfully introduce and deploy the solution with the least amount of disruption and the highest level of interoperability with the existing network.

Phase 4.1 – Staging

If applicable, the Vendor performs the tasks referenced in the Scope of Work during the staging process in the staging lab facility.

Phase 4.2 – Implementation

Once the equipment has been received and inventoried by the Customer, the Vendor works with Customer to integrate the new system within Customer’s production environment.

The Vendor’s Implementation Team will be on-site at Customer's location. All work will be completed between 8:30 am - 5:30 pm local time, Monday through Friday, unless agreed upon by both parties during Phase 1: Project Kickoff.

The Vendor will perform the tasks referenced in the Scope of Work and complete the Items Provided to Customer as outlined in the Project Schedule and Implementation Plan.

Phase 4.3 – Knowledge Transfer

The knowledge transfer will take place onsite or remotely at a mutually agreed upon scheduled time. Knowledge transfer includes "over the shoulder" demonstration and sessions specified in the Scope of Work that covers the following topics:

• Review the architecture or deployed solution and the functional capabilities.

• Discuss resources for further information such as administration guides, community, and support.

• Support/troubleshooting

• Conduct Q&A

Knowledge transfer sessions can vary based on the length and complexity of projects. Further details are referenced in the Scope of Work.

Phase 4.4 – Acceptance Testing

The Vendor will execute the Test Plan immediately following Implementation. The function of the Test Plan is to validate all features and functionality that were agreed upon during the previous phases of the project and establish a system baseline following implementation. All results and deficiencies will be documented, and the Test Plan must be signed prior to the Vendor engineer leaving the site or troubleshooting any tested deficiencies. Once the system baseline is established, implementation can be closed if no major deficiencies are reported. If service-impacting deficiencies exist as a result of work performed by the Vendor, the engineer will continue iterations of troubleshooting and baselining the system until stakeholders agree on a satisfactory baseline to transition into an operational state. The final Test Plan must be signed and returned to the Vendors PM before implementation can be closed and As-Built, training, or other documentation is delivered.

Phase 4.5 – Post-Deployment Support

The Vendor will provide post-deployment support as specified in the Scope of Work. This support occurs following the execution and approval of the Test Plan.

Phase 5: Project Closeout

A Project Closeout Meeting will be held to review the project as a whole. The team will review the original objectives and scope of the project and the high-level tasks that were completed during implementation. A milestone timeline will be evaluated against the schedule baseline and any significant deltas will be discussed, in addition to any Change Orders that were submitted. Most importantly, the Customer team will be asked to provide any feedback on the overall project and participating resources from the Vendor to collect Lessons Learned for continual improvement.

Phase 5.1 – As-built Document

The Vendor will capture redlines to design drawings for development of the As-Built Document. The Vendor will deliver the As-Built Document after completion of post-implementation support and prior to the Project Closeout meeting.

Phase 5.2 – Project Completion Acceptance

During the Closeout meeting, Customer will be presented with the final Items Provided to Customer. Customer will be required to sign off on the Project Closeout document, thus signifying project acceptance.

In the event either party desires to change this scope of work, the following procedures will apply.

• The Vendor will deliver a change request form to the Customer.

• The change order request may be initiated by either party and will describe the nature of the change, the reason for the change, and the effect the change will have on the statement of work, which may include changes to the Items Provided to Customer and/or the schedule.

• The Project Manager of the requesting party will review the proposed change with his/her counterpart and negotiate in good faith the changes to the services and the additional charges, if any, required to implement the change order request.

• If both parties agree to implement the change order request, a modification incorporating the change to the existing contract/purchase order will be issued by the customer Contracts Representative or Buyer for execution by both parties.

• The Vendor is under no obligation to proceed with the change order request until such time as the change order request has been agreed upon by both parties.

GENERAL RESPONSIBILITIES AND ASSUMPTIONS

This SOW is based on the following assumptions.

Schedule

1. Project schedules must be confirmed at minimum two (2) weeks after the Project Kickoff to secure resource availability. If confirmation does not occur, resources may be released for other engagements and may need to be rescheduled based on availability.

2. If applicable, project timelines and installation dates are dependent upon verification of delivery of the items listed in the BOM.

3. Vendor's SOW is predicated on timely receipt and availability of Customer-furnished equipment, property, software, information or access to facility as described in this SOW. All such Customer-furnished equipment, systems, and software shall be functional and in good operating condition to ensure Vendor can timely and successfully start the project. Customer will guarantee that all required site preparations have been completed prior to the arrival of Vendor resources. Due to its dependency on these items to meet the proposed schedule, Vendor retains its right to secure an equitable price and/or schedule adjustment in the event of any resulting Customer delay.

4. If the project is put on hold for more than thirty (30) days due to Customer delays or the Customer fails to engage within thirty (30) days of project award, Vendor may exercise its rights to any or all of the following: reassign resources, invoice for all equipment delivered to Vendor, charge storage fees, require ten (10) business days from the point of reengagement to reallocate resources to the project and request equitable adjustment. If Vendor has to hold the equipment for more than thirty (30) days due to Customer delays, Customer will accept delivery at Vendor's warehouse via onsite verification or packing slip verification. Title and risks of ownership will pass to the customer upon acceptance of delivery at Vendor's warehouse.

Communication

5. Customer will assign a project sponsor responsible for approval/resolution of escalation and issues and must assign a daily point of contact for the Vendor Project Manager to work with for the duration of the project. This contact must work with the Vendor Project Manager, provide assistance and support should issues arise that require Customer specific decisions and be available for all key project milestones and meetings. Customer will assign a Project Sponsor solely responsible for approval/resolution of escalation and issues.

6. Customer must keep the Vendor Project Manager apprised of business, organizational and technical issues that may have impact on the performance and delivery of the project. Changes to any system that are related to or impact the solution being installed should be discussed with Vendor prior to implementation. Any changes could have impact to price, scope, SOW, and/or scheduling of the project.

7. Customer must provide technical support for implementation team during scheduled deployment as detailed in the project schedule. Customer will be responsible for implementing any and all required hardware or software infrastructure changes and be available for all key project milestones and meetings.

8. Customer is responsible for any internal change control processes necessary to implement the solution into their production environment. This includes but is not limited to submitting necessary documentation for internal review and approval for scheduling appropriate system maintenance windows and securing proper resources for support and testing.

9. During a cutover, a System Administrator who possesses all system passwords must be available for the duration of the cutover.

Workspace

10. The Customer understands and will provide accommodations to include the following:

o Provide a safe, compliant with all applicable building/safety codes, working conditions, with a minimum of 10x12 feet of climate-controlled, secured space with lighting, power, and internet access, that are conducive for the successful completion of the project including suitable office space, telephone access and meeting facilities;

preferably convenient to the general work area and can serve as a staging and storage area of BOM hardware, tools and testing equipment, when applicable.

o Guarantee site access to building(s) where work will take place, including, but not limited to, loading docks, freight elevators, service corridors, and parking facilities for work vehicles, and availability as scheduled and coordinated with the site representative. If work will be performed outside of normal working hours, Customer personnel will be available to facilitate the required access.

Scope of Work

11. Reserved.

12. Any tasks/Items Provided to Customer not specifically identified within the SOW section: Scope of Work are considered out of scope for this project.

13. All existing hardware and software must be functioning and adequately licensed by Customer, and maintenance service contracts must be active.

14. All software and software license products and purchases are subject to the terms and conditions of the software

Vendor(s) or licensor(s)'s end-user license agreement (EULA). Customer must accept and execute the applicable EULA(s). All warranties with respect to any software product, license, or Customer use thereof, are expressly limited in scope, coverage, and duration to the warranties provided by the software product Vendor or licensor.

15. The version at the time of submission of the Design Document is the final version Vendor is responsible for installing.

16. Vendor will not be responsible for any software bugs encountered that are not directly related to the solution presented in the Design Document. This includes both software bugs identified during the integration of the solution, or as a result of a code upgrade necessary for the agreed upon solution outlined in the Design Document.

Vendor considers this type of incident outside of our control and the customer will be responsible for resolving the issue directly with the original equipment manufacturer (OEM).

17. When executing the Test Plan, Vendor will not be responsible for troubleshooting and resolving any deficiencies found that were created by other factors in the customer environment. Customer will have fifteen (15) business days to resolve the issues with their resources so that Vendor can execute the Test Plan again and determine if the deficiency is resolved. If Customer issues are not resolved within fifteen (15) days, Customer agrees to accept the deficiencies as the acceptable baseline to transition into operations and therefore close out the project.

18. Knowledge transfer is not a replacement for classroom training but is intended to help the Customer gain a working knowledge of implementation details specific to their environment. Product training is available for an additional fee through our certified training partners.

19. Vendor is not responsible for the removal of boxes and packing materials provided for the shipment of the Customer equipment.

20. Vendor will not complete any cutover or testing in an environment that is not fully operational and configured to support the solution.

21. Vendor will hold no responsibility for any changes made after releasing the system to Customer. If any errors occur following the release, a Change Order must be approved for associated labor and travel to correct the issue.

Services not specified in this SOW are considered out of scope and will be addressed with a separate SOW or Change Order.

• Customer is responsible for providing all access that is reasonably necessary to assist and accommodate Vendor’s performance of the Services.

• Customer will provide in advance and in writing and Vendor will follow, all applicable Customer’s facility’s safety and security rules and procedures.

• Customer is responsible for security at all Customer-Designated Locations; Vendor is not responsible for lost or stolen equipment, other than solely as a result of Vendor’s gross negligence and willful misconduct.

• Customer acknowledges that in order to efficiently and effectively perform the Services the vendor may need to collect information from Customer’s systems by using software tools developed or used by the vendor's (“Tools”).

In some cases, these Tools will need to be loaded onto the Customer’s systems to gather necessary information, and the vendor may also use them to make changes in the Customer’s systems consistent with the agreed upon scope.

Tools will be used only for purposes of performing the Services and will be removed or automatically deleted when Vendor has completed use of them. Customer hereby consents to vendors use of the Tools as set forth in this paragraph.

• Upon completion of the Services, Customer is responsible for disabling or deleting all vendors coworker access credentials and completing any other necessary steps to ensure that access to all of Customer’s environments has been permanently terminated for all vendor coworkers and contractors that were part of this engagement.

• This SOW can be terminated by either party without cause upon at least fourteen (14) days’ advance written notice.

CONTACT PERSONS

Each Party will appoint a person to act as that Party’s point of contact (“contracting officer”) as the time for performance nears and will communicate that person’s name and information to the other Party’s contracting officer.

Customer contracting officer is authorized to approve materials and Services provided by Vendor, and Vendor may rely on the decisions and approvals made by the Customer contracting officer (except that Vendor understands that Customer may require a different person to sign any Change Orders amending this SOW). The Customer contracting officer will manage all communications with Vendor, and when Services are performed at a Customer-Designated Location, the Customer contracting officer will be present or available. The Parties’ Contact Persons shall be authorized to approve changes in personnel and associated rates for Services under this SOW.

CHANGE MANAGEMENT

This SOW may be modified or amended only in a writing signed by both Customer and Vendor, generally in the form provided by Vendor (“Change Order”). Services not specified in this SOW are considered out of scope and will be addressed with a separate SOW or Change Order.

In the event of a conflict between the terms and conditions set forth in a fully executed Change Order and those set forth in this SOW or a prior fully executed Change Order, the terms and conditions of the most recent fully executed Change Order shall prevail.

PERIOD OF PERFORMANCE

The period of performance (“Period of Performance”) for Services provided in this Statement of Work shall be from Jun 24 2025 to Mar 31 2026. Should additional time to complete Services be required, the parties shall agree upon a revision to the Period of Performance in writing.

PROJECT SCHEDULING

Customer and Vendor, who will jointly manage this project, will together develop timelines for an anticipated schedule (“Anticipated Schedule”) based on Vendor’s project management methodology. Any dates, deadlines, timelines or schedules contained in the Anticipated Schedule, in this SOW or otherwise, are estimates only, and the Parties will not rely on them for purposes other than initial planning.

The following scheduling scenarios that trigger delays and durations to extend beyond what's been planned may require a Change Order:

• Site preparation, such as power, cabling, physical access, system access, hardware/software issues, etc. must be completed in a timely manner.

• Project tasks delegated to Customer PMs/Engineers/Techs/Management/Resources must be completed in a timely manner. For example, in the event a project 's prioritization is demoted, and Customer resources are reallocated causing the project's schedule to extend on account of experiencing interruptions to its momentum requiring complete stop(s) and start(s).

• External projects/dependencies that may have significant impact on the timeline, schedule and deliverables. It is Vendor's assumption that every reasonable attempt will be made to mitigate such situations.

TOTAL FEES

The total fees due and payable under this SOW (“Total Fees”) include both fees for Vendor’s performance of work (“Services Fees”) and any other related costs and fees specified in the Expenses section (“Expenses”).

Vendor will invoice for Total Fees. Customer will pay invoices containing amounts authorized by this SOW in accordance with the terms of the Agreement. Unless otherwise specified, taxes will be invoiced but are not included in any numbers or calculations provided herein. The pricing included in this SOW expires and will be of no force or effect unless it is signed by Customer and Vendor within thirty (30) days from the Date listed on the SOW, except as otherwise agreed by Vendor. Any objections to an invoice must be communicated to the Vendor contracting officer within fifteen (15) days after receipt of the invoice.

This SOW may include multiple types of Services Fees; please reference below Services Fees section(s) for further details.

EXPENSES

Vendor will invoice Customer for Vendor’s reasonable, direct costs incurred in performance of the Services. Direct expenses include, but may not be limited to: airfare, lodging, mileage, meals, shipping, lift rentals, photo copies, tolls and parking.

Vendor will charge actual costs for these expenses. Any projected expenses set forth in this SOW are estimates only.

CUSTOMER-DESIGNATED LOCATIONS

Vendor will provide Services benefiting the following locations (“Customer-Designated Locations”)

Location Address

New York, New York 1 Federal Plaza, New York, NY 10278

Qty MFR Part # Description

17 C9300-48P-E Catalyst 9300 48-port PoE+, Network Essentials

17 CON-SNT-C93004PE SNTC-8X5XNBD Catalyst 9300 48-port PoE+, Network Esse

17 C9300-NW-E-48 C9300 Network Essentials, 48-port license

17 SC9300UK9-1712 Cisco Catalyst 9300 XE 17.12 UNIVERSAL

17 PWR-C1-715WAC-P 715W AC 80+ platinum Config 1 Power Supply

17 PWR-C1-715WAC-P/2 715W AC 80+ platinum Config 1 SecondaryPower Supply

34 CAB-TA-NA North America AC Type A Power Cable

17 C9300-SSD-NONE No SSD Card Selected

17 C9K-ACC-RBFT RUBBER FEET FOR TABLE TOP SETUP 9200 and 9300

17 C9300-DNA-E-48 C9300 DNA Essentials, 48-Port Term Licenses

17 C9300-DNA-E-48-3Y C9300 DNA Essentials, 48-port - 3 Year Term License

17 C9K-ACC-SCR-4 12-24 and 10-32 SCREWS FOR RACK INSTALLATION, QTY 4

17 CAB-GUIDE-1RU 1RU CABLE MANAGEMENT GUIDES 9200 and 9300

17 C9300-NM-8X Catalyst 9300 8 x 10GE Network Module

17 NETWORK-PNP-LIC Network Plug-n-Play Connect for zero-touch device deployment

17 STACK-T1-50CM 50CM Type 1 Stacking Cable

17 CAB-SPWR-30CM Catalyst Stack Power Cable 30 CM

3 C9300-24P-E Catalyst 9300 24-port PoE+, Network Essentials

3 CON-SNT-C93002PE SNTC-8X5XNBD Catalyst 9300 24-port PoE+, Network Esse

3 C9300-DNA-E-24 C9300 DNA Essentials, 24-Port Term Licenses

3 C9300-DNA-E-24-3Y C9300 DNA Essentials, 24-Port, 3 Year Term License

3 C9300-NW-E-24 C9300 Network Essentials, 24-port license

3 SC9300UK9-1712 Cisco Catalyst 9300 XE 17.12 UNIVERSAL

3 PWR-C1-715WAC-P 715W AC 80+ platinum Config 1 Power Supply

3 PWR-C1-715WAC-P/2 715W AC 80+ platinum Config 1 SecondaryPower Supply

6 CAB-TA-NA North America AC Type A Power Cable

3 C9300-SSD-NONE No SSD Card Selected

3 STACK-T1-50CM 50CM Type 1 Stacking Cable

3 CAB-SPWR-30CM Catalyst Stack Power Cable 30 CM

3 C9K-ACC-RBFT RUBBER FEET FOR TABLE TOP SETUP 9200 and 9300

3 C9K-ACC-SCR-4 12-24 and 10-32 SCREWS FOR RACK INSTALLATION, QTY 4

3 CAB-GUIDE-1RU 1RU CABLE MANAGEMENT GUIDES 9200 and 9300

3 C9300-NM-8X Catalyst 9300 8 x 10GE Network Module

3 NETWORK-PNP-LIC Network Plug-n-Play Connect for zero-touch device deployment

PROJECT DESCRIPTION

PROJECT SCOPE

This statement of work outlines the scope of services to support the Customer with optimizing their existing Cisco Identity Services Engine (ISE) solutions robust comply-to-connect (C2C) enforcement within wired network environment.

The primary business objective of the Cisco ISE Optimization Services is to significantly improve the security posture of the Customer’s network environment where ISE is being implemented. This ISE services engagement supports the implementation of the Zero Trust (ZT) architecture, which is essential for modern cybersecurity strategies. Such improvement enhances operational efficiency, reduces security risks, and supports strategic IT initiatives.

TECHNICAL OVERVIEW

The following scope of work is based on Vendor’s current understanding of this project's requirements. This document provides the steps required for a successful Cisco ISE optimization of 802.1x and MAC Authentication Bypass (MAB) authentication and authorization on the wired network. The ISE environment consists of two (2) node, one physical (SNS-3615) appliance and one virtual instance, configured as a 2-Node cluster. The goal is to provide a fully functional

802.1 x/MAB authentication and authorization implementation for up to one hundred and ten (110) endpoints on the Wired network.

Technical Components

No procurement of additional hardware/software components is required for this project SOW.

Technical Design

The following diagram is a logical representation of the Comply-to-Connect (C2C) functionality for the ISE solution.

PROJECT SERVICES

Vendor is to conduct the following services ("Services") under the terms and conditions of this SOW: Phase

1: Project Kickoff

• Team Introduction

• Project Goals and Objectives Validation

• Project Scope and Methodology Review

• Project Milestone Schedule Review

• Project Administration Overview o Escalation o Role & Responsibilities o Security Requirements (Physical, Network, and Certification)

• Next Steps Discussion

Phase 2: Requirements Gathering

• Review and define specific objectives and capabilities

• Review network environment o Baseline current configuration o Existing network architecture and diagrams o Network addressing (IPs, VLANs, etc.)

o Network services (DHCP, DNS, etc.)

o Existing applications and systems (AD, Exchange, etc.)

o Segmentation requirements o User access and traffic scenarios o Endpoint analysis (software, desktop, OS) o Organization security policies and imperatives

• Review ISE infrastructure requirements

• Review wired MAB and 802.1X authorization requirements

• Review switch requirements, existing configuration, and new configuration requirements

• Review ISE profiling requirements

• Review customer's change management procedures and operational protocols

• Identify pre-deployment requirements

• Determine and agree upon a cutover window or windows

• Define phased deployment strategy

• Develop a customer appropriate test plan for post cutover

Items Provided to Customer

• Requirements Gathering Document

• Pre-Implementation Checklist

Phase 3: Design Planning

• Define ISE specifications, configuration, and upgrade/migration path

• Document ISE feature configuration for production environment, including:

o Up to one (1) Wired Policy Set

Up to five (5) new Profiling templates

Up to three (3) Authentication Rules

Up to ten (10) Authorization Rules o Up to one (1) Production Wired Network

• Document any required end computer changes, including:

o Operating System (OS) updates and/or patches o 802.1x supplicant provisioning

• Document ISE supported repositories for data and/or software backup and auditing

• Provide Customer with Design Document for review and acceptance o With up to two (2) minor revisions

Items Provided to Customer

• Design Document

• Implementation Plan

• Test Plan

Phase 4: Implementation

• Upgrade the ISE cluster to the latest gold-start/recommended software and patch level, including

• Provision and apply certificates, if applicable

• Provision the 802.1x supplicant on up to three (3) test machines

• Enable and test ISE features in a pilot environment for up to two (2) network switches of various platforms

• Perform up to five (5) cutovers on the production network in accordance with schedule developed by project management in coordination with engineering team o Deploy ISE features on wired network in monitor mode during agreed upon change window(s) for up to one hundred and ten (110) endpoints o Deploy ISE features in close mode where applicable o Execute test plan following each cutover window o Validate new operating environment

• Provide up to ten (10) hours of Day One support, in increments of two (2) hours per cutover, to assist with troubleshooting and fixing issues that may arise following migration

• Prepare As-Built document for customer, documenting the solution as deployed as well as any auxiliary information relevant to the solution

Items Provided to Customer

• Project Closeout Document

• As-Built Document

Phase 5: Project Closeout

• Conduct Project Closeout meeting and activities

PROJECT ASSUMPTIONS & CONDITIONS

1. Reserved

2. All work will be performed at Vendor offices and/or the customer's location at: 4901 Tesla

Drive Bowie, Maryland

3. Unless otherwise noted, all work will be performed during normal working hours, Monday through Friday, 8:30 am

– 5:30 pm local time, unless agreed upon by both parties during the Project Kick Off phase. Customer will guarantee site access and availability as scheduled and coordinated with the site representative. If work will be performed outside of normal working hours, customer personnel will be available to facilitate the required access.

4. Customer will receive and securely store all components as they arrive at the location(s) of performance, if applicable.

5. Customer will supply Vendor staff with appropriate authorization and passwords to perform work.

6. Customer will be responsible to implement all required network infrastructure updates.

7. Customer will present all requirements of the implementation during the Requirements Gathering phase.

8. Customer will provide space for backup of solution using either FTP, SFTP, NFS, HTTP, HTTPS.

9. Customer will provide configuration and cabling data of the currently installed network devices, which may integrate with the new network architecture.

10. Customer will keep the Vendor Project Manager apprised of the status of all other work being performed that directly affects our work on this project.

11. Customer will be responsible for configuring any third (3rd) party authentication servers, which will integrate with

ISE. These servers are referred to as identity stores in ISE; each identity store has varying requirements for ISE integration. Common caveats include one (1) Active Directory Global Catalog Server for the domain being authenticated against, synchronized time via NTP server(s) between ISE, network devices, and the identity store(s), ensured trust relationships between the domain to which Cisco ISE is associated and relevant domains. Additionally, EAP certificate authentication methods may be limited due to the type of identity store, for instance LDAP integration requires GTC inner encryption. (Example, identity stores = Active Directory, LDAP, CAC).

12. Customer will be responsible for providing certificates for the servers, as well as client certificates (if applicable).

13. Customer will be responsible for the acquisition and management of trusted signed certificates for authentication.

Vendor will provide the associated CSR files. All root and intermediate certificates will be provided by Customer. Additional caveats around certificate installation may be identified during the Requirements Gathering Phase.

14. Only ISE compatible network access devices (NADs) and endpoints are within scope. A listing of compatible devices can be provided upon request.

15. Customer will be responsible for any client supplicant/software and/or operating system upgrades required for integration with ISE.

16. Customer will be responsible for the deployment and configuration of client agents/supplicants to clients for Group Policy Objective (GPO), System Center Configuration Manager SCCM, etc. Vendor will provide guidance on this process, if required.

17. Customer will be responsible for providing and managing additional repositories for backup image and software storage.

18. The production network(s) will be inspected against best practice design standards during the requirements gathering phase, should additional components be required, a change request may be necessary to remediate issues discovered during this phase.

19. During a cutover, a System Administrator who possesses all system passwords must be available for the duration of the cutover.

20. Customer must provide and complete all Project Specific Responsibilities outlined in this section. If responsibilities indicated in this section are not completed prior to the deployment date, the project timelines will need to be rescheduled based on engineering availability. As a result, all additional travel costs will be charged to the customer.

Vendor is qualified to provide most of these services listed in this section upon request. A quote for these services can provided as a separate unsolicited SOW as needed.

21. Unless otherwise stated in this SOW, Security Technical Implementation Guide (STIG) application is not considered to be in scope for this project.

22. Certification and Accreditation services are not included in this SOW.

23. In the event that the customer would prefer an unlisted Use Case, both parties (Vendor and Customer) must agree on the implementation and execution of those tasks with a modification to the SOW.

ITEMS PROVIDED TO CUSTOMER

ITEMS PROVIDED TO CUSTOMER FORMAT

The Vendor will submit Items Provided to Customer in electronic form and will produce reports using Microsoft Office Professional Suite (Word, Excel, Access, and PowerPoint), Microsoft Project, and/or Visio. All Items Provided to Customer and their acceptance criteria for this SOW includes:

Project Kickoff Project Schedule Final after five (5) day review period

Requirements Gathering

Requirements Gathering Document Final after five (5) day review period

Pre-Implementation Checklist Signature required two (2) weeks prior to implementation

Design

Design Document Signature required

Implementation Plan Submittal

Test Plan Submittal

Implementation Executed Test Plan Signature required

Project Closeout Project Closeout Document Final after five (5) day review period

ITEMS PROVIDED TO CUSTOMER REVIEW AND ACCEPTANCE CRITERIA

For any document identified above as Final after five (5) Day Review Period, stakeholders will have five (5) business days from submission of these Items Provided to Customer to review and provide comments and/or feedback. If the Customer does not provide any feedback after the five (5) day review timeframe, Vendor will consider the Items Provided to Customer final and will be used to progress to the next phase of the project.

The Vendor will consider incorporating comments and/or feedback provided by the Customer within the five (5) day review timeframe. Any resulting revision to the Items Provided to Customer will be considered final.