Rules Engine and Workflow Capability Market Assessment

This Tender is invited by the Issuer. Overview The Department of Employment and Workplace Relations is exploring market options for managing complex business rules, decision logic and workflow orchestration across digital services. About The department has undertaken initial analysis of the challenges associated with complex and distributed decision logic. This work indicates a need to improve the way business concepts, rule categories, decision dependencies and workflow pathways are described, governed and implemented. Initial requirements have been developed for centralised rules management, configurable decision services, workflow orchestration, human review, traceability, testing, versioning and monitoring. A representative set of complex rules and decision scenarios can be used to assess market offerings without requiring access to live systems or personal information. The department has also identified the importance of maintaining a clear relationship between source requirements, business terminology, decision models, executable rules and workflow behaviour. Market information is now required to understand how available solutions address this lifecycle, how they integrate with a modern cloud environment, and what implementation, licensing, operational and skills implications should be considered. Purpose Current approaches distribute decision logic across application code, APIs, data structures, user interfaces and manual procedures. This makes rules difficult to discover, interpret, test and change, and can create inconsistent implementation of related concepts, decision categories and rule taxonomies across services. The department is seeking information on solutions that can provide a central, configurable and traceable way to define, organise, execute and govern complex decision logic. The capability should support clear separation between business rules, workflow and application code, while enabling decision services to be consumed through well-defined interfaces. Objectives The outcome will be a clearer view of available products and delivery approaches, how they align with the department's technology and security environment, and the relative effort, cost and constraints associated with adopting and operating the capability. Scope The scope of the market exploration includes: Consideration of the full rules lifecycle, including rule discovery and classification, decision modelling, execution, testing, versioning, approval, deployment, monitoring and retirement Consideration of workflow orchestration, including automated processing, evidence capture, exception handling, escalation and human review Understanding how available solutions can be evaluated in a representative trial environment before any broader investment decision is made, including practical options for establishing and supporting a time-boxed trial, the extent to which the trial can test representative rules, workflows, integrations, performance and scaling limits, and whether resulting artefacts can be reused in a future implementation Providing visibility of the pathway from trial to full-scale rollout, including the likely licensing model, key cost drivers, implementation requirements and how commercial arrangements change as transaction volumes, users, environments, workflow instances and processing capacity increase Users and Their Needs Primary users of the capability may include policy and program owners, business analysts, operational staff, decision and rules designers, workflow administrators, assurance teams, technology delivery teams and service support staff. Business users need to describe and organise complex concepts, rule types, decision points and relationships using a consistent taxonomy. They need to inspect how requirements have been translated into executable logic, understand the impact of proposed changes and participate in controlled authoring, review and approval processes. Operational users need consistent system-supported outcomes, clear work queues, evidence requirements, exception pathways, escalation and review points. The capability should support both automated decision making and human-in-the-loop activity where judgement, validation or approval is required. Technology users need reusable decision and workflow services, well-defined APIs, automated testing, version control, environment promotion, observability and integration with existing and future digital services. Assurance users need a complete decision history, including the rule and workflow version applied, inputs used, intermediate decisions, human interventions, outcome and rationale. They should be able to reconstruct or replay decisions where appropriate. The capability should support changes to rules, thresholds, classifications, pathways and review settings without requiring those elements to be embedded repeatedly in consuming applications. Contractor Requirements Technical and Business Constraints A cloud-native solution is preferred Solutions should align with contemporary container, orchestration, identity, monitoring and automated deployment practices where applicable Departmental data must be retained and processed onshore in Australia The capability must support secure integration through documented APIs and standard authentication and authorisation mechanisms, and should provide granular access control, separation of duties, audit logging, encryption, environment segregation and controlled promotion of rules and workflows The department expects to begin with synthetic or non-personal information in a lower environment; any later use of production information or integration with live services would be subject to separate procurement, security, privacy, architecture and operational approvals Information Requested Respondents should include the following in their response: Supported deployment models, including software-as-a-service, managed cloud and deployment within a department-controlled cloud environment The location of data storage, processing, backups, logs, telemetry and support access, including any circumstances in which data or metadata may leave Australia Support for recognised standards and frameworks for decision modelling and workflow orchestration, including DMN and BPMN where applicable How rules, decision models, workflow definitions, test assets, execution history and configuration can be exported, imported and managed using commonly supported formats and development practices A practical approach for establishing and supporting a representative trial environment, including setup requirements, costs, lead times and support arrangements Any functional, technical, performance, integration or scale limitations that may affect how reliably the trial represents the production solution Instructions to Tenderers Respondents may be invited to a structured clarification session, product demonstration or technical walkthrough after written responses are assessed. Any follow-up would be used to understand the product's capabilities and delivery approach and would not constitute a commitment to procure.