REQUEST FOR PROPOSAL

INDIAN NAVAL SHIP MAINTENANCE AUTHORITY

SHAHID BHAGAT SINGH ROAD, MUMBAI - 23

INVITATION OF BIDS FOR ‘DESIGN AND DEVELOPMENT OF

COMPREHENSIVE MAINTENANCE MANAGEMENT SYSTEM AT
INDIAN NAVAL SHIP MAINTENANCE AUTHORITY’

Request for Proposal (RFP) No ……..

Dated-………………

1. Online bids are invited electronically on the GeM Portal for supply of items
listed in Part II of this RFP.

2. The address and contact numbers for sending Bids or seeking clarifications
regarding this RFP are given below: -

(a) Bids/queries to be addressed to The Director

{for Joint Director (Sys & Proj}
(b) Postal address for sending the Bids Indian Naval Ship Maintenance
Authority
FMU Building
Naval Dockyard
Mumbai - 400 023
(c) Contact Person Lt Cdr Shubham Kumar, System
Controller (NUMARC)
(d) Telephone numbers of the contact 022-2275 2210,
personnel 08374299103
(e) E-mail ids of contact person [email protected]
(f) Fax number 022-22751971

3. This RFP is divided into five Parts as follows: -

(a) Part I – Contains General Information and Instructions for the Bidders
about the RFP such as the time, place of submission and opening of tenders,
Validity period of tenders, etc.

(b) Part II – Contains essential details of the items/services required, such

as the Schedule of Requirements (SOR), Technical Specifications, Delivery
Period, Mode of Delivery and Consignee details

(c) Part III – Contains Standard Conditions of RFP, which will form part of
the Contract with the successful Bidder

(d) Part IV – Contains Special Conditions applicable to this RFP and which
will also form part of the contract with the successful Bidder

Indian Naval Ship Maintenance Authority Page 1

 (e) Part V – Contains Evaluation Criteria and Format for Price Bids

4. List of Appendices and Annexures to RFP is as follows: -

Ser Annexure Part Para Description

(a) A Schedule of Requirement and Technical
Specifications with 05 Annexures: -

Annexure ‘I’: Project Architecture

Annexure ‘II’: CMMS Architecture
Annexure ‘III’: Analytics Requirement
Annexure ‘IV’: Document & Deliverables
Annexure ‘V’: InfoSec Measures
(b) B Technical Compliance Matrix
(c) C Product Support Scope of Work
(d) D Non- Disclosure Agreement
(e) E Certificate of Malicious Code
(f) F Price Bid Format
(g) G Vendor Evaluation Criteria
(h) H Bid Security Certificate

5. Pre-Bid Vendor Conference. A pre-bid conference will be conducted at

INSMA office on ………………… at ………. to discuss in detail issues and clarify
ambiguities, if any, pertaining to the tender, specifications and any other queries
sought by vendors. In order to obtain the requisite security clearance, the vendors are
to forward the following information with regard to the participants (maximum 02
representatives per vendor) by email at least one day prior to the date of Pre-Bid
Conference. Physical attendance of the firm reps for pre-bid conference will be
preferred for Firms selection for Technical. In case of inability to physically attend the
pre-bid meeting, the respective bidder must inform at-least one day in advance.
Provisions for virtual conferencing (VC) will be provided for bidders who have informed
INSMA. The queries of vendors failing to participate in the pre-bid meeting might
remain unaddressed. In view of the same, all bidders are encouraged to participate in
the pre-bid meeting. Various details required for security clearance is as follows: -

(a) Name, Age, Address and Contact Numbers

(b) Valid ID proof/ Aadhaar (Physical Copy)
(c) Authority letter of the firm authorising the rep to attend the pre-bid
conference.

6. This RFP is being issued with no financial commitment and the BUYER
reserves the right to change or vary any part thereof at any stage. BUYER also
reserves the right to withdraw the RFP, should it become necessary at any stage.

(Shubham Kumar)
Lt Commander
System Controller (NUMARC)

Indian Naval Ship Maintenance Authority Page 2

 Part I – General Information

1. Last date and time for depositing the Bids. 1100 h on ……………...

2. Manner of depositing the Bids. The bidders are required to submit soft
copies of their bids electronically on the GeM Portal, using valid Digital Signature
Certificates. More information useful for submitting online bids on the CPP
Portal may be obtained at: https://gem.gov.in

3. Time and date for opening of Bids. Time and date for opening of bids is
1500 h on ………… If due to any exigency, the due date for opening of the Bids is
declared a closed holiday, the Bids will be opened on the next working day at the
same time or on any other day/time, as intimated by the Buyer.

4. Place of opening of the Bids. INSMA OFFICE, FMU FIRST FLOOR.

5. Two-Bid System. Yes

6. Forwarding of Bids. Bids should be forwarded by the bidders under their

original memo/letter pad, furnishing details like TIN number, VAT/CST number, bank
address with EFT account if applicable, etc. and complete postal & e-mail address of
their office. The ‘T’ bid should conform to the following: -

(a) EMD is to be enclosed.

(b) The firm should be in the business of providing IT software services and
IT Hardware.

(c) The firm must have a valid GST number and should possess requisite
registration.

(d) All the firms participating in the Tender must submit a list of their
owners/partners etc. along with their contact telephone numbers and a
Certificate of Undertaking to the effect that the firm is neither blacklisted by
any Government Department nor any criminal case is registered against the
firm. Submit duly completed compliance grids placed at Appendix ‘B’.

Note:- Firm is to submit documentary proof of eligibility criteria viz. photocopies

of registration certificates, proof of annual turnover, copies of orders or any other
documentary evidence are to be provided. In absence of these documents, the tender
will not be entertained.

7. Clarification Regarding Contents of the RFP. A Pre-bid Conference is

planned one week after the date of issue of RFP. Prospective bidders requiring
clarifications regarding the contents of the bidding documents shall notify to the Buyer
in writing prior this meeting. The clarifications to these queries would be given during
the aforesaid meeting. Copies of the queries and clarifications by the Buyer will be
sent to all prospective bidders who have received the bidding documents. No requests
for clarifications would be entertained after the Pre-bid Conference Meeting.

Indian Naval Ship Maintenance Authority Page 3

8. Modification and Withdrawal of Bids. A bidder may modify or withdraw his
bid after submission provided that the written notice of modification or withdrawal is
received by the Buyer prior to deadline prescribed for submission of bids. A withdrawal
notice may be sent by fax and email but it should be followed by a signed confirmation
copy to be sent by post and such signed confirmation should reach the Buyer at-least
one day prior to the deadline for submission of bids. No bid shall be modified after the
deadline for submission of bids. No bid may be withdrawn in the interval between the
deadline for submission of bids and expiration of the period of bid validity specified.
Withdrawal of a bid during this period will result in Bidder’s forfeiture of bid security
and the firm is required to furnish Bid Security Declaration as per Appendix ‘H’.

9. Clarification Regarding Contents of the Bids. During evaluation and

comparison of bids, the Buyer may, at its discretion, ask the bidder for clarification of
his bid. The request for clarification will be given on the GeM portal and no change in
prices or substance of the bid will be sought, offered or permitted. No post-bid
clarification on the initiative of the bidder will be entertained.

10. Rejection of Bids. Canvassing by the Bidder in any form, unsolicited letter
and post-tender correction may invoke summary rejection with forfeiture of EMD.
Conditional tenders will be rejected.

11. Unwillingness to Quote. Bidders unwilling to quote should ensure that

intimation to this effect reaches before the due date and time of opening of the Bid,
failing which the defaulting Bidder may be delisted for the given range of items as
mentioned in this RFP.

12. Validity of Bids. The Bids should remain valid till 180 days from the last
date of submission of Bids.

13. Earnest Money Deposit. Bidders are required to submit Earnest Money
Deposit (EMD) for a sum of ……………………………………..) along with their bids.
The EMD may be submitted in the form of an Account Payee Demand Draft, Fixed
Deposit Receipt, Banker's Cheque or Bank Guarantee from any of the public sector
banks or a private sector bank authorized to conduct government business as per
Form DPM-16 (Available in MoD website and can be provided on request) in favour
of PCDA NAVY Mumbai. EMD is to remain valid for a period of forty-five days beyond
the final bid validity period. EMD of the unsuccessful bidders will be returned to them
at the earliest after expiry of the final bid validity and latest on or before the 30th day
after the award of the contract. The Bid Security of the successful bidder would be
returned, without any interest whatsoever, after the receipt of Performance Security
from them as called for in the contract. EMD is not required to be submitted by those
Bidders who are registered with the Central Purchase Organization (e.g. DGS&D),
National Small Industries Corporation (NSIC) or any Department of MoD or MoD itself.
The EMD will be forfeited if the bidder withdraws, amends, impairs or derogates from
the tender in any respect within the validity period of their tender. Firms registered as
MSME or any other similar category will be exempt from submission of EMD.

Indian Naval Ship Maintenance Authority Page 4

 Part II – Essential Details of Items/Services required

1. Schedule of Requirements. Requirements as necessary, for Installation of

Comprehensive Maintenance Management System (CMMS) in CMMS Application &
Database hosted at INSMA is placed at Appendix ‘A’. Vendors are to submit their
optimal solution for design, development and implementation of application on a
turnkey basis. This shall include: -

Ser Milestone Milestone Goal

URS
(a) Documentation Feasibility studies and basic system concepts
and Concept have been frozen and approval by the
Approval management accorded to proceed for detailed
requirement.
(b) Requirements Requirements specifications are complete,
Review correct, approved and suitable for input to design.
UAT
(c) Preliminary The architectural design satisfies all product
Design Review requirements and is approved and is suitable for
input into the detailed design process and
development. The architectural design is to be
submitted to concerned agencies in Indian Navy
for vetting and approval.
(d) Test plan review Test plans approved and ready for input into
integration testing. All relevant test plans are to
be submitted to concerned agencies in Indian
Navy for vetting and approval.
(e) System test The software product has passed system testing
review and is suitable for input into acceptance testing
post bug fixing.
(f) Operational The software product has passed acceptance
readiness review testing and is suitable for deployment in its target
and Security production environment. All security testing
Testing completed.
FINAL DELIVERY OF PRODUCT
(g) Training and Personnel of target environment trained for use of
Documentation the product. Documentation handed over and
acceptance obtained.
(h) Product The software is in used in its target operational
operational environment

2. Technical details and Scope of Work. The technical details/ requirements

and scope of work are placed at Appendix ‘A’. The vendor must keep in view the
following key requirements while suggesting the solution: -

Indian Naval Ship Maintenance Authority Page 5

 (a) Define design specifications of the solution, complete in all respects,
subject to requirements specified in subsequent sections and ensure efficient
implementation inclusive of any process management review that may be
required to provide utmost benefit to Navy’s critical operational environment.

(b) The solution should provide a high Return-On-Investment. It should be

easily extended to link to all future web enabled, applications. Implementation
of new applications should only require additions / upgrades to this architecture
without the need to undo any of the investments.

(c) The solution should be open-source, extendable and flexible as per

industry standards so that the architecture for this solution can be utilized for
the new applications at a later date. The system should also provide
mechanisms for error handling and robustness to scale up on demand to
support future upgrades/ additional applications without any major changes.

3. Two-bid System/ Compliance Matrix. In respect of Two-bid system, bidders

are required to furnish clause by clause compliance of specifications bringing out
clearly the deviations from specification, if any, as per the format below. In case of
non-compliance, deviation from RFP to be specified in unambiguous terms. In this
regard Technical Compliance Matrix and documents to be attached are placed at
Appendix ‘B’. Development activity associated with the project is in Defense
environment and is unlike any other market based developmental project. As part of
Technical Evaluation the Buyer would conduct an on premise visit for Proof of Concept
(PoC) and to assess firm’s technical capability. The PoC is part of Technical
Evaluation and hence all cost with respect to PoC will be borne by the Bidder. The
Technical Evaluation would be undertaken in two phases, Phase-1 would comprise of
document verification as per vendor evaluation criteria and Phase-2 would consist of
Proof of Concept (based on buyer defined scope of development). The firms clearing
Phase-1 would only be considered to go through Phase-2, scope and timelines would
be intimated through corrigendum to the successful bidders. Successful
demonstration of PoC within 15 days (at Naval Premise) is a mandatory requirement
for the Vendor to qualify TEC. The PoC will be evaluated by a nominated team at IHQ
MoD(N)/DIT or Headquarters Western Naval Command and the decision of TEC
would be final and applicable for qualification of technically capable firms.

4. Delivery and Transportation. All expenses towards transportation and

delivery of the offered solution comprising both hardware and software components,
as applicable at the consignee’s local address mentioned below are to be borne by
the Seller.

5. Consignee details
The Director,
Indian Naval Ship Maintenance Authority,
Fleet Maintenance Unit,
Naval Dockyard {for (ITO)},
Mumbai- 400 023.

Indian Naval Ship Maintenance Authority Page 6

 PART III – Standard Conditions of RFP

The Bidder is required to give confirmation of their acceptance of the Standard

Conditions of the Request for Proposal mentioned below which will automatically be
considered as part of the Contract concluded with the successful Bidder (i.e. SELLER
in the Contract) as selected by the BUYER. Failure to do so may result in rejection of
the Bid submitted by the Bidder.

1. Law The Contract shall be considered and made in accordance with the laws
of the Republic of India. The contract shall be governed by and interpreted in
accordance with the laws of the Republic of India.

2. Effective Date of the Contract The contract shall come into effect on the
date of signatures of both the parties on the contract (Effective Date) and shall remain
valid until the completion of the obligations of the parties under the contract. The
deliveries, supplies and performance of the services shall commence from the
effective date of the contract

3. Arbitration All disputes or differences arising out of or in connection with the

Contract shall be settled by bilateral discussions. Any dispute, disagreement or
question arising out of or relating to the Contract or relating to construction or
performance, which cannot be settled amicably, may be resolved through arbitration.
The standard clause of arbitration is as per Forms DPM-7, DPM-8 and DPM-9
(Available in MoD website and can be provided on request)

4. Penalty for use of Undue Influence The SELLER undertakes that he has
not given, offered or promised to give, directly or indirectly, any gift, consideration,
reward, commission, fees, brokerage or inducement to any person in service of the
Buyer or otherwise in procuring the Contracts or for bearing to do or for having done
or for borne to do any act in relation to the obtaining or execution of the present
Contract or any other Contract with the Government of India for showing or for bearing
to show favour or disfavour to any person in relation to the present Contract or any
other Contract with the Government of India. Any breach of the aforesaid undertaking
by the Seller or any one employed by him or acting on his behalf (whether with or
without the knowledge of the Seller) or the commission of any offers by the Seller or
anyone employed by him or acting on his behalf, as defined in Chapter IX of the Indian
Penal Code, 1860 or the Prevention of Corruption Act, 1986 or any other Act enacted
for the prevention of corruption shall entitle the Buyer to cancel the contract and all or
any other contracts with the Seller and recover from the Seller the amount of
any loss arising from such cancellation. A decision of the Buyer or his nominee
to the effect that a breach of the undertaking had been committed shall be final and
binding on the Seller. Giving or offering of any gift, bribe or inducement or any attempt
at any such act on behalf of the Seller towards any officer/employee of the Buyer or
to any other person in a position to influence any officer/employee of the Buyer for
showing any favour in relation to this or any other contract, shall render the Seller to
such liability/ penalty as the Buyer may deem proper, including but not limited to
termination of the contract, imposition of penal damages, forfeiture of the Bank
Guarantee and refund of the amounts paid by the Buyer.

5. Agents/Agency Commission. The SELLER confirms and declares to the

BUYER that the SELLER is the original manufacturer of the stores/provider of the
Indian Naval Ship Maintenance Authority Page 7
services referred to in this Contract and has not engaged any individual or firm,
whether Indian or foreign whatsoever, to intercede, facilitate or in any way to
recommend to the Government of India or any of its functionaries, whether officially
or unofficially, to the award of the contract to the SELLER; nor has any amount been
paid, promised or intended to be paid to any such individual or firm in respect of any
such intercession, facilitation or recommendation. The SELLER agrees that if it is
established at any time to the satisfaction of the BUYER that the present declaration
is in any way incorrect or if at a later stage it is discovered by the BUYER that the
SELLER has engaged any such individual/firm, and paid or intended to pay any
amount, gift, reward, fees, commission or consideration to such person, party, firm or
institution, whether before or after the signing of this contract, the SELLER will be
liable to refund that amount to the BUYER. The SELLER will also be debarred from
entering into any supply Contract with the Government of India for a minimum period of
five years. The BUYER will also have a right to consider cancellation of the Contract
either wholly or in part, without any entitlement or compensation to the SELLER who
shall in such an event be liable to refund all payments made by the BUYER in terms
of the Contract along with interest at the rate of 2% per annum above LIBOR rate. The
BUYER will also have the right to recover any such amount from any contracts
concluded earlier with the Government of India

6. Access to Books of Accounts. In case it is found to the satisfaction of the

BUYER that the SELLER has engaged an Agent or paid commission or influenced
any person to obtain the contract as described in clauses relating to Agents/Agency
Commission and penalty for use of undue influence, the SELLER, on a specific
request of the BUYER, shall provide necessary information/ inspection of the relevant
financial documents/information

7. Non-disclosure of Contract documents. Except with the written consent of

the BUYER/ SELLER, other party shall not disclose the contract or any provision,
specification, plan, design, pattern, sample or information thereof to any third party.

8. Liquidated Damages. In the event of the SELLER's failure to submit the

Bonds, Guarantees and Documents, supply the services and maintain the agreed
uptime etc as specified in this contract, the BUYER may, at his discretion, withhold
any payment until the completion of the contract. The BUYER may also deduct from
the SELLER as agreed, liquidated damages to the sum of 0.5% of the contract
price of the delayed/undelivered stores/services mentioned above for every
week of delay or part of a week, subject to the maximum value of the Liquidated
Damages being not higher than 10% of the value of delayed services. The overall
reliability and uptime of the enterprise services shall be maintained at 98%, measured
over quarter during the contract period. This amounts to total maximum downtime of
14.4 hours per month. Also non availability should not exceed 04 hrs at one time.
Required resources/ support to attain this serviceability may be made available by the
SELLER at his own cost. Total down time would be calculated at the end of the
quarter. If downtime exceeds permitted downtime, LD would be applicable for the
delayed period

9. Termination of Contract. The BUYER shall have the right to terminate this
Contract in part or in full in any of the following cases: -

Indian Naval Ship Maintenance Authority Page 8

 (a) The delivery of the services (initial implementation) is delayed for causes
not attributable to Force Majeure for more than (01 month) after the scheduled
date of delivery.

(b) The delivery of services is delayed due to causes of Force Majeure by more than
(03 months)

(c) Use of non-genuine/duplicate/assembled/sub-standard items and poor

workmanship or substandard software product while undertaking the contract

(d) The BUYER has noticed that the SELLER has utilized the services of
any Indian/Foreign agent in getting this contract and paid any commission to
such individual/company etc.

(e) In any other occasion when the BUYER feels that the continuation of the
contract will lead to breach of Information Security.

(f) As per decision of the Arbitration Tribunal.

10. Notices. Any notice required or permitted by the contract shall be written in the
English language and may be delivered personally or may be sent by FAX or email or
registered pre-paid mail/airmail, addressed to the last known address of the party to
whom it is sent.

11. Transfer and Sub-letting. The SELLER has no right to give, bargain, sell,
assign or sublet or otherwise dispose of the Contract or any part thereof, as well as to
give or to let a third party take benefit or advantage of the present Contract or any part
thereof.

12. Patents and other Industrial Property Rights. The prices stated in the
present Contract shall be deemed to include all amounts payable for the use of
patents, copyrights, registered charges, trademarks and payments for any other
industrial property rights. The SELLER shall indemnify the BUYER against all claims
from a third party at any time on account of the infringement of any or all the rights
mentioned in the previous paragraphs, whether such claims arise in respect of
manufacture or use. The SELLER shall be responsible for the completion of the
supplies including spares, tools, technical literature and training aggregates
irrespective of the fact of infringement of the supplies, irrespective of the fact of
infringement of any or all the rights mentioned above.

13. Amendments. No provision of the Contract shall be changed or modified in

any way (including this provision) either in whole or in part except by an instrument in
writing made after the date of this Contract and signed on behalf of both the parties
and which expressly states to amend the present Contract.

14. Taxes and Duties. Taxes and duties would be levied as per the existing
government norms/extent regulations/GST regulations.

Indian Naval Ship Maintenance Authority Page 9

 PART IV – Special Conditions of RFP

The Bidder is required to give confirmation of their acceptance of Special Conditions

of the RFP mentioned below, in the format mentioned in Para 19 of Part II, which will
automatically be considered as part of the Contract concluded with the successful
Bidder (i.e. SELLER in the Contract) as selected by the BUYER (i.e Indian Navy in the
Contract). Failure to do so may result in rejection of Bid submitted by the Bidder.

1. Performance Guarantee. The Bidder will be required to furnish a

Performance Guarantee by way of Bank Guarantee through a public sector bank or a
private sector bank authorized to conduct government business (ICICI Bank Ltd., Axis
Bank Ltd or HDFC Bank Ltd.) for a sum equal to 10% of the contract value within 30
days of signing of this contract. Performance Bank Guarantee will be valid up to 60
days beyond the date of warranty/services (as applicable). The specimen of PBG is
given in Form DPM-15 (Available in MoD website and can be provided on request).

2. Option Clause. The contract will have an Option Clause, wherein the Buyer
can exercise an option to procure an additional 5% of the original contracted quantity
in accordance with the same terms and conditions of the present contract. This will be
applicable within the currency of contract. The Bidder is to confirm the acceptance
of the same for inclusion in the contract. It will be entirely the discretion of the buyer
to exercise this option or not.

3. Repeat Order Clause. The contract will have a Repeat Order Clause,
wherein the Buyer can order upto 5% quantity of the items under the present contract
within six months from the date of supply/successful completion of this contract, the
cost, terms and conditions remaining the same. The bidder is to confirm acceptance
of this clause. It will be entirely the discretion of the Buyer to place the Repeat order
or not.

4. Tolerance Clause. To take care of any change in the requirement during the
period starting from issue of RFP till placement of the contract, BUYER reserves the
right to 5% plus/minus increase or decrease the quantity of the required goods/
services up to that limit without any change in the terms & conditions and prices quoted
by the SELLER. While awarding the contract, the quantity/services ordered are to be
increased or decreased by the BUYER within this tolerance limit.

5. Payment Terms. It will be mandatory for the Bidders to indicate their bank
account numbers and other relevant e-payment details so that payments could be
made through ECS/EFT or any other digital payment mechanism instead of payment
through cheques, wherever feasible. A copy of the model mandate form prescribed by
RBI to be submitted by Bidders for receiving payments through ECS is at Form DPM-
11 (Available in MoD website and can be given on request). The payment will be made
Stage-wise on production of the requisite documents. As per current practices, no
advance payment is permissible. However, to ensure cash flow, commensurate with
progress of the project and the deliverables, stage payment would be made as brought
out in succeeding paragraphs. The vendor has to split the quote in two broad sub-
heads of, Application Development and Application Support. The proposed payment
terms have been divided into stages under the broad sub-heads of Application
Development and Application Support and is indicated below: -
Indian Naval Ship Maintenance Authority Page 10
 Application Development

Ser % Remarks

URS Phase
(a) 20% Vendor will qualify to claim on completion of following
milestones: -

(i) Vendor will submit the URS and SRS document. Vetting
and approval of documents by the Navy, and commencement
of development.
(ii) Final submission of approved URS and First Software
Design Review.
Project Setting Phase
(b) 20% Vendor will qualify to claim on completion of following
milestones: -

(i) Vendor will buy complete hardware

(ii) Install the hardware and setup the development
environment as defined in the RFP
Delivery, Testing and Vulnerability Assessment Phase
(b) 30% Vendor will qualify to claim on completion of following
milestones: -

(i) Testing, VA and Delivery of the complete system.

(ii) Migration of application to production environment.
(iii) Delivery of all agreed documentation after it is duly
approved by the user.
Hand Holding Phase
(c) 30% Successful completion of hand holding period as per RFP
Scope
Warranty Phase
(d) D + 30 Warranty for 1 Yr as per scope of Warranty
Application Support

Ser % Remarks
AMC Phase
(d) 15% of Vendor will qualify to claim this stage payment every 6 months,
AMC for five consecutive times.
cost
(e) 25% of Vendor will qualify to claim this stage payment on completion
AMC of AMC period of 3 yrs
cost
2. Advance Payments. No advance payment(s) will be made.

Indian Naval Ship Maintenance Authority Page 11

3. Paying Authority: PCDA (Navy), Mumbai will be the Paying Authority. The
payment of bills will be made on submission of the following documents by the Seller
to the Paying Authority along with the bill:

(a) Indigenous Sellers. The payment of bills will be made on submission

of the following documents by the Seller to the Paying Authority along with the
bill:

(i) Ink-signed copy of contingent bill / Seller’s bill.

(ii) Ink-signed copy of Commercial invoice / Seller’s bill.

(iii) Copy of Contract with U.O. number / Copy of Supply Order and
date of IFA’s concurrence, where required under delegation of powers.

(iv) Claim for statutory and other levies to be supported with requisite
documents / proof of payment such as Excise duty challan, Customs
duty clearance certificate, OCTROI receipt, proof of payment for
EPF/ESIC contribution with nominal roll of beneficiaries, etc as
applicable.

(v) Exemption certificate for Excise duty / Customs duty, if applicable.

(vi) Warranty certificates.

(vii) Bank guarantee for advance, if any.

(viii) Performance Bank guarantee / Indemnity bond where applicable.

(ix) DP extension letter with CFA’s sanction, U.O. number and date
of IFA’s concurrence, where required under delegation of powers,
indicating whether extension is with or without LD.

(x) Details for electronic payment viz Account holder’s name, Bank
name, Branch name and address, Account type, Account number, IFSC
code, MICR code (if these details are not incorporated in contract).

(b) Foreign Sellers. NA

6. Force Majeure Clause.

(a) Neither party shall bear responsibility for the complete or partial
nonperformance of any of its obligations (except for failure to pay any sum
which has become due on account of receipt of goods under the provisions of
the present contract), if the non-performance results from such Force Majeure
circumstances as Flood, Fire, Earth Quake and other acts of God as well as
War, Military operation, blockade, Acts or Actions of State Authorities or any
other circumstances beyond the parties control that have arisen after the
conclusion of the present contract.

Indian Naval Ship Maintenance Authority Page 12

 (b) In such circumstances the time stipulated for the performance of an
obligation under the present contract is extended correspondingly for the period
of time of action of these circumstances and their consequences.

(c) The party for which it becomes impossible to meet obligations under this
contract due to Force Majeure conditions, is to notify in written form the other
party of the beginning and cessation of the above circumstances immediately,
but in any case not later than 10 (Ten) days from the moment of their beginning.

(d) Certificate of a Chamber of Commerce (Commerce and Industry) or

other competent authority or organization of the respective country shall be a
sufficient proof of commencement and cessation of the above circumstance.

(e) If the impossibility of complete or partial performance of an obligation

lasts for more than 6 (six) months, either party hereto reserves the right to
terminate the contract totally or partially upon giving prior written notice of 30
(thirty) days to the other party of the intention to terminate without any liability
other than reimbursement on the terms provided in the agreement for the goods
received.

7. Fall clause. The following Fall clause will form part of the contract placed on
successful Bidder

(a) The price charged for the stores supplied under the contract by the
Seller shall in no event exceed the lowest prices at which the Seller sells the
stores or offers to sell stores of identical description to any person/ Organisation
including the Buyer or any department of the Central Government or any
department of State Government or any statutory undertaking the Central or
State governments as the case may be during the period till performance of all
supply Orders placed during the currency of the rate contract is completed.

(b) If at any time, during the said period the Seller reduces the sale price,
sells or offers to sell such stores to any person/organisation including the Buyer
or any Dept, of Central Govt. or any Department of the State Government or
any statutory undertaking of the Central or state Government as the case may
be at a price lower than the price chargeable under the contract, he shall
forthwith notify such reduction or sale or offer of sale to the Director General of
Supplies & Disposals and the price payable under the contract for the stores
of such reduction of sale or offer of the sale shall stand correspondingly
reduced. The above stipulation will, however, not apply to

(i) Exports by the Seller.

(ii) Sale of goods as original application at price lower than the prices
charged for normal replacement.

(iii) Sale of goods at lower price on or after the date of completion of

sale/placement of the order of goods by the authority concerned under
the existing or previous Rate Contracts as also under any previous
contracts entered into with the Central or State Govt. depts, including
their undertakings excluding joint sector companies and/or private
parties and bodies.

Indian Naval Ship Maintenance Authority Page 13

8. Risk & Expense clause.

(b) Should the item/stores/services or any installment thereof not be

delivered with the time or time specified in the contract documents, or if
unsatisfactory delivery is made in respect of the services or any installment
thereof, the BUYER shall after granting the SELLER 30 days to cure the
breach, be at liberty, without prejudice to the right to recover liquidated
damages as a remedy for breach of contract, to declare the contract as
cancelled either wholly or to the extent of such default.

(c) Should the item/stores/services or any installment thereof not perform in

accordance with the specifications / parameters provided by the SELLER
during the check proof tests or system evaluation, the BUYER shall be at
liberty, without prejudice to any other remedies for breach of contract, to cancel
the contract wholly or to the extent of such default.

(d) In case of a material breach that was not remedied within 45 days, the
BUYER shall, having given the right of first refusal to the SELLER be at liberty
to purchase, manufacture, or procure from any other source as he thinks fit,
other stores of the same or similar description to make good: -

(i) Such default.

(ii) In the event of the contract, being wholly determined the balance
of the stores remaining to be delivered there under.

(e) Any excess of the purchase price, cost of manufacturer, or value of any
stores procured from any other supplier as the case may be, over the contract
price appropriate to such default or balance shall be recoverable from the
SELLER. Such recoveries shall not exceed 10% of the value of the contract.”

9. Quality. Contract shall correspond to the technical conditions and

standards valid for the development of software application for specifications
enumerated as per Scope of Work of RFP and shall also include therein modification
to the functionality/features suggested by the Buyer. Such modifications will be
mutually agreed to. The Seller confirms that the application to be supplied under this
Contract shall be new i.e. not manufactured before (Year of Contract), and shall
incorporate all the latest improvements and modifications. Seller would be required to
provide all test facilities at his premises for acceptance and inspection by Buyer. The
details in this regard will be coordinated during the negotiation of the contract. The
item should be of the latest manufacture, conforming to the current production
standard and having 100% defined life at the time of delivery. The Seller is required
to undertake detailed study to ascertain entire scope of work. The system
documentation should be detailed and self-explanatory. The reports should be
exhaustive with illustrations and explanations (wherever required) for easy
understanding of the Buyer. Training should be imparted so that trainees would be
able to understand the methodology and operate the software. The software should
be robust with user-friendly GUI. Documentation especially with respect to the
software should be complete in all respects.

10. Quality Assurance. The quality of the study, reports, training, documentation
and software should be acceptable to the Buyer on demonstration by the Seller.

Indian Naval Ship Maintenance Authority Page 14

11. Inspection and Acceptance. The Inspection will be carried out by Director
INSMA or a rep nominated by him. The mode of Inspection will be Self-certification.
The software should be checked against a field trials for satisfactory performance. The
modalities for field trials will be finalized by the Buyer during the development stage
and will be presented to the Seller for conduct of trials.

12. Claims. The following claims clause will form part of the contract placed on
successful Bidder

(a) The claims may be presented either on quantity of the items part of
application, where the quantity does not correspond to the requirement shown
in the Scope of Work as mentioned, or on quality of the application, where
quality does not correspond to the technical Specifications mentioned in Scope
of Work.

(b) The quantity claims for deficiency of quantity shall be presented within 3
months of completion of acceptance of application. The quantity claim shall be
submitted to the Seller as per Form DPM-22 (Available in MoD website and can
be given on request).

(c) The quality claims for defects or deficiencies in quality noticed during the
acceptance shall be presented within 3 months of commencement of contract.
Quality claims shall be presented for deficiencies in quality noticed during
contractual period but not later than expiry of the contractual period. The quality
claims shall be submitted to the Seller as per Form DPM-23 (Available in MoD
website and can be given on request).

(d) The description and quantity of the application are to be furnished to the
Seller along with concrete reasons for making the claims. Copies of all the
justifying documents shall be enclosed to the presented claim. The Seller will
settle the claims within 45 days from the date of the receipt of the claim at the
Seller’s office, subject to acceptance of the claim by the Seller. In case no
response is received during this period the claim will be deemed to have been
accepted.

(e) The Seller shall uninstall the application from the location nominated by
the Buyer and deliver the new application at the same location under Seller’s
arrangement.

(f) Claims may also be settled by reduction of cost of application under

claim from bonds submitted by the Seller or payment of claim amount by Seller
through demand draft drawn on an Indian Bank, in favour of Principal
Controller/Controller of Defence Accounts concerned.

(g) The quality claims will be raised solely by the Buyer and without any
certification/countersignature by the Seller’s representative.

13. Product Support (Handholding, Annual Maintenance Contract). The Seller

agrees to provide Product Support for the Software for a total of 4.5 years
comprising 06 months hand-holding, 01 year Warranty and 03 years of CAMC
post-delivery of software to Indian Navy (de-bugging, removal of glitches, any up-

Indian Naval Ship Maintenance Authority Page 15

gradation to make the software (or any sub-part of the application) more user-friendly
or resolution of ambiguities on usage of the software, if any). The firm has to strictly
provide onsite engineers a per qualification criteria provided at Appendix ‘C’, failing
which Indian Navy would charge penalty as per extent rates of the demanded
expertise, in case of any variation in this, the decision has to be mutually agreed and
recorded. Detailed scope of Product Support is defined at Appendix ‘C’.

14. Hybrid Mode for Development. The project would be developed both onsite
and offsite depending upon software development requirements to facilitate time-
bound completion of development of complete software. The bidder in no
circumstances discount this requirement and bid without considering the same. The
onsite development environment may/ may not be conducive for internet based
development. It is a must have requirement that the deployed resources for onsite
development are well conversant with the development framework and architecture
with minimal dependency on internet.

15. Specification. The following Specification clause will form part of the
contract placed on successful Bidder - The Seller guarantees to meet the
specifications as per RFP. The Seller, in consultation with the Buyer, may carry out
technical up gradation/alterations in the design, drawings and specifications due to
change in manufacturing procedures, indigenization or obsolescence. This will,
however, not in any way, adversely affect the end specifications of the equipment.
Changes in technical details, drawings repair and maintenance techniques along with
necessary tools as a result of up gradation/alterations will be provided to the Buyer
free of cost at the earliest on affecting such up gradation/alterations.

16. Warranty. The following Warranty will form part of the contract placed on
successful Bidder –
(a) The Seller warrants that the goods supplied under the contract conform
to technical specifications prescribed and shall perform according to the said
technical specifications.
(b) The Seller warrants for a period of 12 months post completion of 06
months hand-holding period from the date of acceptance of software. The
software supplied under the contract and each component used in its
development thereof shall be free from all types of defects/failures/glitches.
Warranty should also cover the hardware supplied by the seller.

(c) If within the period of warranty, the goods/spares/software are reported

by the Buyer to have failed to perform as per the specifications, the Seller shall
either replace or rectify the same free of charge, within a maximum period of 45
days of notification of such defect received by the Seller, provided that the
goods/software services are used and maintained by the Buyer as per
instructions contained in the Operating Manual. Warranty of the equipment
would be extended by such duration of downtime. Record of the down time
would be maintained by the user in the logbook. Spares required for warranty
repairs shall be provided free of cost by the Seller. The Seller also undertakes
to diagnose, test, adjust, calibrate and repair/replace the goods/equipment
arising due to accidents by neglect or misuse by the operator or damage due

Indian Naval Ship Maintenance Authority Page 16

 to transportation of the goods during the warranty period, at the cost mutually
agreed to between the Buyer and the Seller.

(d) If particular equipment/spare fails frequently, the complete lot / item shall
be replaced by the Seller free of cost within a stipulated period of 45 days of
receipt of notification from Buyer. Warranty of replaced item will start from date
of acceptance by the Buyer. Technical / shelf life of the replacement item will
not be less than original item.

(e) The Scope of warranty would be similar to the Scope of AMC with 06
suitable onsite engineers. The firm has to strictly provide onsite engineers a per
qualification criteria provided at Appendix ‘C’, failing which Indian Navy would
charge penalty as per extent rates of the demanded expertise, in case of any
variation in this, the decision has to be mutually agreed and recorded.

17. Pre-bid Vendor Conference. A pre-bid conference will be conducted at

INSMA, Naval Dockyard, Shahid Bhagat Singh Road, Colaba, Mumbai-23 on
………………… at ………. to discuss in detail issues and clarify ambiguities, if any,
pertaining to the tender, specifications and any other queries sought by vendors. In
order to obtain the requisite security clearance, the vendors are to forward the
following information with regard to the participants (maximum 02 representative per
vendor) by email on ……………………….. at least one day prior to the date of Pre-Bid
Conference. Due to sensitivity of data in the case along with the technical nature of
the deliverables, which directly effects operational capability of the Navy, it is
imperative that all bidders must attend the pre-bid meeting in person. In case of
inability to physically attend the pre-bid meeting, the respective bidder must
inform at-least one day in advance. Provisions for virtual conferencing (VC) will
be provided for bidders who have informed INSMA. The queries of vendors
failing to participate in the pre-bid meeting might remain unaddressed. In view
of the same, all bidders are encouraged to participate in the pre-bid meeting.

18. Earnest Money Deposit. The EMD may be submitted in the form of an Account
Payee Demand Draft, Fixed Deposit Receipt, Banker's Cheque or Bank Guarantee
from any of the public sector banks or a private sector bank authorized to conduct
government business as per Form DPM-16 (Available in MoD website and can be
provided on request) in favour of ………………………………. EMD is to remain valid
for a period of forty-five days beyond the final bid validity period. EMD of the
unsuccessful bidders will be returned to them at the earliest after expiry of the final bid
validity and latest on or before the 30th day after the award of the contract. The Bid
Security of the successful bidder would be returned, without any interest whatsoever,
after the receipt of Performance Security from them as called for in the contract. EMD
is not required to be submitted by those Bidders who are registered with the Central
Purchase Organization (e.g. DGS&D), National Small Industries Corporation (NSIC)
or any Department of MoD or MoD itself. The EMD will be forfeited if the bidder
withdraws, amends, impairs or derogates from the tender in any respect within the
validity period of their tender. Any, certificate/ governing rule exempting EMD shall be
submitted with the bid.

19. Delivery Period & Schedule. The project for complete upgradation of CMMS
to be completed in 18 months. Post completion of project, the bidder has to provide

Indian Naval Ship Maintenance Authority Page 17

hand holding/technical onsite support for 06 months. Post completion of handholding
a warranty support for 12 months followed by AMC for 03 years towards providing non
hindered support. Please note that Contract can be cancelled unilaterally by the Buyer
in case non-compliance of terms & conditions within the contracted period. Extension
of contracted period will be at the sole discretion of the Buyer. Delivery Schedule is as
tabulated below: -

Application Development

Ser Month Remarks

URS Phase
(a) (i) Vendor will submit the URS and SRS document for
vetting and approval by the Navy, and commencement of
D+1 development.
(ii) Final submission of approved URS and First Software
Design Review.
Project Setting Phase
(b) (i) Vendor will buy and install the complete hardware and
setup the development environment as defined in the RFP
D+2
(ii) Vendor will set up working stations to install the
hardware and position the developers for onsite development.
Delivery, Testing and Vulnerability Assessment Phase
(b) (i) Testing, VA and delivery of the complete system.
(ii) Migration of application to production environment.
D + 18
(iii) Delivery of all agreed documentation after it is duly
approved by the user.
Delivery Schedule: -

(i) Phase 1. Following modules should be delivered as part

of Phase 1 of development: -

(aa) Management Rights

(ab) Ship Fit Definition
(ac) MAINTOP
(ad) SRAR
(ae) DART – UM2
(af) EMAPs

(ii) Phase 2. Following modules to be delivered as part of

Phase 2 of development: -

(aa) OPDEF
(ab) REFIT Module
(ac) STOREDEM OPDEM
(ad) CANDEF CANDEM

(iii) Phase 3. Balance of the modules to be developed as

part of Phase 3.
Hand Holding Phase
Indian Naval Ship Maintenance Authority Page 18
 (c) Successful completion of hand holding period as per RFP
D + 24Scope
Warranty Phase
(d) D + 36 Warranty for 1 Yr as per scope of Warranty
Application Support

Ser Month Remarks

AMC Phase
(d)
D + 72 All Scope of CAMC as defined in the RFP

20. Rejection of Offer. An offer received incomplete or ambiguous is likely to be

rejected at the discretion of the Indian Navy without recourse to further clarifications.
The Indian Navy also reserves the right to seek clarifications with one or more vendors
if considered necessary and also not accept any offer at all in case they are not
reasonably priced.

21. Acceptance of Extension. In case of any circumstances arriving

wherein the buyer has to extend the existing contract iaw DFPDS-21 the seller has to
agree to extend the existing contract on the same terms and conditions as mentioned
in the existing contract.

22. Removal and / or Replacement of Vendor's Personnel. If the purchaser

finds that any of the vendor's personnel have:

(a) Committed serious misconduct or have been charged with having

committed a criminal action; or

(b) Has reasonable cause to be dissatisfied with the performance of any of the
personnel

23. Then the vendor shall at the purchasers' written request specifying the grounds
therefore, forthwith provide as a replacement person with qualifications and
experience acceptable to the purchaser. The vendor shall have no claim for additional
costs arising out of / or incidental to any removal and / or replacement of personnel.

24. Security. The following security clauses will be part of the contract: -

(a) The Seller is bound by the Official Secrets Act 1923 and, in its
connection any other statutory Act / Law / Amendment in force and the
information given is to be treated as strictly confidential and is not to be
disclosed to any person or persons not concerned therein. The Seller shall be
responsible to ensure that all persons employed by him in the execution of any
work in connection with this Contract are fully aware of the provisions of the
Official Secrets Act 1923 / Law /Amendment in force and have undertaken to
comply with the same.

(b) The Seller shall also ensure secrecy of design, construction, equipment
and documentation and shall carry out all or any instructions given by the Buyer
in this respect. Should the Buyer desire to check up the security measures

Indian Naval Ship Maintenance Authority Page 19

 which have been provided, or will be adopted to achieve security, the Seller
shall produce necessary evidence to establish the same.

(c) In giving any information to the Sub-Contractors, the Seller shall furnish
to the Sub-Contractors only such information as may be necessary for carrying
out the respective work entrusted to them.

(d) The security of the material in the Seller’s premises is the Seller’s
responsibility. The firm or its resident engineer shall not communicate any
information/data from this headquarters in any form
(telephone/mail/correspondence etc) to any external agency or any
unauthorized personnel. Any breach of this clause will lead to criminal
proceedings to be initiated against the individual and the firm.

(e) Police Verification. Each of the personnel should hold an individual

Police Verification valid in Mumbai in original.

(f) Identify Card. Each of the personnel should hold a Government issued
photo identity card (e.g., PAN card, Driving Licence, Aadhar Card etc) in original.

(g) Photocopy. Attested photocopies of the two abovementioned

documents have to be provide to this unit for recordkeeping and security
clearance within 10 working days or two weeks (whichever is earlier) from the
issue of the Work Order

(h) Attire. When in Naval premises, the personnel would have to be dressed
in formals with formal shoes (no sandals, sneakers or chappals are permitted)
and leather belt, but sans tie.

(i) Smoking and Drinking. The personnel would not smoke or consume
alcohol or be under the influence of any drug whilst within Naval premises.

25. Contractual Terms and Conditions. Any conditions/terms given in the

technical or commercial bids by vendors will not be binding on the Indian Navy. All the
terms and conditions for the supply, delivery, testing and acceptance, payment,
warranty, uptime, penalty will be as given herein and no change in any term or
condition by the vendors will be acceptable. Alterations, if any, in the tender
documents should be attested properly by the vendor, failing which the tender will be
rejected. Vendors will not make any assumptions while submitting their bids. If
required, clarifications will be sought prior to submission of bids.

26. Change in Scope. The purchaser reserves the right to increase or decrease
upto 10% of the quantity specified in the schedule of requirements without any change
in the unit price or other terms and conditions within the agreed delivery schedule. The
purchaser may at any time, by a written order given to the Vendor make changes
within the general scope of the contract in any one or more of the following: -

(f) Designs or specifications for Services for systems that are to be

integrated, developed or customized specifically for the purchaser;

(g) The method of shipment and/or schedule for and/or place of delivery;

(h) The schedule for installation for Acceptance;

Indian Naval Ship Maintenance Authority Page 20
 (i) The services to be provided by the Vendor; and/or

(j) The substitution of new products and services form the Vendor.

27. Data Security. The firm would have to abide by the Non-Disclosure
Agreement (NDA) and Malicious Code Certificate placed at Appendix ‘D’ and
Appendix ‘E’ respectively.

28. Customisation of Base Product (COTS product). The customisations of the

base product have to be carried out with the specific written approval of the purchaser.
For this purpose the Vendor shall submit detailed customisation specifications before
carrying out such customisation. A schedule for customisation shall be provided in the
project plan along with details of functional and design specifications for Custom
Software for the purchaser’s review and approval, within the time periods allocated in
the Project plan. Such specifications will define the standards of performance and
functionality of the customisation to be measured during acceptance testing. Technical
and user documentation for the customized component of the system shall be
submitted by the Vendor to enable the purchaser to use and administer the system,
and if it so elects, to develop additional modules, shall have no Intellectual Property
Rights on the Customised modules developed specifically to the purchaser’s
requirements.

29. Compliance to RFP. The proposal is to include a paragraph-wise compliance

report clearly stating compliance or non-compliance (with reasons) with the RFP.

30. Technical Bids. The information in the technical bid should be complete in
itself to facilitate full technical scrutiny. The vendor must volunteer all information
required for this purpose. The Navy reserves the right to seek necessary clarifications
on the technical bids. It must be borne in mind that no change to commercial bid,
arising out of clarifications on technical bid, is permitted. The technical proposal
submitted by the vendors should necessarily cover following details: -

(a) Complete details of the make and model of hardware and software
systems being proposed along with the standard benchmark test results.

(b) OEM tie-ups / authorized partner and service provider certificates of the
systems proposed including hardware and software.

(c) Company profile and details of infrastructure available for support in

terms of technical manpower (hardware and software), technical competence /
skill set, system analysts, design engineers, manufacturing facilities, support
infrastructure, installation team, site engineers, standards being followed etc.

(d) Delivery schedules for complete system, hardware, documentation,

installation, testing, integration and commissioning time frames and schedules.

(e) Duly filled “Vendor Evaluation Compliance Matrix”.

(f) Certificate for malicious code.

Labour Regulations
Indian Naval Ship Maintenance Authority Page 21
31. Contract Labour (R&A) Act. Contractor should obtain license under section
12 and 13 of the contract labour (Regulation & Abolition) act and rules made there
under and the same should be kept valid at least until the expiry of contract with Indian
Navy. The license should be shown as and when demanded by the concerned Indian
Navy authorities. Xerox copies of the valid license should be produced to the
respective project managers from Indian Navy from time to time. Failure to obtain the
license acceptance of the tender is liable to be withdrawn. The Contractor shall
carryout his obligations and duties under the Contract labour (R & A) Act 1970 and
the rules framed hereunder.

32. Minimum Wages Act. The contractor shall pay to the employee not less than
the minimum wages and allowances applicable to the Engineering Industry as notified
from time to time by the State Govt. under the Minimum Wages Act. Contractor shall
be responsible for timely payment of wages of all employees engaged at
HQWN/INSMA not less than the prescribed minimum wages in each case and without
any deductions of any kind except specified by Government of permissible under the
Payment of Wages Act.

33. PF Act & Scheme. The contractor wherever applicable shall cover all his
eligible employees engaged at HQWNC/INSMA premises for development under the
Employees Provident Fund Act & Scheme and Family Pension scheme and pay the
contribution both in respect of his employees and his own. He shall submit all the
necessary returns and other particulars periodically as prescribed under the said
insurance scheme by filling requisite returns to concerned authorities and obtaining
Code Number/Account Numbers. Contractor should remit employees and employers
contributions directly to the concerned authorities with inspection and Administrative
charges as per relevant provision of the concerning Acts and Schemes made there
under within 15 days from the close of every month.

34. E.S.I. Act. Contractor should also cover all the contract laborer’s working at
HQWNC/INSMA premises for development under the Employees State Insurance Act
and Scheme by furnishing necessary returns to appropriate authority and pay both
employees and employers contributions in respect of these employees to the
concerned authorities within 20 days from the close of every month. Contractor should
produce proof of such remittances to the Contracting Authority along with full details
of contributions etc, as and when such proof is sought. He shall also undertake that
he will not engage any one on our work, who is not duly covered under the said Act
Scheme.

35. Safety Terms and Conditions. This safety clause is not a substitute to
statutory requirement as specified by the Government of India or State Government
vide various acts/rules and prevailing safety regulations or norms of the Indian Navy,
but to further reinforce the existing safety standards which have to be followed by the
CONTRACTOR. All rules, regulations, codes and ordinances of the Government of
India, Government of Delhi and local bodies regarding the safety and Health will be
applicable to the contractors. The contractor is to ensure adequate safeguards for
personnel when employed on work where risk to human health/ injury is involved. Any
compensation or expenditure towards treatment for injury/ casualty or loss of life that
may take place during the course of contracted service shall be the sole responsibility
of the contractor. Software developer (both male and female) below 18 years and
above 60 years of age are not to be employed by contractor. In addition, they should

Indian Naval Ship Maintenance Authority Page 22

be free from any pre-existing morbid conditions which are likely to be aggravated by
the work in the Yard. Chronic alcoholics are not to be employed.

36. Welfare and Security. Following terms and Conditions: -

(a) The Contractor is liable to provide immediate first aid/hospitalization in

case of accident/ sudden illness to personnel.

(b) Naval authorities are to be informed by the Firm immediately in the

eventuality of any accident taking place.

(c) Compensation to the family on account of injury of any engineer

employed by the firm will be the sole liability of the firm.

(d) The firm needs to provide 10% increment of salary every year to every
resident engineer to beat inflation and provide continuity of services to Navy.

37. In cases where only indigenous Bidders are competing, all taxes and duties
(including those for which exemption certificates are issued) quoted by the Bidders
will be considered. The ultimate cost to the Buyer would be the deciding factor for
ranking of Bids.

38. Bid Cost Justification. Bidder is required to include the item wise cost for all
items and services that is to be offered as part of the Bid. The cost should be justified
as per extent hardware, software and services norms prevalent in the industry, to
ensure compliance to the highest quality for the project. In any case the bid price
should not be so low that it raises material concerns, which may lead to bid rejection.

39. The Bidders are required to spell out the rates of Customs duty, Excise duty,
VAT, Service Tax, etc in unambiguous terms; otherwise their offers will be loaded with
the maximum rates of duties and taxes for the purpose of comparison of prices. If
reimbursement of Customs duty / Excise Duty / VAT is intended as extra, over the
quoted prices, the Bidder must specifically say so. In the absence of any such
stipulation it will be presumed that the prices quoted are firm and final and no claim
on account of such duties will be entrained after the opening of tenders. If a Bidder
chooses to quote a price inclusive of any duty and does not confirm inclusive of such
duty so included is firm and final, he should clearly indicate the rate of such duty and
quantum of excise duty included in the price. Failure to do so may result in ignoring of
such offers summarily. If a Bidder is exempted from payment of Customs duty/Excise
Duty / VAT duty up-to any value of supplies from them, they should clearly state that
no excise duty will be charged by them up to the limit of exemption which they may
have. If any concession is available in regard to rate/quantum of Customs duty / Excise
Duty / VAT, it should be brought out clearly. Stipulations like, excise duty was presently
not applicable but the same will be charged if it becomes leviable later on, will not be
accepted unless in such cases it is clearly stated by a Bidder that excise duty will not
be charged by him even if the same becomes applicable later on. In respect of the
Bidders who fail to comply with this requirement, their quoted prices shall be loaded
with the quantum of excise duty which is normally applicable on the item in question
for the purpose of comparing their prices with other Bidders. The same logic applies
to Customs duty and VAT also.

Indian Naval Ship Maintenance Authority Page 23

40. If there is a discrepancy between the unit price and the total price that is
obtained by multiplying the unit price and quantity, the unit price will prevail and the
total price will be corrected. If there is a discrepancy between words and figures, the
amount in words will prevail for calculation of price.

41. The Lowest Acceptable Bid will be considered further for placement of contract
/ Supply Order after complete clarification and price negotiations as decided by the
Buyer. The Buyer will have the right to award contracts to different Bidders for being
lowest in particular items. The Buyer also reserves the right to do Apportionment of
Quantity, if it is convinced that Lowest Bidder is not in a position to supply full quantity
in stipulated time.

Part V – Evaluation Criteria & Price Bid issues

1. Evaluation Criteria - The broad guidelines for evaluation of Bids will be as

follows:

(a) Only those Bids will be evaluated which are found to be fulfilling all the
eligibility and qualifying requirements of the RFP, both technically and
commercially.

(b) In respect of Two-Bid system, the format for submission of commercial

bids is placed at Annexure ‘F’. Firms are to submit the Technical Bids as per
format placed at Annexure ‘B’. The technical Bids forwarded by the Bidders
will be evaluated by the Buyer with reference to the technical characteristics of
the equipment as mentioned in the RFP. The compliance of Technical Bids
would be determined on the basis of the parameters specified in the RFP. The
Price Bids of only those Bidders will be opened whose Technical Bids would
clear the technical evaluation.

(c) The Lowest Bid will be decided upon the lowest price quoted by the
particular Bidder as per the Price Format. The consideration of taxes and duties
in evaluation process will be as follows: -

Indian Naval Ship Maintenance Authority Page 24

 (i) In cases where only indigenous Bidders are competing, all taxes
and duties (including those for which exemption certificates are issued)
quoted by the Bidders will be considered. The ultimate cost to the Buyer
would be the deciding factor for ranking of Bids.

(ii) In cases where both foreign and indigenous Bidders are

competing, following criteria would be followed –

(aa) In case of foreign Bidders, the basic cost (CIF) quoted by

them would be the basis for the purpose of comparison of various
tenders.

(ab) In case of indigenous Bidders, excise duty on fully formed

equipment would be offloaded.

(iii) Sales tax and other local levies, i.e. OCTROI, entry tax etc would
be ignored in case of indigenous Bidders.

(d) The Bidders are required to spell out the rates of Customs duty, Excise
duty, VAT, Service Tax, etc in unambiguous terms, otherwise their offers will
be loaded with the maximum rates of duties and taxes for the purpose of
comparison of prices. If reimbursement of Customs duty / Excise Duty / VAT is
intended as extra, over the quoted prices, the Bidder must specifically say so.
In the absence of any such stipulation it will be presumed that the prices quoted
are firm and final and no claim on account of such duties will be entrained after
the opening of tenders. If a Bidder chooses to quote a price inclusive of any
duty and does not confirm inclusive of such duty so included is firm and final,
he should clearly indicate the rate of such duty and quantum of excise duty
included in the price. Failure to do so may result in ignoring of such offers
summarily. If a Bidder is exempted from payment of Customs duty / Excise Duty
/ VAT duty up-to any value of supplies from them, they should clearly state that
no excise duty will be charged by them up to the limit of exemption which they
may have. If any concession is available in regard to rate/quantum of Customs
duty / Excise Duty / VAT, it should be brought out clearly. Stipulations like,
excise duty was presently not applicable but the same will be charged if it
becomes leviable later on, will not be accepted unless in such cases it is clearly
stated by a Bidder that excise duty will not be charged by him even if the same
becomes applicable later on. In respect of the Bidders who fail to comply with
this requirement, their quoted prices shall be loaded with the quantum of excise
duty which is normally applicable on the item in question for the purpose of
comparing their prices with other Bidders. The same logic applies to Customs
duty and VAT also.

(e) If there is discrepancy between the unit price and the total price that is
obtained by multiplying the unit price and quantity, the unit price will prevail and
the total price will be corrected. If there is a discrepancy between words and
figures, the amount in words will prevail for calculation of price.

(f) The Lowest Acceptable Bid will be considered further for placement of
Supply Order after complete clarification and price negotiations as decided by

Indian Naval Ship Maintenance Authority Page 25

 the Buyer. The Buyer will have the right to award contracts to different bidders
for being lowest in particular items

2. Vendor Evaluation. The vendor must enclose a tender specific

authorization from the manufacturer of passive and active devices and other hardware
and software, which the vendor intends to supply as part of the present proposal. The
authorization must clearly state the present partnership status and the partner’s
authorization to sell and maintain the products. The compliance to vendor evaluation
criteria should be submitted as per the format placed at Appendix ‘G’.

42. Commercial Bid. The Commercial Bids are to correspond to the Technical
Bids and contain all costing details as per the bill of material. Commercial bids of only
technically qualified vendors will be considered. The information in commercial bid
must be in unitized form so that commercial bids of all firms can be properly compared
and L1 vendor can be clearly established. The Navy reserves the right to seek
clarification on commercial bids. The vendor cannot change the overall cost quoted in
the original commercial bid. The format for submitting the commercial bids could be
discussed and finalized during the pre-bid vendor conference, however decision of
Navy in this regard shall be final.

Note:- Determination of L-1 will be done based on total of basic prices (not including
levies, taxes and duties levied by Central / State / Local governments such as CSGT
/ SGST / IGST on final product) of all items / requirements as mentioned above.

(Shubham Kumar)
Lt Commander
System Controller (NUMARC)
INSMA
Feb 24

Indian Naval Ship Maintenance Authority Page 26

 Appendix ‘A’

TECHNICAL DETAILS AND SCOPE OF WORK

COMPREHENSIVE MAINTENANCE MANAGEMENT SYSTEM (CMMS)

1. Comprehensive Maintenance Management System (CMMS) at INSMA is a

web-based database solution designed as a repository of data pertaining to equipment
fitted on-board ships/submarines of the Navy. The CMMS application was
commissioned in 2007 and is available pan Navy to over 20,000 users on Naval
Unified Domain. Presently the application hosts over 2 million records with a lakh more
being added every year. The thrust of the original CMMS development project was on
efficient data warehousing. With the ever-burgeoning database and an application
built on legacy technologies an acute need is being felt design and development of a
state-of-the-art CMMS application addressing requirements such as efficient and well-
organized data storage, fast and efficient query outputs, advanced data mining
capability into the existing application.

2. Presently Comprehensive Maintenance Management System (CMMS) exists

as web application/database. Any upgradation or modification needs changes in code
which requires expertise of the programmer and understanding of the program logic
as well as environment in which the application is operating. Further with ever
expanding user and database and data, the applications in current form is not suitable
for up-scaling. Therefore, CMMS is required to be designed and developed from
ground-up with state of art open source technologies with capability to upscale while
retaining the legacy application functional features.

3. Technical details and scope of work for design and development of

Comprehensive Maintenance Management System (CMMS) comprises complete
scope of project development, and promises to provide hardware, software,
development, testing, setting to Work & commissioning, warranty, post Go Live
support and all associated services. Associated firm which will also act as the System
Integrator shall be completely responsible for the execution of the project as a single
point solution provider and sole prime contractor for the entire project. The firm has
to follow the defined overall architecture (placed at Annexure ‘I’) and technical
specifications at every phase of the project.

Objective of Proposed System/Schedule of Requirement

4. The broad objectives of proposed solution would be to address the following

issues: -

(a) There must be a demonstrable and significant increase in speed of

drawing information from CMMS database.

(b) Provide user specific rights / information/ data / reports on demand along
with relevant information/data from the vast repository of CMMS database to
various stakeholders PAN Navy.

Indian Naval Ship Maintenance Authority Page 27

 (c) The proposed Comprehensive Maintenance Management System
(CMMS) solution should incorporate features to ensure security of data by
displaying results according to login role/ designation based access rights.

(d) Low total cost of ownership.

(e) Provides all supporting software or open source software tools, relevant
code (with suitable comments) which are separately purchased by the unit, thus
reducing the overall expenditure in terms of timely procurement of new software
and cost of upgrading the software as in when new version is launched.

(f) Increased productivity by providing module-wise visualization,

dashboards, tables, graphs, downloadable reports (in requisite format) and
relevant information.

(g) The Comprehensive Maintenance Management System (CMMS)

solution should maintain a retrievable log of time stamped information
exchanged everyday between INSMA/ CMMS and various stakeholders pan-
Navy.

(h) Integration of suitable visualization tools in the application to present the

available data with multiple individual selections, filters and classifications to
ensure relevant information to specific users in an easy to understand format to
aid in quick decision making.

5. Overall scope of the project has been covered in subsequent paragraphs and
detailed scope and specifications are provided as Annexures to the relevant paras in
this appendix, a brief description is as follows: -

6. Basic Components of Comprehensive Maintenance Management System

(CMMS). The basic 5 layered architecture of CMMS application can be understood
and same can also be replicated. The basic components of Comprehensive
Maintenance Management System (CMMS) are as follows: -

(a) Presentation. This is the way applications appears to the end user. The
improvements to the current set-up can be undertaken by various animations
and scripts on offer in an open domain.

(b) User Interface. It is a software component that forms the bridge

between the user and the databased. The UI is required to allow users to
interact with the application in a seamless and intuitive way to facilitate ease in
input and exchange of data.

(c) Business Logic. This component resides between user and the
database. It helps user to input and search for information in a manner pre-
defined at the business logic layer. This layer is also to be capable of executing
complex data analysis tasks.

Indian Naval Ship Maintenance Authority Page 28

 (d) Data Access. This layer is abstracted to insert, delete and perform basic
operation on data in database. This layer is an interface between the database
and application.

(e) Data Storage. Actual physical storage. This layer is responsible for
actual storage and handling of data at physical level.

7. Schedule of Requirement. Vendors are to submit their optimal solution

for design, development and implementation of application on a turnkey basis. This
shall include: -

Ser Milestone Milestone Goal

URS
(i) Documentation Feasibility studies and basic system concepts
and Concept have been frozen and approval by the
Approval management accorded to proceed for detailed
requirement.
(j) Requirements Requirements specifications are complete,
Review correct, approved and suitable for input to design.
UAT
(k) Preliminary The architectural design satisfies all product
Design Review requirements and is approved and is suitable for
input into the detailed design process and
development.
(l) Test plan review Test plans approved and ready for input into
integration testing.
(m) System test The software product has passed system testing
review and is suitable for input into acceptance testing
post bug fixing.
(n) Operational The software product has passed acceptance
readiness review testing and is suitable for deployment in its target
and Security production environment. All security testing
Testing completed.
FINAL DELIVERY OF PRODUCT
(o) Training and Personnel of target environment trained for use of
Documentation the product. Documentation handed over and
acceptance obtained.
(p) Product The software is in used in its target operational
operational environment

8. Broad Attributes of the Comprehensive Maintenance Management

System (CMMS). The systems shall process and share the information in an
integrated manner and make best use of state of art technologies for synchronizing/
fetching/ uploading/ transferring of data between the servers onboard the Ships and
Submarines and External servers placed at various geographical locations in Indian
Navy. The application is accessed at all Indian Naval bases through Navy-wide
network, which are linked to the live servers at various locations and one NLDR (near
line disaster recovery) server. The database in all servers synchronize with each other
and ensures the replication of data in all of them. Broadly, the Comprehensive
Indian Naval Ship Maintenance Authority Page 29
Maintenance Management System (CMMS) should be able to incorporate the
following architecture to perform the intended task: -

(a) Integration with Other Systems. The solution should have a service
based federated architecture which would allow integration / update and
synchronization with all the servers – onboard and ashore, and other
applications and systems used in IN. The CMMS should employ open source
hardware and software for interoperability with various heterogeneous
applications in existence. Solution should also ensure the synchronization time
between the servers onboard ships and submarines is optimized and only the
new data based on time stamp is synchronized to ensure the same.

(b) Redundancy. The search application algorithm should be designed in

RAID or any other redundant network configuration which should provide
redundancy on disk drive failures. Also the application should have capability
to migrate to Virtual Machine environment for disaster management.

(c) Scalability. The Comprehensive Maintenance Management System

(CMMS) architecture should cater for scalability. In future the system is
expected to form the backbone of Material Common Data Framework. As part
of MAT CDF, the CMMS application is required to be linked with ILMS, WLMS
and other applications being developed as part of MAT CDF. Hence scalability
in all the layers of the system should be catered for, to meet performance
requirements with increase in user base, features and applicability.

(d) High security The new system shall cater to high security levels.
Access to the system is to be strictly on the basis of securely administered lists
of users on the navy- wide intranet based on role and designation of individual.
Single sign on facility to be incorporated in the system by integrating it to the
existing active directory.

(a) Flexibility. The application should have characteristics to get

modified/upgraded easily in a short time frame with a separate similar test
server database at INSMA with which the changes can be visualized before
implementation. The applications should have the build on complete open
source software tools and should have the flexibility for addition/ alteration or
deletion of modules as required.

(b) Service-oriented. The system design should be based on services

oriented approach

(c) Simplicity. The overall application should be developed keeping in

mind simplicity as the key, so as to enable easy operation of the application by
personnel even with only basic working knowledge of computers.

(d) Manageability. The application should cater for easy manageability

by the system administrator. It shall be based on open, inter-operable
standards and to be highly scalable, open ended and capable of delivering
high-performance. The solution / application must be able to work in a Microsoft
/ Linux Server and Desktop environment based on the end user requirement.

Indian Naval Ship Maintenance Authority Page 30

 (e) Hierarchy. The login IDs create for ship in application should have a
hierarchical structure where the transaction and approval rights are given to
different individual to ensure integrity of data collected.

(f) The architecture shall be completely web enabled and must provide
access over LAN as well as WAN.

(g) It should be able to run with equal efficiency in a network having

conventional PCs as nodes as well as in a network having thin client
architecture.

(h) Should support virtualization.

(i) Should have the facility to access the servers remotely to carry out
DI/DR in case of any application or database related issue.

(j) Should support customization of Look and feel of the portal

(k) Should integrate with email servers such as Microsoft Exchange.

(l) Should integrate with any other portal products through open standards
such as HTML, XML, RSS, web services, and WSRP

(m) Role Based Access (Admin, General user, Power user, Backup user
etc.)

(n) Should support web traffic reports for administrators and community
managers

(o) Should be XHTML 1.0/WCAG 2.0 AA compliant

(p) Should have workflow capabilities with regard to the content

approval/publishing process

(q) Should support Publishing content in web viewable formats

(r) Should support editions (versions/rollback) of the web site managed

(s) Should be able to 'send' documents to a project or group area by email

(t) The firm should design the web interface using latest available
technologies and standard process preferably XML interface. However, any
software component that may be required for functioning of the system is the
firm’s responsibility and is to be included in scope of supply. The software tools
thus used should be open-source, state of the art and as per relevant industry
standards to provide a robust, scalable and efficient over-all application.

9. Security & Authentication. Features are as follows: -

Indian Naval Ship Maintenance Authority Page 31

 (a) The search should have universal login credential for authentication,
which will be controlled by administrator.

(b) The Comprehensive Maintenance Management System (CMMS) should

be designed in such a way that it should support wide range of security and
access protocols, for example (but not limited to) Kerberos, SAML, HTTP
authentication, Windows integrated authentication etc.

(c) The application should provide a simple admin console with simplified
navigation for easy configuration of multiple user logins, allocation of admin
roles for indexing, serving and monitoring of documents in database.

(d) The Comprehensive Maintenance Management System (CMMS) should

provide a secure search feature by which admin can configure the search result
permissions, so that user will only see permission based results.

(e) The ownership of all hardware and software provided as part of the
solution along with all the relevant licenses will be transferred to Indian Navy.

(f) Should support administrator control of access permissions to shared

repositories.

(g) Should support end-user control of access restrictions to shared

repositories.

10. General Infosec Conditions. All the items viz hardware and software once
delivered will be property of Indian Navy. During maintenance support provided in case
the storage device is to be replaced, the same will be replaced by the OEM at Buyer
premises. However old storage devices will not be returned or taken out of Buyer
premises. The application would be working on INSMA Local Area Network (LAN) and
Naval Unified Domain (NUD) network. However, the application is also required to
be compatible with new Naval Communication Network (NCN) framework.

11. The various security applications running on the network include Firewall and
IDS, supplied by the Navy. Additional security overlays may be employed as and when
required. However, the application should be able to integrate with these security
overlays.

12. Additional Features

(a) Security. Audit trail is must for all data updates/amendments and
deletions for security audit. Size of log file, number of entries, time sensitivity etc
will be discussed and finalised during SRS stage

(b) Backup and Recovery. A rugged back up policy in complete federated

architecture including detailed procedures should be formulated. Audit trails for
the database and procedures for database recovery from the audit trail should
be developed. The system should maintain a backup of all programs, data,
documents, procedures, etc on timely intervals. Verification procedures for
backup taken should be in place. The minimum downtime would be finalised
during system design stage

Indian Naval Ship Maintenance Authority Page 32

 (c) General & ADHOC Queries in Proposed Solution. General queries
that have not been explicitly mentioned in the Buyer requirements based on data
that is captured should be made available based on functionalities explained in
next section. Provision to generate Adhoc queries by joining Tables in a flexible
and user-friendly manner should be made available.

(d) Integration with IN SIEM – The application is to be integrated with IN

SIEM for effective log collection and Incident Response.

(e) Feature of Central Monitoring of Security Logs – The application

should have the feature of central monitoring of security logs on application
servers.

(f) Print and Online Help Options. Proposed system must have the
facility to have Print Options for the Reports and other specified forms in general
/ Pre-Printed format agreed and approved by the Buyer. An Online and Offline
mode of help for all users and administrators should be part of the software. For
all the modules mentioned below, there must be adequate internationally
accepted standard reporting features that enable high quality graphics and user
interactivity. The reports must have facility to be ported in standard office
automation suits like excel, pdf, word documents etc or any other such formats
existing in industry and relevant to the user.

Broad Development Guidelines

13. Step-1: Prepare Project Execution Plan. This phase should define a project-
plan with detailed activity schedule and a time-bound action plan for the
implementation of the Project and associated deliverables. Following activities should
be undertaken by the firm: -

(a) Develop Project Charter. Prepare a document that formally authorizes

the existence of a project and provides the project manager with the authority
to apply organizational resources to project activities. The Firm to designate an
onsite Project Manager who would lead and perform the work defined in the
project management plan and implement approved changes to achieve the
project’s objectives.

(b) Develop Project Management Plan. Prepare an integrated project

management plan comprising requirement definition, Scope, Schedule,
timelines, resources, activity details, change management, Risk & mitigation
plan, dependencies, Project team details with responsibilities, and process
improvement plan.

(c) Manage Project Knowledge. The Project Manager has to ensure that
the existing knowledge is utilised and record the new knowledge to achieve the
project’s objectives and contribute to organizational learning.

(d) Monitor and Control Project Work. The Project Manager needs to
track, review, report overall progress to meet the performance objectives

Indian Naval Ship Maintenance Authority Page 33

 defined in the project management plan. Such activity needs to be performed
utilising an open source project management software.

(e) Perform Integrated Change Control. The Project Manager has to

undertake reviewing all change requests; approving changes and managing
changes to deliverables, organizational process assets, project documents,
and the project management plan; and communicating the decisions.

(f) Close Project. Towards the end it will be responsibility of the Project
manager and the system integrator to finalise all activities for the project,
phase, or contract. This phase should culminate with a system testing
document, wherein the System Integrator/ Project Manager needs to define a
testing document. The testing document should comprise testing of all aspects
of the developed project. On the basis of these tests, a report would be
submitted by the Firm for review and approval by IN.

14. Indian Navy would designate a Project Director. The project director will be
responsible to impart Navy domain knowledge to the Firm’s project manager and the
development team where ever required. Firm to designate a Project Manager who
would be responsible and reporting to the Project Director on weekly basis for project
progress report. Each progress report should be recorded in both hard copy and on
the Project Management Software.

15. Step-2: Project Development Setup, ‘As Is’ Study and Re-design Plan. In
order to understand the existing system an ‘As-Is’ study of the existing CMMS is to be
undertaken. Thereafter, a redesign plan is to be prepared catering to the existing
functionalities and provide for future scale ups. A clear scope for integration with other
pan-Navy established applications and use cases involved in Materiel Management
should also be part of re-design. This activity should cater to the following: -

(a) Commission a Research Study to undertake a detailed study and audit

of existing CMMS application and it’s architecture. The team has to pay
attention to data granularity, creation of metadata and identify single source of
truth for the data. The team has to identify and highlight short-comings in the
current applications and recommend means and ways to mitigate short-
comings in the new application.

(b) Detailed study to design an application that should cater for the scaling-
up to cater for the future increase in user base and data. The 5Vs of data –
Volume, Veracity, Velocity, Variability and Value are to be guiding pillars while
designing such an application.

(c) Detailed study to categorize the various equipment and systems of the
Ships into parent- child relationships using the “Systems Approach”.

(d) Data model design and development with aim to deploy data analytics
and visualization tools.

(e) Involve with Users to refine User Requirement Specification and prepare
Software Requirement Specification for complete project.

Indian Naval Ship Maintenance Authority Page 34

16. Dev-Sec-Ops Development. The firm needs to setup a Dev-Sec-Ops
environment at INSMA Mumbai for undertaking the project development iaw latest
industry parameters.

17. Hardware Requirement. Required hardware shall cater to development and

production requirement. Production environment hardware would be hosted and
installed within NCN Data Centers (at Mumbai, Vizag, Kochi, Karwar, Delhi) and DR
Site (at INSMA Mumbai), and the development hardware would be installed at INSMA,
Mumbai. The firm has to undertake end to end responsibility to procure, successfully
install and undertake Setting to Work of the hardware at respective sites. On award of
Work Order and prior procurement of hardware, the Firm needs to visit the site and
verify the hosting environment specifications obtain approval from Indian Navy. Details
of the required hardware is as follows: -

Proposed Configuration
Ser Description Qty
(but not limited to)
Standalone development server
(32 GB RAM, 32 Core, 1Tb HDD, 32 Core, 32 GB RAM, 10 TB
(a) 02
minimum i7 or as per latest version Storage
of processor available)
i7 ( minimum i7 or as per latest
(b) Development Desktops version of processor available), 16 06
GB RAM, 2 TB HDD (Windows)
i7 ( minimum i7 or as per latest
(c) Desktops for Internet Access version of processor available), 16 02
GB RAM, 2 TB HDD
Ruggedized & customized System i7 ( minimum i7 or as per latest
(d) Administrator Laptop for trouble version of processor available), 16 02
shooting post deployment GB RAM, 2 TB HDD (Windows)
Network Switch to integrate the L2 Switch (Best in Class)
(e) Standalone PCs other than the 02
Internet PC
(f) Work Stations As indicated by Indian Navy 10
(g) Scanners As indicated by Indian Navy 02
(h) Heavy Duty Multifunction Printers As indicated by Indian Navy 02

Note: Additional cost for any estimation of escalation in hardware requirement by firm
should be borne by the firm

18. Software/ License Requirement. Software would comprise of the Operating

System/ Licenses (perpetual) for the above mentioned hardware. Software required
for setting up of Data Warehouse, OCR, application development, application hosting
(dockers or any other open source state of art container platform technology) and data
analytic layer development have to be Open Source and latest available. The Vendor
shall provide perpetual Enterprise licenses for the solution at the time of
commissioning. The Vendor may provide other form of licenses, as deemed
appropriate, during Test Bed and subsequent phased roll-out/ scaling up. Detailed
requirement is covered at respective paragraphs.

Indian Naval Ship Maintenance Authority Page 35

19. Resource Requirement. Rough estimation of required skill sets is placed
below. Number of skill sets can be decided/ deployed by the firm depending upon
project development stage and available timelines. However, at no point in time the
project should suffer due to lack of number of skill sets available onsite. All resources
deployed by the firm onsite should have minimum 03 - 05 yrs experience (except DEO)
in their domain (an undertaking by SI in this regard would be mandatory). Envisaged
skill set is as mentioned below: -

(a) Solution Architect

(b) Data Warehouse architect
(c) Data Modeller
(d) Data Scientist and Machine Learning Expert
(e) Database Engineer
(f) ETL Developers
(g) Front-end and Back-end full stack Developers
(h) Technical Writer
(i) Visualisation Expert
(j) UI/UX Designer
(k) System Administrator
(l) Project Manager
(m) UI/UX and Database Testers
(n) Data Entry Operators

Note :- The list above is only indicative and in no way to be taken as binding. However,
the availability of skilled manpower should be in such a manner so as to facilitate
expeditious and efficient completion of project in a time-bound manner. The firm can
avail liberty as to positioning of suitable manpower subject to adherence to the
condition mentioned at para above.

20. Development Environment. Project Development would be undertaken at

IN specified location. IN would provide the space for development of the project. The
development environment setup would include the following tasks which needs to be
undertaken by the firm:-

(a) Setting up of Servers, PCs, Switch, scanners and work station to create
a development environment.

(b) Setting up of Scanners and mechanism for OCR activities.

(c) Setting up of environment for Data Entry Operators.

21. Baseline Software for Development. Project Development would be

undertaken based on the software baseline defined by IN and shall be mentioned
during award of contract to the selected firm. The existing CMMS will form the baseline
for reference for functional features. The indicative list of baseline software is
mentioned as below: -

LIST OF BASELINE SOFTWARE

Ser Description Stable Version Recommended

(a) Front End Angular JS – ver 12 and above
Indian Naval Ship Maintenance Authority Page 36
 Python 3.8 and above with latest version of
(b) Back End
Django Framework
(c) Database PostgreSQL ver 12 and above
(a) Masters. Defines all global variables
required within the applications.
(b) Transactions. Defines all the forms and
local variable to be transacted within each of the
form for data collection.
(d) Architecture (c) Reports. Defines aggregation of all
transacted data in the user defined logic and
format.
(d) Dashboards. Presents visual analytics
capability based on user defined logic and
visualization requirement.
Must follow single pattern for uniformity. All
modules would be listed in the left pan of the
screen. Masters, transaction, report and
dashboards are to be listed on top as buttons and
(e) UI/UX
shall have drop down list of hover for selection.
However, suitable modifications can be
undertaken to UI/UX based on the firm’s
recommendations.

Note:- List of final baseline software will be defined at the stage of award of contract.

22. Monitoring/ Maintenance Application. In order to efficiently monitor and

maintain the developed project, the System Integrator needs to implement a ticketing
mechanism on NUD/ NCN for initiating the defects/ issues online by Indian Naval
personnel. The Indian Navy would be the final owner of the source code and
same is to be handle to handed over to navy post development with all relevant
documentation and including trouble shooting and maintenance related documents.

23. Project Execution Plan

(a) Submission of Project Execution Plan. The firm will define a project-
plan with detailed activity schedule, a time-bound action plan, plan for
deployment of resources to timely implement the Project and associated
deliverables.

(b) Setting up Project Development Environment. The firm will define

and procure the required hardware, software, and deploy resources to
undertake scope of work defined for setting up of development environment.

(c) Create Data Collection Environment. The firm will undertake scope
covered for creation of database integration layer, New CMMS development,
data digitalization and Near Real Time Data Collection system. This comprises
of two Annexures: -

(i) Annexure ‘I’. Overall Project Architecture

Indian Naval Ship Maintenance Authority Page 37

 (ii) Annexure ‘II’. CMMS Architecture to be followed for module
development

(d) Create Data Storage and Processing Environment. It covers

formulation of CMMS and federated architecture for deployment of the solution
at Data Centers of all commands and DR site INSMA Mumbai.

(e) Create Data Modelling and Analytics Environment. This phase

would cover development of the data analytic layer, develop Use cases (as
defined by IN) and associated dashboards. Annexure ‘III’.

(f) Hosting of Developed Solution. On completion of the entire

development, the firm will undertake scope of work for VAPT and proceed with
hosting of solution on NCN environment.

(g) Creation of Support Environment & Training. This phase of the

project covers scope of work for Handholding (06 months), warranty (1yr) and
Comprehensive AMC (CAMC) (3 yrs) including training.

(h) Project Deliverables. This part lists the end deliverables and detailed
list of Books and Records at Annexure ‘IV’.

(j) Information Security Requirement. This covers the Information

Security Requirements mandated by the Indian Navy. Placed at Annexure ‘V’.

Prepare Project Execution Plan

24. This phase should define a project-plan with detailed activity schedule and a
time-bound action plan for the implementation of the Project and associated
deliverables. Following activities should be undertaken by the firm: -

(a) Develop Project Charter. Prepare a document that formally authorizes

the existence of a project and provides the project manager with the authority
to apply organizational resources to project activities. The Firm to designate an
onsite Project Manager who would lead and perform the work defined in the
project management plan and implement approved changes to achieve the
project’s objectives.

(b) Develop Project Management Plan. Prepare an integrated project

management plan comprising requirement definition, Scope, Schedule,
timelines, resources, activity details, change management, Risk & mitigation
plan, dependencies, Project team details with responsibilities, and process
improvement plan.

(c) Knowledge Management Plan. The Project Manager has to ensure

that the existing knowledge is utilised and record the new knowledge to achieve
the project’s objectives and contribute to organizational learning. The
knowledge thus gained and utilized is to be properly documented and handed
over to IN during closure phase of the project.

Indian Naval Ship Maintenance Authority Page 38

 (d) Monitor and Control Project Work. The Project Manager needs to
track, review, report overall progress to meet the performance objectives
defined in the project management plan. Such activity needs to be performed
utilising an open source project management software.

(e) Perform Integrated Change Control. The Project Manager has to

undertake review of all change requests; approving changes and managing
changes to deliverables, organizational process assets, project documents,
and the project management plan; and communicating the decisions.

(f) Close Project. Towards the end it will be responsibility of the Project
manager and the system integrator to finalise all activities for the project,
phase, or contract. This phase should culminate with a system testing
document, wherein the System Integrator/ Project Manager needs to define a
testing document. The testing document should comprise testing of all aspects
of the developed project. On the basis of these tests, a report would be
submitted by the Firm for review, testing and approval by IN.

25. Indian Navy would designate a Project Director. The project director will be
responsible to impart Navy domain knowledge to the Firm’s project manager and the
development team where ever required. Firm to designate a Project Manager who
would be responsible and reporting to the Project Director on weekly basis for project
progress report. Each progress report should be recorded in both hard copy and on
the Project Management Software.

Prepare Project Development Environment

26. Hardware Requirement. Required hardware shall cater to development and

production requirement. Production environment hardware would be hosted and
installed within NCN Data Centers (at Mumbai, Vizag, Kochi, Karwar, Delhi) and DR
Site (at INSMA Mumbai), and the development hardware would be installed at INSMA,
Mumbai. The firm has to undertake end to end responsibility to procure, successfully
install and undertake Setting to Work of the hardware at respective sites. On award of
Work Order and prior procurement of hardware, the Firm needs to visit the site and
verify the hosting environment specifications obtain approval from Indian Navy. Details
of the required hardware is mentioned at para 17 above.

Note: Additional cost for any escalation in hardware requirement by firm should be
borne by the firm.

27. Software/ License Requirement. Software would comprise of the Operating

System/ Licenses (perpetual) for the above mentioned hardware at Para 4. Software
required for setting up of Data Warehouse, OCR, application development, application
hosting and data analytic layer development have to be Open Source and latest
available. Detailed requirement is covered at respective paragraphs.

28. Resource Requirement. Rough estimation of required skill sets is placed

below. Number of skill sets can be decided/ deployed by the firm depending upon
project development stage and available timelines. However, at no point in time the
project should suffer due to lack of number of skill sets available onsite. All resources
deployed by the firm onsite should have minimum 03 - 05 yrs experience (except DEO)

Indian Naval Ship Maintenance Authority Page 39

in their domain (an undertaking by SI in this regard would be mandatory). Envisaged
skill set is as mentioned below:-

Skill Sets Skill Sets

.Net/Python Developers or
any other relevant,
contemporary and in- Technical Writer
vogue language for
development

ETL Developers Project Manager

Note:- The
Java/Scala Developers Visualization Expert

Testers UI/UX Designer

Data Entry Operators System Administrator

Business Analyst Data Scientist

requirement of envisaged skillset will be finalized during the award of the contract
based on the baseline software finalized by Indian Navy.

29. Development Environment. The development of the project is to be

undertaken in the naval premises (INSMA, Mumbai) and offsite at vendor’s premises
as mandated by the requirements of development of the software. The development
environment setup at INSMA would include the following tasks which needs to be
undertaken by the firm: -

(d) Setting up of Servers, PCs, Switch, scanners and work station to create
a development environment.

(e) Setting up of Scanners and mechanism for OCR activities.

(f) Setting up of environment for Data Entry Operators.

Prepare Data Collection Environment

30. Overall Architecture. Overall architecture of the proposed project is covered

at Annexure ‘I’.

31. Database Integration. Integration of legacy data from the existing CMMS
application is to be undertaken. Existing database would be of minimum 600-700GB
approx. having minimum of 800 tables. Data migration should be such that the newly
developed application is able to utilize the historical as well as the open/ newly
transacted data.

32. CMMS Development. CMMS is the Comprehensive Maintenance

Management System and the umbrella application for Naval Maintenance activities.
There exists a need to enhance its reach by re-developing various modules based on
maintenance processes in-vogue. The firm will have to study and develop CMMS
Indian Naval Ship Maintenance Authority Page 40
modules on the architecture as proposed at Annexure ‘II’. CMMS Architecture defines
the existing backbone, however the firm needs to utilize the latest software tools like
Python, Django, Postgre SQL, etc. for entire development. There would be need to
develop almost 30-35 (number of modules will be finalized post completion of initial
study and audit by the firm) modules in CMMS. Such development should fulfill the
following criteria: -

(a) User Requirement Specifications (URS) prepared by the Firm should be

approved by IN for final development. Number of modules to be developed will
be finalized during this stage.

(b) Amendments in CMMS to receive and handshake data with Materiel and
Acquisition CDF.

(c) Amendments in CMMS data structure and frontend to receive/ capture

data from IPMS, CMS, IBMS, APMS and other Management Systems.
Integration with IPMS, CMS, IBMS and APMS will entail liaison and
involvement of respective OEMs of these systems.

(d) Convert such data into a single format for consumption at CMMS end
and thereafter for analytical and presentation layer.

(e) Developed modules shall migrate historical, open transaction and new
transaction data as an initialization process.

(f) Development of Offline module and remote installation onboard all IN

platforms. Syncing with Central Server of MAT-CDF without any delay or loss
of data in transit.

(g) Development of Offline Analytical module for all IN ships and smooth
integration with MAT-CDF.

(h) Integration of Data Analytic Use Cases developed by INSMA. However,

confirmation for same will be provided during the URS finalization stage. The
firm will not be required to develop any of the Data Analytic Use Case but will
be mandated to integrate the same with CMMS upgraded application.

(i) Interface to accept data from IPMS consoles of ships. The interface
should store and present the data in required format.

(j) Integration with IETM Level 4 and above.

(k) Developed modules shall be reviewed by IN on a periodic basis in

consultation with the Project Manager. Review details are as follows: -

Ser Review Scope

Preliminary The architectural design including security

(i) architecture satisfies all product and user
Design Review
requirements and is approved and is suitable for

Indian Naval Ship Maintenance Authority Page 41

 input into the detailed design process and
development.

Final Design Liquidation of user observation on preliminary design

(ii)
Review and preparation of final design of the application

Test plans approved and ready for input into

(iii) Test plan review
integration testing.

The software product has passed system testing and

System test
(iv) is suitable for input into acceptance testing post bug
review
fixing.

Operational The software product has passed acceptance testing

readiness review and is suitable for deployment in its target production
(v)
and Security environment. All security testing completed.
Testing

33. Near Real Time Data Collection. Batch processing of machinery parametric
data received from IPMS, CMS, IBMS, APMS and other Management Systems. There
would be hourly batches, with a maximum data size varying with frequency of logs
being collected by ship staff. The processing engine should be able to transfer such
data from an onboard server to the Central Server ashore.

34. Integration with e-LogBooks. The application is required to be integrated with

e-LogBooks developed for non-IPMS based platforms. The data is collected on e-
LogBooks installed on ruggedized tablets and loaded into offline CMMS servers
installed on each platform. The new applications should be capable of ingesting
parametric data being collected in e-LogBooks and present the same in prescribed
format.

Prepare Data Modelling and Analytics Environment

35. Data Analytics. Define the analytic layer, which would allow CMMS to ingest,
process, model and analyze the complete scope of maintenance data (both structured
and unstructured) for useful insights targeted to be achieved through interactive
dashboards and pre-defined Use Cases. The CMMS upgraded stack should be in
consonance with the old stack’s functionality with newer versions/ technologies/
software existing at the time of order placement (all open source). Further, required
technical specifications of the analytics environment is placed at Annexure ‘III’.

Prepare Hosting Environment

36. Hosting/ Production Environment would need testing and deployment of the
developed data analytic application. Testing and Deployment scope covers the
following tasks: -

(a) Acceptance Testing. The purpose is to evaluate the system’s

compliance with the business requirements and verify if it has met the required
criteria for delivery to end users. The firm has to submit an Acceptance Test
Indian Naval Ship Maintenance Authority Page 42
 Plan (ATP) for approval by IN and undergo testing as per approved ATP. The
ATP should comprise attributes of various forms of testing as mentioned below:
-
(i) User Acceptance Testing. To be performed by the end user to
accept the software system before moving the software/ application in
the production environment. The applications will be subjected to
rigorous field trials at various units within Indian Navy.
(ii) Business Acceptance Testing. This testing is to be undertaken
to answer “will the system meet the business or operational needs
in the real world?” it includes Functional, System and Regression
testing.
(iii) Contract Acceptance Testing. This testing is to be performed to
assess that the developed software is tested against all the criteria and
specifications which are predefined and agreed upon in a contract.
(iv) Regulations Acceptance Testing. Also known as compliance
acceptance testing, should undertake the software compliance with the
extent regulations, government, local and legal.
(v) Operations Acceptance Testing. Focus should be on the
operational readiness of the system to be supported. Following is to be
determined: -
 Resiliency of the software
 Recovering ability of the software
 Integrity of the software
 Ability of software to be deployed on a network.
 Supportability of the software

(b) Clearance of VAPT. On completion of the project development and

testing, before final implementation, vulnerability analysis of the application
would be undertaken by a CERT empaneled firm. In addition, VA would be
carried out by CIRT-Navy. All observations wrt the developed project needs to
be timely addressed by the firm to facilitate timely hosting on the production
environment.

(c) Hosting on NCN. Once all requisite VAPT and Security clearance has
been obtained, the production environment of the developed project has to be
hosted on NCN Data Centers in a federated architecture. All network layer
requirement for setting up federated architecture would be undertaken by the
NCN team, however, all application layer requirement for federated architecture
has to be undertaken by the firm (SI). Further, the firm has to provide requisite
support and assistance to the NCN team, as and when needed for setting up
and configuration of production environment on NCN Data Centers. Prior
hosting the developed project it needs to clear VAPT test by a CERT-
empaneled firm then by CIRT-Navy, liquidation of all observation would be the
firm’s responsibility.

Indian Naval Ship Maintenance Authority Page 43

 (d) Hosting Onboard Ships. The firm would host the CMMS Offline
application on ships server onboard ships based at Mumbai and integrate with
ship’s LAN. Assistance towards the same would be provided by Indian Navy.
All requirement related to establishing two-way communication related to
application between ship server and Central server of the project has to be
undertaken by the firm. Once desired data from respective Management
Systems are received the firm has to ensure that there is no data loss/ data in-
accuracy while data is at rest and in transit. Once this is proved the Offline
application will be installed on all ships and submarines.

(e) Backup and Recovery. The backup of the application would be

undertaken at DR Site on NCN. The firm has to formulate a rugged back up
policy with detailed procedures. Audit trails for the database and procedures
for database recovery from the audit trail should be developed. The system
should maintain a backup of all programs, data, documents, procedures, etc
on timely intervals. Verification procedures for backup taken should be in place.
The minimum downtime would be finalized during system design state.

Project Deliverables

37. Project deliverables would be as follows: -

(a) Re-development of CMMS Application including Near Real Time data

processing from various onboard Management systems.

(b) Development and deployment of CMMS Offline Module

(c) Requisite hardware and Software as defined at respective paras above.

(d) Database integration (Acquisition CDF, ILMS, WLMS, Yard ERP, SDRS,
and CMS)

(e) Integration of IN developed Use Cases and IN defined dashboards.

(f) Development of a comprehensive AI enabled Comprehensive

Maintenance Management System (CMMS) to search and present data.

(g) Books and Records as defined at project deliverables section.

Create Support Environment

38. Comprehensive AMC. During the entire 03 yrs of comprehensive AMC, 04

resident engineers to be deployed at the Central Server site at INSMA, Mumbai. The
CAMC should be based on Maintenance philosophy as mentioned at Product
Support Section and should liquidate all kinds of issues arising within the developed
solution during 03 yrs period. Deployed engineers should have skill sets of ETL expert,
Data Analyst, Data Visualisation and software development. The deployed resources
should have at-least 03 years of experience in their skill set. The IN may develop more
modules / visualizations as per requirements during the AMC period through these
resources.

Indian Naval Ship Maintenance Authority Page 44

39. Training. Conduct four Awareness lectures for Users at 05 locations (each
session for a day) in a year for 03 yrs. Training of maximum 10 personnel for operation
and monitoring of the entire development at INSMA, Mumbai twice.

Information Security Requirements

40. Security. Audit trail is must for all data updates/ amendments and deletions
for security audit. Size of log file, number of entries, time sensitivity etc will be
discussed and finalised during SRS stage. Security details are covered at Annexure
‘IV’.

41. General Infosec Conditions. All the items viz hardware and software once
delivered will be property of Indian Navy. During maintenance support provided in
case the storage device is to be replaced, the same will be replaced by the firm onsite.
However old storage devices will not be returned or taken out of IN premises. Various
security applications running on the network include Firewall and IDS, will be supplied
by the Navy. Additional security overlays may be employed as and when required.
However, the application should be able to integrate with these security overlays.

42. Certification for Malicious Code and Non Disclosure Agreement (NDA).
The System Integrator will supply a certificate as per format placed at Appendix ‘G’
stating that the software is free from any virus, worm, Trojan, trap door or any other
type of malicious code. Further, the system integrator would also provide an
assurance that no information whatsoever has been siphoned/ passed over from the
development premises to the any un-authorised entity. In this regard an NDA has to
be signed and provided to INSMA by the System Integrator, as per format placed at
RFP.

Indian Naval Ship Maintenance Authority Page 45

 Annexure ‘I’ to Appendix ‘A’

OVERALL PROJECT ARCHITECTURAL OVERVIEW

1. Overall project architectural overview would provide an idea of major processes

integral for commencement and completion of the project. Each of the process and its
associated requirement are not limited to what is mentioned, however, are indicative
to clearly bring out expectation from the developed environment. Detailed requirement
is mentioned at subsequent paragraphs; however, the landscape majorly comprise of
four layers: -

(a) Source Systems.

(b) Enterprise Application Integration Layer.

(c) Common Data Foundation Layer.

(d) Downstream Systems including advanced analytical systems and other

third-party applications.

Source System Layer

2. Source System Discovery and Identification. Requires a detailed study of

all the identified source systems present in the landscape. Regardless of structure,
type, or format, source data intended for migration should be validated in terms of the
following key attributes: -

(a) Relevance. Is it relevant to its intended purpose?

(b) Accuracy. Is it correct and objective, and can it be validated?

(c) Integrity. Does it have a coherent, logical structure?

(d) Consistency. Is it consistent and easily to understand?

(e) Completeness. Does it provide all the information required?

(f) Validity. Is it within acceptable parameters for the business?

(g) Timeliness. Is it up to date and available whenever required?

(h) Accessibility. Can it be easily accessed and exported to the target

application?

(i) Compliance. Does it comply with regulatory standards?

3. Once the data discovery process for the source systems has been completed,
the next step would be to define the integration methodology by setting up the
‘Enterprise Application Integration’ layer to achieve the task of uniting the
databases and workflows associated with business applications to ensure that the

Indian Naval Ship Maintenance Authority Page 46

business uses the information consistently and that changes to core business data
made by one application are correctly reflected in others.

Enterprise Application Integration

4. ‘Enterprise Application Integration’ (EAI) is the task of uniting the databases

and workflows associated with business applications to ensure that the business uses
the information consistently and that changes to core business data made by one
application are correctly reflected in others.

5. It involves a complete system of business processes, managerial practices,

organizational interactions and structural alignments, and knowledge management. It
is an all-inclusive process designed to create relatively seamless and highly agile
processes and organizational structures that are aligned with the strategic objectives
of the enterprise. Enterprise Application Integration method to be utilized should be
Bus-Integration method using ‘Enterprise Service Bus (ESB)’.

6. Bus-Integration method allows data and functions to travel and systems speak
to each other in a faster way, without any human interference. The ESB is
implemented in software that operates between the business applications and enables
communication among them. Ideally, the ESB should be able to replace all direct
contact with the applications on the bus, so that all communication takes place via the
ESB. Primary duties of ESB are: -

(a) Route messages between services.

(b) Monitor and control routing of message exchange between services.

(c) Resolve contention between communicating service components.

(d) Control deployment and versioning of services.

(e) Marshal use of redundant services.

(f) Provide commodity services like event handling, data transformation and
mapping, message and event queuing and sequencing, security or exception
handling, protocol conversion and enforcing proper quality of communication
service.

Common Data Foundation

7. Once the source systems have been identified and the integration technology
has been set up the next step would be to build the ‘Common Data Foundation’
realm. Various components of the framework have been identified as: -

(a) Event Orchestrator. This is primarily an event management system. It

consists of three major components: -

(i) Listening Queue (Listening for messages placed in a queue).

Indian Naval Ship Maintenance Authority Page 47

 (ii) Event Management Engine (Used for identifying the event and
then selecting and executing the appropriate reaction).

(iii) Dispatcher Queue (performs tasks asynchronously and

concurrently and manages tasks submitted to it).

(b) Central Processing engine. The ‘Central Processing Engine’ should

consists of five major components: -

(i) ETL Metadata. Static metadata like the application details, list of
processes, extraction loading batches, runtime stats etc.

(ii) Event Metadata. Information related to real time data feeds,

external triggers, and event management rules.

(iii) Metrics and Logging. Handshaking between internal and

external modules in order to load data into CDF realm. Logging is
essential in order to trace the footprints. Metrics will give us the run time
stats to check the performance of the processors, load on the resources,
stop data bleeding etc in order to achieve optimization.

(iv) Daemon Controller. Is a continuously running service to trigger

the ETL processes after validating the kick-off conditions and navigating
the processes across various stages till completion.

(v) Monitoring and Alerting. Will provide meta data driven rules for
data validation, parity check, conditions for raising exceptions like
failures, delay and communicate to stakeholders by sending SMS and
Email alerts.

(b) Adaptive Data Pipeline Framework. The ‘Adaptive Data Pipeline’

would perform most of the heavy lifting related to data integration. This is a
metadata driven framework that reads from disparate data stores using generic
readers, does necessary transformation using predefined configurable rules or
ML based algorithms, standardizes, cleanses, de-duplicates and enriches the
data before writing to the target data store. Each compute process is
considered as a pipe and the entire pipeline can be considered as a
composition of multiple pipes that exchange data across data stores. The
components of the pipeline can be divided into the following three units
’Ingestion’, ‘Processing’ and ‘Consumers’ as under mentioned: -

(i) Ingestion. A data ingestion pipeline moves streaming data and

batched data from pre-existing databases and data warehouses to a
data lake. Apache Kafka, Hive, or Spark are the typical tools to be used
for data ingestion. Kafka is a popular data ingestion tool that supports
streaming data. Hive and Spark, on the other hand, move data from
HDFS data lakes to relational databases from which data could be
fetched for end users. When choosing a data ingestion tool, the following
major criteria should be taken into consideration: -

Indian Naval Ship Maintenance Authority Page 48

 (aa) The data storage format to be used when storing the data
on disks is dependent on how the organization plans on
consuming data and can be in column- or row-based storage
formats.

(ab) The optimal data compression technique for both storage

and retrieval.

(ac) Integration Platform as a Service (iPaas) could also be used

for data ingestion.

(ii) Processing. There are many data processing pipelines: -

(aa) Integrate data from multiple sources.

(ab) Perform data quality checks or standardize data.

(ac) Apply data security-related transformations, which include

masking, anonymizing, or encryption.

(ad) Match, merge, master, and do entity resolution. Share data

with partners and customers in the required format.

(iii) Consumers or “Targets”. The consumers of data pipelines may

include: -

(aa) Data warehouses like Redshift, Snowflake, SQL data

warehouses, or Teradata.

(ab) BI or Reporting tools like Tableau or Power BI.

(ac) Data lakes like Hadoop, Amazon S3, Microsoft ADLS

platform.

(ad) AI/ML algorithms.

(ae) Temporary repositories or publish/subscribe queues like

Kafka for consumption by a downstream data pipeline.

(c) Data foundation Realm. The ‘Data Foundation Realm’ consists of

the core database where the data is archived for the agreed retention period.
Data persistence stores your data in files or other non-volatile storage so that it
can be processed in batches, rather than all at once, simultaneously. Workflow
management structures the tasks (or processes) in the data pipeline and makes
it easier to supervise and manage them. Serialization frameworks convert data
into more compact formats for storage and transmission.

(e) Data analytics module. The CMMS data will be a structured and
centralized location where users can access business data. Business
intelligence is a set of methods and software used by an enterprise to

Indian Naval Ship Maintenance Authority Page 49

 aggregate, summarize, analyze, and ultimately derive value from business
data.

Standard Operating Procedures for Data Integration

8. For Existing Legacy Systems. Once the data discovery and data profiling
phase is over and the data sets to be migrated have been identified, it will be important
to carry out the following set of processes: -

(a) Requirement Specification Document.

(b) Feasibility Analysis.
(c) Architecture and Development.
(d) Management Plan.
(e) System Integration Design.
(f) Implementation.
(g) Data Cleaning and Structuring.

9. For New Systems. While any new application or information system is added
to the systems landscape then following aspects for implementation has to be taken
care: -

(a) Conform to the CMMS Data Model. The CMMS Data Model is a
holistic, enterprise-level, implementation-independent conceptual or logical
data model providing a common consistent view of data across the enterprise.
This includes key enterprise data entities (i.e., business concepts), their
relationships, critical guiding business rules, and some critical attributes. It sets
forth the foundation for all maintenance data and maintenance data-related
projects.

(b) Conform with the CMMS Data Model Flow Design. Defines the
requirements and master blueprint for storage and processing across
databases, applications, platforms, and networks (the components). These
data flows map the movement of data to business processes, locations,
business roles, and to technical components.

Indian Naval Ship Maintenance Authority Page 50

 Annexure ‘II’ to Appendix ‘A’

CMMS ARCHITECTURAL OVERVIEW

1. INSMA endeavors to provide authoritative decision support to pan-navy

stakeholders for ensuring reliability of on-board equipment/ systems and combat-
worthiness of platforms. INSMA is the repository of Operational and Maintenance data
of all equipment and systems installed on all IN platforms. This data resides on CMMS
database of which INSMA is the custodian. All platforms engage with various modules
on CMMS to render online returns, reports and raise Defect Lists through DART
module.

2. Problem Definition. Considering the quantum of data which is being

generated on CMMS, sifting, segregation, cleaning, manipulation and depiction of data
in order to facilitate almost real-time graphical visualization in order to generate
answers to queries, report generation to help in decision-making, comparison of
trends, identification of defect-prone equipment/equipment with least MTBF, prediction
of defects based on calculated MTBF of a specific equipment, etc., are considered
mandatory to aid in decision-making and policy changes. Presently Excel sheets from
the relevant modules manipulated using Pivot charts to facilitate graphic
representation and analysis. Officers and sailors who join INSMA in SUMS section are
trained upon joining this unit in CMMS and Excel. Cyclic turnover of Officers and
sailors results in loss of knowledge gained in the nuances of CMMS and analysis tools.
A need is therefore felt to develop a software application which can continually access
data from CMMS which would be amenable to manipulation, graphic visualization,
comparison, trending and feeding of queries in order to facilitate decisions. The
requirements of MAT-CDF from data acquisition, management and analysis point of
view for various agencies is covered in subsequent paragraphs. CMMS being a pan-
Navy application would feature as the primary database which would need to be
improved with UX/UI design.

3. CMMS. The new CMMS should be developed with following features

which would provide for customized, interactive dashboards for personnel in various
agencies including hierarchical login IDs for Ships crew, INSMA, Yards, FMU, MOs,
Op authorities, Command HQ, IHQ directorates, Trial Agencies, WOTs, DoI, MMTs,
etc. Each agency depending on its charter of duties and responsibilities would require
a customized dashboard from the same database in CMMS. For e.g., DFM would
require a dashboard which depicts all refits in progress, type of refits, distribution
among Commands, upcoming Refit Commencement and Completion dates, etc., with
provision to click and obtain further information on specifics from the underlying links
to D38, OCRC, Post and Pre-refit appreciation, etc. A Planning manager in yard would
also prefer to have information regarding a previous refit scope in order to plan for a
future refit without having to search for information. Tentative queries have been
outlined based on agency. These can be further developed upon by respective agency
for consolidation towards formulation of database structure. The application should
also have notification facility for DL generation and raising of FUSS, OPDEF, OPDEM,
STOREDEM and other crucial data addition in to the module. The users in Command
and other authoritative positions in Operations and Yard should receive a main in their
SSO login regarding the above mentioned data addition and generation in CMMS
application.
Indian Naval Ship Maintenance Authority Page 51
4. CMMS architecture document indicates the existing structure, however the firm
needs to work on the latest available tools existing during the development phase.

Front end

5. The front end of CMMS comprises following: -

(a) ASP.NET 4.5. The .NET Framework 4.5 includes significant language
and framework enhancements for C# (so that you can more easily write
asynchronous code), the blending of control flow in synchronous code, a
responsive UI, and web app scalability. Latest version of ASP.NET Core

(b) Bootstrap - Bootstrap is the most popular HTML, CSS, and JavaScript
framework for developing responsive websites.

(c) jQuery - jQuery is a JavaScript Library. jQuery greatly simplifies

JavaScript programming.

(d) HTML - HTML is the markup language that we use to structure and give
meaning to our web content, for example defining paragraphs, headings, and
data tables, or embedding images and videos in the page.

(e) CSS - CSS is a language of style rules that we use to apply styling to
our HTML content, for example setting background colors and fonts, and laying
out our content in multiple columns.

(f) JavaScript - JavaScript is a scripting language that enables you to

create dynamically updating content, control multimedia, animate images, and
pretty much everything else.

(g) MVC - The Model-View-Controller (MVC) is an architectural pattern that

separates an application into three main logical components: the model, the
view, and the controller. Each of these components are built to handle specific
development aspects of an application. MVC is one of the most frequently used
industry-standard web development framework to create scalable and
extensible projects.

Back end

6. The back end of CMMS comprises following: -

(a) SQL Server 2017 Enterprise Edition - Enterprise edition in 2014 is the
full featured edition of all the editions. The other editions will have some
limitations in these features. Enterprise edition has no limitation of processor
cores. It can use all the processors the server has. There is No limitation of
memory utilization per instance either.

(b) Microsoft® SQL Server® 2017 Report Builder - Report Builder

provides data visualizations that include charts, maps, sparklines, and data

Indian Naval Ship Maintenance Authority Page 52

 bars that can help produce new insights well beyond what can be achieved with
standard tables and charts. Use Report Builder to create reports and shared
datasets. Publish report parts, and then browse the Report Part Gallery to reuse
existing report parts as building blocks for creating new reports quickly with a
“grab and go” experience.

Software Architecture

7. Layering is logical separation that is implemented in an application. CMMS has

five layered architectures. The basic 5 layered architecture of current CMMS
applications is to be considered as a reference point and state-of-the-art and industry
prevalent software architecture is to replace the current architecture, if replacement
with such an architecture presents significant improvement in the performance and
maintenance of the application. The basic components of extant CMMS are as follows:
-
(a) Presentation Layer. This the UI/UX layer of the application which forms
the interface between the end user and the application. The new application
should confirm to prevalent industry standards and enhance the look and feel
of the application by utilizing the latest trends in the industry.

(b) User Interface Layer. It is software component that forms the bridge
between the end user and the database. This layer should allow the interaction
between the end user and application in a seamless and intuitive manner to
facilitate ease in input and exchange of data.

(c) Business Logic Layer. This component resided between user and the
database. It helps user to input and search for information in a manner pre-
defined at the business logic layer. This layer is also to be capable of executing
complex data analysis tasks.

(d) Data Access Layer. This layer is responsible for insertion, deletion and
basic data operations on the data storage level.

(e) Data Storage Layer. This is the physical storage.

Application Structure.

8. Application is structured in a completely modular fashion wherein any new

development can easily embrace the existing architecture without losing any
functionality. It has four layered structure: -

(a) Master Layer – This layer defines the global variables which are used
throughout the applications such as ship, equipment, department etc.

(b) Transaction – This is temporary or local variables which are specific to

a particular module. Further, this layer also allows for data transaction against
the global/ local variables within the application. Once the data is transacted it
gets validated by the Administrator before it is accepted in the database for
reporting/ further usage.

Indian Naval Ship Maintenance Authority Page 53

 (c) Report – This is user defined reports based on the way a particular set
of users demand the data.

Visualization Structure.

9. Presently, visualization theme involves the following component: -

(a) Left Menu - Displays the module names. Each module is clickable and
content opens in the body.

(b) Top Menu – Top menu comprises of the tabs for Master, Transaction,
Report, Feedback and Documentation/Help, provided for specific role based
data access/ data entry and visualization.

(c) Body – Body is below top menu and on the right of Left Menu, is primarily
used for visualization of data output of selected tabs from left/ top menu. Based
on selection the data/ forms are displayed for data transaction/ visualization.

User Authentication and Access Control.

10. CMMS has its own user authentication layer and access control matrix, based
on the same specific users get specific type of data access.

Technical Requirements – Role Based

Professional Directorates.

(a) Spare Consumption Module. OBS and B&D spares are allocated ship-
wise to facilitate demands by Ships staff or repair agency and procurement by
MOs. Since a number of equipment have been standardised, data wrt defects,
OBS/B & D spares consumed may be queried for each equipment/system in
order to facilitate update of onboard OBS allocation and B & D allocation. Extant
Ranging & Scaling allocation ship-wise may also be updated.

(b) Presentation of Equipment Reliability Based in Trends in Historic

Data. The equipment reliability module should only present data in required
format. The module should not execute any Statistical, Machine and Deep
Learning algorithms to arrive at equipment reliability. Professional Directorates
should be able to raise queries wrt specific equipment reliability drawing data
from CMMS, comparison of same equipment within same platform and different
platforms, life cycle costing based on spares consumed, comparison of the
same, etc., in order to facilitate decisions during equipment selection. Eqpt
performance data uploaded during induction trials and acceptance would also
need to be accessed in order to provide visual representation wrt life cycle
performance, number of defects, MTBF, MTTR, spares support/compliance, no
of defects prior scheduled routine, no of FUSS raised prior defects, no of SS
routines undertaken prior defects, comparison of performance before and after

Indian Naval Ship Maintenance Authority Page 54

 major routines for same equipment and same equipment fitted on other
platforms, etc.

11. Trial Agencies. Various trial agencies undertake trials during induction and
acceptance, before and after refits and in case of specific requirements.

(i) The Trial agencies should be able to track performance of

particular equipment and systems based on trial agency responsibility
such as vibration, SPM, SOAP analysis, and compare it with a baseline.

(ii) Comparison of same equipment parameters within same platform

and different platforms should be feasible.

(iii) Tracking of specific types, numbers of defects in order to facilitate

decision on ABER or major routine to be undertaken.

(iv) Extension of running hours based on historical data along with

comparison of such data with other similar equipment.

(v) Probability of occurrence of major defect based on type and

number of defects, oil analysis and vibration parameters, etc.

12. Dockyards/FMU. Refit/AMP planning and management involves various

stakeholders and variables which are dynamic thereby affecting project schedules.
Development of a Collaborative Refit Application Worksheet on the lines of Google
worksheet would facilitate capture of all refit related information by obtaining inputs
from various databases including CMMS, SDRS, central feeding of information by
stakeholders during the refit, extraction of information for refit planning, progress, and
interact with different databases including CMMS, ILMS, SDRS, WLMS and databases
of Trial agencies. Feasibility of development of a Refit Planning & Management
Application may be explored with following attributes: -

(a) The entire RPP schedule, milestones may be captured on a common

platform to provide collaboration between stakeholders including SS, INSMA,
Repair Agency (Yards, FMU), MOs and Trial agencies.

(b) Dashboards for Higher management based on refit status, forthcoming

milestones, areas requiring attention, etc.

(c) All documentation related to the refit including defect lists, FCL,
compliance, completion of tasks, achievement of milestones, minutes of
meetings, Pre-DLC report, D38, Post Refit Analysis, agenda points for RPM,
break-up of DLs and corresponding WIs leading to milestones, etc., may be
captured. Online forms would be available for various stakeholders to feed data
which can then be printed out in letter or fax format.

(d) Non-availability of particular spare to undertake a specific task may be

indicated on the application. All stakeholders would have access to information
related to SoW, related spares, time by when spares are required, when

Indian Naval Ship Maintenance Authority Page 55

 additional scope has been introduced, and acceptance of additional scope at
various levels vis-à-vis effect on refit timelines.

(e) Change to Scope of Work decided during DLC, post docking and raised
as AWRF may be captured in order to facilitate decision on re-aligning of
schedule.

(f) Each DL, WI should be mapped with corresponding requirement of

spares and the same is to be mapped to the respective DART serial on CMMS.

(g) Number of DL-I, II vis-à-vis other ships of the same class for similar refits.
This would be available from CMMS.

(h) Compliance of FCL and PDD spares as refit progresses. This would
draw inputs from ILMS and yard demands raised. Comparison with other ships
of same class would also be feasible.

(i) Completion dates vis-à-vis planned dates and percentage of closing of

Work Instructions (WIs) leading to milestones thereby providing an appreciation
of tasks completed vis-à-vis overall schedule.
(j) Based on comparison of previous similar data, available manpower,
existing loading of individual production centers, provide an estimate wrt refit
completion date, requirement to increase tasking in order to meet timelines.

(k) Loading of various production centers based on WIs issued, existing

manpower, overall loading in order to facilitate decision on offloading well
before the refit start date.

(l) Inputs from QC for various tasks would be available on the application.

(m) Costing of refits would be feasible for future analysis and provide insights
wrt overall refit costing vis-à-vis cost of offloading entire refits.

(n) The Planning Manager would have details of previous refits available
through all documents captured digitally in order to facilitate planning for future
refits. The application would draw data from various Trial agencies, CMMS,
SDRS, ILMS, WLMS and would facilitate timely preparation of pre-refit
appreciation in an objective format based on post refit appreciation of same
class of Ships.

(o) The Planning manager or COSM would also need information wrt to the
following: -

(i) Comparison between DLs raised in previous refits vis-à-vis

forthcoming refits.
(ii) Comparison between spares compliance of similar refits.
(iii) Major scope of work with time taken in similar refits.
(iv) Total list of spares consumed equipment-wise in similar refits.
(v) Total steel renewals, build-ups, paint renewals in tanks
undertaken in similar refits.
(vi) PDD spares demanded and compliance.

Indian Naval Ship Maintenance Authority Page 56

 (vii) Comparison of specific equipment defect descriptions of similar
equipment in order to facilitate actual spares requirement by production
centers.
(viii) Overall Ship and equipment performance baseline in order to
facilitate comparison of present refit data.
(ix) Specific causes of delays such as spares, dry-dock availability,
load on centers, operational loads, temporary loan of equipment/sub-
components between ships, etc.
(x) Last major defect rectification undertaken or major routines
undertaken on equipment.
(xi) Number of WIs closed prior each major milestone to facilitate refit
progress dashboard.
(xii) Pre-refit trials data to be uploaded by Trial agencies in order to
facilitate decision on final SoW, spares required and effects on refit
timelines if any.
(xiii) Status of QC of each equipment as and when each WI is closed.
(xiv) Status of pending QCs and reasons.
(xv) Feasibility to provide decision on offloading of services based on
forecast load on center which may include no number of routines,
defects, shipboard jobs.
(xvi) Demands raised wrt individual WI based on DLs raised through
SDRS would facilitate linking of spares to respective defect in CMMS.

13. Material Organizations. MOs undertake procurement based on MSL,

demands raised by Ships, Yards and FMUs through ILMS.

(a) Undertake Life cycle costing of particular equipment based on all spares
consumed during routines, defects in order to facilitate comparison and
decision-making for ABER.

(b) Comparison of life cycle costing between similar equipment and same
equipment fitted on different platforms.

(c) Track and raise suitable pop-ups based on life of rubber components
held in inventory in order to facilitate disposal.

(d) Based on number of Op platforms available for a particular year, MOs

would be able to forecast requirements of POLs, AVCAT, gases and other
consumables.

(e) System should generate a flag when number of demands being raised
by a platform for a specific component exceeds stipulated OBS allocation so
that feedback may be provided on the system to undertake analysis as to
additional requirement.

Indian Naval Ship Maintenance Authority Page 57

14. Op Authorities. Op authorities need to manage force levels vis-à-vis AMPs
and refits. AMP/SMPs are scheduled by the Op authorities based on inputs from Ship
regarding major routines due on mission-critical equipment. With the implementation
of Um2 maintenance scheduler, routines can be forecast for action in-house by ships’
crew or by repair agencies supported by spares compliance.

(a) Op authorities would be able to identify type of ships available for long
deployments based on a date range, type of major routines due on equipment,
routines to be advanced / deferred in order to meet scheduled Op commitments
along with actions required by repair agencies and MO.

(b) Depiction of a slider chart depicting various platforms of similar

capabilities which allows selection for various Op tasks.

(c) These charts would obtain inputs from the updated maintenance
scheduler of various platforms and put forward tentative platform availability for
a specific date range in the future.

(d) The final schedule can be utilized to provide a forecast for repair
agencies and MOs to prepare for forthcoming routines wrt contracts and spares.

Indian Naval Ship Maintenance Authority Page 58

15. INSMA. As part of analysis, INSMA and various agencies need answers
to questions for which historical data, human knowledge is relied upon. A Naval Officer
is faced with many such situations wherein answers to queries would not be
immediately available or not available in the format required. A Planner at Dockyard,
Staff at Headquarters, Directors and Joint Directors at IHQ need access to such data
with speed, accuracy and quantity. Certain queries are listed under various heads.
These may be expanded upon in due course.

Technical Requirements.

16. Develop 30-35 Modules in CMMS for user transactions.

17. Import existing data into the new CMMS application. Existing data to be cleaned
of any anomalies.

18. Schema integrity in terms of uniqueness, singular and universal format of

primary keys is to be ensured and proper mapping of Primary Keys to the Foreign
Keys is to be implemented.

19. Create Data dictionary.

20. Create Entity Relation (ER) diagram. ER diagram is to be more exhaustive with
relationships of each and every table clearly mapped. This is to be undertaken future
up-scaling operation whether horizontal or vertical.

21. Publish CMMS manual in soft copy.

22. E-Documentation for recording changes.

23. Audio visual training aid on CMMS and data analytics for users, training
establishments.

24. Deploy data analytic use case and NETRA.

25. NLP or extant Large Language Model based Chat Bot “CMMS Assistant” for
answering user queries.

26. Feedback from users to be added for all users and which can be seen only by
admin users and the same can be amended in next patch or provision to amend the
same should be provided.

27. CMMS Offline Module. Offline module for CMMS Application with following
features: -

(a) Centrally deployable onboard ships in remote mode or by downloading

from CMMS website or portable Hard-drive/DVD.

(b) Capability to push and install updates/patches centrally from backend

without user being involved.

Indian Naval Ship Maintenance Authority Page 59

28. Visualizations/User Interface. Provide role-based dashboards with
Command/Op Authority/Class/Ship wise drill down comprising following displays: -

(a) CMMS Login page to include INSMA organization, contact details,

information/bulletins help files etc as specified by user.

(b) CMMS Dashboard comprising of: -

(i) Shortcuts to important reports.
(ii) Department wise pending DARTs, Routines, OPDEF, FUSS,
CANDEF,CANDEM
(iii) Prompts for upcoming Major Routines from UM2 & SRAR. Ships
can select which equipment to be prompted. A calendar to be made in
dashboard to shown routines on each day/week/month upon
clicking/selecting the day or week (akin to Outlook calendar).
(iv) Prompts for RPP deadlines.
(v) Countdown for next Refit/AMP.
(vi) Key performance indicators like EEF, GUF, FPT etc.
(vii) Running Hours of SRAR equipment.

(c) Standardized drop-down menu for various forms for selection by SS eg

symptom/defect description in DART module. Details will be provided by
INSMA.

(d) Send mail alerts to users on Outlook for pending actions.

(e) Incorporate features of EMAPs into CMMS.

(f) Digital log book for recording parametric data.

(g) Digital signatures of users feeding data into CMMS.

28. Analytics and visualizations. Analytics with facility to drill down

Command/Op Authority/Class/Ship wise and Year/Month wise with date range.
Downloadable graph and table options to be included. Following envisaged: -

(a) All existing individual reports under each module are to be combined
with drill down feature for extraction of specific reports.

(b) Feature for selecting any field in X and Y axis for generating customized
reports.

29. Scalability. Following envisaged: -

(a) Integration with the modules created as part of MAT CDF, HR CDF &
Acquisition CDF.

(b) Integration with SDRS application of Naval Dockyards.

Indian Naval Ship Maintenance Authority Page 60

 (c) Inclusion of Additional Modules as when directed by IHQ.

(d) Integration of Data Analytic Use Cases and NETRA with upgraded
CMMS application.

(e) Integration with IPMS onboard ships through CMMS Offline Module for
parametric data capture.

30. Forecasting and Scheduling. Following forecasting and scheduling actions

envisaged: -
(a) Naval Equipment Maintenance Forecast (NEMF) Module
(b) Unified Maintenance Management System (UM2) scheduler
(c) AMP forecast from UM2
(d) Refit Planning Program (RPP) module
(e) Op Cum Refit Cycle (OCRC)
(f) Defect prediction based on pattern recognition leading to OPDEF.

31. Automated Reports and Data Display. Following reports and actions are to
be automated: -
(a) Generation of INSMA Annual Reports Vol 1 and 2
(b) SFD code allocation
(c) Defect List generation from UM2
(d) Fetching spare lists from ILMS and WLMS
(e) Exporting Defect lists to SDRS and pulling final DL along with remarks
and status from SDRS.
(f) MAINTOP processing.
(g) Defect Analysis.
(h) Equipment Life Cycle milestones.
(i) Spare consumption and compliance.
Analytical Requirements

32. OPDEFs/ DARTs.

(a) Max OPDEFs on which equipment/ Which location? Which serial

number? Which Ship? After how many Running Hours or calendar months post
installation or major routines? No of fits and applicable MT.

(b) Was OPDEF raised during extension of RH? Was FUSS outstanding on
equipment at time of OPDEF?

(c) Last major routine undertaken at which RH (e.g., 6K routine undertaken

at RH of 6500 hours); Next major routine due [after ___Hours] [after __months].

(d) Major cause of OPDEF/Component which failed. Previous DARTs /

OPDEFs/ Defects on same equipment –which /component? Identify repetitive
component failure.

(e) How many of these equipment fits (out of total) have faced OPDEFs in
past?
Indian Naval Ship Maintenance Authority Page 61
 (f) Which ship has raised maximum OPDEFS? Has same equipment
location wise on same ship encountered similar OPDEFS in past? Which ships
have not faced these defects or OPDEFS?

(g) Comparison between equipment which faced OPDEFs & those which
didn’t using above attributes – when, FUSS, extension major routine, pattern,
routine due.

(h) Way ahead recommended based on visual depiction and analysis

(i) Routine amendment
(ii) Change periodicity
(iii) OEM input – design change, quality improvement, etc.

(i) Identify component repetitively not supplied / made good by yard / ship
(pattern no), Manufacturer to be identified.

(j) Generate a chart of different types of defects (color coding resulting in

downtime) in order to identify defects cluster before a major routine [RH input
from SRAR].

(k) Inputs from Trial agencies for OPLR with respect to Vibration
parameters, Op parameters, SOAP analysis, SPM, insulation, temperature
valves at time of OPDEF [A table in CMMS/ OPDEF module accessible to SS/
Trial agencies to input data related to OPDEF including last 100 hours
parametric data.

33. Maintops.

(a) Compare routines in MT for equipment manufactured by different OEMs

e.g. DAs, compressor, ACs steering gear (radar) stabilizers, radars (motors),
controls, HRU, gearing with recommendation to include best routine from
equipment with least defect, best component, best O-ring, gaskets, oils,
periodicity, etc.

(b) Impact analysis post change in MT routine or periodicity.

34. STOREDEM /OPDEM/ CANDEM.

(a) Generate consumption pattern as an input towards Defect Prediction

Module (based on DART, OPDEFs) (covered previously). Identify component
repetitively demanded, issued with manufacturer details with view to re-assess
& promulgate improved QRs.

(b) Generate 10Y data on respective STOREDEM / OPDEM/ CANDEM to

identify most demanded items.

(c) STOREDEM compliance for OPDEFs (pattern numbers of terms not

supplied repeatedly).

35. Defect Prediction Applications.

Indian Naval Ship Maintenance Authority Page 62

 (a) CMMS holds equipment defect and routine data entered by SS on a
specific date and time. RH where relevant are also available from SRAR on a
monthly basis. Similar equipment are fitted on other platforms thus increasing
the population and the database.

(b) Based on DART, OPDEF, SRAR data, a worksheet needs to be

developed in Excel in order to facilitate plotting the various activities (DARTs,
routines, OPDEFs) which occur on a single equipment over a timeline or RH
where applicable. The database needs to be studied and software as applicable
is to be developed in order to be able to predict next failures with some
probability.

(c) Towards this, use of NLP along with key word search to identify and
segregate defects/failures from other activities would also be required to
cleanse the database to be analyzed.

(d) Use of tools in MS Excel such as Weibull Distribution, CA(Crow-AMSAA

analysis) to predict Mean Time to Failure and to facilitate defect prediction to
be in-built into the application. Other commercially available open source
techniques to be employed for defect prediction module.

36. Eqpt Life Cycle Module.

(a) An application to generate a spreadsheet for each equipment code

between a date range. Input from SFD, SRAR, OPDEF, DART, STOREDEM,
OPDEM, CANDEM, FUSS in order to generate a life cycle timeline of defects,
OPDEFS, routines. The spreadsheet will draw inputs for all similar equipment
(with same equipment code) fitted on various platforms.

(b) Since installation, STW, Trials – RH be calculated up to first defect

necessitating change of consumables (O-ring, gaskets mechanical seal /
bearings life 3-4Y) with provision to predict/recommend next change. OPDEFs
& major defect from DARTs to be linked with RH / calendar date from SRAR in
order to predict future failures of consumables - O-ring/ gasket / bearings

(c) Any data input in CMMS such as routines undertaken by SS, Yard or
DART/OPDEF to show up on chart. This would facilitate comparison of
equipment performance between similar equipment on different ships for e.g.,
type of defects causing downtime of radar segregated between turning motor
and antenna/transmitter/wave guide, etc. This would facilitate conjoining of
routines of radar antenna and the motor/panel etc., to ensure reduction in
downtime due to either of these components.

Indian Naval Ship Maintenance Authority Page 63

 Annexure ‘III’ to Appendix ‘A’

TECHNICAL DETAILS OF DATA ANALYTIC LAYER

1. Architectural Features.

Ser Specifications
(a) Solution should provide configurable automated batch loading of the source data
into the target systems (CMMS DC and Offline Module) as per the pre-defined
intervals. Should have ability to integrate with real time data ingestion systems to
enable future development needs.
(b) The solution should be compatible with both Windows and Linux operating
systems
(c) Solution should leverage the open source technologies in the market
(d) Solution should be Scalable to allow Minimal down time future upgrades and
should be supported in clustered environment and should support Open source
frameworks such as Hadoop etc.
(e) The existing 30-35 .Net based CMMS modules are to be developed using the
Micro services Architecture wherever applicable and should be integrated with
the existing Architecture.
(f) Solution should be able utilize the rapid prototyping tools available in open source
model to standardize the processes implemented wherever possible
(g) Solution should be enabled to use the Containerization for optimized resource
utilization - As applicable
(h) The solution should have the ability to use In-Memory Analytics to enable users
to conduct Fast, Thorough Explorations and Analysis on data from different data
sources across the Enterprise
(i) The solution should provide Scalability and High Performance leveraging cost-
effective architecture

2. Data Management Features.

Ser Specifications
(a) The solution should have Metadata driven data ingestion
(b) The solution should have an ability for event-driven Change Data capture
framework and should be able to ingest batch data
(c) The solution should demonstrate a CI/CD (Continuous Integration and
Continuous Delivery) framework for automated DevOps
(d) Containerized execution for automated scale-in & out
(e) The solution should be able to seamlessly call Data Quality processes as a web
service for de-duplication, as part of the ETL process flow
(f) The ETL tool should provide for Multiple-user design environment with a
governance mechanism to prevent corruption of data integration related
objects, and also supports collaboration on large, enterprise wide projects.
(g) The solution should generate code for ETL process flows created through the
GUI which can be viewed / edited by the developers if required

Indian Naval Ship Maintenance Authority Page 64

 (h) The solution should provide the ability to create User Written Code
transformations, which allows leveraging custom code as part of the ETL
process flow
(i) The solution should provide a single metadata repository which provides the
ability to track data lineage by performing impact and reverse impact analysis
visually, through a graphical user interface
(j) The solution should have the ability to perform complex search (based on object
name, type, date range etc.) of the metadata repository and should also be able
to save search criteria for reuse
(k) The solution should have the ability to easily capture and display performance
information such as real time, CPU time, memory use, input/output, and record
count data as a table / graph
(l) Solution should be designed in such a way to accommodate the Real time data
ingestion (future requirement) can be integrated without disturbing the existing
Batch Model ingestion.
(m) Data Profiling and Fallout reporting should be part of the solution implemented.
(n) Automatic reporting of anomalies in data entered in the form of alarm /
notifications. Owing to human error while data entry, an alarm or notification
may alert the Database Administrator to take corrective action in form of alerting
the end user if available or discarding the value in final data.

(o) Data Standardization in the Common Data Platform level should be supported.
(p) Data Enrichment in the Common Data Platform level should be supported
(q) Data Compression and Indexing for federated search/querying should be part
of solution implemented
(r) ABC- Audit, Balancing & Control with email based Alerting should be part of the
solution
(s) The ETL tool should provide connectivity to Industry leading RDBMS like
PostGre, ORACLE, DB2, SQL Server, Sybase, MYSQL, appliances like
Netezza, Teradata, etc and Big Data Storage Platforms like Hadoop using Open
source Connectors such as Maven
(t) ETL tool used should be able to use SOAP as well as REST sources
(u) Hadoop Integration should be part of the implemented solution
(v) Utilizing Spark Computational Capabilities wherever applicable
(w) Data Standardization or Enrichment features such as Data De-Duplication,
State & City standardization should be part of the ETL processing stages
(x) The solution should allow manual as well as automatic ETL configuration
development to speed up development activities
(y) The ETL Solution should allow Custom transformation development and
integration with the existing system without any modifications to the existing
implementation
(z) The ETL tool should be capable of executing Native DB Procedures such as
PLSQL of ORACLE or TSQL of MSSQL and then perform the extraction as
required
(aa) The solution should have the ability for Command-line job deployment options
for deploying single and multiple jobs
(bb) The solution should provide the ability to execute external OS level commands
such as call shell scripts as part of the ETL process
(cc) Sufficient logging should be provided to identify the progress as well as cause
of failures.
Indian Naval Ship Maintenance Authority Page 65
(dd) ETL operations should be rule driven where a one or more rules can be enabled
or disabled before trigger the process.
(ee) The solution should provide the capability to create data profiling reports in the
form of pie charts, bar graphs etc
(ff) The solution should provide the capability to drill through to source level
information in the data profiling report
(gg) The solution should perform the data quality functionalities without creating a
copy of the data in a proprietary/external format
(hh) The solution should have the ability to correct mistakes in spellings,
inconsistencies, casings and abbreviations
(ii) The solution should provide safe string encode/decode capabilities
(jj) The solution should provide a unified capability and system for both offline and
online
(kk) The solution should have the capability to provide fuzzy logic to induce
tolerance during matching
(ll) The solution should have the ability to have options for automatic merging of
clustered records
(mm) The solution should have the capability to enrich data from internal data sources
(nn) The solution should have the capability to enrich data from external/third party
data sources
(oo) Well defined audit trails should be created as a part of the Data Management
activity
(pp) System should have the capability to set alerts
(qq) The solution should be capable of handling duplicates in batch jobs

(rr) The solution should have a conversational interface / chat-bot module with:
 A front-end chat interface or dashboard to access all features of the
converser.
 Ability to interact through voice or text inputs.
 Ability to connect with 3rd party applications approved by navy using
APIs
(ss) The chat-bot module should have a Query-based search
 Ability to handle various types of queries such as:
o Selection
o Filter
o Grouping & Aggregation
o In-built functions
o Operators
 Ability to bookmark the Search Query for reference
(tt) The chat-bot module should have guided search features:
 Query suggestions feature to suggest queries while the user types
 Related Queries feature to suggest other similar queries that the user
might be interested to search
 Ability to define Synonyms for the search terms
 An algorithm to identify and add other interesting data points to the
query result (“Ships ready in eastern part of country” would also bring
data for “for all eastern ports” )

Indian Naval Ship Maintenance Authority Page 66

(uu) The chat-bot module should have Document search
 Document Search feature to search and produce data from documents
(.docx, ppt, pdf etc.)
 FAQ based query support
(vv) Context retention
 Ability to retain the Context of the query to the subsequent queries
 Ability to quickly change one entity in the search query for quick
reference
(ww) Ability to identify the Entities and show different color coding for the same

3. Draw Insight Features.

Ser Specifications
(a) Analytics Sandbox Governance and Optimization - CI/CD etc.
(b) The tool should go beyond BI and be an autonomous monitoring system
(c) The solution should help identify anomalies faster
(d) The solution should identify the right root causes for anomalies
(e) The solution should support unsupervised anomaly detection.
(f) The solution should link actionability across multiple functions
(g) The solution should monitor complex hierarchies, dimensions and hierarchy X
dimensions
(h) The solution should allow users to change queries by selecting items to be
displayed from a sidebar or dynamically filtering and grouping
(i) The solution should provide viewable descriptive statistics, such as min, max
and mean, enabling users to gain an overall sense of a particular measure
(j) The solution should provide the capability to link to an external URL from a
visual object with relevant context
(k) The solution should allow 'On-the-fly' hierarchy creation for adding drill-down
capabilities to visualizations and reports
(l) The solution should provide capabilities to Slice and dice multidimensional data
by applying filters on any level of a hierarchy
(m) The solution should provide capabilities to Drill up and down through
hierarchies, or expand and collapse entire levels
(n) The solution should provide a data acquisition wizard for previewing, filtering
or sampling data prior to creating visualizations or reports
(o) The solution should provide selection and brushing modes for discovering
relationships while exploring data
(p) The solution should provide users the capability to save and share their
analysis as exploration, report, or PDF
(q) The solution should provide the capability to export data to Excel, PDF, Text,
JSON and CSV/TSV document formats
(r) The solution is capable of emailing a report link with comments to users
(s) The solution should provide progressive filters. This refers to cascading
relation between filter controls in the report body with bi-directional filters.
(t) All users should have access to all capabilities of the solution platform and
should not be restricted by way of licensing
(u) The solution should allow user controlled rendering of visualizations

Indian Naval Ship Maintenance Authority Page 67

(v) Solution should support extension of Visualization library using third-party
visualizations by building D3.js graphs, etc. and embedding into Reports and
Dashboards
(w) The solution should be capable to schedule & distribute reports/dashboards
(x) The solution should provide Self-Service platform without the need to build a
semantic metadata layer for End users, thus reducing dependency on IT
(y) The solution should support Outlook Integration with full interactive reports,
gadget panes
(z) The solution should support SharePoint Integration with full interactive reports
(aa) The solution should support Excel integration with ability to leverage native
Excel charts
(bb) The solution should have capability to monitor Resource utilization including
CPU, I/O and Memory
(cc) The solution should have capability to monitor User sessions
(dd) The solution should provide ability to Refresh reports from the device from
browser
(ee) The solution should provide server side logging for user actions – reports
downloaded: custom build
(ff) The solution should have usage report and audit report
(gg) Single environment for interactive data exploration and analytical modelling
capabilities to quickly identify predictive drivers and build descriptive and
predictive models using state-of-the-art statistical, machine and neural network
learning models.
(hh) The solution should have the capability of covering wide range of
anomaly/pattern detection such as: -
 Point Based Anomaly
 Trend Detection
 Trend Change Detection
 Level shift Detection
 Monotonic Pattern
 Change in Distribution Detection
 Peer anomaly detection
(ii) A reconciliation module that enables consistency at multiple levels (Ex:
Command, Class, Ship, Port) & can drive harmony between long term & short
term forecasts
(jj) Inventory algorithms integrated with forecasting to calibrate stock norms
through multiple simulations, project inventory & provide constrained forecasts
(kk) Workflows to capture assumptions of planners, enable planners to simulate,
override forecasts & collaborate
(ll) Control tower to
a) Sense demand, driver changes
b) Monitor forecast “trust index” at multiple hierarchies & stages, to provide
alerts on exceptions
(mm) A feedback layer to continuously improve the algorithm accuracy
by incorporating planner efficiency metrics and
(nn) Simulation-based Inventory Setting
(oo) Advanced Text Analytics using frameworks like -> BERT, ELMO, GPT4 or any
advanced versions, Transformer, Encoder Decoder, etc: python-based
framework for classification of defects up to sub-assembly level.
Indian Naval Ship Maintenance Authority Page 68
4. Analytical Features

Ser Specifications
(a) The proposed solution should combine data wrangling, data exploration,
visualization, feature engineering, and modern statistical, data mining and
machine learning techniques in a processing environment
(b) The solution should have a Model Lifecycle Management
(EDA>FE>TRAIN>TEST>EVALUATE>DEPLOY)
(c) Model Monitoring/Tuning & retraining (Perform monitoring based on system
logs and Model Performance parameters as defined) with Alerting: python
based framework
(d) The proposed solution uses natural language processing (NLP) to analyse and
transform text into formal representations for text processing and
understanding. This includes automated text parsing, word and sentence
tokenization, segmentation, stemming, compound decomposition, synonym
detection, part-of-speech tagging, categorization documents, named entity
recognition and semantic parsing. It should also directly support the use of
regular expressions (REGEX) for matching purposes. The application should
be able to undertake Similarity Analysis to ascertain whether two DART’s are
similar with respect to nature of defect.
(e) The proposed solution should have Smart search applications by categorizing
documents, associating entity relationships and building a contextual search
application for exploration within text, using machine learning and semantic
analysis
(f) The proposed solution should combine machine learning with business
knowledge to generate new rules for improved accuracy.
(g) The proposed solution should provide automatic discovery of topics for initial
taxonomy development: -

• Automated machine discovery identifies the core themes in the input

document collection with associated relevance scores.

• Term relationships within topics can be interrogated and explored with term
clouds (with configurable thresholds), interactive term maps and by drilling into
topics to evaluate relevancy and refine discovered topics.
(h) The proposed solution should employ sophisticated dimension reduction
techniques that enable advanced filtering through weighting, integrated spell
checking and transformation of qualitative data into compact formats.
(i) The solution should provide capabilities to view Entity relationships in Network
Plot and allow drill into details to explore relationships and define strength of
relationships
(j) The solution should have the ability to build Flow Diagrams for Path Analysis
(k) The solution should provide enhanced forecasting capabilities with Scenario
Analysis i.e. It allows users to see how the forecast would be effected by
changing independent variable values
(l) The solution should provide a clear explanation of Analytical results by
providing “What does it mean” capabilities
(m) The proposed solution should provide collaborative environment which
enables easy sharing of data, code snippets and best practices
Indian Naval Ship Maintenance Authority Page 69
(n) The proposed solution should be able of highly scalable, analytical processing
for distributed, processing of complex analytical calculations on large datasets
(o) The proposed solution should have built-in failover management guarantees
submitted jobs always finish

Indian Naval Ship Maintenance Authority Page 70

 Annexure ‘IV’ to Appendix ‘A’

LIST OF BOOKS AND RECORDS

1. Documentation. Understanding and documenting the system specifications,

that describe in detail the envisaged purpose of the application, and the details of its
implementation is very important as it forms the foundation for the risk assessment
and management processes that follow it.. These documents have to be prepared in
soft copy also to put it in the Documentation Module of CMMS, in the similar structure
of CMMS documentation. Various documents to be prepared as part of the project is
covered in subsequent paragraphs.

2. System Specifications. System Specification document that lays down the

purpose and broad technical specifications of the system to include the following:-

(a) Purpose of the cyber system and its linkages with mission/mission
support assets.

(b) Map/ chart/ topology of all physical facilities indicating entry points and
networks.

(c) Logic diagrams, data-flow process and dependencies on external

systems.

3. Patch Update Management. This Document discusses the steps required to

implement a successful security patch management solution which can be used to
help protect the enterprise. Patch management is about mitigating risk to the
confidentiality of your data and the integrity of your systems. Patch management can
be the most effective tool used to protect against vulnerabilities and the least
expensive to maintain if implemented effectively. The objective of this document is to
describe the patch management processes and procedures performed.

4. Change Management. The purpose of this document is to define a formal

process for performing any change process. The process includes the steps involved
including asset identification, scope for change, requester, approver, implementer
including release process. The document covers procedures to be adopted when any
change is incorporated but not limited to operating systems, network configurations
and hardware changes. It will cover all aspects of change from request to
implementation.

5. User Manual. The User Manual should provide an easy to use procedural
view of each page, click by click with a pictorial view. In addition the user manual is to
be made in a video form too for the user to easily assimilate the written material.

Indian Naval Ship Maintenance Authority Page 71

6. Technical Manual. The Technical manual should intend to provide details of
various aspects of the CMMS Application and the system architecture, with regard to
trouble shooting and system setup. This document would be a reference point to
administrator and technical staff maintaining the CMMS Application and related
servers. The CMMS Technical manual documents the various components on the
CMMS Application Server and CMMS Database Server, the deployment view, various
scheduled jobs that form a part of CMMS processes, installation and configuration
information. A set of Annexures following the document provide with supplementary
information for the administrator.

7. Administrator Manual. The Administrator manual defines the process and

steps to be taken by an admin in day to day activity to monitor, modify and resolve the
admin related activity/issues.

8. Risk Assessment Document. The document should consist of the following

types of risks:-

(a) Risk to organizational operations (including mission, functions, image or

reputation)

(b) Risk to organizational assets.

(c) Risk to individuals

(d) Risk resulting from the operation of organizational information systems

and the associated processing, storage, or transmission of the organizational
information.

9. Risk Mitigation Plan. Risk mitigation plan should consist of the following steps
to mitigate the risks as mentioned in the Risk Assessment Document: -

(a) Access Control. Define the authorized users, processes acting on

behalf of authorized users, devices and the types of transactions and functions
that authorized users are permitted to exercise.

(b) Audit and Accountability. Defined procedure to maintain the audit

records, needed to enable the monitoring, analysis, investigation, and reporting
of unlawful, unauthorized, or inappropriate information system activity.

(c) Certification, Accreditation and Security Assessments. Define

process and periodicity to assess the security controls in organizational
information systems to determine if the controls are effective in their application.
Develop plan of action designed to correct deficiencies and reduce or eliminate
vulnerabilities in organization information systems.
Indian Naval Ship Maintenance Authority Page 72
 (d) Configuration Management. Prepare a configuration Management
plan to establish, maintain, and effectively implement plans for emergency
response, backup operations, and post disaster recovery for organizational
information system, to ensure the availability of critical information resources
and continuity of operations in emergency situations.

(e) Incident Response. Define process to establish and operational

incident handling capability that includes adequate preparation, detection,
analysis, containment, recovery and user response activities, and track,
document & report incident to appropriate authorities.

(f) Maintenance Plan. Plan to effectively perform periodic and timely

maintenance and provide control on the techniques, tools and mechanisms for
personnel used to conduct the maintenance.

(g) System and Information Integrity. Procedure to identify, report, and

correct the flaws in a timely manner, provide protection from malicious code,
monitor alerts and advisories and take appropriate actions in response.

10. Cyber Security Policy. Prepare System-specific Cyber Security Policies as

per guidelines provided by Navy to include the following:-

(a) Access control and physical security requirements.

(b) Configuration control to ensure systematic and authenticated alteration

to system parameters.

(c) Process for acquisition of hardware and software.

(d) Mechanism for patch and update management of the operating system,
third-party applications, device drivers and control modules.

(e) Methodology for accounting inventory.

(f) Roles and responsibilities.

(g) Periodicity for conduct of Vulnerability Assessments and security audits.

11. Standard Operating Procedures. Prepare precise, unambiguous and detailed

SOP based on the system specific policy to address all security aspects during
operation and maintenance of the system. Essentially the SOPs translate the system
specific security policies into actionable processes with clear indication of who is to do
what, where and when. In addition, the following are to be included in the SOPs:-

Indian Naval Ship Maintenance Authority Page 73

 (a) Assign and record specific responsibilities with respect to accounting
and security of all IT components of the system.

(b) Document the procedure for testing of new changes/ amendments

before introducing it in live systems and phasing out of the old software
component.

(c) Implement mechanisms to maintain logs of administrators to enable

track-back in the event of a security incident.

(d) Create incident response management plan with CIRT-Navy, SI.

(e) Stipulate chain-of-command for incident reporting and response.

12. Deliverables.

Ser Items Number required

(a) Project plan 02 Hard Copy
(b) Restoration and Backup CDs for the system 01 Set each
software
(c) Documentation with respect to Customised 02 Hard Copies, 01 Soft
application Copy

(d) Training Course material (If any) 20 trainees, one per

trainee and three spare
copies

(e) Copy of CBT package as per IETM level 3 02 Copies

standards(Separate for Administrator and
Buyer) and Tutorial for the application
(f) Copy of Source/customisation code of the 02 Copies
application
(g) Quality Acceptance Plan, Acceptance Test 02 Copies
plan, Acceptance Test Schedule
(h) Documentation, Media and License for the 01 Set each as per the
software software. Including OEM
support certificate in
accordance with para19
of part IV of RFP
(i) Certificate of authenticity for the Software 01 copy each

(j) Consolidated BOM containing complete 02 Copies, one soft copy

information on the installed components with
Manufacturer’s Part No, quantities used,
numbering scheme used, colour codes etc

(k) Warranty certificates from OEM. 01 set

Indian Naval Ship Maintenance Authority Page 74
 (l) Configuration Documents (for servers, switches 02 Sets
and active components)

(m) Malicious code certificate 01 original ink signed

copy
(n) Brochures for the application 02 copies

Indian Naval Ship Maintenance Authority Page 75

 Annexure ‘V’ to Appendix ‘A’

INFORMATION SECURITY REQUIREMENT

Identification and Authentication Mechanism

1. Applications must have robust authentication mechanism. Authentication

should be based on at least one of the following mechanisms:-

(a) Strong Password (minimum eight character length and should be a

combination (at least three) of upper case letters, lower case letters, special
characters and numbers).

(b) X.509 certificates issued for the host/client (Using approved PKI system
as and when available) (something you have).

(c) Biometrics (something you are).

2. The authentication may use a user account database specific to the application
or it may involve leveraging the authentication service of an operating system or
directory service.

3. In case the authentication to an application is based on passwords, then the

standard password policy is to be promulgated for all and should be adhered to.

Data Protection

4. Data Protection at Rest. Sensitive application data must be adequately

protected in rest and appropriate file permissions must be applied. As and when
applicable the data at rest must be in encrypted form.

Audit Features

5. The audit facility of the application must be configured to log all relevant events.
The mechanism that performs auditing may be a combination of the operating system,
web server, database, application, etc. The following are recommended for
logging/auditing in an application:-

(a) Startup and shutdown of application.

(b) Authentication of clients/users.

(c) Authorization/permission granting including starting and ending time for

access to application.

(d) Actions and access to data by trusted users.

(e) Process invocation.

(f) Unsuccessful data access attempt and Denial of access resulting from
excessive number of login attempts.

Indian Naval Ship Maintenance Authority Page 76

 (g) Data deletion.

(h) Changes in configuration of application.

(i) Application of confidentiality or integrity labels to data and any changes

to these.

(j) Override or modification of data labels or markings.

(k) Output to removable media.

(l) Output to a printer (for confidential data only).

(m) Privileged activities and other system level access – For

applications/systems dealing with confidential and higher data.

(n) For applications/systems dealing with confidential and higher data,

activities that might modify, bypass, or negate safeguards controlled by the
system.

(o) Successful or failure of attempt to access a security file. 31

(p) Blocking or blacklisting a User lD, terminal, or access port, and the
reason for the action - For applications/systems dealing with confidential and
higher data.

6. The following information pertaining to the events should be logged: -

(a) User lD of user or process ID of process causing the event.

(b) Success or failure of attempt to access security file.

(c) All data entry into the system to be logged and attached with a time
stamp (events of raising DL, FUSS, OPDEF etc.).

(d) Date/time of event.

(e) Type of event.

(f) Success or failure of event.

(g) For identification and authentication events; origin of request (e.g.

originating host’s IP address).

(h) For write or delete events: name of data object written or deleted.

7. It is recommended that the application must have a mechanism for warning the
administrator, when the audit records are near full. The application audit records must
not be vulnerable to unauthorized deletion, modification, or disclosure.

Indian Naval Ship Maintenance Authority Page 77

8. The application developer must also ensure a process is in place for retaining
application logs for the specified period.

Session Limits for Applications

9. In addition, session limits must exist for the application. For each session type
there must be limits on the number of sessions per user or process and the maximum
time length of an idle session. Alternately, limits could be set on the aggregate number
of sessions or the length of time of any session (active or not). Even if the application
does not provide time limits for idle sessions, such limits may exist at the transport
layer (e.g. TCP timeouts). The details to be mutually arrived at during URS/SRS.

Marking of Security Classification

10. While developing applications, the printed output from the application is to have
appropriate security classification. This would facilitate proper handling of the
information. In some cases technology may prohibit the appropriate markings on
printed documents. For example, in some cases, it is not possible to mark all pages
top and bottom when a user prints from a browser. In this case, user procedures must
exist for manually marking printed documents.

11. Need for role based access control and recommendations for segregation of
roles are to be incorporated. The application must not store authentication credentials
on client computers after a session terminates. Persistent cookies are the primary
means by which an application stores authentication information over more than one
browser session. If the application is a web-based application, browser must be set to
warn the user before accepting a cookie.

12. Application users must be given an option to explicitly terminate a session

(logout).

Mobile Code

13. Mobile code is software obtained from remote systems, transferred across a
network, and then downloaded and executed on a local system without explicit
installation or execution by the recipient. Mobile code could be any of the following
types: -

(a) ActiveX (b) Windows Scripting Host when used as mobile code (c) Unix Shell
Scripts when used as mobile code (d) DOS batch scripts when used as mobile code
(e) Java applets and other Java mobile code (f) Visual Basic for Applications (VBA)
(g) LotusScript (h) PerfectScript (j) Postscript (k) JavaScript (including Jscript and
ECIVlAScript variants) (l) VBScript (m) Portable Document Format (PDF)

14. Following are to be borne in mind in case of developing applications using

mobile code: -

(a) The application should not be developed with the ability to send e-mail
messages that include executable code. If the application sends emails, the
messages must not contains files with the extensions .exe, .bat, .vbs, .reg, .jse,

Indian Naval Ship Maintenance Authority Page 78

 .js, .shs, .vbe, .wsc, .sct, .wsf, .wsh. Similarly, the application must not transmit
unsigned mobile code.

(b) The application must not transmit mobile code that attempts to access
local operating system resources or establish network connections to servers
other than the application server. If the application accepts inputs, the
mechanism that is used to process the request must be documented to ensure
that before mobile code is executed, its signature must be validated.

(c) In case the application allows upload of data, the data file should be
parsed to look for specific pieces of information in an expected format. In case
of anomaly, a suitable error message should be provided and such upload
should not be permitted. An application program in accordance with established
business rules must then process the data. The data file must not be sent
directly to an execution module for processing.

(d) Data Validation and Error/Exception Handling

15. The application must adequately validate user inputs before processing them.
The test plan for the application must document testing with invalid user inputs and
tests for boundary conditions.

16. The application must include an explicit error and exception handling capability.
Application error and exception messages displayed to users must not reveal
information that could be utilized in a subsequent attack. Error messages should not
include variable names, variable types, SQL strings, or source code. The application
code should not rely on internal system generated error handling.

17. An application failure must not result in an insecure state of the system. An
application process must remove temporary objects from memory or disk before it
terminates.

18. Buffer overflow vulnerabilities are one of the most common security flaws. The
application development must ensure that it is not vulnerable to buffer overflows. This
must be documented in the test plan.

19. Applications being used on the Naval intranet should display an appropriate
warning message upon user logon. The warning message does not need to include
the following four general elements verbatim but must convey the same meaning:-

(a) Notice that this is an IN system.

(b) Use of the application is limited to official IN use only.

(c) Unauthorized use is subject to prosecution.

(d) Use of the application constitutes the user’s consent to monitoring.

20. Authentication credentials or sensitive data must not be stored in the application
code. Application code must also not contain invalid references to network.

Indian Naval Ship Maintenance Authority Page 79

21. Any data being transferred across systems must be properly labelled and the
user notified of this fact. Any interface, such as a link or web hyperlink contained within
the application, that connects to an un-trusted system must provide some disclaimer
or notification to the users that they are leaving a trusted resource.

22. Application users must be given an option to explicitly terminate a session

(Logout). Also in case of web based applications a prompt may be given to the user
to close the page/browser on logging out.

23. On logging on to applications, a feedback must be given to the users when he

had last logged into the application.

Indian Naval Ship Maintenance Authority Page 80

 Appendix ‘B’

TECHNICAL COMPLIANCE MATRIX

Sl Parameters Reference of Complies If Yes

No RFP (Part IV with RFP Para ref.
Annexure ‘A’) (Yes/ No) in T bid

Para
1. Objectives of Proposed Systems and
Schedule of Requirements
2. Basic Components of CMMS
3. Broad attributes of the
Comprehensive Maintenance
Management System (CMMS)
4. Security and Authentication
5. General Information

6. Additional Features
7. Broad Development Guidelines
8. Dev-Sep Ops
9. Hardware Requirements
10. Software License Agreements
11. Resource Requirements
12. Development Environment
13. Baseline Software for Development
14. Monitoring and Maintenance App
15. Project Execution Plan
16. Preparation of Project Execution Plan
17. Preparation of Project Development
Plan
18. Resource Requirement
19. Development Environment
20. Prepare Data Collection Environment
21. Prepare Data Modelling and Analytics
Environment
22. Prepare Hosting Environment
23. Project Deliverables
24. Create Support Environment
25. Information Security Requirement
26. General and ADHOC queries
27. Print and online help options

Indian Naval Ship Maintenance Authority Page 81

 Appendix ‘C’

SCOPE OF WORK FOR SUPPORT PHASE

1. Monitoring/ Maintenance Application. In order to efficiently monitor and

maintain the developed project, the System Integrator needs to implement a ticketing
mechanism on NCN/NUD for initiating the defects/ issues online by Indian Naval
personnel.

2. Handholding Scope. The handholding phase of 06 months from the date of

delivery of the software to IN, would have all the scope of CAMC phase. Additionally,
all defects/ issues arising out of newly developed CMMS would be part of handholding
phase and needs to be resolved by the deployed team. Hand holding phase should
include an additional developer (with more than 03 years’ experience in tools used for
development of CMMS Upgrade) for a period of 06 months to resolve such issues of
newly developed CMMS module.

3. Comprehensive Annual Maintenance Contract (CAMC) Scope. CAMC

phase is for 03 years, post completion of handholding phase. The scope of work during
CAMC phase needs to be handled by the four deployed resident engineers with the
support of Firm’s backend team. There are four types of maintenance, namely,
corrective, adaptive, perfective, and preventive. The scope is as follows: -

CAMC Scope

(a) All the items supplied and installed as part of contract will be covered in
the CAMC. This period will consist of spare support, technical support and Help
desk support.

CAMC Tasks

(b) Corrective Maintenance. Corrective maintenance is to be undertaken

to conform the software to its agreed specifications. Need for corrective
maintenance is raised by the User/ bug/ self-monitoring. Defect or errors may
arise due to errors in software design, logic and coding. All these errors,
referred to as residual errors, prevent the software from conforming to its
agreed specifications. Corrective Maintenance requires following activities
pertaining to both Online and Offline CMMS: -

(i) Repair of faults or defects found in day-today system functions.

(ii) In the event of a system failure due to an error, actions is to be

taken to restore the operation of the software system.

(iii) The approach should be to locate the original specifications in

order to determine what the system was originally designed to do.

(iv) During time critical requirements, the maintenance team may

resort to emergency fixes known as patching.

Indian Naval Ship Maintenance Authority Page 82

 (c) Adaptive Maintenance. Adaptive maintenance is to be undertaken to
implement changes in a part of the system, which has been affected by a
change that occurred in some other part of the system. Adaptive maintenance
consists of adapting software to changes in the environment such as change in
web browser, change in hardware, change in database, modification in
maintenance policies impacting the logic of the codes. This also includes
implementation of updates/ Upgrades/ New Releases/ New Versions on the
developed environment post approval from Indian Navy as and when released.

(d) Perfective Maintenance. Perfective maintenance is to be

undertaken to implement new or changed user requirements (within the
capability of resident’s engineers and mutually agreed scope by the System
Integrator’s backend team). Perfective maintenance involves making functional
enhancements to the system in addition to the activities to increase the
system's performance even when the changes have not been suggested by
faults. This includes enhancing both the function and efficiency of the code and
changing the functionalities of the system as per the users' changing needs.
Any new user requirement which is not part of CAMC scope and not mutually
agreed by the System Integrator would be construed as Change Request.

(e) Preventive Maintenance. Preventive maintenance is to be

undertaken to perform activities to prevent the occurrence of errors. It tends to
reduce the software complexity thereby improving program understandability
and increasing software maintainability. It comprises the following activities: -

(i) Documentation updating. Documentation updating involves

modifying the documents affected by the changes in order to correspond
to the present state of the system.

(ii) Code optimization. Code optimization involves modifying the

programs for faster execution or efficient use of storage space and code
restructuring.

(iii) Code Restructuring. Code Restructuring involves transforming

the program structure for reducing the complexity in source code and
making it easier to understand.

(iv) Application Maintenance. Application maintenance such as

clearing of logs, monitoring user activity, checks of hardware
consumption, checks of file system limits etc.

4. CAMC Terms & Methodology. In order to successfully execute the CAMC

phase the System Integrator needs to undertake and ensure the following through the
deployed support team: -

(a) The help desk will be operational on all working days (i.e. Monday to
Friday) and working hours between 9 AM – 6 PM.

(b) Serviceability of 90% per year is to be ensured. Also unserviceability

should not exceed ½ days at one time. Required spares to attain this

Indian Naval Ship Maintenance Authority Page 83

 serviceability may be stored at site by the Seller at his own cost. Total down
time would be calculated at the end of the year. If downtime exceeds permitted
downtime, LD would be applicable for the delayed period.

(c) Spares should be maintained in a serviceable condition to avoid

complete breakdown of the equipment/system.

(d) Deployed team has to liaise with the respective OEMs/ third party vendor
for resolution of defects/ issues arising in the supplied hardware/ software.

(e) On receiving the ticket, “Help Desk” will analyses the problem and
attempt it to resolve in case of any eventuality, call for relevant technical expert
from the backend team to resolve the issue.

(f) If the issue can’t be resolved via call, technical expert will be coming to
onsite to resolve the issue. Time required to reach the onsite should be
communicated to INSMA in advance.

(g) Detailed report of the issue and the fixing of the issue should be
submitted to INSMA on resolution of defect/ issue.

(h) Intimation of patches/upgrade relevant to the deployed software

components will be responsibility of System Integrator’s backend support team.

(i) Any upgrade/ patch released wrt the software used in the developed
environment should be applied by the deployed team.

Scope of Each Vertical Expertise

5. Application Administration

(a) Expertise in at least two scripting language like Python, Django, Spring
Boot, Node JS, Angular JS and PosgreSQL.

(b) User and password management, implementation of LDAP, creation of

domain users and mirroring of users from other location viz
Delhi/Vizag/Kochi/Karwar/Gujrat etc domain to CMMS Upgrade user domain.

(c) Updation of environment by downloading of patches /Up-gradation of

OS/ Development application utilised as and when made available by DIT or
INSMA.

(d) Migration of existing CMMS application source code as well as Database

to upgraded environment for security.

(e) Daily updation and Bug fixing of CMMS Upgrade application code.

(f) Incorporation of validation logic for data import into application.

Indian Naval Ship Maintenance Authority Page 84

 (g) Change request management to enhance functionality, incorporate
logics etc. for enhancing functionality, features, reports, ergonomics and
productivity.

(h) Undertake online receipt of user creation and ship data base updation
and forwarding of various reports through web portal.

(i) Maintenance, Updating, development of CMMS Upgrade modules along

with provisioning of latest software/hardware/license requirements as and when
required for the existing setup of CMMS application.

6. Database Administration

(a) Designing and rationalization of relational database schema as per user

requirement on technologies like PostgreSQL.

(b) Periodic Indexing and Normalization of CMMS Upgrade Application

Database. Running and maintaining database servers in production and
hosting environment with maintenance features like hosting on multiple
platforms and replication.

(c) Set-up, configure, run and maintain relational database server in

Windows/ Linux environments and also facilitate user based data mining and
reporting functions.

(d) Generate and print log and performance reports from the database, and
carry out regular maintenance of the database.

(e) Maintain periodic backup of database for recovery in case of any disaster
or data loss.

7. Network and Security Administration

(a) Testing of network for weakness, ensure that CMMS Upgrade

application network software are up to date, monitoring the performance of the
network, checking for security breaches and poor data management practices.

(b) Disaster Recovery management of applications periodically.

(c) Ensuring network connectivity between user module and the central
server for seamless data migration/mapping between main and client servers.

(d) Installing and implementing network security programs as per extent IT

policies.

(e) Undertake yearly Vulnerability Assessment of CMMS Upgrade.

(f) application and resolve any vulnerability all in accordance with extent
IT/InfoSec policies of Indian Navy.

Indian Naval Ship Maintenance Authority Page 85

Desired Level of Expertise

8. In consonance with Scope of Work the desired level of expertise is tabulated

below: -

Ser Scope of Work Expertise/Qualification Experience

(a) Front end 1st Class MCA, (i) More than 06 years
Developer (02) or of experience. (Minimum)
1st Class M.Sc. in IT/
Computer science, (ii) Should have worked
or on Angular JS, React JS,
Equivalent certification ( will HTML, Java, CSS, Python
be verified during Buyer’s and Django framework
interview)
(iii) Should have worked
on FIGMA and wire framing
tool.

(b) Backend and 1st Class MCA, (i) More than 06 years
Database (02) or of experience. (Minimum)
1st Class M.Sc. in IT/
Computer science, (ii) Should have worked
or on the following: -
Equivalent
certification ( will be (a) Backend on Python,
verified during Django, Spring
Buyer’s interview) Boot, Node JS.
(b) Front end on
Angular JS.
(c) Database on
PostgreSQL.
(d) ERP modules.

(c) Support Hand BCA, or B.Sc. in IT/ Should have work

(02) Computer science, or BE in experience of at least 02
IT/ Computer science, or B- years and should have
Tech in IT/Computer worked on a database
science or Equivalent network or data entry into
diploma database and operations.

Indian Naval Ship Maintenance Authority Page 86

 Appendix ‘D’
NON DISCLOSURE AGREEMENT

It is understood and agreed to that the customer/ discloser (Indian navy) during
the course of the Annual Maintenance Contract of the software application along with
the networking assets would be sharing certain information that may be considered
confidential. To ensure the protection of such information and in consideration of the
agreement to exchange said information, the firm/ recipient (System Integrator) agree
as follows: -

1. The confidential information to be disclosed by Discloser under this agreement

(“Confidential information”) can be described as and includes the following (regardless
of whether such information is designated as “Confidential Information’ at the time of
disclosure): -

(a) Technical and operational information relating to Naval proprietary

information and ideas.

(b) Patentable ideas copyrights and/ or trade secrets.

(c) Existing and/ or contemplated products and services, software,

schematics, research and development, production, costs, profit and margin
information.

(d) Finances and financial projections, customers, clients, marketing and

current or future business plans and models, re

2. In addition to the above, Confidential Information shall also include, and the
Recipient shall have a duty to protect, other confidential and/ or sensitive information
which is: -

(a) Disclosed by the Discloser in writing and marked as confidential (or other
similar designation) at the time of disclosure and/ or

(b) Disclosed by the Discloser in any other manner and identified as

confidential at the time of disclosure and is also summarized and designated
as confidential in a written memorandum delivered to Recipient within thirty (30)
days of the disclosure.

3. Recipient shall use the Confidential Information only for the purpose of
evaluating potential business and investment relationships with Discloser. Recipient
shall limit discloser. Recipient shall limit disclosure of confidential information within its
own organization to its directors, officers, partners, members and/or employees having
a need to know and shall not disclose Confidential information to any third party
(whether an individual, corporation, or other entity) without the prior written consent of
Discloser. Recipient shall have satisfied its obligations under this paragraph if it takes
affirmative measures to ensure compliance with these confidentiality obligations by its
employees, agents, consultants and other who are permitted access to or use of the
confidential information.

Indian Naval Ship Maintenance Authority Page 87

4. This Agreement imposes no obligation upon Recipient with respect to any
Confidential information: -

(a) That was in Recipient’s possession before receipt from Discloser;

(b) Is or becomes a matter of public knowledge through no fault or Recipient;

(c) Is rightfully received by Recipient from a third party not owing a duty of
confidentiality to the Discloser;

(d) Is disclosed without a duty of confidentiality to third party by, or with the
authorization of, Discloser; or

(e) Is independently developed by Recipient.

5. Discloser warrants that he/she has the right to make the disclosures under this
Agreement.

6. This Agreement shall be construed as creating, conveying, transferring,

granting or conferring upon the Recipient any rights, license or authority in or to the
information exchanged, except the limited right to use Confidential information
specified in paragraph 2. Furthermore, and specifically, no license or conveyance of
any intellectual property rights is granted or implied by this Agreement.

7. Neither party has an obligation under this Agreement to purchase any service,
goods, or intangibles from the other party. Discloser may, at its sole discretion, using
its own information, offer such products and/or services for sale and modify them or
discontinue sale at any time. Furthermore, both parties acknowledge and agree that
the exchange of information under this Agreement shall not commit or bind either party
to any present or future contractual relationship (except as specifically stated herein),
nor shall the exchange of information be construed as an inducement to act or not to
act in any given manner.

8. Neither party shall be liable to the other in any manner whatsoever for any
decisions, obligations, costs or expenses incurred, changes in business practices,
plans, organization, products, services, or otherwise, based on either party’s decision
to use or rely on any information exchanged under this Agreement.

9. If there is a breach or threatened breach of any provision of this Agreement, it

is agreed and understood that Discloser shall have no adequate remedy in money or
other damages and accordingly shall be entitled to injunctive relief; provided however,
no specification in this Agreement of any particular remedy authorized representatives
or both parties. This Agreement is made under and shall be construed according to
the laws of the Constitution of India. In the event that this agreement is breached, any
and all disputes must be settled in a court of competent jurisdiction at Mumbai, in the
state of Maharashtra, India.

10. If any of the provisions of this Agreement are found to be unenforceable, the
remainder shall be enforced as fully as possible and the unenforceable provision(s)

Indian Naval Ship Maintenance Authority Page 88

shall be deemed modified to the limited extend required to permit enforcement of the
Agreement as whole.

11. WHEREFORE, the parties acknowledge that they have read and understand
this Agreement and voluntarily accept the duties and obligations set forth herein.

Recipient of Confidential information

Name
Company
Title
Address
City, State & Zip
Signature
Date
Discloser of Confidential Information
Name
Company
Title
Address
City, State & Zip
Signature
Date

Indian Naval Ship Maintenance Authority Page 89

 Appendix ‘E’

CERTIFICATE OF MALICIOUS CODE

(This certificate is to be rendered on company’s letterhead)

1. This is to certify that the hardware and the software being offered as part of the
contract does not contain any kind of malicious code that would activate
procedures to

(a) Inhibit the desired and the designed function of the equipment.

(b) Cause physical damage to the Buyer or his equipment during the
operational exploitation of the equipment.

(c) Tap information regarding network, network Buyers and information

stored on the network that is classified and / or relating to National Security,
thereby contravening Official Secrets Act 1923.

2. There are no Trojans, Viruses, Worms, Spywares or any malicious software on

the system and in the software developed.

3. This firm is liable in case of physical damage, loss of information and those
relating to copyright and Intellectual Property rights (IPRs), caused due to
activation of any such malicious code in embedded / shipped software.

(Signed)

Date: - Designation

Place: - Name and address of firm

Company Seal
(Authorised Signatory)
Place: ........................
Date: .........................

Indian Naval Ship Maintenance Authority Page 90

 Appendix ‘F’

Price Bid Format

1. Basic cost of the item/items (will be considered for determining L1):

Ser Item Unit Qty Total

Price
Software Development
(a) URS, SRS and Project Study
As per RFP
Report
(b) Architecture Development &
As per RFP
Deployment
(c) Frontend Development As per RFP
(d) Backend Development As per RFP
(e) Digitation of Manual Processes As per RFP
(f) Analytical Layer & Search
As per RFP
Capability Development
Service
(g) Legacy Data Migration As per RFP
(h) Installation of Software, Training
As per RFP
and Testing
(i) Vulnerability Assessment As per RFP
(j) Handholding 06 Months
(k) Warranty 12 months
Hardware
(l) Standalone development server
(32 GB RAM, 32 Core, 1Tb HDD,
02
minimum i7 or as per latest
version of processor available)
(m) Development Desktops 06
(n) Desktops for Internet Access 02
(o) Ruggedized & customized
System Administrator Laptop for 02
trouble shooting post deployment
(p) Network Switch to integrate the
Standalone PCs other than the 02
Internet PC
(q) Work Stations 10
(r) Scanners 02
(s) Heavy Duty Multifunction Printers 02
Application Support
(t) AMC post completion of 1 yr
3 Yrs
Warranty
Total Cost without GST
GST @ 18%
Total Cost with GST

Indian Naval Ship Maintenance Authority Page 91

Special instructions

1. All charges as indicated above are to be inclusive of taxes.

2. The grand total will be used for drawing up the CST and identification of L1. In
case of discrepancy between the sum of unitized item cost and grand total, unit cost
multiplied with quantity will be taken as final cost.

3. The exemption certificates required (if any) are to be mentioned separately and
will be issued to L1 firm post placement of order.

Note. The bidder must consider the prices in relation to scope, schedule, allocation
of risks and responsibilities, and any other requirements of the bids document. If, after
evaluating the price analyses, Procuring Entity determines that the bidder has
substantially failed to demonstrate its capability to deliver the contract at the offered
price, the Procuring Entity may reject the bid/ proposal.

Indian Naval Ship Maintenance Authority Page 92

 Appendix ‘G’

Vendor Evaluation Criteria

To ensure that the right product, System Integrators and Software OEMs are
shortlisted for project implementation, the following criteria along with supporting
documents should be included in the technical bid. Vendors will be evaluated on the
below mentioned criteria: -

Evaluation Criteria

Ser Criteria Compliance Reasons for Supporting

Status Non- Documents
(Yes/No) Compliance Required
1. Proposal submitted in
accordance with two-bid Part II Para 3
system
2. The bidder must possess the
following certifications (The
mandatory quality certification
as stated must be active and
valid during the currency of the
complete project): -

ISO 9001:2008 or above Copy of

certification
And

CMMI Level 3 or above

And

ISO 27001:2013 or above

3. The vendor should have
worked on at least 03 similar
cases of Business Process
Automation related to Relevant
Maintenance and Acquisition or Work Orders
on at-least one ERP of
minimum value of 50 lac or
above
4. The vendor must be willing to
Supporting
establish a service base at
document
Mumbai
5. The bidder should self-certify
that they have not been
blacklisted by Govt of Copy of self-
India/Central PSU in the last 05 certification
years preceding the date of
submission of the bid.
Indian Naval Ship Maintenance Authority Page 93
 6. Minimum of average turnover/
work orders of Rs. 50 Lakhs in
last Three Years.
7. The vendors are to furnish an
undertaking that their firm has
not been blacklisted by any
Govt. organization on the date
of issue of this RFP. In case, at Undertaking
any stage it is learnt that the
undertaking furnished is false,
action as deemed fit, will be
taken against the vendor.
8. Vendor to enclose their support Provide
and escalation Matrix to support and
substantiate their capability to escalation
provide required support for the matrix
project. document
9. Bidder to enclose the proposed
Provide
architecture document to
proposed
ascertain their understanding
architecture
of the required solution at IHQ
document
MoD(N)/DIT.
10. The firm must have a valid GST
registration. A copy of the
Yes
registration/certificate should
be enclosed.
11. EMD Deposit Yes
12. Payment Terms Undertaking
13. Acceptance of Standard
Conditions of Contract (SCOC)
Undertaking
and other terms and conditions
given in the RFP
14. The bidder agrees to attend the
pre-bid conference either Undertaking
physically or through VC.
15. The vendor must agree to
undertake Proof of Concept on Undertaking
self-financed basis

Indian Naval Ship Maintenance Authority Page 94

 Appendix ‘H’

BID SECURITY DECLARATION

1. I/We _____________ (hereinafter called the “FIRM”) declare that we will not
withdraw or modify our bid during the period of validity of the bid after the deadline for
submission of such documents.

1. If I/We withdraw or modify the bids during the period of validity, or if I/We are
awarded the contract and fail to sign the contract, or to submit the performance
security before the deadline as defined in the tender document, we will be suspended
for the period specified in the debarment clause in the tender document from being
eligible to submit bids/ proposal for contracts.

Place: ____________ Signature of bidder

Date: ____________ (Name of bidder)

Office Seal of the Firm

Indian Naval Ship Maintenance Authority Page 95

 LIST OF BOOKS AND RECORDS

13. Documentation. Understanding and documenting the system specifications,

that describe in detail the envisaged purpose of the application, and the details of its
implementation is very important as it forms the foundation for the risk assessment
and management processes that follow it. These documents have to be prepared in
soft copy also to put it in the Documentation Module of CMMS, in the similar structure
of CMMS documentation. Various documents to be prepared as part of the project is
covered in subsequent paragraphs.

14. System Specifications. System Specification document that lays down the
purpose and broad technical specifications of the system to include the following: -

(d) Purpose of the cyber system and its linkages with mission/mission
support assets.

(e) Map/ chart/ topology of all physical facilities indicating entry points and
networks.

(f) Logic diagrams, data-flow process and dependencies on external

systems.

15. Patch Update Management. This Document discusses the steps required to
implement a successful security patch management solution which can be used to
help protect the enterprise. Patch management is about mitigating risk to the
confidentiality of your data and the integrity of your systems. Patch management can
be the most effective tool used to protect against vulnerabilities and the least
expensive to maintain if implemented effectively. The objective of this document is to
describe the patch management processes and procedures performed.

16. Change Management. The purpose of this document is to define a formal

process for performing any change process. The process includes the steps involved
including asset identification, scope for change, requester, approver, implementer
including release process. The document covers procedures to be adopted when any
change is incorporated but not limited to operating systems, network configurations
and hardware changes. It will cover all aspects of change from request to
implementation.

17. User Manual. The User Manual should provide an easy to use procedural
view of each page, click by click with a pictorial view. In addition, the user manual is
to be made in a video form too for the user to easily assimilate the written material.

18. Technical Manual. The Technical manual should intend to provide details of
various aspects of the CMMS Application and the system architecture, with regard to
Indian Naval Ship Maintenance Authority Page 96
trouble shooting and system setup. This document would be a reference point to
administrator and technical staff maintaining the CMMS Application and related
servers. The CMMS Technical manual documents the various components on the
CMMS Application Server and CMMS Database Server, the deployment view, various
scheduled jobs that form a part of CMMS processes, installation and configuration
information. A set of Annexures following the document provide with supplementary
information for the administrator.

19. Administrator Manual. The Administrator manual defines the process and
steps to be taken by an admin in day to day activity to monitor, modify and resolve the
admin related activity/issues.

20. Risk Assessment Document. The document should consist of the following
types of risks: -

(e) Risk to organizational operations (including mission, functions, image or

reputation)

(f) Risk to organizational assets.

(g) Risk to individuals

(h) Risk resulting from the operation of organizational information systems

and the associated processing, storage, or transmission of the organizational
information.

21. Risk Mitigation Plan. Risk mitigation plan should consist of the following steps
to mitigate the risks as mentioned in the Risk Assessment Document: -

(h) Access Control. Define the authorized users, processes acting on

behalf of authorized users, devices and the types of transactions and functions
that authorized users are permitted to exercise.

(i) Audit and Accountability. Defined procedure to maintain the audit

records, needed to enable the monitoring, analysis, investigation, and reporting
of unlawful, unauthorized, or inappropriate information system activity.

(j) Certification, Accreditation and Security Assessments. Define

process and periodicity to assess the security controls in organizational
information systems to determine if the controls are effective in their application.
Develop plan of action designed to correct deficiencies and reduce or eliminate
vulnerabilities in organization information systems.

Indian Naval Ship Maintenance Authority Page 97

 (k) Configuration Management. Prepare a configuration Management
plan to establish, maintain, and effectively implement plans for emergency
response, backup operations, and post disaster recovery for organizational
information system, to ensure the availability of critical information resources
and continuity of operations in emergency situations.

(l) Incident Response. Define process to establish and operational

incident handling capability that includes adequate preparation, detection,
analysis, containment, recovery and user response activities, and track,
document & report incident to appropriate authorities.

(m) Maintenance Plan. Plan to effectively perform periodic and timely

maintenance and provide control on the techniques, tools and mechanisms for
personnel used to conduct the maintenance.

(n) System and Information Integrity. Procedure to identify, report, and

correct the flaws in a timely manner, provide protection from malicious code,
monitor alerts and advisories and take appropriate actions in response.

22. Cyber Security Policy. Prepare System-specific Cyber Security Policies as

per guidelines provided by Navy to include the following: -

(h) Access control and physical security requirements.

(i) Configuration control to ensure systematic and authenticated alteration

to system parameters.

(j) Process for acquisition of hardware and software.

(k) Mechanism for patch and update management of the operating system,
third-party applications, device drivers and control modules.

(l) Methodology for accounting inventory.

(m) Roles and responsibilities.

(n) Periodicity for conduct of Vulnerability Assessments and security audits.

23. Standard Operating Procedures. Prepare precise, unambiguous and detailed

SOP based on the system specific policy to address all security aspects during
operation and maintenance of the system. Essentially the SOPs translate the system
specific security policies into actionable processes with clear indication of who is to do
what, where and when. In addition, the following are to be included in the SOPs: -

Indian Naval Ship Maintenance Authority Page 98

 (f) Assign and record specific responsibilities with respect to accounting
and security of all IT components of the system.

(g) Document the procedure for testing of new changes/ amendments

before introducing it in live systems and phasing out of the old software
component.

(h) Implement mechanisms to maintain logs of administrators to enable

track-back in the event of a security incident.

(i) Create incident response management plan with CIRT-Navy, SI.

(j) Stipulate chain-of-command for incident reporting and response.

24. Deliverables.

Ser Description Qty

(a) Hard copy of all the documents listed above 04 Copies
(b) Video of how to use the application Set of videos as
required
(c) Presentation of how to use the application Set of
and application features wrt each module presentations as
required

Indian Naval Ship Maintenance Authority Page 99

 Appendix ‘F’
Annexure ‘C’
Refers Para 20 & 21 of Part IV

LIST OF DELIVERABLES, DOCUMENTATION AND MANUALS

Ser Items Number required

1. Project plan 02 Hard Copy
2. Restoration and Backup CDs for the system 01 Set each
software
3. Documentation with respect to Customised 02 Hard Copies, 01 Soft
application Copy

4. Training Course material (If any) 20 trainees, one per

trainee and three spare
copies

5. Copy of CBT package as per IETM level 3 02 Copies

standards(Separate for Administrator and
Buyer) and Tutorial for the application
6. Copy of Source/customisation code of the 02 Copies
application
7. Quality Acceptance Plan, Acceptance Test 02 Copies
plan, Acceptance Test Schedule
8. Documentation, Media and License for the 01 Set each as per the
software software. Including OEM
support certificate in
accordance with para19
of part IV of RFP
9. Certificate of authenticity for the Software 01 copy each

10. Consolidated BOM containing complete 02 Copies, one soft copy

information on the installed components with
Manufacturer’s Part No, quantities used,
numbering scheme used, colour codes etc

11. Warranty certificates from OEM. 01 set

12. Configuration Documents (for servers, switches 02 Sets
and active components)

13. Malicious code certificate 01 original ink signed

copy
14. Brochures for the application 02 copies

Indian Naval Ship Maintenance Authority Page 100