Loren Data's SAM Daily™

FBO DAILY ISSUE OF FEBRUARY 10, 2006 FBO #1537
SPECIAL NOTICE

66 -- ETHERSTACK APCO P25 OFF-AIR MONITOR

Notice Date

2/8/2006
 

Notice Type

Special Notice
 

NAICS

334516 — Analytical Laboratory Instrument Manufacturing
 

Contracting Office

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

ZIP Code

80305-3328
 

Solicitation Number

NT91060014KAR
 

Response Due

2/22/2006
 

Archive Date

2/25/2006
 

Description

The U.S. Department of Commerce, National Telecommunications and Information Administration (NTIA), Institute for Telecommunication Sciences (ITS) proposed to negotiate on a sole source basis, under the authority of 41 U.S.C. 253 (c ) (1) with Etherstack to procure a Common Air Interface (CAI) Protocol Analyzer, the Etherstack APCO P25 Off-Air Monitor (OAM). The OAM is in support of an emerging Project 25 Compliance Assessment Program for Project 25 trunked and conventional land mobile radios. The Etherstack OAM is needed to conduct a series of Project 25 conformity assessment tests developed by Etherstack which are being considered for adoption by Telecommunications Industry Association (TIA) members to satisfy Project 25 Compliance Assessment Program testing mandates. Execution of the conformity tests requires an instrument capable of monitoring and logging all P25 inbound and outbound signaling packets on a control channel pair, as well as all inbound and outbound link control words on a specified traffic channel. Capture and display all of the messaging used during the various P25 call setup procedures specified in TIA-102 suite of standards is essential. The standards which define the pertinent messages, parameters and protocols are as follows: References 1. TSB102.AABA, APCO Project 25 Trunking Overview, April 1995 2. ANSI/TIA/EIA 102.AABB, Project 25 Trunking Control Channel Formats, May 2000. 3. ANSI/TIA/EIA 102.AABC, Project 25 Trunking Control Channel Messages, May 2000. 4. TSB102.AABF, APCO Project 25 Link Control Word Formats and Messages, May 1996. 5. TSB102.AABG, APCO Project 25 Conventional Control Messages, July 1996. 6. TSB102.AABD, Project 25 Trunking Procedures, October 1997. The P25 CAI Protocol Analyzer must meet the following specifications: Specifications 1. Capable of monitoring all inbound and outbound control channel signaling between a Project 25 subscriber unit and a Radio Frequency Subsystem (RFSS) 1.1. Detect, decode, and capture (log) all of the Inbound Signaling Packets (ISPs) generated by a P25 subscriber unit on a fixed control channel uplink frequency 1.2. Detect, decode, and capture (log) all of the Outbound Signaling Packets (OSPs) generated by an RFSS on a fixed control channel downlink frequency 2. Capable of monitoring all of the inbound and outbound traffic channel signaling between a Project 25 subscriber unit and an RFSS 2.1. Detect, decode, and capture (log) all of the Link Control Words generated by a P25 subscriber unit on a fixed voice channel uplink frequency 2.2. Detect, decode, and capture (log) all of the Link Control Words generated by an RFSS on a fixed voice channel downlink frequency 3. Capable of applying a time stamp to all ISPs and OSPs referenced to the system clock of the instrument 4. Capable of logging and displaying all valid control channel ISPs and OSPs and their payloads, including the following data: 4.1. Date and time stamp 4.2. Type of packet, i.e. ISP or OSP 4.3. Description of packet in the following formats: 4.3.1. Short alias name format 4.3.2. Full name format 4.3.3. Mnemonic 4.3.4. Raw binary, octal, and hexadecimal packet data 4.4. Parameters 5. Capable of logging and displaying all valid traffic channel link control words including the following data: 5.1. Date and time stamp 5.2. Type of packet, i.e. ISP or OSP 5.3. Packet payload 5.4 Raw binary, octal, and hexadecimal packet data 6. Capable of logging and displaying all valid inbound and outbound Link Control Words and Encryption Syncs and their payloads including the following data 6.1. Date and time stamp 6.2. Type of packet, i.e. ISP or OSP 6.3. Description of packet in the following formats: 6.3.1. Short alias name format 6.3.2. Full name format 6.3.3. Mnemonic 6.3.4. Raw binary, octal, and hexadecimal packet data 7. Capable of storing all captured (logged) data to an external firewire or USB hard drive. 8. Support a message-specific triggering capability that would initiate logging or triggering upon receipt of a predefined signaling packet. 9. Capable of operating in the VHF, UHF, 700, and 800 MHz bands which requires both explicit and implicit mode operation. 10. Capable of displaying call flow diagrams for message traffic from the beginning of the call setup process through the end of the call teardown process. 11. Capable of displaying logged data on a real-time tabular display with scrolling capability. This procurement is being conducted per FAR Part 13, Simplified Acquisition Procedures (NTE $100K). This synopsis is issued for information only. No competitive solicitation is planned. Based on our market research, Etherstack offers the only product that meets all of the technical specifications that are necessary requirements of this procurement. Information submitted in response to this notice will be used solely to determine whether or not use of competitive procedures to fulfill this requirement would be in the Government's best interest and must address qualifications pertinent to this requirement. Any questions regarding this notice must be submitted in writing to the attention of Ms. Rima (e-mail preferred). Anticipated award date is February 23, 2006.
 

Place of Performance

Address: 325 BROADWAY, BOULDER, CO

Zip Code: 80305

Country: USA
 

Record

SN00983097-W 20060210/060208211958 (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 |