{"id":10426,"date":"2026-08-03T00:19:16","date_gmt":"2026-08-02T22:19:16","guid":{"rendered":"https:\/\/felusch.de\/?p=10426"},"modified":"2026-08-03T01:04:08","modified_gmt":"2026-08-02T23:04:08","slug":"bf-c-o-r-e-base-framework-for-converged-operations-reliable-event-it","status":"publish","type":"post","link":"https:\/\/felusch.de\/en\/bf-c-o-r-e-base-framework-for-converged-operations-reliable-event-it\/","title":{"rendered":"BF-C.O.R.E. \u2122 \u2013 Base Framework for Converged Operations & Reliable Event-IT"},"content":{"rendered":"

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Every system out there works. Just not with the one next to it.<\/strong><\/p>\n\n\n\n

Why I'm publishing BF-C.O.R.E.\u2122, and why the standard explicitly does not claim to be better than your in-house scheme.<\/p>\n\n\n\n

Let me start with a compliment, and I mean it: the network concepts I've seen across fifteen years of training in this industry are, for the most part, good. People thought them through. Things were decided, documented, taught. In some companies the in-house VLAN and IP scheme is so deeply ingrained that nobody looks anything up anymore \u2014 they're doing the address math in their heads while the case is still opening.<\/p>\n\n\n\n

And still, something is off. Because all of these good concepts stop at a line that has nothing to do with technology: the company boundary.<\/p>\n\n\n\n

The moment it tips<\/strong><\/p>\n\n\n\n

Inside the company, the world makes sense. But our industry doesn't work inside companies, it works in projects. And projects mix departments, vendors, dry-hire gear and above all: freelancers.<\/p>\n\n\n\n

A good freelancer works steadily for four or five companies. Five companies means five VLAN schemes, five IP logics, five ways of answering the same questions. Every switch means re-thinking, on top of the technical development none of us gets to pause. The capacity to permanently memorize somebody else's system is finite. That's not a weakness, that's being human.<\/p>\n\n\n\n

Anyone who has lived it knows the result: prep time that goes into understanding instead of building. Troubleshooting where only the two people who know the house system can help, not the ten who happen to be on site.<\/p>\n\n\n\n

The uncomfortable insight<\/strong><\/p>\n\n\n\n

Here comes the point that mattered most to me while writing the standard, and that would never survive in a marketing text if marketing were calling the shots:<\/p>\n\n\n\n

Technically, almost all of it is equivalent. Whether lighting sits in the 500 range or the 200 range, whether management addresses are derived one way or another, those are conventions, not laws of physics. One doesn't work better than the other.<\/p>\n\n\n\n

But that also means: the Tower of Babel our industry lives in isn't the result of differing technical requirements. It's the result of nobody ever proposing a common path worth following.<\/p>\n\n\n\n

And out of that comes something liberating: if many took the same path, nothing would get worse technically, but almost everything would get better organizationally.<\/p>\n\n\n\n

What would then be possible<\/strong><\/p>\n\n\n\n

Picture a meaningful share of the people on a project no longer having to relearn the basics, VLAN-to-department, IP math, management addressing, at every new client, but simply knowing them cold. The way the in-house crew knows its own system today, only everywhere.<\/p>\n\n\n\n

Setup would go faster because nobody is guessing. Troubleshooting would go faster because the colleague at the next console can read the network without someone explaining the house convention to him first. And dry hire would gain a new dimension: suppliers could deliver not just hardware that fits, but gear that fits logically, preconfigured to the scheme the production is running anyway. That widens the market for both sides and saves exactly the hours that are the most expensive today.<\/p>\n\n\n\n

The bar by which you may The bar you're welcome to hold me to me<\/strong><\/p>\n\n\n\n

A shared standard only works if it makes the decision-makers inside companies \u2014the very people who built their own system so far \u2014 no longer need to do that thinking themselves. Not through persuasion. But because everything they would have had to consider has already been considered.<\/p>\n\n\n\n

And it has to be memorable. Memorable enough that after a short break-in period you stop looking things up. A standard that only lives in a PDF isn't one; it has to fit into your memory, not into a binder.<\/p>\n\n\n\n

That's exactly the bar I wrote BF-C.O.R.E. against. Whether it clears it isn't mine to say \u2014 you decide that on site. The standard is open, free of charge, vendor-neutral, and we're currently developing the second layer together with the community.<\/p>\n\n\n\n

Base Framework for Converged Operations & Reliable Event-IT<\/strong><\/p>\n\n\n\n


Everything about the BF-C.O.R.E.\u2122 standard:<\/p>\n\n\n\n

Itforavs.com<\/a><\/p>\n\n\n\n

<\/p>","protected":false},"excerpt":{"rendered":"

Every system out there works. Just not with each other. Why I publish BF-C.O.R.E. \u2122 and why the standard explicitly does not claim to be better than your company concept. I'll start with a compliment, and it's serious: The network concepts I have seen in fifteen years of seminar work in this industry are for the most part good. Da [\u2026]<\/p>","protected":false},"author":5,"featured_media":10427,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_glsr_average":0,"_glsr_ranking":0,"_glsr_reviews":0,"_vp_format_video_url":"","_vp_image_focal_point":[],"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10426","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nicht-kategorisiert"],"_links":{"self":[{"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/posts\/10426","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/comments?post=10426"}],"version-history":[{"count":3,"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/posts\/10426\/revisions"}],"predecessor-version":[{"id":10430,"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/posts\/10426\/revisions\/10430"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/media\/10427"}],"wp:attachment":[{"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/media?parent=10426"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/categories?post=10426"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/felusch.de\/en\/wp-json\/wp\/v2\/tags?post=10426"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}