1. PRISM Configuration to Require
OALM & NBS
PRISM Configuration to Require
DCIS/FPDS Reporting
April 23, 2013

2. Agenda Overview Solution Benefits of new PRISM FPDS/DCIS Requirement
Awareness
Preparation for Go-live
OALM Change Management
Questions

3. Overview Current State Solution
DCIS reporting is not completed in timely manner
Inconsistent financial data between PRISM and DCIS (e.g. date of award, late reporting, etc.)
Corrections needed on PRISM award after “Released” to successfully report to DCIS (e.g. change in PSC, PIID, contract type)
Solution
Configure PRISM to require an error free draft DCIS record prior to routing for approval and release.
OALM will provide Change Management for the effort
Go-Live: June 1, 2013
11/7/2012

4. Solution Current Practice: New Practice:
Launch FPDS (this can occur at any time in award process)
Complete Draft DCIS record
Log out of PRISM
Log into PRISM to finalize DCIS record
FPDS Approval Number is displayed
New Practice:
Launch FPDS prior to Routing for Approval
Complete error free DCIS record and save
Route for Approval
After the PRISM document is approved and is in a Release status, PRISM automatically finalizes the DCIS record

5. Benefits FPDS/DICS reporting will be in accordance with FAR timeframes
Provide consistent financial acquisition data to DHHS and users of FPDS
Eliminate corrections required after a PRISM award is “Released”
PRISM NAICS and PSC helpdesk tickets will decrease once the new validations are established
IDC DCIS records will be finalized in PRISM prior to buyers awarding internal and external TO’s. Parent Contracts must be finalized in DCIS prior to creating Task Order against them

6. Awareness DCIS and FPDS-NG connectivity
NBS automated modification creations resulting from year end processing will not create a DCIS record
Buyers will be required to complete DCIS
Master data between PRISM and DCIS must be in sync
Buyers will not be able to transact
Updates are not implemented on time
If the DUNS is in-active in SAM, DCIS, PRISM, buyers cannot transact on the award
DCIS has a separate vendor file and creates synchronization issues if the PRISM file does not match the DCIS file
GWAC awards will continue to be directly reported in DCIS

7. Preparation for Go-Live
ServiceNow account will be established for DCIS helpdesk questions and problems
DCIS Helpdesk account will be disabled
Pre-deployment clean-up activity:
All previously released document versions must be finalized in FPDS in order to continue with new PRISM award actions
Parent contracts and BPA Setup’s ICs must have Finalized DCIS record prior to awarding TO’s and BPA Calls
Identify existing converted contracts (IDC and Standalone) that were not able to be reported to DCIS via PRISM still cannot be reported via PRISM
The OALM DCIS team will handle all requests that need to be processed outside of the PRISM to DCIS web service
CDMP will define a process for working with converted legacy awards that have out of sequence modifications
CDMP will work with DCIS Configuration Board to update NIH user accounts from ‘full access’ to ‘transmit’ only
CDMP will grant access to DCIS on a case by case basis
On-going testing between the OALM, NCI, NBS teams

8. OALM Change Management Effort
Education the NIH community on the implementation of new PRISM FPDS/DCIS Validations
Ensure that all active transactions are reported to DCIS/FPDS
Correct Award/IDV Type
Modifications in sequence
Implementation of ServiceNow for CDMP staff
Educate Acquisition community on new helpdesk request process
Create documentation and educate CIT Tier 1 and NBS Level 2 Helpdesk staff on most common errors
Work with NCI eContracts Vendor to implement new PRISM FPDS/DCIS Validations
NBS will update PRISM user documentation

9. Questions