ECR Title: TTFSS v4 Fixes	DCC No: E1800016-v1
Date: 1/24/2018
Requester: Daniel Sigg	Impacted Subsystem(s):	SQZ
Description of Proposed Change(s): The proposed changes are described in E1700364-v2. Changes 1 through 4 were applied during board testing, but changes 5 through 10 need to be applied to all boards in the field.
Reason for Change(s): Several issues were found during the testing the first TTFSS V4, E1700069, when testing with the squeezer laser locking.
Estimated Cost: ~100$
Schedule Impact Estimate: small
Nature of Change (check all that apply): Hardware Safety Correct Hardware Correct Documentation	Improve Hardware/Software 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 hardware 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.): D1700077, D1700076.
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