Anyone had to set this all up from scratch?
After years of submitting projects without digital signatures to the same agencies (i.e., County, SWFWMD, etc.), we've just received a review comment requiring the submittal be digitally signed.
I am loosely familiar with PEDDS (an FDOT App for digital delivery) from my time beta testing the FDOT Civil 3D State Kit some years ago, but that wasn't my focus, and it's never been required for the projects I worked on.
TIA
[Edit] - Apparently the reviewer at SWFWMD that provided the comment requiring this, told my engineer by phone, that during the submittal/upload process (last step?) they can elect to simply generate the manifest, which generates the key for each document, etc... The engineer can then merely print, sign, seal, and scan THAT back into SWFWMD as a valid 'digital signature'.
From what I've read of the statute, etc. that's a far cry from the criteria for a digital signature; acquiring an SHA-1 Certificate, installing for the individual associated with that unique key, and formally 'signing' the documents, etc., no?