Customisation. (i) You and your IT providers may access any VPC assigned to your Staff in respect of a Full Time Service at any time during the term of the Service and may install and configure any software you require, provided you have a valid and current licence for the software and provided that the software is not, or does not contain, malware.
(ii) You may assign hardware to be used by your Staff. If you do so, it is entirely at your own risk. You are responsible for delivery of the hardware to the Staff, its safety while being used by your Staff and its return to you at the end of the Service.
(iii) You may request us to supply additional software or hardware. We will identify whether we can supply the requested items and if so, the price we will charge you to add that item to your Service. If you agree, we will supply the requested Hardware and/or Software for the term of the Service. The software/hardware will remain ours at the end of the Service.
Customisation. One of the best parts of MISP, is the possibility of adding new features using “MISP modules”. These modules are autonomous modules that can be used for expanding the functionalities of the platform, as well as to import and export data. Currently there is a list of an available modules that enables integration with well-known cybersecurity tools such as Shodan, Yara, VirusTotal or event Maltego, that can be used for further analysis of attacks. An example is presented in Figure 22: Besides this official list of MISP modules, organisations can develop their own modules for integrating MISP with their tools and adapt it to their cybersecurity processes and technologies.
Customisation. We shall undertake the customisation of Application to the specifications and requirements and for the cost as described in the Enterprise Proposal (if any) and as may otherwise be agreed by You and Us in writing.
Customisation. (a) If applicable, in consideration of the Driver Partner’s payment of the Security Deposit, The Company will provide the Customisation Services to Diver Partner.
(b) The Company will make reasonable efforts to deliver the Customisation Services to the Driver Partner within the timeframe mutually agreed by The Company and the Driver Partner.
(c) The Driver Partner acknowledges that some backend components of the System cannot be rebranded, including for code manageability purposes, and will continue to bear The Company’s logo, trade marks or name (and not the Driver Partner’s branding).
Customisation. (a) You grant us a licence to use the Customer IP provided by you for the purpose of us providing the Customisation Services under this Agreement, including the right to use, reproduce, modify and create derivative works of the Customer IP.
(b) You must ensure that we are permitted to use any third-party information or intellectual property rights contained in the Customer IP that you provide to us for use in the provision of our Customisation Services and Software.
(c) You acknowledge that all intellectual property rights in the customised Software are owned by us, except for the Customer IP provided under the licence of this Agreement.
Customisation. 5.1. Customisation is not included. In joint consultation and with a suitable business case the Provider and the Customer may agree that the Provider will customise the Platform in accordance with certain specifications (each a Customisation) to be separately agreed in writing between the Parties.
5.2. From the date when a Customisation is first made available to the Customer, the Customization shall form part of the Platform under the Agreement, and accordingly from that date, the Customer’s rights to use the Customization shall be governed by this Agreement.
5.3. The Customer acknowledges that the Provider may make any Customisation available to its other Customers, unless a separate commercial agreement is in place, in which case different terms may apply.
5.4. Processes and procedures for requesting and implementing each of the different types of customisations or integration are laid out in the manual and/or Service Level Agreement.
Customisation. 8.1 From time to time during the Licence, the Licensee may request RELIANSYS to provide Customisations to the Software. RELIANSYS will use its best endeavours to provide the Customisation. If RELIANSYS agrees to provide a Customisation requested by the Licensee, it must advise the Licensee of the Customisation Fees, estimated time and other terms on which it offers to provide such Customisation. If the Licensee accepts (in writing) the terms offered by RELIANSYS, RELIANSYS must provide the Customisation on terms offered and in accordance with this Agreement.
8.2 Where Customisation of the Software is requested, and agreed to by RELIANSYS, the Licensee must pay the Customisation Fee in accordance with the terms agreed with RELIANSYS.
8.3 All Customisations remain the property of RELIANSYS.
Customisation. Given that the system is built around HTML using the HTTP protocol, this allows the user to completely customise the look and feel of all HTML pages and reports. Each report that is produced by the system consists of a header, the body (containing the information), and a footer. Whilst the body is customised by the parameters that are passed to the report, the header and footer remain constant and can be edited using any HTML editor such as, amongst others, Microsoft FrontPage. Each report has an ID number, as follows: Report Name ID Custom Report 1 Billing Report 2 Organisation Drill-Down 3 Trunks Busy 4 Call Geography 5 Top Calls 6 Incoming Response Analysis 7 Dialled Numbers Report 8 Using these ID numbers, header and footer files can be created in the \data folder in the form customheader_x.html and customfooter_x.html, where x is the ID number of the report whose output you want to customise. For example, suppose we wanted to add your company name to the heading of each telephone bill you produce. We know that a telephone bill is a Billing Report whose ID is 2. The custom header would therefore need to be a standard HTML file in the \data folder named customheader_2.html. The raw HTML for such a file may look something like the following: This example uses server-side includes (SSIs) which are explained later in this section. The example code would produce an output similar to the following: When creating header and footer files, it is important to remember that the system constructs the final report from three bits of HTML – the header, the body, and the footer. Whilst it is not essential for some web browsers, you should stick to the HTTP specification where an HTML page is completely housed in a pair of <HTML> </HTML> tags. This means that the report, taken as a whole consisting of all three parts, collectively subscribes to this convention. Your header should contain the <HTML> tag, whilst your footer should contain the </HTML> tag. The system constructs reports in this way to allow maximum flexibility. For example, the whole report may be indented by having a <BLOCKQUOTE> tag in the header and a </BLOCKQUOTE> tag in the footer. The resultant report, including the body, will therefore be indented.
Customisation. Glotelligence will not be responsible for any defect or failure in the Optimiser Touchpoint services caused by the Customer’s customisation. The Customer acknowledges and agrees that the Customer is responsible to conduct quality and security testing of the Customer customisation by performing bug elimination, simulations and integration with other customer systems. Should the Customer fail to implement changes to Customer customisation required by the Optimiser Touchpoint framework, the Customer may need to buy additional Optimiser Touchpoint development support. Any Development Consultant(s) appointed by the Customer under these terms works expressly and exclusively at the Customer’s direction and the Customer is responsible for any acts or omissions of such Development Consultant(s). Glotelligence may deny access to any Development Consultant it deems is adversely impacting the Optimiser Touchpoint services or other Optimiser Touchpoint customers. References to the Customer in these terms refer to both the Customer and its development consultant(s).
Customisation. In consideration for the creation, installation and the configuration of the Wal-Mart Site and the Branded Environment and the rendering of other services and the supply of other products related thereto, Wal-Mart shall pay PhotoChannel the amount of $______ (collectively, the "CUSTOMISATION FEE").
