Support Information
Frequently Asked Questions
Answers to common questions about KCSG services, project engagement and information sharing.
Services and Project Engagement
Can KCSG maintain a system built by another vendor?
Yes, subject to an assessment. We first review the application, source-code availability, documentation, technology stack, access arrangements, known issues and current support responsibilities. We then propose an appropriate transition and maintenance scope.
Can KCSG begin with a small assessment?
Yes. A contained discovery or assessment can clarify the current process, system landscape, risks, priorities and practical next steps before a larger project is approved.
Does KCSG provide both development and ongoing maintenance?
Yes. KCSG can support requirements clarification, design, development, testing, deployment, operational handover, maintenance and controlled enhancement, depending on the agreed scope.
Can KCSG integrate with our ERP, warehouse or partner systems?
KCSG has experience with ERP integration, EDI, APIs, database interfaces and scheduled file exchange. Feasibility depends on the available interface specifications, access, security requirements and ownership of each connected system.
Does KCSG provide software licences without development services?
KCSG can support selected software licensing and renewal requirements. Availability, commercial terms and implementation scope depend on the product and approved vendor arrangements.
Which industries does KCSG have experience in?
KCSG has documented project experience in manufacturing, logistics, shipping and maritime operations, as well as corporate and back-office systems.
How should we share confidential requirements?
Please begin with a high-level description and do not email passwords, personal identification numbers or production data. KCSG can agree on an appropriate confidential information-sharing method before detailed materials are exchanged.
What information is useful for an initial discussion?
A short description of the current problem, affected users, existing systems, desired outcome, important deadlines and known constraints is usually sufficient for the first discussion.