Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JANUARY 31, 2007 FBO #1892
MODIFICATION

D -- Emergency Call Management System

Notice Date
1/29/2007
 
Notice Type
Modification
 
NAICS
517310 — Telecommunications Resellers
 
Contracting Office
Department of Homeland Security, Federal Emergency Management Agency, Response & IT Branch, 500 C Street, S.W. Room 350, Washington, DC, 20472, UNITED STATES
 
ZIP Code
20472
 
Solicitation Number
W381044Y
 
Response Due
2/2/2007
 
Archive Date
2/17/2007
 
Point of Contact
Brooke Bernold, Contract Specialist, Phone 202-646-2932, Fax 202-646-3318,
 
E-Mail Address
brooke.bernold@associates.dhs.gov
 
Small Business Set-Aside
Total Small Business
 
Description
QUESTIONS AND ANSWERS FOR W381044Y The purpose of this amendment is to post the questions received and answers for the Combined Synopsis Solicitation W381044Y. Responses to this posting must be made in writing and submitted to Brooke Bernold by e-mail, Brooke.Bernold@associates.dhs.gov, no later than 4:00PM E.S.T. on Friday, February 2, 2007. Q1. Please provide the following information for each of the locations where a PBX is installed: a. Design Center: (1) Type of PBX: Nortel Remote Intelligent Peripheral Equipment (IPE) Module: (2) DID Range(s): (3) Number of Extensions: 110 (4) Number of Digits in Dialing Plan: b. Crystal City: (1) Type of PBX: Nortel Remote IPE Module (2) DID Range(s): (3) Number of Extensions: 260 (4) Number of Digits in Dialing Plan: c. Patriots Plaza: (1) Type of PBX: Nortel Remote IPE Module (2) DID Range(s): (3) Number of Extensions: 290 (4) Number of Digits in Dialing Plan: d. 999 E St. NW: (1) Type of PBX: Nortel Remote IPE Module (2) DID Range(s): (3) Number of Extensions: 100 (4) Number of Digits in Dialing Plan: e. FEMA Headquarters: (1) Type of PBX: Nortel Meridian M1 (2) DID Range(s): 1140 ? 1146 2400 ? 2499 7590 -- 7599 1271 ? 1279 2501 ? 4399 7650 -- 7699 1342 ? 1358 4500 ? 4699 7900 -- 7949 1375 ? 1391 5780 ? 5799 7970 -- 7979 1640 ? 1654 7040 ? 7099 7390 ? 7399 1901 ? 1915 8240 ? 8249 8192 -- 8196 1955 --1960 1968 ? 1969 8175 -- 8176 1045 -- 1047 1963 ? 1966 8130 -- 8133 8169 -- 8172 8266 ? 8269 8137-- 8143 8262 -- 8263 8272 -- 8273 8272-- 8273 8148 ? 8150 1894 ? 1898 1304 -- 1308 1072 1107 1110 1119 1120 8145 1133 1165 1179 1216 1219 1295 1664 1758 1759 1765 1766 1823 1860 1881 1888 1891 1892 1940 1950 1953 8152 8154 8161 8178 8180 8199 8278 (3) Number of Extensions: 1980 (currently) (4) Number of Digits in Dialing Plan: 4 Q2. For clarification purposes, the requirement is for every 911 call to first ring a phone at the corresponding Security Office at each of the five locations. It is then the decision of the Security Personnel to either handle the call or transfer the calling party to the local 911 Center (Public Safety Answering Point). Is this a true assessment? Typically we deliver the 911 call to security and the local PSAP simultaneously since time is of the essence. If not, please explain desired 911 Call Routing: A2. A 911 call from a remote location should be routed to its corresponding Security Office. Those Security Personnel will make the decision to handle the call or allow the call to proceed to the local PSAP. The call should also be simultaneously routed to the HQ Lobby Security Desk in order for the Security Personnel to monitor and record the calls and notify appropriate HQ personnel. 911 calls at HQ will be routed to the HQ Lobby Security Desk where Security Personnel will decide to handle the call or allow the call to proceed to the local PSAP. Q3. Does each of the five locations have National Standard ISDN PRI circuits available for 911 call routing/delivery? A3. All call processing is done by the HQ PBX and calls delivered/received to/from the remote locations via data T1?s. All calls in and out of HQ PBX from Public Switched Network (PSN) are via ISDN PRI circuits. Q4. Who is your servicing telco that provides PS/ALI services? A4. Verizon Q5. Other than the Security Departments, are there any other agencies at any location that require real-time notification (via computer terminal) of 911 call events? A5. No Q6. Are the five locations networked together for internal dialing purposes? If so, explain network connectivity between PBX?s. A6.It is not a data network, the remote IPE modules are connected back to the HQ PBX via 3 data T1?s from each site. Q7. On a 911 call set-up, can the originating station number be passed from one PBX to another (i.e. routing 911 calls to one main PBX for call handling)? A7. There is only 1 PBX ? at HQ. The sites are tied in with remote modules. Q8. Model and version is the FEMA HQ PBX? A8. Nortel Meridian M1 running Succession 4.5. Q9.Is Virginia site is serviced via the same 911 tandem as the Washington, DC sites? A9. Yes, the remote module is tied to HQ PBX via 3 data T1?s. Q10. Is there an incumbent of this procurement opportunity? If so, I would greatly appreciate the following: contractors name, contract number, date, expiration date and value. A10. No Q11. Is there a required headcount number for this project? A11. 3200 Q12. Is there a requirement for the work to be performed at a FEMA building location, or can it be performed at another site within the United States? A12. Yes Q13. What are the manufacturers of the PBXs/Telephone systems serving each of the five locations noted in the solicitations? A13. See answer for Q1. Q14. If any of the telephone systems serving the five noted locations also support remote site, please identify the number and locations of the remote sites. A14. N/A Q15. Are the telephone systems serving the five noted sites networked together? If so, please describe the network configuration and the network infrastructure. A15. See answer to Q6. Q16. Are any of the telephone instruments which are to be supported by the Emergency Call Management System VoIP instruments? If so, at which site are they located and how many at each site? A16. No Q16.Please identify the Public Service Answering Points (PSAPs) serving each of the five noted locations. Are these PSAPs networked? If so, please provide a description of the network configuration. A16. Information provided upon award of contract. Q17. Will FEMA answer the E911 calls using their own staff or do they just want to be able to monitor and audit the incoming calls. A17. See answer to Q2. PBX issues A)PBX Vendor/Dealer Supplier: Nortel Federal Systems ?COAM Contact Name: Customer Owned and Maintained Tel Number: 18004NORTEL (18004667835) B) Is it stand-alone or networked? Standalone main PBX tied to Remote Modules via T1?s. C) ANI/Caller ID pushed out to network? (ANI turned on?) Yes D) Standard Dialing Plan (4, 5 or 6 digits)? 4 digits exclusive of access codes and private network location codes. Access codes = 6 or 9, loc codes are 3 digit. PSN calls are 9 1 npa nxx xxxx. Private Access Network (PAN) calls are 6 loc xxx E) Automatic Route Select in place and functioning? Yes Is it partitioned? No F) Number of Station Lines Number with DID outgoing capable: appr. 2800 Number non-DID outgoing capable: appr. 2200 G) Presently equipped with ISDN PRI? Yes Network Provider H) Dial-tone provider? Verizon I) Network Diagram if available? N/A 1. PBX Clarifications a. Please identify the PBX?s listed at each location identified in the above solicitation. See answer to Q1. b. Please identify the software release level of each PBX. See answer to Q8. c. Please identify if any, the connectivity of PBX?s between each location. See answer to Q1. d. Please identify the estimated number of lines to be loaded into the OTM database. 3200 e. Please identify if any, the circuits that are in place to deliver emergency calls to the local PSAP or tandem. See Q3 above. f. Please identify the number of line appearances that are associated to the current call takers. Differs at each location min 2 no max. g. Please identify if the lines referenced above are MADN, ACD, AUL?s, or Hot D?s. MADN 2. Network Clarifications a. Please identify the existing infrastructure located at each location. 100baseT b. Please identify available connectivity mediums between each location. See answer to Q6. c. Please identify equipment room space and power availability. Switch room has dedicated HVAC, well lit, ample UPS power 110-220V. d. Please identify the proposed location of the OTM database. HQ switch room located on Mezzanine Level Room M19 e. Please identify the proposed location of the Emergency Call Management System (ECMS) back room equipment. See answer to 2d above. f. Please identify if the OTM and the ECMS will not be located in the same location, is Ethernet connectivity between the locations available. Yes g. Please identify if Ethernet connectivity between the proposed call taker positions and the ECMS back room equipment is available. It is available at the HQ location. A direct data connection or VPN connectivity can be provided to the remote sites. Current Call Processing Clarifications h. Please identify the current process used to handle emergency calls. Calls are routed to the HQ Lobby Security Post and answered by the Security Guards on duty. Local personnel (nurse, EMT etc) if available are dispatched and/or local 911 centers may be called. Security personnel at remote sites are notified to coordinate access for first responders if required. Currently calls from remote sites may not be identified as coming from those locations because they are all HQ numbers. i. Please identify how emergency calls are currently routed that originates from each location? See 3a above j. Please identify if any, all 3rd party applications utilized in the processing of emergency calls at each location. N/A k. If 3rd party products are currently used today, please identify if these products are stand alone at each location or networked with a shared database of information. N/A l. Please identify if radio is utilized in the process of handling emergency calls. N/A m. If radio is utilized in the process, please identify the radio system in place and if possible total nets/trunks/frequencies in use. N/A n. Please identify the device used for archival recording of emergency calls. N/A o. Please identify if any agreements are currently in place with the local serving PSAP?s for each location. N/A p. Please identify the local PSAP for each location. See Q16 q. Please identify if ALI updates for PBX data is required by the local PSAP. Information provided after contract award. r. Please identify if each location will serve as a backup to the other in the event all call takers are busy or unavailable. Not a requirement. 3. Call Taker Clarifications a. Please identify the number of call takers to be present at each location. Varies by location and time of day. This is the local Security Guard force. b. Please identify if any power and or space restrictions exist at each proposed call taker location. There are none known at this time. 4. Database Clarifications a. Please identify the current medium the data that will be used to populate the OTM is stored in. i.e. Excel, Access, Word. OTM integrates with the PBX to download data. b. Please identify the data export abilities of the OTM. i.e. NENA compliant, .xml, .txt. The OTM system integrates with the PBX and downloads data. c. Please identify the current medium the data that is to be used to populate the personnel database is stored in. i.e. Excel, Access, Word. The OTM is integrated and downloads the data. d. Please identify any on site data network security restrictions in place. Information is to be provided after contract award. e. Please identify database update requirements. Database is updated automatically by the OTM. NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (29-JAN-2007); 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.fbo.gov/spg/DHS/FEMA/ORPD/W381044Y/listing.html)
 
Place of Performance
Address: Department of Homeland Security Federal Emergency Management Agency 500 C Street, S.W. Washington, DC,
Zip Code: 20472
Country: UNITED STATES
 
Record
SN01221674-F 20070131/070129222545 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  © 1994-2020, Loren Data Corp.