A CAT generator-set ECM record should explain which engine controller belongs to which generating package and which documents support that relationship. The set model alone is not enough. A generating installation can have separate identities for the engine, generator, operator panel and wider control system.
The useful record is therefore an application record, not just a saved controller number. It should let a later reader distinguish engine-control information from set-level information without having to guess which device a note describes.
Anchor the record to the generating package
Begin with the set identity and the engine identity, keeping each under its own label. Add the engine ECM reference where it is known. Do not copy the generator or package serial into the engine serial field merely because it is the easiest plate to read.
Retain documented rating and operating context as background. Electrical output, frequency and duty can describe the set's intended service. These fields do not replace the controller reference or prove which ECM is required. Their value is in helping a reader understand the application covered by the attached documents.
Show the boundary of engine control
The engine ECM manages defined engine functions. A generator-set control panel may present engine information while also handling set-level functions. A record that calls both items the controller creates ambiguity when a replacement request is raised.
Give each assembly its own description. The CAT 227-5801 display control panel is a panel reference, not an engine ECM reference. Mentioning a panel in a set record does not imply that it can replace the engine controller or that it is approved for every CAT generating package.
Link interface information to its source
Where package documents describe communication or control relationships, retain the relevant document number and revision. The record should identify which device sends a request or supplies information and which device receives it. This is a description of documented responsibility, not a wiring instruction.
A displayed engine value can originate outside the display itself. Likewise, a set-level command may pass through more than one device. Do not assign a function to the ECM merely because the function appears on the same operator screen. Use the applicable system description to establish that relationship.
Keep configuration records separate from part identity
The hardware reference identifies the assembly. Configuration information describes the application preparation recorded for that assembly. Store the two separately so that a copied part number does not imply that the software state has also been confirmed.
A paper label can remain after a change to the application preparation. If the record contains software or configuration information, note its source and date. A past document is evidence of what was recorded at that time; it should not be presented as a fresh confirmation of the current unit without further support.
Record document revisions and later changes
Generator packages may have original-build documents and later records of approved changes. Preserve the date and scope of those changes. An updated panel record does not automatically update the engine ECM record, and a new engine record does not prove that every package document has been revised.
When two sources disagree, write down the exact conflict. For example, a parts list can identify one reference while a later supply record identifies another. The file needs the explanation connecting them, if available. The installed unit should not win automatically, and the oldest document should not be treated as permanently authoritative.
Define what a future ECM order would cover
A useful record leaves room for the accepted replacement reference and the agreed application preparation. It should also identify what is outside that supply, such as the set panel or package-builder work. This prevents the phrase complete controller from carrying several different meanings between the site and the supplier.
If the intended engine identity or required preparation is unresolved, keep that gap explicit. Do not replace it with a general claim that a module is for generator use. A broad application label cannot settle a specific relationship between an engine, an ECM and a package control system.
The completed file should allow a reader to answer three questions: which engine-control assembly is recorded, which generating application does the record describe, and which documents support that connection? Keeping those answers together is more useful than collecting unrelated panel images, ratings and part numbers under a single generator heading.
