Why a structured process analysis
Most large Broadcom Automic Automation landscapes are historically grown. They started small, were extended year after year, absorbed new applications, teams and platforms — and nobody has ever taken a structured look at the whole picture. Schedules were duplicated, time triggers were added “just in case”, jobs were re-run manually when things went wrong, old objects were abandoned rather than deleted. Every individual decision made sense at the time; together they have accumulated into operational debt that nobody has a complete view of. In most environments, nobody knows exactly how many JOBS and JOBF executions run per month, which parent workflows account for the bulk of them, or how many are manually started.
The Automic Process Analysis & Optimisation package is Tricise’s answer to exactly that situation. It is a structured, expert-led engagement that measures how the system actually runs, surfaces the inefficiencies that have accumulated, and hands back a prioritised action plan your team can work through at its own pace. The method has been refined across many Automic customer engagements and uses Tricise’s own SQL-based analysis tooling. A clear picture of your current execution footprint is also the foundation for informed planning around performance, sizing, agent consolidation and budgeting — including around Broadcom’s Execution-Based Licensing model.
The 5-phase method
The Automic Process Analysis & Optimisation engagement is delivered in five clearly separated phases. The first three phases — Determine, Collect, Analyse — make up the fixed-price package and always happen. The fourth and fifth phases — Implement and Review — are optional follow-up work that customers often book separately on time & material, once they have decided which of the recommendations they want to pursue.
The first phase captures the current state of the Automic environment. Before any analysis can produce meaningful numbers, telemetry must be enabled on the system and a reliable baseline of activity has to be established. We capture the as-is state with the standard Broadcom tooling available in Automic, count the number of monthly JOBS and JOBF executions, and review the trend over the last few months to distinguish stable patterns from seasonal spikes.
This phase is quick — it exists to confirm that data is available, to align on what “the Automic system” actually covers (single client or multiple, which agents, which connected applications), and to set the reference points the later analysis will compare against.
Once the baseline is clear, Tricise provides its analysis tooling: an Action Pack containing SQL scripts adapted to your specific Automic database backend (PostgreSQL, Oracle or SQL Server). The scripts are reviewed jointly with your team in a short alignment session — not all environments are identical, and there is often one or two customer-specific adjustments to make before running them.
After the alignment, the scripts are executed against the Automic repository and the collected data is delivered back to Tricise Professional Services for analysis. The execution is low-impact and read-only; nothing in the Automic system is modified during data collection.
The heart of the engagement is a joint analysis workshop. Tricise experts work through the collected data, apply the evaluation catalogue described in the next section, and present the findings to your team in a structured session. The workshop is interactive — not a slide show. We discuss the results together, clarify context only your team knows (which objects belong to which business process, why a given schedule exists, which workflows are critical and which are legacy), and jointly define where the starting points and priorities for optimisation lie.
The phase ends with a concrete set of prioritised recommendations for process optimisation — organised by number of affected executions, implementation effort, and expected operational impact.
Phases 4 and 5 are optional follow-up work, billed on time & material rather than the fixed price. They are a common but separate engagement that some customers book immediately after the analysis, others delay, and others handle entirely with their own team. In Phase 4, the Automic processes are adjusted according to the priorities agreed during the workshop — consolidating schedules, removing redundant triggers, automating manual interventions, cleaning up orphaned objects, and everything else that came out of the recommendations.
When Tricise delivers this phase, our consultants work alongside your operations team and document every change. You can also take the recommendations and implement them internally — the fixed-price package gives you a complete, actionable plan that doesn’t depend on additional Tricise involvement.
After implementation, the analysis scripts are re-run to measure the delta between before and after. Did the removal of redundant triggers reduce the monthly execution count by the expected amount? Did the schedule consolidation smooth the peak load? Are the workflows that used to drive the bulk of runs still behaving the same way? The review phase turns the optimisation work into measurable results and can be repeated periodically to stay ahead of drift.
Many customers book a review phase 2–3 months after implementation, as a short T&M engagement, to validate the effect before the next operational planning cycle.
What we analyse
The Automic Process Analysis & Optimisation catalogue is the result of many years of Automic consulting experience and covers more than 30 structured checks. The categories below describe the types of evaluation performed during the workshop — each one surfaces a different class of inefficiency and together they give a complete picture of how the system is actually running. The exact metrics, queries and thresholds are part of Tricise’s consulting method and are applied by the consultant during the engagement; what you see here is what the findings look like, not how they are computed.
What you receive
At the end of the fixed-price engagement, the Automic Process Analysis & Optimisation package leaves you with a complete set of written and structured outputs that your team can work from on its own, without further Tricise involvement. Every deliverable below is part of the fixed price — the Automic Process Analysis & Optimisation package has no hidden extras and no per-hour billing inside the agreed scope.
Detailed analysis report
A comprehensive written document containing all findings from the engagement, organised by evaluation category and with each finding described, quantified and contextualised. The report is designed to be readable by both the operations team and management — the top section is a structured executive summary, the body carries the detail.
Prioritised recommendations
Every finding comes with a concrete recommendation: what to change, how much effort it represents (small / medium / large), and what the expected operational impact is. Recommendations are ranked by the combination of impact and effort, so your team has a clear top-down list to work through rather than a flat bag of suggestions.
Execution footprint baseline
A structured view of the monthly JOBS and JOBF activity, including the trend over recent months and the breakdown across parent workflows, platforms, agents and clients. This baseline is useful far beyond the immediate analysis — it supports sizing conversations, agent consolidation planning, and informed budgeting across all operational fronts.
Analysis workshop session
The joint workshop in Phase 3 is itself a deliverable. It is where your team sees the results first-hand, asks questions, challenges findings, and adds the context only you can provide. The outputs of the workshop (decisions made, priorities set, items deferred) are captured and fed back into the final report.
Raw analysis data export
A structured export of the metrics collected from your Automic repository, handed over as part of the engagement. You keep this data for your own records, for re-use during internal reviews, and as a reference point for future comparisons after optimisation work has been done.
Optional implementation & review support
Tricise can support the implementation and review phases as a separate follow-up engagement on time & material. This is not part of the fixed price and is scoped individually based on the findings from Phase 3.
Technical scope & what we need from you
The Automic Process Analysis & Optimisation package is deliberately light on customer prerequisites — we do not expect your team to prepare data, run scripts, or assemble reports. What we need is access, participation in the joint sessions, and the contextual knowledge that only your operations team has. The Automic Process Analysis & Optimisation engagement is designed so the customer-side effort stays under a single day of total involvement across the full 3–4 week timeline.
What is in scope
- One Automic system — a single Automic Automation Engine system, which may include multiple clients if they share the same repository
- One analysis cycle — data collection, analysis and workshop, covering the current state plus the recent trend
- Report, recommendations, data export and workshop — the complete deliverable set described above
What your team needs to provide
- Automic telemetry enabled — the standard activity data needs to be available in the repository before Phase 2 can start
- Read access to the Automic repository — for executing the Tricise analysis scripts (PostgreSQL, Oracle or SQL Server, depending on your backend)
- Participants for the joint sessions — typically one or two Automic administrators and a person who understands the business processes the workflows support
- 2–3 hours for the alignment session in Phase 2 to review the scripts before execution
- Half a day for the analysis workshop in Phase 3
Delivery mode
The engagement is delivered remotely by default, which keeps costs predictable and enables fast scheduling. On-site delivery is available on request; travel expenses are then charged in addition to the fixed price, at actual cost. Most customers find the remote format works well because the workshop is the only truly interactive phase and video conferencing handles that format without friction.
Out of scope
- Implementation of the recommendations (optional Phase 4, separate T&M engagement)
- Post-implementation review (optional Phase 5, separate T&M engagement)
- Analysis of systems other than the one contracted in this engagement
- Broadcom licensing negotiations — we provide the execution footprint baseline, but the licensing conversation is between you and Broadcom
Frequently asked questions
Click any question to expand the answer.
What is the Automic Process Analysis & Optimisation package and what does it do?
The Automic Process Analysis & Optimisation package is a fixed-price consulting engagement by Tricise that reviews how your Automic Automation environment actually runs. Broadcom-certified experts collect data from your Automic repository, apply more than 30 structured checks across 8 evaluation categories, and deliver a written report with prioritised recommendations — all within a fixed scope and a fixed price. The package is designed for customers who want a clear, outside-in view of their Automic landscape’s execution footprint, efficiency patterns, and optimisation potential, without committing to an open-ended consulting engagement upfront.
How much does the Automic Process Analysis & Optimisation cost?
The Automic Process Analysis & Optimisation package is offered at a fixed price of 5.000 € (excl. VAT) per Automic system. This fixed price covers the complete engagement described in Phases 1–3: data collection, analysis, the joint workshop, the written report, the prioritised recommendations and the raw analysis data export. If the session is delivered on-site at your request, travel expenses are charged in addition at actual cost. The optional Phases 4 and 5 (implementation and review) are billed separately on time & material.
How long does the engagement take?
The Automic Process Analysis & Optimisation package has a fixed scope rather than a fixed day count, because the calendar time depends on how quickly your team can enable telemetry, align on the scripts and join the workshop. In practice, most engagements run from initial scoping to delivered report within 3–4 weeks. The customer-side effort is very light — typically half a day for the workshop plus 2–3 hours for the scripts alignment, spread across the engagement period.
Which Automic versions and database backends are supported?
The Automic Process Analysis & Optimisation package supports current Automic Automation Engine versions running on any of the three common repository databases: PostgreSQL, Oracle and Microsoft SQL Server. Tricise maintains analysis scripts for each of the three backends and adapts the set used during the engagement to match your specific database type and Automic version. If your landscape uses a different backend or a very old Automic version, let us know during scoping — we will tell you directly whether the standard engagement fits or whether adjustments are needed.
What do I need to prepare before the engagement starts?
The main preparation on your side is making sure Automic telemetry is enabled and the standard activity data is available in the repository. You will also need to provide read access to the Automic database for the Tricise consultant and nominate one or two participants who know both the Automic landscape and the business processes it supports. No data pre-processing, no report pre-assembly, no internal spreadsheets — the engagement is designed so that preparation effort on your side stays under half a day.
Is the data collection intrusive? Does it affect production?
No. The data collection in Phase 2 of the Automic Process Analysis & Optimisation engagement is entirely read-only — the Tricise analysis scripts query the Automic repository but never modify it. There is no code deployed into the Automic Automation Engine, no agents installed, no changes to your workflows, no risk to running jobs. The scripts are reviewed jointly with your team before execution, so you see exactly what they do before they touch your database. The impact on the database is comparable to a reporting query.
How does this differ from a Tricise System Health Check?
The System Health Check is an architecture and configuration review — it looks at how the Automic Automation Engine itself is set up (database parameters, work processes, server routines, AWI configuration, REORG frequency, etc.) and verifies that the platform is healthy. The Automic Process Analysis & Optimisation package is a workload review — it looks at what the system is actually executing, in what volume, at what frequency, and with what efficiency. The two are complementary: Health Check asks “is the platform healthy?”, Automic Process Analysis & Optimisation asks “are we running it efficiently?”. Customers often book both, in either order, depending on which question is more pressing.
Will you tell me exactly which jobs to delete or consolidate?
Yes — the final report contains specific recommendations at the level of individual objects where the findings support that level of precision. For the Top-X execution analysis and the orphaned-object detection in particular, the report names the affected objects and describes the recommended action. For more strategic findings (schedule restructuring, workflow consolidation, platform rebalancing) the recommendations are at the pattern level, because the actual decision depends on business context only your team has. Either way, the report gives you actionable steps — not just observations.
Do we keep the Tricise analysis scripts after the engagement?
The SQL-based analysis scripts are Tricise’s consulting tooling and remain with Tricise — they are the instrument we use to perform the engagement, not a deliverable. What you receive and keep is the raw analysis data collected from your Automic repository, along with the complete report and all findings. If you want a tool that you can run yourself on an ongoing basis, that’s a different conversation — typically either the Automation CLI Action Pack or a separate custom engagement.
What does the optional implementation phase look like?
Phases 4 and 5 of the Automic Process Analysis & Optimisation engagement — implementation and review — are optional follow-up engagements billed on time & material rather than fixed price. In Phase 4, Tricise consultants work alongside your operations team to apply the recommendations from the analysis: consolidating schedules, removing redundant triggers, automating manual interventions, cleaning up orphaned objects, and so on. In Phase 5, the analysis is re-run to measure the concrete impact of the changes. The scope and effort depend entirely on how many findings you decide to act on and how deep each change goes, which is why we refuse to price them upfront — we scope them properly once Phase 3 is complete and you have the full picture.
Can we implement the recommendations ourselves without booking Tricise for Phase 4?
Absolutely. The fixed-price Phases 1–3 are designed to leave you with a complete, actionable plan that your own team can execute. Many customers take the report, internalise the recommendations, and work through them with their own operations and application teams over several months. The optional Phase 4 support exists for customers who prefer to accelerate the rollout or who want an external perspective during the changes — it is not a requirement for getting value out of the engagement.
How is the result useful beyond operational optimisation?
The execution footprint baseline and the evaluation data from an Automic Process Analysis & Optimisation engagement are useful in several conversations beyond day-to-day operations: sizing and capacity planning, agent and platform consolidation decisions, application decommissioning, and informed planning around Broadcom’s Execution-Based Licensing model. In each of these conversations, having the numbers for your current state — broken down in the way the analysis produces them — turns what would otherwise be educated guessing into a data-backed discussion.