Professional Documents
Culture Documents
Software requirements
Diesel Engine Management Software
DTTT (MB) Page 1
DE Management software
Software Requirement
Platform : Windows 2003 or later version
Web Server : IIS 6.0 or later version
Web Technology : Visual Studio 2005 (ASP.Net 2.0)
.NET Framework : .NET Framework 2.0
Database : Microsoft SQL Server 2005
COM Components : Microsoft Excel Application
Application Users ‐ Logging in
1. The hierarchy for logging in the application will be as follows:
(a) Administrator. These users (in DTTT) can have special permissions
like adding or modifying data on all the administrative modules, data
modifications on Trial Information and generating trend analysis graphical
reports.
(b) General User 1 – DTTT. Adding data recorded during the trials and
viewing the equipment data, parameter trends, and LO reports. No editing
privileges will be given.
(b) General User 2 – HQWNC/Ops authorities. These users can only
view the Trial Information and generating trend analysis graphical reports for
all ships/limited class of ships
(c) General User 3 – Ships. These users can only view the Trial Information
and generating trend analysis graphical reports for a particular ship
(d) General user 4 – FMU. User can only upload information on the LO and
coolants on the master database. He will have only viewing privileges for all
data
Input required
2. Following input will be input into the software:
DTTT (MB) Page 2
DE Management software
(a) By ships/trial Units.
(i) Enter equipment information (ships/trial Unit) ‐ Class of ship, Ship,
Engine, Placement of engine, Engine ser no, Date installed, Running hrs
since installation, Placement on ship, Running hrs since last MOH, Oil
used, Coolant used etc.
(ii) Request for trials (ships only) – Requesting for a particular type of
trial on selection of an equipment and a type of trial and actions taken as
directed by HQWNC.
(b) By trial teams.
(i) Enter trial reports in the software in the log created by the ship
after approval of HQWNC.
(ii) Enter parameters in the parameter database
(c) By HQWNC/ND(MB). Comments/ Approval/ defect rectification
undertaken post trials conducted by trial teams
(d) Uploading through external database from firm for LO and Coolants
This module will allow an external user to fill in information in a customized
excel/custom‐made database that could be used to update the main database
server in FMU(MB)/DTTT(MB) .
Software Process
3. Databases. Following databases will be required:
(a) Users. All users names, rank and Admin privileges for all menus which will
be visible/not‐visible will be defined Administrator will have the flexibility to
add/delete/edit the data.
(b) Engine database – Class of ship, Ship, Engine, Placement of engine,
Engine ser no, Date installed, Running hrs since installation, Placement on ship,
DTTT (MB) Page 3
DE Management software
Running hrs since last MOH, Oil used, Coolant used etc. Administrator will have
the flexibility to add/delete/edit the fields in the database.
(c) Trial database – Occasion or type of trial to be undertaken eg‐ Post
engine change, MOH, TOH, Life extension trial, Defect diagnosis trials, PRT, PST
will be entered in the database.
(d) POL database – All fields for entering POL reports will be available as per
formats enclosed. Fields for comments by Trial Units like MTU(MB), GTTT(MB),
DTTT(MB) and MSETT and corrective actions taken can by ships will also be
available. Administrator will have the flexibility to add/delete/edit the fields in
the database.
(e) Parameter trends – Separate databases based on type of engines/class of
ships will be created and facility will exist to display the data graphically
ship/class of ship wise. Administrator will have the flexibility to add/delete/edit
the fields in the databases or complete tables itself.
4. The tables, hierarchy and database structure could be expanded further based
on the information to be displayed in the various menus and could be decided during
the developmental stage.
5. Management modules
(a) Managing users. A list of users in Indian navy – various units, HQWNC
and ships will be created by the administrator. The permissions to change the
name for the users will rest with the administrator at DTTT(MB).
(b) Ship Module. The Ship Module would enable the ship to
undertake the following:-
DTTT should be able to load data sent by the ship in excel format into the
database. Care should be taken so that similar data if uploaded twice
should not create duplicate records. DTTT should be able to create new
DTTT (MB) Page 4
DE Management software
users could log in to the database and view the various trends and query for
reports based on selection of a ship/equipment.
Software Output
6. Reports ‐ Used for the following:
(a) Generating the ops status of various engines, ships refit status etc
(b) No of engines/type of engines in the Command
(c) Displaying trial reports of various ships, directives of HQWNC and actions
taken by ND(MB)/ship staff
(d) Displaying parameter trends for different type of engines based on
selection of class of ship, ship or engine model
(e) Displaying the history of the engine which is fitted in various classes of
ships eg‐ Engines which failed/completed service life and fitted in other ships
post overhaul.
(f) Trending data for lub oils and coolants
Menu bar – for software
7. The home page is the landing page when the users access the DTTT application.
The users post logging in as general users 1‐4/administrator will have the following
buttons on the menu:
(a) Engine information – Submenu for input of engine details, trial
parameters logging and importing data for oil and coolant reports (basic,
advanced and coolant reports). Reports forwarded by the RC firm will be
uploaded on the server by a user at FMU.
(b) Trials – Submenu for request for trial by ships and current status of trial.
Single screen indicating the comments of HQWNC / reports of trial teams and
corrective action by ND(MB)/ships as per the process flow created by the user
will be created. Administrator/general user 1 will reserve the right to correct
the process flow if required.
(c) Parameter reports and trending – Facility for displaying/trending
parameters for all users based on users choice of x and y axis or x, y and z axis.
DTTT (MB) Page 6
DE Management software
Submenus for the various reports indicated in para 6 above.
(d) LO and coolant analysis reports – Submenus for basic, advanced,
ferrography and coolant reports. Facility for displaying/trending LO basic,
advanced and coolant reports for all users based on selection of ship and
equipment.
Requirements for development, execution, training and AMC
1. Intellectual Property Rights of the system would be with the Indian Navy.
The firm would be required to supply the source code entirely.
3. The system should validate entries during data entry and provide online
exception reports.
DTTT (MB) Page 7