Request for Proposal OCHIN, INC. IT Service Delivery Network

Introduction Background and Opportunity Definition OCHIN, INC. is a nonprofit healthcare innovation center designed to provide knowledge solutions that promote quality, affordable healthcare for all. OCHIN, INC. is transforming healthcare to improve outcomes and reduce costs demands for both innovation and collaboration. It takes individuals and communities working side-by-side to design relevant and reasonably priced information technology and data solutions that can be shared across the healthcare continuum. OCHIN, INC. hosts Electronic Health Records (EHR) on the EPIC platform, as well as other IT and Application services via a shared infrastructure in a primary and backup data center facility.

Technical requirements Each of the OCHIN, INC.’s clinics are an enterprise in their own right, with routing domains, security policies, and a secured OCHIN, INC. segment at one of or both of our data center facilities. You can view OCHIN, INC. as an Application Service Provider that has many Enterprise customers that all access OCHIN, INC. applications delivered via one of our OCHIN, INC. facilities. Each Enterprise has their own IP addressing scheme, usually RFC1918 based that access OCHIN, INC. applications on public IP segments routed across our existing (and future) MPLS offerings. These customers connect to OCHIN, INC. via some sort of WAN or VPN/GRE tunnels that OCHIN, INC. provides. In most cases, OCHIN, INC. provides its own CPE router to our clinics where we handle primary and backup VPN, as well as provide Network address translation and firewall services. We also offer what we call ‘colo’ access – where the clinic can rent space and power from OCHIN, INC.’s data center facilities and provide their own compute, storage, and network infrastructure. The high level requirements of this solution are to: 1. Phase I: Provide our clinics access over an MPLS network to our shared applications on public IP subnets where OCHIN, INC. controls routing updates and access for the clinics 2. Phase II: Provide Infrastructure as a Service (IaaS) solutions, which will require allowing for RFC1918 routing from the clinics directly into our shared infrastructure (via isolated routing domains). The requirements of a Service Delivery Network are to provide a WAN infrastructure that meets the following criteria: 

Must Provide: o Access between each enterprise, all of its remote rooftops / locations within a single routing domain / VRF o Provide access between OCHIN, INC. shared application segments delivered from 2 OCHIN, INC. data centers initially, with the ability to grow to x number of data centers, and each remote enterprise network segment o Provide security via separation of routing domains in the Service Provider network (separation of routing domains on CE devices will not meet our requirements)

OCHIN, INC. to control IP routing updates between CPE devices and the OCHIN, INC. shared segments to the Service provider network. o OCHIN, INC. to control IP routing updates between CPE devices within the same enterprise o Access method for remote locations; Ethernet (or equivalent) with end to end SLAs (this criterion is included as a component of the Technical Solution scoring, for meeting OCHIN’s technological needs):  Ethernet (or equivalent) to be provided directly to the clinic via fiber (or equivalent) build out. T1 aggregation devices or NxT1 solutions are not preferred. We expect that fiber (or equivalent) build out proposals on a per site basis will be required. These locations should be called out and preference will be given in this order  Fiber (or equivalent) to the building with Ethernet (or equivalent) Hand-off  T3 with Ethernet (or equivalent) handoff  NxT1 solution as required o IP Quality of Service is required with templates that allow flexible configuration of QoS policies on a per customer, per application basis o Required Access method for Data Center connectivity is primary and redundant Gigabit Ethernet (or equivalent) over Single Mode Fiber (or equivalent) in our primary facility with a single Ethernet (or equivalent) drop in our DR facility. Must provide tiered pricing with low monthly commits for backup circuits o Ability to provision as many VRFs as required to support our customers, without additional cost per VRF Optional, preference given to providers that can provide the following (this criterion is o



included as a component of the Technical Solution scoring, for meeting OCHIN’s technological needs): o

o o

The capability for each routing entity to route via the Service Provider network to the Internet  In this scenario, the provider would inject default route into the routing domain and provide firewall services to the Internet Provide Inter-AS options (A, B, or C) with preference given to Option C, for connectivity to the OCHIN, INC. Data Centers Provided Carrier Supporting Carrier capabilities with the goal of minimizing operational management and economically extending the service providers MPLS network beyond their borders.  As an example, if Clinic A has existing contracts with MPLS provider A, can you provide a carrier supporting carrier or some form of Inter-AS option with MPLS provider A? We realize there are many moving pieces with this request.

Technical Diagram as an Illustration OCHIN Primary Hosting Facility

OCHIN Backup Hosting Facility

Segment-F Shared Segment-H

Customer A

Customer B

Customer B

Customer A

Segment-E

Segment-G

Segment-J Segment-I

Inter‐AS Options Sub‐If/Label  xchange

Inter‐AS Options Sub‐If/Label  xchange

Optional Internet

Optional Internet

Carrier MPLS Network

Internet / IPSec VPN

PE - router

PE - router

Internet / IPSec VPN

QoS Enabled Backbone

Optional Internet

PE - router

Segment-K

Optional Internet PE - router

Segment-A

Segment-D

Location A Segment-B Location B

Segment-C

Customer B

Customer A

Routing, Security and Access requirements The above diagram has the following components: 



 

Customer A o Locations A and B are physically separate locations that can be separated geographically or within the same city, etc. o Location A and B have rack space, servers, and network segments housed in OCHIN, INC. data center facility at segment E. On Segment E there is OCHIN, INC. Customer B o Locations C and D are physically separate locations that can be separated geographically or within the same city, etc. o Location C and D have rack space, servers, and network segments housed in OCHIN, INC. data center facility at segment G. OCHIN, INC. OCHIN, INC. Shared segments F and H are EPIC and other shared services applications that all Member clinics will require access to. OCHIN, INC. Operations will provide the internal routing and segmentation to allow this connectivity An Internet segment K to illustrate the requirement for some locations to access the Internet via the MPLS cloud / shared circuit as an option

The following table attempts to illustrate the bi-directional connectivity requirements between clinic networks to the data centers, each other, and the Internet (refer to the diagrams for locations of each segment).

Network Segments A – Routes to  B – Routes to  C – Routes to  D – Routes to    

A

B

C

D

X X X X

E

F

X X

X X X X

G

H

I X X

X X

X X X X

J

K

X X

X X X X

Customer A and B MUST not have ability to access each other via the Service Provider network or via OCHIN, INC. shared segments. Customer A and B segments in OCHIN, INC.’s Hosting facilities MUST not be able to communicate with each other or the other enterprises segments via the OCHIN, INC. data centers (this is an OCHIN, INC. problem to solve). OCHIN, INC. Shared Segments should have bidirectional communication to each Customers VPN/VRF (A and B in the scenario above).

Access and Transport Requirements 1. Transport Internet Protocol (IP) data packets to and from a specified Ethernet (or equivalent) at each physical address for which service is contracted. Other communications protocols may be used to transport data packets; however, IP over Ethernet (or equivalent) is required at the user and network interfaces. 2 2. Following the Open Systems Interconnection (OSI) model : Layer three interfaces will be Internet Protocol version four (IPv4) with a potential future upgrade to version six (IPv6) after the initial period of contracted service. Preference given to providers that can provide a dual IPv4 and IPv6 stack. Layer two interfaces will be Ethernet (or equivalent) only. Layer one may be any physical medium (fiber optic cable, co-axial cable, copper wire, wireless, satellite or other) meeting the performance requirements specified below (this criterion is included as a component of the Technical Solution scoring, for meeting OCHIN’s technological needs). 3. OCHIN, INC. prefers Ethernet (or equivalent) hand-off to the OCHIN, INC. end-user sites, without the use of NIDS or any other type of aggregation device. No NxT1 solutions are permitted. 4. For all OCHIN, INC. designated Data Center facilities, providers MUST provide complete PE router L1 and L2 diversity. For example, we require complete L1 diversity into and out of the data centers via dual-ring connections as well as PE router diversity for primary and back last mile circuits. For data center circuits, Fiber Optic hand-off over Single Mode fiber (or equivalent) is required. 5. The data capacity between each OCHIN, INC. provider network shall be a minimum of 10Mbps Ethernet (or equivalent). 6. Transport services must be available with at least 99.99 percent reliability. [Note: this availability level permits approximately 52 minutes of unscheduled downtime per year.] Even though the “tail-circuit” into the end-user facility need not be redundant, OCHIN, INC. will give preference to proposers with geographic route-diversity from the community in which the end-user facility is located to the exchange facility (this criterion

is included as a component of the Technical Solution scoring, for meeting OCHIN’s technological needs). No proposal will be accepted without a response to this

request and a sample of the final SLA that lists the terms and conditions of the proposers’ acceptance of this requested metric. 7. Latency is network transit delay. Preference will be given to carriers that provide the lowest latency between Remote Clinics Provider Edge (PE) router and the OCHIN, INC. Datacenter Provider Edge (PE) routers. Transit delay being measured between the served end user site and the OCHIN, INC. datacenters (this criterion is included as a

component of the Technical Solution scoring, for meeting OCHIN’s technological needs).

8. Packet Loss is generally a measure of capacity and traffic congestion. The number of data packets requiring retransmission shall not exceed 0.3 percent (three per thousand) between PE routers and 1 percent for end-to-end loss between Remote Clinics Provider Edge (PE) router and the OCHIN, INC. Datacenter Provider Edge (PE) routers. The OCHIN, INC. recognizes that how performance is tested will determine how the data are reported. To this end, OCHIN, INC. wants to know what independent measures will be used to validate transport performance. Tools such as OWAMP, the One-Way Active Measurement Protocol, test for jitter, latency and packet loss. Please include in your proposal how measurements (the tool, the test) for latency, jitter and packet loss will be obtained. No proposal will be accepted without a response to this request and a sample of the final SLA that lists the terms and conditions of the proposers acceptance of this requested metric.

9. The data access and transport provider must be willing to agree to Service Level Agreements (SLAs) with financial penalties for service outages, lack of availability of the contracted service capacity and any failure to meet quality of service specifications for transit delay, jitter and packet loss or repair. Please include a sample SLA and your escalation process in your proposal. No proposal will be accepted without a sample SLA. 10. The data access and transport proposals must offer a price schedule that specifies the one- time non-recurring construction and/or installation charges and the monthly recurring prices for a contract length of up to 36 month service contract with options for renewal for an intermittent length of time from the start of service. Please note that all pricing will be graded using a fixed 36 month term to normalize the pricing for the purposes of the proposal review. Please be sure that all pricing presented to OCHIN, INC. reflects a 36 month service period on the Pricing Breakdown Template spreadsheet that OCHIN, INC. will provide you upon receipt of your intent to bid notification. Send all Intent to Bid Notifications to Courtney Stennick, Program Manager: [email protected]. Other contract periods may also be offered in the proposal. Please insure that all pricing include all taxes and fees including a FORECAST of all taxes and fees throughout the initial term. FCL’s are going to run July 1 – June 30 per funding year. 11. Proposals must list all telecommunications providers that will be subcontractors for the proposed services. 12. Proposals must list underlying physical transport technologies that will be used in providing the proposed services. 13. Proposals must list the port configurations they plan to use. 14. OCHIN, INC. proposals must contain a network diagram for each client site that is proposed. Multiple sites that are interconnected should be diagramed together on the same network diagram. No proposal will be accepted without a network diagram for all proposed sites. 15. Upon completion of site install, Proposers must agree to provide OCHIN, INC. and the NOC with a completed network information form that will be provided to the Proposer by OCHIN, INC. upon receipt of a funding commitment letter from USAC, and provide to either the NOC or OCHIN, INC. upon request, technical information necessary to monitor performance and assist with the purpose and implementation of the pilot program. In addition the proposer must agree to work with OCHIN, INC.’s IT Project Manager and other staff as assigned, to provide regular build updates throughout the installation phase of any awarded proposal. 16. Proposers must specify the extent to which they provide route diversity between each OCHIN, INC. end-user site and the locally attached PE routers as well as redundancy to the OCHIN, INC. data center PE routers. 17. Proposers must agree to provide full layer 3 BGP peering OCHIN, INC. between all OCHIN, INC. end-user sites and OCHIN, INC. data center facilities. At the data center facilities, Preference will be given to providers that will work with OCHIN, INC. technical staff in designing and provisioning MPLS inter-as options for label exchange (this

criterion is included as a component of the Technical Solution scoring, for meeting OCHIN’s technological needs).

18. Proposer must provide OCHIN, INC. with the ability to control and influence routing paths and routing updates via BGP communities or weight metrics, and bi-directional forwarding detection capabilities. 19. Proposers who can provide a provisioning API for automated sales, implementation, and support needs will be given preference (this criterion is included as a component of the Technical Solution scoring, for meeting OCHIN’s technological needs). The idea here is to move away from provisioning spreadsheets in Microsoft Excel format to an

20. 21. 22.

23.

24.

25.

automated, paperless system. We are open to discussion on this point and look forward to proposers’ solutions in this regard. Proposers must provide a clear estimated time frame for installation post-award and after a USAC Funding Commitment Letter has been received by the vendor for each Proposal. All Proposals should provide a detailed breakdown of costs per site for all non-recurring installation costs. Proposals must include any and all federal and state Regulatory Fees or other fees/taxes, both current and anticipated future increases, in your Proposal numbers. In addition, all Proposers must agree to add all taxes and fees to all applicable charges as a separate line item, subject to exemption. All taxes and fees MUST be included on the OCHIN, INC. Pricing Breakdown Spreadsheet. Failure to properly list all taxes will result in the Proposer paying the difference or a retraction of the award by OCHIN, INC. Proposers must agree to follow and comply with all administrative, invoicing and accounting processes and procedures that are necessary to comply with FCC and USAC requirements. These requirements include, but are not exclusive, to the submitting of detailed invoices in a timely manner via OCHIN, INC.’s current invoicing process which includes submitting invoices via OCHIN, INC.’s SharePoint portal system, as well as USAC’s MyPortal system. All awarded proposers will must negotiate a Master Services Agreement (MSA) with OCHIN, INC. which incorporates this RFP and which otherwise complies with applicable FCC rules and USAC requirements. OCHIN, INC. members will be permitted but not required to purchase services from vendor(s) pursuant to the MSA. Unless submitting a bid that offers only a Standardized Pricing Formula, all bids should provide a detailed breakdown of costs per site for all non-recurring installation costs per the provided spreadsheet which includes FCC/USAC required cost detail per their mandatory reporting and review requirements. This information must be included for all bids in excel format. Please use 1 tab per location and clearly label the tab by the location name listed on the site list in Appendix B of this document. This should be included in the OCHIN, INC. Pricing Breakdown Spreadsheet. A workbook will be sent to you upon receipt of your intent to bid electronic notification.

Additional Sites under Master Services Agreement (MSA) Any contract issued as a result of this RFP will be required to contain provisions permitting the addition of new sites, upgrading services, and adding additional services. This will be achieved with either a Site and Service Substitution or additional funding request (FRN) through USAC. Evaluation Criteria for Network Access and Transport Proposals With 100 total points available, proposals will be evaluated and assigned points based on the judgment of reviewers as to how well the respondent meets each of the following criteria. The categories for evaluation are indicated below.  Technology Solution (32%) o Providers that can meet the technology needs, as defined above, are given the highest score for this criterion  Pricing (33%)  Service Level Agreement (25%)  Account Management and Service ability (10%) o OCHIN, INC. requires a dedicated, global account management team that provides a single point of contact for all account management needs and escalations. The AM team will consist of:  An account manager for all pre-sales work and coordination

A design or Systems Engineer for design and architecture escalations for pre and post sales needs  Project management team for installations  Designated Support manager for working through technical, post-sales and installation issues Quality commitments, including commitment to work with the OCHIN, INC. NOC to resolve issues. Past performance including customer satisfaction, level of service, and ability to respond and resolve issues in a timely manner. 

o

Appendix A: Informational Discussions OCHIN, INC. is in the planning stages of learning what the possibilities are for delivering this network. Some options we would like to explore with carriers are: 



MPLS as a delivery mechanism to meet the above requirements o

Carrier to Carrier solutions and capabilities

o

MPLS VPN Multi-AS option AB peering with our data center(s)

o

Other methods of extending VRF’s to our data center

Other options that may utilize a Carrier’s network to accomplish our goals o

Filtering and routing based on BGP communities / VPNv4 addresses on PE routers

o

Other routing / security / filtering options

HCP # 24420 40908 22520 24396 40634 40712 41168 40344 40779 42281 40378 40724 40347 40893 40747 40504 25375 25266 41196 40814 40649 42259 40376 40384 40731 40659 40646 40896 40618 24292 24293 42374 42303 27672 42379 40997 41116 42377 24390 33566 27805 24411 42450 42593 40902 22988 23086 24395 24314 42446

Eligible for Healthcare  Connect Fund subsidy  (Y/N) Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y N Y Y Y Y Y N

Member Name AH Tillamook Medical Group AIDS Resource Center Wisconsin Alliance Medical Center Asher Community Health Center Axis Medical Center Baker County Health Department Bastyr Center for Natural Health Benton County Health Services Butte Community Health Center Community Health Center of Cape Cod Care Alliance St. Clair Clinic Caring Health Center, Inc. Main Street Clinic Cincinnati Health Department Ambrose Clement Health Center City of Houston Health Department Clackamas County Public Health Department Clatsop County Department of Public Health Coastal Family Health Center Rogue Community Health  Community Health Net Gary Community Health Center Cowlitz Family Health Center Crook County Health Department Deschutes County Health Department Dunes Family Health Care El Centro de Corazon International Community Health Center Jane Pauley CHC Jefferson County Public Health King County Public Health Dept. La Clinica del Valle Family Health Centers La Pine Community Health Center Lincoln County Health & Human Services Lynn Community Health Center Monterey County Health Department Mosaic Medical Bend Clinic National College of Natural Medicine Clinic Neighborhood Family Practice Neighborhood Health Center OHSU Family Medicine at Richmond Health Care) Open Door Community Health Centers Oregon Youth Authority Outside In Pacific University Peninsula Healthcare Connection People's Center Health Services Cedar Riverside Clinic Placer County Health Department Santa Cruz County Health Services The Rinehart Clinic Waterfall Clinic, Inc Women's Community Clinic San Francisco

Required  Bandwidth  (Mbps) 10 10 10 10 10 10 10 10 10 10 10 10 10 10.5 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 20 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10

Healthcare Provider Address  1000 3rd Street Tillamook, OR 97141 820 N. Plankinton Milwaukee, WI 53203 1381 University St. Healdaburg, CA 95448 712 Jay Street Fossil, OR 97830 1801 Nicollet Ave. Minneapolis, MN 55403 3330 Pocahontas Road Baker City, OR 97814 3670 Stone Way N. Seattle, WA 98103 530 NW 27th Street Corvallis, OR 97330 445 Centennial Ave Butte, MT 59701 107  Commercial Street, Mashpee, MA 02649 1530 Saint Clair Ave. Cleveland, OH 44114 1049 main St. Springfield, MA 01103 (1st floor IT Closet) 3101 Burnet Ave Cincinnati, OH 45229 8000 North Stadium Drive Houston, TX 77054 1425 Beavercreek Road Oregon City, OR 97045 820 Exchange St. Astoria, OR 97103 (server room) 2158 Exchange Street Ste 304 Astoria, OR 97103 8385 Division Rd. White City, OR 97503 1021 West 5th Ave. Gary, Indiana 46402 1057 12th Ave. Longview, WA 98632‐2509 375 NW Beaver St. Suite 100 Prineville, OR 97754 2577 NE Courtney Drive Bend, OR 97701 620 Ranch Rd. Reedsport, OR 97467 412 Telephone Rd. Houston, TX 77023 3820 Superior Ave. Ste 214 Cleveland, OH 44114 8931 E 30th St. Indianapolis, Indiana 46219 715 SW 4th St. Madras, OR 97741 401 5th Ave. Suite 1300 Seattle, WA 98104 3617 S. Pacific Hwy. Medford, OR 97501 51600 Huntington Rd. La Pine, OR 97739 1010 SW Coast Highway, Ste. 203 Newport, OR 97365 269 Union Street, Lynn, MA 01901 1441 Constitution Blvd., Bldg. 400, Suite 201 409 NE Greenwood Ave. Bend, OR 97701  049 SW Porter Street Portland, OR 97201 3569 Ridge Road Cleveland, OH 44102 3720 SW 141st Ave Ste 100 Beaverton, OR 97006 3930 SE Division Street, Portland, OR 97202 849 Pacific Ave. Hood River, OR 97031 750 16th Street Arcata, CA 95521 2001 Front Street NE, Salem, OR 97301 1132 SW 13th Avenue Portland, OR 97205 2163 College Way Forest Grove, OR 97116 33 Encina Ave. Ste 103 Palo Alto, CA 94301 425 20th Ave. S minneapolis, MN 55454 11583 C Avenue, Auburn, CA 95603 1080 Emeline Ave. Santa Cruz, CA 95060 230 Rowe Street Wheeler, OR 97147 1890 Waite Rd. North Bend, OR 97459 1833 Fillmore Street San Francisco, CA 94115

Service Address  1000 3rd Street Tillamook, OR 97141 820 N. Plankinton Milwaukee, WI 53203 1381 University Healdsburg, CA 95448 712 Jay Street Fossil, OR 97830 1801 Nicollet Ave. Minneapolis, MN 55403 1995 Third St. Baker City, OR 97814 3670 Stone Way N. Seattle, WA 98103 530 NW 27th Street Corvallis, OR 97330 445 Centennial Ave Butte, MT 59701 107  Commercial Street, Mashpee, MA 02649 1530 Saint Clair Ave. Cleveland, OH 44114 1055 Main Street Springfield, MA 01103 805 Central Ave. Cincinnati, OH 45202 5320 North Shepherd Houston, TX 77091 150 Beavercreek Road Oregon City, OR 97045 820 Exchange St., Astornia, OR 97103 2158 Exchange Street Ste 304 Astoria, OR 97103 19 Myrtle St., Medford, OR 97504 1021 West 5th Ave. Gary, Indiana 46402 1057 12th Ave. Longview, WA 98632‐2509 375 NW Beaver St. Suite 100 Prineville, OR 97754 14 NW Kearney Avenue Bend, OR 97701 620 Ranch Rd. Reedsport, OR 97467 412 Telephone Rd. Houston, TX 77023 3820 Superior Ave. Ste 214 Cleveland, OH 44114 733 W. Henry Street Indianapolis, IN 46225 715 SW 4th St. Madras, OR 97741 3355 S. 120th Place Tukwila, WA 98168 3617 S. Pacific Hwy. Medford, OR 97501 51600 Huntington Rd. La Pine, OR 97739 225 West Olive Street, Rm 110, Newport, OR 97365 269 Union Street, Lynn, MA 01901 1590 Moffett Street Salinas, CA 93905 409 NE Greenwood Ave. Bend, OR 97701  049 SW Porter Street Portland, OR 97201 3569 Ridge Road, Cleveland, OH 44102 3720 SW 141st Ave Ste 100 Beaverton, OR 97006 3930 SE Division Street, Portland, OR 97202 849 Pacific Ave. Hood River, OR 97031 750 16th Street Arcata, CA 95521 530 Center Salem, OR 97301 1132 SW 13th Avenue Portland, OR 97205 2163 College Way Forest Grove, OR 97116 33 Encina Ave. Ste 103 Palo Alto, CA 94301 425 20th Ave. S minneapolis, MN 55454 11295 B Ave. Auburn, CA 95603 701 Ocean Drive, Santa Cruz, CA 95060 230 Rowe Street Wheeler, OR 97147 1890 Waite Rd. North Bend, OR 97459 1833 Fillmore Street San Francisco, CA 94115

End  Circuit  Location cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud cloud