下载PDF
Assuring Work-from-Anywhere User Experience With Smart Edge Monitoring
技术
- 分析与建模 - 实时分析
- 应用基础设施与中间件 - 数据交换与集成
- 功能应用 - 远程监控系统
- 网络与连接 - 网络管理和分析软件
- 平台即服务 (PaaS) - 连接平台
适用行业
- 药品
适用功能
- 离散制造
- 物流运输
- 质量保证
用例
- 边缘计算与边缘智能
- 库存管理
- 自动化制造系统
- 预测性维护
- 供应链可见性(SCV)
服务
- 云规划/设计/实施服务
- 数据科学服务
- 软件设计与工程服务
- 系统集成
- 测试与认证
挑战
该制药公司面临着扩张和劳动力转型带来的挑战,导致数百个远程站点的 IT 可见性有限。该公司在全球混合劳动力转型的背景下进行数字化转型,这对日常 IT 运营和战略项目推进提出了挑战。网络运营 (NetOps) 团队正在领导多样化和扩展业务技术平台的努力,以跟上组织发展的步伐。因此,已开始为美洲、欧洲、中东和非洲地区和亚太地区的基于云的服务、Equinix 主机托管数据中心 (Co-lo)、VMware 虚拟化、软件即服务 (SaaS) 和统一通信即服务 (UCaaS) 项目制定战略规划。
关于客户
客户是一家领先的制药公司,其业务逐年扩张,这得益于收入增长、持续的研发 (R&D) 创新以及执行良好的并购战略。在全球制药业面临挑战的 COVID-19 商业时代,该公司取得了这些财务成功,其研发、联系中心、业务、制造和销售运营都受到该组织混合劳动力转型的影响。甚至在疫情到来之前,网络运营 (NetOps) 团队就已率先努力实现业务技术平台的多元化和扩展,以跟上组织发展的步伐。
解决方案
NetOps 团队通过部署 NETSCOUT Smart Edge Monitoring 解决了他们的近期 IT 需求和战略项目目标,该部署提高了对客户端边缘、网络边缘环境、云服务边缘和数据中心边缘的可见性。签约的 NETSCOUT Premium Service Engineer (PSE) 与 NetOps 团队和其他 IT 资源合作,通过协助定义可见性扩展策略来最大化 Smart Edge Monitoring 投资带来的价值,该策略考虑了缩小所有服务边缘(包括客户端(例如远程和 WFH 办公室)、云、网络和数据中心)的盲点。
运营影响
相关案例.
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
Drug Maker Takes the Right Prescription
China Pharm decided to build a cloud-based platform to support the requirements of IT planning for the next five to ten years which includes a dynamic and scalable mail resource pool platform. The platform needed to have the following functions: all nodes support redundancy, ensuring service continuity and good user experience, simple and easy-to-use user interfaces for end users and administrators and good compatibility and supports smooth capacity expansion.
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.