InnerWeb
Skip to main content

Roles in delivery traffic at an automotive plant: recommendations

The security director of an automotive plant usually sees the same problem: everyone has access to everything, or nobody has enough permissions to settle a matter without a phone call. Below are seven recommendations on how to split the roles of security, the secretariat and logistics in the system, so that deliveries, service and guests each have a clear owner.

5 per 13 min
limit of invitations per user
Source: card

Who these recommendations are for

We address the recommendations to the security director, the logistics manager and the system administrator in a plant that receives deliveries, service companies and guests every day. In an automotive plant these three streams intertwine at the same gates and the same hours, and responsibility for them lies with three different departments.

The InnerWeb system defines roles and the permissions matrix in one place: it is visible who may do what, and a change of permissions requires no change in the code. The roles include, among others, security, the secretariat and the administrative employee. This is a good foundation, but its value depends on how the plant splits responsibility before the start.

Recommendation 1: security records deliveries, it does not manage invitations

The gate guard has the most contact with drivers and the least time. Their role is to confirm the delivery data, close the delivery and handle the verdict at the gate. Guest invitations, account changes and dictionaries should not be their task, because in the peak of a shift nobody has the head for administration.

The reason is practical: the fewer options in the guard's view, the fewer mistakes. The shift supervisor sees deliveries, locators and the roll call, and the rest is hidden.

Number of recommendations by responsible role

Number of recommendations by responsible roleNumber of recommendations by role: security 1, secretariat 2, logistics 1, administrator 3.0123recommendationsSecuritySecurity: 1 recommendations1SecretariatSecretariat: 2 recommendations2LogisticsLogistics: 1 recommendations1AdministratorAdministrator: 3 recommendations3
Source: Illustrative calculation: number of recommendations from this page assigned to the main owner

Recommendation 2: the secretariat is responsible for guests, not for deliveries

The secretariat knows the schedule of visits, so it should be the one that creates planned visits and invitations. Group invitations do not create accounts: a person registers on their own, and an invitation has a limit of 5 requests per 13 minutes per user. This limit protects the system against abuse and against accidentally flooding inboxes.

The reason: the secretariat does not need to know anything about the dock or the carrier. Thanks to this, guests and deliveries have separate paths of responsibility, and a mistake in one does not spoil the other.

Recommendation 3: logistics supervises the status of deliveries

A delivery has a status: active, trailer only, or archived. Closing can happen separately for each driver locator or for all of them at once. That decision belongs to logistics, because it knows whether the trailer stays on the yard until unloading in the next window.

The reason: security knows the fact of entry and exit, but does not know the production plan. The logistician should have the right to correct the status, and security the right to close in standard situations.

Recommendation 4: every external company has one coordinator

For each service company it is worth naming a default contact person. The candidate list also includes people with an invitation waiting for activation, and the server rejects a person from another company or without the coordinator role, so a mistake in the choice will not pass.

The reason: when three companies work on the site in parallel, the dispatcher should not have to look for whom to ask. One coordinator per company shortens every conversation about a permit and about the end of work.

Recommendation 5: who moves a person between companies

It happens that a guest turns out to be an employee of an external company or moves to another company. Moving a guest to another company keeps the same account, so training results, badges and gate entries are not lost. The right to such an operation should belong to the administrator or the secretariat, not to security.

The reason: keeping the account saves repeating the induction training, but only if someone controls the move. Without this control the path could become a loophole for assigning permissions to an unauthorised person.

Recommendation 6: notifications for the team instead of phone calls

Reception events, such as a guest registration, a group taking training at a station, and a guest entering the site, can be sent to the plant's team channel. An empty webhook address means no sending, so the function is optional and requires no change on the side that does not want it.

The reason: a team channel gives shared knowledge of who came in, without calling each person one by one. One person in the secretariat sets the address, and one person in security checks it.

Recommendation 7: review the permissions matrix every quarter

Roles change together with people: a new person in logistics, a promotion in security, a coordinator who leaves. Once a quarter the administrator should review the permissions matrix and remove access that no longer matches the current positions.

The reason is audit-related. In a customer audit the plant shows not only that roles exist, but also that they are reviewed. The system supports this with evidence: the matrix is in one place, so the review takes a short time.

Video

Frequently asked questions

Can security create guest accounts?

We recommend not. Group invitations do not create accounts, and registration belongs to the secretariat. Security focuses on the gate and deliveries.

What if an external company changes its coordinator?

The administrator changes the default contact person. The server rejects a person from another company or without the coordinator role.

Does moving a guest delete their training?

No. The account stays the same, so training results, badges and gate entries are not lost.

Are notifications to the team channel mandatory?

No. An empty webhook address means no sending.

Sources

Split the roles before the gate opens

Book a talk about the permissions matrix for deliveries, service and guests. We will go through the roles in your plant together.

Let's talk