Exhibit 300 (BY2009) - PHIN: BioSense, Centers for Disease Control and Prevention

1. Date of Submission:

2008-02-04

2. Agency:

009

3. Bureau:

20

4. Name of this Capital Asset:

CDC PHIN: BioSense

5. Unique Project Identifier:

009-20-01-03-01-1163-00

6. What kind of investment will this be in FY2009?

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.

BioSense is a national program intended to improve the nation's capabilities for conducting near real-time biosurveillance and health situational awareness through access to existing data from healthcare organizations across the country and national data sources. BioSense is developing and implementing enhanced capabilities for early event detection and real-time health situational awareness. The objective is to expedite event recognition and response coordination among federal, state, and local public health and healthcare organizations by providing each level of public health access to the same data, at the same time. BioSense receives, analyzes, and evaluates health data from national data sources including DoD and VA hospitals and ambulatory care clinics, and a large commercial clinical laboratory. In addition, local hospitals, healthcare systems, and syndromic surveillance systems transmit real-time clinical data to BioSense. Public health uses BioSense data in many ways; to monitor disease trends in their communities, to track potential disease cases, and to incorporate with other local surveillance efforts. In 2005, the program's recruitment goal was to have one hospital from 10 different cities transmitting real-time data to BioSense. This goal was achieved. In 2006, the program's recruitment goal is to have 350 hospitals transmitting real-time data to BioSense. This goal was achieved. 2007 goals include continuing to build BioSense as a network of networks. BioSense supports four of CDC's Preparedness goals: decrease the time needed to classify health events as terrorism or naturally occurring, improve the timeliness and accuracy of communications regarding threats to the public's health, decrease the time to identify causes, risk factors, and appropriate interventions for those affected by threats to the public's health, and decrease the time needed to provide countermeasures and health guidance to those affected by threats to the public's health.

9. Did the Agency's Executive/Investment Committee approve this request?

yes

9.a. If "yes," what was the date of this approval?

2007-06-26

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?

Senior/Expert-level

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?)

BioSense was architected to provide states and local health departments a national repository for visualizing situational awareness thus creating a single point of access to Biosurveillance aggregated data. Prior to BioSense, situational awareness had no national representation, so to create awareness was a manual effort for the public and government entities that own the data. The system allows mapping of progressing syndromes to be communicated via electronic media.

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?

yes

14.b. If yes, what is the name of the PARTed program?

2006: CDC - Terrorism: Biosurveillance

14.c. If yes, what rating did the PART receive?

Results Not Demostrated

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)?

yes

19. Is this a financial management system?

no

20. What is the percentage breakout for the total FY2009 funding request for the following? (This should total 100%)

Area	Percentage
Hardware	0
Software	0
Services	100
Other	0

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?

no

22. Contact information of individual responsible for privacy related questions.

Name	Alice M. Brown
Phone Number	770-488-8223
Title	IT Security Project Manager
Email	AMBrown1@cdc.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?

no

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 Type	Py-1 & Earlier -2006	PY 2007	CY 2008	BY 2009
Planning Budgetary Resources	0.300	0.000	0.000	0.000
Acquisition Budgetary Resources	104.210	29.440	19.805	28.300
Maintenance Budgetary Resources	2.440	2.440	2.400	2.400
Government FTE Cost	5.250	4.820	6.000	6.000
# of FTEs	17	45	45	45

2. Will this project require the agency to hire additional FTE's?

yes

2.a. If "yes," how many and in what year?

In 2006 this investment had 17 FTEs, an additional 13 have been hired bringing the total to 30 as of 08/20/07. Leadership believes the current need for the remainder of '07 and early '08 is to hire an additional 15-16 FTEs bringing the total up to 45. The Summary of Spending indicated 45 FTE positions by the end of 2007 and through 2013. The BioSense leadership believes this staffing level will yield the highest return on investment and allow for efficient development and operations.

3. If the summary of spending has changed from the FY2008 President's budget request, briefly explain those changes.

The extramural amount for BioSense is as a result of the new ceiling letter. Extramural dollars are reflected in another entry in Part V of the Exhibit 53.

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.

Row	Fiscal Year	Strategic Goal Supported	Measurement Area	Measurement Grouping	Measurement Indicator	Baseline	Planned Improvement to the Baseline	Actual Results
1	2006	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to the early detection and quantification of possible bioterrorism events.	30,143,598 records	Increase by 10% over the previous year's volume the number of health interactions related to the early detection and quantification of possible bioterrorism events that are made available for analysis to local, state, federal public health agencies	As of April 2006: Achieved more than 20% over the previous year's volume
2	2006	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of state and local Public Health Department's serviced in key jurisdictions	TBD	33% of State and local public health agencies in key jurisdictions have access to BioSense data	March 2007: 124 public health jurisdictions had access to BioSense data
3	2006	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	7 data sources	CDC acquires sources from 8 potential data sources	Sept 2006: 46 real time data sources and 466 DoD and 863 VA healthcare facilities sending data to BioSense
4	2006	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	Data completeness varies by Source from 2-4 days	BioSense data is updated within 24 hours of receipt from data providers	Sept 2006: Average 2.81 hours from "Time of Visit" to "Viewable in BioSense application" for real time data sources
5	2007	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	2.81 hours from "Time of Visit" to "Viewable in BioSense application"	No more than 2 hours from "Time of Visit" to "Viewable in BioSense application"	In progress
6	2007	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to early detection and quantification of possible bioterrorism events.	36 million records	Increase by 10% over the previous year's volume the number of health interactions related to the early detection and quantification of possible bioterrorism events that are made available for analysis to local, state, federal public health agencies	In progress
7	2007	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of eligible customer services	50% of State and local public health agencies in key jurisdictions have to access BioSense data	75% of State and local public health agencies in key jurisdictions have to access BioSense data	July 2007: 137 public health jurisdictions had access to BioSense data.
8	2007	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	11 data sources and 39 hospitals sending foundational data	CDC acquires sources from 60 potential data sources and 1100 hospitals	Aug 2007: 357 real time data sources, 466 DoD and 863 VA healthcare facilities and 2 special data sources sending data to BioSense
9	2008	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to the early detection and quantification of possible bioterrorism events.	TBD	Increase by 10% over the previous year's volume the number of health interactions related to the early detection and quantification of possible bioterrorism events that are made available for analysis to local, state, federal public health agencies	TBD
10	2008	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of state and local Public Health Department's serviced in key jurisdictions	TBD	60% of State and local public health agencies in key jurisdictions have to access BioSense data	TBD
11	2008	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	TBD	CDC acquires sources from 100 potential data sources and 1100 hospitals	TBD
12	2008	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	TBD	No more than 2 hours from "Time of Visit" to "Viewable in BioSense application	TBD
13	2009	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to the early detection and quantification of possible bioterrorism events.	TBD	Increase by 10% over the previous year's volume the number of health interactions related to the early detection and quantification of possible bioterrorism events that are made available for analysis to local, state, federal public health agencies	TBD
14	2009	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of state and local Public Health Department's serviced in key jurisdictions	TBD	85% of State and local public health agencies in key jurisdictions have to access BioSense data	TBD
15	2009	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	TBD	CDC acquires sources from 200 potential data sources and 3200 hospitals	TBD
16	2009	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	TBD	No more than 2 hours from "Time of Visit" to "Viewable in BioSense application	TBD
17	2010	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to the early detection and quantification of possible bioterrorism events.	TBD	Increase by 10% over the previous year's volume the number of health interactions related to the early detection and quantification of possible bioterrorism events that are made available for analysis to local, state, federal public health agencies	TBD
18	2010	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of state and local Public Health Department's serviced in key jurisdictions	TBD	88% of State and local public health agencies in key jurisdictions have to access BioSense data	TBD
19	2010	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	TBD	CDC acquires sources from 50 potential data sources and	TBD
20	2010	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	TBD	No more than 2 hours from "Time of Visit" to "Viewable in BioSense application	TBD
21	2011	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to the early detection and quantification of possible bioterrorism events.	TBD	Increase by 10% over the previous year's volume the number of health interactions related to the early detection and quantification of possible bioterrorism events that are made available for analysis to local, state, federal public health agencies	TBD
22	2011	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of state and local Public Health Department's serviced in key jurisdictions	TBD	88% of State and local public health agencies in key jurisdictions have to access BioSense data	TBD
23	2011	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	TBD	CDC acquires sources from 18 potential data sources	TBD
24	2011	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	TBD	No more than 2 hours from "Time of Visit" to "Viewable in BioSense application	TBD
25	2012	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to the early detection and quantification of possible bioterrorism events.	TBD	Increase by 10% over the previous year's volume the number of health interactions related to the early detection and quantification of possible bioterrorism events that are made available for analysis to local, state, federal public health agencies	TBD
26	2012	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of state and local Public Health Department's serviced in key jurisdictions	TBD	88% of State and local public health agencies in key jurisdictions have to access BioSense data	TBD
27	2012	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	TBD	CDC acquires sources from 22 potential data sources	TBD
28	2012	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	TBD	No more than 2 hours from "Time of Visit" to "Viewable in BioSense application	TBD
29	2013	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Mission and Business Results	Population Health Management and Consumer Safety	# of health interactions in key jurisdictions related to the early detection and quantification of possible bioterrorism events.	TBD	TBD
30	2013	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Customer Results	New Customers and Market Penetration	% of state and local Public Health Department's serviced in key jurisdictions	TBD	TBD
31	2013	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Technology	External Data Sharing	# of data sources	TBD	TBD
32	2013	S.O. 2.4 - Prepare for and respond to natural and man-made disasters	Processes and Activities	Cycle Time	Time required to update BioSense data	TBD	TBD

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.

CDC PHIN: BioSense

3. Is this investment identified in a completed (contains a target architecture) and approved segment architecture?

yes

3.a. If yes, provide the name of the segment architecture as provided in the agency’s most recent annual EA Assessment.

Public Health Information Network

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.

Row	Agency Component Name	Agency Component Description	Service Type	Component	Reused Component Name	Reused UPI	Internal or External Reuse?	Funding %
1	Standardized / Canned	Defines the set of capabilities that support the use of pre-conceived or pre-written reports.	Reporting	Standardized / Canned			No Reuse	10
2	Ad Hoc	Defines the set of capabilities that support the use of dynamic reports on an as needed basis.	Reporting	Ad Hoc			No Reuse	5
3	Mathematical	Defines the set of capabilities that support the formulation and mathematical analysis of probabilistic models for random phenomena and the development and investigation of methods and principles for statistical inference.	Analysis and Statistics	Mathematical			No Reuse	15
4	Modeling	Defines the set of capabilities that develop descriptions to adequately explain relevant data for the purpose of prediction, pattern detection, exploration or general organization of data.	Knowledge Discovery	Modeling			No Reuse	15
5	Data Mining	Defines the set of capabilities that provide for the efficient discovery of non-obvious, valuable patterns and relationships within a large collection of data.	Knowledge Discovery	Data Mining			No Reuse	30

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.

Row	SRM Component	>Service Area	Service Category	Service Standard	Service Specification (i.e., vendor and product name)
1	Standardized / Canned	Component Framework	Data Interchange	Data Exchange	Electronic Business using XML
2	Ad Hoc	Component Framework	Data Interchange	Data Exchange	Electronic Business using XML
3	Mathematical	Component Framework	Data Interchange	Data Exchange	Electronic Business using XML
4	Modeling	Component Framework	Data Interchange	Data Exchange	Electronic Business using XML
5	Data Mining	Component Framework	Data Interchange	Data Exchange	Electronic Business using XML
6	Standardized / Canned	Service Interface and Integration	Interoperability	Data Format / Classification	Health Level 7 (HL7)
7	Ad Hoc	Service Interface and Integration	Interoperability	Data Format / Classification	Health Level 7 (HL7)
8	Mathematical	Service Interface and Integration	Interoperability	Data Format / Classification	Health Level 7 (HL7)
9	Modeling	Service Interface and Integration	Interoperability	Data Format / Classification	Health Level 7 (HL7)
10	Data Mining	Service Interface and Integration	Interoperability	Data Format / Classification	Health Level 7 (HL7)
11	Standardized / Canned	Service Interface and Integration	Interoperability	Data Format / Classification	HITSP
12	Ad Hoc	Service Interface and Integration	Interoperability	Data Format / Classification	HITSP
13	Mathematical	Service Interface and Integration	Interoperability	Data Format / Classification	HITSP
14	Modeling	Service Interface and Integration	Interoperability	Data Format / Classification	HITSP
15	Data Mining	Service Interface and Integration	Interoperability	Data Format / Classification	HITSP
16	Standardized / Canned	Service Interface and Integration	Interoperability	Data Transformation	Informatica
17	Ad Hoc	Service Interface and Integration	Interoperability	Data Transformation	Informatica
18	Mathematical	Service Interface and Integration	Interoperability	Data Transformation	Informatica
19	Modeling	Service Interface and Integration	Interoperability	Data Transformation	Informatica
20	Data Mining	Service Interface and Integration	Interoperability	Data Transformation	Informatica
21	Standardized / Canned	Service Interface and Integration	Interoperability	Data Format / Classification	International Classification of Diseases
22	Ad Hoc	Service Interface and Integration	Interoperability	Data Format / Classification	International Classification of Diseases
23	Mathematical	Service Interface and Integration	Interoperability	Data Format / Classification	International Classification of Diseases
24	Modeling	Service Interface and Integration	Interoperability	Data Format / Classification	International Classification of Diseases
25	Data Mining	Service Interface and Integration	Interoperability	Data Format / Classification	International Classification of Diseases
26	Standardized / Canned	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes
27	Ad Hoc	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes
28	Mathematical	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes
29	Modeling	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes
30	Data Mining	Service Interface and Integration	Interoperability	Data Format / Classification	Logical Observation Identifier Names and Codes
31	Standardized / Canned	Service Platform and Infrastructure	Hardware / Infrastructure	Wide Area Network (WAN)	SONET, Bellsouth
32	Ad Hoc	Service Platform and Infrastructure	Hardware / Infrastructure	Wide Area Network (WAN)	SONET, Bellsouth
33	Mathematical	Service Platform and Infrastructure	Hardware / Infrastructure	Wide Area Network (WAN)	SONET, Bellsouth
34	Modeling	Service Platform and Infrastructure	Hardware / Infrastructure	Wide Area Network (WAN)	SONET, Bellsouth
35	Data Mining	Service Platform and Infrastructure	Hardware / Infrastructure	Wide Area Network (WAN)	SONET, Bellsouth
36	Standardized / Canned	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT)
37	Ad Hoc	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT)
38	Mathematical	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT)
39	Modeling	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT)
40	Data Mining	Service Interface and Integration	Interoperability	Data Format / Classification	Systematized Nomenclature of Medicine Clinical Terms (SNOMED CT)
41	Standardized / Canned	Service Access and Delivery	Service Transport	Supporting Network Services	T1
42	Ad Hoc	Service Access and Delivery	Service Transport	Supporting Network Services	T1
43	Mathematical	Service Access and Delivery	Service Transport	Supporting Network Services	T1
44	Modeling	Service Access and Delivery	Service Transport	Supporting Network Services	T1
45	Data Mining	Service Access and Delivery	Service Transport	Supporting Network Services	T1
46	Standardized / Canned	Service Access and Delivery	Service Transport	Supporting Network Services	T3
47	Ad Hoc	Service Access and Delivery	Service Transport	Supporting Network Services	T3
48	Mathematical	Service Access and Delivery	Service Transport	Supporting Network Services	T3
49	Modeling	Service Access and Delivery	Service Transport	Supporting Network Services	T3
50	Data Mining	Service Access and Delivery	Service Transport	Supporting Network Services	T3
51	Standardized / Canned	Component Framework	Security	Certificates / Digital Signatures	VeriSign
52	Ad Hoc	Component Framework	Security	Certificates / Digital Signatures	VeriSign
53	Mathematical	Component Framework	Security	Certificates / Digital Signatures	VeriSign
54	Modeling	Component Framework	Security	Certificates / Digital Signatures	VeriSign
55	Data Mining	Component Framework	Security	Certificates / Digital Signatures	VeriSign
56	Standardized / Canned	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0
57	Ad Hoc	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0
58	Mathematical	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0
59	Modeling	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0
60	Data Mining	Service Access and Delivery	Access Channels	Web Browser	Windows Internet Explorer 6.0

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.

This investment leverages: Federal Health Architecture (FHA)

1. Does the investment have a Risk Management Plan?

yes

1.a. If yes, what is the date of the plan?

2007-07-23

1.b. Has the Risk Management Plan been significantly changed since last year's submission to OMB?

yes

1.c. If yes, describe any significant changes:

BioSense underwent an Independent Verification and Validation (IV&V) assessment in order to ensure the chosen architecture and implementation approach is in alignment with industry best practices. This assessment began in May 2006 with the intent to do a thorough review of all aspects of the BioSense technical architecture, platform and operations. The study provided strengths and weaknesses as well recommendations to CDC on refining the vision, establishing goals, outcomes and performance metrics for BioSense. As a result of the IV&V, an updated risk management plan was implemented in September 2006.

3. Briefly describe how investment risks are reflected in the life cycle cost estimate and investment schedule:

The BioSense scope and budget planning using a work breakdown structure technique that decomposes each work element into its fundamental components. Each component is evaluated based on a risk assessment and the appropriate level of funding is assigned based on the work element's risk value. The budget for each element is derived based on the most likely scenario that has been risk adjusted. The total of each element comprises the full budget for BioSense. BioSense reviews its risks on a weekly basis and evaluates any potential changes to the budget plan.

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%?

no

3. Has the investment re-baselined during the past fiscal year?

no