%PDF-1.3 1 0 obj << /Type /Catalog /Outlines 2 0 R /Pages 3 0 R >> endobj 2 0 obj << /Type /Outlines /Count 0 >> endobj 3 0 obj << /Type /Pages /Kids [6 0 R ] /Count 1 /Resources << /ProcSet 4 0 R /Font << /F1 8 0 R /F2 9 0 R /F3 10 0 R /F4 11 0 R >> >> /MediaBox [0.000 0.000 612.000 792.000] >> endobj 4 0 obj [/PDF /Text ] endobj 5 0 obj << /Creator (DOMPDF) /CreationDate (D:20240517100239+00'00') /ModDate (D:20240517100239+00'00') /Title (IT-artikels) >> endobj 6 0 obj << /Type /Page /Parent 3 0 R /Annots [ 12 0 R ] /Contents 7 0 R >> endobj 7 0 obj << /Length 4793 >> stream 0.702 0.800 0.816 rg 34.016 34.016 543.969 723.969 re f 1.000 1.000 1.000 rg 45.266 147.904 521.469 598.830 re f 0.773 0.773 0.773 RG 0.75 w 0 J [ ] 0 d 45.641 148.279 520.719 598.080 re S 0.773 0.773 0.773 rg 61.016 617.359 m 550.984 617.359 l 550.984 618.109 l 61.016 618.109 l f 1.000 1.000 1.000 rg BT 278.868 698.693 Td /F1 10.5 Tf [(POST LIST)] TJ ET 0.200 0.200 0.200 rg BT 212.789 670.111 Td /F1 14.4 Tf [(INFORMASIETEGNOLOGIE)] TJ ET BT 221.824 643.466 Td /F1 11.7 Tf [(INFORMATION TECHNOLOGY)] TJ ET BT 61.016 583.841 Td /F1 14.4 Tf [(FEEDBACK ON THE SU ADMINISTRATION SYSTEM OUTAGE)] TJ ET 0.400 0.400 0.400 rg BT 61.016 564.033 Td /F3 9.0 Tf [(During the last week of April most of our staff and students were affected by a serious outage of core IT-related )] TJ ET BT 61.016 553.044 Td /F3 9.0 Tf [(administrative services and systems. The outage’s impact was widespread and it was handled with high urgency. Almost )] TJ ET BT 61.016 542.055 Td /F3 9.0 Tf [(all of the University’s administrative processes were negatively affected, due to the dependencies on the core Student )] TJ ET BT 61.016 531.066 Td /F3 9.0 Tf [(Information and Financial Systems, which were both unavailable.)] TJ ET BT 61.016 511.077 Td /F3 9.0 Tf [(The affected business processes included, but were not limited to: applications by prospective students, all financial )] TJ ET BT 61.016 500.088 Td /F3 9.0 Tf [(transactions and processes, all student and academic administration processes, approvals of facilities work orders, meal )] TJ ET BT 61.016 489.099 Td /F3 9.0 Tf [(bookings and orders in residences, business intelligence services, amongst others.)] TJ ET BT 61.016 469.110 Td /F3 9.0 Tf [(Services that were generally unaffected by the outage include: delivery of online learning content, email, Internet and )] TJ ET BT 61.016 458.121 Td /F3 9.0 Tf [(communications, Office365 collaboration services, physical access control and security services, amongst others.)] TJ ET BT 61.016 438.132 Td /F3 9.0 Tf [(We wish to thank our colleagues and students for their understanding and apologise for the frustrations that had to be )] TJ ET BT 61.016 427.143 Td /F3 9.0 Tf [(endured. We would also like to thank the technical teams at IT for their dedication and the long hours put in to restore )] TJ ET BT 61.016 416.154 Td /F3 9.0 Tf [(services.)] TJ ET BT 61.016 396.165 Td /F4 9.0 Tf [(When the outage manifested)] TJ ET BT 61.016 385.176 Td /F3 9.0 Tf [(The IT Division became aware of the incident at the beginning of the business day on Wednesday 24 April 2019.)] TJ ET BT 61.016 365.187 Td /F4 9.0 Tf [(When the outage was resolved)] TJ ET BT 61.016 354.198 Td /F3 9.0 Tf [(Services were gradually returned to operation overnight and were fully operational by 09h00 on Friday 26 April 2019. The )] TJ ET BT 61.016 343.209 Td /F3 9.0 Tf [(outage consequently lasted at least 48 hours.)] TJ ET BT 61.016 323.220 Td /F4 9.0 Tf [(Assurances)] TJ ET BT 61.016 312.231 Td /F3 9.0 Tf [(We want to assure the campus community that no data nor transactions were lost during the outage, although we do not )] TJ ET BT 61.016 301.242 Td /F3 9.0 Tf [(discount that some examples may come to light during stabilisation of services.)] TJ ET BT 61.016 281.253 Td /F4 9.0 Tf [(Next steps)] TJ ET BT 61.016 270.264 Td /F3 9.0 Tf [(1. Targeted communication with specifically affected functional and faculty partners will continue as necessary. )] TJ ET BT 61.016 259.275 Td /F3 9.0 Tf [(2. The next phase will be a thorough investigation to determine the root cause\(s\) of the outage. )] TJ ET BT 61.016 248.286 Td /F3 9.0 Tf [(3. The IT Division, in collaboration with its functional and faculty partners, will also review the handling of the incident and )] TJ ET BT 61.016 237.297 Td /F3 9.0 Tf [(use the lessons learnt to refine its standard operating procedures and its communications with the campus. )] TJ ET BT 61.016 226.308 Td /F3 9.0 Tf [(4. Once the causes of the outage have been established, the IT Division will account to the campus community in a )] TJ ET BT 61.016 215.319 Td /F3 9.0 Tf [(summary report that will also enumerate any actions and initiatives to minimise the risk of a re-occurrence.)] TJ ET BT 61.016 195.330 Td /F3 9.0 Tf [(Please be assured of the importance and urgency with which the IT Division attempts to prevent and respond to such )] TJ ET BT 61.016 184.341 Td /F3 9.0 Tf [(disruptions. Please report any further problems with any service on our )] TJ ET 0.373 0.169 0.255 rg BT 345.128 184.341 Td /F3 9.0 Tf [(ICT Partner Portal.)] TJ ET 0.373 0.169 0.255 RG 0.18 w 0 J [ ] 0 d 345.128 183.190 m 420.152 183.190 l S 0.400 0.400 0.400 rg BT 61.016 165.852 Td /F3 9.0 Tf [(Posted in:Connectivity | | With 0 comments)] TJ ET endstream endobj 8 0 obj << /Type /Font /Subtype /Type1 /Name /F1 /BaseFont /Helvetica-Bold /Encoding /WinAnsiEncoding >> endobj 9 0 obj << /Type /Font /Subtype /Type1 /Name /F2 /BaseFont /Helvetica /Encoding /WinAnsiEncoding >> endobj 10 0 obj << /Type /Font /Subtype /Type1 /Name /F3 /BaseFont /Helvetica-Oblique /Encoding /WinAnsiEncoding >> endobj 11 0 obj << /Type /Font /Subtype /Type1 /Name /F4 /BaseFont /Helvetica-BoldOblique /Encoding /WinAnsiEncoding >> endobj 12 0 obj << /Type /Annot /Subtype /Link /A 13 0 R /Border [0 0 0] /H /I /Rect [ 345.1277 183.5086 420.1517 192.6661 ] >> endobj 13 0 obj << /Type /Action /S /URI /URI (https://servicedesk.sun.ac.za) >> endobj xref 0 14 0000000000 65535 f 0000000008 00000 n 0000000073 00000 n 0000000119 00000 n 0000000305 00000 n 0000000334 00000 n 0000000469 00000 n 0000000551 00000 n 0000005396 00000 n 0000005508 00000 n 0000005615 00000 n 0000005731 00000 n 0000005851 00000 n 0000005979 00000 n trailer << /Size 14 /Root 1 0 R /Info 5 0 R >> startxref 6060 %%EOF Feedback on the SU Administration system outage « Informasietegnologie
Language:
SEARCH
  • Recent Posts

  • Categories

  • Archives

Feedback on the SU Administration system outage

During the last week of April most of our staff and students were affected by a serious outage of core IT-related administrative services and systems. The outage’s impact was widespread and it was handled with high urgency. Almost all of the University’s administrative processes were negatively affected, due to the dependencies on the core Student Information and Financial Systems, which were both unavailable.

The affected business processes included, but were not limited to: applications by prospective students, all financial transactions and processes, all student and academic administration processes, approvals of facilities work orders, meal bookings and orders in residences, business intelligence services, amongst others.

Services that were generally unaffected by the outage include: delivery of online learning content, email, Internet and communications, Office365 collaboration services, physical access control and security services, amongst others.

We wish to thank our colleagues and students for their understanding and apologise for the frustrations that had to be endured. We would also like to thank the technical teams at IT for their dedication and the long hours put in to restore services.

When the outage manifested
The IT Division became aware of the incident at the beginning of the business day on Wednesday 24 April 2019.

When the outage was resolved
Services were gradually returned to operation overnight and were fully operational by 09h00 on Friday 26 April 2019. The outage consequently lasted at least 48 hours.

Assurances
We want to assure the campus community that no data nor transactions were lost during the outage, although we do not discount that some examples may come to light during stabilisation of services.

Next steps
1. Targeted communication with specifically affected functional and faculty partners will continue as necessary.
2. The next phase will be a thorough investigation to determine the root cause(s) of the outage.
3. The IT Division, in collaboration with its functional and faculty partners, will also review the handling of the incident and use the lessons learnt to refine its standard operating procedures and its communications with the campus.
4. Once the causes of the outage have been established, the IT Division will account to the campus community in a summary report that will also enumerate any actions and initiatives to minimise the risk of a re-occurrence.

Please be assured of the importance and urgency with which the IT Division attempts to prevent and respond to such disruptions. Please report any further problems with any service on our ICT Partner Portal.

Comments are closed.

 

© 2013-2024 Disclaimer: The views and opinions expressed in this page are strictly those of the page author(s) and content contributor(s). The contents of this page have not been reviewed or approved by Stellenbosch University.