...
The contractor will participate in meetings, teleconferences, email correspondence, and other online collaborative systems to guide the project team to a successful project conclusion. The contractor will provide advice advise the project team based on his/her successful experience with similar projects, critique team work products, and facilitate stakeholder meetings. The contractor will contribute to and coordinate collaborative development of documents including a stakeholder communication plan, an analysis of alternative approaches to each of the constituent technical components, a risk assessment and cost benefit analysis, an implementation plan, and a final presentation to stakeholders.
PERIOD OF PERFORMANCE
May 1, 2008 through November 28, 2008.
...
- Monthly Itemized Resource Use Reports: The contractor will provide an itemized list of the work completed, the personnel involved in the work, and the number of hours and costs associated with each work component as appropriate.
- Staff Interactions: The contractor will meet/teleconference/correspond frequently with identified NMFS staff to discuss progress, problems, and review analysis.
- Contributing to and coordinating documents: The contractor will coordinate the development of project team documents. The contractor will work with the project team to assign writing responsibilities. The contractor will have primary responsibility for writing assignments where prior experience with eSignature systems is critical, while project team members will have primary responsibility for writing assignments where knowledge of NMFS mission, practices, and organization are critical. The contractor will work collaboratively with project team members to complete writing assignments and the contractor will coordinate the incorporation of multiple contributions into complete documents.
- Written Work Product Critiques: The contractor will provide written critiques of project outlines, draft documents, and presentations. These will be informal notes intended for internal team use.
...
Advise the project team with respect to identifying, characterizing, and communicating with stakeholders. Lead the team though a process to identify stakeholders and characterize them with respect to their interest in the outcome and their sensitive issues. Advise on Lead the team through the development of a stakeholder communications plan. Facilitate teleconferences and/or meetings with stakeholders.
...
Advise the project team with respect to risk assessment and cost benefit analysis. Based on experience and knowledge of the eSignature arena, direct and facilitate team research and analysis. Lead the team through the development of a risk assessment and cost benefit analysis per the procedural directive.
...
Task 3:
...
Advise the project team with respect to alternative technical approaches. Based on experience and knowledge of the eSignature arena, direct and facilitate team research and analysis. Connect team members with other practitioners in the eSignature field.
...
Task 3:
...
Reviewing project outlines, drafts, and presentations, providing context, comparisons with prior art, and/or analysis with respect to industry norms or best practicesLead the team through the development of an analysis of alternative technical approaches.
Task 4:
Assist in drafting final finalizing documents and presentations. Present the solution to stakeholders and participate in question and answer sessions.
CONTRACT DELIVERABLES AND DEADLINE FOR EACH:
- June 18, 2008 – Critique the A stakeholder communication plan which identifies stakeholders, the nature of their interest, their sensitive issues, stakeholder contacts, and how to keep each stakeholder informed and engaged.
- July 16, 2008 – Critique the An analysis of alternative approaches to each of the constituent components (see Conceptual Design Outline)
- Identity Assertion, Person Proofing and Registration
- User Interface and Flow and Signing Ceremony
- Binding Document to Identity, Document Integrity and Tamper Evident Packaging, and Audit Trails
- Application Programming Interface
- August 13, 2008 – Critique the A Risk Assessment and Cost Benefit Analysis prepared per the procedural directive
- September 17, 2008 – Critique the An Implementation Plan prepared per the procedural directive
- October 15, 2008 – Present preliminary results to stakeholders
- November 12, 2008 – Critique final project documents
...