Collaboration and Engagement Throughout The Supply Chain : The Role of Government

Collaboration is acknowledged as a key to continued growth in the Australian construction industry. Government, as a major industry client, has an important role to play with respect to fostering collaboration and ensuring the global competitiveness of the industry. The paper draws upon data collected for the Construction 2020 study and aims to demonstrate that government can a) help to break down the adversarial situation that currently exists between clients, project managers and subcontractors; and b) allow the supply chain to collaborate more effectively in terms of satisfying the relational and financial needs of all parties. Government can also provide a clear set of guidelines (backed up by a functional dispute resolution system) that will promote confidence with respect to forging relationships. Thus, the paper will discuss the way in which public policy can be more closely aligned with actual industry needs in order to promote greater collaboration.

Controlled flexibility and lifecycle management of business processes through extensibility

Vendors provide reference process models as consolidated, off-the-shelf solutions to capture best practices in a given industry domain. Customers can then adapt these models to suit their specific requirements. Traditional process flexibility approaches facilitate this operation, but do not fully address it as they do not sufficiently take controlled change guided by vendors' reference models into account. This tension between the customer's freedom of adapting reference models, and the ability to incorporate with relatively low effort vendor-initiated reference model changes, thus needs to be carefully balanced. This paper introduces process extensibility as a new paradigm for customizing reference processes and managing their evolution over time. Process extensibility mandates a clear recognition of the different responsibilities and interests of reference model vendors and consumers, and is concerned with keeping the effort of customer-side reference model adaptations low while allowing sufficient room for model change.

The Order Fulfillment Process Model

This appendix describes the Order Fulfillment process followed by a fictitious company named Genko Oil. The process is freely inspired by the VICS (Voluntary Inter-industry Commerce Solutions) reference model1 and provides a demonstration of YAWL’s capabilities in modelling complex control-flow, data and resourcing requirements.

Process configuration in YAWL

This chapter describes how the YAWL meta-model was extended to support the definition of variation points. These variation points can be used to describe different variants of a YAWL process model in a unified, configurable model. The model can then be configured to suit the needs of specific settings, e.g. for a new organization of project.

The YAWL Architecture

The YAWL system is structured as a service-oriented architecture. It is composed of an extensible set of YAWL Services [1], each of which is deployed at a certain endpoint and offers one or multiple interfaces. Some of these services are userfacing, meaning that they offer interfaces to end users, while others offer interfaces to applications or other services.

YAWL : power through patterns

Workflow Management Systems (WfMSs) enable the development and maintenance of workflow specifications at design time and their execution and monitoring at runtime. The open source WfMS YAWL supports the YAWL language – a formally defined language based on Petri nets which offers comprehensive support for control-flow and resource patterns. In addition, the YAWL system provides extensive support for process flexibility, in particular for process configuration, exception handling, dynamic workflow and declarative workflow. Due to its formal foundation, sophisticated verification support can also be achieved. This paper presents the YAWL system and its main applications.

Preliminary review of over-regulation in Australian financial services

This article examines a preliminary review and the limited evidence of over-regulation in Australian financial services. The 1997 Wallis Report and the CLERP 6 paper resulted in the amendments to Ch 7 of the Corporations Act 2001 (Cth) by the Financial Services Reform Act. Nearly a decade later the system based upon 'one-size fits all' dual track regime and a consistent licensing regime has greatly increased the costs of compliance. In the area of enforcement there has not been a dramatic change to the effective techniques applied by ASIC over other agencies such as APRA. In particular there are clear economic arguments, as well as international experiences which state that a single financial services regulator is more effective than the multi-layered approach adopted in Australia. Finally, in the superannuation area of financial services, which is worth A$800 billion there is unnecessary dual licensing and duplicated regulation with little evidence of any consumer-member benefit but at a much greater cost

Business process extensibility

Vendors provide reference process models as consolidated, off-the-shelf solutions to capture best practices in a given industry domain. Customers can then adapt these models to suit their specific requirements. Traditional process flexibility approaches facilitate this operation, but do not fully address it as they do not sufficiently take controlled change guided by vendors’ reference models into account. This tension between the customer’s freedom of adapting reference models, and the ability to incorporate with relatively low effort vendor-initiated reference model changes, thus needs to be carefully balanced. This paper introduces process extensibility as a new paradigm for customising reference processes and managing their evolution over time. Process extensibility mandates a clear recognition of the different responsibilities and interests of reference model vendors and consumers, and is concerned with keeping the effort of customer-side reference model adaptations low while allowing sufficient room for model change.

Aboriginal community control and decolonizing health policy : a yarn from Australia

This chapter outlines: a brief history of Australian Aboriginal health and health policy and then moves on to demonstrate how the Victorian Aboriginal Community Controlled Health Organisation (VACCHO) undertakes its work and is an example of 'decolonizing policy in action'. Moreover, it highlights how Aboriginal participation in the development of policy and in the planning, delivery, management and evaluation of health programs enables policies and programs to respond effectively to the needs of Aboriginal people and to change future health outcomes for them. It showcases how Aboriginal decision-making has gone some way to decolonizing policymaking and has addressed the power imbalance - both of which have been critical in the improvement in Aboriginal health outcomes.

The design environment

This chapter provides an overview of the Editor, which is the core modeling component of the YAWL system. Specifically, it shows how to specify control-flow, data and resourcing requirements in a YAWL workflow model. Moreover, it describes the error reporting capabilities of the Editor and the features of its interchange format.

Open source software for workflow management : the case of YAWL

"This column is distinguished from previous Impact columns in that it concerns the development tightrope between research and commercial take-up and the role of the LGPL in an open source workflow toolkit produced in a University environment. Many ubiquitous systems have followed this route, (Apache, BSD Unix, ...), and the lessons this Service Oriented Architecture produces cast yet more light on how software diffuses out to impact us all." Michiel van Genuchten and Les Hatton Workflow management systems support the design, execution and analysis of business processes. A workflow management system needs to guarantee that work is conducted at the right time, by the right person or software application, through the execution of a workflow process model. Traditionally, there has been a lack of broad support for a workflow modeling standard. Standardization efforts proposed by the Workflow Management Coalition in the late nineties suffered from limited support for routing constructs. In fact, as later demonstrated by the Workflow Patterns Initiative (www.workflowpatterns.com), a much wider range of constructs is required when modeling realistic workflows in practice. YAWL (Yet Another Workflow Language) is a workflow language that was developed to show that comprehensive support for the workflow patterns is achievable. Soon after its inception in 2002, a prototype system was built to demonstrate that it was possible to have a system support such a complex language. From that initial prototype, YAWL has grown into a fully-fledged, open source workflow management system and support environment