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

« Previous Version 6 Next »

Background

Under Sections 1703 and 1704 of the Government Paperwork Elimination Act (GPEA)1, Executive agencies are required to provide for the use and acceptance of electronic signatures. It is NMFS' policy to use and accept electronic signatures whenever possible and to encourage agency programs to provide individuals or entities with the option of submitting information or transacting business with the agency electronically. During the Electronic Reporting Planning Workshop held in July 2007, it was determined that an approved design and implementation plan for electronic reporting eSignature would be of significant benefit to multiple regions. A project has been initiated to develop an approved design and implementation plan for electronic reporting system(s) eSignature, as well as establishing a template and process for future eSignature initiatives.

The most significant challenge of an eSignature project is creating alignment among many diverse stakeholders. Electronic signatures raise new and cross-cutting issues throughout an organization. General Council and Enforcement have strong interests in enforceability and admissibility; executives have strong interests in agency reputation; Information Technology have strong interests in information security; line of business staff have strong interests in usability, support and customer satisfaction. These groups have different perspectives but all share ownership in an eSignature solution. While often viewed as a technology issue, in reality eSignature initiatives are organizational change efforts where the technology is the easiest part of the project.

The primary analytical challenge for eSignature projects is how to identify and value risks and related mitigations so that an organization can have a fact-based, dispassionate discussion of the relative merits of policy and implementation options. Frequently, there are calls for absolute security or characterizations of great risks that, in reality, have little likelihood of occurring. Part of the problem is that competing interests in eSignature projects often paint choices as black and white, when in fact the analysis requires distinguishing among shades of gray. The lack of specificity of federal law and policy around eSignatures can have a paralyzing effect on organizations. There is no one right way and federal officials have to exercise judgment on how craft and then implement policy with oftentimes murky and incomplete data.

The purpose of this contract is to provide the NMFS eSignature project team with specialized expertise and experience with respect to citizen-to-government eSignature design and implementation.

Objectives of Contract
  • Advising the project team with respect to identifying, characterizing, and communicating with stakeholders
  • Advising the project team with respect to alternative approaches
  • Reviewing project outlines, drafts, and presentations
  • Providing context for the proposed solution, including comparisons between the proposed solution and prior art, and/or analysis with respect to industry norms or best practices
  • Assistance developing and presenting the solution to stakeholders
Scope of Work

The contractor will participate in teleconferences, email correspondence, and other online collaborative systems to guide the project team to a successful project conclusion. The contractor will provide advice based on his/her successful experience with similar projects; evaluate circumstances

Period of Performance
Contractor Performance Requirements
Specific Objectives/Tasks:
Task 1:
  • Advising the project team with respect to identifying, characterizing, and communicating with stakeholders
Task 2:
  • Advising the project team with respect to alternative approaches
Task 3:
  • Reviewing project outlines, drafts, and presentations, providing context for the proposed solution, including comparisons between the proposed solution and prior art, and/or analysis with respect to industry norms or best practices
Task 4:
  • Assistance developing and presenting the solution to stakeholders
Contract Deliverables and Deadline for Each:
Other Critical Factors
  • Key personnel The contractor shall provide an analyst possessing direct experience leading an electronic signature design in an citizen-to-government context. The contractor must have a track record that clearly demonstrates the skills, knowledge and training to satisfactorily perform the services required under this contract.
  • This is a non-personal service contract; personnel performing work under this contract are employees of the contractor and are not employees of the Government.
  • Work Location: The work will occur at the contractor's facilities, with travel as necessary to coordinate work with other NMFS components.
  • Hours of Operation: Normal operating hours are expected to be 8:00 AM to 5:00 PM Pacific Local Time Monday through Friday, except for Federal holidays.
  • Safety: The contractor will provide for the safety and protection of staff employed in support of this contract. The contractor will be required to complete any NOAA required safety training courses in compliance with NOAA policy.
  • Insurance Coverage: The contractor is solely responsible for their own health, workmen's compensation and unemployment insurance as well as applicable social security, local, state, and federal taxes.
  • Site Security: Personnel performing work under this contract will be required to pass NOAA security clearances for contractors.
  • Computers/Software: The contractor is solely responsible for providing any necessary computers/software and office supplies.
Budget

a.

Salary and Wages

 

b.

Personnel Benefits

 

c.

Contractual Services

$35,000

d.

Goods, Supplies and Services

 

e.

Travel Expenses

 

f.

Overhead @ 15%

 

g.

Equipment

 

Total Budget

 

$35,000

  • No labels