Motion Analytics delivers exceptional private AI deployments by maintaining clear integration boundaries and change management processes. This policy ensures quality delivery while protecting both parties from scope creep and miscommunication throughout your AI implementation.
1. Deployment Scope Definition. Your deployment scope is defined in the signed Statement of Work (SOW) and includes specific deliverables, AI model configurations, data source integrations, security architecture, and timeline. Any work beyond the original scope constitutes a change order, regardless of perceived complexity or time required.
2. What Constitutes a Change Order. Change orders include but are not limited to: additional data sources or system integrations, new AI workflow modules or capabilities, modified security architecture or compliance configurations, extra user roles or access permissions, additional compliance certification support, revised model training requirements, and any "while we're at it" requests during deployment.
3. Change Order Process. All change requests must be submitted in writing via email to info@motionanalyticstech.com. We will provide a written estimate including time, cost, and timeline impact within 3 business days. Work begins only after written approval and 50% deposit on the change order amount.
4. Pricing and Billing. Change orders are billed at $150/hour with a 4-hour minimum. Rush changes (requested during the final week of deployment) incur a 100% premium. Payment for change orders is due before work commences — no exceptions.
5. Timeline Impact. Change orders may delay deployment go-live. We will communicate any timeline adjustments in the change order estimate. Original deployment deadlines are adjusted accordingly and do not constitute a breach of agreement.
6. Client-Requested Delays. If deployment work is paused due to client IT team unavailability, delayed infrastructure access, or pending security approvals for more than 10 business days, the project moves to "on-hold" status. Resumption requires 5 business days notice and may affect final go-live dates.
7. Feedback and Revision Cycles. Each deployment phase includes one round of revisions based on the original scope. Additional revision rounds beyond scope are considered change orders. Feedback must be consolidated and provided within agreed timeframes to maintain the deployment schedule.
8. Third-Party Dependencies. Delays caused by third-party infrastructure providers, client IT or security teams, or external compliance auditors do not constitute deployment delays on our part. Additional time required due to these dependencies may incur additional charges at standard hourly rates.
9. Final Delivery and Sign-Off. Deployments are considered complete upon delivery of all items specified in the original SOW, including successful security validation and compliance sign-off. Client has 10 business days to request corrections to work that does not meet original specifications. After sign-off, any additional requests are handled under our Support Plans.