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. 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. 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. 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. (a) Specific requirements for maintenance and support.
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. 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. 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. Rights to development and customisations The rights of the Contractor The Contractor shall retain the copyright to software that are developed specifically for the Customer unless otherwise agreed in the particular case. The rights of the Customer The Customer is granted, free of charge, an indefinite and non-exclusive right to utilise the various parts of the software developed or customised specifically for the Customer (expanded right of disposal). The expanded right of disposal includes the right to use, copy, modify and develop the customisations, either on its own or with the assistance of a third party. The Customer is entitled to confer a corresponding expanded right of disposal on any other public body. Source code and associated specifications and documentation of the development and customisations shall be handed over to the Customer within ten (10) working days after the delivery date, unless otherwise agreed in the particular case. Right of disposal of documentation Making of copies (copying) The Contractor shall make available such number of copies of the documentation as is desired by the Customer, at the prices listed in Appendix 7. If the Contractor is unable to make available the necessary number of copies, the Customer may make such copies itself for its own use. No consideration shall be payable in respect of such copies. Changes to the documentation The Customer may, at its own risk, make such changes, additions, etc., to the documentation for its own use as are deemed appropriate by the Customer. Documentation of development and customisations The Customer is granted a corresponding right of disposal of documentation prepared in connection with development and customisations, cf. clause 10.2, as the Customer is granted in relation to the development and customisations. This shall also cover training materials. Utilisation of the detailed specification Each of the parties may utilise the detailed specification without hindrance in respect of the other party's possible copyright. The right of utilisation includes the right to reuse the detailed specification in other assignments and to make it available to others, including for their reuse. This provision does ...
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.
