General Constraints Sample Clauses

General Constraints. Delivery dates for each iterative release of the software (see section 1.3.2 above) were fixed in the description of work and can only be changed with the approval of the project monitoring officer. • Each functional area should have at least one reference open source implementation with the source code published on a widely accessible platform (e.g. GitHub). • Many of the functional requirements are dependent on availability of functionality and services from Europeana • The specification for each functional component is designed to be technology neutral, i.e. it should be possible for the requirement to be met using a number of different technical approaches (e.g. java, .NET, C#, PHP, etc.).

General Constraints.  Delivery dates for each iterative release of the software (see section 1.3.2 above) are fixed in the description of work and can only be changed with the approval of the project monitoring officer.  Each functional area needs to have at least one reference open source implementation with the source code published on a widely accessible platform (e.g. GitHub).  Many of the functional requirements are dependent on availability of functionality and services from Europeana. Unless Europeana is willing and able to make these available in the required timescales, it will not be possible to deliver the required functionality.  The specification for each functional component should be technology neutral, i.e. it should be possible for the requirement to be met using a number of different technical approaches (e.g. java, .NET, C#, PHP, etc.).

General Constraints. The provisions of FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, concerning organizational conflicts of interest govern this contract. Potential conflicts may exist in accordance with FAR 9.505-1, Providing Systems Engineering and Technical Direction, through 9.505-4, Obtaining Access to Proprietary Information. In this regard, the Contractor is responsible for identifying any actual or potential organizational conflicts of interest to the KO that arise as the result of performance under this contract. To avoid or mitigate a potential conflict related to performance under this contract, the KO will impose appropriate constraints when and if required. (FAR 9.505-3).

General Constraints. The following are the general constraints that are to be considered: 3.9.1 Working in an operational environment where machines and equipment are being handled. 3.9.2 Negotiating with Production Managers to arrange planned shutdowns specifics within the contractual interval requirements 3.9.3 Minimizing down periods as production will still be taking place in and around the vicinity of the working area. 3.9.4 Working in areas where there are vehicle and pedestrian traffic. 3.9.5 Accuracy of existing information may be outdated and need to be verified on site prior to proceeding with any work.

General Constraints. As an example, using a buffer hydrogen storage with storage capacity of 1.3 kg H2 (1.85 m3 @ 10 bar) would allow operation of the PEMFC system at maximum net power of 7 kW for approximately 3.35 hours*, while continuous nominal power of 2 kW will be supplied after the storage is emptied. This size of buffer storage would allow also operation at 7 kW maximum net power for up to 2.5 hours straight with bioethanol reformer and PSA unit turned completely off (H2 production 0 kg/h). The final buffer storage size will be set later after determining available commercial storage sizes, FCS pressure reducer characteristics etc. *) H2 consumption for start-up time not considered (<45min) and assuming that the storage can be emptied down to 2 bar (minimum pressure depends on the FCS pressure reducer characteristics)

General Constraints. 2.6.1 Laws and regulations to be complied with

General Constraints. Li ≤ (cm)i i ∈ P (1) Li ≥ (cn)i i ∈ P (2) Li ≤ MYi i ∈ P (3) Xijct ≤ MZijc i ∈ P, j ∈ P, c ∈ C, t ∈ T (4) Constraint (1) denotes that capacity of each plant is set to be less then maximum capacity determined for each plant. Constraint (2) denotes that capacity of each plant is set to be more then minimum capacity determined for each plant. Constraint (3) denotes that if plant i will not be established than there won’t be any capacity assigned for this plant. Constraint (4) denotes that if the link between the plant i and j to transfer the commodity c will not be established then there won’t be flow of the commodity c between these plants.

General Constraints