%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 >> >> /MediaBox [0.000 0.000 612.000 792.000] >> endobj 4 0 obj [/PDF /Text ] endobj 5 0 obj << /Creator (DOMPDF) /CreationDate (D:20240519062017+00'00') /ModDate (D:20240519062017+00'00') /Title (IT-artikels) >> endobj 6 0 obj << /Type /Page /Parent 3 0 R /Contents 7 0 R >> endobj 7 0 obj << /Length 3866 >> 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 213.838 521.469 532.896 re f 0.773 0.773 0.773 RG 0.75 w 0 J [ ] 0 d 45.641 214.213 520.719 532.146 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 [(SAFECOM – THE FACTS AND THE FUTURE)] TJ ET 0.400 0.400 0.400 rg BT 61.016 564.033 Td /F3 9.0 Tf [(The mere mention of the word )] TJ ET BT 183.569 564.033 Td /F3 9.0 Tf [(Safecom )] TJ ET BT 221.585 564.033 Td /F3 9.0 Tf [(has been causing a combination of panic and frustration over the last few )] TJ ET BT 61.016 553.044 Td /F3 9.0 Tf [(months - and this just among IT staff. Just like you, our patient users on campus, we've been worn out by all the problems. )] TJ ET BT 61.016 542.055 Td /F3 9.0 Tf [(However, the good news is, after months of pulling our hair out, we're closer to a solution and the light at the end of the )] TJ ET BT 61.016 531.066 Td /F3 9.0 Tf [(tunnel is, indeed, not an oncoming train.)] TJ ET BT 61.016 511.077 Td /F3 9.0 Tf [(The first time we started seeing problems with Safecom was in September 2012. At this time the load on the printers )] TJ ET BT 61.016 500.088 Td /F3 9.0 Tf [(weren't as high as it was a fairly quiet time academically. By the end of the academic year the effect on end users, in )] TJ ET BT 61.016 489.099 Td /F3 9.0 Tf [(particular students, was prevalent.)] TJ ET BT 61.016 469.110 Td /F3 9.0 Tf [(The system we initially implemented was clearly not sufficient for a changing and growing environment. Both the )] TJ ET BT 61.016 458.121 Td /F3 9.0 Tf [(production environment and the product's attributes changed since the implementation \(new upgrades were also released\) )] TJ ET BT 61.016 447.132 Td /F3 9.0 Tf [(and consequently the system design wasn't optimal.)] TJ ET BT 61.016 427.143 Td /F3 9.0 Tf [(Keeping this in mind, there was decided to call in an international Safecom expert and also a local HP expert to advise us )] TJ ET BT 61.016 416.154 Td /F3 9.0 Tf [(on the current set up and situation. With the assistance of said experts and the IT team significant decisions were made )] TJ ET BT 61.016 405.165 Td /F3 9.0 Tf [(and plans put into place to resolve the situation as soon as possible.)] TJ ET BT 61.016 385.176 Td /F3 9.0 Tf [(Most of the suggested plan has been executed, but due to the fact that all printers on campus have to be upgraded with )] TJ ET BT 61.016 374.187 Td /F3 9.0 Tf [(new firmware, this is a time consuming exercise. However, a visible improvement has been noted when compared to the )] TJ ET BT 61.016 363.198 Td /F3 9.0 Tf [(previous quarter.)] TJ ET BT 61.016 343.209 Td /F3 9.0 Tf [(We are aware of certain issues that must still be resolved. IT is continuously coordinating and resolving the existing )] TJ ET BT 61.016 332.220 Td /F3 9.0 Tf [(challenges as fast as possible. These include the creation of more internal system capacity, a more efficient printer driver )] TJ ET BT 61.016 321.231 Td /F3 9.0 Tf [(able to generate smaller printing files, more stable printer firmware, implementing more stable Safecom software on each )] TJ ET BT 61.016 310.242 Td /F3 9.0 Tf [(printer and the optimal functioning of this whole configuration.)] TJ ET BT 61.016 290.253 Td /F3 9.0 Tf [(We appreciate staff and student's patience and invite you to report problems at your CUA manager or IT Sevice Centre.)] TJ ET BT 61.016 270.264 Td /F3 9.0 Tf [( )] TJ ET BT 61.016 250.275 Td /F3 9.0 Tf [( )] TJ ET BT 61.016 231.786 Td /F3 9.0 Tf [(Posted in:General | | 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 xref 0 11 0000000000 65535 f 0000000008 00000 n 0000000073 00000 n 0000000119 00000 n 0000000294 00000 n 0000000323 00000 n 0000000458 00000 n 0000000521 00000 n 0000004439 00000 n 0000004551 00000 n 0000004658 00000 n trailer << /Size 11 /Root 1 0 R /Info 5 0 R >> startxref 4774 %%EOF Safecom – the facts and the future « Informasietegnologie
Language:
SEARCH

  • Recent Posts

  • Categories

  • Archives

«
»

Safecom – the facts and the future

The mere mention of the word Safecom has been causing a combination of panic and frustration over the last few months – and this just among IT staff. Just like you, our patient users on campus, we’ve been worn out by all the problems. However, the good news is, after months of pulling our hair out, we’re closer to a solution and the light at the end of the tunnel is, indeed, not an oncoming train.

The first time we started seeing problems with Safecom was in September 2012. At this time the load on the printers weren’t as high as it was a fairly quiet time academically. By the end of the academic year the effect on end users, in particular students, was prevalent.

The system we initially implemented was clearly not sufficient for a changing and growing environment. Both the production environment and the product’s attributes changed since the implementation (new upgrades were also released) and consequently the system design wasn’t optimal.

Keeping this in mind, there was decided to call in an international Safecom expert and also a local HP expert to advise us on the current set up and situation. With the assistance of said experts and the IT team significant decisions were made and plans put into place to resolve the situation as soon as possible.

Most of the suggested plan has been executed, but due to the fact that all printers on campus have to be upgraded with new firmware, this is a time consuming exercise. However, a visible improvement has been noted when compared to the previous quarter.

We are aware of certain issues that must still be resolved. IT is continuously coordinating and resolving the existing challenges as fast as possible. These include the creation of more internal system capacity, a more efficient printer driver able to generate smaller printing files, more stable printer firmware, implementing more stable Safecom software on each printer and the optimal functioning of this whole configuration.

We appreciate staff and student’s patience and invite you to report problems at your CUA manager or IT Sevice Centre.

 

 

Email

This entry was posted on Friday, April 26th, 2013 at 1:01 pm and is filed under General. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

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.