DASHBOARD INTERFACE, PLATFORM, AND ENVIRONMENT

Cross-Reference to Related Applications

[0001] The present application is a continuation-in-part of and claims priority to U.S. Patent Application No. 14/294,046 filed June 2, 2014, which claims the benefit of U.S. Patent Application No. 13/469,331 filed May 11, 2012, which claims the benefit of U.S. Provisional Patent Application No. 61/488, 131 filed May 19, 2011. The present application is also a continuation-in-part of and claims priority to U.S. Patent Application No. 13/469,355 filed May 11, 2012, which claims the benefit of U.S. Provisional Patent Application No.

61/488,126 filed May 19, 2011. The present application is also a continuation-in-part of and claims priority to U.S. Patent Application No. 13/284,566 filed October 28, 2011, which claims the benefit of both U.S. Provisional Patent Application No. 61/488, 131 and U.S.

Provisional Patent Application No. 61/488, 126; U.S. Patent Application No. 13/284,628 filed October 28, 2011, which claims the benefit of both U.S. Provisional Patent Application No. 61/488,131 and U.S. Provisional Patent Application No. 61/488,126; and U.S. Patent Application No. 13/284,518 filed October 28, 2011, which claims the benefit of both U.S. Provisional Patent Application No. 61/488, 131 and U.S. Provisional Patent Application No. 61/488, 126. The disclosure of each of the aforementioned applications is incorporated herein by reference in its entirety for all purposes.

Summary of Illustrative Embodiments

[0002] The present application describes dashboard user interfaces, methods, systems, and environments for manipulating complex data captured by a large number of networked systems distributed over a wide geographic region to identify trends and opportunities in a given marketplace. Generally, the dashboard systems described herein are designed to utilize collected data representing hundreds of thousands of agreements, negotiations, and interactions within the dashboard environment to help predict, on the basis of past behavior, product trends, pricing trends, and industry participants that are likely to express interest in particular types of future opportunities. Industry participants and other entities may access the dashboard systems to view metrics derived through data analysis specific to a particular geographic region or territory, business class, and/or industry sector.

[0003] Furthermore, various dashboard systems described herein support benchmarking metric evaluation of a particular industry participant or other entity against peer performance. Peers of an industry participant or other member of the dashboard environment may be identified using a variety of techniques. In a first example, peer metrics may correspond to a top N (e.g., five, eight, ten, etc.) performers within a given market, or within the dashboard environment as a whole. Performance may be determined based upon financial share, market share, or performance specific to a metric presently highlighted within a dashboard interface. In another example, participants in the dashboard environment may be grouped by type (e.g., industry participant, intermediate participant, and classifications thereof) and ranked within the group. In a particular example, industry participants may be ranked based upon a weighted analysis of factors such as transaction volume, pricing value, and remittance share. From within the list of ranked participants, peers may be identified as being the nearest X above and Y below the present participant (e.g., three above and two below the present participant within the ranked list). In a more customized example, participants may be ranked based upon factors identified by the present participant. For example, the participant may list M factors (e.g., remittance share, feedback score, quote to bind ratio, etc.) based upon relative importance to the participant, and using the ranked list of factors the dashboard system may generate a ranked list of participants from which to identify the nearest (e.g., X above and Y below) peers to the present participant. In a further example, the participant may supply a threshold number of competitors, by name, to the dashboard system for use in presenting peer comparison data. The threshold, for example, may be selected to avoid the ability of the participant to identify competitor metrics as belonging to a particular competitor.

[0004] Certain dashboard systems described herein support an 'introduction' function, which brings together entities having an upcoming renewal opportunity with industry participants identified as demonstrating interest in similar renewal opportunities, proactively matching entity needs to industry participant appetite which, in turn, allows all parties to deploy their resources more efficiently and objectively. The 'introduction' function may be facilitated by an intermediate participant, such as a broker or coordinator. For example, the dashboard system may identify upcoming renewal opportunities and a number of industry participants for fulfillment of the renewal opportunity, and provide this information to the intermediate participant for review, allowing the intermediate participant to obtain the best terms and conditions for the entities serviced by the intermediate participant.

[0005] In some embodiments, dashboard systems described herein provide differing views of the same underlying data based upon a particular audience, for example determined based upon a user profile of an accessing user and/or a particular style of dashboard requested. In one example, the dashboard system may customize the view of particular underlying data for consumption by industry participants versus intermediate participants. Due to geographic variances, in another example, the dashboard system may customize a view of underlying data, for example to adjust to local currency, language, and/or legal limitations related to data presentation. In a third example, the dashboard system may customize a view of underlying data to narrow or broaden the depth of information presented based upon user level variances (e.g., a CEO level view may differ from a marketing level view). In another example, a particular data view may be customized based upon a subscription level of a particular user or enterprise with the dashboard environment (e.g., upon payment of a fee, a greater depth of information may be made available to the user or enterprise).

[0006] Prior to being made available to industry participants, in some embodiments, the dashboard system applies a rigorous "cleansing" process to the data to ensure that data made available to participants of the dashboard environment meets established standards. Data may also be processed by a processing entity, first to identify and correct anomalies, and then to perform the necessary analytics. In one example, the dashboard system collects and cleanses data prior to periodic releases. In a particular example, data may be released on a monthly, 45 day, or quarterly basis. Upon release, the dashboard system may further mingle the data into a data pool made up of significantly older data points, themselves anonymized and aggregated. The pooling process, for example, can be designed to ensure that there can be no possible facilitation of any collusive practices, whether in theory or in practice, through the introduction of the data introduced quarterly.

[0007] In some implementations, the data collected by the dashboard system includes information capturing in-progress negotiations between industry participants and entities participating within the dashboard environment. Trend analysis and forecasting features of the dashboard system may take advantage of the insight presented by the in-progress data to anticipate the shape and movement of markets. With knowledge of in-progress negotiations, the dashboard system may also analyze failures to consummate pending transactions between parties.

Brief Description of the Figures

The patent or application file contains at least one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee.

[0008] FIGS. 1 A through IF illustrate dashboard user interfaces for reviewing and analyzing transactional information and other marketplace metrics collected via a dashboard

environment. [0009] FIG. 2 illustrates a process flow diagram of an example method for preparing a report regarding target opportunities.

[0010] FIGS. 3A, 3B, and 3F illustrate example scatter plots for presenting information in a benchmarking report.

[0011] FIGS. 3C through 3E illustrate example bar graphs for presenting information in a benchmarking report.

[0012] FIGS. 4A and 4B illustrate example charts demonstrating sector distributions in a benchmarking report.

[0013] FIGS. 5A through 5C illustrate example bar graphs demonstrating product category distributions in a benchmarking report.

[0014] FIGS. 6A through 6F illustrate example bar graphs demonstrating product metric comparison to a selected peer group in a benchmarking report.

[0015] FIGS. 7A through 7C illustrate example scatter plots demonstrating product metric comparison to a selected peer group in a benchmarking report.

[0016] FIG. 8 illustrates a process flow diagram of a method that may be used to generate transactional metrics.

[0017] FIG. 9 illustrates a screen adapted to receive transaction data through a set of input fields.

[0018] FIG. 10 illustrates a display embodiment showing a set of aggregate remittance mapped by geographic region with corresponding trade counts.

[0019] FIG. 11 illustrates a display arrangement that maps aggregate remittance for each of set of industry participants.

[0020] FIG. 12 illustrates a display arrangement of transaction metrics that includes a premium amount of aggregate bound policies and an aggregate trade count statistic associated with each of a set of industry participants.

[0021] FIG. 13 illustrates a display arrangement of transaction metrics that include submit- to-quote ratios associated with each of a set of industry participants.

[0022] FIG. 14 illustrates a display arrangement of transaction metrics including industry participant declined submissions.

[0023] FIGS. 15A through 15C illustrate display arrangements involving pricing trends and rate changes.

[0024] FIG. 16A illustrates a trading flow display arrangement of one of three key metrics over a period of time. [0025] FIG. 16B illustrates a submission flow graph for a market segment where only the selected industry participant is plotted with an average competitor line.

[0026] FIG. 17 illustrates a data display arrangement of key metrics for four previous quarters for both a selected industry participant and top competitors to the industry participant.

[0027] FIGS. 18A and 18B illustrate display arrangements of industry participant losses.

[0028] FIG. 19A illustrates a display arrangement of aggregate industry participant declination reasons.

[0029] FIG. 19B illustrates a data display arrangement of declination reasons for an industry participant.

[0030] FIG. 19C illustrates a data display arrangement of declination reasons for an entity.

[0031] FIG. 19D illustrates a detail analysis of declination reasons.

[0032] FIG. 20A illustrates a display arrangement of intermediate participant insights based on industry participant performance survey(s).

[0033] FIG. 20B illustrates the intermediate participant insights display arrangement including options to display details on industry participant performance based on a lifecycle segment of the broking process.

[0034] FIG. 21 A illustrates a pipeline data display arrangement showing transaction opportunities for an industry participant forecast over an upcoming period of time.

[0035] FIG. 2 IB illustrates a report that may be generated from a pipeline display.

[0036] FIGS. 21C and 21D illustrate pipeline data display arrangements showing transaction opportunities for which one or more intermediate participants initially registered interest via the dashboard environment.

[0037] FIGS. 22A and 22B illustrate data display arrangements of premium share showing statistics of industry participant written premium and overall premium share across an intermediate participant company's top product lines.

[0038] FIG. 23 illustrates an exemplary portal screenshot that includes risk data.

[0039] FIG. 24 illustrates an example screenshot presenting high level summary information regarding competitive performance of a reinsurance industry participant within a global market.

[0040] FIGS. 25 A through 25F illustrate example screenshots presenting benchmarking of the performance of a reinsurance industry participant against a group of peer competitors.

[0041] FIGS. 26A and 26B illustrate example screenshots presenting a premium flow analysis between geographical regions. [0042] FIG. 26C illustrates an example screenshot presenting a cross sale analysis demonstrating penetration of a reinsurance industry participant's business.

[0043] FIG. 26D illustrates an example screenshot of a cedent purchase pattern analysis.

[0044] FIG. 26E illustrates an example screenshot of a performance analysis of a reinsurance industry participant compared to overall market pricing.

[0045] FIG. 27 illustrates a flow chart of an example method for determining strategic and tactical components of performance metrics.

[0046] FIGS. 28 A and 28B illustrate various aspects of an exemplary architecture implementing a dashboard environment.

[0047] FIGS. 28C and 28D depict a web server connected via a network to a number of tablets and other web-enabled devices through which a user may initiate and interact with the dashboard environment.

[0048] FIG. 29A illustrates an example integrated pipeline dashboard interface for reviewing information regarding opportunities.

[0049] FIG. 29B illustrates an example filter settings interface for filtering information presented within dashboard interfaces.

[0050] FIG. 29C and 29D illustrate detailed information of particular information panes of the integrated pipeline dashboard interface of FIG. 29 A.

[0051] FIG. 29E illustrates an example cross opportunities information interface.

[0052] FIG. 29F illustrates an example aggregate remittance overview dashboard interface.

[0053] FIG. 30A illustrates an example a marketing activity dashboard interface.

[0054] FIGS. 30B and 30C illustrate example survey metric information interfaces.

[0055] FIGS. 31 A, 31C, and 3 IE illustrate example survey metric comparison interfaces.

[0056] FIG. 3 IB illustrates an example icon setting interface for use with FIG. 31 A or FIG. 31C.

[0057] FIG. 3 ID illustrates an example key for understanding the survey metric comparison interface of FIG. 31C.

[0058] FIG. 32 illustrates an example method for gathering survey data, calculating survey metrics, and distributing survey report information.

[0059] FIG. 33 illustrates an example graphic analysis layout presenting financial metrics and rankings of industry participants.

[0060] FIGS. 34A through 34C illustrate example velocity change graphic interfaces illustrating percentage movements in remittance values. [0061] FIG. 35 illustrates an example scatter bar graph interface for reviewing transactions by remittance value.

[0062] FIG. 36 illustrates an example data input screen for supplying information associated with a prospective entity participant.

[0063] FIGS. 37A through 37E illustrate example graphic analysis layouts for presenting peer comparison metrics related to entity participants.

Detailed Description

[0064] The present disclosure describes methods, systems, and transactional environments for supply knowledge and insight to industry participants such as subscription service providers as well as intermediate participants such as dealers or salespersons in a dashboard environment. Aspects of the present disclosure discuss aggregating transactional data and generating transaction metrics (also referred to herein as transaction statistics) for display to an industry participant or intermediate participant via a computing device (e.g. through a dashboard user interface). Data on transactions may be collected from each of a number of participant (industry participant and intermediate participant) computing devices that are located across a wide geography. The data may be filtered for specific parameter values and these parameter values may be aggregated across the number of computing devices.

Transaction metrics may then be generated based on the aggregated data and organized into unique data combinations and display arrangements to assist an intermediate participant in servicing entity participants and industry participants. The transaction metrics may then be made available for display on one or more of the computing devices via a dashboard user interface.

[0065] Aspects of the present disclosure describe methods, systems, and transactional environments enabling participants (industry participants and intermediate participants) to interact with a dashboard environment via graphical user interface dashboards. Each dashboard includes a number of controls configured, upon selection, to present the participant with information relevant to the type of participant. The controls presented to a particular participant may be configurable based upon a user profile. For example, an industry participant may select various features (widgets, controls, and/or other information displays) to include within a customized dashboard. The level of customization, in some embodiments, may be based upon a participant level associated with the particular participant (e.g., customization may be an option based upon payment of an additional fee). In another example, features provided within the dashboard may be designated in part upon a user authorization level. For example, an intermediate participant employed by a brokerage may have access to a limited view of business metrics, while a CEO or board member may have unlimited access to business metrics.

[0066] In some embodiments, data may be collected by the dashboard system at three key points during the negotiation process of placing a subscription or purchase offer: first, when an entity (e.g., customer) or intermediate participant informs industry participants about an opportunity (referred to as a "trade" or a "submission"); second, when the chosen industry participants provide their response to an opportunity ("quote" or "decline"); and third, when the entity or intermediate participant decides which industry participant option it wants to accept (a "hit", a "win" or a "bind"). Opinion data may be collected by way of responses to questionnaires. The information may be collected by intermediate participants and directly inputted by them into a dashboard system database at the time of collection.

[0067] Beginning with the intermediate participants (e.g., dealers, insurance brokers, and reinsurance brokers, etc.), FIGS. 1 A and IB are screenshots of an example intermediate participant dashboard 100 for accessing entity (e.g., client or product purchaser/subscriber) and intermediate participant company (e.g., brokerage, dealership, etc.) information via a dashboard environment. The dashboard 100 is part of a web site, web portal, personal computer application, or mobile device application configured to allow the intermediate participant to interface with the dashboard environment.

[0068] The dashboard 100 is open to a "benchmarking" tab 114a. Other tabs available to the intermediate participant include an "overview" tab 114b and a "research and analytics" tab 114c. The intermediate participant may navigate to the additional tabs 114 to access different information. For example, the "overview" tab 114b may present a customized set of widgets presenting quick information important to daily activities of the intermediate participant. Example aspects of the "research and analytics" tab 114c are described in relation to FIG. IB, below.

[0069] As shown in FIG. 1 A, a "reports" pane 102 presents the intermediate participant with two navigation controls 116 for accessing benchmarking reports. An intermediate participant can utilize benchmarking reports to understand and confirm limits, compare entity (e.g., client/purchaser/subscriber) exposures and risk placements to the exposures and risk placements of an entity's peers, evaluate premium spending within a category (e.g., sector, geography, product, etc.), and challenge rates by reviewing whether an entity's rates are in line with peer rates (e.g., overall, per geography, per sector, per product, etc.). The intermediate participant may review product benchmarking reports, for example, to gain insights into entity sectors, product purchasing patterns, and/or entity positions in relation to selected peers. A first navigation control 116a, when selected, presents the intermediate participant a list of previously created benchmarking reports. Through the first navigation control 116a, in some examples, the intermediate participant can review, download (e.g., to a portable memory device), print, share (e.g., email, fax, etc.), and/or delete an existing report. A second navigation control 116b, when selected, presents the intermediate participant with a list of in-progress benchmarking reports, for example created in part on a prior occasion and suspended for further edit. In addition, in some implementations, previously created reports may be edited and modified by selecting the "finalized reports" navigation control 116a.

[0070] To create a new report, in some implementations, a user selects entity information via an "identify client" pane 104. The "identify client" pane 104 includes three navigation controls 118 - a "select existing client" control 118a, an "add prospective client" control 118b, and a "no client" control 118c. Upon activation of the "select existing client" control 118a, for example, the intermediate participant may be presented with a drop-down menu, search box, or other selection control for identifying an entity that currently has a product managed with the dashboard environment. The entity may be an existing client of the intermediate participant, or the entity may have an account with the dashboard environment without having a preexisting relationship with the intermediate participant. The "add prospective client" control 118b, upon selection, allows the intermediate participant to add an entity that does not yet have an account with the dashboard environment. The intermediate participant, for example, may enter a name of the new entity. The dashboard system may attempt to locate a same or similar entity name within the system participants, upon receipt of the identified prospective client, to avoid duplicates within the dashboard system and dashboard environment. If the entity does not yet exist within the dashboard environment, the prospective client may be added. Optionally, information regarding the prospective client may be added through the "add prospective client" control 118b. For example, the intermediate participant may enter business sector, geographical location, business size, and/or business maturity information to categorize the type of prospective client entered.

[0071] If the intermediate participant wishes to generate a report that is not associated with a particular entity, the intermediate participant selects the "no client" control 118c. In this manner, the intermediate participant can set up benchmarking reports to follow trends through the identification of key preexisting participant entities by identifying those entities using a "manage peers" pane 106. In another example, the intermediate participant may select the "no client" control 118c to create a basic report style that can later be copied and assigned to one or more prospective clients and/or existing entities. For example, upon receiving program information, the basic "no client" report may be modified through addition of prospective client information. In another example, the intermediate participant may prepare an example report for a prospective client which does not wish to disclose information at this time. This is also useful when the intermediate participant has no program information regarding a prospective client.

[0072] In some implementations, the intermediate participant can add one or more products to the new benchmarking report through a "manage products" pane 108. For example, the intermediate participant may select a "product categories" navigation control 122a to navigate information regarding product categories and product types. For example, upon selection of the "product categories" navigation control 122a, the intermediate participant dashboard 100 may present a list of product categories, such as, in some examples, automobile, casualty, employee benefits, employers liability, products liability, professional indemnity, and property insurance. If the intermediate participant selected a preexisting entity through the "select existing client" navigational control 118a, the intermediate participant dashboard 100 may promote the products purchased by the selected entity within product category selection. For example, the products purchased by the selected entity may be rendered in bold, a different color, highlighted, and/or promoted to the beginning of the list to allow the intermediate participant ease of selection of relevant products to the selected entity. The intermediate participant may instead or additionally opt to identify one or more products not yet purchased by the selected entity, for example as penetration opportunities.

[0073] Furthermore, within each product category, the intermediate participant may be provided one or more exposure variables for selection. For example, upon selection of an "exposure" control 122b, the intermediate participant may refine selected products by desired exposure(s). Within the category of professional indemnity, exposure variables may include, in some examples, revenue/sales, square footage, total assets, total insured value, and/or number of policy years. The intermediate participant may select a number of

product/exposure combinations through the "product categories" navigational control 122a and/or the "exposure" navigational control 122b. The dashboard system, in some

embodiments, limits the maximum number of products or product/exposure combinations available within a single report. In a particular example, the dashboard system may limit the intermediate participant in selecting more than four, five, or eight products. Larger reports, for example, may become unwieldy or confusing for an entity to digest, and multiple reports may be generated on behalf of a single entity. [0074] The intermediate participant may choose to select a target opportunity for the selected (preexisting or prospective) entity through a "target opportunity" control 122d. For example, the intermediate participant dashboard 100, upon selection of the "target opportunity" control 122d, may be present the intermediate participant with one or more available opportunities for one or more of the selected product/exposure combinations. For example, for any product/exposure combination not already purchased by the selected entity, the dashboard system may search for available opportunities. Each opportunity presented, for example, may include a premium value, exposure amount, limit, and deductible. If, instead, no available opportunity has been identified for the selected entity for a particular

product/exposure combination, the intermediate participant dashboard 100 may issue an alert to the intermediate participant (e.g., pop-up message, flag, warning icon, etc.) regarding a lack of available opportunity.

[0075] If the selected entity has provided program information, the intermediate participant may select a "custom opportunity" navigational control 122d to enter customized opportunity information. For example, upon selection of the "custom opportunity" navigational control 122d, the intermediate participant dashboard 100 may present the intermediate participant with an interface configured for entry of custom data representing exposure value, premium, limit, deductible type, and deductible value. Although the custom opportunity is entered by the dashboard system for the purposes of the present report, the custom opportunity, in some embodiments, is not added to the dashboard environment for selection outside of the scope of the present report.

[0076] Upon identification of an entity using the navigation controls 118 (and, optionally, one or more products via the "manage products" pane 108), the intermediate participant can identify peers of the entity (or, if no entity was identified, a selected group of entities) through the "manage peers" pane 106. By selecting a "view available peers" navigational control 120a, for example, the intermediate participant dashboard 100 may present the intermediate participant with an interface for selection of peers from a list of existing participant entities of the dashboard environment. The peers, in some embodiments, may be limited to entities that have purchased the products identified by the intermediate participant through the "manage products" pane 108. To aid in selection, the intermediate participant dashboard 100 may present selected information regarding each available peer such as, in some examples, a country, premium level, exposure amount, limit, deductible type, industry, and business sector description. [0077] Identification of an existing entity as a peer of the identified entity (e.g., existing or prospective), in some examples, can include comparing entity demographic information. In one example, the peers of an identified entity include other entities within a same

employment sector. The demographics, in other examples, can include geographic location, size, and/or maturity. By selecting a "view candidate peers" navigational control 120b, in some implementations, the intermediate participant dashboard 100 presents the intermediate participant with a list of candidate peers, evaluated based upon demographic information corresponding to the selected entity. In other implementations, the "view candidate peers" navigational control 120b, upon selection, presents the intermediate participant with a list of the one or more peers already selected (e.g., while the intermediate participant is continuing to fill in an incomplete report). In further embodiments, the intermediate participant may supply an example peer (e.g., a main competitor of a prospective client), and the dashboard system may select a list of candidate peers based upon the demographic information of the example peer. For example, upon identification of a particular fertilizer company, other agricultural and/or industrial chemical organizations of a same size/geography/maturity may be identified. Further, the dashboard system may suggest industries and/or product interests based upon the example peer demographic information. For example, upon identification of a delivery service, the dashboard system may recommend searching for peers based upon organizations that have purchased motor fleet products.

[0078] In some implementations, to focus in on the type peers the intermediate participant is interested in, the intermediate participant may select a "peers by geographic region" navigational control 120d, a "peers by industry" navigational control 120e, and/or a "peers by limit range control" 120f. Additionally, in some implementations, the filters may be used consecutively or concurrently, such as peers by geography and by industry or peers by limit range and by industry. Other possibilities for filtering entities for selection include peers by premium range, peers by exposure range, peers by deductible type, and/or peers by business maturity.

[0079] When presenting potential peers on the basis of product/exposure comparison, the dashboard system may highlight the quality of data available for each peer. For example, the intermediate participant may wish to obtain data representative of at least the past two years. Any potential peer without available information for the full time period may be deemed ineligible as a candidate peer. Further, although data is available, in some embodiments the dashboard system identifies a concern towards the quality of the data. For example, the data for a particular candidate peer may be deemed questionable due to one or more inconsistencies between data values maintained by the dashboard environment. Inconsistencies may include, in some examples, differences in dashboard system premium value and billing system premium value, an exposure value lower than a threshold level (e.g., 10 for value exposures and 4 for number of exposures), limits less than a threshold level (e.g., 10), and/or premiums less than a threshold level (e.g., 10). In the circumstance of missing data or severe validation errors, the global risk information dashboard system may disable selection of a particular candidate peer (e.g., data cannot be trusted).

[0080] In some implementations, the intermediate participant selects a "select peer opportunities" navigational control 120c to refine the candidate peers by particular opportunities (e.g., products / exposures). For example, a given candidate peer may have purchased a number of products through the dashboard environment. The intermediate participant may refine candidate peers, further, by applying one or more filters. The filter criteria, in some examples, may include geographic region, year(s) of data to review, premium amount (or range), limit amount (or range), exposure amount (or range), industry, and/or Standard Industrial Classification (SIC) code. The dashboard system, in some embodiments, requires a minimum threshold number of selected peers relevant to each selected opportunity for generation of a report. For example, the dashboard 100 may require that the intermediate participant activate at least five peer candidates for a given opportunity opportunities. Additionally, the dashboard 100 may limit the intermediate participant to a threshold maximum number of opportunities, such as twenty opportunities.

[0081] In some implementations, upon selection of peer opportunities, the intermediate participant dashboard 100 provides the intermediate participant the opportunity to select one or more peer comparison charts for presentation of peer comparison benchmarking statistics. Within a "manage charts" pane 110, the intermediate participant is presented with graphical display options, including a number of types of scatter plots 124 and bar graphs 126, each presenting different statistical information.

[0082] As illustrated, the scatter plots options 124 include an "exposure vs. premium" plot type control 124a, a "limit vs. exposure" plot type control 124b and a "limit vs. premium" plot type control 124c. Turning to FIG. 3 A, an example plot 300 illustrates a scatter distribution of exposure versus premium (e.g., as made available by the "exposure vs.

premium" plot type control 124a). Each data point, for example, may correspond to a particular peer. Further, if the intermediate participant opted to include data from more than one year, in some embodiments, each year of peer data may be illustrated separately (e.g., a 2011 data point and a 2012 data point). If an existing entity was identified, a data point representing the entity is included within the scatter plot 300. In this manner, the entity may compare its data metric to peer distribution of the same metric. The peers, as noted earlier, are rendered anonymously to protect individual data representations. Similar in rendering to the example plot 300, an example plot 320 of FIG. 3B illustrates a scatter distribution of limit versus exposure (e.g., as made available by the "limit vs. exposure" plot type control 124b), and an example plot 390 of FIG. 3F illustrates a scatter distribution of limit versus premium (e.g., as made available by the "limit vs. premium" plot type control 124c).

[0083] When reviewing scatter plots, the more linear the peer data appears in the plot, the stronger the relationship between the two elements. As illustrated in FIGS. 3 A and 3F, the selected peers do not represent a strong relationship trend between the elements, while the peers in FIG. 3B do represent a strong relationship trend between the limit and revenue/sales elements. As noted above, to protect statistical data representing individual entities, the entities are not identified within the plots 300 and 320. In the circumstance of a preexisting selected entity, however, the plot representing the selected entity may be identified using a unique identifier (e.g., shape, color, and/or label). In some embodiments, the scatter plots 300, 320, and 390 illustrate "summary" or "preview" plots. For example, in a computer- based hyperlinked report, selection of one of the scatter plots 300, 320, or 390 may present the intermediate participant with a more detailed version of the selected plot 300, 320, or 390 similar to, for example, the graph 720 of FIG. 7B. In another example, during report creation, the user interface may present thumbnail or preview plots to the intermediate participant upon the intermediate participant having entered a threshold number (e.g., five) of peer opportunities.

[0084] Returning to FIG. 1 A, as illustrated, the bar graphs 126 include a "rate per exposure" graph type control 126a, an "aggregate deductible, limit and rate" graph type control 126b, and a "per occurrence deductible, limit, and rate" graph type control 126c. Example bar graphs are illustrated in FIGS. 3C through 3E. As noted above, to protect statistical data representing individual entities, the entities are not identified within the graphs 340, 360, and 380. In the circumstance of a preexisting selected entity, however, the bar representing the selected entity may be identified using a unique identifier (e.g., shape, color, and/or label).

[0085] Turning to FIG. 3C, an example graph 340 illustrates a graphic comparison of rate per exposure (e.g., as made available by the "rate per exposure" graph type control 126a). An example graph 360 of FIG. 3D illustrates a graphic comparison of per occurrence deductible, limit and rate (e.g., as made available by the "per occurrence deductible, limit, and rate" graph type control 126c). The graph 360 reflects a comparison of five different peers sharing a particular deductible type. Rate information is represented by scatter plot markers applied upon each bar, while each bar represents both a deductible (lower portion) as well as a limit (upper portion). Turning to FIG. 3E, an example bar graph 380 illustrates a graphic comparison of aggregate deductible, limit and rate (e.g., as made available by the "aggregate deductible, limit, and rate" graph type control 126b). The graph 380 reflects a comparison of six different entities sharing a particular deductible type. Rate information is represented by scatter plot markers applied upon each bar, while each bar represents both a deductible (lower portion) as well as a limit (upper portion). As with the scatter plots of FIGS. 3 A, 3B, and 3F, the bar graphs of FIGS. 3C through 3E may represent thumbnail or preview graphs, available to the intermediate participant to preview report information during the report preparation process. The graphs presented within the report may include a higher level of detail than the information presented within the bar graphs of FIGS. 3C through 3E.

[0086] Returning to FIG. 1 A, in preparing the finalized report, a "report preview" pane 112 includes a number of controls 128 that allow the intermediate participant to select

presentation options and to preview the report information. A "sector overview" navigational control 128a, upon selection, presents the intermediate participant with an interface for adding industries into a sector overview section of the report. The sector overview section provides the intermediate participant with average entity statistics representing product activity of one or more particular geographies and industries within the dashboard

environment. For example, the sector overview section may present statistical information regarding entity portfolio composition and entity (premium) spending. To initialize the sector overview portion of the benchmarking report, the intermediate participant may be prompted to select at least one geographical region and at least one industry. In a particular example, the intermediate participant may select a global geographical region and the health and medical products and services industry. Responsive to these selections, the dashboard system may generate graphical displays for presenting sector-based analysis of entity statistical information. Example graphical displays are provided in FIGS. 4A and 4B.

[0087] Turning to FIG. 4A, a doughnut graph 400 illustrates average percentages of premium by product within a selected industry. The graph segments include the main products of financial lines, casualty /liability, property, automobile, and employers' liability, as well as a remaining wedge designated "other." The "other" segment, for example, may represent products that are not commonplace throughout the selected industry and/or represent a minimal portion of overall premium budget within the selected industry. The intermediate participant may review the doughnut graph 400, for example, to identify products that the selected entity (e.g., prospective or preexisting) may be interested in purchasing based upon products purchased by other entities within the same industry.

[0088] FIG. 4B illustrates a bar graph 420 representing premium distribution among participant entities of the dashboard environment for the selected industry. The bar graph 420 breaks down premiums into ranges, with bars representing the frequency of entities purchasing at a particular premium level. The intermediate participant may review the bar graph 420 to identify the size of entities represented in the selected industry. As illustrated in the bar graph 420, the dashboard environment includes a range of entities, from very small to very large, within the selected industry.

[0089] Returning to FIG. 1 A, a "product category overview" navigational control 128b within the "report preview" pane 112, upon selection, presents the intermediate participant with a statistical analysis of information regarding exposures, limits, and premium of participant entities of the dashboard environment for each product category selected via the "product categories" navigational control 122a of the "manage products" pane 108. FIGS. 5A through 5C illustrate example graphical displays of statistical product category information. Turning to FIG. 5A, a bar graph 500 illustrates an exposure distribution for entities that purchased a selected product (e.g., general liability). The bar graph 500 breaks down total insured value into ranges, with bars representing the frequency of exposures of the selected product at a particular value level. Turning to FIG. 5B, a bar graph 520 illustrates a limit distribution for entities that purchased a selected product. The bar graph 520 breaks down limits into ranges, with bars representing the frequency of entities at a particular limit range. Turning to FIG. 5C, a bar graph 540 illustrates a premium distribution for entities that purchased a selected product. The bar graph 540 breaks down premium into ranges, with bars representing the frequency of premium purchase at a given premium level range. An intermediate participant may review the bar graphs 500, 520, and 540 to determine a profile for peers within the industry of the selected entity, purchasing products in the selected category.

[0090] Return to FIG. 1 A, a "peer product comparison" navigational control 128c within the "report preview" pane 112, upon selection, presents the intermediate participant with a statistical analysis of information regarding comparisons between the selected entity and the selected peer group relative to premium, exposure, and limit values. The intermediate participant may review information through the "peer product comparison" navigational control 128c to determine relative alignment of the selected entity with the peer group. Example graphical displays for peer product comparison are illustrated in FIGS. 6A through 6C and FIGS. 7 A through 7C.

[0091] Turning to FIGS. 6A through 6C, a series of bar graphs illustrate a peer group analysis including average value for each of premium, limit, and exposure. FIG. 6A, for example, illustrates an example bar graph 600 of premium values for each entity in the peer group for the particular product. A line 602 illustrates an average premium value. As noted above, to protect the identity of statistics pertaining to a particular entity, the entities are labeled CaOl through Ca08. The selected entity, if existing and having purchased this particular product, may be represented in a manner that draws attention to the selected entity, such as, in some examples, through highlighting, using a different color or outline, and/or labeling the bar representing the selected entity with the entity's name. As illustrated, entity participant "ABC Ltd." is illustrated in a darker shade as the surrounding peer bars. Similarly FIG. 6B illustrates an example bar graph 620 of limit values for each entity in the peer group for the particular product. A line 622 identifies the average limit value. Finally, FIG. 6C illustrates an example bar graph 640 of total insured values for each entity in the peer group for the particular product. A line 642 identifies the average insured value. Other graphical analysis may include a rates graph 660 of FIG. 6D illustrating premium per revenue/sales for a selected product (general liability), a price per million of limit purchased graph 680 of FIG. 6E illustrating the ratio of each peer's premium compared to each one million value of limit, a per occurrence deductible graph 690 of FIG. 6F, and/or an aggregate deductible, limit, and rate graph specific to the selected product (similar to the bar graph 380 of FIG. 3E).

[0092] FIGS. 7 A through 7C illustrate example scatter plots demonstrating product metric comparison to a selected peer group in a benchmarking report. Turning to FIG. 7A, a scatter plot 700 illustrates a distribution of limit versus premium for the selected peer group and the selected product. Each peer within the peer group, CaOl through Ca05, is individually labeled within the scatter plot 700. The selected entity, if existing and having purchased this particular product, may be represented in a manner that draws attention to the selected entity, such as, in some examples, through highlighting, encircling, labeling with an icon such as an arrow, and/or labeling the entity within a key 702 with the entity name 704. The key 702 also includes a premium value and exposure value for each peer entity CaOl through Ca05. As illustrated in the scatter plot 700, the premium generally increases as the limit increases. If the selected entity is outlying from the linear trend demonstrated by the scatter plot 700, the intermediate participant may suggest that the entity discuss a remarketing decision. Similar to the scatter plot 700, FIG. 7B is an example scatter plot 720 representing limit value versus premium value for each of the peer entities CaOl through Ca08, where a key 722 references both the premium value and the limit value for each peer entity CaOl through Ca05 as well as entity participant ABC Ltd. 724. Furthermore, FIG. 7C is an example scatter plot 740 representing limit value versus exposure for each of the peer entities CaOl through Ca05, where a key 742 references both the total insured value and the limit value for each peer entity CaOl through Ca05 as well as entity 744. The scatter plot 740, for example, is illustrated for exposure variables that are "value" exposures rather than "number of exposures.

[0093] Returning to FIG. 1 A, upon configuring the report information to satisfaction, the intermediate participant may select a "full report" navigational control 128d to review complete information presented within the benchmarking report. Upon selection of the "full report" navigational control 128d, for example, the intermediate participant dashboard 100 may present the intermediate participant with a user interface for removing or reordering report pages (e.g., placement of the sector overview prior to the peer product comparison, etc.). Further, the user interface may include controls allowing the intermediate participant to select a currency for presentation of monetary values and/or select a geographic region for targeting the report. The intermediate participant, at this time, may choose to name and save the report as a finalized report or as a work-in-progress report (if the intermediate participant identifies more work to accomplish in preparing the report information).

[0094] FIG. 2 illustrates a process flow diagram of an example method 200 for preparing a benchmarking report presenting statistical information pertinent to an entity identified by an intermediate participant. The method 200, for example, includes steps an intermediate participant may perform via the intermediate participant dashboard interface 100 of FIG. 1 A.

[0095] In some implementations, the method 200 begins with receiving information indicating selection of an entity (202). Information may be provided by a user to a dashboard system of a dashboard environment through a software application interface. For example, as discussed in relation to FIG. 1 A, an intermediate participant may enter entity information via one of the navigational controls 118a within the "identify client" pane 104 of the intermediate participant dashboard 100.

[0096] If the entity is an existing entity participant (204), in some implementations, an entity industry sector is retrieved (208). For example, if an entity was selected via the "select existing client" navigational control 118a, as described in FIG. 1A, the dashboard system may retrieve industry sector information associated with the identified entity as well as, in some embodiments, additional demographic information (e.g., geographic region, maturity, etc.).

[0097] If, instead, the entity is a prospective entity (204), an indication of the prospective entity's industry sector may be received (206). For example, prospective entity information, including an entity name and entity industry sector, may be entered by an intermediate participant using the "add prospective client" navigational control 118b of FIG. 1A.

[0098] In some implementations, information is received indicating selection of one or more products (210). The product information, for example, may include one or more product categories and/or product exposures selected from a menu system. For example, an intermediate participant may select product categories via the "product categories" navigational control 122a of the intermediate participant dashboard 100 of FIG. 1A and product exposures via the "exposure" navigational control 122b. The product information, in some examples, may include exposure value, premium, limit, deductible type, and/or deductible value.

[0099] In some implementations, a target opportunity is identified (212). Using the information indicating selection of one or more products, for example, the dashboard system may match one or more target opportunities to the indicated entity. The target opportunities, in this example, may be presented to the user for selection. For example, target opportunities may be reviewed and selected by an intermediate participant through the "target opportunity" navigational control 122d of the intermediate participant dashboard 100 of FIG. 1A. In another example, an intermediate participant may enter a custom opportunity involving a specified product and exposure. For example, an intermediate participant may enter a custom opportunity via the "custom opportunity" navigational control 122c of the intermediate participant dashboard 100 of FIG. 1A.

[00100] In some implementations, selection of one or more peers of the indicated entity is received (214). The dashboard system may present a user with options regarding peers of the indicated entity. For example, using the "view available peers" navigational control 120a of the intermediate participant dashboard 100 of FIG. 1A, an intermediate participant may browse participant entities of a dashboard environment for peer entities of the indicated entity. Further, the dashboard system may propose one or more peer entities, for example based upon demographic information associated with the indicated entity and/or filtering entities for those entities that have purchased the one or more products indicated by the user. For example, by selecting the "view candidate peers" navigational control 120b, an intermediate participant may access a list of candidates proposed by the dashboard system. Further, a user may browse a list of filtered entities by applying filters to an entity database, such as, in some examples, industry, geographic region, and limit range filters. In a particular example, the navigational controls 120d through 120f provide filtering options via the intermediate participant dashboard 100 of FIG. 1A.

[00101] In some implementations, report parameters are received (216). For example, a user may identify, from options presented within a user interface, a number of statistical analysis features, such as bar graphs, scatter plots, and pie graphs, representing information pertinent to the indicated entity. In a particular example, an intermediate participant may interact with the navigational controls 124 and 126 within the "manage charts" pane 110 of the

intermediate participant dashboard 100 of FIG. 1A, as well as the "sector overview" navigational control 128a, "product category overview" navigational control 128b, and/or "peer product comparison" navigational control 128c to select benchmarking report options.

[00102] In some implementations, a preview report is prepared (218). Based upon the information provided to the dashboard system, report preview information may be generated for display upon a user interface. For example, an intermediate participant may select the "full report" navigational control 128d of the intermediate participant dashboard 100 of FIG. 1 A to trigger preparation of a report preview.

[00103] In some implementations, the report preview is provided to the requesting computing system (220). The report preview may be presented within the user interface that the user interacted with to provide the various information during the preceding steps of the method 200. In other examples, the report preview may be downloaded to a memory region within the requesting computing system or transmitted to the user via email. Furthermore, the report preview may be maintained (e.g., stored) by the dashboard system for later access.

[00104] Although illustrated in a particular order, in other implementations, one or more steps may be in a different order. For example, selection of one or more peers may be received (214) prior to indication of selection of one or more products (210). Furthermore, one or more steps, in other implementations, may be removed or added. For example, in some implementations, rather than identifying a target opportunity, the information regarding the products and peers may be combined to prepare a report more general to a target and industry. Other modifications are possible without deviating from the scope of the method 200.

[00105] As shown in FIG. IB, the dashboard 100 is open to the "research & analytics" tab 114c. In a "renewal analysis" pane 132, the intermediate participant is provided with a series of navigational controls 140 to access information regarding subscription renewals (e.g., a term subscription, insurance plan, or service contract, etc.). Upon selection of a "percentage change renewals" control 140a, the intermediate participant may be provided with a graphical analysis of percentage change in subscription renewals over a period of time. The period of time, in some embodiments, includes a forecast into future events, such that the dashboard system estimates projected renewal pricing trends based upon a historical data analysis. An example screenshot of a graphical display of projected pricing trends is presented in FIG. 15 A, described in more detail below. Upon selection of a "percentage rate change on renewal" control 140b, the intermediate participant dashboard 100 may present the intermediate participant with a graphical analysis of percentage rate change on renewal over a period of time. The period of time, in some embodiments, includes a forecast into future events, such that the dashboard system estimates projected renewal rate change trends based upon a historical data analysis. An example screenshot of a graphical display of projected rate change trends is presented in FIG. 15C, described in more detail below. Upon selection of a "percentage renewal rate components" control 140c, the intermediate participant dashboard 100 may present the intermediate participant with a graphical analysis of individual sector components (e.g., industries such as manufacturing, marine,

pharmaceuticals and chemicals, etc.) of renewal rates over a period of time. The period of time, in some embodiments, includes a forecast into future events, such that the dashboard system estimates projected renewal rate change trends based upon a historical data analysis. An example screenshot of a graphical display of projected component rate change trends is presented in FIG. 15B, described in more detail below. Furthermore, as illustrated in FIGS. 15A and 15C, the percentage change in renewals and percentage rate change on renewal analysis may be filtered by product (as made available by a "renewals by product" control 140d), industry (as made available by a "renewals by industry" control 140e), and geography (as made available by a "renewals by geography" control 140f). Combinations of filters are possible. For example, the intermediate participant may use the "renewal analysis" pane 132 of the intermediate participant dashboard 100 to gain access to statistical analysis of percentage change in renewals by geography and by product, or to gain access to statistical analysis of percentage rate change on renewal by industry and by geography. Other filtering combinations are possible.

[00106] A "quote analysis" pane 134 presents the intermediate participant with options for reviewing statistics related to the outcomes of quotes, captured along the timeline from request to bind. For example, a "carrier declination" control 142a, upon selection, may cause the intermediate participant dashboard to present a graphical analysis of industry participant (e.g., insurance carriers, reinsurance carriers, etc.) declination reasons to the intermediate participant. An example graphical user interface for reviewing industry participant declination reasons is illustrated in FIG. 14, described in more detail below. Conversely, detailed analysis of entity declination reasons and entity acceptance reasons are available to the intermediate participant using a "client declination" control 142b and a "client acceptance" control 142c. Selection of a "submit-to-quote" control 142d presents the user with an analysis of percentage submissions quoted by each of a number of industry participants. For example, as illustrated in FIG. 13 (described in greater detail below), percentage submission-to-quote is presented for each of the top five industry participants. The top five industry participants, in some examples, may be identified as the top five performing industry participants within the dashboard environment, the five industry participants determined to be most similar to the present industry participant, and/or the top five performing industry participants for the type metrics presently presented, etc.). A "quote by deductible type" control 142e, upon selection, allows the intermediate participant to review percentages of quotes submitted based upon deductible type. Similarly, a "quote by deductible value" control 142f, upon selection, allows the intermediate participant to review percentages of quotes submitted based upon deductible ranges, as illustrated in FIG. 13.

[00107] Turning to a "product and industry analysis" pane 136, a series of navigational controls 144 provide an intermediate participant with access to statistics regarding products offered via the dashboard environment and purchasing trends across industry sectors. Upon selection of a "top products" control 144a, the intermediate participant dashboard 100 presents the intermediate participant with a graphical display of top products by aggregate premiums. An example graphical display of top products is illustrated in FIG. 11, described in further detail below. Similarly, selection of a "top industries" control causes presentation of a graphical display of the top industries by aggregate premiums (illustrated in FIG. 11). Furthermore, the information, as illustrated in FIG. 11, may be filtered by geography (e.g., using a "product by geography" control 144c) and/or by industry (e.g., using an "industry by geography" control 144d). Further, the analysis may be broken down to illustrate top industry participants for each of top products (e.g., using a "product by carrier" control 144e) and top industries (e.g., using an "industry by carrier" control 144f).

[00108] A "market analysis" pane 138 includes a series of navigational controls 146 for accessing analysis of trade volume and aggregate premiums across industry participants participating in the dashboard environment. A "trades by carrier" control 146a, upon selection, presents an intermediate participant with aggregate numbers of trades by industry participant over a given period of time. The information may additionally include identification of a bound premium associated with the aggregate trades, accessible for example via a "carrier by aggregate premium" control 146d. As illustrated in FIG. 12, for example, a bar graph illustrates both aggregate trades and bound premium. The bound trades statistics and aggregate premium statistics may further be filtered by geography (using a "trades by carrier by geography" control 146b and/or "carrier by premium by geography" control 146e) and/or by industry (using a "trades by carrier by industry" control 146c and/or a "carrier by premium by industry" control 146f). Additional filtering options and

combinations are possible, such as industry participant by premium and by geography.

[00109] Reinsurance industry participants may also access the dashboard system via a dashboard interface to review and analyze data relevant to reinsurance industry participants. FIGS. 1C and ID illustrate reinsurance industry participant dashboard user interfaces for reviewing and analyzing reinsurance transaction information. Turning to FIG. 1C, a dashboard 130 is part of a web site, web portal, personal computer application, or mobile device application configured to allow an intermediate participant acting as a reinsurance intermediate participant to interface with the dashboard system and dashboard environment. The dashboard 130 includes the same tabs 114 as illustrated in FIGS. 1 A and IB in relation to intermediate participant dashboard interfaces, but each of the tabs 114 now present information relevant to reinsurance intermediate participants. However, similar information presented in relation to insurance intermediate participants may be relevant to reinsurance intermediate participants and vice-versa. For example, the reinsurance dashboard 130, in other embodiments, may include the "product and industry analysis" pane 136 of FIG. IB and/or the "quote analysis" pane 134 of FIG. IB. In some implementations, selection of the "overview" tab 114b presents the user with an information overview display similar to the screenshot of FIG. 23, presenting a summary analysis of risk data (described in greater detail below). As shown in FIG. 1C, the "benchmarking" tab 114a is active.

[00110] Beginning with a "reports" pane 150, a "market reports" navigational control 162a, upon selection, may present the reinsurance industry participant with a report-style review of present market statistics, for example combining information accessible through one or more of a "market pricing" pane 152, a "program participation" pane 154, a "market flow analysis" pane 158, and a "premium flow analysis pane" 160. Additionally, in some embodiments, a market report may include information accessible through the research and analytics tab 114c, as described below in relation to FIG. ID. In one example, the "market reports" control 162a, upon selection, may generate a synopsis of market analytics similar to a screenshot 2400 of FIG. 24 (described in further detail below). The "reports" pane 150 also includes a "carrier reports" control 162b, selectable to access a report-style review of analytical information pertaining to industry participants. For example, the industry participant reports may include information accessible through a "client purchasing patterns" pane 156 and/or an industry participant dashboard 190, described below in relation to FIGS. IE and IF. Report preparation, in a general sense, may be similar in method to the steps described in relation to method 200 as described in FIG. 2.

[00111] Turning to the "market pricing" pane 152, upon selection of an "overall pricing" navigational control 164a by the reinsurance industry participant, the reinsurance dashboard 130 presents the reinsurance industry participant with an analysis of pricing indices over a period of time. For example, as illustrated in FIG. 26E, a screenshot 2680 illustrates a comparison of the reinsurance industry participant's historic pricing to market averages quarter-by-quarter over two years. The line graph provides the reinsurance industry participant with insight into the reinsurance industry participant's performance relative to overall market pricing. As illustrated, a series of drop-down menus 2682, upon selection, may be used to filter the information by category (menu 2682a), line of business (menu 2682b), product (menu 2682c, e.g., quota share, excess of loss, etc.), and/or geographic region (menu 2682d). In other embodiments (not illustrated) the period of time and/or the time increments may be manipulated to refine or enlarge the scope of analysis. In some examples, the reinsurance industry participant may be provided the opportunity to review a month-by-month analysis over a period of six months or an annual analysis over the period of ten years. Furthermore, returning to FIG. 1C, rather than overall pricing analytics, the reinsurance industry participant may opt to focus on a particular pricing category, such as pricing by aggregate premium index (using a "pricing by aggregate premium index" control 164b) and pricing by limit index (using a "pricing by limit index" control 164c).

[00112] In the "program participation" pane 154, a series of navigational controls 166 provide the reinsurance industry participant with access to information pertaining to allocation of the reinsurance industry participant's premium by attachment point and layer limit. For example, by activating a "participation by premium" navigational control 166a, a reinsurance industry participant may be directed to an information display similar to an example screenshot 2550 of FIG. 25D. Turning to FIG. 25D, two side-by-side charts 2552 illustrate a comparison between the reinsurance industry participant's percentage of premium allocation per attachment point and layer limit and the average reinsurance industry participant peer percentage of premium allocation per attachment point and layer limit. The participation charts 2552 may furthermore be color-coded to draw attention to high participation combinations as well as low participation combinations. For example, the reinsurance industry participant demonstrates low participation 2556 for a five to ten million dollar layer limit with a zero to two million dollar attachment point and high participation 2558 for a zero to two million dollar layer limit with a zero to two million dollar attachment point, as referenced by a participation key 2560. In some embodiments, the information presented within the screenshot 2550 is directed towards a particular country. A series of drop-down menus 2554 provide the reinsurance industry participant with the opportunity to filter the information by one or more of a "line of business" menu 2554a (e.g., similar to a "participation by business line" navigational control 166b of FIG. 1C), a "product" menu 2554b (e.g., similar to a "participation by product" navigational control 166c of FIG. 1C), a "region in country" menu 2554c (e.g., similar to a "participation by geography" navigational control 166d of FIG. 1C), a "view" menu 2554d (e.g., similar to a "participation by view" navigational control 166d of FIG. 1C), and an "incumbency" menu 2554e providing the options, for example, of existing business and new business (e.g., similar to a "participation by incumbency" navigational control 166f of FIG. 1C). An incumbent, for example, may refer to a reinsurance industry participant with any share greater than zero on a program, contract, or layer.

[00113] Returning to FIG. 1C, the "client purchasing patterns" pane 156 includes a number of navigational controls 168 for reviewing buying behaviors of cedents across lines of business. The information accessible via the navigational controls 168, for example, may be similar to a graphical analysis provided in a screenshot 2660 of FIG. 26D. Turning to FIG. 26D, a bar graph illustrates, for each of ten lines of business, average program structure data per line of business (e.g., accessible via an "average program structure by business line" control 168a of FIG. 1C). For example, the bar graph includes the following data: a maximum gross written premium percentage 2662 (e.g., accessible via a "max GWP % vs. peers" control 168c of FIG. 1C), an average number of participants per program 2664 (e.g., accessible via an "average participants per program" control 168b of FIG. 1C), and an average security rating 2666 (e.g., accessible via an "average security rating" control 168d of FIG. 1C). In some embodiments, the information presented within the screenshot 2660 is directed towards a particular country. Additionally, a series of drop-down menus 2668 are available to the reinsurance industry participant to filter the information presented within the bar graph. For example, a "region in country" menu 2668a, when selected, filters the information by geographical region, a "product" menu 2668b, when selected, filters the information by product type, a "cedent type" menu 2668c, when selected, filters the information by cedent type, and a "premium band" menu 2668d, when selected, filters the information by range of premium values. Filters may be applied individually or together to refine information presented by the bar graph. In other embodiments (not illustrated), the reinsurance dashboard 130 may include filtering options within the "client purchasing patterns" pane 156 of FIG. 1C.

[00114] As shown in FIG. 1C, the "market flow analysis" pane 158 includes navigational controls 170 directed towards accessing information regarding market flow analytics, such as benchmarking analysis of the reinsurance industry participant's requested line versus signed line by line of business as well as market capacity versus capacity utilization by line of business. The navigational controls 170, for example, may provide the reinsurance industry participant with access to graphical output such as the display illustrated in a screenshot 2516 of FIG. 25B.

[00115] Turning to FIG. 25B, the screenshot 2516 includes a "requested line vs. signed line benchmark" graph 2518 illustrating, for each of a reinsurance industry participant 2522a, an average peer 2522b, a best in class peer 2522c, and a market average performance 2522d, data points including maximum 2520a, average 2520b, and minimum 2520c percentages of requested line to signed line. The information illustrated in the graph 2518, for example, may be accessible via a "market flow" control 170a of FIG. 1C. Using a "line of business" menu 2528c, the graph 2518 may be filtered by a selected line of business, similar for example to using a "flow by business line" control 170c of FIG. 1C. Similarly, using a "product" menu 2528d, the graph 2518 may be filtered by a selected product type, similar for example to using a "flow by product" control 170e of FIG. 1C.

[00116] Next to the graph 1518, a "market capacity vs. utilization" bar graph 2530 illustrates a comparison of market capacity 2524a to market capacity utilization 2524b by line of business. Further, beneath the bar graph, a percentage capacity utilization 2526 is displayed. Information similar to the information provided by the bar graph 2530, for example, may be accessible via a "market capacity" control 170b of FIG. 1C. In some embodiments, the information presented within by the bar graph 2530 is directed towards a particular country. Using a "line of business" menu 2528c, the graph 2530 may be filtered by a selected line of business, similar for example to using a "capacity by business line" control 170d of FIG. 1C. Similarly, using a "product" menu 2528d, the graph 2530 may be filtered by a selected product type, similar for example to using a "capacity by product" control 170f of FIG. 1C. Additional filters applicable to the graphs 2518 and 2530 (not illustrated within the "market flow analysis" pane 158 of FIG. 1C) include a "region in country" menu 2528a for filtering by geographic region, a "view" menu 2528b for filtering by cedent location, and an

"incumbency" menu 2528e for filtering by incumbency. Rather than or in addition to filtering by cedent location, in other embodiments, information may be filtered by type of cedent (e.g., local, regional, or global; small, medium, or large; etc.). In other

implementations, controls for filtering by geography, view, and/or incumbency are included in the dashboard 130. Further, in other embodiments, information may be filtered to identify where the participant is "leading" the market as opposed to where the participant is

"following" the market. In yet another example, information may be filtered by type of market.

[00117] Returning to FIG. 1C, the "premium flow analysis" pane 160 presents the reinsurance industry participant with navigational controls 172 configured to provide access to analytics demonstrating the flow of premium between a geographic location where business originated to a geographic region the business is placed from or a geographic region the business is underwritten from. Additionally, navigational controls 174 are configured to provide access to analytics demonstrating the contribution of premium on a geographic location basis, presenting information regarding business origination location, broked location, and/or underwriting location. In some examples, screenshot 2600 of FIG. 26A and screenshot 2620 of FIG. 26B illustrate map-based premium flow displays for presenting premium flow analytics to a reinsurance industry participant.

[00118] Turning to FIG. 26A, the screenshot 2600 illustrates a map demonstrating premium flow from an originating region 2602 (Oceana) to reinsurance industry participant hubs 2604 (Asia Pacific 2604a, Europe 2604b, United Kingdom 2604c, Bermuda 2604d, North America 2604e, and Other 2604f). Location 2602 includes a pie graph illustrating marketplace outflow premium 2606b as well as participant premium outflow contribution 2606a. Each location 2604 is represented with a pie graph illustrating marketplace in flow premium 2608a as well as participant in flow premium contribution 2608b. In other embodiments, statistical data may be presented in the screenshot 2600, for example upon selection of one of the pie graphs associated with locations 2602 and/or 2604. In some examples, statistical data can include GWP pool, percentage GWP share by the reinsurance industry participant, and percentage GWP share by the average peer. The information presented within the screenshot 2600 may be accessed, for example, using a "premium flow by underwriting region" control 172c of FIG. 1C. The reinsurance industry participant may choose to filter the information presented within the screenshot 2600 using one or more of a series of drop-down menus 2610. The drop-down menus 2610 include a "market flow" menu 2610a, a "from location" menu 2610b, a "line of business" menu 2610d, and a "product" menu 2610c. Using the "market flow" menu 2610a, for example, the industry participant may choose to switch from underwriting location to originating location or broked location, for example as accessible by a "premium flow by broked region" control 172b of FIG. 1C or a "premium flow by originating region" control 172c of FIG. 1C.

[00119] Referring to FIG. 26B, a screenshot 2620 illustrates a map demonstrating premium contra flow into reinsurance industry participant location United Kingdom 2622 from cedent locations 2624 (e.g., for example as accessible by a "contribution by underwriting region" control 174c. Location 2622 includes a pie graph illustrating marketplace inflow premium 2608a as well as industry participant premium inflow contribution 2608b. Each location 2624 is represented with a pie graph illustrating marketplace out flow premium 2606a as well as industry participant out flow premium contribution 2606b. In other embodiments, statistical data may be presented in the screenshot 2620, for example upon selection of one of the pie graphs associated with locations 2622 and/or 2624. As with the screenshot 2600, the dropdown menus 2610 provide the industry participant with filtering opportunities. For example, the industry participant may choose to switch from cedent location to originating location or broked location, for example as accessible by a "contribution by broked region" control 174b of FIG. 1C or a "contribution by originating region" control 174c of FIG. 1C.

[00120] Upon selection of the research & analytics tab 114c of FIG. 1C, the reinsurance industry participant is presented with a dashboard view presented in FIG. ID. Turning to FIG. ID, a "trade analysis" pane 174 includes navigational controls 182 selectable to access trading flow performance analytics of a reinsurance industry participant's requested line and signed line. The trading flow performance analytics may be presented on a per-business line basis, and changes in trading flow may be tracked across a period of time, such as quarterly, annually, bi-annually, etc. The trading flow performance of the reinsurance industry participant may be compared to performance of a peer group and/or overall market averages. In a particular example, turning to FIG. 25C, a screenshot 2530 presents a trading flow analysis comparing requested line performance of a reinsurance industry participant 2532a to a peer group 2532b as well as to market averages 2532c over a period of four quarters. The screenshot 2530, for example, may be presented to the reinsurance industry participant upon selection of a "percentage change by phase" control 182a of FIG. ID. Phase, for example, may refer to requested line and/or signed line. In some embodiments, the information presented within the screenshot 2660 is directed towards a particular country. The selection of the requested phase in the screenshot 2530 is represented by a selection made in a "phase" drop-down menu 2534a. The data presented in the screenshot 2530 is further filtered through a "view" drop-down menu 2534e, presenting trading flow data from the viewpoint of cedent location (e.g., versus broked location or underwriter location). Selection of view, for example, may be made using a "percentage change by view" control 182b of FIG. ID. The reinsurance industry participant is presented with additional filtering options via a "line of business" drop-down menu 2534b (e.g., correlating to a "percentage change by business line" control 182c of FIG. ID), a "product" drop-down menu 2534c (e.g., correlating to a

"percentage change by product" control 182d of FIG. ID), a "region in country" drop-down menu 2534d (e.g., correlating to a "percentage change by product" control 182d of FIG. ID), and an "incumbency" drop-down menu 2324f (e.g., correlating to a "percentage change by incumbency" control 182f of FIG. ID). A table 2536 presents percentage values for each of the participant 2532a statistic, average peer 2532b statistic, and market average 2532c statistic for each quarter of the presented period of time, as well as average values 2538 for the entire time period for each of the participant 2532a, the average peer 2532b, and the market average 2532c.

[00121] FIG. ID also includes a "customer feedback analysis" pane 176 with navigational controls 184 configured to present the reinsurance industry participant with information regarding customer feedback collected, for example, via the dashboard environment. The customer feedback, as illustrated in a screenshot 2570 of FIG. 25E, may be combined to determine an overall feedback score such as a Net Promoter® Score (NPS) by Satmetrix Systems, Inc. of San Mateo, CA. Additionally, as illustrated in a screenshot 2580 of FIG. 25F, the reinsurance industry participant may be provided access to analysis of individual attributes contributing to an overall customer feedback score. Collection and calculation of customer feedback metrics are described in greater detail below in relation to FIG. 20A.

[00122] Upon selection of a "feedback score" control 184a, the reinsurance industry participant may be presented with the screenshot 2570, illustrating a bar graph that compares a participant 2572 customer feedback score with averages for a selection of eight anonymized peers 2572 collected over a same period of time (e.g., calendar years 2012 and 2013 as illustrated in the screenshot 2570). Commentary may be presented (e.g., beneath the graph, as a pop-up upon selection of the participant 2572a data, etc.) presenting individual feedback provided by one or more reinsurance intermediate participants that have done business with the reinsurance industry participant. The data presented in the screenshot 2570 can be filtered through a series of drop-down menus 2576. For example, a "line of business" menu 2576 may map to a "feedback by business line" control 184c of FIG. ID, while a "product" menu (not illustrated) maps to a "feedback by product" control 184d of FIG. ID, a "role" menu (not illustrated) (e.g., broker, claims, client management, etc.) maps to a "feedback by role" control 184e of FIG. ID, and a "years of experience" menu 2576e (not illustrated) maps to a "feedback by experience" control 184f of FIG. ID. A "category" menu 2576a, currently set to PS, may be switched to "attribute score", thereby causing presentation of the screenshot 2580 of FIG. 25F. Similarly, selection of a "feedback attributes" control 184b of FIG. ID may cause presentation of the screenshot 2580 of FIG. 25F.

[00123] Turning to FIG. 25F, the screenshot 2580 includes a set of radar charts 2582 illustrating comparisons of values of a set of attributes 2584, arranged from a least important attribute 2586a to a most important attribute 2586b. The importance of each attribute 2584, for example, may be determined by a ranking made by the customers during the feedback process. Alternatively, the importance of each attribute 2584 may be selected by the reinsurance industry participant, established by a third party (such as the NPS® provider), or determined by the dashboard system (e.g., through a survey of select participants, analysis of total NPS® score in relation to individual attribute components, etc.). Each attribute 2584 is represented by a brief descriptive label. In some embodiments, full definitions of each attribute 2584 are available to the reinsurance industry participant via the screenshot 2580 (not illustrated). For example, attribute definitions may be presented upon selection of one of the attributes 2584 or beneath the radar charts 2582.

[00124] In a first radar chart 2582a, participant attribute values collected from two separate time periods 2588 (e.g., year 2013 and year 2012) are displayed together to illustrate positive and negative movement in each attribute 2584 between the two consecutive time periods 2588. In a second radar chart 2582b, participant 2590a attribute values collected during a most recent time period (e.g., year 2013) are displayed with average peer 2590b attribute values and market average 2590c attribute values collected during the same time period. In review, a reinsurance industry participant can quickly identify strengths and weaknesses regarding the various feedback attributes 2584.

[00125] As illustrated in FIG. ID, a premium share analysis pane 178 provides the reinsurance industry participant with a set of navigational controls 186 configured to access a detailed breakdown of the reinsurance industry participant's competitive position by line of business against peers. The information, for example, may include a presentation similar to a screenshot 2500 of FIG. 25 A. For example, upon selection of a "share by premium" control 186a, the reinsurance dashboard 130 may present the reinsurance industry participant with a display similar to the screenshot 2500 of FIG. 25 A.

[00126] Turning to FIG. 25 A, the premium share 2504 by line of business 2510 of a marketplace broked premium 2502 is charted in a bar graph. The bar graph is overlaid by two line graphs, the first illustrating a reinsurance industry participant share 2506 by line of business, and the second illustrating an average peer share 2508 by line of business. Review of the bar graph allows the reinsurance industry participant to track its position within the marketplace relative to the average peer share.

[00127] Additionally, beneath the bar graph, a table lists specific statistical values related to premium share for each of the marketplace 2504, the participant 2506, and the average peer share 2508 as well as totals 2515 related to each particular value (2512a, 2512b, 2514a, 2514b, and 2508). Statistics 2512 associated with the marketplace include total premium 2512a per line of business 2510 as well as percentage of book 2512b per line of business 2510. Statistics 2514 associated with the participant 2506 include GWP 2514a per line of business 2510, market share 2514b per line of business 2510, and rank 2514c per line of business 2510. In some embodiments, the information presented within the screenshot 2500 is directed towards a particular country.

[00128] The reinsurance industry participant may filter the illustrated statistics using a series of drop-down menus 2501. For example, rather than reviewing an analysis of premium value in dollars, a "category" menu 2501a provides the option of reviewing the statistical analysis on the basis of policy count (e.g., similar to a "share by policy count" control 186b of FIG. ID). Other filters include a "region in country" menu 2501b (e.g., similar to a "share by geography" control 186c of FIG. ID), a "view" menu 2501c (e.g., similar to a "share by view" control 186d of FIG. ID), a "product" menu 250 Id (e.g., similar to a "share by product" control 186e of FIG. ID), and a "cedent type" menu 250 le (e.g., similar to a "share by cedent type" control 186f of FIG. ID). Additional filters include a "reinsurer capital" menu 2501f providing selection of premium by band (e.g., similar to a "share by premium by band" control 186g of FIG. ID) and a "security rating" menu 2501g providing selection of premium by rating (e.g., similar to a "share by security rating" control 186h of FIG. ID).

[00129] Returning to FIG. ID, a "strategic and tactical impact analysis of premium share" control 186i, upon selection, generates an analysis of premium share in comparison to average (baseline) results within the marketplace to identify both a contribution caused by strategic reasons (e.g., the participant writes a larger or smaller share of lines with high or low profits) and by tactical reasons (e.g., the participant is better or worse at selecting individual cedents). The analysis obtained through the "strategic and tactical impact analysis of premium share" control 186i, for example, allows the participant to review performance measures based upon the participant's actual business balance. The "strategic and tactical impact analysis of premium share" control 186i works to present performance measures based upon actual business line balance such as, in an analogous situation, a stock portfolio may be reviewed based upon a risk-aligned analysis of the portfolio to determine how well a stock broker is doing in selecting individual stocks within a particular risk segment.

[00130] Turning to FIG. 27, a flow chart illustrates an example method 2700 for determining strategic and tactical impact components of a participant's performance results, such as premium share metrics, cross sales metrics, trade metrics, and profitability metrics (e.g., based upon loss ratios, ceding commission ratios, brokerage ratios, and/or expense ratios) for a given reinsurance participant. The method 2700, for example, may be used to present an analysis of strategic and tactical impacts on performance metrics in response to selection of the "strategic and tactical impact analysis of premium share" control 186i of FIG. ID and/or a "strategic and tactical impact analysis of GWP" control 188g of FIG. ID.

[00131] In some implementations, the method 2700 begins with determining a basic portfolio composition of a requesting participant (2702). The composition, for example, may be composed of fundamental building blocks such as, in some examples, cedent location(s), line(s) of business, and/or product type(s). A software algorithm may analyze the

participant's book of business to identify a portfolio composition. In another example, a user may be presented with an interactive graphical user interface selection process for identifying portfolio composition. For example, the user may select to filter information to focus on a particular geographic region, business line, product type, or product category.

[00132] In some implementations, results for a total book average portfolio of the marketplace are calculated by cell (2704). Each cell, for example, may represent a particular combination of fundamental building blocks (e.g., location "North America," product, "Treaty Pro Rata," line of business "professional liability," or a combination of two or more elements). If the participant chose to filter the information, the total book average portfolio results may similarly be filtered to the target viewpoint. The resultant information may be referred to as Marketplacex ₀ tai- The Marketplacexotai data reflects the average composition of the books of business of reinsurance participants of the dashboard environment.

[00133] In some implementations, results for a book average portfolio of the participant are calculated by cell (2706). Data correlating to the results described above in relation to the total book average portfolio of the dashboard environment may be calculated pertaining to the portfolio composition of the participant. The resultant information may be referred to as Subscribers Results / s Mix- The information Subscribers Results / s Mix reflects a composition (mix) of the book of business of the participant with metrics reflecting results achieved by the participant.

[00134] In some implementations, potential results representing the participant book portfolio composition and marketplace averages for that composition are calculated (2708). Data corresponding to the marketplace averages are combined in the composition (mix) of the participant portfolio to obtain metrics demonstrating potential (marketplace) results, referred to as Subscriber _M Results / s Mix- The information Subscriber _M Results / s Mix reflects average marketplace performance, taking into account the participant's portfolio

composition.

[00135] In some implementations, a participant portfolio result relative to the marketplace portfolio results is calculated (2710). The difference, for example, between marketplace average performance and participant portfolio performance may be calculated by subtracting the information Marketplacexotai from the information Subscribers Results / s Mix to obtain a relative result R (e.g., R = Subscribers Results / s Mix - Marketplace _Tot ai).

[00136] In some implementations, a strategic decision impact component of the participant's achieved results is calculated (2712). The strategic impact component, for example, may be determined by calculating the difference of the marketplace average based upon marketplace average portfolio information and the marketplace average calculated using the particular portfolio composition of the participant. In a particular example, the strategic decision component S is calculated as follows: S = Subscriber _M Results / s Mix - Marketplacex ₀ tai- This value represents the relative performance of the participant's portfolio balance to the performance of the marketplace as a whole, based entirely on performance averages of the marketplace. In reviewing this information, the participant may review the impact of the participant's basic portfolio composition decisions on performance without focusing on particular performance based upon the participant's particular book of business.

[00137] In some implementations, a tactical decision impact component of the participant's achieved results is calculated (2714). The tactical decision component, for example, may be determine by calculating the difference of the participant's result metrics and marketplace averages based upon the portfolio balance of the participant. In a particular example, the tactical decision component T is calculated as follows: T = Subscribers Results / s Mix - Subscriber _M Results / s Mix- The participant may review the tactical decision component to determine how well line underwriters are performing in selecting individual cedents for building the participant's book of business.

[00138] In some implementations, a graphical user interface illustrating comparison information regarding strategic and tactical impact components of participant total results is prepared for presentation upon a participant computing device (2716). The graphical user interface, for example, may illustrate, using graphs, charts, tables, and/or other visual representations, relative performance aspects of the participant's portfolio based upon a decomposition of performance into strategic and tactical components. Further, the graphical user interface may include detailed information corresponding to performance analysis based upon separate portfolio components (fundamental blocks) of the overall portfolio

composition. The user may be provided an opportunity, for example, to filter information to focus upon one or more components of the overall portfolio.

[00139] Although described in relation to a reinsurance participant, in other

implementations, an insurance participant or other industry participant may review

decomposition of strategic and tactical components of various performance metrics based upon the impact of the fundamental building blocks of the participant's book of business. Further, in some implementations, a participant may be provided the opportunity to historically analyze a potential portfolio composition, for example by selecting a balance of fundamental building blocks to define a portfolio composition. In analyzing historic performance, in some embodiments, the participant is presented with timeframe options (e.g., past year, past three years, past five years, etc.). The timeframe options may differ by type of participant. For example, monthly changes are more appropriate to insurance industry participants than to reinsurance industry participants.

[00140] Referring to FIG. ID, a "cross sale analysis" pane 180 presents navigational controls 188 configured to provide the reinsurance industry participant with access to analysis of the reinsurance industry participant's penetration of the entire book of business. The information provided via the navigational controls 188 may help the reinsurance industry participant to identify the potential for additional premium within its risk appetite (e.g., line of business and/or product) by providing data regarding potential new clients as well as data regarding existing participant entities. Further, a "strategic and tactical impact analysis of GWP" control 188g, when selected, may present the reinsurance industry participant with a decomposition of cross sale results based upon strategic decision components and tactical impact components, as discussed above in relation to FIG. 27. The data, for example, may be presented in a similar manner to a screenshot 2640 of FIG. 26C. [00141] Turning to FIG. 26C, a bar graph presents information regarding reinsurance industry participant GWP 2650a and cross sale GWP opportunity 2650b (e.g., such as the GWP of the industry participant's existing clients accessible via a "GWP of existing clients" control 188d of FIG. ID and GWP of potential new clients accessible via a "GWP of potential clients" control 188a of FIG. ID). In a first bar of the bar graph, a participant premium 2646a represents actual premium for the participant (e.g., total premium for all broking locations 2648a, all cedent locations 2648b, all products 2648c, and all lines of business 2648d). The data regarding opportunity is broken down, within the bar graph, by 100% premium by category, where the categories include premium on the layers with participant participation 2646b, premium on the contracts with participant participation 2646c (e.g., contracts having one or more layers), and premium on entities with participant participation 2646d (e.g., entities having one or more contracts). Additionally, a marketplace total premium 2646e is presented in comparison.

[00142] In some implementations, upon selection of a particular bar 2646 of the bar graph of screenshot 2640, the participant can drill down into specific account information, for example to identify particular opportunities. A similar concept, for example, has been described in relation to pipeline opportunities of FIGS. 21 A through 21D, below.

[00143] In some examples, when identifying opportunities, potential new clients may be entity participants of the dashboard environment, entities external to the dashboard environment, and/or potential clients identified by the reinsurance industry participant.

Potential clients, in some examples, may be identified by the dashboard system based upon the potential clients' line of business and/or products relevant to the potential clients. Using the graph presented in the screenshot 2640, a reinsurance industry participant can understand opportunities on contracts and entities representing existing relationships that are defined at different levels (e.g., by broking location, cedent location, etc.).

[00144] The reinsurance industry participant may analyze potential clients by line of business using a line of business drop-down menu 2648d (e.g., accessible via a "GWP of clients by line of business" control 188b of FIG. ID). Additionally or alternatively, the reinsurance industry participant may be able to identify potential for additional premium falling within its risk appetite by analyzing potential clients by product through a product drop-down menu 2648c (accessible via a "GWP of clients by product" control 188e of FIG. ID). In some embodiments, the information presented within the screenshot 2640 is directed towards a particular country. The data provided within the screenshot 2640 may be filtered by geography using a "broking location" drop-down menu 2648a, a "cedent location" drop- down menu 2648b, or a "GWP of clients by geography" control 188c of FIG. ID. The data provided within the screenshot 2640 may also be filtered by view using a "view" drop-down menu (not illustrated) or a "GWP of clients by view" control 188f of FIG. ID.

[00145] FIG. 24 illustrates the example screenshot 2400 presenting high level summary information regarding competitive performance of a reinsurance industry participant within a global market. The screenshot 2400 includes a "premium by line" section 2402, a "global distribution of risk" section 2404, and "Premium by Product Split" section 2406, and a "net promoter score summary" section 2408. The information displayed in each of the sections 2402, 2404, 2406, and 2408 may optionally be filtered, in some examples, by line of business, geographic region, and/or product (not illustrated).

[00146] In the "premium by line" section 2402, statistical information regarding annual premiums for particular lines of business are shown for both the present participant (Acme Reinsurance Co.) and for the marketplace as a whole. In other embodiments, peer comparisons may be illustrated within the "premium by line" section 2402. The peers, in some examples, may be limited to reinsurance industry participants that, for example, are active in the presented lines of business. The peers may be limited to other reinsurance industry participants participating within the dashboard environment. Conversely, at least a portion of the peers may include reinsurance industry participants active outside the dashboard environment. When identifying a subscribing reinsurance industry participant as a peer of the present reinsurance industry participant, in some examples, the dashboard environment may compare reinsurance industry participant demographic and/or business information to identify comparable reinsurance industry participants. For example, peer reinsurance industry participants may include the closest 20 reinsurance industry participants to a GWP of the present reinsurance industry participant, reinsurance industry participants active in similar geographic locations as the present reinsurance industry participant, and/or reinsurance industry participants active in similar lines of business as the present reinsurance industry participant. In other embodiments, peers may be individually identified by industry participant Acme Reinsurance Co., for example through a search and/or selection graphical user interface.

[00147] Turning to the "global distribution of risk" section 2404, premium distribution is broken down by cedent location, identifying, for each geographic location presented on a map illustration, the marketplace GWP as well as the reinsurance industry participant's percentage share. The shares are noted both in numerical format and in pie chart format. In other embodiments, the "global distribution of risk" section 2404 may further illustrate the average peer competitor's percentage share.

[00148] The "premium by product split" section 2406 presents a graphical illustration of relative product share by industry participant "Acme Reinsurance Co.". As illustrated, catastrophe holds the greatest share, and facultative the smallest share, with excess of loss (270L) and pro rata holding similar shares (totaling approximately 10% each). In other implementations, the percentages and/or total premiums associated with each product segment may also/alternatively be illustrated.

[00149] The "net promoter score summary" section 2408 presents a comparison between reinsurance industry participant PS data, average peer PS data for eight peers of Acme Reinsurance Co., and a market average NPS for the marketplace. Further detail regarding NPS statistics is provided in relation to FIG. 25E.

[00150] FIGS. IE and IF illustrate an industry participant dashboard user interface 190 for reviewing and analyzing transaction information. The dashboard 190 is part of a web site, web portal, personal computer application, or mobile device application configured to allow the industry participant to interface with the dashboard system and dashboard environment. The dashboard 190 includes the same tabs 114 as illustrated in FIGS. 1 A and IB in relation to intermediate participant dashboard interfaces, but each of the tabs 114 now present information relevant to industry participants. As shown in FIG. IE, the "benchmarking" tab 114a of the dashboard 190 is active.

[00151] Turning to FIG. IE, a "reports" pane 192 includes a series of navigational controls 196 configured, upon selection, to provide an industry participant with report-style information. The reports, in some embodiments, are customizable by the user, such that individual metrics, geographical regions, products, and other business aspects important to the particular industry participant are highlighted. Report preparation, in a general sense, may be similar in method to the steps described in relation to method 200 as described in relation to FIG. 2.

[00152] A "pipeline reports" control 196a, upon selection, may present the industry participant with a report-style review of transaction opportunities for the industry participant as forecast over an upcoming period of time (e.g., over an upcoming quarter, six months, etc.). Generally, a pipeline opportunity represents one or more of an expiring policy that may be up for renewal, a new policy interest, and/or an opportunity for early renewal or restructuring of a policy that is not otherwise expiring in the near future. The pipeline opportunities may be filtered by product, industry, and/or geographical region. The pipeline opportunities may also be filtered by industry participant appetite, incumbency, and/or cross sale opportunities. In one example, the "pipeline reports" control 162a, upon selection, may cause the presentation of display aspects similar to those illustrated in FIGS. 21 A through 2 ID (described in further detail below). In the event of an interactive report style (e.g., rendered online or through a computer-based interface linking different display features), aspects of the pipeline report may be accessible within other aspects of the pipeline reports. For example, an industry participant may be provided the opportunity to "drill down" into more detailed analysis of pipeline opportunities, for example down to a detailed report 2120 illustrated in FIG. 2 IB. Further, in some embodiments, a pipeline report provides the industry participant with an indication of interest in opportunities registered by intermediate participants. In this manner, the industry participant may be alerted to opportunities in which intermediate participants have an active interest. The interest tracking feature is described in greater detail below in relation to FIGS. 21C and 21D.

[00153] The "reports" pane 192 also includes a "feedback reports" control 196b, selectable to access a report-style review of customer feedback data collected, for example, via the dashboard environment. The report may present feedback metrics related to the present industry participant in comparison to feedback metrics related to peer competitors. Example report components are illustrated in FIGS. 20 A and 20B, described in greater detail below. The customer feedback, as illustrated in a screenshot 2000 of FIG. 20A, may be combined to determine an overall feedback score such as a Net Promoter® Score (NPS). Feedback metrics may also be calculated for each stage of the lifecycle of the broking process, such as underwriting, post-placement, claims and overall relationship attributes. FIG. 20B illustrates a screenshot 2020 including a bar graph style comparison between performance of the present industry participant during the underwriting stage of the broking process and performance of select peer competitors during the underwriting stage. Additionally, as illustrated in a screenshot 2580 of FIG. 25F in relation to reinsurance feedback, in some embodiments the industry participant may be provided access to analysis of individual attributes contributing to an overall customer feedback score.

[00154] A "carrier reports" control 196c of the "reports" pane 192, when selected, may present the industry participant with a report-style review of present market and/or benchmarking analytics, for example combining information accessible through one or more of a "flow rate analysis" pane 194, a "premium share" pane 101 of FIG. IF, an "interest tracker" pane 103 of FIG. IF, a "declination analysis" pane 107, and a "loss analysis" pane 109 of FIG. IF. [00155] Turning to the flow rate analysis pane 194, a set of navigational controls 198 provides access to a set of analytics referred to as "flow trading," including submission flow, hit rate, quote rate, and conversion rate. The set of analytics, for example, are illustrated in FIG. 17, described in further detail below. The "flow trading" benchmarking analytics are compared to peer competitors to review performance of the industry participant within the marketplace. Furthermore, a set of filtering navigational controls 199 are available to the industry participant to filter the "flow trading" analytics by product (using a "flow trading by product" control 199a), geography (using a "flow trading by geography" control 199b), industry (using a "flow trading by industry" control 199c), and/or capacity (using a "flow trading by capacity" control 199d). Other possible filtering options include industry participant appetite, incumbency, and industry participant division, as discussed below in relation to FIG. 16 A.

[00156] Upon selection by the industry participant, a "submission flow v. peers" control 198a may cause presentation of a screenshot 1600 of FIG. 16A in the industry participant dashboard 190. Within the screenshot 1600, submission flow metrics of the industry participant are compared to submission flow metrics of the average of top peers as well as the metrics of five individual peers (labeled A through E). In some embodiments, the period of time presented in the screenshot 1600 is user configurable. A "phase" drop-down menu 1602 is available to switch to different trade flowing analytics, similar to use of a "hit rate v. peers" control 1998b, a "quote rate v. peers" control 198c, and a "conversion rate v. peers" control 198d of FIG. IE. Furthermore, upon selection of a product using a "product/segment" dropdown menu 1602b (or selection of the "flow trading by product" control 199a), a screenshot 1650 of FIG. 16B may be presented to the industry participant.

[00157] Rather than displaying the "flow trading" metrics individually, in some

implementations, aggregate flow rates may be presented within a same display. Turning to FIG. 17, a "submission rate" bar graph 1702, a "quote rate" bar graph 1704, a "hit rate" bar graph 1706, and a "conversion rate" bar graph 1708 are presented within a single screenshot 1700.

[00158] Turning to FIG. IF, the "research and analytics" tab 114c of the industry participant dashboard 190 presents the industry participant with the "premium share" pane 101 including navigational controls 111 configured, upon selection, to present analytics regarding premium share. The premium share analytics provide the industry participant a general overview of its place in the overall market and the concentration of its business by segment. An example premium share display is presented in a screenshot 2200 of FIG. 22A, described in greater detail below. The screenshot 2200, for example, may be presented to the industry participant upon selection of an "aggregate premium" control 111a. Further, the premium share analytics may be filtered by one or more of category (using a "premium by category" control 11 lb), geographical region (using a "premium by geography" control 111c), view (using a "premium by view" control 11 Id), product (using a "premium by product" control 11 le), and/or industry (using a "premium by industry" control 11 le).

[00159] To receive greater insight into historic trends of premium share metrics, for example based upon trends within particular entity participants or particular underwriters, in some embodiments, a row of the screenshot 2200 may be selected to cause presentation of a detailed premium share analysis, for example as illustrated in a screenshot 2220 of FIG. 22B. Turning to FIG. 22B, detailed premium share analysis includes information such as a policy effective date, policy expiration date, underwriter name, entity name, entity description, and aggregate premium amount.

[00160] Portions of aggregate premium data, either at the more abstract level presented in FIG. 22A or on a refined level as presented in FIG. 22B, may be shared with other participants of the dashboard environment (e.g., to contribute to peer metrics of competitors). Sharing, in some embodiments, is enabled through an anonymizing feature of the dashboard system, such that other participants cannot recognize data points as belonging to a particular participant. Access to greater levels of data granularity and/or greater refinement of peer comparison metrics, in some embodiments, may be based upon participant level. For example, a particular participant may pay an additional fee for access to enhanced data granularity and/or peer comparison tools.

[00161] Turning to FIG. IF, instead of or in addition to the premium share pane 101, a "premium change velocity analysis" pane 121 includes a set of navigational controls 121 for accessing metrics regarding percentage fluctuations in premium. The navigational controls 121, for example, may each be selectable to present a particular velocity change graphic interface. A user may review the velocity change graphic interfaces via the navigational controls 121 to identify areas of rapid growth (e.g., indicating a potential need for additional resources) as well as rapid decline (e.g., indicating a potential need for improvement efforts). Velocity change graphic interfaces are described in greater detail below in relation to FIGS. 34A through 34C. Upon selection of an "industry change velocity" control 121a, for example, the user may be presented with a graphic analysis of percentage movements in remittance values of entity participants classified within certain industries over a period of time, such as the industry velocity change interface 3400 of FIG. 34A. The user may select a "product change velocity" control 121b, in another example, to review a graphic analysis of percentage movements in remittance values related to transactions involving various types of products, such as the product velocity change interface 3410 of FIG. 34B. In a further example, the user may select a "client size change velocity" control 121c to review a graphic analysis of percentage movements in remittance values based upon aggregate annual remittance value ranges, where entity participants engaged in transactions with the present participant are classified within a particular remittance value range based upon aggregate annual remittance value. An example client size change velocity graphic analysis is presented in FIG. 34C. The user may choose to select a "broking center change velocity" control 12 Id, in a final example, to review a graphic analysis of percentage movements in remittance values based upon individual broking centers involved in placing transactions with the present participant. Other premium change velocity analysis controls 121 are possible, as discussed below in relation to FIGS. 34A through 34C.

[00162] Returning to FIG. IF, the "interest tracker" pane 103 includes a series of

navigational controls 1 13 for accessing opportunities associated with intermediate participant interest requests. As discussed above in relation to the pipeline reports control 196a, the interest tracking feature connects interested intermediate participants with available industry participants for fulfilling new opportunities. Rather than accessing the opportunities via the pipeline reports control 196a of FIG. IE, the industry participant may select one of the navigational controls 113 to quickly review interest tracker submissions by product (using a "requests by product" control 113a), by entity industry (using a "requests by client industry" control 113b), by deal size (using a "requests by deal size" control 113c), by status (using a "requests by status" control 113d), by category (using a "requests by category" control 113e), and/or by geographical region (using a "requests by geography" control 113f). Selection of one of the navigational controls 113, for example, may present the industry participant with a view similar to the screenshot 2160 of FIG. 21D.

[00163] Turning to the "declination analysis" pane 107, a set of navigational controls 115 provides the industry participant with the ability to review either industry participant declination reasons (using a "carrier declinations" control 115a) or entity/intermediate participant declination reasons (using a "client declinations" control 115b). Industry participant declination metrics are discussed in greater detail below, in relation to FIGS. 19A through 19D. For example, selection of the "carrier declinations" control 115a may cause presentation of a screenshot 1900 of FIG. 19A within the industry participant dashboard 190. Further, the industry participant declination metrics may be filtered using one or more filtering navigational controls 117. For example, upon selection of a "declinations by product" control 117e, the industry participant may be presented with a screenshot 1910 of FIG. 19B. Similarly, selection of both the "client declinations" control 115b and the

"declinations by product" control 117e may result in review of a screenshot 1920 of FIG. 19C. Other filters available via the declination analysis pane 107 include a "declinations by carrier appetite" control 117a, a "declinations by carrier division" control 117b, a

"declinations by industry" control 117c, a "declinations by incumbency" control 117d, and a "declinations by deal size" control 117f. Filtering options are discussed in greater detail below in relation to FIGS. 19A through 19C.

[00164] As shown in the "loss analysis" pane 109, an industry participant may review losses incurred through individual accounts through a series of navigational controls 119. Upon selection of a "losses" control 119a, for example, the industry participant may be presented with a display similar to a screenshot 1800 of FIG. 18A and/or a screenshot 1820 of FIG. 18B. Turning to FIG. 18A, the screenshot 1800 presents a table of records regarding industry participants incurring losses in relation to premiums. Each record presents an industry participant name 1804, net premiums amount 1806, claims amount 1808, reserves amount 1810, loss ratio paid 1812, and loss ratio incurred 1814. In some embodiments, a

benchmarking component may be available, including a comparison of industry participant loss metrics (e.g., loss ratio paid, loss ratio incurred) of the present industry participant (subscriber 1816) and loss metrics of peer competitors 1818. In some embodiments, selection of a particular field of the table in the screenshot 1800 activates presentation of a detailed view of record information.

[00165] As illustrated along the top of the screenshot 1800, a series of drop-down menus 1802 are available for filtering presentation of loss metrics. A "country" menu 1802a presents options for selection of a geographic region, similar to a "loss by geography" control 119d of FIG. IF. A "year" menu 1802b enables the industry participant to review loss data by calendar year. In other embodiments, the industry participant may be presented the opportunity to select a date range (e.g., month, quarter, or customized span of dates, etc.). A "product" menu 1802c enables the industry participant to review loss data by product line, similar to a "loss by product" control 119c of FIG. IF. An "industry" menu 1802d enables the industry participant to review loss data by entity industry, similar to a "loss by industry" control 119d of FIG. IF.

[00166] Further, the information may be illustrated in a graph presentation to identify trends in loss ratios over a period of time. Turning to FIG. 18B, a screenshot 1820 illustrates a loss ratio comparison graph 1822 of an average loss ratio 1824 and a participant loss ratio 1826 for a presented timeframe (e.g., years 2008 to 2011). The loss ratio comparison graph 1822 is illustrated next to a premium to market share comparison graph 1828, illustrating both a total premium 1830 for participant during a presented timeframe (e.g., years 2008 to 2011) as well as a market share 1832 for the participant during the timeframe.

[00167] FIG. 8 illustrates a process flow diagram or flow chart of a method, routine, or process 800 that may be used to generate subscription transaction statistics according to an embodiment. A block 802 may access information from a number of intermediate participant computing devices that are communicatively coupled to a network and retrieve selected transaction data from each of the number of computing devices. The transaction data may be inputted or captured by a number of intermediate participant users at a number of

intermediate participant computing devices remotely located from each other. Examples of intermediate participant computing devices and a network for connecting the intermediate participant computing devices are illustrated in FIGS. 28A-28D and are discussed further below. Block 802 may also store or archive the accessed information to an easily accessible data storage medium or device, such as a server, for further processing. The server may be one of a number of intermediate participant computing devices communicatively coupled to the network. The block 802 may aggregate data values for particular selected parameters across all the data collected (e.g., across the number of intermediate participant computing devices). A block 804 may generate a set of subscription transaction statistics (or simply insurance transaction statistics) based on the accessed transaction data of block 802. The generation process of block 804 may involve or include an analysis or calculation of values based on the aggregated data of block 802. A block 806 may generate a display of one or more of the set of subscription transaction statistics for display on a display device, such as an intermediate participant computing device. Block 806 may involve or include generating a display arrangement of a set of subscription statistics. Generally, the display arrangement may include the set of subscription statistics and a layout of the set of subscription statistics. The layout may include display positions for each of the set of subscription statistics or relational data to indicate how each of the set of subscription statistics should be positioned relative to one another. The display arrangement may be generated based on a set of intermediate participant parameters that are inputted into a computing system implementing the process of FIG. 8. The intermediate participant parameters may be based on a particular workflow designed by the intermediate participant company. In one embodiment, the intermediate participant parameters may be based on an aggregate study of client relationships. The study may produce general or average client interaction schedules. For example, a client interaction schedule may include specific events associated with clients such as client sales pitching, creation of subscription structure, managing renewals, etc. along with a chronological sequence for the events and sub-events within the events. Each element of the client interaction schedule may be used to define the set of intermediate participant parameters, where the intermediate participant parameters may be used to generate one or both of the set of policy transaction statistics of the block 804 or the display arrangement of transaction statistics of the block 806.

[00168] In some embodiments, the system may be used to selectively provide access to the transaction statistics and/or display arrangements of the one or more sets of insurance statistics (block 808). This may involve any authentication or authorization needed to determine a user's level of participation (e.g., paid subscription) with the dashboard environment. The system may also include transmission of the display arrangement (e.g., an image of the display arrangement or instructions for displaying the arrangement) (block 808).

[00169] The data aggregation (block 802) from a number of intermediate participant computing devices may involve a timed collection of selected data from each intermediate participant computing device to a central data store or database. The aggregation may be performed in response to an ad hoc request for one or more subscription transaction statistics. In particular, an ad hoc request to generate a subscription transaction statistic may be distinguished from statistics that are generated by a periodic reporting function, which may be initiated at fixed intervals (e.g., at the end of financial reporting periods). Further, the aggregation may be performed such that the generated subscription transaction statistic is based on transaction data that is available (e.g., inputted into one or more intermediate participant computing devices connected to the network) contemporaneously during a period of the request. In some embodiments, block 802 may be implemented by aggregating transaction data that is released, stored, or otherwise made available in response to the request. In this manner the aggregation may be called "real time" aggregation as the subscription transaction statistic is based on any data inputted into the system during the time of the request. Real time aggregation may be distinguished from archival aggregation of transaction data which may occur or may be performed only at fixed intervals (e.g., reporting periods). For example, archival aggregation may occur in conjunction with the periodic reporting function, where the reporting function and aggregation occur at fixed periods. In aggregating for a periodic reporting function, data that may be inputted after a cutoff period may not be included in the aggregation and/or report generation. More particularly, archival aggregation may only aggregate transaction data that has been released on a fixed schedule and may not include transaction data entered contemporaneously with an ad hoc request for generating a statistic. In some embodiments, selection of data may occur at a server that acts on the central store or database after non-filtered data from the intermediate participant computing devices is accessed and transferred to the database. Generally, the data from the intermediate participant computers may be inputted primarily by intermediate participants during the transaction of each subscription or product trade, from inception to binding (or other result, such as no response or lack of response). The majority of information within the dashboard system described herein may be intermediate participant data and/or entity participant data. However, some data may be provided by industry participants such as information on policy quotes and reasons industry participants declined quotes.

[00170] Table 1 lists a set of parameters that may be collected from intermediate participant computers as part of a data aggregation process. The parameters may include at least subscription or product placement name, effective date/start date, expiration date, business unit, placement status, currency, office location, country, entity name, entity status, account type, entity ID, source system, Data Universal Numbering System (DUNS) number, ARS industry group, and primary Standard Industrial Classification (SIC) code. The list of parameters may describe a minimum list of transaction data required to produce a useful set of transaction statistics. FIG. 9 illustrates a screen adapted to receive the transaction data through a set of input fields.

TABLE 1

Insurance policy placement name

policy effective date/start date

policy expiration date

Business unit

placement status

Currency

office location

Country

client name

client status

account type

client ID

source system

DUNS number

ARS industry group

primary SIC code

Policy Premium

Client Declination Reasons

Carrier Rejection Reasons

[00171] Generally, the transaction data may be collected at three key points during the process of placing a subscription or purchasing a product: first, when an intermediate participant informs industry participants about an entity (e.g., entity participant or intermediate participant) policy opportunity (known as a "trade" or a "submission"); second, when the chosen industry participants provide a response to a policy proposal ("quote" or "decline"); and third, when the entity decides which industry participant option it wants to accept (a "hit", a "win" or a "bind"). Opinion data may be collected using responses to questionnaires. The information may be collected by intermediate participants and directly inputted by them into a database at the time of collection. A significant proportion of global premiums (corresponding to a large pool of transaction data from a number of countries) brokered may be captured in the system. Moreover, the policies may cover a broad range of entity industries and products.

[00172] In block 802 of FIG. 8, the parameter values for each policy generated or managed by an intermediate participant via the intermediate participant computing device may be aggregated over multiple levels of increasing group scope (such as inter-company defined divisions) and geographic area. The data may be aggregated first locally and then regionally, and finally companywide, which may be on an international scale. The data may then be indexed and organized as described below to provide unique views of the data for intermediate participants, regardless of which computer contributed the information for the view. A benefit of aggregating an overall data set over such a sample is that the larger the presence of an intermediate participant, the larger the accuracy of a data parameter. Even previously seldom used transaction statistics may become more useful because the data is now aggregated over a larger number of computers and consequently, over a larger number of data points.

[00173] The block 802 may also perform a data anonymizing process. Generally, anonymizing data may involve manipulating the data so that no individual pricing data or individual identity data can be retrieved from the data. All data available may be

retrospective. Prior to being made available from the computer system, the data may undergo a "cleansing" or anonymizing process to ensure that data made available meets established standards. One process for anonymizing the data may involve commingling newly released data with a data pool made up of significantly older data points, themselves anonymized and aggregated. This pooling process may be used to help prevent possible facilitation of any collusive practices, whether in theory or in practice, through the introduction of the data introduced quarterly.

[00174] The block 804 may generate subscription transaction statistics that include at least an aggregate remittance value of premiums for subscriptions brokered by the intermediate participant company. As discussed above, the subscription transaction statistic may be generated based on transaction data that is available in any one of the intermediate participant computing devices at the time of a request to generate the statistic. In some embodiments, the generation of the statistic may be continuous or ongoing. For example, as new data is being inputted into any one of the intermediate participant computing devices, the system may aggregate new inputs and update or regenerate a statistic. One subscription premium statistic may be generated by summing all collected policy premiums from the aggregated policy transaction data. It should be noted that calculations may be performed to determine specific aggregated premium values for different stages of policy transactions (e.g., for policies that are finalized or are at different stages of the transaction process). The block 804 may also anonymize any statistics generated so that no individual trade pricing or individual identity information can be extracted from the transaction statistics.

[00175] The system may display (block 806) the combinations of subscription statistics described herein on an intermediate participant computing device that did not contribute all the transaction data used to produce the statistic. In one embodiment, at least one

intermediate participant computing device may display the described transaction statistic combinations and arrangements where the intermediate participant computing device may not have contributed any transaction data during the aggregation process of block 802. As discussed above, it is important to foster communication of valuable data for assisting all intermediate participant members of an intermediate participant company to provide better customer service and to increase sales of subscriptions and/or products.

[00176] As discussed above, the system may generate (block 804) a number of different sets of transaction statistics (a set including one or more elements). These sets of transaction statistics may be generated based on the intermediate participant parameters and further combined and arranged in particular unique displays on an intermediate participant computing device.

[00177] A first set or combination of transaction statistics that may be generated include a set of aggregate remittance values (e.g., premiums) for a first period. The aggregate remittance values may be indexed or categorized by a region for the first period. The aggregate remittance values may be further indexed or categorized by industry and/or product for the first period. The first period may be a current period, which may be a current business or calendar quarter or annual period, or may be a user determined period. In some embodiments, an aggregate value may include a sum of all collected or accessed values for a selected parameter. The aggregate value may include a sum of all values collected when a request to aggregate and/or generate a statistic is received. In some embodiments, the aggregate value may be constantly calculated or updated as new information is being input into one or more of the intermediate participant computing devices that provides transaction data to the aggregation process. Thus, in one embodiment, the aggregate remittance values of the first set may be a summation of the total remittance values for each of a number of subscriptions and/or products collected by the described system.

[00178] Another transaction statistic that may be combined with the aggregate remittance values may be aggregate subscription or product trade counts that are indexed by the regions over the first period. Generally, a trade count may include submitted, quoted, bound, indication only, and/or response trades. The trade count may not, in some embodiments, include declined or rejected trades. In one embodiment, a display arrangement may be generated and displayed showing the trade counts with (e.g., adjacent to) corresponding aggregate remittance amounts. The combinations may be displayed, for example, with the corresponding aggregate remittance values by region when the aggregate remittance values are also displayed by region. FIG. 10 illustrates a display embodiment showing a set of aggregate remittance values mapped by geographic region with corresponding trade counts. For example, FIG. 10 illustrates that an Americas region has an aggregate insurance policy premium amount of 7,344 million dollars with a corresponding total trade count of 197,282 policies.

[00179] An additional transaction statistic that may be combined with the first set of transaction statistics may be a set of trade status parameters. FIG. 10 illustrates that a combination of trade statistics may include a set of trade status parameters. The set of trade status parameters may include an indication of the current aggregate amounts of subscriptions or products in a set of categories that include submitted transactions, bound transactions, entity participant rejected transactions, industry participant declined transactions, quoted transactions, and no response (or lack of response) transactions. This section may provide an intermediate participant an immediate understanding of the general state of an intermediate participant's company regionally and internationally.

[00180] Remittance values for subscriptions and/or products may be aggregated based on the industry participant for which the transactions were placed. Thus, for example, a particular industry participant may have a corresponding aggregate premium statistic that indicates an aggregate amount of insurance premiums that were placed with that industry participant (by the intermediate participant company) for the first period. Accordingly, a second set of insurance transaction statistics may include at least this set of aggregate remittance parameters that are categorized by industry participants.

[00181] FIG. 10 illustrates an exemplary display arrangement that maps aggregate remittance values for each of a set of industry participants. The set of industry participants may be a subset of a total set of industry participants for which transaction data exists. The subset of industry participants may be determined by a system parameter or by a user selection. The subset of industry participants may be determined based on a size of the premiums (e.g., top 20 premium industry participants). Further, the order of display of the industry participants may be ordered based on a size of the aggregate premium amount associated with each industry participant (e.g., highest to lowest or lowest to highest).

[00182] A further addition to the second set of transaction statistics may include aggregate remittance values categorized by industry and/or by products over a first period. FIG. 11 illustrates an embodiment displaying an arrangement of the data or information combination for a set of product categories having corresponding aggregate remittance values associated with each product category. FIG. 11 orders the product categories by remittance amounts, the largest remittance amount products listed first. FIG. 11 also illustrates displaying an arrangement of information for a set of industry categories having corresponding aggregate remittance values associated with each industry. In some embodiments, the aggregate remittance values may be based on multiple regions (e.g., local city, region, country, and company-wide/international). In other embodiments, the display arrangement may include functions to display an additional arrangement of information including sub-products and/or sub-industries. For example, FIG. 11 may display a breakdown of remittance values based on sub-products and/or sub-industries when a pointer hovers over a main product or industry category.

[00183] FIG. 11 orders the industry categories by remittance amounts (based on designated geographic area), where the industries with the largest remittance amounts are listed first. The number of industries and products displayed in one screen such as FIG. 11 may only show a subset of a total set of industries or products, respectively. In one embodiment, the display may provide a function that enables additional categories to be displayed, such as a scroll function. FIG. 11 displays the products and industries adjacent each other and parallel each other with a sliding scroll function in which the order of both the product category and top industries category is based on premium amounts per category. The adjacent and parallel arrangement of the products and industries allows an intermediate participant to quickly assess strengths of an intermediate participant company in subscription and/or product placement with respect to product and industry groups.

[00184] Using the displayed arrangement of information, an intermediate participant may be able to immediately determine remittance amounts placed for each product and entity industry to support the intermediate participant's assertions of expertise in those products and industries during for example, a scheduled sales pitch. Generally, this is a common preliminary inquiry during initial meetings with potential clients. Accordingly, the speed at which this data can be communicated to an intermediate participant for handling a potential client is critical and the described information arrangement may guide the intermediate participant accordingly during a presentation.

[00185] FIG. 12 illustrates a third combination of transaction statistics that include a premium amount of aggregate bound policies associated with each of a set of industry participants and an aggregate trade count statistic corresponding to the aggregate bound policies for each of the industry participants. The aggregate bound premium and trade count statistic may be indexed (meaning categorized or filtered) based on product, industry, or both product and industry. As discussed above, a trade count may include submitted, quoted, bound, indication only, and response trades. The premium amount of the third combination or third set of transaction statistics may include only bound transactions. Bound transactions may be subscription or product transactions that have been submitted, quoted for by an industry participant, and accepted by an entity participant. The set of industry participants displayed in a particular screen may be a subset of a total set of industry participants in which associated premium and trade count data exists. The subset of industry participants may be determined by a user selection of the set. Alternatively, the subset may default to a top set of industry participants based on aggregate premium for bound polices, trade count for the bound policies, or both (e.g., based on a ratio of the two).

[00186] FIG. 12 further illustrates a particular graphical arrangement of the combination of transaction statistics as a chart in which the subset of industry participants for the data are displayed along a horizontal axis. A first vertical axis displays a scale indicating an amount of bound premium. A second vertical axis displays a scale indicating a number of trades. The arrangement of the chart allows an aggregate policy premium amount for bound trades to be displayed against an indication of a trade count for the number of bound policies corresponding with the aggregate bound premiums for each industry participants for a period of time. This combination or arrangement of transaction statistics may allow an intermediate participant to quickly assess an industry participant's appetite for specific types of transactions (e.g., based on premium amount). For example, where an industry participant's aggregate bound premium number is high relative to a trade count, the industry participant may be focused on high premium deals. The opposite may be true for industry participants where the bound premium number is low relative to the industry participant's bound trade count.

[00187] In some embodiments, the vertical scales (e.g., scale ranges or scale factors) for aggregate bound premium amounts and bound trade counts may be adjusted based on a number of parameters. For example, the scales may be normalized so that aggregate bound premiums and bound trade counts for each of the displayed industry participants can be displayed within one screen for comparison. In some embodiments, an average ratio between aggregated bound premium amount and bound trade count may be calculated for each of the displayed industry participants. Another advantage of the display arrangement of FIG. 12 is that an intermediate participant may effectively compare the efficiencies of (as determined by the bound premium to bound trade count numbers) each of the set of displayed industry participants. This may be helpful in discussions with both industry participants and entity participants.

[00188] The third combination of transaction statistics may provide advantages in a number of situations. For example, the combination may be advantageous during subscription renewal strategy formulation. The combination may indicate, for example which industry participants have recently been most competitive and recently have the strongest appetite for an entity participant's insurance risk. The information combination and display arrangement may help an intermediate participant facilitate entity participant decisions. In preparing for an upcoming subscription renewal between an entity participant and an existing incumbent industry participant, the display arrangement may be generated based on the entity participant's primary industry as a filter. The results may indicate that the current industry participant (the incumbent) is not one of the top five industry participants by premium for the entity participant's industry, which may prompt advising the entity participant to reconsider renewing with the incumbent. The display arrangement may also provide an insight into an industry participant's preference for small or large premiums (e.g., ratio of trades to premium) to further guide the entity participant as to which markets (e.g., which industry participants) might be the more suitable for the estimated premium for the entity participant.

[00189] The information combination and display arrangement may help in another renewal situation. Based on entity participant feedback, the entity participant may prefer to stay with the incumbent industry participant for the renewal period. The entity participant may be expecting a premium reduction at renewal. The information combination and display arrangement may indicate that the rates for the entity participant's product are flat and the incumbent industry participant appears to have a strong appetite for the product. The entity participant may then make an informed decision for the renewal period based on the most recent data.

[00190] A fourth combination of transaction statistics include submit-to-quote ratios that are aggregated based on policy transactions associated with each of a set of industry participants. A submit-to-quote ratio is a ratio of a number of policy submissions that are quoted over a total number of policy submissions. Generally, a submission is a proposed policy that is submitted to an industry participant for a price quotation. A quoted submission is a proposed or submitted policy in which an industry participant submits a bid (quote or price). Often times, not all submissions may be quoted or bid for, and thus, the submit-to-quote ratios are usually less than one.

[00191] FIG. 13 illustrates an embodiment of a displayed arrangement of transaction statistics that include submit-to-quote ratios associated with each of a set of industry participants. The set of industry participants displayed in the screen of FIG. 13 may be a subset of a total set of industry participants having associated submit-to-quote statistics. The subset may be determined by a user selection of the set. Alternatively, the subset may default to a set of top industry participants based on submit-to-quote values (e.g., highest subset or lowest subset). In one embodiment, the set of displayed industry participants may be placed in order according to the value of their associated submit-to-quote ratios. FIG. 13 further illustrates that a menu function may be activated to filter the subset of displayed industry participants by product and/or industry. Thus the arrangement of statistics can be filtered/indexed/categorized based on product, industry, or both product and industry.

[00192] FIG. 13 further illustrates that an additional transaction statistic to the fourth combination of the submit-to-quote transaction statistics may be a parameter indicating a percentage of quoted submissions attributed to a deductible amount and a limit amount for the quoted policies. FIG. 13 illustrates a table as part of a display arrangement that has deductible ranges disposed along a horizontal axis and limit ranges disposed along a vertical axis. Each entry in the table has a corresponding deductible and limit range. An entry in the table indicates a percentage of a total number of quoted submissions for a particular deductible and limit range. In one embodiment, the total number of quoted submissions may be restricted to the aggregate number of quoted submissions for the subset of displayed industry participants. Thus, for example, in FIG. 13, the 100 percent value of quoted submissions may refer to the total quoted submissions for the five industry participants listed in the display.

[00193] The combination of statistics provides intermediate participants with the advantage of being able to identify which markets may currently be quoting for placements with certain limit and deductible characteristics. Further, the arrangement of the statistics may allow intermediate participants to efficiently determine which specific industry participants have been quoting for an entity participant in a given industry or product group. This may be helpful in the following situations. A first situation is responsive marketing. An incumbent industry participant may have promised a flat renewal for an entity participant. At the eleventh hour, the incumbent industry participant may quote a double-digit increase. An intermediate participant needs to be able to react immediately to determine which industry participants may be most likely to quote the entity participant's program so that a last-minute submission may be made. The information combination and corresponding display arrangement may allow an intermediate participant to immediately determine that one or more markets (e.g., insurance provider) have a high submit-to-quote ratio for the type of program the entity participant needs and a submission may be directed to each market (e.g., insurance provider). In a second situation called "carrier participation" an entity participant may be interested in alternative subscription structures. The entity participant may, in this case, want to know which industry participants are quoting on certain program structures to best align their program with the right industry participants. The display arrangement may allow an intermediate participant to immediately identify the optimal limit and deductible level for each of its industry participants. In a third situation of program design, an entity participant may inquire about appropriateness of their limit and deductible for an existing policy. The information combination and display arrangement may allow the intermediate participant to determine where the entity participant fits into the mix of limits and deductible ranges for a current period and advise the entity participant appropriately.

[00194] A fifth set or combination of transaction statistics and a display arrangement of the transaction statistics illustrate industry participant declined submissions and declination reasons for those declined submissions. Generally, the dashboard system and environment provides overviews from both the industry participant and entity participant perspective on the reasons why proposals have been declined. The intermediate participant may generally input this information into an intermediate participant computer at the time that either the industry participant or the entity participant declines a quote, and is selected from one of twenty standardized declination reasons. The aggregate declinations may be categorized by product and industry. In some embodiments, when filtering by one or both of product and industry, only the policies for the particular product and/or industry may be examined for declination reasons. Thus, the percentages of the declination reasons may be only a portion of total declination reasons for all declined policies or transactions.

[00195] FIG. 14 illustrates an embodiment of a display arrangement involving the fifth set of transaction statistics. The declination policies used to determine percentages may be filtered by a product (e.g., property) and an industry (e.g., manufacturing). In the arrangement of FIG. 14, a first chart lists a set of declination reasons and a percentage breakdown for each declination reason for all industry participants specific to the selected product and industry. In the embodiment illustrated by FIG. 14, industry participant declination reasons may include uncompetitive price, exposure limit issues, no response (or lack of response) from industry participant, other declination reason, and insufficient underwriting data. FIG. 14 also shows at the top of the chart that the percentage of overall declination reasons attributed to the product and industry is 91 percent. In some embodiments, when no industry and no product group are selected, the number of industry participant declined submissions may represent an aggregate of total declined submissions across all industry participants (i.e., 100 percent). [00196] The information or data arrangement of FIG. 14 illustrates that the number of industry participant declined submissions may be filtered for a particular industry participant and displayed adjacent to the declination percentages for all industry participants (of a particular industry and/or product, if selected). In particular, FIG. 14 illustrates a display embodiment showing an arrangement of transaction statistics where a chart of overall industry participant declination reasons is arranged adjacent to a chart of declination reasons for a specific or selected industry participant. The industry participant may be selected or targeted for analysis. FIG. 14 further includes a peer chart in which declination reasons can be aggregated for a select subset of industry participants. FIG. 14 illustrates that at least a second peer chart may be disposed adjacent the first peer chart, the selected industry participant chart, and the all industry participants declination chart. In one embodiment, the subset of industry participants for either the Peer 1 or Peer 2 group may be selected based on comparable peer industry participants. The comparable peers may be determined based on a number of pre-programmed parameters such as, but not limited to, industry and product, aggregate premiums, deductible and/or limit amounts of polices placed, etc. In one embodiment, Peer 1 and Peer 2 may be determined by choosing industry participants that rank above and below the subject or selected industry participant in terms of total rejection reasons. If the subject industry participant is first in terms of premium volume ranking, then the next two industry participants may be chosen as peers. If the subject industry participant is the last in terms of premium volume ranking, then the preceding two industry participants may be chosen.

[00197] The combination of statistics may provide intermediate participants with an advantage of being able to advise an entity participant towards industry participants (markets) that may eventually be more receptive to their policy structures for specific industry and product groups. For example, if an incumbent industry participant has a history of quote rejection for inferior pricing, an intermediate participant may consult the display of declination reasons for the incumbent industry participant in relation to the overall industry participant and peer industry participant information and may advise the entity participant to market a submission for an upcoming renewal accordingly. This could provide the entity participant with premium savings.

[00198] The combination of industry participant declination reasons and corresponding display arrangements may also have positive impacts on the following intermediate participant situations. A first situation may involve intermediate participant coaching of industry participants. In this situation an intermediate participant may use the aggregated information to discuss industry participant performance feedback. For example, an industry participant may meet with an intermediate participant company to introduce a new product. The underwriter or industry participant may ask for performance feedback from the intermediate participant. The intermediate participant may be able to use the display and information combination to demonstrate that the primary reason entity participants may by rejecting the industry participant's quotes is inferior pricing. One may specifically identify that this industry participant loses on pricing some percentage (e.g., 55%) of the time, but the industry participant's peers lose on pricing less frequently (e.g., only about 30%).

[00199] In a second situation, an intermediate participant can use the information set or display arrangement of the described system to advise an entity participant for an upcoming renewal. An intermediate participant may plan to approach three markets (industry participants) with a high risk for which it may be difficult to solicit bids. The entity participant may want to know the rejection behavior of the three markets. Using the described display arrangement, the entity participant may be advised of the top five reasons each of the industry participants have rejected quotes as well as how they may match up against their peers.

[00200] A third situation may involve public perception of an industry participant. For example, an industry participant may be under public financial pressure and entity

participants may want to know how other buyers perceive the industry participant as a viable market. An intermediate participant can use the display arrangement of Client Rejection Reasons to determine why entities have declined to bind (or accept contracts) with that market (industry participant).

[00201] A sixth transaction statistic set may include percent change in pricing and policy components for subscription renewals based on real time aggregated transaction data. The sixth set may show a rate of change or a percentage change in premium pricing for corresponding periods from a year ago. In other words, the rate change of a displayed quarter may be a percent change in the difference in a price value (e.g., a premium value) from the most recent quarter (e.g., second quarter of 2010) to the corresponding quarter from a year prior (e.g., second quarter 2009). FIG. 15A illustrates a display embodiment of renewal pricing trends for five previous quarters, Q4 2010, Ql 2011, Q2 2011, Q3 2011, Q4 2011. FIG. 15A illustrates the data as a bar graph with quarterly periods on a horizontal axis and percentage change of aggregate premium amounts on a vertical axis. The aggregate premiums may be filtered by product and industry groups. Thus, for example, the percentage change in premiums may be specific to subscription contracts placed for a selected product and/or a selected industry.

[00202] In some embodiments, the sixth transaction statistic or any of the statistics described herein may be generated based on real time pricing information. For example, as transaction details (e.g., of policy premiums) are inputted into an intermediate participant computer for a particular recent transaction, that data may be tagged for more immediate aggregation and/or continual recalculation (or generation) of the sixth statistic (or any of the other statistics described herein). In some embodiments, real time aggregation, as used herein, may include a release of the data values of the selected parameter(s) for access by an aggregation function immediately after the completed policy transaction has been entered into the computing system. In some embodiments, the request for the statistic may trigger a release of the data values for aggregation. The release of the data values may involve allowing access to the selected parameter values (e.g., by the aggregation function) for generation of statistics. Releasing data values as used herein may involve storing the data values in a manner that makes the data values available or accessible to the aggregation function. In some embodiments, real time aggregation may include initiation of a function to transmit and/or collect data values of the selected parameter(s) immediately after a completed policy transaction has been entered into a system. In some embodiments, real time aggregation may include a function to access/aggregate data values of the selected parameter(s) that are released, stored, or otherwise made available in response to a request to generate statistics. In any case, while a first process of aggregating transaction data described above is made on a quarterly basis, real time aggregation may involve aggregation of the values of selected parameters before a quarterly period is finished. In some embodiments, the real-time data may form the basis of a continual extrapolation of premium rate data to indicate predicted values of premium rates for the current quarter (or beyond the current quarter).

[00203] The generation of real time statistics may be a costly function in terms of computing power and bandwidth (e.g., continually transmitting transaction data over a network and executing functions to receive and process the data) and thus, in some embodiments, only one or a few parameters may be selected for real time, continuous aggregation and statistic generation. In some embodiments, the selected parameters for real time aggregation may be determined based on a legal status parameter associated with an access location or with a user identity. Alternatively, the display of any statistics based on any parameters of real time aggregation may be based on the legal status parameter. Generally, the legal status parameter (as used herein) may be a parameter based on a local or regional law dictating what type of policy or transaction data may be used or displayed to certain entities. In some embodiments, premium pricing may be the selected parameter of focus. The transaction statistic may involve a forecasted quarter that may represent a current quarter that is not yet complete or finished. For example, if the current day is January 27, 2012, then a designated third quarter (01) of 2012 may not yet have finished. A value of a metric (e.g., premium pricing/rates) for Ql 2012 may represent a forecasted metric. FIG. 15A illustrates a forecasted current quarter of Ql 2012 as an example. Generally, the forecasted current quarter may be calculated based, in part, on policy contracts that have been bound during the current, unfinished quarterly period, where the data on the premiums of the policy contracts (or other parameters) may be continuously aggregated based on a shorter time period (e.g., by day, hour, minute, second rather than monthly or quarterly). Transaction data for an unfinished quarter is generally data that has not been released by the system for general reports and aggregation. The forecasted current quarter may also be calculated by extrapolating the percentage change of prior quarters with the information collected for the current unfinished quarter.

[00204] FIG. 15B illustrates another combination of transaction statistics that includes percent change in premiums broken down by a number of industries for a selected product. An alternative embodiment may involve transaction statistics that include percent change in premiums broken down by a number of products for a selected industry. The arrangement of FIG. 15B includes a bar chart where industries are displayed on a vertical axis with corresponding percent changes in premiums indicated as bars on a horizontal axis. FIG. 15B illustrates that one arrangement may include an adjacent second bar graph of the same configuration except with forecasted percent changes for each industry based on a current, unfinished quarterly period.

[00205] FIG. 15C illustrates another combination of transaction statistics that include percent change in renewal premiums along with changes in components of the policies renewed. In particular, FIG. 15C illustrates the percent change in renewal rate and renewal PPM and percent changes in policy limits, policy exposure amounts, and policy premiums.

[00206] The sixth set of statistics and the set of display arrangements may be used to start a price discussion with an industry participant. An intermediate participant may be able to compare current premium pricing against recent or historical pricing to identify pricing trends and develop optimal broking strategies. The combination of transaction statistics may also assist an intermediate participant in preparing early renewal strategies and to manage entity participant's renewal expectations. [00207] The information combination and display arrangement may benefit an intermediate participant in the following situations. A first situation is when an intermediate participant is developing a renewal strategy plan for an entity participant in a particular industry, for example, the aviation industry. The intermediate participant may use the information combination and display arrangement to provide a real-time pricing comparison of where the aviation market is currently to where it was the previous year. If the rates are down about 1%, for example, from last year, the intermediate participant may advise the entity participant that a significant market-driven rate increase may be unlikely.

[00208] In a second example, an intermediate participant may be approached by an entity participant who discovers from general news sources that the liability market may be hardening, meaning that the entity participant may experience a 10% increase, for example, during the 2010 renewal cycle. In this situation, the entity participant may be concerned about the entity participant's upcoming products liability placement. Using the information combination and displays, an intermediate participant may be able to advise the entity participant that while the general liability marketplace may appear to be hardening, the products liability marketplace may only be experiencing a modest hardening (e.g., a 1% to 2% increase).

[00209] A third illustrative situation involves determining a broking strategy. For example, an incumbent industry participant may have indicated that a construction entity participant can expect a 5% price increase at renewal time. By consulting the information combination and display arrangements, an intermediate participant may quickly assess that rates for the construction industry have declined by 1%. Because the entity participant's losses have remained relatively stable and their exposure values have decreased, the intermediate participant may be able to recommend remarketing at renewal (i.e., plan for new policy submissions to other industry participants).

[00210] FIG. 16A illustrates a data display arrangement of one of three key metrics over a period of time that may be referred to as a "trading flow" set or display arrangement. The three key metrics may be a submission flow, a quote rate, and a Hit Rate. FIG. 16B illustrates a particular example of a submission flow statistic. The length of the periods for the key metrics may be adjusted, for example, to be monthly or quarterly periods. The key metrics may be indexed (categorized or narrowed) by product, industry, or region association (e.g., North American region). In an embodiment, the key metrics may also be indexed by industry participant appetite, incumbency, and industry participant division. Indexing by industry participant appetite may include filtering the metric based on the capacity or requested limit of an industry participant to accept submissions. Indexing by incumbency may include filtering the metric based on policy transactions that remain with an existing industry participant. With respect to industry participant divisions, indexing may be performed differently based on the entity accessing the data. For example, indexing may be performed differently for an industry participant than a sub-carrier industry participant.

Generally, indexing data may refer to a method of identifying data that has a particular characteristic or belongs to a particular category. This may be done, for example, by associating a tag, flag, or other parameter with the data. With respect to using a database, indexing may refer to associating a parameter with a discrete unit of data. The association of a parameter may be referred to as tagging the data or applying a flag to the data. More particularly, where a database includes a database record that may be represented as a row of a table, indexing the database record may involve associating a field or including a field with the database record to identify the database record or row with a particular category or characteristic. The associated parameter may then be used in various functions to separate database records by the characteristic. The aggregated transaction statistics may be separated into specific categories such as a product and/or an industry. This separation into categories may be referred to herein as categorizing, narrowing, specifying, etc. In some cases, indexing of the data may also refer to the separation of the data into a specific category.

Generally, when a statistic is described herein to be indexed or specific to a particular category, then the statistic may have been aggregated to exclude records that do not belong to the particular category when calculating the statistic. Thus, for example, when the

"submission flow" is indexed by a product such as property insurance, then the "submission flow" metric may be aggregated for and specific to only the property insurance transactions, excluding other transactions from product categories outside of property insurance.

[00211] For each of the three metrics, the display arrangement may narrow the metric data to (e.g., show aggregate data that is specific to) each of a set of industry participants, the set of industry participants including at least a selected or subject industry participant, wherein the subject industry participant may be displayed for comparison. The subject industry participant may correspond to a subscribed industry participant viewing the statistic or display arrangement of the statistic. The set of industry participants may be a subset of a total set of industry participants for which transaction data exists within the dashboard system. The subset of industry participants may be determined by a dashboard system parameter or by a user selection (e.g., by the selected industry participant using the described system). An average of each of the three metrics may be included, wherein the average is calculated based on the subset of industry participants including the subject industry participant (in some embodiments, the subject industry participant may not be included in the average).

[00212] Each of the three key metrics may be arranged for display as a line graph, as illustrated in FIG. 16A. A vertical axis of each graph may correspond to a value of the metric while a horizontal axis of the graph may represent time periods (e.g., divisions based on monthly or quarterly periods). FIG. 16A illustrates that each of the metrics may be indicated on the vertical axis as a percentage of overall transaction submissions. Each industry participant may be represented as a different color line. It should be noted that while FIG. 16A illustrates the data as a line graph, other types of graphs may be used as well. Each metric displayed may also include a plot of an average value of the metric for the determined set of competitors. In some embodiments, the average may be calculated to include the subject industry participant, while, in other embodiments, the average may be calculated to exclude the subject industry participant. FIG. 16B illustrates a submission flow graph for a casualty /liability segment where only the subject industry participant is plotted along with an average competitor line. When comparable industry participants (e.g., peers) are difficult to determine for a selected industry participant, the average competitor plot may be displayed as a default without competitor (peer) plots. This may be the case when there are only a few competitors in a particular industry segment and revealing submission data for a

competitor(s) may indicate the identity of the competitor (i.e., the competitor information may not be anonymous). In an embodiment, individual competitors (industry participants) may not be displayed unless at least a threshold number (e.g., three, five, ten, etc.) of comparable industry participants can be determined. In an embodiment, an average may only be shown if there are at least a threshold number of comparable industry participants.

[00213] The set of competitors may be determined based on a number of pre-programmed parameters such as, but not limited to, industry and product, aggregate premiums, deductible/and or limit amounts of policies placed, etc. In one embodiment, the set of competitors may be determined by choosing industry participants that rank above and below a threshold amount or level from the subject industry participant in terms of premium volume. If the subject industry participant is first in terms of premium volume ranking, then the next two industry participants may be chosen as peers. If the subject industry participant is the last in terms of premium volume ranking, then the preceding two industry participants may be chosen.

[00214] Generally, a "submission flow" statistic may be a metric indicating an aggregate number of submissions for the selected industry participant over a total number of submissions. The "submission flow" statistic may also include a submission flow indicating an average number of submissions for a first set of industry participants that are competitors to the selected industry participant over the total number of submissions. A "submission flow" display arrangement may be used to determine patterns of submissions for competitor industry participants by product and industry and the display may allow a selected industry participant to make an advantageous, timely solicitation for submissions in particular marketing areas (e.g., for a specific product or industry).

[00215] A "quote rate" statistic may be a metric indicating an aggregate number of submissions to an industry participant(s) that have been quoted for by the industry

participant s). The "quote rate" statistic may be indicated as a percent of the aggregate number of submissions to an industry participant(s) that have been quoted for by the industry participant s) over a total number of submissions to the industry participant (s). An industry participant may not quote on all submissions it receives.

[00216] A "hit rate" statistic may be a metric indicating an aggregate number of quoted submissions that are bound. In other words, the "hit rate" may represent a number of submissions that have been quoted by the industry participant and are accepted by entity participants or policy buyers. The "hit rate" statistic may be indicated as a percent of the aggregate number of quoted submissions that are bound over a total number of quoted submissions. Generally, the "hit rate" statistic may be specific to a particular industry participant or set of industry participants. For example, the "hit rate" statistic may be an aggregate number of binds for an industry participant over a total number of transactions quoted by the industry participant. Similarly, for a set of industry participants, the "hit rate" statistic may be an aggregate number of binds for the set of industry participants over a total number of transactions quoted by the set of industry participants.

[00217] FIG. 17 illustrates a data display arrangement of key metrics for four previous quarters for both the selected industry participant and top competitors (peers) to the industry participant. The set of competitors used in this data arrangement may be based on a paid service level for the selected or subject industry participant. The key metrics may be narrowed by product, industry, and region. In this data arrangement, the key metrics may be further narrowed by incumbent or non-incumbent parameters. In an embodiment, the key metrics may also be indexed by industry participant appetite and industry participant division. Indexing by industry participant appetite may include filtering the metric based on the capacity or requested limit of an industry participant to accept submissions. With respect to industry participant divisions, indexing may be performed differently based on the entity accessing the data. For example, indexing may be performed differently for an industry participant than a sub-carrier industry participant. The key metrics may include "submission flow", "quote rate", "hit rate", and "conversion rate."

[00218] Conversion rate may represent the proportion of trades which ultimately result in binding quotes. Conversion rates may be calculated by multiplying submission rates (number of submissions for an industry participant over total number of submissions) by quote rates (number of submissions quoted by one or more industry participants over a total number of submissions) and then by hit rates (number of quoted submissions that are bound over a total number of quoted submissions). As with submission rates, knowledge of conversion rates may allow an industry participant to focus on particular industries and products in which it has an appetite for risk, and to greatly improve its service offering. The transparency of conversion rates, and industry participants' desire to improve this metric, may increase competition for the benefit of entity participants.

[00219] FIG. 19A illustrates a data display arrangement 1900 of trade declination statistics. A subject industry participant is labeled "Demo" in FIGS. 19A, 19B, and 19C. The declination statistics may involve aggregate declination reasons for both entity participants and industry participants as identified by intermediate participant members of the

intermediate participant company during transaction recording. For example, the total declined trades by an industry participant may be decomposed or separated into constituent parts, for example, by industry participant declination reasons 1906. In one embodiment, the top declination reasons specific to the selected industry participant may be displayed along with a corresponding percentage indicating the rest of the market (provided as a benchmark), and labeled "market" 1904 in FIG. 19 A.

[00220] Turning to FIG. 30C, the screenshot 3030 illustrates another graphical layout for reviewing industry participant declination reasons. As illustrated, a bubble graph interface presents industry participant declination reasons, illustrated in circles ranging in size by most prevalent declination reason to least prevalent declination reason. For example, as illustrated, the reasons of no response by carrier, class of business, underwriting concerns, and pricing were most prevalent, while the reasons did not respond by deadline and loss experience were lease prevalent. As illustrated, the industry participant declination reasons of the screenshot 3030 also include a terms and conditions declination reason and a capacity declination reason.

[00221] The declination statistics may be calculated to be specific for product, industry, and/or deal size (e.g., FIG. 19B is specific to a property category). Deal size may be separated where large deals are deals with premiums above an aggregated average premium or median premium while small deals are deals with premiums below the average or median. FIG. 19B illustrates that the industry participant declination reasons 1906 may include at least one reason from the set of reasons including uncompetitive price, capacity, class of business, exposures, and premium threshold or entity participant financials.

[00222] Entity participant rejected trades may be decomposed in a similar manner to industry participant declination reasons. As illustrated in FIG. 19C, entity participant rejection or declination reasons 1922 may include at least one reason from the set of reasons including different quote accepted, inferior pricing, inferior terms and conditions, incumbent relationship, and industry participant financials or perceived weakness.

[00223] Generally, the dashboard system industry participant dashboard 190, illustrated in FIGS. IE and IF, may provide an overview from both the industry participant and entity participant perspective on the reasons why proposals have been declined. This information may be input by the intermediate participant at the time that either the industry participant or the entity participant declines a quote, and is selected from one of many standardized declination reasons. Declination reasons may include capacity, class of business, loss experience, negative prior experience, no response, terms and conditions, uncompetitive, and/or underwriting concerns. Declination reasons may also be indexed by industry participant appetite, incumbency and industry participant division, similar to other display arrangements described herein. The industry participant may then be presented with the top five reasons for declination (as a percentage of the total reasons for declination), and separated further according to the industry participant's preferences by reference to product, industry and deal size. Higher subscription level industry participants may be able to see their performance measured against a market average. By contrast, lower subscription level industry participants may see only the market average. The declination display arrangements may be performance enhancing for the selected industry participant, as it may enable industry participants to determine key areas in which their performance can be improved.

[00224] To receive greater insight into trade declination metrics, in some embodiments, a particular bar in any one of the bar graphs represented in screenshots 1900, 1910, and 1920 may be selected to cause presentation of a detailed declination record analysis, for example as illustrated in a screenshot 1930 of FIG. 19D. Turning to FIG. 19D, detailed declination analysis includes information such as entity participant name, line of business, effective date, expiration date, risk description, industry participant declination reason, and deal size. [00225] Portions of declination metrics data, either at the more abstract level presented in FIGS. 19A through 19C or on a refined level as presented in FIG. 19D, may be shared with other participants of the dashboard environment (e.g., to contribute to peer metrics of competitors). Sharing, in some embodiments, is enabled through an anonymizing feature of the dashboard system, such that other participants cannot recognize data points as belonging to a particular participant.

[00226] FIG. 20A illustrates a transaction statistic and data arrangement referred to as "broker insights." The "broker insights" transaction statistic set may be based on an industry participant performance survey conducted by the intermediate participant company that classifies and quantifies intermediate participant perceptions of industry participants across a number of areas or attributes. The surveys may be performed or executed on a periodic basis (e.g., at least once a year) on intermediate participant computers (e.g., based on interactions with entity participants). The surveys may be asked while performing general entity participant processing.

[00227] A summary metric from the survey may be a Net Promoter Score (also referred to herein as an "NPS") which may represent an overall metric compiled to indicate the proportion of respondents that reported positive, negative, or neutral towards an industry participant. The NPS may be presented for the selected or subject industry participant and competitors associated with the selected industry participant across a number of dimensions, including respondent (a surveyed entity) line of business, entity participant segment and respondent role.

[00228] An NPS rating may be obtained, for example, by asking customers, on a zero to ten rating scale, how likely they would be to recommend a product to a friend or colleague.

Based on their responses, customers may be categorized into one of three groups: Promoters (e.g., 9-10 rating), Passives (e.g., 7-8 rating), and Detractors (e.g., 0-6 rating). The percentage of Detractors may be subtracted from the percentage of Promoters, for example, to obtain a Net Promoter Score. While a scale of 10 is used in the example above, any scale range may be implemented. Ranges for each category type may be a high, middle and low range. In particular, promoters would be a high end range, passives would be a middle range, and detractors would be a low end range.

[00229] Under a system implementing an NPS-based survey, members of the intermediate participant company may be encouraged to supplement the question with further queries, thereby soliciting the reasons for a customer's rating of that company or product. The reasons may then be provided to front-line employees and management teams for follow-up action. Intermediate participant feedback may be used extensively when engaging actively with industry participants in assessing areas where industry participants could improve their responsiveness for entity participants' benefit.

[00230] In the described system, NPS ratings may be obtained for key activity areas, such as underwriting performance and claims performance, and key product areas such as property, construction and casualty /liability. Follow-up questions may also be asked around a set of "attributes" of the industry participant's performance, such as willingness to pay, empathetic claims handling, and efficiency. The industry participant's score (based on the scale of ten) for each NPS attribute may then be presented against those of each of its top competitors (presented anonymously). In an embodiment, the top ten competitors may be presented. Industry participants may typically regard NPS and attribute data points as key metrics in improving their product and service offering.

[00231] FIG. 20B illustrates a more granular review of intermediate participant insight metrics including a detailed display on industry participant performance based on segments of the lifecycle of the broking process. The lifecycle may include, for example, underwriting, post-placement, claims and overall relationship attributes. In one embodiment, survey demographics may be viewed from the industry participant dashboard interfaces described in relation to FIGS. IE and IF to show the number and make-up of respondents to the survey in each industry participant dashboard region.

[00232] Industry participants' enhanced insights obtained from use of the intermediate participant insight display may enable industry participants to deliver distinctive value for entity participants, by giving them a clearer understanding of the reasons underpinning success and failure, improving entity participant satisfaction and competing more effectively. More industry participants are able to benefit from the service, including those whose size and value currently precludes them from purchasing access to the system. Industry affiliates would be granted insights into macro and micro industry trends, which would enable them to assess industry participant company performance.

[00233] FIG. 21 A illustrates a data display arrangement referred to as a pipeline. The pipeline display generally shows transaction opportunities for an industry participant forecast over an upcoming period of time (e.g., over an upcoming six months). Generally, a pipeline opportunity represents an expiring policy that may be up for renewal. In some embodiments, a pipeline opportunity may also represent new policy interest. In other embodiments, a pipeline opportunity may also represent policies that may not be up for renewal in the near future, but where an entity participant owning the policy may have a desire to renew early or restructure its policy. The pipeline opportunities may be filtered or narrowed by product and industry and by region. The pipeline opportunities may also be filtered or indexed by industry participant appetite and incumbency. In an embodiment, pipeline opportunities may also be filtered by cross sale opportunities where the condition of one policy may present opportunities to sell a different policy. Additional reports may be displayed as an option based on a subscription level.

[00234] There may be two elements to the pipeline opportunity monitoring section of the industry participant dashboard. The first may be a statistical analysis of an intermediate participant's renewal book of business, and the second may be a report of upcoming policy renewal opportunities. The pipeline display arrangement shows for each selected geographic area the total number and total value of renewal possibilities on an intermediate participant's book of business falling due in the next six months. Industry participants may be able to view this information by product or by industry. In an embodiment, all industry participants may have the same view of information. In an embodiment, not all industry participants will have the same view. This display arrangement may assist industry participants in planning their future business.

[00235] FIG. 2 IB illustrates a pipeline report that may be generated from a pipeline display that includes a column called "Policy ID." Each row in the pipeline report may be a unique entry having a corresponding unique policy identifier relating to the underlying pipeline opportunity that the row may represent. The pipeline report lists opportunities arising from existing policies that are brokered that may be due for renewal in the near term. The information available in this display arrangement may include entity participant name, industry, product, approximate deal size, region, and month of maturity. Industry participants may have the ability to scan the record themselves for potential opportunities. This ability may be based on a service level. Once an industry participant becomes aware of a particular risk opportunity, they may be able express their interest in the opportunity. When a selected industry participant determines a particular opportunity in which the industry participant is interested, the policy ID may be referenced in a "register policy interest" screen for inputting an interest (not shown). Once the policy interest screen is filled out and submitted, a computer system implementing the methods described herein may then notify the

intermediate participant company of the interest in the selected pipeline opportunity for further action. If an entity participant is receptive to obtaining quotes from alternative industry participants, an intermediate participant may then attempt to secure options for those industry participants the entity participant has selected. [00236] Pipeline opportunity management in essence may operate as an introduction service prior to policy renewal time, increasing the visibility of upcoming renewal opportunities to industry participants that have the risk appetites for that entity participant's custom or specifications and thus broadening the entity participant's choice (e.g., by motivating industry participants to bid for renewals) where options may have otherwise been restricted to an incumbent. This may result in the introduction of increased competition into relationships that were previously locked, which may tend to result in more suitable coverage on better terms and conditions.

[00237] Traditional means of brokering introductions between entity participants and industry participants at renewal time may have been somewhat haphazard and reliant entirely on the knowledge possessed by individual intermediate participants. The industry participant dashboard introduces a sophisticated and systematic introduction service which allows proactive matching of entity participant needs to industry participant risk appetite and which, in turn, may allow all parties to deploy their resources more efficiently and objectively.

[00238] FIG. 21C illustrates a screenshot 2140 including a bar graph representing opportunities at various stages 2144, where an intermediate participant initially registered interest in the opportunities via the dashboard system. By registering interest via the dashboard system, features of the dashboard system can push the interest request information to industry participants to prompt a timely response regarding the opportunity. As illustrated in the screenshot 2140, blocks of opportunities span the entire timeline of stages 2144, from a pending stage 2144a (e.g., pending a response from the industry participant) to a bound stage 2144g. Intermediate stages represented may include, for example, a submitted stage 2144b, a carrier declined stage 2144c, a client rejected stage 2144d, a not suitable for submission stage 2144e, and a quoted stage 2144f. Additionally, the bar graph illustrates a total number of opportunity interest requests 2146 placed by intermediate participants during a time period defined by a "start" drop-down menu 2142a and an "end" drop-down menu 2142b. The industry participant may optionally filter the information presented in the bar graph using a "category" drop-down menu 2142c for filtering by product category, a "division" drop-down menu 2142d for filtering by industry participant division, and/or a "region" drop-down menu 2142e for filtering by geographic region.

[00239] FIG. 2 ID illustrates a screenshot 2160 of a detail report regarding interest intermediate participants have expressed in opportunities during a selected time period. An industry participant may have accessed the screenshot 2160, for example, by selecting the column of the bar graph in the screenshot 2140 of FIG. 21C indicating total number of opportunity interest requests 2146. The detail report includes a table of opportunities registered by an interest tracker system of the dashboard system. Each opportunity may include a combination of the following details: interest registration date, entity participant name, product, line of business, policy expiration date, entity participant industry, intermediate participant name(s), intermediate participant email(s), deal size, and status. As in FIG. 21C, the series of drop-down menus 2142 are available for filtering the data presented in the table, for example by time period (using the "start" menu 2142a and "end" menu 2142b), category (using the "category" menu 2142c), industry participant division (using the "division" menu 2142d) and/or geographical region (using the "region" menu 2142e).

[00240] FIG. 22A illustrates a data display arrangement referred to as "premium share". The "premium share" display or statistics set may provide a breakdown of industry participant written premium, overall market premium share, and a ratio or percent of industry participant premium share over total market premium share. These statistics may be specific to each of a set of product lines over the past 12 months in a selected geographic region (e.g., country).

[00241] The "premium share" statistics and corresponding display arrangements may provide a subject industry participant a general overview of their place in the overall market and the concentration of their business by segment.

[00242] The industry participant dashboard described herein generally provides selected information to those industry participants that procure access to the industry participant dashboard computing system. An essential function of the described system may be to provide an objective benchmarking tool by reference to which industry participants may assess their performance in relation to other industry participants on an anonymized and aggregated basis. This may allow industry participants utilizing the system to focus their efforts on aspects of their business which require improvement, and ultimately to develop a better service offering for their existing and potential clients.

[00243] The system may function to collate and process historical and aggregated information crucial to the subscription decisions specific to industry participants separately by class and geography around the globe. The information provided may include various business performance analytics that do not include individual trade pricing data. The data may be presented in a user-friendly format that may indicate in general terms the extent and approximate value of coverage which industry participants are quoting and binding in particular classes and territories. Sophisticated algorithms may allow an intermediate participant to predict buying behavior in the coming months, thereby informing strategic marketing and buying decisions and enabling its entity participants to stay ahead of the market.

[00244] Industry participants may also be able to obtain accumulated information on classes of business and territories in which they are interested. This benchmarking process may allow industry participants to assess in general terms how they are performing relative to their peers, which may enable them to improve their products and services, and to make them more attractive to potential clients. Moreover, the dashboard system may provide insight into market conditions across multiple geographies. As such, access to the dashboard

environment may provide an indirect benefit of forging a more coherent marketplace, by facilitating cross-border coverage.

[00245] Generally, the dashboard system may utilize a relational database for the industry participant dashboard. In some embodiments, an analysis database (cube) may be used. The database may be implemented with a database schema that includes tables containing the aggregated data, prepared and loaded by an intermediate participant procedure, for example using an SQL Server Integration Service, for the appropriate reporting period. The data in the database may comprise all necessary data to populate different screens of the dashboard. The database schema may exist primarily to service the industry participant dashboard application and may be designed to make retrieval as simple as possible and optimize query performance. Most, if not all, aggregation and data manipulation may be performed upon loading of the data into the dashboard schema. Based on this design principle, the schema for the dashboard schema may use a small set of tables for each panel (display arrangement) within the dashboard. These tables may be pre-aggregated by an extract transform load (ETL) process to minimize joins and data manipulation at run-time. In addition, the database may use views (or indexed views if possible) to further minimize joins for the display panel chart data. Therefore the SQL queries will just do simple queries— avoiding complex SQL. The ETL process may pre-calculate averages for each industry participant /product/industry combination as required by the panels. It may also pre-calculate the "market" values, i.e. sum of competitors where appropriate. A refresh of the data within the dashboard database may be performed regularly by an ETL process. This process may include aggregation and transformation of the data to fit the analytical schema design of the industry participant dashboard database and its retention of historical data. Some aggregation and data manipulation may also be performed upon user request through the industry participant dashboard application. [00246] The default dataset for the dashboard may be the most recent reporting period, e.g. the current month, quarter or year, as appropriate. However, to facilitate future extension of the dashboard, including potential reporting data comparison, the database schema may support the tagging of data according to the reporting period for which it was first supplied. This means that the data in the dashboard schema may grow over time and each new data load may augment the existing data, even if portions of it are potential copies of previous data.

[00247] In some embodiments, one or more computer devices are used to generate a risk portal that allows business entities to view and interact with a wide range of risk data. As used herein, business entities are not limited to for-profit entities and include government entities and nonprofit entities. FIG. 23 illustrates an example portal screenshot 2300 that includes risk data. The data used to populate screenshot 2300 may be transmitted from one or more devices, such as networked servers. The servers and/or other computer devices may generate a number of portals that each contains risk data relevant to a particular business entity.

[00248] Portal screenshot 2300 is divided into several sections. A dashboard system section 2302 may be included to allow a business entity to access information such as pricing insights, research insights and market insights. In some embodiments, the data used to populate dashboard system 2302 may originate from a database of subscription and/or product placement data, delivering critical marketplace intelligence. The dashboard system, for example, may provide insight across industry participants, industries and products on every level, from individual transactions to global trends. The dashboard system may also enable benchmarking of like risks placed throughout the globe, and at what price, in order to help entity participants evaluate industry participant performance and anticipate shifts in the market.

[00249] Portal screenshot 2300, in some implementations, includes a video section 2304. Video section 2304 may include links to recorded programs 2306 that may be general in nature and/or targeted toward specific business entities. For example, a recorded program may relate to mitigating reputation risk concerns for a particular business entity. Video section 2304 may also include a live TV feed section 2308. Live TV feed section 2308 may be used to provide real time information to business entities. For example, during a hurricane live TV feed section 2308 may include an expert explaining how current hurricane developments may impact a business entity. [00250] A risk management tools section 2310 may be included to provide users with a variety of risk management tools. A worldwide risk levels link 2312 may be selected to display a map that illustrates and explains risk levels around the world or within a specific geographic region. The map may be color coded to represent overall risks to supply chains, manufacturing capabilities, reputation and other elements. A dashboard system

benchmarking service link 2314 may be selected to request a benchmark report.

[00251] Risk management tools section 2310 may also include a risk maturity index section. The risk maturity index section may include a link to provide an overview of a risk maturity index. In one embodiment, a risk maturity index is created from answers to a questionnaire on risk management processes, corporate governance and risk understanding.

[00252] Portal screenshot 2300, in some implementations, also includes risk information derived from one or more social media sources, such as blogs, Twitter® by Twitter, Inc. of San Francisco, CA and Facebook® by Facebook, Inc. of Menlo Park, CA. Social media sources may show trends that are not reported by other sources of information. For example, a Facebook® group may be attempting to convince users to boycott a product and this event may not be reported by traditional news sources. Social media sources may also report news sooner than other traditional news sources.

[00253] Social media sources may be monitored to provide industry risk news in an industry risk news section 2318, reputation risk news in a reputation risk news section 2320 and supply chain risk news in a supply chain risk news section 2322. In some embodiments, business entities provide search criteria, search templates or other information used to located relevant social media posts. In various embodiments, social media information may be filtered with one or more computer devices, manually or with a combination of computer devices and manual filtering. Each section may include a news feed that identifies the social media source and provides a brief summary of the content. The news feed may be in the form of a hyperlink that allows user to link to the source of the content. In some

embodiments, users may select the social media sources that will be monitored. Users may also provide specific areas to monitor and may provide search criteria. For example, a user may decide to delete industry risk news and substitute industry risk news section 2318 with a risk section relating to a newly released product. The user may provide search criteria for the newly released product.

[00254] Portal screenshot 2300 may also include a graph section 2324 that illustrates counts of mentions of the news events by a number of social media sources over a predetermined time period. Graph section 2324 shows relative numbers of mentions by a number of social media sources for three events, Event A, Event B and Event C. The events may include, in some examples, natural disasters, company boycotts or any other types of events that represent risks to business entities.

[00255] FIG. 29A illustrates an integrated pipeline dashboard interface 2900 for reviewing information regarding opportunities. Opportunities, in some examples, can include renewal opportunities, cross sale opportunities, and new sale opportunities. A pipeline pane 2902 includes two bar graphs 2914 presenting individual upcoming opportunities along a timeline 2916. A cross opportunities pane 2904 presents a bar graph representing total value of cross sale opportunities available to the user based upon a present client (e.g., purchaser, subscriber, etc.) base. An ROI tracker pane 2906 presents overview metrics corresponding to activities coordinated through the interest registration feature of the dashboard environment. A premium pane 2908 presents a graphic representation of the present participant's portion of the full transactional "book" of the dashboard environment. An opportunities overview pane 2910 includes an opportunities lifecycle overview funnel chart illustrating stages of opportunity negotiation. A broker survey pane 2912 presents response data obtained through providing survey questions to clients or customers of the present participant.

[00256] In some embodiments, the information presented within the various panes of the integrated pipeline dashboard interface 2900 may be filtered using a set of filter controls 2922. As illustrated, the filter controls include a product control used to filter according to one or more product names or product categories, an industry control used to filter according to one or more client industries, and a more filters control used to filter according to other categories such as, in some examples, geographical region (e.g., continent, country, state, or other municipality or geographic region of the client), timeframe (e.g., as referenced in a timeline 2916 of the pipeline pane 2902), deal size (e.g., only those opportunities meeting or exceeding a set remittance value, or opportunities within a range of remittance values), transaction count (e.g., only those opportunities associated with dashboard environment clients who have placed a certain number of transactions or hold a certain number of subscriptions or policies presently through the dashboard environment), transaction value (e.g., only those opportunities associated with dashboard environment clients who have placed a certain remittance value of transactions through the dashboard environment), or incumbency (e.g., only those entity participants that are currently clients of the present participant). Further filter options can include, in some examples, a participant office filter (e.g., identifying a particular geographic office of the present participant), a membership filter (e.g., in relation to health and benefits insurance), and a package name filter. In some embodiments, two or more filters may be set concurrently. For example, as illustrated, both a product filter 2922b and an industry filter 2922c may be set.

[00257] In some implementations, filter information may be set using a filter settings interface 2930 as illustrated in FIG. 29B. For example, upon selection of a more filters filter control 2922a of FIG. 29 A, the user may be presented with the filter settings interface 2930 of FIG. 29B. Turning to FIG. 29B, the filter settings interface 2930 includes a collection of filter controls for filtering information presented within dashboard interfaces such as the integrated pipeline dashboard interface 2900 of FIG. 29 A. Upon finalizing selections within the filter settings interface 2930, the user may select a "show dashboard" control 2948 to return to a most recent dashboard user interface.

[00258] In some implementations, the filter settings interface 2930 includes "policy effective date" controls 2932 (e.g., pertaining to a date of renewal of an existing policy and/or a date of a client's interest in pursuing a new transaction such as insurance coverage of a business that is currently pending purchase). Although illustrated as a series of drop-down menus, in other implementations, a calendar selection widget, end date selection widget (e.g., starting at present day), or other control may be provided within the filter settings interface 2930. In the circumstance of filter settings which are maintained by the dashboard environment (e.g., automatically applied upon subsequent access to a dashboard interface such as the integrated pipeline dashboard interface 2900 of FIG. 29A), the policy effective date controls 2932 may be used to set a rolling time period beginning at present date or start of a time period including the present date, such as a number of months, one year, etc. For example, using the third drop-down menu of the policy effective date controls 2932, a full year setting is illustrated. Upon selection of "full year", for example, the first two policy effective date controls 2932 may illustrate a date range based upon a present date or the first of the month of the present month (e.g., "Apr 1 2014" and "Mar 31 2015" as illustrated).

[00259] In some implementations, the filter settings interface 2930 includes currency controls 2934 for setting a currency used in presenting remittance values within dashboard interfaces such as the integrated pipeline dashboard interface 2900 of FIG. 29 A. As illustrated, the currency controls 2934 include a United States dollars control 2934a, a European Union euros control 2934b, and a United Kingdom pound control 2934c. Other currency controls are possible, depending upon the geographic reach of a particular embodiment of the dashboard environment. Currency, in other embodiments, may default to a currency used within a region associated with the present user or participant. For example, a user profile may include a geographical location associated with the user. [00260] The filter settings interface 2930, in some implementations, includes a deal size control 2936 for selecting a remittance value range for transactions and/or transaction opportunities presented within a dashboard interface such as the integrated pipeline dashboard interface 2900 of FIG. 29A. As illustrated, the deal size control 2936 may be implemented as a slide control for establishing a minimum deal size and (optionally) a maximum deal size. The deal size, for example, may correspond to the currency selected via the currency controls 2934. As illustrated, the deal size control 2936 ranges from a minimum of 10,000 to an unlimited maximum value.

[00261] In some implementations, the filter settings interface 2930 includes geographical controls 2938 for selecting one or more geographic regions. As illustrated, geographical regions selected via the geographical controls 2938 include the Americas 2938a, Europe, Middle East, and Africa (EMEA) 2938b, and Asia Pacific (APAC) 2938c. While the geographical controls 2938 present multi-country regions, in other embodiments, the geographical controls 2938 may be used to select individual countries, geographic regions within the countries (e.g., the New England region of the United States, the Manitoba province of Canada, etc.), individual states, and/or other geographical regions. The geographic regions may correspond to regions where clients are situated (e.g., region of incorporation, region of place of business). In another example, the geographic regions may correspond to regions where transaction-related items are located. For example, the region may correspond to the location of a business insured via a policy placed through the dashboard environment or the location of a brokerage involved in placing the transaction. Further, in the circumstance of reinsurance, the geographic region may correspond to the location of the cedent. Application of the geographic region may depend, for example, upon the particular type of present participant and/or a type of dashboard interface associated with entry into the filter settings interface 2930.

[00262] In some implementations, the filter settings interface 2930 includes product controls 2940 for selecting one or more products. The products, for example, may include those products offered by the present participant via the dashboard environment. In some examples, insurance type products may include (as illustrated) property 2940a, financial lines 3940b, and casualty/liability 2940c. The product controls 2940, as illustrated, further include an expansion control 2940d for selecting additional product types.

[00263] The filter settings interface 2930, in some implementations, includes industry controls 2942 for selecting one or more client industries, such as an industry name, ARS industry group, and/or primary Standard Industrial Classification (SIC) code. The industries, as illustrated, may include a manufacturing industry 2942a, a financial institution industry 2942b, and an environmental industry 2942c. The industry controls 2942 include an expansion control 2942d for selecting additional industries. Rather than industries, in other implementations, the filter settings interface 2930 may include a business lines control. For example, in the circumstance of reinsurance, the reinsurance industry participant may be interested in industry participants dealing in particular business lines.

[00264] In some implementations, the filter settings interface 2930 includes client sales controls 2944. The client sales controls 2944 may relate to a total transaction value associated with each client. For example, a user may select the client sales controls 2944 to filter presented transactions and/or transaction opportunities for those opportunities associated with dashboard environment clients who have placed a certain remittance value of transactions through the dashboard environment. Alternatively, the client sales controls 2944 may apply to those dashboard environment clients who have placed a certain remittance value of transactions with the present participant. The remittance values, for example, may be presented in the currency selected via the currency controls 2934. Rather than or in addition to the client sales controls 2944, in some embodiments, the filter settings interface 2930 may include one or more transaction count controls for filtering by only those clients who have placed a threshold number of transactions via the dashboard environment and/or with the present participant.

[00265] The filter settings interface 2930, in some implementations, includes incumbency status controls 2946 for narrowing presented transactions and/or transaction opportunities by incumbent clients (e.g., only those entity participants that are currently clients of the present participant) or non-incumbent clients (e.g., only those entity participants that are not currently clients of the present participant).

[00266] Returning to FIG. 29A, beneath the filter controls 2922, a set of premium component filter controls 2924 provide the user with account category filtering options for filtering presented metrics by account categories representing sources of remittance, for example within one or more selected geographic regions. The account category filter controls 2924 include a structured portfolio solution (SPS) control 2924a (illustrated as selected), a "to be marketed" control 2924b, and a global insurance control 2924c. In other embodiments, the account category filters 2924 may include, in some examples, a direct premium component control and an invoiced premium component control. In further embodiments, the account category filters 2924 may include controls directed towards different types of products such as, in some examples, reinsurance products, other subscription products, and/or service contracts. Each category of account, in this example, would include filters specific to the particular type of product.

[00267] Turning to the pipeline pane 2902, a premiums view pipeline graph 2914a illustrates upcoming opportunities by amount of potential remittance, and a count view pipeline graph 2914b illustrates upcoming opportunities by total number of opportunities on a given date or date range of the timeline 2916. The timeline 2916, as illustrated, covers a three month timespan between February 10 and May 10. The "more filters" filter control 2922a, for example, may be used to set a timeframe of the timeline 2916. The timeline 2916 can cover a shorter or longer period, for example by selecting a timespan control 2952 (as illustrated in FIG. 29C including zoom, 1 month, 3 months, 5 months, year to date (YTD), 1 year, and all).

[00268] In some implementations, a user associated with a particular participant (e.g., industry participant, reinsurance industry participant, or intermediate participant), such as a particular insurance agency, may append one or more notes to a particular opportunity or otherwise highlight the opportunity for the attention of one or more colleagues. For example, an industry participant branch team member may draw attention to opportunities and/or share notes regarding opportunities with additional team members through the pipeline pane 2902. In a particular example, a team member may highlight a particular opportunity for attention, and the corresponding bar of the pipeline graph 2914a and/or 2914b may be rendered differently to alert other team members to review the highlighted opportunity. As illustrated in FIG. 29C, a particular bar 2954 is rendered in a different color (e.g., orange rather than blue). In other examples, the bar 2954 corresponding to the highlighted opportunity may be outlined, patterned, or shaded one or more colors to highlight the opportunity. In a further example, the bar 2954 corresponding to the highlighted opportunity may be presented in a different shape (e.g., zig-zagged or rounded) to draw attention to the opportunity.

[00269] Further, if a team member appended a note regarding the highlighted opportunity, in some implementations an icon 2918 (illustrated as a dialog box) is presented adjacent to or overlapping the bar 2954. The icon 2918, for example, may include a synopsis, portion, and/or count of any notes appended to the highlighted opportunity (illustrated as reading "5 Notes"). Rather than being immediately presented to the user upon accessing the integrated pipeline dashboard interface 2900, the icon 2918 may be presented upon selection or mouseover of the bar 2954 corresponding to the highlighted opportunity. In other embodiments, the icon 2918 may be presented as a count (e.g., digit superimposed or adjacent to the bar 2954 corresponding to the highlighted opportunity) or a pop-up dialog box. [00270] In some implementations, upon mouse-over or selection of the bar 2954, any notes associated with the highlighted opportunity are presented in a notes region 2920 of the pipeline pane 2902. The bar graphs 2914, for example, may be compressed and/or the timeline 2916 shortened to provide space for the notes region 2920 of the pipeline pane 2902. Turning to a pipeline pane view 2950 of FIG. 29C, as illustrated, the notes region 2920 includes category headers 2956, and the notes are presented under corresponding categories 2956. The category headers 2956 include a "registration of interest" header 2956a (e.g., corresponding to an interest tracker feature), a "renewal" header 2956b (e.g., corresponding to subscription renewals such as a term subscription, insurance plan, or service contract), and a "new new" header 2956c (e.g., corresponding to participants recently added to the dashboard environment). Each note under one of the category headers 2956 includes an entity name, a participant name, and a date. In further implementations, upon mouse-over or selection of a particular bar of one of the bar graphs 2914, a listing of opportunities is presented within the notes region 2920. Similar to the listing of notes, the listing of opportunities may be presented under the category headers 2956.

[00271] In some implementations, notes are added to the dashboard environment via a detailed report interface such as the pipeline detailed report 2120 illustrated in FIG. 21B or the opportunities detail report illustrated in the screenshot 2160 of FIG. 21D. The report, for example, may include one or more columns for adding note information such as, in some examples, a note type column, a note description column, and a note sharing column. The note description column, for example, may provide the user with a text entry field for adding brief information related to the selected pipeline opportunity. The user may further select a type of note, such as an interest registration, renewal, cross opportunity, new business, or other (miscellaneous). In some embodiments, the type of note defaults to a type of report requested by the user. For example, if a note is entered via the opportunities detail report, related to interest tracking, the note type may default to an interest registration type.

[00272] In some implementations, the note addition feature is accessible to only certain users, such as users having a particular role (e.g., region leads, relationship managers, and other managerial or decision-making roles). Further, the note feature may be limited to those participants (or subset of users associated therewith) having a particular access level, such as a paid service level or subscription level with the dashboard environment. Even if note addition is limited to certain users, other users associated with the same participant may be authorized to review notes added. For example, the user adding the note may identify one or more users, a user demographic (e.g., users identified as being part of the office in region "A"), and/or a user role (e.g., all relationship managers, etc.) as authorized reviewers (e.g., in a note sharing column of the note adding user interface). If not limited by the user, the added note may be accessible to all users associated with the same participant. Upon sharing or saving a note, the note may become accessible to other users reviewing pipeline information (e.g., via the integrated pipeline dashboard interface 2900 of FIG. 29 A or other pipeline dashboard interfaces such as those described in relation to FIGS. 21 A through 21D).

[00273] Although described above in relation to a single highlighted bar 2954, in some implementations, a user may select two or more bars for review in one of the bar graphs 2914. In some examples, a user may drag across multiple bars, consecutively select (e.g., "click" upon) multiple bars, or hold the control key while selecting multiple bars. Rather than presenting note information upon selection of multiple bars, in other implementations, selection of multiple bars of one of the bar graphs 2914 results in presentation, to the user, of a pipeline detail report including the timeframe of the selected bars, such as the pipeline detailed report 2120 illustrated in FIG. 21B or the opportunities detail report illustrated in the screenshot 2160 of FIG. 2 ID.

[00274] The cross opportunities pane 2904 of FIG. 20 A presents a bar graph illustrating potential benefits of exploring opportunities based upon established relationships. Turning to FIG. 29D, bars 2962 of the bar graph, as illustrated, represent a total current remittance value (e.g., total premium) for the present participant 2962a (e.g., industry participant or intermediate participant), a total remittance value for the clients of the present participant 2962b (e.g., including all transactions made through the dashboard environment by the client base of the present participant), and a total remittance value for potential new clients of the present participant 2962c (e.g., based upon interest expressed by the present participant in renewal opportunities or new business opportunities with clients that are not currently doing business with the present participant). Although described in relation to a client such as an entity participant, in other implementations, an industry participant may be presented with metrics related to cross opportunities involving intermediate participant relationships (e.g., total remittance value placed by intermediate participants on behalf of the present industry participant, total remittance value placed by intermediate participants that have a relationship with the present industry participant, total remittance value placed by intermediate participants that do not have a relationship with the present industry participant). In further implementations, a reinsurance industry participant may be presented with metrics related to cross opportunities involving industry participant relationships (e.g., total remittance value of transactions between the present reinsurance industry participant and its cedents, total remittance value ceded by industry participants that have a cedent relationship with the present reinsurance industry participant, total remittance value ceded by industry participants that do not have a relationship with the present reinsurance industry participant).

[00275] In other implementations, rather than illustrating total remittance values for current and potential new clients, the bar graph presented in the cross opportunities pane 2904 may illustrate a total remittance value for a set (e.g., 3, 4, 5, etc.) of current clients of the present participant for transactions involving participants of the dashboard environment than the present participant. The current clients, for example, may include top clients of the present participant by total remittance value obtained by the present participant or top clients of the present participant by total remittance value obtained by any participant via the dashboard environment.

[00276] In some implementations, upon selection of a bar 2962 of the bar graph presented within the cross opportunities pane 2904, the user is presented with a list of cross

opportunities 2964. The list of cross opportunities 2964, for example, may include a series of records 2966 each identifying a particular client 2966a, a client industry 2966b, and a number of opportunities 2966c (e.g., new new business opportunities, renewal opportunities, and/or other cross opportunities). Each record 2966 of the list of cross opportunities 2964 may further include a review new business control 2966d (e.g., illustrated as a selection box). When reviewing select business opportunities, for example, the user may activate one or more of the review new business controls 2966d of the list of cross opportunities 2964, and select a review control 2968 to generate a report of the selected cross opportunities. The report, for example, may involve information similar to the screen shot 2160 of FIG. 2 ID in which records illustrate details of client name, product, policy expiration date, client industry, and deal size.

[00277] In some implementation, a user may select a viewpoint control 2967 to alter a viewpoint of the information presented within the list of cross opportunities 2964. For example, presently the viewpoint is set to client via the viewpoint control 2967. Additional viewpoints selectable via the viewpoint control 2967, in some examples, may include an intermediate participant (e.g., broker) viewpoint or an office viewpoint.

[00278] In other implementations, the cross opportunities pane 2904 of FIG. 29 A presents a cross opportunities metrics comparison such as the cross opportunities comparison view 2970 of FIG. 29E. Turning to FIG. 29E, comparisons are presented between a system total metric 2972a (e.g., all similar participants within the dashboard environment), a participant A metric 2972b (e.g., the present participant), and a peer average metric 2972c (e.g., based upon selected participants identified as peers of the present participant) in a series of bar charts presented in both a remittance value (e.g., premiums ranging from $0M to $100M) analysis column 2974a and a transaction count (e.g., plans ranging from 0 to 100) analysis column 2974b. The cross opportunities comparison view 2970 further includes three rows 2976 of metrics, including a "clients with >=3 products" row 2976a, a "clients with 2 products" row 2976b, and a "clients with 1 product" row 2976c. The product ranges represented by the rows 2976, for example, may be appropriate in the circumstance of health and benefits insurance, where clients typically do not purchase a large number of products. In reviewing the cross opportunities comparison view 2970, for example, a user may identify that, in comparison with peer averages, participant A is successful in marketing a third product to existing clients (e.g., in comparing relative lengths of the peer average 2972c bars from row 2976b to row 2976b with relative lengths of the participant A 2972b bars from the same rows 2976).

[00279] In some implementations, the metrics presented within the cross opportunities comparison view 2970 may be filtered by industry using an industry filter control 2978. In other implementations, additional filtering options may be presented, such as geography and deal size. The filtering options, in one example, may be set via the filter settings interface 2930 of FIG. 29B.

[00280] Returning to FIG. 29A, beneath the cross opportunities pane 2904, the registration of interest (ROI) tracker pane 2906 presents a waterfall graph of transactional stages between parties brought together through the interest registration feature of the dashboard interface. The waterfall graph, for example, may present aggregate metrics similar to the waterfall graph described in relation to screenshot 2140 of FIG. 21C. For example, upon selection of a portion of the ROI tracker pane 2906, the user may be presented with the detailed interface described in relation to screenshot 2160 of FIG. 2 ID.

[00281] Beneath the ROI tracker pane 2906, a premium overview pane 2908 presents a graphic representation of the present participant's portion of the full transactional "book" of the dashboard environment. As shown in the premium overview pane 2908, the comparison is illustrated as a doughnut graph with a total remittance value (premium) associated with the present participant presented in the center of the doughnut. The total remittance value of the dashboard environment, for example, may be tailored to the type business transacted by the present participant (e.g., reinsurance in particular markets, etc.).

[00282] Upon selecting a portion of the premium pane 2908, such as clicking upon the doughnut graph, in some implementations, the user is presented with a premium overview dashboard 2980. Turning to FIG. 29F, the dashboard 2980 includes a market position pane 2982, a remittance value trend pane 2984, and a remittance value detail pane 2986. The metrics presented in panes 2982, 2984, and 2986 are filtered by the applied filters 2922, described in relation to FIG. 29A. The filters 2922, for example, may have been set by the user via the filter settings interface 2930 of FIG. 29B. Additionally, the metrics presented in panes 2982, 2984, and 2986 are filtered by the premium component filter controls 2924 described in relation to FIG. 29A.

[00283] The market position pane 2982 presents a bar graph comparing aggregate remittance values 2990 (e.g., premium values) of peers 2988 of the present participant to aggregate remittance value of the present participant. Although illustrated as representing nine peers 2988 as well as the present participant, in other implementations more or fewer peers 2988 may be illustrated. The peers 2988, as noted earlier, are rendered anonymously to protect individual data representations. Peer selection is described, for example, in relation to the dashboard 100 of FIG. 1A. As illustrated, the present participant and the peer participants 2988 are arranged in order of "market position" where the peer participant 2988 with the largest aggregate remittance value is presented at the top of the bar graph and the peer participant 2988 with the lowest aggregate remittance value is presented at the bottom of the bar graph.

[00284] Beneath the market position pane 2982, the remittance value trend pane 2984 presents line graphs of participant aggregate remittance value per time period (e.g., month) for the present participant in comparison to selected (e.g., top five, as illustrated) peers 2988 of the present participant. A line graph 2992, presented in bold with points representing the time periods, illustrates the aggregate remittance trend of the present participant. In some implementations, the points of the line graph 2992 are selectable to present detailed information regarding remittance flow during a selected time period. For example, the detailed information may be presented within the remittance value detail pane 2986.

[00285] The remittance value detail pane 2986, in some implementations, presents a table of client transactions (e.g., insurance policies) along with additional client information. As illustrated, the records presented within the remittance value detail pane 2986 present client name, line of business, effective date, expiration date, risk description, carrier declination reason, and deal size. The records, in some implementations, may be arranged in alphabetical order based upon a selected field (e.g., column). In the illustrated embodiment, the records are arranged in order of declination reason. The declination reason, for example, may be used to demonstrate reasons behind opportunities which the present participant declined to quote. Further, arrangement by declination reason may provide the present participant with an understanding of what types of opportunities are not being pursued as well as why.

[00286] Returning to FIG. 29 A, a pane 2910 illustrates an opportunities lifecycle overview funnel chart 2928 including three stages 2928a through 2928c of opportunity negotiation, along with a total remittance value associated with deals at each stage. In the example of a broker participant, the lifecycle overview funnel chart 2928 may represent stages of the broking process, such as underwriting, post-placement, and claims. Selection of one of the three stages 2928a through 2928c, in one example, may result in presentation of metrics specific to that stage. For example, upon selection of an underwriting stage 2928, the user may be presented with the bar graph described in relation to FIG. 20B, presenting a comparison between performance of the present industry participant during the underwriting stage of the broking process and performance of select peer competitors during the underwriting stage. In an example involving an insurance carrier industry participant, the opportunities lifecycle overview funnel chart 2928 may represent stages of an insurance product transaction, such as a pending stage, a submitted stage, a quoted stage, and a bound stage. In this example, following selection of a bound stage 2928, the present participant may be presented with detailed metrics such as the bar graph of aggregate trades and bound premium illustrated in FIG. 12. Further to the example, following selection of a quote stage 2928, the present participant may be presented with detailed quote metrics such as the bar graph of submit-to-quote ratios illustrated in FIG. 13.

[00287] Returning to FIG. 29 A, the survey results pane 2912 presents response data obtained through providing survey questions to clients or customers of the present participant. For example, in the example of an insurance industry participant, the survey results may include information obtained from a number of brokers that have done business with the present participant. The survey results pane 2912, for example, may include a thumbnail image of survey results or a brief overview of survey results related to the present participant. Further, in some implementations, the survey results may include comparison metrics related to survey results of one or more peers of the present participant. Survey results are discussed in greater detail in relation to FIGS. 20A, 25E, and 25F. Additional survey result layouts are illustrated in FIGS. 31 A and 31C.

[00288] Turning to FIG. 31 A, a survey metrics comparison interface 3100 provides a quick comparison between present participant metrics 3102, peer average metrics 3104, and a relative trend 3106 of changes in metrics of the present participant as compared to changes in peer average metric values. The comparisons are supplied over a number of metric types 3108 through 3116, including an overall performance metric 3110, a set of overall relationship metrics 3110, a set of underwriting metrics 3112, a post-placement service metric 3114, and a claims performance metric 3116.

[00289] The present participant metrics 3102 are illustrated for a first time period 3102a (e.g., May 2013), a second time period 3102b (e.g., October 2013), and a percent change 3102c in the most recent metric (e.g., October 2013) as opposed to the earlier (e.g., May 2013) metric. Additionally, a trend icon 3102d illustrates a direction of change of the metric between the first time period 3102a and the second time period 3102b. The trend icon 3102d, for example, may be illustrated as one of the icon styles 3124 illustrated in a trend

presentation formatting pane 3120 of FIG. 3 IB.

[00290] Turning to FIG. 3 IB, the trend presentation formatting pane 3120 provides the user with a selection of formatting styles 3122 as well as icon styles 3124 associated with a selected formatting style 3122. As illustrated "icon sets" is selected as the formatting style 3122, and the icon styles 3124 selected include a downward red arrow 3130e, a lower right yellow arrow 3130d, a right yellow arrow 3130c, an upward right arrow 3130b, and an upward green arrow 3130a. A reverse icon order control 3126, when selected, causes reversal of presentation of the icon controls 3130. Although illustrated as a set of five icons 3130, in some embodiments, more or fewer icons may be selected. For example, a user may opt to set three icons 3130 to identify positive, neutral, and negative movements in metric trends.

[00291] For each of the icons 3130a through 3130d, in some implementations, the user may set an associated threshold value for presenting the particular icon 3130 using the trend presentation formatting pane 3120. The threshold value, for example, is based upon a comparator 3132 (e.g., illustrated as ">="), a value 3134 (e.g., illustrated as a numeric value ranging from -1 to 2), and a value type (e.g., illustrated as "number"). In this manner, based upon volatility, marketing expectations, or typical trends within survey performance of the present participant, a user may set values 3134 for each icon 3130 to capture appropriate presentation (e.g., when trends are strongly improved as designated by upward green arrow 3130a as compared to trends which are somewhat improved as designated by the upward right yellow arrow 3130b, etc.). As illustrated, with all other icons 3130a through 3130d set to value ranges, icon 3130e receives a default value. Upon selection of the reverse icon order control 3126, instead of a default negative range, the user may select values for icons 3130b through 3130e, with icon 3130a receiving a default value. [00292] Rather than selecting icon sets 3122 and arrow icon styles 3124, in some implementations, the user may format survey trends information interfaces to have color coded metric presentations. For example, as illustrated in FIG. 31C, strongly improving trends may be designated by a green-filled box of a line of business (LOB) metrics comparison interface 3140, while strongly worsening trends may be designated by a red- filled box. In other examples, trends may be visually represented using shadings,

highlighting, bold font, other arrow styles, varying facial expressions (e.g., on a "smiley face" type icon), and/or flags (such as the flags illustrated in FIG. 31C).

[00293] Returning to FIG. 31 A, similar to the present participant metrics 3102, peer average metrics 3104 are illustrated for a first time period 3104a (e.g., May 2013), a second time period 3104b (e.g., October 2013), and a percent change 3104c in the most recent metric (e.g., October 2013) as opposed to the earlier (e.g., May 2013) metric. Additionally, a trend icon 3104d illustrates a direction of change of the peer average metric between the first time period 3104a and the second time period 3104b. The user, for example, may review the present participant metrics 3102 in light of the peer average metrics 3104 to gauge how well the present participant is faring in relation to peer participants.

[00294] Additionally, in some implementations, the relative trend 3106 column of the survey metrics comparison interface 3100 provides a set of icons identifying relative changes in metrics of the present participant as compared to changes in peer average metric values for each of the metrics 3108 through 3116. In this manner, the user may quickly identify areas of relative strength (e.g., understanding of value proposition 3110a, speed of underwriting process 3112c, price competitiveness 3112d, etc.) as well as areas needing improvement (e.g., reliable and trustworthy staff 3110b, breadth and flexibility of coverage terms3112a).

[00295] FIG. 31C illustrates a line of business (LOB) metrics comparison interface 3140 presenting a comparison of metrics 3144 through 3148 across a collection of lines of business 3142 of a particular present participant. The results presented in the LOB metrics

comparison interface 3140 are based upon aggregate survey responses 3150. As illustrated, the survey posed questions related to a net promotor score 3144, such as overall relationship questions, underwriting questions, post-placement questions, and claims questions. The outcome of the questions presented in the survey, in average, provides the overall

performance score 3146, while the net promotor score 3144 presents an excess of promoters (positive responses) over detractors (negative responses).

[00296] In some implementations, in addition to presenting metrics associated with the present participant, the LOB metrics comparison interface 3140 is used to present a comparison of the present participant's survey results to peer survey results. Turning to FIG. 3 ID, a graphic key 3160 correlates a green shading 3162a to a metric which is over five percent better than a peer average and a red shading 3162b to a metric which is over five percent worse than a peer average. Turning to FIG. 31C, for example, metrics shaded green include automotive line of business metrics 3142b related to overall performance 3146 as well as a portion of attribute performance metric 3148. Conversely, the overall performance metric 3146 related to the agribusiness line of business metrics 3142a, as well as a number of attribute performance metrics 3148, are shaded red, demonstrating that the present participant is receiving survey results that are over five percent worse than peer average in these areas.

[00297] In addition to relative performance, the graphic key 3160 correlates a green flag 3164a with identification of a "best in class" rating and a red flag 3164b with identification of a "worst in class" rating. The "class" referred to within the graphic key 3160, for example, may pertain to a ranking of the present participant in relation to the peers used to generate the peer average metrics. As illustrated in FIG. 31C, the present participant is "best in class" in "product industry/expertise" 3148e in the automotive line of business 3142b. Further, the present participant is "worst in class" in net promotor score 3144 in the agribusiness line of business 3142a.

[00298] Similar to the survey interface 3140 of FIG. 31C, FIG. 3 IE illustrates an example international survey interface 3170 presenting metrics related to international broking activities. The international survey interface 3170 presents both inward metrics 3172a and outward metrics 3172b, where individual metrics are presented on a per-industry participant or per-line of business basis, depending upon a type of international survey report requested by the user. On both the inward metrics 3172a side and the outward metrics 3172b side, an overall performance metric 3174 is presented. Additional metrics are significant based upon the direction of viewpoint (inward or outward). Turning to the inward metrics 3172a, the international survey interface 3170 presents an accuracy of policies metric 3176a, an accuracy of invoices metric 3176b, a speed of policies metric 3176c, a speed of invoices metric 3176d, and a speed of inquiry responses metric 3176e. The inward metrics 3172b of the international survey interface 3170 include a multinational program knowledge and authority metric 3178a, an accurate and complete program implementation metric 3178b, a timely program implementation metric 3178c, and a detailed and efficient premium collection and reporting metric 3178d. As with the survey interface 3140 of FIG. 31C, the international survey interface 3170 includes color-coded shading such as the shading described in relation to the key 3160 of FIG. 3 ID. [00299] FIG. 32 illustrates a flow chart of a method 3200 for collecting, preparing, and distributing survey data regarding relationships between subject participants (e.g., industry participants, intermediate participants, etc.) and survey recipient participants (e.g., participants which are clients, customers, or business representatives of a respective subject participant). The method 3200, for example, may be used to collect information and prepare metrics for presentation within the survey result layouts of FIGS. 31 A and 31C.

[00300] In some implementations, the method 3200 begins with distributing a survey to recipient participants eliciting feedback regarding subject participants (3202). Requests for survey feedback, for example, may be distributed to recipient participants on a periodic basis such as, in some examples, annually, bi-annually, or quarterly. The survey may be distributed via a messaging service of the dashboard environment or other electronic communication, such as email. Survey distribution may be targeted to intermediate participants that have worked with a particular industry participant. Recipients of the survey, in some examples, may include affiliates of each recipient participant having a particular role or set of roles. In a particular example, the survey requests may be distributed to chief broking officers in each geographic region covered by a particular brokerage intermediate participant. The survey request may include a selectable control, such as a HTML link within an email, to access a computer-based survey. In other embodiments, one or more survey recipients may receive paper-based survey forms. For example, the survey recipients may fill in the survey form and mail or fax the survey form back to the requestor (e.g., management group of the dashboard environment). In the event that the intermediate participant has worked with a number of industry participants, the intermediate participant may receive multiple survey requests, one associated with each industry participant.

[00301] In some implementations, survey data is collected from client computing devices associated with the recipient participants (3204). The survey may include a series of questions developed for calculating feedback scores related to aspects of the relationship between the recipient participant and the subject participant with response options designed for aggregation, weighting, or otherwise combining to develop meaningful comparisons between past performance and present performance of the subject participant and/or meaningful comparisons between performance of the subject participant and peer participants of the subject participant. In some examples, the survey may include multiple choice, numeric, and/or sliding scale response options available, via selectable controls, for submission by the respective recipient participant. As illustrated in FIGS. 31 A and 31C, the questions may relate to subject participant staff, responsiveness, underwriting, post- placement service, and claims. The recipient participant, in some embodiments, is requested to answer the same questions in relation to multiple lines of business, if applicable. For example, for a particular recipient participant that has done business with a subject participant related to both casualty /liability insurance and aviation insurance, the recipient participant may answer the same questions in relation to each line of business.

[00302] In some implementations, each survey data set collected from each recipient participant is mapped to an appropriate geographic region and subject participant identity within a database (3206). In some embodiments, a particular subject participant has an affiliation with only one country or other geographic region. If so, the geographic region may be entered based upon the identified subject participant. If, instead, the particular subject participant is affiliated with two or more geographic regions, a particular geographic region may be identified based upon, for example, a recipient participant, line of business, or other identification relating geographical region to the present survey data. In some embodiments, based upon a selected country of one or more potential countries (or alternatively, another geographical region such as province or grouping of states), a subsidiary of the subject participant (e.g., country or regional office) may be identified as the subject participant identity associated with the survey data set.

[00303] Additionally, the survey data set, in some implementations, is mapped to a particular line of business (3208). If the recipient participant has a relationship with the subject participant in only one line of business, the line of business mapping may be derived from affiliations stored within the dashboard environment. In other embodiments, the line of business may be included as a selection within the survey and/or associated with the particular survey request (e.g., associated with a survey session activated by the recipient participant via the request). In further embodiments, the recipient participant may respond to questions associated with two or more lines of business within a single survey data set. In this example, the survey data set may be divided based upon individual lines of business.

[00304] In some implementations, mapping and completeness of data within the database is verified (3210). In a first example, it may be verified that each subject participant is associated with multiple survey data sets. Survey data sets, in second example, may be verified for each subject participant, for each geographical region in which the respective subject participant does business, and for each line of business in which the subject participant does business. In a further example, for each geographical region and line of business combination applicable to a particular subject participant, a number of survey responses may be verified, The survey results, for example, may only be meaningful upon collection of a threshold number or threshold percentage of survey data sets, such as survey data sets collected from at least four of the recipient participants which have done business with the subject participant within a particular geographic region pertaining to a particular line of business. Further, the survey data sets may be validated for uniqueness, where duplicate submissions by a single recipient participant pertaining to the same relationship with a particular subject participant may be discarded. In a particular example, it is verified that each recipient identifier / subject participant identifier combination is unique (e.g., responder email address and industry participant name). In another example, a total number of present survey response data sets related to a particular subject participant (optionally in combination with line of business and/or geographical region) is compared to a total number of survey response data sets collected in relation to the particular subject participant during a prior survey period. If, for example, the number of response has decreased by a threshold percentage or threshold number, survey requests related to the particular participant may be flagged for follow-up review. Additional verifications, in some examples, may include verifying that subject participants are identified as ASCII strings, that various categories of information pertaining to the subject participant align with valid entries in the database (e.g., lines of business, years of experience, industry segments, etc.) and that each geographic region aligns with a valid geographic region code, such as a three-letter country code.

[00305] Based upon the survey data sets, in some implementations, categorical feedback metrics representing each type of survey question presented are calculated for each line of business of each subject participant (3212). The categorical feedback metrics may be based upon one or more response fields within the survey. Additionally, one or more categorical feedback metrics may represent aggregate feedback metrics of individual feedback metrics with the category. For example, an aggregate underwriting metric could be calculated based upon the underwriting metrics 3148d through 3148g illustrated in FIG. 31C.

[00306] Based upon the categorical feedback metrics, in some implementations, an overall feedback metric is calculated for each line of business of each subject participant (3212). For example, as illustrated in FIG. 31 A, the overall performance rating 3108 may be calculated based upon aggregate survey results. In a particular example, the overall feedback metric may be a Net Promoter Score calculated based upon categorization of each categorical feedback metric as representing an aggregate "promoter" (positive feedback) or an aggregate "detractor" (negative feedback).

[00307] In some implementations, a subject participant survey report is prepared for each subject participant (3216). The subject participant survey report, for example, may include a survey report by geographic region for each subject participant. The subject participant report, for example, may include portions of data presented within the survey interface of FIG. 31 A, such as the carrier metrics 3102 over the metrics 3108 through 3116. Instead of or in addition to the subject participant survey report presented upon a per-geographical region basis, a line of business survey report may be prepared. As illustrated in FIG. 31C, the line of business survey report may include metrics derived on a per-line of business basis. The subject participant survey report may optionally include a peer metrics comparison aspect, as described in relation to FIGS. 31 A and 31C.

[00308] For each subject participant survey report, in some implementations, availability of data for all lines of business of the respective subject participant is verified (3218). In a first example, availability of survey data sets pertaining to each line of business of the subject participant, as known by the dashboard environment, may be verified. In addition to availability of data, in some embodiments, sufficiency of data sets (e.g., threshold response numbers) may be verified for each line of business of the subject participant. If, for example, a particular line of business is underrepresented in survey responses (e.g., less than 10, 20, etc. respondents), metrics corresponding to the underrepresented line(s) of business may be left off of the survey report. For example, the survey report may identify unavailability of adequate survey data corresponding to a particular line of business. In other embodiments, metrics for an underrepresented line of business may be presented with a caveat pertaining to the inadequacy of survey data for an accurate assessment.

[00309] In some implementations, subject participant survey reports are distributed to respective subject participants (3220). The subject participant survey reports, for example, may be electronically distributed within a spreadsheet document, text document, or image document to identified recipients. The recipients, for example, may be identified based upon a role within the subject participant organization. In another example, the subject participant survey reports may be made available via the dashboard environment as a dashboard interface, such as the survey interfaces illustrated in FIGS. 31 A and 31C. Similar to electronic document distribution, access to survey report interfaces may be limited to users having a certain seniority level or role within the subject participant organization. In further embodiments, generalized survey reports (e.g., at a country level) may be publicized for all users of the dashboard interface such that peer participants may review survey results related to competitors on a coarse level of granularity. For example, overall feedback metrics may be published for all subject participants to review. [00310] Although described in relation to a particular series of operations, in other embodiments, the method 3200 may include more or fewer steps. In one example, rather than distributing the survey (3202), survey data may be collected by a third party, such as an industry watchdog agency, and imported (3204) into the dashboard environment. In another example, upon receiving at least a threshold number of responses pertaining to a subject participant or line of business not included within the database, the subject participant or line of business may be added to the database. For example, the method may validate the new subject participant or line of business with the dashboard environment prior to addition to the survey database. Conversely, upon receipt of subject participants not included within the database, the responses may be flagged to investigate whether a name change or corporate merger has affected the identification of a pre-existing subject participant. In further embodiments, one or more of the steps of the method 3200 may be performed in a different order. For example, prior to preparing subject participant survey reports (3216), the method 3200 may verify availability of data for all lines of business of each subject participant (3218). Further modifications of the method 3200 are possible.

[00311] Returning to FIG. 29A, a news feed 2926, in some implementations, presents information of interest to the reviewing participant or related to the reviewing participant. For example, the news feed 2926 may present information related to industry risk news 2318, reputation risk news 2320, and/or supply chain risk news 2322, described in relation to FIG. 23. In other embodiments, the news feed 2926 may provide updates to the reviewing participant related to recently added features and/or recently updated data available through the dashboard environment. For example, upon availability of one or more types of reports related to survey results (described, for example, in relation to FIGS. 31 A through 32), the reviewing participant may be alerted to the availability through the news feed 2926. Further, in some embodiments, the news feed 2926 may present third party news relevant to the particular industry of the present participant or updates relevant to the supplier of the dashboard interface. Scrolling news headlines, for example, may be selectable by the present participant from the news feed 2926 to obtain a more complete description, article, demonstration of a new dashboard interface feature, etc.

[00312] Turning to FIG. 30A, an example marketing activity dashboard interface 3000 presents various metrics regarding declined opportunities and successful (e.g., transacted) opportunities between a present participant and other participants of the dashboard environment (e.g., entity participants, intermediate participants, or industry participants). The marketing activity dashboard interface 3000 includes a market activity pane 3002, a market comparison pane 3004, an opportunity survey pane 3006, and an opportunity detail pane 3008. The metrics presented in panes 3002, 3004, 3006, and 3008 may be filtered by the applied filters 2922, described in relation to FIG. 29A. The filters 2922, for example, may have been set by the user via the filter settings interface 2930 of FIG. 29B. Additionally, the metrics presented in panes 2982, 2984, and 2986 may be filtered by the premium component filter controls 2924 described in relation to FIG. 29A.

[00313] Turning to the market activity pane 3002, in some implementations, three shaded areas 3010 of the marketing activity graph illustrate aggregate submissions 3010a, aggregate quotes 3010b, and aggregate hits 3010c (e.g., completed transactions) associated with the present participant. The narrower the spread between the aggregate submissions 3010a and the aggregate hits 3010c, for example, the more successful the marketing activities for the period of time. As illustrated, the marketing activity graph is presented over a range of months (1 through 12) and an aggregate count (e.g., total number of submissions, quotes, and/or hits) per time. The timeframe, for example, may be selected via a filtering option as discussed above in relation to FIG. 29A.

[00314] Upon clicking one of the shaded areas 3010 of the marketing activity graph, in some implementations, the user may be presented with both opportunity survey results related to the selected shaded area 3010 in the opportunity survey pane 3006 and a detailed analysis of the survey results related to the selected shaded area 3010 in the opportunity detail pane 3008. In the example of a present participant which is an industry participant, a portion of the aggregate submissions 3010a failed to lead to aggregate quotes 3010b for reasons that may be expressed as industry participant declination reasons (e.g., reasons the present participant failed to pursue the opportunity). Example industry participant declination reasons are illustrated and described in relation to FIGS. 19A and 19B. An alternative layout of industry participant declination reasons is illustrated in screenshot 3030 of FIG. 30C. In another example, a portion of the aggregate quotes 3010b failed to lead to aggregate hits 3010c for reasons that may be expressed as entity participant declination reasons (e.g., reasons individual declining entity participants gave for declining a quote provided by the present participant). Example entity participant declination reasons are illustrated and described in relation to FIG. 19C. In a final example, the aggregate hits 3010c succeeded in completed transactions for reasons that may be expressed as win reasons. Example win reasons are illustrated in a bar graph 3020 of FIG. 30B. The bar graph 3020, for example, may be presented within the opportunity survey pane 3006 upon selection of the aggregate hits region 3010c. [00315] Turning to FIG. 30B, the bar graph 3020 includes the following reasons (each reason being a separate bar of the bar graph 3020): incumbent relationship with the industry participant 3022a, financial strength of the industry participant 3022b, structured portfolio solution 3022c, favorable coverage terms 3022d, and pricing 3022e. As illustrated, the most prevalent reason for the resent participant's success is pricing 3022e.

[00316] Turning to the opportunity detail pane 3008 of FIG. 30A, details corresponding to the topic presented within the opportunity survey pane 3006 (e.g., industry participant declination reasons, entity participant declination reasons, or successful transaction reasons) are presented within a records grid, such as the detailed declination analysis of FIG. 19D. Selection of the opportunity detail pane 3008, for example, may navigate the user to a pop-up window or additional presentation (e.g., web page, browser tab, etc.) illustrating the information in the opportunity detail pane 3008 in an easier to read and easier to navigate format. Further, the user may be provided the opportunity to sort the information (e.g., by particular declination reason, line of business, deal size, etc.) and/or export the information into a spreadsheet application.

[00317] Upon clicking one of the shaded areas 3010 of the marketing activity graph in the marketing activity pane 3002, in some implementations, the user may be presented with a peer metric comparison in the market comparison pane 3004. As illustrated, the market comparison pane 3004 includes a bar graph comparing present participant performance 3012 to average peer participant performance 3014. Additionally, a line graph within the market comparison pane 3004, overlaying the bar graph, illustrates an average performance for the same time period of a top five (industry) participants 3016 of the dashboard environment. Peer selection is described, for example, in relation to the dashboard 100 of FIG. 1A. The average peer performance 3014 may be based upon industry participants most similar to the present participant (e.g., two above in performance and three below in performance pertaining to aggregate remittance values, similar markets, similar product lines, etc.).

Conversely, the top five participants 3016 may include the five participants 3016 of the dashboard environment with the greatest aggregate remittance values. In this manner, the top five participants 3016 and the peer participants 3014 may or may not include one or more identical industry participants.

[00318] FIG. 33 illustrates a financial key metrics report interface 3300 presenting financial metrics and rankings of industry participants of the dashboard environment. The selected industry participants, for example, may include the top N industry participants based upon dashboard environment remittance (e.g., premium) share. A user may review the financial metrics, in some examples, to identify those industry participants having a robust position within the market, and those industry participants which present low risk transactions. The data presented within FIG. 33, for example, represents a combination of transactional and business data and key financial metrics derived through public sources such as stock market reports, financial reporting clearinghouses, and corporate annual reports. In a particular example, at least a portion of the data may be obtained from Bloomberg market data provided by Bloomberg L.P. of New York, NY, market Auction Rate Security (ARS) rating provided, in some examples, by Standard & Poor's of Baltimore, MD or Fitch Ratings provided by Fitch Ratings, Inc. of New York, NY, and Foreign Account Tax Compliance Act (FATCA) compliance data provided by, for example, the Internal Revenue Service (IRS).

[00319] As illustrated in FIG. 33, the financial key metrics report interface 3300 presents key metrics for a series of top industry participants 3302 of the dashboard environment. The metrics include earnings per share 3304, dividend yield 3306, cost of capital 3308, market share 3310, real revenue growth 3312, sustainable revenue growth 3314, operating expenses 3316, earnings before interest, taxes, depreciation, and amortization (EBITDA) 3318, return on assets 3320, gross profit 3322, loss ratio 3324, sales per share 3326, and market capitalization 3328. Each of the key metrics 3304 through 3328, for example, may be obtained from various public sources for financial data.

[00320] In some implementations, for each of the key metrics 3304 through 3328, an average 3330 of the top industry participants 3302 is also presented. The financial key metrics report interface 3300 may include color-coding of metrics based upon the averages 3330. For example, as illustrated, those entries above the respective average 3330 are shaded in blue, while those entries below the respective average 3330 are shaded in red. In other embodiments, a median may be included rather than an average, or additional shading may be provided (e.g., green shading for the top three industry participants 3302 in a given metric 3304 through 3328).

[00321] FIGS. 34A through 34C illustrate example velocity change graphic interfaces demonstrating swings in remittance values between a baseline (e.g., first time period illustrated within the graphic interface) and various points in time upon a timeframe, such as quarters or months. In other embodiments, the baseline may represent a value derived from prior or present remittance value metrics such as, in some examples, an annual or other prior timeframe baseline (average, mean, median, etc.), peer baseline, or dashboard environment participant baseline. The velocity change graphic interfaces, in general, may present percentage remittance value changes for each time period based upon one or more of geography, industry, and product. Further, the velocity change graphic interfaces may present percentage remittance value changes in view of a set of industry participants (e.g., in the example of a reinsurance industry participant). In some embodiments, velocity change graphic interfaces may be used to reflect comparisons in percentage remittance value changes, such as, in some examples, SPS vs. non-SPS, broking center to broking center, and/or global insurance vs. non-global insurance. A user may review the velocity change graphic interfaces to identify areas of rapid growth (e.g., indicating a potential need for additional resources) as well as rapid decline (e.g., indicating a potential need for

improvement efforts). In further embodiments, any of the aforementioned velocity change graphic interfaces may include peer participant comparison metrics. In this manner, for example, trending increases or decreases in remittance values may be differentiated from increases or decreases most attributable to participant success (or shortcoming). Although illustrated as individual velocity change graphic interfaces, in other embodiments, combinations of velocity change graphic layouts may be presented within a single interface to provide greater depth of information on movements within the business of the present participant. Further, a user, in some embodiments, may filter or drill down within a particular velocity change graphic layout to access refined metrics related to the presented information.

[00322] Turning to FIG. 34A, an industry velocity change interface 3400 illustrates percentage movements in remittance values of entity participants classified within certain industries 3402. Line graphs illustrate movement from time period to time period (quarters), while each point (quarter) of a timeline 3404 is identified with a particular percentage value change from a baseline 3406. In a particular example, in an aviation industry 3402b, remittance values were 955% over a baseline 3406b at the second quarter of 2013 and then only 205% over the baseline 3406b at the third quarter of 2013. In comparison, at the third quarter of 2014, the aviation industry 3402b remittance values were 11% under the baseline 3406b. Further, while remittance values of most industries increased to significantly above the baseline 3406 at the fourth quarter of 2013, remittance values in the aviation industry 3402b and an energy industry 3402e sharply declined. In reviewing the percentage values illustrated by the timelines of the industry velocity change interface 3400, a user may recognize that the least volatile industry during the time period 3404 is a construction services industry 3402d (ranging from 396%) above a baseline 3406d to 20% below the baseline 3406d) while a holding company industry 3402j is the most volatile industry during the time period 3404 (ranging from 33247% above a baseline 3406j to 40% below the baseline 3406j). [00323] Turning to FIG. 34B, a product velocity change interface 3410 illustrates percentage movements in remittance values of products 3412 of the present participant. Unlike the line graphs of the industry velocity change interface 3400 of FIG. 34A, the bar graphs of the product velocity change interface 3410 illustrate a particular percentage value change from a baseline 3416 for each point (quarter) of a timeline 3414, while changes from quarter to quarter are identifiable based upon individual bar graph heights as well as the percentage change value label above each bar. For example, in an energy product 3412k, a percentage change associated with the second quarter of 2013 is only 2% from a baseline 3416k, with a barely visible bar, while a percentage change associated with the third quarter of 2013 is 6081% over the baseline 3416k with a tall bar. A user may review the product velocity change interface 3410, for example, to identify product areas exhibiting growth, decline, and/or stability.

[00324] An entity participant annual remittance value velocity change interface 3420 of FIG. 34C illustrates percentage movements in remittance values based upon entity participant bands 3422 of annual remittance values. The bands 3422, for example, separate entity participants which are clients/customers of the present participant by relative size, from an under $5 million band 3422a to an over $1 billion band 3422e. In some embodiments, the present participant may specify two or more bands of remittance values for classifying entity participants. For example, annual remittance value bands may be included in a settings interface similar to the filter settings interface 2930 of FIG 29B.

[00325] Turning to FIG. 34C, line graphs illustrate movement from time period to time period (quarters), while each point (quarter) of a timeline 3424 is identified with a particular percentage value change from a baseline 3426. The line graphs, as illustrated, are relevant to a percentage of total remittance value (total book) upcoming for renewal in a defined period and within a given remittance value band. A user may review the entity participant annual remittance value velocity change interface 3420, for example, to identify client/customer retention trends within the bands 3422. In another example, an increase in percentage value from quarter to quarter may be indicative of success of a cross-sales program. Additionally, the user may review the entity participant annual remittance value velocity change interface 3420 to identify trends in entity participant transactions, thereby identifying periods of time to allocate greater resources to pursuing and completing transactions. For example, the fourth quarter of 2013 demonstrated a sharp increase across most bands 3422, suggesting that attention should be made to annual renewal opportunities within the fourth quarter of the following year. [00326] FIG. 35 illustrates an example scatter bar graph interface 3500 for reviewing transactions by remittance value. The scatter bar graph interface 3500, for example, may be accessible via a control (not illustrated) presented within the integrated pipeline dashboard interface 2900 of FIG. 29A. The interface 3500, in some examples, can provide the user with a sense of which industries and/or products carry a high remittance value concentration, which intermediate participant(s) field a high remittance value concentration, and which entity participant(s) carry a high remittance value concentration. Via the information derived through the scatter bar graph interface 3500, the user may identify product, industry, intermediate participant, and/or entity participant exposure risks.

[00327] Turning to FIG. 35, the scatter bar graph interface 3500 includes a set of filtering controls 3502 for narrowing the presentation of information by remittance value band 3502a, industry 3502b, product 3502c, and/or geography 3502d. As illustrated, the filtering controls 3502 are set such that geography 5302d is limited to Spain.

[00328] As illustrated, the scatter bar graph interface 3500 presents columns of rings by time period 3504 (as illustrated, month of expiration date of insurance policy). The rings within the columns are aligned at a remittance value level 3506 within the selected remittance value band 3502a (as illustrated, set to $0 to $5M). In some implementations, each ring is selectable to obtain information regarding an individual transaction (e.g., insurance policy). For example, upon selection of a ring 3508, the user is presented with a pop-up dialog 3510 illustrating details regarding a particular insurance policy (e.g., policy identification, country, expiration date, and remittance value). In other implementations, the pop-up dialog 3510 may include additional or alternative detail information such as, in some examples, product type, entity participant identification (e.g., a particular customer), intermediate participant identification (e.g., a broker which placed the particular policy), renewal status, and purchase date.

[00329] FIG. 36 illustrates an example data input screen 3600 for supplying information associated with a prospective entity participant, such as the example prospective entity participant labeled "XYZ Company" within an entity participant name field 3602. The prospective entity participant, for example, may be an entity interested in pursuing a subscription product through an intermediate participant of the dashboard environment (e.g., casualty insurance through a broker). The information supplied via the example data input screen 3600 may be used to develop initial benchmarking comparisons, such as the peer comparison metric layouts illustrated in FIGS. 37A through 37E. General information 3604 associated with the prospective entity participant may include an industry (selected via an industry drop down box 3604a, "retail & wholesale trade" as illustrated), and a line of business (selected via a line of business drop down box 3604b, "workers' compensation" as illustrated) associated with the prospective entity participant. Other general information fields 3604, in some examples (not illustrated), may include entity maturity (e.g., ranges of years demonstrating, in some examples, start-up, established, and mature entities), enterprise type (e.g., private, public, non-profit, etc.), and/or geographic region. The general information 3604 associated with the prospective entity participant, for example, may be used to identify a number of peer entity participants similar to the prospective entity participant. In another example, the general information 3604 may be used to refine options in other data entry fields below.

[00330] Beneath the general information 3604 are current metrics input fields 3606, including a remittance amount (e.g., annual premium) input field 3606a and a retained losses amount input field 3606b. In further refinement regarding a current subscription (e.g., in accordance with the annual premium 3606a), a set of subscription details input fields 3608 may include a deductible amount input field 3608a, a limit amount input field 3608b, and/or a program limit amount input field 3608c.

[00331] Finally, business metrics 3610 supply information relevant to the selected line of business. As illustrated, a payroll input field 3610a is active, since payroll relates to the workers' compensation line of business entered in the line of business drop-down box 3604b. If, instead, "commercial auto" was selected within the line of business drop-down box 3604b, a number of vehicles input field 3610b may be activated for input. Other business metrics, as illustrated, include a percentage private passenger vehicles input field 3610c and a revenue input field 3610d. In further examples (not illustrated) an aircraft input field 3610 may be presented to correspond with an aircraft line of business 3604b, an inventory input field 3610 or assets input field 3610 may be presented to correspond with a burglary line of business 3604b, an insured value field 3610 or square footage field 3610 may be presented to correspond with a property line of business 3604b, and/or a revenues field 3610, throughput field 3610, or units produced field 3610 may be presented to correspond with a products liability line of business 3604b.

[00332] FIGS. 37A through 37E illustrate example graphic analysis layouts for presenting peer comparison metrics related to entity participants. In some implementations, the graphic analysis layouts present metrics derived from the information entered via the data input screen 3600 of FIG. 36, related to a prospective entity participant. For example, when meeting with a prospective entity participant, a representative (e.g., broker) of an intermediate participant may quickly enter data regarding the prospective entity participant into the data input screen 3600, then present the various graphic analysis layouts of FIGS. 37A through 37E to the prospective entity participant, using the graphic analysis layouts to trigger discussion points and to demonstrate the powerful features available within the dashboard environment. The graphic analysis layouts of FIGS. 37A through 37E, for example, may be presented upon a handheld computing device such as a tablet computer or other mobile device for ease of presentation at the site of the prospective entity participant. To further encourage ease of interaction during a meeting with the prospective entity participant, various fields within the data input screen 3600 and/or graphic analysis layouts of FIGS. 37A through 37E may be voice activated, such that a user may enter information via verbal commands.

[00333] In some implementations, the graphic analysis layouts present metrics derived from information collected and managed related to a present entity participant of the dashboard environment. For example, upon renewal of a subscription product, the information regarding a particular entity participant may be reviewed to identify discrepancies between peer metrics and the present metrics of a particular entity participant. The information, in some examples, may be presented to the particular entity participant via a dashboard interface or in a report (e.g., a file distributed via electronic mail, the dashboard environment, or in print). In another example, the information may be presented to the particular entity participant by a representative of an intermediate participant, for example during a subscription renewal discussion. Similar to the scenario described above in relation to a prospective entity participant, the graphic analysis layouts of FIGS. 37A through 37E may be presented by the representative of the intermediate participant on a mobile computing device such as a tablet computer during an in-person meeting with a representative of the particular entity participant.

[00334] In further implementations, the graphic layouts may present metrics derived from aggregate information collected and managed related to current entity participants of the dashboard environment to forecast likely outcomes for a prospective entity participant without entering information regarding the prospective participant beyond general information 3604 (e.g., information sufficient to identify peers of the prospective entity participant). A current entity participant, for example, may be interested in reviewing such information prior to pursuing acquisition or expansion into a new industry. Additionally, a current entity participant may be interested in reviewing such information when evaluating the performance of the intermediate participant working with the entity participant. The information, in a further example, may provide a current entity participant with insight into external market perception of the entity participant. In another example, a current entity participant may use the information to assess opportunities for investment in consultative solutions in order to improve their relative standing in relation to peer entity participants. In yet another example, a current or prospective intermediate participant may be interested in reviewing such information to obtain an understanding of how the graphic analysis layouts of FIGS. 37A through 37E may be used as tools by the intermediate participant to support prospective and present entity participants in identifying subscription products best suited for the needs of the entity participant.

[00335] Turning to FIG. 37 A, an example loss rate / premium rate graphic interface 3700 presents information regarding both loss rate 3712 and premium rate 3714 per unit worker's payroll 3708 (e.g., per $100 payroll) in relation to a workers' compensation line of business 3704 for an entity participant 3702. The loss rate 3712 of the entity participant 3702, for example, may be derived from information entered into the retained losses input field 3606b and the payroll field 3610a of the data input screen 3600 of FIG. 36, while the premium rate 3714 of the entity participant 3702 may be derived from information entered into the remittance value field 3606a and the payroll field 3610a of the data input screen 3600.

[00336] The loss rate 3712 of the entity participant 3702 and premium rate 3714 of the entity participant 3702 are compared, within the graphic interface 3700, to metrics derived from a number of peers 3710 (e.g., fourteen peers, as illustrated). The peers, for example, may be selected automatically based upon similarities between the entity participant 3702 and each of the peers 3710 as well as data availability regarding loss rate and premium rate for the worker's compensation line of business 3704 for each of the peers 3710. The similarities, in a first example, can include similar general traits shared between the entity participant and the peers, such as the general information presented within the fields 3604 of FIG. 36. In a second example, similarities can include similarities in workers' compensation plans as derived, for example, via the subscription details input fields 3608 of FIG. 36.

[00337] As illustrated, a retail and wholesale trade filter 37061 of an industry filter checkbox list 3706 has been selected. The filter, for example, may correspond to the industry dropdown box 3604a of FIG. 36, such that, in other implementations, the industry filters 3706 may not be presented within the graphic interface 3700 since the industry is derived from the data input screen of FIG. 36. In some implementations, a user may optionally select additional industry filters 3706 (e.g., beyond the industry selected via the drop-down box 3604a of FIG. 36) to generate a wider sample of peers. For example, an alcoholic beverage company may identify with both retail and wholesale trade 37061 as well as food system, agribusiness, and beverage 3706f.

[00338] Turning to the loss rate graphic analysis 3712, an entity participant rate 3720 (e.g., 1.06 as illustrated) is compared to a peer minimum loss rate 3716a (e.g., 0.32), a peer maximum loss rate 3716c (e.g., 5.51), and a peer median loss rate 3716b (e.g., 1.43).

Additionally, a lower bounds 3718a and an upper bounds 3718b illustrate a more prevalent window surrounding the peer median loss rate 3716b. The lower and upper bounds 3718, in some examples, may illustrate minimum and maximum peer loss rates when the outlier peers (e.g., corresponding to the peer minimum loss rate 3716a and the peer maximum loss rate 3716c) have been discarded, first quartile and third quartile loss rate among the peer loss rates, historic peer median loss rate values (e.g., during a past three, five, or 10 years, etc.), or minimum and maximum peer loss rates of those peers most similar to the entity participant 3702 (e.g., the X closest to entity participant 3702). In a particular example, the peers 3710 may include all peers of the entity participant 3702 based upon subscription details input fields 3608, while the most similar peers may be those peers also matching information entered via the general information fields 3604 of the data input screen 3600 of FIG. 36. In reviewing the loss rate graphic analysis 3712, the entity participant 3702 can see that its loss rate 3720 is lower than the median loss rate 3716b and is generally towards the low end of the lower bound 3718a, demonstrating that the entity participant 3702 has performed better overall in loss retention per unit payroll than other similar entity participants of the dashboard environment. This would suggest that the entity participant 3702 is a desirable subscriber for industry participants (e.g., insurance companies) and may be positioned to bargain for improved remittance values accordingly.

[00339] Similar to the loss rate graphic analysis 3712, the premium rate graphic analysis 3714 illustrates a comparison of entity participant premium rate 3726 (e.g., 0.26) to a peer minimum premium rate 3722a (e.g., 0.08), a peer maximum premium rate 3722c (e.g., 0.7), and a peer median premium rate 3722b (e.g., 0.14). Additionally, a lower bounds 3724a and an upper bounds 3724b illustrate a more prevalent window surrounding the peer median premium rate 3722b, as described in more detail above in relation to the lower and upper bounds 3718. In reviewing the premium rate graphic analysis 3714, the entity participant 3702 can see that, despite having a lower loss rate 3720 than typical, the entity participant 3702 pays a greater amount of premium per unit payroll than the peer median premium rate 3722b. In fact, the entity participant premium rate 3726 exceeds the upper bound 3724b, suggesting that the entity participant 3702 should bargain to lower current remittance value (e.g., premium).

[00340] In the circumstance of a current entity participant of the dashboard environment which is approaching renewal of the present workers' compensation subscription, because of the discrepancy illustrated between the loss rate 3712 and the premium rate analysis 3714, information such as the graphic analysis illustrated in the interface 3700 may be flagged for the attention of an intermediate participant (e.g., current broker of the entity participant 3702 or a competing broker) so that the intermediate participant may share the information presented by the graphic analysis interface 3700 with the entity participant 3702. In one example, the intermediate participant may have the opportunity to review metrics similar to those presented in the graphic analysis interface 3700 upon selection of an opportunity within an opportunity pipeline dashboard interface such as the pipeline opportunity interfaces described in relation to FIGS. 21 A through 21D and FIGS. 29A through 29D, above.

[00341] Further to the discussion above regarding the insights derived through comparison of the loss rate 3712 analysis and premium rate 3714 analysis, turning to FIG. 37B, a loss- adjusted pricing analysis graphic interface 3730 presents a line graph of premium rate per unit payroll (y-axis) over loss rate per unit payroll (x-axis) for the entity participant 3702 (illustrated by entity pattern 3732a), the upper bound 3718b, 3722b (illustrated by upper bound pattern 3732c), and the lower bound 3718a, 3722a (illustrated by lower bound pattern 3732d). Further, the line graph includes a workers' compensation price index (illustrated by price index pattern 3732b), illustrating a loss-adjusted price index of workers' compensation line of business 3704 for the dashboard environment as a whole (falling between the upper bound 3732c and lower bound 3732d). The workers' compensation price index, for example, may be derived based upon analysis of variables associated with subscription programs such as, in some examples, loss rates, premium rates, program structure, and/or size of exposure. In a particular example, the workers' compensation price index pattern 3732b may represent a best fit of workers' compensation subscription pricing information for industry participants of the dashboard environment involved in the workers' compensation line of business. As evidenced by the line graph, the premium rate per unit payroll over loss rate per unit payroll of the entity participant 3732a exceeds the upper bound 3732c. In reviewing the interface 3730 with a representative of the intermediate participant, the entity participant 3702 may discuss options and opportunities to improve pricing (e.g., upon subscription renewal).

[00342] In discussing subscription renewal options, turning to FIG. 37C, a rate change and market share analysis graphic interface 3740 presents information regarding change in premium rates 3742 between a current or recent time period (e.g., quarter, year, etc.) and a prior time period (e.g., past quarter, past year, etc.) for industry participants 3752 within the workers' compensation line of business 3704. In this manner, the graphic interface 3740 may be used either to illustrate recent movements in remittance values for workers' compensation line of business 3704 or to forecast movements within a current quarter. If forecasting is performed, in some implementations, both real time or near real time (e.g., present time period up to prior day, prior hour, real time gathering from intermediate participant computing system records, etc.) remittance values as well as prior (finalized) time period remittance values (e.g., previous time period and/or corresponding time period of prior year) may be used to forecast overall movement in remittance value for the current time period. Forecasting is described in greater detail above in relation to FIG. IB and FIG. 21 A. In this manner, the entity participant 3702 may be counseled on whether to lock in premium rates early (e.g., rates appear to be on the rise) or to hold off on accepting subscription renewal (e.g., rates appear to be falling). The particular industry participants 3752, labeled the "peer set" in relation to a change in premium rate analysis 3742a, may include those industry participants 3752 supplying workers' compensation policies to the peer entity participants 3710 identified for analysis in relation to the analysis interface 3700 of FIG. 37A, while the "full set" identified in relation to a change in premium rate analysis 3742b may include all industry participants of the dashboard interface providing workers' compensation policies (or, optionally, filtered to match policy criteria of the entity participant 3702 such as region, premium value range, industry, etc.).

[00343] Turning to the peer set change in premium rate analysis 3742a, an average peer rate change 3744a (e.g., -0.4) is illustrated in comparison to a median peer rate change 3744b (e.g., 0.0), as well as both a first quartile peer rate change 3746a (e.g., 0.0) and a third quartile peer rate change 3746b (e.g., 2.0). Similarly, adjacent to the peer set change in premium rate analysis 3742a, a full set change in premium rate analysis 3742b illustrates an average industry participant rate change 3748a (e.g., -1.4) in comparison to a median industry participant rate change 3748b (e.g., 0.0), as well as both a first quartile industry participant rate change 3750a (e.g., -2.9) and a third quartile industry participant rate change 3750b (e.g., 2.0). As may be noted in comparing the two charts 3742a, 3742b, the median peer rate change 3744b and third quartile peer rate change 3746b match the median industry participant rate change 3748b and the third quartile industry participant rate change 3750b, respectfully. However, the average rate changes 3744a, 3748a and first quartile rate changes 3746a, 3750a differ by quite a bit, suggesting that there is greater volatility within the industry participants overall than in the peer industry participants 3752. On the other hand, greater cost benefits may be gained by switching to an industry participant outside the peer industry participants 3742, since the average industry participant rate change 3748a and first quartile industry participant rate change 3750 are so much lower than the corresponding rate changes 3744a, 3746a of the peer industry participants.

[00344] To aid in analyzing the relative strength of the peer industry participants 3752, a market share analysis table presents a percentage of total remittance value 3754 (e.g., within the dashboard environment, within the dashboard environment for the workers' compensation line of business 3704) and a rank 3756 for each peer industry participant 3752 (identified by name). While percentage total remittance value 3754 and rank 3756 are illustrated in descending order , in other implementations, the peer industry participants 3752 may be listed in alphabetical order, with rank 3756 and associated premium 3754 being randomly presented within the table. As evidenced by the market share analysis table, a first industry participant 3752a holds over a third of the total remittance value 3754a, while the industry participants 3752 ranked sixth through tenth 3756 each share less than two percent of the total remittance value 3754 each. Overall, the peer industry participants capture over 95% of remittance value of the dashboard environment. As such, remaining industry participants of the full set are small in market share and, as evidenced by the full set graphic analysis 3742a, more volatile on average than the peer set. The entity participant 3702 may wish to consider one of the peer industry participants 3752 for renewal purposes if volatility is a concern. In another example, a prospective entity participant may review the information presented within the rate change and market share analysis graphic interface 3740 when considering marketing a program within the dashboard environment to determine which other industry participants have engaged in transactions with peers of the prospective entity participant and have experience with entity participants similar to the prospect entity participant. In a further example, the information of the interface 3740 may alert a prospective entity participant to a market that is significant for peers of the prospective entity participant but is relatively unfamiliar to the prospective entity participant. In this circumstance, the intermediate participant may be provided the opportunity to help the entity participant in making connections with industry participants related to the unfamiliar market. In a final example, if significant changes to market share are noted over time via the information portrayed within the interface 3740, the entity participant and/or intermediate participant may be provided the opportunity (e.g., via a drill-down mechanism or further information access mechanism of the interface 3740) to identify one or more causes for a particular industry participant or group of industry participants to gain or lose market share.

[00345] FIG. 37D illustrates an umbrella/excess program limit comparison graphic interface 3760 presenting a program limit comparison between the entity participant 3702 and a set of peer entity participants 3710 for an umbrella liability line of business 3768. The program limit, for example, may correspond to the limit field 3608b of the data entry screen 3600 illustrated in FIG. 36. Unlike the graphic interface 3700 of FIG. 37A which involved fourteen peer entity participants 3710, the comparison illustrated in the graphic interface 3760 involves data gleaned from forty peer entity participants 3769. This may be, for example, based upon differing parameters between the lines of business 3704, 3768 (e.g., workers' compensation vs. umbrella liability). Umbrella liability, for example, may be linked to assets or revenues of the entity participant 3702, while workers' compensation peers are selected based upon payroll data of the entity participant 3702. In a particular example, the peers 3766 selected for comparison in the umbrella liability line of business 3768 may be identified as having a similar revenue structure to the entity participant 3702 (e.g., based upon the revenue field 3610d of the data input screen 3600 of FIG. 36).

[00346] As in FIG. 37 A, the retail and wholesale trade filter 37061 of the industry filter checkbox list 3706 has been selected. The filter, for example, may correspond to the industry drop-down box 3604a of FIG. 36, such that, in other implementations, the industry filters 3706 may not be presented within the graphic interface 3760 since the industry is derived from the data input screen of FIG. 36. In some implementations, a user may optionally select additional industry filters 3706 (e.g., beyond the industry selected via the drop-down box 3604a of FIG. 36) to generate a wider sample of peers. For example, an alcoholic beverage company may identify with both the retail and wholesale trade industry 37061 as well as the food system, agribusiness, and beverage industry 3706f.

[00347] Turning to the graphic analysis, an entity participant program limit 3764 (e.g., $75M) is illustrated in comparison to a minimum peer program limit 3762a (e.g., $4M), a median peer program limit 3762b (e.g., $100M), and a maximum peer program limit 3762c (e.g., $400M). Additionally, a lower bounds 3766a (overlapped by the minimum peer program limit 3762a) and an upper bounds 3766b illustrate a more prevalent window surrounding the peer program limit 3762b. The lower and upper bounds 3766, in some examples, may illustrate minimum and maximum peer program limits when the outlier peers (e.g., corresponding to the peer minimum program limit 3762a and the peer maximum program limit 3762c) have been discarded, first quartile and third quartile program limit among the peer program limits, historic peer median program limit values (e.g., during a past three, five, or 10 years, etc.), or minimum and maximum peer program limits of those peers most similar to the entity participant 3702 (e.g., the X closest to entity participant 3702). In a particular example, the peers 3769 may include all peers of the entity participant 3702 based upon subscription details input fields 3608, while the most similar peers may be those peers also matching information entered via the general information fields 3604 of the data input screen 3600 of FIG. 36. Alternatively, rather than presenting both an upper bounds and a lower bounds, a single threshold program limit 3766 may be used to represent, in some examples, an average of peer program limits, a median of peer program limits discounting the minimum 3762a and maximum 3762c outliers, or a historic median peer program limit (e.g., over the past two years, three years, five years, etc.).

[00348] In reviewing the graphic analysis of the graphic interface 3760, the entity participant 3702 may conclude that its limit is a bit low which could represent an unnecessary liability to the entity participant 3702. The representative of the intermediate participant may use the graphic interface 3760 to lead into a discussion of the remittance value (e.g., premium) difference between coverage at the present program limit 3762b and increased coverage at the peer median program limit 3762b. Conversely, if the umbrella/excess program limit comparison graphic interface 3760 presented information suggesting that the entity participant 3702 is overspending due to the present program limit 3762b exceeding the peer median program limit 3762b. In this circumstance, the entity participant may discuss adjusting present subscription levels to a smaller limit to conserve and/or redirect funds.

[00349] FIG. 37E illustrates a collateral efficiency analysis graphic interface 3770 for reviewing a collateral/liability ratio comparison between the entity participant 3702 and other entity participants of the dashboard environment, based upon a credit rating equivalent 3780. As background, certain subscription programs available via the dashboard environment, such as primary casualty insurance programs, may be offered with large deductibles where the entity participants retain the risk within the deductible (e.g., retained liabilities). To secure the retained liabilities, industry participants of the dashboard environment may require collateral from the entity participants. The collateral amounts, for example, may be based on the value of the liabilities, less a credit. As such, the larger the credit, the smaller the collateral, and the better collateral efficiency of the program. In the interface 3770, the collateral efficiency is communicated in terms of credit to liability ratio (or credit ratio). The credit liability of a particular entity participant is sensitive to the credit quality of the entity participant, and is thus (generally speaking) influenced by the credit rating applied to the particular entity participant.

[00350] In some implementations, the interface 3770 is provided to demonstrate for the prospective entity participant 3702 how the prospective entity participant's credit/liability ratio 3776a compares to peers of similar credit rating 3780. The bands 3782 may represent guideline ranges of typical credit/debt ratios of other entity participants within the dashboard environment (e.g., peer entity participants to the entity participant 3702, entity participants subscribed to programs with a same industry participant or group of industry participants, etc.), from a respective high end 3774a to a respective low end 3774b.

[00351] As illustrated, ranges illustrated via the bands 3782 overlap, such that, for example, a credit/liability ratio band 3782b associated with the BBB+ credit rating equivalent 3780 is encompassed within the credit/liability ratio band 3782a associated with the greater than or equal to A- credit rating equivalent 3780. A collateral ratio 3776a of the entity participant 3702 lands at the bottom of the low end 3774b of band 3782h with a B+ credit rating equivalent 3780, while the credit rating equivalent 3780 of the entity participant 3702 is a BB- rating, placing the entity participant at point 3776b of the graph (e.g., far below the band 3782g corresponding to the BB- rating).

[00352] A prospective entity participant 3702, for example, may review the information presented within the interface 3770 to determine whether the entity participant's credit level aligns appropriately with its collateral. For example, if the credit ratio 3776a of the prospective entity participant 3702 falls below the band 3782 corresponding to the prospective entity participant's credit rating 3780, the prospective entity participant 3702 may be concerned that it is not receiving adequate credit and/or are posting too much

collateral. Conversely, if the credit ratio 3776a of the prospective entity participant 3702 lies above the band 3782 corresponding to the prospective entity participant's credit rating 3780, the prospective entity participant 3702 may determine that it is receiving more credit than might be expected, and posting less collateral than its peers. Further, the interface 3770 may be used to make determinations regarding how collateral outcome might change for a particular entity participant if the credit rating 3780 of entity participant is altered (e.g., upgraded or downgraded). As a general observation, the interface 3770 also provides information on how the industry participants of the dashboard environment treat collateral from a perspective of reviewing aggregate data of a group (e.g., peers, geography, all, etc.) of entity participants. [00353] In some implementations, the comparison data used to present the graphic analysis of the graphic interface 3770 is gleaned from individual transactions between entity participants and industry participants involving collateral. Alternatively or additionally, the comparison data may be gleaned from public data sources based upon information regarding present entity participants of the dashboard environment (e.g., company name, stock ticker identification, etc.). For example, credit ratings may be published periodically via

Morningstar, Inc. of Chicago, IL, Moody's Investors Service of New York City, NY, Standard & Poor's of Baltimore, MD, etc.

[00354] FIGS. 28 A and 28B illustrate various aspects of an exemplary architecture implementing a dashboard environment 2800. The high-level architecture includes both hardware and software applications, as well as various data communications channels for communicating data between the various hardware and software components. The dashboard environment 2800 may be roughly divided into front-end components 2802 and back-end components 2804. The front-end components 2802 are primarily disposed within a participant network 2810 including multiple participant systems 2812. The participant systems 2812 may be located, by way of example rather than limitation, in separate geographic locations from each other, including different areas of the same city, different cities, different states, or even different countries. The front-end components 2802 include a number of computing devices such as workstations 2828. The workstations 2828 are local computers located in the various participant systems 2812 throughout the participant network 2810 and executing various dashboard environment applications.

[00355] Web-enabled devices 2814 (e.g., personal computers, tablets, cellular phones, smart phones, web-enabled televisions, etc.) may be communicatively connected to participant systems 2812 and a dashboard system 2840 through a digital network 2830 or a wireless router 2831, as described below.

[00356] Referring now to FIG. 28A, those of ordinary skill in the art will recognize that the front-end components 2802 could also include a number of participant facility computing devices such as facility servers 2826 disposed at the number of participant systems 2812 instead of, or in addition to, a number of workstations 2828. Each of the participant systems 2812 may include one or more facility servers 2826 that may facilitate communications between the web-enabled devices 2814 and the back-end components 2804 via a digital network 2830, described below, and between the terminals 2828, 2828A of the participant systems 2812 via the digital network 2830, and may store information for a number of customers/employees/accounts/etc. associated with each participant facility. Of course, a local digital network 2884 may also operatively connect each of the workstations 2828 to the facility server 2826. Unless otherwise indicated, any discussion of the workstations 2828 also refers to the facility servers 2826, and vice versa. Moreover, environments other than the participant systems 2812, such as the kiosks, call centers, and Internet interface terminals may employ the workstations 2828, the web-enabled devices 2814, and the servers 2826. As used herein, the term "location" refers to any of these points of contact (e.g., call centers, kiosks, Internet interface terminals, etc.) in addition to the participant systems 2812, etc. described above.

[00357] The front-end components 2802 communicate with the back-end components 2804 via the network 2830. One or more of the front-end components 2802 may be excluded from communication with the back-end components 2804 by configuration or by limiting access due to security concerns. For example, the web enabled devices 2814 may be excluded from direct access to the back-end components 2804. In some embodiments, the participant systems 2812 may communicate with the back-end components via the network 2830. In other embodiments, the participant systems 2812 and web-enabled devices 2814 may communicate with the back-end components 2804 via the same network 2830, but digital access rights, IP masking, and other network configurations may deny access of the web- enabled devices 2814. The web-enabled devices may also connect to the network 2830 via the encrypted, wireless router 2831.

[00358] The network 2830 may be a proprietary network, a secure public Internet, a virtual private network or some other type of network, such as dedicated access lines, plain ordinary telephone lines, satellite links, combinations of these, etc. Where the network 2830 includes the Internet, data communication may take place over the network 2830 via an Internet communication protocol. In addition to one or more web servers 2890 (described below), the back-end components 2804 include the dashboard system 2840, for example within a central processing facility or cloud-based processing farm. Of course, the participant systems 2812 may be communicatively connected to different back-end components 2804 having one or more functions or capabilities that are similar to the dashboard system 2840. The dashboard system 2840 may include one or more computer processors 2862 adapted and configured to execute various software applications and components of the dashboard environment 2800.

[00359] The dashboard system 2840 further includes a database 2846 (which may include one or more databases). The database 2846 is adapted to store data related to the operation of the dashboard environment 2800. The dashboard system 2840 may access data stored in the database 2846 when executing various functions and tasks associated with the operation of the dashboard environment 2800.

[00360] Although the dashboard environment 2800 is shown to include the dashboard system 2840 in communication with three participant systems 2812, and various web-enabled devices 2814 it should be understood that different numbers of processing systems, locations, and devices may be utilized. For example, the network 2830 (or other networks, not shown) may interconnect the dashboard environment 2800 to a number of included dashboard systems 2840, hundreds of participant systems 2812, and thousands of web-enabled devices 2814. According to the disclosed example, this configuration may provide several advantages, such as, for example, enabling near real-time uploads and downloads of information as well as periodic uploads and downloads of information. This provides for a primary backup of all the information generated in the wireless customer data transfer process. Alternatively, some of the participant systems 2812 may store data locally on the facility server 2826 and/or the workstations 2828.

[00361] FIG. 28A also depicts one possible embodiment of the dashboard system 2840. The dashboard system 2840 may have a controller 2855 operatively connected to the database 2846 via a link 2856 connected to an input/output (I/O) circuit 2866. It should be noted that, while not shown, additional databases may be linked to the controller 2855 in a known manner.

[00362] The controller 2855 includes a program memory 2860, the processor 2862 (may be called a microcontroller or a microprocessor), a random-access memory (RAM) 2864, and the input/output (I/O) circuit 2866, all of which are interconnected via an address/data bus 2865. It should be appreciated that although only one microprocessor 2862 is shown, the controller 2855 may include multiple microprocessors 2862. Similarly, the memory of the controller 2855 may include multiple RAMs 2864 and multiple program memories 2860. Although the I/O circuit 2866 is shown as a single block, it should be appreciated that the I/O circuit 2866 may include a number of different types of I/O circuits. The RAM(s) 2864 and the program memories 2860 may be implemented as semiconductor memories, magnetically readable memories, and/or optically readable memories, for example. A link 2835 may operatively connect the controller 2855 to the digital network 2830 through the I/O circuit 2866.

[00363] FIG. 28B depicts one possible embodiment of the front-end components 102 located in one or more of the participant systems 2812 from FIG. 28A. Although the following description addresses the design of the participant systems 2812, it should be understood that the design of one or more of the participant systems 2812 may be different from the design of others of the participant systems 2812. Also, each of the participant systems 2812 may have various different structures and methods of operation. It should also be understood that while the embodiment shown in FIG. 28B illustrates some of the components and data connections that may be present in a participant system 2812, it does not illustrate all of the data connections that may be present in a participant system 2812. For exemplary purposes, one design of a participant system 2812is described below, but it should be understood that numerous other designs may be utilized.

[00364] Each of the participant systems 2812 has one or more tablets 2833 and/or a facility server 2826. The network 2830 and wireless router 2831 operatively connect the facility server 2826 to the number of tablets 2833 and/or to other web-enabled devices 2814 and workstations 2828. The network 2830 may be a wide area network (WAN), a local area network (LAN), or any other type of digital network readily known to those persons skilled in the art. The network 2830 may operatively connect the facility server 2826, the tablets 2833, the workstations 2828, and/or the other web-enabled devices 2814 to the dashboard system 2840.

[00365] Each tablet 2833, workstation 2828, participant computing device terminal 2828a, or facility server 2826 includes a controller 2870. Similar to the controller 2855 from FIG. 28A, the controller 2870 includes a program memory 2872, a microcontroller or a microprocessor (MP) 2874, a random-access memory (RAM) 2876, and an input/output (I/O) circuit 2880, all of which are interconnected via an address/data bus 2878. In some embodiments, the controller 2870 may also include, or otherwise be communicatively connected to, a database 2882. The database 2882 (and/or the database 2846 of FIG. 28 A) includes data such as entity participant information records, intermediate participant information records, industry participant information records, and other rules and

miscellaneous information. As discussed with reference to the controller 2855, it should be appreciated that although FIG. 28B depicts only one microprocessor 2874, the controller 2870 may include multiple microprocessors 2874. Similarly, the memory of the controller 2870 may include multiple RAMs 2876 and multiple program memories 2872. Although the FIG. 28B depicts the I/O circuit 2880 as a single block, the I/O circuit 2880 may include a number of different types of I/O circuits. The controller 2870 may implement the RAM(s) 2876 and the program memories 2872 as semiconductor memories, magnetically readable memories, and/or optically readable memories, for example.

I l l [00366] Either or both of the program memories 2860 (FIG. 28A) and 2872 may also contain machine-readable instructions (i.e., software) 2871, for execution within the processors 2862 (FIG. 28 A) and 2874, respectively. The software 2871 may perform the various tasks associated with operation of the location or locations, and may be a single module 2871 or a number of modules 2871a, 2871b. While the software 2871 is depicted in FIGS. 28A and 28B as including two modules, 2871a and 2871b, the software 2871 may include any number of modules accomplishing tasks related to location operation.

[00367] In addition to the controller 2870, the tablets 2833, the workstations 2828 and the other web-enabled devices 2814 may further include a display and a keyboard as well as a variety of other input/output devices (not shown) such as a scanner, printer, mouse, touch screen, track pad, track ball, isopoint, voice recognition system, digital camera, bar code scanner, RFID reader, etc. An employee at a particular participant location may sign on and occupy each tablet 2833, workstation 2828 or client device terminal 2828a to assist the employee in performing his or her duties. Employees may sign onto the tablet 2833, workstation 2828 or the terminal 2828a using any available technique, such as entering a user name and password. If an employee signs on to the system using a tablet 2833, the network 2830 communicates this information to the facility server 2826, so that the controller 2870 may identify which employees are signed onto the dashboard environment 2800 and which tablet 2833, workstation 2828 or terminal 2828a the employee is signed onto.

[00368] Various software applications resident in the front-end components 2802 and the back-end components 2804 implement functions related to participant location operation, and provide various user interface means to allow users (e.g., industry participant employees, intermediate participant employees, etc.) to access the dashboard environment 2800. One or more of the front-end components 2802 and/or the back-end components 2804 may include a user-interface application 2811 for allowing a user to input and view data associated with the dashboard environment 2800, and to interact with the dashboard system 2840 described herein. In one embodiment, the user interface application 2811 is a web browser client, and the facility server 2826 or the dashboard system 2840 implements a server application 2813 for providing data to the user interface application 2811. However, the user interface application 2811 may be any type of interface, including a proprietary interface, and may communicate with the facility server 2826 or the dashboard system 2840 using any type of protocol including, but not limited to, file transfer protocol (FTP), telnet, hypertext-transfer protocol (HTTP), etc. Moreover, some embodiments may include the user interface application 2811 running on one of the web-enabled devices 2814, while other embodiments may include the application 2811 running on the tablet 2833 in a participant system 2812. The dashboard system 2840 and/or the facility server 2826 may implement any known protocol compatible with the user-interface application 2811 running on the tablets 2833, the workstations 2828 and the web-enabled devices 2814 and adapted to the purpose of receiving and providing the necessary information during the data transfer process.

[00369] For purposes of implementing the dashboard environment 2800, the user interacts with the dashboard environment 2800 (e.g., the dashboard system 2840) via a number of web pages. FIG. 28C depicts a web server 2890 connected via the network 2830 to a number of tablets 2833 and other web-enabled devices through which a user 2892 may initiate and interact with the dashboard environment 2800. The web enabled devices may include, by way of example, a smart-phone 2894a, a web-enabled cell phone 2894b, a tablet computer 2833, a personal digital assistant (PDA) 2894c, a laptop computer 2894d, a desktop computer 2894e, a portable media player (not shown), etc. Of course, any web-enabled device appropriately configured may interact with the dashboard environment 2800. The web- enabled devices 2833 and 2894 need not necessarily communicate with the network 2830 via a wired connection. In some instances, the web enabled devices 2833 and 2894 may communicate with the network 2830 via wireless signals 2896 and, in some instances, may communicate with the network 2830 via an intervening wireless or wired device 2831, which may be a wireless router, a wireless repeater, a base transceiver station of a mobile telephony provider, etc. Each of the web-enabled devices 2833 and 2894 may interact with the web server 2890 to receive web pages, such as the web page 2898 depicted in FIG. 28C, for presentation on a display associated with the web-enabled device 2833 and 2894. It will be appreciated that although only one web server 2890 is depicted in FIG. 28C, multiple web servers 2890 may be provided for the purpose of distributing server load, serving different web pages, implementing different portions of the location web interface, etc.

[00370] Turning now to FIG. 28D, the web server 2890, like the facility server 2826, includes a controller 2806. Similar to the controllers 2855 and 2870, the controller 2806 includes a program memory 2808, one or more microcontrollers or microprocessors (MP) 2816, a random-access memory (RAM) 2818, and an input/output (I/O) circuit 2820, all of which are interconnected via an address/data bus 2822. In some embodiments, the controller 2806 may also include, or otherwise be communicatively connected to, a database 2824 or other data storage mechanism (e.g., one or more hard disk drives, optical storage drives, solid state storage devices, etc.). The database 2824 may include data such as customer web profiles, product data, web page templates and/or web pages, and other data necessary to interact with the user 2892 through the network 2830. As discussed with reference to the controllers 2855 and 2870, it should be appreciated that although FIG. 28D depicts only one microprocessor 2816, the controller 224 may include multiple microprocessors 2816.

Similarly, the memory of the controller 2806 may include multiple RAMs 2818 and multiple program memories 2808. Although the FIG. 28D depicts the I/O circuit 2820 as a single block, the I/O circuit 2820 may include a number of different types of I/O circuits. The controller 2806 may implement the RAM(s) 2818 and the program memories 2808 as semiconductor memories, magnetically readable memories, and/or optically readable memories, for example.

[00371] In addition to being connected through the network 2830 to the user devices 2833 and 1694, as depicted in FIG. 28C, FIG. 28D illustrates that the web server 2890 may also be connected through the network 2830 to the dashboard system 2840 and/or one or more facility servers 2826. As described below, connection to the dashboard system 2840 and/or to the one or more facility servers 2826 facilitates the dashboard environment 2800.

[00372] The program memory 2808 and/or the RAM 2818 may store various applications for execution by the microprocessor 2816. For example, an application 2832 may provide a user interface to the server, which user interface may, for example, allow a network administrator to configure, troubleshoot, or test various aspects of the server's operation, or otherwise to access information thereon. A server application 2834 operates to populate and transmit web pages to the web-enabled devices 2894, receive information from the user 2892 transmitted back to the server 2890, and forward appropriate data to the dashboard system 2840 and the facility servers 2826, as described below. Like the software 2871, the server application 2834 may be a single module 2834 or a number of modules 2834a, 2834b. While the server application 2834 is depicted in FIG. 28D as including two modules, 2834a and 2834b, the server application 2834 may include any number of modules accomplishing tasks related to implementation of the web server 2890. By way of example, the module 2834a may populate and transmit the web pages and/or may receive and evaluate inputs from the user 2892 to facilitate in the wireless transfer of data from a first tablet to a second tablet, while the module 2834b may communicate with one or more of the back end components 104 to provide the requested data.

[00373] Typically, a user may launch or instantiate a user interface application (e.g., a web browser or other client application) from a web-enabled device, such as the web-enabled devices 2833 and 2894, to access the web server 2890 cooperating with the dashboard system 2840 to implement functionality of the dashboard environment 2800. [00374] One or more processors can be utilized to implement any functions and/or algorithms described herein, unless explicitly stated otherwise. Additionally, any functions and/or algorithms described herein, unless explicitly stated otherwise, can be performed upon one or more virtual processors, for example on one or more physical computing systems such as a computer farm or a cloud drive.

[00375] Reference has been made to flowchart illustrations and block diagrams of methods, systems and computer program products according to implementations of this disclosure. Aspects thereof are implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[00376] These computer program instructions may also be stored in a computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[00377] A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of this disclosure. For example, preferable results may be achieved if the steps of the disclosed techniques were performed in a different sequence, if components in the disclosed systems were combined in a different manner, or if the components were replaced or supplemented by other components. The functions, processes and algorithms described herein may be performed in hardware or software executed by hardware, including computer processors and/or programmable circuits configured to execute program code and/or computer instructions to execute the functions, processes and algorithms described herein. Additionally, some implementations may be performed on modules or hardware not identical to those described. Accordingly, other implementations are within the scope that may be claimed.