Service Pack (SP) 16c Changes to the MIP Service Pack (SP) 16c provides fixes to certain outstanding MIP issues and introduces enhancements to certain processes, specifically increasing the consistency of the data upload process whether you upload through the Citrix client, the data depot, or the MIP. This document outlines the significant changes that impact MIP Studies users. A series of screen shots and instructions are available at the end of this document that provides additional information on some of the issues and fixes presented below. (Note, please see file: ServicePack16cReleaseOverview_December2008.pdf, available at hazards.fema.gov > MIP User Care > Guides and Documentation > Recent and Upcoming service packs for any images). Data Uploads and Manual Submission for Metadata and DFIRM DB QA Validation: REMINDER: Earlier SP updates increased the recommended size limit from 300 MB 1 GB per submission upload Prior to SP16c, when using the MIP for data uploads, the MIP would unzip the submission package, place the files on the J drive and immediately send the appropriate files to FAFS for QA review. This process required users to have all metadata and/or DFIRM database files included in the zipped file and ready for review before uploading through the MIP. With the introduction of SP16c, neither DFIRM nor non-DFIRM submission uploads are automatically sent to FAFS upon upload through the MIP. Users can upload files individually or as zipped files through the MIP Submit Data Files portlet until ready to send the submission to FAFS for review. Prior to SP16c, the metadata and DFIRM DB validation would process concurrently and any changes made to any files would require the submission to be re-sent to both Metaman and FAFS for additional validation. With the deployment of SP16c, these two validations will happen sequentially. The metadata validation will occur first and require the metadata to receive a passing report before the DFIRM DB is automatically sent to FAFS for review. Because the data is not automatically sent to FAFS, users must manually kick off the validation process by clicking the Validate Contents button once all files have been uploaded to the MIP and they are ready for review. This now mirrors the Citrix file upload process where the user is responsible for manually kicking off the metadata and DFIRM DB QA validation. This should reduce the need to send data to the Data Depot as users can now upload data directly to the MIP in submissions up to 1 GB at a time. The MIP will continue to unzip the files loaded through the Submit Data Files portlet and place them on the J drive. Data Revised Changes: SP16c will also provide an update to the status indicator on the “submission status” section. Instead of Data Revised, the status will now show as Validation required. This new Validation required indicator will only appear if the metadata file or files validated by FAFS have changed on the J drive. If the status displays Validation Required, the Validate Contents button will appear indicating the user must click the button to start the validation process. Some users have also experienced the issue where the Submission Status reverts to Data Revised immediately upon upload through the MIP. This issue will be fixed with SP16c. In rare circumstances, users were able to complete a data development task while the Submission Status section displays Data Revised. A fix will be implemented in SP16c to address this issue. The submission status will correctly display Passed and continue to allow the user to complete the task. Updating Cost and Schedule Information during Post Preliminary Processing: Current MIP logic prevents the Manager from updating cost and schedule information in the Manage Post Preliminary Map Production (PPP) activity if the project is in the Manage Revalidation process. A change in SP16c will allow the Manager to add cost and schedule information while in the revalidation process. - If revalidation is not required for the project, the user indicates that action by unchecking the “Revalidation Letters Required for Any Community” box in the Prepare Revalidation Letter task. When this box is unchecked, this task cannot be completed until 45 days prior to the FIRM effective date, but cost and schedule information can still be updated on the PPP activity during the time the task is open. Once the task is completed, the Actual End date can be added to the PPP activity and that activity can be completed. - If revalidation is required, Managers can continue to update cost and schedule information while the project is in the revalidation process. But the Manage PPP activity cannot be completed until all tasks in the revalidation process are complete and the FIRM effective date has passed. Work Item Details image example Prepare Revalidation Letter: Task Information Populating County-wide Dates Users reported a discrepancy on MARS reports when dates were updated using the PA process instead of during the normal studies workflow. The MIP was not populating dates for county-wide and multi-county projects. This defect was exposed on MARS reports sometimes as additional rows or no dates at all. With the deployment of SP16c, dates will be populated at the county-wide level and also for multi-county projects. This update will address the inconsistency of data in the system and reflect the proper dates on the MARS reports. FOR MIP CHAMPIONS AND BLACK BELTS ONLY: Process Admin (PA) Updates Prior to SP16c, baseline start and end dates for Independent QA tasks updated through PA were not being saved in the MIP. PA indicated the changes were saved, but the MIP did not display them. This issue will be fixed with SP16c and data entered in PA will be saved and displayed correctly. Additionally, users could not update letter dates in PA for legacy (MICS) projects. This issue will also be addressed in SP16c so users can use PA to update letter dates for MICS projects. The series of screen shots below walk through the revised process for submitting data for Metaman and/or DFIRM DB QA validation. Once data has been uploaded through the Submit Data Files portlet, the Citrix client or the Data Depot, return to the Submit Data section and click Update Contents to confirm the files were uploaded. After clicking on Update Contents the Submission Status for both the Metadata Profile Validation and DFIRM DB QA Validation should display Validation Required. Work Item Details image example Develop DFIRM Database: Data Submission Submit Data - Update Contents When all files are ready to be submitted for QA review, click Validate Contents. Work Item Details image example Develop DFIRM Database: Data Submission Submit Data - Validate Contents Once the metadata validation has passed, the DFIRM DB is automatically sent to FAFS for validation. To reduce the number of partial and/or multiple submissions to FAFS, make sure the complete DFIRM DB is uploaded to the J drive before beginning the metadata and DFIRM DB validation process. Work Item Details image example Develop DFIRM Database: Data Submission Submission Status Metadata Profile Validation = Passed DFIRM DB QA Validation =In-Progress Once the DFIRM DB QA Validation has passed, the user clicks Continue to complete the task. The process works the same for non-DFIRM tasks. The user must click the Validate Contents button to start the metadata validation.