Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

<Briefly describe the project background, if applicable.>
The purpose of this project is to establish an approved process for implementing esignatures for use with electronic reporting systems. During the Electronic Reporting Planning Workshop held in July 2007, it was determined that a clear process for implementing esignatures for electronic reporting would be of significant benefit to multiple regions. This project will review the requirements of the Agency's esignature policy (32-110), evaluate existing methods and procedures, and develop a standard approach for implementing esignatures for electronic reporting.

    1. Objectives
      <Briefly describe objectives for establishing the project. How does this project directly relate to the mission, vision, goals and objectives of the FIS Program? Why is the project important? What are the benefits and intended outcomes?>
      The following lists the major objectives to be accomplished by this project in FY08:
    • Enable electronic signatures for certification and enforcement of electronic reporting
    • Establish standards for the enrollment and authentication of fishery participant's use of electronic reporting
    1. Management Approach*
    2. Resource Management
      <Determine the list of project participants, including their roles and responsibilities, and the name of each person who will be fulfilling each role. As a minimum, you will need to define the Project Sponsor and/or stakeholders, Project Manager, and Project Point of Contact.
      In addition you may have one or more of the following parties in your project structure: Project Team, Reference Groups, Working Groups, and Consultants. If these participants are critical to your project, please list them as well.>
      The following table identifies key project members who will contribute to the planning and execution of this project.
      Table 1: Project Members

      Project Role

      Name

      Responsibilities

      Project Sponsor

      Al Coan (SW)

      PMT Liaison

      Project Manager

      Larry Talley (AK)

      Day-to-day management

      Project Point of Contact

      Larry Talley (AK)

       

      Team Members

      Richard Kang (NW)
      Jason Rueter (SE)
      Karen Sender (PI)
      TBD (GCEL)
      TBD (OLE)

      Project team members

      Contractor

      TBD

      Project execution support

    1. Communication Management
      <Provide a summary of the overall key communication and management issues for the project, concentrating on what will contribute to the project's success or where a lack of communication can lead to failure. Modify the example as needed for your project.>
      The following strategies have been established to promote effective communication within this project.
  1. The Project Manager will present project status to the Project Sponsors on a monthly basis; however, ad hoc meetings will be established at the Project Manager's discretion as issues or changes arise.
  2. The Project Manager will provide written meeting minutes for all meetings relevant to the project and distribute to attendees, and to other participants upon request.
  3. The Project Sponsors will be notified via e-mail of all urgent issues. Issue notification will include a description of the issue, time constraints, possible impacts, and resolutions if proposed.
  4. The Project Team will have weekly update/status meetings to review completed tasks and determine current work priorities. Minutes will be produced for all meetings.
  5. All electronic Project Documents will be maintained in by the Project Manager and stored for reference in QuickPlace.
    1. http://www.projectmanagement.tas.gov.au/pm_templates/pm994_smlbusinessplanv1.0.htmRisk Management
      <A risk analysis should be undertaken upon commencement of the project and regularly reviewed throughout the project life cycle.
      Include a summary of the major risks, mitigation strategies, estimated additional costs to deploy the strategies (these should be included in the budget) and an overall assessment as to the level of risk associated with the project. Also discuss how risks will be managed in relation to risk identification, reviews, and reporting.>
      Risks will be determined during initial planning for the project.
  • *# *## Project Estimates*
    1. Schedule and Milestones
      <List the project output or deliverables. These may be new or modified products, services, documents, or management practices that need to be implemented to meet each identified outcome.>
      List the milestones and major activities for the project. Milestones are indicated by a blank scheduled start date, these are the dates identified during the initial planning stage used to monitor progress of the project. Activities in the predecessor column must be completed prior to the activity commencing.
      For this task, you may use Microsoft Project, if this software is available.>
      The following presents a schedule of major tasks, activities, and milestones for the project.
      Table 3: Project Schedule - Major Tasks and Milestones

      ID

      Activity Description

      Planned Start

      Planned Finish

      Predecessor

      1

      Task 1: Analyze existing esignature policy

      MM/DD/YY

      MM/DD/YY

       

      2

      Activity 1.1: Identify requirements

       

       

       

      3

      Activity 1.2: Evaluate implications for esignature, user enrollment, authentication

       

       

       

      4

      Task 2: Review existing approaches to implementing esignature

       

       

       

      5

      Task 3: Establish draft esignature approach for electronic reporting

       

       

       

      6

      Deliverable: Draft ER Esignature Approach

       

       

      5

      7

      Task 4: Review and approve esignature approach

       

       

       

      8

      Activity 4.1: Conduct legal, PRA review

       

       

       

      9

      Activity 4.2: Conduct IT security, other reviews

       

       

       

      10

      Task 5: Publish approved esignature approach

       

       

       

      11

      Deliverable: Final Approved Esignature Approach

       

       

      10

    1.  
    2. Cost Estimates
      <Summarize the project's budget and expected overall budget projections.
      Provide a detailed list of resourcing requirements, for example human resources, IT equipment, information requirements, special equipment, etc. Use the following table to calculate the project cost estimates. Please note that the items listed in the Project Needs column are provided as examples only. Modify the list as needed to suit the specific needs of the project.>

Instructions: To calculate costs, place the totals for each category in the Total column on the right. To update the grand Total, click the last cell in the Total column. When the tab turns gray, right click and select the "Update Field" option.)

The following table presents the estimated funding needed to execute the project and create the deliverables identified in Section 3.1.
Table 5: Cost Estimates

Project Need

Description

Estimated Cost, per item

Date Needed

Total

Hardware

 

 

 

 

Software

 

 

 

 

License Fees

 

 

 

 

Service Contract or Maintenance Fees

 

 

 

 

Testing Equipment or Facilities

 

 

 

 

* Additional Project Staff

 

 

 

 

Consultants

PMO management support
Other Consultant

 

Project start

2,000

50,000

Training

 

 

 

 

Project-specific Travel

Meetings

 

TBD

23,000

Administrative Support Fees

 

 

 

 

Other

 

 

 

 

*Grand TOTAL*

$75,000.00

FY08 Proposal eReporting - eSignature

i

Page 5

Page 6

  • No labels