TIBCO Business Studio™ is a standards-based, unified business process modeling environment that enables business analysts and IT to model, design, and implement business process applications for TIBCO ActiveMatrix® BPM.
There are two views of TIBCO Business Studio, TIBCO Business Studio for Analysts and TIBCO Business Studio for Designers. TIBCO Business Studio for Analysts is a business friendly non-technical version of the design environment. The complexity of the technical implementation details is hidden for business users.
Business Studio™ for Analysts
TIBCO Business Studio for Designers is a full-featured design-time environment for process applications for TIBCO ActiveMatrix® BPM. You are able to model three distinct types of business processes, organizational models, business object models (data definitions), user forms, and rules in TIBCO Business Studio.
TIBCO Business Studio™ for Designers
TIBCO Business Studio also provides process simulation functionality. Simulations can be run based on real data to validate as-is and to-be processes, identify bottlenecks and inefficiencies, run comparative cost or time analyses, or highlight underutilized resources. Built-in reporting enables users to generate comparative, cost, and time-based reports to assess the business impact of their proposed changes.
Common business process patterns are built into TIBCO Business Studio and ActiveMatrix BPM. You can apply these patterns without any code. This capability speeds process design and improves process visibility and business operations. The most common process pattern is "Separation of Duties," also known as Maker-Checker or 4-eyes. If a person performs task A, they cannot perform task B. For example, when you submit an expense report you cannot be the approver of that report.
Another common process pattern is "Chaining", in which work will continually be presented to the same user until the chain is broken. As soon as they finish one screen the next screen appears. Chains can break due to the user not having the authority, role, skills, or authorization to complete the work. System tasks can be executed in the middle of a chain without breaking the chain.
In our human-only scenario above, when the user finishes task A, he is immediately presented with task B. When he finishes task B he is immediately presented with task C.
In the human- and system-task Chaining scenario, when a user finishes task A, a web service is called to collect more information, then task C is immediately presented to the user. This presents a seamless interface and streamlines work efficiency.
The subject of intense research for many years, there are many more process patterns, all of which can be applied without a single line of code. Learn more about process patterns.