| Release Manager: | | The Release Manager is busy with at least one new release every day. | | With any service of say 1000 functions and growing, at least one function can be improved and implemted each day. | | This relentless continual improvement ensures that users are not hit with retraining as the scope of any improvement is minor and well within their capabilities of adaptation. |
| Dynamic Improvements: | | Web-based application services never need to be taken down when a new release of a component is implemented - everything is dynamic. | | People can be working with a specific data entry form and when they next use the same form, it may have gained an extra field or have some other field change. | | No computer needs to be rebooted. Nobody needs to log-off and log in again. People simply continue without any impact while improvements are delivered. |
| | | New Release: | | In the good old days, vendors would bring out a new software release and every user had to magically change from the old release to the new release at the same time. | | The whole concept of a new release was full of problems that we have siimply eliminated - we never ever have a new release. | | Day by day, little improvements are implemented with an up-front notice of changes to everybody knows what is happening. Nobody needs to be retrained, nobody needs to learn a new way of working, the cost of a new release is avoided and staff disruption has been eliminated. |
| Translation: | | Data is stored in the database in the language that the data is entered. | | Business notes and comments can be translated into another human language in a simply way that may be adequate for internal business use. Translation is not to legal quality and should not be used in external correspondance that is subject to terms and conditions. | | Management information may be generated in different languages from data stored in the database, but that information canot be translated again into another language. True round-trip translation facilities are not provided. |
| Release System: | | With one thousand functions in a typical service, a significant internal system is the management of what is being released on a day-by-day basis. | | Any change can be dynamically backed out if it proves to be defective and this demands a full understanding of component dependencies. | | Release numbers are meaning less as each component has it own unique release number and most components can only work in coorperation with other components. This level of releace control is handled internally and is totally transparent to all users. |
| Security: | | We deliver a more secure service than any in-house server system by using purpose built highly secure remote data centers in different places. | | PCI-DSS standards are manadated by FSA regulation for the storage of valuable data with a life of at least seven years. | | Data replication betwen data centers using encrypted message switching services ensure that multiple copies of all data are store within a few seconds of each transaction. Business continuity is NOT created with online tape backup, but with database mirrors on spinning disks in at least three data centers. |
|