A Coggle Diagram about Previous events (The Number of Test Object vehicles in a fleet/pool are measured as a KPI. Goal in GOT is ~ 200 and max 600 worldwide., With the implementation of the RnD30 philosophy, Test Objects are often shared by the product development projects for cost efficiency reasons. Historically the test objects were connected to single projects to a larger extent. (TBC),
GLORIA & ProTOM systems have been developed to replace previous system combination TOB/JENA & PROTUS (partly).
PROTUS still has issue reporting functionality. Gloria is being implemented. and Old SUV2 was the working IT tool in GOT for planning of Test Objects until PROTOM was released. SUV2 was in contact with PROTUS and TOB/JENA but now when we have released PROTOM and GLORIA (Q3 2016) we have lost the connection to plan in SUV2.
Old SUV2 was also developed to handle both SW request, Material status, Material Not ordered, Software Update Meeting, SWUP. Test Object status meeting Week minus 2, WEM-2, Campaign management status, Project Vehicle/Rigs Update meetings, VUM/RUM, Test Object diaries, Resource and appointed persons, Weekly and Long lead times planning for both projects, SW and persons (my rebuilds), Allocating Test Objects to specific projects. EE task list for upcoming work. SW baselines to be chosen in SW request. KPI reports. Road Approval list. ), Fundamental ideas (Product Builds is the organization preparing and delivering all Prototype Builds (called Test Objects) requested by Group Trucks Technology projects for any users., The mission is to lead the cross functional work in the Physical Project Build process from an order is received to the Test Object is delivered to the customer according to agreement. and The planning of the Test Object building is done locally.) and Current status of the change process.