KR20130112354A - Apparatus for interfacing project management tool and systems engineering tool - Google Patents

Abstract

PURPOSE: An interface device between a project management tool and a system engineering tool is provided to enable mutual examination between the project management tool and the system engineering tool about PM items. CONSTITUTION: When the inquiry on PM items transmitted from a project management tool is completed, SE data transfer is selected (S10). When the SE data transfer is selected, the issue information is stored in an interface data storage unit (S20). According to the batch schedule, a PM conversion unit generates a PM meta file and a PM share file about the issue information and stores the files into a share storage unit (S30, S40). According to the batch schedule in a system engineering tool, an SE conversion unit is automatically run every fifteen minutes. The SE conversion unit accesses a PM interface file, converts the file, and provides the converted file to the system engineering tool (S50). The issue information of the project management tool is stored and registered into an SE database by the system engineering tool so that the issue information managed in the project management tool can be inquired from the system engineering tool (S60). [Reference numerals] (AA) Start; (BB) End; (S10) Select the transmission of SE data; (S20) Store interface information; (S30) Execute a PM conversion unit; (S40) Generate a PM interface file; (S50) Execute an SE conversion unit; (S60) Register SE

Description

Interface device between project management tool and system engineering tool {APPARATUS FOR INTERFACING PROJECT MANAGEMENT TOOL AND SYSTEMS ENGINEERING TOOL}

The present invention relates to an interface device between a project management tool and a system engineering tool, and more particularly, a project management to convert, transmit, and register output information generated by the project management tool and the system engineering tool to be shared. The interface device between the tool and the system engineering tool.

In general, Systems Engineering (SE) seeks to scientifically explain and effectively construct and manipulate a moving system in which various elements such as humans, objects, information, technology, and time are complex, such as phenomena in an organization or society. Developed.

This system engineering has four common requirements.

The first is a holistic approach to system top-down analysis and bottom-up integration.

The second is addressed from the life-cycle perspective of deriving, acquiring and operating requirements at all stages of system design, development, production or construction, distribution, operation, maintenance and support, disposal and disposal. .

Third, it must be identified in advance so that specific design goals and appropriate design criteria can be presented and decisions can be analyzed and analyzed in a faster and more effective way in the design process.

Fourth, the system design and development process can achieve the desired design goals through interdesciplinary collaboration.

This system engineering has recently evolved into Model Based Systems Engineering (MBSE), which is model-based and utilizes many system engineering computer tools, and has developed model-based acquisition, modeling and simulation, and concurrent engineering and integrated product needle processes. Techniques have shortened product development time, reduced costs, and reduced design changes and product defects.

On the other hand, a project means that several people work for a certain period of time to achieve a certain result. Therefore, the detailed requirements of such a project are determined first, in what time frame, how much budget should be completed, who should be in charge of the details, and who will be in charge? Therefore, the participant is determined, the detailed work is divided among the participant, and how well the participant is performing the detailed work within the period is managed through weekly or monthly work reports.

However, when there are a large number of participants in the project or the output of the participants is not only a loophole in management, but also it is not clear how objectively the project is going. If no one is able to perform the task assigned to him or her, the task and participant have been assigned to complete the project. When a new task is added or when a change of participant is required or a new participant is required, such a change, modification, etc. are not smoothly performed and there is a problem in that time and space are wasted.

Therefore, in order to solve these problems, a project management tool that integrates the management of the entire project is established to manage the report materials and various outputs so that the project can be executed smoothly, thereby increasing the overall reliability of the project.

Related prior art is Korean Patent Publication No. 10-2011-0003126 (2011.01.11.) "Project management method using the activity project management system".

Although system engineering and project management techniques are used as the scientific management methods for efficiently carrying out large-scale projects, the current business environment is becoming more complex and sophisticated, so it is possible to efficiently share and manage the vast amount of data generated by the scientific management techniques used. Sudan suffers a lot in reality.

Particularly, in the light rail project site, information generated from project management and system engineering are managed separately or stored in one data storage system by manual method, making it very difficult to use traceability or linkage between data. Increasingly, there is an increasing need for integrated integration.

The present invention was created in accordance with the necessity as described above, and can be transmitted to the Systems Engineering (SE) tool for the PM (Project Management) item managed by the Project Management (PM) tool. It aims to provide an interface device between the project management tool and the system engineering tool that can convert and transfer the SE (Systems Engineering) items managed by the system engineering tool so that the project management tool can be converted and registered.

The interface device between the project management tool and the system engineering tool according to an aspect of the present invention is a PM (Project Management) interface file and a SE (Systems Engineering) interface that can be mutually shared about the outputs shared between the project management tool and the system engineering tool. Shared storage unit for storing as a file; PM conversion managed by the project management tool to convert the PM interface file into the shared storage so that it can be viewed by the system engineering tool. part; SE, which is managed by the system engineering tool, is converted into SE interface file and stored in the shared storage so that the project management tool can be searched, and the PM interface file stored in the shared storage is converted and provided as the system engineering tool. It characterized in that it comprises a conversion unit.

In the present invention, the PM interface file is a PM metafile and a PM shared file, which are allocated to PM items for interfacing from the project management tool to the system engineering tool.

In the present invention, the SE interface file is an SE metafile and an SE shared file, which are allocated to SE items for interfacing from the system engineering tool to the project management tool.

In the present invention, the PM item is characterized in that it includes any one or more of SEMS (Systems Engineering Master Schedule) information, SEDS (Systems Engineering Detailed Schedule) information, issue information, meeting minutes information and document information.

In the present invention, the SE item is characterized in that it includes any one or more of the data reporting information, requirements information, issue information, risk information, terminology information.

In the present invention, the PM conversion unit is characterized in that the transmission from the project management tool to the system engineering tool is executed in the unit of the set period for the selected PM item is converted and transmitted and records the transmission result.

In the present invention, characterized in that it further comprises an interface information storage unit for storing the PM item selected for transmission from the project management tool to the system engineering tool.

In the present invention, the SE conversion unit is executed in a set cycle unit when the transmission target to be transmitted from the system engineering tool to the project management tool is characterized in that the conversion and transmission and recording the transmission result.

The present invention not only can transmit and check PM items managed by the project management tool to the system engineering tool, but also converts and transmits and registers each other so that the project management tool can check the SE items managed by the system engineering tool. By effectively sharing outputs and exchanging information from different systems for scientific management, it is possible to efficiently manage large projects.

1 is a block diagram illustrating an interface device between a project management tool and a system engineering tool according to an exemplary embodiment of the present invention.
2 is a flowchart illustrating an operation of an interface device between a project management tool and a system engineering tool according to an embodiment of the present invention.
3 is an issue information screen of the project management tool of the interface device between the project management tool and the system engineering tool according to an embodiment of the present invention.
4 is a screen illustrating a storage state of an interface information storage unit of an interface device between a project management tool and a system engineering tool according to an exemplary embodiment of the present invention.
5 is a batch schedule management screen provided in a project management tool of an interface device between a project management tool and a system engineering tool according to an embodiment of the present invention.
6 is a screen illustrating a generation state of a PM interface file of an interface device between a project management tool and a system engineering tool according to an exemplary embodiment of the present invention.
7 is a screen illustrating issue information registered in a system engineering tool of an interface device between a project management tool and a system engineering tool according to an embodiment of the present invention.

Hereinafter, an embodiment of an interface device between a project management tool and a system engineering tool according to the present invention will be described with reference to the accompanying drawings. In this process, the thicknesses of the lines and the sizes of the components shown in the drawings may be exaggerated for clarity and convenience of explanation. In addition, the terms described below are defined in consideration of the functions of the present invention, which may vary depending on the intention or custom of the user, the operator. Therefore, definitions of these terms should be made based on the contents throughout this specification.

1 is a block diagram illustrating an interface device between a project management tool and a system engineering tool according to an exemplary embodiment of the present invention.

As shown in FIG. 1, an interface device between a Project Management (PM) tool and a Systems Engineering (SE) tool according to an embodiment of the present invention includes a shared storage unit 40 and a PM conversion unit 20. ) And the SE conversion unit 50.

The shared storage unit 40 stores the shared output between the project management tool 10 and the system engineering tool 60 as a PM (Project Management) interface file and a SE (Systems Engineering) interface file.

The PM (Project Management) interface file is a PM metafile and a PM shared file which are allocated to PM items managed by the project management tool 10 for interfacing from the project management tool 10 to the system engineering tool 60.

The PM items are SEMS (Systems Engineering Master Schedule) information, SEDS (Systems Engineering Detailed Schedule) information, issue information (Issure), meeting minutes information (Meeting) and document information (Document). It is defined as shown.

As shown in Table 1, the PM metafile is defined as a csv (Comma separated values) file having the name of the association object, and the PM shared file is stored in the PM shared folder.

object send
unit PM metafile PM
Shared file PM shared file
Folder name SE
Linked Information SEMS project EP_SEMS.csv × SEMS SEDS project EP_SEDS.csv ○ EXF_SEDS SEDS document Case by case EP_Document.csv ○ EXF_Document Document issue Case by case EP_Issue.csv ○ EXF_Issue Issue meeting log Case by case EP_Meeting.csv ○ EXF_Meeting proceeding

At this time, SEMS information and SEDS information define the detailed schedule in the System Engineering Management Plan (SEMP) for the system engineering activities of the light railroad project and manage the system engineering activities according to the defined detailed schedule. The document information, the issue information, and the minutes information are transmitted on a case-by-case basis.

Minutes information is sent to the meeting minutes distributed in the project management tool 10, the issue information is sent to the subjects processed in the project management tool (10).

The SE (Systems Engineering) interface file is an SE metafile and an SE shared file which are allocated to SE items managed by the system engineering tool 60 for interfacing from the system engineering tool 60 to the project management tool 10.

SE items are documented report information, requirements information, issues information, risk information, risk information, and term information defined terms. The SE metafile and SE shared file are defined as shown in Table 2. do.

As shown in Table 2, the SE metafile is defined as a csv (Comma separated values) file with the name of the association object, and the SE shared file is stored in the SE shared folder.

object send
unit SE metafile SE
Shared file SE shared file
Folder name PM
Linked Information Document Case by case SE_Document.csv ○ EXF_Document Report Requirement Case by case SE_Requirement.csv ○ EXF_Requirement Requirements Issue Case by case SE_Issue.csv ○ EXF_Issue Issue Management Risk Case by case SE_Risk.csv ○ EXF_Risk Issue Management DefinedTerm Case by case SE_DefinedTerm.csv ○ EXF_DefinedTerm Glossary

The data report information is transmitted to the system engineering tool 60 for payment of document information, and in the case of documents approved by the payment function in the project management tool 10, the approval result is transmitted to the system engineering tool 60 again. It is sent on a case-by-case basis.

The PM conversion unit 20 converts the PM interface file so that the system engineering tool 60 can be inquired about the PM items managed by the project management tool 10, and stores them in the shared storage unit 40 and stores the shared storage unit 40. By converting the SE interface file stored in the (40) and provided to the project management tool 10, the project management tool 10 to store the SE item in the PM database (15).

The interface information storage unit 30 stores the PM item selected for transmission from the project management tool 10 to the system engineering tool 60.

The PM converting unit 20 executes an automatic batch schedule at a set cycle to convert PM items stored in the interface information storage unit 30 to generate PM metafiles and PM shared files, and store them in the shared storage unit 40. Record it.

The SE conversion unit 50 converts the SE interface file so that the project management tool 10 can be inquired about the SE items managed by the system engineering tool 60, and stores them in the shared storage unit 40, and stores the shared storage unit. By converting the PM interface file stored in (40) and providing it to the system engineering tool (60), the system engineering tool (60) stores PM items in the SE database (65).

The SE conversion unit 50 executes an automatic batch script at a set cycle, and converts the SE items to be transmitted from the system engineering tool 60 to the project management tool 10 when the transmission target is not transferred to convert the SE metafile and the SE shared file. After generating and storing in the shared storage unit 40 records the transmission result.

2 is a flowchart illustrating an operation of an interface device between a project management tool and a system engineering tool according to an embodiment of the present invention, FIG. 3 is an issue information screen of the project management tool, and FIG. 4 is an interface information storage unit. 5 is a screen showing a storage state, FIG. 5 is a batch schedule management screen provided by a project management tool, FIG. 6 is a screen showing a state of generating a PM interface file, and FIG. 7 is a screen showing issue information registered by a system engineering tool. to be.

2 to 7 illustrate the transmission from the project management tool to the system engineering tool by way of example.

First, when the PM items transmitted from the project management tool 10 are inquired, the transmission to the system engineering tool 60, that is, SE data transmission is selected (S10).

3 is an issue information inquiry screen in the project management tool 10, when the issue processing is completed can select the SE data transmission or query the transmitted history.

When the SE data transmission is selected in this way, the issue information is stored in the interface information storage unit 30 (S20).

As shown in FIG. 4, as the data transmission is selected, the corresponding information may be checked in the interface information storage unit 30.

Afterwards, according to the batch schedule, the PM converter 20 generates the PM metafile and the PM shared file with respect to the issue information and stores it in the shared storage 40 (S30) (S40).

5 is a batch schedule management screen provided by the project management tool 10, it can be seen that the schedule management so that the transmission from the project management tool 10 to the system engineering tool 60 is automatically executed every 15 minutes.

As described above, the PM metafile and the PM shared file generated by the PM converter 20 may be checked according to the batch schedule.

For example, in case of the issue information, it can be confirmed that the PM metafile of EP_Issue.csv and the PM shared file of EXF_Issue are generated.

Thereafter, the SE conversion unit 50 is automatically executed at intervals of 15 minutes according to the arrangement schedule of the system engineering tool 60 to access and convert the PM interface file stored in the shared storage unit 40, and to convert the system engineering tool 60. Provided by (S50).

The issue information of the project management tool 10 provided as described above is stored and registered in the SE database 65 in the system engineering tool 60 and managed in the project management tool 10 in the system engineering tool 60 as shown in FIG. 7. The issue information can be confirmed (S60).

As described above, according to the interface device between the project management tool and the system engineering tool according to the present invention, the PM items managed by the project management tool 10 and the SE items managed by the system engineering tool 60 are mutually converted and transmitted and registered. It enables the effective management of large projects by effectively sharing and exchanging information of outputs from different systems for scientific management.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. I will understand. Accordingly, the technical scope of the present invention should be defined by the following claims.

10: project management tool 15: PM database
20: PM conversion unit 30: interface information storage unit
40: shared storage unit 50: SE conversion unit
60: System Engineering Tools 65: SE Database

Claims (8)

A shared storage unit for storing the outputs shared between the project management tool and the system engineering tool as a PM (Project Management) interface file and a Systems Engineering (SE) interface file that can be shared with each other;
The PM item managed by the project management tool is converted into the PM interface file to be viewed by the system engineering tool and stored in the shared storage, and the SE interface file stored in the shared storage is converted into the project. PM conversion unit provided by the management tool; And
The SE item managed by the system engineering tool is converted into the SE interface file to be viewed by the project management tool and stored in the shared storage, and the PM interface file stored in the shared storage is converted into the system. An interface device between a project management tool and a system engineering tool, comprising an SE conversion unit provided as an engineering tool.
The project management tool and system engineering of claim 1, wherein the PM interface file is a PM metafile and a PM shared file which are allocated to the PM items for interfacing from the project management tool to the system engineering tool. Tool-to-tool interface device.
The project management tool and system engineering of claim 1, wherein the SE interface file is an SE metafile and an SE shared file which are allocated to the SE items for interfacing from the system engineering tool to the project management tool. Tool-to-tool interface device.
The project management tool according to claim 1, wherein the PM item includes at least one of Systems Engineering Master Schedule (SEM) information, Systems Engineering Detailed Schedule (SEDS) information, issue information, meeting minutes information, and document information. Interface device between system engineering tools.
The apparatus of claim 1, wherein the SE item comprises at least one of data report information, requirement information, issue information, risk information, and terminology information.
The project management according to claim 1, wherein the PM converting unit executes the transmission from the project management tool to the system engineering tool in a set cycle unit for the selected PM item to convert, transmit, and record a transmission result. Interface device between tool and system engineering tool.
The interface device according to claim 1, further comprising an interface information storage unit for storing the PM item selected from the project management tool to the system engineering tool.
The project management tool according to claim 1, wherein the SE conversion unit is executed in a set cycle unit when the transmission target to be transmitted from the system engineering tool to the project management tool is not transmitted. Interface device between system engineering tools.

Images