JPH0469138A - Synchronous delivery system - Google Patents

Abstract

PURPOSE:To perform correct and detailed delivery indication by developing line-on information into delivery indication information referring to parts information, delivering this delivery indication information to the terminal installed at each shipper, and making delivery indication by means of the terminal. CONSTITUTION:A communication controller 4 receives the line-on information which is output by a production line computer and transfer it to a host computer 1. The host computer 1 receives this line-on information and develops it, and the resultant various output data are delivered to each shipper through the communication controller 4. On the other hand, each shipper makes order slips based on the delivered data. Then, the parts based on these order slips are delivered to the slide who placed the order. This constitution makes it possible to place orders with shippers for desired parts automatically eliminating wrong delivery caused by the mis-reading of numbers.

Description

DETAILED DESCRIPTION OF THE INVENTION "Field of Industrial Application" The present invention relates to a synchronous delivery system suitable for use in managing parts delivered to a production line for, for example, automobiles.

"Prior Art" As is well known, on an automobile production line, parts brought in from each parts manufacturer are prepared for each assembly process, and then assembled to produce a vehicle. Such parts are usually supplied by one of the following delivery methods: lot delivery, daily delivery, and synchronous delivery. This lot delivery refers to the method of delivering specified parts once a day at a specified time.
The formula, daily division delivery, means that the daily delivery amount is divided into 8, 4,
This method divides the cargo into two parts and transports them at designated times.

Parts delivery using these methods is carried out according to a predetermined production plan. On the other hand, synchronous delivery means that parts are supplied at any time in synchronization with the production order of the production line. In other words, it is a delivery system in which the necessary parts are prepared at the start of each process. According to such a delivery system, there is no need to keep parts in stock on the production line, and it becomes possible to perform multi-product production extremely efficiently.

This type of delivery system consists of a computer for logistics management and multiple terminal devices linked to this computer, and is used to order parts based on a predetermined production plan, conduct logistics such as acceptance inspection, etc. It is supposed to be managed.

``Problems that Keiho is trying to solveJ'' By the way, in the conventional system, while company-wide EDP including production lines is being implemented, parts ordering and acceptance inspection of incoming parts require manual intervention. As a result, delivery records and delivery times cannot be ascertained in real time, and incorrect deliveries may occur due to misreading of order numbers. From this point of view, it is difficult to say that the conventional system has created a completely synchronous import system.

This invention has been made in view of the above-mentioned circumstances, and aims to provide a synchronized delivery system that can shorten the lead time for parts delivery and provide accurate and more detailed delivery instructions.

"Means for Solving the Problem" According to the present invention, there is a host computer that orders parts necessary for vehicle production from each import source, and a host computer that is connected to the host computer via a line and installed at each import source. In a synchronized import system consisting of a terminal device and a terminal device, information supplied from a means for managing a production line, which represents the attributes of each vehicle input to the production line;
Receiving means for receiving in-on information; and parts development means for referencing parts information for each vehicle model registered in advance in a storage means and developing the line-on information into carry-in instruction information for ordering parts. a distribution means for distributing the carry-in instruction information to a terminal device installed for each of the carry-in sources, and a distribution means provided for each terminal device to create a carry-in instruction sheet according to the distributed carry-in instruction information. The terminal processing means is characterized by comprising a carry-in management means for inspecting the parts carried in according to the carry-in instruction information and checking the carrying-in status of the parts.

"Operation" According to the above configuration, the receiving means receives line-on information supplied from the means for managing the production line, and the parts deployment means stores parts information for each vehicle model registered in advance in the storage means. The line-on information is referred to and developed into delivery instruction information for ordering parts. Then, the distribution means distributes this carry-in instruction information to the terminal devices installed at each carry-in source, and the terminal processing means creates a carry-in instruction sheet according to the delivered carry-in instruction information. Further, the carry-in management means inspects the parts carried in according to the carry-in instruction information and checks the carrying-in status of the parts.

"Embodiments" Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a nodeware configuration of an embodiment of the present invention. In this figure, numerals 1 and 2 are host computers, which have a standby redundant configuration so that if the main host computer I goes down, the standby host computer 2 backs up the system. Reference numeral 3 denotes an external storage device composed of a magnetic disk device and the like. This external storage device 3 is commonly connected to the host computer 1.2, so that various data files can be shared. A communication control device 4 controls communication procedures between different types of computers.

6-1 to 6-N are modems, and 7-1 to 7-N are terminal units. These terminal units 7-1 to 7-N and modems 6-1 to 6-N are respectively installed at the delivery point where the parts are supplied. Moreover, this terminal unit is 7-1 to 7-
N represents the terminal device 7a, the magnetic disk 7b, the CRT7C,
It consists of a printer 7d.

According to such a configuration, the communication control device 4 receives line-on information (described later) output from the production line computer.
) and supplies it to the host computer 1. The host computer 1 receives this line-on information, performs expansion processing to be described later, and distributes various data outputted as a result to each import source via the communication control device 4.

On the other hand, each delivery source creates an order slip or the like according to the distributed data. Then, parts based on this order slip are delivered to the ordering side. As a result, desired parts can be ordered to the delivery source without manual intervention, and there is no possibility of erroneous deliveries due to misreading of numbers, etc.

Next, the software functional configuration of this embodiment will be explained with reference to FIG. First, the synchronous import system of this embodiment is roughly divided into the following processing groups. That is, a) line-on information reception processing b) deployment processing C) distribution processing d) terminal processing e) acceptance inspection/delivery management processing.

Below, these processing functions will be described in order.

Note that all processes other than the above-mentioned "terminal processing" are executed on the host computer 1 side.

a) Line-on information reception processing This processing is performed by the line-on information reception processing program pt.
(See FIG. 2), and this program P1 is activated when line-on information LOD is input. This line-on information LOD is sent from a production line computer (not shown), and is information generated when a vehicle to be produced is put into the vehicle body assembly process. Such line-on information LOD is composed of a start record, a data record, and an end record.

Here, the data record of the line-on information LOD will be explained with reference to FIG. This data record forms a table for each vehicle, and predetermined data is stored for each item in the table. As shown in the figure, this item includes the line number of the vehicle assembly line, AP-ON (line-on information) serial number LO, line-on time LOT, vehicle frame number FN, loft number, model code, etc. be. This line-on information LOD is used to identify the attributes of each vehicle scheduled for production.

Next, returning to FIG. 2, the line-on information reception processing program PI will be explained. This program PI reads the line-on information LOD mentioned above and stores it in the line-on information index file PI and the line-on information LOD.
Register the ON information data file F24. This index file F1 is a file in which data for managing the data file F2 is registered, such as a write start address and a write end address of the data file F2. On the other hand, data records of line-on information LOD are registered in the data file F2 according to the write start address registered in the index file F1. Such processing is performed as follows depending on the record attribute of the line-on information LOD.

(2) In the case of a start record In this case, the program work area in the main memory of the host computer I is initialized, and the writing start address of the line-on information index file F1 is detected.

■In the case of a data record In this case, the line-on information LOD is sequentially written to the line-on information data file F from the write start address mentioned above.
Write in 2.

■In the case of an end record The end record defines the number of vehicles stored in the data record, and when the writing of the data record is completed, it is determined whether or not the number of vehicles has been written. do. Then, if writing for the number of vehicles has been executed, the writing start address of the line-on information index file F1 is incremented.

As described above, the line-on information LOD is managed separately into the index file F1 and the data file F2. By doing this, even if the amount of data to be displayed increases, the reading speed will not be affected. Further, each seal file, which will be described later, is similarly divided into an index section and a data section.

Next, this program PI refers to the import source terminal management file (not shown) and executes the expansion processing program P2.
(described later) is activated at the import source end.
The ID number, import light name, parts import location, etc. for each 7-N are registered.

b) Expanding Process Here, the line-on information LOD taken in by the line-on information receiving program Pl is expanded into parts items to be ordered for each delivery source.

That is, the expansion processing program P2 (see FIG. 2) refers to the model code expansion master file F3 to determine the parts to be ordered. This model code expansion master file F'3 (hereinafter abbreviated as master file F3) has registered data for identifying parts to be imported at the same time. The parts to be brought in at the same time are parts that are required for each assembly process and are assembled into a set pack. Note that this deployment processing program P2 is executed as a multi-task process in which each import source end is uncut by time sharing.

The contents of this expansion process will be described below.

■Index file F1 and data file F2
Reading First, the processed point record and the write point record are read from the line-on information index file PI, and when they are compared and they match, it is assumed that there is no data to be developed and the development process is terminated.

On the other hand, if they do not match, the processed point record is read from the line-on information data file F2.

(2) Writing to distribution index file F6 and distribution data file F7 In the distribution index file F6, a read pointer record that is referred to when transferring the contents of the distribution data file F7 to the input source is registered.

Here, this read pointer record is written to the distribution index file F6.

On the other hand, line-on information LOD is sequentially written into the distribution data file F7 starting from the address specified by this read pointer record. In this case, the processed point records and subsequent records of the above-mentioned line-on information data file F2 are written.

■Development of the master file F3 According to the model code included in the line-on information LOD, refer to the master file F3 and develop the necessary parts for each vehicle into parts items to be imported synchronously. This J! The learned parts items become parts deployment information.

■Writing to the component development index file F4 and component original data file F5 Attribute data is registered in the component development index file F4. This attribute data is referred to when reading component development information etc. registered in the component development data file F5.

Here, this attribute data is written to the component development index file F4. On the other hand, contents obtained by merging the line-on information LOD and the above-mentioned component development information are written in the component development data file F5 in sequence from the address designated by the read pointer record among the attribute data. The parts development data file F5 in which such contents are registered is referred to when editing the layout of set pack specifications and delivery slips, which will be described later.

■Setback output unit check Check the set pack specification output unit, and edit the layout of the set pack specification based on the accumulated data for those that have reached the output unit and distribute data file F7
Output to.

■Carry-in unit check parts expansion index file F4J Compares the accumulated number of carried-in and the instructed unit of carried-in among the registered attribute data, and edits the layout of the public slip based on the accumulated data for those that have reached the output unit. and outputs it to the distribution data file F7 and import instruction file F9.

■Processed point record of end processing line/on information index file Fl, parts development index file F4
The read point record of the distribution index file F6 and the read point record of the distribution index file F6 are updated.

c) lk! Communication Processing Here, the distribution processing program P3 (see FIG. 2) transfers various data written in the distribution data file F7 to each input source terminal. This program P3 is automatically started so that a transaction for reading distribution data from the distribution data file F7 and transferring it to the import source terminal is performed every minute. Below is the distribution processing program P3
Describe the contents.

■Reading the distribution index file F6 Read the read point record and transferred point record of the distribution index file F6. Compare this read point record with the transferred point record,
If these match, the process for when there is no distribution data, which will be described later, is performed. On the other hand, if they do not match, the process described below when there is distribution data is performed.

■Processing when there is no distribution data If there is no distribution data, create null data (data that has no meaning) and transfer it to the source terminal.

■Processing when there is distribution data In this case, the distribution data file F7 is sequentially read out according to the read point record read from the distribution index file F6, and this is used as the distribution data.
Transfer to the import source terminal. However, this distribution data includes
Depending on the content, a 4-tier ranking is given to the buyer.
Distribution data with a higher priority is transferred first. Data indicating this priority is included in the read point record.

■Delivery completion When data indicating completion of reception is received from the import source terminal, the transferred point record of the distribution index file F6 is updated and the distribution process is completed. However, when null data is transferred using the above-mentioned 0 item, the transfer automatically ends after one minute.

d) Terminal processing This terminal processing is performed in terminal units 7-1 to 7-N (see FIG. 1) installed at each delivery source. Here, the terminal processing program P4 receives the distribution data transferred from the post-computer side, and creates forms such as set pack specifications and public person slips, as well as line-on information L.
Performs OD screen display, etc. The contents are described below.

■Initial terminal conversion The terminal units 7-1 to 7-N installed at each delivery point are
-1 [When J is turned on, the printer initial settings and the basic information table are read. This basic information table 7 is a data table in which the location where the parts to be synchronously carried in, the parts management number, the form creation information, etc. are registered. This is stored in the import source data file F8. When these initial settings are completed, the host computer 1 is accessed and an online state is established.

■Output processing of distribution data Receives the distribution data transferred from the host computer 1 and performs the following output processing. The identification of these output processes is based on data indicating the priority order (AP, SP, HN, MS, TB) included in the read pointer record of the distribution data.
, NL) etc.

For redata AF; line-on information LOD to CRT
The images are sequentially scrolled and displayed on the 7cJ screen.

11) For data SP; print out the setback specification.

iii) In the case of data HN; print the carrier biography list.

iv) For data MS; print out the notification from the host computer.

(2) For data TB: Receive the basic information table and update the registration.

vi) In the case of data NL; the current time on the terminal screen is updated to indicate that the line with the host computer is normal.

(2) Reissue Process All output list information is recorded on the magnetic disk 7b via the terminal device f7a, and can be reissued by operation at the import source.

(2) Restarting the distribution program If the distribution data is not transferred from the host computer 1 after two minutes or more, the distribution program P3 on the host side is activated from each import source.

2) Calibration-Inspection Management Process In this process, the delivery instruction file F9 created by the above-mentioned expansion process is referred to, and the acceptance inspection status of the delivered parts is managed. The processing contents of the acceptance inspection/delivery management processing program P5 will be described below.

(2) Creating a carry-in time index file Read the carry-in instruction data from the carry-in instruction file F9 created by the expansion process, and register it in the carry-in time index file. This carry-in time index file (illustrated path) is a file in which the scheduled time for carrying parts from the carry-in source to the ordering side is registered.

■Carry-in record Human power The barcode written on the carry-in slip created by the above-mentioned terminal processing and the carry-in card as carry-in record data is read at the time of acceptance inspection. Then, if the delivery record data read through this operation and the delivery instruction data match,
The specified parts will be inspected as delivered.

■ Creation of carry-in record data The carry-in record data and carry-in instruction data input through the above input operations are aggregated to create a carry-in progress management file (illustrated route), and a daily carry-in report and other management materials.

■Linkage with other systems Payment data is created from the delivery record data and linked to other systems.

Next, the operation of the embodiment with the above configuration will be explained separately into the operation when the ordering side issues a delivery instruction to the delivery source and the acceptance inspection operation.

(1) Operation when delivery instructions are given First, when a vehicle body is placed on the production line, line-on information LOD (see Figure 3) is sent from the production line computer that manages this process via the communication line. and is supplied to the host computer l.

The host computer I reads the line-on information receiving processing program PI by importing the line-on information LOD.
Start. As a result, the information LOD is registered in the line-on information index file Fl and the line-on information data file F2. And the line
When the acquisition of the ON information LOD is completed, the host computer 1 starts the s familiarization processing program P2. When this is started, the model code expansion master file F
3, the line-on information LOD is developed into parts items to be ordered from each delivery source, and this is registered in the parts development index file F4 and the parts development data file F5. Then, the line-on information LOD and this parts expansion data are merged and registered in the distribution data file F7. Next, the host computer 1 reads the distribution data from the distribution data file F7 and performs a transaction every minute to transfer the distribution data to each import source terminal. This allows each delivery source to know in real time which parts should be delivered.

On the other hand, at each import source, line-on information LOD is extracted from the distribution data supplied via the communication line and displayed as a screen DSP shown in FIG. 4. As a result, the operating status of the production line can be monitored in real time even at the delivery source. Furthermore, a set pack specification is created from the distribution data, and parts to be delivered at the same time are arranged based on this specification. In this way, delivery instructions are given on the spot in accordance with the information distributed from the ordering side. In addition, the carry-in card CARD shown in Figure 5, the public slip, etc. are created based on the distributed data. do. At this time, the above-mentioned shujin slip,
A delivery card CARD (see FIG. 5) is attached to the parts and delivered. This carry-in card CARD has a barcode BC written on it, and by reading this, carry-in record data is input into the host computer I. Then, the host computer l imports the import instruction file F9 mentioned above.
It is determined whether or not the carry-in instruction data stored in the carry-in record data matches the carry-in record data. As a result, if these data match, the items will be inspected as being delivered synchronously according to a predetermined plan.

"Effects of the Invention" As explained above, according to the present invention, the receiving means receives the line-on information supplied from the means for managing the production line, and registers the line-on information in the parts deployment means or storage means in advance. The line-on information is developed into carry-in instruction information for ordering parts by referring to the parts information for each vehicle model.

Then, the distribution means distributes this carry-in instruction information to one terminal device installed at each carry-in source, and the terminal processing means creates a carry-in instruction sheet according to the delivered ship carry-in instruction information. Based on this delivery instruction, the required parts are delivered to the production line at the required time. Further, the carry-in management means inspects the parts carried in according to the carry-in instruction information and checks the carrying-in status of the parts. As a result, the lead time for parts delivery is shortened, and
Accurate and more detailed delivery instructions can be given.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing the hardware configuration of an embodiment of the present invention, FIG. 2 is a block diagram showing the software functional configuration of the embodiment, and FIG.
A diagram showing an example of the on-information LOD, FIG. 4 is a diagram showing three examples of the line-on information display screen on the terminal unit in the same embodiment, and FIG. 5 is a diagram showing an example of the carry-in card CAR in the same embodiment.
It is a figure showing an example of D. Figure 1 1.2...Host computer, 3...External storage device, 4...Communication control device, 6-1 to 6-N...Modem, 7 -1 to 7-N...Terminal unit.

Claims (1)

[Claims] Consisting of a host computer that orders parts necessary for vehicle production from each import source, and a terminal device connected to the host computer via a line and installed at each import source. The synchronous delivery system includes a receiving means for receiving line-on information, which is information supplied from a means for managing a production line and representing the attributes of each vehicle introduced into the production line, and a receiving means for receiving line-on information that is registered in advance in a storage means. a parts development means that refers to the stored parts information for each vehicle model and develops the line-on information into delivery instruction information for ordering parts; and a terminal installed at each delivery source to convert the delivery instruction information to the delivery instruction information. A distribution means for distributing data to each device; a terminal processing means provided for each terminal device for generating a carry-in instruction sheet according to the delivered carry-in instruction information; and a terminal processing means for inspecting parts carried in according to the carried-in instruction information. A synchronous carry-in system characterized by comprising: a carry-in management means for checking the carry-in status of parts.