GOSSRA Architecture For Standardisation - Vol. 2
C ollaborative P rojectP AD R F P S S A 2017 800783GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)This project has received funding from the European Union's Preparatory Action on Defence Research under grantagreement No 800783 GOSSRA. This document reflects the view of the author(s) and the GOSSRA Consortium,EDA and the Commission are not responsible for any use that may be made of the information it contains.This document is disclosed outside the GOSSRA Consortium and specifically targeted to the dismounted soldiersystem community. It shall not be used – in whole or in part – for any purpose other than for architectural work (e.g.reference architecture standardisation, derivation of target architectures, or extracting recommendation for soldiersystem definition, specification, design, and development), unless otherwise expressly authorised by the GOSS RAConsortium.This project as well as any other results and rights obtained in performing the GOSSRA Grant Agreement,including copyright and other intellectual or industrial property rights, shall be owned solely by the GOSSRAConsortium, which may use, publish, assign or transfer them as it sees fit, without geographical or other limitation,except where industrial or intellectual property rights exist prior to the contract being entered into.Identification: BL8464A037 REPDocument Date: 31 July 2020Version: v1.1Status: FinalDissemination Level: PU: Public
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)MetadataWork Package WP8: Technical ValidationDeliverable Number D8.5Due Date: 30 April 2020Submission Date: 30 April 2020Lead Partner GMVAuthor(s): See Section 1.2Reviewer(s): All GOSSRA ConsortiumDelivery Type: R: ReportDissemination Level: PU: PublicVersion 2019-12-05Norbert HärleRMEInitial Release1.02020-04-30Iñigo BarredoGMVSubmitted Release1.12020-07-31Daniel RiggersRMEFinal ReleaseD: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 2 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)Table of ContentsOVERVIEW AND SUMMARY INFORMATION .51A RCHITECTURE SCOPE.7IDENTIFICATION .81.11.2CAPABILITY VIEW. 1022.12.1.12.1.22.1.32.1.4NCV-1 CAPABILITY VISION . 10Vision Statement . 10Vision Goals . 10Identifying Combat Capability Needs. 11Capability Requirement Areas and Goals. gory 1: Command, Control, Communications, Computing (C4) . 13Category 2: Intelligence, Surveillance, T arget Acquisition and Reconnaissance (IST AR) . 14Category 3: Effective Engagement. 15Category 4: Mobility . 16Category 5: Protection and Survivability . 17Category 6: Sustainability and Logistics. 18Category 7: Education and Training. 19Category 8: Multi-National Interoperability . 20NCV-2 CAPABILITY TAXONOMY . 21Capability Category 1: Command, Control, Communications, Computing (C4). 21Capability Category 2: Intelligence, Surveillance, Target Acquisition and Reconnaissance (ISTAR). 24Capability Category 3: Effective Engagement . 25Capability Category 4: Mobility . 26Capability Category 5: Protection and Survivability . 27Capability Category 6: Sustainability and Logistics . 29Capability Category 7: Education and Training . yIndividual E ducation and T raining. 31Collective T raining and Exercises . 31Capability Category 8: Multi-National Interoperability . 322.2.8.12.2.8.22.2.8.32.32.4Interoperability T erms and Definitions . 32Levels of Standardisation . 32Interoperability T axonomy. 33NCV-4 CAPABILITY DEPENDENCIES . 35NCV-6 CAPABILITIES TO OPERATIONAL A CTIVITY M APPING . 37INTEGRATED DICTIONARY . 5033.13.2A BBREVIATIONS AND A CRONYMS . 50REFERENCED DOCUMENTS . 52D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 3 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)Table of FiguresFigure 1-1 – GOSSRA Document Structure. 5Figure 2-1 – Identifying Combat Capability Requirements . 12Figure 2-2 – Capability Categories . 13Figure 2-3 – NATO-ACT Conceptual C2 Framework . 22Figure 2-4 – Taxonomy of Command, Control, Communications and Computing Capability Category. 23Figure 2-5 – Taxonomy of the ISTAR capability category . 24Figure 2-6 – Taxonomy of Effective Engagement Capability. 25Figure 2-7 – Taxonomy of Mobility Capability Category. 26Figure 2-8 – Taxonomy of Protection and Survivability Capability Category . 28Figure 2-9 – Taxonomy of Sustainability and Logistics Capability Category . 29Figure 2-10 – Categorisation of Education and Training (Bi-SC 75-2/75-3). 30Figure 2-11 – Taxonomy of Training Capability . 31Figure 2-12 – Taxonomy of Interoperability . 33Figure 2-13 – Capability Taxonomy Dependencies Relationship. 35Table of TablesTable 2-1 – Capability to Operational Activity Mapping (Capability Category 1: C4) . 38Table 2-2 – Capability to Operational Activity Mapping (Capability Category 2: ISTAR) . 39Table 2-3 – Capability to Operational Activity Mapping (Capability Category 3: Effective Engagement). 41Table 2-4 – Capability to Operational Activity Mapping (Capability Category 4: Mobility). 42Table 2-5 – Capability to Operational Activity Mapping (Capability Category 5: Protection andSurvivability) . 44Table 2-6 – Capability to Operational Activity Mapping (Capability Category 6: Sustainability &Logistics). 46Table 2-7 – Capability to Operational Activity Mapping (Capability Category 7: Education & Training). 48Table 2-8 – Capability to Operational Activity Mapping (Capability Category 8: Multi-NationalInteroperability). 49D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 4 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)1 Overview and Summary InformationThe Generic Open Soldier System Reference Architecture (GOSSRA) is described in this set ofdocuments and represents the proposal of the GOSSRA Consortium for subsequentstandardisation.The standardisation itself lies outside the scope of this project. However, the consortium plans topropose the architecture to the “C4I and System Architecture” Working Group of the NATO “LandCapability Group Dismounted Soldier System” (LCG DSS) which has been following the workthrough GOSSRA Presentations and discussions during the course of the project.The architecture consists of a set of documents with seven volumes /1/, /2/, /3/, /4/, /5/, /6/, and /7/which contain the different architectural views according to the NATO Archit ecture Frameworkv3.1, with the addition of a Security View (see Figure 1-1). It is accompanied by a formalarchitecture represented by a set of computer files, compiled by using the SparxSystemsEnterprise Architect (version 13) /8/.Figure 1-1 – GOSSRA Document StructureD: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 5 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)This for Soldier Systems was developed based on following assumptions: This is a reference architecture . It consists of common best practices and does notdepict any one nation’s solution. When nations define, specify or develo p their specificdismounted soldier system, they may elect to use this architecture as a reference. As a reference architecture, it is not intended to dictate acquisition or procurementdecisions. Rather, it is meant to be used as a template for developing solutions. Nations are responsible for using this reference to create target architectures(solutions) depicting their implementation including specific equipment for specificroles. The reference architecture standardizes specific aspects where innovatio n isexpected to be slow, but leave options open where innovation is fast andcompetition is desired. Nations are also responsible for using this reference when creating system-ofsystem architectures that include soldier systems. This architecture models a squad as well as a single soldier. We recognize soldiersdo not operate on their own, are networked, and share equipment (especially vehicleplatforms). A squad also consists of soldiers performing different roles, e.g. ascommander, machine gunner, sniper, scout, medic, or other mission specific role andthus, needing different equipment. This architecture focuses on the electrical and electronic equipment a soldier wears,carries, and consumes as well as on software and data communication. This architecture embraces concepts of interoperability, interchangeability, andcommonality. This reference architecture does not strictly and blindly comply with the process andviews in the NATO Architectural Framework but rather takes the underlying conceptsand uses them to efficiently develop views which are thought to be useful for thepurpose and the community.D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 6 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)1.1 Architecture ScopeThe purpose of the Generic Open Soldier System Reference Architecture (GOSSRA) is to serve asa common reference architecture on EU-/NATO-Level for deriving a Target Architecture at countrylevel.This Reference Architecture comprehensively focuses on: softwareelectronicsvoice and data communicationsensorseffectorshuman interface devicesC4IThis Reference Architecture for Soldier Systems is ready for standardization to become openlyavailable and not implying any protected intellectual property. T he architecture, to be appliedduring at least the next 10 years, shall consider trends and potentials with respect to capabilities,operations and technologies.The architecture represents “best practice”, “future trends and developments” and suggestsstandard interfaces. It shall be used as a reference to derive the “Target Architecture” which is thearchitecture for a specific Soldier System to be procured.By referring to this reference architecture, the “Target Architecture” then: is easier to develop,includes all major aspects, anduses specific common standards enabling interoperability.D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 7 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)1.2 IdentificationThis set of documents represent the “GOSSRA Architecture for Standardisation” which is thedeliverable D8.5 of the GOSSRA project.The architecture had been developed between the 6th May 2019 and the 30st April 2020 by theGOSSRA Consortium. Led by Rheinmetall Electronics GmbH (Germany), GOSSRA’s consortiumencompasses 9 participants from 7 countries: GMV (Spain), iTTi (Poland), Tekever -ASDS(Portugal), Larimart (Italy), Leonardo (Italy), SAAB (Sweden), Indra (Spain) and TNO (theNetherlands) and received an EU grant of roughly 1.5 million over 23 months (1st July 2018 to30st April 2020).The companies include major European Soldier System companies which developed and alreadydelivered Soldier Systems in large numbers. Further, participants are smaller companies whichprovided subsystems or components and contributed their specific and valuable expertise to theproject. Finally, a research institute provided knowledge about newest developments andtechnologies.Following are the GOSSRA project team members: Rheinmetall Electronics GmbH (DEU, prime contractor)o Dr. Norbert Härle (Contract Manager)o Erik Wimmer (Deputy Contract Manager)o Daniel Riggers (Technical Coordinator)o Dr. Deepak Das (Technical Expert)GMV Aerospace and Defence (ESP)o Jose Luis Delgado (Project Manager and Technical Expert)o Ricardo Sáenz Amandi (Technical Expert)o Vicente Javier de Ayala Parets (Technical Expert)o Iñigo Barredo (Technical Expert)o Gustavo Alberto García García (Technical Expert)ITTI Sp. z o.o. (POL),o Piotr Gmitrowicz (Project Manager and Technical Expert)o Łukasz Szklarski (Technical Expert)o Patryk Maik (Technical Expert)o Mateusz Oles (Technical Expert)Tekever ASDS Lda. (PRT),o António Monteiro (Project Manager)o Duarte Belo (Technical Expert)o Aleksandra Nadziejko (Technical Expert)o Filipe Rodrigues (former Project Manager & Technical Expert)o André Oliveira (former Project Manager & Technical Expert)Larimart SpA (ITA),o Marco Stella (Technical Expert),o Fabrizio Parmeggiani (Project Manager and Technical Expert)o Luigi Esposito (Technical Expert)Leonardo SpA (ITA)o Francesco Fedi, LDO (Principal Editor)o Rosa Ana Lopez Mazuelas (Technical Expert)o Fabio Casalino (Technical Expert)o Francesco Cazzato (Project Manager)o Antonio DiRocco (Technical Expert)o Mazzulli Vanessa (Technical Expert)o Zamburru Lorenzo (Technical Expert)D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 8 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV) SAAB AB (SWE)o Dennies Olesen (Technicas l Expert)o Pär-Åke Anderkrans (Project Manager and Technical Expert)Indra (ESP)o Pablo Martínez Mena (Project Manager)o Ángel Pérez Martín-Nieto (Technical Expert)TNO (NLD)o Marcel van der Lee (Technical Expert)o Angela Kwaijtaal (Project Manager)o RonaldRonald in ’t Velt (Technical Expert)o Eelco Cramer (Technical Expert)Additional to the consortium, the GOSSRA project established a Stake Holder Advisory Board withrepresentatives from following European Governments: NLDo Luc de Beer (Mindef, DMO, DP&V, Ressort Projecten, Soldier SystemProcurement)o Major Koen van Veen (Defence Centre of Expertise for Soldier and Equipment)o Jasper Groenewegen (DNV GL) DEUo Dr. Karl-Heinz Rippert (Federal Office of Bundeswehr Equipment, InformationTechnology and In-Service Support, Soldier System Procurement) ITAo Magg. Ing. Mattia Bevilacqua (Ministero della Difesa, IV Reparto “Coordinamentodei programmi di armamento”, Direzione di Programma “Forza NEC”)o Ten. Col. Vincenzo Bello (Ministero della Difesa, IV Reparto “Coordinamento deiprogrammi di armamento”, Direzione di Programma “Forza NEC”)o Col. Mauro Fanzani (Ministero della Difesa, IV Reparto “Coordinamento deiprogrammi di armamento”, Direzione di Programma “Forza NEC”) ESPo Col. Antonio Varo Gutiérrez (ET MDE)o Col. (ET) Moisés Serrano Martínez (ET MDE) PRTo Lt. Col. Luís Paz Lopes (Portugese Army)o LTCol Simão Sousa (Portugese Army)Special thanks for their feedback and contributions.D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 9 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)2 Capability View2.1 NCV-1 Capability VisionThe NATO Capability View (NCV) provides a strategic context for the capabilities described in thearchitecture. It also provides a high-level scope for the architecture which is more general than thescenario-based scope defined in NOV-1. Capability in the context of a Multi-National Force orNational Force would entail having the ability to meet most, if not all, of the envisaged operationalscenarios and challenges optimally. This would imply that the Dismounted Soldier System (DSS)envisaged through this reference architecture should provide a competitive edge over itsadversaries in terms of every desired combat and combat support capability to the soldier.Capability development of a force is a complex activity and the DSS, therefore, needs to look at allaspects of combat capability from observation, detection, target acquisition, target dissemination,decision support, effective engagement, reporting mission status, logistics and preparation forensuing battle space contingencies to training and interoperability.Envisioning such a capability spectrum would require a peep into the future threats to thedismounted soldier, as well as a constant check of the capability acquired by our adversaries aswell as technology trends to keep the soldier system state of the art.It is therefore important to spell out what such a vision encapsulates in terms of a vision statementand the vision goals which will help realise such a capability vision.2.1.1 Vision StatementThe Capability Vision for a state-of-the-art soldier system is to enhance multinational soldiers’fighting capabilities by empowering them with information superiority, enhanced mobility, effectiveengagement, interoperability, resilience and agility to operate in diverse, complex and contestedcurrent and future environments.2.1.2 Vision GoalsIn order to be able to envision all the capability needs in the correct perspective, it is important toidentify the vision goals encapsulated within the capability vision. These vision goals are as under: Information Superiority through efficient and robust information sharing both amongnational land forces and with joint multinational forces and other actors (like media, NGOs,other humanitarian agencies, etc.);Effective and rapid decision making at all levels, supported by enhanced situationalawareness in complex, congested battlefields;Enhanced mobility to allow forces to engage in joint manoeuvre, more flexible, agiledeployments and operations in complex, contested and hazardous environments;Effective engagement to include countering remotely piloted and autonomous unmannedaerial systems including UAV swarms and a flexible range of non -lethal and non-kineticeffects, such as microwave and sonic-based weapons, to allow forces to minimise collateraldamage while disrupting the adversary’s capabilities.More independent and self-sustainable deployments through the provision of integralelectronic manned / unmanned surveillance and reconnaissance means at the SmallTactical Unit (STU) level.D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 10 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV) Enhanced CIMIC (Civil Military Cooperation) to ensure the fulfilment of mission mandatesand leverage deeper and common understanding between the armed forces and civilianactors;Enable integrated and reduced logistics through lightweight modular and easilytransportable materials and equipment;Conduct defensive and offensive cyber operations at the strategic, operational and tacticallevel, including the ability to disrupt and take control of the adversary’s manned andunmanned systems;Interoperability between EU/NATO Forces and their allies.However, in order to be able to look at all the capability needs from the basic, through the currentand to the future, it is important to envision the complete spectrum of soldier needs in a holisticmanner. This entails examining capability from the different view-points of operations, services,technical, training, maintenance and logistics, business and sustainability.The ensuing paragraphs explain the methodology of evolving this holistic capability vision for asoldier system.2.1.3 Identifying Combat Capability NeedsThe DSS supports soldiers in a mission with respect to the core questions to which a soldier seeksanswers to during any operation: “What is my environment?”“Where am I?”“Where is the enemy?”“Where are my comrades?”“What is my task?”“What is the best way to engage/neutralise the enemy?”“What are my communicating and reporting instructions?”“What is my next likely task?” (In keeping with the Commander’s Intent).Figure 2-1 below, depicts the manner in which a soldier’s basic capability needs should beinterpreted to identify capability requirements for a soldier system.In the first column, a soldier’s or small tactical unit’s basic combat questions are listed e.g. “What ismy environment like?”, “Where am I?”, “Where is the enemy?” etc. In brackets below eachquestion is the scope of the question e.g. the question ‘What is my environment?’ encompassesthe physical environment – terrain, altitude, air, oxygen level, temperature, etc. Similarly, thequestion ‘Where am I?’ encompasses the scope of location (enemy/own), identifiable landmark,distance (from enemy/own troops / RV / Hide / Firm Base, etc.).The third column depicts how these questions should be interpreted to evolve the requirement ofcombat capabilities e.g. terrain analysis, navigation, day-night visibility, location andcommunication, operational orders, target designation, effective engagement, co mmunication,reporting instructions, situational and future task awareness, etc.The second column depicts, how these capabilities apply commonly or differently to the threecategories of Basic Soldier,Specialist Soldier (Gunner/Grenadier/ Bombardier) orSTU Leader.D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 11 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)BASICSOLDIERCOMBATANT’S QUESTIONSGUNNER /GRENADIERSQUADLEADERCAPABILITYINTERPRETATIONWHAT IS MY ENVIRONMENT? (Physical:Terrain, Altitude, Air, Temp., etc.)Terrain Analysis, Going/AscentRate, O2 Level, Toxicity of Air,Temperature, etcWHERE AM I?(Location, Distances, Identifiable TacticalLandmarks, etc.)GNSS (GPS), GIS, Bearing andRange, Inter-visibility, etc.WHERE IS THE ENEMY?(Force Level, Bearing, Distance, WeaponRange, Visibility, etc.)Day/Night Sensors, GIS with RFOverlay, Bearing and Range,Inter-visibility, etc.WHERE ARE MY COMRADES?(Bearing, Distance, Inter-visibility, etc.)GIS with BF Tracking, RadioCommunication. etc.WHAT IS MY TASK?(Op. Plan, Cdr’s Intent, Timelines, etc.)Orders, Operational CodeWords, C4I, etcWHAT IS THE BEST WAY TO ENGAGETHE ENEMY?(Direct/Indirect Fire, Area Weapons, Inf.Mortar/ Artillery/ Naval Guns, Air, etc.)Target Profile, JointCommunications, TargetDesignation, TargetIllumination, EffectiveEngagement, etc.WHAT IS MY COMMUNICATING /REPORTING INSTRUCTION?(When, To Whom, How to Report?)Frequency, Codes, Keys, PowerRestrictions & Requirements,Bounds, etc.Intelligence Update,Communications, SituationalAwareness, Decision Support,Replenishments, etc.WHAT IS MY NEXT LIKELY TASK /CDR’SINTENT?(Timings, Distances, Nature of Task, Op.Plan, Logistics, etc.)Figure 2-1 – Identifying Combat Capability RequirementsThere would of course be a number of related questions that a soldier would need answers to,depending upon the combat situation or nature of mission. These would lead to the interpretationof further capability needs.Analysis of the capability interpretation column specifically for different combatant categories of theindividual soldier, gunner/bomber/grenadier or the STU leader would also help in arriving at thebasic and add-on capability configuration of the DSS.D: BL8464A037 REPRevision: v1.1RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAABUse or disclosure of data contained on this sheet is subjectto restriction on the title page of this documentDate: 31 July 2020Page 12 of 52
GOSSRA Architecture for Standardisation - Vol. 2Capability (View NCV)2.1.4 Capability Requirement Areas and GoalsIn order to design a holistic soldier system, it is important to be able to classify the capabilityrequirements in broad categories, which would encompass most operational needs. The CapabilityVision Goals defined in section 2.1.2 above, can be achieved through the synergistic developmentof a number of capability requirements. Figure 2-2 depicts the broad capability requirement areasand the ensuing paragraphs describe the trends and goals to be achieved within each in detail.Capability Categories Command, Control, Communication, Computing (C4)Intelligence, Surveillance, Target Acquisition, Reconnaissance
GOSSRA Architecture for Standardisation - Vol. 2 Capability (View NCV) D: BL8464A037 REP RME, IND, GMV, LDO, LRT, iTTi, TNO, TEK, SAAB Date: 31 July 2020 Revision: v1.1 Use or disclosure of data contained on this sheet is
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
Menschen Pagina 20 Schritte international Neu Pagina 22 Motive Pagina 24 Akademie Deutsch Pagina 25 Starten wir! Pagina 26 Themen aktuell Pagina 28 em neu Pagina 29 Sicher! Pagina 30 Vol A1 1 Vol A1 Vol 1 Vol 1 2 Vol unico Vol 1 Volume 1 Volume 1 Vol 1 Vol 1 1 Vol A1 2 Vol 2 Vol 1 2 Vol A2 1 Vol A2 Vol 3 Vol
Akenson, Donald Harman Vol 8: 10 Alan, Radous, at Agincourt Vol 12: 1 Albert, King Vol 7: 45, 47 Albert, Prince Vol 12: 17; Vol 14: 1 Alden, John Vol 5: 34; Vol 9: 18 Alexander III Vol 13: 24 Aleyn, John, at Agincourt Vol 12: 1 Allen, Pat Vol 10: 44 Alling Vol 4: 26 Amore, Shirley Vol 12: 3 Anderson, Robert Vol 10: 46 Anderson, Virginia DeJohn .
International Dysphagia Diet Standardisation Initiative (IDDSI) 6 Ramverk för implementering av IDDSI 7 Implementeringsforskning 8 Consolidated Framework for Implementation Research (CFIR) 9 Metod 10 Studiedesign 10 Litteratursökning 12 Rekrytering och urval 12 Transkribering och analys 13 Etiska överväganden 14 Resultat 14
10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan
service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största
Hotell För hotell anges de tre klasserna A/B, C och D. Det betyder att den "normala" standarden C är acceptabel men att motiven för en högre standard är starka. Ljudklass C motsvarar de tidigare normkraven för hotell, ljudklass A/B motsvarar kraven för moderna hotell med hög standard och ljudklass D kan användas vid
Fedrico Chesani Introduction to Description Logic(s) Some considerations A Description Language DL Extending DL Description Logics Description Logics and SW A simple logic: DL Concept-forming operators Sentences Semantics Entailment Sentences d 1: d 2 Concept d 1 is equivalent to concept d 2, i.e. the individuals that satisfy d 1 are precisely those that satisfy d 2 Example: PhDStudent .
