General requirements to infrastructure and platform No Sample Clauses

General requirements to infrastructure and platform No. Requirement Importance (O/H/M/L) Describe T 27 The Contractor should describe all relevant components (operating system, client applications, database platform, web servers, server software, third party components, etc.) that are not provided as a part of the system, or that deviate from the Customer's standards. Note: This may include web browser, browser extensions, web server, database platform, Java, Flash, Silverlight, Microsoft Office, .NET Framework, C++ Redistributable, MDAC, etc. The Contractor is asked to clarify the component’s purpose, in addition to Contractor, component name and version of the components for all parts of the system. H D T 28 The system should be established without dependencies on specific versions of Microsoft Office on the Customer's client platform. The Contractor is asked to clarify any dependencies, the purpose of the dependency, product in the Office package and version required. Note: Dependencies to products in the Office package are not desirable, as it poses challenges to maintenance and upgrades of the Office package on the Customer’s client platform. H D T 29 The client applications should run without the use of Java runtime, ActiveX controls, Flash, Silverlight or browser extensions installed on the Client PC. In the event of needs, this must be described and justified. Note: Due to security reasons, the Customer does not permit local installations of Java runtime on client PCs. Java runtime may be enabled for applications distributed through App-V (virtualised), but it is preferable to avoid this. It is preferable to avoid dependencies on ActiveX controls, Flash and Silverlight, as these have already lost or are in the process of losing support in modern web browsers. H D No. Requirement Importance (O/H/M/L) Describe T 30 The system should maintain support for N and N-1 life cycle for all of the system’s components. The Contractor is asked to clarify such support, and describe methodology to ensure that the system is updated to support new versions. Note: For example, this applies to components and services: • provided by the Customer’s service provider, and not part of the delivery of the system • provided by the Contractor as part of the system • provided by a third party H D T 31 All components included in the system shall synchronise time with a central NTP server in the Customer’s technical platform. H T 32 The system must have support for Norwegian characters, for example UTF-8 or ISO/IEC 10646. H
AutoNDA by SimpleDocs

Related to General requirements to infrastructure and platform No

  • General Requirements The Contractor hereby agrees:

  • Monitoring Compliance with Contract For purposes of monitoring the District’s compliance with this contract, the Department may require the District to provide information or may conduct site visits as needed.

  • Personnel Requirements and Documentation Grantee will;

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Provide Data in Compliance with Applicable Laws LEA shall provide Student Data for the purposes of obtaining the Services in compliance with all applicable federal, state, and local privacy laws, rules, and regulations, all as may be amended from time to time.

  • Provide Data In Compliance With Laws LEA shall provide data for the purposes of the DPA in compliance with the FERPA, PPRA, IDEA, 603 C.M.R. 23.00, 603 CMR 28.00, and Massachusetts General Law, Chapter 71, Sections 34D to 34H, and the other privacy statutes quoted in this DPA. LEA shall ensure that its annual notice under FERPA includes vendors, such as the Provider, as “School Officials.”

  • Federal Requirements Pertaining to Grants and Subrecipient Agreements A. Requirement to Have a Single Audit: In the case that this Agreement is a Grant that is funded in whole or in part by federal funds, the Subrecipient will complete the Subrecipient Annual Report annually within 45 days after its fiscal year end, informing the State of Vermont whether or not a Single Audit is required for the prior fiscal year. If a Single Audit is required, the Subrecipient will submit a copy of the audit report to the granting Party within 9 months. If a single audit is not required, only the Subrecipient Annual Report isrequired. For fiscal years ending before December 25, 2015, a Single Audit is required if the subrecipient expends $500,000 or more in federal assistance during its fiscal year and must be conducted in accordance with OMB Circular A-133. For fiscal years ending on or after December 25, 2015, a Single Audit is required if the subrecipient expends $750,000 or more in federal assistance during its fiscal year and must be conducted in accordance with 2 CFR Chapter I, Chapter II, Part 200, Subpart F. The Subrecipient Annual Report is required to be submitted within 45 days, whether or not a Single Audit is required.

  • Compliance with Audit and Reporting Requirements; Maintenance of Records A. The Grantee shall submit to an audit of funds paid through this Grant Agreement and shall make all books, accounting records and other documents available at all reasonable times during the term of this Grant Agreement and for a period of three (3) years after final payment for inspection by the State or its authorized designee. Copies shall be furnished to the State at no cost

  • Provide Data In Compliance With FERPA School Unit shall provide data for the purposes of the Service Agreement in compliance with FERPA, COPPA, PPRA, IDEA, MSIPA, and MUSER and all other Maine privacy statutes and regulations referenced or identified in this DPA.

  • CERTIFICATION PROHIBITING DISCRIMINATION AGAINST FIREARM AND AMMUNITION INDUSTRIES (Texas law as of September 1, 2021) By submitting a proposal to this Solicitation, you certify that you agree, when it is applicable, to the following required by Texas law as of September 1, 2021: If (a) company is not a sole proprietorship; (b) company has at least ten (10) full-time employees; (c) this contract has a value of at least $100,000 that is paid wholly or partly from public funds; (d) the contract is not excepted under Tex. Gov’t Code § 2274.003 of SB 19 (87th leg.); and (e) governmental entity has determined that company is not a sole-source provider or governmental entity has not received any bids from a company that is able to provide this written verification, the following certification shall apply; otherwise, this certification is not required. Pursuant to Tex. Gov’t Code Ch. 2274 of SB 19 (87th session), the company hereby certifies and verifies that the company, or association, corporation, partnership, joint venture, limited partnership, limited liability partnership, or limited liability company, including a wholly owned subsidiary, majority-owned subsidiary parent company, or affiliate of these entities or associations, that exists to make a profit, does not have a practice, policy, guidance, or directive that discriminates against a firearm entity or firearm trade association and will not discriminate during the term of this contract against a firearm entity or firearm trade association. For purposes of this contract, “discriminate against a firearm entity or firearm trade association” shall mean, with respect to the entity or association, to: “(1) refuse to engage in the trade of any goods or services with the entity or association based solely on its status as a firearm entity or firearm trade association; (2) refrain from continuing an existing business relationship with the entity or association based solely on its status as a firearm entity or firearm trade association; or (3) terminate an existing business relationship with the entity or association based solely on its status as a firearm entity or firearm trade association. See Tex. Gov’t Code § 2274.001(3) of SB 19. “Discrimination against a firearm entity or firearm trade association” does not include: “(1) the established policies of a merchant, retail seller, or platform that restrict or prohibit the listing or selling of ammunition, firearms, or firearm accessories; and (2) a company’s refusal to engage in the trade of any goods or services, decision to refrain from continuing an existing business relationship, or decision to terminate an existing business relationship to comply with federal, state, or local law, policy, or regulations or a directive by a regulatory agency, or for any traditional business reason that is specific to the customer or potential customer and not based solely on an entity’s or association’s status as a firearm entity or firearm trade association.” See Tex. Gov’t Code § 2274.001(3) of SB 19.

Time is Money Join Law Insider Premium to draft better contracts faster.