Reference: (a) ISS Memo CMS 96-00864 dtd 20 Dec 96, Subj: Intelink-S Task Force

1. In response to Community concerns with regard to Intelink-S, reference (a) tasked the Commands, Services, and National Intelligence Agencies and Production Centers to participate in an Intelink-S Task Force to develop a corrective plan of action and an implementation schedule for correcting Intelink-S shortfalls. Task force participants were provided a questionnaire for surveying their user-base and provided responses to the Intelink Management Office (IMO) Information Management Directorate (IMD) in preparation for a 4-6 March 1997 task force meeting in Colorado Springs. Meeting participants are listed at enclosure (1). Corrective action implementation dates are discussed below and depicted in enclosure (2). Enclosure (3) is the revised task force effort schedule. NOTE: Implementation dates discussed below are goals agreed to by Intelink-S Task Force meeting attendees. Organizations unable to comply with these target dates are requested to provide their proposed timeline for meeting Intelink requirements/standards to the IMO/IMD.

2. Following informational briefings provided by IMO/IMD (NRAD), IMO/ISMC, and TRANSCOM task force members, primary Intelink-S problem areas, based on survey responses and previous Intelink conference results, were addressed in four separate groups. The task force, however, agreed that most of the problem areas identified in Intelink-S were duplicate of overall Intelink problems and the following decisions/solutions should apply across the board. Each group drafted a corrective plan of action and schedule for discussion among the overall task force. Listed below are the groups and detailed explanations of task force results/decisions:

a. Group 1: PROCEDURES FOR MOVING PRODUCTS FROM INTELINK-SCI TO INTELINK-S: This discussion generated several questions regarding security procedures/accreditation. The task force unanimously agreed that the IMO Security Policy and Plans Directorate must be staffed ASAP and an Intelink-S Security Policy written. In order to facilitate passing of collateral products from Intelink-SCI to Intelink-S, the Security Directorate must provide guidance/input in developing a plan for approved passing methodologies. As an interim, the following guidelines will be enforced across all Intelink-S production centers:

- Organizations that are not currently moving data from Intelink-SCI to Intelink-S must develop a locally approved plan to do so by 1 June 1997.

- Organizations will set a goal to move/post collateral products to Intelink-S on a daily basis beginning 15 June 1997 for new products. Products posted prior to 15 June 1997 will be passed to Intelink-S as resources permit. The IMO/IMD will provide assistance as available. In the process of moving collateral information, producers must ensure its accessibility in Intelink-S (e.g. No broken links).

- The IMO agreed to have a Intelligence Community-Wide plan in place by 1 July 1997 to address policy and guidelines with regard to moving products to Intelink-S. The IMO Security Policy and Plans Directorate will lead this effort. Task Force members were asked to investigate local solutions that could be of benefit to other organizations. NGIC's solution is posted at: http://www.ngic.ic.gov/spprojects/projects.index, then click on "Special Projects and Services: Product Migration". Actual address is http://www.ngic.ic.gov/support/productmigrate/title.html.

- Format Standards: The current HTML 2.0 minimum standard will be modified to HTML 3.2 effective 1 October 1997. Producers are responsible for posting products in HTML 3.2 first and then any other format in addition to HTML 3.2 is acceptable. HTML-wrapped Adobe 3.0 (PDF) products are acceptable as meeting the minimum standard. The Intelink user community is required to acquire HTML 3.2 compliant browsers. Browsers should be PDF compatible. PDF readers can be provided by the ISMC at no charge. Organizations must ensure they have HTML 3.2 browsers and PDF readers by 1 October 1997.

b. Group 2: METADATA STANDARDS: In response to user needs for improving the ability to locate new and archived information and increased confidence in search results, the task force agreed to implement/enforce the utility of the previously approved core set of metadata fields by 15 April 1997 for new products. Producers will be responsible for populating the following set of metadata fields identified as core (mandatory) fields when posting products: Product Title, Product Security Classification, Descriptive Product Keywords, Producing Agency, Date of Information (ICOD), Intelink Posting Date, Object Type, Country. By 1 April 1997, the IMD will have completed an assessment of acceptable "keywords" and develop an initial list of keywords for the 15 April 97 implementation. This list of keywords will evolve/change as requirements dictate. Additionally, producers are strongly encouraged to use the following optional set of metadata fields as well: Office of Primary Responsibility/Point of Contact, Product Summary, Product ID, Uniform Resource Locator (URL), Content Type, Product Subject, Geographic Reference. The IMD agreed to assess the status of metadata issues from the October 1996 Intelink Users and Producers Conference by 1 April 1997. By 10 April 1997, the IMD will have developed a streamlined process using templates. The production centers will be responsible for the enforcement of metadata use and will provide progress reports to the IMO/IMD beginning 1 May 1997.

c. Group 3: HOME PAGE/PRODUCT STANDARDS: Customers require an improved ability to locate data while browsing the information space. While every organization has a different approach to providing information and navigational aids to their customers, a standard set of categories for listing information will help in discovery/retrieval and in the building/maintenance of topical/regional pages by various organizations (e.g. PACOM-managed page of reporting on Korea). Additionally, a standard set of navigational aids will ensure that customers entering an information space via search engines will have the ability to scroll within sight for other products (e.g. Get to like products or move to home page). The implementation of metadata is critical to the ease of locating information. In response to collateral customer's requirements for a product similar to the DIA Register of Intelligence Products (RIP), metadata will also facilitate the ability to provide such a product. The task force is mandating the below list of minimum standards, however, organizations may impose additional requirements. The following standards apply:

- Home Page Standards: The current minimum home page standards remain in effect and require that the following information be included: Classification, Security/Monitoring Banner, Organization Identifier, Mission Statement/Link (Intro to Organization), POC List/Link (ISSO, System Admin, Intelink Site Information Manager, 24-hour desk), Link to Intelink Central, Navigator to Products/Information (Table of Contents). By 1 June 1997, home pages will comply with the standard.

- Product Page Standards: The standards agreed to for minimum information required on product pages is mandated for implementation by 1 June 1997. Product pages must include a backlink to Table of Contents (TOC) pages, information POC (name, office, phone number), classification and declassification instructions, and must conform to legal and security requirements [DCID].

Product pages posted after 1 June 1997 must conform to these standards. Organizations will make a determination for their ability to conform to standard for those products posted prior to 1 June 1997.

- TOC Page Standards: Table of Contents pages must include a backlink to home organization and higher level TOC pages, and classification markings in accordance with security requirements/policies. TOC pages posted after 1 June 1997 must conform to these standards. Organizations will make a determination for their ability to conform to standards for those products posted prior to 1 June 1997.

As a result of questionnaire responses and task force discussions, it was determined the best compromise to organizing information was to have producers provide data by a number of categories (country/region, topic/issue, product line, chronological, organization structure).

The concept of "centralized" pages to avoid organization format was discussed, however, questions of who maintains, how to link, etc., make this issue too complicated to resolve at this time. The interim solution is for producers to register their product holdings with Wer'zit.

The IMD agreed to provide information on standards guidance and a schedule for when new standards will become valid. Organizations need to know what and when to plan for in order to acquire necessary hardware/software.

d. Group 4: TECHNOLOGY INTEGRATION: The task force established the World Wide Web Council (W3C) published guidelines as the minimum standards for web-based material (i.e. HTML standards). This allows for both the adoption of standards which the survey responses called for and allows for impartiality in deciding when HTML standards should be modified. The IMO/ISMC will seek funding to "level the playing field" to the HTML 3.2 standard by investigating the feasibility of purchasing HTML 3.2 compliant browsers for those organizations which do not currently have it. Plans will be discussed with DISA. Target date to acquire browsers is 1 October 1997.

The task force mandates that organizations index their individual servers every 24 hours. Indexing will allow standardization of searches and currency of search results. Systems administrators should contact the ISMC to discuss options for indexing (Harvest, Retrieval Ware, etc.) and then establish indexing on their servers. Indexing procedures are required to be in place at each organization by 1 July 1997.

To further improve standardization searches and currency of search results, producers must register their topical page holdings with Wer'zit and provide a link to the product. Target date to do so is 1 July 1997. ISMC will provide assistance if necessary. Producers should also determine their feasibility for acquiring Wer'zit locally by 1 July 1997. The IMO/IMD will investigate the advantages of registering topical page holdings vice whole products with Wer'zit. Additionally, for categories not currently supported in Wer'zit, the ISMC has agreed to work with the Intelligence Community Librarians Committee (ICLC) to reach agreement on adoption of the categories.

3. TRAINING AND EDUCATION: The IMD agreed to draft and coordinate a comprehensive training management plan by 1st quarter FY98. It will investigate the JITAP computer-based training (CBT), FITCPAC CBT and identify other existing training programs for possible application throughout the Intelink community. In the event existing training programs prove to be insufficient in satisfying user requirements, the IMD has agreed to seek funding for an FY98 training development program. As requested during the October 1996 Intelink Users and Producers Conference, a topical page to address Intelink training will be created by 15 May 97.

4. TASK FORCE RECOMMENDATIONS:

a. RESOURCES: That Intelink-S sites appropriately resource Intelink-S in terms of manpower and funding. Appropriate level to be defined by each site, but at a minimum to ensure implementation of task force recommendations and IAW the implementation dates recommended.

b. BANDWIDTH: The ISS agreed to take up issues of increasing bandwidth for Intelink (i.e. SIPRNET) with NSA/TELMO, DISA, and JIVA/PMO. ISS will prepare a report for incorporation into SIM panel briefing for 13 May 1997.

5. TASK FORCE CHAIR ACTIONS:

a. Chair noted that IMO Management Plan defined IMO managed Intelink services as the current Intelink-SCI, Intelink-S, Intelink-P and Intelink-U. Also noted that all plans for corrective action (with exception of procedures for posting products from Intelink-SCI to Intelink-S) plus timelines should apply to Intelink across the board. This was voted on and passed unanimously.

b. It was noted that Intelink-S Task Force was to be conducted over period of 90 days beginning 15 January. This was extended for another 90 days to 15 July 1997 to permit additional time for implementation of task force actions.

c. Task force minutes and briefing to be posted on Intelink (IMD Home page) and message sent to Intelink sites NLT 1 April 1997.

d. Briefings to be given to IMG, SIM Panel, Director, DIA, and DASD for Intelligence and Security by IMO. Participants were tasked to schedule similar briefings throughout their Agencies/Commands during first 2 weeks of April 1997.

As a result of the Intelink-S Task Force meeting, the following goals should apply to all Intelink services (-SCI, -S, -P, -U). For further explanation, see Report on Intelink-S Task Force Meeting.

1 April 1997:

-IMO/IMD completed assessment of keywords and list developed for metadata implementation.

-IMO/IMD assess metadata issues from October 1996 Intelink Users and Producers Conference.

10 April 1997:

-IMO/IMD streamlined metadata process through the use of templates.

15 April 1997:

-Implement/Enforce use of metadata core set.

1 May 1997:

-Producers responsible for enforcing metadata use and first progress report due to the IMO/IMD.

13 May 1997:

-ISS prepared/incorporated input to SIM briefing re: increasing Intelink-S bandwidth.

15 May 1997:

-IMO/IMD create a topical page to address Intelink training.

1 June 1997:

-Locally approved plans for moving data from Intelink-SCI to Intelink-S from organizations not

currently doing so.

-Home pages comply with home page standards.

-Implementation of Product page standards.

-Implementation of TOC page standards.

15 June 1997:

-Organizations begin moving/posting collateral products to Intelink-S on daily basis.

1 July 1997:

-IMO/SPPD IC-wide plan which addresses policy/guidelines for moving products to Intelink-S.

-Organizations required to begin indexing their servers every 24 hours. Contact ISMC for options.

-Producers required to register topical pages in Wer'zit with a link to product, and investigate the

feasibility of acquiring Wer'zit locally.

-IMO/IMD will investigate the advantages of registering topical pages in Wer'zit vice products.

1 October 1997:

-Implement HTML 3.2 as minimum standard vice HTML 2.0.

-User community have HTML 3.2 compliant browsers and PDF readers.

1st Quarter FY98:

-IMD draft and coordinate comprehensive training management plan.

ENCLOSURE (2)

20 December 1996:

-ISS Memorandum requesting Intelink-S Task Force participants.

15 January 1997:

-Commence date for Intelink-S Task Force.

4 February 1997:

-Intelink-S Task Force Questionnaire forwarded to participants.

20 February 1997:

-Questionnaire responses due to IMO/IMD.

4-6 March 1997:

-Intelink-S Task Force Meeting - Colorado Springs, CO.

14 March 1997:

-Complete review of meeting results and draft Intelink-S Corrective Action Plan.

1 April 1997:

-Intelink-S Task Force corrective action plan, schedule, and briefing available on Intelink(s) and

message released.

2-18 April 1997:

-Task force participants brief their organization's leadership.

18 April 1997:

-In response to message, impact statements re: implementation of corrective actions due from

community.

13 May 1997:

-Progress report to the SIM panel (w/ ISS input re: bandwidth).

15 July 1997:

-Intelink-S Task Force completion.

ENCLOSURE (3)