OREGON WIRELESS INTEROPERABILITY NETWORK (OWIN) PROJECT. Conceptual Design for Radio System, Revision 1 (November 30, 2006) (Deliverable 9-D)

Transcription

1 OREGON WIRELESS INTEROPERABILITY NETWORK (OWIN) PROJECT Conceptual Design for Radio System, Revision 1 () (Deliverable 9-D) Prepared by: Federal Engineering, Inc Arrowhead Drive, Suite 160 Fairfax, VA

2 Executive Summary This Conceptual Design for a Radio System describes the Oregon Wireless erability Network (OWIN) at a high level, with enough detail to understand its operation and configuration. The purpose of the conceptual radio design is to identify the major system components of the system in sufficient detail to enable the creation of an accurate estimated budget to be applied to the following stages of the project. OWIN will be composed of several subsystems. A microwave system is required to connect every site together into a complete network. Although other forms of digital networks could be used, the remoteness of the sites, make the use of microwave the most economical. The primary radio system will be the APCO Project 25 (P25) trunked radio subsystem. This system meets the requirements of the APCO P25 standards, making it compatible with equipment from many vendors. This system will be trunked, meaning that it uses a pool of channels for all users, and when a channel is needed, the system automatically assigns one for the conversation. This is in contrast to today s system where channels are dedicated for individual agencies and where secondary channels are usually not available to handle a second conversation. The OWIN P25 trunked system will be divided into three geographic areas, and it will use two different frequency bands Each area will use one primary frequency band Some sites have trunked channels; some have trunked 700 channels, and other sites will have both and 700 channels. Most of the mobile units operating in the trunked radio system will be equipped with a mobile and a portable radio, and the mobile can be connected to a vehicular repeater. In this configuration, when the user is out of the vehicle, the signal from the portable radio can be relayed through the vehicular repeater. This extends the effective range of the portable radio to provide the same coverage as the mobile radio in the vehicle. Where users do not require portable radio coverage, a different configuration can be used. Since the P25 radio system is a digital network it carries a continuous data stream that can also carry low speed data for some mobile computer applications. This data can be used for form-based information look-up and filing, but is not fast enough to carry web and image based applications. The P25 data network will require a minimal amount of equipment connected to the mobile radio to provide low speed mobile data service wherever the P25 voice network provides coverage. For higher speed applications, a separate 700 high speed data system will be installed at selected sites. This network will carry Page 2 of 57

3 applications that are more demanding and will require an additional radio and computer components in each vehicle. OWIN also contains another infrastructure-based radio subsystem providing conventional (non-trunked) operation. This system has two components. The first principally serves the Oregon Department of Forestry (ODF) and uses an additional repeater on each site that is presently and ODF radio site. This approach will achieve equal coverage to ODF s present service areas, and it retains compatibility with the federal agencies and other agencies with whom ODF interoperates. For statewide applications, ODF units can also operate on the trunked system. ODF will also retain its mobile (and temporary location) based fire cache, and initial attack systems for its tactical uses. The second conventional component, for use by all OWIN agencies, is two, statewide, conventional repeater channels at every OWIN site. These channels will be used for general tactical, coordination, and interoperability with state agencies in addition to being part of the continuum of solutions for continuity of service during a system failure. To provide interoperability among all public safety radio users in Oregon, an interoperability subsystem will have a mix of repeaters and simplex channels located strategically at sites throughout the state. This subsystem will provide OWIN with channels 1, UHF channels, and 800 channels 2 that are all on dedicated use nationwide interoperability channels. Most of these channels will operate in both analog and P25 digital (conventional) modes. 3 These channels, as well as channels and talk-groups from all other subsystems, will be connected to an interoperability matrix switch. This switch communicates with equipment on the many sites by use of an Internet Protocol network carried by the microwave system. Consistent with coordination from the SIEC, this 1 The channels are presently simplex. OWIN is working with the Federal Partnership for erable Communications (FPIC) to secure federal frequencies to pair with the nationwide interoperability frequencies to establish five, interoperability frequency repeater pairs for statewide use in Oregon. 2 It is important to note that through the current 800 rebanding process, the NPSPAC mutual aid channels will be changing frequency over the next several years. 3 By rule, the national calling channels cannot operate in the encrypted mode. For expediency, it is recommended that the calling channels in each band should only be operated in the analog mode. Page 3 of 57

4 switch will enable any channel to connect to any other channel operated by OWIN. Remote control terminals at various dispatch centers will control the switch. Because of their centralized type of dispatch, and the conversion to P25 digital transmission, the Oregon Department of State Police (OSP) and Oregon Department of Transportation (ODOT) will have new dispatch consoles installed in their dispatch centers. Replacement of the consoles is necessary in order to allow them to control the P25 radio system. The Oregon Department of Forestry (ODF) and the Oregon Department of Corrections (DOC) will be equipped with appropriate dispatch equipment at each of their facilities. This conceptual design report highlights the previous reports and decisions made to decide on the architecture used for OWIN, and concludes with descriptions of the operation of OWIN communications. Page 4 of 57

5 Table of Contents Executive Summary Introduction OWIN design goals Current system Agency needs Current system deficiencies Previous recommendations Technology recommendations System consolidation recommendations Core site recommendations Frequency band recommendations Draft radio design concepts Radio system design Radio system design criteria Radio system overview Conceptual design Description of OWIN system configuration Description of OWIN operation Satisfaction of design criteria Gap Analysis (Deliverable 11-A) Next steps...40 Appendix A. Site equipment detail...41 Appendix B. Coverage maps...52 Page 5 of 57

6 1.0 Introduction The Oregon Wireless erability Network (OWIN) project has progressed through the following steps: Selecting Federal Engineering, Inc. (FE) as the State s consultant Performing a needs assessment Studying the State s radio sites Studying the radio coverage from these sites Performing a frequency assessment Developing a channel plan Selecting the frequency bands and technology to use Similar work was performed to develop a plan for a new microwave system. The conceptual designs of OWIN and its microwave system provide the basis for determining a budgetary price and provide insights into the implementation process. The Statement of Work (SOW) for this Conceptual Design report identifies the following activities to be included as preparation before the conceptual design can be developed: Choice of analog or digital Choice of trunked or conventional operation Review and choice of network architecture Choice of consolidated or distributed radio systems Review of system requirement Needs of Oregon state agency participants and stakeholders individually and as a whole Compliance with the provisions of HB2101 erability capabilities and capacity, now and anticipated for the future within the State and with participating jurisdictions State system frequency spectrum requirements and availability Meets or exceeds the current functional capabilities offered by participants existing wireless communications systems Leverages existing State wireless communications assets where feasible as well as those new assets being deployed within Oregon Uses available, open architecture, standards-based technologies, services, and products that exist in today's marketplace but allows migration to emerging wireless technologies when user requirements and economics support migration Page 6 of 57

7 Identify the issues from technical, economic, performance, regulatory, and frequency availability viewpoints The SOW also requires that: The system design will include an analysis for State agencies to operate in a consolidated analog trunking system, and it will be determined if all units in the system must operate in digital mode. This will be done through analysis of the capabilities of the technologies under consideration as well as understanding the specific user needs and constraints. More specifically, the design will include the capability for some ODF users to operate in conventional analog modes. System design must also consider statewide use of frequencies in a conventional mode. Federal Engineering (FE) provided a set of recommendations based heavily upon the user needs and requirements as discovered through and documented within the Needs Analysis (Deliverable 4-D), subsequent analysis and ongoing, discussions with Oregon agencies and stakeholder organizations. Then FE will recommend a conceptual design which will provide cost effective, shared, reliable communications outlining the reasons for the recommendation. The system recommendations will address State networks, tower facilities, and infrastructure. Compatibility with existing facilities and equipment will be taken into account. FE s conceptual design will be innovative and directed toward the State's future public safety wireless needs and goals in a cost effective manner. This report is the result of the discussions between OWIN staff and FE concerning the most appropriate conceptual design for the OWIN radio system. 2.0 OWIN design goals 2.1 Current system Four state agencies have radio systems that will be replaced or supplemented by OWIN. The Oregon State Police (OSP) operates a conventional radio system. The Oregon Department of Transportation (ODOT) uses conventional operation. The Oregon Department of Forestry (ODF) has a highly diversified conventional system with dispatch points at area offices. And the Department of Corrections (DOC) uses UHF and 800 trunked systems within their facilities. These Page 7 of 57

8 systems are outlined in detail in the Report and Recommendation for System Consolidation report (Deliverable 9-B). 2.2 Agency needs The Needs Analysis report describes the needs and requirements for radio communications for the state agencies. These needs and requirements as captured in that report include the following as described in Table 2.1: Increased interoperability Dispatch from State EOC Common interoperability channels Increased capacity Tactical/local repeater channels Wide area communications Statewide channel Increased coverage Improve mobile coverage Improve portable coverage Improve rural coverage Adjacent state coverage Improved wide-area coverage Mobile data transport capability Mobile data transport Automatic vehicle locator Maps and images In-vehicle messaging In-vehicle computing Medical data Infrastructure linked dispatch locations Comm center to comm center link Local PSAP connection Multiple main communications centers Load sharing Back-up transfer Governance needs Support appropriate funding Maintain priority, autonomy, control, flexibility Address governance Service and support needs 7X24 service Distributed service Locations Increased technical staff Other common needs Maintain existing coverage Emergency communications Infrastructure system needs Network reliability Network redundancy Site/Infrastructure improvements Infrastructure data transport Network expandability for growth Ring down phone/intercom capability Radio system and equipment features Scan Remote disable Unit identification Emergency call Simple to use radios Secure communications/encryption P-25 compliance Automatic channel selection Telephone interconnect Uniquely reported needs Field programmable Clone-able Open network (any authorized user) On-site coverage Portable communications systems Table 2.1 Requirements for Radio Communications While some needs are related to the operation, management, and governance of the system, most are directly related to the design. The goal of the OWIN design is to meet these needs to the greatest extent possible in a cost effective manner. Page 8 of 57

9 2.3 Current system deficiencies The current radio systems fall short of almost every need and requirement identified. The current systems provide only basic communications, where OWIN will support many required features such as security, statewide interoperability for state agencies, emergency call, and data communications. Beyond coverage and features, the OWIN design will address the reliability needs that the current systems are unable to meet. 3.0 Previous recommendations Throughout the progress of this project, reports have been prepared to provide an account of the work and to memorialize the findings of the Federal Engineering Project Team. The recommendations made in these reports were approved by OWIN technical staff, the State Wireless Infrastructure Investment Group (SWIIG) and the State erability Executive Council (SIEC) whenever appropriate and were incorporated into the conceptual design. Some of these reports are described in the next sections. 3.1 Technology recommendations In the Recommendations of Selected Technologies Report (Deliverable 9-A), FE recommended that OWIN be based on P25 digital modulation and trunking technology wherever possible. Review of this report and approval of this recommendation was by OWIN technical staff, the SWIIG and the SIEC. 3.2 System consolidation recommendations In the Report and Recommendation for System Consolidation (Deliverable 9-B), FE recommended that wherever possible, all State agencies should use a consolidated radio system infrastructure. As with the Selected Technologies a review of the report and approval of this recommendation, was by OWIN technical staff, the SWIIG and the SIEC. Page 9 of 57

10 3.3 Core site recommendations FE conducted an exhaustive review of the radio sites currently in use by the State of Oregon, and many additional sites to develop a core sites list capable of providing the desired coverage for OWIN. The sites are identified in this process and their properties are discussed in the Core Site report (Deliverable 5-B). After considerable review of the recommended sites and their coverage potential by OWIN technical staff, the State decided on proceeding forward with a conceptual design based on the use of 257 core sites. Sites were selected to provide a level of coverage that meets or exceeds the existing coverage from the best State radio system in each county, assuring consistent and improved coverage for all agencies. FE incorporated this core site list into this Conceptual Radio Design. 3.4 Frequency band recommendations The Frequency Band Recommendation, (Deliverables 7-A and 7-B), describes how the frequency bands were chosen for OWIN. These recommendations were a result of an exhaustive study described in the Frequency Analysis Report (Deliverable 5-A). Although propagation and other factors favored as the band of choice, the frequency analysis and planning determined that there is not a sufficient quantity of frequencies to allow reuse of channels without them interfering with one another. It was also determined through the coverage analysis that the 700 band would require a prohibitively high number of new radio sites. Therefore, only a dual band, hybrid approach using both and 700 channels can provide a practical design for OWIN. 3.5 Draft system design concepts During the development of the Conceptual Microwave System Design and of this document, FE presented several draft versions to the State for review. These designs, similar to what is being presented in this document, were used to drive discussion that has resulted in the adjustment of the subsystems to optimize their alignment with the needs of OWIN, their cost, and their resulting value. Page 10 of 57

11 4.0 Radio system design As with any large, complex project or mission, it can be more easily understood and managed by examining its smaller components or subsystems. OWIN will be a system of systems, with each smaller system (or subsystem) having distinctive and understandable roles. 4.1 Radio system design criteria Sections 2 and 3 above summarize the work that was required to bring the OWIN project to this conceptual design phase. This background is critical to assure the State of Oregon that the outcome of this program meets the States needs, in the most cost effective manner while minimizing risks. The work from the previous reports calls for a radio system with the following characteristics: Project 25 compliant Improved radio coverage Provide more capacity and 700 dual band Use of 257 core radio sites Place interoperability channels at appropriate sites Use trunking wherever possible Provide a conventional, digital subsystem for ODF Retain a conventional tactical capability for ODF Interface with existing DOC radio systems Use an interoperability matrix switch Provide mobile data capabilities Simple user operation These factors must all be included in the conceptual design of the OWIN radio system. Each of these factors captures the needs of the State as concluded by FE and agreed upon by the OWIN project management. Page 11 of 57

12 4.2 Radio system overview The OWIN radio system will be composed of several subsystems, each with the purpose of fulfilling specific needs for the State. Each of these subsystems is interrelated and dependent upon one another to fulfilling their mission. These subsystems are shown in Exhibit 4.1, System overview. Page 12 of 57

13 Simulcast subsystems P25 & low speed data controllers Microwave to other sites P25 trunked or 700 radios P25 conventional radios Conventional interoperability, UHF, & 800 radios High speed 700 data radio Microwave system connecting all radio sites Dispatch centers Central controllers & interoperability switches Exhibit 4.1 System overview The key to the entire system s operation is the digital microwave subsystem. The microwave subsystem, described in the Conceptual Page 13 of 57

14 Microwave System Design report (Deliverable 8-B), is the first subsystem of OWIN and provides the communication backbone of OWIN. This backbone not only connects all of the radio sites to the dispatch and control locations, but also connects each of the other subsystems components where required. The next four subsystems make up OWIN s radio infrastructure. This radio infrastructure is comprised of several independent radio subsystems. These are; a P25 trunked radio subsystem a conventional radio subsystem an interoperability radio subsystem a dedicated mobile data radio subsystem The second subsystem is the P25 trunked radio system. This P25 trunked radio subsystem is the primary communications network for the agencies participating in OWIN. The third is the conventional radio subsystem provides communications for agencies that have reasons not to move to the trunked system. This allows those agencies to continue to use conventional systems where and when required. The fourth is the interoperability subsystem, which provides communications connectivity between OWIN participants and other agencies who continue to operate their own separate systems. The fifth is the dedicated data radio subsystem that provides a high speed 700 data channel for mobile data applications. In addition to these radio infrastructure subsystems there are three additional subsystems which are in some ways components of the four radio systems previously discussed. The sixth subsystem is necessary in any radio system. It is the dispatch console and control subsystem. This provides the dispatch and primary user interface to the various OWIN radio subsystems. Each agency uses this subsystem in a different manner. In some agencies it is a central command and control point. In other agencies it may perform as a dispatch and message relaying center. In other agencies it provides communications monitoring and the support of field operations. No matter how the functionality is used, technically the subsystems are very similar. In OWIN this subsystem is made up of the dispatch console equipment that is connected through the microwave subsystem to the various radio subsystems. The seventh subsystem is the interoperability matrix switch subsystem. This subsystem provides primary control over the interoperability radio Page 14 of 57

15 subsystem, and also provides the interface functionality between the various radio channels on all of the voice radio subsystems. The eighth subsystem is the P25 mobile data subsystem, composed of the equipment required to provide integrated voice and data services on the P25 trunked subsystem and on any of the conventional P25 channels. The P25 data functionality requires installation of equipment at control sites, radio sites, and in the vehicle. This subsystem is an ancillary component of the P25 voice subsystem. The equipment in this subsystem is also linked with the control and interface equipment of the dedicated mobile data radio subsystem. These subsystems are described in more detail in Section 5 below. 5.0 Conceptual design Using the basics of the subsystems described in Section 4, this section will describe in more detail how they will be applied to OWIN. This conceptual design is provided to demonstrate the configuration of the system and its subsystems, describe how the system will operate, and provide the basis for developing a budgetary cost estimate. It will also be crucial for the development of the implementation plan and the business case study, both of which will be developed in this project soon after the acceptance of the conceptual design. 5.1 Description of OWIN system configuration The description of the technical configuration of OWIN and its subsystems begins with the common components essential to the operation and control of the system. This description will work through the central controllers, data switches, and dispatch centers, and work its way outward to the radio site and its equipment and then to the subscriber units operated by the users in the field. The configuration for the connectivity of the system components is dependent upon the microwave network as it is described in the Conceptual Microwave Design Report (Deliverable 8-B). For the sake of this report, we assume that the microwave subsystem design and build meets the needs of the radio system, and we can consider the microwave to be a telecommunications pipeline connecting all the subsystems as needed. Exhibit 5.1 System overview, provides a high-level view of OWIN. Page 15 of 57

16 Exhibit 5.1 System overview The microwave subsystem The conceptual design of the microwave is described in the Conceptual Microwave System Design Revised report (Deliverable 8-B,). This subsystem will provide the necessary interconnection of all system components. The conceptual design assumes that all equipment used in the system will use Internet Protocol (IP) connections. Therefore the Page 16 of 57

17 microwave subsystem will be composed of microwave radios, multiplex equipment, and other items such as SONET switches. The equipment would also include routers, switches, and other local area network (LAN) equipment found in data communications environments. The radio subsystem equipment will simply plug into the microwave subsystem The Project 25 trunked radio subsystem The heart of the OWIN radio system is the P25 trunked radio subsystem. This subsystem will have transmitters located at each OWIN radio site throughout the State. This subsystem provides radio communications for all of the OWIN participants. The trunked system makes use of a hybrid frequency plan, using both the and the 700 radio bands. The key element of this subsystem is the use of trunking. Where a conventional radio system has one or more individual channels for each agency, trunking pools the channels for all agencies, and when needed one of the pooled channels is assigned automatically for a conversation. The channel is returned to the pool when the conversation is concluded. Trunking makes the most efficient use of a group of channels by automatically distributing them over many agencies, as needed. The trunked radio system will meet the requirements of ANSI/TIA 102 series standards, referred to as APCO Project 25 (P25). P25 is the only set of open standards for public safety digital radio systems available in the United States. The use of these standards provides a set of features meeting the needs of public safety communications in a non-vendor specific environment. This will permit multiple vendors to supply equipment compatible with the system. P25 is the accepted standard for many agencies, including federal agencies such as the Department of Defense, Federal Bureau of Investigation, and United States Forest Service. The features of P25 trunking were discussed in the Overview of Selected Technology Issues presentation that accompanied the Recommendations of Selected Technologies (Deliverable 9-A). They include a wide range of available capabilities including but not limited to: Page 17 of 57 Greater channel efficiency Fewer channels requirements Automatic roaming Simplified operation

18 Consistent features Simplified system expansion Improved integrated voice and data Automatic channel assignment Automatic site selection Group call Private call Telephone interconnect Unit ID transmission Emergency call Priority (multiple levels) Queuing and call back Call alert Radio disable Multiple group call The State of Oregon will be covered by trunked P25 radio communications in either the ( ) or 700 radio bands. For each OWIN radio site, either or 700 was chosen depending on the area for which that site provides coverage. Some sites will have both and 700 channels. Detail on the site selection is available in the Frequency Analysis Report (Deliverable 5-A). That report also outlines assignments of channels, frequencies, the quantity of channels, and the sites where simulcast groups will be implemented. A summary of this information is included in Appendix A Site equipment detail, attached to this report. Simulcast technologies are used where conservation of frequencies is required and where geographic site separation criteria are met. In the simulcast groups, the same radio channels are used at all the sites in the group. When a channel is assigned for a conversation, that channel transmits the same information from all sites simultaneously. Simulcast transmission requires careful engineering and specialized equipment to align the signals being transmitted to prevent the signals from interfering with one another. The simulcast group also uses receiver voting, where all of the receivers on the same channel feed their audio to equipment called comparators that evaluate the quality of all the audio, selects the best quality receiver, and then feeds that audio to both the dispatch center and back to the simulcast transmitters. Therefore, only the best audio received is rebroadcast by the simulcast system. For each of the simulcast groups, one site will serve as the central site for that simulcast group. This site will house the simulcast group controller Page 18 of 57

19 and the receiver voting system serving that group of sites. This simulcast controller provides the interface to the system central controller and provides the signal alignment information so the transmitted signals do not interfere with one another. Initially, there appear to be enough usable channels within the State Use portion of the 700 band to accomplish the Oregon hybrid design without adding the complexity of simulcast to the 700 portion of the system. In the final design, however, simulcast will be an option for the vendors to consider as they develop their proposed design. OWIN staff will also work within the Region Regional Planning Committee to best plan for how the General Use portion of the band can be used to benefit all of Oregon through OWIN. The flexibility of the system to use both the State Use and General Use portions of the band will assure an adequate number of channels for the implementation and growth of OWIN. As described earlier, some areas of the State will be served by channels and others by 700 channels. These channels are proposed to be distributed as listed in the Frequency Analysis Report, (Deliverable 5-A). To the extent possible, all channels will be trunked. In some areas, will be simulcast among a group of sites. The breakdown of these quantities is as follows: Radio System # of Sites # of Repeaters # of Simulcast Groups Trunked P Trunked Simulcast Trunked P Table 5.1 Quantity of sites and equipment An overview of the coverage provided by these trunked systems is provided in Exhibit 5.2 OWIN trunked system coverage, and Exhibit OWIN 700 trunked system coverage, below. Higher resolution versions of these maps are included in Appendix B. Page 19 of 57

20 STATE OF OREGON Conceptual Mobile Talk-in Coverage (257 Total Sites, 136 ) County Border Interstate State/County Road Candidate Site Dual-Band Site Area Covered (95% Reliability, DAQ > 3.4) Lake / Ocean Mobile Transmit Power: 40 Watts Mobile Antenna Height: 1.5 m Transmit Frequency: 154 PERCENTAGE OF STATE COVERED: 80 % File: OWIN.OREGON.conceptual.P25(257Sites) jpg Exhibit 5.2 OWIN trunked system coverage STATE OF OREGON Conceptual 700 Mobile Talk-in Coverage (257 Total Sites, ) County Border Interstate State/County Road 700 Site Dual-Band Site Area Covered (95% Reliability, DAQ > 3.4) Lake / Ocean Mobile Transmit Power: 35 Watts Mobile Antenna Height: 1.5 m Transmit Frequency: 800 PERCENTAGE OF STATE COVERED: 20 % File: OWIN.OREGON.conceptual.P25(257Sites) jpg Exhibit 5.3 OWIN 700 trunked system coverage Page 20 of 57

21 The conceptual design of the OWIN significantly improves coverage over the existing systems throughout the State. This design provides 86% coverage of the State for P25 voice services, which is significantly better than the current coverage. Currently the coverage varies by state agency and ranges from 44% to 75% statewide. In addition, OWIN is designed to provide a well engineered, robust voice network, providing coverage in every county that meets or exceeds the coverage of the best of the three existing State systems. The OWIN design assumptions do not consider the signal levels required for the reliable penetration into buildings. OWIN, as a statewide system, has been designed as needed to support the use of mobile radios in motion and of handheld radios used outside of vehicles. No consideration has been taken to design for the use of the system from within structures. This consideration could cause a huge increase in the number of sites to achieve that additional level of reliable coverage. Penetration of buildings by signals is a local requirement. The types of signal level considerations required for reliable in-building use are left to any local agencies that may consider use of the OWIN system. The P25 trunked subsystem stations installed at each OWIN radio site will be connected to antennas via appropriate antenna combining equipment and connected to the microwave using IP connections. The stations will be in either the ( ) land mobile radio band or the 700 public safety radio band, depending on the coverage the particular site provides. Some sites will have equipment for both bands where the site requires such. The specific configuration of the radio equipment is left for the detailed design phase. That level of design at this stage in the program is of little value due to the differences between vendors architectures. Appendix (A) Site equipment detail, provides a complete listing of the radio sites used by OWIN in this conceptual design, and the complement of radio transmitters at each of those sites. The radio equipment will be able to be powered by either the primary power system or the supplemental power system available at each site. In most cases the primary power system is commercially supplied alternating current (AC), and the supplemental power system is a combination of AC generator and direct current (DC) battery supplies. Some sites will have different power supply configurations due to the availability of commercial AC power, and any restrictions on the type of generator or fuel storage at the site. Page 21 of 57

22 As this is a conceptual design, the final system configuration used by OWIN will be determined by the selected vendor s design (through a Request for Proposals process). Because OWIN anticipates the use of 700 it is probable that the State will be able to partner with metropolitan areas of Oregon. This would enable OWIN to use the partnering agencies trunking systems without overbuilding. It will also give local government agencies the ability to gain wide area coverage outside of their metropolitan areas by connection to OWIN. This partnering effort could reduce the number of sites needed by OWIN and increase the coverage afforded by local governments. Local government systems typically designed to support the use of portable radios and have in-building penetration levels. OWIN is building a system that is designed to provide coverage in all areas of the state. When reaching agreements with local government, OWIN would need to be responsible for adding transmitters (not sites) to local government systems in order to account for the capacity needs of OWIN. Where local government systems may not cover well in rural areas, OWIN may be able to add sites and equipment that benefit both local government and OWIN systems The P25 trunking central control system The P25 trunking system requires a central controller to perform the critical tasks of managing and controlling the radio infrastructure. This includes performing the basic trunking operation; identifying and validating users, assigning sites and channels, and other control functions. The various manufacturers use different controller architectures to accomplish these tasks. For this reason the types and quantities of controllers used to manage the functions of their P25 trunking systems varies. Some manufacturers distribute more control to the radio sites and others keep most control in a centralized unit. The centralized control model is the best defined from a system viewpoint; therefore we will use this for the conceptual design. The conceptual OWIN system will rely on central controllers placed at two locations to support the state. FE recommends that at a minimum, central controllers be placed on either side of the Cascade Mountains to insure survivability in the case of a major natural disaster. Each of these two locations will have two controllers configured as a redundant set. This redundancy is necessary due to the importance of the controllers to keep the entire system operational. In some vendor s architectures the redundant controllers can be geographically separated allowing four separate controller locations to be supported with four non-redundant Page 22 of 57

23 controllers. Additionally some configurations may allow load sharing or emergency back-up provisions between the central controllers. The central controller locations will be determined during detailed design. The locations will need emergency power, an uninterruptible power system, sufficient climate control, and reliable connectivity to the microwave subsystem. In addition, they should have relatively easy access for service, be well secured, and be hardened against likely hazards, such as earthquake, storms, and flooding. FE recommends that the console control equipment and the interoperability matrix switch also reside at these facilities. The trunked radio equipment is typically monitored through its control system. In addition, any available status and failure alarms, such as low power, antenna system failures, etc, will be managed through the alarm system described in the microwave system design The conventional radio subsystem The OWIN conventional radio system will provide communications on channels where interoperability with agencies that do not operate on OWIN is the primary consideration. An example is the Oregon Department of Forestry, which will maintain coordination, initial attack, and fire ground tactical communications on conventional channels. This capability is required since these channels are used as a shared resource between ODF and many of their cooperators that are outside the control of the State of Oregon. These cooperators, many of them are private land owners, corporations and smaller municipalities, will require additional time to make the investments necessary to convert to trunking technology. Some ODF traffic will migrate to the P25 digital trunked operation as its capacity and wide area coverage capabilities better serve the agency. The conventional OWIN system contains two separate components to provide the infrastructure for these uses. The first component is the implementation of a unique conventional channel at each existing ODF site. These channels will serve ODF and their cooperators, just as the current ODF system does. These repeaters will replicate the existing ODF repeater system coverage. Each of these repeaters will be on an individual frequency pair in a frequency reuse plan similar to the current system. The selection of specific frequencies will fit the overall OWIN frequency plan to minimize interference. Page 23 of 57

24 The second component is the implementation of two common conventional channels at each OWIN site to serve users on a shared basis, statewide. This will create two conventional channels that will be available statewide. These conventional channel base stations will be dual mode, selectable for either digital P25 operation or analog operation. This will allow for the smooth migration from today s analog operation to conventional P25 system, and finally to the OWIN P25 trunking system. The radio base stations supporting these channels will be configured similarly to the stations supporting the OWIN trunked radio subsystem. This includes the use of antenna combining systems, IP interconnection via the OWIN microwave subsystem, primary and supplemental power systems, and monitoring and alarm systems. Provision is also made for continuation of the ODF statewide initial attack frequencies and for the ODF fire cache radio systems. The fire cache deployable systems are on statewide frequencies and are principally used on larger fire situations. The statewide conventional radio subsystem will have coverage as shown be in Exhibit erability overview map. The repeaters that will emulate the current ODF channels at will have an aggregate coverage as shown below in Exhibit ODF coverage. STATE OF OREGON Conceptual erability Mobile Talk-in Coverage (257 Sites) County Border Interstate State/County Road OWIN Candidate Site Area Covered (95% Reliability, DAQ > 3.4) Lake / Ocean Mobile Transmit Power: 40 Watts Mobile Antenna Height: 1.5 m Transmit Frequency: 154 PERCENTAGE OF STATE COVERED: 85 % File:.OREGON.conceptual.(257 Sites).m.ti jpg Exhibit 5.4 overview map Page 24 of 57

25 ODF - STATE OF OREGON - Conceptual P25 Mobile Talk-in Coverage (55 Sites) County Border Interstate State/County Road Conceptual ODF Site Area Covered (95% Reliability, DAQ > 3.4) Lake Mobile Transmit Power: 40 Watts Mobile Height: 1.5 m Transmit Frequency: 154 PERCENTAGE OF STATE COVERED: 63 % Filename: ODF.OREGON.conceptual(55Sites).P25.m.ti jpg Exhibit 5.5 ODF coverage The complement of OWIN conventional radio channels will be interfaced to the OWIN interoperability matrix switch subsystem described in Section below. This will allow the creation of communications paths between the conventional channels and the other OWIN radio subsystems The interoperability radio and switching matrix subsystems In the post-9/11, post Hurricane-Katrina era, the ability for public safety agencies to communicate with each other has created banner headlines and has come to the forefront. The keyword here is interoperability, and interoperability in the OWIN is required by HB2101. OWIN has enhanced interoperability inherent in its design and function. The interoperability radio subsystem is composed of specific, UHF, and 800 national mutual aid calling and tactical channels located at selected OWIN radio sites. OWIN has selected, UHF, and 800 national interoperability channels, to maintain statewide interoperability functions. The specific National Calling and National Tactical channels implemented at each interoperability site will depend on the communications requirements of the area that site covers. The Page 25 of 57

26 frequencies for these channels are listed in Table erability subsystem channels, below. Additional radio channels can, at sometime in the future, be included in the design of the OWIN interoperability radio subsystem. Frequency Designation Description VCALL National Calling VTAC 1 National Tactical VTAC 2 National Tactical VTAC 3 National Tactical VTAC 4 National Tactical UHF 453./ UCALL National Calling 453./ UTAC 1 National Tactical 453./ UTAC 2 National Tactical 453./ UTAC 3 National Tactical / ICALL National Calling 821/ ITAC 1 National Tactical 822/ ITAC 2 National Tactical 822/ ITAC 3 National Tactical 823/ ITAC 4 National Tactical Table erability subsystem channels The purpose of interoperable radio subsystems is to provide a common platform that will allow communications with almost any radio. Agencies throughout the State most likely have some of these channels in their radios already, and those that don t could install them depending on the specific radio band as appropriate. Agencies operating on would use the interoperability channels. Likewise, those agencies operating on UHF or 800 would install those appropriate for their radios. To maximize interoperability these radio channels will be non-trunked, but will be dual mode P25 digital and analog for greatest expandability in the future. The subsystem will initially be operated in conventional analog FM mode for compatibility with the existing non OWIN users. Based on the decision by OWIN staff, the repeater/base stations will be located at strategically selected OWIN radio sites, for a total of 584 base/repeater stations. The listing of the sites used by the OWIN Page 26 of 57

27 interoperability subsystem is detailed in Appendix A Site equipment detail attached to this report. Like the other OWIN radio subsystems, the radio base/repeater stations supporting these channels will be configured to include the use of antenna combining systems where possible, IP interconnection via the OWIN microwave subsystem, primary and supplemental power systems and monitoring and alarm systems. The interoperability radios will be connected to the interoperability matrix switch via the OWIN microwave subsystem. If desired, some of the stations could also be connected to the dispatch console subsystem. The configuration of the OWIN interoperability radio subsystem is depicted in Exhibit erability subsystem overview, below. OWIN interoperability channels OWIN conventional channels OWIN P25 trunked channels Microwave at OWIN radio site Radio site interconnections Typical OWIN radio site OWIN interoperability channels OWIN conventional channels OWIN P25 trunked channels OWIN interoperability channels OWIN conventional channels OWIN P25 trunked channels Microwave at OWIN radio site OWIN interoperability channels Radio site interconnections Typical OWIN radio site OWIN conventional channels OWIN P25 trunked channels OWIN Microwave & other types of data circuits Microwave at OWIN radio site OWIN interoperability channels Radio site interconnections Typical OWIN radio site OWIN conventional channels OWIN P25 trunked channels Microwave at OWIN radio site Radio site interconnections Typical OWIN radio site Microwave at OWIN radio site Radio site interconnections Typical OWIN radio site OWIN control site P25 system controller Control site interconnections Microwave at OWIN radio site Dispatch console controller erability matrix switch Exhibit erability subsystem overview Page 27 of 57

28 The interoperability subsystem uses a matrix switch to connect any OWIN channel to any other channel. This switching could be accomplished through a dispatch console patch, however patching the total number of channels that the OWIN system has access to, exceeds the capabilities of most console systems. For this reason an interoperability matrix switch is used to perform this function. The matrix switch equipment for this subsystem will be co-located with each OWIN trunking central controller for each part of the state. The matrix switch will be configurable by remote operator terminals that will be located at regional centers as prescribed by the State erability Executive Council (SIEC). These centers will most probably be at a city or county Public Safety Answering Point (PSAP) equipped and staffed to handle this responsibly seven days a week, 24-hours a day. Additionally, OWIN dispatch locations such as the State Police dispatch centers and the State Emergency Coordination Center (ECC) would also have control equipment for the interoperability subsystem. The matrix switch system will allow the partitioning of responsibility to ensure that each control center has full control over the resources for which they are responsible. OWIN is providing for the interoperability channel infrastructure, however, the SIEC will need to develop the governance and placement of regional control centers High speed data subsystem The installation of the high speed infrastructure is described in the Mobile Data erability Radio System Report (Deliverable 9-C). The high speed data subsystem infrastructure will consist of 700 wide bandwidth data radios located at each of the OWIN radio sites supporting the 700 portion of the P25 trunked system. These sites support the counties of the I-5 corridor and Deschutes County. Coverage will be similar to the 700 P25 Trunked systems as shown in Exhibit OWIN 700 trunked system coverage and in Appendix B. The design of the high speed data subsystem will share interface equipment with the P25 mobile data system to the greatest extent possible. This is done both as a cost saving measure, and to ensure the highest level of interoperability between these two networks. Configuration of the base station radios supporting these data channels is similar to that of the other OWIN subsystems. This includes the use of antenna combining systems, IP interconnection via the OWIN microwave Page 28 of 57

29 subsystem, primary and supplemental power systems, and monitoring and alarm systems The dispatch console and control subsystems The OWIN system needs both human and automatic control. The human control is provided at dispatch centers. The conceptual design does not change the present configuration of dispatch centers; it provides for OWIN dispatch centers to serve OSP and ODOT just as they are today. Some ODF will be served by remote console position, and others will utilize radio control stations. Similarly, as agencies join OWIN, their dispatch centers can be connected to the system either via microwave, fiber, or through the use of control station radios. The various State agencies use several types of dispatch centers, and OWIN has the ability to use all types. Two agencies use full dispatch centers, with operator consoles and dispatchers. The State Police currently has dispatch centers in Salem and Central Point. The Department of Transportation has centers in Salem, Central Point, Bend, and Portland. In addition Oregon Emergency Management (OEM) operates the State Emergency Coordination Center (ECC) in Salem. The ECC is in the same building with OSP s Northern Command Center and ODOT s Northwest Transportation Operations Center and is for this report, considered part of the same system The full centers used by OSP and ODOT require connection to the radio system by microwave or other Internet Protocol (IP) connectivity. The console positions are interfaced to the radio system by a central electronic switch; however, newer IP based designs may replace this design with data network routing equipment. This OWIN design allows for either configuration in order to not restrict any vendor from providing the best possible solution. This central electronic equipment, whether a switch or router, can be located with the console positions at each dispatch center, or it can be located at a centralized location with the console position equipment remotely connected. This configuration will allow the centers to back-up each other in the event of a failure. OWIN will use four central electronics units, one in each city having a dispatch center. Thus, an electronics unit will be located in Bend to serve the ODOT center there and one will be at Portland for the ODOT center there. In Salem and Central Point, one unit will be located in each city serving both OSP and ODOT consoles in each city. Should the state Page 29 of 57

30 move to unified dispatch centers in Salem, Medford, Bend, and Pendleton, this same design concept will apply. Each dispatch center will also be equipped with control station radios providing emergency back-up communications in case the consoles or console subsystem should have a failure. The Oregon Department of Forestry dispatches from their area offices located throughout the State. Dispatching is by the use of control station radios or wireline remote controls from these offices. There are 3 offices requiring nine control stations at each office. Control stations are simply base station radios that communicate with the radio system just as mobiles do and may be desk top radios or radios that are remotely controlled from dispatch consoles. The control station has features and talkgroups similar to mobile units. Some ODF dispatch locations will be equipped with remote control console positions to allow the integration of additional radio systems. A summary of the various dispatch control locations and the number of dispatch positions provided is detailed in Table 5.3 Agency dispatch locations. AGENCY LOCATION POSITIONS STATUS OSP Salem 22 Existing OSP Central Point 16 Existing DOT Salem 7 Existing DOT Central Point 3 Existing DOT Bend 4 Existing DOT Portland 5 Existing Table 5.3 Agency dispatch locations Exhibit 5.7 Console subsystem overview, provides an abstract of the various ways that OWIN can provide dispatch and control access to the radio subsystems. As other agencies join the OWIN system, their operations can use any of these types of dispatch subsystems. Page 30 of 57

31 Central controllers & interoperability switches Centralized dispatch console system OWIN Microwave and Radio Network Control Station radios Console control equipment Console control equipment To dispatch consoles Remote dispatch console system Control station dispatch console system Exhibit 5.7 Console subsystem overview P25 integrated low speed data subsystem The portions of the radio subsystems that adhere to the P25 standards, including the trunked subsystem and the conventional repeater channels, have the capability to carry low speed data. This can be used to provide some mobile data services to field units. This low speed data capability is integrated into the entire P25 voice radio network. The data rides right alongside of voice and can be used anywhere a voice radio can be used. The network uses the same base stations and repeaters for voice or data, and the same mobile radio can often support both modes. This capability Page 31 of 57

32 is inherent with a P25 system and only requires the installation of data interfaces in the infrastructure and in the vehicles and the implementation of mobile data applications. P25 data is relatively low speed when compared to Internet-type data speeds currently in use provided by digital subscriber line (DSL), optical fiber, or cable television providers. P25 data is carried at a raw data rate of 9600 bits per second (bps) with a throughput of between 4800 to 7200 bps. While this speed sounds very low, the majority of public safety mobile data systems today operate successfully on networks between 4.8 kbps and 19.2 kbps. This type of low speed data is capable of providing access to forms and providing basic database lookup from vehicular mounted mobile data devices. Many mission critical applications currently are supported in thousands of agencies across the nation by similar low speed data. The P25 low speed data will be provided statewide with approximately the same coverage as the primary P25 voice radio system as shown in Exhibit OWIN trunked system coverage, Exhibit OWIN 700 trunked system coverage and in Appendix B. This design provides 86% coverage of the State for P25 data services. Detailed coverage prediction maps are included in the Core Sites report references previously. This data will be available on any of the subsystems using the P25 protocols including both and 700 ; trunked subsystems, and on conventional channels where appropriate. Data will not be available on analog subsystems. The P25 integrated low speed data subsystem shares the transmitters and channels of both the P25 and the P voice subsystems. This subsystem uses signaling inherent in the P25 standards to provide up to a 9,600 bps data rate to mobile equipment. The P25 voice radio subsystems, trunked and conventional, will include the equipment necessary to make this data stream available. Each of the vendors designs their equipment for this type of data operation differently. Some require a data controller at each radio site while others require one installed in each radio station. While the quantities are different, so is the complexity and costs of the equipment. Generally, the cost of the equipment taken as whole is close enough that using any major vendor s design will allow a fairly accurate estimation of the cost of any vendor s system. To make use of this capability, data equipment also needs to be installed in the mobile units. Page 32 of 57

33 In addition to the equipment required to add data capabilities to the radio channels, there is equipment required to manage the overall P25 mobile data system. This is made up of one or more radio network controllers (RNCs), and one or more radio network gateways (RNGs). These may be independent hardware platforms or may be software modules running on a common hardware system. The output of the mobile data subsystem is provided to a router or switch. This router or switch acts as the interface point between the mobile data system and the computer systems that it is servicing. This conceptual design is based upon having one mobile data switch or router located at each of the trunking central controllers Department of Corrections radio subsystem The Oregon Department of Corrections (DOC) will be retaining its existing in-facility radio systems. For that reason, the DOC on-site radio systems are not included in the earlier discussion of OWIN subsystems. The DOC uses primarily UHF repeater systems except for two facilities that use 800 EDACS trunked systems. These systems are designed specifically to provide a high level of coverage inside and very near each of the DOC facilities. DOC will operate on OWIN for prisoner transportation and work crew communications. To accommodate the DOC s special requirements, an OWIN trunked control station will be deployed in the control centers of each of the prison facilities. This configuration will allow each DOC facility to communicate to other prison facilities, transportation vehicles, work crews, other offices and to OSP when necessary. Existing DOC in-facility portables can have the interoperability channels installed if desired. The DOC has expressed the desire to migrate additional facilities to 700 or 800 trunking operation. These systems could become subsystems to OWIN through the implementation of P25 technology, rather than the continuing with the proprietary trunking technology currently in use. Additionally, the same is true of the two facilities currently using M/A-COM s EDACS proprietary technology, providing they are migrated to P25 technology. Page 33 of 57

34 Subscriber radio equipment Although, not a formal sub-system of OWIN, the subscriber radio equipment is discussed here to highlight its role as an integral component. The subscriber radio equipment will be made up of several different configurations of mobile and portable radio equipment depending on the agency and users needs, and the area of operation. The most sophisticated configuration would be a vehicle equipped with mobile transceivers for both the and 700 band to allow full operation in either coverage area. This configuration would also include a portable radio for either the or the 700 band, and a vehicular mounted repeater on the same band. The repeater would allow the radio user to use the portable radio as an extension of their mobile radio when they are away from the vehicle. This repeater would be designed to maintain the full P25 feature set, including trunking, unit ID and encryption. The portable radio would be equipped with a vehicular charger, so it can be charged and ready for use in the vehicle at all times. A less sophisticated field radio equipment configuration includes the use of only one mobile radio, relying on either the portable radio on the other band, or interoperability channels on the primary band, for service when out of the primary coverage area. Additional configurations are similar to those mentioned above, and may or may not include the option of the vehicular repeater system. In units not equipped for both bands, the specific band of the radios will depend on the area of operation. For units operating primarily in the coverage area, a 700 portable radio will communicate through a 700 vehicular repeater connected to the mobile radio. For units operating primarily in the 700 area, the reverse will be used. A portable radio will communicate through a vehicular repeater connected to the 700 mobile radio. A vehicular charger for the portable radio can be equipped with a microphone, speaker, and antenna. This enables the portable radio to be used much like a mobile radio while it is in the vehicle and being charged. FE recommends that all mobile and portable radios be trunking capable, dual mode digital P25 and analog units. This assures the greatest level of compatibility with future radio systems available today. Many systems, such as most federal agencies and many other agencies are already migrating to P25 operation in the band. Page 34 of 57

35 5.2 Description of OWIN operation Operation of the OWIN systems as described in this conceptual design is simple for every user: for the dispatcher, for the local agency dispatchers, for the mobile user, for interagency coordination, and for mobile data operation. For dispatching of OWIN users such as OSP and ODOT, there will be new consoles. Initially, the consoles will have their current radio channels and operation will be similar to today s operation. When all units are cut-over to the new OWIN operation using P25 trunking, the dispatching will operate much like today s dispatching, except that instead of controlling radio channels, the dispatcher will be selecting trunking talkgroups. The field units in the talkgroup may be on or 700 or both and they may be anywhere in the State, and still all of the units within that talkgroup will hear and can transmit messages to the group. The dispatcher can patch together talkgroups to connect different groups together, connecting personnel from different agencies. To the dispatcher, selecting talkgroups is no different than selecting radio channels. During the time when cutover is taking place, the dispatcher can have old radio channels and new talkgroups appear on his or her console. This will allow the dispatcher to patch a channel to a talkgroup, to continue dispatching of units not yet converted to the new system as well as those already migrated to the new system. Dispatching will be no more complicated than when dispatching on the existing channels. Oregon DOC transportation and work crew communications will operate on OWIN in the same manner as OSP and ODOT. DOC will continue to meet the unique needs of their on-site and in-facility communications through the continued use their existing systems. These systems can be interfaced to OWIN for interoperability or if they choose to migrate to the P25 OWIN system. For local agencies, dispatching can occur just like the OSP/ODOT dispatch operation described above. These agencies may use control stations, in which case the dispatcher simply selects the talkgroup of interest and joins a group as a mobile radio would. Mobile and portable radio users will select the talkgroup they need and when there is traffic for that talkgroup, all the radios user are gathered together on the group and can communicate. These units may be on or 700 or both and still communicate as a group. The mobiles will automatically roam from site to site. Therefore, the operation is simple: select the talkgroup as they currently select the radio channel. Mobile and Page 35 of 57

36 portable radios will have many features, including the ability to belong to more than one talkgroup and to scan multiple talkgroups. For the agencies making use of the conventional channels (primarily ODF), the users will have to select the specific channel assigned for their specific area just as they do today. This is similar to current operation, and is a fundamental attribute of conventional operation. This added complexity of operation allows for the ODF and other agencies that are required to communicate with users outside of the state agencies who may not have access to P25 trunked equipment. Additionally, conventional operation allows slightly easier use of simplex, direct unit-to-unit communications often associated with tactical fireground operations. However, FE recommends that ODF migrate as much of their operations as possible to the OWIN system and use the conventional channels as a means to intercommunicate with outside agencies. Interagency coordination can occur in various manners. OWIN system users can communicate with other OWIN agencies by changing over to a talkgroup of the other agency or by meeting others on a common interoperability talkgroup. The decision on how this actually happens is dependent upon the governance that OWIN will put into place for the use of the system. The interoperability subsystem could be used to bridge other OWIN or interoperability channels directly to a talkgroup. A dispatcher uses the remote terminal of the interoperability switch system to connect the desired talkgroups and/or channels together, allowing field units to change to that talkgroup or channel and communicate without regard as to the system each party is using. Dispatchers also have the ability to patch a talkgroup to another talkgroup or channel to provide interoperability. If mobile data is used, whether low speed P25 on or 700 or high speed 700- subsystems, operation is usually via a computer keyboard and video monitor, similar to a notebook computer. The complexity of the operation is only dependant on the complexity of the applications deployed. The low speed data is sufficient for data forms, database lookups, and many other typical public safety mobile data applications. The speed of this portion of the network is considered fairly slow for real time and web based applications. High speed data applications may go beyond the keyboard/monitor interface. The data input may be via a card reader for driver license scanning, a video camera, or a finger print scanner. The applications that Page 36 of 57

37 could be implemented are almost limitless. Many popular application concepts are listed in the Mobile Data erability Radio System Report (Deliverable 9-C). 5.3 Satisfaction of design criteria The OWIN radio system fully meets all of the design criteria listed in Section 4.1. It is P25 compliant with operation in the and 700 dual bands. It provides more radio coverage due to increased number of sites. Trunking improves efficiency of channel use and therefore more talk-paths and increased capacity. Two of the systems use all of the core radio sites; these are the P25 trunked system, and the 2 channel conventional system. The 700 data and statewide interoperability system use a subset of the OWIN core radio sites. The implementation of the additional conventional channel at ODF sites allows ODF to use a conventional radio system when and where required, and provides P25 capabilities in digital mode statewide. OWIN provides an interface with existing DOC radio systems and uses includes the interoperability matrix switch with remote control positions to provide the greatest degree of interagency communications. The P25 system automatically provides low speed mobile data capabilities, and the use of the high speed 700 system provides for new and more complicated applications. As innovative and intricate as the system may be, it still provides simple user operation. 5.4 Gap Analysis (Deliverable 11-A) OWIN will be a leap forward in public safety communications for the State of Oregon. The old radio system being replaced was designed and implemented using technology before the personal computer became a household word. The operational gaps identified in the Needs Analysis Report centered around four issues; Coverage Channel availability Ease of use System reliability Page 37 of 57

38 5.4.1 Coverage The conceptual design of the OWIN significantly improves coverage over the existing systems in every county in the State. The conceptual design provides 86% coverage of the State for P25 voice and data services, which is significantly better than the current coverage, which varies by state agency and ranges from 44% to 75% statewide. In addition, OWIN is designed to provide a well engineered, robust voice and data network, providing coverage in every county that meets or exceeds the coverage of the best of the three State systems today. Detailed coverage prediction maps are included in the Core Sites report references previously Channel availability Today s systems require manual selection of channels based on the unit s location and the available channels in that area. Only a few of channels are available in any given area, requiring users to wait until radio traffic clears. OWIN provides multiple talk-paths, and if a priority situation occurs, its traffic on one talkgroup can be prioritized to gain channel access in an orderly manner as other traffic is handled in other talk-groups. This occurs transparently to the users even though they all share the same set of pooled radio channels Ease of use Today s systems require the knowledge of the unit s location to make the appropriate manual selection of channels. This complicates use, as each and every field radio user must comprehend the radio system well enough to make the correct selections without interfering with other users. OWIN provides automatic channel selection and automatic roaming of units, so they will not have to know where they are and what channel to use. P25 features bring other automatic capabilities not currently available. These include unit identification, emergency button, private conversation, talkgroup scanning, secure communications, low speed data communications, and automatic call return. Page 38 of 57

39 A minor short fall is the use of the hybrid and 700, because there is not complete seamless roaming between the area and the 700 areas. Ideally, this could be resolved by the use of either dual band radios, which currently are not available, or a single band used statewide. A single band solution is not practical because there are not enough frequencies available in the band and a Statewide 700 system would require an excessive number of sites, and be prohibitively expensive. However, by including and a 700 radio (one as a portable radio and the other as a mobile) and a vehicular repeater, both bands are usable by mobiles that cross the band boundaries to provide very near seamless operation System reliability The existing State of Oregon systems have several reliability issues. While the general age of the equipment varies greatly, with the oldest being well beyond its typical lifespan, some of the equipment is much newer. However, even the system comprised of newer equipment does not make use of newer design philosophies including redundancy and failure mitigation. These systems continue to rely on physical infrastructure, buildings and towers that are unsuitable for the electronics they support. Ancillary system such as security and maintenance alarms are insufficient or nonexistent. OWIN has taken a ground-up approach to reliability. The physical infrastructure will be replaced or improved to a level that can support the electronic systems reliably. The individual subsystems are designed to eliminate single points of failure, and to incorporate the required redundancy. The system of systems approach provides multiple methods of communications. And finally, the system incorporates not just security and failure alarms, but sufficient operational monitoring to enable the appropriate levels of preventative maintenance to be conducted. These multiple layers of reliability enhancements build upon each other to provide OWIN with the highest level of reliability available in a system of this type. Page 39 of 57

40 6.0 Next steps This project will continue with the preparation of an implementation plan and a business case study. The implementation plan will break out costs and identify spending cycles planned for the implementation, while the business case will create a persuasive discussion why it is important to the future of all Oregonians that OWIN be implemented. Page 40 of 57

41 Appendix A. Site equipment detail The following pages are tables showing the sites by name and the equipment quantities in the following columns: Site Name The name of the radio site Operational Region Region of the State of Oregon that the site is located Simulcast Group Identification of which simulcast group the site belongs Total Number of Trunked Channels Number of trunked channels at the site Simulcast Channels Number of simulcast channels at the site Non-Simulcast Channels Number of channels not simulcast Trunked 700 Channels Number of 700 channels at the site Conventional Channels Number of non-trunked channels at the site ODF Sites Base radios at existing ODF sites for tactical, etc. Channels number of interoperability channels UHF Channels number of UHF interoperability channels 800 Channels number of 800 interoperability channels 700 Data Channels number of 700 high speed wide band channels Page 41 of 57

42 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 ODF Sites UHF 800 Agency Plains West-Central 1 N/A Aldrich Mtn Central 2 N/A Anthony Lakes Grant North-East 3 N/A Arrowwood Point Central 4 N/A Ashland Mtn (Day Wireless Medford 5 N/A Augspurger (NW Natural) NW-Central 6 Group Bachelor West-Central 7 N/A Bailey Mtn SW-Central 8 Group Baker Ridge ATT Central-East 9 Group Bald Mtn Klamath SW-Central 10 N/A Bald Mtn - Polk Salem 11 N/A Bald Mtn West Salem 12 N/A Bald Ridge Roseburg 13 Group Baldy Butte Roseburg 14 Group Bear Mtn Eugene 15 N/A Convent South- Central 16 N/A Beaty s Butte Beaver Ridge (USFS) Central-East 17 Group Bennett Butte South Coast 18 Group Benton 02 Eugene 19 N/A Benton 03 Salem 20 N/A Benton 04 Eugene 21 N/A Benton 05 Central Coast 22 N/A Benton 06 Central Coast 23 N/A Benton 07 Eugene 24 N/A Data Page 42 of 57

43 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 ODF Sites UHF 800 Convent Benton 08 Salem 25 N/A Benton 09 Salem 26 N/A Black Butte (Burns) Central-East 27 N/A Black Cap South- Central 28 Group Black Mtn North-Central 29 Group Blue Mtn (Basque) South-East 30 N/A Bolivar Mtn Roseburg 31 Group Bone Point North-Central 32 N/A Bosley Butte South Coast 33 Group Buck Mtn Eugene 34 N/A Burns Butte Central 35 N/A Buxton Lookout Portland 36 N/A Cabbage Hill ODOT North-Central 37 N/A Canyon Mtn Medford 38 N/A Cape Lookout L190 North Coast 39 N/A Cape Perpetua Central Coast 40 N/A Carpenterville South Coast 41 Group Cedar NW-Central 42 N/A Chehalem Mtn Portland 43 N/A Chilcoot Mtn Roseburg 44 N/A Clackamas 01 Salem 45 N/A Clackamas 02 Salem 46 N/A Clatsop 02 North Coast 47 N/A Coffin Mtn (ODF) Salem 48 N/A Columbia 01 Portland 49 N/A Columbia 02 Portland 50 N/A Columbia 03 North Coast 51 N/A Data Page 43 of 57

44 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 Convent ODF Sites UHF 800 Columbia 04 Portland 52 N/A Columbia 05 Portland 53 N/A Columbia 06 Portland 54 N/A Columbia 07 Portland 55 N/A Columbia 08 Portland 56 N/A Columbia 09 Portland 57 N/A Columbia 10 North Coast 58 N/A Columbia 11 North Coast 59 N/A Columbia 12 Portland 60 N/A Columbia 13 Portland 61 N/A Columbia 14 Portland 62 N/A Columbia Hills (WA) NW-Central 63 N/A Condon NW-Central 64 N/A Coombs Canyon North-Central 65 N/A Cottonwood Mtn Central-East 66 N/A Courtney Butte North-East 67 N/A Crater Lake SW-Central 68 N/A Criterion Summit NW-Central 69 Group Dead Indian Mtn SW-Central 70 N/A Dean Mtn Roseburg 71 Group Devils Ridge North-East 72 N/A Devine Ridge Central 73 N/A Dixie Butte Central 74 Group Doane Creek Salem 75 N/A Dodson Roseburg 76 N/A Edson Butte South Coast 77 Group Elk Mtn North-East 78 N/A Data Page 44 of 57

45 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 Convent ODF Sites UHF 800 Elkhorn Central 79 Group Elks Peak Roseburg 80 Group Euchre Mtn Central Coast 81 N/A Fairview Peak Roseburg 82 N/A Fall Mtn Central 83 N/A FCC Site 11 North-East 84 N/A FCC Site 127 South- Central 85 Group FCC Site Roseburg 86 N/A FCC Site 230 Medford 87 N/A FCC Site 57 Central 88 N/A FCC Site 64 Central 89 Group FCC-BS- CLACKAMAS Portland 90 N/A Fiddler Mtn Medford 91 N/A Fielder Medford 92 N/A Fill Site - Cinnamon Butte SW-Central 93 Group Fill Site - Elkton Roseburg 94 N/A Fish Rim (Adel Remote) South- Central 95 Group Gardiner Hill Roseburg 96 Group Glass Butte Central 97 N/A Gleason Butte North-Central 98 Group Glenada Eugene 99 Group Glendale Remote Medford 100 N/A Goat Mtn Portland 101 N/A Goodwin Peak Eugene 102 Group Gordan Ridge NW-Central 103 N/A Data Page 45 of 57

46 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 ODF Sites UHF 800 Convent Green Mtn MF&S Site Portland 104 N/A Green Peter (Bald Peter) Salem 105 N/A Grizzly Mtn West-Central 106 N/A Grizzly Peak South- Central 107 N/A Grizzly West South Coast 108 Group Halls Point Medford 109 N/A Halls Ridge Salem 110 N/A Hamaker Mtn SW-Central 111 N/A Harbor Hill South Coast 112 Group Hebo Mtn North Coast 113 N/A High Heaven Salem 114 N/A Hogback SW-Central 115 N/A Hood River NW-Central 116 Group Hoodoo Butte West-Central 117 N/A Horeb Mtn Salem 118 N/A Howard Butte North-East 119 N/A Hulse Ranch NW-Central 120 Group Iron Mtn South Coast 121 N/A Isabelle Mtn Medford 122 N/A Ivers Peak Roseburg 123 Group Josephine 01 Medford 124 N/A Josephine 02 Medford 125 N/A Josephine 03 Medford 126 N/A Josephine 04 Medford 127 N/A Kent Elevator NW-Central 128 Group Keyes Summit Central 129 N/A Data Page 46 of 57

47 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 Convent ODF Sites UHF 800 Ladd Canyon North-East 130 N/A Lane 01 Eugene 131 N/A Lane 02 Eugene 132 N/A Lane 03 Eugene 133 N/A Lane 04 Central Coast 134 N/A Lane 05 Eugene 135 N/A Lane 06 Eugene 136 N/A Lane 07 Roseburg 137 N/A Lane 08 Eugene 138 N/A Lane 10 Eugene 139 N/A Lime Hill Central-East 140 N/A Linn 01 Salem 141 N/A Linn 02 Eugene 142 N/A Linn 03 Eugene 143 N/A Linn 04 Eugene 144 N/A Linn 05 Salem 145 N/A Linn 06 Salem 146 N/A Madison North-Central 147 Group Mahogany South-East 148 N/A Manzanita (Round Top) Medford 149 N/A Marion 01 Salem 150 N/A Marion 02 Salem 151 N/A Marion 03 Salem 152 N/A Marys Peak Salem 153 N/A Megler Mtn North Coast 154 N/A Meissner Portland 155 N/A Middle Mtn NW-Central 156 Group Data Page 47 of 57

48 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 Convent ODF Sites UHF 800 Monument Peak (From Phase 1) Central-East 157 N/A Mount Yoncalla Roseburg 158 N/A Mt Defiance NW-Central 159 Group Mt Emily (FCC) North-East 160 N/A Mt Fanny North-East 161 N/A Mt Hagan Eugene 162 N/A Mt Hood (Timberline) Portland 163 Group Mt Howard North-East 164 N/A Mt Nebo Eugene 165 N/A Mt Weston North-Central 166 N/A Mult 01 Portland 167 N/A Mult 02 Portland 168 N/A Neahkahnie Mtn North Coast 169 N/A Nicolai Mtn (ODF) North Coast 170 N/A Noti (Badger Mtn) Eugene 171 Group Onion Mtn Medford 172 N/A Owyhee Reservoir Central-East 173 N/A Peavine West Central 174 N/A Pelican Butte SW-Central 175 N/A Pharmacy Hill South-East 176 N/A Pilot Butte Comm Site West-Central 177 N/A Pine Grove NW-Central 178 N/A Pine Mtn West-Central 179 N/A Pisgah Mtn Central 180 N/A Polk 01 Salem 181 N/A Polk 02 Salem 182 N/A Data Page 48 of 57

49 Appendix A Site Equipment List (continued) Site Name Page 49 of 57 Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 ODF Sites UHF 800 Convent Polk 03 Salem 183 N/A Polk 04 Salem 184 N/A Polk 05 Salem 185 N/A Polk 10 Salem 186 N/A Port Orford South Coast 187 Group Powell Butte West-Central 188 N/A Prairie Mtn Eugene 189 N/A Pueblo Mtn South-East 190 N/A Rancheria Rock NW-Central 191 Group Rector Ridge North Coast 192 N/A Red Butte Roseburg 193 N/A Red Mtn North-East 194 Group Roman Nose Eugene 195 Group Roosevelt NW-Central 196 N/A Round Pass South- Central 197 N/A Roxy Ann Medford 198 N/A Saddlebag Mtn Salem 199 N/A Scott Mtn - Douglas Roseburg 200 N/A Scott Mtn (Linn) Eugene 201 N/A Sexton Mtn Medford 202 N/A Shaniko NW-Central 203 Group Sheep Ridge North-East 204 N/A Signal Tree (Kenyon Mtn) Roseburg 205 Group Sillusi Butte OSP North-Central 206 N/A Skamania Portland 207 N/A Slide Creek Roseburg 208 Group Smith Mtn North-East 209 N/A Data

50 Appendix A Site Equipment List (continued) Site Name Page 50 of 57 Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 Convent ODF Sites UHF 800 Snow Peak Salem 210 N/A Snowboard NW-Central 211 Group Soda Mtn Medford 212 N/A South Saddle Portland 213 N/A Spout Springs North-East 214 N/A Stacker NW-Central 215 Group Starveout Medford 216 N/A Steens Mtn (FCC) South-East 217 N/A Stephenson West-Central 218 N/A Sturgill Mtn Central-East 219 N/A Sugarpine Butte West-Central 220 N/A Summit Point (Solar Site North-East 221 Group Table Mtn Roseburg 222 N/A Table Mtn (Newport) Central Coast 223 N/A Tallowbox Medford 224 N/A Tamarack Central 225 N/A Tillamook Head North Coast 226 N/A Tiller Remote Roseburg 227 N/A Tygh Ridge NW-Central 228 Group Walker Mtn SW-Central 229 N/A Walker Point Eugene 230 Group Wampus West-Central 231 N/A Wasco Butte NW-Central 232 Group Washington 01 Portland 233 N/A Washington 02 North Coast 234 N/A Washington 03 North Coast 235 N/A Washington 04 North Coast 236 N/A Data

51 Appendix A Site Equipment List (continued) Site Name Operational Region Count Simulcast Group # of Trnk Chan Simul cast Non- Simul cast Trnk 700 Convent ODF Sites UHF 800 Washington 05 Portland 237 N/A Washington 06 Portland 238 N/A Washington 11 Portland 239 N/A Washington 12 Portland 240 N/A Washington 13 Portland 241 N/A Welch Butte SW-Central 242 Group West Zigzag LO Portland 243 Group Whalehead Mtn (FCC 241) Portland 244 N/A Wickiup (Clatsop 01) North Coast 245 N/A Wilkenson North-Central 246 Group Wilson River Portland 247 N/A Wolf Mtn SW-Central 248 N/A Yainax Butte SW-Central 249 N/A Yamhill 01 Salem 250 N/A Yamhill 02 Portland 251 N/A Yamhill 03 Portland 252 N/A Yamhill 04 Salem 253 N/A Yamhill 10 Salem 254 N/A Yamhill 11 Portland 255 N/A Yaquina Head Central Coast 256 N/A Yellow Butte Roseburg 257 N/A Total Data Page 51 of 57

52 Appendix B. Coverage maps The following pages are larger version of the maps shown earlier in the report trunked coverage 700 trunked coverage OWIN combined trunked coverage Statewide conventional coverage (257 sites) ODF conventional coverage (55 sites) Page 52 of 57

53 Appendix B Coverage maps (continued) STATE OF OREGON Conceptual Mobile Talk-in Coverage (257 Total Sites, 136 ) County Border Interstate State/County Road Candidate Site Dual-Band Site Area Covered (95% Reliability, DAQ > 3.4) Lake / Ocean Mobile Transmit Power: 40 Watts Mobile Antenna Height: 1.5 m Transmit Frequency: 154 PERCENTAGE OF STATE COVERED: 80 % File: OWIN.OREGON.conceptual.P25(257Sites) jpg Page 53 of 57

54 Appendix B Coverage maps (continued) STATE OF OREGON Conceptual 700 Mobile Talk-in Coverage (257 Total Sites, ) County Border Interstate State/County Road 700 Site Dual-Band Site Area Covered (95% Reliability, DAQ > 3.4) Lake / Ocean Mobile Transmit Power: 35 Watts Mobile Antenna Height: 1.5 m Transmit Frequency: 800 PERCENTAGE OF STATE COVERED: 20 % File: OWIN.OREGON.conceptual.P25(257Sites) jpg Page 54 of 57

55 Appendix B Coverage maps (continued) STATE OF OREGON OWIN Hybrid -700 Mobile Talk-In Coverage (257 Sites) County Border Interstate State/County Road Candidate Site 700 Site Dual-Band Site Area Covered (95% Reliability, DAQ > 3.4) Lake / Ocean Mobile Transmit Power: 40 Watts Transmit Frequency: Transmit Power: 35 Watts 700 Transmit Frequency: Mobile Antenna Height: 1.5 m PERCENTAGE OF STATE COVERED: 86 % Page 55 of 57

56 Appendix B Coverage maps (continued) STATE OF OREGON Conceptual Conventional Mobile Talk -in Coverage (257 Sites) County Border Interstate State/County Road OWIN Candidate Site Area Covered (95% Reliability, DAQ > 3.4) Lake / Ocean Mobile Transmit Power: 40 Watts Mobile Antenna Height: 1.5 m Transmit Frequency: 154 PERCENTAGE OF STATE COVERED: 85 % File:.OREGON.conceptual.(257 Sites). m.ti jpg Page 56 of 57

57 Appendix B Coverage maps (continued) ODF - STATE OF OREGON - Conceptual P25 Mobile Talk-in Coverage (55 Sites) County Border Interstate State/County Road Conceptual ODF Site Area Covered (95% Reliability, DAQ > 3.4) Lake Mobile Transmit Power: 40 Watts Mobile Height: 1.5 m Transmit Frequency: 154 PERCENTAGE OF STATE COVERED: 63 % Filename: ODF.OREGON.conceptual(55Sites).P25.m.ti jpg Page 57 of 57