SOP for Software Application User Creation, Activation, and Deactivation

OBJECTIVE
To establish a process for creating, activating, and deactivating users for software applications.

SCOPE
Every manufacturing location can use this SOP.

ACCOUNTABILITY
  • CIT (Officer/Executive): This SOP was prepared.
  • Officer/Executive CQA: Disseminating, retrieving, archiving, and destroying this SOP. Creation of the software application's user list.
  • Operating Manager (CIT): Instruction and efficient application of this SOP.
  • to examine the software application's user list.
  • CQA (Operating Manager): Distribution of this SOP to the appropriate department.
  • The corresponding department (the user) prepared the request for the creation, activation, and deactivation of the user ID.

ACCOUNTABILITY
Head CQA: 
Permission, Make sure this SOP is distributed. 
Keeper of all Master Corporate SOPs in hard form and soft copy.



Head CIT: 
Approval and to guarantee that this SOP is implemented effectively. 
To guarantee the software application's user creation, activation, and deactivation.

PROCEDURE
  • All users must receive thorough training on how to operate and create data using the BIMS and QMS Amplelogic software.
  • Every user must use their unique login to access SAP, LIMS, BIMS, QMS, and other programs.
  • In accordance with Annexure-I, "Requisition for User ID Creation, Activation and Deactivation," users or others must submit a request to the IT administrator for the creation or deactivation of their user IDs.
  • Every user must be fully aware of their privileges.
  • Department-wise login creation will be done.
  • Before creating a user, the IT person or department head must be trained in the relevant field to ensure that the person is appropriately trained.


  • Department Head of respective area (QA/ Warehouse/Production/PPIC etc.) shall be intimate to Head IT or Designee for User creation of person.
  • After the Department Head confirms, Head IT will create the user.
  • The manager or designee is responsible for making sure that only authorized individuals have logical access to the software used in the plants.
  • The user will be given a password and unique identification code to access the software for entering purposes.
  • The QA administrator is in charge of granting authorization, which includes rescinding and distributing the credentials shown in the table.
  • Users must use their given unique ID and password to complete tasks on departments.
  • The "List of User" for software should follow Annexure-II.
  • The title of Annexure-II, "List of User for Software Application," must include the user's name, ID, creation date, and time.
  • A new user must submit a request for user creation in accordance with Annexure-III, Titled "User Creation," which must be accepted by the department head or designee and sent to the administrator so that the IT administrator can assign a user ID and password.
  • In accordance with Annexure-IV, the user will submit a request for user deletion or disablement if they leave the company, move to another department, or transfer to another plant. titled "User Deletion/Modification," and the head of QA must approve it.
  • The administrator will provide the user ID and password following the completion of the entire training program and/or the manager's or section head's recommendation.
  1. Depending on the features available in the software, the administrator at the workstations will configure the user access rights and privileges for different functions.

User Obligations:
  1. When a user logs in to their workstation for the first time, they must update their password to ensure that it remains secret.
  2. To prevent easy password detection, the user group password must be at least six characters long and comprise both alphanumeric and numeric characters in a unique combination.
  3. The user must replace his password after the 90-day period that the user group password has expired.
  4. A user may log in to a computerized lab instrument no more than three times. The user ID will be automatically locked after three failed attempts to log in.
  5. If the user ID is locked or disabled, a request to have the ID unlocked or enabled is made using Annexure-III. All concerned parties will receive training after the IT administrators unlock user IDs and passwords and confirm the reason.

ANNEXURE
Annexure-I: User ID Creation, Activation, and Deactivation Requisition
Annexure-II: Software Application User List
Annexure III: User Creation
Annexure-IV: User Deletion/Modification 

REVISION HISTORY
Nil

Post a Comment

0 Comments

Close Menu
close