MHE Fleet Management for Pharmaceutical and Regulated Warehouses
A practical framework for managing warehouse trucks, operator assignments, maintenance evidence and utilization while keeping safety and product decisions with responsible people.

On this page · 11 sections
- 1What MHE Fleet Management means—and where it stops
- 2Regulatory mapping by jurisdiction, product and activity
- 3Operator competence, evaluation and local authorization
- 4The fleet lifecycle: register, assign, operate and close
- 5Maintenance evidence and return-to-service decisions
- 6A data model that connects trucks, people and warehouse work
- 7Integrations, offline work and exception recovery
- 8Measure availability and utilization without hiding constraints
- 9Three worked cases: capacity, duplicate data and a damaged load
- 10Failure modes and the controls that expose them
- 11Implementation and review checklist
How does MHE Fleet Management apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What MHE Fleet Management means—and where it stops
MHE Fleet Management is the coordinated control of a site's material handling equipment fleet, operator assignments, equipment condition, maintenance and use. It connects equipment availability with the people and warehouse work that depend on it, rather than treating a truck register as the whole management process.
This article focuses on forklifts and other powered warehouse trucks. Attachments, batteries and charging arrangements are related fleet resources where relevant to the site's operating model. These are practical boundaries, not regulatory equipment classifications.
The following terms describe different operational decision objects, not interchangeable systems or formal legal categories.
| Term | Management object | Main decision | Boundary |
|---|---|---|---|
| MHE fleet management | Fleet and assignments | Which truck and operator fit the task? | Coordinates fleet readiness and use |
| Forklift fleet management | Forklift subset | Which forklift is suitable and available? | Narrower equipment scope |
| Warehouse task management | Moves and work queues | What work runs next? | Warehouse execution, not equipment upkeep |
| Maintenance management | Asset condition and repair work | What servicing or repair is needed? | CMMS records support fleet decisions |
| Operator training administration | Learning and evaluation records | What competence evidence exists? | A warehouse training matrix supports, rather than replaces, assignment decisions |
The central question is concrete: which suitable truck can a competent operator use for this task, and what evidence supports that decision? Fleet records should help responsible people answer it. They are decision support—not proof that every applicable obligation has been met, and not a substitute for the judgement needed to make the assignment.
02Regulatory mapping by jurisdiction, product and activity
Map each fleet control to the equipment, activity, product and jurisdiction before calling it a requirement. A pharmaceutical warehouse context alone is not an applicability test. Keep workplace safety, drug-product equipment controls, GDP guidance and local operating procedures distinguishable in the fleet register.
| Jurisdiction or context | Source category | Relevant provision | Fleet-management boundary |
|---|---|---|---|
| US powered-industrial-truck safety | Binding regulation | 29 CFR 1910.178(a)(1) | Specified powered industrial trucks; not every item commercially described as MHE. |
| US drug-product equipment | Binding regulation | 21 CFR 211.68(a) | Conditional relevance to equipment used in manufacture, processing, packing and holding of a drug product. |
| European medicines wholesale distribution | Official guidance overview | EMA good distribution practice overview | Check current scope before assigning premises, equipment or record obligations; this is not a truck-specific requirements list. |
| Supplements, food, devices and chemicals | Cross-industry operating practice | Separate product-and-jurisdiction assessment | Use the shared fleet workflow as an operating method, not a substitute for applicable product rules. |
| Fleet software and connected systems | Software support | Site-defined system responsibilities | Specify record support separately from legal applicability and human decision authority. |
The OSHA provision addresses fork trucks, tractors, platform lift trucks, motorized hand trucks and other specialized industrial trucks powered by electric motors or internal combustion engines. Its express exclusions are compressed air or nonflammable compressed gas-operated industrial trucks, farm vehicles, and vehicles intended primarily for earth moving or over-the-road hauling. These are equipment exclusions, not exemptions for particular warehouse sectors or products.
The drug-product provision covers automatic, mechanical, electronic and other equipment, including computers or related systems. If such equipment is used for the listed functions, it must be routinely calibrated, inspected, or checked under a written program designed to assure proper performance. Preserve that wording: it does not say that every forklift entering a pharmaceutical warehouse must be calibrated. For fleet mapping, document the equipment’s function and the applicability decision alongside the broader 21 CFR 211 framework.
For medicines distribution, EMA's GDP overview describes GDP as the minimum standards a wholesale distributor must meet so that “the quality and integrity of medicines is maintained throughout the supply chain”, including that medicines are stored in the right conditions at all times and that “contamination by or of other products is avoided”. EMA does not prescribe forklift records. As operating practice, fleet records can support those expectations: truck cleanliness and condition at hand-over, maintenance restrictions that keep a leaking or damaged truck away from product areas, and handling-event records that link a struck or spilled load to the goods affected.
As operating practice, give each applicability decision an owner and rationale, and define which records belong in the fleet system and which belong in a maintenance management system.
03Operator competence, evaluation and local authorization
For US operations subject to OSHA’s powered industrial truck rule, the employer must ensure that each operator can operate safely, demonstrated through successful completion of the specified training and evaluation. That is the competence obligation in 29 CFR 1910.178(l)(1)(i).
Training combines instruction, practice and evaluation
29 CFR 1910.178(l)(2)(ii) requires a combination of three components:
- Formal instruction, such as lectures, discussion, interactive computer learning or written material.
- Practical training: trainer demonstrations and practical exercises performed by the trainee.
- Evaluation of the operator’s performance in the workplace.
Under 29 CFR 1910.178(l)(2)(iii), people conducting training and evaluation must have the knowledge, training and experience to train powered industrial truck operators and evaluate their competence.
Each operator’s performance must be evaluated at least once every three years under 29 CFR 1910.178(l)(4)(iii). This is a performance-evaluation interval, not a universal certificate-expiry or retraining interval. For refresher-training scope and triggers, check the current text of paragraph (l)(4).
Use a separate local assignment control
As an operational practice, use a warehouse training matrix to connect competence evidence with the work a person is locally authorized to undertake. Suggested fields are:
- Operator identifier and truck type.
- Working area covered by the assignment.
- Relevant restrictions on the assignment.
- Evaluation date and a link to the supporting evidence.
- Local authorization decision and the person responsible for it.
These are proposed operational fields, not the legally prescribed contents of a training certificate. Link each assignment to its training record, rather than treating a single “trained” flag as the whole decision. A practical assignment review should ask whether the recorded truck type, area and restrictions match the proposed work, then leave the authorization decision with the designated person. This keeps the local permission decision distinct from the underlying evidence of competence.
04The fleet lifecycle: register, assign, operate and close
Use the following proposed lifecycle as a local operating model, not a sequence mandated by regulation. Name the person responsible for each transition so that an assignment does not advance merely because a screen shows a completed field.
Fleet coordinator identifies truck and intended work → warehouse supervisor establishes suitability for the load, route and destination → supervisor matches an operator to the task → operator completes applicable condition checks → dispatcher assigns work after reviewing readiness → operator performs work and reports defects or exceptions → shift supervisor reconciles activity and status before closing or handing over the assignment.
29 CFR 1910.178(q)(7) sets the US examination timing for covered trucks: “Industrial trucks shall be examined before being placed in service, and shall not be placed in service if the examination shows any condition adversely affecting the safety of the vehicle. Such examination shall be made at least daily.” Where trucks are used on a round-the-clock basis, the same paragraph requires examination after each shift, and “Defects when found shall be immediately reported and corrected.” Any additional site schedule is local practice and should be labelled as such, not as an OSHA frequency.
For each inspection event, record the asset, person, time, observed condition and resulting action. Keep the operator’s observation separate from the named decision-maker’s equipment-use decision. These are recommended evidence fields, not an OSHA record-field specification.
- Physical service condition: maintenance coordinator owns the recorded condition and unresolved technical concerns.
- Assignment availability: dispatcher owns reservations, current work and task-specific suitability.
- Administrative completeness: fleet coordinator owns missing checks, acknowledgements and closure details.
For example, a mechanically available truck may already be reserved, or the supervisor may not yet have identified a suitable operator for the proposed task. Neither situation should silently change its physical service condition; each should prevent that assignment from being marked ready.
Route technical defects to the maintenance coordinator, task conflicts to the dispatcher, and possible load damage to the designated quality contact. Give unresolved exceptions a named owner in the shift handover report. Repair decisions belong in the maintenance process; cross-system record reconciliation is addressed in the integration section. Close the assignment only when the supervisor has recorded its outcome and any continuing exception ownership.
- IdentifyConfirm asset identity, intended task and operating area.
- MatchReview operator scope against the proposed truck assignment.
- CheckRecord applicable condition checks and resolve adverse observations.
- AssignConfirm readiness before allocating the warehouse task.
- OperateConnect activity to the truck and movement context.
- ResolveRoute defects, repairs and product concerns to owners.
- ReconcileClose records and review status or measurement conflicts.
05Maintenance evidence and return-to-service decisions
Under 29 CFR 1910.178(q)(1), a power-operated industrial truck not in safe operating condition must be removed from service, and all repairs must be made by authorized personnel. Treat the restriction and repair assignment as connected actions, rather than leaving an unsafe truck available while a maintenance request waits.
As an operating control, maintain a defect-to-work-order chain in the maintenance management system or equivalent controlled records. This is a recommended accountability structure, not a record format prescribed by paragraph (q)(1):
- Reported condition and affected asset: identify the defect and the specific truck.
- Restriction: record the service status and the restriction communicated to operators.
- Repair work: link the work performed to the original defect.
- Completion evidence: retain the results supporting completion, not merely a closed status.
- Service-status decision: identify the responsible person and the decision to restore availability or retain the restriction.
For equipment within the drug-product context of 21 CFR 211.67(a), cleaning and maintenance—and sanitizing and/or sterilizing as appropriate for the nature of the drug—must occur at appropriate intervals. The objective is to prevent malfunctions or contamination that would alter drug-product safety, identity, strength, quality or purity beyond official or other established requirements.
21 CFR 211.67(c) requires maintenance, cleaning, sanitizing and inspection records as specified in §§ 211.180 and 211.182. Where paragraph 211.68(a) applies as mapped above, its written-record requirement covers those calibration checks and inspections.
Keep equipment return to service separate from assessment of affected product. Assign the truck-status decision to the site's responsible equipment person and any product assessment and disposition to responsible quality personnel. Link the maintenance event to a deviation record where appropriate. A closed work order should not trigger automatic product release: restored truck availability does not resolve the condition of a load involved in the incident.
06A data model that connects trucks, people and warehouse work
Use these five proposed entities as a starting relationship map, not a mandatory regulatory schema. Keep each record independently identifiable so observations, repairs and warehouse movements remain traceable without copying whole records between systems.
| Entity | Relationships and proposed ownership |
|---|---|
| FleetAsset | One physical truck links to many InspectionEvent observations and MaintenanceWorkOrder records. A fleet custodian owns asset master data. |
| OperatorScope | Links an identified person to relevant truck types and operating areas. A designated training or operations owner maintains the scope. |
| InspectionEvent | Links an observation to its FleetAsset and observer; retain findings and supporting evidence. |
| MaintenanceWorkOrder | Links repair work to its FleetAsset and, where relevant, the originating observation. A maintenance owner records repair completion. |
| MovementContext | Links warehouse work to its FleetAsset and, where applicable, lot references. A warehouse owner maintains movement references. |
Separate physical identity from the reusable display label. Give each truck a stable asset ID; retain local names and rental identifiers as associated references, with effective dates where useful. A replacement truck gets a new asset ID even if it inherits the label “Forklift 3.” Historical records stay attached to the original truck. This is a practical application of data integrity by design.
For event records, include event time, recording time, originating system, responsible person, reason and evidence reference. Keeping the two timestamps separate distinguishes when something happened from when it was entered; identifying the responsible person supports attributable recording. Store meter readings with explicit units and meter definitions: operating hours are not elapsed calendar hours, and neither alone measures productive activity.
Where a CMMS holds repair records, designate that record’s owner rather than maintaining competing completion records. Use software to record, link and present information. A database relationship does not itself demonstrate operator competence, equipment safety or appropriate product disposition; those assessments remain with the responsible people. Make ownership explicit before deciding where each entity is stored.
FleetAsset
Stable identity and current service condition.
- asset_id
- truck_type
- location_id
- service_state
- hour_meter
OperatorScope
Assignment scope linked to evaluation evidence.
- operator_id
- truck_type
- area_id
- evaluator_id
- evaluated_at
InspectionEvent
Dated observation with an actionable result.
- inspection_id
- asset_id
- performed_at
- result
- defect_id
MaintenanceWorkOrder
Repair activity linked to its initiating defect.
- work_order_id
- asset_id
- defect_id
- completed_by
- completed_at
MovementContext
Warehouse activity and relevant material references.
- movement_id
- asset_id
- lot_id
- location_id
- exception_id
07Integrations, offline work and exception recovery
Treat interfaces as agreed exchanges, not shared status labels. The following is a proposed operating design, not a statutory checklist. Apply the same explicit event definitions when connecting a CMMS or planning maintenance-system integration.
| Interface | Record owner | Shared identifiers | Event meaning | Expected acknowledgement |
|---|---|---|---|---|
| Warehouse task → fleet | Warehouse supervisor | Task ID + asset ID | Assignment requested | Fleet coordinator accepts or rejects assignment |
| Maintenance order → fleet | Maintenance lead | Work-order ID + asset ID | Repair work completed | Fleet coordinator records receipt; availability decision remains separate |
| Operator record → assignment | Training coordinator | Operator ID + equipment category | Competence record changed | Assignment owner confirms review of assignment implications |
| Fleet observation → maintenance | Fleet supervisor | Observation ID + asset ID | Condition reported | Maintenance lead returns work-order reference or triage decision |
Give each event a unique identifier. Treat repeat delivery of that identifier as a duplicate, retaining its receipt history without applying the change twice. Put late messages, conflicting asset identifiers and stale status into a reconciliation queue. Compare event time and record version before accepting a change; do not let arrival order alone decide current status. Show when status was last confirmed and seek confirmation before relying on stale information.
During an outage, use a controlled fallback record: decision-maker, asset identifier, operational decision and original event time. When electronic access returns, enter the record with its later entry time as a separate field. Reconcile both timestamps and retain the fallback reference rather than silently replacing the chronology.
Assign every unresolved conflict to a named responsible person. Preserve the competing records, resolution reason, decision-maker and resolution time so the final status remains explainable.
08Measure availability and utilization without hiding constraints
Use the following analytical conventions for fleet reporting, not mandated regulatory KPIs or universal definitions. For each percentage, divide the numerator by the denominator and multiply by 100. Report a zero denominator as not applicable, not zero performance.
Define available truck-hours as scheduled truck-hours minus non-overlapping unavailable truck-hours within that schedule. Count overlapping unavailability intervals only once per truck. Define productive truck-hours through a documented classification of warehouse work, using the same trucks and reporting window.
| Metric | Numerator | Denominator | Interpretation limit |
|---|---|---|---|
| Availability (convention) | Available truck-hours | Scheduled truck-hours | Equipment availability does not establish operator coverage. |
| Productive utilization against schedule (convention) | Productive truck-hours | Scheduled truck-hours | Includes the effect of unavailable time. |
| Productive utilization against availability (convention) | Productive truck-hours | Available truck-hours | Can remain high despite substantial downtime. |
| Defect-related downtime (convention) | Scheduled truck-hours unavailable because of defects | Scheduled truck-hours | Requires a declared rule for overlapping downtime causes. |
Declare the reporting window, included trucks, treatment of rental assets, planned downtime and missing observations alongside the figures. State whether planned downtime remains inside scheduled hours. Do not silently classify missing observations as either productive time or downtime; show their extent and any estimation method.
Do not treat an engine or traction meter as a direct measurement of productive warehouse work without defining its interpretation. State which activities count as productive and how meter readings map to those activities.
Review operator coverage, task suitability and the timing of demand before interpreting fleet averages. Use targeted warehouse-floor observation to investigate mismatches between recorded activity and actual work. These are review dimensions, not utilization targets or fleet-reduction thresholds; investment decisions belong in FAQ 5.
09Three worked cases: capacity, duplicate data and a damaged load
These hypothetical examples illustrate calculations and evidence handling, not customer results, typical performance or sector-wide requirements.
Case 1: Pharmaceutical warehouse capacity
Assume four trucks are scheduled for one eight-hour shift: 4 × 8 = 32 truck-hours. Planned maintenance consumes four truck-hours and unplanned downtime consumes two, with no overlap. Available time is therefore 32 − 4 − 2 = 26 truck-hours. Assume productive work totals 18 truck-hours.
| Selected measure | Calculation | Result |
|---|---|---|
| Availability | 26 ÷ 32 × 100 | 81.25% |
| Scheduled-time utilization | 18 ÷ 32 × 100 | 56.25% |
| Available-time utilization | 18 ÷ 26 × 100 | 69.23% |
Percentages are rounded to two decimal places. Scheduled-time utilization describes productive work against the whole scheduled window; available-time utilization describes it against time remaining after downtime. Changing the denominator changes the interpretation, not the underlying 18 productive truck-hours. Label the measure before comparing shifts.
Case 2: Duplicate meter import
In a hypothetical food or supplement warehouse, assume an opening meter of 1,250.0 operating hours and a closing meter of 1,266.5 operating hours. The increase is 1,266.5 − 1,250.0 = 16.5 operating hours. Receiving the same closing observation twice does not make that increase 33.0 hours.
Preserve the duplicate's source, observation identity and receipt history using attributable recording, then reconcile it before reporting. Keep the 16.5 operating hours separate from productive task hours: this example establishes a meter difference, not what work occurred during it.
Case 3: Fault during pharmaceutical load handling
Assume, hypothetically, that a truck develops a reported fault during a movement involving three pallets, each carrying 40 cartons. The movement context identifies 3 × 40 = 120 potentially relevant cartons; it does not establish that all 120 were damaged.
- Truck condition: What fault was reported, and what did examination establish?
- Movement history: Which pallets, lots, locations and times are linked through bin-level lot genealogy?
- Packaging observations: Which cartons show impact, deformation or leakage, and where?
- Product assessment: What do those observations establish about the identified products?
Apply the decision separation covered above: authorised people assess truck return to service and product disposition separately. Neither a release nor a destruction outcome follows from the carton count alone.
10Failure modes and the controls that expose them
Use these illustrative patterns to test the operating model described above. They are proposed practice controls, not a statutory checklist or a ranking of failure frequency. During a gemba review, compare recorded decisions with the truck and work actually observed.
| Failure mode | Observable signal | Proposed control | Responsible role |
|---|---|---|---|
| Reused asset identifiers | One identifier maps to different serial numbers. | Identity reconciliation: sample retired and active records; does each identifier resolve to one physical truck? | Asset-register owner |
| Ambiguous availability status | Dispatch and maintenance show different states. | Explicit state ownership: can a sampled status change identify its decision owner and effective time? | Fleet supervisor |
| Unlinked defects and work orders | A defect is closed without a repair reference. | Defect-to-work-order linkage: trace a closed defect to its work order and documented disposition. | Maintenance planner |
| Duplicated meter events | The same reading appears through multiple imports. | Duplicate detection: replay a sample event; is it flagged rather than counted twice? | Integration owner |
| Utilization without a denominator | A percentage lacks its time basis. | Published calculation definitions: can a reviewer reproduce the figure from stated hours, exclusions and period? | Fleet analyst |
| Unresolved interface conflicts | Conflicting updates remain without a decision. | Assigned reconciliation ownership: sample a conflict; is an owner named and the resolution recorded? | Reconciliation owner |
Feed unresolved samples into exception-based review, retaining the question, supporting records and named follow-up owner.
11Implementation and review checklist
Use this proposed implementation review to check the operating design. It is not a regulator’s list of required review elements.
- Confirm fleet scope, including rentals, locations and equipment types; assign stable identifiers and record owners.
- Check operator-record links and identify who decides local assignments.
- Trace condition events through restriction, maintenance linkage and the recorded return-to-service decision; check the connection to the maintenance system.
- Confirm movement references connect equipment activity to the relevant warehouse work without duplicating product records.
- Test fallback records, reconciliation responsibilities and interface handling for missing, duplicate or conflicting events.
- Declare KPI definitions, including units, denominators, time windows and exclusions, before comparing results.
Test one normal assignment, one equipment defect and one record-reconciliation exception from beginning to end. Check that each handoff reaches its intended owner and preserves the decision history for audit trail review.
Decision ownership follows the boundary set at the start of this article.
Frequently asked questions
Q.Can a newly hired operator rely on powered-industrial-truck training completed for a previous employer?+
Previous training can count, but it is not a blanket clearance. Under 29 CFR 1910.178(l)(5), additional training in a previously covered topic is unnecessary when that training fits the truck and working conditions and the operator has been evaluated and found competent to operate safely. As a fleet-management practice, use the warehouse training matrix to map relevant previous training, identify gaps and record the evaluation supporting the new assignment.
Q.What may a trainee do before being assigned to operate a truck independently?+
Under 29 CFR 1910.178(l)(2)(i), a trainee may operate only under direct supervision by someone with the knowledge, training and experience to train operators and evaluate competence, and only where operation does not endanger the trainee or other employees. As a scheduling practice, distinguish supervised training from independent assignments in the operator skill matrix. Name the supervisor and define the training task rather than treating a trainee as unrestricted available capacity.
Q.How should a rented or temporary replacement truck enter the fleet record?+
As a recordkeeping practice, create a distinct asset entry rather than borrowing the unavailable truck’s identity. Capture the supplier, serial number, truck type, arrival date, initial meter reading with units, intended assignment and return details. Link its inspections and maintenance separately in the CMMS. Examine it under the same paragraph (q)(7) timing as owned trucks before it is placed in service, and record the supplier's hand-over condition and any open defects on its own entry.
Q.Should mechanical-condition observations and cleanliness observations use the same inspection form?+
As a form-design practice, either arrangement can work: one form with clearly separated sections, or linked forms sharing the truck identity and inspection time. Keep mechanical findings, cleanliness observations, actions and closure decisions distinguishable. For example, a hydraulic leak and residue on a load-contact surface may need different follow-up, even when observed together. Link cleanliness findings to spillage and cross-contamination control where relevant. Do not let one overall checkbox conceal an unresolved finding.
Q.Does high utilization justify reducing the number of trucks?+
Not by itself. As a capacity-planning practice, test the proposed fleet against actual demand, concurrent tasks and unavailable time. Assume three interchangeable trucks each provide eight available hours per shift, with demand of 18 truck-hours: utilization is 18 ÷ 24 = 75%. Removing one leaves 16 truck-hours, a two-truck-hour shortfall. Even adequate total hours do not establish that simultaneous work can be covered. Use finite capacity scheduling to examine timing before deciding on fleet size.
Q.How should warehouse work be replanned when a truck is unavailable and no suitable spare exists?+
Removal and repair of an unsafe truck follow the maintenance section. As a planning practice, have the responsible warehouse manager defer dependent moves, reassess priorities and communicate revised commitments, and use another handling method only when it is suitable and authorised for the load.
Q.What should happen when a meter reading is corrected after a utilization report has been issued?+
As a data-management practice, preserve the original reading and report, record the corrected value and units, identify who made the correction and why, and recalculate affected results. For example, if independently classified productive time for one truck scheduled for eight hours is corrected from six to five truck-hours, productive utilization falls from 75% to 62.5%. Meter runtime is a separate measure and should be corrected and reported on its own line. Issue an identifiable revised report rather than overwriting the original.
Q.When is it useful to link a truck event to pallet or batch records rather than only to a warehouse location?+
As a traceability practice, add pallet or batch links when the event concerns identifiable goods: a struck pallet, a spill beside a handled load or visible residue transferred during a move. Record the event time, truck, location and known affected handling units, distinguishing confirmed associations from possible ones. A location alone may not distinguish successive loads passing through it. Use container status tracking to connect the event with subsequent handling decisions without treating association as proof of product damage.
Primary sources
Want to see how MHE Fleet Management could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
