下载PDF
Nikko Chemicals' Secure Cloud Migration with Data-Driven Approach
![Nikko Chemicals' Secure Cloud Migration with Data-Driven Approach - IoT ONE Case Study Nikko Chemicals' Secure Cloud Migration with Data-Driven Approach - IoT ONE Case Study](/files/casestudy/Achieves-Secure-Cloud-Migration-With-Data-Driven.png)
技术
- 平台即服务 (PaaS) - 应用开发平台
- 传感器 - 化学传感器
适用行业
- 化学品
- 药品
适用功能
- 维护
用例
- 供应链可见性(SCV)
- 篡改检测
服务
- 云规划/设计/实施服务
- 系统集成
挑战
作为负责任的企业公民,日兴化学致力于平衡环境和经济因素。作为其业务连续性战略的一个组成部分,该公司努力运行安全、可扩展、无障碍且完全可见的云操作。
- 来自不同来源的日志的耗时集成,操作可见性受限
- 云迁移和 SaaS 应用程序管理的安全问题
- 云基础设施管理的人力和资源有限
客户
日兴化学
关于客户
日本的特种化学品制造商Nikko Chemicals生产化妆品、药品、食品和可持续产品的成分。
解决方案
为确保服务完整性并保护关键业务信息,Nikko Chemicals 用 Splunk 平台替换了其旧资产管理工具,从而立即提高了整个组织的运营可见性。
自部署 Splunk® 以来,它具有:
- 具有跨多个 SaaS 应用程序的整体视图的自动化云操作
- 通过集中和主动的威胁保护最大限度地提高业务安全性
- 通过简化的操作和无痛的系统维护提高效率
运营影响
数量效益
相关案例.
![](/files/casestudy/Case-Study--Pfizer.png)
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.
![](/files/casestudy/Honeywell---Tata-Chemicals-Improves-Data-Accessibility-with-OneWireless.png)
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.
![](/files/casestudy/Advanced-Elastomer-Systems-Upgrades-Production.png)
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.
![](/files/casestudy/Fusion-Middleware-Integration-on-Cloud-for-Pharma-Major.png)
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.
![](/files/casestudy/Process-Control-System-Support.png)
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.