Page 1 14 December 2001 DBOR Release 2.4.0 Features Title Slide AT&T DBOR

Page 114 December 2001

DBOR Release 2.4.0 Features

Title SlideAT&T DBORAT&T DBOR



1. Describe the SANS Web Form Process & Terms

2. How to Create a New SANS Web Forms

3. How to Update and Save the Form

4. How the BOU Integrity Check Button Operates

5. Describe the SANS Web Form Final Version Process.

6. Describe the Actions Completed by the IM/AMs.

Training Agenda

SANS Web Form



Users view forms in Electronic Library by Project ID from SANS Web Form.

DBOR DBOR E-LibE-Lib

BOU Reps Populate AllSANS Web Form Fields

and Contact IM/AM. After Providing SANS ID#, BOU Reps Inputs

Date Submitted to IM/AM and Clicks on BOU

Integrity Check Button.

IM/AM Updates SANS Web Form Section #6 with

Project IDs and Email Submission Message

(ESM) Numbers.

2.4.0

NCOS/MVS SANS Web Form Processing



SANS Web Form Process

BOU rep Fills Out All Sections of SANS Web

Form Except Sections 5 &

6

BOU Inputs Submitted Date and

Completes Integrity Check

Successfully

BOU Gets IM/AM

Name from NCOS

Contacts List &

Contacts IM/AM

IM/AM Creates

Projects to Generate

Project IDs

IM/AM Completes Section 5 and 6 per

SRT/Project

IM/AM Submits

Final Version and

ESM(s)

AcqMgt Completes

PIP Compliance

Step #1

DBOR

Locks Email Submission Message &

Project IDs



SANS Web Form Features & Terms1. Section Tabs – SANS Web Form Tabs Contain the NCOS SANS

Form Sections. Saves Changes Automatically Between Tabs.

2. Detail Records – Contain MVS & Unix/NT Hardware and Software Information as Section 3 in SANS Form.

3. BOU Integrity Check – Confirms All Required Fields Populated and Indicates Invalid Fields.

4. Submit Final Version – Confirms IM/AM Fields Populated and Generates Email Submission Message and Project ID Definition Form.

5. Locking – SANS Web Form and ESM / Project ID Form.

6. SANS ID – SANS Tracking Number Used to Manage Projects.



AT&T Secured Logon Authentication



SANS Web Form Significant Fields

1. Asset Ownership – IBM or AT&T.

2. Business Operating Unit (BOU) – Used to Generate Project ID List for Email Submission Messages.

3. BOU Director – Used to Generate Project ID List for Email Submission Messages.

4. Service Request Type (SRT) – Used to Generate Project ID List for Email Submission Messages per SRT.

5. Project IDs – Can Only Be Selected Once on Any SANS Web Form.



Web Based Forms Limitations

1. After BOU Integrity Check, Should Not Press Browser’s Back Button because Web Page Back Restores to Previous Contents, Not Changes. Best to always click links on current page where provided.

2. To Save Changes on an Updated Page without Changing Tabs, Press the Current Page’s Tab and Information is Saved.



Title

Creating a New SANS Web FormCreating a New SANS Web Form



e-Library Main Menu



Creating a New SANS Web Form



Create New SANS Web Form



Title

Query an Existing Query an Existing SANS Web FormSANS Web Form



SANS Web Form Query to Update



SANS Web Form Query Selection Parameters



SANS Web Form Query Results



SANS Web Form Query by SANS ID



SANS Web Form Populated



Title

Updating a SANS Web FormsUpdating a SANS Web Forms



SANS Web Form Base Buttons

Saves Changes and Unlocks SANS Web Form HRID Lock.

Confirms All SANS Web Form Fields Populated.

Generates ESM/Project ID Web Form After Confirming All SANS Web Form Fields Populated.



SANS Web Form Save & Exit Web Page

After clicking the Save & Exit Button, a page appears similar to the illustration below.



SANS Web Form BOU Integrity Check Results

After clicking the BOU Integrity Check Button on an incomplete SANS Web Form, a page appears similar to the illustration

below. Please do not click Browser’s Back Button.



SANS Web Form BOU Integrity Check Results

After clicking the BOU Integrity Check Button on a complete SANS Web Form, a page appears similar to the illustration

below. Please do not click Browser’s Back Button.



Title

Updating Resources Detail Updating Resources Detail RecordsRecords



SANS Web Form MVS & Unix/NT Resources Tabs



SANS Web Form MVS & Unix/NT Resources Tabs



Adding Unix/NT Resources SRTs



Adding Unix/NT Resources Detail Records


DBOR Release 2.4.0 FeaturesUpdating Unix/NT (Server) Detail

Records


DBOR Release 2.4.0 FeaturesSANS Web Form Detail Record

Summaries



SANS Web Form Print-Ready Version



Future NCOS Web Form Automation Target Dates

SANS Web Form – 17 December 2001

AATP/PE Web Forms – 25 March 2002

SRT #1, 2, 7, and 8 Web Forms – 5 August 2002

SRT #1A and 4 Web Forms – TBD

Remaining SRT Web Forms – TBD



Title

IM/AM Final Version ProcessIM/AM Final Version Process



Additional DBOR Release Features

1. Automatic Implementation Phase Start with AT&T and IBM Acquisition Phase Start.

2. SRT #4 Disconnects Processed Through IPPP and IAP.

3. SRT #1A Reuse Processed Through IPPP Step #1 only, then IAP.

4. Infrastructure Acquisition Projects Handled as Separate Project ID and Processed Through IPPP Step #1 only, then IAP.



Submit Final IM/AM Version Process

IM/AM Completes

Integrity Check

Successfully

IM/AM Creates

Projects to Generate

Project IDs

IM/AM Completes Section 5 and 6 per

SRT/Project

IM/AM Submits

Final Version and

ESM(s)

AcqMgt Completes

PIP Compliance

Step #1

DBOR

Locks Email Submission Message &

Project IDs



Submit Final IM/AM Version Results

After IM/AM clicks on the Submit Final Button, a page appears similar to the illustration below. This allows user to Generate

Section 6. Note: Please do not click Browser’s Back Button.



Submit Final IM/AM Version Process

1. Start DBOR Projects after BOU Integrity Check Successful.

2. All Fields Must Exactly Match the DBOR Project Record with BOU, Director, and SRT Number.

3. Failure to Comply Impact: Project IDs Cannot Be Selected from Options.

4. BOU, Director, and Asset Ownership fields will be locked FOREVER after Final Version Submitted.

5. After Final Version Submitted, the ESM and Project IDs can be Defined.

6. SANS Web Form Locked after IBM Procurement Planning Phase Step #1 Completed. After Locked, Cannot Be Changed.

IMPORTANT NOTICES



NCOS Project ID Assignment Rules

1. There is one Project ID defined per SRT.2. There is one Project ID per SRT where the Installation or

Removal Dates are within 2 weeks of each other.3. There is one Project ID per IBM Acquisition and one per

AT&T Acquisition based on Asset Ownership and Retained Vendor state.

4. For SRT #7, 7A, 8, 8A, there is one Project ID per IBM Suppliers and one per AT&T Retained Vendors.

5. For IBM Projects, there will be one Project ID per Infrastructure and one per Production/Development Platform Use Type.

6. There is one Project ID defined per Project Type of CON, MVS, and NCI.



Defining ESM and Project IDs

Project ID #1

SANS Web Form (SWF)

Project ID #1

ESM#1

ESM #3 & Project ID #3ESM#4

Project ID #2

NCOS SRT#7

Server Detail #1

Server Detail #2

Server Detail #3

Server Detail # n

NCOS SRT#1

Server Detail #1

Server Detail #2

Server Detail #3

Server Detail # n

NCOS SRT#5(AT&T Only)

Server Detail #1

Server Detail #2

Server Detail #3

Server Detail # n

ESM#5

Project ID #4 ESM#2

MVS SRT#7

Platform Detail #1

Platform Detail #2

Platform Detail #3

Platform Detail # n



Update BOU Budget/Funding Tab



ESM/Project ID Definition Web Form New



ESM/Project ID Definition Web Form Saved

Documents

Page 1 14 December 2001 DBOR Release 2.4.0 Features Title Slide AT&T DBOR