From: Subject: Date: To: CBPFOIA@cbp.dhs.gov Final Disposition, Request CBP-2017-041474 April 30, 2018 at 12:20 PM foia@americanoversight.org April 30, 2018 CBP-2017-044174 Austin Evers American Oversight Washington, DC Dear Mr. Evers: As agreed to in American Oversight v. U.S. Department of Homeland Security, et at., Case No. 1:17-cv-01187-RDM (D.C.), this is the final response to your Freedom of Information Act (FOIA) request to U.S. Customs and Border Protection (CBP), on behalf of American Oversight, in which you are seeking records pertaining to the decision to initiate a reassessment of the SBInet program. A search of CBP databases produced 762 pages of records responsive to your request. CBP has determined that 4 pages will be released in their entirety, 22 pages will be withheld in full pursuant to Title 5 U.S.C. § 552 (b)(5), and 733 pages of the records are partially releasable, pursuant to Title 5 U.S.C. § 552 (b)(3),(b)(4),(b)(5), (b)(6), (b)(7)(C), and (b)(7)(E). Uploaded to your FOIAonline account and attached to this email are 737 pages with certain information withheld as described below: FOIA Exemption (b)(3) pertains to information exempted from disclosure by statute (other than Section 552b of this title) provided that such statute (A) requires that the matters be withheld from the public in such a manner as to leave no discretion on the issue, or (B) establishes particular criteria for withholding or refers to particular types of matters to be withheld. As it pertains to this request, specifically Statute 41 U.S.C. § 2102; Contractor bid or proposal information and source selection information. FOIA Exemption (b)(4) exempts from disclosure trade secrets and commercial or financial information obtained from a person that is privileged or confidential. FOIA Exemption (b)(5) exempts from disclosure information considered to be pre-decisional and deliberative, information that is attorney-client privilege, and inter-agency or intra-agency memoranda or letters which would not be available by law to a party other than an agency in litigation with the agency. FOIA Exemption (b)(6) exempts from disclosure personnel or medical files and similar files the release of which would cause a clearly unwarranted invasion of personal privacy. This requires a balancing of the public’s right to disclosure against the individual’s right privacy. The types of documents and/or information that we have withheld may consist of birth certificates, naturalization certificates, driver license, social security numbers, home addresses, dates of birth, or various other documents and/or information belonging to a third party that are considered personal. The privacy interests of the individuals in the records you have requested outweigh any minimal public interest in disclosure of the information. Any private interest you may have in that information does not factor into the aforementioned balancing test. FOIA Exemption (b)(7)(C) protects records or information compiled for law enforcement purposes that could reasonably be expected to constitute an unwarranted invasion of personal privacy. This exemption takes particular note of the strong interests of individuals, whether they are suspects, witnesses, or investigators, in not being unwarrantably associated with alleged criminal activity. That interest extends to persons who are not only the subjects of the investigation, but those who may have their privacy invaded by having their identities and information about them revealed in connection with an investigation. Based upon the traditional recognition of strong privacy interest in law enforcement records, categorical withholding of information that identifies third parties in law enforcement records is ordinarily appropriate. FOIA Exemption (b)(7)(E) protects records compiled for law enforcement purposes, the release of which would disclose techniques and/or procedures for law enforcement investigations or prosecutions, or would disclose guidelines for law enforcement investigations or prosecutions if such disclosure could reasonably be expected to risk circumvention of the law. CBP has determined that disclosure could reasonably be expected to risk circumvention of the law. Additionally, as per settlement negotiations you will be provided a link to the reading room for the Transition Team documents, items three (3) and five (5) of your request. We foresee the documents being uploaded within the next two weeks and will provide you with the link via email. This completes CBP’s response to your request. If you have questions or concerns regarding this first interim response, you may contact Assistant United States Attorney W. Mark Nebeker at (202) 252-2536 or mark.nebeker@usdoj.gov. Please notate file number CBP-2017-041474 on any future correspondence to CBP related to this request. Sincerely, Jodi Drengson FOIA Analyst, FOIA Division Office of Diversity and Civil Rights Records were released to the public as a result of this request. You may retrieve these records immediately using the following link: View Records.Over the next 2 hours, these records are also being added to FOIAonline's search pages, further enabling you to retrieve these documents associated with your FOIA request at any time. retrieve these documents associated with your FOIA request at any time. From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) Re: SBI Update Briefings for House/Senate Homeland Friday, January 29, 2010 3:04:44 PM Looks like House Homeland will be scheduled for Friday from 9:30-11:00. - (b)(6);(b)(7)(C) will that work for you? 1111 (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) To: Cc: Sen Subject: RE: SBI Update Briefings for House/Senate Homeland (b)(6);(b)(7)(C) I am available to back up the SBInet representative by speaking to the operational requirements and impacts.   From: (b)(6);(b)(7)(C) Sent: Thursday, January 28, 2010 9:59 AM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: SBI Update Briefings for House/Senate Homeland Good Morning Gentlemen, House and Senate Homeland staff have requested that CBP come up and provide briefings next week to update them on the latest with SBInet. I anticipate the briefings will primarily focus on the latest delays to the timeline and the Secretary’s call for a “review” of the program, however they will likely also ask questions about BP’s early “familiarization” with the system (i.e., how it will work, whether there will be a mechanism to provide feedback on the system or if it will be strictly informal), operational testing, and possibly other issues that BP would want to chime in on. As of right now, we are looking at 10:30am-12:00pm next Tuesday, February 2, to meet with Senate Homeland. I am trying to arrange the House Homeland briefing for either Tuesday afternoon or possibly sometime on Thursday. Would you or someone from your group be available to participate in these briefings next week? -- Thank you! (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) U.S. Customs and Border Protection Office of Congressional Affairs (b)(6);(b)(7)(C) BW7 FOIA CBP 000001 DHS-17-0046-C-000001 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) Re: STATUS SLIDES Friday, January 29, 2010 6:22:20 PM Sorry. I forgot to include it. • will send it to you shortly. (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Sent: Fri Jan 29 15:47:59 2010 Subject: RE: STATUS SLIDES • —   I really need whatever we have as the latest schedule chart (Gantt chart) for (b) (7)(E) please.   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection -   From: (b)(6);(b)(7)(C) Sent: Friday, January 29, 2010 2:02 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: STATUS SLIDES - - :  Here are the status slides you asked for, plus additional slides for my bi-weekly update.  One note on the OIC slide.  There is some minor disagreement over the date that construction will actually be completed.  I’ve given you two slides showing the differing opinions.  I personally think the Oct date is (b)(6);(b)(7)(C) more realistic, is concerned that is we say Oct we will need to update congress as this is a change.       I’m headed out to a meeting with MTCSC Corporation.  I do not plan on coming back to the office this afternoon, but will be available by cell phone if you have any questions on this package.    Thanks       (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the BW7 FOIA CBP 000002 DHS-17-0046-C-000002 contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. BW7 FOIA CBP 000003 DHS-17-0046-C-000003 ------------(b)(6);(b)(7)(C) From: Sent: To: Subject: (b)(6);(b)(7)(C) on behalf of (b)(6);(b)(7)(C) Thursday, January 14, 2010 1:41 PM (b)(6);(b)(7)(C) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000004 DHS-17-0046-C-000004 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) RE: Wednesday, January 13, 2010 4:25:27 PM Yes Sir, will do.   v/r   (b)(6);(b)(7)(C) - Acting Chief U.S. Border Patrol (b)(6);(b)(7)(C) 1300 Pennsylvania Ave, Washington, DC 20229 (b)(6);(b)(7)(C) WARNING: This document is LAW ENFORCEMENT SENSITIVE and is designated  FOR OFFICIAL USE ONLY (FOUO). It contains information that may be exempt from public release under the Freedom of Information Act (5 USC 552). This document is to be controlled, handled, transmitted, distributed, and disposed of in accordance with Department of Homeland  Security policy relating to FOUO information, and is not to be  released to the public or personnel who do not have a valid "need to know" without prior approval from the Acting Chief, US Border Patrol (202) 344-3159. From: (b)(6);(b)(7)(C) Sent: Wednesday, January 13, 2010 4:18 PM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject:   (b)(6);(b)(7)(C)   In one of the breaks that we had yesterday in dealing with all the activities surrounding the 12/25 incident, Haiti, and another hot button item, the Secretary and I had a chance to very briefly discuss SBInet, the 60 Minutes piece, and path forward. She is of the same opinion as we are: the 60 Minutes piece was a lot less negative than what we had anticipated and she also thought that Boeing took the brunt of the piece. She also stated that the purpose of the memo that went out with her directing the “review” of SBInet was in anticipation of a more negative piece.  But basically she agrees with the options paper that we put forth before the holidays. She did not specifically identify option 2 as her preference but as she lined out her recollection of the memo and it fits right along with Option 2. She noted that she had “spoken to Congress” about this and that they were not surprised and supportive. I did not ask how this communication was done, formally or informally. Given the timeline from when we sent the paper forth I would guess that it was a verbal and informal.   (b)(6);(b)(7)(C) ,   This being the case we need to look at redesigning our thought process as to technology capability requirements (i.e, detection, deterrence, identification, classify, etc.. or mix of) that we would be looking to get resourced under this option. Exercising this option or something similar to it would mean that we would be weighting our resource procurement efforts and requirements towards “commodity purchases” of technology versus “system development”. Not that we would stop the systems development completely (block one). I would ask that Border Patrol revisit our technology requirements against this new information.   - BW7 FOIA CBP 000005 DHS-17-0046-C-000005 Keep me apprised. BW7 FOIA CBP 000006 DHS-17-OO46-C-000006 From: To: Subject: Date: (b)(6);(b)(7)(C) Assessment talking points Sunday, January 31, 2010 10:22:02 PM This should be a solid start for assessment talking points everyone can use for consistency. (b)(6);(b)(7)(C) From: To: (b)(6);(b)(7)(C) Sent: Sun Jan 31 21:36:17 2010 Subject: Why was the department wide assessment requested? This fall, due to ongoing concerns about SBInet, the Secretary directed the Acting Commissioner of Customs and Border Protection to evaluate its implementation. As his analysis uncovered unacceptable delays, a department-wide reassessment was ordered to consider options that may more efficiently, effectively and economically meet border security needs. Delays are caused by CBPs commitment to review the quality and effectiveness of the system. As previously reported, the program faced a number of technical issues identified with the system resulting from the testing performed over the last year. Although none of the issues were considered to be "show-stoppers," CBP did feel it prudent to address each of them very deliberatively and comprehensively. As a result, time was invested to do full-engineering analysis, design corrections, and fully test the corrections. Most of this is complete, but it has taken time. (b) (7)(E) The detailed test planning will need to accommodate the system corrections, which is a comprehensive and time-consuming effort. CBP chose specifically NOT to take excessive short cuts, which might have made the nearterm schedule appear better but would likely have created new delays in the future. To mitigate the delays, CBP is now working with Boeing to use the system "as is" over the next few months, even before extensive testing is performed. In that way, CBP can get most of the operational benefit if the schedule had been maintained, while still protecting the government equities to ensure the government doesnt fully accept the system until it is ready. How long with the assessment last? DHS is just beginning to set up the parameters of the assessment. However, it is expected that there will be both a near term and long term piece to the assessment. The near term assessment will be based on the particular needs and urgency of border security and whether SBInet can fill those requirements. A longer term assessment will be based on what DHS learns from the testing of SBInet initial deployments. What will be the outcome of the assessment? The assessment will focus immediately on whether or not SBInet can be done. This program BW7 FOIA CBP 000007 DHS-17-0046-C-000007 has experienced a tremendous amount of delays. The assessment will determine if the government is prepared to accept any more delays. And given an understanding or expectation of the availability of this technology, what decisions need to be made to deal with the urgency of technology in support of border security. Does the reassessment put the program at risk? After the reassessment, DHS will make a future acquisition decision on the program, which could include a recompete of the contract, extending the contract or going down an entirely different path. Who will be involved in the assessment? The assessment will include all parts of DHS including the CBP Secure Border Initiative officee, the Science and Technology Directorate, the Chief Acquisition Officer's office, the CBP chief information officer and others. What does the assessment mean for SBInet current operations? -- SBInet will maintain the current plan which is to deploy the first two production systems of (b) (7)(E) SBInet. Construction of the initial deployments of SBInet in will continue. The first deployment, (b) (7)(E) is built and the second deployment of SBInet, (b) (7)(E) is beginning construction now. (b) (7)(E) is built and is currently undergoing individual component testing in preparation for systems acceptance testing. Boeing will not start any new work on the program. - In the meantime while DHS reevaluates SBInet, CBP is working with Boeing to let border patrol agents begin using the deployed technology. BW7 FOIA CBP 000008 DHS-17-0046-C-000008 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) FW: openings (DOT&E help) Thursday, January 07, 2010 3:23:35 PM (b)(6);(b)(7)(C) , - I had some initial discussions with (b)(6);(b)(7)(C) from IDA.  He supports DoD DOT&E.  They are willing to support us and/or Border Patrol in providing some assistance (consulting services) re: Operational Test Planning and Execution.  I would like to provide IDA an SBInet 101 and SBInet OT&E 101 brief in the nearterm. After that brief, I believe we can come to some agreement as to what level of support IDA can provide.  Pls see the email below and let me know if any of those windows work. - Thanks, (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. -----Original Message----From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:55 PM To: (b)(6);(b)(7)(C) Subject: openings (b)(6);(b)(7)(C) ,    The openings on my schedule next week are: Tuesday, after 1 Wednesday, after noon Friday, any time after 10    I haven't had a chance to track down someone who might be familiar with the relevant FCS components.  I'll try to find someone Tuesday who know a bit about it and is available whatever date/time you go for.  (b)(6);(b)(7)(C)         (b)(6);(b)(7)(C) Operational Evaluation Division Institute for Defense Analyses 4850 Mark Center Drive Alexandria, VA 22311-1882 Voice: (b)(6);(b)(7)(C) Fax: (b)(6);(b)(7)(C) Cell: BW7 FOIA CBP 000009 DHS-17-0046-C-000009 From: To: Cc: Subject: Date: Attachments: Importance: - (b)(6);(b)(7)(C) SBInet: --- FW: CBP Status of ARRA Projects due COB Thursday, 01/08/10 (for Week 46) Friday, January 08, 2010 3:37:36 PM CBP Status of Recovery Projects- Week 46 - DRAFT .xls High , (b)(6);(b)(7)(C) SBInet’s submission for Week 46 attached (changed cell highlighted in yellow). Regards, • (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Management and Program Analyst, Program Information Team Secure Border Initiative (SBI) U.S. Customs and Border Protection (CBP) U.S. Department of Homeland Security (DHS) (b)(6);(b)(7)(C) Email Address: Office: (b)(6);(b)(7)(C) Arlington, VA 22202 - From: (b)(6);(b)(7)(C) On Behalf Of (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:38 PM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject: CBP Status of ARRA Projects due COB Thursday, 01/08/10 (for Week 46) Importance: High Good morning, ARRA Program Managers and key contacts   Please update the attached Excel file for week 46 (using week 45’s final report, now a draft for week 46), and submit your input for the “Status of ARRA Projects” to (b)(6);(b)(7)(C) not later than COB Thursday, 01/08.   As always: Please highlight in yellow any cells with changes.  • Please use this exact version of the report. • Please return this report in an email separate from the Weekly Update report (kindly do not submit both in one email). • As a reminder, please include all projects that have already been obligated, as well as anything we expect to obligate. If any projects originally scheduled have been pushed back, please note that and continue to include them on the spreadsheet. If you have any questions, please contact us at (b)(6);(b)(7)(C) Thank you. BW7 FOIA CBP 000010 DHS-17-0046-C-000010 *************************************************************************************************************************************** For the latest information on CBP ARRA efforts, please visit the CBP ARRA Working Group KMS site at: (b)(6);(b)(7)(C) *************************************************************************************************************************************** BW7 FOIA CBP 000011 DHS-17-0046-C-000011 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/08/10 Week 46 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) DRAFT Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b)(6);(b)(7)(c) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b)(6);(b) (7)(c) (b)(6);(b) (7)(c) (b)(6);(b) (7)(c) (b)(6);(b) (7)(c) (b)(6);(b)(7)(c) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b)(6);(b)(7)(c) BW7 FOIA CBP 000012 DHS-17-0046-C-000012 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/08/10 Week 46 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) DRAFT Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b)(6);(b)(7)(c) NON-RESPONSIVE (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7)(E) (b)(6);(b)(7)(c) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b)(6);(b)(7) (c) (b)(6);(b) (7)(c) BW7 FOIA CBP 000013 DHS-17-0046-C-000013 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) (b) (7)(E) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/08/10 Week 46 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) DRAFT Outlays TAFS # Awardee Awardee Address (b)(6);(b)(7) (c) Contract Number Contract Type Competition Type NON-RESPONSIVE (b)(6);(b) (7)(c) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b)(6); (b)(7) (c) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b)(6);(b)(7)(c) BW7 FOIA CBP 000014 DHS-17-0046-C-000014 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/08/10 Week 46 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) DRAFT Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b)(6);(b) (7)(c) NON-RESPONSIVE (b) (7) (E) (b) (6); (b) (b)(7) (6); (c) (b) (7) (c) Yes. The "Anticipated Obligation Date" provided is the last date on which we anticipate obligating funds for this project, which will cover CBP Tactical Communications Modernization efforts in the (b) (7)(E) (b) (7)(E) There will be several contracts let over the course of the project, and the schedule for those contracts is contingent upon a decision pending on the Tactical Communications Acquisition Strategy. The data provided in this sheet for obligations incurred to date concern individual task orders supporting the ongoing modernization efforts in (b) (7)(E) Tactical Communications - Will modernize legacy land mobile radio systems used by CBP agents and officers to provide (b) (7)(E) (b) (7)(E) equipment with (b) (7)(E) encryption. In addition, the modernization will provide for (b) (7)(E) (b) (7)(E) which directly supports SBInet's Common (b) (7)(E) Operating Picture. (b) (7) (E) (b)(6);(b)(7)(c) (b)(6);(b)(7)(c) (b) (6); (b) (7) (b)(6); (c) (b)(7) (c) Eyaktek: 22980 Indian Creek Drive, Suite 400, Dulles, VA 20166 9/10/10 5/11/2009 5/27/09 7/29/09 (b)(3) Wrightline: 160 Gold Star Blvd, Worcester, MA 01606 70-0534 2009 \ 2010 EyakTek Wrightline Commdex Commdex: 1531 South Edgewood Road, Suite C, Baltimore, MD 21227 HSPB100823360 GS-29F-0100G HSPB1008P22970 Eyaktek tasks directed 8a, Native American owned. The Wrightline order Firm fixed price replaced pre-existing contract equipment. BW7 FOIA CBP 000015 DHS-17-0046-C-000015 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) Tactical Communications -(b) (7)(E) modernization services and comms Direct award must be approved by the S2 equipment (b) (7) (b) (7)(E) Tactical Communications (E) (b) Will be awarded in an 8a modernization open market equipment and reserve expenses (7) competition is transfer out rather than a (E) This contract award; TacCom transferred -- (b)(3) o the ENTS Training branch to support TACCOM-related training travel and services. It willl be obligated and expended on an asTactical Communications - Training consumed basis. as of 01/08/10 Week 46 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) DRAFT 10/31/09 (b)(3) 12/31/09 8/29/09 (b Just awarded. ) Tactical Communications (b Will be awarded in open competition services and civil equipment (7 )) Tactical Communications - (b) (7)(E) (b) (7 Will be awarded in open competition services and civil equipment (E (7) ) )TACCOM (E) (E TACCOM Expenditures - not disbursed ) TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b)(3) 70-0534 2009 \ 2010 Motorola 1303 East Algonquin Road Schaumburg, IL 60196 TBD Firm fixed price contract Name Brand 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price contract 8a 70-0534 2009 \ 2010 N/A - funded government travel N/A N/A 70-0534 2009 \ 2010 American Tower 116 Huntington Avenue, 11th Floor, Boston, MA, 02116 1009P28032 Firm fixed price contract Name Brand 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price contract Open 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price contract Open (estimated) (b)(3) 8/29/2009 Tactical Communications (b) (7)(E) structural analysis for towers Outlays (b)(3) 9/21/2009 (b) (7)(E) TACCOM Net Outlays 6/30/10 (b)(3) stimated) 6/30/10 (b)(3) stimated) N/A N/A (b)(3) $0 (b)(3) NON-RESPONSIVE (b)(6);(b)(7)(c) BW7 FOIA CBP 000016 DHS-17-0046-C-000016 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/08/10 Week 46 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) DRAFT Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b)(6);(b)(7) (c) (b) (7) (E) BW7 FOIA CBP 000017 DHS-17-0046-C-000017 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) SBInet Long Lead Components & Equipment Purchases Block 1 SAT is now scheduled to begin mid- 2010 (Jun or July). A decision on procurement of the parts for the next deployment would be made around Aug 2010. Alternate use of these funds due to the slips in SAT is being actively investigated. Expect a decision to be made in early Jan 2010 SBInet Existing Technology(b) (7)(E) SBInet Anticipated Obligation Date is June 2010. The (b) (7)(E) RFP was released on 28 December 2009, with responses due by 29 January 2010. Planning a kick-off meeting with the SBInet Acquisition team to develop a contract vehicle strategy/plan of action and milestones to obligate funding by June 30, 2010. (b) (7)(E) as of 01/08/10 Week 46 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) 4/15/10 6/30/10 6/30/10 DRAFT TBD (b)(3) TBD (b)(3) TBD (b)(3) (b)(3) SBInet Outlays TAFS # 0 0 70-0536 2009 \ 2010 70-0536 2009 \ 2010 70-0536 2009 \ 2010 Awardee TBD TBD TBD Awardee Address TBD TBD TBD Contract Number Contract Type Competition Type TBD Task Order issued on existing competitively awarded IDIQ Firm Fixed Price contract Contract. TBD TBD but most likely Firm Fixed Price Competitively contract awarded contract. TBD TBD but most likely Firm Fixed Price Competitively contract awarded contract. $0 SBInet Expenditures - not disbursed $0 SBInet Net Outlays $0 ` BW7 FOIA CBP 000018 DHS-17-0046-C-000018 From: To: (b)(6);(b)(7)(C) Cc: Subject: Date: Attachments: Importance: new PIN: CBP ARRA Weekly Update as of 12/31/09 (week 45) DRAFT - for your review Monday, January 04, 2010 1:02:41 PM Weekly Update Report - Week 45_CBP DRAFT.xls High Sorry for the mix-up.  Here is the new phone info for our 1:00 call.  The PIN has changed.    Title Location CBP ARRA weekly conference call  (b) (7)(E) Start Time 1/4/2010 1:00 PM  End Time 1/4/2010 1:30 PM  - (b)(6);(b)(7)(C) [PIN expires 3/30/10]    BW7 FOIA CBP 000019 DHS-17-0046-C-000019 CBP ARRA Weekly Update as of 12/31/2009 (Week 45) D R A F T Major Completed Actions Issues to Discuss on Tuesday AM DHS Conference Call Major Planned Actions NON-RESPONSIVE Tactical Communications: No new actions taken to report this week. Tactical Communications: Complete procurement actions for (b) (7)(E) nd initiate actions for near-term competitions. Tactical Communications: Please provide update on the status of S2 approval on sole source award. NON-RESPONSIVE SBInet: (b) (7)(E) The RFP was released on 12/28. - SBInet: Block 1 System Acceptance Test (SAT) is now set to commence mid-2010 (June or July). The formal test write up of SQT Phase 2 is expected as early as 01/15/2010. A plan for alternate use of the (b)(3) for SBInet Block 1 components is being actively investigated. A decision on this is expected in Jan 2010. SBI: Nothing to report. An Industry Day for the MSC is planned for the week of 1/4/2010. Responses from the RFP are currently due 1/29/2010. (b) (7)(E) BW7 FOIA CBP 000020 DHS-17-0046-C-000020 CBP ARRA Weekly Update as of 12/31/2009 (Week 45) Obligations Outlays Expenditures DRAFT Total Budget % Obligated NON-RESPONSIVE (b)(3) TacCom SBI 1.19% NON-RESPONSIVE $0.00 $0.00 $0.00 (b)(3) 0.00% (b)(3) Total CBP NON-RESPONSIVE (b)(3) BW7 FOIA CBP 000021 DHS-17-0046-C-000021 CBP ARRA Weekly Update as of 12/31/2009 (Week 45) back pocket info for CBP ARRA team Obligations Outlays NON-RESPONSIVE Total Budget % Obligated (b)(3) 9438 TacCom 1.19% NON-RESPONSIVE $0.00 9433 SBI Total (b)(3) $0.00 0.00% (b)(3) NON-RESPONSIVE BW7 FOIA CBP 000022 DHS-17-0046-C-000022 From: To: (b)(6);(b)(7)(C) Cc: Subject: Date: Attachments: Importance: CBP ARRA Weekly Update as of 1/8/2010 (week 46) DRAFT - for your review Monday, January 11, 2010 11:17:32 AM Weekly Update Report - Week 46_CBP DRAFT 2.xls High Good morning - Attached is the revised consolidated draft ARRA Weekly Report based upon your input.  Comments are in red bold.   All programs - please review and be prepared to discuss at today’s 1:00 PM call.   Below are the call details: Call Title:         CBP ARRA weekly conference call Date:                weekly on Mondays Time:               1:00-1:30 pm (30 minutes)  Phone #:          ((b)(6);(b)(7)(C) Pin #:               (b)(6);(b)(7)(C)   Thanks! - (b)(6);(b)(7)(C)   BW7 FOIA CBP 000023 DHS-17-0046-C-000023 CBP ARRA Weekly Update as of 01/08/2010 (Week 46) DRAFT Major Completed Actions Issues to Discuss on Tuesday AM DHS Conference Call Major Planned Actions NON-RESPONSIVE (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (E) Tactical Communications: Tactical Communications: TacCom Expenditures decreased significantly this week Complete procurement actions for (b) (7)(E)nd initiate actions for near-term competitions. due to a decision to swap out ARRA for non-ARRA funds on one contract due to the vendor's noncompliance with ARRA reporting requirements. Suggest change to Nothing new to report, as changes to Expenditures are not reflected in SAP system as of this morning. (b) (7) (E) (b) (7) (E) Tactical Communications: Please provide update on the status of S2 approval on sole source award. NON-RESPONSIVE SBInet: The Industry Day for the RFP took place on 1/8/2010. (b) (7)(E) SBInet: (1) Block 1 System Acceptance Test (SAT) is now set to commence mid-2010 (June or July). The formal test write up of SQT Phase 2 is expected as early as 1/15/2010. A plan for alternate use of the (b)(3) or SBInet Block 1 components is being actively investigated. A decision on this is expected in January 2010. (2) Responses from th SBI: Nothing to report. (b) (7)(E) (b) (7) (E) RFP are currently due 1/29/2010. BW7 FOIA CBP 000024 DHS-17-0046-C-000024 CBP ARRA Weekly Update as of 01/08/2010 (Week 46) Obligations Outlays Expenditures NON-RESPONSIVE DRAFT Total Budget % Obligated (b)(3) TacCom 1.19% NON-RESPONSIVE SBI $0.00 (b)(3) Total CBP NON-RESPONSIVE $0.00 $0.00 (b)(3) 0.00% 46.83% (b)(3) BW7 FOIA CBP 000025 DHS-17-0046-C-000025 CBP ARRA Weekly Update as of 01/08/2010 (Week 46) back pocket info for CBP ARRA team Obligations Outlays Total Budget % Obligated NON-RESPONSIVE (b)(3) 9438 TacCom (b)(3) 1.19% NON-RESPONSIVE $0.00 9433 SBI Total $ $0.00 (b)(3) (b)(3) 0.00% 46.83% NON-RESPONSIVE BW7 FOIA CBP 000026 DHS-17-0046-C-000026 From: To: Cc: Subject: Date: Attachments: (b)(6);(b)(7)(C) SBInet Agenda for Today at 2PM Room 4123 Friday, January 29, 2010 1:55:50 PM SBInet Agenda 01292010 (2).doc <> See attached! BW7 FOIA CBP 000027 DHS-17-0046-C-000027 SBInet I. Introductions II. Purpose of the Meeting 1. Review of Near Term Plan (b) (7)(E) - completion? a. b. Make ARRA funds decision 2. Review of Long Term Plan a. Strategy for 3. Establish Stakeholders a. Level of Stakeholders going forward b. Communications structure c. Centralized POCs for each area of review III. Goals 1. Reach a decision on use of Recovery Act funds 2. Establish timeframes on report-backs 3. Establish near-term assignments IV. Tasks 1. Establish list of specific questions that need to be answered 2. CFO complete list of accounting of SBInet funds 3. CPO provide a report on status of all contracts/ task orders (both operational and support) 4. Schedule regular meetings for update and review BW7 FOIA CBP 000028 DHS-17-0046-C-000028 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: - RE: SAVER support for Border Patrol Friday, January 22, 2010 12:43:51 PM (b)(6);(b)(7)(C) As follow-up to our discussions yesterday, (b)(6);(b)(7)(C) is the System Assessment and Validation for Emergency Responders (SAVER) PM who works for me. SAVER performs objective assessments and validations on commercial equipment and systems. The program will provide the assessment results along with other relevant equipment information to you in an operationally useful form that you need. SAVER performs the assessments using your operators with their weighted criteria. Additionally, a first step that often takes place is a market survey and report based on user needs. Below are technical agents that we have are using, but we add other agents if our current agent capabilities don’t cover the (b)(6);(b)(7)(C) equipment that you need assessed. is ready to support you if you would like to give him a call. We already have funding in place, so that will not be an issue. We can get moving quickly. Thanks (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) SAVER Program Manager - - (Office):   (b)(6);(b)(7)(C) (Mobile):   (b)(6);(b)(7)(C)   Ce ter for Domestic Preparedness (CDP) Na ional Urban Security Technology Laboratory (NUSTL) Sci nce Applications International Corporation (SAIC) Sp ce and Naval Warfare (SPAWAR) Systems Center, Atlantic Te hnical Support Working Group (TSWG) Te as A&M Engineering / The Texas A&M University System Th Naval Surface Warfare Center Dahlgren Division Th Nevada Test Site Operated by National Security Technologies, LLC, for the Department o Energy U. . Army Natick Soldier Research Development and Engineering Center (NSRDEC) (b)(6);(b)(7)(C) Director, DHS Test and Evaluation and Standards Division Department of Homeland Security (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Friday, January 22, 2010 6:53 AM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: RE: SAVER support for Border Patrol Importance: High 1111 (b)(6);(b)(7)(C) - r his Certainly!! We are now in the planning stage for the FY2010 project list. Have Chief representative give me a call or e-mail with the list of products he wants assessed and we will put them (b)(6);(b)(7)(C) BW7 FOIA CBP 000029 DHS-17-0046-C-000029 - on the list. I have already done this with earlier request I got from CBP (they wanted (b) (7)(E) . By the way, if it’s we may already have the (b) (7)(E) category on the list and just need to focus the technical agent on the right products. (b)(6);(b)(7)(C) SAVER Program Manager (Office):    (b)(6);(b)(7)(C) (Mobile):   (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Thursday, January 21, 2010 10:43 PM To: (b)(6);(b)(7)(C) Subject: SAVER support for Border Patrol - Chief (b)(6);(b)(7)(C)from Border Patrol supporting SBInet has a requirement for several market surveys and possibly several assessments of commercially available products. Do you (b)(6);(b)(7)(C) think that you can support him? Thanks… (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) - Director, DHS Test and Evaluation and Standards Division Department of Homeland Security (b)(6);(b)(7)(C) BW7 FOIA CBP 000030 DHS-17-0046-C-000030 From: To: Cc: Subject: Date: Attachments: Importance: (b)(6);(b)(7)(C) CBP ARRA Weekly Update as of 1/8/2010 (week 46) DRAFT - for your review Monday, January 11, 2010 11:07:46 AM Weekly Update Report - Week 46_CBP DRAFT 2.xls High Good morning - Attached is the consolidated draft ARRA Weekly Report based upon your input.   All programs - please review and be prepared to discuss at today’s 1:00 PM call.   Below are the call details: Call Title:         CBP ARRA weekly conference call Date:                weekly on Mondays Time:               1:00-1:30 pm (30 minutes)  Phone #:          (b)(6);(b)(7)(C) Pin #:               (b)(6);(b)(7)(C)   Thanks! - (b)(6);(b)(7)(C)   BW7 FOIA CBP 000031 DHS-17-0046-C-000031 CBP ARRA Weekly Update as of 01/08/2010 (Week 46) DRAFT Major Completed Actions Issues to Discuss on Tuesday AM DHS Conference Call Major Planned Actions NON-RESPONSIVE (b) (7)(E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (E) Tactical Communications: No new actions taken to report this week. (b) (7) (E) Tactical Communications: Tactical Communications: Please provide update on the status of S2 approval on sole source award. (b) (7)(E) Complete procurement actions for and initiate actions for near-term competitions. (b) (7) (E) NON-RESPONSIVE SBInet: The released on 12/28/2009. (b) (7)(E) ) RFP was - SBInet: (1) Block 1 System Acceptance Test (SAT) is now set to commence mid-2010 (June or July). The formal test write up of SQT Phase 2 is expected as early as 1/15/2010. A plan for alternate use of the (b)(3) for SBInet Block 1 components is being actively investigated. A decision on this is expected in January 2010. SBI: Nothing to report. (b) (7)(E) (2) An Industry Day for the s planned for the week of 1/4/2010. Responses from (b) (7)(E) the RFP are currently due 1/29/2010. (b) (7) (E) (b) (7) (E) BW7 FOIA CBP 000032 DHS-17-0046-C-000032 CBP ARRA Weekly Update as of 01/07/2010 (Week 46) Obligations Outlays Expenditures DRAFT Total Budget % Obligated NON-RESPONSIVE (b)(3) 1.19% NON-RESPONSIVE SBI $0.00 $0.00 NON-RESPONSIVE $0.00 (b)(3) Total CBP (b)(3) 0.00% 46.64% (b)(3) BW7 FOIA CBP 000033 DHS-17-0046-C-000033 CBP ARRA Weekly Update as of 12/31/2009 (Week 45) back pocket info for CBP ARRA team Obligations Outlays Total Budget % Obligated NON-RESPONSIVE (b)(3) 9438 TacCom 1.19% NON-RESPONSIVE 9433 SBI $0.00 $0.00 (b)(3) Obligations Outlays Total (b)(3) 0.00% 46.64% Total Budget % Obligated NON-RESPONSIVE IAA USACE IAA GSA IAA Subtotal CBP LPOE non-IAA (b)(3) - $ (b)(3) BW7 FOIA CBP 000034 DHS-17-0046-C-000034 From: To: Subject: Date: Attachments: Importance: (b)(6);(b)(7)(C) DCMA SBInet Dec MER Friday, January 08, 2010 6:49:15 PM DCMA MER Dec 09.docx High Attached is the subject report, please feel free to contact me should you have unanswered questions.   (b)(6);(b)(7)(C) Program Integrator SBInet Program DCMA Huntsville  (b)(6);(b)(7)(C)   "It's the soldier who gives us democracy. It's the soldier who protects us. It's the soldier, not the reporter, who has given us Freedom of Press. It's the soldier, not the poet, who has given us Freedom of Speech. It's the soldier, not the campus organizer, who has given us the Freedom to Demonstrate. It's the soldier who salutes the flag, who serves beneath the flag, and whose coffin is draped by the flag that allows the protester to burn the flag "-- Unknown      NOTICE: The Contracting Officer is the sole individual that is authorized to make changes to the contract. The contents of this email are not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes.   BW7 FOIA CBP 000035 DHS-17-0046-C-000035 01/08/2010 T O: (b)(6);(b)(7)(c) Executive Program Director, SBInet Secure Border Initiative Program Office Department of Homeland Security and US Customs and Border Protection Washington, DC FROM: (b)(6);(b)(7)(c) Program Integrator SBInet Program DCMA Huntsville (b)(6);(b)(7)(c) SUB [DCMA Monthly Executive Report- December 2009] CONTRACT INFORMATION: 1. Prime Contract: HSB1006D01353 2. Prime Contractor: Boeing - Integrated Defense Systems 3. Work Scope: This contract is broken into individual Task Orders based on the various sectors and type of work to be performed. 4. Program Period of Performance: Period of performance currently thru September 2010 with two one year options remaining. Program Status 1. EVMS – DCMA has yet to close any additional EVM CARs due the fact that Boeing has either not been able to meet the intent of the subject CARs or to meet the required criteria as stated in each CAR. DCMA and Boeing have segregated the EVM CARs into three groups to help facilitate their closure. (b) (7)(E) (b) (7)(E) DCMA is in the process of finalizing their 2010 EVMS for the (b) (7)(E) (b) (7)(E) facility. DCMA hopes that this will be adopted by (b) (7)(E) and performed jointly in a more teaming effort. 2010 (b) (7)(E) (b) (7)(E) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000036 DHS-17-0046-C-000036 2. Engineering – In DCMA’s assessment, the modification of a COTs item obviously cause one to question whether or not it remains an actual COTs item in name only. One would expect the vender to show specifically how it is readily available for verification purposes. _,,,.. 3. Quality Assurance – 94% of the(b) (7)(E) Tower site GMIPs are complete and 91% of the C2 facility GMIPs are complete. See QA report below for list of those outstanding. I (b) (7)(E) DCMA (b) (7)(E) has been turned on through an LOD from DCMA Huntsville to support the (b) (7)(E) eployment on NBP. Quality Assurance – Software - DCMA software quality foresees Boeing should implement a process for Configuration Management control on the firmware and test tools for each item within the SBInet Program. DCMA is anticipating that Boeing (Huntsville) will be updating the (b) (7)(E) Corrective Action Request (CARs) CAR Level I CAR Level II Open Closed New CAP QA-Hardware Huntsville 0 2 0 2 0 Yes QA-Hardware Tucson 5 3 0 3 0 Yes QA-Software Huntsville 0 1 0 1 0 Yes CARs QA-Software Mesa 0 1 0 1 0 N/A Engineering Huntsville 0 1 0 1 0 Yes Earned Value Total 0 5 18 26 17 17 1 9 0 0 Yes Notes Follow up on CARs 12 & 15 in Jan CAR rescinded upon further analysis Early 08 DOORs findings Working closure to EV CARs Chart 1 Earned Value Management Specialist DCMA EVM Specialist, Huntsville, AL (b)(6);(b)(7)(c) (b)(6);(b)(7)(c) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000037 DHS-17-0046-C-000037 Email: (b)(6);(b)(7)(c) STO The cumulative EVM data for the STO Task Order indicates that cost and schedule performance are both very close to plan and budget with relatively small negative cost and schedule variances. A positive cost variance is forecast at completion, although it is offset by $ (b)(3) in potential cost impacts that appear to be incurred already incurred or necessary. The level of accounting and charging issues, especially for Major Suppliers, is considered a significant EVMS system issue, although Boeing is now taking effective corrective action to correct them. The numerous technical issues and schedule problems would be expected to become evident in the EV data in the CPR. This is not shown in the cumulative cost data. However the current period does show the impacts of the technical problems and their related schedule impacts with a .76 CPI based on $ (b)(3) in BCWP costing (b)(3) to accomplish. The large current period negative cost variances in System Qualification Test, Segment Design and Integration and CONOPS Integration give an indication of the future expected negative cost performance for this Task Order. This indicates that the cumulative cost performance should worsen in the next few reporting periods. - - - The majority use of LOE and the period of performance defined rather than fixed work scope based Task Orders significantly reduce the effectiveness of EVMS as a management tool for this Task Order. The question of extending the period of performance to complete the planned work for the task order or how much work initially planned to be completed during this Task Order’s period of performance that will be delayed and move into the follow on STO Task Order remains a major constraint on developing a DCMA Independent EAC. Either the extended period of performance and additional months of manning costs or the shortfall in work accomplished impacting the long term program through follow on Task Orders are the potential cost drivers. The current spend rate and cumulative costs to date should drive total incurred costs for this STO Task Order with the current Period of Performance to the $ (b)(3) BAC. If the Period of Performance for this Task Order is significantly extended, the EAC would be significantly increased. For STO, the in place Boeing and Supplier personnel are likely to maintain a relatively high spend rate as the work to be accomplished takes longer than planned to perform. This is expected to be the fundamental cost growth driver for 2010. - ADTO Both the cumulative and current period ADTO EVMS data indicate a significant level of cost growth as would be expected from the known technical issues and their associated schedule impacts. The cumulative CPI is .89. The current period cost performance with ACWP of $ (b)(3) and claimed BCWP of only (b)(3) generating a current period CPI of less than .40. Allowing for $ (b)(3) of this being due to a DRS material transfer expense in the current period with the EV credit having been taken in the prior period, the resulting calculated CPI of .57 is still a red flag for future cost performance on the ADTO Task Order. The CPR Format 5 prepared by Boeing gives improving descriptions of the pattern of much higher than planned efforts and longer periods of time being needed to accomplish tasks and their cost impacts. Although more detail to support Format 5 variances and forecasts EACs, especially specific technical issues, and the estimates of their cost impacts are needed. These trends are expected to continue. The possible cost impacts of system technical performance risks are very large. With the majority of the budget for integration and test activities already claimed as BCWP, the additional testing and integration - -- FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000038 DHS-17-0046-C-000038 costs for both delays and more extensive than initially planned efforts are likely to go directly into negative cost variances. The cumulative SPI is driven by completed construction and purchased hardware costs. The current period and expected future CPI performance is driven by additional testing and Integration costs. The Program Office indicated that they intend to extend the period of performance for the ADTO effort to accomplish the planned tasks rather than transfer work to a follow on Task Order. Supplier revisions of staffing levels are in process. This program extension is being defined in numerous technical planning and scheduling activities and is expected to be a major cost growth driver. The definition of the extended period of performance for this Task Order also complicates the development of a DCMA independent EAC. Based on additional delays being defined since the CPR was prepared the (b)(3) worst case EAC is likely to be optimistic to accomplish the major milestones originally planned for the Subject ADTO Task Order. - DTO The DTO execution review held on 10 December 2009 was successfully accomplished. For the current period, the Management and Integration control account claimed two months of budget work credit but only one month of actual costs for a false positive cost variance of $ (b)(3) The Project and Sector (b) (7)(E) Design control account had a negative cost variance of (b)(3) due to continued work on after exhausting the planned budget for this objective. Slippage of the FONSI date, continued work on the (b) (7)(E) RAT tower design and additional effort to achieve DRR for are cost drivers. It was planned to have shifted the focus of work to the (b) (7)(E) projects by this time. Currently this effort appears to have much better expected cost performance over the next few months than ADTO and STO detailed above. The independent DCMA EAC is for this task order to complete near the $ (b)(3) BAC as impacts of technical problems and delays on STO and ADTO are likely to impact this effort enough to erode the cumulative and projected positive cost variances. - - CARs for Earned Value Management issues 1. Total CARs issued for Earned Value Management issues =18 2. Total CARs closed for Earned Value Management issues =1 3. Total CARs for Earned Value Management issues currently open =17 4. Average time to CAR closure for Earned Value Management issues = this is a long term issue. The EVMS implementation by Boeing on SBInet is still considered to require considerable improvement to be fully compliant to the EIA ANSI 748 EVMS Criteria. Boeing is invited to submit effective corrective action plans for the outstanding CARS. The majority of the CARs fall into three groups. Some of the CARs appear to be dependent or at least impacted by improvements to the Boeing IDS EVMS System description being done under the EVMS Center managed Corporate level corrective action plan and may be paced by issuance of revision D of this Document. Work Scope issues that cite criteria 1 and 3and Critical Path issues that cite criteria 6 are the other major areas needing to be addressed. For the Critical Path CARs, I think Boeing and the Program office need to agree as to what are the relevant Critical Path requirements for this program; given the use of 1 year or effectively shorter Task Orders on both STO Development and Deployment ADTO efforts. Is the ability to do Critical Path analysis for specific milestones, as Boeing now does, adequate and or the limit of what can be done FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000039 DHS-17-0046-C-000039 under the contract structure? I think we need some sort of requirements definition under the limits of the contract structure to close out the critical path CARs. For the work break down structure CARs, this will probably be paced by seeing how the work effort is managed by intensive program surveillance and by seeing a STO IBR with a majority of the work covered by Discrete EV methodology. These 3 major areas of concern will probably be the pacing items for CAR closure. -- Earned Value Management Schedule Analyst (b)(6);(b)(7)(C) DCMA Earned Value Schedule Analyst, Huntsville, AL (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C) No report for December. System Engineering (b)(6);(b)(7)(C) DCMA Huntsville, (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C) The non-conformances (NCs) in the embedded file below have been submitted through the TIPQA system for customer concurrence (with dispositions of repair, use as is (UAI), or scrap). Through November 30, 2009 there are a total of 16 NCs (12 Use as is, 1 repair, 3 scrap), with 15 given customer concurrence, and 1 pending, awaiting further information. No non-conformances were presented to the DCMA Systems Engineer for disposition concurrence this report period. Dec 09 Eng Monthy report input.xls (b) (7)(E) . Verification The following requirements were closed in December through 12/16/2009: Dec 8: (b) (7) (E) (b) (7)(E) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000040 DHS-17-0046-C-000040 (b) (7)(E) Dec 11: (b) (7) (E) . ICD (b) (7)(E) B-2 (b) (7)(E) Dec 16: B-2 (b) (7)(E) Quality Assurance Lead – Hardware (b)(6);(b)(7)(C) CMA Huntsville, (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C) DCMA Huntsville Audits Completed in Dec 09 • None DCMA Audits In Work • Boeing Internal Audits (to be completed in Jan 10) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000041 DHS-17-0046-C-000041 Boeing Internal Audits due in Jan 09 • Product Realization Boeing Internal Audits Completed in Dec 09 • Playas Developmental Test 3 Major Findings 4 Minor Findings 4 Observations • Lab Life Cycle Process and Lab Operating Process – Minor Finding (P &M) There is currently no objective evidence that life cycle and a Lab operations process exist. These processes can provide a specific life cycle analysis of the Playas Lab. (See attached procedure) The Laboratory Operations Process would identify the necessary support requirements and resources as well as providing data collection and validation. • Personnel Training – Minor Finding (P) I have not seen a Lab Manager Accreditation course for Playas. This would be required 30 days before assuming Lab Manager Duties. Technical personnel have specific training in My Learning, but there is not a developed training matrix for required courses and certifications that are applicable to Playas. • Processes and Procedures – Major Finding (M) There is no evidence of a Lab Operating Plan. This plan would be tailored to the specific Playas Lab functions and tasks. Here is where the Security, Configuration and data management, SHEA, Audits, Property Management, and Lab costs would be identified. • The Lab Manager – Major Finding (M) This person is responsible for Lab Management Accreditation Course, Plans, Processes, and Procedures to assure compliance with all Boeing and IDS common procedures. The lack of a lab operating plan makes it difficult to comply with this requirement. • Site Lab Focal – Minor Finding (P) • There is a site Lab Focal at Playas. There is not a clear direction for Site Lab Focal responsibilities due to the lack of the Lab Operating Plan. Responsibilities to include training, processes and procedures, property management, and review of costs and life cycle analysis. Quality – Minor Finding (P) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000042 DHS-17-0046-C-000042 Site Quality responsibilities are not defined due to the lack of an operating plan. Training matrix should not be the responsibility of Playas Quality. This is the responsibility of performing site personnel. Playas Quality should be conducting audits to verify compliance to all applicable processes and procedures. • Security and Shea Requirements - Observation STOP training and STOP audits? This is at the discretion of the Site Lab Manager. This may not be needed in Playas. This would be in the Lab Operating plan. • Rework and Repairs – Major Finding Work performed on the Towers and work performed on the bench Ref. D2-5378-1 PROCEDURE PS1054 ESD work station certification The two work station are not certified and there is evidence that a been opened up to install (b) (7)(E) Government property tag # (b) (7)(E) (b) (7)(E) PN (b) (7)(E) (b) (7)(E) has (b) (7)(E) • Lab Management Best Practices - Observation I have found evidence that Lab Management Best Practices are being used in Playas Areas of improvement: Self – audits tailored to lab operations Check personnel training records before proceeding with a test. • Property Management - Observation (b) (7)(E) Configuration Management – Observation (b) (7)(E) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000043 DHS-17-0046-C-000043 (b) (7)(E) Boeing Internal Audits in-work: • None Boeing Non-conformances( Does not include • Total NC’s generated in Dec – 42 (b) (7)(E) ) NC generated in Dec.xls • Total NC’s closed in Dec – 56 NC closed in Dec.xls • Total NC’s open at end of Dec – 98 Open NC.xls Boeing Corrective Actions(Does not include - (b) (7)(E) CAB meetings are now only going to being held once a month. Meeting was held 13 Oct. Attached is a list of CA open as of 31 Dec 09. • Total CA’s generated in Dec - 14 CA generated in Dec.xls • Total CA’s closed in Dec - 2 closed CA.xls • Total CA’s open at end of Dec – 59 Open CA.xls Issues and Concerns FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000044 DHS-17-0046-C-000044 (b) (7)(E) DCMA Corrective Actions Status (b) (7)(E) 1. Program Directive was issued Nov 17, 2009. Training began on Nov 23rd. DCMA verification of Boeings CA and PA effectiveness will be performed in Jan 2010. • SBI-2009-15 – Presenting Non-conforming product for GMIP. 2. Contractors response was submitted and accepted Nov 30, 2009. DCMA verification of Boeings CA and PA effectiveness will be performed in Jan 2010. Northern Border • • • • - Initial meeting on 12/15/09 with Boeing PM (b)(6);(b)(7)(C) and QA (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) DCMA QAR’s o Received Program overview; toured Border Patrol HQ in Grand Island, NY; briefed on equipment set up and locations o Discussed timeline for all testing operations, cold weather performance upgrades o Exchanged all contact information 12/16/09 o Tele-meeting with DCMA Huntsville to discuss (b) (7)(E) requirements and Letter of Delegation o Developed and sent (b) (7)(E) for approval to DCMA Huntsville; received approval on 12/17/09 12/18/09 o Forwarded (b) (7)(E) to Boeing QA, (b)(6);(b)(7)(C) o Tele-meeting with (b)(6);(b)(7)(C) and discussed preliminary testing progress thus far; all stations on pace to be complete on 12/19 12/21/09 o Reviewed report from Boeing QA; (b) (7)(E) - o Determined no further DCMA involvement until Boeing returns from holiday break. Boeing QA will contact this office on 1/4/10 with update • 12/30/09 o Monthly status report For December 2009 there was a total of 30 hours expended on this program by DCMA QAR’s . A breakdown of these hours (b)(6);(b)(7)(C) will be kept in a log in our office. FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000045 DHS-17-0046-C-000045 Quality Assurance Tucson (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) DCMA Phoenix-Tucson, (b)(6);(b)(7)(C) Email : (b)(6);(b)(7)(C) DCMA Phoenix-Tucson, (b)(6);(b)(7)(C) Email : (b)(6);(b)(7)(C) (b) (7)(E) DCMA GMIP status as of 12/31/09 - - - - - - - - - (b) (7)(E) GMIPs PPE - 01/06/10 Tower Site GMIPs Total (b) (7)(E) Tower Site GMIPs Completed Total (b) (7)(E) Tower Site GMIPs Remaining Total (b) (7)(E) Percent (b) (7)(E) Tower Sites GMIPs Complete 34 32 2 94% C2 GMIPs Total (b) (7)(E) C2 GMIPs Complete Total (b) (7)(E) C2 GMIPs Remaining Total (b) (7)(E) Percent (b) (7)(E) C2 GMIPs Complete 34 31 3 91% (b) (7)(E) (b) (7)(E) (b) (7)(E) Total Total Total Percent (b) (7)(E) Observation Observations Observations Observations Points Completed Remaining Complete 513 498 15 97% Total Total GMIPs Total GMIPs Total GMIPs GMIPs for Performed for Not Passed for Month Month Performed for Month Month 6 6 0 0 ACCOMPLISHMENTS/MILESTONES: • Completed all L3 antenna torque verification’s except for site • (b) (7)(E) (b) (7)(E) CONCERNS: • NC’s/Rework changes performed on GMIP’s after task is completed with no notification FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000046 DHS-17-0046-C-000046  • • • • • • • Example: Site (b) (7)(E) notified cable rework, RFU & SPU R&R DCMA not (b) (7)(E) Rework to (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) Quality Assurance – Software Huntsville (b)(6);(b)(7)(C) DCMA Huntsville, (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(c) attended the PCR Authentication testing for RTU 09.04 in Huntsville, Al on December 8, 2009. (b) (7)(E) (b) (7)(E) A Corrective Action Request will be issued for failure to comply with Secure Border Initiative SBInet Program Software Development Plan (b) (7)(E) and Release Software Test Plan (b) (7)(E) Procedures/Descriptions ( • The (b) (7)(E) was issued November 02, 2009 and formal response was issued on November 18, 2009. • The source code was added to clear case by (b)(6);(b)(7)(C) Reviewed by(b)(6);(b)(7)(c) and recommended CAR closure and follow – up to ensure all code has been captured in the clear case software tool. NOC/SOC will be performing monthly releases for the New Event Engineering Status. (b) (7)(E) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000047 DHS-17-0046-C-000047 (DCMA concern: The monthly releases should be under Configuration Management Control.) The Boeing Huntsville Quality Team has been requested to provide assistance on the (b) (7)(E) . They will also expand upon the understanding of the NOC/SOC software and system issues. IV&V Review Board - No Known issued due to the amount of meeting during the holidays. Status on ADTO Business and Contract Management (UNISYS)  Accomplishments 1. 12:/17/2009: Participated in weekly EVM Meeting 2. Delivered SDRLs: (b) (7)(E) ADTO ITI Projected Schedule Jun Jul (b) (7)(E) 107 days O days Thu Jf26/09 Thu 3mi& 29 days Fri 5122/09 5 days Mon 6115l1J9 28 days 6 days Au Se 4th Quarter Oct Nov Dec 1st Quart er Jan Feb Mar • Tu e 7114/09 Thu 3126/09 • , 3!26 Fri S/19/09 Sal 5f23l1J9 Thu 5f28l1J9 4 day s Fri 6f5l1J9 24 days Tue 6/9l1J9 • 1f2 DCMA perspective observations/concerns: 1. DCMA is anticipating that Boeing (Huntsville) will be updating the (b) (7)(E), (b)(6);(b)(7)(C) ) FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000048 DHS-17-0046-C-000048 2. DCMA software quality foresees Boeing should implement a process for Configuration Management control on the firmware and test tools for each item within the SBInet Program. This will ensure a better software product to the government and it will help dissimulate question being asked about what & why the different test tool version are being used at each facilities (b)(6);(b)(7)(C) Engineer: DCMA –Boeing Mesa (b)(6);(b)(7)(C) Work Number: (b)(6);(b)(7)(C) Contracts ACO: (b)(6);(b)(7)(C) DCMA Huntsville, AL, (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C) DCMA Huntsville, AL, (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C) DCMA Huntsville, AL, (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C) DCMA Huntsville, AL, (b)(6);(b)(7)(C) Email : (b)(6);(b)(7)(C) Currently in audit: DCMA Case No. 309-3E020060: L3 GS&ES, Design Task Order POP Extension, Proposal Value $ (b)(3) - DCMA Case No. 309-3E020083: ILS Extension Subject, Proposal Value (b)(3) Audits completed: 1 Audits Cancelled: 0 Technical Support for Negotiations: None Comments: reference audit 309-3E020060 DCMA continues to assist the third level sub contractor – those costs comprises 50% of the total proposal cost- to develop an auditable proposal. Property Administration (b)(6);(b)(7)(C) DCMA Huntsville, (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C) DCMA Government Property Administrators (GPA) has been trying since 28 February 2008 to integrate their support on the SBInet program and have not been able to do so for a multitude of reasons. December presented the latest road block when Boeing convinced the ILS COTR that if DCMA was to be utilized as the GPA then it was going to cost the program a lot more money. Boeing said that they would have to hire several more persons to meet DCMA’s requirements. Be assured that DCMA has not and will not levy any additional requirements on Boeing. DCMA was merely trying to validate that Boeing is performing to the FAR clause 52.245-1 2007 for Government Property Management. FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000049 DHS-17-0046-C-000049 Updates will come regarding this in January. FOR OFFICIAL GOVERNMENT USE ONLY BW7 FOIA CBP 000050 DHS-17-0046-C-000050 From: To: Cc: Subject: Date: Perfect. Thanks (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Re: Called Chief Friday, January 29, 2010 3:26:43 PM - (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Sent: Fri Jan 29 15:23:25 2010 Subject: Re: (b)(6);(b)(7)(C) Called Chief - (b)(6);(b)(7)(C) Meeting today went well. did mention she was calling just as a courtesy and to provide an update about what's going on with the assessment. It should be pretty benign and constructive. (b)(6);(b)(7)(C) 1111 We have an outline of a plan ahead. I'll send you a copy of the chart when I get back to my office. From: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Sent: Fri Jan 29 13:34:16 2010 Subject: RE: (b)(6);(b)(7)(C) Called Chief That’s probably what it’s about.  My guess is the Chief will not say it’s necessary for you to come over for a 10 minute call, but we’ll double check.     (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Meanwhile, can you just send a quick email to me and (it’s actually (b)(6);(b)(7)(C) using ’s email) after your NAC meeting to let us know if you get additional info from them.       Thanks   - - -- (b)(6);(b)(7)(C) Counselor, Office of the Commissioner U.S. Customs and Border Protection (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Friday, January 29, 2010 1:14 PM To: (b)(6);(b)(7)(C) Subject: Re: (b)(6);(b)(7)(C) Called Chief Probably about the Department's plans and approach for the SBInet assessment. USM has the lead and had an planning meeting with her own staff yesterday. (b)(6);(b)(7)(C) 1111 We are now headed to the NAC for a status meeting with the DHS participants. If the Chief wants me there, I'll try to re-wicker my schedule this afternoon. Please let me know. BW7 FOIA CBP 000051 DHS-17-0046-C-000051 From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Fri Jan 29 13:05:53 2010 Subject: (b)(6);(b)(7)(C) Called Chief 1111   (b)(6);(b)(7)(C) -- - just called and asked to speak to the Chief about SBInet for about 10-15 minutes today at 5 pm.  Any idea what that might be about?  Would you want to be here when he talks to her?   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Counselor, Office of the Commissioner U.S. Customs and Border Protection (b)(6);(b)(7)(C) BW7 FOIA CBP 000052 DHS-17-0046-C-000052 From: To: Subject: Date: (b)(6);(b)(7)(C) RE: Coffee with (b)(6);(b)(7)(C) Monday, January 25, 2010 11:57:07 AM 1111 (b)(6);(b)(7)(C) I am sitting in Tucson in the SWFO office.  I know the SBInet personnel down here also have an interest in the coffee with (b)(6);(b)(7)(C) .  Is their anyway they could dial in or our office could phone them here? Thanks - (b)(6);(b)(7)(C) -----Original Appointment----(b)(6);(b)(7)(C) From: Sent: Monday, January 25, 2010 9:26 AM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: Updated: Coffee with (b)(6);(b)(7)(C) When: Tuesday, February 02, 2010 7:00 AM-8:00 AM (GMT-07:00) Arizona. Where: Conference Room 624 (b)(6);(b)(7)(C) - BW7 FOIA CBP 000053 DHS-17-0046-C-000053 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: RE: SBInet Study on TI Cost Effectiveness Monday, January 25, 2010 1:47:38 PM , (b)(6);(b)(7)(C) I spoke with and (b)(6);(b)(7)(C) and we think the HSI effort may address the GAO recommendation: “To improve the quality of information available to allocate resources and determine tactical infrastructure’s contribution to effective control of the border, we recommend that the Commissioner of CBP conduct a cost-effective evaluation of the impact of tactical infrastructure on effective control of the border.”   HSI is drafting a synopsis of their proposed scope of work. I will provide the synopsis to all concerned and follow-up with a meeting between HSI and OBP hopefully this week to ensure we are all on the same page.   Thanks very much, (b)(6);(b)(7)(C) - 1111 - - (b)(6);(b)(7)(C)   (b)(6);(b)(7)(C) 1901 S. Bell St. Arlington, VA 22202 (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) From: Sent: Monday, January 25, 2010 9:20 AM (b)(6);(b)(7)(C) To: Subject: FW: SBInet Study on TI Cost Effectiveness fysa   (b)(6);(b)(7)(C) Communications and Reporting Branch Chief Office of Border Patrol Program Management Office Facilities Management and Engineering (b)(6);(b)(7)(C)(w) (bb) (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Monday, January 25, 2010 7:59 AM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject: FW: SBInet Study on TI Cost Effectiveness Hello all,   Please see the email below from (b)(6);(b)(7)(C) .  The one recommendation in GAO-09-896 (SBI Program IV) was directed to OBP.  However, it looks like FM&E is addressing the recommendation.  Should this recommendation be transferred to OA/FM&E instead of OBP?  Can you please provide some additional details regarding the TI and Technology Impact Study that was initiated?  I want to ensure there is no - BW7 FOIA CBP 000054 DHS-17-0046-C-000054 duplication of efforts here.  Thanks.   (b)(6);(b)(7)(C) CBP Audit Liaison U.S. Customs and Border Protection (b)(6);(b)(7)(C) (Office) (Fax) (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Friday, January 22, 2010 3:36 PM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: SBInet Study on TI Cost Effectiveness 1111   (b)(6);(b)(7)(C) I received email from the OBP Branch Chief overseeing TI.  He received a call from FM&E informing him that a TI and Technology Impact Study was initiated by SBInet Director (b)(6);(b)(7)(C)   Considering that BP had been in consultation with the University of Arizona to conduct our own assessment to fulfill a GAO requirement, we would be very interested in knowing what the objectives of this TI and Tech Impact study are to preclude duplication of effort on our part.    Could you please contact FM&E and/or SBI to obtain more information for us?  Our efforts were directed at fulfilling the GAO recommendation referenced in the attached DHS response to GAO.  At the time, SBInet directed that recommendation to BP; however, now it appears as if they have taken the lead on it.  We will defer to them since our efforts to date have only been to consult with UofA and may not be as far along as SBInet in their efforts to conduct this study.   Thank you.   (b)(6);(b)(7)(C) Analysis Branch Strategic Planning, Policy and Analysis Division CBP-Office of Border Patrol Office:(b)(6);(b)(7)(C) (b)(6);(b)(7)(C) BW7 FOIA CBP 000055 DHS-17-0046-C-000055 From: To: Subject: Date: Attachments: - (b)(6);(b)(7)(C) RE: STATUS SLIDES Sunday, January 31, 2010 6:42:06 PM SBInet Update 1-29-10 rev1.ppt —   Thanks.  Here’s what I intend to use with the staffers this week.   Please note I had to make lots of changes to format.  Titles, for example, had different color and font sizes.  Font sizes on several charts were so small as to be illegible—I fixed what I could but some were embedded within graphics.   In the future, please use the format that I use for my briefings.  I think you have copies but if not, let me know and I will send an example.  It will help save me hours of time reformatting.  Thanks.   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) Sent: Friday, January 29, 2010 6:31 PM (b)(6);(b)(7)(C) To: Subject: RE: STATUS SLIDES - Sir, attached is an update to the slide deck (b)(6);(b)(7)(C) provided with a schedule.  This is still being massaged a bit, that’s why it still is in powerpoint graphic versus IMS format.     As for the MSC, proposals are planned to be due on 1 Mar 2010, predicated on the revised RFP being released by 5 Feb.   Thks   V/r   (b) (7)(E) (b)(6);(b)(7)(C) Deputy Director, Secure Border Initiative Network Phone (b)(6);(b)(7)(C) Mobile Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. BW7 FOIA CBP 000056 DHS-17-0046-C-000056 SBInet Update January 29, 2010 BW7 FOIA CBP 000057 For Fo Official Official Use U Only O ly For Official DHS-17-0046-C-000057 al Use U e Only Only (b) (7)(E) Schedule (b) (5) CCB Approved for planning purposes 1-27-10 (b) (5) 9/3 9/13 9/15 ROT&E BW7 FOIA CBP 000058 For Official DHS-17-0046-C-000058 a Use Only Ony (b) (7)(E) (b) (7)(E) Status (b) (7)(E) Field Construction Completed – Construction began on 5/4/09 – Modification of (b) (7)(E) was completed on 5/29/09 (b) (7)(E) – Completed (b) (7)(E) Issues and Concerns – Final Acceptance behind schedule due to software changes/fixes – Test definitions and agreements still unresolved – Ao still in refinement • Working with OID and Boeing to converge on an agreed definition Look ahead - Next 90 Days – Complete Field Check-out and Integration (b) (7)(E) – Installation of – Installation of upgrades for (b) (7)(E) – User familiarization starts week of 1 Feb BW7 FOIA CBP 000059 For Official Use Only DHS-17-0046-C-000059 (b) (7)(E) Schedule • Field Check-out & Integration – 2nd quarter, FY2010 • IT Infrastructure Installation & Check Out – 3rd quarter, FY2010 • System Acceptance Dry Runs – 3rd/4th quarter, FY2010 • System Acceptance Test – 4th quarter, FY2010 • Test Data Analysis – 4th quarter, FY2010 • Operational Test & Evaluation – 1st quarter, FY2011 • Schedule dates still under refinement BW7 FOIA CBP 000060 For Official DHS-17-0046-C-000060 a Use Only Ony (b) (7)(E) Status As of 1/27/10 • - (b) (7)(E) Accomplishments (b) (7)(E) − − − − − C2 Modular Facility construction began 8/20/09 Biological Opinion Signed on 12/10/09 FONSI signed on 12/23/09 (b) (7)(E) SUP obtained on 1/5/10 Bureau of Land Management Right of Way obtained on 1/19/10 − Quality Summit held on 1/20/10 − CRR held on 1/21/10 − Start of Construction on 1/25/10 for (b) (7)(E) , (b) (7)(E) • Issues and Concerns − GSA Land Access – Site 301 − Working with FM&E to resolve (ECD 2/28) − Overall Construction Schedule stretches into Pronghorn Season (working with DOI for possible opportunities to mitigate) − RAT Towers construction meeting Pronghorn Fawning restriction • Look Ahead - Next 90 days − Receive land use permits from GSA, Arizona State Land Department, and (b) (7)(E) − Start of Construction for (b) (7)(E) - − IAA with USFWS and National Park Service for conservation measures. BW7 FOIA CBP 000061 For Official DHS-17-0046-C-000061 a Use Only Ony (b) (7)(E) Tower Construction As of 25 Jan (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) ID 4 ,748 (b) (5) 4769 4 ,790 4812 487 1 4904 4995 5108 Piro111gho:m Fawmin o Seaso1111Beg in s :J11s .A I 5109 Pro n gjh mrn Faw rf mg Seas o n Bmds µ 001111'116 IJJ6e Dli~ • ct' Elata 1CCl"ltamed al ·llilS Sheeli IS &Utf,ectto n!mlciloo. 7115 summary T;a.A n.a,_,wt Pl:M'eJ" · OOO!crele 1Grl>Ud11g DRS T_. e.aetmgSlteCfO Page,1 MUe&i:Dlr!e (b)(6);(b)(7)(C) BW7 FOIA CBP 000062 (b)(6);(b)(7)(C) (b)(6);(b) l Use Only DHS-17-0046-C-000062 (b) (7)(c) (6); (b) (7)(E) Schedule •Field Check-out & Integration – 2nd quarter, FY2010 • IT Infrastructure Installation & Check Out – 3rd quarter, FY2010 • System Acceptance Dry Runs – 4th quarter, FY2010 • System Acceptance Test – 1st quarter, FY2011 • Operational Test & Evaluation – 1st quarter, FY2011 BW7 FOIA CBP 000063 For Official DHS-17-0046-C-000063 a Use Only Ony Departmental Re-Assessment • Directed by Secretary Napolitano • Motivated by concern over program delays – Need to review program viability – Need to identify options for near-term technology deployment to high priority areas • Near-term focus on consideration of “stand-alone” options that could meet immediate needs • Long-term focus based on anticipated Acquisition Decision Event 3 (ADE-3)—next year – Completion of SBInet Initial Deployments – Evaluation of system effectiveness – Decision on future deployments of SBInet (if any) • Detailed assessment plan currently under development BW7 FOIA CBP 000064 For Official DHS-17-0046-C-000064 a Use Only Ony (b) (7)(E) Improvement Effort BW7 FOIA CBP 000065 For Fo Official Official Use U Only O ly For Official DHS-17-0046-C-000065 al Use U e Only Only (b) (7)(E) (b) (7)(E) Effect of Improvements (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) Does not include (b) (7)(E) improvements BW7 FOIA CBP 000066 For Official DHS-17-0046-C-000066 a Use Only Ony (b) (7)(E) Effect of Improvements (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) Does not include (b) (7)(E) improvements (b) (7)(E) BW7 FOIA CBP 000067 For Official DHS-17-0046-C-000067 a Use Only Ony Northern Border BW7 FOIA CBP 000068 For Fo Official Official Use U Only O ly For Official DHS-17-0046-C-000068 al Use U e Only Only (b) (7)(E) Site Status Northern Border Project (b) (7)(E) Site (b) (7)(E) Name I&CO Completed 01/05/10 1/6/10 2009 2010 December January Site Construction I&CO Completed 12/23/09 Buffalo HQ I&CO 12/28/09 February 1/4 1/5 Dry Runs 1/15 = 1/21 01/04/10 (b) (5) 01/04/10 12/28/09 (b) (7)(E) 12/30/09 Additional Notes: 1. Functional Acceptance Testing to be complete on Friday, January 29th. The results so far have revealed no discrepancies. 2. (b) (7)(E) (b) (7)(E) (b) (7)(E) 3. (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7) (E) Plan to turn the system over to Border Patrol for operational use at the conclusion of regression test (approx 2/13). Major Issues/Concerns: Exploring a no-cost extended warranty for the (b) (7)(E) BW7 FOIA CBP 000069 icial DHS-17-0046-C-000069 a Use Only Ony (b) (7)(E) Site Status Site (b) (7)(E) Name I&CO Completed 02/23/10 Northern Border Projec (b) (7)(E) 1/4/10 2010 January 01/14/10 February March (b) (5) 01/15/10 01/29/10 01/19/10 02/05/10 02/04/10 01/14/10 01/13/10 TBD 02/26/10 02/04/10 - Additional Notes: (b) (7)(E) • USACE to begin condemnation proceedings for (b) (7)(E) . Government Acceptance for all other sites is scheduled for 3/22/10 with the (b) (7)(E) to be completed in late summer 2010. (b) (7)(E) (b) (7)(E) • . • Boeing to begin directional boring for (b) (7)(E) utility corridor 02/13/2010. • Construction is completed for sites (b) (7)(E) Sites (b) (7)(E) . Sector HQ estimated date of completion is 2/3/2010. BW7 FOIA CBP 000070 (b) (7)(E) condemnation proceedings. (b) (7)(E) directional boring and electrical cable construction Major Issues/Concerns: (weather permitting). - For Official DHS-17-0046-C-000070 a Use Only Ony Operational Integration Center (OIC) Status Task Duration Expected Completion Approval from SECAF Obtain Abatement Permits n/a (b) (5) 3 wks Abatement 6 wks Construction 30 wks Hardware Installation 4 wks System Testing 2 wks OIC Opening Day n/a Operational Integration Center ((b) (7)(E) ) 1/28/10 JAN FEB MAR 2010 APRSite Construction MAY JUN 2/22 JUL Completed AUG SEP OCT (b) (5) -  Recent (b) (7)(E) approval allows project to proceed , albeit later than planned  Unanticipated requirement for abatement and additional permits has created schedule delays Notes: 1. Construction schedule is a preliminary estimate only! Actual schedule TBD once construction contract awarded. (Expected 2/5) 2. Assumption is made that hardware can be installed prior to completion of construction. BW7 FOIA CBP 000071 For Official DHS-17-0046-C-000071 a Use Only Ony NOV From: (b)(6);(b)(7)(C) Sent: Friday, January 29, 2010 3:51 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: STATUS SLIDES Based on the MSC RFP update, when do we expect proposals?   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) Sent: Friday, January 29, 2010 2:02 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: STATUS SLIDES - :  Here are the status slides you asked for, plus additional slides for my bi-weekly update.  One note on the OIC slide.  There is some minor disagreement over the date that construction will actually be completed.  I’ve given you two slides showing the differing opinions.  I personally think the Oct date is (b)(6);(b)(7)(C) more realistic, is concerned that is we say Oct we will need to update congress as this is a change.       I’m headed out to a meeting with MTCSC Corporation.  I do not plan on coming back to the office this afternoon, but will be available by cell phone if you have any questions on this package.    Thanks       (b)(6);(b)(7)(C) - (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. BW7 FOIA CBP 000072 DHS-17-0046-C-000072 (b)(6);(b)(7)(C) From: To: Subject: Date: Re: Next week"s JPMR Monday, January 25, 2010 6:06:00 PM I certainly won't be able to live up to the standards you've set, but I can chair the review. - (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, DHS (b)(6);(b)(7)(C) From: To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Sent: Mon Jan 25 16:47:53 2010 Subject: Next week's JPMR • —   It looks like I’ll have a heck of a time with the JPMR next week, since it overlaps with (1) the SBI budget (b)(6);(b)(7)(C) presentation to appropriations staffers and (2) s farewell luncheon.  I don’t think it’d make sense to reschedule JPMR—which means you’ll probably have to chair it.  Okay?   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000073 DHS-17-0046-C-000073 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: Attachments: FW: DHS OPCP Final Draft certification Monday, January 25, 2010 2:05:07 PM Chief Procurement Officer Certification Table of Contents FY 2010(5) (2).doc (b) (5) Sirs: I know well enough the silence is not the same as concurrence. I would really appreciate your input so I can begin routing the package without multiple returns.   Thanks…   (b)(6);(b)(7)(C) SBI Contract Division Director Chief of the Contracting Office O (b)(6);(b)(7)(C) C (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Wednesday, January 20, 2010 5:24 PM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: DHS OPCP Final Draft certification Sirs:  I want to get you chop on the CBP DHS OCPO Memorandum that is required as part of BSIT Expenditure Plan. Members of your staff have been involved. We have attempted to address SBI, TI & TACCOM in the memorandum in a consolidated manner.  It is thru the Procurement Directorate to DHS OCPO.   Attached are the draft memo and the Table of Contents for the supporting data.  Would appreciate you comments by Friday 22 Jan 10.   Thanks   (b)(6);(b)(7)(C) SBI Contract Division Director Chief of the Contracting Office O (b)(6);(b)(7)(C) C (b)(6);(b)(7)(C) BW7 FOIA CBP 000074 DHS-17-0046-C-000074 Chief Procurement Officer Certification Supporting Documentation for Certification of the Secure Border Initiative Program, U.S. Customs and Border Protection Table of Contents A. The program (SBI, TI, & TACOM) has been reviewed and approved in accordance with the investment management process of the department, and that the process fulfills all capital planning and investment control requirements and reviews established by the Office of Management and Budget, including as provided in Circular A-11, part 7 1. SBI a. Acquisition Decision Memorandum (ADM) (1) ADM February 11, 2009 (2) ADM May 26, 2009 b. Investment Review (1) SBlnet Review Methodology N/A (2) Investment Review Status as of April 03, 2009 c. OMB 300 (1) DHS Exhibit 300 for Mixed BY 11-CBP SBI SBInet 2011 September 24, 2009 2. TI a. Acquisition Decision Memorandum (ADM) (1) TI ADM August 8, 2008 (2) CBP FME CTIMR Fence Maintenance Services ADM September 09, 2009 b. Investment Review (1) SBI Tactical Infrastructure Investment Review Board Presentation August 8, 2009 (2) SBI Tactical Infrastructure Investment Review Presentation August 13, 2008 c. OMB 300 (1) Awaiting Documents 3. NON-RESPONSIVE BW7 FOIA CBP 000075 DHS-17-0046-C-000075 B. The plans for The Program (SBI, TI, & TACCOM) to comply with Federal Acquisition Regulation (FAR) and where the plans are in non-compliance with the FAR, adequate strategies are in place to address areas of non-compliance 1. SBI Contracting a. COTR Designation (1) Database Listing of all COTRs November 16, 2009 b. COTR Processes, Procedures, Statistics, and Training (1) COTR Certification Process/Procedures N/A (2) DHS Acquisition Training Schedule N/A 2. NON-RESPONSIVE 3. 4. SBI Contracting DCAA Interagency Agreement (1) DCAA Support on the SBI Program N/A (2) Copy of Interagency Agreement January 09, 2008 (3) Modification P00001 March 06, 2008 (4) Modification P00002 October 01, 2008 (5) Modification P00003 January 23, 2009 5. SBI Contracting DCMA Interagency Agreement (1) DCMA Support on the SBI Program N/A (2) Copy of Interagency Agreement February 13, 2008 (3) SBInet MOA between CBP and DCMA N/A (4) Contracting Officer's Letter to DCMA March 19, 2008 (5) Modification P00001 February 12, 2008 (6) Modification P00002 February 13, 2009 6. NON-RESPONSIVE 7. SBI Contracting DCMA and DCAA Systems Status Reviews of The Boeing Company (1) DCAA Recon Corrective Action Plan July 08, 2009 BW7 FOIA CBP 000076 DHS-17-0046-C-000076 (2) DCAA MFR 01201-2009L11015003 March 03, 2009 (3) DCAA Report 01201-2008L17750003 April 22, 2009 (4) DCAA Report 01201-2008L17750004 July 22, 2009 (5) EOY Recommendation Boeing IDS HSV site rev. 1 February 12, 2008 (6) DCMAM-SHAC-ACO-09-06 March 24, 2009 (7) DCMAM-SHAC-ACO-09-18 May 18, 2009 (8) DCMAM-SHAC-ACO-09-24 July 22, 2009 (9) DCMAM-SHAC-ACO-09-30 October 23, 2009 (10) DCMA Financial Surveillance on The Boeing Company for the First Quarter of FY 2009 FAB Case No. 09-663 June 04, 2009 (11) System Surveillance Report Boeing IDS HSV rev. 3 December 05, 2008 (12) System Status Matrix October 01, 2009 (13) Boeing response to DCAA Audit Report No. 1201-2008L17750004 June 04, 2009 8. SBI Contracting MAP (1) 2009 SBI Mission Action Plan (MAP) January 16, 2009 (2) 2008-2009 SBI MAP Comparison Table N/A (3) Map Description for 2010 Procurement Certification N/A (4) FY 2009 Annual Report on Internal Controls N/A (5) FY 2009 DHS MAPs Year End Status of Milestones Data Call N/A 9. SBI Contracting SBlnet Contract Policy and Management (1) SBI AO Contract Policy and Management N/A (2) Listing of all SBI AO Policies N/A 10. SBI Contracting Buy American - FRGN Reporting (1) DHS FRGN ITEM Report Form(Buy American) N/A C. Adequate procedures are in place to prevent conflicts of interest between the prime integrator and major subcontractors 1. SBI Contracting Organization Conflict of Interest (OCI) (1) Boeing's Proposal May 30, 2006 (2) Boeing's Guidance for Programs Establishing Firewalls to Mitigate Organizational Conflicts of Interest March 19, 2004 (3) SBlnet Acquisition office Request to DCMA to Perform a Review of Boeing's Compliance with their OCI March 28, 2008 (4) DCMA Response to SBInet Acquisition Office 28 March Request concerning Boeing's OCI Compliance April 03, 2008 (5) DCMA e-mail Regarding SBlnet request 28 March Request concerning Boeing's OCI Compliance May 15, 2008 (6) DCMA e-mail Regarding SBInet 28 March Reques Concerning Boeing's OCI Compliance May 06, 2008 (7) SBInet, IDIQ OCI Clause N/A BW7 FOIA CBP 000077 DHS-17-0046-C-000077 D. The SBI, TI & TACCOM Program Offices and other programs that receive BSFIT has adequate staff and resources to effectively manage the SBI program, including adequate staff to support all contracts 1. SBI, TACCOM, TI Contracts & Program Management Offices Staffing Statistics a. SBI, TACCOM & TI Contracting Office Staffing Statistics FY10 January 20, 2010 b. SBI, TACCOM & TI Program Management Office Staffing Statistics FY10 January 20, 2010 c. Summary Staff Totals for PMO and CO for SBI, TI, and TACCOM January 20, 2010 2. SBI Program Management Office, Certification and Related Statistics/ Center of Excellence (CoE) (1) PM Certification Process/Procedures N/A (2) PM Currency Tracking Process N/A (3) SBI program Project PM DPM Status November 16, 2009 (4) Center of Excelence Overview November 16, 2009 3. NON-RESPONSIVE 4. 5. Operational Status Report a. SBI & TI Contracting Operational Status Report (1) Operational Status Report 4Q Final N/A (2) FY09 DHS OSR Q4 (FINAL)- SBIAO N/A b. NON-RESPONSIVE BW7 FOIA CBP 000078 DHS-17-0046-C-000078 From: To: (b)(6);(b)(7)(C) Cc: Subject: Date: Attachments: Importance: CBP Status of ARRA Projects- Week 48 Final Tuesday, January 26, 2010 7:56:25 AM CBP Status of Recovery Projects-1-25-10.xls High Good morning, ARRA Program Managers and key contacts Attached for your records, is the final CBP Status of ARRA Projects that was submitted to DHS for Week 48.     If you have any questions, please contact us at (b)(6);(b)(7)(C) .  Thank you.       *************************************************************************************************************************************** For the latest information on CBP ARRA efforts, please visit the CBP ARRA Working Group KMS site at: (b)(6);(b)(7)(C) ***************************************************************************************************************************************   BW7 FOIA CBP 000079 DHS-17-0046-C-000079 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) as of 01/22/10 Status of Project (Is the project on Anticipated track to be obligated by the Obligation anticipated obligation date? If not, please explain the delays) Date Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b)(6);(b)(7)(c) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b)(6);(b) (7)(c) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b ) (6 (b)(6);(b) ); (7)(c) (b)(6);(b)(7)(c) (b ) (7 ) (c ) BW7 FOIA CBP 000080 DHS-17-0046-C-000080 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) as of 01/22/10 Status of Project (Is the project on Anticipated track to be obligated by the Obligation anticipated obligation date? If not, please explain the delays) Date Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b)(6);(b)(7)(c) NON-RESPONSIVE (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b)(6);(b)(7)(c) (b) (7) (E) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b)(6);(b) (7)(c) (b)(6);(b) (7)(c) (b) (7)(E) BW7 FOIA CBP 000081 DHS-17-0046-C-000081 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) as of 01/22/10 Status of Project (Is the project on Anticipated track to be obligated by the Obligation anticipated obligation date? If not, please explain the delays) Date Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) Outlays TAFS # Awardee (b)(6);(b)(7) (c) Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b) (7) (E) (b)(6);(b) (7)(c) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b ) (b)(6);(b)(7) (6 (c) ); (b ) (7 ) (c ) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b)(6);(b)(7)(c) (b) (7) (E) (b) (7) (E) BW7 FOIA CBP 000082 DHS-17-0046-C-000082 CBP ARRA Weekly Status of ARRA Projects as of 01/22/10 Status of Project (Is the project on Anticipated track to be obligated by the Obligation anticipated obligation date? If not, Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been NON-RESPONSIVE (b) (b) (7) (b) (7) (E) (7) (E (E) ) (b) (b)(7) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (7) (E) (E) (b)(6);(b)(7) (b)(6);(b)(7)(c) (c) (b) (7)(E) (b ) (b (7 ) (7 (E ) (E ) (b)(6);(b)(7)(c) (b)(6);(b)(7)(c) (b)(6);(b)(7)(c) (b)(6);(b)(7)(c) (b)(6);(b) (7)(c) (b)(6);(b) (7)(c) BW7 FOIA CBP 000083 DHS-17-0046-C-000083 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) as of 01/22/10 Status of Project (Is the project on Anticipated track to be obligated by the Obligation anticipated obligation date? If not, please explain the delays) Date Yes. The "Anticipated Obligation Date" provided is the last date on which we anticipate obligating funds for this project, which will cover CBP Tactical Communications (b) (7)(E) Modernization efforts in the (b) (7)(E) There will be several contracts let over the Tactical Communications - Will course of the project, and the modernize legacy land mobile radio schedule for those contracts is systems used by CBP agents and contingent upon a decision pending officers to provide (b) (7)(E) on the Tactical Communications (b) (7)(E) equipment with Acquisition Strategy. The data (b) (7)(E) . In addition, the provided in this sheet for obligations modernization will provide for (b) (7)(E) incurred to date concern individual which task orders supporting the ongoing (b) (7)(E) directly supports SBInet's Common ization efforts in (b) (7)(E) (b) (7)(E) Operating Picture. Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) Outlays TAFS # Awardee (b) (7) (E) (b) (7) Tactical Communications (b) (7)(E) (E) Will be awarded in an 8a modernization open market (b) equipment and reserve expenses (7) competition This is transfer out rather than a (E) contract award; TacCom transferred $25,100 to the ENTS Training branch to support TACCOM-related training travel and services. It willl be obligated and expended on an asTactical Communications - Training consumed basis. TACCOM Net Outlays Contract Number Contract Type Competition Type Eyaktek: 22980 Indian Creek Drive, Suite 400, Dulles, VA 20166 9/10/10 8/29/09 (b)(3) 5/11/2009 5/27/09 7/29/09 (b)(3) TBD Tactical Communications (b) (7)(E) structural analysis for towers Just awarded. (b ) (b) (7)(E) Tactical Communications (7 Will be awarded in open competition services and civil equipment (b ))(b) (7)(E) Tactical Communications (b) services and civil equipment (7 (E Will be awarded in open competition TACCOM )(7) ) (E) (E TACCOM Expenditures - not disbursed ) Awardee Address (b)(3) estimated) 8/29/2009 (b)(3) 9/21/2009 (b)(3) 6/30/10 (b)(3) 6/30/10 (b)(3) 70-0534 2009 \ 2010 EyakTek Wrightline Commdex Commdex: 1531 South Edgewood Road, Suite C, Baltimore, MD 21227 HSPB100823360 GS-29F-0100G HSPB1008P22970 Eyaktek tasks directed 8a, Native American owned. The Wrightline order Firm fixed price replaced pre-existing contract equipment. 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price contract 8a 70-0534 2009 \ 2010 N/A - funded government travel N/A N/A 70-0534 2009 \ 2010 American Tower 116 Huntington Avenue, 11th Floor, Boston, MA, 02116 1009P28032 Firm fixed price contract Name Brand 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price contract Open 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price contract Open Wrightline: 160 Gold Star Blvd, Worcester, MA 01606 (b)(3) N/A N/A (b)(3) $0 (b)(3) NON-RESPONSIVE (b)(6);(b)(7)(c) (b)(6);(b)(7)(c) BW7 FOIA CBP 000084 DHS-17-0046-C-000084 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) as of 01/22/10 Status of Project (Is the project on Anticipated track to be obligated by the Obligation anticipated obligation date? If not, please explain the delays) Date Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b)(6);(b)(7)(c) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (b) (E) (7) (E) (b) (7) (b) (E) (7) (b) (E) (7) (b (E) ) (7 (b) ) (7) (b) ( (E) (7) E (E) ) (b) (7) (E) (b) (7) (E) (b)(6);(b)(7)(c) (b)(6);(b) (7)(c) (b)(6);(b)(7) (c) (b) (7) (E) BW7 FOIA CBP 000085 DHS-17-0046-C-000085 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) as of 01/22/10 Status of Project (Is the project on Anticipated track to be obligated by the Obligation anticipated obligation date? If not, please explain the delays) Date Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been obligated) (anticipated or actual) Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b)(6);(b)(7) (c) NON-RESPONSIVE (b) (7) (E) SBInet Long Lead Components & Equipment Purchases Block 1 SAT is now scheduled to begin mid- 2010 (Jun or July). A decision on procurement of the parts for the next deployment would be made around Aug 2010. Alternate use of these funds due to the slips in SAT is being actively investigated. Expect a decision to be made in early Feb 2010 - Anticipated Obligation Date is June (b) (7)(E) 2010. Th RFP was released SBInet Existing Technology (b) (7)(E) on 28 December 2009, with responses due by 29 January 2010. (b (b) (b) (7)(E) ) (7) (7 (E) ) Planning a (E kick-off meeting with the SBInet Acquisition team to develop a contract vehicle ) strategy/plan of SBInet TACCOM modernization in and milestones to obligate ( action (b) (7)(E) funding by June 30, 2010. SBInet b ) SBInet Expenditures - not disbursed ( 7 SBInet Net Outlays ) ( E ) 4/15/10 6/30/10 (b)(3) TBD (b)(3) TBD 0 0 70-0536 2009 \ 2010 70-0536 2009 \ 2010 TBD TBD TBD TBD TBD Task Order issued on existing competitively Firm Fixed awarded IDIQ Price contract Contract. TBD TBD but most likely Firm Fixed Price Competitively contract awarded contract. TBD TBD but most likely Firm Fixed Price Competitively contract awarded contract. (b) (7)(E) 6/30/10 (b)(3) TBD 70-0536 2009 \ 2010 TBD TBD $0 $0 $0 ` BW7 FOIA CBP 000086 DHS-17-0046-C-000086 From: To: (b)(6);(b)(7)(C) Cc: Subject: Date: Attachments: Importance: CBP Status of ARRA Projects- Week 48 Final (Revised) Tuesday, January 26, 2010 10:39:36 AM CBP Status of Recovery Projects-1-25-10-revised .xls High Good morning, ARRA Program Managers and key contacts Attached for your records, is the final (revised) CBP Status of ARRA Projects that was submitted to DHS for Week 48.     If you have any questions, please contact us at (b)(6);(b)(7)(C) .  Thank you.       *************************************************************************************************************************************** For the latest information on CBP ARRA efforts, please visit the CBP ARRA Working Group KMS site at: (b)(6);(b)(7)(C) ***************************************************************************************************************************************   BW7 FOIA CBP 000087 DHS-17-0046-C-000087 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/22/10 Week 48 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been (anticipated or actual) obligated) FINAL Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b)(6);(b)(7)(c) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (b) (7) (E) (E) (b) (7)(E) (b) (7) (E) (b)(6);(b)(7)(c) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (b ) (6 (b)(6);(b) ); (7)(c) (b)(6);(b)(7)(c)(b ) (b)(6);(b)(7)(c)(7 ) (c ) (E) (b) (7) (E) BW7 FOIA CBP 000088 DHS-17-0046-C-000088 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/22/10 Week 48 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been (anticipated or actual) obligated) FINAL Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b)(6);(b)(7)(c) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7) (b)(6);(b) (7)(c) (b)(6);(b) (7)(c) (E) (b) (7)(E) (b) (7) (E) BW7 FOIA CBP 000089 DHS-17-0046-C-000089 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) (b) (7) (E) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/22/10 Week 48 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been (anticipated or actual) obligated) FINAL Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b)(6);(b)(7) (c) NON-RESPONSIVE (b)(6);(b) (7)(c) (b) (7) (E) (b) (7) (E) (b) (6); (b)(6);(b)(7) (b) (c) (7) (c) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b)(6);(b) (7)(c) (b)(6);(b)(7)(c) BW7 FOIA CBP 000090 DHS-17-0046-C-000090 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) Schedule will be rebaselined post as of 01/22/10 Week 48 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been (anticipated or actual) obligated) FINAL Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b) (b) (7) (b) (7) (E) (b) (7) (E) (b) (7) (E) (7) (E) (b) (7)(E) (E) (b) NON-RESPONSIVE (7) (E) (b) (7) (E) (b )(b)(6);(b)(7)(c) (6 );(b)(6);(b)(7)(c) (b ) (7 (b)(6);(b)(7)(c) ) (c ) (b ) (b (7 ) (7 (E (b)(6);(b) ) (7)(c) (E ) (b)(6);(b)(7) (c) (b)(6);(b)(7) (c) (b ) (6 ); (b ) (7 ) (c ) BW7 FOIA CBP 000091 DHS-17-0046-C-000091 as of 01/22/10 Week 48 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been (anticipated or actual) obligated) CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) Yes. The "Anticipated Obligation Date" provided is the last date on which we anticipate obligating funds for this project, which will cover CBP Tactical Communications Modernization efforts in th (b) (7)(E) There will be several contracts let over the Tactical Communications - Will course of the project, and the modernize legacy land mobile radio schedule for those contracts is systems used by CBP agents and contingent upon a decision pending officers to provide (b) (7)(E) on the Tactical Communications (b) (7)(E) Acquisition Strategy. The data (b) (7)(E) In addition, the provided in this sheet for obligations modernization will provide for (b) (7)(E) incurred to date concern individual (b) (7)(E) hich task orders supporting the ongoing directly supports SBInet's Common modernization efforts in (b) (7)(E) (b) (7)(E) Operating Picture. FINAL Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type (b) (7)(E) 5/11/2009 (b) (7) (E) Will be awarded in an 8a competition This is transfer out rather than a contract award; TacCom transferred (b)(3) o the ENTS Training branch to support TACCOM-related training travel and services. It willl be obligated and expended on an asTactical Communications - Training consumed basis. Tactical Communications (b)(3) TACCOM Net Outlays The Wrightline order replaced pre-existing equipment GS-29F-0100G 70-0534 2009 \ 2010 Commdex Commdex: 1531 South Edgewood Road, Suite C, Baltimore, MD 21227 HSPB1008P22970 Firm fixed price contract 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price 8a contract 70-0534 2009 \ 2010 N/A - funded government travel N/A N/A 70-0534 2009 \ 2010 American Tower 116 Huntington Avenue, 11th Floor, Boston, MA, 02116 1009P28032 Firm fixed price Name Brand contract 6/30/10 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price Open contract 6/30/10 70-0534 2009 \ 2010 TBD TBD TBD Firm fixed price Open contract 9/10/10 (b)(3) 7/29/2009 TBD 8/29/09 (b) (7)(E) TACCOM Expenditures - not disbursed Eyaktek tasks directed 8a, Native American owned. . Wrightline: 160 Gold Star Blvd, Worcester, MA 01606 5/27/2009 8/29/2009 (b)(3) (b) (7)(E) (b Just awarded. ) Tactical Communications (b) (7)(E) services and civil equipment (b (7 Will be awarded in open competition )(b) ) (7)(E) Tactical Communications services and civil equipment (7 ((b) Will be awarded in open competition (7) )E) (E) (E TACCOM ) HSPB100823360 Wrightline (b) (7)(E) Tactical Communications modernization open market equipment and reserve expenses Eyaktek: 22980 Indian Creek Drive, Suite 400, Dulles, VA 20166 EyakTek 9/21/2009 N/A N/A (b)(3) $0 (b)(3) (b)(6);(b)(7)(c) NON-RESPONSIVE BW7 FOIA CBP 000092 DHS-17-0046-C-000092 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/22/10 Anticipated Obligation Week 48 FINAL Actual Obligation Date (if funds have Amount of Obligation already been (anticipated or actual) obligated) NON-RESPONSIVE (b)(6);(b)(7)(c) (b)(6);(b)(7)(c) (b)(6); (b)(7) (b)(6); (c) (b)(7) (c) (b)(6);(b) (7)(c) BW7 FOIA CBP 000093 DHS-17-0046-C-000093 CBP ARRA Weekly Status of ARRA Projects Project (name/short description) Status of Project (Is the project on track to be obligated by the anticipated obligation date? If not, please explain the delays) as of 01/22/10 Week 48 Anticipated Obligation Date Actual Obligation Date (if funds have Amount of Obligation already been (anticipated or actual) obligated) FINAL Outlays TAFS # Awardee Awardee Address Contract Number Contract Type Competition Type NON-RESPONSIVE (b)(6);(b)(7) (c) (b) (7) (E) SBInet Long Lead Components & Equipment Purchases SBInet Existing Technology (b) (7)(E) Capability) Block 1 SAT is now scheduled to begin mid- 2010 (Jun or July). A decision on procurement of the parts for the next deployment would be made around Aug 2010. Alternate use of these funds due to the slips in SAT is being actively investigated. Expect a decision to be made in early Feb 2010 -(b) (7)(E) Anticipated Obligation Date is June (b) (7)(E) 2010. Th RFP was released on 28 December 2009, with responses due by 29 January 2010. Planning a kick-off meeting with the SBInet Acquisition team to develop a contract vehicle strategy/plan of (b) (7)(E) SBInet TACCOM modernization i action and milestones to obligate nding by June 30, 2010. (b) (7)(E) 4/15/10 6/30/10 6/30/10 (b)(3) TBD TBD (b)(3) TBD 0 0 (b)(3) 70-0536 2009 \ 2010 70-0536 2009 \ 2010 (b)(3) SBInet 70-0536 2009 \ 2010 TBD TBD TBD TBD TBD TBD TBD Task Order issued on existing competitively Firm Fixed awarded IDIQ Price contract Contract. TBD TBD but most likely Firm Fixed Price Competitively contract awarded contract. TBD TBD but most likely Firm Fixed Price Competitively contract awarded contract. $0 SBInet Expenditures - not disbursed $0 SBInet Net Outlays $0 ` BW7 FOIA CBP 000094 DHS-17-0046-C-000094 From: To: Subject: Date: Attachments: (b)(6);(b)(7)(C) RE: STATUS SLIDES Friday, January 29, 2010 6:31:11 PM SBInet Update 1-29-10 rev1.ppt - Sir, attached is an update to the slide deck (b)(6);(b)(7)(C) provided with a schedule.  This is still being massaged a bit, that’s why it still is in powerpoint graphic versus IMS format.     As for the MSC, proposals are planned to be due on 1 Mar 2010, predicated on the revised RFP being released by 5 Feb.   Thks   V/r   (b) (7)(E) (b)(6);(b)(7)(C) Deputy Director, Secure Border Initiative Network Phone (b)(6);(b)(7)(C) Mobile Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Friday, January 29, 2010 3:51 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: STATUS SLIDES Based on the MSC RFP update, when do we expect proposals?   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) Sent: Friday, January 29, 2010 2:02 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: STATUS SLIDES - :  Here are the status slides you asked for, plus additional slides for my bi-weekly update.  One note (b)(6);(b)(7)(C) BW7 FOIA CBP 000095 DHS-17-0046-C-000095 on the OIC slide.  There is some minor disagreement over the date that construction will actually be completed.  I’ve given you two slides showing the differing opinions.  I personally think the Oct date is (b)(6);(b)(7)(C) more realistic, is concerned that is we say Oct we will need to update congress as this is a change.       I’m headed out to a meeting with MTCSC Corporation.  I do not plan on coming back to the office this afternoon, but will be available by cell phone if you have any questions on this package.    Thanks       (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security - Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. BW7 FOIA CBP 000096 DHS-17-0046-C-000096 From: To: Cc: Subject: Date: Attachments: (b)(6);(b)(7)(C) Request a John Hopkins University Applied Physics Laboratory (JHU/APL) Electronic Gold (Acquisition Strategy) Review for Monday, January 25, 2010 Wednesday, January 20, 2010 9:41:41 AM (b) (5) , (b)(6);(b)(7)(C)   The SBI Systems Engineering Directorate and SBI Contracts Branch would like to conduct the JHU/APL Gold (Acquisition Strategy) Review electronically on Monday, January 25, 2010.  The JHU/APL Gold Review is for a follow-on IDIQ contract that provides support the SBI Systems Engineering Directorate for technical analysis and research for SBInet testing and evaluation activities.  The current JHU/APL contract ends on February 28, 2010.   The electronic Gold Review process would be as follows:   1. The advisors will be sent the documentation electronically today.    (b)(6);(b)(7)(C) will be provided a hardcopy binder for their review tomorrow. 2. The advisors will have until COB Friday, January 22, 2010 to review and make their recommendation 3. AMD will consolidate the inputs and provide them to for a decision (b)(6);(b)(7)(C) on Monday, January 25, 2010. 4. AMD has verified the entrance criteria for the Gold Review has been met.   Note:  Although the execution of the review board will be done electronically; advisors are encouraged to make phone calls or meet face to face (if necessary); as long as they are able to provide their input to AMD by COB Friday, January 22, 2010.   Please advise if you are agreeable to the recommended sequence for this Gold Review.   Thank you,   (b)(6);(b)(7)(C) SBI Business Operations Office Contractor supporting the Acquisition Management Division (AMD) Desk Tel: (b)(6);(b)(7)(C) Cell Tel (b)(6);(b)(7)(C) Email: (b)(6);(b)(7)(C)   BW7 FOIA CBP 000097 DHS-17-0046-C-000097 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) RE: SBINET Thursday, January 07, 2010 3:14:59 PM We were able to track him down.  He is just trying to get back up to speed as to where we are coming out of SQT.   We’ll put something together providing him a summary of SQT 2 results and we’ll make sure we provide updates on the top issues that came out of SQT 1.   V/R, - (b)(6);(b)(7)(C)   (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: Sent: Thursday, January 07, 2010 2:52 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBINET (b)(6);(b)(7)(C) Yes, please.   I presume he’s talking about types of things we might identify as limitations, waivers, or deviations…   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:51 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBINET   • and I just chatted and we are not sure what he is specifically talking about.   Would you like for us to give him a shout?   V/R, (b)(6);(b)(7)(C) BW7 FOIA CBP 000098 DHS-17-0046-C-000098 - (b)(6);(b)(7)(C)   (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:46 PM (b)(6);(b)(7)(C) To: Subject: FW: SBINET Do you know what list he’s talking about?   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   (b)(6);(b)(7)(C) From: Sent: Thursday, January 07, 2010 2:45 PM To: (b)(6);(b)(7)(C) Subject: SBINET Could you send me the latest list of SBINET deficiencies? Thanks, 1111 -------------------------(b)(6);(b)(7)(C) Sent from my BlackBerry Wireless Handheld - (b)(6);(b)(7)(C) BW7 FOIA CBP 000099 DHS-17-0046-C-000099 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) RE: SBINET Thursday, January 07, 2010 2:55:13 PM Roger. Pls standby. V/R, - (b)(6);(b)(7)(C) 1111 (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:52 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBINET Yes, please. I presume he’s talking about types of things we might identify as limitations, waivers, or deviations… (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:51 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBINET • and I just chatted and we are not sure what he is specifically talking about. (b)(6);(b)(7)(C) Would you like for us to give him a shout? V/R, (b)(6);(b)(7)(C) 1111 - (b)(6);(b)(7)(C) Director, Systems Engineering BW7 FOIA CBP 000100 DHS-17-0046-C-000100 Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:46 PM (b)(6);(b)(7)(C) To: Subject: FW: SBINET Do you know what list he’s talking about? (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection (b)(6);(b)(7)(C) From: Sent: Thursday, January 07, 2010 2:45 PM To: (b)(6);(b)(7)(C) Subject: SBINET - (b)(6);(b)(7)(C) ] , Could you send me the latest list of SBINET deficiencies? Thanks, -------------------------Sent from my BlackBerry Wireless Handheld - (b)(6);(b)(7)(C) BW7 FOIA CBP 000101 DHS-17-0046-C-000101 From: To: (b)(6);(b)(7)(C) Cc: Subject: Attachments: (b) (7)(E) Group 1 Tower CRR NON-RESPONSIVE When: Thursday, January 21, 2010 8:00 AM-4:30 PM (GMT-07:00) Arizona. Where: Conf Rm 50-530.2, Conf Rm 237 Note: The GMT offset above does not reflect daylight saving time adjustments. *~*~*~*~*~*~*~*~*~* Enter through the 510 main lobby(east end), head to west end and down the stairs.  Cross the courtyard and enter the 530.  Go up to the second floor and the conference room is in the SE corner. , - If we have left anyone off that you think should be invited to this CRR please contact (b)(6);(b)(7)(C) and he will send a meeting notice to them.  Thank You TOPIC: (b) (7)(E) Group 1 Tower CRR DATE: Thursday, January 21, 2010 TIME: 7:00 am, Mountain Standard Time (GMT -07:00, Arizona) 1. Audio conference (b) (7)(E) 2. WebEx meeting (b) (7)(E) WebEx site: Meeting number: (b) (7)(E) Meeting password: (b) (7)(E) Join meeting as Attendee: Start meeting as Host: (b) (7)(E) (b) (7)(E) 3. Host Key for Alternate Hosting - Only send the host key to your alternate host. Do not send the host key to other attendees. Host Key:(b) (7)(E) BW7 FOIA CBP 000102 DHS-17-0046-C-000102 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) RE: SBINET Thursday, January 07, 2010 3:16:01 PM Thank you!   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 3:14 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBINET We were able to track him down.  He is just trying to get back up to speed as to where we are coming out of SQT.   We’ll put something together providing him a summary of SQT 2 results and we’ll make sure we provide updates on the top issues that came out of SQT 1.   V/R, - (b)(6);(b)(7)(C)   (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:52 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBINET Yes, please.   I presume he’s talking about types of things we might identify as limitations, waivers, or deviations…   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000103 DHS-17-0046-C-000103   From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:51 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBINET   • and I just chatted and we are not sure what he is specifically talking about.   Would you like for us to give him a shout?   V/R, (b)(6);(b)(7)(C) -- (b)(6);(b)(7)(C)   (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 2:46 PM (b)(6);(b)(7)(C) To: Subject: FW: SBINET Do you know what list he’s talking about?   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   (b)(6);(b)(7)(C) From: Sent: Thursday, January 07, 2010 2:45 PM To: (b)(6);(b)(7)(C) Subject: SBINET - (b)(6);(b)(7)(C) ] , Could you send me the latest list of SBINET deficiencies? Thanks, -------------------------Sent from my BlackBerry Wireless Handheld - (b)(6);(b)(7)(C) BW7 FOIA CBP 000104 DHS-17-0046-C-000104 From: To: Subject: (b)(6);(b)(7)(C) SBInet Planning Meeting When: Thursday, January 21, 2010 11:00 AM-1:00 PM (GMT-05:00) Eastern Time (US & Canada). Where: 1901 S. Bell St (Crystal City), Room 624 *~*~*~*~*~*~*~*~*~* Just a follow up to be snure everyone has details about meeting location. You can call my assistant, (b)(6);(b)(7)(C) when you arrive--she will meet you in the lobby to provide access to the 6th floor. My phone is (b)(6);(b)(7)(C) if you need it. See you at 11:00! BW7 FOIA CBP 000105 DHS-17-0046-C-000105 From: To: Cc: Subject: Date: Attachments: (b)(6);(b)(7)(C) FW: S1"s comments on SBI Technology Memo Thursday, January 07, 2010 3:46:17 PM 20095968.WF.850830.pdf FYI. Note suspense of mid-Janaury from S1… (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 3:35 PM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: FW: S1's comments on SBI Technology Memo Sir, See S1’s comments regarding the SBI Technology Programs memo attached. Thanks!! (b)(6);(b)(7)(C) SBI Exec. Sec. (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 3:25 PM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: S1's comments on SBI Technology Memo SBI Team: We just got the attached back from the Dept. - Please provide a copy of this to (b)(6);(b)(7)(C) – as S1 made comments on a memo that he drafted about the future for SBI tech programs. Please call S1’s comments to his attention – they are on the last page of the attached…thank you! VR, - (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Director, Executive Secretariat Office of the Commissioner U.S. Customs and Border Protection office: (b)(6);(b)(7)(C) cell: (b)(6);(b)(7)(C) BW7 FOIA CBP 000106 DHS-17-0046-C-000106 J, ,)f..,Ii/.-/;~, "A..,j 1 '" J S sw'-<,1,.:,:,-• ,,.,..; f L~ ~L c1ce:J:"'--- n.uj f i~ ,._,,1., ~~,.,/c~. ,.,1,t;,I-~(b) (6) 1 j,,.·r·C I;I«leL/,• (.. c1tt/'7'" ~c. /)It? t- t-.;.../ ....:--. _..5o"""-t:5ocJ-.... ,,.,..,~ tr ll t? 6 - ;;:;::, Y ci }i>, rei) P/ Ol ,4, ,..i OL A I ~ £.. L. .:>t--,._ j j j 0 ~~JJ IitJd,c.l Q/~'r...c..f{,.. /, ,+/ j. J,-...__ ;- l".....,7,.___,+ I i-. jl1e-t:7 e-J'/I f"fA..c.- ,. ~ c-.7!d::-J''u- ,_ ..,.,_c_•7_ h.,:,. f._. ~,... jl fL. .J . . II>>:,. (,.: t,.,: It It :Jc-.c-. bc.).:, h rr 1, f 1±- ~~ L.Lf,,_.,. ,, ..C>"'-~c,'"t, c. Co _f.,,.,.. f<>,,~ .:7:J /. /44._ -1 i!.~ ;; -,) 1 t:,:, ,._t-7-. '"....,i.7 '-j /,; ~ -_ ..(c.hLL.! .r<./4.i.LJ. f,o>~.;;, «'J f&,.,•.J....&,/-tc.../ ffp/t. ~ . ~ .- /)/) ••0.).)J..) .'.-~~ l_ . j 55 j j IL.) r. lr'- --ss; ; j j j j j j j j j BW7 FOIA CBP 000111 DHS-17-0046-C-000111 j ------------(b)(6);(b)(7)(C) From: Sent: To: Subject: (b)(6);(b)(7)(C) Thursday, January 21, 2010 8:10 AM (b)(6);(b)(7)(C) Accepted: SBInet Planning Meeting   1 BW7 FOIA CBP 000112 DHS-17-0046-C-000112 (b)(6);(b)(7)(C) From: To: Subject: Next Steps for SBInet When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 - *~*~*~*~*~*~*~*~*~* .-- - To discuss the path forward for SBI after the (b) (7)(E) and (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) briefing given to Chief and Chief (b)(6);(b)(7)(C)n December.  POC:  (b)(6);(b)(7)(C) .  Calendared by BW7 FOIA CBP 000113 DHS-17-0046-C-000113 (b)(6);(b)(7)(C) From: To: Subject: Date: RE: S1"s comments on SBI Technology Memo Thursday, January 07, 2010 4:41:10 PM Boss; Do you want a quick meeting to discuss actions on this? (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 3:46 PM To: ICc: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Subject: FW: S1's comments on SBI Technology Memo FYI. Note suspense of mid-Janaury from S1… (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 3:35 PM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: FW: S1's comments on SBI Technology Memo Sir, See S1’s comments regarding the SBI Technology Programs memo attached. Thanks!! (b)(6);(b)(7)(C) SBI Exec. Sec. (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 3:25 PM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: BW7 FOIA CBP 000114 DHS-17-0046-C-000114 Subject: S1's comments on SBI Technology Memo SBI Team: We just got the attached back from the Dept. - Please provide a copy of this to (b)(6);(b)(7)(C) – as S1 made comments on a memo that he drafted about the future for SBI tech programs. Please call S1’s comments to his attention – they are on the last page of the attached…thank you! VR, - (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Secretariat Office of the Commissioner U.S. Customs and Border Protection office: (b)(6);(b)(7)(C) cell: (b)(6);(b)(7)(C) BW7 FOIA CBP 000115 DHS-17-0046-C-000115 From: To: Cc: Subject: Date: - (b)(6);(b)(7)(C) Re: Napolitano announcement on SBInet reassessment Saturday, January 09, 2010 6:45:23 PM , Really appreciate the heads up! It turns out that DHS did reach out to senior folks in Boeing and the message is consistent w/ yours. (b)(6);(b)(7)(C) Concur that the next few days (weeks?) will be "interesting". I, too, love this job! But, we remain (b)(6);(b)(7)(C)ed to getting it done right. (b)(6);(b)(7)(C) From: To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Sent: Sat Jan 09 13:43:58 2010 Subject: Re: Napolitano announcement on SBInet reassessment No. A lot will depend on how the Department assesses the actual 60 Minutes piece and reaction. - I understand they are engaging with (b)(6);(b)(7)(C) and have offered to follow up with him. (b)(6);(b)(7)(C) From: To: (b)(6);(b)(7)(C) Cc: > (b)(6);(b)(7)(C) , (b)(6);(b)(7)(C) Sent: Sat Jan 09 14:34:30 2010 Subject: RE: Napolitano announcement on SBInet reassessment 1111 (b)(6);(b)(7)(C) Thanks for the SA, had not yet heard of the Secretary's announcement.  Let us know if there is anything we can do or need to start pulling together to help you with the re-assessment.  Is there a target completion date? •   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) From: Sent: Saturday, January 09, 2010 2:28 PM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: Napolitano announcement on SBInet reassessment Folks-Yesterday afternoon, Secretary Napolitano released a statement to 60 Minutes indicating she had directed DHS to BW7 FOIA CBP 000116 DHS-17-0046-C-000116 conduct a re-assessment of SBInet in light of continued delays. We actually didn't have much notice of the statement, although its contents are entirely consistent with discussions we've had before. I understand the Department has reached out to the highest levels of Boeing to inform them of the statement. Don't know if you'd heard--but if not, wanted to ensure you were aware. Should be an interesting few days. I love this job. R/ (b)(6);(b)(7)(C) BW7 FOIA CBP 000117 DHS-17-0046-C-000117 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: RE: SBInet Meeting Friday, January 22, 2010 11:05:09 AM Absolutely. I will connect with everyone later today to set up a time that works. - (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) (cell) (b)(6);(b)(7)(C) From: Sent: Friday, January 22, 2010 10:59 AM To: ] (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBInet Meeting — 1111 (b)(6);(b)(7)(C) - As we discussed last week, our small group met yesterday to sketch out a structure for the review. I think wanted to have a quick follow-up so he could stay apprised of status and direction. Is that something you can orchestrate? (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000118 DHS-17-0046-C-000118 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) Re: Initial direction for our OA strategy Monday, January 11, 2010 3:01:20 PM Team, The following is the response to our initial OA direction from the boss: "I think that’s pretty solid.  You capture it, but I want to try to keep focus on leveraging existing commercial (or government) systems and avoid as much as possible any significant OA developmental activity". So we are good to go and will be moving out quickly..  By the way I responded back to the boss stating that I would re-emphasize his COTS/GOTS statement by modifying the 2nd near-term execution statement as follows: "Procure a COTS or GOTS solution, or multiple solutions, for test and evaluation" - Thanks to all who provided comments. (b)(6);(b)(7)(C) ------Original Message-----From: (b)(6);(b)(7)(C) To: Cc: Cc: Cc: Cc: Cc: Sent: Jan 7, 2010 16:34 Subject: Initial direction for our OA strategy (b)(6);(b)(7)(C) Good afternoon Boss, Had an internal SBI session to discuss the latest OA thoughts bouncing around the 6th/7th floor. It was a very good session.  However, before we move further down a specific path, the group thought that we needed to have some direction from you as to where we are heading so that, ultimately, we could develop a detailed OA strategy.    To that end, I came up with the following (which was chopped through the group) as our initial direction.  Please take a look and let me know if we hit the mark.  Once I get your tweaks and/or concurrence, I will move out and begin putting meat to the bones.  By the way, I initially had this as a CBP vision – it was scaled back to an SBI vision – but I still think we may want to take this on at the CBP level given the expected CBP reorg. BW7 FOIA CBP 000119 DHS-17-0046-C-000119 V/R, (b)(6);(b)(7)(C) ----------------- As the industrial base transitions into designing, developing, and producing open architected technological products, SBI is transitioning its acquisition and procurement strategies to take advantage of those open architected technological products to yield modular, interoperable systems that adhere to open standards with published interfaces.  This approach significantly increases opportunities for innovation and competition, enables reuse of components and technologies from a broad range of industry partners, facilitates rapid technology insertion, and reduces maintenance constraints.  SBI’s Open Architecture Vision Transform SBI’s organization and culture and align resources to adopt and institutionalize open architecture principles and processes in order to deliver more capability to the agents and officers in the field faster and at reduced costs. Open Architecture Principles (tailored to meet SBI vision): 1.  Encourage the building of modular designs and disclosure of data to permit evolutionary designs, technology insertion, competitive innovation, and alternative competitive approaches from multiple qualified sources 2.  Encourage competition and collaboration through the identification of alternative solutions and sources. . 3.  Encourage the building of interoperable applications and web services and ensure secure information exchange using common services (e.g. common time reference), common operator applications (e.g. track manager) and information assurance as intrinsic design elements. 4.  Identify reusable application software selected through open competition of ‘best of breed’ candidates, reviewed by subject matter expert peers and based on data-driven analysis and experimentation to meet operational requirements while improving the overall integration of mission capabilities. BW7 FOIA CBP 000120 DHS-17-0046-C-000120 5.  Ensure life cycle affordability including system design, development, delivery, and support while mitigating obsolescence by exploiting the Rapid Capability Insertion Process. Near-term Strategy: Procure an open architected Commercial Off the Shelf (COTS) Common Operational Picture (COP) as a SBI commodity buy that could replace, or begin to replace, the current SBInet Block 1 COP and be used as the next generation COP to meet existing and future SBInet requirements as well as other SBI project requirements.  Near-term Execution: Develop an RFP using special contract requirements that describe the use of open software and other key data for use by contractors in bidding on this new procurement for which open-architecture compliance is a requirement. Procure a solution, or multiple solutions, for test and evaluation (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. Director, Systems Engineering US Customs and Border Protection Secure Border Initiative (b)(6);(b)(7)(C) BW7 FOIA CBP 000121 DHS-17-0046-C-000121 Sent from my Blackberry BW7 FOIA CBP 000122 DHS-17-OO46-C-000122 (b)(6);(b)(7)(C) From: To: Subject: Date: RE: Initial direction for our OA strategy Monday, January 11, 2010 2:00:33 PM Roger. I will re-emphasize your COTS/GOTS statement by modifying the 2nd near-term execution statement as follows: Procure a COTS or GOTS solution, or multiple solutions, for test and evaluation V/R, (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Monday, January 11, 2010 1:56 PM To: (b)(6);(b)(7)(C) Subject: RE: Initial direction for our OA strategy   Thanks, . I think that’s pretty solid. You capture it, but I want to try to keep focus on leveraging existing commercial (or government) systems and avoid as much as possible any significant OA developmental activity. 1111 (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection    From: (b)(6);(b)(7)(C) Sent: Monday, January 11, 2010 1:54 PM To: (b)(6);(b)(7)(C) Subject: FW: Initial direction for our OA strategy   Boss, Resent to get it to the top of your email queue. V/R, (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) BW7 FOIA CBP 000123 DHS-17-0046-C-000123 U.S. Customs and Border Protection (b)(6);(b)(7)(C)   Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Thursday, January 07, 2010 4:35 PM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: Initial direction for our OA strategy   Good afternoon Boss,   Had an internal SBI session to discuss the latest OA thoughts bouncing around the 6th/7th floor.   It was a very good session.  However, before we move further down a specific path, the group thought that we needed to have some direction from you as to where we are heading so that, ultimately, we could develop a detailed OA strategy.       To that end, I came up with the following (which was chopped through the group) as our initial direction.  Please take a look and let me know if we hit the mark.  Once I get your tweaks and/or concurrence, I will move out and begin putting meat to the bones.    By the way, I initially had this as a CBP vision – it was scaled back to an SBI vision – but I still think we may want to take this on at the CBP level given the expected CBP reorg.   V/R, - (b)(6);(b)(7)(C)   ----------------  As the industrial base transitions into designing, developing, and producing open architected technological products, SBI is transitioning its acquisition and procurement strategies to take advantage of those open architected technological products to yield modular, interoperable systems that adhere to open standards with published interfaces.  This approach significantly increases opportunities for innovation and competition, enables reuse of components and technologies from a broad range of industry partners, facilitates rapid technology insertion, and reduces maintenance constraints.    SBI’s Open Architecture Vision   Transform SBI’s organization and culture and align resources to adopt and institutionalize open architecture principles and processes in order to deliver more capability to the agents and officers in the field faster and at reduced costs.   Open Architecture Principles (tailored to meet SBI vision):   1.  Encourage the building of modular designs and disclosure of data to permit evolutionary designs, BW7 FOIA CBP 000124 DHS-17-0046-C-000124 technology insertion, competitive innovation, and alternative competitive approaches from multiple qualified sources   2.  Encourage competition and collaboration through the identification of alternative solutions and sources. . 3.  Encourage the building of interoperable applications and web services and ensure secure information exchange using common services (e.g. common time reference), common operator applications (e.g. track manager) and information assurance as intrinsic design elements.   4.  Identify reusable application software selected through open competition of ‘best of breed’ candidates, reviewed by subject matter expert peers and based on data-driven analysis and experimentation to meet operational requirements while improving the overall integration of mission capabilities.   5.  Ensure life cycle affordability including system design, development, delivery, and support while mitigating obsolescence by exploiting the Rapid Capability Insertion Process.   Near-term Strategy:   Procure an open architected Commercial Off the Shelf (COTS) Common Operational Picture (COP) as a SBI commodity buy that could replace, or begin to replace, the current SBInet Block 1 COP and be used as the next generation COP to meet existing and future SBInet requirements as well as other SBI project requirements.     Near-term Execution:   Develop an RFP using special contract requirements that describe the use of open software and other key data for use by contractors in bidding on this new procurement for which openarchitecture compliance is a requirement.   Procure a solution, or multiple solutions, for test and evaluation (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C)   Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes.   BW7 FOIA CBP 000125 DHS-17-0046-C-000125 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: Attachments: Importance: FW: ACTION: GAO response RE: nPRS & Acquisition Decision Memorandum (ADM) Action Items Friday, January 22, 2010 6:19:35 PM 2010 Jan 22 Major Acq Pgm Weekly Rpt.pdf High PMs,   Per the email below, this is a heads up that you should be hearing from your respective CAEs or Component Acquisition Staffs regarding response to a GAO information request on your major acquisition program.  The request involves reviewing your nPRS program/project data and updating outstanding ADM action item status (in the attached Major Acquisition Program weekly report).   Your support and timely response to this GAO request is greatly appreciated.   Regards,   (b)(6);(b)(7)(C) Acquisition PM Division (APMD) Department of Homeland Security Office of the Chief Procurement Officer Washington, DC  20528    Phone Email: (b)(6);(b)(7)(C) - From: (b)(6);(b)(7)(C) Sent: Friday, January 22, 2010 5:56 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: FW: ACTION: GAO response RE: nPRS & Acquisition Decision Memorandum (ADM) Action Items Importance: High CAEs/Component Acquisition Support Staffs: 1. To follow up on this past week’s Program Management Council (PMC) meeting of 20 January, I am asking for your support in responding to two actions tasked to DHS from a recent GAO information request: a. The first action requests an updated status of Acquisition Decision Memorandum (ADM) action items (AI), and a summary statement from DHS identifying factors that have prevented implementation of the ADM AI within the established timelines. b. The second action requests the most recent nPRS monthly summary for each of the BW7 FOIA CBP 000126 DHS-17-0046-C-000126 programs being reviewed by the GAO in their ongoing major program review. 2. ADM action items. Please review your component programs’ outstanding action items and provide APMD with updates on these items, with particular attention paid to overdue action items (for overdue action items, provide an assessment of what prevented on-time accomplishment, and when the action item will be completed). This week’s Major Acquisition Program (MAP) report with open ADM AI’s is forwarded to assist in your (b)(6);(b)(7)(C) response. Please provide the Component response to (b)(6);(b)(7)(C) copy to by COB 1 February 2010. 3. nPRS Program Reports. GAO has requested an updated nPRS report be provided at a program/project level for the following programs currently under review in the ongoing GAO review of major DHS programs: CBP ACE SBInet TECS MOD WHTI NPPD NCPS US-VISIT OHA Biowatch TSA EBSP PSP SF USCG C4ISR FRC MPA NSC R21 RB-M To ensure that the most up-to-date data is provided to GAO on the programs identified above, please ensure that the Program Manager reviews (and updates, as necessary) the nPRS data for his program/project set. Please provide positive confirmation of this review for all affected (b)(6);(b)(7)(C) programs/projects in your component to nPRS lead, with copy to (b)(6);(b)(7)(C) by COB 1 February 2010. 4. If you have any questions please feel free to contact me or my staff. Thank you for your cooperation and quick response on this important matter. -    (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Director, Acquisition PM Division (APMD) Department of Homeland Security Office of the Chief Procurement Officer Washington, DC  20528    Phone:   Email:  (b)(6);(b)(7)(C) BW7 FOIA CBP 000127 DHS-17-0046-C-000127 -t ·•·"'" ?. H ome 1an d '. Security Data as of 1/22/2010 Major Acquisition Program Weekly Executive Report Acquisition Program Management Division Status of Component Acquisition Portfolios Number of Major Component Acquisition Programs Percent with Certified PM Percent Reporting to nPRS Acquisition Program Baselines Number Approved Number Submitted Number In Preparation Number Not Needed 0 14 0 NON-RESPONSIVE CBP 16 81% 78% 2 NON-RESPONSIVE Acquisition Review Board (ARB) Upcoming Schedule NON-RESPONSIVE NON-RESPONSIVE BW7 FOIA CBP 000128 DHS-17-0046-C-000128 1 -t ·•·"'" ?. H ome 1an d '. Security Data as of 1/22/2010 Major Acquisition Program Weekly Executive Report Acquisition Program Management Division Status of Acquisition Decision Memorandum (ADM) Action Items Component Program ADM Date Actions Assigned Actions Completed Actions Overdue NON-RESPONSIVE CBP SBI TI & SBInet 8-Sep-08 10 10 0 NON-RESPONSIVE CBP SBInet 11-Feb-09 12 3 0 NON-RESPONSIVE CBP SBInet 26-May-09 2 0 1 NON-RESPONSIVE CBP SBInet 6-Sep-09 2 1 1 NON-RESPONSIVE BW7 FOIA CBP 000129 DHS-17-0046-C-000129 2 ~ ,~ 1 Homeland Data as of 1/22/2010 Major Acquisition Program Weekly Executive Report i) Security Acquisition Program Management Division Overdue Acquisition Decision Memorandum (ADM) Action Items Component Program Acronym ADM Date Action Item Action Lead Action Item Due Date Status (b) (7) (E) NON-RESPONSIVE (b) (7) (E) (7)(E) (b) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7) (b) (7)(E) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E ) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7) (E) BW7 FOIA CBP 000130 DHS-17-0046-C-000130 3 ~ ,~ 1 Homeland Data as of 1/22/2010 Major Acquisition Program Weekly Executive Report i) Security Acquisition Program Management Division Component Program Acronym ADM Date Action Item Action Lead Action Item Due Date Status NON-RESPONSIVE (b) (7)(E) CBP TACCOM 24-Sep-09 (b) (7) (E) (b) (7) (E) (b) (7) (E) Provide USM with detailed plan to mitigate O&M funding shortfalls CBP 15-Oct-09 (b (b) (b ) (7) ) (7 (E) (7 )(b ) (E ) (E )(7 ) 2010 )TACCOM FYHSP now contains O&M funding for FY and 2011. Funding is from SBInet BSFIT funds. (E (b) ) (b (7) ) (E) (7 ) (E Not submitted )as of 22-Jan-2010 NON-RESPONSIVE (b) (7) (E) CBP SBInet 26-May-09 (b) (7) (E) (b) (b) (7) (7) Develop and approve an addition to SBInet differences (E)TEMP for AJO-1 (E) SBI PM 26-Aug-09 (b) (7) (E) NON-RESPONSIVE (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7) (E) BW7 FOIA CBP 000131 DHS-17-0046-C-000131 4 ~ ,~ 1 Homeland Data as of 1/22/2010 Major Acquisition Program Weekly Executive Report i) Security Acquisition Program Management Division Component Program Acronym ADM Date Action Item Action Lead Action Item Due Date Status NON-RESPONSIVE (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7) (E) (b) (7) (b) (E) (7) (E) (b) (7) (E) (b) (7) (E) (b) (7)(E) (b) (7)(E) BW7 FOIA CBP 000132 DHS-17-0046-C-000132 5 ~ ,~ 1 Homeland Data as of 1/22/2010 Major Acquisition Program Weekly Executive Report i) Security Acquisition Program Management Division Component (b) (7) (E) Program Acronym ADM Date Action Item Action Lead Action Item Due Date Status NON-RESPONSIVE BW7 FOIA CBP 000133 DHS-17-0046-C-000133 6 (b)(6);(b)(7)(C) From: To: Subject: SBInet When: Friday, January 29, 2010 2:00 PM-3:00 PM (GMT-05:00) Eastern Time (US & Canada). Where: (b) (7)(E) *~*~*~*~*~*~*~*~*~* BW7 FOIA CBP 000134 DHS-17-0046-C-000134 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: ; RE: SBInet Meeting Monday, January 25, 2010 8:34:06 AM With a little juggling, I could be available:   - All day Tuesday - Wednesday afternoon between 1:00 and 4:00 - Thursday afternoon after 1:00 - Friday afternoon after 1:00       (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   (b)(6);(b)(7)(C) From: ] Sent: Friday, January 22, 2010 6:14 PM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject: RE: SBInet Meeting Hello everyone,   I will reach out on Monday to schedule this meeting for next week.  If anyone has days that you know will absolutely not work for the meeting just let me know when you have a chance and I will work around it.  Have a great weekend!   (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) cell) (b)(6);(b)(7)(C) From: Sent: Friday, January 22, 2010 10:59 AM To: ] (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBInet Meeting — 1111   (b)(6);(b)(7)(C) - As we discussed last week, our small group met yesterday to sketch out a structure for the review.  I think wanted to have a quick follow-up so he could stay apprised of status and direction.  Is that something you can orchestrate?   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) BW7 FOIA CBP 000135 DHS-17-0046-C-000135 Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000136 DHS-17-0046-C-000136 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: RE: SBInet Meeting Saturday, January 23, 2010 1:34:55 PM 1111 Monday, Wednesday and Thurs before 3pm are bad for me, but all day Tues, Thurs afternoon and Friday (b)(6);(b)(7)(C) - are goo.  Thanks... (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) - Director, DHS Test and Evaluation and Standards Division Department of Homeland Security (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) From: ] Sent: Friday, January 22, 2010 6:14 PM (b)(6);(b)(7)(C) To: Cc: Subject: RE: SBInet Meeting (b)(6);(b)(7)(C) Hello everyone,   I will reach out on Monday to schedule this meeting for next week.  If anyone has days that you know will absolutely not work for the meeting just let me know when you have a chance and I will work around it.  Have a great weekend!   -- (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) From: Sent: Friday, January 22, 2010 10:59 AM To: ] (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: SBInet Meeting — 1111   (b)(6);(b)(7)(C) - As we discussed last week, our small group met yesterday to sketch out a structure for the review.  I think wanted to have a quick follow-up so he could stay apprised of status and direction.  Is that something you can orchestrate?   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000137 DHS-17-0046-C-000137 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) FW: Additional questions for DHS Tuesday, January 26, 2010 11:47:18 AM FYI – See below for OLA’s response to an inquiry regarding the “DHS-wide review” of SBInet…   (b)(6);(b)(7)(C) From: Sent: Tuesday, January 26, 2010 11:13 AM To: (b)(6);(b)(7)(C) Subject: Fw: Additional questions for DHS     (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) To: Sent: Tue Jan 26 10:35:43 2010 Subject: FW: Additional questions for DHS > - FYI – Session’s office asked about SBInet and there are a number of minority staffers included on the email chain.  I wanted to make sure you saw (b)(6);(b)(7)(C) response.   (b)(6);(b)(7)(C) 1111   (b)(6);(b)(7)(C) From: Sent: Tuesday, January 26, 2010 9:36 AM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: RE: Additional questions for DHS   - Hey – the Department is not changing the view that technology is a critical component of our border security efforts, but there are some long-standing issues with SBI net as it was initially designed.  As you know, the program has yet to meet any of the deadlines, and it was actually supposed to be fully deployed by now.  In fact, there is no near-term, reliable deadline for deployment.  As such, our agents don’t have – nor will they have anytime soon - this critical tool on the border.   In order to get technology on the border as quickly and efficiently as possible, the Secretary has ordered this Department wide re-assessment to bring in all of the expertise of the Department, e.g., Science and Technology, Management, other components, etc. to make sure the project as it has been designed and configured is, in fact, the best way to get technology on the border.  We should have some more information to put out on the scope of the review and timeline shortly.   The Secretary remains consistent in the view that DHS should be aggressive in its pursuit of technology on the border.   (b)(6);(b)(7)(C)     (b)(6);(b)(7)(C) - (b)(6);(b)(7)(C) From: Sent: Monday, January 25, 2010 8:10 PM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: ] BW7 FOIA CBP 000138 DHS-17-0046-C-000138 (b)(6);(b)(7)(C) Subject: RE: Additional questions for DHS   , et al. Many thanks for the briefing this morning.  It was quite helpful. On a somewhat different topic, can anyone at DHS HQ shed a little more light on the news item below regarding SBINet?  What is the significance of the Secretary’s call for a “department-wide reassessment” following on the heels of CBP’s implementation review?  The scope of the review, and labeling it a “reassessment,” seems to suggest something more than a study for ways to improve design or execution.  Is the Department considering cancellation of the SBINet project?   Napolitano orders SBInet reassessment Electronic border fence has 'unacceptable delays' By Alice Lipowicz Jan 22, 2010 Homeland Security Secretary Janet Napolitano has ordered a reassessment of the $8 billion SBInet virtual border fence program in Arizona after another round of delays in the program, an official confirmed today. Boeing Co. is the prime contractor on the project. SBInet is an electronic surveillance system composed of cameras, radars and other sensors strung on towers and coordinated with other sensor systems, communications and command and control networks. U.S. Customs and Border Protection recently has been deploying a 23-mile segment of the system near Tucson, Ariz. Napolitano requested the SBInet reassessment Jan. 8 after an internal evaluation revealed “unacceptable delays” in the program, according to a Jan. 11 e-mail message from Napolitano provided today by Matthew Chandler, a Homeland Security Department spokesman. Although the message did not state the extent of the delays, the Seattle Times recently reported that the initial operational segment, known as Tucson-1, would be three months late in beginning operation. Instead of beginning operation at the end of 2009, the operation has been delayed to March 2010, the newspaper said. Napolitano indicated in her message that SBInet continues to fall short of expectations. “Americans need border security now — not 10 years down the road. I am committed to ensuring that our border security programs are timely and cost-effective,” Napolitano wrote. “This fall, due to my ongoing concerns about SBInet, I directed the acting commissioner of U.S. Customs and Border Protection to evaluate its implementation. As his analysis uncovered unacceptable delays, last Friday I ordered a department-wide reassessment of the program to consider options that may more efficiently, effectively and economically meet our border security needs,” Napolitano wrote. Mark Borkowski, project manager for the Secure Border Initiative, which includes SBInet and other fencing programs, told Federal News Radio recently that the next segment of the project, Ajo-1, will be built as scheduled, but Boeing will not begin any new work until the reassessment is completed. Boeing got the initial SBInet contract in September 2006, and first built an 18-mile prototype of the system near Sasabe, Ariz. The border patrol has been using that prototype segment in its daily operations to protect against border incursions since it was accepted by DHS in February 2008. Borkowski a year ago said the system was undergoing additional testing before permanent construction would begin.     (b)(6);(b)(7)(C)   BW7 FOIA CBP 000139 DHS-17-0046-C-000139 --------------(b)(6);(b)(7)(C) From: Sent: To: Subject: - (b)(6);(b)(7)(C) Tuesday, January 26, 2010 7:29 AM (b)(6);(b)(7)(C) Accepted: SBInet   1 BW7 FOIA CBP 000140 DHS-17-0046-C-000140 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) RE: SCHEDULE CONFLICTS Tuesday, January 05, 2010 12:21:04 PM OK. I’ll look at possibly moving it to Thursday of next week. It looks like you’re open that afternoon. We’ll have to get the word out right away. - (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Tuesday, January 05, 2010 12:19 PM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: RE: SCHEDULE CONFLICTS I may have a conflict with the award fee, as well—so perhaps we should reschedule it. (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(C) Sent: Tuesday, January 05, 2010 12:18 PM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: SCHEDULE CONFLICTS ) - : I was just notified that the ARRA execution briefing to USM that was postponed from 21 Dec (b)(6);(b)(7)(C) because of the weather is now scheduled for the 12th at 2:00. That means I will not be able to attend the C3I award fee board. I was also notified that the monthly meeting of the CBP Efficiency Review Steering Committee is on the 13th from 1:00 to 2:00. I’ll leave the JPMR when we break for lunch, attend the meeting, and then return to the JPMR. Thanks (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security BW7 FOIA CBP 000141 DHS-17-0046-C-000141 Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. BW7 FOIA CBP 000142 DHS-17-0046-C-000142 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: RE: Draft SBI SED Overview sjk 5 Jan 10.pptx Tuesday, January 05, 2010 12:33:47 PM Thanks .  I think from an overall conceptual standpoint we’re in alignment, but there are several detailed areas that need further discussion.        1111 (b)(6);(b)(7)(C) - (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Tuesday, January 05, 2010 10:49 AM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: Draft SBI SED Overview sjk 5 Jan 10.pptx - (b)(6);(b)(7)(C)   As you go forward to introduce your new organization to your team tomorrow, I wanted to offer you both a chance to view what I believe are SBI SE’s vision and mission.   Understanding the SE perspective may provide a little more clarity in understanding the grey areas between my organization and yours OR may be the catalyst for follow-on discussions.   The attached is still work in progress but believe I am near 80% complete.   Thanks, - (b)(6);(b)(7)(C)   (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. - (b)(6);(b)(7)(C) BW7 FOIA CBP 000143 DHS-17-0046-C-000143 Office of Administration U.S. Customs and Border Protection (b)(6);(b)(7)(C)(office) cell) BW7 FOIA CBP 000144 DHS-17-0046-C-000144 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) RE: CBP BUR Activity List and initial feedback from DHS PA&E Tuesday, January 05, 2010 12:41:02 PM I don’t think so—at least, not at the moment.  I just wanted you to have the SA…   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) Sent: Tuesday, January 05, 2010 12:39 PM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: RE: CBP BUR Activity List and initial feedback from DHS PA&E Do you need anything from us to support the meeting with Budget?      - (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Tuesday, January 05, 2010 11:14 AM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject: FW: CBP BUR Activity List and initial feedback from DHS PA&E FYI…   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) Sent: Tuesday, January 05, 2010 11:14 AM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject: FW: CBP BUR Activity List and initial feedback from DHS PA&E BW7 FOIA CBP 000145 DHS-17-0046-C-000145 Enclosed is the feedback we have received from DHS PA&E on our BUR activities list. The comments are long and a bit of a mixed bag (looks like there were a few analysts providing comments). Budget will be providing general comments but CBP will need to have comments/counter proposal back to DHS by COB Friday. As you can see from the email below we have reached out to some of the other components to get some intel on what they have gotten in terms of comments. This may help guide us, but even if it is not fruitful, Budget will be providing comments back to DHS on Friday. As you will see from the comments, while there are some concerns about OFO’s activities and the granularity, they recognize that this has been driven by the fees. They also recommend we look at the activities in the statement of net cost, and see what can be used from there to add detail. Short answer is I don’t think we will have much work to develop comments/counter proposals for OFO. For OIOC, OBP, SBI and OAM the task is more complicated. DHS has offered a number of options, some of which may work and some may not and/or may conflict with each other. Budget would like to meet with OBP at a minimum and possibly OBP, SBI and OAM together to discuss any recommendations on an alternative approach.  We will be reaching out to OBP (probably Wednesday) to set up a meeting which will hopefully work with OAM and SBI’s schedule. For OIOC we will reach out to you separately to discuss your thoughts. The only option not on the table is to ignore DHS completely. We would like your input but budget will be addressing their concerns with or without your support. We need to have an approach which works for all of CBP, but is consistent with how we do business. We look forward to sitting down and discussing this with you. Thanks, (b)(6);(b)(7)(C) Executive Director for Budget Office of Administration U.S. Customs and Border Protection (b)(6);(b)(7)(C) (office) cell) From: (b)(6);(b)(7)(C) Sent: Tuesday, January 05, 2010 9:07 AM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: CBP BUR Actvity List and initial feedback from DHS PA&E Happy New Year Fellow Budget OfficersI am enclosing DHS’s initial feedback on the activities list for the BUR for CBP. There are a number of comments, and it looks like CBP, ICE, TSA and USCG will be pulled together to address some come activities. If it all possible, I would like to get together this week (in person or on the phone) to understand how your organizations are moving forward and to share our thoughts. If you feel comfortable, we would love to see the comments on your activities. This is not so much to feel better about what we have done (ok, maybe just a little) but to understand DHS’s approach across the board. One of the comments we have received BW7 FOIA CBP 000146 DHS-17-0046-C-000146 is that our activities list is not granular enough. It would be great to know if you have received similar feedback and/or how you are going to respond. It may be helpful for us to collaborate more frequently as we move forward, but we can discuss when we meet this first time. We will be sending you an invite to a meeting/call-in for Tuesday or Wednesday. If there is a time that is particularly bad, please let us know. I am copying the CBP BUR leads. Please let us know if there are people on your staffs that should be included. Thanks, (b)(6);(b)(7)(C) Executive Director for Budget Office of Administration U.S. Customs and Border Protection (b)(6);(b)(7)(C) (office) (cell) BW7 FOIA CBP 000147 DHS-17-0046-C-000147 From: To: Subject: Date: - (b)(6);(b)(7)(C) RE: SBInet Review and Status Friday, January 22, 2010 9:22:53 AM , (b)(6);(b)(7)(C) on travel. I think it is fine for you to handle from here. Just keep us apprised of the when’s and 1what’s. 111isthanks (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Counselor, Office of the Commissioner U.S. Customs and Border Protection (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) Sent: Thursday, January 21, 2010 4:12 PM (b)(6);(b)(7)(C) To: Subject: SBInet Review and Status -- (b)(6);(b)(7)(C) - We had the follow-up meeting with reps from DHS S&T and DHS CPO, as we agreed with (b)(6);(b)(7)(C) last week. We’ve got a sketch of a time-phased way forward for the overall SBInet review based on today’s discussion. wanted to have fairly frequent updates and statuses, at least for the next couple of weeks. We had agreed we would set something up with him and the other participants from last week, once we completed our smaller group meeting (the one we held today). (b)(6);(b)(7)(C) Would you like to take the initiative to schedule a status update with me to handle from here? Thanks, - , or is that something you’d like (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000148 DHS-17-0046-C-000148 (b)(6);(b)(7)(C) From: To: Subject: Date: FW: SBInet Status Tuesday, January 19, 2010 8:53:01 AM Just FYSA.   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(C) ) Sent: Monday, January 18, 2010 8:13 PM (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Subject: RE: SBInet Status - –   The issues that you have identified here are exactly what the review team will be interested in knowing.  Thanks for your candor.  I think you are right in fixing the root problems instead of taking a gamble on the “band aid” fix.   (b)(6);(b)(7)(C) 1111   (b)(6);(b)(7)(C)   From: (b)(6);(b)(7)(C) Sent: Friday, January 15, 2010 8:12 AM To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: Subject: SBInet Status Chief-  Since we didn’t have staff meeting or ESC yesterday, I thought I’d give you a quick update on the current status of SBInet.   As you know, testing will be delayed.  However, we think the basic system that’s constructed in Tucson is (b) (7)(E) pretty good. -I (b) (7)(E) think it would be irresponsible to take full ownership until everything’s done— (b) (7)(E)   Therefore, we are working with Boeing to turn the system over to the Border Patrol for “Initial Operations and Familiarization” (we’re still working on the right terminology but that seems to get the basic message across).  We may be able to do this as soon as January 25.  Over the next months, as we’re waiting to complete testing, the Border Patrol will be able to use the existing system, with support from Boeing as required, on a non-interference basis.  That will generally mean it will be available to support operations (b) (7)(E)   That way, we can take advantage of what we have while we continue to work on cleaning up remaining BW7 FOIA CBP 000149 DHS-17-0046-C-000149 issues.   (b) (5) .  System Acceptance Test (SAT) would be in June or July.  (Operational Test, which would be the OBP evaluation, would follow after SAT—SAT is the test we need before we take ownership of the system from Boeing, and we do Operational testing after we take ownserhsip).   There are a couple of key reasons for these delays.  We think we’ve got a pretty good handle on the system and the things we need to fix—most of which are annoyances.  For example, (b) (7)(E)  Rather than simply “patching” these types of things, we’re actually trying to fix the root cause.  I think that’s smart for the long-term, but it costs time because we have to do the analysis, design the fix, and then actually buy the upgraded system.  For example, (b) (7)(E) there’s time between ordering something and receiving it.  It’s not that the problem is all that hard—it’s just the reality of the time it takes to buy stuff.   (b) (5)   Another example has to do with the SAT itself.  Our original plans called for about 2 weeks of dry runs followed by 2-3 weeks of official “runs for the record.”  However, we’ve decided we should do much more testing to give us statistical confidence in our results.  Our future decisions about SBInet depend on good data on performance—so we think we should take the time to get the statistics right.  In this case, we have we need to check through the (b) (7)(E) AOR.  To be statistically (b) (7)(E) valid,   That (b) (5) wasn’t our original plan but we think it makes sense now.  Another difference comes from an OBP request.  The system as designed calls fo (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) e’ve agreed to check that out in SAT—which is almost like doubling the amount of testing.  This is a tough call for a program manager because it costs time and it’s not part of the formal requirement for the system—but it seems to be a very high priority for OBP so I think it prudent to be responsive.  As a result of all of this, SAT will be much longer than our original plan —it will be about a month for dry runs and 6-8 weeks for formal runs for the record.   v/r, - (b)(6);(b)(7)(C)   (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000150 DHS-17-0046-C-000150 From: To: Cc: Subject: Date: Attachments: - (b)(6);(b)(7)(C) Draft SBI SED Overview sjk 5 Jan 10.pptx Tuesday, January 05, 2010 10:48:40 AM SBI SED Overview sjk 5 Jan 10.pptx (b)(6);(b)(7)(C) As you go forward to introduce your new organization to your team tomorrow, I wanted to offer you both a chance to view what I believe are SBI SE’s vision and mission. Understanding the SE perspective may provide a little more clarity in understanding the grey areas between my organization and yours OR may be the catalyst for follow-on discussions. The attached is still work in progress but believe I am near 80% complete. Thanks, (b)(6);(b)(7)(C) Director, Systems Engineering Secure Border Initiative (SBI) U.S. Customs and Border Protection (b)(6);(b)(7)(C) Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. • (b)(6);(b)(7)(C) BW7 FOIA CBP 000151 DHS-17-0046-C-000151 DRAFT CBP SBI Systems Engineering Directorate Presented by (b) (6) (b)(6);(b)(7)(c) Director of Systems Engineering 5 January 2010 BW7 FOIA CBP 000152 DHS-17-0046-C-000152 CBP SBI Systems Engineering Directorate (SED) Vision Practice Practice the systems engineering discipline by providing qualified Subject Matter Expertise across the enterprise. SED Center of Excellence Lead Lead systems engineering efforts for CBP acquisitions Advocate Advocate for the systems engineering discipline for the CBP SE Center of Excellence BW7 FOIA CBP 000153 July 14, 2008 DHS-17-0046-C-000153 2 CBP SBI Systems Engineering Directorate (SED) Mission • The Systems Engineering Directorate is the Practice Lead within CBP for Systems Engineering: – Develops and applies Systems Engineering practices across the CBP enterprise by: • Identifying • Defining • Maintaining • Executing • and monitoring system engineering processes throughout a system’s entire life cycle – Trains and supplies Subject Matter Experts • Provides technical Subject Matter Expertise (SMEs) to CBP acquisition programs/projects (current focus is SBInet) July 14, 2008 Practice BW7 FOIA CBP 000154 DHS-17-0046-C-000154 3 CBP SBI Systems Engineering Directorate (SED) Mission (cont.) • The Systems Engineering Directorate leads program and enterprise efforts to achieve superior technical outcomes through: – Process Improvement • Continuously monitor and improve the Technical and Technical Management Processes. – Quality Control • Monitor and improve the quality of Systems Engineering Products that impact Cost, Schedule or Technical Performance – Applied Systems Engineering and Guidance/Mentoring • Provides guidance and mentoring for the SE processes by participating in Integrated Product Teams and Technical Review Boards July 14, 2008 Lead BW7 FOIA CBP 000155 DHS-17-0046-C-000155 4 CBP SBI Systems Engineering Directorate (SED) Mission (cont.) • The Systems Engineering Directorate is the CBP and Program Systems Engineering advocate: July 14, 2008 Advocate BW7 FOIA CBP 000156 DHS-17-0046-C-000156 5 Systems Engineering Directorate Technical and Technical Management Processes Technical Management Processes Technical Processes Monitors Transition Identify Technical Planning Configuration Mgmt Validation Requirements Mgmt Verification SELC E Executes Integration Requirements Analysis Technical Assessment Data Management Implementation Architecture Design Define Maintains Develops Interface Management Risk Management Development and implementation of technical process “Best BW7 FOIA CBP 000157 DHS-17-0046-C-000157 July 14, 2008 Practices" is part of SED Mission of Practice, Lead & Advocate 6 6 Systems Engineering Directorate SBI Program Activities • The SBI Systems Engineering Division supports SBInet in the following Projects: – System Block Development for Block-1 Northern Border Project Increment 1 – Southwest Border projects: • P-28 • C3I/COP • TUS-1 • AJO-1 – Northern Border projects: • Increment 1: Surveillance Enhancement Project TUS-1 Laydown • Increment 2: Integration Demonstration Project (b) (7)(E) – P-25 Tactical Modernization Program AJO-1 Laydown – Spectrum Relocation (b) (7)(E) (b) (7)(E) BW7 FOIA CBP 000158 July 14, 2008 DHS-17-0046-C-000158 SED & SBI Program Project Production (P3) Relationship SBI Program Manager SBI Director SED Executive Director SBInet P3 Authority Technical Authority Requirements Design Prototype Implementation Deployment Sustainment Test Systems Engineers and Systems Analysts Program & Technical Authority •Sets system level technical direction and content •Develops standards, architectures, tools and processes •Provides systems engineering SMEs to Programs and Projects for production assistance to ensure proper implementation •Ensures engineering products are complete and meet program needs •Ensures resource competency, allocation, career development July 14, 2008 Program Managers and Analysts Interface Interface Areas • Execution of technical management processes • Execution of technical processes • Issue Resolution Project Production Authority •Accountable to the SBI Program Manager for executing SBInet production as designed by the SED •Responsible for all production aspects of Program management (Cost, Schedule, Performance) •Production Planning •Measure progress 8 BW7 FOIA CBP 000159 •Report status DHS-17-0046-C-000159 SED Technical Authority •The Systems Engineer (SE) Technical Authority (TA) is responsible for the following activities: – Elicits stakeholder requirements – Analyzes requirements – Develops the Functional Architectural Design – Guides Physical Architectural Design – Guides Developer Implementation Activities – System integration – Verifies that system meets requirements baseline – Transitions the system to the production environment – Validates that the system meets the users operational needs – Sustains the system in its operational environment – Maintains the system until it meets the end of its life cycle – Disposal of the system BW7 FOIA CBP 000160 July 14, 2008 DHS-17-0046-C-000160 9 SBI Program Project Production (P3) Authority •The Executive Director for SBInet has Program Authority (PA) and is responsible for the following activities for the PEO: – Executes programmatic functions (Cost, Schedule, and Performance) – Ensures alignment with SED Architecture Specifications and SE Processes – Develops and assesses the Production Plan – Controls production execution – Responsible for Production decision-making – Monitors and mitigates Production risk associated – Produces the product BW7 FOIA CBP 000161 July 14, 2008 DHS-17-0046-C-000161 10 Systems Engineering Directorate Office of the Director Sr Sys Eng (b)(6);(b)(7)(c) (b) (6) Dir. Systems Engineering GS-340-15 110 (b) (6) (b)(6);(b)(7)(c) T r GS-801-15 115 Director Systems Engineering –(b)(6);(b)(7)(c) (b) (6) Mission - The CBP/SBI Systems Engineering Director provides supervisory functions for a diverse staff of engineers, analysts, and computer scientists which includes: setting priorities and schedules; assigning; making decisions on issues presented by the staff; communicating performance requirements; evaluating work performance; and executing personnel actions. The CBP/SBI Systems Engineering Director assists the SBInet Program Manager to identify, direct and maintain the resources (e.g., personnel, facilities, equipment and funds) to achieve SBInet capabilities. BW7 FOIA CBP 000162 July 14, 2008 DHS-17-0046-C-000162 11 CBP/SBI Systems Engineering Director Responsibilities •Responsibilities - SBI Systems Engineering Director ensures: – strategic technical issues/tenets drive the program management structure and decision framework – SBI’s established mission, vision, and management philosophy for the systems engineering enterprise is adhered to – IEEE or equivalent Systems Engineering and Software Development standards are used in developing the SBI product suite – development of the systems engineering toolbox (i.e., design reference mission, formalized metrics, modeling and simulation tools, assessment tools) necessary to execute a discipline systems engineering approach – assistance to the SBInet Program Manager to identify, direct and maintain the resources (e.g., personnel, facilities, equipment and funds) to achieve SBInet capabilities •Deliverables – products are delivered by each division within the directorate and coordinated at the Director level for internal SE approval before release to the Program Management Authority BW7 FOIA CBP 000163 July 14, 2008 DHS-17-0046-C-000163 12 Systems Engineering Directorate Divisions (b) (6) (b)(6);(b)(7)(c) Dir. Systemsl::r\faln· erlflg GS-340--15 110 (b) (6) (b)(6);(b)(7)(c) Vacam Dir ~q~ ~ Arclit G~liOH5 us Br Dir Logi,;tir:,; l:!i;GS.-3'B-115 11 VACJtNT e&I &, l:VBI r Gs:::ba01• 16 I) V;ic;;imJ Di' S eri l E"'3 Br e~oo,, 1' Mission - The Systems Engineering Directorate Divisions support the Systems Engineering Director by ensuring SBI engineering staff execute across the program and in alignment with the SBI Program and SE Division Vision, DHS and CBP acquisition policies, all Technical and Technical Management Processes, the Technical Baseline, the SBInet SELC as documented in the program’s Systems Engineering Plan (SEP), and the SBI Enterprise Architecture to produce quality integrated SBI capabilities meeting the end users’ needs. BW7 FOIA CBP 000164 July 14, 2008 DHS-17-0046-C-000164 13 CBP/SBI Systems Engineering Directorate Technical Management Division (b)(6);(b)(7)(c) (b) (6) VACA NT Teen Mgmt D1reo (b)(6);(b)(7)(c) (b) (6) VACA Tecti A.ssessrnet VACANT Work Force . (b) (6) (b)(6);(b)(7)(c) Director - VACANT/(b)(6);(b)(7)(c) (b) (6) ns VACAN CM Data Mgr (b)(6);(b)(7)(c) VACANT Risk Ma en (b) (6) Acting) Mission -The CBP/SBI Technical Management Division, under the Director of Systems Engineering, develops manages, and executes industry best Technical Management Processes and Practices for Systems Engineering across CBP and within acquisition programs such as SBInet. Technical Management Processes such as Configuration Management, Risk Management, and Quality Control ensure the proper control and delivery of superior engineering products while mitigating program risk (cost, schedule, and technical performance). BW7 FOIA CBP 000165 July 14, 2008 DHS-17-0046-C-000165 14 Technical Management Division •Responsibilities – manages the technical management processes executed across the SBI program. Executes the following responsibilities for the program: – SE Process development and execution – Quality Control & Assurance – Configuration Management – Risk Management – Work Force Operations Development – Develops and sustains all SE processes ensuring proper execution across the program •Deliverables – – SE Technical and Technical Management Processes – Technical Review Manual – Quality Assurance Plan – Risk Management Plan – Configuration Management Plan BW7 FOIA CBP 000166 July 14, 2008 DHS-17-0046-C-000166 15 Systems Engineering Division Requirements & Architecture – Organization Vaca t Di r 1:!e qmts & Aich l ec Br GS-a0 1-1 5 11 8 VP£ANT Mg r, Requ irerne11\s GS - 080 1- 14 VACA N T Mgr . Architecture Design GS-1550-14 12 4 23 (b)(6);(b)(7)(C) (b) (6) (b) (6) (b)(6);(b)(7)(C) (b) (6) (b)(6);(b)(7)(C) Sysim Sp ecifcn Eng GS-,801-13 126 (b)(6);(b)(7)(C) (b) (6) Vacant (b) (6) (b)(6);(b)(7)(C) MS Eogmeet"i11g GS-00 1-13/1 :4 129 (b) (6) (b)(6);(b)(7)(C) (b) (6) (b)(6);(b)(7)(C) 7 Engin-r iI1 Tmg GS - 0801 - 517/9 1:32 eCI) ::llfpp(!l"l Cir 134 (C) (b) (6) (b)(6);(b)(7)(C) Tech Support 135 (0) Director - VACANT Mission -The CBP/SBI Requirements and Architecture Division, under the Director of Systems Engineering, manages the Requirements Process for CBP/SBI by identifying, documenting, analyzing, tracing, tracking, prioritizing, and agreeing on requirements, sets the requirements baseline and then controls change and communicates any changes to relevant stakeholders. It is a continuous process throughout CBP’s acquisition programs and SBInet. BW7 FOIA CBP 000167 July 14, 2008 DHS-17-0046-C-000167 16 Systems Engineering Division Requirements & Architecture •Responsibilities – manages the requirements management process for the SBI program. – ensures form, fit and function of all user defined and system derived functional, non-functional, and performance requirements; – interface to the Requirements Review Board – ensures alignment of all requirements to the CBP EA through architecture modeling and analysis – contributes to infrastructure and environmental impact analysis – coordinates with T&E on the development of the Test and Evaluation Master Plan – develops Service Level Agreements (SLAs) – responsible for Information Security Assessments and plans •Deliverables: – Requirements Traceability Matrix – SBI Enterprise and System Architectures – Interface Control Documents – Service Level Agreements – Systems Security Plan – Security Risk Assessment July 14, 2008 BW7 FOIA CBP 000168 DHS-17-0046-C-000168 17 Systems Engineering Division Integrated Logistics Support (b)(6);(b)(7)(C) (b) (6) Dir Logist ics Br - AC Gs-340-15 (b) (6) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b) (6) Oep Dir/ Field Liaiso n GS-343--14 (b) (6) (b)(6);(b)(7)(C) Staff Asst. GS-30·1-9111 (b)(6);(b)(7)(C) (b) (6) (b)(6);(b)(7)(C) b,, (b)(6);(b)(7)(C) (b) (6) ISSE and r) (b)(6);(b)(7)(C) (b) (6) Ctr) roo Ill VACANT Le!ILS Pol11:y& Plarwing ~343-14 VACANT In-service Mgml GS-343-14 (b)(6);(b)(7)(C) (b) (6) (b)(6);(b)(7)(C) Ld Mat.erial Mgmt Precess Dev & Imp! Vacant System Software Support GS--343-14 <3$-1 _5_5 _0_ (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b) (6) ILS Dev l:!,lmplem GS-434-1 3114 ILS Division Director (b)(6);(b)(7)(C) (b) (6) (b)(6);(b)(7)(C) Mission – The SBI ILS Division, under the Director of Systems Engineering, supports the acquisition and sustainment of critical border enforcement assets through the development and implementation of ILS requirements in accordance with DHS Acquisition Directive 102-01, Appendix J. The ILS Division ensures for the program that design considerations are met to support customer needs in the areas of reliability, maintainability, and availability, to optimize border enforcement operations at optimal life-cycle costs BW7 FOIA CBP 000169 July 14, 2008 DHS-17-0046-C-000169 18 Systems Engineering Division Integrated Logistics Support •Responsibilities – manages supportability and sustainment requirements for SBI baseline technology products by: – establish a CBP wide ILS Integrated Product Team to develop a CBP capability to sustain border enforcement technology – develop a model to integrate logistics engineering requirements into the systems engineering process – partner with CBP/SBI acquisition offices to develop an O&M budgeting process/model suitable to meet SBI and legacy life-cycle support needs – identify and develop an ILS infrastructure to meet the life-cycle support needs of critical border enforcement technology – work with the Office of Administration, Acquisition Directorate, in the development and implementation of DHS-wide ILS Policy in support of DHS AD 102-01, Appendix J – develop tailored engineering specification requirements to meet the reliability, maintainability, and availability needs of the border enforcement end user communities •Deliverables: – Integrated Logistics Support Plan – Supportability and Sustainment Risks – In-service engineering plans – Technical Training Plans – Reliability, Maintainability, and Availability Plans – Trade studies – Operations and Maintenance budget development and expenditure planning BW7 FOIA CBP 000170 July 14, 2008 DHS-17-0046-C-000170 19 Systems Engineering Division Test & Evaluation Di VACANT est &. ,Eva l.Br GS{l80 1-15 120 VACANT V ACANT M g r- Op r l Test lng GS- 15 15- 14 M g r De'v&De,plyTest G S-0801-14 158 150 (b)(6);(b)(7)(C) (b) (6) (Ctr ) ,:,ys; ,m,ag , e,sl lng GS"801- (b)(6);(b)(7)(C) (b) (6) 1 2/ 14 152 (b)(6);(b)(7)(C) (b) (6) (b)(6);(b)(7)(C) (b) (6) (b) (6) (b)(6);(b)(7)(C) Dt;!vetqp , e su ng GS-0801- 9/ 14 160 (b)(6);(b)(7)(C) (b) (6) (b) (6) (b)(6);(b)(7)(C) Ctr ) IV&V Manage..GS-601 -1,2/1 4 15 3 (b) (6) (b)(6);(b)(7)(C) Sys lrrteg Te& ti ng GS-60112 /1 4 154 (b)(6);(b)(7)(C) (b) (6) Technica l Spt.. CTR 156 (C) (b)(6);(b)(7)(C) (b) (6) Technical Spt CTR 163 (b)(6);(b)(7)(C) (b) (6) VACANT TECHNICAL SPT 157 (C Director Test and Evaluation Division – VACANT Mission – The SBI Test and Evaluation Division under the direction of the SED Director develops, implements, and executes all CBP and SBI Test and Evaluation Processes in coordination with SBInet ensuring that all program and project requirements are implemented correctly for a given capability - does the product do what it is suppose to due as envisioned by the end users. BW7 FOIA CBP 000171 July 14, 2008 DHS-17-0046-C-000171 20 Systems Engineering Division Test & Evaluation •Responsibilities – ensure that all requirements in the SBI Baseline are tested and meet the users end needs through testing, verification and validation techniques and methods. Included are the following activities: – manages and execute all test activities to include Acceptance and System Qualification Testing – develops test scenarios – Develops Test Plans – responsible for coordinating verification and validation testing of all SBI requirements – coordinates product development with the Requirements and Architecture Branch – develop security certification documentation •Deliverables: – Test and Evaluation Master Plan – Operational Test Scenarios – Verification and Validation of all SBI Baseline Requirements – Product and Program Maturity Assessments – SBI Test and Evaluation Data Management Plan – SQT Detailed Test Plans – Security Certifications BW7 FOIA CBP 000172 July 14, 2008 DHS-17-0046-C-000172 21 Systems Engineering Division Specialty Engineering – Organization VACANT c ~9 ..ic.:mt Dir Specls l Erl~ Br S"'11Af: .  Please put a hold on Friday at 2PM at the NAC.  I will send a request later today.  Thank 1111 Thanks you!!   (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) cell) (b)(6);(b)(7)(C) From: Sent: Tuesday, January 12, 2010 6:18 PM (b)(6);(b)(7)(C) To: Subject: Re: SBInet Meeting - ] I can adjust anything on Friday fairly easily. Thursday morning is also pretty adjustable. Thursday afternoon is the worst for me. From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: Sent: Tue Jan 12 17:40:16 2010 Subject: SBInet Meeting > (b)(6);(b)(7)(C) Hello everyone,   BW7 FOIA CBP 000273 DHS-17-0046-C-000273 Can you please send me your available times for an SBInet meeting here at the NAC this Thursday or Friday.  There will be a call in as well if you are not able to attend in person.  Thanks!!   (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) (cell) BW7 FOIA CBP 000274 DHS-17-0046-C-000274 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: RE: SBInet Meeting Wednesday, January 13, 2010 10:43:21 AM Thank-you and I will make sure this is on his calendar for Friday.   (b)(6);(b)(7)(C) Customs and Border Protection Secure Border Initiative Offic (b)(6);(b)(7)(C) Main (b)(6);(b)(7)(C) From: Sent: Wednesday, January 13, 2010 10:39 AM (b)(6);(b)(7)(C) To: Subject: RE: SBInet Meeting Thanks you!!   ] - .  Please put a hold on Friday at 2PM at the NAC.  I will send a request later today.  Thank (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) (cell) (b)(6);(b)(7)(C) From: Sent: Tuesday, January 12, 2010 6:18 PM To: (b)(6);(b)(7)(C) Subject: Re: SBInet Meeting ] - I can adjust anything on Friday fairly easily. Thursday morning is also pretty adjustable. Thursday afternoon is the worst for me. From: To: (b)(6);(b)(7)(C) Cc: Sent: Tue Jan 12 17:40:16 2010 Subject: SBInet Meeting > (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Hello everyone,   Can you please send me your available times for an SBInet meeting here at the NAC this Thursday or Friday.  There will be a call in as well if you are not able to attend in person.  Thanks!!   (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) BW7 FOIA CBP 000275 DHS-17-0046-C-000275 BW7 FOIA CBP 000276 DHS-17-OO46-C-000276 --------------(b)(6);(b)(7)(C) From: Sent: To: Subject: - (b)(6);(b)(7)(C) Wednesday, January 13, 2010 2:27 PM (b)(6);(b)(7)(C) Accepted: SBInet   1 BW7 FOIA CBP 000277 DHS-17-0046-C-000277 (b)(6);(b)(7)(C) From: To: Subject: SBInet When: Friday, January 15, 2010 2:00 PM-3:00 PM (GMT-05:00) Eastern Time (US & Canada). Where: (b) (7)(E) *~*~*~*~*~*~*~*~*~* BW7 FOIA CBP 000278 DHS-17-0046-C-000278 From: To: Subject: Date: (b)(6);(b)(7)(C) Re: Wednesday, January 13, 2010 6:18:55 PM Right on. Thanks! From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Wed Jan 13 18:15:47 2010 Subject: RE: Nothing specific, I just wanted to make sure.  I will ask my team to start giving some thought to the types of technology that might be useful and available, and will also get some informal market surveys done so we can have an idea of what’s out there and what’s in the realm of the possible.  I would like to be poised with some information in hand.  But this activity will NOT take any focus away from the problems we have facing us already.      (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Wednesday, January 13, 2010 6:11 PM To: (b)(6);(b)(7)(C) Subject: Re: I don't think we need to do that just yet--unless you think we have something I should bring in. From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Wed Jan 13 18:09:53 2010 Subject: RE: - :  Do you want an internal meeting to do some planning on this (i.e. what technology options might be viable)?       (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to BW7 FOIA CBP 000279 DHS-17-0046-C-000279 constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. From: (b)(6);(b)(7)(C) Sent: Wednesday, January 13, 2010 4:46 PM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject: Re: Chief-10-4. We've actually started this already and are planning to accelerate it. Vr (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Sent: Wed Jan 13 16:18:17 2010 Subject: (b)(6);(b)(7)(C) ,   In one of the breaks that we had yesterday in dealing with all the activities surrounding the 12/25 incident, Haiti, and another hot button item, the Secretary and I had a chance to very briefly discuss SBInet, the 60 Minutes piece, and path forward. She is of the same opinion as we are: the 60 Minutes piece was a lot less negative than what we had anticipated and she also thought that Boeing took the brunt of the piece. She also stated that the purpose of the memo that went out with her directing the “review” of SBInet was in anticipation of a more negative piece.  But basically she agrees with the options paper that we put forth before the holidays. She did not specifically identify option 2 as her preference but as she lined out her recollection of the memo and it fits right along with Option 2. She noted that she had “spoken to Congress” about this and that they were not surprised and supportive. I did not ask how this communication was done, formally or informally. Given the timeline from when we sent the paper forth I would guess that it was a verbal and informal.   (b)(6);(b)(7)(C) ,   This being the case we need to look at redesigning our thought process as to technology capability requirements (i.e, detection, deterrence, identification, classify, etc.. or mix of) that we would be looking to get resourced under this option. Exercising this option or something similar to it would mean that we would be weighting our resource procurement efforts and requirements towards “commodity purchases” of technology versus “system development”. Not that we would stop the systems development completely (block one). I would ask that Border Patrol revisit our technology requirements against this new information.   Keep me apprised.   (b)(6);(b)(7)(C)   - 1111 BW7 FOIA CBP 000280 DHS-17-0046-C-000280 From: To: Cc: Subject: (b)(6);(b)(7)(C) Updated: SBInet When: Friday, January 15, 2010 2:00 PM-3:00 PM (GMT-05:00) Eastern Time (US & Canada). (b) (7)(E) Where: *~*~*~*~*~*~*~*~*~* BW7 FOIA CBP 000281 DHS-17-0046-C-000281 From: To: Subject: Date: Sensitivity: (b)(6);(b)(7)(C) Re: SBI Call Feedback Friday, January 15, 2010 1:31:51 PM Confidential Thanks! From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Fri Jan 15 13:26:00 2010 Subject: Fw: SBI Call Feedback Heads up on this issue for todays meeting From: (b)(6);(b)(7)(C) . To: (b)(6);(b)(7)(C) Sent: Fri Jan 15 12:37:20 2010 Subject: Fw: SBI Call Feedback (b)(6);(b)(7)(C) From: To: (b)(6);(b)(7)(C) . Sent: Fri Jan 15 11:38:16 2010 Subject: RE: SBI Call Feedback I don’t know about talking points but this is an opportunity to do tech on border the right way.  As gov, we were pretty pissed off about how DHS never consulted with state and locals.  In general, we are trying to fix that.  With regard to sbinet, yes, we intend to get input from as many points of view as possible.  We would be nuts not to talk to these folks along the border to see what concerns they have and how technology could improve the situation.  There is a lot of expertise down there.  Getting that input would make the program better and build greater public support for deploying technology, which the Secretary believes is critical to controlling the border.       (b)(6);(b)(7)(C) From: Sent: Tuesday, January 12, 2010 8:14 PM To: (b)(6);(b)(7)(C) Subject: FW: SBI Call Feedback Sensitivity: Confidential   - ] Hi ,   (b)(6);(b)(7)(C) I believe you are setting up a meeting to discuss the SBInet review, but asked me to follow up with you on a particular issue.  We received the summary below from IGP and were surprised to see that state and locals were told they would have the opportunity to provide input – particularly those that are not in Arizona.   We were not aware that this was part of the talking points and are concerned that this is raising expectations among our state/local stakeholders.   Thanks, (b)(6);(b)(7)(C) 1111 BW7 FOIA CBP 000282 DHS-17-0046-C-000282 - (b)(6);(b)(7)(C)     (b)(6);(b)(7)(C) From: Sent: Monday, January 11, 2010 5:21 PM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Subject: SBI Call Feedback Sensitivity: Confidential   FOR OFFICIAL USE ONLY   (b)(6);(b)(7)(C) , Below is the listing for the calls we made on Friday night and the little bit of response we received. If you have any questions, please let us know. Thanks, 1111   (b)(6);(b)(7)(C) CALIFORNIA (b) (6) Contact: Chief of Staff, CalEMA · Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. · Said that the review would not impact current operations.  · Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. · RESPONSE:  Thanks for heads up.  (b)(6);(b)(7)(C) on the way to meet with Governors office and he would bring up.   (b) (6) Contact: Governor’s DC office.  · Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. · Said that the review would not impact current operations.  · Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. · Left msg.  (b)(6);(b)(7)(C) followed up w email “Thanks for the heads up!”   ARIZONA (b) (6) Contact:  HSA · Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. · Said that the review would not impact current operations.  · Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. · RESPONSE: Said thanks for the heads up and he would communicate to Deputy COS (b) (6) - - (b) (6)   NEW MEXICO (b) (6) Contact:   HSA · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days BW7 FOIA CBP 000283 DHS-17-0046-C-000283 ·   · Stated that the review will seek input from the four SW border states as provided in the TPs RESPONSE:  Said thanks for the heads up TEXAS (b) (6) Contact:  HSA · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Good, the system is a waste of billon dollars   Phoenix (b) (6) via email (his preference) Contact · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Said “thanks for the heads up   Los Angeles (b) (6) Contact: Office of the Deputy Mayor for Public Safety · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Heads up was appreciated   San Diego Contact:  DC Representative via email (b) (6) · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Appreciated the notice    Tucson (b) (6) Contact:  Mayor’s Chief of Staff · Sent him an email to call as he was out of the office on Friday · No response   TON (b) (6) Chairman’s Assist Contact: · Communicated to the TON was that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet and that it did not impact current operations · No mention of them being part of the system review as I did not have the facts as to how the review would take them into account · RESPONSE:  Expressed concern as to how this would impact the towers as he thought some of them were going to also be used for LE and some of the environmental impact BW7 FOIA CBP 000284 DHS-17-0046-C-000284 assessments that have been hurried through the system   BORDER COUNTIES COALITION Contact: (b) (6) · Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. · Said that the review would not impact current operations.  · Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. · RESPONSE: Said “Oh, good.” Very appreciative of heads up.  Mentioned that BCC would be meeting during annual NACO meeting and suggested Departmental presence at meeting.  Will follow up with me via email.    FOR OFFICIAL USE ONLY     (b)(6);(b)(7)(C) Deputy Assistant Secretary Intergovernmental Affairs U.S. Department of Homeland Security (O)(b)(6);(b)(7)(C) (F) (b)(6);(b)(7)(C) (E)   Warning: This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain confidential and legally privileged information such as found under 49 CFR 1520 or the Privacy Act of 1974. It should not be communicated to any person, or agency, unless disclosure is in performance of official DHS duties and there exists a valid need to know.  If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited.  If you have received this in error, please reply immediately to the sender and delete this message.     BW7 FOIA CBP 000285 DHS-17-0046-C-000285 (b)(6);(b)(7)(C) From: To: Cc: Subject: Date: RE: SBInet Meeting Tuesday, January 12, 2010 7:37:26 PM Thursday isn’t at all good for me, Friday is open right now after the morning ARRA Meeting     (b)(6);(b)(7)(C) Dir. Policy & Acquisition Workforce Office of the Chief Procurement Officer Department of Homeland Security (b)(6);(b)(7)(C) (W) (C)   - From: (b)(6);(b)(7)(C) Sent: Tuesday, January 12, 2010 5:40 PM To: Cc: Subject: SBInet Meeting (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Hello everyone,   Can you please send me your available times for an SBInet meeting here at the NAC this Thursday or Friday.  There will be a call in as well if you are not able to attend in person.  Thanks!!   (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) (cell) BW7 FOIA CBP 000286 DHS-17-0046-C-000286 From: To: Cc: Subject: (b)(6);(b)(7)(C) Updated: SBInet Plan When: Thursday, January 21, 2010 11:00 AM-1:00 PM (GMT-05:00) Eastern Time (US & Canada). Where: To be provided by (b)(6);(b)(7)(C) - *~*~*~*~*~*~*~*~*~* (b)(6);(b)(7)(C) - , if you could provide the meeting location.  Thanks…(b)(6);(b)(7)(C) BW7 FOIA CBP 000287 DHS-17-0046-C-000287 --------------(b)(6);(b)(7)(C) Subject: SBInet Plan Start: End: Show Time As: Thu 1/21/2010 11:00 AM Thu 1/21/2010 1:00 PM Tentative Recurrence: (none) Meeting Status: Not yet responded Organizer:   - (b)(6);(b)(7)(C) 1 BW7 FOIA CBP 000288 DHS-17-0046-C-000288 From: To: Subject: Date: Copying (b)(6);(b)(7)(C) Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet Saturday, January 09, 2010 1:00:10 PM -- and (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) To: Sent: Sat Jan 09 13:00:04 2010 Subject: Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet - (b)(6);(b)(7)(C) may call me directly, if so, I will let you guys know. (b)(6);(b)(7)(C) Assistant Secretary Office of the Private Sector Department of Homeland Security From: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) To: Sent: Sat Jan 09 12:55:08 2010 Subject: Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet - Excellent. Thanks, (b)(6);(b)(7)(C) . - (b)(6);(b)(7)(C) Adding and (b)(6);(b)(7)(C) we should coordinate w(b)(6);(b)(7)(C) on Monday re more fully briefing the Boeing folks. We first, of course, need to specifically chart out our assessment process. 1111 Thx. -------------------------Sent using BlackBerry From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Sat Jan 09 12:44:30 2010 Subject: Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet Message delivered. They had been contacted by 60 minutes but really appreciated the outreach by us. (b)(6);(b)(7)(C) Assistant Secretary Office of the Private Sector Department of Homeland Security From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Sat Jan 09 12:37:16 2010 Subject: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet Obviously, the stuff re Recovery Act is especially sensitive. BW7 FOIA CBP 000289 DHS-17-0046-C-000289 Thanks. -------------------------Sent using BlackBerry From: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: ' Sent: Fri Jan 08 14:33:18 2010 Subject: HEADS UP: Napolitano to ask for reassessment of SBInet > Later today, Secretary Napolitano will direct the Department to conduct a reassessment of SBInet, the technology piece of the Southwest Border Initiative (SBI).  (b) (5)   We can discuss later if you would like.     (b)(6);(b)(7)(C) Senior Counselor to Secretary Janet Napolitano U.S. Department of Homeland Security Washington, DC  20528   (b)(6);(b)(7)(C) BW7 FOIA CBP 000290 DHS-17-0046-C-000290 From: To: Subject: Date: (b)(6);(b)(7)(C) Re: SBInet Follow-ups Tuesday, January 12, 2010 4:03:13 PM Yeah... (b)(6);(b)(7)(C) From: To: (b)(6);(b)(7)(C) Sent: Tue Jan 12 16:02:23 2010 Subject: RE: SBInet Follow-ups If I hadn’t read this, I wouldn’t believe it…   From: (b)(6);(b)(7)(C) Sent: Tuesday, January 12, 2010 3:48 PM (b)(6);(b)(7)(C) To: Subject: RE: SBInet Follow-ups   Are you asking about the review the Secretary directed?  If so, we don’t have that information in SBI.   (b)(6);(b)(7)(C) From: Sent: Tuesday, January 12, 2010 3:43 PM To: ] (b)(6);(b)(7)(C) Subject: RE: SBInet Follow-ups   Do we know how long the review will take? Thanks   (b)(6);(b)(7)(C) From: Sent: Tuesday, January 12, 2010 1:42 PM (b)(6);(b)(7)(C) To: Subject: Re: SBInet Follow-ups   Work does continue. With respect to delays, we've said a MINIMUM of three months--which would be April. We don't have the final schedule yet because we have a variety of options that we're trading against risk and benefit. We expect to lock down the schedule in the next couple of weeks.   From: To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Sent: Tue Jan 12 13:38:37 2010 BW7 FOIA CBP 000291 DHS-17-0046-C-000291 Subject: Re: SBInet Follow-ups Looping (b)(6);(b)(7)(C) and (b)(6);(b)(7)(C) 1111 -   From: To: (b)(6);(b)(7)(C) > (b)(6);(b)(7)(C) Sent: Tue Jan 12 13:34:38 2010 Subject: RE: SBInet Follow-ups - Meant to add   (b)(6);(b)(7)(C) . From: (b)(6);(b)(7)(C) Sent: Tuesday, January 12, 2010 1:34 PM To: Subject: SBInet Follow-ups (b)(6);(b)(7)(C)   (b) (6) from The Daily Star in AZ had a couple follow-up questions, both of which I just wanted to confirm answers for and make sure it was ok to verify for him.   • How long has the project been delayed this time? When is the new estimated delivery date? (I had heard March or April) Is work halted on the project during the review? (No – work continues)   Thanks, • (b)(6);(b)(7)(C) Deputy Press Secretary Office of Public Affairs U.S. Department of Homeland Security O - (b)(6);(b)(7)(C) C- (b)(6);(b)(7)(C)   BW7 FOIA CBP 000292 DHS-17-0046-C-000292 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet Saturday, January 09, 2010 1:39:20 PM Good. From: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Sent: Sat Jan 09 13:34:40 2010 Subject: Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet Thanks. At our level, we've been discussing the likelihood of this with Boeing for some time--so they should not be terribly surprised. (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(C) Sent: Sat Jan 09 12:55:08 2010 Subject: Fw: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet FYI (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(C) To: (HQ) Sent: Sat Jan 09 12:55:08 2010 Subject: Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet - Excellent. Thanks,(b)(6);(b)(7)(C) . - (b)(6);(b)(7)(C) Adding and (b)(6);(b)(7)(C) we should coordinate w (b)(6);(b)(7)(C) on Monday re more fully briefing the Boeing folks. We first, of course, need to specifically chart out our assessment process. 1111 Thx. -------------------------Sent using BlackBerry From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Sat Jan 09 12:44:30 2010 Subject: Re: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet Message delivered. They had been contacted by 60 minutes but really appreciated the outreach by us. (b)(6);(b)(7)(C) Assistant Secretary Office of the Private Sector Department of Homeland Security BW7 FOIA CBP 000293 DHS-17-0046-C-000293 From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Sat Jan 09 12:37:16 2010 Subject: FYI: HEADS UP: Napolitano to ask for reassessment of SBInet Obviously, the stuff re Recovery Act is especially sensitive. Thanks. -------------------------Sent using BlackBerry From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Cc: ' Sent: Fri Jan 08 14:33:18 2010 Subject: HEADS UP: Napolitano to ask for reassessment of SBInet Later today, Secretary Napolitano will direct the Department to conduct a reassessment of SBInet, the technology piece of the Southwest Border Initiative (SBI).    (b) (5)   We can discuss later if you would like.     (b)(6);(b)(7)(C) Senior Counselor to Secretary Janet Napolitano U.S. Department of Homeland Security Washington, DC  20528 (b)(6);(b)(7)(C)   BW7 FOIA CBP 000294 DHS-17-0046-C-000294 From: To: Subject: Date: (b)(6);(b)(7)(C) Out of Office AutoReply: SBInet on Federal News Radio Friday, January 22, 2010 10:36:35 AM - I will be out of the office until Monday, January 25, 2010.  Please contact the Office of Congressional Affairs at (b)(6);(b)(7)(C) .  BW7 FOIA CBP 000295 DHS-17-0046-C-000295 From: To: Cc: Subject: Date: (b)(6);(b)(7)(C) SBInet meeting with DHS Monday, January 18, 2010 9:24:13 PM (b)(6);(b)(7)(C) ),   For your awareness, I provided the notes below on our Friday meeting with(b)(6);(b)(7)(C) to the Chief in preparation for his component’s meeting tomorrow morning.  I also had a brief chance to fill him in verbally.  He is still a little concerned about the outreach to state and local (ie made an analogy to the checkpoints) and may try to talk to a little more about that aspect.  I did tell him that I thought we were pretty much on the same page with Dept on the other issues.   - (b)(6);(b)(7)(C) SBInet For Your Info Only: • Per S1 direction, (b)(6);(b)(7)(C) held a meeting with CBP, S&T and DHS Management to discuss the plan to review the future of the SBInet technology program. • The purpose of the review is to drill down on the four options in the December 16, 2009 memo from (b)(6);(b)(7)(C) to S1.  The goal is to get the right capabilities to the right places as quickly as possible. • It was recognized the first option (status quo) and the fourth option (discontinue/delay) are probably out, but the focus should be on option 2 (CBP’s recommendation) and option 3.  • Next week CBP, S&T and DHS Management will convene to set up a subcommittee to discuss roles, goals, timelines and output.  • It was discussed by all that the recommended solution has a clear linkage to Operational Requirements Documents (ORD), and a more robust Analysis of Alternatives.  • S1 office would like us to involve stakeholders in some way such as border sheriffs, mayors, county supervisors, GAO, IG and the Hill, etc.  This does not need to be a formal complex outreach plan – i.e. could be phone calls; not town hall meetings or hearings. • Once the most effective strategy is identified and approved, DHS will provide the necessary cover for that future direction.  CBP should not feel bound by past constraints.  • Short Term – Stimulus funding issues may need to be worked on a separate, more expedited.  Specifically, if we don’t have a viable/verifiable plan in the next one to two weeks, it may be time for DHS/CBP to consider reprogramming some of those funds for more pressing needs.  - - (b)(6);(b)(7)(C) Counselor, Office of the Commissioner U.S. Customs and Border Protection (b)(6);(b)(7)(C) BW7 FOIA CBP 000296 DHS-17-0046-C-000296 From: To: Subject: Date: Attachments: (b)(6);(b)(7)(C) FW: House Homeland request Wednesday, January 20, 2010 12:03:41 PM SQT2 fix before SAT rev 1.ppt (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection -----Original Message----From: (b)(6);(b)(7)(C) Sent: Saturday, January 09, 2010 4:01 PM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Subject: RE: House Homeland request - (b)(6);(b)(7)(C) - :  Here's a quick look at the 47 items from SQT2 that we've agreed need to be fixed prior to SAT.  We'll (b)(6);(b)(7)(C) certainly want to package this differently to give to .  Last week (b)(6);(b)(7)(C) starting work on binning these into categories along with a top level description of each bin.  We can probably have that done sometime Monday unless we need to make it a higher priority (we have several meeting scheduled with Boeing Monday morning on (b) (7)(E) and SAT related topics). • 1111 Thanks    (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual  authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. -----Original Message----From: (b)(6);(b)(7)(C) Sent: Saturday, January 09, 2010 12:28 PM To: (b)(6);(b)(7)(C) Subject: Re: House Homeland request - (b)(6);(b)(7)(C) - : I think the number is 47, but will confirm. We actually worked on this same type of info for (b)(6);(b)(7)(C) late yesterday. As soon as I get back home I'll mobikey into my computer and try to retrieve the data and send it to you. (b)(6);(b)(7)(C)    Executive Program Director, SBInet    U.S. Customs and Border Protection, DHS   (b)(6);(b)(7)(C) BW7 FOIA CBP 000297 DHS-17-0046-C-000297 ----- Original Message ----From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(C) Sent: Sat Jan 09 12:12:18 2010 Subject: Re: House Homeland request Hi, - (b)(6);(b)(7)(C) . I'll have to track down the details but we can certainly do that early next week.  The 42 is an old number so it may be a bit difficult to recreate that exaxct list--but we should be able to meet the intent of the question. I'm probably going to be the best POC, at least on Monday--I've pretty much blocked off my calendar to deal with this type of stuff. ----- Original Message ----From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(C) Sent: Sat Jan 09 12:05:55 2010 Subject: House Homeland request (b)(6);(b)(7)(C) 1111 I received an email from (b) last night requesting additional information on the 42 issues that arose during the second SQT that Boeing (6); is required to fix before SAT.  I anticipate getting similar questions from our other usual (b)(7) POCs, and probably several other folks after 60 Minutes airs. (c) This by no means needs to be answered this weekend, but I at least wanted to make you aware.  Also, since I know you'll be responding to a lot of media inquiries as well on Monday, I wanted to check and see if I should direct my questions to (b) , or if I should still send along to you? (6) Hope you're ;having a nice weekend! (b) (7) (b) (c) (6); (b) (7) (c) • - BW7 FOIA CBP 000298 DHS-17-0046-C-000298 For Official Use Only FIX FIX Prior Prior to SAT 47 Open Items Items BW7 FOIA CBP 000299 For Official Use Only DHS-17-0046-C-000299 12/11/2017 2:31 PM 1 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 4 Change Area: Paper (b) (7)(E) Status: Complete-This is a procedural issue related to the • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Complete; Fix Prior to SAT Work Around: N/A Follow proper Startup sequence BW7 FOIA CBP 000300 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000300 12/11/2017 2:31 PM 2 For Official Use Only (b) (7)(E) • Issue Title: Validate (b) (7)(E) • Priority Assignment: 1 • Change Area: Firmware • Status: Complete - This validation has already been accomplished. (b) (7)(E) • • • • Impact to SAT: This revision is not a constraint to SAT Impact to OT&E: None Recommended Correction Date: Fix Prior to SAT Work Around: N/A BW7 FOIA CBP 000301 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000301 12/11/2017 2:31 PM 3 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 4 Change Area: Paper Status: This is a procedural issue related to th • • • • . Impact to SAT: No Impact Impact to OT&E: No Impact Recommended Correction Date: Fix Prior to SAT Work Around: Use Proper Start up Procedure (b) (7)(E) BW7 FOIA CBP 000302 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000302 12/11/2017 2:31 PM 4 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 4 Change Area: Paper (b) (7)(E) Status: This is a procedural issue related to the • • • • Impact to SAT: No Impact Impact to OT&E: No Impact Recommended Correction Date: Fix Prior to SAT Work Around: Use Proper Start up Procedure BW7 FOIA CBP 000303 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000303 12/11/2017 2:31 PM 5 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: • • • • Impact to SAT: None if Fixed Prior to SAT Impact to OT&E: None if Fixed Prior to SAT Recommended Correction Date: Fix Prior to SAT Work Around: None BW7 FOIA CBP 000304 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000304 12/11/2017 2:31 PM 6 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: Complete - Should close paperwork being closed • Impact to SAT: None • Impact to OT&E: None • Recommended Correction Date: Completed • Work Around: None BW7 FOIA CBP 000305 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000305 12/11/2017 2:31 PM 7 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: • • • • Impact to SAT: None if Fixed Prior to SAT Impact to OT&E: None if Fixed Prior to SAT Recommended Correction Date: Fix Prior to SAT Work Around: None BW7 FOIA CBP 000306 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000306 12/11/2017 2:31 PM 8 For Official Use Only (b) (7)(E) • Issue Title: • • • • • • • (b) (7)(E) Priority Assignment: 4 Change Area: Paper (b) (7)(E) Status: Procedural issue relative to Impact to SAT: None if Fixed Prior to SAT Impact to OT&E: None if Fixed Prior to SAT Recommended Correction Date: Fix Prior to SAT (b) (7)(E) Work Around: BW7 FOIA CBP 000307 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000307 12/11/2017 2:31 PM 9 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 1 Change Area: Software (b) (7)(E) Status: • • • • Impact to SAT: None if fixed Prior to SAT Impact to OT&E: None Recommended Correction Date: Fix Prior to SAT Work Around: None BW7 FOIA CBP 000308 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000308 12/11/2017 2:31 PM 10 For Official Use Only (b) (7)(E) • • • • • • • • (b) (7)(E) Issue Title: Priority Assignment: 1 Change Area: Software (b) (7)(E) Status: Impact to SAT: None if fixed prior to SAT Impact to OT&E: None Recommended Correction Date: Fix Prior to SAT Work Around: None BW7 FOIA CBP 000309 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000309 12/11/2017 2:31 PM 11 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Paper (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to SAT (b) (7)(E) Work Around: BW7 FOIA CBP 000310 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000310 12/11/2017 2:31 PM 12 For Official Use Only (b) (7)(E) • • • • • • • • (b) (7)(E) Issue Title: Priority Assignment: 2 Change Area: Software (b) (7)(E) Status: Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to SAT Work Around: None BW7 FOIA CBP 000311 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000311 12/11/2017 2:31 PM 13 For Official Use Only (b) (7)(E) • Issue Title: • • • • • • • (b) (7)(E) Priority Assignment: 2 Change Area: Paper (b) (7)(E) Status: Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to SAT Work Around: None BW7 FOIA CBP 000312 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000312 12/11/2017 2:31 PM 14 For Official Use Only (b) (7)(E) • • • • (b) (7)(E) Issue Title: Priority Assignment: 2 Change Area: Software (b) (7)(E) Status: . • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000313 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000313 12/11/2017 2:31 PM 15 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Firmware (b) (7)(E) • Status: • • • • Impact to SAT: Negligible Impact to Pid Impact to OT&E: None if fixed prior to OT&E Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000314 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000314 12/11/2017 2:31 PM 16 For Official Use Only (b) (7)(E) (b) (7)(E) • Issue Title: • Priority Assignment: 4 • Change Area: Paper (b) (7)(E) • Status: • • • • Impact to SAT: No Impact Impact to OT&E: No Impact Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000315 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000315 12/11/2017 2:31 PM 17 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 1 • Change Area: Software (b) (7)(E) • Status: • Impact to SAT: (b) (7)(E) • Impact to OT&E: None if Fixed Prior to OT&E • Recommended Correction Date: Fix Prior to OT&E • Work Around: None BW7 FOIA CBP 000316 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000316 12/11/2017 2:31 PM 18 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 4 • Change Area: Software (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000317 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000317 12/11/2017 2:31 PM 19 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 4 • Change Area: Software (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None if Fixed prior to OT&E Recommended Correction Date: Fix Prior to OT&E Work Around: Dismiss Alert BW7 FOIA CBP 000318 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000318 12/11/2017 2:31 PM 20 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E Work Around: Dismiss Alert BW7 FOIA CBP 000319 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000319 12/11/2017 2:31 PM 21 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 1 • Change Area: Software (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000320 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000320 12/11/2017 2:31 PM 22 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 1 Change Area: Software (b) (7)(E) Status: • • • • Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: (b) (7)(E) . BW7 FOIA CBP 000321 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000321 12/11/2017 2:31 PM 23 For Official Use Only (b) (7)(E) • • • • (b) (7)(E) Issue Title: Priority Assignment: 2 Change Area: Software (b) (7)(E) Status: • Impact to SAT: (b) (7)(E) • Impact to OT&E: None if Fixed Prior to OT&E • Recommended Correction Date: Fix Prior to OT&E • Work Around: None BW7 FOIA CBP 000322 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000322 12/11/2017 2:31 PM 24 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 1 • Change Area: Software (b) (7)(E) • • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000323 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000323 12/11/2017 2:31 PM 25 For Official Use Only (b) (7)(E) (b) (7)(E) • Issue Title: • Priority Assignment: 4 • Change Area: Software (b) (7)(E) • Status: • • • • Impact to SAT: None Operator Nuisance Impact to OT&E: None if fixed Prior to OT&E Recommended Correction Date: Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000324 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000324 12/11/2017 2:31 PM 26 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 4 Change Area: Software (b) (7)(E) Status: ) • • • • Impact to SAT: None Operator Nuisance Impact to OT&E: None if fixed Prior to OT&E Recommended Correction Date: Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000325 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000325 12/11/2017 2:31 PM 27 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000326 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000326 12/11/2017 2:31 PM 28 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 2 Change Area: Software (b) (7)(E) Status: • • • • Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: (b) (7)(E) BW7 FOIA CBP 000327 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000327 12/11/2017 2:31 PM 29 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 1 Change Area: Software (b) (7)(E) Status: • • • • Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: (b) (7)(E) BW7 FOIA CBP 000328 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000328 12/11/2017 2:31 PM 30 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 1 • Change Area: Software (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000329 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000329 12/11/2017 2:31 PM 31 For Official Use Only (b) (7)(E) • • • • • (b) (7)(E) Issue Title: Priority Assignment: 1 Change Area: Software Status: Ref PCR 2633 (b) (7)(E) Impact to SAT: • Impact to OT&E: None if fixed prior to OT&E • Recommended Correction Date: Fix Prior to OT&E • Work Around: None BW7 FOIA CBP 000330 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000330 12/11/2017 2:31 PM 32 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 1 Change Area: Software (b) (7)(E) Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000331 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000331 12/11/2017 2:31 PM 33 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 4 Change Area: Firmware (b) (7)(E) Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000332 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000332 12/11/2017 2:31 PM 34 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 2 Change Area: Paper (b) (7)(E) Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000333 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000333 12/11/2017 2:31 PM 35 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Paper (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000334 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000334 12/11/2017 2:31 PM 36 For Official Use Only (b) (7)(E) (b) (7)(E) • Issue Title: • Priority Assignment: 2 • Change Area: Paper (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000335 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000335 12/11/2017 2:31 PM 37 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 3 Change Area: Paper (b) (7)(E) Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000336 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000336 12/11/2017 2:31 PM 38 For Official Use Only (b) (7)(E) (b) (7)(E) • Issue Title: • Priority Assignment: 4 • Change Area: Paper (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Fix Prior to OT&E Work Around: None BW7 FOIA CBP 000337 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000337 12/11/2017 2:31 PM 39 For Official Use Only (b) (7)(E) (b) (7)(E) • • • • Issue Title: Priority Assignment: 1 Change Area: Paper (b) (7)(E) Status: • • • • Impact to SAT: None Impact to OT&E: None Recommended Correction Date: Prior to OT&E Work Around: None BW7 FOIA CBP 000338 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000338 12/11/2017 2:31 PM 40 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Paper (b) (7)(E) • Status: • • • • Impact to SAT: None Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000339 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000339 12/11/2017 2:31 PM 41 For Official Use Only (b) (7)(E) (b) (7)(E) • Issue Title: • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000340 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000340 12/11/2017 2:31 PM 42 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Paper (b) (7)(E) • Status: • Impact to SAT: (b) (7)(E) • Impact to OT&E: None if Fixed Prior to OT&E • Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) • Work Around: BW7 FOIA CBP 000341 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000341 12/11/2017 2:31 PM 43 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000342 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000342 12/11/2017 2:31 PM 44 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Software (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: Impact to OT&E: None if Fixed Prior to OT&E Recommended Correction Date: Fix Prior to OT&E Work Around: Operator Dismisses Alerts BW7 FOIA CBP 000343 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000343 12/11/2017 2:31 PM 45 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 4 • Change Area: (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: (b) (7)(E) Impact to OT&E: Recommended Correction Date: Fix after OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000344 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000344 12/11/2017 2:31 PM 46 For Official Use Only (b) (7)(E) • Issue Title: (b) (7)(E) • Priority Assignment: 2 • Change Area: Paper/Software (b) (7)(E) • Status: • • • • (b) (7)(E) Impact to SAT: (b) (7)(E) Impact to OT&E: Recommended Correction Date: Fix After OT&E (b) (7)(E) Work Around: BW7 FOIA CBP 000345 U.S. Customs and Border Protection ~ BOEING For Official Use Only DHS-17-0046-C-000345 12/11/2017 2:31 PM 47 (b)(6);(b)(7)(c) From: To: Cc: Subject: Date: Attachments: - Importance: FW: ACTION: GAO response RE: nPRS & Acquisition Decision Memorandum (ADM) Action Items Wednesday, January 27, 2010 10:29:23 AM 2010 Jan 22 Major Acq Pgm Weekly Rpt.pdf SBInet Action Item Closure Artifacts.zip NON-RESPONSIVE f NON-RESPONSIVE High Hello(b)(6); ,   (b)(7) On Nov 6, 209, SBInet provided a status on all of the open ARB open action items from the previous DHS ARBs and we reconciled (c)against your list. All of the open items were closed except for CBP ID 43 and 73.   I have attached the following:    our list   1. SBI Closure Artifacts provided on Nov 6, 2009 2. The ADM the closes CBP IDs: 75, 76, 77 and 78 3. The CBP SBInet Action Item List   The APMD Status of ADM Action Items “Action Completed” does not reflect several of the SBInet closed actions.   The Summary I sent on Nov 6, 2009: _____________________________________   CBP ID SBI ID Status Due Date File Name 43 ARB-13 Open - Under Review 11/30/2009   49 ARRA-1 Closed 11/2/2009 49 - ADM Brief - Pilot Project Plan.ppt 65 and 72 - SBI Presentation to DHS ARB 21 May 09 65 ARB-2 Closed 5/11/2009 v8.ppt 65 and 72 - SBI Presentation to DHS ARB 21 May 09 72 ARB-3 Closed 5/11/2009 v8.ppt 73 ARB-7 Open 6/30/2010   74 ARB-9 Closed 5/18/2009 74 - NB Final Letter Signed 5-18-2009.pdf 75 ARB-17 Closed 2/11/2009 75-76-77-78 SignedSBINetADM02 11 09.pdf 76 ARB-18 Closed 2/11/2009 75-76-77-78 SignedSBINetADM02 11 09.pdf 77 ARB-19 Closed 2/11/2009 75-76-77-78 SignedSBINetADM02 11 09.pdf 78 ARB-20 Closed 2/11/2009 75-76-77-78 SignedSBINetADM02 11 09.pdf     If you have any questions please do not hesitate to call or email me.   Thank you,   (b)(6);(b)(7)(c) SBI Business Operations Office Contractor supporting the Acquisition Management Division (AMD) Desk Te (b)(6);(b)(7) Cell Tel: (c) Email: (b)(6);(b)(7)(c) - From:( Sent: b Wednesday, January 27, 2010 7:25 AM To: (b)(6);(b)(7)(c) ) Cc: (b)(6);(b)(7)(c) ( Subject: ACTION: GAO response RE: nPRS & Acquisition Decision Memorandum (ADM) Action Items 6 Importance: High ) ; PMs, ( b Based) on an ongoing GAO audit from fall 2009, GAO is requesting data from the four CBP Acquisition Programs involved (SBI, ACE, TECS Mod, WHTI).  Your response is due Friday, 29 Jan. ( 7 The actions required are: ) 1.      Provide Acquisition Decision Memorandum (ADM) Action Item updates for each of the programs (SBI, ACE, ( TECS Mod, WHTI)—The “official” tally of ADM action items is attached, page 2.   c )   BW7 FOIA CBP 000346 DHS-17-0046-C-000346 2.      For action items that are late, provide a statement for each open action item explaining why required action has not been accomplished within the established timelines; what prevented the action from being accomplished within established timeline, when it will be completed; what is being done to ensure it will be completed—The “official” listing of overdue ADM action items is attached, page 3-5. 3.      Provide an nPRS Report—please ensure that nPRS data is current, complete, and accurate.  My staff will pull the report on Monday, Feb 01, and forward to APMD. - Please provide your responses(b)(6);(b)(7) Cc addressee by 3:00 PM, Friday, 29 Jan.  You staff should have been contacted by your program liaison (c) to begin working this action.  I am also available to answer any questions your may have. (b)(6);(b)(7)(c) Director, Acquisition Standards and Policy Acquisition and Program Management Office U.S. Customs and Border Protection Department of Homeland Security (DHS) 1331 Pennsylvania Ave, NW (b)(6);(b)(7)(c) Washington, DC 20229   Office: (b)(6);(b)(7)(c) Cell:    BW7 FOIA CBP 000347 DHS-17-0046-C-000347 Secure Border Initiative SBI Innovative Technologies Pilot Program (b) (6) Acting Deputy Director SBI Operational Integration Division October 2009 U.S. Custoins and Border Protection BW7 FOIA CBP 000348 DHS-17-0046-C-000348 Introduction • The SBI Operational Integration Division (OID) is currently developing a pilot program to seek innovative solutions and promising technology applications to enhance border control. • The purpose is to deliver capabilities to the operators in the field, provide them with the opportunity to give feedback, and to continually improve the SBI toolkit. • SBI OID released a series of Request for Information (RFIs) in order to determine if government or commercial (GOTS/COTS) products were available to meet operational needs within the following categories: • • • • • • (b) (7)(E) 2 BW7 FOIA CBP 000349 DHS-17-0046-C-000349 Project Pilot Scope • Funding to support this effort will primarily come from Border Security, Fencing, and Information Technology (BSFIT) • Selection Criteria: • Each commodity buy will be relatively inexpensive (approx. (b)(3) or less) • Within BSFIT scope • Small businesses preferred • Begin initial purchases by the end of CY09 • Cross-component impact preferred • Multiple Vendors preferred • SBI OID will coordinate with vendors for demonstrations of promising technology options and work with the acquisition office to procure items for use in the field. OID, in conjunction with the operating components, will establish a deployment plan to the southwest border and conduct an operational evaluation of all items procured. • SBI Commodity Buy Process - • • • • • Operator Facilitation Market Research Selection Evaluation Procurement Operational Field Evaluation BW7 FOIA CBP 000350 DHS-17-0046-C-000350 Current Project Status Commodity Purchases / Under Consideration • • (b) (7)(E) • • • Research conducted, selection pending (b) (7)(E) Options expensive/out of scope-coordinating (b) (7)(E) next steps with the Working Group *Procurements will continue through January (b) (7)(E) • • • • Research conducted, selection pending (b) (7)(E) Handled as a separate effort with OBP, research conducted Cost/Budget • Total budget for this effort remains the discretion of the SBI, Executive Director and has not yet been defined. (b) (7)(E) • • 7/17 – User Working Group: brainstorm list of potential items 7/23 – Component reps briefing/prioritization lists 7/31 – Reviewed prioritized “wish list” 8/1-9/30 – Conduct Market Research 10/14 – Identify Operationally Valid Options and targeted potential vendors for each commodity 11/1 – Release procurement announcement's) 12/1 – Execute initial procurements* (b) (7)(E) • Options Identified (b) (7)(E) • Options Identified • • Proposed Timeline (b) (7)(E) Agriculture and Trade • Options identified, pursuing GSA procurement Potential SBInet ARRA Funding Alternatives Plan: SBInet intends to spend up to $35M on Long Lead Items; Backup Plan: If the schedule to procure these long lead items slips the program may choose to use ARRA funds to: • Expand the scope of this Program Pilot effort to explore and evaluate additional technologies or • Buy additional operationally viable products requested by the Office of the Border Patrol. BW7 FOIA CBP 000351 DHS-17-0046-C-000351 From: To: Subject: Date: (b)(6);(b)(7)(c) Fw: SBInet Follow-ups Thursday, January 14, 2010 10:59:18 AM FYI. From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Sent: Wed Jan 13 12:58:49 2010 Subject: RE: SBInet Follow-ups - Ok – thanks (b) , much appreciated. (6);   (b) (7) (b)(6);(b)(7)(c) From: (c) Sent: Wednesday, January 13, 2010 12:42 PM To: (b)(6);(b)(7)(c) Subject: Re: SBInet Follow-ups Delays are caused by our commitment to review the quality and effectiveness of the system. As we have reported before, we had a number of technical issues we identified with the system as a resulting of testing over the last year. Although we did not feel any of the issues were "show-stoppers," we did feel it prudent to address each of them very deliberatively and comprehensively. As a result, we took the time to do full-engineering analysis, design corrections, and fully test the corrections. We've completed most of that, but it has taken time. It has also impacted the design of future testing--including the System Acceptance Testing and ultimately the Border Patrol's operational testing. We have to accommodate the system corrections into the detailed test planning, which is a comprehensive and time-consuming effort. We specifically chose NOT to take excessive short cuts, which might have made the near-term schedule appear better but would likely have created new delays in the future. To mitigate the delays, we are now working with Boeing so that we can use the "as is" system over the next few months, even before we do the extensive testing. In that way, we can get most of the operational benefit we would have gotten if we had been able to maintain the schedule, while still protecting the government equities to esnure we don't fully accept the system until we are ready. From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Sent: Wed Jan 13 12:19:43 2010 Subject: Re: SBInet Follow-ups 10-4. From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) > BW7 FOIA CBP 000352 DHS-17-0046-C-000352 (b)(6);(b)(7)(c) Sent: Wed Jan 13 12:19:04 2010 Subject: RE: SBInet Follow-ups For a radio package on AZ NPR – so they are looking for it as soon as possible.   From: (b)(6);(b)(7)(c) Sent: Wednesday, January 13, 2010 12:15 PM To: (b)(6);(b)(7)(c) ] Subject: Re: SBInet Follow-ups - (b)(6);(b)(7)(C) (b) is in a full day program update with the contractor. Can you provide a deadline? (6); (b) (7) From: (b)(6);(b)(7)(c) > (c) To: (b)(6);(b)(7)(c) Sent: Wed Jan 13 12:06:11 2010 Subject: RE: SBInet Follow-ups Another follow-up. – what is the reason for the delay?   Thanks!   From: (b)(6);(b)(7)(c) Sent: Tuesday, January 12, 2010 3:52 PM To: (b)(6);(b)(7)(c) Subject: RE: SBInet Follow-ups - Ok, thanks (b) (6); (b)(6);(b)(7)(C) (b) (b) (7) (6);   (c) (b) (7) From: (b)(6);(b)(7)(c) (c) Tuesday, January 12, 2010 3:48 PM Sent: To: (b)(6);(b)(7)(c) (b)(6);(b)(7)(C) ] Subject: RE: SBInet Follow-ups Are you asking about the review the Secretary directed?  If so, we don’t have that information in SBI.   From: (b)(6);(b)(7)(c) Sent: Tuesday, January 12, 2010 3:43 PM To: (b)(6);(b)(7)(c) ] BW7 FOIA CBP 000353 DHS-17-0046-C-000353 Subject: RE: SBInet Follow-ups Do we know how long the review will take? Thanks   From: (b)(6);(b)(7)(c) Sent: Tuesday, January 12, 2010 1:42 PM To: (b)(6);(b)(7)(c) ] Subject: Re: SBInet Follow-ups Work does continue. With respect to delays, we've said a MINIMUM of three months--which would be April. We don't have the final schedule yet because we have a variety of options that we're trading against risk and benefit. We expect to lock down the schedule in the next couple of weeks. From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Sent: Tue Jan 12 13:38:37 2010 Subject: Re: SBInet Follow-ups -(b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Looping (b) and (b) (6); (6); (b) (b)(7) (7) (c) (b)(6);(b)(7)(c) From: (c) To: (b)(6);(b)(7)(c) > Sent: Tue Jan 12 13:34:38 2010 Subject: RE: SBInet Follow-ups (b)(6);(b)(7)(C) Meant to ad (b) (6);   (b)(7) (c) From: (b)(6);(b)(7)(c) Sent: Tuesday, January 12, 2010 1:34 PM To: (b)(6);(b)(7)(c) Subject: SBInet Follow-ups (b) (6) from The Daily Star in AZ had a couple follow-up questions, both of which I just wanted to confirm answers for and make sure it was ok to verify for him.   How long has the project been delayed this time? When is the new estimated delivery date? (I had heard March or April) • Is work halted on the project during the review? (No – work continues)   Thanks, • (b)(6);(b)(7)(c) BW7 FOIA CBP 000354 DHS-17-0046-C-000354 Deputy Press Secretary Office of Public Affairs U.S. Department of Homeland Security O (b)(6);(b)(7)(c) C(b)(6);(b)(7)(c) BW7 FOIA CBP 000355 DHS-17-0046-C-000355 From: To: Subject: Start: End: Location: (b)(6);(b)(7)(c) SBInet Planning Meeting Thursday, January 21, 2010 11:00:00 AM Thursday, January 21, 2010 1:00:00 PM 1901 S. Bell St (Crystal City), Room 624 When: Thursday, January 21, 2010 11:00 AM-1:00 PM (GMT-05:00) Eastern Time (US & Canada). Where: 1901 S. Bell St (Crystal City), Room 624 *~*~*~*~*~*~*~*~*~* Just a follow up to be snure everyone has details about meeting location. You can call my assistant, (b)(6);(b)(7)(c) when you arrive--she will meet you in the lobby to provide access to the 6th floor. My phone is (b)(6);(b) if you need it. (7)(c) See you at 11:00! BW7 FOIA CBP 000356 DHS-17-0046-C-000356 From: To: Subject: Date: (b)(6);(b)(7)(c) (b) (6) Re: story ? Wednesday, January 13, 2010 8:13:14 AM Why does that not surprise me - lead with a press statement and then figure out the review...the only good thing I can think of is that (b)(6);(b)(7)(c) - is gone; he would have done his own review with the sheriffs and we would have ended up with a new set of requirements for them ----- Original Message ----From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc:(b)(6);(b)(7)(c) Sent: Wed Jan 13 08:05:51 2010 (b) (6) Subject: Re: story ? No.  I think DHS is still figuring it out.  They're trying to schedule a meeting for Thursday or Friday to structure it. ----- Original Message ----From:(b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Wed Jan 13 07:50:42 2010 (b) (6) Subject: Re: story ? Do we have any visibility on the state/local piece of the review?  Or who else within dhs will be involved? And, can opa please send the statement to (b)(6);(b)(7)(c) with the CBP Audit team? Thanks, (b) (6); (b) (7)(c) ----- Original Message ----From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Wed Jan 13 07:48:41 2010 (b) (6) Subject: Re: story ? 1111 Sending the statement was their version of responding to inquiries. ----- Original Message ----From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Wed Jan 13 07:10:53 2010 Subject: Re: story ? (b) (6) I never heard any suggestion of pulling the statement back.  I thought DHS was simply sending the statement out in response to any and all press queries. BW7 FOIA CBP 000357 DHS-17-0046-C-000357 ----- Original Message ----From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Wed Jan 13 07:08:42 2010 (b) (6) Subject: story ? Did we know dhs was sending S1's statement re: the sbinet review to him?  I thought they pulled it back.  I am still concerned about the state/local review piece.  Unless something changed recently, I thought we were building a system for BP. BW7 FOIA CBP 000358 DHS-17-0046-C-000358 From: To: Subject: Date: - (b)(6);(b)(7)(c) If I were in your shoes what would I think about Thursday, January 14, 2010 5:30:22 PM (b)(6); (b)(7)   (c) This is just my two cents, I have been reluctant for a number of reasons to provide before, but I have held back too long.  You have tough decisions to make, and while they are your decisions I hope others perspectives might assist you in forming your own path forward.   You came into a program in bad shape.  You have put your heart and sole into improving the process and gaining an acceptable system for your customer.  However, since you seem to like analogies, you have been trying to teach a pig to sing.  All that has been accomplished is irritating the pig, it still cannot sing, and has no desire to sing.  I want to be sure however, to make sure you know the problem is wider than just the prime contractor.     Significant amounts of funds have been put against this SBInet endeavor.  And although the SBInet product is not what was expected, it does have some capability that will be useful to our customer.  As you have noticed, the rate of uncovering problems continues to be greater than the rate of solving those problems, even considering the many that are agreed to be ignored.  There are still several major steps before we can accept the system.     (b) (7)(E) and even incremental steps toward a real solution has value.  The problems that exist are in two categories, cleaning up paperwork and real changes to system required.   If I were in your shoes there are several options worth considering.   1. Stop everything and decide if another attempt should be made 2. Continue deployment effort for (b) (7)(E) and stop everything else and decide if another effort should be made 3. Decide Boeing is our partner and reevaluate how we are approaching improving the quality of the product provided.     Options 1 and 2 are just slight variations on the theme of cutting losses and starting over.  Canceling SBInet for the convenience of the government stops the hemorrhage of funds with little progress.  It however provides no capability for the spend dollars.  The question of “is the SBInet that has been produced worth operating and maintaining” needs answering.  Now we cannot even get in to the test event to evaluate the capability.  Boeing has little incentive to make progress, because they fear this is the end and no fee is better than no program.  If the path to is to get(b) (7)(E) deployed, I would recommend picking a date this spring at the latest, and telling Boeing the test will commence on this date.  Results of this test will decide if SBInet is cancelled or just future work cancelled.     Option 3, reaffirms that Boeing is our trusted supplier, but requires totally changing the management approach taken.  The theory has been for many years that quality of a product is 85% management.  Management on both the government and Boeing side must take responsibility for the quality of the effort thus far, and change so the quality of future effort is BW7 FOIA CBP 000359 DHS-17-0046-C-000359 high.  Today’s management accepts responsibility, but does not push responsibility to the working level.  The working level is disenchanted, because so many decisions are made at the upper levels of management without input.  There is too much backroom negotiations on what to do and how to pass.  Too little on how to make this a quality product and make the process repeatable.  We have trained Boeing that poor quality is acceptable for schedules sake.  Basic contract management is not well executed.    Most of this is self obvious.  The possibility of stopping work, while using (b) (7)(E) is unusual.  There is a possibility of using the maintenance Task Order to fix the remaining problems.  Why do we need acceptance testing if we are going to stop work, if we are not going for a production decision?     SBInet is not that complicated.  Many vendors should be able to construct and deploy SBInet towers and stations..  A separate product improvement program will be more effective than one run by a large prime.  Use Boeing where they are good, and stop using them where they are just expending funds.     While I am deeply familiar with effort on SBInet Block 1,  and somewhat familiar with (b) (7)(E) and (b) (7)(E) I have no visibility into Northern Border or other projects. I do recommend stopping everything you can, and holding a stand down for CMMi training.  If we want to hold our contractor to CMMi level 3, then the program office should be held to the same standard.     I would gain approval of your plan, because it is obvious Boeing will attempt to make this your fault not theirs.  I think you have sufficient documentation to show otherwise.    I hope this is helpful, if not the trash can is near by.  Sorry it is longer than I wanted.  I will keep on pressing forward at the working level.    respectfully - - - (b)(6);(b)(7)(C) BW7 FOIA CBP 000360 DHS-17-0046-C-000360 From: To: Subject: Date: (b)(6);(b)(7)(c) RE: House Homeland request Thursday, January 21, 2010 7:44:51 AM Thanks! We’ll be ready. (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(c) Sent: Wednesday, January 20, 2010 6:12 PM To: (b)(6);(b)(7)(c) Subject: RE: House Homeland request Just to follow up – I spoke to both House Homeland majority/minority, and gave the high-level update that we discussed regarding the items that needed to be fixed prior to SAT (b) (7)(E) as two biggies, but mostly just procedural corrections), and the reasons behind the extension of SAT. A few things that did come out of the phone calls: · Majority staff is still interested in getting a high-level summary at some point of the SQT issues, but it is not as pressing. · Minority staff indicated that a letter would be forthcoming (addressed to S1) requesting more information on the "DHS review” -- and likely a general dissatisfaction/frustration with the continued delays (i.e., why do these issues continue to pop up/why are they not discovered sooner). · Potential date for SBInet hearing – March 18. Senate Homeland had the Secretary testifying this morning and staff have been pretty much unreachable over the past couple weeks, so I’ll give them a call tomorrow morning and let you know how those calls go. - (b) (6); (b)(7) (c) -----Original Message----From: (b)(6);(b)(7)(c) Sent: Wednesday, January 20, 2010 12:02 PM To: (b)(6);(b)(7)(c) Subject: FW: House Homeland request (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000361 DHS-17-0046-C-000361 -----Original Message----From: (b)(6);(b)(7)(c) Sent: Saturday, January 09, 2010 4:01 PM To:(b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: RE: House Homeland request - • (b) : Here's a quick look at the 47 items from SQT2 that we've agreed need to be fixed prior to (6); SAT. We'll certainly want to package this differently to give to (b) . Last week (b)(6);(b)(7)(c) (b) (6); description of each bin. We can starting work on binning these into categories along with a top level (7)(c) (b)(7)it a higher priority (we have probably have that done sometime Monday unless we need to make (b) (7)(E) several meeting scheduled with Boeing Monday morning on (c)and SAT related topics). Thanks (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. -----Original Message----From: (b)(6);(b)(7)(c) Sent: Saturday, January 09, 2010 12:28 PM To: (b)(6);(b)(7)(c) Subject: Re: House Homeland request (b) : I think the number is 47, but will confirm. We actually worked on this same type of info for (6); (b)(6);(b)(7) late yesterday. As soon as I get back home I'll mobikey into my computer and try to (b) (c) retrieve the data and send it to you. (7)(c) (b)(6);(b)(7)(C) Executive Program Director, SBInet U.S. Customs and Border Protection, DHS (b)(6);(b)(7)(C) ----- Original Message ----From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Sat Jan 09 12:12:18 2010 Subject: Re: House Homeland request BW7 FOIA CBP 000362 DHS-17-0046-C-000362 - Hi, (b) . (6); (b)(7)to track down the details but we can certainly do that early next week. The 42 is an old I'll have (c) so it may be a bit difficult to recreate that exaxct list--but we should be able to meet the number intent of the question. I'm probably going to be the best POC, at least on Monday--I've pretty much blocked off my calendar to deal with this type of stuff. ----- Original Message ----From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Sent: Sat Jan 09 12:05:55 2010 Subject: House Homeland request (b)(6);(b)(7)(c) - I received an email from (b)(6); last night requesting additional information on the 42 issues that (b)(7)that Boeing is required to fix before SAT. I anticipate getting similar arose during the second SQT usual POCs, and probably several other folks after 60 Minutes airs. questions from our other (c) This by no means needs to be answered this weekend, but I at least wanted to make you aware. Also, since I know you'll be responding to a lot of media inquiries as well on Monday, I wanted to check and see if I should direct my questions to (b) , or if I should still send along to you? • Hope you're having a nice weekend! - (b) (6); (b)(7) (c) (6); (b) (7) (c) BW7 FOIA CBP 000363 DHS-17-0046-C-000363 From: To: Subject: Date: Sensitivity: (b)(6);(b)(7)(c) Fw: SBI Call Feedback Tuesday, January 12, 2010 8:08:37 AM Confidential Fyi - (b)(6);(b)(7)(C) Do you have time to chat before or after your ESC mtg with Chief today? I told nd AMS I am concerned with the state/local input piece and that CBP needs to take a lead role on future outreach. - Thanks, (b) (6); (b)(7) (c) From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7) (c)Mon Jan 11 17:21:04 2010 Sent: Subject: SBI Call Feedback (b)(6);(b)(7)(C) > FOR OFFICIAL USE ONLY   (b)(6);(b)(7)(c) Below is the listing for the calls we made on Friday night and the little bit of response we received. If you have any questions, please let us know. Thanks, ------(b)(6);(b)(7)(C) (b) (6);   (b)(7) CALIFORNIA (c) Contact: (b) · · · · (6) Chief of Staff, CalEMA Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. Said that the review would not impact current operations.  Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. RESPONSE:  Thanks for heads up.  (b)(6);(b)(7)(C) on the way to meet with Governors office and he would bring up.   (b) (6) Contact: Governor’s DC office.  · Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. · Said that the review would not impact current operations.  · Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. · Left msg.  (b)(6);(b)(7)(C) followed up w email “Thanks for the heads up!”   ARIZONA (b) (6) Contact:  HSA · Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. · Said that the review would not impact current operations.  - BW7 FOIA CBP 000364 DHS-17-0046-C-000364 · · Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. RESPONSE: Said thanks for the heads up and he would communicate to Deputy COS (b) (6) - (b) (6) -   NEW MEXICO Contact:   HSA (b) (6) · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Said thanks for the heads up   TEXAS (b) (6) Contact:  HSA · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Good, the system is a waste of billon dollars   Phoenix Contact: Mayor (b) (6) via email (his preference) · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Said “thanks for the heads up -   Los Angeles (b) (6) Contact: Office of the Deputy Mayor for Public Safety · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Heads up was appreciated   San Diego (b) (6) Contact:  DC Representative via email · Communicated that S1 will be calling for a review of the SBINet program in the next couple of days · Stated that the review will seek input from the four SW border states as provided in the TPs · RESPONSE:  Appreciated the notice    Tucson (b) (6) Contact: Mayor’s Chief of Staff · Sent him an email to call as he was out of the office on Friday · No response   BW7 FOIA CBP 000365 DHS-17-0046-C-000365 TON Contact: (b) (6) Chairman’s Assist · Communicated to the TON was that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet and that it did not impact current operations · No mention of them being part of the system review as I did not have the facts as to how the review would take them into account · RESPONSE:  Expressed concern as to how this would impact the towers as he thought some of them were going to also be used for LE and some of the environmental impact assessments that have been hurried through the system   BORDER COUNTIES COALITION (b) (6) Contact:  · Communicated that the Secretary was announcing on the 60 minutes piece that she planned to do a review of SBINet to ensure that the project was delivering. · Said that the review would not impact current operations.  · Mentioned that review would solicit input from Congress, GAO, and border stakeholders and that they would be consulted. · RESPONSE: Said “Oh, good.” Very appreciative of heads up.  Mentioned that BCC would be meeting during annual NACO meeting and suggested Departmental presence at meeting.  Will follow up with me via email.    FOR OFFICIAL USE ONLY     (b)(6);(b)(7)(c) Deputy Assistant Secretary Intergovernmental Affairs U.S. Department of Homeland Security (O) (b)(6);(b)(7)(c) (F)  (E)    Warning: This communication, along with any attachments, is covered by federal and state law governing electronic communications and may contain confidential and legally privileged information such as found under 49 CFR 1520 or the Privacy Act of 1974. It should not be communicated to any person, or agency, unless disclosure is in performance of official DHS duties and there exists a valid need to know.  If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, use or copying of this message is strictly prohibited.  If you have received this in error, please reply immediately to the sender and delete this message.     BW7 FOIA CBP 000366 DHS-17-0046-C-000366 From: To: Subject: Date: -- (b)(6);(b)(7)(c) FW: SBInet ARB Recap Tuesday, January 19, 2010 4:48:02 PM (b)(6);(b)(7)(C) (b) (6); (b)(6);(b)(7)(C) (b) Here’s the summary we wrote about our ARB review with S2. We sent it to the Department (b) (b)(6);(b)(7)(C) (7) (6); hop), and they then sent it to the PMs in DHS… (c) (b) (7)(c) USM a few As noted below, our review to S2 was a follow-up to the actual decision ARB that had gone to weeks before. - (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(c) Sent: Thursday, June 04, 2009 10:11 AM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: SBInet ARB Recap Program Managers, (b)(6);(b)(7)(C) The following is a recap of the SBInet ARB, which was the first presented to (b)(6); I passed my (b)(7)(c) comments to (b)(6);(b)(7)(c) , and he added depth from the perspective of “man in the seat”. This ARB was Informational; SBInet met a Decisional ARB, chaired b (b)(6);(b)(7)(C) DHS/USM, on 21 May, and received an Acquisition Decision Memorandum on 26 May. (b)(6);(b)(7)(C) The ARB was scheduled for 1 ½ hours. Although this was an Acquisition forum, (b)(6);(b) questions (7)(c) were quite broad and extended well beyond just acquisition. Some of that may be due to the fact this was the first ARB and her first opportunity to set a tone. However, she was also genuinely interested in BW7 FOIA CBP 000367 DHS-17-0046-C-000367 understanding the “substance” of the program, outside of acquisition processes…operating environment, terminology, concepts of operation, benefits, relative costs, technology, etc. Her questions drilled down to the third and fourth level of indenture, which spawned further questions from the staff. The Deputy Secretary asks a LOT of questions, and they range from very broad to very detailed. In most cases, they really WERE questions and she was interested and attentive to the answers. She clearly tried hard to understand the answers—she listened carefully and thought about what she heard. She worked hard to get beyond specific words and to the actual intent of the answers. It appears that our briefers should feel free to provide answers to questions and to defend them. The Deputy Secretary appears willing to be convinced by a good explanation or argument. And in cases where she doesn’t agree with the briefer’s conclusions, she still seems to appreciate conclusions that are based on thought and rationale argument. -- (b)(6);(b)(7)(C) (b)(6); is very quick, which suggests it would be folly for any briefer to “fake” an answer. (b)(7)(c) (b)(6);(b)(7)(C) (b)(6); is very concerned about the way we manage our programs, and about whether or not we have (b)(7)(c) the requisite skills in adequate depth, breadth, and quantity. She perceives industry as trying to sell us more than we need and is interested in our ability to weigh capability against the validated requirement. (b)(6); spends time ensuring a common understanding of words and phrases that we have typically (b)(7)(c) taken for granted. For example, she asked about the appropriate use of terms like “force multiplier versus force enabler” and “commodity”—and then challenged our use of them. In doing so, she made clear she was not trying to be confrontational—instead, she wanted to make sure everyone understood how SHE interpreted the word when she saw it. She commented on distribution markings on charts and asked why they were there, and if they were used properly. Briefers should be prepared to explain the use of any word on a chart or in a statement. (b)(6);(b)(7)(C) The Deputy Secretary was equally able to drill into technical details. She can quickly connect information from multiple charts to identify seeming inconsistencies, and then ask about them. For example, the . In a later chart, SBInet briefing referenced the fact that we accommodated (b) (7)(E) where we discussed predicted system performance, she noticed we didn’t count the contribution of those (b) (7)(E) and she asked a number of questions about why we handled things that way. - In short, briefers should be able to explain why they have made the conclusions and decisions they have (b)(6);(b)(7)(C) made—and the rationale needs to be sound. Briefers should understand that (b)(6);(b) questions really (7)(c) are questions—at least within the SBInet ARB, they were NOT purely rhetorical. And briefers should be able to explain word choices on charts or in verbal statements—clarity of communication and common understanding of meanings are very important. At the conclusion of the 1 ½ hour session 21 of the fifty slides were briefed. The takeaway is…in addition to being prepared to present your programs for an Acquisition Decision Event, be as prepared for an indepth discussion of the history, context, inter-relationships, and relevance of your program as the Deputy Secretary spins up on our programs. Respectfully, (b)(6);(b)(7)(C) Investment Management Office (IMO) Office of Finance U.S. Customs and Border Protection Department of Homeland Security (DHS) 1331 Pennsylvania Ave, NW (b)(6);(b)(7)(C) Washington, DC 20229 BW7 FOIA CBP 000368 DHS-17-0046-C-000368 Of?ce: (6) (C) Cell: BW7 FOIA CBP 000369 DHS-17-OO46-C-000369 From: To: Subject: Date: - (b)(6);(b)(7)(c) Can we help? Monday, January 25, 2010 1:00:35 PM (b)(6);(b)(7)(C) (b) (6);   (b)(7) (c) We (the Battelle we) came across this article today. Please let us know if we can help with the assessment or the IV&V. I hope your holidays were good. (b)(6);(b)(7)(C) (b)(6);(b) (7)(c)    Boeing's SBInet project under fire again Napolitano says electronic fence has 'unacceptable delays'   Homeland Security Secretary Janet Napolitano has ordered a reassessment of the $8 billion SBInet virtual border fence program in Arizona after another round of delays in the program, an official confirmed today. Boeing Co. is the prime contractor on the project. SBInet is an electronic surveillance system composed of cameras, radars and other sensors strung on towers and coordinated with other sensor systems, communications and command and control networks. U.S. Customs and Border Protection recently has been deploying a 23-mile segment of the system near Tucson, Ariz. Napolitano requested the SBInet reassessment Jan. 8 after an internal evaluation revealed “unacceptable delays” in the program, according to a Jan. 11 e-mail message from Napolitano provided today by Matthew Chandler, a Homeland Security Department spokesman. Although the message did not state the extent of the delays, the Seattle Times recently reported that the initial operational segment, known as Tucson-1, would be three months late in beginning operation. Instead of beginning operation at the end of 2009, the operation has been delayed to March 2010, the newspaper said. Napolitano indicated in her message that SBInet continues to fall short of expectations. “Americans need border security now — not 10 years down the road. I am committed to ensuring that our border security programs are timely and costeffective,” Napolitano wrote. “This fall, due to my ongoing concerns about SBInet, I directed the acting commissioner of U.S. Customs and Border Protection to evaluate its implementation. As his analysis uncovered unacceptable delays, last Friday I ordered a department-wide reassessment of the program to consider options that may more efficiently, effectively and economically meet our border security needs,” BW7 FOIA CBP 000370 DHS-17-0046-C-000370 Napolitano wrote. Mark Borkowski, project manager for the Secure Border Initiative, which includes SBInet and other fencing programs, told Federal News Radio recently that the next segment of the project, Ajo-1, will be built as scheduled, but Boeing will not begin any new work until the reassessment is completed. Boeing got the initial SBInet contract in September 2006, and first built an 18-mile prototype of the system near Sasabe, Ariz. The border patrol has been using that prototype segment in its daily operations to protect against border incursions since it was accepted by DHS in February 2008. Borkowski a year ago said the system was undergoing additional testing before permanent construction would begin.       (b)(6);(b)(7)(C) Relationship Manager Battelle Office of Homeland Security 1150 Crystal Drive, (b)(6);(b)(7)(C) Arlington VA 22202 Phone (b)(6);(b)(7)(C) Cell (b)(6);(b)(7)(C) Email (b)(6);(b)(7)(C)   - BW7 FOIA CBP 000371 DHS-17-0046-C-000371 (b)(6);(b)(7)(c) From: To: Subject: Start: End: Location: Accepted: SBInet Planning Meeting Thursday, January 21, 2010 11:00:00 AM Thursday, January 21, 2010 1:00:00 PM 1901 S. Bell St (Crystal City), Room 624 BW7 FOIA CBP 000372 DHS-17-0046-C-000372 - From: To: Subject: Date: (b)(6);(b)(7)(c) Re: SBInet Planning Meeting Thursday, January 21, 2010 10:44:31 AM - (b) - will be about 10 minutes late - see you then - (b)(6);(b)(7)(C) (b) (6); (6); -------------------------(b) (b) Sent using BlackBerry (7)(c) (7) (c) From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) (b)(6);(b)(7)(C) Sent: Thu Jan 21 08:06:13 2010 Subject: SBInet Planning Meeting When: Thursday, January 21, 2010 11:00 AM-1:00 PM (GMT-05:00) Eastern Time (US & Canada). Where: 1901 S. Bell St (Crystal City), Room 624 *~*~*~*~*~*~*~*~*~* Just a follow up to be snure everyone has details about meeting location. You can call my assistant, (b)(6);(b)(7)(c) provide access to the (b)(6); (b)(7)(c) My phone is(b)(6);(b)(7)(c) if you need it. when you arrive--she will meet you in the lobby to See you at 11:00! BW7 FOIA CBP 000373 DHS-17-0046-C-000373 From: To: Subject: Date: (b)(6);(b)(7)(c) RE: SBInet Meeting Thursday, January 28, 2010 7:47:18 AM (b)(6);(b)(7)(C) 10-4. We’re obviously not doing anything irrevocable—we’re just getting foundations laid so we can move out expeditiously. All subject to change and review… I’ll look forward to meeting with you soon. (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(c) Sent: Thursday, January 28, 2010 7:47 AM To: (b)(6);(b)(7)(c) Subject: Re: SBInet Meeting ] (b)(6);(b)(7)(C) (b) (6); (b) Thanks for your message. (7)(c) I would like to spend an hour with you before we get too far down the path. Given your extensive knowledge, that would be helpful. I have scheduled a couple of pre-meetings, one with the MGMT chiefs this morning and one with OLA, IGP and OPA, to make sure there is general visibility in the various offices that have a nexus to the work. Look forward to working with you. (b)(6);(b)(7)(C) Chief of Staff for Management Department of Homeland Security Washington, DC (b)(6);(b)(7)(C) office BB From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Thu Jan 28 07:38:01 2010 Subject: RE: SBInet Meeting BW7 FOIA CBP 000374 DHS-17-0046-C-000374 - (b)(6);(b)(7)(C) Hi, (b)(6); (b)(7) (c)thought I should follow up to see what you need, if anything, from us. I just We did have a small follow-up meeting, as I indicated below. We have sketched out a basic outline of a “plan of attack,” which includes near-, mid-, and far-term activities. Based on that sketch, we are starting to lay out implementation plans. In particular, we’re laying out a preliminary strategy to get started on a formal Analysis of Alternatives for the long-term assessment. We’ve also generated a list of near-term candidates for technology investments (other than SBInet Block 1) that could fill immediate gaps along the Southwest Border by diverting about $35M of ARRA funds that we had originally planned for SBInet Block 1. - (b)(6);(b)(7)(C) As I understand (b) (7) note, you have the lead for pulling us all together for any follow-up review and (E) be happy to support as required. status update. We’ll Best, (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(c) Sent: Monday, January 25, 2010 8:48 AM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: Re: SBInet Meeting - (b)(6);(b)(7)(C) Thank (b) Yes, let's have update session when everyone can make it. (6); (b) As we discussed at our first, organizational meeting, it makes most sense for Management to coordinate (b)(6);(b)(7)(C) (7)(c) this reassessment . Accordingly, Chief of Staff (b)(6);(b)(7)(C) will be our chair. Pls work with regarding agenda items, etc. - Thanks, and see you this week. -------------------------Sent using BlackBerry From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) > Cc: (b)(6);(b)(7)(c) Sent: Fri Jan 22 18:16:16 2010 Subject: RE: SBInet Meeting -(b)(6);(b)(7)(C) (b) all day Monday, and Tuesday through noon, are bad for me – rest of the week is easier. (6);   (b)(6);(b)(7)(C) (b) Thanks, (b) (7) (6); (c) (b) BW7 FOIA CBP 000375 (7) DHS-17-0046-C-000375 (c)   From: (b)(6);(b)(7)(c) ] Sent: Friday, January 22, 2010 6:14 PM To ( b Cc:)(b)(6);(b)(7)(c) Subject: RE: SBInet Meeting ( 6 Hello ) everyone, ; I will( reach out on Monday to schedule this meeting for next week. If anyone has days that you know will absolutely not work for the meeting just let me know when you have a chance and I will work around it. b Have ) a great weekend! ( (b)(6);(b)(7)(C) 7 ) ( c of the Secretary Office ) of Homeland Security Department (b)(6);(b)(7)(C) (cell) From: (b)(6);(b)(7)(c) Sent: Friday, January 22, 2010 10:59 AM To: (b)(6);(b)(7)(c) ] Cc: (b)(6);(b)(7)(c) Subject: RE: SBInet Meeting - (b)(6);(b)(7)(C) (b)(6); (b)(7)(c) As we discussed last week, our small group met yesterday to sketch out a structure for the review. I think (b)(6);(b)(7)(C) (b) wanted to have a quick follow-up so he could stay apprised of status and direction. Is that (6); something you can orchestrate? (b) (b)(6);(b)(7)(C) (7) (c) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000376 DHS-17-0046-C-000376 (b)(6);(b)(7)(c) From: To: Subject: Date: Attachments: UPDATE Thursday, January 07, 2010 5:40:49 PM SBInet update for MrB 010710.ppt (b) Since I won’t be able to give you my bi-weekly update tomorrow, attached are the slides I would 1111 (6); have used. (b) (7)(c) Thanks (b)(6);(b)(7)(c) Executive Program Director, SBInet U.S. Customs and Border Protection, Department of Homeland Security Note: The Contracting Officer is the sole individual authorized to make changes to the contract on behalf of the Government. The content of this email is not intended to change the existing scope of contract. If the Contractor considers any part of this communication to constitute a change in scope, the Contractor shall notify the Contracting Officer in accordance with FAR Clause 52.243-7, Notifications of Changes. BW7 FOIA CBP 000377 DHS-17-0046-C-000377 For Official Use Only SBInet Southern Border Project Update January 8th, 2010 U.S. Customs and Border Protection BW7 FOIA CBP 000378 DHS-17-0046-C-000378 1 For Official Use Only (b) (7)(E) Status (b) (7)(E) • (b) (7)(E) – Completed (b) (7)(E) integration and checkout Completed(b) (7)(E)Characterization – Govt Inspection closure 1000 of 1004 completed – • - Issues and Concerns – Final Acceptance behind schedule due to issues including: • • • • • Field Construction CISCO/VSOC issues (b) (7)(E) Software changes/fixes as a result of SQT 2 Acceptance test procedures and tower functional checkout procedures still ongoing Look ahead - Next 90 Days – – Finalize test procedures Finalize remaining schedule to Acceptance BW7 FOIA CBP 000379 DHS-17-0046-C-000379 2 For Official Use Only • (b) (7)(E) (b) (7)(E) C2 Modular Facility Accomplishments − Received the Findings of No Significant Impact Statement (23 Dec) − Received Special Use Permit (b) (7)(E) ) and Right of Way for construction (BLM). − Awaiting compatibility determination (b) (7)(E) from (b)(6);(b)(7)(c) − Conducted Deployment Readiness Review on December 2nd. - - • Status Concerns − Closure of the RAT design − Obtain GSA approval to − - (b) (7)(E) (b) (7)(E) (b) (7)(E)construction schedule encroaching on Pronghorn Fawning Season − Additional BMPs and measures required • Look Ahead - Next 90 days − Receive land use permits − Conduct CRR − Start (b) (7)(E) onstruction - BW7 FOIA CBP 000380 DHS-17-0046-C-000380 3 For Official Use Only (b) (7)(E) • - (b) (7)(E) – Accomplishments Completed Supplemental EA Public Review, now in internal SBInet review • Issues and Concerns (b) (7)(E) – working through landowner issues – SST and SST combo design approval not final • Look Ahead – Next 90 days – Work on real estate effort • Conduct Metes and Bound Surveys • Perform Land appraisals (b) (7)(E) – Conduct design TIM (b) (7)(E) – Conduct C2 Facilities Design TIM (b) (7)(E) – Conduct (b) (7)(E) – Work design drawing package from 60% to 95% Status (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) BW7 FOIA CBP 000381 DHS-17-0046-C-000381 4 For Official Use Only (b) (7)(E) • - • Accomplishments Completed Supplemental EA Public Review, now in internal SBInet review Issues and Concerns – (b) (7)(E) – • (b) (7)(E) (b) (7)(E) – Status - i Working through (b) (7)(E) access road issue. (b) (7)(E) (b) (7) (E) (b) (7)(E) Look Ahead - Next 90 days – Progress engineering effort • Conduct (b) (7)(E) – Work on real estate effort • Conduct Metes and Bound Surveys • Perform Land appraisals • Work design drawing package from 60% to 95% (b) (7)(E) (b) (7)(E) BW7 FOIA CBP 000382 DHS-17-0046-C-000382 5 For Official Use Only (b) (7)(E) • - TON Accomplishments (b) (7)(E) – Held briefing with ouncil – – 11/19/09 Held environmental meeting (b) (7)(E) 12/8/09 Initial site surveys on the (b) (7)(E)held week of 12/14/09 - • Issues and Concerns • Look Ahead – Next 90 days – Initial site surveys continue in other Districts (b) (7)(E) from 1/11 through February 2010 (b) (7)(E) – DPR 3/25/10 (tentative) Status (b) (7)(E) (b) (7)(E) (b) (7)(E) - BW7 FOIA CBP 000383 DHS-17-0046-C-000383 6 For Official Use Only SBInet Northern Border Project Update January 8th, 2010 U.S. Customs and Border Protection BW7 FOIA CBP 000384 DHS-17-0046-C-000384 7 For Official Use Only (b) (7)(E) Site Name (b) (7)(E) I&CO Completed 01/05/10 Site Status Northern Border Project (b) (7)(E) o 1/6/10 2009 2010 December February January (b) (5) 12/23/09 (b) (7)(E) 12/28/10 01/04/10 01/04/10 12/28/09 12/30/10 (b) (7)(E) Additional Notes: 1. Lengthy NTIA process caused delay in Government acceptance. 2. A previous problem with the (b) (7)(E) 3. (b) (7)(E) Estimate starting Dry Runs on January ) has been resolved. 15th. is pursuing a long term solution to (b) (7)(E) . BW7 FOIA CBP 000385 DHS-17-0046-C-000385 8 For Official Use Only (b) (7)(E) Site Name (b) (7)(E) I&CO Completed 02/23/10 Site Status Northern Border Project (b) (7)(E) 1/4/10 2010 01/18/10 January February March (b) (5) 01/15/10 01/20/10 (b) (7)(E) 01/19/10 01/21/10 01/22/10 01/14/10 01/13/10 02/22/10 02/17/10 (b) (7) (E) 01/25/10 Additional Notes: 1. Delay due to challenges obtaining lease for (b) (7)(E) 2. A previous problem with the (b) (7)(E) . ) has been resolved. BW7 FOIA CBP 000386 DHS-17-0046-C-000386 9 From: To: Subject: Date: (b)(6);(b)(7)(c) RE: SBInet Meeting Thursday, January 28, 2010 7:51:54 AM - Great—thanks. I hadn’t heard anything from o I figured I’d “shake the tree a bit.” If stuff is happening, that’s good. It just seemed awfully quiet! (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection From: (b)(6);(b)(7)(c) Sent: Thursday, January 28, 2010 7:52 AM To: (b)(6);(b)(7)(c) Subject: Re: SBInet Meeting -- (b)(6);(b)(7)(C) ] just for your situational awareness - there is a "USM staff only" meeting w/ (b)(6);(b)(7)(c) (b)(6);(b)(7)(C)and me) at 1030 today on SBInet. No agenda...I'll let you know what transpires. (b)(6);(b)(7)(C) -------------------------Sent using BlackBerry From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Thu Jan 28 07:38:01 2010 Subject: RE: SBInet Meeting - Hi, (b)(6);(b)(7)(C) I just thought I should follow up to see what you need, if anything, from us. We did have a small follow-up meeting, as I indicated below. We have sketched out a basic outline of a “plan of attack,” which includes near-, mid-, and far-term activities. Based on that sketch, we are starting to lay out implementation plans. In particular, we’re laying out a preliminary strategy to get started on a formal Analysis of Alternatives for the long-term assessment. We’ve also generated a list of near-term candidates for technology investments (other than SBInet Block 1) that could fill immediate gaps along the Southwest Border by diverting about $35M of ARRA funds that we had originally planned for SBInet Block 1. - As I understand note, you have the lead for pulling us all together for any follow-up review and status update. We’ll be happy to support as required. (b)(6);(b)(7)(C) Best, (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) BW7 FOIA CBP 000387 DHS-17-0046-C-000387 Customs and Border Protection From: (b)(6);(b)(7)(c) Sent: Monday, January 25, 2010 8:48 AM To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(c) Subject: Re: SBInet Meeting Thanks - (b)(6);(b)(7)(C) Yes, let's have update session when everyone can make it. As we discussed at our first, organizational meeting, it makes most sense for Management to coordinate this reassessment . Accordingly, Chief of Staf (b)(6);(b)(7)(C) will be our chair. Pls work with (b)(6);(b)(7)(C) regarding agenda items, etc. Thanks, and see you this week. -------------------------Sent using BlackBerry From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Fri Jan 22 18:16:16 2010 Subject: RE: SBInet Meeting -(b)(6);(b)(7)(C) all day Monday, and Tuesday through noon, are bad for me – rest of the week is easier.   (b)(6);(b)(7)(C) Thanks, (b)(6);(b) (7)(c)   From: (b)(6);(b)(7)(c) Sent: Friday, January 22, 2010 6:14 PM (b)(6);(b)(7)(C) To: Cc: (b)(6);(b)(7)(c) Subject: RE: SBInet Meeting Hello everyone, I will reach out on Monday to schedule this meeting for next week. If anyone has days that you know will absolutely not work for the meeting just let me know when you have a chance and I will work around it. Have a great weekend! (b)(6);(b)(7)(C) Office of the Secretary Department of Homeland Security (b)(6);(b)(7)(C) (cell) BW7 FOIA CBP 000388 DHS-17-0046-C-000388 From: (b)(6);(b)(7)(c) Sent: Friday, January 22, 2010 10:59 AM To: (b)(6);(b)(7)(c) ] Cc: (b)(6);(b)(7)(c) Subject: RE: SBInet Meeting - (b)(6);(b)(7)(C) (b)(6); (b)(7)(c) As we discussed last week, our small group met yesterday to sketch out a structure for the review. I think (b)(6);(b)(7)(C) (b)(6);(b) wanted to have a quick follow-up so he could stay apprised of status and direction. Is that (7)(c)something you can orchestrate? (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection BW7 FOIA CBP 000389 DHS-17-0046-C-000389 From: To: Subject: Date: (b)(6);(b)(7)(c) - RE: SBInet Data Call Thursday, January 28, 2010 11:38:06 AM I have pulling together an entire slide deck for the SBI rollout; idea is for you to use any/all that you’d like.  We will include an updated fiscal roll-up as soon as we get it ready.   CBP Budget folks also sent us a template to follow, but I think the template is entirely inadequate and told them we’ll bring our own material tuned to what we (you) think is the staffers’ appetite these days.   (b)(6);(b)(7)(C) From: (b)(6);(b)(7)(c) Sent: Thursday, January 28, 2010 11:34 AM To: (b)(6);(b)(7)(c) Subject: Re: SBInet Data Call I will probably need something similar for my budget brief next week to the Hill, if I can get it... From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Sent: Thu Jan 28 08:21:24 2010 Subject: Re: SBInet Data Call Thx From: (b)(6);(b)(7)(C) To: (b)(6);(b)(7)(c) Sent: Thu Jan 28 08:10:33 2010 Subject: FW: SBInet Data Call     (b)(6);(b)(7)(C) Executive Director, Secure Border Initiative (SBI) Customs and Border Protection   From: (b)(6);(b)(7)(c) Sent: Wednesday, January 27, 2010 5:17 PM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: SBInet Data Call Just want to give you a “heads-up” that a data call on SBInet spending is forthcoming with a possible due date of Feb 4, 1010.  The following data will most likely be requested:   1) Summary of funding received by the program, by appropriation and year. BW7 FOIA CBP 000390 DHS-17-0046-C-000390 2) Total of funds currently obligated against all contracts or grants, incl.             List of Contractor by Contract and Task order w/ $ amount, contract type             List of deliverables by Contract / Task Order / line item (Funded) 3) Total of outlays against all contracts 4) Total of unliquidated obligations on all contracts / task orders / line items (funded) 5) Total of unobligated funds by appropriation and year 6) Estimate of current outstanding liabilities whether funded or not.   V/R   (b)(6);(b)(7)(C) Assistant Director Budget Division - (b)(6);(b)(7)(C) Office of the Chief Financial Officer phone (b)(6);(b)(7)(C) BB (b)(6);(b)(7)(C) fax (b)(6);(b)(7)(C) email (b)(6);(b)(7)(C) BW7 FOIA CBP 000391 DHS-17-0046-C-000391 From: To: Subject: Date: (b)(6);(b)(7)(c) RE: Request a John Hopkins University Applied Physics Laboratory (JHU/APL) Electronic Gold (Acquisition Strategy) Review for Monday, January 25, 2010 Wednesday, January 20, 2010 9:46:09 AM Thank you.   (b)(6);(b)(7)(C) SBI Business Operations Office Contractor supporting the Acquisition Management Division (AMD) Desk Tel(b)(6);(b)(7)(C) Cell Tel: (b)(6);(b)(7)(C) Email: From: (b)(6);(b)(7)(c) Sent: Wednesday, January 20, 2010 9:45 AM To: (b)(6);(b)(7)(c) ) Subject: Re: Request a John Hopkins University Applied Physics Laboratory (JHU/APL) Electronic Gold (Acquisition Strategy) Review for Monday, January 25, 2010 From my perspective, this is fine. From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Wed Jan 20 09:43:07 2010 Subject: Request a John Hopkins University Applied Physics Laboratory (JHU/APL) Electronic Gold (Acquisition Strategy) Review for Monday, January 25, 2010 (b)(6);(b)(7)(c) ,   The SBI Systems Engineering Directorate and SBI Contracts Branch would like to conduct the JHU/APL Gold (Acquisition Strategy) Review electronically on Monday, January 25, 2010.  The JHU/APL Gold Review is for a follow-on IDIQ contract that provides support the SBI Systems Engineering Directorate for technical analysis and research for SBInet testing and evaluation activities.  The current JHU/APL contract ends on February 28, 2010.   The electronic Gold Review process would be as follows:   1. The advisors will be sent the documentation electronically today.   (b)(6);(b)(7)(c) will be provided a hardcopy binder for their review tomorrow. 2. The advisors will have until COB Friday, January 22, 2010 to review and make their recommendation 3. AMD will consolidate the inputs and provide them to (b)(6);(b)(7)(c) for a decision on Monday, January 25, 2010. 4. AMD has verified the entrance criteria for the Gold Review has been met.   Note:  Although the execution of the review board will be done electronically; advisors are encouraged to make phone calls or meet face to face (if necessary); as long as they are able to provide their input to AMD by COB Friday, January 22, 2010. BW7 FOIA CBP 000392 DHS-17-0046-C-000392   Please advise if you are agreeable to the recommended sequence for this Gold Review.   Thank you,   (b)(6);(b)(7)(C) SBI Business Operations Office Contractor supporting the Acquisition Management Division (AMD) Desk Tel (b)(6);(b)(7)(C) Cell Tel: (b)(6);(b)(7)(C) Email: BW7 FOIA CBP 000393 DHS-17-0046-C-000393 (b)(6);(b)(7)(c) From: To: Subject: Date: Friday, January 29, 2010 5:37:20 PM (b) 1111 (6);   (b)(7) I wanted to say hey, as I will be part of the SBInet Review process, and I wanted you to know where I (c) fit in.  I left CBP Budget in November and I am currently the Acting Deputy Director of PA&E, under (b)(6);(b)(7)(C) I will be the central POC for the SBInet Review within the Office of the CFO at DHS.  By now you should have received a budget data call from us thorough the ExecSec process (IQ 854649).  If you have any questions on that, please let me know.  Looking forward to working with you again.  Lots of folks around here say really nice things about you.  You have their respect.   (b)(6);(b)(7)(C) BW7 FOIA CBP 000394 DHS-17-0046-C-000394 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Friday, January 29, 2010 10:04 AM (b)(6);(b)(7)(c) Accepted: Mtg meeting with (b)(6);(b)(7)(C) Director SBINet   1 BW7 FOIA CBP 000395 DHS-17-0046-C-000395 From: To: (b)(6);(b)(7)(c) Subject: Next Steps for SBInet When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 - *~*~*~*~*~*~*~*~*~* - To discuss the path forward for SBI after the (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the (b)(6);(b)(7)(C) briefing given to Chief and Chief (b)(6);(b)(7)(C) in December.  POC: (b)(6);(b)(7)(C)  Calendared by (b)(6);(b)(7)(C) BW7 FOIA CBP 000396 DHS-17-0046-C-000396 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Thursday, January 14, 2010 1:41 PM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000397 DHS-17-0046-C-000397 From: To: Subject: Start: End: Location: (b)(6);(b)(7)(c) Next Steps for SBInet Friday, January 22, 2010 3:30:00 PM Friday, January 22, 2010 4:30:00 PM Conference Room 1 When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 - *~*~*~*~*~*~*~*~*~* To discuss the path forward for SBI after the (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) briefing given to Chief and Chief in December.  POC: (b)(6);(b)(7)(C)   Calendared by BW7 FOIA CBP 000398 DHS-17-0046-C-000398 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Thursday, January 14, 2010 1:31 PM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000399 DHS-17-0046-C-000399 From: To: Cc: Subject: Date: Attachments: (b)(6);(b)(7)(c) - RE: Change in Key Performance Parameters for (b) (7)(E) Friday, January 15, 2010 5:27:36 PM Issue Paper Pd and Pid v2 0 (2).doc Attached is the issue paper relating to the changes in probability of detection and probability of identification reported by Boeing at the JPMR this week.   As you are aware, the Department is taking a close look at the SBInet and will make a determination at some point whether to continue with these deployments.  During the last two months, the schedule to turn the (b) (7)(E) system over to Border Patrol slipped from a date in January 2010 to the current estimate of October 5, 2010.  The negative information could potentially jeopardize the program’s continued existence.   - - (b)(6);(b)(7)(C) (b)(6); (b)(7)   (c) From: (b)(6);(b)(7)(c) To: (b)(6);(b)(7)(C) Cc: (b)(6);(b)(7)(c) Sent: Thu Jan 14 07:25:39 2010 Subject: FW: Change in Key Performance Parameters for(b) (7)(E) - - (b)(6);(b)(7)(C) (b)(6); (b)(7)   (c) Can you please put an issue paper together answering Chief (b)(6);(b)(7)(C) concerns below?   Thanks,   (b)(6);(b)(7)(C) (b) (6);   (b) (7) From: (b)(6);(b)(7)(c) (c) Sent: Thursday, January 14, 2010 7:21 AM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: RE: Change in Key Performance Parameters for(b) (7)(E) - - (b)(6);(b)(7)(C) Let’s get with (b) -I need to understand the programmatic implication of this as well as the anticipated (7) if realized.  I do not have the institutional knowledge as perhaps you or the staff and I operational impact (E)up to speed mid-stream. will need to get   Thanks.   (b)(6);(b)(7)(C) - Acting Chief U.S. Border Patrol (b)(6);(b)(7)(C) 1300 Pennsylvania Ave, Washington, DC 20229 (b)(6);(b)(7)(C) secure) BW7 FOIA CBP 000400 DHS-17-0046-C-000400 WARNING: This document is LAW ENFORCEMENT SENSITIVE and is designated FOR OFFICIAL USE ONLY (FOUO). It contains information that may be exempt from public release under the Freedom of Information Act (5 USC 552). This document is to be controlled, handled, transmitted, distributed, and disposed of in accordance with Department of Homeland Security policy relating to FOUO information, and is not to be released to the public or personnel who do not have a valid "need to know" without prior approval from the Acting Chief, US Border (b)(6);(b)(7)(C) Patrol (b)(6);(b)(7) (c) From: (b)(6);(b)(7)(c) Sent: Thursday, January 14, 2010 6:50 AM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: RE: Change in Key Performance Parameters for (b) (7)(E) - - (b)(6);(b)(7)(C) (b) (6);   (b) (7) (c) (b) (5) .   (b)(6);(b)(7)(C) (b) (6);   (b) (7) From: (b)(6);(b)(7)(c) (c) Sent: Wednesday, January 13, 2010 6:41 PM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: Change in Key Performance Parameters for (b) (7)(E) - During the JPMR for SBInet today, we were told done to verify these numbers, (b) (7)(E) (b) (7) (E) needs to be While there is still some work that (b) (7)(E) (b) (7)(E) (b) (7)(E)   With the current attention being given to SBInet at the Department and the assessment to determine if we will deploy more iterations of Block 1 technology on the southwest border, this could prove to be a significant development especially in light of the latest schedule which has the system not being turned over to us for testing until October 5.  That has slipped in the last two months from a January system acceptance date.   There were several representatives from DHS present at the JPMR who are charged with acquisition overview for the Department.  They have likely relayed this information up the chain.   - (b)(6);(b)(7)(C) (b)(6); (b)(7) (c)   BW7 FOIA CBP 000401 DHS-17-0046-C-000401 SITUATION: • At the January 13, 2010, SBInet Joint Project Management Review (JPMR) Boeing revealed a potential change to projected estimates of the (b) (7)(E) • • (b) (7)(E) Boeing claims a mistake was made in their presentation of clearly defining the results. Key terminology Defined: (b) (7)(E) (b) (7)(E) o standard test (b) (7)(E) (b) (7)(E) procedure to measure the . o (b) (7)(E) standard test procedure to (b) (7)(E) • • • • • . o Key Performance Parameters (KPP): identified as the program’s critical essential characteristics or capabilities. o Threshold Value – the minimum acceptable value to meet contractual obligations. o Objective Value – goal Boeing is trying to meet. In previous JPMRs Boeing had stated that (b) (7)(E) percent respectively, which were determined through modeling and analysis. At the JPMR on January 13, 2010, Boeing presented projected (b) (7)(E) These lowered numbers alarmed SBI and OBP officials attending the meeting. Boeing representative could not adequately explain how the lower percentages were obtained. DHS S&T representatives were in attendance. The SBInet Operational Requirements Document (ORD) states in the Key Performance Parameters (KPP) that the objective value (target) fo (b) (7) (E) ACTIONS TAKEN: 1. After the JPMR all parties started investigating the issue. 2. Boeing is putting together a tiger team to review the data presented at the JPMR. OUTCOMES OF ACTIONS TAKEN 1. Initial investigation revealed the following: o The original percentages of(b) (7)(E) (b) (6) Prepared by: (b)(6);(b)(7)(c) Subject: Potential Operational Impact of Date of last Revision: January 15, 2010 (b) (7) (b) (7)(E) (E) BW7 FOIA CBP 000402 DHS-17-0046-C-000402 (b) (7)(E) o The were based on an actual characterization test conducted by Boeing in the field for only (b) (7)(E) a small segment, o Boeing believes their field characterization was not a complete analysis and cannot be used to judge the future performance of the system. In order to compare the predictive model analysis numbers a complete field characterization test would have to be (b) (7)(E) completed covering the entire area (b) (7)(E) . 2. There have been no actions taken to date by the tiger team. - CHALLENGES: • If accurate, these revised numbers could represent a (b) (7)(E) • Any (b) (7)(E) • RISK - Until the true capabilities of this system are understood, through test and evaluation, operational impacts may not be fully evaluated. Boeing anticipates that an actual field characterization of the entire area (b) (7)(E) will be very near their model prediction analysis estimations of (b) (7)(E) • - OPTIONS: 1. Study the issue more and aggressively investigate this occurrence to ensure it is not a symptom of a larger problematic issue. 2. Wait for Systems Acceptance Testing (SAT) to begin in July 2010 and see (b) (7)(E) (7) percentages are recorded. what actual (b) (E) RECOMMENDATIONS: 1. Study the issue more and aggressively investigate this occurrence to ensure it is not a symptom of a larger problematic issue. Prepared by: (b)(6);(b)(7)(c) Subject: Potential Operational Impact of (b) Date of last Revision: January 15, 2010 (b) (7) (7)(E) (E) BW7 FOIA CBP 000403 DHS-17-0046-C-000403 (b)(6);(b)(7)(c) From: To: Cc: Subject: Date: Attachments: Importance: FW: Revised Papers Friday, January 15, 2010 5:56:56 PM Issue Paper Pd and Pid v2.0.doc High Attached is the issue paper relating to the changes in (b) (7)(E) (b) (7)(E) reported by Boeing at the JPMR this week.   BW7 FOIA CBP 000404 DHS-17-0046-C-000404 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Thursday, January 14, 2010 1:28 PM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000405 DHS-17-0046-C-000405 (b)(6);(b)(7)(c) From: To: Cc: Subject: Tentative: Updated: ESC Pre-brief I will be at the SBInet JPMR but will try to come back early.  If I am unable to attend, I will send a representative. BW7 FOIA CBP 000406 DHS-17-0046-C-000406 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Thursday, January 14, 2010 1:50 PM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000407 DHS-17-0046-C-000407 - (b)(6);(b)(7)(C) on behalf of (b)(6);(b)(7)(C) From: To: Subject: Start: End: Location: (b)(6);(b)(7)(C) Next Steps for SBInet Friday, January 22, 2010 3:30:00 PM Friday, January 22, 2010 4:30:00 PM Conference Room 1 When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 - *~*~*~*~*~*~*~*~*~* To discuss the path forward for SBI after the (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the (b)(6);(b)(7)(C) briefing given to Chief and Chief (b)(6);(b)(7)(C) in December.  POC:  (b)(6);(b)(7)(C).  Calendared by (b)(6);(b)(7)(C) BW7 FOIA CBP 000408 DHS-17-0046-C-000408 From: To: Subject: Start: End: Location: (b)(6);(b)(7)(C) on behalf o (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Next Steps for SBInet Friday, January 22, 2010 3:30:00 PM Friday, January 22, 2010 4:30:00 PM Conference Room 1 When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 - *~*~*~*~*~*~*~*~*~* - To discuss the path forward for SBI after the (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) briefing given to Chief and Chief (b)(6);(b)(7)(C) in December.  POC: (b)(6);(b)(7)(C) .  Calendared by BW7 FOIA CBP 000409 DHS-17-0046-C-000409 From: To: Subject: Start: End: Location: (b)(6);(b)(7)(C) on behalf of (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Next Steps for SBInet Friday, January 22, 2010 3:30:00 PM Friday, January 22, 2010 4:30:00 PM Conference Room 1 When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 - *~*~*~*~*~*~*~*~*~* To discuss the path forward for SBI after the (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) briefing given to Chief and Chief in December.  POC:  (b)(6);(b)(7)(C).  Calendared by (b)(6);(b)(7)(C) BW7 FOIA CBP 000410 DHS-17-0046-C-000410 From: To: Subject: Start: End: Location: (b)(6);(b)(7)(C) on behalf of (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Next Steps for SBInet Friday, January 22, 2010 3:30:00 PM Friday, January 22, 2010 4:30:00 PM Conference Room 1 When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 - *~*~*~*~*~*~*~*~*~* - To discuss the path forward for SBI after the (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) briefing given to Chie (b)(6);(b)(7)(C) nd Chief in December.  POC: (b)(6);(b)(7)(C)Calendared by BW7 FOIA CBP 000411 DHS-17-0046-C-000411 From: To: Subject: Date: (b)(6);(b)(7)(c) RE: Thursday, January 14, 2010 5:47:23 AM I’ll get with you on this. - (b)(6);(b)(7)(C) (b) (6);   (b) (7) From: (b)(6);(b)(7)(c) (c) Sent: Wednesday, January 13, 2010 7:08 PM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: FW: (b)(6);(b)(7)(C) (b) (6);   (b) Are we aligned with SBI on this or do we need to coordinate.  I just need the background on our tasker (7) and what has, is, and will be done toward the effort. (c)   Thanks.   (b)(6);(b)(7)(C) Acting Chief U.S. Border Patrol 1300 Pennsylvania Ave, (b)(6);(b)(7)(C) Washington, DC 20229 (b)(6);(b)(7)(C) (secure) WARNING: This document is LAW ENFORCEMENT SENSITIVE and is designated FOR OFFICIAL USE ONLY (FOUO). It contains information that may be exempt from public release under the Freedom of Information Act (5 USC 552). This document is to be controlled, handled, transmitted, distributed, and disposed of in accordance with Department of Homeland Security policy relating to FOUO information, and is not to be released to the public or personnel who do not have a valid "need to know" without prior approval from the Acting Chief, US Border (b)(6);(b)(7) Patrol (b)(6);(b)(7)(C) (c) From: (b)(6);(b)(7)(c) Sent: Wednesday, January 13, 2010 4:54 PM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: Re: Chief-FYSA, S1's staff has scheduled a meeting for Friday afternoon, presumably tpo frame out the review. Also--if we ever get an opening to get DHS to loosen the shackles and let us continue our communications strategy (which, by the way, is a big part of the reason the 60 Minutes thing was not so bad), we will all be better off. As it stands, DHS is making us refer everything to them--and I'm concerned it's going to destroy the relationships we've established, compromise our credibility, create misinformation (due to lack of detailed knowledge), and broken glass we'll end up cleaning. I obviously wouldn't tilt at windmills just yet--but if the opportunity presents itself... BW7 FOIA CBP 000412 DHS-17-0046-C-000412 - Thanks and vr, (b) (6); (b) (7) From: (b)(6);(b)(7)(c) (c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Wed Jan 13 16:47:45 2010 Subject: RE: (b)(6);(b)(7)(C) J - 10-4   When, and it will, slow down, I am sure that we will be “on deck” to brief out our options and our adjusted plans. Appreciate it.   (b)(6);(b)(7)(C) (b) (6);   (b)(7) (c) From: (b)(6);(b)(7)(c) Sent: Wednesday, January 13, 2010 4:46 PM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: Re: (b)(6);(b)(7)(C) - Chief-10-4. We've actually started this already and are planning to accelerate it. - (b)(6);(b)(7)(C) (b) (6); (b) (7) From: (b)(6);(b)(7)(c) (c) To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Sent: Wed Jan 13 16:18:17 2010 Subject: (b)(6);(b)(7)(C) (b)(6);(b) (7)(c) In one of the breaks that we had yesterday in dealing with all the activities surrounding the 12/25 incident, Haiti, and another hot button item, the Secretary and I had a chance to very briefly discuss SBInet, the 60 Minutes piece, and path forward. She is of the same opinion as we are: the 60 Minutes piece was a lot less negative than what we had anticipated and she also thought that Boeing took the brunt of the piece. She also stated that the purpose of the memo that went out with her directing the “review” of SBInet was in anticipation of a more negative piece.  But basically she agrees with the options paper that we put forth before the holidays. She did not specifically identify option 2 as her preference but as she lined out her recollection of the memo and it fits right along with Option 2. She noted that she had “spoken to Congress” about this and that they were not surprised and supportive. I did not ask how this communication was done, formally or informally. Given the timeline from when we sent the paper forth I would guess that it was a verbal and informal. - (b)(6);(b)(7)(C) (b) (6);   (b) This being the case we need to look at redesigning our thought process as to technology capability (7) requirements (i.e, detection, deterrence, identification, classify, etc.. or mix of) that we would be looking to (c) get resourced under this option. Exercising this option or something similar to it would mean that we BW7 FOIA CBP 000413 DHS-17-0046-C-000413 would be weighting our resource procurement efforts and requirements towards “commodity purchases” of technology versus “system development”. Not that we would stop the systems development completely (block one). I would ask that Border Patrol revisit our technology requirements against this new information.   Keep me apprised.   (b)(6);(b)(7)(C) (b) (6); (b)(7) (c) - BW7 FOIA CBP 000414 DHS-17-0046-C-000414 (b)(6);(b)(7)(c) From: To: Cc: Subject: Date: RE: Wednesday, January 13, 2010 4:25:27 PM Yes Sir, will do.   v/r   (b)(6);(b)(7)(C) Acting Chief U.S. Border Patrol 1300 Pennsylvania Ave, (b)(6);(b)(7)(C) Washington, DC 20229 (b)(6);(b)(7)(C) secure) WARNING: This document is LAW ENFORCEMENT SENSITIVE and is designated  FOR OFFICIAL USE ONLY (FOUO). It contains information that may be exempt from public release under the Freedom of Information Act (5 USC 552). This document is to be controlled, handled, transmitted, distributed, and disposed of in accordance with Department of Homeland  Security policy relating to FOUO information, and is not to be  released to the public or personnel who do not have a valid "need to know" without prior approval from the Acting Chief, US Border (b)(6);(b)(7)(C) Patrol (b)(6);(b)(7) (c) From: (b)(6);(b)(7)(c) Sent: Wednesday, January 13, 2010 4:18 PM To: (b)(6);(b)(7)(c) Cc: (b)(6);(b)(7)(c) Subject: - (b)(6);(b)(7)(C) (b)(6);(b) (7)(c) In one of the breaks that we had yesterday in dealing with all the activities surrounding the 12/25 incident, Haiti, and another hot button item, the Secretary and I had a chance to very briefly discuss SBInet, the 60 Minutes piece, and path forward. She is of the same opinion as we are: the 60 Minutes piece was a lot less negative than what we had anticipated and she also thought that Boeing took the brunt of the piece. She also stated that the purpose of the memo that went out with her directing the “review” of SBInet was in anticipation of a more negative piece.  But basically she agrees with the options paper that we put forth before the holidays. She did not specifically identify option 2 as her preference but as she lined out her recollection of the memo and it fits right along with Option 2. She noted that she had “spoken to Congress” about this and that they were not surprised and supportive. I did not ask how this communication was done, formally or informally. Given the timeline from when we sent the paper forth I would guess that it was a verbal and informal.   (b)(6);(b)(7)(C) (b) (6);   (b) This being the case we need to look at redesigning our thought process as to technology capability (7) requirements (i.e, detection, deterrence, identification, classify, etc.. or mix of) that we would be looking to (c) get resourced under this option. Exercising this option or something similar to it would mean that we would be weighting our resource procurement efforts and requirements towards “commodity purchases” of technology versus “system development”. Not that we would stop the systems development completely (block one). I would ask that Border Patrol revisit our technology requirements against this new information.   - BW7 FOIA CBP 000415 DHS-17-0046-C-000415 Keep me apprised.   (b)(6);(b)(7)(C) (b) (6); (b)(7) (c) - BW7 FOIA CBP 000416 DHS-17-0046-C-000416 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Thursday, January 14, 2010 1:52 PM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000417 DHS-17-0046-C-000417 From: To: Subject: Start: End: Location: (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) on behalf of (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Declined: Next Steps for SBInet Friday, January 22, 2010 3:30:00 PM Friday, January 22, 2010 4:30:00 PM Conference Room 1 will be returning from Phoenix, AZ and unable to attend. Please let me know if there are any questions / concerns. v/r, (b)(6);(b)(7)(C) BW7 FOIA CBP 000418 DHS-17-0046-C-000418 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Thursday, January 14, 2010 1:34 PM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000419 DHS-17-0046-C-000419 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Friday, January 15, 2010 7:33 AM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000420 DHS-17-0046-C-000420 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Friday, January 15, 2010 7:51 AM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000421 DHS-17-0046-C-000421 From: To: Subject: Start: End: Location: (b)(6);(b)(7)(C) - n behalf o (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) FW: Next Steps for SBInet Friday, January 22, 2010 3:30:00 PM Friday, January 22, 2010 4:30:00 PM Conference Room 1 When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). Where: Conference Room 1 *~*~*~*~*~*~*~*~*~* >_____________________________________________ > From:(b)(6);(b)(7)(C) (b)(6);(b)(7) > (c) Sent: Thursday, January 14, 2010 1:28 PM > To:(b)(6);(b)(7)(c) > Subject: Next Steps for SBInet > When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). > Where: Conference Room 1 > > When: Friday, January 22, 2010 3:30 PM-4:30 PM (GMT-05:00) Eastern Time (US & Canada). > Where: Conference Room 1 > > *~*~*~*~*~*~*~*~*~* > > To discuss the path forward for SBI after (b)(6);(b)(7)(C) the (b) (7)(E) deployments.  No read ahead material.  This meeting is a follow on meeting to the briefing given to Chief (b)(6);(b)(7)(C)and Chief n December.  POC: (b)(6);(b)(7)(C)  Calendared by (b)(6);(b)(7)(C) > - ....... - BW7 FOIA CBP 000422 DHS-17-0046-C-000422 ------------(b)(6);(b)(7)(c) From: Sent: To: Subject: (b)(6);(b)(7)(c) Thursday, January 14, 2010 1:33 PM (b)(6);(b)(7)(c) Accepted: Next Steps for SBInet   1 BW7 FOIA CBP 000423 DHS-17-0046-C-000423 FOUO – FOR OFFICIAL USE ONLY SBInet ILS Program Management Review 26 January 2011 (b) (6) Prepared for: (b) (6) , Contracting Officerr , Contracting Officer Technical Representative epresentative WARNING: This document is designated FOR OFFICIAL USE ONLY (FOUO). It contains information that may be exempt from public release under the Freedom of Information Act (5 USC 552). This document is to be controlled, handled, transmitted, distributed, and disposed of in accordance with Department of Homeland Security Management Directive 11042.1, and is not to be released to the public or personnel who do not have a valid “need to know” without prior approval from the CBP Secure Border Initiative – Program management Office (PMO) (b)(6);(b)(7)(C) BOEING is a trademark of Boeing Management Company. Copyright © 2006 Boeing. All rights reserved BW7 FOIA CBP 000424 FOUO – FOR OFFICIAL USE ONLY DHS-17-0046-C-000424 5/24/2017 2:18 PM 1 FOUO – FOR OFFICIAL USE ONLY Systems Support Analysis SBInet Program Management Review 21anuary 2011 (b) (6) WARNING: This document is designated FOR OFFICIAL USE ONLY (FOUO). It contains information that may be exempt from public release under the Freedom of Information Act (5 USC 552). This document is to be controlled, handled, transmitted, distributed, and disposed of in accordance with Department of Homeland Security Management Directive 11042.1, and is not to be released to the public or personnel who do not have a valid “need to know” without prior approval from the CBP Secure Border Initiative – Program management Office (PMO) (b)(6);(b)(7)(C) BOEING is a trademark of Boeing Management Company. Copyright © 2006 Boeing. All rights reserved BW7 FOIA CBP 000425 FOUO – FOR OFFICIAL USE ONLY DHS-17-0046-C-000425 5/24/2017 2:18 PM 2 Owner: Status Date: Telephone: (b)(6);(b)(7)(C) 01/21/2011 FOUO – FOR OFFICIAL USE ONLY (b)(6);(b)(7)(C) Systems Support Analysis Accomplishments • Update to Integrated Logistics Support Plan (ILSP) in progress • Team review stats for Promotion and Release Notifications – 3 notices for new document promotions/releases • 2 were release notice only (no ILS associated review/approval) • Developed default Work Order Priority Reference Guide. – Incorporated into Maximo Equipment Classification description by Maximo System Administrator. • Expanded Maximo Equipment Classifications to include NOC/SOC & NDC. • Provided information on TUS-1 Metrics Tool to (b) (6) , in support of next generation TUS-1 Metrics Reporting system. • Generated TUS-1 Ao Metrics history (6-month) in support of customer request. • Updated MSS Engineering Change tracking sheet with completion data BW7 FOIA CBP 000426 ha. 1, pc)r.1t1!itl l t1, c.1r1y The S.)'fitflm i:1cli::; pu sci d om into11dod f,11"1io11 h l !ltm Iu,J1le 1I Note: A SElC Tall'o~lng1P,lan must be developed that d'eflnes what stages , activities , and artifacts will be completed for the proJed. Tihe SElCTa.ilo ,ring P,la.11should re.fleet the unique chara.cte~istics of the project I RR: Integration Readiness Re,..,iew IPRR: Produetlon Readiness Revllew OTRR: Oper11tlon11I Test Readiness Review ORR: Operational Readiness Reviiew -'1,P_ l~R ~,:~.P~0~st ~··~1,m -,.rilHl6nta.tl.~0~n_,~R ~.•~-\l=l=1:w ",_ ___ 0 Additional TRG Reviews included: Systems Requirements Review Software Preliminary Design Review Software Critical Design Review Systems Verification Review and pro"tlide the best opportunity to deli ,ver the syst8DI effectively; _, Systems Functional Review Software Specification Review Software Test Readiness Review Physical Configuration Audit Performlower-level lower-levelreviews reviewsin insupport supportof ofsystem-level system-levelreviews. reviews. Perform BW7 FOIA CBP 000546 DHS-17-0046-C-000546 Next Steps • Develop training materials • Conduct training across OTIA technical and program staff • Collaborate with the CBP CIO to align elements of the TRG with IT processes (e.g. one voice) • Work with Program teams to properly plan and conduct event-based technical reviews • Enhance program success by providing Program Managers with objective assessments of technical progress against SELC criteria It’snot notabout aboutthe thegate gateits itsabout aboutthe thejourney! journey! It’s BW7 FOIA CBP 000547 CLASSIFICATION DHS-17-0046-C-000547 30 Agenda •• Overview Overview of of SE SE Directorate Directorate Roles Roles and and Responsibilities Responsibilities •• OTIA OTIA Technical Technical Review Review Guide Guide –– A A focus focus on on an an SE SE product product • Lead Technical Authority - Overview of a “second hat” •• Overview Overview of of the the SBInet SBInet Analysis Analysis of of Alternatives Alternatives ((AoA AoA)) BW7 FOIA CBP 000548 DHS-17-0046-C-000548 Lead Technical Authority for nonIT Systems 1300 l'em!sylvaniaAvenueNW Washington, DC 20229 • Appointed by CAE US.Customs and BorderProtection • • Mandated participant for all SE reviews and is empowered to represent agency-wide technical considerations & recommendations to the PM and CAE • Responsible for – Ensuring SELC Review exit criteria are satisfied – Endorsing the SELC Tailoring Plans – Signing the SELC Review Completion Letter MEMORANDUMFOR: FROM: SUBJECT: (b)(6);(b)(7)(C) Appointment of the Lead Technical Authority for Non-IT Systems The Department of Homeland Security (OHS) I 02-0 I Acquisition Management Directive states that the Component Acquisition Executive (CAE) is the senior acquisition official within a Component responsible for implementation, management, and oversight of the Component's acquisition processes. Appendix B of I 02-01-001, the Systems Engineering Life Cycle states that the CAE will designate the Lead Technical Authority for non-IT systems, will ensure Components have adequate functional lines ofbusiness (e.g., Systems Engineering, Logistics, etc.) and ensure that Components support the program/project Systems Engineering Life Cycle (SELC) reviews. Table 1-2 (OHS SELC Review Stakeholder Roles and Responsibilities) discusses the basic level of technical authority for the SELC including the definition andassociated criteria to include making technically sound engineering decisions, andrequiring technical authorities to support Program Managers. (b)(6);(b)(7)(C) -~cal "hiefEngineer, Office of Technology Innovation and Acquisition, is hereby Authority for non-IT systems. Distribution: All Assistant Commissioners Chief, Office of Border Patrol Chief Counsel Executive Director, Office of Diversity and Civil Rights Executive Director, Office of Policy andPlanning Director, Office of Trade Relations Director, Office of the Executive Secretariat Director, State and Local Liaison BW7 FOIA CBP 000549 DHS-17-0046-C-000549 Agenda •• Overview Overview of of SE SE Directorate Directorate Roles Roles and and Responsibilities Responsibilities •• OTIA OTIA Technical Technical Review Review Guide Guide –– A A focus focus on on an an SE SE product product •• Lead Lead Technical Technical Authority Authority -- Overview Overview of of aa ““second second hat hat”” • Overview of the SBInet Analysis of Alternatives (AoA) BW7 FOIA CBP 000550 DHS-17-0046-C-000550 Assessment Approach (Three Elements) • Immediate term: divert the ARRA funds from SBInet to other technology (complete) • Mid-term: consider diversion of some existing (currently frozen) SBInet Block 1 funding to other technology options for high-priority border areas (decisions by May/June) – Fill holes that cannot wait for the results of the AoA assessment or that cannot wait for SBInet to be available • Long-term: comprehensive, quantitative, science-based assessment (e.g., Analysis of Alternatives) of SBInet compared to other technology options for each individualized area of the border – Meets recognized standards for these types of assessments—appropriate for large investment decisions – Usually a 6-9 month effort – Highly analytical (requires highly expert and experienced personnel) – Can be phased to get interim results for highest priority needs and decisions BW7 FOIA CBP 000551 DHS-17-0046-C-000551 Three-Phased AoA Approach •Phase 1a: – Science-based, quantitative analysis (e.g., AoA) for Arizona (Tucson and Yuma Sectors) • SBI and S&T will identify technology options based on current knowledge vice market research • Identify and score Operational Outcomes and Measures of Effectiveness (MOEs) for each alternative or set of alternatives • Develop credible cost-estimates for each alternative • Compare effectiveness and cost for each alternative – Data analysis complete by 30 Jun 2010 (goal); annotated brief complete by 16 Jul 2010 •Phase 1b: – Conduct AoA for next three priority sectors (El Paso, Rio Grande Valley, San Diego) – Data analysis to start in Aug 2010 (given results and products from phase 1a make sense) and complete by end of 22 Nov 2010 (goal); annotated brief complete by 20 Dec 2010 •Phase 2: – Extend and complete AoA for the remaining sectors and segments along the SWB – Data analysis complete by 25 Feb 2011; final report complete by 29 Apr 2011 Received approval for Phase 1b on 22 July 2010 BW7 FOIA CBP 000552 DHS-17-0046-C-000552 AoA Assessment Status •Phase 1a (Arizona) – Completed July 2010; briefed to S1 on 22 Jul 2010 •Arizona Technology Deployment Plan created – Awaiting S1’s announcement – Beginning preliminary acquisition actions •Phase 1b – 3 prioritized sectors from OBP: RGV, El Paso & San Diego – Phase 1b differences from Phase 1a • 2 additional MOEs – Strategic Intelligence – Dynamic Surveillance • 2 additional technology alternatives – Aerostats – Cerberus lite • 2 additional environmental areas – Maritime (Land/Sea interface) – Urban (developing the framework to assess during Phase 2) – Regarding the S1’s action to open the aperture • DoD has validated the existing technology choices – With the addition of Aerostats and Cerberus lite BW7 FOIA CBP 000553 DHS-17-0046-C-000553 AoA Next Steps •OBP (with support from the Study Team and OTIA) is developing the Technology Development Plan for RGV, El Paso, and San Diego (12-22 Dec) – Informed by the phase 1b analysis results •Study Team will hold a Peer Review with DoD in January – Response to S1’s action to open the aperture •AoA ESC briefing ready (week of 20 Dec); briefing to other stakeholders (early January) •Technology Development Plan briefing ready (early January) BW7 FOIA CBP 000554 DHS-17-0046-C-000554 Backups BW7 FOIA CBP 000555 DHS-17-OO46-C-000555 OTIA Integrated Logistics Support (ILS) Program U.S. Custom.s and Border Protection (b)(6);(b)(7)(C) 6 January 2011 BW7 FOIA CBP 000556 DHS-17-0046-C-000556 Agenda • Organizational Overview – Vision, Mission, Structure – Support Concept – Organizational Responsibilities • Division Missions – – – – – Policy, Planning, and Performance Resource Planning and Execution Implementation and Life Cycle Management Operations and Support Asset Management and Automation – Organization Management • Corporate Challenges • Key Activities BW7 FOIA CBP 000557 DHS-17-0046-C-000557 40 Vision To become the Integrated Logistics Support (ILS) Center of Excellence advancing life cycle supportability and sustainment best practices across all CBP programs BW7 FOIA CBP 000558 DHS-17-0046-C-000558 41 How to Achieve the Vision ¾ We plan to use the seven Baldridge Criteria as an integrated framework for managing the ILS organization: 1. 2. 3. 4. 5. 6. 7. Leadership Strategic planning Customer focus Measurement, analysis, and knowledge management Workforce focus Operations focus Results ¾ By using these criteria, we can align resources; improve communication, productivity, and effectiveness; and achieve strategic goals ¾ Journey has just begun…but it’s going to be exciting! BW7 FOIA CBP 000559 DHS-17-0046-C-000559 42 Mission The ILS Directorate: Develops and implements life-cycle logistics support requirements for OTIA Programs ¾ Implements and maintains DHS/CBP ILS policy ¾ Develops, monitors, forecasts, and reports ILS fiscal requirements ¾ Influences system design to achieve operational effectiveness and efficiency and minimize life cycle cost ¾ Identifies requirements and develops and delivers ILS solutions to resolve system operational inefficiencies ¾ Synchronizes and aligns ILS resources to optimize border enforcement system operations DHS-17-0046-C-000560 BW7 FOIA CBP 000560 43 ILS Directorate Organization Deputy (b)(6);(b)(7)(C) ILS Directorate (b)(6);(b)(7)(C) Policy, Planning, & Performance Division (b)(6);(b)(7)(C) Resource Planning & Execution Division Implementation & Life Cycle Mgt Division Organization Mgt Division (b)(6);(b)(7)(C) Operations & Support Division (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Intern Asset Mgt & Automation Division (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) I •-•-•-•-•-•-•-•-•-•-• BW7 FOIA CBP 000561 DHS-17-0046-C-000561 44 ILS Support Concept OTIA Programs APMLs Implementation and Life Cycle Management Policy, Planning, & Performance [____ ] [ Resource Planning & Execution Operations & Support J [~_] [ Asset Management & Automation J Organization Management Division BW7 FOIA CBP 000562 DHS-17-0046-C-000562 45 APML Support Concept to PMO Maintenance Planning Technical Data Computer Resources Support Manpower & Personnel Programs A- Z Facilities Supply Support Packaging, Handling Storage, & Transportation Support Equipment Training & Support Interfaces BW7 FOIA CBP 000563 DHS-17-0046-C-000563 46 ILS Organizational Responsibilities I I I DHS AD 102-01 Appendix J Compliance; Logistics Policy, Best Practices, Standards, Tools; Organizational Goals/Objectives; Performance Metrics & Process Improvement Policy, Planning & Performance LRFP Development; Funds Control; Financial Reports; Support Agreements Resource Planning & Execution _1-------_I-------1-------- ISEA; SSA; PICA/Depot; Field Support; Supply Support; Configuration Mgt; Tech Data Mgt Project Material Management; Asset ID; Inventory Control I Organization Management Director Deputy Operations & Support Asset Management & Automation Implementation & Life Cycle Management Programs A-Z APML ORD CONOPS AoA ILSP LSA LCCE Contract Dev OT&E Disposition i.e., IFT (b) (7)(E) Mobile Surveillance AMDA CCB BW7 FOIA CBP 000564 DHS-17-0046-C-000564 47 Policy, Planning, & Performance Division The Policy, Planning, and Performance Division enables excellence in logistics by providing superior support to the logistics community of interest (COI) by: ¾ Implementing and maintaining ILS policies, processes, procedures, standards, and templates to achieve optimal outcomes ¾ Developing a strategic plan that aligns ILS and OTIA goals with quantifiable and measurable objectives ¾ Identifying, providing, and inculcating logistics best practices, lessons learned, and value-added tools for PMs’ and APMLs’ use BW7 FOIA CBP 000565 DHS-17-0046-C-000565 48 Planning & Execution Division Resource The Resource Planning and Execution Division manages Operations and Maintenance (O&M) resource requirements to support OTIA deployed projects to include current and out-year budget development and execution as well as administrative duties for O&M contracts and agreements. Additionally, consult with programs during the transition from implementation to in-service logistics support. Support the development of ILS capital investment costs to support OTIA Development and Deployment (D&D) programs. Responsible for the following: ¾ Logistics Requirement and Funding Plan (LRFP) Development ¾ Funds Control (O&M allocation) ¾ Financial Reports ¾ Support Agreements ¾ Annual FY Spend Plan Development (SB 200 & 300) BW7 FOIA CBP 000566 DHS-17-0046-C-000566 49 Implementation & Life Cycle Mgt Division The Implementation and Life Cycle Management Division implements ILS best practices by providing projects with APMLs who: ¾ Coordinate, participate and contribute to artifact/product development in terms of reliability, availability, maintainability, and testability (RAMT) throughout the life cycle ¾ Establishes and maintains baselines and configuration control for the IPT(s) ¾ Develops projects’ Integrated Logistics Support Plan (ILSP) and the associated ILS Product Support Package (PSP) requirements ¾ Assists in defining and obtaining solutions to meet the requirements of the ILSP and PSP ¾ Develop Life-Cycle Cost Estimate (LCCE) for the logistics portion of projects ¾ Participates in project CCBs for system(s) development and sustainment / Planned Product Improvements ¾ Defines and uses logistics analysis tools to track Availability to cost efficiency to budgeting in the process developing and assessing performance based logistics criteria/metrics ¾ Reviews and approves ILS PSP deliverables and assists in overseeing CMLS / organic sustainment efforts BW7 FOIA CBP 000567 DHS-17-0046-C-000567 50 Operations & Support Division The Operations and Support Division is responsible for the following ILS activities within CBP: ¾ In-Service Engineering Agent (ISEA) ¾ Software Support Activity (SSA) ¾ Primary Inventory Control Activity (PICA)/Depot/Supply Support ¾ Field Support ¾ Configuration Management (CM) ¾ Technical Data Management BW7 FOIA CBP 000568 DHS-17-0046-C-000568 51 Asset Management & Automation Division The Asset Management and Automation Division develops and implements practical, cost-effective asset management practices at the strategic, tactical, and operational levels to manage and control all OTIA assets assuring asset integrity and visibility by: ¾ Controlling all OTIA assets and project material until they are placed in use by field managers ¾ Assigning ownership within SAP and Integrated Logistics Support System (ILSS/Maximo) ¾ Identifying and classifying new assets ¾ Developing Standard Asset Management and Disposal Plans for projects to utilize as guidance from project initiation to final disposition ¾ Conducting Final Acceptance inventories ¾ Integrating tools to provide Asset visibility throughout the life cycle BW7 FOIA CBP 000569 DHS-17-0046-C-000569 52 Organization Management Division The Organization Management Division supports our ILS personnel and mission by developing and implementing: ¾ Workforce Planning and Management ¾ Professional Development ¾ Administrative Support ¾ Information Management ¾ Special Projects and Inquiries BW7 FOIA CBP 000570 DHS-17-0046-C-000570 53 Corporate Challenges ¾ O&M Budget ¾ Infrastructure ¾ Experienced Logisticians BW7 FOIA CBP 000571 DHS-17-0046-C-000571 54 • • • • Key Activities P-28 Disposal TUS 1 sustainment Prep for AJO sustainment MSS sustainment – Implementing critical ECPs – Right sizing parts • Northern Border (b) (7)(E)sustainment – Implementing critical ECPs – Supply chain optimization • Prep for NB OIC sustainment • MSS and Block 1 Technical Training • Acquisition Logistics Working Group (ALWG) – ILS Competency Certification BW7 FOIA CBP 000572 DHS-17-0046-C-000572 55 Questions - 5% PMO’s Business Operations Directorate (BOD) (b)(6);(b)(7)(C) 6 JAN 2011 BW7 FOIA CBP 000574 DHS-17-0046-C-000574 Business Operations Overview Mission • Lead and administer OTIA’s fiscal management systems, processes, and products • Enhance PMs success through disciplined project baselining, assessment, and control • Demonstrate continuous improvement with measured results Imperatives • Decentralize – Set budget/funds management with PMs • Ownership – BOD success = PMO projects’ success • Transparency – Budget, funding decisions in “daylight” BW7 FOIA CBP 000575 DHS-17-0046-C-000575 PMO Biz Ops – Proposed Organization Director Dep Director Chief Programming and Budget Chief Funds Management Chief Cost and Schedule Mgmt Business / Financial Mgr (Air & Maritime) Business / Financial Mgr (Integ Fix Tower) Business / Financial Mgr (b) (7)(E) • Focus = BSFIT Portfolio • Support Projects • Focus = Projects • Support Portfolio Business / Financial Mgr (Mobile / Agent Sys) Business / Financial Mgr (Block 1) BW7 FOIA CBP 000576 DHS-17-0046-C-000576 PMO Biz Ops Organization Director (b)(6);(b)(7)(C) Dep: (b)(6);(b)(7)(C) tbd Business / Financial Mgr (Air & Maritime) (b)(6);(b)(7)(C) Chief Programming and Budget (b)(6);(b)(7)(C) ¾PPBES Lead ¾BSFIT, CBP Capital Programming ¾BSFIT Budget Dev, Defense, and Exn Plan ¾Database Maintenance ¾DHS, CBP Budget Liaison Chief Funds Management (b)(6);(b)(7)(C) >Funds allocation, execution (PRs, Inv) ¾Reporting, analysis, and reprogramming Chief Cost and Schedule Mgmt (b)(6);(b)(7)(C) (Det) Business / Financial Mgr (Integ Fix Tower) (b)(6);(b)(7)(C) Business / Financial Mgr ¾Lifecycle Cost Estimating / Analysis ¾Earned Value Mgmt ¾IMP-IMS Mgmt (b) (7)(E) tbd Business / Financial Mgr (Mobile / Agent Sys) ¾SAP System Admin ¾Program Control Tools tbd ¾DHS, CBP Execution ¾PM Assessments, Business / Financial Mgr (Block 1) BW7 FOIA CBP 000577 Liaison Assistance DHS-17-0046-C-000577 Business / Finance Managers Accountable manager to the PM for— • Project baselines, including – – – – – • • Work Breakdown Structure(s), linked to Components of a Project Work plans (IMP), linked to Acqn Prog Baseline (APB) Schedules (IMS), linked to Cost estimates and time-phased budgets Associated business risks and mitigation efforts PPBES Input, e.g., RAP, RAD, Budget, Spend Plans, Program assessment and reporting – Progress vs. Planned – Mgmt reporting (nPRS, OTIA reviews, etc) – Change control (programmatic baseline) • • Contract financial execution: PRs, POs, Invoicing, performance reporting Acquisition planning and procurement support docs BW7 FOIA CBP 000578 DHS-17-0046-C-000578 BOD Near-Term Priorities • Complete Reorganization – Personnel Re-alignments, Fill “TBDs” – PMO Integration and “Battle Rhythm” – Performance Plans, Supervisor Discussions • Portfolio Reset Æ BSFIT Capital Investment Projects database – FY10/11 Funds Allocation – Detailed Execution Plans for revised OTIA plans – OMB Exhibit 300 Reset (must be sync’d with desired nPRS structure) • BOD Key Process Development, Documentation • CBP-wide Capital Programming Process Responsibilities - tbd • Pending GAO Report—Improper Payments? Invoicing? • TUS-1, AJO-1 Final Asset Disposition BW7 FOIA CBP 000579 DHS-17-0046-C-000579 Border Security Fencing Infrastructure and Technology (BSFIT) Financial Picture BW7 FOIA CBP 000580 DHS-17-0046-C-000580 BSFIT Budget Track $ in Millions FY10 FY11 FY12 FY13 FY14 FY15 FY16 800.0 574.9 588.3 602.8 617.6 632.6 ----- FY12-16 RAD (08/10) (95.2) (100.9) (106.6) (112.5) 529.4 FY12 Passback (12/10) (54.1) 529.4 FY11-15 RAD (08/09) FY11 Pres. Budget (02/10) (.7) Border Security Supp TACCOM Increase 14.0 Border Security Supp Tech Rescission (100.0) FY12 Pres Budget Delta 714.0 574.2 439.0 501.9 510.9 520.1 (100.0) (.7) (149.3) (100.9) (106.6) (112.5) BW7 FOIA CBP 000581 DHS-17-0046-C-000581 Current BSFIT FY10-16 Funding (FY13-16 Based on Final DHS RAD) $ in Millions PPA BSFIT PM BSFIT D&D BSFIT O&M BSFIT Total Border Tech D&D Border Tech O&M Border Tech Total TACCOM D&D TACCOM O&M TACCOM Total TI D&D TI O&M TI Total FY10 92.0 438.0 170.0 700.0 FY11 69.2 379.0 126.0 574.2 FY12 59.6 240.0 139.4 439.0 FY13 68.5 278.7 154.7 501.9 FY14 68.1 253.3 189.4 510.9 FY15 67.7 239.3 213.1 520.1 FY16 61.0 235.8 232.6 529.4 235.9 92.4 328.3 314.0 42.0 356.0 200.0 64.4 264.4 238.7 73.7 312.4 213.3 92.4 305.8 199.3 110.1 309.4 195.8 121.6 317.4 51.0 2.6 53.6 40.0 9.0 49.0 40.0 13.0 53.0 40.0 17.0 57.0 40.0 31.0 71.0 40.0 35.0 75.0 40.0 41.0 81.0 151.1 75.0 226.1 25.0 75.0 100.0 0.0 62.0 62.0 0.0 64.0 64.0 0.0 66.0 66.0 0.0 68.0 68.0 0.0 70.0 70.0 BW7 FOIA CBP 000582 DHS-17-0046-C-000582 FY11 Budget Status • Congress unable to complete FY2011 DHS Appropriations bill - Currently under Continuing Resolution Authority through March 2011 - OTIA’s CR ceiling pegged to our FY2011 PB request • Unclear whether we’ll see new FY2011 Appropriations bills Appropriation ($ in Millions) Prior Year Rescission ($ in Millions) President’s Budget Submission (02/10) 574.2 0.0 House Appropriations Subcommittee (06/10) 470.0 0.0 Senate Appropriations Subcommittee (07/10) 574.2 0.0 House Full-Year Continuing Resolution (12/10) 574.2 0.0 Senate Consolidated Approp. (Omnibus) (12/10) 574.2 68.0 Congressional Action Taken • Carry-over (FY10 and Prior): Tech D&D $94m; Tech O&M $22m; PM BW7 FOIA CBP$52m 000583 DHS-17-0046-C-000583 Block 1 BW7 FOIA CBP 000584 DHS-17-OO46-C-000584 Tucson 1 (TUS-1) Status Update • All towers built and in use. C2 facility completed and in use. • Systems Acceptance Testing (SAT) conducted during July-August 2010 – – – • (b) (7)(E) (b) (7)(E) Boeing declared RFOT&E 23 September • Operational Test and Evaluation (OT&E) completed November 2010 – awaiting preliminary results • We expect to take possession of the system from Boeing Jan 2011. At that time Border Patrol will assume full control of the system • Border Patrol using system for Early Ops since Feb 2010 (b) (7)(E) – – Led to apprehensions (As of 25 Dec 2010) Led to the capture of (b) (7)(E) of illegal drugs (As of 25 Dec 2010) BW7 FOIA CBP 000585 DHS-17-0046-C-000585 AJO-1 Status Update (b) (7)(E) • All towers built and in use. C2 facility completed and in use. • Remaining construction: – – – • -- Grid Power hook-up for (b) (7)(E) - to be completed Mar 2011 Completion of impound lot at (b) (7)(E)POE – to be completed Jan 2011 Remediation of site on – to be completed Mar 2011 (b) (7)(E) Systems Functional Test completed in October 2010 in lieu of Systems Acceptance Test – System Functionality and Sensor Fusion demonstrated successfully • Boeing declared RFOT&E 16 December. No operational test and evaluation to be conducted at this time • We expect to take possession of the system from Boeing in Feb 2011. At that time Border Patrol will assume full control of the system • Border Patrol using the system for Early Ops since the end of August 2010 – – Led to Led to (b) (7)(E) apprehensions (as of 25 Dec 2010) (b) (7)(E) of marijuana seized (as of 5 Dec 2010) BW7 FOIA CBP 000586 DHS-17-0046-C-000586 Block 1 Status SSTO merged ILS on 2 December 2010 Assumptions for the future: – – – – No new deployments of Block 1 System TUS-1 and AJO-1 O&M efforts ONLY past March 2011 New Operations and Maintenance Task Order (OMTO) to be awarded by end of March 2011 Period of Performance (POP): 12 Month Task Order with 6 month Priced Option (total 18 months through FY12) – • Proposed Contract Type: FPIF System Changes to be started under SSTO prior to April 2011: – – – – – Laser Illuminator ECP and Radar controls ECP (Boeing funded) Maintenance Laptop (MLT) ECP UGS upgrade ECP New Block 1 S/W Build ECP (TBD) Grid Power ECP (ISEA vs. Boeing) BW7 FOIA CBP 000587 DHS-17-0046-C-000587 Integrated Fixed Towers - (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) BW7 FOIA CBP 000588 DHS-17-0046-C-000588 Advanced Wireless Services (AWS) Spectrum Relocation - Overview Segment Description NEED 0 Advanced Wireless Services (AWS) (b) (7)(E) Phase II, Upgrade Advanced Wireless Services (AWS) (b) (7)(E) Phase II, Upgrade - 1 ANALYZE SELECT OBTAIN 2A 3 2B PRODUCE DEPLOY SUPPORT Microwave Spectrum Relocation • Level 3 acquisition ( (b)(3) Lifecycle Cost) – Legacy System Upgrade – (b)(3) Awarded from OMB for AWS Spectrum Relocation • Phase I - (b)(3) • Phase II - (b)(3) • ILS & PM Support - (b)(3) • Current Status: Adjusting scope due to affordability concerns. • Acquisition Strategy – Inter-Agency Agreement (IAA) w/ SPAWAR Systems Center, San Diego • Serco - PM and Installation and Engineering Support • NAVFAC – Environmental, Real Estate and Construction BW7 FOIA CBP 000589 DHS-17-0046-C-000589 72 AWS: Revised Strategy • Major program cost driver is the construction of new towers (b) (7)(E) – and Yuma Sectors (b) (7)(E) , Class III Tower Str • (b) (7)(E) (b) (7)(E) – Sites from Border will remain at current frequency, however with upgraded DHS security compliant equipment. – – – – (b) (7)(E) • Assumption: New program entails additional funds • CBP is in better position to more accurately estimate construction costs • (b) (7)(E) – Provide (b) (7)(E) data path to Sector Headquarters or Station. – AWS towers located within (b) (7)(E) of border are upgraded or brought into (b) (7)(E) specification or replaced – High bandwidth (video) Requirement – New Tower Construction BW7 FOIA CBP 000590 DHS-17-0046-C-000590 – Anticipated to support Integrated Fixed Tower approach 73 Integrated Fixed Towers (IFT): Overview Segment Description NEED 0 Integrated Fixed Towers 1 ANALYZE SELECT OBTAIN 2A 3 2B PRODUCE DEPLOY SUPPORT Persistent Awareness of Border Activities • Level 1 acquisition (>(b)(3) Lifecycle Cost) – DHS Acquisition Directive 102-01 compliant • Current Status – Developing tailored Systems Engineering Lifecycle (SELC) plan (COTS/NDI) – Initial Acquisition Decision Event (ADE): ADE 3 – Current AoA effort will support ADE 3 decision • Preliminary Acquisition Strategy – – – – – – Leverage P-28/Block 1 lessons learned No system development; procure COTS/GOTS system Conduct near term market survey/request for information (RFI): January Competitive award, firm-fixed price, IDIQ contract Verify system performance in IOC region selected by OIAD May include ‘down select’ & system demonstrations BW7 FOIA CBP 000591 DHS-17-0046-C-000591 74 IFT: Initial Focus Areas • Capability Development Plan (CDP): under review • Establish & kick off Project IPTs – Operational Requirements IPT – Project Management IPT – Tower and Power IPT – C4STA IPT • Market Survey – RFI complete and under review by Contracting – release date TBD – Industry Day is TBA • Operational Requirements Document – Completed initial draft – Final draft due in March, 2011 BW7 FOIA CBP 000592 DHS-17-0046-C-000592 75 IFT: Preliminary Timeline I Initial Planning Pre-acquisition activities Project Documentation SELC Documentation and Reviews Q4 ... 11 FY11 I Q2 11 CDP/ORD 11 FY12 Q2 11 ... ,, Develop PM Docs ,, I I PPR I I • SELC Docs I • SDR • I I I I I QFY13 I •••I EAB Note: Timeline assumes no system development (COTS/GOTS) and ability to leverage environmental review work completed as part of SBInet Program. 11 I ADE 3 RFP(s) • TRR II • PRR I Q2 - - I I ,, ,, I 11 Additional Acronl(ms EAB: Enterprise Architecture Board CDP: Capability Development Plan RFI: Request for Information RFP: Request for Proposal ORD: Operational Requirements Doc IOC: Initial Operational Capability SELC: Systems Engineering Lifecycle ADE: Acquisition Decision Event ,, I Q4 SELCStage Reviews SOR: System Definition Review PPR: Project Planning Review Integration Readiness Review IRR: PRR: Production Readiness Review TRR: Test Readiness Review I RFI I I Develop RFP(s) Market Survey II Q3 11 I ... ... ~ Q4 11 ~, Acquisition Decision Events Development/ Production Q3 11 I I Award(s) I • ,~ ~, I • I IOC I Deploy IOC Region I ,, 76 ,, BW7 FOIA CBPI 000593 Acceptance Testing DHS-17-0046-C-000593 r Ultra Light Aircraft Detection (ULAD): Overview Segment Description NEED 0 Ultralight Aircraft Detection 1 ANALYZE SELECT OBTAIN 2A 2B 3 PRODUCE DEPLOY SUPPORT Detect/track low-flying aircraft with small radar cross section • Level 3 acquisition (<(b)(3) Lifecycle Cost) – Purchase up to (b) (7)(E) systems for northern and southern borders • Current Status: – Finalizing Source Selection Plan and Request for Proposal (RFP) – Blue Review scheduled for mid January – approval to release RFP • Acquisition Strategy – Non developmental; procure COTS/GOTS system – Multiple award, firm-fixed price, IDIQ contract; 2-yr base plus 8, 1yr options – Verify unit performance via Acceptance Test and Evaluation BW7 FOIA CBP 000594 (ATE), ULAD Acceptance Testing (UAT) and operational test DHS-17-0046-C-000594 event 77 Miscellaneous Projects: Status • • (b) (7)(E) • (b) (7)(E) BW7 FOIA CBP 000595 DHS-17-0046-C-000595 78 Mobile/Portable Asset Program Program Portfolio - January, 2011 - (b)(6);(b)(7)(C) Executive Director Program Management Office Operations Management Office I -------, Detailed from another PMO Division 1_______ I I I I I (b)(6);(b)(7)(C) Deputy Executive Dir . Program Management Office Southwest Field Office PMO Support Staff Air and Marine Domain Program Integrated Fixed Towers Program 1 CJf.: ---1 CJ :CJ:! Program Manager Program Manager IPT Manager Deputy Program Manager : --------,' I Lead Systems Engineer dD' 11 ,_______ J~ r-------, IPT Analyst I I IPT COTR I -------, I Assistant PM for I Business II _______ II ...... Increment 1 Project Manager :1 \i~---~'I , ______ .,,,.11 N.B . Inc 1 I I : Deputy Program Manager Lead Systems Engineer ...______.... I Assistant PM for I Logistics I I I 1_______ -+ I I IPT - AMDA Asst PM for Logistics T&P IPT Mgr T&P Program Analyst T&P IPT COTR T&P IPT C4STA IPT Mgr Assistant PM for Business C4STA IPT Analyst (b) (7)(E) SBInet Block 1 Program CJ CJ I-------, Deputy Program Manager IPT Analyst I I II I I Lead Systems Engineer 11 I IPT COTR I\ I I I I Assistant PM for I Business II_______ II I I I Asst PM for Logistics '---------------, I I I I Assistant PM for I I I Business I I '-------- I / , (b) (7)(E) PT I-------, I-------, +-~ IPT Manager l'-------'1 Deputy Program Manager I Asst PM for Logistics I 1_______ CJf CJiCJi r-------::o: '-------_ --------, ___ Program Manager Program Manager I Lead Systems Engineer II_______ Mobile /Portable Asset Program System Program •- ..... ___ ... • J,o... Deputy Program Manager '------I Lead Systems Engineer ULAD /APSS/TID !_______ r-------,, I Asst PM for Logistics MVSS/MSC PM 11 :_______ J! r-------,, II Assistant PM for Business '-------- C4STA IPT COTR C4STA IPT AWS COTR AWS COTR r-------,'- _____.... AWS Project Manager AWS Analyst ULAD /APSS/TID PM Program Manager BW7 FOIA CBP 000597 DHS-17-0046-C-000597 ~----1 MVSS/MSC COTR I11, _____ I\'- , -------.-J,' MVSS/MSC _ 'I Mobile/Portable Asset Program Portfolio Manager (b)(6);(b)(7)(C) ULAD/APSS/TID PM (b)(6);(b)(7)(C) Deputy Portfolio Manager (b)(6);(b)(7)(C) ----, ,_.., ---Lead Systems I Engineer (b)(6);(b)(7)(C) I I __ (b)(6);(b)(7)(C) I 1--- , I -- -----, Asst PM for Logistics (b)(6);(b)(7)(C) I , I (b)(6);(b)(7)(C) I I ---1 ----Assistant PM for I L__ I (b)(6);(b)(7)(C) I J BW7 FOIA CBP 000598 DHS-17-0046-C-000598 WE) New Upgrade January 6, 2011 (b) (7)(E) History • (b) (7)(E) • Originally named (b) (7)(E) (b) (7)(E) • • Built on northern and southern border 1997-2005 • (b) (7)(E) • • • (b) (7)(E) towers nationwide (b) (7)(E) (b) (7)(E) (b) (7)(E) BW7 FOIA CBP 000600 DHS-17-0046-C-000600 (b) (7)(E) Status (b) (7)(E) Structural Assessment currently underway – Initial Findings (b) (7)(E) BW7 FOIA CBP 000602 DHS-17-0046-C-000602 Background - SBInet AoA • AoA (Phase 1A) provided proposed Arizona Technology Deployment Plan for Arizona border to support decisionmaking (b) (7)(E) – Focus Area 1 ( • • • – Focus Area 2 ( (b) (7)(E) ) (b) (5) • (b) (7)(E) – Focus Area 3 ( • • – Focus Area 4 ( (b) (7)(E) ) • • – Total (b) (7)(E) from AoA • • ) (b) (5) ) (b) (5) (b) (5) (b) (5) BW7 FOIA CBP 000603 DHS-17-0046-C-000603 Recommended Arizona. Border Technology (b) (7)(E) Schedule FY11 Jan - Mar (b) (7)(E)Upgrade (b) (7)(E) New - Target Apr - Jun FY12 Jul - Sept Oct - Dec Jan - Mar Apr - Jun Jul - Sept (b) (7)(E) RFP Release - Estimated Contract Award - Estimated Delivery/Deployment Period BW7 FOIA CBP 000605 DHS-17-0046-C-000605 ASSUMPTIONS for (b) (7)(E) • Acquisition Strategy – COTS (no development) – FFP – Combined RFP for Upgrade & New (preferred) • Full C&A will be required (encryption) (b) (7)(E) • Upgrade/New – – – – – – will include (b) (7)(E) BW7 FOIA CBP 000606 DHS-17-0046-C-000606 Land, Air and Maritime Systems (NB 0000000000000000 Organizational Chart (b)(6);(b)(7)(C) Land, Air and Maritime Domain Awareness - (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) NAVAIR ILS Division ILS/Sustainment Program Analyst NBP (Incre 1) Project Manager NB Integration Demo (b)(6);(b)(7)(C) CTR Support VACANT CTR Support - (b)(6);(b)(7)(C) Project Lead/COTR (b)(6);(b)(7)(C) OIT Detailee – (b)(6);(b)(7)(C) CTR Support (b)(6);(b)(7)(C) Technical Design Agent NSWC-Dahlgren CTR Support (b)(6);(b)(7)(C) (b)(6);(b)(7)(C) Project Manager Air & Maritime Domain Awareness Project - (b)(6);(b)(7)(C) Program Analyst (b)(6);(b)(7)(C) Program Analyst (b)(6);(b)(7)(C) LCDR Project Lead Business Management (b)(6);(b)(7)(C) CTR Support (b)(6);(b)(7)(C) CTR Support (b)(6);(b)(7)(C) Mission Support (b)(6);(b)(7)(C) APCP-X Intern (b)(6);(b)(7)(C) APCP-X Intern BW7 FOIA CBP 000608 DHS-17-0046-C-000608 Dilbert BY SCOTT ADAMS . CA.N I GET A ROUGH SCHEDULE EE,TIMAn: FOP.THE:me OPBNING? i I .--- --. , •-- ..,. ... ; ti I i Ij DECISION6 WILi!.BE MADE:.~EO?Lf WllL GET HVf\T . FOR EVERVON£~ SA.KE. T.. E &AFE&TTHING 1 CP.N00 IS t-'\ii\KEAN ANNO'YI!NG HUM.MING SOU .D IJNTlL YOV GO -y--------._ A.WAY. HUM.MMMM MMl'"\MMJ"\MM.M - MMMMM_ YOU'R'E TME L(.lt40Of GU¥ WHO WILL REM,OVE VS.EfUl QUl\l IfIER5 A.'NO Dl&Tlili.'IBU ITE A. t,lill; '4.&l'F 1T lS TP.UEIN "LL CASE&. HN.f OF l lfE IS Mll.klt4G PEOPLEGO tr,.WA.'V , BW7 FOIA CBP 000609 DHS-17-0046-C-000609 Northern Border Project Northern Border Project (NBP) DHS-17-OO46-C-00061 1 Detroit Sector Sites DHS-17-OO46-C-000613 Niagara Falls N (b) (7)(E) Official Use(b) (7)(E) BuffaloForSector Sites (b) (7)(E) Can BW7 FOIA CBP 000614 Lake Erie DHS-17-0046-C-000614 Northern Border Integration Demonstration Northern Border Integration Demonstration (NBID) Capability Description Operational Integration Center (OIC) The establishment of the OIC capabilities to support developmental efforts with Hanscom Air Force Base (HAFB) / MIT, National Air & Space Intelligence Center (NASIC), System Engineering Solution Inc. (SESI)/Old Dominion University (ODU), Air and Marine Operation Center (AMOC), Office of Information Technology (OIT), and others OIC – Facility Construction The construction of the OIC Facility at (b) (7)(E) (b) (7)(E) Tactical Communications Program [OFO] Sensor Infrastructure Situational Awareness System (SAS) (NSWCDD – Technical Design Agent Monitor and Surveillance Approved Requirements (SAS) (b) (7)(E) Air & Marine Sensors (Downlink) Mobile Surveillance Systems Law Enforcement Technical Collection (LETC) Video Exploitation (b) (7)(E) Dual Band Radios to improve communications and situational awareness to the Offices of Border Patrol, Air and Marine, Field Operations, and OIC partners - - RADAR capabilities to the (b) (7)(E) tower site and the (b) (7)(E) site Interagency Agreement (IAA) with the Technical Design Agent, Naval Surface Warfare Center-Dahlgren Division (NSWCDD), to develop and deploy the Collaboration Network (CN) and Law Enforcement Technical Collection (LETC) system development and implementation Several surveillance requirements to include Common Situational Display (CSD aka Video Wall), Network equipment and circuits (HSDN, USCG, AMOC, OneNet), and Geospatial Information System (GIS) support. Software developed (b) (7)(E) Aircraft video downlink capabilities for the (b) (7)(E) for mission critical video surveillance I (b) (7)(E) Up to Mobile Surveillance Capabilities (MSC) to priority locations in the NB (b) (7)(E) IAA with NSWCDD in collaboration with SPAWAR San Diego for the LETC system implementation (b) (7)(E) Management Reserve for Emerging Threats Unknown risks/requirements (emerging threats) BW7 FOIA CBP 000616 DHS-17-0046-C-000616 Operations Integration Center (NBID) Original Building Structure BW7 FOIA CBP 000618 DHS-17-OO46-C-000618 Original Building Floor Plan 7 BW7 FOIA CBP 000619 DHS-17-OO46-C-000619 Floor Plan for OIC (b) (5) Design Notice to Proceed Issued on 2/3/2010 BW7 FOIA CBP 000620 DHS-17-0046-C-000620 OIC Functionality & Stakeholders (b) (7)(E) - New capabilities provided by NBID BW7 FOIA CBP 000621 DHS-17-0046-C-000621 Humble Beginnings… Interior on March 18, 2010 Exterior on March 18, 2010 BW7 FOIA CBP 000622 DHS-17-0046-C-000622 OIC Building Abatement LC) C) BW7 FOIA CBP 000623 DHS-17-0046-C-000623 Demolition Start after Abatement Notice to proceed (NTP) for Abatement & Demolition Issued 03/3/2010 BW7 FOIA CBP 000624 DHS-17-0046-C-000624 Demolition of Interior BW7 FOIA CBP 000625 DHS-17-OO46-C-000625 OIC Building Exterior Original Structure March 31, 2010 Oct 29, 2010 BW7 FOIA CBP 000626 DHS-17-0046-C-000626 Video Wall Installation Continued 7 DHS-17-OO46-C-000629 OIC Offices - BEFORE Conference Room Deputy OIC Director’s Office OIC Director’s Office MayBW7 7,FOIA 2010 CBP 000631 DHS-17-0046-C-000631 OIC Offices - AFTER I l I I I I I I I OIC Director’s Office Conference Room Deputy OIC Director’s Office BW7 FOIA CBP 000632 DHS-17-0046-C-000632 HSDN Room BW7 FOIA CBP 000633 DHS-17-0046-C-000633 Large Conference Room BW7 FOIA CBP 000634 DHS-17-OO46-C-000634 The Necessities Grub Station BW7 FOIA CBP 000635 DHS-17-0046-C-000635 Vista Radar (NBID) 0000000000000000 Vista Radar Screen Shot (NB Vista Radar Screen Shot WE) Air Maritime Domain Awareness 0000000000000000 Air and Marine Domain Awareness (AMDA) Capability Northern Border Environmental Impact Statements Operational Integration Center Description Complete regional EISs for future deployments Provides for one year of O&M for the OIC Low Flying Aircraft Surveillance Combination of ULAD radar and collaboration with DHS S&T for other technologies Combined Agency Security Centers (CASCs) Provides O&M support and limited tech refresh in Seattle Field Office POEs Maritime RADAR Commercially available maritime radar for Buffalo AOR Aircraft Video Data Link Law Enforcement Technical Collection Ku Band Satellite Backhaul Procure • (b) (7)(E) video downlink stations Utilize SPAWAR San Diego as Technical Design Agent to develop LETC Database Proof of concept in Air and Marine P-3 BW7 FOIA CBP 000640 DHS-17-0046-C-000640 Maritime Radar 7 BW7 FOIA CBP 000641 DHS-17-OO46-C-000641 Low Flying Aircraft Surveillance (b) (7)(E) The Threat: Blaine, Spokane, and Havre Sectors BW7 FOIA CBP 000642 DHS-17-0046-C-000642 Aircraft Video Downlink 7 BW7 FOIA CBP 000643 DHS-17-OO46-C-000643 Law Enforcement Technical Collection (LETC) Approach: – Develop LETC data base environment that can capture all current and future LETC needs – Effort should address the following priorities • (b) (7)(E) • • (b) (7)(E) • Need a Data Base that has capability to leverage useful widgets that involve little or no cost – Implement Inter Agency Agreement (IAA) with SPAWAR San Diego for effort (b) (7)(E) BW7 FOIA CBP 000644 DHS-17-0046-C-000644 Focus Areas for 2011 CBP’s Strategic Goals and Priority Initiatives for 2011 • • Mission Set 1: Securing America’s Borders - CBP protects the United States and the American people from the entry of unlawful or dangerous people and goods. Securing the physical borders of the United States is and will remain an essential mission for CBP. – Priority Area 1: Securing the Southwest Border - To secure the southwest border, CBP must increase the probability that those attempting illegal entry will be apprehended. – Priority Area 2: Securing the Northern Border, Littoral Borders, and Associated Airspace CBP must also help to secure the northern border and maritime approaches to the United States Mission Set 2: Securing Flows of Goods and Movement of People Securing flows of goods, conveyances, and people to and through the U.S. is key to CBP’s success in protecting our nation at the border. – Priority Area 1: Enhance Intelligence and Targeting – Priority Area 2: Segment Flows through Vetted Traveler and Shipper Programs – Priority Area 3: Strengthen CBP’s International Presence – Priority Area 4: Rethink and Restructure the “Business Model” at Ports of Entry - CBP must ensure that CBP has the right mix of people and technology at ports of entry, and that personnel are assigned to the right functions. BW7 FOIA CBP 000646 DHS-17-0046-C-000646 CBP’s Strategic Goals and Priority Initiatives for 2011 • • Mission Set 3: Expediting Lawful Trade and Travel - Trade is crucial to America’s economic competitiveness and CBP has important trade facilitation and trade law enforcement missions – Priority Area 1: Expand Infrastructure – Priority Area 2: Transform CBP’s Engagement with the Trade Community Mission Set 4: Sustaining Investment in People and Capabilities CBP’s people are our greatest asset. We must continuously work to improve our organizational effectiveness and to multiple our presence with advanced technology. – Priority Area 1: Enhance Integrity Programs and Train New Leaders – Priority Area 2: Integrate CBP as an Organization - Mission integration – realizing operational synergies across CBP’s various Offices – is essential to CBP’s effectiveness. Managers from all parts of CBP must approach planning, BW7mindset. FOIA CBP 000647 budgeting, technology acquisition, and operations with a corporate DHS-17-0046-C-000647 SBI Strategic Plan 2010 - 2015 • Strategic Goal 1 – Enhance and improve border security by providing technology and tactical infrastructure – – – – – – • Objective 1.1 – Enhance situational awareness Objective 1.2 - Deter and dissuade illegal entries Objective 1.3 – Enhance ability to appropriately respond and resolve Objective 1.4 – Support integrated operations Objective 1.5 - Predict and anticipate Objective 1.6 – Promote technology and innovation Strategic Goal 2 – Create a center of excellence for acquisition and program management – – – – – Objective 2.1 – People Objective 2.2 – Process Objective 2.3 – Tools Objective 2.3 – Requirements and user integration Objective 2.5 – Exemplify the behaviors of a healthy, robust acquisition organization BW7 FOIA CBP 000648 DHS-17-0046-C-000648 SBI Strategic Plan (cont) • Strategic Goal 3 – Enhance, facilitate, and support operational integration including (b) (7)(E) and requirements – – – – – – – • Objective 3.1 – Organizational Objective 3.2 – Operational requirements advocacy Objective 3.3 – Technology awareness and exploration Objective 3.4 – Comprehensive DOTMLPF Objective 3.5 – Tools Objective 3.6 – Training Objective 3.7 – Facilitate CONOPS and TTPs Strategic Goal 4 - Provide a work environment that embraces diversity in our workforce, enables professional growth of our people, and facilitates a positive work-life balance – Objective 4.1 – Build and value a culture of diversity – Objective 4.2 – Recruit, develop, and retain a high-performing, mission-focused workforce – Objective 4.3 – Build and value a culture of employee appreciation – Objective 4.4 – Promote employee health and wellness BW7 FOIA CBP 000649 DHS-17-0046-C-000649 OTIA PMO Focus Areas 2011 (not prioritized…and not complete) • • • • • • • • Continuous workforce development Define, document and improve PMO processes and procedures Implement “portfolio” management Build cross-functional IPT culture Define organizational roles, authorities, and responsibilities Complete SBInet Block 1 Complete Northern Border (b) (7)(E) and OIC Successfully execute the Arizona Border Surveillance Technology Plan (pending S1 decision) • Successfully execute Northern Border air and maritime projects • Improved life cycle support planning and execution • Establish ability to support other CBP program offices BW7 FOIA CBP 000650 DHS-17-0046-C-000650 QUESTIONS AND ANSWERS BW7 FOIA CBP 000651 DHS-17-OO46-C-000651 For Official Use Only Arizona Border Surveillance Technology Plan (Advised by the SBInet Analysis of Alternatives) July 22, 2010 Abridged, for CBP Senior Staff July 23, 2010 U.S. Custollls and Border Protection BW7 FOIA CBP 000652 For Official Use Only DHS-17-0046-C-000652 For Official Use Only Executive Summary • First phase of SBInet Analysis of Alternatives (AoA) focused on Arizona: complete • Border Patrol has augmented AoA with operational assessment of technology needs • Result: baseline plan for technology deployment across Arizona • Go-forward plans will build on results-to-date – Develop the baseline – Extend analysis beyond Arizona BW7 FOIA CBP 000653 DHS-17-0046-C-000653 2 For Official Use Only (b) (7)(E) (b) (7)(E) +-' C CL) E +-' (/) CL) > C "- a +-' C'O "CL) a. 0 "'O C C'O E "- ~ C'O • Alt 1 A t-C t . (b) (7)(E) (b) (7)(E) - - --- 0... Command and Control(C2) Investment Axes are conceptual only: the positions of the alternatives are not shown to scale. ;\11 OperoUng Unit of Analytic:Services Inc:. BW7 FOIA CBP 000654 For Official Use Only DHS-17-0046-C-000654 5 3 For Official Use Only General AoA Conclusions • There is no “one-size-fits-all” solution • “Best” solution depends on specifics of a given area – Terrain, geography, population – Concept of operations and enforcement tactics (e.g., rapid egress) – Trade between cost and overall capability • Mixing and matching technologies can increase overall cost effectiveness in any given area BW7 FOIA CBP 000655 DHS-17-0046-C-000655 7 For Official Use Only Operational Assessment Goal – Identify appropriate mix of technologies to gain situational awareness to manage the Arizona border area Process – Convened a panel of operational SMEs from Arizona – SMEs briefed on the science based AoA methodology and results – Initially deferred to lower cost technology to meet the situational awareness requirement in each focus area – Recommendations informed by existing IAA, ORBBP, Arizona surge documents, and the AoA – Team doubled back to ensure proposed technology laydowns were reasonable based on the AoA Result – Proposed technology deployment in Arizona BW7 FOIA CBP 000656 DHS-17-0046-C-000656 8 For Official Use Only U.S. Customs and Recommended Arizona Border Technology (b) (5) BW7 FOIA CBP 000657 DHS-17-0046-C-000657 For Official Use Only Implications for SBInet • Fixed towers and a Common Operating Picture (COP) have a role in future technology deployments • Comprehensive technology integration may someday be useful—but best left to the future. • However, the original concept for SBInet of a single, wholly integrated “virtual fence” may not be appropriate – Not the right answer for all border areas – Not the system to integrate all other technologies – Not cost-effective BW7 FOIA CBP 000658 DHS-17-0046-C-000658 14 For Official Use Only Recommendations • Adopt Arizona proposed technology deployment as the basis for near-term decisions • Continue deployment and testing of integrated fixed towers in TUS-1 and AJO-1 • Communicate (explicitly acknowledge) changes to the SBInet program • Apply AoA methodology along the rest of the border • Optimize technology deployment based on operator judgments, the AoA, results of the fixed tower testing, and budget decisions BW7 FOIA CBP 000659 5/24/2017 DHS-17-0046-C-000659 18 For Official Use Only Arizona Border Surveillance Technology Plan (Advised by the SBInet Analysis of Alternatives) July 22, 2010 U.S. Custollls and Border Protection BW7 FOIA CBP 000660 For Official Use Only DHS-17-0046-C-000660 For Official Use Only Executive Summary • First phase of SBInet Analysis of Alternatives (AoA) focused on Arizona: complete • Border Patrol has augmented AoA with operational assessment of technology needs • Result: baseline plan for technology deployment across Arizona • Go-forward plans will build on results-to-date – Develop the baseline – Extend analysis beyond Arizona BW7 FOIA CBP 000661 DHS-17-0046-C-000661 2 For Official Use Only SBInet Analysis of Alternatives (AoA) • Part of broader, Secretarial-directed assessment of SBInet • Provides a “quantitative, science-based” assessment of types of technology approaches • Enables rigorous comparisons of technologies and analysis of operational judgments • Considers both effectiveness and cost • Does not dictate a solution, but can provide a test of reasonableness or an input to broader analysis • First Phase focused on Arizona—completed – Reviewed in detail with many DHS offices BW7 FOIA CBP 000662 DHS-17-0046-C-000662 3 For Official Use Only AoA Alternatives • Basic requirement: Awareness of border activity through surveillance and detection to facilitate apprehension • Four basic technology approaches – Agent-centric – Mobile, decentralized systems – Fixed systems with centralized control centers – Aviation centric BW7 FOIA CBP 000663 DHS-17-0046-C-000663 4 For Official Use Only +-' C CL) E +-' (/) CL) (b) (7)(E) (b) (7)(E) > C "- a +-' C'O "CL) a. 0 "'O C C'O E "- ~ C'O (b) (7)(E) (b) (7)(E) 0... Command and Control(C2) Investment Axes are conceptual only: the positions of the alternatives are not shown to scale. ;\11 OperoUng Unit of Analytic:Services Inc. BW7 FOIA CBP 000664 For Official Use Only DHS-17-0046-C-000664 13 For Official Use Only Note on UAS • AoA evaluated whether UAS could also substitute for fixed, ground-based systems (b) (7)(E) BW7 FOIA CBP 000665 DHS-17-0046-C-000665 6 For Official Use Only General AoA Conclusions • There is no “one-size-fits-all” solution • “Best” solution depends on specifics of a given area – Terrain, geography, population – Concept of operations and enforcement tactics (e.g., rapid egress) – Trade between cost and overall capability • Mixing and matching technologies can increase overall cost effectiveness in any given area BW7 FOIA CBP 000666 DHS-17-0046-C-000666 7 For Official Use Only Operational Assessment Goal – Identify appropriate mix of technologies to gain situational awareness to manage the Arizona border area Process – Convened a panel of operational SMEs from Arizona – SMEs briefed on the science based AoA methodology and results – Initially deferred to lower cost technology to meet the situational awareness requirement in each focus area – Recommendations informed by existing IAA, ORBBP, Arizona surge documents, and the AoA – Team doubled back to ensure proposed technology laydowns were reasonable based on the AoA Result – Proposed technology deployment in Arizona BW7 FOIA CBP 000667 DHS-17-0046-C-000667 8 For Official Use Only U.S. Customs and Recommended Arizona Border Technology (b) (5) BW7 FOIA CBP 000668 DHS-17-0046-C-000668 For Official Use Only Example: (b) (7)(E) within Focus Area 1 • (b) (7)(E) – – – (b) (7)(E) • AoA result: – (b) (7)(E) • Operational assessment: – (b) (7)(E) BW7 FOIA CBP 000669 DHS-17-0046-C-000669 10 For Official Use Only (b) (7)(E) : AoA Summary 0.8 0 .6 (b) (7)(E) (b) (7)(E) 0.4 0.2 Alt 1 Agent-Centric 0 (b) (7)(E) Alt 2 Fixed 1 o.s O.S (b) (7)(E) Alt 3 Mobile Alt 4 Aviation-Centric $0 OA 0 .2 0 Alt 1 Alt 2 Agent-Centric Fixed Alt 3 Mobile Alt 4 Aviation $50 $150 $200 $250 …at higher cost. Operational assessment determines whether value is worth the cost BW7 FOIA CBP 000670 DHS-17-0046-C-000670 11 For Official Use Only Focus Area 1 (b) (7)(E) • Focus Area Characteristics – – – (b) (7)(E) (b) (7)(E) • Additional Technology Requirements (ROM* initial investment) – – – – – – – – – (b) (5), (b) (7)(E) • Air Support – – – 5/24/2017 (b) (7)(E) BW7 FOIA CBP 000671 DHS-17-0046-C-000671 12 For Official Use Only Cost Estimates • Focus Area 1 – – (b) (5) • Focus Area 2 – – (b) (5) • Focus Area 3 – – (b) (5) • Yuma Sector – – (b) (5) • Cost Assumptions – Rough-Order-of-Magnitude (ROM) costs for technology investment and Operations and Maintenance (O&M) – Costs do not include air support – Costs do not include an embedded operational support cost for shared IT software and equipment of (b) (5) BW7 FOIA CBP 000672 5/24/2017 DHS-17-0046-C-000672 13 For Official Use Only Implications for SBInet (b) (5) BW7 FOIA CBP 000673 DHS-17-0046-C-000673 14 Go-Forward Plan BW7 FOIA CBP 000674 DHS-17-OO46-C-000674 For Official Use Only Implications for Boeing Contract (b) (5) BW7 FOIA CBP 000675 DHS-17-0046-C-000675 16 For Official Use Only Key Schedule Events • Complete AoA (b) (7)(E) (Arizona) • • • • • • • • • • • • Done (b) (7)(E) (b) (5) * Not including due to environmental issues (b) (7)(E) ** Dependent on GAO resolution of contractor protest BW7 FOIA CBP 000676 DHS-17-0046-C-000676 17 For Official Use Only Recommendations • • • (b) (5) • • BW7 FOIA CBP 000677 5/24/2017 DHS-17-0046-C-000677 18 Backup BW7 FOIA CBP 000678 DHS-17-OO46-C-000678 27 For Official Use Only Background • CBP currently deploys a variety of technologies along the Southwest Border • SBInet was planned to become the major, allencompassing technology solution for the border • The wisdom of this original SBInet concept is questionable • Urgency of border security issues requires a timely and rational plan for technology deployment—now—to maintain persistent monitoring and surveillance BW7 FOIA CBP 000679 DHS-17-0046-C-000679 28 For Official Use Only U.S. Customs and Current Arizona Border Technology (b) (7)(E) BW7 FOIA CBP 000680 DHS-17-0046-C-000680 For Official Use Only The Contribution of Technology • Provides information about activity – Monitoring and surveillance • Enhances ability to respond – Information about nature of incursions – Agent safety – Options (how, when, where) • Contributes as one of three elements – Personnel, tactical infrastructure, technology • Supports efforts both to gain and maintain border security BW7 FOIA CBP 000681 DHS-17-0046-C-000681 30 For Official Use Only Technology for Arizona • Compared technology alternatives against operational needs in Arizona – Advised, but not dictated, by SBInet Analysis of Alternatives (AoA) Phase 1A • Developed comprehensive technology proposal with emphasis on focus areas • “Doubled back” to ensure proposal was reasonable based on AoA BW7 FOIA CBP 000682 DHS-17-0046-C-000682 31 For Official Use Only Focus Area 2 (b) (7)(E) • Focus Area Characteristics – – (b) (7)(E) (b) (7)(E) • Additional Technology Requirements – – – – – – (b) (7)(E) • Air Support – – – (b) (7)(E) BW7 FOIA CBP 000683 5/24/2017 DHS-17-0046-C-000683 32 For Official Use Only Focus Area 3 (b) (7)(E) • Focus Area Characteristics – – – (b) (7)(E) (b) (7)(E) • Additional Technology Requirements – – – – – – – – – (b) (7)(E) • Air Support – – – 5/24/2017 (b) (7)(E) BW7 FOIA CBP 000684 DHS-17-0046-C-000684 33 For Official Use Only (b) (7)(E) Station (b) (7)(E) • Focus Area Characteristics – – – (b) (7)(E) (b) (7)(E) • Additional Technology Requirements – – – – – – – – (b) (7)(E) • Air Support – – – 5/24/2017 (b) (7)(E) BW7 FOIA CBP 000685 DHS-17-0046-C-000685 34 For Official Use Only AoA Results Depend on Area Cost-Effectiveness Comparison Analysis Area A - 0.9 Evaluation: MOE 2.0 X Q) ., ""O .E Results for All Analysis Areas A-D If> (b) (7)(E) ~ tn Q) C ~ ~ w 0.6 (b) (7)(E) (b) (7)(E) .. .. 0.3 (b) (7)(E) Cost-Effectiveness Comparison Analysis Area D -I(b) (7)(E) (b) (7)(E) MOE 2.0: Enable Timely and Effective Response For Official Use Only 39 An Operating Unif of Analytic Services Inc. -(b) (7)(E) Life-Cycle Cost, Then-Year$M BW7 FOIA CBP 000686 For om,1,1 U•• Oni'; DHS-17-0046-C-000686 ~ 35 For Official Use Only SBInet Near-Term Schedule Jul (b) (7)(E) Acceptance Testing (b) (7)(E) Operational Testing (b) (7)(E) Construction* Aug Sep Oct Nov Dec Jan Feb Mar (b) (5) (b) (7)(E) Acceptance Testing AoA Acquisition Decision Event-3 * Not including (b) (7)(E) —environmental issues BW7 FOIA CBP 000687 DHS-17-0046-C-000687 36 For Official Use Only (b) (5) Focus on • Near-ter m tec hnologies • Arizona border • SBlnet program decisions (b) (7)(E) BW7 FOIA CBP 000688 For Official Use Only 5/24/2017 An Operating Unit of Analytic Services Inc. DHS-17-0046-C-000688 37 ATTACHMENT 1 Meeting Minutes Arizona Border Surveillance Technology Plan July 22, 2010 Start time of Meeting: End time of Meeting Location of Meeting 12:30 PM 1:30 PM DHS Headquarters, Conference Room 5107 Principals in Attendance: Janet Napolitano, Dr. Tara O’Toole (b) (6) (b) (6) Alan Bersin David Aguilar Mark Borkowski (b)(6);(b)(7)(C) (b) (6) Secretary, Department of Homeland Security (DHS) Under Secretary, DHS Science and Technology Deputy Chief of Staff Chief of Staff, DHS Science and Technology Commissioner, U.S. Customs and Border Protection (CBP) Deputy Commissioner, CBP Assistant Commissioner, CBP, Office of Technology Innovation and Acquisition Deputy Chief, CBP, Office of Border Patrol Deputy Director, Homeland Security Studies and Analysis Institute (HSSAI) Commissioner Bersin initiated the meeting by providing an executive summary to highlight the purpose of the briefing. In his opening comments he highlighted the following key points. • • • • CBP had completed the first phase of the Analysis of Alternative (AoA) as requested by Secretary Napolitano. The AoA was a collaborative effort between CBP and DHS. The Border Patrol utilized the results of the AoA to provide recommendations for a baseline deployment of technology for Arizona which includes Tucson and Yuma Border Patrol Sectors. CBP will continue this approach and extend the AoA to other areas along the southwest border and recommend technology baselines. Commissioner Bersin concluded his remarks and asked Assistant Commissioner (AC), Mark Borkowski, to provide Secretary Napolitano with an overview of AoA. In his presentation, AC Borkowski provided the following remarks relative to this section of the briefing. • The AoA did produce a “quantitative, science based” assessment of types of technology approaches. BW7 FOIA CBP 000689 DHS-17-0046-C-000689 • • • • • The AoA was asked to consider whether or not the SBInet technology developed in Tucson and Ajo was cost effective technology that should be considered as an option for other areas along the southwest border. An AoA considered both effectiveness and cost of technologies. An AoA does not dictate a point solution, but it provides a test of reasonableness and inputs to the operational community. This phase of the AoA concentrated on the basic requirement of awareness of border activity through surveillance and detection to facilitate apprehension. In this phase there were four basic technology approaches analyzed by the AoA. (b) (7)(E) o Agent Centric(b) (7)(E) o Mobile, (b) (7)(E) o Fixed Systems (b) (7)(E) (b) (7)(E) o Aviation Centric- - AC Borkowski then provided a more detailed discussion surrounding the Air Centric approach as it relates to (b) (7)(E) and how it was evaluated in the AoA. - • The AoA did not evaluate whether or not we need the capabilities because it supports many other DHS missions and complements border operations. • (b) (7)(E) (b) (7)(E) The major differences between the • • - (b) (7)(E) and (b) (7)(E) are as follows. (b) (7)(E) AC Borkowski finished the AoA portion of the briefing by providing these general conclusions. • • The AoA illustrates that there is no “one size-fits all” solution. • taken into account when selecting the best solution. Mixing and matching technologies can increase overall effectiveness in any given area. (b) (7)(E) must be At this time, AC Borkowski turned the briefing over to Deputy Chief (b)(6);(b)(7)(C) to present the operational assessment of the AoA and the process by which they used this information to (b)(6);(b)(7)(C) recommend the baseline of technology for the Arizona Sectors. Deputy Chief started by stating that their goal had been to identify the appropriate mix of technologies to gain situational awareness to manage the Arizona border. He then provided an overview of the process that was followed by their office. - • A panel of agents from the Tucson and Yuma sectors were convened to review the AoA and make technology recommendations based on the AoA results. BW7 FOIA CBP 000690 DHS-17-0046-C-000690 • • • • The panel was provided a detailed brief by the HSSAI on the AoA, as well as instruction on how to interpret and use the data contained within the report. When considering technology solutions for a given area, agents were asked to defer to the lowest cost technology to meet their situational awareness requirement. Border Patrol, in addition to the AoA results, utilized information from their individual concept of operations, Operational Requirements and Budget Based Planning process, and the Arizona surge documents to support their decisions. After the group finished their proposed technology laydowns, they doubled back to the AoA results to make certain that their recommendations were reasonable based on the AoA results. - -- (b)(6);(b)(7)(C) Deputy Chief referenced two maps that were generated for this briefing; one map highlighted the current laydown of technology in the Arizona Sectors and the other illustrated the proposed laydown of technology for Arizona based on their operational assessment. (b)(6);(b)(7)(C) (b) (7)(E) Deputy Chief then focused on the station to exemplify how the (b) (7)(E) agents in this working group proposed as the best capability for the (b) (7)(E) border area and how the AoA results supported this decision. (b)(6);(b)(7)(C) Deputy Chief then transitioned back to AC Borkowski who briefed one of the AoA charts that was done for the (b) (7)(E)area by HSSAI to exemplify the previous discussion by (b)(6);(b)(7)(C) Deputy Chief . (b)(6);(b)(7)(C) Deputy Chief then resumed his presentation by explaining that the working group had proposed technology solutions for all of the Arizona Sectors. The recommendations covered Focus areas 1, 2, and 3 for Tucson Sector and then Yuma Sector independently. Deputy Chief (b)(6);(b)(7)(C) utilized Focus Area 1 as an exemplar of the mixed solutions suggested by the agents and the Rough Order of Magnitude (ROM) costs for each set of technologies. Secretary Napolitano then asked several questions related to the effectiveness and practicality of (b) (7)(E) utilizing along the border. Operational discussion ensued to show where (b) (7)(E) has its advantages based on enforcement tactics used by the Border Patrol. - Finally, Deputy Chief (b)(6);(b)(7)(C) talked to the ROM costs associated with the deployment for Focus Area 1 which was presented as follows. • (b) (5) million initial investment • million annual operations and maintenance costs (O&M). Focus Area 2, 3, and Yuma sector were also listed on this chart and Secretary Napolitano wanted to know why the O&M costs for focus area 3 were higher. In the back-up charts it was pointed (b) (7)(E) out that there were and (b) (7)(E) which had higher maintenance and personnel costs. BW7 FOIA CBP 000691 DHS-17-0046-C-000691 Commissioner Bersin then introduced Dr. Tara O’Toole, the Under Secretary for DHS Science and Technology, who briefed the implications for SBInet. Under Secretary O’Toole emphasized the following conclusions. • • • (b) (7)(E) There is a role for similar to the SBInet technology in areas along the border. This type of capability based upon the knowledge we have today has proven very effective. DHS and CBP can leverage what we have learned from the SBInet program and utilize the (b) (7)(E)technology in the future but with these general caveats: o Not the right answer for all border areas o SBInet is not the system to integrate all other technologies o SBInet itself is not cost effective - Under Secretary O’Toole also emphasized that comprehensive technology integration may someday be useful, but not currently. We will focus our efforts with localized command. Commissioner Bersin then resumed briefing CBP’s go forward plan. • • • • • • - - CBP is recommending that (b) (7)(E) and (b) (7)(E) be completed and tested as planned. Continue the AoA and other technology evaluations beyond Arizona. (b) (7)(E) Utilize as a technology where appropriate. Continue leveraging benefits from our investment in SBInet technology. Emphasize our messaging that this is a change from the original SBInet concept. Evaluate the implications to the Boeing contract. AC Borkowski then spoke to more detail concerning the Boeing contract. • • • CBP is recommending that we exercise the current option year on the Boeing contract. Exercising this option allows the following work to be done. o Completion of testing and construction of (b) (7)(E) and(b) (7)(E) o Maintenance of (b) (7)(E) o Storage of steel for fence construction and repair. Boeing contract does not lock DHS into buying anything else from Boeing. - -- Commissioner Bersin then stated that CBP is proposing the following recommendations for Secretary Napolitano’s approval. • • • • • -- Adopt the proposed technology deployment as the basis for near term decisions. (b) (7)(E) Continue deployment and testing s in (b) (7)(E) and (b) (7)(E) Communicate and message the changes to the SBInet program. Continue the AoA process along the rest of the border. Optimize the technology deployments based on operator judgements, the AoA, results of the (b) (7)(E) testing, and budget decisions. - BW7 FOIA CBP 000692 DHS-17-0046-C-000692 Secretary Napolitano expressed that she was inclined to adopt the recommendations made by CBP but asked that a decisional document be packaged by CBP and submitted through the Executive Secretariat. Additionally, she gave the following instructions to CBP. 1. As we continue doing more AoAs, we should open the aperture to consider more technologies than those we might have used in the Arizona AoA. Secretary Napolitano mentioned the DoD technologies that might be available. 2. Secretary Napolitano asked that CBP do a legal review of the Boeing contract and focus on the following subjects. • • (b) (5) 3. As we continue doing more AoAs and technology deployments, Secretary Napolitano would like CBP to begin using DoD personnel experienced in base and border security to be part of a peer review panel that would assist us in technology deployments and analysis. 4. We need to change the SBInet name and begin working our external and internal messaging to key stakeholders. 5. Secretary Napolitano asked to see the work behind the Operations and Maintenance costs associated with the technology deployments. She commented that we need to see where we can be more cost effective. 6. Secretary Napolitano asked CBP to provide her a budget plan that reflects the technology recommendations in the briefing. Commissioner Bersin told Secretary Napolitano that they would follow up on her requests. He noted that CBP had produced a couple of draft documents that covered proposed messaging for the change in the SBInet label and strategy, along with our initial attempt at capturing technology deployments against our budget. Commissioner Bersin stated that he had given the initial draft to for her comment and review. (b) (6) Meeting Adjourned: BW7 FOIA CBP 000693 DHS-17-0046-C-000693 1300 Pennsylvania Avenue, NW Washington, DC 2 0 2 2 9 U.S. Customs and Border Protection Commissioner October 29, 2010 MEMORANDUM FOR: INFORMATION Janet Napolitano Secretary FROM: SUBJECT: Re art on the Comprehensive, Science-Based Re-Assessment of the Secure Border Initiative-Network Program Purpose On October 4, 2010 you approved CBP's technology deployment for Arizona that was derived from our Analysis of Alternatives (AoA) of the Secure Border Initiative-network (SBinet) and the Border Patrol's operational assessment of technology needs for Arizona. Subsequent to your approval, 0MB requested a report summarizing the findings of the AoA and describing the path forward prior to executing the technology deployment plan. In addition to 0MB, it is envisioned the report would be used for Congressional and press briefings and released publicly to ensure maximum transparency. Background: The SBinet program, as conceived in 2005, was intended to cover the entire Southwest border with a highly integrated set of fixed sensor towers. Early in its design, SBlnet gave little, if any, consideration to other technologies, as the presumption was that SBinet would handle all technology needs. Discussion The attached report describes the technology plan that CBP intends to deploy and the implications of the plan. Attachment BW7 FOIA CBP 000706 DHS-17-0046-C-000694 DEPARTMENT OF HOMELAND SECURITY REPORT ON THE COMPREHENSIVE, SCIENCE-BASED RE-ASSESSMENT OF THE SECURE BORDER INITIATIVE-NETWORK (SBinet) PROGRAM EXECUTIVE SUMMARY The Secure Border Initiative-network (SBinet) program, as conceived in 2005, was intended to cover the entire Southwest border with a highly integrated set of fixed sensor towers. Early in its design, SBinet gave little, if any, consideration to other technologies, as the presumption was that SBinet would handle all technology needs. Original plans called for deployment across the Southwest border to be complete by 2011 at a total cost of about $8 billion. By January 20 I 0, the SBinet operational deployments had just begun along 53 miles of border area in Arizonawell behind the intended schedule. Engineering development activities had overrun cost targets, creating significant concern that the final program price tag could well exceed the $8 billion estimate. Dating back to her tenure as Governor of Arizona, Secretary Napolitano has long been concerned by SBinet's continued and repeated technical problems, cost overruns and schedule delays, and believed they raised fundamental questions about SBinet' s ability to meet the needs for technology along the border. During 2009, Secretary Napolitano asked Customs and Border Protection (CBP) for an analysis of the SBinet program. Based on this analysis, in January 2010, Secretary Napolitano ordered a Department-wide reassessment of the SBinet program that incorporated an independent, quantitative, science-based "Analysis of Alternatives" to determine if SBinet was the most efficient, effective and economical way to meet our nation's border security needs. DHS completed the first phase of the assessment in Fall 2010, focused on the Arizona border, as half of all illegal border crossings currently occur there. This assessment combined the quantitative, science-based results of the Analysis of Alternatives, the input of U.S. Border Patrol agents on the front lines and the analysis of the Department's leading science and technology experts. The assessment--the first of its kind that the Department had ever undertaken for SBinet--focused on the viability and cost-effectiveness of SBinet, evaluating the operational value against its projected cost. Based on the assessment, the Department has concluded that the SBinet program, as originally proposed, is no longer appropriate. While it has generated some significant advances in technology that can improve CBP's agents' ability to detect, identify, deter and respond to threats along the border, SBinet does not and cannot provide a single technological solution to border security. Secretary Napolitano has directed CBP to end SBinet and instead utilize existing, proven technology solutions tailored to the distinct terrain and population density of each border regions--a significant departure from the original SBinet concept of a single, wideranging fixed tower-based solution across the entire border. BW7 FOIA CBP 000707 DHS-17-0046-C-000695 This new secure border technology plan will include a mixture of proven surveillance technologies, including commercially available Mobile Surveillance Systems 1, Unmanned Aerial Systems, thermal imaging devices, and tower-based Remote Video Surveillance Systems2. Where appropriate, this technology plan will also include elements of the former SBinet program that have proven successful, such as stationary radar and infrared and optical sensor towers. The Department believes that the new plan provides better coverage, more effective balance between cost and capability tailored to each area of the border, faster deployment of technology, and better linkage between operations and technology, complementing the Administration's unprecedented investments in manpower, infrastructure and resources to secure the Southwest border. The new plan will be implemented within current budget projections and will utilize funding previously requested for SBinet. CBP intends to acquire all the technologies in the new plan, including the integrated fixed towers, through full and open competitions. It is anticipated that the Arizona technology deployment will be complete in 2014 with significant elements available in 2011. Further, independent, quantitative, science-based assessments will continue along each sector of the Southwest border to determine the optimal combination of technology, and eventually across the Northern border. OBAMA ADMINISTRATION SOUTHWEST BORDER INITIATIVE Since the beginning of this Administration, OHS has dedicated unprecedented personnel, technology, and resources to the Southwest border. Today, the Border Patrol is better staffed than at any time in its 86-year history, having nearly doubled the number of agents from approximately 10,000 in 2004 to more than 20,500 today. DHS has doubled the number of personnel assigned to Border Enforcement Security Task Forces; tripled the number of U.S. Immigration and Customs Enforcement (ICE) intelligence analysts working along the U.S.Mexico border; quadrupled deployments of Border Liaison Officers; and begun screening 100 percent of southbound rail shipments for illegal weapons, drugs, and cash--for the first time ever. DHS has also deployed additional canine teams trained to detect drugs and weapons and non-intrusive inspection technology that help identify anomalies in passenger vehicles at the Southwest Border. These initiatives and investments have yielded impressive results. During this Administration, seizures of contraband along the Southwest border have increased across the board and illegal crossings continue to decline. In fiscal years 2009 and 2010, CBP seized more than $104 million 1 Within this report, we use Mobile Surveillance System (MSS) broadly to refer both to the current configuration of MSSs deployed along the border, as well as to the systems OHS will purchase from the ongoing competitive Mobile Surveillance Capability (MSC) procurement. MSSs are mobile (usually pickup truck-mounted) extensible poles with a radar, day camera, and night camera. The truck operator can view the signals from the cameras and radar on a display in the cab of the truck. 2 Remote Video Surveillance Systems, or RVSSs, are pairs of day and night cameras, often mounted on fixed poles. Each camera displays its individual image on a monitor at a Border Control Station. BW7 FOIA CBP 000708 DHS-17-0046-C-000696 in southbound illegal currency-an increase of approximately $28 million compared to 20072008. CBP and ICE also seized more than $282 million in illegal currency, more than 7 million pounds of drugs, and more than 6,800 weapons in fiscal years 2009 and 2010 along the southwest border-increases of more than $73 million, more than 1 million pounds of drugs and more than 1,500 weapons compared to 2007-2008. Moreover, Border Patrol apprehensions decreased 36 percent from nearly 724,000 in fiscal year 2008 to approximately 463,000 in fiscal year 2010-indicating that fewer people are attempting to cross the border. Further, in FY 2009 and FY 2010, ICE made over 20,100 criminal arrests along the Southwest border, an increase of approximately 12% compared to the two previous years. Over 12,850 of these arrests were of drug smugglers and over 2,560 were of human smugglers. The recent passage and signing of Southwest border security supplemental legislation will provide additional capabilities to secure the Southwest border at and between our ports of entry and reduce the illicit trafficking of people, drugs, currency and weapons. Specifically, this bill provides $14 million for improved tactical communications systems along the Southwest border; $32 million for two additional CBP unmanned aircraft systems; $176 million for 1,000 additional Border Patrol agents to be deployed between ports of entry; $68 million to hire 250 new Customs and Border Protection (CBP) officers at ports of entry and to maintain 270 officers currently deployed to ports of entry; $80 million for 250 new ICE agents; and $6 million to construct two forward operating bases along the Southwest Border to improve coordination of border security activities. Further, President Obama has deployed 1,200 National Guard troops to the Southwest border to contribute additional capabilities and capacity to assist law enforcement agencies. TECHNOLOGY AND BORDER SECURITY Reduction in the flow of illegal traffic between the ports of entry depends not on a single element like technology alone, but on the appropriate combination of personnel, tactical infrastructure, and technology. Personnel are the most robust and adaptable of these resources, as Border Patrol agents conduct surveillance and respond to incursions. Tactical infrastructure, primarily focused on physical fencing, enhances the ability of personnel to respond by creating delays or by making it easier for agents to reach a particular area. The Border Patrol primarily uses technology for detection and surveillance between ports of entry, enabling CBP to maximize its effectiveness in responding to and disrupting illicit activity. In other words, technology helps provide awareness of the amount and types of illegal activity at the border. Technology supports personnel so that they can spend more of their time responding to incursions and less time detecting them. Along the Southwest Border, the primary technology system has been the Remote Video Surveillance System (RVSS), a tower with a pair of day and night cameras, which are monitored by border patrol agents in a given area. There are currently 250 of these systems deployed along the Southwest Border. More recently, DHS has added other systems, including truck mounted infrared camera systems and radars, (Mobile Surveillance Systems, or MSSs) which are shown one of the most on an integrated display within the cab of the truck and are considered(b) (7)(E) surveillance technologically advanced ground-based systems. There are currentl-obile BW7 FOIA CBP 000709 DHS-17-0046-C-000697 systems (MSSs) deployed along the Southwest border. In addition there are more than 130 aircraft (planes and helicopters) deployed to the Southwest Border along with 3 Unmanned Aircraft Systems (UASs). SBinet HISTORY Beginning in 2005, the Department initiated an ambitious technology program known as Secure Border Initiative-network (SBinet). SBinet was intended to cover the entire Southwest Border (and eventually the entire border) with a highly effective, comprehensive, and tightly integrated surveillance system where information from multiple sensors could be combined into a single display, providing a clear picture of activity within a large area. Over time, the development of SBinet was scaled back due to several factors, including technical issues that led to significant schedule delays and cost overruns; increased use of other technology systems that reduced the demand on SBinet; and recognition that personnel and other technology could more effectively fulfill security needs in certain areas of the border. Given these issues, in 2009, Secretary Napolitano asked Customs and Border Protection (CBP) for an analysis of the SBinet program. Based on this analysis, Secretary Napolitano froze funding for SBinet beyond the ongoing, initial deployments of Block 1 and ordered a Department-wide reassessment of the SBinet program that incorporated an independent, quantitative, science-based "Analysis of Alternatives" to determine if SBinet was the most efficient, effective and economical way to meet our nation's border security needs. The assessment focused on two fundamental questions. The first was whether or not the SBinet program was viable-in other words, if it could ever be made to work effectively and fulfill the original intent of the program. The second was related to cost-effectiveness. Even if SBinet was viable, the assessment evaluated whether other equally or more effective technologies were available at lower cost. Prior to this assessment, the Department had not conducted a comprehensive cost-effectiveness analysis to assess the operational value of the SBinet system against the projected cost even though such an analysis is normally a well-established prerequisite for a project of this size and scope. SBinet VIABILITY The issue of viability was evaluated within the context of the initial SBinet configuration, known as SBinet Block 1, which has completed construction in two areas of the Arizona borderTucson-1 (TUS-1) and AJO-1. While testing and evaluation in each of these sectors is underway 3, the Border Patrol has begun using the technology. The Border Patrol has used TUS1 since February 2010 and AJO-1 since August 2010. 3 Engineering testing ofTUS-1 is complete and the results are currently under analysis. In October and November, the Border Patrol will conduct Operational Test and Evaluation of TUS-1. AJO-1 will complete its engineering testing by the end of the year. BW7 FOIA CBP 000710 DHS-17-0046-C-000698 Although it is too early to quantify the effectiveness of the SBinet Block 1 system, the qualitative assessments from the Border Patrol suggest that select elements of the technology such as sensor towers integrated together to observe a large area in a localized areas, can enhance operational capabilities. In the case of TUS-1, agents noticed an increase in apprehensions of illegal entrants when they first started using the system despite no apparent increase in illegal traffic and, over time, a decrease in activity and apprehensions. In other words, it appears that the use of the TUS-1 system, in association with other initiatives like increased personnel and tactical infrastructure, contributed to decreasing the flow of illegal entrants and increasing the likelihood of their apprehension. SBinet COST-EFFECTIVENESS To assess the cost effectiveness of SBinet, DHS conducted an analysis using a standard practice known as an Analysis of Alternatives (AoA). The first phase, which is now complete, analyzed technology options for Arizona. The Department will conduct additional phases in the coming months to complete the analysis of the entire Southwest Border. In the AoA, DHS quantified the effectiveness of various possible technology solutions by identifying the most important elements of effectiveness, and then assigning scores that reflect how well each technology option supports each of these elements. These scores are called "Measures of Effectiveness" (MOEs). Because there are several MO Es, each one was weighed, then combined into a single, overall effectiveness score. The AoA also generated rough-order-of magnitude (ROM) cost estimates for each technology option. Together, the AoA compared the overall effectiveness score and ROM for each option. Figure 1 presents an example of this analysis: Alt n Most Cost-Effective 10 -- -----• -----------------------------• _______ _LeastCost~e_ctlve j -----------•--------- •-- - ---+------- ------- • Alt 1 0 -+-------,-------.-- 0 2 4 Cost 6 8 10 12 Figure 1: Example Depiction of AoA Results BW7 FOIA CBP 000711 DHS-17-0046-C-000699 Each red diamond on the chart represents a discrete technology alternative ("alt"). Therefore, the chart depicts the relative "scoring" of each alternative based on both effectiveness and cost. In figure 1, the set of options highlighted in the oval at the top left comer are the most cost-effective options. They have a high effectiveness score at a low cost. Conversely, the options highlighted in the oval at the bottom right comer are least cost effective. The Department used this process to evaluate technology options in four specific areas along the Arizona border that were representative of other areas on the Southwest border and will complete individual assessments of additional sectors in the months ahead. ... C , QI F ,n '1) > .µ L. '- E (\) ,..__ m o." 0 -C1 C: m C:0111n1and and Ccntrol (C2) Investment Placementof alternativesis purelynotionaland illustrative.It does not representthe actualscoring of the variousalternativesin any givenscenario Figure 2: Structure of the AoA for Arizona Technology As shown in Figure 2, we analyzed four types of technology options. Alternative 1, AgentCentric, included small, usually handheld systems that assist individual agents in observing activity. Alternative 2, Fixed, focused on fixed sensor towers with radars and cameras integrated together through a common operating picture (COP), the class of technology systems like the existing SBinet Block 1. Alternative 3, Mobile, focused on the class of technology systems like the existing Mobile Surveillance Systems (MSS) or Mobile Video Surveillance System (MVSS), which include cameras and radars and provide information from those sensors directly to the operator of the individual mobile system. Alternative 4, Aviation-Centric, focused on systems like the Unmanned Aircraft Systems (UAS), which are remotely piloted drones with sensors. The results of the Ao A also provided insight regarding possible combinations of these various options based on the relative strengths and weaknesses of each. The AoA selected four Measures of Effectiveness (MOEs). Based on the Border Patrol's assessment of relative importance, two of those counted for 85 percent of the overall effectiveness score: "Monitoring and Persistent Surveillance" and "Enable Timely and Effective Response." "Monitoring and Persistent Surveillance" measured how well a technology option BW7 FOIA CBP 000712 DHS-17-0046-C-000700 provides coverage (situational awareness) of all activities within a defined area. "Enable Timely and Persistent Surveillance" measured how well the particular technology enhanced each individual agent's ability to focus on and respond to activity within the area. The other two MOEs, which focused on the ability of various options to support other considerations (like, for example, agent safety) and the ability to adapt to migrating threats, were evaluated but only counted for a total of 15 percent of the score, based on the priorities of the Border Patrol. The results of the AoA showed that the selection of technology for a given area of the border is highly dependent on the nature of that area. There does not appear to be a "one-size-fits-all" solution-contrary to the original SBinet concept of a single, wide-ranging fixed tower-based solution across the entire border. In fact, the AoA suggested that the optimal options involved a mix of technology tailored to each area of the border and based on the operational judgment of the Border Patrol Agents in that area. TECHNOLOGY DEPLOYMENT PLAN FOR ARIZONA After completion of the formal Ao A, the Border Patrol used the results to develop a detailed technology deployment plan for each sector in Arizona based on current and anticipated operational activity. Accordingly, the new plan is fully aligned with both the quantitative analysis of science and engineering experts and the real-world operational assessment of the Border Patrol. The new border security technology plan will utilize existing, proven technology tailored to the distinct terrain and population density of each border region. This new plan will include a mixture of surveillance technologies, including commercially available MSSs, thermal imaging (b) (7)(E) devices, and tower-based Remote Surveillance Systems complemented by technologies. Where appropriate, this technology plan will also include elements of the former SBinet program that are already underway or complete and have proven successful, such as stationary radar and infrared and optical sensor towers. The Department believes that the new plan provides better coverage, more effective balance between cost and capability tailored to each area of the border, faster deployment of technology, and better linkage between operations and technology. Specifically, the Department believes that, relative to SBinet, the new technology plan is: • More operationally appropriate: The new plan is explicitly based on operational Border Patrol needs. • Lower risk: The new plan leverages the lessons learned and technology investment from SBinet and utilizes currently available technology systems that have already proven to be effective such as Remote Video Surveillance Systems (RVSS) and Mobile Surveillance Systems (MSSs). • More effective: The new plan covers gaps in technology that would not have been accommodated by SBinet. (See, for example, the RVSS case described below.) BW7 FOIA CBP 000713 DHS-17-0046-C-000701 • More timely: The new plan's use of currently available technology systems means these systems can be ordered, delivered and put to use on the front lines more quickly. • More cost-effective: The new plan will cost less, on balance, than the original SBinet plan would have. • Analytically defensible: The new plan is supported by a science-based, quantitative Analysis of Alternatives (AoA). Based on the 2010 Southwest Border Supplemental appropriation, throughout fiscal year 2011 and continuing into 2012, the Department expects to add more than 500 additional Border Patrol Agents, 30 Customs and Border Protection Officers, 160 Immigration and Customs Enforcement (b) (7)(E) Investigators, 1 Unmanned Aircraft Systems (UAS) (bringing the total in Arizona to_, and repair / replace 6 miles of physical fence. These enhancements, coupled with the new technology deployment, are expected to significantly reduce the flow of illegal and narcotic traffic in Arizona and provide full situational awareness of the Arizona border. The FY 2011 (b) (7)(E) technology investment, alone, will provide an additional of surveillance capability within Arizona. By 2014, when combined with all of the resources DHS has provided, the complete Arizona technology plan will provide situational awareness for the entire Arizona border. Situational awareness means the Border Patrol will have complete and timely knowledge of activity between the ports of entry. IMPLICATIONS OF THE NEW BORDER SECURITY TECHNOLOGY PLAN At Secretary Napolitano's direction earlier this year, DHS froze funding for SBinet beyond what is required to complete the ongoing deployments ofTUS-1 and Ajo-1 and diverted $50 million of American Recovery and Reinvestment Act funding from SBinet to other technologies. That $50 million is being used to acquire: • • • • Ten new backscatter radars for Border Patrol checkpoints (already delivered); 104 vehicle pursuit cameras for ports of entry (already delivered). Thermal imaging devices and aerial observation cameras (delivery scheduled to begin next March); and 30 Mobile Surveillance Systems (delivery scheduled to begin April 2011). Going forward, DHS will redirect funding originally intended for SBinet - including the SBinet funds in the pending FY 2011 DHS appropriations bill- beginning with the new border security technology plan in Arizona and extending across the Southwest border in the out-years. The following chart summarizes, by focus area, the differences between what SBinet originally included and the border security technology deployments under the new plan - demonstrating that the new plan will achieve both increased coverage and increased flexibility over the original SBinet plan. BW7 FOIA CBP 000714 DHS-17-0046-C-000702 Original $.atDJtlDeployment Plan for Arizona FocusArea2 Focus Areal (I'ucson, Nogak:s, a11d~ (dis/and Casa G,a,rde) 26 iafep'ated seasor towers, indadi • g 9 already i • TUS-1 23 iatea;nted sensor towers, incl • diag 6 already ia AJO-1 FocU$Area3 and Hilcox) (Dougl.as,~' FocU$Area4 (Ywna Sector) 16 iatea;nted seasor towers 26 integrated seasor towers Proposed Arizona Technology Deployment Plan FocusArea2 FocusArea3 FocusArea4 24 i• tesrated m:ed towers, i• cl • des 9 already i • TUS-1 m:ed towers, 23 iatqnted iadades 6 aJready in AJO-1 8 integrated m:ed towers 12 integrated fixed towers 6 • ewRVSS 4newRVSS 2 aewRVSS 6newRVSS 13 replacement RVSS 19 replacement RVSS FocusAreal 9 repbcemeat RVSS 15 RVSS cameras 22 tliermal ima1iin11deYices 13 tlaermal imaiiiag de,·ices 11 thermal imaging deyices IO thermal imaging de,;ces 2APSS 4APSS SAPSS lAPSS 75 imaginii sensors 65 imapq; sensors 200UGS 200UGS 2MSS 2MVSS 125UGS 20UGS 9MSS IMSS 21\fVSS 4 Figure 3: Comparison of Original SBinet Deployment to New Technology Plan Figure 3 shows that the new plan contains significantly fewer "integrated fixed tower" systems than the original SBinet plan did. Instead, it adds a significant number of lower cost systems where the performance of those systems is adequate to meet requirements. In the original SBinet plan, older RVSS systems were anticipated to become obsolete with no plan for replacement or funding to address this shortcoming. As seen in Figure 3, the new plan includes replacement RVSSs, and specifically addresses this shortcoming of the old plan. The anticipated cost to procure and deploy the new technology across Arizona is estimated at $750 million, beginning in FY 2011 and extending into FY 2014 -which represents a lower cost and faster deployment schedule than SBinet Block 1. By contrast, the most recent detailed cost estimate, from late 2008, of the required funds to procure and deploy SBinet Block 1 across Arizona projected a total cost of $800 million and completion in FY 2014. In addition, the cost estimates for SBinet Block 1 deployment across Arizona did not include needed provisions for upgrading RVSS and deploying additional MSS. In addition, the cost estimates for SBinet Block 1 deployment across Arizona did not include needed provisions for upgrading RVSS and deploying additional MSS, which would have increased the total estimate well above the $800 million. In short, the new technology deployment plan appears more cost-effective than the original SBinet plan. 4 RVSS: Remote Video Surveillance System; MSS: Mobile Surveillance System; MVSS: Mobile Video Surveillance System; APSS: Agent-Portable Surveillance System; UGS: Unattended Ground Sensor BW7 FOIA CBP 000715 DHS-17-0046-C-000703 If the President's budget request for fiscal year 2011 Border Security, Fencing, Infrastructure, and Technology (BSFIT) is fully funded at $185 million for new technology, CBP will be able to purchase all of the elements of the new technology plan except for the integrated fixed towers in 2011. The remaining budget required to complete the plan with the deployment of integrated fixed towers will be allocated from future year BSFIT budgets. (b) (7)(E) (b) (7)(E) (b) (7)(E) (b) (7)(E) The new technology plan will provide additional capability, providing more continuous and extensive surveillance of the Arizona border. As we deploy the new technology, the Department will evaluate personnel needs and begin to transition to a more mobile response capability as warranted. The Department recognizes that, as we tighten the security of one area, our adversaries will attempt to find new routes in other areas. A more mobiles and flexible response capability will allow us to move with the changes in illegal activity patterns. ACQUISITION STRATEGY AND THE CURRENT BOEING CONTRACT As discussed above, the Department has concluded that the original concept for SBinet is no longer appropriate. The SBinet system is not the right system for all areas of the border and it is not cost-effective. However, some elements of the SBinet development have provided useful capability. The experience gained with the initial SBinet Block 1 deployments to TUS-1 and AJO-1 has shown that integrated fixed towers, connected through a common operating picture, can enhance the effectiveness of our agents and support border security. Therefore, although the Department will discontinue the SBinet program as it currently exists, the Department will utilize the lessons learned during development and the elements of the system that have shown their worth and utility. Currently, SBinet is developed and deployed under a very broad and flexible contract with the Boeing Corporation. The contract was awarded in 2006 with a 3-year base period, and includes provision for a sequence of three, one-year options. The Department exercised the first option year in 2009. The second option decision was due in September 20 IO but the Department has deferred the option exercise pending the SBinet assessment results. Instead, the Department and Boeing have implemented incremental contract extensions until the assessment is complete. Besides the completion of Block 1 TUS-1 and AJO-1, the current Boeing contract includes several other activities, including operation and maintenance of the TUS-1 and AJO-1 systems, maintenance of the Mobile Surveillance Systems, completion of RVSS towers along the Northern Border, construction of fence in Arizona, and storage of steel for future fence construction and repair. The contract does not include any follow on SB/net deployments. BW7 FOIA CBP 000716 DHS-17-0046-C-000704 In short, the Boeing contract includes a number of activities that will continue, regardless of the future of SBinet. For that reason, the Department intends to exercise the option to extend the contract for another year to support these non-SBinet activities. To be clear, however, the Department does not intend to use the existing contract for procurement of any of the technology systems included in the new Southwest border technology plan. The Department intends to conduct full and open competition for all of the elements in the new plan, including the integrated fixed towers. NEXT STEPS The Department will conduct the same type of AoA along the rest of the Southwest Border over the next several months, beginning with the Border Patrol sectors in San Diego, El Paso (which includes all of New Mexico), and Rio Grande Valley. The AoA for those sectors, in conjunction with the Border Patrol operational assessment, is expected to be complete by December 2010. Following these three high-priority sectors, the Department will complete the same process for the remaining five sectors along the Southwest Border by March 2011. CONCLUSION The independent, quantitative, science-based assessment of the SBinet program has demonstrated that SBinet is not the most efficient, effective and economical way to meet our nation's border security needs. The assessment has made clear that SBinet cannot provide a single technological solution to border security, as it was originally intended to, though it has generated some significant advancements in technology that can improve our agents' ability to detect, identify, deter and respond to threats along the border. Based on the assessment and the front line agents' evaluation, Secretary Napolitano has directed CBP to end SBinet and instead utilize existing, proven technology solutions tailored to the distinct terrain and population density of each border regions. Secretary Napolitano's decision recognizes that we must effectively deploy a wide range of proven technology along the Southwest border - rather than a single, experimental technology program - to meet our nation's pressing border technology needs and complement this Administration's unprecedented investment in manpower, infrastructure and resources to secure the Southwest border. The plan is consistent with the President's fiscal year 2011 budget request and with the Department's longer term budget plan. BW7 FOIA CBP 000717 DHS-17-0046-C-000705 ILS Support Projects on the Southwest Border Findings and Options 1/25/2011 BW7 FOIA CBP 000718 DHS-17-0046-C-000706 1 Table of Contents • (b) (7)(E) Program Support Facility (PSF) – Background – Findings – Recommendations • (b) (7)(E) Program Support Facility (PSF) – Background – Findings – Recommendations • (b) (7)(E) Training Facility – Background – Findings – Recommendations BW7 FOIA CBP 000719 DHS-17-0046-C-000707 (b) (7)(E) Program Support Facility (PSF) Findings and Recommendations BW7 FOIA CBP 000720 DHS-17-0046-C-000708 3 Background (b) (7)(E) Program Support Facility (PSF) • Boeings current lease at the (b) (7)(E) Arizona Program Support Facility (PSF) will expire on June 30, 2011. Due to expected deployment in the (b) (7)(E) AOR, a determination was made that the facility will be needed in the foreseeable future. • Director, Integrated Logistics Staff requested (b) (6) , Real estate Manager to meet with the current PSF Owner to determine the feasibility of continued leasing. • Conducted a fast track market survey to determine real time leasing cost of comparable facilities. BW7 FOIA CBP 000721 DHS-17-0046-C-000709 Findings • Held a meeting with owner of the current Boeing leased facility. – Owner is willing to rent to the Federal government and work around Federal leasing issues such as being prohibited to pay insurance, taxes and indemnification. – Lease cost is negotiable (starting point (b) (4) /sf/yr). – Long term lease may reduce annual costs. – Current facility can be expanded to house additional program staff. BW7 FOIA CBP 000722 5 DHS-17-0046-C-000710 Findings Cont. • Visited 6 additional facilities to determine if comparable to the PSF. – Only 4 are comparable to the current PSF facility – All 4 have more square feet than required • 56,700 sf - (b) (4) /sf/yr 1 , 2 • 59,500 sf - (b) (4) /sf/yr 1, 2 • 80,000 sf - (b) (4) /sf/yr 1, 2 • 39,062 SF - 191,950 SF - (b) (4) /sf/yr (new construction in 2011) 1 1 Lease cost does not include additional rent for items (insurance, real estate taxes, etc.) which the government is prohibited to pay and is usually negotiated and added to total annual rent cost. 2 Lessor not willing to sub-divide. BW7 FOIA CBP 000723 6 DHS-17-0046-C-000711 Options • Include relocating the Southwest Field Office (SWFO) to the PSF in the program of requirements. This will reduce lease payments in the (b) (7)(E) area by $172,000 (SWFO current annual lease cost). • Relocate contractors currently housed in the PSF to current temporary buildings on site. • Provide an urgent and compelling justification and negotiate with the current PSF building Owner to lease the facility. BW7 FOIA CBP 000724 DHS-17-0046-C-000712 (b) (7)(E) Program Support Facility (PSF) Findings and Recommendations BW7 FOIA CBP 000725 DHS-17-0046-C-000713 8 Background (b) (7)(E) Program Support Facility (PSF) (b) (7)(E) • The current office and bench space is adequate to support Field Technology Officers (FTO)s. With the deployment of (b) (7)(E) and the necessity to increase the manpower at this site, there will not be enough office and shop space to effectively support legacy and SBI related technologies. I (b) (7)(E) • This facility would require at least individual office spaces with enough electronic bench space, vehicle garage bays, and warehouse storage to support not only the personnel enhancements but legacy and SBInet technologies. • Director, Integrated Logistics requested (b) (6) , Real Estate Manager to look into the feasibility of leasing a facility in AJO, Arizona. BW7 FOIA CBP 000726 DHS-17-0046-C-000714 Findings • Visited (b) (7)(E) (b) (7)(E) s facility/staging area for • The facility address is towers. (b)(6);(b)(7)(C) ., Ajo, AZ 85321 (b) (7)(E) • Facility/staging area consisted of a metal structure (approx. ) with a small office space on approximately acre of fenced land. I (b) (7)(E) • The structure does not have air conditioning and the restroom facility is problematic. • (b) (7)(E) also used temporary buildings to support the operation as well as portable restrooms. BW7 FOIA CBP 000727 DHS-17-0046-C-000715 Options • Lease this facility and rent temporary structures to meet program requirements. • Offer to lease this site, demolish the structure and construct new facility. • Offer to purchase facility, demolish the structure and construct new facility. BW7 FOIA CBP 000728 DHS-17-0046-C-000716 (b) (7)(E) Training Facility Lease Feasibility Findings and Recommendations BW7 FOIA CBP 000729 DHS-17-0046-C-000717 12 Background (b) (7)(E) • Boeings current lease at the (b) (7)(E) Training Facility ( will expire on March 31, 2011. In addition, the Agency’s contractual agreement with Boeing will also expire in 2011. Based on the lease expiration and projected contract expiration, (b) (7)(E) a determination was made that the is necessary to continue SBI mission objectives and activities in the foreseeable future. • Director, Integrated Logistics requested (b) (6) , Real Estate Manager to meet with the current New Mexico Tech Program Manager to determine the feasibility of continued leasing. BW7 FOIA CBP 000730 DHS-17-0046-C-000718 Findings BW7 FOIA CBP 000731 DHS-17-OO46-C-000719 Findings Cont. • Boeing lease costs before and after scaling back operations. Facility Description Classroom (COP) Server Room Cost prior to scaling back operations Cost after scaling back operations (b)(3) (b)(3) Square Footages (b) (7)(E) Supply Room Tower Site (b) (7)(E) Tower Site Tower Site Computer Room Classroom (Office 3) High Speed Internet General PTRC Use Sub Total Program Pricing Efficiency (33%) (b)(3) Management Allowance (10%) TOTAL 15 BW7 FOIA CBP 000732 DHS-17-0046-C-000720 (b) (7)(E) Training and Research Center (b) (7)(E) (b) (7)(E) BW7 FOIA CBP 000733 DHS-17-0046-C-000721 Planned (b) (7)(E) Training Center Floor plan (b) (7)(E) BW7 FOIA CBP 000734 DHS-17-0046-C-000722 Options • Develop requirements to effect a test/in-service engineering capability. • Select a couple of additional candidate sites as alternatives and present to SBI senior management. • Continue meeting with (b) (7)(E) key officials to fine tune long term lease cost. • Explore the feasibility of leasing the planned new (b) (7)(E) Training Center. BW7 FOIA CBP 000735 DHS-17-0046-C-000723 For Official Use Only Status Update SBInet Decisions and Arizona Border Surveillance Technology Plan September 20, 2010 U.S. Customs and Border Protection For Official Use Only BW7 FOIA CBP 000736 DHS-17-0046-C-000724 For Official Use Only Discussion Outline • Summary of “get backs” from July 22, 2010 briefing • Recommendations and decisions • Messages • Arizona laydown: status and schedule forward • Process: next steps • Review of Boeing contract BW7 FOIA CBP 000737 DHS-17-0046-C-000725 2 Summary of “Get Backs” For Official Use Only (From briefing, July 22, 2010) • Ensure future Analysis of Alternatives (AoA) efforts “open the aperture” • Ensure maximum use of competition for future efforts • Develop and apply a peer review process for future AoA efforts • Provide a more detailed basis of estimate for operations and maintenance cost estimates • Provide a time-phased deployment plan, linked to budgets • Change the SBInet name and begin working the messaging BW7 FOIA CBP 000738 DHS-17-0046-C-000726 3 For Official Use Only Summary of Recommendations and Decisions (From briefing, July 22, 2010) • Apply the Analysis of Alternatives (AoA) methodology across the rest of the border • Optimize technology deployment based on operator judgments, the AoA, results of current (b) (7)(E) testing, and budget decisions • Communicate and explicitly acknowledge changes to the SBInet program • Continue deployment and testing of (b) (7)(E) (b) (7)(E) in (b) (7)(E) and (b) (7)(E) • Adopt the proposed Arizona technology deployment plan as the basis for near-term decisions BW7 FOIA CBP 000739 DHS-17-0046-C-000727 4 For Official Use Only Messaging—Key Themes • DHS will end the SBInet program and its strategy to cover the entire border with a complex, interconnected “virtual fence” • DHS will leverage the elements of SBInet technology that have been effective, but in more limited and tailored fashion and through use of competitive acquisition approaches • The Secretary’s assessment has shown that tailored mixes of technology, tightly linked to Border Patrol operational needs, is more cost-effective than a large “virtual fence” • DHS has applied the assessment results to develop a new, more cost-effective technology plan for Arizona • DHS will extend its analysis to the entire border BW7 FOIA CBP 000740 DHS-17-0046-C-000728 5 For Official Use Only Arizona Laydown • Complete (b) (7)(E) and(b) (7)(E) • Initiate acquisition for the new, tailored set of technologies immediately – Sequence based on Border Patrol prioritization BW7 FOIA CBP 000741 DHS-17-0046-C-000729 6 For Official Use Only Projected Schedule Acquisition for new Arizona plan •FY11 •OctDec •Technology (b) (7)(E) - Target RFP Release - Estimated Contract Award - Estimated Delivery/Deployment Period •JanMar •AprJun •JulSep •FY12 •OctDec •JanMar •AprJun •JulSep •FY13 •OctDec •JanMar •AprJun •JulSep (b) (5) (b) (7)(E) BW7 FOIA CBP 000742 DHS-17-0046-C-000730 7 For Official Use Only Funding by Fiscal Year FY $ Technology FY09 (ARRA) (b) (7)(E) FY 11 $185M FY 12 $160M FY13 $165M $160M * $405M $64M $64.2M $24.5M $14.6M $6.3M $6M $5M $0.4M $3.3M $21.2M ($240M) •Shown for completeness—CBP will seek efficiencies through competition to reduce the shortfall as well as defer costs to FY14 BW7 FOIA CBP 000743 DHS-17-0046-C-000731 8 For Official Use Only Process—Next Steps • Announce the new plan – Briefing paper, questions and answers, and outreach schedule are prepared • Extend Analysis of Alternatives to (1) highest priority sectors ((b) (7)(E) (b) (7)(E) and then (2) the remainder of the Southwest Border BW7 FOIA CBP 000744 DHS-17-0046-C-000732 9 For Official Use Only Boeing Contract • Scheduled to expire last Friday • Planned one-year option – Enables completion of (b) (7)(E) and (b) (7)(E) plus (b) (7)(E) continuation of non-SBInet work (like maintenance) – Does NOT require award of ANY new SBInet work to Boeing • Deferred option for one month (via temporary one-month extension) – Avoid confusing / premature messaging – Propose to execute the option AFTER announcement and roll-out of the new plan BW7 FOIA CBP 000745 DHS-17-0046-C-000733 10 U.S. Department ofHomeJand Security Washington, DC 20229 U.S.Customs and Border Protection September 27, Commissioner 2010 MEMORANDUMFOR: /J · Janet Napolitano Secretary : J l,M1i\ /J14r FROM: Alan Bersin • Commissiof r f l? - Alternativesfor Securing the Border SUBJECT: r Following our discussions on September20, 2010 about SBinet and our proposed new plan for Arizona border security technology deployment,you asked for a revised decision memorandum on those topics. The purpose of this memorandumis to respond to your request and to request approval for the new plan. As background,we briefed you on the proposed new plan on July 22, 2010. The plan is advised by a formal Analysis of Alternatives (AoA), which is the "quantitative, science-based assessment" you directed last January. In developingthe new plan, we integratedthe results of the AoA with the Border Patrol's operationalassessment. (b) (7)(E) (b) (7)(E) Thus, the assessment you ordered in January made clear that SBinet does not provide a single technological solution to border security, as it was originally intended.~For example, in (b) (7)(E) ut at a fraction of the cost ofSBinet's integrated (b) (7)(E) Accordingly,the new border security technolo will utilize existing, (b) (7)(E) proven technology tailored to each border region-a significant departure from the original SBinet concept of a single, wide-ranging fixed towerbased solution across the entire border. This new plan will include a mixture of (b) (7)(E) (b) (7)(E) BW7 FOIA CBP 000746 DHS-17-0046-C-000734 Alternatives for Securing the Border Page2 appropriate,this technologyplan will also include elementsof the former SBinet program that are already underway or complete and have proven successful,such as (b) (7)(E) and (b) (7)(E) . r We believe, based in large part on consultationwith the experts at the Department's Science and TechnologyDirectorate and frontlineofficers and agents on the border, that the new plan provides better coverage, more effectivebalance between cost and capabilitytailored to each area of the border, faster deploymentof technology,and better linkagebetween operations and technology. At your direction earlier this year, we froze funding for SBinet beyond what is required to complete the ongoing deploymentsof and we diverted $50 million of (b) (7)(E) Recovery Act funding from SBinet to other technologies. That $50 million is being used to acquire: (b) (7)(E) for Border Patrol checkpoints(alreadydelivered); • (b) (7)(E) to our ports of entry (alreadydelivered). • (b) (7)(E) (to be deliveredby early October) • (b) (7)(E) (delivery scheduledto begin • next March); and (b) (7)(E) (delivery scheduledto begin April 2011). • At least Going forward, we intend to redirect funding originallyintended for SBinet - includingthe SBinet funds in the p_endingFY 2011 OHS appropriationsbill- to the,new border security technologyplan for Arizona, and eventuallythe remainderof the border. The followingchart summarizes,by focus area, the differencesbetween what SBinet originally included and the proposed border security technologydeploymentsunder the new plan - demonstratingthat the new plan will achieve both increasedcoverage and increasedflexibilityover the original SBinet plan. Original SB/net Plan: (b) (7)(E) (b) (7)(E) Proposed Arizona Technology Deployment Plan: Focus Area 1 Focus Area 2 FocusArea3 FocusArea4 (b) (5) BW7 FOIA CBP 000747 DHS-17-0046-C-000735 Alternatives for Securing the Border Page3 (b) (5) (b) (7)(E) (b) (7)(E) We estimate that the cost to procure and deploy the new teclmology across Arizona would be (5) beginning in FY 2011 and extending into FY 2014- which represents a lower cost and faster deployment schedule than SBinet Block 1. The most recent detailed cost estimate, from late 2008, of the required funds to procure and deploy SBinet Block 1 across Arizona (b) (5) projected a total cost and completion in FY 2013 - and the more recent delays and cost overruns would have pushed the completion date into FY 2014 and further increased the final cost. In addition, the cost estimates for SBinet did not include needed provisions for (b) (7)(E) upgradin~ (b) (7)(E) and deploying additiona~. In short, the new teclmology deployment plan appears very cost-effective when compared to the original SBinet plan. (b) (5) (b) Based on the results of our analysis, we propose the following recommendations: • • • • (b) (5) 1 This figure includes"sunk costs," so the go-forwardcosts should have been less. However,this is likely offset by the impact of cost overruns. BW7 FOIA CBP 000748 DHS-17-0046-C-000736 Alternatives for Securing the Border Page4 We request your approval to proceed with the new technology deployment plan for Arizona and to extend our AoA planning to the remainder of the Southwest border. ApprovrldateJJ/1,k=Disapproved/date ________ Modify/date _________ _ _ Needs discussion/date ------- Attachment . . ~ ~ BW7 FOIA CBP 000749 DHS-17-0046-C-000737