Maintainability and evolvability of control software in machine and plant manufacturing — An industrial survey

Vogel‐Heuser, Birgit; Ocker, Felix

doi:10.1016/j.conengprac.2018.08.007

Cited by 31 publications

(35 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Whenever possible, quantitative and, if not possible, selected qualitative results (Q3) are delivered concerning five essential RQs introduced above based on 61 German MM and PM companies in Q4. Qualitative results are gained from Q3 especially regarding the engineering workflow for example the usage of universal modules (in electrics/ electronics (EE) with 30%, in Human Machine Interfaces (HMI) with 26% and in SW with 18%) or automatic generation from documents to engineering artefacts with high-est values for EE followed by mechanics (M) and SW. QoaPS SWE exceeds previous surveys [7], [8], [9] in providing significant results regarding, e.g., SW maturity (M MOD+ ), complexity, and Model-Based Software Engineering (MBSE) more precisely modeling tools used (cp. Table 14).…”

Section: Rq4 What Are the Causes And Consequences Of Control Sw Compmentioning

confidence: 90%

“…In [8], the usage of OO IEC as one potentially promising paradigm to structure SW was analyzed: 42% of the participating companies did not use OO IEC at all, 48% partially, and 10% by default. However, neither dependencies between the used controller brand, the company's industrial sector and the engineering process/programming paradigm nor dependencies between usage of OO IEC and SW maturity could be proven.…”

Section: Rq4 What Are the Causes And Consequences Of Control Sw Compmentioning

confidence: 99%

“…Additionally, prior research results [7], [8] highlight the influence of company-specific constraints on SW development. Further, [23] emphasizes the impact of the development team size on applicable reuse strategies in SW development and their potential benefits.…”

Section: Characteristics Of Aps Suppliersmentioning

confidence: 99%

“…In terms of standardization, library blocks range between vendor-specific (to ease controlling a vendor's hardware) and company-specific, which can be further distinguished into company-wide or machine-type-specific libraries [18]. However, regarding the release processes of library blocks, [8] showed that even though these processes are almost standard in industry, they are not well designed in most cases. If a company develops libraries for company-wide use, designated module developers often program them in separate departments.…”

Section: Reuse Strategies In the Aps Domain: Software Configuration mentioning

confidence: 99%

See 3 more Smart Citations

Success Factors for the Design of Field-level Control Code in Machine and Plant Manufacturing - an Industrial Survey -

Vogel‐Heuser

Fischer

Neumann

et al. 2021

Preprint

Self Cite

View full text Add to dashboard Cite

The amount of software in automated production systems, including its development effort, is continuously increasing to currently up to 35-50% of the development personnel. Consequently, success factors for achieving modularity and complexity management of control software are of high economic interest. Scientific solutions are manifold but often not implemented in industry. This paper introduces the study QoaPS SWE (Quality of automated Production Systems’ Software Engineering) providing insights into 61 machine and plant manufacturing companies to give quantitative and qualitative results to five essential research questions on success factors in the design of field-level control code. Compared to preceding surveys, QoaPS SWE achieves statistically significant results for software maturity (MMOD+), complexity, and model-based software engineering and provides detailed insights into causes and consequences for single criteria, thus clearly identifying obstacles to be addressed in future research and with industrial countermeasures. Especially staff qualification and organizational issues are identified as obstacles to applying the object-oriented programming paradigm for control software in machine and plant manufacturing. Validity is ensured by analyzing the statistical significance of the results in addition to comparisons with earlier surveys and interviews as well as the comparison with already existing and accepted maturity levels. The provided qualitative and quantitative results will allow the benchmarking of companies’ maturity and the derivation of concrete recommendations for companies depending on their MMOD+ value and the evaluated characteristics.

show abstract

Section: Rq4 What Are the Causes And Consequences Of Control Sw Compmentioning

confidence: 90%

Section: Rq4 What Are the Causes And Consequences Of Control Sw Compmentioning

confidence: 99%

Section: Characteristics Of Aps Suppliersmentioning

confidence: 99%

Section: Reuse Strategies In the Aps Domain: Software Configuration mentioning

confidence: 99%

See 2 more Smart Citations

Success Factors for the Design of Field-level Control Code in Machine and Plant Manufacturing - an Industrial Survey -

Vogel‐Heuser

Fischer

Neumann

et al. 2021

Preprint

Self Cite

View full text Add to dashboard Cite

show abstract

“…This occurs as remote service access is a common application in IAS, especially in distributed IAS. Examples of this are the following: remote software updates [55], remote patch management and maintenance [21], remote programming, parametrization, monitoring and diagnosis [20,56], etc.…”

Section: Integration In Industrial Automation Systemsmentioning

confidence: 99%

Towards Industrial Intrusion Prevention Systems: A Concept and Implementation for Reactive Protection

Martinez

Vogel‐Heuser

2018

Applied Sciences

Self Cite

View full text Add to dashboard Cite

Featured Application: The paper presents a concept to actively and automatically respond to security intrusions in Industrial Automation Systems. It is comprised of reactive actions, and security and operational policies that consider both security and architectural trends of this kind of systems. This concept is of significance to system stakeholders that wish to increase the security of their system by implementing automatic and active protection.Abstract: System intrusions violate the security of a system. In order to maintain it, it is necessary to decrease the chances of intrusions occurring or by detecting them as soon as they ensue in order to respond to them in a timely manner. These responses are divided in two types: passive or reactive responses. Passive responses are limited to only notification and alerting; whereas, reactive responses influence the intrusion by undoing or diminishing its consequences. Unfortunately, some reactive responses may influence the underlying system where the intrusion has occurred. This is especially a concern in the field of Industrial Automation Systems, as these systems are critical and have a well-defined set of operational requirements that must be maintained. Hence, automatic reactive responses are often not considered or are limited to human intervention. This paper addresses this issue by introducing a concept for reactive protection that integrates the automatic execution of active responses that do not influence the operation of the underlying Industrial Automation System. This concept takes into consideration architectural and security trends, as well as security and operational policies of Industrial Automation Systems. It also proposes a set of reactive actions that can be taken in the presence of intrusions in order to counteract them or diminish their effects. The feasibility and applicability of the presented concept for Industrial Automation Systems is supported by the implementation and evaluation of a prototypical Reactive Protection System.

show abstract

Multi‐criteria decision‐making approach for modular enterprise resource planning sorting problems

Carpitella

Certa

Izquierdo

et al. 2021

Multi Criteria Decision Anal

View full text Add to dashboard Cite

Implementing Enterprise Resource Planning (ERP) systems is currently recognised as best practice with wide associated possibilities of business improvement for companies. Integrating these kinds of systems with business processes in the most efficient way requires to endeavour as much as possible simplifications for final users, which can be pursued by optimising crucial software characteristics. The present paper proposes a novel multi-criteria decision-making (MCDM) approach to deal with such an issue. Specifically, the ELECTRE (ELimination Et Choix Traduisant la REalité) TRI technique is suggested to assign ERP modules into predefined and ordered categories according to maintainability and usability, which are useful drivers in evaluating which module of an ERP software should be enhanced with priority. The results prove to have whole beneficial impact on system performance with relation to a case study: improvement evaluations will be identified based on the classes the ERP modules are assigned to by the method.

show abstract

Maintainability and evolvability of control software in machine and plant manufacturing — An industrial survey

Cited by 31 publications

References 39 publications

Success Factors for the Design of Field-level Control Code in Machine and Plant Manufacturing - an Industrial Survey -

Success Factors for the Design of Field-level Control Code in Machine and Plant Manufacturing - an Industrial Survey -

Towards Industrial Intrusion Prevention Systems: A Concept and Implementation for Reactive Protection

Multi‐criteria decision‐making approach for modular enterprise resource planning sorting problems

Contact Info

Product

Resources

About