公司规模
Large Corporate
地区
- America
国家
- United States
产品
- Camunda BPM
技术栈
- Java
- Spring Boot
- REST
实施规模
- Enterprise-wide Deployment
影响指标
- Productivity Improvements
- Innovation Output
技术
- 平台即服务 (PaaS) - 应用开发平台
适用行业
- 生命科学
- 药品
- 化学品
适用功能
- 产品研发
- 质量保证
用例
- 质量预测分析
- 过程控制与优化
服务
- 软件设计与工程服务
关于客户
Zymergen 是一家总部位于美国的分子技术公司,利用生物学技术创造和改进产品。该公司与农业、制药、化学品、材料、电子和个人护理等行业的公司合作,以改善现有分子的经济效益,并利用工程微生物开发新产品。Zymergen 的制造团队对细菌和酵母等微生物进行工程设计和测试,以提高大规模发酵过程中的性能。这些方法最终有助于微生物更有效地将原料(如糖)转化为目标分子。
挑战
Zymergen 是一家分子技术公司,在加快新项目启动流程的同时保持流程效率和可定制性方面面临着挑战。随着客户数量的增加,该公司需要减少启动新项目所需的时间,同时仍要保证流程的高效性和可定制性。这需要一个可以与其自动化和数字系统集成的解决方案,同时为科学家和其他非程序员提供灵活的界面来创建、更新和执行这些复杂的工作流程。
解决方案
Zymergen 决定实施 Camunda BPM,这是一种灵活且可扩展的工作流自动化解决方案。该公司使用 Camunda 的 Spring Boot 集成来实施项目,并主要使用 Java 与其生态系统中的不同软件和自动化服务进行交互。Spring 和 Camunda 的结合使 Zymergen 能够轻松利用 REST 或发布/订阅等技术来协调和编排其系统。利用这些技术,Zymergen 软件团队开发了一个与数据和自动化系统交互的调用活动库,科学家使用它来组装具有生物学意义的工作流。
运营影响
数量效益
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
Honeywell - Tata Chemicals Improves Data Accessibility with OneWireless
Tata was facing data accessibility challenges in the cement plant control room tapping signals from remote process control areas and other distant locations, including the gas scrubber. Tata needed a wireless solution to extend its control network securely to remote locations that would also provide seamless communication with existing control applications.
Case Study
Advanced Elastomer Systems Upgrades Production
In order to maintain its share of the international market for thermoplastic elastomers AES recently expanded its Florida plant by adding a new production line. While the existing lines were operating satisfactorily using a PROVOX distributed control system with traditional analog I/O, AES wanted advanced technology on the new line for greater economy, efficiency, and reliability. AES officials were anxious to get this line into production to meet incoming orders, but two hurricanes slowed construction.
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.