Numerical controller and computer-readable storage medium

Abstract

The numerical controller includes: an operation request reception unit that receives an operation request from an operator; and a division determination unit that manages approval information that is setting information for an operation right for data for which an operation request is to be operated. The approval information includes a partition of an operator that has generated an operation authority for the operator, a partition of a restriction subject, which is an operator whose operation authority is restricted, and content that restricts an operation to which the subject has an authority, and if the operator that has output an operation request for editing the operation authority is a manager, the operator that has output the operation request for editing the operation authority. If the division of the operator who has output the operation request is the same as the division of the operator who has generated the operation authority, the division determination unit permits editing of the operation authority.

Description

Technical Field

[0001] The present disclosure relates to a numerical control device and a computer-readable storage medium. Background Art

[0002] Conventionally, industrial machines in factories have controllers that have a function of limiting user access based on the operator's operation authority level. For example, see Patent Document 1.

[0003] Prior art literature

[0004] Patent Literature

[0005] Patent Document 1: Japanese Patent Application Laid-Open No. 2012-13731 Summary of the Invention

[0006] Problems to be solved by the invention

[0007] During the manufacturing process of machine tools, for example, embedded devices such as servo motors and inverters, peripheral equipment such as coolants and loaders, sensors, and numerical controllers are installed, parameters are set, and programs are generated to customize the machine tools to achieve the desired functions. Furthermore, after the machine tools are completed, they are often operated by multiple operators for maintenance.

[0008] Machine tool operators set parameters and create programs. Manufacturers need to protect the parameters, programs, and other data set by their operators.

[0009] Furthermore, organizations other than manufacturers, such as system integrators and suppliers, also have a need to protect data generated by their own workers.

[0010] In the field of numerical control devices, it is desirable to manage access rights to data related to the creation of machine tools.

[0011] Means for solving problems

[0012] A numerical control device as one embodiment of the present invention includes: an operation request accepting unit that accepts an operation request from an operator; and a division determination unit that manages approval information, wherein the approval information is setting information of the operation authority for data set as an operation object for the operation request, the approval information including: the division of the operator for whom the operation authority for the operator is generated, the division of the operator who is restricted due to the operation authority, i.e., the restriction object, and the content of the operation for which the restriction object has authority. In a case where the operator who outputs the operation request to edit the operation authority is an administrator, if the division of the operator who outputs the operation request is the same as the division of the operator who generated the operation authority, the division determination unit permits the editing of the operation authority. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 It is a data structure diagram of operator information.

[0014] Figure 2 This is a schematic diagram showing the operators associated with the machine tool.

[0015] Figure 3 This is a block diagram of the numerical control device according to this embodiment.

[0016] Figure 4 This is a diagram of the data structure of the approval information.

[0017] Figure 5 This is a flowchart showing the operation of the segmentation determination unit.

[0018] Figure 6 This is a data structure diagram of operator information and approval information.

[0019] Figure 7 It is an explanatory diagram showing the determination result of the operation request.

[0020] Figure 8 This is a flowchart showing the operation of the division determination unit.

[0021] Figure 9 This is the hardware structure diagram of the numerical control device. DETAILED DESCRIPTION

[0022] The following describes the numerical controller 100. The numerical controller 100 stores parameters and programs used to cause a machine tool to perform machining operations. These parameters and programs are created, referenced, and edited by operators in various roles, including machine tool manufacturers, embedded device and peripheral equipment manufacturers, equipment manufacturers that manufacture the numerical controller 100, system integrators, suppliers, and machine users who use the machine tools for machining.

[0023] The operator's access rights are managed by the administrator. The administrator has administrator privileges. The presence and classification of administrator privileges for operators are specified in the operator information. Data operation privileges are specified in the authorization information. Here, data refers to information stored within the numerical controller 100. Data refers to data stored in a file or memory such as RAM, recorded in some format.

[0024] The division represents the position of the operator (the company to which the operator belongs, etc.). In the numerical controller 100 , by setting divisions for all operators including managers, it is possible to manage the authority of each position related to the machine tool.

[0025] Reference Figure 1 The conventional operator information and the operator information of this embodiment are described with reference to examples.

[0026] Conventional operator information categorizes operators into groups. Operator groups include managers and operators (non-managers). Managers can edit and approve operator information using their manager permissions. "Operator" permissions are governed by the manager's settings.

[0027] In conventional operator information, if multiple operators belonging to the administrator group are set, there arises a problem in that the operation authority of data generated by an operator in a certain position can be changed by an administrator group in another position.

[0028] In this embodiment, the operator information is provided with a division item, which enables management of the operation authority according to the standpoint of the operator who created the data.

[0029] right Figure 1 The operator information includes the identification information of the operator, the operator group, and the operator classification. Figure 1 The operator information includes "Operator A," "Operator B," "Operator C," and "Operator D." A "Group" is assigned to each operator. "Operator A" and "Operator C" are "Managers," while "Operator B" and "Operator D" are "Operators." Managers are granted manager authority.

[0030] In addition to groups, operators are also categorized into divisions. Figure 1 In the operator information, "Operator A" and "Operator B" are divided into "Machine Manufacturer", and "Operator C" and "Operator D" are divided into "Machine User". Division refers to the operator's position (company, etc.). The location of data operation authority can also be matched with the division. Figure 1 In the example, the division is set according to the organization (company) to which the operator belongs.

[0031] Operators can be divided into three categories: upper managers, division managers, and operators (refer to Figure 2 ). The upper manager understands the position of the operator related to the machine tool (organization, ownership of data operation authority, etc.) and generates initial operator information. Information about the operator's position can be obtained from the machine tool's design document, specification document, contract document, production process document, etc. The upper manager is, for example, a numerical control device manufacturer, a system integrator, etc. The upper manager infers a single or multiple positions (organizations) related to the machine tool controlled by the numerical control device and generates operator information. Set the division manager in the operator information. The division manager manages the data associated with its own division (position).

[0032] exist Figure 1In the example, "Operator A" is a partition manager belonging to the partition "Machine Manufacturer" and "Operator C" is a partition manager belonging to the partition "Machine User".

[0033] In addition, Figure 1 In the operator information, there is only one "machine manufacturer", but when a machine tool is actually created, there may be multiple "machine manufacturers". In addition to "machine manufacturers", there may be various types of operators such as "equipment manufacturers", system integrators, and suppliers of numerical control devices.

[0034] Both the upper manager and the division manager have manager authority, but the manager authority of the division manager is limited to the division itself.

[0035] Operators do not have administrator privileges. Operations performed by operators are called general operations. General operations refer to operations on data other than those restricted by administrator privileges, such as operator information and authorization information.

[0036] Figure 3 1 is a block diagram of a numerical controller 100 according to the present embodiment. The numerical controller 100 includes an operation request accepting unit 11 , an authenticating unit 12 , an operation request executing unit 13 , a division determining unit 14 , and an attribute managing unit 15 .

[0037] Furthermore, the components of the numerical controller 100 are classified according to their functions, and may not be clearly divided in terms of physical structure or program structure.

[0038] The operation request accepting unit 11 accepts operation requests from an information processing device such as a PC or server connected to the numerical controller 100, or from an input unit (described later) of the numerical controller 100. These operation requests are requests for accessing data within the numerical controller, such as referencing, creating, or editing data. The operation request includes identification information of the operator making the operation request, identification information of the data being operated on (identification information of the indicated data, type and path of the file containing the data, etc.), and the details of the requested operation.

[0039] The authentication unit 12 authenticates the operator who has made the operation request. Conventional methods are used for authentication. The operator enters his or her identification information. The authentication unit 12 authenticates the operator as the operator corresponding to the input identification information. This authentication allows the operator to be uniquely identified.

[0040] The operation request execution unit 13 executes the requested operation when the segmentation determination unit 14 permits the operation request. The operation includes reference, creation, and editing of data.

[0041] The classification determination unit 14 determines whether to deny or permit an operation request based on the operator classification. The classification determination unit 14's determination method will be described based on the types of operation requests: [1. Editing authorization information / adding operation permissions], [2. Editing operator information / generating initial operator information], [3. Generating new data], and [4. General operations].

[0042] [1. Addition of editing / operation permissions for authorized information]

[0043] If the requested operation is "Edit Approval Information," the classification determination unit 14 refers to the operator information and reads the group and classification of the operator who issued the operation request. If the operator's group is "Operator," the classification determination unit 14 determines that the operator does not have permission to edit approval information and rejects the operation request. If the operator's group is "Administrator," the classification determination unit 14 proceeds to the next step.

[0044] Authorization information associates data with the operating permissions of an operator (referred to as a restricted user). The operating permissions include the divisions of operators for whom the operating permissions are set. Upon receiving an operation request to edit authorization information, the division determination unit 14 determines whether the operating permissions for the data specified in the operation request have been set. If not, the generation of operating permissions is permitted. If the operating permissions for the data specified in the operation request have been set, the division of the operator for whom the operating permissions have been set is compared with the division of the operator who issued the operation request. If the divisions are identical, the editing of the operating permissions is permitted.

[0045] Set the operation authority in the authorization information. Figure 4 , the structure of the approval information is explained in detail. Figure 4 The approval information includes the division of managers who set the operation authority, the division and group of operators (restricted persons) who are subject to operation authority restrictions, information that determines the data that is subject to restrictions (data type, data identification information, data path, folder containing data, etc.), operation content, and operation authority of the restricted persons.

[0046] Figure 4 The first row of the table's operation permissions lists the administrator's group as "Machine Manufacturer." This permission limits the "reference" operation to "ladder program" data, but denies the "edit" operation to operators whose group is "Administrator" and whose group is "Machine User."

[0047] The second row of operation permissions has the "Machine Manufacturer" category for the administrator. This permission restricts the "Ladder Program" data to "Reference" for operators in the "Operator" group and "Machine User" category. The "Edit" operation is permitted for the "Ladder Program" data.

[0048] The third row of operation permissions has the administrator category "Machine User." This permission restricts operators who are grouped as "Operator" and classified as "Machine User" to "Reference" and "Edit" operations on "Parameter" data.

[0049] The operation rights in the fourth to sixth rows are different from those in the first to third rows. The operation rights in the fourth to sixth rows are affected by the operation rights of the "machine user" category of the operator who generated the data.

[0050] The fourth row of operation permissions has the administrator category "Machine User." This permission restricts the user whose group is "Administrator" and whose operator category is "Machine Manufacturer" to "Reference" and "Edit" operations for the "Machine User Generated Machining Program" data.

[0051] The fifth row of operation permissions lists the administrator category as "Machine User." This permission restricts the "Worker" group and the "Machine Manufacturer" operator category from performing the "Reference" and "Edit" operations for the "Machine User Generated Machining Program" data.

[0052] The sixth row of operation permissions has the administrator category "Machine User." This permission allows the "reference" operation for the "Machine User Create Machining Program" data, but denies the "edit" operation, for users whose group is "Administrator" and who are subject to restrictions under the "Machine User" category.

[0053] Reference Figures 5 to 7 The operation of the division determination unit 14 will be described. Figure 5 is a flowchart showing the operation of the division determination unit 14. Figure 6 This is an example of operator information and authorization information. Figure 7 The result of determination of the operation request of operator A and operator C is shown. In the following description, it is assumed that an edit request of the approval information is received as the operation request.

[0054] The operation request accepting unit 11 accepts the operation request (step S1), and the authenticating unit 12 authenticates the operator (step S2). Using the operator identification information acquired during authentication, the operator information is referenced. If the operator is a "division manager" (step S3: Yes), the division determination unit 14 searches for authorization information using the data specified in the operation request as a key.

[0055] If the operation authority has been set for the data specified by the operation request (step S4: Yes), the division determination unit 14 compares the division of the operator who generated the operation authority with the division of the operator who issued the operation request. If the division of the operator who generated the operation authority matches the division of the operator who issued the operation request (step S5: Yes), the operator is allowed to edit the operation authority for the data specified by the operation request (step S6). If the division of the operator who has set an existing operation authority does not match the division of the operator who issued the operation request (step S5: No), editing of the operation authority is denied (step S7).

[0056] Furthermore, in step S4 , when the operation authority is not set in the data for which the operator requests setting of the operation authority (step S4 ; No), the division determination unit permits addition of new operation authority to the data (step S8 ).

[0057] Furthermore, in step S3 , when the operator is not a division manager (or a higher-level manager) (step S3 ; No), the division determination unit 14 rejects editing of the operation authority (step S7 ).

[0058] Reference Figure 6 and Figure 7 , the operation of the division determination unit 14 will be described in detail.

[0059] Figure 6 Example showing operator information and approval information, Figure 7 Indicates the determination result of the operation request for editing the operation authority of operator A and operator B.

[0060] First, the operator A's group is "Administrator" and is divided into "Machine Manufacturer". In the operator information, the operator A is defined as the "Division Administrator" of the "Machine Manufacturer" division. As an operation request, the operator A requests to edit the operation authority of the data "Ladder Program". In contrast, the division determination unit 14 searches for the approval information using the data "Ladder Program" as a keyword. Figure 6 In the approval information, the user has already been assigned permission to operate the "ladder program" data. The partition of the partition manager who has assigned permission to operate the "ladder program" data is "Machine Manufacturer." The partition determination unit 14 compares the partition "Machine Manufacturer" of the operator who has assigned permission to operate the "ladder program" data with the partition "Machine Manufacturer" of operator A who requested the operation. The comparison results in a match between the two partitions. Therefore, the partition determination unit 14 denies operator A's permission to edit the "ladder program" data.

[0061] When the operator A requests the setting of the operation authority of the data "machine user generates processing program" as the operation request, the division determination unit 14 searches the authorization information using the data "machine user generates processing program" as a key. Figure 6 In the approval information, the user has already been assigned permission to operate the data "Machine User Creates Processing Program." The division of the division manager who has assigned permission to operate the data "Machine User Creates Processing Program" is "Machine User." Division determination unit 14 compares the division "Machine User" of the operator who has assigned permission to operate the data "Machine User Creates Processing Program" with the division "Machine Manufacturer" of operator A who requested the operation. The comparison reveals that the two divisions do not match. Therefore, division determination unit 14 denies operator A's permission to edit the data "Machine User Creates Processing Program."

[0062] When operator A requests permission to operate the data "Machine Manufacturer Generates Processing Programs" as an operation request, the division determination unit 14 searches for authorization information using the data "Machine Manufacturer Generates Processing Programs" as a keyword. The search results show that the division for the administrator who has already set permission for the data "Machine Manufacturer Generates Processing Programs" and the division for the administrator who has set permission for the data "Machine User Generates Processing Programs" is "Machine Manufacturer." The division determination unit 14 compares the division "Machine Manufacturer" of the operator who has set permission for the data "Machine User Generates Processing Programs" with the division "Machine Manufacturer" of operator A who requested the operation. The comparison results show that the two divisions match. Therefore, the division determination unit 14 permits operator A to edit the permission for the data "Machine Manufacturer Generates Processing Programs."

[0063] If operator A requests permission to operate the data "error correction" as an operation request, the division determination unit 14 searches the authorization information using the data "error correction" as a key. The search results show that permission to operate the data "error correction" has not been set. Therefore, the division determination unit 14 permits operator A to add permission to operate the data "error correction."

[0064] The above describes the operation of the division determination unit 14 in response to the operation request (editing of approval information) from operator A. The operation request (editing of approval information) from operator C is the same as that from operator A, and therefore, description thereof will be omitted.

[0065] [2. Editing operator information / generating initial operator information]

[0066] Before explaining how to manipulate operator information, it is assumed that initial operator information is stored in the numerical controller 100 through some means. This initial operator information is generated by a higher-level administrator. The higher-level administrator understands the operator's position regarding the machine tool controlled by the numerical controller 100. The higher-level administrator generates segmented operator information that categorizes operators into their respective positions. The initial operator information generated by the higher-level administrator is referred to as initial operator information. The higher-level administrator and segmented administrator have the authority to edit operator information.

[0067] When the division manager instructs the operator information to add an operator, the division determination unit 14 assigns the division manager's division to the operator's division. For example, if the division manager's division is "machine manufacturer," the division determination unit 14 assigns the operator's division added to the operator information to the same "machine manufacturer" as the division manager who added the operator.

[0068] When receiving an operation request from operator information, the division determination unit 14 determines whether the operator has the authority to operate the operator information. The division determination unit 14 reads the operator's group and division, and if the operator is a division manager, allows operation of the operator information of the same division as the division manager.

[0069] [3. New generation of data]

[0070] New data generated by an operator can also be associated with the division of the operator who generated the data. This association is performed by the attribute management unit 15. The attribute management unit 15 refers to the operator information, obtains the division of the operator who generated the data, and associates the division of the operator who generated the data with the data.

[0071] For example, Figure 6 The "Machine User Generated Processing Program" is associated with the "Processing Program" data and the "Classification (Machine User)" of the operator who created the data. This allows the "Classification (Machine User)" of the operator who created the data to be used to limit operational permissions. For example, management can be implemented to prevent other "Machine Manufacturers" from "referencing" data created by a particular "Machine Manufacturer."

[0072] The classification can be added to the data as attribute information or managed centrally using a table. Alternatively, instead of assigning classification to the data, the operator can be associated with the data. By associating the operator with the data, the classification of the operator who generated the data can be determined based on the operator information.

[0073] [4. General Operation]

[0074] Here, general operations refer to operations on data other than those restricted by administrator authority, such as operator information and authorization information. Examples of such data include "machining programs" and "parameters." These are data used to achieve the performance, functions, and purpose of machine tools. This data is generated by operators in their roles related to the machine tools.

[0075] If the operation request is a general operation, the classification determination unit 14 determines the classification of the operator who made the operation request (referred to as a restricted user). As described above, the classification of restricted users is set in the approval information. The classification determination unit 14 reads the operation authority of the restricted user set in the data received for the operation request from the approval information. Based on the read operation authority of the restricted user, the classification determination unit 14 determines whether to permit or deny the operation on the restricted user's data.

[0076] Reference Figure 8 The operation of the above-mentioned division determination unit 14 will be described.

[0077] The operator outputs an operation request, and the authentication unit 12 authenticates the operator who has issued the operation request.

[0078] When the operation request is "editing of approval information" (step S11), the operation request includes identification information of the data to be operated. The division determination unit 14 determines whether the operation authority of the data specified by the operation request has been set (step S12). In addition, the division determination unit 14 refers to the operator information to determine whether the operator is a division manager. If the operation authority of the data has been set (step S12; yes) and the division of the operator who generated the operation authority is the division of the operator who output the operation request, the division determination unit 14 allows the editing of the operation authority (step S13). If the operator's division is different, the editing of the operation authority is rejected (step S14).

[0079] If the operation authority for the data specified by the operation request is not set (step S12: No), and the operator is a segment manager, the segment determination unit 14 permits the addition of the operation authority for the data specified by the operation request (step S15). The segment determination unit 14 grants the segment of the operator who created the added data the operation authority.

[0080] If the operation request is "Edit Operator Information" (step S21), the division determination unit 14 determines whether the operator who issued the operation request is a division administrator. If the operator is a division administrator, operation of operator information for the same division is permitted (step S22). Alternatively, if the operator is a higher-level administrator, operation of operator information may be permitted regardless of the division. The authority of higher-level administrators to manipulate operator information can also be changed according to settings.

[0081] If the operation request is "new data creation" (step S31), the attribute management unit 15 refers to the operator information and determines the category of the operator who issued the operation request. The attribute management unit 15 associates the category of the operator who created the data with the data (step S32).

[0082] If the operation request is a "normal operation" (step S41), the segment determination unit 14 refers to the operator information and determines the group and segment of the operator who issued the operation request. The operation authority for normal operations is set in the approval information. The segment determination unit 14 reads the data to be operated, the segment and group of the operator who issued the operation request, and the details of the requested operation from the approval information, and determines whether to approve or deny the operation request (step S42).

[0083] As described above, the numerical controller 100 of this embodiment categorizes operators who manipulate data within the numerical controller 100 using the term "division." Administrators categorized into divisions are referred to as division administrators. Division administrators are granted administrator authority for their divisions. The division determination unit 14 limits the authority of division administrators to those within the same division. Division administrators manage operators within the same division using operator information, and administrators within the same division manage operational authority using authorization information.

[0084] In addition, the attribute management unit 15 associates the data generated by the operator with the operator's division. In this way, the "division" of the operator who generated the data can be used as a condition for the operation authority. Figure 6 In the example of "Machine User Generates Machining Program," the "Classification (Machine User)" of the operator who created the data (machining program) can be used to limit the data to be operated. This allows management to prevent other "Machine Manufacturers" from "referencing" data generated by a certain "Machine Manufacturer." Furthermore, operation permissions can be set on a folder-by-folder basis. For example, management can prevent other "Machine Manufacturers" from "referencing" folders created by a certain "Machine Manufacturer."

[0085] Initial operator information is generated by a higher-level administrator. The higher-level administrator understands the positions of operators related to machine tools (organization, data ownership, etc.) and sets administrators (division administrators) to manage information for each position.

[0086] Hereinafter, the hardware configuration of the numerical controller 100 will be described using the present disclosure. Figure 9 is a hardware structure diagram of the numerical control device 100. Figure 9As shown, the numerical controller 100 includes: a CPU 111 for overall control of the numerical controller 100, a ROM 112 for recording programs and data, and a RAM 113 for temporarily expanding data. The CPU 111 reads the system program recorded in the ROM 112 via a bus and executes avoidance according to the system program.

[0087] The nonvolatile memory 114 is backed up, for example, by a battery (not shown), and maintains its stored state even when the power to the numerical controller 100 is turned off. The nonvolatile memory 114 stores various data, such as programs read from an external device 120 via interfaces 115, 118, and 119, and user operations input via the input unit 30. The nonvolatile memory 114 may also store programs and data for executing the numerical controller 100 of this embodiment. Furthermore, the display unit 70 displays various data, measurement results, and the cause of improper data.

[0088] The interface 115 is an interface for connecting the numerical controller 100 and an external device 120 such as an adapter. Programs, various parameters, and the like are read from the external device 120.

[0089] The interface 118 is an interface for connecting the numerical controller 100 and a display unit 70 such as a liquid crystal display. The display unit 70 displays various data read into the memory, data obtained as a result of executing a program, and the like.

[0090] The interface 119 is an interface for connecting the numerical controller 100 to the input unit 30 such as a keyboard and a pointing device. The input unit 30 transmits commands, data, etc. in accordance with an operator's operation to the CPU 111 via the interface 119 .

[0091] While the present disclosure has been described in detail, the present disclosure is not limited to the various embodiments described above. These embodiments can be supplemented, replaced, altered, or partially deleted without departing from the scope of the present disclosure, or without departing from the scope of the present disclosure derived from the contents described in the scope of the claimed patent and its equivalents. Furthermore, these embodiments can also be implemented in combination. For example, in the above-described embodiments, the order of each action and the order of each process are shown as examples and are not limited thereto.

[0092] The following supplementary notes are also disclosed regarding the above-mentioned embodiment and modifications.

[0093] (Note 1)

[0094] A numerical control device (100) comprises: an operation request receiving unit (11) which receives an operation request from an operator; and a division determination unit (14) which manages approval information, wherein the approval information is setting information of the operation authority for data set as an operation object for the operation request, and the approval information includes the division of the operator who generates the operation authority for the operator, the division of the operator who is restricted by the operation authority, i.e., the restriction object, and the content of the operation for which the restriction object has authority. In the case where the operator who outputs the operation request to edit the operation authority is an administrator, if the division of the operator who outputs the operation request is the same as the division of the operator who generated the operation authority, the division determination unit (14) allows the editing of the operation authority.

[0095] (Note 2)

[0096] Regarding the numerical control device (100), when the operator who outputs an operation request for the operation authority included in the approval information is an administrator and the operator requests editing of the operation authority, if the division of the operator who outputs the operation request is different from the division of the operator who generated the operation authority, the division determination unit (14) rejects the editing of the operation authority.

[0097] (Note 3)

[0098] Regarding the numerical control device (100), the division determination unit (14) manages operator information that associates an operator, the presence or absence of the operator's administrator authority, and a division indicating the operator's position.

[0099] (Note 4)

[0100] Regarding the numerical control device (100), the division determination unit (14) manages so that the operator added to the operator information is the same as the division of the operator to whom the operator is added.

[0101] (Note 5)

[0102] Regarding the numerical control device (100), the approval information includes a generator of the data as information identifying the data.

[0103] (Note 6)

[0104] A computer-readable storage medium (112, 113, 114) stores computer-readable instructions for causing one or more processors (111) to execute the following processing: accepting an operation request from an operator, managing approval information, wherein the approval information is setting information of the operation authority for data set as an operation object for the operation request, the approval information including: the division of operators who generated the operation authority for the operator, the division of operators who are restricted due to the operation authority, i.e., restricted subjects, and the content of operations for which the restricted subjects have authority, the computer-readable storage medium stores instructions for executing the following processing: in a case where the operator who outputs the operation request to edit the operation authority is an administrator, if the division of the operator who outputs the operation request is the same as the division of the operator who generated the operation authority, then allowing the operator who made the operation request to edit the operation authority.

[0105] Description of Reference Numerals

[0106] 100 Numerical Control Device

[0107] 11 Operation Request Acceptance Department

[0108] 12 Certification Department

[0109] 13 Operation Request Execution Unit

[0110] 14 Division Judgment Unit

[0111] 15 Property Management Department

[0112] 111 CPU

[0113] 112 ROM

[0114] 113 RAM

[0115] 114 Non-volatile memory.

Claims

1. A numerical control device, characterized in that: The numerical control device comprises: an operation request accepting unit that accepts an operation request from an operator; and a division determination unit that manages authorization information, the authorization information being setting information of an operation authority for data set as an operation target for the operation request; The approval information includes: a classification of operators who have generated the operation authority for the operator, a classification of operators who are restricted due to the operation authority, i.e., restriction subjects, and contents of operations for which the restriction subjects have authority; If the operator who outputs the operation request to edit the operation authority is an administrator, the division determination unit permits editing of the operation authority if the division of the operator who outputs the operation request is the same as the division of the operator who generated the operation authority.

2. The numerical control device according to claim 1, wherein When the operator who outputs an operation request for the operation authority included in the approval information is an administrator and the operator requests editing of the operation authority, the division determination unit rejects editing of the operation authority if the division of the operator who outputs the operation request is different from the division of the operator who generated the operation authority.

3. The numerical control device according to claim 1, wherein The division determination unit manages operator information that associates an operator, whether or not the operator has administrator authority, and a division indicating the operator's position.

4. The numerical control device according to claim 3, wherein: The division determination unit manages so that the operator added to the operator information is assigned to the same division as the operator to whom the operator was added.

5. The numerical control device according to claim 4, characterized in that The authorization information includes a generator of the data as information identifying the data.

6. A computer-readable storage medium storing computer-readable instructions for causing one or more processors to execute the following processing: accepting an operation request from an operator; and managing approval information, wherein the approval information is setting information of the operation authority of the operation request for data set as an operation target, characterized in that The approval information includes: a classification of operators who have generated the operation authority for the operator, a classification of operators who are restricted due to the operation authority, i.e., restriction subjects, and contents of operations for which the restriction subjects have authority; The computer-readable storage medium stores a command for performing the following processing: in a case where the operator who outputs an operation request to edit the operation permission is an administrator, if the division of the operator who outputs the operation request is the same as the division of the operator who generated the operation permission, the operator who made the operation request is allowed to edit the operation permission.

Images