"We are finding that as business rules are being updated from the business side, it is harder to understand the extent of the changes needed," he says.
The regulatory environment at Lonsec has been fairly stable for several years so changes to regulations has not been a driving force for automation, says Watson.
"However, the existing overhead of some regulatory requirements were minimised by the automation of some key processes, which supported the operational efficiency benefits of the automation," he says.
For County Court's Fredman, complying with regulations is not a choice, it's a requirement.
"If we cannot adjust our technology platform accordingly, we have to implement intensively manually processes until the development cycle is complete. This is ridden with risk and potential quality pitfalls," he said.
Letting go of control
Attendees agreed that there is a need for IT to let go of control over business rules and allow knowledgeable people to implement change.
Business rules exist to generate value to the organisation, and they should not be controlled by IT, says Aurecon's Ross. IT owes the business a high degree of transparency in how those business rules are applied with and across systems. This allows business process owners greater freedom to drive and own change, he says.
Progress' Swale says he's seeing a change in the market where IT people are now looking to provide staff with control and encouraging the business to manage its own process and make changes.
"This is because the BRMS tools are now available to enable the business to modify and run 'what if' testing independent of IT so this makes both parties happy. The IT department is free to concentrate on core system development and the business can implement change without being tied to the IT project schedule," Swale says.
Source: CIO Australia
Sign up for Computerworld eNewsletters.