Sections in this article
- K3S Project Services and Scheduling
- Project Types
- Scheduling
- ERP Upgrade — 2 Months+
- ERP Changing — 6 Months+
- Unique Project — Variable
- Emergency Work
K3S Project Services and Scheduling
K3S provides project-based services for development, integration, and system transitions that fall outside the scope of standard maintenance and support. All project work is scheduled on a quarterly basis and subject to resource availability.
For all project inquiries, contact K3S at support@k3s.com to obtain a scope assessment and estimate.
Project Types
Project-Based Services — Wide Release
You may sponsor development of a defined feature or function for the K3S software platform. You may choose to pay for priority queue placement, if available. You will work with K3S to define the specifications or use case, and K3S will provide the development. K3S owns the resulting code and releases it to all customers upon wide release.
Project-Based Services — Controlled Release
You may sponsor development of a defined feature or function for the K3S software platform. You may choose to pay for priority queue placement, if available. You will work with K3S to define the specifications or use case, and K3S will provide the development. K3S owns the resulting code and provides you an exclusive, non-transferable license for as long as an annual maintenance fee is paid.
Custom Services Work
Custom services work covers development or integration outside the normal scope of K3S offerings. All custom work is the property of K3S and is subject to a premium development rate as well as an annual maintenance fee for ongoing support.
Invoicing
Project work invoices under $2,000 are prepaid in full. Invoices of $2,000 or more are due 50% upfront and 50% upon completion of work. All estimates represent a minimum number of hours. If work requires additional hours beyond the estimate, those hours are due in full upon completion.
Project work is invoiced monthly.
Scheduling
K3S schedules all project work on a quarterly basis, with project cycles beginning on January 1st, April 1st, July 1st, and October 1st. Projects are scheduled on a first-come, first-served basis, subject to resource availability, and may be planned well in advance. K3S will not schedule work beyond available engineering capacity.
To ensure successful execution, all projects involving data exchanged with K3S must incorporate the lead times outlined below into planning and timeline commitments. While K3S is committed to supporting customer initiatives, project timelines must be realistic and account for required planning, testing, and resource allocation.
Customer-Initiated System Changes
Customers are responsible for notifying K3S of any system changes that may impact data exchanged with K3S, including but not limited to ERP upgrades, ERP replacements, database changes, file structure changes, or process changes.
If K3S is not engaged with sufficient lead time to evaluate and prepare for such changes, K3S cannot guarantee uninterrupted processing or compatibility with updated systems.
Work required to address issues resulting from unplanned or late-notice changes may be treated as emergency work and will be scheduled and billed accordingly.
ERP Upgrade — 2 Months+
If your team is planning an ERP upgrade that may impact the data provided to K3S interface files, K3S recommends engaging in a formal project to validate compatibility and prevent downtime or data issues.
Based on experience, K3S recommends allowing a minimum of two (2) months for evaluation, testing, and implementation support. Customers are encouraged to engage K3S early in the planning process to ensure proper scheduling.
ERP Changing — 6 Months+
ERP system changes are significantly more complex than upgrades and typically require a full project to support new integrations and data structures, as well as the migration of historical data.
K3S recommends engaging at the earliest stages of ERP selection or planning. These projects often require six (6) months or more, depending on scope and complexity.
Unique Project — Variable
Unique projects fall outside of standard ERP upgrades or changes and may include specialized integrations, enhancements, or custom workflows.
Due to their variability, these projects are evaluated individually based on scope, complexity, and resource requirements. Customers should provide a detailed project outline as early as possible to support feasibility assessment and scheduling.
All unique projects are scheduled within K3S quarterly planning cycles and are subject to resource availability.
Emergency Work
Emergency work is defined as unplanned, critical support required to address disruptions that impact your ability to interact with K3S systems.
Due to the immediate nature of emergency work, it is handled outside of normal project scheduling and is subject to premium rates. While K3S will make reasonable efforts to assist promptly, response times depend on current workload and resource availability.
For emergencies, please contact your designated K3S support representative directly to initiate escalation procedures.
