ServiceNow SOMT Architect

Telecom service fulfilment architecture and technical leadership

Own the SOMT solution architecture and guide its implementation for two access-service journeys. Establish reusable service-order patterns, supported integrations and extensible inventory models, while making platform dependencies, technical decisions and delivery risks explicit.

• Delivery location: UK onsite engagement with offshore engineering and modelling teams
• Engagement:
  Implementation through March 2027; phase allocation and onsite attendance to be agreed

Exact start date, office location, allocation and engagement terms will be confirmed during selection and mobilisation.

The programme establishes Service Now Order Management for Telecommunications (SOMT) for offnet broadband and low Earth orbit satellite access services. Orders arrive through an upstream integration layer using TMF
641. 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.

• Demonstrable architecture ownership of Service Now telecom order-management or service-fulfilment implementations, with evidence of delivery beyond conceptual designs.
• Strong understanding of service-order life cycles, CFS/RFS modelling, resource specifications, catalogue-driven decomposition, attribute propagation and service inventory.
• Practical ability to distinguish TMF
  622 product ordering, TMF
  641 service ordering and TMF
  638 service inventory, and to define usable contracts rather than rely on API labels alone.
• Hands-on understanding of Service Now workflows, scripting, native work spaces, integration patterns and supported extension mechanisms sufficient to review code and diagnose implementation gaps.
• Experience with CMDB and service-model alignment, access control, non-functional requirements, release compatibility, upgrade impact and operational supportability.
• Ability to lead vendor-engineering discussions, compare configuration and custom-development options, and communicate scope, effort and dependency impacts clearly.
• Experience establishing design decisions, acceptance evidence, technical handover and shared ownership across onsite, offshore and client teams.