Maintainability Sample Clauses

Maintainability. This Agreement assumes the Covered Equipment to be in maintainable condition. With regard to maintenance work, should repairs or replacements be found necessary upon initial inspection or initial seasonal start-up, repair and/or replacement charges will be submitted to the Customer for approval.
AutoNDA by SimpleDocs
Maintainability. A measure of the ability of an item to be retained in, or restored to, a specified condition when maintenance is performed by personnel having specified skill levels using prescribed procedures.
Maintainability. The ability of an item to be retained in or restored to specified condition when maintenance is performed by personnel having specified skill levels, using prescribed procedures and resources, at each prescribed level of maintenance and repair. Maintainability consists of two major categories: maintenance and diagnostics.
Maintainability. If the Contractor chooses to deliver customer customisations in the form of developing the source code of software that provides the basis for the deliverables, the Contractor shall ensure that the customer customisations are also addressed in subsequent versions of the software.
Maintainability. Maintainability consists of three major areas: time to repair OMFs, total corrective maintenance time, and maintenance burden or maintenance ratio. Maintainability may be expressed as (1) Mean Corrective Maintenance Time for Operational Mission Failure Repairs (MCMTOMF), (2) Mean Corrective Maintenance Time for all incidents (MCMT), (3) Maximum (e.g., 90 Percentile Time) Corrective Maintenance Time for Operational Mission Failures (MaxCMTOMF), (4) Maximum (e.g., 90 Percentile) Corrective Maintenance Time for all incidents (MaxCMT), and (5) various maintenance ratios (MR), e.g., Maintenance Man-Hours Per Operating Hour, Mile, Round, etc. (See paragraph 8 for definitions.)
Maintainability. The parameters for addressing maintainability are mean corrective maintenance time for operational mission failures (MCMTOMF), maximum corrective maintenance time for operational mission failures (MaxCMTOMF), mean corrective maintenance time for operational mission faults-software (MCMTOMFSW), MRT, BIT, and MR. (1) MCMTOMF is the average elapsed corrective maintenance time needed to repair all operational mission hardware failures. It includes time for maintenance preparation, fault location and isolation, on-board parts procurement, fault correction, adjustment and calibration, as well as follow-up checkout time. It does not include off-board logistic delay time. MCMTOMF = Total Elapsed Time to Correct Operational Mission Failures Total Number of Operational Mission Failures Onboard logistic delay is the logistic delay associated with obtaining the spare part at the unit or organizational level. For aircraft systems, the squadron will be considered the unit level. Therefore; MCMTOMF will be calculated as the mean of the elapsed maintenance time (block A45 of the maintenance action form). (2) MaxCMTOMF is that time below which a specified percentage of corrective maintenance tasks must be completed to restore the system to operation after an OMF; e.g., 90 percent of all corrective maintenance times for operational mission hardware repairs will be less than MaxCMTOMF. This parameter is recommended when the time required to repair and restore the system due to operational urgency is considered an important aspect of the system under test. (3) MCMTOMFSW is the average elapsed time needed to restore a software-intensive system following an operational mission software fault. The system is considered to be restored when a tactical picture that is useful to the tactical action officer/operator is first established. This may include the time to restore all processes, functions, files, and databases to a tactically useful state as well as the time required to physically reboot the system following an operational mission software fault. It does not include the time to obtain spare parts or utilize the expertise of personnel outside the unit or organizational level. For aircraft systems, the unit level will be the squadron. MCMTOMFsw = (4) MRT is the average elapsed time required to reboot a software-intensive system. MRT is addressed as cold start MRT (MRTC) and warm start MRT (MRTW). Both MRTC and MRTW include only the time necessary to physically reboot the syste...
Maintainability. (a) Specific requirements for maintenance and support. (b) Support for our own maintenance.
AutoNDA by SimpleDocs
Maintainability. In general, the system should be developed to be easy to maintain. A user guide should be prepared and it should include some specific chapters to find information to solve common problems. The software elements must produce log files to monitor possible problems. The logs must be easy to understand and they must point directly to any problem that may occur in order to find the root of the problem and the way to solve it as soon as possible. Every element must be scalable after installation. There must be a procedure to do so and this procedure should be easy to follow. For example, there must be instructions to add a node to the data base cluster (if there is one). The data integrity should not be affected by these procedures and, as a desirable goal; these processes should be seamless for the user (meaning that the service availability is not affected during the process). Automatic backups must be done of all the relevant information of the system periodically. This includes databases, Solr cores, logs, etc. A complete restore of all this data must be possible to do in case of general failure. The procedure to restore such data must be well documented and easy to follow.
Maintainability. Maintainability is the ability of an item to be retained in, or restored to, a specific condition when maintenance is performed by personnel having specified skill levels, using prescribed procedures and resources, at each prescribed level of maintenance and repair. The established threshold for GCSS-MC/LCM Increment 1 is no more than four (4) hours of system downtime for 90.00% of downtime occurrences. The Contractor shall compute and report the Mean Corrective Maintenance Time (MCMT) and Corrective Maintenance Downtime Occurrences (CMDO) using the formulas provided in Figure 4below. 𝑇𝑜𝑡𝑎𝑙 𝑈𝑛𝑝𝑙𝑎𝑛𝑛𝑒𝑑 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑛𝑐𝑒 𝑇𝑖𝑚𝑒 = 𝑇𝑜𝑡𝑎𝑙 𝑈𝑛𝑝𝑙𝑎𝑛𝑛𝑒𝑑 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑛𝑐𝑒 𝐴𝑐𝑡𝑖𝑜𝑛𝑠 𝑇𝑜𝑡𝑎𝑙 𝑈𝑛𝑝𝑙𝑎𝑛𝑛𝑒𝑑 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑛𝑐𝑒 𝑇𝑖𝑚𝑒 = 𝑇𝑜𝑡𝑎𝑙 𝐷𝑜𝑤𝑛𝑡𝑖𝑚𝑒 * 100
Maintainability. The complete set of safety requirements should be hierarchical, organized, complete and consistent (i.e. requirements should not contradict each other). These characteris- tics of the safety requirements can be listed in a checklist for the safety requirements.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!