# Electronic Signatures and Change Management

**URL:** <https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413>\
**Category:** Ignition\
**Created:** [October 25, 2019, 11:09pm UTC](https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413 "2019-10-25T23:09:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmonter](https://avatars.discourse-cdn.com/v4/letter/j/858c86/32.png) [@jmonter](https://forum.inductiveautomation.com/u/jmonter)\
**Post date:** [October 25, 2019, 11:09pm UTC](https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413/1 "2019-10-25T23:09:43Z")

</div>

Have a potential project to migrate an iFix system to Ignition but there is a feature in iFix that will need to be duplicated. Electronic Signature and Change Management does anyone know if there is an add-on module already developed for ignition?

**Before an action is performed (i.e. set-point change) the performer must provide his/her user name and password and optional comment than a verifier (someone else) must do the same before the action can be performed.**

_ **All this has to be 21 CFR Part 11 compliant.** _

[https://www.ge.com/digital/documentation/ifix/Subsystems/CM/content/cm\_ifix\_electronic\_signatures\_and\_change\_management.htm](https://www.ge.com/digital/documentation/ifix/Subsystems/CM/content/cm_ifix_electronic_signatures_and_change_management.htm)

---

<div class="post-metadata">

**Author:** ![rodoljub.ivanovic](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rodoljub.ivanovic](https://forum.inductiveautomation.com/u/rodoljub.ivanovic)\
**Post date:** [February 9, 2020, 10:23am UTC](https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413/2 "2020-02-09T10:23:01Z")

</div>

I also searching for this answer, what I found there is not kind of module for the esign. Think, that is the way to make your own pop up window, with the esign login form, on some event of changing the value of tag. Good thing there is the option which you can enable it, for tracking and storing, all events from operator side in an SQL database

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [February 9, 2020, 2:21pm UTC](https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413/3 "2020-02-09T14:21:34Z")

</div>

Why is it necessary to log credentials before making changes? A user shouldn’t be able to make changes unless they are logged in and auditing keeps track of the changes they made. All of this is already at your finger tips.

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [February 9, 2020, 7:16pm UTC](https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413/4 "2020-02-09T19:16:08Z")

</div>

> [@jlandwerlen](#):
>
> Why is it necessary to log credentials before making changes?

The requirement is for two separate users to confirm the specific action:

> [@jmonter](#):
>
> the performer must provide his/her user name and password and optional comment **than a verifier (someone else) must do the same before the action can be performed**.

This can be accomplished easily with a custom popup window as suggested by @rodoljub.ivanovic. If you don't need to confirm two credentials or reconfirm one before taking the action, auditing as you suggest could be a good solution.

---

<div class="post-metadata">

**Author:** ![rodoljub.ivanovic](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rodoljub.ivanovic](https://forum.inductiveautomation.com/u/rodoljub.ivanovic)\
**Post date:** [February 9, 2020, 7:43pm UTC](https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413/5 "2020-02-09T19:43:27Z")

</div>

Here is the link of GE IFIX solutions for esign: [https://www.ge.com/digital/documentation/ifix/version61/Subsystems/ESIG/content/esig\_examining\_the\_electronic\_signature\_dialog\_box.htm](https://www.ge.com/digital/documentation/ifix/version61/Subsystems/ESIG/content/esig_examining_the_electronic_signature_dialog_box.htm)  
The link from @jmonter is broken.

---

<div class="post-metadata">

**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\
**Post date:** [February 9, 2020, 9:28pm UTC](https://forum.inductiveautomation.com/t/electronic-signatures-and-change-management/29413/7 "2020-02-09T21:28:54Z")

</div>

> [@witman](#):
>
> The requirement is for two separate users to confirm the specific action:

Gotcha, I missed the part on a separate verification.