E-signatures
E-signatures are used to sign off documents for legal purposes or strict internal control, following the standards of organizations like eIDAS. Example documents are Bills of Material, Shipments, and Payment batches.
You can specify these qualifications for documents:
- The situations in which an e-signature is required or triggered
- The person who must sign off, based on the business case
The document data with the signature is stored, separately from the active LN applications, in the E-signatures table in LN Tools. Because it is stored separately, data security is guaranteed. The data, including the related data such as names and descriptions, can never be changed.
To meet legal obligations, the stored data with the e-signature can be audited by certifying institutions such as the FAA or FDA. Internal control or auditors can also run audits to meet internal procedures, depending on internal business cases.
The data in e-signatures can bypass the GDPR regulations, as the name of the person who signs is not anonymized. Any other name or description in the e-signature is also not anonymized or erased. The data for e-signatures cannot be archived or removed.
This table shows the sessions with an e-signature and the triggers:
Session | Trigger |
---|---|
Production Model | Approval |
Production Bill of Material | Approval |
Job Shop Bill of Material | Approval |
Job Shop Routing | Approval |
Production Order | Release |
Service Order | Completion |
Work Order | Completion |
Order Inspection | Closure |
Non-Conformance | Disposition |
Non-Conformance | Closure |
Conformance Document | Certification |
Corrective Action Plan | Closure |
Corrective Action Plan | Completion |
Receipt | Confirmation |
Receipt | Correction |
Shipment | Confirmation |
Trade Compliance Check Results | Override |
Bid | Approval |
Budget (LN Project) | Adjustment |
Payment Batch | Approval |
Direct Debit Batch | Approval |
Task | Approval |
Task | Rejection |