DOCSLIB.ORG

Embedded Systems - ECE)​​ I -M.TECH I -Semester (AUTONOMOUS-R18

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Embedded Systems - ECE)​​ I -M.TECH I -Semester (AUTONOMOUS-R18 Presentation on Principles of Distributed Embedded Systems (Embedded Systems - ECE)​​ I -M.TECH I -Semester (AUTONOMOUS-R18) Prepared by, Dr. S. Vinoth Associate Professor UNIT - I REAL TIME ENVIRONMENT 2 UNIT - I REAL-TIME ENVIRONMENT .Real-time computer system requirements .classification of real time systems .simplicity, global time .internal and external clock synchronization .real time model. Real time communication .temporal relations, dependability .power and energy awareness .real time communication .event triggered .rate constrained .time triggered. 3 What is an Embedded system? 4 What is a real-time system? . A real-time system is any information processing system which has to respond to externally generated input stimuli within a finite and specified period –the correctness depends not only on the logical result but also the time it was delivered –failure to respond is as bad as the wrong response! . The computer is a component in a larger engineering system => EMBEDDED COMPUTER SYSTEM 99% of all processors are for the embedded systems market 5 Terminology • Hard real-time — systems where it is absolutely imperative that responses occur within the required deadline. E.g. Flight control systems. • Soft real-time — systems where deadlines are important but which will still function correctly if deadlines are occasionally missed. E.g. Data acquisition system. • Real real-time — systems which are hard real-time and which the response times are very short. E.g. Missile guidance system. • Firm real-time — systems which are soft real-time but in which there is no benefit from late delivery of service. A single system may have all hard, soft and real real-time subsystems In reality many systems will have a cost function associated with missing each deadline. 6 Characteristics of a RTS • Large and complex — vary from a few hundred lines of assembler or C to 20 million lines of Ada estimated for the Space Station Freedom • Concurrent control of separate system components — devices operate in parallel in the real-world; better to model this parallelism by concurrent entities in the program • Facilities to interact with special purpose hardware — need to be able to program devices in a reliable and abstract way 7 Characteristics of a RTS cont…… . Extreme reliability and safe — embedded systems typically control the environment in which they operate; failure to control can result in loss of life, damage to environment or economic loss . Guaranteed response times — we need to be able to predict with confidence the worst case response times for systems; efficiency is important but predictability is essential 8 Embedded computing systems are becoming pervasive in our society (more than 109 units/year): . Robotics . Flight control systems . Plant control . Automotive . Consumer electronics . Multimedia systems . Sensor/Actor 9 Criticality QoS management High performance Safety critical firm hard Timing contraints 10 Common features .In these diversified domains some shared features can be identified: .Dedicated function (vs general-purpose computers) .Reactive / Interactive .Real-time .Constraints on several metrics: cost, power, performance, noise, weight, size, flexibility, maintainabilit y, correctness, safety, time-to-market 11 Embedded systems overview .Embedded computing systems .Computing systems embedded within Computers are in here... electronic devices and here... .Hard to define. Nearly any computing system and even here... other than a desktop computer .Billions of units produced yearly, versus millions of desktop units Lots more of .Perhaps 50 per household and per these, though they automobile cost a lot less each. 12 A “short list” of embedded systems Anti-lock brakes Modems Auto-focus cameras MPEG decoders Automatic teller Network cards machines Network Automatic toll systems switches/routers Automatic transmission On-board navigation Avionic systems Pagers Battery chargers Photocopiers Camcorders Point-of-sale systems Cell phones Portable video games Cell-phone base Printers stations Satellite phones Cordless phones Scanners Cruise control Smart Curbside check-in ovens/dishwashers systems Speech recognizers Digital cameras Stereo systems Disk drives Teleconferencing Electronic card readers systems Electronic instruments Televisions Electronic toys/games Temperature Factory control controllers Fax machines Theft tracking systems Fingerprint identifiers TV set-top boxes And the list Home security systems VCR’s, DVD players Life-support systems Video game consoles goes on and on 13 Common characteristics of Embedded systems Some common characteristics of embedded systems .Single-functioned –Executes a single program, repeatedly .Tightly-constrained –Low cost, low power, small, fast, etc. .Reactive and real-time –Continually reacts to changes in the system’s environment –Must compute certain results in real-time without delay 14 An embedded system example – Digital camera .Single-functioned -- always a digital camera .Tightly-constrained -- Low cost, low power, small, fast .Reactive and real-time -- only to a small extent 15 What is real-time? What is real-time? Is there any other kind? .A real-time computer system is a computer system where the correctness of the system behavior depends not only on the logical results of the computations, but also on the physical time when these results are produced. .By system behavior we mean the sequence of outputs in time of a system. 16 Real-time means reactive .A real-time computer system must react to stimuli from its environment .The instant when a result must be produced is called a deadline. .If a result has utility even after the deadline has passed, the deadline is classified as soft, otherwise it is firm. .If severe consequences could result if a firm deadline is missed, the deadline is called hard. Example: Consider a traffic signal at a road before a railway crossing. If the traffic signal does not change to red before the train arrives, an accident could result. 17 Reliability • The Reliability R(t) of a system is the probability that a system will provide the specified service until time t, given that the system was operational at the beginning (t-t0). • The probability that a system will fail in a given interval of time is expressed by the failure rate, measured in FITs (Failure In Time). • A failure rate of 1 FIT means that the mean time to a failure (MTTF) of a device is 10^9 h, i.e., one failure occurs in about 115,000 years. • If a system has a constant failure rate of λ failures/h, then the reliability at time t is given by, R(t)= exp(-λ(t-to)) MTTF = 1/λ 18 Computer System Organization Computer-system operation • One or more CPUs, device controllers connect through common bus providing access to shared memory • Concurrent execution of CPUs and devices competing for memory cycles 19 Distributed Systems • Computation is distributed among several processors. In contrast to tightly-coupled systems, the processors do not share a clock or memory. Each has its own local memory. • Communication is via a network. These systems are termed loosely- coupled or distributed systems. The processors vary in size and function and are called nodes. Advantages of distributed systems: • Reliability: If one node fails, the remaining nodes can continue operating. So by building enough redundancy, the system will not fail if one or more nodes fail (e.g. redundant web servers). • Computation speedup: Computation can be distributed among various nodes to run concurrently (e.g. load balanced web servers). 20 Distributed Systems (contd.) • Resource Sharing: Software, data, and hardware resources can be shared. E.g. data files in node A can be accessed by a user at node B. Files can be printed at a shared laser printer. • Communication: Processes at various nodes can exchange information. 21 Special Purpose Systems 22 WHEN IS A COMPUTER SYSTEM REAL-TIME? • A real-time computer system is a computer system in which the correctness of the system behavior depends not only on the logical results of the computations, but also on the physical instant at which these results are produced. • A real-time computer system is always part of a larger system–this larger system is called a real-time system. • A real-time system changes its state as a function of physical time, e.g., a chemical reaction continues to change its state even after its controlling computer system has stopped. • It is reasonable to decompose a real-time system into a set of sub- systems called clusters. 23 Real- Time system cont….. • We refer to the controlled object and the operator collectively as the environment of the real-time computer system. • If the real-time computer system is distributed, it consists of a set of computer) nodes interconnected by a real-time communication network 24 Real- Time system cont….. • The interface between the human operator and the real-time computer system is called the man-machine interface, and the interface between the controlled object and the real-time computer system is called the instrumentation interface. • The man-machine interface consists of input devices (e.g., keyboard) and output devices (e.g., display) that interface to the human operator. • The instrumentation interface consists of the sensors and actuators that transform the physical signals (e.g., voltages, currents) in the controlled object into a digital form and vice versa. • A node with an instrumentation interface is called an interface node. 25 Real- Time system cont….. • A real-time computer system must react to stimuli from the controlled object (or the operator) within time intervals dictated by its environment. • The instant at which a result must be produced is called a deadline. If a result has utility even after the deadline has passed, the deadline is classified as soft, otherwise it is firm. If a catastrophe could result if a firm deadline is missed, the deadline is called hard. 26 Real- Time system cont….. Consider a railway crossing a road with a traffic signal. • If the traffic signal does not change to "red" before the train arrives, a catastrophe could result.
Load more

Recommended publications
  • Validated Products List, 1995 No. 3: Programming Languages, Database
    NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 QC 100 NIST .056 NO. 5693 1995 NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 (Supersedes April 1995 issue) U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director FOREWORD The Validated Products List (VPL) identifies information technology products that have been tested for conformance to Federal Information Processing Standards (FIPS) in accordance with Computer Systems Laboratory (CSL) conformance testing procedures, and have a current validation certificate or registered test report. The VPL also contains information about the organizations, test methods and procedures that support the validation programs for the FIPS identified in this document. The VPL includes computer language processors for programming languages COBOL, Fortran, Ada, Pascal, C, M[UMPS], and database language SQL; computer graphic implementations for GKS, COM, PHIGS, and Raster Graphics; operating system implementations for POSIX; Open Systems Interconnection implementations; and computer security implementations for DES, MAC and Key Management.
    [Show full text]
  • Polycom Realpresence Collaboration Server (RMX) Deployment Guide for Maximum Security Environments
    [Type the document title] Military Unique Deployment Guide Version 8.3.0.J May 2014 | DOC2714B Polycom® RealPresence® Collaboration Server (RMX) 1500/2000/4000 Deployment Guide for Maximum Security Environments Polycom Document Title 1 Trademark Information POLYCOM® and the names and marks associated with Polycom's products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product may be protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. This software has achieved UC APL certification. This document provides the latest information for security-conscious users running Version 8.3.0.J software. The information in this document is not intended to imply that DoD or DISA certifies Polycom RMX systems. Support Information For support on your Polycom systems, contact Polycom Global Services at 1-888-248-4143 or go to the Polycom Support Contact page (http://support.polycom.com/PolycomService/support/us/support/ Contact_Us.html). Documentation Feedback Polycom appreciates your help as we work to improve its product documentation. Send your comment to [email protected]. © 2014 Polycom, Inc. All rights reserved. Polycom, Inc. 6001 America Center Drive San Jose CA 95002 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format.
    [Show full text]
  • Sistemi Operativi Real-Time Marco Cesati Lezione R13 Sistemi Operativi Real-Time – II Schema Della Lezione
    Sistemi operativi real-time Marco Cesati Lezione R13 Sistemi operativi real-time – II Schema della lezione Caratteristiche comuni VxWorks LynxOS Sistemi embedded e real-time QNX eCos Windows Linux come RTOS 15 gennaio 2013 Marco Cesati Dipartimento di Ingegneria Civile e Ingegneria Informatica Università degli Studi di Roma Tor Vergata SERT’13 R13.1 Sistemi operativi Di cosa parliamo in questa lezione? real-time Marco Cesati In questa lezione descriviamo brevemente alcuni dei più diffusi sistemi operativi real-time Schema della lezione Caratteristiche comuni VxWorks LynxOS 1 Caratteristiche comuni degli RTOS QNX 2 VxWorks eCos 3 LynxOS Windows Linux come RTOS 4 QNX Neutrino 5 eCos 6 Windows Embedded CE 7 Linux come RTOS SERT’13 R13.2 Sistemi operativi Caratteristiche comuni dei principali RTOS real-time Marco Cesati Corrispondenza agli standard: generalmente le API sono proprietarie, ma gli RTOS offrono anche compatibilità (compliancy) o conformità (conformancy) allo standard Real-Time POSIX Modularità e Scalabilità: il kernel ha una dimensione Schema della lezione Caratteristiche comuni (footprint) ridotta e le sue funzionalità sono configurabili VxWorks Dimensione del codice: spesso basati su microkernel LynxOS QNX Velocità e Efficienza: basso overhead per cambi di eCos contesto, latenza delle interruzioni e primitive di Windows sincronizzazione Linux come RTOS Porzioni di codice non interrompibile: generalmente molto corte e di durata predicibile Gestione delle interruzioni “separata”: interrupt handler corto e predicibile, ISR lunga
    [Show full text]
  • RTI Data Distribution Service Platform Notes
    RTI Data Distribution Service The Real-Time Publish-Subscribe Middleware Platform Notes Version 4.5c © 2004-2010 Real-Time Innovations, Inc. All rights reserved. Printed in U.S.A. First printing. June 2010. Trademarks Real-Time Innovations and RTI are registered trademarks of Real-Time Innovations, Inc. All other trademarks used in this document are the property of their respective owners. Copy and Use Restrictions No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form (including electronic, mechanical, photocopy, and facsimile) without the prior written permission of Real- Time Innovations, Inc. The software described in this document is furnished under and subject to the RTI software license agreement. The software may be used or copied only under the terms of the license agreement. Technical Support Real-Time Innovations, Inc. 385 Moffett Park Drive Sunnyvale, CA 94089 Phone: (408) 990-7444 Email: [email protected] Website: http://www.rti.com/support Contents 1 Supported Platforms.........................................................................................................................1 2 AIX Platforms.....................................................................................................................................3 2.1 Changing Thread Priority.......................................................................................................3 2.2 Multicast Support ....................................................................................................................3
    [Show full text]
  • The Norwegian State Railway System GTL (1976) Tor Olav Steine
    The Norwegian State Railway System GTL (1976) Tor Olav Steine To cite this version: Tor Olav Steine. The Norwegian State Railway System GTL (1976). 4th History of Nordic Com- puting (HiNC4), Aug 2014, Copenhagen, Denmark. pp.290-298, 10.1007/978-3-319-17145-6_30. hal-01301420 HAL Id: hal-01301420 https://hal.inria.fr/hal-01301420 Submitted on 12 Apr 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License The Norwegian State Railway System GTL (1976) Tor Olav Steine, with the help of former colleagues [email protected] Abstract. In 1976 the Norwegian State Railway System (NSB) planned a new system to keep track of all its freight cars. Among the duties were these: arranging trains at the shifting station in Alnabru outside Oslo, following (tracking) the trains as they moved along the tracks inside Norway, optimization of car maintenance and statistics. The system could save millions of Norwegian Crowns by better utilization of the car pool. It was named GTL for Gods Transport Ledelse (there is no Divine link; “Gods” simply means cargo in Norwegian).
    [Show full text]
  • Research Purpose Operating Systems – a Wide Survey
    GESJ: Computer Science and Telecommunications 2010|No.3(26) ISSN 1512-1232 RESEARCH PURPOSE OPERATING SYSTEMS – A WIDE SURVEY Pinaki Chakraborty School of Computer and Systems Sciences, Jawaharlal Nehru University, New Delhi – 110067, India. E-mail: [email protected] Abstract Operating systems constitute a class of vital software. A plethora of operating systems, of different types and developed by different manufacturers over the years, are available now. This paper concentrates on research purpose operating systems because many of them have high technological significance and they have been vividly documented in the research literature. Thirty-four academic and research purpose operating systems have been briefly reviewed in this paper. It was observed that the microkernel based architecture is being used widely to design research purpose operating systems. It was also noticed that object oriented operating systems are emerging as a promising option. Hence, the paper concludes by suggesting a study of the scope of microkernel based object oriented operating systems. Keywords: Operating system, research purpose operating system, object oriented operating system, microkernel 1. Introduction An operating system is a software that manages all the resources of a computer, both hardware and software, and provides an environment in which a user can execute programs in a convenient and efficient manner [1]. However, the principles and concepts used in the operating systems were not standardized in a day. In fact, operating systems have been evolving through the years [2]. There were no operating systems in the early computers. In those systems, every program required full hardware specification to execute correctly and perform each trivial task, and its own drivers for peripheral devices like card readers and line printers.
    [Show full text]
  • Vxworks OS Changer Gives Developers the Ability to Reuse Vxworks Applications on Diff Erent Operating Systems
    VxWorks® OS Changer Change Your OS - Keep Your Code The OS Changer family of products gives developers the freedom to switch operating systems while leveraging on their existing code and knowledge base to protect their software investment. VxWorks OS Changer gives developers the ability to reuse VxWorks applications on diff erent operating systems. VxWorks OS Changer Highlights Protect your software investment by re-using your VxWorks code Reduce time to market by migrating VxWorks code to a standard OS interface architecture Protect your knowledge-base by using familiar APIs and eliminate the learning curve on the new OS platform Eliminate dependency on a single OS vendor and switch to - An OS that meets your performance and memory footprint needs - An OS that off ers better tools, middleware/drivers and support - An OS that supports your next generation silicon Reduce ongoing development and maintenance cost - Develop target specifi c code on a host platform - Re-use one set of code across multiple host & target OS platforms - Break down VxWorks applications into manageable pieces to reduce complexity and add module protection - Use same APIs for inter-task and inter-process communications OS Changer is highly optimized for each specifi c OS platform Eclipse-based host environment is available to port VxWorks applications using OS Changer in OS PAL (refer to the OS PAL datasheet) OS Changer includes access to the BASE OS Abstractor API features to allow development of highly portable applications (refer to the OS Abstractor datasheet) Additionally, POSIX or open source Linux code can be reused on a new OS platform with POSIX OS Abstractor (refer to the POSIX OS Abstractor datasheet) VxWorks OS Changer is off ered royalty-free with source code Using VxWorks OS Changer OS Changer is designed for use as a C library.
    [Show full text]
  • Polycom RMX™ 2000/4000 Administrator's Guide
    Polycom RMX™ 2000/4000 Administrator’s Guide Version 5.0 | December 2009 | DOC2518B Trademark Information Polycom®, the Polycom “Triangles” logo, and the names and marks associated with Polycom’s products are trademarks and/or service marks of Polycom, Inc., and are registered and/or common-law marks in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. Portions, aspects and/or features of this product are protected under United States Patent Law in accordance with the claims of United States Patent No: US 6,300,973; US 6,492,216; US 6,496,216; US 6,757,005; US 6,760,750; US 7,054,620; US 7,085,243; US 7,113,200; US 7,269,252; US 7,310,320. PATENT PENDING © 2009 Polycom, Inc. All rights reserved. Polycom, Inc. 4750 Willow Road Pleasanton, CA 94588-2708 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc., retains title to and ownership of all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g., a book or sound recording).
    [Show full text]
  • Altaapi Software User's Manual
    AltaAPI™ Software User’s Manual Part Number: 14301-00000-I4 Cage Code: 4RK27 ● NAICS: 334118 Alta Data Technologies LLC 4901 Rockaway Blvd, Building A Rio Rancho, NM 87124 USA (tel) 505-994-3111 ● www.altadt.com i AltaAPI™ Software User’s Manual ● 14301-00000-I4 Alta Data Technologies LLC ● www.altadt.com CUSTOMER NOTES: Document Information: Alta Software Version: 2.6.5.0 Rev I4 Release Date: November 10, 2014 Note to the Reader and End-User: This document is provided for information only and is copyright by © Alta Data Technologies LLC. While Alta strives to provide the most accurate information, there may be errors and omissions in this document. Alta disclaims all liability in document errors and any product usage. By using an Alta product, the customer or end user agrees (1) to accept Alta’s Standard Terms and Conditions of Sale, Standard Warranty and Software License and (2) to not hold Alta Members, Employees, Contractors or Sales & Support Representatives responsible for any loss or legal liability, tangible or intangible, from any document errors or any product usage. The product described in this document is not US ITAR controlled. Use of Alta products or documentation in violation of local usage, waste discard and export control rules, or in violation of US ITAR regulations, voids product warranty and shall not be supported. This document may be distributed to support government programs and projects. Third party person, company or consultant distribution is not allowed without Alta’s written permission. AltaCore, AltaCore-1553, AltaCore-ARINC, AltaAPI, AltaAPI-LV, AltaView, AltaRTVal, ENET- 1553, ENET-A429 & ENET-1553-EBR are Trademarks of Alta Data Technologies LLC, Rio Rancho, New Mexico USA Contact: We welcome comments and suggestions.
    [Show full text]
  • Irmx Installation and Startup
    iRMX® Installation and Startup RadiSys Corporation 5445 NE Dawson Creek Drive Hillsboro, OR 97124 (503) 615-1100 FAX: (503) 615-1150 www.radisys.com 07-0683-01 December 1999 EPC, iRMX, INtime, Inside Advantage, and RadiSys are registered trademarks of RadiSys Corporation. Spirit, DAI, DAQ, ASM, Brahma, and SAIB are trademarks of RadiSys Corporation. Microsoft and MS-DOS are registered trademarks of Microsoft Corporation and Windows 95 is a trademark of Microsoft Corporation. IBM and PC/AT are registered trademarks of International Business Machines Corporation. Microsoft Windows and MS-DOS are registered trademarks of Microsoft Corporation. Intel is a registered trademark of Intel Corporation. All other trademarks, registered trademarks, service marks, and trade names are property of their respective owners. December 1999 Copyright 1999 by RadiSys Corporation All rights reserved. ii Quick Contents Section I. Choosing Your Installation Chapter 1. Introduction Section II. iRMX Installation Procedures Chapter 2. Installing on iRMX development/target systems that are PC-compatible Platforms with no DOS Chapter 3. Installing on iRMX development/target systems that are PC-compatible Platforms with DOS Chapter 4. Installing on iRMX Development/Target Systems that are Multibus II Platforms Chapter 5. Installing the iRMX III OS on Multibus I Systems Chapter 6. Installing on Windows NT systems used as iRMX development systems Section III. iRMX Getting Started Chapters Chapter 7. DOSRMX Specifics Chapter 8. iRMX for PCs Specifics Chapter 9. Getting Acquainted with the Operating System Chapter 10. Where To Go From Here Section IV. Appendices Appendix A. Installed Directories Appendix B. Limitations Appendix C. Configuration Requirements for PC Platforms Appendix D.
    [Show full text]
  • Assessment of the Technical Feasibility of ICT and Charging Solutions
    Assessment of the technical feasibility of ICT and charging solutions Deliverable No. D4.2.1 Workpackage No. WP4.2 Workpackage Title Technical feasibility of ICT and charging solutions Authors ENIDE, ICCS, CEA, CIRCE, CRF, TECNO, UNIGE, VEDE Status (Final; Draft) Final Dissemination level (Public; Public Restricted; Confidential) Project start date and duration 01 January 2014, 48 Months Revision date 2014 – 10 – 31 Submission date 2014 – 10 – 31 This project has received funding from the European Union’s Seventh Framework Programme for research, technological development and demonstration under grant agreement no 605405 Copyright FABRIC <D4.2.1> Public Contract N. 605405 TABLE OF CONTENTS EXECUTIVE SUMMARY ............................................................................................................................ 12 1. INTRODUCTION ............................................................................................................................... 17 1.1 GENERAL .................................................................................................................................... 17 1.2 CONTRIBUTION TO FABRIC OBJECTIVES ...................................................................................... 17 1.3 DELIVERABLE STRUCTURE ........................................................................................................... 17 2. METHODOLOGY .............................................................................................................................. 19 2.1 GENERAL
    [Show full text]
  • FR-1998-01-27.Pdf
    1±27±98 Tuesday Vol. 63 No. 17 January 27, 1998 Pages 3791±4150 Briefings on how to use the Federal Register For information on briefings in Washington, DC, see announcement on the inside cover of this issue. Now Available Online via GPO Access Free online access to the official editions of the Federal Register, the Code of Federal Regulations and other Federal Register publications is available on GPO Access, a service of the U.S. Government Printing Office at: http://www.access.gpo.gov/nara/index.html For additional information on GPO Access products, services and access methods, see page II or contact the GPO Access User Support Team via: ★ Phone: toll-free: 1-888-293-6498 ★ Email: [email protected] federal register 1 II Federal Register / Vol. 63, No. 17 / Tuesday, January 27, 1998 SUBSCRIPTIONS AND COPIES PUBLIC Subscriptions: Paper or fiche 202±512±1800 Assistance with public subscriptions 512±1806 General online information 202±512±1530; 1±888±293±6498 FEDERAL REGISTER Published daily, Monday through Friday, (not published on Saturdays, Sundays, or on official holidays), Single copies/back copies: by the Office of the Federal Register, National Archives and Paper or fiche 512±1800 Records Administration, Washington, DC 20408, under the Federal Assistance with public single copies 512±1803 Register Act (49 Stat. 500, as amended; 44 U.S.C. Ch. 15) and FEDERAL AGENCIES the regulations of the Administrative Committee of the Federal Subscriptions: Register (1 CFR Ch. I). Distribution is made only by the Superintendent of Documents, U.S. Government Printing Office, Paper or fiche 523±5243 Washington, DC 20402.
    [Show full text]