Not sure if this is where such a comment might go, but standard CRM-type software might already be designed handle this type of uncommon situation: homeowner provides information necessary for a federal grant-funded buyout case (like repetitive loss), as well as information about personal finances. Something changes (like insurance or financial need) and the homeowner must be transferred to a separate grant program. Under that new grant, the case file/folder/record has the capability to hide the information specific to the old grant requirements, but to display it if it also has general case information.

meeting today with Program and DOIT to confirm a rough understanding of needs and decide next steps forward. 

The following record was created for the project and includes the Problem Assessment and IT Project Sheet:   [IPTD-438] Blue Acres comprehensive system for all buyout st (external-share.com)

Anyone is welcome to add comments or attach documents as may support progress. 

A DOIT review of the problem assessment worksheet led us to an appreciation of the following main work processes in need of integrated technology support. 

In the meeting we want to correct/confirm this understanding and explore some specifics in consideration of possible paths forward.  

Major distinct processes in Blue Acres:

1. Generating intertest in the program targeted to candidate communities (not really or clearly part of the system need)

   1. Requires good handle on property-level historic flooding and damage

2. Processing and tracking a stream of applicants/potential properties and their basic qualifications incl. approval/denial

3. Applying for specific Federal funding opportunities

   1. Batching up known properties that qualify for the specific funding as part of the Federal application

   2. Lots of demonstrations/reporting on use of funds once secured

4. Navigating and negotiating/pricing all the individual property deals including:

   1. Meeting rental displacement requirements (URA)

   2. checking for duplication of benefits (DOBs)

   3. executing the property transaction to close

   4. relocation tracking and follow-up

5. Contracting for demolition and remediation (can be batched properties different from 3a)

6. Establishing oversight and maintenance (muni/NGO) for batches of properties (can be batched different from 3a or 5)

Outcome was general agreement to further explore options within and perhaps building onto existing enterprise systems, mainly NJEMS/Masterfile, Regulatory Services Portal, SIROMS, etc. No obvious alternative was uncovered. A previous demo by Forerunner was promising for related features but expensive even without significant elements that would require custom building to support all the Blue Acres documented workflows.

Next Steps:

1. Michele Zola to schedule NJEMS demo and provide program access, to include program demo of their current tools/process for full awareness

2. DOIT to work toward an analysis and potential roadmap with CGI

DOIT internal meeting today (Knute, Pete T. Jim B. Angela, Michele Z., and John Flemming) reviewed the program submissions and will seek a next meeting with program players who are key to the processes to be supported by a new technology solution. DOIT is unclear about the perceived potential of the recently presented Forerunner software to meet elements of the needs described herein. DOIT sees some potential to leverage NJEMS and current GIS tools for some of the need. One option discussed was a preliminary DOIT-funded closeness-of-fit-analysis that might bring missing pieces and their likely costs into focus. If known subscription costs to Forerunner are not already prohibitive for the program, a similar investigation of closeness-of-fit to that toolset could be investigated. Knute to set a follow-up meeting with this DOIT group plus key Blue Acres program staff.