Company for Urban Innovative Transport (CUIT) 19/12/2007 Request for proposal.

Slides:



Advertisements
Similar presentations
Radiopharmaceutical Production
Advertisements

WP4 – Task 4.4 LCA Activities
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
ISO 9001 : 2000.
EPSON STAMPING ISO REV 1 2/10/2000.
Contractor Safety Management
The ISO 9002 Quality Assurance Management System
Stepan Potiyenko ISS Sr.SW Developer.
Overview Lesson 10,11 - Software Quality Assurance
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
WHS Management Plans.
Enterprise Architecture
Project Management Lecture 5+6 MS Saba Sahar.
© Joseph F Iaquinto, PE May 14, © Joseph F Iaquinto, PE May 14, 2012 EAI / SOA Composite System A System Engineering Approach.
Web Development Process Description
PMP® Exam Preparation Course
Introduction to Software Quality Assurance (SQA)
Copyright 2005 Welcome to The Great Lakes TL 9000 SIG TL 9000 Requirements Release 3.0 to Release 4.0 Differences Bob Clancy Vice President, BIZPHYX,
The Role of the Internal Auditor for Maintaining System Compliance and Promoting Continuous Improvement Wayne M. Uttke
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
CLEANROOM SOFTWARE ENGINEERING.
Commissioning of Fire Protection and Life Safety Systems Presented by: Charles Kilfoil Bechtel National Waste Treatment Plant Richland WA.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Workshop Mark Heggli Innovative Hydrology, Inc. Consultant to the World Bank Expert Real-time Hydrology Information Systems Module 6: Training, Operations.
Engineering System Design
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
IT Requirements Management Balancing Needs and Expectations.
1 FRENCH PROPOSAL FOR ESARR6 1 - BACKGROUND - 15/02/00 : Kick-off meeting, Presentation of the CAA/SRG input (SW01), Request from the chairman to comment.
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
13 Step Approach to Network Design Steps A Systems Approach 8Conduct a feasibility Study 8Prepare a plan 8Understand the current system 8Design.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
International Atomic Energy Agency Roles and responsibilities for development of disposal facilities Phil Metcalf Workshop on Strategy and Methodologies.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
1 Project Management C53PM Session 3 Russell Taylor Staff Work-base – 1 st Floor
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Software Quality Assurance. Software Quality Software quality is defined as the quality that ensures customer satisfaction by offering all the customer.
CABLING SYSTEM WARRANTY REGISTRATION. PURPOSE OF CABLING REGISTRATION.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Team-Based Development ISYS321 Managing the Information Systems Project.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
Ondřej Přibyl L3: System Development Life Cycle page 1 Lecture 3: System Development Life Cycle Doc.Ing. Ondřej Přibyl, Ph.D. Department of applied mathematics.
Quality Management: Mutually beneficial supplier relationships.
Software Quality Control and Quality Assurance: Introduction
PERSONAL SAFETY INTERLOCKS External EHS Expert Panel Workshop
ISO/IEC
CS4311 Spring 2011 Process Improvement Dr
TechStambha PMP Certification Training
IEEE Std 1074: Standard for Software Lifecycle
Development Projects / Analysis Projects / On-site Service Projects
Session II: System authority for ERTMS 4RP Trackside approval
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Chapter 3 Managing the Information Systems Project
CMMI – Staged Representation
Quality Management Systems – Requirements
ATO over ETCS Benoît BIENFAIT 10/2/2016.
Engineering Processes
Software Project Management
Joint WG on Guidance for an Integrated Transport and Storage Safety Case for Dual Purpose Casks TM TM to Produce Consolidated Drafts of the IAEA’s.
Project Management Process Groups
Project Management Chapter 11.
Engineering Processes
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
Radiopharmaceutical Production
Presentation transcript:

Company for Urban Innovative Transport (CUIT) 19/12/2007 Request for proposal

Presentation title - 01/01/ P 2 Table of content 1st topicCustomer requirements Page 3 2nd topic Project Management acceptance criteriaPage 4 3rd topic System analysis acceptance criteriaPage 5 4th topic System V&V and Test report acceptance criteriaPage 6

Presentation title - 01/01/ P 3 Autonomous Transportation Unit Request for proposal: Customer requirements - The CUIT company request for proposal of innovative autonomous transportation units for urban transport on demand. -The transportation system will integrate the pre-existing urban environment : road, crossing, signalling…. -In order to reduce urban integration works and for the shake of flexibility: -The route will be materialized by a closed guiding line painted on the road, that the Autonomous transportations units shall follows. -Specific areas will be materialised by discriminative shapes painted on road. Specific areas are : Station entry, depot entry, secondary routes, and turn back. -The transportation units will stop at each stations to make their transportation capacity at disposal of passengers. -If a passenger is detected, the transportation units will ensure a dwell time of 5 sec for passengers boarding then run to the next station -The transportation units will, at the next station, ensure 5 sec of dwell time for passenger detrainment. -If no transportation demand is detected at a station the Unit will not stay more then 3sec and than run to the next station -Because the transportation units are in an open environment their shall ensure non-collision of passengers or other units. - Secondary routes shall be followed in case of obstacle to maintain the station services in case of maintenance work. - the transport station unit will start from the depot at morning start-up, and will go back to the depot every 3 run for maintenance. -Station could be in turnback zones.

Presentation title - 01/01/ P 4 Autonomous Transportation Unit Request for proposal: Contract award -The competitors will be selected according to the following criteria -Ability to manage their development -Effectiveness of the system development process - use of a system vision -Handling of needs and product requirement -System specifications - and Design description - Provision of relevant proof of compliance to requirements -Cost of the selected solution -Operational Performance of the selected solution -Trip time -Reliability of train precise stopping -Station service availability -Robustness -Safety

Presentation title - 01/01/ P 5 Autonomous Transportation Unit Request for proposal: Deliverables Competitors will provide the following deliverables as objective evidences of the selection criteria satisfaction: A project management plan by Jan A system design documentation that shall enclose at least the following : System concept System specification System design description A System V&V and Test report A technical solution prototype based on the standard Mindstroms technology.

Presentation title - 01/01/ P 6 Autonomous Transportation Unit Request for proposal: Test and commissioning The technical solution commissioning procedure will enclose the following operational scenarios: Manufacturability: The autonomous Transportation System design will have to demonstrate its ability to manufacture and maintenance thanks to the shortest assembling time of components. The Mean time to repair shall not exceed 1,5 minute (which is the maximum assembling and disassembling time of the entire unit) Train trip : the Autonomous Transportation System will have to perform a train trips without station service, to demonstrate their ability to complete runs allows a closed route at average speed of 4 cm/sec. Obstacle detection : the Autonomous Transportation System will have to perform trips with obstacle detection in order to demonstrate their ability to integrate the urban operational context. In case of maintenance work on the road secondary routes shall be followed. Station service : the Autonomous Transportation System will have to perform train trips with station services, to demonstrate their ability to provide transportation capability and passenger exchanges in a reliable and scheduled manner. The waiting time shall not exceed 25 sec in peak off hours and 35 sec in peak hours Carrousel: The 4 competitors solutions will be gathered in a Transportation unit fleet an will operate in a carrousel mode to demonstrate their ability to interoperate. Any failure will give rise to a retrieval of the Transportation unit from the carrousel.

Presentation title - 01/01/ P 7 Table of content 1st topicCustomer requirementsPage 3 2nd topic Project Management acceptance criteria Page 4 3rd topic System analysis acceptance criteriaPage 5 4th topic System V&V and Test report acceptance criteriaPage 6

Presentation title - 01/01/ P 8 Project Management acceptance criteria Evidence that the project is managed: Evidence that the project is planned Evidence that project Purpose and Objective are defined Evidence that that project scope of work is defined (Activities and work-products) Evidence that process is defined Evidence that resources are planned, roles and responsibilities are assigned Evidence that project schedule is established Evidence that the project is monitored and controlled Evidence that the project progress is monitored against plan Evidence that correctives actions are planned and tracked to closure

Presentation title - 01/01/ P 9 Table of content 1st topicCustomer requirementsPage 3 2nd topic Project Management acceptance criteriaPage 4 3rd topic System analysis acceptance criteria Page 5 4th topic System V&V and Test report acceptance criteriaPage 6

Presentation title - 01/01/ P 10 System analysis acceptance criteria Evidence that the system analysis investigate the system view points and satisfy the Consistency rules at preliminary, pre-final and final project phases: System concept (preliminary design) Evidence that the operational context has been defined Evidence that the needs are identified in those contexts Evidence that the main functions and functional requirements are defined Evidence that the main architecture principles are defined with their associated requirements Evidence that the 3 visions are mutually consistent System development(pre-final design) Evidence that the operational statements follow the canonical form Evidence that the functional statements follow the canonical form Evidence that the constructional statements follow the canonical form Evidence that Refinement consistency rules are satisfied Evidence that the viewpoints are mutually consistent System design description(final design) Evidence that the Selected solution is described and performance stated Evidence that the integration sequence is described Evidence that the software is documented

Presentation title - 01/01/ P 11 Table of content 1st topicCustomer requirementsPage 3 2nd topic Project Management acceptance criteriaPage 4 3rd topic System analysis acceptance criteriaPage 5 4th topic System V&V and Test report acceptance criteria Page 6

Presentation title - 01/01/ P 12 System Verification &Validation and Test report acceptance criteria Evidence that the system design has been subject to Verification and validation: Test cases are planned and specified: Evidence that test cases as been specified and documented Test reports: Evidence that the test cases has been performed Needs validation and Requirement are covered by a test case.