Document Overview Sample Clauses

Document Overview. Transition consists of those standard activities necessary for the Service Provider to assume service delivery responsibility from the State beginning on Commencement Date. These activities include the transfer of staff, establishment of the IT environment, setup of the program management system, implementing workplace logistics, and deploying any necessary interim processes and tools.

Document Overview. This document specifies functional, performance and interface requirements for the integrated Satellite and the Spacecraft Bus, including external Satellite interfaces, Instrument-Bus interfaces and Instrument integration, Bus and Satellite test, launch, and operational requirements. Separate Interface Control Documents (ICDs) detail the specifics of the Instrument-Bus interfaces and Integration and Test processes. Satisfaction of the Satellite-level requirements contained in this specification assume the Instrument provided as CFE meets its requirements, which are documented separately. As the SSI, BATC will refer to the separate Instrument Specifications as necessary to maintain the Spacecraft Bus to Instrument ICDs and develop an integration and test plan sufficient to ensure the integrated Satellite meets its system-level functional and performance requirements.

Document Overview. This document specifies functional, performance and interface requirements for the integrated Satellite and the Spacecraft Bus, including external Satellite interfaces, Instrument-Bus interfaces and Instrument integration, Bus and Satellite test, launch, and operational requirements. Separate Interface Control Documents (ICDs) detail the specifics of the Instrument-Bus interfaces and Integration and Test processes. Satisfaction of the Satellite-level requirements contained in this specification assume the Instrument provided as CFE meets its requirements, which are documented separately. As the SSI, BATC will refer to the separate Instrument Specifications as necessary to maintain the Spacecraft Bus to Instrument ICDs and develop an integration and test plan sufficient to ensure the integrated Satellite meets its system-level functional and performance requirements. This specification may contain requirements that have not been fully defined. These open requirements are indicated by a TBR, and/or TBD: TBR – To Be Resolved: Indicates parameters that exist, but may change after discussions with Contractor and others (e.g.: DigitalGlobe).

Document Overview. Transformation consists of activities necessary to evolve from the existing environment (via changes to the infrastructure, processes, tools, etc.) to meet the requirements of the Services. Transformation projects fall into three groupings – Stabilization, Optimization, and Consolidation. Transformation projects fall under the oversight and management of the Service Provider’s Program Management Office (PMO). This document will begin with an overall look at Transformation followed by information on specific projects within the Stabilization, Optimization and Consolidation groupings. The later portions of the document provide information about the PMO, Governance, Quality and Risk which apply to all projects. The purpose of the document is to present a high level view how projects come together and to generally describe the main SCP and incumbent interactions. Additional details are located in the Transformation Microsoft Project Plan and Attachment 20-A.

Document Overview. Transformation consists of activities necessary to evolve from DIR’s existing environment (via changes to the infrastructure, processes, tools, etc.) to meet the objectives of the State. Transformation consists of stabilization, optimization, and consolidation.

Document Overview. The document shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

Document Overview. ‌ The three case studies have been modelled using the methods and tools developed in the Maenad project. The Maenad development framework heavily relies on East-ADL modelling language, a domain specific language for the design of automotive electronic architecture that has been settled and enriched in various phases within different European research projects. In the context of the Maenad project, the original languages, design methodology and related tools for the development and evaluation of complex automotive architectures further grow to support and capture specifics aspect related to the design of Electric vehicles, while evolving to maintain compatibility with existing commercial tools and design standard. With this background, the structure of the document reflects and embraces the approach that the modelling languages provide to organize and represent the engineering information related to a particular system Models are organized in different levels of abstraction, each of which provide a particular view of the entire vehicle embedded system. At the Vehicle Level, through the Vehicle Features Model, the EE architecture of the vehicle is described in terms of “features” that characterize the vehicle. Features describe the intended functional and non-functional characteristic of the vehicle without giving detail on how they are implemented. The Vehicle Feature Model provide also a mechanism to capture and describe the different “variant“ of a vehicle, supporting the definition of rules for the inclusion of the features on the final product. The Analysis Level support the design of the EE architecture in term of functions that concur on the realization of the different features captured at the Vehicle Level In the Design Level, the functional architecture of the vehicle is addressed in detail. This layer of design concern with the Hardware architecture of the vehicle embedded systems, the mapping of functionalities on electronic devices, the definition of constraints related to sensor and actuators, definition of signal data types exchanged between functionalities and time properties. At the implementation level, the different macro functionalities that concur to the realization of the vehicle features are detailed and mapped to the “Autosar” software components. 2 Case studies modelling‌ 2.1 EV Demo

Document Overview. The structure of this deliverable follows a similar structure found in the first deliverable (and refers to it in many places), while also providing an update. Section 1 Introduction and motivations’ provides the document overview. • Section 2 ‘Towards architectural paradigms on virtual infrastructures’ summarises the FEDERICA architectural principles focusing on the JRA2 related issues, namely the IaaS framework, the interoperability prototype, and the business processes covered by IPsphere. The validation of the applied design principles are done by studying novel architectural concepts (such as multi-stage software routers and OpenFlow, which may lead to paradigm shifts in the future) on top of the FEDERICA virtualised infrastructure. • Section 3 ‘Authentication and Authorization Infrastructure for ▇▇▇▇▇▇▇▇’ includes all the security aspects related to internal risks and external threats. It gives details of the AAI infrastructure proposed for FEDERICA and the practical usage of the federated SSH access to FEDERICA resources.

Document Overview. This document is the first deliverable for SA2.4 task summarizing the work done until month 15. The objective of SA2.4 task is to provide a User Controlled IP Slice Service. This document gives an overview of the state of every subtask that needs to be accomplished to achieve this service. The different subtasks that need to be done are: study and selection of the computer virtualization platform and the software routing tool, development of the software that will create and manage logical routers and prototyping of the software that will create and manage virtual machines and software routers. This document is structured as follows: Chapter 1, entitled ‘Introduction’, is a short introduction describing the aims and the scope of this deliverable. In chapter 2, entitled ‘FEDERICA and MANTICORE’, the different technologies that are used in the MANTICORE development are explained. Also the architecture used in the development is specified. Chapter 3, entitled ‘Logical routing capabilities’, describes the current capabilities that MANTICORE has to create and manage logical routers based on the Juniper platform. In chapter 4, entitled ‘Computer virtualization capabilities’, the study done in order to choose a computer virtualization tool is presented. On the other hand, the different scenarios and use cases that have been prototyped are described. Finally, the actual status of the prototype is specified. Chapter 5, entitled ‘Software router capabilities’, it is fully described the study and selection of the software routing tool. Also it is described the status of the prototype that will manage software routers. In chapter 6, entitled ‘FEDERICA IP services’, the scenarios and use cases that have been developed in order to manage IP configurations of logical routers are specified, and the new protocols that will be included in the MANTICORE enhancement are also defined.