2024-07-23

OFCOM disinterest in OTS?

OFCOM sent a mildly threatening letter about One Touch Switching and the impending deadline.

I replied by email, two, nothing. So wrote, and nothing.

So now this.

We'll see if they reply.

Update: OFCOM want a call, yay!

Update: Useful call, OFCOM listening.

OK, being constructive

I am pondering what could be done right now. So some thoughts...

  • Firstly - this is not simply pedantry, or my getting pissed that I misread the spec - this is not hypothetical. Working with other CPs, and monitoring testing on my NOTSCO test platform, yesterday, half the CPs testing were falling foul of the latest checks on source correlationID added because of TOTSCO bulletin 66. I see other CPs are running in to all the issues I have raised with the specifications. Most of the errors my test platform picks up would not be picked up by the existing TOTSCO testing process. 
  • I feel some people with some clue how to write a clear specification and understand the challenges of coding systems to meet such a specification are engaged with TOTSCO and taken seriously. I can help (though probably not for free - though have I made many suggestions anyway).
  • I feel the specifications need to be consolidated and simplified and put in one place - there are too many parts, in different places, some freely available, some under a login on the control pages, some XLS, some a web page, some PDF, and so on, it is a total mess. Clear and complete set of specifications in one place.
  • TOTSCO need the specifications updated, and kept updated, and a process to notify updates to all CPs involved, so they can ensure compliance. This means proper change controlled notices of what has changed, not a random bulletin that assumes/implies a serious change to a spec that is in a change freeze! Even if this was a weekly spec update with all changes sent to all CPs.
  • I feel going for 12th Sep is fine - we have to start somewhere, but for the start of full OTS usage, and not a requirement for all CPs to be on line, simply because I am not sure there is time for that. But from that date, all CPs that are live on TOTSCO should offer it as part of their ordering process, related to other CPs that are on TOTSCO.
  • Some later deadline for all CPs, maybe an even later one for small CPs.
  • I definitely think a self service test platform is needed for API and OTS with all sorts of scenarios (valid and error testing) and messages both ways, needs to be in place, and a key part of compliance testing. I have one, and I am happy to work with TOTSCO if they want to use it. But it literally took only a couple days to make, so TOTSCO could make one themselves. Testing should be to a reference implementation and against the specification. In practice making this a CP on pre-production (and even live), called TEST, with a control page on TOTSCO to manage tests and replies and logs, would be ideal.
  • We also seem to lack a way to contact other CPs when live to address issues - and a way for TOTSCO to arbitrate that one CP claims another CP does not meet the spec. A clear spec is needed, but a whole inter CP dispute process needs to be in place - and a reference test system would be invaluable for that.

5 comments:

  1. Have you considered getting in contact with the tech media? Perhaps The Register would be interested? They run a lot of articles about actual or impending IT disasters, and it wouldn't be a good look for OFCOM if concerns were raised publicly and they did nothing about it.

    ReplyDelete
  2. My company until recently provided technical support services to a major trade association in the retail industry, maintaining test and simulation tools for a set of industry-specific protocols. Even with clear, mature specifications and good tools, disputes arose between manufacturers / providers as to the correct interpretation of the specification, and we would be called in as consultants to arbitrate.
    God help CPs if there isn't even a clear spec to work from. And thank you Adrian for all your hard work on this.

    ReplyDelete
  3. I look forward to today's stakeholder meeting. For once I intend to stay silent as it seems asking pointed questions is seen as 'heckling'.

    ReplyDelete
  4. There are a couple of key individuals who wrote many of the OTS specifications and processes that have been fighting to get many of the issues resolved as well, and are constantly rebuffed by TOTSCo change control.

    It would really be beneficial if you were to talk to them and use the forum of the industry process group to air the issues as that forum are very much ISP aligned and trying their best to get everything resolved and ready for launch.

    ReplyDelete
  5. Working on it - it is a challenge

    ReplyDelete

Comments are moderated purely to filter out obvious spam, but it means they may not show immediately.

One Touch Switching

It has been some weeks since One Touch Switching was fully live. TOTSCO say over 100,000 switch orders now, so it is making good progress, ...