公司规模
Large Corporate
地区
- America
国家
- United States
产品
- Camunda BPM
- TrackWise
技术栈
- Java
- BPMN 2.0
实施规模
- Enterprise-wide Deployment
影响指标
- Productivity Improvements
- Digital Expertise
技术
- 应用基础设施与中间件 - API 集成与管理
适用行业
- 药品
适用功能
- 离散制造
- 质量保证
用例
- 过程控制与优化
- 自动化制造系统
服务
- 软件设计与工程服务
- 培训
关于客户
20 多年来,Sparta Systems 一直致力于提供企业质量管理解决方案 (EQMS),帮助客户安全高效地将产品推向市场。这些解决方案专注于优化质量、确保合规性、降低风险和降低成本,为整个企业及其关键供应商网络提供控制和透明度。Sparta Systems 总部位于新泽西州,其软件解决方案基于最佳实践设计,并配置为满足制药、医疗设备、离散制造和消费品等垂直行业的行业特定流程要求。Sparta Systems 的旗舰 EQMS 产品 TrackWise 拥有超过 750,000 名用户,该产品是生命科学领域事实上的质量管理标准,Sparta Systems 建立了质量业务网络基础,使所有生态系统利益相关者能够随时随地就质量问题进行联系和协作,以提高运营效率和整体业务成果。
挑战
Sparta Systems 是一家企业质量管理解决方案 (EQMS) 提供商,该公司正在寻找一种技术来管理其下一代基于云的产品的工作流。该公司希望通过其软件提供一个角色,使业务或合规性分析师能够创建和部署业务流程。虽然这可以在内部构建,但 Sparta 更愿意利用第三方技术来利用新特性和功能,而无需为此投入开发资源。该公司评估了几种 BPM 产品,使用的标准包括开源/OEM 友好许可证、广泛的社区采用、开放标准和对 BPMN 2.0 的本机支持、设计器/建模器工具可用性、公开的 API、可嵌入到其应用程序中或可作为服务使用、数据库支持、可扩展性和性能以及流程版本控制。
解决方案
Sparta Systems 选择 Camunda BPM 是因为它满足了他们的所有标准,并且可以轻松嵌入到他们现有的 Java 应用程序中。事实证明,Camunda 在整个过程中都是一个很好的合作伙伴,它在评估阶段提供咨询,了解 Sparta 的用例,合作成功实施,并允许 Sparta 影响他们的路线图。利用 Camunda 的技术和其他主题专家,Sparta 能够将流程执行封装到其平台代码库中的单个层中。这使得 Sparta 能够专注于开发与质量管理相关的增加业务价值的功能,同时利用 Camunda 社区多年来在 BPMN 技术上投入的资金。Sparta 还与 Camunda 开发团队密切合作,扩展了他们的基于 Web 的建模器,最终 Sparta 以定制的 BPMN 2.0 建模器的形式为开源项目做出了贡献,该建模器将专注于 Sparta 客户的特定建模需求。
运营影响
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
相关案例.
Case Study
Case Study: Pfizer
Pfizer’s high-performance computing software and systems for worldwide research and development support large-scale data analysis, research projects, clinical analytics, and modeling. Pfizer’s computing services are used across the spectrum of research and development efforts, from the deep biological understanding of disease to the design of safe, efficacious therapeutic agents.
Case Study
Fusion Middleware Integration on Cloud for Pharma Major
Customer wanted a real-time, seamless, cloud based integration between the existing on premise and cloud based application using SOA technology on Oracle Fusion Middleware Platform, a Contingent Worker Solution to collect, track, manage and report information for on-boarding, maintenance and off-boarding of contingent workers using a streamlined and Integrated business process, and streamlining of integration to the back-end systems and multiple SaaS applications.
Case Study
Process Control System Support
In many automated production facilities, changes are made to SIMATIC PCS 7 projects on a daily basis, with individual processes often optimised by multiple workers due to shift changes. Documentation is key here, as this keeps workers informed about why a change was made. Furthermore, SIMATIC PCS 7 installations are generally used in locations where documentation is required for audits and certification. The ability to track changes between two software projects is not only an invaluable aid during shift changes, but also when searching for errors or optimising a PCS 7 installation. Every change made to the system is labour-intensive and time-consuming. Moreover, there is also the risk that errors may occur. If a change is saved in the project, then the old version is lost unless a backup copy was created in advance. If no backup was created, it will no longer be possible to return to the previous state if and when programming errors occur. Each backup denotes a version used by the SIMATIC PCS 7 system to operate an installation. To correctly interpret a version, information is required on WHO changed WHAT, WHERE, WHEN and WHY: - Who created the version/who is responsible for the version? - Who released the version? - What was changed in the version i.e. in which block or module of the SIMATIC PCS 7 installation were the changes made? - When was the version created? Is this the latest version or is there a more recent version? - Why were the changes made to the version? If they are part of a regular maintenance cycle, then is the aim to fix an error or to improve production processes? - Is this particular version also the version currently being used in production? The fact that SIMATIC PCS 7 projects use extremely large quantities of data complicates the situation even further, and it can take a long time to load and save information as a result. Without a sustainable strategy for operating a SIMATIC PCS 7 installation, searching for the right software version can become extremely time-consuming and the installation may run inefficiently as a result.
Case Study
ELI LILLY ADOPTS MICROMEDIA’S ALERT NOTIFICATION SYSTEM
Pharmaceutical production is subject to a strict set of enforced rules that must be adhered to and compliance to these standards is critically necessary. Due to the efforts of WIN 911’s strategic partner Micromedia, Lilly was able to adopt an alarm notification infrastructure that integrated smoothly with their existing workflows and emergency hardware and protocols. These raw energy sources enable the industrial process to function: electricity, WIN-911 Software | 4020 South Industrial Drive, Suite 120 | Austin, TX 78744 USA industrial steam, iced water, air mixtures of varying quality. Refrigeration towers, boilers and wastewater are monitored by ALERT. Eli Lilly identified 15000 potential variables, but limitations compelled them to chisel the variable list down to 300. This allowed all major alarms to be covered including pressure, discharge, quantity of waste water discharged,temperature, carbon dioxide content, oxygen & sulphur content, and the water’s pH.