DOCSLIB.ORG

DOCS) Systems Configuration Management Plan (SCMP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
DOCS) Systems Configuration Management Plan (SCMP U. S. Department of Energy Office of the Executive Secretariat Document Online Coordination System (DOCS) Systems Configuration Management Plan (SCMP) October, 1998 U. S. DEPARTMENT OF ENERGY Assistant Secretary of Human Resources Administration Deputy Assistant Secretary for Information Management Operations, Management, Systems Support, and Customer Service Groups Table of Contents 1. INTRODUCTION ...............................................................................................................................................4 1.1. PURPOSE.........................................................................................................................................................4 1.2. SCOPE.............................................................................................................................................................4 1.3. SYSTEM OVERVIEW........................................................................................................................................4 1.3.3. System Description................................................................................................................................5 1.3.4. System Architecture ...............................................................................................................................6 1.4. DOCUMENT OVERVIEW ..................................................................................................................................6 1.5. REFERENCED DOCUMENTS .............................................................................................................................7 1.5.1. Government Documents.........................................................................................................................7 1.5.2. Non-Government Documents.................................................................................................................7 1.5.3. Documents Reviewed.............................................................................................................................8 2. CONFIGURATION MANAGEMENT ORGANIZATION ............................................................................9 2.3. CONFIGURATION MANAGEMENT ROLES AND RESPONSIBILITIES ....................................................................9 2.4. CONFIGURATION MANAGEMENT ENVIRONMENT..........................................................................................11 2.4.1.1. Standing Configuration Management Board Members.................................................................................... 13 2.4.1.2. Non-Standing Configuration Management Board Members............................................................................ 14 2.4.1.3. CMB Roles and Responsibilities ..................................................................................................................... 14 2.4.2. Interface Control.................................................................................................................................15 2.4.3. Configuration Management Policy and Procedures ...........................................................................15 2.4.4. Configuration Management Methodology and Tools..........................................................................16 3. CONFIGURATION IDENTIFICATION.......................................................................................................17 3.1. CONFIGURATION ITEMS (CIS).......................................................................................................................17 3.1.1. Software Configuration Items (SWCIs) ...............................................................................................17 3.1.2. Documentation Configuration Items (DCIs) .......................................................................................18 3.1.3. Hardware Configuration Items............................................................................................................19 3.1.4. System/Sub-system Configuration Items..............................................................................................19 3.2. CONFIGURATION ITEM IDENTIFIERS..............................................................................................................19 3.2.1. SWCI Identification Numbers ..............................................................................................................19 3.2.2. Software Release and Version Identifiers............................................................................................20 3.3. BASELINE MANAGEMENT.............................................................................................................................20 3.3.1. Formal Baselines.................................................................................................................................20 3.3.2. Internal Baselines................................................................................................................................20 3.4. DOCS CONFIGURATION MANAGEMENT LIBRARIES (REPOSITORIES) ...........................................................21 3.4.1. Physical Library..................................................................................................................................21 3.4.2. Electronic Library ...............................................................................................................................22 3.5. SYSTEM RELEASE MANAGEMENT.................................................................................................................22 4. CONFIGURATION CONTROL.....................................................................................................................24 4.1. CHANGE CONTROL .......................................................................................................................................24 4.1.1. System Change Requests (SCRs) .........................................................................................................24 4.1.2. System Change Request (SCR) Priorities ............................................................................................25 4.1.3. SCR Processing...................................................................................................................................25 4.1.3.1. Roles and Responsibilities of SCR Processing ................................................................................................ 27 4.2. SOFTWARE AND DOCUMENTATION PROBLEM REPORTING............................................................................28 4.3. CHANGE TRACKING SYSTEM ........................................................................................................................29 4.4. VERSION CONTROL ......................................................................................................................................29 4.4.2. Production Phase Change Releases ....................................................................................................30 Docsscb5c.doc Page 2 of 93 2/23/2007 4.4.2.1. System Modification........................................................................................................................................ 30 4.4.2.2. System Enhancements...................................................................................................................................... 30 4.4.2.3. Software Modification and Enhancement Release Methods............................................................................ 31 4.4.2.4. User Notification of Changes........................................................................................................................... 32 4.5. NETWORK CM..............................................................................................................................................32 5. CONFIGURATION STATUS ACCOUNTING .............................................................................................33 5.1. CONFIGURATION STATUS ACCOUNTING PROCESS ........................................................................................33 5.2. CONFIGURATION STATUS ACCOUNTING REPORT (CSAR)............................................................................33 6. CONFIGURATION AUDITS AND REVIEWS.............................................................................................35 6.1. CONFIGURATION AUDITS..............................................................................................................................35 6.1.1. Functional Configuration Audit (FCA) ...............................................................................................35 6.1.2. Physical Configuration Audit (PCA) ...................................................................................................35 6.1.3. Roles and Responsibilities for Configuration Audit ............................................................................36 6.2. FCA/PCA PROCESS......................................................................................................................................38 6.3. IN-PROCESS CM STATUS REVIEWS (INFORMAL) ..........................................................................................38 6.4. PEER REVIEWS..............................................................................................................................................38 7. ARCHIVE AND RETRIEVAL........................................................................................................................39
Load more

Recommended publications
  • Administrator's Guide for SAP Simple Finance, On-Premise Edition 2 PUBLIC Content Document History
    Administrator's Guide PUBLIC Document Version: 1503 SP 7 – 17.07.17 Administrator's Guide for SAP Simple Finance, On- Premise Edition Content 1 SAP Simple Finance, On-Premise Edition............................................ 4 2 Getting Started................................................................5 3 System Landscape.............................................................11 3.1 Introduction...................................................................11 Technical System Landscape....................................................12 Central Finance..............................................................19 Deployment Options for SAP Cash Management powered by SAP HANA.....................21 4 Installation and Migration Process................................................ 22 4.1 Introduction..................................................................22 Installation and Upgrade of SAP Simple Finance, On-Premise Edition....................... 22 Technical Installation of SAP Simple Finance, On-Premise Edition..........................39 Technical Installation of SAP HANA Live 2.0, Virtual Data Model for SAP Simple Finance, On- Premise Edition.............................................................44 5 Operation Information......................................................... 46 5.1 Introduction..................................................................46 Support Packages and Patch Implementation........................................48 Data Aging.................................................................48
    [Show full text]
  • Experience and Lessons from Software Configuration Management for PMAS
    Transactions of the Korean Nuclear Society Spring Meeting Jeju, Korea, May 22, 2009 Experience and Lessons from Software Configuration Management for PMAS Joo Hyun Cho a∗, Seung Min Baek a, Hang Bae Kim a a KOPEC, I&C System Engineering Department,150 Deokjin-Dong, Yuseong-Gu, Daejon, 305-353 *Corresponding author: [email protected] 1. Introduction for performing ongoing backup of work in progress for the system periodically, and the engineers are Plant Monitoring and Annunciator System (PMAS) responsible to develop source code and prepare the for Shin-kori and Shin-wolsong nuclear power plants 1 related document. and 2 is the first localization of a large scale I&C The configuration control plan for the PCS is based system in nuclear power plant construction project. The on the principle of a single, controlled source archive. PMAS is composed of Plant Computer System (PCS), Each engineer is responsible for developing the single Plant Data Acquisition System (PDAS) and Plant source of archive and the system administrator Annunciator System (PAS). The function of the PCS is maintains the single controlled archive. Configuration to perform plant status monitoring and application control of externally developed software begins upon programs running. The PDAS performs I/O signal receipt of the software from the external supplier. acquisition, processing and data communication for the PCS, and the PAS performs the annunciation of plant 2.1.2. SCM Activities alarm through annunciator window. The PCS and the PDAS/PAS are developed by different organizations, Configuration identification is applied to all software, and they are integrated at the staging area.
    [Show full text]
  • REQUEST for INFORMATION for Enterprise Resource Planning (ERP) Software, and Implementation and Integration Services
    City of Rockville RFI 08-18 RFI for ERP Software and Services City of Rockville Rockville, Maryland REQUEST FOR INFORMATION For Enterprise Resource Planning (ERP) Software, and Implementation and Integration Services Responses Due by 2:00 P.M. Eastern Time, Friday, September 8, 2017 ISSUED BY: Jessie J. Woods, Senior Buyer Procurement Division City of Rockville, City Hall 111 Maryland Avenue Rockville, Maryland 20850 Phone: (240) 314‐8430 Fax: (240) 314‐8439 Any individual with a disability who would like to receive the information in this publication in another form may contact the ADA Coordinator at 240‐314‐8100, TDD 240‐314‐8137 MFD Outreach Program It is the intent of the City of Rockville to increase opportunities for minority, female and disabled (MFD) owned businesses to compete effectively at supplying goods, equipment, and services to the City, within the constraints of statutory purchasing requirements, departmental needs, availability, and sound economical considerations. Suggested changes and MFD enhancements to this solicitation’s requirements for possible consideration and/or inclusion in future solicitations are encouraged. Page i City of Rockville RFI 08-18 RFI for ERP Software and Services Table of Contents 1.0 INTRODUCTION ............................................................................................................................................. 3 1.1 Intent of RFI ................................................................................................................................... 3 1.2
    [Show full text]
  • System Administrator Description
    GASCOSAGE ELECTRIC COOPERATIVE SYSTEM ADMINISTRATOR GENERAL SUMMARY: The System Administrator is responsible for managing the day-to-day operation of Gascosage Electric Cooperative and GTech Fiber networks. This position provides internal technical support to users, performs technology installations and software installations, employee training, participates in technology solution selections, and ensures network reliability and security. ROLES & RESPONSIBILITIES: 1. Implement, monitor and maintain servers and network devices. 2. Responsible for ensuring the availability of servers and the network to support operational needs. 3. Troubleshoot system failures and execute procedures to restore operations. 4. Monitor server and network performance and anticipate needed changes to optimize performance. 5. Analyze hardware and software for acquisition. 6. Design and test configurations necessary for new applications, new technologies and enhanced performance. ESSENTIAL DUTIES: Provide the administration of the following systems: Windows and Linux servers, SAN storage, virtualization infrastructure, local area networks, fiber optic wide area network, telephone system, Microsoft Office 365 applications, NISC’s iVUE enterprise hardware and software, Aclara’s TWACS automated meter reading hardware and software, electronic devices including desktop computers, laptop computers, tablets, copiers, printers and cell phones. 1. Install and maintain current release level for all desktop/server operating systems, network storage and network equipment. 2. Manage internal and external telecommunication services, cellular service and equipment including setup and maintenance. System Administrator, Page 2 3. Consult with the Management and staff personnel to identify long-term computer and telecommunication needs. 4. Answer and track internal technical and application support calls and submit monthly status report updates to Management. 5. Troubleshoot equipment problems and place service calls with the appropriate maintenance vendors when necessary.
    [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]
  • TIBCO Activematrix Businessworks™ Smartmapper EPS Business UI User’S Guide
    TIBCO ActiveMatrix BusinessWorks™ SmartMapper EPS Business UI User’s Guide Version 6.0.1 August 2021 Copyright © 1999-2021. TIBCO Software Inc. All Rights Reserved. | ii Contents Figures . iv Tables . vi Chapter 1 SmartMapper EPS Business UI Overview . .1 Product Overview. 2 Chapter 2 Starting SmartMapper EPS Business UI . .3 Prerequisites . 4 Setting Up the Configuration File . 4 Starting Server. 6 Logging in to SmartMapper EPS Business UI. 7 Forgot Your Password. 8 Logging out SmartMapper EPS Business UI . 8 Stopping Server . 10 Chapter 3 User Interface Overview. .11 Home Page . 12 Main Menu . 13 Product and User Information. 13 Quick Tips Panel. 14 Recent Activity Panel . 14 Favorites Panel . 15 Relationship and Entity Management Page. 16 Left Panel Overview . 16 Right Panel Overview . 19 Chapter 4 Managing Identity Relationships . .21 Identity Relationship Management Page Overview . 22 Left Panel of the Identity Relationship Management Page . 22 Right Panel of the Identity Relationship Management Page. 23 Creating an Identity Relationship Instance . 25 Editing an Identity Relationship Instance. 29 Setting Up Favorite Relationships . 30 TIBCO ActiveMatrix BusinessWorks™ SmartMapper Enterprise Server Business UI User’s Guide iii | Contents Chapter 5 Managing Association Relationships . 31 Association Relationship Management Page Overview . 32 Left Panel of the Association Relationship Management Page . 32 Right Panel of the Association Relationship Management Page . 33 Creating an Association Relationship Instance. 34 Editing an Association Relationship Instance . 36 Setting Up Favorite Relationships . 37 Chapter 6 Managing Participants . 39 Adding a Participant Instance . 40 Changing Display Field and Setting Up Anchor Participant . 43 Chapter 7 Managing Entities . 47 Entity Management Page Overview .
    [Show full text]
  • Systems Administrator
    SYSTEMS ADMINISTRATOR SUMMARY The System Administrator’s role is to manage in-house computer software systems, servers, storage devices and network connections to ensure high availability and security of the supported business applications. This individual also participates in the planning and implementation of policies and procedures to ensure system provisioning and maintenance that is consistent with company goals, industry best practices, and regulatory requirements. ESSENTIAL DUTIES AND RESPONSIBILITIES: The Authority’s Senior Systems Manager may designate various other activities. The following statements are intended to describe the general nature and level of work being performed. They are not intended to be construed, as an exhaustive list of all responsibilities, duties and skills required of personnel so classified. Nothing in this job description restricts management's right to assign or reassign duties and responsibilities to this job at any time for any reason, including reasonable accommodation. Operational Management Manage virtual and physical servers with Windows Server 2003 – 2012 R2 and RHEL operating systems Manage Active Directory, Microsoft Office 365, and server and workstation patching with SCCM Manage the physical and virtual environment (VMware) of 300 plus servers Have familiarity with MS SQL server, windows clustering, domain controller setup, and group policy Ensure the security of the server infrastructure by implementing industry best-practices regarding privacy, security, and regulatory compliance. Develop and maintain documentation about current environment setup, standard operating procedures, and best practices. Manage end user accounts, permissions, access rights, and storage allocations in accordance with best- practices Perform and test routine system backups and restores. Anticipate, mitigate, identify, troubleshoot, and correct hardware and software issues on servers, and workstations.
    [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]