Custom Solutions Clause Samples
The "Custom Solutions" clause defines the terms under which a provider delivers tailored products or services to meet a client's specific requirements. Typically, this clause outlines the process for gathering client needs, developing unique features or integrations, and setting expectations for delivery timelines and costs. Its core function is to ensure both parties understand the scope and limitations of bespoke work, thereby reducing misunderstandings and clarifying responsibilities during the customization process.
Custom Solutions. If You require Us to perform for You certain professional services, custom development work, which is not included in the definition of Maintenance and Support under Our Maintenance and Support Terms of Service, or provide other Custom solutions, You will need to request such Additional Work by submitting an Order. You will be charged for such Custom solutions at Our then current rates and such Custom solutions will be subject to the terms of Our CSTs which form a Schedule to this Agreement.
Custom Solutions. ● Are interface changes needed? If so, how will change be managed and tested? ● Include software architecture diagrams of the system(s). ● If the proposal calls for in-house software development, what is the proposed software management approach (i.e., Agile, Waterfall, Kanban)? ● How will version control be managed? ○ If the proposal calls for in-house software development, what will the culture of Code Reviews be? ● Describe Unit Test Coverage goals, if applicable. ● How will Dev, Staging, and Production environments be established and maintained? ● What software language(s) and services (i.e., cloud services, open- source software frameworks) will be used, and how will this impact maintainability? ● What are the standards for documentation? Will Interface Control Documents (ICDs) be established? ○ An ICD determines the format of various subcomponents of the system that will communicate with each other and the schemas of database records.
Custom Solutions. ● Describe how the system was built to be “testable” in the architecture. How will this pattern be enforced during development? ● When and how will you define and document test cases? Identify the chosen QA Testing platform, if applicable. ● How will QA be managed and staffed? If you plan to continue feature development, how will this process be maintained?
Custom Solutions. If the Port selects a solution that is considered a custom solution, the approach described in
Custom Solutions. Unitrends may provide, at its discretion and if feasible, Custom solutions to meet a Customer’s unique business requirements. Custom solutions are provided by Unitrends pursuant to the Unitrends Professional Services Agreement and Customer will be required to enter into Unitrends’ Professional Services Agreement and a Statement of Work thereunder prior to Unitrends providing any Custom solutions for Customer. If Unitrends agrees to provide Custom solutions requested by Customer, Unitrends will submit to Customer a Statement of Work describing, among other things, the responsibilities of the parties, the Custom solution requirements, and an estimate of the fees payable by Customer for such Custom solution. Customer must authorize, in writing, the implementation of the Custom solution before Unitrends will implement the Custom solution. Any Custom solution implemented for a Customer remains Custom, is not covered by Technical Support, and is supported by Unitrends as a one-off solution at Unitrends’ then-current Professional Services rates, until such time, if any, as the features or functions provided by the Custom solution is included by Unitrends, in its sole discretion, as a part of the Supported Software.
Custom Solutions. To support the phases outlined in the Section 2.4 Scope of Work, the Maritime PortConnect System architecture will be established to connect internal and external data sources. This will require building a data warehouse and necessary data processes/services to manage ingress, egress, and reporting. Descriptions of the data sources, data processes/services, data warehouse, and technology to be used are identified in APPENDIX C (Custom Solutions – Maritime PortConnect System Architecture) and are summarized in Figure 7.
Custom Solutions. Using the combination of above rules, many topologies can be simplified. However, if the Feynman diagram does not contain a triangle, a diamond, an insertion, or a carpet, the IBPs have to be solved manually. One well-known example is the reduction of the three-loop non-planar diagram [43], which paved the way for fast three-loop reductions. Let us consider a straightforward example with a system of two equations:
1) Z(n1, n2, n3) = n1Z(n1 − 1, n2, n3) + Z(n1, n2 + 1, n3)
2) Z(n1, n2, n3) = n3Z(n1, n2, n3 − 1) + n2Z(n1, n2 + 1, n3) (36) Here we see that we have two terms that only increase indices without lowering any others, highlighted in bold. These terms have to be removed in order to have a reduction scheme that, when repeatedly applied, always lowers one of the indices. Solving it analytically, we get:
1 − n2 Z(n1, n2, n3) = 1 n3Z(n1, n2, n3 − 1) − n1n2Z(n1 − 1, n2, n3) (37) This rule can be applied until n2 = 1 or until n1 = 0 or n3 = 0, since the latter cases mean we have removed a propagator. The next step would be to solve Z(n1, 1, n3), since any configuration with n2 > 1 will have n1 = 0 or n3 = 0. In general, it is quite difficult to solve these systems parametrically. Therefore, many computations are performed using the ▇▇▇▇▇▇▇ method [42, 94, 95, 100]. In its basic form, each parameter is substituted by a number, and every configuration is solved separately. The solutions to the system are brute force Gaussian eliminations, which is a time consuming process. The ▇▇▇▇▇▇▇ system above for Z(1, 2, 1) looks like:
1) Z(1, 2, 1) = Z(0, 2, 1) + Z(1, 3, 1)
2) Z(1, 2, 1) = Z(1, 2, 0) + 2Z(1, 3, 1) ⇒ Z(1, 2, 1) = 2Z(0, 2, 1) − Z(1, 2, 0) . (38) If we had to solve Z(2, 2, 1), we would have to solve the system of eq. (36) for Z(2, 2, 1) and for Z(1, 2, 1). Some topologies are called master topologies: these cannot be guaranteed to get a line removed through IBPs, and they have to be solved using different methods. An example is the simple system above, that could be used to reduce n2 to 1, but not to