POMS offers the full scope of project services to serve our customers and to implement POMS® solutions. All services are governed by POMS‘ proven Project Methodology which has been refined over more than 25 years.
POMS professional project services utilize experienced project engineers and project managers as well as our industry partners to deliver best in class services to our customers. Our services include:
  • Project Management
  • Requirements Definition
  • Business Process Analysis and Process Standardization
  • System Functional and Technical Design
  • Integration Services for Business and Plant Systems
  • System Configuration, Testing, Commissioning, and Go-live
  • Validation Services
home-5-980x432
Phases_1
The Concept phase involves the activities in the sales cycle to develop project estimates and a customer proposal document. Appropriate POMS organizations are involved in the creation and approval of the proposal. The customer purchase order is received and booked in this phase.
POMS begins the project with set up of the project infrastructure which includes requesting creation of a new project workspace and organization of the workspace.

An initial Project and Quality Plan governs the Planning and Analysis Phases which may be revised as needed to cover the Implementation Phase.

An initial project schedule is created. POMS works with the customer to schedule the project tasks, deliverables, and resources for the project. Critical customer dependencies are included and highlighted in the schedule.

The purpose of the requirements analysis exercise is for POMS to completely understand the customer user requirements, to translate those into POMS functional requirements, and to document the functional design(s) for the system.
The Implementation Phase deploys and tests the POMS solution using the functional requirements, POMS products, and data supplied by the customer.
The purpose of the Project Closeout phase is to ensure that all contracted project commitments have been met, that the customer project manager agrees the project has been completed, and that POMS’ internal accounting procedures for project close-out have been performed.
Previous slide Next slide

Global Rollouts

Core System

  • The program depends upon development of the requirements, design, and solution for a core system.

  • The core teams will review in detail the various processes and corresponding user requirements that comprise the solution landscape.

  • The result is finalized and approved process flows, User Requirements, Functional Design Specification, and Interface Design Specification documents.

  • Recipe standards and best practices will be documented in a Recipe Standards document.

  • Interface detailed design and configuration occurs during core system activities. Interfaces will be designed and configured so that a common transaction set is created and maintained for the program. Plant specific configurations will be applied at each plant utilizing the core transaction set.

  • The core POMSnet application is tested in a Factory Acceptance Test. The test results will be leveraged to reduce the testing and validation effort required for each site rollout.

  • Planning for all core system and plant rollout activities is ongoing. The core teams help manage, monitor, and control the plant rollouts. The customer coordinates through their core team the software, data, installation, and issue tracking activities to centralize this effort and reduce duplication of effort during plant rollouts.

 

Plant Rollout

  • Plant rollouts begin at the completion of the core system activities culminating in core system Factory Acceptance Testing. The POMS Core Team is engaged throughout plant deployment globally. The customer core team and plant teams continue to take on more responsibility following completion of the core system work and as plant deployments progress.

  • The core system, including interfaces, is deployed for each site. The core system is “localized” for each site, meaning that the plant specific configurations and language are implemented.

  • Site Acceptance Testing is conducted with the purpose of testing site specific configurations rather than core system functionality. User training is conducted, validation testing is executed, and the system is deployed live in production.

core_Team