PSR Catalog & TM Forum Enterprise Architect

Overview
We are seeking a PSR Catalog & TM Forum Enterprise Architect to lead the architecture, governance, and end-to-end design of the Product-Service-Resource (PSR) catalog model across the customer lifecycle, from Day -1 Catalog Authoring through Day 0 Buy, Day 1 Get, Day 2 Pay and Support.
The role will serve as a strategic architecture advisor to Enterprise Architecture, defining the Future Mode of Operations (FMO) for quote-to-order, order-to-fulfillment, billing, and assurance value streams. The architect will ensure that PSR catalog and orchestration decisions align with the organization's target Business, Data, Application, and Integration Architecture, while applying TM Forum Open Digital Architecture (ODA), eTOM, and Open API best practices.
The role combines enterprise architecture, telecom BSS/OSS architecture, product catalog modeling, TM Forum standards, API architecture, order orchestration, service/resource decomposition, and catalog governance.
Responsibilities
Design and author the end-to-end Product-Service-Resource (PSR) catalog model spanning the full customer journey, Day -1 through Day 2, across Buy, Get, Pay, and Support.
Serve as CUSTOMER Enterprise Architecture's Future Mode of Operations advisor for the quote-to-order, order-to-fulfillment, and assurance value streams, applying cross-industry eTOM and TM Forum best practice to validate that PSR design decisions align with CUSTOMER's target Business, Data, and Application Architecture, not only the immediate delivery scope.
Validate that Day 0 (Buy) and Day 1 (Get) processes, operations, and data comply with the PSR Governance Best Practices as agreed and accepted by CUSTOMER, to minimize rework to the PSR governance framework itself.
Define and enforce PO, PS, CFS, RFS, and RS layer structures, relationship types, and cardinality rules for each product family, at Day 0 (Buy), before any customer order exists.
Validate structural integrity of the catalog, relationship type, cardinality, decomposition rules, in a governed authoring environment prior to publication.
Map PO/PS commercial and technical characteristics exposed to CPQ for guided selling, pricing, and real-time service qualification at Day 0 (Buy) (TMF645, TMF648, TMF651).
Define Decomposition Rules governing how a signed Product Order becomes Service Orders (CFS, RFS) and Resource Orders (RS) at Day 1 (Get), including enforced build-sequence dependencies (TMF622, TMF641, TMF640, TMF652).
Define commercial characteristics that drive both order decomposition and billing from a single sourced value, for each new product family onboarded under Day 0 (Buy) and Day 1 (Get).
Define the reconciliation gate binding the contracted line item to its discovered Configuration Item at Day 1 (Get), the correlation dependency necessary for Incident, Alarm, and Case correlation to succeed at Day 2.
Apply the established Mandatory versus Optional characteristic classification methodology to all Day 0 (Buy) and Day 1 (Get) catalog characteristics as they are defined, ensuring consistent classification with the Day 2 model already in production.
Cross-reference and validate the Day 0 (Buy) and Day 1 (Get) PSR model additions against their governing TM Forum Open APIs (TMF620, 622, 633, 640, 641, 642, 645, 648, 651, 652) and eTOM Level 2/3 processes across CRM, SM&O, and RM&O.
Extend the existing 39-component runtime artifact inventory to the components introduced by Day 0 (Buy) and Day 1 (Get), tracing each to its governing API, its PSR layer, and the specific record it produces, Quote, Agreement, Customer Order, Service Order, Resource Order, Install Base Item, Configuration Item.
Define the Application Component integration architecture, component-to-component interaction sequence diagrams and communication diagrams, for Day -1 catalog authoring, Day 0 (Buy) customer and offer management, and Day 1 (Get) order-to-resource orchestration, matching the pattern already delivered for Day 2, naming the specific interfaces and the order they fire in.
Produce current-state and future-state process flow diagrams (swimlane, per value stream stage) and the interaction sequence diagrams showing the specific API and data trigger that replaces each manual step, for example Buy moving from manual per-address lookup to real-time TMF645 qualification, Pay moving from manual invoice entry to an automated billing trigger on activation, feeding CUSTOMER Enterprise Architecture's CMO→FMO Capabilities documentation.
Extend the model's existing position within TM Forum's Open Digital Architecture Value Stream Framework (Business Architecture layer) and eTOM (Process Architecture layer) to cover the Day 0 (Buy) and Day 1 (Get) additions.
Produce onboarding materials for CUSTOMER product owners entering Day 0 (Buy) and Day 1 (Get) catalog work, extending the existing Primer and Governance Guide rather than duplicating them.
Reconcile product-owner input, commercial scope, pricing, packaging, and resource-owner input, platform and infrastructure capability, into a single PSR blueprint for each new product family onboarded under Day 0 (Buy) and Day 1 (Get), passing the same relationship-type, cardinality, and decomposition-rule validation applied to every other structural component.
Requirements
Required Skills & Experience
Primary Skills
PSR Catalog Architecture
TM Forum ODA and Open APIs
eTOM Process Architecture
Telecom Enterprise Architecture
Product, Service and Resource Catalog Management
BSS/OSS Architecture
Quote-to-Order and Order-to-Fulfillment Architecture
Product/Service/Resource Decomposition
CPQ and Product/Offer Management
Service Qualification
Order Management and Orchestration
API-led Integration Architecture
Business, Data and Application Architecture
Future Mode of Operations / CMO-to-FMO Transformation
Catalog Governance and Data Modeling
TM Forum Expertise
Strong working knowledge of relevant TM Forum Open APIs, including:
TMF620, TMF622, TMF633, TMF640, TMF641, TMF642, TMF645, TMF648, TMF651 and TMF652.
Experience mapping TM Forum APIs to business capabilities, application components, processes, data objects, and end-to-end customer journeys.
Secondary Skills
BPMN / Business Process Modeling
eTOM Level 2/3 process mapping
TM Forum ODA Value Stream Framework
Application Component Modeling
API and Event-driven Architecture
Sequence and Communication Diagrams
Product/Service/Resource Data Modeling
Relationship and Cardinality Modeling
Commercial Product and Pricing Modeling
Mandatory/Optional Characteristic Modeling
Order Decomposition and Dependency Management
Configuration Item and Install Base Modeling
Incident, Alarm and Case Correlation
CRM, SM&O and RM&O Architecture
Billing and Charging Integration
Data Lineage and Traceability
Architecture Governance
Product Owner Enablement
Stakeholder and Cross-functional Leadership
Experience
12+ years of experience in Enterprise, Solution, BSS/OSS, Telecom, or Digital Service Provider architecture.
Strong experience in TM Forum standards, eTOM, ODA, product/service catalog, and telecom operating models.
Demonstrated experience designing end-to-end product-to-service-to-resource architectures.
Experience working across CRM, CPQ, Order Management, Service Management, Resource Management, Billing, and Assurance domains.
Experience translating business and commercial requirements into governed catalog and architecture models.
Experience producing architecture diagrams, process models, API mappings, data models, and integration specifications.
Experience working with senior business, product, engineering, operations, and Enterprise Architecture stakeholders.
Education
Bachelor's or Master's degree in Computer Science, Information Technology, Engineering, Telecommunications, Enterprise Architecture, or a related discipline.
Preferred Qualifications
TM Forum certifications or demonstrated equivalent practical experience.
TOGAF or equivalent Enterprise Architecture certification.
Experience with telecom BSS/OSS transformation programs.
Experience implementing TM Forum Open APIs in production environments.
Experience with Product Catalog, CPQ, Order Management, Service Orchestration, Resource Orchestration, Billing, and Assurance platforms.

Work arrangement
No