Prognostics health management: perspectives in engineering systems reliability prognostics

The Prognostic Health Management (PHM) has been asserting itself as the most promising methodology to enhance the effective reliability and availability of a product or system during its life-cycle conditions by detecting current and approaching failures, thus, providing mitigation of the system risks with reduced logistics and support costs. However, PHM is at an early stage of development, it also expresses some concerns about possible shortcomings of its methods, tools, metrics and standardization. These factors have been severely restricting the applicability of PHM and its adoption by the industry. This paper presents a comprehensive literature review about the PHM main general weaknesses. Exploring the research opportunities present in some recent publications, are discussed and outlined the general guide-lines for finding the answer to these issues.

2013 Iowa DOT Engineering Intern Development and Management Program, 13-464, 2013

The Institute for Transportation (InTrans) at Iowa State University (ISU) developed an internship mentoring program in collaboration with the Iowa Department of Transportation (DOT) to provide additional mentorship to both student interns and Iowa DOT intern managers. For the summer 2013 Iowa DOT Engineering Intern Development and Management Program, this report summarizes the following: * Mentoring activities conducted by ISU; * Results of the different intern program success assessments that were conducted; * Experiences, lessons learned, and recommendations; * Program benefits that were realized.

Development of Concepts for Pavement Management, MLR-79-04, 1979

Sufficient evidence was not discovered in this brief search to alter the general opinion that the Serviceability (Present Serviceability Index-PSI) - Performance Concepts developed by the AASHO Road Test provides the optimum engineering basis for pavement management. Use of these concepts in Iowa has the additional advantage in that we have a reasonable quantity of historical data over a period of time on the change in pavement condition as measured by PSI's. Some additional benefits would be the ability to better assess our needs with respect to those being recommended to Congress by AASHTO Committees. These concepts have been the basis used for developing policies on dimensions and weight of vehicles and highway needs which the AASHTO Transport Committees have recommended to the United States House Committee on Ways and Means. The first recommendation based on these concepts was made in the mid 1960's. Iowa's participation in the evaluation for this recommendation was under the direction of our present Director of Transportation, Mr. Raymond Kassel. PSI Indexes had to be derived from subjective surface ratings at that time. The most recent recommendation to Congress was made in November of 1977. Based on the rationale expressed above, a pilot study of the major part of the rural interstate system was conducted. The Objective of the study was to measure pavement performance through the use of the Present Serviceability Index (PSI) - Pavement Performance concepts as developed by the AASHO Road Test and to explore the usefulness of this type of data as a pavement management tool. Projects in the vicinity of the major urban centers were not included in this study due to the extra time that would be required to isolate accurate traffic data in these areas. Projects consisting of asphalt surface courses on crushed stone base sections were not included.

Corridor Management Pilot Projects, 2004

Managing existing and newly constructed highway corridors has recently become a significant concern in many states, including Iowa. As urban land and land on the urban fringe develops, there is pressure to add features such as commercial driveways, at-grade public road intersections, and traffic signals to arterial highway routes that should primarily serve high-speed traffic. This diminishes the speed and traffic capacity of such roadways and can also cause significant safety issues. if mobility and safety are diminished, the value of the highway investment is diminished. Since a major highway corridor improvement may cost tens of millions of dollars or more, corridor management is as critical to preserving that investment as is more "hard side" management practices such as pavement or bridge management. Corridor management is a process that applies access management principles to highway corridors in an attempt to balance the competing needs of traffic service, safety, and support for land development. This project helped to identify routes that should be given high priority for corridor management. The pilot study in the form of two corridor management case studies provides an analytical process that can be replicated along the other Iowa commuting corridors using commonly available transportation and land use data resources. It also offers a general set of guidelines for the Iowa Department of Transportation to use in the development of its own comprehensive corridor management program.

Iowa Department of Transportation Office of Research & Analytics Guidance on Data Management Plan (DMP) Requirements for Federally Funded Research Projects

The Iowa Department of Transportation Office of Research & Analytics has created this Guide to help researchers and contractors of the Iowa DOT attain compliance with Federal and Iowa DOT Public Access Policies for transportation-related research publications and datasets. This guide provides direction for filling out the data management plan template (also attached to this record) that will help satisfy Iowa DOT and U.S. DOT requirements.

Legal issues in promoting FOSS in R+D projects - Policy, Organisation and Management

Creating and using FLOSS in R+D projects raises several legal issues, which need to be managed as soon as possible - preferably during the project planning stage. Challenges in the areas of project structure and policy, licenses and licensing, exploitation strategies, community management, and FLOSS-friendliness in general all have their legal aspects, which are commented here. Some recommendations are made for assisting in the use of FLOSS in R+D projects, especially in multiple party consortiums.

Release Process Effectiveness - Case of Operating Room Management Software

Työn päätavoitteena oli tuoda esiin tärkeimmät julkistamisprosessin tehokkuuteen vaikuttavat tekijät. Tutkimuksessa tarkasteltiin aihetta julkistamisprojektien vetäjän näkökulmasta. Kirjallinen selvitys kattaa keskeisimmät ohjelmistoprosessin, palvelun laadun sekä projektihallinnan teoriat. Kokeellisena aineistona käytettiin asiakkailta ja myynnin sekä käyttöönoton organisaatioilta tullutta palautetta ja asiantuntijahaastatteluita. Case-tuotteena tarkasteltiin suuren kansainvälisen yrityksen jälleenmyymää leikkaussalihallinnan ohjelmistoa. Tärkeimpiä julkistamisprosessin tehokkuuteen vaikuttavia tekijöitä ovat tiekartan ja julkistamispakettien sisällön hallinta, projektin aikataulujen pitäminen, rehellinen ja nopea kommunikaatio myyntikanavaan ja asiakkaille, sekä hyvin toteutettu testaus. Työssä käydään läpi esimerkkistrategioita kehittymiseen näillä alueilla.

Introducing Basic Systematic Requirements Engineering Practices in Small Organizations with an Easy to Adopt Method

Requirements-relatedissues have been found the third most important risk factor in software projects and as the biggest reason for software project failures. This is not a surprise since; requirements engineering (RE) practices have been reported deficient inmore than 75% of all; enterprises. A problem analysis on small and low maturitysoftware organizations revealed two; central reasons for not starting process improvement efforts: lack of resources and uncertainty; about process improvementeffort paybacks.; In the constructive part of the study a basic RE method, BaRE, was developed to provide an; easy to adopt way to introduce basic systematic RE practices in small and low maturity; organizations. Based on diffusion of innovations literature, thirteen desirable characteristics; were identified for the solution and the method was implemented in five key components:; requirements document template, requirements development practices, requirements; management practices, tool support for requirements management, and training.; The empirical evaluation of the BaRE method was conducted in three industrial case studies. In; this evaluation, two companies established a completely new RE infrastructure following the; suggested practices while the third company conducted continued requirements document; template development based on the provided template and used it extensively in practice. The; real benefits of the adoption of the method were visible in the companies in four to six months; from the start of the evaluation project, and the two small companies in the project completed; their improvement efforts with an input equal to about one person month. The collected dataon; the case studies indicates that the companies implemented new practices with little adaptations; and little effort. Thus it can be concluded that the constructed BaRE method is indeed easy to; adopt and it can help introduce basic systematic RE practices in small organizations.

On Effort Estimation in Software Projects

Software engineering is criticized as not being engineering or 'well-developed' science at all. Software engineers seem not to know exactly how long their projects will last, what they will cost, and will the software work properly after release. Measurements have to be taken in software projects to improve this situation. It is of limited use to only collect metrics afterwards. The values of the relevant metrics have to be predicted, too. The predictions (i.e. estimates) form the basis for proper project management. One of the most painful problems in software projects is effort estimation. It has a clear and central effect on other project attributes like cost and schedule, and to product attributes like size and quality. Effort estimation can be used for several purposes. In this thesis only the effort estimation in software projects for project management purposes is discussed. There is a short introduction to the measurement issues, and some metrics relevantin estimation context are presented. Effort estimation methods are covered quite broadly. The main new contribution in this thesis is the new estimation model that has been created. It takes use of the basic concepts of Function Point Analysis, but avoids the problems and pitfalls found in the method. It is relativelyeasy to use and learn. Effort estimation accuracy has significantly improved after taking this model into use. A major innovation related to the new estimationmodel is the identified need for hierarchical software size measurement. The author of this thesis has developed a three level solution for the estimation model. All currently used size metrics are static in nature, but this new proposed metric is dynamic. It takes use of the increased understanding of the nature of the work as specification and design work proceeds. It thus 'grows up' along with software projects. The effort estimation model development is not possible without gathering and analyzing history data. However, there are many problems with data in software engineering. A major roadblock is the amount and quality of data available. This thesis shows some useful techniques that have been successful in gathering and analyzing the data needed. An estimation process is needed to ensure that methods are used in a proper way, estimates are stored, reported and analyzed properly, and they are used for project management activities. A higher mechanism called measurement framework is also introduced shortly. The purpose of the framework is to define and maintain a measurement or estimationprocess. Without a proper framework, the estimation capability of an organization declines. It requires effort even to maintain an achieved level of estimationaccuracy. Estimation results in several successive releases are analyzed. It isclearly seen that the new estimation model works and the estimation improvementactions have been successful. The calibration of the hierarchical model is a critical activity. An example is shown to shed more light on the calibration and the model itself. There are also remarks about the sensitivity of the model. Finally, an example of usage is shown.

Business Process Modeling in Software Requirements Engineering for Small and Medium Software Projects

Vaatimusmäärittelyn tavoitteena on luoda halutun järjestelmän kokonaisen, yhtenäisen vaatimusluettelon vaatimusten määrittämiseksi käsitteellisellä tasolla. Liiketoimintaprosessien mallintaminen on varsin hyödyllinen vaatimusmäärittelyn varhaisissa vaiheissa. Tämä työ tutkii liiketoimintaprosessien mallintamista tietojärjestelmien kehittämistä varten. Nykyään on olemassa erilaisia liiketoimintaprosessien mallintamiseen tarkoitettuja tekniikoita. Tämä työ tarkastaa liiketoimintaprosessien mallintamisen periaatteet ja näkökohdat sekä eri mallinnustekniikoita. Uusi menetelmä, joka on suunniteltu erityisesti pienille ja keskisuurille ohjelmistoprojekteille, on kehitetty prosessinäkökohtien ja UML-kaavioiden perusteella.

Cost Estimation of Engineering Environment Services

Työn tavoitteena oli kehittää tutkittavan insinööriyksikön projektien kustannusestimointiprosessia, siten että yksikön johdolla olisi tulevaisuudessa käytettävänään tarkempaa kustannustietoa. Jotta tämä olisi mahdollista, ensin täytyi selvittää yksikön toimintatavat, projektien kustannusrakenteet sekä kustannusatribuutit. Tämän teki mahdolliseksi projektien kustannushistoriatiedon tutkiminen sekä asiantuntijoiden haastattelu. Työn tuloksena syntyi kohdeyksikön muiden prosessien kanssa yhteensopiva kustannusestimointiprosessi sekä –malli.Kustannusestimointimenetelmän ja –mallin perustana on kustannusatribuutit, jotka määritellään erikseen tutkittavassa ympäristössä. Kustannusatribuutit löydetään historiatietoa tutkimalla, eli analysoimalla jo päättyneitä projekteja, projektien kustannusrakenteita sekä tekijöitä, jotka ovat vaikuttaneet kustannusten syntyyn. Tämän jälkeen kustannusatribuuteille täytyy määritellä painoarvot sekä painoarvojen vaihteluvälit. Estimointimallin tarkuutta voidaan parantaa mallin kalibroinnilla. Olen käyttänyt Goal – Question – Metric (GQM) –menetelmää tutkimuksen kehyksenä.

Creating customer relationship management concept for engineering and service business

Customer relationship management has been one essential part of marketing for over 20 years. Today’s business environment is fast changing, international and highly competitive, and that is why the most important factor for long-term profitability is one-to-one customer relationships. However, managing relationships and serving customers that are profitable has been always challenging. In this thesis the objective was to define the main obstacles that the case company must overcome to succeed in CRM. Possible solutions have also been defined. The main elements of the implementation i.e. people, processes and technologies, can clearly be found behind these matters and solutions. This thesis also presents theoretical information about CRM and it is meant to act as a guide book inside the organisation to spread information about CRM for those who are not so familiar with the topic.

Factors of customer project profitability in an engineering industrial enterprise

The purpose of the study is to find factors affecting projects' profitability in project business. The issue is approached from customer profitability and project management point of view. The study has been made for a big Finnish company acting in a global market place. The research method is quantitative. Research hypotheses are based on the literature. The used database is originated from the company's ERP- (enterprise resource planning) and project financial follow-up —system. The findings of the study supported the hypotheses weakly. Obviously profitability fluctuated depending on a customer and a project manager. The reasons could not be justified with the variables used in the research.