SPAWARSYSCEN-Charleston, PO Box 190022, N. Charleston, SC 29419-9022

58 -- INFORMATION REGARDING STATE-OF-THE-ART WIRELESS TELEPHONY SOL N65236-00-J514JN POC JAMES W. NEW, Code J514JN, 757-558-6845, FAX 757-396-0411 E-MAIL: Click here to contact the point of contact via e-mail., newj@spawar.navy.mil. 1. SPAWAR Systems Center Charleston Code 514JN is soliciting industry comments and information concerning the establishment of minimum functional requirements for application of wireless telephony devices (such as PCS) to critical portable wireless communications requirements in US Navy Ships. There is no procurement of hardware planned at this time, and availability of funding for eventual procurement is uncertain. The purpose of this request is to determine what the current state-of-the-art is in wireless telephony, and to look at how rapidly-evolving systems could best be used to support the Navy's shipboard communications needs. This is a request for technical information only, so realistic competitive performance specifications can be written if the technology looks promising and funding becomes available for eventual procurement. 2. BACKGROUND. Two technologies currently provide most US Navy shipboard portable wireless communications: trunked radio (viz., land mobile radio (LMR)) and wireless telephony (viz. personal communications services (PCS)). Trunked radio (LMR) has been perceived to be a broadcast system (one-to-many) that can supply limited point-to-point connectivity (one-to-one). Wireless telephony (PCS) has been perceived to be the opposite: a point-to-point system providing limited broadcast capability. For the most part, LMR has been used for critical functions such as damage control, flight deck, well deck, navigation, and underway replenishment, while PCS has been used for less critical administrative duties. At their core, both LMR and PCS systems are heavily software-driven devices. Both have proprietary, closed operating systems. Although users can program many system features, they cannot alter the operating systems structure. Many observers speculate that PCS might provide an attractive alternative to LMR. This speculation is driven both by the fact that PCS is a newer technology, and by the anticipated introduction of a new generation of PCS based on open architecture, wireless Internet Protocol (IP) telephony. Thus, to evaluate the possibility that PCS might be suitable for additional shipboard portable wireless communications, those requirements need to be clearly defined in functional terms. 3. DESIRED FEATURES A. Hierarchical Requirements -- Shipboard communications require four hierarchical levels (Figure 1). Level 1 is the Command Node. Level 2 are Department Nodes (Engineering, Navigation, Weapons, Command, Intelligence, Medical, Supply, Damage Control, Combat Cargo, Air Operations). Level 3 are Work Centers. Level 4 are end users. (1) Level 1. The Command Node must be able to communicate: (a) Simultaneously with all Department Nodes (Level 1 -> 2 Paths B1, Bn-1, Bn). (b) Selectively with any subset of Department Nodes on demand (Level 1 -> 2 Paths B1, Bn-1, Bn). (c) Simultaneously with all nodes, ruthlessly preempting all nodes nearly instantaneously (Level 1 -> All Level Paths A1, A2, An-1, An). Figure 1. US Navy Ship Portable Wireless Hierarchical Requirements—NOTE: To obtain this figure contact the POC via telephone, FAX, or e-mail. (2) Level 2. Department Nodes must be able to communicate: (a) Selectively with the Command Node (Level 2 -> 1 Paths B1, Bn-1, Bn). (b) Simultaneously and selectively with all Department Nodes (Level 2 -> 2 Paths C1, Cn-1, Cn). (c) Simultaneously and selectively with all Work Center Nodes within its functional chain (Level 2 -> 3 Paths D1, Dn-1, Dn). During communications with Level 3 Nodes, Level 2 Nodes must be able monitor Level 1 and Level 2 Nodes. (3) Level 3. Work Center Nodes must be able to communicate: (a) Selectively with its associated Department Level Node (Level 3 -> 2 Paths D1, Dn-1, Dn). (b) Simultaneously and selectively with all Level 3 Nodes reporting to its associated Level 2 Node (Level 3 -> 3 Paths E1, En-1, En). (c) Simultaneously and selectively with all Level 4 Nodes within its functional chain (Level 3 -> 4 Paths F1, Fn-1, Fn). During communications with Level 4 Nodes, Level 3 Nodes must be able monitor its associated Level 2 Node. (4) Level 4. User Nodes must be able to communicate: (a) Selectively with its associated Work Center Node (chain (Level 4 -> 3 Paths F1, Fn-1, Fn). (b) Simultaneously and selectively with all Level 4 Nodes reporting to its associated Level 3 Node (chain (Level 4 -> 4 Paths G1, Gn-1, Gn). During communications with Level 4 Nodes, Level 4 Nodes must be able monitor its associated Level 3 Node. B. Preemption Requirements -- Selected Level 2 Users on aircraft carriers must be provided with multiple levels of ruthless preemption. Flight deck operations require five levels of preemption: the flight deck announcing system has first priority, the Air Boss has second priority, the Mini-Air Boss has third priority, the Flight Deck Handler has fourth priority, and the Carrier Air Group (CAG) has fifth priority. C. Latency -- The system must provide minimum switching latency. Latency begins with the first operator action to execute a call and ends with the beginning of audio receipt by the slowest call participant. This delay should not exceed one-quarter second and must not exceed three-quarter second regardless of system size. D. Power Levels -- All system RF devices (handsets and fixed units) must be safe to operate in close proximity to any ordnance in any condition. E. Single Action Access (Push-to-Talk) -- All user devices must provide single action access, e.g. push-to-talk (PTT), for the initiation of calls. F. Capacity -- The system must be scalable to fit a variety of ships. As a goal, the system should be capable of supporting the ship's full complement. The system must be scalable (Figure 1). In the extreme, every user in the system must be capable of creating a call that includes all users for emergency situations. System architecture must be capable of supporting large concentrations of users in small areas. At a minimum, the system must be capable of simultaneously supporting up to 30 users located within a 100' radius without blocking. As a goal, the entire system should be non-blocking. At a minimum, the system should provide a grade of service of at least 5%, i.e. no more than 1 in 20 calls are denied because of insufficient capacity. G. Interfaces -- Interfaces are required for standard shipboard communications devices including Flight Deck and Well Deck Helmets, Handsets, Headsets, Intercommunication Systems, and Announcing Systems. Wireless fixed units are required to replace or supplement wired telephony devices, wired intercommunication stations, or wired announcing system speakers. H. Transportability -- All handsets must be capable of shifting between related talk groupings by rapid, easily understood and executed user actions. Consider a Level 4 example (Figure 1): Level 4 User #A2B3 must be capable of shifting from Level 3 talk grouping #A2B to Level 3 talk grouping A2C, e.g. to take the place of Level 4 User #A2C1. This is analogous to a damage control repair party member shifting repair zones during a casualty. At Level 3, this would be analogous to one Repair Locker assuming communication responsibilities of another Repair Locker. I. Suitability -- All portable devices must be compatible with typical shipboard ranges of temperature, shock, vibration, moisture, and corrosion such that they provide a reasonable service life. All devices must be compatible with typical ranges of shipboard RF emitters such that they are not susceptible to, and do not cause, harmful electromagnetic interference (EMI). Selected handsets must be capable of extended operation on a single battery charge with an extreme duty cycle that is the equivalent of 40% transmit, 40% receive and 20% standby. At a minimum, flight deck handsets must be capable of at least six (6) hours of uninterrupted operation under this equivalent duty cycle. As a goal, they should be capable of 12 hours of continuous operation with this equivalent duty cycle. J. Survivability -- As a goal, all handsets should be capable of point-to-point communications, independent of the communications infrastructure. K. Security -- All handsets should be capable of privacy encryption meeting the requirements of FIPS 182 for protection of sensitive, but unclassified information. As a goal, all handsets should be capable of providing encryption suitable for handling classified National Defense information. 4. Interested vendors are asked to forward explanations and/or technical literature concerning this equipment via e-mail newj@spawar.navy.mil, or via mail to SPAWAR Systems Center Charleston, Code 514JN -- James New, PO Box 1376, Norfolk VA 23501-1376, or delivery to SPAWAR Systems Center Charleston, Code 514JN -- James New, Bldg 172 Wood Road, St Juliens Creek Annex, Portsmouth VA 23702, with a copy of the cover letter (no tech data enclosed) to: SPAWAR Systems Center Charleston, Code 1115, Jean Duncan, PO Box 190022, North Charleston SC 29419-9022. In addition, plese provide information regarding the size of business: average annual revenue for past 3 years, and the number of employees. Replies are requested by June 30, 2000. 5. This synopsis is for information and planning purposes and is not to be construed as a commitment by the Government. This is not a solicitation announcement for proposals and no contract will be awarded from this announcement. No reimbursement will be made for any costs associated with providing information in response to this announcement, and any follow-up information requests. Respondents will not be notified of the results of the evaluation. Respondents deemed fully qualified will be considered in any resulting solicitation for the requirement. The Government reserves the right to consider a small business set-aside or 8(a) set-aside based on responses hereto. Posted 05/26/00 (W-SN459210). (0147)

Loren Data Corp. http://www.ld.com (SYN# 0144 20000531\58-0003.SOL)