JP2013008149A - Business face-to-face data generation device and system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To quantitatively grasp not only facing between staffs of an organization, but also facing to a non-organization staff as one piece of information effective for business efficiency improvement.SOLUTION: A sensor terminal that each of in-organization staffs as staffs who belong to the organization outputs a facing detection result of detection of physical facing between in-organization staffs. Inside facing data (ASMM) having the physical facing between the in-organization staffs quantized is generated based upon the facing detection result. Information capable of specifying physical facing to a non-organization staff who does not put on a sensor terminal is extracted from business information as information associated with business activities of respective in-organization staffs, and outside facing data (EXMT) having the physical facing between the in-organization staff and non-organization staff quantized is generated.The inside facing data (ASMM) and outside facing data (EXMT) are integrated to generate integrated facing data (ASGM_1).

Description

  The present invention uses the face-to-face data of a person acquired by a sensor terminal and face-to-face data derived from work information such as expense for business trips, digitizes communication in work, and shares the data within the organization. The present invention relates to a business information system that promotes improvement of business efficiency.

  For companies, people are important capital, and the state of the company changes greatly depending on the behavior of people. Nevertheless, human behavior itself has never been used as a material for management decisions or business improvement. This is probably because there was no quantitative representation of human behavior during work, and there was no standard for judgment.

  One type of human behavior during work is the exchange of information and knowledge through communication. Each person's knowledge of the relationship between people in the business leads to grasping the human network in his / her business and the human network in the organization. It has the potential to increase efficiency and revitalize the organization. There is a network correlation diagram in which one person is represented by one node and nodes where some kind of interaction occurs are connected by lines according to their strengths as a way of presenting the relationship between people visually and clearly.

  2. Description of the Related Art Conventionally, a technique for creating a network diagram between members of an organization from an email, an electronic document filing system, and a telephone communication record log is known as a method for creating a correlation diagram of people in business (Patent Document 1, Patent Document 2).

  Knowing the exchanges between members of the organization, that is, the exchanges within the organization to which they belong, is necessary for smooth execution of business, but it is also very important to know exchanges with people outside the organization such as outside the company. It is. Having interaction with outside the company will play a very important role in business, leading to expansion of human and technical networks and deeper understanding of the world situation.

JP2007-249307 JP 2009-59075 A

  As one of the information necessary for smooth execution of business and improvement of business efficiency, it is effective to quantitatively grasp physical confrontation including internal and external business, but there was no means to do so.

A typical example of the present invention is as follows. That is, the business-facing face-to-face data generation apparatus that processes the face-to-face detection results output from the sensor terminals attached to each of the in-organization personnel in order to detect physical facing between the in-organization personnel who are members of the organization But,
A face detection result acquisition unit for acquiring a face detection result output from each of the sensor terminals;
Based on the face-to-face detection result, an internal face-to-face data generation unit that generates internal face-to-face data that quantifies the physical face-to-face between the personnel in the organization;
A business information acquisition unit that acquires business information that is information related to the business activities of each of the personnel in the organization;
Information that can identify a physical meeting between an outside organization person who is not a member of the organization and an inside organization person is extracted from the business information, and the physical meeting between the inside organization person and the outside organization person An external face-to-face data generator that generates quantified external face-to-face data;
An integrated face data generation unit configured to integrate the internal face data and the external face data to generate integrated face data;

  According to the present invention, it is possible not only to grasp the amount of communication between internal personnel wearing sensors, but also to obtain the amount of communication with external personnel not wearing sensors from business information stored in the business information system. it can.

It is a figure which shows an example of a structure example and utilization scene of a business facing data generation apparatus. It is a figure which shows the example of a structure of a client, a personal client, and an application server. It is a figure which shows the structural example of a business information management server, a sensor network server, and each base station. It is a figure which shows the structural example of a sensor terminal. It is a figure which shows an example of a sequence until sensing data is stored in a sensor network server. It is a figure which shows an example of the basic content creation sequence in an application server. It is a figure which shows an example of the sequence at the time of the process of a content display being performed with a client. It is a figure which shows the process example of the browser determination performed with a client. It is a figure which shows a mode that emphasis display is performed within a display content. It is a figure which shows the example of the access control rule memorize | stored in an application server. It is a figure which shows an example of the business meeting matrix preparation process sequence performed with an application server. It is a figure which shows an example of the communication amount calculation process sequence performed with an application server. It is a figure which shows the example of the business information which an application server acquires from a business information management server, (a) is an example in which business information is information on a business trip expense adjustment, (b) is business information as information on a visitor application. It is a figure which shows an example, respectively. It is a figure which shows the example of the external business facing table produced | generated by an application server based on the business information illustrated in FIG. 13, (a) of the external business facing table produced | generated based on the information of business trip expense adjustment. (B) is a figure which shows the example of the external business facing table produced | generated based on the information of a visitor application, respectively. It is a figure which shows an example of the user attribute list hold | maintained at an application server. It is a figure which shows the example of the facing table hold | maintained in the sensing database of a sensor network server, (a) is an example of the facing table corresponding to the sensor terminal with terminal ID 1002, (b) is terminal ID 1003. It is a figure which shows the example of the facing table corresponding to a sensor terminal, respectively. It is a figure which shows the example of the acceleration data hold | maintained in the sensing database of a sensor network server. It is a figure which shows the example of the facing matrix hold | maintained in the secondary database of a sensor network server. It is a figure which shows the example of the business meeting matrix produced | generated by an application server. It is a figure which shows another example of the business meeting matrix produced | generated by an application server. It is a figure which shows the example of the network diagram created from the business facing matrix, (a) is an example of an in-house network diagram, (b) to (e) are examples of displaying a business network diagram in various forms, respectively. FIG. It is a figure which shows an example of the external meeting person list | wrist hold | maintained at an application server. It is a figure which shows an example of the external meeting person list update process sequence performed with an application server. It is a figure which shows an example of the business meeting matrix preparation process sequence performed with an application server. It is a figure which shows an example of the business meeting matrix produced | generated by an application server. It is a figure which shows the example of the business network figure produced from the business meeting matrix, (a) is an example displayed without distinguishing the meeting by visiting and the meeting by visiting, (b) to (d) are meeting by visiting It is a figure which shows the example which distinguishes and displays the meeting by visiting, respectively.

  First, an outline of the business meeting data generation apparatus according to the embodiment of the present invention will be described. Organizational personnel who are members of a certain organization are each equipped with a sensor terminal. This sensor terminal can detect a physical meeting between personnel within the organization. The term “physical face-to-face” means that communication is performed by approaching each other at an appropriate distance regardless of remote communication means such as telephone or electronic mail. While the personnel in the organization are physically facing each other, the sensor terminals attached to the respective personnel communicate with each other to acquire each other's sensor ID and detect the amount and closeness of communication between the personnel. Based on the detection results (face-to-face detection results) obtained from each sensor terminal, the business face-to-face data generation device generates internal face-to-face data that quantifies the physical face-to-face between personnel within the organization.

  On the other hand, since the non-organization personnel who do not belong to the organization do not wear the sensor terminal, the physical facing between the in-organization personnel and the non-organization personnel cannot be detected by the sensor terminal. As a substitute for the detection result obtained from the sensor terminal, the business face-to-face data generation device extracts physical face-to-face operations performed between internal and external personnel from the business information, and the internal and external personnel. Generates face-to-face data that quantifies the physical face-to-face.

  The above-mentioned internal face-to-face data and external face-to-face face data are integrated to generate integrated face-to-face data. Based on this integrated face-to-face data, not only the personnel within the organization but also the communication between personnel within and outside the organization is evaluated.

  In the following, an example will be described in which the employees in the organization are internal employees (employees) and the employees outside the organization are employees of another company, that is, external employees.

− First embodiment −
<Figure 1: Overall processing flow>
FIG. 1 shows a system outline of the first embodiment. In FIG. 1, the business meeting data generation apparatus is configured as a system including a plurality of apparatuses. In-house employees, that is, users who are employees (in FIG. 1, symbols of US, US2 to US8 are attached, and in the following, when users are not individually identified, they are indicated as “user (US)”). Business information that is related to the business of the client, for example, information on the expense of business trips, visitor application, working hours, schedule, business progress, etc., are personal clients (CP, CP2-3 are attached in FIG. 1) In the following description, if a personal client is not individually identified, it is input using “personal client (CP)”. The input business information is stored in the business information management server (GS) through the network (NW).

  Each user (US) wears a sensor terminal (indicated by TR and TR2 to 8 in FIG. 1 and referred to as “sensor terminal (TR)” if the sensor terminal is not individually identified below). Then, sensing data relating to the behavior of each employee and the exchange (interaction) between employees is acquired by these sensor terminals (TR). The interaction is detected by transmitting and receiving information using infrared rays as a transmission medium between the sensor terminals (TR) when the users (US) face each other. The sensor terminal (TR) is connected to the base station (GW) wirelessly or by wire. Sensing data acquired by each sensor terminal (TR) is transmitted to the base station (GW), transferred to the sensor network server (SS) through the network (NW), and stored. The sensor network server (SS) periodically performs the preprocessing of these sensing data and stores it as secondary data (internal meeting data).

  Content to be presented to the user (mostly images, but other data such as moving images, text data, audio data, etc.) may be requested by the user (US) via a client (CL) described later. Based on the application server (AS). The application server (AS) periodically acquires business information from the business information management server (GS) and acquires secondary data from the sensor network server (SS). Then, when creating content, external facing data is generated from the business information, and data (integrated facing data) that combines this and secondary data is generated. As business information, it is possible to use information such as expense settlement for business trips and application for visitor input by individual employees. The details of the travel expense adjustment and visitor application information will be described later in detail, but it is information that can extract the physical meeting between employees in the company and employees in another company. Other business information includes attendance (work hours), schedule, business progress report, business daily report, business report, financial information, production information, sales information, and the like. Outward facing data can be generated using appropriate information from these pieces of information.

  The client (CL) includes a viewer detector (CLVD) and a display (CLOD). The browser detector (CLVD) detects that the user (US) is browsing the display (CLOD) by receiving infrared information including the user ID transmitted from the sensor terminal (TR). As a method for detecting a viewer, in addition to the infrared sensor, a face recognition using a wireless transceiver, RFID, or camera may be used. When a viewer is detected, the client (CL) sends a list of viewers to the application server (AS). The application server (AS) returns content corresponding to the viewer described in the list to the client (CL). The client (CL) displays the content received from the application server (AS) on the screen (OD) of the display (CLOD). Also, the personal client (CP) can acquire and display the content from the application server (AS) in the same manner as the client (CL). At this time, in a personal client (CP) that does not have a viewer detector (CLVD), an ID of a specific user (US) who owns the personal client (CP) is set and always displayed at the time of display. Assuming that the user (US) is browsing, content directed to the user (US) can be displayed on the display device of the personal client (CP).

<FIGS. 2 to 4: Block diagram of the entire system>
2 to 4 are block diagrams illustrating the entire configuration of a sensor network system that implements the business facing data generation apparatus according to the embodiment of the present invention. For convenience of illustration, the components shown in FIGS. 2 to 4 are divided, but the illustrated components operate in cooperation with each other. Each function in the figure is realized by hardware, software, or a combination thereof, and each functional block is not necessarily accompanied by a hardware entity. In the following description, it is assumed that each component has a control unit, a storage unit, and a transmission / reception unit, as shown in FIGS.

  Each control unit is configured by a central processing unit (CPU, not shown) that is a processing unit such as a normal computer, and the storage unit is configured by a memory device such as a semiconductor storage device or a magnetic storage device. The transmission / reception unit includes a wired / wireless network interface. In addition, a clock or the like is provided as necessary.

  Business information entered by the user (US) using the personal client (CP), such as travel expense adjustment, visitor application, etc., is transmitted to the business information management server (GS) via the network (NW) and stored. Is done. The sensor terminal (TR) acquires sensing data related to the movement and communication of the person wearing the sensor terminal, and the sensing data is transmitted to the sensor network server (SS) and stored via the base station (GW). The The client (CL) or personal client (CP) receives the content created in the application server (AS) based on the data called from the business information management server (GS) and the sensor network server (SS), and the client (CL or CP) can be output to a display (CLOD or CPOD). The client (CL) constantly monitors the viewer, and processing for changing the display content is performed so that the content is presented in a method suitable for the viewer. FIGS. 2 to 4 also show a series of flows when this processing is performed.

  The five types of arrows in FIG. 2 to FIG. 4 have different forms of data or signal flow for time synchronization, associate, storage of acquired sensing data, analysis of sensing data, firmware update, and control signals, respectively. Represents each. Hereinafter, description will be made with reference to FIGS. 2 to 4 individually.

<Figure 2: Overall system 1 (CL, CP, AS)>
FIG. 2 shows a configuration example of the client (CL), the personal client (CP), and the application server (AS).

<About client (CL)>
The client (CL) inputs and outputs data as a contact (interface) with the user (US). The client (CL) includes an input / output unit (CLIO), a transmission / reception unit (CLSR), a storage unit (CLME), a control unit (CLCO), and a viewer detector (CLVD).

  The input / output unit (CLIO) is a part serving as an interface with the user (US). The input / output unit (CLIO) includes a display (CLOD), a touch panel (CLIT), a keyboard (CLIK), a mouse (CLIM), and the like. Other input / output devices can be connected to an external input / output (CLIU) as required.

  The display (CLOD) is an image display device such as a CRT (Cathode-Ray Tube) or a liquid crystal display. The display (CLOD) may include a speaker, a printer, and the like. When the touch panel (CLIT) is used to support the input by the user, the touch panel (CLIT) is installed so as to overlap the screen (OD) of the display (CLOD), and output and input are performed on the same screen. You can also show it.

  The transmission / reception unit (CLSR) transmits / receives data and commands to / from the application server (AS) and other devices connected to the network. Specifically, the transmission / reception unit (CLSR) transmits a content request to the application server (AS) and receives the content corresponding to the request from the application server (AS).

  The storage unit (CLME) is configured by an external recording device such as a hard disk, a memory, or an SD (registered trademark) memory card. The storage unit (CLME) is a detector ID (CLVDID) that is an ID of a viewer detector (CLVD) under the control of the client (CL), or a user ID list (CLID) that shows a list of valid user IDs. In addition, it has a client log (CLCB) for accumulating logs related to events that occur in the client and records of detected browsers and their detection times.

  The viewer detector (CLVD) is a terminal built in or externally connected to the client (CL), has a sensor such as an infrared transmitter / receiver (CLVDIR) or a human sensor (CLVDHI), and displays the client (CL) display ( This is for detecting a viewer who is browsing (CLOD). When the browser detector (CLVD) is externally connected to the client (CL), it is connected via an interface such as a USB. At this time, a plurality of viewer detectors (CLVD) can be connected to expand the detection range, or only the viewer detector (CLVD) can be replaced with another individual at the time of failure. When a viewer is detected by infrared rays, detection is performed by receiving a user ID periodically transmitted from an infrared transmission / reception unit (AB) provided in a sensor terminal (TR) worn by the user (US).

  The control unit (CLCO) includes a CPU (not shown), controls communication, inputs related to content selection from the user (US), and input / output control (CLCIO) for outputting content to the user (US). Control of the viewer detector (CLCBD), browser determination (CLCVD) for appropriately determining the viewer from the detected data, content list request (CLCLR) and content request (CLCLR) to the application server (AS) CLCCR) is executed.

  The detector control (CLCBD) controls the operation of the viewer detector (CLVD). A detector ID (CLVDID) is given and transmitted from the viewer detector (CLVD), or the received information is noise. Instead, the user ID list (CLID) is confirmed to be valid data, and the infrared ray transmission / reception timing in the viewer detector (CLVD) is controlled. The detector control (CLCBD) function may be implemented in a viewer detector (CLVD). However, if the function of the detector control (CLCBD) is performed by the control unit (CLCO) in the client (CL), the detector ID can be replaced even if the viewer detector (CLVD) is replaced with another individual. Since (CLVDID) and the operation of the detector do not change, it is an advantage that the viewer detector (CLVD) can be handled as the same individual without being aware of them.

In the browser determination (CLCVD), users who are considered to be browsing at the present time are sequentially identified based on the detection data obtained from the viewer detector (CLVD). For example,
(A) A user whose ID is detected only for a moment is regarded as not browsing,
(B) Even if browsing, infrared transmission from the sensor terminal (TR) may be hindered by an arm or the like, so browsing is performed even if no ID is detected for 30 seconds after the last detection. Considered
Etc., and the user ID of the viewer at that time is constantly monitored. In addition, it is also determined that the user who was browsing has left the display.

  In the content list request (CLCLR), a list of user IDs of the current viewer is sent to the application server (AS), and the content list having the browsing permission in the member configuration and the name of the viewer are sent from the application server (AS). receive. In this regard, a content list (ASCL) and an access control rule (ASAC) may be held in the client (CL), and a content list having browsing permission may be created in the client (CL). However, by creating a content list (ASCLM) that is permitted to be browsed on the application server (AS) side and searching for the name from the user ID, the name of the user as personal information is changed to the client (CL). This eliminates the need to hold the data and increases security.

  The input / output control (CLCIO) generates and controls a screen image to be output to the display (CLOD), and also accepts input from a touch panel (CLIT), a mouse (CLIM), and the like. The output screen is sequentially changed according to the input, that is, the user's operation. The input / output control (CLCIO) reflects the content list received from the application server (AS) and the name of the user, and displays a content switching button (OD_C) and a viewer selection button (OD_A) on the screen. The content switching button (OD_C) and the viewer selection button (OD_A) will be described later with reference to FIG. These buttons are used by the user to select content that the user wants to browse, and only buttons related to content that has browsing permission in the member configuration of the viewer at that time are displayed. By this mechanism, since the viewer cannot access content that does not have permission to browse, browsing restrictions can be realized.

  The input / output control (CLCIO) waits for input from the touch panel (CLIT) or mouse (CLIM) by a user operation, and when there is an input operation, a request for content corresponding to the input operation is sent to the application server (AS). And receive content information (CLCCR). The content information is mainly an image, and is received together with a highlighted coordinate list (ASEM) corresponding to the user ID. When there is no designation by the user operation, the latest date data is requested. The input / output control (CLCIO) displays a content image on a display, and an overlay (CLCEM) displays symbols such as a rectangle and a circle for emphasizing coordinates corresponding to the current viewer. . In addition, highlighting (CLCEM) displays a content image by moving or enlarging the image so that the portion including the current viewer is at the center of the screen. With this mechanism, it is possible to first focus attention on information having a high priority for the viewer at that time.

<Personal client (CP)>
The personal client (CP) is a PC used by a specific individual for business, and includes an input / output unit (CPIO), a transmission / reception unit (CPSR), a storage unit (CPME), and a control unit (CPCO). The control unit (CPCO) has a business information input (CPGS) function, and the user (US) inputs business information, for example, business trip expense settlement, visitor application, working hours, schedule, business progress, etc. Or a process for calling and browsing the input information.

  The personal client (CP) has substantially the same function as the client (CL) and is configured to be able to present content transmitted from the application server (AS). In that case, the personal client (CP) does not need to have a viewer detector (CLVD), but instead stores the user ID and password (CPIP) of one user who is the owner as a storage unit (CPME). ). As a result, the viewer performs display similar to that of the client (CL) on the assumption that the viewer is always a specific person, that is, a user of the personal client (CP).

  In addition, all the functions of the personal client (CP) correspond to the functions of the client (CL), and perform the same functions. That is, the input / output unit (CPIO) is an input / output unit (CLIO), the external input / output (CPU) is an external input / output (CLIU), the display (CPOD) is a display (CLOD), and the keyboard (CPIK) is a keyboard ( CLIK), mouse (CPIM) correspond to mouse (CLIM), and touch panel (CPIT) corresponds to touch panel (CLIT). The control unit (CPCO) is the control unit (CLCO), the input / output control (CPCIO) is the input / output control (CLCIO), the highlighting (CPCEM) is the highlighting (CLCEM), and the content list request (CPCLR) is The content list request (CLCLR), the content request (CPCCR) correspond to the content request (CLCCR), the transmission / reception unit (CPSR) corresponds to the transmission / reception unit (CLSR), and the storage unit (CPME) corresponds to the storage unit (CLME), respectively. .

<Application server (AS)>
The application server (AS) receives business information from the business information management server (GS), and receives secondary data of sensing data from the sensor network server (SS). The application server (AS) processes and analyzes the secondary data of the received business information and sensing data, and provides content information to be presented to the user (US) through the client (CL) or the personal client (CP). Generate. The content information is mostly an image, but may be other data such as a moving image, text data, audio data, or a combination of these data.

  The application server (AS) includes a transmission / reception unit (ASSR), a storage unit (ASME), and a control unit (ASCO). The transmission / reception unit (ASSR) is connected to the sensor network server (SS), the business information management server (GS), the NTP (Network Time Protocol) server (TS), the client (CL), and the personal client (CP) through the network (NW). ) And data transmission to and reception control.

  The storage unit (ASME) is configured by an external recording device such as a hard disk, a memory, or an SD memory card. The storage unit (ASME) stores the created content information, a program for creating content, and other data related to content creation. Specifically, the storage unit (ASME) includes a user attribute list (ASUL), an external meeting person list (ASPL), a content list (ASCL), a client log (ASCB), an access control rule (ASAC), a business meeting matrix ( ASGM), basic content file (ASBF), highlighted coordinate list (ASEM), secondary data reading program (ASSR), external meeting list update program (ASLU), business information reading program (ASGR), basic content creation program (ASGR) ASBP), a business meeting matrix creation program (ASMP), and a communication amount calculation program (ASCP) are stored. In FIG. 2, the program is expressed as “PGM”.

  The user attribute list (ASUL) can refer to the relationship between the ID of the sensor terminal (TR) and the name / user ID / affiliation of the user (US) wearing the sensor terminal (TR), mail address, attribute, etc. It is a comparison table. When the detected user ID of the viewer is received from the client (CL), the user attribute list (ASUL) is inquired, and the name of the corresponding user is returned to the client (CL). The user attribute list (ASUL) is not a connection between each user (US), but when generating a content indicating a connection between organizations to which each user (US) belongs, It is also referred when checking whether it belongs to.

  The outside meeting person list (ASPL) is a comparison table that can refer to the name, company name, affiliation, position, etc. of outside meeting persons. From the business information stored in the business information management server (GS), such as travel expense adjustment information, visitor application, schedule, business daily report, etc., the relevant data is extracted and combined to create an external meeting list (ASPL) Created. When grouping outside meeting persons for each company, an outside meeting person list (ASPL) is inquired.

  The client log (ASCB) is an accumulation of logs (CLCB) of the client (CL) and the personal client (CP), and the ID of the detected viewer, its time, the operated content, and the content being browsed This is a record of the type of item. The client log (ASCB) can be used to preferentially display content that is often selected by the user (US).

  The content list (ASCL) is a list describing a list of contents that can be presented by the client (CL). When the content list request (CLCLR) is received together with the user ID of the viewer from the client (CL), the content list (ASCL) and the access control rule (ASAC) are inquired together, and in the content list creation (ASCLM) A list that can be browsed by the current viewer is extracted and returned to the client (CL).

  The access control rule (ASAC) defines a condition for enabling browsing for each content. It is mainly defined by the user ID. For example, the user ID is a logical expression so that the user ID can be viewed when a user belonging to a specific organization or a user with a specific position or higher is included in the viewer. Defined by OR. Further, the logical expression AND may be defined so that browsing is possible only when all the specific members are detected by the browser detector (CLVD). Alternatively, it may be specified that browsing is not possible when a specific member is present.

  The business meeting matrix (ASGM) uses the constituent members of the organization and the meeting partners outside the organization as elements of the vertical axis (column direction) and horizontal axis (row direction), and information related to the face-to-face in each combination (time, number of times, etc.) Is converted into a numerical value, and the numerical value is input to the corresponding cell on the matrix. This numerical value is generated by secondary data of sensing data, that is, internal meeting data, and data obtained by processing and analyzing business information, that is, external meeting data. The elements on the vertical and horizontal axes of the matrix are not limited to the constituent members (internal employees) and the meeting partners (outside employees) outside the organization. A matrix may be generated as a relationship with an in-house department name or a company name of a face-to-face partner, or constituent members may be arranged on the vertical axis and department names may be arranged on the horizontal axis. Moreover, a person name and an organization name may be mixed on the same axis. In this case, based on the user list (ASUL) and the outside face-to-face person list (ASPL), the members belonging to the same affiliation are searched, and the face-to-face values for each organization are created by adding the face-to-face values of the corresponding members. Enter a value in the corresponding cell.

  The basic content file (ASBF) contains content information (as a result of basic content creation (ASCBC)) (many are images, but may be other data such as moving images, text data, audio data). An image based on sensor data relating to a specific period and a specific member may be accommodated, or a text content or coordinate value of the text is stored as text data, and a basic content file when called from a client (CL) May be combined and rearranged to generate an image. A program that changes the shape of an image in real time according to a user operation, such as a servlet, may be used. All contents are provided with tags such as date, user ID or organization ID, and content type, and are specified as one by a request from the client (CL).

  The highlighted display coordinate list (ASEM) is a list in which coordinates corresponding to the user ID are described for the image of the basic content file (ASBF). As a result, when a viewer is detected, the display coordinate position of the display portion corresponding to the viewer is known, so that the display portion can be highlighted with a square or circle. It is also possible to specify an emphasis method, for example, the shape, color, thickness, line type, etc. of the symbol to be emphasized. Further, additional information to be displayed beside the emphasized symbol, for example, the name of the user or text indicating the reason for emphasis can be designated. Even when the basic content file (ASBF) is not an image but is composed of character information or the like, by specifying a location of data corresponding to a specific user or a member of a belonging organization in the highlighted coordinate list (ASEM), the basic content file (ASBF) Emphasis information may be added to the content file (ASBF) and output to the display (CLOD or CPOD) of the client (CL or CP).

  The secondary data reading program (ASSR) is a program for reading secondary data of sensing data received from the sensor network server (SS). A file format such as a face-to-face matrix (ASMM) that is secondary data is held, and data of a designated date / time / target user is read in accordance with the format. The meeting matrix (ASMM) will be described later with reference to FIG.

  The business information reading program (ASGR) is a program for reading business information received from the business information management server (GS). Data corresponding to each item such as a business trip expense settlement table and a visitor application table of the specified date / time / target user is read. At that time, it is identified from the data format information (GSMF) in the business management server (GS) where the target information can be obtained by referring to the business information received from the business information management server (GS). To do.

  The external meeting person list update program (ASLU) extracts information related to external meeting persons, name, company name, affiliation, position, etc. from the data read by the business information reading program (ASGR) and puts it in the list as necessary. Append.

  The basic content creation program (ASBP) is various programs for creating basic content. At the time of basic content creation (ASCBC), this is started by timer activation (ASTK), manual activation by an administrator, or a request by a client (CL), and a basic content file is output.

  The business meeting matrix generation program (ASMP) is a part of the basic content creation program (ASBP), and is a program for creating a business meeting matrix that is a basis for creating contents for visualizing business meetings. In the business meeting matrix, the communication amount is recorded in an N × N matrix.

  The communication amount calculation program (ASCP) is a part of the business meeting matrix generation program (ASMP), and is a program for calculating the communication amount from the business information received from the business information management server (GS).

  The control unit (ASCO) includes a CPU (not shown), and executes data transmission / reception control and data processing. Specifically, a CPU (not shown) executes a program stored in a storage unit (ASME), thereby creating a content list (ASCLM), content selection / drawing control (ASCCS), timer activation (ASTK), basic Processing such as content creation (ASCBC) and highlight coordinate list creation (ASCEM) is executed. Also, the clock (ASCK) held inside holds the standard time of the site (where the system is installed) by periodically connecting to an external NTP server (TS).

  When the content list creation (ASCLM) receives the content list request (CLCLR) together with the user ID of the viewer from the client (CL), the content list (ASCL) and the access control rule (ASAC) are inquired together. This is a process of performing processing from extracting a list of contents permitted to be browsed by the viewer of the current client (CL) and returning it to the client (CL). The same applies when a content list request (CPCLR) is received from a personal client (CP).

  The content selection / drawing control (ASCCS) is specified in response to a selection operation by a user (US) browsing the display (CLOD) of the client (CL) or a request automatically issued from the client (CL). In this process, the content is extracted from the basic content file (ASBF), and if necessary, the corresponding highlight coordinate list (ASEM) is combined and returned to the client (CL). In the case of content that moves interactively according to the operation of the user (US) such as a servlet, the content selection / drawing control (ASCCS) controls the drawing. In addition, a process of creating a single image by combining basic content files in accordance with the member configuration of the user (US) who is browsing is performed.

  The timer activation (ASTK) activates the basic content creation (ASCBC) process when the clock (ASCK) reaches a predetermined time in advance.

  Basic content creation (ASCBC) reads the basic content creation program (ASBP), and obtains business information obtained from the business information management server (GS) and sensing data obtained from the sensor network server (SS) or its secondary data. Process and output basic content file (ASBF). Specifically, a basic content file (ASBF) such as a screen of the network diagram (FIG. 9) is output.

  When creating basic content (ASCBC), update the external meeting list as needed (ASCLU), calculate the amount of communication between internal employees and external meeting persons (ASCCC), and create a business meeting matrix (ASCMC) . At this time, information related to outside meeting is extracted from the business information including outside meeting information such as business trip expense settlement data, and the contents of the outside meeting person list are updated. Furthermore, based on the secondary data (internal meeting data) acquired from the sensor network server (SS), the business information, and the external meeting data generated based on the external meeting list as needed, the meeting in the work A matrix (business meeting matrix) is created. As a result, face-to-face data including not only the organization but also outside the company is created.

  When creating the basic content (ASCBC), the highlighted coordinate list is simultaneously output (ASCEM) as necessary. In the basic content creation process, a user ID and a coordinate value (display position in the screen) in which a symbol or graph corresponding to the user is drawn are stored and output as a list.

  By separating the client (CL) and the application server (AS) in this way, it is not necessary to store personal information or confidential information in the client (CL), so the client (CL) is placed outside the security area. Can do. However, the client (CL) and the application server (AS) may be integrated, and the content file and the user attribute list may be held in the client (CL).

<Figure 3: Overall system 2 (GS / SS / GW)>
FIG. 3 shows a configuration example of a business information management server (GS), a sensor network server (SS), and a base station (GW).

<Business information management server (GS)>
The business information management server (GS) stores the business information entered by the employee, such as data for the expense of business trips, visitor application data, and schedules, as well as information for the organization to manage employees and business progress. It is an accumulating server.

  The control unit (GSCO) of the business information management server (GS) has a business information storage (GSSDB) and a business information search (GSDS).

  Business information storage (GSSDB) includes business information entered by a user (US) using a personal client (CP), for example, information for settlement of business trip expenses (date, time, purpose, route, destination, face-to-face partner, etc.) Is transmitted through the network (NW), business information is acquired through the transceiver unit (GSSR). In the business information storage (GSSDB), the acquired business information is classified according to its type, and the business information and the time obtained from the clock (GSCK) when the business information is acquired are stored in the business unit (GSME). Accumulate in the information database (GSDB). The clock (GSCK) to be held holds the local standard time by periodically connecting to an external NTP server (TS).

  In business information retrieval (GSDS), a personal client (CP), an application server (AS). In response to a request from the sensor network server (SS), business information data and organization attribute information (GSOF) in the storage unit (GSME) are provided. At this time, after checking whether the request source has the authority to access the information, or after adjusting the format of the information in the storage unit (GSME), the transmission / reception unit ( Data is sent to the requester through GSSR).

  The storage unit (GSME) has a business information database (GSDB), organization attribute information (GSOF), and data format information (GSMF).

  In the business information database (GSDB), business information belonging to an individual transmitted from a personal client (CP), information on business results, progress, and accounting, for example, sales and expenditure of each department, results of plans, etc. Business information belonging to the organization such as achievement is stored.

  The organization attribute information (GSOF) stores, for example, information such as the department to which the employee belongs, position, age, and sex.

  The data format information (GSMF) stores information related to the data format (data structure) of information stored in the business information database (GSB).

<Sensor network server (SS)>
The sensor network server (SS) manages data collected from all sensor terminals (TR). Specifically, the sensor network server (SS) stores the sensing data sent via the base station (GW) in the sensing database (SSDB), and also the application server (AS) and client (CL). Sensing data or secondary data is transmitted based on a request from. Furthermore, the sensor network server (SS) manages information on the base station (GW) and sensor terminals (TR) under its management as needed. Also, this is the starting point when a control command for updating the firmware of the sensor terminal (TR) is executed.

  The sensor network server (SS) includes a transmission / reception unit (SSSR), a storage unit (SSME), and a control unit (SSCO).

  The transceiver unit (SSSR) transmits and receives data to and from the base station (GW), application server (AS), business information management server (GS), personal client (CP) and client (CL). In this case, communication control is performed.

  The storage unit (SSME) is configured by a data storage device such as a hard disk, and includes at least a sensing database (SSDB), a secondary database (SSDT), data format information (SSMF), a terminal management table (SSTT), and terminal firmware (SSFW). ). Furthermore, the storage unit (SSME) stores a program executed by a CPU (not shown) of the control unit (SSCO).

  The sensing database (SSDB) includes the sensing data acquired by each sensor terminal (TR), information on the sensor terminal (TR), and the base station (GW) through which the sensing data transmitted from each sensor terminal (TR) has passed. It is a database for recording information and the like. A column is created for each data element such as acceleration and temperature, and the data is managed. A table may be created for each data element. In either case, all data is managed in association with terminal information (TRMT) (FIG. 4), which is the ID of the sensor terminal (TR) that acquired the data, and information regarding the sensed time.

  The secondary database (SSDT) is a database that stores the result of sensing data processing (SSCDT) on data in the sensing database (SSDB). The secondary data stored in the secondary database (SSDT) is data that can be specified by physical processing between users (US), that is, in-house employees, which has been subjected to the standardization after being processed. This secondary data is a noise-free format suitable for creating basic content, such as a matrix representation of the total facing time between any two users (US) per day, Stored in When acquiring data for basic content creation (ASCBC) on the application server (AS), the operation is always unified so that the secondary data is acquired, so that the sensor terminal (TR) and communication conditions such as noise removal can be used. A content creation program can be developed without taking into account the characteristics of the sensing data that it depends on. As the database, the secondary database (SSDT) may be the same as the sensing database (SSDB), and only the table may be divided. If necessary, basic content creation (ASCBC) may acquire data before sensing data processing (SSCDT) from a sensing database (SSDB).

  Data format information (SSMF) includes a data format for communication, a method of separating sensing data tagged with a base station (GW) and recording it in a database, and secondary data subjected to sensing data processing (SSCDT). Information indicating a method of recording in the next database (SSDT) and a method of responding to the request for data are recorded. This data format information (SSMF) is referred to after data reception and before data transmission to perform data format conversion and data distribution.

  The terminal management table (SSTT) is a table that records which sensor terminal (TR) is currently managed by which base station (GW). When a sensor terminal (TR) is newly added under the management of the base station (GW), the terminal management table (SSTT) is updated. Further, when the base station (GW) and the sensor terminal (TR) are connected by wire, it is not necessary to constantly monitor the terminal management information.

  The terminal firmware (SSFW) stores a program for operating the sensor terminal (TR), and when the terminal firmware update (SSCFW) is performed, the terminal firmware (SSFW) is stored in the network (NW ) To the base station (GW), and further to the sensor terminal (TR) through the personal area network (PAN) or the like, and the firmware in the sensor terminal (TR) is updated.

  The control unit (SSCO) includes a CPU (not shown) and controls transmission / reception of sensing data and recording / retrieving to / from a database. Specifically, when the CPU executes a program stored in the storage unit (SSME), sensing data storage (SSCDB), terminal management information correction (SSTF), terminal firmware update (SSCFW), sensing data processing (SSCDT) ) And secondary data search (SSCTS).

  Sensing data storage (SSCDB) is processing for receiving sensing data sent from a base station (GW) and storing it in a sensing database (SSDB). Additional information such as time information, terminal ID, and time via the base station is combined and stored in the database as one record.

  The clock (SSCK) maintains a standard time by periodically connecting to the external NTP server (TS). When the clock (SSCK) satisfies a predetermined time or a specific condition, the sensing data processing (SSCDT) is activated (SSTK).

  In the sensing data processing (SSCDT), sensing data from the sensing database (SSDB), that is, data acquired by the sensor terminal (TR) is down-processed by a method specified by the data format information (SSMF), and the secondary data is processed. Generate. Secondary data is stored in a secondary database (SSDT). By starting sensing data processing (SSCDT) at regular intervals and processing newly added sensing data, the secondary database is always kept updated.

  When the secondary data search (SSCTS) receives a request from the application server (AS) or the business information management server (GS), secondary data corresponding to the request is extracted from the secondary database (SSDT), and the request source Process to return to. At that time, the search is performed based on tag information such as date and user ID given to the secondary data.

  The terminal management information correction (SSCTTF) updates the terminal management table (SSTT) when receiving a command for correcting the terminal management information from the base station (GW). As a result, it is possible to grasp the latest information regarding the sensor terminals (TR) under the control of each base station (GW).

  When the firmware of the sensor terminal (TR) needs to be updated, the terminal firmware (SSFW) in the storage unit (SSME) is updated manually or automatically. In response to the update of the terminal firmware (SSFW), the terminal firmware update (SSCFW) issues an instruction to update the firmware of the subordinate sensor terminal (TR) to the base station (GW). In addition, a response indicating that the firmware update has been completed at each sensor terminal (TR) is received, and the process is continued until the update of all the sensor terminals (TR) is completed.

<Base station (GW)>
The base station (GW) plays a role of mediating between the sensor terminal (TR) and the sensor network server (SS). When the sensor terminal (TR) and the base station (GW) are wirelessly connected, a plurality of base stations (GWs) are provided so as to cover areas such as living rooms and workplaces in consideration of the wireless reachable distance. Be placed. In the case of wired connection, an upper limit of the number of sensor terminals (TR) to be managed is set in accordance with the processing capability of the base station (GW).

  The base station (GW) includes a transmission / reception unit (GWSR), a storage unit (GWME), and a control unit (GWCO).

  The transmission / reception unit (GWSR) receives data from the sensor terminal (TR) wirelessly or by wire, and performs wired or wireless transmission to the sensor network server (SS). When wireless is used for transmission / reception, the transmission / reception unit (GWSR) includes an antenna for performing wireless communication. Further, as necessary, congestion control, that is, communication timing control is performed so that data is not lost during transmission and reception of sensing data. Also, the type of received data is distinguished. Specifically, the received data is identified as general sensing data, associate data, or time-synchronized response, etc., from the header part of the data, and these data are respectively appropriate. To pass the function.

  The storage unit (GWME) is configured by an external recording device (not shown) such as a hard disk, a memory, or an SD memory card. The storage unit (GWME) stores operation settings (GWMA), data format information (GWMF), terminal management table (GWTT), base station information (GWMG), and terminal firmware (GWTFD). The operation setting (GWMA) includes information indicating an operation method of the base station (GW). The data format information (GWMF) includes information indicating a data format for communication and information necessary for tagging the sensing data. The terminal management table (GWTT) includes terminal information of subordinate sensor terminals (TR) that can be currently associated, and local IDs distributed to manage those sensor terminals (TR). If the base station (GW) is connected to the sensor terminal (TR) by wire and it is not necessary to keep track of the subordinate sensor terminal (TR), the terminal management table (GWTT) may not be provided. . The base station information (GWMG) includes information such as the address of the base station (GW) itself. The terminal firmware (GWTFD) stores a program for operating the sensor terminal. When receiving a firmware update command and new terminal firmware from the sensor network server (SS), the terminal firmware (GWTFD) Firmware update data (TRDFW) is transmitted to the sensor terminal (TR) via PAN) (GWCFW).

  The storage unit (GWME) may further store a program executed by a CPU (not shown) of the control unit (GWCO).

  The control unit (GWCO) includes a CPU (not shown). When the CPU executes a program stored in the storage unit (GWME), the timing at which sensing data is received from the sensor terminal (TR), the processing of the sensing data, to the sensor terminal (TR) or the sensor network server (SS) The transmission / reception timing and the time synchronization timing are managed. Specifically, processes such as sensing data reception control (GWCSR), sensing data transmission (GWCSS), associate (GWCTA), terminal management information correction (GWCTF), terminal firmware update (GWCFW), and time synchronization (GWCS) are executed. To do.

  The clock (GWCK) holds time information. The time information is updated at regular intervals. That is, the time information of the clock (GWCK) is corrected by the time information acquired from the NTP server (TS) at regular intervals.

  Time synchronization (GWCS) transmits time information to a subordinate sensor terminal (TR) at a fixed interval or triggered by the sensor terminal (TR) being connected to a base station (GW). Thereby, the time of the clock (GWCK) of the plurality of sensor terminals (TR) and the base station (GW) is synchronized.

  In response to the associate request (TRTAQ) sent from the sensor terminal (TR), the associate (GWCTA) performs an associate response (TRTAR) that transmits the assigned local ID to each sensor terminal (TR). When the associate is established, the associate (GWCTA) performs terminal management information correction (GWCTF) for correcting the terminal management table (GWTT).

  The sensing data reception control (GWCSR) receives a packet of sensing data (SENSD) sent from the sensor terminal (TR). The header of the data packet is read to determine the type of data, or congestion control is performed so that data is not concentrated and transmitted simultaneously from a large number of sensor terminals (TR).

  In the sensing data transmission (GWCSS), the ID of the base station through which the data has passed and the time data thereof are given, and the sensing data is transmitted to the sensor network server (SS).

<Figure 4: Overall system 3 (TR)>
FIG. 4 shows a configuration of a sensor terminal (TR) which is an embodiment of the sensor node. Here, the sensor terminal (TR) has a name tag type shape and is assumed to hang from a person's neck. However, this is an example, and other shapes may be used. In many cases, a plurality of sensor terminals (TR) exist in the system described in the present embodiment, and a person belonging to an organization (in this embodiment, a user (US) who is an in-house employee) Equivalent to this). The sensor terminal (TR) has a plurality of infrared transmission / reception units (AB) for detecting the human face-to-face situation, a triaxial acceleration sensor (AC) for detecting the wearer's movement, and the wearer's speech and surrounding sounds. Various sensors such as a microphone (AD) for detection, an illuminance sensor (LS1F, LS1B) for detecting the front and back of the sensor terminal, and a temperature sensor (AE) are mounted. The mounted sensor is an example, and other sensors may be used to detect the face-to-face situation and movement between wearers.

  In the present embodiment, four sets of infrared transmission / reception units (AB) are provided. The infrared transmission / reception unit (AB) continues to periodically transmit terminal information (TRMT), which is unique identification information of the sensor terminal (TR), in the front direction of the sensor terminal (TR). When a person wearing another sensor terminal (TR) is positioned substantially in front (for example, front or diagonally front), the sensor terminal (TR) and the other sensor terminal (TR) have their respective terminal information (TRMT). Communicate with each other via infrared. For this reason, it is possible to record who is facing who. In addition, the viewer detector (CLVD) provided in the client (CL) receives this terminal information (TRMT), which user (US) is browsing the display (CLOD) of the client (CL). Can be detected. Conversely, the user (US) stayed at the installation location of the client (CL) when the sensor terminal (TR) received the detector ID (CLVDID) transmitted from the viewer detector (CLVD). Can be recorded.

  Each infrared transmission / reception unit (AB) includes a combination of an infrared light emitting diode for infrared transmission and an infrared phototransistor. The infrared ID transmitter (IrID) generates a signal corresponding to the terminal information (TRMT) which is its own ID, and outputs it to the infrared light emitting diode of each infrared transmitter / receiver (AB). In the present embodiment, all infrared light emitting diodes are turned on simultaneously by outputting the same signal to a plurality of infrared transmission / reception units (AB). Of course, a signal may be output to each infrared light emitting diode at an independent timing, or a different signal may be output to each infrared light emitting diode.

  The data received by the infrared phototransistor of the infrared transmission / reception unit (AB) is ORed by an OR circuit (IROR). That is, if the ID is received by at least one infrared light receiving unit, the sensor terminal (TR) can recognize the ID. Of course, a configuration having a plurality of ID receiving circuits independently may be employed. In this case, since the transmission / reception state can be grasped corresponding to each infrared transmission / reception module, it is also possible to obtain additional information such as in which direction the other sensor terminal (TR) facing each other is.

  Sensing data (SENSD) detected by the various sensors described above is stored in the storage unit (STRG) by the sensing data storage control unit (SDCNT). The sensing data (SENSD) is processed into a transmission packet by the communication control unit (TRCC) and transmitted to the base station (GW) by the transmission / reception unit (TRSR).

  At this time, it is the communication timing control unit (TRTMG) that takes out the sensing data (SENSD) from the storage unit (STRG) and determines the timing of wireless or wired transmission. The communication timing control unit (TRTMG) has a plurality of time bases for determining a plurality of timings. In FIG. 4, only time base 1 (TR1) and time base 2 (TR2) are shown.

  In order to update the data stored in the storage unit, in addition to the sensing data (SENSD) detected by the sensor immediately before, the batch sending data (CMBD) accumulated in the past and the firmware that is the operation program of the sensor terminal Firmware update data (FMUD).

  In the present embodiment, the sensor terminal (TR) detects that an external power supply (EPOW) is connected by an external power supply connection detection circuit (PDET), and generates an external power supply detection signal (PDETS). The time base switching unit (TMGSEL) that switches the transmission timing generated by the communication timing control unit (TRTMG) or the data switching unit (TRDSEL) that switches data to be wirelessly communicated by an external power supply detection signal (PDETS) (TR) is a unique configuration. In FIG. 4, as an example, when the time base switching unit (TMGSEL) switches the transmission timing by the external power supply detection signal (PDETS), the time base 1 (TB1) and the time base (TB2) are switched between two time bases. It is shown. In addition, as data to be communicated, among the sensing data (SENSD) obtained from the sensor, the collective feed data (CMBD) accumulated in the past, and the firmware update data (FMUD), a data switching unit is set by an external power supply detection signal (PDETS). A configuration in which (TRDSEL) switches to any data is illustrated.

  The illuminance sensors (LS1F, LS1B) are mounted on the front surface and the back surface of the sensor terminal (TR), respectively. Data acquired by the illuminance sensors (LS1F, LS1B) is stored in the storage unit (STRG) by the sensing data storage control unit (SDCNT), and at the same time is compared by the turnover detection unit (FBDET). When the name tag is correctly mounted, the illuminance sensor (LS1F) mounted on the front side receives external light, and the illuminance sensor (LS1B) mounted on the back side is connected to the main body of the sensor terminal (TR). Since the positional relationship is sandwiched between the wearer and the wearer, no extraneous light is received. At this time, the illuminance detected by the illuminance sensor (LS1F) takes a larger value than the illuminance detected by the illuminance sensor (LS1B). On the other hand, when the sensor terminal (TR) is turned over, the illuminance sensor (LS1B) receives extraneous light, and the illuminance sensor (LS1F) faces the wearer side. Therefore, from the illuminance detected by the illuminance sensor (LS1F), The illuminance detected by the illuminance sensor (LS1B) is larger.

  Here, when the illuminance detected by the illuminance sensor (LS1F) and the illuminance detected by the illuminance sensor (LS1B) are compared by the turnover detection unit (FBDET), the name tag node may be turned over and not correctly mounted. It can be detected. When turning over is detected by the turn over detection unit (FBDET), a warning sound is generated from the speaker (SP) to notify the wearer.

  The microphone (AD) acquires audio information. The surrounding information such as “noisy” or “quiet” can be known from the sound information. In addition, by acquiring and analyzing the voices of people, whether communication is active, stagnant, whether they are communicating with each other equally or unilaterally, whether they are angry or laughing , Etc. Face-to-face communication can be analyzed. Furthermore, the face-to-face state that the infrared transmitter / receiver (AB) could not detect due to the relationship of the person's standing position or the like can be supplemented by voice information and acceleration information obtained by a triaxial acceleration sensor (AC) described later.

  The voice acquired by the microphone (AD) acquires both the voice waveform itself and the signal obtained by integrating the voice waveform by the integration circuit (AVG). The integrated signal represents the energy of the acquired speech.

  The triaxial acceleration sensor (AC) detects the acceleration of the node, that is, the movement of the node. That is, from the acceleration data obtained from the triaxial acceleration sensor (AC), it is possible to analyze the intensity of movement of a person wearing the sensor terminal (TR) and behavior such as walking. Further, by comparing the acceleration values detected by the plurality of sensor terminals (TR) in time series, for example, the activity of communication between the persons wearing the sensor terminals (TR), the mutual rhythm, and the mutual correlation Etc. can be analyzed.

  In the present embodiment, in the sensor terminal (TR), the data acquired by the triaxial acceleration sensor (AC) is stored in the storage unit (STRG) by the sensing data storage control unit (SDCNT), and at the same time, the vertical detection is performed. The vertical direction of the name tag is detected by a circuit (UDDET). This is because two types of acceleration detected by the three-axis acceleration sensor (AC) are observed: a dynamic acceleration change due to the wearer's movement and a static acceleration due to the gravitational acceleration of the earth. Yes.

  When the sensor terminal (TR) is worn on the chest, the display device (LCDD) displays personal information such as the affiliation and name of the wearer. In other words, it behaves as a name tag. On the other hand, when the wearer holds the sensor terminal (TR) in his hand and points the display device (LCDD) toward himself / herself, the top and bottom of the sensor terminal (TR) is reversed. At this time, the content displayed on the display device (LCDD) and the function of the button are switched by the vertical detection signal (UDDETS) generated by the vertical detection circuit (UDDET). In the present embodiment, information to be displayed on the display device (LCDD) according to the value of the up / down detection signal (UDDETS), the analysis result by the infrared activity analysis (ANA) generated by the display control (DISP), and the name tag display An example of switching between (DNM) is shown.

  Whether the sensor terminal (TR) has faced another sensor terminal (TR) by transmitting / receiving infrared rays to / from the other sensor terminal (TR), that is, whether the sensor terminal (TR) It is detected whether or not the person wearing TR) faces a person wearing another sensor terminal (TR). For this reason, it is desirable that the sensor terminal (TR) be mounted on the front part of a person. As described above, the sensor terminal (TR) includes a sensor such as a triaxial acceleration sensor (AC). The sensing process in the sensor terminal (TR) corresponds to the processing step of sensing (TRSS1) in FIG.

  In many cases, there are a plurality of sensor terminals (TR), and when the sensor terminal (TR) and the base station (GW) are wirelessly connected, each is connected to a nearby base station (GW) and is a personal area. A network (PAN) is formed.

  The temperature sensor (AE) acquires the temperature of a place where the sensor terminal (TR) is located, and the illuminance sensor (LS1F) acquires illuminance such as the front direction of the sensor terminal (TR). As a result, the surrounding environment can be recorded. For example, it is possible to know that the sensor terminal (TR) has moved from one place to another based on the detected changes in temperature and illuminance.

  As input / output devices corresponding to the worn person, buttons 1 to 3 (BTN1 to 3), a display device (LCDD), a speaker (SP) and the like are provided.

  The storage unit (STRG) is specifically composed of a nonvolatile storage device such as a hard disk or a flash memory, and includes terminal information (TRMT) that is a unique identification number of the sensor terminal (TR), a sensing interval, and a display. Operation settings (TRMA) that define operations such as output contents are recorded. In addition, the storage unit (STRG) can temporarily record data and is used to record sensed data.

  The clock (TRCK) is a clock that holds time information (GWCSD) and updates the time information (GWCSD) at regular intervals. In order to prevent the time information (GWCSD) from deviating from that of other sensor terminals (TR), the time information is periodically corrected based on the time information (GWCSD) transmitted from the base station (GW). The time synchronization may also be executed immediately after an associate described later, or may be executed according to a time synchronization command transmitted from the base station (GW).

  The sensing data storage control unit (SDCNT) controls the sensing interval of each sensor according to the operation setting (TRMA) recorded in the storage unit (STRG) and manages the acquired data.

  The communication control unit (TRCC) performs transmission interval control and conversion to a data format compatible with wireless transmission and reception when transmitting and receiving data. If necessary, the communication control unit (TRCC) may have a wired communication function instead of wireless communication. The communication control unit (TRCC) may perform congestion control so that transmission timing does not overlap with other sensor terminals (TR).

  The associate (TRTA) transmits / receives an associate request (TRTAQ) and an associate response (TRTAR) to form a personal area network (PAN) with the base station (GW), and transmits a base station (GW) to which data is to be transmitted. decide. Associate (TRTA) is executed when the power of the sensor terminal (TR) is turned on and when transmission / reception with the base station (GW) is interrupted as a result of movement of the sensor terminal (TR) . In the case of wired connection, it is executed when it is detected that the sensor terminal (TR) is connected to the base station (GW) by wire. As a result of the association (TRTA), the sensor terminal (TR) is associated with one base station (GW) in a close range to which a radio signal from the sensor terminal (TR) can reach.

  The transmission / reception unit (TRSR) includes an antenna and transmits and receives radio signals. If necessary, the transmission / reception unit (TRSR) can perform transmission / reception using a connector for wired communication. Data (TRSRD) transmitted and received by the transceiver (TRSR) is transferred to and from the base station (GW) via the personal area network (PAN).

<Figure 5: Data storage sequence>
FIG. 5 is a sequence diagram showing a procedure for storing sensing data, which is executed in the embodiment of the present invention. FIG. 5 shows processing executed in each of the terminal (TR), the base station (GW), and the sensor network server (SS).

  First, when the sensor terminal (TR) is powered on and the sensor terminal (TR) is not associated with the base station (GW), the sensor terminal (TR) performs associate (TRTA1). That is, the terminal (TR) transmits an associate request to the base station (GW) and receives an associate response from the base station (GW). “Associate” means that the sensor terminal (TR) defines (establishes a connection) as a relationship of communicating with a certain base station (GW). By determining the transmission destination of the data by the associate, the sensor terminal (TR) can surely transmit the data.

  When the associate response is received from the base station (GW) and the associate is successful, the sensor terminal (TR) performs time synchronization (TRCS). In time synchronization (TRCS), the sensor terminal (TR) transmits a request for time synchronization to the base station (GW), receives time information from the base station (GW), and receives a clock (TRCK) in the sensor terminal (TR). ) Is set. The base station (GW) periodically connects to the NTP server (TS) and corrects the time. For this reason, time is synchronized in all the associated sensor terminals (TR). In this way, when analyzing the sensing results at each sensor terminal (TR) later, by comparing the time information added to the sensing data, communication between persons (in-house employees) at the same time It is also possible to analyze the mutual exchange of body expressions or audio information.

  Various sensors such as the three-axis acceleration sensor (AC) and temperature sensor (AE) of the sensor terminal (TR) start a timer (TRST) at a constant cycle, for example, every 10 seconds, and control acceleration, sound, temperature, illuminance, etc. Sensing (TRSS1). The sensor terminal (TR) detects the facing state by transmitting / receiving a sensor terminal ID, which is one of terminal information (TRMT), to / from another sensor terminal (TR) using infrared rays. Various sensors of the sensor terminal (TR) may always perform sensing without starting the timer (TRST). However, the power supply can be used efficiently by starting up at a constant cycle, and the sensor terminal (TR) can be used for a long time with one charge.

  The sensor terminal (TR) attaches time information of the clock (TRCK) and terminal information (TRMT) to the sensed data (TRCT1). When analyzing data, the terminal information (TRMT) identifies the person wearing the sensor terminal (TR).

  In the data format conversion (TRDF1), the sensor terminal (TR) adds tag information such as sensing conditions to the sensing data, and converts the data into a predetermined wireless transmission format. This format is stored in common with the data format information (GWMF) in the base station (GW) and the data format information (SSMF) in the sensor network server (SS). The converted data is then transmitted to the base station (GW).

  When transmitting a large amount of continuous data such as acceleration data and voice data, the sensor terminal (TR) limits the number of data to be transmitted at one time by dividing the data (TRBD1) into a plurality of packets. As a result, the risk of data loss during the transmission process decreases.

  Data transmission (TRSE1) transmits data to an associated base station (GW) through a transmission / reception unit (TRSR) in accordance with a wireless communication standard.

  When the base station (GW) receives sensing data from the sensor terminal (TR) (GWRE), the base station (GW) returns a reception completion response to the sensor terminal (TR). The sensor terminal (TR) that has received the response determines that transmission is complete (TRSO).

  If transmission is not completed (TRSO) even after a certain period of time (that is, the sensor terminal (TR) does not receive a response), the sensor terminal (TR) determines that data transmission has failed. In this case, the data is stored in the sensor terminal (TR) and transmitted together when the transmission state is established again. As a result, even if the person wearing the sensor terminal (TR) has moved to a place where the radio signal does not reach or the data is not received due to a malfunction of the base station (GW), the data is It becomes possible to save without losing. This makes it possible to obtain a sufficient amount of data and analyze the nature of the tissue. This mechanism in which data that has failed to be transmitted is stored in the sensor terminal (TR) and retransmitted is called collective sending.

  The procedure for sending data together will be described. The sensor terminal (TR) stores the data that could not be transmitted (TRDM), and requests association again after a predetermined time (TRTA2). Here, when an associate response is obtained from the base station (GW), the sensor terminal (TR) performs data format conversion (TRDF2), data division (TRBD2), and data transmission (TRSE2). These processes are the same as data format conversion (TRDF1), data division (TRBD1), and data transmission (TRSE1), respectively. Note that, during data transmission (TRSE2), congestion control is performed so that radios do not collide. After that, the process returns to normal processing.

  If the associate response is not obtained, the sensor terminal (TR) stores the newly acquired data while periodically performing sensing (TRSS1) and terminal information / time information attachment (TRCT1) until the associate succeeds. (TRDM). The data acquired by these processes is stored in the sensor terminal (TR) until a reception completion response is obtained from the base station (GW). The sensing data stored in the sensor terminal (TR) is stable when the associate is successful, when charging in the wireless range, or when connected to the base station (GW) by wire. Are transmitted to the base station (GW) collectively (TRSE2).

  Also, the sensing data transmitted from the sensor terminal (TR) is received (GWRE) by the base station (GW). The base station (GW) determines whether or not the received data is divided based on the divided frame number attached to the sensing data. When the data is divided, the base station (GW) performs data combination (GWRC), and combines the divided data into continuous data. Further, the base station (GW) gives the base station information (GWMG), which is a unique number of the base station, to the sensing data (GWGT), and sends the data to the sensor network server (SS) via the network (NW). Send to (GWSE). The base station information (GWMG) can be used in data analysis as information indicating the approximate position of the sensor terminal (TR) at that time.

  When the sensor network server (SS) receives data from the base station (GW) (SSRE), the sensor network server (SS) classifies the received data for each element such as time, terminal information, acceleration, infrared rays, and temperature (SSPB). This classification is performed by referring to a format recorded as data format information (SSMF). The classified data is stored in the appropriate column (row) of the record (row) of the sensing database (SSDB) (SSKI). By storing data corresponding to the same time in the same record, a search based on time and terminal information (TRMT) becomes possible. At this time, if necessary, a table may be created for each terminal information (TRMT). This data reception (SSRE), data classification (SSPB), and data storage (SSKI) are performed in the sensing data storage (SSCDB) in FIG.

<Figure 6: Basic Content Creation (ASCBC) Sequence>
FIG. 6 is a sequence diagram showing a basic content creation procedure executed in the embodiment of the present invention. FIG. 6 shows processing executed by each of the personal client (CP), the business management server (GS), the sensor network server (SS), and the application server (AS). In FIG. 6, the process executed by the application server (AS) corresponds to the basic content creation (ASCBC) process executed in the application server (AS) of FIG.

  Prior to the processing described below being performed in the application server (AS), business information input (CPGS) processing is appropriately performed in the personal client (CP). That is, the user (US) operates the personal client (CP) and inputs the business information described above as needed. This business information is transmitted to a business information management server (GS).

  In the business information management server (GS), the timer is started (GSTK) when the clock (GSCK) reaches a predetermined time, and the business information is based on the business information transmitted from each of the personal clients (CP). Processing to be stored in the database (GSDB), that is, business information storage (GSSDB) processing is performed.

  In the application server (AS), when the clock (ASCK) reaches a predesignated time, the timer is started (ASTK), and the execution of the basic content creation program (ASBP) is started. Alternatively, the basic content creation program (ASBP) is started when a user (US) having administrator authority of the application server (AS) operates at an arbitrary timing. The basic content creation program may include a plurality of types of programs, and may output a plurality of types of basic content files (ASBF) corresponding to the programs. Alternatively, the order of starting individual programs may be specified, and the output basic content file (ASBF) may be read to generate another basic content file (ASBF).

  Here, there is only one type of basic content, and the content is created based on both business information and secondary data. Furthermore, the content visualizes the face-to-face between internal employees and outsiders. The sequence will be described assuming that

  The application server (AS) sends the data request to the sensor network server (SS) and the business information server (GS) by specifying the target period and target user for the necessary data described in the basic content creation program (ASBP). (ASCBC1). The secondary data acquired from the sensor network server (SS) includes a face-to-face matrix (ASMM) that indicates the amount of communication within a period between arbitrary members in the company. In addition, the business information acquired from the business information management server (GS) includes business trip expense adjustment, customer application, and the like in which information such as a person who is considered to have met in business and the affiliation of the person is described.

  The sensor network server (SS) searches the secondary database (SSDT) based on the received request (SSCTS), and returns necessary data to the application server (AS). Similarly, the business information management server (GS) performs business information search (GSDS) based on the request and returns the business information to the application server (AS).

  The application server (AS) receives the secondary data and business information retrieved above (ASCBC2). Secondary data is read based on the data format using a secondary data reading program (ASPR) (ASCBC3). Similarly, the business information is read based on the data format using the business information reading program (ASGR) (ASCBC4).

  The information of the person to whom you meet (name, company name, etc.) is extracted from the business information such as travel expense adjustment and visitor application, etc., and the information of the person who has faced the business in advance (name, company name, etc.) The external meeting list is updated (ASCLU) by comparing with the outside meeting person list (ASPL) in which is written and additionally writing as necessary.

  Information related to the business (for example, name, start time, end time, face-to-face partner, business trip destination, nearest station, etc.) is extracted from business information such as travel expense adjustment and visitor application. The amount of communication with the other party is calculated (ASCCC) and external meeting data is generated.

  In addition, the face-to-face matrix (ASMM) showing the amount of communication within a period between any member in the company, which is one of the secondary data acquired from the sensor network server (SS), has been expanded, and the amount of communication with external partners Is described in the corresponding cell, a business meeting matrix is created (ASCMC). That is, a business face-to-face matrix in which internal face-to-face data and external face-to-face data are integrated is created.

  A process (ASCBC5) for rendering in a form that is easy for the viewer to understand based on the business-facing matrix created from the secondary data and the amount of communication with the external party extracted from the business information as described above. Done. An image file of the content obtained by rendering in this way is output (ASCBC6) and stored as a basic content file (ASBF) in the storage unit (ASME). A highlighted coordinate list (ASEM) is also created (ASCEM). This highlighting coordinate list is a list describing the coordinate values (display coordinate positions) in an image on which each user's ID and data related thereto are displayed, and includes information for designating the emphasis method. For example, in the case of emphasizing with a rectangular broken line, the upper left and lower right coordinate values (or information defining the coordinate value of the starting point and the display size of the rectangle when drawing the rectangle) are associated with the user ID. be written. Also, the access control rule (ASAC) is output together (ASCBC7). According to the access control rule (ASAC), the user ID of a user who can view the content (image) created by the above process is specified in the form of a logical expression or the like.

<FIG. 7: Content Display Sequence>
FIG. 7 is a sequence diagram showing a procedure for displaying contents, mainly images, executed in the embodiment of the present invention. In FIG. 7, processing executed in each of the application server (AS), the client (CL), and the sensor terminal (TR) is shown together with operations performed by the user (US).

  The client (CL) usually displays (CLD1) open content (for example, a network diagram not displaying a personal name, a message board, a weather forecast acquired from the Internet, etc.) that can be viewed by anyone on the display (CLOD). The browser detector (CLVD) is always in a standby state, and performs browser determination (CLCVD). If it is determined that there is no viewer, the open content is continuously displayed.

  When the user ID (CLD2) transmitted from the sensor terminal (TR) is received and it is determined that there is a viewer, the client (CL) creates a viewer ID list (CLD3) and uses the viewer ID list as an application. A request is sent to the server (AS) to request a list of contents that can be browsed by the member structure of the current viewer (CLCLR). The application server (AS) inquires of the content list (ASCL) and the access control rule (ASAC), extracts a list of contents that can be browsed by the member configuration of the viewer, and returns it to the client (CL) (ASCLM). The application server (AS) also queries the user attribute list (ASUL) and returns the viewer's name to the client (CL). Based on the content list, the client (CL) displays a content switching button (OD_C) indicating a link to the browseable content and a viewer selection button (OD_A) indicating the name of the viewer (CLD4). These content switching buttons (OD_C) and viewer selection buttons (OD_A) are shown in FIG. And it waits for a user (US) to push down a button (operating a touch panel) and to select content (CLD5). Or what was set as a default screen may be displayed on a display (CLOD), without waiting for a user's (US) operation. When an operation by the user (US) is detected, an image (or other type of data) of the selected content is requested from the application server (AS) (CLCCR). The application server (AS) selects the corresponding content according to the requested conditions (target date, target user, content type) and returns it to the client (ASCCS). In addition, the highlighted coordinate list (ASEM) corresponding to the content is also returned.

  The client (CL) displays the content received from the application server (AS) (CLD6), and further adds highlighting by surrounding the coordinate value corresponding to the current viewer with a rectangle (CLD7). When the user operates the screen (CLD8), the drawing and highlight positions and methods are changed accordingly (CLD9). For example, when a specific user is selected by the viewer selection button (OD_A), only the highlighted display of the user is blinked, or the display portion related to the user is enlarged and displayed. Then, a viewer determination (CLCVD) is performed at regular intervals. Therefore, when it is determined that the member configuration of the viewer has changed (CLD10), the drawing / highlight display is changed again (CLD11). Specifically, additional viewer names and highlights may be added that hide hidden viewer names and highlights. Further, when there is no viewer who has permission to access the currently displayed content due to a change in the member configuration and the viewing authority is lost (CLD12), the open content is automatically displayed (CLD13) and displayed. The content switching button (OD_C) linked to the selected content is hidden.

<FIG. 8: Flowchart of browser determination (CLCVD)>
FIG. 8 shows a flowchart of browser determination (CLCVD) performed by the client (CL). The browser determination (CLCVD) is a process that is always performed while the browser detector (CLVD) is activated.

  After start (CVDS), the client (CL) captures the infrared data received from the detector (CVD1), queries the user ID list, and if the infrared data is not a valid user ID listed there The data is judged as noise and removed (CVD2). Then, the number of times of receiving the user ID is counted for a predetermined time, for example, every 1 second or 5 seconds. It is determined whether the number of times is equal to or greater than a predetermined threshold number (CVD3). If this determination is affirmed, the received user ID is regarded as a viewer (CVD42). Otherwise, the user ID is not regarded as a viewer (CVD 41). This is to prevent a user (US) who has just passed for a moment from being included in the viewer. In this way, the client (CL) creates a list of user IDs (viewer ID lists) of users (US) regarded as viewers in a given time interval (CVD 5). The client (CL) sends the created viewer ID list to the application server (AS), and acquires a name corresponding to each user ID in the list (CVD6). That is, the viewer's name is acquired from the application server (AS). The above flow is repeated until the viewer determination (CLCVD) program is terminated manually or by a timer.

<Figure 9: Example of highlight screen when displaying network diagram>
FIG. 9 shows an example of a highlight display screen. As content information to be displayed, a case where display of an organization network diagram is selected is used as an example. The network diagram image received from the application server (AS) is displayed in the content display area (OD_B) of the screen (OD) displayed on the display (CLOD) of the client (CL). In accordance with the highlighted coordinate list (ASEM) received together, the part related to the current viewer is highlighted by being surrounded by a thick circle or the like. The viewer selection button (OD_A) displays the name of the user who is currently detected as a viewer. When one of the names is selected, the highlight corresponding to the name of the user flashes. Or the line type surrounding the name may change. In addition, in a network diagram of an organization with a large number of people, since one user is displayed in a small size, the image is moved and enlarged so that the current viewer can see the center of the content display area (OD_B). May be.

  As a result of selecting the network diagram display of the organization, in the example shown in FIG. 9, personnel in the organization (TN, KB, KM, KT, YD, YM, FW, SK enclosed in circles are the respective personnel. And a name thereof) and a connection between external organizations (X and Y2 companies surrounded by a rectangle mean each external organization and the organization name).

  In the display state illustrated in FIG. 9, when the display of the network diagram indicating the connection with the non-organization personnel is selected, the personnel belonging to each of the X company and the Y2 company (external to the organization) The name of the personnel) is displayed, and a network diagram showing the connection between those outside the organization and the personnel in the organization is displayed.

<FIG. 10: Access Control Rules (ASAC)>
FIG. 10 shows an example of the data structure in the access control specification (ASAC) file recorded in the storage unit (ASME) of the application server (AS). The access control rule (ASAC) file is output in accordance with basic content creation (ASCBC) in the application server (AS), and describes conditions for accessing the corresponding basic content file (ASBF). is there. For example, an access condition is defined such that a file related to a certain department can be browsed if at least one member of the department is included in the viewer.

  In the access control rule (ASAC), the file ID (ASAC01), file type (ASAC02), and access condition (ASAC03) of the basic content file are described in association with each other. Note that the file type (ASAC02) can be omitted if the files can be individually identified by the ID. The file ID (ASAC01) is an ID individually assigned to the file output in the basic content creation (ASCBC). Even if the content is the same type, another ID is assigned if the data target period and target member are different. to be dumped. For example, in the case of a network diagram, access permission is granted to all members of a department in a diagram that targets a department, but access permission is granted only to members of that department in a figure that targets a department. In this way, access conditions can be determined corresponding to individual files.

  The file type (ASAC02) indicates the type of content. Used for heading and classification when displaying a button in the content switching button (OD_C). “In-house network”, “business network”, and “business tapestry” in the file type (ASAC02) illustrated in FIG. 10 mean content presentation forms.

  The access condition (ASAC03) is a logical expression showing the user ID of the viewer necessary for displaying the corresponding file. “1000”, “1001”, etc. in FIG. 10 mean the user ID. As shown in the rows (RE03, RE04), when a plurality of user IDs are connected by [AND], display permission is not issued unless all the viewers corresponding to these user IDs are detected at the same time. Means that. Further, as shown in the row (RE05), when a plurality of user IDs are connected by [OR], it means that display is permitted if at least one of them is detected as a viewer. Further, as shown in the row (RE06), by using the NOT condition, it is possible to restrict the display permission from being given when a specific user (in this example, a user whose user ID is 1000) is browsing. it can. As shown in the row (RE07), display permission can be given to everyone by [ALL], that is, it can be defined as open content.

  As described above, display conditions can be given to individual files by defining the display permission by a logical expression. As a result, the file that can be viewed changes as the member configuration of the viewer changes, so that the motivation “I want to browse with other members next time” can be encouraged.

<Fig. 11: Flowchart for creating a business meeting matrix>
In creating the basic content shown in FIG. 6, when creating the content that visualizes the business meeting between the in-house employee and the outsider, a business meeting matrix is created in which the face-to-face state is represented by an N × N matrix.

  FIG. 11 shows a flowchart for creating a business meeting matrix executed by the application server (AS). Here, an example of business face-to-face matrix creation based on a combination of in-organization structural members as internal personnel and external face-to-face persons as external personnel is shown.

  After the start (CMCS), when the application server (AS) sends the business information type, target user, target period, and other conditions to the business information management server (GS), the business information management server (GS) meets the conditions. Information to be searched is retrieved and transmitted to the application server (AS) as business information. The application server (AS) reads the business information transmitted from the business information management server (GS) (CMC1), and extracts information related to meeting with an outsider from the business information (CMC2). For example, when business trip expense adjustment information is read as business information, information on the name of the business traveler, business trip destination, business start time, and business end time is extracted as minimum information, and the name of the face-to-face partner is also extracted if possible. . From the business start time and business end time, the amount of communication between the business traveler and the face-to-face partner is calculated (ASCCC), and an outside business face-to-face table describing the business trip person, the face-to-face partner and the face-to-face time is created (CMC3). A method for calculating the communication amount will be described in detail later with reference to FIG. If the name of the face-to-face partner is not described in the business trip expense settlement information, the name of the business trip (company name) can be written in the place of the face-to-face partner.

  From the outside business face-to-face table created in CMC3, the number of face-to-face opponents, excluding overlapping face-to-face opponents, is counted (CMC4).

  On the other hand, processing (CMC5) for reading a face-to-face matrix (ASMM) obtained from the sensor network server (SS) and indicating the amount of communication within an arbitrary period between arbitrary members in the company is performed. In creating the business face-to-face matrix, the face-to-face matrix (ASMM) indicating the internal face-to-face inside the company is used as a base, and is expanded to add a part representing the face-to-face (outside face-to-face) with an outsider. Therefore, first, a process (CMC6) is performed to expand the matrix size of the meeting matrix (ASMM) by the number of meeting partners outside the company. For example, if the size of the face-to-face matrix (ASMM) is 30 × 30 (this indicates that the number of in-house target members is 30) and the number of external face-to-face opponents is 15, a 45 × 45 matrix Is created. The face-to-face matrix (ASMM) data is copied as it is to the 30 × 30 portion indicating the internal face-to-face. The 30 × 15 and 15 × 30 portions indicating the face-to-face contact between the in-house target member and the outside face-to-face partner are defined as an extended matrix (EXMT), and the data of the external work face-to-face table created in CMC3 is the corresponding cell of the extended matrix (EXMT). (CMC7). At that time, the place in the matrix is determined from the business trip person described in the outside business face-to-face table and the face-to-face partner, and the communication amount between the business trip person and the face-to-face partner is described in the determined place. If the place where the communication amount is described overlaps (when there is data of the same business traveler and meeting partner), the communication amount is added to the value at that place and described. For example, when a specific member in the company has faced a specific member outside the company for a plurality of days, the amount of the face-to-face is added by the above processing.

  It is determined whether or not all the data described in the external business meeting table is reflected in the expansion matrix (CMC8), and the communication amount is continuously embedded in the matrix until all the data is reflected. When all the data of the outside business meeting table is reflected, the business meeting matrix (ASGM) is completed (CMC9) and returned (CMCR).

  In FIG. 11, a flowchart is shown so that the processes from CMC1 to CMC4 and the process of CMC5 are performed in parallel, but actually, even if the processes are performed concurrently in this way. The processing may be performed serially.

  What has been described so far is an example of creating a business meeting matrix (ASGM_1) based on a combination of in-organization structural members, that is, in-organization personnel, and external meeting persons, that is, outside-organization personnel. With this business meeting matrix (ASGM_1), it is possible to grasp the meeting situation between individuals including inside and outside the company. This business meeting matrix (ASGM_1) will be described later with reference to FIG.

  Now, in order to grasp the business trip situation, not only how much the employee (internal organization personnel) met with the outside employee, but also information such as how much the employee visited which company (external organization) is important. In order to obtain the information, in the flowchart shown in FIG. 11, a business meeting matrix (ASGM_2) centered on the combination of the organization members (internal personnel) and the name of the company on the business trip (external organization) is used. What is necessary is just to create (the business meeting matrix (ASGM_2) will be described later with reference to FIG. 20). Specifically, in the processing of CMC 4, the number of business trip destinations is counted from the outside business facing table, and duplicate business trip destinations are not counted. In CMC 6, the matrix size of the meeting matrix (ASMM) is expanded by the number of business trip destinations. In CMC 7, the location of the expansion matrix (EXMT) is determined from the business travelers and business trip destinations described in the external business meeting table, What is necessary is just to describe the communication amount of the business trip person and the other party of the business trip destination in the place. If the communication amount description locations overlap (when there is a combination of the same business trip person and business trip destination), the communication amount is added to the value at that location and described. For example, when a specific member in the company travels to a specific business destination for a plurality of days, the amount of communication increases corresponding to the business trip.

  In the above, the example in which the business meeting matrix (ASGM_1) and (ASGM_2) are created using the information that the personnel in the organization travels to the external organization and meets the personnel outside the organization has been described. However, since personnel within the organization may meet with a visit from a member outside the organization, it is also possible to reflect the meeting after the visit with the business facing matrix. In that case, the visitor application in the business information may be used. In other words, based on the information on the visitor application, it is possible to extract information on who in the organization receives the visit from the external organization and from what time of day to when. Therefore, it is possible to add information to the external business meeting table by using such information and create business meeting matrices (ASGM_1) and (ASGM_2).

<FIG. 12: Flowchart of Communication Amount Calculation (ASCCC)>
FIG. 12 shows a flowchart of communication amount calculation (ASCCC) executed by the application server (AS). The amount of communication is calculated from business information such as business trip expense settlement information obtained from the business information management server (GS).

  After the start (CCS), first, the basic setting file is read (CC1). The basic setting file includes travel time and minimum meeting time. The travel time is set to the same time as the travel time associated with a business trip, and the minimum meeting time is set to the same value as the minimum value of the meeting time during a business trip or visitor. For example, the travel time is set to 60 minutes and the minimum meeting time is set to 30 minutes, which are described in advance in the file. If the acquired business information is visitor application information, the travel time is preferably 0 minutes because the travel information is not accompanied.

  From the information on outside meeting (face-to-face with outside organization) extracted by CMC2, the start time and end time related to meeting on business trip or visit are further extracted (CC2), and the outside time is subtracted from the end time by starting time Business hours are calculated (CC3). In addition, the time required for meeting after the visit is calculated as outside business hours. Out of this outside business time, the time excluding travel time is regarded as the amount of communication, but here the travel time is fixed, so most of the outside business time becomes travel time depending on the meeting place, and the amount of communication ( There is a possibility that the (facing time) becomes zero. The amount of communication cannot be zero in the face-to-face after a business trip or visit. Therefore, the minimum amount of communication is ensured as follows by predetermining the minimum meeting time that is assumed to be the minimum unit (minimum amount) of the meeting time during a business trip or visit. In other words, the provisional meeting time is calculated by subtracting the travel time read in the basic setting from the event time (outside business time) by the round trip (CC4). The temporary meeting time is compared with the minimum meeting time read in the basic setting (CC51). When the temporary meeting time is equal to or longer than the minimum meeting time (CC51: yes), the temporary meeting time is regarded as the communication amount. (CC61). On the other hand, when the provisional meeting time is shorter than the minimum meeting time (CC51: no), the outside work time and the minimum meeting time are compared (CC52). When the outside business time is equal to or longer than the minimum meeting time (CC52: yes), the minimum meeting time is regarded as the communication amount (CC62). On the other hand, when the external business time is less than the minimum meeting time (CC52: no), the external business time is regarded as the communication amount (CC63). This value is returned as a communication amount and returned (CCR).

<Figure 13: Example of business information (ASGD)>
FIG. 13 shows an example of business information (ASGD) that the application server (AS) acquires from the business information management server (GS). (A) is business information (ASGD_1) for the settlement of business trip expenses, and (b) is business information (ASGD_2) for customer application.

  In acquiring the business information, conditions such as the type of business information, the target user, and the target period are transmitted from the application server (AS) to the business information management server (GS). The business information management server (GS) searches for information corresponding to the condition and transmits it to the application server (AS) as business information. FIG. 13 shows the conditions for the information search as follows: (a) business trip expense adjustment information or (b) visitor application information, and target user as a user number in the user attribute list (ASUL). ASUIT 1) 0 to 7 and an example when the target period is set to be January 1, 2011 to February 28, 2011. The user attribute list (ASUL) will be described later with reference to FIG.

  The business information (ASGD_1) for the settlement of business trip expenses in (a) includes the user name (ASGD_11), the date of business trip (ASGD_12), the company name of the business trip destination (ASGD_13), the business trip start time (ASGD_14), and the business trip end time (ASGD_15). ), Departure place (place name or station name) (ASGD_16), arrival place (place name or station name) (ASGD_17), face-to-face partner (ASGD_18), and the like are recorded in association with each other. Since the expense for the business trip is settled by each individual, when a plurality of people go to the same business trip destination, data for the number of people is created. Moreover, the meeting partner (ASGD_18) is not limited to one person. If a plurality of persons can be described when inputting business information, the number of persons may be recorded.

  The business information (ASGD_2) of the visitor application in (b) includes the name of the responder (ASGD_21), the visit date (ASGD_22), the visit start time (ASGD_24), the visit end time (ASGD_25), and the visitor affiliation (company name) ( Information such as ASGD_23) and meeting partner (ASGD_28) is recorded in association with each other. Since a visitor application is applied on behalf of one of the recipients, a set of data is created for each visit received. For this reason, in the business information input, it is common to be able to describe a plurality of names of responders and visitors per case, and there are a plurality of names of responders (ASGD_21) and meeting partners (ASGD_28). The name is often written.

<Figure 14: External Business Meeting Table (ASBT)>
FIG. 14 is an example of an outside business meeting table (ASBT) in which information related to outside business meeting is extracted from the business information (ASGD_1, ASGD_2) and described together with the calculated communication amount. FIG. 14A is an outside business meeting table 1 (ASBT_1) generated by extracting from business information (ASGD_1) for business trip expense settlement, and FIG. 14B is extracted from business information (ASGD_2) of a customer application. This is the outside business meeting table 2 (ASBT_2) generated in this manner.

  In the outside business meeting table 1 (ASBT_1) for clearing business trip expenses shown in FIG. 14A, the user name (ASBT_11), the date of the business trip (ASBT_12), the company name (ASBT_13) of the business trip destination, the communication amount (ASBT_14), and the face-to-face Information such as the partner (ASBT_15) is recorded in association with each other. For data other than the face-to-face partner (ASBT_15) and the communication amount (ASBT_14), the corresponding data of the business information (ASGD_1) is copied as it is. The face-to-face partner (ASBT_15) copies the name of the face-to-face partner name (ASGD_18) as it is, and if it does not contain the data, [Corporate name] (ASGD_13) or [Business trip destination] Company name] (ASGD_13) with a character string of “Other” added. For the communication amount (ASBT_14), the value calculated by the communication amount calculation (ASCCC) processing described with reference to the flowchart of FIG. 12 based on the business trip start time (ASGD_14) and the business trip end time (ASGD_15) is substituted. .

  In FIG. 14B, the external application face-to-face table 2 (ASBT_2) of the visitor application includes a responder name (ASBT_21), a visit date (ASBT_22), a visitor affiliation (company name) (ASBT_23), a communication amount (ASBT_24), Information such as the name of the face-to-face partner (visitor) (ASBT_25) is recorded in association with each other. In the business information referred to when creating the external business meeting table 2 (ASBT_2), when a plurality of visitor names (ASGD_21) and face-to-face names (ASGD_28) are recorded, that is, the visiting side in one meeting, When there are a plurality of personnel attending on the response side, as shown in FIG. 14, each of the responders and visitors is disassembled into one person and the data is described. For example, for one visitor application, if there are 4 responders and 3 visitors, 12 sets of data are created.

  The communication amount (ASBT_24) is recorded based on the visit start time (ASGD_24) and the visit end time (ASGD_25), which is calculated by the communication amount calculation (ASCCC) process described with reference to the flowchart of FIG. The

<FIG. 15: Example of User Attribute List (ASUL)>
FIG. 15 is a diagram illustrating an example of a format of a user attribute list (ASUL) stored in the storage unit (ASME) of the application server (AS). In the user attribute list (ASUL), a user number (ASUIT1), a user name (ASUIT2), a terminal ID (ASUIT3), and a part (ASUIT4) and section (ASUIT5) to which the user belongs are recorded in association with each other. The user number (ASUIT1) indicates a serial number of an existing user. The user name (ASUIT2) is a name or nickname notation of the user (US) used when generating a display screen or content, and the terminal ID (ASUIT3) is the terminal information of the sensor terminal (TR) owned by the user (US). It is shown. The user (US) and the terminal ID (ASUIT3) basically correspond one to one. Also, the department (ASUIT4) and section (ASUIT5) to which the user belongs is information corresponding to the organization to which the user (US) belongs. For example, when creating basic content in organizational units, it is included in the data based on this information. Identify members

  In FIG. 15, information on the user and the organization to which the user belongs is defined in the form of a table, but this may be shown hierarchically using XML or the like. In such a case, it is possible to indicate according to the organizational hierarchy, such as A section under company A and A1 section under section A, and the individual user name in the corresponding organization And terminal ID can be described. Since the same person may belong to a plurality of organizations concurrently, information on a plurality of organizations may be added corresponding to one user.

<FIG. 16: Example of meeting table stored in sensing database (SSDB)>
The sensing database (SSDB) records a plurality of types of sensing data corresponding to each of a plurality of members. An example of a table in which meeting data by infrared transmission / reception is collected is shown in FIGS. 16A and 16B. Shown in FIG. 16A shows a meeting table (SSDB_IR_1002), which is assumed to be a table in which data acquired by a sensor terminal (TR) whose terminal ID is 1002 is collected. Similarly, FIG. 16B shows a meeting table (SSDB_IR_1003), which is a table in which data acquired by the sensor terminal (TR) whose terminal ID is 1003 is collected. In addition, it is also possible not to divide a table for every acquired sensor terminal (TR) by adding infrared receiving side ID to a column. Further, other data such as acceleration and temperature may be included in the same table. Further, the detector ID (CLVDID) received from the infrared transmitter / receiver (CLVDIR) of the viewer detector (CLVD) is also recorded in the infrared transmitter ID (DBR10) in the same manner as the user ID received from the sensor terminal (TR). May be. In this case, by searching the table using the detector ID as a key, it is possible to check who has viewed the display at which location.

  16 (a) and 16 (b), 10 sets of the time (DBTM) when the sensor terminal (TR) transmitted data, the infrared transmission side ID (DBR1), and the number of receptions from the ID (DBN1) are 10 sets. (DBR1 and DBN1, DBR2 and DBN2,..., DBN10 and DBN10) are stored examples. For example, when data is transmitted at a frequency of once every 10 seconds, this table shows how many infrared rays are received from which sensor terminal (TR) in 10 seconds after the previous transmission. Become. In the example shown in FIG. 16, when facing a plurality of sensor terminals (TR) within 10 seconds, it is possible to record up to 10 sets. The number of groups that can be recorded can be freely set. When meeting, that is, when there is no infrared reception, the value of the table is “null”. Also, in FIGS. 16A and 16B, the time is shown up to milliseconds, but any time format may be used. The time interval is not limited to 10 seconds and can be changed according to the purpose.

<FIG. 17: Example of Sensing Database (SSDB): Acceleration Data Table>
FIG. 17 shows an example of an acceleration data table (SSDB_ACC — 1002) as an example of sensing data stored in the sensing database (SSDB) in the sensor network server (SS). This is basically the sensing data acquired by the sensor terminal (TR) as it is, and is the data that has not been subjected to the down-processing. A table is created corresponding to each individual, and is correlated with time information (DBTM) at each sampling period (for example, 0.02 seconds), along the X axis (DBAX), Y axis (DBAY), and Z axis (DBAZ). Acceleration data for each of the three axial directions orthogonal to each other is stored. The raw numerical value detected by the acceleration sensor may be stored, or the value after the unit is converted to [G] may be stored. Such an acceleration data table is created for each member, and stored in association with the sensed time information. If a column indicating a user ID is added, the table can be integrated without being divided for each individual (a table in which data of all personnel in the organization is recorded).

<FIG. 18: Example of Secondary Database (SSDT): Meeting Matrix>
FIG. 18 shows an example of a face-to-face matrix (ASMM) as an example of a secondary database (SSDT) that stores the results of sensing data processing (SSCDT) in the sensor network server (SS). The secondary database is a database that stores the information of a specific user for a certain period in a common format after finishing the preprocessing.

  FIG. 18 shows an example of a face-to-face matrix (ASMM) showing the total face-to-face time within a predetermined period between any members in the organization. The face-to-face matrix is called an adjacency matrix in network analysis terms. The meeting matrix (ASMM) calculates the total meeting time between members of an arbitrary combination based on the meeting table (SSDB_IR) described with reference to FIG. 16, and arranges them in a matrix format. The face-to-face matrix illustrated in FIG. 18 indicates that the user with the user number 2 and the user with the user number 3 faced each other for 750 minutes, as shown in the element (MM3_4) and the symmetric element (MM4_3). As the data format of the face-to-face matrix, text may be used, or each column of the database may be associated with the names and user IDs of both members. When calculating the total face-to-face time from the face-to-face table (SSDB_IR), the values after correcting the non-face-to-face time may be summed rather than being summed as they are. For example, the correction can be made in consideration of the lunch break time. FIG. 18 shows an example in which the face-to-face matrix (ASMM) is a symmetric matrix, but it may be an asymmetric matrix depending on the processing method.

  In addition, the meeting matrix (ASMM) does not total the meeting time using only the meeting table (SSDB_IR), but refers to the acceleration data table (SSDB_ACC) of both users at the meeting time, and the acceleration is both or at least Only when one of the values is equal to or greater than the threshold value may be considered to be facing and added to the count. As a result, when the sensor terminal (TR) happens to be left unattended, or when it is not communicating with each other, it is not included in the meeting time. Thus, only data effective as communication can be recorded in the face-to-face matrix.

  Further, the face-to-face matrix (ASMM) may be provided with a threshold value of the face-to-face time per day, for example, per day, and the number of days exceeding the threshold value within the period may be used as the element value. For example, if there are three days exceeding the threshold, it can be recorded as 3. In this case, when a conversation with a large amount of information is made within a certain period (one day), it is considered that the persons are linked.

<FIG. 19: Example of business meeting matrix (ASGM_1)>
FIG. 19 shows an example of a business meeting matrix (ASGM_1) centered on a combination of arbitrary members in the company and outside meeting persons. The business face-to-face matrix (ASGM_1) is one of the secondary data acquired from the sensor network server (SS), and is internal face-to-face data indicating face-to-face between arbitrary members in the company, that is, face-to-face matrix (ASMM), The outside meeting data indicating the meeting of the members of the outside and the outside meeting person, that is, the extended matrix (EXMT) is combined.

  The expansion matrix (EXMT) is a matrix in which an arbitrary member in the company and an outside meeting person are taken as respective axes. In FIG. 19, an arbitrary member in the company is assigned a terminal ID (named [TN in FIG. 19) according to the correspondence between the terminal ID (ASUIT3) and the user name (ASUIT2) in the user attribute list (ASUL) illustrated in FIG. ], [KT], [KM], [KB], [YM], [FW], [YD], and [SK] are names). Further, in FIG. 19, the company name ([X company], [Y company], [Z company] is the company name in FIG. 19) and the name ([HD], [YA], [MR in FIG. 19) as outside meeting persons. ], [FI] is a name) is recorded, but only a name may be recorded.

  According to the outside business face-to-face tables (ASBT_1, ASBT_2) described with reference to FIG. 14, the communication amount between the in-house member and the outside face-to-face person is described in the corresponding cell in the expansion matrix (EXMT). In the business meeting matrix shown in FIG. 19, as shown in the element (GM5_11) and the symmetric element (GM11_5), the user (YM) with the user number 4 and the third-party outside person (Y company MR) are listed. It shows that they met for 180 minutes. When deriving the amount of communication with people outside the company, by using the same quantification scale (in this example, [minute]) as when deriving the amount of communication between internal employees, Communication between in-organization personnel and non-organization personnel can be evaluated on the same evaluation scale.

  Further, here, in order to show each component of the matrix by the communication amount, an example in which the unit is unified to the minute is shown, but the unit is not limited to the one representing the amount such as the minute. For example, there is a method of unifying by the number of communication. In a face-to-face matrix (ASMM) that represents face-to-face contact between any members in the company, the days exceeding a certain face-to-face time within the corresponding period can be counted as the days of face-to-face and the total value can be described. . And in the expansion matrix (EXMT) that represents the meeting between the members in the company and the outside meeting person, the number of days when meeting by the business trip in the corresponding period is counted and the total value is described, so that the unit is counted as a number of times. It is also possible to create a unified business meeting matrix.

<FIG. 20: Example of business meeting matrix (ASGM_2)>
FIG. 20 is an example of a business meeting matrix (ASGM_2) centered on a combination of an arbitrary member in the company and the name of a company as an external organization. The business face-to-face matrix (ASGM_2) is one of the secondary data acquired from the sensor network server (SS), and is internal face-to-face data indicating face-to-face between arbitrary members in the company, that is, face-to-face matrix (ASMM), The external meeting data indicating the meeting of the members of the company and the external organization (company), that is, the expansion matrix (EXMT) is combined.

  The expansion matrix (EXMT) is a matrix in which arbitrary members in the company and names of companies as external organizations are taken as axes. According to the outside business face-to-face tables (ASBT_1, ASBT_2) described with reference to FIG. 14, the communication amount between the in-house member and the outside face-to-face person is described in the corresponding cell in the expansion matrix (EXMT). In the business meeting matrix ASGM_2 shown in FIG. 20, as shown in the element (GM5_10) and the symmetric element (GM10_5), the user (YM) of the user number 4 and the person belonging to the second listed company (Company Y) It is shown that the total meeting time was 180 minutes.

<Figure 21: Example of network diagram created from business meeting matrix>
Up to this point, the business meeting matrix in which the amount of communication between people is represented by an N × N matrix (N: any positive integer) has been described. In order to express this information visually and in an easy-to-understand manner, a network diagram is created that connects people who have encountered each other with lines. If the created network diagram is saved in the form of an image or the like, it becomes one of the contents that can be presented to the user. Hereinafter, various display forms as a network diagram will be described with reference to FIG.

  First, FIG. 21A shows an in-house network diagram (ASNF) that represents a person-to-person meeting in the company before adding information obtained from business information. The in-house network diagram (ASNF) is included in the basic content file (ASBF).

  The in-house network diagram (ASNF) is a network diagram created on the basis of a face-to-face matrix (ASMM) showing face-to-face between arbitrary members in the company, which is one of the secondary data acquired from the sensor net server (SS). This is a visualization of physical confrontation between personnel within the organization. If the face-to-face matrix (ASMM) describes the terminal ID instead of the user name, the user name corresponding to the terminal ID is acquired from the user attribute list (ASUL), and the user name is displayed on the node representing the person. It can be described. In FIG. 21A, each circle represents a node, and a two-letter alphabet (eg, KB, KM, TN) surrounded by the circle represents the name of a person corresponding to each node.

  A business network diagram (ASGN) in which information obtained from business information is added to an in-house network (ASNF) will be described with reference to FIGS. 21 (b) to 21 (e). The business network diagram (ASGN) is also included in the basic content file (ASBF).

  Business network FIG. 1 (ASGN_11) shown in FIG. 21 (b) is based on a business meeting matrix (ASGM_1) centered on a combination of arbitrary members in the company and outside meeting persons, as exemplified in FIG. It is a business network diagram to be created. Here, an example is shown in which the shape of the node is changed and displayed in order to distinguish in-house members from outside-facing persons. That is, nodes indicated by circles represent personnel within the organization, and nodes represented by rectangles represent personnel outside the organization. A two-letter alphabet written in each node represents a person's name. When the business meeting matrix described with reference to FIG. 11 is created, business information is read in the processing procedure of the CMC 1. At this time, business information necessary for matrix creation, for example, business information, is obtained from the application server (AS). The type, target user, target period, and the like are transmitted to the business information management server (GS). The target user specified by the information transmitted to the business information management server (GS) is a member in the company described in the business meeting matrix. When creating a network diagram, in order to distinguish between in-house members and outside-facing people in the business meeting matrix (ASGM_1), the target user specified at the time of business information request may be regarded as an in-house member. Alternatively, when the attribute information that can distinguish the in-organization personnel and the non-organization personnel is included in the data, it is also possible to distinguish them by referring to them.

  The business network shown in FIG. 21 (c) 2 (ASGN_12) is divided into units of departments to which in-house members (internal personnel) belong in the business meeting matrix (ASGM_1), and one department is divided into one node. FIG. By the way, since a company organization has been described as an example of the organization so far, the above-described department can be expressed as an in-house organization belonging to the company organization. Alternatively, it can be expressed as a sub-organization. That is, the personnel within the organization belong to the sub-organization, and the sub-organizations gather to finally form one organization. At this time, taking a company organization as an example, in-house organizations and sub-organization groups can be formed in a hierarchy in correspondence with the presence of a staff member, a section, a department, a business office, and a business department. The in-house personnel, that is, the sub-organization to which each in-house employee belongs, can be derived from the user attribute list (ASUL). Hereinafter, the sub-organization will be referred to as “in-house organization”, assuming that the organization is a company. In FIG. 21C, the shape of the node is changed in order to distinguish between an in-house organization and an outside organization person, that is, an outside meeting person. That is, a node representing an in-house organization is indicated by a hexagon, and an outside meeting person is indicated by a rectangle. In addition, an example is shown in which a node of an in-house organization is displayed with its size changed according to the size of the in-house organization.

  The business network diagram 3 (ASGN_21) shown in FIG. 21 (d) is a business network diagram created from a business-facing matrix (ASGM_2) based on a combination of an arbitrary member in the company and an external organization name. is there. Here, an example is shown in which the shape of the node is changed and displayed in order to distinguish in-house members from outside organizations. That is, nodes corresponding to members in the company are indicated by circles, and nodes corresponding to external organizations are indicated by rectangles.

  Business network FIG. 4 (ASGN — 22) shown in FIG. 21 (e) is a network diagram showing the relationship between the department (internal organization) to which each of the members in the company belongs in the business meeting matrix (ASGM — 2) and the external organization. The in-house organization to which in-house members belong can be derived from the user attribute list (ASUL). Here, an example is shown in which the node shape is changed and displayed in order to distinguish between the in-house organization and the outside organization. That is, a node representing an in-house organization is indicated by a hexagon, and a node representing an outside organization is indicated by a rectangle. Further, as in FIG. 21C, an example is shown in which the nodes of the in-house organization are displayed with the size changed according to the scale of the in-house organization.

The following summarizes the display methods that make it possible to visually grasp the communication status and facilitate the understanding of the communication status.
(1) When connecting face-to-face people (between nodes) with a line, the thickness of the line is changed according to the amount of communication. In this way, not only the presence / absence of face-to-face, but also the amount of communication can be confirmed at a glance.
(2) Lines that connect face-to-face people with lines can be changed by changing the line type or color depending on the communication between personnel within the organization and communication between personnel within the organization and those outside the organization. Display. It becomes easy to see internal communication (internal meeting) and external communication (external meeting) separately.
(3) Change and display at least one of the color, pattern, and shape of the node of the personnel within the organization and the node of the personnel outside the organization. In this way, it becomes possible to distinguish between in-house members and outsiders at a glance.
(4) Change the color, pattern, and shape of the node of the non-organization personnel corresponding to different external organizations. In this way, it is possible to easily grasp not only who in which company the in-house member is connected to, but also which company.
(5) When a character string is drawn on the node of the non-organization personnel, the name of the external organization to which the non-organization personnel belong is displayed in addition to the name of the non-organization personnel. In this way, it becomes easy to know who in the company has faced who in the company.
(6) The size of the node of the sub organization (in-house organization) is changed according to the size of the organization.

  Any of the display methods described above may be used alone, or a plurality of methods may be combined. However, when combining a plurality of display methods, depending on the combination method, the display method may be complicated and difficult to grasp. For this reason, it is effective to select a display method according to what is desired to be noticed and which display effect is required.

<Figure 22: Example of external meeting list (ASPL)>
FIG. 22 is a diagram showing an example of a format of an outside meeting list (ASPL) stored in the storage unit (ASME) of the application server (AS). In the outside face-to-face person list (ASPL), the face-to-face person name (ASPL1) and the company name (ASPL2) are recorded in association with each other.
By referring to this data, the business meeting matrix (ASGM_2) shown in FIG. 20 can be created from the business meeting matrix (ASGM_1) shown in FIG. In addition to the company name (ASPL2) of the outside meeting person, the department, position, etc. can be recorded in the outside meeting person list (ASPL).

  From the business face-to-face matrix (ASGM_1), an external face-to-face partner belonging to the same company is found, and the amount of communication is added to derive the amount of communication between any member in the company and the external organization (company), as shown in FIG. A business meeting matrix (ASGM_2) can be created.

<FIG. 23: Flowchart for updating the external meeting list>
FIG. 23 shows a flowchart of external meeting list update (ASCLU) executed by the application server (AS). External meeting person list update (ASCLU) is a process performed when business information including external meeting person information is read.

  After the start (CLUS), the business information acquired from the business information management server (GS) is read (CLU1), and information related to outside meeting is extracted from the business information (CLU2). For example, when the business trip expense settlement information is read, information on the business trip destination and the name of the face-to-face partner is extracted. An external meeting list (ASPL) held in the application server (AS) is read (CLU3). Subsequently, it is determined whether or not the information on the face-to-face partner is described in the outside face-to-face person list by collating the information on the face-to-face person extracted from the business information with the outside face-to-face person list (ASPL) (CLU4). . When it is not described (CLU4: no), a line is added to the external meeting list (ASPL) and the corresponding information is input (CLU5). If the determination of CLU4 is affirmed, the processing of CLU5 is skipped. It is determined whether or not all external meeting information included in the work information acquired from the work information management server (GS) has been collated (CLU6). If the collation process is not completed (CLU6: no), Return to information extraction (CLU2). Until all the collation processes are completed, the processes of CLU3, CLU4, and CLU5 are repeated.

  If the external meeting list (ASPL) is not in the application server (AS) when reading the outside meeting list (CLU3), a new outside meeting list (ASPL) is created and extracted from the business information. The face-to-face name and company name are recorded sequentially.

  As described above, according to the business face-to-face data generation apparatus according to the first embodiment of the present invention, the physical face-to-face between the organization personnel and the non-organization personnel is extracted from various business information. Is done. For example, it is extracted who in the organization, who in which external organization, and how long the meeting has occurred. Then, external meeting data is generated by quantifying the meeting between the in-organization personnel and the non-organization personnel. On the other hand, the physical meeting between the personnel in the organization is detected by the sensor terminal (TR) that each wears, and the detection results are accumulated in the sensor network server (SS), and the meeting between the personnel in the organization is quantified. Face-to-face data is generated. The internal face-to-face data and the face-to-face face-to-face data are integrated to generate a business face-to-face matrix (ASGM_1, ASGM_2). Therefore, it is possible to quantify the face-to-face contact between personnel outside the organization who are not wearing sensor terminals (TR) and personnel within the organization, and not only within the organization but also quantifies and evaluates communication over a wider range. It becomes possible. As a result, it is possible to improve productivity by building a better cooperative relationship between the organization and the external organization.

− Second Embodiment −
A second embodiment of the present invention will be described with reference to the drawings. In the first embodiment, the business meeting matrix (ASMM) has been described as a symmetric matrix, but in the second embodiment, two types of business information are used to represent a communication sender and a receiver. A method for creating an asymmetric matrix will be described. In other words, in the face-to-face (communication) conducted between personnel inside and outside the organization, the face-to-face (visit) face-to-face is defined as “sender communication”, and the face-to-face contact is defined as “receiver communication”. Create a business-to-face matrix of matrix. This makes it easier to grasp the tendency of meeting with outsiders. The description overlapping with the description of the first embodiment is omitted.

<FIG. 24: Flowchart for creating a business meeting matrix>
FIG. 24 is a flowchart for creating a business meeting matrix. Here, an example of creating a business face-to-face matrix centering on a combination of an arbitrary member in the company and an external organization name is shown.

  After the start (CMCS), business information related to a business trip as “sender communication” and business information related to a customer as “receiver communication” are read from the business information management server (GS) (CMC11, CMC12). ). For example, CMC 11 reads business trip expense settlement information as business information, and CMC 12 reads customer application information. In each case, information related to the outside meeting is extracted (CMC21, CMC22), the amount of communication with the meeting partner is calculated (ASCCC1, ASCCC2), and an outside business meeting table (ASBT_1, ASBT_2) is created (CMC31, CMC32). Details are the same as those described with reference to FIG.

  The company name (ASBT_13) of the business trip destination described in the external business facing table 1 (ASBT_1) created from the business information related to the business trip and the visit described in the external business facing table 2 (ASBT_2) created from the business information related to the customer The company names (ASBT_23) are listed, and if there is the same company name, the company names are integrated (CMC40). Then, the number of face-to-face partners and the number of companies are counted (CMC4).

  On the other hand, a face-to-face matrix (ASMM) obtained from the sensor network server (SS) and indicating the amount of communication within an arbitrary period between arbitrary members in the company is read (CMC5). In this face-to-face matrix (ASMM), the matrix size is expanded by the number of companies counted in CMC4 (CMC6). An expanded meeting matrix is shown in FIG. The expanded parts (EXMT_1, EXMT_2) of the matrix are the two parts of the upper right area and the lower left area of the face-to-face matrix (ASMM) as a part indicating the facing of any member of the company (inside the organization) and the outside organization (outside organization) Created on. A part showing the meeting between the outside organization and the outside organization is created in the lower right area, but the meeting data between outside organizations cannot be obtained in the same unit as other meeting, so nothing is described here Or 0 is substituted. The lower left portion (EXMT_1) of the expansion matrix is an area for describing the communication amount of the sender, and the upper right portion (EXMT_2) of the expansion matrix is an area for describing the communication amount of the receiver.

  From the business trip name (ASBT_11) and the company name (ASBT_13) of the business partner in the external business meeting table 1 (ASBT_1) created from the business information related to the business trip, the corresponding cell in the lower left part (EXMT_1) of the expansion matrix A communication amount (ASBT_14) is described (CMC71). If a value has already been input to the corresponding cell, the communication amount (ASBT — 14) is added to the value. Similarly, based on the visitor name (ASBT_21) and the visitor's company name (ASBT_23) described in the external business face-to-face table 2 (ASBT_2) created from the business information related to the visitor, the upper right part (EXMT_2) of the expansion matrix The communication amount (ASBT — 24) is written in the corresponding cell (CMC72). If a value has already been input to the corresponding cell, the communication amount (ASBT — 24) is added to that value.

  Data is written in the matrix until all the data of the external business meeting table (ASBT_1, ASBT_2) is reflected in the matrix (CMC71, CMC72). When it is determined that all the data in the external business meeting table (ASBT_1, ASBT_2) is reflected (CMC81: yes, CMC82: yes), the business meeting matrix generation process is completed (CMC9). When the processing described above with reference to FIG. 24 is completed, the business meeting matrix (ASGM_PC2) illustrated in FIG. 25 is completed.

  What has been described here is an example of creating a business meeting matrix (ASGM_PC2) based on a combination of organization members and external organization names. In this regard, in-house (inside organization) members and outside (outside organization) face-to-face persons in the same manner as described with reference to the business face-to-face matrix (ASGM_1) in FIG. 19 in the first embodiment. It is also possible to create a business-facing matrix with the combination of

  That is, in order to create a business meeting matrix centered on a combination of in-organization structural members and outside meeting persons, the following processing may be performed in the flowchart shown in FIG. In the CMC 40, from the meeting partner (ASBT_15) described in the outside business meeting table 1 (ASBT_1) and the visitor name (ASBT_25) described in the outside business meeting table 2 (ASBT_2) created from the business information regarding the visitor, Processing to integrate the face-to-face partner is performed. In CMC4, the number of face-to-face opponents is counted. In CMC6, the process of expanding the face-to-face matrix is performed based on the number of face-to-face partners rather than the number of face-to-face companies. Thereafter, similarly, the communication amount is input to the corresponding cell of the matrix.

  In the flowchart of FIG. 24, a plurality of processes are shown as if they were processed in parallel for the purpose of facilitating understanding of the invention. Actually, parallel processing may be performed in this way, or serial processing may be performed.

<FIG. 25: Example of Business Meeting Matrix (ASGM_PC2)>
FIG. 25 is an example of a business meeting matrix (ASGM_PC2) in which communication amounts are stored separately for a sender and a receiver, with a combination of an arbitrary member in the company and an external organization name as an axis. The business face-to-face matrix (ASGM_PC2) is a face-to-face matrix (ASMM) indicating a face-to-face contact between arbitrary members within the company, which is one of the secondary data acquired from the sensor network server (SS), and a member within the company and an external organization The extension matrix 1 (EXMT_1) indicating the communication of the sender and the extension matrix 2 (EXMT_2) indicating the communication of the receiver between any member in the company and the outside organization.

  The expansion matrix (EXMT_1, EXMT_2) is a matrix in which an arbitrary member in the company and an outside organization are taken as axes.

  According to the outside business meeting table 1 (ASBT_1) created from the business information related to the business trip, the communication amount between the members in the company and the outside organization is recorded in the corresponding cell in the expansion matrix (EXMT_1). The element (GM5_12) indicates that the total amount of communication by the business trip face-to-face contact with the fifth user (YM) and the company Y (face-to-face visit to the company Y) is 180 minutes.

  Further, according to the external business facing table 2 (ASBT_2) created from the business information related to the customers, the communication amount between the in-house member and the external organization is described in the corresponding cell in the expansion matrix (EXMT_2). The element (GM13_3) indicates that the total amount of communication by the third user (KM) and the Y2 company corresponding to the visitor (face-to-face after receiving a visit from the Y2 company) is 120 minutes.

  FIG. 25 shows an example in which the unit is divided into minutes when each component of the matrix is represented by the communication amount. However, the unit is not limited to the one representing the amount such as minutes. For example, the number of communications may be unified.

<FIG. 26: Example of Network Diagram Created from Business Meeting Matrix>
FIG. 26 shows an example of a network diagram created from the business meeting matrix. In order to express the business meeting matrix (ASGM_PC2) visually and in an easy-to-understand manner, people and organizations are represented by nodes. A network diagram (ASGN) in which presence / absence of face-to-face is determined based on numerical values input to each element in the business face-to-face matrix (ASGM_PC2), and when corresponding face-to-face is determined, corresponding nodes are connected by a line. ) Is created. This network diagram is generated by an application server (AS). If the network diagram created here is saved as an image, it becomes one of the contents presented to the user.

  The business meeting matrix (ASGM_PC2) described with reference to FIG. 25 is a matrix centered on a combination of internal members and external organizations. It is recorded separately from the face-to-face.

  In the business network diagram 5 (ASGN_3) shown in FIG. 26 (a), if a value is input in one of the face-to-face contact by the business trip and the face-to-face visit for the in-house member and the outside organization, the line is connected as having face-to-face. It is a network diagram. As described above, in the business meeting matrix (ASGM_PC2), the meeting by the business trip is recorded in the expansion matrix 1 (EXMT_1), and the meeting by the customer is recorded in the expansion matrix 2 (EXMT_2). Therefore, if a value indicating a facing (a value other than 0) is input to any of the elements of the expansion matrix 1 (EXMT_1) and the symmetric elements of the expansion matrix 2 (EXMT2), there is no meeting due to a business trip or a visit. That is. Correspondingly, nodes corresponding to the corresponding in-house member and the corresponding outside organization are connected by lines. At this time, when changing the line width connecting the nodes according to the communication amount, the value of the element in the expansion matrix 1 (EXMT_1) and the value of the symmetric element in the expansion matrix 2 (EXMT_2) are added. The line width is determined based on the value. In the example shown in FIG. 26A, the shape of the node is changed in order to distinguish in-house members from outside organizations. Further, an example is shown in which lines connecting nodes are displayed with their line widths changed according to the amount of communication.

  In the business network diagram 6 (ASGN_PC 31) shown in FIG. 26 (b), the line segment connecting the in-house member and the external organization in the business network diagram 5 (ASGN_3) is represented by a directed line segment corresponding to the visit and the visit. Is. The value described in the expansion matrix 1 (EXMT_1) represents the amount of communication involving a business trip, and is defined as the sender's communication. Therefore, when a value indicating the meeting is recorded in the extended matrix 1 (EXMT_1), these nodes are connected by a directed line segment from the in-house member node to the outside organization node. On the other hand, the value recorded in the expansion matrix 2 (EXMT_2) represents the amount of communication after the visit, and is defined as the communication of the receiver. Therefore, when the value indicating the meeting is recorded in the expansion matrix 2 (EXMT_2), these nodes are connected by the directed line segment from the node of the outside organization to the node of the in-house member. When a value indicating facing is input to both the expansion matrix 1 (EXMT_1) and the expansion matrix 2 (EXMT_2), the nodes are connected by directed line segments facing both.

  FIG. 26B shows an example of presenting the communication amount between the in-house member and the outside organization, but it is also possible to present the communication amount between the in-house member and the outside meeting person. In this case, the name of the outside organization and the name of the outside member are described in the rectangular node shown in FIG. When presenting the amount of communication between the in-house member and the outside-faced person, a business face-to-face matrix is created around the combination of any in-house member and the outside-faced person. That is, a business meeting matrix similar to the business meeting matrix (ASGM_1) shown in FIG. 19 is created.

  The business network shown in FIG. 26C (ASGN_PC 321) is a network diagram showing an example in which the members in the company in the business meeting matrix (ASGM_PC 31) are collectively created as one node for each organization to which each member belongs. It is. Nodes are displayed in different shapes corresponding to internal and external organizations.

  Business network FIG. 8 (ASGN_PC 322) shown in FIG. 26D shows an example in which the directed line segments facing both in the business network FIG. 7 (ASGN_PC 321) are displayed separately. At this time, the threshold for determining the line width may be changed so that the amount of communication can be easily recognized. By displaying in this way, for example, while there is only a meeting with a visit from Y2 company, there is a meeting with a visit and a visit with Y company, and a meeting after a visit from Y company is also visited It is possible to visually grasp that there are more than face to face with.

  As described above, with reference to FIG. 26B to FIG. 26D, the example in which the line segment connecting the nodes is expressed by the directed line segment according to the visit and the visit has been described. It is also possible to change the line color and pattern according to the visit and the visit. For example, it is possible to set a warm color to correspond to the face-to-face meeting and a cold color to correspond to the face-to-face meeting. When changing the line pattern to distinguish between visits and visits, the line width gradually increases from the solid line to the broken line, the single line and the multiple line, the thin line and the thick line, from the internal organization personnel (internal organization) to the external organization organization (external organization) It can be a gradually decreasing line or the like.

  By using the method described in the second embodiment, it is possible to compare the face-to-face meeting and the face-to-face meeting with the same standard. Furthermore, when meeting with outsiders, it is possible to confirm the tendency of whether there are many meeting after visiting or many meeting with visiting.

  Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and various modifications can be made and the above-described embodiments can be appropriately combined. Will be understood by those skilled in the art.

TR, TR2-8 Sensor terminal GW Base station US, US2-8 User GS Business information management server NW Network PAN Personal area network SS Sensor network server AS Application server CL Client CP, CP2, CP3 Personal client

Claims (15)

A business-facing face-to-face data generation device that processes face-to-face detection results output from sensor terminals attached to each of the in-organization personnel in order to detect a physical face-to-face between personnel within the organization who are members of the organization. And
A face detection result acquisition unit for acquiring a face detection result output from each of the sensor terminals;
Based on the face-to-face detection result, an internal face-to-face data generation unit that generates internal face-to-face data that quantifies the physical face-to-face between the personnel in the organization;
A business information acquisition unit that acquires business information that is information related to the business activities of each of the personnel in the organization;
Information that can identify a physical meeting between an outside organization person who is not a member of the organization and an inside organization person is extracted from the business information, and the physical meeting between the inside organization person and the outside organization person An external face-to-face data generator that generates quantified external face-to-face data;
A business-facing face-to-face data generation apparatus comprising an integrated face-to-face data generation unit that generates integrated face-to-face data by integrating the internal face-to-face data and the face-to-face face-to-face data. In claim 1,
A business face-to-face data generation apparatus, further comprising: a content generation unit that generates content that visualizes the connection between the in-organization personnel and the non-organization personnel based on the integrated face-to-face data. In claim 2,
The business-facing face-to-face data generation apparatus, wherein the content generation unit further generates a content that visualizes the connection between the internal personnel and the external organization to which the external personnel belong. In claim 2 or 3,
A business face-to-face data generation apparatus, further comprising a display unit for displaying the content. In claim 1,
The business face-to-face data generation apparatus, wherein the internal face-to-face data and the external face-to-face data are generated with the same quantification scale. In claim 1,
The business-facing face-to-face data generation device, wherein the business information includes at least one of information related to business trips and information related to visitors. In claim 6,
The external meeting data generation unit is included in the information related to the business trip when extracting information from the business trip when extracting information that can identify the physical meeting between the external personnel and the internal personnel. Business trip time information is extracted, and when it is extracted from the information about the visitor, the information on the visit time included in the information about the visitor is extracted, and the external meeting data is generated. Data generator. In claim 1,
The business information includes information on business trips and information on visitors,
The outside meeting data generation unit is a meeting where the in-house staff visits an external organization to which the outside staff belongs, and a meeting after receiving the outside staff to the organization to which the inside staff belongs. A face-to-face data generation apparatus for business purposes, wherein the external face-to-face data is distinguished. In claim 8,
Based on the integrated face-to-face data, content that visualizes the connection between the in-organization personnel and the non-organization personnel, in a form that distinguishes between the face-to-face visit and the face-to-face visit. A business face-to-face data generation device, further comprising a content generation unit. In claim 9,
The content generation unit further visualizes the connection between the in-organization personnel and the external organization to which the non-organization personnel belong, and discriminates between the visiting meeting and the receiving meeting A business-facing face-to-face data generation apparatus characterized by generating content in form. In claim 10,
A business face-to-face data generation apparatus, further comprising a display unit for displaying the content. A sensor terminal attached to each of the personnel within the organization to detect physical encounters between personnel within the organization that are personnel belonging to the organization;
A business face-to-face data generation system comprising a computer that processes the face-to-face detection results output from the sensor terminal,
The calculator is
A face detection result acquisition unit for acquiring the face detection result output from each of the sensor terminals;
Based on the face-to-face detection result, an internal face-to-face data generation unit that generates internal face-to-face data that quantifies the physical face-to-face between the personnel in the organization;
A business information storage unit that stores business information that is information related to the business activities of each of the personnel in the organization;
A business information acquisition unit that acquires the business information from the business information storage unit;
Information that can identify a physical meeting between an outside organization person who is not a member of the organization and an inside organization person is extracted from the business information, and the physical meeting between the inside organization person and the outside organization person An external face-to-face data generator that generates quantified external face-to-face data;
A business-facing face-to-face data generation system comprising an integrated face-to-face data generation unit that generates integrated face-to-face data by integrating the internal face-to-face data and the face-to-face face-to-face data. In claim 12,
The business information includes information on business trips and information on visitors,
The outside meeting data generation unit is a meeting where the in-house staff visits an external organization to which the outside staff belongs, and a meeting after receiving the outside staff to the organization to which the inside staff belongs. A business-facing face-to-face data generation system, characterized in that said face-to-face data is distinguished. A business-facing face-to-face data generation system comprising a business information management device that manages business information that is information related to the business activities of each of the personnel within the organization that are members of the organization, and a business-to-face data generation device,
The business information management device has a business information database that collects and manages the business information input by each of the personnel in the organization,
The business face-to-face data generation device is:
A face detection result acquisition unit for acquiring a face detection result output from a sensor terminal attached to each of the persons within the organization in order to detect a physical face between the persons within the organization;
Based on the face-to-face detection result, an internal face-to-face data generation unit that generates internal face-to-face data that quantifies the physical face-to-face between the personnel in the organization;
A business information acquisition unit that acquires the business information from the business information management device;
Information that can identify a physical meeting between an outside organization person who is not a member of the organization and an inside organization person is extracted from the business information, and the physical meeting between the inside organization person and the outside organization person An external face-to-face data generator that generates quantified external face-to-face data;
A business-facing face-to-face data generation system comprising an integrated face-to-face data generation unit that generates integrated face-to-face data by integrating the internal face-to-face data and the face-to-face face-to-face data. In claim 14,
The business information includes information on business trips and information on visitors,
The outside meeting data generation unit is a meeting where the in-house staff visits an external organization to which the outside staff belongs, and a meeting after receiving the outside staff to the organization to which the inside staff belongs. A business-facing face-to-face data generation system, characterized in that said face-to-face data is distinguished.