Maintainability Sample Clauses

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.
AutoNDA by SimpleDocs
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. (DAU Glossary)
Maintainability. 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 and resources, at each prescribed level of maintenance and repair.
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.
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. 𝑀𝑒𝑎𝑛 𝐶𝑜𝑟𝑟𝑒𝑐𝑡𝑖𝑣𝑒 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑛𝑐𝑒 𝑇𝑖𝑚𝑒 𝑀𝐶𝑀𝑇 𝑇𝑜𝑡𝑎𝑙 𝑈𝑛𝑝𝑙𝑎𝑛𝑛𝑒𝑑 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑛𝑐𝑒 𝑇𝑖𝑚𝑒 = 𝑇𝑜𝑡𝑎𝑙 𝑈𝑛𝑝𝑙𝑎𝑛𝑛𝑒𝑑 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑛𝑐𝑒 𝐴𝑐𝑡𝑖𝑜𝑛𝑠 𝐶𝑜��𝑟𝑒𝑐��𝑖𝑣𝑒 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑐𝑒 𝐷𝑜w𝑛𝑡𝑖𝑚𝑒 𝑂𝑐𝑐𝑢𝑟𝑟𝑒𝑛𝑐𝑒𝑠 𝑇𝑜𝑡𝑎𝑙 𝑈𝑛𝑝𝑙𝑎𝑛𝑛𝑒𝑑 𝑀𝑎𝑖𝑛𝑡𝑒𝑛𝑎𝑛𝑐𝑒 𝑇𝑖𝑚𝑒 = 𝑇𝑜𝑡𝑎𝑙 𝐷𝑜𝑤𝑛𝑡𝑖𝑚𝑒 * 100 Figure 4: Maintainability Formula
AutoNDA by SimpleDocs
Maintainability. “The ease with which the CIS maintenance (both corrective and evolutive) can be performed in accordance with prescribed quality of service requirements.” In the case of services requiring special responsiveness, introducing corrections or changes to the CIS shall be possible without disrupting service (e.g. hot deployment).
Maintainability. Recommendation: 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.
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.
Time is Money Join Law Insider Premium to draft better contracts faster.