DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

Similar documents
Subj: THREAT SUPPORT TO THE DEFENSE ACQUISITION SYSTEM

THREAT SUPPORT TO THE DEFENSE ACQUISITION SYSTEM

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON DC

DEPARTMENT OF THE NAVY COUNTERINTELLIGENCE

Subj: CERTIFICATION OF THE AVIATION CAPABILITY OF SHIPS OPERATING AIRCRAFT

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

Subj: MISSION, FUNCTIONS, AND TASKS OF NAVAL SPECIAL WARFARE COMMAND

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

COMMUNICATIONS SECURITY MONITORING OF NAVY TELECOMMUNICATIONS AND INFORMATION TECHNOLOGY SYSTEMS

Subj: CHEMICAL, BIOLOGICAL, RADIOLOGICAL, AND NUCLEAR DEFENSE REQUIREMENTS SUPPORTING OPERATIONAL FLEET READINESS

CERTIFICATION OF THE AVIATION CAPABILITY OF SHIPS OPERATING AIRCRAFT

OPNAVINST A N2/N6 19 Dec Subj: NAVAL OCEANOGRAPHY POLICY, RELATIONSHIPS, AND RESPONSIBILITIES

PROCEDURES FOR NAVY PARTICIPATION IN THE DEPARTMENT OF DEFENSE SPACE TEST PROGRAM

Subj: DEPARTMENT OF THE NAVY (DON) INFORMATION SECURITY PROGRAM (ISP) INSTRUCTION

Subj: NAVY ACCELERATED ACQUISITION FOR THE RAPID DEVELOPMENT, DEMONSTRATION, AND FIELDING OF CAPABILITIES

OPNAVINST A N2/N6 31 Oct Subj: NAVY ELECTRONIC CHART DISPLAY AND INFORMATION SYSTEM POLICY AND STANDARDS

OPNAVINST E N97 7 Nov 2017

OPNAVINST DNS-3/NAVAIR 24 Apr Subj: MISSIONS, FUNCTIONS, AND TASKS OF THE COMMANDER, NAVAL AIR SYSTEMS COMMAND

SECNAVINST E OUSN 17 May 12 SECNAV INSTRUCTION E. From: Secretary of the Navy

Subj: ELECTRONIC WARFARE DATA AND REPROGRAMMABLE LIBRARY SUPPORT PROGRAM

Subj: RELEASE OF COMMUNICATIONS SECURITY MATERIAL TO U.S. INDUSTRIAL FIRMS UNDER CONTRACT TO THE DEPARTMENT OF THE NAVY

1. Purpose. To implement the guidance set forth in references (a) through (e) by:

OPNAVINST B N98 4 Jun 2018

OPNAVINST D N96 23 Jan Subj: SHIP ANTISUBMARINE WARFARE READINESS AND EFFECTIVENESS MEASURING PROGRAM

OPNAVINST G N09P 17 Jul Subj: MISSION, FUNCTIONS, AND TASKS OF THE BOARD OF INSPECTION AND SURVEY

OPNAVINST N2/N6 19 Aug 2014

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

Subj: MISSION, FUNCTIONS AND TASKS OF DIRECTOR, STRATEGIC SYSTEMS PROGRAMS, WASHINGTON NAVY YARD, WASHINGTON, DC

Subj: COMMUNICATIONS SECURITY (COMSEC) MONITORING OF NAVY TELECOMMUNICATIONS AND AUTOMATED INFORMATION SYSTEMS (AIS)

Subj: DEPARTMENT OF THE NAVY (DON) PERSONNEL SECURITY PROGRAM (PSP) INSTRUCTION

OPNAVINST E DNS-H 18 June 2012

Subj: IMPLEMENTATION OF THE DEFENSE STANDARDIZATION PROGRAM IN THE DEPARTMENT OF THE NAVY

OPNAVINST F N09D 2 JUL 2010

Subj: UNIFORM MATERIEL MOVEMENT AND ISSUE PRIORITY SYSTEM

OPNAVINST C N43 18 Jun Subj: NAVY EXPEDITIONARY TABLE OF ALLOWANCE AND ADVANCED BASE FUNCTIONAL COMPONENT POLICY

DEPARTMENT OF THE NAVY OFFICE OF THE SECRETARY 1000 NAVY PENTAGON WASHINGTON, DC

Subj: NAVY HEADQUARTERS CRISIS MANAGEMENT PROCEDURES AND ORGANIZATION. a. The clarification of Navy service watch cell and conditions I and II watch.

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

Subj: DEPARTMENT OF THE NAVY POLICY ON INSENSITIVE MUNITIONS

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

(c) DoD Instruction of 11 March 2014 (d) SECNAVINST D (e) CNO WASHINGTON DC Z Apr 11 (NAVADMIN 124/11)

Subj: IDENTIFICATION OF MAJOR PROGRAM MANAGER EQUIVALENT BILLETS

DEPARTMENT OF THE NAVY CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON DC

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC OPNAVINST DNS-3 11 Aug 2011

a. To promulgate policy on cost analysis throughout the Department of the Navy (DON).

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

OPNAVINST H N12 3 Sep 2015

DEPARTMENT OF THE NAVY OFFICE OF THE SECRETARY 1000 NAVY PENTAGON WASHINGTON, DC

DEPARTMENT OF THE NAVY CONTINUITY OF OPERATIONS (DON COOP) PROGRAM

PARTICIPATION IN THE GOVERNMENT-INDUSTRY DATA EXCHANGE PROGRAM (GIDEP)

MCO D C Sep 2008

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON DC

SECNAVINST F DNS Dec 2005

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

OPNAVINST C N2/N6 31 Mar Subj: UNITED STATES NAVAL COOPERATION AND GUIDANCE FOR SHIPPING

OPNAVINST D N4 24 May (a) OPNAV M , Naval Ordnance Management Policy Manual

DEPARTMENT OF THE NAVY OFFICE OF THE SECRETARY 1000 NAVY PENTAGON WASHINGTON, D.C

Subj: DEPARTMENT OF THE NAVY NUCLEAR WEAPON INCIDENT RESPONSE MANAGEMENT

a. Reference (a) and the provisions of this instruction will be implemented by OPNAV and all activities under the command of CNO.

Subj: MISSION, FUNCTIONS, AND TASKS OF THE BUREAU OF NAVAL PERSONNEL

CHANGES TO THE NAVY DIRECTIVES PROGRAM FOR ECHELON 2 DIRECTIVES CONTROL POINTS AND MANAGERS

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON DC

DEPARTMENT OF THE NAVY HEADQUARTERS UNITED STATES MARINE CORPS 3000 MARINE CORPS PENTAGON WASHINGTON, DC

Subj: MISSION, FUNCTIONS, AND TASKS OF COMMANDER, NAVAL INFORMATION FORCE RESERVE

OPNAVINST N46 21 Apr Subj: MISSION, FUNCTIONS, AND TASKS OF COMMANDER, NAVY INSTALLATIONS COMMAND

DEPARTMENT OF THE NAVY FOREIGN AREA OFFICER PROGRAMS

OPNAVINST C N4 31 May 2012

Subj: MISSION AND FUNCTIONS OF THE NAVAL SAFETY CENTER

Subj: NAVY ENTERPRISE TEST AND EVALUATION BOARD OF DIRECTORS

Subj: MISSION, FUNCTIONS, AND TASKS OF THE NAVAL EDUCATION AND TRAINING COMMAND

DEPARTMENT OF THE NAVY 0HICfOI 1111 CIIIEHII "\\\ \LOI'I RAIIO'I,\ N \\ \ 1'1 'T\C:O'I, \\ASIIIM:TOI\, DC ()

Ref: (a) DoD Instruction of 22 November 2011 (b) NTTP 1-15M (c) OPNAVINST H (d) CNO memo 1000 Ser N1/ of 24 Feb 09

1. Purpose. To define and implement a comprehensive approach to the conduct of force structure assessments.

OPNAVINST B N1/PERS-9 24 Oct 2013

OPNAVINST N9 16 Jun Subj: CHIEF OF NAVAL OPERATIONS SIMULATOR DEVELOPMENT AND TRAINING STRATEGY

DEPARTMENT OF THE NAVY COMMANDER, NAVY INSTALLATIONS COMMAND 716 SICARD STREET, SE, SUITE 1000 WASHINGTON NAVY YARD, DC

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC

OPNAVINST DNS 25 Apr Subj: MISSION, FUNCTIONS AND TASKS OF COMMANDER, NAVAL SUPPLY SYSTEMS COMMAND

MCO A C Apr Subj: ASSIGNMENT AND UTILIZATION OF CENTER FOR NAVAL ANALYSES (CNA) FIELD REPRESENTATIVES

DEPARTMENT OF THE NAVY OFFICE OF THE SECRETARY NAVY PENTAGON WASHINGTON DC

Subj: NAVY NUCLEAR COMMAND, CONTROL, AND COMMUNICATIONS EXECUTIVE STEERING COMMITTEE

Subj: NAVY DEFENSE SUPPORT OF CIVIL AUTHORITIES PROGRAM

Subj: APPROVAL PROCESS FOR PUBLIC RELEASE OF INFORMATION

Subj: OFFICE OF DIRECTOR OF NATIONAL INTELLIGENCE MILITARY FELLOWSHIP PROGRAM

a. To provide information, policy, and procedural guidance for U.S. Navy personnel

Subj: SELECTION OF THE COMMANDING OFFICER, U.S. NAVY BAND, WASHINGTON, DC

OPNAVINST D N1/CNRC 18 Nov 2014

Subj: IMPLEMENTATION OF THE DEPARTMENT OF THE NAVY (DON) SMALL BUSINESS INNOVATION RESEARCH (SBIR) PROGRAM

NAVY CONTINUITY OF OPERATIONS PROGRAM AND POLICY

Subj: OVERSIGHT OF THE DEPARTMENT OF THE NAVY MILITARY INTELLIGENCE PROGRAM

Subj: DEPARTMENT OF THE NAVY NUCLEAR WEAPONS RESPONSIBILITIES AND AUTHORITIES

DEPARTMENT OF THE NAVY HEADQUARTERS UNITED STATES MARINE CORPS 2 NAVY ANNEX WASHINGTON, DC MCO B C4I/CIC 21 Mar 96

Encl: (1) References (2) Department of the Navy Security Enterprise Governance (3) Senior Director for Security (4) Definitions (5) Responsibilities

OPNAVINST A N Oct 2014

OPNAVINST A N13 6 Dec Subj: LATERAL TRANSFER AND REDESIGNATION OF OFFICERS IN THE NAVY

NAVAL AVIATION SURVIVAL TRAINING PROGRAM DEVICES QUALITY ASSURANCE AND REVALIDATION POLICY

D E P A R T M E N T O F THE NAVY

OPNAVINST B N96 29 Jul 2014

OPNAVINST A N Jan 2015

Subj: ROLE AND RESPONSIBILITIES RELATED TO MEDICAL DEPARTMENT SPECIALTY LEADERS

Transcription:

DEPARTMENT OF THE NAVY OFFICE OF THE CHIEF OF NAVAL OPERATIONS 2000 NAVY PENTAGON WASHINGTON, DC 20350 2000 OPNAV INSTRUCTION 3880.6A N2 From: Chief of Naval Operations Subj: SCIENTIFIC AND TECHNICAL INTELLIGENCE LIAISON OFFICER (STILO) PROGRAM AND INTELLIGENCE SUPPORT FOR THE NAVAL RESEARCH, DEVELOPMENT, TEST & EVALUATION, AND ACQUISITION COMMUNITIES Ref: (a) Director of Central Intelligence Directive 6/6 (DCID), Security Controls on the Dissemination of Intelligence Information of 11 Jul 01 (NOTAL) (b) DOD 5105.21-M-1, Department Of Defense Sensitive Compartmented Information Administrative Security Manual, of Mar 95 (NOTAL) (c) SECNAVINST C4200.35 (NOTAL) (d) DOD 5220.22-M-Sup 1, National Industrial Security Program Operating Manual Supplement, of Feb 95 (e) NAVSEA ltr 5450 Ser 00U/02-014, University Affiliated Research Centers (UARCs) of 24 Jun 02 (NOTAL) (f) OPNAVINST 3811.1C (g) OPNAVINST S3882.2B (NOTAL) (h) Defense Intelligence Management Document, DOD-OOOO 151-94, Department of Defense Intelligence Production Program of Jul 94 (NOTAL) (i) SECNAV 5000.2C 1. Purpose a. To define objectives and scope of the STILO Program. b. To outline STILO Program responsibilities of the Director of Naval Intelligence (DNI) (Chief of Naval Operations (CNO) (N2)) and the Navy STILOs. 2. Cancellation. OPNAVINST 3880.6.

3. Background and Definitions a. The Naval acquisition community must have current, validated intelligence to support Naval program developments. The complexity and speed of technological developments demand the insertion of threat information at the earliest phase of the system development cycle. The cost and complexity of design, research, development, test, evaluation, procurement, installation, maintenance, and modification of modern Naval systems require continued intelligence support throughout the life cycle of those systems. The STILO Program is a "community of interest," specifically designed by the Navy to provide consistent intelligence support, liaison, and coordination among the acquisition, research, development, test, and evaluation (RDT&E) and intelligence communities. The program incorporates a wide range of collaborative techniques and methodologies to ensure effective interagency networking. Efficiencies are gained through identifying, sharing, leveraging, and expanding collaborative relationships and best practices between participating STILO activities. This instruction has been administratively revised and should be read in its entirety. b. The Commander, Office of Naval Intelligence (ONI) directs and coordinates much of the intelligence collection, production, and dissemination to satisfy Navy intelligence information requirements. c. The STILO acronym was selected to reflect the strong reliance of the RDT&E community upon scientific and technical (S&T) intelligence support. Increasingly, that support has diversified to encompass a broader spectrum of intelligence requirements which goes well beyond traditional S&T intelligence boundaries. The STILO designation has been retained because its brand name recognition is a valuable asset in the business of obtaining intelligence support. d. The STILO Program was established in 1970 to strengthen the interface and flow of intelligence between the intelligence community (IC) and non-ic Navy components that require intelligence support. The long history of the program has resulted in mature and trusted relationships within the acquisition, Naval laboratory, academic, and intelligence communities. The primary STILO objectives are: (1) To channel and expedite intelligence flow from the IC to Navy acquisition and RDT&E activities in a manner that consistently satisfies program requirements; 2

(2) To reduce duplication of effort among STILO participants and the IC; (3) To establish a method for Navy acquisition and RDT&E activities to access experienced intelligence professionals as primary points of contact for intelligence matters within those activities; (4) To develop a partnership for the sharing of technical information and expertise between the national IC and Navy RDT&E centers; and (5) To ensure that security concerns regarding "need to know" are satisfied in accordance with reference (a). The STILO at an activity may also serve as the activity's Senior Intelligence Officer (SIO) as described in reference (b). 4. Scope a. The STILO Program is designed to support the intelligence needs of the Navy's acquisition community, including the systems commands, Program Executive Offices (PEOs), warfare centers, systems centers, and their RDT&E field activities. b. Naval systems commands, RDT&E Centers, and Laboratories which participate in the Navy's STILO Program shall designate STILOs and provide essential resources and facilities. STILO Program funding and billet management are the responsibility of the parent activities. These STILOs serve as the single point of contact for obtaining threat intelligence to support their activity's requirements. The STILO Program is in consonance with and facilitates the execution of reference (c). c. Participation in the Navy's STILO Program is extended to select university Affiliated Research Centers (UARCs), through Commander, Naval Sea Systems Command (COMNAVSEASYSCOM) sponsorship. Reference (d) provides enhanced security requirements, procedures, and provisions that apply to UARC STILO activities. UARCs operate under a COMNAVSEASYSCOM contract. The COMNAVSEASYSCOM STILO office will validate the intelligence-related requirements of UARC STILO offices as outlined in reference (e). 5. Responsibilities 3

a. The DNI (CNO(N2)) is responsible for overall policy direction and coordination of the Navy STILO Program. b. STILO Program funding and billet management responsibilities are determined and executed by the parent command and funded with CNO resources, with the exception of the ONI STILO. The ONI STILO acts as the Program Coordinator and is funded out of General Defense Intelligence Program funds. c. ONI fulfills the STILO Program coordination responsibility for the DNI. The ONI STILO is responsible for the day-to-day operations and coordination with the STILO offices. Specifically, the ONI STILO will: (1) Be proactive in facilitating a robust intelligence sharing network. Coordinate intelligence support to, and information sharing within, the STILO community to ensure consistent, effective intelligence support to the Navy acquisition and RDT&E community; (2) Serve as the primary point of contact between the Navy acquisition and RDT&E activities and the IC; (3) Coordinate products and activities among STILO organizations that share common interests; (4) Conduct STILO conferences (at least annually) to assure effective program management and currency of intelligence available to STILOs; and (5) Coordinate with acquisition and RDT&E community STILOs to obtain technical and engineering assistance for the IC when required. d. Naval Systems Commands, RDT&E Centers, and Laboratories that participate in the Navy's STILO Program shall designate STILOs and provide essential resources and facilities. The STILO function should be established at the staff level with direct access to the commander/technical director for intelligence policy matters. The designated STILO shall be aware of planned and ongoing command programs and projects to ensure they receive appropriate intelligence support. The STILO shall be alert to applicable intelligence already available, establish requirements for that which is not available, and be aggressive in the pursuit of both. Specifically, and as 4

described by the threat support responsibilities identified in reference (f), the STILO shall: (1) Keep the commanding officer or activity director informed of intelligence and technological developments that impact on the command's mission and assigned programs and projects. STILOs should be given an appropriate level of access to special access programs at their activities to ensure adequate intelligence support is provided to these programs; (2) Exercise overall management of Sensitive Compartmented Information (SCI) programs and that portion of the Defense Special Security System (DSSS) under the SIO's security cognizance; execute other SIO duties as described in reference (b) ; (3) Maintain a current file of intelligence requirements pertaining to activity acquisition programs and RDT&E projects; (4) Ensure Navy systems development and acquisition programs consider and use valid, current intelligence appropriate to their programs; (5) Review proposed technical approaches, technical development plans, and/or test plans for appropriate and adequate intelligence input; (6) Coordinate the submission of requests for threat support, intelligence Production Requirements (PRs), and statements of intelligence interest (SIIs); (7) Assure compliance with restrictions on use of contractor-produced threat assessments in development and acquisition efforts in accordance with reference (f); assist command program/project managers in identifying required contractor intelligence support; (8) Prior to execution of any contract DD Form 254 which shows a "yes" in block 10e(1) for SCI, coordinate with the sponsor's SCI Information Security Department to assure compliance with contracting procedures defined in reference (c). Review other DD Form 254 documents on a case-by-case basis to ensure appropriate intelligence support is considered; (9) Coordinate activity requirements for special intelligence billets and clearances with the Special Security 5

Officer; provide expertise and assistance when required to establish sensitive intelligence-related compartmented programs; (10) Assist the IC in obtaining technical expertise when requested; (11) Maintain liaison with the STILOs of other activities in the acquisition/rdt&e community and act as the primary point of contact with the IC; (12) Coordinate the command's involvement in foreign material acquisition and exploitation, including the submission of command/activity requirements for acquisition and exploitation. Reference (g) pertains; (13) Act as the primary command point of contact for the Foreign Military Intelligence Collection Activities (FORMICA) Program; (14) Serve as the activity's tasking authority for required intelligence and threat support; (15) Serve as the sole command/activity authority for tasking the IC (through ONI) for intelligence and threat support, including coordinating funding to support such tasking when ONI requires such funding. All requests for intelligence, unless signed by a flag officer or member of the Senior Executive Service, must be originated by the activity's STILO office or contain a statement that the activity's STILO has approved the request; and (16) Serve as the activity's point of contact for providing customer feedback to the IC, coordinating with endusers as necessary. 6. Procedures. Navy acquisition and RDT&E activities, through their STILOs, shall request intelligence support and conduct coordination and liaison with other intelligence organizations as outlined below. Prior to submitting a PR, the STILO is responsible for reviewing existing holdings and searching Intelink (SIPRNET and/or JWICS) to ensure new intelligence production is needed to fulfill a request for support. These procedures are not meant to inhibit routine, informal liaison and information exchange. a. Government STILOs should maintain a Community On-line Intelligence System for End Users and Managers (COLISEUM) 6

account; COLISEUM is the preferred method of assigning requirements. Requests for intelligence products should be submitted to the Navy Validation Office (VO) in the PR format described in reference (h). E-mail, electronic message, FAX, or mail should only be used if COLISEUM is not available. At a minimum, PRs are required for: (1) Requirements for mandatory threat assessment support to Navy systems development programs required by references (f) and (i); (2) Other requirements which will result in one-time or recurring publications; and (3) All requirements that will be satisfied by a Department of Defense (DoD) intelligence production center other than ONI. b. The Navy VO shall either: (1) Decide that an existing product will satisfy the customer's requirement, in which case the product will be ordered and delivered to the customer; or (2) Determine that new production is required, in which case the customer's draft PR will be submitted by the Vo as a validated PR to the DoD intelligence production center bestsuited to satisfy the customer's requirement. Reference (h) applies. c. Requests for ONI intelligence briefings should be directed to ONI tasking/operations via COLISEUM, e-mail, FAX, message, or mail. To ensure briefer availability and a clear understanding by ONI of the customer's requirement, precoordination with the pertinent analytical office within ONI is strongly encouraged. d. Intelligence collection requirements prepared in response to IC solicitations for use in time-sensitive collection will be forwarded to ONI Operations. e. visits by activity STILOs to ONI are encouraged. All visits, regardless of length, shall be coordinated in advance with the ONI STILO coordinator. f. visits to ONI by acquisition/rdt&e scientists and engineers are welcome but shall be coordinated with the activity 7

STILO, who will ensure that prospective visitors have already reviewed intelligence available locally and that the proposed visit is not duplicative of other ongoing efforts. The notification requirements described in paragraph 6e shall also apply to these visits. Professional contacts and relationships between ONI analysts and RDT&E personnel are strongly encouraged, provided the activity STILO is kept informed. This procedure should be followed regardless which organization (i.e., ONI or the RDT&E activity) initiated the contact or who benefits from the exchange(s). For long-term or ongoing projects, once initial contact has been coordinated through the activity STILO, follow-on visits pertaining to that specific project need not necessarily be coordinated through the STILO. g. In the spirit of paragraphs 6e and 6f, visits by ONI personnel to RDT&E field activities should be coordinated with the activity STILOs. h. Requests for liaison/visits by cleared personnel from Navy acquisition and RDT&E activities to other intelligence agencies, such as the National Security Agency or the Central Intelligence Agency, will be coordinated through the RDT&E center STILO office. i. Proposals for in-house or contractor studies and analyses on foreign threats or other intelligence-related subjects will be coordinated with the responsible service or agency authority. j. UARC participation in the STILO Program is sponsored by and subordinate to COMNAVSEASYSCOM. Accordingly, and as outlined in reference (e), UARC STILOs shall forward a copy of all requests for support to the COMNAVSEASYSCOM STILO office for endorsement. 7. Action. foregoing. Revise all directives at varlance with the 4#!:P:/ ~ Rear Admiral, U.S. Navy Director of Naval Intelligence Distribution: Electronic only, via Department of the Navy Issuances Website http://doni.daps.dla.mil 8