Loren Data's SAM Daily™

FBO DAILY ISSUE OF JANUARY 31, 2005 FBO #1162
MODIFICATION

70 -- DODIIS VOIP EQUIPMENT

Notice Date

1/29/2005
 

Notice Type

Modification
 

NAICS

334210 — Telephone Apparatus Manufacturing
 

Contracting Office

Other Defense Agencies, Defense Intelligence Agency, Virginia Contracting Activity (ZD50), 200 MacDill Boulevard Post Office Box 46563, Washington, DC, 20035-6563
 

ZIP Code

20035-6563
 

Solicitation Number

HHM402-05-R-0007
 

Response Due

2/8/2005
 

Archive Date

2/23/2005
 

Point of Contact

Lynda Cave, Contract Specialist, Phone 202-231-8464, Fax 202-231-2831,
 

E-Mail Address

brunilda.cave@dia.mil
 

Description

Potential offerors are responsible for acknowledging all amendments to this combined synopsis/solicitation. The purpose of this amendment is to incorporate Appendix A, DODIIS VOIP Technical Requirements and Appendix B, VOIP Cost Table as follows: APPENDIX A – DODIIS VOIP TECHNICAL REQUIREMENTS: 1.1 Voice system must utilize VoIP technology and VoIP phones 1.2. The VoIP System must provide internal gateway functionality so DoDIIS users can place secure calls to other Intelligence Community users 1.2.1 VoIP system must support T-1 trunking 1.2.2 VoIP system must support two T-1s trunks from the gateway to the traditional TDM PBX 1.3. The VoIP system must provide for calls to be placed at the security level of PL-3 as outlined in 5.5 1.4 VoIP system must tolerate delays that might occur globally between phones and PBX (phone boot/call signalling). 1.5. The VoIP system must interoperate ( i.e. place phone to phone software based encrypted secure calls, connect and maintain without dropping calls while utlizing standard PBX features as listed in 1.15) with existing 1150 VoIP CISCO phones fielded throughout CENTCOM 1.5.1 VoIP system must interoperate ( i.e. place phone to phone software based encrypted secure calls, connect and maintain without dropping calls while utlizing standard PBX features as listed in 1.15) with existing 80 VoIP CISCO phones deployed with C-JWICS/JMICS tatical mobile units 1.6. A 7-digit Dial-Plan must be used to provide for consistency, legacy interoperability, and expansion throughout the DoDIIS community. 1.7.1 VoIP system must be capable of operating over low bandwidth (64 kbps) and/or high latency links (600ms) 1.8. VoIP system must utilize the JWICS wide area network (WAN) for transport between sites, commands, and network regions. 1.8.1 VoIP system must allow for VoIP Traffic to be routed into and out-of specific ATM VCs 1.9. VoIP system must utilize appropriate local area network (LAN) for transport within sites. 1.9.1 The VoIP system must allow VoIP traffic to be routed into and out of specific VLAN 1.9.1.1 The VoIP system must provide a method for phones to operate on specific VLANS (with or without PCs attached) 1.10. The system must provide voice mail for all users. 1.10.1 The VoIP System must provide the capability to turn-on and turn-off (set and clear) Message Waiting Indicators (MWI) per station set. 1.10.2 The voice mail system must adhere to security requirements in 5.5 1.11. Calls which encounter a busy/no-answer state must be forwarded to voice mail or coverage. 1.12. The voice mail or coverage portion of the VoIP system must provide zero-out capability for all users. 1.13. VoIP system must utilize unique IP address space from end-to-end. 1.14. VoIP system must support the use of DHCP or Static addressing based on the requirements of the site. 1.15. VoIP system must, as a minimum, provide traditional PBX capabilities 1.15.1 VoIP system must provide call forwarding capability (VoIP, other trunk) 1.15.1.1 The VoIP system must provide Call Forward-All feature. 1.15.1.2 The VoIP system must provide Call Forward No-Answer feature. 1.15.1.3 The VoIP system must provide Call Forward Busy feature. 1.15.2 System must implement call hold 1.15.3 System must implement call park 1.15.4 The VoIP system must provide Transfer feature. 1.15.5 The VoIP system must provide Call Pickup Group feature. 1.15.6 The VoIP system must provide Last Number Redial feature (LNR). 1.15.7 The VoIP system must provide Call Waiting feature (CW). 1.15.8 The VoIP system must provide (DTMF) Touch Tone Dialing. 1.15.9 The VoIP system must provide Do Not Disturb. 1.15.10 The VoIP system must provide System Speed Dial feature. 1.15.11 Users of the VoIP system must have the capability to dial 911 for emergency situations. 1.15.12 The VoIP system must provide Alternate Route Selection. 1.15.13 The VoIP system must provide Station Hunting. 1.15.14 The VoIP system must provide Feature Transparency across switches. 1.15.15 The VoIP system must provide Class-of-Restrictions (COR). 1.15.16 The VoIP system must provide Class-of-Service (COS). 1.15.17 The VoIP system must provide Trunk Groups. 1.16. The system must be upgradable to IPv6 within the timeframe of the DoD policy. 1.17 System must implement a signaling gateway (H.323, SIP, etc) 1.18 The VoIP phones must provide LDAP Directory integration, available to the user on the phone via visual screen 1.18.1 The VoIP phones must contain a color screen per phone endpoint 1.18.2 The IP phones must support open standards G.711 and G.729a audio compression 1.18.3 The VoIP phones must allow the user to disable the speakerphone 1.18.4 The VoIP phone must provide local power 1.18.4 The VoIP phone must support software based encryption 2.1. The system must be capable of being fully centrally administered and managed (not including physical management); however certain functions may be delegated to specific sites and/or commands. 2.1.1 The VoIP system must provide System Status Reports which include as a minimum, Out-of-Service Reports for stations and trunks, System Error Reports, System Failure Reports and Switch Database Dumps 2.1.2 The VoIP system must be capable of running Demand Diagnostics on Trunks, Stations and Circuit Packs. 2.1.3 The system must be capable of being stopped, started, and rebooted remotely 2.2. The VoIP system shall support an entirely web based Administrative User Interface secured through Secure HTTP (HTTPS). 2.3. Management views must be available at RSCs and local sites to support delegation and distributed management capabilities. 2.4. System use must be governed by policy which specifies allowed users and use cases; subject policy must address management, security, interoperability, and interface issues. 2.5. System must maintain backups of configurations. 2.5.1 System must allow for backup to removable media 2.5.2 System must allow for backup across network 2.6. System must maintain call detail records for all calls and must include storage and analysis capability (for how long? And report capability?). 2.6.1 The VoIP system must log Call Detail Records (CDR) for all station-to-station calls. 2.6.2 The VoIP system must log Call Detail Records (CDR) for all station-to-trunk calls. 2.6.3 The VoIP system must log Call Detail Records (CDR) for all trunk-to-station calls. 2.6.4 The VoIP system must log Call Detail Records (CDR) for all trunk-to-trunk calls. 3.1 VoIP system must leverage the resources provided at RSCs (personnel, bandwidth, data center resources, etc). 3.2 The VoIP system IP phones must be able to dial fielded DoDIIS H.323 (Tandberg) 100+ endpoints, and put the dial video system on hold, without dropping the call. 3.3 The system must permit H.323 video endpoints to be pointed at the IP PBX switch and make video calls to other H.323 video devices on the network. . 3.4 The contractor must provide 24 x 7 telephonic maintenance support for their proposed VoIP system 3.5 The contractor must provide annual maintenance for all equipment excluding IP phones 3.6 The contractor must provide specialized on-site maintenance support within 3 hours hours in the event telephonic support cannot solve the problem. 4.1 The VoIP system must provide a mean opinion score (MOS) of 4.0 for LAN completed calls – toll quality. 4.1.1 The LAN system must implement QoS mechanisms to eliminate or minimize packet loss, jitter and excessive queuing delay 4.2 The VoIP system must provide a mean opinion score (MOS) of 3.8 for WAN completed calls – near toll quality, minus delay factor for overseas calls. 4.3 IP phones must generate dial tone locally on the IP phone in order to conserve WAN bandwidth. 4.4 VoIP system must have controlled bandwidth impact, and must not be allowed to over-consume bandwidth, bandwidth limits must be allocated. 4.5. VoIP system must support concurrent calls by 8% of installed users (need to further investigate this requirement) in conjunction with availability requirement (stated below). 4.6. Availability – For routine use the VoIP system must provide four 9s of reliability. 4.6.1 The VoIP system must provide 99.9 percent availability over a 30-day period (Threshold) 4.6.2 The VoIP system must be resistant to worms, viruses and intrusions 4.7. Availability – During a National Emergency, the VoIP system must continue to provide an equivalent of four 9s (further investigate this) of reliability. 4.8. Availability – VoIP system must attempt to maximize reliability and redundancy, however, VoIP system must not provide backup voice communications for sites that have been isolated from the network due to primary and secondary link failure. 4.9. Availability- VoIP system shall be capable of failing over from one IP PBX to another IP PBX, across multiple IP subnets, without human intervention. This functionality must be supported between IP PBX’s over 100 miles apart. 4.9.1 IP phones must be able to register to multiple IP PBX’s concurrently. 4.10. The VoIP system must support conference calls, up to ten users and will support up-to 1% of installed users for this feature at any time. 4.10.1 The VoIP system must provide 3-party Conference feature. 4.10.2 The VoIP system must provide 6-party Conference feature. 4.11. VoIP system must scale to potential 60,000 total users 4.12. The VoIP system must continue to operate during general power failures. 4.13. VoIP system must be capable of implementing silence suppression. 4.14 VoIP system must block phone calls if adequate bandwidth is not available in the WAN. 4.15 The IP PBX must implement baterry-backed power adequate to allow the VoIP system to be shutdown "soft" 4.16 The IP PBXs and voice mail servers must provide one hour of uninterrupted power 4.17 The VoIP system must have power distribution for racks, monitor, keyboard, mouse tray, KVM controller, and keyboard mouse monitor switch for each RSC/Virtual RSC site 4.18 The VoIP system must be rack mountable using standard 19 inch rack enclosures to house IP PBXs, routers, gateways and voicemail servers 5.1. VoIP system must not connect with voice VoIP systems of lower classifications (i.e., Secret and Unclass). 5.2 The VoIP system must support phones which do not provide speaker-phone capability, or provides an acceptable (for security accreditation) alternative to disable a speaker phone capability. 5.3 The VoIP system must be accredited to operate on JWICS and within the appropriate DoDIIS community networking VoIP systems. 5.4 VoIP system must adhere to the security requirements necessary to NSTS. (PL-3) 5.5 VoIP system must meet PL-3 Auditing Requirements 5.5.1.1. The VoIP system must provide the capability to audit the actions of privileged users that meets the requirements for PL-3 operation. 5.5.1.1.1 The audit records must include logons and priviledged user actions, including the date and time of action, system locale, the entity and resources related to the action 5.5.1.2. The VoIP system must provide the capability to create unique logins (user and pwd) for each privileged administrator 5.5.1.2.1. The VoIP system must provide the capability to detect and record (log) attempts at unauthorized acesss (intrusions) and report these to the ISSO. 5.5.1.3 The VoIP system audit trail must be unchangeable 5.5.2 VoIP system must meet PL-3 Configuration and access requirements. 5.5.2.1. The VoIP system must provide the capability to authenticate both general and privileged users. 5.5.2.2. The VoIP system must allow the use of strong passwords (at least 8 characters and include numbers and special characters) 5.5.2.2.1 The VoIP system must require a password change after initial logon 5.5.2.3 The VoIP system must implement a screen lock function that will automatically be invoked after a 15 minute period of inactivity 5.5.2.4 VoIP system must support end-to-end [voip] software based encryption of calls from phone-to-phone 5.5.2.5 VoIP system must support end-to-end [voip] encryption of calls from phone-to-gateway (and vice-versa) 5.5.2.6 The VoIP system (PBX) must provide a pre-login banner which provide consent to monitoring and required DoD warning banners 5.5.2.7 The VoIP system must be resistant to worms, viruses and intrusions 5.6 The IP phones must display icons indicating the security mode during the call, telling the user whether the call is encrypted, authenticated, or both. 5.6.1 The voice encryption must adhere to the AES encryption standard. 5.7 The VoIP system must support both Manufacturer Installed Certificates and Locally Significant Certificates. All certificates must adhere to the X.509.v3 standard. 5.8 The VoIP system must use standards-based Transport Layer Security (TLS) to validate that no tampering has occurred to signaling packets during transmission. 5.9 The VoIP system must use SRTP to encrypt the media stream. Media encryption includes creating a media master key pair for the devices, delivering the keys to the devices, and securing the delivery of the keys while the keys are in transport. APPENDIX B – VOIP COST TABLE: Provide a table including the unit price and total cost for each line item as follows: 0001- INFRASTRUCTURE: 0001AA - VOIP Core Infrastructure for 30,000 users (6000 per RSC); 0001AB - VOIP Core Infrastructure Licensing for 30,000 users (6,000 per RSC); 0001AC - Failover Infrastructure for 30,000 users 0001AD - Failover Infrastructure Licensing for 30,000 users; 0001AE - Voice Mail design for 10,000; 0001AF - Voice Mail for 10,000 users (2,000 per RSC); 0002 – IP PHONES (2,000 each); 0003 – MAINTENANCE: 0003AA - Maintenance Equipment; 0003AB - Maintenance Cost for 2,000 IP Phones; 0003AC - 24X7 Telephonic Support; 0003AD - On-call Maintenance Support as required NOTE: THIS NOTICE WAS NOT POSTED TO WWW.FEDBIZOPPS.GOV ON THE DATE INDICATED IN THE NOTICE ITSELF (29-JAN-2005); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT fbo.support@gsa.gov REGARDING THIS ISSUE.
 

Web Link

Link to FedBizOpps document.
(http://www.eps.gov/spg/ODA/DIA/ZD50/HHM402-05-R-0007/listing.html)
 

Place of Performance

Address: Bolling Air Force Base, Washington DC

Zip Code: 20340

Country: USA
 

Record

SN00742600-F 20050131/050129212951 (fbodaily.com)
 

Source

FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)

---

| FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |