ServiceNow SOMT Data Modeller

ServiceNow SOMT Data Modeller
Service catalogue and inventory modelling
Own the service-catalogue and service-inventory models used by SOMT fulfilment. Translate access-service requirements into implementable specifications, relationships and mappings, with clear identity and lifecycle rules that support ordering, manual fulfilment and later assurance.
Role detail Proposed arrangement
Delivery location Offshore delivery with regular collaboration during agreed UK working hours
Engagement Implementation through March 2027; allocation agreed against the delivery plan
Exact start date, office location, allocation and engagement terms will be confirmed during selection and mobilisation.
Programme context
The programme establishes ServiceNow Order Management for Telecommunications (SOMT) for offnet broadband and low Earth orbit satellite access services. Orders arrive through an upstream integration layer using TMF641. The first release combines manual fulfilment, a native Build team workspace, lightweight service inventory and outbound notifications. Delivery progresses from Create to Cease, bounded MACDs, in-flight amendments and cancellations.
Responsibilities
• Review existing models and define customer-facing service (CFS), resource-facing service (RFS) and resource specifications at the appropriate level of detail for each service journey.
• Distinguish service types, resource types, operational instances, characteristics and fulfilment tasks. Justify modelling choices through lifecycle, identity, ownership and reuse needs.
• Create model diagrams, a data dictionary and characteristic definitions covering types, allowed values, mandatory fields, cardinalities, relationships and validation rules.
• Define catalogue relationships and decomposition mappings with the architect and developers, including characteristic propagation and any required quantity or dependency rules.
• Map incoming TMF641 data, manually captured supplier information and fulfilment results to order records, service inventory and outbound TMF638-style notifications.
• Specify stable service identifiers, supplier references, source-of-truth ownership and lifecycle changes for Create, Cease, bounded MACDs, amendments and cancellations.
• Align lightweight service inventory and CMDB relationships with assurance needs. Identify the minimum approved resource representation and assess later inventory extensions separately.
• Version models and mappings, assess changes to existing payloads and workflows, and prepare representative data with positive, invalid, missing-value and duplicate cases.
• Support catalogue configuration, model verification and client-led testing. Reconcile data discrepancies and hand over editable models, mapping rules and operational field guidance.