Advertisement
Ask Kulongoski to Stop the Nuking of Portland
Call on Gov Ted Kulongoski to cancel Operation Noble Resolve
Call on Gov Ted Kulongoski to cancel Operation Noble Resolve at least until some major issues are cleared up over the Presidential Directive 51 and the habit of some strategic games becoming simultaneous real events is fully investigated.
Congressman Peter DeFazio has been blocked in his investigations on the issues surrounding the planned event and its relationship to National Security Presidential Directive 51 which would give Bush dictatorial powers if such a real event like a nuclear attack on Portland did happen. Governor Kulongoski could address this issue and demand that state employees not comply or work with FEMA and other organizations planning Operation Noble Resolve until major issues and questions are satisfactorily answered. On July 20th of 2007 after refusal to have access to documents related to Presidential Directive 5, DeFazio "Maybe the people who think there's a conspiracy out there are right." The fear is that like the Tube Bombing in London on 7/7 2005 and the 9/11 tragedy there were simultaneous mock events that were similar to the actual events taking place.
contacting Oregon Governor Kulongoski:
Please use one of the following methods if you would like to share an opinion or if the Governor´s Office can be of assistance:
MAIL Governor Kulongoski 160 State Capitol 900 Court Street Salem, Oregon 97301-4047
PHONE Governor’s Citizens’ Representative Message Line 503.378.4582
FAX 503.378.6827
POSSIBLE STATE ALTERNATIVES TO OPERATION NOBLE RESOLVE
Governor Ted Kulongoski and Governor Christine Gregoire could propose alternatives to Operation Noble Resolve. One alternative could be to have strategic simulations on counter-dictatorial usuption of our federal system. This could be done by having mass teach-ins on administrative noncooperation, civil disobedience and other nonviolent actions as well as civics with mock events simulating a coups d'état in our federal system. In 1983, Dr. Gene Sharp had proposed that creating a civillian based defense using nonviolent tactics would be far more effective against invading and anti democratic forces as well as much more economically sustainable.
www.fragmentsweb.org/fourtx/...lec.html
The two sister states of Oregon and Washington could host a training and implimentation of a civillian based defense in complete cooperation with the Oregon and Washington State National Guards. We could give such a civics training and mock events even a name like Operation Evergreen. This could be done with the cooperation of the various states’ educational systems, liberaries and other organizations both governmental and non-governmental.
Gene Sharp, Civilian-Based Defense: A Post-Military Weapons System (Princeton, New Jersey: Princeton University Press, 1990).
Gene Sharp Lecture on Civilian-Based Defense (audio of the 1983 lecture on creating a nonviolent civillian system to counter tryanny) www.fragmentsweb.org/fourtx/...lec.html
NSPD 51 FROM WHITEHOUSE WEBSITE (for those not familiar with the Presidential Directive)
White House News
NATIONAL SECURITY PRESIDENTIAL DIRECTIVE/NSPD 51
HOMELAND SECURITY PRESIDENTIAL DIRECTIVE/HSPD-20
Subject: National Continuity Policy
Purpose
(1) This directive establishes a comprehensive national policy on the continuity of Federal Government structures and operations and a single National Continuity Coordinator responsible for coordinating the development and implementation of Federal continuity policies. This policy establishes "National Essential Functions," prescribes continuity requirements for all executive departments and agencies, and provides guidance for State, local, territorial, and tribal governments, and private sector organizations in order to ensure a comprehensive and integrated national continuity program that will enhance the credibility of our national security posture and enable a more rapid and effective response to and recovery from a national emergency.
Definitions
(2) In this directive:
(a) "Category" refers to the categories of executive departments and agencies listed in Annex A to this directive;
(b) "Catastrophic Emergency" means any incident, regardless of location, that results in extraordinary levels of mass casualties, damage, or disruption severely affecting the U.S. population, infrastructure, environment, economy, or government functions;
(c) "Continuity of Government," or "COG," means a coordinated effort within the Federal Government's executive branch to ensure that National Essential Functions continue to be performed during a Catastrophic Emergency;
(d) "Continuity of Operations," or "COOP," means an effort within individual executive departments and agencies to ensure that Primary Mission-Essential Functions continue to be performed during a wide range of emergencies, including localized acts of nature, accidents, and technological or attack-related emergencies;
(e) "Enduring Constitutional Government," or "ECG," means a cooperative effort among the executive, legislative, and judicial branches of the Federal Government, coordinated by the President, as a matter of comity with respect to the legislative and judicial branches and with proper respect for the constitutional separation of powers among the branches, to preserve the constitutional framework under which the Nation is governed and the capability of all three branches of government to execute constitutional responsibilities and provide for orderly succession, appropriate transition of leadership, and interoperability and support of the National Essential Functions during a catastrophic emergency;
(f) "Executive Departments and Agencies" means the executive departments enumerated in 5 U.S.C. 101, independent establishments as defined by 5 U.S.C. 104(1), Government corporations as defined by 5 U.S.C. 103(1), and the United States Postal Service;
(g) "Government Functions" means the collective functions of the heads of executive departments and agencies as defined by statute, regulation, presidential direction, or other legal authority, and the functions of the legislative and judicial branches;
(h) "National Essential Functions," or "NEFs," means that subset of Government Functions that are necessary to lead and sustain the Nation during a catastrophic emergency and that, therefore, must be supported through COOP and COG capabilities; and
(i) "Primary Mission Essential Functions," or "PMEFs," means those Government Functions that must be performed in order to support or implement the performance of NEFs before, during, and in the aftermath of an emergency.
Policy
(3) It is the policy of the United States to maintain a comprehensive and effective continuity capability composed of Continuity of Operations and Continuity of Government programs in order to ensure the preservation of our form of government under the Constitution and the continuing performance of National Essential Functions under all conditions.
Implementation Actions
(4) Continuity requirements shall be incorporated into daily operations of all executive departments and agencies. As a result of the asymmetric threat environment, adequate warning of potential emergencies that could pose a significant risk to the homeland might not be available, and therefore all continuity planning shall be based on the assumption that no such warning will be received. Emphasis will be placed upon geographic dispersion of leadership, staff, and infrastructure in order to increase survivability and maintain uninterrupted Government Functions. Risk management principles shall be applied to ensure that appropriate operational readiness decisions are based on the probability of an attack or other incident and its consequences.
(5) The following NEFs are the foundation for all continuity programs and capabilities and represent the overarching responsibilities of the Federal Government to lead and sustain the Nation during a crisis, and therefore sustaining the following NEFs shall be the primary focus of
the Federal Government leadership during and in the aftermath of an emergency that adversely affects the performance of Government Functions:
(a) Ensuring the continued functioning of our form of government under the Constitution, including the functioning of the three separate branches of government;
(b) Providing leadership visible to the Nation and the world and maintaining the trust and confidence of the American people;
(c) Defending the Constitution of the United States against all enemies, foreign and domestic, and preventing or interdicting attacks against the United States or its people, property, or interests;
(d) Maintaining and fostering effective relationships with foreign nations;
(e) Protecting against threats to the homeland and bringing to justice perpetrators of crimes or attacks against the United States or its people, property, or interests;
(f) Providing rapid and effective response to and recovery from the domestic consequences of an attack or other incident;
(g) Protecting and stabilizing the Nation's economy and ensuring public confidence in its financial systems; and
(h) Providing for critical Federal Government services that address the national health, safety, and welfare needs of the United States.
(6) The President shall lead the activities of the Federal Government for ensuring constitutional government. In order to advise and assist the President in that function, the Assistant to the President for Homeland Security and Counterterrorism (APHS/CT) is hereby designated as the National Continuity Coordinator. The National Continuity Coordinator, in coordination with the Assistant to the President for National
Security Affairs (APNSA), without exercising directive authority, shall coordinate the development and implementation of continuity policy for executive departments and agencies. The Continuity Policy Coordination Committee (CPCC), chaired by a Senior Director from the Homeland Security Council staff, designated by the National Continuity Coordinator, shall be the main day-to-day forum for such policy coordination.
(7) For continuity purposes, each executive department and agency is assigned to a category in accordance with the nature and characteristics of its national security roles and
responsibilities in support of the Federal Government's ability to sustain the NEFs. The Secretary of Homeland Security shall serve as the President's lead agent for coordinating overall
continuity operations and activities of executive departments and agencies, and in such role shall perform the responsibilities set forth for the Secretary in sections 10 and 16 of this directive.
(8) The National Continuity Coordinator, in consultation with the heads of appropriate executive departments and agencies, will lead the development of a National Continuity Implementation Plan (Plan), which shall include prioritized goals and objectives, a concept of operations, performance metrics by which to measure continuity readiness, procedures for continuity and incident management activities, and clear direction to executive department and agency continuity coordinators, as well as guidance to promote interoperability of Federal Government continuity programs and procedures with State, local, territorial, and tribal governments, and private sector owners and operators of critical infrastructure, as appropriate. The Plan shall be submitted to the President for approval not later than 90 days after the date of this directive.
(9) Recognizing that each branch of the Federal Government is responsible for its own continuity programs, an official designated by the Chief of Staff to the President shall ensure that the executive branch's COOP and COG policies in support of ECG efforts are appropriately coordinated with those of
the legislative and judicial branches in order to ensure interoperability and allocate national assets efficiently to maintain a functioning Federal Government.
(10) Federal Government COOP, COG, and ECG plans and operations shall be appropriately integrated with the emergency plans and capabilities of State, local, territorial, and tribal governments, and private sector owners and operators of critical infrastructure, as appropriate, in order to promote interoperability and to prevent redundancies and conflicting lines of authority. The Secretary of Homeland Security shall coordinate the integration of Federal continuity plans and operations with State, local, territorial, and tribal governments, and private sector owners and operators of critical infrastructure, as appropriate, in order to provide for the delivery of essential services during an emergency.
(11) Continuity requirements for the Executive Office of the President (EOP) and executive departments and agencies shall include the following:
(a) The continuation of the performance of PMEFs during any emergency must be for a period up to 30 days or until normal operations can be resumed, and the capability to be fully operational at alternate sites as soon as possible after the occurrence of an emergency, but not later than 12 hours after COOP activation;
(b) Succession orders and pre-planned devolution of authorities that ensure the emergency delegation of authority must be planned and documented in advance in accordance with applicable law;
(c) Vital resources, facilities, and records must be safeguarded, and official access to them must be provided;
(d) Provision must be made for the acquisition of the resources necessary for continuity operations on an emergency basis;
(e) Provision must be made for the availability and redundancy of critical communications capabilities at alternate sites in order to support connectivity between
and among key government leadership, internal elements, other executive departments and agencies, critical partners, and the public;
(f) Provision must be made for reconstitution capabilities that allow for recovery from a catastrophic emergency and resumption of normal operations; and
(g) Provision must be made for the identification, training, and preparedness of personnel capable of relocating to alternate facilities to support the continuation of the performance of PMEFs.
(12) In order to provide a coordinated response to escalating threat levels or actual emergencies, the Continuity of Government Readiness Conditions (COGCON) system establishes executive branch continuity program readiness levels, focusing
on possible threats to the National Capital Region. The President will determine and issue the COGCON Level. Executive departments and agencies shall comply with the requirements and
assigned responsibilities under the COGCON program. During COOP activation, executive departments and agencies shall report their readiness status to the Secretary of Homeland Security or the Secretary's designee.
(13) The Director of the Office of Management and Budget shall:
(a) Conduct an annual assessment of executive department and agency continuity funding requests and performance data that are submitted by executive departments and agencies as part of the annual budget request process, in order to monitor progress in the implementation of the Plan and the execution of continuity budgets;
(b) In coordination with the National Continuity Coordinator, issue annual continuity planning guidance for the development of continuity budget requests; and
(c) Ensure that heads of executive departments and agencies prioritize budget resources for continuity capabilities, consistent with this directive.
(14) The Director of the Office of Science and Technology Policy shall:
(a) Define and issue minimum requirements for continuity communications for executive departments and agencies, in consultation with the APHS/CT, the APNSA, the Director of the Office of Management and Budget, and the Chief of Staff to the President;
(b) Establish requirements for, and monitor the development, implementation, and maintenance of, a comprehensive communications architecture to integrate continuity components, in consultation with the APHS/CT, the APNSA, the Director of the Office of Management and Budget, and the Chief of Staff to the President; and
(c) Review quarterly and annual assessments of continuity communications capabilities, as prepared pursuant to section 16(d) of this directive or otherwise, and report the results and recommended remedial actions to the National Continuity Coordinator.
(15) An official designated by the Chief of Staff to the President shall:
(a) Advise the President, the Chief of Staff to the President, the APHS/CT, and the APNSA on COGCON operational execution options; and
(b) Consult with the Secretary of Homeland Security in order to ensure synchronization and integration of continuity activities among the four categories of executive departments and agencies.
(16) The Secretary of Homeland Security shall:
(a) Coordinate the implementation, execution, and assessment of continuity operations and activities;
(b) Develop and promulgate Federal Continuity Directives in order to establish continuity planning requirements for executive departments and agencies;
(c) Conduct biennial assessments of individual department and agency continuity capabilities as prescribed by the Plan and report the results to the President through the APHS/CT;
(d) Conduct quarterly and annual assessments of continuity communications capabilities in consultation with an official designated by the Chief of Staff to the President;
(e) Develop, lead, and conduct a Federal continuity training and exercise program, which shall be incorporated into the National Exercise Program developed pursuant to Homeland Security Presidential Directive-8 of December 17, 2003 ("National Preparedness"), in consultation with an
official designated by the Chief of Staff to the President;
(f) Develop and promulgate continuity planning guidance to State, local, territorial, and tribal governments, and private sector critical infrastructure owners and operators;
(g) Make available continuity planning and exercise funding, in the form of grants as provided by law, to State, local, territorial, and tribal governments, and private sector critical infrastructure owners and operators; and
(h) As Executive Agent of the National Communications System, develop, implement, and maintain a comprehensive continuity communications architecture.
(17) The Director of National Intelligence, in coordination with the Attorney General and the Secretary of Homeland Security, shall produce a biennial assessment of the foreign and domestic threats to the Nation's continuity of government.
(18) The Secretary of Defense, in coordination with the Secretary of Homeland Security, shall provide secure, integrated, Continuity of Government communications to the President, the Vice President, and, at a minimum, Category I executive departments and agencies.
(19) Heads of executive departments and agencies shall execute their respective department or agency COOP plans in response to a localized emergency and shall:
(a) Appoint a senior accountable official, at the Assistant Secretary level, as the Continuity Coordinator for the department or agency;
(b) Identify and submit to the National Continuity Coordinator the list of PMEFs for the department or agency and develop continuity plans in support of the NEFs and the continuation of essential functions under all conditions;
(c) Plan, program, and budget for continuity capabilities consistent with this directive;
(d) Plan, conduct, and support annual tests and training, in consultation with the Secretary of Homeland Security, in order to evaluate program readiness and ensure adequacy and viability of continuity plans and communications systems; and
(e) Support other continuity requirements, as assigned by category, in accordance with the nature and characteristics of its national security roles and responsibilities
General Provisions
(20) This directive shall be implemented in a manner that is consistent with, and facilitates effective implementation of, provisions of the Constitution concerning succession to the Presidency or the exercise of its powers, and the Presidential Succession Act of 1947 (3 U.S.C. 19), with consultation of the Vice President and, as appropriate, others involved. Heads of executive departments and agencies shall ensure that appropriate
support is available to the Vice President and others involved as necessary to be prepared at all times to implement those provisions.
(21) This directive:
(a) Shall be implemented consistent with applicable law and the authorities of agencies, or heads of agencies, vested by law, and subject to the availability of appropriations;
(b) Shall not be construed to impair or otherwise affect (i) the functions of the Director of the Office of Management and Budget relating to budget, administrative, and legislative proposals, or (ii) the authority of the Secretary of Defense over the Department of Defense, including the chain of command for military forces from the President, to the Secretary of Defense, to the commander of military forces, or military command and control procedures; and
(c) Is not intended to, and does not, create any rights or benefits, substantive or procedural, enforceable at law or in equity by a party against the United States, its
agencies, instrumentalities, or entities, its officers, employees, or agents, or any other person.
(22) Revocation. Presidential Decision Directive 67 of October 21, 1998 ("Enduring Constitutional Government and Continuity of Government Operations"), including all Annexes thereto, is hereby revoked.
(23) Annex A and the classified Continuity Annexes, attached hereto, are hereby incorporated into and made a part of this directive.
(24) Security. This directive and the information contained herein shall be protected from unauthorized disclosure, provided that, except for Annex A, the Annexes attached to this directive are classified and shall be accorded appropriate handling, consistent with applicable Executive Orders.
GEORGE W. BUSH
www.whitehouse.gov/news/rel...9-12.html
Call on Gov Ted Kulongoski to cancel Operation Noble Resolve
Call on Gov Ted Kulongoski to cancel Operation Noble Resolve at least until some major issues are cleared up over the Presidential Directive 51 and the habit of some strategic games becoming simultaneous real events is fully investigated.
Congressman Peter DeFazio has been blocked in his investigations on the issues surrounding the planned event and its relationship to National Security Presidential Directive 51 which would give Bush dictatorial powers if such a real event like a nuclear attack on Portland did happen. Governor Kulongoski could address this issue and demand that state employees not comply or work with FEMA and other organizations planning Operation Noble Resolve until major issues and questions are satisfactorily answered. On July 20th of 2007 after refusal to have access to documents related to Presidential Directive 5, DeFazio "Maybe the people who think there's a conspiracy out there are right." The fear is that like the Tube Bombing in London on 7/7 2005 and the 9/11 tragedy there were simultaneous mock events that were similar to the actual events taking place.
contacting Oregon Governor Kulongoski:
Please use one of the following methods if you would like to share an opinion or if the Governor´s Office can be of assistance:
MAIL Governor Kulongoski 160 State Capitol 900 Court Street Salem, Oregon 97301-4047
PHONE Governor’s Citizens’ Representative Message Line 503.378.4582
FAX 503.378.6827
POSSIBLE STATE ALTERNATIVES TO OPERATION NOBLE RESOLVE
Governor Ted Kulongoski and Governor Christine Gregoire could propose alternatives to Operation Noble Resolve. One alternative could be to have strategic simulations on counter-dictatorial usuption of our federal system. This could be done by having mass teach-ins on administrative noncooperation, civil disobedience and other nonviolent actions as well as civics with mock events simulating a coups d'état in our federal system. In 1983, Dr. Gene Sharp had proposed that creating a civillian based defense using nonviolent tactics would be far more effective against invading and anti democratic forces as well as much more economically sustainable.
www.fragmentsweb.org/fourtx/...lec.html
The two sister states of Oregon and Washington could host a training and implimentation of a civillian based defense in complete cooperation with the Oregon and Washington State National Guards. We could give such a civics training and mock events even a name like Operation Evergreen. This could be done with the cooperation of the various states’ educational systems, liberaries and other organizations both governmental and non-governmental.
Gene Sharp, Civilian-Based Defense: A Post-Military Weapons System (Princeton, New Jersey: Princeton University Press, 1990).
Gene Sharp Lecture on Civilian-Based Defense (audio of the 1983 lecture on creating a nonviolent civillian system to counter tryanny) www.fragmentsweb.org/fourtx/...lec.html
NSPD 51 FROM WHITEHOUSE WEBSITE (for those not familiar with the Presidential Directive)
White House News
NATIONAL SECURITY PRESIDENTIAL DIRECTIVE/NSPD 51
HOMELAND SECURITY PRESIDENTIAL DIRECTIVE/HSPD-20
Subject: National Continuity Policy
Purpose
(1) This directive establishes a comprehensive national policy on the continuity of Federal Government structures and operations and a single National Continuity Coordinator responsible for coordinating the development and implementation of Federal continuity policies. This policy establishes "National Essential Functions," prescribes continuity requirements for all executive departments and agencies, and provides guidance for State, local, territorial, and tribal governments, and private sector organizations in order to ensure a comprehensive and integrated national continuity program that will enhance the credibility of our national security posture and enable a more rapid and effective response to and recovery from a national emergency.
Definitions
(2) In this directive:
(a) "Category" refers to the categories of executive departments and agencies listed in Annex A to this directive;
(b) "Catastrophic Emergency" means any incident, regardless of location, that results in extraordinary levels of mass casualties, damage, or disruption severely affecting the U.S. population, infrastructure, environment, economy, or government functions;
(c) "Continuity of Government," or "COG," means a coordinated effort within the Federal Government's executive branch to ensure that National Essential Functions continue to be performed during a Catastrophic Emergency;
(d) "Continuity of Operations," or "COOP," means an effort within individual executive departments and agencies to ensure that Primary Mission-Essential Functions continue to be performed during a wide range of emergencies, including localized acts of nature, accidents, and technological or attack-related emergencies;
(e) "Enduring Constitutional Government," or "ECG," means a cooperative effort among the executive, legislative, and judicial branches of the Federal Government, coordinated by the President, as a matter of comity with respect to the legislative and judicial branches and with proper respect for the constitutional separation of powers among the branches, to preserve the constitutional framework under which the Nation is governed and the capability of all three branches of government to execute constitutional responsibilities and provide for orderly succession, appropriate transition of leadership, and interoperability and support of the National Essential Functions during a catastrophic emergency;
(f) "Executive Departments and Agencies" means the executive departments enumerated in 5 U.S.C. 101, independent establishments as defined by 5 U.S.C. 104(1), Government corporations as defined by 5 U.S.C. 103(1), and the United States Postal Service;
(g) "Government Functions" means the collective functions of the heads of executive departments and agencies as defined by statute, regulation, presidential direction, or other legal authority, and the functions of the legislative and judicial branches;
(h) "National Essential Functions," or "NEFs," means that subset of Government Functions that are necessary to lead and sustain the Nation during a catastrophic emergency and that, therefore, must be supported through COOP and COG capabilities; and
(i) "Primary Mission Essential Functions," or "PMEFs," means those Government Functions that must be performed in order to support or implement the performance of NEFs before, during, and in the aftermath of an emergency.
Policy
(3) It is the policy of the United States to maintain a comprehensive and effective continuity capability composed of Continuity of Operations and Continuity of Government programs in order to ensure the preservation of our form of government under the Constitution and the continuing performance of National Essential Functions under all conditions.
Implementation Actions
(4) Continuity requirements shall be incorporated into daily operations of all executive departments and agencies. As a result of the asymmetric threat environment, adequate warning of potential emergencies that could pose a significant risk to the homeland might not be available, and therefore all continuity planning shall be based on the assumption that no such warning will be received. Emphasis will be placed upon geographic dispersion of leadership, staff, and infrastructure in order to increase survivability and maintain uninterrupted Government Functions. Risk management principles shall be applied to ensure that appropriate operational readiness decisions are based on the probability of an attack or other incident and its consequences.
(5) The following NEFs are the foundation for all continuity programs and capabilities and represent the overarching responsibilities of the Federal Government to lead and sustain the Nation during a crisis, and therefore sustaining the following NEFs shall be the primary focus of
the Federal Government leadership during and in the aftermath of an emergency that adversely affects the performance of Government Functions:
(a) Ensuring the continued functioning of our form of government under the Constitution, including the functioning of the three separate branches of government;
(b) Providing leadership visible to the Nation and the world and maintaining the trust and confidence of the American people;
(c) Defending the Constitution of the United States against all enemies, foreign and domestic, and preventing or interdicting attacks against the United States or its people, property, or interests;
(d) Maintaining and fostering effective relationships with foreign nations;
(e) Protecting against threats to the homeland and bringing to justice perpetrators of crimes or attacks against the United States or its people, property, or interests;
(f) Providing rapid and effective response to and recovery from the domestic consequences of an attack or other incident;
(g) Protecting and stabilizing the Nation's economy and ensuring public confidence in its financial systems; and
(h) Providing for critical Federal Government services that address the national health, safety, and welfare needs of the United States.
(6) The President shall lead the activities of the Federal Government for ensuring constitutional government. In order to advise and assist the President in that function, the Assistant to the President for Homeland Security and Counterterrorism (APHS/CT) is hereby designated as the National Continuity Coordinator. The National Continuity Coordinator, in coordination with the Assistant to the President for National
Security Affairs (APNSA), without exercising directive authority, shall coordinate the development and implementation of continuity policy for executive departments and agencies. The Continuity Policy Coordination Committee (CPCC), chaired by a Senior Director from the Homeland Security Council staff, designated by the National Continuity Coordinator, shall be the main day-to-day forum for such policy coordination.
(7) For continuity purposes, each executive department and agency is assigned to a category in accordance with the nature and characteristics of its national security roles and
responsibilities in support of the Federal Government's ability to sustain the NEFs. The Secretary of Homeland Security shall serve as the President's lead agent for coordinating overall
continuity operations and activities of executive departments and agencies, and in such role shall perform the responsibilities set forth for the Secretary in sections 10 and 16 of this directive.
(8) The National Continuity Coordinator, in consultation with the heads of appropriate executive departments and agencies, will lead the development of a National Continuity Implementation Plan (Plan), which shall include prioritized goals and objectives, a concept of operations, performance metrics by which to measure continuity readiness, procedures for continuity and incident management activities, and clear direction to executive department and agency continuity coordinators, as well as guidance to promote interoperability of Federal Government continuity programs and procedures with State, local, territorial, and tribal governments, and private sector owners and operators of critical infrastructure, as appropriate. The Plan shall be submitted to the President for approval not later than 90 days after the date of this directive.
(9) Recognizing that each branch of the Federal Government is responsible for its own continuity programs, an official designated by the Chief of Staff to the President shall ensure that the executive branch's COOP and COG policies in support of ECG efforts are appropriately coordinated with those of
the legislative and judicial branches in order to ensure interoperability and allocate national assets efficiently to maintain a functioning Federal Government.
(10) Federal Government COOP, COG, and ECG plans and operations shall be appropriately integrated with the emergency plans and capabilities of State, local, territorial, and tribal governments, and private sector owners and operators of critical infrastructure, as appropriate, in order to promote interoperability and to prevent redundancies and conflicting lines of authority. The Secretary of Homeland Security shall coordinate the integration of Federal continuity plans and operations with State, local, territorial, and tribal governments, and private sector owners and operators of critical infrastructure, as appropriate, in order to provide for the delivery of essential services during an emergency.
(11) Continuity requirements for the Executive Office of the President (EOP) and executive departments and agencies shall include the following:
(a) The continuation of the performance of PMEFs during any emergency must be for a period up to 30 days or until normal operations can be resumed, and the capability to be fully operational at alternate sites as soon as possible after the occurrence of an emergency, but not later than 12 hours after COOP activation;
(b) Succession orders and pre-planned devolution of authorities that ensure the emergency delegation of authority must be planned and documented in advance in accordance with applicable law;
(c) Vital resources, facilities, and records must be safeguarded, and official access to them must be provided;
(d) Provision must be made for the acquisition of the resources necessary for continuity operations on an emergency basis;
(e) Provision must be made for the availability and redundancy of critical communications capabilities at alternate sites in order to support connectivity between
and among key government leadership, internal elements, other executive departments and agencies, critical partners, and the public;
(f) Provision must be made for reconstitution capabilities that allow for recovery from a catastrophic emergency and resumption of normal operations; and
(g) Provision must be made for the identification, training, and preparedness of personnel capable of relocating to alternate facilities to support the continuation of the performance of PMEFs.
(12) In order to provide a coordinated response to escalating threat levels or actual emergencies, the Continuity of Government Readiness Conditions (COGCON) system establishes executive branch continuity program readiness levels, focusing
on possible threats to the National Capital Region. The President will determine and issue the COGCON Level. Executive departments and agencies shall comply with the requirements and
assigned responsibilities under the COGCON program. During COOP activation, executive departments and agencies shall report their readiness status to the Secretary of Homeland Security or the Secretary's designee.
(13) The Director of the Office of Management and Budget shall:
(a) Conduct an annual assessment of executive department and agency continuity funding requests and performance data that are submitted by executive departments and agencies as part of the annual budget request process, in order to monitor progress in the implementation of the Plan and the execution of continuity budgets;
(b) In coordination with the National Continuity Coordinator, issue annual continuity planning guidance for the development of continuity budget requests; and
(c) Ensure that heads of executive departments and agencies prioritize budget resources for continuity capabilities, consistent with this directive.
(14) The Director of the Office of Science and Technology Policy shall:
(a) Define and issue minimum requirements for continuity communications for executive departments and agencies, in consultation with the APHS/CT, the APNSA, the Director of the Office of Management and Budget, and the Chief of Staff to the President;
(b) Establish requirements for, and monitor the development, implementation, and maintenance of, a comprehensive communications architecture to integrate continuity components, in consultation with the APHS/CT, the APNSA, the Director of the Office of Management and Budget, and the Chief of Staff to the President; and
(c) Review quarterly and annual assessments of continuity communications capabilities, as prepared pursuant to section 16(d) of this directive or otherwise, and report the results and recommended remedial actions to the National Continuity Coordinator.
(15) An official designated by the Chief of Staff to the President shall:
(a) Advise the President, the Chief of Staff to the President, the APHS/CT, and the APNSA on COGCON operational execution options; and
(b) Consult with the Secretary of Homeland Security in order to ensure synchronization and integration of continuity activities among the four categories of executive departments and agencies.
(16) The Secretary of Homeland Security shall:
(a) Coordinate the implementation, execution, and assessment of continuity operations and activities;
(b) Develop and promulgate Federal Continuity Directives in order to establish continuity planning requirements for executive departments and agencies;
(c) Conduct biennial assessments of individual department and agency continuity capabilities as prescribed by the Plan and report the results to the President through the APHS/CT;
(d) Conduct quarterly and annual assessments of continuity communications capabilities in consultation with an official designated by the Chief of Staff to the President;
(e) Develop, lead, and conduct a Federal continuity training and exercise program, which shall be incorporated into the National Exercise Program developed pursuant to Homeland Security Presidential Directive-8 of December 17, 2003 ("National Preparedness"), in consultation with an
official designated by the Chief of Staff to the President;
(f) Develop and promulgate continuity planning guidance to State, local, territorial, and tribal governments, and private sector critical infrastructure owners and operators;
(g) Make available continuity planning and exercise funding, in the form of grants as provided by law, to State, local, territorial, and tribal governments, and private sector critical infrastructure owners and operators; and
(h) As Executive Agent of the National Communications System, develop, implement, and maintain a comprehensive continuity communications architecture.
(17) The Director of National Intelligence, in coordination with the Attorney General and the Secretary of Homeland Security, shall produce a biennial assessment of the foreign and domestic threats to the Nation's continuity of government.
(18) The Secretary of Defense, in coordination with the Secretary of Homeland Security, shall provide secure, integrated, Continuity of Government communications to the President, the Vice President, and, at a minimum, Category I executive departments and agencies.
(19) Heads of executive departments and agencies shall execute their respective department or agency COOP plans in response to a localized emergency and shall:
(a) Appoint a senior accountable official, at the Assistant Secretary level, as the Continuity Coordinator for the department or agency;
(b) Identify and submit to the National Continuity Coordinator the list of PMEFs for the department or agency and develop continuity plans in support of the NEFs and the continuation of essential functions under all conditions;
(c) Plan, program, and budget for continuity capabilities consistent with this directive;
(d) Plan, conduct, and support annual tests and training, in consultation with the Secretary of Homeland Security, in order to evaluate program readiness and ensure adequacy and viability of continuity plans and communications systems; and
(e) Support other continuity requirements, as assigned by category, in accordance with the nature and characteristics of its national security roles and responsibilities
General Provisions
(20) This directive shall be implemented in a manner that is consistent with, and facilitates effective implementation of, provisions of the Constitution concerning succession to the Presidency or the exercise of its powers, and the Presidential Succession Act of 1947 (3 U.S.C. 19), with consultation of the Vice President and, as appropriate, others involved. Heads of executive departments and agencies shall ensure that appropriate
support is available to the Vice President and others involved as necessary to be prepared at all times to implement those provisions.
(21) This directive:
(a) Shall be implemented consistent with applicable law and the authorities of agencies, or heads of agencies, vested by law, and subject to the availability of appropriations;
(b) Shall not be construed to impair or otherwise affect (i) the functions of the Director of the Office of Management and Budget relating to budget, administrative, and legislative proposals, or (ii) the authority of the Secretary of Defense over the Department of Defense, including the chain of command for military forces from the President, to the Secretary of Defense, to the commander of military forces, or military command and control procedures; and
(c) Is not intended to, and does not, create any rights or benefits, substantive or procedural, enforceable at law or in equity by a party against the United States, its
agencies, instrumentalities, or entities, its officers, employees, or agents, or any other person.
(22) Revocation. Presidential Decision Directive 67 of October 21, 1998 ("Enduring Constitutional Government and Continuity of Government Operations"), including all Annexes thereto, is hereby revoked.
(23) Annex A and the classified Continuity Annexes, attached hereto, are hereby incorporated into and made a part of this directive.
(24) Security. This directive and the information contained herein shall be protected from unauthorized disclosure, provided that, except for Annex A, the Annexes attached to this directive are classified and shall be accorded appropriate handling, consistent with applicable Executive Orders.
GEORGE W. BUSH
www.whitehouse.gov/news/rel...9-12.html
posted by:
|
Advertisement
Advertisement
-
Re: Ask Kulongoski to Stop the Nuking of Portland
Thu, August 16, 2007 - 7:43 PMfrom www.thepriceofliberty.org/may.htm
Staging the Portland Nuke (A Comedy of Terrors)
By Captain Eric H. May - Special Military Correspondent
August 13, 2007
"All the world's a stage, and all the men and women merely players."
William Shakespeare
Writer's note: Several of the characters in the Portland Nuke plot have supplied their own lines via emails and articles, from which I have included extracts below. All emails were addressed to me as replies to my questions or articles.
Prologue: LTC Philip Smith
"In August, Noble Resolve will coordinate with officials in Oregon to model a nuclear attack on Portland." wrote Josh Rogin, military reporter for Federal Computer Week's FCW.com on April 4. His article was the basis of my first call with Lt. Col. Philip Smith, a senior public affairs officer for the U.S. Joint Forces Command, which is conducting the military exercise.
Smith and I found plenty to talk about in a half-hour chat. As a former Army public affairs officer myself, I knew about his job, which is to inform the public on stories of interest or concern. We discussed computer-simulated exercises like Noble Resolve, and he seemed interested in my own experience with the concept back in its initial days, around the time of the first Iraq war. It's a small world when you're part of the military intelligentsia, and we soon discovered that both his wife and I had belonged to the 75th Division, specializing in military exercises, headquartered in Houston, Texas.
On the subject of Noble Resolve itself though, he had few ready answers other than the date of the exercise, which was August 20-24. I told him that this bare fact added greatly to public knowledge, and said that I found it shocking that no press release had come out since the spring. It was as if the government was purposely avoiding informing the public of the training it claimed to be conducting for the public's security, and that impression of things had become general across the Internet, where alarmed citizens and specialists were writing that the exercise might be a cover operation for the execution of the nuke scenario it was practicing.
Smith agreed with me that it was important to get an updated story out, and later replied to my email promising to follow up with much-needed details. By then, we were on a first-name basis:
Subject: RE: ATTN LTC SMITH:
Next 9/11, Summer 2007?
Date: Thu, 2 Aug 2007
Eric,
I've have [sic] not received an answer to the two questions you asked yesterday; a list of participating agencies to include Oregon state assets, and a list of unclassified exercises like Noble Resolve.
Ms. Susanne Moore, LT Jereal Dorsey or I will contact you via phone or email as soon as we have the answer.
Philip J. Smith Lieutenant Colonel,
U.S. Army Deputy Director of Public Affairs
U.S. Joint Forces Command
After this communication, though, he dropped strangely out of touch, something public affairs officers are taught never to do.
Act One: Politicians Dodging and Diving
Smith wasn't the only government official playing hard to get. Penny Dodge, chief of staff for Oregon's Congressman Peter DeFazio, had already disappeared from media scrutiny, although her boss was the center of anxious attention. DeFazio's constituents had blitzed him with their fear that Noble Resolve might turn out to be a false flag attack against them, undertaken by a sagging Bush administration to justify implementing National Security Presidential Directive 51, a plan for dictatorship, which Bush signed into effect in May -- at about the time that Dick Cheney led a growing chorus of White House insiders suggesting that an Al Qaeda nuclear attack was imminent.
Worried Oregonians hounded DeFazio, despite his initial assurances that all was well, into requesting an examination of the secret annexes of NSPD-51. As a member of the House Homeland Security Committee, with all appropriate security clearances, DeFazio was entitled to see NSPD-51 in full, but for the first time in his 20-year career he was refused access.
"Maybe the people who think there's a conspiracy out there are right" DeFazio said in a July 20 interview, then issued a second request, this one written and co-authored by House Homeland Security Committee Chairman Bernie Thompson. On August 1 the possibility of a conspiracy seemed all the more likely: the White House had again refused DeFazio.
To date both DeFazio and Dodge have failed to return calls or offer an update. They are more than a week into the congressional summer break, and less than two weeks away from Noble Resolve.
One of the signs of an official conspiracy, it's said, is that officials refuse to consider the possibility of a conspiracy. According to that rule, the city of Portland is behaving most curiously, if not complicitly. On the same day I contacted Mayor Tom Potter's office about the widespread concern that his city might be a false flag target, his chief spokesman dived for cover, and hasn't been heard from since:
Subject: RE: John Doussard (Portland's Director of Communications)
Date: Tue, 31 Jul 2007
Capt May - No agency or bureau affiliated with the City of Portland is participating in any part of any operation affiliated with Noble Resolve. Our director of the Office of Emergency Management has contacted the federal government and asked that our name be removed from any public communication about Noble Resolve.
John Doussard
Director of Communications
So Portland isn't an interested participant in a most alarming exercise -- it's only the target.
Act Two: An Iconoclastic Inquest
Wednesday, after a week of waiting for LTC Smith to supply promised details of Noble Resolve, and more than a week since Congressman DeFazio and Mayor Potter had become incommunicado, my editor at The Lone Star Iconoclast, W. Leon Smith, decided that we had waited long enough. I wrote a brief article, "Portland Nuclear Inquest Formed & Functioning." It contained the email from Smith, was copied to the offices of DeFazio and Potter and, thanks to a raging Internet interest, was quickly published worldwide. It was a no-frills attempt to kick start what had become a closed conversation -- and it worked.
Act Three: Heroic Helpers -- KBOO-FM and an Anonymous Official
The next day Portland's KBOO FM radio station continued the truth offensive. Its news analysis program Press Watch, hosted by Theresa Mitchel, carried an hour-long examination of Noble Resolve. Mitchel noted that the KBOO news department had just contacted the JFCOM public affairs office, which had informed the station that the Portland nuclear attack of Noble Resolve had been changed into a volcanic eruption instead. Mitchel said she doubted the new story, likely issued as a "public relations soother," and urged her listeners to monitor and discuss the upcoming exercise.
That same day The Iconoclast and I received word from an anonymous military official that there was plenty in Noble Resolve -- and JFCOM's silence about it -- to worry about:
Subject: Re: "PORTLAND NUCLEAR INQUEST" Formed & Functioning
Date: Wed, 8 Aug 2007
CPT May: I'm sure LTC Smith has been given his marching orders to NOT reply to your questions. If you make enough noise about Portland going live, then they can't pull it off. I have no vibes on activities, but if I were there, I would be on the look out for indicators of something being set up. I sure hope someone steps up and offers assistance from the inside. I look forward to your words and works.
Act Four: A Lap Dog and a Lap Dancer -- The Oregonian
On July 28 The Oregonian ran a story by its Washington reporter, Jeff Kosseff, with the headline "DeFazio chases secret terror-crisis plan," followed by the subheading "After the White House denies access, the Web buzzes with conspiracy chatter."
Kosseff's article continued:
"After conspiracy theorists fanned the Internet with their outrage, the Oregon congressman renewed his push Friday to gain access to the classified portion of a White House plan to operate the government after a terrorist attack."
The deprecating tone of The Oregonian and Kosseff toward the "conspiracy chatter" in the Internet was a cheap shot to say the least. By all accounts, the only reason that DeFazio had attempted to gain access to NSPD-51 at all was the incessant -- and informed -- opinion of Internet writers that there was a story worth investigation. Without "conspiracy chatter" and "conspiracy theorists," DeFazio would have dodged the confrontation with the White House, and The Oregonian wouldn't have bothered to run the story of the presidential directive.
Further, The Oregonian had ignobly shirked half the story of why Oregon residents were worried about NSPD-51 in the first place: the Noble Resolve nuclear exercise, which they feared would turn into an awful false flag reality. In the months since the Internet took up the story, The Oregonian had never bothered to acknowledge the existence -- let alone report the details -- of Noble Resolve.
Having failed to report the news of the exercise, The Oregonian nevertheless editorialized in favor of it yesterday with its "'Noble' is good, not grand."
"In a couple of weeks, members of the Oregon National Guard are going to take part in a multiagency homeland security exercise... This drill, which the Pentagon has dubbed Operation Noble Resolve, has sparked concerns in some quarters in Oregon, where suspicions about the military and the Bush administration abound [because of the] online exercise that presses players to respond to a simulated emergency involving a nuclear threat... While some choose to view this exercise as sinister -- a pretext for a nuclear attack by the U.S. military on American citizens, according to some fevered speculation -- it is, in fact, a prudent thing to do.
Act Five: Joint Forces Comedy (JFCOM)
Yesterday JFCOM launched a public affairs operation for Noble Resolve as well. LTC Smith sent me and The Iconoclast a reply to the Portland Nuclear Inquest article. His tone had changed since our conversations and emails of a week before, and we were no longer on a first-name basis. He wrote (repeatedly) that what he had previously agreed was the Noble Resolve exercise was actually only an experiment -- and that he had always called it that. Finally, and amazingly, he asserted that the exercise didn't involve a nuclear scenario. This contradicted insider articles of previous months, KBOO's news department of the day before and The Oregonian's editorial of the same day:
Subject: RE: "PORTLAND NUCLEAR INQUEST" Formed & Functioning
Date: Fri, 10 Aug 2007
CC: Rep. Peter DeFazio,
City of Portland,
The Lone Star Iconoclast
Mr. May,
As discussed in our phone conversation last week, Noble Resolve is an experiment conducted completely in a modeling and simulation, or computer, environment. No troops or emergency management personnel will deploy. All of this is conducted in rooms and across computer networks.
[T]here is no "nuke" or weapon of mass destruction event, real or otherwise, simulated in the Noble Resolve experiment.
the [sic] most recent article on the experiment is found below. I believe it will answer your questions.
Philip J. Smith Lieutenant Colonel,
U.S. Army Deputy Director of Public Affairs
U.S. Joint Forces Command
Smith attached a JFCOM press release, prepared that same day, with the innocuous title "Noble Resolve 07-2 aims at making communication easier." It asserted the same points he had made in his email, and it was poor reading -- unless you read between the lines. Needless to say, I had some hard questions for Smith about his email and the press release, but he had sent them at the close of business on a Friday, and neither he nor any other public affairs official has responded to messages relayed through the JFCOM duty officer. It's worth noting that Smith failed to provide the specific answers he had promised to my specific questions of the week before.
Epilogue: The Enemy at the Bridge
"Let us never tolerate outrageous conspiracy theories..."
George W. Bush to the United Nations, 11/1/01
The "war president" who uttered the words above was, at the time of the utterance, credible and supported by nine-tenths of the American People; the same man now lacks credibility and is scorned by two-thirds of the American People. His White House actions and actors have revealed impeachable motives, and may lead to his impeachment. As commander-in-chief, he is the ultimate source and director of Noble Resolve, and we are right to not trust him.
The same presstitutes who now openly detail his lies were once afraid to question his assertions in private, and they continue to lag behind public opinion when it comes to George W. Bush. Their incessant description of anyone who knows about, speaks about or writes about things outside their "reporting" as a "conspiracy theorist" is a self-serving attempt to explain away their failure to do their jobs, and is a good argument that there is indeed a conspiracy -- and that they are part of it.
I offer one parting conspiracy theory for the affable or the anxious reader: Portland really has been set up by a failing Bush administration, and is being let down by its political and media leaders. A disturbing report, dated April 19, by the "Preventive Defense Project," suggests that Portland is in the crosshairs of a nuclear attack. With the ominous title "The Day After: Action in the 24 Hours Following a Nuclear Blast in an American City," the report contains three nuclear blast/fallout maps. Two of them are general and, not surprisingly, show Washington D.C. as ground zero; the third is quite specific, and, quite surprisingly, shows northwest Portland's Burlington Northern Railroad Bridge, near the port on the Willamette River, as ground zero:
Whether or not the Comedy of Terrors I have presented above will succeed or fail is up to the American People, who must compensate for the propaganda and plans of their leaders by thinking and acting for themselves. This is what was expected of us by the founders who created our republic, who had the vision to predict that eventually their creation would become corrupt and, if not redeemed, conspiratorial.
Captain May is a former Army military intelligence and public affairs officer, as well as a former NBC editorial writer. His political and military analyses have appeared in The Wall Street Journal, the Houston Chronicle and Military Intelligence Magazine. Readers can receive regular updates on Noble Resolve through the Portland Nuclear Inquest.
[Editor's note: The links to articles at "The Oregonian" may not be valid without a paid subscription within a short time.]
***********
And from www.oregonlive.com/oregonia...index.ssf
'Noble' is good, not grand
Friday, August 10, 2007
I n a couple of weeks, members of the Oregon National Guard are going to take part in a multiagency homeland security exercise that will be roughly equivalent to playing "The Sims" on a supercomputer. This drill, which the Pentagon has dubbed Operation Noble Resolve, has sparked concerns in some quarters in Oregon, where suspicions about the military and the Bush administration abound. But it is exactly the kind of thing that the Homeland Security and Defense Departments should be doing.
(The drill, that is. Not the name, which flows from the same marketing minds that gave us "Exercise Eager Mace," "Operation Shining Presence" and other gems.)
Oregon will be "home" -- although the exercise will involve people in other states, too -- to an online exercise that presses players to respond to a simulated emergency involving a nuclear threat.
There won't be people running down the streets, dragging fire hoses or tending to actors feigning internal hemorrhages. It's all virtual, in which players respond to a catastrophe by, say, choosing to blockade a city street, and in doing so, trigger consequences, such as causing a traffic jam in an unexpected place. It's useful because it pulls together multiple agencies in multiple places, just as a real-world disaster would do. And when a real-world disaster strikes, breakdowns in response most frequently occur on the seams between agencies. We need cast our minds back no further than last winter's bungled hunt for the Kim family in southern Oregon to understand how costly such breakdowns can be.
Operation Noble Resolve is actually a rolling series of exercises -- "experiments," in the parlance of the U.S. Forces Joint Command -- taking place over two years in multiple jurisdictions. The command conducted one centered in southern Virginia in April, basing it on a simulated terrorist attack. It's all a preamble to a more complex exercise called TopOff that will take place in Portland this fall.
This idea for Noble Resolve evolved from simulations of overseas catastrophes, such as how to react to explosions in Baghdad, for example, and applied them to the United States. While some choose to view this exercise as sinister -- a pretext for a nuclear attack by the U.S. military on American citizens, according to some fevered speculation -- it is, in fact, a prudent thing to do.
Nobody wants to live through a real disaster in which all the decision-makers are thinking for the first time about how to deal with it.
(no author named) -
-
Re: Ask Kulongoski to Stop the Nuking of Portland
Thu, August 16, 2007 - 7:46 PMfrom www.oregonlive.com/news/ore...index.ssf
DeFazio chases secret terror-crisis plan
Homeland security - After the White House denies access, the Web buzzes with conspiracy chatter
Saturday, July 28, 2007
JEFF KOSSEFF
The Oregonian Staff
WASHINGTON -- Peter DeFazio won't take no for an answer.
After conspiracy theorists fanned the Internet with their outrage, the Oregon congressman renewed his push Friday to gain access to the classified portion of a White House plan to operate the government after a terrorist attack.
This time, DeFazio is joined by two other Democrats on the House Homeland Security Committee who wrote to a top Bush administration Homeland Security official requesting access to the information. The White House refused to provide it to DeFazio earlier this month, offering no explanation beyond national security concerns.
After The Oregonian reported the situation a week ago, the story spread rapidly across the Internet, linked from more than 250 blog postings and political Web sites.
"We can think of no basis for you to deny members of the Committee on Homeland Security the opportunity to review this document in a secure setting," states the letter signed by DeFazio; Rep. Bennie Thompson, D-Miss., chairman of the committee; and Rep. Chris Carney, D-Pa., chairman of the Homeland Security oversight subcommittee.
The letter was addressed to Frances Townsend, assistant to the president for homeland security and counterterrorism.
DeFazio wants to read the secret file after hearing from constituents concerned about a conspiracy. The public portion of the presidential directive lays out general policies for operating the government during a major catastrophe, but it referred to classified portions.
According to the letter, White House staff had initially said it would provide the document to Homeland Security Committee staff so DeFazio could review it. But on July 18, White House staff, the congressmen wrote, "informed the committee that the request had been reconsidered and rejected. In fact, the committee staff was told the document is 'close hold,' and 'frankly we are not willing to share it.' "
"This response is as troubling as it is shocking," wrote DeFazio and the other Democrats.
Members of Congress are allowed to view classified material in a secured room in the Capitol, provided they do not disclose the contents.
"In addition to the standard oath of secrecy taken by all members of Congress, members of the Committee on Homeland Security are required to sign an oath agreeing not to disclose any classified information received during the course of their service on the Committee," the congressmen wrote.
In a written statement, White House spokesman Trey Bohn would not say why DeFazio was denied access: "We do not comment through the press on the process that this access entails. It is important to keep in mind that much of the information related to the continuity of government is highly sensitive."
DeFazio's dispute points to a broader tension between the White House and members of Congress, who say they are not provided with information they request from the executive branch.
"I'm trying to think of one piece of information this administration has actually supplied to me that it hasn't first put out on CNN," Rep. David Wu, D-Ore., said in a recent interview, citing requests for information about whether helmet liners were being provided to the National Guard to requests for evidence of weapons of mass destruction.
Jeff Kosseff: jeff.kosseff@newhouse.com -
-
More on the possible Nuking of Portland
Fri, August 17, 2007 - 5:15 AMMore on the possible Nuking of Portland
If you have not heard there is a growing concern the fascist elements within the US corporate and government structures may use a mock scenario to actually nuke Portland Oregon and then use Presidential Directive 51 to declare Bush dictator and to declare war on Iran.
Some articles giving background:
portland.indymedia.org/en/200...4.shtml
portland.indymedia.org/en/200...4.shtml
portland.indymedia.org/en/200...8.shtml
Updated articles:
Swan Island Networks role in Portland drills
author: Mr_DNA
press release is from 1 year ago, but seems to shed some light on their role in the upcoming operations.
www.rainsnet.org/press/pr/...066778.asp
Portland Seeks Designation as First 'Synthetic City'
Technology in the war on terror now key to homeland security
Portland, OR - August 18, 2006 -
On Friday, August 18, a group of federal, state and local officials, academics, and private sector leaders will convene on the campus of Portland State University to talk about a potential transfer of power. Under discussion is the notion that technology used to fight the war on terror abroad could soon be applied to homeland security needs... and that Portland, Oregon could be an early test-bed for such transfers.
According to the Regional Alliances for Infrastructure and Network Security (RAINS), a central player in the development of homeland defense technology solutions, the primary military technology under consideration for transfer is "synthetic city" software—a digital information platform that fuses data from a variety of real-world sources, such as 9-1-1 centers, atmospheric sensors, smart buildings, health networks, and intelligent transportation systems—then organizes and displays it all in a 3-D geographical modeling and simulation environment.
"Our military friends are going to be demonstrating some very cutting edge technology—sort of the ultimate Sim City," explained RAINS' chairman Charles Jennings, "They'll be displaying virtual version of the real Portland, with real-time data inside." Jennings is the CEO of Portland-based Swan Island Networks.
The "Synthetic Portland" conference brings together participants from around the country, representing all levels of government, large federal contractors and system integrators; information technology vendor companies; universities; hospitals; and various types of non-governmental service organizations.
Also participating will be representatives from the Department of Homeland Security and the Transportation Security Administration; United States Joint Forces Command (JFCOM); the Information Assurance Directorate of the National Security Agency; and the U.S. Department of Transportation.
"We are excited to have such an innovative technology conference in Portland—especially since its ultimate purpose is to increase public safety," said Matt Lampe, the City of Portland's Chief Technology Officer. This new technology, like the Internet, was developed by the military and now, the military is actively exploring its use and potential in civil environments to improve emergency response, transportation systems and sustainability practices.
The central purpose of new synthetic city technology is to generate predictive models that can be used by the real city to prepare for and manage emergencies, increase public safety, and generally improve urban quality of life.
According to Jennings, "Although it could have been held anywhere, having this conference in Portland makes perfect sense. To connect previously stove-piped information systems in new ways, you need a city with a culture of both innovation and collaboration—two of Portland's best qualities."
"This is a unique opportunity to look at new, advanced technology and how that technology could help in the event of disasters or security problems. Portland State University does leading edge research in computer security, and we're interested in how that research can be used for application in areas that will be discussed at this symposium. That makes our campus the perfect venue for this event," said Mike Burton, Vice Provost of Portland State University and RAINS board member.
Sponsors of the event, in addition to RAINS and PSU, include Oregon Economic & Community Development Department; Portland Development Commission; Siemens; Online Business Systems; the Zeno Group; and Swan Island Networks.
About RAINS
RAINS (Regional Alliances for Infrastructure and Network Security) is a public/private partnership formed in 2001. RAINS has forged alliances with technology companies, multiple research universities, critical infrastructure providers, local, state and federal agencies, and first responders. Its Connect & Protect information sharing service was launched in 2003, and has successfully delivered hundreds of thousands of alerts. Connect & Protect was described as a "radical breakthrough" by WIRED Magazine (December 2005). Connect & Protect was also a finalist for the inaugural Mitretek Innovations Award in Homeland Security, a partnership of Mitretek Systems and the Ash Institute for Democratic Governance and Innovation at Harvard's John F. Kennedy School of Government.
For RAINS information:
Tel: 503-796-5804
info@rainsnet.org
contribute to this article
update 16.Aug.2007 15:07
Mr_DNA link
According to Sherry Lamoreaux, Marketing Communications Manager of Swan Island Networks:
1. Swan Island wanted to be a part of the Noble Resolve exercise but is not now participating and has no information regarding it.
2. RAINS is no longer an active organization. In her words, it has been "dormant" since around June of this year.
3. Swan Island Networks CEO and RAINS founder, Charles Jennings, will be on vacation beginning at the end of this week or next week.
found at portland.indymedia.org/en/200...7.shtml
__
Regarding Noble Resolve
author: fellow worker
8/10/07 naval vessel spotted at Port of Portland docks-maybe part of Noble Resolve nuke exercise?
While I was at lunch break on 8/10, I was sitting outside the Gunderson lunch room on the south bank of the Willamette, across from a Port of Portland facility. I saw an unidentifiable navel vessel, smallish, uniform battleship grey, apart from the blue and yellow bands encircling the stack. I was only able to make out numbers on the bow, either 23 or 28. No other markings, flags or symbols were visible, and I only wish I had my binoculars with me. Based on the projected blast pattern from "The Day After" Report as seen on www.lonestaricon.com, I am thinking this may be part of the exercise to come.
contribute to this article
specifics 16.Aug.2007 10:32
Mr_DNA link
Do you know which Terminal this is docked in or closest to?
unusual license plate 16.Aug.2007 11:17
hum link
seen this plate this morning heading into downtown
probably not "Noble related" but it caught my eye
it was hard to read all the print on the plate
picture at media.portland.indymedia.org/ima....jpg
posted at portland.indymedia.org/en/200...8.shtml -
-
Re: More on the possible Nuking of Portland
Fri, September 7, 2007 - 6:39 AMPlease keep this in mind:
While Operation Noble Resolve was seen by some of us as a potential for a nuclear false flag on Portland to trigger a war against Iran. Look what the military did last week with a B-52 "accidently armed with nukes mounted on its wings"
www.washingtonpost.com/wp-dyn...62.html
-
-
-
