JPH1131179A - Method and device for managing inter-company transaction progress - Google Patents

Method and device for managing inter-company transaction progress

Info

Publication number
JPH1131179A
JPH1131179A JP18791197A JP18791197A JPH1131179A JP H1131179 A JPH1131179 A JP H1131179A JP 18791197 A JP18791197 A JP 18791197A JP 18791197 A JP18791197 A JP 18791197A JP H1131179 A JPH1131179 A JP H1131179A
Authority
JP
Japan
Prior art keywords
date
progress
schedule
work
company
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP18791197A
Other languages
Japanese (ja)
Other versions
JP4312846B2 (en
Inventor
Tsuyoshi Miyake
強志 三宅
Hiromitsu Shiina
洋充 椎名
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Priority to JP18791197A priority Critical patent/JP4312846B2/en
Priority to TW087104638A priority patent/TW432305B/en
Priority to SG9800665A priority patent/SG79964A1/en
Priority to US09/050,064 priority patent/US6049787A/en
Priority to KR1019980011240A priority patent/KR100282750B1/en
Publication of JPH1131179A publication Critical patent/JPH1131179A/en
Priority to US10/095,058 priority patent/US20020095381A1/en
Priority to US10/915,566 priority patent/US7428511B2/en
Priority to US12/219,799 priority patent/US7590597B2/en
Application granted granted Critical
Publication of JP4312846B2 publication Critical patent/JP4312846B2/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Classifications

    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30Computing systems specially adapted for manufacturing

Landscapes

  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • General Factory Administration (AREA)

Abstract

PROBLEM TO BE SOLVED: To perform progress management of transaction or a project in which plural companies work together and participate in accordance with the time of deliver when final products are delivered to a customer. SOLUTION: A relaying part 22 of a server 11 relays transaction information sent from a transaction information sending terminal 12 of a certain company to a transaction information receiving terminal 13. An inter-company progress managing part 24 expands it into a work schedule that consists of plural work processes and stores it in a progress state database 21 when it receives merchandise order information from the part 22. When the actual results report of a related work process is acquired through the part 22 and a receiving part 23, actual results date is recorded on the schedule and when it is later than a scheduled date, changed date about a subsequent work process is recorded. A retrieving part 27 fetches corresponding progress state from the database 21 in response to an inquiry from a progress state inquiring terminal 14 and sends it to the terminal 14 via an editing part 28 and an outputting part 29.

Description

【発明の詳細な説明】DETAILED DESCRIPTION OF THE INVENTION

【0001】[0001]

【発明の属する技術分野】本発明は、コンピュータを利
用する取引の進捗管理方法および装置に係わり、特に企
業間に伝送される取引情報を基にして複数企業が関与す
る作業スケジュールの進捗管理を行う方法および装置に
関する。
BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and apparatus for managing the progress of a transaction using a computer, and more particularly to the progress management of a work schedule involving a plurality of companies based on transaction information transmitted between the companies. Method and apparatus.

【0002】[0002]

【従来の技術】コンピュータを利用する単一企業内の生
産管理やプロジェクトの工程管理は多くの企業で実施さ
れ、その技術は良く知られている。例えば特開平7−1
29667号公報は、プロジェクトを管理する業務の工
程管理方法を開示する。
2. Description of the Related Art Production management and project process management within a single company using a computer are carried out by many companies, and the technology is well known. For example, JP-A-7-1
Japanese Patent Publication No. 29667 discloses a process management method of a business for managing a project.

【0003】[0003]

【発明が解決しようとする課題】顧客に最終製品を納入
するときの納期に合わせて部品の製造と出荷、装置の組
立と出荷など最終製品を納入するまでの間に複数企業の
連動を必要とする商品がある。このように最上流の作業
工程から最終製品の納入に至るまで複数の企業が一連の
納期条件の下に関与するような取引あるいはプロジェク
トの進捗管理をする場合には、従来の同一企業内の工程
管理技術をそのまま適用することはできない。すなわち
このような企業間取引の進捗管理をするサーバが関連す
る企業の企業内サーバにアクセスして生産管理や在庫管
理のデータを引き出すことは困難であるし、企業による
データ形式やコード体系の相違から目的とする取引又は
プロジェクトの進捗管理のために有用なデータを収集す
ることはさらに困難である。このような事情によって従
来発注した商品についてどの企業までの作業が終了して
いて予定に対して遅れがないか否かを把握することが困
難であった。
[Problem to be Solved by the Invention] It is necessary to link a plurality of companies until the final product is delivered, such as manufacturing and shipping parts, assembling and shipping equipment, according to the delivery date when delivering the final product to the customer. There are products to do. In this way, when managing the progress of a transaction or project in which multiple companies are involved under a series of delivery conditions from the highest-level work process to the delivery of the final product, the conventional process within the same company Management technology cannot be applied directly. In other words, it is difficult for the server that manages the progress of such inter-company transactions to access the in-company server of the related company to extract the data of production management and inventory management, and differences in data formats and code systems between companies. It is even more difficult to collect useful data for managing the progress of a target transaction or project from a company. Under such circumstances, it has been difficult to determine which company has completed the work on the previously ordered product and whether there is any delay with respect to the schedule.

【0004】本発明の目的は、上記従来の問題点を解決
することにあり、複数企業が関与する取引の進捗管理を
する方法および装置を提供することにある。
[0004] An object of the present invention is to solve the above-mentioned conventional problems and to provide a method and apparatus for managing the progress of a transaction involving a plurality of companies.

【0005】[0005]

【課題を解決するための手段】本発明は、ネットワーク
を介して企業間に伝送される取引情報を取得し、この取
引情報を基にして複数の企業に亘る複数の作業工程と完
了予定日を含む作業スケジュールに展開し、この作業工
程について作業の実績報告を取得したとき作業スケジュ
ールに実績日を記録し、実績日が完了予定日より遅れた
とき遅れ日数に応じて後続の作業工程の完了予定日を修
正する変更日をスケジュールに記録する企業間の取引進
捗管理方法および装置を特徴とする。ここで作業の実績
報告は、展開された複数の作業工程のうちの1つに対応
付けできるものとし、その作業完了予定日と報告された
実績日を比較できるものとする。
SUMMARY OF THE INVENTION The present invention acquires transaction information transmitted between companies via a network, and based on the transaction information, determines a plurality of work processes and a scheduled completion date across a plurality of companies. Expand to the work schedule including the work schedule, record the actual date in the work schedule when acquiring the performance report of the work for this work process, and when the actual date is later than the scheduled completion date, plan the completion of the subsequent work process according to the number of days delayed The present invention is characterized by a method and an apparatus for managing the progress of transactions between companies that record a change date for correcting a date in a schedule. Here, it is assumed that the work result report can be associated with one of a plurality of developed work processes, and that the scheduled work completion date can be compared with the reported work date.

【0006】[0006]

【発明の実施の形態】以下、本発明の一実施形態につい
て図面を用いて説明する。
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below with reference to the drawings.

【0007】図1は、本実施形態の進捗管理システムの
構成図である。システムはサーバ11と、ネットワーク
15を介してサーバ11に接続され、クライアントとな
る取引情報送信端末12、取引情報受信端末13及び進
捗状況照会端末14から構成される。取引情報送信端末
12は、一方の企業に設置され、ネットワーク15を介
してサーバ11へ取引情報を送信する。取引情報受信端
末13は、他の企業に設置され、ネットワーク15を介
してサーバ11から取引情報を受信する。サーバ11
は、取引情報送信端末12から受信した商品の発注に関
する取引情報を取引情報受信端末13へ中継するととも
に商品の製造から納入までの作業の進捗状況テーブルを
作成し、その進捗状況を管理する。進捗状況照会端末1
4は、ネットワーク15を介してサーバ11へ特定の商
品発注についてその進捗状況を問い合わせ、進捗状況デ
ータを取得する。
FIG. 1 is a configuration diagram of the progress management system of the present embodiment. The system is composed of a server 11, a transaction information transmitting terminal 12, a transaction information receiving terminal 13, and a progress status inquiry terminal 14 which are connected to the server 11 via a network 15 and serve as clients. The transaction information transmission terminal 12 is installed in one company and transmits transaction information to the server 11 via the network 15. The transaction information receiving terminal 13 is installed in another company, and receives transaction information from the server 11 via the network 15. Server 11
Relays the transaction information relating to the ordering of the product received from the transaction information transmitting terminal 12 to the transaction information receiving terminal 13, creates a progress table of the work from production to delivery of the product, and manages the progress. Progress inquiry terminal 1
4 inquires of the server 11 via the network 15 about the progress of a specific product order, and acquires progress data.

【0008】取引情報送信端末12、取引情報受信端末
13及び進捗状況照会端末14は、パーソナルコンピュ
ータ等の情報処理装置である。各端末装置の名称はその
情報処理装置で実行されるアプリケーションプログラム
(AP)の機能を表しているので、1台の情報処理装置
がこれら端末の2つ以上の機能を備えることが可能であ
る。サーバ11は、パソコン、ワークステーション、メ
インフレームコンピュータ、並列計算機等の情報処理装
置である。ネットワーク15は、複数企業間で利用でき
るインターネット、VAN業者が提供する専用線などの
ネットワークである。
[0008] The transaction information transmitting terminal 12, the transaction information receiving terminal 13, and the progress inquiry terminal 14 are information processing devices such as personal computers. Since the name of each terminal device indicates a function of an application program (AP) executed by the information processing device, one information processing device can have two or more functions of these terminals. The server 11 is an information processing device such as a personal computer, a workstation, a mainframe computer, and a parallel computer. The network 15 is a network such as the Internet that can be used between a plurality of companies and a dedicated line provided by a VAN company.

【0009】図2は、サーバ11が保持するデータベー
ス及び機能モジュールの構成を示す図である。進捗状況
データベース21は、企業間の商品の発注を元にして複
数の企業に亘る製品の製造、出荷、納入などの作業の進
捗状況のデータを格納する。中継部22は、取引情報送
信端末12から受信した取引情報を取引情報受信端末1
3へ中継するとともに企業間進捗管理部24に渡す。な
お取引情報送信端末12は、同報通信によって同一の取
引情報を取引情報受信端末13とサーバ11の両方に送
信してもよい。その場合には中継部22は、取引情報の
単なる受信部となる。受信部23は、取引情報送信端末
12などの送信端末から受信した作業実績データを企業
間進捗管理部24に渡す。企業間進捗管理部24は、中
継部22から受けた商品の発注取引情報を進捗状況テー
ブルの形式に展開して進捗状況データベース21に格納
する処理部である。また企業間進捗管理部24は、中継
部22又は受信部23から受けた取引情報又は作業実績
データによって進捗状況データベース21の該当する進
捗状況テーブルを更新する。その結果として作業スケジ
ュールに遅れが生じる場合に、アラーム/作業指示送信
部25は関連企業の取引情報受信端末13などの受信端
末へアラームまたは作業指示を送信する。受付部26
は、進捗状況照会端末14から取引の進捗状況照会を受
信する処理部である。検索部27は、進捗状況データベ
ース21を検索して該当する進捗状況テーブルを取得す
る処理部である。編集部28は、取得した進捗状況テー
ブルを編集する処理部である。出力部29は、作成した
進捗状況データを進捗状況照会端末14へ送信する処理
部である。なお上記機能モジュールを含むAPを記憶媒
体に格納し、サーバ11がこの記憶媒体上のAPを読み
取って実行することが可能である。
FIG. 2 is a diagram showing the configuration of the database and functional modules held by the server 11. The progress database 21 stores data on the progress of operations such as manufacturing, shipping, and delivery of products across a plurality of companies based on orders for products between companies. The relay unit 22 transmits the transaction information received from the transaction information transmitting terminal 12 to the transaction information receiving terminal 1.
3 and handover to the inter-company progress management unit 24. The transaction information transmitting terminal 12 may transmit the same transaction information to both the transaction information receiving terminal 13 and the server 11 by broadcasting. In that case, the relay unit 22 is merely a receiving unit of the transaction information. The receiving unit 23 passes the work result data received from the transmitting terminal such as the transaction information transmitting terminal 12 to the inter-company progress management unit 24. The inter-company progress management unit 24 is a processing unit that develops the order transaction information of the product received from the relay unit 22 into a progress table format and stores the information in the progress database 21. The inter-company progress management unit 24 updates the corresponding progress table in the progress database 21 with the transaction information or work result data received from the relay unit 22 or the receiving unit 23. If the work schedule is delayed as a result, the alarm / work instruction transmitting unit 25 transmits an alarm or a work instruction to a receiving terminal such as the transaction information receiving terminal 13 of the related company. Reception unit 26
Is a processing unit that receives a transaction progress inquiry from the progress inquiry terminal 14. The search unit 27 is a processing unit that searches the progress status database 21 and acquires a corresponding progress status table. The editing unit 28 is a processing unit that edits the obtained progress status table. The output unit 29 is a processing unit that transmits the created progress data to the progress inquiry terminal 14. Note that it is possible to store the AP including the functional module in a storage medium, and the server 11 can read and execute the AP on the storage medium.

【0010】図3は、取引情報送信端末12から取引情
報受信端末13へ送信される取引情報35のデータ例を
示す図である。図3(a)は、A社からX社へ送信され
る発注情報であり、商品番号、数量、納期、発注者、受
注者及び発注番号から成る。図3(b)は、C社からY
社へ送信される出荷情報であり、商品番号、数量、納
期、発注者、受注者、発注番号、出荷番号及び実際の出
荷日から成る。なお取引情報の書式としてCIIシンタ
ックスルール、EDIFACTのような標準書式に準拠
することができる。また発注番号や商品番号などは企業
間のコード体系の統一基準に従って統一されているもの
とする。
FIG. 3 is a diagram showing an example of data of the transaction information 35 transmitted from the transaction information transmitting terminal 12 to the transaction information receiving terminal 13. FIG. 3A shows order information transmitted from Company A to Company X, which includes a product number, a quantity, a delivery date, an orderer, a contractor, and an order number. FIG. 3 (b) shows that the company C
This is shipping information transmitted to the company, and is composed of a product number, quantity, delivery date, orderer, orderer, order number, shipping number, and actual shipping date. The format of the transaction information can be based on a standard format such as CII syntax rule and EDIFACT. It is also assumed that order numbers, product numbers, and the like are unified according to the unified standard of the code system between companies.

【0011】図4は、進捗状況データベース21に格納
される進捗状況データの構成を示す図である。進捗状況
データは、各商品発注について関連する企業の作業の順
に進捗状況を示すスケジュール・テーブルである。テー
ブルは列方向に発注番号、企業名、作業名、作業完了予
定日、作業実績日及び作業変更日を配列し、行方向に同
一商品発注に係わる各企業の作業とその進捗状況を作業
順に配列する。企業名は単独の企業名又は企業間取引に
係わる2つの企業名を示す。発注番号、企業名、作業名
及び作業完了予定日は、最初の商品発注のとき作業展開
によって設定されたデータである。作業実績日及び作業
変更日は、企業の実績報告又は取引情報35によって格
納されるデータである。作業変更日は実績報告のあった
作業工程より後続の作業工程の作業完了予定日を修正す
るものである。例えばC社からY社への出荷についてそ
の作業実績日は、C社からY社への取引情報35から抽
出されたものである。各作業について付加されているア
ラーム及び作業指示は、作業遅れに伴って後続の作業を
担当する企業へ送信されるアラーム及び作業指示を示し
ている。図4の例は、C社からY社への出荷が1日遅れ
たために、Y社からB社への納入が1日遅れ、その結果
として仕向先の企業であるB社へ「納入遅れ」を警告す
ることを示している。またB社の製造スケジュールを変
更する代わりにB社へ「リードタイム短縮」を指示する
ことを示している。またB社からX社への出荷が遅れる
恐れがあるので、X社へ「緊急出荷」を指示し、X社か
らA社への出荷が遅れる恐れがあるので、A社へ「納入
遅れのおそれあり」を警告することを示している。アラ
ーム及び作業指示の内容は、作業の種類と遅れ日数に応
じてパターンを用意する。アラーム及び作業指示を進捗
状況データベース21に登録する必要はないが、各作業
に対応して発生するので便宜的に各作業の進捗状況と並
列して示した。
FIG. 4 is a diagram showing a configuration of the progress data stored in the progress database 21. The progress data is a schedule table showing the progress in the order of the work of the company related to each product order. The table arranges the order number, company name, work name, scheduled work completion date, actual work date and work change date in the column direction, and arranges the work of each company involved in the same product order and its progress in the work order in the row direction. I do. The company name indicates a single company name or two company names involved in an inter-company transaction. The order number, the company name, the work name, and the scheduled work completion date are data set by work development when the first product order is placed. The actual work date and the work change date are data stored by the company's performance report or the transaction information 35. The work change date is for correcting the scheduled work completion date of the work process subsequent to the work process for which the performance report was made. For example, the actual work date of shipment from Company C to Company Y is extracted from transaction information 35 from Company C to Company Y. The alarm and the work instruction added to each work indicate the alarm and the work instruction transmitted to the company in charge of the subsequent work due to the work delay. In the example of FIG. 4, the delivery from Company C to Company Y is delayed by one day, so the delivery from Company Y to Company B is delayed by one day, and as a result, “delivery delayed” to Company B, the destination company. Indicates that the warning. In addition, it indicates that the company B is instructed to “reduce the lead time” instead of changing the manufacturing schedule of the company B. In addition, there is a possibility that the shipment from Company B to Company X may be delayed. Therefore, "Emergency shipment" is instructed to Company X, and the shipment from Company X to Company A may be delayed. Yes "is indicated. A pattern is prepared for the contents of the alarm and the work instruction according to the type of work and the number of days delayed. Although it is not necessary to register the alarm and the work instruction in the progress database 21, the alarm and the work instruction are generated in correspondence with each work, and therefore are shown in parallel with the progress of each work for convenience.

【0012】なおC社及びB社のような単独企業の製造
工程を設けずにC社−Y社及びB社−X社の出荷取引情
報によってその中に製造工程を含ませてもよい。「出
荷」は製造を伴う場合の商品の引き渡しを意味し、「納
入」は販売店や商社を経由するときのように製造を伴わ
ない場合の商品の引き渡しを意味している。なお図4の
例は作業工程が直列に接続される単純な例であるが、複
数の作業工程が並列して進行し、各企業で製造される部
品をアセンブルして最終製品を組み立てて発注者に納入
する複雑な作業スケジュールの場合も同様に1つの商品
発注を進捗状況テーブルに展開し、企業の実績報告又は
取引情報35によって作業実績日及び作業変更日を設定
可能である。
The manufacturing process may be included in the shipping transaction information of the company C-Y and the company B-X without providing the manufacturing process of a single company such as the company C and the company B. "Shipment" means delivery of a product in the case of production, and "delivery" means delivery of a product in the absence of production, such as when passing through a store or a trading company. Although the example of FIG. 4 is a simple example in which work steps are connected in series, a plurality of work steps proceed in parallel, assembling parts manufactured by each company, assembling a final product, and ordering the orderer. In the case of a complicated work schedule to be delivered to a company, similarly, one product order can be developed in the progress status table, and a work result date and a work change date can be set by a company result report or transaction information 35.

【0013】図5は、サーバ11の企業間進捗管理部2
4及びアラーム/作業指示送信部25の処理の流れを示
すフローチャートである。企業間進捗管理部24は、中
継部22又は受信部23から取引情報35又は作業実績
データを受信すると(ステップ51)、発注番号によっ
て進捗状況データベース21を検索し(ステップ5
2)、進捗状況データベース21に登録されていない新
規の商品発注の取引情報か否か判定する(ステップ5
3)。新規の商品発注であれば(ステップ53YE
S)、あらかじめ記憶装置に設定された企業名、作業名
及び標準作業日数をプロトタイプのスケジュールとして
作業展開し(ステップ54)、進捗状況データベース2
1に登録し(ステップ55)、処理を終了する。発注情
報に含まれる受注者−発注者を最後の納入作業又は出荷
作業の企業名として設定し、商品の納期が最後の納入作
業又は出荷作業の作業完了予定日として設定する。新規
の商品発注でなければ(ステップ53NO)、既登録の
商品発注の企業間取引情報又は作業実績報告かを判定す
る(ステップ56)。既発注商品の取引情報/実績報告
であれば(ステップ56YES)、進捗状況テーブルに
当該発注番号の該当する作業の作業実績日を設定し、そ
れによって作業完了予定日に変更が生じる場合にはその
遅れ日数に応じて作業変更日に変更日を設定する(ステ
ップ57)。次に作成した進捗状況テーブルによって進
捗状況データベース21を更新する(ステップ58)。
ステップ57の処理の結果、作業実績日が作業完了予定
日より遅れない場合には(ステップ59NO)、処理を
終了する。納期遅れが生じる場合には(ステップ59Y
ES)、制御はアラーム/作業指示送信部25に渡り、
アラーム/作業指示送信部25は、あらかじめ設定され
たアラーム及び作業指示のパターンに従って関連する企
業の受信端末へ発注番号、作業名、アラーム又は作業指
示を送信する(ステップ60)。送信端末から受信した
取引情報又は企業内情報が既登録の発注商品の進捗状況
に関係しないものであれば(ステップ56NO)、処理
を終了する。なお進捗状況テーブルの中に単独企業の製
造工程を設けない場合には、企業間進捗管理部24に入
力される情報に受信部23からの情報はなく、中継部2
2から入力される企業間取引情報だけである。
FIG. 5 shows an inter-company progress management section 2 of the server 11.
4 is a flowchart showing a flow of processing of an alarm / work instruction transmitting unit 25; Upon receiving the transaction information 35 or the work result data from the relay unit 22 or the receiving unit 23 (Step 51), the inter-company progress management unit 24 searches the progress database 21 based on the order number (Step 5).
2) It is determined whether or not the transaction information is for a new product order not registered in the progress database 21 (step 5).
3). If it is a new product order (step 53YE
S), work is developed as a prototype schedule using the company name, work name and standard work days preset in the storage device (step 54), and the progress database 2
1 (step 55), and the process ends. The orderer-orderer included in the ordering information is set as the company name of the last delivery work or shipping work, and the delivery date of the product is set as the scheduled completion date of the last delivery work or shipping work. If it is not a new product order (NO in step 53), it is determined whether the registered product order is inter-company transaction information or a work result report (step 56). If the transaction information / result report is for an already ordered product (YES in step 56), the actual work date of the work corresponding to the order number is set in the progress status table. A change date is set on the work change date according to the number of delay days (step 57). Next, the progress database 21 is updated with the created progress table (step 58).
As a result of the processing in step 57, if the actual work date is not later than the scheduled work completion date (step 59NO), the processing is ended. If the delivery date is delayed (step 59Y)
ES), control is passed to the alarm / work instruction transmitting unit 25,
The alarm / work instruction transmission unit 25 transmits the order number, the work name, the alarm or the work instruction to the receiving terminal of the related company in accordance with the preset alarm and work instruction pattern (step 60). If the transaction information or the in-company information received from the transmission terminal does not relate to the progress of the registered order product (NO in step 56), the process ends. When the manufacturing process of the single company is not provided in the progress status table, the information input to the inter-company progress management unit 24 does not include the information from the receiving unit 23, and the relay unit 2
Only the inter-company transaction information input from step 2.

【0014】なおステップ54の作業展開の際に部品の
在庫があり/なしに応じてそれぞれ別の作業プロトタイ
プを採用することができる。例えば図4に示す例でB社
が発注された商品の数量に見合う部品の在庫をもってい
るという情報が得られれば、作業プロトタイプはB社の
製造から開始すればよい。サーバ11はB社の最新の部
品在庫情報を保有するか、またはB社のサーバに問い合
わせて取得することができる。
It should be noted that different work prototypes can be employed depending on whether parts are in stock or not at the time of work development in step 54. For example, in the example shown in FIG. 4, if it is possible to obtain information that the company B has a stock of parts corresponding to the number of ordered products, the work prototype may be started from the manufacture of the company B. The server 11 can hold the latest component inventory information of the company B, or can obtain it by inquiring of the server of the company B.

【0015】図6は、進捗状況照会端末14からサーバ
11へ送信される進捗状況照会65のデータ例を示す図
である。進捗状況照会65は、発注番号、発注者、受注
者、納期のような情報から成る。
FIG. 6 is a diagram showing a data example of the progress status inquiry 65 transmitted from the progress status inquiry terminal 14 to the server 11. The progress status inquiry 65 includes information such as an order number, an orderer, a contractor, and a delivery date.

【0016】図7は、サーバ11から進捗状況照会端末
14へ送信される照会結果である進捗状況データ75の
データ例を示す図である。進捗状況データ75は、指定
された発注番号の進捗状況テーブルを人が見易い表の形
式に編集したものである。なお進捗状況データとして、
進捗状況テーブルを図形を用いて表現する工程管理図の
形式に編集することも可能である。
FIG. 7 is a diagram showing a data example of the progress data 75 which is an inquiry result transmitted from the server 11 to the progress inquiry terminal 14. The progress status data 75 is obtained by editing the progress status table of the designated order number into a table format that is easy for a person to see. As progress data,
It is also possible to edit the progress status table in the form of a process control chart that uses graphics to represent the progress table.

【0017】図8は、サーバ11の受付部26から出力
部29までの処理の流れを示すフローチャートである。
受付部26は進捗状況照会端末14から進捗状況照会6
5を受信し(ステップ81)、検索部27は進捗状況デ
ータベース21を検索して指定された発注番号の進捗状
況テーブルを取り出す(ステップ82)。編集部28は
取得した進捗状況テーブルを進捗状況データ75の形式
に編集し(ステップ83)、出力部29は作成した進捗
状況データ75を進捗状況照会端末14へ送信する(ス
テップ84)。
FIG. 8 is a flowchart showing the flow of processing from the receiving unit 26 to the output unit 29 of the server 11.
The receiving unit 26 sends a progress inquiry 6 from the progress inquiry terminal 14.
5 (step 81), the search unit 27 searches the progress database 21 and extracts the progress table of the designated order number (step 82). The editing unit 28 edits the acquired progress table into the format of the progress data 75 (step 83), and the output unit 29 transmits the created progress data 75 to the progress inquiry terminal 14 (step 84).

【0018】なおサーバ11が各取引情報送信端末12
から取引情報受信端末13へ伝送される取引情報をとら
えて進捗状況データベース21に進捗状況テーブルを登
録したり更新する代わりに、各企業の企業情報システム
内で取引情報送信端末12から送信された取引情報を企
業内サーバによって中継して取引情報受信端末13へ伝
送し、各企業の企業内サーバからサーバ11へ取引情報
を送信してもよい。
The server 11 is connected to each transaction information transmitting terminal 12
Instead of registering and updating the progress table in the progress database 21 by capturing the transaction information transmitted from the transaction information receiving terminal 13 to the transaction information receiving terminal 13, the transaction transmitted from the transaction information transmitting terminal 12 in the company information system of each company. The information may be relayed by a company server and transmitted to the transaction information receiving terminal 13, and the transaction information may be transmitted from the company server of each company to the server 11.

【0019】[0019]

【発明の効果】以上説明したように本発明によれば、複
数企業が関与する取引について統合的な進捗管理を行う
ので、その進捗状況を即座に把握できる。
As described above, according to the present invention, integrated progress management is performed for transactions involving a plurality of companies, so that the progress can be immediately grasped.

【図面の簡単な説明】[Brief description of the drawings]

【図1】実施形態のシステムの構成を示す図である。FIG. 1 is a diagram illustrating a configuration of a system according to an embodiment.

【図2】実施形態のサーバ11の内部構成を示す図であ
る。
FIG. 2 is a diagram illustrating an internal configuration of a server 11 according to the embodiment.

【図3】取引情報35のデータ例を示す図である。FIG. 3 is a diagram showing a data example of transaction information 35;

【図4】実施形態の進捗状況データベース21のデータ
構成を示す図である。
FIG. 4 is a diagram illustrating a data configuration of a progress database 21 according to the embodiment.

【図5】実施形態の企業間進捗管理部24及びアラーム
/作業指示送信部25の処理の流れを示すフローチャー
トである。
FIG. 5 is a flowchart showing a processing flow of an inter-company progress management unit 24 and an alarm / work instruction transmission unit 25 of the embodiment.

【図6】進捗状況照会65のデータ例を示す図である。FIG. 6 is a diagram showing a data example of a progress status inquiry 65;

【図7】進捗状況データ75のデータ例を示す図であ
る。
FIG. 7 is a diagram showing a data example of progress situation data 75;

【図8】実施形態の進捗状況照会処理の処理の流れを示
すフローチャートである。
FIG. 8 is a flowchart illustrating a flow of a progress inquiry process according to the embodiment;

【符号の説明】[Explanation of symbols]

11:サーバ、12:取引情報送信端末、13:取引情
報受信端末、14:進捗状況照会端末、21:進捗状況
データベース、24:企業間進捗管理部、35:取引情
11: server, 12: transaction information transmitting terminal, 13: transaction information receiving terminal, 14: progress inquiry terminal, 21: progress database, 24: inter-company progress management unit, 35: transaction information

Claims (8)

【特許請求の範囲】[Claims] 【請求項1】ネットワークを介して企業間に伝送される
取引情報を取得し、該取引情報を基にして複数の企業に
亘る複数の作業工程と完了予定日を含むスケジュールに
展開し、該作業工程について作業の実績報告を取得した
とき該スケジュールに実績日を記録し、実績日が完了予
定日より遅れたとき遅れ日数に応じて後続の作業工程の
完了予定日を修正する変更日を該スケジュールに記録す
ることを特徴とする企業間の取引進捗管理方法。
Claims 1. Transaction information transmitted between companies via a network is acquired, and based on the transaction information, the information is developed into a schedule including a plurality of work processes and a scheduled completion date across a plurality of companies. When a performance report of a process is acquired, the actual date is recorded in the schedule, and when the actual date is later than the scheduled completion date, the change date for correcting the scheduled completion date of the subsequent work process according to the number of days delayed is set in the schedule. A method for managing the progress of transactions between companies, characterized by recording the information in
【請求項2】該実績日が該完了予定日より遅れたとき、
後続の作業工程の仕向先企業に警告のメッセージを送信
することを特徴とする請求項1記載の企業間の取引進捗
管理方法。
2. When the actual date is later than the scheduled completion date,
The method according to claim 1, wherein a warning message is transmitted to a destination company of a subsequent work process.
【請求項3】進捗状況の照会に応答して指定されたスケ
ジュールを取り出し、編集したスケジュールを照会元に
送信することを特徴とする請求項1記載の企業間の取引
進捗管理方法。
3. The business progress management method according to claim 1, wherein a designated schedule is taken out in response to the inquiry about the progress, and the edited schedule is transmitted to an inquiry source.
【請求項4】ネットワークを介して企業間に伝送される
取引情報を取得する手段と、該取引情報を基にして複数
の企業に亘る複数の作業工程と完了予定日を含むスケジ
ュールに展開する手段と、該作業工程について作業の実
績報告を取得したとき該スケジュールに実績日を記録
し、実績日が完了予定日より遅れたとき遅れ日数に応じ
て後続の作業工程の完了予定日を修正する変更日を該ス
ケジュールに記録する手段とを有することを特徴とする
企業間の取引進捗管理をするサーバ装置。
4. A means for acquiring transaction information transmitted between companies via a network, and a means for developing a schedule including a plurality of work processes and a scheduled completion date for a plurality of companies based on the transaction information. And when the actual result report of the work is acquired for the work process, the actual date is recorded in the schedule, and when the actual date is later than the scheduled completion date, the scheduled completion date of the subsequent work process is corrected according to the number of days delayed. Means for recording a date in the schedule.
【請求項5】該実績日が該完了予定日より遅れたとき、
後続の作業工程の仕向先企業に警告のメッセージを送信
する手段をさらに設けることを特徴とする請求項4記載
の企業間の取引進捗管理をするサーバ装置。
5. When the actual date is later than the scheduled completion date,
5. The server device according to claim 4, further comprising means for transmitting a warning message to a destination company of a subsequent work process.
【請求項6】コンピュータが読み取り可能な記憶媒体上
に実体化され、企業間の取引の進捗管理をするコンピュ
ータプログラムであって、該プログラムは下記ステップ
を含む: (a)ネットワークを介して企業間に伝送される取引情
報を取得し、(b)該取引情報を基にして複数の企業に
亘る複数の作業工程と完了予定日を含むスケジュールに
展開し、(c)該作業工程について作業の実績報告を取
得したとき該スケジュールに実績日を記録し、実績日が
完了予定日より遅れたとき遅れ日数に応じて後続の作業
工程の完了予定日を修正する変更日を該スケジュールに
記録する。
6. A computer program embodied on a computer-readable storage medium for managing the progress of a transaction between companies, the program including the following steps: And (b) develops a schedule including a plurality of work processes and a scheduled completion date for a plurality of companies based on the deal information, and (c) performance of the work for the work process. When the report is obtained, the actual date is recorded in the schedule, and when the actual date is later than the scheduled completion date, a change date for correcting the scheduled completion date of the subsequent work process according to the number of days delayed is recorded in the schedule.
【請求項7】該プログラムは、さらに該実績日が該完了
予定日より遅れたとき、後続の作業工程の仕向先企業に
警告のメッセージを送信するステップを含むことを特徴
とする請求項6記載のコンピュータプログラム。
7. The program according to claim 6, further comprising a step of transmitting a warning message to a destination company of a subsequent work process when the actual date is later than the scheduled completion date. Computer programs.
【請求項8】該プログラムは、さらに進捗状況の照会に
応答して指定されたスケジュールを取り出し、編集した
スケジュールを照会元に送信するステップを含むことを
特徴とする請求項6記載のコンピュータプログラム。
8. The computer program according to claim 6, further comprising a step of retrieving a designated schedule in response to the inquiry about the progress, and transmitting the edited schedule to an inquiry source.
JP18791197A 1997-03-31 1997-07-14 Transaction progress management method Expired - Fee Related JP4312846B2 (en)

Priority Applications (8)

Application Number Priority Date Filing Date Title
JP18791197A JP4312846B2 (en) 1997-07-14 1997-07-14 Transaction progress management method
TW087104638A TW432305B (en) 1997-03-31 1998-03-27 Electronic commerce transaction system
US09/050,064 US6049787A (en) 1997-03-31 1998-03-30 Electronic business transaction system with notarization database and means for conducting a notarization procedure
SG9800665A SG79964A1 (en) 1997-03-31 1998-03-30 Electronic business transaction system
KR1019980011240A KR100282750B1 (en) 1997-03-31 1998-03-31 E-commerce system
US10/095,058 US20020095381A1 (en) 1997-03-31 2002-03-12 Electronic business transaction system
US10/915,566 US7428511B2 (en) 1997-03-31 2004-08-11 Electronic business transaction system
US12/219,799 US7590597B2 (en) 1997-03-31 2008-07-29 Electronic business transaction system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP18791197A JP4312846B2 (en) 1997-07-14 1997-07-14 Transaction progress management method

Related Child Applications (1)

Application Number Title Priority Date Filing Date
JP2005314190A Division JP4241922B2 (en) 2005-10-28 2005-10-28 Inter-company transaction progress management method

Publications (2)

Publication Number Publication Date
JPH1131179A true JPH1131179A (en) 1999-02-02
JP4312846B2 JP4312846B2 (en) 2009-08-12

Family

ID=16214370

Family Applications (1)

Application Number Title Priority Date Filing Date
JP18791197A Expired - Fee Related JP4312846B2 (en) 1997-03-31 1997-07-14 Transaction progress management method

Country Status (1)

Country Link
JP (1) JP4312846B2 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002109331A (en) * 2000-10-04 2002-04-12 Brother Ind Ltd System, server and method for managing merchandise
JP2002240951A (en) * 2001-02-15 2002-08-28 Sankyu Inc Physical distribution system, physical distribution processing method, and recording medium
US6694202B2 (en) 2000-04-04 2004-02-17 Fujitsu Limited Production management network system, production management method and recording medium having recorded production management program
US6725122B2 (en) 2001-03-28 2004-04-20 Renesas Technology Corp. Device and method of selecting photomask manufacturer based on received data
WO2004085297A1 (en) * 2003-03-27 2004-10-07 Takeshi Oguchi Supply chain matching management system
US6918089B2 (en) 2000-07-11 2005-07-12 Honda Giken Kogyo Kabushiki Kaisha Schedule management system
JP2006004430A (en) * 2004-06-15 2006-01-05 Microsoft Corp Method and system for restarting project management system scheduling engine based on user input of contractual start/finish data
JP2006221305A (en) * 2005-02-09 2006-08-24 Komatsu Ltd Production management system and method
JP2007109151A (en) * 2005-10-17 2007-04-26 Fujitsu Fip Corp Process management system, process management method, recording medium and process management program
JP2011090459A (en) * 2009-10-21 2011-05-06 Prime Japan Co Ltd Account settlement business promotion system
JP2011090608A (en) * 2009-10-26 2011-05-06 Prime Japan Co Ltd Account settlement business support system
JP2011090607A (en) * 2009-10-26 2011-05-06 Prime Japan Co Ltd Account settlement business support system
CN118378796A (en) * 2024-06-24 2024-07-23 成都光创联科技有限公司 Optical device production process control method and system, storage medium and electronic equipment

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6694202B2 (en) 2000-04-04 2004-02-17 Fujitsu Limited Production management network system, production management method and recording medium having recorded production management program
JPWO2001075541A1 (en) * 2000-04-04 2004-04-30 富士通株式会社 Production management network system, production management method, and recording medium recording production management program
US6918089B2 (en) 2000-07-11 2005-07-12 Honda Giken Kogyo Kabushiki Kaisha Schedule management system
JP2002109331A (en) * 2000-10-04 2002-04-12 Brother Ind Ltd System, server and method for managing merchandise
JP2002240951A (en) * 2001-02-15 2002-08-28 Sankyu Inc Physical distribution system, physical distribution processing method, and recording medium
US6725122B2 (en) 2001-03-28 2004-04-20 Renesas Technology Corp. Device and method of selecting photomask manufacturer based on received data
WO2004085297A1 (en) * 2003-03-27 2004-10-07 Takeshi Oguchi Supply chain matching management system
JP2006004430A (en) * 2004-06-15 2006-01-05 Microsoft Corp Method and system for restarting project management system scheduling engine based on user input of contractual start/finish data
JP2006221305A (en) * 2005-02-09 2006-08-24 Komatsu Ltd Production management system and method
JP2007109151A (en) * 2005-10-17 2007-04-26 Fujitsu Fip Corp Process management system, process management method, recording medium and process management program
JP2011090459A (en) * 2009-10-21 2011-05-06 Prime Japan Co Ltd Account settlement business promotion system
JP2011090608A (en) * 2009-10-26 2011-05-06 Prime Japan Co Ltd Account settlement business support system
JP2011090607A (en) * 2009-10-26 2011-05-06 Prime Japan Co Ltd Account settlement business support system
CN118378796A (en) * 2024-06-24 2024-07-23 成都光创联科技有限公司 Optical device production process control method and system, storage medium and electronic equipment

Also Published As

Publication number Publication date
JP4312846B2 (en) 2009-08-12

Similar Documents

Publication Publication Date Title
US7613648B2 (en) Method and apparatus for enhancing the business and engineering communication between a supplier and a buyer
JP6144730B2 (en) A method adapted to be used for commercial transactions
US20020099735A1 (en) System and method for conducting electronic commerce
US20030144852A1 (en) Providing highly automated procurement services
JPH1131179A (en) Method and device for managing inter-company transaction progress
CN101140637A (en) System and method for turn electric order list to work list
US20040193435A1 (en) EDI declaration management system and method
US8406910B2 (en) Management device, production management device, production management system
CN109214776A (en) A kind of thermoelectricity EPC general contract of civil engineering management overall process total factor control platform
Hassan et al. Development of an order processing system using Google Sheets and Appsheet for a Malaysian automotive SME factory warehouse
JP2002288487A (en) Ordering method and ordering system
JP2001318953A (en) Cost data management system, cost data managing method and its recording medium
JP4241922B2 (en) Inter-company transaction progress management method
JP6581395B2 (en) Format conversion management apparatus and format conversion management method
JP2002203096A (en) Selling support system and method thereof
CN116610685B (en) Method, device, equipment and medium for updating standard information base
US20090171809A1 (en) Efficient purchase order creation
US20220374976A1 (en) Manufacturing ordering assistance apparatus, method and storage medium
JP2003058603A (en) System, method, and program for automatic delivery date inquiry
CN113592374A (en) Equipment purchasing management system, method, server and storage medium
JP2011192158A (en) Book information processing system
WO2010028695A1 (en) Method and system for automatic import of technical data from a manufacturing control system or enterprise resource planning system into an integrated common edp publishing system
JP2004054368A (en) Message access authority processing method
JP2004078405A (en) Order processing system
JP2003196525A (en) Order placing and receiving management system

Legal Events

Date Code Title Description
A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20050830

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20051028

RD02 Notification of acceptance of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7422

Effective date: 20051028

A02 Decision of refusal

Free format text: JAPANESE INTERMEDIATE CODE: A02

Effective date: 20060221

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20060421

A911 Transfer to examiner for re-examination before appeal (zenchi)

Free format text: JAPANESE INTERMEDIATE CODE: A911

Effective date: 20060510

A912 Re-examination (zenchi) completed and case transferred to appeal board

Free format text: JAPANESE INTERMEDIATE CODE: A912

Effective date: 20060526

A521 Request for written amendment filed

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20090324

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20090514

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20120522

Year of fee payment: 3

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

LAPS Cancellation because of no payment of annual fees