Had discussed with Ezhil about releasing Data management sections like par file tab enabled, Hardware part number for Rapid Prime BSVI, ECU configuration & mapping, etc..

Meeting Session with Ezhil: Rapid Prime Tools Deployment in production 

1) Changed the file name of verification (.ver) file and report file (.vrp) to generate with order number and VIN number and performed the testing the same with an order number.2) In the result screen, display the fault code list that is read from the veps report (.vrp) file. 3) Latest code changes are deployed separately in the dev server with port 8093.4) Debug Session and Performed testing to validate the changes.

CIT Web Tool Deployment in Production Server.

Testing the CIT tool along with Ezhil by creating an order number 14010999 and VIN MEC829MFXX0126247.

Reverted back the dynamic system VEPS execution changes as requested by Ezhil as he is doing the vehicle testing.

Made changes in the application to run VEPS automatically in any client system instead of configuring each and every system through INI settings file.

Testing CIT Veps web tool along with Ezhil (DICV)

1. Testing CIT Tool along with Ezhil2. Supported in releasing part number in CDMT for Vehicle level testing.

Coordination with Ezhil on testing CIT tool.

Coordination with Ezhil and performed CIT testing.

1) PAR file release with the given part numbers in the CDMT release mechanism 2) Coordinated with Ezhil to validate the released PAR file in the CIT tool.

Discussion with Ezhil on the table-level updates from the DICV SAP/MES team and clarifications on the process workflow. 

Coordination with Ezhil (DICV) to perform the CIT app testing at the vehicle level. Besides, discussed the change in table level update based on the SAP/MES team update. 

Modified the functional logic to trigger the VEPS exe file through batch file as did for vehicle station and tested taking the Toughbook in remote. In addition, on the PO verification step, the data was inserted from the PO Sap table to the Activities log table and the VCC_VIN Map table like the Vehicle station.

Testing VEPS execution for vehicle station and it is working fine as expected results. Tested VEPS execution for the engine station and identified similar changes in vehicle station functionality to be followed for the engine station.  

Testing CIT App with Ezhil

Modification in the CIT application with an alternate approach of making the VEPS executable file work and generating the output file as sometimes the batch command is not functioning properly while testing.

Validation of VEPS exe through the application from a shared network path

R&D on making the batch file in the remote system to run from CIT App Server to execute VEPS exe file using Windows Dot Net DLL through WMI Connect method

Debug & Bug fixes with the latest CIT version with the batch file to execute the VEPS exe file.

Applying the share path access code changes in the latest version of the CIT application which was done in the old version of the application for debugging purposes.

Verified that the Par file download to input and output folder creation works in two systems' shared folder path. Based on this, changed the application file in the actual method for further testing.

In order to test the share path permission, developed a new page with a form to get the inputs of the share folder path and folder name to be created. It helps to test the specific system share path having proper read/write permission to verify the application running server. 

Tried alternate options for setting the shared network folder permission thro' IIS, user groups settings, and also by installing XAMPP standalone Apache Webserver and running the folder creation script and testing to see if the permission issue resolves.

R&D Analysis was done for the problem of creating the folder or files dynamically in the shared network path of the client machine from the CIT application running on the server and is still in progress in finding a way to solve the problem. 

Checking folder creation issue in the shared drive path

Bench-level testing by running the CIT application in the toughbook and faced a problem in creating the PAR file input and output folders in the server due to permission access. We checked the same activity in my DICV laptop and were able to see the folder has been created properly and the file downloaded to the input folder.  Ezhil will check this problem with his plant IT team and get back in order to proceed next level of testing.

Change the logic of the VEPS process by downloading and executing the VEPS file with the approach of creating a shared folder path and placing it to run it. Also, performed the alpha testing to check if the PAR files were properly downloaded, VEPS batch file generation, and created the output files from the server to the client test machine shared folder path and reading the result file from the local to server where the CIT application runs.

Technical coordination with DICV and testing the tool with a sample order number to identify the VEPS executable file process and generate the proper output files - verification file and report file. Besides, we also performed the testing by making some changes and found the problem that the issue is due to not executing both VCI and VEPS exe in the same system. (It should run on the same machine).

Code Review of the CIT web app (both Version1 and latest) and found the Veps command constructed dynamically with old exe file installed path. It was then changed to the latest installed folder path which was generated dynamically and tested in the local system to generate the verification and report file which was not generated in the previous state.   

Released a par file in CDMT for vehicle pilot test and coordinated DICV in checking the output file generated by VEPS in CDMT Server. Also as per discussion with Ezhil, re-installed the VEPS exe file to verify again the output file which seems not in the expected result.

Creating the Get Flashing Data API for INS & ABS Parameterization

DICV Plant Visit: - Demo on the complete workflow of back documentation of Vehicle Station - Bench Level Validation of the CIT enhancements

Testing Back Documentation & Fixes on the CIT app enhancements

Enhancements: Modification in back documentation of VEPS Execution based on the enablement of Engine / Vehicle Stations.

Single Vehicle Station Enhancement: 1. Option to enable/disable Engine Station functional feature.2. Combine Engine & Vehicle Station functional behavior as one station if the engine station is disabled.