WO1997036255A1

WO1997036255A1 - System and method for integrating planning and operations information

Info

Publication number: WO1997036255A1
Application number: PCT/US1997/006083
Authority: WO
Inventors: David Michael Zumwalt; Charles Daniel Staggs
Original assignee: Glenayre Electronics, Inc.
Priority date: 1996-03-25
Filing date: 1997-03-19
Publication date: 1997-10-02
Also published as: AU2457797A

Abstract

A system for integrating planning and operations data relating to an organization's (10) infrastructure (14) is provided. The system includes a planning system (22) for maintaining design data on the infrastructure's design. The system also includes an operations system (26) for maintaining operations data on the infrastructure's operation. An integrated process and application (IPA) (32) integrates the planning data and operations data. The IPA (32) includes a planning system IPA agent (42) for accessing the planning data from the planning system (22) and an operations system IPA agent (40) for accessing the operations data from the operations system (26). The planning system (22) can receive operations data from the operations system (26) via the IPA (32) and the operations system (26) can receive planning data from the planning system (22) via the IPA (32).

Description

SYSTEM AND METHOD FOR INTEGRATING PLANNING AND OPERATIONS INFORMATION

TECHNICAL FIELD OF THE INVENTION

This invention relates in general to the field of management information systems, and more particularly to a system and method for integrating planning and operations information for a network having a wireless element .

BACKGROUND OF THE INVENTION

Management information systems (MIS) have in recent years received widespread use and acceptance in managing the information associated with an organization. An organization may have several groups within it that make up the overall organization. For example, an organization may include a sales group, a marketing group, a customer-care group, an engineering group, and an operations group. Each of the groups may be referred to as having a horizontal relationship with respect to one another. Each group performs the duties and responsibilities assigned to it. Typically, each group within an organization will develop and use a MIS that allows the group to satisfy its purpose. Unfortunately, the independent development of each MIS may result in several MISs that do not provide for the sharing of information between the different systems and organizations. Therefore, for example, the customer-care group creates its MIS for dealing with customers, and likewise the sales and marketing group or groups develop their own MIS. Thus, while the MIS developed for each group generally meets the needs for that group, it does not provide for "sharing" of data and information between groups. When each of the groups reports its performance to the organization's management based on its MIS, this may result in a "microscopic" presentation of the overall organization's performance. An organization's management, however, requires a

"macroscopic" view of the organization and therefore may find it difficult to use the information from the various groups in best managing the organization. For example, if the sales group reports record sales revenue, but the customer-support group reports excessive customer returns or complaints, then a problem within the organization may exist. If management relies on just one of the group's information and data a skewed view of the organization may result. The owners and operators of telecommunication networks may also suffer from having separate groups working on separate and sometimes incompatible MIS and other computer systems. Because of the complexities of deploying and operating a telecommunications network, the owners and operators of such networks have come to rely extensively on computer systems for both designing and operating the networks. Like most organizations, a paradigm has persisted in telecommunications organizations where the "planning" group and its computer tools is separate from the "operations" group. This separation has resulted in the development of computer systems used by each group that are not generally compatible with one another and also precludes the "sharing" of information and data between groups. The owners of telecommunications networks having a wireless element have also followed this paradigm. Traditional network management and operational support systems (OSS) , e . g. , billing and customer-care, for so-called wireless networks (those having a wireless element) have been designed for use in fixed networks, i.e., those in which the connection between any two points can be specifically described. In wireless networks, although the location of a wireless terminal unit can be generally determined, the radio path or air interface between the wireless unit and the serving base station cannot be treated deterministically. The very nature of wireless communications suggest unfettered mobility. The usage characteristics of any given wireless unit cannot be precisely anticipated and thus are generally treated statistically. As a result, the use of traditional network management and OSS with wireless networks has amounted to little more than the application of those systems to the fixed elements of the network. This approach neglects the importance of integrating the management of the air interface into the system and also leaves the network manager with little information on the impact the air interface has on the network' s performance.

The traditional management approach has fostered the emergence of separate network operations and planning groups within the wireless system operator's organization. This may lead to a compartmentalization of tasks, responsibilities, and reporting structure. These all tend to lengthen the network operator's response time to events occurring in, or peripherally involving, the air interface portion of the wireless network. In turn, this may impact overall system quality as perceived by the wireless customer.

Additionally, this segregation of information and systems between planning and operations groups leaves a wireless network's manager with an incomplete picture of how best to maintain or expand the network. Since the planning group does not have access to the operations group and its information, and likewise, the operations group does not have access to the planning group and its information, this disjoinder of groups, systems, and infrastructure may result in a network that typically does not operate at and prevents the network manager from achieving maximum performance of its network and best use its capital .

SUMMARY OF THE INVENTION

Therefore, a need has arisen for a system and method for integrating planning and operations information.

In accordance with the present invention, a system and method is provided that substantially eliminates or reduces disadvantages and problems associated with the previously developed management information systems. In particular, the present invention provides a system and method for integrating planning and operations information for an organization. The present invention is particularly well-suited for integrating planning and operations information for a network having a wireless element .

One aspect of the present invention provides a system for integrating planning and operations data relating to an organization's infrastructure. The system includes a planning system that maintains design data on the infrastructure's design. The system also includes an operations system that maintains operations data on the infrastructure's operation. An integrated process and application (IPA) integrates the planning data and operations data. The IPA includes a planning system IPA agent for accessing the planning data from the planning system and an operations system IPA agent for accessing the operations data from the operations system. The planning system receives operations data from the operations system via the IPA and the operations system receives planning data from the planning system via the IPA. Another aspect of the present invention provides a system for integrating data associated with a wireless network. This data includes planning data from a network planning system that maintains design data on the network's design including data on the air interface for the wireless network. The data associated with the wireless network also includes network operations data from a network operations system that maintains operations data on the network's operation. The system also includes an integrated process and application (IPA) for integrating the network planning data and network operations data. The IPA includes a network planning system IPA agent for accessing the network planning data from the network planning system and a network operations system IPA agent for accessing the network operations data from the network operations system. The network planning system receives network operations data from the network operations system via the IPA and the network operations system receives network planning data from the network planning system via the IPA.

Yet another aspect of the present invention provides a method for integrating data associated with a wireless network. This data includes network planning data from a network planning system that maintains design data on the network's design including data on the air interface for the wireless network. The data associated with the wireless network also includes network operations data from a network operations system that maintains operations data on the network's operation. The method includes providing an integrated process and application (IPA) for integrating the network planning data and network operations data. The method further includes accessing the network planning data from the network planning system through a network planing IPA agent and accessing the network operations data from the network operations system through a network operations system IPA agent. The method also includes transmitting network operations data to the network planning system via the IPA and transmitting network planing data to the network operations system via the IPA.

The present invention provides several technical advantages. One technical advantage of the present invention is that it provides for integrating planning and operations information. The present invention is especially well-suited for use with a network having a wireless element. This allows a manager and operator of the wireless network to use both planning and operations information to more efficiently manage the wireless network.

Another technical advantage of the present invention is the ability to visually display the network and the impact of various elements in the network to several performance factors for the network. Performance factors that may be visualized include, but are not limited to, capacity, revenue, and coverage associated with an element or portion of the network.

An additional technical advantage of the present invention is that it provides an analysis tool for identifying underlying root causes of events that may affect the network.

Another technical advantage of the present invention is that it provides a tool for performing trend analysis on the network that can be used to suggest timetables for action as well as prioritize activities that affect the network.

Yet another technical advantage of the present invention is that it provides for both fully dynamic reprovisioning of the elements in the network as well as audited reprovisioning of the elements in the network. An additional technical advantage of the present invention is that it provides a tool for analyzing the impact of changes or corrective action to a wireless network so as to minimize the impact to the ongoing operations of the network. BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings in which like reference numbers indicate like features and wherein:

FIGURE 1 illustrates the integration of planning the operations information for an organization embodying concepts of the present invention; FIGURE 2 shows the integration of planning and operations information for a network having a wireless element in accordance with the present invention;

FIGURE 3 provides a class diagram for the network planning and operations functions in FIGURE 2 in accordance with the present invention;

FIGURE 4 illustrates a platform representation of a method for integrating planning and operations information for a network having a wireless element in accordance with the present invention,- FIGURE 5A is an object diagram for analyzing dropped calls in a wireless network in accordance with the present invention;

FIGURES 5B and 5C are graphical representations for the analysis in FIGURE 5A; FIGURE 6A is an object diagram for analyzing the revenue associated with a cell in a wireless network in accordance with the present invention;

FIGURE 6B illustrates a graphical representation of the analysis in FIGURE 6A; FIGURE 7A provides an object diagram for depicting customer impact associated with a problem in the wireless network in accordance with the present invention; and

FIGURE 7B provides an exemplary depiction for the output of the object diagram in FIGURE 7A.

DETAILED DESCRIPTION OF THE INVENTION Preferred embodiments of the present invention are illustrated in the FIGURES, like numerals being used to refer to like and corresponding parts of the various drawings. FIGURE 1 shows organization 10 employing the present invention to integrate planning and operations information relating to organization 10. Management 12 of organization 10 typically has a mission or goal for organization 10. Management 12 obtains the necessary infrastructure 14 to support and provide the appropriate goods and services to customers 16 of organization 10 in achieving the mission of organization 10. It is noted that "customers" is not intended in a limiting sense and covers both external customers to and internal customers within an organization. The present invention may be used to support various types of infrastructure 14 and include, for example but are not limited to, petroleum refineries, copier services, call centers, and telecommunication service providers, including both wire- based and "wireless" telecommunications services.

Organization 10 may include several groups, and in the example depicted in Figure 1 for organization 10 are planning group 18 and operations group 20. Typically, planning and operations groups develop independently from one another such that a disjoiner of information, services, and systems between each group results. Each group may employ a computer syst-m or systems for meeting the goals and responsibilities set for it by management 12. Planning group 18, for example, may use planning system 22 for designing infrastructure 14 required to satisfy the needs of customers 16 of organization 10. Planning system 22 is generally one of many types of computer systems that execute both proprietary and non- proprietary software programs that allow planning group 18 to perform its duties. Planning system 22 is typically accessed by one or more system planners in planning group 18 via a planning system workstation or workstations, which are collectively represented as planning system workstation 24 in FIGURE 1. Using planning system workstation 24 and with a set of assumptions on the customer's needs, available capital, and the desired level of goods and services to be provided by organization 10, planning group 18 using planning system 22 can design infrastructure 14 for organization 10 to meet its mission. Typically, once planning group 18 completes its design of infrastructure 14, its system plan, in the form of data and other information, is provided to operations group 20 to obtain the necessary equipment and deploy infrastructure 14 as designed by planning system 22. It is noted that the terms data and information are used interchangeably throughout the remainder of this specification to refer to all forms of electronic information exchanged or generated when using computer systems.

Once infrastructure 14 has been put in place the control and management of infrastructure 14 is typically made the responsibility of operations group 20. Operations group 20 uses an operations system 26 for monitoring the performance of infrastructure 14. Operations system 26 is typically on one or more computer systems executing proprietary or non-proprietary software programs that allow infrastructure 14 to be automatically monitored from one or more remote locations. An operator or operators in operations group 20 in, for example, an "operations center", sitting at operations system workstation or workstations, which are collectively represented by operations workstation 28 in FIGURE 1, can generally monitor the current and historical performance of infrastructure 14 via workstation 28. Operations system 26 stores the data and information relating to infrastructure 14 so that the performance of infrastructure 14 over a period of time or at any instant may be ascertained through the use of operations system 26 and operations system workstation 28. The individual elements of infrastructure 14 are typically monitored through the use of sensors so that their performance, and in particular their failure, may be detected and reported via operations system 26 to operations group 20. As shown in FIGURE 1 the planning group and operations group are typically separate groups within organization 10 as indicated by dashed line 30. Because of perceived differences between the missions of the planning and operations group there has not been any need to share information and data between the two groups. This has resulted in planning systems 22 and operations system 26 that are generally not compatible with one another. The data structures and messaging protocols, for example, in each system may not be compatible with one another and may also prevent the "sharing" of data between systems and groups. Unfortunately, this division of responsibilities may leave management 12 receiving separate sets of data, which oftentimes are difficult to correlate with one another and sometimes present different pictures of the organization's performance. Additionally, because of the disjoinder of the groups and their systems, duplication of tasks between the planning and operations groups often results. This leaves management 12 with a sometimes difficult task of resolving the differences between the planning and operations information so that organization 10 may be guided to operating at desirable performance levels. The present invention for integrating planning and operations information solves the problem of having separate planning and operations functions in organization 10 as described in discussion relating to FIGURE 1 to this point. In accordance with the present invention, an integrated process and application (IPA) is provided for integrating planning and operations information. As shown in the example of FIGURE 1 depicting organization 10, IPA 32 provides for the integration of information from the various systems used by organization 10 so that organization 10 may be managed more efficiently. IPA 32 shown in FIGURE 1 provides for the exchange of information and data among planning system 22 and operations system 26. This exchange of information may also include other groups beyond planning group 18 and operations group 20, which in the example of the present invention shown in FIGURE 1 includes strategic decision support system (SDSS) 34. It is also noted that while FIGURE 1 shows IPA 32 interfacing with all three depicted systems used by organization 10, that the present invention is not limited to a single IPA for use with the organization's systems. Multiple IPAs encompassing different systems may be used without deviating from the spirit and scope of the present invention.

SDSS 34 represents all the other groups within organization 10 and includes, for example, the sales group, customer-care group, and accounting groups of organization 10. Since management 12 generally uses the so-called "bottom line" for an organization as the measure of the organization's performance, it often uses SDSS 34 and its view 36 of organization 10 as a gauge of the organization's performance. SDSS workstation 38 couples to SDSS 34 and can also share information with planning system 22 and operations system 26 using IPA 32. This integration of operations, planning, and SDSS information provides a truer representation of the functions and operations of organization 10.

IPA 32 may be implemented in one or more computer systems executing software programs that allow for the sharing of data and information among otherwise separate computer systems used by organization 10. The computer programs of IPA 32 may be developed using standard programming techniques, for example, object-oriented programming. Additional detail on several examples for programs in IPA 32 will be provided hereinafter. IPA 32 incorporates an open architecture system which allows IPA 32 to interface with many systems, e.g., planning system 22, operations system 26, and SDSS 34. This may be accomplished through the use of industry standards and published programmable interfaces for each system.

An IPA accomplishes the integration of information through the use of IPA agents. As shown in FIGURE 1, each computer system in organization 10 couples to an IPA agent. Operations IPA agent 40 couples to operations system 26, planning system IPA agent 42 couples to planning system 22, and SDSS IPA agent 44 couples to SDSS 34. The IPA agents provide a "filter" or "gateway" for the data that is maintained by each of the systems so that the other systems within the organization may use that data. The present invention recognizes that the data structure or format for the data in operations system 26 may not be compatible with the data and information structure of planning system 22 and SDSS 34, and vice versa. IPA 32 uses the IPA agents to put the data from each of these systems in a format that can be easily used by the other computer systems within organization 10. The IPA agents can also recognize when requests to its associated system develop into a pattern and will poll the associated system for the necessary data in anticipation of those requests. For example, if SDSS 34 requests revenue data from operations system 26 on the first of every calendar month, then operations system IPA agent 40 can prepare that data prior to the scheduled request . This may help minimize any invasiveness of the IPA agent on its associated system. Additionally, it is noted that IPA 32 as shown in FIGURE 1 represents one of several IPAs that may be used to integrate information within an organization. Additional IPAs may be used to interface with these systems as well as other systems used by organization 10. This is represented by reference number 46 is FIGURE 1. Additionally, IPA 32 may be used as a vehicle to upgrade the IPA agents that are a part of IPA 32 as well as to upgrade the systems interfaced by IPA 32. Such upgrades include, for example, software upgrades to the IPA agents and systems associated with the agents.

By providing for the exchange of information from each of the systems in organization 10, management 12 may obtain better understanding of the needs of customers 16 and infrastructure 14 required to meet those current needs as well as future needs. This enhanced understanding allows management 12 to prioritize changes and improvements to organization 10 so that capital improvements are made with a view to the impact to the organization's bottom line. This allows management 12 to more effectively meet its mission while making optimum use of the available resources to organization 10. FIGURE 2 shows the integration of planning and operations information in accordance with the concepts of the present invention for a network having a wireless element. "Wireless" as it is used in describing the present invention refers to the RF or air interface used for transmitting information and data via radio frequency waves. While the present invention may be used for many types of systems as described in discussions relating to FIGURE 1 above, one embodiment of the present invention may be used to integrate planning and operations information for a wireless network.

As shown in FIGURE 2, wireless service provider 48 contains several functional groups similar to organization 10 in FIGURE 1. Wireless service provider 48 may include geographic group 49 that maintains and operates geographic information system (GIS) 50 that contains data on geographic region or regions 52 in which a wireless network may be deployed. GIS 50 products are commercially available from many sources. In fact, the U.S. government is one possible source for the data that may be the basis of GIS 50. Also, GIS 50 is available from the assignee of the present application, CNET, Inc. Other sources for GIS 50 include a product under the trade-name ARC/Info from Environmental Systems Research Institute, Inc. GIS 50 and its associated information 52 are generally used as part of or in the planning of a wireless network.

Wireless service provider 48 in FIGURE 2 also includes network management group 53 that maintains and operates an operations system, hereinafter referred to as network management system (NMS) 54, which maintains data on and operation of wireless network infrastructure 56. NMS 54 in FIGURE 2 generally corresponds to operations system 26 in FIGURE 1. Network infrastructure 56 typically includes, for example, the type and location of switches, base stations, and antennas for the wireless network. There are many suitable NMS that may be used in implementing the present invention. The assignee of the present inventor, CNET, Inc., has available a NMS product by the trade-name BOS™. The present invention is not, however, limited to operation with the BOS™ NMS. NMS products under the trade-name NetExpert from Objective Systems Integrators, Inc. and TNM from AT&T may also be suitable for use with the present invention.

Wireless service provider 48 may also include network planning group 55 that operates and maintains network planning system (NPS) 58. NPS 58 typically includes RF information data 60, which includes the signal strength, coverage, attenuation, and other RF information that is pertinent to the deployment of a wireless network. There are many suitable NPS that may be used in implementing the present invention. The assignee of the present invention, CNET, Inc., has available a NPS product by the trade-name WiNGS™. The present invention is not, however, limited to use with the WiNGS™ NPS. NPS products under the trade-name PlaNET from Mobile Systems International, trade-names ANET and Cellcad from LCC, L.L.C., and Wizard from TEC Cellular may also be suitable for use with the present invention. It is noted that while existing GIS, NMS, and NPS products for wireless networks have been commercially available for some time, there has been no attempt to integrate the information available from each of these systems for use with the other systems.

Each of the separate systems depicted in FIGURE 2 may also include a workstation or workstations for its access and use. NPS 58 has NPS workstation 62, NMS 54 has NMS workstation 64, and GIS 50 has GIS workstation 66. It is noted that while a single workstation is depicted for each system in FIGURE 2 that each may represent multiple workstations for use with their respective systems. Typically, there has been no sharing of information between GIS 50, and NMS 54, and NPS 58. The groups responsible for maintaining and operating their associated system may use the appropriate workstation to provide the required services. Since there is no sharing of information between the different systems, however, it makes it very difficult to respond to problems that may occur in the wireless network, anticipate the future needs of the wireless network, and to prioritize the expenditure of capital on the wireless network. In accordance with the present invention, one or more IPAs are provided for integrating the information available through the various systems used by wireless service providers so that the operators of wireless networks can more effectively allocate their limited resources as well as respond more effectively to problems that may arise during the operation of the network. IPA 68 shown in FIGURE 2 is representative of the one or more IPAs that may be used in accordance with the present invention.

Similar to organization 10 in FIGURE 1, wireless service provider 48 as shown in FIGURE 2 may have SDSS 70 for performing similar functions as described above for SDSS 34, e.g., sales, marketing, customer-care, and accounting. SDSS 70 includes SDSS workstation 72. SDSS 70 provides view 73 of the wireless source provider's organization that generally focuses on the "bottom-line" of the organization, but is not helpful in guiding the organization to its optimum performance.

As previously described in discussions relating to FIGURE 1, the incorporation of an IPA to an organization's computer systems helps break down the barriers to the sharing of data from separate systems to provide an enhanced view of the organization's performance. An example of the application of an IPA to the computer systems used to design and maintain a wireless network follows.

IPA 68 in FIGURE 2, which is an example of one of the many IPAs that may be used by wireless service provider 48, includes several IPA agents that are located at each of the different systems within system 48. IPA 68 accordingly includes GIS IPA agent 74 coupled to GIS 50, NMS IPA agent 76 coupled to NMS 54, NPS IPA agent 78 coupled to NPS 58, and SDSS IPA agent 80 coupled to SDSS 70. As previously described for the IPA agents in FIGURE 1, IPA agents 74, 76, 78, and 80 provide a gateway or filter for the information available at any one of the systems so that information may be shared and used by any one of the systems associated with the wireless network.

IPA 68 in FIGURE 2 can be used to provide several functions and meets several objectives that are desirable for wireless service provider 48. IPA 68 provides for observation and characterization of events that affect the performance and operation of the wireless network. IPA 68 provides for depiction and display of network events. For example, if a given antenna in network infrastructure 56 fails, IPA 68 identifies, for example, the coverage, interference, and capacity implications of the failed antenna site. IPA 68 can also aid in determining the availability and acceptability of alternate or secondary servicing sites for the failed antenna in network infrastructure 56. Additionally, IPA 68 can be used to determine a probable cause for a given event. IPA 68 can correlate a given failure to a root cause by looking beyond individual alarms and identifying their underlying root causes. Using IPA 68, the treatment of probable causes for network failures is more effective because the air interface as represented by RF information 60 may be used in analyzing a given failure or failures. For example, system utilization may be affected by weather and other local conditions. A "no traffic" indication on an interconnect link for an element in network infrastructure 56 may be misinterpreted as a problem in the link when monitored by a fixed network monitoring system alone. Where a more complete analysis inclusive of the air interface from RF information 60 may show that the problem lies in subscriber usage patterns not the system.

Additionally, IPA 68 provides for trend analysis as well as performance projections. Analysis of performance data from NMS 54 for the wireless network collected over a period of time may give rise to identifying system performance trends. Trend analysis of the performance data can suggest a timetable for action as well as prioritization. For example, when the existing capacity in a given cell site for network infrastructure 56 will exhaust can be projected based on past traffic levels and subscriber growth. Subscriber growth interaction may be obtained from GIS 50 and the existing capabilities available in NPS 58. IPA 68 can use both sets of data along with data from NMS 54 to determine when network infrastructure 56 needs to be upgraded. IPA 68 in FIGURE 2 can also provide for timely response to network events . Using either NMS 54 or SDSS 70 as the monitoring system, IPA 68 can support fully dynamic reprovisioning. IPA 68 can be used to automatically post configuration changes or corrections to network infrastructure 56 based on events or trends observed manually or through software via NMS 54. Alternatively, NMS 54 or SDSS 70 using IPA 68 can provide audited reprovisioning with work order generation. Similar to fully dynamic reprovisioning, audited reprovisioning generates reprovisioning instructions in an outline or work order form. This allows a service technician to audit or manually implement the modification suggested by a dynamic reprovisioning feature . Additionally, IPAs in accordance with the present invention can integrate planning data with real-time operations data to present a dynamic depiction of the network's operation including information on the air interface portion of the network. For example, combining planned coverage information from NPS 58 with current usage data from NMS 54 may provide wireless service provider 48 with useful information on how to best modify his RF coverage to meet the network's current usage. While the present invention provides many new desirable capabilities to a wireless network operator, a few examples, not intended to limit the spirit and scope of the present invention, may be helpful in demonstrating the advantages of the present invention. An example of the capability available with the present invention is that the network planning system depictions, e.g., coverage maps and signal maps, from NPS 58 can be delivered to network management group 53. IPA 68 can operate in either the background or foreground on NMS workstation 64, which is primarily used to interact with NMS 54. When an alarm or measured event is triggered in NMS 54, which directly involves network infrastructure 56, for example a base station, IPA 68 monitors and observes the alarm or measured event and initiates appropriate directions to NPS IPA agent 78. Generally, these directions to NPS IPA agent 78 are in the form of "display geographically one or more RF characteristics of the alarmed base station and its immediate neighbors as identified by NMS 54." NPS IPA agent 78 translates these directions into a form readily processed by NPS 58. Alternatively, NPS IPA agent 78 may directly access any of a number of stored databases normally managed by NPS 58 for which a standardized access mechanism is available. Once the request is fulfilled by the NPS IPA agent 78, or stored results are available, NPS IPA agent 78 notifies IPA 68, which then further processes the results and directs the results as appropriate to NMS workstation 64. This mechanism allows the network operator to visualize the impact of a failed base station on the operation of the network from an RF prospective. IPA 68 can be configured to perform a variety of other tasks. By way of another example and not intended to limit the spirit and scope of the present invention, IPA 68 processes information from NPS 58 through NPS IPA agent 78 to provide additional information to support decisions made by NMS group 53. By measuring the difference between normal and failed coverage for an alarmed site, and then mapping the difference over traffic statistics stored in NMS 54 or demographic information 52 stored in GIS 50, IPA 68 can report anticipated revenue loss, unserved traffic, adjusted grade of service during the outage, or other meaningful statistics. By obtaining coverage information for base stations that neighbor the alarm site, IPA 68 can direct NMS 54 through NMS IPA agent 76 to retune the neighboring sites in network infrastructure 56 to provide temporary service during the alarm site's outage. Additionally, the present invention can be used to deliver network switch configuration databases to NPS group 55. IPA 68 can operate in the background or foreground of NPS workstation 62, which is primarily used to interact with NPS 58. When an application running on NPS 58 requires an updated, accurate database of network infrastructure 56, IPA 68 monitors NPS 58 and initiates appropriate directions to NMS IPA agent 76. Generally, these directions are in the form of "provide base station location and configuration data from RF infrastructure 56 for the system currently undergoing analysis by NPS 58." The NMS IPA agent 76 translates these directions into a form readily processed by NMS 54. Alternatively, the NMS IPA agent 76 directly accesses any of a number of stored databases normally managed by NMS 54 for which a standardized access mechanism is available. Once the request is fulfilled by NMS IPA agent 76 or stored results are available, NMS IPA agent 76 notifies NPS 58 that then further processes the results in or directs the results as appropriate to NPS workstation 62. This mechanism allows network planning group 55 to be assured the site location and configuration data for network infrastructure 56 used for planning purposes matches the actual database stored in the switch.

In another example of the present invention, IPA 68 can process the results retrieved from NMS 54 to provide additional decision support to network planning group 55. These include, for example, measuring the difference between the previous and current site database for network infrastructure 56. IPA 68 can summarize changes in coverage, revenue generation, or traffic capacity for each affected site. In addition, IPA 68 can simply call out any changes between the network plan and actual build allowing network planning group 55 to confirm that the changes were appropriate. Also, by using the base station information retrieved from NMS 54 through its agent, IPA 68 can direct NPS 58 through its agent to predictively optimize the configuration of the wireless network.

FIGURE 3 illustrates a class diagram for an IPA in accordance with the present invention. As previously noted, IPAs in accordance with the present invention may be developed using standard programming techniques. FIGURE 3 provides an example of a class diagram that can be converted by one skilled in the art of object-oriented computer programming into a computer program or programs for implementing the functions described for an IPA in accordance with the present invention. IPA 82 in FIGURE 3 represents a subset of IPA 68 shown in FIGURE 2. In the example of FIGURE 3, portions of GIS 50 have been incorporated into NPS 58. IPA 82 integrates the network planning and operations data from NMS 54 and NPS 58 for wireless service provider 48 in FIGURE 2. It is noted that IPA 82 in FIGURE 3 does not include SDSS 70 as did IPA 68 in FIGURE 2. As previously noted, an IPA in accordance with the present invention may access many different systems and is not limited to those depicted and described in the FIGURES. Also, an IPA in accordance with the present invention can be used with or on existing computer systems and does not require separate computer platforms and systems. On the planning side of IPA 82 are multiple RF

2planners 84 coupled to IPA 82, and more particularly to NPS IPA clients 86. NPS IPA clients 86 include, for example, planning terminal class 88, demographic map class 90, coverage map class 92, and signal map class 94. RF planner 84 typically interfaces with planning terminal class 88 and uses planning terminal class 88 as represented by circle 96 to make use of the capabilities of IPA 82. (The usage relationship of the classes in FIGURE 3 will be represented by the use of circle 96.)

Additionally, on the planning side of IPA 82 are NPS IPA servers 98. NPS IPA servers 98 include, for example, demographic coordinator server class 100, antenna class 102, RF coordinator server class 104, and subscriber class 106. It is noted that the objects within NPS IPA clients 86 and NPS IPA servers 98 are not limited to those shown in FIGURE 3, but these objects are provided by way of an example only. NPS IPA servers 98 serve NPS IPA clients 86, including providing information and data to and from NPS IPA clients 86. Also, on the planning side of IPA 82 is NPS IPA agent 78 previously described in discussions relating to FIGURE 2. As previously stated, agent 78 provides a filter or gateway for information to and from NPS 58 to IPA 82.

On the operations side of IPA 82 are multiple network operators 110 coupled to NMS IPA clients 112. NMS IPA clients 112 may include several objects and examples of classes for these objects are shown in FIGURE 3. Coverage map class 114, trouble map class 116, operations terminal class 118, and traffic map class 120 may all be included in NMS IPA clients 112. Typically, network operator 110 accesses data from NMS IPA clients 112 via operations terminal class 118.

Additionally, IPA 82 includes NMS IPA servers 122. In the example of IPA 82 shown in FIGURE 3, NMS IPA servers 122 include, for example, network element class 124, site class 126, alarm bell class 128, and traffic coordinator server class 130. NMS IPA servers 122 provide appropriate information to and from NMS IPA clients 112 as illustrated in FIGURE 3. Also, on the operations side of IPA 82 is NMS IPA agent 76 from FIGURE 2, which provides a gateway or filter for data to and from NMS 54 as previously described. Additionally, as shown in FIGURE 3, NPS IPA servers 98 and NMS IPA servers 122 couple with each other to provide for sharing information and data between servers. Also, NPS IPA clients 86 may access information to and from NMS IPA servers 122, and NMS IPA clients 112 may access information to and from NPS IPA servers 98. IPA 82, therefore, provides for the sharing of information across the planning and management systems that was not previously available because of stand-alone and separate planning and management systems. Additional detail on the objects in FIGURE 3 will be provided in discussions relating to FIGURE 4 hereinafter.

FIGURE 4 illustrates a hardware embodiment for IPA 82 of FIGURE 3 embodying concepts of the present invention. As previously described, network operator 110 couples to a NMS client computer 132 that supports NMS IPA clients 112. FIGURE 4 shows additional NMS IPA clients above those shown in FIGURE 3. NMS IPA clients 112 include coverage map class 114 that correlates coverage data for each antennae in network infrastructure 56 to a geographic reference. Trouble map class 116 provides a correlation of trouble items or events in network infrastructure 56 to a geographical reference. Traffic map class 120 essentially correlates traffic in network infrastructure 56 to a geographical reference. The network map class provides a correlation of network infrastructure 56 to a geographical reference. The alarm list class provides a list of network infrastructure 56 events that should trigger an alarm in NMS 54. The traffic report class provides information on traffic flow within network infrastructure 56. The trouble report class includes additional information on the data that makes up trouble map 116. The call report class contains individual detail data that makes up the traffic report class. The revenue report class provides data on the revenue being generated with network infrastructure 56. NMS client computer 132 couples via network 134 to NMS server computer 136 and to NPS server computer 140. Network 134 may be embodied in a local area network (LAN) , wide area network (WAN) , SONET, token ring, Ethernet, and many other suitable network configurations for coupling several computers together.

NMS server computer 136 supports NMS IPA servers 122 as previously described in discussions relating to FIGURE 3. The objects in NMS IPA servers 122 shown in FIGURE 4 provide a larger set of those that may be available on NMS server computer 136 than shown in FIGURE 3. Traffic coordinator server class 130 provides information on the routing of traffic within network infrastructure 56. The communications network class maintains information on the relationships between the network elements in network infrastructure 56. Network element class 124 keeps track of the status, information, the location, and characteristics of a network element. For example, network element class 124 would include information on the site where the element is located, the capacity of the element, and the current traffic on the element. The call class keeps track of all the calls being processed through network infrastructure 56. Alarm bell class 128 provides an indication of a given alarm in network infrastructure 56. Site class 126 maintains information on the configuration of network infrastructure 56 and software that is located at each site. A trouble ticket class provides information on events that have occurred in network infrastructure 56 that may require corrective action or analysis. The network message class keeps track of the communication between elements in network infrastructure 56.

NMS server computer 136 may also have on it NMS IPA agent 76 as was previously described in discussions relating to FIGURES 2 and 3. NMS IPA agent 76 provides access to and from the information stored within NMS 54. NMS 54 typically contains several databases and a few are shown in FIGURE 4, including; call detail record database, alarm logs database, traffic database, and service record database. On the planning side of FIGURE 4, RF planner 84 couples to NPS client computer 138. NPS client computer 138 supports NPS IPA clients 86. The depiction of NPS IPA clients 86 shown in FIGURE 4 illustrates additional clients above those shown in FIGURE 3. Signal map class 94 contains the signal level from various antennas within network infrastructure 56. The terrain map class provides the physical terrain around each antennae. The structure map class contains basic information on where structures, buildings, and other objects are located. Demographic map class 90 contains information on where people are located and other various attributes about the population. The attenuation map class provides the attenuation effect on the signals generated at each antennae. The contour map class describes contours surrounding the areas. Coverage map class 92 is similar to coverage map class 114 in NMS IPA clients 112. The revenue report class, traffic map class, and call report class are as previously described in discussion relating to NMS IPA clients 112. As shown in FIGURE 4, NPS client computer 138 couples to NPS server computer 140 and NMS server computer 136 via network 134. NPS server computer 140 contains within it NPS IPA servers 98 as was previously described in discussions relating to FIGURE 3. NPS IPA server 98 includes RF coordinator server class, demographic coordinator server class, antenna class, subscriber class, structure class, terrain class, and road class. RF coordinator server class 104 maintains the RF information for the wireless network and generates appropriate representations of that RF information.

Demographic coordinator server class 100 maintains the demographic information for the wireless network and generates appropriate representations of that demographic information. Antenna class 102 maintains information on each antenna in the network. Subscriber class 106 contains information on the customers, e . g. , billing and usage information for a customer. The structures class contains information on the structures in and around the wireless network. The terrain class maintains information on the terrain in and around the wireless network. The roads class maintains information on the roads in and around the wireless network.

In this embodiment, NPS IPA server 98 includes the information typically found in GIS 50 shown in FIGURE 2. NPS server computer 140 also contains within it NPS IPA agent 78 that provides a gateway or filter to and from NPS 58. NPS 58 typically contains several databases including, for example; a terrain database, a geographic database, a demographic database, an antennae database, and a structure database. It is noted that IPAs in accordance with the present invention are not limited to the hardware configuration shown in FIGURE 4. In one embodiment of the present invention, client computers 132 and 138 may be embodied in personal computers (PC) , while server computers 136 and 140 are embodied in UNIX™-based workstations.

Alternatively, in another embodiment of the present invention, NMS client computer 132, NMS server computer 136, NPS client computer 138, and NPS server computer 140 would all be located on a single computer. Additionally, when embodied in separate computers, NMS client computer

132 can access information to and from either NMS server computer 136 or NPS server computer 140 via network 134. Also in this configuration, NPS client computer 138 can access information through network 134 to and from NMS server computer 136 and NPS server computer 140. The IPA structure of the present invention provides several technical advantages and allows for integrating planning and operations information so that a network containing a wireless element can be more efficiently managed. Integration of this information provides owners and operators of wireless networks access to information and in a form that was not previously available. The formatting of this information generally provides a graphical representation of the effect of certain elements used in the system. The IPA allows the network manager to understand the costs associated with a particular network event, e . g. , losing a cell site, or other factors that may be important to the network manager. By way of an example, and not intended to limit the spirit and scope of the present invention, three examples of the operation of an IPA in accordance with the present invention and the benefits of integrating planning and operations information for a wireless network follow. These three examples include dropped calls analysis, revenue coverage map analysis, and customer impact location analysis.

FIGURE 5A illustrates an object diagram for analysis of the first example problem - dropped calls in the wireless network. As shown in FIGURE 5A, analyst 142 may be sitting at any of the workstations associated with IPA 68 or 82. In this example, analyst 142 has decided to analyze dropped calls in network infrastructure 56 using IPA 68. As previously noted, NMS 54 collects data on dropped calls, but this data alone may not be sufficient to highlight a recurring problem with the network. By accessing the other systems available to wireless service provider 48, a root cause for the dropped calls may be identified. The first part of the dropped calls analysis depicted in FIGURE 5A involves obtaining the dropped call data collected by NMS 54. Proceeding from analyst 142, information on the dropped calls between two given dates is requested via traffic coordinator 130 in NMS IPA servers 122. Traffic coordinator 130 obtains this information through NMS IPA agent 76 coupled to NMS 54. Using the dates of interest, NMS IPA agent 76 can retrieve the appropriate data from NMS 54. It is noted that call data from NMS 54 may also be retrieved in real¬ time as the calls are processed through the network. This allows an IPA in accordance with the presentation to provide a dynamic view of the operation of the network. As previously noted, NMS IPA agent 76 can read the data provided by NMS 54 and put it in proper format for use for generating the desired dropped call report. Once the dropped call data is obtained by NMS IPA agent 76 from

NMS 54, it is used in generating dropped call report 144. This raw data on dropped calls alone may in and of itself not indicate a trend for the dropped calls.

One additional form of analysis of the dropped call data that may be performed in accordance with the present invention is to analyze the dropped calls as a function of the calls' duration. IPA 68 will facilitate this analysis by obtaining the duration information for each dropped call. Analyst 142 can generate such a report with dropped call report 144. Dropped call report 144 gets the call duration data for each call from call object 146.

FIGURE 5B shows an example of a graphical representation for dropped call report 144 including call data by duration or length. Graph 148 in FIGURE 5B has call duration along the X-axis, while the total number of calls is on the left-hand Y-axis and the dropped call percentage is represented on the right-hand Y-axis. The drop rate for all calls is represented by line 150 in graph 148. Graph 148 shows that for the shortest calls having a duration of less than 30 seconds, that the drop rate is approximately 2%. As the duration of the call increases to over 360 seconds, the drop rate increases to approximately 3%. This indicates that the longer the call the more likely the call is to be dropped. Wireless service provider 48 may find this information helpful in formulating marketing literature and warranty provisions for its customers.

Using an IPA in accordance with the teachings of the present invention, additional analysis of the dropped call problem is possible. For example, the type of equipment being used by the customer, and particularly the telephone manufacturer, may also affect the dropped call rate. NMS 54 may not, however, contain information on the subscriber's telephone, so it may be necessary to go to SDSS 70 for data on the caller's telephone manufacturer. This additional analysis is illustrated in the remainder of FIGURE 5A and is depicted in FIGURE 5C.

In FIGURE 5A in order to display dropped calls by the telephone manufacturer, dropped call report 144 needs additional data from SDSS 70. The type of telephone used by the caller is typically stored in a database associated with the sales group of wireless service provider 48. In the example of FIGURE 5A this data is found in SDSS 70. As shown in FIGURE 5A, the data on the caller's telephone manufacturer happens to be accessed via two paths. First, dropped call report 144 can access the revenue associated with each customer via subscriber object 154, which also is built via SDSS IPA agent 80 using data from SDSS 70. Once this revenue information is obtained, then dropped call report 144 will access the subscriber's telephone manufacturer information. To do so, dropped call report 144 can access cellular telephone object 152, which contains the information on the type of telephone manufacturer used by the caller. Cellular telephone object 152 is also built via SDSS IPA agent 80, which gets the appropriate data from SDSS 70. Dropped call report 144 can then display the dropped calls by manufacturer as shown in FIGURE 5C.

FIGURE 5C shows graph 156 having the manufacturer on the X-axis, the total calls on the left-hand Y-axis, and the dropped call percentage on the right-hand Y-axis. Also shown in FIGURE 5C is the average dropped call rate, which is slightly less than 2% as represented by line 158. The call volume for each manufacturer is illustrated in bar-graph form. Also, the drop rate for each manufacturer is illustrated by an "X" above each manufacturer.

Presenting dropped call report 144 in this way, it becomes obvious that manufacturer 1 handles the majority of calls and has a drop rate that is below the average drop rate. In contrast, manufacturer 4 handles a small number of calls and also has a drop rate that is significantly above the average drop rate. This information may be helpful to wireless service provider 48 in deciding which manufacturer's telephone to possibly "bundle" with its services. Bundling an inexpensive telephone having a high drop rate may result in customer complaints that will affect the revenue of wireless service provider 48. This information is therefore very helpful to service provider 48 in analyzing dropped calls .

FIGURE 6A shows an object diagram for developing a revenue coverage map using an IPA in accordance with the teachings of the present invention. Such analyses of the revenue associated with each site in network infrastructure 56 may be helpful to wireless service provider 48 in prioritizing responses to problems that arise in the network's operation. As shown in FIGURE 6A, analyst 142 decides to analyze the revenue associated with each site in network infrastructure 56. The first step in this analysis is to retrieve the calls for a period of time from NMS 54. Retrieving calls from NMS 54 was previously described in discussions relating to FIGURE 5A. Traffic coordinator server 130 gets the calls and some of the call data via NMS IPA agent 76 that couples to NMS 54. The call data in NMS 54 also contains information that can be used to generate revenue data for each site in network infrastructure 56. Alternatively, the call information from NMS 54 may be retrieved by the IPA in real-time so that a dynamic representation of the revenue being generated by the network at any one point in time can be depicted and analyzed.

In order to correlate the revenue data to each site in network infrastructure 56, the network's configuration as maintained by NPS 58 must be accessed. Therefore, analyst 142 uses NPS IPA 82 to gather the appropriate information from the NMS 58. To complete revenue report 160 containing revenue data in a geographic map, revenue information for the calls processed with network infrastructure 56 must be obtained from NMS 54. This data is available through call object 146. The revenue must be correlated to the configuration of the network, which is stored in NPS 58. Revenue report 160 accesses coverage map 114 via RF coordinator 104, which use NPS IPA agent 78 to get the appropriate coverage data from NPS 58. Revenue report 160 then uses coverage map 114 and call object 146 to provide a color coded revenue coverage map. An example of such a map is shown in FIGURE 6B.

FIGURE 6B shows exemplary revenue coverage map 162 showing revenue for each site in network infrastructure 56. The base station for each site is indicated by reference number 161. Revenue coverage map 162 includes high revenue sites 163, 164, 165, and 166. Revenue coverage map 162 also depicts marginal revenue sites 167, 168, 169, 170, 171, and 172 as shown in FIGURE 6B. All the remaining sites in map 162 are low revenue sites and are represented collectively as reference number 174, with the noted exception of low revenue site 176.

Revenue coverage map 162 in FIGURE 6B provides a graphical representation to wireless services provider 48 on where the revenue is being generated by network infrastructure 56. This information may be very helpful to provider 48 in prioritizing its resources. For example, if site 163 and site 172 were both to experience a problem, then provider 48 would be best served by fixing site 163 before site 172 because site 163 provides more revenue. Additionally, map 162 illustrates that site 166 is somewhat distant from the other high revenue sites in network infrastructure 56. Provider 48 should be aware of this and may possibly co-locate resources near site 166 for maintaining that site.

Additionally, low revenue site 176 is separately identified as a low revenue site because it is surrounded by three high revenue sites and one moderate revenue site. This may indicate that site 176 requires some special tuning or adjustments or that the sites surrounding it may require adjustment. The low revenue associated with site 176 as compared to its surrounding sites may be an indication that some network adjustments are required. By combining revenue data from NMS 54 and coverage data from NPS 58, wireless service provider 48 can quickly see the performance of each site in network infrastructure 56. This allows provider 48 to allocate his resources and respond to events that affect the network more efficiently. FIGURES 7A and 7B illustrate customer impact location analysis using an IPA in accordance with the utility of the present invention. This analysis is used to review anticipated customer impact with respect to customer location when a problem occurs in the wireless network. FIGURES 7A and 7B and discussions relating thereto provide an example of how using an IPA the integration of planning and operations data can be used to anticipate the impact of a network event to the wireless service provider's customers. The following example demonstrates how the present invention may be used to highlight the effect of network events to the network' s subscribers.

FIGURE 7A shows object diagram 178. Network operator 110 wishes to be notified on a geographically- related map when an alarm goes off in network infrastructure 56. Initially network operator 110 using, for example, NMS workstation 64 activates trouble map 116 telling it to watch for certain alarms in network infrastructure 56. Trouble map 116 is generally located in NMS IPA clients 112. Trouble map 116 registers with the appropriate network element 124 in NMS IPA servers 122 that it is to be notified when alarms in network infrastructure 56 are triggered. Members of network management group 53 are then free to attend to other tasks. At some future time, an element in network infrastructure 56 represented by network element 124 in NMS IPS servers 122 may encounter a problem causing alarm bell 128 to register. This, in turn, causes notification to be sent to trouble map 116 in NMS IPA clients 112 that an alarm has occurred. Trouble map 116 asks network element 124 for its site location in network infrastructure 56 so that it can provide network operator 110 with information on the problem via operations terminal 118. This alarm information would be stored in a database managed by NMS 54, e . g. , the alarm bell on NMS server computer 136 in FIGURE 4, and accessed by NMS IPA agent 76. Also, trouble map 116 will ask site 126 that has experienced the alarm where the site is geographically located. This information could be stored in a database managed either by NMS 54 or NPS 58 and accessed by the appropriate IPA agent. Once trouble map 116 has determined the location, a display to network operator 110 including both the coverage and the traffic that are affected by the problem may be displayed. In order to create this display, trouble map 116 queries RF coordinator server 104 for coverage map 114 around the location of the failed network element and site. RF coordinator server 104 is generally an NPS IPA server 98. RF coordinator server 104 may not necessarily build the coverage map itself, but may ask NPS IPA agent 78 to generate the coverage map. NPS IPA agent 78 is, in turn, just an interface to NPS 58 and asks NPS 58 to build the coverage map.

Once trouble map 116 has received its coverage map, it tells coverage map 114 to highlight the problem site and its coverage area. Then, trouble map 116 may tell coverage map 114 to display itself on NMS workstation 64 so network operator 110 can observe the map.

Also, trouble map 116 will go through a similar set of operations in order to get traffic map 120 displayed. First, trouble map 116 asks traffic coordinator 130 for traffic map 120 around the same location as used by coverage map 114. Traffic coordinator 130 is an NMS IPA server 122. Traffic coordinator 130 also does not build traffic map 120, but rather requests NMS IPA agent 76 to build traffic map 120. NMS IPA agent 76 is an interface to NMS 54 and asks NMS 54 to build traffic map 120.

Once trouble map 116 receives traffic map 120 from traffic coordinator server 130, it tells traffic map 120 to highlight the site on the map and the affected traffic. Finally, the traffic map is displayed on NMS workstation 64 for network operator 110 to see. FIGURE 7B illustrates map 190 showing the anticipated impact due to a problem in a wireless network. Map 190 shows base stations 192, 194, 196, 198, 200, and 202 as they are located on geographic map 204 for the wireless network. In the example of FIGURE 7B, base station 196 has experienced a problem that affects its ability to provide a RF link to customers. Three levels of anticipated trouble densities associated with the problem at base station 196 are also represented on map 190. The high density trouble is designated generally by reference number 206, moderate trouble density by reference number 208, and low trouble density area by reference number 210. Depicting trouble densities 206, 208, and 210 on the geographic map 204 immediately shows that the anticipated highest trouble density will occur near base station 196. Map 190 also shows the anticipated impact of the problem at base station 196 on the remainder of the wireless network. By incorporating the design of the wireless network into the analysis, the problem areas not immediately adjacent to base station 196 can also be identified. This allows wireless service provider 48 to analyze the anticipated problems with the network and to direct resources to either repair what is wrong with base station 196 or to modify the performance of the base stations around base station 196 so that the impact to the customers is alleviated in the most efficient manner.

While these three specific examples of how an IPA may be used to integrate planning and operations information for a wireless network have been provided, the present invention is not limited to these examples. IPAs may use planning and operations information in several forms to provide graphical representations that more specifically and more quickly highlight events or problems that may affect the wireless network.

In operation, the present invention provides an IPA for integrating planning and operations information so that the performance of a system may be more easily analyzed and events that affect the system may be more easily understood and responded to. The present invention provides several technical advantages. One technical advantage is the ability to integrate planning and operations information so that operations data may be graphically depicted to allow the network managers to more fully understand their network's operations, understand the impact of events in the network, and plan their network's use and growth to respond to customer's needs.

Although the present invention has been described in detail, it should be understood that various changes, substitutions, and alterations can be made thereto without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

WHAT IS CLAIMED IS:

1. A system for integrating planning and operations data relating to an organization's infrastructure, the system comprising: a planning system for maintaining design data on the infrastructure's design; an operations system for maintaining operations data on infrastructure's operation; an integrated process and application (IPA) for integrating the planning data and operations data, and wherein the IPA further comprises; a planning system IPA agent for accessing the planning data from the planning system, and an operations system IPA agent for accessing the operations data from the operations system; and wherein the planning system can receive operations data from the operations system via the IPA and the operations system can receive planning data from the planning system via the IPA.

2. The system of Claim 1 wherein the operations system is further operable to control the operation of the infrastructure.

3. The system of Claim 1 wherein the planning system is further operable to generate a design for the infrastructure.

4. The system of Claim 1 further comprising: a strategic decision support system (SDSS) operable to process business data relating to the operation of the infrastructure; wherein the IPA further comprises a SDSS IPA agent for accessing business data from the SDSS; and wherein; the planning system can receive operations data from the operations system and business data from the SDSS via the IPA, the operations system can receive planning data from the planning system and business data from the SDSS via the IPA, and the SDSS can receive planning data from the planning system and operations data from the operations system via the IPA.

5. The system of Claim 1 wherein the IPA is further operable to provide predetermined planning data to the operations system in response to predetermined events occurring in the infrastructure.

6. The system of Claim 1 wherein the IPA is further operable to provide planning data to the operations system so that events that affect the infrastructure may be depicted with respect to infrastructure design data.

7. The system of Claim 1 wherein the IPA is further operable to use planning data with the operations data to identify a probable cause for an infrastructure event .

8. The system of Claim 1 wherein the IPA is further operable to generate proposed changes to the infrastructure from analysis of the planning and operations data.

9. The system of Claim 1 wherein: the infrastructure comprises a wireless network; the planning system is a network planning system operable to maintain network planning data for the wireless network including data on the air interface for the wireless network; and the operations system is a network operations system operable to manage the wireless network and maintain network operations data associated with the wireless network.

10. The system of Claim 9 wherein the IPA is further operable to provide network planning data to the network operations system for providing depictions of the air interface on the network's operation.

11. The system of Claim 9 wherein the IPA is further operable to provide network operations data to the network planning system so that the planned wireless network may be analyzed with respect to the deployed wireless network.

12. The system of Claim 9 wherein the wireless network is one of a cellular telephone network, a personal communication system (PCS) network, and a paging network.

13. The system of Claim 9 wherein the IPA is further operable to correlate events occurring in the wireless network to the type of equipment used in the wireless network.

14. The system of Claim 9 wherein the IPA is further operable to correlate network operations data to individual network elements.

15. The system of Claim 14 wherein the network operations data further comprises revenue data.

16. The system of Claim 9 further comprising: a strategic decision support system (SDSS) operable to process business data relating to the operation of the wireless network; wherein the IPA further comprises a SDSS IPA agent for accessing business data from the SDSS; and wherein; the network planning system can receive network operations data from the network operations system and network business data from the SDSS via the IPA, the network operations system can receive network planning data from the network planning system and network business data from the SDSS via the IPA, and the SDSS can receive network planning data from the network planning system and network operations data from the network operations system via the IPA.

17. The system of Claim 9 further comprising: a geographic information system (GIS) containing geographic data on the geographic area in which the wireless network is deployed; wherein the IPA further comprises a GIS agent for accessing geographic data from the GIS; and wherein; the network planning system can receive network operations data from the network operations system and GIS data from the GIS via the IPA, and the network operations system can receive network planning data from the network planning system and GIS data from the GIS via the IPA.

18. The system of Claim 17 wherein the GIS is part of the network planning system.

19. The system of Claim 17 wherein the IPA is further operable to correlate events occurring in the network to a given geographic location in the network.

20. The system of Claim 9 wherein the IPA is further operable to provide predetermined network planning data to the network operations system in response to predetermined events occurring in the wireless network.

21. The system of Claim 9 wherein the IPA is further operable to provide network planning data to the network operations system so that events that affect the wireless network may be depicted with respect to wireless network's design data.

22. The system of Claim 9 wherein the IPA is further operable to use network planning data with the network operations data to identify a probable cause for a wireless network event .

23. The system of Claim 9 wherein the IPA is further operable to generate proposed changes to the wireless network from analysis of the network planning and network operations data.

24. A system for integrating data associated with a wireless network, the data further comprising network planning data from a network planning system that maintains design data on the network's design including data on the air interface for the wireless network and network operations data from a network operations system that maintains operations data on the network's operation, the system comprising: an integrated process and application (IPA) for integrating the network planning data and network operations data, and wherein the IPA further comprises; a network planning system IPA agent for accessing the network planning data from the network planning system, and a network operations system IPA agent for accessing the network operations data from the network operations system; and wherein the network planning system can receive network operations data from the network operations system via the IPA and the network operations system can receive network planning data from the network planning system via the IPA.

25. The system of Claim 24 wherein the IPA is further operable to provide predetermined network planning data to the network operations system in response to predetermined events occurring in the wireless network.

26. The system of Claim 24 wherein the IPA is further operable to provide network planning data to the network operations system so that events that affect the wireless network may be depicted with respect to network design data.

27. The system of Claim 24 wherein the IPA is further operable to use network planning data with the network operations data to identify a probable cause for a network event .

28. The system of Claim 24 wherein the IPA is further operable to generate proposed changes to the wireless network from analysis of the network planning and network operations data.

29. The system of Claim 24 wherein the IPA is further operable to provide network planning data to the network operations system for providing depictions of the air interface on the network's operation.

30. The system of Claim 24 wherein the IPA is further operable to provide network operations data to the network planning system so that the planned wireless network may be analyzed with respect to the deployed wireless network.

31. The system of Claim 24 wherein the wireless network is one of a cellular telephone network, a personal communication system (PCS) network, and a paging network.

32. The system of Claim 24 wherein the IPA is further operable to correlate events occurring in the wireless network to the type of equipment used in the wireless network.

33. The system of Claim 24 wherein the IPA is further operable to correlate network operations data to individual network elements.

34. The system of Claim 24 wherein the network operations data further comprises revenue data.

35. A method for integrating data associated with a wireless network, the data further comprises network planning data from a network planning system that maintains design data on the network's design including data on the air interface for the wireless network and network operations data from a network operations system that maintains operations data on the network's operation, the method comprising the steps of: providing an integrated process and application (IPA) for integrating the network planning data and network operations data; accessing the network planning data from the network planning system through a network planning system IPA agent; accessing the network operations data from the network operations system through a network operations system IPA agent; transmitting network operations data to the network planning system via the IPA; and transmitting network planing data to the network operations system via the IPA.

36. The method of Claim 35 further comprising the step of providing predetermined network planning data to the network operations system via the IPA in response to predetermined events occurring in the wireless network.

37. The method of Claim 35 further comprising the step of providing network planning data to the network operations system via the IPA for depicting events that affect the wireless network with respect to network design data.

38. The method of Claim 35 further comprising the step of identifying probable causes for a network event by integrating the network planning data with the network operations data with the IPA.

39. The method of Claim 35 further comprising the step of generating with the IPA proposed changes to the wireless network from analysis of the network planning and network operations data.

40. The method of Claim 35 further comprising the step of providing network planning data to the network operations system with the IPA for depicting the air interface on the network's operation.