Patent Grant
8473303
The invention relates to electronic commerce technology. More particularly, the invention relates to a comprehensive electronic business support system for communications service providers.
Bringing businesses online is challenging in any industry. In the communications industry, complex operational infrastructures and intricate partner relationships pose an even bigger challenge in extending businesses to the Internet. In addition, today's climate of active consolidation means all providers will eventually face the challenge of integrating existing operational systems with those of a newly-formed subsidiary, parent, or partner. To remain competitive, providers must evolve into new organizations based on scalable infrastructures that incorporate dynamic and automated business processes to support customer-centric activities. New systems must also be designed for flexibility and efficiency to ensure continuous and responsive customer support. Retooling an existing infrastructure, however, is a costly and time-consuming option, even for new entrants burdened by few legacy systems.
What is desired is to develop a comprehensive, communications-specific electronic business (eBusiness) solution that communications service providers can easily deploy.
This invention provides a comprehensive, modular solution that brings eBusiness to communications service providers. The solution according to the invention is based on a deep understanding of communications business processes, operations support systems (OSS) complexity, and Internet technology. It integrates marketing, sales, ordering, billing and service into a single, personalized Internet portal and brings communications service providers directly to their customers. The Internet portal fulfills the promise of “one-stop shopping”, delivering targeted, convergent product bundles and round-the-clock service to valued customers. The completely open, modular architecture unites functionally segmented processes and systems across all customer touch-points. Together, these elements form a comprehensive solution that delivers speedy implementation, low maintenance cost, and rapid return on investment.
The solution is unique in that it allows customers to view their communications profile and requirements on their terms—in a format and flow consistently presented through a trusted and familiar Web browser interface. The information hub translates customer management processes into myriad discrete service order transactions, each one tracked, coordinated and reported on via the browser interface. This solution empowers customers and business partners with self-service capabilities, creating a revolutionary end-to-end customer experience that increases revenue and customer loyalty while dramatically reducing costs. It allows customers to interact with communications service providers in a whole new way with simplicity, intimacy, transparency and immediacy. Simplicity is possible because interfaces are clear, convenient and easy-to-use. Intimacy is created through expressed preferences and personalized profiles that are remembered, and service presentations tailored to customer preferences. Transparency is achieved through the presentation of meaningful status—customers understand exactly where their orders stand, reducing human intervention. Immediacy is attainable because customer requests are handled in real time.
The system according to the invention is built on a Java platform using open Internet standards, proven enterprise technology and leading workflow and middleware applications. It enables communications service providers to rapidly deploy a complete eBusiness solution all at once or in stages that fit their strategic and technical needs. The eBusiness portals are the Internet interfaces designed for a particular sales channel and audience. They provide a complete customer experience—one-stop-shopping and round-the-clock service. The invention's eBusiness platform provides the foundation for a communications-specific business model that enables a single view of the customer across functional silos. Its integration components automate business processes and leverage complex and heterogeneous OSS.
The eBusiness platform according to the invention provides a consolidated customer view and experience through a communications-specific business model spanning all customer touch-points. This end-to-end experience allows more than self-service purchasing of product bundles, by allowing customers to administer accounts, view bills, open trouble tickets, and more.
The eBusiness platform contains Smart Components and an Administrator. The Smart Components represent communications-specific data and business logic that is customer-focused, convergent, and cross-functional. They provide a single unified customer view across functional silos from marketing, sales, ordering, billing, to service and are built to Sun's Enterprise JavaBeans specifications. The Smart Components are grouped by logical functionality, providing a flexible design that makes it easy to add capabilities as the communications service provider's business evolves. Each Smart Component is designed to manage the unique application logic, data, and business rules for the communications industry and can be easily extended to implement the specific business policies and processes of a communications provider. The Administrator is a graphical user interface tool used by the communications service provider's internal staff to define and maintain the eBusiness site data.
The solution according to this invention allows for integration with operations support systems (OSS). Specifically, the Interconnect Framework provides predefined interfaces and connectivity to infrastructures. Through these components, the solution ensures that the customer experience remains simple, intimate, transparent and immediate.
The Interconnect Framework provides a flexible solution for integrating across business applications and OSSs. The solution utilizes CMIs to communicate with a communications provider's OSS. The communications messaging interfaces (CMIs) are predefined interfaces to any system, such as a communications provider's existing marketing, sales, ordering, billing, and service systems.
The eBusiness Portals, as embodiments of the solution, are the Internet interfaces that allow communications service providers to redefine the complete customer experience—integrating touch points across marketing, sales, ordering, billing and service into a personalized Web-based interface.
Each eBusiness portal provides the capabilities for a particular customer segment or sales channel. They are designed to quickly deploy a branded Internet presence. The eBusiness Portals present a communications provider communications-specific functionality and data dynamically and are easily configurable to evolve as its business changes and grows. Each of the eBusiness Portals utilizes a set of unique interfaces to meet the specific needs of the channel and audience. So whether the target customer is an IT administrator who is managing a communications service for 3,000 employees, a small business owner with 50 employees who needs Internet, phone, voice mail and other new products, or a residential customer who wants to add a new phone line or install DSL, the eBusiness Portals can be customized to support these specific customer needs. Each of the eBusiness Portals consists of a set of JavaServer Pages (JSPs) that allow for quick and easy changes to the presentation of the communications provider's portal by using standard Web development tools.
Section 1. Architecture
This section describes the architecture of the eBusiness support system according to the invention.
1.1. Overview
Referring to
(1) Business Layer 101, which is the core of the system 100. Smart Components 104 employ Enterprise JavaBeans (EJB) technology, which allows them to encapsulate all the core functionality needed to complete communications specific business transactions. By encapsulating this functionality, Smart Components 104 provide a unified view that seamlessly presents information obtained from disparate systems.
(2) Integration Layer 102, through which Smart Components 104 access external systems 110. The interconnect service within this layer uses communications messaging interfaces (CMIs) 105 and adapters 106/107 to transport messages. The CMIs are pre-defined interfaces to common services (e.g. rating, address validation, service reservation, etc.) needed to complete client requests for customer, pre-order, order, and post order transactions. The EAI Adapters 106 provide the flexibility to integrate with an EAI package 109. These adapters are configurable software interfaces for different EAI packages, such as Vitria BusinessWare or BEA eLink. Other adapters are also available.
(3) Presentation Layer 103, in which eBusiness portals provide communications specific functionality tailored to particular types of users, such as small businesses or resellers. These portals are eBusiness sites with interfaces and process flows dedicated to particular customer group. They use JavaServer Pages (JSP) technology—standard HTML files that contain blocks of simple Java code—to dynamically generate customer views 108. The JSP-based portal architecture enables the separation of the user interface from application logic, enabling the design of the page to change without altering the underlying content. Additional components of the portal architecture include a Web session controller, which maintains user session state, and page transition policies—Java classes that enforce page transition rules by accessing business functionality contained in the Smart Components 104.
Administrator 111 is a Java-based tool that uses XML files to map object attributes to the database. It enables users in product marketing to create and configure new products and services, without the need for software code changes. It provides access to system maintenance functions for setting up secure user access.
The layered and component-based architecture provides a carrier-class performance, transactional integrity, and communications expertise. For example, the Smart Component Server has the ability to cluster Smart Components for increased performance; and maintains transactional integrity and security; provides powerful, communications- specific capabilities.
The architecture provides fast and easy integration capabilities. For example, the interconnect service facilitates interoperability with external systems; can be middleware-based of communicate directly with an external system; and provides the ability to add new message types and adapters to external systems.
The architecture also provides a flexible front-end user experience. For example, the eBusiness portals are completely independent from the core Smart Components 104. Each portal can be redesigned without rebuilding or altering core functionality; can be one of many portals simultaneously accessing the same Smart Component Server; and is adaptable to new presentation vehicles.
The communications industry demands a carrier-class eBusiness solution that provides high performance, scalability and resiliency. The Smart Components 104 in this invention are implemented as stateless session beans in order to meet these requirements.
The Smart Components 104 are clustered to increase performance. Their stateless nature obviates the need to maintain instance-specific information over invocations. This means that even though bean instances are pooled, no complex state activation logic is required. Furthermore, in case of failure, instance data need not be replicated across nodes in a cluster.
New Smart Component instances can be dynamically generated as needed to meet increasing user demand. The request load is then distributed among the Smart Components 104 to fully utilize all resources.
Because the Smart Components 104 do not maintain any state information, a client need not maintain contact with the same bean instance throughout the life of a session. The Smart Components 104 can be replicated across servers. In the event of an outage, clients are switched to another bean instance on a working server.
1.2. Smart Component Server
Referring to
1.2.1. Activity Smart Components
The activity Smart Components 104 includes a plurality of managers. For examples: (1) Shop Manager 122, which provides the ability to navigate through a catalog and place offers in a shopping cart; (2) Quote Manager 124, which provides the ability to dynamically quote product charges to the customer. Possibly in conjunction with an integrated billing system, the Quoting Manager calculates a product charge based on an action (e.g. add, remove, upgrade, recurring, etc.), time period, customer pricing group and rate method. It also manages the configuration of products and creates the quote; (3) Order Manager 125, which governs the creation of an order and sending it to an external provisioning system; (4) Customer Manager 126, which delivers a consolidated view of an enterprise vision representing the customer, accounts, users and services. Customers manage their accounts, products, services, and users from their own perspective, which could be from an organizational, location or financial reporting structure; (5) Business Rule Manager 128, which defines valid business relationships between customers, accounts, products, and processes. Works with business rules to define allowable configurations during the ordering process (e.g. a customer must have an access line to order voice-mail). Customers are now able to self-manage the complex communications-specific configurations during the ordering process and account management; (6) Interaction Manager 129, which allows customers to track an order or service request from start to finish. Customers can immediately view provisioning steps that have been completed during the flow-through provisioning process. A high-level status is provided to the customer while a detailed status is used by the provider to track potential performance enhancements; (7) Bill Presentation Manager, which presents consolidated billing views online using information from customer invoices. The bill presentation manager interfaces with external billing systems to obtain billing information for display, dispute and adjustment; (8) Trouble Ticket Manager 133, which provides a self-service mechanism for the customer to request service assistance such as reporting trouble for a product. When used with Interaction Manager 129, real-time trouble ticket status can be viewed. The trouble ticket manager interfaces with an external trouble ticket application to handle the dispatch and resolution; (9) Sales Manager 127, which provides basic functionality to support a sales force in relation to a customer hierarchy; (10) Profile Manager 130, which provides a mechanism to collect and organize information about a customer; (11) Payment manager 132, which manages payments towards non-recurring charges either by adding the charges to the customer's next invoice or by collecting a payment method at the time of ordering; (12) Notice Manager 134, which provides a mechanism to store messages for display to targeted customers.
For situations where the processing logic is likely to change for each licensee, the addition of plug-ins is supported. The plug-ins are small, dynamically deployed algorithms that a communications service provider (CSP) can implement to perform specific tasks.
For example, the CSP could create an algorithm that determines which news and information item to select based on where a customer lives. To do this, the CSP would create a plug-in that selects the news and information item based on the customer's address. The CSP could later override this behavior by creating and registering a new plug-in that selects the news and information item based on different criteria-for example, the customer's area code.
1.2.2. Service Smart Components
Referring to
(1) Data Access
(2) Domain Objects
The domain objects are created by DAS 135 by invoking a create method, which looks in the BUILDER table to determine the builder class to use to create the new object. DAS 135 then passes the logical class name to the buildObject method in the builder class, which creates, initializes, and returns the new object. The system employs TopLink for Java, an object relational mapping tool, to map attributes from a domain object or display object to the database. TopLink accesses the database 145 via Java Database Connectivity (JDBC) 144.
(3) Data Cursor
The data cursor service is implemented as a stateful enterprise bean. It creates a scrollable, read-only cursor used when a large result set from a query is expected. However, because the resulting list is read-only, the data cursor service cannot be used to retrieve attribute values that need to be updated.
(4) Logging Service
The logging service 138 creates files that report on specific actions within the system. A CSP can configure the logging service to meet individual business needs. Log messages contain identifiers that report on the severity of an event (e.g. fatal, critical, warning, etc.), the architectural component where the event occurred (e.g. DAS, interconnect service, activity object, etc.), and the functionality that the application was attempting (e.g. shopping cart, customer, menu, etc.). Two types of loggers are used: a file logger that sends information to a text file, and a console logger that sends information to the screen.
(5) Authentication and Authorization
An authentication service is used to verify that a user name and password is valid for the system. An authorization service determines what a given user is allowed to do within a portal.
The authentication service is used by the Customer Manager 126 to register new user IDs and passwords, as well as authenticate users logging in to the system. It provides an abstraction to a security provider that contains principal information used for authentication. Principals are specific users of the system, and can be either individual users or defined groups. In implementation, an RDBMS-based authentication security provider is used to assigns new users to specific groups. This assignment happens when a user is created in either a Universal Agent Portal or a Small Business Portal. The CSP can also use the LDAPRcalm class, which authenticates principals using a directory service such as the Netscape Directory Server. New users and groups are also entered in this directory server.
Note that LDAP can only be used for authentication (verifying a user and password are valid for the system). All authorization within the application must be done using the RDBMSRealm service. The framework accesses the CYG-ACL table before rendering a page or executing a transition policy. This table associates permissions (either allowing or restricting execution) for a JSP or transition policy with specific groups.
The groups include: (1) UA_LICENSEE_USER, which can use the Universal Agent Portal to shop for and purchase products, manage hierarchies on behalf of customers and partners, and create price overrides; (2) UA_LICENSEEADMINISTRATOR, which can use the Universal Agent Portal to create other users of that portal, create price overrides, and also use the Administrator Console and the licensee-level features in the Small Business Portal; (3) CP_ADMIN, which can shop for and purchase products and manage hierarchies in the Channel Partner Portal and create other users of the Channel Partner Portal; (4) CP_USR, which is a read-only user of the Channel Partner Portal; (5) SB_ADMIN, which can shop for and purchase products and manage hierarchies in the Small Business Portal and create other users of the Small Business Portal; and (6) SB_USR, which is a read-only user of the Small Business Portal.
For example, the users of a Small Business portal are assigned to one of two groups: (1) sb_customer_user, which has read-only access to the portal; and (2) sb_customer_admin, which can shop for products and manage products.
If a user assigned to one of these groups attempts to log into a Universal
Agent Portal, an error message displays, and they are prevented from logging into that portal. Similarly, within a portal, access to specific pages can be restricted, and through the use of the tags in a JSP, links and content can be displayed to and executed by certain user groups.
1.2.3. Constant Classes
Constant classes are used throughout the application to store static data such as state names, street type codes, types of contacts, and so on.
When a CSP needs to add new codes and the corresponding values to the application, the CSP can either create its own constant class or subclass an existing constant class.
For example, the constant class StreetTypeCode defines codes that can be used by the application:
1.3. Integration with External Systems
The interconnect service EJB provides an interface that the activity smart components use to access external systems 110. Messages that contain information for external systems 110 are sent from the eBusiness support system through a particular type of communications messaging interface (CMI) 105. Examples of these CMI types include credit card validation, address validation, and service reservation, etc.
The CMIs are designed to work via EAI facilities. They provide APIs built on best practices established by industry groups such as the TeleManagement Forum (TMF) and the Ordering and Billing Forum (OBF), and through participation with emerging standards bodies such as IPDR Working Group, and vendor programs such as SunConnect Framework for Communications. Open architecture and a standards-based technology platform ensures that messages exchanged between the eBusiness platform and existing systems leverage standard interconnect techniologies such as XML CORBA Java Messaging Service, and TUXEDO.
Referring to
Various transport adapters are available with the Smart Component Server. For example: (1) Default adapter—this is a file adapter 156 that prints out all CMI information sent to it. By default, all CMIs 105 deal with provisioning or trouble ticketing writing to the default adapter. A CSP can change the routing data associated with the CMI so that these use a different adapter; (2) Open adapter 154—by default, this adapter's handlers are stubs used by CMIs 105 such as address validation or credit card authorization.
A CSP can configure these handlers to send the type of message appropriate to the transport. The CSP can also create additional handlers for new CMIs, or configure existing CMIs to use different (or new) adapters or handlers. However, if the CSP needs to send many messages via a particular transport type (for example 110P or DCOM), and if that transport type requires specific adapter properties (configured in the adapter's XML file), the CSP should create a new transport-specific adapter; (3) SMTP email adapter 155—this adapter sends email messages based on CMIs. Handlers for the email adapter 155 determine who receives the email and the template used to create the message; (4) EAI Adapter 106—this adapter is integrated with Vitria's BusinessWare, an enterprise application integration system that allows disparate systems to communicate via messages.
Each CMI 105 is also mapped to source and target strategy classes 151/152. The interconnect service 136 uses the source strategy to build up the payload message associated with the CMI before being dispatched to the transport adapter 153. Payloads are of a specific message type, such as name/value pairs or an XML, message. Target strategies are used to update the system with data from inbound messages.
Various strategies are available. For examples: (1) OidSourceStrategy, which builds a payload of OIDs. This is the default strategy used by all CMIs 105. It is the only one that can be used by the EAI Adapter 106; (2) DummySourceStrategy, which used when no source strategy is needed; (3) DummyTargetStrategy, which used when no target strategy is needed.
A CSP needs to create source strategies for each CMI that the CSP wants to actually be sent to external systems. When creating CMIs, the CSP can set the CMI_LOG flag so data about the dispatching of CMIs is persisted to the CMI_LOG table.
To receive inbound messages, inbound transport adapters 153 need to be created. The inbound transport adapter 153 creates a CMI, invokes the remote method receiveCMI(cmi) on the interconnect EJB. The interconnect service receives the inbound CMT and uses the target strategy to update the data model or to call the API.
1.3.1. How the Interconnect Service Sends CMIs
(1) The createCmi method on the interconnect service 136 is called, passing in the code value of the CMI.
(2) The createCmi method returns an empty CMI object.
(3) The putCmiDataItem method on the CMI object is called, passing in the Object Identifier (01D) and the fully qualified class name of the domain object that contains the event information the CSP wants to send. The source strategy 150 uses this information to retrieve data for the message.
(4) The sendCmi method on the interconnect service 136 is called, passing in a reference to the CMI object created in step (2). The sendCmi method returns information about the CMI response.
(5) The interconnect service 136 performs a database lookup in the CMI_CMI_POLICY table to determine which routing policy to use for the CMI.
This table maps each CMI code to the fully-qualified Java class of its routing policy. The routing policy determines the adapter to invoke and if the CMI is to be logged.
The eBusiness support system provides three routing policy classes: (a) a default policy that sends CMIs to the default file adapter 156; (b) a generic policy that uses the GENERIC_CMI_POLICY table to determine the adapter to which the CMI is delivered; and (c) a vendor product policy that uses the VENDOR_PROD_CMI_POLICY table to determine the adapter to which the CMI is delivered based on a product's action. For more advanced policies, a CSP needs to write its own policy class.
(6) If the default routing policy is used (or if no policy is specified) the routing policy sends the CMI to the file adapter 156 with a default payload (OIDs).
(7) If a generic routing policy is used, the routing policy class performs a database lookup in the GENERIC_CMI_POLICY table to determine which adapter to use. This table associates the CMI with: (a) Adapter home, which is the JNDI-bound name of the adapter; (b) Context, which is used to determine how to translate the data into a format the external system expects. Examples of context include the handler class name, an email address, a fax number, or any information the adapter needs to pass on the message; (c) Payload, which determines the type of message being sent, such as a class name and OID, a name/value pair, or an XMI, document. There is a payload constant for each payload type.
(8) If a vendor product policy is used, the routing policy class performs a database lookup in the VENDOR_PROD_CMI_POLICY table to determine which adapter to use. This table associates the CMI with: (a) an action, (b) vendor product OID, (c) adapter home, (d) context, and (e) payload. Vendor product routing policies are useful when the adapter to use varies depending on the action performed on a product. For example, to “Add” an access fine, the eBusiness support system might send a CMI to an external provisioning system. However, to “Remove” the same access line, the system might send an email. In this case, the VENDOR_PROD_CMI_POLICY table would contain one row for the “Add” action that sends the CMI to an adapter which uses handlers to deliver to the external system 110. The table would contain another row for the “Remove” action that calls an email adapter 155 to send an email to the CSP.
(9) The interconnect service 136 performs a database lookup in the SOURCE_TARGET_STRATEGY_POLICY table to determine the source strategy 150 to use for the CMI and the given payload. The strategy is invoked and it calls the Smart Component Server (either through DAS or a direct API call) to collect the data needed to build up the payload. If the default file adapter 156 was associated with the CMI, then the default source strategy 150 (OidSourceStrategy) is used.
(10) The adapter sends the message out to the external system 110.
(11) If in the CMI_CMI_POLICY table, the CMI_LOG_FLAG is set to 1, the interconnect service 136 populates the CMI_LOG table with dispatch information. The interconnect service also updates the CMI_DOMAINOBJECT_LOG.
If a CMI has multiple entries in the CMI_CMI_POLICY table, then the steps (5) through (11) are repeated again for the CMI. The order in which the process is repeated depends on the order in the database.
1.3.2. How the Interconnect Service Receives Messages
(1) The external system 110 sends a message to a transport adapter 153.
This adapter acts similar to a daemon process in that it listens to a specific port number or socket, or in the case of RMI, an RMI call. This message must include a CMI code value, CMI ID, and a payload type code.
(2) The transport adapter 153 calls createCmi (cmi) on the interconnect service 136 to build the CMI based on the code value.
(3) The createCmi method returns an empty CMI object. The adapter must be written such that it populates the CMI with the needed data before proceeding to the next step.
(4) The transport adapter 153 calls receiveCmi (cmi) on the interconnect service 136.
(5) The interconnect service 136 performs a database lookup in the SOURCE_TARGET_STRATEGY_POLICY table to determine the target strategy 151 to use for the CMI and the given payload.
(6) The target strategy 151 is invoked and it calls a smart component 120 (either through DAS 135 or a direct APT call) to update the system accordingly.
1.3.3. How the Interconnect Service Recovers from Errors
It is possible that a CMI 105 may fail correctly to reach its intended destination, or that it may fail processing at that system. In this event, the external system 110 should provide information describing the error in the response message.
The eBusiness support system provides an Error Correction Facility (ECF) to review, correct, and re-send CMIs which may have failed in this way. The ECF can also be used to re-send successful CMIs, should this be desired.
The ECF relies on information written to CMI_LOG and CMI_DOMAIN_OBJECT LOG when reviewing and correcting CMIs. For this reason, if the CSP wants to recover and correct an erred CMI, the CSP must populate the CMI_LOG_FLG flag in the CMI_CMI_POLICY table with ‘1’ to insure that CMIs of that type are logged.
Only CMIs whose payload is composed of the OIDs can be reviewed, corrected and re-sent by the ECF. The payload of a CMI 105 is determined by the source strategy 150.
When reviewing a CMI 105, the ECF relies on data in the CMI_DOMAIN_OBJECT_LOG table to re-construct the CMI and allow users to change and correct domain object data which may have caused the CMI to fail. Once corrected, the CMI and its payload can be re-sent to the external system 110.
Any error information provided by the external system 110 is captured in three fields in the CMI_LOG table: (a) ERROR-CDE, which is a numeric code for the error encountered; (b) ERROR-CNTXT, which is the context in which the error occurred; and (c) ERROR-MSG, which is a text string describing the nature of the error encountered.
It is the job of the target policy 151 for the CMI 105 to receive this error information from the remote system's response and populate the eBusiness support system's database 145. Then, when the CMI 105 is reviewed in the Error Correction Facility, this error information is displayed.
1.4. EBusiness Portals
The eBusiness support system provides portals that are specific to a market segment of the communications industry. The Universal Agent Portal, Channel Partner Portal, and Small Business Portals all use: (1) JavaServer Pages (JSP) technology—these HTML pages with embedded Java source code allow for dynamic Web content; (2) Display policies—embedded within the JSP pages, these policies access and manipulate data for display; (3) A Web session controller 162—this servlet mediates the creation and display of JSP pages; (4) Transition policies 163—these Java files determine navigation logic through the site; and (5) Resource Bundles—the classes store display values or messages corresponding to codes in constant classes.
1.4.1. JavaServer Pages
JSP pages are standard HTML files containing blocks of simple Java code that display dynamic content. A CSP can use a standard HTML editor to create and edit these pages.
The eBusiness support system leverages JSP auto-compilation capabilities but defers all navigation and application logic to other components within the portal. This approach clearly separates presentation responsibilities from application logic so a licensee can change events that occur during a page transition without having to alter the JSP page. A JSP page uses display policies that handle any process logic needed to display a page.
To create or edit JSP pages for the portal, a CSP needs to understand various aspects of JAVA or HTML such as Page directives, Transition directives, Scriptlets, Expressions, Tags, and JavaScript libraries.
(1) JSP Page Directives. The directives are used to set JSP page directives. For example:
The directives are also used to import needed classes. For example:
(2) Transition Directives. The transition directives are special HTML hidden form fields that appear on a JSP page. They determine what navigation logic, if any, the server should execute. Transition directives also determine the destination JSP page. The CSP is required to set the following three transition directives on the JSP page:
to—the intended destination page.
from—the originating page (the page the link is on).
Task—the task to accomplish during the transition from the originating page to the destination page.
The names that the CSP sets for “to” and “from” directives are logical names that uniquely represent pages on the server. The framework uses the URL_MAP table to obtain a fully-qualified path for the page corresponding to the logical page name.
The following code might appear on a JSP page:
At submit time, the values for the “to” and “task” directives are populated by the sub FormjavaScript function, which is defined in js_common.js, a library provided for input and form submit manipulation. The script notifies the browser to submit all form data, including transition directives, to the server. The server then parses through the data and looks in the TRANS_MAP table to determine if there is a transition policy associated with the “from” and “task” directives. If a transition policy does not exist, the user is directed to the page set in the “to” directive. If a transition policy exists, the policy is invoked and the server executes the navigation logic defined in the policy.
(3) Scriptlets. Java code within the page is placed inside a scriptlet tag. For example:
(4) Expressions. Java code that evaluates a string is placed inside an expression tag. For example:
(5) Tags. The Web framework provides a library of the tags that allow JSP page writers to retrieve value objects and display dynamic content using a simple tag syntax. These tags are action tags used to instantiate object(s) and make them available through scripting variables. They are specifically designed to simplify the process of retrieving or displaying information from the database.
The tags used in the eBusiness support system allow a CSP to introduce dynamic content into a page from a variety of sources, including databases, resource bundles, CMIS, and file systems. Table 1.1 illustrates various tags, including source tags for retrieving and displaying dynamic content, and presentation tags for display purposes.
For each of the source tags, the CSP can implement a corresponding display policy. Display policies can be used to modify the behavior of a custom tag.
To perform a simple data retrieval, such as retrieving an object by its primary key, a display policy is not necessary. However, if the CSP had compound criteria for its data retrieval, or if the CSP wanted to do some post-query data manipulation (e.g. calculate someone's age from their birth date), then the CSP would do those activities from a display policy. At request time, the tag invokes methods defined in the display policy implementation.
In the following example, the queryObject tag invokes a display policy that constructs a query used to retrieve the display object for the CustomerDetail screen:
To access the tag library, add the following line of code below the page directives in the source file:
(6) JavaScript Libraries. The JavaScript libraries are used for client-side validation. js_validation.js provides JavaScript methods for validating data to submit to the server. For example, it is used to verify that the required fields are filled in by the user.
Client-side validation should be used in conjunction with server-side validation. The former is not a replacement for the later. Although client-side validation may enable a better user experience by performing validation on the fly, it exposes the application to security risks from users who could bypass the JavaScript and submit erroneous data to the database.
The JavaScript libraries are also used for input and form submit manipulation. js_common.js provides javaScript methods for setting request parameters and passing variables and values to the server.
All pages that submit form data should access the librares.
To access the libraries, the JavaScript codes must be included in the HEAD tag of the HTML page. For example:
(7) Implementing a Back Button. Within JSP navigation there are two different types of contracts between JSPs. One is explicit and the other is dynamic.
In an explicit contract, a button or link on JSPA always takes the user to JSPB. The button or link on JSP_A has JSP_B coded into the navigation logic. In the same fashion, the “back” or “cancel” button on JSP_B will always return the user to JSPA.
In a dynamic contract, one screen can be accessed from multiple JSPs. For example, JSP_C can be accessed from either JSP_A or JSP_B. In this case, the “back” or “cancel” button on JSP_C cannot be tied to a physical JSP. The back functionality must rely on the history or stack that the browser stores to know where the user came from and what the previous JSP is.
Two methods that access the browser stack are history.go( ) and history.back( ).
history.back( ) always returns the user to the previous page. If a user navigates from JSP_A to JSP_B, and then executes the “back” button on JSP_B, the application returns the user to JSP_A. When JSP_B will return to JSP_A, implement history.back( ).
For more complex situations, history.go( ) can be implemented. history.go( ) is similar to history.back( ), but it accepts a parameter (Integer) that communicates how many pages the CSP wants the navigation to take the user forward (positive Integer value) or backwards (negative integer value). A counter is maintained on the JSP that is then used as the input parameter to history.go( ).
There are various cases that warrant the use of history.go( ). For examples:
(a) When a JSP includes both validation and a “back” button. If a user navigates to JSP_B, from JSP_A, and then experiences a validation error, JSP_B will be re-rendered with a validation message. Because technically the previous page from JSP_B with validation errors is JSP_B, history.go( ) needs to be implemented. The following code sample shows how the counter can be implemented:
(b) When a JSP includes cursoring and a “back” button. If a user navigates to JSP_B, from JSP_A, then clicks “next” to see more items on a list, JSP_B is re-rendered with the next set of list items. Because the last JSP from the second set of list items on JSP_B, if there is a “back” button, history.go must be implemented to return to JSP_A instead. The following code sample shows how the counter can be implemented:
In the case where a JSP has cursoring logic, as well as validation, the above counters would have to be added together.
(c) When there is a sequence of screens that all have “back” buttons. (Note that the JSPs in this sequence may also have validation and cursoring, so the above rules may also apply.) An example might be JSP-A, JSP_B, JSP_C, and JSP_D, all of which have back functionality on them. A user can navigate to JSP_A, then execute a link off JSP_A that begins the screen flow JSP_B, JSP_C, JSP_D, then back to JSP_A.
A concrete example is an AccountDetail JSP that allows a user to navigate to OpenTroubleTicket then TroubleTicketDetail, which then returns the user to AccountDetail.
In this scenario, a similar counter must be maintained by all JSPs in this sequence, in order that all “back” buttons work correctly. In the trouble ticket example, the following counter would be implemented on all screens in the flow:
(d) When a JSP requires multiple counters. For example, a JSP may have validation and be part of a JSP sequence. In this case, two counters are needed. The counter for validation is added to the common counter, kept by all JSPs in a sequence. For example:
When adding screens into existingjSP sequences, the CSP must evaluate whether a counter needs to be added to the JSP. This can be done by analyzing any counters that are on the screen before the new JSP and after the new JSP to see if a counter is being maintained.
(8) Display Objects. Display objects are value objects in the eBusiness support system that hold attributes displayed on a page. They are used as an alternative to domain objects when (a) the attributes to display span more than one domain object and (b) the domain object contains more attributes than what is needed to display.
For example, if a domain object called Foo contains four attributes, the CSP may want to display only one attribute. The CSP could choose to carry the extra three attributes or create a display object that contains only the attribute that the CSP wants to display
1.4.2. Display Policies
If the destination page in a transition requires more information than the parameters passed via the HTTP request from the Web session controller, or if a tag alone is not sufficient to retrieve and manipulate needed data, then a display policy is used. Query and generic tags on the resulting page access these policies, which are then used to retrieve and optionally manipulate data.
Display policies are interfaces that a CSP can implement to extend the functionality of the tags. Each tag of the tags has a corresponding display policy interface that the tag can invoke.
Table 1.2 illustrates various display policies and methods to implement.
The CSP can also use JSPs to upload files to a server. The properties file determines the directory to which any uploaded file will be saved, and the maximum allowable file size.
To allow an upload, the <FORM> tag must include the following attribute setting:
This upload request is handled slightly differently than any other page request from a JSP. Normally, all data submitted from a JSP is available to a portal as parameters. However, parameters are only allowed to be of type String. In this case, since a file is created on the server, an attribute in Request scope is created. It is accessible using the same form input name as indicated in the <INPUT TYPE=“FILE”> field on the JSP. The getAttribute method in this case, returns an object of type File. All other input fields are available, as usual, as parameters.
Additionally, to prevent overwriting of files on the server, the name of the file is prepended with the session ID, which is unique. The original file name (without the session id) is available as a Parameter using the name as indicated in the <INPUT TYPE=“FILE”> field on a JSP.
Since the Web framework is unable to determine when the portal is done using the file, the framework is unable to know when the file should be deleted from the server. It is left to the portal developers to delete this uploaded file, when no longer needed. This can be done using the method delete on the Java File object.
1.4.3. Web Session Controller
The Web session controller is a Java servlet that provides load balancing through a session-level, round-robin algorithm that weighs server load information and routes requests accordingly. This servlet also provides failover by replicating HTTP session information across nodes in a cluster, and maintains session state via a cookie-based session ID.
Every link or form submission on a JSP page points to this controller, called Go. When a transition starts, the following information is passed:
The Web session controller also resolves the page ID submitted with the request to an actual URL, in order to display the page.
The Web session controller uses scope as a way of describing the lifecycle of data as it travels from a client, through the framework, and back to the client. There are four types of scope and they range from a very short lifecycle to a long running lifecycle. These scopes are:
(1) Page. Page scope begins when a JSP starts rendering, and is available only to that page. Page scope is primarily used to pass data back and forth between a page and a display policy. Page scope expires when a JSP is finished rendering.
Sub JSPs each have their own scope, therefore the Request scope must be used to pass something from a parent to sub JSP.
(2) Request. Request scope is analogous to parameter and attribute data in an HTTP request. It begins with a browser request that passes in HTML form data, which is stored in the scope of parameters. Request scope lives throughout the life of the request from a client, until the destination JSP is rendered and sent back to the browser. Request scope is most often used to pass data from transition policies to JSPs and display policies. It is also used to pass data between parent and sub JSPs.
(3) Session. Session scope is analogous to attribute data in an HTTP session. It is created when a user first makes a request to the Web session controller and is destroyed when the session times out. Session scope is generally used to store data between requests. Keep in mind that information placed in session scope lives until it is explicitly removed or the session is terminated. Therefore, putting many objects into session scope can have performance impacts.
(4) Application. Application scope spans all sessions on the server. It begins with server startup and ends when the server is shut down. It is not clustered; each node has its own application scope.
1.4.4. Transition Policies
When a transition off a page requires data to be submitted or requires complex business processes, then a transition policy is invoked. When a user clicks a button or link, the Web session controller accesses the TRANS_MAP database table to determine if a transition policy is needed, using the from and task directives. It then routes the request either to that policy or if no policy exists, directly to the subsequent page.
Transition policies are Java files that contain navigation and validation logic. They access the Smart Components' API to perform specific business logic through the process and parse methods. These methods may also provide server-side validation against any submitted data. Once this method is executed, control returns to Go, which then determines the URL of the destination page using the URL_MAP table in the database.
Transition policies may also use the parseAddOn method, which enables the CSP to handle any new form fields that are added to a JSP in addition to the fields handled by the parse method. The parse method in the transition policy takes user input (HTML form data) and returns ParameterData, which contains at least one hash map of attributes and values, or at least one new (or updated) domain objects.
To add a new form field, the CSP must first subclass the existing transition policy for the task that needs to pass in the new field value. In the subclass, the CSP implements the parseAddOn method, which receives as a parameter the ParameterData returned by parse. To accommodate the new form field, the CSP should alter the hash map or object to include data that corresponds to the new fields. The updated ParameterData is then used by the process method when executing the necessary navigation logic and calls to activity Smart Components.
For example:
To add validation for a new form field, it is necessary to call the add method on the validation context object from within the parseAddon method. The process method then executes validation and handles validation errors for the new field.
(1) Nested Flows
Whenever a page flow has an undetermined exit, that process is considered a nested flow 185. In these cases the transition policy for the transition into the nested flow invokes a method that passes in (a) the ID for the first page in the nested flow; (b) the origin page ID; and (c) the destination page ID.
The Web session controller then stores that information and directs the user into the nested flow 185. A transition directive on the last page in the nested flow informs the controller to re-execute the transition policy for the originating page. However if needed, the last page in the flow may use a transition policy to first perform some business process, such as persisting data, before re-executing the originating page's transition policy.
If the DEST keyword is present, the server detects the keyword and re-executes the initial transition policy. In some cases, the CSP may also want to execute a transition policy that performs some business process, such as persisting data, before re-executing the transition policy that initiated entry into the nested flow. To do this, create an entry in the TRANS_MAP table that maps the logical page and task to the transition policy class. Then, the new task can be passed to the subForm method to execute the transition policy. After the original transition policy executes, the user exits the nested flow and forwards to the initial destination.
If the ORIG keyword is present, the server redirects the user to the page specified by the origPageld parameter without re-executing the transition that initiated entry into the nested flow.
In the previous registration example, when the transition policy for checkout on shopping cart 181 is re-executed, the user is now registered; therefore the destination page (either Quote Summary 183 or MyHome 184) is displayed.
If there is a need to reroute to another page, for example, to send the user to an error page, the nested flow 185 needs to be cleared. To do this, the clearNestedState method on the CygentContext object in the transition policy should be called.
(2) Non-Repeatable Transitions
The portal architecture also allows for the restriction of transition policies to be repeated. For example, when an end user has placed an order, the user should not be allowed to use his browser back button and resubmit the same order. To prevent this, transition policies can be flagged so that they cannot be repeated in the scope of a page flow. When this flag is set, instead of re-executing the transition policy, the server redirects to the destination page determined during the first execution of the transition policy.
In some cases, the CSP may not want a user to execute the same transition twice during a critical flow. For example, a user ordering an access line should not be able to submit the same order twice by using the back button to return to the order page after the order has already been submitted. To avoid this, the CSP can create a clearly defined set of related logical pages that constitute a flow, and specify pages within the flow that have non-repeatable transition policies. These transitions are non-repeatable within the scope of the flow.
Now referring to
Also referring to Table 1.3, for the first execution of the submit link on page C, the server looks in the TRANS_MAP table and executes the transition policy-associated with the originating page ID (C) and task (submit).
After clicking the “submit” button and transitioning to page D, the user may use the “back” button to return to page C. However, if the user (now on page C) tries to click the “submit” button again, the server does not re-execute the transition policy because the NO_RFPEAT_FLG is set to 1. Instead, it bypasses the transition policy and directs the user to the destination page determined during the first execution of the policy (when the FLOW table was accessed). In this example, the next page would be page D. See Table 1.4.
The user can now only execute Policy3 again by navigating through the application to page A (without using the browser button to go back).
For all pages with the same FLOW_ID, the data in the PAGE_ORDER column must consist of consecutive numbers that start with 1.
(3) Server-Side Validation
Whenever the CSP collects HTML form data that will be persisted to the database, the server-side validation within the transition policies should be used. Data that does not meet the validation criteria is placed in a validation exception (along with an error message retrieved from a resource bundle) and thrown. The Web framework redirects the user to the previous screen and makes information about the exception, including the input data, available to the screen.
Table 1.5 illustrates the server-side validation types supported by the current system.
The CSP can change the error messages that these validation types return by editting the resource bundle cygent.common.resource.ValidationMessageResourceBundle, or creating a new resource bundle and change the cygent.httpd.validation bundle property in the cygent properties file to use a different resource bundle class name.
1.4.5. Resource Bundles
The eBusiness support system stores all static data displayed at the front end (except data coded directly into JSP pages) in Java classes called resource bundles. Resource bundles associate text strings that appear in the portal with unique codes used internally by the application.
For example, static data for street types is stored in a bundle class called StreetTypeCodeResourceBundle:
Each resource bundle must have a corresponding constant class that identifies the unique codes used by the application. For this example, the constant class StreetTypeCode defines the codes that are used in the bundle class StreetTypeResourceBundle.
1.5. Client Request Process
(1) A user clicks a link on a page. Referring to
(2) The Web session controller 162 accesses the TRANS_MAP table in the database 145 to determine whether to invoke a transition policy 163. For example, the database row that contains CreateTroubleTicket as the origin page and submit as the task also contains the required transition policy, TroubleTicket-Submit Policy. This class is invoked.
(3) The transition policy 163 calls an activity Smart Component 120. For example, the TroubleTicket transition policy calls the factory 143 to obtain the TroubleTicketManager Smart Component 133.
(4) The activity Smart Component 120 calls DAS 135 to create and persist value objects 141. The transition policy 163 passes in values for the object. For example, the TroubleTicketManager Smart Component 133 calls DAS 135 to create new trouble ticket and trouble ticket contact domain objects. It then updates the objects with form data and persists the updated objects.
(5) Control is passed back to the transition policy 163. For example: the transition policy populates the CMI 105 with needed form data, and passes the CMI 105 to the interconnect service 136.
(6) The transition policy 163 returns control to the Web session controller 162.
(7) The Web session controller 162 resolves the page ID passed in the HTTP request 161 to a URL, and invokes the corresponding JSP page 201. For example, the TroubleTicketRecapJSP page is invoked. This file contains query tags to access the TroubleTicketRecapPolicy display policy.
(8) Corresponding display policies 202 are invoked and, if needed, a display object is created. For example, the TroubleTicketRecapPolicy gets all the information needed to display the new trouble ticket.
(9) The dynamic HTML page is returned to the client via HTTP. Referring to
Section 2. Data Structure
This section describes the data structure for the eBusiness support system which includes various database tables.
2.1 Area Table Descriptions
All tables of the database are grouped according to their area. Each table lists the name of each field attribute, whether or not the field is required, the type and length, and a description for each field.
(1) Populating Tables Manually
Every row in most database tables uses an Object Identifier (OID) as the primary key. To manually populate a row in a database, the entry for the row's OID must be determined for that area, using the SEQ table. The SEQ table contains an entry for each area of the application (the SEQ_NAME attribute) and a VALUE. The value is the next number to be used as an OID for that area, and is the number to be used as the OID for the new row. However, once this number is used, it must also be manually incremented, so that the next entry made will use a unique number.
(2) Type
Some tables have a TYPE field, a class indicator field used by the persistence layer to determine the subclass for a particular object. If the database is manually populated for an object that has subclasses, the correct type value must be entered. If the database is populated using the Administrator console, these values are automatically entered. To determine the correct value, the TopLink Builder console is used to view the inheritance properties for the superclass object.
(3) Write Lock
Most tables have a WRITE_LOCK field. This field works with the persistence layer to provide an optimistic lock that prevents access to a field if it is in the process of updating.
(4) Primary Keys
The field name OID denotes the primary key for a table. Any other field that uses “_OID” in its name is a foreign key.
(5) Dates:
All unset dates are treated as Y.
2.2. Agent
An agent is a user of the Universal Agent Portal.
Table 2. 2 maps an agent to an agent group.
Table 2.3 maps an agent to an agent group to which they have visibility.
Table 2. 4 maps an agent to a root (either a customer or a partner).
Table 2.5 creates a parent/child association between agent groups.
Table 2. 7 maps the agent to the root request with the root associated.
2.3. Bill Presentment
Table 2. 8 is a container used to pass billing point information to the portal.
Table 2. 9 represents an entry to an account.
Table 2. 10 displays header information regarding charge amounts for a specific account imported from an external billing system.
Table 2. 11 represents a dollar amount by which a charge is adjusted.
Table 2. 12 represents the amount charged for a transaction against an object. These values are imported from an external billing system.
Table 2. 13 represents an invoice charge item that represents a discount imported from an external billing system.
Table 2. 14 Represents information regarding a single line item imported from an external billing system.
Table 2. 15 represents an invoice charge that represents a non-recurring charge. This is imported from an external billing system.
Table 2. 16 allows addition of external data in the form of new attributes to any classes within the bill presentment domain.
Table 2. 17 represents an invoice charge that represents a recurring charge. This is imported from an external billing system.
Table 2. 18 represents invoice summary information, which is imported from an external billing system.
Table 2. 19 represents an invoice charge item that represents a tax charge imported from an external billing system.
Table 2. 20 represents an invoice charge item that represents usage charges imported from an external billing system.
Table 2. 21. is a collection of attributes representing Adjustment Request to a Customer Bill.
2.4. Business Rules
Table 2. 22 contains information regarding rules used to maintain valid relationships between objects. These rules are based on a finite set of atomic rules both simple (e.g., mutual exclusion) and complex (e.g., mutual exclusion plus a numerical limit).
Table 2. 23 contains parameter information which is used to describe a business rule.
Table 2. 24 contains information regarding descriptor groups. Descriptors are used to create groupings of objects or groupings of other descriptors that are used by business rules.
Table 2. 25 Contains information regarding individual items within descriptor groups. Descriptors are used to create groupings of objects or groupings of other descriptors that are used by business rules.
Table 2. 26 combines two simple object descriptors with a boolean operator to create grouping of objects used by business rules.
2.5. Common
Table 2. 27 represents a group of principals that share a role for authorization purposes.
Table 2. 28 maps individual Cygent users to Cygent groups
Table 2. 29 contains an encrypted password for a user of the Cygent system.
Table 2. 30 maps a CMI to a CMI policy.
Table 2. 31 contains information used to grant a permission on a resource or class of resources to a list of Users and Groups.
Table 2. 32 is used to group JSP pages into logical “flows” or sequences of pages which together perform a certain function.
Table 2. 33 determines which adapter to use if the CMI is associated with the generic routing policy.
Table 2. 36 maps a domain class with a domain OID for a CMI.
Table 2. 37 maps a plug-in constant to the appropriate plug-in class.
Table 2. 38 determines whether a transition policy is associated with the “from” and “task” directives during a page transition at the front end.
Table 2. 39 maps a page identifier to an external URL.
Table 2. 40 maps a validation constant to the appropriate validation policy class.
2.6. Customer
Table 2. 41 is default implementation of a billing point.
Table 2. 43 is a collection of attributes representing an address.
Table 2. 44 represents an offer instance that is either a provisioned product or a composite product, and has been assigned to a customer hierarchy.
Table 2. 45 contains the information required for billing purposes. To order billable products, a customer or partner must have at least one billing point. A customer or partner can have multiple billing points.
Table 2. 46 represents the group of products ordered using an offer collection.
Table 2. 47 is a collection of attributes representing a person responsible for an entity in the Cygent system. An entity can have one to many contacts.
Table 2. 48 represents credit information for a hierarchy object
Table 2. 49 is an implementation of the root hierarchy object.
Table 2. 51 represents a partner as an implementation of a root.
Table 2. 52 captures changes made to a Partner.
Table 2. 53 represents Partner-defined ID for a partner's customer.
Table 2. 54 contains information about geographical area where Partner is authorized to resale.
Table 2. 55 represents delivered products which are owned by an account and require no subscriber-type relationship.
Table 2. 56 represents a point on the hierarchy. A hierarchy objects can be a root, a billing point, or an assigned product.
Table 2. 57 allows external information to be added to hierarchy classes in the form of attributes.
Table 2. 58 maps a summary point to a hierarchy object.
Table 2. 59 maps a delivered product to an associated hierarchy object.
Table 2. 60 contains information regarding the customer's name.
Table 2. 61 maps an object to a specific address and address type. This table is populated when an object can be associated with multiple addresses (each of a different type). If an object is associated with only one address, the ADDR_OID is stored on the object itself and the OBJ_ADDR_MAP table is not used.
Table 2. 62 is used to apply rates specific to a group of customers or partners, such as residential or business price group. Every root must be assigned to a price group.
Table 2. 63 represents products that have been provisioned.
Table 2. 64 represents the highest point in a hierarchy. A root has no parent.
Table 2. 65 encapsulates a change instance of the Customer hierarchy object
Table 2. 66 represents that a billing point request captures changes made to a billing point.
Table 2. 67 represents a specific category associated with a hierarchy point for creating different views of the hierarchy.
Table 2. 68 represents a general category from which specific summary points are created.
Table 2. 69 represents that a person at the provider site is responsible for a particular aspect of a customer or partner's business.
Table 2. 70 maps a support to a root.
Table 2. 71 contains temporary information necessary to hold descriptions of products that are being considered for removal.
Table 2. 72 represnets the user object that contains information pertaining to a registered user's login name and password.
Table 2. 73 holds information pertaining to a user interaction with the system. For all portals it is used to log that a user has registered or signed in. For the Universal Agent Portal, a log is also created when an agent puts a user or customer into session.
2.7. Frame
Table 2. 74 is used with TopLink to create an aggregation of object attributes for OID, amount, and date.
Table 2. 75 is used to instantiate domain objects
Table 2. 76 is for a sequence of numbers used to determine OIDs.
Every row in a database table uses the Object Identifier (OID) as the primary key. To manually populate a row in a database, the entry for the row's OID for that area must be determined. The SEQ table is used to determine this number.
Each area of the application should have its own entry in this table. The value is the next number to be used as an OID for that area, and is the number to be used as the OID for the new row. However, this number is used, it must also be manually incremented, so that the next entry made (either by an administrator or by the application) will use a unique number.
2.8. Interaction
Table 2. 77 provides a portal view of an instance of an interaction model. This object contains information that allows customers to view the past, current, and future states of an instance of a business process model managed by an external workflow tool. Different portals may display different end-user views.
Table 2. 78 displays the end-user view of an instance state. The past, current, and future states of an instance are displayed as part of the end-user view of that business process model.
Table 2. 79 maintains state values of objects based on information from an external workflow tool.
Table 2. 80 maps interaction model objects to end-user view objects, enabling the end user to view the interaction model information in the portal.
Table 2. 81 references an interaction model associated with states for a particular object instance.
Table 2. 82 references the state of a step within an interaction model instance.
Table 2. 83 contains information regarding the state of a step within the interaction model.
Table 2. 84 contains information used to select an order item for an interaction model.
2.9. Note
Table 2. 85 represents notes that can be associated with a Customer, Quote or Order.
Table 2. 86 represents a note comment associated with a given note.
2.10. Notice
Table 2. 87 displays news and information to a user at the front end.
Table 2. 88 associates a content item with the specific object to which it is displayed.
2.11. Offer
Table 2. 89 maps the disclosure that the user selected with the offer instance.
Table 2. 90 determines what happens to offers within an offer collection when the collection is broken, usually by the removal of an offer within the collection.
Table 2. 92 represents a group that contains offers to be compared against each other.
Table 2. 93 maps a comparison group to a comparison definition.
Table 2. 94 maps a comparison group to a specific determinant.
Table 2. 95 stores values for comparison definitions for specific offers.
Table 2. 96 represents the individual screens within an offer collection.
Table 2. 97 represents the offers in an offer collection from which the user can make a selection.
Table 2. 98 maps one offer collection determinant to another.
Table 2. 99 represents legal information that a user must agree to before ordering a quote.
Table 2. 100 represents a single marketable entity offered by a licensee to its customers. An offer contains all the data necessary for displaying the offer to a customer, which is then related to one or more vendor products.
Table 2. 101 represents a set of screens used to display and select offers purchased as a group.
Table 2. 102 contains information used for mapping source offer collection objects with target offer collection objects during a transition.
Table 2. 103 represents licensee-entered price that overrides an associated price
Table 2. 104 represents associated reason for an override.
Table 2. 105 represents a specific instance of an offer as it moves through cart, quote, and order, and is assigned to the customer hierarchy. Each offer instance object contains a reference to the offer being ordered, the vendor product that needs to be provisioned, the non-recurring prices associated with the item, and the configured parameters.
Table 2. 106 contains the discount line items that are attributed to a particular offer instance.
Table 2. 107 contains information regarding a non-recurring charge for an offer instance.
Table 2. 108 contains information regarding a non-recurring charge for an offer instance
Table 2. 109 represents information regarding any tax rate associated with an offer instance.
Table 2. 110 references information regarding a usage rate for an offer instance.
Table 2. 111 maps source offer objects to target offer objects.
Table 2. 112 maps offers to vendor products.
Table 2. 113 maps source Offer's with target Offers during a Replacement
Table 2. 114 maps source Offer Collection's with target Offer Collections during a transition
Table 2. 115 determines an offer that is an upsell of another offer.
Table 2. 116 is used by determinant items to create parent/child relationships.
Table 2. 117 represents information necessary to display, validate, and collect parameters for products.
Table 2. 118 represents default parameter value for a specific vendor product.
Table 2. 119 maps enumerations to parameter definitions
Table 2. 120 contains the list of values for an associated parameter.
Table 2. 121 allows the user to validate against a group of parameters as if they were one entity (e.g., address validation). Parameters must belong to a parameter group
Table 2. 122 maps the parameter group object to the parameter definition object.
Table 2. 123 contains the configured parameter value selected by the user for a given offer instance.
Table 2. 124 maps a Cygent offer to an external provider's.offer.
Table 2. 125 represents displayed link from one offer to another related offer.
Table 2. 126 represents a single line item indicating what the offer instance was created from. An offer instance can be created in many different ways. (e.g., from the menu, an existing service, etc.) The offer instance can handle zero to many instances of source line items.
Table 2. 127 represents the lead time required to complete an action on an offer.
Table 2. 128 temporarily stores offer instances during the selection of an offer collection.
Table 2. 129 represents a vendor who supplies a product to the licensee.
Table 2. 130 represents an actual product that can be shipped or provisioned.
Table 2. 131 maps a vendor product to a CMI policy.
Table 2. 132 maps a disclosure to a vendor product.
Table 2. 133 maps vendor products to parameter groups.
Table 2. 134 represents a charge related to the creation of a supplemental order.
2.12. Order
Table 2. 135 represents a customer commitment to purchase a set of offers.
Table 2. 136 represents an external request for an offer. The scheduled due date and start work flow date are set when the preceding Quote Item is configured.
2.13. Payment
Table 2. 137 represents a subclass of payment. The credit card payment contains credit card information regarding a specific payment.
Table 2. 138 contains information regarding payment transactions made by users.
Table 2. 139 allows addition of new attributes to any classes within the Payment domain.
2.14. Pricing
Table 2. 140 represents the unique key for an action used for a price
Table 2. 141 is used to indicate which unit price is valid for different levels in a multi-level price arrangement
Table 2. 142 determines the active price arrangement for a given price group supported.
Table 2. 143 determines how a price is calculated (e.g., flat, tier).
Table 2. 144 represents the junction of a price group and an action supported for a given offer.
Table 2. 145 provides the actual monetary amount to be charged per unit for a given price arrangement.
2.15. Profile
Table 2. 146 defines a profile that can be associated with any Cygent class.
Table 2. 147 defines an element of a list from which a user can select a value for a profile. A set of ProfileEnumerations are associated with a Profile Definition through Profile Definition Profile Enumeration Maps.
Table 2. 148 is used to group profile definitions. All profile definitions must be assigned to a ProfileGroup.
Table 2. 149 associates profile definitions with ProfileGroups. Each ProfileDefinition must be assigned with one or more ProfileGroups
Table 2. 150 associates individual Profile Enumerations with Profile Definitions.
Table 2. 151 associates Profile Groups with Cygent objects.
Table 2. 152 contains the value of profile definitions selected by the user.
2.16. Quote
Table 2. 153 represents the point in the ordering process flow where a limited-time price is offered for items a user wants to purchase.
Table 2. 154 represents an offer instance in a quote
Table 2. 155 identifies groups of attributes on a quote item that will be populated either by preconfiguration or propagation. Groups include the product parameters, attachment date, requested date, and others.
2.17. Shop
Table 2. 156 contains information regarding offers placed in a customer or partner's shopping cart.
Table 2. 157 contains the information needed to display a menu, offer, or offer collection at the front end.
Table 2. 158 is a menu of other menus or offers displayed to the user. Users see root menus corresponding to their price groups. Each user has a price group and each price group has a root menu.
2.18. Task Manager
These tables are specifically for the task manager, which is an optional product. These tables are populated only if you have purchased the cygent task manager.
Table 2. 159 represents an object to which a task can be assigned.
Table 2. 160 represents a specific initiated instance of a process flow.
Table 2. 161 represents a group of objects qualified to perform a certain type of task.
Table 2. 162 maps a role to a specific performer.
Table 2. 163 represents a specific instance of an invoked task.
Table 2. 164 represents the value of a task variable for a specific task.
2.19. Trouble Ticket
Table 2. 165 represents a trouble ticket which provides a way for users to report issues regarding objects in their hierarchy or for an invoice.
Table 2. 166 contains comments for a specific trouble ticket object. A trouble ticket can have zero to many associated comments.
Table 2. 167 contains information used to map a trouble ticket to an interaction model selection.
2.20. Vitria Adapter
Table 2. 168 is specifically for the EAI adapter to Vitria BusinessWare, which is an optional product. This table determines the source and target strategies for vendor products that use the Vitria adapter. It is populated only if you have purchased that product.
2.21. View Tables
Views are logical representations of physical tables; they retrieve data based on operations on their underlying base tables.
Table 2. 169 retrieves offer instance, address and partner customer information for an assigned product, when applicable. Base tables include: ASSGND_PROD, OFFER_INSTNC, HIER_OBJECT, ADDR, and PARTNER_CUST.
Table 2. 170 retrieves offer instance, address and partner customer information for an assigned product, when applicable. Base tables include: ASSGND_PROD, HIER_OBJECT, and ADDR.
Table 2. 171 retrieves offer instance, address and partner customer information for an assigned product, when applicable. Base tables include: ASSGND_PROD, HIER_OBJECT, and ADDR.
Table 2. 172 retrieves data for actions taken when an offer collection is broken, when applicable. Base tables include: DSPL_ATTRIBS, BREAK_OFFER_COLLCTN_RULE, OFFER, and OFFER_COLLCTN.
Table 2. 173 retrieves data object descriptors and compound data object descriptors combined with a boolean operator to create grouping of objects used by business rules, when applicable. Base tables include: CMPND_DATA_OBJ_DSCPTR and DATA_OBJ_DSCPTR.
Table 2. 174 retrieves content items.
Table 2. 175 retrieves offer instance, address and partner customer information for a delivered product, when applicable. Base tables include: DELVRD_PROD, PARTNER_CUST, ADDR, OFFER_INSTNC.
Table 2. 176 retrieves partner customer information for a delivered product, when applicable. Base tables include: DELVRD_PROD, PARTNER_CUST.
Table 2. 177 retrieves data for determinant items and their associated offers when applicable. Base tables include: DSPL_ATTRIBS, DTRMNT, OFFER, and DTRMNT_ITEM.
Table 2. 178 retrieves data for mappings from one offer collection determinant to another, when applicable. Base tables include: DSPL_ATTRIBS, OFFER, OFFER_COLLCTN, DTRMNT_SEQ, and DTRMNT.
Table 2. 179 retrieves data for offer collections and their determinants, when applicable. Base tables include: OFFER_COLLCTN, DSPL_ATTRIBS, DTRMNT, and OFFER.
Table 2. 180 retrieves data for mappings of source offer collection's with target offer collections during a replacement, when applicable. Base tables include: DSPL_ATTRIBS, OFFER, OFFER_COLLCTN, and OFFER_COLLCTN_OFFER_RPLCMNT.
Table 2. 181 retrieves data for mappings of source offer collection's with target offer collections during a transition, when applicable. Base tables include: DSPL_ATTRIBS, OFFER, OFFER_COLLCTN, and OFFER_COLLCTN_OFFER_RPLCMNT.
Table 2. 182 retrieves data for offer transitions, when applicable. Base tables include: DSPL_ATTRIBS, OFFER, and OFFER_TRANSTN.
Table 2. 183 retrieves data for replacement offers, when applicable. Base tables include: DSPL_ATTRIBS, OFFER, and OFFER_RPLCMNT.
Table 2. 184 retrieves information for an offer, when applicable. Base tables include: DISPL_ATTRIBS, DTRMNT, OFFER.
Table 2. 185 retrieves information for an order item interaction model, when applicable. Base tables include: ORDR_ITEM_INTRCTN_MODEL_SELCTN, INTRCTN_MODEL, and VENDOR_PROD.
Table 2. 186 retrieves partner customer, agent and supplemented order information for an order, when applicable. Base tables include: ORDR, CNTCT, NAME, ORDR, HIER_OBJECT and PARTNER_CUST.
Table 2. 187 retrieves data for determinant items to create parent/child relationships, when applicable. Base tables include: OFFER, OFFER_COLLCTN, DSPL_ATTRIBS, DTRMNT_ITEM, and PARENT_ASSIGNMENT.
Table 2. 188 retrieves information for prices, contexts, and price arrangements, when applicable. Base tables include: PRICE, PRICE_ARRGMNT, and CNTXT
Table 2. 189 retrieves information to display returned provider offers for the service availability pre-qualification function. Base tables include: DTRMNT, DTRMNT_ITEM, PRVDR_SVC_OFFER_MAP.
Table 2. 190 retrieves partner customer, agent and supplemented order information for a quote, when applicable. Base tables include: QUOTE, CNTCT, NAME, ORDR and PARTNER_CUST.
Table 2. 191 retrieves data for links between related offers, when applicable. Base tables include: DSPL_ATTRIBS, OFFER, and RLTD_OFFER.
Table 2. 192 retrieves agent and contact information for a given root (partner or customer), when applicable. Base tables include: HIER_OBJECT, NAME, ROOT, AGENT_ROOT_MAP, CNTCT.
Table 2. 193 retrieves data needed to display a root request for a given agent. Base tables include: AGENT and ROOT_RQST.
Table 2. 194 retrieves data needed to display items in the news and information (notice) area. Base tables include: TARGET_CONTENT, CONTENT_ITEM, MENU, DSPL_ATTRIBS.
Table 2. 195 retrieves partner customer information for a given trouble ticket, when applicable. Base tables include: TRBL_TKT, PARTNER_CUST.
Section 3. Operations
This section describes the basic operations of the Smart Component Server (SCS), including the core services and comprehensive business process logic required to successfully conduct business online.
3.1. Users, Groups, and Agents
3.1.1. Users
Users are those who access the Smart Component Server through an eBusiness portal, or through the Administrator Console. Each user has a unique user name/password combination that provides authentication within the system. The user name and password are stored in an encrypted table (USR). The USR table contains all other user information, such as the hierarchy object or agent that a user is associated with.
3.1.2. Groups
Once a password is established, a user is assigned to one of the groups for the system. These groups are used by the ACL table to determine which JSPs and transition policies can be executed.
Various groups are available. For example:
Users, who use the Universal Agent Portal and who belong to the UA_LICENSEE_USER and UA_LICENSEE_ADMINISTRATOR groups, are agents with associated agent types. While the existing groups in the system determine application-level security, additional groups are needed to determine the actual data displayed to agents in the Universal Agent Portal. Customers and partners are associated with agents during the registration process. The associated agent will always be able to see that root's associated data.
However, a communications services provider (CSP) may want certain agents to be able to view data associated with other agents. For example, the CSP may want sales agent managers to view data for all customers and partners associated with the sales agents they are responsible for. This ability is handled through the use of agent groups and agent group visibilities.
The CSP can use agent groups and agent group visibility to create complex viewing scenarios. Group assignment and visibility work together to create data-level security. Although the New Jersey and Florida groups both belong to the East Coast group, they cannot see each other's data as they do not have visibility into that group.
Sally belongs to the East Coast group. Because Sally has visibility into the
East Coast group, she can see all data associated with any member of the East Coast group, which includes all members of the New Jersey group and all members of the Florida group-whether or not those members have visibility into the groups.
Sally also belongs the Regional Managers group, as does Marla. But because neither of them have visibility into that group, Marla cannot view anything associated with the East Coast group, and Sally cannot view anything associated with the West Coast group.
Christine does have visibility into the Regional Managers group, even though she is not a member. This means she has visibility to everything Sally and Marla also have visibility to.
When any customer or partner data is requested by a portal, the Agent
Visibility plug-in first determines whether the user associated with the request is an administrator or a CSR agent. If they are, all customer and partner data matching the request is returned. If not, then only the data for which the agent has visibility rights is returned.
3.2. Offers
Offers can either be single offers or can be associated and sold with other offers, such as bundles. Once offers are created, a CSP can create associations for upsell and related products, as well as upgrade and replacement paths for a particular offer. The CSP uses the Administrator Console to create offers and all associated objects such as vendor products, prices, and transitions.
3.2.1. Vendor Products
Vendor products contain information needed to provision products such as provisioning codes and provisioning start and end dates. Product parameters, disclosures, and service level agreements (the time it takes to complete a specific action such as “add” or “remove”) are also associated with vendor products.
Users are never shown vendor products. Instead, they see the offers associated with vendor products. More than one vendor product can be associated with a single offer. For example, an offer item of “Access Line” might be associated with two vendor products: one from Company ABC and one from Company XYZ. The ChooseVendorProduct plug-in in the system simply chooses the first associated vendor product found in the database. The CSP can develop a new plug-in that determines the valid vendor product for a given circumstance using different logic. Or the CSP could elect to determine the vendor product manually after the order is placed. It should be noted that the ChooseVendorProduct plug-in is only called if an offer is associated with more than one vendor product.
(1) Parameters
Product parameters provide information for the installation and operation of products; for example, the number of rings before voice mail activates. During the configuration process, form fields such as dropdown lists, radio buttons, and text entry fields collect the selections the user makes. These values are then persisted in the database.
Every parameter is associated with a parameter group. This allows the CSP to group similar parameters together. Vendor products are associated with parameter groups and not with individual parameters.
To have the user select from a list of valid values for a parameter, the CSP create a parameter enumeration. For example, if the CSP creates a parameter named “Number of rings before voice mail activates,” then the CSP might create a list containing the values “2,” “4,” and “6.”
If more than one vendor product is associated with an offer, and a plug-in is not used to determine the correct vendor product for a given customer, the user configures parameters for all associated products.
The CSP may have a situation where vendor products share parameter definitions, but each vendor product should have a different default value. For example, the CSP might have a parameter definition called speed. This definition might be used by both a dial-up access product and a DSL product. The
CSP might want the default for the dial-up access to be 58K, and the default for the DSL to be 512K.
The CSP can set a default value override for any vendor product. This ensures that the specified vendor product always has a certain parameter value set by default. Parameters (groups, definitions, and enumerations), as well as value overrides are all created in the Administrator Console.
(2) Disclosures
Disclosures are sets of terms and conditions that the CSP requires a customer or partner to read and agree to before a product can be provisioned. A single disclosure can be associated with many vendor products, and a single vendor product can be associated with many disclosures. Users are shown all disclosures for all vendor products associated with an offer.
3.2.2. Offers
Offers contain all the information needed to make purchasing decisions, such as price and descriptive text. Offers have an availability date and an expiration date. When an offer reaches its expiration date, it can no longer be offered for purchase. However, an offer can be associated with another offer to which the original offer transitions when it expires. This is the expiration offer. If no expiration offer is associated, then the user might see a message stating that they can no longer order the original offer.
All offers to be displayed in an eBusiness portal menu are associated with a DisplayAttributes object. The display attribute contains all formatting information needed to display an object in an eBusiness portal; for example, label, icon, font color, and description. A sales message can also be held in a display attribute. This message can be targeted towards an internal user such as a sales agent, to prompt them with information they should impart to their customer when selling the offer.
3.2.3. Offer Instances
When a user elects to buy an offer, an offer instance is created. An offer instance represents the single, unique instance of an offer purchased by a particular user. For example, when users shop the menu, they are looking at offers-representations of products they might want to buy. When they elect to place the product in their cart, they receive their own offer instance that they can configure as needed.
Offer instances are created whenever a cart item is created in the case of shopping the menu, or are created when a quote item is created, as in the case of reordering an existing product. Additionally, when an offer instance is created because a user is adding a product to the hierarchy, an associated assigned product hierarchy object or an associated delivered product is also created.
An offer instance retains its association with the offer and vendor product through the shopping, quoting, and ordering processes and when it is assigned to the customer hierarchy. An instance also retains an association with the parameter values selected and any active rates. Users can change parameter values and can remove products from their hierarchy. Both these actions can have a related price.
Offers may have different relationships with other offers. For examples:
When a user views an offer in a menu or cart, a pricing CMI prices that offer based on the price group for the root associated with the current customer or partner. Once a quote reaches the “quoted” stage, the price for non-recurring charges is calculated and assigned to that offer instance. Additionally, committed prices for recurring and usage charges are also associated with the offer instance.
At this point, any future changes to the active price for recurring or usage rates on the associated offer are not reflected on the offer instance—the rates originally associated with the offer instance remain valid.
(1) Price Groups
Price groups allow the CSP to market and provide specific products and prices to specific sets of customers. For example, an access line could have one set of prices for a residential price group and a different set for a business price group. Price groups are associated with root menus. Additionally, every root of a customer hierarchy (customer) must be assigned to a price group, and every price must be associated with a price group. This way, users only view prices associated with the root of their customer hierarchy.
Because Universal Agent Portal users are not themselves associated with a root object, they are shown the defaultInternalUserRootMenu as defined in the properties file. They are shown prices from the default price group.
To set a price group as the default, the CSP must edit the properties file. A price group adapter is available, which automatically assigns all customers to the default price group specified in the properties file. The CSP can create its adapters to call an external system to determine a price group.
A price is derived from the following objects:
Referring to
For price group B, there is only a price for usage for local toll. Because there is no price created for long distance, any user associated with price group B will be shown the long distance usage price associated with the default price group.
(2) Price Group Supported
A price group supported (PGS) determines the price based on a given price group and the action performed on a specific offer. The default actions that come with the eBusiness support system include actions that create non-recurring charges and actions that create recurring and usage rates.
(a) Actions that create non-recurring charges include:
It should be noted that by default, the system only calculates charges for non-recurring actions.
Unregistered users, or internal agents who shop for customers or partners before registering them, are shown prices associated with the default price group. Therefore, it is important to post notification that the final price may be different from the price displayed in the menu or cart. Because customers and partners must be registered before a quote can be created, prices shown in a quote reflect the price group assigned during registration.
Additionally, if a PGS does not exist for an action on an offer given a price group, then the user is shown the price associated with the default price group. If instead, CSP do not want members of a price group to be charged for a particular action, CSP must set the NO_PRICE_INDICATOR flag for that price group supported (unless there is also no PGS for the default price group for that action, in which case no price is shown).
For example, the Call Waiting offer has a PGS for the add action for Price Group 1 (the default), but does not have a PGS for Price Group 2. Therefore, any customer or partner associated with Price Group 2 is shown the price for Price Group 1. (If there were also no price for the add action for the default price group, then no price would be shown.)
However, if a PGS is created for Price Group 2 with the NO_PRICE_INDICATOR flag activated, then an customer or partner associated with Price Group 2 is not shown any price for the add action on the Call Waiting offer.
(3) Price
The price is the intersection of a PGS, a context, and the active price arrangement.
Context differentiates actions of the same type. Referring to
For prices charged for the action “transition” the context must contain the OID of the offer that the user is transitioning from.
The price can display a short and long description. Additionally, the format code determines where the price appears on the bill. For example, the CSP may want to group all rates of the same action together. The CSP create format codes in constant classes to work in conjunction with external systems.
(4) Price Arrangement
The price arrangement determines how to calculate the price. For example, a price may be multi-level such as tier or threshold, or it may be flat. The price arrangement code specifies the type of price arrangement.
(5) Unit Price
The unit price contains the monetary amount per unit, such as the dollar amount and the unit of measure (e.g., minute, hour). If a unit price is one of many prices in a price arrangement, the CSP need to create criteria to indicate the valid unit price for each level of the arrangement.
(6) Criteria
Criteria determine the valid price for a unit of measure in a multi-level price arrangement. The operand code represents text that describes the levels, such as “equals” or “less than.”
3.3. Offer Collections
The offer collection feature of the eBusiness support system allows the CSP to market and provision complex collections of products.
The CSP can also use offer collections to ask questions that help determine the appropriate group of products to present during the shopping process. During the shopping process, an offer collection is presented as a set of screens that gathers the information needed to create a grouping of products. As the user selects an item from a screen, the corresponding offer instance is placed in a temporary collection object 403. Once all selections are determined, the user verifies the grouping, and the individual offer instances are placed in their shopping cart.
3.3.1. Creating an Offer Collection
To allow users to order groups of products, the CSP needs to create: (a) offer collection 403, which is a representation of the groups of screens that displays offers to users; (b) determinant 401, which provides more functionality than that of a simple menu. For example, a determinant allows a user to select from a list of offers to create a bundle; (c) determinant item 402, which is an individual item that represents an offer on a determinant.
(1) Offer Collections
An offer collection represents the set of screens that displays and captures information needed to create a group of offers. There are three types of offer collections:
When offers purchased through a collection need to retain an association with each other, the CSP must also create a composite offer that represents the collection as a whole. In the example shown in
Products created from independent collections retain no association with each other. Therefore once provisioned, individual items can be deleted or transitioned without affecting the others.
(2) Determinants
Determinants, rather than menus, are used to display offers within an offer collection. Each determinant type corresponds to a specific JSP page whose transition policies use smart component functionality to create the collection. New determinants may be created by CSP. The solution provides the following determinant types:
Determinant items represent the offers from which the user can make a selection. They are associated with both a determinant and the actual offer they represent. When a user selects a determinant item, an offer instance is created and placed in the temporary collection.
The CSP must be sure that associated offers have not expired. If expired offers are associated with determinant items, the user is still shown the determinant items, and the offer and collection expire when the user elects to purchase the associated quote.
Each offer collection has an associated sequence that establishes the default order in which determinants are displayed within the collection. However, individual determinant items can override that sequence if the next determinant displayed depends on the determinant item selected. For example, in the Web bundle shown in
3.3.2. Ordering a Fixed Bundle of Offers
3.3.3. Ordering a Dynamic Bundle of Offers
3.4. Creating Offer Transitions
Transitions allow users to upgrade from an offer instance associated with an assigned product to another pre-determined offer. When a user chooses to upgrade a product, the assigned product becomes associated with the new offer instance and a quote item associated with the new offer is created. The CSP create offer transitions in the Administrator console. For any given offer, the CSP can create one to many transitions. However, the CSP cannot create transitions for delivered products.
3.4.1. Transitioning Offer Collections
The CSP also creates transitions for each offer within an offer collection. Additionally, the CSP can create transitions for when a user breaks an offer collection by attempting to remove an associated product.
For dynamic collections, users can transition the individual offers. Therefore the CSP creates transitions for each offer associated with determinant items in the collection. The composite itself cannot be transitioned—the transitioned products retain an association to the original composite.
For fixed offer collections, the user can only transition the composite product, and at this time, all offer instances associated with that composite are automatically transitioned. Therefore, the CSP must also create transitions for each of those offers, along with a transition for the composite itself.
3.5. Catalogs and Menus
Menus comprise the catalog from which users select product offers. The CSP creates menus using the Administrator Console. A menu can contain a list of links to other menus or it can contain information regarding an offer. When a menu has no associated parent menu, it is a root menu.
The root menu displayed to a user (and therefore all subsequent menus associated with the root menu) depends on the root object currently in session. Users are either associated directly with a root object (as is the case with Small Business Portal and Channel Partner Portal users), or they are agents (as in the Universal Agent Portal).
Referring to
The CSP use the Administrator Console to create menus. Each menu is associated with a DisplayAttributes object that determines display information such as icons, text color, and description. When creating a menu that will be associated with the default menu, be sure to include only offers or offer collections that everyone who will shop on the CSP's Web site can order.
3.6. Hierarchy
In the eBusiness support system, billing points and products that a user procures are organized on a hierarchy. Referring to
To allow for different objects in the eBusiness support system to have the same hierarchy properties, hierarchy objects 451 may be subclassed. For example, in the Channel Partner Portal, the partner object subclasses the root object and is therefore the root in that portal's hierarchy. In the Small Business Portal, the customer object subclasses the root object.
Each hierarchy object has a valid state at any given time. States determine the current stage in the lifecycle and the actions that can be performed on the object.
3.6.1. Creating a Hierarchy
Root and billing point hierarchy objects are created during registration. At this point, other objects can also be associated with these hierarchy objects, such as contacts, names, and addresses. Assigned product hierarchy objects are created during the shop process when the cart items and associated offer instances are created.
(1) Request Objects
Whenever a hierarchy object is created or modified, before the new or changed information is persisted to the actual hierarchy object, a request specific to that object is created (for assigned and delivered products, the request object is a quote item, then an order item). For example, before an actual customer is created, a customer request is created. This request object contains all information that might be needed by any external system that also needs to create a corresponding object.
(2) Root
The root of a hierarchy is at the top level; that is, it has no parent. Products cannot be assigned to a root. The act of registration creates a root hierarchy object to which billing points and products can be associated. The root object holds the following information:
The root's associated hierarchy object stores state information. A root can have the following states:
A root can be either a customer or a partner. If the root is a customer, it can have an associated customer ID. If the root is a partner, it has an associated partner ID and can also be associated with a resale region.
(3) Billing Point
A root hierarchy object has one or more billing point objects as a child. This is the point at which billing for all associated products occurs. All information needed for billing purposes is stored on the billing point, such as active/inactive dates, billing periodicity; bill round, and running balance.
The billing point's hierarchy object stores state information. A billing point has the following valid states:
A product is a representation of an item that a user has purchased and placed on a hierarchy (this is done during the quote process). Products retain an association with an instance of an offer—the entity that the user shopped and elected to purchase. Products must be attached to either a billing point or another product.
There are two types of products: assigned products and delivered products. An assigned product is a hierarchy object, and can be either a provisioned product or a composite product. A delivered product is not a hierarchy object, but can be associated with a hierarchy object.
(a) Provisioned Product. Provisioned products have a subscriber relationship. That is, the account to which the product is assigned is charged on a periodic basis during the life of the product. These charges can be a one-time fee, a recurring fee, or a fee for usage of the product. An example of a provisioned product is voice mail. Provisioned products can have the following states:
(b) Composite product. Composite products represent a group of products ordered as a bundle. An example of a composite product might be “The Essential Bundle,” which maintains an association with an access line, voice mail, and call forwarding provisioned products (these associated products can be placed anywhere on the hierarchy). Composite products always have a billing point as a parent, and do not have children. Composite products can have the following states:
(c) Delivered Products. Delivered products are normally shipped to and owned outright by the customer and require no subscriber relationship. That is, the billing point is charged for the product only once. They are not hierarchy objects themselves, but instead, may be associated with a hierarchy object. An example of a delivered product is a cell phone associated with a wireless service program.
Delivered products can have the following states:
Once a hierarchy is created, it can be managed. The Small Business Portal and the Channel Partner Portal users can self-manage their hierarchies. The
Universal Agent Portal users manage hierarchies on behalf of customers and partners.
The actions that a user can initiate against a hierarchy include: (1) Add an account or modify an existing billing point; (2) Modify customer or partner information, including addresses and contacts; (3) Upgrade assigned products. When a user upgrades an assigned product, the association the assigned product had to an offer instance changes to the offer instance the user upgraded to; (4) Re-order products and attach the new products to other points in the hierarchy; (5) Modify the configuration of an vendor product associated with an assigned product; (6) Suspend and resume an offer instance associated with an assigned product (Universal Agent Portal users only); and (7) Report trouble on any hierarchy object.
3.6.3. Hierarchy Related Objects
The following listed are objects that can also be created and then associated with hierarchy objects.
For example, during the registration process, form fields such as dropdown lists, radio buttons, and text entry fields collect the selections the user makes in response to predetermined questions (called profile definitions). These values are then persisted in the database and are associated with a target class and target OID (for example, the customer who answered the questions).
To have the user select from a list of valid values for a profile definition, the CSP create a profile enumeration. For example, if the CSP creates a profile definition “Choose your industry,” the CSP might create a list containing the values “Software,” “Consulting,” and “Hardware.”
By mapping profile definitions to profile groups, the CSP can display sets of parameter definitions together. By further associating these groups to profile keys, the CSP can determine which profile groups are displayed under what circumstances. For example, the CSP might create a profile key of customer and a profile key of partner. The CSP would then create its JSPs such that those that display the profiles to customers only display groups associated with the customer key.
A user can create associations among hierarchy objects to display them by category. To do this, a user creates summary point types and specific summary points. For example, a summary point type might be “Location” and the summary points might be “East,” “West,” and “Midwest.” Once the summary point types and summary points are created, a user can go through the hierarchy and assign summary points to specific billing points or assigned products.
A user can assign many summary points to a hierarchy object. For example, in addition to “Location,” a user might also create a summary point type of “State” and individual summary points for specific states, and then assign both summary points to hierarchy objects.
Once summary points are assigned, users can change the hierarchy view by sorting according to summary point type. The user can select up to three different summary point types to determine sorting priorities; for example, first by location, then by state. Items that are not assigned a summary point type used in the sort order are not displayed in the view
Views do not retain any hierarchical information. All objects are shown as a list. These views cannot be saved. Users must determine a sorting order each time they wish to view the hierarchy in an order other than the default.
A user can rename and remove summary point types and summary points. If a user removes a summary point type, all summary points associated with it are also removed. When a summary point is removed, any billing point or product that was associated with the summary point loses that association.
3.8. Shopping Cart
When a user elects to purchase an offer from a menu, the following happens:
The cart acts as a “sandbox,” where offers can be added and deleted, and quantities changed, before moving on the quote process where the offer instances are configured.
An user can remove a cart item if it does not belong to a fixed or dynamic offer collection. If the removed item is a composite product, then all other products associated with the same offer collection are also removed.
3.9. Quotes
Users create a quote by selecting to purchase the items in their cart. Each offer instance associated with a cart item becomes associated with a quote item, and the quote becomes associated with the root of the current hierarchy in session. This allows the user to view that hierarchy during the configuration process to determine where to assign or associate the items in the quote.
Quotes display the total monthly recurring charges as well as the total non-recurring (one-time) charges for all items in the quote. Users can enter a description for the quote.
Quotes are associated with the customer or partner's root object. They also maintain an association with an agent if the quote was created using the Universal Agent portal.
Quotes may have various states including: (1) New, which indicates that the quote is created; (2) Pending Configuration, which indicates that not all quote items are completely configured; (3) Configured, which indicates that all quote items are completely configured; (4) Quoted, which indicates that all quote items are configured and contain all the information needed to order the entire quote. The user can no longer alter the quote; (5) Expired, which indicates that the quote has expired and can no longer be ordered; (6) Pending Approval, which indicates that the quote cannot be completed until one or more requirements are met. For example, at this point you might have an external system run a credit check; (7) Canceled, which indicates that the user canceled the quote; (8) Rejected, which indicates that requirements in the approval state were not met; and (9) Completed, which indicates that the quote has been ordered.
3.9.1. Held Quotes
Once a quote reaches the negotiated quote stage, it can be held for a predetermined amount of time before it expires and can no longer be ordered. Once a quote expires, the user must create a new one.
When a quote expires depends on when the user requested provisioning during the configuration process. If the user accepted the earliest possible start date for all items in the quote, then the quote expires 30 days later. If the user selected a later date for provisioning, then the quote expires on the day that is the earliest of all provisioning dates. However, no quote is valid more than 30 days. If the date selected for provisioning is more than 30 days, the quote still expires after 30 days. The CSP can change the 30-day period for maximum valid days to any length of time by editing the properties file.
If a price for an offer represented by a negotiated quote item changes while a quote is held, the associated offer instance retains the association to the original price and not the new price. And if the offer itself expires, the associated offer instance remains valid for the quote.
3.9.2. Quote Items
Quote items, which are the individual items that make up the quote, are associated with offer instances. During the quoting process, users configure parameters for each quote item. The parameters they configure, and the values they can choose from, are determined by the vendor product associated with the offer instance for the quote item. Once the parameter values are set, those values are directly associated with the offer instance.
It is also during the configuration that a user determines where the quote items should be attached: either to an existing point in their hierarchy or to another item in the current quote. The eBusiness support system uses business rules to determine and display only valid attachment points.
Quote items can have the following states:
If the quote is created because the user is transitioning from an existing product in their hierarchy, then the quote item retains an association with the original offer for transition pricing purposes.
When a user elects to purchase a quote, all disclosures for the offer items associated with the quote items are displayed. If the disclosure is not accepted, the user can return to the quote and remove the associated quote item. Once all disclosures are accepted, a CMI sends information regarding the relationships of all quote items to the business rule adapter. If any quote item violates a business rule, a warning is displayed.
(1) Pre-Populating Default Configuration Values
The eBusiness support system can be configured such that certain values for an offer instance are automatically populated during the transition from the cart to the quote through the use of plug-ins. The plug-ins default the values for the following attributes:
When configuration values are pre-populated, the status for each item is set to “configured” during the transition from cart to quote. If needed, the user can then change any of the defaulted values.
(2) Propagating Configuration Values
When a user purchases several of the same item, instead of having to configure each item, the user can elect to propagate values from one quote item to all quote items associated with the same offer item, so that the values are the same for all items. As with setting default configuration values, this is done with one of the plug-ins that can propagate the following configuration values:
If needed, the user can then change any of the defaulted values.
(3) Price Overrides
The prices displayed for a quote item are those associated with the corresponding offer item. However users of the Universal Agent Portal can override these prices.
A price override can be either a percentage off an existing price, or it can be a new dollar amount that represents the final price. This is determined by the price override type. Overrides reasons are pre-configured using constant class codes. Users pick a reason from this pre-configured list.
Each agent has a threshold that determines the amount they can reduce a charge or rate (overrides can only be used to reduce a rate or charge). This override amount cannot be exceeded when the quote is submitted to be ordered.
If a price is overridden in the Universal Agent portal, this overridden price is the price displayed in the Small Business and Channel Partner portals.
3.9.3. Modifying Quotes
Once quotes reach the negotiated state, they can be modified. However, instead of changing the current quote, all information is copied onto a new quote and the original quote remains the same. This allows the user to compare quotes. When these quotes contain the same offer instance(s), only one of the quotes can actually be ordered.
3.9.4. Suspend/Resume Services
Quotes are also created when a user wishes to suspend or resume an existing assigned product. It may be desirable to suspend rather than remove or unprovision products for a number of reasons. For example, a subscriber may be a large customer who has allowed one or more accounts to fall into arrears. Rather than terminate service (which may damage the customer relationship), services can be suspended while the subscriber is given a chance to bring their account current.
Only assigned products that are in state Provisioned may be suspended. Delivered products may not be suspended or resumed.
(1) Suspension
While an assigned product is suspended, it is put into state Suspended and is no longer a valid attachment point for new products. A quote that contains the products to be suspended is priced as usual, showing charges on the associated offer for the action “Suspend.” The assigned product is then moved to a pending state and once the suspend order is submitted and complete, the assigned product moves to state Suspended.
(2) Suspension of Products in Offer Collections
The process described above is true for single, a la carte products. The situation is slightly more complicated in hierarchies with multiple child products or products which were provisioned as part of an Offer Collection.
When an agent attempts to suspend a product, the DetermineSuspendProductList plug-in checks to determine if the product can be suspended. The default plug-in logic is as follows:
As stated above, only products in state Provisioned may be suspended. If a child product is in a state other than provisioned, the plug-in will throw an exception, an error message will be presented, and the entire transaction will be rolled back.
(3) Resuming
Resuming products functions similarly. Resuming a product will resume all of its child products, and only products that are in a state Suspended can be resumed. However, if there is a need to resume a product that is in a Provisioned state, it will not throw an error. For example, in the hierarchy in
3.10. Orders
When the user purchases all items on an existing quote that has not expired, an order is created. All items in a state of Configured on the quote become order items.
Like a quote, an order is associated with the same hierarchy root as the user. In a default implementation, orders can have the following states: (1) New, which indicates that the quote is ordered; (2) Pending Dispatch, which indicates that all order items are created; (3) Dispatched, which indicates that the order is dispatched to the provisioning system; (4) Completed, which indicates that the order is provisioned; (5) Rejected, which indicates that the order is rejected; (6) Pending Cancellation, which indicates that a request is submitted to cancel the order; (7) Canceled, which indicates that the order is canceled; and (8) Supplemented, which indicates that a user changed the order by creating a supplemental order.
An order retains an association with any shipping address associated with the quote, as well as the total of the order, any payment made, and the date the order was submitted.
3.10.1. Order Items
Order items derive much of their information from the associated quote item, except for their order, their requested, scheduled, and submitted dates, and their state. The valid states for an order item include: (1) New, which indicates that the quote item is ordered and is now an order item; (2) Dispatched, which indicates that the order item is dispatched to the provisioning system; (3) Completed, which indicates that the order item is provisioned; (4) Rejected, which indicates that the order item is rejected; (5) Pending Cancellation, which indicates that a request is submitted to cancel the order item; (6) Canceled, which indicates that the order item is canceled; and (7) Supplemented, which indicates that the order has been replaced by an order created through a supplemental quote.
3.10.2. Supplemental Orders
Users can change an order once it has been submitted as long as the item they wish to change has not completed the provisioning process. This is done through the creation of a supplemental order. This process is similar, but not identical to, the standard quote-to-order process.
When a user elects to create a supplemental order, the system creates a new quote which is populated with copies of each of the order items from the original order. During this transition, the SupplementalOrder plug-in determines which items in the original order are eligible for supplement.
By default, this plug-in only allows supplemental orders for items that are in a Dispatched state. Items in any other state still appear in the new supplemental order quote, but have the Supplemental Complete state, indicating that they are complete and no further action need (or may) be taken. The CSP can modify this plug-in to include any other logic, the only requirement is that it return a “True” or “False” value for each order item from the original order indicating if that item is eligible for supplement.
For the quote items that can be changed, users can elect to do one of the following:
The following actions are taken when an agent submits a supplemental quote:
5. The supplemental quote, and all its quote items move to state Complete and the quote ceases to be active.
6. The original order and all its order items move to the state Supplemented and the original order ceases to be active. The new supplemental order becomes the active order.
Once this process is complete, the proper CMI is dispatched to the external system. This CMI is the ServiceRequest CMI in the case of add or change, and the CancelServiceRequest CMI in the case of cancellations.
Second, the agent cancels the Call Waiting product in the supplemental quote, moving the quote item to Supplemental Cancel 482.
Third, the agent replaces the Voicemail product with the Super V-Mail product 483. The original Voicemail quote item moves to state Replaced, and a new quote item for Super V-mail is added to the supplemental quote in state Pending Configuration.
Forth, the agent must configure those products in state Pending Configuration; Super V-Mail (which was just added via the replacement) and Call Forward 484.
Finally, the agent submits the order 485. The plug-in runs again on the items in the original order and finds that none of them have become ineligible for supplement (which might occur if one of the items in the original order had subsequently completed provisioning and changed state from Dispatched to Complete), and so allows the supplemental order to be created. Access Line, since it was not eligible for supplement, enters the Supplemental Order in the same state (Complete) that it was in the original order. New or reconfigured items (Super V-Mail, Call Forward) are added in state Dispatched. Call Waiting, which was canceled, shows up in the supplemental order in a Pending Cancel state. Finally, Voicemail does not appear in the order since it was replaced by Super V-Mail. After all items have been added, the proper CMIs are sent to the external system. Note that this includes a CMI for Access Line, even though it is expected that the external system will do nothing (since no change was made to the order item),
(2) Charges from Supplemental Orders
The action of creating a supplemental order can create a charge. However, unlike charges or rates associated with a particular offer, the system uses the CalculateSupplementalCharge plug-in to create the charge. By default, this plug-in creates a supplemental charge object, which is a flat fee, and then associates it to a hierarchy object (by default, the billing point). The logic to create the charge can be modified.
(3) Escalations
Users can escalate an supplemental order. This sets the escalation flag attribute on the supplemental quote and order.
3.11. Business Rules
The CSP can define rules that maintain valid relationships between objects. These rules are based on a finite set of atomic rules both simple (e.g., mutual exclusion) and complex (e.g., mutual exclusion plus a numerical limit). For example, when defining a voice mail product, a rule might be assigned that does not allow a customer to order voice mail unless they already have phone service.
Rules are invoked during the quote process. When users determine where to attach a quote item (either to an existing point in their customer hierarchy, or to another quote item), the system uses the business rule adapter to determine and display only valid attachment points. Later in the quote process, once all disclosures are accepted, a CMI sends information regarding all quote items to the business rule adapter. At both points, the adapter validates all given items against all existing rules. If any quote item relationship violates a business rule, a warning is displayed.
3.11.1. Rule Templates
The CSP creates rules in the Administrator Console using templates. Within each template are parameters that are defined by specific data-for example, the vendor product the rule is created for.
(1) Template Descriptions
Following are descriptions of each of the business rule templates. Parameters whose values must be determined to create a rule are placed between the brackets [ ].
Template 8
Rule Statement: Any hierarchy item described as an [anchorDescriptor] can have between [min] and [max] relatives of [correspondentRelationship] which are described as a [correspondentDescriptor].
Rule Example #1: A business access line must be attached to an account.
Rule Example #2: Nothing can be attached to a custom calling feature.
Template 9
Rule Statement: At any time when a hierarchy item described as [anchorDescriptor] is in the state [anchorState] it must have at least one relative given by [correspondentRelationship] which is described as [correspondentDescriptor] and is in the state [correspondentState].
Rule Example: Whenever a voice mail product is effective, it must have a sibling call forwarding product that is also effective (i.e., voice mail requires call forwarding).
Template 10
Rule Statement: At any time when a hierarchy item described as [anchorDescriptor] is in the state [anchorState] it cannot have any relative given by [correspondentRelationship] which is described as [correspondentDescriptor] and is in the state [correspondentState].
Rule Example: Two voice mail products cannot be siblings and be effective at the same time.
Template 11
Rule Statement: At any time when a product described by [anchorDescriptor] is in the state [anchorState] it cannot have any relative given by [correspondentRelationship] which is described by [correspondentDescriptor], has the same vendor product OID, has the same [parameterToMatch], and is in the state [correspondentState].
Rule Example #1: Two voice mailboxes with the same mailbox number cannot be assigned to the same parent and be effective at the same time.
Rule Example #2: Only one of each type of custom calling feature can be assigned to an object and be effective at a time.
(2) Descriptors
Often a rule does not apply to one object but to a group of similar objects. For example, in the following rule:
Voice mail must be attached to an access line
there may be many vendor products that are defined as voice mail and many other vendor products that are defined as access lines. Descriptors are used to create groupings of objects or groupings of other descriptors.
3.12. Paying Non-Recurring Charges
The system allows users to pay for any non-recurring charges (i.e. one-time charges) by credit card. Once all credit card information is entered, a CMI sends that information, along with the total dollar amount to an external system, for authorization. The external system then returns authorization messages that can be displayed to the user. The CSP may need to create new CMIs specific to the CS P′s external payment system.
3.13. Notes
Notes are text-based messages that the user creates for future reference. Notes are associated with certain objects such as a quote or order which are created in different portals.
No matter in which portal the note was created, it retains an association with a specific root object. However, users can only view a note from the portal in which that note was created. For example, if a Universal Agent portal user creates a note regarding a partner, a Channel Partner Portal user also associated with that customer cannot view it. However, any other Universal Agent user that can view that customer's information can view that note.
Notes retain an association with the user who created the note, the date and time the note was created, and the comment (this is the actual note text).
Notes cannot be appended; that is, if a user wishes to add a comment to an existing note, they must create a new note comment. However, multiple notes can be associated with the same object.
3.14. Viewing Invoices
To display invoices, the CSP uses the API to import billing information from an external billing system into the invoice tables. Or instead of importing information for all billing points, the CSP can create a link to existing external invoices.
The INVOICE table holds imported header-type information, such as a reference to the account, date information, total amount due, and state information. The INVOICE_SUMMARY table contains the total charges for recurring, usage, and non-recurring charges, as well as tax, adjustment, and discount totals. Individual charge data is stored in the INVOICE_LINE_ITEM table. Invoice line items retain associations with the tables that contain the detailed information for each charge imported from the external billing system.
Once invoice information is imported, a user can view individual invoices (i.e. each month's invoice), past due balances aged at current, 30, 60, 90, and greater than 90 days, and payment history.
3.14.1. Disputes
When a customer or partner questions an invoice line item, an agent can raise a dispute. Disputes are handled in exactly the same way as trouble tickets.
3.14.2. Adjustments
Agent users can create billing adjustments when an error on an existing invoice has been found. Instead of actually creating an adjustment, the user creates a request for adjustment, which an external billing system then accesses, calculates, and returns to the system in the INVOICE_ADJMNT_ITEM table.
Adjustment reasons are pre-defined using constant classes, so that users can select the appropriate reason from a drop-down menu. The CSP can add reasons to this class as needed.
3.15. Reporting Trouble
The system allows users to report trouble for any object in the system by creating a trouble ticket (or in the case of an issue with an invoice, a dispute).
Users enter a description of the issue, including a detailed comment. After the information is submitted, the system's server dispatches a CMI to an external trouble ticket system.
As the external trouble ticket system resolves the issue, it notifies the server of each step taken towards resolution. A user can then view those steps. During this time, users can create additional comments associated with the trouble ticket. Agent users can resolve trouble tickets.
Users can also request cancellation of a trouble ticket. When this occurs, a request is sent via a CMI to the trouble ticket system. The external trouble ticket system must be configured to notify the system whether or not the trouble ticket is canceled.
3.16. Viewing Status
The system's server includes interaction models that allow users to view the past, present, and future steps related to business processes managed by external systems. For example, users can view the status of steps for the provisioning of order items and the handling of trouble tickets.
3.16.1. Interaction Models
Interaction models reflect the workflow that external systems use to complete a given task. Interaction model states reflect the individual steps within that workflow. When a user kicks off an event associated with a model, an instance of the model and an instance for each of its states are created, specific to that user's event. As the event travels through the external workflow, the status is passed back to the system. (The configuration of the external workflow determines how the status is passed back.) At this point, the status for the current model instance state is updated. Once a state reaches a status of complete, the completion date is populated for that state, and the next state (specified by the display order), becomes active.
For example, an external provisioning workflow for an access line might have the following steps: (1) Provision access line; (2) Line set up; (3) Establish external service; (4) Establish internal service; (5) Test tine; and (6) Provisioning complete
The CSP would create an interaction model named PROVISION_ACCESS_LINE and then create states for each of these steps.
3.16.2. End-User Views
For users to view the status of each state, the CSP creates end-user views that correlate to interaction models, and end-user view states that correlate to interaction model states. Together, these allow users to see pending, in progress, and completed steps for an interaction model instance in language they understand. The CSP can create multiple views for one model to reflect the different portals that can access the data.
Referring to Table 3.1, for example, the interaction model for provisioning an access line might have two views—one for the Small Business Portal viewed by customers, and one for the Universal Agent portal.
Dates can be associated with end user views to determine when they are valid. This way, if the CSP needs to change an interaction model, any user associated with a model instance that has not completed all steps is shown the view for the model as it was before the CSP changed the model. However, any new instances of the model are shown the new end-user view.
3.17. Viewing Notices
The CSP can create an information queue to display pertinent news and product information to a specific object in the customer hierarchy. For example, the CSP could create a notice about an outage and only show it to affected accounts.
Content items are the actual items that the CSP creates for display. They can contain a reference to a specific offer. The CSP can also set the maximum amount of times the content item is shown. For each content item that CSP creates, the CSP must also create a target. The target determines who sees the notice. The system's server keeps track of each time the content item is shown to a specific target, and also each time that target clicks through to view the associated offer (if applicable).
3.18. Reports
The CSP can generate reports using the system's definition files pulled from the database. The definition files include: (1) Financial Bookings (Universal
Agent portal only), which shows monthly recurring and non-recurring charges for a provider's customer and partner base; (2) Financial Bookings for a partner, which shows monthly recurring and non-recurring charges for one Partner; (3) Financial Forecast (Universal Agent Portal only), which shows forecast recurring and non-recurring charges based on orders placed but not yet completed, for a provider's customer and partner base; (4) Financial Forecast for a partner, which shows forecast recurring and non-recurring charges for a partners products; (5) Orders Past Due, which shows all past due orders for a partner.
From Crystal Reports, the CSP can edit these definition files or create its own to suit its needs. When the CSP generates these reports, it needs to save them using a standardized report name.
Section 4. Small Business Portal
One embodiment of the invention is the Small Business Portal (SBP) that allows customers, either business or residential, to manage their accounts with a provider. SBP users can use the portal to shop for products and services, manage these services, and report and track trouble tickets and disputes.
In this section, “CSP” refers to a communications service provider from whom the customers purchase products and services to resell. CSP deploys the SBP to enable its customers to manage their accounts.
The “customer” refers to other organizations and individuals who purchase products and services from the CSP.
The “user” refers to any user of the SBP. These users will typically be either residential or small business users or personnel at the customer organization. There are two kinds of users: Users and Administrator Users. These two kinds of users have different authority, which is discussed in more detail in the following subsections. For the purposes of this document, the term user will refer to a user with all authority.
3.1. The Small Business Portal
3.1.1. Logging In
The SBP user logs in using a user name and password. By default, two security levels are supported:
The CSP creates the first user (typically an Administrator) for a customer via the Universal Agent portal, or customers can register themselves. Once at least one administrator user is created for a customer, either by the provider or the customer, that user may then in turn create other users.
3.1.2. Self-Registering
A new customer may self-register by clicking the “New User Register Here” link from the splash page. Clicking this link takes the new customer to a page that prompts them to the Create User page, where they enter a user name and password. By default, new users have customer administrator authority.
Once they have created this information, they can create customer information by clicking on the “Accounts” link in the My Menu navigation bar. A new customer may shop (they will be shown the menu for the default price group) without creating customer information, but will be prompted to enter the information when they attempt to create an order from their cart.
3.2. Small Business Portal Home
After a SBP user logs in to the portal, he sees the customer homepage, called My Home. This page contains the following areas:
(1) The main navigation bar, which is visible throughout the SBP and allows the user to navigate to the following areas:
(2) The My Menu Navigation Bar, which sits below the main navigation bar and contains the following:
The My Home page also contains the following:
A customer can use the SBP to shop, select, configure and order products. Ordering products in the SBP consists of the three stages: (1) shopping; (2) creating and configuring items in a quote; and (3) Ordering the items in a quote.
The following subsections detail how the SBP implements this life cycle, and the options available to SBP users. The SBP user begins shopping by clicking the “Browse Catalog” link in the main navigation bar on the My Home page.
3.3.1. Menus
Menus are navigable lists of products offered for ordering. In the SBP, the user shops product menus, then chooses and configures offered products.
Menus typically break product offerings down into categories desired to be presented by the licensee such as “Business Services” and “Residential Services”.
When the user is browsing the product menu he will see a set of product offerings determined by their assigned price group. The price group determines the root menu and prices for each offer. If a user browses the menu before registering, he is shown the root menu and price associated with the default price group.
The SBP shows a “breadcrumb” displaying the path thus far taken through the hierarchy. The user can click back at any link in the chain to return to the menu at that level.
3.3.2. Offers
The offers in menus are listed with a brief description and an “Add to Cart” button.
(1) Offer Detail. When the user shops and finds an offer they wish to purchase, they can choose to drill in to the offer detail page by clicking on the product name link. The detail page displays the name of the offer, itemized prices for recurring, non-recurring and usage charges, and any related offers. The user can then add that product to the cart then continue shopping.
(2) Related Offers. When viewing an individual offer via the detail page, the user is shown related offers if any exist. Related offers are offers that have some connection or marketing synergy with the offer being viewed. Both related offers are displayed on the detail page as links. These related offers can themselves be drilled into from the first offer's detail page.
3.3.3. Offer Collections
Since simple, one-product offers may not be sufficient to meet a providers product offering requirements, the system allows for individual offers to be bundled together into offer collections. Offer collections (and also simple offers) are configured in the Administrator Console.
To select an offer collection for purchase the user must click the “Add Bundle” link for that offer and then select which options for that collection they wish to purchase.
If the offer collection is fixed, then all offers in the collection will be automatically selected; no choices can be made.
If the collection is dynamic, the user is guided through the collection's determinants where the user selects the individual offers that will make up the collection. At any point in this process, the user can go back to a previous determinant to select a different offer. The navigation path through the collection, as well as the determinants used and the offers included are all configured through the Administrator Console.
3.3.4. Shopping Cart
As the user selects offers for purchase, they are placed in the shopping cart. At any point in the shopping process, the user can view their shopping cart by selecting the “Cart” link from the My Menu navigation bar in the My Home page. This is a view of all products that have been selected for ordering, their total recurring and total non-recurring charges, the quantity currently selected for quote and a text field to input an updated quantity. The user may also remove items from a quote by checking the remove button and clicking the “Update” button.
3.4. Quotes
3.4.1. Creating Quotes
When the user has shopped and selected all the desired products, clicking “Checkout” takes the customer to the Choose Quote page. The customer can then select an existing quote or click the “Create Quote” button to add the items to the cart to create a quote from the current shopping cart. All of the items that were in the cart now appear as quote items in the Quote Summary page.
3.4.2. Managing Quote Summaries
The Quote Summary page shows all the items in the user's quote. The top of the summary page shows the quote number, creation date, and status. The user can also enter a master purchase order number, a brief description, and an e-mail address.
Items in a quote display the item number (ordinal number of item in quote) product offer name, the action for this item (i.e., add, remove, change, etc.), the purchase order number (if one was provided), the status (configured, pending configuration, etc.), the price for recurring and non-recurring charges, and a checkbox with which the user can remove items from the quote. If the user removes any items from a quote, they must click “Update” to commit those changes. If there are more items than will fit on one page, a pair of previous/next links allows users to navigate between pages.
The user can hold or cancel the quote, shop more, continue the quote—to-order process.
Holding a quote allows a quote to be held in its current state and then re-opened to order at a later time. Once held, it is persisted. Within this time frame, the user can re-open a non-expired held quote at any time and continue working on it by shopping more, configuring items, ordering it or canceling it. After a quote expires, it is no longer available for ordering, but will still appear in and be viewable via the quote history as an “expired quote”.
Held quotes are displayed in the current quote history, available from the activity history area on the My Home page.
Canceling a quote causes the quote to become inactive, but it will continue to be viewable as a “Canceled quote” in the quote history. Canceling a quote stops the ordering process and moves the current quote to state “Canceled”. Canceled quotes can always be viewed from the quote history available from the My History menu.
3.4.3. Configuring Quote Items
Before quote items can be purchased and moved to order items, they must be configured. Configuration is reached by selecting the “Configure” link which is next to every quote item requiring configuration. If the user attempts to click
“Continue” without configuring all quote items, the SBP will prompt for configuration information for each unconfigured item in the quote.
The following attributes are configured in a quote:
(1) Service Start Date. Users can choose to accept the earliest possible start date for a quote item, or select another date (as long as the date they select is not earlier than the earliest possible date). The earliest possible start date is calculated from the Service Level Agreement between the CSP and the User.
A constraint on service start dates arises when a quote item is attached to an existing quote item. Users cannot select a start date for a dependent product that is earlier than the start date selected for its parent product.
(2) Service Address. For some offers, Users must input information for the service address. This associates the product to a physical location, typically a customer address.
(3) Selecting Service Identifier. Users must select a service identifier (a telephone number for access line, for example). The system uses a plug-in which can be interfaced with an external system to retrieve a set of service identifiers from which to choose.
(4) Product Association. The user must also attach each quote item either to a place in the customer's hierarchy or to another item in the quote. The determination of which hierarchy objects or quote items are valid attachment points is handled by the business rules engine.
(5) Product Parameters. Finally, the user must provide values for product parameters (such as number of rings before voicemail picks up, guaranteed level of service, etc.). What parameters are required is an attribute of the offer's associated vendor product. These parameters are defined in the Administrator Console.
3.4.4. Automating Quote Item Configuration
In addition to manually configuring quote items, users can take advantage of features of the Smart Component Server to streamline the quote configuration process, pre-population.
Certain offered products can be set up to have values for their parameters pre-populated when they are added to a quote. By default, when an offer item moves from a cart item to a quote item, a plug-in can then give pre-populated values to certain product parameters. By default, various parameters can be pre-populated: For examples: attachment point, service identifier, and start date.
The parameters to be pre-populated are determined by the PreConfigure*.java plug-ins. By default, the pre-populated values for product parameters are taken from the default values specified when the offer was configured in the Administrator Console.
Other parameters can be pre- populated as follows:
Once the user accepts the pre-populated configuration information, they can at any time before ordering the quote go back and modify the configuration of individual quote items which were pre-configured.
3.4.5. Disclosures
Offer items in the quote have disclosures associated with them which communicate legal or other information the customer must agree to before purchasing. All associated disclosures for quote items are displayed and the user must accept them before the quote can proceed.
3.4.6 Negotiated Quotes
Once all the configuration described has been completed and disclosures have been accepted, a quote reaches the “quoted” stage, and the display updates to reflect this by bringing the user to the Negotiated Quote page. Once a user elects to order a negotiated quote, all quote items become order items.
(1) Prices of Held Negotiated Quotes. Once a quote reaches the negotiated stage, the price for that quote is fixed. If the user holds the quote, and prices for offers ordered in that quote and for that customer's price group should change, the quote will remain at the price at which it was held. The held negotiated quote information is persisted the same way as a held quote summary, except that a held quote summary will be repriced every time it is accessed.
(2) Modifying a Negotiated Quote. Selecting “Modify Quote” brings the user back to the quote summary page. All of the user's previous configuration information is preserved, and they can make any changes they wish. They then can proceed with ordering the quote.
3.4.7. Orders
Once in the Negotiated Quote page, the user can create an order. Offers which represent equipment (cell phones, pagers) which are physically delivered to a customer are called delivered products in the SBP. When purchasing a quote containing one or more delivered products, users are required to single shipping address into the Shipping Address page to which all delivered products in the quote will be shipped.
If there are no offers corresponding to delivered products in the quote, then no shipping address is required.
Clicking the “Order Now” button in the Negotiated Quote or Shipping Address page takes the user to the Payment Option page. At this point the customer can select to either add the charges for the order to a bill, or to pay immediately via credit card. If the user chooses to pay by credit card, they are taken to the Make Payment page where they provide credit card and billing address information. When they have entered the credit card information and clicked the “Order Now” button a CMI sends all credit infor to an external system for approval and the user is taken to a confirmation page.
3.5 My History
Users can view history information from the links in the activity history section of the My Home page. The user can choose from orders, quotes, or trouble tickets. Choosing one of these categories brings up the history page for that item. Depending on the type of item whose history the user is viewing, they may take different actions.
3.5.1. Order History
SBP users can view a history of service orders from the My Home page. The following information is returned for each item on the order history page: Order number; Date Created; Description; One-time Charges; Recurring Charges; and Status.
(1) Order Detail. By clicking on the order number, the user can then bring up a detail of the order from which they can also request to cancel or reorder the quote. This page lists:
Each order item in the list displays:
The detail page for an order item displays: product name, purchase order number, totals for one-time and recurring/monthly charges, and all the configuration information which was determined when that item was configured in a quote.
(2) Request to Cancel an Order. Canceling an order is not guaranteed to completely cancel all products ordered. Since the system relies on external systems to handle provisioning, it is possible that an ordered item can already be provisioned at the time the user is requesting cancellation, but that the new state information has not been communicated to the system. Therefore, canceling an order from the order detail page simply requests a cancellation and sends the appropriate CMI to the external system. If the external system is successful, the order will be canceled and the state reflected in the order history.
(3) Reordering. When the user selects “Reorder” from the Order Detail page, they are brought to the Quote Summary page for a new quote, populated with any items which were in the original order having an action of “Add”. This prevents reordering any items which were in the original order as upgrades, or which were removed, changed suspended or resumed. The items in the re-ordered quote are in a pre-configured state, but the user can then change the configuration of the quote items. They then can resubmit them as a new order, leaving the original order unchanged.
3.5.2. Quote History
Users can view quotes from the quote history available from the My Home page in the activity history. For each current quote, the quote history page displays: Quote number; Date Created; Description; Status; and Detail.
A user can also view ordered, expired and canceled quotes. The user can switch between these categories via links on the main quote history page.
(1) Quote Detail. The user can view a detail page for a quote by clicking the “View Detail” link in the history list. The detail page summarizes the data displayed in the history entry, and also shows a list of every item in that quote. As in quote summaries, the user can also request to hold, cancel, modify, or order the quote from this page.
For each item, the quote detail displays:
Users can view payments in the payment history page. This page is accessed via the “Payments” link in the “My History” menu in the My Home page. For each current quote, the payment history page displays: Date; Amount; Status; and Details.
The user can view a detail page for a payment by clicking the “View Detail” link in the history fist. For each payment, the Payment Detail page displays:
Past trouble tickets are viewed via the trouble ticket history link in the My Home page.
The following information is returned for each item on the Dispute History page:
The dispute detail page lists:
Past trouble tickets are viewed via the trouble ticket history in the My Home page.
The following information is returned for each item on the trouble ticket history page:
The ticket detail page lists:
Accounts allow the CSP's customers to segment their business into logical units such as geographic location or department. The My Home page provides the SBP user with a list of all of their accounts in the My Accounts section. The list gives the name of the account, its status, and a link to view products for that account.
Clicking on the account name brings the user to the account detail page, where they can view all information pertaining to the selected account such as billing address, credit information, and the names of any contact personnel assigned to the account.
A drop-down menu at the top allows the user quickly to switch to other accounts, which then displays that account's information. From the account detail page, the user can:
Users of the SBP can create accounts from the My Home page by clicking the “Add Account” link. The user must provide an account name, billing address and credit information for every account they create. Once created, the account will be displayed in the list of accounts on the customer accounts page.
3.6.3. Managing Products in an Account
From the account management page the user can view products and services provisioned to a particular account by clicking the “view the products” link next to that account.
This leads to the My Products page, which displays a hierarchical view of all products provisioned to that account. Arrows next to products allows the user to click to expand or collapse that level of the product hierarchy.
Clicking on the name of a product brings the user to the detail page for that product.
(1) Product Detail Page. For assigned products, the detail page shows the name of the product, a brief description, the date the product was provisioned, and a summary of the configuration information. Any contacts assigned to this product are also visible, as is a link to add new contact information.
The user can then perform the following operations to manage the product hierarchy, for assigned products only: (a) upgrade; (b) remove; (c) report trouble; and (d) reorder.
For delivered products, users may only report trouble and add/remove contacts.
(2) Modifying Products. The user modifies an assigned product by clicking “Modify Product” from the assigned product detail page. Since an external provisioning system must be used to make the desired modifications to a provisioned product or service, the SBP implements product modification as an order. Modifying an assigned product takes the user to the Quote Summary page for a new quote, consisting only of the product to be modified.
From this new quote detail, users can then configure any parameters including a “start” date when the modification will take effect as well as any other product parameters, service identifier, etc. The user can then submit the quote.
(3) Removing Products. The user can request to discontinue an assigned product by clicking “Remove Product” from the assigned product detail page. Once again, since an external provisioning system must be used to remove a product, the SBP implements product removal as an order. Removing a product brings up the quote summary page of a new quote, consisting only of the product to be removed.
The only configuration possible for this removal quote is the termination date. Analogous to the service start date selected when ordering the product, the user can choose the earliest possible date or a specific date, as long as the date chosen is not earlier than the earliest possible date.
(4) Upgrading Products. Product upgrades are initiated from the detail page for the provisioned product to be upgraded. Which product offers are on a given product's upgrade path is configurable through the Administrator Console. Once an upgrade product is chosen, that new product is quoted and ordered like a normal product offer. Once the upgrade order is complete, the new offer instance replaces the original.
(5) Reporting Trouble. The user can raise a trouble ticket on a product.
(6) Reordering. When the user selects “Reorder” from the product detail page, they are brought to the Quote Summary page for a new quote, populated with an order item corresponding to the product being reordered. The item in the quote is in a configured state, but the user can then change the configuration. They then can re-submit them as a new order.
3.6.4. Customer Details
The customer detail page presents the SBP user with a summary of their customer information. The page displays customer information, resale authority, address, and contacts. The user can also view their customer history, modify their address information, raise a trouble ticket, or add, modify, and remove contacts. Customer history consists of any changes made to customer information such as mailing address.
(1) Modifying customer Information. The SBP user can click the “Modify Customer Information” link on the customer detail page to provide new or updated address information.
(2) Reporting Trouble. The user can raise a trouble ticket on an account.
(3) Adding and Removing Contacts. The process for adding, modifying, and removing contacts for a customer is identical to the process for adding contacts to an account.
3.6.5. About Contacts
Contacts are individuals in the customer's organization who are assigned responsibility for various aspects of the customer's relationship with the provider. Users of the SBP may assign contacts to customers and accounts.
When adding a contact, the user must provide a name, address and telephone number. Contacts are of a particular type such as “primary” or “technical”. Users of the SBP can assign as many contacts as they desire. There can also be multiple contacts of a given type. What contact types are defined is determined by a constant class which may be changed.
Customer contacts are displayed on the customer, account, and product detail pages, where the user can add new contacts, modify an existing contact, or remove an existing contact.
3.6.6. Managing Bills
The Invoice Summary page presents the SBP user with a summary of their billing information. Clicking on the “View Bills” link next to the account name in the My Home page brings the user to the Invoice Summary page, where they can view billing information pertaining to the selected account.
Drop-down menus at the top allow the user quickly to switch to other accounts and other billing cycles, which will then display in this page. From the Invoice Summary page, the user can view detail pages about: One-time Charges; Monthly Charges; Usage Charges; Adjustments; Discounts; and Taxes.
The user can create a billing dispute by clicking on the “Open Dispute” button.
3.6.7. Managing Users
SBP users with administrator authority can create other users for their customer account from the manage users area of the customer My Home page.
The user must provide a user name, password, and password hint. They must also select the authority level. The two authority levels and their default permissions are:
An SBP user of sufficient authority can also remove existing users by checking the Remove radio button and clicking the “Update” button. The selected user is then made inactive and will be unable to log in to the SBP.
3.7. Creating Trouble Tickets and Disputes
3.7.1. Issuing Trouble Tickets
Users of the SBP can issue trouble tickets against the following items by clicking the “Report Trouble” link on the following detail pages: (a) customer; (b) account; (c) provisioned product; (d) delivered products; (e) composite product.
The trouble ticket is date-stamped and marked with the ID of the SBP user submitting it. The user must supply contact information for the customer making the trouble report and specify a category or reason for the report. The user must also include a detailed text description of the problem, and any recommended action.
Once the user has provided all the information required for the ticket and submitted it, the Trouble Ticket Detail page displays a summary of the ticket.
3.7.2. Creating Billing Disputes
Users of the SBP can create billing disputes against invoices by clicking on the “Open Dispute” button in the Invoice Summary page.
The new dispute is date-stamped and marked with the ID of the SBP user submitting it. The user must supply contact information for the customer making the trouble report and specify a category or reason for the report. The user must also include a detailed text description of the problem, and any recommended action.
Once the user has provided all the information required for the dispute and submitted it, The Dispute Detail page displays a summary of the dispute.
3.8. Manual Approval
The SBP allows administrators at the provider site to manually set the status of order items, account requests, and customer requests. This is useful in testing or in deployments which do not use external systems for provisioning or trouble ticketing. By default, the SBP allows a licensee to set the “pending”, “rejected”, and “complete” states, plus the “canceled” state for an order item.
The CSP must launch the approval screens from a new browser. The following URL will bring up the approval sign-in page:
http://<hostname>:<port_number>/go?to=UA_ApprovalSignin&from=nafrom&task=naTask
In this URL, replace <localhost> and <port_number> with the appropriate values for the CSP's Smart Component Server deployment.
At the sign-in page, enter the following login information, entering each token exactly as it appears after the colon:
This user has Licensee_Admin level authority. Do not give this user name to anyone who should not have this authority.
The CSP will then see the approval menu which contains the following:
Each of these menus presents a list of items (appropriate to the menu chosen), their item number, the date the item was created, the current status, and radio buttons allowing the CSP to alter the state of the item. Once the CSP have made the desired modifications, clicking “Update” will commit those changes and change the state of the items within the system.
Section 5. Universal Agent Portal
One embodiment of the invention is the Universal Agent Portal (UAP), which allows users (customer service representatives, sales agents, or other administrative users) at a communications service provider (CSP) site quick access to customer and partner data, enable them to create and modify customers and partners, shop for products, report trouble, and perform many other functions offered in the eBusiness support system on behalf of customers and partners.
5.1. Navigating the UAP
The functionality available in the UAP can be broken down between the user home page and customer home page. The user home page is displayed after a UAP user have logged in to the portal. Much of the functionality in the UAP is only available once the UAP user has selected a customer or partner with whom to work. This is referred to in this document as making the customer “active”. Different navigation controls are available at different points in the portal.
5.1.1. Starting the UAP
First start the Smart Component Server; then open a browser and navigate to the following URL
http://<webserver>:<listen_port>/go?to=UA-Signin&from=nafrom&task=naTask
When the splash Page appears, enter the user name and password and click “SIGN IN” to log in to the portal.
5.1.2. Main Navigation Bar
The Main navigation bar appears at all times, regardless of whether a customer or partner is active and allows the UAP user to navigate to the following areas:
The customer/partner navigation bar is active throughout the portal whenever a customer or partner is active. This navigation bar allows the UAP user to navigate the following locations:
This bar is visible throughout the portal and contains the following links:
Universal Agent Portal users are those who access the eBusiness support system through the Universal Agent Portal. Each UAP user has a unique user name/password combination that provides authentication within the system.
5.2.1. Agents
It is necessary not only to restrict the functionality available but also the data visible to the different types of UAP users. The primary motivation is to protect customer/partner data from inappropriate or inconsistent modification. The system implements this data-level security via agents. Agents are distinct from users, but every UAP user is also of a particular agent type. The following three agent types are defined, by default: (a) CSR; (b) Sales Agent; and (c) Administrator.
Sales Agents are subject to visibility restrictions. CSRs and Administrators are exempt from these restrictions. New agent types can be created by modifying the appropriate constant class. A user's agent type affects what data they can see when executing customer searches. When searching for customers or partners, a plug-in runs and examines the agent type of the user executing the search. The default behavior of the plug-in is as follows:
If the agent executing the search is of agent type CSR, or Administrator no check is made to agent group visibility table.
Otherwise, the table is consulted, and the data returned is restricted according to the visibility rights granted to the agent.
5.2.2. Agent Groups
Agents are further associated into groups. An agent group may be a geographical division (East Coast office, West Coast office, etc.) or by agent's last name, or any other division. Agent groups, and group visibility are what implement the data-level security. UAP administrator users can create new agent groups.
5.2.3. Creating Users and Agents
By default, only administrators can create new UAP agents. The “manage agents” link from the user navigation bar brings the UAP user to the manage agents page. Here, the UAP user is presented with a list of existing agents, which the UAP user can view or modify. The “CREATE” link allows the UAP user to create a new user and the associated agent.
The UAP user must provide a name and password for this user. This name and password is stored with the user. The UAP user must also select an agent type and a security type (one of Administrator or User) and must enter contact information (name, phone, email, pager, etc.) for this agent.
From the Agent Group Assignment page, the UAP user must assign the agent to one or more groups. Finally, the UAP user must make visibility assignments for this agent. Giving an agent visibility into a group allows that agent to see all customer data associated with members of that group.
5.2.4. Managing Agent Groups
The “manage agent groups” link from the user navigation bar brings the UAP user to the manage group page where the UAP user can create, modify or remove groups.
The Manage Groups page shows the UAP user a list of all agent groups, and allows the UAP user to remove, view or modify them, or to create a new group.
Note that the UAP user can assign entire groups as members of a group, so that the UAP user could, for example, create a group called “North America” and assign the groups “East Coast;’ “West Coast”, and “Midwest” to it.
An agent group may be removed from the system. Agents or agent groups that were members of, or had visibility into the removed group continue to exist. When a group is removed, all agents who had visibility into that group and could see its associated data will no longer have that visibility. This can cause agents to be unable to see the customer data they require.
5.3. The User Homepage
Once logged in, a UAP user are presented with the User Homepage. The UAP user see any news and information targeted to the UAP user, the user navigation bar, and the search pane.
5.3.1. Agent Visibility and Customer Data
What data is visible to the UAP user depends on the following criteria:
(1) Certain agent types are exempt from these visibility rules. The choice of which agents are subject to/exempt from visibility rules is made by a plug-in whose default behavior exempts agents of type CSR or Administrator. All other agent types (that is, Sales Agent) are subject to the visibility restrictions.
(2) The UAP user's agent group and agent group visibility assignments affect what customer data is visible to the UAP user. When executing a search for a customer/partner or a related item, the set of data against which the UAP user search is executed is determined by the UAP user's agent group visibility.
5.3.2. Selecting an Existing Customer
Much of the functionality offered in the UAP is only available when the UAP user has made a customer (or partner) “active”. In order to select a customer or partner, the UAP user must perform a search. By selecting a customer or partner from the search result set, the UAP user activates that customer or partner active.
The UAP allows users to search for customers and partners using the attributes of: (a) Customer Name; (b) Customer ID; (c) Customer Contact Phone Number; (d) Customer Contact First Name; (e) Customer Contact Last Name; and (f) Assigned Sales Agent (sort by first and last name individually).
Searches may also be made ascending or descending. Once a customer is selected and made active, the agent is brought to the Customer Homepage.
5.3.3. Searching for Related Items
The UAP user can execute searches for objects other than customers. A dropdown menu on the search pane controls which type of object the UAP user are searching for. Changing this drop-down causes the search pane to redraw with input fields for search criteria appropriate to that object. Once the UAP user specify values for the search criteria, executing the search returns a set of matching items (if any). Selecting an item from the result set causes the associated customer to become the active customer, and replaces the current active customer/partner.
The search then brings the UAP user to the appropriate detail page for that item (product detail page for a provisioned product, trouble ticket detail for a trouble ticket, etc.). With a customer or partner active, the UAP user can also navigate to pages for trouble ticket, product, and service order from the customer/partner navigation bar. These searches will only be against data specific to the active customer or Partner.
The UAP user can execute searches for the following types of items from the user home page:
(1) Product Instance. Search on and Sort on: (a) Product Name; (b) Service
Identifier (e.g., telephone number); (c) Customer Name; (d) Customer ID; (e) Partner-Customer ID; and (f) Requested Due Date. Search on only: (a) Service Street Number; (b) Service Street Name; (d) Service City; (e) Service State/Province; and (f) ZIP/Postal Code.
(2) Service Order. Search and Sort on: (a) Order Number; (b) Purchase Order Number; (c) Order Status; (d) Assigned Sales Agent; (e) Customer Name; (f) Customer ID; (h) Partner-Customer ID; (i) Expedite Flag; and (j) Date Created. Sort on only: (a) Agent First Name; (b) Agent Last Name
(3) Trouble Ticket. Search on and Sort By: (a) Ticket Number; (b) Ticket Status; (c) Customer Name; (d) Customer ID; (e) Partner-Customer ID; (f) Ticket Contact Name; and (g) Date Created.
When the UAP user finishes working with a customer or partner, the UAP user can choose to release the customer or partner, by selecting the “RELEASE CUSTOMER” link on the main navigation bar. Doing so will remove everything related to that customer/partner from the current session and return the UAP user to the user home page.
The UAP user need not explicitly release a customer or partner from being active. Selecting a new active customer or partner from a customer search result set will automatically make the newly selected customer active in lieu of the original one.
5.3.4. Bulk Pre-Qualification
Some services may require pre-qualification before they can be provisioned. The UAP allows the UAP user to create and submit requests for bulk pre-qualification of customers to an external system.
From the user navigation bar, the UAP user can select “bulk pre-qualification”. The bulk pre-qualification page allows the UAP user to browse for and select a file containing information needed to qualify a group of customers for a product. The UAP user must give a name to the request and an email address that will be notified when the request has been processed. The UAP user can then submit the request.
5.4. Registering New Customers/Partners
5.4.1. Creating Customers or Partners
Any UAP user can create customers and partners. The process is slightly different for the two entities.
(1) Creating Customers
When creating a customer, the UAP user enter relevant information such as mailing address and company name. Also, if there are any profiles defined the data required for the profile is captured. The UAP user can also specify: (a) a document URL that points to contracts or other documentation relevant to this customer; (b) a price group for the customer; and (c) an assigned sales agent.
(2) Creating Partners
For partners, additional information is captured during creation. Most notably, partners are often only allowed to resell services in certain geographical areas. Hence, the UAP user must select from a list of (configurable) geographical regions and indicate explicitly in which regions the new partner is authorized to resell services. For partners, the particular partner program in which this new partner is enrolled is called “partner level” This is simply the implementation of price group for partners. In addition to a document URL (which for partners might contain a link to legal or other contractual documents for the partner), the UAP user specifies a URL pointing to the Partner Logo image. This logo is used in the Channel Partner Portal to re-brand the interface for the partner user.
(3) Profiles
Profiles provide a way to capture various demographic or marketing information for a customer or partner at the time that customer is created. What information is gathered is entirely configurable through the Administrator Console.
(4) Assigning Contacts
During the registration process, the UAP user is prompted for information for a contact.
(5) Creating a User
Finally, the UAP user create a user for the customer or partner just created. The UAP user specifies a user name and password, a password hint, and selects a user type. It is this name and password that allows customers to log in to the Small Business Portal and partners to log in to the Channel Partner Portal to manage their partner relationship on their own behalf.
(6) Assigning Support
The UAP user can also assign support resources from the UAP user's organization to a customer.
5.4.2. Creating Accounts
Customers and partners have associated accounts. Once the customer or partner is created, the UAP user can then proceed to create one or more accounts, capturing the required name, address and credit/payment information. Referring to
The eBusiness support system relies on external systems to do the actual network provisioning of customers and their accounts and products. If there is no external system, all objects (customers/ partners, accounts, orders) will persist in a pending state until manually changed via the approval pages.
5.5. Customers/Partner Homepage
Once a customer/partner has been selected and made active, the UAP user is shown that customer or partner's home page.
This page displays the following:
The name of the customer/partner on the home page is a link to the customer/partner detail page. This page summarizes the information for that customer/partner (including resale authority for partners and customer address for customers) and allows the UAP user to modify the customer/partner information, report trouble, and manage contacts.
5.5.2. Accounts
On the customer summary page, the UAP user is presented with a list of every account associated with that customer. For each account in the list are the following links:
Once the UAP user have selected one of these links, each of the subsequent account-related pages has a drop-down menu containing all other accounts associated with this customer, allowing the UAP user to move from viewing information for one account to viewing information for a different account without needing to return to the customer detail page.
(1) Account Detail
Clicking the name of an account in the listing on the customer summary page brings the UAP user to the account detail page for that account. This detail page contains a summary of the account's information such as name, billing information, billing address, and credit information. Also listed are the contacts (if any) for that account.
The account detail page includes links which allow the UAP user to view history items for this account, modify account information, raise a trouble ticket on this account and add, modify or remove contacts for that account.
(2) Bills
Next to each account in the account listing on the customer summary page is the “Manage Bills” link which allows the UAP user to view bills for that account. This page presents a list of bills for the selected account, a drop-down list to select which billing cycle to view, and a drop-down menu from which the UAP user can select a different account whose bills are then displayed in place of the original account selected.
Selecting a bill from the list brings up the bill detail page, which gives a breakdown with subtotals for various types of invoice items, including: (a)
Monthly, or Recurring Charges; (b) One-time, or Non-Recurring Charges; (c) Usage charges; (d) Taxes; (e) Adjustments; and (f) Discounts.
The UAP user can then drill in to each type of charge and see a list of charge instances for that type and for that invoice.
(3) Accounts Receivable
In addition to viewing invoices, an “A/R” link next to each account in the customer summary list allows the UAP user to view past balances for a customer account, broken down into intervals of 30 days, 60 days, 90 days, and 90 days and above. The UAP user can then select a different account for the current customer and view that account's A/R balances as well.
(4) Creating an Account
Accounts can be created at any time from the customer summary page by clicking the “ADD NEW ACCOUNT” link. The UAP user must provide an account name, billing address and credit information for every account the UAP user create. Once created, the account will be displayed in the list of accounts on the customer summary page.
5.5.3. History
From the customer/partner home page, the UAP user can view history, showing events in the life-cycle of the customer to date. By default, a list of the last five history items is shown. If the agent wishes to view history information for a particular category, those histories are available from the navigation bar. These history items include the categories of: (a) Orders; (b) Quotes; (c) Payments; (d) Adjustments; (e) Disputes; and (f) Trouble Tickets.
From a history item link, the UAP user can then drill in to the specific item to view its detail page.
5.6. Shopping
The UAP user can use the UAP to shop, select, configure and order products on behalf of customers or partners. Ordering products in the UAP consists of the stages of: (a) Shopping; (b) Creating and configuring items in a quote; and (c) Ordering the items.
5.6.1. Price Group
Price groups are a mechanism by which the UAP user can segment the UAP user's customers, perhaps into “VIP”, “Executive” and “Standard” groups, for example. Price groups determine what products and what prices for those products are available to a given customer. The prices displayed throughout the shop process are determined by the active price group, but can later be negotiated or overridden. What price groups exist and their associated prices are both configured in the Administrator Console.
What price group is active when using the UAP is dependent on whether or not the UAP user have an active customer. If there is no active customer or partner, the default price group determines the associated product prices. If a customer or partner is active, then the price group for that customer (which was assigned when the customer or partner was created) determines which associated prices are displayed.
5.6.2. Menus
Menus are navigable lists of products offered for ordering. In the UAP, the UAP user shop product catalogs, and choose and configure offered products for the customers or partners on whose behalf they are acting. Menus typically break product offerings down into categories such as “Business Services” and “Residential Services”. What categories exist and what offers are available through them is configured through the Administrator Console.
(1) Default Menu
When the UAP user are browsing the product catalogue with no active customer or partner, the UAP user will see a set of product offerings determined by the parameter customer.defaultInternalUserRootMenuOid in the properties file. Once a partner or customer is active, and that partner's price group becomes active and in turn determines the root menu the UAP user see when shopping the catalog. The contents of all menus, including the default menu is configurable through the Administrator Console.
(2) Alphabetical Product Index
In addition to the hierarchical menus, the UAP user can also locate products by name. Selecting a letter from the alphabetical index will bring the UAP user to a menu of products beginning with that letter. The names on which the UAP user search are taken from the menu item label, in the DISPLATTRIBS table entry for that menu item.
(3) Breadcrumbs
While browsing the hierarchical menus (but not while viewing an alphabetical list), the UAP shows a “breadcrumb” displaying the path thus far taken through the catalog. The UAP user can click back at any fink in the chain to return to the menu at that level.
5.6.3. Offers
The offers in menus are listed with a brief description (from the DISPL_ATTRIBS table entry for that menu item), the total price for recurring rates and for non-recurring charges, a field displaying both the current quantity in a quote and a field for entering a different quantity.
When the UAP user shops and finds an offer the customer/partner wishes to purchase for a customer, the UAP user can choose to drill down to the offer detail page. The page displays the name of the offer, a list of which price groups can purchase this offer, itemized prices for recurring, non-recurring and usage charges, and any upsell or related offers. The UAP user can then specify a quantity of the product to be ordered, just as in the order's line-item in the menu page.
Whenever the UAP user changes the quantity of an item to be purchased, either from the menu page or the offer detail page, the UAP user must click “UPDATE” to save the new quantity before moving to a new page, This commits the items the UAP user has selected to the shopping cart, which can be viewed at any time by selecting “quote preview”. The UAP user can then continue shopping, perhaps in a different category of product offerings.
When viewing an individual offer via the detail page, the UAP user are shown related offers or upsell offers, if any exist. Related offers are offers which have some connection or marketing synergy with the offer being viewed. Upsell offers are related offers that might be interesting to the user.
Both related and upsell offers are displayed on the detail page in a one-line format similar to the offers on a menu page. These related offers can themselves be drilled into from the first offer's detail page, or the UAP user can specify quantities immediately for purchase.
For example, when the UAP user clicks on the Business Access Line product offer, the UAP user is taken to the offer detail page for Business Access Line. There, in addition to the Business Access Line product, the UAP user see various Upsell Products including: Business Voice Mail w/Pager Notification; Essential Bundle; and Business Messaging Bundle.
The UAP user can enter a quantity for purchase for any of these upsell offers and click “UPDATE” to add those offers to the customer/partner cart. Which offers are related to one another and which are on an upsell path is configurable through the Administrator Console.
5.6.4. Offer Collections
Since simple, one-product offers may not be sufficient to meet a providers product offering requirements, the system allows for individual offers to be bundled together into offer collections. Offer collections (as well as simple offers) are configured in the Administrator Console. Instead of selecting a quantity to purchase, as the UAP user does with simple offers, to select an offer collection for purchase the UAP user must click the “add Bundle” link for that offer and then select which options for the collection the UAP user wish to purchase. If the offer collection is fixed, then the UAP user will automatically select all of the offers in the collection; no choices can be made. If the collection is dynamic, the UAP user are guided through the collection's determinants where the UAP user select the individual offers that will make up the collection. At any point in this process, the UAP user can go back to a previous determinant to select a different offer. The navigation path through the collection, as well as the determinants used and the offers included are all configured through the Administrator Console.
5.6.5. Quote Preview
At any point in the shopping process, the UAP user can view a quote preview by selecting that link from the customer/partner navigation bar. This is a view of all products that have been selected for ordering, their total recurring and total non-recurring charges, the quantity currently selected for quote and a text field to input an updated quantity. As the UAP user select offers for purchase, they are placed in the quote preview. The quote preview is the UAP implementation of the shopping cart. The UAP user can adjust the quantity of remove items from the UAP user's cart.
5.7. Quotes
5.7.1. Creating Quotes
When the UAP user has shopped and selected all the products desired, clicking “CHECKOUT” creates a quote. All of the items that were in the UAP user's quote preview when the UAP user selected checkout now appear as quote items.
5.7.2. Quote Summary
The quote summary page shows all the items in the UAP user's current quote. The top of the summary page shows the quote number, creation date, status, last-modified user, and create user. The UAP user can also enter a master purchase order number, a brief description, e-mail address, select a sales agent, and either select an existing partner-customer ID or enter a new one (only if there is a partner active).
Partner-Customer ID is a field where the UAP user can store a partner's internal ID for their end-customers. When the UAP user is shopping on behalf of a partner, the partner can provide the UAP user with its end-customer's ID which the UAP user can then associate with the quote via this field.
Items in a quote display the item number (ordinal number of item in quote) product offer name, the action for this item, the purchase order number (if one was provided), the status (configured, pending configuration, etc.), the price for recurring usage, and non-recurring charges, and a checkbox with which the UAP user can remove items from the quote. If the UAP user remove any items from a quote, the UAP user must click “UPDATE” to commit those changes. If there are more items than will fit on one page, a pair of previous/next links allow the UAP user to navigate between pages.
The UAP user can hold or cancel the quote, add notes, shop more, or continue. Canceling a quote causes the quote to become inactive, but it will continue to be available as a “Canceled quote” in the customer's quote history. Adding a note to a quote allows the UAP user to attach an annotation to the quote that will then be visible to anyone else working with that quote in the UAP. Any notes created in the UAP can only be viewed in the UAP. Users of other e-Business portals cannot view or modify them.
If the UAP user chooses to “shop more” from the quote summary, the UAP user is returned to the product catalog. Any products the UAP user purchased now are added to the current quote.
5.7.3. Holding a Quote
Holding a negotiated quote causes the quote to persist for a period of time. The UAP user can re-open a held quote at any time and continue working on it by shopping more, configuring items, ordering it or canceling it. After a quote expires, it is no longer available for ordering, but will still appear in and be viewable via the quote history as an “expired quote”.
5.7.4. Canceling a Quote
Canceling a quote stops the ordering process and moves the current quote to a “Canceled” state. Canceled quotes can always be viewed from the quote history available from the customer/partner navigation bar.
5.7.5. Configuring Quote Items
Before quote items can be purchased and moved to order items, they must be configured. Configuration is reached by selecting the “Configure” link which is next to every quote item requiring configuration. If the UAP user attempt to click “CONTINUE” without configuring all quote items, the UAP will prompt the UAP user for configuration information for each item in the quote.
(1) Service Start Date
The UAP user can choose to accept the earliest possible start date for a quote item, or select another date (as long as the date the UAP user selects is not earlier than the earliest possible date).
The Service Level Agreement (SLA) is an attribute of the offer's associated vendor product, configured via the Administrator Console when product offerings are created. The SLA is added to the current date resulting in the earliest possible start date. This represents, for example, the amount of time it would take a technician to perform all the necessary network provisioning (perhaps including a customer premises visit) before the offered product is available for use. A constraint on service start dates arises when the UAP user attaches a quote item to an existing quote item. The UAP user may not select a start date earlier than the start date for a dependent product that is earlier than the start date selected for its “parent” product.
(2) Service Address
The UAP user must input information for the service address. This associates the product to a physical location, typically a customer address.
(3) Selecting Service Identifier
The UAP user must select a service identifier (a telephone number for access line, for example). The system uses a plug-in to interface with an external provisioning or telephone-number-inventory system to retrieve a set of service identifiers from which to choose.
(4) Product Association
The UAP user must also attach each quote item either to a place in the customer's hierarchy, or to another item in the quote. The determination of which hierarchy objects or products are valid attachment points is handled by the business rules manager.
(5) Product Parameters
Finally, the UAP user must provide values for product parameters (such as number of rings before voice mail picks up, guaranteed level of service, etc.). What parameters are required is an attribute of the offer's associated vendor product. These parameters are defined in the Administrator Console.
5.7.6. Automating Quote Item Configuration
In addition to manually configuring quote items, the UAP user can take advantage of two features of the UAP to streamline the quote configuration process, pre-population and propagation.
(1) Pre-Population of Parameters
Certain offered products can be set up to have values for their parameters pre-populated when they are purchased in a quote. By default, when an offer item moves from a cart item to a quote item, a plug-in can then give pre-populated values to certain product parameters. By default, the following parameters can be pre-populated: (a) attachment point; (b) service address (customers only); (c) service identifier; (d) start date; and (e) other product parameters.
The parameters to be pre-populated are determined by the PreConfigure*,java plug-ins. By default, the pre-populated values for product parameters are taken from the default values specified when the offer was configured in the Administrator Console.
Other parameters are populated as follows:
Once the UAP user accepts the pre-populated configuration information, the UAP user can at any time before ordering the quote go back and modify the configuration of individual quote items which were pre-configured, until the quote is submitted as an order.
(2) Propagation of Parameters
If there is more than one of the same quote items to be ordered, the UAP allows configuration parameters to propagate to subsequent items in the quote.
Once the UAP user has configured a quote item, the UAP user can check the box marked “Propagate to all items (same product)”. Then, when accepting the configuration for that item, the UAP user will see a confirmation page indicating which items in this quote (if any) have been selected by the plug-in to receive the propagated configuration information. The UAP user can then accept or cancel the propagation. If the UAP user accepts the propagation, the indicated quote items receive the configuration information from the “primary” quote item from which the UAP user elected to propagate.
Certain configuration parameters for a quote item can be propagated. By default, they are: (a) attachment point; (b) service address; (c) service identifier: (d) start date; and (e) other product parameters.
The determination of which quote items are to be configured by propagation is also determined by the plug-in. By default, the plug-in propagates configuration to the following class of quote items: (a) quote items that are of the same product type (determined by vendor product type) as the ‘root’ quote item; and (b) of those quote items, only quote items in state “pending configuration” are eligible for propagation.
Once the UAP user propagates configuration information, the UAP user can at any time go back and modify the configuration of individual quote items which were propagated.
5.7.7. Disclosures
Offer items in the quote can have disclosures associated with them which communicate legal or other information the customer must agree to before purchasing. All disclosures for each item in the quote which has them are displayed and the UAP user must accept them before the quote can proceed.
5.7.8. Negotiated Quote
Once all the configuration described has been completed for a quote, it reaches the “quoted” stage, and the display updates to reflect this by bringing the UAP user to the Negotiated Quote page. Once a user elects to order a negotiated quote, A quote items become order items.
(1) Price Overrides
UAP agents can issue price overrides to a quote item once the containing quote has reached the negotiated stage. Every item in a negotiated quote has a link labeled “Modify” which brings up the price override page.
The UAP user must specify a reason for the override, a description of the particular reason (i.e. reason is “promotion” and the description of the particular promotion is “Summer DSL Blowout”. )
The UAP user can then specify a percentage discount for each item in the One-time Charges, Monthly Rates or Usage Rates categories. The system calculates and displays the new final charge. The UAP user can either reset or click “APPLY” and commit the override. The total quote price is recalculated based on the overridden items, and the quote summary updates to reflect this new price.
(2) Prices of Held Quotes
Once a quote reaches the negotiated stage, the price for that quote is fixed. If the UAP user holds the quote, and prices for items in that quote and for that customer's price group should change, the quote will remain at the price at which it was held.
5.7.9. Shipping Address for Delivered Products
Offers which represent equipment (cell phones, pagers) which are physically delivered to a customer or partner are called delivered products in the UAP. When purchasing a quote containing one or more delivered products, the UAP user is required to give a single shipping address to which all delivered products in the quote will be shipped. If there are no offers corresponding to delivered products in the quote, then no shipping address is required.
5.8. Orders
Once products have been selected for ordering, configured in a quote and submitted by clicking the “ORDER NOW” link, an order is created.
5.8.1. Order History
The UAP user can search on service orders from the user home page, or orders can be tracked from the Order History off of the customer/partner navigation bar. The order history page displays: (a) Order number; (b) Date Created; (c) Partner-Customer ID; (e) Description; (f) Status; and (g) Last Modified By.
(1) Order Detail
By clicking on the order number, the user can then bring up a detail of the order. This page lists: (a) Order number; (b) Date Created; (c) Status; (d) Master PO number (if any); (e) Description; (f) Partner-Customer ID; and (g) each of the constituent order items
Each order item in the list displays:
The status that is visible from the order item line-item in the order detail page is obtained from an interaction model; it is a view into the external provisioning process. Clicking on this status will bring up the interaction history for that order item.
5.8.2. Canceling an Order
Canceling an order is not guaranteed to completely cancel all products ordered. Since the system relies on external systems to handle provisioning, it is possible that an ordered item can already be provisioned at the time the UAP user are requesting cancellation, but that the new state information has not been communicated to the system. Therefore, canceling an order from the order detail page simply requests a cancellation and sends the appropriate CMI to the external system. If the external system is successful, the order will be canceled and the state reflected in the order history.
5.8.3. Reordering
When the UAP user select “REORDER” from the order detail page, the UAP user are brought to the quote summary page for a new quote, populated with any items which were in the original order with an action of “Add”. This excludes from reordering any items which were in the original order as upgrades, or which were removed, changed suspended or resumed. The items in the re-ordered quote are in a configured state, but the UAP user can then change the configuration of the quote items. The UAP user then can re-submit them as a new order, leaving the original order unchanged.
5.8.4. Supplemental Orders
From the Order Detail page, the UAP user can elect to supplement the order. Supplemental orders are a way for UAP agents to add or change aspects of an order before it has been fully provisioned. What items in an order are eligible for supplement is controlled by a plug-in, but by default only products who have not reached state “complete” can be supplemented.
The supplemental quote contains those order items which the plug-in determined were eligible for supplement. All other items which were ineligible also appear in the supplemental order quote, but are un-modifiable and retain their state from the original order. The UAP user can make whatever supplemental changes are required, such as replace items in the quote for supplemental order, reconfigure them or cancel them outright. Once the UAP user make these supplemental changes, the UAP user submit the supplemental quote and creates a supplemental order.
(1) Charges for Supplemental Orders
A plug-in calculates charges for a supplemental order. By default, this charge is a flat-fee which is then assessed to the account and associated with the quote. This behavior can be customized. The supplemental charge is displayed on the Negotiated Quote page in the totals area.
The UAP user can also elect to waive this supplemental charge from the Negotiate Quote page by clicking the “Waive Charge” link next to the supplemental charge amount. The charge is then removed and no longer displays.
(2) Escalations
While submitting a supplemental order, the UAP user can flag individual items as “escalation” items, indicating that the item is in response to an issue raised by a customer.
5.9. Service Managment
5.9.1. Products in the UAP
Products such as access lines, voice mail, and call forwarding for which there is an ongoing subscriber relationship are referred to as assigned products in the system. Assigned products can be modified, suspended, resumed, or removed.
Delivered products represent actual end-user equipment such as a cell phone or other customer premise equipment. These delivered products maintain an association to an account within the system, but are not eligible for the same actions as provisioned products; they cannot be modified, upgraded, suspended or resumed, or removed.
5.9.2. Viewing Services
From the Customer Summary page, the UAP user can view products and services provisioned to particular account by clicking the “view services” link next to that account. The UAP user is then shown a hierarchical view of all products provisioned to that account. Arrows next to products indicate that the UAP user can click to expand or collapse that level of the product hierarchy. Clicking on the name of a product brings the UAP user to the detail page for that product. The UAP user can also bring up the products page by clicking the “products” link from the customer/ partner navigation bar.
(1) Product Detail Page
For assigned products, the detail page shows the name of the product, a brief description, the date the product was provisioned, and a summary of the configuration information. Any contacts assigned to this product are also visible, as is a link to add new contact information.
To manage the product hierarchy, the UAP user can modify, remove, suspend/resume, upgrade, report trouble, and contacts for the assigned products. For delivered products, the UAP user may only report trouble and add/remove contacts.
5.9.3. Modifying Products
The UAP user modifies an assigned product by clicking “Modify Product” from the assigned product detail page. Since an external provisioning system must be used to make the desired modifications to a provisioned product or service, the UAP implements product modification as an order. Modifying an assigned product takes the UAP user to the quote summary page for a new quote, consisting only of the product to be modified.
From this new quote detail, the UAP user can then configure the active parameters on the offer including a “start” date when the customer wishes the modification to take effect as well as any other product parameters, service address, service identifier, etc. The UAP user can then submit the quote.
5.9.4. Removing Products
The UAP user can request an assigned product to be discontinued by clicking “Remove Product” from the assigned product detail page. Removing a product brings the UAP user to the quote summary page of a new quote, consisting only of the product to be removed.
The only configuration possible for this removal quote is the termination date. Analogous to the service start date the UAP user selected when ordering the product, the UAP user can choose either the earliest possible date, or a specific date, as long as the date the UAP user choose is not earlier than the earliest possible date.
5.9.5. Suspend/Resume Product
From the product detail page, the UAP user can suspend products that are provisioned and active. When the UAP user selects a product to be suspended, the system will check to see if the product is an Offer Composite. If it is, the entire offer collection and any of its constituents' child products are suspended, even if they reside on other accounts associated with the active customer. Otherwise, the selected product and all of its children are suspended.
When the UAP user wish to resume a product, the UAP user first locate it in the product hierarchy and select “RESUME”. The system traverses that product's children and resumes them as well. Finally, if the UAP user is resuming a previously suspended composite offer, the entire collection and any of its constituents' children are resumed.
Since an external provisioning system must be used to make the desired suspensions/resumptions to a provisioned product or service, the UAP implements product suspend/resume as an order. Suspending or resuming an assigned product takes the UAP user to the quote summary page for a new quote, consisting only of the products to be suspended or resumed.
5.9.6. Upgrading Products
Product upgrades are initiated from the detail page for the provisioned product to be upgraded. Which product offers are on a given product's upgrade path is configurable through the Administrator Console. Once an upgrade product is chosen, that new product is quoted and ordered like a normal product offer. Once the upgrade order is complete, the new offer instance replaces the original.
5.9.7. Contacts
The UAP user may also view or remove existing contacts for this product, and add new contacts.
5.9.8. Reporting Trouble
The UAP user may also raise trouble tickets against specific products.
5.10. Support Personnel
Support Personnel are individuals within the UAP user's organization with assigned areas of responsibility and whom the UAP user can then associate with customers. By default, the UAP has three categories for support: (a) business; (b) primary; and (c) technical. These categories reside in a constant class and can be modified.
5.10.1. Assigning Support
The UAP user can assign support personnel to the active customer by clicking “support” on the customer navigation bar. The assign support page presents the UAP user with a list of all available support personnel. Clicking on “ASSIGN” associates the selected support person to the account, and adds them to the list of assigned supports displayed at the bottom of the page. The UAP user can also un-assign support personnel from this page.
Note that the UAP user can assign multiple support resources from a single category; there is no limit to the number of business, technical or primary supports for a customer.
5.10.2. Managing Support Personnel
Administrative users can create new support personnel and can modify or remove existing ones. If the UAP user is an administrative user, the “manage support” link appears on the user navigation bar and brings up the manage support page. Here, the UAP user is presented with a list of existing support personnel and can view or modify a support person by clicking the corresponding link.
Creating a new support person requires the UAP user to select a category of support from the drop-down menu (these categories can be customized via a constant class). Then, the UAP user must enter name and contact information for this support person, and can enter any comments.
From the manage support page, the UAP user can remove an existing support person outright by selecting them from the list and clicking “REMOVE”.
5.12. Contacts
Contacts are individuals in the customer's or partners organization who are assigned responsibility for various aspects of the relationship with the provider. The UAP user may assign contacts to (a) the customer/partner; (b) an account; and (c) a product instance. The UAP user also must provide at least one contact for the customer/partner during registration.
When adding a contact, the UAP user must provide a name, address and telephone number. Contacts are of a particular type such as “primary” or “technical”. The UAP user can assign as many contacts as needed. There can also be multiple contacts of a given type. What contact types are defined is determined by a constant class which may be changed.
5.11.1. Managing Contacts
Customer contacts are displayed on the customer/partner, account, and product detail pages. From there, the UAP user can add new contacts, modify an existing contact, or remove an existing contact.
5.12. Reporting Trouble
5.12.1. Issuing Trouble Tickets
By clicking the “Report Trouble” link on the detail pages, the UAP user can issue trouble tickets against customer, account, and provisioned product
The trouble ticket is date-stamped and marked with the ID of the UAP agent submitting it. The UAP user must supply contact information for the customer or partner claimant making the trouble report and specify a category or reason for the trouble report. The UAP user should also provide a detailed text description of the problem, and any recommended action. If the UAP user specifies an e-mail address and indicate that this is the preferred contact method, a notification is automatically sent to that e-mail address as the ticket changes state.
Once the UAP user has provided all the information required for the ticket and submitted it, a summary page is displayed.
5.12.2. Tracking Trouble Tickets
Past trouble tickets against a customer are viewed either by executing a search from the user home page or via the history list from the customer/partner navigation bar.
Clicking the trouble ticket number in the history list opens the detail page for that ticket showing a summary of the ticket. The status link brings the UAP user to the interaction status for the ticket, which displays the state of the ticket as reported from the external ticketing system through an end-user view of an interaction model.
As issues are worked, the UAP user can open trouble tickets and click the modify link to add updated information. The systems always records and displays the last-modified date and the user ID of the UAP agent who last modified the trouble ticket.
5.12.3. Resolving a Trouble Ticket
When an issue has been resolved, the UAP user can open the associated trouble ticket to modify it and mark it resolved. The UAP user must put in a description of how the issue was resolved when resolving a ticket. If an external system is in use for tracking trouble tickets, the system sends a CMI to notify the external system of the ticket's resolution.
5.13. Adjustments and Disputes
5.13.1. Adjustments
The UAP user can view the adjustment history for a customer by selecting the “adjustments” link from the customer navigation bar. A drop-down list with all accounts associated with that customer allows the agent to view adjustment histories for each account.
From the adjustment history, the UAP user can issue a new adjustment to the customer. The UAP user selects an account, an invoice against which to issue the adjustment (optional), whether the adjustment is a credit (reduces the amount a customer owes) or debit, (increases the amount the customer owes), an adjustment reason (allowable adjustment reasons are defined in a constant class and are configurable), and a detailed description of the problem or issue that led to the adjustment.
The UAP user may also issue an adjustment when resolving a dispute.
5.13.2. Disputes
When viewing the invoice summary page, or a detail page for a specific invoice, the UAP user can open a dispute on behalf of a customer or partner. The UAP user must specify the partner or customer ID, a name, contact information for the claimant, select a category for the dispute (these categories reside in a constant class and are configurable), and write a detailed text description of the problem. Once submitted, the UAP user can view the dispute, along with any other for that customer at any time by clicking the ‘disputes’ link in the customer navigation bar. The dispute history gives the dispute ID, the date created, a category and brief description, and the state of the dispute. The UAP user can only create disputes from an invoice summary page, not from the dispute history page.
If the UAP user needs to add or change information in a dispute record, the
UAP user can do so from the dispute history by opening that dispute and modifying the description. When the issue which occasioned the dispute has been resolved, the UAP user can open and modify the dispute record, add a resolution description, and then either save the record, or save and issue an adjustment to the account. If the UAP user chooses to save and issue adjustment the UAP user is then brought to the adjustment page and can issue the adjustment.
5.14. Notes
The UAP users can create notes to record activity taken on various entities in the system. Notes capture the date and time they were created, the UAP agent who created them, the customer with whom they are associated, and the entity the note is attached to. Notes can be attached to: (a) Customers or partners, from their respective detail pages; (b) Orders, from the Order Detail page; and (c) Quotes, from the Quote Detail page. Also, a note history can be viewed for each of these entities from their detail pages.
5.15. Reporting
The UAP user can view five different reports from the UAP. Two are visible from the user home page: (a) Financial Forecast; and (b) Financial Bookings. These two reports summarize revenue forecast or booked, respectively broken out by product line and charge type (recurring vs. non-recurring) for the current month.
Three reports are specific to partners and are visible from the partner home page for a particular partner in session. They are: (a) Financial Forecast; (b) Financial Bookings; and (c) Orders Past Due. The first two reports are analogous to the two reports on the user home page, except that they cover revenue for the active partner alone. The last, Orders Past Due summarizes any outstanding orders which are not complete and are past their requested due date.
The actual data in these reports comes from the database, but the reports themselves are provided by an external system; the portal merely supplies links to those reports.
5.16. Manual Approval
The Universal Agent Portal provides pages that allow the UAP user to manually set the status of order items, account requests, and customer requests. This is useful in testing or in deployments which do not use external systems for provisioning or trouble ticketing. By default, the UAP allows a licensee to set the “pending”, “rejected”, and “complete” states, plus the “canceled” state for an order item.
Click the “approval menu” link off of the user navigation bar to bring up the approval menu. The UAP user will then see the approval menu which contains: (a) Approve Customer Requests; (b) Approve Partner Requests; (c) Approve Account Requests; and (d) Approve Order Item Requests.
Each of these menus presents a list of items (appropriate to the menu chosen), their item number, the date the item was created, the current status, and radio buttons allowing the UAP user to alter the state of the item. Once the UAP user has made the desired modifications, clicking “UPDATE” will commit those changes and change the state of the items within system.
Section 6. The Channel Partner Portal
One embodiment of the invention is the Channel Partner Portal (CPP), which allows users at communications service provider sites to manage their accounts with a provider. CPP users can use the portal to shop for products and services (typically on behalf of their own end-customers), manage these services, view reports, and report and track trouble tickets.
6.1. CPP Logging In
The CPP user logs in using a user name and password set up for their organization by a communications service provider (CSP). The CSP can set up multiple users for a partner, with differing levels of security or access to data. By default, two security levels are supported: administrator and user.
The CSP creates the first user (typically an administrator) for a partner via the Universal Agent Portal. Once the CSP has created at least one administrator user for a partner, that user may then in turn create other users for the partner.
A CPP user's security level determines what transition policies they may execute and what JSP's they may view.
The two security levels, administrator and user have the following permissions and restrictions for navigating the CPP:
(1) CP_partner_user. User may not add, remove, or modify accounts; may not access bulk pre-qualification; may not add, remove or modify support resources; may not add, remove or modify CPP users; may not reorder products or existing orders.
(2) Partner_admin. Administrator may access the entire portal except the manual approval screens.
6.2. CPP Home
After a CPP user logs in to the portal, the partner home page comes to screen. This page contains the following areas:
(1) Navigation. The main navigation bar is visible throughout the CPP and allows the user to navigate to the following areas:
(2) Partner Name and Logo. The partner's name and logo are displayed at the top of the partner home page, as well as the name of the user currently logged in.
(3) News and information. This area displays any news (such as reports of outages, new service offerings, etc.) or other promotional messages targeted at the CPP user. The contents of this area are configurable via the Administrator Console.
(3) Search. The search area of the partner home page, as well as the “SEARCH” link on the navigation bar, brings the CPP user to the search page from where they can execute three different types of searches.
(4) Information Management. The information management area contains links to three types of partner-specific reports. It also provides a link where CPP users can create bulk pre -qualification requests. CPP users can also manage accounts and view their partner detail page.
(5) Activity History. The activity history area allows CPP users to view past activity in three areas: quotes, orders and trouble tickets.
(6) Administering Users. Functions in this area allow CPP users to change their password, and (if they have sufficient authority) to create other partner users.
6.3. Searching
From the search area on the partner home page, the user can execute searches for three types of objects: orders, trouble tickets, and products.
Clicking any one of these links brings the user to the search page for that type of object.
6.3.1. Search Types
On the search page, a drop-down menu controls which type of object the user is searching for. Changing the selection in this drop-down reloads the search page with input fields for search criteria appropriate to that object.
The user can execute searches for the following types of items:
In addition, the user can specify whether any sort should be ascending or descending.
6.3.2. Search Results
Once the user specifies values for the search criteria, executing the search returns a set of matching items (if any). By clicking on a column header, the user can cause the result set to be sorted on that columns parameter. Clicking again toggles the sort from ascending to descending.
Clicking on an item in a result set brings the user to the appropriate detail page for that item (product detail page for a provisioned product, trouble ticket detail for a trouble ticket, etc.)
6.4. Shopping
A partner can use the CPP to shop, select, configure and order products. Ordering products in the CPP consists of the stages of: (a) shopping; (b) creating and configuring items in a quote; and (c) Ordering the items in a quote.
6.4.1. Menus
Menus are navigable lists of products offered for ordering. In the CPP, the user shops product menus, and selects offered products for purchasing. Menus typically break product offerings down into categories such as “Business Services” and “Residential Services”.
(1) Default Menu and Price Groups
When the user is browsing the product menu they will see a set of product offerings determined by their assigned price group. The price group determines the root menu and prices for each offer.
(2) Alphabetical Product Index
In addition to the hierarchical menus, the user can also locate products by name. Selecting a letter from the alphabetical index will bring the user to a menu of products beginning with that letter.
(3) Breadcrumbs
While browsing the hierarchical menus (but not while viewing an alphabetical list), the CPP shows a “breadcrumb” displaying the path thus far taken through the menu hierarchy. The user can click back at any link in the chain to return to the menu at that level.
6.4.2. Offers
The offers in menus are listed with a brief description, the total price for recurring charges and for non-recurring charges, a field displaying both the current quantity in the quote and a field for entering a different quantity.
(1) Offer Detail
When the user shops and finds an offer they wish to purchase, they can choose to drill in to the offer detail page. The detail page displays the name of the offer, itemized prices for recurring, non-recurring and usage charges, and any upsell or related offers. The user can then specify a quantity of the product to be ordered, just as in the order's line-item in the menu page.
Whenever the user changes the quantity of an item to be purchased, either from the menu page or the offer detail page, they must click “UPDATE” to save the new quantity before moving to a new page. This commits the items the user has selected to their shopping cart, which can be viewed at any time by selecting “Quote Preview”. The user can then continue shopping, perhaps in a different category of product offerings.
(2) Related Offers and Upsell Offers
When viewing an individual offer via the detail page, the user is shown related offers or upsell offers, if any exist. Related offers are offers which have some connection or marketing synergy with the offer being viewed.
Both related and upsell offers are displayed on the detail page in a one-line format similar to the offers on a menu page. These related offers can themselves be drilled into from the first offer's detail page.
For example, when the user clicks on the Business Access Line product offer, they are taken to the offer detail page for Business Access Line. There, in addition to the Business Access Line product, the user sees: Business Voice
Mail w/Pager Notification, Essential Bundle, and Business Messaging Bundle.
The user can enter a quantity for purchase for any of these upsell offers and click “UPDATE” to add those offers to their cart.
Which offers are related to one another and which are on an upsell path is configurable through the Administrator Console.
(3) Offer Collections
Since simple, one-product offers may not be sufficient to meet a providers' product offering requirements, the system allows for individual offers to be bundled together into offer collections. Offer collections (and also simple offers) are configured in the Administrator Console.
Instead of selecting a quantity to purchase, as with simple offers, to select an offer collection for purchase the user must click the “add Bundle” link for that offer and then select which options for that collection they wish to purchase. If the offer collection is fixed, then the user will automatically receive all of the offers in the collection; no choices can be made. If the collection is dynamic, the user is guided through the collection's determinants where the user selects the individual offers that will make up the collection. At any point in this process, the user can go back to a previous determinant to select a different offer. The navigation path through the collection, as well as the determinants used, and the offers included are all configured through the Administrator Console.
6.4.4. Quote Preview
At any point in the shopping process, the user can view a quote preview by selecting that link from the top of any menu page. This is a view of all products that have been selected for ordering, their total recurring and total non-recurring charges, the quantity currently selected for quote and a text field to input an updated quantity. The user may also remove items from a quote. The quote preview is the CPP implementation of the shopping cart. As the user selects offers for purchase, they are placed in the quote preview.
6.5. Quotes
6.5.1. Creating Quote
When the user has shopped and selected all the products desired, clicking “CHECKOUT” creates a quote. All of the items that were in their quote preview when they selected checkout now appear as quote items.
6.5.2. Quote Summary
The quote summary page shows all the items in the user's current quote. The top of the summary page shows the quote number, creation date, status, the name of the user who created the quote, and the last-modified user. The user can also enter a master purchase order number, a brief description, select an existing partner-customer ID (or enter a new one), and enter an e-mail address. Partner-Customer ID is a convenience field where the user can store an internal ID for their end-customers. Items in a quote display the item number (ordinal number of item in quote) product offer name, the action for this item (i.e., add, remove, change, etc.), the purchase order number (if one was provided), the status (configured, pending configuration, etc.), the price for recurring and non-recurring charges, and a checkbox with which the user can remove items from the quote. If the user removes any items from a quote, they must click “UPDATE” to commit those changes. If there are more items than will fit on one page, a pair of previous/next links allows users to navigate between pages.
(1) Working With a Quote
The user can hold or cancel the quote, add notes, shop more, or continue. Holding a quote allows a quote to be held in its current state and then re-opened at a later time. Held quotes are displayed in the current quote history, available from the activity history area on the partner home page. Canceling a quote causes the quote to become inactive, but it will continue to be available as a “Canceled quote” in the quote history.
If the user chooses to “shop more” from the quote summary, they are returned to the product catalog. Any products they purchase now are added to the current quote.
Adding a note to a quote allows the user to attach an annotation to the quote that will then be visible to anyone else working with that quote in the CPP. Any notes created in the CPP can only be viewed in the CPP. Users of other e-Business portals cannot view or modify them.
6.5.3. Holding a Quote
Holding a non-negotiated quote causes the quote to persist for a period of time. The user can re-open a non-expired held quote at any time and continue working on it by shopping more, configuring items, ordering it or canceling it.
6.5.4. Canceling a Quote
Canceling a quote stops the ordering process and moves the current quote to state “Canceled”. Canceled quotes can always be viewed from the quote history available from the main navigation bar.
6.5.5. Configuring Quote Items
Before quote items can be purchased and moved to order items, they must be configured. Configuration is reached by selecting the “Configure” link which is next to every quote item requiring configuration. If the user attempts to click “CONTINUE” without configuring all quote items, the CPP will prompt for configuration information for each item in the quote.
The following attributes are configured in a quote:
(1) Service Start Date. Users can choose to accept the earliest possible start date for a quote item, or select another date (as long as the date they select is not earlier than the earliest possible date. The earliest possible start date is an attribute of the offers associated vendor product configured via the Administrator Console when product offerings are created. A constraint on service start dates arises when a quote item is attached to an existing quote item. Users cannot select a start date for a dependent product that is earlier than the start date selected for its parent product.
(2) Service Address. Users must input information for the service address. This associates the product to a physical location, typically a customer address.
(3) Selecting Service Identifier. Users must select a service identifier (a telephone number for access line, for example). The system uses a plug-in to interface with an external system to retrieve a set of service identifiers from which to choose.
(4) Product Association. The user must also attach each quote item either to a place in the partner's hierarchy or to another item in the quote. The determination of which hierarchy objects or quote items are valid attachment points is handled by the business rules manager.
(5) Product Parameters. Finally, the user must provide values for product parameters (such as number of rings before voice mail picks up, guaranteed level of service, etc.). What parameters are required is an attribute of the offer's associated vendor product. These parameters are defined in the Administrator Console.
6.5.6. Automating Quote Item Configuration
In addition to manually configuring quote items, users can take advantage of two features of the CPP to streamline the quote configuration process, pre-population and propagation.
(1) Pre-Population of Parameters
Certain offered products can be set up to have values for their parameters pre-populated when they are added to a quote. By default, when an offer item moves from a cart item to a quote item, a plug-in can then give pre-populated values to certain product parameters. By default, the following parameters can be pre-populated: (a) attachment point; (b) service identifier; (c) start date; and (d) Other product parameters.
The parameters to be pre-populated are determined by the PreConfigure*.Java plug-ins. By default, the pre-populated values for product parameters are taken from the default values specified when the offer was configured in the Administrator Console.
Other parameters are populated as follows:
Once the user accepts the pre-populated configuration information, they can at any time before ordering the quote go back and modify the configuration of individual quote items which were pre-configured.
(2) Propagation of Parameters
If there is more than one of the same quote item to be ordered, the CPP allows configuration parameters to propagate to subsequent items in the quote.
Once the user has configured a quote item, they can check the box marked “Propagate to all items (same product)”. Then, when accepting the configuration for that item, they will see a confirmation page indicating which items in this quote (if any) have been selected by the plug-in to receive the propagated configuration information. They can then accept or cancel the propagation. If they accept, the indicated quote items receive the configuration information from the “primary” quote item from which they elected to propagate.
Certain configuration parameters for a quote item can be propagated. By default, they are: (a) attachment point; (b) service address; (c) service identifier; (d) start date; and (e) other product parameters.
The determination of which quote items are to be configured by propagation is also determined by the plug-in. By default, the plug-in propagates configuration to the following class of quote items: (a) quote items that are of the same product type (determined by vendor product type) as the ‘root’ quote item; and (b) of those quote items, only quote items in state “pending configuration” are eligible for propagation
Once the user propagates configuration information, they can at any time before purchasing the quote go back and modify the configuration of individual quote items which were propagated, until the quote is submitted as an order.
After configuration is complete, the user is returned to the quote detail page.
Clicking “Continue” from here, after having configured the quote, will bring up the disclosures page.
6.5.7. Disclosures
Offer items in the quote can have disclosures associated with them which communicate legal or other information the customer must agree to before purchasing. All disclosures for each item in the quote which has them are displayed and the user must accept them before the quote can proceed.
6.5.8. Negotiated Quote
Once all the configuration described has been completed for a quote, and disclosures have been accepted, it reaches the “quoted” stage, and the display updates to reflect this by bringing the user to the Negotiated Quote page. Once a user elects to order a negotiated quote, all quote items become order items.
(1) Prices of Held Quotes
Once a quote reaches the negotiated stage, the price for that quote is fixed. If the user holds the quote, and prices for items in that quote and for that customer's price group should change, the quote will remain at the price at which it was held. A held negotiated quote will expire after a predetermined period of time has elapsed, measured from when the quote was first created. This time limit is specified in the properties file by the parameter quote.defaultquote-validtimeduration. This parameter has a value of 30 days, by default. After a quote expires, it is no longer available for ordering, but will still appear in and be viewable via the quote history as an “expired quote”.
(2) Modifying a Quote
Selecting “Modify Quote” brings the user back to the quote summary page. All of the user's previous configuration information is presented, and they can make changes. The new quote will be repriced. They can proceed with ordering the modified quote.
6.5.9. Shipping Address for Delivered Products
Offers which represent equipment (cell phones, pagers) which are physically delivered to a partner are called delivered products in the CPP. When purchasing a quote containing one or more delivered products, users are required to give a single shipping address to which all delivered products in the quote will be shipped. If there are no offers corresponding to delivered products in the quote, then no shipping address is required.
6.6. Managing Support
Support Personnel are individuals within the CSP's organization who are assigned areas of responsibility and whom the CSP can then associate with partners via the Universal Agent Portal. CPP users can then view support information to determine the correct contact for a given situation.
Users of the CPP can view the support resources assigned to them via the “SUPPORT” link on the main navigation bar. This displays the support list, from which users can select a support resource and view their detailed information. By default, the CPP has three categories for support: (a) business; (b) primary; (c) technical.
6.7. Viewing Activity History
Users can view history information from the links in the activity history section of the partner home page. The user can choose from orders, quotes or trouble tickets. Choosing one of these categories brings up the history page for that item. Depending on the type of item whose history the user is viewing, they may take different actions.
6.7.1. Order History
CPP users can search on service orders from the home page. The following information is returned for each item on the order history page: (a) Order number; (b) Date Created; (c) Partner-Customer ID; (d) Description; (e) Status; and (e) Last Modified By.
(1) Order Detail
By clicking on the order number, the user can then bring up a detail of the order. This page lists: (a) Order number; (b) Date Created; (c) Status; (d) Master PO number (if any); (e) Description; (f) Partner-Customer ID; and (g) each of the constituent order items.
Each order item in the list displays:
No actions, apart from returning to the order detail page, are available from the order item detail page.
(2) Canceling an Order
Canceling an order is not guaranteed to completely cancel all products ordered. Since the system relies on external systems to handle provisioning, it is possible that an ordered item can already be provisioned at the time the user is requesting cancellation, but that the new state information has not been communicated to the system. Therefore, canceling an order from the order detail page simply requests a cancellation and sends the appropriate CMI to the external system. If the external system is successful, the order will be canceled and the state reflected in the order history.
(3) Reordering
When the user selects “REORDER” from the order detail page, they are brought to the quote summary page for a new quote, populated with any items which were in the original order with an action of “Add”. This excludes from reordering any items which were in the original order as upgrades, or which were removed, changed suspended or resumed. The items in the re-ordered quote are in a pre-configured state, but the user can then change the configuration of the quote items. They then can resubmit them as a new order, leaving the original order unchanged.
(4) Notes
Users may attach notes to an order.
6.7.2. Quote History
Users can view quotes from the quote history available from the partner home page in the activity history. The quote history page displays the following information for each current quote: (a) Quote number; (b) Date Created; (c) Partner-Customer ID; (d) Description; (e) Status; and (f) Last Modified By.
A user can also view ordered, expired and canceled quotes. The user can switch between these three categories via links on the main quote history page.
(1) Quote Detail
The user can view a detail page for a quote by clicking the quote in the history list. The detail page summarizes the data displayed in the history entry, and also shows a list of every item in that quote. For each item, the quote detail displays: (a) Item number; (b) Product Name (Clicking this link shows associated charges for the product); (e) The action (add, remove, etc.) for that item which caused it to appear in the quote; (f) The PO number (if any); (g) Item Status; (h) One Time Charge; and (i) Recurring Charge.
(2) Quote Item Detail
Each quote item also has a detail link which shows the user a detail page for that quote item, including the configuration parameters which were chosen when the quote item was purchased.
6.7.3. Trouble Ticket History
Past trouble tickets are viewed either by executing a search, or by viewing the trouble ticket history, both from the partner home page.
The following information is returned for each item on the trouble ticket history page: (a) Ticket number (Clicking the trouble ticket number in the history list or search result set opens the detail page for that ticket showing a summary of the ticket); (b) Date Created; (c) Category; (d) Name of trouble ticket (a headline); and (e) Ticket Status.
The user can view a detail for a trouble ticket by clicking on it from the history list. The ticket detail page lists: (a) Trouble Ticket Name; (b) Trouble Ticket Number; (c) Partner-Customer ID; (d) Status (The ticket status displayed is obtained from an interaction model; it is a view into the external provisioning process. Clicking on this status will bring up the interaction history for that trouble ticket); (e) Created By; (f) Created Date; (g) Last Modified By; (h) Last Modified Date; (i) Contact to Notify; (j) Phone Number; (k) Email Address; (l) The entity (partner, account, product) for which the ticket was raised; (m) The category; (n) The ticket description text; and (o) The resolution text (if any).
6.8. Information Managment
6.8.1. Reports
The CPP allows users to view three different reports from the partner home page. The default reports are: (a) Financial Forecast; (b) Financial Bookings; and (c) Orders Past Due.
The first two reports summarize revenue forecast or revenue booked, respectively broken out by product line, charge type (recurring vs. non-recurring), and by month. The last report is a summary of all open orders which are past their current due date.
The actual data in these reports comes from the database, but the reports themselves are provided by an external system; the portal merely supplies links to those reports.
6.8.2. Bulk Pre-Qualification
Some services may require pre-qualification before they can be provisioned.
The CPP allows partners to create and submit requests for bulk pre-qualification of a group of customers to an external system. From the partner home page, CPP users can select “bulk pre-qualification”. The bulk pre-qualification screen allows users to browse for and select a file containing information on customers to be qualified. They must give a name to the request, and an email address that will be notified when the request has been processed. They then submit the request. The file is then sent to a system which can handle the request.
6.8.3. Account Management
Accounts allow the CSP's partners to segment their business into logical units such as geographic location or department. The partner accounts page provides the CPP user with a list of all of their accounts. The list gives the name of the account, its status, and a link to view products for that account. Clicking on the account name brings the user to the account detail page, where they can view all information pertaining to the selected account such as billing address, credit information, and the names of any contact personnel assigned to the account.
A drop-down menu at the top allows the user quickly to switch to other accounts, which will then display their information. From the account detail page, the user can view the account's history, modify any of the account's information, and report trouble for this account, which will raise a trouble ticket, as, well as add, modify or remove contacts.
Users of the CPP can create accounts from the partner accounts page by clicking the “Add Account” link. The user must provide an account name, billing address and credit information for every account they create. Once created, the account will be displayed in the list of accounts on the partner accounts page.
6.8.4. Managing Products
From the account management page the user can view products and services provisioned to a particular account by clicking the “view the products” link next to that account. They are then shown a hierarchical view of all products provisioned to that account. Arrows next to products allow the user to click to expand or collapse that level of the product hierarchy. Clicking on the name of a product brings the user to the detail page for that product.
(1) Product Detail Page
For assigned products, the detail page shows the name of the product, a brief description, the date the product was provisioned, and a summary of the configuration information. Any contacts assigned to this product are also visible, as is a link to add new contact information.
To manage the product hierarchy, the user can modify, upgrade, remove, report trouble, and reorder the assigned products. For delivered products, users may only report trouble and add/remove contacts.
(2) Modifying Products
The user modifies an assigned product by clicking “Modify Product” from the assigned product detail page. Modifying an assigned product takes the user to the quote summary page for a new quote, consisting only of the product to be modified. From this new quote detail, users can then configure any parameters which were available when the product was first ordered, including a “start” date when the modification will take effect as well as any other product parameters, service address, service identifier, etc. The user can then submit the quote.
(3) Removing Products
The user can request an assigned product to be removed from the hierarchy by clicking “Remove Product” from the assigned product detail page. Removing a product brings up the quote summary page of a new quote, consisting only of the product to be removed. The only configuration possible for this removal quote is the termination date. Analogous to the service start date selected when ordering the product, the user can choose either the earliest possible date, or a specific date, as long as the date chosen is not earlier than the earliest possible date.
(4) Upgrading Products
Product upgrades are initiated from the detail page for the provisioned product to be upgraded. Which product offers are on a given product's upgrade path is configurable through the Administrator Console. Once an upgrade product is chosen, that new product is quoted and ordered like a normal product offer.
(4) Reporting Trouble
The user can raise a trouble ticket on a product.
(5) Reordering
When the user selects “REORDER” from the product detail page, they are brought to the quote summary page for a new quote, populated with a quote item corresponding to the order items in the order which had an action of ‘Add’. The item in the re-ordered quote is in a configured state, but the user can then change the configuration of the quote items. They then can re-submit them as a new order.
6.8.5. Partner Detail
The partner detail page presents the CPP user with a summary of their partner information. The page displays partner information, resale authority, address, and contacts. The user can also view their partner history, modify their address information, raise a trouble ticket, and add, modify, or remove contacts. Partner history consists of any changes made to partner information such as mailing address.
(1) Modifying Partner Information
The CPP user can click the “Modify Partner Address” link on the partner detail page to provide new or updated address information. Once they click modify, the new information is displayed on the partner detail page.
(2) Reporting Trouble
The user can raise a trouble ticket on an account.
(3) Adding, Modifying and Removing Contacts
The process for adding contacts to a partner is identical to the process for adding contacts to an account.
6.9. User Administration
6.9.1. Changing Passwords
CPP users may change their passwords from the user administration area of the partner home page. They must provide their current password, type their new password twice, and give a password hint which can be shown to a user if they forget their password.
6.9.2. Managing Users
(1) Adding New Users. CPP users with sufficient authority can create other users for their partner account from the manage users area of the partner home page. The user must provide a user name, password, and password hint. They must also select the authority level. The two authority levels and their default permissions are: (a) User: read-only user who may not create orders of perform maintenance activities; and (b) Administrator: user who has full access to all of the features.
(2) Removing Existing Users. From the Manage Users page, a CPP user of sufficient authority can remove existing users by selecting them from the drop-down menu and clicking “update”. The selected user is then made inactive and will be unable to log in to the CPP.
6.10. Issuing Trouble Tickets
Users of the CPP can issue trouble tickets against the following items by clicking the “Report Trouble” link on the following detail pages: (a) partner; (b) account; (c) provisioned product; (d) composite product; and (e) delivered product
The trouble ticket is date-stamped and marked with the ID of the CPP user submitting it. The user must supply contact information for the partner making the trouble report and specify a category or reason for the report. The user must also include a detailed text description of the problem, and any recommended action. If the user specifies an e-mail address and indicates that this is the preferred contact method a notification is automatically sent to that e-mail address as the ticket changes state.
Once the user has provided all the information required for the ticket and submitted it, summary page is displayed.
6.11. Contacts
Contacts are individuals in the partners organization who are assigned responsibility for various aspects of the partner's relationship with the provider. Users of the CPP may assign contacts to the following entities: (a) the partner; (b) an account; and (c) a product instance.
When adding a contact, the user must provide a name, address and telephone number. Contacts are of a particular type such as “primary” or “technical”. Users of the CPP can assign as many contacts as they desire. There can also be multiple contacts of a given type. What contact types are defined is determined by a constant class which may be changed.
Customer contacts are displayed on the customer, account, and product detail pages, where the user can add new contacts, modify an existing contact, or remove an existing contact.
6.12. Notes
CPP users can create notes to record activity taken on various entities in the system. Notes capture the date and time they were created, the CPP agent who created them, the customer with whom they are associated, and the entity the note is attached to.
Notes can be attached to: (a) Customers or partners, from their respective detail pages; (b) Orders, from the order detail page; and (c) Quotes, from the quote detail page
Also, a note history can be viewed for each of these entities from their detail pages.
6.13. Manual Approval
The CPP allows administrators to manually set the status of order items, account requests, and customer requests. This is useful in testing or in deployments which do not use external systems for provisioning or trouble ticketing. By default, the CPP allows a licensee to set the “pending”, “rejected” and “complete” states, plus the “canceled” state for an order item.
Upon navigating to the Manual Approval page, the CPP user will then see the following options: (a) Approve Customer Requests; (b) Approve Partner Requests; (c) Approve Account Requests; and (d) Approve Order Item Requests.
Each of these menus presents a list of items (appropriate to the menu chosen), their item number, the date the item was created, the current status, and radio buttons allowing the CSP to alter the state of the interim. Once the CSP have made the desired modifications, clicking “UPDATE” will commit those changes and change the state of the items within system.
Section 7. EAI Adapter
The EAI adapter runs within the eBusiness support system's process space specifically as part of the Interconnect Service. It uses source and target strategies that run within an external system's process space to transmit data between the Smart Component Server (SCS) and the external system. Once integrated with the external system, the eBusiness support system can publish events into the external system, and objects within the eBusiness support system can be updated based on events within the external system.
7.1. Creating Events
The eBusiness support system employs communications messaging interfaces (CMIs), objects within the system that contain references to data needed to be sent as events into an external system such as BusinessWare. Each CMI is associated with a routing policy that dispatches it to the correct adapter. When a routing policy dispatches the CMI to the BusinessWare adapter, the appropriate handler for that CMI creates an event. This event retains an association to the data referenced by the CMI.
There are six generic handlers for the Vitria's BusinessWare adapter, which correspond to six generic events that the system publishes:
To use the BusinessWare adapter to publish events to an automator model in BusinessWare, the CSP must complete the following steps for each CMI that will use the adapter:
(1) Create a BusinessWare automator model to handle the event associated with the CMI.
(2) Populate the CMI_CMI_POLICY table so that the CMI uses the generic routing policy.
(3) If the CMI data is for an object other than a vendor product, populate the GENERIC_CMI_POLICY table so that the ADAPTER_HOME attribute is the Java Naming Directory (JNDI) deployed name of the BusinessWare adapter EJB and the CNTXT attribute is the fully qualified class name for the appropriate handler.
The system provides a source connection template that the BusinessWare console uses to create a new connection model. The process for creating a source connection model using the console includes the steps of:
(5) Configure the publisher channel. This is the channel that publishes the event to the automater model.
The system provides a target connection template that the BusinessWare console uses to create a new connection model. The process for creating a target connection model using the console includes the steps of:
One embodiment of the invention is the application of the Smart Component Server (SCS) in DSL commerce. The application is based on the integration of the DSLAdvantage, SCS, and the adapters for Vitria BusinessWare via an HTTP connection to provide flow-through provisioning for DSL products.
8.1. Connection Model
Communication Message Interfaces (CMIs) transport references to data collected in the portal to the BusinessWare adapter. A DSLAdvantage source connection model translates the CMI into specific event data based on the request, then sends it to the appropriate automator model. This model translates the message to XML and sends the message via an HTTP connection directly to the DSL provider. When the BusinessWare adapter receives a return XML message, it uses the same automator model to translate the message before sending it to the DSLAdvantage target connection model, which updates the appropriate objects. DSLAdvantage uses the BusinessWare adapter to interact with a DSL service provider at three key points: (a) Service availability; (b) Order entry; and (c) Order status
8.2. Service Availability
The service availability function enables the eBusiness support system to present available services to an end user by sending pre-qualification information to the DSL service provider via a synchronous request, so that the provider immediately returns a list of services the customer qualifies for. Then a determinant allows a user to select from a list of offers to create a dynamic bundle. Offer collections for DSL services use two determinants to capture and send pre-qualification information to the DSL provider: the SERVICE_ADDRESS_REQUEST determinant, which collects address and site information, and the SERVICE_AVAILABILITY_CHOOSE_ONE determinant, which sends that site information to the DSL provider and then displays the returned products. The following steps illustrate how these determinants work in a DSL offer collection:
An offer collection is set up so that once a user selects a DSL product, the following determinant displays the corresponding customer premises equipment (CPE) needed to complete the DSL offer collection.
8.3. Order Entry
Once the end user completes the parameter configuration of all items in a quote and accepts the associated disclosures, an order is created. At this point, all order items associated with DSL services, along with the end user pre-qualification information, are sent to the provider via the BusinessWare adapter. This event is asynchronous-the adapter does not wait for a response from the provider. Once the provider accepts the order, it assigns an order ID to each item and sends that information back to the system via the BusinessWare adapter. The order entry target connection model translates the information and populates the PRVDR_ORDR_ID attribute for each order item.
8.4. Order Status
Once the DSL service provider has returned the order ID, the provisioning status of a DSL item can be requested. When an end user checks the status of a DSL item, the BusinessWare adapter uses the provider order ID saved to the corresponding order item to send a status request to the provider via the BusinessWare adapter. This event is synchronous—the adapter waits for a response from the provider. Once the provider sends status information back, the system posts this information to the DSL service provider status page. The system neither translates nor saves the status information—it is posted to this page exactly as it is sent by the DSL service provider. If the provider does not yet have status on the order, the system displays a message stating that provisioning status is not yet available.
If the providers site is not active when the order is submitted, the provider might not receive the order. For this reason, it is recommended that the user check the status of new orders daily to ensure the provider receive all orders sent.
8.5. Creating DSL Vendor Products and Offers
Vendor products and offers for DSL services and CPF are created in the same way as any other products and offers in the Cygent system. The user must associate a vendor with a vendor product, associate any disclosures, service level agreements, and parameter groups, and then create corresponding offers and prices. The user can also create new business rules specific to the relationship between the DSL services and CPE.
The user may also want to create a placeholder CPE vendor product and offer with a price of $0, for use when a customer already owns the specified CPE. This allows a customer to select this placeholder product when they don't need to order a CPE, thereby not breaking any business rules. Additionally, a representation in their account services for the CPE shows the delivered product was not provisioned by the DSL service provider.
BusinessWare is configured to send specific provisioning information to the DSL service provider when the order is submitted. To get this information to BusinessWare, the use needs to create vendor product parameters to associate with the DSL service vendor products.
8.6. Creating a DSL Offer Collection
To create offer collections for DSL services, the user must first design the flow of the collection, create the determinants, create corresponding determinant items for the DSL offers, then populate the determinant sequence table.
When creating a DSL offer collection, adhere to the following:
This application is a continuation of U.S. patent application Ser. No. 10/240,614, filed Jan. 19, 2010, now U.S. Pat. No. 7,657,436, which is the National Phase of International Patent Application No. PCT/US2001/10473, filed Mar. 30, 2001, which claims the benefit of U.S. Provisional Patent Application No. 60/193,315, filed Mar. 30, 2000. The contents of these applications are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2107450 | Miller | Feb 1938 | A |
| 2689082 | Kolisch | Sep 1954 | A |
| 4499545 | Daniels et al. | Feb 1985 | A |
| 5165726 | Talbott | Nov 1992 | A |
| 5243643 | Sattar et al. | Sep 1993 | A |
| 5408416 | Gilham | Apr 1995 | A |
| 5415341 | Diamond | May 1995 | A |
| 5612889 | Pintsov et al. | Mar 1997 | A |
| 5713511 | Diamond | Feb 1998 | A |
| 5761499 | Sonderegger | Jun 1998 | A |
| 5826085 | Berkery et al. | Oct 1998 | A |
| 6075843 | Cave | Jun 2000 | A |
| 6226626 | Thiel | May 2001 | B1 |
| 6459953 | Connelly et al. | Oct 2002 | B1 |
| 6763336 | Kolls | Jul 2004 | B1 |
| 7225170 | Ryan, Jr. | May 2007 | B1 |
| 7254641 | Broughton et al. | Aug 2007 | B2 |
| 7382773 | Schoeneberger et al. | Jun 2008 | B2 |
| 7568001 | McPartlan et al. | Jul 2009 | B2 |
| 20020046196 | Ogg | Apr 2002 | A1 |
| 20020143430 | Sansone et al. | Oct 2002 | A1 |
| 20030135627 | Hussain | Jul 2003 | A1 |
| 20070043569 | Potter et al. | Feb 2007 | A1 |
| 20070044023 | Carter et al. | Feb 2007 | A1 |
| 20070044026 | Potter et al. | Feb 2007 | A1 |
| 20070053513 | Hoffberg | Mar 2007 | A1 |
| 20080034354 | Brughton et al. | Feb 2008 | A1 |
| 20080086564 | Putman et al. | Apr 2008 | A1 |
| 20090164595 | Shiigi | Jun 2009 | A1 |
| 20090259753 | Hinton et al. | Oct 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 404 014 | Mar 2001 | CA |
| 0 889 421 | Jan 1999 | EP |
| 1 063 602 | Dec 2000 | EP |
| Entry |
|---|
| Office Action issued against U.S. Appl. No. 11/208,028 dated Jan. 30, 2009. |
| Final Office Action issued against U.S. Appl. No. 11/208,028 dated Jun. 23, 2009. |
| Office Action issued against U.S. Appl. No. 11/208,028 dated Oct. 26, 2009. |
| Final Office Action issued against U.S. Appl. No. 11/208,028 dated Mar. 15, 2010. |
| Office Action issued against U.S. Appl. No. 11/207,609 dated May 22, 2007. |
| Final Office Action issued against U.S. Appl. No. 11/207,609 dated Oct. 17, 2007. |
| Office Action issued against U.S. Appl. No. 11/207,609 dated Feb. 19, 2009. |
| Office Action issued against U.S. Appl. No. 11/207,609 dated Jul. 21, 2009. |
| Office Action issued against U.S. Appl. No. 11/207,609 dated Mar. 2, 2010. |
| Office Action issued against U.S. Appl. No. 11/208,041 dated May 2, 2007. |
| Final Office Action issued against U.S. Appl. No. 11/208,041 dated Oct. 17, 2007. |
| Office Action issued against U.S. Appl. No. 11/208,041 dated Jun. 2, 2008. |
| Final Office Action issued against U.S. Appl. No. 11/208,041 dated Nov. 13, 2008. |
| 1 Office Action dated Nov. 29, 2010 for U.S. Appl. No. 11/208,028. |
| Heineman, G.T., “A Model for Designing Adaptable Software Components,” Proceedings of the 22nd Annual International Computer Software and Applications Conf. (1998) pp. 121-127. |
| Hill, J. et al., “Persistence in Enterprise JavaBeans Applications,” JOOP (Jul. 1999). |
| Huber, F. et al, “Modeling dynamic component interfaces,” Proceedings. Technology of Object-Oriented Languages. Tools, Proceedings of International Conference on Tools, USA (Aug. 3, 1998) pp. 58-70. |
| International Search Report dated May 15, 2002 for Application No. PCT/US01/10473. |
| Office Action dated Mar. 26, 2004 for U.S. Appl. No. 09/796,058. |
| Office Action dated Sep. 13, 2004 for U.S. Appl. No. 09/796,058. |
| Office Action dated Apr. 21, 2005 for U.S. Appl. No. 09/796,058. |
| Office Action dated Jun. 6, 2005 for U.S. Appl. No. 09/796,058. |
| Office Action dated Dec. 22, 2005 for U.S. Appl. No. 09/796,058. |
| Office Action dated May 13, 2009 for U.S. Appl. No. 11/552,117. |
| Shimura, T. et al., “Storage and Retrieval of XML Documents using Object-Relational Database,” Database & Expert Systems Applications, DEXA, Wien, At, vol. 1677 (1999) pp. 206-217. |
| The Object People: “A White Paper: TopLink for Java,” The Object People (1997). |
| Number | Date | Country | |
|---|---|---|---|
| 20100145718 A1 | Jun 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10240614 | Feb 2005 | US |
| Child | 12689782 | US |
