PTS# 13697

NASR Geographical Objectives Reporting

Business Requirements Document

Table of Contents

1 Introduction ......................................................................................................................... 32
1.1 USER PROBLEM/ PROJECT BACKGROUND....................................................................... 32
1.2 TO-BE BUSINESS USER ROLES ...................................................................................... 32
2 Behavioral Business Requirements ................................................................................. 43
2.1 BR-001: SENDING VENDOR PROCESS CHANGES ............................................................ 43
2.2 BR-002: NASR STORING MONTHLY OBJECTIVE FILE(S) ................................................... 54
2.3 BR-003: NASR REPORTING CHANGES .......................................................................... 65
2.4 BR-004: NASR “BLOCKING” FLAG FOR MODEL AND GEOGRAPHY LEVEL REPORTING .... 87
2.5 BR-005: NASR MID-MONTH BAC OBJECTIVE CHANGES............................................... 109
2.6 BR-006: REPROCESSING THE 7 GEOGRAPHICAL LEVELS AT MID-MONTH...................... 1211
2.7 BR-007: SUMMING HISTORICAL OBJECTIVES .............................................................. 1312
2.8 BR-008: DATA LOAD STATUS SCREEN UPDATES ........................................................ 1413
Behavioral Models ................................................................................................................... 1615
2.9 CONCEPTUAL INFORMATION MODEL............................................................................ 1615
3 Non-Functional Business Requirements ..................................................................... 1615
3.1 USABILITY REQUIREMENTS ......................................................................................... 1615
3.2 BUSINESS SPEEDS AND FEEDS .................................................................................. 1615
3.3 ADDITIONAL NON-FUNCTIONAL BUSINESS REQUIREMENTS .......................................... 1615
4 Legal Requirements ........................................................................................................ 1615
Formatted: Default Paragraph Font, Font: Bold
4.1 COMPLIANCE REQUIREMENTS ..................................................................................... 1615
4.2 GLOBALIZATION REQUIREMENTS ................................................................................ 1615 Formatted: Default Paragraph Font, Font: Bold
4.3 SECURITY REQUIREMENTS .......................................................................................... 1615 Formatted: Default Paragraph Font, Font: Bold, Small caps
5 Reporting Requirements ................................................................................................ 1615 Formatted: Default Paragraph Font, Font: Bold, Small caps

6 Operational Requirements ............................................................................................. 1716 Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
6.1 RUNTIME REQUIREMENTS ........................................................................................... 1716
6.2 DATA ARCHIVING REQUIREMENTS ............................................................................... 1716 Formatted: Default Paragraph Font, Font: Bold
6.3 ADDITIONAL OPERATIONAL REQUIREMENTS ................................................................ 1716 Formatted: Default Paragraph Font, Font: Bold
7 Project Definitions & Acronyms .................................................................................... 1716 Formatted: Default Paragraph Font, Font: Bold, Small caps

1 Introduction ........................................................................................................................... 2 Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
1.1 USER PROBLEM/ PROJECT BACKGROUND......................................................................... 2
1.2 TO-BE BUSINESS USER ROLES ........................................................................................ 2 Formatted: Default Paragraph Font, Font: Bold, Small caps

2 Behavioral Business Requirements ................................................................................... 3 Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
2.1 BR-001: SENDING VENDOR PROCESS CHANGES .............................................................. 3
2.2 BR-002: NASR STORING MONTHLY OBJECTIVE FILE(S) ..................................................... 4 Formatted: Default Paragraph Font, Font: Bold, Small caps
2.3 BR-003: NASR REPORTING CHANGES ............................................................................ 5 Formatted: Default Paragraph Font, Font: Bold, Small caps
2.4 BR-004: NASR “BLOCKING” FLAG FOR GEOGRAPHY LEVEL REPORTING ......................... 7
Formatted: Default Paragraph Font, Font: Bold, Small caps
2.5 BR-005: NASR MID-MONTH BAC OBJECTIVE CHANGES................................................... 9
Formatted: Default Paragraph Font, Font: Bold, Small caps
NASR Geographical Business Requirements Document Doc. Version 1.01
Objectives Reporting
SDP Template Version 1.4 Page 1 of 19
 2.6 BR-006: REPROCESSING THE 7 GEOGRAPHICAL LEVELS AT MID-MONTH.......................... 11 Formatted: Default Paragraph Font, Font: Bold, Small caps
2.7 BR-007: SUMMING HISTORICAL OBJECTIVES .................................................................. 12 Formatted: Default Paragraph Font, Font: Bold, Small caps
Behavioral Models ....................................................................................................................... 13 Formatted: Default Paragraph Font, Font: Bold, Small caps
2.8 CONCEPTUAL INFORMATION MODEL................................................................................ 13 Formatted: Default Paragraph Font, Font: Bold, Small caps

3 Non-Functional Business Requirements ......................................................................... 13 Formatted: Default Paragraph Font, Font: Bold
Formatted: Default Paragraph Font, Font: Bold, Small caps
3.1 USABILITY REQUIREMENTS ............................................................................................. 13
3.2 BUSINESS SPEEDS AND FEEDS ...................................................................................... 13 Formatted: Default Paragraph Font, Font: Bold, Small caps
3.3 ADDITIONAL NON-FUNCTIONAL BUSINESS REQUIREMENTS .............................................. 13 Formatted: Default Paragraph Font, Font: Bold
4 Legal Requirements ............................................................................................................ 13 Formatted: Default Paragraph Font, Font: Bold

4.1 COMPLIANCE REQUIREMENTS ......................................................................................... 13 Formatted: Default Paragraph Font, Font: Bold, Small caps
4.2 GLOBALIZATION REQUIREMENTS .................................................................................... 13 Formatted: Default Paragraph Font, Font: Bold, Small caps
4.3 SECURITY REQUIREMENTS .............................................................................................. 13 Formatted: Default Paragraph Font, Font: Bold, Small caps
5 Reporting Requirements .................................................................................................... 13 Formatted: Default Paragraph Font, Font: Bold, Small caps
6 Operational Requirements ................................................................................................. 14 Formatted: Default Paragraph Font, Font: Bold, Small caps

6.1 RUNTIME REQUIREMENTS ............................................................................................... 14 Formatted: Default Paragraph Font, Font: Bold, Small caps
6.2 DATA ARCHIVING REQUIREMENTS ................................................................................... 14 Formatted: Default Paragraph Font, Font: Bold
6.3 ADDITIONAL OPERATIONAL REQUIREMENTS .................................................................... 14 Formatted: Default Paragraph Font, Font: Bold
7 Project Definitions & Acronyms ........................................................................................ 14 Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold
Formatted: Default Paragraph Font, Font: Bold
Formatted: Default Paragraph Font, Font: Bold
Formatted: Default Paragraph Font, Font: Bold
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold, Small caps
Formatted: Default Paragraph Font, Font: Bold
Formatted: Default Paragraph Font, Font: Bold

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 2 of 19
1 Introduction
1.1 User Problem/ Project Background
The objective of this project is to provide GM Sales & Marketing greater flexibility in managing
and reporting the sales objectives of their dealers (BACs). Currently, NASR obtains monthly
objectives from ISAS at a BAC/model level. This single geographical level (BAC) is used within
NASR as the base for reporting upper level geographies (i.e. Region, Area, Section, Zone) by
summing the BAC level objectives. The GM business needs to manage the BAC level objectives
to, and in some cases, exceed the sum of the Area, Zone, Region, and National objectives while
keeping these geographical objectives constant. The existing process of rolling up BAC
objectives does not provide the flexibility required to run the business and needs to be modified.
This “roll-up” process must be eliminated and replaced by the computed objectives obtained from
the Vendor for each level of geography.

1.2 To-Be Business User Roles

The users of the sales reporting systems include GM internal personnel that track and monitor US
sales performance relative to achieving stated sales objectives and forecasts. These individuals
include VSSM employees based at both the GM Global Headquarters at the Renaissance Center
as well as those based at the five GM Regional Offices. This group also includes select members
of the remote VSSM Field Teams. In addition, the system is supported by the GM IT Operations
group that is responsible for managing the sales reporting systems.

Business Location Subject Technical Preferred Background Other

User Role / Matter Knowledge Environment Observations, if
User Group Knowledge any

Corporate US GSSM N/A Web NA View Daily Sales

General User processes Reports
View Field Reports
P. Query
Field General US GSSM N/A Web NA View Daily Sales
User processes Reports
View Field Reports
P. Query
GMIA Report RenCen GSSM Cognos Cognos Data Experts Report author
Author processes, authority
reporting
System RenCen NA Cognos, TOAD, Unix, System System
Administrator Java, Unix, Cognos Custodian administration
Oracle
Data RenCen GSSM Oracle, Unix Cognos Data Data administration
Administrator processes Custodian
Forecaster RenCen GSSM N/A Web NA View forecast
processes reports and
forecast data

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 3 of 19
2 Behavioral Business Requirements
2.1 BR-001: Sending Vendor Process Changes
Business Requirement BR-001
ID
Associated Business Dealer objective File Processing
Process Step or
Process Name
Source of Requirement ITSR 001-2010-008-04
Business Value Frequency of Use

High High (Monthly/ Manual)

Business User Roles

Data Administrator, System Administrator

Business Requirement Description

A vendor will provide NASR 7 levels of monthly objectives: National, Region, Section, Zone,
Area, GMMA, and BAC.
 Each level must contain objectives by ISAS model code. This is the same model that
is currently provided at a BAC level.
 These objectives will be created on approximately the 3rd or 4th business day of the
new month.
 Separate files will be created for each of the 7 geographies.

Key Business Behaviors / System Actions

2.1.1 The Sending Vendor System transmits flat files to the NASR database server.
o 7 flat files will be created, each corresponding to one of the geographies.
Acceptance/Fit Criteria

Data in the Flat files provided by vendor will be reflected in the NASR database tables.
Vendor will transmit flat files on a monthly and ad-hoc basis to NASR.
Business Rules, Constraints

N/A

Dependent Requirements

BR-002, BR-003, BR006

Notes

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 4 of 19
2.2 BR-002: NASR storing monthly objective file(s)
Business Requirement BR-002
ID
Associated Business Dealer objective File Processing
Process Step or
Process Name
Source of Requirement ITSR 001-2010-008-04
Business Value Frequency of Use

High High
Business User Roles
Data Administrator, System Administrator

Business Requirement Description

 Objectives for all 7 levels of geography (from Requirement 1) must be stored in the
NASR database.
 Each level must be stored by reporting model and by sales month & year.
 Prior months’ objective data needs to be retained, not overwritten.
 All 7 files need not be processed at a given time.
 Any geographical level objective file will be processed when it is received at the
Secure FTP site.
Key Business Behaviors
1. Flat files corresponding to objectives for all or any of the 7 geographical levels will be posted at
the Secured FTP site.
2. The files will be input to the NASR tables corresponding to the geographical level objectives.
3. NASR performs the data validation.
 Objectives will now be recorded for the following geographical levels: National, Region,
Section, Zone, Area, GMMA, BAC.
4. NASR application loads the data to the NASR database.
 NASR table structures will contain the different levels of objectives.

Acceptance/Fit Criteria
1. Data from files transferred to NASR will be updated in the tables for the corresponding
reporting period.

Business Rules, Constraints

NA

Dependent Requirements

BR-003, BR-004, BR-005, BR-006

Notes

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 5 of 19
2.3 BR-003: NASR Reporting Changes
Business Requirement BR-003
ID
Associated Business NASR Reporting table update
Step or Process Name
Source of Requirement ITSR 001-2010-008-04
Business Value Frequency of Use

High High
Business User Roles

Data Administrator, System Administrator

Business Requirement Description

 The NASR standard and ad-hoc reports that contain objective data will be updated to
read the stored objectives for the required level(s) of geography (national, region, section,
zone, area, GMMA, BAC).
 The NASR standard and ad-hoc reports will display the objective data only if the data is
stored in the NASR tables for the given month & year and if the field is not blocked (see
Requirement BR-004 for definition of blocked).
 For objective data that has not been received from the Supplying Vendor and is not
blocked (is displayable), the NASR standard and ad-hoc reports will display objective data
the same way the current NASR report data is displayed when objective data has a value
of zero:
o Objectives will display zero
o Gap to Objective will display the delivery units (gap = deliveries – objective)
o Percent to Objective will display a blank
o Run Rate vs Objective will display the run rate volume (rr vs obj = run rate –
objective)
o Balance to Go will display a negative delivery count (balance = objective –
deliveries)
 For objective data that has been received from the Supplying Vendor and is blocked (is
not displayable), the NASR standard and ad-hoc reports will display objective data the
same way the current NASR report data is displayed when objective data has a value of
zero:
o Objectives will display zero
o Gap to Objective will display the delivery units (gap = deliveries – objective)
o Percent to Objective will display a blank
o Run Rate vs Objective will display the run rate volume (rr vs obj = run rate –
objective)
o Balance to Go will display a negative delivery count (balance = objective –
deliveries)
 The process of summing up BAC objectives at the time of report generation will be
discontinued. Summing will not be required because the summed values for each level of
geography will already be stored in NASR (see Requirement BR-002)
 The following reports will be updated:

Reports With
Objectives.xls

Key Business Behaviors

Acceptance/Fit Criteria
1. Reports will be successfully generated with the correct objective value for each of the 7
geographical levels.

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 6 of 19
Dependent Requirements
NA

Notes

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 7 of 19
2.4 BR-004: NASR “Blocking” flag for Model and Geography
Level Reporting
Business Requirement BR-004 Formatted Table
ID
Associated Business Objective Blocking process for model level and 7 geographical levels (new)
Step or Process Name
Source of Requirement ITSR 001-2010-008-04, ITSR-001-2010-008.001
Business Value Frequency of Use

High High
Business User Roles
Data Administrator, System Administrator

Business Requirement Description

 A new Admin screen will be created to allow the GM business team to “block” certain
objectives at model level from Field and Ad-hoc reporting. The fields that will be
displayed on the screen is:
National Month (drop-down)
Region (list box) Year (drop-down) Formatted: Font: Italic
Section (list box) Model (associated with the selected geographical level) Formatted: Font: Italic
Area (list box)
Zone (list box) Formatted: Font: Italic
GMMA (list box) Formatted: Font: Italic
BAC (list box and search field) Formatted: Font: Italic

Blocking Indicator Formatted: Font: Italic

Formatted: Font: Italic
 The Blocking Indicator values are checked or unchecked. Formatted: Font: Italic
 A checked Blocking Indicator represents a field’s objectives MUST NOT be displayed in
Formatted: Indent: Left: 0"
ad-hoc and field reports.
 An unchecked Blocking Indicator represents a field’s objectives can be displayed in Ad-
Hoc and Field reports.
 The default value of the Blocking Indicator is unchecked (displayable).
 The GM business team needs the ability to modify the value of the Blocking Indicator.
They need to be able to control if the Blocking Indicator value should be “checked/not
displayable” or “unchecked/displayable”.
 During the month the business team will be able to check and uncheck the fields.
 The business team will be able to select multiple or all models at a particular geographical
level to be blocked from reporting.
 This Boolean Blocking Indicator must revert back to the default value at the beginning of
each sales month, irregardless of it’s value on the last day of the sales month. In other
words, all data fields are displayable.
 All settings will be retained by model and by month & year for all geographical levels.

Key Business Behaviors

1. If the blocking indicator for some or all models at one of the 7 geographical levels is checked,
the objective data for these models will not be reported in the Standard and Ad-hoc reports.
When the Blocking Indicator of a certain field (e.g. GMMA) is checked in the admin screen, the
Field and Ad-Hoc reports will not display Objective data for the field, even if the objectives have
been stored in the NASR database.
2. If the Blocking Indicator values offor all models at all geographical levels is all field(s) is “un
checked” objective data for all locations will be reported in the Standard and Ad-hoc report.
3. If the default value of a field is marked as “checked”, see BR003 for 0 record display.

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 8 of 19
Acceptance/Fit Criteria
1. Standard and Ad-hoc reports will display only the objective data that is not blocked through the
Admin Screen.
2. At the beginning of the month, the Blocking Indicator for each of the fields will be set to
unchecked so that all geographical objectives will be displayed in NASR standard and AdHoc
reports.
3. The value of the Blocking Indicators in the impacted tables for the 7 geographical areas will be
stored for each model in base tables.
Business Rules, Constraints
NA

Dependent Requirements
BR 003

Notes
This requirement will be modified as part of CR001, with an additional drop-down option added for
blocking by Model.

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 9 of 19
2.5 BR-005: NASR mid-month BAC Objective Changes
Business Requirement BR-005
ID
Associated Business Objective File processing
Step or Process Name
Source of Requirement ITSR 001-2010-008-04
Business Value Frequency of Use

High High
Business User Roles

Data Administrator, System Administrator

Business Requirement Description
 At anytime during the month the GM business team may need to modify BAC level
objectives. An “Admin” screen will be created to accept these changes. The file will be
created by the GM business team in Excel format with the following fields:
o Month
o Year
o BAC number
o Reporting Model Name (will be in same format as NASR model names)
o Current Objective
o New Objective
 The new screen must have a button to allow the business user to browse for the file and a
second button to process the file.
 This process will ONLY be used to modify BAC/Reporting Model level objectives. When
updating the record in the NASR database, the key for the search must include Month,
Year, BAC, and Reporting Model only. The Previous Objective listed in the Excel file
does not have to match the existing objective stored in NASR.
 This process must return an appropriate error message if it is unable to find an existing
row in the NASR database to update.
 A log file must be created with both a before and after shot of the updated record. This
log file must be available (mostly for audit purposes) via a service request ticket to the
NASR team.
 The screen that is used to process the file must also allow for the display and printing of
the current day’s error log with timestamp. This error log must contain detailed
information on why each record from the Excel file could not be loaded.
 It is expected reasonable number of errors logs (the most recent 6 months of load logs)
that the most recent 6 months of load logs will be saved on the system.
 If the business team wants access to any of the error logs --with the exception of the most
recent -- a service ticket will be created.
 The processing of records must NOT stop when an error occurs. All errors must be
identified on a single processing request. When the processing in done, a decision
message must appear that states:
o “Errors have occurred…Do you want to update the database with those records
that contain no errors? (Y/N)”
 Only NASR users with Admin privileges can perform this process of loading the file.
 When a mid-month National file is received from the Sending Vendor and is processed,
the NASR main screen must be updated with the latest timestamp.
 When a mid-month BAC file is received from the Sending Vendor and is processed, the
NASR main screen must be updated with the latest timestamp.(See BR-008)

Key Business Behaviors

1. Admin user logs on to the system and browses for the excel spreadsheet with Objective details.
2. The folder structure is displayed for the user to select the file. Only files in excel format will be
allowed to be selected.

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 10 of 19
 3. Admin user clicks on the “Process file” button on the screen.
a. System will validate the format of the Excel File.
b. For each record in the spreadsheet, the system will search for the corresponding
record in the NASR database.
i. If no record is found, an error is logged.
ii. If a corresponding record is found, the data from the Excel spreadsheet is
moved to the Staging area.
c. If there were errors, system will display a dialog box to prompt the user to continue or
cancel processing. Error log must contain the row number on the excel spreadsheet.
i. If User selects “No”, no further action is taken.
ii. If User selects “Yes”,
1. The records in the staging area are moved to the main table where
they overwrite the existing objective details.
2. Previous and new record details for each record are logged.
4. Admin user clicks on the “Display Errors” button on the screen.
a. Errors captured during the last upload of excel file will be displayed.
b. All error logs for current day will be displayed.
Acceptance/Fit Criteria

1. Data provided in the excel files will successfully be updated to the corresponding record (s)

Business Rules, Constraints

1. The date field in every record should always reflect the first day of the month.
2. This process can only be used to update existing objective details and not for adding new
BAC/Model/Objective combinations.
Dependent Requirements
BR-008N/A

Notes

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 11 of 19
2.6 BR-006: Reprocessing the 7 Geographical Levels at mid-
month
Business Requirement BR-006
ID
Associated Business Dealer objective File Processing
Process Step or
Process Name
Source of Requirement ITSR 001-2010-008-04
Business Value Frequency of Use

High High
Business User Roles

Data Administrator, System Administrator

Business Requirement Description

At anytime during the month the business team must be able to reload any or all the 7
geographical level files. This is similar to today’s process of reprocessing the BAC level
objectives.
Key Business Behaviors
1. The Receiving Vendor will load any/all of the 7 geographical level objective files from the
Sending vendor.
2. The objective processing job will be updated to be able to pick up these files as soon as they
are available on the NASR Secure FTP site.
3. The data files will overwrite the existing geographical objective data for the month and year.
Acceptance/Fit Criteria
 The Receiving Vendor is able to load new objective data at any time during the month
 Old geographical objective data for the month is successfully overwritten by data from the new
geographical objective file sent.
Business Rules, Constraints

1. Even if the objective files are loaded into NASR at any time of the month, the date field should
always contain the 1st calendar day of the month.

Dependent Requirements

NA

Notes

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 12 of 19
2.7 BR-007: Summing Historical Objectives
Business Requirement BR-007
ID
Associated Business Objective File Processing
Process Step or
Process Name
Source of Requirement ITSR 001-2010-008-04
Business Value Frequency of Use

High High
Business User Roles

System Administrator

Business Requirement Description

 A one-time only process will be created to sum historical objectives for all geographical
levels.
 This historical summing will utilize the existing GMDID structure stored within the VSNA
database.
 The historical summing must be at the same structure as the future geographical data (i.e.
by year, by month, by geography, by model). Since NASR already contains historical
objectives at a BAC level, the historical summing will only take place for the remaining 6
geographical levels – National, Region, Section, Zone GMMA, and Area.
 All existing historical BAC objective level data will be summed.
Key Business Behaviors
Acceptance/Fit Criteria

Historical objectives are available in the NASR reporting tables for all 7 levels of geography
The process will run for all historical records.

Business Rules, Constraints

N/A
Dependent Requirements

N/A

Notes

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 13 of 19
2.8 BR-008: Data Load Status Screen updates
Business Requirement BR-008
ID
Associated Business NASR Main screen data load status display
Process Step or
Process Name
Source of Requirement ITSR-001-2010-008.001
Business Value Frequency of Use

High High
Business User Roles
Data Admin, System Admin, General User

Business Requirement Description

 As-Is situation: The Data Load Status Screen is the first screen a NASR user sees when
logging into the application. The screen shows a small table currently consisting of 4
rows (and 2 columns) providing a last_update_timestamp of the four recent data loads.
The four current loads are 1) All GM Data, 2) National Objectives (from MADM), 3)
Dealer Objectives, 4) Track. Formatted: Font: (Default) Arial, 8 pt, Font color: Auto
 To-Be: Additional 6 rows will be added to this table to include a timestamp for all 7
Objective file loads from the Sending Vendor, as illustrated below. This will help the
NASR user to know when the application was last updated for Objectives. Formatted: Font: (Default) Arial, 8 pt
Formatted: Font: (Default) Arial, 8 pt, Font color: Auto
Data Load Status Formatted: Indent: Left: 0.25", No bullets or numbering
Data Category Last Update (ET) Formatted Table
<Date and time stamp>
All GM Data e.g.Tue, Jan 26, 2010 01:30:39
National Objectives (from MADM) <Date and time stamp>
National Objectives (dealer Sales) <Date and time stamp>
Regional Objectives <Date and time stamp>
Section Objectives <Date and time stamp>
Zone Objectives <Date and time stamp>
Area Objectives <Date and time stamp>
GMMA Objectives <Date and time stamp>
Dealer Objectives <Date and time stamp>
Track <Date and time stamp>
Formatted: Indent: Left: 0.25", No bullets or numbering
 The Dealer Objective Timestamp will be updated whenever there is a change to the Formatted: Font: (Default) Helv, 10 pt, Font color: Black
dealer objective table through 1) Flat file transfer during month end processing, 2) Flat file
transfer at any time of the month, or 3) Mid-month objective change via the new BAC
objective change screen (see BR-005)
 The timestamps for National (for dealer sales), Region, Section, Zone, Area and GMMA
will be updated whenever there is a flat file transfer into the NASR tables for the
respective geographical level.
Formatted: No bullets or numbering
Key Business Behaviors
Acceptance/Fit Criteria

The NASR data load table will display the correct date and timestamp of the latest changes to the NASR
main tables for all the 7 geographical reporting levels

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 14 of 19
Business Rules, Constraints

N/A
Dependent Requirements

N/A

Notes

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 15 of 19
Behavioral Models
2.82.9 Conceptual Information Model
Attached is the format of the 7 files that will be provided by Vendor to the NASR Subsystem. The
files are in a similar format as the current BAC level objective file. Expected filenames will be
documented in the SRS.

BR DOCs - Dealer
Objectives for all Geographies.xls

The existing data model will be re-used where applicable.

3 Non-Functional Business Requirements

3.1 Usability Requirements
N/A – Identified as part of Functional Requirements.
Layouts and formats of the two new screens will be similar to that of the existing screens in NASR

3.2 Business Speeds and Feeds

TBD in the SRS documentation
Please refer to the SLA documents and NASR System Design Document, section 6 (System
Performance) for additional details

3.3 Additional Non-functional Business Requirements

No additional non-functional requirements are in scope of this enhancement project.

4 Legal Requirements
There are no changes to any existing legal requirements. Only the source of objective data is
being changed, along with corresponding changes to reports.

4.1 Compliance Requirements

There are no compliance requirements identified for this enhancement. The system is not a SOX
application

4.2 Globalization Requirements

N/A – North America only

4.3 Security Requirements

N/A – Existing web security testing processes will be adopted during deployment into production

5 Reporting Requirements
The following Cognos reports will be modified with the geographical objective information;

Reports With
Objectives.xls

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 16 of 19
6 Operational Requirements
N/A – Existing Operational Requirements are not being changed as part of the enhancement
project.

6.1 Runtime Requirements

N/A – No changes to existing Runtime Requirements

6.2 Data Archiving Requirements

N/A – no changes to existing data archival requirements. Data Retention must be identical to the
VSNA data retention periods.

6.3 Additional Operational Requirements

NA - A one-time process will be run by the AD team to sum historical objective data at the 7
geographical levels (BR-007).

7 Project Definitions & Acronyms

Term Definition
BAC Business Associate Code

NASR North America Sales Reporting

VSNA Vehicle Sales North America

GMDID Table within the NASR application. This table stores the geographical hierarchy. Dealer
through Region
GMMA GM Market Area

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 17 of 19
SDP Revision History
Version Date Updated Revision Author Brief Description of Changes
Number
1.0 October 17, 2006 SDP R10 / Standardized First release of SDP 10.
Work Team
1.1 February 15, SDP R10 Content Team Added SDP Revision History and
2007 distinguished from Project
Revision History
1.2 October 29, 2007 SDP R10 Content Team • Updated Requirement IDs for
Standard Requirements
• Corrected Requirement # to
Requirement ID for Standard
Requirements.
1.3 April 11, 2008 SDP R10 Content Team Updated Capacity Classification
1.4 December 12, SDP R10 Content Team Updated Business Requirements
2008 Document to behavioral business
requirements from a Use Case
framework perspective. Added
Requirements Quality Process
Elements
1.5 September 30, SDP R10 Content Team Updated to latest SDP Format;
2009 Updated content to move Use
Case Diagram to Use Case spec;
Combine Business Requirements
and Business Scenario tables into
one; remove Legal field from BR
table
Added section 4.2 (business
speeds and feeds)
Added Caliber RM guidance

Project Revision History

Project Date Revision Author Brief Description of Changes
Version Updated
Number
0.1 5/21/2010 Sindhu Nair Created
0.2 5/24/2010 Sindhu Nair Updated per internal Peer Review
comments
0.3 5/27/10 Sindhu Nair Updated per GM Peer Rieview
Feedback
1.0 6/1/2010 Sindhu Nair Updated per Business User
feedback; approved version
1.1 6/15/2010 Sindhu Nair Updated for CR 001 and 003, Formatted: Font: (Default) Arial, Font color: Auto
refer ITSR-001-2010-008.001. Formatted: Normal, Left, Right: 0.01", Don't adjust space
BR-008 was added and BR-004 between Latin and Asian text, Don't adjust space between
was updated to reflect the Asian text and numbers, Tab stops: 0.5", Left
blocking of objective reporting at
model level

NASR Geographical Business Requirements Document Doc. Version 1.01

Objectives Reporting
SDP Template Version 1.4 Page 18 of 19
NASR Geographical Business Requirements Document Doc. Version 1.01
Objectives Reporting
SDP Template Version 1.4 Page 19 of 19