DE102021100433A1 - Process for finding and processing problem areas in complex technical projects - Google Patents

Abstract

Main claim: Computer-implemented method for finding and processing problem areas in complex technical projects with the following steps:
(1) Identification of project participants
(2) Classification of the project participants within the groups
(A) Component Interface Partners
(B) Process Interface Partners
(C) Contract Request Officers
(D) Secondary Request Officers
(3) Definition of project process phases and associated questions
(4) Relating the project participants from steps (1) and (2) and the associated questions from step (3) to a matrix
(5) Use of this matrix in an EDP-based database

Description

The invention relates to a method for finding and processing problem areas in complex technical projects.

Various computer-implemented solutions for sub-areas of project management are known. A holistic solution that can be universally adapted to specific scenarios is desirable in order to identify and process problem areas in complex technical projects.

The object of the invention is therefore to provide a computer-implementable method for finding and processing problem areas in complex technical projects that can be easily adapted to the respective project.

The object is achieved according to the invention by a method having the features of claim 1.

• (1) Ermitteln aller relevanten Projektbeteiligten z.B. aus den Engineering- und Projektorganigrammen.
• (2) Klassifizierung der Projektbeteiligten:
  1. (A) Komponenten-Schnittstellenpartner A1, A2, A3, ... (alle mechanischen und elektrischen Komponenten, Stromlaufplan, Software, etc.)
  2. (B) Prozess-Schnittstellenpartner B1, B2, B3, ... (z.B. Einkauf, Fertigung, Projektleitung, Kunde, Lieferant, etc.)
  3. (C) Verantwortliche C1, C2, C3, ... für die primären Anforderungen aus Kundenvertrag, bzw. Lasten- und Pflichtenheft (z.B. technische Anforderungen, Anforderungen zu Kosten, Anforderungen zu Terminen, etc.)
  4. (D) Verantwortliche D1, D2, D3, ... für sekundäre Anforderungen, also Anforderungen die sich aus den primären Anforderungen plus dem eigenen Know-How, Berechnungen, Auslegung von Normen und Gesetzen, etc. ergeben (z.B. Gewichtsmanagement, Brandschutz, Akustik, statische und dynamische Berechnungen, etc.)
• (3) Festlegung von Projektablaufphasen, wie z.B. Konzeptphase, Designphase, Phase bis Design-Freeze, etc. und einer dazugehörigen Fragestellung was zum Ende dieser Phase erreicht sein soll. Diese Fragestellung kann sowohl für einzelne oder mehrere Projektbeteiligte (z.B. nur für A1), als auch für die gesamte Gruppe gültig sein (z.B. A1 bis A3).
• (4) In Beziehung setzen der Projektbeteiligten aus den Schritten (1) und (2) und der dazugehörigen Fragestellungen aus Schritt (3) zu einer Matrix.

The procedure includes the following steps:

• (1) Determination of all relevant project participants, eg from the engineering and project organization charts.
• (2) Classification of project participants:
  1. (A) Component interface partners A1, A2, A3, ... (all mechanical and electrical components, circuit diagram, software, etc.)
  2. (B) Process interface partner B1, B2, B3, ... (e.g. purchasing, production, project management, customer, supplier, etc.)
  3. (C) Responsible persons C1, C2, C3, ... for the primary requirements from the customer contract, or requirements and functional specifications (e.g. technical requirements, cost requirements, deadline requirements, etc.)
  4. (D) Responsible D1, D2, D3, ... for secondary requirements, i.e. requirements that result from the primary requirements plus their own know-how, calculations, interpretation of standards and laws, etc. (e.g. weight management, fire protection, acoustics , static and dynamic calculations, etc.)
• (3) Definition of project process phases, such as concept phase, design phase, phase up to design freeze, etc. and an associated question of what should be achieved at the end of this phase. This question can be valid for one or more project participants (e.g. only for A1), as well as for the entire group (e.g. A1 to A3).
• (4) Relating the project participants from steps (1) and (2) and the associated questions from step (3) to a matrix.

• (5) Nutzung dieser Matrix in einer EDV-basierten Datenbank:
  • Hierzu gibt es verschiedene optionale und verschiedenartig miteinander kombinierbare Möglichkeiten, etwa:
    • - optische Kenntlichmachung der Kreuzungspunkte zur Identifikation von Problemstellen, z.B. rot für dringende Probleme, gelb für weniger dringliche Probleme, grün für problemfreie Kreuzungspunkte, schwarz für keine Anforderung / Schnittstelle
    • - Belegung der Kreuzungspunkte mit Textinformation über die einzelnen Probleme und deren Status
    • - Belegung der Kreuzungspunkte in einer EDV-basierten Datenbank mit der Beschreibung der ToDos (Beschreibung der Lösung, wer ist für die Lösung verantwortlich, bis wann ist die Lösung zu erarbeiten), die für die Lösung dieser Probleme notwendig sind.
    • - Ausstattung dieser Datenbank mit teil- oder vollautomatisierten Prozessen zur Abarbeitung und Überwachung dieser ToDos z.B. mittels zeitabhängig versendeter Emails an die, für die Lösung verantwortlichen Mitarbeiter mit Aufforderung zum finalisieren der Problemlösung bzw. der Möglichkeit der Rückmeldung in die Datenbank über den Stand und etwaige Änderungen oder Verschiebungen.
    • - Ausstattung dieser Datenbank mit teil- oder vollautomatisierten Prozessen zur Auswertung der Daten z.B. für ToDo-Listen, Aufgaben für die nächste Arbeitswoche, Risikolisten, Auswertungen für die Projekt- oder Firmenleitung.
    • - Ausstattung dieser Datenbank mit teil- oder vollautomatisierten Prozessen zum Austausch mit anderen Systemen, wie Qualitätsmanagement, Terminplanung, Risikolisten, Key Performance Indicator - Systemen, etc.
    • - Belegung der Felder für Projektbeteiligte (A1, A2, ... bis D1, D2, ...) mit den Kontaktdaten zum jeweiligen Verantwortlichen, links zu relevanten Dokumenten, Datum der geplanten Finalisierung, etc.

The columns of the matrix are preferably specified by elements or members A1, A2, A3, ... of group (A) and the rows of the matrix are preferably specified by elements or members A1, A2, A3, ..., B1, B2 , B3, ..., C1, C2, C3, ..., D1, D2, D3, ... of the groups (A) to (D) are specified, with the lines preferably being grouped according to questions from step (3). .

• (5) Use of this matrix in an EDP-based database:
  • There are various optional options that can be combined with one another in various ways, such as:
    • - Visual identification of the crossing points to identify problem areas, eg red for urgent problems, yellow for less urgent problems, green for problem-free crossing points, black for no requirement/interface
    • - Assignment of the crossing points with text information about the individual problems and their status
    • - Assignment of the crossing points in an EDP-based database with the description of the to-dos (description of the solution, who is responsible for the solution, by when the solution is to be worked out), which are necessary for solving these problems.
    • - Equipping this database with partially or fully automated processes for processing and monitoring these to-dos, e.g. by means of time-dependent emails sent to the employees responsible for the solution with a request to finalize the problem solution or the possibility of reporting back to the database about the status and any changes or shifts.
    • - Equipping this database with partially or fully automated processes for evaluating the data, eg for to-do lists, tasks for the next working week, risk lists, evaluations for the project or company management.
    • - Equipping this database with partially or fully automated processes for exchange with other systems, such as quality management, scheduling, risk lists, key performance indicator systems, etc.
    • - Assignment of the fields for project participants (A1, A2, ... to D1, D2, ...) with the contact details of the respective person responsible, links to relevant ones documents, date of planned finalization, etc.

A schematic example of such a matrix is shown in the attached figure using exemplary project phase-dependent questions.

Claims (5)

Computer-implemented method for finding and processing problem areas in complex technical projects with the following steps: (1) Identification of project stakeholders (2) Classification of project stakeholders within multiple groups, including: (A) Component Interface Partners (B) Process Interface Partners (C) Contract Request Officers (D) Secondary Request Officers (3) Definition of project process phases and associated questions (4) Relating the project participants from steps (1) and (2) and the associated questions from step (3) to a matrix (5) Use of this matrix in an EDP-based database procedure after claim 1 , wherein the columns of the matrix are specified by elements of group (A), and wherein the rows of the matrix are specified by elements of groups (A) to (D) and are preferably grouped according to questions from step (3). procedure after claim 1 or 2 , whereby crossing points of the matrix are marked optically to identify problem areas. Device with means for carrying out the method according to one of the preceding claims. Computer program product with means for carrying out the method according to one of Claims 1 to 4 on a computer system.

Images