iTAC Product Lifecycle Management (iPLM)

There is no doubt that the success of a product is related to the success of its manufacturer. In defining and developing the iTAC.MES.Suite, we have included the continuous monitoring of the product from the very beginning throughout its life cycle, i.e. from defining market requirements through to implementation.

The iPLM process is divided into phases

• Market analysis
• Requirement management
• Specification phase
• Development phase
• Testing phase
• Software release process
• Go to market

Market analysis

• Market observation of global company requirements
• Use of production logistics and other company processes
• Market needs based on feedback from sales processes and the wishes of existing customers
• Creation and definition of the standardization activities of different associations (VDA, VDMA, ZVEI)
• Competition analysis
• Internal analyses: GAP, SWOT

Requirement management

• Definition of strategic requirements based on global market analyses
• Customer-specific requirements are defined in relation to standardization
• Definition of the functions and release date
• Systemized requirement management with the “MKS Integrity Manager“

Specification phase

• Definition of the strategic function extensions for further but consistent development of the product
• Customer-specific requirements are defined in relation to standardization in order to benefit all customers
• The entire requirement management phase is systematically represented via a defined specification
  process with support from the “MKS Integrity Manager“

Development phase

• Definition of development specifications on the basis of technical function requirements
• Derivation of organizational measures to set deadlines for the individual functions as input for defining the testing phase and establishing a resource plan
• Transfer of technical function requirements in defined task packages for development – mapping with the “MKS Source Integrity“

Testing phase

• Internal: Qualification of internal operations such as support, Professional Service, sales, etc.
• External: Release and Delta training for customers, implementation partners, etc.

Scheduling various test phases

• Alpha test phase for verifying the technical requirements regarding functionality, usability, etc.
• System test phase for testing the entire software release using automated test routines
• Test of the basic technolog

System tests and tests of the basic technology are carried out on automated testing systems. The mapping and definition of all test phases is performed with the “MKS Integrity Manager“.

Software release process

• Review of all test phases
• Customer acceptance test and review of test results
• Release and definition of the release state according to the specified process based on the “MKS Integrity Manager“

Go to market

• Definition and creation of product documentation such as handbooks, interface descriptions, etc.
• Training:
  • Internal
    Qualification of internal operations such as support, Professional Service, sales, etc.
  • External
    Release and Delta training for customers, implementation partners, etc.

• Implementation of software releases
  • Verification of function extensions with the customer using customers’ testing systems
  • Implementation in the production system following the customer acceptance test