Hi,
The "Physical Work" row in your table is not one API call
"Replace ONT" is TWO resources changing state, transactionally
- Use POST /resourceOrder (TMF652) with wrapper action = modify
- This wrapper action is internally broken down in to a single resource order with two resourceOrderItems each with corresponding action {delete, add}. {Delete Old, Add New}
Additionally there seems following gap in the flow
Gap 1: SERVICE INVENTORY (TMF638)
- Replacing the ONT means the CFS/RFS binding (broadband service -> ONT resource) must be re-pointed.
- TMF639 alone does not do this; TMF638 owns the service -> resource relationship.
Gap 2: ACTIVATION IS MISSING
- A new ONT needs provisioning: PLOAM auth on OLT, TR-069 ACS enrolment, WiFi SSID/PSK restore, VLAN/QoS profile push.
- This is TMF640 Service Activation & Configuration territory.
Regards
------------------------------
Nitin Srivastava
Jio Platforms Limited
------------------------------
Original Message:
Sent: Jul 22, 2026 02:26
From: yanto yanto
Subject: TMF 697 WorkOrder Management
Hello,
We have already impement tmf 621, 641, 646 . But we having problem to make standardized API transaction with Partner for Work Order require device replacement (CPE) on customer site End to End . Figure out how the best implement if there is business flow require this, here what we got :
| Step |
TMF API |
Purpose |
| Customer reports "No Internet" |
TMF621 |
Create and track the trouble ticket |
| Diagnostics conclude ONT must be replaced |
Internal diagnostics / business rules |
Decision making (not standardized by TMF) |
| Dispatch technician |
TMF697 |
Create the field work order |
| Schedule visit |
TMF646 |
Manage the appointment |
| Replace ONT |
Technician |
Physical work |
| Update installed device |
TMF639 |
Update the resource inventory |
| If new equipment must be allocated |
TMF652 |
Request/provision the physical resource if needed |
| Close customer case |
TMF621 |
Resolve and close the ticket |
Device replacement become common with operation transaction medium quantity. High when there are upgrade device on certain area..
Please suggest the flow above, does they are effecient ?
thanks and regards
yanto
------------------------------
yanto yanto
Axiata Group Berhad
------------------------------
Original Message:
Sent: May 06, 2026 09:23
From: Goutham Babu
Subject: TMF 697 WorkOrder Management
Hi Camila,
TMF697 is not yet operational as a published Open API, and there is no confirmed release date at this time.
Based on current Open API project records:
- TMF697 (Work Order Management API) is still under development and remains in an Feedback implementation phase.
The API has not completed the required lifecycle gates for publication, including:
- A complete and reviewed asset set (OAS, User Guide, Conformance Profile)
- Resolution of implementer feedback
- Successful validation and readiness checks
Release timing in the Open API programme is member‑driven, and progression depends on:
- Active implementer engagement
- Closure of feedback items
- Completion of mandatory build assets
As such, it is not possible to commit to or predict a release date at this stage.
------------------------------
Goutham Babu
API Product Owner
TM Forum
------------------------------