RDATS Amend 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY AFFTC/PKEE CODE FA9302 7. ADMINISTERED BY (If other than Item 6) CODE

DIRECTORATE OF CONTRACTING

5 SOUTH WOLFE AVE, BLDG 2800

EDWARDS AFB CA 93524-1185

ALBERT J. YEH 661-277-8658

albert.yeh@edwards.af.mil

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

FA9302-10-R-0005

X 9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning 0 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 MODIFICATION OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(X )

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: ( ) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

RDATS

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print). 16A. NAME AND TITLE OF SIGNER (Type or print)

15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.12.0 FAR (48 CFR) 53.243 Created 24 Jun 2010 3:59 PM

SCHEDULE

FA9302-10-R-0005 0001

The purpose of this amendment is to:

A) Attach updated Edge Requirement Specifications. The configurations (A-D) have been updated to match the Excel Pricing Worksheet.

B) Include Questions and Answers from various interested offerors that provide clarifications to the RFP.

QUESTIONS AND ANSWERS:

Question #1: Is it Government's intent that a single chassis box must be capable of supporting all requirements with the addition of appropriate modules (or interface cards), or can requirement be satisfied with more than one chassis? The Specifications document implies a single chassis must be provided, but the Exhibit B table implies multiple chassis (of same type) can be bid. We believe we can meet the system requirements through use of 2 separate boxes: an IP based router with SONET/ATM/Ethernet ports, and a TM (circuit emulation) device to convert serial traffic to IP. Will a 2 box solution (different chassis) be technically acceptable?

Answer #1: In some cases two chassis are needed to meet the port densities described in Para 13, however the chassis should be the same. Furthermore, the solution sought will do TM over ATM. The above describes a solution dong TM over IP, then IP over ATM using dissimilar chassis.

Question #2: Specifications, Para 9: Does the multiplexor have to support the capability to connect a TM port to an ATM port? If yes, what are the ATM port requirements?

Answer #2: A TM port will not connect directly to an ATM port.

Question #3: Item 1 of the Memorandum states that the new multiplexers will connect to the backbone switch via OC3 or OC12 optical connections. Also item 7 pg 2 of the Edge Requirements Specifications lists OC3 and OC12 as requirements. The Pricing tab, however, does not have a location to price OC12.

Are both OC3 and OC12 capabilities a requirement that must be supported by the vendor's proposed offering?

Answer #3: OC3 is an absolute requirement, OC12 is optional.

Question #4: What are the physical connectivity, protocol and any other relevant details pertaining to the Telemetry requirement item 9 on page 3 of the Edge Requirements Specifications? The data rate requirement of 1K to 30Mbps is quite a large range depending on the connectivity and protocol used. Are these data rates to be supported by a single module for the various speeds and feeds?

Answer #4: The physical connector are two BNC ports, one data and one clock, at 75 Ohms. These are TTL ports.

Question #5: As the highest requested output speed is OC-12 (622Mbps), what is the justification for requiring that the multiplexor backplane support 2.5 Gigabit throughput?

Answer #5: What we want is a non blocking backplane.

Question #6: The manufacturer of "TW400" equipment, Terawave Communications, appears to be defunct. How can interoperability be determined with the TM Mux/Demux interface?

Answer #6: The equipment is available via third party resellers. If the offerors chooses to obtain the equipment the expense will not be reimbursed by the Government.

Question #7: What is the traffic format for the TM Mux/Demux interface? Is it TMoIP packets that are received and adapted into the ATM network or is it raw telemetry data that is encapsulated into TMoIP payloads and then adapted into the ATM network?

Answer #7: It's TM over ATM. We are not looking for TMoIP, but if the unit can do both that is acceptable. A PCM stream segmentation and reassembly (SAR'd) to ATM cells.

Question #8: What is the messaging format for the TM interface to Ethernet interface for bi-directional provisioning?

Answer #8: TM to Ethernet is not required. TM to ATM is.

Question #9: Is the reference for SONET only for transport of ATM traffic or is there a requirement for

SONET?

Answer #9: Yes. We are using ATM over SONET.

Question #10: For the configurations with 2 OC-3 interfaces, are these both operational or one a protection or redundancy interface? Same with the chassis containing 4 OC-3 interfaces.

Answer #10: Both optical port should be independently operational

Question #11: The specification talks of 2 and 4 OC-3 interfaces while the Excel pricing workbook lists 1 and 2 OC-3 interfaces. Which is correct?

Answer #11: The Excel sheet is describing 1 or 2 per chassis. There is a typo and in the Edge requirements specifications attachment. The most updated one is attached.

Question #12: There are no rates specified for the ATM interfaces. Are they all OC-3c single and multi-mode? Is OC-12c required?

Answer #12: The ATM must be OC-3 (155Mbps). Multi-mode and Single-mode optical ports should be supported. OC-12 is optional.

Question #13: Are network diagrams or details on how the network topology is today and if there are changes or plans to engineer for IP or other next generation services available?

Answer #13: No. The core is an ATM switched network.

Question #14: Please define/describe interface requirements for "telemetry"

Answer #14: These are two BNC connectors (75 Ohms) coaxial. One for data and one for clock.

Question #15: Regarding the Telemetry Modules in the various MUX configurations (RDATS Exhibit B), and using Year 1 MUX configuration A spreadsheet as an example, the solicitation says "Telemetry should support 16 receive and 16 transmit ports". Does this mean we should quote a chassis with 16 simultaneous transmit and receive ports (total of 32 ports that can operate at the same time), or a chassis with a total of 16 ports that can be configured independently as either transmit or receive ports?

Answer #15: The chassis should support 16 ports that can be set independently as transmit or receive

Question #16: Please define/describe interface requirements for "telemetry"

Answer #16: These are two BNC connectors (75 Ohms) coaxial. One for data and one for clock.

Question #17: What are the page limits/requirements for the bid submission document?

Answer #17: For the technical proposal, there is a 35 page limit.

Question #18: How many bid copies are required and what format are bids to be submitted?

Answer #18: For hard copies, two (2) proposals are required. Acceptable formats are Microsoft Office 2003 or later and Adobe PDF for digital proposals.

Edge Requirements Specifications 412 RANS RDATS Edge Replacement

23 June 2010

412 RANS is replacing the ATM multiplexer used on the Range’s test and evaluation data transport system. The new multiplexer will be installed at varied sites and connect to the Range T&E transport core (ATM backbone) via an OC3 or OC12 optical (multimode or single mode fiber) links. The range is looking for a modular and scalable solution which is compatible with existing ATM multiplexors. The new ATM multiplexer must be able to transport telemetry, TDM (DS1, T1), 10/100 Fast Ethernet (100BASE-TX), and Serial data. Specifications below are inclusive of requirements and optional features.

Specifications are as follows:

1. Chassis Power Multiplexor shall support both AC and DC powers sources

1. 120 VAC, 60 Hz power supplies

2. 48 VDC power supplies

Multiplexor shall support redundant (dual) power supplies

1. Redundant power supplies shall be hot swappable

2. Chassis Controller modules Multiplexor control modules shall support unit configuration back up Multiplexor control modules shall support unit configuration restore Multiplexor shall support redundant control modules Multiplexor shall support hot swappable control modules

3. Chassis Multiplexor shall support remote in-band or out-of-band (Ethernet) control capability

Multiplexor shall support remote provisioning (ATM connections, bandwidth, QoS, loopbacks, etc)

Multiplexor shall support remote port status (SONET, ATM cells TX and RX, TDM, Ethernet)

1. Statistics, counters Multiplexor shall be able to get health and status for all ports

1. Alarms, traps, logs Multiplexor shall be able to get health and status for power source

1. Alarms, traps, logs Multiplexor shall be able to password protect unit Multiplexor shall be able to create multiple user accounts with different access levels Multiplexor shall support different levels of access (administration, read only, etc.)

Multiplexor shall support SNMP protocol

1. Traps notification and logging Multiplexor shall support SYSLOG

Multiplexor shall support RADIUS authentication

4. Chassis Multiplexor shall support a modular design Multiplexor shall support a non-blocking backplane

1. Backplane capacity shall support all combinations of interface configurations

Multiplexor shall be able to build (any combination of port configuration) to satisfy customer requirements

Multiplexor backplane shall support at 2.5 Gigabit throughput Chassis dimensions shall fit into a 19” rack

5. Chassis Multiplexor availability Multiplexor shall support 100,000 hours MTBF, threshold 200,000 hours MTBF is objective Multiplexor shall support 2 hours MTTR, threshold 1 hour MTTR is objective

6. Chassis Multiplexor life expectancy shall be minimum 5 years Inclusive of modules and chassis Option for extended warranty and support during life of multiplexor plus additional two years after end-of-sale announcement

7. Chassis Multiplexor warranty and support Vender shall provide initial one year warranty and support for all components

1. Maximum 10 to 20 day turn-around on RMA parts. Shipping to vender at customer expense, shipping to customer at vender expense

2. Telephone technical support minimum 8 hours a day 5 days a week

3. Correction of software errors (bugs)

4. Access to software upgrades and patches

Vender shall offer extended warranty and support options after initial one year warranty is expired

1. RMA turn-around options; 24 hours to 2 days, 5 to 10 days, 10 to 20 days. Shipping to vender at customer expense, shipping to customer at vender expense

2. Telephone technical support options; 25 hours 7 days a week, 12 hours 7 days a week, 8 hours 5 days a week

3. Corrective actions on software errors

4. Access to software upgrades and patches

8. Module – Transmit & Receive SONET Multiplexor shall support OC3c optical ports Multiplexor shall support OC12c

Multiplexor shall support single-mode and multi-mode OC3c and OC12c

Multiplexor shall support single-mode intermediate range (15-20Km) and long range (60-80Km) optical ports

Multiplexor shall support loopback provisioning on SONET interface Multiplexor shall support minimum of (2) SONET ports Timing

1. Multiplexor shall be able to recover timing from SONET interface

9. Module – ATM Transmit & Receive Multiplexor shall support Permanent Virtual Connection Channel

(PVCC) connections

1. Minimum 256 per VPI

Multiplexor shall support Permanent Virtual Connection Path (PVCP) connections

1. Minimum 64 Quality of Service (QoS)

1. Multiplexor shall support constant bit rate (CBR), and unspecified bit rate (UBR) provisioning

2. Multiplexor shall support provisioning of cell delay variation timing (CDVT) and peak cell rate (PCR) or be auto-adaptive to data rate.

3. Multiplexor shall support provisioning of cell loss priority

(CLP)

4. Multiplexor shall support AAL1, AAL5 adaption layers

5. Multiplexor shall support early packet discard

6. Multiplexor shall support ATM traffic policing

7. Multiplexor shall support ATM traffic shaping

ATM Cell Emulation Service (CES)

1. Multiplexor shall be able to provision structured and unstructured ATM circuits

10. Telemetry (TM) Mux/Demux Multiplexor shall support TTL input/output Multiplexor shall support BNC connectors Multiplexor shall support Data and Clock BNC interface Multiplexor shall support ATM connection provisioning

1. TM interface to ATM interface, bi-directional

2. Multiplexor shall support CBR, AAL1 for TM

Multiplexor shall support of TM over IP

1. RCC Standard 218-07

2. TM interface to Ethernet interface bi-directional provisioning

Multiplexor shall support data rates from 1Kbps to 30 Mbps Multiplexor shall be able to auto sense received bit rates

Multiplexor shall support maximum latency requirements (< 50msec for every bit rate)

Multiplexor shall support interoperability with existing Range telemetry equipment

1. Terawave TW400 Multiplexor shall be able to maintain zero errors during BER tests

1. Duration: 48 hours Multiplexor shall support minimum of (8) bi-directional telemetry ports

11. Dual T1 I/O (Channelized & Unchannelized) TDM (DS1/T1) Multiplexor shall support T1 framing ESF or SF(D4) Multiplexor shall support T1 line code B8ZS or AMI Multiplexor shall support ATM connection provisioning

1. T1 interface to ATM interface, bi-directional

2. Multiplexor shall support CBR, AAL1 for TDM

3. ATM Cell Emulation Services (CES)

Multiplexor shall support TDM over IP

1. TDM interface to Ethernet interface bi-directional provisioning Multiplexor shall be able to chose between full T1 or partial T1 Multiplexor shall be able chose between unstructured or structured T1 Multiplexor shall be able to provision Line, Local, and Payload loopbacks on T1 interfaces Multiplexor shall support RJ48 connectors (standard T1 pin-out) Multiplexor shall support minimum (6) T1 ports Multiplexor shall support interoperability with Range existing TDM equipment

1. Terawave TW400

12. Two Channel Ethernet Module Multiplexor shall support 10/100 BASE-TX Ethernet Multiplexor shall support 1Gb Ethernet Multiplexor shall support minimum (4) Ethernet ports Multiplexor shall support RJ45 connectors (standard Ethernet pin-out) Multiplexor shall support ATM connection provisioning

1. Ethernet interface to ATM interface, bi-directional

2. Multiplexor shall support UBR ,CBR, AAL1, AAL5

3. RFC 1483 or RFC 2684

Multiplexor shall support interoperability with Range existing Ethernet equipment

1. Terawave TW400

13. (Optional) Serial data Module Multiplexor shall support RS-232 and RS-422

Multiplexor shall support data ranges from 2.4Kbps to 128Kbps Multiplexor shall support Asynchronous or Synchronous Multiplexor shall support ATM connection provisioning

1. Serial interface to ATM interface, bi-directional

2. Multiplexor shall support CBR, AAL1

Multiplexor shall support Serial data over IP

1. Serial interface to Ethernet interface bi-directional provisioning Multiplexor shall support interoperability with Range existing Serial equipment Multiplexor shall support minimum (4) Serial ports

14. Multiplexor shall support the following configuration capabilities. Number of chassis required may vary per interface density on modules and module density per chassis.

The following chassis configurations define the majority of customer sites. The Range needs to have the capability of adding to or deleting from any of these configurations with any interface module (TM, T1, Ethernet, OC3, etc.).

MUX configuration A

1. 16 telemetry interfaces

2. 4 Ethernet interfaces

3. 4 T1 interfaces

4. 2 OC3 interfaces

MUX configuration B

1. 8 telemetry interfaces

2. 4 Ethernet interfaces

3. 4 T1 interfaces

4. 2 OC3 interfaces

MUX configuration C

1. 4 telemetry interfaces

2. 2 Ethernet interfaces

3. 4 T1 interfaces

4. 2 OC3 interfaces

MUX configuration D

1. 2 telemetry interfaces

2. 1 Ethernet interfaces

3. 2 T1 interfaces

4. 1 OC3 interfaces

Each customer site requires different configurations of the chassis. Some sites need more telemetry capabilities than other sites. Some sites need T1 and Ethernet capabilities and no telemetry capabilities. The Range is looking for the capability of configuring each chassis to fulfill the site requirement.

15. Multiplexor shall be provided with support technical documentation User manuals

1. Installation

2. Configuration

3. Specifications

Training manuals

Contractor shall provide maintenance/repair support along with software/firmware upgrades as needed.