Loren Data's SAM Daily™

FBO DAILY ISSUE OF FEBRUARY 04, 2009 FBO #2627
DOCUMENT

59 -- Inter-RF Sub-System Interface (ISSI) Project 25 (P25) Infrastructure Equipment - FBO Notice in Word

Notice Date

2/2/2009
 

Notice Type

FBO Notice in Word
 

NAICS

334220 — Radio and Television Broadcasting and Wireless Communications Equipment Manufacturing
 

Contracting Office

Department of Commerce, National Oceanic and Atmospheric Administration (NOAA), Mountain Region Acquisition Division, 325 Broadway - MC3, Boulder, Colorado, 80305-3328
 

ZIP Code

80305-3328
 

Solicitation Number

NTIA-ISSI-P25
 

Archive Date

2/11/2009
 

Point of Contact

Mark Caban,, Phone: 303-497-6875, Mark Caban,, Phone: 303-497-6875
 

E-Mail Address

mark.caban@noaa.gov, mark.caban@noaa.gov
 

Small Business Set-Aside

N/A
 

Description

NOTICE: THIS IS A REQUEST FOR INFORMATION ONLY. The Institute for Telecommunication Sciences (ITS) on the behalf of National Institute of Standards and Technology/Office of Law Enforcement Standards (NIST/OLES) is conducting market research to determine sources for the following equipment. The anticipated North American Industry Classification system Code (NAICS) for this procurement is 334220 Radio and Television Broadcasting and wireless Communications Equipment Manufacturing with a size standard of 750 employees. The Government anticipates award of a contract in the 2nd or 3rd quarter of 2009. ISSI Based Project 25 Trunked Infrastructure 1. Project Overview The Institute for Telecommunication Sciences (ITS) on the behalf of National Institute of Standards and Technology/Office of Law Enforcement Standards (NIST/OLES) is in the process of building out a laboratory that includes Project 25 (P25) infrastructure manufactured by different vendors that is capable of interoperating via the Inter-RF Sub-System Interface (ISSI). We would like information on P25 trunked ISSI capable systems. Since we currently have an ISSI based P25 trunked system manufactured by EADS, we are interested in obtaining information about other vendors' ISSI based P25 trunked systems. An example of some of the major components that the terms infrastructure and system refer to in this context are the Radio Frequency Sub-System (RFSS) (a.k.a. base station controller, site controller, system controller, etc.), trunked P25 base stations, ISSI interface, and Operation, Administration, and Maintenance (OA&M) interface, etc. It should be clearly noted that this infrastructure will be used by ITS for research and test purposes only. The intent is not to support mission critical traffic using this infrastructure. The purpose of this market research process is to determine what companies offer ISSI based P25 trunked infrastructure that may fulfill the needs of ITS. This is a Request For Information (RFI) announcement and NOT A SOLICITATION. The responses provided by the vendors will allow us to compile the necessary information in order to make informed choices on ISSI based P25 trunked infrastructure. 2. Disclaimer It should be fully understood by all companies who provide responses to this document that this is in no way is an endorsement from ITS. The information given to ITS is strictly for research purposes. At no time should press releases or any type of sales brochures references be made with regards to this process. It should also be understood that any and all information provided, unless specifically noted by the company, could be made available to the public in the future. If specific information is covered by an existing NDA, this should be clearly described in the reply. 3. Band of Operation The frequency bands that Project 25 systems typically are capable of operating in is VHF, UHF, and 800MHz. ITS would like the infrastructure to be capable of operating in UHF band since we currently have licensed frequency pairs in this band. However, for future purposes, we'd like information on how the different manufacturers would go about converting the system to operate in the 800MHz or VHF bands. If a forklift upgrade is required, in your response, please indicate that this is the case. 4. Request For Information Questions The next several sections contain questions and requirement statements on the specific information we need to gather on ISSI based P25 trunked infrastructure. Please provide information about your current or future products that can address these questions and statements. For all questions and requirements, if your product does not currently support a particular feature or function please indicate when you anticipate the feature/function in question will be available. 4.1. Minimum Feature & Functionality Requirements 1. Infrastructure must be capable of operating in the UHF band as noted in the previous section. Specific frequencies the equipment (Fixed Station/Base Station) needs to operate on are listed in the Table 1 below: Table 1: Fixed Station/Base Station UHF Frequency Pairs Transmit Frequency (MHz) Receive Frequency (MHz) 410.5 419.5 410.225 419.225 410.425 419.425 410.85 419.85 2. For future purposes, the ability to convert the system from operating in the UHF band to operate in the 800MHz or VHF bands is desired. In your response please elaborate on the procedure to do this and what additional equipment would be required. Again, if a forklift upgrade is required please indicate this in your response. 3. ITS requires two RF sites (fixed stations) that each support two RF channels. In each RF site, it is assumed that one channel acts as a voice channel while the other acts as a control channel. If your RF site acts differently please describe. 4. Related to item 3, the capability to reconfigure and provision the system as a single RF site (fixed station) that contains all four channels (see Table 1) is required. In this case, it is assumed that one channel acts as a control channel while the other three channels act as voice channels. If your RF site behaves differently please describe. 5. The system must have an Inter-RF Sub-System Interface (ISSI) that is TIA 102.BACA-A (Update to Project 25 Inter-RF Subsystem Interface Messages and Procedures) compliant. 6. The system's common air interface must be TIA-102.BAAA-A (Project 25 FDMA Common Air Interface) compliant. 7. The modulation scheme employed by the system must be C4FM. Please describe any other modulation schemes your system supports. 8. The system must be compliant with TIA-102.AABD (Project 25 Trunking Procedures). 9. Once the TIA P25 standards are complete for packet data (TIA-102.BAEB-A) need a clear upgrade path to support trunked packet data traffic. 10. Full system Operation, Administration, and Maintenance (OA&M) to all network nodes. 11. The system must support group voice calls. 12. The system must support subscriber to subscriber voice calls. 13. There must be a clear path (or procedure) to add a TIA-102.BACA-2 (Project 25 Inter-RF Subsystem Interface Messages and Procedures - Addendum 2 - Trunked Console ISSI) compliant trunked console interface to the system. In your response please elaborate on the procedure to do this and what additional equipment (hardware, software, etc.) would be required. 14. There must be an optional upgrade path to support a trunked PSTN interconnect (TIA-102.BADA). 15. The system must support a form of cryptography (crypto). In your response please list the crypto algorithms (default and optional) that are supported by your system. 16. If Advanced Encryption Standard (AES) is not a default crypto algorithm there must be a clear path (or procedure) to add AES encryption and Key Management Facility (KMF) to the system. In your response please elaborate on the procedure to do this and what additional equipment (hardware, software, etc.) would be required. 17. If the items in item number 16 are installed, the system should allow for over the air re-keying (OTAR). In your response please elaborate on the procedure to do this and what additional equipment (hardware, software, etc.) would be required. 18. There must be an optional path to support trunked over the air programming (OTAP). 19. A complete set of documentation that clearly explains how to perform OA&M of the system. 20. Ten year Mean Time Before Failure (MTBF). 4.2. Common Air Interface (CAI) 1. What RF channel bandwidth options are available for a digital P25 trunked FDMA system? (e.g. 25KHz, 12.5 KHz, etc.) 2. Assuming the P25 TDMA specification is complete, what would it take to convert an FDMA system to a TDMA based system? a. What hardware and software would be required to do this? b. What hardware and software can be reused, or would a forklift upgrade be required? c. How much would it cost for this upgrade? 4.3. RF Site/ Fixed Station The term RF site/Fixed Station will be used generically to describe the radio interface. Other common nomenclature includes: Base Station Transceiver (BTS), Radio Node, etc. It should be noted that all questions listed below refer to a trunked FDMA RF Site/Fixed Station. 1. Please provide overall physical/mechanical information on your trunked FDMA RF site/Fixed Station. (weight, size, number of U's it would occupy in a 19" rack, power supply AC/DC requirements, RF/LAN/serial interfaces...etc) 2. How many channels can a single trunked RF Site/Fixed Station support? 3. Is one RF channel dedicated to control 100% of the time, or is the control function dynamically assigned to an idle RF channel? 4. Does your RF site/Fixed Station offer different RF power output options or power amplifiers? 5. What is the minimum and maximum RF power output per channel? 6. Indicate what backhaul interfaces are supported in your RF site/Fixed Station? (IP, T1, E1, Satellite...etc). 7. Is the protocol used on the backhaul interface proprietary or open interface - please provide a detailed description. 8. Provide any n+1 redundancy options available for your RF site/Fixed Station. 9. List and explain cost differentials (options) that affect the overall cost by more than 5%. 4.4. Controller (RFSS, Site Controller, System Controller, Base Station Controller, etc.) 1. Please provide overall physical/mechanical information on your controller. (weight, size, number of U's it would occupy in a 19" rack, power supply, RF/LAN/serial interfaces, AC/DC requirements...etc) 2. Please describe and provide detail on interconnection and the functionality between multiple controllers. a. Is the interconnection an open interface (ISSI) or proprietary? 3. Please describe and provide detail on connection and the functionality between the controller and a trunked console. a. Is the connection an open interface (CSSI) or proprietary? 4. Please describe and provide detail on the controller's supplemental data capability. In your response please elaborate on the procedure to incorporate this feature, and what additional equipment (hardware, software, etc.) would be required. 5. What is the cost of a controller supporting two RF Sites/Fixed Stations with two channels per RF site? 6. What vocoders do you support? 7. Does the controller support an external Home Location Register (HLR) and Visitor Location Register (VLR)? a. Is so what type of interface/signaling used? 8. Provide any n+1 redundancy options available for your controller. 9. List and explain cost differentials (options) that affect the overall cost by more than 5%. 4.5. OA&M elements Elements that allow the management of the network elements. 1. Can OA&M be managed for a controller (RFSS) and RF site/Fixed Site from a single interface or does each node require its own interface? 2. What external interfaces for OA&M are supported (SNMP, etc.)? 3. Can all system provisioning take place from the OA&M interface - provide details? 4. Can all system upgrades take place from the OA&M interface - provide details? 5. Are alarms for system components (RFSS, Fixed Station, etc.) reported to a main OA&M interface - provide details? 6. Does the system provide call detail records (call detail logs)? 7. Is a debug interface available for all system network elements? 8. What user interfaces are available for provisioning system components, subscribers, and groups? (For example: command line, web browser, custom GUI, etc.) 9. What system metrics are available? a. Performance metrics (PM) (i.e. BER, etc.) b. Call setup data 10. Does the system provide real-time call processing related information? If so please provide details. 11. Is there a way to set user and group priority access levels via the OA&M interface? 4.6. Network Architecture It is understood that certain components (interfaces) that compose future Project 25 trunked systems will be based upon IP networks. For now, the use of IPv4 is the preferred option. However, it is desired that all IP based network equipment be upgradeable to IPv6 from IPv4. It is understood that IP migration may need to take place at some point in the future. Please provide any information pertinent to this subject. Some P25 network architectures are moving all system intelligence into a single node. This single node may contain the following functionality: system controller, fixed station, ISSI, CSSI, etc. The system, when deployed, would be composed of several of these nodes and allows for another level of redundancy. Sometimes this type of architecture is referred to as "flat IP" or "mesh". Please describe your system architecture. 1. Provide a network or system architecture diagram showing interconnects from the RF site/Fixed Station through to the RFSS (Controller). If you architecture is a flat IP implementation please provide a network diagram of all interconnects. 2. Provide end-to-end call setup and teardown delays for the following: a. Group call b. Subscriber to Subscriber 3. Please describe how your system keeps time. (GPS, NTP, etc.) 4. Does your system currently support emergency calls for both group call and subscriber to subscriber call scenarios? If it does please indicate whether this a default feature. 5. Does your system support prioritization of users and groups? If it does please indicate whether this a default feature. 6. Please describe any data related capabilities your system may have. In your description please indicate the maximum data rate, and indicate whether this is a default feature. a. Does your ISSI implementation support data? 4.7. Subscriber System Interoperability 1. Please provide a list of the trunked subscriber device vendors that your infrastructure interoperates with. a. Please provide any pertinent test data regarding subscriber interoperability testing. b. Please include the model number of the subscriber device(s) as well. c. What type of subscriber devices can be used with your infrastructure? (portable, mobile, etc.) 5. Acronyms AC/DC - Alternating Current/Direct Current AES - Advanced Encryption Standard BSC - Base Station Controller BTS - Base station Transceiver System C4FM - Continuous 4-level Frequency Modulation CSSI - Console Sub-System Interface E1 - E-carrier level 1 FDMA - Frequency Division Multiple Access GPS - Global Positioning System GUI - Graphical User Interface HLR - Home Location Register IP - Internet Protocol ISSI - Inter-RF Sub-System Interface ITS - Institute for Telecommunication Sciences KHz - Kilohertz KMF - Key Management Facility MHz - Megahertz MTBF - Mean Time Before Failure NDA - Non Disclosure Agreement NIST - National Institute of Standards NTP - Network Time Protocol OA&M - Operation & Maintenance OLES - Office of Law Enforcement Standards OTAP - Over the Air Programming OTAR - Over the Air Re-Keying P25 - Project 25 PM - Performance Management RF - Radio Frequency RFSS - Radio Frequency Sub-System SNMP - Simple Network Management Protocol T1 - Transmission level 1 TDMA - Time Division Multiple Access TIA - Telecommunications Industry Association UHF - Ultra High Frequency VHF - Very High Frequency VLR - Visitor Location Register RFI Instructions, This is not a solicitation, it is a Request for information. The purpose of the RFI is to determine whether there are sources capable of satisfying the Government's requirements. No proposals are being requested or accepted under this synopsis. Interested sources must provide information regarding their capabilities and response in writing, including company name, address, point of contact, email address, telephone number, business type and size. Reponses will be treated separately from, and will have no bearing on any subsequent evaluation of proposals submitted in response to any resulting future formal Request for Proposals. NTIA/NIST will not pay for information or comments provided and will not recognize any costs associated with submission of comments. NTIA/NIST, as noted above, is assessing the existence of sources. Written comments or email messages shall respond in writing via email and/or hardcopy to Contact Specialist Mark Caban, MC3, 325 Broadway, Boulder, CO 80305.
 

Web Link

FedBizOpps Complete View
(https://www.fbo.gov/?s=opportunity&mode=form&id=563ecdebd6d5dcf391a1c29082f086a4&tab=core&_cview=1)
 

Document(s)

FBO Notice in Word
 

File Name: Word version of FBO posting (RFI for P25 ISSI Infrastructure v2.doc)

Link: https://www.fbo.gov//utils/view?id=0011ec215fa921e09c916930d3713733

Bytes: 83.50 Kb
 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Place of Performance

Address: Institute for Telecommunication Sciences, 325 Broadway, Boulder, Colorado, 80305-3328, United States

Zip Code: 80305-3328
 

Record

SN01742520-W 20090204/090202215751-563ecdebd6d5dcf391a1c29082f086a4 (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 |