Exhibit_A_-GEARSS_CDRLs.pdf

FA8823-15-R-0001

EXHIBIT A

CONTRACT DATA REQUIREMENTS LIST (CDRL)

INSTRUCTIONS

FOR

GPS ENGINEERING, ANALYSIS & REMOTE SITE SUSTAINMENT

(GEARSS)

7 AUGUST 2015

CONTRACT DATA REQUIREMENT LIST (CDRL) INSTRUCTIONS

Page: 2 of 10

1. SCOPE

These instructions supplement the Global Positioning System (GPS) Engineering, Analysis & Remote Site Sustainment (GEARSS) CDRL Exhibit A. All delivery instructions are specified in this CDRL package and related contract references.

2. GENERAL

The CDRL is a list of data requirements authorized for this specific procurement and are part of this contract. The CDRLs shall apply to all increments of GEARSS unless otherwise stated. The computer generated CDRL form and CDRL package specifies the data required to be delivered to the government, as well as the frequency and approval requirements. The Data Item Description (DID), listed on the CDRL form, was selected from the Acquisition Streamlining and Standardization Information System (ASSIST) http://www.assistdocs.com/search/search_basic.cfm and provides additional direction for data preparation.

3. COMMUNICATIONS

Any correspondence related to requests for data delivery deviations and amendments, additions or deletions to the CDRL form shall be addressed to the GEARSS Procuring Contracting Officer (PCO) with a courtesy copy to the GEARSS Program Manager, and GEARSS Data Management Officer (DMO).

4. CODES USED IN THE CDRL FORM

The directions for submittal and approval of data is indicated in Blocks 7, 8, 9, 10, 11, 12, 13, or 16 of the CDRL form. Usually, the direction is in the form of a code (explained below). The following abbreviations/codes are either extracted from DoD 5010.12-M or are common usage within the Space and Missiles Center (SMC).

4.1 Block 7, DD 250 Req

Block 7 of the CDRL form indicates whether Procurement Quality Assurance (PQA) inspections and acceptance of deliverable data by the CDRL form is required.

CODE INSPECTION ACCEPTANCE

SS Source (DD Form 250) Source (DD Form 250) DD Destination (DD Form 250) Destination (DD Form 250) SD Source (DD Form 250) Destination (DD Form 250) DS Destination (DD Form 250) Source (DD Form 250)

LT Letter of Transmittal only NO No inspection or acceptance required XX Inspection and acceptance requirements specified elsewhere in contract S Indicates the contractor’s facility D Indicates the primary distribution point

Page: 3 of 10

4.2 Block 8, Approval Code

CODE DESCRIPTION

A Approval required N/R Approval not required

4.3 Block 10, Frequency of Submittals

DAILY Daily WEKLY Weekly BI-WE Each 2 weeks MTHLY Monthly BI-MO Each 2 months QRTLY Quarterly ANNLY Annually SEMIA Each 6 months OTIME One time ONE-R One time and revisions R/ASR Revisions as required ASGEN As generated ASREQ As required* DFDEL Deferred delivery DFORD Deferred ordering DFREQ Deferred requisitioning ONE/P One time draft XTIME Multiple separate submittals (i.e., 2Time, 3Time)

* When ASREQ is used in Blocks 10, 11, 12 or 13 an explanation of the requirements must be entered in Block 16.

4.4 Blocks 12 and 13, Dates of First and Subsequent Submissions

ATP Authority To Proceed ASGEN As generated

ASREQ

CDR

As required* Critical Design Review

CA Contract Award CO Change Order CD Calendar Day(s)

Page: 4 of 10

CP/REQ Change page/as required CP/O Change page/(only) DCARC Defense Cost and Research Center DFDEL Deferred delivery FQT Formal Qualification Test FCA Functional Configuration Audit

PCA

PDR

Physical Configuration Audit Preliminary Design Review

TRR Test Readiness Review SA Supplemental Agreement WD Working Day(s)

* When ASREQ is used in Blocks 10, 11, 12 or 13 an explanation of the requirements must be entered in Block 16.

Page: 5 of 10

5. SUPPLEMENTAL DATA PREPARATION INSTRUCTIONS

5.1 Data Item Description (DID) Tailoring

The DID is a specification for the preparation of data. DID tailoring is reflected in Block 16 of the CDRL form. If tailoring is required a /T entered after the DID informs you that the DID has been tailored.

5.1.1 Block 4 tailoring is made to either relax preparation instructions or to tailor the DID to be in consonance with the source document tailoring contained in the Performance Work Statement (PWS).

5.2 Distribution Statement Marking

The designation in Block 9 of the CDRL form indicates that one of the following seven

(7) authorized distribution statements from DOD 5010.12-M shall be annotated on that technical data. Distribution statements will be selected to denote the audience the data is intended for: A distribution statement marking is distinct from and in addition to a security classification marking. Should Block 9 of the CDRL form and the DID be in conflict, Block 9 of the CDRL form shall take precedence. The following distribution statements are authorized for use in marking technical documents:

Distribution Statement A:

Approved for public release; distribution is unlimited.

Distribution Statement B:

Distribution authorized to U.S. government agencies only (fill in reason) (date of determina-tion). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement C:

Distribution authorized to U.S. government agencies and their contractors (fill in reason) (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement D:

Distribution authorized to the DoD and DoD contractors only (fill in reason) (date determination). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement E:

Distribution authorized to DoD components only (fill in reason) (date determination).

Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement F:

Further distribution only as directed by (insert controlling DoD office) (date of determination) or higher DoD authority.

Page: 6 of 10

Distribution Statement X:

Distribution authorized to U.S. government agencies and private individuals or enterprises eligible to obtain export-controlled technical data IAW regulations implementing 10 U.S.C. 140 (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

The following Table, lists examples of Distribution Statement usage on Technical Documents follow:

DISTRIBUTION

STATEMENT USED

DISTRIBUTION

STATEMENT

REASON FOR USE

Distribution Statement B Distribution authorized to U.S. government agencies only.

Company Sensitive information (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

Distribution Statement D

Distribution authorized to DoD and DoD contractors only.

Critical technology (date of determination). Other requests for this document shall be referred to (insert controlling DoD office).

Table 5-1 Distribution Statement Usage Example

5.3 Destruction Notice

All technical documents marked with Distribution Statements B, C, D, E, F, or X will also be marked with the following notice:

Destruction Notic For classified documents follow the procedures in DoD Manu 5220.22M, Industrial Security Manual, Chapters 4 and 5 , and DOD Regulation 5200.01 Volumes 1-4.1/ AFI 31-401 Informati Security Program, Chapter 6. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Page: 7 of 10

6. SUPPLEMENTAL DATA DELIVERY INSTRUCTIONS

6.1 General delivery requirements

All data, unless otherwise specified, will be submitted via GSIMS with link(s) to data, via email notification to assigned government representative(s) or GPL mailbox.

6.2 Due Dates

Due dates for delivery of data are to be construed as receipt at destination.

6.3 Late Delivery

Delivery of data is considered late if it does not arrive at its destination by 1600 hours (4:00 PM) Mountain Time on the date specified in Blocks 12, 13 and 16 of the CDRL. If the data delivery is post marked three business days before the due date, and due to U.S.

Postal Service handling it is not received on the due date, the CDRL delivery requirements are still met. The use of U.S. Postal Service “Express Mail” or overnight courier/delivery services must be coordinated and approved by the government prior to shipment of any CDRL delivery requirements.

6.4 Letter of Transmittal (Block 7)

Each data submittal shall be accompanied by a Letter of Transmittal (LT). Transmittal letters shall contain the following information:

1. Contractor letter reference number/contract number.

2. CDRL sequence number (i.e., A001).

3. Exact title and subtitle (if applicable) of the document being transmitted.

4. Document date, number, and revision information (if applicable).

5. Whether the document is a draft or final submittal.

6. For approval data: State “For Approval”.

7. If the document is a re-submittal, reference the government letter requesting re-submittal or disapproval of previous submittal.

8. For periodic reports: The report period that the document covers.

9. Distribution: Information disclosing the total contractual distribution being made per

Block 14 or Block 16 of the CDRL form.

6.5 Submittal Procedure

Unclassified CDRLs are submitted to the government via GPS Information Management System (GSIMS) and in accordance with this instruction. Classified CDRLs, documentation, are submitted in accordance with this instruction and are never to be posted to GSIMS.

6.5.1 Unclassified CDRL Submittal Procedure

Unclassified CDRLs will be submitted through GSIMS.

Page: 8 of 10

6.5.2 Classified CDRL Submittal Procedure

Classified CDRLs or portions of a CDRL, as applicable, shall be forwarded in accordance with (IAW) Appendix B of the DD-254.

Transmission of all classified information must be in accordance with all governing directives and instructions, DODM 5200.1, Volumes 1-4, and AFI 31-401, AF Information Security Program.

For Classified Disks send two (2) copies.

6.6 Distribution

The contractor is not authorized to provide copies of any data to any outside agency other than those listed in Block 14 or Block 16 of the CDRL form without specific approval of the Procuring Contracting Officer (PCO).

All official submittals shall be accompanied with a corresponding transmittal letter.

Address transmittal to SMC/PKL.

Page: 9 of 10

7. SUPPLEMENTAL DATA REVIEW AND APPROVAL PROCESS

7.1 Approval CDRLs

The letter “A” in Block 8 of the CDRL form indicates that the government must approve the data item. In addition, Block 16 of the form may contain additional directions.

Written Approval

Written approval indicates agreement or concurrence with the contractor furnished data only and shall not be construed as changing any of the terms or conditions of the subject contract. The approval authority shall be the PCO. Approval shall take the form of a letter signed by the PCO. Data items submitted for approval are NOT automatically approved without government approval.

Approved with Comment or Disapproved

The contractor shall revise data items Approved with Comments or Disapproved in accordance with the specific written comments transmitted with a PCO letter and resubmit not later than 30 calendar days from receipt of the Approval with Comments or Disapproval, unless otherwise directed. The resubmitted data will require a new approval cycle as indicated in Block 8 of the CDRL form.

Should the government have comments on the data item, the PCO letter will include a Comment Resolution Matrix (CRM).

7.2 DD Form 250 Requirements

Block 7 of the CDRL form indicates whether Procurement Quality Assurance inspections and acceptance of deliverable data by DD Form 250 are required. Information copies of DD Form 250 shall accompany each letter of transmittal for this category.

Page: 10 of 10

8. DATA ACCESSION LIST (DAL)

Requests from the PCO for data ordered from the Data Accession List (DAL) (with the application of DID DI-MGMT-81453A), maximum of two copies of each document order, shall be provided at no increase in contract price. Transmittal of any data so ordered shall include information notification to the GEARSS DMO.

TDP _____ TM _____ OTHER: X

1. DATA ITEM NO.

A001

PWS Item(s): 2.3.2.1

7. DD 250 REQ

LT

8. APP CODE

N/R SUBMISSION Block 16 Reg Repro

16. REMARKS SMC/PKP (PCO) BLK 16

BLK 4: SMC/PKP (CS) BLK 16

BLK 10: SMC/GPLX (PM) BLK 16

BLK 11: SMC/GPLX (COR) BLK 16

BLK 12:

BLK 13:

15. TOTAL

H. DATE

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

CONTRACT DATA REQUIREMENT LIST Form Approved

(1 Data Item) OMB No. 0704‐0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information.

Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704‐0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

Contract/PR No. listed in Block E.

0001, 1001, 2001, and 3001 A BLK 2

D. SYSTEM/ITEM E. CONTRACT/PR. NO. F. CONTRACTOR

GEARSS FA8823‐15‐C‐XXXX TBD

2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING SOURCE

SMC/GPL

9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

Block 16

In section 3.2 delete “’LR’ = Limited Rights. ‘RR’ = Restricted Rights (Computer Software only).” Add section 3.3: “Each submission shall be cumulative.”

Block 16

a. ADDRESSEE (See PWS

Item 7)

b. COPIES

D

11. AS OF DATE 13. DATE OF SUBSEQUENT

Draft

Final

Block 16

G. PREPARED BY I. APPROVED BY J. DATE

Vernon Miller Norman J. Churchill

Data Accession List (DAL)

DI-MGMT-81453A/T

First submission 30 DACA and monthly thereafter.

First submission 30 DACA and monthly thereafter.

First submission 30 DACA and monthly thereafter.

First submission 30 DACA and monthly thereafter.

Page 1 ofExcel Version ‐ DD FORM 1423‐1, FEB 2001

A002

See BLK 16 and:

7. DD 250 REQ

XX

8. APP CODE

SUBMISSION BLK 16 Reg Repro

16. REMARKS SMC/PKP (PCO) BLK 16

BLK 4: Contractor Format Acceptable: DIDs for Content Reference Only SMC/PKP (CS) BLK 16

Ref: DiDs DI‐MGMT‐80368A/T Funds and Manhour Expenditures

DI‐FNCL‐80912 Performance and Cost Report SMC/GPLX (PM) 1 BLK 16

DI‐FNCL‐81866 Other Direct Cost Report SMC/GPLX (COR) 1 BLK 16

WAWF (Invoice) 1 BLK 16

BLK 5:

BLK 7: Inspection and Acceptance Specified Elsewhere

Performance Assessment will be performed primarily by Quality Assurance Personnel:

QA areas include Quality, Accuracy, Timeliness, Effectiveness, and Meaningfulness

BLK 8:

BLK 9: Only as directed by Controlling Offices (SMC/MCL and SMC/PKP)

BLK 10: Monthly; Prior to Invoicing in WAWF

BLK 11: As of each calendar month EOM closeout prior to 2n1 Invoice in WAWF or equiv

BLK 12:

BLK 13: Monthly; No Later Than 5 work days prior to monthly invoicing action.

BLK 14:

NOTE: Include an electronic copy attached to applicable invoice.

Identification:

Example: FA8823‐15‐C‐XXX A002 Initial MCPSR 01 Feb 2016.doc

Printed/Embedded: Header/Footer ‐ Same Information as Electronic File Name

15. TOTAL

H. DATE

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

CONTRACT DATA REQUIREMENT LIST Form Approved

(1 Data Item) OMB No. 0704‐0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704‐0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

Monthly Contractor Performance Status Report (MCPSR) Evidence of Service

0001, 1001, 2001, and 3001 A BLK 2

D. SYSTEM/ITEM E. CONTRACT/PR. NO. F. CONTRACTOR

GEARSS FA8823‐15‐C‐XXXX TBD

2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING SOURCE

BLK 16 PWS Item(s): Para 3.1.1 SMC/GPL

Govt Review (Approval/Disapproval) Comments within two (2) work days after receipt of each submission.

9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

BLK 16 BLK 16

a. ADDRESSEE (See PWS

Item 7)

b. COPIES

F

11. AS OF DATE 13. DATE OF SUBSEQUENT

Draft

Final

See BLK 16

The contractor shall prepare performance status reports to include, at a minimum, information regarding issues and resolutions, and cost/fund status on applicable cost CLINs. The report will identify requests, authorizations and approvals for all expenditures for the period. This monthly report will identify manpower reporting information to be reported annually in the eCRMA system. Contractor shall prepare and distribute agendas, minutes and perform Action

Item tracking and reporting, as applicable.

Excel Version ‐ DD FORM 1423‐1, FEB 2001

Note: Cost Reimbursable reporting status may coincide with Ktr Monthly Accounting Cycle.

No earlier than 30 calendar days after contract effective date and 5 work days prior to monthly invoicing action.

Information to be included supports payment for services provided in the month prior to support invoicing for services in arrears.

Include an electronic file in MS Office compatible format. Files to be be editable. CD‐ROM or electronic transmission acceptable.

Electronic ‐ File Name will be unique for each submission. Include contract number, Data Item

No., Submission Number

G. PREPARED BY I. APPROVED BY J. DATE

A003 Student Guide

PWS Item(s): 3.1.4

7. DD 250 REQ

NO

8. APP CODE

N/R SUBMISSION ASREQ Reg Repro

16. REMARKS SMC/PKP (PCO) BLK 16

BLK 3: SMC/PKP (CS) BLK 16

BLK 4: Contractor Format Acceptable: DIDs for Content Reference Only SMC/GPLX (PM) BLK 16

Ref: DiDs DI‐MISC‐81456 Student Guide SMC/GPLX (COR) BLK 16

BLK 5:

BLK 10:

BLK 11:

BLK 13:

BLK 14:

15. TOTAL

H. DATE

All subsequent updates must coincide with PCA for associated modifications.

Include an electronic file in MS Office compatible format. Files to be be editable. CD‐ROM or electronic transmission acceptable

The NAO PTS/PTG training document must be updated prior to final approval for system upgrade.

The NAO PTS/PTG training document must be updated when the Government modifies the operational system and results in changes to system operations that would require updated training for the NAO.

The Government will provide a baseline NAO PTS/PTG at contract award. (See attachment below)

Network Administrative Officer (NAO) Position Training Standard (PTS)/Position Training Guide (PTG)

G. PREPARED BY I. APPROVED BY J. DATE

Vernon Miller Norman J. Churchill

13. DATE OF SUBSEQUENT

Draft

Final

ASREQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

ASREQ PCA

a. ADDRESSEE (See PWS

Item 7)

b. COPIES

F

11. AS OF DATE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING SOURCE

BLK 16 SMC/GPL

NAO PTS/PTG

0001/1001,2001,3001 A BLK 2

D. SYSTEM/ITEM E. CONTRACT/PR. NO. F. CONTRACTOR

GEARSS FA8823‐15‐C‐XXXX TBD

2. TITLE OF DATA ITEM 3. SUBTITLE

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

CONTRACT DATA REQUIREMENT LIST Form Approved

(1 Data Item) OMB No. 0704‐0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information.

Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704‐0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

Contract/PR No. listed in Block E.

(2 SOPS) NAO

PTS 15 Oct 12

Section 3: 1 of 10

SECTION III – POSITION TASK LIST

2 SOPS

Network Administration Operator

Task List

Training Start Date: ___________________________

Trainee Name Trainer Name Print Print

Sign Sign

Mandatory SCN Text courses:

Note: If the Trainee has already completed any of these courses via other PTSs, it’s the option of the Section Lead whether these courses should be completed again or not. SCN completion dates are recorded in the Ops Spt TDB.

Courses Test Complete

Initials

(Trainer or TC)

(optional)

(optional)

(optional)

(optional)

TRAINER/TRAINEE NOTE: If equipment or job situation makes actual demonstration performance on a given task unavailable or inaccessible, the Trainer will have the Trainee “demonstrate” their knowledge/ability by thoroughly explaining and simulating procedures utilizing the TO and/or local job aids without actually performing the task. The task may then be considered “completed”.

Section 3: 2 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee & Trainer Initials

1 Safety and Security

1.1 Safety

1.1.1 Locate Module 11 and Building 400 layout and exits

C

1.1.2 2 SOPS duress words and evacuation points procedures

3c

1.1.3 2 SOPS Fire and Evacuation procedures

1.1.4 2 SOPS Recall process

1.1.5 Know the accident, injury and illness process

1.1.6 Know natural disaster and severe weather process

1.2 Security

1.2.1 Know the bomb threat and suspicious object process

1.2.2 Know the 2 SOPS Force Protection Condition (FPCON), Random Anti-terrorism Measures (RAM) and Information Condition (INFOCON) policies and processes

1.2.3 Handling classified materials

1.2.4 Search and secure procedures

1.2.5 Entry and escort procedures

2 GPS Overview

2.1 GPS Mission

Understand the GPS Constellation Operations mission Understand the GPS Operations Center mission

2.2

GPS Organizations

Air Force Space Command (AFSPC) GPS Wing (SMC)

14 AF

50 SW

50 OG

2 SOPS

19 SOPS

Level 2 Software Maintenance Level 1 Software Maintenance GPS Remote Sites Air Force Satellite Control Network (AFSCN) Remote Tracking Station (RTS)

Section 3: 3 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

2.3

GPS Leadership

50 SW Commander 50 OG Commander 2 SOPS Commander 2 SOPS Director of Operations 2 SOPS Maintenance 2 SOPS Flight Commander

2.4 GPS Crew Positions

Mission Commander Mission Chief Satellite Vehicle Operator Payload Systems Operator NAV Warfare Officer Satellite Systems Operator Network Administration Operator Mission Support Personnel Schedule Engineer Experimental Navigation Operator Analyst On-Call

3 Site Overview

3.1 Master Control Station (MCS)

3.1.1 MCS Overview

Understand the overall mission and work centers of the MCS

Section 3: 4 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

3.1.2 MCS Equipment

Understand how the servers are connected within the

MCS

Know MCS servers & workstations basic operations Consolidated Operator Support Environment

(COSE) workstations Administration (Admin) workstations Common servers Mission servers Telemetry, Tracking and Commanding (TT&C) servers L-Band servers Gateway servers Crypto servers Lab Controller (LABC) workstation Operations Transfer Administration (xadmin) workstations Operations Transfer (xfer) servers Automated Remote Tracking Station (ARTS) workstations System Log Evaluation Utility Transfer Host

(SLEUTH) server Primary Archive Controller Remote Archive

Transfer (PACRAT) server Electronic Scheduler Dissemination (ESD) Distributed Communications Controller (DCC) Almanac workstation Virus Checker workstation MCS Offline workstation (MOW) Temporary Analysis Tool for 2 SOPS (TAT-2)

Understand the Redundant Arrays of Inexpensive

Disks (RAID) drives utilized by the AEP system

Understand the tape backup system utilized by the AEP system

3.1.3 MCS Communication

Know all routers providing communications to Remote Sites and External Agencies

Understand the communication path between the MCS and Remote Sites Ascension Island Diego Garcia Island Kwajalein Atoll Cape Canaveral Hawaii Colorado Springs

Section 3: 5 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

3.2 Alternate MCS

3.2.1 Alternate MCS Overview

Know the overall mission and work centers of the

Alternate MCS

3.2.2 Alternate MCS Equipment

Understand how the servers are connected within the

Alternate MCS

3.2.3 Alternate MCS Communication

Know all routers providing communications to

Remote Sites and External Agencies

Understand the communication path between the Alternate MCS and Remote Sites

3.3 Remote Sites

3.3.1 Remote Site Overview

Understand the overall mission of the GPS Remote

Sites

3.3.2 Remote Site Equipment

Understand how the Remote Site equipment is connected

3.4 Remote Tracking Stations (RTS)

RTS Mission and Equipment Understand the overall mission of the RTSs Know the equipment used to utilize the RTSs Understand the communication path between the

MCS and the RTSs

3.5 External Agencies

Understand each External Agency supported by 2 SOPS and the communication between them and the

MCS

Integrated Mission Operation Support Center

(IMOSC)

National Geospatial-Intelligence Agency (NGA) GPS Information System (GPSIS) High Accuracy Navigation User (HANU) Air Force Tactical Application Center (AFTAC)

Section 3: 6 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

4 Basic NAO Instructions

4.1 Technical Orders (TO)

4.1.1 Demonstrate TO checklist discipline

4.1.2 Know systems that can access TOs

4.1.3 Know which books are available:

Orbital Operations Handbook (OOH) Job Aids Reports Guide Schedule Control Satellite Vehicle

4.1.4 Understand the different chapters in the Satellite Vehicle TOs

4.1.5 Opening and searching within TOs

4.1.6 Printing within TOs

4.2 UNIX Commands

4.2.1 Know UNIX Syntax

4.2.2 Perform basic UNIX Commands

4.3 Snapshot Print Utility

Utilize Snapshot Print Utility window

4.4 Voice Communications

4.4.1 Operations floor telephone procedures

4.4.2 Utilize Integrated Services Telephone (IST)

4.4.3 Utilize Secure Telephone Unit – Third Generation (STU-III)

4.5 Computer Software Configuration Items (CSCI)

Understand the CSCIs within AEP

4.6 Oracle Databases

Understand the different Oracle databases within AEP

Section 3: 7 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

5 Administration Workstation

5.1 Spectrum

5.1.1 Basic function and opening required screens

5.1.2 Understand color codes

5.1.3 Utilize Performance Meter window

5.1.4 Utilize Alarms window

5.1.5 “Drill Down” process

5.2 System Status Monitor

5.2.1 Basic function and launching System Status Monitor

5.2.2 Navigating first level of System Status Monitor

5.2.3 Navigating second level of System Status Monitor

5.2.4 Understand the Alarm, Warning and Error (AWE) window

5.2.5 Understand the Operations and Control window

5.3 Mission Operations Transfer

5.3.1 Basic function and launching the Mission Operations

Transfer window

5.3.2 Utilizing the Set States, States Compatibility and Site States functions

5.3.3 Work Item Queues

5.3.4 Understand and clear alarms

5.3.5 Manipulate Work Item List

5.4 COMET Commander

Basic function and launching the COMET Commander window

Section 3: 8 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

6 COSE Workstation

6.1 GPS Graphical Interface

6.1.1 Basic function and launching of GPS Graphical Interface

6.1.2 Opening desired applications

6.1.3 Accessing and utilizing programs under the:

GGI LOG menu GGI TTC menu GGI NAV menu GGI Applications menu

6.2 Mission Scheduler

6.2.1 Basic function of the Mission Scheduler

6.2.2 Launching Schedule Control window

6.2.3 Utilizing the Schedule Control window

6.2.4 Accessing and utilizing required screens within Schedule Control window

6.3 Hierarchy

6.3.1 Launching Hierarchy window

6.3.2 Accessing and utilizing the Ground Antenna Summary

window

6.3.3 Accessing and utilizing the Monitor Station Summary

window

6.4 Ground Site Control and Status

6.4.1 Launching the Ground Site Control and Status windows

6.4.2 Utilizing the Automated Remote Tracking Station Ground

Site and Control windows

6.4.3 Utilizing the Ground Antenna and Monitor Station Ground Site and Control windows

6.5 Ground Control

6.5.1 Accessing the Ground Control windows

6.5.2 Maneuvering through all Ground Control windows

6.5.3 Controlling Remote Site equipment using Ground Station

Equipment Control feature

Section 3: 9 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

7 Reoccurring/Administrative Crew Actions

7.1 Crew Changeover

7.1.1 Crew Changeover process

7.1.2 Off going procedures

7.1.3 Oncoming procedures

7.2 Problem Reporting

Hardware/Software problem reporting process

7.3 Satellite Vehicle Pre-Pass

Perform proper satellite vehicle Pre-Pass activities

7.4 Scheduled Maintenance

7.4.1 Readying Remote Site for scheduled maintenance

7.4.2 Returning Remote Site from scheduled maintenance

7.5 Communication Maintenance

Clearing MCS for communication maintenance

Section 3: 10 of 10

Position Tasks (Knowledge and performance) Code Tng Start

Tng Comp

Trainee &

8 Routine and Anomalous Work Actions

8.1 General Information

8.1.1 Troubleshooting Concepts

Understand the Restore-to-Ops concept Understand troubleshooting techniques

8.1.2 Log and Core Files

Accessing log and core files in the AEP system

8.1.3 Failover

Understand the Redundancy, Hot Backup, Failover and Manual Failover concepts

Identify the hardware/software that supports

Redundancy, Hot Backup and Failover

8.2 Know when and how to utilize TO procedures for problems

with:

Communications Routers Commanding

COSE

MCS

Workstations RTSs GAs and MSs Processes Exporting Miscellaneous

Section 4: 1 of 3

SECTION IV – POSITION EVALUATION GUIDE

Network Administration Operator (NAO)

Guidance for the Certifier:

The Position Certification check is strictly pass/fail:

Whenever possible, pass/fail is evaluated by the end product quality.

Observe trainee’s checklist compliance throughout the process.

All tasks must be passed for positional certification.

Sign off on all tasks passed regardless of overall certification results.

If any tasks are failed:

Corrective training must be accomplished for those tasks; followed by a certification check covering those failed tasks.

These tasks will be signed off once they have been performed successfully.

Re-evaluation will be documented on the same sheet as the initial Certification check.

Comments & Recommended Improvement Area usage:

Include task number referred to when commenting on task performance.

Any task failures.

Minor errors not serious enough to warrant task failure (including deficiencies in console operations, if applicable).

Provide feedback to training program/trainee on weak/strong areas.

Section 4: 2 of 3

POSITION CERTIFICATION CHECK

Reminder: If equipment or job situation makes actual demonstration performance on a given task unavailable or inaccessible, the Certifier will have the Trainee “demonstrate” his/her knowledge/ability by thoroughly explaining and simulating procedures utilizing the TO and/or local job aids without actually performing the task. The task may then be considered “completed”.

NOTEs:

1. Each Task will be evaluated via single Task evaluation.

Successful completion of a task evaluation qualifies the individual to perform that task.

2. The task numbers are not related to the task numbers listed in Section III

3. P/F/NA = Pass/Fail/Not Applicable

Task P/F/NA 1 Routine/Administrative Tasks

1.1. Perform Crew/NAO Changeover

1.2. Perform NAO Logging Activities

1.3. Demonstrate TO discipline and crew protocol

2 Routine Activities

2.1. Demonstrate CDE navigation

2.2. Perform terminal window activities

2.3. Perform all necessary system checks

2.4. Perform all necessary communication checks

2.5. Perform prepass, pass, and postpass activities

2.6. Perform GA readiness test

2.7. Perform Mission-Ops transfer activities

3 Problem Resolution

3.1. Demonstrate System Troubleshooting techniques and

recovery actions

3.2. Demonstrate Communication Troubleshooting techniques and recovery

Brief CC/DO at squadron request

Section 4: 3 of 3

RECOMMENDED IMPROVEMENT AREAS:

TRAINEE PERFORMANCE: SATISFACTORY: ________ UNSATISFACTORY: ________

POSITION QUALIFICATION

Trainee Signature: Date:

Certifier Signature: Date:

Certifying Official Signature: Date:

A004 GPS RST Onsite Work Log (GROWL)

7. DD 250 REQ

NO

8. APP CODE

N/R SUBMISSION Block 16 Reg Repro

16. REMARKS SMC/GPLH (PM) BLK 16

BLK 4: 50 SCS/SCP BLK 16

21 SOPS/MA BLK 16

BLK 10: 23 SOPS/MA BLK 16

BLK 11: 2 SOPS/MA BLK 16

BLK 12:

BLK 13:

15. TOTAL

H. DATE

PWS Item(s): 3.3.1

Contractor Format Acceptable: DIDs for Content Reference Only

NOTE: Must include the information at the attachment below.

J. DATE

Vernon Miller Norman J. Churchill

Each business day.

At the end of each business day.

At the end of the first business day of the GEARSS contract.

At the end of each business day through the life of the GEARSS contract.

G. PREPARED BY I. APPROVED BY

Block 16

a. ADDRESSEE (See PWS

Item 7)

b. COPIES

E

11. AS OF DATE 13. DATE OF SUBSEQUENT

Draft

Final

Block 16

9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

Daily

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING SOURCE

DI-MISC-80508 SMC/GPL

Technical Report

0001/1001,2001,3001 A BLK 2

D. SYSTEM/ITEM E. CONTRACT/PR. NO. F. CONTRACTOR

GEARSS FA8823‐15‐C‐XXXX TBD

2. TITLE OF DATA ITEM 3. SUBTITLE

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

CONTRACT DATA REQUIREMENT LIST Form Approved

(1 Data Item) OMB No. 0704‐0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information.

Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704‐0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the

Contract/PR No. listed in Block E.

FOR OFFICIAL USE ONLY

FOR OFFICIAL USE ONLY

From:

To:

Subject: Daily Activity Log

Julian Date:

J-Day/Z-time Comments Initials

GA Status – MS Status –

HPA Device Failures:

A$ - B$ -

COMM Status:

HVAC Status:

POWER Status:

GA Status – MS Status –

HPA Device Failures:

A$ - B$ -

FS#1 E Mult:

FS#2 E Mult:

On call site tech-

COMM Status:

HVAC Status:

POWER Status:

A005 GPS RST Onsite Weekly Log Enhanced Report (GROWLER)

7. DD 250 REQ

NO

8. APP CODE

N/R SUBMISSION Block 16 Reg Repro

16. REMARKS SMC/GPLH (PM) BLK 16

BLK 4: 50 SCS/SCP BLK 16

21 SOPS/MA BLK 16

BLK 10: 23 SOPS/MA BLK 16

BLK 11: 2 SOPS/MA BLK 16

BLK 12:

BLK 13:

15. TOTAL

H. DATE

Page 1 of

J. DATE

Vernon Miller Norman J. Churchill Excel Version ‐ DD FORM 1423‐1, FEB 2001

Each business week.

At the end of each business week.

At the end of the first business week of the GEARSS contract.

At the end of each business week through the life of the GEARSS contract.

G. PREPARED BY I. APPROVED BY

NOTE: Must include the information at the attachment below.

9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

Weekly Block 16

a. ADDRESSEE (See PWS

Item 7)

b. COPIES

E

11. AS OF DATE 13. DATE OF SUBSEQUENT

Draft

Final

Block 16

Contractor Format Acceptable: DIDs for Content Reference Only

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING SOURCE

DI-MISC-80508 PWS Item(s): 3.3.1 SMC/GPL

Technical Report

0001/1001,2001,3001 A BLK 2

D. SYSTEM/ITEM E. CONTRACT/PR. NO. F. CONTRACTOR

GEARSS FA8823‐15‐C‐XXXX TBD

2. TITLE OF DATA ITEM 3. SUBTITLE

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

CONTRACT DATA REQUIREMENT LIST Form Approved

(1 Data Item) OMB No. 0704‐0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704‐0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

For Official Use Only (FOUO)

Interoffice Memo

To:

From:

Date:

Subject: Weekly Activity Report, Week of XX/XX/XX New Job Numbers:

GA Status: A$: B$:

MS Status:

COMM Status: COMM line #1 COMM line #2 HVAC Status:

POWER Status:

Major Events Past 7 Days:

Major Issues Past 7 Days:

Major Events Next 10 Days:

Major Issues Next 10 Days:

GA Open Jobs/JCNs:

GA Closed Jobs/JCNs:

MS Open Jobs/JCNs:

MS Closed Jobs/JCNs:

Items on Order MICAP:

FSP Inventory Items on Order:

Supply Issues:

OT/Call Outs:

Plans for Next Period/New Upcoming Projects (not mentioned above)

Training Accomplished:

Facilities Projects/other items (not mentioned above):

Upcoming/Visitors on Site:

Name Purpose of Visit Organization Period of Visit

Vacation Schedule:

Miscellaneous items: