JP4436923B2 - Usage amount acquisition method and usage amount acquisition device - Google Patents

Description

  The present invention relates to a usage amount acquisition method and a usage amount acquisition apparatus suitable for application to counter confirmation work for acquiring the number of printed sheets (counter value) in, for example, a copier maintenance service.

  Conventionally, there is a business of leasing a copy machine to a client company and totaling and billing a usage fee for each number of sheets calculated from the number of sheets printed using the leased copy machine. The counter value is counted by a counter built in the copier, and the counter value is recorded in the built-in memory. The counter confirmation worker requested from the copier leasing source reads the counter value from the built-in memory of the copier and performs counter confirmation work.

  The operation of obtaining the counter value from the copier is referred to as “counter confirmation”. The target period for checking the counter and charging the customer company for the usage fee is, for example, one month. Then, when paying attention to a certain month, the target period for the counter confirmation is from the first day to the end of the month, and this period is referred to as “current month”.

  In the counter confirmation business, several counter confirmation methods have been adopted. For example, a counter confirmation method includes a method of acquiring data through a communication line, a method in which a person in charge of a customer company confirms a counter, fills in a counter value on a dedicated sheet, and sends it to a service company by postcard or FAX; There was a method in which the confirmation worker went to the site where the copier was installed and checked the counter.

  In addition, there are two types of fee billing methods determined when a lease contract between a service company and a customer company is concluded. There are two methods: billing by adding the usage fee to the basic fee, and billing the current month's usage fee in addition to the next month's billing fee without charging the current month if billing is not possible during the current month. It was.

In Patent Document 1, counter confirmation data obtained by measuring the consumption amount of recording paper or the like transmitted by the OA device is transmitted to a host computer. The host computer evaluates the counter confirmation data to determine whether there is an abnormality in the OA device. A communication system for determining is disclosed.
JP 2001-69291 A

  By the way, even if the counter confirmation data is transmitted through the telephone line, the counter value may not be collected due to a line failure or the like. Further, even if the counter confirmation worker goes to the customer's office to perform counter confirmation, the counter confirmation work may be delayed because the counter confirmation worker cannot enter the office. Even if the person in charge of the customer company confirms the counter, the service company may not obtain the counter value by not sending the counter value to the service company within the period.

  In such a case, it took a long time to find out that the counter confirmation data could not be acquired. In addition, even if a counter check worker is sent to the office based on the result, the counter check work will take time, so the counter check work will not be completed within the specified period (for example, the last business day of the month). As a result, there were cases in which it was not possible to charge the client company.

  For this reason, there has been a problem that the charge to be billed in the current month is billed in the following month, or only the basic fee is billed, and the counter check and billing that accurately reflect the actual results within the current month cannot be made.

  In addition, when the counter checker checks the counter by eye verification, the counter value is input after returning to work. However, if such a posting operation is performed, there is a risk that a transcription mistake or the like may occur. For this reason, it has been required that the acquired counter value can be mechanically input.

  The present invention has been made in view of such a situation, and an object thereof is to improve the accuracy of counter confirmation.

In the present invention, based on the contract ID, it extracts the equipment to check the usage of consumables is identified for each extracted equipment, a cutoff date to confirm the usage of consumables, use of consumables Among the plurality of closing dates having different dates for each procedure for checking the quantity, a closing date that is closest to the current date and for which the current date has not elapsed is acquired. Then, by referring to a log that records the consumption amount of consumables, it is confirmed whether there is a confirmation date for which the usage amount has been confirmed by the closing date. If the confirmation date does not exist in the log, priorities are assigned to a plurality of closing dates for checking the consumption amount of consumables, and the closing date and procedure are linked to each consumable specified by the contract ID. From the priority order data that is attached, the procedure for checking the usage amount of consumables is changed by reading the procedure that associates the closing date with a higher priority and the current date has not passed, and according to the changed procedure, Instruction data for instructing confirmation of the amount of consumables used by the closing date for which the current date has not yet passed is created .

  By doing in this way, when a counter value cannot be acquired by the closing date, it is possible to change the counter confirmation method to ensure counter confirmation.

  According to the present invention, when the counter check cannot be performed by a certain closing date, the counter check is performed by switching to a highly reliable counter checking method by the final closing date. There is an effect that billing can be performed.

  Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings.

FIG. 1 is a schematic diagram showing the entire device management system as an example of the present embodiment.
The device management system 101 of this embodiment can be connected to several web servers 102 and 103, a database server (hereinafter referred to as “DB server”) 104, and a number of client PCs 105, 106 and 107, and client PCs 107 which access these servers. The counter confirmation portable terminal 108 is configured. The counter confirmation portable terminal 108 is, for example, a PDA (Personal Digital Assistant) provided with a dot printer, and can print a counter value and an invoice acquired at a customer company visit.
The in-house LAN 109 constitutes a TCP / IP network mainly composed of known private IP addresses, and covers all group companies.
The client PC 105 is a typical personal computer and operates a web browser (not shown) for accessing the web server 102.
The web server 102 is separated and distributed for each group company or for each business in charge.
The counter check portable terminal 108 can be connected to the client PCs 105 and 106 to supply a counter value, and can also print a counter value and an invoice from a printer (not shown) connected to the in-house LAN. It is.

The client PC 105 accesses the web server 102.
The web server 102 accesses the DB server 104.
That is, the web server 102 provides a user interface for accessing the DB server 104 to the client PC 105.

The web servers 102 and 103 and the DB server 104 are distributed for the purpose of load distribution, safety ensuring, etc., and for facilitating the construction such as duplexing for safety ensuring.
Of course, when the scale of the system is small, these can be integrated.

FIG. 2 is a functional block diagram showing details of the web server 102 and the DB server 104.
The web server 102 includes a web server program 202 and many cgi (Common Gateway Interface: a mechanism for a web server to start a program in response to a request from a web browser).
Each cgi includes an employee authentication cgi 203 for authenticating an employee who can access the in-house LAN 109, and a cgi for creating an html document for creating various user interfaces.
The DB server 104 has a number of tables for storing various data, which play a central role in the device management system 101. FIG. 2 shows a part thereof. A detailed description of the table group will be described later (see FIG. 3).
The DB server 104 constitutes a well-known SQL (language specialized for relational database operation) server.

FIG. 3 is a schematic diagram partially extracting field names of a table group included in the DB server 104.
The employee table 302 is a table centered on an employee ID that uniquely identifies the employee. In addition to the “employee ID”, the field includes a field indicating the employee “name” and “affiliation”. Although not shown, a hash value of a password is also included, and is used for employee login authentication and the like.
An employee who visits a customer company and concludes a contract is also referred to as a “sales representative”.

The customer company table 303 is a table centering on a customer ID that uniquely identifies a customer company. In addition to “customer ID”, the field includes a field indicating “customer company name”. When a desired customer company name is displayed on the display screen of the client PC 105, the value of the “customer company name” field is acquired from this table.
The customer contact person table 304 is a table centering on the contact person ID for uniquely identifying the customer contact person. In addition to the “person in charge ID”, there are a “person in charge name” of the customer person in charge and a “customer ID” field for identifying the customer company.
The customer installation destination table 305 is a table centered on an installation destination ID that uniquely identifies an installation location (installation destination) when installing a device sold to a customer. In addition to “installation destination ID”, there are “installation location” and “customer ID” fields.

The negotiation table 306 is a table centering on the negotiation ID that uniquely identifies the negotiation. Create a new record when a salesperson starts a business deal with a customer. The field
・ In addition to "Business negotiation ID"
・ As one of the details of the negotiation, the “Opportunity Date” field showing the date when the negotiation was started,
・ The “negotiation status” field indicating the progress of the negotiation and the result (provisional contract, contract establishment, contract failure, etc.), and “customer ID” in the customer company table,
・ "Contact ID" in the customer contact table,
・ "Employee ID" in the employee table
Exists.

The contract table 307 is a table centering on a contract ID for uniquely identifying a contract. Create one new record per contract. The field
・ In addition to “Contract ID”,
-"Contract Type ID" indicating the type of contract,
-As one of the details of the contract, "Contract Date" field that shows the date when the contract was created,
-“Contract Status” field that shows the progress of the contract and its results (provisional contract, contract establishment, contract failure, etc.)
-“Issuance count status” that stores the number of officially issued contracts
・ "Parts code" indicating the parts that make up the contract,
-"Template code" indicating the template file determined for each part of the contract,
Exists.

  The business negotiation contract table 308 is a table composed of a pair of “business negotiation ID” and “contract ID” that describes a one-to-many relationship between a business negotiation and a contract. That is, a plurality of contracts can be generated for one business negotiation. Due to the presence of this table, it is possible to refer to the negotiation ID from the contract ID and vice versa.

  The forbidden condition table 309 is a table that describes combinations of products and services that cannot be sold together in an estimate created when a salesperson proceeds with a business negotiation. The combinations of “product codes” in the product basic information table 312 described later or “service codes” in the service basic information table are listed.

The closing date condition table 310 is a table describing contract conditions relating to the closing date of work for checking a counter such as a copier. The field
-"Contract ID" that indicates which contract the device belongs to,
・ In addition to the “product code” that identifies the device and the serial number of the device (hereinafter referred to as the “machine number”),
-As one of the details of the contract, a "Condition date condition" field indicating the condition of the due date,
There is a “priority” field indicating the priority of the “closing date condition”.
In the present embodiment, different closing dates are set depending on the counter confirmation method. That is, when the counter confirmation method changes, the closing date also changes.
In the counter confirmation method, priority is set for each machine number. A counter confirmation method with a high priority is determined, and the counter value is acquired by the closing date.

The contract type table 311 is a table that lists contract types. The fields include “contract type ID” and “contract type name”.
The contract types include “sales contract”, “hardware maintenance contract”, and “performance contract”.

The product basic information table 312 is a table centering on a product code for uniquely identifying a product. In addition to the “product code” for identifying each product, there are a “product name”, “product detailed information” field, and the like.
The service basic information table 313 is a table centered on a service code that uniquely identifies a service. In addition to the “service code” for identifying each service, there are a “service name”, “service detailed information” field, and the like.
The product etc. configuration table 315 is a table composed of a set of “service code” and “product code” describing a one-to-many relationship between services and products.
For example, under the name “Safety Pack”, a service including the maintenance service of personal computers and the provision of virus protection software products can be considered. Thus, since some services include products, such a table is provided.

  The contract product etc. table 314 is a table composed of a set of “contract ID” and “product code” or “service code” describing a one-to-many relationship between a contract and a product or service. That is, a plurality of products or services can be generated for one contract. This table includes fields such as “machine number” and “installation destination ID”.

The device management table 316 is a table that plays a core role in this embodiment.
Each device (product) is uniquely identified by the “product code” and “machine number”, and the date and status information of “the lifetime of the device”, from the delivery of the device to the customer, to the disposal or recycling of the device. This is a table that is recorded and managed one by one. The field
・ In addition to `` product code '' and `` machine number ''
"Contract ID" in the contract table 307 indicating the contract to which this device belongs,
"Installation ID" of the customer installation table 305 indicating the location where this device is installed,
-"Equipment operation status" indicating the status of this equipment, "Equipment logistics status", and "Date" recording the status information
Exists.

The counter confirmation log table 317 is a table that is mainly built in the copying machine and records a “counter” value that is incremented with each use. The copying machine is configured to charge the usage amount according to the number of times of use, that is, the number of sheets consumed by the copy output. Therefore, the counter value built in the copying machine is confirmed on the closing date determined every month and recorded in the counter confirmation log table 317. The field
"Contract ID" in the contract table 307 indicating the contract to which this device belongs,
・ In addition to `` product code '' and `` machine number ''
・ "Confirmation date" indicating the date when the counter value was acquired,
・ "Counter value" that stores the number of copies printed by copiers, etc. within the current month
・ "Counter status" indicating the status of obtaining the counter value,
・ "Counter check method" which shows which counter check method was adopted when acquiring counter value
Exists.

The contract template table 318 is a table for recording a part code for identifying a template part necessary for the contract and a template code for identifying the template. A contract template corresponding to the part code and the template code is recorded in the contract template table 318 as a template file.
The contract is created by combining the five parts described below. However, there are parts that are required in one contract but not required in another contract. These five parts are also referred to as “basic patterns”.
・ "Cover": A part that expresses the contractual relationship between A and B.
・ "Basic provisions": Parts that express "basic provisions" necessary for sales.
“Service clause”: A part that expresses a “basic clause” for added value such as maintenance service, not a thing (for example, a copy machine, a PC).
-“Contract fee”: A part that expresses the price at the time of estimation.
“Maintenance details”: When a maintenance service is contracted, a part that expresses what the service is to be performed on.

[Counter check function]
In the present embodiment, counter confirmation is performed and a usage fee is charged to a customer company that has concluded a performance contract.
The counter confirmation function performed in the device management system 101 roughly undergoes the following processing.
Before the monthly closing date, the counter value of the copier must be checked.
However, depending on the customer, the counter value may not be confirmed by the closing date.
In such a case, the “priority order” recorded in the closing date condition table 310 created when the contract is created in advance is referred to.
Check what counter check work will be performed after how many days from the closing date, and whether or not the work has already been completed, and create counter check instruction data to create a counter check slip to instruct the person in charge. Present appropriate instructions to the person in charge.

[Details of counter check]
FIG. 4 is a block diagram focusing on the counter confirmation function in the device management system 101 of this embodiment.

  The client PC 107 is an input unit 107b that accepts input of characters and numbers from a keyboard and the like, a communication interface 107c that is an interface for transmitting and receiving an html document to and from a counter confirmation web server 402 having a counter confirmation function, and a liquid crystal display A display unit 107d for displaying a screen (not shown) used for counter check work, an output unit 107e for outputting a counter check work slip to a printer (not shown) attached to the client PC 107, and a counter value from the counter check portable terminal 108. The input / output interface 107f is an interface that obtains and provides device information of the client company to the counter check portable terminal 108. The output unit 107e prints a counter confirmation work slip for a counter confirmation worker, which will be described later, a counter confirmation work slip for a person in charge of a customer company, and the like. In the following description, a counter confirmation work slip, a counter confirmation work slip and the like used for counter confirmation are also simply referred to as “counter confirmation slip”.

A counter confirmation worker 401 working at the service company can access the counter confirmation web server 402 installed at the sales company by operating the client PC 107. The counter confirmation worker 401 who performs the counter confirmation work is authenticated with the user ID and password input on the client PC 107 by the authentication cgi (not shown) of the counter confirmation web server 402.
The counter confirmation web server 402 performs predetermined processing in response to an access request (HTTP request message) coming from the client PC 107.
Depending on the contents of the predetermined processing, various tables stored in the DB server 104 are accessed such as data acquisition or writing in accordance with the SQL standard. An arrow line extending from the counter confirmation form creation cgi 403 to each table corresponds to this. Although these are conceptual lines, actually, as shown in FIG. 1, the web server 102 and the DB server 104 are connected to the in-house LAN 109, and these access operations indicated by arrows are performed through the in-house LAN 109. .

  The counter confirmation web server 402 includes a web server program 202, a counter confirmation form creation cgi 403, and an invoice creation unit 404. Although many cgi exist in addition to this, only those directly related in the present embodiment are extracted and described in FIG.

The web server program 202 constitutes an HTTP server. In response to a client request (HTTP request message) coming through the in-house LAN 109, which is a TCP / IP network, an HTML document and an execution result of cgi are transmitted in the form of an HTTP response message. An example is Apache (http://www.apache.org/).
The counter confirmation form creation cgi 403 creates an html document displayed on the web browser of the client PC 107.
The counter confirmation form creation cgi 403 and the invoice creation unit 404 include functions of an SQL client, access each table of the DB server 104, and acquire desired data.

  As described above, the DB server 104 constitutes a well-known SQL server. In FIG. 4, the program part of the SQL server is omitted in order to clarify the table handled by the counter confirmation form creation cgi 403. The actual DB server 104 includes a combination of an interactive database engine program that interprets and executes an input SQL language and a data file group that constitutes a table.

  FIG. 5 is a block diagram for explaining the function of the counter confirmation form creation cgi 403 in the counter confirmation web server 402.

A counter confirmation instruction data creation unit 503 that acquires data necessary for each item constituting the counter confirmation slip is obtained from the customer company table 303, the contract table 307, the closing date condition table 310, the contract type table 311, the counter confirmation log table 317, and the like. Information necessary for creating counter confirmation instruction data is acquired.
Then, the counter confirmation instruction data creation unit 503 extracts a device for counter confirmation based on the contract ID, and acquires a counter check closing date specified for each extracted device. Also, the counter confirmation log table 317 for recording the counter value is referred to, and it is confirmed whether there is a confirmation date for which the counter has been confirmed by the closing date. When the confirmation date does not exist in the counter confirmation log table 317, the procedure for confirming the counter is changed according to the priority order data defined by the contract ID with reference to the closing date condition table 310.

  Then, the counter confirmation instruction data creation unit 503 supplies the created counter confirmation instruction data to the counter confirmation form creation unit 502. The counter confirmation form creation unit 502 creates image data of the counter confirmation form based on the counter confirmation instruction data.

An html document creation unit 501 that creates an html document converts the image data of the counter confirmation slip into an html document and sends it to the client PC 107 as an html message.
The counter value for each device acquired by the counter checking worker is taken into the client PC 107. Then, the control unit 107a of the client PC 107 converts the counter value into an html document, and transmits an html message to the counter confirmation web server 402.

  The html document receiving unit 504 of the counter confirmation web server 402 receives this html message. When the counter value cannot be acquired by the closing date based on the received html message, the counter confirmation instruction data creation unit 503 creates counter confirmation instruction data in which the counter confirmation method and the closing date are changed, and the counter confirmation form creation unit 502 Supply.

  When the counter value can be acquired by the closing date, the counter confirmation instruction data creation unit 503 supplies the counter value to the fee calculation unit 505 that calculates the billing fee. The fee calculation unit 505 calculates a billing fee for the current month and creates billing data. The billing data is supplied to a bill data creation unit 506 that creates bills for customer companies. The invoice data creation unit 506 creates invoice image data and issues the invoice by a printer (not shown).

FIG. 6 is a conceptual diagram showing the relationship between the fields of each table in the DB server 104 of FIG.
The counter confirmation form creation cgi 403 searches the negotiation table 306 by using the negotiation ID with which the negotiation with the customer has been established as a key, and obtains various information related to the negotiation.
Next, the counter confirmation form creation cgi 403 searches the negotiation agreement table 308 with the negotiation ID, and obtains one or more agreement IDs of the corresponding agreements.
Next, the counter confirmation form creation cgi 403 searches the contract table 307 by contract ID and obtains various information related to the contract.
Next, the counter confirmation form creation cgi 403 searches the contract type table 311 using the contract type ID to obtain various information related to the contract type.
Further, the counter confirmation form creation cgi 403 searches the contract product etc. table 314 by the contract ID,
・ One or more product codes or service codes
・ Get one installation ID.

Next, the counter confirmation form creation cgi 403 searches the product basic information table 312 using the product code, and obtains various information related to the product.
Further, the counter confirmation form creation cgi 403 searches the service basic information table 313 using the service code, and obtains various information related to the service.
Also, the counter confirmation form creation cgi 403 searches the customer installation destination table 305 with the installation destination ID, and obtains various information relating to the installation destination.
Then, the counter confirmation form creation cgi 403 searches the device management table 306 with the contract ID and the installation destination ID, and obtains various information regarding the installation destination.
In this way, the counter confirmation form creation cgi 403 can acquire data in a state where the information of each table is linked, and can create counter confirmation instruction data.

  FIG. 7 is a flowchart showing an example of processing between the PC client that creates the contract and the counter confirmation web server 402.

  First, the counter confirmation web server 402 creates counter confirmation instruction data (step S1). Then, the counter confirmation form image data created based on the counter confirmation instruction data is transmitted to the client PC (step S2).

  The client PC receives the counter confirmation form image data (step S3) and issues a counter confirmation form. The counter confirmation slip is used by a service company counter confirmation worker to list devices for the counter confirmation within the current month.

  When the client PC obtains the counter value from the device (step S4), it transmits the counter value to the counter confirmation web server 402 (step S5). Then, the counter confirmation web server 402 receives the counter value (step S6).

  The counter confirmation web server 402 calculates a charge to be charged in the current month based on the received counter value (step S7). Thereafter, billing data as a basis for the bill to be sent to the customer company is created (step S8).

FIG. 8 is a flowchart illustrating an example of the counter confirmation process.
First, the counter confirmation web server 402 extracts “active devices” and “devices that require counter confirmation” from the device management system 101 (step S11), and sets them as a list. Then, the search key is set at the top of the list (step S12).

  Next, from the contract information specified by the contract ID, a closing date for checking the counter of the device is acquired (step S13). Then, the counter confirmation log table 317 is searched to obtain the counter confirmation status up to the previous month (step S14).

  Next, the counter confirmation web server 402 determines whether or not the counter has been confirmed by the closing date (step S15). If the counter has not been confirmed by the closing date, a counter confirmation changing process described later is performed (step S16).

  If the counter has been confirmed by the closing date, it is determined whether there is a next record (step S17). If there is a next record, the process returns to step S3 to continue the process of acquiring the counter value. If there is no next record, the process ends.

FIG. 9 is a flowchart illustrating an example of the counter confirmation change process.
First, the counter confirmation web server 402 obtains a confirmation date from the counter confirmation log table 317, thereby retrieving the counter confirmation result up to the previous month (step S21). Then, the counter confirmation condition specified by the contract ID is referred to (step S22). As the counter confirmation condition, when the counter value cannot be acquired by the closing date, a counter checking method having a higher priority is selected and the closing date on which the counter confirmation is performed is determined.

Next, the counter confirmation web server 402 refers to the closing date condition table 310 and selects a counter confirmation method with a higher priority of the machine number specified by the contract ID (step S23). Next, it is determined whether or not a condition for changing the counter confirmation method is satisfied (step S24).
The condition for changing the counter confirmation method is to determine whether it is possible to switch to the counter confirmation method with the next highest priority when the counter value cannot be obtained by the closing date with the counter confirmation method with the highest priority. It is a condition. When the counter check method with the next highest priority is switched, a closing date designated by this counter check method can be newly set.

  When the change condition of the counter check method is satisfied, a list based on the changed counter check method is output (step S25), and the process returns to the counter check process (see FIG. 7). If the condition for changing the counter check method is not satisfied, it is determined whether or not the next counter check method can be changed (step S26).

  If it can be changed to the next counter check method, the process returns to the process of step S24, and the counter check method is changed to the next highest priority check method. If there is no changeable counter confirmation method, the sales representative is directed to the installation location of the device to generate instruction data (step S27), and the process returns to the counter confirmation process (see FIG. 7).

Here, specific counter confirmation processing will be described with reference to FIG.
FIG. 10 is a flowchart illustrating an example of counter confirmation processing.
In the present embodiment, the CSS (Customer Support System) acquisition in which the first closing date is set, the visit acquisition in which the second closing date is set, and the third closing date are set in descending order of the priority of the counter confirmation method. It is a counter confirmation request. Naturally, according to the embodiment, the priority order changes and the closing date also changes.

  CSS acquisition is a method of acquiring a counter value of a device via a communication line. CSS is a remote diagnosis and automatic counter confirmation system using a public line. It has a function of preventing a failure of the device and minimizing the failure period even if the device breaks down. In addition, the counter value can be automatically transmitted by the first closing date.

  The visit acquisition is a method in which the counter confirmation worker visits the customer company and confirms the counter by the second closing date. Upon receipt of the counter confirmation work slip issued by the counter confirmation web server 402, the counter confirmation worker heads for the device installation location. Then, the counter confirmation worker uses the counter confirmation portable terminal 108 to input the counter value or connect to a device to acquire the counter value.

The counter confirmation request is a method in which, when entry to the place where the device is installed is prohibited from the viewpoint of security, the person in charge at the client company is asked to confirm the counter by the third closing date. . In this case, the counter confirmation web server 402 issues a counter confirmation request form and transmits it to the person in charge at the customer company.
Upon receipt of the counter confirmation request form, the counter value confirmed by the person in charge at the customer company is sent to the service company via a web page, fax, postcard, etc. (not shown). In the case of the counter value obtained from the web page, the counter confirmation operator of the service company converts the data and sends it to the counter confirmation web server 402. Similarly, the counter value received by Fax, postcard, etc. is acquired by the client PC by OCR reading or key input, and is sent to the counter confirmation web server 402.

  First, a communication check between the counter confirmation web server 402 and the counter confirmation target device is performed (step S31), and it is determined whether there is a communication abnormality (step S32). When there is a communication abnormality, the visit inspection instruction data for making the engineer go to the installation location of the counter confirmation target device and perform the inspection work is created (step S33).

  Next, as a result of the visit inspection by the engineer, it is determined whether or not the communication abnormality of the counter confirmation target device continues (step S34). When communication abnormality of the counter confirmation target device continues, instruction data for switching the counter confirmation method to visit confirmation by the worker is created (step S41).

  When there is no communication abnormality in the process of step S32 and the process of step S34, the counter confirmation web server 402 creates counter confirmation instruction data (step S35). Then, the counter confirmation web server 402 compares the magnitude relationship between the current date and the first closing date (step S36). As the current date, a system date acquired by the counter confirmation web server 402 may be used.

If the current date is before the first closing date, a process of acquiring a counter value via the communication line is performed (step S37).
As a result, it is determined whether or not the counter has been confirmed (step S38). If the counter can be confirmed, charge calculation is performed (step S50). If the counter cannot be confirmed, the process returns to step S36, and the counter value acquisition process via the communication line is continued until the first closing date is passed.

  In the determination step S36, if the current date exceeds the first closing date, that is, if the counter value cannot be obtained by CSS by the first closing date, the counter confirmation web server 402 sets the second closing date. At the same time, visit data for making the counter check worker go to the installation location of the device is created (step S41). Then, the counter confirmation web server 402 compares the magnitude relationship between the current date and the second closing date (step S42).

  If the current date is before the second closing date, the counter check worker is directed to the installation location of the device, and the counter value is acquired from the device using the mobile terminal 108. The acquired counter value is taken in by the counter confirmation web server 402 (step S43).

  As a result, it is determined whether or not the counter has been confirmed (step S44). If the counter can be confirmed, charge calculation is performed (step S50). If the counter cannot be confirmed, the process returns to the process of step S42, and the process of issuing a counter confirmation work sheet for directing the counter confirmation worker to the installation location of the device is continued until the second closing date is passed.

  In the determination step S42, when the current date exceeds the second closing date, that is, when the counter checking worker cannot acquire the counter value by the second closing date, the counter checking web server 402 sets the third closing date. And a counter confirmation request form for requesting counter confirmation to the person in charge of the customer company is issued (step S45).

  Then, the counter confirmation web server 402 compares the magnitude relationship between the current date and the second closing date (step S45). If the current date is before the third closing date, the data acquisition from the fax, postcard or the like in which the counter value is recorded from the person in charge of the customer company, or the data acquisition from the web screen is continued (step S47).

  As a result, it is determined whether or not the counter has been confirmed (step S48). Note that. When the person in charge of the customer company checks the counter, the counter check may not be performed correctly because the numerical value is read incorrectly or the character cannot be determined.

  If the counter can be confirmed, charge calculation is performed (step S50). If the counter cannot be confirmed, the process returns to step S46 and waits for the reception of the counter value sent from the person in charge at the customer company until the third closing date is passed.

  If the counter cannot be confirmed by the third closing date, the charge for the current month is carried forward to the next month or the basic charge is applied to the billed amount according to the contents of the contract concluded with the customer in advance (step S49).

  After calculating the billing amount in the processing of steps S49 and S50, a bill for usage fee is issued to the customer (step S51).

  According to the present embodiment described above, when the counter check cannot be performed by the closing date by a certain counter check method, the counter value can be acquired within the current month by switching to another counter check method. Each counter check method has a closing date within the current month. If the counter cannot be confirmed, the counter confirmation method is switched according to the priority order. In this way, since a plurality of closing dates are set within the current month and the method is switched to a plurality of counter confirmation methods, the reliability of the acquired counter value is increased. For this reason, billing can be performed with a more accurate counter value, which has the effect of improving customer satisfaction.

  In addition, when the counter is confirmed on the set closing date, it is possible to calculate an immediate fee and issue an invoice. Conventionally, when the counter is checked at the end of the current month, even if the client company wishes to make a bill at the end of the month, there is no choice but to issue a bill by hand. However, according to the present invention, it is possible to deal with an immediate invoicing of customer convenience without creating an individual invoice. For this reason, it is possible to reduce the man-hours required for counter confirmation, and to increase the reliability of charges charged to customer companies.

  Conventionally, when the counter value could not be obtained through the communication line, an emergency counter check operation was performed, so that the normal operation was affected by the arrangement of workers. However, according to the present embodiment, a worker who performs counter confirmation can go to a necessary place at a necessary time and confirm it. For this reason, it is easy to estimate the personnel allocation, and it is not necessary to perform irregular personnel allocation, so that it is possible to perform an efficient counter check operation.

  If the counter cannot be confirmed, only the basic fee can be applied for the current month or the next month can be charged. For this reason, the urgent counter check operation at the end of the current month can be abolished, and the effect on the normal operation can be eliminated.

  Further, the period for checking the counter is within the current month, but it may be, for example, within two weeks or within three months. The length of the period can be freely changed according to the contract with the customer.

  The embodiment of the present invention has been described above. However, the present invention is not limited to the above-described embodiment, and other modifications may be made without departing from the gist of the present invention described in the claims. It goes without saying that application examples are included.

1 is a schematic diagram illustrating an entire device management system according to an embodiment of the present invention. It is a functional block diagram which shows the detail of a web server etc. and DB server. It is the schematic which extracted a part of field name of the table group contained in DB server. It is a block diagram which shows the example of a counter confirmation function among apparatus management systems. It is a block diagram explaining the function of counter confirmation form creation cgi and an invoice creation part. It is a conceptual diagram which shows the relationship of the field of each table in DB server. It is a sequence diagram which shows the example of a contract creation process of a client PC and a counter confirmation web server. It is a flowchart which shows the example of a contract preparation process of a client PC. It is a flowchart which shows the example of a change process of a counter confirmation method. It is a flowchart which shows the example of a change process of a counter confirmation method and charge calculation.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 101 ... Equipment management system, 102, 103 ... Web server, 104 ... DB server, 105, 106, 107 ... Client PC, 109 ... In-house LAN, 202 ... Web server program, 203 ... Employee authentication cgi, 302 ... Employee table , 303 ... customer company table, 304 ... customer staff table, 305 ... customer installation destination table, 306 ... negotiation table, 307 ... contract table, 308 ... negotiation contract table, 309 ... prohibition condition table, 310 ... deadline condition table, 311 ... Contract type table, 312 ... Product basic information table, 313 ... Service basic information table, 314 ... Contract product etc. table, 315 ... Service basic information table, 316 ... Device management table, 317 ... Counter confirmation log table, 318 ... Contract Template table, DESCRIPTION OF SYMBOLS 01 ... Sales person, 402 ... Contract preparation web server, 403 ... Counter confirmation table preparation cgi, 404 ... Invoice preparation part, 502 ... Counter confirmation form preparation part, 503 ... Counter confirmation instruction data preparation part, 505 ... Charge calculation Part, 506... Bill data creation part

Claims (4)

Extracting a device for checking the amount of consumables used based on the contract ID;
It is a closing date for confirming the consumption amount of the consumable that is specified for each extracted device, and the date is different among the plurality of closing dates for each procedure for confirming the consumption amount of the consumable. Obtaining the closing date that is closest and for which the current date has not passed;
Referring to a log that records the consumption amount of the consumables, and confirming whether there is a confirmation date for confirming the consumption amount by the closing date;
If the confirmation date does not exist in the log, priorities are assigned to a plurality of closing dates for checking the consumption amount of the consumables, and the closing date is set for each of the consumables specified by the contract ID. And a procedure for reading the procedure that is associated with the closing date that has the higher priority and the current date has not yet passed from the priority data that is associated with the procedure, and confirms the amount of consumables used. Step to change the
A usage amount acquisition method comprising the step of creating instruction data for instructing to check the usage amount of the consumables by the modified date when the current date has not passed by the closing date. Further, the method includes a step of creating data representing a confirmation slip associated with the changed procedure and the closing date associated with the procedure and including the closing date for which the current date has not passed, based on the instruction data. The usage amount acquisition method according to claim 1. Based on the contract ID, a device for confirming the amount of consumables used is extracted, and is the closing date for confirming the amount of consumables used, which is specified for each extracted device. Refer to the log that records the usage amount of the consumables by obtaining the closing date that is closest to the current date and the current date has not yet passed among the plurality of closing dates that have different dates for each procedure to check And a usage amount confirmation instructing unit for confirming whether there is a confirmation date for confirming the usage amount by the closing date;
If the confirmation date does not exist in the log, priorities are assigned to a plurality of closing dates for confirming the consumption amount of the consumables, and the plurality of consumables specified by the contract ID are A procedure changing unit that reads out the procedure having the higher priority from the priority data that records the priority of the procedure of the procedure, and changes the procedure for checking the usage amount of the consumables;
An instruction data creating unit that creates instruction data for instructing to check the amount of the consumable used by the closing date when the current date has not passed, according to the changed procedure. Usage acquisition device. And a confirmation slip creation unit that creates data representing a confirmation slip associated with the changed procedure and the closing date for which the current date has not passed, based on the instruction data. The usage amount acquisition device according to claim 3.

Images