Kingdee Cloud ERP Implementation Assistant

Problem

During Kingdee Cloud ERP implementation, delivery documents such as kickoff notices, project manager appointments, meeting minutes, training sign-in sheets, user manuals, and handover checklists must stay aligned with the customer name, project stage, business module, and reported issues. Manual placeholder replacement can miss fields, and switching projects can carry stale client details into new documents.

How it works

• Structured six-field collection: captures the customer's legal name, project stage, business module, current issue, customer project manager, and start date, asking one field at a time.
• Template-based generation: reads local .docx templates with python-docx, replaces placeholders, and outputs stage-specific delivery documents.
• Guided outputs: after the fields are complete, it generates Word files, a Markdown summary, module-specific talking points, and issue guidance in the format of current state, cause, solution, and related template.
• State persistence: supports saving, switching, and resetting project fields in project_state.json, so the same implementation project can continue across sessions.

Boundaries

• Limited to existing templates: it does not generate out-of-scope non-standard clauses.
• Excel is not auto-filled: it reminds users to complete 01-03 and 02-04 manually.
• Signature documents need follow-up: 01-01, 01-02, 02-01, and 03-01 are marked for copying to the official headquarters Word file, formatting, and sealing.