Готові списки джерел за темами / SCRM process

Добірка наукової літератури з теми "SCRM process"

Автор: Grafiati

Опубліковано: 19 червня 2021

Оновлено: 1 лютого 2022

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся зі списками актуальних статей, книг, дисертацій, тез та інших наукових джерел на тему "SCRM process".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Статті в журналах з теми "SCRM process":

Birkel, Hendrik Sebastian, and Evi Hartmann. "Internet of Things – the future of managing supply chain risks." Supply Chain Management: An International Journal 25, no. 5 (April 20, 2020): 535–48. http://dx.doi.org/10.1108/scm-09-2019-0356.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Purpose The purpose of this paper is to investigate the implications for supply chain risk management (SCRM) by applying internet of things (IoT). Therefore, the impact and effects on the SCRM process, as well as the internal and external pathway and the outcome of SCRM are examined. Design/methodology/approach This study adopts a multiple case study methodology with twelve companies from the manufacturing industry. This study is guided by the information processing theory (IPT) and a theory-grounded research framework to provide insights into information requirements and information processing capabilities for IoT-supported SCRM. Findings The studied cases demonstrate an increase in data availability in the companies that contribute to improved process transparency and process management. Furthermore, the process steps, risk transparency, risk knowledge and risk strategies have been enhanced, which enabled improved SCRM performance by fitting information requirements and information processing capabilities, thus allowing for competitive advantage. Practical implications This study offers in-depth insights for SCRM managers into the structure of IoT systems, primary use cases and changes for the process itself. Furthermore, implications for employees, incentives and barriers are identified, which could be used to redesign SCRM. Originality/value This study addresses the requirement for additional empirical research on technology-enhanced SCRM, supported by IPT as a theoretical foundation. The radical change of SCRM by IoT is demonstrated while discussing the human role, implications for SCRM strategies and identifying relevant topics for future development.

Prakash, Surya, Gunjan Soni, and Ajay Pal Singh Rathore. "A critical analysis of supply chain risk management content: a structured literature review." Journal of Advances in Management Research 14, no. 1 (February 6, 2017): 69–90. http://dx.doi.org/10.1108/jamr-10-2015-0073.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Purpose The research on supply chain risk management (SCRM) is visibly on the rise, although its literature still lacks the state of the art that critically analyzes its content. The SCRM literature seems to require studies that utilize risk typology, sources of risk, etc. for reviewing the topic. The purpose of this paper is to bridge the gap by synthesizing the information obtained from 343 articles across 85 journals. This study also presents a critical analysis of the content of SCRM in a structured manner to identify the directions for future research. Design/methodology/approach A systematic literature review (SLR) was devised and adopted, which involved the selection, classification, and evaluation of 343 research articles published over a period of 11 years (2004-2014). The content of extant SCRM literature was critically analyzed and synthesized from the perspective of the risk management process (RMP). Findings The analysis of extant literature shows that there is a marked rise in research in the SCRM area, especially after the year 2005. It was observed that not only risk but also different forms of uncertainties make supply chain (SC) operations difficult to manage. The SCRM actions yielded most benefits when their implementation was at chain or network level and managed strategically. The analysis also reveals that the manufacturing sector is most affected by risks and highly investigated by researchers. Practical implications A complete process for SCRM based on risk stratification, objectives of risk management, and RMP will be a guiding model for firms to manage risks. The research gaps identified and future directions provided here will encourage researchers and managers to devise new methods, tools, and techniques to address the risks in modern SC operations. Originality/value An SLR and risk-based content classification of SCRM literature were performed. To identify, locate, select, and analyze the SCRM literature, a structured and systematic process was adopted with some very rarely used methods such as two levels of search keywords, and strings were formulated to locate the most relevant articles in major academic databases.

Fan, Yiyi, and Mark Stevenson. "A review of supply chain risk management: definition, theory, and research agenda." International Journal of Physical Distribution & Logistics Management 48, no. 3 (April 3, 2018): 205–30. http://dx.doi.org/10.1108/ijpdlm-01-2017-0043.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Purpose The purpose of this paper is to review the extant literature on supply chain risk management (SCRM, including risk identification, assessment, treatment, and monitoring), developing a comprehensive definition and conceptual framework; to evaluate prior theory use; and to identify future research directions. Design/methodology/approach A systematic literature review of 354 articles (published 2000-2016) based on descriptive, thematic, and content analysis. Findings There has been a considerable focus on identifying risk types and proposing risk mitigation strategies. Research has emphasised organisational responses to supply chain risks and made only limited use of theory. Ten key future research directions are identified. Research limitations/implications A broad, contemporary understanding of SCRM is provided; and a new, comprehensive definition is presented covering the process, pathway, and objectives of SCRM, leading to a conceptual framework. The research agenda guides future work towards maturation of the discipline. Practical implications Managers are encouraged to adopt a holistic approach to SCRM. Guidance is provided on how to select appropriate risk treatment actions according to the probability and impact of a risk. Originality/value The first review to consider theory use in SCRM research and to use four SCRM stages to structure the review.

Dias, Gabriela Costa, Ualison Rébula de Oliveira, Gilson Brito Alves Lima, and Vicente Aprigliano Fernandes. "Risk Management in the Import/Export Process of an Automobile Company: A Contribution for Supply Chain Sustainability." Sustainability 13, no. 11 (May 27, 2021): 6049. http://dx.doi.org/10.3390/su13116049.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Supply chain risk management (SCRM) is imperative to achieve business sustainability in the long-term perspective and also to increase companies’ competitiveness. ISO 31000—Risk Management explains in its latest versions the need for companies to integrate a risk management process into their business models. Complementary to this standard, ISO 31010 presents 31 risk tools to guide companies in this task. However, a question of practical application arises as to which tools should be used for each stage of the SCRM process. In view of the raised question, the main objective of this research is to select ISO 31010 tools that can be used in each of the stages (identify, analyze, and evaluate) of the risk management of the import and export process of an automotive industry located in Brazil. For this, the analytic hierarchy process (AHP method) was used in a case study to prioritize the tools to compose the SCRM. As practical implications, this study resulted in the suggestion of a structured risk management process, considering the assessment of key professionals of the department studied in the company.

Salleh Hudin, Norlaile, and Abu Bakar Abdul Hamid. "Supply Chain Risk Management in Automotive Small and Medium Enterprises in Malaysia." Applied Mechanics and Materials 773-774 (July 2015): 799–803. http://dx.doi.org/10.4028/www.scientific.net/amm.773-774.799.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

The current automotive supply chain is facing more risks than ever due to the heavy dependencies of local automotive component manufacturers with foreign and established global producers. In response, this paper is designed to explore the supply chain risk management (SCRM) practice of automotive industry in Malaysia. In-depth case studies were conducted at two automotive components manufacturers based on three constructs of SCRM framework including the SCRM process, tools used in SCRM and techniques to minimize risk. The case studies revealed that the automotive companies implemented failure mode and effect analysis (FMEA), 5 why analysis, impact-aspect study, and recovery planning to manage their supply chain risks. In addition, brainstorming techniques, experience and expert judgment were mainly used as risk identification and assessment techniques. Most of the risks encountered during operations were dealt by reactive strategies such as back-up suppliers and increasing buffer stocks. Overall, the automotive companies are heading towards more formal and sophisticated SCRM especially with the certification of TS16949 although there are still plenty of rooms for improvements in the risk identification and risk assessment techniques since very limited quantitative techniques were evidenced.

Conklin, Art, and Chris Bronk. "Enhancing a SCRM Curriculum With Cybersecurity." International Journal of Systems and Software Security and Protection 9, no. 2 (April 2018): 46–56. http://dx.doi.org/10.4018/ijsssp.2018040104.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Supply chain-related curricula exist across many universities, with many including risk management as an important or focal element. With the rise of software-driven technology across the supply chain, how can firms manage the inherent risks associated with software as part of a procurement process? This article examines how to provide context appropriate cybersecurity exemplars in a model supply chain education program, bringing to light the issue of embedded risk in software acquisition. Through a series of specifically placed educational elements that provide targeted cybersecurity knowledge to students, the objective is to provide additional skill sets for future supply chain professionals to assist firms in including software related cybersecurity risk as a component in SCRM.

Fagundes, Marcus Vinicius Carvalho, Eduardo Oliveira Teles, Silvio A. B. Vieira de Melo, and Francisco Gaudêncio Mendonça Freires. "Supply chain risk management modelling: A systematic literature network analysis review." IMA Journal of Management Mathematics 31, no. 4 (September 5, 2020): 387–416. http://dx.doi.org/10.1093/imaman/dpaa019.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Abstract The modelling of supply chain risk management (SCRM) has attracted increasing attention from researchers and professionals. However, a systematic network analysis of the literature to understand the development of research over time is lacking. Therefore, this study reviews SCRM modelling and its evolution as a scientific field. We collected 566 papers published in the Scopus database and shortlisted 120 for review. We have analysed the field's performance, mapped the most influential studies, as well as the generative and evolutionary research areas, and derived future research directions. Using bibliometric methods and tools for citation network analysis to understand the field's dynamic development, we find that five generative research areas provide the fundamental knowledge for four evolutionary research areas. The interpretation of gaps and trends in these areas provides an SCRM modelling timeline with 14 future research directions, which should consider adopting a holistic SCRM approach and developing prescriptive and normative risk models. The holistic approach enables more research on key factors—like process integration, design, information risk, visibility and risk coordination—that directly impact industry, decision-makers and sustainability needs. Risk models with evolved prescriptive and normative typology should respect both business model strategies and actual supply chain performance.

Yoga Irsyadillah, N., and S. Dadang. "A LITERATURE REVIEW OF SUPPLY CHAIN RISK MANAGEMENT IN AUTOMOTIVE INDUSTRY." Journal of Modern Manufacturing Systems and Technology 4, no. 2 (September 30, 2020): 12–22. http://dx.doi.org/10.15282/jmmst.v4i2.5020.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Supply chain risk management (SCRM) has a strong influence on the cooperation among partners and the performance of the entire production chain across the world. A supply chain designed to minimize risks enables firms to establish a competitive position and provides long-term benefits to stakeholders. Especially in a complicated and slow-growing industry like Automotive Industry. The auto industry's most important segments including commercial vehicles and passenger cars. Global sales of passenger cars are forecast to fall to 59.5 million units in 2020, down from a peak of 79.6 in 2017. The SCRM system should be structured to manage both routine and extraordinary risks, such as economical crisis, global pandemic issues, or even other unexpected event. The risks should be managed both reactively, by monitoring changes in the chain, the needs of customers, technology and the strategies of suppliers and competitors, among others, to enable quick reaction to events; and proactively, to identify risks and implement actions to prevent them or minimize their impacts. The basic risk management process consists of identifying, evaluating, mitigating and controlling risks. The objective of this paper is to analyze how SCRM could manages the risk factors in Automotive Industry’s supply chain in three different segmentation perspective. To achieve this aim, we performed a qualitative, applied and exploratory field study of the development trend of automotive Industry across the world, Asia, and Indonesia in terms of gaining more insight about the latest development trend of SCRM implementation in various segmentation. The data were collected by doing literature review from previous published research related to SCRM in Automotive Industry.

Bak, Ozlem. "Supply chain risk management research agenda." Business Process Management Journal 24, no. 2 (April 3, 2018): 567–88. http://dx.doi.org/10.1108/bpmj-02-2017-0021.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Purpose Supply chain risk (SCR) has increasingly attracted academic and corporate interest; however, the SCR debate in academic literature is rather limited to case- and location-specific studies. Hence, the purpose of this paper is to utilize a systematic literature review (SLR) to explore the SCR research trends and gaps within the management literature. Design/methodology/approach To achieve the research objective an SLR, looking into 25 years since 1990, into supply chain risk management (SCRM) was conducted, which resulted in 114 papers. Findings While the SCRM literature is growing, results from the SLR identified limited organized understanding of what constitutes a holistic SCR process, and high reliance of particular categories for SCR, such as the high reliance on specific country settings (the USA and the UK); limited presence of cross competitive SCR process analysis and challenges in developing conceptual SCR frameworks. Research limitations/implications The SCR embeds categories of location, scope of supply chain, risk management tools, and the industry sectors involved. The search for related publications was mainly used from a wide range of coverage from accountancy to design in SCR; hence, although there is indication to specific industries, and foci of risk, this could be explored further. Practical implications This review of SCRM identifies various research gaps and directions for future research to develop theory and a practical understanding of SCR. Originality/value The current literature on SCR has been assessed based on its definition and utilization. The current paper bridges this gap by synthesizing the diverse academic journal papers into the categories based on the design continuum, relationship continuum, process continuum and economic continuum. In addition, it highlights the gaps in industry context, theoretical contribution, geographic location, and research methods applied and addresses the scope for further research.

Tarei, Pradeep Kumar, Jitesh J. Thakkar, and Barnali Nag. "Benchmarking the relationship between supply chain risk mitigation strategies and practices: an integrated approach." Benchmarking: An International Journal 27, no. 5 (April 28, 2020): 1683–715. http://dx.doi.org/10.1108/bij-12-2019-0523.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

PurposeThe purpose of this paper is to explore the relationship between various risk management strategies and risk management practices in order to design and hence enact a suitable supply chain risk mitigation (RM) plan. Additionally, this study proposes a hierarchical framework to explain the mutual relationship between supply chain risk management (SCRM) practices and strategies by considering the underlying dimensions between them.Design/methodology/approachAn amalgamation of systematic literature analysis (SLA) and correspondence analysis (CA) has been performed to develop the conceptual framework. A real-life case of Indian petroleum supply chain has been considered to validate and explain the proposed model.FindingsThe results reveal three underlying dimensions, which associate the relationship between RM strategies. They are, risk adaptability of SC managers with a variance of 34.71%, followed by resource capability of the firm and the degree of sophistication of RM practices, with variances of 27.72 and 20.35%, respectively. Risk avoidance strategy comprises of practices such as supplier evaluation, technology adaption, flexible process and information security. On the other extreme, the risk sharing strategy includes revenue sharing, insurance, collaboration, public–private partnership and so on as essential RM practices.Research limitations/implicationsThe study not only focuses on the distinction between RM strategies and practices, which were used interchangeably in the prior literature, but also provides an association between the same by exploring the underlying dimensions. These underlying dimensions perform a crucial role while developing a risk management plan. This study explicitly focuses on the RM step of SCRM process. Pre and post risk mitigation phases of SCRM process, such as risk assessment and risk monitoring, are beyond the scope of the current research.Originality/valueThe paper develops a framework for mapping various RM strategies with their corresponding practices by considering the Indian petroleum supply chain as a viable case study. Various theoretical and business implications are derived in the context of the developing country.

Більше джерел

Дисертації з теми "SCRM process":

Wiss, Gullberg Ellen, and Alison Karlsson. "SCRM-processen i byggkeramikbranschen : Innan och under COVID-19 och framåt." Thesis, Linnéuniversitetet, Institutionen för ekonomistyrning och logistik (ELO), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-104983.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Titel: SCRM-processen i byggkeramikbranschen: innan och under COVID-19 och framåt Författare: Alison Karlsson & Ellen Wiss Gullberg Examinator: Peter Berling Handledare: Helena Forslund Bakgrund: Byggkeramikbranschen har visat sig vara en ostuderad bransch med flera litteraturgap, bland annat i relation till SCRM-processen och till COVID-19 pandemin. Syfte: Att genomföra en fallstudie av hur försörjningskedjor i byggkeramikbranschen har arbetat med SCRM-processen innan och under COVID-19 pandemin, samt att skapa en SCRM-process som är specificerad för byggkeramikbranschen. Frågeställningar: Hur har arbetet med SCRM-processen sett ut i återförsäljarens försörjningskedjor innan och under COVID-19 pandemin? Hur skulle en SCRM-process specificerad för byggkeramikbranschen se ut? Genomförande: Genom intervjuer med respondenter från flera aktörer i återförsäljarens försörjningskedjor samlades empiri så att arbetet med SCRM-processen innan och under COVID-19 pandemin kunde kartläggas. Empiri samlades även in från en branschexpert och från försörjningskedjornas aktörer till den andra frågeställningen. Därefter gjordes förslag till en sårbarhetskarta, en riskbedömningsmatris och en riskhanteringsmatris för byggkeramikbranschen, som slutligen sammanfattades till en SCRM-process specificerad för byggkeramikbranschen. Slutsats: Arbetet med SCRM-processen innan COVID-19 tycks inte ha skett i återförsäljarens försörjningskedjor, men alla studerade aktörer har använt sig av SCRM-processen i olika mån under COVID-19, varav återförsäljaren har arbetat mest och leverantörerna arbetat minst med SCRM-processen. En SCRM-process specificerad för byggkeramikbranschen har skapats och har sammanfattats både i text och i figur, där specifika verktyg och branschspecifika aspekter har rekommenderats. Nyckelord: SCRM-process, byggkeramikbranschen, byggkeramik, COVID-19.
Title: The SCRM process in the ceramic tiles business: before and during COVID-19 and forward Researchers: Alison Karlsson & Ellen Wiss Gullberg Examinator: Peter Berling Supervisor: Helena Forslund Background: The ceramic tiles business has turned out to be an unstudied business with many literature gaps, among others in relation to the SCRM process and to the COVID-19 pandemic. Purpose: To do a case study of how supply chains in the ceramic tiles business have worked with the SCRM process before and during the COVID-19 pandemic, and to create a SCRM process that is specified for the ceramic tiles business. Research questions: How has the work with the SCRM process looked like in the reseller’s supply chains before and during the COVID-19 pandemic? What could a SCRM process specified for the ceramic tiles business look like? Method: Through interviews with respondents from many of the actors in the reseller’s supply chains, empirical data was collected so that the work with the SCRM process before and during the COVID-19 pandemic could be mapped. Empirical data was also collected from a business expert and from the supply chain actors to the second research question. Thereafter a suggestion for a supply chain vulnerability map, a risk assessment matrix and a risk handling matrix for the ceramic tiles business was created, which was finally summarized to a SCRM process specified for the ceramic tiles business. Conclusion: The work with the SCRM process before COVID-19 seems to have not existed in the reseller’s supply chains, but all of the actors of the supply chains that were studied have used the SCRM process in different degrees during COVID-19, where the reseller has worked the most and the suppliers have worked the least with the SCRM process. A SCRM process specified for the ceramic tiles business has been created and has been summarized both in text and in figure, where specific tools and business specific aspects have been recommended. Keywords: SCRM process, ceramic tiles business, ceramic tiles, COVID-19.

Krbušek, Adam. "Použití metodiky SCRUM v inovačním procesu firmy." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-261990.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Diploma thesis deals with SCRUM methodology and its uses in innovation management. The main objective of the thesis is creation of a specific framework which will enable to use SCRUM methodology in the innovation process. The thesis is divided into three parts. The first part presents theoretical framework important for the main research. This part contains literature review and research dedicated to the SCRUM methodology and innovation process. The second part of the thesis deals with mapping of the SCRUM methodology to Hladik's innovation process. This part also contains own design of the innovation management process. The third part of the thesis is dedicated to the case study. The case study uses described innovation management process for verification of the hypothesis saying that is possible to use SCRUM methodology in the innovation process. The author's contribution lies in creation of a framework which provides agile alternative to the classical innovation management models.

Zhang, Yanpeng, and Ce Zhou. "Introducing Domain Specific Language for Modeling Scrum Projects." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13328.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Context. A clear software process definition is important because it can help developers to share a common understanding and improve the development effectiveness. However, if the misconceptions or misunderstandings are introduced to the team during the process definition, it will bring numerous uncertain problems to the projects and reduce the productivity. Scrum is one of the most popular Agile development processes. It has been frequently used in software development. But the misunderstanding of usage of the Scrum method always leads to situations where teams cannot achieve the hyper-productivity even failure. Therefore, introducing a reasonable graphical language for describing the Scrum process may help learners to gain a correct and common understanding of the Scrum method. Objectives. In this study, we introduce a graphical Domain Specific Language for modeling the Scrum process and specific Scrum projects. Further, we evaluated the proposed language to figure out if and how this language can help developers learn Scrum method and understand the specific Scrum projects. For the first, we decide to extract the essential elements and their relative relationships of the Scrum process, and based on that, we define and specify the graphical language. After that, we evaluate the proposed graphical language to validate whether this language can be considered as useful to help developers to learn Scrum method and understand the specific Scrum projects. Methods. In order to define the graphical language, we studied and reviewed the literature to extract the essential elements and their relationships for describing the Scrum process. Based on that, we defined and specified the graphical DSL. With the aim of evaluating the proposed graphical language, we performed the experiment and survey method. This experiment was conducted in an educational environment. The subjects were selected from the undergraduate and master students. At the same time, we carried out a survey to capture the developers‘ opinions and suggestions towards the proposed language in order to validate its feasibility. Results. By studying the literature, we listed and specified the essential elements for describing the Scrum process. By executing the experiment, we evaluated the efficiency and effectiveness of learning Scrum in using the proposed language and the natural language. The result indicates that the graphical language is better than the natural language in training Scrum method and understanding specific Scrum projects. The result shows that the proposed language improved the understandability of the Scrum process and specific Scrum projects by more than 30%. We also performed a survey to investigate the potential use of the proposed graphical DSL in industry. The Survey results show that participants think the proposed graphical language can help them to better understand the Scrum method and specific Scrum projects. Moreover, we noticed that the developers who have less Scrum development experience show more interests in this proposed graphical language. Conclusions. To conclude, the obtained results of this study indicate that a graphical DSL can improve the understandability of Scrum method and specific Scrum projects. Especially in managing the specific Scrum project, subjects can easily understand and capture the detailed information of the project described in the proposed language. This study also specified the merits and demerits of using the graphical language and textual language in describing the Scrum process. From the survey, the result indicates that the proposed graphical language is able to help developers to understand Scrum method and specific Scrum projects in industry. Participants of this survey show positive opinion toward the proposed graphical language. However, it is still a rather long way to applying such a graphical language in Scrum projects development because companies have to consider the extra learning effort of the graphical DSL.

Svoboda, Radek. "Efektivní využití SCRUM metodiky ve vývojovém týmu." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2017. http://www.nusl.cz/ntk/nusl-318346.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

The master thesis focuses on more efficient application of Scrum methodology in a development team within specific company. The thesis takes an advantage from the SW-CMM philosophy applied in agile environment in order to achieve better effectivity. Theorethical base is utilized for a comparison with current state in the company described in analytical part. Proposals for a solution of current situation are based on drawback detection. Proposals are subject for risk analysis followed by precaution. Costs of proposals implementation with included precautions are evaluated in economic evaluation part. This part also contains benefits of proposals.

Kubalcová, Monika. "ITIL v prostředí agilního vývoje software metodikou Scrum." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2014. http://www.nusl.cz/ntk/nusl-235418.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

This thesis follows concept of integration ITIL library and agile methodology Scrum into the IT company developing IT services. After theoretical analysis of both concepts and analysis of chosen company, we will develope methodology, which will tie both process approaches and ensure their perfect synergy. As a methodology support, web application was developed. It evaluates effectivness of processes using key informations and their plot representation. Proposed methodology was presented in the AVG Technologies, which used described processes as template for its internal proceses. Main result of the thesis is set of templates describing processes, which could be specified and applied in companies using Scrum together with ITIL for their development.

Srirangarajan, Ananth Lall Pradeep Umphress David A. "The scrum process for independent programmers." Auburn, Ala, 2009. http://hdl.handle.net/10415/1617.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Kodali, Manvisha. "TRACEABILITY OF REQUIREMENTS IN SCRUM SOFTWARE DEVELOPMENT PROCESS." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-28326.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Incomplete and incorrect requirements might lead to sub-optimal software products, which might not satisfy customers’ needs and expectations. Software verification and validation is one way to ensure that the software products meets the customers’ expectations while delivering the correct functionality. In this direction, the establishment and the maintenance of traceability links between requirements and test cases have been appointed as promising technique towards a more efficient software verification and validation. Through the last decades, several methodologies supporting traceability have been proposed, where most of them realize traceability by implicitly exploiting existing documents and relations. Nevertheless, parts of the industry is reluctant to implement traceability within software development processes due to the intrinsic overhead it brings. This is especially true for all those light-weight, code-centric software development processes, such as scrum, which focus on the coding activities, trying to minimizing the administrative overhead. In fact, the lack of documentation finishes to hamper the establishment of those trace links which are the means by which traceability is realized. In this thesis, we propose a methodology which integrates traceability within a scrum development process minimizing the development effort and administrative overhead. More precisely we i) investigate the state-of-the-art of traceability in a scrum development process, ii) propose a methodology for supporting traceability in scrum and iii) evaluate such a methodology upon an industrial case study provided by Westermo.

SILVA, Ivonei Freitas da. "A scrum-inspired process for software product lines scoping." Universidade Federal de Pernambuco, 2013. https://repositorio.ufpe.br/handle/123456789/12265.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Scoping in Software Product Lines (SPL) is the first step to identify products, features, and assets in a market segment. Traditional approaches for SPL scoping are heavyweight and upfront processes in scenarios with unpredictable changes and little resources. An incurred key challenge is handling systematically the iterativeness, adaptability, and feedback in the SPL scoping process. As a final consequence, the software industry can hamper investment in the SPL scoping. In this context, the Scrum framework, as the most popular agile approach to foster the iterativeness, adaptability, and feedbacks, can address that challenge. Previous studies have combined Scrum into some SPL activities with good results. This thesis provides a process, named of RiPLE-SCA, for SPL scoping inspired in the Scrum practices. This process bases on industrial evidence (a case study of a traditional SPL scoping), expert opinion on agile SPL (through a survey), and scientific literature about agile SPL (a systematic mapping). A feasibility study and a cross-case study carried out with two industrial partners indicated that the RiPLE-SCA is practicable and appropriate for an industrial setting as well as fosters iterativeness, adaptability, and feedbacks detecting early obsolete features and changes in domain, requirements, features, and technology.
Submitted by João Arthur Martins (joao.arthur@ufpe.br) on 2015-03-12T18:58:41Z No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Made available in DSpace on 2015-03-12T18:58:41Z (GMT). No. of bitstreams: 2 Tese Ivonei Freitas da Silva.pdf: 9233841 bytes, checksum: 6029df71deecd12c97bd99e1787a8361 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2013-10-29
CNPq
A atividade de escopo em linhas de produto de software é o primeiro passo para identificar produtos, características e ativos de software em um segmento de mercado. As abordagens tradicionais para escopo de linhas de produto de software são processos densos e abrangentes em cenários com mudanças imprevisíveis e com poucos recursos. Um desafio chave nesse cenário é o gerenciamento sistemático da iteratividade, adaptabilidade e do feedback no processo de escopo de linhas de produto de software. Como último efeito, a indústria de software pode restringir investimentos no processo de escopo. Neste contexto, o framework Scrum, abordagem mais popular para incentivar a iteratividade, a adaptabilidade e o feedback, pode lidar com esse desafio. Estudos anteriores têm combinado Scrum com algumas atividades de linhas de produto de software obtendo bons resultados. Esta tese define um processo, denominado de RiPLE-ASC, para o escopo da linha de produtos de software inspirado nas práticas do Scrum. Este processo basea-se nas evidências da indústria (um estudo de caso real de escopo de linhas de produto usando uma abordagem tradicional), na opinião de especialistas em linhas de produto de software ágeis (através de um survey) e na literatura científica sobre linhas de produto de software ágeis (uma mapeamento sistemático). Um estudo de viabilidade e um estudo de caso “cross-case” executados com dois parceiros industriais de nosso grupo de pesquisa indicaram que o RiPLE-ASC tem aplicação prática e adequa-se em um ambiente de produção de software industrial bem como incentiva a iteratividade, adaptabilidade e o feedback detectando cedo características obsoletas e mudanças no domínio, requisitos, características e tecnologia

Malone, Michael W. "Process subversion in Agile Scrum software development| A phenomenological approach." Thesis, Capella University, 2014. http://pqdtopen.proquest.com/#viewpdf?dispub=3632735.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

This qualitative study examined the ways in which process subversion, defined as any attempt, conscious or unconscious, to work around, ignore, or turn to one's own purposes an established process, occurs in Scrum software development. Scrum is a software development methodology that uses self-managing teams and a well-defined process but does not dictate developer practices. It has been shown in previous research that problems with Scrum can cause issues with productivity and software quality. This descriptive phenomenological study specifically examined the ways in which process subversion was experienced by Scrum Masters. The Scrum Master is a coach and facilitator to the development team in Scrum. The study revealed a wide variety of perceptions of the Scrum Master's role as well as sources of subversion ranging from individuals on the development team to the structure of the organization. The study also revealed the creativity used by some Scrum Master in responding to such subversion. This study is important because it fills a gap in the extant literature in dealing with the problems that occur when an organization attempts to use Scrum as its development process, and provides insights that may be helpful in either mitigating the effects of such subversion or preventing it outright.

Marques, Joice Basilio Machado. "OntoSoft: um processo de desenvolvimento ágil para software baseado em ontologia." Universidade de São Paulo, 2017. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-06022018-084132/.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

A formalização e o compartilhamento do conhecimento tem incentivado cada vez mais o uso de ontologias em diversas áreas da computação. Na Engenharia de Software, por exemplo, elas são usadas em diferentes fases do ciclo de vida do software. Especificamente no desenvolvimento de software a ontologia pode ser considerada como um artefato de software que atua na formalização do conhecimento e requisitos, na geração automática de código, na integração contínua e na transformação de dados em conhecimento. No entanto, poucos estudos abordam esses fatores de maneira sistematizada na construção do software baseado em ontologia, ao associar os conceitos da Engenharia de Software à Engenharia de Ontologias. Além disso, as abordagens atuais não inserem princípios ágeis em suas definições. Portanto, este trabalho tem por objetivo definir um processo de desenvolvimento considerando os princípios e valores ágeis para o desenvolvimento de software baseado em ontologia. No processo, denominado OntoSoft, fases, atividades, tarefas, papeis e modelos de artefatos foram definidos de maneira detalhada para guiar as equipes de desenvolvimento. Ademais, foram especificados três cenários de desenvolvimento considerando a complexidade do software a ser desenvolvido, a fim de evidenciar possibilidades distintas na sequência das atividades durante o fluxo de desenvolvimento do software baseado em ontologia. Com base nos estudos de caso conduzidos em diferentes cenários de desenvolvimento, os resultados sugerem que o processo OntoSoft contribui positivamente na produção dos artefatos do software baseado em ontologia, colaborando para a efetividade e produtividade da equipe.
Formalization and knowledge sharing have increasingly encouraged the use of ontologies in several areas of computing. In Software Engineering, for example, they have been used in different phases of the software life cycle. Specifically in software development, an ontology can be considered as a software artifact, which acts in the formalization of knowledge and requirements, automatic generation of code, continuous integration and data transformation into knowledge. However, few studies deal with these factors in a systematized way for the development of ontology based software, regarding to associating Software Engineering and Ontology Engineering concepts. In addition, current approaches do not address agile principles in their definitions. In this sense, this work aims to define a development process concerning the principles and agile values for ontology based software development. In the process, called OntoSoft, phases, activities, tasks, roles, and artifact models were defined in detail to guide development teams. In addition, three development scenarios were specified considering the complexity of the software to be developed, in order to demonstrate distinct possibilities of development flow of the ontology based software. Based on case studies conducted in different development environments, the results suggest that the OntoSoft process contributes positively to the development of ontology based software artifacts, contributing to the effectiveness and productivity of the team.

Більше джерел

Книги з теми "SCRM process":

Rubin, Kenneth S. Essential Scrum: A practical guide to the most popular agile process. Upper Saddle River, NJ: Addison-Wesley, 2012.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Expert Meeting on Social Capacity for Environmental Management (2nd 2004 Renmin University of China). The Second Expert Meeting on Social Capacity for Environmental Management (SCEM): Capacity indicators and development process modeling : selected proceedings. Hiroshima, Japan: Hiroshima International Center for Environmental Cooperation, Graduate School of International Development and Cooperation, Hiroshima University, 2005.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Kovalenko, Vladimir. Design of information systems. ru: INFRA-M Academic Publishing LLC., 2020. http://dx.doi.org/10.12737/987869.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

The tutorial discusses the design features of information systems (is) involved in the implementation of CALS technologies: MRP/MRPII/ERP systems, e-Commerce systems (B2B), supply chain management (SCM), customer relationship management (CRM), and decision support systems (OLAP). The issues of choosing the design technology, software tools for project development, building functional and information models in the environment of Business Studio, MS Visio, Elma, AllFusion Modeling Suite and Oracle Designer 10g, as well as the development of technical and operational documentation are highlighted. The characteristics of CASE technologies and their implementation in the Oracle Designer 10g environment are considered. A comparative analysis of the standards of the organization of the life cycle of creating and using IP, practical recommendations for the development of standard profiles, examples of the development of an IP project based on a cascading model of the life cycle, including using a process approach in the management and automation of processes. The models of the client — server architecture and the structure of cloud computing are considered. Modern approaches to the selection of ready-made is and their implementation in automated enterprises are studied in detail. Meets the requirements of the Federal state educational standards of higher education of the latest generation. It is intended for students (bachelors and specialists) and masters of higher educational institutions studying in the direction of "Applied Informatics". It is also recommended for teachers and specialists working in the field of information technology.

Ullman, DAVID G. Scrum for Hardware Design: Supporting Material for The Mechanical Design Process. David Ullman LLC, 2019.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Bateman, Anthony W., and Roy Krawitz. Structured clinical management: general treatment strategies. Oxford University Press, 2015. http://dx.doi.org/10.1093/med:psych/9780199644209.003.0003.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Chapter 3 focuses on structured clinical management (SCM) as a treatment for borderline personality disorder (BPD). It describes the structure, pathway to assessment, process of assessment and diagnosis, crisis planning (including risk assessment, legal aspects, clinician and patient responsibilities, therapeutic alliance, substance abuse, stabilizing medication), and the treatment approach.

Gronwald, Klaus-Dieter. Integrated Business Information Systems: A Holistic View of the Linked Business Process Chain ERP-SCM-CRM-BI-Big Data. Springer, 2018.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Gronwald, Klaus-Dieter. Integrated Business Information Systems: A Holistic View of the Linked Business Process Chain ERP-SCM-CRM-BI-Big Data. Springer, 2017.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Gronwald, Klaus-Dieter. Integrated Business Information Systems: A Holistic View of the Linked Business Process Chain ERP-SCM-CRM-BI-Big Data. Springer, 2020.

Знайти повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Sepúlveda, Jovanny, ed. Enfoques multidisciplinares en Ingeniería, tecnología e innovación. CUA - Medellin, 2020. http://dx.doi.org/10.52441/ing202002.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

El propósito del presente libro es el de contribuir al desarrollo de la ciencia y la tecnología en países de América Latina desde un enfoque inclusivo y sostenible. Las investigaciones aportan elementos para la sostenibilidad, la repetitividad de la iniciativa científica, así como criterios e indicadores para la medición de resultados y futuros impactos en la aplicación de nuevas tecnologías y herramientas para mejorar procesos en la estructura gubernamental, en la sociedad y la empresa en particular. El libro ha sido estructurado en trece capítulos, uno por cada tema de investigación abordado por diferentes grupos de investigadores provenientes de universidades nacionales e internacionales. El orden en que son presentados los capítulos responde en un primer bloque al análisis de tendencias en materia de metodologías y estrategias para la innovación, en un segundo bloque se da cuenta de avances en materia de metodologías y diseño de prototipos aplicados al ecosistema empresarial desde una perspectiva ingenieril para en un tercer y último bloque de capítulos presentar aspectos asociados al impacto de las tecnologías emergentes en diferentes sectores económicos. Cada capítulo contiene componentes básicos: el título de la investigación, sus autores con datos referenciales, el resumen que incluye las palabras clave, metodología y marco referencial o teórico, resultados, conclusiones y referencias bibliográficas. En algunos de los temas investigados se aplica de manera transversal el enfoque de la innovación social, el cual es capaz de poner de acuerdo voluntades diversas para solventar, en forma comprometida, necesidades y problemas latentes en territorios específicos. Este enfoque prioriza desde el inicio, en el diseño de soluciones a necesidades o problemáticas, la transformación social basada en el aprendizaje, la originalidad y la sostenibilidad de los resultados. En temas de aprendizaje interactivo y digital se presentan los resultados de un estudio de vigilancia tecnológica de plataformas MOOC (Massive Online Open Course) y su aplicación en el aprendizaje de ciencias básicas haciendo uso de un campus virtual en el LMS, Moodle. Con relación a aportes a la industria de la construcción, se presentan los resultados de un estudio de vigilancia tecnológica en un periodo de veinte años sobre ecoinnovación en edificaciones. De igual manera se presenta la descripción de un prototipo arquitectónico de una vivienda modular sostenible, para superar el déficit de vivienda en las zonas rurales, el cual puede ser replicado en otras zonas. Complementariamente, se aportan conocimientos sobre avances para ejecutar y monitorear actividades en el ciclo de vida de un producto, tal es el caso de los modelos tridimensionales digitales que sirven como soporte y fuente de información necesaria en la organización y el aporte que representan las metodologías ágiles, como el SCRUM, aplicada en el ecosistema empresarial para lograr mayor eficiencia y efectividad en los proyectos de nuevos productos. Un tema que podría ser profundizado para impulsar procesos de innovación en nuestros países es lo relacionado con la capacidad de absorción tecnológica en las empresas, la cual se entiende como la habilidad de la empresa de reconocer, internalizar y explotar el conocimiento tecnológico externo para generar valor en forma de nuevos productos o servicios. Al respecto se presenta en uno de los capítulos, los resultados que se obtuvieron al investigar esta capacidad en el sector industrial manufacturero de Colombia. Se espera que la presente publicación sea potenciada al máximo en el avance de desarrollos y aplicaciones tecnológicas que propugnen por mejorar cada vez más la calidad de vida de las personas y la competitividad tanto del sector empresarial como gubernamental.

Частини книг з теми "SCRM process":

Schwaber, Ken. "SCRUM Development Process." In Business Object Design and Implementation, 117–34. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0947-1_11.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Bos, Koen. "Distributed Scrum Process Guide." In Collaboration in Outsourcing, 316–27. London: Palgrave Macmillan UK, 2012. http://dx.doi.org/10.1057/9780230362994_18.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

González-Moreno, Juan C., Alma Gómez-Rodríguez, Rubén Fuentes-Fernández, and David Ramos-Valcárcel. "INGENIAS-Scrum." In Handbook on Agent-Oriented Design Processes, 219–51. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-642-39975-6_8.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Wyrich, Marvin, Ivan Bogicevic, and Stefan Wagner. "Improving Communication in Scrum Teams." In Product-Focused Software Process Improvement, 602–5. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-69926-4_50.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Lepmets, Marion, and Margus Nael. "Balancing Scrum Project Management Process." In Lecture Notes in Business Information Processing, 391–92. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-13054-0_47.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Noll, John, Mohammad Abdur Razzak, Julian M. Bass, and Sarah Beecham. "A Study of the Scrum Master’s Role." In Product-Focused Software Process Improvement, 307–23. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-69926-4_22.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Visconti, Marcello, and Rodolfo Villarroel. "Managing the Improvement of SCM Process." In Product Focused Software Process Improvement, 35–48. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-36209-6_6.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Vlaanderen, Kevin, Peter van Stijn, Sjaak Brinkkemper, and Inge van de Weerd. "Growing into Agility: Process Implementation Paths for Scrum." In Product-Focused Software Process Improvement, 116–30. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-31063-8_10.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Hossain, Emam, Paul L. Bannerman, and D. Ross Jeffery. "Scrum Practices in Global Software Development: A Research Framework." In Product-Focused Software Process Improvement, 88–102. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-21843-9_9.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Scott, Ezequiel, and Dietmar Pfahl. "Exploring the Individual Project Progress of Scrum Software Developers." In Product-Focused Software Process Improvement, 341–48. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-69926-4_24.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Тези доповідей конференцій з теми "SCRM process":

Ounsrimuang, Pimolrat, and Supakit Nootyaskool. "Introducing scrum process optimization." In 2017 International Conference on Machine Learning and Cybernetics (ICMLC). IEEE, 2017. http://dx.doi.org/10.1109/icmlc.2017.8107761.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Lous, Pernille, Paolo Tell, Christian Bo Michelsen, Yvonne Dittrich, and Allan Ebdrup. "From Scrum to Agile." In ICSSP '18: International Conference on the Software and Systems Process 2018. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3202710.3203149.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Nootyaskool, Supakit, and Pimolrat Ounsrimuang. "Optimization algorithm using scrum process." In 2016 International Conference on Machine Learning and Cybernetics (ICMLC). IEEE, 2016. http://dx.doi.org/10.1109/icmlc.2016.7860908.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Rong, Guoping, Dong Shao, and He Zhang. "SCRUM-PSP: Embracing Process Agility and Discipline." In 2010 17th Asia Pacific Software Engineering Conference (APSEC). IEEE, 2010. http://dx.doi.org/10.1109/apsec.2010.44.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Pagotto, Tiago, Jose Augusto Fabri, Alexandre Lerario, and Jose Antonio Goncalves. "Scrum solo: Software process for individual development." In 2016 11th Iberian Conference on Information Systems and Technologies (CISTI). IEEE, 2016. http://dx.doi.org/10.1109/cisti.2016.7521555.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Alegria, Julio Ariel Hurtado, Maria Cecilia Bastarrica, and Alexandre Bergel. "Analyzing the Scrum Process Model with AVISPA." In 2010 XXIX International Conference of the Chilean Computer Science Society (SCCC). IEEE, 2010. http://dx.doi.org/10.1109/sccc.2010.18.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Nikitina, Natalja, Mira Kajko-Mattsson, and Magnus Strale. "From scrum to scrumban: A case study of a process transition." In 2012 International Conference on Software and System Process (ICSSP). IEEE, 2012. http://dx.doi.org/10.1109/icssp.2012.6225959.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Irfan, Danish, Xu Xiaofei, and Deng Shengchun. "Business process modeling for SCM systems." In 2008 International Conference on Emerging Technologies (ICET). IEEE, 2008. http://dx.doi.org/10.1109/icet.2008.4777510.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Estublier, Jacky, and Sergio Garcia. "Process model and awareness in SCM." In the 12th international workshop. New York, New York, USA: ACM Press, 2005. http://dx.doi.org/10.1145/1109128.1109133.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Razmochaeva, Natalya V., Viktor P. Semenov, and Artem A. Bezrukov. "Investigation of Statistical Process Control in Process Automation Tasks." In 2019 XXII International Conference on Soft Computing and Measurements (SCM). IEEE, 2019. http://dx.doi.org/10.1109/scm.2019.8903597.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Звіти організацій з теми "SCRM process":

Qi, Yan, Ryan Fries, Shambhu Saran Baral, and Pranesh Biswas. Evaluating the Costs and Benefits of Snow Fences in Illinois: Phase 2. Illinois Center for Transportation, November 2020. http://dx.doi.org/10.36501/0197-9191/20-020.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Serving as a windbreak, properly sited and designed snow fences have been proven effective in mitigating the negative impacts of blowing snow. To achieve the best snow-control effects, the ideal locations for snow fences are usually outside the roadway right-of-way. Few efforts have been made to examine the economic efficiency of snow fences and explore ways to reward private landowners. The objective of this project was to develop methodologies for evaluation of the costs and benefits of snow fences in Illinois and identify ways to encourage private landowners’ participation in the snow fence program while keeping it cost-effective. The researchers conducted a literature review as well as agency and landowner surveys. They also acquired crash data, snow fence and blowing snow segment inventory data, and blowing snow removal expenditure data as well as performed benefit-cost analyses of three types of snow fences following Federal Highway Administration guides. The survey results suggested that standing corn rows (SCRs) and structural snow fences (SSFs) were the least intrusive options for landowners and living snow fences (LSFs) with trees were the most intrusive. Some concerns related to LSFs could be reduced by allowing landowners to play a role in the design and plant-selection process. The crash data indicated that no fatal and severe crashes occurred at snow fence segments, while several fatal and severe crashes occurred at blowing snow segments during 2012–2016. The results of the benefit-cost analyses showed that the benefit-cost ratios for LSFs and SSFs are comparable. However, LSFs are favorable over SSFs because little maintenance is needed after the plants are mature. Although SCRs have the highest benefit-cost ratio, the need to renew the agency-landowner agreement annually and the alternating of crops planted may limit their snow-control effectiveness and large-scale implementation. A tool was developed using MS Excel to facilitate the benefit-cost analysis of snow fences.