and D5. 7, where an employee has applied for leave without pay or leave at reduced pay with insufficient notice to allow pay adjustments to occur during the period of leave, the salary adjustment will be made to the next available pay, unless there are extenuating circumstances, and the employee will be notified of such an adjustment.
and D5. 3 are related to training programmes templates and examples. Some of these examples may become “Sectorial Flagship Programmes” as described before. Deliverable D5.4 should be the outcome of in-depth analyses of best practices, referred to the main elements of the template (business-model and academic-model elements). Some measures and recommendations from D5.4 will be applicable to the BSDE itself, while others will be addressed to other agents, such as administrations, companies and training providers. Id Title (report) Leader Due Description D5.1 Specification, conceptual design and application to the partial results compiled from other work packages COMILLAS 24 It will contain a consolidated view of the skill gaps, the stakeholders and the current policies and requirements, assessing and stressing the ones with the highest usefulness to define the BSDE and providing an initial draft view on how this can be applied to build the blueprint D5.2 Intermediate draft templates for educational programs KTH 24 This deliverable contains the pre‐design of education programmes, initial and continuous training activities D5.3 Final education programmes and training activities KTH 36 This deliverable contains the main results of the works in T5.2, i.e., education programmes, initial and continuous training activities, together with their expected relative impact in the correction of skill gaps. D5.4 Recommendations on how to improve the educational frameworks in the focus countries COMILLAS 43 This deliverable will contain the list of actions identified to improve the educational frameworks. The report will present the results covering a set of focus countries in representative regions, so that these results can also be applied to other countries with similar characteristics. The pre‐defined focus countries are Germany, Spain, Sweden, Greece D5.5 BSDE presentation and strategic roadmap for the deployment of the action plans COMILLAS 48 This report will present the priorities assigned to each of the actions defined in the previous tasks. Based on these priorities, the report will propose a strategic roadmap for their deployment. The results of the pilot will be compiled and analysed to determine if corrective actions to the roadmap are required, according to the scheme proposed in Figure 1 Figure 9. Description of deliverables in WP5 Figure 10 gathers in the same planning diagram: • In yellow, the different WPS of XXXXX • In light blue, the original tasks WP5, from th...
and D5. 1.3 the MSCs for an IEC 61508 compliant hypervisor, partition, COTS device and mixed-criticality network are defined. Those MSCs and the analysis of the IEC 61508 compliant safety standard have given rise to the identification of common sources of issues related to the mixed-criticality system architectures and its components (e.g., COTS device, hypervisor, partitions and mixed-criticality network). In the following subsections the identified issues for mixed-criticality systems are analysed. Section 3.1 analyses the challenges related to COTS multi-core devices. Section 3.2 analyses the issue of hypervisor based virtualization mechanisms, instead, Section 3.3 analyses the issues related to the mixed-criticality networks implemented on today’s mixed-criticality systems.
and D5. 1 The outcomes of D 4.1, D4.2 and D5.1 (previously issued) have proved very valuable. State of the art and guidelines for standards applicable (D 4.1) is an analysis of a wide range of standards selected on the basis of their potential application, to ARROW; Guidelines for technical interoperability (D 4.2) and Analysis of bibliographic resources and clearing mechanisms existing in Europe (D 5.1) analyse the existing databases of the three domains (Libraries, BIPs and RROs). These three deliverables provided key information about the metadata content of each domain’s databases, the structure and organisation of this metadata in the different databases, the existing exchanges between these databases, the standards and protocols used for these exchanges and an overview of the local interconnections between the 3 domains in each partner country. The deliverables D4.1, D4.2, D5.1 provided the real background to the message definition. In the light of their content, practical solutions to ensure interoperability and scalability were made: the choice of international standards including standard identifiers, XML structure, MARC21 format in the Library Domain and ONIX based formats in the BIP and RRO domains, the choice of The European Library (TEL) as unique access point for the National Libraries, and the selection of countries which have the most suitable infrastructure to engage with ARROW prototyping: Germany, UK, Spain, France. It was identified, for example, that different BIPs already support different web- service-based request/response protocols for data exchange, and that ARROW may need to adopt different protocols for different BIPs, in which case the development of the standard message becomes part of the "reference architecture" rather than being an implemented message. Moreover, to comply with specific national context, 2 variants of the workflow have been designed: following Workflow A, ARROW queries the BIP and the RRO separately, while following Workflow B, ARROW only queries the RRO (which also manages the BIP data). These early decisions have been reflected in the message choreography and structure. These 3 deliverables were essential for defining the workflow and designing the architecture as described in D 5.2 Specification of right information infrastructure issued in December 2009.
and D5. 1. The results from this report can also be used by institutions to assess how well their own access services meet the identified user needs.
and D5. 7, where an employee has applied for leave without pay or leave at reduced pay with insufficient notice to allow pay adjustments to occur during the period of leave, the salary adjustment will be made to the next available pay, unless there are extenuating circumstances, and the employee will be notified of such an adjustment. Any outstanding money owing to CIT when an employee ceases employment is to be recovered by deduction from any final entitlements payable to the employee. If a debt still exists further debt recovery action is to be taken unless the Chief Executive: directs the recovery be waived, in part or in full, based on evidence provided by the employee of exceptional circumstance or that such recovery would cause undue hardship; or determines that an overpayment is not recoverable. Where the Chief Executive determines that an overpayment is not recoverable, the provisions of CIT’s Financial Instructions, relating to the waiver and write off of monies, will apply.
and D5. 2.1) was successful during our experiments. The use of the Eclipse extension point mechanism even allows to add additional analysis tool without the need of changing or recompiling OptiPAL. However, if the external analysis tool exists outside the Eclipse/Java environment, a significant run-time overhead has to be expected for exporting the model for each architecture candidate to be assessed and for importing the analysis results into OptiPAL (but see conclusion below). In our experiments we covered this case for the dependability objective, because HipHops is a native Windows application. Feasibility of EAST-ADL’s Variability Modeling Concepts During the MAENAD optimization case study, the EAST-ADL language elements for modeling variability provided an effective means to define all variability encountered in our model. On the one hand, this shows that EAST-ADL has effective language constructs for modeling non-trivial system variability in general, on the other hand (and more important to MAENAD) this shows that the EAST-ADL variability modeling mechanisms can also applied to design space variability, i.e. for defining the set of architecture alternatives to be considered during an architecture optimization (definition of the optimization space). Before the MAENAD project, this was not an intended purpose of EAST-ADL variability modeling, but our experiments indicate that it can be used for that. Relation of Design Space and Product Line Variability Within a Single EAST-ADL Model
and D5. 1/D6.1top-level components, and transfer of the components of D4.1 to the PICOS View Model. As part of this step, components roles and descriptions and were analysed, including divergence between D4.1 and D5.1/D6.1, and where appropriate refined. Re-assessment of the relationships between components at the top level, including alignment between D4.1 and D5.1/D6.1. Recording of the role that each component fulfils Assessment of which requirements have not been implemented, and the selection of requirements that should be implemented by D4.2 (this is recorded in D4.2 under prototype sub-section). Development and documentation of components that implement the selected requirements, including specification and documentation of the relationships between components and between these components and the other components of the architecture Adaptation of Use Cases from D4.1, where necessary incorporating additional/new use cases and scenarios (particularly where these relate to privacy, trust and identity management aspects) Creation of the Deployment View from the D4.1 description of community topologies Linking of requirements to components, noting that components often fulfil multiple roles and that mappings can become complex to describe. Similarly, linking components with PICOS features and PICOS principles.
and D5. 2.2 The dissemination level of this deliverable is public (PU) i.e. once approved by the European Commission (EC), it will be freely available for download through the DREAMS project website (xxxx://xxx.xxxxxx-xxxxxxx.xx).
and D5. 5) Presented the EFD project and gave them the promotional material (bookmarks, leaflets and stickers) to the “Italia Autentica” consortium. These manufacturers expressed their interest in becoming data providers of Europeana supplying the portal with images of their historical archives. The companies are very glad to cooperate with the Italian Ministry of Cultural Heritage and a European project. PS: (See D2.6) secured new content providers through their outreach and engagement event: Culture Foundation of the Piraeus Bank Official organisation of traditional products in Greece Public company of the municipality of the Cyclades (commercial organisation) National Historical Museum Enterprise Greece (commercial organisation) National Wine Association These new partnerships will extend beyond the lifetime and scope of the project. Additional RPAs
