My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25B - AGMT - PD SOFTWARE SYS
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2015
>
11/17/2015
>
25B - AGMT - PD SOFTWARE SYS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/12/2015 2:33:31 PM
Creation date
11/12/2015 1:58:24 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Item #
25B
Date
11/17/2015
Destruction Year
2020
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
204
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
The Client is responsible for obtaining the API for each of the third party vendors that TriTech applications <br />are interfacing with. The API must be for the version of the third party software that TriTech will be <br />interfacing with. The timelines for providing these documents to TriTech is concurrent with development of <br />the OSD, so that any limitations associated with the level of integration with the third party application call <br />be taken into consideration. <br />Upon approval of the OSD the custom interfaces are developed by TriTech engineering team. Once <br />developed, these interfaces will be installed on Client equipment and go through testing with the Client and <br />applicable third party vendors who own and administer the vendor side of the interface. <br />The Client is also responsible for coordinating execution of a mutual Non- Disolosure Agreement (NDA) <br />between the third party vendors and TriTech before any technical information or documentation can be <br />exchanged or testing can commence. <br />Note t: The Client's provision of Imerface requirements for each of the Custom Interfaces is atr early <br />Project checkpoint. This information is needed to develop the OSDs for Custom Interfaces. <br />Incomplete, inaccurate, or delayed infornation can have a cascading effect on the Project <br />Schedule, and riiay result in a'sir Iornt delay in in ofthe projOct. <br />Note 2: The Client is responsible for providing Application Programming Interface (API) <br />documentation for the Third Party Systems, The APT must document the integration process <br />for the level of interface integration defined by TriTech's response to the RFP. The Client is <br />responsible for any services or software needed from such Third Party Systems to allow for <br />integration with the third party system: <br />Note 3: The scope of functionality for the custom interfaces is limited to 1) the capability of the <br />THTeolr System being interfaced and 2) the Application Programming Interface (API) ' <br />------c�ap±lities of the external system being interfaced. <br />Note 4: High level descriptions of each of the custom interfaces in Appendix D - Custom TriTech <br />Interfaces; will become the basis for the scope. of detailed requirements;'describod in the <br />OSD. Any changes in the requirements documented in the System OSDs, post approval of <br />the OSDs are subject to formal Change Order, <br />Note 5: The Client is responsible for coordinating the development of the vendor side of all interfaces <br />to the third party applications for the interfaces that the vendor is not a TriTech <br />Subcontractor, based on the Purchase Agreement. <br />Note 6: TriTech is not responsible for any cost associated for the API, any required third party lab or <br />certification testing, cost associated with required programming or custom work by the third <br />party vendors, or any license fees that may be required by the third party vendors. <br />62 <br />25B -109 <br />
The URL can be used to link to this page
Your browser does not support the video tag.