ETS: Sunapsis Project Team Meeting

 Sunapsis Project Meeting Minutes

October 20, 2015 3:00-4:00 p.m.

Attendees:   Matt Reynolds, Sherri Mines, Joseph Ng, Chien Shih, Mahmood Hasan, Jerrick Woo, Ryan Anthony, Jim Clow, Katia Rostam Yazdi, Linda KoyamaOn-site Visit

  1. On-Site Visit Progress Update 
    1. Residency status and country of citizenship fields mapping issue has been resolved.
    2. Validated the data feed.
    3. Will enable system alerts later today.
    4. Will review how Banner data compares with Sevis compliance.
    5. Smoothest site visit so far.
    6. Tomorrow's user training will take 4-6 hours starting at 9:30 a.m. in D270.
    7. Will require ongoing term configurations (Sherri will be responsible).
    8. When the Sunnyvale campus is finished, it will need Sevis certification.

  2. Sunapsis Support during the implementation phase
      1. Answers any questions setting up the product
      2. Understanding the API for the data feed
      3. Insuring that the data file loads correctly
      4. Offering suggested practices
  3. After Go Live
      1. Will go live with Sevis tomorrow, 10/21/15; FSAAtlas will no longer be used.
      2. We should expect a rough couple of months dealing with the data problems (red alerts)
      3. Diffferent types of alerts (Sevis alerts, Banner alerts and Sunapsis alerts with different threat levels)
      4. May involve Banner standards for data entry
      5. May need to contact the data feed team for help (Sherri will initiate contact with Sunapsis and if  ETS is needed, Sherri will submit a KACE ticket).  Sevis has strict data requirements that Banner doesn't necessarily enforce.
      6. Sunapsis Support Team will help with any non-customized feature.
  4. Patches
    1. Because Sunapsis and Sevis are evolving products, we should expect patches, or hot fixes approximately once a month
    2. Ideally ETS will install them as they are released to our test instance and once tested, moved to prod.  Sunapsis does not have access to our servers.
    3. Every email will list whether the patch is cumulative or not.
    4. Sunapsis now does checks and balances to ensure we are applying them in the proper order.
    5. Conference call can be scheduled if we need help with applying patches.
  5. ETS does not need to dedicate someone to monitor the logs.  The Sunapsis administrator (Sherri or if she's not available, Joseph) will be alerted by email when there are problems (i.e.  data feed didn't run).  If it can't be resolved locally, a ticket can be submitted with Sunapsis support.
  6. Next step:
      1. Go Live for Sevis targeted for Wednesday, 10/21/15.   Will stop FSAAtlas to avoid  
      2. All RTI will be done through Sunapsis; no longer using a direct link to access RTI.  
      3. We need to upload the same security certificate for De Anza to begin SEVIS batching within Sunapsis.
      4. Daily banner data load of all F-1 students is fed into Sunapsis, Sunapsis runs its scripts to update the data, and a batch is created based on those changes which is approved by the Sunapsis administrators that is fed into Sevis.   Until this is ready to go live, batches can be manually created and manual changes can be made via RTI.
      5. There is an Sevis compliance emergency hotline but most things are fine with a 2 day response time window.
  7. Goal for eforms to be built by Feb 2016.