Hobbs Valves - Cardiff University
categories
There is some evidence of fragmentation of the information is seen, in the form of individual stores of information. Individual updates are requested and delivered between staff in order to augment the ‘standard’ information.
The production planning database is potentially a driving force of information, but one that appears to be a source of data driven by individual updates.
The continuous review process appears to be labour intensive even considering the level of reward for it. There are a series of set rules being followed, with a degree of additional manual input which adds value for the customer but creates a unique identity for every enquiry (despite the high level of repeated enquiries from different sources). Would a more standardised response to the enquiry process make the process more straightforward once the relevant details are collated? Although they are described as wide and constantly varying there must be a common core set of details required which are currently being used to create the quality plan, production schedule and purchasing timetable? – this could be included in the front end of the production planning environment, negating the need for extensive sign-off and actuation activity, and also provide a more rigid framework for capturing the initial enquiry details – ‘get it right first time’.
There is an opportunity to maintain the quality of work being done and of information being communicated by dedicating all efforts to maintenance of a single system. This could be either
- a single excel workbook created specifically for each job listing all of the individual information sheets (a list of which forms the simplest form of production schedule)
- the existing database controlling all the jobs and recording all the information, which would require some detailed application of access to create lower levels of information for use by the individual business functions which directly (and automatically) report back to the top level.
Therefore, prior to complete investment in an MRP/ERP system, it is proposed that the current database OR project spreadsheets could be adapted to add functionality and delay the need for investment. The principle benefits would be a better understanding of what is required from the system, and how it could be achieved.
The production planning database is potentially a driving force of information, but one that appears to be a source of data driven by individual updates.
The continuous review process appears to be labour intensive even considering the level of reward for it. There are a series of set rules being followed, with a degree of additional manual input which adds value for the customer but creates a unique identity for every enquiry (despite the high level of repeated enquiries from different sources). Would a more standardised response to the enquiry process make the process more straightforward once the relevant details are collated? Although they are described as wide and constantly varying there must be a common core set of details required which are currently being used to create the quality plan, production schedule and purchasing timetable? – this could be included in the front end of the production planning environment, negating the need for extensive sign-off and actuation activity, and also provide a more rigid framework for capturing the initial enquiry details – ‘get it right first time’.
There is an opportunity to maintain the quality of work being done and of information being communicated by dedicating all efforts to maintenance of a single system. This could be either
- a single excel workbook created specifically for each job listing all of the individual information sheets (a list of which forms the simplest form of production schedule)
- the existing database controlling all the jobs and recording all the information, which would require some detailed application of access to create lower levels of information for use by the individual business functions which directly (and automatically) report back to the top level.
Therefore, prior to complete investment in an MRP/ERP system, it is proposed that the current database OR project spreadsheets could be adapted to add functionality and delay the need for investment. The principle benefits would be a better understanding of what is required from the system, and how it could be achieved.