Feasibility Study ofThickness Measurement System

Thickness Measurement System is a method for using risk as a basis for prioritizing and managing the efforts of an inspection program. In an operating plant, a relatively large percentage of the risk is associated with a small percentage of the equipment items. Thickness Measurement System permits the shift of inspection and maintenance resources to provide a higher level of coverage on the high-risk items and an appropriate effort on lower risk equipment. This system provides companies the opportunity to prioritize their equipment for inspection; optimize inspection methods, frequencies and resources; develop specific equipmentinspectionplans, and enable the implementation of equipmentmaintenance. This results in improvedsafety, lower failure risks, fewer forced shutdowns, and reduced operational costs This project work around on how to develop the software so that it can be easily use. This project use Visual Basic.Net for the interface and software implementation and SQL server as database. API RP 580 Risk Base Inspection and API RP 581 RBI Base Resource Document are the reference documents

Addressing Software-Based, Platform Interoperability Risks in Defense Systems by Using Distressed Debt Financial Strategies: A Technical Debt Mitigation Concept

This concept paper explores an innovative approach to detecting and managing software vulnerabilities in cyber-physical defense systems. Software-based vulnerabilities that hinder or preclude the maintainability and evolvability of combat systems are a pernicious form of technical debt that threaten all cyber-physical systems. The risks associated with technical debt across increasingly interdependent DoD cyber-physical systems will accelerate if left unchecked. Without changes in acquisition and maintenance practices, we can foresee cascading, potentially catastrophic cross-system failures. To illustrate the risk and possible solutions, we focus on the software embedded in combat systems that are subject to ongoing modernization efforts that extend their applicability to evolving operations. Our research revealed that software vulnerabilities in critical combat systems can threaten the reliability and readiness of those systems. These vulnerabilities provide an opportunity for the defense acquisition communities to create a new capability within their organizations, an Acquisition Technical Debt Team (ATDT) to help detect, manage, and mitigate technical debt. We explore risk classification by including interoperability into risk evaluation schemas. We then apply common distressed debt management models to suggest when and how the ATDT might help manage and mitigate technical debt to help rehabilitate an ailing system.Prepared for the Naval Postgraduate School, Monterey, CA 93943.Naval Postgraduate SchoolApproved for public release; distribution is unlimited.Approved for public release; distribution is unlimited

Technical Debt Prioritization: State of the Art. A Systematic Literature Review

Background. Software companies need to manage and refactor Technical Debt issues. Therefore, it is necessary to understand if and when refactoring Technical Debt should be prioritized with respect to developing features or fixing bugs. Objective. The goal of this study is to investigate the existing body of knowledge in software engineering to understand what Technical Debt prioritization approaches have been proposed in research and industry. Method. We conducted a Systematic Literature Review among 384 unique papers published until 2018, following a consolidated methodology applied in Software Engineering. We included 38 primary studies. Results. Different approaches have been proposed for Technical Debt prioritization, all having different goals and optimizing on different criteria. The proposed measures capture only a small part of the plethora of factors used to prioritize Technical Debt qualitatively in practice. We report an impact map of such factors. However, there is a lack of empirical and validated set of tools. Conclusion. We observed that technical Debt prioritization research is preliminary and there is no consensus on what are the important factors and how to measure them. Consequently, we cannot consider current research conclusive and in this paper, we outline different directions for necessary future investigations

Benchmarking of project planning and success in selected industries

Purpose - To identify the industry in which projects are best planned and executed and use it as a benchmark for improving project planning in other industries. Design/methodology/approach - Based on data collected from 280 project managers, project success and quality of project planning were evaluated and analyzed for four industries - construction and engineering, software and communications, services, and production and maintenance. Findings - Quality of project planning was found to be the highest in construction and engineering organizations and the lowest in manufacturing organizations. This is a result of a few factors, among them the intensive organizational support which is offered to project managers working in construction and engineering organizations. The other three industries limit their support mostly to tactical aspects, such as the purchasing of project management software. The high quality of project planning in the construction and engineering organizations resulted in their ability to complete projects by almost half the cost and schedule overruns, as compared to organizations belonging to the other industries. Finally, results of the industries in Israel and Japan are compared and analyzed. Research limitations/implications - Findings are limited to the four industries included in the study. Practical implications - If organizations, not belonging to the construction industry, wish to improve the probability of success in project planning and execution, they should follow methodologies commonly used in the construction industry. Originality/value - This paper introduces a valid field study, exploring project management practices in four industries and identifies the one which may be used as a benchmark for the others. It also identifies specific strengths and weaknesses in project management within the explored industries

Operational software maturity: An aerospace industry analysis

Software applications have become crucial to the aerospace industry, providing a wide range of functionalities and capabilities used during the design, manufacturing and support of aircraft. However, as this criticality increases, so too does the risk for business operations when facing a software failure. Hence, there is a need for new methodologies to be developed to support aerospace companies in effectively managing their software portfolios, avoiding the hazards of business disruption and additional costs. This paper aims to provide a definition of operational software maturity, and how this can be used to assess software operational behaviour, as well as a view on the different aspects that drive software maturity within the aerospace industry. The key research question addressed is, how can operational software maturity monitoring assist the aerospace industry in effectively managing large software portfolios? This question has been addressed by conducting an in depth review of current literature, by working closely with aerospace professionals and by running an industry case study within a major aircraft manufacturer. The results are a software maturity model composed of a set of drivers and a prototype tool used for the testing and validation of the research findings. By utilising these methodologies to assess the operational maturity of software applications in aerospace, benefits in maintenance activities and operations disruption avoidance have been observed, supporting business cases for system improvement. Paper originally presented at ICSM 2017 : 19th International Conference on Software Maintenance, 18-19 September 2017, Rome, Italy

Evaluating cost taxonomies for information systems management

The consideration of costs, benefits and risks underpin many Information System (IS) evaluation decisions. Yet, vendors and project-champions alike tend to identify and focus much of their effort on the benefits achievable from the adoption of new technology, as it is often not in the interest of key stakeholders to spend too much time considering the wider cost and risk implications of enterprise-wide technology adoptions. In identifying a void in the literature, the authors of the paper present a critical analysis of IS-cost taxonomies. In doing so, the authors establish that such cost taxonomies tend to be esoteric and difficult to operationalize, as they lack specifics in detail. Therefore, in developing a deeper understanding of IS-related costs, the authors position the need to identify, control and reduce IS-related costs within the information systems evaluation domain, through culminating and then synthesizing the literature into a frame of reference that supports the evaluation of information systems through a deeper understanding of IS-cost taxonomies. The paper then concludes by emphasizing that the total costs associated with IS-adoption can only be determined after having considered the multi-faceted dimensions of information system investments

Adaptive development and maintenance of user-centric software systems

A software system cannot be developed without considering the various facets of its environment. Stakeholders – including the users that play a central role – have their needs, expectations, and perceptions of a system. Organisational and technical aspects of the environment are constantly changing. The ability to adapt a software system and its requirements to its environment throughout its full lifecycle is of paramount importance in a constantly changing environment. The continuous involvement of users is as important as the constant evaluation of the system and the observation of evolving environments. We present a methodology for adaptive software systems development and maintenance. We draw upon a diverse range of accepted methods including participatory design, software architecture, and evolutionary design. Our focus is on user-centred software systems

Surfacing ERP exploitation risks through a risk ontology

Purpose – The purpose of this paper is to develop a risk identification checklist for facilitating user companies to surface, organise and manage potential risks associated with the post-adoption of Enterprise Resource Planning (ERP) systems. Design/methodology/approach – A desktop study, based on the process of a critical literature review, was conducted by the researchers. The critical review focused on IS and business research papers, books, case studies and theoretical articles, etc. Findings – By systematically and critically analysing and synthesising the literature reviewed, the researchers identified and proposed a total of 40 ERP post-implementation risks related to diverse operational, analytical, organisation-wide and technical aspects. A risk ontology was subsequently established to highlight these ERP risks, as well as to present their potential causal relationships. Research limitations/implications – For researchers, the established ERP risk ontology represents a starting point for further research, and provides early insights into a research field that will become increasingly important as more and more companies progress from implementation to exploitation of ERPs. Practical implications – For practitioners, the risk ontology is an important tool and checklist to support risk identification, prevention, management and control, as well as to facilitate strategic planning and decision making. Originality/value – There is a scarcity of studies focusing on ERP post-implementation in contrast with an over abundance of studies focusing on system implementation and project management aspects. This paper aims to fill this significant research gap by presenting a risk ontology of ERP post-adoption. It represents a first attempt in producing a comprehensive model in its area. No other such models could be found from the literature reviewed

Identification of Risks in the Course of Managing the Deep Sea Archeological Projects Using Marine Robotics

An analysis is conducted of the basic risks that occur when managing the projects of deep-sea archeological research. It is proposed to consider possible risks of such projects in the form of a general set of risks that contains subsets of the identified and unidentified risks. Based on the generalization of existing experience of conducting underwater archaeological research and with regard to the peculiarities of their execution by using TV-controlled unmanned underwater vehicles, the main risks of such operations are identified. A classification of risk factors is proposed, which takes into account weather and hydrological conditions in the area of operations, peculiarities of the underwater situation, technological and technical provision of underwater archaeological research, possible obstacles from the navigation in the explored area and errors in geographical coordinates of fulfilled work, as well as the human factor. Additionally, environmental, organizational and financial risks, which the project team is aware of, are defined as directly related to planning the projects of deep-sea archeological research. A generalized risk register is developed of the projects\u27 deep-sea archaeological studies as theoretical foundation for designing the models of risk management and their quantitative evaluation when planning financial and temporal resources for such projects