build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | format run

$ soultec get service/managed-service -o yaml$ soultec get service/managed-service -o json$ soultec get service/managed-service -o toml$ soultec get service/managed-service -o xml$ python3 managed-service.pyPS> ./managed-service.ps1$ go run managed-service.go$ node managed-service.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: managed-service locale: en labels: group: support capability/managed-services: 2.65 capability/monitoring: 2.44 annotations: source: src/content/services/en/managed-service.md route: /en/services/managed-service/ schema: /nerd/schema/services.json markdown: /en/services/managed-service.mdspec: title: Managed Service group: support audience: [enterprise, provider] order: 2 tags: [managed-services, monitoring] summary: >- Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle. photoNeed: >- The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working stub: false draft: false sections: - heading:

What this is about

body: | Your own IT department should be able to concentrate on its core work. For certain operational tasks it is therefore worth handing responsibility to us, rather than letting them run alongside everything else. - heading:

Where it helps most

body: | On solutions we implemented ourselves. There we can commit to keeping the estate in a supported state across its whole lifecycle, aligned with every surrounding system. That is more than a form of words. A version that is supported on its own can still fall outside the compatibility matrix in combination with the storage underneath it or the backup beside it. Keeping that combination in view is the actual work, and it is exactly what stops happening when something more urgent turns up in the day job. - heading:

What is included

body: | - Patching of the Microsoft servers - System and firmware updates - Daily checks of the backups and regular restore tests - Capacity, log and performance monitoring - Individual tasks on site or remote, as agreed Your team gains time for development and projects, and demanding configurations are done by someone who does them regularly. That saves training cost and closes knowledge gaps that would otherwise show up internally only with the next incident. - heading:

How this differs from the Service Desk

body: | The service desk is where you go when something is not working. The managed service is the responsibility for keeping the state maintained, including when nobody is calling.status: corpus: 315 solutions: - {ref: solutions/omnissa/workspace-one/workspace-one-assist, score: 0.42} - {ref: solutions/vmware/vmware-cloud-service-provider, score: 0.41} - {ref: solutions/vmware/vmware-cloud-foundation/addon/business-operations, score: 0.40} - {ref: solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon, score: 0.40} alsoLike: - {ref: services/monitoring, score: 1.00} - {ref: services/managed-security, score: 0.52} - {ref: posts/infrastructure-assessment-mit-hpe-cloudphysics, score: 0.49} experts: - {ref: experts/valentina-cicmak, score: 0.42} - {ref: experts/mike-schmid, score: 0.33} - {ref: experts/matthias-frech, score: 0.32} search: /en/search.json
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "managed-service", "locale": "en", "labels": { "group": "support", "capability/managed-services": 2.65, "capability/monitoring": 2.44 }, "annotations": { "source": "src/content/services/en/managed-service.md", "route": "/en/services/managed-service/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/managed-service.md" } }, "spec": { "title": "Managed Service", "group": "support", "audience": [ "enterprise", "provider" ], "order": 2, "tags": [ "managed-services", "monitoring" ], "summary": "Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.", "photoNeed": "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", "stub": false, "draft": false, "sections": [ { "heading": "

What this is about

",
"body": "Your own IT department should be able to concentrate on its core work. For certain\noperational tasks it is therefore worth handing responsibility to us, rather than letting\nthem run alongside everything else." }, { "heading": "

Where it helps most

",
"body": "On solutions we implemented ourselves. There we can commit to keeping the estate in a\nsupported state across its whole lifecycle, aligned with every surrounding system.\n\nThat is more than a form of words. A version that is supported on its own can still fall\noutside the compatibility matrix in combination with the storage underneath it or the\nbackup beside it. Keeping that combination in view is the actual work, and it is exactly\nwhat stops happening when something more urgent turns up in the day job." }, { "heading": "

What is included

",
"body": "- Patching of the Microsoft servers\n- System and firmware updates\n- Daily checks of the backups and regular restore tests\n- Capacity, log and performance monitoring\n- Individual tasks on site or remote, as agreed\n\nYour team gains time for development and projects, and demanding configurations are done by\nsomeone who does them regularly. That saves training cost and closes knowledge gaps that\nwould otherwise show up internally only with the next incident." }, { "heading": "

How this differs from the Service Desk

",
"body": "The service desk is where you go when something is not working. The managed service is the\nresponsibility for keeping the state maintained, including when nobody is calling." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.42" }, { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.41" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/business-operations", "score": "0.40" }, { "ref": "solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon", "score": "0.40" } ], "alsoLike": [ { "ref": "services/monitoring", "score": "1.00" }, { "ref": "services/managed-security", "score": "0.52" }, { "ref": "posts/infrastructure-assessment-mit-hpe-cloudphysics", "score": "0.49" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.42" }, { "ref": "experts/mike-schmid", "score": "0.33" }, { "ref": "experts/matthias-frech", "score": "0.32" } ], "search": "/en/search.json" }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "managed-service"locale = "en"[metadata.labels]group = "support""capability/managed-services" = 2.65"capability/monitoring" = 2.44[metadata.annotations]source = "src/content/services/en/managed-service.md"route = "/en/services/managed-service/"schema = "/nerd/schema/services.json"markdown = "/en/services/managed-service.md"[spec]title = "Managed Service"group = "support"audience = ["enterprise", "provider"]order = 2tags = ["managed-services", "monitoring"]summary = "Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle."photoNeed = "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working"stub = falsedraft = false[[spec.sections]]heading = "

What this is about

"
body = '''Your own IT department should be able to concentrate on its core work. For certainoperational tasks it is therefore worth handing responsibility to us, rather than lettingthem run alongside everything else.'''[[spec.sections]]heading = "

Where it helps most

"
body = '''On solutions we implemented ourselves. There we can commit to keeping the estate in asupported state across its whole lifecycle, aligned with every surrounding system.That is more than a form of words. A version that is supported on its own can still falloutside the compatibility matrix in combination with the storage underneath it or thebackup beside it. Keeping that combination in view is the actual work, and it is exactlywhat stops happening when something more urgent turns up in the day job.'''[[spec.sections]]heading = "

What is included

"
body = '''- Patching of the Microsoft servers- System and firmware updates- Daily checks of the backups and regular restore tests- Capacity, log and performance monitoring- Individual tasks on site or remote, as agreedYour team gains time for development and projects, and demanding configurations are done bysomeone who does them regularly. That saves training cost and closes knowledge gaps thatwould otherwise show up internally only with the next incident.'''[[spec.sections]]heading = "

How this differs from the Service Desk

"
body = '''The service desk is where you go when something is not working. The managed service is theresponsibility for keeping the state maintained, including when nobody is calling.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/omnissa/workspace-one/workspace-one-assist"score = "0.42"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-service-provider"score = "0.41"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/business-operations"score = "0.40"[[status.solutions]]ref = "solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon"score = "0.40"[[status.alsoLike]]ref = "services/monitoring"score = "1.00"[[status.alsoLike]]ref = "services/managed-security"score = "0.52"[[status.alsoLike]]ref = "posts/infrastructure-assessment-mit-hpe-cloudphysics"score = "0.49"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.42"[[status.experts]]ref = "experts/mike-schmid"score = "0.33"[[status.experts]]ref = "experts/matthias-frech"score = "0.32"
<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>managed-service</name> <locale>en</locale> <labels> <group>support</group> <entry key="capability/managed-services">2.65</entry> <entry key="capability/monitoring">2.44</entry> </labels> <annotations> <source>src/content/services/en/managed-service.md</source> <route>/en/services/managed-service/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/managed-service.md</markdown> </annotations> </metadata> <spec> <title>Managed Service</title> <group>support</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>2</order> <tags> <item>managed-services</item> <item>monitoring</item> </tags> <summary>Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.</summary> <photoNeed>The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

What this is about

</heading>
<body>Your own IT department should be able to concentrate on its core work. For certainoperational tasks it is therefore worth handing responsibility to us, rather than lettingthem run alongside everything else. </body> </section> <section> <heading>

Where it helps most

</heading>
<body>On solutions we implemented ourselves. There we can commit to keeping the estate in asupported state across its whole lifecycle, aligned with every surrounding system.That is more than a form of words. A version that is supported on its own can still falloutside the compatibility matrix in combination with the storage underneath it or thebackup beside it. Keeping that combination in view is the actual work, and it is exactlywhat stops happening when something more urgent turns up in the day job. </body> </section> <section> <heading>

What is included

</heading>
<body>- Patching of the Microsoft servers- System and firmware updates- Daily checks of the backups and regular restore tests- Capacity, log and performance monitoring- Individual tasks on site or remote, as agreedYour team gains time for development and projects, and demanding configurations are done bysomeone who does them regularly. That saves training cost and closes knowledge gaps thatwould otherwise show up internally only with the next incident. </body> </section> <section> <heading>

How this differs from the Service Desk

</heading>
<body>The service desk is where you go when something is not working. The managed service is theresponsibility for keeping the state maintained, including when nobody is calling. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/omnissa/workspace-one/workspace-one-assist</ref> <score>0.42</score> </item> <item> <ref>solutions/vmware/vmware-cloud-service-provider</ref> <score>0.41</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/business-operations</ref> <score>0.40</score> </item> <item> <ref>solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon</ref> <score>0.40</score> </item> </solutions> <alsoLike> <item> <ref>services/monitoring</ref> <score>1.00</score> </item> <item> <ref>services/managed-security</ref> <score>0.52</score> </item> <item> <ref>posts/infrastructure-assessment-mit-hpe-cloudphysics</ref> <score>0.49</score> </item> </alsoLike> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.42</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.33</score> </item> <item> <ref>experts/matthias-frech</ref> <score>0.32</score> </item> </experts> <search>/en/search.json</search> </status></manifest>
# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "managed-service", "locale": "en", "labels": { "group": "support", "capability/managed-services": 2.65, "capability/monitoring": 2.44, }, "annotations": { "source": "src/content/services/en/managed-service.md", "route": "/en/services/managed-service/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/managed-service.md", }, }, "spec": { "title": "Managed Service", "group": "support", "audience": ["enterprise", "provider"], "order": 2, "tags": ["managed-services", "monitoring"], "summary": "Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.", "photoNeed": "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", "stub": False, "draft": False, "sections": [ { "heading": "

What this is about

",
"body": ( "Your own IT department should be able to concentrate on its core work. For certain\n" "operational tasks it is therefore worth handing responsibility to us, rather than letting\n" "them run alongside everything else." ), }, { "heading": "

Where it helps most

",
"body": ( "On solutions we implemented ourselves. There we can commit to keeping the estate in a\n" "supported state across its whole lifecycle, aligned with every surrounding system.\n" "\n" "That is more than a form of words. A version that is supported on its own can still fall\n" "outside the compatibility matrix in combination with the storage underneath it or the\n" "backup beside it. Keeping that combination in view is the actual work, and it is exactly\n" "what stops happening when something more urgent turns up in the day job." ), }, { "heading": "

What is included

",
"body": ( "- Patching of the Microsoft servers\n" "- System and firmware updates\n" "- Daily checks of the backups and regular restore tests\n" "- Capacity, log and performance monitoring\n" "- Individual tasks on site or remote, as agreed\n" "\n" "Your team gains time for development and projects, and demanding configurations are done by\n" "someone who does them regularly. That saves training cost and closes knowledge gaps that\n" "would otherwise show up internally only with the next incident." ), }, { "heading": "

How this differs from the Service Desk

",
"body": ( "The service desk is where you go when something is not working. The managed service is the\n" "responsibility for keeping the state maintained, including when nobody is calling." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.42", }, { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.41", }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/business-operations", "score": "0.40", }, { "ref": "solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon", "score": "0.40", }, ], "alsoLike": [ { "ref": "services/monitoring", "score": "1.00", }, { "ref": "services/managed-security", "score": "0.52", }, { "ref": "posts/infrastructure-assessment-mit-hpe-cloudphysics", "score": "0.49", }, ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.42", }, { "ref": "experts/mike-schmid", "score": "0.33", }, { "ref": "experts/matthias-frech", "score": "0.32", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))
# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'managed-service' locale = 'en' labels = [ordered]@{ group = 'support' 'capability/managed-services' = 2.65 'capability/monitoring' = 2.44 } annotations = [ordered]@{ source = 'src/content/services/en/managed-service.md' route = '/en/services/managed-service/' schema = '/nerd/schema/services.json' markdown = '/en/services/managed-service.md' } } spec = [ordered]@{ title = 'Managed Service' group = 'support' audience = @('enterprise', 'provider') order = 2 tags = @('managed-services', 'monitoring') summary = 'Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.' photoNeed = 'The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working' stub = $false draft = $false sections = @( [ordered]@{ heading = '

What this is about

'
body = @'Your own IT department should be able to concentrate on its core work. For certainoperational tasks it is therefore worth handing responsibility to us, rather than lettingthem run alongside everything else.'@ } [ordered]@{ heading = '

Where it helps most

'
body = @'On solutions we implemented ourselves. There we can commit to keeping the estate in asupported state across its whole lifecycle, aligned with every surrounding system.That is more than a form of words. A version that is supported on its own can still falloutside the compatibility matrix in combination with the storage underneath it or thebackup beside it. Keeping that combination in view is the actual work, and it is exactlywhat stops happening when something more urgent turns up in the day job.'@ } [ordered]@{ heading = '

What is included

'
body = @'- Patching of the Microsoft servers- System and firmware updates- Daily checks of the backups and regular restore tests- Capacity, log and performance monitoring- Individual tasks on site or remote, as agreedYour team gains time for development and projects, and demanding configurations are done bysomeone who does them regularly. That saves training cost and closes knowledge gaps thatwould otherwise show up internally only with the next incident.'@ } [ordered]@{ heading = '

How this differs from the Service Desk

'
body = @'The service desk is where you go when something is not working. The managed service is theresponsibility for keeping the state maintained, including when nobody is calling.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/omnissa/workspace-one/workspace-one-assist' score = '0.42' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-service-provider' score = '0.41' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/addon/business-operations' score = '0.40' } [ordered]@{ ref = 'solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon' score = '0.40' } ) alsoLike = @( [ordered]@{ ref = 'services/monitoring' score = '1.00' } [ordered]@{ ref = 'services/managed-security' score = '0.52' } [ordered]@{ ref = 'posts/infrastructure-assessment-mit-hpe-cloudphysics' score = '0.49' } ) experts = @( [ordered]@{ ref = 'experts/valentina-cicmak' score = '0.42' } [ordered]@{ ref = 'experts/mike-schmid' score = '0.33' } [ordered]@{ ref = 'experts/matthias-frech' score = '0.32' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32
// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "managed-service", "locale": "en", "labels": map[string]any{ "group": "support", "capability/managed-services": 2.65, "capability/monitoring": 2.44, }, "annotations": map[string]any{ "source": "src/content/services/en/managed-service.md", "route": "/en/services/managed-service/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/managed-service.md", }, }, "spec": map[string]any{ "title": "Managed Service", "group": "support", "audience": []any{"enterprise", "provider"}, "order": 2, "tags": []any{"managed-services", "monitoring"}, "summary": "Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.", "photoNeed": "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

What this is about

",
"body": "Your own IT department should be able to concentrate on its core work. For certain\n" + "operational tasks it is therefore worth handing responsibility to us, rather than letting\n" + "them run alongside everything else.", }, map[string]any{ "heading": "

Where it helps most

",
"body": "On solutions we implemented ourselves. There we can commit to keeping the estate in a\n" + "supported state across its whole lifecycle, aligned with every surrounding system.\n" + "\n" + "That is more than a form of words. A version that is supported on its own can still fall\n" + "outside the compatibility matrix in combination with the storage underneath it or the\n" + "backup beside it. Keeping that combination in view is the actual work, and it is exactly\n" + "what stops happening when something more urgent turns up in the day job.", }, map[string]any{ "heading": "

What is included

",
"body": "- Patching of the Microsoft servers\n" + "- System and firmware updates\n" + "- Daily checks of the backups and regular restore tests\n" + "- Capacity, log and performance monitoring\n" + "- Individual tasks on site or remote, as agreed\n" + "\n" + "Your team gains time for development and projects, and demanding configurations are done by\n" + "someone who does them regularly. That saves training cost and closes knowledge gaps that\n" + "would otherwise show up internally only with the next incident.", }, map[string]any{ "heading": "

How this differs from the Service Desk

",
"body": "The service desk is where you go when something is not working. The managed service is the\n" + "responsibility for keeping the state maintained, including when nobody is calling.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.42", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.41", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/addon/business-operations", "score": "0.40", }, map[string]any{ "ref": "solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon", "score": "0.40", }, }, "alsoLike": []any{ map[string]any{ "ref": "services/monitoring", "score": "1.00", }, map[string]any{ "ref": "services/managed-security", "score": "0.52", }, map[string]any{ "ref": "posts/infrastructure-assessment-mit-hpe-cloudphysics", "score": "0.49", }, }, "experts": []any{ map[string]any{ "ref": "experts/valentina-cicmak", "score": "0.42", }, map[string]any{ "ref": "experts/mike-schmid", "score": "0.33", }, map[string]any{ "ref": "experts/matthias-frech", "score": "0.32", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}
// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "managed-service", locale: "en", labels: { group: "support", "capability/managed-services": 2.65, "capability/monitoring": 2.44, }, annotations: { source: "src/content/services/en/managed-service.md", route: "/en/services/managed-service/", schema: "/nerd/schema/services.json", markdown: "/en/services/managed-service.md", }, }, spec: { title: "Managed Service", group: "support", audience: ["enterprise", "provider"], order: 2, tags: ["managed-services", "monitoring"], summary: "Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.", photoNeed: "The support desk in an ordinary hour: headset, ticket queue on screen, the person actually working", stub: false, draft: false, sections: [ { heading: "

What this is about

",
body: "Your own IT department should be able to concentrate on its core work. For certain\n" + "operational tasks it is therefore worth handing responsibility to us, rather than letting\n" + "them run alongside everything else.", }, { heading: "

Where it helps most

",
body: "On solutions we implemented ourselves. There we can commit to keeping the estate in a\n" + "supported state across its whole lifecycle, aligned with every surrounding system.\n" + "\n" + "That is more than a form of words. A version that is supported on its own can still fall\n" + "outside the compatibility matrix in combination with the storage underneath it or the\n" + "backup beside it. Keeping that combination in view is the actual work, and it is exactly\n" + "what stops happening when something more urgent turns up in the day job.", }, { heading: "

What is included

",
body: "- Patching of the Microsoft servers\n" + "- System and firmware updates\n" + "- Daily checks of the backups and regular restore tests\n" + "- Capacity, log and performance monitoring\n" + "- Individual tasks on site or remote, as agreed\n" + "\n" + "Your team gains time for development and projects, and demanding configurations are done by\n" + "someone who does them regularly. That saves training cost and closes knowledge gaps that\n" + "would otherwise show up internally only with the next incident.", }, { heading: "

How this differs from the Service Desk

",
body: "The service desk is where you go when something is not working. The managed service is the\n" + "responsibility for keeping the state maintained, including when nobody is calling.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/omnissa/workspace-one/workspace-one-assist", score: "0.42", }, { ref: "solutions/vmware/vmware-cloud-service-provider", score: "0.41", }, { ref: "solutions/vmware/vmware-cloud-foundation/addon/business-operations", score: "0.40", }, { ref: "solutions/omnissa/workspace-one/addon/omnissa-intelligence-addon", score: "0.40", }, ], alsoLike: [ { ref: "services/monitoring", score: "1.00", }, { ref: "services/managed-security", score: "0.52", }, { ref: "posts/infrastructure-assessment-mit-hpe-cloudphysics", score: "0.49", }, ], experts: [ { ref: "experts/valentina-cicmak", score: "0.42", }, { ref: "experts/mike-schmid", score: "0.33", }, { ref: "experts/matthias-frech", score: "0.32", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 74 lines · YAML · validated at build# 104 lines · JSON · validated at build# 113 lines · TOML · validated at build# 129 lines · XML · validated at build# 129 lines · Python · read back at build, equals the JSON record# 126 lines · PowerShell · read back at build, equals the JSON record# 133 lines · Go · read back at build, equals the JSON record# 118 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/managed-service.md

Service · support

Managed Service

Hand over operational tasks so your own IT can concentrate on its core work. For solutions we built, across the whole lifecycle.

04Solutions
02Capabilities
315Corpus

What this is about

Your own IT department should be able to concentrate on its core work. For certain operational tasks it is therefore worth handing responsibility to us, rather than letting them run alongside everything else.

Where it helps most

On solutions we implemented ourselves. There we can commit to keeping the estate in a supported state across its whole lifecycle, aligned with every surrounding system.

That is more than a form of words. A version that is supported on its own can still fall outside the compatibility matrix in combination with the storage underneath it or the backup beside it. Keeping that combination in view is the actual work, and it is exactly what stops happening when something more urgent turns up in the day job.

What is included

  • Patching of the Microsoft servers
  • System and firmware updates
  • Daily checks of the backups and regular restore tests
  • Capacity, log and performance monitoring
  • Individual tasks on site or remote, as agreed

Your team gains time for development and projects, and demanding configurations are done by someone who does them regularly. That saves training cost and closes knowledge gaps that would otherwise show up internally only with the next incident.

How this differs from the Service Desk

The service desk is where you go when something is not working. The managed service is the responsibility for keeping the state maintained, including when nobody is calling.

Experts for this

Maybe you? Take a look at our open roles.

You might also like