Skip Navigation

Exhibit 300 (BY2010) for FDA Regulatory Business Information Services

PART ONE


OVERVIEW


1. Date of Submission:
2008-09-08
2. Agency:
009
3. Bureau:
10
4. Name of this Capital Asset:
FDA Regulatory Business Information Services
5. Unique Project Identifier:
009-10-01-03-01-8033-00
6. What kind of investment will this be in FY2010?
Mixed Life Cycle
7. What was the first budget year this investment was submitted to OMB?
FY2004
8. Provide a brief summary and justification for this investment, including a brief description of how this closes in part or in whole an identified agency performance gap.
Regulatory Business Information Services (RBIS) manages ORA's reporting and information management projects. These include: a centralized data warehouse, the Online Reporting, Analysis, and Decision Support System (ORADSS), implemented to provide integrated information for regulatory compliance and risk-based analysis; the Firms Master List Services (FMLS), to manage, improve the quality of, and standardize data on firms; and, the ORA Data Marts, providing secure storage of and access to electronic documents such as inspection reports and exhibits. ORA and Center staff access these integrated systems for analysis and decision-making used to protect public health and safety and communicate to the public. Over 5,000 users throughout FDA use ORADSS in regulatory compliance and risk-based analysis. ORADSS uses a commercially available user interface that allows access to standardized reports and simplifies the creation of ad-hoc reports without specialized knowledge of the underlying data. Without ORADSS, only a small group of users were able to access critical data. ORADSS provides decision support covering all aspects of FDA's mission, from work planning to performance measurement and reporting to Congress. The FMLS system provides services to manage the demographic data on firms doing business with and/or required to register with the FDA. These tools maintain accurate data in the warehouse and clean up the operational databases. FMLS standardizes and validates the facility name and address data received from imports, registration and listing systems, and inspections. Much of the data on firms is received from outside the Agency in non-standard and often inaccurate form. Without FMLS, the Agency would be limited in protecting the public by evaluating risks using data on firms in the supply chain. The ORA Data Marts provide storage of critical Agency documents including inspection documentation, digital photographs, and scanned documents. Currently the electronic documents are hard to find and not fully secured, while hard copies are stored in file rooms in each District requiring copying and shipping for use at HQ. Enhancements to the RBIS systems, including integration across FDA, provide staff with critical data, improving their ability to make risk-based decisions. Staff will be able to respond more rapidly and effectively to public health crises, such as a salmonella outbreak, to save lives and reduce the cost to industry.
9. Did the Agency's Executive/Investment Committee approve this request?
yes
9.a. If "yes," what was the date of this approval?
2008-07-21
10. Did the Project Manager review this Exhibit?
yes
11.a. What is the current FAC-P/PM certification level of the project/program manager?
Waiver Issued
11.b. When was the Program/Project Manager Assigned?
2002-01-01
11.c. What date did the Program/Project Manager receive the FACP/PM certification? If the certification has not been issued, what is the anticipated date for certification?
2009-07-31
12. Has the agency developed and/or promoted cost effective, energy-efficient and environmentally sustainable techniques or practices for this project.
no
12.a. Will this investment include electronic assets (including computers)?
yes
12.b. Is this investment for new construction or major retrofit of a Federal building or facility? (answer applicable to non-IT assets only)
no
13. Does this investment directly support one of the PMA initiatives?
yes
If yes, select the initiatives that apply:
Initiative Name
Expanded E-Government
13.a. Briefly and specifically describe for each selected how this asset directly supports the identified initiative(s)? (e.g. If E-Gov is selected, is it an approved shared service provider or the managing partner?)
Expansion of E-Government is supported through the FMLS system, which reduces the burden on filers during electronic submission of Prior Notice and Registration data. ORADSS will support E-gov by providing a mechanism to report data on FDA regulated products and firms to the public, expanding public access to health and safety information. The Firm Finder will also support industry by facilitating public access to firm information via the Broker Import Communications system.
14. Does this investment support a program assessed using the Program Assessment Rating Tool (PART)?
yes
14.a. If yes, does this investment address a weakness found during the PART review?
no
14.b. If yes, what is the name of the PARTed program?
10001057 - Food and Drug Administration
14.c. If yes, what rating did the PART receive?
Moderately Effective
15. Is this investment for information technology?
yes
16. What is the level of the IT Project (per CIO Council's PM Guidance)?
Level 2
17. What project management qualifications does the Project Manager have? (per CIO Council's PM Guidance)
(1) Project manager has been validated as qualified for this investment
18. Is this investment identified as high risk on the Q4 - FY 2007 agency high risk report (per OMB memorandum M-05-23)?
no
19. Is this a financial management system?
no
19.a.2. If no, what does it address?
Regulatory Business Information Systems: decision support, data quality, and information management systems. The RBIS systems provide information for FDA staff that is used to ensure product safety and regulatory compliance, protect the public from health threats, and combat the threat of bioterrorism. RBIS systems also improve the quality of data in systems throughout the Agency, particularly for firms doing business with FDA.
20. What is the percentage breakout for the total FY2009 funding request for the following? (This should total 100%)
AreaPercentage
Hardware0
Software3
Services78
Other19
21. If this project produces information dissemination products for the public, are these products published to the Internet in conformance with OMB Memorandum 05-04 and included in your agency inventory, schedules and priorities?
n/a
22. Contact information of individual responsible for privacy related questions.
NameFred Sadler
Phone Number301-827-6567
TitleFDA Privacy Act Officer
Emailfrederick.sadler@fda.hhs.gov
23. Are the records produced by this investment appropriately scheduled with the National Archives and Records Administration's approval?
yes
24. Does this investment directly support one of the GAO High Risk Areas?
yes

SUMMARY OF SPEND


1. Provide the total estimated life-cycle cost for this investment by completing the following table. All amounts represent budget authority in millions, and are rounded to three decimal places. Federal personnel costs should be included only in the row designated Government FTE Cost, and should be excluded from the amounts shown for Planning, Full Acquisition, and Operation/Maintenance. The total estimated annual cost of the investment is the sum of costs for Planning, Full Acquisition, and Operation/Maintenance. For Federal buildings and facilities, life-cycle costs should include long term energy, environmental, decommissioning, and/or restoration costs. The costs associated with the entire life-cycle of the investment should be included in this report.

All amounts represent Budget Authority

Note: For the cross-agency investments, this table should include all funding (both managing partner and partner agencies).

Government FTE Costs should not be included as part of the TOTAL represented.
Cost TypePy-1 & Earlier
-2007
PY
2008
CY
2009
BY
2010
Planning Budgetary Resources4.5300.0001.8930.000
Acquisition Budgetary Resources18.6819.6502.6602.166
Maintenance Budgetary Resources5.2801.6552.1812.715
Government FTE Cost1.4460.4500.4320.406
# of FTEs4433
2. Will this project require the agency to hire additional FTE's?
no
3. If the summary of spending has changed from the FY2008 President's budget request, briefly explain those changes.
The funding for FY 2010 is increased from the FY 2009 budget request. The FY 2009 request was based on the funding projected to be available in FY 2010. Since that time, additional funding for RBIS in FY 2010 has been identified, and will be used to address some of the new scope identified in areas such as imports, food safety, and drug safety.

PERFORMANCE


In order to successfully address this area of the exhibit 300, performance goals must be provided for the agency and be linked to the annual performance plan. The investment must discuss the agency's mission and strategic goals, and performance measures (indicators) must be provided. These goals need to map to the gap in the agency's strategic goals and objectives this investment is designed to fill. They are the internal and external performance benefits this investment is expected to deliver to the agency (e.g., improve efficiency by 60 percent, increase citizen participation by 300 percent a year to achieve an overall citizen participation rate of 75 percent by FY 2xxx, etc.). The goals must be clearly measurable investment outcomes, and if applicable, investment outputs. They do not include the completion date of the module, milestones, or investment, or general goals, such as, significant, better, improved that do not have a quantitative measure.

Agencies must use the following table to report performance goals and measures for the major investment and use the Federal Enterprise Architecture (FEA) Performance Reference Model (PRM). Map all Measurement Indicators to the corresponding Measurement Area and Measurement Grouping identified in the PRM. There should be at least one Measurement Indicator for each of the four different Measurement Areas (for each fiscal year). The PRM is available at www.egov.gov. The table can be extended to include performance measures for years beyond FY 2009.
RowFiscal YearStrategic Goal SupportedMeasurement AreaMeasurement GroupingMeasurement IndicatorBaselinePlanned Improvement to the BaselineActual Results
12005S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsBorder and Transportation SecurityResponse time to validate that manufacturer data identified in Prior Notice submittals is consistent with FFRM data, as required by the Prior Notice Interim Final RuleTwo independent databases with no linkage and no real-time ability to verify Manufacturer's data.Link that allows validation and reconciliation of data from PN submissions against Registration, with response to user within 3 seconds (PNSI) and without delaying response > 5 sec for ACS submittals.System is in Production and functioning within these specifications. Load testing completed with response <2.5 seconds.
22005S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesKnowledge ManagementNumber of duplicate firms identified and resolved.FIRMS data was poor with many duplicates (est. 50,000 duplicates); no process exists to prevent continued introduction of additional duplicatesUse data quality tool to clean up and maintain better data on firms - identify and merge 30,000 duplicates.Nightly process to maintain clean data has been implemented to identify and clean duplicates, as planned ~40,000 duplicates merged.
32005S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyInternal Data SharingNumber of years of historical data available for queries, reporting, and trend analysis.Current system provides access to 1 year of dataProvide access to 4 years of dataMigration of historical data into Production is complete. System is available to users. Up to 11 years of data is available.
42005S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsAccuracy of Service or Product Delivered% of new FFRM records validated.None, new system (no method currently exists to validate electronically)FMLS will provide validation of address information, determine existence of firm, and update as needed, for >99% of new FFRM recordsBatch process for validation is in Production for FFRM and OASIS. Real time validation is in Production for PNSI. All (100%) FFRM records are validated by FMLS.
52006S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsBorder and Transportation SecurityNumber of PN reports available.Reporting dependent on time-consuming SQL queries and manipulation of data in Excel; no standard reports available.Expanded range of PN reports allow users to rapidly obtain critical information; 2 initial reports and PN Datamart available.PN Data Mart and 3 reports are now available using Production system. ~10 additional relevant reports available through Imports menu
62006Effective Management of Human Capital/Information Technology/ResourcesProcesses and ActivitiesProductivityNumber of modules/reports with OLAP capabilities enabledReporting requires custom development of SQL code5 modules/ >50 reportsNew system is available for target program areas & reports
72006S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsCustomer Impact or BurdenNumber of canned reports available to allow easy retrieval of dataData resides in database designed for operations, not queries. All reports require custom coding.Organize FACTS \ OASIS data into pre summarized, aggregated subject area data marts, with at least 200 reports available.Initial OASIS data marts are complete. >500 Domestic reports are available.
82006S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyInternal Data SharingInterface with new MARCS database. Measure length of time for extraction job.Data extracted from legacy databases; time will be remeasured just prior to migration.Migration from new system with no significant impact on system performanceMARCS plans to move to UNIX prior to database redesign; work will proceed once MARCS is ready.
92007S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of Data Marts available for user queries.Data resides in legacy database designed for operations, not queries.Develop and deploy average of 1 new Data Mart/year, including Firms, Products, Organizations, and Program Assignments, to ensure consistent reporting across ORA enabling broader analysis and trendingDeferred to FY 2008-9 due to changing priorities. Firms and Laboratory Data Marts are in development. Additional data marts will be developed following completion.
102007Effective Management of Human Capital/Information Technology/ResourcesProcesses and ActivitiesSecurityNumber of separate user accounts required for ORA systemsSystem-specific independent login requires separate account for each systemOne user ID and password allows user access to all RBIS systems along with other ORA systems.Single Sign-On implemented 6/06. Users now login to FDA network and have full access to ORADSS without additional login.
112007S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsNew Customers and Market PenetrationNumber of ORADSS system usersORADSS current number of users 100ORADSS will allow additional users to access data from multiple data sources in a timely fashion; expected number of users is 400.Measure successfully completed. Over 4000 users have logged into ORADSS
122007Effective Management of Human Capital/Information Technology/ResourcesTechnologyOperations and Maintenance CostsNumber of versions of Business Objects in use in AgencyInitial deployment is independent, with an older version of Business Objects.Integrate ORADSS Business Objects user interface with FDA consolidated Architecture to reduce hardware cost and maintenance, so only one version is in use.ORADSS has migrated to Agency standard version of Business Objects and meets architecture standards.
132008S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsPopulation Health Management and Consumer SafetyTime required to locate (map) domestic firms of interestEst. 10 min - using manual address/map lookup in Google Maps<2 min to generate report and create map using Business Objects/MapInfoLoad test confirms 1-2 min to generate report + map. Pilot of MapInfo underway.
142008S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesProductivityAbility to find Firm records provided by new Firm Finder, measured by number of parameters available for search.Limited search screens are available in FACTS & OASIS, using 22 parameters and limited Boolean combinationsIncrease available search parameters by 50% to improve specificity and flexibility in searchesFirm Finder will be implemented in July, 2008. Users can select from over 50 parameters with expanded Boolean combinations.
152008S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsResponse TimeResponse time to retrieve an inspection report.Obtaining documents requires logging into District Servers with widely varying response timesDocuments can be retrieved from local/regional storage at all ORA locations with delays beyond network bandwidth limitations of no greater than 30 seconds.Load test confirms 1-2 min to generate report + map. Pilot of MapInfo underway.
162008S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyInternal Data SharingNumber of documents in available in Documentum repository.Documents must be obtained by logging into District Servers, not connected to the reporting system, none are in repository4 years of inspection documents in Repository (80,000 documents)Will be addressed once MARCS components of SERS are in Production.
172009S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsBorder and Transportation SecurityPercentage of new firm records created due to inability to matchCurrent process introduces ~10,000 records/week, including both new firms and duplicatesReduce the % of new records created by 25% through improved tools and processes2009 Metric
182009S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesEfficiencyNumber of instances of duplicated data with differing identifiers across AgencyTBD - data is scattered across Centers, requiring assessment during integration phaseMapping to single identifier reduces instances of duplicates by 75%2009 Metric
192009S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsNew Customers and Market PenetrationNumber of Users from Centers other than ORATBD - usage will be assessed at time of implementationIncorporation of data from Centers other than ORA allows usage by non-ORA users (25% increase in users)2009 Metric
202009S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologySystem Response TimeTime to access non-ORA documentsTBD - current system requires login to multiple systemsReduce access time by 75% by integration with other DM systems2009 Metric
212010S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsBorder and Transportation SecurityPercentage of duplicate firm records created from Customs feedTBD - currently data from CBP does not contain a reliable and unique standard identifierImplementation of FHA standard identifier eliminates 99% of duplicate records2010 Metric
222010S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsResponse TimeResponse time for most used queriesTBD - measure response times at start of FYTune queries and improve system to reduce top 20 queries to meet customer specifications (100%)2010 Metric
232010S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesTimelinessTime LagData is available in warehouse after next nightly extract (up to 24 hr delay)Near Real-time availability - lag no more than 15 min for all critical data2010 Metric
242010S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyReliabilityAmount of system downtimeCurrent system outages occur for both planned (upgrades) and unscheduled (problem) outagesImprove redundancy and processes to reduce by 25%2010 Metric
252011S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyData Reliability and QualityNumber of Systems Using Data Standardization/Validation Service1 System in Production in FY 2007All Critical Agency Systems in Production (number TBD once assessment complete)2011 Metric
262011S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesKnowledge ManagementData Mining Reports; number of reports availableNo predictive analysis capability; no reports availableData mining capability provides risk-based indicators for at least 2 critical areas (e.g., Firms and Shipments) with at least 1 report each2012 Metric
272011S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of Queries (avg)/dayTBD - tool to audit to be procured5% increase/year2011 Metric
282011S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsCustomer RetentionNumber of ORADSS users4000 user accounts in FY 2007At least as many user accounts, adjusted for FDA staffing levels2011 Metric
292012S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyReliabilitySystem AvailabilitySLA's not establishedSLA's established; all RBIS systems meet SLA's2012 Metric - systems are in Steady State (no new DME metrics)
302012S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of Queries (avg)/dayTBD - tool to audit to be procured5% increase/year2012 Metric
312012S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsCustomer RetentionNumber of ORADSS users4000 user accounts in FY 2007At least as many user accounts, adjusted for FDA staffing levels2012 Metric
322012S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesTimelinessHelp desk response timeUser calls are resolved in TBD days or lessAll user calls are resolved in 5 business days or less2012 Metric
332013S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of user report requests metRequests are currently deferred due to competing priorities100% of valid requests for report maintenance met2013 Metric
342013S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsCustomer RetentionNumber of ORADSS users4000 user accounts in FY 2007At least as many user accounts, adjusted for FDA staffing levels2013 Metric
352013S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyReliabilitySystem AvailabilitySLA's not establishedSLA's established; all RBIS systems meet SLA's2013 Metric
362013S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesTimelinessHelp desk response timeUser calls are resolved in TBD days or lessAll user calls are resolved in 5 business days or less2013 Metric
372014S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsPopulation Health Management and Consumer SafetyNumber of user report requests metRequests are currently deferred due to competing priorities100% of valid requests for report maintenance met2014 Metric
382014S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsCustomer RetentionNumber of ORADSS users4000 user accounts in FY 2007At least as many user accounts, adjusted for FDA staffing levels2014 Metric
392014S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyReliabilitySystem AvailabilitySLA's not establishedSLA's established; all RBIS systems meet SLA's2014 Metric
402014S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesTimelinessHelp desk response timeUser calls are resolved in TBD days or lessAll user calls are resolved in 5 business days or less2014 Metric

Enterprise Architecture


In order to successfully address this area of the business case and capital asset plan you must ensure the investment is included in the agency's EA and Capital Planning and Investment Control (CPIC) process, and is mapped to and supports the FEA. You must also ensure the business case demonstrates the relationship between the investment and the business, performance, data, services, application, and technology layers of the agency's EA.

1. Is this investment included in your agency's target enterprise architecture?
yes
2. Is this investment included in the agency's EA Transition Strategy?
yes
2.a. If yes, provide the investment name as identified in the Transition Strategy provided in the agency's most recent annual EA Assessment.
FDA Regulatory Business Information Services
3. Is this investment identified in a completed (contains a target architecture) and approved segment architecture?
no
4. Identify the service components funded by this major IT investment (e.g., knowledge management, content management, customer relationship management, etc.). Provide this information in the format of the following table. For detailed guidance regarding components, please refer to http://www.whitehouse.gov/omb/egov/.

Component: Use existing SRM Components or identify as NEW. A NEW component is one not already identified as a service component in the FEA SRM.

Reused Name and UPI: A reused component is one being funded by another investment, but being used by this investment. Rather than answer yes or no, identify the reused service component funded by the other investment and identify the other investment using the Unique Project Identifier (UPI) code from the OMB Ex 300 or Ex 53 submission.

Internal or External Reuse?: Internal reuse is within an agency. For example, one agency within a department is reusing a service component provided by another agency within the same department. External reuse is one agency within a department reusing a service component provided by another agency in another department. A good example of this is an E-Gov initiative service being reused by multiple organizations across the federal government.

Funding Percentage: Please provide the percentage of the BY requested funding amount used for each service component listed in the table. If external, provide the funding level transferred to another agency to pay for the service.
RowAgency Component NameAgency Component DescriptionService TypeComponentReused Component NameReused UPIInternal or External Reuse?Funding %
1ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.Knowledge DiscoveryData Mining  No Reuse4
2Firm Management ServicesFind information on firms in FDA databasesKnowledge ManagementKnowledge Capture  No Reuse6
3ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.ReportingStandardized / Canned  No Reuse4
4Integration of Documentum DocBase with Oracle Database applicationsAbility to store all documents that relate to a record in an Oracle database application in Documentum DocBase. The user has the ability to search, retrieve and manage the documents from the Oracle application.Knowledge ManagementInformation SharingInformation Sharing009-10-01-09-02-1010-00Internal0
5ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.Data ManagementData Mart  No Reuse4
6ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.Data ManagementExtraction and Transformation  No Reuse4
7SERS Data MartThe RBIS investment will provide a data mart that provides secure storage and gives users easy access to a wide variety of ORA electronic materials ORA and Center staff will have access to documents, digital photographs, and scanned documents.Document ManagementDocument Revisions  No Reuse0
8SERS Data MartThe RBIS investment will provide a data mart that provides secure storage and gives users easy access to a wide variety of ORA electronic materials ORA and Center staff will have access to documents, digital photographs, and scanned documents.Document ManagementLibrary / Storage  No Reuse1
9ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.Business IntelligenceDecision Support and Planning  No Reuse4
10Firms Master List Servicesproviding services to manage and standardize data on the firms doing business with the FDA.Data ManagementData Cleansing  No Reuse15
11Business ObjectsBusiness Intelligence reporting toolReportingAd HocAd Hoc Internal0
12Firms Master List Servicesproviding services to manage and standardize data on the firms doing business with the FDA.VisualizationMapping / Geospatial / Elevation / GPS  No Reuse4
13ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.ReportingOLAP  No Reuse4
14ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.Knowledge ManagementInformation Sharing  No Reuse4
15Address StandardizationStandardize address formats &amp; data for firmsData ManagementData Cleansing  No Reuse4
16Integration of Documentum DocBase with Oracle Database applicationsAbility to store all documents that relate to a record in an Oracle database application in Documentum DocBase. The user has the ability to search, retrieve and manage the documents from the Oracle application.Records ManagementDocument ClassificationDocument Classification009-10-01-09-02-1010-00Internal0
17ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.VisualizationMapping / Geospatial / Elevation / GPS  No Reuse4
18Firms Master List Servicesproviding services to manage and standardize data on the firms doing business with the FDA.Knowledge ManagementInformation Retrieval  No Reuse10
19Firm Management ServicesFind information on firms in FDA databasesKnowledge ManagementInformation Retrieval  No Reuse6
20SERS Data MartThe RBIS investment will provide a data mart that provides secure storage and gives users easy access to a wide variety of ORA electronic materials ORA and Center staff will have access to documents, digital photographs, and scanned documents.Document ManagementIndexing  No Reuse1
21ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.Data ManagementData Warehouse  No Reuse4
22SERS Data MartThe RBIS investment will provide a data mart that provides secure storage and gives users easy access to a wide variety of ORA electronic materials ORA and Center staff will have access to documents, digital photographs, and scanned documents.Document ManagementDocument Referencing  No Reuse1
23ORA Reporting Analysis Decision Support Systemprovide integrated decision support for regulatory compliance.Knowledge ManagementInformation Retrieval  No Reuse4
24Integration of Captiva Input Accell scan software with Documentum DocBase.Ability to scan documents directly into a Documentum DocBase and sync them to a record in an Oracle application.Document ManagementDocument Imaging and OCRDocument Imaging and OCR009-10-01-09-02-1010-00Internal0
5. To demonstrate how this major IT investment aligns with the FEA Technical Reference Model (TRM), please list the Service Areas, Categories, Standards, and Service Specifications supporting this IT investment.

FEA SRM Component: Service Components identified in the previous question should be entered in this column. Please enter multiple rows for FEA SRM Components supported by multiple TRM Service Specifications.

Service Specification: In the Service Specification field, Agencies should provide information on the specified technical standard or vendor product mapped to the FEA TRM Service Standard, including model or version numbers, as appropriate.
RowSRM Component>Service AreaService CategoryService StandardService Specification (i.e., vendor and product name)
1Data MiningComponent FrameworkData ManagementReporting and AnalysisBusiness Objects XI by: SAP AG
2Knowledge CaptureService Platform and InfrastructureSupport PlatformsIndependent PlatformJava 2 Enterprise Edition by: Sun Microsystems, Inc.
3Standardized / CannedService Platform and InfrastructureDelivery ServersApplication ServersOracle Application Server by: Oracle Corporation
4Standardized / CannedService Platform and InfrastructureHardware / InfrastructureServers / ComputersSun Solaris 10 by: Sun Microsystems, Inc.
5Standardized / CannedService Platform and InfrastructureDatabase / StorageDatabaseOracle 9i Database R2 by: Oracle Corporation
6Standardized / CannedComponent FrameworkData ManagementReporting and AnalysisBusiness Objects XI by: SAP AG
7Data MartService Platform and InfrastructureHardware / InfrastructureServers / ComputersSun Solaris 10 by: Sun Microsystems, Inc.
8Data MartService Platform and InfrastructureDatabase / StorageDatabaseOracle 9i Database R2 by: Oracle Corporation
9Data MartService Interface and IntegrationIntegrationEnterprise Application IntegrationInformatica by: Informatica Corporation
10Extraction and TransformationComponent FrameworkData ManagementReporting and AnalysisInformatica by: Informatica Corporation
11Document RevisionsService Interface and IntegrationInteroperabilityData TransformationMicrosoft Office by: Microsoft Corporation
12Library / StorageService Platform and InfrastructureDatabase / StorageStorageDocumentum by: EMC Corporation
13Library / StorageService Platform and InfrastructureHardware / InfrastructureServers / ComputersSun Solaris 10 by: Sun Microsystems, Inc.
14Decision Support and PlanningComponent FrameworkData ManagementReporting and AnalysisBusiness Objects XI by: SAP AG
15Data CleansingService Interface and IntegrationInteroperabilityData Types / ValidationDataFlux by: DataFlux
16Data CleansingService Platform and InfrastructureHardware / InfrastructureServers / ComputersSun Solaris 10 by: Sun Microsystems, Inc.
17Ad HocComponent FrameworkData ManagementReporting and AnalysisBusiness Objects by: SAP AG
18Mapping / Geospatial / Elevation / GPSService Interface and IntegrationInteroperabilityData TransformationIBM Websphere QualityStage by: International Business Machines Corp.
19OLAPComponent FrameworkData ManagementReporting and AnalysisOLAP Services by: Microsoft Corporation
20Information SharingComponent FrameworkData ManagementReporting and AnalysisBusiness Objects XI by: SAP AG
21Data CleansingService Interface and IntegrationInteroperabilityData Types / ValidationIBM Websphere QualityStage by: International Business Machines Corp.
22Data CleansingService Platform and InfrastructureDelivery ServersApplication ServersOracle Application Server by: Oracle Corporation
23Document ClassificationService Interface and IntegrationInteroperabilityData Types / ValidationDocumentum by: EMC Corporation
24Mapping / Geospatial / Elevation / GPSService Platform and InfrastructureDelivery ServersApplication ServersOracle Application Server by: Oracle Corporation
25Mapping / Geospatial / Elevation / GPSComponent FrameworkData ManagementReporting and AnalysisBusiness Objects XI by: SAP AG
26Mapping / Geospatial / Elevation / GPSService Platform and InfrastructureHardware / InfrastructureServers / ComputersSun Solaris 10 by: Sun Microsystems, Inc.
27Mapping / Geospatial / Elevation / GPSComponent FrameworkData ManagementReporting and AnalysisMapInfo by: Pitney Bowes, Inc.
28Mapping / Geospatial / Elevation / GPSComponent FrameworkUser Presentation / InterfaceContent RenderingMapInfo by: Pitney Bowes, Inc.
29Mapping / Geospatial / Elevation / GPSService Interface and IntegrationInteroperabilityData TransformationDataFlux by: DataFlux
30Information RetrievalService Interface and IntegrationInteroperabilityData TransformationBusiness Objects XI by: SAP AG
31IndexingService Interface and IntegrationInteroperabilityData Types / ValidationDocumentum by: EMC Corporation
32Data WarehouseService Platform and InfrastructureHardware / InfrastructureServers / ComputersSun Solaris 10 by: Sun Microsystems, Inc.
33Data WarehouseService Platform and InfrastructureDatabase / StorageDatabaseOracle 9i Database R2 by: Oracle Corporation
34Data WarehouseComponent FrameworkData InterchangeData ExchangeInformatica by: Informatica Corporation
35Document ReferencingService Interface and IntegrationInteroperabilityData Format / ClassificationDocumentum by: EMC Corporation
36Information RetrievalComponent FrameworkData ManagementReporting and AnalysisFAST RetrievalWare by: FAST, a Microsoft Subsidiary
37Document Imaging and OCRService Interface and IntegrationIntegrationEnterprise Application IntegrationEMC Captiva by: EMC Corporation
38Document Imaging and OCRService Interface and IntegrationInteroperabilityData TransformationEMC Captiva by: EMC Corporation
6. Will the application leverage existing components and/or applications across the Government (i.e., FirstGov, Pay.Gov, etc)?
yes
6.a. If yes, please describe.
no

PART TWO


RISK


You should perform a risk assessment during the early planning and initial concept phase of the investment's life-cycle, develop a risk-adjusted life-cycle cost estimate and a plan to eliminate, mitigate or manage risk, and be actively managing risk throughout the investment's life-cycle.

Answer the following questions to describe how you are managing investment risks.

1. Does the investment have a Risk Management Plan?
yes
1.a. If yes, what is the date of the plan?
2007-08-17
1.b. Has the Risk Management Plan been significantly changed since last year's submission to OMB?
no
3. Briefly describe how investment risks are reflected in the life cycle cost estimate and investment schedule:
The life cycle cost and schedule estimates were revised in conjunction with the Alternatives Analysis conducted in FY 2007. The estimates were developed based on the historical data from the ORADSS project (primarily FY 2003-FY 2007). That experience included significant changes in scope and schedule due to the introduction of the Prior Notice requirements. The biggest impacts to cost and schedule for this project have been due to this and similar changes in business needs. Thus, the project expects that the current estimates include a reasonable contingency for the impact of the risks identified on both budget and schedule. In addition, although there is considerable interdependency with other systems, most of the identified tasks do not have fixed deadlines. Many tasks can also be addressed without dependency on the completion of other tasks. Therefore, the investment risks can be managed in part by adjusting the order in which tasks are undertaken, based on changing business priorities.

COST & SCHEDULE


1. Does the earned value management system meet the criteria in ANSI/EIA Standard 748?
no
2. Is the CV% or SV% greater than ± 10%?
no
3. Has the investment re-baselined during the past fiscal year?
no