perform maintenance and purchase tasks as well. The typical breakdown of an Amos project for naval vessels is the following: Regarding one vessel of the Italian Navy,
SpecTec has been asked to study and provide the initial stock levels dimensioning using specific software named OPUS10 (Systecon AB). A custom interface has been developed to allow data exchange between Amos and Opus10. Data entry activity is, generally, the
most relevant part of the total cost of a CMMS because of the amount of technical information lying on paper documents. SpecTec has overcome this critical step enabling AMOS to retrieve automatically all needed information from electronic technical publication according with the ASD1000 standard. Customers, to benefit from this functionality and save time, have to adopt and apply ASD1000 methodology. The first step, implementing a CMMS
In recent years maintenance management
in the Navies has evolved from paper based systems, such has the PMS (Planned Maintenance System) methodology created in US Navy and traded abroad, to CMMS (Computerized Maintenance Management Systems). Some Navies started very early and worked diligently to keep in step with technology but, generally speaking, several maintenance practices and approaches managing maintenance have fallen because of a lack of experience from the IT partner side. Besides, all Navies are facing increasing pressure on their businesses and operations due to greater maintenance costs. AMOS (Asset Management Operating System) is cost/effective software to keep under control efficiency and costs. AMOS M&P (Maintenance and Purchase) has been delivered to the Italian Navy to manage maintenance, stocks and purchase tasks on board two vessels. Currently it is successfully used and a larger implementation is under evaluation from the Italian Navy side. AMOS M&P software is part of the AMOS
Business Suite which include several products. Generally, for naval applications,
AMOS M&P is the product mostly delivered due to its functionalities and modules. The approach adopted for naval vessels is based on a distributed architecture where each site plays its own role: on the land side more offices work together on Amos database to
such as AMOS, is the Work Breakdown Structure design which is built up using the customer coding rules: the NATO-ESWBS code is used for all naval vessels. The Amos internal logic is often named
“component centred” because of the deep dependencies exiting among a “component” (asset) and its related information and entities. Using both the Functions and Components
CONTACTS: Defence:
Admiral Dino Vene (Head of Defence Department)
dino.vene@
spectec.net +39 0187 566621
Marco Vatteroni (ILS Manager)
marco.vatteroni@
spectec.net +39 0187 566623 Enrico Viti (Project Manager)
enrico.viti@
spectec.net +39 0187 566622 Marketing:
Deanne Aline Litman (Communication Manager)
deanne.litman@
spectec.net +39 0187 566613
hierarchical views, the comprehension of PMS contents is easier and the technician is able to better understand which function is performed by each component (installed equipment) and vice versa. SpecTec is very proud to count among
its valuable international customers in the defence market, The Italian Navy (including SIGINT vessels), the Danish Navy, the Swedish Coast Guard, a NATO Underwater Research Vessel, a US Military Sealift Command and the Irish Fishery Coast Guard. HDW shipyards have selected AMOS as an essential part of their internal logistic environment and they have already delivered 2 S209 submarines installed with AMOS to the South African Navy as CMMS. Such a delivery is also planned for the Greek and Portuguese Navies.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68