DOCSLIB.ORG

Ada Standardization: Status and Issues

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ada Standardization: Status and Issues Prepared for the: SIGAda Conference, 14 November 2000 AdaAda Standardization:Standardization: StatusStatus andand IssuesIssues The views and opinions James W. Moore expressed in this presentation The MITRE Corporation are those of the author and do not represent MITRE or the Department of Defense. SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 1 ScopeScope ofof PresentationPresentation ◆ Standardization ◆ Who makes standards? ◆ How are they made? ◆ Ada Standards ◆ Status ◆ Plans SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 2 WhoWho MakesMakes Standards?Standards? ◆ De jure standards are formal standards made by organizations authorized, in some way, to make them. Examples include ISO and IEEE standards. ◆ De facto standards (more properly called specifications) are those recognized by the marketplace as important. Examples include OMG CORBA, Windows API. SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 3 DevelopersDevelopers ofof InternationalInternational StandardsStandards ISO IEC ITU ... TC176 JTC1 TC56 SC65A Quality Information Technology Dependability Functional Safety ... SC7 SC22 Software & Systems Languages, OS Engineering SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 4 HowHow thethe USUS isis RepresentedRepresented inin JTC1,JTC1, SC22SC22 andand WG9WG9 JTC1 TAG: Members are US TAG domiciled Administrator JTC1 organizations A * CT22: TAG N Members are reps Administrator SC22 of WG TAGs S I WG9 TAG: Members are US TAG domiciled Administrator WG9 organizations * Caution: This is a unique arrangement. SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 5 DevelopersDevelopers ofof USUS StandardsStandards ANSI NCITS AIAA ANS ASTM EIA IEEE PMI INCOSE About 550 organizations in the U. S. make standards. About half of them are accredited by ANSI, allowing them to participate in international standardization activity. SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 6 ThreeThree WaysWays toto MakeMake aa USUS StandardStandard ◆ Accredited Standards Organization: An organization that does many things including making standards, e.g. IEEE. ◆ Accredited Standards Committee: An organization created purely for the purpose of making standards, e.g. X3. ◆ The Canvass method SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 7 WhatWhat SortSort ofof StandardStandard isis AdaAda?? ◆ Ada is an international standard, approved by JTC1: ◆ Originally in 1987 ◆ Revision in 1995 ◆ Ada is an ANSI standard, developed via the Canvass method ◆ Originally in 1983 ◆ Revision in 1995 SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 8 InternationalInternational StandardsStandards ◆ The International Organization for Standardization (ISO is not an acronym) teamed with International Electrotechnical Commission (IEC) in 1986 to set up a Joint Committee (JTC1) with the scope of Information Technology SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 9 JTC1:JTC1: MembershipMembership ◆ “National Bodies”: Each country is represented by their statutory national standards organization. (Exception: The US is represented by ANSI.) ◆ P-Members (Participating Members) each have one vote. ◆ O-Members (Observing Members) are provided with all information. SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 10 JTC1:JTC1: StructureStructure Technical Direction Subcommittees Cultural and Linguistic SC22/WG20 - Internationalization Adaptability and User SC35 - User Interfaces Interfaces SC02 - Coded Character Sets Data Capture and SC31 - Automatic Identification and Data Capture Techniques Identification Systems SC17 - Cards and Personal Identification Data Management Services SC32 - Data Management and Interchange Document Description SC34 - Document Description and Processing Languages Languages Information Interchange SC11 - Flexible Magnetic Media for Digital Data Interchange Media SC23 - Optical Disk Cartridges for Information Interchange Multimedia and SC29 - Coding of Audio, Picture, and Multimedia and Hypermedia Information Representation SC24 - Computer Graphics and Image Processing Networking and SC25 - Interconnection of Information Technology Equipment Interconnects SC06 - Telecommunications and Information Exchange between Systems Office Equipment SC28 - Office Equipment Programming Languages SC22 - Programming Languages, their Environments and Systems Software and System Interfaces Interfaces Security SC27 - IT Security Techniques Software Engineering SC07 - Software Engineering TBD SC36 - Learning Technology SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 11 SC22:SC22: ProgrammingProgramming Languages,Languages, Environments,Environments, SystemSystem SWSW InterfacesInterfaces ◆ Programming Languages ◆ Environments ◆ WG3, APL ◆ System Software Interfaces ◆ WG4, COBOL ◆ WG15, POSIX ◆ Other ◆ WG5, Fortran ◆ WG11, Binding Techniques ◆ WG9, Ada ◆ WG19, Formal Specification ◆ WG13, Modula-2 Languages ◆ WG20, Internationalization ◆ WG14, C ◆ Lingering responsibility for ◆ WG16, ISLisp Pascal, Algol, PL/I, Basic, ◆ WG17, Prolog FIMS, PCTE, CHILL, MUMPS, Extended BNF, Forth ◆ WG21, C++ SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 12 WG9:WG9: AdaAda ProgrammingProgramming LanguageLanguage ◆ Active Member Bodies: Canada, Germany, Japan, Switzerland, UK, USA ◆ Rapporteur Groups ◆ Ada: Language maintenance ◆ Annex H: High integrity systems ◆ ASIS: Library interfaces SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 13 InternationalInternational StandardsStandards andand TechnicalTechnical ReportsReports ◆ International Standard (sometimes called IS): A normative document ◆ Technical Report (often called TR): Any document that is not normative: ◆ Type 1: A document that failed to achieve consensus ◆ Type 2: A document on which work continues ◆ Type 3: Material not suitable for standardization, e.g. a reference model SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 14 HowHow areare InternationalInternational StandardsStandards Made?Made? WG SC JTC1 ISO Central Secretariat PNWI NP 3 mo 4 mo 2 mo ? CD FCD WD CDR CD FCD FDIS IS Review, Comment and Drafting Approval Publication Ballot by National Bodies SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 15 ISO/IECISO/IEC 18009:18009: AA JTC1JTC1 StandardStandard inin OneOne YearYear WG9 PNWI WG9 WD Prep Edit SC22 CD Registration SC22 CD/FCD Ballot JTC1 NP Ballot FDIS Ballot ISO Central Secretariat Edit Pub Concept JTC1 approves NP JTC1 WDWG9 approves WG9 submits FDIS FDIS approves JTC1 publishes ISO SC22 endorses NP SC22 endorses SC22 approves CDR, FCDSC22 CDR, approves uSC22 mtg uWG9 mtg 98 98 98 99 99 99 99 06 09 12 03 06 09 12 12 months - Concept to Final Text 12 months - NP approval to Publication SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 16 LanguageLanguage StandardsStandards ◆ ISO/IEC 8652:1995, IT--Programming Languages--Ada The Ada Language Reference Manual ◆ Technical Corrigendum to ISO/IEC 8652 Formal disposition of many of the “Ada Issues” ◆ ISO/IEC 18009:1999, Conformity Assessment of an Ada Language Processor The replacement for “compiler validation”. SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 17 PlansPlans forfor LanguageLanguage ◆ Technical Corrigendum 1 will be approved this year by SC22. ◆ Another CORR is planned circa 2003. ◆ Language revision will be considered circa 2005. SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 18 NumericsNumerics StandardsStandards ◆ ISO/13813:1998, IT--Programming Languages--Generic Packages of Real and Complex Type Declarations and Basic Operations for Ada (including Vector and Matrix Types) ◆ ISO/13814:1998, IT--Programming Languages--Generic Package of Complex Elementary Functions for Ada SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 19 IntegrityIntegrity StandardsStandards ◆ ISO/IEC TR 15942:2000, Guidance for the Use of Ada in High Integrity Systems ◆ Refers to 15 standards from other areas of ISO, IEC, JTC1 and other bodies, including: ◆ IEC 880, Software for computers in the safety systems of nuclear power stations ◆ IEC 61508, Functional safety: Safety-related systems ◆ ISO/IEC 15026, System and software integrity levels ◆ ISO/IEC 15408, Evaluation criteria for information technology security SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 20 ASISASIS StandardsStandards ◆ ISO/IEC TR 15291:1999, IT--Programming Languages--Ada Semantic Interface Specification (ASIS) SIGAda2000 © 2000, The MITRE Corporation. Permission is granted to reproduce without modification. James W. Moore - 21.
Load more

Recommended publications
  • Communications/Information
    Communications/Information Volume 7 — November 2008 Issue date: November 7, 2008 Info Update is published by the Canadian Standards Association (CSA) eight times a year. It contains important information about new and existing standards, e.g., recently published standards, and withdrawn standards. It also gives you highlights of other activities and services. CSA offers a free online service called Keep Me Informed that will notify registered users when each new issue of Info Update is published. To register go to http://www.csa-intl.org/onlinestore/KeepMeInformed/PleaseIdentifyYourself.asp?Language=EN. To view the complete issue of Info Update visit http://standardsactivities.csa.ca/standardsactivities/default.asp?language=en. y Completed Projects / Projets terminés New Standards — New Editions — Special Publications Please note: The following standards were developed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC), and have been adopted by the Canadian Standards Association. These standards are available in Portable Document Format (PDF) only. CAN/CSA-ISO/IEC 7812-2:08, 2nd edition Identification cards — Identification of issuers — Part 2: Application and registration procedures (Adopted ISO/IEC 7812-2:2007).................................................................. $110 CAN/CSA-ISO/IEC 7816-2:08, 1st edition Identification cards — Integrated circuit cards — Part 2: Cards with contacts — Dimensions and location of the contacts (Adopted ISO/IEC 7816-2:2007) ......................... $60 CAN/CSA-ISO/IEC 7816-13:08, 1st edition Identification cards — Integrated circuit cards — Part 13: Commands for application management in a multi-application environment (Adopted ISO/IEC 7816-13:2007)....... $110 CAN/CSA-ISO/IEC 8484:08, 1st edition Information technology — Magnetic stripes on savingsbooks (Adopted ISO/IEC 8484:2007) ......................................................................................
    [Show full text]
  • Instructions to the Ada Rapporteur Group from SC22/WG9 For
    Work Programme of ISO/IEC JTC1/SC22/WG9 (Ada) For presentation to the SIGAda Conference December 2003 Jim Moore, [The MITRE Corporation] Convener of ISO/IEC JTC1/SC22/WG9 In this presentation, Jim Moore is representing his opinions as an officer of ISO/IEC JTC1/SC22/WG9. His opinions do not necessarily represent those of The MITRE Corporation or any of its sponsors. Goal for the Presentation A quick description of international standardization. An overview of the work programme of the standards committee responsible for Ada. A description of the process and constraints for amending the Ada language standard. Who Makes Standards? De jure standards are formal standards made Today’s by organizations authorized, in some way, to Subject make them. Examples include ISO and IEEE standards. De facto standards (more properly called specifications) are those recognized by the marketplace as important. Examples include OMG CORBA, Windows API. Developers of International Standards ISO IEC ITU ... TC176 JTC1 TC56 SC65A Quality Information Technology Dependability Functional Safety ... SC7 SC22 Software & Systems Languages, OS Engineering WG9 Ada Developers of US Standards ANSI INCITS AIAA ANS ASTM EIA IEEE PMI OMG About 550 organizations in the U. S. make standards. About half of them are accredited by ANSI, allowing them to participate in international standardization activity. Three Ways to Make a US Standard Accredited Standards Organization: An organization that does many things including making standards, e.g. IEEE. Accredited Standards
    [Show full text]
  • The Evolution of Lisp
    1 The Evolution of Lisp Guy L. Steele Jr. Richard P. Gabriel Thinking Machines Corporation Lucid, Inc. 245 First Street 707 Laurel Street Cambridge, Massachusetts 02142 Menlo Park, California 94025 Phone: (617) 234-2860 Phone: (415) 329-8400 FAX: (617) 243-4444 FAX: (415) 329-8480 E-mail: [email protected] E-mail: [email protected] Abstract Lisp is the world’s greatest programming language—or so its proponents think. The structure of Lisp makes it easy to extend the language or even to implement entirely new dialects without starting from scratch. Overall, the evolution of Lisp has been guided more by institutional rivalry, one-upsmanship, and the glee born of technical cleverness that is characteristic of the “hacker culture” than by sober assessments of technical requirements. Nevertheless this process has eventually produced both an industrial- strength programming language, messy but powerful, and a technically pure dialect, small but powerful, that is suitable for use by programming-language theoreticians. We pick up where McCarthy’s paper in the first HOPL conference left off. We trace the development chronologically from the era of the PDP-6, through the heyday of Interlisp and MacLisp, past the ascension and decline of special purpose Lisp machines, to the present era of standardization activities. We then examine the technical evolution of a few representative language features, including both some notable successes and some notable failures, that illuminate design issues that distinguish Lisp from other programming languages. We also discuss the use of Lisp as a laboratory for designing other programming languages. We conclude with some reflections on the forces that have driven the evolution of Lisp.
    [Show full text]
  • NINETEENTH PLENARY MEETING of ISO/IEC JTC 1/SC 22 London, United Kingdom September 19-22, 2006 [20060918/22] Version 1, April 17, 2006 1
    NINETEENTH PLENARY MEETING OF ISO/IEC JTC 1/SC 22 London, United Kingdom September 19-22, 2006 [20060918/22] Version 1, April 17, 2006 1. OPENING OF PLENARY MEETING (9:00 hours, Tuesday, September 19) 2. CHAIRMAN'S REMARKS 3. ROLL CALL OF DELEGATES 4. APPOINTMENT OF DRAFTING COMMITTEE 5. ADOPTION OF THE AGENDA 6. REPORT OF THE SECRETARY 6.1 SC 22 Project Information 6.2 Proposals for New Work Items within SC 22 6.3 Outstanding Actions From the Eighteenth Plenary of SC 22 Page 1 of 7 JTC 1 SC 22, 2005 Version 1, April 14, 2006 6.4 Transition to ISO Livelink 6.4.1 SC 22 Transition 7. ACTIVITY REPORTS 7.1 National Body Reports 7.2 External Liaison Reports 7.2.1 ECMA International (Rex Jaeschke) 7.2.2 Free Standards Group (Nick Stoughton) 7.2.2 Austin Joint Working Group (Nick Stoughton) 7.3 Internal Liaison Reports 7.3.1 Liaison Officers from JTC 1/SC 2 (Mike Ksar) 7.3.2 Liaison Officer from JTC 1/SC 7 (J. Moore) Page 2 of 7 JTC 1 SC 22, 2005 Version 1, April 14, 2006 7.3.3 Liaison Officer from ISO/TC 37 (Keld Simonsen) 7.3.5 Liaison Officer from JTC 1 SC 32 (Frank Farance) 7.4 Reports from SC 22 Subgroups 7.4.1 Other Working Group Vulnerabilities (Jim Moore) 7.4.2 SC 22 Advisory Group for POSIX (Stephen Walli) 7.5 Reports from JTC 1 Subgroups 7.5.1 JTC 1 Vocabulary (John Hill) 7.5.2 JTC 1 Ad Hoc Directives (John Hill) 8.
    [Show full text]
  • Gábor Melis to Keynote European Lisp Symposium
    Gábor Melis to Keynote European Lisp Symposium OAKLAND, Calif. — April 14, 2014 —Franz Inc.’s Senior Engineer, Gábor Melis, will be a keynote speaker at the 7th annual European Lisp Symposium (ELS’14) this May in Paris, France. The European Lisp Symposium provides a forum for the discussion and dissemination of all aspects of design, implementationand application of any of the Lisp and Lisp- inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop etc. Sending Beams into the Parallel Cube A pop-scientific look through the Lisp lens at machine learning, parallelism, software, and prize fighting We send probes into the topic hypercube bounded by machine learning, parallelism, software and contests, demonstrate existing and sketch future Lisp infrastructure, pin the future and foreign arrays down. We take a seemingly random walk along the different paths, watch the scenery of pairwise interactions unfold and piece a puzzle together. In the purely speculative thread, we compare models of parallel computation, keeping an eye on their applicability and lisp support. In the the Python and R envy thread, we detail why lisp could be a better vehicle for scientific programming and how high performance computing is eroding lisp’s largely unrealized competitive advantages. Switching to constructive mode, a basic data structure is proposed as a first step. In the machine learning thread, lisp’s unparalleled interactive capabilities meet contests, neural networks cross threads and all get in the way of the presentation. Video Presentation About Gábor Melis Gábor Melis is a consultant at Franz Inc.
    [Show full text]
  • JTC1 and SC22 - Terminology
    JTC1 AD Hoc Terminology, August 2005 1 JTC1 and SC22 - Terminology Background Following my offer to collect together the definitions from SC22 standards, SC22 accepted my offer and appointed me as its terminology representative (I was later also asked to represent UK and BSI) on the JTC1 ad hoc group on terminology. These notes summarise the results of collecting the SC22 definitions, and my impressions of the JTC1 ad hoc group. Roger Scowen August 2005 A collection of definitions from SC22 standards SC22 asked me to prepare a collected terminology for SC22 containing the definitions from standards for which SC22 is responsible, and asked the project editors to send me the definitions in text form. Many, but not all, project editors did so. However there are sufficient for SC22 to judge whether to complete the list or abandon it as an interesting but unprofitable exercise. Adding definitions to the database The project editor of a standard typically sends the definitions from the standard as a Word file, but it may be plain text or in Latex or nroff format. These definitions are transformed into a uniform format by a series of global ‘find & replace’ operations to produce a Word file where each definition is represented as a row of a table with three columns: the term, its definition, and any notes and/or examples. It is often easier to check this has been accomplished by copying and pasting successive attempts into Excel than examining the Word file itself. Sometimes there are special cases such as exotic characters (for example Greek or mathematical characters), special fonts, illustrations, diagrams, or tables.
    [Show full text]
  • Evaluation of Open Source Operating Systems for Safety-Critical Applications Master’S Thesis in Embedded Electronic System Design
    Evaluation of open source operating systems for safety-critical applications Master’s thesis in Embedded Electronic System Design Petter Sainio Berntsson Department of Computer Science and Engineering CHALMERS UNIVERSITY OF TECHNOLOGY UNIVERSITY OF GOTHENBURG Gothenburg, Sweden 2017 MASTER’S THESIS 2017 Evaluation of open source operating systems for Safety-critical applications Petter Sainio Berntsson Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg Gothenburg, Sweden 2017 Evaluation of open source operating systems for safety-critical applications Petter Sainio Berntsson © Petter Sainio Berntsson, 2017 Examiner: Per Larsson-Edefors Chalmers University of Technology Department of Computer Science and Engineering Academic supervisor: Jan Jonsson Chalmers University of Technology Department of Computer Science and Engineering Industrial supervisors: Lars Strandén RISE Research Institutes of Sweden Dependable Systems Fredrik Warg RISE Research Institutes of Sweden Dependable Systems Master’s Thesis 2017 Department of Computer Science and Engineering Chalmers University of Technology University of Gothenburg SE-412 96 Gothenburg Telephone +46(0) 31 772 1000 Abstract Today many embedded applications will have to handle multitasking with real-time time constraints and the solution for handling multitasking is to use a real-time operating system for scheduling and managing the real-time tasks. There are many different open source real-time operating systems available and the use of open source software for safety-critical applications is considered highly interesting by industries such as medical, aerospace and automotive as it enables a shorter time to market and lower development costs. If one would like to use open source software in a safety-critical context one would have to provide evidence that the software being used fulfills the requirement put forth by the industry specific standard for functional safety, such as the ISO 26262 standard for the automotive industry.
    [Show full text]
  • Relevant Norms and Standards
    Appendix A Relevant norms and standards A.1 A Short Overview of the Most Relevant Process Standards There is a huge number of different process standards, and Fig. A.1 contains an overview of the most relevant such standards as covered in this book, showing the topics covered. A more extensive list of the relevant standards will be provided in the following section below. ISO/IEC 15504, ISO 19011 ISO/IEC 330xx Auditing man- agement systems Process Process assessment ISO/IEC 20000-1 ISO 9001 ISO/IEC 15504-6 ISO/IEC 15504-5 Service management QM system re- System life cycle PAM Software life cycle PAM Assessments, audits Criteria system requirements quirements ISO/IEC/IEEE 15288 ISO/IEC/IEEE 12207 ITIL System life cy- Software life cy- IT Infrastruc- cle processes cle processes ture Library COBIT Life cycle processes SWEBoK Software engineering Funda- Body of Knowledge mentals ISO/IEC/IEEE 24765 ISO 9000 Systems and SW Engineering Vocabulary QM fundamentals (SEVOCAB) and vocabulary Vocabulary Systems Software Organzational IT Quality Management Engineering Engineering Fig. A.1 Overview of the most important standards for software processes © Springer Nature Switzerland AG 2018 327 R. Kneuper, Software Processes and Life Cycle Models, https://doi.org/10.1007/978-3-319-98845-0 328 A Relevant norms and standards A.2 ISO and IEC Standards The International Organization for Standardization (ISO) is the main international standard-setting organisation, working with representatives from many national standard-setting organisations. Standards referring to electrical, electronic and re- lated technologies, including software, are often published jointly with its sister organisation, the International Electrotechnical Commission (IEC), but IEC also publishes a number of standards on their own.
    [Show full text]
  • IEC 61508 Standard for Functional Safety of Electrical/Electronic/Programmable Electronic Safety-Related Systems
    IEC 61508 Overview Report A Summary of the IEC 61508 Standard for Functional Safety of Electrical/Electronic/Programmable Electronic Safety-Related Systems exida Sellersville, PA 18960, USA +1-215-453-1720 © exida IEC 61508 Overview Report, Version 2.0, January 2, 2006 Page 1 of 29 1 Overall Document Summary IEC 61508 is an international standard for the “functional safety” of electrical, electronic, and programmable electronic equipment. This standard started in the mid 1980s when the International Electrotechnical Committee Advisory Committee of Safety (IEC ACOS) set up a task force to consider standardization issues raised by the use of programmable electronic systems (PES). At that time, many regulatory bodies forbade the use of any software-based equipment in safety critical applications. Work began within IEC SC65A/Working Group 10 on a standard for PES used in safety-related systems. This group merged with Working Group 9 where a standard on software safety was in progress. The combined group treated safety as a system issue. The total IEC 61508 standard is divided into seven parts. Part 1: General requirements (required for compliance); Part 2: Requirements for electrical/electronic/programmable electronic safety-related systems (required for compliance); Part 3: Software requirements (required for compliance); Part 4: Definitions and abbreviations (supporting information) Part 5: Examples of methods for the determination of safety integrity levels (supporting information) Part 6: Guidelines on the application of parts 2 and 3 (supporting information) Part 7: Overview of techniques and measures (supporting information). Parts 1, 3, 4, and 5 were approved in 1998. Parts 2, 6, and 7 were approved in February 2000.
    [Show full text]
  • D1.5 Impact on Standards and Open Initiatives - First Analysis
    Ref. Ares(2020)1266005 - 28/02/2020 D1.5 Impact on standards and open initiatives - First analysis Version 1.0 Document Information Contract Number 825473 Project Website https://elastic-project.eu/ Contractual Deadline M15, Feb 2020 Dissemination Level CO Nature R Author(s) Thales R&T Contributor(s) BSC, ISEP, SIX, THALIT Reviewer(s) SIX, BSC Keywords Railway Safety Standards, Open Initiatives, Impact Notices: The ELASTIC project has received funding from the European Union’s Horizon 2020 research and innovation programme under the grant agreement Nº 825473. © 2019 ELASTIC. A Software Architecture for Extreme-ScaLe Big-Data AnalyticS in Fog CompuTing ECosystems. All rights reserved. D1.5 Impact on standards and open initiatives - First analysis Version 1.0 Change Log Version Author Description of Change V0.1 TRT Initial Draft Contribution on the analysis of OpenFog V0.2 BSC Initiative V0.2 TRT Contribution 61508 std, Railway std V0.3 SIX DMTF V0.4 ISEP FIWARE V0.5 BSC OpenFog V0.6 THALIT Contribution 61508 std, Railway std V0.7 TRT Final version, including revision V0.8 SIX Internal review V1.0 BSC Final adjustments. Version released to EC. 2 D1.5 Impact on standards and open initiatives - First analysis Version 1.0 Table of contents Change Log ...................................................................................... 2 1. Executive Summary ....................................................................... 5 2. Introduction ............................................................................... 6 2.1 Purpose
    [Show full text]
  • CIP Safety Protocol Training Session 0: Overview of Functional Safety and Safety Networks
    CIP Safety Protocol Training Session 0: Overview of Functional Safety and Safety Networks Virtual Training Courses Before We Begin • Introductions • All attendees are automatically muted with no video connection as a default. • Please use the Q&A to ask questions, not the chat. We will address questions as they come in. • At the end if there is time, we will take questions verbally from the attendees. We will advise if and when there is time for you to “raise your hand” if you have a question. • Please complete the 4 question post session survey. The survey will launch when you close out of the webinar. PUB00303R6, CIP Safety Protocol Training, © 2021 ODVA 2 Overview of Functional Safety Standards Jim Grosskreuz Rockwell Automation Evolution of Factory Safety In early factories, workers were encouraged to act in unsafe ways to meet production goals. Industry 2.0 and 3.0 gave us increased focus improved safety by focusing on human factors and developing best practices. Industry 4.0 requires flexibility, ease of use, human-machine collaboration, and interoperability between vendors. PUB00303R6, CIP Safety Protocol Training, © 2021 ODVA 4 Machinery Builder & Operator Responsibilities • European Union – Machinery Directive • Prescriptive approach to machinery safety • Mandates risk assessments and safe machines • United States – OSHA • Less prescriptive approach to machinery safety • Introduces fines for violations – Litigious Culture • OEMs and System Integrators aren’t protected from litigation • Elsewhere – Mixed legal and cultural environments
    [Show full text]
  • Writing Cybersecurity Job Descriptions for the Greatest Impact
    Writing Cybersecurity Job Descriptions for the Greatest Impact Keith T. Hall U.S. Department of Homeland Security Welcome Writing Cybersecurity Job Descriptions for the Greatest Impact Disclaimers and Caveats • Content Not Officially Adopted. The content of this briefing is mine personally and does not reflect any position or policy of the United States Government (USG) or of the Department of Homeland Security. • Note on Terminology. Will use USG terminology in this brief (but generally translatable towards Private Sector equivalents) • Job Description Usage. For the purposes of this presentation only, the Job Description for the Position Description (PD) is used synonymously with the Job Opportunity Announcement (JOA). Although there are potential differences, it is not material to the concepts presented today. 3 Key Definitions and Concepts (1 of 2) • What do you want the person to do? • Major Duties and Responsibilities. “A statement of the important, regular, and recurring duties and responsibilities assigned to the position” SOURCE: https://www.opm.gov/policy-data- oversight/classification-qualifications/classifying-general-schedule-positions/classifierhandbook.pdf • Major vs. Minor Duties. “Major duties are those that represent the primary reason for the position's existence, and which govern the qualification requirements. Typically, they occupy most of the employee's time. Minor duties generally occupy a small portion of time, are not the primary purpose for which the position was established, and do not determine qualification requirements” SOURCE: https://www.opm.gov/policy-data- oversight/classification-qualifications/classifying-general-schedule-positions/positionclassificationintro.pdf • Tasks. “Activities an employee performs on a regular basis in order to carry out the functions of the job.” SOURCE: https://www.opm.gov/policy-data-oversight/assessment-and-selection/job-analysis/job_analysis_presentation.pdf 4 Key Definitions and Concepts (2 of 2) • What do you want to see on resumes that qualifies them to do this work? • Competency.
    [Show full text]