Component Integration Review Checklist


Overview

Summary Sheet
AR000A
Vector_BSWs
Renesas_MCAL
AR100A
AR300A
AR400A
AR999A
CF009A
CF010A
CF012A
CF016A
CF017A
CF018A
CF025A
CM010A
CM100A
CM101A
CM102A
CM103A
CM104A
CM106A
CM107A
CM108A
CM111A
CM200A
CM300A
CM320A
CM340A
CM410A
CM455A
CM460A
CM475A
CM620A
CM640A
CM650A
CM660A
CM670A
CM680A
CM690A
CM700A
DF001A
ES002A
ES004A
ES005A
ES006A
ES008A
ES100A
ES101A
ES102A
ES104A
ES105A
ES106A
ES200A
ES208A
ES209A
ES210A
ES229A
ES239A
ES241A
ES247A
ES248A
ES249A
ES250A
ES259A
ES300A
ES311A
ES312A
ES320A
ES400A
ES999A
GM001A
GM002A
GM003A
MM000A
MM001A
MM005A
MM006A
MM007A
MM008A
MM009A
MM017A
MM018A
MM019A
MM500A
MM501A
MM502A
MM503A
MM504A
MM505A
MM506A
MM507A
NM001A
NM002A
NM004A
NM010A
NM100A
SF001A
SF002A
SF003A
SF005A
SF007A
SF009A
SF011A
SF012A
SF013A
SF014A
SF015A
SF016A
SF018A
SF019B
SF020A
SF021A
SF023A
SF027A
SF028A
SF029A
SF032A
SF033A
SF040A
SF042A
SF043A
SF044A
SF045A
SF048A
SF049A
SF050A
SF051A
SF053A
SF054A
SF102A
SF103A
SF104A
SF105A
SF106A
SF107A
SF108A
CustomData
Issue List
Revision History


Sheet 1: Summary Sheet
























Rev 1.03/10/2014

Component Integration Review Sheet



























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Change Request ID:


Many, see individual tabs





























Integration Steps
























































































































kzshz2: Intended Use: Identify who where the reviewers, what they reviewed, and if the reviewed changes have been approved to release the code for testing. Comments here should be at a highlevel, the specific comments should be present on the specific review form sheet. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. ADD DR Level Move reviewer and approval to individual checklist form Review Checklist Summary:



























Comments:

The calibration section was altered from the approved review checklist to better suit the process used by EA4.

Tab Colors:
Green: Reviewed and passing for this release
Gray: Reviewed and pssing on previous release





















































































General Guidelines:


- The reviews should be performed over the steps taken to integrate each of the SWC.
- If a section does not apply, select "N/A" in the Yes column and state why it did not apply.



































Abbreviations and Acronyms


- CIG: Component Integration Guidlines.































References



Document TitleVersionApplicable Sections


[1]Component Integration GuidelinesVersion 1.2All

Sheet 2: AR000A






















Rev 1.03/10/2014
SWC Integration Review for AR000A Integration Project

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 07.02.01

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9707, EA4#9679, EA4#9717, EA4#9718, EA4#9735, EA4#9740, EA4#9783, EA4#9817







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








N/A
Comments:









the required component version to be integrated.











Integration project is not a component
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Updated Core Voltage Monitor, EcuM settings.
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No Changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











Not a SWC
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not a SWC
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not a SWC
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











Not a SWC
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











Not a SWC
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not a SWC
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











Not a SWC
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











Not a SWC
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not a SWC
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











Not a SWC
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















Not a SWC








































General Notes / Comments:























EA4#9707: Add "TESTHWTQ_CNT_U08" rationality check for CPID 02

EA4#9679: Updates to CM112A - Core Voltage Monitor settings [Reviewed tasks 18170, 18247]

EA4#9717: Updates to CDD version 19.0.4_60 and generate function templates

EA4#9718: Update Rationality for DIDs $02, $90, $98, $99

EA4#9735: Davinci Configurator Settings changes to exclude Mcu_Init_RamSection function invocation in EcuM_AL_DriverInitOne function. In Davinci Configurator, DEM code has to be re-generated.

EA4#9740: Update Customer Part Numbers

EA4#9783: Add PIDs $4303, $4304 for Maximum Hand Wheel Angle Traveled

EA4#9817: Add DID A1

Removed EPS_AdcDiagc_ecuc.arxml

Software Version changes

Changes to Release Notes supporting documentation

























kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/13/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):


Lucas Wendling






































































Sheet 3: Vector_BSWs






















Rev 1.03/10/2014
SWC Integration Review for AR000A Integration Project

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. TL102A_Davinci_3.13.22.2_0
BswM_Vector_Ar4.0.3_08.00.00_0
Crc_Vector_Ar4.0.3_05.03.00_0
Dem_Vector_Ar4.1.2_11.01.00_0
Det_Vector_Ar4.0.3_07.01.00_0
EcuC_Vector_Ar4.0.3_04.01.00_0
EcuM_Vector_Ar4.0.3_07.00.00_0
Fee_Vector_Ar4.0.3_08.01.02_0
IoHwAb_Vector_Ar4.0.3_03.00.00_2
MemIf_Vector_Ar4.0.3_03.03.00_0
NvM_Vector_Ar4.0.3_05.05.00_0
Os_Vector_Ar4.0.3_01.06.08_0
WdgM_Vector_Ar4.0.3_03.03.03_2
Suprt_Vector_Bsw_02.01.00
Rte_Vector_4.12.0.0_1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8935

























































































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








X

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








X
Comments:









reviewed.













CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No changes in Nvm Blocks
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No changes in Nvm Blocks
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No changes in FEE configuration
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer











Imported BswM and WdgM
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











No changes
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











Not a SWC
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No changes






































TuningSets.arxml generated and imported into








X
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








N/A
Comments:
















Not a SWC








































General Notes / Comments:























EA4#8935: Integrate Vector SIP CBD1400351_D04

Reviewed all generated files (Tasks: EA4#16276, EA4#16277, EA4#16295)








































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 4: Renesas_MCAL






















Rev 1.03/10/2014
SWC Integration Review for AR000A Integration Project

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. Dio_Renesas_Ar4.0.3_01.00.11_0
Mcu_Renesas_Ar4.0.3_01.00.07_0
Port_Renesas_Ar4.0.3_01.05.02_0
Wdg_Renesas_Ar4.0.3_01.00.11_0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8936

























































































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








X

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Used settings from Selva/Lucas
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








X
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicabale to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







X
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer interface
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer interface
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer interface
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer interface
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer interface
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











No Developer interface
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











Not a SWC
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer interface
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























Settings for new components provided via email from Lucas and all settings were assummed to be previously reviewed and correct

Integration review focused not on generated MCAL config files but on other changes that were required for integration.








































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/23/16


































Lead Peer Reviewer:


Gustavo Nunes

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 5: AR100A






















Rev 1.03/10/2014
SWC Integration Review for AR100A NxtrMath

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9024







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer component
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer component
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer component
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer component
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer component
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer component
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/23/16


































Lead Peer Reviewer:


Gustavo Nunes

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 6: AR300A






















Rev 1.03/10/2014
SWC Integration Review for AR300A MotCtrlMgr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7773







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.













CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No additional considerations
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

10/07/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 7: AR400A






















Rev 1.03/10/2014
SWC Integration Review for AR400A NxtrStrtUp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9023







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer component
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer component
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer component
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer component
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer component
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer component
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























Startup component is source only

Required the addition of -nostartfiles to T1xx.gpj to remove GHS startup library files

Removed lowinit and startup source files from src folder as they have been replaced by this component




























kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/22/16


































Lead Peer Reviewer:


Gustavo Nunes

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 8: AR999A






















Rev 1.03/10/2014
SWC Integration Review for AR999A ArchGlbPrm

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5161







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.













CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator













CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








N/A
Comments:


























































General Notes / Comments:























Design update only, no source files changed


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/08/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 9: CF009A






















Rev 1.03/10/2014
SWC Integration Review for CF009A GmOvrlStMgr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 4.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9657







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No changes








































General Notes / Comments:























Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 10: CF010A






















Rev 1.03/10/2014
SWC Integration Review for CF010A GmTqArbn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9814







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source, Developer, Calibration update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 11: CF012A






















Rev 1.03/10/2014
SWC Integration Review for CF012A GmStrtStop

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6500







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Initial integration was from 1.2.0 to 1.3.0 which changed the names of the outputs

Update from 1.3.0 to 1.4.0 was a source only change from unit testing issue































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/19/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 12: CF016A






















Rev 1.03/10/2014
SWC Integration Review for CF016A GmVehSpdArbn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#2175







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No developer changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

05/06/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 13: CF017A






















Rev 1.03/10/2014
SWC Integration Review for CF017A GmVehPwrMod

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9040







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configurations
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No new runnables
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes in Client/Server ports
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








N/A
Comments:


























































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/23/16


































Lead Peer Reviewer:


Gustavo Nunes

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 14: CF018A






















Rev 1.03/10/2014
SWC Integration Review for CF018A GmRoadWhlInQlfr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8753







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/05/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 15: CF025A






















Rev 1.03/10/2014
SWC Integration Review for CF025A GmFctDiArbn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6553







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








X
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/19/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 16: CM010A






















Rev 1.03/10/2014
SWC Integration Review for CF010A GmT1xxMcuCfg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9455







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











This component is implemented directly in the integration project
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











This component is implemented directly in the integration project
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











This component is implemented directly in the integration project
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No client/server ports
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























Updates for port initializations


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 17: CM100A






















Rev 1.03/10/2014
SWC Integration Review for CM100A StrtUpSeq

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9456







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer component
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer component
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer component
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer component
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer component
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer component
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























Design update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 18: CM101A






















Rev 1.03/10/2014
SWC Integration Review for CM101A ExcpnHndlg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 4.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7356







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











None
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 19: CM102A






















Rev 1.03/10/2014
SWC Integration Review for CM102A FlsMem

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 5.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7355







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No changes
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No developer updates
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No developer updates






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 20: CM103A






















Rev 1.03/10/2014
SWC Integration Review for CM103A RamMem

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7205







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Required removal of SPI double bit ecc error interrupt notification


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

08/26/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 21: CM104A






















Rev 1.03/10/2014
SWC Integration Review for CM104A EcmOutpAndDiagc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 4.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7072







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











Source-only update
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











Source-only update
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Source-only update
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











Source-only update
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











Source-only update
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

08/26/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 22: CM106A






















Rev 1.03/10/2014
SWC Integration Review for CM106A McuCoreCfgAndDiagc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5361







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











Source-only update
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











Source-only update
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Source-only update
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











Source-only update
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











Source-only update
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























This was a source only update that did not require any changes beyond using the newest version in Synergy


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/18/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 23: CM107A






















Rev 1.03/10/2014
SWC Integration Review for CM107A GuardCfgAndDiagc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5156







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Using latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.













CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No change
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











No change
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator













CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No RTE changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








N/A
Comments:


























































General Notes / Comments:























Source only change - no integration work required other than to update component version


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/08/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 24: CM108A






















Rev 1.03/10/2014
SWC Integration Review for CM108A DataAndAdrPar

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5157







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Only version available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.













CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











No change
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator













CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No RTE changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








N/A
Comments:


























































General Notes / Comments:























Source only change - no integration work required other than to update component version


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/08/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 25: CM111A






















Rev 1.03/10/2014
SWC Integration Review for CM111A VrfyCritReg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5512







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








X

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 26: CM200A






















Rev 1.03/10/2014
SWC Integration Review for CM200A DmaCfgAndUse

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5395







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























This was a source only update that did not require any changes beyond using the newest version in Synergy


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 27: CM300A






















Rev 1.03/10/2014
SWC Integration Review for CM300A Adc0CfgAndUse

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7714







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No changes
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No developer updates
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No developer updates






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 28: CM320A






















Rev 1.03/10/2014
SWC Integration Review for CM320A Adc1CfgAndUse

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7715







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No changes
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No developer updates
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No developer updates






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 29: CM340A






















Rev 1.03/10/2014
SWC Integration Review for CM340A AdcDiagc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9658







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








X

Comments:









of the SWC.











Executed integrate.bat and removed required files. Informed component team on the updates needed for next version.
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Configurator settings modified to remove AdcDiagc generation
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























Source, Davinci Configurator changes [Reviewed tasks 18151, 18363]


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 30: CM410A






















Rev 1.03/10/2014
SWC Integration Review for CM410A SnsrMeasStrt

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8856







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change to NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change to NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No change to NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 31: CM455A






















Rev 1.03/10/2014
SWC Integration Review for CM455A Tauj0CfgAndUse

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4876







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No change
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.











None
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























This was a source only update that required no changes to the integration project


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

03/24/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 32: CM460A






















Rev 1.03/10/2014
SWC Integration Review for CM460A Tauj1CfgAndUse

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4877







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No change
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.











None
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:























This was a source only update that required no changes to the integration project


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

03/24/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 33: CM475A






















Rev 1.03/10/2014
SWC Integration Review for CM475A TSG31CfgAndUse

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7716







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No changes
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No developer updates
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No developer updates






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 34: CM620A






















Rev 1.03/10/2014
SWC Integration Review for CM620A MotAg0Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8882







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











Cno configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change to NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change to NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No change to NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 35: CM640A






















Rev 1.03/10/2014
SWC Integration Review for CM640A MotAg1Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4880







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











Cno configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change to NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change to NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











None
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











No change
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No change
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No change to NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

03/24/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 36: CM650A






















Rev 1.03/10/2014
SWC Integration Review for CM650A HwTq0Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.8.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8862







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 37: CM660A






















Rev 1.03/10/2014
SWC Integration Review for CM660A HwTq1Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.7.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8859







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 38: CM670A






















Rev 1.03/10/2014
SWC Integration Review for CM670A HwAg1Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.8.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6453







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No configuration files changed
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration files changed
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 39: CM680A






















Rev 1.03/10/2014
SWC Integration Review for CM680A HwTq2Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.1.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8860







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch files
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 40: CM690A






















Rev 1.03/10/2014
SWC Integration Review for CM690A HwAg0Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.8.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6453







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No configuration files changed
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration files changed
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 41: CM700A






















Rev 1.03/10/2014
SWC Integration Review for CM700A HwTq3Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.1.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8861







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch files
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 42: DF001A






















Rev 1.03/10/2014
SWC Integration Review for DF001A FltInj

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7707







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 43: ES002A






















Rev 1.03/10/2014
SWC Integration Review for ES002A McuDiagc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7886







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











Co changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

10/07/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 44: ES004A






















Rev 1.03/10/2014
SWC Integration Review for ES004A PwrUpSeq

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9443







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design, Source, Developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 45: ES005A






















Rev 1.03/10/2014
SWC Integration Review for ES005A TmplMonr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.6.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8927







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration setting changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source, Developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 46: ES006A






















Rev 1.03/10/2014
SWC Integration Review for ES006A Nvm

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7935







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








X

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Updated NvM MultiBlkCallBack to match new name
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.













CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

10/07/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 47: ES008A






















Rev 1.03/10/2014
SWC Integration Review for ES008A PwrSply

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7739







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No Batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 48: ES100A






















Rev 1.03/10/2014
SWC Integration Review for ES100A SysStMod

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5155







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No appicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Only change to source was two name changes on inputs - both were mapped back to the same outputs from CF017A


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/08/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 49: ES101A






















Rev 1.03/10/2014
SWC Integration Review for ES101A DiagcMgr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 4.5.0


















.





Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8734







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








X

Comments:









of the SWC.











Ran the integration batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS Settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








X
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







X
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








X
Comments:



NvM created by Configurator













CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source Code, Developer and Configurator updates


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 50: ES102A






















Rev 1.03/10/2014
SWC Integration Review for ES102A PolarityCfg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.0.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5632







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.













CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

05/06/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 51: ES104A






















Rev 1.03/10/2014
SWC Integration Review for ES104A XcpIf

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.0.3

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7345







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 52: ES105A






















Rev 1.03/10/2014
SWC Integration Review for ES105A StHlthSigNorm

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8027







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes to groups






































Calibration ports linked properly in Developer.








N/A
Comments:
















No changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

10/14/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 53: ES106A






















Rev 1.03/10/2014
SWC Integration Review for ES106A StHlthSigStc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.2.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8894, EA4#8906







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No change
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable fot T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No change
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No change
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No change
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source, Developer updates

Reviewed 2.2.0 and 2.2.1 version integrations































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 54: ES200A






















Rev 1.03/10/2014
SWC Integration Review for ES200A CurrMeas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 4.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8869







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No changes to NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No changes to NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/09/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 55: ES208A






















Rev 1.03/10/2014
SWC Integration Review for ES208A CurrMeasArbn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.6.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#4889







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























This was a source only update that required no changes to the integration project


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

03/24/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 56: ES209A






















Rev 1.03/10/2014
SWC Integration Review for ES209A CurrMeasCorrln

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7708







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 57: ES210A






















Rev 1.03/10/2014
SWC Integration Review for ES210A EcuTMeas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5657







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No devloper changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No devloper changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No devloper changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No devloper changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No devloper changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No devloper changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only change


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

05/06/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 58: ES229A






















Rev 1.03/10/2014
SWC Integration Review for ES229A HwTqCorrln

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8019







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

10/14/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 59: ES239A






















Rev 1.03/10/2014
SWC Integration Review for ES239A HwAgCorrln

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5465







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update only - no change


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):




































Other Reviewer(s):










































































Sheet 60: ES241A






















Rev 1.03/10/2014
SWC Integration Review for ES241A MotAg2Meas

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.6.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9422







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No devloper changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 61: ES247A






















Rev 1.03/10/2014
SWC Integration Review for ES247A MotAgCmp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8716







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer











Latest SW component integrated
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not applicable
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes in runnables
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes in ports
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source and developer changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/05/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 62: ES248A






















Rev 1.03/10/2014
SWC Integration Review for ES248A MotAgArbn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.0.2

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6586







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS Settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/18/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 63: ES249A






















Rev 1.03/10/2014
SWC Integration Review for ES249A MotAgCorrln

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 4.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5398, EA4#5429







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























New outputs are provided for SoH updates that are not yet integrated so outputs were intentionally left disconnected

Discovered an implementation issue while reviewing the integration of version 4.0.0 that was quickly resolved for version 4.1.0 of component































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/19/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 64: ES250A






















Rev 1.03/10/2014
SWC Integration Review for ES250A BattVltg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7122







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS Settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Devloper changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Devloper changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Devloper changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Devloper changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Devloper changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Devloper changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update only


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

08/26/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 65: ES259A






















Rev 1.03/10/2014
SWC Integration Review for ES259A BattVltgCorrln

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6513







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS Settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








X
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








X
Comments:
















No calibration changes








































General Notes / Comments:























Added new NTC 0x03D


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/19/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 66: ES300A






















Rev 1.03/10/2014
SWC Integration Review for ES300A SinVltgGenn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6587







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/18/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 67: ES311A






















Rev 1.03/10/2014
SWC Integration Review for ES311A GateDrv0Ctrl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9458







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch files
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design, Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 68: ES312A






















Rev 1.03/10/2014
SWC Integration Review for ES312A GateDrv1Ctrl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9457







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch files
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design, Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 69: ES320A






















Rev 1.03/10/2014
SWC Integration Review for ES320A MotDrvDiagc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5469, EA4#







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Outputs were added for state of health which is not integrated yet so they were left disconnected

A minor issue was observed during integration of 1.4.0 that was repaired and rolled in as 1.5.0. This was a source only change so the review from 1.4.0

was retained above.




























kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):




































Other Reviewer(s):










































































Sheet 70: ES400A






















Rev 1.03/10/2014
SWC Integration Review for ES400A TunSelnMgmt

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7346







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








X

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 71: ES999A






















Rev 1.03/10/2014
SWC Integration Review for ES999A ElecGlbPrm

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 6.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6587







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/18/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 72: GM001A






















Rev 1.03/10/2014
SWC Integration Review for GM001A ChkPt

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.7.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7926







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No new server runnables
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

10/07/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 73: GM002A






















Rev 1.03/10/2014
SWC Integration Review for GM002A PartNr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.7.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7924







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No additional considerations
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











New Init1 runnable
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No change
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

10/07/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 74: GM003A






















Rev 1.03/10/2014
SWC Integration Review for GM003A CustDiagc

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.15.0, 0.16.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9782, EA4#9816







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Dem re-generated due to FreezeFrame Data changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No new calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source, Developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/13/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 75: MM000A






















Rev 1.03/10/2014
SWC Integration Review for MM000A SerlComInpProxy

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.7.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9246







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Reviewed OS changes that fixed DaVinci configurator warning [Task ID: 17407]


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/10/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 76: MM001A






















Rev 1.03/10/2014
SWC Integration Review for MM001A GmMsg0C5BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer updates
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer updates
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer updates
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer updates
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer updates
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer updates
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/16/16


































Lead Peer Reviewer:


Willy Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 77: MM005A






















Rev 1.03/10/2014
SWC Integration Review for MM005A GmMsg180BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Only PIM changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 78: MM006A






















Rev 1.03/10/2014
SWC Integration Review for MM006A GmMsg1E9BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Only PIM changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 79: MM007A






















Rev 1.03/10/2014
SWC Integration Review for MM007A GmMsg1F1BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9766







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No changes








































General Notes / Comments:























Source, Developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 80: MM008A






















Rev 1.03/10/2014
SWC Integration Review for MM008A GmMsg1F5BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Only PIM changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 81: MM009A






















Rev 1.03/10/2014
SWC Integration Review for MM009A GmMsg214BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 82: MM017A






















Rev 1.03/10/2014
SWC Integration Review for MM017A GmMsg180BusChassisExp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 83: MM018A






















Rev 1.03/10/2014
SWC Integration Review for MM018A GmMsg182BusChassisExp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 84: MM019A






















Rev 1.03/10/2014
SWC Integration Review for MM019A GmMsg337BusChassisExp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5511







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 85: MM500A






















Rev 1.03/10/2014
SWC Integration Review for MM500A SerlComOutpProxy

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.8.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7336







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 86: MM501A






















Rev 1.03/10/2014
SWC Integration Review for MM501A GmMsg148BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6567







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/19/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 87: MM502A






















Rev 1.03/10/2014
SWC Integration Review for MM502A GmMsg184BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8879







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not Applicable
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








X
Comments:
















Calibration port and connections removed








































General Notes / Comments:























Source, Developer and Calibration updates

Removal of unused Hands on wheel calibration































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 88: MM503A






















Rev 1.03/10/2014
SWC Integration Review for MM503A GmMsg1E5BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.8.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9247







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/10/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 89: MM504A






















Rev 1.03/10/2014
SWC Integration Review for MM504A GmMsg778BusHiSpd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8956







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 90: MM505A






















Rev 1.03/10/2014
SWC Integration Review for MM505A GmMsg1CABusChassisExp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7333







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 91: MM506A






















Rev 1.03/10/2014
SWC Integration Review for MM506A GmMsg1E5BusChassisExp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.8.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9247







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.













CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/10/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 92: MM507A






















Rev 1.03/10/2014
SWC Integration Review for MM507A GmMsg335BusChassisExp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7334







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS configuration
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/01/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 93: NM001A






















Rev 1.03/10/2014
SWC Integration Review for NM001A CmnMfgSrv

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.20.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9032







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not required
CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











No change
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











Ports for new BMW handwheel torque component intentionally left disconnected
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/23/16


































Lead Peer Reviewer:


Gustavo Nunes

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 94: NM002A






















Rev 1.03/10/2014
SWC Integration Review for NM002A CmnMfgSrvIf

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9031







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Regenerated for MISRA fix in .tt file
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not required
CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











Removed periodic, added empty init to end of Appl6 init task
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No change
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvMs
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/22/16


































Lead Peer Reviewer:


Gustavo Nunes

Approved by Reviewer(s):




Yes






























Other Reviewer(s):










































































Sheet 95: NM004A






















Rev 1.03/10/2014
SWC Integration Review for NM004A NxtrCalIds

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5278







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








X
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/18/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):




































Other Reviewer(s):










































































Sheet 96: NM010A






















Rev 1.03/10/2014
SWC Integration Review for NM010A ProgMfgSrv

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 0.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5821







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibrations






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibrations






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibrations








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

06/14/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 97: NM100A






















Rev 1.03/10/2014
SWC Integration Review for NM100A MotVelCtrl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6798







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

08/12/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 98: SF001A






















Rev 1.03/10/2014
SWC Integration Review for SF001A Assi

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7199







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








X
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :





































Lead Peer Reviewer:





Approved by Reviewer(s):




































Other Reviewer(s):










































































Sheet 99: SF002A






















Rev 1.03/10/2014
SWC Integration Review for SF002A Rtn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8731







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Init runnable mapped to Appl10
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A

Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not applicable
CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.











Init runnable mapped to Appl10
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source and developer changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/05/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 100: SF003A






















Rev 1.03/10/2014
SWC Integration Review for SF003A Dampg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8846







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 101: SF005A






















Rev 1.03/10/2014
SWC Integration Review for SF005A StOutpCtrl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8848







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.











Changed the periodics execution order in Appl10 2ms Task
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes in Client/Server ports
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source code, Developer and Configurator updates


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 102: SF007A






















Rev 1.03/10/2014
SWC Integration Review for SF007A SysFricLrn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9815







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.











Initial value changed for a calibration






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No changes








































General Notes / Comments:























Source, Developer update

Reviewed Task 18366: Add RamBlock, NvM Proxy Configurator updates, Dem Generation































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 103: SF009A






















Rev 1.03/10/2014
SWC Integration Review for SF009A DutyCycThermProtn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7878







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS setttings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

10/07/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 104: SF011A






















Rev 1.03/10/2014
SWC Integration Review for SF011A EotLrng

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 3.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8929







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








X
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







X
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








X
Comments:



NvM created by Configurator













CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No change






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source, NvM, Calibration update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 105: SF012A






















Rev 1.03/10/2014
SWC Integration Review for SF012A HysCmp

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9465







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No changes
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS changes
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NVM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Design-only change
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design, Source, Developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 106: SF013A






















Rev 1.03/10/2014
SWC Integration Review for SF013A PullCmpActv

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9720







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No changes








































General Notes / Comments:























Source, Developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 107: SF014A






















Rev 1.03/10/2014
SWC Integration Review for SF014A InertiaCmpVel

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.10.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9417







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











Design-only change
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











Design-only change
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











Design-only change
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











Design-only change
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Design-only change
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











Design-only change
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 108: SF015A






















Rev 1.03/10/2014
SWC Integration Review for SF015A WhlImbRejctn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.10.0, 1.11.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9813, EA4#9850







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








X
Comments:









the requirements of the SWC and program.













CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







X
Comments:









NvM blocks. CRC's and other checks are applied













as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








X
Comments:



NvM created by Configurator













CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No changes








































General Notes / Comments:























Source, Developer, Configurator update

Reviewed Task 18404: Fix for 0xA5 NTC setting































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/14/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 109: SF016A






















Rev 1.03/10/2014
SWC Integration Review for SF016A VehSpdLimr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5588







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











Design-only change
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











Design-only change
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Design-only change
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











Design-only change
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











Design-only change
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











Design-only change
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











Design-only change
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only change


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

05/06/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 110: SF018A






















Rev 1.03/10/2014
SWC Integration Review for SF018A EotProtn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.7.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8015







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








N/A
Comments:









the required component version to be integrated.











Design only updates
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design only updates


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

10/14/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 111: SF019B






















Rev 1.03/10/2014
SWC Integration Review for SF019B PwrLimr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5162







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.













CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports











No client/server ports
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Only initial value changes - nothing needed except to import the latest DCF


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/08/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 112: SF020A






















Rev 1.03/10/2014
SWC Integration Review for SF020A HwAgTrakgServo

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7741







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 113: SF021A






















Rev 1.03/10/2014
SWC Integration Review for SF021A HwAgTrajGen

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5472







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 114: SF023A






















Rev 1.03/10/2014
SWC Integration Review for SF023A TunSelnAuthy

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6517







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change to existing block
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change to existing block
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM change for this update
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








X
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/19/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 115: SF027A






















Rev 1.03/10/2014
SWC Integration Review for SF027A EotProtnFwl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7751







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 116: SF028A






















Rev 1.03/10/2014
SWC Integration Review for SF028A_AssiHiFrq_Impl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9499







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source, Developer, Calibration update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 117: SF029A






















Rev 1.03/10/2014
SWC Integration Review for SF029A_StabyCmp_Impl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9765







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source, Developer, Calibration update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 118: SF032A






















Rev 1.03/10/2014
SWC Integration Review for SF032A MotTqCmdSca

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7753







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS Settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 119: SF033A






















Rev 1.03/10/2014
SWC Integration Review for SF033A VehSigCdng

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.3.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8732







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change to existing block
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change to existing block
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not Applicable
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No new runnables
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No new client/server ports
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM change for this update
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No cal changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No cal changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No cal changes








































General Notes / Comments:























Source and developer changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/05/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 120: SF040A






















Rev 1.03/10/2014
SWC Integration Review for SF040A MotVel

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8889







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch files
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source, Developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 121: SF042A






















Rev 1.03/10/2014
SWC Integration Review for SF042A HwAgSnsrls

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.4.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8636







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NVM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NVM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not Applicable
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes in tuning sets






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source and Developer changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/05/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 122: SF043A






















Rev 1.03/10/2014
SWC Integration Review for SF043A TqOscn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9467







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Design, Source, Developer, Calibration update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 123: SF044A






















Rev 1.03/10/2014
SWC Integration Review for SF044A HowDetn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8827







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NVM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NVM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not Applicable
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No change in runnables
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source Code, Developer and Calibration updates

Mapping of HowDetnOffThd, HowDetnOffTi cals to Region 2 Online Group C































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/09/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 124: SF045A






















Rev 1.03/10/2014
SWC Integration Review for SF045A HwAgSysArbn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9719







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NVM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NVM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source, developer update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

02/12/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 125: SF048A






















Rev 1.03/10/2014
SWC Integration Review for SF048A TqLoa

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9420







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 126: SF049A






















Rev 1.03/10/2014
SWC Integration Review for SF049A LoaMgr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8715







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change to existing block
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change to existing block
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











Not Applicable
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM change for this update
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No cal changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No cal changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No cal changes








































General Notes / Comments:























Source and developer changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/05/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 127: SF050A






















Rev 1.03/10/2014
SWC Integration Review for SF050A MotTqTranlDampg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5474







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/26/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 128: SF051A






















Rev 1.03/10/2014
SWC Integration Review for SF051A SnsrOffsLrng

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8907







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No change to existing block
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable to T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No change to existing block
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM change for this update
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








N/A
Comments:
















No new ports added








































General Notes / Comments:























Source, calibration initial value update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 129: SF053A






















Rev 1.03/10/2014
SWC Integration Review for SF053A HwAgVehCntrTrim

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.5.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#8891







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM changes
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM changes
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No changes
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Source, Developer, Calibration update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

12/16/16


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 130: SF054A






















Rev 1.03/10/2014
SWC Integration Review for SF054A PwrpkCmpbltyChk

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.0.1

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#7754







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available version
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

09/28/16


































Lead Peer Reviewer:


Hari Mattupalli

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 131: SF102A






















Rev 1.03/10/2014
SWC Integration Review for SF102A MotCtrlPrmEstimn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5428







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











Co configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








X
Comments:



Configurator project.



















































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

04/19/16


































Lead Peer Reviewer:


Lucas Wendling

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 132: SF103A






















Rev 1.03/10/2014
SWC Integration Review for SF103A MotRefMdl

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.0.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6503







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/19/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 133: SF104A






















Rev 1.03/10/2014
SWC Integration Review for SF104A MotCurrRegCfg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9424







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











No configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No new runnables
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Design, Source changes


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 134: SF105A






















Rev 1.03/10/2014
SWC Integration Review for SF105A MotCurrRegVltgLimr

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Hari Mattupalli
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 2.1.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9479







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








X

Comments:









meet program needs and requirements.













CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM change
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








X
Comments:



Developer project.



















































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No changes






































Calibration ports linked properly in Developer.








X
Comments:


























































General Notes / Comments:























Design, Source, Developer, Calibration update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Hari Mattupalli
Review Date :

01/27/17


































Lead Peer Reviewer:


Jared Julien

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 135: SF106A






















Rev 1.03/10/2014
SWC Integration Review for SF106A MotRplCoggCfg

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#6575







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











Co configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

07/19/16


































Lead Peer Reviewer:


Willie Haywood

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 136: SF107A






















Rev 1.03/10/2014
SWC Integration Review for SF107A MotRplCoggCmd

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.3.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#9024







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











Co configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








N/A
Comments:



Developer











No Developer changes
CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








N/A
Comments:



considerations required have been performed and reviewed.











No Developer changes
CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








N/A
Comments:



version used for the SWC.











No Developer changes
CIG Section 4.4




































All runnables of the SWC mapped to the correct








N/A
Comments:



application, task, and order within the task.











No Developer changes
CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








N/A
Comments:



required ports











No Developer changes
CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








N/A
Comments:



changes were in line with the changes made by the SWC











No Developer changes
CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:























Source only update


































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

12/23/16


































Lead Peer Reviewer:


Gustavo Nunes

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 137: SF108A






















Rev 1.03/10/2014
SWC Integration Review for SF108A MotCurrPeakEstimn

























Change Owner:


kzshz2: Intended Use: Identify the developer who made the change(s) Rationale: A change request may have more than one resolver, this will help identify who made what change. Change owner identification may be required by indusrty standards. Jared Julien
Component Revision:


kzshz2: Intended Use: Identify which Synergy revision of this component is being reviewed Rationale: Required for traceability. It will help to ensure this form is not attaced to the the wrong change request. 1.2.0

























Change Request ID:


Smith, Kevin: Defaults to the CR number on the summary sheet. If a different number is required, overwrite the cell with the correct value. EA4#5584







































Quality Check Items:

































YesNo











Configurator Changes (Group Review)SWC downloaded from Synergy and version matches








X
Comments:









the required component version to be integrated.











Latest available
CIG Section 4.1




































If available, run the integrate batch file in the tools folder








N/A

Comments:









of the SWC.











No batch file
CIG Section 4.2




































Smith, Kevin: Since each program has specific needs when it comes to the configuration of the SWC the item is pretty wide in scope. But the intent is for the integrator to review the settings and rationale behind those choices with the reviewer. Any comments/questions shall be documented below and followed up before completeing the integration task. All conifguration settings reviewed for the SWC to








N/A

Comments:









meet program needs and requirements.











Co configuration settings
CIG Section 4.2, SWC Integration guide.




































OS: If required, the changes made in the OS files are








N/A
Comments:









reviewed.











No OS settings
CIG Section 5.2




































NvM: If required, NvM blocks are conifgured to meet








N/A
Comments:









the requirements of the SWC and program.











No NvM
CIG Section 7.2.1




































Ea:If applicable, Ea configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











Not applicable for T1xx
as required.












CIG Section 7.2.2.1














































FEE:If applicable, FEE configured with the new SWC







N/A
Comments:









NvM blocks. CRC's and other checks are applied











No NvM
as required.












CIG Section 7.2.2.1















































Developer Changes (Group Review)Import the SWC that is required to integrate into








X
Comments:



Developer













CIG Section 4.3




































Per the integration guidelines for the SWC, all additional








X
Comments:



considerations required have been performed and reviewed.













CIG Section 4.3.1




































Imported Std_Workspace that meets or exceeds the








X
Comments:



version used for the SWC.













CIG Section 4.4




































All runnables of the SWC mapped to the correct








X
Comments:



application, task, and order within the task.













CIG Section 5.1, SWC FDD




































SWC Service and Client/Server ports mapped to








X
Comments:



required ports













CIG Section 6.2, SWC FDD/Integration Guide




































NvM: If applicable, create NvM block mapping for







Smith, Kevin: If NvM changes are NOT required for this integration, all NvM items can be marked "NO" with "No NvM Changes" in the comments section.
N/A
Comments:



per-instance memory items in the SWC











Not applicable for EA4
CIG Section 7.1




































NvM: Import generated component descriptions for the








N/A
Comments:



NvM created by Configurator











No NvM
CIG Section 7.2.4




































RTE Generated an all file changes were compared and








X
Comments:



changes were in line with the changes made by the SWC













CIG Section 8





































Calibration Changes (Group Review)CalComponent.arxml regenerated and imported into








N/A
Comments:



Developer project.











No calibration changes






































TuningSets.arxml generated and imported into








N/A
Comments:



Configurator project.











No calibration changes






































Calibration ports linked properly in Developer.








N/A
Comments:
















No calibration changes








































General Notes / Comments:



























































kzshz2: Intended Use: Identify who where the reviewers and if the reviewed changes have been approved. Rationale: Since this Form will be attached to the Change Request it will confirm the approval and provides feedback in case of audits. Group Review Level: There are four Design Review States that a document may have as follows: DR1 – Un-reviewed document. The DR1 reviews usually require larger, cross functional review teams (i.e. Management, Hardware Engineering, etc.) It is usually advisable, but not required to include outside representation as well such as system engineers. It is up to the document owner to decide on the scope of the review, however, the peer group can decide that a re-review with additional team member is required. DR2 – The Document has previously passed through the peer review process, but requires design changes significant enough to require another group peer review. DR3 – The Document has passed group peer review but needs minor corrections that can be re-reviewed with the Lead Peer Reviewer. DR4 – The document has passed all peer reviews and is ready for release. Review Board:


























Change Owner:

Jared Julien
Review Date :

05/06/16


































Lead Peer Reviewer:


Kevin Smith

Approved by Reviewer(s):



Yes































Other Reviewer(s):










































































Sheet 138: CustomData

SrlComOutput
Column A can be used to add integration specific components to the review list since this list will be different for each application.
SrlComInput

SER


Sheet 139: Issue List

Issue #DateIssueCreated ByResolvedResolved DateReviewed ByAdditional Comments

13/18/2016ADC0 diagnostic consistantly settingJaredYes3/18/2016LucasTurned out to be a disconnected signal in MotCtrlMgr - corrected during review.

2








3








4








5








6








7








8








9








10








11








12








13








14








15








16








17








18








19








20








21








22








23








24








25








26








27








28








29








30








31








32








33








34








35








36








37








38








39








40









Sheet 140: Revision History

Sl. No.DescriptionAuthorVersionDateApproved By
1Initial Version
1

2Updated the revision of referance document "Component Integration Guidelines" from 1.0 to 1.2M. Mehta1.117-Jul-14










































Last modified October 12, 2025: Initial commit (312cf32)