Specification Versioning/ Amendmen : 

1.QA & Packaging Section Amendment

2.QA Section Amendment

 


If there is any requirement to amend the existing active specifications, then there is an option in MQuality tool to create new version of the same specification

 

  • To create a new version, Local QA user clicks on Request icon and clicks on Specification Management
  • Local QA user searches for active specification by using filter on Specification page 

  • Local QA user views “Amend SP” option for active specifications
  • Local QA user clicks on “Amend SP” and a pop-up opens with two options which user can select:
  1. QA Section: If Local QA user selects this option then only QA section will be available for amendment
  2. QA & Packaging Section: If Local QA user selects this option then both QA & Packaging sections will be available for amendment

 

 

1.QA & Packaging Section Amendment

 

  • Local QA selects QA & Packaging section as amend type and lands on to Amend SP Request page

 

  • New SP Id is created with new versioning
  • Supplier Contact, CQA Expert, OB Expert user and GTIN details are pre-populated with previous data which can be edited
  • Amend Type attribute is editable for Local QA
  • Start date for new version is automatically updated when the new version is opened

 

  • Local QA user click on Save and Next to proceed to Amend QA & Packaging Section

  • Local QA user updates the QA section and Packaging Section
  • If Local QA user clicks on Send for Review action, then the SP is sent to Supplier and OB user for alignment so Local QA can update new version of SP accordingly
  • OB Expert user logs into MQuality tool and view task to Amend Packaging section sent by Local QA user

  • OB user runs the task and lands on to Amend Packaging section screen

 

  • OB user reviews the details and updates the packaging section by providing comments

 

  • If OB user clicks on Send for review then the task will be moved to Local QA user and Supplier for review
  • If OB user clicks on Accept, then the task will be sent to Local QA user for approval
  • If Local QA user clicks on Accept action, then new SP version’s status changes to Approved

 

 

2.QA Section Amendment

  • Local QA selects QA section as amend type and lands on to Amend SP Request page

 

  • New SP Id is created with new versioning
  • Supplier Contact, GQA Expert and GTIN details are pre-populated with previous data which can be edited
  • OB user attribute is non-editable
  • Start date for new version is automatically updated when the new version is opened

  • Local QA user click on Save and Next to proceed to Amend QA Section

  • Local QA user updates the QA section 
  • If Local QA user clicks on Send for Review action, then the SP is sent to Supplier and OB user for review so Local QA can update new version of SP accordingly
  • If Local QA user clicks on Accept action, then new SP version’s status changes to Approved

 

 

Packaging Section Amendment

  • OB user logs in to MQuality tool and navigates to search specification page
  • OB user searches for active specification by using filter on Specification page

 

  • OB user views “Amend SP” option for active specifications
  • OB user clicks on “Amend SP” and a pop-up opens with option which user can select:
    1. Packaging Section: If OB user selects this option then only Packaging section will be available for amendment

 

  • OB user selects Packaging section as amend type, clicks on OK button and lands on to Amend SP Request page


  • New SP Id is created with new versioning
  • Supplier Contact and OB Expert user are pre-populated with previous data which can be edited
  • GTIN details are not editable by Packaging user
  • Amend Type attribute is non-editable
  • Start date for new version is automatically updated when the new version is opened

  • OB Expert user click on Save and Next to proceed to Amend Packaging Section

 

  • OB Expert user updates the Packaging Section
  • If OB Expert user clicks on Send for Review action, then the SP is sent to Supplier user for alignment so Local QA can update new version of SP accordingly
  • If OB Expert user clicks on Accept, then the task will be sent to Local QA user for approval
  • If Local QA user clicks on Accept action, then new SP version’s status changes to Approved