CalMod Design-Build Electrification Services
|
|
- Joseph Strickland
- 8 years ago
- Views:
Transcription
1 SECTION SYSTEMS INTEGRATION AND INTEGRATOR REQUIREMENTS PART 1 GENERAL DESCRIPTION A. This section specifies the system-wide integration requirements for the Caltrain Electrification system, i.e. the System. GENERAL A. The Design-Build Contractor, identified as Contractor, shall be responsible for the System-wide integration of all hardware and software within their scope of Work. The Contractor shall be responsible for the implementation and management of the integration of the System and for their design, installation and testing interfaces with the existing and new external systems that include but are not limited to JPB Engineering, Operations and safety, EMU Vehicles, CBOSS PTC, Signals, Highway Grade Crossings, Communications, SCADA, OCS, TPSS, CEMOF, ROCS, other railroad tenants and operations, associated hardware, software and human operations and maintenance support systems. B. The Contractor shall be responsible for systems integration to ensure: compliance with all performance and functional requirements, safety certification requirements, System/subsystem reliability, availability and maintainability requirements, and provision of integrated training and maintenance support materials. C. The Contractor shall be responsible to coordinate with all affected stakeholders satisfactory integrated solutions to resolve all integration issues. D. The Contractor shall review and coordinate their Work with the Reference Documents provided in Volume 4 as is necessary to integrate their Work into the System in accordance with the requirements of the Contract. DEFINITIONS A. Definitions shall be in accordance with IEEE 100, The Authoritative Dictionary of IEEE Standards Terms and Definitions, and the Glossary of Terms and Acronyms in the Scope of Work. REFERENCE STANDARDS A. The Contractor s systems integration plan and procedures shall be based upon a rigorous and Project specific approach, such as that defined in IEEE 1220: IEEE Standard for Application and Management of the Systems Engineering Process, or approved equivalent. SUBMITTALS A. Systems Integration Management Plan; B. Requirements Traceability (Baseline) Matrix and monthly summary reports on requirements traceability and management including planned actions; C. Configuration Management Plan; Contract # 14-PCJPB-P-053 Page 1 of 6 (Rev. 2.0, )
2 D. System Database Standards, System Database Administration Tool(s); E. Design Review Submissions; F. Verification and validation compliance reports as defined in the System Integration Management Plan; G. The JPB will facilitate meetings on a regular (bi-weekly or as otherwise needed at the discretion of the JPB) basis at which the Contractor and interfacing 3rd party entities shall report progress and issues on work to define the resolution of associated interfaces. Attendees may include JPB departments or contractors that are required to alter operational, maintenance and logistical support systems and processes for which they are responsible. Contractor participation, including the preparation of any materials relating to interface status reporting shall be included in the Contract price. PART 2 PRODUCTS Not Used PART 3 EXECUTION 3.01 GENERAL A. System Integration Management Plan: 1. The Contractor shall develop and submit for SONO a System Integration Management Plan, as part of the Systems Engineering Plan that delineates all systems integration activities throughout the lifecycle of the project. The System Integration Management Plan shall describe how the Contractor plans to manage and control integration risk associated with interoperability and other mission critical aspects. 2. The System Integration Management Plan shall: a. Define how progress and issues are communicated within the Contractor s organization and how such information is then consolidated for reporting to JPB; b. Establish the activities and documentation for validation and verification of the System including: i. Verification actions to incrementally confirm that the delivered System, subsystems and services will meet the requirements of these Specifications. ii. Validation actions to incrementally confirm that the behavior of the delivered System, subsystems and services will meet JPB s needs and standards. c. Establish the activities and documentation requirements of systems integration activities, necessary to support the Reliability, Availability, Maintainability (RAM) Program, the Safety Program, the FRA Certification process including submittals and overall System Safety Certification. B. Requirements Traceability and Management (RTM): Contract # 14-PCJPB-P-053 Page 2 of 6 (Rev. 2.0, )
3 1. The Contractor shall establish and manage a RTM process, using a JPB-approved requirements management and traceability process of the specified requirements and resulting works deliverables. The Contractor shall provide to JPB all required software licenses for the JPB- RTM tool installed on PCs. 2. The Contractor shall develop a Systems RTM Plan (as part of the Systems Integration Management Plan) that identifies the roles and responsibilities of the Contractor (including all subcontractors). 3. The Contractor shall identify all requirements, and systems integration requirements, and shall be responsible for their incorporation into the RTM process. The performance requirements and the systems integration requirements shall be linked through the hierarchy of Contractor prepared design documents to the appropriate Contract functional and performance requirements. 4. The Contractor shall identify and attribute that all subsystem performance requirements and functional requirements, and shall be responsible for their incorporation into the RTM process. 5. The Contractor shall identify and link the validation and verification activities for each construction segment of the project to the formal requirements, including those in the phases of; design, factory test, post installation test, subsystemslevel test, both factory and field integrated systems test, operational activation and pre-revenue test, and reliability, availability and maintainability demonstration/test including validation and verification of change throughout the contract. 6. The Contractor shall establish parameters for the RTM attributes and linkages for RTM items that are needed in the RTM database for systems integration. The RTM shall provide the ability to trace a contract requirement down to the subsystem and detailed design aspects and the software and hardware that implement the requirement and conversely that ability to trace from each piece of hardware or software the features and capabilities that link back up to contract requirements. 7. The Contractor shall establish attributes of the RTM to track verification and validation of all vital requirements throughout the design and test processes. 8. The Contractor shall submit traceability and records of all factory and field test plans, test procedures and test results to the specific contract requirement or corresponding design requirements. The Contractor shall include RTM aspects of all factory and field integration tests of software running in the host hardware, all re-test for new hardware or software releases, integration test within the subsystems, factory tests of functionality and interoperability before shipment, post installation tests, and final systems-level on-site cut-over tests. C. PTC Configuration Management: 1. The Contractor shall be responsible for updating overall configuration management as modified by this project. a. The Contractor shall utilize the JPB approved CBOSS Configuration Management Plan, which may be included as a part of the Systems Engineering Plan, to document a configuration management program including processes for declaration of configuration baselines, change Contract # 14-PCJPB-P-053 Page 3 of 6 (Rev. 2.0, )
4 D. Design Reviews: requests, modifications, and update releases. Corrective changes that materially affect the configuration, or have the potential for affecting the configuration, shall be treated as change requests. b. The Configuration Management Plan shall cover all System hardware and software design, design analysis and hazard analysis documentation, factory and field test plans and procedures, associated test equipment and simulation tools, test facilities, operations, JPB field force account support and maintenance documentation and all other items that are normally placed under configuration control for a safety and mission critical system. CBOSS plans and specifications are included in Volume 4 as reference. 1. The Contractor shall be responsible for leading all design reviews. 2. The Contractor shall be responsible for verification and validation of all systemlevel design requirements. Requirements traceability verification that is programmed to be achieved by inspection of the design shall be formally documented including references to any higher level hierarchal documents. 3. The Contractor shall report all design concerns and deficiencies to JPB as soon as the concern/deficiency has been identified and with sufficient detailed information to for a preliminary characterization of the problem. E. Working Groups and Design Workshops: 1. The Contractor shall schedule and administer a series of workshops with representatives from JPB to incrementally advance systems engineering to allow re-validation of the design and integrated work throughout the life cycle of the project. The primary objective will be to resolve design issues as early as possible and in advance of formal verification activities that are the scheduled design review and test milestones. 2. The Contractor shall lead or participate, as requested, in Working Groups with JPB staff, consultants to JPB, and other nominated participants. 3. The Contractor shall maintain a log of all issues and potential requirements changes that arise from the Working Groups. F. Performance Compliance: 3.02 DESIGN REVIEW PROCESS 1. The Contractor shall be responsible for ensuring compliance with the specified functionality and performance requirements. 2. The Contractor shall allocate performance and functional requirements to each Electrification and Signal subsystem and interfacing element of work to ensure that the specified requirements are met. The Contractor shall report the verification of these requirements to JPB throughout the project. 3. The Contractor shall conduct performance simulations to demonstrate the throughput and runtime capabilities of the traction electrification, integrated wayside signaling and grade crossing warning Systems. A. During System design development, JPB will monitor the Contractor s progress to verify compliance with the requirements through design reviews and audits. Design reviews Contract # 14-PCJPB-P-053 Page 4 of 6 (Rev. 2.0, )
5 and audits shall be conducted jointly by JPB, the Contractor, and other JPB-designated parties. SONO by JPB shall not constitute relief from contractual obligations. Reviews shall be conducted incrementally, and, as a minimum, grouped for the major system elements listed below. All ancillary and associated designs shall be included in the reviews of the major system elements below. Each succeeding level of design review shall update the material from the previous review as well as advancing the design to the next level. B. Design reviews shall be held to review system and subsystems designs for each of the following major areas. Reviews can be combined for logically associated system elements and locations, and are subject to SONO by the JPB. 1. Electrification: a. OCS b. TPSS c. SCADA d. CEMOF e. JPB operations, maintenance and safety 2. Signals & Communications: 3. Vehicles a. CBOSS/PTC; b. ROW Signals; c. Highway Grade Crossings; d. Communications e. ROCs a. EMU Vehicles C. Provide all required design review materials for a scheduled design review at least twenty (20) working days prior to the proposed review date and notice to the JPB PM for all design reviews. D. Preliminary Design Review (PDR): 1. The purpose of these reviews is to ensure that the Contractor fully understands the basis of design and can express rational assumptions relating to the design at the start of the detail design process. A PDR shall be conducted by the Contractor for each interface, subsystem or combination thereof prior to detail design so that JPB can determine that the Contractor will adequately progress the design at the start. 2. Submit to JPB, within 60 days after the Contract Notice of Award, a date by which a satisfactory PDR can be performed. Hold the reviews on mutually agreeable dates at a JPB designated location. JPB may, at its sole discretion, elect to hold the review at a contractor s facility. E. Critical Design Review (CDR): Contract # 14-PCJPB-P-053 Page 5 of 6 (Rev. 2.0, )
6 1. Conduct these reviews incrementally when the detail design of an item is at least to the 50% design completion level. This review will determine that the detail design of the item under review will satisfy the design requirements in these Specifications and to establish exact interface relationships between the item and other items of equipment, software or facilities being procured under this or other contracts. Hold the review on mutually agreeable dates at a JPB designated location. JPB may, at its sole discretion, elect to hold the review at a contractor s facility. 2. The final wayside layouts and CIH, case, and other facility layouts with maintenance facilities and clearances shall be completed no later than CDR. 3. The final housing construction detail, including cabling facilities and requirements shall be completed no later than CDR. 4. Detailed plans, procedures and schedules for the installation and commissioning of the System shall be completed no later than CDR. F. Final Design Review (FDR): 1. The final design review shall be conducted and the design reviewed for SONO by JPB. END OF SECTION Contract # 14-PCJPB-P-053 Page 6 of 6 (Rev. 2.0, )
TfNSW Standard Requirements TSR T Technical Management
Template Applicable to: Transport Projects Quality Management System Status: Division: Approved Transport Projects Version: 5.0 Desksite No.: 3455797_1 Date of issue: 1 July 2014 Effective date: 1 July
More informationProject Management Guidelines
Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.
More informationCriteria for Flight Project Critical Milestone Reviews
Criteria for Flight Project Critical Milestone Reviews GSFC-STD-1001 Baseline Release February 2005 Approved By: Original signed by Date: 2/19/05 Richard M. Day Director, Independent Technical Authority
More information8. Master Test Plan (MTP)
8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across
More informationSTATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840
MARYLAND STATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840 Bobbie S. Mack, Chairman David J. McManus, Jr., Vice Chairman Rachel T. McGuckian Patrick H. Murray Charles
More informationPROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
More informationCalMod Design-Build Electrification Services
SECTION 28 16 00 INTRUSION DETECTION SYSTEM PART 1 - GENERAL 1.1 DESCRIPTION A. This section describes the detailed technical requirements for the Intrusion Detection System (IDS), where the Contractor
More informationD R A F T. Resource Ordering and Status System (ROSS) Software Configuration Management Guidelines
TO #GA81 Resource Ordering and Status System (ROSS) D R A F T Resource Ordering and Status System (ROSS) Software Configuration Management Guidelines June 28, 2000 Version 1.1 Contract: GS-35F-4863G Delivery
More informationITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE
PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution
More informationThe Software Development Life Cycle (SDLC)
Document ID: Version: 2.0 1 / 22 2 TABLE OF CONTENTS INTRODUCTION... 4 THE SDLC WATERFALL... 4 ALLOWED VARIATIONS... 5 OTHER SDLC MODELS... 6 REFERENCES... 7 GENERIC STAGE... 8 KICKOFF PROCESS... 8 INFORMAL
More informationSoftware Project Management Plan (SPMP)
Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.
More informationSOFTWARE MANAGEMENT PROGRAM. Software Testing Checklist
SOFTWARE MANAGEMENT PROGRAM Software Testing Checklist The following checklist is intended to provide system owners, project managers, configuration managers, and other information system development and
More informationWhat methods are used to conduct testing?
What is testing? Testing is the practice of making objective judgments regarding the extent to which the system (device) meets, exceeds or fails to meet stated objectives What the purpose of testing? There
More information6500m HOV Project Stage 1: A-4500 HOV
6500m HOV Project Stage 1: A-4500 HOV Systems Engineering, Integration & Testing Plan Document Control No.: 0000000 01-November-2009 WOODS HOLE OCEANOGRAPHIC INSTITUTION WOODS HOLE, MA 02543 Document Control
More informationSOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
More informationSOFTWARE ASSURANCE STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8739.8 w/change 1 Space Administration July 28, 2004 SOFTWARE ASSURANCE STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-2201-93 DATED NOVEMBER
More informationSoftware Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201
PURCHASE ORDER ATTACHMENT Q-201A Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201 1. A qualified employee shall be selected by the Software Quality Manager
More informationPROJECT SCOPE STATEMENT
PROJECT SCOPE STATEMENT Note: Any work not explicitly included in this Project Scope Statement is implicitly excluded from the project. Create links to referenced documents (e.g., Link_To_ ) by using Insert
More informationProject Management Plan for
Project Management Plan for [Project ID] Prepared by: Date: [Name], Project Manager Approved by: Date: [Name], Project Sponsor Approved by: Date: [Name], Executive Manager Table of Contents Project Summary...
More informationAppendix E Program Management Plan Template
Appendix E Program Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions
More informationVERIFICATION (TEST) PLAN GUIDELINES
I-680 SMART CARPOOL LANE PROJECT SYSTEM ENGINEERING MANAGEMENT PLAN VERIFICATION (TEST) PLAN GUIDELINES PLAN SECTIONS: 1. GENERAL 2. ROLES AND RESPONSIBILITIES 3. TEST PLAN 4. EQUIPMENT ENVIRONMENTAL TESTING
More informationIT Project Management Methodology. Project Scope Management Support Guide
NATIONAL INFORMATION TECHNOLOGY AUTHORITY - UGANDA IT Project Management Methodology Project Scope Management Support Guide Version 0.3 Version Date Author Change Description 0.1 23 rd Mar, 2013 Gerald
More informationAP1000 European 18. Human Factors Engineering Design Control Document
18.2 Human Factors Engineering Program Management The purpose of this section is to describe the goals of the AP1000 human factors engineering program, the technical program to accomplish these goals,
More informationATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES
1. ROLE DEFINITIONS ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES The purpose of this section is to distinguish among the roles interacting with the SPM obtained through
More informationSCOPE MANAGEMENT PLAN <PROJECT NAME>
SCOPE MANAGEMENT PLAN TEMPLATE This Project Scope Management Plan Template is free for you to copy and use on your project and within your organization. We hope that you find this template useful and welcome
More informationA Guide To The Project Management Body of Knowledge (PMBOK) Significant Changes from the 3 rd edition to the 4 th edition
A Guide To The Project Body of Knowledge (PMBOK) Significant Changes from the 3 rd edition to the 4 th edition Major Changes The adoption of the verb-noun format for process names Amplification as to Enterprise
More informationSystems Development Life Cycle (SDLC)
DEPARTMENT OF BUDGET & MANAGEMENT (SDLC) Volume 1 Introduction to the SDLC August 2006 Table of Contents Introduction... 3 Overview... 4 Page 2 of 17 INTRODUCTION 1.0 STRUCTURE The SDLC Manual consists
More informationExhibit G Project Management Plan, Implementation Schedule, and Cutover Plan
Exhibit G - Project Management Plan, Implementation Schedule, and Cutover Plan Exhibit G Project Management Plan, Implementation Schedule, and Cutover Plan G-1 Exhibit G - Project Management Plan, Implementation
More informationENOVIA Aerospace and Defense Accelerator for Program Management
ENOVIA Aerospace and Defense Accelerator for Program Management Through project pipeline dashboards, ENOVIA Aerospace and Defense Accelerator for Program Management provides real-time visibility into a
More information<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
More informationSuperseded by T MU AM 04001 PL v2.0
Plan T MU AM 04001 PL TfNSW Configuration Management Plan Important Warning This document is one of a set of standards developed solely and specifically for use on the rail network owned or managed by
More informationSystem Requirements Specification (SRS) (Subsystem and Version #)
of the (Subsystem and Version #) () (Document Revision Number) Contract (No.) Task (No.) GSA Contract (No.) Prepared for: The United States Department of Agriculture Food & Nutrition Service (FNS)/ Information
More informationPositive Train Control (PTC) Program Management Plan
Positive Train Control (PTC) Program Management Plan Proposed Framework This document is considered an uncontrolled copy unless it is viewed online in the organization s Program Management Information
More informationMinnesota Health Insurance Exchange (MNHIX)
Minnesota Health Insurance Exchange (MNHIX) 1.2 Plan September 21st, 2012 Version: FINAL v.1.0 11/9/2012 2:58 PM Page 1 of 87 T A B L E O F C O N T E N T S 1 Introduction to the Plan... 12 2 Integration
More informationPHASE 5: DESIGN PHASE
PHASE 5: DESIGN PHASE During the Design Phase, the system is designed to satisfy the requirements identified in the previous phases. The requirements identified in the Requirements Analysis Phase are transformed
More informationIT Project: System Implementation Project Template Description
2929 Campus Drive Suite 250 IT Project: System Implementation Project Template Description Table of Contents Introduction... 2 Project Phases... 3 Initiation & Requirements Gathering Milestone... 3 Initiation
More informationProject Risk Management: IV&V as Insurance for Project Success
Project Risk Management: IV&V as Insurance for Project Success Introduction Software development projects can be expensive and risky: Ever more complex mission-critical requirements lead to increasingly
More information<PROJECT NAME> PROJECT MANAGEMENT PLAN
PROJECT MANAGEMENT PLAN Version VERSION HISTORY [Provide information on how the development and distribution of the Project Management Plan was controlled and tracked.
More informationINDEPENDENT VERIFICATION AND VALIDATION OF EMBEDDED SOFTWARE
PREFERRED RELIABILITY PRACTICES PRACTICE NO. PD-ED-1228 PAGE 1 OF 6 INDEPENDENT VERIFICATION AND VALIDATION OF EMBEDDED SOFTWARE Practice: To produce high quality, reliable software, use Independent Verification
More informationSTATEMENT OF WORK FOR DESIGN, FABRICATION, INTEGRATION AND TESTING OF THE TELESCOPE STRUCTURE SYSTEM TMT.STR.MGT.12.001.REL01
STATEMENT OF WORK FOR DESIGN, FABRICATION, INTEGRATION AND TESTING OF THE TELESCOPE STRUCTURE SYSTEM TMT.STR.MGT.12.001.REL01 27 July, 2012 TMT.STR.TEC.12.001.DRF01 Page 2 of 13 Table of Contents 1. INTRODUCTION
More informationSAFETY AND SECURITY MANAGEMENT PLAN LIGHT RAIL TRANSIT BUILD-OUT PHASE II PROJECT
SAFETY AND SECURITY MANAGEMENT PLAN LIGHT RAIL TRANSIT BUILD-OUT PHASE II PROJECT Prepared By: July, 2009 Final Revision 4 Safety and Security Management Plan Revision History As of July 2009 Revision
More informationAppeals Case Management System Project. Scope Management Plan. November 20, 2014
Appeals Case Management System Project Version 1.0 Health and Human Services Agency, Office of Systems Integration Template Revision History REVISION HISTORY REVISION # DATE OF RELEASE OWNER SUMMARY OF
More informationProgram/Project Management Series Work Breakdown Structure Reference Guide
Program/Project Management Series Work Breakdown Structure Reference Guide National Aeronautics and Space Administration May 1994 2 Work Breakdown Structure Reference Guide May 1994 Table of Contents Chapter
More informationCONTRACT-BASED PROGRAM MANAGER OBJECTIVE
CONTRACT-BASED PROGRAM MANAGER OBJECTIVE Successful execution of contract-based programs means managing volumes of information to efficiently meet all contractual obligations. Tracking, reporting and communicating
More informationClinical Risk Management: Agile Development Implementation Guidance
Document filename: Directorate / Programme Document Reference NPFIT-FNT-TO-TOCLNSA-1306.02 CRM Agile Development Implementation Guidance v1.0 Solution Design Standards and Assurance Project Clinical Risk
More information5 FAH-5 H-520 LIFE CYCLE MANAGEMENT
5 FAH-5 H-520 LIFE CYCLE MANAGEMENT (CT:ITS-5; 02-05-2013) (Office of Origin: (IRM/BMP/SPO/PM) 5 FAH-5 H-521 CONFIGURATION MANAGEMENT REQUIREMENTS Configuration management (CM) is a function deployed throughout
More informationApplication Functional Safety IEC 61511
Application Functional Safety IEC 61511 Introduction Functional safety must be an integral part of the project execution if we shall succeed to make safe application program We can t test and audit safety
More informationSoftware Quality Assurance Plan
For Database Applications Document ID: Version: 2.1a Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 54 Copyright 2000-2006 Digital Publications LLC.
More informationDeveloping Work Breakdown Structures
Developing Work Breakdown Structures International Cost Estimating & Analysis Association June 2014 Neil F. Albert MCR, LLC nalbert@mcri.com 703-506-4600 2014 MCR, LLC Distribution prohibited without express
More informationSOFTWARE DEVELOPMENT AND DOCUMENTATION
DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. NOT MEASUREMENT SENSITIVE MIL-STD-498 5 December 1994 (PDF version) Superseding DOD-STD-2167A 29 February 1988 DOD-STD-7935A
More informationEarned Value Management System (EVMS) Manual. System Description and Implementing Procedures
Manual System Description and Implementing Procedures Manual System Description and Implementing Procedures Contact Information This document is maintained, updated, and formally revised electronically
More informationDATA ITEM DESCRIPTION
DATA ITEM DESCRIPTION Form Approved OMB NO.0704-0188 Public reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions,
More informationAn Introduction to the ECSS Software Standards
An Introduction to the ECSS Software Standards Abstract This introduces the background, context, and rationale for the creation of the ECSS standards system presented in this course. Addresses the concept
More informationGENCO Systems Inc. 3900 Germantown Road, Suite 300, Fairfax, VA 22030, Phone 703-934-4690
GENCO Systems Inc. Response to FTA s Project Management Oversight Solicitation GENCO SYSTEMS is an 8(a) Business Development [8(a)BD] and Small Disadvantaged Business (SDB) certified by the U.S. Small
More informationPHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
More informationPURCHASE ORDER ATTACHMENT Q-202 SOFTWARE QUALITY SUBCONTRACTOR REQUIREMENTS TASK DESCRIPTIONS - PURCHASE CATEGORY "B"
PURCHASE ORDER ATTACHMENT Q-202 SOFTWARE QUALITY SUBCONTRACTOR REQUIREMENTS TASK DESCRIPTIONS - PURCHASE CATEGORY "B" 1 SOFTWARE QUALITY PROGRAM. This attachment establishes the software quality requirements
More informationSpace engineering. System engineering. ECSS-E-10 C Draft 1
Space engineering System engineering This ECSS document is a draft standard distributed for Public Review. It is therefore subject to change without any notice and may not be referred to as an ECSS Standard
More informationPHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The Planning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
More informationNUMBER: 12.PM-004 RESPONSIBILITY: Office of Project Support Services REVISION: 4 APPROVED BY: TITLE SUBJECT: Head, Office of Project Support Services
SUBJECT: FERMI RESEARCH ALLIANCE PROCEDURES PROJECT MANAGEMENT NUMBER: 12.PM-004 RESPONSIBILITY: Office of Project Support Services REVISION: 4 APPROVED BY: TITLE Head, Office of Project Support Services
More informationSECTION 4 TESTING & QUALITY CONTROL
Page 1 SECTION 4 TESTING & QUALITY CONTROL TESTING METHODOLOGY & THE TESTING LIFECYCLE The stages of the Testing Life Cycle are: Requirements Analysis, Planning, Test Case Development, Test Environment
More informationFederal Aviation Administration Standard Work Breakdown Structure (WBS) Version 3.1
Federal Aviation Administration Standard Work Breakdown Structure (WBS) Version 3.1 July, 2003 Page Intentionally Left Blank INTRODUCTION This Federal Aviation Administration (FAA) Standard Work Breakdown
More informationVDOT GOVERNANCE DOCUMENT
VDOT GOVERNANCE DOCUMENT Minimum Requirements for Quality Assurance and Quality Control on Design Build and Public-Private Transportation Act Projects Location and Design Division Alternate Project Delivery
More information074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements
Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality
More informationTASPO-ATS-L System Test Plan
TASPO-ATS-L System Test Plan Automated Targeting System-Land ATS-L_(WR_1941)_STP_1.1 Document Number: ATS-L_(WR_1941)_STP_1.1 October 6, 2011 For Official Use Only - 42414 - TASPO-ATS-L System Test Plan
More informationProgram Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
More information1.1 Identification This is the Subcontractor Management Plan, document number XYZ035, for the SYSTEM Z project.
A Sample contractor Management Plan 1.0 INTRODUCTION 1.1 Identification This is the contractor Management Plan, document number YZ035, for the SYSTEM Z project. 1.2 Purpose The contractor Management Plan
More informationITS Projects Systems Engineering Process Compliance Checklist
ITS Projects Systems Engineering Process Compliance Checklist FHWA Final Rule (23 CFR 940) This checklist is to be completed by the MDOT or LPA Project Management Staff. Please refer to the accompanying
More informationSystem Engineering Plan
Project Documentation Document SPEC-0064 Revision A System Engineering Plan Rob Hubbard, Jeremy Wagner, Larry Daggert, Larry Stepp, Christoph Keller Systems Engineering / Project Management 5 October 2006
More informationService Support. 2005 Kasse Initiatives, LLC. ITIL Configuration Management - 1. version 2.0
Service Support Configuration Management ITIL Configuration Management - 1 Goals of Configuration Management The goals of Configuration Management are to: Account for all the IT assets and configurations
More informationISO 9001: 2008 Construction Quality Management System Sample - Selected pages (not a complete plan)
ISO 9001: 2008 Construction Quality Management System Sample - Selected pages (not a complete plan) Part 1: Project-Specific Quality Plan Part 2: Company Quality Manual Part 3: Submittal Forms Part 4:
More informationCapacity Plan. Template. Version X.x October 11, 2012
Template Version X.x October 11, 2012 This is an integral part of infrastructure and deployment planning. It supports the goal of optimum provisioning of resources and services by aligning them to business
More informationASSEMBLY OF FIRST NATIONS
ASSEMBLY OF FIRST NATIONS REQUEST FOR PROPOSAL CONTRACTOR FOR MEETING REGISTRATION This is a Request for Proposal only. The AFN is not obligated to accept any proposal or to proceed further. The AFN may
More informationThe Project Management Plan will be used to guide, communicate and coordinate project efforts.
F.1 General Implementation Contractor Deliverables include critical system planning and development components. Sufficient deliverables have been identified at key steps in the project to guide the project
More informationNODIS Library Program Formulation(7000s) Search
NODIS Library Program Formulation(7000s) Search NASA Procedural Requirements This Document Is Uncontrolled When Printed. Check the NASA Online Directives Information System (NODIS) Library to verify that
More informationCovance Construction Management Staffing Plan Chandler, Arizona
INTRODUCTION: This Construction Management (CM) Staffing Plan has been prepared for Covance to identify the critical organizational structure necessary to successfully complete the Chandler project according
More informationAppendix 2-A. Application and System Development Requirements
Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility
More informationDATA REQUIREMENTS DESCRIPTION (DRD)
DATA REQUIREMENTS DESCRIPTION (DRD) 1. DPD NO.: XXX ISSUE: Draft 2. DRD NO.: STD/EDAL 3. DATA TYPE: 3 4. DATE REVISED: 5. PAGE: 1/3 6. TITLE: Engineering Drawings and Associated Lists 7. DESCRIPTION/USE:
More informationSystem Development Life Cycle Guide
TEXAS DEPARTMENT OF INFORMATION RESOURCES System Development Life Cycle Guide Version 1.1 30 MAY 2008 Version History This and other Framework Extension tools are available on Framework Web site. Release
More informationasuresign Aero (NATEP Grant MA005)
asuresign Aero (NATEP Grant MA005) WP2 Workshop: Identification of Needs for Tool Support in Meeting Aircraft Avionics Systems, Hardware & Software Certification Standards Dr Chris Harper Systems & Safety
More informationVAIL-Plant Asset Integrity Management System. Software Development Process
VAIL-Plant Asset Integrity Management System Software Development Process Document Number: VAIL/SDP/2008/008 Engineering For a Safer World P u b l i c Approved by : Ijaz Ul Karim Rao Revision: 0 Page:2-of-15
More informationFDA Software Validation-Answers to the Top Five Software Validation Questions
Whitepaper FDA Software Validation-Answers to the Top Five Software Validation Questions Author: Penny Goss, Penny Goss Technical Solutions The FDA (Food and Drug Administration) and IEC (International
More informationYour Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.
INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing
More informationRequirements Traceability. Mirka Palo
Requirements Traceability Mirka Palo Seminar Report Department of Computer Science University of Helsinki 30 th October 2003 Table of Contents 1 INTRODUCTION... 1 2 DEFINITION... 1 3 REASONS FOR REQUIREMENTS
More informationProject Scope Management in PMBOK made easy
By Dr. TD Jainendrakumar The main objective of any project is to fulfill the scope of the project on time and within the budget. What is Project Scope? Scope refers to all the work involved in creating
More informationEnergy Design Resources Commissioning Plan Outline Template
IMPORTANT NOTICE: This sample document is provided for instructional purposes only. CCC is not rendering advice concerning any commission project or practices. This document is neither approved nor intended
More informationISA CERTIFIED AUTOMATION PROFESSIONAL (CAP ) CLASSIFICATION SYSTEM
ISA CERTIFIED AUTOMATION PROFESSIONAL (CAP ) CLASSIFICATION SYSTEM Domain I: Feasibility Study - identify, scope and justify the automation project Task 1: Define the preliminary scope through currently
More informationSCHEDULE 3. Milestones and Deliverables. Redacted Version
SCHEDULE 3 Milestones and Deliverables Redacted Version This Schedule 3 sets out the Service Provider s obligations in respect of the milestones and deliverables relating to the implementation and operation
More informationManag. Roles. Novemb. ber 20122
Information Technology Manag gement Framework Roles and Respo onsibilities Version 1.2 Novemb ber 20122 ITM Roles and Version History Version ed By Revision Date Approved By Approval Date Description of
More informationJOHN HART GENERATING STATION REPLACEMENT PROJECT. Schedule 9. Quality Management
JOHN HART GENERATING STATION REPLACEMENT PROJECT Schedule 9 Quality Management SCHEDULE 9 QUALITY MANAGEMENT TABLE OF CONTENTS 1. QUALITY MANAGEMENT SYSTEM... 1 1.1 Quality Management System...1 1.2 Project
More informationPROJECT SCOPE STATEMENT
PROJECT SCOPE STATEMENT Note: Any work not explicitly included in the Project Scope Statement is implicitly excluded from the project. Project Name: Prepared by: BI - IT Governance Amy Winkel Date: 12/20/2010
More informationTREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION
TREASURY INSPECTOR GENERAL FOR TAX ADMINISTRATION The Customer Account Data Engine 2 Systems Development Guidelines; However, Process Improvements Are Needed to Address Inconsistencies September 30, Year
More informationIntroduction to the ITS Project Management Methodology
Introduction to the ITS Project Management Methodology In September 1999 the Joint Legislative Committee on Performance Evaluation and Expenditure Review (PEER) produced a report entitled Major Computer
More informationChap 1. Software Quality Management
Chap 1. Software Quality Management Part 1.1 Quality Assurance and Standards Part 1.2 Software Review and Inspection Part 1.3 Software Measurement and Metrics 1 Part 1.1 Quality Assurance and Standards
More informationSECTION 01 32 00 - PROJECT PLANNING AND SCHEDULING PART 1: GENERAL 1.1 DEFINITIONS
SECTION 01 32 00 - PROJECT PLANNING AND SCHEDULING PART 1: GENERAL 1.1 DEFINITIONS A. The term Baseline Schedule, as used throughout the contract documents, shall refer to a fixed projection of the project
More informationALS Configuration Management Plan. Nuclear Safety Related
Westinghouse Non-Proprietary Class 3 Advanced Logic System 6002-00002-NP, Rev. 10 Function Author Nuclear Safety Related July 2014 APPROVALS Name and Signature Anthony C. Pagano* Integrated Process Lead,
More informationTechnical Baseline Management
Technical Baseline Management September 30, 2003 Pat Hascall LAT System Engineering 1 Technical Baseline Management We are required to manage the configuration of our technical baseline What is configuration
More informationESPC Life of Contract (LOC) Plan:
ESPC Life of Contract (LOC) Plan: Documents Management and Checklist for Savings Performance Contracts (ESPC) (Contract Number), (Date Amended), (Contributors) (SITE) ENERGY SAVINGS PERFORMANCE CONTRACT
More informationSoftware Test Plan (STP) Template
(STP) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project. This
More informationSpace product assurance
ECSS-Q-ST-80C Space product assurance Software product assurance ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS
More informationPOLICY AND PROCEDURES OFFICE OF STRATEGIC PROGRAMS. CDER Master Data Management. Table of Contents
POLICY AND PROCEDURES OFFICE OF STRATEGIC PROGRAMS CDER Master Data Management Table of Contents PURPOSE...1 BACKGROUND...1 POLICIES...2 RESPONSIBILITIES...2 PROCEDURES...4 REFERENCES...5 DEFINITIONS...5
More information