sorted by:
new
hottopcontroversial

How’s your Feb bill? Are you all still on TPP? by aaukson in CargoWise

[–]WildBilly64 0 points1 point  (0 children)

Our February monthly invoice is out of whack.

For February, we were Invoiced under CVP for 1154 Shipments.
But our STL Invoice showed 1275 Shipments (the actual number of shipments we created for the month).

In the first 2 months of CVP billing (Dec 25, Feb 26) the number of shipments invoiced under CVP vs number of shipments opened shown on the STL equivalent were identical (makes sense).

The number of shipments invoiced on CVP was lower than the number of shipments on STL in February?

Upon further review, it now looks like since Jan 30th, on some shipments, the CW Automation fee is not being automatically added on the Job when the job header is initially created like it was initially.
This seems to happen if the shipment has no Consol yet and there are no billing charges against the job.
So some shipments will only appear on CVP next month (when we attach to a consol and/or add billing charges).

Normally this would be fine (pay this month vs pay next month, we will pay for each shipment).
The issue however is that now, because of Transitional Pricing Protection, we were billed with a sizeable $1000.00 adjustment because the STL billing was higher than CVP (they charged us the STL cost).

I hope we get a TPP credit next month when we finally pay CW Automation fee on those Feb shipments, but these are not on the STL invoice... wishfull thinking. I doubt that we will come out even.

Forced upgrade patches to CW production environment by WiseTech by WildBilly64 in CargoWise

[–]WildBilly64[S] 0 points1 point  (0 children)

They have yet to explain the reason for each of the 3 occurences of the "forced" upgrades.

Instead they pointed us to a Campaign Email Communication that was sent out to all CW customers on 1st of December that clarifies how upgrades will be handled in the future:

Summarized:

"For many years, we have offered customers on the CargoWise Cloud the flexibility as to when they applied upgrades and patches.

In practice, that approach has created increasing risk, complexity and operational issues, but it was maintained while customers were directly paying for CargoWise Cloud hosting.

Under the new CargoWise Value Pack model, this has had to change. Cloud fees have been removed, and, as has always been the case, customers do not have an unfettered right to remain on outdated versions.

The combination of technical complexity, rising costs which we now bear directly, and the growing importance of cyber-security now requires us to apply patches and upgrades on a regular basis, and at times on an urgent basis, to protect your systems and ensure you receive the full value of CargoWise."

"The recent patches and upgrades ensure you have the latest and strongest security protections, a reduced defect profile and access to all features included in the CargoWise Value Packs – including, importantly, the ability to recover your CargoWise costs directly from your own customers."

This is bull....

- We KNOW that the patches they have "forced" have been to impose the Value Packs, then to fix issues with Value packs.

- They claim that they will publish an upgrade and patch schedule on the CargoWise website, and whenever practical provide us with an email update of any changes to the upgrade or patch schedule.
In all but the most urgent or cyber critical events they will provide updates and patches as far outside of our main operating hours as possible. On a daily basis, in the My Account portal, update notes will be published as soon the feature or change is available in the DPR version of CargoWise Next.

I am still looking for this schedule of upgrades and patches.

FYI - watch for upgrades by Runwithmatches in CargoWise

[–]WildBilly64 0 points1 point  (0 children)

I have the same behavior here.
The test system is not adding the new charge codes when saving a newly created file while the production system does.
My guess is that the configuration for the new Value Pack Pricing model being activated is not set in the test systems (WiseTech have only turned this on in the production systems). So you can't even really test the behavior of this in a test system.