System brief
Document site use, expected duty cycle, available footprint, and power objective before comparing system architectures.
Lifecycle support
A useful project handoff names the operating objective, electrical boundaries, documentation needs, and the people responsible for each open question.

Document site use, expected duty cycle, available footprint, and power objective before comparing system architectures.
Record control, protection, communications, and acceptance questions so the technical conversation has clear boundaries.
Clarify monitoring, maintenance ownership, and the evidence a service team will need after deployment.
Discuss which standards apply to the intended system rather than assuming a universal certification claim.
Request the specific reports needed for the product, market, and installation route being reviewed.
Keep the latest approved documents together with the project’s defined responsibilities.
Use a short requirements summary before requesting a storage-system discussion.
Open quick configuratorSend the application and regional context to begin a controlled support route.
Contact support