|
New functionality has been added to SSIS for Adult Protection Services-Afterhours Emergency Protective Services Email Notifications. Click here for details. For recipients of the afterhours emails to view the intake in SSIS under the Unassigned Intake Log they must be assigned to the “SSIS Default” under Department Assignments and Unit Assignments within SSIS Administration. This document discusses how to Access Users of SSIS. Departments, Units and the SSIS Default are on pages 24 through 26.
Effective December 1, 2021, the data clean up error "Expectant/Parenting Youth information or review is required for youth in continuous placement" will no longer appear when attempting to close a workgroup. If issues continue after the v21.4 Statewide Release, contact the SSIS Help Desk.
SSIS Statewide Release v21.4 installation will begin Tuesday, November 30 at 4:30 p.m. for all agencies excluding v21.4 pilot agencies. All agency users should be logged out of SSIS by 4:30 p.m. November 30. Expected outage time is approximately two hours. Contact the SSIS Help Desk for assistance, if needed.
SSIS v21.4 Release notes, recorded webinars, and prior Release information can be found on the SSIS Resource page.
A new SSIS Mentor Manual, created for all mentors and coordinators, has been posted to the SSIS Resource page. The manual provides guidance on SSIS business and technical processes including password resets, the enhancement request process, and Statewide releases.
The Minnesota Department of Human Services would like your input on how to improve the online learning experience of the SSIS Essentials curriculum.
A short survey, which should take five to ten minutes to complete, has been designed to gather information from SSIS users. Feedback gathered will be used in shaping, planning, and redesigning the SSIS Essentials eLearning curriculum as well as future courses available. The survey will be open until December 3, 2021.
Minnesota Department of Human Services staff thank you for continuing to report issues with the Social Service Information System (SSIS) and impacts those issues have on your ability to complete agency work. SSIS Help Desk staff are closely tracking reports from county/Tribal users, and continuing to work closely with MNIT partners on resolving issues resulting in unacceptable slowness. The identified issues, not isolated to one IT function, include databases, infrastructure, and Virtual Desktop Infrastructure (VDI) changes. MNIT leadership designated resolution of these issues as a priority for the various MNIT teams working on solutions to improve user experiences. MNIT staff are reviewing reported experiences of users, as well as working to identify and correct components of applications having issues. While some efforts will result in immediate relief for users; others will require more time and effort.
Total number of reports to the SSIS HelpDesk related to slowness have decreased in each of the past two weeks, although significant impact in some agencies have been reported. Please continue to report issues you are experiencing with SSIS, and include specific details. We will continue to track calls and may ask specific agency mentors/workers to report any incidents of lagging.
Technical efforts to identify and resolve issues specific to SSIS applications, and MAARC for county and Tribal agencies within the past week
1. The SSIS Help desk is monitoring reports related to system performance. Help Desk staff continue to reach out to various agencies for detailed information about slowness issues.
2. MNIT monitoring the Horizon Servers at various times of the day for issues continues.
3. Three of five new application servers have been added into the pool.
- Found that the number of critical Horizon servers has decreased below the 50 percent mark and hovers around 35 – 45 percent throughout the day since the new application servers have been added.
4. MNIT Enterprise Horizon team found three host servers causing issues in production and removed them from the pool for analysis.
a. One host had network flapping on its management port. Horizon team is still researching.
b. One host server locked up. Reason not yet determined. Removed from the pool and rebooted and symptoms disappeared. This was put back in the pool on 11/17/2021.
c. One host server’s mezzanine card failed. Ordered a replacement.
5. MNIT Enterprise networking team monitoring
a. We have been monitoring memory / CPU usage on the horizon servers and have found something interesting.
- The CPU usage is extremely high most of the day. Ideally the CPU should not surpass 80% of available processing. We are frequently at 100%.
- The fast memory (RAM) is not being utilized effectively by the operating system.
- Finding the application is reading from disk memory much more than reading from fast memory (RAM). Reading from disk memory is significantly slower than reading from RAM (1000 times).
- The SSIS team is looking at making a modification to the application to force it to use more fast memory (RAM) vs disk memory to run. This will require testing.
6. Continued testing with Scott and Washington counties with a new Horizon environment.
a. Working to increase users in each agency on the new server then moving the rest of the users.
- Minimal testing has been completed. Scott County representative reported progress with users logging in and beginning to pilot the new server farm.
7. Conducting analysis regarding slowness regarding the RTF editor, including possible removal of the HYDRA component from SSIS. Not a quick fix to this issue; it will take several months and significant work to remove and replace HYDRA. Implementing the change will require a release.
8. Building a Baseline Network timing diagram for MAARC. This allows for comparison with the baseline when reports of latency in MAARC.
9. MICROSOFT review of the system, specifically servers within the system.
The Annual Preferences presentation and accompanying script will provide guidance in establishing SSIS agency preferences for CY 2022.
If you have any questions, please contact the SSIS Help Desk.
Subscribe to the SSIS Update
|
