Charter for eSignature Team

is not a deliverable but is published here to establish context for the other information.

• Charter

  The purpose of this project is to establish an approved process for implementing eSignatures for use with electronic reporting systems. This project will review the requirements of the Agency's eSignatures policy (32-110) and procedural directive (32-110-01), evaluate alternative methods and procedures, and develop a standard approach for implementing eSignatures for electronic reporting. This project is a planning, design, and plan approval exercise, and this project is not a system development process resulting in implemented production systems. Of course a development process (and/or procurement) is eventually intended, but it is not part of this phase.

  • What will we have accomplished by January 2009?
    We will have secured approval for an eSignature implementation as specified in the policy and procedural directive.
  • What we will have not done by January 2009?
    We will not have done software requirements specifications, detailed design, data models, programming, testing, implementation, or other systems development work that would typically follow a conceptual design.
  • What does success look like in January 2009?
    • We understand eSignature opportunities and challenges, preferably understanding these in more than one context (for example, in the context of an eLogbook, and in the context of a permit application)
    • We have secured approval for our selected solution through an approved Business Plan, including a Justification, Requirements, Risk Assessment, Cost Benefit Analysis, and Implementation Plan Outline
    • Our documents provide enough detail to serve as a conceptual design and the basis for a software requirements specification and/or procurement specifications