Software Interface Sample Clauses
POPULAR SAMPLE Copied 3 times
Software Interface. Provider will provide sufficient specifications to Buyer to enable Buyer to build an electronic data interface compatible with Provider’s patient accounting system so that Buyer can receive data from Provider. The parties acknowledge and accept that the development of the interface system is based on information given by the Provider during the application and development processes as outlined in the A/RxMed Medical Data Analysis which is attached as Exhibit H. The Provider acknowledges that inaccuracies and/or omissions in the information provided for the interface specifications will affect the funding provided for the Provider pursuant to this Agreement. Neither Buyer nor its Processor will be liable for any consequences of inaccuracies and or omission of information, regarding the interface specifications. The Provider will be given the opportunity to review the specifications that will be used to develop the interface. The Buyer and its Processor will make a reasonable effort to ensure that the information being sent by the Provider is interpreted accurately and timely. In the event that a processing error occurs or that a correction is required of the interface, it is understood by all parties that:
(a) the Buyer and its Processor are only responsible for correcting the errors that it made to the extent that the remedy is reasonable and that no further liability exists;
(b) any required correction to the interface or its operation that is the responsibility of the Buyer or its Processor will be corrected, to the extent that the remedy is reasonable, at the Buyer’s expense;
(c) any correction to the interface or its operation that is due to incorrect interface specifications and or omissions in the interface specifications given to the Buyer or its Processor by the Provider will be corrected, to the extent that the remedy is reasonable, at the Provider’s expense;
(d) any corrections to the interface or its operation are billable by the Buyer or its Processor at $200.00 per hour and;
(e) the Buyer and its Processor will make the determination of who is at fault regarding any required corrections to the interface.
Software Interface. A. The parts provider must interface with the City’s Fleet Management Information System (FMIS), Collective Data.
B. Any costs of interface with the City’s software provider shall be borne at the provider’s expense. The Contractor will staff the Fleet Maintenance Facility Parts Warehouse Monday through Friday between the hours of 6:30 a.m. to 11:00 p.m., Saturday 8:00 a.m. to 3:30 p.m., and as directed by the Fleet Manager or designee during a declared emergency. The Contractor will own the parts and supplies inventory in the Parts Warehouse to satisfy the City’s Service Level Agreement. To satisfy the City’s non-stocked requirements, the Contractor’s on-site staff will purchase those items from local, regional, or national sources in order to satisfy the City’s requested brand, immediacy of need, or price point. The Contractor will purchase third-party provided services such as tire mount/balance, glass repair/replacement, body work, engine overhaul, etc. from City identified vendors at prices negotiated by the City. The Contractor’s on-site stocked inventory will be tailored to support the City’s fleet configuration and will be adjusted based on changes to the fleet configuration via inventory level setting driven by historical demand and through frequent communication with City maintenance personnel. The Contractor will consult with the Fleet Manager to determine which items are to be stocked. The Contractor will provide competitively priced parts that meet or exceed Original Equipment Manufacturer (OEM) standards or better and the Contractor will source parts and supplies for all of the City’s fleet maintenance related material requirements. When directed by the City, the Contractor will furnish retread, rebuilt, refurbished, recycled, or refined products that meet or exceed OEM, SAE, UL, Mil-spec, ANSI, or other industry quality standards required by the City. The Contractor will manage and ship core returns for credit for items such as water pumps, alternators, starters, and engine blocks in addition to disposing and/or recycling batteries, tires, antifreeze, motor oil, and grease. The Contractor will charge the City a firm fixed price for their service to be invoiced monthly, following the month of performance, as prescribed on the following page. The firm fixed price management fee is predicated on the Contractor staffing one Parts Warehouse for two (2) shifts conducting approximately $2.4 million in annual parts and supplies sales. If the City inc...
Software Interface. Customer acknowledges that ▇▇▇▇▇’▇ will be using a third party to provide imaging software and certain data consolidation and transmission services.
Software Interface. Here we describe the batch interface (i.e., an R script) for the software for the landslide susceptibility zonation. In this section we will first describe the input data specifications (Section 3.1), including within that section a complete list of the files required for the susceptibility analysis is specified in (Table 1). We then describe the configuration parameters (Section 3.2). To be executed the software requires the download of the source code, consisting of a textual file “SusceptibilityAnalysis_vX_YYYYMMDD.R” (where X is the software version and YYYYMMDD the release date) and two configuration files, both described in Section 3.2 containing (i) the parameters controlling directly the susceptibility analysis (“configuration.txt”), and (ii) the parameters for the spatial data configuration (“configuration_spatial_data.txt”).
Software Interface. The general graphical layout of fiberdesk is shown in Fig. 3.1.
Fig. 2.1 fiberdesk: graphical interface layout.
2.1). Its structure is comparable to a menu, but with advanced features and easier access to the command structure. It is explained in section 3.1. Beside the main view, additionally information and setups are displayed in four attachable windows. These four windows are the propagation window, the measured value window, the output window and the graph window. More details can be found in section 3.2.