The URL can be used to link to this page

Home My WebLink AboutFW: CFS Conversion - 9/16 update Mike Plane From:Kathy Markus Sent:Thursday, September 16, 2021 09:18 To:Steven Gassert Subject:FW: CFS Conversion - 9/16 update Steven, I did not see a reply to Keith. Are you OK with just leaving the dates and times as they are for the highlighted situations? Kathy From: Keith Lazarus <keith.lazarus@centralsquare.com> Sent: Thursday, September 16, 2021 09:04 To: Kathy Markus <kmarkus@tfid.org> Cc: Candy Reynolds <Creynolds@tfid.org>; Steven Gassert <sgassert@tfid.org> Subject: CFS Conversion - 9/16 update \[EXTERNAL SENDER\] Today’s updates: - The beat in the event address is pulling data from the wrong area. The beat should either be D1, D2, or D3. These are something that are new to the system and not something we tracked in the old system. So I am assuming there shouldn’t be any data converting to the Beat Field. Completed. - The data that is going into beat should actually be being converted into the Reporting Area field. These are numbers that range from 100-130. Not working – I need to look at why this is. Completed. - Is there a way we can have the call type get converted into the problem field under event? This field allows us to filter the column of situation reported on the CFS Q. So for example CFS Event # 2107240035 in EIS shows that it was a ACCHR – Hit and Run. In C/S in the testing system, nothing is showing in the Problem field. It’s showing the ACCHR down in the CAD Incident Type field. CAD Incident Type Field isn’t something we can filter by in the Q. So If I wanted to filter all traffic stops at a certain address, I want to make sure we can filter by the call type for the data that comes over. (I hope that all makes sense) Not working – but definitely doable. Update 9/16 – my attempt at doing this last night didn’t work. I’ll try something else today. - Area code for the phone number isn’t coming over. So example Event # 2107240035 The reporting party is Mandy and has a phone number in EIS. When you look in C/S it only has her name and the phone number without the area code in the Call Back Information section under event. Done, although I will insert a hyphen into the phone number itself on my next iteration. Completed - Case number isn’t coming over. Example Event # 2107240035 in EIS there was a case number assigned 21003934. I don’t see where that is coming over to the call for service in C/S. Completed - Primary Officer on the event section of C/S isn’t getting filled in. If you go to the response section it marks what officer is primary in C/S. Can we not also have it fill in the Primary Officer under event section. Example Event # 2107240035 If you look at Justin Clark it shows him as primary when you click his name but not up under the event section. Partially done – the formatting of the name is wrong but the value is coming over. This will be fixed in the next iteration. Completed. - Some of the times are being converted over incorrectly. Example – Event # 2107240095 Under event section in C/S – It states first unit enroute at 1908 hours and then first unit arrived at 1830. When you look in EIS, its pulling the enroute time from when the officer was marked enroute to a second location at 1908 hours. Under discussion - In CAD comments in C/S for the CAD Unit History… it looks like we have converted the dispatchers name (Operator). If possible I would rather we convert the officers name over and just put the badge number for the 1 operator. Example – Event # 2107240095 The yellow highlighted is the officers badge number. The green highlighted is the dispatchers badge number. Looking at it, it just looks cluttered when you have the dispatchers name on there for almost every line. (That make sense? Or I am also open to suggestions to make it look a little cleaner) o 2021-07-24 18:51:33 12416 C4 Operator: MILLER, DEANNA (391) 2021-07-24 18:51:50 12284 C4 Operator: MILLER, DEANNA (391) Completed. - Are linked names not able to come over like linked vehicles are? Example – Event # 2107240154 – The linked vehicle in EIS came over to the vehicle section in C/S. The Linked name (Hadrian Fields) didn’t come over to the person section in C/S. Seems to be working now – I’m not sure why it didn’t work previously. Completed. I see, however, that the Involvement Type is blank. I’ll see if there is a value for this in EIS and, if so, get that added. Thanks, Keith Keith Lazarus ____ Data Conversion Engineer Public Safety & Justice – Data Conversion keith.lazarus@centralsquare.com o: 913-991-8214 From: Keith Lazarus Sent: Wednesday, September 15, 2021 11:54 AM To: Kathy Markus <kmarkus@tfid.org> Cc: Candy Reynolds <Creynolds@tfid.org>; 'Steven Gassert' <sgassert@tfid.org> Subject: RE: CFS Conversion All, I am not on the ball today – it turns out that I did do a run after my last changes and you can have a look at the data: - The beat in the event address is pulling data from the wrong area. The beat should either be D1, D2, or D3. These are something that are new to the system and not something we tracked in the old system. So I am assuming there shouldn’t be any data converting to the Beat Field. Corrected - The data that is going into beat should actually be being converted into the Reporting Area field. These are numbers that range from 100-130. Not working – I need to look at why this is. - Is there a away we can have the call type get converted into the problem field under event? This field allows us to filter the column of situation reported on the CFS Q. So for example CFS Event # 2107240035 in EIS shows that it was a ACCHR – Hit and Run. In C/S in the testing system, nothing is showing in the Problem field. It’s showing the ACCHR down in the CAD Incident Type field. CAD Incident Type Field isn’t something we can filter by in the Q. So If I wanted to filter all traffic stops at a certain address, I want to make sure we can filter by the call type for the data that comes over. (I hope that all makes sense) Not working – but definitely doable. - Area code for the phone number isn’t coming over. So example Event # 2107240035 The reporting party is Mandy and has a phone number in EIS. When you look in C/S it only has her name and the phone number 2 without the area code in the Call Back Information section under event. Done, although I will insert a hyphen into the phone number itself on my next iteration. - Case number isn’t coming over. Example Event # 2107240035 in EIS there was a case number assigned 21003934. I don’t see where that is coming over to the call for service in C/S. Done - Primary Officer on the event section of C/S isn’t getting filled in. If you go to the response section it marks what officer is primary in C/S. Can we not also have it fill in the Primary Officer under event section. Example Event # 2107240035 If you look at Justin Clark it shows him as primary when you click his name but not up under the event section. Partially done – the formatting of the name is wrong but the value is coming over. This will be fixed in the next iteration. - Some of the times are being converted over incorrectly. Example – Event # 2107240095 Under event section in C/S – It states first unit enroute at 1908 hours and then first unit arrived at 1830. When you look in EIS, its pulling the enroute time from when the officer was marked enroute to a second location at 1908 hours. Under discussion - In CAD comments in C/S for the CAD Unit History… it looks like we have converted the dispatchers name (Operator). If possible I would rather we convert the officers name over and just put the badge number for the operator. Example – Event # 2107240095 The yellow highlighted is the officers badge number. The green highlighted is the dispatchers badge number. Looking at it, it just looks cluttered when you have the dispatchers name on there for almost every line. (That make sense? Or I am also open to suggestions to make it look a little cleaner) o 2021-07-24 18:51:33 12416 C4 Operator: MILLER, DEANNA (391) 2021-07-24 18:51:50 12284 C4 Operator: MILLER, DEANNA (391) Done - Are linked names not able to come over like linked vehicles are? Example – Event # 2107240154 – The linked vehicle in EIS came over to the vehicle section in C/S. The Linked name (Hadrian Fields) didn’t come over to the person section in C/S. Seems to be working now – I’m not sure why it didn’t work previously. I see, however, that the Involvement Type is blank. I’ll see if there is a value for this in EIS and, if so, get that added. Keith Keith Lazarus ____ Data Conversion Engineer Public Safety & Justice – Data Conversion keith.lazarus@centralsquare.com o: 913-991-8214 From: Keith Lazarus Sent: Wednesday, September 15, 2021 10:54 AM To: Kathy Markus <kmarkus@tfid.org> Cc: Candy Reynolds <Creynolds@tfid.org>; Steven Gassert <sgassert@tfid.org> Subject: FW: CFS Conversion Kathy, I just noticed that in anticipation of doing another run of the CFS load, I purged the results of my last run. I’m going to kick that off right now but I know from experience that it takes a few hours to run. As soon as it’s up, I’ll drop you a note. Depending on Sgt. Gassert’s response to my note from earlier about the “Enroute” issue, I think we should be able to get this wrapped up pretty quickly. I anticipate having a couple items to fix after this run but if everything else looks good, we could look at getting this loaded into live either Friday or, preferably, for Monday. 3 Are either of those attractive to you? Thanks, Keith Keith Lazarus ____ Data Conversion Engineer Public Safety & Justice – Data Conversion keith.lazarus@centralsquare.com o: 913-991-8214 From: Keith Lazarus Sent: Wednesday, September 15, 2021 9:34 AM To: Steven Gassert <sgassert@tfid.org>; Kathy Markus <kmarkus@tfid.org> Cc: Candy Reynolds <Creynolds@tfid.org> Subject: RE: CFS Conversion Sgt. Gassert, My recommendation is to just present the data as it appears in the legacy system, knowing that the person who looks at it might need to do some thinking when interpreting it. In previous jobs, I’ve had to try to analyze this type of stuff programmatically and managed to do it with a bit of success (we were doing response time analysis) but it was messy, with false positives and negatives. If we stick to reporting the data as it was recorded by CAD, at least what’s there reflects what was actually recorded by the Officers and Dispatchers – even if it’s “weird” from an analysis perspective. As for the status of the other items Several of those are done/tested and a few others received tweaks after my last run. I’m going to run through the list again and will send that off in the next half hour or so - @Kathy Markus just sent me a note saying that we need to get this done with some urgency. Thanks, Keith Keith Lazarus ____ Data Conversion Engineer Public Safety & Justice – Data Conversion keith.lazarus@centralsquare.com o: 913-991-8214 4 From: Steven Gassert <sgassert@tfid.org> Sent: Wednesday, September 15, 2021 1:41 AM To: Keith Lazarus <keith.lazarus@centralsquare.com> Cc: Kathy Markus <kmarkus@tfid.org>; Candy Reynolds <Creynolds@tfid.org> Subject: FW: CFS Conversion CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Report any suspicious activities using the Report Phishing Email Button above. Keith: So I reviewed the document you sent and the comments on it. I guess I would ask your advise/input on what you suggest. The enroute you are referring to on this case in when the officer was enroute to a secondary location. Our old CAD didn’t distinguish the difference between enroute to the original location or a secondary location like C/S does. Also I’m just waiting to hear back that you are done with the formatting things you mentioned below and then I will take a look at the testing database again. Steven Gassert Sergeant – Patrol Division Twin Falls Police Department Ph:(208)735-4357 Fax:(208)735-0876 sgassert@tfid.org https://link.edgepilot.com/s/58077e79/s3KS1m0OYkSEs461_vqvbw?u=http://www.tfid.org/ From: Keith Lazarus <keith.lazarus@centralsquare.com> Sent: Monday, September 13, 2021 2:36 PM To: Steven Gassert <sgassert@tfid.org>; Kathy Markus <kmarkus@tfid.org>; Candy Reynolds <Creynolds@tfid.org> Subject: RE: CFS Conversion \[EXTERNAL SENDER\] Sgt. Gassert, An update for you on the CFS work – I have most of the changes you requested taken care of. I was planning on releasing them to you this morning but, while doing some QA, I saw a couple formatting-related things that needed attention so I’m working on that right now. The 5 attached spreadsheet shows you the data that I used regarding the “Enroute at 19:08” issue that you reported. Can you please have a look at my comments and let me know your thoughts? Kathy & Candy – hopefully word has gotten back to you already but the issue related to the trailing spaces after the case numbers should be resolved now – I took care of that this morning. Thanks, Keith Keith Lazarus ____ Data Conversion Engineer Public Safety & Justice – Data Conversion keith.lazarus@centralsquare.com o: 913-991-8214 From: Steven Gassert <sgassert@tfid.org> Sent: Sunday, September 5, 2021 2:03 AM To: Keith Lazarus <keith.lazarus@centralsquare.com>; Kathy Markus <kmarkus@tfid.org>; Candy Reynolds <Creynolds@tfid.org> Subject: RE: CFS Conversion CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Report any suspicious activities using the Report Phishing Email Button above. Keith: Here are a few things that I have noticed as I am reviewing CFS in the testing system. - The beat in the event address is pulling data from the wrong area. The beat should either be D1, D2, or D3. These are something that are new to the system and not something we tracked in the old system. So I am assuming there shouldn’t be any data converting to the Beat Field. - The data that is going into beat should actually be being converted into the Reporting Area field. These are numbers that range from 100-130. - Is there a away we can have the call type get converted into the problem field under event? This field allows us to filter the column of situation reported on the CFS Q. So for example CFS Event # 2107240035 in EIS shows that it was a ACCHR – Hit and Run. In C/S in the testing system, nothing is showing in the Problem field. It’s showing the ACCHR down in the CAD Incident Type field. CAD Incident Type Field isn’t something we can filter by in the Q. So If I wanted to filter all traffic stops at a certain address, I want to make sure we can filter by the call type for the data that comes over. (I hope that all makes sense) - Area code for the phone number isn’t coming over. So example Event # 2107240035 The reporting party is Mandy and has a phone number in EIS. When you look in C/S it only has her name and the phone number without the area code in the Call Back Information section under event. - Case number isn’t coming over. Example Event # 2107240035 in EIS there was a case number assigned 21003934. I don’t see where that is coming over to the call for service in C/S. - Primary Officer on the event section of C/S isn’t getting filled in. If you go to the response section it marks what officer is primary in C/S. Can we not also have it fill in the Primary Officer under event section. Example Event # 6 2107240035 If you look at Justin Clark it shows him as primary when you click his name but not up under the event section. - Some of the times are being converted over incorrectly. Example – Event # 2107240095 Under event section in C/S – It states first unit enroute at 1908 hours and then first unit arrived at 1830. When you look in EIS, its pulling the enroute time from when the officer was marked enroute to a second location at 1908 hours. - In CAD comments in C/S for the CAD Unit History… it looks like we have converted the dispatchers name (Operator). If possible I would rather we convert the officers name over and just put the badge number for the operator. Example – Event # 2107240095 The yellow highlighted is the officers badge number. The green highlighted is the dispatchers badge number. Looking at it, it just looks cluttered when you have the dispatchers name on there for almost every line. (That make sense? Or I am also open to suggestions to make it look a little cleaner) o 2021-07-24 18:51:33 12416 C4 Operator: MILLER, DEANNA (391) 2021-07-24 18:51:50 12284 C4 Operator: MILLER, DEANNA (391) - Are linked names not able to come over like linked vehicles are? Example – Event # 2107240154 – The linked vehicle in EIS came over to the vehicle section in C/S. The Linked name (Hadrian Fields) didn’t come over to the person section in C/S. That’s what I was able to come up with so far. Running on minimal sleep this weekend so I will keep giving it a look over to see if I can see anything else. Once again, I apologize for the delay in getting to reviewing this for you. The delay in getting access to the testing system and then things the last week have been a little crazy for our agency. Steven Gassert Sergeant – Patrol Division Twin Falls Police Department Ph:(208)735-4357 Fax:(208)735-0876 sgassert@tfid.org https://link.edgepilot.com/s/03e0c7f6/i7nIRqlVqE27qdFGVvGTuQ?u=http://www.tfid.org/ From: Keith Lazarus <keith.lazarus@centralsquare.com> Sent: Tuesday, August 31, 2021 8:25 AM To: Kathy Markus <kmarkus@tfid.org>; Steven Gassert <sgassert@tfid.org>; Candy Reynolds <Creynolds@tfid.org> Subject: CFS Conversion \[EXTERNAL SENDER\] Have you all had a chance to review the latest CFS details that I sent you? Are those suitable for applying to live, or do they need more work? Thanks, Keith 7 Keith Lazarus ____ Data Conversion Engineer Public Safety & Justice – Data Conversion keith.lazarus@centralsquare.com o: 913-991-8214 CONFIDENTIALITY: This message contains information that is confidential and/or may be privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copy of this message or its attachments is strictly prohibited. If you have received this message in error, please advise the sender immediately by reply email and delete this message and its attachment. Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning. CONFIDENTIALITY: This message contains information that is confidential and/or may be privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copy of this message or its attachments is strictly prohibited. If you have received this message in error, please advise the sender immediately by reply email and delete this message and its attachment. Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning. CONFIDENTIALITY: This message contains information that is confidential and/or may be privileged. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copy of this message or its attachments is strictly prohibited. If you have received this message in error, please advise the sender immediately by reply email and delete this message and its attachment. Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning. 8