Lean and Agile Assessment Workflows

The dramatic plunge in oil price will be the impetus to transform our industry again. No segment of the industry has embraced innovation more than have unconventionals. At the core of this innovation has been an approach to solving complex problems that had no known solutions before the 2000s. An opportunity now exists to further develop the way we solve problems by adopting agile work flows. Originating from software development in 2001, agile work flows will be a key part of driving the oil and gas industry to its next level of efficiency. Here are three reasons why. Accelerated Delivery of Executable Program. Developing projects that are economical in a depressed oil price environment requires multidisciplinary problem-solving in an accelerated, time-efficient manner. The traditional subsurface work flow that generates these projects experiences difficulty because typically it is designed for known problems (e.g., standard well designs) and requires many handoffs between functional groups, leading to extended project cycle times. Critically, the longer the accepted project cycle time, the less optimization can occur and the less the business can tolerate. An alternate agile approach is to perform key steps of the project as multidisciplinary sprints. These are fast-loop, multidisciplinary activities that require active involvement of the customer and decision-makers - temporary, fully dedicated, empowered teams that aim to reach completion within a defined time frame. Stability in a Time of Change. Maintaining frequent staff engagement is critical during a time when staff members are uncertain about their jobs and often are working remotely. Agile work flows that include daily check-ins or standup meetings are required to provide a regular cadence for staff members and allow for course corrections in response to a volatile market. Flexibility. A flexible, fully committed work force is never more necessary than now. Agile and sprint work flows promote flexibility, directing staff to the task of highest priority and thereby maximizing staff utility. An agile culture promotes staff members who work beyond their traditional geographical or even functional areas.

Despite of many criticisms, agile software development (Beck et al., Manifesto for Agile Software Development, http://agilemanifesto.org, [1]) philosophy has been proved to be quite successful to increase the project success rate up to a significant extent. The primary reasons behind the criticism of agile are the strong violation of the traditional disciplined software engineering theories, principles and practices. The goal of this research paper is to establish the fact that agility may also be achieved by following traditional process models especially with BRIDGE (Mandal, 2009 IEEE International Advance Computing Conference (IACC 2009) Patiala, India, [2]) process model. Hence, the aim of this paper is to integrate the agile and traditional disciplined software development process models and establish the compatibility between both the approaches. At the beginning, we have explored the objectives and principles of agile software development. Next, we briefly discussed the BRIDGE process model and further justified that--following BRIDGE process model, the philosophy of agile may also be achieved and conclude that BRIDGE model has both the capability of traditional software development process model as well as of the agile process.

We propose to introduce novel constructs for workflow modeling in the context of changing the organization of work when virtualizing organizations. We do not only develop a list of required constructs in a structured way, but also show how existing approaches could be enhanced through modeling different modes of work. We present the results of analyzing traditional workflow specification languages against the structured requirements. The proposals focus on organizing collaboration in distributed work environments, ensuring the utmost compatibility of traditional workflow modeling techniques with the enhancements.

Workflow management systems have been applied in enterprises for many years in collaborative environment to assist individuals or organizations to carry out tasks automatically and effectively. As market requirements are developing rapidly, the enterprises now find the traditional workflow management system under such rapid circumstances difficult to copy with changes in the market both promptly and flexibly. The inflexibility of traditional workflow model has cumbered the development of enterprises. Introducing SOA technology to current workflow management systems, we propose a service oriented workflow model to solve the problem mentioned above.Based on this framework, this paper also discusses how decentralized process enactment, and dynamic process adaptation can be achieved. It can improve flexibility, scalability, and interoperability and the proposed workflow management system can cooperate with other systems and enterprise applications more effectively.

Training and communication in the implementation of environmental management systems (ISO 14001): a case study at the University of Gävle, Sweden

This paper intends to contribute to efforts for standardising ECBS process and information models and ECBS architectures by exploring these ECBS constituents with respect to the design and development of heterogeneous systems like micro-systems. These highly-integrated systems are usually embedded into larger systems like cars and consist of many different mechanical or electrical elements. This diversity of system parts requires special technology in order to combine the different engineering disciplines involved during the design of such systems. Thus, a process model including the development of all system pacts and an information model able to keep descriptions of the different parts in a uniform way are necessary. They are developed in this paper. In addition to these modelling approaches the paper shows how the system architecture influences the design decisions and which tool support is required.

Machine learning is an established and frequently used technique in industry and academia, but a standard process model to improve success and efficiency of machine learning applications is still missing. Project organizations and machine learning practitioners face manifold challenges and risks when developing machine learning applications and have a need for guidance to meet business expectations. This paper therefore proposes a process model for the development of machine learning applications, covering six phases from defining the scope to maintaining the deployed machine learning application. Business and data understanding are executed simultaneously in the first phase, as both have considerable impact on the feasibility of the project. The next phases are comprised of data preparation, modeling, evaluation, and deployment. Special focus is applied to the last phase, as a model running in changing real-time environments requires close monitoring and maintenance to reduce the risk of performance degradation over time. With each task of the process, this work proposes quality assurance methodology that is suitable to address challenges in machine learning development that are identified in the form of risks. The methodology is drawn from practical experience and scientific literature, and has proven to be general and stable. The process model expands on CRISP-DM, a data mining process model that enjoys strong industry support, but fails to address machine learning specific tasks. The presented work proposes an industry- and application-neutral process model tailored for machine learning applications with a focus on technical tasks for quality assurance.

A concept is introduced in this article which has strong practical impact for computer aided system configuration. System configuration is a cumbersome and fault sensitive task while setting up systems in a broad range of business applications like ERP (enterprise resource planning) and other workflow-systems. Given a generic process or workflow model in YAWL-notation (yet another workflow language) or any other process modeling language like business process model and notation or WFMC (workflow management coalition), it could be stated that, by using a set of reduction rules as introduced, it is possible to generate a hierarchically structured tree of sub graphs of the workflow graph-representation. According to the notation used, authors call these sub graphs facts. The tree structure of the graph-representation on one hand and the logical relation between the branches and leafs of the tree on the other can be utilized to create a set of constraints and dependencies among the single facts. Some researchers showed that the nested branches can be associated to (predefined) questions with respect to the configuration of a workflow management system, for instance an ERP-application. They presented an algorithm which dynamically sorts the questions and answers in a maximum efficient configuration path, while working through the corresponding questionnaire. By combining the different elements as facts, constraints on questions, and configuration space, it is thus possible to algorithmically generate the efficient structured and interactive questionnaire for the configuration of workflow systems and algorithmically check the consistency (dead lock free, free of synchronization structural conflict) of the underlying workflow model. The concept was tested in the prototype of the interactive questionnaire for configuration of the web-service based ERP-Application

In earlier software development all process is completed and implemented but now this is not a scenario. In modern era changes are frequent to any software product or module which is under development phase, due to market competitions priority of requirement changes Due to the fact that the traditional process models are incompatible with these changes, agile methodology is used instead.. Earlier waterfall model was convenient because of less requirement of features and emergency of the application in the short period of time .This Paper Discusses the comparative Analysis of waterfall model and agile methodologies while agile methodologies are taking over, even the waterfall model is older and time consuming it is still use in many sectors The paper will help other software development process models. Agile method plays important role in the areas of software project management, software schedule management etc. The main aim of the agile is Customer satisfaction as well as faster development with low defect rate. This paper reflects the comparison of the agile processes with waterfall model software development life cycle model. Agile processes aren't always beneficial; they have their own set of downsides. Agile method promotes continuous iteration of development and testing throughout the software developed.

Supporting the deployment of ISO-based project management processes with agile metrics

Thematic Framing: Creating Healthcare Innovations1

Virtual reality (VR) refers to an artificial environment which is experienced through sensory stimuli (such as sights and sounds) provided by a computer and in which one's actions partially determine what happens in the environment (Merriam-Webster.com Dictionary, Merriam-Webster, 2020). In recent years, VR is increasingly used in different fields, and its role in medical practice is expanding quickly (Darekar et al., 2015; Chirico et al., 2016). One important feature of VR technology is its reproducibility (Ramnanan and Pound, 2017; Cao and Cerfolio, 2019). Practitioners can rehearse a procedure on a virtual patient or simulated tissue as many times as they wish before performing it on real patients. In medical education, VR allows students to see through body tissues and visualize the underneath areas (Cao and Cerfolio, 2019; Yu et al., 2019; Siyar et al., 2020). Practice experience is an essential element in pharmacy education (Teramachi et al., 2018). It is effective in boosting students' communication skills and problem-solving skills, which are both crucial for the provision of patient-centered care in a team-based approach (Lang et al., 2019). Unfortunately, actual practice experience can be limited by various factors, such as the policies at attachment sites, patients' preference, and availability of teaching staff (Wartman, 2019; Shrestha et al., 2020). Therefore, institutions are looking for alternative channels for students to practice their skills. One strategy is to adopt simulated patient cases (Kurup et al., 2017; Willemsen-Dunlap et al., 2018; Silva et al., 2019). In this paper, we share our experience of using VR learning tools in pharmacy education in a Hong Kong university. We will discuss the opportunities, challenges, and suggestions for future development of VR in pharmacy education.

Now workflow technique is almost the unique candidate to handle a business process in a software application. But graph based traditional workflow is not enough flexible in software engineer which is well known since it was introduced from manufacture industry in 1980s. Until now how to make workflow more flexible is also an unresolved problem in workflow technique which is a serious bottleneck for its popularization, although many efforts have been done to advance it. Author thinks it is wrong to design a process model based on graph theory, which is just the reason to cause workflow so inflexible. In this paper, author presents new generation process model --- Easy Flow based on task and its semantic, which is easy to understand, design, modify and refactor a business process. Easy Flow model is completely different with workflow model, which is more adept to control a changing business process in an enterprise application. Easy Flow will replace workflow to realize real business process management in future applications.

This study presents a novel low-cost workflow integrating smartphone-based photogrammetry, Building Information Modeling (BIM), infrared thermography, and real-time interactive visualization to create digital twins for comprehensive energy assessment of existing buildings. Unlike conventional approaches requiring expensive laser scanning equipment and specialized software, this methodology democratizes advanced building diagnostics through accessible technologies and academic licenses. The research aims to develop and validate a replicable workflow that enables architects, engineers, and educators to conduct detailed energy assessments without high-end equipment, while establishing technical criteria for accurate geometric reconstruction, thermal data integration, and interactive visualization. The workflow combines terrestrial photogrammetry using smartphone cameras for 3D reconstruction, BIM modeling in Autodesk Revit for semantic building representation, infrared thermography for thermal performance documentation, and Unreal Engine for immersive real-time visualization. The approach is validated through application to the historic control tower of the former Rabassa aerodrome at the University of Alicante, documenting data capture protocols, processing workflows, and integration criteria to ensure methodological replicability. Results demonstrate that functional digital twins can be generated using consumer-grade devices (high-end smartphones) and academically licensed software, achieving geometric accuracy sufficient for energy assessment purposes. The integrated platform enables systematic identification of thermal anomalies, heat loss patterns, and envelope deficiencies through intuitive three-dimensional interfaces, providing a robust foundation for evidence-based energy assessment and renovation planning. The validated workflow offers a viable, economical, and scalable solution for building energy analysis, particularly valuable in resource-constrained academic and professional contexts, advancing both scientific understanding of accessible digital twin methodologies and practical applications in building energy assessment.

Traditional business process modeling languages use an imperative style to specify all possible execution flows, leaving little flexibility to process operators. Such languages are appropriate for low-complexity, high-volume, mostly automated processes. However, they are inadequate for case management, which involves low-volume, high- complexity, knowledge-intensive work processes of today's knowledge workers. OMG's Case Management Model and Notation (CMMN), which uses a declarative style to specify constraints placed at a process execution, aims at addressing this need. To the extent that typical case management situations do include at least some measure of imperative control, it is legitimate to ask whether an analyst working exclusively in CMMN can comfortably model the range of behaviors s/he is likely to encounter. This paper aims at answering this question by trying to express the extensive collection of Workflow Patterns in CMMN. Unsurprisingly, our study shows that the workflow patterns fall into three categories: 1) the ones that are handled by CMMN basic constructs, 2) those that rely on CMMN's engine capabilities and 3) the ones that cannot be handled by current CMMN specification. A CMMN tool builder can propose patterns of the second category as companion modeling idioms, which can be translated behind the scenes into standard CMMN. The third category is problematic, however, since its support in CMMN tools will break model interoperability.