DOCSLIB.ORG

Configuration Management for Transportation Management Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Configuration Management for Transportation Management Systems Configuration Management for Transportation Management Systems Final Report September 2003 Notice This document is disseminated under the sponsorship of the Department of Transportation in the interest of information exchange. The United States Government assumes no liability for its contents or use thereof. This report does not constitute a standard, specification, or regulation. The United States Government does not endorse products or manufacturers. Trade and manufacturers’ names appear in this report only because they are considered essential to the object of the document. Technical Report Documentation Page 1. Report No. 2. Government Accession No. 3. Recipient's Catalog No. FHWA-OP-04-013 4. Title and Subtitle 5. Report Date Configuration Management for Transportation Management Systems September 2003 6. Performing Organization Code 7. Author(s) 8. Performing Organization Report No. Dr. Brian Smith, Smart Travel Laboratory – University of Virginia 9. Performing Organization Name and Address 10. Work Unit No. (TRAIS) University of Virginia Department of Civil Engineering Thornton Hall; B-227 11. Contract or Grant No. 351 McCormick Road DTFH61-01-C-00180 P.O. Box 400742 Charlottesville, VA 22904-4742 12. Sponsoring Agency Name and Address 13. Type of Report and Period Covered Operations Office of Transportation Management Final Report Federal Highway Administration May – September 2003 400 Seventh Street, SW Washington, DC 20590 14. Sponsoring Agency Code 15. Supplementary Notes Jon Obenberger, FHWA Operations Office of Transportation Management, Contracting Officer’s Technical Representative (COTR) 16. Abstract Configuration Management for Transportation Management Systems is intended to provide guidance for transportation professionals who are either (a) seeking to improve change management in a traffic management system or regionally integrated intelligent transportation system by introducing formal CM or (b) using CM currently and require a technical reference to support their activities. 17. Key Word 18. Distribution Statement configuration management, traffic management system, No restrictions transportation management system, intelligent transportation system 19. Security Classif. (of this report) 20. Security Classif. (of this page) 21. No. of Pages 22. Price Unclassified Unclassified 210 Form DOT F 1700.7 (8-72) Reproduction of completed page authorized This page intentionally left blank. Configuration Management for Transportation Management Systems TABLE OF CONTENTS CHAPTER 1 – Introduction to Configuration Management and Transportation Management Systems.....................1-1 CHAPTER 2 – Configuration Management and Transportation Management Systems – Current Practices.............2-1 CHAPTER 3 – Configuration Management Processes................................................................................................3-1 CHAPTER 4 – Configuration Management Plan...........................................................................................................4-1 CHAPTER 5 – Configuration Management Baselines ..................................................................................................5-1 CHAPTER 6 – Configuration Management Program Making it Work in Your Agency.................................................6-1 CHAPTER 7 – Configuration Management and the System Life Cycle .......................................................................7-1 CHAPTER 8 – Configuration Management Tools .........................................................................................................8-1 CHAPTER 9 – Resources to Support Configuration Management Programs..............................................................9-1 CHAPTER 10 – Conclusion..........................................................................................................................................10-1 APPENDIX A – Description/Summary of EIA 649........................................................................................................ A-1 APPENDIX B – Annotated Bibliography ....................................................................................................................... B-1 APPENDIX C – Summary of CM Plans ........................................................................................................................C-1 APPENDIX D – System Descriptions............................................................................................................................D-1 APPENDIX E – List of References................................................................................................................................E-1 APPENDIX F – List of Acronyms................................................................................................................................... F-1 LIST OF FIGURES Figure 1.1 – Configuration Management Process..........................................................................................................1-5 Figure 2.1 – Functional Classes of Systems...................................................................................................................2-2 Figure 2.2 – CM Use by System Size .............................................................................................................................2-3 Figure 2.3 – Core System Software ................................................................................................................................2-3 Figure 2.4 – Use of CM Based on Software Class .........................................................................................................2-4 Figure 2.5 – Percent of Agencies Using CM that Have a Formal CM Plan...................................................................2-5 Figure 2.6 – CM Tools Used by Agencies.......................................................................................................................2-7 Figure 2.7 – Lead Organization During Planning Phase................................................................................................2-8 Figure 2.8 – Lead Organization During Design Phase...................................................................................................2-8 Figure 2.9 – Lead Organization During Development Phase.........................................................................................2-9 Figure 2.10 – Lead Organization During Operations & Maintenance Phase.................................................................2-9 Figure 2.11 – Subsystems Covered by CM ..................................................................................................................2-10 Figure 2.12 – Agencies Including CM Elements...........................................................................................................2-11 Figure 3.1 – Levels of Hardware Configuration Identification .......................................................................................3-7 iii Configuration Management for Transportation Management Systems Figure 3.2 – NaviGAtor CCB Organization ..................................................................................................................3-23 Figure 3.3 – Configuration Control Board Organization ..............................................................................................3-26 Figure 3.4 – SCPC CM Subcommittee Organization ..................................................................................................3-27 Figure 3.5 – Georgia NaviGAtor SCR Flow ..................................................................................................................3-30 Figure 3.6 – CHART II Change Priorities......................................................................................................................3-32 Figure 3.7 – CHART II Change Control Process..........................................................................................................3-33 Figure 3.8 – Richmond Trouble Report Form ...............................................................................................................3-35 Figure 4.1 – Southern California Priority Corridor Identification Structure...................................................................4-11 Figure 4.2 – Southern California Priority Corridor Change Control Process ...............................................................4-11 Figure 4.3 – Southern California Priority Corridor CM Program Organization.............................................................4-12 Figure 5.1 – Baselines in the System Life Cycle (Control gate letters refer to table 5.1)..............................................5-4 Figure 6.1 – Project Office Organization.......................................................................................................................6-12 Figure 7.1 – Configuration Items and Supporting Elements...........................................................................................7-2 Figure 7.2 – The Systems Engineering Life Cycle and Configuration Items .................................................................7-3 Figure 7.3 – NaviGAtor Software Development Cycle ................................................................................................7-10 Figure C.1 – SCR Flow...................................................................................................................................................C-9 LIST OF TABLES Table 1.1 – Handbook Usage Recommendations........................................................................................................1-10
Load more

Recommended publications
  • MITRE Defense Agile Acquisition Guide
    i Approved for Public Release; Distribution Unlimited. 14-0391 Executive Summary The Department of Defense (DoD) needs an acquisition framework for information technology (IT) that can keep pace with rapidly changing technologies and operations, including the challenges associated with information assurance. Agile development practices can help the DoD to transform IT acquisition by delivering capabilities faster and responding more effectively to changes in operations, technology, and budgets. This guide provides DoD acquisition professionals with details on how to adopt Agile practices within each element of their programs, thus helping them to succeed in an increasingly complex environment. Agile has emerged as the leading industry software development methodology, and has seen growing adoption across the DoD and other federal agencies. Agile practices enable the DoD to achieve reforms directed by Congress and DoD Acquisition Executives. DoD Instruction 5000.02 (Dec 2013) heavily emphasizes tailoring program structures and acquisition processes to the program characteristics. Agile development can achieve these objectives through: Focusing on small, frequent capability releases Valuing working software over comprehensive documentation Responding rapidly to changes in operations, technology, and budgets Actively involving users throughout development to ensure high operational value Agile practices integrate planning, design, development, and testing into an iterative lifecycle to deliver software at frequent intervals. Developers can demonstrate interim capabilities to users and stakeholders monthly. These frequent iterations effectively measure progress, reduce technical and programmatic risk, and respond to feedback and changes more quickly than traditional methods. Programs can adopt Agile practices within current policy by tailoring program processes and structure to deliver releases every 6–12 months.
    [Show full text]
  • Managing the Configuration of Information Systems with a Focus on Security
    MANAGING THE CONFIGURATION OF INFORMATION SYSTEMS WITH A FOCUS ON SECURITY Shirley Radack, Editor Computer Security Division Information Technology Laboratory National Institute of Standards and Technology U.S. Department of Commerce Organizations have to make frequent changes to their information systems in order to implement new and updated hardware and software components, correct software flaws and other errors, address new security threats, and adapt to changing business objectives. These constant changes result in adjustments being made to the configuration of information systems; these activities could have an impact on the security of the systems and operations. In developing information systems, organizations employ many components that can be interconnected in different arrangements to meet the organization’s business, mission, and information security needs. To protect information systems and information, organizations need techniques for the secure configuration, operation, and management of system components, including mainframes, workstations, servers, networks, operating systems, middleware, and applications, and for the management and control of risks to systems and information. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) has issued a new guide to help organizations develop a well-defined process for managing and controlling secure system configurations, and for managing risks in information systems. NIST Special Publication 800-128, Guide to Security- Focused
    [Show full text]
  • Optimization of Configuration Management Processes
    DEGREE PROJECT IN INFORMATION AND COMMUNICATION TECHNOLOGY, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2016 Optimization of Configuration Management Processes JOHAN KRISTENSSON KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF INFORMATION AND COMMUNICATION TECHNOLOGY Abstract Configuration management is a process for establishing and maintaining consistency of a product's performance, as well as functional and physical attributes with regards to requirements, design and operational information throughout its lifecycle. The way configuration management is implemented in a project has a huge impact on the project’s chance of success. Configuration management is, however, notoriously difficult to implement in a good way, i.e. in such a way that it increases performance and decrease the risk of projects. What works well in one field may be difficult to implement or will not work in another. The aim of this thesis is to present a process for optimizing configuration management processes, using a telecom company as a case study. The telecom company is undergoing a major overhaul of their customer relationship management system, and they have serious issues with quality of the software that is produced and meeting deadlines, and therefore wants to optimize its existing CM processes in order to help with these problems. Data collected in preparation for the optimization revealed that configuration management tools were not used properly, tasks that could be automated were done manually, and existing processes were not built on sound configuration management principles. The recommended optimization strategy would have been to fully implement a version handling tool, and change the processes to take better advantage of a properly implemented version handling tool.
    [Show full text]
  • Industrial Maintenance
    Industrial Maintenance Program CIP: 47.0303 – Industrial Maintenance Ordering Information Research and Curriculum Unit for Workforce Development Vocational and Technical Education Attention: Reference Room and Media Center Coordinator P.O. Drawer DX Mississippi State, MS 39762 www.rcu.msstate.edu/curriculum/download/ (662) 325-2510 Direct inquiries to Doug Ferguson Andy Sims Instructional Design Specialist Program Coordinator P.O. Drawer DX Office of Vocational Education and Workforce Mississippi State, MS 39762 Development (662) 325-2510 Mississippi Department of Education E-mail: [email protected] P.O. Box 771 Jackson, MS 39205 (601) 359-3479 E-mail: [email protected] Published by Office of Vocational and Technical Education Mississippi Department of Education Jackson, MS 39205 Research and Curriculum Unit for Workforce Development Vocational and Technical Education Mississippi State University Mississippi State, MS 39762 Robin Parker, EdD, Curriculum Coordinator Jolanda Harris, Educational Technologist The Research and Curriculum Unit (RCU), located in Starkville, MS, as part of Mississippi State University, was established to foster educational enhancements and innovations. In keeping with the land grant mission of Mississippi State University, the RCU is dedicated to improving the quality of life for Mississippians. The RCU enhances intellectual and professional development of Mississippi students and educators while applying knowledge and educational research to the lives of the people of the state. The RCU works within
    [Show full text]
  • Business Rule Based Configuration Management and Software System Implementation Using Decision Tables
    Business Rule Based Configuration Management and Software System Implementation Using Decision Tables Olegas Vasilecas, Aidas Smaizys Vilnius Gediminas Technical University, Sauletekio av. 11, LT-10223 Vilnius, Lithuania [email protected], [email protected] Abstract. Deployment and customization of the software in different information systems of separate organizations challenge large requirement conformity, project and specification management, design and architecture complexity, code integration, compatibility and interoperability issues, frequently causing the need of reengineering through the entire all the system development lifecycle. The paper proposes new business rule based method of information system configuration management and automated way of configuration implementation into the final software system code. 1 Introduction Business systems are functioning according to business rules in specific business domain. Due to dynamic of its nature, business environment is changing frequently according to internal and external influences such as changes in law, new competition etc. [1]. However Business rules (BR) of particular problem domain are similar in several organizations but they are never applied the same way even they depend on the same legal regulations. Production and implementation of such a software system into the large amount of slightly different information systems of separate organizations challenge large requirement conformity, project and specification management, design and architecture complexity,
    [Show full text]
  • ITIL Asset and Configuration Management in the Cloud
    ITIL Asset and Configuration Management in the Cloud January 2017 © 2017, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Contents Introduction 1 What Is ITIL? 1 AWS Cloud Adoption Framework 2 Asset and Configuration Management in the Cloud 3 Asset and Configuration Management and AWS CAF 5 Impact on Financial Management 5 Creating a Configuration Management Database 6 Managing the Configuration Lifecycle in the Cloud 8 Conclusion 9 Contributors 10 Abstract Cloud initiatives require more than just the right technology. They also must be supported by organizational changes, such as people and process changes. This paper is intended for IT service management (ITSM) professionals who are supporting a hybrid cloud environment that leverages AWS. It outlines best practices for asset and configuration management, a key area in the IT Infrastructure Library (ITIL), on the AWS cloud platform.
    [Show full text]
  • Software Project Monitoring and Control
    Module 12 Software Project Monitoring and Control Version 2 CSE IIT, Kharagpur Lesson 31 Risk Management and Software Configuration Management Version 2 CSE IIT, Kharagpur Specific Instructional Objectives At the end of this lesson the student would be able to: • Identify the main categories of risks which can affect a software project. • Explain how to assess a project risk. • Identify the main strategies to plan for risk containment. • Explain what risk leverage is. • Explain how to handle the risk of schedule slippage. • Explain what is meant by configuration of a software product. • Differentiate among release, version and revision of a software product. • Explain the necessity of software configuration management. • Identify the principal activities of software configuration management. • Identify the activities carried out during configuration identification. • Identify the activities carried out during configuration control. • Identify the popular configuration management tools. Risk management A software project can be affected by a large variety of risks. In order to be able to systematically identify the important risks which might affect a software project, it is necessary to categorize risks into different classes. The project manager can then examine which risks from each class are relevant to the project. There are three main categories of risks which can affect a software project: Project risks. Project risks concern varies forms of budgetary, schedule, personnel, resource, and customer-related problems. An important project risk is schedule slippage. Since, software is intangible, it is very difficult to monitor and control a software project. It is very difficult to control something which cannot be seen. For any manufacturing project, such as manufacturing of cars, the project manager can see the product taking shape.
    [Show full text]
  • Quality Assurance and Configuration Management
    Quality Assurance and Configuration Management Energy, Climate, & Sandia National Laboratories implements quality assurance and configuration Infrastructure Security systems essential to the control and traceability of modeling used to demonstrate regulatory compliance. Introduction agencies, including, most significantly, the U.S. Nuclear Regulatory Commission Sandia National Laboratories has a long and the U.S. Environmental Protection history of involvement in significant Agency, as well as various federal, state, national programs directed at solving and other organizations. Among more the national problem of managing the notable successes of this work has been disposal of various forms of nuclear the adaptation of quality assurance wastes. These involvements include to activities sponsored largely by the significant responsibility on the Waste U.S. Department of Energy involved Isolation Pilot Plant (WIPP), the Yucca in the characterization, selection, and Mountain Site Characterization Project performance analyses associated with (YMP), the Hanford Tank Waste programs involving nuclear waste Remediation System (TWRS), and management. Quality assurance the Greater Confinement Disposal requirements originated from a need to (GCD) programs. In addition, control and assure the quality of nuclear Sandia has also played major roles power plant design, construction, and in nuclear waste transportation, operations; modifying these concepts and in several environmental for application to scientific investigation remediation and restoration and characterization activities was a programs, including those at Fernald, necessary and beneficial effort that Ohio, and Hanford, Washington. has proven successful for nuclear waste A key to the success of our activities management. on these programs, particularly for Decades of experience under the WIPP, YMP, TWRS, and GCD, was the scrutiny of independent audits, development and application of quality identifying quality deficiencies, and assurance for program activities.
    [Show full text]
  • Service Asset and Configuration Management (SACM/CMDB) Process
    Service Transition SERVICE ASSET AND CONFIGURATION MANAGEMENT PROCESS VERSION: 4.3 REVISION DATE: February 23, 2017 Service Transition USER GUIDE Service Asset and Configuration Management Process 4.3 | 02/23/2017 Contents Section 1. Introduction ......................................................................................... 1 1.1 Purpose .............................................................................................. 1 1.2 Goal .................................................................................................... 1 1.3 Overview ............................................................................................ 1 1.4 Key Relationships with other processes ........................................ 2 1.5 Definitions .......................................................................................... 2 Section 2. Roles and Responsibilities .................................................................. 4 2.1 Process Owner/Configuration Manager ......................................... 4 2.2 Configuration Item Class Owner ..................................................... 4 2.3 Configuration Item Class Administrator ......................................... 4 2.4 Configuration Item Company Administrator .................................. 5 2.5 IT Service Continuity Management (ITSCM) Role......................... 5 2.6 IT Staff ................................................................................................ 5 2.7 ITSM Product Manager ....................................................................
    [Show full text]
  • Operational Availability Modeling for Risk and Impact Analysis
    Operational Availability Modeling for Risk and Impact Analysis David J. Hurst Manager Accreditation and Audits Aerospace Engineering and Project Management Division National Defence Headquarters Major General George R. Pearkes Building 400 Cumberland Street Ottawa, Ontario K1A 0K2 CANADA [email protected] ABSTRACT Availability is a system performance parameter which provides insight into the probability that an item or system will be available to be committed to a specified requirement. Depending on the application, availability can be defined to include reliability, maintainability and logistic support information. For fleet management purposes, the ability to quantify availability in terms of all of its contributing elements is essential. This paper provides a discussion on a steady state operational availability model which can be used to assist the Canadian Air Force in its aircraft fleet management requirements. The availability model embodies scheduled and unscheduled maintenance and allows for impact analysis using in-service maintenance data. The model is sensitive to fleet size, aircraft flying rate, frequency of downing events, aircraft maintainability, scheduled inspection frequency, and scheduled inspection duration. The predictive capability of this availability model is currently providing the Canadian Air Force with a more sophisticated maintenance analysis decision support capability. In order for this paper to be available for general distribution, it must be unclassified. As a result, the case studies presented do
    [Show full text]
  • Milestones in Future Mobility, Annual Report 2018
    ANNUAL REPORT 2018 #Milestones in Future Mobility ANNUAL 2018 ANNUAL REPORT We are inventing the mobility of the future, in which we think and work in new ways. We invite you to learn more about how we see the future today. CONTENTS 1 4 TO OUR SHAREHOLDERS CORPORATE Page 4 BMW Group in Figures GOVERNANCE Page 8 Report of the Supervisory Board Page 200 Statement on Corporate Governance Page 16 Statement of the Chairman of the (Part of the Combined Management Report) Board of Management Page 200 Information on the Company’s Governing Constitution Page 201 Declaration of the Board of Management and of the Page 20 BMW AG Stock and Capital Markets in 2018 Supervisory Board Pursuant to § 161 AktG Page 202 Members of the Board of Management Page 203 Members of the Supervisory Board Page 206 Composition and Work Procedures of the Board of 2 Management of BMW AG and its Committees Page 208 Composition and Work Procedures of the COMBINED Super visory Board of BMW AG and its Committees Page 215 Disclosures Pursuant to the Act on Equal MANAGEMENT REPORT Gender Participation Page 216 Information on Corporate Governance Practices Applied Page 26 General Information and Group Profile beyond Mandatory Requirements Page 26 Organisation and Business Model Page 218 Compliance in the BMW Group Page 36 Management System Page 223 Compensation Report Page 40 Report on Economic Position (Part of the Combined Management Report) Page 40 General and Sector-specific Environment Page 239 Responsibility Statement by the Page 44 Overall Assessment by Management Company’s
    [Show full text]
  • 2. Configuration Management
    Computer Science and Software Engineering University of Wisconsin - Platteville 2. Configuration Management Yan Shi SE 3730 / CS 5730 Lecture Notes Outline . What is configuration management? — Identification — Change control — Status accounting — Audit and review . CM techniques and practices — lock-modify-unlock — copy-modify-merge — RCS — branching — deltas . CM tools Why is CM needed? . ``This worked yesterday and doesn't work now.” What happened? . ``The user manual says to do this, but when I do it, something different happens.'' Which is correct, the manual or the code? Why was one changed? . ``The code changes that I made last week are no longer in the code.” What happened to the fix? Who changed the code and Why? . ``The listing doesn't match what the program does!'' Which is correct? . ``Did the bug get fixed in this copy, too?'' Why is CM needed? . Control the changes — Versions of documents need to be combined to form a product, or configuration — With many people working on many files, inconsistencies can occur . Required for testing — We must know and control what source was used to produce a software system in order to know what is being tested — We need to be able to build and rebuild a software system reliably . Reduce the quality cost — https://www.youtube.com/watch?v=Ij1yDpfZI8Q CM CONCEPTS AND COMPONENTS What is Configuration Management? . Software CM is a discipline for managing the evolution of software systems throughout all stages of the software life cycle. SCM is a component of SQA system. — Infrastructure component — Organizational framework . SQA teams are often required to take the responsibility of managing the CM system.
    [Show full text]