Control System Hardware, Firmware and Software

(1) Describe the system to be retired. (2) Identify the final status of the software. (3) Describe why retirement is needed.

(4) Identify the maintainer/support organization. (5) Identify the specific software processes retired.

(6) Describe any retirement protocols between customer and supplier. (7) Identify where retirement will be performed.

(8) Identify when retirement will commence. (9) Identify costs to provide retirement. (10) Identify the retirement schedule.

ii) Hardware Retirement

(1) Identify all components to be retired. (2) Identify where the components are located.

(3) Identify special tools and equipment needed for removal.

(4) Identify special disposal requirements (CRTs, Batteries, electronic boards, etc.). (5) Document all hardware disposal.

iii) Firmware Retirement

(1) Identify all components storing firmware.

(2) Identify licensing requirements specific to the firmware. (3) Follow all licensing requirements with respect to disposal. (4) Identify where the components are located.

(5) Identify special tools and equipment needed for removal.

(6) Identify special disposal requirements (CRTs. Batteries, electronic boards, etc.). (7) Document all firmware disposal.

iv) Software Retirement

(1) Identify all software to be retired.

(2) Identify licensing requirements specific to the software. (3) Follow all licensing requirements with respect to disposal. (4) Identify where the software is located.

(5) Identify special tools and equipment needed for removal (uninstallers, electronic shredders, disk formatters, etc.).

(6) Identify special disposal requirements of the software storage media (disks, tapes, memory). (7) Document all software disposal.

v) Develop Consolidated Retirement Report and Archive (1) Hardware Document

Appendix 7 Operation and Maintenance Phase

5

Software Change Control Process (1 September 2012)

It is recommended that the Owner/DCO reviews the Software Change Control Process to determine completeness. The following figure is an example of a recommended process.

Appendix 7 Operation and Maintenance Phase

7

Example Software Control Form Process Flow

The following is the process for handling software change control forms.

Software Control Form

Operator Responsible

Person

Person in Charge Vendor Chief Electrician Chief Engineer

Yes No Yes No _Yes No No Yes

Close Out Software Control Form Approve Software Control Form Identify Software Change Initiate Software Control Form Approve Software Control Form Approve Software Control Form Operator Request Repair Maintenance Approve Software Control Form Complete Software Control Form Software Backup Exists Test/Witness Software Change Completed Complete Upgrade Complete Upgrade Acknowledge Software Control Form Complete Backup of Software to be Changed Approve Software Control Form

Appendix 7 Operation and Maintenance Phase

9

Example MOC Process

FIGURE 1

Appendix 7 Operation and Maintenance Phase

Recommended inclusions to the retirement or replacement plan

i) Introduction

ii) Describe the system to be retired.

iii) Identify the final status of the software.

iv) Describe why retirement is needed.

v) Identify the maintainer/support organization.

vi) Identify the specific software processes retired.

vii) Describe any retirement protocols between customer and supplier.

viii) Identify where retirement will be performed.

ix) Identify when retirement will commence.

x) Identify costs to provide retirement.

xi) Identify the retirement schedule. Hardware Retirement

i) Identify all components to be retired.

ii) Identify where the components are located.

iii) Identify special tools and equipment needed for removal.

iv) Identify special disposal requirements (CRTs. Batteries, electronic boards, etc.).

v) Document all hardware disposal. Firmware Retirement

i) Identify all components storing firmware.

ii) Identify licensing requirements specific to the firmware.

iii) Follow all licensing requirements with respect to disposal.

iv) Identify where the components are located.

v) Identify special tools and equipment needed for removal.

vi) Identify special disposal requirements (CRTs. Batteries, electronic boards, etc.).

vii) Document all firmware disposal. Software Retirement

i) Identify all software to be retired.

ii) Identify licensing requirements specific to the software.

iii) Follow all licensing requirements with respect to disposal.

iv) Identify where the software is located.

v) Identify special tools and equipment needed for removal (uninstallers, electronic shredders, disk formatters, etc.).

vi) Identify special disposal requirements of the software storage media (disks, tapes, memory).

vii) Document all software disposal. Develop Consolidated Retirement Report and Archive

i) Hardware Document

ii) Firmware Document

Appendix 7 Operation and Maintenance Phase

11 Obsolete Control System Components Considerations

a. PC Workstations and laptops may be considered obsolete when any of the following milestones occur:

i) The unit is five or more years old.

ii) PC components such as RAM, CPU chipset and processor speed, and hard drive capacity do not meet the minimum requirements of necessary software applications.

iii) The manufacturer’s web site no longer offers support for that model.

b. PC Peripherals may be considered obsolete when any of the following milestones occur:

i) The model has been discontinued for three years (unless warranted).

ii) The manufacturer ceases business or is bought by a competitor (unless they support it).

iii) The manufacturer does not provide suitable device drivers for the operating system(s).

c. PC Applications may be considered obsolete when any of the following milestones occur:

i) The software version is three or more generations out of date.

ii) The manufacturer ceases business or is bought by a competitor (unless they support it).

iii) The manufacturer fails to correct any significant security flaw in a timely manner.

A p p e n d i x 8 : P r o j e c t M a n a g e m e n t A P P E N D I X

8 Project Management

INITIATING PLANNING EXECUTION & MONITORING CONTROL CLOSING

Accepted Verification

1

Scope

Project management is the application of knowledge, skills, tools, and techniques that enables the initiation, planning, execution, monitoring and control, and closure of a project within a given schedule and budget, and with the expected level of quality to satisfy project requirements and objectives.

3

Background

The Project Management Institute’s Project Management Body of Knowledge (PMBOK®), the application of knowledge, skills, tools, and techniques have been implemented in processes that are depicted in Appendix 8, Table 1. The differentiation between core processes and facilitating (support) processes. Each process group may contain core and support processes. Core processes are those that occur in sequence.

Project management results in the creation of deliverables, and utilizes milestones to mark the plan’s progress. In the following discussion, it is noted that the focus is on project management processes where the milestones and deliverables are relatively independent from the Software Development Life Cycle (SDLC), noted in white in Appendix 8, Figure 1, milestones and deliverables.

TABLE 1

39 Project Processes

Knowledge Area

Process Group Integration Scope Time Cost Quality Initiating Initiation

Planning Project Plan Development Scope Planning Scope Definition Activity Definition Activity Sequencing Activity Duration Estimating Schedule development Resource Planning Cost Estimating Cost Budgeting Quality Planning

Executing Project Plan Execution Quality Assurance Monitoring and Controlling Integrated Change Control Scope Verification Scope Change Control

Schedule control Cost control Quality Control

Closing

Underline = Core Process, non-underline – Facilitating processes