The December 2022 issue of IEEE Spectrum is here!

Close bar

One Major IT Problem in Pennsylvania Fixed, Another in Sweden Persists

Major dependence on one IT supplier in Sweden highlights risk

2 min read
One Major IT Problem in Pennsylvania Fixed, Another in Sweden Persists

There were news reports today stating that the glitch plaguing the US state of Pennsylvania's Department of Labor and Industry computer system for over two weeks has finally been fixed. Since the 13th of November, some 13,000 Pennsylvanians eligible for extended unemployment checks have not been receiving them, according to this WGAL TV news video report. The WGAL report said state officials claimed that there was no way that the missing checks could be manually written, and according to a WGAL article on its web site Tuesday, state officials also indicated that "people will have to live without benefits" until the state could figure out what was causing the glitch and fix it.

Fortunately, WGAL reported today that state officials said the computer issue was now resolved, and that back payments "... should be processed by Friday and at the latest show up in accounts early next week." Exactly what the computer glitch was has not been explained.

In 2009, some 100,000 Pennsylvanians on unemployment were affected by another Department of Labor and Industry computer system glitch. The state is currently in the midst of working on a new computer system to replace the current one which no longer looks fit for purpose, according to this WTAE TVreport.

In similar "glitch-related" news, some 50 Swedish organizations, ranging from Stockholm's city government to the country's largest pharmacy chain Apoteket and even the state-owned bank SBAB, have been affected by an unspecified computer hardware problem at the Finnish IT services provider Tieto, according to Stockholm News and Reuters news stories. Apparently, Tieto provides Internet and intranet services to the affected organizations. 

Tieto, which says that it's "... the leading IT service company in Northern Europe" has not been able to provide an estimate of when the problem will be fixed. The Reuters article states the IT company may be facing millions in damages because of the operational impacts on the affected organizations.

The Stockholm News story states that the Swedish Authority for Civil Contingencies (MSB) is in discussions with the organizations about the on-going problem. It quotes Richard Oehm, Head of Information Security at the MSB, as saying:

"There is a big risk when using more and more of the same services, but the responsibility to make a proper risk and vulnerability assessment lies on the individual authority or company."

If anyone has more insight about the Tieto situation, please comment about it. News stories in English on the situation are sparse in both numbers and details, which is a bit surprising, given the number and size of organizations affected and the problem's duration.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}