Questions pertaining to RFP 2 are included on this page. Please submit your questions and inquiries to vendorinfo [at] oregonhealthnet [dot] org.

Q:
It seems somewhat unclear as to what the due date is for responses. Can you clarify?
A:
Responses to OHN RFP #2 are due on or before 4 p.m. July 3, 2009.

Q:
The Network Access and Transport Specification states in #16 "Proposers may also elect to place one or more OHN "leaf nodes" at strategic points..." Do you have a list of the make/model of leaf node devices approved by OHN?
A:
We're envisioning a small appliance (such as a minimal Cisco router or other embedded system) which would be placed on the customer network. OHN has a prototype based on a Linux build, and Easystreet (our NOC provider) is currently working up a prototype based on a Cisco router platform.  We can't give you any more specifics until the design is formalized, other than to say that the NOC and other OHN sites would need controlled access to the leaf node, and it would under some circumstances actively create traffic to measure, as well as the standard passive measurement & statistical analysis.

Q:
The RFP states (page 12, 2nd half of top paragraph): "For many locations, OHN anticipates that more than one service provider will be needed to connect the end-user location with an OHN-specified data exchange location. In order to provide the requested transport capacity at the specified quality of service levels between each end-user location and specified exchange location, OHN requests that a single service provider bid the access and transport service as the primary provider that assumes overall responsibility for the entire link through appropriate sub-contracting arrangements."

Can we bid the following six locations in conjunction with the necessary provider to deliver the data into the NWAX facility...with neither party assuming overall responsibility for the entire link (i.e. a true meet-point arrangement)?

A:
When two vendors are involved on the link from any end-user site to NWAX, one of the vendors should be prime contractor with responsibility for end-to-end quality meeting the quality of service specifications. Either vendor could be prime contractor and the other sub-contractor, but the prime contractor will be legally and financially responsible for providing the end-to-end service.

Q:
Are you seeking either a Layer 2 only, or a Layer 3 only, solution?

A:
OHN is Ethernet based, and much like today’s Internet but with improved routing, improved quality and security considerations.  Each Local Service Provider (LSP) will have a layer 3 (BGP4) connection with other participating OHN Local Service Providers via a Layer2 exchange such as NWAX, Data Center West, and Quantum.  In this sense OHN is a layer 3 phenomenon as there is not one single Internet Autonomous System number serving the OHN as a whole.

With that said, Local Service Providers could also pool their resources, such that one provider could become the LSP of record and subcontract layer2 physical connectivity in region to one or more additional providers.  We anticipate that each OHN customer would have a premises router to segment the customer network from the LSP network.

Q:
What is the maximum installation interval permitted?

A:
We have not specified that parameter and will accept reasonable proposals.

Q:
What are the (proposed) addresses for Data Center West in Medford and Quantum Communications in Redmond?

A:
The Data Center West address is 739 Welch St., Medford OR, 97501. The Quantum Communications address is 285 E. Salmon Ave. Redmond OR 97756.

Q:
Please describe the contracting/ transaction process between the carrier and the end-user and/or OHN?  Who initiates the transaction?  Are the end-user organizations required to complete an agreement with the successful carrier?

A:
Once a vendor is selected, the vendor will initiate a contract with the OHN participant (end user), which will be the customer of record. However, contracts must also be approved by OHN and by the Universal Service Administrative Company (USAC) before they become effective.

Q:
Page 14 #5:  Please explain further “the data transport provider will provide an Internet data connection for other Internet data packets addressed to or from the OHN end-user location that cannot be delivered or accepted for delivery at the Portland or other Oregon Internet exchange sites”.  Can you give an example?

A:
In addition to connectivity at NWAX and regional exchanges, the selected vendors will provide access to the public Internet. Data traffic from an OHN participant site that cannot be handed off at the exchanges will delivered to the specified IP address via the public Internet.

Q:
Please amplify the evaluation criteria for “route diversity” on page 16, Evaluation Criteria.  Where do you want route diversity to be accomplished--- physically and logically?

A:
Route diversity is relevant any place there could be a single point of failure.  In particular, the local loop is often the lowest quality portion of any network, so some redundancy in this arena is helpful, such as independent physical routes or a self-healing fiber ring.

Q:
Considering many organizations consider Friday July 3rd a holiday, can you please confirm the deadline?

A:
The deadline for submission of responses for RFP #2 is Friday July 3rd at 4 pm.  The OAHHS offices will be open from 9 am - 4 pm on that day.

<!--[endif]-->