Which SDLC phase is analogous to the maintenance process of obtaining a maintenance request?

3.1 Socialization of Responsibility

West African children perform a much wider range of economically productive and maintenance activities than is the case in contemporary, urbanized Western societies. The goal of training is to socialize responsible intelligence. The expectation that older siblings will care for infants and perform some chores is a priming process for such socialization. Priming is an ontogenetic strategy to prepare children progressively for their future adulthood. Through it, children make progress toward adulthood as they ‘graduate’ from one role to another. The Nso of Cameroon, for example, assign pivotal roles to children at different ‘stations’ of the life cycle, depending on the perceived level of the child's maturity and competence. Sending children on errands is another form of responsibility training that permits children to develop listening skills, ability to follow instructions, widen perspective, and follow goals. Yoruba children who went on errands demonstrated superior cognitive performance on an adapted Bayley Mental Scale (Yoruba Mental Subscale) compared to peers who did not (Ogunnaike 1997). Role assignment underscores parental awareness of children's cognitive maturity and readiness for specific tasks.

12.4.2 Maintenance

Creating backups of digital information is an essential and also easily postponed maintenance activity. Our PDAs must also be periodically recharged.25 And every so often the software on our PDAs must be updated or “patched.” Why not combine these activities? All three might happen through a single charge-upload-download device as we sleep through the night.26

The recharging and maintenance of accessories to the PDA should also be considered. Support for maintenance will impact the likely adoption of accessories such as the “watch” watch. Today people are not in the habit of charging their watches. Instead, we expect our watches to last for a year or longer on a single replaceable battery. Some people will think that the watch as an accessory to a PDA is more trouble than it's worth. But others may value the features of a “watch” watch—the ability, for example, to get some information without the need to fish a PDA out of a pocket or purse. Some may even have a range of different watches for different occasions, for fashion27 as well as function, so that even as one watch is being worn, at least one other watch is being charged.

Preventative Maintenance

Preventative maintenance refers to the maintenance required to keep equipment and hardware running. Maintenance activities include performing diagnostics on circuit boards, changing boards, performing diagnostics on memory, and BIOS and any other parts of the hardware. It's possible that certain computers at times may need a new power supply or a new fan. Who are the folks who would make this determination and perform the installation? Preventative maintenance may be done by your agency's in-house staff, or it might be contracted out to a third-party organization. Whatever the case may be, document who performs preventative maintenance and whether it is performed on any sort of regular schedule. If an outside third-party performs these tasks, you'll need to include the name and contact information of the person or department responsible for managing the third-party.

A thoughtful argument can be made that preventative maintenance also includes the detection of software problems. However, I prefer to see information about the detection of software problems in the technical controls section that discusses preservation of data integrity. System diagnostics related to file system errors and file systems filling up belong in the preventative maintenance section. Some systems run scheduled diagnostics on a regular schedule to check the size of the file systems to ensure that they do not fill up. If the systems in your C&A package run any regularly scheduled diagnostics on the file systems, or are regularly defragmented, be sure to indicate this.

Preventative maintenance

Preventative maintenance refers to the maintenance required to keep equipment and hardware running. Maintenance activities include performing diagnostics on circuit boards, changing boards, performing diagnostics on memory, and BIOS and any other parts of the hardware. It’s possible that certain computers at times may need a new power supply or a new fan. Who are the folks who would make this determination and perform the installation? Preventative maintenance may be done by your agency’s in-house staff or it might be contracted out to a third-party organization. Whatever the case may be, document who performs preventative maintenance and whether it is performed on any sort of regular schedule. If an outside third-party performs these tasks, you’ll need to include the name and contact information of the person or department responsible for managing the third-party.

A thoughtful argument can be made that preventative maintenance also includes the detection of software problems. However, I prefer to see information about the detection of software problems in the technical controls section that discusses preservation of data integrity. System diagnostics related to file system errors and file systems filling up belong in the section on Preventative Maintenance. Some systems run scheduled diagnostics on a regular schedule to check the size of the file systems to ensure that they do not fill up. If the systems in your Security Package run any regularly scheduled diagnostics on the file systems, or are regularly defragmented, be sure to indicate this.

3.5 Maintenance constraints

The maintenance constraints implement the maintenance policy. Eq. (17) ensures that the maintenance activities are started only once over the considered time horizon. Eqs. (18) - (19) forces the maintenance to be performed in a specific time window (between day 30 and 40). Eq. (20) defines the duration of the maintenance.

(17)xmaintenancet≥xmaintenancet−1∀t∈T,t≠1

(18)∑t∈window xmaintenance_t≥1

(19)∑t∉windowxmaintenance_t=0

(20)∑txmaintenance_t≥dur

PREVENTATIVE MAINTENANCE THE COMPANY GOAL

A list of required items, to be incorporated in the program were initiated.

Maintenance activities must be dedicated to ensuring all equipment and systems are capable of achieving a steady, efficient production of products to meet their customer’s requirements.

Develop a list of supplier recommended spare parts to be available for each long lead item.

Prepare a checklist and maintenance plan with a schedule of preventative maintenance operations to be performed at set, supplier recommended internals. The schedule is modified with in-house failure rate data for estimating actual service requirements.

Review equipment and system failure problems, Parato charting, actual down time, and equipment and services required to repair, get system back on line, and skill level of employee to diagnosis problem and implement repair.

If not in-place, develop individual equipment problem, repair and parts list of most frequent failure items. Review this with item two to ensure sufficient parts are always in stock or readily available overnight if to high a cost item to have in stock.

Review maintenance department skill and manning levels to ensure capability is available in-house to support maintenance requirements and repair when they occur on all shifts.

Develop rapid response repair teams with required equipment and tools for analysis of a problem. Repair stations are centrally located within the plant with equipment specific to the operations performed in the surrounding area available for use when necessary. Tool kits are identified in each maintenance shop for all shifts use with the supervisor responsible at the end of each shift that all tools are returned to the tool kits unless the repair is still being performed.

Establish estimated maintenance down time requirements along with personnel requirements to let production know effects it will have on their production schedule.

Provide work instructions and equipment manuals with part identification, for each piece of equipment in the maintenance program so that the correct replacement part is used and installed correctly.

Once the maintenance system is established, audit all first time maintenance procedures and work instructions to ensure they are accurate, complete, and within anticipated time requirements for service support.

Develop a communication system with production and plant personnel to inform them when scheduled maintenance is required, to coordinate maintenance with minimum disruption of their production schedule.

Document all problems for each machine or major piece of equipment in the ‘Problem Solution Book’ with the recommended method to use for developing and diagnosis a solution to a problem. In the Solution Book should be a list of commonly replaced parts and their part number for easy locating in your inventory. Also, if special personnel are required to correct the problem they should be listed with their home phone numbers if off shift and they are necessary to contact when a problem occurs. Also, any preventative solutions that have been developed to prevent or reduce the time interval between a wear or failure problem. Document the personnel required and time necessary to solve and repair the problem.

The results from developing a well coordinated and timely maintenance schedule will result in the following benefits to the company production schedule and product quality.

TRAINING REQUIREMENTS

The most commonly underestimated costs associated with the implementation of a CMMS are the level and amount of training that will be required to achieve acceptable results from the system. Almost without exception, CMMS vendors claim that training requirements are minimal. In their view, a few days of CMMS user training is more than adequate. The assumption that all CMMS users will already have the basic reading, writing, and computer skills that are the minimum requirement for using any computer-based system is often erroneous. As a minimum, these skills must be taught to the principal users of the new system. While this recommended level of training is required, it is not enough to achieve acceptable performance from the CMMS.

Effective use of the maintenance resources, including the CMMS, will require a substantial training investment in addition to the CMMS user training. As a minimum, the following training courses should be provided:

Monitoring

Another role that falls under the “support” umbrella is keeping the enterprise application running. This includes maintenance activities (which we’ll cover next), but also all of the tasks necessary to ensure that the system has the highest level of availability possible. A key component of this is monitoring the enterprise application to ensure that everything is working as expected. The key idea here is for the enterprise applications administrator to be aware of issues before the application fails or end users report an issue.

Monitoring falls into several areas including monitoring the utilization of hardware, operating systems, network utilization, database performance, and application performance. In most cases, there are three levels of monitoring that are performed. The first is simple availability monitoring, that is, making sure that each component of the enterprise application is “up.” The second is functionality monitoring, which involves making sure that not only is the application available, but that it’s working the way that it’s supposed to. And the last is performance monitoring, which is watching to be sure that the application is performing at the speed that it’s supposed to.

There are a number of tools available for performing this monitoring, but in the end, it’s typically the responsibility of the enterprise applications administrator to make sure that some form of monitoring is in place and that there are processes in place to react to any issues discovered by the monitoring. It doesn’t help much from an availability perspective when an automated monitoring system determines that there’s a problem if no one is notified or paying attention to the monitoring system.

Support

For an operational system, support comprises monitoring, technical administration, troubleshooting and problem resolution, and routine maintenance activities such as backup, configuration control, patch management, and upgrade and release management for software or other technical components. Depending on organizational policies, procedures, and standards, support may also include information security management activities such as vulnerability analysis, automated or manual verification of configuration settings, and security information and event management. The support phase of an IT project typically runs in parallel with utilization; phases analogous to support in many SDLC methodologies are termed maintenance, with the combination of utilization and support known collectively as operations and maintenance. Audits of IT project support activities examine technical documentation such as administrative manuals and system configuration information; adherence of the project’s support processes to organizational policies, procedures, standards, and guidelines; and the ability of support resources allocated to the project to satisfy service-level agreements or other performance objectives specified for operational systems and services. An organization’s technical support capabilities have a direct impact on the operational effectiveness of its systems, so although support-phase activities can be audited in isolation, the scope of audits focusing on the utilization phase often includes support functions.

Under the umbrella function of continuous monitoring used in many organizational IT environments, capabilities such as intrusion detection and incident response are often performed for the organization as a whole rather than for specific projects or programs. Similarly, organizations that have standardized on particular hardware, software, operating systems, or other technologies may have a centralized function for managing updates, correcting vulnerabilities, or making other changes. Project-specific responsibilities in these support areas may be limited to ensuring that appropriate changes have been made and that technical documentation has been updated accordingly to accurately reflect the operational status of each system.