C
C.E. Marshall
Definition & management of revisions of in-house d-bases
Our company has a "mature" quality system that is gaining momentum in our efforts to move from paper to electronic documentation. Since the inception of our QS we have used a document change process that has "controlled" every change for almost every document. The processes key input is a formal approval and one of it's key outputs is a change record. The exception to this formal approval process and resulting record trail has been our in-house databases that are regularly being "tweaked" to meet internal customer requirements. These continuous improvements are a good thing, but we struggle with what constitutes a change and if, when, or how to record these changes. Currently we enter these databases onto our master lists, but the majority are still the original issue despite numerous tweaks. D-bases are maintained on our network, are regularly backed up, and users can only access the most current" version. So, how do other folks define and manage all types of changes/revisions to internal databases?
Thanks C.E. Marshall
Our company has a "mature" quality system that is gaining momentum in our efforts to move from paper to electronic documentation. Since the inception of our QS we have used a document change process that has "controlled" every change for almost every document. The processes key input is a formal approval and one of it's key outputs is a change record. The exception to this formal approval process and resulting record trail has been our in-house databases that are regularly being "tweaked" to meet internal customer requirements. These continuous improvements are a good thing, but we struggle with what constitutes a change and if, when, or how to record these changes. Currently we enter these databases onto our master lists, but the majority are still the original issue despite numerous tweaks. D-bases are maintained on our network, are regularly backed up, and users can only access the most current" version. So, how do other folks define and manage all types of changes/revisions to internal databases?
Thanks C.E. Marshall