J-14_DRFP ICE Operating Environment.pdf

J-14.1

Attachment J-14

December 19, 2019

Integrated Collaborative Environment (ICE)

Operating Environment

J-14.2

Section I – Background/Overview: The Integrated Collaborative Environment (ICE) is a major tool for NASA’s Exploration Systems Development (ESD) programmatic management activities and allows identification, collection, analyses, and dissemination of data and information associated with the Agency’s goals and mission. ICE provides a secure data repository with the necessary access control for data protection in conjunction with a collaborative environment.

This enables real time decision-making relative to program and project deliverables. ICE is an integral component for decision support throughout the program and projects’ life cycles and is based on the availability of needed information to team members involved in decision making.

The ESD programs and projects will use ICE to facilitate effective feedback, efficient change management and rapid change propagation. ICE will also support a wide variety of other uses.

Some of these include: support for management reviews, support for minor and major design reviews, linking users of the tools, support to team meetings, issue recording, etc.

NASA is responsible for implementing ICE and has done so using a suite of commercial-off-the-shelf licensed software tools as the core elements of the solution. The ESD Chief Information Officer (CIO) organization manages authorization and authentication. Access control policies are developed and maintained by the ESD CIO organization and can be applied at the individual object level. All NASA sites and Contractors are expected to request and implement ICE licenses and to use the system as a collaboration tool with the ESD program and projects and as a source of all relevant data. The ESD program and projects will provide access and Contractor training personnel to a limited set of users from the Contractor. The Contractor must assess their participation to determine the number of personnel who will need access. As guidance, any individual that contributes to the process of defining, collaborating, reviewing, and delivering contributions to the Orion MPCV Program will need an ICE license. This includes both inter-company and intra-company collaborative activities. Additionally, other users may include many of the following persons involved in collaboration with other project element organizations, such as:

1. Procurement & Supplier Management Personnel

2. Engineers

3. IT Personnel

4. Manufacturing & Assembly Personnel

5. Administration

6. Simulation, Testing & Analysis Engineers

Data with restricted rights markings will be access controlled and disseminated in accordance with the contractually established agreements. ICE will use several levels of access controls to ensure security of sensitive data.

Section II – ESD ICE Data Requirements: The Contractor shall comply with the following requirements for making their data a part of the Integrated Collaborative Environment:

Data Access Requirements: The Contractor shall deliver the data to ESD using one of the following two options:

J-14.3

1) Use the ESD ICE directly to develop and manage Contractor data. The Contractor personnel will be provided licenses and access to the ICE environment and will do their day-to-day work in the ICE environment.

2) ICE access will be accomplished through the use of a credentialing mechanism mutually agreed upon by the Contractor and NASA. As stated previously, several levels of access controls will be used for security of sensitive data. As part of this architecture, ICE will communicate with the Contractor’s Information Technology (IT) systems via an integration broker (i.e. middleware technology)-to-integration broker communication.

The following is meant to be a representative, but not complete, list of the interactions which can occur between NASA’s ICE and the Contractor’s IT environment:

a. Services that update ICE with new/updated files, objects, and application activity.

b. Services that participate in, publish, and subscribe broker service.

c. Services that have a set of events that the integration broker responds to.

The Contractor shall work with NASA to develop a directory structure that addresses the needs of NASA program and project integration. This directory structure shall be documented in the Contractor Configuration Management Plan.

The Orion CIO organization will participate with the NASA sites and/or Contractors to coordinate and establish the integration with the Integrated Collaborative Environment.

ICE Tools: The ICE Architecture does not require the Contractor to use any particular set of tools; however, there are always questions as to what tools make up ICE. The following is provided to the Contractor for informational purposes:

Systems Engineering – Cradle Product Life Cycle Management – Windchill

a. CAD Data Management

b. Product Structure

Confluence Wiki

a. Configuration

b. Data

c. Document Management

d. Project Collaboration

Risk Management – Active Risk Manager (ARM) Earned Value Management – Primavera and wInsight Integrated Master Schedule/Integrated Master Plan – Microsoft Project MCAD – Pro/Engineer®

Licenses for Applications: The Contractor is responsible for acquiring their corporate licenses if they choose to set up a similar ICE Tools suite.

[End of Attachment]

Accessibility Report

Filename:

J-14_DRFP ICE Operating Environment.pdf

Report created by:

Organization:

[Enter personal and organization information through the Preferences > Identity dialog.]

Summary

The checker found no problems in this document.

Needs manual check: 1

Passed manually: 1

Failed manually: 0

Skipped: 1

Passed: 29

Failed: 0

Detailed Report

Document

Rule Name Status Description

Accessibility permission flag Passed Accessibility permission flag must be set

Image-only PDF Passed Document is not image-only PDF

Tagged PDF Passed Document is tagged PDF

Logical Reading Order Passed manually Document structure provides a logical reading order

Primary language Passed Text language is specified

Title Passed Document title is showing in title bar

Bookmarks Passed Bookmarks are present in large documents

Color contrast Needs manual check Document has appropriate color contrast

Page Content

Rule Name Status Description

Tagged content Passed All page content is tagged

Tagged annotations Passed All annotations are tagged

Tab order Passed Tab order is consistent with structure order

Character encoding Passed Reliable character encoding is provided

Tagged multimedia Passed All multimedia objects are tagged

Screen flicker Passed Page will not cause screen flicker

Scripts Passed No inaccessible scripts

Timed responses Passed Page does not require timed responses

Navigation links Passed Navigation links are not repetitive

Forms

Rule Name Status Description

Tagged form fields Passed All form fields are tagged

Field descriptions Passed All form fields have description

Alternate Text

Rule Name Status Description

Figures alternate text Passed Figures require alternate text

Nested alternate text Passed Alternate text that will never be read

Associated with content Passed Alternate text must be associated with some content

Hides annotation Passed Alternate text should not hide annotation

Other elements alternate text Passed Other elements that require alternate text

Tables

Rule Name Status Description

Rows Passed TR must be a child of Table, THead, TBody, or TFoot

TH and TD Passed TH and TD must be children of TR

Headers Passed Tables should have headers

Regularity Passed Tables must contain the same number of columns in each row and rows in each column

Summary Passed Tables must have a summary

Lists

Rule Name Status Description

List items Passed LI must be a child of L

Lbl and LBody Passed Lbl and LBody must be children of LI

Headings

Rule Name Status Description

Appropriate nesting Skipped Appropriate nesting

Back to Top