Hosting on AIMS - Intros & SOPs

Date

Jan 31, 2023

Attendees

  • @Alissa McShane

  • @Keith Reynolds (Unlicensed)

  • @Paul Jankauskas

  • @John Reaves

  • @Marty Sibley

  • Kate Beagle

  • Nydia Palacios

Invited

  • @Emma Sudduth

  • @dari.shirazi@aphl.org

  • @Eduardo Gonzalez Loumiet

  • @Michelle Meigs

Goals

  • review documentation

  • request any missing gaps

  • discuss best practices for hosting the GAIHN-HAI project on AIMS

Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5

Introductions

All

5

GAIHN-HAI overview

@Paul Jankauskas

40

review documentation, request any missing gaps, discuss best practices for hosting the GAIHN-HAI project on AIMS

@Alissa McShane

  • Described the two documents shared and how they can be helpful in the development, production readiness, and post-production phases

  • Marty and John are in progress on external partner developer documentation for environment information, Devops expectations, hardware, network, system support, etc...

  • Discussed possible technical and project meeting cadence

    • Assumption is 1x/week technical will suffice and that PMO reporting bi-weekly can mostly cover project level cadence, but if additional meetings or working sessions are required, they can be scheduled or factored in

    • Alissa will follow up on the key resources' (Bryan Parsons, Ryan Key) bandwidth to gauge any initial resourcing concerns

    • Alissa will identify if we can assign a project coordinator from Ruvos for help with scheduling and jira hygiene

  • Reminder to get NARF background check working for 2 Deloitte devs and anyone who will require Jira, Smartsheet, or other network/application access. Any level of check will do, just need details and proof of completion, and CDC credentials will cover this requirement.

  • Kate is already set up with PMO bi-weekly reporting

  • Alissa to work with Deaw to have a Jira project set up for GAIHN-HAI

    • We can update permissions and add all required personnel once everyone is onboarded

Action items

@Alissa McShane will follow up on the key resources' (Bryan Parsons, Ryan Key) bandwidth to gauge any initial resourcing concerns
@Alissa McShane will identify if we can assign a project coordinator from Ruvos for help with scheduling and jira hygiene
@Alissa McShane to work with Deaw to have a Jira project set up for GAIHN-HAI (We can update permissions and add all required personnel once everyone is onboarded)
Kate / @Paul Jankauskas to submit NARF with background check for 2 Deloitte devs and anyone who will require Jira, Smartsheet, or other network/application access (link to AIMS Service Desk portal: https://aphlinformatics.atlassian.net/servicedesk/customer/portal/3 )

Quick decisions not requiring context or tracking

For quick, smaller decisions that do not require extra context or formal tracking, use the “Add a decision…” function here.

Decisions requiring context or tracking

For decisions that require more context (e.g., documentation of discussion, options considered) and/or tracking, use the decision template to capture more information.