24/7 NOC and shift models for mid-size colo

Reading order

Name the labour object before you name a logo. Write whether the file is on-site shift staff in the hall, a remote network-operations centre, contractor call-out, or only a monitoring platform. The parent workforce page already splits construction-peak jobs from standing operations. This page keeps that split because a 24/7 badge that does not name the object invents a roster.

Then name the rest clock. Section 13 writes eleven consecutive hours and the midnight-to-05:00 cell, with a nature-of-the-work exception. Section 13 a writes the eight-hour average for night workers over at most four months. Section 14 writes thirty-six hours of weekly rest and excludes off-site standby from that rest. Arbetsmiljöverket’s Working Hours Act page is the authority starting page for those sections. A remote NOC in another municipality does not delete those clocks for the people who still work nights.

Only then open the process paper and the operator PDFs as neighbouring files. EN 50600-3-1:2026 writes operations, incident, problem, change, capacity and availability processes and writes people management out of scope. The standards-and-certification page already owns the wider EN 50600 family. Microsoft’s 145 / 561 figures and the Academy’s nine months stay on the parent page as named-operator rows. They are not a mid-size colo headcount this register will invent.

• Name on-site shift, remote NOC, contractor or monitor before any headcount.
• Keep the eleven-hour rest clock off a 24/7 logo.
• EN 50600-3-1 writes people management out of scope.
• The parent page already owns Microsoft’s 145 / 561 rows.

What a 24/7 model actually is

A 24/7 model is a set of dated papers about who is awake, where they sit, and which rest clock they are on. It is not a logo. On-site shifts, a remote NOC and contractor call-out can run in the same week. Each still meets section 13’s eleven hours. Night workers still meet section 13 a’s eight-hour average. Weekly rest still meets section 14, and off-site standby still does not count as that rest. A slide that says “follow-the-sun” does not write those hours.

The midnight-to-05:00 cell is a statutory default, not a ban on halls. Section 13 allows the exception where the work must run in those hours because of its nature, the public’s need or other special circumstances. A colo hall can be that kind of work. The exception is not a headcount, and it is not a collective-agreement substitute that this page will invent. Arbetsmiljöverket’s page is guidance to the Act. It is not a shift roster for Kista or Akalla.

EN 50600-3-1:2026 is a process paper. The cited catalogue abstract writes an implemented strategy, implemented management, and implemented policies for operations and incident management among the conformance cells, and writes people management and financial management out of scope. This page will not extract a Swedish technician number from a process list. The campus-security page already owns EN 50600-2-5 as a security-systems paper. That paper is not a NOC roster either.

Mid-size colo is not a hyperscale campus PDF. Microsoft’s 145 current employees and 561 end-2026 projection name Gävle, Sandviken and Staffanstorp on the parent page. Meta’s Luleå careers page does not, in the cited text, publish a current headcount. Equinix, Digital Realty, Conapto and Bahnhof pages used in this register publish halls, not a 03:00 roster. Empty cells stay empty.

What named primary sources show

The Working Hours Act shows the eleven-hour rest, the midnight-to-05:00 cell and its exception, the eight-hour night-worker average over at most four months, the thirty-six-hour weekly rest and the standby exclusion. Arbetsmiljöverket’s page is the official starting commentary. EN 50600-3-1:2026 shows a process scope that excludes people management.

The parent workforce page already shows Microsoft’s 145 / 561 rows, the 5.3 million hours and more than 1,299 peak-construction jobs, and the nine-month Academy. Those rows are not reused here as a colo census. EN 50600-2-5 remains the security-systems paper on the campus-security page.

Related pages already in this register: workforce and skills, campus security, standards and certification, and local impact. A groundbreaking photo is not a roster.

A matrix instead of one 24/7 headcount

The table is a permission table. A filled cell is a claim the named URL can carry. An empty cell means this page will not invent the missing colo roster.

Do not treat EN 50600-3-1 as a headcount, and do not paste Microsoft’s 145 onto a mid-size colo.

Common misreads

The first misread is to treat a 24/7 logo as proof that someone is in the hall at 03:00. The second is to treat a remote NOC as an exemption from sections 13, 13 a and 14. The third is to treat off-site standby as weekly rest. The Act excludes it.

The fourth is to extract a headcount from EN 50600-3-1. The standard writes people management out of scope. The fifth is to paste Microsoft’s 145 onto a retail colo. The sixth is to treat the midnight-to-05:00 cell as a ban on night work in a hall. The same section writes the nature-of-the-work exception.

What to ask next

If a brief prints a mid-size colo headcount, ask which named URL uses that number for on-site shifts, a remote NOC or only a hyperscale PDF. If the URL only shows a process standard or a 24/7 logo, the brief has already left the source.

Then open the parent workforce page, the campus-security page and the standards page. Those pages already own the named-operator rows, the security-systems paper and the certification family. This page only asks whether the rest clock is named.

1. Is the object on-site shift, remote NOC, contractor or only a monitor?
2. Which Working Hours Act section is in play — 13, 13 a or 14?
3. Has off-site standby been counted as weekly rest?
4. Has EN 50600-3-1 been treated as a roster?
5. Has Microsoft’s 145 been pasted onto a mid-size colo?

What this does and does not prove

This page proves that Swedish primary sources already publish rest clocks for night and weekly work, and that EN 50600-3-1 is a process paper that excludes people management. It proves that Microsoft’s employment rows stay on the parent page.

It does not prove how many people a named colo employs at 03:00. It does not invent a statutory headcount. It does not treat a logo as a roster.

Empty cells stay empty. Until a later primary source names a Swedish colo’s shift model with a dated roster and a boundary, the model stays a method, not a census.