6002-00002-np, revision 4, 'advanced logic system ... · als configuration management plan cs...

ALSAdvanced Logic System

*CS hnnOvaitions:A WOslinghouse Electric,,Company,

6002-00002-NPALS Configuration Management Plan

Revision 4August 11, 2010

Function Name and Title Signature and Date

Author Joe Lorson Electronic SignatureConfiguration Manager

Charles Bobbitt Electronic SignatureQA Manager

Thomas Christensen Electronic SignatureApproved Software Manager

CS InnovationsPublic Information - Class 0

This document is the property of CS Innovations of Scottsdale, AZ.

© 2010 CS Innovations

All Rights Reserved

ALS Configuration Management Plan CS InnovationsALS Configuration Management Plan CS Innovations

RECORD OF CHANGES

OPEN ITEMS

0

CD

Item Description Status

6002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary of 31

ALS Configuration Management Plan CS Innovations

Table of Content

1 Introduction ................................................................................................................................................................ 51.1 Purpose ............................................................................................................................................................ 5

1.2 Scope ............................................................................................................................................................... 5

1.2.1 ALS Developm ent Overview ...................................................................................................... 5

1.2.2 ALS Board Configuration Items ................................................................................................... 7

1.2.3 Support Configuration Items ...................................................................................................... 7

1.2.4 Other Configuration Items .................................................................................................................... 8

1.2.5 Lim itations ............................................................................................................................................ 8E (I .4 Terms and Abbreviations .................................................................................................................................

2 CM Managem ent ....................................................................................................................................................... 92.1 Organization .................................................................................................................................................... 9

2.2 CM Responsibilities .......................................................................................................................................... 9

2.3 Applicable policies, directives, and procedures ................................................................................................ 9

3 CM Activities ............................................................................................................................................................ 113.1 Configuration Identification ............................................................................................................................. 11

3.1.1 Configuration Items (CIs) ................................................................................................................... 11

3.1.2 Nam ing Configuration Items ............................................................................................................... 14

3.1.3 Acquiring Configuration Items ..................................................................................................... 16

3.1.4 Control of Software Tools ................................................................................................................... 16

3.2 Configuration Control ..................................................................................................................................... 16

3.2.1 Change Control .................................................................................................................................. 16

3.2.2 Change Control Prior to Baseline .................................................................................................. 17

3.2.3 Configuration Item Release, Archive and Retrieve Activities ........................................................ 17

3.2.4 Issue Reporting, Tracking and Corrective Action Activities .......................................................... 17

3.2.5 Approval Authority - the Change Control Board (CCB) ................................................................. 17

3.3 Status Accounting .......................................................................................................................................... 18L is3.5 Configuration Audits and Reviews ................................................................................................................ 18

3.5.1 Internal Reviews ................................................................................................................................ 18

3.5.2 Managerial Reviews ........................................................................................................................... 18

4 Schedules ................................................................................................................................................................ 195 Resources ................................................................................................................................................................ 21

6 Plan Maintenance .................................................................................................................................................... 236.1 Responsibilities .............................................................................................................................................. 23

6.2 Change Approvals .......................................................................................................................................... 23


ALS Configuration Management Plan CS Innovations,

This page intentionally left blank



1.1 PurposeThe ALS Configuration Management Plan (ALS CM Plan) describes the CM organization and practices used forbaseline control of ALS related configuration items. The ALS CM Plan is used for initial design activities related toALS boards, but also for modifications to released ALS boards after baselining. Modifications include changes toALS board hardware design, Field Programmable Gate Array (FPGA) design and non-volatile memory (NVM).

1.2 ScopeThe ALS CM Plan is to be applied consistently and uniformly throughout the life cycle of ALS boards. The intendedaudience for the ALS CM Plan is CS Innovations personnel associated with managing, developing, reviewing, andproviding quality assurance of ALS based products.

The ALS CM Plan is based on the guidance provided in IEEE Std 828-1998, the CS Innovations document 9000-00000: "Quality Assurance Manual" (Reference 6) and 6002-00000: ALS Management Plan (Reference 1).

1.2.1 ALS Development OverviewThe Advanced Logic System (ALS) technology is a safety system platform designed by CS Innovations. The focusof the ALS technology is to make a reliable and deterministic safety system that may be used in applications wheresafety is the focus. The ALS platform consists of control, input, output, and communication boards mounted in 19"sub-racks to provide a specific control solution.

The individual ALS boards are developed to be generic and can be configured for used in different applications. Theobjective is for CS Innovations to be able to develop and manufacture generic ALS boards to stock, and then laterintegrate them into dedicated systems.

The ALS platform is 19" rack mountable where sub-racks are configured with ALS boards to perform a specificfunction. A sub-rack backplane allows for intercommunication between the ALS boards and for ALS input and outputboards to connect to field signals. The field connectors will normally be accessible from the back side of the sub-rack.

Each ALS board is developed in an independent development flow with separate:

" Requirements

" Specifications

F CD

6002-00002-NP, Rev 4, August 11,2010 Non-Proprietary of 316002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary Page 5 of 31


CD

(D

The ALS board development may run in parallel or be spread out over time. CS Innovations adds additional, ALS

boards as needs and markets are identified. Figure 2: Multiple ALS Board Development Flow illustrates how ALSboard development is performed in parallel with additional, future board development being added as needed. Eachboard uses the same documentation structure.

Figure 2: Multiple ALS Board Development Flow

6002-00002-NP, Rev 4, August 11,2010 Non-Proprietary of 31


1.2.2 ALS Board Configuration ItemsThe ALS board itself consists of the following 3 Configuration Items (CIs):

Table 1: Ownership of ALS Board Cis

(D

1.2.3 Support Configuration Items

1.2.3.1 Hardware and software used for programming FPGA

The FPGA image is programmed/burned into the FPGA using the appropriate programming tool and librariesprovided by the FPGA manufacturer.

CD



K1.2.4 Other Configuration Items

1.2.5 LimitationsN/A

1.4 Terms and Abbreviations

~LcDIs'

I

A complete list of ALS Platform terms and abbreviations is provided in the CS Innovations, document 6002-00040:ALS Terms and Abbreviations (Reference 4).



2.1 OrganizationRefer to Reference 1 for information regarding the project organization.

2.2 CM Responsibilities

Refer to Reference 1 for information regarding CM roles and responsibilities.

2.3 Applicable policies, directives, and procedures

All activities performed in the ALS CM Plan shall be conducted in accordance with Reference 6 and Reference 1.



This page intentionally left blank.



3.1 Configuration IdentificationA Configuration Item (CI) is an object or collection of objects that are treated as a self-contained unit for the purposeof version control. Unique identifiers are assigned to all Cl's according to the document control procedures definedby Reference 6.

3.1.1 Configuration Items (Cis)All Cis associated with an ALS project are listed a set of Configuration Status Accounting documents. There is oneConfiguration Status Accounting document per board type. An example Configuration Status Account template ispresented in Appendix B. When an ALS board development is initiated, an Excel Spreadsheet containing theinformation similar to what is shown-in Appendix B is prepared and placed in:

CVS: /DO021ALS-xyz/docsl6002-xyz5O - ALS-xyz Configuration Status Accounting\6002-xyz5O - ALS-xyzConfiguration Status Accounting.xls"xyz" represents the board-type-number portion of the document's part number. For example, the ALS-102 board'sConfiguration Status Accounting part number would be 6002-10250, the ALS-302 would be 6002-30250, and so on.The Configuration Status Accounting document is maintained by the person responsible for ConfigurationManagement, generally the Project Manager.

As documents are completed and assigned a revision number the spreadsheet is updated to reflect the newestinformation. The Project Manager is responsible for identifying and adding Cl's to the spreadsheet as needed.

The Configuration Status Accounting document is printed to PDF files at milestones, baselines, and other points ofinterest during the board development and will later be used as a part of the CM report. The PDF printout must bereviewed and approved according to the document control procedure for baselines and releases.

CD

6002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary of 316002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary Page 11 of 31


CD



P

(D


AILS Configuration Management Plan CS InnovationsALS Configuration Management Plan CS Innovations

K3.1.1.2 Release Area

3.1.1.3 Baseline

3.1.2 Naming Configuration ItemsAll documents are assigned a unique CS Innovations Part Number. Documents are named:

I(D

CD


ALS Configuration Management Plan CS InnovationsALS Configuration Management Plan CS innovations

P

CD

3.1.2.1 Identification of the ALS board

0

CD



P

3.1.3 Acquiring Configuration ItemsAll configuration items are released under their revision number following the document control procedure describedby Reference 6.

3.1.4 Control of Software Tools

P

The exact revision number and storage location of each software tool used in the ALS development are tracked onthe Configuration Status Accounting spreadsheet.

3.2 Configuration Control

Configuration control describes the activities for requesting, evaluating, approving or disapproving, andimplementing changes to baseline configuration items.

3.2.1 Change ControlThe purpose of the change control activities is to ensure the recording, evaluation, resolution and approval ofchanges. The Cl must be baselined according to the schedule shown in Chapter 4.

Guidance includes:

1) Change control shall preserve the integrity of the configuration items by providing protection againstunauthorized change.

2) Change control shall ensure a change is assessed to determine whether or not the configuration identityneeds to be updated

3) Changes to configuration items under change control should be recorded, approved, and tracked.

4) Change control should ensure traceability of changes to the reason for the change

5) Change control should ensure that the impact of the change-is assessed to determine the effect of the changeon the outputs of the processes and that the output data is updated

6) Change control should ensure that feedback is provided to affected processes

P

(D

b'

6002-00002-NP, Rev 4, August11, 2010 Non-Proprietary of 316002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary Page 16 of 31


3.2.2 Change Control Prior to Baseline

3.2.3 Configuration Item Release, Archive and Retrieve"ActivitiesThe purpose of the release activity is to place data items under configuration management control to ensure thatonly authorized data is used in other activities, and to ensure that data items associated with the product can beretrieved in case of a need to duplicate, regenerate, re-test or modify the product.

CSI document control procedure (document number 9000-00600) must be followed for all releases.

3.2.4 Issue Reporting, Tracking and Corrective Action ActivitiesThe purpose of issue reporting, tracking and corrective action is to record problems and ensure correct dispositionand resolution. Problems may include non-compliance with specifications or standards, deficiencies of life cycleprocess outputs, anomalous behavior of products, and inadequacy or deficiency of tools and technology processes.Issue reporting should be implemented no later than the establishment of a baseline.

PC)

CD

3.2.5 Approval Authority - the Change Control Board (CCB)

CD 9


ALS Configuration Management Plan

3.3 Status Accounting

CS Innovations

3.5 Configuration Audits and Reviews

P

(D

3.5.2 Managerial Reviews

Il I

6002-00002-NP, Rev 4, August 11,2010 Non-Proprietary of3l6002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary Page 18 of 31


I 7w



The tools, techniques, and procedures identified in the ALS CM Plan are similar or identical to the proceduresdescribed in Reference 6. CS Innovations personnel require no additional training to follow the ALS CM Plan.

CD

6002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary of3l6002-00002-NP, Rev 4, August 11, 2010 Non-Proprietary Page 21 of 31


This plan may be amended as necessary. All revisions must be reviewed and approved following the documentcontrol procedure (Reference document number 9000-00600).

6.1 ResponsibilitiesThe Configuration Manager is responsible for monitoring the ALS CM Plan to ensure and request/perform changes ifneeded.

The Configuration Manager is responsible for maintaining the CM Report including the Configuration StatusAccounting documents.

6.2 Change ApprovalsAll changes to the ALS CM Plan must be reviewed by the Configuration Manager, reviewer and approver listed inthe approvals section. Changes are also reviewed by the Project Manager if he is not serving as the ConfigurationManager.


AILS Configuration Management Plan CS InnovationsALS Configuration Management Plan CS Innovations




CD



wpCD



P)

P)

CD



I

6002-00002-NP, Rev 4, August 11,2010 Non-Proprietary of 31

ALS Configuration Management Plan

6002-00002-NP, Rev 4, August 11, 2010

CS Innovations

a,pCD

Non-Proprietary Page3O of 31

Non-Proprietary of 31 -

ALS Configuration Management Plan ALS onfgurtio Mangemnt lanCS Innovations

CD

6002-00002-NP, Rev 4, August 11,2010 Non-Proprietary of316002-00002-N P, Rev 4, August 11, 2010 Non-Proprietary Page 31 of 31

* CS nnovaton

6002-00301 A Westinghouse Electric Company

U.S. Nuclear Regulatory CommissionDocument Control DeskWashington, DC 20555-0001

August 13, 2010

APPLICATION FOR WITHHOLDING PROPRIETARYINFORMATION FROM PUBLIC DISCLOSURE

Subject: CS Innovations ALS Topical Report and Supporting Documents Submittal Follow Up ofNon-proprietary Document Versions

Reference: Cover letter from Mr. David Dunsavage, Resource Manager, CS Innovations dated August13, 2010.

The Application for Withholding Proprietary Information from Public Disclosure is submitted by CSInnovations (CSI), pursuant to the provisions of paragraph (b)(1) of Section 2.390 of the Commission'sregulations. It contains commercial strategic information proprietary to CSI and customarily held inconfidence.

The proprietary material for which withholding is being requested is identified in the proprietary versionof the subject documents. In conformance with 10 CFR Section 2.390, an Affidavit accompanies thisapplication for withholding, setting forth the basis on which the identified proprietary information may bewithheld from public disclosure.

Accordingly, it is respectfully requested that the subject information which is proprietary to CSI bewithheld from public disclosure in accordance with 10 CFR Section 2.390 of the Commission'sregulations.

Correspondence with respect to this application for withholding or the accompanying affidavit shouldreference the cover letter and be sent to Mr. Joe Lorson - Program Manager, CS Innovations, 7400 E TierraBuena Ln, Suite 101, Scottsdale, AZ, 85260.

Sincerely,

David Dunsavage, Resource anagerCS Innovations

Enclosurescc: Joe Lorson, Program Manager

'~'CS Innv-ations

AFFIDAVIT

State of ArizonaCounty of Maricopa

Before me, the undersigned authority, personally appeared David Dunsavage, who, being by me dulysworn according to law, deposes and says that he is authorized to execute this Affidavit on behalf of CSInnovations (CSI), and that the averments of fact set forth in this Affidavit are true and correct to the bestof his knowledge, information, and belief:

David Dunsavage, Resource ane'-rCS Innovations

Sworn to and subsc~rdbefore me this _3dayof ,2010

Notary Public

Page 1 of 5

6002-00301

(1) 1 am the Resource Manager, CS Innovations (CSI), and as such, I have beenspecifically delegated the function of reviewing the proprietary information sought tobe withheld from public disclosure in connection with nuclear power plant licensingand rule making proceedings, and am authorized to apply for its withholding onbehalf of CSI.

(2) 1 am making this Affidavit in conformance with the provisions of 10 CFR Section2.390 of the Commission's regulations and in conjunction with the CSI "Applicationfor Withholding" accompanying this Affidavit.

(3) I have personal knowledge of the criteria and procedures utilized by CSI indesignating information as a trade secret, privileged or as confidential commercial orfinancial information.

(4) Pursuant to the provisions of paragraph (b)(4) of Section 2.390 of the Commission'sregulations, the following is furnished for consideration by the Commission indetermining the information sought to be withheld from public disclosure should bewithheld.

(i) The information sought to be withheld from public disclosure is ownedand been held in confidence by CSI.

(ii) The information is of a type customarily held in confidence by CSI andnot customarily disclosure to the public. CSI has a rational basis fordetermining the types of information customarily held in confidence by itand, in that connection, utilizes a system to determining when andwhether to hold certain types of information in confidence. Theapplication of that system and substance of that system constitutes CSIpolicy and provides the rational basis required.

Under that system, information is held in confidence if it falls in one ormore of several types, the release of which might result in the loss of anexisting or potential competitive advantage, as follows:

(a) The information reveals the distinguishing aspects of a process (orcomponent structure, tool, method, etc.) where prevention of its useby any of CSI's competitors without license from CSI constitutes acompetitive economic advantage over other companies.

(b) It consists of supporting data, including test data, relative to aprocess (or component, structure, tool, method, etc.) the applicationof which data secures a competitive economic advantage, e.g. byoptimization or improved marketability.

(c) Its use by a competitor would reduce his expenditure of resources orimprove his competitive position in the design, manufacture,shipment, installation, assurance of quality, or licensing a similarproduct.

(d) It reveals costs or price information, production capacities, budgetlevels, or commercial strategies of CSI, its customers or suppliers.

Page 2 of 5

6002-00301

(e) It reveals aspects of past, present, or future CSI or customer fundeddevelopment plans and programs of potential commercial value toCSI.

(f) It contains patentable ideas, for which patent protection may bedesirable.

There are sound policy reasons behind the CSI system which include thefollowing:

(a) The use of such information by CSI gives CSI a competitiveadvantage over its competitors. It is, therefore, withheld fromdisclosure to protect the CSI competitive position.

(b) It is information that is marketable in many ways. The extent towhich such information is available to competitors diminishes theCSI ability to sell products and services involving the use of theinformation.

(c) Use by our competitor would put CSI at a competitive disadvantageby reducing his expenditure of resources at our expense.

(d) Each component of proprietary information pertinent to a particularcompetitive advantage is potentially as valuable as the totalcompetitive advantage. If competitors acquire components ofproprietary information, any one component may be the key to theentire puzzle, thereby depriving CSI of a competitive advantage.

(e) The CSI capacity to invest corporate assets in research anddevelopment depends upon the success in obtaining and maintaininga competitive advantage.

(iii) The information is being transmitted to the Commission in confidenceand, under the provisions of 10 CFR Section 2.390, it is to be received inconfidence by the Commission.

(iv) The information sought to be protected is not available in public sourcesor available information has not been previously employed in the sameoriginal manner or method to the best of our knowledge and belief.

(v) The proprietary information sought to be withheld in this submittal isthat which is appropriately marked in the documents listed in the coverletter from Mr. David Dunsavage, Resource Manager, CS Innovationsdated August 13, 2010 and with the subject "CS Innovations ALSTopical Report and Supporting Documents Submittal Follow Up of Non-proprietary Document Versions". The information is being submitted insupport of a topical report submittal and is being transmitted by the coverletter mentioned prior and an Application for Withholding Proprietary

Page 3 of 5

6002-00301

Information from Public Disclosure, to the Nuclear RegulatoryCommission's Document Control Desk.

This information is part of that which will enable CSI to develop ageneric ALS platform for using in I E safety systems.

Further this information has substantial commercial value as follows:

(a) The information requested to be withheld reveals the distinguishingaspects of a methodology which was developed by CSI.

(b) The information requested to be withheld reveals trade secrets(c) The information requested to be withheld reveals details of CSI

intellectual property.(d) The information requested to be withheld reveals commercial

strategies

Public disclosure of this proprietary information is likely to causesubstantial harm to the competitive position of CSI because it wouldenhance the ability of competitors to provide similar products forcommercial power reactors without commensurate expenses. Also,public disclosure of the information would enable others to use theinformation to meet NRC requirements for licensing documentationwithout purchasing the right to use the information.

The development of the technology described in part by the informationis the result of applying the results of many years of experience in anintensive CSI effort and the expenditure of a considerable sum of money.

In order for competitors of CSI to duplicate this information, similartechnical programs would have to be performed and a significantmanpower effort, having the requisite talent and experience, would haveto be expended.

Further the deponent sayeth not.

Page 4 of 5

PROPRIETARY INFORMATION NOTICE

Transmitted herewith are proprietary and/or non-proprietary versions of documents furnished to the NRCin connection with requests for generic and/or plant-specific review and approval.

In order to conform to the requirements of 10 CFR 2.390 of the Commission's regulations concerning theprotection of proprietary information so submitted to the NRC, the information which is proprietary in theproprietary versions is contained within brackets, and where the proprietary information has been deletedin the non-proprietary versions, only the brackets remain (the information that was contained within thebrackets in the proprietary versions having been deleted). The justification for claiming the informationso designated as proprietary is indicated in both versions by means of lower case letters (a) through (f)located as a superscript immediately following the brackets enclosing each item of information beingidentified as proprietary or in the margin opposite such information. These lower case letters refer to thetypes of information CS Innovations customarily holds in confidence identified in Sections (4)(ii)(a)through (4)(ii)(f) of the affidavit accompanying this transmittal pursuant to 10 CFR 2.390(b)(1).

COPYRIGHT NOTICE

The reports transmitted herewith each bear a CS Innovations copyright notice. The NRC is permitted tomake the number of copies of the information contained in these reports which are necessary for itsinternal use in connection with generic and plant-specific reviews and approvals as well as the issuance,denial, amendment, transfer, renewal, modification, suspension, revocation, or violation of a license,permit, order, or regulation subject to the requirements of 10 CFR 2.390 regarding restrictions on publicdisclosure to the extent such information has been identified as proprietary by CS Innovations, copyrightprotection notwithstanding. With respect to the non-proprietary versions of these reports, the NRC ispermitted to make the number of copies beyond those necessary for its internal use which are necessary inorder to have one copy available for public viewing in the appropriate docket files in the public documentroom in Washington, DC and in local public document rooms as may be required by NRC regulations ifthe number of copies submitted is insufficient for this purpose. Copies made by the NRC must includethe copyright notice in all instances and the proprietary notice if the original was identified as proprietary.

Page 5 of 5