Article Navigation
Customer Data Quality and Implementation
Customer Responsibility: Customer acknowledges that the quality, accuracy, and completeness of data provided for use in the Asset Management Software as a Service (the Services) are critical to the successful implementation and operation of the Services. The customer shall ensure that all data provided is accurate, current, and free of errors and shall hold CivicPlus harmless from any damages arising out of inaccurate or incomplete data. Timely cooperation from the Customer, including providing access to necessary resources and personnel, is essential for the successful provision of the Services. Delays caused by the Customer may result in adjusted timelines and additional costs.
Impact of Data Deficiencies: CivicPlus is not responsible for delays, errors, or deficiencies in service performance resulting from inaccurate, incomplete, or poor-quality Customer Data. Any additional professional services required to address data issues may result in the Customer being billed at CivicPlus’s then-current rates, to be reviewed and agreed upon before initiation of such services.
Data Format and Standards: Customer shall provide all necessary data in the format and standards specified herein. Failure to comply with these requirements may result in delays or additional costs.
Aerial imagery:
- standard formats: .jpg, .tiff, .mrsid, or .ecw
- georeferenced using a well-known coordinate system (WKID) or well-known text (WKT) definition
Shapefiles (.shp) or geodatabase (.gdb) containing feature and base data:
- objects must contain geometry information
- data must exist in a known coordinate system
- base data layers should be relevant to the software being deployed
Successful conversion of digital feature data (.xls, .mdb, other databases) depends on the data quality.
Attachments (video, photos, as-builts, other documents) must be able to be tied to an individually identifiable feature, activity, or event.
System Configurations
Baseline Configurations: The Services will be provided with standard configurations or the Customer’s reasonably selected configurations, depending on the model included in the SOW. Once the Services go live, Customer acknowledges that any requested reconfiguration by CivicPlus from these baseline configurations may be subject to additional professional services at the expense of Customer.
Configuration Responsibility: The customer is responsible for ensuring that all system configurations, including user roles, workflows, and permissions, align with their operational requirements. CivicPlus is not liable for any inaccuracies, inefficiencies, issues, or failures resulting from inputs, configurations, or customizations, whether Customer-defined or approved.
Testing and Validation: Upon finalization of the implementation of the Services, CivicPlus will provide the Customer with an environment for testing. The customer is responsible for testing and validating all configurations before deployment. Once the Customer’s instance of the Services is deployed, any additional reconfiguration will be at the cost of the Customer.
Third-party API Integrations
Third-Party API Compatibility: CivicPlus provides API integration capabilities to facilitate interoperability with third-party systems. The customer acknowledges that CivicPlus does not guarantee compatibility with all third-party APIs. CivicPlus is not responsible for disruptions caused by changes to third-party APIs. The customer shall bear the cost of any necessary adjustments to maintain integrations.
API Usage Limits: Customer agrees to comply with applicable acceptable use policies and usage limits specified for API calls, including without limitation, [CivicPlus’ Proprietary API Acceptable Use Policy]. Excessive use or misuse of APIs may result in additional fees or suspension of access.
CivicPlus is not responsible for the performance, availability, or maintenance of any third-party API integrations once such an API call exits the Services. Any disruptions, errors, or failures occurring in third-party systems or services are solely the responsibility of the respective third-party provider. The customer acknowledges and agrees that CivicPlus bears no liability for any issues arising from such external API interactions.
Risk Allocation for Services Use
Operational Risks: Customer acknowledges that the Services are a tool to support asset management and maintenance activities and does not replace professional judgment or decision-making. The Customer is responsible for implementing appropriate mitigation measures, including backup procedures and contingency plans, to address potential risks associated with reliance on the Services.
Custom Workflows and Processes: The customer acknowledges that custom workflows or processes implemented in the Services may carry additional risks. CivicPlus shall not be responsible for outcomes resulting from Customer-defined workflows.
In-Article Glossary
Review the Help Center Glossary, a comprehensive explanation of the acronyms, abbreviations, and company-specific terminology. The terms located in this section are listed alphabetically:
- API: Application Programming Interface
- SOW: Statement of Work
Comments
Let us know what was helpful or not helpful about the article.0 comments
Article is closed for comments.