CN117010803A - Method and apparatus for displaying change state of part and storage medium - Google Patents

Abstract

The present disclosure relates to a method and apparatus for displaying a part change state, and a storage medium, wherein the method includes: merging the data rows with the same old part number, new part number, version, factory, model and change application number in the part change record; searching a part change plan for the latest one or more change window start dates after a specific date; determining one or more versions corresponding to the one or more change window start dates; acquiring a data row associated with version numbers of the one or more versions in the part change record; and displaying a statistical map of the part change state associated with the acquired data line.

Description

Method and apparatus for displaying change state of part and storage medium

Technical Field

The present disclosure relates to a method and apparatus for displaying a part change state and a storage medium.

Background

In factories, parts often need to be changed, i.e., old parts are changed to new parts, due to product perfection, upgrading, etc. Part changes may involve multiple processes including, for example, pre-application, formal distribution to related departments, part admission, start of implementation, etc. The factory will typically set up several change window periods (e.g., 10 or 12 window periods per year, etc.), each corresponding to a version of a part change, in which changes to the part must be made. In order to ensure that the part change is correctly executed, the part change state needs to be analyzed and checked, so that abnormal conditions can be early-warned and adjusted in advance.

Disclosure of Invention

It is an object of the present disclosure to provide a method and apparatus for displaying a part change state and a storage medium.

Some embodiments of the present disclosure provide a computer-implemented method for displaying a part change state, the method comprising: merging the data rows with the same old part number, new part number, version, factory, model and change application number in the part change record; searching a part change plan for the latest one or more change window start dates after a specific date; determining one or more versions corresponding to the one or more change window start dates; acquiring a data row associated with version numbers of the one or more versions in the part change record; and displaying a statistical map of the part change state associated with the acquired data line.

Some embodiments of the present disclosure provide an apparatus for displaying a part change state, the apparatus comprising: means for performing the steps of the methods described by embodiments of the present disclosure.

Some embodiments of the present disclosure provide an apparatus for displaying a part change state, the apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method described by the embodiments of the present disclosure.

Some embodiments of the present disclosure provide a non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause performance of the methods described by the embodiments of the present disclosure.

Other features and advantages of the present disclosure will become apparent from the following description with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain, without limitation, the principles of the disclosure. Like reference numerals are used to denote like items throughout the various figures.

FIG. 1 is a block diagram of an exemplary apparatus for displaying part change status according to some embodiments of the present disclosure.

FIG. 2 is a flowchart illustrating an exemplary method for displaying part change status according to some embodiments of the present disclosure.

FIG. 3 is a schematic diagram illustrating part change records according to some embodiments of the present disclosure.

Fig. 4 is a schematic diagram illustrating a part change plan according to some embodiments of the present disclosure.

Fig. 5 is a schematic diagram illustrating a statistical diagram of part change states according to some embodiments of the present disclosure.

Fig. 6 is a schematic diagram illustrating a statistical diagram of part change states according to some embodiments of the present disclosure.

Fig. 7 illustrates a general hardware environment in which the present disclosure may be applied, according to some embodiments of the present disclosure.

Detailed Description

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the described exemplary embodiments. It will be apparent, however, to one skilled in the art that the described embodiments may be practiced without some or all of these specific details. In the described exemplary embodiments, well known structures or processing steps have not been described in detail in order to avoid unnecessarily obscuring the concepts of the present disclosure.

The blocks within each block diagram shown below may be implemented by hardware, software, firmware, or any combination thereof to implement the principles of the present disclosure. It will be appreciated by those skilled in the art that the blocks described in each block diagram may be combined or divided into sub-blocks to implement the principles of the present disclosure.

The steps of the methods presented in this disclosure are intended to be illustrative. In some embodiments, the method may be accomplished with one or more additional steps not described and/or without one or more of the steps discussed. Furthermore, the order in which the steps of a method are illustrated and described is not intended to be limiting.

As described above, in order to ensure that the part change is performed correctly, it is necessary to analyze and check the state of the part change. Currently, part change states are typically analyzed manually by a change manager. Specifically, the change manager needs to first download the part change record and the part change plan from the system of the factory, search the part change plan for the version number to be checked, manually screen out the data line corresponding to the version number from the part change record, and manually analyze the change state with reference to each data item in the data line.

However, the amount of data for the part change record is very large (e.g., there may be thousands of data rows), and there may be duplicate data rows in which only one or more data items (e.g., installation stations) differ. The change manager can only check a small amount of data at a time, the monitoring range is small, and the condition of only one data attribute dimension can be checked at a time. Therefore, the change cases cannot be presented from multiple data attribute dimensions at once, and the change cases of multiple versions cannot be presented at once. The change manager needs to spend a great deal of time to perform data screening and processing, and the work efficiency is low. In addition, it is desirable to intuitively present the duty cycle and distribution of the different change states in an imagewise manner. Therefore, an efficient technique for displaying the state of the component change is required.

Fig. 1 is a block diagram of an exemplary apparatus 100 for displaying part change status according to some embodiments of the present disclosure. As shown in fig. 1, the apparatus 100 may include a data line merging section 110, a change window start date searching section 120, a version determining section 130, a data line acquiring section 140, and a statistical map displaying section 150. Although fig. 1 illustrates the above 5 units, this is merely a schematic configuration of the apparatus for displaying the part change state, and the apparatus for displaying the part change state 100 may further include other possible units (e.g., a data line deleting means), or may include a combination unit of any of the above 5 units.

The data line merging component 110 may be configured to merge data lines in the part change record having the same old part number, new part number, version, factory, model number, and change application number. The part change record may be a file (e.g., a data table file) that records specific information of the part change and states of different stages, and may be downloaded from a part change management system of the factory. For example, each data line of the part change record may include, but is not limited to, one or more of the following: the part change belongs to a version, a corresponding vehicle model, a factory, an old part number, a new part number, a pre-change application number, a state of a pre-change application, a result of the pre-change application, a formal change application number, a formal change application state, a part arrival time, a change application number, an installation station, a part change implementation type and the like. However, there may be multiple rows of data in the part change record where only one or more data items are different and other data items are the same. For example, a screw may be used in multiple locations on a vehicle, and thus a change to the screw may involve multiple installation stations, and for each of the multiple installation stations, a data row of part change records may be generated that is identical for data items other than the installation station, and thus it may be considered to merge the data rows to remove duplicate data and reduce the size of the data. Old part number, new part number, version, factory, model number, and change application number are important factors for aggregating rows of data in part change records because these factors in combination may be able to uniquely identify a part change record. According to some embodiments, merging data lines in a part change record having the same old part number, new part number, version, factory, model, and change application number may include removing different data items (e.g., the above-mentioned installation stations) that these data lines have in the merged data line.

The change window start date lookup component 120 may be configured to lookup in the part change plan the most recent change window start date or dates after the particular date. The part change plan may be a file (for example, a data table file) in which specific information of the part change plan of the factory is recorded, or may be downloaded from a part change management system of the factory. The part change plan may correspond to the part change record, i.e., the part change plan may include scheduling information for the versions involved in the part change record. For example, each data line of the part change plan may include, but is not limited to, one or more of the following: vehicle model, factory, part arrival start date, part arrival end date, change window start date, change window end date, change schedule expiration date, version, and the like. According to some embodiments, the particular date may be the current date or any date in the past or future. Since the component change in the factory is performed according to a predetermined change window period and cannot be performed at any time, it is necessary to determine the latest one or more change window start dates after the specific date in order to know the component change state after the specific date. If only one change window period is concerned, only the latest change window starting date after the specific date can be searched; if multiple change window periods are of interest, the most recent (e.g., four) change window start dates after the particular date may be looked up. According to some embodiments, for the case where the part change plan is used for vehicle production, since the whole vehicle stage change application (change application involving a part other than the vehicle body structure) and the vehicle stage change application (change application involving a part of the vehicle body structure) have different change window periods, the latest first one or more change window start dates for the whole vehicle stage change application and the latest second one or more change window start dates for the vehicle stage change application after the specific date can be searched for the subsequent processing, respectively.

The version determination component 130 may be configured to determine one or more versions corresponding to the one or more change window start dates. As described above, each change window period corresponds to a version of a part change. One or more versions corresponding to the one or more change window start dates may be determined by looking up a "version" data item of the data line in which the one or more change window start dates are located in the part change plan. That is, the one or more versions of the closest part change after the particular date are determined. According to some embodiments, for the case where the part change plan is for vehicle production, a first one or more versions corresponding to a first one or more change window start dates for the whole vehicle level change application and a second one or more versions corresponding to a second one or more change window start dates for the vehicle level change application may be determined, respectively.

The data line acquisition component 140 may be configured to acquire a data line in the part change record associated with the version number of the one or more versions. The data line acquisition component 140 may utilize version numbers of one or more versions determined by the version determination component 130 to acquire data lines in the part change record associated with those version number(s). Specific information of the part change application in the one or more versions of the closest part change after the particular date may thus be obtained for analysis and presentation. According to some embodiments, for the case where the part change plan is for vehicle production, the whole vehicle level change application and the vehicle level change application may be handled separately as well, i.e., the data line associated with the version number of the first one or more versions and the data line associated with the version number of the second one or more versions may be acquired, respectively.

The statistical map display component 150 may be configured to display a statistical map of the part change state associated with the acquired data line. The statistical map may reflect the status of the part change from different data attribute dimensions. In addition, the statistical map may reflect the part change state of one version of the change application, or may reflect the part change states of a plurality of versions of the change application. According to some embodiments, the one or more change window start dates looked up by the change window start date lookup component 120 include four change window start dates, and the statistical map may include a statistical map reflecting the part change population states of the four versions corresponding to the four change window start dates.

According to some embodiments, the statistical map display component 150 may be configured to filter, sum, compare, etc., the data items in the acquired data lines to generate data for displaying the statistical map.

According to some embodiments, the statistical map may include one or more of the following: a statistical map (e.g., bar graph, ring graph, etc.) reflecting the number of change applications in one or more versions, a statistical map (e.g., pie graph, bar graph, etc.) reflecting the proportion of the different states of the formal change applications in one or more versions, a statistical map (e.g., pie graph, bar graph, etc.) reflecting the result of the pre-change application in one or more versions, a statistical map (e.g., pie graph, ring graph, etc.) reflecting the proportion of the different part change implementation types of the change applications in one or more versions, a statistical map (e.g., bar graph, pie graph, etc.) reflecting the proportion of the different states of the pre-change applications in one or more versions, a statistical map (e.g., bar graph, pie graph, etc.) reflecting the proportion of the change applications with part to field time in one or more versions, a statistical map (e.g., bar graph, pie graph, etc.), a statistical map (e.g., bar graph, etc.) reflecting the number of part change applications with part to field time in one or more versions, a scatter plot (e.g., field time), etc.). According to some embodiments, the one or more change window start dates may include a first change window start date, and the statistical map may include a scatter plot reflecting whether a part arrival time of a change application having a part arrival time in a first version corresponding to the first change window start date falls within a first part arrival start date associated with the first version and between the first change window start date. According to some embodiments, for the case where the part change record and the part change plan are for vehicle production, the scatter plot may include a first scatter plot for a full vehicle level change application in the first version with part arrival time and a second scatter plot for a vehicle level change application in the first version with part arrival time. Statistical graphs according to embodiments of the present disclosure will be further described below with reference to fig. 5 and 6.

In some embodiments, the apparatus 100 for displaying part change status may also optionally include a data line deletion component (not shown) that may be configured to delete a data line for which the change application number is empty in the part change record. Under normal conditions, after a user submits a part change application, the part change management system automatically generates a corresponding change application number. Therefore, the data line with the blank change application number in the part change record is not generated through the normal flow. Such a data line is not included in the part change state analysis and needs to be deleted in advance. This is not required if the part change record does not include a data row for which the change application number is empty.

Fig. 2 is a flowchart illustrating an exemplary method 200 for displaying part change status according to some embodiments of the present disclosure. Although fig. 2 illustrates 5 steps of method 200, this is merely a schematic flow of a method for displaying a part change state, and method 200 for displaying a part change state may also include other possible steps, or may include a combination of any of the 5 steps described above.

The method 200 starts at step S210, where step S210 may be performed by the data line merging component 110 of fig. 1. At step S210, the data lines in the part change record having the same old part number, new part number, version, factory, model number, and change application number are merged.

The method 200 proceeds to step S220, and step S220 may be performed by the change window start date finding component 120 of fig. 1. At step S220, the latest change window start date or dates after the specific date is found in the part change plan.

The method 200 proceeds to step S230, which step S230 may be performed by the version determination component 130 of fig. 1. At step S230, one or more versions corresponding to the one or more change window start dates are determined.

The method 200 proceeds to step S240, and step S240 may be performed by the data line acquisition component 140 of fig. 1. At step S240, a data line in the part change record associated with the version number of the one or more versions is acquired.

The method 200 proceeds to step S250, which step S250 may be performed by the statistical map display component 150 of fig. 1. At step S250, a statistical map of the part change state associated with the acquired data line is displayed.

According to some embodiments, the method 200 for displaying part change status may optionally further include the step of deleting a data row in the part change record for which the change application number is empty. This step may be performed at any stage prior to step S240 (e.g., prior to step S210, or between steps S210 and S220, etc.).

A method for displaying a part change state according to an embodiment of the present disclosure will be described in further detail below with reference to fig. 3-6.

FIG. 3 is a schematic diagram illustrating a part change record 300 according to some embodiments of the present disclosure. It should be appreciated that while FIG. 3 illustrates part change records in the form of a data table, the present disclosure is not so limited, and part change records may be stored in any suitable format and may be displayed in any suitable format. As shown in FIG. 3, part change record 300 includes 9 data rows and 14 columns 301-314, each data row including a plurality of data items for one part change application, wherein the data items include version, model, factory, old part number, new part number, pre-change application number, status (of pre-change application), pre-change application result, formal change application number, formal change application status, part arrival time, change application number, installation station, part change implementation type, and the like. It should be appreciated that the part change record 300 is merely a simplified example, and that an actual part change record may have many more rows and columns than the part change record 300. As shown in fig. 3, the old part number (MAT-01), the new part number (MAT-02), the version (22-07-20), the factory (a), the model (D1) and the change application number (1860) of the first data line and the second data line are all the same, except that the mounting stations are different (the mounting station of the first line is L122, the mounting station of the second line is 122), so that the first data line and the second data line can be combined. The data items corresponding to the installation stations may be deleted in the merged data row. Similarly, lines 3 and 4 may be combined, lines 5 and 6 may be combined, and lines 7, 8, 9 may be combined. Thereby significantly reducing the amount of data in the part change record.

Fig. 4 is a schematic diagram illustrating a part change plan 400 according to some embodiments of the present disclosure. It should be appreciated that while fig. 4 illustrates the part change plan in the form of a data table, the present disclosure is not so limited, and the part change plan may be stored in any suitable format and may be displayed in any suitable format. As shown in FIG. 4, part change plan 400 includes 4 rows of data and 8 columns 401-408, each row of data including a plurality of data items for a part change version, wherein the data items include a model, a factory, a part arrival start date, a part arrival end date, a change window start date, a change window end date, a change schedule expiration date, a version, and the like. It should be appreciated that part change plan 400 is merely a simplified example, and that an actual part change plan may have many more rows and columns than part change plan 400. The time period between the part arrival start date and the part arrival end date is the time period when the part (i.e., new part) that is ideally changed should arrive at the factory. The change window start date is a date at which a change (i.e., a part after the change is applied) is started in the factory, and the change window end date is a date at which the change is completed in the factory, i.e., after the date, the part change has been completed, and a new part has been fully applied in place of the old part. The change schedule expiration date is a date preceding the part arrival start date, the part arrival end date, the change window start date, and the change window end date, and if a part change is desired to be included in a certain version, a corresponding part change application should be submitted before the change schedule expiration date for that version. It should be appreciated that multiple part change applications may be included in a part change version. Assuming that the part change state after 2022 month 3 and 1 is currently focused, the change window start date of line 2 (2022 month 3 and 2), the change window start date of line 3 (2022 month 4 and 12), and the change window start date of line 4 (2022 month 4 and 26) are found after 2022 month 3 and 1, and thus the corresponding versions are determined to include 22-11-40, 22-11-50, and 22-11-60. Next, a data row (not shown) in the part change record (e.g., part change record 300) associated with version numbers 22-11-40, 22-11-50, 22-11-60 may be acquired, and then a statistical map of the part change status associated with the acquired data row is displayed.

Fig. 5 is a schematic diagram illustrating a statistical diagram 500 of part change states according to some embodiments of the present disclosure. The statistical diagram 500 includes 5 icons 502, 504, 506, 508, and 510. By selecting (e.g., clicking, double clicking, long pressing, etc.) icon 502, a statistical map of the total status of the most recent four versions of part changes after a particular date may be displayed. For example, the statistical map 500 may be displayed after the icon 502 is selected. By selecting icons 504, 506, 508, and 510, statistics of the part change status of the first, second, third, and fourth versions, respectively, that were most recent after a particular date, can be displayed.

The statistical map 500 may include one or more of the statistical maps 521-528. The statistics 521 may be a histogram reflecting the number of change applications in four versions. 21-11-30, 21-11-40, 21-11-50, 21-11-60 in the statistical map 521 are version numbers of four versions. According to some embodiments, in response to hovering a cursor over a pillar, a particular number of change applications in the corresponding version may be displayed, the particular number may be derived by cumulatively summing the change applications included in the corresponding version in the data line. The specific number may also be shown directly above or in the middle of the column, etc. According to some embodiments, in response to selecting a column, at least a portion of the acquired data lines of the change application in the corresponding version may be displayed to facilitate the change administrator's view of the particular data.

The statistical map 522 may be a pie chart reflecting the proportion of different states of the formal change application in four versions, and specific values of the proportion may be explicitly displayed or not displayed on the map, and these specific values may be obtained by classifying and summarizing one item of the "formal change application state" of the data line. After the pre-application passes, the formal change application stage can be entered. At this time, the change application can be distributed to related departments of logistics, purchasing, production and the like for formal evaluation and approval. The formal change applications may have different states, e.g., stateless, under-approval, approval complete, etc., depending on the approval progress of these relevant departments. For formal change applications in stateless and in approval, the change manager may be required to pay attention to their progress, so such formal change applications may be highlighted (e.g., in yellow, red, etc.) in the statistics diagram 522. According to some embodiments, in response to selecting one of the sectors in the pie chart, at least a portion of the acquired data lines of the change application with the corresponding status of the formal change application may be displayed.

The statistical map 523 may be a bar graph reflecting the results of the pre-change applications in four versions, and may or may not explicitly display specific values of the pre-change applications with different results, which may be obtained by sorting and summarizing one of the "pre-change application results" of the data line. After the user submits the part change application, the pre-change application stage is entered first. At this time, the pre-change application can be distributed to related departments of logistics, purchasing, production and the like for pre-evaluation and approval. Depending on the approval results of these relevant departments, the pre-change application may have different results, e.g., consent, disagreement. The number of pre-change applications with different results may be shown in a different color or pattern in the statistics 523. According to some embodiments, at least a portion of the acquired data lines of the change application in the respective version with the respective pre-change application result may be displayed in response to selecting one of the rectangular portions in the histogram.

The statistical map 524 may be a ring map reflecting the proportions of the different part change implementation types of the change applications in the four versions, and specific values of the proportions may or may not be explicitly displayed on the map, and may be obtained by classifying and summarizing one item of "part change implementation type" of the data line. Part change implementation types may include both hard and soft handoffs. For the hard switching type, the new part is directly switched to be used after the starting date of the change window no matter how much stock the old part is; for the soft-handoff type, it is necessary to consume the old parts in inventory after the start date of the change window and then switch to use the new parts. Hard handoff types are highly demanding on logistics and therefore may require significant attention from a change manager. The hard handoff type may be highlighted in statistics 524. According to some embodiments, at least a portion of the acquired data line of the change application with the corresponding part change implementation type may be displayed in response to selecting a different portion in the ring map.

The statistics 525 may be a bar graph reflecting the status of the pre-change applications in four versions, and may or may not explicitly show specific values for the pre-change applications with different status, which may be obtained by sorting and summarizing the "(pre-change application) status" of the data line. The difference between the outcome of the pre-change application and the status of the pre-change application is that the outcome of the pre-change application may depend only on the approval results of the relevant departments located locally (e.g., home), whereas the status of the pre-change application is related to the approval status worldwide. The status of the pre-change application may include blank, confirmed. Referring back to fig. 3, both the validation and validation of the status of the pre-change application may correspond to the result of the consent because the result of the consent may be output as long as the local relevant department approves, but may not have completed the approval in other areas worldwide (corresponding to the status in validation) or may have completed the approval worldwide (corresponding to the validated status). The number of pre-change applications with different states in each version may be shown in a different color or pattern in the statistics 525. According to some embodiments, at least a portion of the acquired data lines of the change application in the respective version with the respective pre-change application state may be displayed in response to selecting one of the rectangular portions in the histogram.

The statistics 526 may be statistics reflecting the proportion of the change applications with part arrival times in the four versions, and may or may not explicitly show a specific value for the proportion, which may be obtained by summing up the change applications with part arrival times in the data line and dividing by the total number of change applications. There may be potential problems with not having a part arrival time change application, for example, because the flow has not progressed to this step, i.e., the part arrival time has not yet been determined. As another example, this may be because the change administrator does not add part arrival times to the part change log, and the change administrator is required to further confirm whether the part arrival times need to be replenished or the part arrival times are temporarily not determinable. According to some embodiments, at least a portion of the acquired data lines with the change application for part arrival time may be displayed in response to selecting the scale or corresponding graphic displayed in statistical map 526.

The statistics 527 may be a bar graph reflecting the number of part changes for a change application without part arrival time in four versions, and may explicitly or non-display specific values for the number of part changes that may be obtained by summing up the different old part numbers in the data line that are involved in the change application without part arrival time. In the statistics graph 527, the vertical axis represents the number of change applications for which there is no part arrival time, and the horizontal axis represents the number of part changes corresponding to the change applications. The right side can comprise a scroll bar, so that the scroll bar can be dragged to check the part change number of other change applications without part arrival time. According to some embodiments, at least a portion of the acquired data lines of the corresponding change applications may be displayed in response to selecting the column displayed in statistics 527.

The statistical map 528 may be a distribution map reflecting the part arrival time and the number of part changes of the four versions of the change application with the part arrival time. In the statistical graph 528, the vertical axis represents time, and the horizontal axis represents the number of component changes, wherein the larger the bubble is, the larger the number of component changes included in the change application corresponding to the bubble is. According to some embodiments, at least a portion of the acquired data lines of the corresponding change application may be displayed in response to selecting the bubble displayed in the statistical map 528.

It should be appreciated that FIG. 5 is merely an example, and that one or more of the statistical graphs 521-528 may be arranged in any suitable manner in the user interface.

Fig. 6 is a schematic diagram illustrating a statistical diagram 600 of part change states according to some embodiments of the present disclosure. The statistical map 600 may be displayed after the icon 604 is selected, which may be a statistical map of the part change status of the most recent first version (21-11-30 in this example) after a particular date. It should be appreciated that the statistical map of the part change status of the second, third, and fourth versions that are most recent after a particular date may be similar to statistical map 600.

The statistics 600 may include one or more of the statistics 621-628. Statistical graphs 621-626 are similar to statistical graphs 521-526 described above with reference to FIG. 5, except that statistical graphs 621-626 reflect part change status for only one version (i.e., 21-11-30). Therefore, a description of the statistical graphs 621-626 is omitted herein.

According to some embodiments, part change records and part change plans are used for vehicle production. The statistics 627 may be a scatter plot that reflects whether the part arrival time of the full vehicle level change application with part arrival time in the version falls between the part arrival start date and the change window start date associated with the version (version 21-11-30 preceded by the letter a to indicate the version of the full vehicle level change application). In the statistics 627, the vertical axis indicates the date, the lower dotted line indicates the arrival start date of the part, and the upper dotted line indicates the change window start date. If the part arrival time falls between the part arrival start date and the change window start date, the part arrival time indicates that the part can arrive on time, and the part change can be normally implemented. And if the part arrival time does not fall between the part arrival start date and the change window start date, then a problem may exist. For example, if the part arrival time is earlier than the part arrival start date, the new part may occupy inventory for a longer time before being put into use, resulting in wasted resources; if the part arrival time is later than the change window start date, a new part can not arrive in time when part change is started to be implemented, and production efficiency is affected. According to some embodiments, different colors or patterns may be used to distinguish between a whole vehicle level change application (represented as a white filled circle in statistics 627) where the part arrival time does not fall between the part arrival start date and the change window start date, and a whole vehicle level change application (represented as a black filled circle in statistics 627) where the part arrival time falls between the part arrival start date and the change window start date. According to some embodiments, at least a portion of the acquired data lines of the corresponding change application may be displayed in response to selecting the circle displayed in the statistics 627. The statistical map 627 can intuitively reflect which part change applications can be normally implemented and which part change applications may have problems. Therefore, a change manager can conveniently identify potential problems and adjust the problems in advance, and the production efficiency is improved.

The statistics 628 may be a scatter plot that reflects whether the part arrival time of a body level change application in that version with a part arrival time falls between the part arrival start date and the change window start date associated with that version (version number 21-11-30 preceded by the letter B to indicate the version of the body level change application). In the statistics 628, the vertical axis indicates the date, the lower dotted line indicates the part arrival start date, and the upper dotted line indicates the change window start date. If the part arrival time falls between the part arrival start date and the change window start date, the part arrival time indicates that the part can arrive on time, and the part change can be normally implemented. And if the part arrival time does not fall between the part arrival start date and the change window start date, then a problem may exist. Similar to the statistics 627, according to some embodiments, different colors or patterns may be used to distinguish between a vehicle body level change application (represented as a white filled circle in the statistics 628) in which the part arrival time does not fall between the part arrival start date and the change window start date, and a vehicle body level change application (represented as a black filled circle in the statistics 628) in which the part arrival time falls between the part arrival start date and the change window start date. According to some embodiments, at least a portion of the acquired data lines of the corresponding change application may be displayed in response to selecting the circle displayed in the statistics 628.

It should be appreciated that FIG. 6 is merely an example, and that one or more of statistics 621-628 may be arranged in a user interface in any suitable manner.

As described above, the method for displaying a part change state according to the present disclosure can show the state distribution of change data from multiple dimensions, thereby facilitating a change manager to view and analyze the part change state from multiple angles. By exhibiting the data of the latest multiple versions (for example, four versions) in the future, the data viewing range is enlarged, which is beneficial to grasp the progress of the part change as a whole. By removing duplicate data, the amount of data can be greatly reduced while maintaining data uniqueness. The statistical graph is automatically generated by screening, matching, summing and other operations on the data items in the data row, manual operation is not needed, and the working efficiency is improved. In addition, the selection of the part displayed by the statistical diagram can jump to the corresponding specific data page, so that the change manager can conveniently check and analyze the data page, and the improvement of the working efficiency can be brought.

Hardware implementation

Fig. 7 illustrates a general hardware environment 700 in which the present disclosure may be applied, according to an exemplary embodiment of the present disclosure.

With reference to fig. 7, a computing device 700 will now be described as an example of a hardware device applicable to aspects of the present disclosure. Computing device 700 may be any machine configured to perform processes and/or calculations and may be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, a personal digital assistant, a smart phone, a portable camera, or any combination thereof. The apparatus 100 described above may be implemented in whole or at least in part by a computing device 700 or similar device or system.

Computing device 700 may include elements capable of connecting with bus 702 or communicating with bus 702 via one or more interfaces. For example, computing device 700 may include a bus 702, one or more processors 704, one or more input devices 706, and one or more output devices 708. The one or more processors 704 may be any type of processor and may include, but is not limited to, one or more general purpose processors and/or one or more special purpose processors (such as special purpose processing chips). Input device 706 may be any type of device capable of inputting information to a computing device and may include, but is not limited to, a mouse, keyboard, touch screen, microphone, and/or remote control. Output device 708 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, a video/audio output terminal, and/or a printer. Computing device 700 may also include a non-transitory storage device 710 or any storage device that is connected to non-transitory storage device 710, which non-transitory storage device 710 may be non-transitory and may implement a data store, and may include, but is not limited to, a disk drive, an optical storage device, a solid state storage, a floppy disk, a flexible disk, a hard disk, a magnetic tape, or any other magnetic medium, a compact disk or any other optical medium, a ROM (read only memory), a RAM (random access memory), a cache memory, and/or any other memory chip or cartridge, and/or any other medium from which a computer may read data, instructions, and/or code. The non-transitory storage device 710 may be detachable from the interface. The non-transitory storage device 710 may have data/instructions/code for implementing the methods and steps described above. Computing device 700 may also include a communication device 712. The communication device 712 may be any type of device or system capable of communicating with external apparatus and/or with a network and may include, but is not limited to, a modem, a network card, an infrared communication device, wireless communication equipment, and/or a device such as bluetooth ^TM A device, 802.11 device, wiFi device, wiMax device, a chipset of a cellular communication facility, etc.

Bus 702 can include, but is not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

Computing device 700 may also include a working memory 714, where working memory 714 may be any type of working memory that may store instructions and/or data useful for the operation of processor 704, and may include, but is not limited to, random access memory and/or read-only memory devices.

Software elements may reside in the working memory 714 including, but not limited to, an operating system 716, one or more application programs 718, drivers, and/or other data and code. Instructions for performing the above-described methods and steps may be included in one or more applications 718, and components of the apparatus 100 described above may be implemented by the processor 704 reading and executing the instructions of the one or more applications 718. More specifically, the data line merging component 110 can be implemented, for example, by the processor 704 upon execution of an application 718 having instructions to perform step S210. The change window start date lookup component 120 may be implemented, for example, by the processor 704 upon execution of the application 718 having instructions to perform step S220. The version determination component 130 may be implemented, for example, by the processor 704 upon execution of an application 718 having instructions to perform step S230. The data line acquisition component 140 may be implemented, for example, by the processor 704 upon execution of the application 718 with instructions to perform step S240. The statistical map display component 150 may be implemented, for example, by the processor 704 upon execution of the application 718 with instructions to perform step S250. Executable code or source code of instructions of the software elements may be stored in a non-transitory computer readable storage medium, such as the storage device(s) 710 described above, and may be read into the working memory 714, possibly compiled and/or installed. Executable code or source code for the instructions of the software elements may also be downloaded from a remote location.

From the above embodiments, it is apparent to those skilled in the art that the present disclosure may be implemented by software and necessary hardware, or may be implemented by hardware, firmware, etc. Based on this understanding, embodiments of the present disclosure may be implemented, in part, in software. The computer software may be stored in a computer readable storage medium, such as a floppy disk, hard disk, optical disk, or flash memory. The computer software includes a series of instructions that cause a computer (e.g., a personal computer, a service station, or a network terminal) to perform a method according to various embodiments of the present disclosure, or a portion thereof.

Having thus described the present disclosure, it is clear that the present disclosure can be varied in a number of ways. Such variations are not to be regarded as a departure from the spirit and scope of the present disclosure, and all such modifications as would be obvious to one skilled in the art are intended to be included within the scope of the following claims.

Claims (16)

1. A computer-implemented method for displaying a change state of a part, comprising:

merging the data rows with the same old part number, new part number, version, factory, model and change application number in the part change record;

Searching a part change plan for the latest one or more change window start dates after a specific date;

determining one or more versions corresponding to the one or more change window start dates;

acquiring a data row associated with version numbers of the one or more versions in the part change record; and

a statistical map of part change states associated with the acquired data lines is displayed.

2. The method of claim 1, further comprising:

and deleting the data row with the blank change application number in the part change record.

3. The method of claim 1 or 2, wherein the one or more change window start dates comprise four change window start dates, and the statistical map comprises a statistical map reflecting an overall status of part changes for four versions corresponding to the four change window start dates.

4. The method of claim 1 or 2, wherein the statistical map comprises a statistical map reflecting a number of change applications in the one or more versions.

5. The method of claim 1 or 2, wherein the statistical map comprises a statistical map reflecting proportions of different states of the formal change applications in the one or more versions.

6. The method of claim 1 or 2, wherein the statistical map comprises a statistical map reflecting results of pre-change applications in the one or more versions.

7. The method of claim 1 or 2, wherein the statistical map comprises a statistical map reflecting proportions of different part change implementation types of the change applications in the one or more versions.

8. The method of claim 1 or 2, wherein the statistical map comprises a statistical map reflecting proportions of different states of the pre-change application in the one or more versions.

9. The method of claim 1 or 2, wherein the statistical map comprises a statistical map reflecting proportions of change applications in the one or more versions having part arrival times.

10. The method of claim 1 or 2, wherein the statistical map comprises a statistical map reflecting a number of part changes for a change application without part arrival time in the one or more versions.

11. The method of claim 1 or 2, wherein the statistical map comprises a distribution map reflecting part arrival times and number of part changes for the one or more versions of the change application with part arrival times.

12. The method of claim 1 or 2, wherein the one or more change window start dates comprises a first change window start date, and the statistical map comprises a scatter plot reflecting whether a part arrival time of a change application having a part arrival time in a first version corresponding to the first change window start date falls between a first part arrival start date associated with the first version and the first change window start date.

13. The method of claim 12, wherein the part change record and the part change plan are for vehicle production, and the scatter plot includes a first scatter plot for a full vehicle level change application in a first version having a part arrival time and a second scatter plot for a vehicle level change application in a first version having a part arrival time.

14. An apparatus for displaying a change state of a part, comprising: means for performing the steps of the method of any one of claims 1-13.

15. An apparatus for displaying a change state of a part, comprising:

at least one processor; and

At least one memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method of any of claims 1-13.

16. A non-transitory computer-readable storage medium storing instructions which, when executed by a processor, cause performance of the method recited in any one of claims 1-13.