![]() | Rules for good corporate governance spread rapidly around the world. To name a few : ISO20000, ITIL/ITSM, ..., SOX, MIFID (Banks-EUR), Basel II , Turnbull, Solvency II (Insurance-EUR), ... |
Permanently check !
![]() | ![]() | ![]() |
- are correctly and fully carried out
- are best executed in a minimum of time (Best Execution principle)
Finally, from a commercial point of view, one must recognize that final customers are less and less bound to their suppliers. They change more frequently of supplier even for very tiny details. Therefore IT applications must reach high standards of quality / availability / security / ease of maintenance and evolution.
This is what ASK calls : good operational Corporate Governance.
ASK tries to introduce policies reflecting an organizations logical progression from working in an ad-hoc manner to one where people are following common and consistent processes. A policy reflects your organization's desire for everyone to perform a specific function in a specific way. Policies help everyone understand how to do things, and they help managers understand the framework in which they can manage.
Indicates in (almost) real time what's going on with all your Business Processes. Thanks to the SOA architecture, anyone is able to map IT processes with real business processes.

Like in the past with "record keeping books" where one could be sure that every incoming event (documents / claims / contracts ...reception) was recorded chronologically, this is the contemporary electronic version, where we can track the flow of documents to be handled by your back office without loosing a single one.
Document standard and/or custom properties may be added at several stages. We update/complete the archives at each step...

As SOA rules imply (from a technical point of view) to develop the most independant software components from each others, each one having (in theory) no knowledge of any other component running concurrently, some 'glue' is mandatory required as your organisation is not made of 'independant components'. It's even the other way round : your organisation is a 'semantically' tight logical suite of tasks to be carried out !
The 'semantic' of your Business Processes is under control of our BusinessProcessWatchers. They are of course customised along your specific organisation.
Like in industrial contexts (manufacturing floor), we provide graphical indicators and gauges to show the continous workload of your Business Processes in (almost) real time. Warnings & Alerts can be sent immediately like in a brick-and-mortar factory to warn Supervisors that something went wrong along your own norms and standards.
One thing you will observe about policies is that they are created and approved by the people or group that owns the process. Because of this, you hope that the policy reflects the best practices of the group that is most experienced in the area and most impacted by the outcome. The IT policy then can align everyone under these best practices.
Most of us recognize the value of reuse. It makes more sense to reuse things that are already developed instead of having to re-invent everything we do from scratch. This is true with work processes and policies as well. For instance, you could certainly come up with a framework for handling IT security on your project.
Having common policies saves you the time to having to invent and gain approval on these for each individual project or group. It also saves time for new people in the company as they learn how things work in your world.
As companies get bigger, they need to establish policies so that people have guidance on how to do things. Since policies are established and approved by the subject-matter experts, ASK cares that everyone is doing things in ways that protect the company and make sense.