In an ideal world, all Matrix Platform businesses would run their logistics operations in the same way.

Instead, Customer A requires photo proof of delivery and Customer B requires a person aged 21 or over to sign for a package. To support both customer requirements easily, Matrix’s configuration system allows each business unit to customize their final delivery process.

To imagine how this works, think of the Matrix configuration system as an all-you-can-eat Vegas buffet. Handmade California sushi rolls and fresh crab legs comingle with chefs carving Fiorentina-style prime rib or manning the make-your-own omelet station.

Is it time for lunch yet?

In this scenario, success means the ability to customize your plate (or three) based on personal culinary preferences.

Success in Matrix TMS/SCM means each customer can effectively manage their supply chain by configuring the main features to use (entrées). Then, specifics around each function and web page can be configured with personalized datapoints and milestones that meet specific business needs. Need to see a specific button? Need to hide that button from certain users? Need to show only specific content on a page?

No problem.

For some businesses, like Matrix Core+ customers, configurations are consistent and predictable, allowing for simple, repeatable set up and maintenance. For others, like CEVA’s global contract logistics partners, a business’ required functions in Matrix TMS/SCM are highly customized — think five-star gourmet.

Flexibility drives Matrix’s configuration system. Even though it supports all customers with a standard set of modules like carrier management, procurement management and freight settlement, it allows each business to set up the modules from an extensive array of features like those required for proof of delivery.

To fully grasp how the current config system revolutionized the relationship between Matrix and its businesses, it’s necessary to look back.

Matrix and the Wild, Wild West

Let’s set the scene. It’s the early 2000s. Matrix, under the hood, is like an unruly tween.

Changing functionality from one business unit to another happens in a couple of ways:

With hard-codes, the platform’s core code is copied and changed for a new customer. This can mean multiple duplicates of the core code might exist with minor changes for each business. Making a change that affects all users means updating the code for each duplicate.

Soft codes allow specific functionality to be turned on or off by changing a value, which is better than hard-coding separate logic for each customer. But it lacks fine-tuned control. On the other hand, anyone with business unit admin rights can make changes.

And they did. In production. Without always testing well beforehand.

Ouch.

Neither scenario provides stability. There’s either a lot of hard-coded duplicate code with corresponding maintenance issues, or soft code settings without strong quality assurance testing.

Pat Heilmann, the Matrix Platform Director of Engineering, likens the platform's pre-config days to the "wild, wild west". But that’s not all. Implementing new customers causes another issue to rear its head.

“We used to get a new customer, or a new project and we would say it’s just like Vector or it’s just like somebody else. And what that meant was literally copying code and doing it again,” said Matt Franklin, Matrix Design Solutions Architect. In essence, that should streamline the onboarding process. But as the team realizes, there is no standard customer. No organization runs their logistics business like any other customer, doing the exact same thing in the exact same way.

Like a tween gradually maturing to adulthood, the acceptance that the platform needs a better way to organize its framework becomes a catalyst leading to configuration system still used today.

Matrix gets retooled

The Matrix configuration system brings order to chaos by defining how different user interfaces, workflows and features can be set up uniquely for each business in a non-technical way. It allows non-IT administrative users to determine how the platform looks, operates and functions to support their business needs without IT involvement.

“The configuration system was the first time where we collectively, as a department, did something that organized what we had in a less technical nature,” Franklin said. “It bridged the two worlds of engineering or development architecture with the people who were pretty savvy technically and didn’t know all the ins and outs but were empowered to go set the system up for new businesses.”

“It took all the things that made up the application and organized them into modules with business functions,” Franklin continued. “This level of organization was a major milestone over what we had before.”

Right now, Matrix supports over 6,800 configurable elements in the platform, which doesn't include the specific data that drives each business (routes, paths, locations, part details, etc.).

No business will activate every element. Instead, features are built, like asset tracking, as a product within Matrix and then the configuration system handles any tweaks needed to meet customer requirements. To ease the set-up process, all Matrix modules come with a standard set of activated features (ie. buttons, menu items, form fields). After that, each business can customize their view of a module, like in the Dispatch Board image pictured above, by adding or removing features.

The number of these elements that each user sees upon logging in to the platform is an example of the level of refinement that the config system brings. A user’s view in Matrix can be broad and only tied to their role, like dispatcher or supplier, using predefined system filters. Or a view can be complex (see example below), drilling down through multiple layers of the supply chain for magnified visibility.

One Matrix to rule them all

The technology that supports Matrix’s configuration system allows the platform to cater to all customers, whether it’s a smaller operation needing basic freight management functionality or a complex contract logistics customer seeking a high-level of customization to manage their end-to-end global supply chain.

It allows our implementations team to deploy Matrix TMS/SCM for new businesses on a case-by-case basis. Whereas many TMS platforms provide a standard out-of-the-box logistics technology for all businesses with very little flexibility or scalability, Matrix not only caters to CEVA customers’ custom requests but has an IT team who can build new features that save customers millions of dollars in additional fees.

The ability to expand Matrix’s functionality easily is because it’s a high-availability platform with one single code base that’s updated in 6-week increments as part of our standard release cycle. Since Matrix is owned by CEVA, its IT team along with the product and business owners control the platform’s roadmap without relying on outside vendors to expand offerings.

“Even the oldest and most mature Matrix operations continue to evolve within the platform,” said Heilmann. “This evolution can be driven by the need to overcome operational challenges or to win additional business with a customer.”

More importantly, all requested changes are developed in a product-centric way, meaning that an update for Customer A can be utilized by Customer B. New features can be enabled by any business at any time by using the config system. All updates, even the less splashy ones, are recorded in the Matrix Release Notes allowing businesses to look regularly for new features to activate that can improve their workflow in the platform.

“The config system enabled Matrix TMS/SCM and FSS to grow and provide a lot of the additional features and seamless deployments that everyone continues to benefit from,” added Antonio Rodriquez, the Matrix TMS/SCM Product Head.