Versions Compared

Version Old Version 30 New Version 31
Changes made by

Larry Talley - NOAA Federal (Unlicensed)

Larry Talley - NOAA Federal (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • We reviewed the Principles Distinction
    Panel
    • Move on despite ambiguity
    • Listen as allies
    • Get to the point
    • Give criticism with upgrades
    • Finish each part
  • We went over the team introductions.
    Panel
    • Themes:
      • There is a larger population of people who need a solution than we thought
      • A lot of expertise
      • A strong desire to get things done.
      • Relatively limited amount of time for people.
      • Good representation across regions, but missing someone from Northeast
      • We could use a real Fisheries person.
        • A regulation writer, someone who has done an EIS, NEPA, FMP (Fisheries Management Plan).
          • We should look at PFMC - Pacific Fisheries Management Council
            (Dayna will look into that)
    • NOTES:
      • Distribute periodic updates for stakeholders (weekly or bi-weekly summaries of progress)
      • We should get someone from the North East.
Panel
  • Susan's Presentation (See slides)
    • The goals of her project are
      • Consistent national online system for permit applications/renewals/customer service/management
      • They need to find out who the participants are, who their partners are, what they need, etc.
    • Currently not everything is accepted by the national permits team.
    • The technical is the easiest part.
    • The presentation:
      • Most of our users are Existing Permit Owners
      • Should we collect SSNs?
        • NMS has the authority and responsibility to collection SSNs during the permit application process , but local practice is affected by concerns for data protection.
        • We need to examine and document the business risks of not collecting SSNs.
        • SSA will validate the relationship between names and SSNs on a yes/no basis.
        • We need the "green light" from general council in order to clarify authority for NMFS to collect SSNs.
        • Balsinger may need to clarify the legal mandate.
      • The permits are a many to many setup. Many people can own a single permit and a single person can own many permits.
      • It is difficult to track our customers and the agents who are acting on behalf of others.
      • It is then difficult to track exactly who is who and who is participating because of the brokers and the agents involved.
      • Right now we verify identification by sending information through the mail.
      • This could be avoided by using SSNs - it would simplify things.
      • Do we have enough top-level authority to help push buy-in by all the little players?
      • There are people who are able to opt out.
      • For the "signing ceremony" language - it would work better to have the GPEA language than the E-Signature Act language.
  • Timeline
    • Steve reviewed the project timeline.
    • We are currently at the beginning of the second phase in Susan's life-cycle road map.
    • For the alternatives analysis - we can think of this more as an effective due diligence rather than an exhaustive list of alternatives.
      • We should at least mention the heavy weight tech options we are ruling out (at least 1 or 2) and one on the very light weight side that we are also ruling out.
      • Alternatives
        • Light-credit card or permit example (Tuna? where there is no ID proofing currently)
        • NPS-username password
        • EAuthentication
    • We do need to consider the digital divide.
    • The people who are approving (CIO, CG, CGEL, etc) will be looking at this for the first time.
    • We need to figure out who is important to engage in with this process.
    • We should have at least 2 very different environments.
      • Permits, Log Books, Dealer Reports/Fish Tickets.
    • Different solutions for trusted relationships and un-trusted relationships.
    • There is a lot of regional variability.
    • The alternatives are both technology and business process
  • Risk Assessment and Cost Benefit Analysis
    • We will need a lot of help is this section from the larger group.
  • Implementation Plan
    • This will be the next steps document
  • Stakeholder Grid and the Wiki Overview
  • Next Steps
    Tasklist
    Action Items
    Action Items
    ||Completed||Priority||Locked||CreatedDate||CompletedDate||Assignee||Name||
|F|M|F|1216078914538|          |ltalley|Add Leadership Question to the Stakeholder Grid - Larry|
|T|M|F|1216078924308|1216079038418|ltalley|Look for an East Coast person through John Witzig - Larry|
|F|M|F|1216078932719|          |ltalley|Investigate SSNs for her business plan - Susan|
|F|M|F|1216078940646|          |ltalley|Does anyone use the adobe system as a means of authentication? - Steve and Larry|
|F|M|F|1216078950718|          |ltalley|Should we start up a standing meeting fortnightly? - Steve and Larry|
|T|M|F|1216078957672|1216079044845|ltalley|Setup the new usernames - Larry|
|F|M|F|1216078966525|          |ltalley|Link for the FISH! Video - Jared|
|F|M|F|1216078974101|          |ltalley|Set date and time for next meeting to discuss stakeholder analysis grid and draft communications plan - Larry and Steve|
|F|M|F|1216078984370|          |ltalley|Stakeholder Analysis Input Due on Friday, July 18 - Everyone|
  • Concluding Thoughts
    • What is the timeline on Susan's plan being approved?
      • ASAP - within the next two weeks.
    • Larry -
      • This is a great group
      • I'm "jazzed" about where we are and I think we can make it happen.
      • It helps to have people with concrete experience.
    • Thank you to everyone.

...