JP2019192276A - Iso certification acquisition support device and iso certification acquisition support method - Google Patents

Abstract

To acquire ISO certification to reduce the work for maintaining the same by focusing on the practice of activities.SOLUTION: An ISO certification acquisition support device developed based on the concept of dataless orientation that does not use electronic files for the "Manual" and "Procedure" group is provided. The configuration of the Website can be displayed dynamically in conjunction with the "Information and Activities in Documents", they can be approved from the registration while reviewing the plans and rules on each dedicated screen and PDCA can be developed on the screen. In the table filtered from each DB, the "slimming" of the "manual" and "procedure book" group (compressed to the conventional 1 to 2/10) and "automation" of various document generation and activity trails were realized, reducing the operational load, shortening of ISO construction, and making it easier to apply the document to education.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a system for obtaining ISO certification.

  Conventional software products have created "manuals", "procedure manuals", etc., in the system or as a single booklet in electronic files. In this case, since it is a method of uploading or referring to the system, when it is adopted in a system that implements two-party audit or an ISO integrated authentication system, the load of document creation becomes large and the amount of documents becomes enormous. .

JP 2002-197262 A

1. Due to the nature of ISO standards, it is not easy to streamline the document system.
The industry wisdom is documentary supremacy, and there is a tendency to focus on document refinement, strictness, and creation. The larger the quantity and number of pages in the “Manuals” and “Procedures” groups, the more difficult it is to understand the whole picture. ) And so on. When modifying or adding rules, the entire document may be looked down to ensure consistency, and inconsistencies between documents tend to occur.

  Due to these factors, it is not possible to take a mechanism of flexibly spiraling up and evolving in accordance with the improvement and changes in the situation required by the standard, which is the ideal form, and there is a tendency to become a rigid ISO that lacks flexibility. is there. For the purpose of promoting understanding, it is possible to create additional procedures and reference information according to each level, department, theme, and ISO integrated certification systems (ISMS, EMS, QMS, BCMS, FSMS) In this case, since it is necessary to prepare documents individually, the maintenance load is large.

2. Since PDCA of a considerable part of ISO activities cannot be expanded from the screen, it is necessary to create a document outside the system.
3. The traditional two-part audit is to answer, complete and evaluate questionnaires by sending paper documents for the number of suppliers. There is no system that can effectively perform audits through two-way communication in terms of the number of suppliers, audit technology, and workload.

  The ISO certification acquisition support device according to the present invention includes a procedure storage unit that identifies and stores a plurality of procedures described in accordance with ISO certification standards, and a plurality of action plans to be executed for each period, A plan data storage unit (plan DB) for identifying and storing each target person, selecting a target person, extracting a target person procedure corresponding to the target person from the plurality of procedures, and from the plurality of action plans The extraction unit for extracting the target person plan corresponding to the target person, and the target person procedure and the target person plan extracted by the extraction part for the selected target person, respectively, on one screen of a separate frame A plurality of procedures and plan data in which activity records are input for the target person procedure and the target person plan displayed by the display part, and the input result is stored in the procedure storage part. Comprising a reflecting unit for reflecting the plurality of action plan which is stored in 憶部, the.

  According to one aspect of the present invention, when obtaining ISO certification for manuals, etc., by making the common text about the minimum elements, the “manual” and “procedure manual” group is slimmed down, Can be compressed to 10. By automating various document generation and activity trails and dynamically linking content, PDCA can be managed for items described in the manual via the display screen. Therefore, it reduces the operational burden and simplifies education. As a result, it works effectively in shortening ISO construction. In addition, according to one form, the initial registration of know-how, FAQ, educational information, commentary, guidelines, etc. on the “Reference Information” screen can be done without the need for or minimized consulting support. Design your own rules freely and flexibly. Moreover, according to one form, it is possible to implement a remote audit function by providing a mechanism for assisting in-house audit technology without burdening the two-party audit. Furthermore, according to one form, it can respond to MSS accompanying the ISO common text without load of document creation.

Outline of design concept and system linkage Differences in document structure and content structure Explanatory drawing explaining the outline of each database System configuration including a two-party audit image-conceptual diagram Rule DB configuration Mechanism of dynamic linkage between various rules DB tables and documents Structure of plan / activity DB Plan / Activity DB table Standard DB configuration Standard DB table VTR button site screen The whole manual site screen Handbook site screen Operation regulation site screen Audit regulation site screen Site screen showing plans and reports for two-party audits Site screen showing audit checklist Approval document site screen Overview of systematization of ledger Construction and operation flow

(System overview)
The ISO authentication acquisition support apparatus according to the present embodiment is realized on a computer system, and includes a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), an image processing unit, and a memory. I have. The CPU, ROM, RAM, image processing unit, and memory are connected to each other via a bus.

  The CPU executes various processes according to a program recorded in the ROM or a program loaded from the memory to the RAM. The RAM appropriately stores data necessary for the CPU to execute various processes.

  The image processing unit includes a DSP (Digital Signal Processor), a VRAM (Video Random Access Memory), and the like, and performs various image processing on image data in cooperation with the CPU.

  The memory may be any storage medium such as a DRAM, a cache memory, a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory. The memory includes not only memory connected by a bus but also memory read / written via a drive. The data stored in the present embodiment will be described as being temporarily stored in this memory, both for temporary storage and for long-term storage using a nonvolatile memory.

  An input / output interface is connected to the ISO authentication acquisition support apparatus according to the present embodiment. A display unit, an imaging unit, an input unit, and a communication unit are connected via an input / output interface. The input unit includes various buttons and accepts user instruction operations. The communication unit controls communication performed with other devices via a network including the Internet.

  The ISO authentication acquisition support apparatus according to the present embodiment has the above-described configurations, but the functional configuration will be described later. Each functional configuration is functionally realized by the cooperative operation of the CPU, ROM, RAM, image processing unit, and memory. The function of each of these units is a module configuration provided by an electronic circuit or a program. The program is stored in the ROM and executed by cooperating with each unit while being appropriately read out by the CPU.

(Database overview)
The ISO certification acquisition support apparatus according to the present embodiment has, as its functional configuration, a procedure storage unit that identifies and stores a plurality of procedures in which a subject of a rule and items are described in accordance with ISO certification standards. (Rule DB). Further, a standard storage unit (standard DB) that stores standard data defining standards related to a plurality of procedures is further provided. In other words, each content of procedure, rule, and standard is designed by module design, and used as a standard / rule DB.

  In addition, a plan data storage unit (plan DB) for identifying and storing a plurality of action plans to be executed for each time period is provided. That is, the plan PLAN, execution DO, and evaluation CHECK are also converted into a DB (database) by the same method as described above, and the plan / execution DB (database) is obtained. Further, the apparatus further includes a reference information storage unit (reference information DB) that stores a plurality of reference information associated with each of a plurality of procedures stored in the procedure storage unit. The above procedure storage unit (rule DB), standard storage unit (standard DB), plan data storage unit (plan DB), and reference information storage unit (reference information DB) will be described simply as DB.

(Outline of filtering: Extraction unit)
Furthermore, an extraction unit is provided that selects a target person, extracts a target person procedure corresponding to the target person from a plurality of procedures, and extracts a target person plan corresponding to the target person from a plurality of action plans. An example of extraction processing by the extraction unit is filtering processing. In the authentication system, DB columns and record conditions are selected and specified, and multiple procedural documents for each standard are automatically filtered for each department, charge, and theme. Generate. On the site page, the rule DB and the plan DB are filtered, and multiple procedure documents for each standard are automatically generated for each department, charge, and theme by combining the tables using Iframe. Make it possible. Hereinafter, what is described as filtering processing of the present system is processing executed by the extraction unit of the present embodiment.

(Screen display overview: Display section)
Further, the system includes a display unit. A display part is implement | achieved as a display apparatus which displays the image image-processed by the image processing part of the previous day in this system. The display unit collectively displays the target person procedure and the target person plan extracted by the extraction unit for each selected target person on one screen of another frame.

  The display unit arranges each table filtered from the above two types of DBs on the site page in an iframe, thereby enabling search and matching between the tables in the site page and using it as a paper medium. When printing, the entire page is output at once. In addition, various plans and records (education plans, audit plans, overall plans, annual plans, correction reports, etc.) can be displayed as past documents in a table that is filtered based on the date and time in the DB. Make it unnecessary to keep the old version file. Hereinafter, what will be described as display processing of the present system is processing executed by the display unit of the present embodiment.

(PDCA overview: reflection section)
Furthermore, for the target person procedure and target person plan displayed by the display unit, an activity record is input, and the input result is stored in a plurality of procedures and plan data storage unit (plan DB) stored in the procedure storage unit (rule DB). A reflecting unit for reflecting the stored action plans is provided. With the reflection unit, PDCA can be deployed from the screen by placing an approval function on each dedicated screen. Hereinafter, all processes except the DB, filtering, and display process of this system are processes executed by the reflection unit of the present embodiment. In particular, processing relating to PDCA such as auditing and approval is executed by the reflection unit.

  According to the above ISO integrated certification acquisition and maintenance device, it is possible to search and collate between tables built in the DB, and the reflection between the modules built in the DB can be examined by the reflection unit. It becomes easy. In addition, by having a configuration that does not require consulting support or minimizes the arrangement of reference information in the DB, the reflection unit can share the same screen for two-party, three-party audits, and remote audits for internal audits. Two-way communication, trail display, audit standards, audit result setting and registration are simplified. In this way, PDCA can be deployed on each site, department, and theme by placing an administrator approval function on each site screen.

  By providing a database in which the site contents and the modules (columns) of each table are combined with a href, it becomes easy to understand the customer and respond to the examination through the reflection unit. In addition, two-party, three-party audits, and internal audits are conducted by remote audits, and screen sharing enables two-way communication and trail display, simplifying audit setting standards.

  According to the above configuration, PDCA can be expanded from the screen by implementing various automation engines, and (dataless) standards and procedures include shared modules. First, it is an authentication system that makes it easy to configure ISO integrated authentication for each customer because a change history is automatically generated with a single correction and a shared module is included. Implements two-party, three-party audit, and internal audit Authentication system. The outline of each of the above elements will be described in more detail.

  FIG. 1 shows an outline of the design concept and system linkage of the present embodiment. As shown in FIG. 1, a manual and related screens conforming to ISO standards are displayed on the display (upper left). The display unit displays the display screen by assigning the contents of the database of the rule DB, the plan DB, and the standard DB to the corresponding positions on the display screen. Therefore, by operating the rule DB, plan DB, and standard DB, the user not only displays the manual on the screen, but also plans the case to be executed, actually moves to execution, and executes it. The system confirms the result and corrects the trajectory, and the activity along the so-called PDCA cycle can be reflected in the system.

  In the conventional ISO-compliant procedure manual, the manual, general rules, system rules, operation rules, and various procedures shown in the upper right of FIG. 1 are listed as one booklet, which is very difficult to handle. In the present embodiment, data is stored in the rule DB, and this is filtered and displayed for each user attribute, and the confirmation result is prompted. Since the entire system is designed as a module rather than a conventional collection of simple documents, the data is made compact and automation is realized. In particular, the person in charge, the management layer, and the secretariat can easily realize that they receive “education, develop, undergo audits / examination, and keep a record of activities” simply by operating the buttons on the display screen.

  Conventionally, a huge amount of information had to be displayed, but according to the present embodiment, a substantially large amount of information is displayed on the minimum screen, and collation and search are possible.

  FIG. 2 explains the difference in document system / content structure and module design. For ISO-compliant procedure manuals, conventionally, a so-called pyramid-type document system has been adopted in which policies are placed at the top and rules, procedures, and records are placed at the bottom. In the present embodiment, the elements of the procedure manual are collected in each DB according to the minimum configuration of the basic part described in 5W1H. In other words, policies, manual rules, procedures, plans, records, and approvals are summarized as specific contents of documented information. After that, reference information, that is, reference, guidelines, explanations, own rules, FAQ, and other parts that are not particularly essential in the ISO standard are separated from the standard and configured in the reference DB. In this way, each element of the procedure manual is configured as a flat type.

  On the other hand, with regard to the content configuration, conventionally, when it is realized on a system, the content configuration is described directly on a site page and linked to a file server. In the present embodiment, the rule DB, the plan DB, and the standard DB are prepared as independent data groups, and the PDCA action for these is prepared as a PDCA module, and a link is formed between the modules and stored. As a result, the display unit facilitates operation and confirmation by displaying a combination of tables based on each of the rule DB, the plan DB, and the standard DB as separate frames on the display screen of the user.

  Conventionally, data is so-called static content that is saved by uploading for each file and displayed as it is saved. In the present embodiment, the form is a set of individual electronic files. This system is provided as a dynamic content that changes display items and operation items according to the user's state.

  FIG. 3 shows an overview of each database. According to the present embodiment, it is the rule DB, the plan DB, and the standard DB that are to be saved as procedure manuals, each having a different configuration. On the other hand, in addition to the manual part as the main body, each of these DBs has general rules, department rules, operational rules (D-execution), audit rules (C-inspection), approval (A-improvement), annual plan (P -Plan) and reference information, respectively, are filtered by the extraction unit. The extraction unit extracts the manual management TB (table) and the change history TB for the manual display operation as a result of the filtering, while the general regulation TB and the department regulation for the general regulation. Filling is done such as department regulation TB.

<Outline of each DB: Document hierarchy ⇒ DB ⇒ Dynamic linkage of information>
On the Web site, the “manual” is easily constructed as a database by adding SVO, 5WIH on the basis of a commercial standard, and is used as the basic part (relatively fixed part) of the standard. The slimming of the basic part makes it easy to grasp the whole picture. The concept of the document hierarchy is a flat hierarchy and is divided into the above part and the procedure + “reference information (fluid part)”. The initial placement of reference information (know-how, FAQ, educational information, commentary) in the reference DB makes consulting support unnecessary or minimized. Reference information can be easily added, deleted, and changed by users according to internal circumstances during operation, and it is not a requirement of the standard, so non-conformance can be prevented. This configuration eliminates the need for a template manual for each industry and business category.

  “Information in documents” and activities in the “manual” and “procedure manual” groups are made into modules, made into a database, and built into the system as a DB. By using the DB, overlapping portions of sentences can be deleted, which is effective in minimizing the document system. In the case of an ISO integrated certification system, create a common part for each ISO and add a page for each standard.

  When updating the "procedure manuals" group by the reflection unit, each procedure manual and related documents are linked with the update history by changing one location, so there is no inconsistency between the procedure manuals, and there is no management load for automation. Has been reduced. All site documents are managed in the approval list, and the name, date and time information of update, creation and approval are linked. Each element of “plan, activity, inspection, improvement” is configured in a plurality of databases in the same manner.

  Each table of the “Standard” DB includes “Standards such as ISMS, QMS, EMS”, “Declaration of Conformity”, “Internal Audit Standard”, “Two-Party Audit Standard”, and the like. Each table of the “rules and control measures” DB includes “manual”, “handbook”, “operation inspection”, “change history”, and the like. Each table in the “Plan / Activity” DB consists of “Overall Plan, Audit Plan, Monthly Plan, Actual, Next Plan”. Old versions, current, and future documents are centrally managed by date and time filtering by the extractor, eliminating the need to store them in files.

  FIG. 4 is a conceptual diagram of the overall system configuration to which the present system is applied. As shown in the figure on the left side, an ISO-compliant two-party audit system is installed on a server for each company, while a consultant has access authority to each company server and performs management. Each company's servers are accessed through registration / browsing by using the system corresponding to each company.

  The image of each company is as shown on the right side of FIG. The supplier of company A that installs the system is company D. When using this system for a two-party audit, the audit screen of the entire database is displayed with company A as the audit side and company D as the auditee. Access and give feedback.

  FIG. 5 shows the configuration of the rule DB. As shown in FIG. 5, each procedure is stored as a table in the rule database for each item shown in “Content”. For each procedure, the status such as the inspection state and various attribute information such as the category are stored in association with each other.

  FIG. 6A shows a mechanism of dynamic linkage between various tables in the rule DB and documents. By inputting each item shown in FIG. 6A, each procedure to be stored as a rule DB is registered. As an item of each procedure, there is an inspection month, which is an item for performing an inspection every input month. In this regard, the display unit automatically displays on the display screen as an item of an operation check table every time the month changes.

  Furthermore, by inputting each item about nonconformity, auditing, manual, and charge by checking the check box, the respective items are input and the DB is reconstructed. This makes it possible to create dedicated documents such as manuals, handbooks, auditing rules, etc. Further, as shown in FIG. 6A, specific contents are registered as management measures. Then, by checking the “change” check box, the contents can be input as the change history.

  FIG. 6B shows an automatic display of the operation check table. When the rule DB is registered as shown in FIG. 6A, the display unit automatically displays the operation check table shown in FIG. 6B every time the month changes. Since there are items that require a monthly check for work, the items that need to be checked are displayed as an operation check table shown in FIG. 6B in accordance with the registered items shown in FIG. 6A. Here, each item assigned ID 28, 31, 32 is a rule described in the manual, and the manual is constituted by a set of these rules.

  For example, in this case, the subject is described as being “in charge”, so that the subject subject to the rule is clarified and described. However, the subject must not be clearly included in the sentence. Although there is no subject, there is a clear rule that the entire employee is targeted, and the target of each rule in some way is clear. In other words, these rules are procedures, and manuals including the plurality of procedures are stored in each database.

  The target person is the target of the operation and rules corresponding to the filtering items, and for example, the secretariat, general employees, managers, managers, persons in charge and the like are illustrated. By selecting a target person and filtering from a number of procedures registered in the database, the target person procedure is selected, and the rules for each target person shown in FIGS. 6B to 6E are displayed. . The same applies to FIG.

  By inputting the activity record for the target person procedure and target person plan displayed by the display unit, the reflection unit stores the input result in the plurality of procedures stored in the procedure storage unit and the plan data storage unit. Reflect in multiple action plans. Here, the activity record is a record of an activity as a result of an action by an operation input by any one of the subjects of the system. For example, what recorded the execution content with respect to a plan, and what was recorded as a trail as a result of a simple click are included. The processing of the reflection unit will be described with reference to FIG. 6C.

  FIG. 6C shows a display screen when a user on the secretariat side creates a dedicated document such as a manual, a handbook, and an audit rule from a manual display on the top screen by a click operation. In the database, an item for displaying a trail may be provided by setting a link destination as an a href code among the items. A trail is an operation record for a database. For example, when a link is set on a manual and recorded in the database, and the user refers to the link destination by a click operation, the reflection unit performs the click operation. Record what you did as a trail. The audit will allow the trail to be confirmed at a later date.

  FIG. 6D shows an example of a dedicated document for the general employee handbag on the left side. FIG. 6E shows an automatic display of the correction list. By operation, the display unit automatically displays the correction list. FIG. 6F shows the audit rules above and shows the display screen after filtering for audit objectives, programs and responsibilities. Below is a change history display screen, and as shown in the right figure, an authorized person can approve the “change history” by clicking.

  FIG. 7A is a diagram showing an outline of a plan (activity) DB. Specifically, it consists of an overall plan TB, an audit plan TB, a monthly plan TB, an actual result TB, a next season plan TB, an education plan TB, a minutes TB, and the like. Each of these items is described as a single action plan, and a target vehicle plan for each target person is extracted by filtering for each target person. Each TB described above is the result of filtering. As shown in FIG. 7A, each procedure includes items of a target department, start and end times, title, target person, contents, and evaluation.

  FIG. 7B shows a plan DB input screen. The reflection unit reflects the following activity records in the database based on the input result. First, the operator inputs procedures one by one from the input screen shown in FIG. 7B and registers them in the plan DB. As the first input item, there is an evaluation. With this item, it is evaluated whether or not the manager has implemented the employee plan. Further, each item described in FIG. 7A is input. Although there is a title in the input item, a table according to the purpose such as overall plan, education plan, audit plan, operation plan by department by department is created by filtering (check only) by combination of title and target person be able to.

  Further, by inputting the start time and the end time and referring to the registered items, it is possible to display the past, present, and future of each plan. Therefore, according to the purpose of use in the combination method of each TB, according to the purpose of use, the rules for managers and monthly plans are provided at 01 site, the rules, general plans, actual results and evaluations of general employees are provided at 02 site, and the information system section at 03 site. In the 04 site, the rules, plans, results, evaluation, and approval at the time of operation can be displayed on the 04 site, and the rules, plans, results, evaluation, and approval at the time of the audit can be displayed on the 05 site, respectively.

  FIG. 8A is a diagram for explaining an outline of a table in the plan (activity) DB. When the current annual plan and results are selected, they are displayed on the display screen as shown in 1 company-wide annual plan in the upper left. Furthermore, depending on filtering, it is also possible to display the results as last year as shown in the upper right. By filtering by date, it is not necessary to hold past documents, and future documents can be centrally managed. As shown in the lower right, the annual plan for the next year may be displayed by date and time filtering.

  FIG. 8B is a diagram for explaining the outline of the table of the plan (activity) DB. The company-wide monthly plan is displayed in the upper left corner in the form of a monthly calendar. By clicking a predetermined item, the corresponding plan table is filtered and displayed as the annual depot annual plan. FIG. 8C shows a list of internal audit plans. By filtering the internal audit, the plan DB is displayed as shown in FIG. 8C. On the other hand, by filtering on the two-party audit, it is displayed as shown in the lower part of FIG. 8C.

  FIG. 9A shows an outline of the standard DB. The standard storage unit (standard DB) stores standard data that defines standards related to the above-described plurality of procedures. In the standard data, titles and management measures are listed for each item. The standard DB includes a standard TB, a declaration of conformity TB, an internal audit standard TB, and a two-party audit standard TB as a common database. Each of these TBs is extracted and displayed as a result of filtering.

  FIG. 9B shows a standard DB input screen. There are input items such as titles and management items, and items such as acceptance / rejection reasons, implementation, and audits are input via check boxes. The check box for audit includes various items such as internal management, internal charge, two-party audit, and information system. The screen is displayed according to the selected audit item, and input is accepted.

  FIG. 10A is a diagram illustrating each table of the standard DB. FIG. 10A particularly shows a collation standard DB table displayed on the home screen. FIG. 10B shows the application declaration TB in the upper table in the standard DB table. Each is created by selecting items from the standard DB. For each project, the stages of drafting, screening, and approval are shown as the stages of electronic approval, and approval is performed by check boxes as processing of the reflection unit. For each stage, the post of the approver, the name, and the date and time of approval are displayed in association with each other. Below FIG. 10B, specific corresponding contents of the standard DB are shown. In addition to titles, items / control measures, there are also reasons for adoption and implementation / non-execution. FIG. 10C shows an outline of a standard DB for internal audit and two-party audit. When auditing criteria are selected during auditing, the left screen is displayed when internal auditing is selected, and the right screen is displayed when two-party auditing is selected.

  FIG. 11 shows an example of reference information. For each item associated with each DB described above, reference information can be presented by a link. The manual procedures are prepared in accordance with ISO standards, but the parts that conform to ISO standards are created as a minimum document, and the parts that are not related to ISO standards are separated as reference information. To do. An example of reference information is shown on the left side of FIG. 11. For example, a site operation method, educational information, a reference moving image, and the like can be prepared. For access to the reference information, as shown on the right side of FIG. 11, for example, a moving image of a corresponding operation method may be displayed by clicking the upper bar.

<Function / role dedicated screen, TB combination>
12A and 12B show the site screen of the entire manual. In the top menu of the site shown in FIG. 12, rules are shown on the left and PDCA is shown on the right. Further, as shown on the right side, a site combining the reference information shown in FIG. 11 is arranged. The rule sites are “01-HOME (for the secretariat)”, “02-handbook (for general employees)”, “03-department”, “04-operation rules”, and “05-audit rules”. Within each site, each table filtered from multiple databases is enclosed in iframe program code and combined.

  With the configuration described above, the document system can be minimized and the document display can be maximized. In addition, inter-document search / collation and (item number collation) display can be performed, and the reading speed can be improved. When used as a paper medium, printing can output the entire page at once.

  On the dedicated screen for each person in charge, “plan (including goals), procedures, documented information, trails, reference information”, etc. corresponding to the site page are displayed in a flat, and the inspection and approval of the manager and manager It has functions. PDCA can be deployed after confirming the rules and plans from each dedicated screen. The content is an integrated structure of documents and records, arranged in the order of the questions of the judges, the title or content of each procedure manual, and the module of the table column are combined with ahref, and the screen is dedicated for each department in charge. Made correspondence easier.

  13A and 13B show the site screen of the handbook. FIG. 14A and FIG. 14B show site screens for operation rules. FIG. 15 shows a site screen for audit regulations. FIG. 16 shows a site screen for two-party audit. Regarding the handbook, operation rules, audit rules, and two-party audits, the correspondence is the same as in each diagram of FIG.

  FIG. 17A shows a site screen showing an audit checklist. An audit checklist is displayed above, a correction report is displayed below, and items related to internal audit of the plan DB are displayed on the upper right side, and items related to nonconformity and corrective action of the plan DB are displayed on the lower right side. These are put together on one screen. The audit checklist in the upper left is linked with the information in the correction report in the lower left, is composed of a combination of the plan DB and the plan DB on the right, and is automatically linked to each other. FIG. 17B shows the site screen of the approval document. The approval document management screen and the pages of each site are linked, and the creation, update date and name are linked and displayed on the screen.

  Two-party audits and internal audits are remote audits that share the same screen and allow two-way communication, allowing flexible questions. Answers are registered in the system, and only relevant parties can view them when necessary. It should be designed so that it can be operated even by unilateral registration on the audited side. The internal and two-party audit screens have an integrated structure such as “plan, plan approval, audit standard, procedure, report, audit conclusion”, and audit standards can be easily set by creating a standard database.

  Regarding access rights and settings, access restrictions are set on each screen so that only necessary authorized persons can select operations, registration, browsing, and the like. The approval system enables the approval by AD linkage, access control, and program-controlled log acquisition.

  FIG. 18 shows a schematic diagram of systematization of the ledger. As the ledger, there is an information management ledger, an example of which is shown on the left side of FIG. The upper left is data for storage, and the lower right is data related to risk analysis. Each asset name is defined as a document name, and each item is registered in each asset. When one of these assets is clicked, a registration screen is displayed and items relating to assets for the information management ledger are registered. The risk assessment procedure is shown on the right side of FIG. Information on risk assessment procedures is displayed for reference to user work procedures.

  Normally, various management ledgers are created for each branch or base such as the Tokyo branch, Osaka branch, human resources department, accounting department, and many of the contents are common items. In the case of using a conventional ledger, in particular, when there are a lot of correction points at the time of updating, the common ledger may cause a mismatch of common items due to an administrator's mistake for each jurisdiction. In this system, many overlapping items can be entered by one person in a centralized management, so that concern is eliminated. It is possible to display and input for each department and site in the filtered TB. In other words, since various ledgers can be centrally managed by this system, it is not necessary to create each department.

<Construction and operation flow>
At the time of construction on the user side, the “manual” is composed of SVO or 5WIH as the main database because it is composed at the minimum based on the commercial specifications. Necessary items are registered with reference to “reference information” in FIG. During operation, the procedure and plan are automatically displayed on each screen, and PDCA is expanded accordingly. The trail of activities is completed with a click instead of a document, reducing the operational burden.

  FIG. 19 shows a construction and operation flow. In the present embodiment, the site is constructed in the order of PDCA as shown in FIG. First, the manager determines the authentication range, sets the applicable range, and then proceeds to a series of processes. In the planned PLAN phase, various documents are created first. Specifically, various information registered in the rule DB, the plan DB, and the standard DB is registered here. That is, the secretariat registers manuals and standard documents in the “rule DB” according to the registration procedure, registers various plans in the “plan DB”, and registers standards and standards in the “standard DB”. Furthermore, reference information (including goals) is registered and associated with each.

  These DB documents are registered as documented information, registered by module design, and linked to each other by automatic linkage means. As a result, a rule DB, a plan DB, and a standard DB are constructed. Next, the secretariat creates and registers the information management ledger shown in FIG. Then, additional management measures based on risk assessment are registered.

  Although the description is common to FIG. 3, the documented information includes reference information and various ledger guidelines as the top reference information. The TB of the rule DB includes a manual, audit rules, operation rules, general rules, and change history. The TB of the plan DB includes an annual plan, a monthly plan, an audit plan, an education plan, and an actual result. The standards DB TB includes audit standards, correction reports, and application declarations.

  Then, the execution DO phase is entered. Here, the risk response plan and operation are performed first, and then education and training are performed based on manuals and reference materials on the site. In particular, the management layer performs education by operating a risk response plan according to each plan and rule filtered from the plan DB. The result is appropriately registered in the system.

  Then, the inspection CHECK phase is entered. Here, effectiveness evaluation and internal audit are performed. When the registration reference process is performed in each of the above phases, a linkage process is appropriately performed between the document information, the rule DB, the plan DB, and the standard DB. In particular, the person in charge of management evaluates the effectiveness and registers it in the system. In the case of NG, re-educate. On the other hand, auditors conduct internal audits throughout the company according to the audit plan. Evaluate the results and register with the system. In the case of NG, review management measures.

  Finally, the improved ACT phase is entered. First, management evaluates it in the management review. The future policy is registered in the system as an output. In the case of NG, review the entire system. On top of that, continuous improvement will continue. In other words, we will continue to make improvements by evolving the entire system and effectively representing PDCA.

  As described above, the table of each database is registered in the system, and filtered and displayed on the screen according to various uses such as audit, operation, general use, etc., thereby prompting operation input along the PDCA cycle. In the conventional ISO manual, common data was repeatedly documented for various purposes, so the amount of data was very redundant, but the data was shared and registered, and filtering was applied as necessary. As a result, the amount of data can be significantly reduced.

  On top of that, the usage status of the ISO manual can be managed as appropriate by inputting the PDCA cycle such as the plan DB. It is possible to make it a highly useful manual that is promoted. As a result, it is more convenient for external use such as two-party audit, and an ISO compliant manual with high effect can be provided.

As mentioned above, although this invention was demonstrated using the Example, the technical scope of this invention is not limited to the range as described in the said Example. It will be apparent to those skilled in the art that various modifications and improvements can be made to the above-described embodiments. It is apparent from the description of the scope of claims that embodiments with such changes or improvements can be included in the technical scope of the present invention.

The ISO certification acquisition support apparatus according to the present invention targets a procedure storage unit that identifies and stores a plurality of procedures described in accordance with ISO certification standards, and a plurality of action plans to be executed for each period. A plan data storage unit for identifying and storing a person, selecting a target person, extracting a target person procedure corresponding to the target person from the plurality of procedures, and corresponding to the target person from the plurality of action plans An extraction unit for extracting a target person plan, and a display part for displaying the target person procedure and the target person plan extracted by the extraction part for each of the selected target persons on one screen of separate frames. And an activity record for the target person procedure and the target person plan displayed by the display unit, and a plurality of procedures stored in the procedure storage unit and the plan data storage unit stored therein. Comprising a reflecting unit for reflecting the plurality of Action Plan and the action plan includes information indicating the subject, and information indicating a start time related to the action plan, and information indicating completion timing related to the action plan And information indicating an evaluation result regarding the action plan . The present invention is also an ISO certification acquisition support method performed for the above-described ISO certification acquisition support device, and includes a planning step, an execution step performed after the planning step, and an inspection performed after the execution step. And an improvement step performed after the inspection step, wherein the planning step accepts a plurality of procedures described in accordance with ISO certification standards and a target person, and the received plurality of procedures. A step of storing in the procedure storage unit in association with the received target person, a step of receiving a plurality of action plans to be executed for each period and the target person, and the target received for the received plurality of action plans And associating a person with the person to be stored in the plan data storage unit. And the step of displaying the target person procedure and the target person plan together on one screen of different frames based on the received target person, and the step of receiving the activity result input from the target person And the step of storing the inputted activity result in the procedure storage unit or the plan data storage unit .

Claims (5)

A procedure storage unit that identifies and stores a plurality of procedures written in accordance with ISO certification standards,
A plan data storage unit that identifies and stores a plurality of action plans to be executed for each time period,
An extraction unit that selects a target person, extracts a target person procedure corresponding to the target person from the plurality of procedures, and extracts a target person plan corresponding to the target person from the plurality of action plans;
For the selected target person, the target person procedure extracted by the extraction part and the target person plan, respectively, a display part that collectively displays on one screen of another frame,
For the target person procedure and the target person plan displayed by the display unit, an activity record is input, and a plurality of procedures stored in the procedure storage unit and a plurality of procedures stored in the plan data storage unit are input results. A reflection part to be reflected in the action plan;
ISO certification acquisition support device. A reference information storage unit that stores a plurality of reference information each associated with any one of the plurality of procedures stored in the procedure storage unit;
The display unit displays reference information associated with the extracted target person procedure together with the extracted target person procedure.
The ISO certification acquisition support apparatus according to claim 1. The display unit displays the target person procedure and the target person plan together with a trail display and an audit standard based on a two-party audit standard.
The ISO certification acquisition support apparatus according to claim 1 or 2. 4. The plurality of procedures stored in the procedure storage unit each include at least one of a manual, a handbook, rules for each department, operation rules, audit rules, and a change history. 5. ISO certification acquisition support device. A standard storage unit that stores standard data defining standards related to the plurality of procedures;
The display unit displays standard data about the subject in a different frame on the same screen as the subject procedure and the subject plan,
The ISO certification acquisition support apparatus according to any one of claims 1 to 4.