WO2022239150A1 - データ配信プログラム、サーバ装置、端末装置、データ配信方法およびデータ配信システム - Google Patents
データ配信プログラム、サーバ装置、端末装置、データ配信方法およびデータ配信システム Download PDFInfo
- Publication number
- WO2022239150A1 WO2022239150A1 PCT/JP2021/018062 JP2021018062W WO2022239150A1 WO 2022239150 A1 WO2022239150 A1 WO 2022239150A1 JP 2021018062 W JP2021018062 W JP 2021018062W WO 2022239150 A1 WO2022239150 A1 WO 2022239150A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- project data
- project
- data
- version
- unit
- Prior art date
Links
- 238000009826 distribution Methods 0.000 title claims abstract description 47
- 238000000034 method Methods 0.000 title claims abstract description 15
- 238000012790 confirmation Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 21
- 238000012546 transfer Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 12
- 238000007726 management method Methods 0.000 description 11
- 238000003860 storage Methods 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000002716 delivery method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/18—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form
- G05B19/4093—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form characterised by part programming, e.g. entry of geometrical information as taken from a technical drawing, combining this with machining and material information to obtain control information, named part programme, for the NC machine
- G05B19/40937—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form characterised by part programming, e.g. entry of geometrical information as taken from a technical drawing, combining this with machining and material information to obtain control information, named part programme, for the NC machine concerning programming of machining or material parameters, pocket machining
- G05B19/40938—Tool management
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B19/00—Programme-control systems
- G05B19/02—Programme-control systems electric
- G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
- G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/30—Nc systems
- G05B2219/31—From computer integrated manufacturing till monitoring
- G05B2219/31418—NC program management, support, storage, distribution, version, update
Definitions
- the present disclosure relates to a data distribution program, a server device, a terminal device, a data distribution method, and a data distribution system executed by a server device that distributes data to a tool that writes data to FA (Factory Automation) equipment.
- FA Fractory Automation
- FA factory automation
- S/M set manufacturers
- E/U end users
- the FA equipment consists of hardware required to implement the required functions and project data describing operation instructions for the hardware.
- S/M provides maintenance support, it will correct the project data.
- a dedicated tool corresponding to the data is required to create and modify the project data. This tool is also called an engineering tool.
- Engineering tools are also required to write created or edited project data to the hardware that executes this project data.
- An FA device may operate as a single device that achieves a desired function by executing processing in cooperation with other FA devices. That is, one device may be composed of a plurality of FA devices.
- S/M stores the created project data in a file server in the company by dividing the folder each time the data is updated.
- the S/M can collectively manage the project data related to one device, and by collectively writing them to the hardware, the device can be operated without problems.
- Patent Document 1 discloses a method of storing data of a monitoring system for a large-scale equipment group such as a plant on the cloud, and by updating the data on the cloud, the equipment side detects the update and synchronizes the data. , and how to restore past data.
- the control programs described in the project data for operating the FA devices have a close relationship with each other, and depending on the content of the change, even one change It may be necessary to reflect to the project data of other FA devices.
- updating only the project data of a specific FA device or omitting the update may cause inconsistencies between the operations performed by each FA device, resulting in unstable device operation. have a nature.
- the present disclosure has been made in view of the above, and is a data delivery method that can prevent the operation of a device realized by combining a plurality of devices from becoming unstable due to the update of the project data of the devices. Aim to get the program.
- the present disclosure provides data distribution that causes a server device to execute a process of distributing project data to a terminal device that writes project data to devices of a device that is configured with a plurality of devices.
- a program comprising: a first step of receiving a project data distribution request from a terminal device; and specifying a related device that is another device that constitutes one device together with the device to which the project data specified in the distribution request is written. and a third step of identifying the related device whose project data needs to be updated based on the version of the project data specified in the delivery request and the version of the project data written in the related device. and a fourth step of transmitting to the terminal device the project data specified in the distribution request and the project data to be written into the related equipment specified in the third step.
- the data distribution program according to the present disclosure has the effect that it is possible to prevent the operation of a device realized by combining a plurality of devices from becoming unstable as the project data of the devices is updated.
- FIG. 1 is a diagram showing a configuration example of a data distribution system according to an embodiment
- FIG. Diagram for explaining a configuration example of a device connected to a user-side client terminal
- a diagram showing an example of the versions and levels of importance of project data handled by the data distribution system and the required versions of engineering tools.
- a diagram showing an example of a functional block configuration of a server device, a creator-side client terminal, and a user-side client terminal, which constitute a data distribution system.
- Diagram for explaining the operation of the request version specification part A diagram showing an example of data registered in the database of the server device Flowchart showing an example of the operation of the data distribution system A diagram showing an example of a correspondence list between project IDs and user IDs A diagram showing an example of a correspondence list between user IDs and email addresses of notification target users Flowchart showing an example of an operation in which the server determines project data to be updated and transmits the data to the client terminal on the user side.
- Diagram showing an example of a related device list A diagram for explaining the operation of the request version comparison unit of the server device.
- Diagram showing an example of the correspondence relationship between the project data version and the required version of the engineering tool A diagram showing an example of hardware that implements a server device
- a data distribution program, a server device, a terminal device, a data distribution method, and a data distribution system according to an embodiment of the present disclosure will be described in detail below with reference to the drawings.
- FIG. 1 is a diagram showing a configuration example of a data delivery system 100 according to an embodiment.
- the data distribution system 100 includes a server device 1 provided in the cloud, a creator-side client terminal 2, and a user-side client terminal 3.
- FIG. A device 4 used in a production system to which factory automation (FA) is applied is connected to the client terminal 3 on the user side.
- the user-side client terminal 3 may have a configuration in which a plurality of devices 4 can be connected simultaneously.
- a plurality of creator-side client terminals 2 may be provided.
- the number of user-side client terminals 3 may be plural.
- the server apparatus 1 may be configured as one server apparatus by cooperating with a plurality of apparatuses having similar functions.
- the device 4 connected to the user-side client terminal 3 is composed of a plurality of FA devices each having different functions.
- FIG. 2 is a diagram for explaining a configuration example of the device 4 connected to the user-side client terminal 3.
- the device 4 having a device ID (Identifier) ⁇ which is device identification information, is composed of FA devices 41A, 41B, and 41C.
- Different project data are written in these FA devices 41A to 41C.
- Project data with a project ID of "1001" is written in the FA device 41A with a device ID of "A", which is identification information of the FA device, and the version of this project data (project version) is "3". .
- Project data with a project ID of "1002" is written in the FA device 41B with the device ID of "B”, and the version of this project data is “2".
- Project data with a project ID of "1003" is written in the FA device 41C with the device ID of "C”, and the version of this project data is "2".
- the project data written in the FA equipment may be referred to as the project data of the FA equipment.
- the functions of the device 4 are realized by the cooperative operation of the FA devices 41A to 41C. Therefore, the project data of the FA devices 41A to 41C of the apparatus 4 have some kind of relationship, such as synchronizing the processes executed by the FA devices 41A to 41C and exchanging data.
- the server device 1 includes a database 10 in which project data for operating each FA device that constitutes the device 4 and information on the project data are registered.
- the creator-side client terminal 2 is a terminal device used for creating and correcting project data to be registered in the database 10 .
- a worker creates and modifies project data using an engineering tool.
- the creator-side client terminal 2 uploads the obtained project data to the server device 1 when the work of creating or correcting the project data is completed.
- the creator-side client terminal 2 also uploads information about the project data.
- the information about the project data includes, for example, the importance of the project data, the version of the engineering tool that should be used in writing the project data to the FA device 41 (hereinafter referred to as required version), and the like.
- information about project data may be referred to as project-related information. As shown in FIG.
- the user-side client terminal 3 downloads the project data corresponding to the FA equipment that constitutes the device 4 from the database 10 of the server device 1, and writes the downloaded project data to the FA equipment.
- the client terminal 3 on the user side downloads all the project data that needs to be updated together, and updates each project data accordingly.
- the FA device that For example, when one of the FA devices that make up the device 4 operates according to a certain version of project data, the other FA devices need to operate according to a specific version of the project data in order to ensure the normal operation of the device 4.
- the client terminal 3 on the user side downloads all the project data necessary to ensure the normal operation of the device 4, and writes each project data to the corresponding FA equipment.
- there is an FA device in which the project data required to ensure the normal operation of the device 4 is already written there is no need to download and write the necessary project data to this FA device.
- the user-side client terminal 3 uses an engineering tool to write the project data to the FA equipment.
- the user-side client terminal 3 confirms whether or not the engineering tool to be used needs to be updated when writing the project data to the FA device.
- the user-side client terminal 3 first updates the engineering tool, and then writes the project data to the FA equipment.
- FIG. 4 is a diagram showing a functional block configuration example of the server device 1, the creator side client terminal 2, and the user side client terminal 3 that constitute the data distribution system 100. As shown in FIG. The device 4 described above is connected to the client terminal 3 on the user side.
- the apparatus 4 is composed of a plurality of FA devices 41 described as devices in FIG.
- the server device 1 includes the database 10 described above, a project data registration unit 11, a project data update notification unit 12, a project data using device list creation unit 13, a related device list creation unit 14, and a request version comparison unit 15. , an update target project list creation unit 16, and a project data transmission unit 17.
- the project data registration unit 11 acquires project data and project-related information created by the creator-side client terminal 2 from the creator-side client terminal 2 and registers them in the database 10 .
- the project data update notification unit 12 sends a Notify that the project data to be used has been updated.
- the project data using device list creation unit 13 When receiving a project data distribution request from the user-side client terminal 3, the project data using device list creation unit 13 creates a list of the FA devices 41 that use the requested project data. The project data using device list creating unit 13 transmits the created list to the user side client terminal 3 .
- the related device list creation unit 14 is a related device identification unit.
- the related device list creation unit 14 identifies other FA devices 41 related to the selected FA device 41, A list of the identified FA devices 41 is created.
- the list created by the related device list creation unit 14 will be referred to as a related device list.
- the FA devices 41 included in the related device list are referred to as related FA devices.
- a related FA device is another FA device 41 that constitutes one device 4 together with the selected FA device 41 . For example, in the apparatus 4 having the configuration shown in FIG.
- the related device list creation unit 14 creates a list of the FA devices 41 that are not selected as targets for updating the project data among the FA devices 41 that constitute one device 4, and uses this list as the related device list. .
- the request version comparison unit 15 is an update target related device identification unit.
- the request version comparison unit 15 compares the version of the project data written in each of the related FA devices included in the related device list with the request version indicated by the project related information of the project data to be updated. Specifically, the requested version comparison unit 15 confirms whether the version of the project data written in each of the related FA devices included in the related device list satisfies the requested version.
- a requested version is a version guaranteed to be used in combination with the project data to be updated. If the version of the project data does not satisfy the required version, that is, if the compared two versions are different, the requested version comparison unit 15 determines that the project data of the related FA device needs to be updated.
- the update target project list creation unit 16 registers the project data of the related FA devices for which the request version comparison unit 15 determines that the update of the project data is necessary as update target project data in the list.
- the list created by the update target project list creation unit 16 will be referred to as an update target project list.
- the project data transmission unit 17 transmits the project data registered in the update target project list to the user-side client terminal 3.
- the creator-side client terminal 2 includes a project data transfer unit 21, an update importance designation unit 22, a requested version designation unit 23, a required version designation unit 24, and a project data creation unit 25. These units are implemented by an engineering tool 20 installed in a computer that operates as the client terminal 2 on the creator side.
- the project data transfer unit 21 accepts from the user who is the creator a designation of a target to be uploaded to the server device 1 from among one or more project data held by the client terminal 2 on the creator side, and transfers the specified project. Data and project-related information are transferred to the server device 1 .
- the update importance specification unit 22 accepts from the user the specification of the update importance of the project data specified by the project data transfer unit 21, that is, the project data to be uploaded to the server device 1.
- the level of importance designated by the update level-of-importance designation unit 22 is one piece of information included in the project-related information described above.
- the requested version designation unit 23 receives from the user a designation of a requested version, which is a version requested for project data related to project data to be uploaded to the server device 1 (hereinafter referred to as related project data).
- Related project data is project data of other FA devices 41 that constitute one device 4 together with the FA device 41 in which the project data to be uploaded to the server device 1 is written.
- the requested version specifying unit 23 Upon receiving the specification of the requested version from the user, the requested version specifying unit 23 generates, for example, the configuration information shown in FIG. FIG. 5 is a diagram for explaining the operation of the requested version specifying unit 23. As shown in FIG. FIG.
- the version of other project data used in combination when verifying the project data to be uploaded to the server device 1 is specified.
- the required version specification unit 24 accepts from the user the specification of the required version of the engineering tool used when writing the project data to be uploaded to the server device 1 to the FA device 41 .
- the required version for example, the version of the engineering tool used to create the project data to be uploaded to the server device 1 or a newer version than this is specified. Since the required version can be arbitrarily determined by the user, these versions are not always specified.
- the required version specified by the required version specifying unit 24 is one of the information included in the project-related information described above.
- the project data creation unit 25 creates project data according to the user's project data creation operation.
- the project data creating unit 25 is also used when changing project data.
- the user-side client terminal 3 includes a project data distribution request unit 31, an update target selection unit 32, a project data acquisition unit 33, a tool version confirmation unit 34, a project data writing unit 35, and a writing result registration unit 36. And prepare. These units are implemented by an engineering tool 30 installed in a computer that operates as the user side client terminal 3 .
- the project data delivery request unit 31 receives a notification from the server device 1 that a new version of the project data corresponding to the FA device 41 owned by the user has been registered, and the user updates the notified project data. If desired, a project data distribution request is transmitted to the server device 1 .
- the update target selection unit 32 accepts the selection of the FA device 41 to be updated from the user.
- the project data acquisition unit 33 acquires project data to be updated from the server device 1 .
- the tool version confirmation unit 34 confirms whether or not the version of the engineering tool 30 used by the user-side client terminal 3 is appropriate when writing the project data acquired from the server device 1 to the FA device 41 . If the version of the engineering tool 30 is not appropriate, the user side client terminal 3 updates the engineering tool 30 .
- the project data writing unit 35 writes the project data acquired from the server device 1 to the FA equipment 41 .
- the writing result registration unit 36 registers the information of the FA device 41 that wrote the project data in the database 10 of the server device 1 as the project data writing result.
- FIG. 6 is a diagram showing an example of data registered in the database 10 of the server device 1.
- FIG. 6 one or more user data 201, device data 202, equipment data 203, project management data 204, project data 205 and engineering tool data 206 are registered in the database 10, respectively.
- the user data 201 is data relating to users who use the project data 205, and includes a user ID 2011, an owned device ID 2012, a device component ID 2013, and an email address 2014.
- the user ID 2011 is user identification information.
- the owned device ID 2012 is identification information of the device 4 owned by the user with the user ID 2011 . Multiple owned device IDs 2012 may be included in one user data 201 .
- the device configuration device ID 2013 is identification information of the FA device 41 configuring the device 4 of the owned device ID 2012 .
- a plurality of device component IDs 2013 may be included in one user data 201 .
- the email address 2014 is an example of contact information for the user with the user ID 2011 .
- the user's contact information may be information other than an email address.
- the device data 202 is data related to the device 4 and includes a device ID 2021, a device component ID 2022 and a user ID 2023.
- the device configuration device ID 2022 is identification information of the FA device 41 that configures the device 4 with the device ID 2021.
- a plurality of device configuration device IDs 2022 may be included in one device data 202 .
- the device configuration device ID 2022 is identification information of the user who owns the device 4 with the device ID 2021 .
- the device data 203 is data relating to the FA device 41 and includes a device ID 2031, a project ID 2032, a project version 2033, a user ID 2034, and an affiliated device ID 2035.
- the project ID 2032 is identification information of the project data written in the FA device 41 with the device ID 2031.
- a project version 2033 indicates the version of project data of the project ID 2032 .
- the user ID 2034 is identification information of the user who owns the FA device 41 with the device ID 2031 .
- the belonging device ID 2035 is identification information of the device 4 to which the FA device 41 of the device ID 2031 belongs, that is, the device 4 configured by the FA device 41 .
- Project management data 204 is data relating to project data, and includes project ID 2041, compatible device ID 2042, creator ID 2043, project version 2044, engineering tool required version 2045, related project information 2046, related project request version 2047, and importance 2048. .
- the project ID 2041 is identification information of project data.
- the corresponding device ID 2042 is identification information of the FA device 41 in which the project data of the project ID 2041 is written. This compatible device ID 2042 is updated when the project data of the project ID 2041 is written to the FA device 41 .
- Creator ID 2043 is identification information of the creator of the project data of project ID 2041 .
- Project version 2044 indicates the version of project data of project ID 2041 .
- the required engineering tool version 2045 indicates the version of the engineering tool that should be used when writing the project data of the project ID 2041 to the FA device 41 .
- Related project information 2046 is information indicating related project data of project data of project ID 2041 .
- Related project information 2046 is the project ID of related project data.
- Other project data related to the project data with the project ID 2041 is project data written in each of the other FA devices 41 that constitute one apparatus 4 together with the FA device 41 to which the project data with the project ID 2041 is written.
- the related project request version 2047 is the version required for each project data indicated by the related project information 2046 .
- the importance 2048 indicates the importance of updating the project data of the project ID 2041 .
- the project data 205 is project data created and edited by the client terminal 2 on the creator side. written.
- the project data 205 includes information such as a project ID and version in addition to the data itself.
- the project management data 204 and the project data 205 are separately registered in the database 10, but the project data 205 may include the project management data 204.
- FIG. The project management data 204 may be added to the project data 205 and registered in the database 10 .
- the engineering tool data 206 is transmitted to the requesting client terminal (creator client terminal 2 or user client terminal 3) in response to a request from the creator client terminal 2 or user client terminal 3, Installed on the client terminal.
- the above user data 201, device data 202, equipment data 203 and project management data 204 are associated with one or more of the information they contain.
- the correspondence of information is indicated by arrows.
- user ID 2011 , user ID 2023 and user ID 2034 correspond to user data 201 , device data 202 and device data 203 .
- Owned device ID 2012 and device ID 2021 associate user data 201 and device data 202 .
- the project ID 2032 and the project ID 2041 associate the device data 203 and the project management data 204 with each other.
- the functions possessed by the client terminal 2 on the creator side and the functions possessed by the client terminal 3 on the user side appear to be different, but these two terminals have similar functions.
- the configuration of the functions used by the creator of the project data is described
- the configuration of the functions used by the user of the project data is described. is doing.
- FIG. 7 is a flow chart showing an example of the operation of the data delivery system 100.
- the client terminal 2 on the creator side creates project data and uploads it to the server device 1
- the client terminal 3 on the user side downloads the project data from the server device 1 to the FA device 41 of the device 4 .
- It shows the operation up to writing to "Equipment” in FIG. 7 means "FA equipment”.
- "creator terminal” means “creator side client terminal”
- “user terminal” means “user side client terminal”.
- the creator-side client terminal 2 creates project data (step S1).
- project data is created by the project data creating section 25 .
- the creator-side client terminal 2 registers the project data created in step S1 in the server device 1 (step S2).
- the project data transfer unit 21 receives from the user the designation of the project data created in step S1 as the project data to be transferred to the server device 1, and the update importance designation unit 22 receives the project data to be transferred. Receives from the user the designation of the importance of the update of Further, the requested version designation unit 23 receives from the user a designation of the requested version for the related project data of the project data to be transferred. Further, the required version specification unit 24 receives specification of the required version of the engineering tool used for writing the specified project data to the FA device 41 from the user. The project data transfer unit 21 transfers the project data specified by the user, the update importance specifying unit 22 specifies the importance specified by the user, and the request version specifying unit 23 specifies the request for related project data specified by the user. The version and required version specifying unit 24 adds the required version of the engineering tool specified by the user, and transmits it to the server device 1 .
- the server device 1 that has received the project data from the creator side client terminal 2 registers the project data in the database 10 .
- the project data registration unit 11 registers the received project data in the database 10 as the project data 205, and registers the information added to the received project data in the database 10 as the project management data 204. .
- the server device 1 notifies the user-side client terminal 3 that the project data has been newly registered in the database 10 (step S3). At this time, the server device 1 targets the user-side client terminal 3 of the user who owns the FA device 41 that uses the newly registered project data in the database 10, and provides information on the newly registered project data. notification. This operation is described in detail below.
- step S3 the project data update notification unit 12 checks the user data 201 and equipment data 203 registered in the database 10, and creates a list of correspondence between project IDs and user IDs, for example, as shown in FIG. to identify the user ID of the target user to whom the notification is to be sent.
- the project data update notification unit 12 creates a correspondence list between the user ID of the user to be notified and the e-mail address that is the contact address, as shown in FIG.
- a mail indicating that the project data has been newly registered in the database 10 is sent. This email will also notify you of the importance of updating the registered project data.
- the user of the user-side client terminal 3 who has received the notification determines whether or not to update the notified project data. demand.
- the project data distribution request unit 31 transmits a project data distribution request to the server device 1 .
- the project data using equipment list creation unit 13 refers to the equipment data 203 of the database 10, and FA equipment using the old version of the project data newly registered in the database 10 41 list is created and sent to the client terminal 3 on the user side as a list of devices used in the project.
- the user-side client terminal 3 that has received the project use device list selects the FA device 41 whose project data is to be updated from among the FA devices 41 included in the project use device list.
- Select step S4. This selection is made by the user using the user-side client terminal 3 . That is, in step S4, the user-side client terminal 3 receives from the user the selection of the FA device 41 whose project data is to be updated.
- the update target selection unit 32 displays the list of devices used in the project on a display unit (not shown in FIG. 4), and accepts from the user the selection of the FA device 41 whose project data is to be updated.
- the update target selection unit 32 creates a list of the selected FA devices 41 and transmits the list to the server device 1 as an update target device list.
- the server device 1 Upon receiving the update target device list, the server device 1 determines update target project data based on the update target device list and transmits the project data to the user side client terminal 3 (step S5).
- FIG. 10 is a flow chart showing an example of the operation of the server device 1 determining project data to be updated and transmitting it to the user-side client terminal 3 .
- step S5 shown in FIG. 7 first, as shown in FIG. 10, the related device list creating unit 14 searches the database 10 to find all related FA devices of all FA devices 41 included in the update target device list.
- a device list is created (step S51). This list is called a related device list.
- the related device list creating unit 14 extracts information that satisfies the conditions from a list of version information of project data used by each FA device 41 that constitutes each device 4, for example, as shown in FIG. Create a device list.
- FIG. 11 is a diagram showing an example of a related device list.
- the requested version comparison unit 15 compares the version of the project data of each FA device 41 registered in the related device list with the requested version ( By comparing with the related project request version 2047), the FA device 41 whose project data needs to be updated is specified (step S52).
- the update target project list creation unit 16 creates a list of update target projects, which are project data determined to require updating by the request version comparison unit 15 (step S53).
- the list created by the update target project list creating unit 16 will be referred to as an update target project list.
- the project data transmission unit 17 transmits each project data registered in the update target project list to the user side client terminal 3 (step S54). .
- the project data transmission unit 17 adds the engineering tool required version 2045 included in the project management data 204 shown in FIG. 6 to the project data and transmits the project data.
- the engineering tool required version 2045 to be added to the project data is assumed to be the engineering tool required version 2045 of the project management data 204 corresponding to the project data registered in the database 10 in step S2 described above.
- the project data acquisition unit 33 receives the project data transmitted by the server device 1 in step S5.
- the user-side client terminal 3 that has received the project data from the server device 1 confirms whether or not the engineering tool needs to be updated (step S6).
- the tool version confirmation unit 34 checks the version of the engineering tool indicated by the required engineering tool version 2045 added to the received project data and the version of the engineering tool 30 used by the user-side client terminal 3. Compare with If these two versions are different, the tool version checking unit 34 determines that the engineering tool needs to be updated.
- FIG. 13 is a diagram showing an example of the correspondence relationship between the version of the project data and the required version of the engineering tool.
- engineering tools may need to be updated.
- the tool version checking unit 34 determines whether the project data to be written to each of the plurality of FA devices 41 to be updated is required. The version is compared with the version of the engineering tool 30 used by the user-side client terminal 3, and it is determined whether or not the engineering tool needs to be updated.
- step S6 the user-side client terminal 3 updates the engineering tool to be used (step S7).
- step S7 the user-side client terminal 3 downloads and installs the engineering tool data 206 of the version indicated by the engineering tool required version 2045 added to the received project data from the database 10 of the server device 1, and installs the engineering tool. Update 30.
- step S6 When the update of the engineering tool is not necessary (step S6: No), and when the update of the engineering tool in step S7 is completed, the user-side client terminal 3 sends the project data received from the server device 1 to the corresponding FA. Write to the device 41 to update the project data (step S8). Specifically, each project data received by the project data acquisition unit 33 is written by the project data writing unit 35 to the corresponding FA device 41 .
- the user-side client terminal 3 registers the update result of the project data in the server device 1 (step S9).
- the write result registration unit 36 transmits the update result of the project data to the server device 1 , and the server device 1 receives this and registers it in the database 10 .
- the registration of the update result in the database 10 may be performed by another functional unit whose description is omitted in FIG. 4, or may be performed by the illustrated project data registration unit 11, for example.
- the description is continued assuming that the project data registration unit 11 registers in the database 10 .
- the update result of the project data includes at least the information of the FA device 41 that updated the project data and the version information of the updated project data.
- the project data registration unit 11 updates the project version 2033 of the equipment data 203 shown in FIG. 6 according to the content of the received update result. That is, the project data registration unit 11 rewrites the value of the project version 2033 of the device data 203 in which the device ID of the FA device 41 whose project data has been updated is registered with the version of the updated project data.
- the user-side client terminal 3 issues a project data distribution request when receiving a notification that new project data has been registered in the database 10 of the server device 1, but this is an example. be.
- the user-side client terminal 3 can issue a project data distribution request at any timing.
- FIG. 14 is a diagram showing an example of hardware that implements the server apparatus 1. As shown in FIG. 14
- the server device 1 can be realized by a processor 101, a storage device 102 and a communication device 103.
- An example of the processor 101 is a CPU (Central Processing Unit, central processing unit, processing unit, arithmetic unit, microprocessor, microcomputer, DSP (Digital Signal Processor)) or system LSI (Large Scale Integration).
- the storage device 102 is a RAM (Random Access Memory), a ROM (Read Only Memory), a hard disk drive, an SSD (Solid State Drive), a removable memory device, or a combination thereof.
- the project data registration unit 11, the project data update notification unit 12, the project data using equipment list creation unit 13, the related equipment list creation unit 14, the request version comparison unit 15, and the update target project list creation unit 16 of the server device 1 are It is realized by the processor 101 executing a data distribution program, which is a program for operating each part.
- a data distribution program for operating as a project data registration unit 11, a project data update notification unit 12, a project data using device list creation unit 13, a related device list creation unit 14, a request version comparison unit 15, and an update target project list creation unit 16. are stored in the storage device 102 in advance.
- the processor 101 reads the data distribution program from the storage device 102 and executes it to obtain the project data registration unit 11, the project data update notification unit 12, the project data using device list creation unit 13, the related device list creation unit 14, the request It operates as a version comparison unit 15 and an update target project list creation unit 16 .
- the project data transmission unit 17 of the server device 1 is implemented by the communication device 103 .
- Database 10 is implemented by storage device 102 .
- the processor 101, storage device 102, and communication device 103 shown in FIG. 14 may be hardware that constitutes a computer. That is, the server device 1 may be realized by a computer and a data distribution program executed by the computer.
- the above data distribution program for operating as each part of the server device 1 is pre-stored in the storage device 102, it is not limited to this.
- the above data distribution program is written in a recording medium such as a CD (Compact Disc)-ROM, a DVD (Digital Versatile Disc)-ROM, and is supplied to the user, and is installed in the storage device 102 by the user. good too. Further, the above data distribution program may be provided to the user via a network such as the Internet.
- the client terminal 2 on the creator side and the client terminal 3 on the user side can also be implemented with the same hardware as the hardware that implements the server device 1 .
- the client terminal 2 on the creator side and the client terminal 3 on the user side install a program in the storage device 102 for operating as an engineering tool having the functions of the processing units described above, and the processor 101 executes the program. Realized.
- the server device 1 when the server device 1 receives a delivery request for the project data of the FA device 41, the server device 1 is associated with the FA device 41 that uses the requested project data. Identify the FA device, further check whether there is any related FA device that requires project data update, and if there is a related FA device that requires project data update, this related FA device.
- the project data that needs to be written to the device is sent to the user side client terminal 3 together with the requested project data to be written to the FA device 41 .
- the user-side client terminal 3 writes each project data received from the server device 1 to the corresponding FA device 41 .
- the version of the project data of the other FA device 41 constituting the same device 4 is updated to the version of the selected FA device.
- an engineering tool is used to visually confirm details of the project data to be transferred, for example, changed parts, before transferring the project data to the FA equipment.
- the software version of the engineering tool used in the project data change work on the creator side client terminal 2 is different from the software version of the engineering tool used by the user side client terminal 3 that transfers the project data to the FA device, the project Data may not be verified. Also, there may be a case where project data cannot be successfully transferred to the FA equipment.
- the version of the engineering tool used by the client terminal 3 on the user side is older than the version of the engineering tool used by the client terminal 2 on the creator side in changing the project data
- the old version of the engineering tool is replaced by the new version of the engineering tool.
- Project data created by engineering tools may be recognized as unknown data, and as a result, content confirmation and transfer may be restricted.
- the user-side client terminal 3 confirms the necessity of updating the engineering tool, as described above, and when the update is necessary, first updates the engineering tool, and updates the engineering tool after the update. Use the tool to transfer the project data to the sending FA device. Therefore, it is possible to prevent the confirmation of the contents of the project data and the transfer thereof from being restricted.
- the operation of updating the project data of the FA device 41 to a new version has been described, but it is also applicable to the case of writing back to an old version of the project that has been used in the past.
- the user-side client terminal 3 acquires a list of project data registered in the database 10 of the server device 1, and the user selects a version of the project data to be written back, the selected project data and The server device 1 confirms whether or not the version of the project data guaranteed to be used in combination is used by another FA device 41 . If the project data of the version guaranteed to be used in combination with the selected project data is not used by another FA device 41 (related FA device), the server device 1 selects the guaranteed version of the project data.
- the data is transmitted to the user side client terminal 3, and the user side client terminal 3 writes back to the related FA equipment.
- the project data of a certain FA device 41 is written back due to reasons such as the operation of the device 4 becoming unstable, the project used by each FA device 41 of the device 4 after being written back
- the correct combination of versions of the data can be ensured to return the device 4 to its proven and stable operation.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Manufacturing & Machinery (AREA)
- Theoretical Computer Science (AREA)
- Automation & Control Theory (AREA)
- Business, Economics & Management (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Geometry (AREA)
- Human Computer Interaction (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Human Resources & Organizations (AREA)
- Computer Security & Cryptography (AREA)
- Game Theory and Decision Science (AREA)
- Educational Administration (AREA)
- Development Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
Description
図1は、実施の形態にかかるデータ配信システム100の構成例を示す図である。データ配信システム100は、クラウドに設けられたサーバ装置1と、作成者側クライアント端末2と、利用者側クライアント端末3とを備える。利用者側クライアント端末3にはファクトリーオートメーション(FA)が適用された生産システムで用いられる装置4が接続される。利用者側クライアント端末3は、装置4が複数台同時に接続可能な構成であってもよい。なお、作成者側クライアント端末2は複数であってもよい。同様に、利用者側クライアント端末3も複数であってもよい。また、サーバ装置1は、同様の機能を有する複数の装置が連携することで1つのサーバ装置として成り立つ形態であってもよい。
Claims (9)
- 複数の機器で構成される装置の前記機器にプロジェクトデータを書き込む端末装置へ前記プロジェクトデータを配信する処理をサーバ装置に実行させるデータ配信プログラムであって、
前記端末装置から前記プロジェクトデータの配信要求を受信する第1のステップと、
前記配信要求で指定されたプロジェクトデータが書き込まれる前記機器とともに1つの装置を構成する他の前記機器である関連機器を特定する第2のステップと、
前記配信要求で指定されたプロジェクトデータのバージョンと、前記関連機器に書き込まれているプロジェクトデータのバージョンと、に基づいて、プロジェクトデータの更新が必要な前記関連機器を特定する第3のステップと、
前記配信要求で指定されたプロジェクトデータと、前記第3のステップで特定した前記関連機器に書き込むプロジェクトデータとを前記端末装置へ送信する第4のステップと、
を前記サーバ装置に実行させることを特徴とするデータ配信プログラム。 - 前記プロジェクトデータは、前記関連機器に書き込まれているプロジェクトデータである関連プロジェクトデータが満たすべきバージョンである要求バージョンの情報を含み、
前記第3のステップでは、前記関連プロジェクトデータのバージョンが前記要求バージョンと異なる前記関連機器を、プロジェクトデータの更新が必要な関連機器とする、
ことを特徴とする請求項1に記載のデータ配信プログラム。 - 新しいプロジェクトデータを取得してデータベースに登録する第5のステップと、
前記第5のステップで前記データベースに登録したプロジェクトデータに関する情報を前記端末装置に通知する第6のステップと、
を含むことを特徴とする請求項1または2に記載のデータ配信プログラム。 - 前記第5のステップで取得するプロジェクトデータには当該プロジェクトデータの更新の重要度が設定されており、
前記第6のステップで前記端末装置に通知する情報は、前記第5のステップで前記データベースに登録したプロジェクトデータに設定されている重要度を含む、
ことを特徴とする請求項3に記載のデータ配信プログラム。 - 複数の機器で構成される装置の前記機器にプロジェクトデータを書き込む端末装置へ前記プロジェクトデータを配信するサーバ装置であって、
前記プロジェクトデータおよび前記プロジェクトデータが書き込まれるデータベースと、
前記端末装置から前記プロジェクトデータの配信要求を受信すると、前記配信要求で指定されたプロジェクトデータが書き込まれる前記機器とともに1つの装置を構成する他の前記機器である関連機器を特定する関連機器特定部と、
前記配信要求で指定されたプロジェクトデータのバージョンと、前記関連機器に書き込まれているプロジェクトデータのバージョンと、に基づいて、プロジェクトデータの更新が必要な前記関連機器を特定する更新対象関連機器特定部と、
前記配信要求で指定されたプロジェクトデータと、前記更新対象関連機器特定部で特定された前記関連機器に書き込むプロジェクトデータとを前記端末装置へ送信するプロジェクトデータ送信部と、
を備えることを特徴とするサーバ装置。 - 請求項5に記載のサーバ装置とともにデータ配信システムを構成する前記端末装置であって、
前記サーバ装置から前記プロジェクトデータを取得するプロジェクトデータ取得部と、
前記プロジェクトデータ取得部が取得したプロジェクトデータをエンジニアリングツールを使用して前記機器に書き込むプロジェクトデータ書込部と、
前記プロジェクトデータ取得部が取得したプロジェクトデータの前記機器への書き込みに使用する前記エンジニアリングツールのバージョンが適切か否かを確認するツールバージョン確認部と、
を備えることを特徴とする端末装置。 - 前記プロジェクトデータ取得部が取得する前記プロジェクトデータには、プロジェクトデータの書き込みで使用することが可能な前記エンジニアリングツールのバージョンの情報が含まれ、
前記ツールバージョン確認部は、前記プロジェクトデータ取得部が取得したプロジェクトデータに含まれる前記情報が示すバージョンが、前記プロジェクトデータ書込部が使用しているエンジニアリングツールのバージョンと異なる場合、前記プロジェクトデータ書込部が使用しているエンジニアリングツールの更新が必要と判断する、
ことを特徴とする請求項6に記載の端末装置。 - 複数の機器で構成される装置の前記機器にプロジェクトデータを書き込む端末装置へ前記プロジェクトデータを配信するデータ配信方法であって、
前記プロジェクトデータが登録されるデータベースを備えたサーバ装置が、前記端末装置から前記プロジェクトデータの配信要求を受信する第1のステップと、
前記サーバ装置が、前記配信要求で指定されたプロジェクトデータが書き込まれる前記機器とともに1つの装置を構成する他の前記機器である関連機器を特定する第2のステップと、
前記サーバ装置が、前記配信要求で指定されたプロジェクトデータのバージョンと、前記関連機器に書き込まれているプロジェクトデータのバージョンと、に基づいて、プロジェクトデータの更新が必要な前記関連機器を特定する第3のステップと、
前記サーバ装置が、前記配信要求で指定されたプロジェクトデータと、前記第3のステップで特定した前記関連機器に書き込むプロジェクトデータとを前記端末装置へ送信する第4のステップと、
を含むことを特徴とするデータ配信方法。 - 複数の機器で構成される装置の前記機器に書き込まれるプロジェクトデータを保持するサーバ装置と、
前記サーバ装置から前記プロジェクトデータを取得して前記機器に書き込む端末装置と、
を備えるデータ配信システムであって、
前記サーバ装置は、
前記プロジェクトデータおよび前記プロジェクトデータが書き込まれるデータベースと、
前記端末装置から前記プロジェクトデータの配信要求を受信すると、前記配信要求で指定されたプロジェクトデータが書き込まれる前記機器とともに1つの装置を構成する他の前記機器である関連機器を特定する関連機器特定部と、
前記配信要求で指定されたプロジェクトデータのバージョンと、前記関連機器に書き込まれているプロジェクトデータのバージョンと、に基づいて、プロジェクトデータの更新が必要な前記関連機器を特定する更新対象関連機器特定部と、
前記配信要求で指定されたプロジェクトデータと、前記更新対象関連機器特定部で特定された前記関連機器に書き込むプロジェクトデータとを前記端末装置へ送信するプロジェクトデータ送信部と、
を備え、
前記端末装置は、
前記配信要求を前記サーバ装置へ送信して前記サーバ装置から前記プロジェクトデータを取得するプロジェクトデータ取得部と、
前記プロジェクトデータ取得部が取得したプロジェクトデータをエンジニアリングツールを使用して前記機器に書き込むプロジェクトデータ書込部と、
前記プロジェクトデータ取得部が取得したプロジェクトデータの前記機器への書き込みに使用する前記エンジニアリングツールのバージョンが適切か否かを確認するツールバージョン確認部と、
を備えることを特徴とするデータ配信システム。
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE112021005779.0T DE112021005779T5 (de) | 2021-05-12 | 2021-05-12 | Datenversandprogramm, Servervorrichtung, Endvorrichtung, Datenversandverfahren und Datenversandsystem |
JP2021557859A JP7069431B1 (ja) | 2021-05-12 | 2021-05-12 | データ配信プログラム、サーバ装置、端末装置、データ配信方法およびデータ配信システム |
PCT/JP2021/018062 WO2022239150A1 (ja) | 2021-05-12 | 2021-05-12 | データ配信プログラム、サーバ装置、端末装置、データ配信方法およびデータ配信システム |
US18/039,966 US11835937B2 (en) | 2021-05-12 | 2021-05-12 | Non-transitory computer readable medium storing data distribution program, server apparatus, terminal apparatus, and data distribution system |
CN202180088747.5A CN116670599A (zh) | 2021-05-12 | 2021-05-12 | 数据传送程序、服务器装置、终端装置、数据传送方法以及数据传送系统 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/018062 WO2022239150A1 (ja) | 2021-05-12 | 2021-05-12 | データ配信プログラム、サーバ装置、端末装置、データ配信方法およびデータ配信システム |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022239150A1 true WO2022239150A1 (ja) | 2022-11-17 |
Family
ID=81607969
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/018062 WO2022239150A1 (ja) | 2021-05-12 | 2021-05-12 | データ配信プログラム、サーバ装置、端末装置、データ配信方法およびデータ配信システム |
Country Status (5)
Country | Link |
---|---|
US (1) | US11835937B2 (ja) |
JP (1) | JP7069431B1 (ja) |
CN (1) | CN116670599A (ja) |
DE (1) | DE112021005779T5 (ja) |
WO (1) | WO2022239150A1 (ja) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006018359A (ja) * | 2004-06-30 | 2006-01-19 | Sony Corp | クライアントサーバシステム、クライアント端末、更新情報提供サーバ、更新処理プログラム、及び更新情報提供プログラム |
WO2015083243A1 (ja) * | 2013-12-03 | 2015-06-11 | 三菱電機株式会社 | エンジニアリングツールプログラムおよびネットワークシステム |
WO2016166799A1 (ja) * | 2015-04-13 | 2016-10-20 | 三菱電機株式会社 | 制御システム及びプログラマブルロジックコントローラ |
JP2017187888A (ja) * | 2016-04-04 | 2017-10-12 | 京セラドキュメントソリューションズ株式会社 | ファームウェア更新システムおよびファームウェア更新プログラム |
JP2019020798A (ja) * | 2017-07-12 | 2019-02-07 | 富士通株式会社 | 情報処理装置およびプログラム |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6167563A (en) * | 1998-09-17 | 2000-12-26 | Unisys Corporation | Method and system for building components in a framework useful in developing integrated business-centric applications |
US7082457B1 (en) * | 2000-11-01 | 2006-07-25 | Microsoft Corporation | System and method for delegation in a project management context |
JP2003005991A (ja) | 2001-06-25 | 2003-01-10 | Toshiba Tec Corp | ファームウェアアップデートシステム、ファームウェア配信プログラムおよび電子機器 |
JP6851708B2 (ja) | 2014-08-28 | 2021-03-31 | 株式会社アイ・オー・データ機器 | ネットワークシステムおよびネットワーク方法 |
US11226985B2 (en) * | 2015-12-15 | 2022-01-18 | Microsoft Technology Licensing, Llc | Replication of structured data records among partitioned data storage spaces |
US10560356B2 (en) * | 2016-07-14 | 2020-02-11 | International Business Machines Corporation | Assuring data correctness in non-stable network environment |
JP2018180722A (ja) | 2017-04-06 | 2018-11-15 | 株式会社東芝 | データ管理システム |
JP6610639B2 (ja) | 2017-10-03 | 2019-11-27 | 株式会社安川電機 | ソフトウェア管理システム、ソフトウェア更新装置、ソフトウェア更新方法、及びソフトウェア更新プログラム |
US11308447B2 (en) * | 2020-04-02 | 2022-04-19 | Rockwell Automation Technologies, Inc. | Cloud-based collaborative industrial automation design environment |
-
2021
- 2021-05-12 WO PCT/JP2021/018062 patent/WO2022239150A1/ja active Application Filing
- 2021-05-12 DE DE112021005779.0T patent/DE112021005779T5/de active Pending
- 2021-05-12 CN CN202180088747.5A patent/CN116670599A/zh active Pending
- 2021-05-12 JP JP2021557859A patent/JP7069431B1/ja active Active
- 2021-05-12 US US18/039,966 patent/US11835937B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006018359A (ja) * | 2004-06-30 | 2006-01-19 | Sony Corp | クライアントサーバシステム、クライアント端末、更新情報提供サーバ、更新処理プログラム、及び更新情報提供プログラム |
WO2015083243A1 (ja) * | 2013-12-03 | 2015-06-11 | 三菱電機株式会社 | エンジニアリングツールプログラムおよびネットワークシステム |
WO2016166799A1 (ja) * | 2015-04-13 | 2016-10-20 | 三菱電機株式会社 | 制御システム及びプログラマブルロジックコントローラ |
JP2017187888A (ja) * | 2016-04-04 | 2017-10-12 | 京セラドキュメントソリューションズ株式会社 | ファームウェア更新システムおよびファームウェア更新プログラム |
JP2019020798A (ja) * | 2017-07-12 | 2019-02-07 | 富士通株式会社 | 情報処理装置およびプログラム |
Non-Patent Citations (1)
Title |
---|
MATSUMOTO, HIDEHIKO : "Motion controller engineering environment ''MT Developer2''", MITSUBISHI ELECTRIC TECHNICAL REPORT, vol. 81, no. 4, 25 April 2007 (2007-04-25), JP , pages 29 - 32, XP009541419, ISSN: 0369-2302 * |
Also Published As
Publication number | Publication date |
---|---|
JP7069431B1 (ja) | 2022-05-17 |
US11835937B2 (en) | 2023-12-05 |
JPWO2022239150A1 (ja) | 2022-11-17 |
DE112021005779T5 (de) | 2024-01-04 |
CN116670599A (zh) | 2023-08-29 |
US20230350379A1 (en) | 2023-11-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7373643B2 (en) | Apparatus, methods and articles of manufacture for data transmission | |
JP6039621B2 (ja) | ロード可能な航空機用ソフトウェアパーツ(lsap)を配信する方法及び装置 | |
US7302558B2 (en) | Systems and methods to facilitate the creation and configuration management of computing systems | |
US9104574B2 (en) | System and method for software application remediation | |
CN106575227B (zh) | 自动软件更新框架 | |
US20060271553A1 (en) | Document management system and method | |
JP2011113391A (ja) | 機器管理システム、機器管理装置、管理対象機器、ソフトウェア更新方法、ソフトウェア更新プログラム、及びそのプログラムを記録した記録媒体 | |
US20130235407A1 (en) | Information processing system, management method, and storage medium | |
US8775552B1 (en) | Methods and systems for distribution of technical manuals | |
US20220004379A1 (en) | System and method for secure peer deployment of software to networked devices | |
KR20170131551A (ko) | 시스템 설계 지원 장치, 시스템 설계 지원 방법 및 시스템 설계 지원 프로그램 | |
US11669573B2 (en) | Data management system | |
CN106339176B (zh) | 中间文件处理方法、客户端、服务器和系统 | |
WO2022239150A1 (ja) | データ配信プログラム、サーバ装置、端末装置、データ配信方法およびデータ配信システム | |
WO2016080268A1 (ja) | 処理条件管理システムおよび生産システム | |
EP2711836B1 (en) | Data distribution system | |
JP2005063420A (ja) | コンテンツ配信サーバ、通信端末、コンテンツ配信システム、コンテンツ配信方法、コンテンツ配信プログラム、端末制御プログラムおよび該プログラムを記録した記録媒体 | |
JP2018180722A (ja) | データ管理システム | |
TWI466049B (zh) | 客製化生產(cto)軟體部署及管理 | |
EP3780551A1 (en) | Method and system for managing assets in a cloud computing environment | |
JP2005006370A (ja) | ディジタル形保護継電器のデータ更新方法 | |
JP7456507B2 (ja) | 情報流通装置、情報流通方法及びプログラム | |
US7644306B2 (en) | Method and system for synchronous operation of an application by a purality of processing units | |
US20180267492A1 (en) | Method and System For An Automated Configuration Of An Industrial Controller | |
US20080228840A1 (en) | Data updating method and data processing system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2021557859 Country of ref document: JP Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21941884 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 112021005779 Country of ref document: DE Ref document number: 202180088747.5 Country of ref document: CN |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 21941884 Country of ref document: EP Kind code of ref document: A1 |