信息系统运行管理是确保信息系统高效、稳定、安全运行的关键环节，掌握其基本方法与技术对于保障企业或组织信息化建设的成功至关重要

信息系统运行管理是保障系统稳定、高效、安全运行的关键环节，涉及日常维护、性能优化、安全防护、数据管理等多方面内容。以下从基本方法和核心技术两方面展开介绍：

一、基本方法

1. 标准化流程管理

• 制定操作规范：建立系统启停、数据备份、用户权限变更等标准化操作流程，降低人为失误风险。
  例如：规定每日凌晨自动备份数据库，并记录备份日志。
• 故障处理流程：定义“故障报告→初步诊断→技术支持→修复验证→闭环归档”的全流程，确保问题快速响应。
  工具参考：使用ITSM（IT服务管理）平台（如ServiceNow）跟踪故障工单。

2. 日常监控与维护

• 实时监控：通过监控工具（如Zabbix、Prometheus）监测系统性能指标（CPU/内存利用率、磁盘I/O、网络流量等），设置阈值预警。
  示例：当服务器内存使用率超过80%时，自动触发告警通知管理员。
• 定期巡检：每周/月检查系统日志、软件版本更新、硬件状态（如服务器风扇、硬盘健康度），提前发现潜在隐患。

3. 用户管理与培训

• 权限控制：基于最小权限原则（PoLP）分配用户角色，定期清理离职人员账号，防止权限滥用。
  技术实现：通过LDAP（轻量级目录访问协议）统一管理用户认证和授权。
• 培训机制：针对新功能或系统变更，组织用户培训（如操作手册、视频教程、现场演示），提升用户使用效率。

4. 数据管理与备份

• 数据生命周期管理：根据数据重要性分级存储（如热数据存于SSD，冷数据归档至云存储），定期清理无效数据。
• 备份与恢复策略：
  • 全量备份：每周对核心数据进行完整备份；
  • 增量备份：每日仅备份变更数据，降低存储成本；
  • 异地容灾：将备份数据同步至异地数据中心，应对自然灾害等极端情况。
    工具推荐：使用Veeam、Backup Exec等专业备份软件。

5. 性能优化与升级

• 性能调优：分析系统瓶颈（如数据库慢查询、应用代码低效），通过优化SQL语句、增加缓存（如Redis）、扩展硬件（如增加服务器节点）提升性能。
• 版本管理：制定软件升级计划（如季度小版本更新、年度大版本升级），先在测试环境验证，再逐步部署至生产环境。

二、核心技术

1. 自动化运维（AIOps）

• 技术价值：通过脚本（Shell/Python）或自动化平台（如Ansible、Jenkins）实现重复性任务自动化（如批量部署软件、日志分析），减少人工干预。
  案例：使用Ansible编写playbook，一键完成100台服务器的安全补丁安装。
• 智能监控：结合AI算法（如机器学习）预测系统负载趋势，自动调整资源分配（如云计算中的弹性伸缩）。

2. 容器化与微服务架构

• Docker/Kubernetes：通过容器化技术封装应用及其依赖环境，实现“一次构建，随处运行”；利用Kubernetes管理容器集群，提升部署效率和系统可用性。
  场景：电商大促期间，Kubernetes自动扩容容器实例，应对流量峰值。
• 微服务治理：将复杂系统拆分为独立微服务（如用户服务、订单服务），通过API网关（如Nginx、Spring Cloud Gateway）统一管理服务路由和流量控制。

3. 网络与安全技术

• 网络管理：
  • 配置防火墙（如Cisco ASA、Fortinet）过滤非法流量；
  • 使用VPN（虚拟专用网络）实现远程安全接入；
  • 通过SDN（软件定义网络）动态调整网络拓扑，优化数据传输路径。
• 安全防护：
  • 入侵检测（IDS/IPS）：部署Snort、Suricata等工具实时检测攻击行为；
  • 漏洞管理：使用Nessus、OpenVAS定期扫描系统漏洞，及时修复；
  • 身份认证：采用多因素认证（MFA，如短信验证码+指纹）增强登录安全。

4. 云计算与虚拟化技术

• 云平台管理：在AWS、阿里云等公有云或OpenStack私有云中，通过控制台或CLI（命令行接口）管理云服务器（EC2/ECS）、存储（S3/OSS）和数据库（RDS）。
• 虚拟化技术：利用VMware、Hyper-V创建虚拟机（VM），实现硬件资源池化，提高利用率（如一台物理服务器运行10个VM，分别承载不同应用）。

5. 日志与数据分析

• 日志管理：通过ELK Stack（Elasticsearch+Logstash+Kibana）或Fluentd集中收集、存储和分析系统日志，快速定位故障根源。
  示例：通过Kibana可视化界面查看某接口的错误日志分布，识别高频问题点。
• 数据分析技术：运用SQL、Python Pandas等工具分析运行数据（如用户访问量、系统响应时间），为优化决策提供依据。

三、实践建议

1. 建立知识库：将常见故障解决方案、操作手册等整理成内部知识库（如Confluence），方便团队快速检索。
2. 定期应急演练：模拟系统崩溃、数据丢失等场景，测试备份恢复流程和应急预案的有效性。
3. 关注技术趋势：跟踪DevOps、边缘计算、AIops等新技术，持续优化管理模式。

通过以上方法和技术的结合，可有效提升信息系统的可靠性、可用性和可维护性，支撑业务的持续稳定运行。

信息系统运行管理是确保信息系统高效、稳定、安全运行的关键环节，掌握其基本方法与技术对于保障企业或组织信息化建设的成功至关重要。以下是相关信息：

一、信息系统运行管理的基本方法

1. 制定运行管理制度
   • 明确职责分工：明确系统管理员、网络管理员、数据库管理员、安全管理员等不同角色的职责，确保每个环节都有专人负责。
   • 建立操作规范：制定系统操作流程、数据备份与恢复流程、故障处理流程等，确保操作的标准化和规范化。
   • 制定应急预案：针对可能出现的系统故障、数据丢失、网络攻击等突发事件，制定详细的应急预案，明确应急响应流程和责任人。
2. 建立监控机制
   • 实时监控：通过监控工具对系统的运行状态进行实时监控，包括服务器性能、网络流量、应用系统运行情况等，及时发现异常情况。
   • 性能评估：定期对系统的性能进行评估，分析系统的响应时间、吞吐量、资源利用率等指标，找出性能瓶颈，为系统优化提供依据。
   • 日志分析：收集和分析系统运行日志，及时发现潜在的安全隐患和故障隐患，为故障排查和系统优化提供线索。
3. 实施变更管理
   • 变更申请与审批：对系统进行任何变更（如软件升级、硬件更换、配置调整等）都需要经过严格的申请和审批流程，确保变更的必要性和安全性。
   • 变更测试：在变更实施前，进行充分的测试，包括功能测试、性能测试、兼容性测试等，确保变更不会对系统的正常运行产生负面影响。
   • 变更记录与回退：详细记录变更的内容、时间、责任人等信息，以便出现问题时能够快速定位原因，并制定回退方案，将系统恢复到变更前的状态。
4. 加强用户管理
   • 用户权限管理：根据用户的角色和职责，授予相应的系统访问权限，确保用户只能访问其工作所需的资源，防止权限滥用。
   • 用户培训与支持：定期对用户进行系统使用培训，提高用户对系统的熟悉程度和操作技能，同时为用户提供技术支持，及时解决用户在使用过程中遇到的问题。
   • 用户反馈收集：建立用户反馈渠道，收集用户对系统运行的意见和建议，及时对系统进行优化和改进，提高用户满意度。

二、信息系统运行管理的基本技术

1. 网络管理技术
   • 网络设备管理：通过网络管理工具对路由器、交换机等网络设备进行配置和管理，包括设备的IP地址分配、端口配置、VLAN划分等，确保网络的稳定性和安全性。
   • 网络流量监控与优化：使用网络流量监控工具实时监测网络流量，分析流量的来源、去向和类型，及时发现网络拥塞和异常流量，通过流量整形、负载均衡等技术优化网络性能。
   • 网络安全防护技术：部署防火墙、入侵检测系统（IDS）、入侵防御系统（IPS）等网络安全设备，防止外部攻击和内部安全威胁，同时采用加密技术对网络传输的数据进行加密，确保数据的保密性和完整性。
2. 服务器管理技术
   • 服务器性能监控：通过服务器监控工具对服务器的CPU、内存、磁盘、网络等硬件资源的使用情况进行实时监控，及时发现性能瓶颈，通过资源调配、性能优化等手段提高服务器的运行效率。
   • 服务器安全加固：对服务器操作系统进行安全配置，关闭不必要的服务和端口，安装安全补丁，设置访问控制策略，防止服务器被攻击和入侵。
   • 服务器虚拟化技术：采用服务器虚拟化技术将一台物理服务器虚拟成多台虚拟服务器，提高服务器资源的利用率，降低硬件成本，同时便于服务器的管理和维护。
3. 数据库管理技术
   • 数据库备份与恢复：定期对数据库进行备份，包括全备份、增量备份和差异备份，将备份数据存储在安全的位置，并定期进行恢复测试，确保在数据丢失或损坏时能够快速恢复数据。
   • 数据库性能优化：通过分析数据库的运行状态和性能指标，优化数据库的结构设计、索引配置、查询语句等，提高数据库的查询速度和存储效率。
   • 数据库安全防护：采用数据库加密技术对敏感数据进行加密存储，设置数据库访问权限，防止非法访问和数据泄露，同时对数据库的运行日志进行监控和审计，及时发现异常操作。
4. 中间件管理技术
   • 中间件配置管理：对中间件（如Web服务器、应用服务器、消息中间件等）进行配置和管理，确保中间件的正常运行和性能优化。
   • 中间件性能监控：通过监控工具对中间件的运行状态进行实时监控，包括中间件的响应时间、吞吐量、资源占用等指标，及时发现性能问题并进行优化。
   • 中间件安全防护：对中间件进行安全配置，防止中间件被攻击和入侵，同时对中间件的运行日志进行监控和审计，及时发现异常操作。

三、信息系统运行管理的注意事项

1. 持续学习与创新：信息系统运行管理是一个不断发展和变化的领域，需要持续学习新的技术和方法，关注行业动态和发展趋势，不断优化和改进运行管理策略。
2. 注重团队协作：信息系统运行管理涉及多个部门和多个角色，需要加强团队协作，建立良好的沟通机制，确保各部门之间能够密切配合，共同保障信息系统的正常运行。
3. 强化安全意识：信息安全是信息系统运行管理的重要组成部分，需要强化安全意识，加强安全管理和技术防护，防止信息系统的安全事件发生。
4. 以用户为中心：信息系统运行管理的最终目的是为用户提供优质的服务，因此需要以用户为中心，关注用户需求，提高用户满意度，不断优化系统性能和服务质量。

总之，掌握信息系统运行管理的基本方法与技术，对于保障信息系统的稳定运行、提高企业或组织的信息化水平具有重要意义。
Steelcase 通过采用云原生实践和技术重构核心业务应用，主要体现在以下几个方面：

与专业团队合作

Steelcase 与 Pivotal Labs 在马萨诸塞州剑桥进行了为期 15 周的协作。Pivotal Labs 是一家在云原生应用开发方面具有丰富经验的团队，通过此次合作，Steelcase 获得了专业的技术指导和开发支持，为其重构核心业务应用奠定了基础。

采用云原生技术

Steelcase 的云原生实践基于容器化、微服务等技术。这些技术使得应用能够以更灵活、高效的方式运行在动态环境中，如公共云、私有云或混合云。通过容器化，Steelcase 的应用可以快速部署和扩展，同时微服务架构使得应用的各个组件可以独立开发和更新，提高了开发效率和系统的可维护性。

构建敏捷开发流程

Steelcase 通过云原生实践实现了敏捷开发。开发团队能够更快速地响应业务需求的变化，频繁地进行应用的更新和优化。这种敏捷性使得 Steelcase 能够在市场变化中保持竞争力，及时推出新的功能和服务。

提升数据处理与分析能力

Steelcase 利用云原生技术重构核心业务应用后，能够更好地处理和分析大量数据。通过与微软 Azure 云平台的合作，Steelcase 的应用可以高效地收集、存储和处理来自各个业务环节的数据。这些数据不仅包括生产过程中的机器数据，还包括用户行为数据等。通过对这些数据的分析，Steelcase 能够获得更深入的业务洞察，从而优化生产流程、提升产品质量和用户体验。

增强系统的可靠性和弹性

云原生技术使得 Steelcase 的应用具备了更高的可靠性和弹性。通过容器编排工具（如 Kubernetes）的自动化管理，应用能够在出现故障时自动恢复，并且能够根据负载动态调整资源分配，确保系统的稳定运行。这种弹性和可靠性对于 Steelcase 的核心业务应用至关重要，尤其是在面对高并发访问和复杂业务场景时。

促进跨部门协作

Steelcase 的云原生实践还促进了不同部门之间的协作。开发团队、运维团队和业务团队能够通过云原生平台更好地协同工作。开发团队可以更快速地将新功能推向市场，运维团队能够更高效地管理基础设施，业务团队则能够根据实时数据做出更明智的决策。这种跨部门的协作模式提高了整个组织的运营效率和创新能力。
This sentence can be parsed as: “How did Steelcase use cloud - native practices and technologies to re - design or re - imagine a core business application?” It focuses on exploring the methods and processes by which Steelcase, a company, leverages cloud - native related practices and technologies to transform or upgrade its core business applications, with the aim of improving application performance, enhancing business efficiency, and better meeting business needs.

Steelcase is the world’s largest office furniture manufacturer. It may adopt cloud - native practices and technologies to reconstruct core business applications, probably to solve problems such as complex traditional application architectures, difficulty in rapid iteration, and poor compatibility with the cloud environment. According to the available information, Steelcase may have taken the following measures:

• Cooperated with technology providers: Steelcase cooperated with VMware Tanzu. By using the latter’s cloud - native tools, it updated a decades - old application, which brought considerable efficiency improvements to the enterprise.
• Used the application service platform: It is likely to use VMware Tanzu Application Service. This platform streamlines the development process, enabling developers to have more time to write code. Its automation function, combined with Concourse (a CI/CD delivery system), can realize the automation of the delivery pipeline.
• Automated manual processes: With the help of VMware Tanzu Automation, Steelcase can easily transform manual processes into automated pipelines, and automatically execute regular updates, and can also realize the automation of core security functions to achieve large - scale and rapid execution.
  Pivotal is now part of VMware, so some of these products and services are now part of VMware Tanzu. Learn more

Since the founding of Steelcase over 100 years ago, its products have embodied an ethos of user centricity. In fact, one of the company’s first patents was for a metal wastepaper basket designed to prevent fires caused by office workers using wicker baskets while smoking. The user-centered principles that led to metal baskets continue to inform Steelcase’s products and contribute to the company’s rise as the largest furniture manufacturer in the world.

Steelcase now specializes in helping “customers create the unique workspace environments they need to drive their own innovation and growth,” explained Gail Moutrey, VP of Global Brand Management and Workplace Innovation. Today, Steelcase is sold by hundreds of dealers across the globe and furnishes offices as varied as the companies it serves—with furniture, technology, and architectural solutions that are almost infinitely customizable. “Every human on earth could buy 66 million different products from us before there would be a duplicate,” said Steelcase CIO Steve Miller.

To help customers design and order these custom solutions, Steelcase and its dealers have relied on a massive application built in the 1980s by Hedberg Data Systems, a subsidiary of Steelcase. The Hedberg application provides quoting and order management as well as various functionalities to help dealers manage their business. According to Miller, Hedberg processes in excess of $5 billion worth of invoices for Steelcase dealers annually.

“It has been the workhorse of our business,” said Miller. “This is how our business flows in. It’s been the face of Steelcase to our dealer community for decades.”

While Hedberg has been refreshed from time to time, the monolithic application system is based on decades-old technology, making development difficult and slow. And while some of the platform is in the cloud, much is not, requiring dealers to maintain on-premises hardware and software.

There are lots of companies that can develop stuff for us. But what we wanted was a transformation in the way we work. And that was where we felt Pivotal was especially suited as a partner.”
Steven Miller, CIO

“Dealers need a technology that is able to keep pace with rapidly changing business requirements as they face pressures like shifting market conditions and higher customer expectations,” said Brian Saum, IT Director, Customer Engagement at Steelcase. “It takes us the better part of 9–12 months to get out a major release to all of our dealers…This is not at all a pace that’s going to allow our dealers to stay competitive down the road.”

Steelcase saw an opportunity to not only change the software platform, but also improve the way its engineers build software. “We’ve really hit the point where it’s time for a rebirth,” said Miller. “It was about bringing together both the practice changes and the software changes in order to sustain a continuous innovation of the [Hedberg] platform.

“There are lots of companies that can develop stuff for us. But what we wanted was a transformation in the way we work. And that was where we felt Pivotal was especially suited as a partner. Unleashing the team to deliver results quickly was really at the heart of what we needed to do.”
New skills and cloud native tools mean fresh possibilities for a decades-old application

Steelcase engaged with Pivotal Labs in a 15-week engagement in Cambridge, Massachusetts. The engagement centered on enabling the Hedberg team in modern development practices such as pair programming and test-driven development (TDD). Simultaneously, they applied this hands-on learning by building a new application, referred to as H2, to replace the old Hedberg system.

“There was a lot of synergy right from the beginning … we were speaking the same language. And what was really great was the way the Pivotal team had a plan,” said Miller. “They had a process that worked and it was very complementary to the process Steelcase uses with our customers. So it felt right.”

Business Director for Hedberg, Brian DeRoo recalls the one-on-one nature of the Pivotal experience: “When you go to a Pivotal Labs engagement, every person you send is paired with somebody from Pivotal Labs. So as you go through this transformational journey, you’ve always got someone alongside you—whether you’re the product manager, designer, a software engineer, you’ve always got someone coaching you.”

Moving to public cloud was also an important part of the engagement with Pivotal. So Pivotal Labs practitioners taught the Steelcase team how to use modern developer tools like Spring Boot and technologies like Pivotal Platform to accelerate the shift to a cloud native architecture. The new H2 applications run on Tanzu Application Service atop Microsoft Azure.

Another goal of the Pivotal Labs engagement was helping Steelcase reimagine what Hedberg could become. Pivotal practitioners showed the Steelcase team how to conduct in-depth user research and perform structured exercises to help identify what to prioritize and build first. Through these processes, the group determined that one core function of the Hedberg application needed to be tackled first: building and editing quotes for customer orders, a complex process compounded by the sheer number of customizable product combinations.

When you go to a Pivotal Labs engagement, every person you send is paired with somebody from Pivotal Labs. So as you go through this transformational journey, you've always got someone alongside you.”
Brian DeRoo, Business Director for Hedberg

Fast release cycles and user-centered design give dealers a new competitive edge

Equipped with new development skills, fast, flexible tools, and a jumpstart at Pivotal Labs, the Hedberg team is steadily developing and transitioning from the old Hedberg to the new H2 applications. “In the environment that we’re working in and the way that we’re working, we’re pushing out updates every week—and with the goal of doing it even more frequently,” said DeRoo.

This has significant implications for Steelcase’s business. “In the past when there were changes in the market and we needed to get new capabilities to dealers, it could take 14 months,” said Miller. “Now, we’ve taken that down to a matter of days…that is a radical shift that will lead to business results for both the dealers and us.”

Additionally, using Pivotal Platform and cloud native practices allows Steelcase to develop and release new capabilities while the legacy system is still in use. “What we’ve been able to do is develop this in a way that they could run both and that allows them to really develop this in a fast iterative way, which is key,” explained Miller.

Aside from the speed with which the Hedberg team is able to develop software, adopting Pivotal’s rigorous, user-centered practices has made the new applications easier and more efficient for dealers to use. With a full-time UX designer—something brand new for the Hedberg system—Steelcase now follows a more in-depth process that includes building prototypes for users to try while the product team observes the interaction.

“We get better feedback and we get it a whole lot quicker which is great,” said Brian Walch, Director of IT for Hedberg Data Systems.

The new order and quote system serves as an example of the power of user-centered design for software. Previously, dealers had to navigate through many screens with multiple menus to create an order. The new application significantly reduces the number of clicks, keystrokes and screens for users. Dealers reported that the new system takes half the time and keystrokes to structure a quote compared to the old. One dealer noted that the new application will eliminate a full 40 hours of work per week.

“That’s a person that can now be out selling or doing something to serve the customer,” said Miller. “So the initial feelings are that it’ll have a pretty dramatic effect on their operational overhead. Our dealer community is so excited.”

Adopting a product mindset brings IT closer to the business

In addition to embracing new technologies and practices, Steelcase made organizational changes to facilitate its new development practices. The IT team is now organized by product teams, improving the relationship IT has with the business side of the company. Processes and roles related to security and quality have also changed with the adoption of TDD and the automation and continuous delivery enabled by Pivotal Platform.

“Security used to be something that happened as the last step before you launch something,” explained Miller. “Now it’s actually built into the process of developing solutions.”

Another organizational change the Hedberg team adopted was a redesign of the workspace. Steelcase and Pivotal collaborated on redesigning the office to allow for pair programming and colocated teams in one single area. The new Agile Studio makes it easy for team members to communicate, reducing the need for email and meetings, and gives Steelcase firsthand knowledge of creating and working in agile workspaces.

Reflecting on the engagement with Pivotal Labs, DeRoo is proud of what the Hedberg team has accomplished and cited Pivotal as an enabler of this transformational undertaking:

“Engaging with Pivotal has given us a new foundation to work with—not only from a tools perspective, but from a process perspective, as well. Pairing with folks who had been through this before, who had experience, who could teach us all of these different tools and processes and technologies—that was absolutely huge. There’s just no way we would have piecemealed this together.”

With the success of H2, the Hedberg renaissance has set a new standard for software for the rest of the company, as well as in the industry as a whole. “Hedberg has traditionally been a tool focused on our business in the Americas and from here it is moving forward to become a global tool, which makes it much more of a global industry standard,” said Miller. “To start to become the standard of how this happens in the industry is a pretty big deal to us.”