Home / Platform
MSActivator

Model once. Automate everywhere.

Every device, controller and cloud becomes the same kind of object, so automation is written once and reused across vendors.

MSactivatorCloudclappCloudcare Services
Cloudiamo software stack

How Cloudclapp and MSActivator fit together

Cloudiamo software stack: northbound systems, Cloudclapp, MSActivator orchestration, automation and integration layers, Cloudcare services and southbound domains
Open full size ↗
Four layers

Integration at the bottom, orchestration on top

MSActivator abstraction modelA business process calls workflows; workflows call configuration objects by function; each managed entity is mapped to its vendor's library; adapters push configuration to routers, switches, optical, firewalls, virtual functions and clouds and read the state back.BPM · BUSINESS PROCESSOrder · Migrate · Upgrade · Remediatecalls workflowsWORKFLOWS · PYTHON OR PHP, VERSIONED IN GITWF 1WF 2WF 3WF 4…WF ncalls configuration objects by function, per managed entityCONFIGURATION OBJECTS · ONE LIBRARY PER VENDORVendor AMS 1MS 2MS 3…MS nVendor BMS 1MS 2MS 3…MS nVendor NMS 1MS 2MS 3…MS nInventory andconfiguration databasedesign state, live state,resource poolseach entity mapped to its vendor libraryADAPTERSCLI · NETCONF · REST · SNMP · cloud APIs · agentlessconfiguration pushed, state read backRouterSwitchROADMFirewallVNF · CNFCloudORCHESTRATIONAUTOMATIONINTEGRATION
BPMSolution architect. No code.
WorkflowsDeveloper, basic Python.
Configuration objectsDomain expert, once per feature.
AdaptersFrom the library, or built once.
Vendor abstraction

One object, any vendor

One configuration object, any vendorThree vendors express the same firewall rule in CLI, NETCONF and REST. MSActivator models it once as a firewall_rule configuration object with name, destination, port and action, so a workflow makes one call regardless of vendor.VENDOR A · CLIobject network WEB01 host 10.0.0.5policy allow tcp any WEB01 443VENDOR B · NETCONF<rule name="WEB01"> <dst>10.0.0.5/32</dst><port>443</port> <action>accept</action></rule>VENDOR C · RESTPOST /api/policy{"dst":"10.0.0.5","svc":"HTTPS", "act":"allow"}CONFIGURATION OBJECTfirewall_rulenamestringdestinationaddressportintegeractionallow | denycreate · read · update · delete · importWORKFLOW CALLfirewall_rule.create( name="WEB01", destination="10.0.0.5", port=443, action="allow")One call. Any vendor.Vendor syntax stays in the library.
Orchestration

One order drives every domain

Orchestration from service order to activationA service order arrives from OSS, BSS or a portal. BPM orchestrates six steps across domains and vendors: reserve resources, configure the network, instantiate virtual functions, apply security, connect cloud, then verify and activate. Assurance closes the loop by triggering remediation workflows. Orders complete per site, can be rolled back and are idempotent.Service orderOSS and BSS · portal · TMF641BPM · ORCHESTRATION ACROSS DOMAINS AND VENDORS01ReserveresourcesInventory, pools02ConfigurenetworkRouters, fabrics03InstantiatefunctionsNFVO, VNF, CNF04ApplysecurityFirewalls, policy05ConnectcloudCloud APIs, K8s06Verify andactivateAssurance, testsService activeclosed loop: alarms and thresholds trigger remediation workflowsCompletes per site, reports per deviceRollback of a completed orderIdempotent: run twice, one result
  • TM Forum TMF641 and TMF652
  • Service function chaining
  • Partial completion and rollback
  • Multi tenant, self care
ETSI MANO

NFV Orchestrator and generic VNF Manager in one platform

Standards compliant where operators need it, open to functions that are not.

MSActivator in the ETSI MANO architectureMSActivator provides the NFV Orchestrator and a generic VNF Manager, exposes SOL005 northbound, uses SOL003 with its own and specialised VNF managers, and drives OpenStack and Kubernetes infrastructure for VNFs, CNFs and physical functions.OSS · BSS · end to end service orchestratorSOL005MSACTIVATOR · ETSI MANONFV Orchestrator (NFVO)· Network service descriptors· Network service lifecycle· VNF package management· NS performance and faultGeneric VNF Manager (VNFM)· Instantiate and configure· Scale out, in, up and down· Heal, upgrade, terminate· Lifecycle notificationsSOL003Specialised VNFMsfrom function vendorsvia SOL003VIM APIsSOL002Virtual infrastructure managersOpenStack · KubernetesVNFCNFPNFDescriptors in TOSCASOL001
  • SOL001 · SOL002 · SOL003 · SOL005
  • VNFs, CNFs and physical functions
  • Multiple VIMs
  • Geo redundant, active disaster recovery
  • ETSI NFV and MEC Plugtests
MANO in production: DR 02
Autonomous networks

Built for the climb to L4 and L5

Abstraction is what makes higher autonomy reachable across vendors and domains.

Autonomous network levels and where MSActivator contributesSix TM Forum autonomous network levels from L0 manual to L5 full autonomy. Abstraction and workflows support L1 and L2, closed loop assurance supports L3, and intent based automation with generative AI targets L4 and L5.L0ManualL1AssistedL2PartialL3ConditionalL4HighL5FullTM FORUM AUTONOMOUS NETWORK LEVELSAbstraction and workflowsAny vendor, automated end to endClosed loopsEvents trigger remediationIntent and GenAIUnforeseen intents handled
  • TMF921 intent management
  • IG1230 · IG1251 · IG1253
  • Contributor to IG1326
  • ODA components
Built in

Everything operations needs, in one platform

Closed loop assuranceKPIs, logs and alarms that trigger workflows
Two viewsOne for developers, one for operations
Multi tenancyDelegation down to customer self care
API firstREST over every function
DevOps readyVersioning, testing and CI/CD
Carrier gradeHigh availability and geo redundancy
Interfaces

Northbound to your systems, southbound to everything else

Northbound and southbound integrationAbove MSActivator sit OSS and BSS, service orchestrators, TM Forum and ETSI MANO interfaces, CMDB, ticketing, SIEM and customer portals, connected by REST API and Python SDK. Below it sit network, mobile and edge, virtualised, cloud and security estates from any vendor, reached over CLI, NETCONF, REST, SNMP, syslog, telemetry and cloud APIs.NORTHBOUND · YOUR SYSTEMSOSS and BSSService orchestratorsTM Forum TMF641ETSI MANOCMDBITSM and ticketingSIEMCustomer portalsREST API · Python SDKMSACTIVATORBPMbusiness processWorkflowstechnical processConfig objectsvendor abstractionAdaptersagentlessAssuranceKPIs · logs · alarmsInventoryresource poolsCLI · NETCONF · REST · SNMP · syslog · telemetry · cloud APIsSOUTHBOUND · YOUR ESTATE, ANY VENDORNetworkOptical and DWDMIP and MPLSData centre fabricsSD WAN and uCPEMobile and edge5G transportRAN and IP radioETSI MECIoT devicesVirtualisedVNFs and CNFsSDN controllersOpenStackKubernetesCloudPublic cloudPrivate cloudSovereign cloudStorage and computeSecurityFirewallsWAF and IPSVPN gatewaysAntivirus and filtering
Agentic AI roadmap

AI that writes integration and assembles operations

Stage 1Continuous integrationVendor APIs read and modelled automatically
Stage 2Autonomous migrationPolicy moved from one vendor to another
Stage 3Intent based operationsWorkflows assembled from a stated intent

See MSActivator in action

Request a demo