Skip Navigation

Exhibit 300 (BY2010) for FDA Mission Accomplishments and Regulatory Compliance Services (MARCS)

PART ONE


OVERVIEW


1. Date of Submission:
2009-04-10
2. Agency:
009
3. Bureau:
10
4. Name of this Capital Asset:
FDA Mission Accomplishments and Regulatory Compliance Services (MARCS)
5. Unique Project Identifier:
009-10-01-03-01-8021-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.
The MARCS program manages the integration, reengineering and enhancement of seven legacy systems to better support FDA's mission. It aligns directly with Obj. 2.2 of the HHS strategic plan: Protect the Public Against Injuries and Environmental Threats, enables FDA Centers to meet FDA Goal 4: Improve the Quality and Safety of Manufactured Products and the Supply Chain, and helps support PMA Expanded E-Government. FDA uses MARCS' applications to: plan FDA field activities and assign staff to inspections, investigations, recalls and other compliance activities; track and control samples and the results of laboratory analysis; collect and maintain information from field activities; collect performance data, particularly that related to FDAAA; send Prior Notice for food imports to Customs and accept import product information from Customs for screening; screen 18 million import lines a year based on calculated risk; collect information about the facilities FDA regulates and those in the import supply chain for risk-based targeting; provide FDA Centers with information on inspections, compliance actions, recalls, laboratory analysis and facilities. Although legacy systems help meet current performance goals, their weaknesses pose increasing risk. HW/SW platforms are aging and inconsistent with EA standards. Import functionality has outgrown platforms, degrading performance; as imports increase, this gap widens. Platforms don't support 24/7 operation--a Bioterrorism Act requirement. The paradigm on which import screening was based has changed; new technologies make an expert system risk-based approach possible. Interfaces with FDA labs are inadequate, and sample tracking inefficient. Enhancements are delayed due to the high cost of maintaining the legacy framework. MARCS is addressing these problems through a combination of technical upgrades, redesign of core components, and enhancements to existing functionality. Migration of MARCS' legacy systems to the Web is complete and migration to Sun/Solaris platforms on track for 2008. Integration, reduced maintenance, and increased functionality will be accomplished through a reusable service-based approach. A planned alignment to FDA-wide Product Quality investment and Import Safety Workgroup's recommendations, including a system inventory required for interoperability, continuity of operations, and implementation, will enable FDA to move away from stove-piped and redundant systems across the enterprise.
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?
2006-12-11
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.
yes
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?)
MARCS supports Expanded E-Government. MARCS breaks down bureaucratic divisions by combining activities and interfaces for domestic and import operations, and will support dynamic work assignment to produce a nation-wide rather than region focused workforce. MARCS supports information sharing with USDA, states (eSAF), internationally (PNSI, COMSTAT), and within FDA through automated and interactive applications. MARCS automates internal processes (expert system PREDICT, sample distribution).
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 3
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?
MARCS provides automated support to the compliance operations that ensure food, drugs, and medical devices are safe and effective, whether made in the US or abroad. It screens 18 million imports every year using data from Customs to decide whether they can enter. It allows FDA to use the findings of state food investigators, tracks samples to and from FDA labs, manages recall activities and consumer complaints. In short, it gives field staff the integrated tools it needs to protect the public.
20. What is the percentage breakout for the total FY2009 funding request for the following? (This should total 100%)
AreaPercentage
Hardware0
Software0
Services91
Other9
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?
yes
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 Resources3.5850.7001.2911.301
Acquisition Budgetary Resources23.29210.91911.2219.014
Maintenance Budgetary Resources6.1312.2175.7479.094
Government FTE Cost2.4800.9601.2321.297
# of FTEs88108
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.
Funding is increased by P.L. 110-252, the "Supplemental Appropriations Act, 2008", signed into law on June 30, 2008. The appropriation increases the budget authority for increasing food protection, enhancing the safety of drugs, medical devices and biologics, and boosting the strength of the agency's workforce. Due to the short time between receiving the appropriation and submitting the FY2010 President's Budget Request, a full impact analysis is not complete. Once the analysis is complete, the Business Case will be updated to reflect the additional funding. The total increase due to the supplemental is $5.000M. This is for Predictive Risk-based Evaluation for Dynamic Import Compliance Targeting (PREDICT). This is reflected in the Summary of Spending in FY08 in the acquisition section as follows: an additional $4.010M in Contract Services (development, data sharing, imports modernization, deployment, PM, CPIC, EA) for a new total of $13.070M, and $0.340M in Security for a new total of $0.640M. And in the maintenance section as follows: an additional $0.600M in Contract Services (Current Events Intelligence, data clean up, PM, CPIC, EA) for a new total of $5.780M, and an additional $0.0.50M in Security for a new total of $0.300M. In addition, funds have been added to FY10 in order to provide for the operations and maintenance of PREDICT. This is reflected in the Summary of Spending in FY10 in the maintenance section as follows: an additional $2.760M in Contract Services for a new total of $8.604M, and an additional $0.240M in Security for a new total of $0.490M. An additional $1.200M in a further supplemental for FY09 is included. This is reflected in the Summary of Spending in FY09 in the acquisition section as follows: an additional $1.080M in Contract Services for a new total of $10.801M, and $0.120M in Security for a new total of $0.420M. As the timeframe for incorporating these funds into this investment has been short, this adjustment was not accomplished before the HHS deadline for submission.

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
12006Effective Management of Human Capital/Information Technology/ResourcesTechnologyStandards Compliance and Deviations% of Infrastructure brought to Current Standard (Web from C/S). Outcome: Improved application maintainability and reduced cost0% of infrastructure100% of infrastructureSuccess. 100% of existing legacy converted from C/S to Web
22006S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesRisk# of import product types screened based on calculated risk factors. Outcome: Higher may proceed rate for low risk products, more resources for higher risk food products0 food product typesdevelopment of pilot for screeningSuccess. Completed
32006S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsCustomer Complaints% Reduction in Complaints about printing capabilities in the field. Outcome: Increased customer satisfaction and productivity for field employeesOngoing complaints100% reductionSuccess. 100% --Release of enhancements packaged with Web Version of FACTS/OASIS eliminated all print complaints
42006Effective Management of Human Capital/Information Technology/ResourcesMission and Business ResultsWorkforce Planning# of districts that have automated support for assignment & scheduling. Outcome: Improved management of worker resources0 districts19 districtsSuccess. 19 districts. Completed
52007Effective Management of Human Capital/Information Technology/ResourcesTechnologyExternal Data Sharing# of Center Registration Systems Accessed via Center Views. Outcome: Greater efficiency of import reviewers due to faster information sharing0 systems4 systemsSuccess. 4 Center systems accessed via web through Center Views
62007S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesRisk# of import product types screened based on calculated risk factors. Outcome: Higher may proceed rate for low risk products, more resources for higher risk food products0 food product types1 food product typeSuccess. 1 Product Type (Seafood) tested
72007S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesEfficiency# of imported products screened per year within a window of two hours. Outcome: Meeting the two hour time window available for screening from Customs and Border Patrol operations as required by law. Reduced impact on commerce (cost to industry)14,000,000 imported products15,000,000 imported productsSuccess. 15,000,000 imported products
82007Effective Management of Human Capital/Information Technology/ResourcesTechnologyExternal Data Sharing% of Interfaces with Center Databases standardized. Outcome: Greater workflow efficiency and more effective decision making resulting in stronger enforcement cases20% of interfaces70% of interfacesFailure. Goal not met. Work delayed.
92007S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsPopulation Health Management and Consumer Safety# of states that have access to an automated checklist for BSE threat analysis. Outcome: Enables the states to conduct effective BSE inspections0 states50 statesSuccess. 50 states
102008Effective Management of Human Capital/Information Technology/ResourcesTechnologyStandards Compliance and Deviations% of Infrastructure brought to Current Standard (VMS to Unix). Outcome: Reliable infrastructure supporting key agency missions20% of infrastructure80% of infrastructureSuccess. UNIX I implemented. All major systems and databases now at current standard.
112008Effective Management of Human Capital/Information Technology/ResourcesTechnologyExternal Data Sharing# of Center Registration Systems Accessed via Center Views. Outcome: Greater efficiency of import reviewers due to faster information sharing4 systems6 systemsSuccess. Center Views accesses 8 Center systems.
122008Effective Management of Human Capital/Information Technology/ResourcesTechnologyInternal Data Sharing% disparate functionality harmonized between legacy systems. Outcome: Greater efficiency for investigators, analysts, and compliance officers0% of functionality20% of functionalitySuccess. Single Sign On and Firm Finder.
132008S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesRisk# of import product types screened based on calculated risk factors. Outcome: Higher may proceed rate for low risk products, more resources for higher risk food products1 food product type3 food product typesFailure. PREDICT Pilot supports 1 food product type.
142008S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesEfficiency# of imported products screened per year within a window of two hours. Outcome: Meeting the two hour time window available for screening from Customs and Border Patrol operations as required by law. Reduced impact on commerce (cost to industry)15,000,000 imported products16,000,000 imported productsSuccess. More than 16,000,000 imported products.
152008Effective Management of Human Capital/Information Technology/ResourcesCustomer ResultsCustomer Complaints% comments are complaints about screens. Outcome: Increased user satisfaction and productivity.65% of comments are complaints60% of comments are complaintsSuccess. Complaints reduced to less than 60%.
162008S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsBorder and Transportation Security# of sources automatically mined for bioterrorism food processing. Outcome: Lower risk of imminent threats due to food0 sources1 sourceSuccess. PREDICT Pilot automatically mines 1 source.
172008S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsCriminal Investigation and Surveillance% of compliance actions share automated workflow actions and evidence captured with Centers. Outcome: Increased efficiency and speed in producing successful performance cases0% of compliance actions20% of compliance actionsSuccess. Data pulled from Domestics into Case Management System
182008S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsWorkforce Planning% of Workforce Planning/scheduling functions in current stovepipes integrated. Outcome: Decreased cost of assigning staff to inspections20% of workforce functions25% of workforce functionsSuccess. National Sample Distributor implemented.
192008S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyIT Contribution to Process, Customer, or Mission# of work functions available on mobile devices. Outcome: Decreased amount of time needed to perform inspections, investigations, exams, and collections2 work functions3 work functionsSuccess. Establishment Inspection Report, 483 (adverse observations), and International Mail Facility
202009S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyStandards Compliance and Deviations% of infrastructure brought to current standard (VMS to Unix). Outcome: Reliable infrastructure supporting key agency missions80% of infrastructure100% of infrastructureTBD
212009Effective Management of Human Capital/Information Technology/ResourcesTechnologyExternal Data Sharing% of Interfaces with Center Databases standardized. Outcome: Greater workflow efficiency and more effective decision making resulting in stronger enforcement cases0% of interfaces20% of interfacesTBD
222009Effective Management of Human Capital/Information Technology/ResourcesTechnologyInternal Data Sharing% disparate functionality harmonized between legacy systems. Outcome: Greater efficiency for investigators, analysts, and compliance officers20% of functionality36% of functionalityTBD
232009S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesRisk# of import product types screened based on calculated risk factors. Outcome: Higher may proceed rate for low risk products, more resources for higher risk food products3 food product types80% of food product typesTBD
242009S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesEfficiency# of imported products screened per year within a window of two hours. Outcome: Meeting the two hour time window available for screening from Customs and Border Patrol operations as required by law. Reduced impact on commerce (cost to industry)16,000,000 imported products17,000,000 imported productsTBD
252009Effective Management of Human Capital/Information Technology/ResourcesCustomer ResultsCustomer Complaints% comments are complaints about screens. Outcome: Increased user satisfaction and productivity.60% of comments are complaints55% of comments are complaintsTBD
262009S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsBorder and Transportation Security# of sources automatically mined for bioterrorism food processing. Outcome: Lower risk of imminent threats due to food1 source2 sourcesTBD
272009S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsCriminal Investigation and Surveillance% of compliance actions share automated workflow actions and evidence captured with Centers. Outcome: Increased efficiency and speed in producing successful performance cases20% of compliance actions30% of compliance actionsTBD
282009S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsWorkforce Planning% of Workforce Planning/scheduling functions in current stovepipes integrated. Outcome: Decreased cost of assigning staff to inspections25% of workforce functions30% of workforce functionsTBD
292009S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyIT Contribution to Process, Customer, or Mission# of work functions available on mobile devices. Outcome: Decreased amount of time needed to perform inspections, investigations, exams, and collections3 work functions4 work functionsTBD
302010Effective Management of Human Capital/Information Technology/ResourcesTechnologyStandards Compliance and Deviations% of Infrastructure 24/7 compliant that is required to be 24/7 Compliant. Outcome: Compliance with Bioterrorism Act to check every food product and conformation to Customs and Border Patrol's two hour time window0% of infrastructure100% of infrastructureTBD
312010Effective Management of Human Capital/Information Technology/ResourcesTechnologyExternal Data Sharing% of Interfaces with Center Databases standardized. Outcome: Greater workflow efficiency and more effective decision making resulting in stronger enforcement cases20% of interfaces70% of interfacesTBD
322010Effective Management of Human Capital/Information Technology/ResourcesTechnologyInternal Data Sharing% disparate functionality harmonized between legacy systems. Outcome: Greater efficiency for investigators, analysts, and compliance officers36% of functionality48% of functionalityTBD
332010S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesRisk% of import product types screened based on calculated risk factors. Outcome: Higher may proceed rate for low risk products, more resources for higher risk drug products0% of drug product types80% of drug product typesTBD
342010S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesEfficiency# of imported products screened per year within a window of two hours. Outcome: Meeting the two hour time window available for screening from Customs and Border Patrol operations as required by law. Reduced impact on commerce (cost to industry)17,000,000 imported products18,000,000 imported productsTBD
352010Effective Management of Human Capital/Information Technology/ResourcesCustomer ResultsCustomer Complaints% of comments are complaints about screens. Outcome: Increased user satisfaction and productivity.55% of comments are complaints50% of comments are complaintsTBD
362010S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsBorder and Transportation Security# of sources automatically mined for bioterrorism food processing. Outcome: Lower risk of imminent threats due to food2 sources3 sourcesTBD
372010S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsCriminal Investigation and Surveillance% of compliance actions share automated workflow actions and evidence captured with Centers. Outcome: Increased efficiency and speed in producing successful performance cases30% of compliance actions40% of compliance actionsTBD
382010S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsWorkforce Planning40% of compliance actions30% of workforce functions45% of workforce functionsTBD
392010S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyIT Contribution to Process, Customer, or Mission# of work functions available on mobile devices. Outcome: Decreased amount of time needed to perform inspections, investigations, exams, and collections4 work functions5 work functionsTBD
402011Effective Management of Human Capital/Information Technology/ResourcesTechnologyExternal Data Sharing% of Interfaces with Center Databases standardized. Outcome: Greater workflow efficiency and more effective decision making resulting in stronger enforcement cases70% of interfaces80% of interfacesTBD
412011Effective Management of Human Capital/Information Technology/ResourcesTechnologyInternal Data Sharing% disparate functionality harmonized between legacy systems. Outcome: Greater efficiency for investigators, analysts, and compliance officers48% of functionality60% of functionalityTBD
422011S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesRisk% of import product types screened based on calculated risk factors. Outcome: Higher may proceed rate for low risk products, more resources for higher risk device products0% of device product types80% of device product typesTBD
432011S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesEfficiency# of imported products screened per year within a window of two hours. Outcome: Meeting the two hour time window available for screening from Customs and Border Patrol operations as required by law. Reduced impact on commerce (cost to industry)18,000,000 imported products19,000,000 imported productsTBD
442011Effective Management of Human Capital/Information Technology/ResourcesCustomer ResultsCustomer Complaints% of comments are complaints about screens. Outcome: Increased user satisfaction and productivity.50% of comments are complaints45% of comments are complaintsTBD
452011S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsWorkforce Planning% of Workforce Planning/scheduling functions in current stovepipes integrated. Outcome: Decreased cost of assigning staff to inspections45% of workforce functions60% of workforce functionsTBD
462011S.O. 2.2 - Protect the public against injuries and environmental threatsTechnologyIT Contribution to Process, Customer, or Mission# of work functions available on mobile devices. Outcome: Decreased amount of time needed to perform inspections, investigations, exams, and collections5 work functions6 work functionsTBD
472012Effective Management of Human Capital/Information Technology/ResourcesTechnologyInternal Data Sharing% disparate functionality harmonized between legacy systems. Outcome: Greater efficiency for investigators, analysts, and compliance officers60% of functionality68% of functionalityTBD
482012S.O. 2.2 - Protect the public against injuries and environmental threatsProcesses and ActivitiesRisk% of import product types screened based on calculated risk factors. Outcome: Higher may proceed rate for low risk products, more resources for higher risk other regulated products0% of other regulated product types80% of other regulated product typesTBD
492012S.O. 2.2 - Protect the public against injuries and environmental threatsCustomer ResultsCustomer Complaints% of comments are complaints about screens. Outcome: Increased user satisfaction and productivity.45% of comments are complaints40% of comments are complaintsTBD
502012S.O. 2.2 - Protect the public against injuries and environmental threatsMission and Business ResultsWorkforce Planning% of Workforce Planning/scheduling functions in current stovepipes integrated. Outcome: Decreased cost of assigning staff to inspections60% of workforce functions70% of workforce functionsTBD

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 Mission Accomplishments and Regulatory Compliance Services (MARCS). Migration to Web (complete in 2006) Migration to Unix (underway) upgrade to Oracle 10G (inconjunction with Unix migration)
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 %
1FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Security ManagementAccess Control  No Reuse2
2FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Human Capital / Workforce ManagementResource Planning and Allocation  No Reuse2
3FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Routing and SchedulingInbound Correspondence Management  No Reuse2
4FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Knowledge ManagementKnowledge Engineering  No Reuse2
5FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Document ManagementDocument Review and Approval  No Reuse1
6FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Tracking and WorkflowCase Management  No Reuse2
7FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Knowledge DiscoveryData Mining  No Reuse2
8FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Knowledge ManagementCategorization  No Reuse2
9FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.VisualizationMapping / Geospatial / Elevation / GPS  No Reuse0
10FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.SearchQuery  No Reuse1
11FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Customer Relationship ManagementCustomer Analytics  No Reuse1
12FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Data ManagementData Classification  No Reuse0
13FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Knowledge ManagementKnowledge Distribution and Delivery  No Reuse2
14FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Security ManagementAudit Trail Capture and Analysis  No Reuse2
15FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Management of ProcessesRisk Management  No Reuse4
16FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Customer PreferencesAlerts and Notifications  No Reuse2
17FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Investment ManagementStrategic Planning and Mgmt  No Reuse1
18FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Forms ManagementForms Modification  No Reuse2
19FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Tracking and WorkflowConflict Resolution  No Reuse2
20FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Customer Initiated AssistanceOnline Help  No Reuse0
21FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Organizational ManagementWorkgroup / Groupware  No Reuse2
22FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Document ManagementDocument Revisions  No Reuse1
23FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Investment ManagementPerformance Management  No Reuse2
24FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Data ManagementLoading and Archiving  No Reuse0
25FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Human Capital / Workforce ManagementTeam / Org Management  No Reuse2
26FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Data ManagementExtraction and Transformation  No Reuse0
27FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Development and IntegrationLegacy Integration  No Reuse3
28FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Human ResourcesTime Reporting  No Reuse0
29FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Business IntelligenceDemand Forecasting / Mgmt  No Reuse3
30FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Security ManagementDigital Signature Management  No Reuse2
31FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Data ManagementMeta Data Management  No Reuse1
32FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Data ManagementData Exchange  No Reuse1
33FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Management of ProcessesBusiness Rule Management  No Reuse3
34FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Knowledge ManagementKnowledge Capture  No Reuse2
35FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Development and IntegrationData Integration  No Reuse2
36FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.SearchPattern Matching  No Reuse2
37Firm Management ServicesFind information on firms in FDA databasesKnowledge ManagementInformation RetrievalInformation Retrieval Internal2
38FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Data ManagementData Cleansing  No Reuse2
39FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Security ManagementIdentification and Authentication  No Reuse2
40FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Tracking and WorkflowProcess Tracking  No Reuse2
41FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Data ManagementData Recovery  No Reuse0
42FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Document ManagementDocument Referencing  No Reuse1
43FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Forms ManagementForms Creation  No Reuse2
44FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Records ManagementDocument Classification  No Reuse2
45FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Development and IntegrationEnterprise Application Integration  No Reuse2
46FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Routing and SchedulingOutbound Correspondence Management  No Reuse2
47FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.CollaborationDocument Library  No Reuse2
48FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Human Capital / Workforce ManagementContingent Workforce Management  No Reuse2
49FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Business IntelligenceDecision Support and Planning  No Reuse3
50FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Knowledge ManagementInformation Sharing  No Reuse2
51FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Management of ProcessesQuality Management  No Reuse2
52FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Customer Relationship ManagementContact and Profile Management  No Reuse1
53FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.ReportingAd Hoc  No Reuse1
54FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.CollaborationTask Management  No Reuse2
55FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Customer Relationship ManagementPartner Relationship Management  No Reuse2
56FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Management of ProcessesGovernance / Policy Management  No Reuse2
57FDA Mission Accomplishments and Regulatory Compliance ServicesThe MARCS program is a comprehensive integration and reengineering of nine legacy systems with two major objectives: upgrading their technical infrastructure and better integrating and enhancing their business functionality to support FDA's expanding operational needs.Knowledge DiscoveryModeling  No Reuse2
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)
1Access ControlComponent FrameworkData ManagementDatabase ConnectivityJava Database Connectivity by: Sun Microsystems, Inc.
2Resource Planning and AllocationService Platform and InfrastructureSoftware EngineeringModelingRational Rose by: International Business Machines Corp.
3Inbound Correspondence ManagementService Platform and InfrastructureSoftware EngineeringIntegrated Development EnvironmentMacromedia RoboHelp by: Adobe Systems
4Knowledge EngineeringService Platform and InfrastructureSupport PlatformsDependent PlatformMicrosoft Windows XP by: Microsoft Corporation
5Document Review and ApprovalService Platform and InfrastructureDelivery ServersApplication ServersOracle Application Server by: Oracle Corporation
6Case ManagementService Platform and InfrastructureDatabase / StorageDatabaseMicrosoft Office Access by: Microsoft Corporation
7Data MiningService Interface and IntegrationInteroperabilityData Format / ClassificationExtensible Markup Language (XML) 1.1 by: World Wide Web Consortium
8CategorizationService Platform and InfrastructureDelivery ServersWeb ServersMicrosoft Windows 2000 by: Microsoft Corporation
9Mapping / Geospatial / Elevation / GPSComponent FrameworkUser Presentation / InterfaceContent RenderingCascading Style Sheets, level 1 by: World Wide Web Consortium
10QueryComponent FrameworkSecuritySupporting Security ServicesPVCS Tracker by: Synergex
11Customer AnalyticsService Platform and InfrastructureSupport PlatformsDependent PlatformOpenVMS by: Hewlett-Packard Corporation
12Data ClassificationService Interface and IntegrationIntegrationEnterprise Application IntegrationJava 2 Enterprise Edition by: Sun Microsystems, Inc.
13Knowledge Distribution and DeliveryService Interface and IntegrationInteroperabilityData Format / ClassificationDocument Type Definition by: TBD
14Audit Trail Capture and AnalysisComponent FrameworkSecuritySupporting Security ServicesEntrust Authority by: Entrust
15Risk ManagementService Interface and IntegrationIntegrationEnterprise Application IntegrationUniversal Description, Discovery and Integration by: Organization for the Advancement of Structured Information Standards
16Alerts and NotificationsComponent FrameworkData ManagementDatabase ConnectivityJava Database Connectivity by: Sun Microsystems, Inc.
17Strategic Planning and MgmtService Access and DeliveryAccess ChannelsWeb BrowserWindows Internet Explorer by: Microsoft Corporation
18Forms ModificationComponent FrameworkBusiness LogicPlatform Independent TechnologiesEnterprise Java Beans by: Sun Microsystems, Inc.
19Conflict ResolutionService Interface and IntegrationInteroperabilityData Format / ClassificationMicrosoft Office Word by: Microsoft Corporation
20Online HelpService Platform and InfrastructureSoftware EngineeringSoftware Configuration ManagementRational RequisitePro by: International Business Machines Corp.
21Workgroup / GroupwareService Platform and InfrastructureDelivery ServersApplication ServersOracle Application Server by: Oracle Corporation
22Document RevisionsService Platform and InfrastructureDatabase / StorageDatabaseOracle Database 10g Release 2 Enterprise Edition by: Oracle Corporation
23Performance ManagementService Platform and InfrastructureSoftware EngineeringTest ManagementQuick Test Professional by: Hewlett-Packard Development Company, L.P.
24Loading and ArchivingComponent FrameworkUser Presentation / InterfaceContent RenderingDynamic Hypertext Markup Language by: TBD
25Team / Org ManagementService Interface and IntegrationIntegrationEnterprise Application IntegrationXML Linking Language (XLink) Version 1.0 by: World Wide Web Consortium
26Extraction and TransformationService Platform and InfrastructureDatabase / StorageDatabaseDocumentum by: EMC Corporation
27Legacy IntegrationService Interface and IntegrationIntegrationMiddlewarePL/SQL by: Oracle Corporation
28Time ReportingService Platform and InfrastructureSoftware EngineeringTest ManagementMercury Interactive WinRunner by: Hewlett-Packard Corporation
29Demand Forecasting / MgmtService Platform and InfrastructureSoftware EngineeringIntegrated Development EnvironmentOracle JDeveloper by: Oracle Corporation
30Digital Signature ManagementComponent FrameworkData ManagementDatabase ConnectivityJava Database Connectivity by: Sun Microsystems, Inc.
31Meta Data ManagementService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Asynchronous Transfer Mode by: ITU Telecommunication Standardization Sector (ITU-T)
32Data ExchangeService Interface and IntegrationInterfaceService Description / InterfaceOracle by: Oracle Corporation
33Business Rule ManagementComponent FrameworkData ManagementReporting and AnalysiseXtensible Business Reporting Language by: XBRL International, Inc.
34Knowledge CaptureService Platform and InfrastructureSoftware EngineeringSoftware Configuration ManagementApache Ant by: Apache Software Foundation
35Data IntegrationComponent FrameworkBusiness LogicPlatform Independent TechnologiesJavaScript by: Sun Microsystems, Inc.
36Pattern MatchingService Platform and InfrastructureSoftware EngineeringSoftware Configuration ManagementPVCS Version Manager by: Synergex
37Information RetrievalService Interface and IntegrationInteroperabilityData TransformationBusiness Objects XI by: SAP AG
38Data CleansingComponent FrameworkData ManagementReporting and AnalysisOracle Enterprise Manager by: Oracle Corporation
39Identification and AuthenticationService Platform and InfrastructureSoftware EngineeringTest ManagementLoadRunner by: Hewlett-Packard Development Company, L.P.
40Process TrackingComponent FrameworkUser Presentation / InterfaceDynamic Server-Side DisplayJava Server Pages by: Sun Microsystems, Inc.
41Data RecoveryService Platform and InfrastructureSoftware EngineeringIntegrated Development EnvironmentOracle Forms by: Oracle Corporation
42Document ReferencingComponent FrameworkUser Presentation / InterfaceContent RenderingAdobe Acrobat by: Adobe Systems
43Document ReferencingComponent FrameworkData ManagementDatabase ConnectivityObject Linking and Embedding, Database by: Microsoft Corporation
44Document ReferencingService Platform and InfrastructureHardware / InfrastructureWide Area Network (WAN)Integrated Services Digital Network (ISDN) - Core Aspects of Frame Protocol for Use with Frame Relay Bearer Service by: ANSI
45Document ReferencingService Platform and InfrastructureSoftware EngineeringIntegrated Development EnvironmentOracle JDeveloper by: Oracle Corporation
46Forms CreationService Platform and InfrastructureDatabase / StorageDatabaseOracle Enterprise Manager 10g Grid Control by: Oracle Corporation
47Document ClassificationService Interface and IntegrationIntegrationMiddlewareIBM Websphere MQ by: International Business Machines Corp.
48Enterprise Application IntegrationService Platform and InfrastructureDelivery ServersPortal ServersOracle Portal by: Oracle Corporation
49Outbound Correspondence ManagementService Access and DeliveryService TransportService TransportPoint-to-Point Protocol (PPP) by: The Internet Engineering Task Force
50Document LibraryComponent FrameworkData ManagementDatabase ConnectivityJava Database Connectivity by: Sun Microsystems, Inc.
51Contingent Workforce ManagementComponent FrameworkData ManagementReporting and AnalysisOLAP Services by: Microsoft Corporation
52Decision Support and PlanningComponent FrameworkUser Presentation / InterfaceStatic DisplayHyper Text Markup Language by: International Organization for Standardization
53Information SharingService Platform and InfrastructureSoftware EngineeringTest ManagementMercury Interactive Test Director by: Hewlett-Packard Corporation
54Quality ManagementService Platform and InfrastructureSupport PlatformsDependent PlatformSun Solaris 9 by: Sun Microsystems, Inc.
55Contact and Profile ManagementComponent FrameworkBusiness LogicPlatform Dependent TechnologiesMicrosoft Visual Basic by: Microsoft Corporation
56Ad HocComponent FrameworkData ManagementDatabase ConnectivityJava Database Connectivity by: Sun Microsystems, Inc.
57Task ManagementService Interface and IntegrationInteroperabilityData Types / ValidationXML Schema by: World Wide Web Consortium
58Partner Relationship ManagementComponent FrameworkUser Presentation / InterfaceStatic DisplayPortable Document Format by: Adobe Systems
59Governance / Policy ManagementComponent FrameworkSecuritySupporting Security ServicesLightweight Directory Access Protocol by: The Internet Engineering Task Force
60ModelingComponent FrameworkData InterchangeData ExchangeElectronic Data Interchange (EDI) by: National Institute of Standards and Technology
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.
Yes. Through its interfaces with CBP's systems, MARCS will continue to enable FDA staff to work collaboratively at the U.S. borders with CBP to screen, review, hold, or seize FDA regulated products that might cause harm to humans or other animals. Neither CBP nor FDA could accomplish the full mission by themselves, but the automated systems that are currently in place provide limited support to this funciton. As FDA evolves to MARCS and CBP implements ACE this interaction should be even tighter. In addition to providing more effective screening for safety, this collaborarion reduces the impact on trade that would be the result of separate systems.

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-05-22
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:
Risk was one of the major factors in selecting the overall MARCS approach (the alternative to migrate to web and rebuild over time) because FDA's regulatory environment is dynamic and cannot be put in position where change cannot be accommodated quickly. Where possible, higher risk projects are scheduled without follow on dependencies so that a schedule delay will not impact other projects. Cost and schedule are risk adjusted based on the particulars of a project. This is done through an analogous and experience-based approach. For example, the Web Migration project was risk adjusted in both cost and schedule. In particular, the amount of time and money allocated to address issues that might arise after implementation was increased due to the risk of implementing this major infrastructure change across the entire United States and a total base of close to 5,000 users. The original cost and time estimates for this portion of the project were doubled. Due to a phased implementation approach, the number of issues after implementation was surprisingly low. This meant that this project was below budget and ahead of schedule because anticipated risks did not materialize into issues. Another example is the UNIX Migration project. An estimate was produced for this by a contractor. This estimate was essentially doubled in both time and cost. The MARCS management team felt that the estimate did not take into full account the risks from organizational and platform dependencies. This is a critical path project since effective future development is reliant upon upgraded infrastructure. The Standardized Evidence and Reference Services (SERS) project was also risk adjusted. Additional time and money has been included in its plan. This component will be accessed by almost every application within MARCS, so it is the source of a number of dependencies. This has also resulted in risk adjustments being made in the planning of other projects (such as Mobile Automated Regulatory Services) that are dependent on SERS. Each project in MARCS is approached on its individual merits and risk adjusted as appropriate as illustrated in the examples above.

COST & SCHEDULE


1. Does the earned value management system meet the criteria in ANSI/EIA Standard 748?
yes
2. Is the CV% or SV% greater than ± 10%?
yes
2.a. If yes, was it the?
Both
2.b. If yes, explain the variance.
As a whole, the investment is not outside of the +/-10% variance threshold. SS Cost Variance is greater than allowable threshold but the overall cost variance is within 10%. When the Web Migration project began, monies were set aside in Steady State to address expected post implementation issues. Due to the size of the user base, the applications involved, and the geographical distribution of the user base, it was expected that a number of issues would be discovered after rolling out the web interface. However, a strategy of incremental deployment was utilized during development. This allowed early deployment to field locations as test implementations. The tests conducted during this time revealed a number of shortcomings that were corrected. This was all tracked as DME spending. Upon implementation of the entire project, the number of errors that were discovered had been significantly reduced due to the early deployment and testing. This resulted in a lower SS level of spending than was expected. The lower level of SS spending resulted in the SS Operations FY06- milestone variance of $0.247M. Monies were also earmarked for dealing with issues that were expected to arise after implementation of the DME milestone UNIX Migration Phase I in FY07. Implementation of this project has been delayed until August of 2008 as the scope was expanded due to an EA requirement to upgrade to Oracle 10g. The implementation was delayed as additional work was added to this milestone. This additional work included migrating to Oracle 10g and moving some elements from Phase II into Phase I. As a result, SS funds that were expected to be spent in FY07 have not been spent. These funds represent cost variance in the milestone SS Operations FY07 of $0.800 of the total $1.016M. Monies were also earmarked for dealing with issues that were expected to arise after implementation of the DME milestone UNIX Migration Phase II in FY08. This has been delayed due to the slippage in UNIX 1 and is expected to be completed in March of 2009. This accounts for $0.600M of the current cost variance of SS Operations FY08 of $0.844M.
2.c. If yes, what corrective actions are being taken?
As a whole, the investment is not outside of the +/- 10% variance threshold. Due to supplemental funding received and changes in planning MARCS, the investment milestones will be adjusted. This will be done for three main reasons. The first is to address the added supplemental funds. The second is to address new requirements placed on MARCS due to the initiatives of the Harmonized Inventory investment. The third is to address the SS Cost Variance. The SS Cost Variance will be addressed directly by re-categorizing the current DME expenses for UNIX 1 and UNIX II to SS. These were originally classified as DME expenses based on a strict interpretation of what constitutes DME. As this was not just bug fixes, this was classified as such. In reality, these two projects are infrastructure upgrades that do not add new functionality. UNIX 1 is currently scheduled to be implemented during September, 2008. This implementation should produce an increase in SS spending that will also help to address the variance. Because of all the new work being added to MARCS, over time, the current SS variance will be reduced as the amount of SS spending increases.
3. Has the investment re-baselined during the past fiscal year?
no