PA013

Higher Bot Availability vs. Lower Infrastructure Cost

Business Context. Business-critical bots are expected to run around the clock, but maintaining always-on infrastructure for every bot, including those with low or intermittent usage, drives up cost unnecessarily.

Process TRIZ Resolution. Rather than provisioning fixed always-on capacity for every bot, organizations should use elastic infrastructure that scales bot capacity up during periods of demand and down during quiet periods, reserving fixed capacity only for genuinely continuous workloads.

Applicable TRIZ Principles

Principle 37 (Thermal Expansion) allows bot infrastructure capacity to expand and contract with actual demand.

Principle 19 (Periodic Action) activates full infrastructure capacity only during periods of genuine need.

Principle 3 (Local Quality) matches infrastructure provisioning to each bot's actual usage pattern.

Expected Outcome

High availability where required

Lower overall infrastructure cost

Efficient resource utilization

Scalable capacity for peak demand

Decision Indicators

Infrastructure runs at full capacity around the clock regardless of demand.

Low-usage bots consume the same resources as high-demand ones.

Infrastructure cost has grown faster than automation volume.

No elastic scaling exists for bot infrastructure.

Capacity planning is based on peak demand applied uniformly.

If several of these indicators are present, the contradiction is likely active and the Process TRIZ resolution above should be evaluated.