Scribd Logo
Upload

Welcome to Scribd!

  • Managing Ship Repair Information For Project Control

    Uploaded by

    Mohamed Fakhr El Din
    10 views22 pages
    The document discusses management of ship repair projects. It covers the nature of ship repair work, which involves initial planning but is subject to variation as emergent work is discovered. It also discusses contract preparation and control, including estimating work, identifying subcontractors, and monitoring progress and costs. Finally, it addresses the need for management information systems to track the rapidly changing tasks and status within repair contracts.

    Original Description:

    Original Title

    Managing Ship Repair Information for Project Control

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses management of ship repair projects. It covers the nature of ship repair work, which involves initial planning but is subject to variation as emergent work is discovered. It also discusses contract preparation and control, including estimating work, identifying subcontractors, and monitoring progress and costs. Finally, it addresses the need for management information systems to track the rapidly changing tasks and status within repair contracts.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    10 views22 pages

    Managing Ship Repair Information For Project Control

    Uploaded by

    Mohamed Fakhr El Din
    The document discusses management of ship repair projects. It covers the nature of ship repair work, which involves initial planning but is subject to variation as emergent work is discovered. It also discusses contract preparation and control, including estimating work, identifying subcontractors, and monitoring progress and costs. Finally, it addresses the need for management information systems to track the rapidly changing tasks and status within repair contracts.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 22

    Management of Ship Repair

    Information for Project Control

    Professor George Bruce

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Content
    • The Nature of Shiprepair
    • Contract Preparation
    • Contract Control
    • Information Systems

    • MIS in Ship Repair

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Nature of Shiprepair
    • Basic Initial Planning
    • Subject to variation
    • Emerging Work
    • Cancellations

    • May require Re-planning

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Ship Building & Ship Repair
    New Construction Repair & Conversion
    • design driven • existing condition
    • known workload • unknown workload
    • limited changes • emergent work
    • standard tasks • few standards
    • fixed price • variable price

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Contract Phase Outputs
    • Marketing - good enquiries
    • Tendering - realistic estimates
    • Negotiation - contracts
    • Planning - acceptable costs & schedules
    • Purchasing - correct deliveries
    • Production - control of operations
    • Invoicing - agreed costs prior to sailing

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Contract Preparation

    • Set Timescale and Delivery Date


    • Estimate Man-hours
    • Identify Sub-contract needs
    • Use Tariffs where Feasible
    • Identify Uncertain Areas

    • Review Shipyard Forward Workload

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Contract Control

    • Monitor Progress and Spending


    • Identify New Resource Requirements
    • Review New Contracts
    • Review Cancellations

    • Maintain the Delivery Date

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Management Information Systems

    • Built on a Database
    – Identify All Tasks
    – Manage the Task Status at all times

    • Not Accounting – History


    • Not Planning – Variable

    • Need is for a New Approach


    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com
    MIS in Shiprepair

    • Uses a Database
    • Manages Tasks within Contracts
    • Flexible in Operation
    • Follows Contract Life-cycle

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Shiprepair Requirements (1)

    • Management of Client Base


    • Management of Enquiries
    • Estimating
    • Production Planning
    • Purchasing

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Dynamic Trading Community

    Customer 1 Vessel 1

    Person 1
    Person 2

    Vessel 2
    Customer 2

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Shiprepair Requirements (2)

    • Progress Monitoring
    • Labour Cost Control
    • Invoicing

    • Keeping an up to date picture of a rapidly


    changing contract situation

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    The EPIC system

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    The EPIC system

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Hierarchical Data Model
    Customer 1 Customer 2

    Person 1 Person …
    Person 2 Person …
    Person … Vessel …
    Vessel 1 Vessel …
    Vessel … Vessel …

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Poor Interfaces (1)

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Poor Interfaces (2)

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    ‘Waterfall’ Development
    Requirement

    Analysis

    Design

    Development

    Testing

    duration : N months
    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com
    ‘Waterfall’ Problems
    what the user
    asked for how the
    analysts saw it

    how the system


    was designed
    as the programmer
    wrote it

    what the user


    really wanted how it actually
    works

    with thanks to Dan Tasker

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com


    Iterative Development

    Development
    Iteration

    Acceptance
    Testing

    duration : 2-8 weeks


    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com
    Open Source
    • a great enabler
    • cheap, reliable software
    • example:
    – HSqlDb – portable database
    – Hibernate – database access
    – Avalon – server application
    – Alt-Rmi – client / server communication
    – Eclipse RCP – client application
    – SWT – user interface
    – POI – Microsoft document generation
    – log4J, dom4j, apache…
    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com
    Q&A

    George Bruce

    9 November 2005 Ship Repair & Conversion 2005 mike.evans@incremental.eu.com

    You might also like