INFORMATION PROVIDING SYSTEM, SERVER DEVICE AND INFORMATION PROVIDING METHOD

The information providing system includes a mobile terminal and a server device that communicates with the mobile terminal. The mobile terminal includes: a sensor that reads a facility ID used to identify at least one facility; and a communication device that transmits, to the server device, the facility ID read by the sensor and a user ID used to identify a user of the mobile terminal. The server device includes: a memory that stores a plurality of types of facility-related information; a processor that extracts, from the plurality of types of facility-related information stored in the memory, facility-related information corresponding to the facility ID and the user ID transmitted from the mobile terminal; and a communication device that transmits, to the mobile terminal, the facility-related information extracted by the processor. The mobile terminal includes a display on which the facility-related information transmitted from the server device is displayed.

TECHNICAL FIELD

This disclosure relates to an information providing system, a server device, an information providing method, and an information providing program.

BACKGROUND ART

Japanese Patent Laying-Open No 2004-234229 (PTL 1) discloses a facility monitoring system in which facility-related information is stored in a server device and transmitted by and from the server device to a user's mobile terminal in response to the user's request.

CITATION LIST

Patent Literature

SUMMARY OF INVENTION

An information providing system according to this disclosure is for use in providing facility-related information of at least one facility. The information providing system includes a mobile terminal and a server device that communicates with the mobile terminal. The mobile terminal includes: a sensor that reads first identification information used to identify at least one facility; and a terminal communication device that transmits, to the server device, the first identification information read by the sensor and second identification information used to identify a user of the mobile terminal. The server device includes: a memory that stores a plurality of types of facility-related information correspondingly to at least one facility; a processor that extracts, from the plurality of types of facility-related information stored in the memory, facility-related information corresponding to the first identification information and the second identification information transmitted from the mobile terminal; and a server communication device that transmits, to the mobile terminal, the facility-related information extracted by the processor. The mobile terminal includes a display on which the facility-related information transmitted from the server device is displayed.

A server device according to this disclosure is for use in providing facility-related information of at least one facility. The server device includes: a memory that stores a plurality of types of facility-related information correspondingly to at least one facility; a processor that extracts, from the plurality of types of facility-related information stored in the memory, facility-related information corresponding to first identification information read by a mobile terminal and used to identify at least one facility and second identification information used to identify a user of the mobile terminal, and a server communication device that transmits, to the mobile terminal, the facility-related information extracted by the processor.

An information providing method according to this disclosure is for use in providing facility-related information of at least one facility. The information providing method includes: extracting, from a plurality of types of facility-related information stored in a memory correspondingly to at least one facility, facility-related information corresponding to first identification information read by a mobile terminal and used to identify at least one facility and second identification information used to identify a user of the mobile terminal; and transmitting, to the mobile terminal, the facility-related information extracted earlier.

An information providing program according to this disclosure is for use in providing facility-related information of at least one facility. The information providing program prompts a computer to functionally operate as: a storage that stores a plurality of types of facility-related information correspondingly to at least one facility; a computing unit that extracts, from the plurality of types of facility-related information stored in the storage, facility-related information corresponding to first identification information read by a mobile terminal and used to identify at least one facility and second identification information used to identify a user of the mobile terminal; and a server communication unit that transmits, to the mobile terminal, the facility-related information extracted by the computing unit.

DETAILED DESCRIPTION

Problem to be Solved by the Present Disclosure

In the facility monitoring system described in PTL 1, the server device is allowed to provide a user with facility-related information. This facility monitoring system, however, fails to address how users and facility-related information are associated with each other, thus inviting the server device to provide users with facility-related information irrelevant to them.

This disclosure is directed to providing an information providing system, a server device, an information providing method, and an information providing program that allows users to access and receive facility-related information suited to the users.

Advantageous Effect of the Present Disclosure

This disclosure may successfully provide an information providing system, a server device, an information providing method, and an information providing program that allows users to access and receive facility-related information suited to the users.

Description of Embodiments

(1) An information providing system1according to this disclosure is for use in providing facility-related information of at least one facility4. Information providing system1includes a mobile terminal5and a server device3that communicates with mobile terminal5. Mobile terminal5includes: a sensor56that reads a facility ID used to identify at least one facility4; and a communication device52that transmits, to server device3, the facility ID read by sensor56and a user ID used to identify a user of mobile terminal5. Server device3includes: a memory33that stores a plurality of types of facility-related information correspondingly to at least one facility4; a processor31that extracts, from the plurality of types of facility-related information stored in memory33, facility-related information corresponding to the user ID and the facility ID transmitted from mobile terminal5; and a communication device32that transmits, to mobile terminal5, the facility-related information extracted by processor31. Mobile terminal5includes a display54on which the facility-related information transmitted from server device3is displayed.

(2) In information providing system1as defined in 1), memory33may store a table333for identification purpose (user management table). In identification table333are defined authorities to access the plurality of types of facility-related information depending on types of the users. Processor31may extract, from the plurality of types of facility-related information stored in memory33, particular facility-related information defined as accessible in table333for identification purpose (user management table) based on the user ID.

(3) Information providing system1as defined in 1) or 2) may include a plurality of facilities4as at least one facility4. Memory33may store the plurality of types of facility-related information correspondingly to respective ones of these facilities4. Processor31may extract, from the plurality of types of facility-related information stored in memory33, facility-related information corresponding to facility4identified based on the facility ID.

(4) Information providing system1as defined in 1) or 2) may include a plurality of facilities4as at least one facility4. Memory33may store the plurality of types of facility-related information correspondingly to respective ones of these facilities4. Processor31may extract, from the plurality of types of facility-related information stored in memory33, facility-related information corresponding to another facility4that differs from facility4identified based on the facility ID.

(5) In information providing system1as defined in one of 1) to 4), the plurality of types of facility-related information may include an analysis result of at least one facility4.

(6) In information providing system1as defined in one of 1) to 5), the first identification information may be included in a code10attached to at least one facility4.

(7) A server device3according to this disclosure provides facility-related information of at least one facility4. Server device3includes, a memory33that stores a plurality of types of facility-related information correspondingly to at least one facility4, a processor31that extracts, from the plurality of types of facility-related information stored in memory33, facility-related information corresponding to a facility ID read by a mobile terminal5and used to identify at least one facility4and a user ID used to identify a user of mobile terminal5; and a communication device32that transmits, to mobile terminal5, the facility-related information extracted by processor31.

(8) An information providing method according to this disclosure is for use in providing facility-related information of at least one facility4. The information providing method includes: (S36) extracting, from a plurality of types of facility-related information stored in memory33correspondingly to at least one facility4, facility-related information corresponding to a facility ID read by mobile terminal5and used to identify at least one facility4and the user ID used to identify a user of mobile terminal5; and (S37) transmitting, to mobile terminal5, the facility-related information extracted earlier.

(9) An information providing program332aaccording to this disclosure is for use in providing facility-related information of at least one facility4. Information providing program332aprompts server device3to operate as; a storage330that stores a plurality of types of facility-related information correspondingly to at least one facility4; a computing unit310that extracts, from the plurality of types of facility-related information stored in storage330, facility-related information corresponding to a facility ID read by a mobile terminal5and used to identify at least one facility4and a user ID used to identify a user of mobile terminal5; and a communication unit320that transmits, to mobile terminal5, the facility-related information extracted by computing unit310.

Description of Embodiments

Embodiments according to this disclosure are hereinafter described in detail referring to the accompanying drawings. The same or similar components and units in the description below are simply illustrated with the same reference signs, redundant description of which will basically be omitted.

<Configuration of Information Providing System>

The configuration of an information providing system1according to an embodiment is hereinafter described with reference toFIGS.1to4.

FIG.1is a drawing that illustrates an exemplified configuration of information providing system1according to this embodiment. As illustrated inFIG.1, information providing system1includes at least one facility4and a mobile terminal5. In this embodiment, information providing system1includes, as at least one facility4, a plurality of facilities4installed in a plurality of factories. Of these facilities4, facilities A1 and A2 are installed in a factory A, while facilities B1 and B2 are installed in a factory B. Information providing system1may include one facility4alone, instead of two or more facilities4.

Facility4is engaged in the manufacture of, for example, automobile parts and circuit boards and is equipped with machines, tools, and apparatuses used to assemble the parts and circuits into finished products. Examples of facility4may include electrical facility, gas facility, plumbing installation, conveyance equipment, air conditioning equipment, and lighting facility.

First identification information is allocated to each of facilities4. The first identification information is used to identify each facility4and may include letters and characters, symbols, numbers and/or codes. An example of the first identification information used in this embodiment is facility ID (identifier), for example, production serial number of facility4, as illustrated inFIG.11described later. The facility ID is included in a code10attached to each facility4. Examples of code10include one-dimensional codes like barcodes and two-dimensional codes like QR codes (registered trademark). Different facility MDs are respectively allocated to facilities4, and facilities4are thus discriminable by server device3based on their facility IDs.

Mobile terminal5, examples of which may include smart phone, PDA (personal digital assistant) and tablet PC (personal computer), is an information terminal allowed to communicate with server device3. Mobile terminal5is allowed to read the facility ID allocated to each facility4using a sensor56described later.

Mobile terminal5is carried with and used by a user. Though not illustrated in the drawings, there are a plurality of users in each of factories A and B. These users are, for example, chief supervisors, team leaders, and workers and operators, who are allowed to use facilities4installed in the factories.

Second identification information is allocated to each of the users. The second identification information is used to identify each user and may include letters and characters, symbols, numbers and/or codes. An example of the second identification information used in this embodiment is user ID set by a user him/herself, as illustrated inFIG.12described later.

Server device3disclosed herein is a computer that provides users with facility-related information of at least one facility4. The facility-related information is information of facility4, for example, information of operation and work items of facility4(hereinafter, may be referred to as “work items”), information of any gas generated in facility4, properties of products manufactured using facility4(parts and components, finished products), defect-related information of products manufactured using facility4, information of a facility4-installed production line, and/or information of sensors installed in facility4.

In this embodiment, server device3is installed in a different site apart from factories A and B where facilities4are installed. Server device3communicates with facility4in each factory through a network2. Server device3communicates with mobile terminal5carried with each user through network2. Server device3may be installed in one of factories A and B or may functionally operate as a cloud computer and thereby communicate with facility4and mobile terminal5in each factory.

FIG.2is a drawing that illustrates a process to provide facility-related information using information providing system1according to this embodiment. As illustrated inFIG.2, facility4transmits facility-related information of facility4to server device3. The timing of transmission of the facility-related information by facility4may be optionally decided and set by an administrator of facility4, for example, after the manufacture of products for a certain number of lots is completed in facility4. Server device3obtains the facility-related information transmitted from facilities4in the factories and stores the obtained facility-related information successively in memory33described later.

Server device3collects various pieces of facility-related information from facilities4in the factories and provides the collected facility-related information to a user who is requesting information using mobile terminal5. If server device3equally provides all of users, without checking their identities, all types of facility-related information requested, the users may receive totally irrelevant facility-related information from server device3.

To address this issue, information providing system1according to this embodiment is configured to provide a user, who has been identified by server device3based on his/her user ID, with a piece(s) of facility-related information relevant to this user.

Specifically, a user inputs, to mobile terminal5, his/her user ID and password registered beforehand in server device3. Mobile terminal5transmits the inputted user ID and password to server device3. Based on the user ID obtained from mobile terminal5, server device3identifies the user registered for this user ID and authorizes mobile terminal5to access server device3if the password is valid.

After the user is authenticated by server device3, the user, using his/her mobile terminal5, detects code10attached to facility4and reads the facility ID included in code10. Mobile terminal5transmits the read facility ID to server device3. Server device3, based on the facility ID transmitted from mobile terminal5, identifies facility4with this facility ID.

When a request to access the facility-related information is received from the authenticated user, server device3extracts the requested facility-related information. Server device3extracts a piece(s) of facility-related information relevant to the authenticated user from a plurality of types of facility-related information stored in memory33. For instance, server device3extracts both of first facility-related information and second facility-related information in response to a request from a certain user, while extracting, of these types of information, the first facility-related information alone in response to a request from another user.

Server device3transmits the extracted facility-related information to the user's mobile terminal5. Mobile terminal5presents, on display54, the facility-related information transmitted from server device3. Server device3provides each of different types of users with a particular piece(s) of facility-related information suited to the user.

FIG.3is a block diagram that illustrates a hardware configuration of information providing system1according to this embodiment. As illustrated inFIG.3, server device3is equipped with a processor31, a communication device32, a memory33, and a medium reading device34.

Processor31is a processing device in charge of running a program(s) (for example, control program332described later) to carry out processes related to server device3. Processor31may include, for example, at least one of CPI. (central processing unit), FPGA (field programmable gate array) and GPU (graphics processing unit). Processor31may include a processing circuitry.

Communication device32builds communication with facility4and mobile terminal5through network2to allow data (information) to be transmitted and received to and from facility4and mobile terminal5.

Facility-related information331(hereinafter, may be simply referred to as “facility-related information”) includes pieces of information of facilities4which are obtained from facilities4in the factories. Control program332is a program for control of components and units in server device3, inclusive of an information providing program332a. Information providing program332ais a program run to provide a user with facility-related information suited to the user in response to his/her request transmitted from mobile terminal5. Processor31runs information providing program332ato carry out the processing steps ofFIG.15described later. Identification tables333include a facility management table ofFIG.11containing information used to identify facilities4based on the facility IDs, and a user management table ofFIG.12containing information used to identify users based on the user IDs. These management tables will be described later.

Medium reading device34receives a recording medium35in which programs and data are recordable and reads the programs and data from recording medium35. Examples of recording medium35may include CD (compact disk), SD card (secure digital card) and USB memory (universal serial bus memory). In this embodiment, medium reading device34reads control program332(information providing program332a) stored in recording medium35and stores the read control program332(information providing program332a) in memory33.

Facility4is equipped with a processor41, a communication device42, a memory43, a display44, an input interface45, and a driver device46.

Processor41is a processing device in charge of running programs (for example, control program432described later) to carry out processes related to facility4. Processor41includes at least one of, for example, CPU, FPGA and GPU. Processor41may include a processing circuitry.

Communication device42builds communication with server device3through network2to allow data (information) to be transmitted and received to and from server device3.

Memory43includes a volatile memory, for example, DRAM and/or SRAM or may include a non-volatile memory, for example, ROM, SSD and/or HDD. Memory43stores a facility ID431, a control program432and a drive data433.

Facility ID431(hereinafter, may be simply referred to as “facility ID”) is an example of the first identification information, which is used to identify facility4. Control program432is a program for control of the components and units of facility4. Drive data433includes various pieces of data used to operate driver device46.

Input interface45is an interface through which data inputs concerning the operation and management of facility4are receivable. For instance, a user, who is an operator or worker, is allowed to input data through input interface45to check the condition of facility4.

Driver device46drives an actuator used in the manufacture of products, not illustrated in the drawings, based on the control by processor41.

Mobile terminal5is equipped with a processor51, a communication device52, a memory53, a display54, an input interface55, and a sensor56.

Processor51is a processing device in charge of running programs (for example, control program532described later) to carry out processes related to mobile terminal5. Processor51may include, for example, at least one of CPU, FPGA and GPU. Processor51may otherwise include a processing circuitry.

Communication device52builds communication with server device3through network2to allow data (information) to be transmitted and received to and from server device3.

Memory53includes a volatile memory, for example, DRAM and/or SRAM or may include a non-volatile memory, for example, ROM, SSD and/or HDD. Memory53stores a terminal ID531and a control program532.

Terminal ID531is information used to identify mobile terminal5and includes the product serial number or IP address (Internet protocol address) of mobile terminal5. The first identification information, which is the user ID in this embodiment, may instead be terminal ID531. Control program532is a program for control of components and units of mobile terminal5.

Input interface55is an interface through which data inputs to mobile terminal5are receivable. For example, the user of mobile terminal5is allowed input his/her user ID and password through input interface55.

Sensor56detects code10attached to facility4and thereby reads facility ID431included in this code10. For example, code10may be a barcode or QR code (registered trademark), in which case sensor56may be a camera-equipped image sensor.

FIG.4is a block diagram that illustrates a functional configuration of information providing system1according to the embodiment. As illustrated inFIG.4, principal functional elements of server device3include a computing unit310, a communication unit320, a storage330, and a medium reader340.

Computing unit310is a functional element of processor31, which executes various processes related to server device3.

Communication unit320is a functional element of communication device32, which allows data (information) to be transmitted and received to and from facility4and mobile terminal5through network2.

Storage330is a functional element of memory33. Storage330stores various types of information, inclusive of facility-related information obtained from respective facilities4in the factories and information used to identify facilities4and users.

Medium reader340is a functional element of medium reading device34. Medium reader340reads the programs and data stored in recording medium35and stores the read programs and data in storage330.

Principal functional elements of facility4include a computing unit410, a communication unit420, a storage430, a display unit440, an input unit450, and a driver unit460.

Computing unit410is a functional element of processor41, which executes various processes related to facility4.

Communication unit420is a functional element of communication device42, which allows data (information) to be transmitted and received to and from server device3through network2.

Storage430is a functional element of memory43, and stores various types of information concerning facility4, for example, facility ID431.

Display unit440is a functional element of display44, which displays thereon images to broadcast various pieces of information.

Input unit450is a functional element of input interface45, which receives data inputs concerning the operation and management of facility4.

Driver unit460is a functional element of driver device46, which drives an actuator for the manufacture of products, not illustrated in the drawings.

Principal functional elements of mobile terminal5include a computing unit510, a communication unit520, a storage530, a display unit540, an input unit550, and a reader560.

Computing unit510is a functional element of processor51, which is in charge of executing various processes related to mobile terminal5.

Communication unit520is a functional element of communication device52, which allows data (information) to be transmitted and received to and from server device3through network2.

Storage530is a functional element of memory53, and stores various types of information concerning mobile terminal5, for example, terminal ID531.

Display unit540is a functional element of display54, which displays thereon images to broadcast various pieces of information.

Input unit550is a functional element of input interface55, which receives data inputs to mobile terminal5.

Reader560is a functional element of sensor56, which detects code10attached to facility4and thereby reads facility ID431included in this code10.

Facility-related information331stored in memory33by server device3is hereinafter described, with reference toFIGS.5to10.FIG.5is a work management table included in facility-related information331stored in server device3according to this embodiment. In the work management table, information is stored indicating whether work items are completed in each of facilities4of in the factories (may be referred to as “work management information), as illustrated inFIG.5.

The work items stored in the work management table include results on, for example, whether the following work items are completed; roller rotation number in facility4, presence/absence of cracking in facility4, and air pressure in facility4. In the work management table, information of “I” is stored when the completion of each work item is confirmed, while information of “0” is stored otherwise. The results on whether the work items are completed may be inputted to facility4by a user or may be automatically stored in facility4depending on whether each work item is done. The results may be inputted by a user to a computer not illustrated in the drawings and then into facility4. Server device3obtains these results on whether the work items are completed from each of facilities4in the factories and stores the obtained results in the work management table.

An example is given in regard to a facility A1 of a factory A, in which roller rotation number, presence/absence of cracking, and air pressure were checked at 8:00, and presence/absence of cracking and air pressure were checked at 20:00. This example is applied likewise to a facility A2 of factory A and facilities B1 and B2 of a factory B. In the work management table, information of “1” is stored when the completion of each work item is confirmed, while information of “0” is stored otherwise.

Through management of the work items, whether they are completed, in each of facilities4in the factories using the work management table, server device3, in response to a user's request, is thus allowed to provide the user with information on whether any work or operation is done for facility4of his/her interest.

FIG.6is a gas management table included in facility-related information331stored in server device3according to this embodiment. In the gas management table, information is stored indicating daily gas consumption and total gas consumption in each of facilities4in the factories (may be referred to as “gas management information”), as illustrated inFIG.6.

The gas management table contains, as types of gases to be used, information indicating the quantities of oxygen and chlorine used. Oxygen and chlorine are just examples, which may be replaced with be any other gases. Server device3obtains the gas consumption per day from each of facilities4in the factories and stores the obtained result in the gas management table. Further, server device3sums the obtained gas consumptions and then stores information indicating its result in the gas management table.

Through management of daily gas consumption in each of facilities4in the factories using the gas management table, server device3, in response to a user's request, is thus allowed to provide the user with the gas consumption in facility4of his/her interest on a requested date.

FIG.7is a property management table included in facility-related information331stored in server device3according to this embodiment. In the property management table, information is stored indicating the values of property α in each processing step for a plurality of products processed in each of facilities4in the factories (may be referred to as “property management information), as illustrated inFIG.7. Property α indicates a property of each product processed in facility4, examples of which include voltage, electric current, spring's strength, and thermal radiation rate. Server device3obtains the value of property α of each product in each processing step from each of facilities4in the factories and stores the obtained values in the property management table.

In regard to a product 1 processed in a facility A1 of a factory A, for example, “α1” is stored in the property management table as property α measured in a processing step A, and “α1.” is stored in the property management table as property α measured in a processing step B. In the property management table are stored likewise information indicating the values of property α of the following products measured in each processing step, a product 2 processed in facility A1, products 3 and 4 processed in a facility A2 of factory A, and a product processed in facility4of factory B.

FIG.8is a graph of property α analysis result included in facility-related information331stored in server device3according to this embodiment. Server device3analyzes the values of property α in each processing step that are stored in the work management table and then stores the result of this analysis in memory33as facility-related information331. The property α analysis result is included in the property management information.

FIG.8is a scatter diagram presented by server device3, showing a property α analysis result of products processed in facility A1 in the following steps; processing step A and processing step B that follows processing step A. In the scatter diagram ofFIG.8, its vertical axis represents the values of property α in processing step A, and its horizontal axis represents the values of property σ in processing step B. This example ofFIG.8demonstrates that the values of property α are greater in processing step B than in processing step A.

As described thus far, server device3, by thus presenting the scatter diagram of the property α values of products for each processing step, is allowed to provide a user with changes of the property α values in any desired facility4between processing steps of the user's interest whenever requested by the user.

FIG.9is a defect management table included in facility-related information331stored in server device3according to this embodiment. In the defect management table, information is stored indicating the count of defects, cumulative count of defects and cumulative ratio for each of different types of defects in each of facilities4in the factories (hereinafter, may be referred to as “defect management information”), as illustrated inFIG.9.

The defects storable in the defect management table include, cracking, chipping, heat control error, elasticity control error, and any other defects to be addressed. Server device3obtains the counted number of the defects for each defect type from each of facilities4in the factories and stores the obtained results in the defect management table. Further, server device3sums the counted numbers of defects, calculates the cumulative ratio for each defect type, and stores information of this result in the defect management table.

FIG.10is a graph of a defect-related analysis result included in facility-related information331stored in server device3according to this embodiment. Server device3analyzes the counts of the defects stored in the defect management table per defect processing step and stores the obtained results in memory33as facility-related information331. The defect analysis result is included in the defect management information.

For instance, server device3presents, as illustrated inFIG.10, a Pareto chart of the count of defects per processing step, cumulative count of defects, and cumulative ratio of defects for each of facilities4. In the Pareto chart ofFIG.10, its vertical axis on the left represents the cumulative ratio, its horizontal axis represents the defect types, and its vertical axis on the right represents the cumulative count of defects.

Server device3, by thus presenting the Pareto chart of the count of defects, cumulative count result, and cumulative ratio for different defect types in the drawing in each facility4, is allowed to successfully provide, to a user, the count of defects, cumulative count result, and cumulative ratio for different defect types in any desired facility4whenever requested by the user.

<Exemplified Tables for Identification Purpose>

Next, identification tables333, which are stored in memory33by server device3, are hereinafter described with reference toFIGS.1and12.FIG.11is a drawing that illustrates a facility management table included in identification tables333stored in server device3according to this embodiment. The facility IDs are each allocated to respective ones of facilities4in the factories, and pieces of information of facilities4with these facility IDs are storable in the facility management table, as illustrated inFIG.11.

For example, information of facility A1 in factory A is stored in the facility management table as information of facility4with facility ID “AAA1”. In regard to the other facilities4in factories A and B, information of the facility IDs and facilities4with the facility IDs are stored likewise in the facility management table.

Server device3, by consulting the facility management table, is allowed to identify facility4with facility ID obtained from mobile terminal5.

FIG.12is a drawing that illustrates a user management table included in identification tables333stored in server device3according to this embodiment. User IDs are allocated to users, and pieces of information of the users with the user IDs are storable in the user management table, as illustrated inFIG.12.

In the user management table, user names, passwords, and job titles that are registered in advance in server device3by users themselves are stored as user-related information. In the user management table, access authorities for the facility-related information are defined depending on different types of users. The user management table is an example of the “access authority table” as claimed herein. Server device3extracts, from the plurality of types of facility-related information stored in memory33, a particular piece(s) of facility-related information defined as accessible in the user management table based on the user ID. To be specific, server device3defines and sets the levels of access control in the user management table according to the job titles of registered users. The level of access control refers to whether the facility-related information is offered to a user (whether his/her access is allowed) depending on the degrees of importance and confidentiality of facility-related information. In the user management table, information of “1” is stored for user-accessible facility-related information, while information of “0” is stored for user-inaccessible facility-related information. The levels of access control include “low” indicating a user most likely to be granted an access to the facility-related information, “high” indicating a user most unlikely to be granted an access to the facility-related information, and “medium” indicating a user between the high and low levels.

For a user; chief supervisor, who is subject to the low level of access control, server device3is allowed to provide this user with the work management information ofFIG.5, gas management information ofFIG.6, property management information ofFIGS.7and8, and defect management information ofFIGS.9and10. A chief supervisor, who is responsible for knowing details and specifics of facility4in the factory, including defect rates, may be a user allowed to extensively access substantially all types of facility-related information.

For a user; team leader, who is subject to the medium level of access control, server device3is allowed to provide this user with the work management information ofFIG.5, gas management information ofFIG.6and property management information ofFIGS.7and8, while prohibiting this user from accessing the defect management information ofFIGS.9and10. A team leader, who may be not as knowledgeable as a chief supervisor, still needs to have a certain amount of knowledge of facility4in the factory. The team leader, therefore, may be a user allowed to access certain pieces of facility-related information including the properties of facility4.

For a user; worker, who is subject to the high level of access control, server device3is allowed to provide this user with the work management information ofFIG.5, while prohibiting this user from accessing the gas management information ofFIG.6, property management information ofFIGS.7and8, and defect management information ofFIGS.9and10. A worker, who only needs to grasp work-related matters of facility4in the factory, may be a user only allowed to access the facility-related information of work items alone due to confidentiality required of the defect rates and properties of facility4.

An example of server device3providing a user with the facility-related information is hereinafter described with reference toFIGS.13and14.FIG.13is a drawing that illustrates indication changes130on display54of mobile terminal5according to this embodiment.

An application program (may be hereinafter referred to as “app”) has been downloaded into and installed in a user's mobile terminal5. This application program allows the user to access and view the facility-related information stored in server device3. When the user activates the app on mobile terminal5, a login screen is presented on display54, as illustrated inFIG.13(A). The login screen includes an entry field for user ID input, and an entry field for password input. When the user inputs his/her user ID and password, mobile terminal5transmits the user ID and password to server device3.

When server device3authenticates the user based on the received user ID and password, a menu screen is presented on display54, as illustrated inFIG.13(B). The menu screen includes an icon used to read code10and an icon for input of settings.

When the user clicks icon for reading code10, a code-reader screen is presented on display54to read code10, as illustrated inFIG.13(C).

When the user focuses the frame of this code-reader screen on code10attached to facility4, sensor56detects this code10. When code10is detected, an indication of URL (uniform resource locator) is presented on display54to allow the user to access server device3, as illustrated inFIG.13(D).

When the user clicks the indication of URL to access and view the facility-related information of any target facility4, an icon is presented on display54on which the target facility4is selectable, as illustrated inFIG.13(E). When, for example, the user reads code10attached to facility A1 using his/her mobile terminal5, an icon is displayed on display54on which one of facility A1 with read code10and facility4that differs from facility A1 is selectable. Thus, the user is allowed to access and view the facility-related information of a different facility4, as well as the facility-related information of facility A1 with read code10.

When the user selects facility A1, display54presents icons for types of facility-related information that may be accessible by the user depending on his/her level of access control, as illustrated inFIG.13(F). For a user A who is subject to the low level of access control, for example, display54presents an icon for selecting the work management information ofFIG.5, an icon for selecting the gas management information ofFIG.6, an icon for selecting the property management information ofFIGS.7and8, and an icon for selecting the defect management information ofFIGS.9and10. This user who is subject to the low level of access control is allowed to access and view four different types of facility-related information; work management information, gas management information, property management information, and defect management information.

When the user clicks one of these icons to select a desired piece of facility-related information, the selected piece of facility-related information is presented on display54, as illustrated inFIG.13(G). When the user selects the defect management information, for example, the analysis result ofFIG.10, for example, may be presented on display54. Thus, any user who is subject to the “high” level of access control is allowed to select, access and view any desired one(s) of the four different types of facility-related information.

FIG.14is a drawing that illustrates indication changes140on display54of mobile terminal5according to this embodiment. As withFIG.13(E), when a user, who wants to view the facility-related information, clicks the URL-indicating image, icons are presented on display54on which target facility4of the user's interest is selectable, as illustrated inFIG.14(E).

When the user selects facility A1, an image in one ofFIGS.13(F),14(F1) and14(F2) is presented on display54depending on the user's level of access control.

For a user B who is subject to the medium level of access control, for example, display54presents the icon for selecting the work management information, icon for selecting the gas management information, and icon for selecting the property management information. The icon for selecting the defect management information alone is not presented on display54. The user who is subject to the medium level of access control is allowed to access and view three different types of facility-related information; work management information, gas management information and property management information.

When the user clicks one of these icons to select a desired piece of facility-related information, the selected piece of facility-related information is presented on display54, as illustrated inFIG.14(G1). When the user selects the property management information, for example, the analysis result ofFIG.8, for example, may be presented on display54. Thus, any user who is subject to the “medium” level of access control is allowed to select, access and view any desired one(s) of these three different types of facility-related information.

For a user B who is subject to the high level of access control, for example, display54presents one icon alone for selecting the work management information. Display54does not present the icon for selecting the gas management information, icon for selecting the property management information, or icon for selecting the defect management information. Thus, any user who is subject to the high level of access control is only allowed to access and view the work management information alone.

When the user clicks the icon for selecting the work management information, the work management information ofFIG.5may be presented on display54, as illustrated inFIG.14(G2). Thus, any user who is subject to the “high” level of access control is allowed to select, access and view only a certain type of selectable facility-related information alone.

<Processing Steps of Information Providing System>

Steps of a process carried out in information providing system1are hereinafter described with reference toFIG.15.FIG.15is a flow chart that illustrates processing steps carried out in information providing system1according to this embodiment. The processing steps illustrated inFIG.15(hereinafter, may be abbreviated to “S”) are feasible by having the following processors run the respective control programs; processor51(computing unit410) of mobile terminal5runs control program432, and processor31(computing unit310) of server device3runs control program332(information providing program332a).

As illustrated inFIG.15, mobile terminal5determines, after the app is activated, whether a user's user ID and password have been inputted on the login screen illustrated inFIG.13(A) (S51). In case the input of the user ID and password is yet to be done (NO in S51), mobile terminal5repeats the processing step of S51. When the input of the user ID and password is confirmed (YES in S51), mobile terminal5transmits the user ID and password to server device3(S52).

Server device3determines, based on the user ID and password transmitted from mobile terminal5, whether user authentication has been successful (S31). In this processing step, server device3determines whether the user ID and password transmitted from mobile terminal5are included in user IDs and passwords of a plurality of users registered in the user management table ofFIG.12.

In case the user ID and password transmitted from mobile terminal5are not found in the user IDs and passwords of a plurality of users registered in the user management table, server device3skips the user authentication (NO in S31) and then transmits login-reject information to mobile terminal5(S32) and ends this process.

When the user ID and password transmitted from mobile terminal5are found in the user IDs and passwords of a plurality of users registered in the user management table, server device3authenticates (YES in S31) and then identifies (S33) this user. Then, server device3transmits login-approve information to mobile terminal5(S34).

Mobile terminal5determines whether the login is authorized by server device3based on the login-reject information or login-approve information transmitted from server device3(S53).

In case the login is not approved by server device3(NO in S53), mobile terminal5rejects the login (S54) and ends this process.

When the login is approved by server device3(YES in S53), mobile terminal5authorizes the login (S55). In this instance, a menu screen is presented on display54of mobile terminal5, as illustrated inFIG.13(13).

When the user clicks the code10-reader icon on the menu screen, mobile terminal5determines whether code10has been read by sensor56(S56). In case code10fails to be read (NO in S56), mobile terminal5repeats the processing step of S56. When code10is successfully read (YES in S56), mobile terminal5transmits the facility ID included in the read code10to server device3(S57).

Server device3, by consulting the facility management table ofFIG.13, identifies facility4corresponding to facility ID with the facility ID transmitted from mobile terminal5(S35). Then, server device3extracts, from a plurality of types of facility-related information stored in memory33, a piece(s) of facility-related information relevant to the user ID and facility ID transmitted from mobile terminal5(S36).

For example, server device3, based on the level of access control of the user identified in S33and facility4identified in S35, extracts the facility-related information of the identified facility4. When the user's level of access control is found to be low, server device3extracts the work management information, gas management information, property management information, and defect management information. When the user's level of access control is found to be medium, server device3extracts the work management information, gas management information, and property management information, while leaving the defect management information unextracted. When the user's level of access control is found to be high, server device3does not extract the gas management information, property management information or defect management information but extracts the work management information alone. The extracted facility-related information is the information of facility4whose code10was read by the user. Server device3transmits the extracted facility-related information to mobile terminal5(S37).

When facility4whose code10was read is selected by the user, as illustrated inFIG.13(F), mobile terminal5presents, on display54, the facility-related information extracted by server device3(S58) and then ends this process. In the processing step of S58described earlier, facility4, code10of which was reads is selected by the user. In case the user selects a different facility4in a different factory, a piece(s) of facility-related information allowed for the user's level of access control alone is presented on display54of mobile terminal5, among all of pieces of facility-related information of the selected facility4.

In information providing system1, a piece(s) of facility-related information corresponding to the user ID and the facility ID read by sensor56of mobile terminal5is extracted from a plurality of types of facility-related information stored in memory33of server device3, and the extracted piece(s) of facility-related information is presented on display54of mobile terminal5. Thus, server device3, depending on users' different levels of access control, provides each user with a piece(s) of facility-related information suited to the user

In information providing system1, server device3extracts, from a plurality of types of facility-related information concerning facilities4stored in memory33, a piece(s) of facility-related information corresponding to the user ID used to identify a user of the mobile terminal and facility ID read by sensor56of mobile terminal5, and mobile terminal5presents the extracted piece(s) of facility-related information on display54. Information providing system1thus characterized may successfully provide a user with facility-related information suited to the user in view of the degrees of importance and confidentiality of various pieces of facility-related information.

In information providing system1characterized as described thus far, server device3, as illustrated inFIG.12, defined and sets a plurality of different levels of access control for different types of users and extracts a piece(s) of facility-related information corresponding to each user's level of access control from a plurality of types of facility-related information stored in memory33. For a user; chief supervisor, who is subject to the low level of access control, server device3extracts the work management information, gas management information, property management information, and defect management information and provides the user with these pieces of extracted information. For a user; team leader, who is subject to the medium level of access control, server device3extracts the work management information, gas management information and property management information and provides the user with these pieces of extracted information, while prohibiting this user from accessing the defect management information. For a user, worker, who is subject to the high level of access control, server device3extracts the work management information and provides the user with this extracted information, while prohibiting this user from accessing the gas management information, property management information, and defect management information. Thus, information providing system1, depending on different types of users, may successfully provide each user with a piece(s) of facility-related information suited to the user.

In information providing system1characterized as described thus far, server device3stores, in memory33, the facility-related information of each of facilities4installed in a plurality of factories. Then, server device3extracts, from a plurality of types of facility-related information stored in memory33, a piece(s) of facility-related information concerning facility4identified based on the facility ID transmitted from mobile terminal5and provides a user with the extracted piece of facility-related information. Information providing system1thus characterized may successfully provide a user with facility-related information of facility4, code10of which was read by the user using his/her mobile terminal5. This may allow the user to access the facility-related information of any desired facility4, improving user-friendliness of this information providing system1.

In information providing system1characterized as described thus far, server device3stores, in memory33, the facility-related information of each of facilities4installed in a plurality of factories. Then, server device3extracts, from a plurality of types of facility-related information stored in memory33, a piece(s) of facility-related information concerning another facility4that differs from facility4identified based on the facility ID transmitted from mobile terminal5and provides a user with the extracted facility-related information. Information providing system1thus characterized may successfully provide a user with facility-related information of another facility4that differs from facility4, code10of which was read by the user using his/her mobile terminal5. This may allow the user to access the facility-related information of any desired facility4, improving user-friendliness of this information providing system1.

In information providing system1, server device3includes, as the facility-related information, an analysis result of facility4. For example, server device3stores, in memory33, an analysis result of property α values obtained from a processing step A and a subsequent processing step B as the facility-related information, as illustrated inFIG.8. Thus, information providing system1may successfully provide a user with not only the current facility-related information but also the past facility-related information in response to the user's request for the facility-related information of facility4and may also successfully provide the user with a comparison result of pieces of current and past facility-related information. As illustrated inFIG.10, server device3stores, in memory33, defect rate analysis results obtained from defect processing steps as the facility-related information. Thus, information providing system1may successfully provide a user with an analysist result of different products processed in facility4in response to the user's request for the facility-related information of facility4.

In information providing system1, mobile terminal5, by reading code10attached to facility4using sensor56, is allowed to read facility ID. Thus, information providing system1may successfully and readily provide a user with the facility-related information of any facility4located near the user.

Modified Example

In information providing system1according to the earlier embodiment, each facility4transmits the facility-related information to server device3directly through network2. Instead, a PLC (programmable logic controller) programmed to collectively control a plurality of facilities4may be used. In this instance, the PLC obtains the facility-related information of each facility4and transmit the obtained facility-related information to server device3through network2. Optionally, a sensor(s) installed in each facility4or a sensor(s) connected to each facility4may transmit the facility-related information to server device3through network2.

In information providing system1, server device3may provide a user with the facility-related information as described below. Server device3may provide a user with the facility-related information obtained from one facility4installed in one factory (facility4whose code10was read). Server device3may provide a user with the current or past facility-related information obtained from one facility4installed in one factory (facility4whose code10was read). Server device3may provide a user with an analysis result of facility-related information obtained from one facility4installed in one factory (facility4whose code10was read).

Server device3may provide a user with pieces of facility-related information obtained from a plurality of facilities4installed in one factory (facilities4including facility4whose code10was read). Server device3may provide a user with pieces of current or past facility-related information obtained from a plurality of facilities4installed in one factory (facilities4including facility4whose code10was read). Server device3may provide a user with an analysis result of pieces of facility-related information obtained from a plurality of facilities4installed in one factory (facilities4including facility4whose code10was read).

Server device3may provide a user with the facility-related information obtained from another facility4installed in any other factory but a certain factory (facility4that differs from facility4whose code10was read). Server device3may provide a user with the current or past facility-related information obtained from another facility4installed in any other factory but a certain factory (facility4that differs from facility4whose code10was read). Server device3may provide a user with an analysis result of facility-related information obtained from another facility4installed in any factory but a certain factory (facility4that differs from facility4whose code10was read).

Server device3may provide a user with an analysis result of pieces of facility-related information of one facility4installed in one factory (facility4whose code10was read) and of another facility4installed in the same factory (facility4that differs from facility4whose code10was read). Server device3may provide a user with an analysis result of pieces of facility-related information of one facility4installed in one factory (facility4whose code10was read) and of another facility4installed in another factory (facility4that differs from facility4whose code10was read).

Code10may not necessarily be attached directly to facility4. Code10may be attached to any other suitable object apart from facility4. Code10may not necessarily be a one-dimensional code like barcode or a two-dimensional code like QR code (registered trademark). Code10may instead be one of IC tags (integrated circuit tags), for example, passive or active tags like RFID (radio frequency identifier) or Bluetooth (registered trademark) tags. In this instance, sensor56may be a reader adapted to read such IC tags.

The facility-related information may not necessarily be limited to the work management information, gas management information, property management information, or defect management information. The facility-related information may instead be any type of information concerning facility4. For instance, the facility-related information may contain sales-related information and/or inventory-related information of products manufactured in facility4. The facility-related information may contain information of the surrounding environment of facility4, for example, a factory, hospital or warehouse where facility4is installed.

The timing of analysis of the facility-related information by server device3may be an optional timing, for example, timing in response to storage of the facility-related information in memory33, periodical timing, or timing of receipt of a user's request.

The embodiments and examples disclosed herein are given by way of example in all aspects and should not be construed as limiting the scope of this disclosure. The scope of this disclosure is solely defined by the appended claims and is intended to cover the claims, equivalents, and all of possible modifications made without departing the scope of this disclosure.

REFERENCE SIGNS LIST