Operators use Cockpit to inspect running and completed process instances and take care of incidents. An operator can be a technical person, like a system administrator or DevOps engineer, but it can also be someone working in a business department.
The Camunda BPM Enterprise Edition comes with an advanced version of Cockpit, that includes the following features:
In this model the Camunda process engine is started inside the application server. The process engine is provided as a container service and can be shared by all applications deployed inside the container. The concept can be compared to a JMS Message Queue which is provided by the runtime and can be used by all applications. There is a one-to-one mapping between process deployments and applications: the process engine keeps track of the process definitions deployed by an application and delegates execution to the application in question.
For IBM Websphere AS and Oracle Weblogic Server, the Camunda shared engine deployment model is only available as part of the Camunda BPM Enterprise Edition.
The Camunda Enterprise support helps you during development and in operation: During development, it will increase your productivity, as your questions about product features will be answered and your reported bugs are fixed quickly. In operation, it ensures you will immediately receive qualified assistance in case of emergency.
Your support tickets will be taken care of by the same engineers that are also the core developers of the Camunda BPM platform. Those engineers are fluent in both English and German and can provide immediate assistance, look into bug reports etcetera.
The response time for the Camunda support is usually way better than the guaranteed SLA: On average, our customers get a qualified response to their requests within 80 minutes. When necessary, we are often able to deliver a patch release to fix a reported bug at the same day we received the report.
Camunda's Net Promoter Score (NPS) as a known metric for benchmarking customer satisfaction is currently more than 75%.
We have received very positive feedback for our support from numerous organizations using Camunda for mission-critical business processes, among them AT&T, Allianz Indonesia, Deutsche Bahn, Financial Regulatory Authority (FINRA), Lufthansa Technik, T-Mobile Austria, Zalando. You can find some of their statements in the right column.
The support offered in the base editions is based on the "Standard SLA". You can choose "Advanced SLA" optionally. This only effects particularly critical incidents ("Severity Level 1 incidents"). The "Advanced SLA" option is therefore especially useful if you want to protect the most critical processes in your live operation.
|Level||Name||Description||Availability||Max. response time|
|L1||Blocker||Core components (i.e., process engine) of Camunda BPM do not work at all/produce critical errors that prevent usage in production mode.||8x5||24x7||2 hours|
|L2||Critical||Usage of Camunda BPM seriously affected, a workaround is urgently needed.||8x5||8 business hours|
|L3||Non-critical errors, Help Requests, Feature Requests.||8x5||16 business hours|
Availability: Within this time frame the ticket is worked on.
Response time: time span within which you will get a qualified answer to your inquiry. This is not an automatic reply e-mail, but the result of the examination of your request by a qualified employee.
8x5 = Monday to Friday 9am-5pm CET, except on public holidays in Berlin, Germany.
One business hour = one hour within a 8x5-availability
We currently publish a fully tested minor release of Camunda BPM every six months. Despite our extensive testing, those releases may still contain bugs that can become a critical risk if you are using Camunda BPM in production, and a hassle if you are still in development.
The solution are patch releases: These are releases we publish as soon as we have fixed any bugs that we have discovered or that have been reported to us. This will allow you to get rid of those bugs before the next minor release, so you do not have to wait for six months or more. We also backport the bugfixes to previous Camunda releases, so if you do not want to migrate from Camunda BPM 7.4 to 7.5 just because you need a bugfix, you can take the 7.4.x patch release instead.
Patch releases are only available for enterprise subscription customers, as the table below explains.
|Major||7.0||The Major release contains fundamental new features and bugfixes. It is fully tested and meant to be used for production systems. The Major release may contain incompatible API changes.|
|Minor||7.4||The Minor release contains features and bugfixes. It is fully tested and meant to be used for production systems. In Minor releases we add functionality in a backwards compatible manner.|
|Development||7.5-alpha1||We release ALPHA versions in short iteration cycles. Those development releases are previews of an upcoming minor or major release and contain the latest features and bug fixes. They are not fully tested and a snapshot of the current development state.|
|Patch||7.4.1||Whenever bugs are fixed, we perform patch releases. Patch releases do not contain new features and are meant as a further stabilization of existing major or minor releases. They are are fully tested and only available for enterprise subscription customers.|
For questions that go beyond product support, enterprise customers get exclusive access to our consulting team. Typical examples include best practice recommendations or a comprehensive review of your process models, decision tables, code or general setup. You will receive: