Generator Maintenance Schedules and Consumables

A distributor should not turn a generic generator maintenance table into a purchase order. Start with the exact build and serial range, then link each service task to the right manual revision. Order stock only when the source supports the item and quantity; keep the row open if usage, part identity, replacement part numbers, shelf life, minimum order quantity (MOQ) or lead time is unknown.

This is a fleet stock plan, not a service manual. It sets no service interval or procedure and approves no substitute part. Warranty terms and BEAR's offered parts or service scope still need their own evidence.

Group the fleet by the sources that actually control it

Group units only when they use the same service sources and item identities. A change in engine, alternator or controller may require a separate group. Check the same question for fuel and cooling systems, enclosure, market version, options, software and serial range.

Start the fleet register with these fields:

A supplier may propose that two builds share a group. The return still needs to identify the documents and serial/configuration scope that support the grouping. A familiar model name, product photograph, filter dimension, or previous order is not enough.

Build a source map before copying any interval

One manual may not cover the whole set. The engine, alternator, controller, battery, aftertreatment or an option may have its own file. For each source, record the publisher, file reference, title, language and revision or date. Then record the covered models and serials, source location and person who must confirm that it applies.

Manuals and parts lists use model, serial or dataplate records to identify the equipment they cover. That does not make a third-party manual valid for a quoted generator. Use the files that cover the exact offered build.

When two sources address the same task, do not silently choose the shorter or more convenient interval. Return both rows with their revisions and scopes, and name who must resolve the conflict. The set supplier should state which source it intends to govern the offered build. Technical, contract, warranty and safety owners still retain their own decisions.

Keep different maintenance triggers separate

Keep each trigger as the source states it. A date, an hour-meter reading, an event and a condition finding do not mean the same thing. Turning them all into one annual count can give a false total.

Use separate columns for:

• calendar trigger and its start point;
• operating-hours trigger and the meter/source record;
• event trigger, if the applicable source identifies one;
• condition-based decision and the accountable reviewer;
• a “whichever occurs first” relationship only when the controlling source says so;
• duty, environment, fuel, storage, standby/frequent-use, market, and serial limitations;
• document reference, revision, page/table/row, and note or exception.

Keep the source verb as well. INSPECT, CHECK, ADJUST, CLEAN, SAMPLE, TEST, and REPLACE are different tasks. Only a supported replacement row should create automatic stock demand. An inspection may find a worn part; it does not mean every inspection needs a new part. Any pre-order rule needs its own source.

This page intentionally gives no universal oil, filter, belt, battery, spark-plug, coolant, hose, seal, or other interval. Exact procedures and safety controls remain with the applicable manuals and qualified service personnel.

Use one Maintenance and Consumables Stocking Matrix

The matrix should connect a scheduled event to an item that procurement can identify. It should also make uncertainty easy to see rather than burying it inside a stock total.

Do not copy maintenance procedures into this matrix. It is a planning and traceability record, not a technician instruction. Likewise, a commercial quotation can populate MOQ, pack size, lead time, and price fields, but it cannot establish part compatibility or manual applicability by itself.

When a private-label build changes the controller, fuel system, enclosure, battery, cooling, documentation, or kit contents, carry those maintenance identities and revision boundaries into the BEAR OEM and private-label project review.

Forecast demand without inventing a usage rate

Calculate demand separately for each fleet group, controlled item, and planning period. Use these inputs:

• U = units in the controlled fleet group;
• E = planned service events per unit derived from the applicable schedule and the stated operating profile;
• Q = supported item quantity per event;
• O = usable opening stock after identity, condition, and shelf/storage review;
• I = confirmed inbound stock for the same controlled item and period;
• R = buyer-selected reserve policy, recorded separately from source requirements;
• X = unresolved demand or supply uncertainty kept visible.

The planning relationship is:

gross event demand = U × E × Q

preliminary replenishment need = gross event demand + R - O - I

Keep the purchase quantity open while E, Q, source coverage, pack size, MOQ, lead time or X is unresolved. First check date-based and hour-based events on their own. Then apply the source's rule for how they interact. Adding both counts can count one event twice; taking the smaller count can miss it.

The buyer owns the reserve policy; there is no default percentage here. Base it on the site's use and service needs, supply delays and local stock. Keep shelf life, storage, transport status, pack size and cash limits visible too. Record the chosen reserve separately from the manual's requirements.

Control exact item identity, kits, and substitutions

“Oil filter,” “service kit,” or a dimension is not a purchase identity. Each row needs a maker's part number or a supplier code with a documented link to that number. Add the covered build and serial range, specification where needed, quantity per supported event and source.

A kit needs its own number and revision. List every item and quantity, covered fleet groups and service events, exclusions and package identity. State who can change the contents and how that change is recorded. Do not assume one kit covers commissioning, routine service and contingency repairs. The first-order generator spare-parts guide separates those purposes before quantities are discussed.

A cross-reference, matching thread or dimension, supplier statement, or photograph can be a proposal. It is not approval. Link any alternate or supersession to:

1. the original and proposed identities;
2. affected fleet groups, serial ranges, kits, stock, and open orders;
3. the technical/document basis and responsible reviewer;
4. effective date or production/service boundary;
5. handling of obsolete or quarantined stock;
6. manuals, catalogues, labels, service records, and future replenishment rows that must change.

Apply the same discipline to fluids, batteries, belts, hoses, plugs, filters, coolant, additives, seals, and enclosure/control items where the exact configuration requires them. Do not expand the list with “usual generator parts.”

Make the supplier return evidence before scaling the plan

Require one controlled supplier return, then trace one fleet group in both directions before scaling the plan across the portfolio:

• delivered/configuration register with engine, alternator, controller, option, and serial identities;
• applicable manual set and revision register;
• row mapping from each service event to its document, trigger, verb, condition, and serial scope;
• part-number/specification list and quantity-per-event basis;
• approved-alternate and supersession policy with decision owners;
• kit numbers, contents, quantities, exclusions, and revision control;
• current quotation fields for pack size, MOQ, lead time, and price basis;
• shelf, expiry, storage, handling, and transport evidence where applicable;
• service-record template and warranty-condition references kept separate from any invented interpretation;
• technical escalation owner and change-notification route.

For the sample check, choose one exact fleet group and several different service tasks. Trace each unit to its manual, event and item. Then work backward: which units and source rows may use that stocked item? Record mismatches, missing files, unapproved substitutes and unknown quote terms. Expand the plan only after that chain works for the chosen group.

Return or hold plans that hide uncertainty

Use COMPARE when the fleet, source, event, item and quantity fields line up on the same basis, with quote terms, owners and exceptions clear. Use RETURN for a missing or conflicting row that the supplier can correct. Use HOLD for questions that need qualified review, such as part fit, safety, warranty, waste or transport.

Return or hold the plan when:

• one schedule is applied across unlike engine, controller, fuel, enclosure, or market variants;
• a manual revision or serial range is missing;
• engine-manufacturer and generator-supplier rows conflict without a declared precedence and owner;
• calendar and operating-hour triggers are added together or collapsed without source support;
• an inspection, cleaning, adjustment, test, or sampling row is converted into automatic replacement demand;
• a part description, photo, or dimension replaces a controlled identity;
• a cross-reference or supersession is treated as approved without scope and authority;
• kit contents or quantities are hidden;
• MOQ, pack size, lead time, shelf life, storage, or inbound stock is assumed;
• a maintenance table is used to invent warranty obligations;
• obsolete stock remains active after a configuration or part change;
• a precise total conceals unknown usage, event count, quantity, or source applicability.

Used oil and other wastes may trigger destination-specific handling and record duties. The US EPA used-oil business guidance is jurisdiction-specific; it is not a universal instruction and does not establish the rules for another market or material.

Hand the approved matrix into quotation and support

Hand over the fleet groups, planning period, file revisions and accepted service rows together. Attach the item list and quote version. Keep stock assumptions, reserve owner, open questions and the change-notification route visible. Save old versions instead of overwriting them.

Send suppliers the fleet register, expected operating-profile ranges, destination, document list, planning period, service ownership, and required return fields. The broader pre-order document checklist helps reconcile controlled files, while the generator supplier checklist helps keep declarations separate from observed evidence.

For a BEAR inquiry, send Miya the target market, planned generator configurations, quantity by fleet group, operating-profile assumptions, required manual languages, service responsibilities, planning period, and requested parts/consumables return. BEAR must still identify what is actually offered and what evidence applies. The buyer and qualified project parties retain final responsibility for maintenance, compatibility, safety, warranty, storage, transport, disposal, and stocking decisions.