Best Practice and Standard Workflow. First Due intends to meet the organizational needs of the Customer and their respective software requirements by configuring the Purchased Products to closely align with existing workflows. Although First Due is incredibly flexible, there may be times when First Due recommends using standard functionality or best practice to ensure a timely implementation, and simplification of current process. These workflows may differ from Customer existing workflows. Customer understands the importance of collaboration to achieve the ultimate goal of successfully adopting the Purchased Products and is aware there may be changes to existing workflow to accomplish this.
Best Practice and Standard Workflow. First Due intends to meet the organizational needs of the Customer and their respective software requirements by configuring the Purchased Products to closely align with existing workflows. Although First Due is incredibly flexible, there may be times when First Due recommends using standard functionality or best practice to ensure a timely implementation, and simplification of current process. These workflows may differ from Customer existing workflows. Customer understands the importance of collaboration to achieve the ultimate goal of successfully adopting the Purchased Products and is aware there may be changes to existing workflow to accomplish this. Go-live Requirements & Gaps Over the course of the Implementation, both parties may uncover functionality gaps in the Purchased Products. Some of these gaps may have a material impact on the ability to implement or adopt the product. Gaps of this nature, deemed Go-Live Requirements, will be prioritized to ensure a timely go-live and project completion. However, in the case that certain features are not complete before go-live, they will be added to module and system signoffs as exceptions and will be completed within an agreed upon timeframe.
