ECR Title: Acquisition of FSS RFPD DC signal	DCC No: E1400002-v1
Date: 3 January 2014
Requester: Kiwamu Izumi	Impacted Subsystem(s): PSL, LSC
Description of Proposed Change(s): Implementation of a filter module for acquiring the FSS RFPD DC signal in the pslfss realtime model. Removal of a temporary filter module for the FSS RFPD DC signal from the lsc realtime model.
Reason for Change(s): The FSS RFPD DC signal needs to be read through the pslfss realtime model. In fact, an ADC channel (i.e. ADC_1_6) and physical cables have been reserved for the signal (see D1100367 and h1pslfss model at rev.6343), although they have not been used due to convenience during the past commissioning tests. Currently, the signal is acquired through the lsc model temporarily and this should be deleted to avoid conflicts in the digital systems.
Estimated Cost: None
Schedule Impact Estimate: None
Nature of Change (check all that apply): Safety Correct Hardware Correct Documentation	Improve Hardware Improve/Clarify Documentation Change Interface Change Requirement
Importance: Desirable for ease of use, maintenance, safety Desirable for improved performance, reliability Essential for performance, reliability Essential for function Essential for safety	Urgency: No urgency Desirable by date/event: ____________ Essential by date/event: ____________ Immediately (ASAP)
Impacted Hardware (select all that apply): Repair/Modify. List part & SNs: ______________________ Scrap & Replace. List part & SNs:_____________________ Installed units? List IFO, part & SNs: _________________ Future units to be built	Impacted Documentation (list all dwgs, design reports, test reports, specifications, etc.): None
Disposition of the proposed change(s): The disposition of this proposed engineering change request is to be completed by Systems Engineering and indicated in the “Notes and Changes” metadata field in the DCC entry for this ECR. The typical dispositions are as follows: Additional Information Required: in which case the additional information requested is defined. The ECR requester then re-submits the ECR with the new information using the same DCC number for the ECR but with the next version number. Rejected: in which case the reason(s) for the rejection are to be given Approved Approved with Caveat(s): in which case the caveat(s) are listed TRB: the ECR is referred to an ad-hoc Technical Review Board for further evaluation and recommendation. It is the System Engineer’s (or designee’s) responsibility to organize the TRB. The System Engineer (or designee) then makes a technical decision based on the TRB’s recommendation. Links to the TRB’s documentation (charge, memos, final report, etc.) are to be added to the “Related Documents” field for this ECR. CCB: a change request for approval of additional funds or schedule impact is to be submitted to the Configuration Control Board. Links to the CCB’s documentation (CR, etc.) are to be added to the “Related Documents” field for this ECR. Concurrence by Project Management: Acknowledgement/acceptance/approval of the disposition is to be indicated by the electronic “signature” feature in the DCC entry for this ECR, by one the following personnel: Systems Scientist Systems Engineer Deputy Systems Engineer