What generic fields/values are required for the PRO-M software application?
In addition to those listed above, which are existing fields in EAM/CMMS systems, PRO-M generates a lot of output (~40 data fields per component) that can stay within PRO-M. However, the newly generated or modified PM Task Names and Intervals will presumably need to go back to the EAM/CMMS – currently a simple batch export – for regular scheduling, work control, and PM package preparation. Some other data fields might also be desirable in the EAM/CMMS and can be exported if needed – such as the economic risk from an in-service failure, functional importance classification, etc.
