JP2009086723A - Due date management support processing system, method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a due date management support processing system, due date management support processing method and due date management support processing program for supporting implementation of efficient and secured due date management. <P>SOLUTION: In an event management database 23, an event management record constituted including data about a subject code, process code, cycle, process scheduled day, priority, and holiday revision is recorded. When the process code of a preceding event is not recorded in an event management record in a schedule development process, a control part 21 of a due date management support server 20 computes the process due date based on the process scheduled day. Meanwhile, when the process code of preceding event is recorded on event management record, the control part 21 computes the process due date based on the preceding event. Then the control part 21 performs holiday revision and registers the processing due date in a due date management database 24. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a due date management support processing system, method, and program for supporting due date management in which office work processes are continuously performed according to a determined rule.

  Today, various asset management methods are being considered. For example, in order to raise management funds, there are cases where securitization of receivables is performed. Furthermore, liquidity prevents financial immobilization and effectively rotates funds to improve financial content and strengthen the management base. Representative liquidation methods include a method of trusting monetary claims, etc. and allowing investors to acquire the beneficial interests (trust method), transferring monetary claims etc. to a corporation such as SPC, There is a method of issuing (SPC method).

  In the basic scheme of securitization of receivables using a monetary receivable trust, receivables held by a consignor (originator) are trusted by a trust bank. The trust bank creates trust beneficiary rights using the entrusted receivables as trust assets, sells them to investors, and receives the purchase price of beneficiary rights from investors. The trust bank then delivers the beneficiary sales price received from the investor to the consignor, and the consignor raises funds. When the date of the trusted receivable comes, the obligor settles the debt with the consignor. The consignor hands over the funds received from the obligor to the trust bank that is the receivable holder at that time. The trust bank uses the funds delivered from the consignor as the source of funds to redeem the principal of the beneficial interest to the investors and pay a dividend. By securitizing the receivables in this way, the originator can procure low interest funds based on the creditworthiness of the receivable receivables, and it is possible to off-balance the receivables in trust.

  Local governments may also convert loans to SMEs into trust beneficiary rights. As part of the bond market concept for SMEs, “CLO funding” is being implemented as part of the Tokyo system financing. CLO (Collateralized Loan Obligation) is a method of raising funds from the market by selling securities backed by loans to investors. Here, a financial institution transfers a loan to a trust bank for a new loan made to a small and medium-sized company, and issues a security backed by the trust beneficiary right to investors through an SPC (Special Purpose Company).

  Along with such a trend of fluidization, various asset fluidization methods have been studied (for example, see Patent Document 1). In the technology described in this document, the originator does not require the establishment of a special purpose company, and the originator trusts the assets it owns in order to mobilize the assets owned by the originator without causing tax payment obligations under the tax law. Trust the company. Then, the trust company that received the asset trust gives the originator the trust beneficiary right for the received asset. The trust company accepts non-recourse loans from investors on the basis of the trust assets in trust. Then, the trust company transfers the money lent from the investor to the originator as a principal redemption based on the trust beneficiary right. In addition, the trust company returns a part of the profits from the cash flow to the investors as interest.

In addition, a system that manages such securitization of claims and completes a series of securitization operations with high accuracy (see, for example, Patent Document 2). In the technology described in this document, the system server is provided with an assigned receivable information storage unit that stores receivable information that is information on receivables to be liquidated. When revising the receivable information stored in the transferred receivable information storage unit, the receivable revocation information having the receivable amount at the time of transfer that offsets the receivable amount at the time of transfer of the receivable receivable information and the receivable information after the correction Certain credit correction information is entered into the system server. The system server stores the input receivable cancellation information and receivable correction information in the transferred receivable information storage unit in addition to the correction target receivable information.

In such an asset management method, due date management is important. For example, in the defined contribution pension management, many dates are set, and management according to the dates is performed (see Patent Document 3).
JP 2001-325429 A (first page) JP 2005-309697 A (first page) Japanese Patent Laying-Open No. 2005-157886 (first page)

  Management of such due dates requires certainty and places a heavy burden on the administrator. Even in the above securitization of receivables, a lot of work occurs because various institutions such as trust banks, SPCs and investors are involved. Furthermore, the securitization of receivables has a large target amount and has a significant impact on the business condition. For this reason, reliable management is desired in the business of liquidated assets. In particular, in the liquidation scheme of receivables, there are many events such as collection closing, collection status report, collection payment, revenue calculation, revenue distribution, etc., and due dates are set between the parties for these events.

  Further, during this time limit, the due date of the next event may be determined according to the previous event. In addition, such dates are subject to change depending on the situation. It is only necessary to unify such due date management, but many of the liquidation schemes for own receivables are handmade by trial and error, the management methods are diverse, and unification is sometimes difficult. When spreadsheet software or the like is used in such due date management, plasticity and versatility cannot be imparted.

  The present invention has been made to solve the above-described problems, and provides a date management support processing system, a date management support processing method, and a date management support processing program for supporting efficient and reliable execution of date management. It is to provide.

  In order to solve the above-mentioned problem, the invention according to claim 1 records an event management record in which an event identifier of a preceding event and a difference day number of the due date of the preceding event are associated with the event identifier. A date management support processing system provided with event information storage means, due date information storage means for recording a due date management record in which a due date for processing is recorded for an event identifier, and a control means for calculating an event processing due date, In the event setting, the control means obtains a preceding event to be associated with the event and a difference day between the due date of the preceding event and records it in the event information storage means, and develops a schedule for the event. If yes, get the predecessor date scheduled for the preceding event Calculating a due date obtained by adding the difference days to the preceding due date, and recording a schedule expansion unit that records the due date information storing unit as a processing due date of the event; and outputs a processing due date recorded in the due date information storing unit The schedule output means is provided.

  According to a second aspect of the present invention, in the due date management support processing system according to the first aspect, the event information storage means stores a priority for each event identifier, and the event registration means associates with the preceding event. The gist of the given event is to record the event information storage means with the next priority of the priority given to the preceding event.

  According to a third aspect of the present invention, in the due date management support processing system according to the first or second aspect, in the due date information storage means, a completion flag is recorded for each event for which processing has ended, and the schedule output means When the processing date of the event that has reached the due date is output, the preceding event of this event is specified, and when the completion flag is not recorded for the event identifier of this preceding event in the due date storage means The gist is to output an alarm.

  According to a fourth aspect of the present invention, there is provided an event information storage unit that records an event management record in which an event identifier of a preceding event and a difference date from the due date of the preceding event are associated with the event identifier; On the other hand, a due date management support processing system provided with due date information storage means for recording a due date management record for recording a due date and a control means for calculating the due date for processing an event is a method for performing due date management support processing. In the event setting, the control means obtains the preceding event associated with this event and the difference days between the due dates of the preceding event, and records them in the event information storage means, and the event In the case of schedule expansion, the destination of the schedule expansion for the preceding event A schedule development stage for obtaining a due date, calculating a due date obtained by adding the number of difference days to the preceding due date, and recording the due date in the due date information storage means, and recording the due date information in the due date storage means The gist is to execute a schedule output stage for outputting a processing date.

  According to a fifth aspect of the present invention, there is provided an event information storage means for recording an event management record in which an event identifier of a preceding event and a difference date from the due date of the preceding event are associated with the event identifier; In order to perform due date management support processing using due date management support processing system provided with due date information storage means for recording due date management records for recording the due date of processing and control means for calculating the due date of event processing An event registration unit, an event for acquiring a preceding event associated with the event in the event setting and a difference day number between the due date of the preceding event and recording the difference in the event information storage unit If the schedule is expanded for the preceding event, A schedule expansion unit that acquires the date of the preceding due date, calculates a due date obtained by adding the difference days to the preceding due date, and records it in the due date information storing unit as a processing due date of the event, and records in the due date information storing unit The gist is to function as a schedule output means for outputting the processed processing date.

(Function)
According to the first, fourth, and fifth aspects of the present invention, in the event setting, the control means acquires the preceding event associated with the event and the number of days difference between the due date of the preceding event, and the event information storage means To record. Then, when performing schedule development for the event, the preceding date that was scheduled for the preceding event is acquired, a date obtained by adding the difference days to the preceding date is calculated, and the due date information storage means is used as the event processing date. Record. Then, the processing date recorded in the date information storage means is output. This makes it possible to register a processing date for an event linked to another event.

  According to the second aspect of the present invention, the priority order is recorded for each event identifier in the event information storage means. Then, the event registration means assigns the next priority of the priority given to the preceding event and records the event associated with the preceding event in the event information storage means. Thus, by using this priority order, processing dates linked to other events can be calculated sequentially.

According to the third aspect of the invention, the due date information storage means records a completion flag for each event for which processing has ended. Then, when outputting the processing due date of the event for which the due date has arrived, the schedule output means identifies the preceding event of this event and records a completion flag for the event identifier of this preceding event in the due date information storage means. If not, an alarm is output. As a result, when the preceding event to be linked is not completed, an alert is issued, so that the paperwork can be reliably performed for the linked event.

  According to the present invention, it is possible to provide a date management support processing system, a date management support processing method, and a date management support processing program for supporting efficient and reliable execution of date management.

  DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments embodying the present invention will be described with reference to FIGS. The present embodiment will be described as a due date management support processing system, due date management support processing method, and due date management support processing program used for due date management of liquid assets. In the management of the liquidated assets, events such as “recovery closing”, “recovery status report”, “payment of payment”, “revenue calculation”, “revenue distribution”, and the like are performed. Here, a date is set for each event. For example, the due date for “collection closing” is set to a predetermined day (15th of every month) every month, and the due date for “collection status report” is set to be three business days after “collection closing”.

  In this embodiment, as shown in FIG. 1, the due date management support server 20 as the due date management support processing system executes the due date management support processing. A client terminal 10 is connected to the due date management support server 20 via a network.

  The client terminal 10 is a computer terminal used by a registration person who registers a case or an event, a paperwork person who performs paperwork according to a due date, a manager of these persons, and the like. The client terminal 10 is used when each user accesses the due date management support server 20. The client terminal 10 has a function of transmitting data via a network, a function of displaying received data, and the like. For this reason, the client terminal 10 includes an input unit such as a keyboard and a mouse, an output unit such as a display, a communication unit, and the like in addition to a CPU, RAM, and ROM (not shown).

  The due date management support server 20 is a computer system that performs data processing for managing due dates based on data received from the client terminal 10. The due date management support server 20 includes a case management database 22, an event management database 23 as an event information storage unit, a due date management database 24 as a due date information storage unit, a calendar database 25, and a control unit 21 for controlling them.

  The control unit 21 functions as a control unit that performs various data processing for supporting date management. The control unit 21 includes a CPU, a RAM, a ROM, and the like (not shown), and performs processes described later (each process in the item registration stage, event registration stage, schedule development stage, schedule output stage, schedule change stage, etc.). By executing the date management support processing program for that purpose, the control unit 21 functions as a case registration unit 211, an event registration unit 212, a schedule expansion unit 213, a schedule output unit 214, and a schedule change unit 215 as shown in FIG. To do.

Here, the case registration unit 211 executes a process for registering a case for which due date management is performed.
The event registration unit 212 executes processing for registering the contents (events) of the paperwork performed in each case.

The schedule expansion unit 213 executes a process for expanding a registered event on a due date to create a schedule.
The schedule output unit 214 executes a process for outputting a list of events for performing the business process.
The schedule changing unit 215 executes processing for changing the schedule of each event.

  In the case management database 22, as shown in FIG. 2A, a case management record 220 in which a case for managing a due date is registered is recorded. This matter management record 220 is registered when a matter to be managed is set. The case management record 220 includes data relating to a case code, a case name, a secretary, a period, trust contract information, and underlying bond information.

Data relating to an identifier for identifying each case is recorded in the case code data area.
In the case name data area, data relating to an identifier for specifying the name of the case is recorded. In the present embodiment, a name for specifying the liquidated asset is recorded.

In the secretary data area, data for identifying the financial institution in charge of this case is recorded. In this embodiment, the name of the secretary is recorded.
In the period data area, data relating to the period for which the case is fluidized is recorded.

In the trust contract information data area, data related to the contents of the trust contract (execution date of original receivable, final date, trust end date, etc.) is recorded.
The original receivables information data area relates to the contents of the original receivables of this project (initial repayment date and final repayment date of principal, interest initial repayment date and final repayment date, interest collection method, cycle, collection month, collection, etc.) Data is recorded.

  In the event management database 23, as shown in FIG. 2B, an event management record 230 in which events included in the case are registered is recorded. This event management record 230 is registered when an event for performing paperwork in a case is set. The event management record 230 includes data relating to a case code, a processing code, an initial date, a cycle, a scheduled processing date, priority, holiday correction, and an end date.

Data relating to an identifier for identifying each case is recorded in the case code data area.
In the processing code data area, data relating to an identifier (event identifier) for specifying the contents (event) of the paperwork in this case is recorded. In the present embodiment, the events include “collection closing”, “collection status report”, “collection payment”, “revenue calculation”, “revenue distribution”, and the like. By using each processing code, it is possible to specify a name representing the processing content using a processing code table (not shown).

In the initial date data area, data relating to the date (year / month / day) for specifying the initial implementation date of this event is recorded.
In the cycle data area, data for specifying the cycle of this event is recorded. For example, when a periodic cycle is designated such as “once a month”, “1 month” is registered as the periodic information. Further, when linking to another event, the processing code of the event to be linked (event identifier of the preceding event) is registered as the cycle information.

In the scheduled processing date data area, data for specifying a calendar date for carrying out the paperwork of this event is recorded in this cycle. For example, when “monthly” is recorded in the periodic data area, a calendar date (for example, “25th day”) is recorded as the scheduled processing date. If “every week” is recorded in the periodic data area, the day of the calendar (for example, “Monday”) is recorded as the scheduled processing date. In the case of the end of the month, the “month end” designation code is recorded as the scheduled processing date. In addition, when a processing code to be linked is recorded in the periodic data area to be linked to another event, the number of difference days to be shifted with respect to the due date of the linked event (for example, “3 business days later”) Record.

  In the priority data area, data for specifying the order in which the schedule is developed is recorded. For example, the date and day of the week are recorded in the scheduled processing date data area, and an event that is not linked to other events is given the first priority (highest priority). In addition, a second priority order is assigned to an event that is linked to an event assigned the first priority order. Then, an event linked to an event to which the n-th priority is assigned is given the next (n + 1) -th priority.

In the holiday correction data area, data for specifying the handling when the processing due date is set as a closed day in the calendar database 25 is recorded. For example, when paperwork is performed only on business days, a flag for specifying “next business day” or “previous business day” is recorded.
In the end date data area, data for specifying the end of the period for setting the event is recorded.

  In the due date management database 24, as shown in FIG. 2C, a due date management record 240 relating to the due date of the event of each item is recorded. This date management record 240 is registered when a schedule development process described later is performed. The due date management record 240 is configured to include data relating to a case code, a case name, a processing code, a processing date, a reception number, a confirmation flag, and a completion flag.

Data relating to an identifier for identifying each case is recorded in the case code data area.
In the case name data area, data relating to an identifier for specifying the name of the case is recorded.

In the processing code data area, data relating to an identifier for identifying an event in this case is recorded.
In the processing date data area, data relating to the date (year / month / day) for carrying out the paperwork is recorded.

In the reception number data area, data relating to an identifier for specifying the execution contents of the paperwork is recorded.
In the confirmation flag data area, a flag indicating that the contents of the paperwork have been confirmed on the due date is recorded.
In the completion flag data area, a flag indicating that the paperwork has been completed on the due date is recorded.

  In the calendar database 25, a business day table for specifying business days in the calendar is recorded. In the present embodiment, holiday correction is performed using this business day table. For example, in an event in which holiday correction is registered, if the calendar date calculated using the scheduled processing date of the event management record 230 corresponds to a closed day, the next business day or the previous business day specified by the business day table The processing date is changed.

  Next, processing when performing due date management support according to the present embodiment will be described. Here, periodic information registration processing, schedule expansion processing, schedule output processing, and schedule change processing are performed.

(Cycle information registration process)
First, the period information registration process will be described with reference to FIG. This periodic information registration process is executed when the due date management support server 20 receives a schedule registration request input by the person in charge of registration from the client terminal 10.

  Here, the control unit 21 of the due date management support server 20 executes a case information registration process (step S1-1). Specifically, the case registration unit 211 of the control unit 21 transmits the case information registration screen data to the client terminal 10. In this case, the display of the client terminal 10 outputs a case information registration screen provided with a case name setting field, a secretary line setting field, a period setting field, a trust contract information setting field, and an underlying bond information setting field. Then, the person in charge of registration inputs the matter contents on the matter information registration screen. When the input of the case details is completed and the transmission instruction is input, the client terminal 10 transmits the case registration instruction to the due date management support server 20. This matter registration instruction includes data related to the matter contents entered on the matter information registration screen. Upon receiving the case registration instruction, the case registration unit 211 of the control unit 21 of the due date management support server 20 assigns a case code to the case registration instruction, and manages the case management record 220 including the contents of each received case. Register in the database 22.

  Next, the control unit 21 of the due date management support server 20 executes an event registration process (step S1-2). Specifically, the event registration unit 212 of the control unit 21 transmits event registration screen data to the client terminal 10. In this case, an event registration screen provided with a processing code setting field, an initial date setting field, a cycle setting field, a scheduled processing date setting field, and a holiday correction selection field is output on the display of the client terminal 10. First, the person in charge of registration sets the processing code and the initial date of the event to be registered in the processing code setting field and the initial date setting field of the event registration screen.

  Then, using the period setting field on the event registration screen, a period cycle (“monthly” or “weekly”) is selected, or a link to another event is selected. When a period is selected in the period setting field, the client terminal 10 transmits a period setting notification to the due date management support server 20. This cycle setting notification includes data related to the processing code, initial date, and cycle information (cycle cycle and interlocking flag) input on the event registration screen.

  In this case, the event registration unit 212 of the control unit 21 generates an event management record 230 that records the registration target case code, processing code, and initial date, and registers the event management record 230 in the event management database 23.

  Next, the control unit 21 of the due date management support server 20 executes an event-linked necessity determination process (step S1-3). Specifically, the event registration unit 212 of the control unit 21 determines whether the interlock flag is set in the cycle information included in the cycle setting notification.

  When a cycle is set in the cycle setting notification and is not linked to another event (in the case of “NO” in step S1-3), the control unit 21 of the due date management support server 20 performs a cycle information registration process. Is executed (step S1-4). Specifically, the event registration unit 212 of the control unit 21 records the received periodic cycle in the periodic data area of the event management record 230.

  Next, the control unit 21 of the due date management support server 20 executes the highest priority assignment process (step S1-5). Specifically, the event registration unit 212 of the control unit 21 assigns a first rank to the event management record 230 and records it in the priority data area.

  And the control part 21 of the due date management support server 20 performs the registration process of a process scheduled date (step S1-6). Specifically, the event registration unit 212 of the control unit 21 acquires the date and day of the week as the scheduled processing date from the client terminal 10 through the event registration screen. Then, the event registration unit 212 records the scheduled processing date in the scheduled processing date data area of the event management record 230.

  On the other hand, when the linkage flag is set in the cycle setting notification and linked to another event (in the case of “YES” in step S1-3), the control unit 21 of the due date management support server 20 starts the event from the registered event. A candidate extraction process is executed (step S1-7). Specifically, the event registration unit 212 of the control unit 21 extracts from the event management database 23 the event management record 230 that has already been registered with the same case code.

  Then, the event registration unit 212 transmits the processing code of the extracted event management record 230 to the client terminal 10 as an event candidate that can be linked. In this case, a list of event candidates received from the due date management support server 20 is displayed in the scheduled processing date setting field output on the display of the client terminal 10. When an event candidate is selected from the list display, the client terminal 10 transmits event selection information including the processing code of the selected event to be linked to the due date management support server 20.

  When the due date management support server 20 acquires the event selection information (“YES” in step S1-8), the control unit 21 of the due date management support server 20 executes a period information registration process (step S1-9). ). Specifically, the event registration unit 212 of the control unit 21 records the processing code of the event to be linked selected on the client terminal 10 in the periodic data area of the event management record 230. If no event is selected and the content of the period setting field is changed (in the case of “NO” in step S1-8), the event registration unit 212 of the control unit 21 starts over from the processing from step S1-3. .

  Next, the control unit 21 of the due date management support server 20 executes a subordinate order assignment process (step S1-10). Specifically, the event registration unit 212 of the control unit 21 acquires the priority order recorded in the event management record 230 to be linked. Then, the event registration unit 212 records the rank obtained by lowering the priority of the event to be linked by one in the priority data area of the event management record 230 to be registered.

  Then, the control unit 21 of the due date management support server 20 executes registration processing for the scheduled processing date (step S1-11). Specifically, the event registration unit 212 of the control unit 21 acquires information on the event to be linked from the client terminal 10 through the scheduled processing date setting field on the event registration screen. Then, the event registration unit 212 records the “number of shift days” in the scheduled processing date data area of the event management record 230.

  In this manner, the processing from step S1-2 is repeated until registration completion instructions for all events are received from the client terminal 10 ("NO" in step S1-12). When the event registration completion instruction is received from the client terminal 10 (in the case of “YES” in step S1-12), the cycle information registration process is terminated.

(Schedule expansion process)
Next, the schedule development process will be described with reference to FIG. This schedule expansion process is executed when the due date management support server 20 receives a schedule expansion instruction in which a case code is specified.

  First, the control unit 21 of the due date management support server 20 executes a process of specifying the rank to be developed first (step S2-1). Specifically, when receiving a schedule expansion instruction from the client terminal 10, the schedule expansion unit 213 of the control unit 21 specifies the first rank as the rank to be expanded first. On the other hand, when a schedule expansion instruction is received from a schedule change unit 215 to be described later, the priority of the event of the processing code acquired from the schedule change unit 215 is specified as the first expansion order.

  And the control part 21 of the date management support server 20 performs the specific process of the event of this order | rank (step S2-2). Specifically, the schedule development unit 213 of the control unit 21 extracts from the event management database 23 an event management record 230 in which a designated item code is recorded. Then, the schedule development unit 213 identifies all event management records 230 in which the priority order of the deployment targets is recorded in the extracted event management records 230.

Then, the control unit 21 of the due date management support server 20 repeatedly executes the following processing for each event of the identified event management record 230.
Here, the control unit 21 of the due date management support server 20 executes an event-linked necessity determination process (step S2-3). Specifically, the schedule development unit 213 of the control unit 21 uses the periodic data area of the event management record 230 to check the presence / absence of an event to be linked. When the processing code of the preceding event is not recorded in the event management record 230 (when “NO” in step S2-3), the control unit 21 of the due date management support server 20 calculates the due date based on the scheduled processing date. Processing is executed (step S2-4). Specifically, the schedule development unit 213 of the control unit 21 calculates a calendar date (year / month / day) from the scheduled processing date to the end date based on the period recorded in the event management record 230.

  On the other hand, when the processing code of the preceding event is recorded in the event management record 230 (in the case of “YES” in step S2-3), the control unit 21 of the due date management support server 20 determines the processing due date based on the interlocking target. Calculation processing is executed (step S2-5). Specifically, the schedule development unit 213 of the control unit 21 specifies the processing code of the interlocked event recorded in the event management record 230. Then, from the due date management database 24, the due date management record 240 in which the schedule development target case code and the specified processing code are recorded is extracted. Then, the schedule expansion means 213 adds the shift days recorded in the event management record 230 to the processing date (preceding date) recorded in the date management record 240, and the calendar date ( (Year / month / day) is calculated until the end date.

  Next, the control unit 21 of the due date management support server 20 executes holiday correction processing (step S2-6). Specifically, when the calendar date is registered as a business day in the calendar database 25, the schedule expanding unit 213 sets the calendar date as a processing due date. On the other hand, when the calendar date is registered as a closed day in the calendar database 25, the schedule expansion unit 213 calculates a processing date corresponding to the calendar date based on the holiday correction data.

Then, the control unit 21 of the due date management support server 20 executes a process due date registration process (step S2-7). Specifically, the schedule development unit 213 of the control unit 21 generates a date management record 240 in which data relating to a case code, a case name, a processing record, and a processing date is recorded, and registers it in the date management database 24. At this stage, the confirmation flag data area and the completion flag data area of the due date management record 240 are left blank.

Then, the process date calculation process is repeated for each event in this order.
Next, the control unit 21 of the due date management support server 20 executes a subordinate order confirmation process (step S2-8). Specifically, the schedule development unit 213 of the control unit 21 confirms whether there is an event management record 230 to which a priority lower than the order in which the processing dates are calculated is present. Here, when the lower-level event management record 230 exists (in the case of “YES” in step S2-8), the control unit 21 of the due date management support server 20 executes the process of specifying the rank of the deployment target (step S2-8). S2-9). Specifically, the schedule development unit 213 of the control unit 21 specifies the order with the next lowest priority registered in the event management record 230 as the order to be developed. Then, when the calculation of the processing dates for all priorities is completed (in the case of “NO” in step S2-8), the schedule development processing is terminated.

(Schedule output process)
Next, the schedule output process will be described with reference to FIG. This schedule output process is executed when the due date management support server 20 receives a schedule confirmation instruction input from the client terminal 10 by a person in charge of paperwork or an administrator.

  First, the control unit 21 of the due date management support server 20 executes a search process for the current day schedule (step S3-1). Specifically, the schedule output unit 214 of the control unit 21 specifies the current date using a system timer. Then, the schedule output unit 214 searches the due date management database 24 for the due date management record 240 in which the current date is registered as the processing due date.

  Here, when the existence of the schedule is detected by extracting the due date management record 240 in which the current date is recorded (when “YES” in step S3-2), the control unit 21 of the due date management support server 20 A search process for preceding events is executed (step S3-3). Specifically, the schedule output unit 214 of the control unit 21 uses the periodic data area of the event management record 230 to check whether there is a preceding event to be linked.

  Here, when the processing code of the preceding event is recorded in the event management record 230 (in the case of “YES” in step S3-4), the control unit 21 of the due date management support server 20 confirms the completion of the preceding paper processing. Is executed (step S3-5). Specifically, the schedule output unit 214 of the control unit 21 uses the due date management database 24 to record the same case code and the processing code of the preceding event, and the latest processing due date before the current date. The due date management record 240 is specified. Then, the schedule output unit 214 confirms whether or not a completion flag is recorded in the due date management record 240.

  When it is determined that the completion flag is not recorded in the due date management record 240 and the paperwork of the preceding event has not been completed (in the case of “NO” in step S3-5), the control unit of the due date management support server 20 21 executes an alarm output process (step S3-6). Specifically, the schedule output unit 214 of the control unit 21 notifies the client terminal 10 that the paperwork of the preceding event has not ended.

And the control part 21 of the date management support server 20 performs the output process of a schedule (step S3-7). Specifically, the schedule output unit 214 of the control unit 21 creates a schedule list in which events to be processed on the day are listed, and the client terminal 1
Send to 0. It should be noted that when the preceding event processing code is not recorded in the event management record 230 (in the case of “NO” in step S3-4), or when it is determined that the prior event paperwork has been completed (step S3). In the case of “YES” in −5), the process in the middle is skipped and this schedule output process is executed.

  Then, a schedule list is output on the display of the client terminal 10. When the schedule list is confirmed, the person in charge of paperwork performs confirmation input on the client terminal 10. In this case, the client terminal transmits a confirmation notification to the due date management support server 20. Then, the control unit 21 of the due date management support server 20 records a confirmation flag in the due date management record 240 of the event included in the schedule list.

  Then, when the paperwork person completes the paperwork, the event that completed the paperwork is identified in the schedule list output on the display of the client terminal 10, and the reception number given when the paperwork is executed is set And complete input. In this case, the client terminal 10 transmits a completion notification to the due date management support server 20. This completion notification includes the processing code for completing the paperwork and data regarding the receipt number assigned when the paperwork is executed.

  When the control unit 21 of the due date management support server 20 receives the completion notification (in the case of “YES” in step S3-8), the control unit 21 of the due date management support server 20 performs a completion flag recording process. (Step S3-9). Specifically, the control unit 21 records the reception number and the completion flag in the due date management record 240 in which the processing code included in the completion notification is recorded.

(Schedule change process)
Next, the schedule change process will be described with reference to FIG. This schedule change process is executed when the due date management support server 20 receives a schedule change request input by the person in charge of registration from the client terminal 10.

  First, the control unit 21 of the due date management support server 20 executes a process for specifying an event to be changed (step S4-1). Specifically, the schedule changing unit 215 of the control unit 21 acquires data relating to the schedule change target case code and processing code from the client terminal 10.

  And the control part 21 of the date management support server 20 performs the deletion process of the future schedule of change object (step S4-2). Specifically, the schedule changing unit 215 of the control unit 21 specifies the due date management record 240 in which the identified case code and processing code are recorded in the due date management database 24. Then, the schedule changing unit 215 acquires the current date from the system timer, and deletes the due date management record 240 in which the future processing due date is recorded with respect to this current date from the due date management database 24.

  Next, the control unit 21 of the due date management support server 20 executes a lower-order event specifying process associated with the event to be changed (step S4-3). Specifically, the schedule changing unit 215 of the control unit 21 searches the event management record 230 in which the processing code to be changed is recorded as the interlocking target in the periodic data area.

  Due to the presence of such event management record 230, when a lower-order event is registered (in the case of “YES” in step S 4-4), the due date management support server 20 performs the same as in step S 4-2. The control unit 21 executes a future schedule deletion process for the lower-order event (step S4-5).

  Further, the control unit 21 of the due date management support server 20 executes a process for specifying a lower-order event associated with this event, similarly to step S4-3 (step S4-6).

  When the event to be changed and the lower-order event are no longer registered (in the case of “NO” in step S4-4), the control unit 21 of the due date management support server 20 executes schedule expansion processing ( Step S4-7). Specifically, the schedule changing unit 215 of the control unit 21 outputs a schedule development instruction to the schedule development unit 213. This schedule development instruction includes data relating to the schedule change target item code and processing code. In this case, the schedule expansion unit 213 of the control unit 21 executes the above-described schedule expansion process for events of the priority order or lower specified by the case code and the process code.

As described above, according to the present embodiment, the following effects can be obtained.
In the above embodiment, the event management database 23 records the event management record 230 in which the event included in the matter is registered. This event management record 230 is configured to include data relating to a case code, a processing code, an initial date, a cycle, a scheduled processing date, and a priority order. When the event is linked to another event, the processing code of the event to be linked is registered as cycle information in the cycle data area. In the scheduled processing date data area, the number of days to be shifted with respect to the due date of the event to be linked (for example, “3 business days later”) is recorded. Then, in the schedule development process, when the process code of the preceding event is recorded in the event management record 230 (in the case of “YES” in step S2-3), the control unit 21 of the due date management support server 20 is set as the interlock target. Based on this, the processing date calculation process is executed (step S2-5). As a result, an event schedule linked to other events can be registered. In particular, in the management of liquidated assets, due dates of subsequent events may be determined in conjunction with preceding events, but this system can flexibly set due dates for various events. it can.

  In the above embodiment, the event management record 230 is configured to include data related to priority. Then, the control unit 21 of the due date management support server 20 performs schedule expansion sequentially from the higher rank (step S2-9). Here, since events that are not linked to other events are set in the first order, the schedule can be expanded sequentially from the event whose due date is determined by the calendar.

  In the above embodiment, the event management record 230 includes data related to holiday correction. Then, the control unit 21 of the due date management support server 20 executes holiday correction processing (step S2-6). Thereby, the due date for carrying out the paperwork can be set as a business day.

  In the above embodiment, in the schedule output process, the control unit 21 of the due date management support server 20 executes a search process for a preceding event (step S3-3). When the preceding event processing code is recorded in the event management record 230 (in the case of “YES” in step S3-4), the control unit 21 of the due date management support server 20 performs the preceding office processing completion confirmation processing. Execute (Step S3-5). As a result, the schedule of the next subsequent event can be output while confirming the completion of the paperwork for the preceding event to be linked. In particular, even in the management of securitized assets where the context of paperwork is important, accurate business management can be performed.

In the above embodiment, in the schedule change process, a process for deleting the future schedule to be changed is executed (step S4-2). Further, the control unit 21 of the due date management support server 20 identifies the lower order event associated with the event to be changed, and the lower order event is registered (in the case of “YES” in step S4-4). ), The process of deleting the future schedule of the lower order event is executed (step S4-5). Then, the schedule expansion process is executed again. As a result, when one event is changed, other schedule events can be changed together.

In addition, you may change the said embodiment into the following aspects.
In the above embodiment, the due date management support process is applied to the due date management of the liquidated asset, but the application field is not limited to this.

  In the above embodiment, the schedule expansion process is executed using the priority order. Instead of this, it is also possible to execute the schedule development process using the link information for other events. This process will be described with reference to FIG. Here, the following processing is repeatedly executed until the schedule is developed for all events regardless of the priority order. Here, an expanded flag indicating that the schedule has been expanded is recorded in the event management record 230 of the event management database 23 instead of the priority order.

  First, the control unit 21 of the due date management support server 20 executes a process for specifying an event that is a schedule development target (step S5-1). Specifically, the schedule development unit 213 of the control unit 21 uses the developed flag to identify the event management record 230 that has not been scheduled yet.

  Then, the control unit 21 of the due date management support server 20 executes a confirmation process as to whether or not the event specified as the deployment target is linked to another event (step S5-2). Specifically, the schedule development unit 213 of the control unit 21 makes a determination using the processing code recorded in the periodic data area of the event management record 230. When the event to be expanded is linked to another event (in the case of “YES” in step S5-2), the control unit 21 of the due date management support server 20 confirms whether or not the event to be linked has been expanded in schedule. Is executed (step S5-3). Specifically, it is determined by whether or not the expanded flag in the event management record 230 of the event to be linked is recorded.

  Here, when the event to be linked has not yet been developed in the schedule (in the case of “NO” in step S5-3), the control unit 21 of the due date management support server 20 postpones the schedule development of this event ( Step S5-4).

  On the other hand, when the event to be expanded is not linked to other events (in the case of “NO” in step S5-2), or the event to be linked has already been expanded in the schedule (“YES” in step S5-3). ), The control unit 21 of the due date management support server 20 executes a schedule expansion process for the event to be expanded (step S5-5). Specifically, the schedule development unit 213 of the control unit 21 calculates the due date in the same manner as in steps S2-4 and S2-5, and executes holiday correction processing in the same manner as in step S2-6. Here, when the schedule is expanded, the expanded flag is recorded in the event management record 230 of this event.

  The process is repeatedly executed until the schedule is developed for all events (“NO” in step S5-6). As a result, schedule development can be performed for linked events without using priority.

In the above embodiment, in step S2-4 and step S2-5, the processing date is calculated using the cycle and the scheduled processing date recorded in the event management record 230. In this case, for foreign projects, it is possible to consider a business day table that takes into account the local calendar and time differences. Specifically, the target country in which the country for which the due date management of this case is recorded is registered in the case management database 22 and the event management database 23 of the due date management support server 20 for the case code and the processing code. Further, the due date management support server 20 is provided with a country management information storage unit that holds a country-specific business day table and a time difference table. And the control part 21 of the due date management support server 20 specifies the country which performs due date management based on the case code. Then, the control unit 21 acquires the time difference between the local time of this country and the time of the system timer from the time difference table, and adds the time difference to the calculated processing date. In this case, the control unit 21 performs holiday correction using a local business day table. As a result, for international events, the processing date can be set in consideration of the local time and business days.

The system schematic of embodiment of this invention. It is explanatory drawing of the data recorded on each database, (a) is a case management database, (b) is an event management database, (c) is explanatory drawing of the data recorded on the due date management database. Explanatory drawing of the process sequence of this embodiment of this invention. Explanatory drawing of the process sequence of this embodiment of this invention. Explanatory drawing of the process sequence of this embodiment of this invention. Explanatory drawing of the process sequence of this embodiment of this invention. Explanatory drawing of the process sequence of other embodiment of this invention.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Client terminal, 20 ... Due date management support server, 21 ... Control part, 211 ... Case registration means, 212 ... Event registration means, 213 ... Schedule expansion means, 214 ... Schedule output means, 215 ... Schedule change means, 22 ... Case Management database, 23 ... event management database, 24 ... due date management database, 25 ... calendar database.

Claims (5)

Event information storage means that records an event management record that associates the event identifier of the preceding event with the difference date between the due date of the preceding event and the event identifier;
Due date information storage means for recording a due date management record that records a processing due date for the event identifier;
A date management support processing system provided with a control means for calculating an event processing date,
The control means is
In event setting, an event registration unit that acquires a preceding event to be associated with this event and a difference day number between the due date of the preceding event and records it in the event information storage unit;
When performing schedule expansion for an event, obtain the preceding due date that was scheduled for the preceding event,
A schedule expansion unit that calculates a date obtained by adding the difference days to the preceding date, and records the date as a processing date of the event in the date information storage unit;
A date management support processing system comprising: schedule output means for outputting a processing date recorded in the date information storage means. In the event information storage means, a priority order is recorded for each event identifier,
2. The event registration unit records an event associated with a preceding event in the event information storage unit by assigning the next priority of the priority given to the preceding event. Due date management support processing system. In the date information storage means, a completion flag is recorded for each event for which processing has ended,
When outputting the processing due date of the event that has reached the due date, the schedule output means identifies the preceding event of this event, and records a completion flag for the event identifier of the preceding event in the due date storage means. 3. The due date management support processing system according to claim 1, wherein an alarm is output when the date is not set. Event information storage means that records an event management record that associates the event identifier of the preceding event with the difference date between the due date of the preceding event and the event identifier;
Due date information storage means for recording a due date management record that records a processing due date for the event identifier;
A method for performing due date management support processing using a due date management support processing system provided with a control means for calculating an event processing due date,
The control means is
In the event setting, an event registration stage for acquiring a preceding event to be associated with this event and a difference day between the due date of the preceding event and recording it in the event information storage means;
When performing schedule expansion for an event, obtain the preceding due date that was scheduled for the preceding event,
A schedule expansion stage that calculates a date by adding the difference days to the preceding due date, and records it in the due date information storage means as a processing due date of the event;
And a schedule output step of outputting a processing date recorded in the date information storage means. Event information storage means that records an event management record that associates the event identifier of the preceding event with the difference date between the due date of the preceding event and the event identifier;
Due date information storage means for recording a due date management record that records a processing due date for the event identifier;
A program for performing due date management support processing using a due date management support processing system provided with a control means for calculating an event processing due date,
The control means;
In event setting, an event registration means for acquiring a preceding event to be associated with this event and a difference number of days from the due date of the preceding event, and recording it in the event information storage means,
When performing schedule expansion for an event, obtain the preceding due date that was scheduled for the preceding event,
A schedule expansion unit that calculates a date obtained by adding the difference days to the preceding date, and records the date as a processing date of the event in the date information storage unit;
A due date management support processing program which functions as a schedule output means for outputting a process due date recorded in the due date information storage means.

Images