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. The Framework Agreement consists of the following documents: • Form 5101 (front page of the contract with signatures) • General Contract Provisions (this document) • Annexes specified in clause Xxxx! Xxxx ikke referansekilden.
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 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. 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. 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 provides 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 provides 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. Figure 1-1: EAST-ADL Abstraction levels 2 Case studies modelling
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. This document contains Service Management categories of responsibilities that apply to the delivery of Services. These categories are considered “cross-functional” in that they are functions which cross all SCPs.
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.
