- 1. Intro
- 2. AltanaESP Network (man) & System (machine) Symbiosis
- 3. Building Blocks & Foundation
- 4. Finances & Costs
- 5. Dependability & Trustworthiness
- 6. Reliability & Accuracy
- 7. Operational & Functional Requirements
Operational & Functional Requirements
We live in a society and deal with a rapid changing environment. Thus, it often happens that a function should be developed or changed within a matter of hours to have any real useful effect.
[wptabs style=”wpui-sevin” mode=”horizontal” background=”true”] [wptabtitle]Open Source Software[/wptabtitle] [wptabcontent]A system can be kept up and running with the minimum of down time. Normally most issues can be dealt with within 24 hours as a rule, NOT the exception. Regardless the complexity of the issue.[/wptabcontent] [wptabtitle]Copyright Software[/wptabtitle] [wptabcontent]The rule is – when things goes exceptionally well – changes can be implemented in about 6 to 18 months time. This is the rule, on rare occasions, implementation might happen in a months time.[/wptabcontent] [wptabtitle] AltanaESP System Requirement[/wptabtitle] [wptabcontent]Things change and more so when attempting to accommodate individualization, customization and context. No real use and purpose for committees, research programs and plenty of bureaucracy to get thing on the road. Just put in a request, verify authenticity and get things done.[/wptabcontent] [/wptabs]
Thus, the main reason why AltanaESP Pty Ltd selected the open source route and strategy, is due to the code versatility and the ability to adapt and tweak the code to efficiently and productively meet the individualization, customization and contextualization requirements of a Self-organizing Network of Services.