-------------- ------------------------------------------------------------------ ------------
  **8**          **Information Technology**                                         **C8, 1**

                                                                                    

  **8.1**        **General Information**                                            **C8, 1**

  8.1.1          Annex Description ........................................         C8, 1

  8.1.2          Information Technology Systems ....................                C8, 1

  8.1.3          Special Rights For Licensed Software ..............                C8, 1

  8.1.4          Hardware Configuration ................................            C8, 1

  8.1.5          Government-provided Computer Services .........                    C8, 1

  8.1.6          Workstation Hardware and Software Audits/Push, Pull or Automatic   C8, 1
                 Updates of Software ..............                                 

  8.1.7          Standard Software Installation/Usage ...............               C8, 2

  8.1.8          Network Connections ....................................           C8, 2

  8.1.9          Server-based Storage ...................................           C8, 2

  8.1.9.1        Server-based Storage for General Use Applications                  C8, 2
                 ................................................                   

  8.1.9.2        Server-based Storage for General Web Applications                  C8, 2
                 ................................................                   

  8.1.9.3        Maintenance (clean up and removal of old files) /usage             C8, 2
                 ........................................................           

  8.1.10         Printer Support ............................................       C8, 2

  8.1.10.1       Networked Laser/Mainframe Laser/Impact Printers                    C8, 2

  8.1.10.2       Contractor Provided Printer Supplies ............                  C8, 2

  8.1.11         Data Integrity ...............................................     C8, 2

  8.1.12         Building Number Standard ........................\....             C8, 3

                                                                                    

  **8.2**        **Main Frame Application Support**                                 **C8, 4**

                                                                                    

  **8.3**        **Computerized Maintenance Management System**                     **C8, 4**

  8.3.1          Provide IT Support for the CMMS .....................              C8, 4

  8.3.2          CMMS Capability ..................... .......................      C8, 4

  8.3.3          Maintain the CMMS ......................................           C8, 5

  8.3.4          Maintain History Files ...................................         C8, 6

                                                                                    

  **8.4**        **Environmental Management IT Support**                            **C8, 6**

                                                                                    

  **8.5**        **Energy Management Control System (EMCS) System Support**         **C8, 7**

                                                                                    

  **8.6**        **System Operations/Maintenance**                                  **C8, 8**

                                                                                    

  **8.7**        **Online System Access And Support**                               **C8, 8**

  8.7.1          Provide and Maintain Government Access............                 C8, 8

  8.7.2          Web Based Management Information System.......                     C8, 9

                                                                                    

  **8.8**        **Facility Cad System/Space Utilization**                          **C8, 9**

  8.8.1          CAD Software Support ..................................            C8, 9

  8.8.2          CAD Software Licenses .................................            C8, 9

  8.8.3          CGM Viewing Support/Facility Drawing Database...                   C8, 10

  8.8.4          Space Utilization Management System Programming Support Data Entry C8, 10
                 ....................                                               

                                                                                    

  **8.9**        **Other Applications**                                             **C8, 10**

  8.9.1          Gas Cylinder Tracking System ........................              C8, 10

  8.9.2          Barcode Scanners/Support ............................              C8, 11

  8.9.3          Thermography Data .....................................            C8, 11

  8.9.4          Vibration Data .............................................       C8, 11

  8.9.5          Real Property Database ................................            C8, 12

  8.9.6          WinEst/Means.... ............................................      C8, 12

                                                                                    

  **8.10**       **NEMS Scanning System**                                           **C8, 12**

                                                                                    

  **8.11**       **IT Security.................................................**   **C8, 12**

  8.11.1         Computer Systems and Data Security.. ...............               C8, 13

  8.11.2         Computer Security Manager ...........................              C8, 13

  8.11.3         Computer System Administrator Certification                        C8, 14

                                                                                    

  **8.12**       **Documentation/It Help Support........... .............**         **C8, 13**

  8.12.1         IT Help Support ...........................................        C8, 13

  8.12.2         Documentation Maintenance / Update for Major                       C8, 14
                 System..........................................................   

  8.12.3         Documentation, Minor Systems ......................                C8, 15

  8.12.4         Documentation, Minor Applications ..................               C8, 15

                                                                                    

  **8.13**       **Records, Reports And Submittals**                                **C8, 15**

  8.13.1         Provide IT Security Plan                                           C8, 15

                                                                                    

  **TABLE 8-1**  **CMMS Specified Field Definitions.....................**          **C8, 16**

  **TABLE 8-2**  **CMMS Management Information System...........**                  **C8, 18**
  -------------- ------------------------------------------------------------------ ------------

**8.0 INFORMATION TECHNOLOGY**

**8.1 GENERAL INFORMATION**

**8.1.1 Annex Description**

This Annex identifies the Information Technology Support Services that
cannot be identified with a single annex or may be related to the
performance of services throughout this Contract. Even though this Annex
contains certain guidelines, the Contractor has the responsibility to
establish a management program that is effective, innovative, and uses
to full advantage the facilities and equipment provided by the
Government.

**8.1.2 Information Technology Systems**

It is at the discretion of the Contractor to utilize the
Government-provided systems or to initiate new systems for the purpose
of increasing efficiency and to meet contract requirements. However, the
new systems must parallel and act in the same manner as the
Government-provided systems. If the Contractor proposes to deviate from
the existing systems, including workstations (CLIN 8.1.5), all proposals
shall be submitted in writing, through the Information Technology
Technical Management Representative (**\*TMR**), for approval prior to
implementation. (NOTE: The Government will normally provide a response
within 10 working days. Rationale will be provided for any request that
is \"disapproved\"). If the contractor elects to provide a new system
rather than use the existing Government system, the new system will
become the property of the Government, however, if the software /
hardware is leased, it will be the responsibility of the contractor to
prepay the lease, including technical support, for one year after the
end of this contract.

**8.1.3 Special Rights For Licensed Software**

In the event the Contractor uses licensed software, the Contractor is
required to prepay a license, including technical support, for
Government use, for 1 year beyond the end of the Contract.

**8.1.4 Hardware Configuration**

**GENERAL**: The Information Technology (IT) System consists of:

(1) Installation-provided hardware

(2) A computer room with 24-hour cooling and adjacent office space is
    included as part of the space provided to the contractor.

(3) A JSC Institutional Network System (INS) linking all onsite computer
    systems via Ethernet with 100 Base-T cabling, site PCs have 10/100
    base cards. The site backbone is being upgraded for higher bandwidth
    and over time the routers / concentrators are being replaced. This
    is a multi-year effort and will generally be completed in areas with
    higher population first.

(4) Installation-provided off-the-shelf programming software (some
    contractor maintained and / or upgraded).

(5) Installation-provided systems, which include programs, databases,
    on-line systems and report generating programs (some contractor
    maintained and / or upgraded).

(6) Contractor-provided systems.

(7) IT Hardware

(8) Installation operated Web Based Applications.

These Installation-provided systems are integrated with and necessary
for the performance of the overall contract. See Section J, Attachments
I and K, for a listing of Installation-provided hardware, off-the-shelf
programming software and systems. The Government does not warrant that
the equipment as currently configured is optimal for the needs of this
contract. The contractor may modify the configuration of this equipment
to meet the needs of this contract except for the workstations in CLIN
8.1.5.

5.  **Government-provided Computer Services**

The Government will provide computer services up to 228 seats
(workstations) including monitors, keyboards, CDROM, mice, and network
cards. These services are equivalent to those provided for Civil
Servants. The service provides for workstations to be refreshed on a
three-year cycle, loaded with a recent version of a Windows based
operating system and a standard version of Microsoft Office, antivirus
software, and various viewers. These workstations will be upgraded to
more current operating system versions, as the Government deems
necessary. The Contractor will provide any miscellaneous hardware over
and above what is provided with a standard seat. The contractor shall
provide any workstations required above the quantity listed above.

NOTE: The Government will provide the network connection for each
contractor PC. The contractor may purchase from the Government
additional services at the same delta cost above the Government network
cost. The Government cost for a seat and for a Network connections are
documented catalog prices in a Seat Contract (known as Outsourcing
Desktop Initiative for NASA (ODIN). Many items from the Seat contractor
remain the property of the Seat contractor and as such will not become
the property of the COSS contractor.

NOTE: The Government provided workstations will come with software
indicated above and 8.1.7 Standard Software Installation / Usage. Some
software like the 3270 emulation is only needed on a few of the
contractor workstations that support the NEMS, NSMS, and NPDMS
applications on the IBM Mainframes. The Contractor is responsible for
loading this Government provided software or Contractor provided
software on Contractor User Workstations.

6.  **Workstation Hardware and Software Audits / Push, Pull or Automatic
    updates of software.**

The Government uses an automated electronic equipment auditing system of
all computer workstations (hardware and software) connected to the
network. The Contractor will be provided access to the data for their
computer workstations. The Government also uses an automated process to
push, pull, or do automatic upgrades to workstations. For example, the
Government does automatic periodic upgrades of the virus definitions.
The contractor will cooperate with the Government for the upgrades and
audits.

7.  **Standard Software Installation / Usage**

Use software that is compatible with the Center standard (type and
version) to permit the flow of information back and forth with other COD
elements with minimal impact. Use a software load on the computer
workstations that is compatible with the software used by other COD
elements.

NOTE: Each of the existing user computer workstations is configured with
the Center standard software, including a recent version of Microsoft
Windows with access to the server-based administrative applications
(Microsoft Office, Web Browsers), the Center Electronic Mail System,
News Readers, and 3270 emulators (where applicable). Where necessary a
project scheduler is also provided. . The Government will provide an
e-mail account for contractor personnel, as required.

NOTE: It is illegal to pirate software. Contractor personnel are not to
use the Government Internet system for non-Government-related business
or personal use.

8.  **Network Connections**

The Government will provide the network interface for all Government
provided and contractor provided workstations, with one exception. The
exception is that no workstations with modems will be connected to the
center network.

9.  **Server- based Storage**

    1.  **Server-based Storage for General Use Applications**

Government supplied space will be provided for server-based general use
applications and databases. The Government will perform administrative
functions for these servers. Reasonable amounts of storage will be
provided to the Contractor (equivalent to the same capability and
capacity provided to Civil Servants).

2.  **Server-base Storage for General Web Applications**

Space will be provided on Government servers for server-based Web
applications and databases. The Contractor is required to follow policy
guidelines including: NPG2801.1, Security of Information Technology, JPD
2800.4, IT Program Management, and JPD 2800.1A, JSC Information
Technology Policy. The Government will perform server administrative
functions for these servers. The contractor will be responsible for all
of the data / data input. Storage will be provided to the Contractor
(not to exceed 50 Meg).

3.  **Maintenance (clean up and removal of old files) / usage**

The contractor will cooperate with the Government to remove / archive
old files from Government supplied space that are needed only for
historical reasons. The intent is to provide reasonable storage, and yet
be able to enforce reasonable storage housekeeping rules**.** Server
space is provided to support necessary contractor operations, however,
the server storage is only to be used for current needs.

10. **Printer Support**

    1.  **Networked Laser/Mainframe Laser/ Impact Printers**

General use networked Black and White laser printers/impact printers
will be made available to the Contractor. These printers will be
maintained and replaced with current center standard equipment by the
Government as the printers become obsolete. The requirement for
providing Networked printers does not include any buildings / locations
where the total number of users in the area is 5 or less. For areas with
5 or less users, it will be the contractor's responsibility to provide
local direct connect or local shared printers.

Any additional printers will be the responsibility of the Contractor.
The Contractor is responsible for all CMMS networked impact printers /
special printers / special use (personnel, payroll, etc. where privacy
concerns might preclude the use of network printers by other users).

NEMS, NPDMS, and NSMS use mainframe impact or laser printers for
reports. The Government will provide printers for these purposes where
Networked General use printers are not appropriate.

2.  **Contractor provided printer supplies**

Provide all printer consumables (toner, inkjet ink, ribbons, paper,
etc.). The consumables shall be compatible with the printers.

11. **Data Integrity**

Design and maintain databases to have data field integrity. This
requires that the field used is the right type (i.e. numbers for number
fields, dates for date fields, etc.). Text fields shall not be used for
fields that should be another type to maintain data integrity.

Ensure all data entered into the system is appropriate, accurate, and
current. Provide accurate data input. The highly desired User Input
method is for the database to restrict related data to predetermined
values. Where this is not appropriate, the contractor will incorporate
quality processes to identify errors. All errors whether found by the
contractor or the Government will be corrected by the contractor.

12. **Building Number Standard**

Maintain building data integrity in all databases by using a standard
method to reference buildings. The contractor must use the building
numbers as specified by the Government.

Buildings shall be related in the database(s) structure using a 7
character fixed length designation. Examples are as follow:

J\*001\*\*

J\*009NW

JT585\*\*

E\*990\*\*

S\*920L\*

NOTE: The first character represents the site "J" for Johnson Space
Center, "E" for Ellington Field, and "S" for the Sonny Carter Training
Facility at Ellington Field. The second character represents the
building Prefix with "T" for Temporary and an "\*" for "No Prefix".
Characters 3, 4, and 5 are the building number with leading zeros to pad
the data. The last two characters are the suffix with "\*\*" as "no
suffix" for the character spacing and either on suffix followed by an
"\*" or a two letter suffix. It is intended that the users will see the
generic number for a building (example 1, 2, 3, 4S, 11, 30S).

+------+--------------+----------------------------+------+----------+
| **8  | **Main Frame |                            |      |          |
| .2** | Application  |                            |      |          |
|      | Support**    |                            |      |          |
+------+--------------+----------------------------+------+----------+
|      | Provide IT   | > Provide IT support for   | 365  | Age      |
|      | Support for  | > the Government furnished | days | ncy-wide |
|      | the          | > systems described in     |      | appl     |
|      | Governme     | > Section J Attachment I   |      | ications |
|      | nt-furnished | > and K. Use NASA          |      | are used |
|      | IT Systems.  | > agency-wide              |      | excl     |
|      |              | > applications, including  |      | usively. |
|      |              | > NEMS, NSMS, and NPDMS.   |      |          |
|      |              | >                          |      |          |
|      |              | > Ensure that data entered |      |          |
|      |              | > into the systems are     |      |          |
|      |              | > appropriate, accurate,   |      |          |
|      |              | > and current.             |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | Call the ISD helpdesk when |      |          |
|      |              | there is a system access   |      |          |
|      |              | problem. Advise the IT     |      |          |
|      |              | **\*TMR** if there are     |      |          |
|      |              | repeated breakdowns or the |      |          |
|      |              | system has an unscheduled  |      |          |
|      |              | outage of more than 4      |      |          |
|      |              | hours.                     |      |          |
+------+--------------+----------------------------+------+----------+
| **8  | **           |                            |      |          |
| .3** | Computerized |                            |      |          |
|      | Maintenance  |                            |      |          |
|      | Management   |                            |      |          |
|      | System**     |                            |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | Provide IT   | Provide IT support for the | 365  | CMMS is  |
| .3.1 | support for  | CMMS system. Maintain,     | days | fully    |
|      | the CMMS     | control and protect        |      | fu       |
|      |              | \"key\" data/information   |      | nctional |
|      | Accurately   | to ensure the integrity of |      | and data |
|      | track and    | the CMMS program. These    |      | is       |
|      | document all | data will include Master   |      | accurate |
|      | contract     | Equipment Inventory,       |      |          |
|      | work.        | Preventive and Predictive  |      | Training |
|      |              | data, task, the Work       |      | for      |
|      |              | Element Codes, criticality |      | Go       |
|      |              | code, the schedule dates,  |      | vernment |
|      |              | start dates, completed     |      | e        |
|      |              | dates, **\*total cost**,   |      | mployees |
|      |              | **\*bare cost,**           |      | is       |
|      |              | maintenance, and other     |      | a        |
|      |              | current data in fields of  |      | vailable |
|      |              | the database (see DRD      |      | when     |
|      |              | AN-1-10 for scope of this  |      | r        |
|      |              | data). Write reports,      |      | equested |
|      |              | query the databases,       |      |          |
|      |              | perform quality checks,    |      | CMMS     |
|      |              | and trouble shoot database |      | acces    |
|      |              | problems.                  |      | sibility |
|      |              |                            |      | to       |
|      |              | Provide routine IT support |      | co       |
|      |              | and training to Government |      | ntractor |
|      |              | employees that need to use |      | operated |
|      |              | the CMMS Data.             |      | systems. |
|      |              |                            |      |          |
|      |              | Maintain a set of user     |      | Backups  |
|      |              | manuals (and/or equivalent |      | are      |
|      |              | on-line help) in the       |      | p        |
|      |              | Facility Technical         |      | erformed |
|      |              | Reference Library (TRL).   |      | daily.   |
|      |              |                            |      |          |
|      |              | Provide software utilities |      |          |
|      |              | to permit the Government   |      |          |
|      |              | to export data to Excel,   |      |          |
|      |              | Access, CSV, TSV, etc.     |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | Using the CMMS Program,    |      |          |
|      |              | provide **\*daily (D7)**   |      |          |
|      |              | reports in electronic web  |      |          |
|      |              | based format for work      |      |          |
|      |              | schedules, including       |      |          |
|      |              | scheduled maintenance,     |      |          |
|      |              | repair, construction, and  |      |          |
|      |              | outages. Query and         |      |          |
|      |              | reporting shall have, at a |      |          |
|      |              | minimum the capabilities   |      |          |
|      |              | as the **\*\*Building      |      |          |
|      |              | Maintenance and Repair     |      |          |
|      |              | Report** search on the     |      |          |
|      |              | current COD homepage.      |      |          |
|      |              |                            |      |          |
|      |              | Upon breakdowns, advise    |      |          |
|      |              | the IT **\*TMR** of all    |      |          |
|      |              | scheduled actions to bring |      |          |
|      |              | the system back on-line.   |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | CMMS         | Provide a CMMS capability  | 365  | CMMS     |
| .3.2 | Capability   | that includes all          | days | system   |
|      |              | hardware, software and     |      | fully    |
|      |              | software provider's        |      | ope      |
|      |              | technical support          |      | rational |
|      |              | capability. This system    |      | at start |
|      |              | shall be available,        |      | of       |
|      |              | on-line and fully          |      | c        |
|      |              | operational at the start   |      | ontract. |
|      |              | of the contract. The       |      |          |
|      |              | system shall be capable of |      | Server   |
|      |              | handling the load required |      | online   |
|      |              | by the CMMS software and   |      | at all   |
|      |              | provide reliable and       |      | times.   |
|      |              | responsive service to the  |      |          |
|      |              | Government.                |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | The CMMS software license  |      |          |
|      |              | with software provider's   |      |          |
|      |              | technical support shall be |      |          |
|      |              | provided by the Contractor |      |          |
|      |              | for each year of the       |      |          |
|      |              | contract and for one year  |      |          |
|      |              | beyond the end of the      |      |          |
|      |              | contract. The contractor   |      |          |
|      |              | shall provide, in addition |      |          |
|      |              | to the licenses he         |      |          |
|      |              | requires, 15 additional    |      |          |
|      |              | concurrent licenses for    |      |          |
|      |              | Government access to the   |      |          |
|      |              | CMMS. If proposed CMMS is  |      |          |
|      |              | web based then license     |      |          |
|      |              | must allow for 15          |      |          |
|      |              | Government computers       |      |          |
|      |              | online at one time.        |      |          |
|      |              |                            |      |          |
|      |              | NOTE: The existing         |      |          |
|      |              | contractor has prepaid a   |      |          |
|      |              | license for 50 concurrent  |      |          |
|      |              | sessions of MP2 for the    |      |          |
|      |              | first year of the COSS     |      |          |
|      |              | contract. The version of   |      |          |
|      |              | the CMMS in use is not the |      |          |
|      |              | latest and is no longer    |      |          |
|      |              | supported by the software  |      |          |
|      |              | provider. The server that  |      |          |
|      |              | MP2 is installed on is     |      |          |
|      |              | owned by the BOSS          |      |          |
|      |              | contractor and will not be |      |          |
|      |              | available.                 |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | Provide the Government     |      |          |
|      |              | mandated fields, listed in |      |          |
|      |              | Table 8-1, as part of the  |      |          |
|      |              | CMMS. The fields shall be  |      |          |
|      |              | setup and configured as    |      |          |
|      |              | listed and any changes     |      |          |
|      |              | must be approved by the    |      |          |
|      |              | Information Technology     |      |          |
|      |              | **\*TMR** and the          |      |          |
|      |              | Maintenance & Repair       |      |          |
|      |              | **\*TMR**. These fields    |      |          |
|      |              | are in addition to fields  |      |          |
|      |              | that the contractor needs  |      |          |
|      |              | to perform contract        |      |          |
|      |              | functions. The fields      |      |          |
|      |              | shall be fully searchable  |      |          |
|      |              | and sortable.              |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | Maintain the | Identify, report and       | 365  | Program  |
| .3.3 | CMMS.        | incorporate changes,       | days | changes  |
|      |              | errors, deficiencies, or   |      | s        |
|      | Ensure the   | recommended improvement to |      | ubmitted |
|      | CMMS Program | the CMMS Program to ensure |      | within   |
|      | remains      | the Program remains        |      | 14 days. |
|      | accurate and | accurate and up-to-date.   |      |          |
|      | up-to-date.  |                            |      | CMMS     |
|      |              | This includes providing    |      | program  |
|      |              | programming support on a   |      | a        |
|      |              | continual basis to         |      | vailable |
|      |              | \"troubleshoot,\" correct  |      | conti    |
|      |              | minor programming bugs,    |      | nuously. |
|      |              | etc.                       |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | NOTE: To encourage         |      |          |
|      |              | improvement and            |      |          |
|      |              | effectiveness, the         |      |          |
|      |              | Contractor\'s work force   |      |          |
|      |              | is encouraged to identify  |      |          |
|      |              | improvements or changes to |      |          |
|      |              | the CMMS Program. As a     |      |          |
|      |              | minimum, this includes     |      |          |
|      |              | work that is reasonably    |      |          |
|      |              | visible to any Contractor  |      |          |
|      |              | personnel performing any   |      |          |
|      |              | related service.           |      |          |
|      |              |                            |      |          |
|      |              | Evaluate proposed changes  |      |          |
|      |              | identified by the IT       |      |          |
|      |              | **\*TMR**. Perform actions |      |          |
|      |              | necessary to identify      |      |          |
|      |              | change, research           |      |          |
|      |              | (including field           |      |          |
|      |              | verification to validate   |      |          |
|      |              | the information), develop  |      |          |
|      |              | associated maintenance     |      |          |
|      |              | documentation (e.g.,       |      |          |
|      |              | Annual Maintenance Plans   |      |          |
|      |              | and Schedule, PM and PT&I  |      |          |
|      |              | Maintenance Work           |      |          |
|      |              | Description for each task, |      |          |
|      |              | critical spares data,      |      |          |
|      |              | etc.) and to submit to the |      |          |
|      |              | IT **\*TMR** for           |      |          |
|      |              | consideration and          |      |          |
|      |              | approval..                 |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | Submit proposed changes in |      |          |
|      |              | electronic format.         |      |          |
|      |              |                            |      |          |
|      |              | NOTE: Contractor-proposed  |      |          |
|      |              | recommendations will be    |      |          |
|      |              | subject to                 |      |          |
|      |              | Government-approved format |      |          |
|      |              | and will include proposed  |      |          |
|      |              | maintenance documentation  |      |          |
|      |              | changes.                   |      |          |
|      |              |                            |      |          |
|      |              | Submit changes to the IT   |      |          |
|      |              | **\*TMR** within 14 days   |      |          |
|      |              | of (1) completion of work  |      |          |
|      |              | performed under the terms  |      |          |
|      |              | of this contract; (2)      |      |          |
|      |              | notification of change; or |      |          |
|      |              | (3) first observation of   |      |          |
|      |              | change, whichever is       |      |          |
|      |              | first.                     |      |          |
|      |              |                            |      |          |
|      |              | Ensure changes include all |      |          |
|      |              | backup or supporting       |      |          |
|      |              | documentation.             |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | Provide, implement, and    | Co   | CMMS     |
|      |              | maintain the necessary     | ntra | data     |
|      |              | process analysis, data     | ctor | ac       |
|      |              | gathering, and reporting   | de   | cessible |
|      |              | software to meet contract  | term | to       |
|      |              | requirements (DRD's,       | ined | Go       |
|      |              | reports, metrics, etc.).   |      | vernment |
|      |              |                            |      | at all   |
|      |              | Provide on-line            |      | times.   |
|      |              | connectivity to the        |      |          |
|      |              | Government and integrate   |      |          |
|      |              | the data with CMMS.        |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | #####        | Maintain History Files     | 365  | Files    |
| .3.4 | # Maintain H |                            | days | are      |
|      | istory Files | History files include, but |      | r        |
|      |              | are not limited to,        |      | ecorded, |
|      | Maintain     | Facility Condition         |      | a        |
|      | history      | Assessment (FCA), MA,      |      | ccurate, |
|      | files to     | PT&I, PM, and Repair,      |      | and      |
|      | reflect all  | databases, records, and    |      | current. |
|      | Contract     | logs.                      |      | Files    |
|      | Services     |                            |      | are      |
|      |              | Assume management of       |      | c        |
|      |              | existing on-line history   |      | omplete, |
|      |              | files from the preceding   |      | c        |
|      |              | Contractors and create and |      | entrally |
|      |              | incorporate new history    |      | located, |
|      |              | files. Continue            |      | and      |
|      |              | maintaining files and data |      | readily  |
|      |              | fields for all services    |      | a        |
|      |              | provided under the terms   |      | vailable |
|      |              | of this contract; e.g.,    |      | for      |
|      |              | maintenance and repair     |      | review   |
|      |              | actions, construction and  |      | or       |
|      |              | alteration projects,       |      | obtained |
|      |              | inspection results,        |      | via hard |
|      |              | Predictive Testing and     |      | copy at  |
|      |              | Inspection (PT&I) Data,    |      | all      |
|      |              | PT&I Baselines, PT&I       |      | times.   |
|      |              | Trends, equipment          |      |          |
|      |              | condition, Maintenance     |      |          |
|      |              | Activation, accomplished   |      |          |
|      |              | Preventive Maintenance     |      |          |
|      |              | (PM), etc.                 |      |          |
|      |              |                            |      |          |
|      |              | Ensure and maintain a      |      |          |
|      |              | filing/maintenance system  |      |          |
|      |              | that provides quick and    |      |          |
|      |              | easy access to existing    |      |          |
|      |              | files. All previous data   |      |          |
|      |              | must be incorporated and   |      |          |
|      |              | accessible.                |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | Maintain on-line access to |      |          |
|      |              | files; ensure that hard    |      |          |
|      |              | copies are easily          |      |          |
|      |              | obtainable with no loss of |      |          |
|      |              | pertinent data. Submit     |      |          |
|      |              | improvement                |      |          |
|      |              | recommendations to the IT  |      |          |
|      |              | **\*TMR** for approval.    |      |          |
+------+--------------+----------------------------+------+----------+
| **8  | **E          |                            |      |          |
| .4** | nvironmental |                            |      |          |
|      | Management   |                            |      |          |
|      | IT Support** |                            |      |          |
+------+--------------+----------------------------+------+----------+
|      | E            | Provide IT support to      | 365  | All      |
|      | nvironmental | install environmental web  | days | envir    |
|      | Web based /  | based / client             |      | onmental |
|      | client       | applications that are used |      | software |
|      | application  | either by the contractor   |      | and      |
|      | support      | or NASA Environmental      |      | websites |
|      |              | Office. Current            |      | are      |
|      |              | applications include NETS, |      | fully    |
|      |              | STEERS, ISW database,      |      | fu       |
|      |              | web-based training, EO/EMS |      | nctional |
|      |              | website and EMS database.  |      | and      |
|      |              | All upgrades or updates    |      | a        |
|      |              | will be installed within 7 |      | vailable |
|      |              | calendar days of receipt.  |      | at all   |
|      |              | Test the upgrades to       |      | times    |
|      |              | ensure it works properly   |      |          |
|      |              | prior to full              |      | NASA or  |
|      |              | implementation. All        |      | re       |
|      |              | personnel requesting       |      | gulatory |
|      |              | user-ids and passwords     |      | agency   |
|      |              | receive them within 7      |      | authori  |
|      |              | calendar days.             |      | zations, |
|      |              |                            |      | l        |
|      |              | Maintain / update the data |      | icenses, |
|      |              | including but not limited  |      | requ     |
|      |              | to (help data, train       |      | irements |
|      |              | modules, FAQ, help) on the |      | and      |
|      |              | COD Environmental Web      |      | rest     |
|      |              | page.                      |      | rictions |
|      |              |                            |      | will be  |
|      |              |                            |      | followed |
|      |              |                            |      | at all   |
|      |              |                            |      | times    |
|      |              |                            |      | for all  |
|      |              |                            |      | aspects  |
|      |              |                            |      | of the   |
|      |              |                            |      | software |
|      |              |                            |      | and      |
|      |              |                            |      | programs |
+------+--------------+----------------------------+------+----------+
|      | ######       | NOTE: The programming for  |      |          |
|      |              | these applications and     |      |          |
|      |              | help desk is provided by   |      |          |
|      |              | the owning organization    |      |          |
|      |              | (State of Texas, Other     |      |          |
|      |              | Government Agencies, or    |      |          |
|      |              | Other NASA Centers).       |      |          |
|      |              | Generally, these           |      |          |
|      |              | applications access a web  |      |          |
|      |              | page via a browser;        |      |          |
|      |              | however, they may require  |      |          |
|      |              | a local client to be       |      |          |
|      |              | loaded on the user PC. At  |      |          |
|      |              | least one application      |      |          |
|      |              | requires a database to be  |      |          |
|      |              | installed and maintained   |      |          |
|      |              | on COD server space that   |      |          |
|      |              | is backed up by others. It |      |          |
|      |              | is the user responsibility |      |          |
|      |              | to interface with the      |      |          |
|      |              | appropriate help desk to   |      |          |
|      |              | report an initial problem. |      |          |
|      |              | Provide local user help    |      |          |
|      |              | and troubleshooting        |      |          |
|      |              | whenever a change to the   |      |          |
|      |              | software or when problems  |      |          |
|      |              | occur. The NASA            |      |          |
|      |              | Environmental Office will  |      |          |
|      |              | be responsible for         |      |          |
|      |              | requesting and maintaining |      |          |
|      |              | user-ids / list,           |      |          |
|      |              | conducting beta tests as   |      |          |
|      |              | requested. NASA or         |      |          |
|      |              | regulatory agency          |      |          |
|      |              | authorizations, licenses,  |      |          |
|      |              | requirements and           |      |          |
|      |              | restrictions will be       |      |          |
|      |              | followed at all times for  |      |          |
|      |              | all aspects of the         |      |          |
|      |              | software and programs.     |      |          |
|      |              |                            |      |          |
|      |              | NOTE: Programming changes  |      |          |
|      |              | to the Environmental Web   |      |          |
|      |              | Page, the impacts database |      |          |
|      |              | or the program database    |      |          |
|      |              | will be done by others.    |      |          |
+------+--------------+----------------------------+------+----------+
| **8  | #            |                            |      |          |
| .5** | ##### Energy |                            |      |          |
|      |  Management  |                            |      |          |
|      | Control Syst |                            |      |          |
|      | em (EMCS) Sy |                            |      |          |
|      | stem Support |                            |      |          |
+------+--------------+----------------------------+------+----------+
|      | EMCS         | > Provide IT support to    | 365  | IT       |
|      | database     | > manage the EMCS          | days | support  |
|      | support      | > databases that support   |      | of       |
|      |              | > day-to-day operations of |      | da       |
|      |              | > the EMCS system          |      | y-to-day |
|      |              | > (excludes hardware such  |      | op       |
|      |              | > as RTU's, Metasys hubs,  |      | erations |
|      |              | > Woodward Smart 3000,     |      | /        |
|      |              | > etc.). The COSS          |      | database |
|      |              | > contractor shall         |      | support  |
|      |              | > maintain existing        |      | of       |
|      |              | > Microsoft Access and     |      | co       |
|      |              | > Excel data status files. |      | ntractor |
|      |              | >                          |      | users is |
|      |              | > NOTE: The EMCS is        |      | p        |
|      |              | > primarily a real-time    |      | rovided. |
|      |              | > system that is used for  |      |          |
|      |              | > control of facilities    |      | D        |
|      |              | > (HVAC, boilers,          |      | atabases |
|      |              | > chillers, Power, etc.)   |      | are      |
|      |              | > and is partially the     |      | f        |
|      |              | > responsibility of the    |      | ormatted |
|      |              | > COSS contractor, the     |      | co       |
|      |              | > Honeywell contractor and |      | rrectly. |
|      |              | > other contractors. For   |      |          |
|      |              | > the sake of clarity the  |      |          |
|      |              | > operations support for   |      |          |
|      |              | > this system is primarily |      |          |
|      |              | > covered in the EMCS      |      |          |
|      |              | > Operations section of    |      |          |
|      |              | > the contract (Annex 4).  |      |          |
+------+--------------+----------------------------+------+----------+
| **8  | ##           |                            |      |          |
| .6** | #### System  |                            |      |          |
|      | Operations / |                            |      |          |
|      |  Maintenance |                            |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | Provide support and        | 365  | Co       |
|      |              | operate IT systems while   | days | ntractor |
|      |              | ensuring the programs are  |      | operated |
|      |              | functioning properly and   |      | IT       |
|      |              | in the same manner as the  |      | systems  |
|      |              | programs provided.         |      | ac       |
|      |              |                            |      | cessible |
|      |              | Maintain and protect all   |      | at all   |
|      |              | IT systems and maintain    |      | times.   |
|      |              | data integrity in all      |      |          |
|      |              | databases and other        |      |          |
|      |              | programs/systems. Upon     |      |          |
|      |              | termination of the         |      |          |
|      |              | Contract, return to the    |      |          |
|      |              | Government all current     |      |          |
|      |              | source/compiled programs,  |      |          |
|      |              | documentation, data, or    |      |          |
|      |              | similar software data, in  |      |          |
|      |              | a usable format consistent |      |          |
|      |              | to the manner in which the |      |          |
|      |              | Government originally      |      |          |
|      |              | provided it.               |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | > Maintain                 |      |          |
|      |              | > installation-provided    |      |          |
|      |              | > systems separately from  |      |          |
|      |              | > the Contractor\'s        |      |          |
|      |              | > proprietary systems such |      |          |
|      |              | > as the Contractor\'s     |      |          |
|      |              | > financial management,    |      |          |
|      |              | > personnel and other like |      |          |
|      |              | > systems.                 |      |          |
|      |              |                            |      |          |
|      |              | Upon breakdowns, advise    |      |          |
|      |              | the IT **\*TMR** of all    |      |          |
|      |              | scheduled actions to bring |      |          |
|      |              | the system back on-line.   |      |          |
+------+--------------+----------------------------+------+----------+
| **8  | ####         |                            |      |          |
| .7** | ### Online S |                            |      |          |
|      | ystem Access |                            |      |          |
|      |  and Support |                            |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | Provide and  | Provide, maintain, and     | 365  | Go       |
| .7.1 | maintain     | support continuous         | days | vernment |
|      | Government   | Government on-line access  |      | access   |
|      | access and   | to all contractor operated |      | to any   |
|      | support to   | computer systems (except   |      | required |
|      | all existing | payroll and personnel)     |      | data in  |
|      | contractor   | including, but not limited |      | any      |
|      | operated     | to contract required       |      | system   |
|      | on-line      | databases, data, records,  |      | or       |
|      | computer     | plans, metrics, schedules, |      | database |
|      | systems.     | and history, and to all    |      | is       |
|      |              | Government-provided        |      | mai      |
|      |              | applications and           |      | ntained. |
|      |              | databases. Access is to be |      |          |
|      |              | compatible with server     |      | Co       |
|      |              | configurations and loads   |      | ntractor |
|      |              | such that COD users may    |      | operated |
|      |              | utilize, analyze, and      |      | systems  |
|      |              | extract data, etc.         |      | ac       |
|      |              |                            |      | cessible |
|      |              | Notify the IT **\*TMR** in |      | at all   |
|      |              | case of system failure and |      | times.   |
|      |              | provide status updates to  |      |          |
|      |              | the IT **\*TMR** every     |      |          |
|      |              | four hours. Scheduled      |      |          |
|      |              | downtime for short periods |      |          |
|      |              | of up to 4 hours to allow  |      |          |
|      |              | for upgrades, repairs and  |      |          |
|      |              | maintenance are acceptable |      |          |
|      |              | exceptions to              |      |          |
|      |              | \"continuous\" on-line     |      |          |
|      |              | access. Where possible     |      |          |
|      |              | these periods should be in |      |          |
|      |              | the evening after **\*Core |      |          |
|      |              | Hours**.                   |      |          |
|      |              |                            |      |          |
|      |              | NOTE: Systems with on-line |      |          |
|      |              | support: See Section J,    |      |          |
|      |              | Attachment K List 1.       |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | ###### Web   | Provide a web based        | 365  | Data     |
| .7.2 |  Based Manag | Management Information     | days | shall be |
|      | ement Inform | System on JSC web servers  |      | a        |
|      | ation System | which displays the         |      | ccurate, |
|      |              | required data as shown in  |      | unders   |
|      | Provide a    | Table 8-2. The data shall  |      | tandable |
|      | Web Based    | be maintained for access   |      | and      |
|      | Management   | by the JSC user community  |      | av       |
|      | Information  | (see Table 8-2 for         |      | ailable. |
|      | System       | restricted data) and the   |      |          |
|      |              | Contractor.                |      |          |
|      |              |                            |      |          |
|      |              | The web page shall be      |      |          |
|      |              | updated to display the     |      |          |
|      |              | latest reports, plans,     |      |          |
|      |              | metrics, procedures, etc.  |      |          |
|      |              | within 3 **\*workdays**.   |      |          |
|      |              | All other data, (e.g. work |      |          |
|      |              | orders) shall be updated   |      |          |
|      |              | as required to keep the    |      |          |
|      |              | data current and           |      |          |
|      |              | meaningful.                |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | The MIS shall also allow   |      | The MIS  |
|      |              | 24 hour, 7 day a week      |      | allows   |
|      |              | web-based accessibility to |      | w        |
|      |              | provide on-line:           |      | eb-based |
|      |              |                            |      | acces    |
|      |              | 1\. Customer real-time     |      | sibility |
|      |              | statusing of ordered work, |      | to the   |
|      |              |                            |      | required |
|      |              | 2\. Submission of feedback |      | features |
|      |              | by customers at any time,  |      | at all   |
|      |              |                            |      | times    |
|      |              | 3\. \"Community Page\" -   |      | and the  |
|      |              | which provides site        |      | data     |
|      |              | information to the site    |      | accessed |
|      |              | community such as planned  |      | is       |
|      |              | road closures, power       |      | a        |
|      |              | outages, and other         |      | ccurate. |
|      |              | activities that affect the |      |          |
|      |              | public,                    |      |          |
|      |              |                            |      |          |
|      |              | 4\. \"Performance Page\" - |      |          |
|      |              | which provides technical   |      |          |
|      |              | information such as        |      |          |
|      |              | critical system            |      |          |
|      |              | availability compared      |      |          |
|      |              | against trigger metrics.   |      |          |
|      |              |                            |      |          |
|      |              | 5\. Monitoring of all COSS |      |          |
|      |              | performance metrics,       |      |          |
|      |              |                            |      |          |
|      |              | 6\. Access to corrective   |      |          |
|      |              | action plans.              |      |          |
+------+--------------+----------------------------+------+----------+
| **8  | ###### Faci  |                            |      |          |
| .8** | lity CAD Sys |                            |      |          |
|      | tem / Space  |                            |      |          |
|      | Utilization  |                            |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | ###          | Provide support for the    | 200  | R        |
| .8.1 | ### CAD Soft | CAD software versions used | h    | equested |
|      | ware support | to support the Facility    | ours | pro      |
|      |              | Cad System. Support        |      | gramming |
|      |              | includes, but is not       |      | support  |
|      |              | limited to, response to    |      | provided |
|      |              | questions,                 |      | at all   |
|      |              | trouble-shooting problems, |      | times.   |
|      |              | installing the server      |      |          |
|      |              | application, installing    |      | Support  |
|      |              | the client application and |      | provided |
|      |              | assistance in printing.    |      | within 8 |
|      |              | Provide application        |      | hours of |
|      |              | support within 8 hours of  |      | request. |
|      |              | the request.               |      |          |
|      |              |                            |      |          |
|      |              | Maintain for the           |      |          |
|      |              | capability for the current |      |          |
|      |              | and two previous CAD       |      |          |
|      |              | software versions of all   |      |          |
|      |              | CAD drawings.              |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | ####         | #### Provide 2 AutoCAD li  | 2    | Correct  |
| .8.2 | ## CAD Softw | censes (latest version) an | Aut  | number   |
|      | are Licenses | d retain 5 concurrent Micr | oCAD | of       |
|      |              | oStation user licenses (la | lice | co       |
|      |              | test version) exclusively  | nses | ncurrent |
|      |              | for use by the Government. |      | licenses |
|      |              |                            |      | is       |
|      |              | **NOTE: The government     |      | p        |
|      |              | will provide 23            |      | rovided. |
|      |              | MicroStation licenses at   |      |          |
|      |              | contract start.**          |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | #### P                     |      | New      |
|      |              | rovide a new capability wi |      | ca       |
|      |              | thin the first 6 months of |      | pability |
|      |              |  the contract to produce d |      | provided |
|      |              | rawings in AutoCAD format. |      | on time. |
+------+--------------+----------------------------+------+----------+
|      | ######       | #                          |      | Upgrades |
|      |              | ### Upgrade existing licen |      | are      |
|      |              | ses within 6 months after  |      | provided |
|      |              | a new version is released. |      | within 6 |
|      |              |                            |      | months   |
|      |              | #### NOTE: The             |      | of       |
|      |              | Contractor shall upgrade l |      | release. |
|      |              | icenses in the proportion  |      |          |
|      |              | needed (MicroStation vs Au |      |          |
|      |              | toCAD) to adequately perfo |      |          |
|      |              | rm the CAD drafting requir |      |          |
|      |              | ements identified in Annex |      |          |
|      |              |  5. It is anticipated that |      |          |
|      |              |  the number of each applic |      |          |
|      |              | ation will vary during the |      |          |
|      |              |  contract as the number of |      |          |
|      |              |  AutoCAD facility drawings |      |          |
|      |              |  will increase and the num |      |          |
|      |              | ber of MicroStation facili |      |          |
|      |              | ty drawings will decrease. |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | ######       | #### Main                  | 365  | CGM      |
| .8.3 | CGM Viewing  | tain the databases for all | days | files    |
|      | Support / fa |  facility drawings and Fac |      | are      |
|      | cility drawi | ility Housing Plans (FHP). |      | a        |
|      | ng database  |  Update the databases with |      | vailable |
|      |              | in 5 working days after ea |      | within 5 |
|      |              | ch drawing is updated. If  |      | days     |
|      |              | the drawing being updated, |      | after    |
|      |              |  is needed to provide curr |      | update.  |
|      |              | ent information about a pa |      |          |
|      |              | rticular facility, update  |      |          |
|      |              | the database in real-time. |      |          |
|      |              |                            |      |          |
|      |              | ###                        |      |          |
|      |              | # Convert any updated draw |      |          |
|      |              | ings at least once a week  |      |          |
|      |              | to Computer Graphics Metal |      |          |
|      |              | ife (CGM) format and place |      |          |
|      |              |  them in a predetermined l |      |          |
|      |              | ocation on JSC_COD_CAD01 o |      |          |
|      |              | r other designated server. |      |          |
|      |              |                            |      |          |
|      |              | ####                       |      |          |
|      |              | NOTE: The existing convers |      |          |
|      |              | ion is presently being don |      |          |
|      |              | e with an automated proces |      |          |
|      |              | s (macro) that has minimal |      |          |
|      |              |  user effort. The contract |      |          |
|      |              | or will maintain an automa |      |          |
|      |              | ted conversion capability. |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | Space        | Provide programming        | 40   | Pro      |
| .8.4 | Utilization  | support for Space          | h    | gramming |
|      | Management   | Utilization Management     | ours | support  |
|      | System       | System (SUMS) including    |      | provided |
|      | Programming  | response to questions,     |      | within 8 |
|      | Support Data | trouble shooting problems, |      | hours of |
|      | Entry        | and assistance in          |      | request. |
|      |              | printing. Support shall be |      |          |
|      | ###### Ensu  | provided within 8 hours of |      |          |
|      | re data entr | the request.               |      |          |
|      | y assistance |                            |      |          |
|      |              | Create new or modify       |      |          |
|      |              | existing reports on an as  |      |          |
|      |              | needed basis.              |      |          |
+------+--------------+----------------------------+------+----------+
| **8  | #            |                            |      |          |
| .9** | ##### Other  |                            |      |          |
|      | Applications |                            |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | ###### Gas   | Replace the existing Gas   | 1    | Gas      |
| .9.1 | Cylinder Tra | Cylinder Tracking System   | trac | Cylinder |
|      | cking System | within the first 6 months  | king | Tracking |
|      |              | of the contract with a new | sy   | system   |
|      |              | system that is compatible  | stem | is       |
|      |              | with Microsoft Access, SQL |      | c        |
|      |              | Server or Oracle.          |      | onverted |
|      |              |                            |      | in year  |
|      |              | Provide the same           |      | 1 and    |
|      |              | capability in the new      |      | data and |
|      |              | system that exists in the  |      | r        |
|      |              | present system and further |      | eporting |
|      |              | detailed in the following: |      | ca       |
|      |              |                            |      | pability |
|      |              |                            |      | is as    |
|      |              |                            |      | sp       |
|      |              |                            |      | ecified. |
+------+--------------+----------------------------+------+----------+
|      | ######       | 1.  Provide the capability |      | Data is  |
|      |              |     to barcode, and the    |      | a        |
|      |              |     necessary scanners     |      | ccurate. |
|      |              |     (equivalent to or      |      |          |
|      |              |     newer than the latest  |      |          |
|      |              |     Intermec Scanners used |      |          |
|      |              |     by the NEMS            |      |          |
|      |              |     personnel).            |      |          |
|      |              |                            |      |          |
|      |              | 2.  Install the new        |      |          |
|      |              |     application on one of  |      |          |
|      |              |     the                    |      |          |
|      |              |     Contractor-Operated    |      |          |
|      |              |     Contractor Maintained  |      |          |
|      |              |     servers.               |      |          |
|      |              |                            |      |          |
|      |              | Provide two users licenses |      |          |
|      |              | for NASA.                  |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | Provide reports that show  |      |          |
|      |              | the number, type, serial   |      |          |
|      |              | numbers, gas, and quantity |      |          |
|      |              | of gas, delivered each     |      |          |
|      |              | month. Provide a report    |      |          |
|      |              | that includes the          |      |          |
|      |              | cylinders returned to the  |      |          |
|      |              | suppliers, serial number,  |      |          |
|      |              | type of gas, date          |      |          |
|      |              | delivered, date returned,  |      |          |
|      |              | if rejected, why cylinder  |      |          |
|      |              | was rejected. Provide an   |      |          |
|      |              | ad hoc query capability    |      |          |
|      |              | for the Government to      |      |          |
|      |              | write reports.             |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | ###### Barc  | Provide barcode scanner    | 365  | Barcode  |
| .9.2 | ode Scanners | capability that includes   | days | scanner  |
|      |  Support and | all hardware, software,    |      | ca       |
|      |  Maintenance | and support capability.    |      | pability |
|      |              | This capability shall be   |      | fully    |
|      |              | available and fully        |      | ope      |
|      |              | operational at the start   |      | rational |
|      |              | of the contract..          |      | at start |
|      |              |                            |      | of       |
|      |              | NOTE: See Section J        |      | c        |
|      |              | Attachment I, List 3 for   |      | ontract. |
|      |              | the listing of government  |      |          |
|      |              | provided scanners to be    |      |          |
|      |              | used for the               |      |          |
|      |              | Transportation Inbound     |      |          |
|      |              | Freight Log (TIFL) and the |      |          |
|      |              | Gas Cylinder Tracking.     |      |          |
|      |              |                            |      |          |
|      |              | NOTE: All scanners         |      |          |
|      |              | required to support NASA   |      |          |
|      |              | agency-wide applications   |      |          |
|      |              | (i.e., NEMS, NSMS, and     |      |          |
|      |              | NPDMS) will be provided by |      |          |
|      |              | the government.            |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | Provide support to write   | 365  | Menu     |
|      |              | the menus, maintain, and   | days | updates  |
|      |              | load all bar code scanners |      | are      |
|      |              | and the scanners used by   |      | a        |
|      |              | the JSC Security Forces on |      | vailable |
|      |              | another contract. Provide  |      | within 5 |
|      |              | all maintenance for the    |      | working  |
|      |              | barcode scanners, docking  |      | days of  |
|      |              | units, and power supplies. |      | request  |
|      |              |                            |      |          |
|      |              | NOTE: The support will be  |      |          |
|      |              | for 31 scanners. The       |      |          |
|      |              | general use breakdown is   |      |          |
|      |              | for 12 scanners used to    |      |          |
|      |              | support NEMS, 6 scanners   |      |          |
|      |              | to support TIFL, 4         |      |          |
|      |              | scanners to support Gas    |      |          |
|      |              | Cylinder Tracking, and 9   |      |          |
|      |              | scanners to support the    |      |          |
|      |              | JSC Security Forces. The   |      |          |
|      |              | scanners are multipurpose  |      |          |
|      |              | devices that can be used   |      |          |
|      |              | on several systems by      |      |          |
|      |              | activating a different     |      |          |
|      |              | menu.                      |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | ###### Them  | Maintain and operate the   | 365  | Appl     |
| .9.3 | ography Data | existing thermography      | days | ications |
|      |              | data. Provide a new        |      | are      |
|      |              | capability to make the     |      | a        |
|      |              | thermoghrapy data          |      | vailable |
|      |              | available on the web       |      | within 6 |
|      |              | within the first 6 months  |      | months   |
|      |              | of the contract.           |      | of       |
|      |              |                            |      | contract |
|      |              | Data will be updated       |      | start.   |
|      |              | within 7 days of data      |      |          |
|      |              | collection.                |      | Data is  |
|      |              |                            |      | accurate |
|      |              |                            |      | and      |
|      |              |                            |      | timely.  |
+------+--------------+----------------------------+------+----------+
| 8    | ###### Vi    | Maintain and operate the   | 365  | Appl     |
| .9.4 | bration Data | existing Vibration Data    | days | ications |
|      |              | Application. Keep the      |      | are      |
|      |              | software current within 6  |      | a        |
|      |              | months of the issuance of  |      | vailable |
|      |              | new version.               |      | within 6 |
|      |              |                            |      | months   |
|      |              |                            |      | of       |
|      |              |                            |      | contract |
|      |              |                            |      | start..  |
+------+--------------+----------------------------+------+----------+
|      | ######       | Data will be updated       |      | Data is  |
|      |              | within 7 days of data      |      | accurate |
|      |              | collection.                |      | and      |
|      |              |                            |      | timely   |
+------+--------------+----------------------------+------+----------+
|      | ######       | Within 6 months of the     |      |          |
|      |              | start of the contract,     |      |          |
|      |              | provide a new capability   |      |          |
|      |              | to have a Web based        |      |          |
|      |              | database that will list    |      |          |
|      |              | the vibration data that is |      |          |
|      |              | being accumulated.         |      |          |
|      |              | Additionally, link all     |      |          |
|      |              | equipment items to the     |      |          |
|      |              | equipment numbers in the   |      |          |
|      |              | CMMS system. Provide a     |      |          |
|      |              | user-friendly interface    |      |          |
|      |              | that will permit a CMMS    |      |          |
|      |              | user to determine if       |      |          |
|      |              | Vibration data is          |      |          |
|      |              | available.                 |      |          |
+------+--------------+----------------------------+------+----------+
| 8    | #####        | Provide programming and    | 40   | No       |
| .9.5 | # Real Prope | system support for the     | h    | occ      |
|      | rty Database | Real Property Accounting   | ours | urrences |
|      |              | System (RPAS) used in      |      | of       |
|      |              | annex 5. Support shall     |      | failure  |
|      |              | include, but not be        |      | to       |
|      |              | limited to, responding to  |      | provide  |
|      |              | questions,                 |      | pro      |
|      |              | trouble-shooting problems  |      | gramming |
|      |              | and assistance in          |      | support  |
|      |              | printing. Provide support  |      | when     |
|      |              | within\                    |      | re       |
|      |              | 2-4 hours of the request.  |      | quested. |
|      |              | The exact schedule for     |      |          |
|      |              | each task shall be given   |      | Support  |
|      |              | when the task is assigned. |      | provided |
|      |              |                            |      | within   |
|      |              |                            |      | 2-4      |
|      |              |                            |      | hours of |
|      |              |                            |      | request  |
+------+--------------+----------------------------+------+----------+
| 8    | ###### Wi    | Provide all support to     | 40   | Appl     |
| .9.6 | nEst / Means | maintain the server-based  | h    | ications |
|      |              | application of WinEst and  | ours | are      |
|      |              | the Means cost data using  |      | a        |
|      |              | clients / icons on user    |      | vailable |
|      |              | work stations. Maintain    |      | when     |
|      |              | the current copy (and one  |      | server   |
|      |              | version back) of the       |      | access   |
|      |              | WinEst estimating          |      | is       |
|      |              | applications and current   |      | av       |
|      |              | yearly and quarterly       |      | ailable. |
|      |              | updates of Means           |      |          |
|      |              | Electronic Cost Databases. |      | Most     |
|      |              | Provide 5 concurrent       |      | current  |
|      |              | licenses for Government    |      | version  |
|      |              | use.                       |      | of       |
|      |              |                            |      | software |
|      |              |                            |      | is       |
|      |              |                            |      | av       |
|      |              |                            |      | ailable. |
+------+--------------+----------------------------+------+----------+
|      | ######       | The Contractor's           |      |          |
|      |              | computerized estimating    |      |          |
|      |              | software shall be          |      |          |
|      |              | compatible with Microsoft  |      |          |
|      |              | Windows and WinEst Pro     |      |          |
|      |              | Plus, by WinEstimator, Inc |      |          |
|      |              | estimating software or     |      |          |
|      |              | equal.                     |      |          |
|      |              |                            |      |          |
|      |              | NOTE: Presently, there are |      |          |
|      |              | 12 licenses being used for |      |          |
|      |              | Contractor and CS support. |      |          |
+------+--------------+----------------------------+------+----------+
| **8. | ####         | a\. Provide at contract    | 1    | System   |
| 10** | ## NEMS Syst | start a scanning           | sy   | is ready |
|      | em Scanning  | capability for support of  | stem | at start |
|      |              | COD Activities. Scanning   |      | of       |
|      |              | capability will have a     |      | c        |
|      |              | non-proprietary database   |      | ontract. |
|      |              | (SQL Server, Oracle, or    |      |          |
|      |              | database approved by the   |      | System   |
|      |              | Contracting Officer).      |      | is sized |
|      |              |                            |      | ad       |
|      |              | NOTE: Current system uses  |      | equately |
|      |              | a workstation and flatbed  |      | to       |
|      |              | scanner with data stored   |      | handle   |
|      |              | on CDR's. The Contractor   |      | number   |
|      |              | shall provide the          |      | of       |
|      |              | workstation and scanner    |      | scans.   |
|      |              | system.                    |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | #### b.                    | 80   | Data     |
|      |              |  Provide IT support for th | h    | scanned  |
|      |              | e NEMS Scanning system. Co | ours | is       |
|      |              | ntinue to operate the exis |      | av       |
|      |              | ting historical portion of |      | ailable. |
|      |              |  that system and continue  |      |          |
|      |              | to have the information av |      | Database |
|      |              | ailable to the NEMS users. |      | has      |
|      |              |                            |      | correct  |
|      |              | #### Meet with the Govern  |      | keyword  |
|      |              | ment to agree on the data  |      | search   |
|      |              | to be scanned, keyword sea |      | cap      |
|      |              | rch, identification, inter |      | ability. |
|      |              | faces, etc. Design, implem |      |          |
|      |              | ent, and maintain the data |      |          |
|      |              |  necessary to recover and  |      |          |
|      |              | display the data, via ad h |      |          |
|      |              | oc search capability. Repe |      |          |
|      |              | at the above process as ne |      |          |
|      |              | w systems are identified t |      |          |
|      |              | hat need scanning support. |      |          |
|      |              |                            |      |          |
|      |              | NOTE: See CLIN 11.2.2.2    |      |          |
|      |              | for current scanning       |      |          |
|      |              | requirements.              |      |          |
+------+--------------+----------------------------+------+----------+
| **8. | ######       |                            |      |          |
| 11** |  IT Security |                            |      |          |
+------+--------------+----------------------------+------+----------+
| 8.   | Computer     | Provide support necessary  | 365  | On-line  |
| 11.1 | Systems and  | to ensure                  | days | systems  |
|      | Data         | Contractor-operated        |      | and data |
|      | Security     | systems and data remain    |      | security |
|      |              | secure at all times.       |      | are      |
|      | Maintain     |                            |      | ma       |
|      | Governme     | Backup daily all           |      | intained |
|      | nt-furnished | applications and data      |      | at all   |
|      | computer     | stored on                  |      | times.   |
|      | systems and  | Government-furnished       |      |          |
|      | data         | Contractor-operated        |      | All data |
|      | security for | servers or                 |      | or       |
|      | Contrac      | Contractor-furnished       |      | system   |
|      | tor-operated | Contractor-Operated        |      | appl     |
|      | systems.     | Servers.                   |      | ications |
|      |              |                            |      | ma       |
|      |              | > NOTE: The Government     |      | intained |
|      |              | > will backup each         |      | and      |
|      |              | > Government-operated      |      | secure.  |
|      |              | > server and mainframe     |      |          |
|      |              | > application.             |      | Changes  |
|      |              |                            |      | approved |
|      |              |                            |      | prior to |
|      |              |                            |      | impleme  |
|      |              |                            |      | ntation. |
+------+--------------+----------------------------+------+----------+
| 8.   | ###### C     | Appoint, in writing, a     | 365  | CSM is   |
| 11.2 | omputer Secu | Computer Security Manager  | Days | a        |
|      | rity Manager | (CSM). CSM duties include: |      | ppointed |
|      |              |                            |      | in       |
|      |              | 1.  Have knowledge and     |      | writing. |
|      |              |     background experience  |      | CSM      |
|      |              |     in IT Security.        |      | ex       |
|      |              |                            |      | perience |
|      |              | 2.  Have knowledge of      |      | and      |
|      |              |     contractor systems.    |      | ba       |
|      |              |     Prepare contractor     |      | ckground |
|      |              |     risk assessment        |      | comm     |
|      |              |     packages and security  |      | ensurate |
|      |              |     plans.                 |      | with     |
|      |              |                            |      | task.    |
|      |              | 3.  Attend and support     |      | CSM      |
|      |              |     Center Security or COD |      | passes   |
|      |              |     security meetings.     |      | ba       |
|      |              |                            |      | ckground |
|      |              | 4.  Fully cooperate with   |      | checks.  |
|      |              |     Government Security    |      |          |
|      |              |     Officials.             |      |          |
|      |              |                            |      |          |
|      |              | Provide \"supervisory      |      |          |
|      |              | access\" on an as needed   |      |          |
|      |              | basis to Government        |      |          |
|      |              | Computer Security          |      |          |
|      |              | Official(s). NOTE: The     |      |          |
|      |              | Government does not intend |      |          |
|      |              | to use this supervisory    |      |          |
|      |              | access right except where  |      |          |
|      |              | there is an indication of  |      |          |
|      |              | security violation or      |      |          |
|      |              | indication of unacceptable |      |          |
|      |              | security risks.            |      |          |
+------+--------------+----------------------------+------+----------+
| 8.   | ##           | Achieve and maintain       | 365  | All      |
| 11.3 | #### Compute | current certifications for | Days | ind      |
|      | r System Adm | all individuals who        |      | ividuals |
|      | inistrator C | perform tasks on COSS IT   |      | meeting  |
|      | ertification | systems as a system        |      | the      |
|      |              | administrator or have      |      | system   |
|      |              | authority to perform tasks |      | admin    |
|      |              | normally performed by the  |      | istrator |
|      |              | system administrator. This |      | de       |
|      |              | certification, referred to |      | finition |
|      |              | as the NASA System         |      | are      |
|      |              | Administrator Security     |      | appro    |
|      |              | Certification, is a        |      | priately |
|      |              | Government-funded          |      | c        |
|      |              | assessment to verify that  |      | ertified |
|      |              | system administrators are  |      | at all   |
|      |              | able to demonstrate        |      | times.   |
|      |              | knowledge in:              |      |          |
|      |              |                            |      |          |
|      |              | 1.  System administration  |      |          |
|      |              |     for the operating      |      |          |
|      |              |     systems for which they |      |          |
|      |              |     have responsibility.   |      |          |
|      |              |                            |      |          |
|      |              | 2.  The understanding and  |      |          |
|      |              |     application of Network |      |          |
|      |              |     and Internet Security. |      |          |
|      |              |                            |      |          |
|      |              | #### A system              |      |          |
|      |              | administrator responsible  |      |          |
|      |              | for multiple operating sys |      |          |
|      |              | tems must be certified in  |      |          |
|      |              | each system. The Governmen |      |          |
|      |              | t will provide the locatio |      |          |
|      |              | n as to where this certifi |      |          |
|      |              | cation(s) can be obtained. |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | A system administrator is  |      |          |
|      |              | one who provides IT        |      |          |
|      |              | services, network          |      |          |
|      |              | services, files storage,   |      |          |
|      |              | web services, etc. to      |      |          |
|      |              | someone else other than    |      |          |
|      |              | themselves and takes or    |      |          |
|      |              | assumes the responsibility |      |          |
|      |              | for the security and       |      |          |
|      |              | administrative controls of |      |          |
|      |              | that service or machine. A |      |          |
|      |              | lead system administrator  |      |          |
|      |              | has responsibility for     |      |          |
|      |              | information technology     |      |          |
|      |              | security (ITS) for         |      |          |
|      |              | multiple computers or      |      |          |
|      |              | network devises            |      |          |
|      |              | represented within a       |      |          |
|      |              | system; ensuring all       |      |          |
|      |              | devices assigned to them   |      |          |
|      |              | are kept in a secure       |      |          |
|      |              | configuration              |      |          |
|      |              | (patched/mitigated); and   |      |          |
|      |              | ensuring that all other    |      |          |
|      |              | system administrators      |      |          |
|      |              | under their lead           |      |          |
|      |              | understand and perform IT  |      |          |
|      |              | security duties.           |      |          |
+------+--------------+----------------------------+------+----------+
|      | ######       | NOTE - An individual that  |      |          |
|      |              | has full access or         |      |          |
|      |              | arbitrative rights on a    |      |          |
|      |              | system or machine that is  |      |          |
|      |              | only servicing themselves  |      |          |
|      |              | does not constitute a      |      |          |
|      |              | \"system administrator\"   |      |          |
|      |              | since they are only        |      |          |
|      |              | providing or accepting     |      |          |
|      |              | responsibility for their   |      |          |
|      |              | system. An individual that |      |          |
|      |              | only services themselves   |      |          |
|      |              | is not required to obtain  |      |          |
|      |              | a system administrator     |      |          |
|      |              | certification."            |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | Cooperate with and         |      |          |
|      |              | interface with the site    |      |          |
|      |              | Seat contractor for IT     |      |          |
|      |              | problems.                  |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | NOTE: The site has a Seat  |      |          |
|      |              | contractor that users can  |      |          |
|      |              | call to resolve IT issues. |      |          |
|      |              | If the issue is not the    |      |          |
|      |              | responsibility of the Seat |      |          |
|      |              | contractor then the        |      |          |
|      |              | problem is forwarded to    |      |          |
|      |              | the responsible group. It  |      |          |
|      |              | is expected that the COSS  |      |          |
|      |              | users will normally call   |      |          |
|      |              | the Seat contractor for    |      |          |
|      |              | issues that the Seat       |      |          |
|      |              | contractor is responsible  |      |          |
|      |              | for and the COSS users     |      |          |
|      |              | will normally call the     |      |          |
|      |              | COSS contractor IT support |      |          |
|      |              | for those systems for      |      |          |
|      |              | which the COSS contractor  |      |          |
|      |              | is responsible.            |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | b\. Provide a continuous   | 365  | List is  |
|      |              | **\*daily (D7)** emergency | days | posted   |
|      |              | IT Help Support capability |      | in the   |
|      |              | to handle emergency IT     |      | facility |
|      |              | issues. Provide access via |      | h        |
|      |              | a pager and cell phone.    |      | elpdesk. |
|      |              | Provide the name of a      |      |          |
|      |              | prime and two alternate    |      | IT Help  |
|      |              | contacts to call that can  |      | Support  |
|      |              | address emergency IT       |      | phone    |
|      |              | problems.                  |      | message  |
|      |              |                            |      | provides |
|      |              | Designate a permanent      |      | correct  |
|      |              | prime and alternate        |      | numbers  |
|      |              | contact that can address   |      | for      |
|      |              | emergency IT security      |      | emer     |
|      |              | issues.                    |      | gencies. |
|      |              |                            |      |          |
|      |              |                            |      | Prime    |
|      |              |                            |      | and      |
|      |              |                            |      | a        |
|      |              |                            |      | lternate |
|      |              |                            |      | contact  |
|      |              |                            |      | has been |
|      |              |                            |      | de       |
|      |              |                            |      | signated |
|      |              |                            |      | in       |
|      |              |                            |      | writing  |
|      |              |                            |      | to COD   |
|      |              |                            |      | OCSM and |
|      |              |                            |      | one is   |
|      |              |                            |      | a        |
|      |              |                            |      | vailable |
|      |              |                            |      | at all   |
|      |              |                            |      | times    |
+------+--------------+----------------------------+------+----------+
| 8.   | D            | Provide and maintain       | 365  | All      |
| 12.2 | ocumentation | copies of all updated      | days | docum    |
|      | Maintenance  | computer system            |      | entation |
|      | / Update for | documentation for major    |      | is       |
|      | Major        | systems (CMMS, EMCS, and   |      | current  |
|      | Systems      | Scanner System), Keep all  |      | and      |
|      |              | documentation in neatly    |      | acc      |
|      | Continually  | bound volumes with title   |      | essible. |
|      | update and   | covers and table of        |      |          |
|      | maintain all | contents. Maintain a copy  |      |          |
|      | computer     | of all updated manuals in  |      |          |
|      | system       | the IT Reference Annex TRL |      |          |
|      | d            | in the main COSS IT area.  |      |          |
|      | ocumentation |                            |      |          |
|      | for all      | Validate all documentation |      |          |
|      | Contrac      | no less than once every    |      |          |
|      | tor-provided | six months. Update         |      |          |
|      | and operated | documentation within two   |      |          |
|      | systems.     | weeks of change            |      |          |
|      |              | implementation.            |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | **Run Manuals** -- Ensure  | Co   | Audit    |
|      |              | all System Operator        | ntra | shows    |
|      |              | Manuals, job flow          | ctor | run      |
|      |              | configurations, and other  | Det  | manuals  |
|      |              | flow charts are updated    | ermi | are up   |
|      |              | and validated, including   | ned. | to date. |
|      |              | batch programming manuals  |      |          |
|      |              | and instructions.          |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | **Terminal Operation       | Co   | Audit    |
|      |              | Manuals** - Ensure all     | ntra | shows    |
|      |              | on-line systems operated   | ctor | terminal |
|      |              | by both the Government and | Det  | o        |
|      |              | the Contractor have        | ermi | peration |
|      |              | detailed narrative         | ned. | manuals  |
|      |              | descriptions, system flow  |      | are up   |
|      |              | charts, menu flow charts,  |      | to date. |
|      |              | access codes and other     |      |          |
|      |              | pertinent user             |      |          |
|      |              | information. Provide a     |      |          |
|      |              | point of contact to answer |      |          |
|      |              | questions in case of       |      |          |
|      |              | system problems.           |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | **Data Element             | Co   | Audit    |
|      |              | Dictionary** - Ensure data | ntra | shows    |
|      |              | element dictionaries       | ctor | that     |
|      |              | contain comprehensive      | Det  | data     |
|      |              | listings by data of all    | ermi | element  |
|      |              | fields including field     | ned. | di       |
|      |              | name, length, character    |      | ctionary |
|      |              | type, etc. Provide         |      | is up to |
|      |              | revisions to all           |      | date.    |
|      |              | documentation when changes |      |          |
|      |              | occur.                     |      |          |
+------+--------------+----------------------------+------+----------+
|      | .            | **System                   | Co   | All      |
|      |              | Configurations** - Provide | ntra | system   |
|      |              | and maintain system        | ctor | config   |
|      |              | configuration flow charts  | Det  | urations |
|      |              | that accurately portray    | ermi | are      |
|      |              | all functions, links, and  | ned. | accurate |
|      |              | relationships between the  |      | and      |
|      |              | different components.      |      | current  |
|      |              |                            |      | with a   |
|      |              | [Hardware                  |      | complete |
|      |              | C                          |      | audit    |
|      |              | onfiguration]{.underline}: |      | trail of |
|      |              | Accurately reflects all    |      | all      |
|      |              | terminals, connections,    |      | changes/ |
|      |              | modem communication links, |      | updates. |
|      |              | mainframe and ancillary    |      |          |
|      |              | supports, and other        |      |          |
|      |              | supplementary items.       |      |          |
|      |              |                            |      |          |
|      |              | [Databases and Program     |      |          |
|      |              | C                          |      |          |
|      |              | onfiguration]{.underline}: |      |          |
|      |              | Show the relationships     |      |          |
|      |              | between the programs,      |      |          |
|      |              | databases, and other       |      |          |
|      |              | components.                |      |          |
+------+--------------+----------------------------+------+----------+
|      |              | **Program Listings** -     | Co   | All      |
|      |              | Provide a hard copy of     | ntra | source   |
|      |              | source programs. Provide   | ctor | programs |
|      |              | revisions to all programs  | Det  | are      |
|      |              | when changes occur.        | ermi | current  |
|      |              |                            | ned. | and      |
|      |              |                            |      | acc      |
|      |              |                            |      | essible. |
+------+--------------+----------------------------+------+----------+
|      |              | **Programmer Manuals** -   | Co   | Manuals  |
|      |              | Ensure all programmer      | ntra | are      |
|      |              | maintenance manuals        | ctor | ma       |
|      |              | provide detailed           | Det  | intained |
|      |              | information about the      | ermi | and      |
|      |              | original program           | ned. | updated  |
|      |              | requirement, flow chart of |      | as       |
|      |              | program development, hard  |      | changes  |
|      |              | copy of source programs,   |      | occur.   |
|      |              | etc.                       |      |          |
|      |              |                            |      |          |
|      |              | NOTE: These manuals are    |      |          |
|      |              | developed for the purpose  |      |          |
|      |              | of aiding future           |      |          |
|      |              | programmers in the         |      |          |
|      |              | organization and           |      |          |
|      |              | philosophy of the existing |      |          |
|      |              | program.                   |      |          |
+------+--------------+----------------------------+------+----------+
| 8.   | Do           | Maintain a folder, or      | 365  | Database |
| 12.3 | cumentation, | other data as appropriate  | days | of       |
|      | Minor        | on the minor applications  |      | s        |
|      | Systems      | that are supported by the  |      | upported |
|      |              | IT group. Maintain a       |      | appl     |
|      |              | database that lists each   |      | ications |
|      |              | supported application, the |      | are      |
|      |              | owner, organization,       |      | a        |
|      |              | number of users,           |      | vailable |
|      |              | description, support       |      | to the   |
|      |              | method, how to get access, |      | COD IT   |
|      |              | server where application   |      | P        |
|      |              | is stored, etc.            |      | ersonnel |
|      |              |                            |      | via read |
|      |              |                            |      | only     |
|      |              |                            |      | access   |
|      |              |                            |      | to the   |
|      |              |                            |      | database |
|      |              |                            |      | or a web |
|      |              |                            |      | page     |
+------+--------------+----------------------------+------+----------+
| 8.   | Do           | Perform a yearly survey to | 1    | List is  |
| 12.4 | cumentation, | list the minor             | su   | a        |
|      | Minor        | applications that are      | rvey | vailable |
|      | Applications | being used by the COSS     |      | to COD   |
|      |              | (i.e. these are            |      | IT       |
|      |              | applications that are not  |      | Pe       |
|      |              | normally supported by the  |      | rsonnel. |
|      |              | IT group) to ascertain     |      |          |
|      |              | whether the data in the    |      |          |
|      |              | applications is being      |      |          |
|      |              | properly protected and     |      |          |
|      |              | location of data.          |      |          |
|      |              | Requirement is to list     |      |          |
|      |              | user, owner, description,  |      |          |
|      |              | type (Access2000, Excel    |      |          |
|      |              | 2000, etc.)                |      |          |
+------+--------------+----------------------------+------+----------+
| **8. | #####        |                            |      |          |
| 13** | #### Records |                            |      |          |
|      | , Reports an |                            |      |          |
|      | d Submittals |                            |      |          |
+------+--------------+----------------------------+------+----------+
| 8.   | Provide IT   | IT Security Plan DRD       | 1    | Accurate |
| 13.1 | Security     | AN-1-15 (initial plan      | plan | and      |
|      | Plan         | within 90 days of contract |      | detailed |
|      |              | start -- subsequent plans  |      | plan,    |
|      |              | as required before system  |      | complete |
|      |              | configuration is changed)  |      | and on   |
|      |              |                            |      | time.    |
+------+--------------+----------------------------+------+----------+

# Table : EQUIPMENT

+-------------+-----+------+------------------------------------------+
| **Field     | *   | **F  | ## Comments                              |
| Name**      | *Fi | ield |                                          |
|             | eld | Leng |                                          |
|             | Typ | th** |                                          |
|             | e** |      |                                          |
+-------------+-----+------+------------------------------------------+
| MAINTID     | T   | 10   | Unique record combination of number      |
|             | ext |      | and/or alpha characters identified as    |
|             |     |      | the specific level that individual       |
|             |     |      | maintenance records must be kept. Also   |
|             |     |      | Alphanumeric text that identifies system |
|             |     |      | level assignment when no specific number |
|             |     |      | ID is available. Will be used as a space |
|             |     |      | holder for contractor until actual       |
|             |     |      | equipment is identified. Example:        |
|             |     |      | J\*009NWHAC -- Bldg 9NW HVAC System      |
+-------------+-----+------+------------------------------------------+
| EQUIPID     | T   | 25   | Smart number used for quick              |
|             | ext |      | identification and recognition of        |
|             |     |      | equipment. Assigned by design            |
|             |     |      | engineering. Contains three codes. First |
|             |     |      | code indicates the type of equipment.    |
|             |     |      | The second code represents the building  |
|             |     |      | the equipment is installed in. The third |
|             |     |      | code represents the sequence of this     |
|             |     |      | unit in the overall count of similar     |
|             |     |      | units in the resident building.          |
+-------------+-----+------+------------------------------------------+
| DESCRIPTION | T   | 50   | Air Handler, Chiller, etc...Consistent   |
|             | ext |      | with the noun descriptor first and the   |
|             |     |      | primary pertinent information following  |
|             |     |      | a comma and if needed secondary          |
|             |     |      | pertinent information following a comma. |
|             |     |      |                                          |
|             |     |      | (Air Handler, PTOA) (Tank, Hot Water,    |
|             |     |      | Gas)                                     |
+-------------+-----+------+------------------------------------------+
| INSERVICE   | T   | 1    | (Y or N) If N then operating status      |
|             | ext |      | (OPERATINGSTATUS) should be used to      |
|             |     |      | indicate why.                            |
+-------------+-----+------+------------------------------------------+
| EQTYPE      | T   | 3    | Alpha legend that indicates the          |
|             | ext |      | equipment being described. Examples:     |
|             |     |      | (CHP -- Chilled Water Pump, AHU -- Air   |
|             |     |      | Handler Unit, HWG, Hot Water Generator)  |
|             |     |      | , allows grouping of similar items to    |
|             |     |      | run metrics for group failure analysis.  |
+-------------+-----+------+------------------------------------------+
| SITE        | T   | 5    | ELL (Ellington Field), JSC (Johnson      |
|             | ext |      | Space Center), SCTF (Sonny Carter        |
|             |     |      | Training Facility)                       |
+-------------+-----+------+------------------------------------------+
| BLDG        | T   | 12   | Alpha numeric to indicate building as    |
|             | ext |      | follows: S\*924\*\* or JT585\*\*. The \* |
|             |     |      | is used as a placeholder to allow proper |
|             |     |      | sorting.                                 |
+-------------+-----+------+------------------------------------------+
| SYSTEM      | T   | 20   | Contract labeled system, Codes used are  |
|             | ext |      | identified in Section J, Attachment N,   |
|             |     |      | Exhibit N-1 Table 1.0. This code allows  |
|             |     |      | running of metrics report to assess      |
|             |     |      | availability/reliability of contact      |
|             |     |      | systems.                                 |
+-------------+-----+------+------------------------------------------+
| LOCATION    | T   | 30   | Physical location, Room, Floor, O/S.     |
|             | ext |      |                                          |
+-------------+-----+------+------------------------------------------+
| SYSTYPECODE | T   | 10   | M Mechanical, E-Electrical,              |
|             | ext |      | X-Environmental, O-Other, UE-User        |
|             |     |      | Equipment etc...                         |
+-------------+-----+------+------------------------------------------+
| PKGFTR      | N   | 5    | Limit of Financial Liability for         |
|             | ume |      | Repairs. Multiplied by \$5000.00 per     |
|             | ric |      | factor.                                  |
+-------------+-----+------+------------------------------------------+
| SERIALNUM   | T   | 30   | Unique ID code from manufacture          |
|             | ext |      |                                          |
+-------------+-----+------+------------------------------------------+
| MODELNUM    | T   | 30   | General group from manufacture           |
|             | ext |      |                                          |
+-------------+-----+------+------------------------------------------+
| M           | T   | 20   | Manufacturers name                       |
| ANUFACTURER | ext |      |                                          |
+-------------+-----+------+------------------------------------------+
| COSTCENTER  | T   | 6    | Contractor Defined                       |
|             | ext |      |                                          |
+-------------+-----+------+------------------------------------------+
| PURCHDATE   | Sh  | 10   | Format: 11/26/2000. Original Purchase    |
|             | ort |      | date.                                    |
|             | D   |      |                                          |
|             | ate |      |                                          |
+-------------+-----+------+------------------------------------------+
| STARTUPDATE | Sh  | 10   | Format: 11/26/2000. Building Occupancy   |
|             | ort |      | Date.                                    |
|             | D   |      |                                          |
|             | ate |      |                                          |
+-------------+-----+------+------------------------------------------+
| W           | Sh  | 10   | Format: 11/26/2000. One year past        |
| ARRANTYDATE | ort |      | Building Occupancy date.                 |
|             | D   |      |                                          |
|             | ate |      |                                          |
+-------------+-----+------+------------------------------------------+
| O           | I   | 10   | Original purchase cost If available.     |
| RIGINALCOST | nte |      |                                          |
|             | ger |      |                                          |
+-------------+-----+------+------------------------------------------+
| OPER        | T   | 10   | Used when the INSERVICE field has a N    |
| ATINGSTATUS | ext |      | for equipment being in service.          |
|             |     |      | Examples: OOSMR -- Out of Service Major  |
|             |     |      | Repair, OOSMB -- Mothballed, OOSOB --    |
|             |     |      | Obsolete to be excessed, OOSEC -- Energy |
|             |     |      | Conservation                             |
+-------------+-----+------+------------------------------------------+
| PERSON      | T   | 10   | Used to indicate past Union and          |
| RESPONSIBLE | ext |      | Non-Union work jurisdiction set by       |
|             |     |      | presidence.                              |
+-------------+-----+------+------------------------------------------+
| PRIORITY    | I   | 1    | Could be used to represent Mission       |
|             | nte |      | Criticality. (Contractor option)         |
|             | ger |      |                                          |
+-------------+-----+------+------------------------------------------+
| CLASS       | T   | 1    | (N or C) Collateral or Non-Collateral    |
|             | ext |      |                                          |
+-------------+-----+------+------------------------------------------+
| SAFETY      | T   | 1    | (Y or N) If Y then equipment is a safety |
|             | ext |      | critical item (e.g. elevator, man rated  |
|             |     |      | crane)                                   |
+-------------+-----+------+------------------------------------------+

# Table : TASK

  -------------- --------- ---------- ------------------------------------------
  **Field Name** **Field   **Field    **Comments**
                 Type**    Length**   

  TASKNUM        Text      20         Unique ID code for task.

  DESCRIPTION    Text      80         Text statement that describe the required
                                      Scheduled Maintenance activity.

  WOTYPE         Text      8          SM (Scheduled Maintenance)

  PRIORITY       Integer   1          "3" All SM work will have a priority of 3
                                      for the initial input into the CMMS
                                      system.

  INSERVTASK     Text      1          (Y or N) Only "N" if task is being created
                                      or removed in order to keep it from
                                      generating a WO in the mean time.

  RACCODE        Integer   1          RAC code for safety tasks

  EXPENSECLASS   Text      6          Contractor Defined

  MULTITASK      Text      1          (Y or N)

  ASSIGNEDTO     Text      8          Contractor Defined

  INSTRCODE      Text      12         Unique ID for instruction assigned to
                                      perform task.

  CRAFT          Text      8          Craft to perform task

  CRAFT EST      Integer   3          =number of workers X hours/person
  -------------- --------- ---------- ------------------------------------------

# Table : EQTASK

  -------------- --------- ---------- ------------------------------------------
  **Field Name** **Field   **Field    **Comments**
                 Type**    Length**   

  MAINTID        Text      10         See EQUIPMENT Table

  EQUIPID        Text      25         See EQUIPMENT Table

  TASKNUM        Text      20         See TASK Table

  DUEDATE        Short     10         Format: 11/26/2000. Next date that a Work
                 Date                 Order has to be created in the CMMS for
                                      this Activity.

  PERFDATE       Short     10         Not Used
                 Date                 

  DURATION       2         numeric    Days to perform task from start to finish.
                                      Not necessarily the actual hours of work.
                                      Used to plan the number of days to spread
                                      the activity over in the daily schedule.

  DOWNTIME       2         numeric    Total number of hours the equipment must
                                      be down for this activity. Used to plan
                                      equipment outages.

  MUSTBEDOWN     Text      1          (Y or N)

  FREQ           Text      10         Cyclic time based code that allows the
                                      CMMS to generate this work again after
                                      each completion on the next correctly
                                      scheduled date. See Contract reference for
                                      Deferred Maintenance codes for the
                                      appropriate frequency codes.
  -------------- --------- ---------- ------------------------------------------

### Table:TASK INST TABLE

  -------------- ------ ------- ------------------------------------------
  INSTRCODE      Text   12      Unique ID for instruction assigned to
                                perform task.

  INSTRUCTIONS   Text   12      Text page with consistent format for
                                instructions used.
  -------------- ------ ------- ------------------------------------------

# 

# COSS Organization Chart\*

# Metrics -- All metrics related to this contract Examples include:

All AN-1-10 metrics

Metrics for High Visibility Items

Contractor-created metrics

Result from Customer Surveys

# Reports - All reports requested within this contract

# Examples include:

Mishap Reports\*

Daily Reports\*

Flash Reports\*

Spill Reports

Operations Logs

Open Constraints (MCC)

# Plans - All plans requested within this contract

# Examples include:

FCA Plan

Hurricane Plan

Environmental Compliance Plan

Mission Readiness Plan

# 

# Schedule Information - All schedule-related information requested within this contract

# Examples include:

Inspection schedules\*

Maintenance Schedules (Daily / Weekly / Monthly)\*

Maintenance Annual Work Plan\*

Outages\*

Crane Certifications\*

# Procedures - All procedures information requested within this contract

# Examples include:

Work Methods

Utility Procedures

Mission Exceptions\*

Hot Work Permits

Tunnel Access\*

Confined Space Access\*

Excavation and Boring Permits\*

# Safety - All safety related information requested within this contract

# Examples include:

Safety Procedures

Safety Inspection Reports (Internal / External)

Corrective Action Plans\*

Lost Work Day Cases\*

Mishaps\*

OSHA Recordables\*

# Work Orders -- All data related to open and closed 

**work orders**

# Examples include:

CMMS Queries\*

Work Authorization Document (WAD)\*

Move Requests\*

# 

# Quality Control - All quality control information requested within this contract

# Examples include:

Quality Control Plan

ISO Procedures / Work Methods

Inspection Reports (Internal / External)

Corrective Action Plans\*

# Facility Data -- Facility Related Data

Specific Items are:

Panel Schedules\*

Equipment/System List\*

# Who To Call

[NASA]{.underline} (Information to be provided by the Government)

Managers

Maintenance and Operations

Environmental

Logistics

Grounds

Information Technology

[Contractor]{.underline}

Managers

Maintenance and Operations

Environmental

Logistics

Grounds

Information Technology

\*Accessible to all JSC/EF/SCTF employees. All others are accessible by
COD / COSS personnel only.

NOTE: All data requested electronically within the contract scope of
work that fits the identified categories above shall be placed on this
website.

NOTE: The exact location of information to be placed on this website may
vary based upon CO direction.