USUN Ambassador Nikki Haley Says United States Taking Names. Again. #UNGA #Thursday

Posted: 3:40 am ET

 

Back in January, Ambassador Nikki Haley made her first appearance before the press as USUN ambassador prior to presenting her credentials. She made a huge splash with her opening salvo:  “For those who don’t have our back, we’re taking names – we will make points to respond to that accordingly.” (see @USUN Ambassador Nikki Haley: Taking Names and Diplomatic Dustup).

Now, she’s taking names again of those who will criticize the impending US embassy move.  The UN General Assembly is set to meet on Thursday for an emergency discussion on the U.S. recognition of Jerusalem as Israel’s capital. Haaretz is reporting that in an attempt to avoid embarrassment, “Israel has instructed its diplomatic missions to seek meetings with high-level officials to persuade them to direct their representatives at the UN to oppose, not to support, or at the very least not to deliver a speech at the General Assembly.”

#

Advertisements

#Jerusalem Recognition: Protests and Limited Public Services #USEmbassies

Posted: 12:21 pm PT

 

#

@StateDept Spox Talks “No Double Standard Policy” and 7 FAM 052 Loudly Weeps

Posted: 2:58 am ET

 

So we asked about the State Department’s “no double stand policy” on December 5 after media reports say that classified cables went out  in the past 2 weeks warning US embassies worldwide to heighten security ahead of a possible @POTUS announcement recognizing Jerusalem as the capital of Israel.

On December 7, the State Department press corps pressed the official spokesperson about a cable that reportedly asked agency officials to defer all nonessential travel to Israel, the West Bank, and Jerusalem. Note that the security messages issued by multiple posts on December 5 and 6 with few exceptions were personal security reminders, and warnings of potential protests.  The Worldwide Caution issued on December 6 is an update “with information on the continuing threat of terrorist actions, political violence, and criminal activity against U.S. citizens and interests abroad.

None of the messages released include information that USG officials were warned to defer non-essential travel to the immediate affected areas. When pressed about this apparent double standard, the official spox insisted that “unfortunately, just as State Department policy, we don’t comment on official – whether or not there was an official communication regarding — regarding this.”

Noooooooooooooooooo!

The spox then explained  what the “no double standard” policy means while refusing to comment on official communication that potentially violates such policy. And if all else fails, try “hard to imagine that our lawyers have not gone through things.”  

Holy moly guacamole, read this: 7 FAM 052  NO DOUBLE STANDARD POLICY

In administering the Consular Information Program, the Department of State applies a “no double standard” policy to important security threat information, including criminal information.

Generally, if the Department shares information with the official U.S. community, it should also make the same or similar information available to the non-official U.S. community if the underlying threat applies to both official and non-official U.S. citizens/nationals.

If a post issues information to its employees about potentially dangerous situations, it should evaluate whether the potential danger could also affect private U.S. citizens/nationals living in or traveling through the affected area.

The Department’s “No Double Standard” policy, provided in 7 FAM 052, is an integral part of CA/OCS’s approach to determine whether to send a Message.  The double standard we guard against is in sharing threat-related information with the official U.S. community — beyond those whose job involves investigating and evaluating threats — but not disseminating it to the U.S. citizen general public when that information does or could apply to them as well.

Also this via 7 FAM 051.2(b) Authorities (also see also 22 CFR 71.1, 22 U.S.C. 2671 (b)(2)(A), 22 U.S.C. 4802, and 22 U.S.C. 211a):

…The decision to issue a Travel Alert, Travel Warning, or a Security or Emergency Message for U.S. Citizens for an individual country is based on the overall assessment of the safety/security situation there.  By necessity, this analysis must be undertaken without regard to bilateral political or economic considerations.  Accordingly, posts must not allow extraneous concerns to color the decision of whether to issue information regarding safety or security conditions in a country, or how that information is to be presented.

As to the origin of this policy, we would need to revisit the Lockerbie Bombing and Its Aftermath (this one via ADST’s Oral History).

The State Department’s official spokesperson via the Daily Press Briefing, December 7, 2017:

QUESTION: So a cable went out to all U.S. diplomatic and consular missions yesterday that asked State Department officials to defer all nonessential travel to the entirety of Israel, the West Bank, and Jerusalem. Normally when you are discouraging American officials from going to a particular area, under the no double standard rule, you make that public to all U.S. citizens so that they have the same information. I read through the Travel Warnings on Israel, the West Bank, and Gaza yesterday, both in the middle of the day and then at the end of the day after the worldwide caution, and I saw no similar warning to U.S. citizens or advice to U.S. citizens to defer nonessential travel to those areas. Why did you say one thing in private to U.S. officials and another thing – and not say the same thing in public to U.S. citizens?

MS NAUERT: Let me state the kinds of communication that we have put out to American citizens and also to U.S. Government officials. And one of the things we often say here is that the safety and security of Americans is our top priority. There are top policy priorities, but that is our overarching, most important thing, the safety and security of Americans.

We put out a security message to U.S. citizens on the 5th of December – on Monday, I believe it was. We put out a security message to our U.S. citizens that day – that was Tuesday? Okay, thank you – on the 5th of December. We put out another one on the 6th of December as well, expressing our concerns. We want to alert people to any possible security situations out of an abundance of caution. That information was put, as I understand it, on the State Department website, but it was also issued by many of our posts overseas in areas where we thought there could be something that could come up.

In addition to that, there is a Travel Warning that goes out regarding this region. That is something that is updated every six months, I believe it is. This Travel Warning for the region has been in effect for several, several years, so that is nothing new. In addition to that, we put out a worldwide caution. That is updated every six months. We had a worldwide caution in place for several years, but yesterday, out of an abundance of caution, we updated it. As far as I’m aware of, and I won’t comment on any of our internal communications to say whether or not there were any of these internal communications because we just don’t do that on any matter, but I think that we’ve been very clear with Americans, whether they work for – work for the U.S. Government or whether they’re citizens traveling somewhere, about their safety and security. This is also a great reminder for any Americans traveling anywhere around the world to sign up for the State Department’s STEP program, which enables us to contact American citizens wherever they are traveling in the case of an emergency if we need to communicate with them.

QUESTION: But why did you tell your officials not to travel to those areas between December 4th and December 20th, and not tell American citizens the same things? Because you didn’t tell that to American citizens in all of the messages that you put up on the embassy website, on the consulate website, nor did you tell American citizens that in a Worldwide Caution, nor did you tell them that in the link to Israel, the West Bank, and Gaza that was put out by the State Department in the Worldwide Caution yesterday. You’re telling your people inside one thing, and you’re telling American citizens a different thing, and under your own rules, you are – there is supposed to be no double standard. Why didn’t you tell U.S. citizens the same thing you told the U.S. officials?

MS NAUERT: Again, unfortunately, just as State Department policy, we don’t comment on official – whether or not there was an official communication regarding —

Image via Wikimedia Commons by Saibo

QUESTION: (Off-mike.)

MS NAUERT: – regarding this. But I can tell you as a general matter, I think we have been very clear about the security concerns regarding Americans. We have put out those three various subjects or types of communications to American citizens who are traveling in areas that could be affected.

QUESTION: I’m going to ask you –

MS NAUERT: In terms of the U.S. Government, when we talk about the U.S. Government deferring non-essential travel, I would hope that people would not travel for non-essential reasons just as a general matter anyway.

QUESTION: But why – I’m going to ask you a hypothetical, which I would ask you to entertain, if you’ll listen to it.

MS NAUERT: I’ll listen to it. I’d be happy to listen to it.

QUESTION: If there were such communication, and you know and every U.S. diplomat who gets an ALDAC, which means every other person who works at the State Department knows that this communication went out – so if there were such communication, why would you say one thing to your own officials and a different thing to American citizens —

MS NAUERT: As our —

QUESTION: – which is what the law and your own rules require?

MS NAUERT: As you well know, we have a no “double standard.” And for folks who aren’t familiar with what that means, it’s when we tell our staff something about a particular area or a security threat, we also share that same information with the American public. I would find it hard to imagine that our lawyers have not gone through things to try to make sure that we are all on the same page with the information that we provide to U.S. Government officials as well as American citizens. And that’s all I have for you on that. Okay? Let’s move on to something else.

#

Trump Admin Gets Multiple Warnings That Jerusalem Recognition Could Trigger Dangerous Consequences

Posted: 3:04 am ET

 

#


USG Seeks Jerusalem Hotel Room Services For Estimated 2,704 Room Nights For a Year

Posted: 3:06 am ET
[twitter-follow screen_name=’Diplopundit’]

 

On July 20, the US Embassy in Tel Aviv issued a solicitation for Jerusalem Hotel Room Services.

The Embassy intends to conduct a pre-proposal conference, and all prospective offerors are invited to attend. The pre-proposal conference will take place at 10:00 AM local Israel time, on August 1, 2017, at the US Embassy Annex Facility located at 11 Galgalai Haplada St., Entrance B, 3rd floor, Herzelia Pituach, Israel.

The requirement is for the providing of lodging rooms for Official US Government visits to the City of Jerusalem.  The estimated number of hotel rooms for one year is 1,202 rooms and 2,704 room nights.  The anticipated performance is for a base period of twelve months and two one -year periods at the option of the Government.

The scope of services requires the contractor to provide a minimum of 40 (forty) and a maximum of 6,500 (six thousand five hudred) single hotel rooms in Jerusalem. According to FedBiz, the contract type will be indefinite quantity.

#

#

State Dept Seeks Drug/Steroid Testing of Security Personnel in Afghanistan and Jerusalem

The State Department is looking for a contractor to provide drug and steroid screening of all Diplomatic Security employees in Afghanistan and Jerusalem. The announcement was posted on FedBiz on Apr 29, 2013  per Solicitation Number: RFI(04292013):

Via FedBiz

The Department of State (DoS) Office of Diplomatic Security (DS) is concerned with the well-being of its employees, the successful accomplishment of agency missions, and the need to maintain employee productivity. Many of the DS-hired U.S. Citizen (USC) and Third Country National (TCN) direct hire and/or contract positions in Afghanistan and Jerusalem involve the use of weapons and access to highly sensitive information that must not be compromised. It is critically important that such armed employees, or those employees exposed to extreme conditions, be reliable, stable, and show good use of judgment. Illegal drug and steroid use creates the possibility of coercion, influence, and irresponsible action under pressure, all of which may pose a serious risk to national defense, public safety, and security. Prior to deployment, all employees certify that drug testing and steroid screening is a nonnegotiable condition of employment.

This performance work statement defines the drug and steroid testing requirements (hereinafter referred to as “Substance Screening”) applicable to DS-hired USC and TCN direct hires and/or contract positions in Afghanistan and Jerusalem. In this document, DS will be referred to as the DS who will receive support from the Contractor. Employee will be the all-encompassing term for DS direct hires, personal services contractors, or third party contractors.

Below is part of the Scope of Work posted with the solicitation:

The Contractor shall be licensed to operate through the Government of the Islamic Republic of Afghanistan (GIRoA) and Government of Israel, and shall be in full compliance with host country business requirements. The Contractor will be self-sufficient and required to provide all life support, travel and security needs for staff. In addition, the Contractor shall support all shipping, maintenance, and housing of equipment necessary to perform services. The Contractor will provide all resources to perform random and non-random Substance Screening, preferably at the following locations, with the corresponding number of estimated employees:

• Kabul: 1300
• Mazar e-Sharif: 150
• Herat: 175
• Jerusalem: 55

Random screening will be on a semiannual basis (every six months) as well as non-random substance testing. All random and non-random substance testing performed shall comply with Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy and Security Rules (http://www.hhs.gov/ocr/privacy/hipaa/understanding/summary/i

[…]

The Contractor shall be prepared to test for the following drugs utilizing a rapid urine test in Afghanistan and/or Israel, except for Steroid:

  • Amphetamine
  • Opiate
  • Benzodiazepine
  • Barbituates
  • Cocaine
  • Marijuana
  • Steroid: Refer to the following commonly abused steroids on the National Institute on Drug Abuse’s (NISA) website or at Steroidabuse.gov.

Security contractors in Afghanistan, particularly those in Kabul  have a um… colorful history (see POGO writes to Secretary Clinton about US Embassy Kabul Guards) so it’s only surprising that it took this long.  But it is  curious about Jerusalem though, isn’t it? Anyone knows what prompted this?

Update:  We understand from a blog pal that this may not be anything new as apparently drug screening is routinely done for “high threat protection” contractors.  Jerusalem has protection contractors that predates both Iraq and Afghanistan as it covers all official travel to Gaza and the West Bank.  But according to a Q&A posted online on FedBiz, these drug tests have not been performed in Israel in the past.

 

— DS