Personnel risk management system and methods

This application is a continuation-in-part of U.S. patent application Ser. No. 10/947,435, filed Sep. 23, 2004, now U.S. Pat. No. 7,343,303 which is a continuation-in-part of U.S. patent application Ser. No. 09/619,245, now U.S. Pat. No. 6,842,737, filed Jul. 19, 2000, the entire disclosures of which are hereby incorporated by reference as if set forth fully herein.

This disclosure contains information subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent disclosure or the patent as it appears in the U.S. Patent and Trademark Office files or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to a system and methods for risk management; more particularly, the present invention relates to a system and methods for assessing and mitigating risk associated with one or more assets.

2. Background Information

Millions of travelers and people living abroad are afflicted with problems each year, problems involving their health and safety, the timeliness and quality of their trip or assignment, and their familiarity with their trip destination or assignment location. Further, asset managers and security directors must assess and/or mitigate increased risk to assets such as people or facilities caused by a variety of factors such as security threats or transportation issues. These problems cost time, money, and even lives. Whenever a travel problem or in-country threat event occurs, however, typically the information necessary to avoid it, or solve it, is available somewhere, if only the traveler, employee, expatriate, or asset manager had known about it. Thus, there is a pressing need to develop a system which continually monitors the world for pertinent travel- and location-related information, on the one hand, and on the other hand, delivers relevant information to travelers, expatriates, or asset managers when, where, and how they need to use this information.

SUMMARY OF THE INVENTION

The method and system of the present invention have met the above-described needs by providing a method and system for the automated delivery of travel information when, where, and how travelers need it.

The invention provides a method for providing travel-related information to a consumer having a consumer-specific profile. This method includes acquiring information from at least one information source; transforming the acquired information into information pertinent to travel related activities; using rules for applying the transformed travel information to the consumer-specific travel profile; and, creating a product for said consumer indicative of the results of the application of the transformed travel information to the consumer-specific travel profile. A system implementation of this method is also provided in another aspect of the invention. It can be appreciated that the invention can also be embodied in a computer-readable medium.

In a further aspect of the invention, an information system segment is provided that is structured for use in a system for providing travel related information to a consumer with a consumer-specific profile. This information system segment includes a collection subsystem for obtaining information from at least one data source; an analysis subsystem for filtering the obtained information to identify its travel related characteristics; and, a distribution/storage subsystem for directing the filtered data to at least one portion of the system for providing travel related information.

It is therefore an object of the present invention to provide, in one aspect, a system based on five elements: a global operations center, which continuously collects, analyzes, and processes information pertaining to travel from at least one information source; a data store for holding the information; a profiling system, for capturing and maintaining traveler profiles; a rules engine for applying rules pertaining to travel based on the traveler's profile; and a plurality of online products that incorporate and deliver the relevant travel information.

It is a further object of the invention to provide, in another aspect, a continuous creation of information in an intelligence operations center, and its storage in the data store, to provide travel related information on a plurality of global destinations.

It is a further object of the invention to provide, in another aspect, a profiling system that captures a traveler's profile, triggers the application of relevant rules (e.g. if the traveler has a respiratory problem, and the altitude of the destination is sufficiently high, then a warning notice will be retrieved), and retrieves pertinent information from the data store.

It is a further object of the invention, in another aspect, to package travel information in an electronic product and deliver that product in an on-line environment.

It is a further object of the invention to provide, in another aspect, connectivity with an external, global airline reservation system, such that the invention is associated with the act of buying an airline ticket, for example, as well as for boats, trains, and other similar consumer transportation.

Furthermore, embodiments may include receiving travel intelligence from at least one travel intelligence source, receiving asset information from at least one asset information source, and generating a risk assessment report based on the travel intelligence and the asset information.

In addition, embodiments may include maintaining an employee or expatriate profile for one or a group of expatriates and their dependents. Such embodiments may also include receiving travel or location related intelligence from at least one travel intelligence source, maintaining employee or expatriate asset information from at least one asset information source, and outputting risk assessment reports based on the travel or location related intelligence and the asset information.

These and other objects of the present invention will be more fully understood from the following description of the invention and by reference to the figures and claims appended hereto.

BRIEF DESCRIPTION OF THE DRAWINGS

A full understanding of the invention can be gained from the following detailed description of the invention when read in conjunction with the accompanying drawings in which:

<figref idref="DRAWINGS">FIG. 1</figref> is a logical and functional architecture diagram showing an embodiment of the method and system of the present invention;

<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 5</figref> is a flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 6</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 7</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 9</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 10</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 11</figref> is a combined system/flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 12</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 13</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 14</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 15</figref> is a flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 16</figref> is a flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 17</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 18</figref> is a flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 19</figref> is a flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 20</figref> is a conceptual flow diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 21</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 22</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 23</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 24</figref> is a system diagram of an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 25</figref> is a functional flow diagram of a global asset risk management system according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 26</figref> is a flow chart of a global asset risk management method according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 27</figref> is an illustration of a risk assessment determination according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 28</figref> is an exemplary source catalog page according to at least one embodiment;

<figref idref="DRAWINGS">FIGS. 29</figref><i>a </i>and <b>29</b><i>b </i>are exemplary general interactive pages showing general details associated with a source according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 30</figref> is an exemplary comments interactive page showing comments associated with a source according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 31</figref> is an exemplary metadata interactive page showing metadata associated with a source according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 32</figref> is an exemplary contact interactive page showing contact information associated with a source according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 33</figref> is an exemplary source ratings page according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 34</figref> is an exemplary additional intelligence page in at least one embodiment;

<figref idref="DRAWINGS">FIG. 35</figref> is an exemplary reference document page in at least one embodiment;

<figref idref="DRAWINGS">FIG. 36</figref> is an exemplary additional intelligent metadata interactive page showing metadata associated with an additional intelligence source according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 37</figref> is an exemplary additional intelligent ratings interactive page showing source ratings associated with an additional intelligence source according to at least one embodiment;

<figref idref="DRAWINGS">FIGS. 38</figref><i>a </i>and <b>38</b><i>b </i>are exemplary pages of a risk assessment report according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 39</figref> is an example employee profile hierarchy according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 40</figref> is a flow chart of a method for establishing asset information in accordance with at least one embodiment;

<figref idref="DRAWINGS">FIGS. 41</figref><i>a </i>through <b>41</b><i>f </i>are example profile information pages in accordance with at least one embodiment;

<figref idref="DRAWINGS">FIG. 42</figref> is an example Traveler/Expatriate Management interactive page according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 43</figref> is an example employee profile interactive page according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 44</figref> is an example itinerary/assignment interactive page according to at least one embodiment;

<figref idref="DRAWINGS">FIGS. 45</figref><i>a </i>through <b>45</b><i>c </i>are example query results interactive pages according to at least one embodiment;

<figref idref="DRAWINGS">FIG. 46</figref> is an example employee/expatriate personal interactive page in accordance with at least one embodiment; and

<figref idref="DRAWINGS">FIG. 47</figref> is an example world map view report in accordance with at least one embodiment.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Travel Information Logical and Functional Architectures

In the method and system of the present invention, a logical architecture and its corresponding functional architecture are provided that can operate on an Internet-based information exchange medium or another similarly structured and suitable medium. This architecture permits a breadth of information sources from which information related to travel, in particular, can be gathered, transformed and provided to a consumer in the form of a product and/or service.

As used herein, the term “travel-related information” includes any information which is related to a particular mode of travel or travel destination. As used herein, a “consumer” can be an individual, a plurality of individuals, a company, and/or any other entity that uses travel-related information. As used herein, a “consumer-specific profile” can include any information that relates to a consumer's travel preferences, such as, but not limited to, any one or more of the following: destination, mode of travel, health condition of traveler, travel risks associated with a particular destination, and the like. An “information source” as used herein can be any electronic, written, verbal or other source from which data can be derived. A “product” as used herein can refer to a product and/or a service.

Referring now to <figref idref="DRAWINGS">FIG. 1</figref>, in the form of the invention shown, the method and system of the present invention can be represented as five architectural layers that represent data processing from information acquisition to product/service delivery. In the information acquisition layer <b>2</b>, information regarding travel can be acquired from information sources <b>4</b> such as other Internet sites. In performing the function of information acquisition, these information sources <b>4</b> may or may not be partnered with the home Internet site from which travel analysis is delivered to the individual consumer.

Referring again to <figref idref="DRAWINGS">FIG. 1</figref>, in the information transformation layer <b>6</b>, data retrieved from information sources in layer <b>2</b> are processed through at least two logical steps in the method and system architecture: one is an oversight and advisement step <b>8</b> and another is the research and analysis step <b>10</b>. A functional architecture of the invention corresponding to the information transformation <b>6</b> logical architecture can be provided that can be designated as an information validation and recommendations <b>12</b> function. The oversight and advisement step <b>8</b> can include, for example, processing acquired data through a health information board, performing an advisement function, and developing business rules <b>14</b> for treatment of current and future travel data related to health and medicine. The research and analysis step <b>10</b> of the information transformation layer <b>6</b> can include, for example, applying medical information and epidemiology findings from clinic networks <b>16</b> that are researching the status of communicable diseases at a given travel destination. In the information transformation layer <b>6</b>, data acquired is validated and recommendations for further processing of that acquired data through the travel method and system of the invention are developed.

Referring again to <figref idref="DRAWINGS">FIG. 1</figref>, in the information development/application step <b>18</b>, business rules, some of which can be substantially continuously and dynamically generated in the oversight and advisement step <b>8</b> of the method and system, are applied to the travel data. In this step <b>18</b>, factors such as health, security and safety business rules <b>20</b> are determined and applied relative to the acquired and transformed travel data. In the product/service creation step <b>22</b> of the method and system of the present invention, a report is generated <b>24</b> for use by a consumer to evaluate a decision regarding travel to a particular country or region of the world. Also, in this step <b>22</b>, activities such as alert characterization and distribution list development <b>24</b> (discussed in more detail hereinafter) are produced and provided as products/services for the consumer.

Referring again to <figref idref="DRAWINGS">FIG. 1</figref>, product/service delivery <b>26</b> occurs with regard to providing the travel information to a consumer. In this step <b>26</b>, the consumer receives desired information regarding travel to and from a particular location of the world. The product/service delivery step <b>26</b> can be performed through a variety of suitable delivery channels <b>28</b>, including without limitation, the Internet, wireless communication media and apparatus, business intranets, kiosks or other virtual and/or physical locations from which it is desirable for a consumer to request and obtain travel information.

Referring again to <figref idref="DRAWINGS">FIG. 1</figref>, in summary, the functional architecture of the invention is a layered architecture, with five distinct functional layers corresponding to the logical architecture layers. The information acquisition layer <b>2</b> includes a unique collection of travel information sources and a robust set of mechanisms for acquiring varied information sources. The information transformation layer <b>6</b> includes extract, transform, and load sub-processes, and a unique, external application of expert research and analysis. The information development/application layer <b>18</b> includes interactions with subsystems such as alert and event monitoring; extract, transform, and load sub-processes; and external oversight, advisement, and travel business rules development such as by industry experts. The product/service creation/delivery layers <b>22</b>,<b>26</b> include content management and global travel information, including workflow, version control, personalization, and content integration; creation of unique, personalized products based on a combination of personalized travel profile information of the global travel information; and a rich and diverse set of delivery channels.

It can be understood by one skilled in the art that the foregoing logical steps can be applied, for purposes of implementing the method and system of the present invention, to a plurality of functional modules. It can be further understood that the specific functional architecture aspects of the invention described herein are intended to be illustrative, and not limiting, as to the scope of the invention.

Travel Information Technology Implementation Architecture

In summary, referring now to <figref idref="DRAWINGS">FIGS. 2 and 3</figref>, the technology implementation architecture of the invention is a descriptive set of a plurality of technology subsystems or segments, each of which can be considered as part of one of several functional systems: collection <b>32</b>, back office <b>34</b>, content repository <b>36</b>, products <b>38</b>, internet site <b>40</b>, and distribution <b>42</b>. <figref idref="DRAWINGS">FIGS. 2 and 3</figref> illustrate the relationships between and among these different technology segments.

Content Identification Segment (CIS)

Referring now to <figref idref="DRAWINGS">FIG. 4</figref>, a content identification segment (CIS) (<b>51</b>) relates to the initial and ongoing identification of information sources such as internet sites that enhance the products and services provided by the invention. The CIS (<b>51</b>) also enables the determination of sites in use that should, based on subjective or objective criteria, no longer be relied upon for accurate, timely, or value-added content.

Content in the invention can be identified by manual methods performed by subject matter experts (SME's) <b>52</b> or individuals with domain expertise using public search engines, for example. In another aspect of the invention, once a base set of content sources has been established, an automated robot process <b>54</b> can be employed to identify potential sites on a regular basis. To improve their performance, such robot processes can be monitored and reviewed by the SME's <b>52</b> on a regular basis with periodic validation of the criteria driving these robots. In general, the robot process begins by returning identified site lists. Refinements can then be added by applying SME-developed context to text returned by these robot processes.

With this SME-developed context, a high-level classification of the sites returned can be developed. The granularity of robot <b>54</b> returns be fairly coarse initially, and more finely grained as identification techniques are honed. Likewise, the levels of classification of robot <b>54</b> returns can be limited, with additional levels added as identification techniques are honed. Multiple levels of robot activity can therefore be implemented in accordance with the invention.

A blanket robot can exist, for example, that combs the web simply for the word “travel,” then discards duplicate hits or hits outside of &lt;Title&gt; or &lt;meta&gt; tags. Ultimately, these robot processes may evolve to several robot processes that can look for specific occurrences of the word “travel” in conjunction with other words (e.g., “health”) in very specific structural elements of the document (e.g., only if both words occur in both the &lt;title&gt; tag and in &lt;meta name=keywords&gt; tag). It can be appreciated that the robot technology can also be effective for non-HTML sources, provide mechanisms for natural language queries, and can be able to route hit returns substantially automatically to specific SME's <b>52</b>.

Content Acquisition/Aggregation Segment (CAAS)

Referring now to <figref idref="DRAWINGS">FIG. 5</figref>, in the invention a CAAS (<b>71</b>) defines the processes by which identified content (see CIS (<b>51</b>) discussion above) is acquired and classified as belonging to a specific domain, then stored in a format by which the content management system (see CMS (<b>131</b>) discussion hereinafter) can use.

The CAAS (<b>71</b>) includes developing agents <b>72</b> to retrieve identified content from an information source <b>74</b> and implementing a scheduling mechanism <b>76</b> to initiate these agents. In general, content acquisition schedules <b>76</b> range from completely static (e.g., a single agent initiation for the power requirements in France) to hourly (e.g., a five-day weather forecast for Paris). Notification agents <b>78</b> can also be developed and scheduled for initiation at regular intervals. These notification agents <b>78</b> can inform content acquisition personnel that a particular content source has changed in content or structure.

If a relatively simple change in content is indicated, the acquisition agent <b>72</b> can be manually initiated to bring in the latest content for a given information source <b>74</b>. Integration with the Administration Segment (ADMS) (<b>181</b>) (discussed hereinafter) is required for this process, as an initial acquisition agent schedule <b>76</b> is sparse until the frequency at which site content changes is understood. If a notification agent <b>78</b> returns information on a content structure change, for example, content management personnel can modify the corresponding acquisition agent <b>72</b> so that the change content is correctly acquired. In addition, an environment can be created whereby SME's can create ad hoc acquisition and notification agents for alert purposes. In another aspect of the invention, the modification of acquisition agents <b>72</b> can be automated and based on the return information of notification agents <b>78</b>. It can be appreciated, however, that some manual oversight is desirable in this process.

Content Repository Segment (CRS)

In the invention, the content repository segment (CRS) <b>91</b> stores, manages, and distributes substantially all acquired travel information that is considered persistent.

Referring now to <figref idref="DRAWINGS">FIGS. 6 and 7</figref>, the content repository can be considered a “hub” for content and data. Although the content repository <b>91</b> includes both relational and object XML data stores <b>92</b>, it can be accessed and managed through a central mechanism and driven by a single engine <b>94</b>. The content repository <b>91</b>, as shown, can provide facilities to store, view, import, organize, modify, export, and query travel-related information. It can include one or more physical data stores <b>92</b>,<b>96</b>,<b>98</b>,<b>100</b>,<b>102</b>,<b>104</b>,<b>106</b>; the data engine <b>94</b>; an integrated tool set for development; and, a centralized management facility <b>108</b>.

It can be appreciated, in an alternative aspect of the invention, that the content repository <b>91</b> could support extended data types including user-defined types and extended data types of audio and video. The content repository <b>91</b> can also include portions of the application of business logic in the data model.

In one embodiment of the invention, the content repository comprises several technological components. A component environment is a dedicated content object layer. An application server <b>93</b> is provided that stores and processes data access/storage components <b>95</b>. Services are enabled with Java Database Connectivity (JDBC) and open database connectivity (ODBC) drivers. An object request broker (ORB) is also employed (an object request broker) to manage object-to-object messaging and inter-ORB communications. The XML object engine <b>94</b> stores/retrieves XML objects from data stores <b>92</b>,<b>102</b>,<b>104</b> and has functionality based on schemas stored in a data map store <b>102</b>. An XML parser <b>110</b> is included that checks syntactical correctness of schemas in the data map store <b>102</b> and ensures the formation integrity of incoming XML objects. An object processor <b>112</b> is included as a component to physically store XML data in the XML store <b>92</b>. A query interpreter <b>114</b> resolves XML Query Language (XQL) requests and interacts with the object composer <b>116</b> to retrieve XML objects according to the schema stored in the data map store <b>102</b>. The object composer <b>116</b> is provided to construct the information objects, based on storage and retrieval rules defined in the data map store <b>102</b>, and return them as XML documents. There are also various utilities in this embodiment, including those that support directory and tree-oriented loading of XML objects. An external storage integration component (ESIC) (<b>118</b>) permits applications to access data regardless of database type or location.

The data map (meta data) store <b>102</b> serves as the content repository's <b>91</b> knowledge base. The data map store <b>102</b> contains the schemas that hold the rules according to which XML objects are stored and composed, such as: (1) storage and indexing of XML objects within the content repository, (2) mapping of data to different data structures to enable the integration of existing data, and (3) executing user-defined application logic with a server extension function associated with an object. An SQL engine <b>120</b> manages an internal SQL store <b>104</b>; executes SQL statements; and, accepts SQL statements in a number of ways: internally, from the object engine <b>94</b>; from applications, which can be either embedded or through standard database interfaces such as ODBC (<b>122</b>), JDBC, or OLE-DB (<b>124</b>); and, from the content repository manager <b>108</b>. The CR manager <b>108</b> provides an administration tool implemented as a graphical user interface (GUI) that runs in standard web browser. In addition, server extensions permit user-defined functions to be incorporated into the content repository <b>91</b>.

Content Management Segment (CMS)

Referring now to <figref idref="DRAWINGS">FIG. 8</figref>, in the form of the invention shown, a content management segment CMS (<b>131</b>) can be defined by the processes and technologies by which content is managed. Content management technologies include content and design control, contributor/user access control, site control, asset control, publication, and workflow. A universal (i.e., generic) presentation format can be developed, along with XML document schema, and content binding to page layouts can be implemented. Substantially all content, including text, graphics, styles, themes, and other assets, can be stored as objects in a high-performance relational database. For performance reasons, all content provided by the invention, as presented to a content consumer, comprises static pages in flat file systems. This content can be dynamically generated on an as-needed basis (e.g., one particular page every minute, one particular subset of pages every week, and the like).

After initial implementation, interaction with ADMS (<b>181</b>) and CRMS determines style and design modifications. In another aspect of the invention, implementation of ancillary services such as advertising management and syndication mechanisms can be incorporated into the invention. It can be appreciated that content can be translated and global sites can therefore be developed in English, Spanish, German, French, Japanese and other suitable languages to which the invention can be adapted.

Travel Information Report Segment (TIRS)

Referring now to the figures, in another embodiment of the invention, a travel intelligence report (TIR) can be generated that includes trip information necessary to make informed decisions regarding pre-travel preparation and enhancement and enjoyment of travel related activities. In one aspect of the invention, the TIR can be divided into four major sections: Pre-Trip Information, Destination Information (for one or more destinations), General Advice, and Products and Services. Within each section is a set of information categories, each of which contains several information requirements. Each of these requirements can be customized to (1) the traveler, based on his/her personal profile, (2) destination, and (3) related issues such as season of travel.

The Pre-Trip section travel categories include Alerts, Entry/Exit Requirements, and Pre-Trip Health considerations. Alerts may include, but are not limited to, Safety/Security, Weather, and Transportation. Entry/Exit Requirements can include all legal, health, and custom issues that are important for entering and leaving a particular destination. The Pre-Trip Health section can also include required and recommended immunizations, health risk considerations, and the like.

Typical travel categories and information requirements in the Destination section includes, but is not limited to:

1. Safety/Security: Social Stability, Crime, Airline, Game Parks

2. Weather/Environment: Climate &amp; Terrain, Natural Risks, Environment, Weather Chart &amp; Forecast

3. Transportation: Air Travel, Water Transportation, Road/Overland Travel, Taxi, Mass Transit, Train Travel, Rental Cars

4. Money: Cash &amp; Credit, Taxes, Cost of Living

5. Telecommunications: Phone/Electric, Internet, Contact Information, Mail, Radio

6. Social Customs: Behavior, Religion, Women's Issues, Business Hours, Public Holidays &amp; Events

7. Legal: Prohibited Items, Penalties

8. Language: Official Language

9. Health: immunizations, nearest hospital, health insurance, health risks

One feature of the TIR is that it can be a hyperlinked report. Consumers have the ability to expand or contract particular information requirements to see detail or concise descriptions for a given TIR, information which has come directly from the global operations center. The TIR can be printed directly from a browser, or saved in a variety of electronic formats, but it is also “alive” in the sense that a traveler can return to it online at anytime up to thirty days after the conclusion of his trip and access the latest information based on his profile. In fact, if an alert level event occurs during the life of the report it will trigger the transmission of an e-mail (or other push technology) warning from the report to the traveler. In this way the report, and the operations center behind it, become the traveler's own personal intelligence agency.

The TIR can also include a rating (such as from 1 to 5 in tenth increments, for example), which is a weighted-average of the total risk of the trip represented by the TIR as determined by criteria applied to the travel data in the TIR. This rating can be illustrated, for example, by a series of “jet” graphics printed on the TIR.

Member Personalization Segment (MPS)

Referring to <figref idref="DRAWINGS">FIGS. 9 and 10</figref>, a member personalization segment (MPS) (<b>151</b>) defines the functions and processes by which the products and services of the invention are personalized to a specific consumer. In addition to personalization of product/service offerings, the MPS (<b>151</b>) provides a mechanism to apply targeted marketing to the travel community.

The MPS (<b>151</b>) includes, for example, the following information: static, stored personal information; name recognition <b>152</b>; and, user-provided information <b>154</b>. In one aspect of the invention, a personalization business rules engine <b>156</b> interacts with this information, along with input from business rules frameworks applied to ISS (<b>351</b>). It can be appreciated that the information sophistication level can increase to provide the following processes: content consumption measurement <b>158</b>; adaptive content and navigation; predictive modeling <b>160</b>; segmentation; and behavioral personalization.

Billing Segment (BIS)

Referring to <figref idref="DRAWINGS">FIG. 11</figref>, a billing segment (BIS) (<b>171</b>) can be employed to define the billing and payment architecture for products and services provided by the invention. The BIS (<b>171</b>) can be associated with the TIR's and channel partners (e.g., e-Ticket TIR). Billable activity can also be captured within the distribution segment (DIS) (<b>190</b>) then routed to BIS (<b>171</b>) and CR<b>5</b> (<b>91</b>) (for updating partner detail records and consumer detail records.

In one aspect of the invention, BIS (<b>171</b>) includes, for example, the following functionality: rules-based messaging to tailor invoicing for specific partners; e-mail based invoice presentation, with a secure uniform resource locator (URL)-link back to the invention internet site for invoice details; a comprehensive customer-care system for issues such as dispute management; an ability to implement prearranged payment plans; and, flexible payment processing, including payment returns and payment confirmation. It can also be appreciated that credit card payments can be accommodated by the invention.

In another aspect of the invention, a cost model for alerts can be determined based on factors such as (1) alert level, (2) number of delivery channels, and (3) type of delivery channel.

With regard to syndication of content, a cost model can be developed for the invention to accommodate granular syndication requirements. For example, one partner may choose to syndicate the entire invention content, while another partner may choose a vertical (e.g., information requirement) or horizontal (e.g., geographical) subset to such syndication. Also related to CMS (<b>131</b>) are the requirements associated with localization. For example, if a channel such as the internet site of the invention is localized for a foreign country, currency considerations are an important consideration.

In another embodiment of the invention, to satisfy these additional requirements, a multi-service BIS (<b>171</b>) considers the following: volume tiering, discounting, multi-format invoicing, billing-on-demand (including threshold, activity-based, and billing in advance), and direct debit processing. In an alternative embodiment of the invention, the billing function can be out-sourced to a service provider.

Administration Segment (ADMS)

Referring now to <figref idref="DRAWINGS">FIG. 12</figref>, an administration segment (ADMS) (<b>181</b>) defines the administration and reporting necessary to maintain a robust, active set of systems and a proactive approach to determining return on investment (ROI) on system processes. Management of the systems of the invention can take place internally such as by personnel, externally by the INFS provider, and/or externally by a management service provider <b>182</b>.

Internally, structured reports are used to measure ROI of several processes, including internet site analysis (navigation, content consumption, activity paths, and the like) and content acquisition ROI. Ad hoc mechanisms <b>184</b> can be used for targeted data mining and analysis. Key elements of this internal reporting mechanism are the determination of content acquisition cost vs. content use (i.e., ROI of destination-specific products).

Externally, base operating system (OS)-level functionality can be managed by collocation FNFS partner(s). This functionality includes security, redundancy, load balancing, and the like. By placing a management service provider client <b>186</b> between the invention's internet site application services <b>188</b> and the DIS (<b>190</b>), one can also manage process, transaction, and infrastructure issues.

In addition, a plurality of metrics can be captured and analyzed. Process metrics include end-to-end transaction response times, actual transactions: target transaction ratio, start-to-finish transaction ratios for key business processes, availability or service level agreement (SLA)-ratios of partners. Transaction metrics can include activity response times, including product (e.g., TIR's, EAS (<b>201</b>)) production and distribution, session ID transaction information, performance based on volume of product creation/distribution, replication updates per unit time (including product, email, etc.).

Infrastructure metrics can include web server metrics, including connection rates, connected users, data transfer rates, and number of connections, database metrics, including database transactions, file sizes, deadlocks, memory cache hit ratios, memory optimization, user logins, logout rate, and user connections; and, server metrics, including packet traffic, queue size, disk and memory utilization, and session errors.

Event/Alert Segment (EAS)

Referring now to <figref idref="DRAWINGS">FIG. 13</figref>, an event/alert segment (EAS) (<b>201</b>) is responsible for the identification, selection, management, and distribution definition of events and alerts. The EAS (<b>201</b>) can support both manual and automated systems. The manual systems permit an Analyst, for example, to generate an Alert and forward it to the EAS (<b>201</b>) for processing. The EAS (<b>201</b>) can process an Alert by queuing it in priority order to a selection system operated by an Event Reporting Analyst. Alerts are reviewed to ensure that the system does not flood the distribution network with low grade or otherwise relatively insignificant Alerts. The Analyst can modify both the Alert content and attributes (duration, region of interest, level, and the like). An Alert can be sent back to one or more designated Analysts for review and comment as a high priority message. Once the Event Reporting Analyst releases an Alert, the EAS (<b>201</b>) determines the applicable members and establishes the distribution orders for the Alert. This information is passed to the Distribution Segment (DIS) (<b>190</b>) to perform transmission of the Alert to various distribution networks, such as by pager, e-mail, and other suitable communication avenues.

In another aspect of the invention, automated systems can be deployed that perform keyword spotting and category analysis to identify potential candidate content for Alert generation. Keyword spotting involves scanning incoming content for specific keywords or combination of keywords using regular expression analysis defined in a Keyword Dictionary. Examples of such keywords for Alert reporting are “hurricane”, “strike”, and the like. Other keywords would include specific names of countries, airlines, and the like.

Once keywords are identified, Category Analysis is used to determine who should review the content. For example, a message with “France”, “United” and “strike” could be automatically routed to the European Desk Analyst and the Transportation Domain Expert as “high priority” content for review.

The method and system of the invention addresses the need to provide multiple Event Reporting Analysts as a role. This role can be passed from shift to shift, and there can be multiple Event Reporting Analysts operating concurrently. If there are multiple Event Reporting Analysts operating, the system can maintain a single, global work queue but resist multiple Event Reporting Analysts from working the same Alert simultaneously.

An important aspect of this embodiment of the invention is the ability to identify, review and select events for Alert reporting. Alerts can have, for example, three (3) levels of significance. A Level 1—High Priority/Critical Alert could be considered one that can directly impact the health, safety, or schedule of the traveler. Examples of Level 1 Alerts could include weather alerts, flight delays and cancellations, actual strike actions, and the like. A Level 2—Medium Priority/Warning Alert relates to information that may have an impact on the health, safety or schedule of the traveler. Examples of Level 2 Alerts include imminent weather conditions, strike advisories, social unrest, airport facility issues, and the like. A Level 3—Low Priority/Informational Alert is related to information that the traveler should be aware of about his/her trip. Examples of Level 3 Alerts can include major events being held at a given destination, financial situations such as money valuation issues, visits of a major head of state, and the like.

In another aspect of the invention, the EAS (<b>201</b>) technology is a subset of ISS (<b>351</b>) technology (discussed hereinafter).

E-Commerce Segment (ECS)

Referring now to the figures, an e-commerce segment (ECS) of the invention provides the consumer with the opportunity to purchase travel associated products, that can be appropriately matched with the consumer's travel itinerary and profile. The ECS can be implemented as conventional hyperlinks at the end of a TIR: these links can be generic and/or targeted to the consumer based on predetermined criteria (e.g., season, destination country). These links are preferably only linked to the source provider for the product.

In another aspect of the invention, targeted contextual e-commerce can also be implemented on the TIR. This contextual e-commerce can be member profile-specific and combined with trip specifics to recommend particular products to the consumer. The consumer can then be linked and transacted through specific channels of the internet site for the invention. It can be appreciated that, instead of dedicated ecommerce platforms being incorporated to implement this type of e-commerce, content agents from CAAS (<b>71</b>) can be used, along with the BIS (<b>171</b>), to achieve this level of e-commerce. This contextual e-commerce can be combined with the internet site of the invention, such as on the personalized “My” internet site section. In addition, the internet site of the invention can employ order fulfillment as a function and service for the consumer.

Customer Relationship Management Segment (CRMS)

A customer relationship management segment (CRMS) (<b>221</b>) of the invention relates to interaction among consumers, site users, and internet site customer service. The CRMS (<b>221</b>) provides a forum in which site users can correspond with a central point of contact (POC) for providing comments and suggestions on products and services provided by the internet site. This feedback can be provided by conventional e-mail links and toll-free telephone numbers, for example.

The CRMS (<b>221</b>) is a virtual contact center, with workflow, routing, queuing, automated e-mail return, single-click email response, and the like. Incoming requests can be automatically comprehended and classified using message content. A response can be automatically composed with an appropriate reply and data can be retrieved to complete and personalize the response. Responses can then be either automatically sent or routed to a review agent or agents who can then send them to the consumer after examination.

In another aspect of the invention, a web-based self-service solution can be implemented that recreates the experience of working with an expert customer service representative.

In addition, an online community can be established by developing discussion forums and a comprehensive knowledge base. In connection with this knowledge base development is a process whereby content suggestions are automatically routed to SME's for analysis and inclusion in the content store.

In another aspect of the invention, CRMS can also include targeted feedback campaigns and e-mail solicitations. The CRMS can be integrated with the ADMS (<b>181</b>) (for metrics relating to customer activity, retention, and referrals), the MPS (<b>151</b>) (to provide customer-provided input and behaviors for personalization), the MOIS (<b>261</b>) (for establishing additional marketing opportunities), the BIS (<b>171</b>) (for billing customer care), and the PRMS (<b>241</b>) (to share technologies and processes). Live person type support can also be out-sourced after a predetermined number of inquiries are noted.

Partner Relationship Management Segment (PRMS)

Referring now to <figref idref="DRAWINGS">FIG. 16</figref>, in the invention, a partner relationship management segment (PRMS) (<b>241</b>) can encompass both partner lifecycle management and extended enterprise selling. The PRMS (<b>241</b>) can be centered on CHAMPS (Channel and Alliance Management Process) <b>242</b> and can concentrate on two areas. Initially, partner lifecycle management can be implemented. This can include partner profiling, partner recruitment, and partner performance monitoring. Integration with MOIS (<b>261</b>) and ADMS (<b>181</b>) is important to implementing this segment.

Enterprise selling can also be addressed. This can include lead assignment, lead distribution and tracking, pricing/quoting, and literature fulfillment. Integration with BIS (<b>171</b>), MOIS (<b>261</b>), and ADMS (<b>181</b>) can be required, as billing customer care and consistent forecasting and reporting can be used:

Lead Assignment—Assigning qualified leads to the right partners at the right time is an important task. Managers can graphically enter business rules for building “decision trees” that decide which partner is assigned each lead. Rule options can include, for example, named accounts, score and qualification-based assignment, and checking to see if a partner is working on another lead in the same account. Multiple lead decision trees for different business models can be supported, as well as optional manual assignment, and lead posting to a pool of partners.

Partner Profiling—Information contained in the partner profile database can enable distributed management of users, customized content, push delivery, and online partner recruitment. This database can store profiles for both individual partners and partner organizations. An organizational profile can include information such as industry focus, location, organizational structure, product authorized to sell and accounts serviced. Individual profiles cover, for example, contact information, certification level, and previous performance.

Channel Partner Recruitment—A challenge for channel managers is the need to recruit qualified channel partners. Channel partner recruitment provides a set of tools to facilitate this recruitment process. Channel managers are able to modify their partner qualification criteria according to the existing partner profiles as well as the current organization needs. Potential partners can be tracked through the recruitment process and analysis can be conducted to determine the optimal way to attract the maximum number of qualifying partners.

Channel Communication—Channel communication can be based on two libraries: a distribution list library and a campaign template library. The distribution lists can be created from the partner database and are able to be filtered by type of partner, level of partner, or other criteria. Lists can be saved (either as a description or as a list of actual partners) and used for future campaigns. The campaign library can allow the marketing user to create new items, such as product announcements or event reminders, based on standard designs. Once the literature is created, the system can then distribute the item to the desired distribution list. Recipients' profiles can be automatically updated to note the information received, and the system monitors and reports on responses.

In an alternative embodiment of the invention, PRMS (<b>241</b>) activity can be coordinated with suitable marketing or sales out-sourcing partners.

Distribution Segment (DIS)

Referring now to the figures, the distribution segment (DIS) (<b>190</b>) is responsible for taking a distribution order and executing it. A Distribution Order can include the item to distribute (i.e., Alert, TIR, etc.) and where to distribute it (i.e. list of e-mail addresses, pager numbers, etc.). The DIS (<b>190</b>) can parse the distribution order and forward it in portions to various distribution systems. These distribution systems can include e-mail, pager, facsimile, wireless, and the like.

The DIS (<b>190</b>) provides advantages with regard to error handling. If a transmission fails, for example, the invention provides a way to link this information back to the consumer's profile with an explanation of why there was an error. For example, status=XMIT ERROR, “invalid e-mail address: paul@ijet.com”.

In another aspect of the invention, the DIS (<b>190</b>) can include an interactive voice response (IVR) capability. Using an IVR System, for example, a member can dial a telephone number (800, 900 or direct) and enter his/her member number and personal ID number (PIN) security code to gain access to his/her account. Using the IVR System and a series of selection options, the member can retrieve Alerts, TIR updates, etc. For example, “Press 1 for Alerts”, “Press 2 for a TIR Update”, “Press 3 for Options”, “Press 4 for a Person”, etc. If the member presses “1”, the system can move to a second level, dynamic menu of options based on the active Alerts for the member. The Alerts can be listed in priority order with unread Alerts prioritized first. The system can, for example, list the Alerts “Press 1 Air Canada Strike”, “Press 2 Snow Storm Hits Montreal”, and the like. The member can select an entry at any time without listening to the entire list. By entering a selection, the system can read the selected entry. The member can select Back, Next, Pause, or Replay at any time while the message is being played.

Marketing Opportunity Identification Segment (MOIS)

Referring now to <figref idref="DRAWINGS">FIG. 18</figref>, a marketing opportunity identification segment (MOIS) (<b>261</b>) of the invention shares the technology base of the CIS (<b>51</b>) and conducts the initial and ongoing identification of sites that present marketing and partner opportunities. In one embodiment, once a base set of marketing opportunities has been established, an automated robot process can identify additional potential opportunities on a periodic basis. The robot process can be monitored and reviewed by marketing personnel on a periodic basis, and the criteria which drives these robots can be periodically validated.

This robot process can return identified opportunity lists. Refinements can be added by applying marketing-developed context to returned text. With this marketing-developed context, a high-level classification of the sites returned can be developed. The granularity of robot returns can be fairly coarse initially, and more finely grained as identification techniques are honed. Likewise, the levels of classification of robot returns can be fairly limited or have additional levels added.

In another aspect of the invention, multiple levels of robot activity can be implemented. A blanket robot can be employed, for example, that searches the internet for the word “travel,” then discards duplicate hits or hits outside of

&lt;Title&gt; or &lt;meta&gt; tags on internet sites that are searched. Another robot process can be utilized that looks for specific occurrences of the word “travel” in conjunction with other words (e.g., “booking”) in specific structural elements of a searched site (e.g., only if both words occur in both the &lt;title&gt; tag and in &lt;meta name=keywords&gt; tag). Such robot processes can also be applied to non-HTML sources, can provide mechanisms for natural language queries, and can automatically route hit returns to marketing personnel or out-sourced marketing/sales organizations affiliated with the internet site of the invention.

In an another embodiment, MOIS (<b>261</b>) information can be funneled to out-sourced sales and marketing resources and/or the PRMS (<b>241</b>).

Yellow Book Online Segment (YBOS)

Referring now to <figref idref="DRAWINGS">FIG. 19</figref>, in another aspect of the invention, the yellow book online (YBO) (<b>281</b>) can be provided as a segment including an electronic version of the CDC's Health Information for International Travelers. The YBO (<b>281</b>) can be a verbatim translation of the print version, with a full-text search and retrieval mechanism. In another embodiment, the YBO content can be syndicated to other internet sites via the use of a direct search link to the YBO (<b>281</b>) on the internet site or through a content window displayed directly from the internet site.

In another aspect of the invention, further employment of the YBO (<b>281</b>) can include enhanced input conditions for a search (e.g., full-text search only on a specific country) and enhanced output (e.g., optional summaries of page “hits”). The Yellow Book Online will provide the core health information for the system.

Web Segment (WEBS)

Referring now to <figref idref="DRAWINGS">FIG. 20</figref>, a web segment (WEBS) (<b>301</b>) of the invention as shown represents the situation where the internet site is a distribution channel for its content, products and services.

Technology Infrastructure Segment (INFS)

Referring now to <figref idref="DRAWINGS">FIG. 21</figref>, in another aspect of the invention, an infrastructure segment (INFS) (<b>321</b>) is provided that includes an operations center and a staging center along with a collocated site in, for example, the United States, Europe, Africa and other suitable international locations. In this embodiment, the primary information activity occurs at an internet site headquarters <b>322</b> with an operations center <b>324</b>. This information activity can then be staged to a staging center <b>326</b>, and then replicated to one or more of the collocated sites <b>328</b>,<b>330</b>,<b>332</b>.

In another aspect of the invention, an archive center <b>334</b> can be created at the internet site headquarters. This archive center <b>334</b> can store all travel information activity, including historical, administrative, and metric data. This archive center <b>334</b> can also be integrated with the ISS (<b>351</b>) so that business information mining and new product creation can be supported.

It can be appreciated that these collocation services can be top-tier, including caching network operations and RAIS (redundant array of independent systems) in a load-balanced environment. Services can include, but are not limited to, the following: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0167">Bandwidth Services</li><li id="ul0002-0002" num="0168">Multi-line local area network (LAN) Connection</li><li id="ul0002-0003" num="0169">Reporting Services</li><li id="ul0002-0004" num="0170">Proactive, Multi-Channel Notification</li><li id="ul0002-0005" num="0171">Bandwidth Reports</li><li id="ul0002-0006" num="0172">Network Caching</li><li id="ul0002-0007" num="0173">Managed Monitoring Services <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0174">Network Monitoring</li><li id="ul0003-0002" num="0175">URL Monitoring</li><li id="ul0003-0003" num="0176">Reboot Service</li></ul></li><li id="ul0002-0008" num="0177">Multi-path Services</li><li id="ul0002-0009" num="0178">Data Vault Services</li><li id="ul0002-0010" num="0179">Security Services <ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0180">Intrusion Detection</li><li id="ul0004-0002" num="0181">Vulnerability Analysis</li><li id="ul0004-0003" num="0182">Managed Firewall</li></ul></li></ul></li></ul>

Information System Segment (ISS)

In one embodiment of the invention, an information system segment (ISS) (<b>351</b>) has three functional subsystems: Collection, Analysis, and Distribution/Storage.

In the invention, the Collection subsystem centers on an analyst or SME who has domain or geographic expertise. Standard content feeds for his/her domain are substantially continuously being examined, as is existing content in the CRS (<b>91</b>). In addition, more focused content is captured by ad hoc queries through both the CIS (<b>51</b>) and the CAAS (<b>71</b>). These queries can be run through a machine translator prior to content acquisition if specialized, foreign language content resources are presented as information sources. In addition, based on return set content, machine translators can also be used prior to CRS (<b>91</b>) storage. Analysts/SME's can also use an RSS Aggregation Module. This module can allow each analyst/SME to develop his/her own, personalized set of headline content that can be scanned on a regular basis.

The CRS (<b>91</b>), outside of its standard data structure, has pre-applied templates that ensure the validity of information returned in analyst/SME queries. These templates are in the form of rules frameworks that are defined by partners such as a Health Information Board (HIB). The Collection subsystem relies on the interfaces between CRMS, PRMS (<b>241</b>), and MPS: Partner and Member activity history and itinerary information can contribute greatly as a background to information activity. Also key to the Collection subsystem is a collaboration network that the analyst/SME participates in with other analysts/SME's. Using the collaboration network, queries and return sets can be analyzed by more than one analyst/SME to ensure validity.

In the invention, the Analysis subsystem operates with a marshaled query on information returned by the Collection subsystem. Such queries can be done, for example, by using meta data searches, with On-Line Analytical Processing (OLAP) tools, or using conventional pattern recognition technologies. Return sets from these initial analysis queries are filtered through two pipes: a filter pipe and an index pipe. The filter pipe applies semantics to incoming signals based on meta data associated with them. If this approach is unsuccessful, semantic application can be attempted based on content. Feature extraction can next be performed to ensure that any semantic application considers multi-semantic issues. The index pipe attempts to index incoming signals based on keywords, thematics, and hierarchical clustering.

At least two key elements are associated with the filter and index pipes. The first is operational qualification agents. These agents capture specific, pre-determined linguistic patterns and can be event-based or schedule-based. Once an operational qualification agent captures a signal, the signal is classified and moves on through the system without proceeding through additional filtering and indexing.

Both the filter and index pipes are dynamic mechanisms, which are not only modified manually, but “learn” through the application of an analysis engine. This analysis engine is a network of adaptive fuzzy feature modules (AFFN's) that collectively comprise an adaptive temporal correlation network (ATCN). AFFN's and ATCN's provide managed artificial information and capture patterns and correlations between linguistic elements that are either too time-intensive for humans to capture or practically impossible without computational assistance.

Once a signal has morphed into an information block (i.e., it has some classification associated with it), the block itself can be considered information or, in the case of misclassification, remain information without attached semantics. At this point, the analyst/SME either validates the information or adds semantics to the information. This can be done through using the information block as input to additional mechanisms in the Collection subsystem, or using the collaboration network and additional analysts/SME's to reach a consensus.

In the invention, aggregated information is classified again as supplemental content or as an alert. If it is classified as supplemental content, the aggregated information is forwarded to the CMS (<b>131</b>), where the content manager filters it through an editorial process. At this point, the supplemental content can be discarded, accepted as is and sent to the CRS (<b>91</b>), or sent back to the analyst/SME for additional analysis. If the aggregated information is classified as an alert, it is sent to an alert framework, along with its meta data. Additional meta data is assigned (e.g., data/time, GIST, alert type) and then concomitantly sent to CRS (<b>91</b>) and distribution list development.

In summary, the method and system of the present invention offer a travel information functional architecture that defines and supports gathering, analysis, storage, and personalized product/service delivery of accurate, comprehensive, and personalized travel information. The method and system of the invention provide a breadth and richness of information sources and acquisition, sophistication of external oversight, advisement, and business rule development processes applied to travel information development, diversity of product and delivery mechanisms, and a comprehensive application of supporting business and technology architecture. The result is an online intelligence agency that both feeds into and is driven by the global airline reservation system.

The following example is intended to be an illustration of certain embodiments of the invention and is not intended to limit the scope of the invention:

An Example of the Travel Information System

The travel information system operates in three distinct phases.

In phase one, information is collected from online sources and analyzed by regional analysts. These analysts screen the information, iron out discrepancies, edit and format the information, and send it to the data store.

In phase two, a traveler enters the system through one of many distribution points in the travel industry. An example would be a traveler who decides to purchase a Travel Intelligence Report (TIR) while purchasing an airline ticket from a travel web site. After purchasing the ticket, the traveler is presented with an online profile form, which is already populated with the traveler's client record and e-ticket information, forming the core profile; he can either accept this profile with a single click, or supplement it with more information. In either case this profile form is transmitted online to the internet site, where it triggers the application of appropriate rules, and the retrieval of pertinent content from the data store.

In the third phase, this content is then assembled into a TIR and delivered to the traveler. The traveler can then print and/or download the TIR. At any point up to 30 days after his return the traveler can also pull up the report online and view the latest version. If any significant changes occur to the underlying information, the report e-mails the traveler. In addition, if the traveler has purchased a separate wireless alert product, the traveler can be notified on his wireless platform.

Global Asset Risk Management

<figref idref="DRAWINGS">FIG. 25</figref> is a functional block diagram of a global asset risk management system <b>400</b> according to at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 25</figref>, the global asset risk management system <b>400</b> may include at least one travel intelligence source <b>401</b> and at least one asset information source <b>402</b>. The travel intelligence source(s) <b>401</b> may include the CIS <b>51</b> and CAAS <b>71</b>, or the intelligence or information associated with the CIS <b>51</b> and CAAS <b>71</b>, as described herein. For example, the travel intelligence source(s) <b>401</b> may include a notification of an event or evolving security situation that creates an increased risk for nearby assets. In an embodiment, the asset information source <b>402</b> may include company proprietary asset information such as, for example, but not limited to, geographic location information for company employees or facilities. In at least one embodiment, the geographic location information may include an objective set of coordinates identifying the location of the asset(s) (e.g., facilities, office locations, or personnel). For example, the geographic location information may include the current or a recent set of Global Positioning System (GPS) coordinates. Furthermore, the geographic location information may include the current or a recent set of coordinates from a Geographic Information System (GIS). In at least one embodiment, the system <b>400</b> may include an expatriate management module embodied using a sequence of programmed instructions to configure the system <b>400</b> to perform employee or expatriate risk management as described herein.

In at least one embodiment, asset information may include for example, but not limited to, information for traveling employees who are traveling to, from, or through and/or are present in a country outside their home country (e.g., country of citizenship) for a relatively short period of time (e.g., a current travel situation), as well as employees who are present in a country not their home country for an extended period of time. As referenced herein, a “trip” may be associated with a traveler or a current travel situation, while an “assignment” may be associated with a long-term stay in a country that is not the home country. Further, an employee with an assignment for a long-term stay in a country other than the home country for an extended period of time may be referred to as an expatriate. Thus, in an embodiment, an employee may be associated with a trip or an assignment, or both. An employee who is associated with a trip may be a traveler. An employee who is associated with an assignment may be further categorized as an expatriate, a Very Important Person (VIP) such as, for example, an executive, or a dependent. A dependent may be a family member or relative of an employee who also present in a country other than their home country for an extended period of time. In at least one embodiment, the asset information may include a link or attribute to associate a dependent with an employee.

Furthermore, multiple employees, of any of these types, may be associated by the system into one or more groups based on one or more common attributes. For example, a group of employees traveling together to a meeting or a conference may define a group. In at least one embodiment, the system may output a report indicating the total number of employees and their dependents in a given location. The system may thus provide the user with the capability to immediately determine the number of people affected by an event or threat, as well as the total number of people to be transported should evacuation be necessary.

In an embodiment, the system may provide for establishing and maintaining an employee profile. For example, the employee profile may be included with and maintained as asset information. For an Expatriate (EXPAT) employee, the employee or expat profile may include detailed personal information on the Expatriate or Expat Dependent required in the event of an incident (i.e., accident, kidnap, death, etc.) or for overall proactive risk management needs. The employee may be responsible for maintaining his information current in the asset database. In at least one embodiment, the employee profile may be hierarchical such as the example employee profile shown in <figref idref="DRAWINGS">FIG. 39</figref>. Referring to <figref idref="DRAWINGS">FIG. 39</figref>, the hierarchical employee profile <b>3900</b> may include four levels, for example. The first level, the Primary Profile <b>3901</b>, may be the default profile in the system. This typically represents the employee's home base contact information and key travel related information such as Passport, Citizenship, etc. The next level profile is the Trip/Assignment Profile <b>3902</b>. For expatriates, VIPs, and Dependents, the Trip Profile <b>3902</b> may include assignment information. The Trip/Assignment Profile <b>3902</b> may override the Primary Profile <b>3901</b> with information that is unique for a given trip or assignment such as a rental cell phone number or specific emergency contact information. The third level profile is the Leg Profile <b>3903</b>. The Leg Profile <b>3903</b> may override both the Trip/Assignment <b>3902</b> and Primary Profiles <b>3901</b> and contains information specific to that leg of the trip. For example, local business offices contact information, local cell phone rental, etc. For expatriates, the employee profile may include additional Expat Profile <b>3904</b> data elements such as, for example, photo, handwriting samples, etc. Some of this data may be associated with the Primary Profile <b>3901</b> for the employee and other information may be specific to the assignment. In an embodiment, the Expat Profile <b>3904</b> may include information for both the Expat (EXPAT) and Expat Dependents (DEP) such as, but not limited to, personal information for the EXPAT and/or Dependents.

In at least one embodiment, each member of a group may inherit a common Primary Profile <b>3901</b> and Trip/Assignment Profile <b>3902</b>. Thus, if the Primary Profile <b>3901</b> or Trip/Assignment Profile <b>3902</b> is changed, the changes are reflected in each group member employee's profile. However, if a Group Member adds or modifies a Leg, this would be preserved and not affected by changes made to the Primary Profile <b>3901</b> or Trip/Assignment Profile <b>3902</b>. This allows a Group Member to alter the base Itinerary for side trips, ate arrival or early departure, etc.

<figref idref="DRAWINGS">FIG. 40</figref> is a flow chart of a method for establishing asset information for an employee (including Expats, VIPs, and Dependent type employees) in accordance with at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 40</figref>, a method <b>4000</b> may commence at <b>4005</b>. Control may then proceed to <b>4010</b> at which a user may create or obtain an Employee or Expat Profile either manually or via a bulk loading mechanism from, for example, an Excel spreadsheet input file. The bulk loading capability may support a subset of the Expat Profile data elements. Embodiments may also include the capability to create an Expat Profile and register an Assignment from a web page on the organization's intranet. After the Employee enters his/her identifying information (i.e., Last Name, First Name, Employee ID, E-mail Address, etc.) the system may search for an existing Traveler Profile before creating a new profile in the system.

Control may then proceed to <b>4015</b>, at which the method may determine if the employee type is Expat, VIP, or Dependent. If the employee type is one of these three, then control may proceed to <b>4020</b> to establish an Assignment. In an embodiment, an Assignment may be created manually. Once an Assignment is registered with the system, the system may, optionally (based on company-specific settings), provision the global asset risk management service for the Employee. Control may then proceed to <b>4025</b> where, in at least one embodiment, any employee that has an active Assignment (e.g., not expired, current date past the Assignment Departure Date) may be categorized as an Expat by, for example, tagging the employee profile with, or including therein, an “EXPAT” attribute. However, in an embodiment, an Employee may also be an EXPAT with an active Trip. In this case, the Trip may take precedence over the Assignment when reporting on the employee's location. Furthermore, an employee may be categorized as a “Very Important Person” for whom kidnapping or other particular threats have a higher chance of occurrence. For example, to the EXPAT attribute may be added an additional attribute called “VIP.” The VIP attribute may enable a user to tag any employee profile as a VIP (e.g., Sr. Executive, Director, Country Manager).

If at <b>4015</b> it is determined that the employee is not an Expat (or VIP or Dependent), then control may proceed to <b>4030</b>, at which a method may establish a Trip. In an embodiment, a Trip may be created manually. Control may then proceed to <b>4035</b> where, in at least one embodiment, an indication may be received from a user as to whether or not to allow an Employee/Expat to access a personal website.

If at <b>4035</b> the user directs that the Expat web-based service be provisioned for the Expat, then control may then proceed to <b>4040</b> at which an Expat Welcome E-mail is sent to the Employee based on, for example, the Expat Profile Primary E-Mail Address. In an embodiment, the Welcome E-mail may include a hyperlink which upon user selection will enable the Employee to access a personalized Expat website which may be, for example, a risk management website. Control may then proceed to <b>4045</b>, at which the method may include outputting or providing an EXPAT personal web site that includes several additional features accessible by an EXPAT such as, for example, View/Edit Assignment, extended Personal Profile, and Add/Modify/Delete Profiles for a Group (i.e., Family). Furthermore, an EXPAT may be provided the capability to Add Locations to the Assignment for Alert Notification. This may be useful when, for example, an Employee works from the Assignment Location, but travels throughout the Region (i.e., AO or TO).

Control may then proceed to <b>4050</b>, at which the method may monitor for an Assignment change by an Employee/Expat (including VIP or DEP). If an Assignment change is made, then control may proceed to <b>4055</b> at which one or more User Notifications may be provided to inform a user whenever an Assignment is added or changed or when a VIP registers a Trip. Other Notification Rules or business rules may include filters by EXPAT, DEP or VIP to enable a user to focus on Expats and/or VIPs.

In addition, control may proceed to <b>4060</b> at which the method may include generating and outputting a report including a World Map. The World Map report may include a filter to display Expats and/or VIPs by, for example, Organizational Unit. An Employee Locator function may provide the user the capability to query and report on only EXPAT/DEPIVIP Employees. Control may then proceed to <b>4060</b>, at which a method may end.

Returning to <figref idref="DRAWINGS">FIG. 4</figref>, an analysis engine <b>403</b> may receive intelligence or information from the travel intelligence source(s) <b>401</b> (e.g., Source A) and the asset information source(s) <b>402</b> (e.g., Source B). In an embodiment, the analysis engine <b>403</b> may correlate the intelligence information (e.g., Source A) with the asset information (e.g., Source B) to determine if one or more assets is proximate to an intelligence event that could impact the security, health, freedom of movement, or otherwise adversely affect the environment in which the assets operate. An asset may include anything of value that is owned or managed by the organization. Assets may include employees, facilities, material, etc. If so, the analysis engine <b>403</b> may produce a risk assessment report <b>404</b> by, among other things, mapping or correlating travel intelligence with asset locations. In at least one embodiment, the analysis engine <b>403</b> may be as shown and described with respect to <figref idref="DRAWINGS">FIGS. 3</figref>, <b>7</b>, and <b>23</b>.

As discussed herein, an area of operation (AO) may refer to the local geographic area where an employee (including EXPAT, VIP, and Dependents) will operate typically bounded by local transportation capabilities (i.e., car, bus, taxi, etc.). A Theater of Operation (TO) may refer to a broader operation geography than the AO that typically requires long-range transportation such as an aircraft or ship. A Threat (or Hazard) may refer to a negative event that may be the source of danger or harm to an Asset. Exposure may be defined as the condition where an Asset may be impacted by a Threat. For example, what Assets (i.e., employees, facilities, etc.) may have been impacted by an earthquake in the AO.

In an embodiment, the global asset risk management system <b>400</b> may assign one or more geocodes to an intelligence related event to aid the analysis engine <b>403</b> in rendering the determination. The geocode for an intelligence event may include informational elements including, but not limited to, the intelligence category to which the event is assigned, the geographic coordinates of the epicenter of the event (e.g. latitude and longitude coordinates), and a threat perimeter for the event. Thus, each combination of the elements comprising a geocode represents a unique geocode for an event, and an event may have more than one associated geocode (e.g., different threat perimeters). The threat perimeter may be of any shape such as, for example, circular, elliptical, regular polygon, or irregular polygon.

In at least one embodiment, the risk assessment report <b>404</b> may be a data set illustrating the vulnerability of an asset or assets in the context of an intelligence event (e.g., threat). By providing the user with an indication of the asset vulnerability in the context of the threat posed by an intelligence event, the user is able to ascertain the risk to the asset and take appropriate mitigating action. The risk assessment report <b>404</b> may be a visual output to a user via text, graphics, or a combination thereof. The risk assessment report <b>404</b> may further include one or more electronic messages in combination with the output. The risk assessment report <b>404</b> may be output to the user, for example, via hardcopy printout, computer terminal display, or mobile device display such as a Liquid Crystal Display (LCD). For example, a risk assessment report <b>404</b> may include a worldview or world map display showing the location of assets and threats or events throughout the world. In at least one embodiment, the risk assessment report <b>404</b> may be available to one or more persons responsible for risk management within an organization and also made available to the affected employee (including expatriate, VIP, or Dependents).

Further, in an embodiment, the global asset risk management system <b>400</b> may provide a risk mitigation toolbox <b>405</b> to assist an asset manager or risk manager, or a person or group who is responsible for the asset at risk, to counteract and/or respond to the increased risk environment. The risk mitigation toolbox <b>405</b> may include one or more tools that serve to provide the asset manager with information, which may include intelligence or intelligence related information, useful in mitigating the increased risk environment for the asset. In at least one embodiment, these tools may be made available to the employee or expatriate as well. In an embodiment, Dependents may also request to receive this information, by, for example, editing a Dependent profile to enable receipt of such information, tools, or alerts. Examples of such tools include, but are not limited to, references to one or more documents specifying security response procedures, policies or procedures to be implemented in response to particular security threats, and the like. In an embodiment, instead of a link or reference to the document(s), an electronic copy of the document(s) may be made available for download by the asset manager using, for example, a computer equipped with a web browser. Other tools may include a notification system for disseminating travel intelligence or security related information and additional information regarding the asset(s) at risk.

<figref idref="DRAWINGS">FIG. 26</figref> is a flow chart of a global asset risk management method <b>500</b> according to at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 26</figref>, a method <b>500</b> may commence at <b>505</b> and proceed to <b>510</b> and <b>515</b>. At <b>510</b>, a method may include receiving travel intelligence from at least one intelligence source. At <b>515</b>, a method may include receiving asset information from at least one information source. The travel intelligence source(s) <b>401</b> may include the CIS <b>51</b> and CAAS <b>71</b>, or the intelligence or information associated with the CIS <b>51</b> and CAAS <b>71</b>, as described herein. In an embodiment, the asset information source may include company proprietary asset information such as, for example, but not limited to, geographic location information for company employees or facilities, as well as the employee profile information described herein. In at least one embodiment, the geographic location information may include an objective set of coordinates identifying the location of the asset(s) (e.g., facilities, office locations, or personnel). For example, the geographic location information may include the current or a recent set of Global Positioning System (GPS) coordinates. Furthermore, the geographic location information may include the current or a recent set of coordinates from a Geographic Information System (GIS).

Control may then proceed to <b>520</b>, at which an analysis engine may determine one or more impact areas for an event based on the intelligence or information received from the travel intelligence source(s) and the asset information source(s). In an embodiment, this may include correlating the intelligence information with the asset information to determine if one or more assets could be impacted, in terms of security, health, freedom of movement, or otherwise adversely affected, by the occurrence or non-occurrence of a particular event, at <b>525</b>. In an embodiment, the method may include assigning at least one geocode to an intelligence event to aid the analysis engine in rendering the impact assessment determination. If the analysis engine determines that one or more assets could be at increased risk due to an event, control may proceed to <b>530</b> at which the global risk management may produce a risk assessment report. In an embodiment, the increased risk may be reflected by assigning a correspondingly higher risk rating to the affected asset(s).

<figref idref="DRAWINGS">FIG. 27</figref> is an illustration of a risk assessment determination or report <b>600</b> according to at least one embodiment. As shown in <figref idref="DRAWINGS">FIG. 27</figref>, this determination or report <b>600</b> may include identifying an impact area <b>604</b> associated with an intelligence event that is categorized as a critical alert. Each such critical alert may be assigned an epicenter <b>603</b>. A map <b>601</b> may include an indication of a one or more asset locations <b>602</b> that could be affected by the increased risk environment based on, among other things, the asset being within one or more impact areas <b>604</b> associated with the epicenter of a critical alert <b>603</b>. In an embodiment, multiple categories of impact areas <b>604</b> may be provided such as, for example, but not limited to, a transportation impact area or a security impact area. Other categories are possible. In at least one embodiment, the risk assessment report <b>600</b> may be output to a user, such as a risk manager or security director, in the form of a visual interactive page that may be displayed using a web browser of a computing or communications device. Alternatively, the risk assessment report <b>600</b> may be output via hardcopy print media.

Returning to <figref idref="DRAWINGS">FIG. 26</figref>, control may then proceed to <b>535</b>, at which a method may include providing a risk mitigation toolbox to assist an asset manager, or a person or group who is responsible for the asset at risk, in responding to the increased risk environment. Examples of such tools include, but are not limited to, references to one or more documents specifying security response procedures, policies or procedures to be implemented in response to particular security threats such as evacuation plans, maps of facilities, and the like. In an embodiment, instead of a link or reference to the document(s), an electronic copy of the document(s) may be made available for download by the asset manager using, for example, a computer equipped with a web browser. An example of an document provided by the risk management toolbox is shown in <figref idref="DRAWINGS">FIG. 35</figref>.

Other tools associated with the toolbox may include a notification system for disseminating travel intelligence or security related information and additional information regarding the asset(s) at risk. The notification system may send a notification to an asset manager or to personnel affected by the event using a variety of communication media. The personnel who receive the notification may be pre-defined and stored by the system. The notification system may further review responses received in reply to a notification message to confirm successful notification delivery. In an embodiment, the notification system may assign different response categories to indicate notification transmission, notification receipt, and confirmation response. In at least one embodiment, the notification system may send notification messages according to a set of business rules. The business rules may include an escalation mechanism for ensuring that a critical alert is received by an asset manager, security director, or other individual or organization responsible for managing the asset(s) at risk. For example, if a notification is sent via e-mail and no confirmation response is timely received, then the escalation mechanism may automatically prompt the system to send the notification using a different communications channel or media for business continuity, such as, for example, triggering a telephone call to the e-mail recipient to ensure her receiving the notification. Multiple levels of escalation using a variety of communications media may be provided, including e-mail, telephone, pager, facsimile, satellite radio, or wireless device. Further, different escalation business rules may be provided for particular individuals.

The additional intelligence may be useful for a security director or asset manager to obtain intelligence for greater contextual understanding of a security threat or increased risk situation. For example, such additional intelligence may include recent intelligence events occurring in a neighboring country near an asset in an impact area. Furthermore, the system <b>400</b> may provide additional intelligence by applying the rules engine to a traveler profile as described herein.

Furthermore, in an embodiment, a user of the system <b>400</b> may be provided with the capability to determine the reliability of the intelligence used in determining a critical alert. In particular, the Content Identification Segment (CIS) may provide the capability for a user to review the source catalog information associated with an event such as, for example, an event leading to a critical alert. Thus, the system <b>400</b> allows the security director or asset manager to apply his personal knowledge in assessing the reliability, for example, of the source(s) of a critical event to be used in developing an appropriate response. In at least one embodiment, a user may interact with the global asset risk management system <b>400</b> to review the source catalog information maintained using the CIS. For example, <figref idref="DRAWINGS">FIG. 28</figref> is an exemplary source catalog page <b>2800</b> listing one or more sources of intelligence used in determining a critical alert. Referring to <figref idref="DRAWINGS">FIG. 28</figref>, the catalog page <b>2800</b> may include, for each source, a source identifier <b>2801</b>, a source name/title <b>2802</b>, media type <b>2803</b>, system reliability rating <b>2804</b>, source location <b>2805</b>, and a last visited date and/or timestamp. Each of these items may be entered by an analyst at an operations center facility of the global asset risk management system <b>400</b>. Furthermore, the catalog page <b>2800</b> may include a source catalog search capability <b>2807</b>. In an embodiment, the source catalog page <b>2800</b> may be an interactive page of a web browser application such as, for example, Microsoft™ Internet Explorer™.

In an embodiment, upon user selection of a source by, for example, using a mouse and cursor to select the line including the above described source information, the global asset risk management system <b>400</b> may respond by outputting to the user one or more interactive pages including further detailed information associated with the source. Each source entry may be hyperlinked to the source catalog page or one or more detailed information pages, for example. Such detailed information interactive pages may include, but are not limited to, general information, comments, metadata, a primary contact, an alternate contact, and ratings. The detailed information may be maintained using the CIS. <figref idref="DRAWINGS">FIG. 29</figref><i>a </i>is a first exemplary general interactive page <b>2900</b> showing general details associated with a source according to at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 29</figref><i>a</i>, the general details page <b>2900</b> may include a source summary <b>2901</b>, the name of the creating analyst or person <b>2902</b> who created the source, the name of the analyst or person <b>2903</b> who last updated the source, the creation date <b>2904</b>, and the date last updated <b>2905</b>.

<figref idref="DRAWINGS">FIG. 29</figref><i>b </i>is a second exemplary general interactive page <b>2950</b> showing further general details associated with a source according to at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 29</figref><i>b</i>, the general details page <b>2950</b> may further include a media type <b>2906</b> associated with the source, a lifespan of the article <b>2907</b> if applicable, the interval between visits <b>2908</b> to the source using the system <b>400</b>, the source title <b>2909</b>, and a source location <b>2910</b>. The source location <b>2910</b> may be a Uniform Reference Locator (URL) for a HTML-formatted web page.

<figref idref="DRAWINGS">FIG. 30</figref> is an exemplary comments interactive page <b>3000</b> showing comments associated with a source according to at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 30</figref>, the comments page <b>3000</b> may further include comments <b>3001</b> associated with the source. In an embodiment, the comments <b>3001</b> may be entered by an analyst such as a SME.

<figref idref="DRAWINGS">FIG. 31</figref> is an exemplary metadata interactive page <b>3100</b> showing metadata associated with a source according to at least one embodiment. In an embodiment, metadata associated with a source may include information maintained by the system <b>400</b> representing relationships of the source to various other informational items beyond the intelligence provided by the source. In an embodiment, each source may be associated with either an intelligence category (e.g., security, terrorism) or location/destination information (e.g., country). For example, referring to <figref idref="DRAWINGS">FIG. 31</figref>, the metadata page <b>3100</b> may include a list of projects <b>3101</b> associated with the source, a list of the categories <b>3102</b> for the source, a list of locations <b>3103</b> to which the source pertains, and an overall source category tree <b>3104</b>.

<figref idref="DRAWINGS">FIG. 32</figref> is an exemplary contact interactive page <b>3200</b> showing primary contact information associated with a source according to at least one embodiment. In an embodiment, contact information associated with a source may include a source owner or entity responsible for the source as well as address and communications contact information for the source owner. Secondary or alternate contact information may be provided on additional contact pages <b>3200</b>.

<figref idref="DRAWINGS">FIG. 33</figref> is an exemplary source ratings page <b>3300</b> showing one or more reliability ratings for a source. Referring to <figref idref="DRAWINGS">FIG. 33</figref>, the source ratings page <b>3300</b> may include an initial reliability assessment <b>3301</b> and a system reliability rating <b>3302</b>. The reliability rating assessment <b>3301</b> and <b>3302</b> may be individually assigned a rating such as, for example, “A,” “B,” or “C,” representing a range of most reliable to least reliable, respectively. The initial reliability assessment <b>3301</b> may be a one-time rating assigned by an analyst or SME based on, for example, the analyst's past experience involving intelligence from the source. In an embodiment, the system reliability rating <b>3302</b> may be determined by the system <b>400</b> based on a rating algorithm that takes into account a variety of factors such as, but not limited to, the availability of the source to provide intelligence to agents of the system <b>400</b> as described earlier herein. Other factors may include the existence of human in the loop feedback regarding intelligence provided by the source to confirm development of the intelligence using, for example, a trend line analysis. The rating algorithm may assign a mathematical or statistical value to each of the various factors and then compute a reliability rating based on the weighted sum. By comparing the initial reliability assessment <b>3301</b> with the system reliability rating <b>3302</b>, the user may determine the change in reliability of a source over time to aid in assessing the intelligence received from that source. Furthermore, the source ratings page <b>3300</b> may further include a source status <b>3304</b>, reliability comments <b>3305</b>, and source status comments <b>3306</b>. The source status <b>3304</b> may indicate the current status for a source including, for example, “in use,” “potential,” “do not use,” and “aggregator.” Comments <b>3305</b> and <b>3306</b> may include analyst or SME observations regarding source reliability or status, respectively.

<figref idref="DRAWINGS">FIG. 34</figref> is an exemplary additional intelligence page <b>3400</b> of the risk mitigation toolbox in at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 34</figref>, the intelligence page <b>3400</b> may include for each source listed an edit selection button <b>3501</b>, source name/title <b>3402</b>, a media type <b>3403</b> (e.g., plain text), a unique source identifier <b>3404</b>, a system reliability rating <b>3405</b>, a creation date <b>3406</b>, a last updated date <b>3407</b>, notes <b>3408</b> (e.g., a URL address of the World Wide Web), and an interactive repository search interface <b>3409</b>. Upon operator selection of the edit selection button <b>3404</b>, the system <b>400</b> may provide the capability for the user to edit the source information including the data fields shown in <figref idref="DRAWINGS">FIG. 34</figref>. In an embodiment, the system <b>400</b> may provide the capability for the user to search the source catalog or repository by entering various search criteria using the repository search interface <b>3409</b>.

<figref idref="DRAWINGS">FIG. 35</figref> is an exemplary reference document page <b>3500</b> showing a plain text document <b>3501</b> and an HTML formatted document <b>3502</b> of the risk mitigation toolbox in at least one embodiment.

<figref idref="DRAWINGS">FIG. 36</figref> is an exemplary additional intelligent metadata interactive page <b>3600</b> showing metadata associated with an additional intelligence source of the risk mitigation toolbox according to at least one embodiment. In an embodiment, additional intelligence metadata associated with a source may include information maintained by the system <b>400</b> representing relationships of the source to various other informational items beyond the intelligence provided by the source. For example, referring to <figref idref="DRAWINGS">FIG. 36</figref>, the additional intelligence metadata page <b>3600</b> may include a list of projects <b>3601</b> associated with the source, a list of the categories <b>3602</b> for the source, and a list of locations <b>3603</b> to which the source pertains.

<figref idref="DRAWINGS">FIG. 37</figref> is an exemplary additional intelligent ratings interactive page <b>3700</b> showing source ratings associated with an additional intelligence source of the risk mitigation toolbox according to at least one embodiment. For example, referring to <figref idref="DRAWINGS">FIG. 37</figref>, the additional intelligence source ratings page <b>3700</b> may include a rater identifier <b>3701</b>, a rate date <b>3702</b> that may include a date/timestamp, a numerically-scaled timeliness score <b>3703</b>, a numerically-scaled accuracy score <b>3704</b>, a numerically-scaled relevance score <b>3705</b>, and source comments <b>3706</b>.

In addition, in at least one embodiment, the analysis engine <b>403</b> may include a compliance function in which a person seeking to travel to a location adversely affected by a critical event, such as a location within an impact area, must first acquire the approval of the asset manager or security director prior to being permitted to travel to the location. This provides the asset manager the opportunity to ensure that the traveler has received proper training in dealing with the increased risk environment prior to traveling there. In at least one embodiment, this compliance function may be provided in the form an online test for which the traveler must obtain a satisfactory score prior to be authorized travel (e.g., prior to being issued tickets).

It is apparent that the global asset risk management system and methods described herein may by configured to provide many useful asset risk management functions in a variety of embodiments for both fixed and mobile assets including, but not limited to, people, facilities, and containers. For example, the global asset management system <b>400</b> may be configured to provide supply chain management by providing a risk assessment for a shipping route for assets or goods in shipment to avoid supply chain interruption (e.g., routing of supply ships around areas of increased risk). In such embodiments, the asset information may include individual shipping container tracking information such as, for example, a container identification code associated with a set of periodically updated geographic coordinates or identifiers. Similarly, the global asset risk management system <b>400</b> may be configured to provide personnel tracking by associating a personal identifier with a set of periodically updated geographic coordinates or identifiers. In at least one embodiment, the tracking information may include GPS or GIS coordinates.

A further example of a risk assessment report according to an embodiment is shown in <figref idref="DRAWINGS">FIGS. 38</figref><i>a </i>and <b>38</b><i>b</i>. Referring to <figref idref="DRAWINGS">FIG. 38</figref><i>a</i>, a message portion <b>3801</b> of a risk assessment report may include a text message <b>3802</b> containing intelligence and affected asset information associated with an intelligence event. The message portion may also include a mapping interface <b>3803</b> and an asset communications interface <b>3804</b>. The mapping interface <b>3803</b> may include a selection mechanism by which a user may select to view a map portion of the risk assessment report. In an embodiment, when the user selects the mapping interface <b>3803</b> the analysis engine may render a map page such as that shown in <figref idref="DRAWINGS">FIG. 38</figref><i>b</i>. The analysis engine may use the CMS to obtain intelligence and information from the CRS in generating the map page. In an embodiment, when the user selects the asset communications interface <b>3804</b>, the CMS may output an interactive page by which the user may compose and cause to be sent a message such as, for example, an electronic message or email, to the asset.

An example of a map page <b>3810</b> according to an embodiment is shown in <figref idref="DRAWINGS">FIG. 38</figref><i>b</i>. Referring to <figref idref="DRAWINGS">FIG. 38</figref><i>b</i>, the map page <b>3810</b> may include a graphical artifact representing an intelligence event <b>3811</b>, a graphical artifact representing a landmark <b>3812</b>, a graphical artifact representing a first asset <b>3813</b> such as a person on the ground at a location, and a graphical artifact representing a second asset <b>3814</b> such as a private facility. Further, the map page <b>3810</b> may also include a geofence <b>3815</b> representing a threat boundary. In the example, of <figref idref="DRAWINGS">FIG. 38</figref><i>b</i>, the area inside the geofence may represent a safe area, and the area outside the geofence may represent an area having an unacceptably high threat or risk. Alternatively, the geofence <b>3815</b> may correspond to a threat perimeter of a geocode in which the area inside the geofence represents the area of unacceptably high risk. The map page <b>3810</b> may also include text information <b>3816</b> to provide the user with, among other things, the status of assets <b>3813</b> or <b>3814</b> with respect to the geofence <b>3815</b>. Further, in at least one embodiment, in response to the user selecting an intelligence event <b>3811</b> on the interactive map page <b>3810</b> (using, for example, a mouse device), the system <b>400</b> may output to the user the source catalog page <b>2800</b> (see <figref idref="DRAWINGS">FIG. 28</figref>) so that the user may review the sources underlying the intelligence event. Thus, the risk assessment report may output to the user an indication of the vulnerability of one or more assets in the context of an intelligence event or events.

In at least one embodiment, the employee profile information <b>3900</b> and its component profiles or portions may be established and maintained using, for example, the Content Management Segment (CMS) described herein with respect to <figref idref="DRAWINGS">FIG. 39</figref>. In such embodiments, the employee profile information may be added or modified using one or more interactive pages of a computer system. For example, a user may add or modify employee profile information <b>3900</b> using a browser application of a computing system. In an embodiment, the interactive pages for outputting or accepting employee profile information <b>3900</b> may be accessed using a network. For example, such a network may be an office or organization Local Area Network (LAN) or the Internet. <figref idref="DRAWINGS">FIG. 41</figref><i>a </i>is one example profile information page <b>4100</b> in accordance with at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 41</figref><i>a</i>, a profile information page <b>4100</b> may include one or more page selection tabs such as <b>4101</b> to <b>4110</b>, one or more information fields such as <b>4111</b> to <b>4124</b>, a photograph <b>4125</b>, and primary contact information <b>4126</b>. Page selection tabs may include, for example, a Profile tab <b>4101</b>, a User Preferences tab <b>4102</b>, an Emergency Contact tab <b>4103</b>, a Travel Documents tab <b>4104</b>, a Personal Info tab <b>4105</b>, a Medical Info tab <b>4106</b>, a Vehicles tab <b>4107</b>, an Images tab <b>4108</b>, a Trip Profile tab <b>4109</b>, and a Configure Reports tab <b>4110</b>. User selection of one of the page selection tabs <b>4101</b> through <b>4110</b> may cause a corresponding profile information page <b>4100</b> to be output to the user via, for example, a computer or portable device display.

As shown in <figref idref="DRAWINGS">FIG. 41</figref><i>a</i>, information fields in an interactive basic profile information page <b>4100</b>, output in response to user selection of the Profile tab <b>4101</b>, may include user name information such as Last Name <b>4111</b>, First Name <b>4112</b>, Middle Name <b>4113</b>, Employee ID <b>4114</b>, Alternative (Alt) Employee ID <b>4115</b>, National ID (e.g., social security number) <b>4116</b>, a first country of citizenship (Citizenship <b>1</b>) <b>4117</b>, a second country of citizenship (Citizenship <b>2</b>) <b>4118</b>, Birthplace <b>4119</b>, Date of Birth <b>4120</b>, Gender <b>4121</b>, a Primary E-Mail address <b>4122</b>, a first Alternative E-Mail (Alt E-Mail <b>1</b>) <b>4123</b>, and a second Alternative E-Mail (Alt E-Mail <b>2</b>) <b>4124</b>. The photograph <b>4125</b> may be a current photograph of the employee or expatriate. Primary contact information <b>4126</b> may include, for example, but not limited to, contact information such as E-mail address, various telephone numbers, and street address.

In an embodiment, upon user selection of the User Preferences tab <b>4102</b>, the system <b>400</b> may output an interactive page <b>4100</b> that includes data entry fields for the user to specify a user name and password. Further, the user may be provided one or more checkboxes to specify an alert level and an alert email format (e.g., HTML or text). In addition, upon user selection of the Emergency Contact tab <b>4103</b>, the system <b>400</b> may output an interactive page <b>4100</b> that includes data entry fields for the user to input contact information for an emergency contact such as, for example, e-mail address, various telephone numbers, and street address.). Further, upon user selection of the Travel Documents tab <b>4104</b>, the system <b>400</b> may output an interactive page <b>4100</b> as shown in <figref idref="DRAWINGS">FIG. 41</figref><i>b </i>that includes an Add Passport button <b>4127</b>, an Add Visa button <b>4128</b>, an employee/expatriate Passport Information data entry field <b>4129</b>, and an employee/expatriate Visa Information data entry field <b>4130</b>. The Passport information data entry field <b>4129</b> may include passport information such as, but not limited to, passport country, passport number, passport expiration date, and place of issue.

Upon user selection of the Personal Info tab <b>4104</b>, the system <b>400</b> may output an interactive page <b>4100</b> as shown in <figref idref="DRAWINGS">FIG. 41</figref><i>c </i>that includes data entry/selection fields such as, for example, Marital Status <b>4130</b>, Ethnic Background <b>4131</b>, Religious Preference <b>4132</b>, and physical identifiers such as Height <b>4133</b>, Weight <b>4134</b>, Eye Color <b>4135</b>, Hair Color <b>4136</b>, Identifying Scars <b>4137</b>, and Identifying Tattoos <b>4138</b>. Personal information may also include Languages Spoken and Proficiency <b>4139</b>, Special Skills <b>4140</b> (e.g., medic, pilot, radio operator), a Life Verification Question <b>4141</b> and Answer <b>4142</b>, and a Notes field <b>4143</b>. The Life Verification Question <b>4141</b> and Answer <b>4142</b> may relate to subject matter known only to the employee/expatriate. As shown in <figref idref="DRAWINGS">FIG. 41</figref><i>c</i>, the system <b>400</b> may provide the user the capability to enter personal information via text entry or by selecting an item from a pull-down menu of possible choices or a list of such choices.

Upon user selection of the Medical Info tab <b>4106</b>, the system <b>400</b> may output an interactive page <b>4100</b> as shown in <figref idref="DRAWINGS">FIG. 41</figref><i>d </i>that includes data entry/selection fields such as, for example, Blood Type <b>4144</b>, Allergies <b>4145</b>, Chronic Conditions <b>4146</b>, and Medical Contact information <b>4147</b>. As shown in <figref idref="DRAWINGS">FIG. 41</figref><i>c</i>, the system <b>400</b> may provide the user the capability to enter personal information via text entry or by selecting an item from a pull-down menu of possible choices or a list of such choices. Upon user selection of the Vehicles tab <b>4107</b>, the system <b>400</b> may output an interactive page <b>4100</b> (not shown) that includes data entry/selection fields such as, for example, vehicle make, model, year, and color. Upon user selection of the Images tab <b>4108</b>, the system <b>400</b> may output an interactive page <b>4100</b> as shown in <figref idref="DRAWINGS">FIG. 41</figref><i>e </i>that includes images <b>4150</b>. The images <b>4150</b> may be thumbnail images of scanned photographs, jpeg files, .bmp files, and the like, showing the employee/expatriate in various circumstances or other related visual identifiers or information. Upon user selection of the Trip Profile tab <b>4109</b>, the system <b>400</b> may output an interactive page that includes data entry/selection fields associated with a trip. Upon user selection of the Configure Reports tab <b>4110</b>, the system <b>400</b> may output an interactive page that includes data entry/selection fields to specify report output formats and content.

Furthermore, the system <b>400</b> may provide the capability for the user to define a Group of employees or expatriates having a common characteristic or particular relationship. <figref idref="DRAWINGS">FIG. 41</figref><i>f </i>is an interactive page <b>4100</b> which may be used to manage group relationships, according to an embodiment. Referring to <figref idref="DRAWINGS">FIG. 41</figref><i>f</i>, the system <b>400</b> may output an interactive page that includes an Add Group button <b>4160</b>, as well as data entry/selection fields to specify Group Name/Type <b>4161</b>, Relationship information <b>4162</b>, and group contact information <b>4163</b>.

<figref idref="DRAWINGS">FIG. 42</figref> is an example Traveler/Expatriate Management interactive page <b>4200</b> according to at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 42</figref>, the Traveler/Expatriate Management interactive page <b>4200</b> may be output by the system <b>400</b> for display using a browser application such as, for example, Netscape™ Navigator™ available from Netscape Corporation of Mountain View, California. In at least one embodiment, the Traveler/Expatriate Management interactive page <b>4200</b> may include a title <b>4201</b>, an Add New Traveler/Expat button <b>4202</b>, Search for Traveler/Expat data entry fields <b>4203</b>, and a Travelers/Expat list <b>4204</b>. In at least one embodiment, the user may toggle between interactive pages <b>4200</b> showing “traveler” information and “Expat” information by selecting an Expat Management button <b>4205</b>. The various static information fields of the interactive page <b>4200</b> may be output as “Traveler” or “Expat,” according to whether traveler or expatriate management is being performed in accordance with the state of the Expat Management button <b>4205</b>.

Further, in at least one embodiment, referring to <figref idref="DRAWINGS">FIG. 42</figref>, the Traveler/Expatriate Management interactive page <b>4200</b> may provide a search function for travelers or expatriates. For example, the user may be provided the capability to search for travelers or expatriates using the Search for Traveler/Expat data entry fields <b>4203</b>. These fields may include, without limitation, the following search fields and terms: Last Name, First Name, Employee ID, Alt Employee ID, by Company, and/or Limited to: Expats, Dependents, or VIP. In an embodiment, if the user enters no fields and selects the SEARCH action, a count of the results and all Expats may be displayed. If an Expat has Dependents (an example of a Group), these may be displayed under the Expat entry. If the user selects “Limit to Dependents”, the SEARCH action may list all Dependents. Further, each Dependent may display the Expat it is linked to. In an embodiment, the result list may be downloaded using a computer-readable medium for access and/or output to an external computing device using an application such as, for example, Microsoft® Excel™.

In addition, as discussed earlier herein, in at least one embodiment the system <b>400</b> may include a bulk load mechanism. For example, in an embodiment, the Traveler/Expatriate Management interactive page <b>4200</b> may include a Bulk Load button <b>4206</b> which, upon user selection, will allow a user to browse to a file to be uploaded into the system. In an embodiment, the user may define the format of the file. The format can be a previously saved format or a new format can be built and optionally saved. For example, the system <b>400</b> may include the capability to bulk load Expat data from a file in Excel or Comma Separated Values (CSV) formats. After defining the input fields and order, the user may select either CANCEL to quit this function or TEST to test load the first row of data. If TEST is selected, the first row of data will be loaded. The system will display the fields and associated data to enable the user to visually inspect that the field formats and mapping are correct. From this display, the user may select either CANCEL to return to the mapping definition or LOAD to load the rest of the data in the file. The system may display an indicator for each data row loaded. In the event of an error, the system may display the row number in error, error description, and a dump of the record data if possible. The user may have the ability to QUIT or CONTINUE. Once the Load is complete, the system may report the number of records loaded successfully.

Furthermore, in at least one embodiment, a user may set an automatic notification setting to output a high risk assignment notification if, for example, an expatriate is assigned to a high risk destination. For example, the user may select “Notification for Assignments registered to Locations &gt;=CSAR”. The Country Security Assessment Rating (CSAR) value can be selected as “1” through “5.” If the User sets the CSAR value to “4”, then any Assignment registered to a Location currently rated 4 or higher will trigger a Notification to the User's e-mail address.

In addition, in at least one embodiment, a user may add a group or dependent relationship or link to an existing expatriate. For example, the user may select an Employee Profile via Search or other link to the Employee Profile. Once the Employee Profile is displayed, the user may scroll to the Group section and select “Add Group Member”. From “Add Group Member”, the user may search for an Employee (Dependent) Profile and select a profile or “Add an Employee Profile” if the Dependent is not already in the system. Upon the user adding Group Member (Dependent) to an Employee Profile, the system may automatically designate the linked Employee Profile as a Dependent (“DEP”) and optionally link the employee's Assignment to the Group Member. If the Dependent is not in the same Assignment Location as the Employee, then the user may create a Trip to designate where the Dependent is located or delete the Assignment from the dependent's Profile

In at least one embodiment, the system <b>400</b> may output an employee profile interactive page <b>4300</b> as shown in <figref idref="DRAWINGS">FIG. 43</figref>. Referring to <figref idref="DRAWINGS">FIG. 43</figref>, the profile interactive page <b>4300</b> may include the information fields <b>4301</b> described earlier herein with respect to <figref idref="DRAWINGS">FIGS. 41</figref><i>a </i>through <b>41</b><i>f </i>and as shown and described in Table 1 below.

<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="84pt" align="left" /><colspec colname="2" colwidth="133pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 1</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Last Name (*)</entry><entry>Employee's last name</entry></row><row><entry>First Name (*)</entry><entry>Employee's first name</entry></row><row><entry>Middle Name</entry><entry>Employee's middle name(s)</entry></row><row><entry>Employee Number (*)</entry><entry>Employee ID used for system lookup</entry></row><row><entry>Alt Employee Number</entry><entry>Alternate Employee ID to be stored in the</entry></row><row><entry /><entry>Profile. Not used by the system.</entry></row><row><entry>National ID (SSN)</entry><entry>National ID (SSN-Social Security Number).</entry></row><row><entry /><entry>Not used by the system.</entry></row><row><entry>Birth Date</entry><entry>MM/DD/YYYY (manual or calendar entry)</entry></row><row><entry>Birth Place</entry><entry>City, Country (list)</entry></row><row><entry>Gender</entry><entry>Male/Female/Unknown</entry></row><row><entry>Citizenship 1</entry><entry>Country (from list)</entry></row><row><entry>Citizenship 2</entry><entry>Country (from list)</entry></row><row><entry>Passport Country 1</entry><entry>Country (from list - new)</entry></row><row><entry>Passport Country 2</entry><entry>Country (from list - new)</entry></row><row><entry>Passport Exp Date 1</entry><entry>MM/DD/YYYY (manual or calendar entry)</entry></row><row><entry>Passport Exp Date 2</entry><entry>MM/DD/YYYY (manual or calendar entry)</entry></row><row><entry>Welcome Email Format</entry><entry>Plain Text or HTML (List)</entry></row><row><entry>Alert Preference</entry><entry>Info/Warn/Critical (Radio Buttons)</entry></row><row><entry>Primary E-mail 1 (*)</entry><entry>Primary Contact E-Mail 1 - used by the</entry></row><row><entry /><entry>system for Welcome e-mail.</entry></row><row><entry>E-mail 1 Alerts</entry><entry>Yes/No (button)</entry></row><row><entry>E-mail 1 Format</entry><entry>Plain Text/HTML (List)</entry></row><row><entry>Primary E-mail 2</entry><entry>Alternate e-mail 2 with Alerts and Format</entry></row><row><entry /><entry>options</entry></row><row><entry>Primary E-mail 3</entry><entry>Alternate e-mail 3 with Alerts and Format</entry></row><row><entry /><entry>options</entry></row><row><entry>Primary Address</entry><entry>Street, City, State, Country, Postal Code</entry></row><row><entry>Primary Phone Contact</entry><entry>Daytime, Evening, Fax, Cell/Pager</entry></row><row><entry>Emergency Contact</entry><entry>(N) Name, Relationship, Day Phone,</entry></row><row><entry /><entry>Evening Phone, Mobile, E-mail (add</entry></row><row><entry /><entry>Relationship and other Phone numbers to</entry></row><row><entry /><entry>existing record)</entry></row><row><entry>Physical Description</entry><entry>Height (ft/in and meters), Weight (Lb and</entry></row><row><entry /><entry>Kg), Eye Color (list), Hair Color (list),</entry></row><row><entry /><entry>Identifying Scars (text), Identifying Tatoos</entry></row><row><entry /><entry>(text)</entry></row><row><entry>Personal Information</entry><entry>Ethnic Background (list), Religious</entry></row><row><entry /><entry>Preference (list), Languages Spoken (list)</entry></row><row><entry /><entry>and Level (Read, Write, Beginner,</entry></row><row><entry /><entry>Intermediate, Fluent), Special Skills (list and</entry></row><row><entry /><entry>other with text) - Medic, Pilot, Radio</entry></row><row><entry /><entry>Operator, Marital Status (Single, Married,</entry></row><row><entry /><entry>Separated, Divorced, Widowed), Number of</entry></row><row><entry /><entry>Children</entry></row><row><entry>Medical Information</entry><entry>(Use an external medical records system for</entry></row><row><entry /><entry>HIPPA and EU Privacy?) Blood Type (list),</entry></row><row><entry /><entry>Allergies (list), Chronic Conditions (list),</entry></row><row><entry /><entry>Shot Record</entry></row><row><entry>Medical Provider Contact</entry><entry>(N) Type (list), Name, Day Phone, Night</entry></row><row><entry /><entry>Phone, Mobile, E-mail, Address</entry></row><row><entry>Life Verification Question</entry><entry>(N) Question and Answer</entry></row><row><entry>Personal Vehicle</entry><entry>(N) Year, Make, Model, Color, VIN,</entry></row><row><entry /><entry>License Number</entry></row><row><entry>Head Photo</entry><entry>Digital Photo (auto scale to standard</entry></row><row><entry /><entry>thumbnail)</entry></row><row><entry>Image</entry><entry>(N) Digital Image (auto thumbnail)</entry></row><row><entry>Handwriting Sample</entry><entry>(N) Digital Image</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

In Table 1, required fields are denoted as (*) and (N) denotes that the record can be entered multiple times, in an embodiment.

In at least one embodiment, the system <b>400</b> may output an itinerary/assignment interactive page <b>4400</b> as shown in <figref idref="DRAWINGS">FIG. 44</figref>. Referring to <figref idref="DRAWINGS">FIG. 44</figref>, the itinerary/assignment interactive page <b>4400</b> may include a traveler/expatriate name <b>4401</b>, a trip or assignment name <b>4402</b>, an alert preference <b>4403</b>, a trip or assignment memo field <b>4404</b>, trip or assignment details <b>4405</b> including legs information, Add Leg information fields <b>4406</b>, and a send itinerary email button <b>4407</b>. As with interactive page <b>4200</b>, the various static information fields of the interactive page <b>4400</b> may be output as “Traveler” or “Expat,” according to whether traveler or expatriate management is being performed in accordance with the state of the Expat Management button <b>4205</b>. In at least one embodiment, itinerary/assignment information which may be input into the system <b>400</b> using, for example, the interactive page <b>4400</b> is set forth in Table 2 below.

<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="168pt" align="left" /><thead><row><entry namest="1" nameend="2" rowsep="1">TABLE 2</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>Assignment</entry><entry>Text field with default format as “Assignment:”,</entry></row><row><entry>Name</entry><entry>Assignment Location, Arrival Date, “to”, Departure</entry></row><row><entry /><entry>Date. For example, “Assignment: London 01-Jan-05 to</entry></row><row><entry /><entry>31-Dec-05”</entry></row><row><entry>Assigned</entry><entry>Location will be used throughout the system for query</entry></row><row><entry>Location (*)</entry><entry>and reporting. Can be a Country or City designation.</entry></row><row><entry>Arrival</entry><entry>The date the employee is expected to arrive to the</entry></row><row><entry>Date (*)</entry><entry>Assigned Location. The system will default the Arrival</entry></row><row><entry /><entry>Time as 00:01.</entry></row><row><entry>Departure</entry><entry>The date the employee is expected to depart the</entry></row><row><entry>Date (*)</entry><entry>Assigned Location and terminate his/her status as an</entry></row><row><entry /><entry>EXPAT. The system will default the Departure Time as</entry></row><row><entry /><entry>23:59.</entry></row><row><entry>Assigned</entry><entry>Ability to link the Assignment to a Company (Agency</entry></row><row><entry>Company (*)</entry><entry>ID) other than the default Company. The default</entry></row><row><entry /><entry>Company will be that of the responsible organization</entry></row><row><entry /><entry>user entering the Assignment.</entry></row><row><entry>Assignment</entry><entry>Text field with free form text entry. Visible to</entry></row><row><entry>Notes PRO</entry><entry>responsible organization user only.</entry></row><row><entry>Assignment</entry><entry>Text field with free form text entry. Visible to both the</entry></row><row><entry>Notes BOTH</entry><entry>responsible organization user and Employee.</entry></row><row><entry>Local Address</entry><entry>Number, Street, City, Postal Code of local residence.</entry></row><row><entry>Local</entry><entry>Phone (Day), Phone (Night), Mobile, Fax, Pager</entry></row><row><entry>Contact</entry></row><row><entry>Information</entry></row><row><entry>Emergency</entry><entry>(N) Name, Relationship, Phone (Day), Phone (Night),</entry></row><row><entry>Contact</entry><entry>Mobile, Fax, Pager</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

In Table 2, required fields are denoted as (*) and (N) denotes that the record can be entered multiple times, in an embodiment.

Furthermore, in at least one embodiment, the system <b>400</b> may include an employee/expatriate locator module. In an embodiment, the Employee Locator may be used to query the system, report and export information using query attributes of EXPAT, DEP and VIP. In particular, the system query interface may be designed to select ALL Employee records as a default. ALL Employees may include Travelers, Expatriates (EXPAT) and Dependents (DEP). For many queries, the user may limit the selection of Employees to a subset; for example, EXPATs only or DEPs only can be selected. The basic filter construct may be:

Limit Employees: [ ] Travelers [ ] VIP [ ] EXPAT [ ] DEP

Some examples of usage may be: 1) checking the Traveler checkbox may cause the system to process the query to mean “show all the Employees that are not EXPAT or DEP; 2) checking the Traveler and VIP checkboxes may cause the system to process the query to mean “show all Travelers that are VIPs,” and 3) checking the EXPAT and DEP checkboxes may cause the system to process the query to mean “show all Expats and Dependents.” Furthermore, in an embodiment, the user may query travelers/expatriates by “VIP” and airline, by date range, by destination, by hotel, by CSAR, and by employee.

In at least one embodiment, the system <b>400</b> may output an one or more query results interactive pages <b>4500</b> as shown in <figref idref="DRAWINGS">FIGS. 45</figref><i>a </i>through <b>45</b><i>c</i>. A simple query results interactive pages <b>4500</b> as shown in <figref idref="DRAWINGS">FIG. 45</figref><i>a</i>. Referring to <figref idref="DRAWINGS">FIG. 45</figref><i>a</i>, the query results interactive page <b>4500</b> may include a number of matching travelers/trips <b>4501</b> indicator, a traveler/expatriate name <b>4502</b>, a trip/assignment name <b>4503</b>, and a contact traveler/expatriate button <b>4504</b>. A detailed query results interactive pages <b>4500</b> may be as shown in <figref idref="DRAWINGS">FIG. 45</figref><i>b</i>. Referring to <figref idref="DRAWINGS">FIG. 45</figref><i>b</i>, the detailed query results interactive page <b>4500</b> may include a number of matching legs <b>4505</b> indicator, a traveler/expatriate name <b>4502</b>, a trip/assignment name <b>4503</b>, the contact traveler/expatriate button <b>4504</b>, and trip leg detailed information <b>4507</b>. A full query results interactive pages <b>4500</b> may be as shown in <figref idref="DRAWINGS">FIG. 45</figref><i>c</i>. Referring to <figref idref="DRAWINGS">FIG. 45</figref><i>c</i>, the full query results interactive page <b>4500</b> may include a number of matching legs <b>4505</b> indicator, a traveler/expatriate name <b>4502</b>, a trip/assignment name <b>4503</b>, the contact traveler/expatriate button <b>4504</b>, and trip leg detail and contact information <b>4508</b>.

In addition, as discussed earlier herein, in at least one embodiment the system <b>400</b> may output a world map view output report. <figref idref="DRAWINGS">FIG. 47</figref> is an example of a world map view report <b>4700</b> according to at least one embodiment. Referring to <figref idref="DRAWINGS">FIG. 47</figref>, the world map view report <b>4700</b> may provide the capability for the user to filter world location data displayed by EXPAT attribute, DEP attribute, and/or VIP attribute using, for example, a pull down menu <b>4701</b>. Furthermore, in at least one embodiment, the world map view report <b>4700</b> may include the capability to provide a “Mouse Over Total Count” output. In particular, upon the user moving a cursor over the total “employee” count (N) <b>4702</b> in a country <b>4703</b> may cause the system to in response display the number of Travelers (X), Expats (Y), Dependents (Z) and VIPs (A) in a country. The total on the map (N) may be the count of Travelers plus the count of Expats and Dependents in the country. The VIP count may be the count of any Employee profile (Traveler, Expat or Dependent) with the VIP attribute. Further, the world map view report <b>4700</b> may include a rating value indication <b>4704</b>. The rating value indication <b>4704</b> may provide an indication of an overall threat or safety level present in a country <b>4703</b>. In at least one embodiment, the rating value indication <b>4704</b> may use different colors to differentiate among varying threat levels. Further, the rating value indication <b>4704</b> may reflect the CSAR for a given country.

Furthermore, as discussed earlier herein, in at least one embodiment the system <b>400</b> may provide employee/expatriate personal websites or interactive pages. <figref idref="DRAWINGS">FIG. 46</figref> is an employee/expatriate personal interactive page <b>4600</b> in accordance with an embodiment. Referring to <figref idref="DRAWINGS">FIG. 46</figref>, the employee/expatriate personal interactive page <b>4600</b> may include a history button <b>4601</b>, current trips/assignments <b>4602</b>, and a group profile button <b>4603</b>. In an embodiment, upon selection of the history button <b>4601</b>, the system <b>400</b> may output an interactive page <b>4600</b> containing a list of completed trips/assignments. User selection of the group profile button <b>4602</b> may cause the system <b>400</b> to output an interactive page <b>4600</b> containing a group profile with which the employee/expatriate is associated.

Whereas particular embodiments of this invention have been described above for purposes of illustration, it can be evident to those skilled in the art that numerous variations of the details of the present invention may be made without departing from the invention as defined in the appended claims.