25.03.2026 12:04
Status: #plant
Tags: #mmr
About
Inspection reports
Service unit
- User navigates to the product SharePoint page within the service area
- User navigates into the default folder called "02 Inspection reports"
- User creates a new "Inspection report" from the New=> Dropdown (like Service orders)
- User fill out basic metadata (TBD)
- User uploads all files for this inspection to the new document set
- Please use name like => General name structure
- User tags files, that should be published to the customer with a metadata flag (Published, To be published, Empty)
MMR unit
- Every night a job runs, that migrates data from Service unit to MMR unit
- Please follow the nomenclature from General name structure
- The job searches for all files, that have the tag "To be published"
- IT iterates those files, and copies them to the MMR unit
- It re-creates exactly the same structure like within the service unit
Within MMR
- If a customer navigates to the site (ie. Hamburg), he will find a button "Inspection reports" on the product.
- Pressing the button will lead, to the list of "Document sets" that have been created by the job from the last section
- Naming of buttons is still a matter of discussion
Inspection report: Name structure
Docset Name:
Date_SerialNumber_Entity_Report => File names stay the sameSpare parts list
Service unit
- User uploads a new PDF file and tags it, as a "spare part list"
- Please follow nomenclature Spare parts list: Name structure
MMR unit
- Each night, a job runs and migrates the spare parts list to the MMR (tags it accordingly)
Within MMR
- User navigates to site overview page
- User clicks a button "Spares list" and finds the file via. SharePoint search
Spare parts list: Name structure
File:
Date_SerialNumber_Entity_SparesListFlags in MMR
Spare parts list exists (Auto set)
Documentation exists (Auto set)
Show documentation in Customer Portal
Show spares list in Customer Portal
Spare parts catalogue exists AND shown in Portal (single flag, no auto set)