This project is motivated by the introduction of regulatory requirements relating to the transport of  dangerous or controlled materials, safely, securely, and affordably. Hazardous materials are defined under the Transport of Dangerous Goods acts, while controlled materials are defined under the Supply-Chain Due Diligence acts.
The intention is to offer a service to large scale enterprises involved in manufacture, or in the recycling sector, to offer a complete, verifiable supply chain for materials defined above, featuring irrefutable date and timestamps.
The requirements for this project are based on feedback from existing customers, most of whom are in the used-battery collection industry, and some of whom are in the plastics-recycling collection industry. There are EU-wide requirements in force governing the transport of Lithium batteries, which are covered by the Transport of Dangerous Goods acts, in each of the member states. There is also a new EU directive called CSDDD ( Corporate Sustainability Due Diligence Directive ), which mandates that large manufactures must be able to show an audit trail for materials that could be regarded as conflict materials, in order to reduce the likelihood of supporting war or forced-labour.
The above regulatory requirements inform technical requirements that the operators will have, such as facilitating optimal route planning, in order to reduce the carbon footprint of the collections process, and to reduce the operating costs for the operator, and consequently for the tax-payer.
The attached diagram shows the project represented in 'swim-lanes' in an Archimate diagram. The two two lanes can be regarded as the 'Why' layer and show the motivation for the project. The Motivation layer covers the regulatory environment and also high-level technical requirements from the operator. The next layer is the 'What' layer, and describes what needs to be done to satisfy the requirements of the Motivation layer. The next two layers describe the conversation between the Business and the Application, and can be regarded as the 'How' layers; how will it be implemented? The next two swim-lanes show the Technology and Implementation layers respectively. This defines the 'Who' and the 'Where' layers. The 'Who' layer is concerned with the actors and 
functions, and the interactions between them, while the 'Where' layer is about subsystems and work packages.
The Technology and the Implementation layers are further broken down into design documents, using UML as appropriate, and implemented using the 'V' model, so that all of the way down through the model, each phase can be tested to ensure phase containment, and that at the end of the project, the product is delivered as expected, with no surprises.