Title: EDA Registration Functions
1Electronic Document Access (EDA)
- EDA Registration Functions
Fly-in Action ( Continue to Page Down/Click on
each page)
2EDA Registration Process
EDA registrants Self Register at the EDA
Website. EDA POC for the registrants C/S/A
receives pending registration notification. EDA
POC authenticates and authorizes registrants
pending registration request. Validates access
request and applies special roles. If approved
by the EDA POC, EDA sends Approval e-mail to
the new user with logon instructions. The EDA
User account is established. The New User may
access EDA as authorized by the EDA POC.
Registration Activity Process
3Registration Activity Process
A User Self Registers in EDA The PROCESS
EDA
EDA E-mails
4E-mail Confirmation to User
Registration Confirmation Notification
SAAR form ROB/AUP submission reminder (by date)
EDA POC Contact information (Identifies EDA POC
to User)
E-mail to EDA POC
5E-mail to EDA POC for Action
Pending Registration E-mail Notification
EDA POC Authorization Process
Registrants Registration information
Instructions to process request in EDA
Escalation Rules
6Escalation Rules
- Action required by PRIMARY EDA POC within 2
Business Days of notification
- If NO Action by the Primary EDA POC within 2
Business Days of notification - Escalates Request to Alternate EDA POC for action
(E-mail sent to alternate)
- If NO Alternate EDA POC assigned at a
particular level within the C/S/A structure - Escalates to higher EDA POC authority (E-mail
sent to Authority Level above as defined in
C/S/A)
- If NO Action by the assigned EDA POCs, the
requests escalate after 7 days to higher
authority for action/follow-up
Escalation E-mail
7E-mail to Higher Authority
Escalation E-mail Notification
Processing Requests
8User Registration Administration
- After Receiving EDAs E-mail Notification
Contacting User to Validate Registration Request - Process the Registration(Approve, Delete or Mark
Misaligned) - Log into EDA
- (http//eda.ogden.disa.mil) or
- (http//eda.cols.disa.mil)
- Note EDA Servers replicate data constantly,
therefore, stay at one site during update
activity. - Click Account Administration
Account Administration Capability
9Account Administration fromDocument Selection
Screen
If you dont see Account Administration on your
Document Selection screen Your User
Administration Role (i.e. EDA POC or EDA
Executive) has not been granted to your user
account. Contact your EDA POC or EDA Executive
for assistance.
To Perform User Account Administration CLICK Acc
ount Administration on the Document
Selection Screen within EDA
Account Administration Menu
10Account Administration Menu
Account Administration Menu Contains Registration
s queues, Request queues, the capability
to Search, View, Modify and Delete user accounts
and EDA POC and CDR POC Assignment Each function
is explained and demonstrated in a separate
training module.
Lets LOOK at the Registration Process in Detail
11Registration Requests
Registration Requests Pending () Approved /
Waiting User Logon () () - Number of Requests
in queue
Pending () holds the registrations waiting for
EDA POC authorization/approval. Approved/Waiting
User Logon () holds registration approvals for
users with Username/Password credentials. Its a
queue waiting for the user to activate their
password/account.
- EDA POC Registration Activities Include
- Authorizing Users for EDA access and
- Processing the Pending registrations within their
user community. - PENDING Registrations are valid for 30 days and
are automatically deleted after 30 days if no
action by EDA POC.
12EDA User Registrations
Registrations Pending () Approved / Waiting
User Logon () Count () represents number of
requests in the queue.
Processing Registrations is a primary
responsibility for Assigned EDA POCs. A signed
SAAR form (DD 2875) is required for each user. In
addition, the Rules of Behavior/Acceptance Use
Policy (ROB/AUP) signature page must also be
submitted. Security forms and instructions are
available in Users Guide. EDA POC holds
security forms for users within their authority
realm (defined by the C/S/A structure).
13Approved Registrations
Approved / Waiting User Logon ()
- After APPROVAL of the Registration,
- EDA sends an e-mail notification to the user with
log on instructions. - EDA places Username/Password approved requests
into a separate queue Approved / Waiting User
Logon (). Certificate accounts dont require
password activation and are not included in this
queue. - When users log into EDA, the request will be
deleted from approved queue. No further action
is required on request. - Approvals for Username/Password accounts are
valid for 7 days. Password reset will be
required if approval expires.
14Registration Queue
How to Navigate
- Navigate the queue
- Navigate View
- Flat View
Lets Take a LOOK at the Registration Queue
15Entering the Registration Queue
Click Pending
The presentation of the registration queue within
EDA depends on your Administrative Role. EDA
POC or Executive EDA POCs view registrations in
Flat View (or List mode) in alphabetical
order Executives will default to the C/S/A
Navigate View, but they may opt to the Flat view.
Pending Registration Queue
16Pending Registrations Flat View
Alphabetical By Name Last, First
Total Registrations in Queue
Delete from Queue OR Delete from Action By
Clicking Name
17Pending RegistrationsNavigate View
Executives have an option to view the
Registration queue in Navigate mode
Navigate View offers the Executive a view of
their entire C/S/A structure and the
registrations in each of their organizations. EDA
POCs dont have Navigate View, they view
registrations in a flat/list view
Lets Continue Navigating
18Executives Navigate View Option
Click Navigate View. EDA presents the Executive
their C/S/A authorization structure.
Expand/drill into file structure as required.
Each level shows pending activity and responsible
EDA POCs
Navigate Capability Information
19Navigate View of Registrations
Navigate C/S/A View offers Executives - a
capability to view requests for their entire EDA
user community based on C/S/A. - a total count of
registrations/requests for a queue - registration
count distribution for each level. -
identification of primary and alternate EDA
POCs. - a direct link to view the EDA POC user
account. - a Flat view queue sorted by
name. Click or the C/S/A name/link to expand
structure or show queue.
20Navigate View of Registration
Each expansion provides more detail and
distributes the counts accordingly. Pending
registrations are displayed under each
activity/organization. Â Expand/Click () the
levels to view pending requests and counts. At
any point during 'drill-down', the Flat View is
available. Â
Lets LOOK at the screen details
21Navigate View of Registrations
Flat View Alphabetical Order By Last Name For
entire C/S/A
Total Registrations in Queue for C/S/A
Direct link to Primary and Alternate EDA POC user
account
Registration requests at level
Distribution of counts to sub-levels
Click C/S/A Name
C/S/A User Authorization Structure. Expand into
each sub-level
Continue Expanding
22Navigating Registration Queue
Navigating/Drilling downward
C/S/A User Authorization Structure. Expand into
each sub-level
Sublevel expanded
Distribution of counts Registrations (1 of 1)
Distribution of counts
Continue Expanding
23Navigating Registration Queue
continue downward
C/S/A User Authorization Structure. Expand into
each sub-level
24Process Registrations
How to Process
EDA
EDA notifies the Primary EDA POC by e-mail when
user account administration activity occurs. The
e-mail will indicate the action required by the
EDA POC.
Registration Processing Options
25Processing Registration Requests
There are five (5) options available when
processing a Registration
- Approve a Registration
- User Account is created
- User is authorized to access EDA
- Suspend a Registration
- Prevents the escalation notification to
Alternate EDA POC - Remains pending for appropriate action by EDA
POC
- Change C/S/A Delegate Registration
- Allows a C/S/A change which delegates the
registration to another - Activity/Organization
- Mark Registration Misaligned
- Allows a registration to be moved to a
misaligned queue. - EDA Help Desk will contact user and assist in
proper placement.
- Delete Registration
- Registration is deleted. NO information is
retained.
Processing on of these options
26Processing a Registration
Click Name
- ACTION Options
- Approve a Registration
- Suspend a Registration
- Change C/S/A Delegate
- Mark Registration Misaligned
- Delete Registration
Lets Look at ALL the Options One-by-One
27Process Registration Screen
- ACTION Options
- Approve a Registration
- Suspend a Registration
- Change C/S/A Delegate
- Mark Registration Misaligned
- Delete Registration
Select ACTION
View History Of Registration (Audit Info)
To APPROVE
28Approve Registration
Select Action Approve Registration
Click Submit
Approve Registration page is displayed
29Verify/Validate Account
VERFY INFORMATION Make any necessary changes by
entering new content into fields Ensure e-mail
and telephone are Correct and current
EDA POCs authorize and approve access for their
user community
Roles Document Access Alter (check/uncheck) as
required (based on Need to Know)
Definition Need-to-Know The principle by which
users are only granted access to the information,
assets, and resources necessary to perform their
assigned job functions.
Apply Special Roles
Validate and apply updates as required
30Understanding Special Roles
A few roles require additional authorization by
EDA POC
- Audit Reports
- EDA Usage metrics within C/S/A
- Managers, Executive
- Attachment Upload
- Various Contract Attachments supporting contract
execution - Contract Officers, Contract specialists, etc
- Contract Load Notification
- Notification on contract load activity. Defined
at the contract/Mod and/or - DO/TO level.
- Contract Officers, Contract Specialists, etc
- REQUIRES Additional DoDAAC criteria (Issue,
Admin)
- Upload/Inactivate Document
- Manual Contract Upload Capability
- Contract Officers, Contract Specialists, etc
- REQUIRES Additional DoDAAC (Issue) criteria
- REQUIRES Executive and EDA POCs with Manual
Upload Capability
31Understand Special Roles - cont
A few roles require additional authorization by
EDA POC
- Vouchers All
- Queries all voucher types and presents in one
result set - As required to users to perform their job
functions
- Signature Cards
- Privacy Act Information
- As required to users to perform their job
functions
- DD1716s
- Old Contract deficiency reports
- Historical purposes, No longer supported/loaded
- As required to users to perform their job
functions
- EDM/EFR Documents
- Contract Pay (by Site)
- Vendor Pay (by Site)
- As required to users to perform their job
functions - Special authorization and setup required by EDM
Help Desk to complete the request (Refer to the
EDM/EFR training module)
32Understand Special Roles - CDR
A few CDR roles require additional authorization
by EDA POC
- Reviewing Official associated to a specific
initiators office - Authority who approves Contract Deficiency
Reports (CDRs) - Managers, Officers, etc
- ACO associated to a specific CDR Organization
- Admin contract officer
- CDR Assignee
- PCO/Buyer associated to specific CDR
Organization - Procurement Contract Officer
- CDR Assignee
- CDR POCs assigned to specific CDR Organizations
- Determined by office/DoDAAC
- May be CDR Assignee
- May be CDR oversight and management of CDR
workflow process
33EDA POC Authorizes Roles
To activate special roles, Check the
corresponding checkboxes.
EDA POCs MAY authorize additional special roles
for users in their community.
Definition Need-to-Know The principle by which
users are only granted access to the information,
assets, and resources necessary to perform their
assigned job functions.
34EDA POC Toggles on CDR Role(s)
EDA POCs MAY authorize additional CDR special
roles for users in their community.
Contract role and CDR role must be
Toggled/Checked ON To GRANT CDR participant
roles, check the corresponding checkboxes.
The CDR POC has NO authority until Assigned to
the C/S/A structure as defined in EDA.
Assignment is described in a separate training
module.
35EDA POC Toggles on Voucher All
EDA POCs MAY authorize Voucher All role if
Need to Know is met.
Voucher All provides users a query result set
containing all voucher types.
Definition Need-to-Know The principle by which
users are only granted access to the information,
assets, and resources necessary to perform their
assigned job functions.
36EDA POC Toggles on Role(s)
Other special roles that may be granted to users
in their community.
Request EDM/EFR Documents By Site
To activate special roles, Check the
corresponding checkboxes.
Definition Need-to-Know The principle by which
users are only granted access to the information,
assets, and resources necessary to perform their
assigned job functions.
37EDA POC Toggles on Role(s)
EDA POCs obtain the role by requesting it from
their C/S/A Executives.
If EDA POC does not have toggle capability in
the Upload/Inactivate Documents entry area to
grant role on the User Account screen The
Upload/Inactivate Role has not been granted to
the EDA POC user account Contact the Executive
or your EDA POC for assistance in granting the
role. Note Executives EDA POCs must have the
Upload /Inactivate Role to grant it.
38DoDAACs Required for Roles
Some Capabilities require DoDAAC(s)
Click More Upload DoDAACs For more entry boxes
Enter Issue DoDAAC(s)
Click More DoDAACs for more entry fields
Enter DoDAAC(s) Issue or Admin
Users functionality is restricted to specific
Issue and/or Admin DoDAAC(s).
EDA POC Appointment Responsibilities
39EDA POC Role
The EDA POC role requires additional
authorization and setup.
- EDA POC Appointment
- Appointed by authority within C/S/A
- DD 2875, ROB/AUP signature page and the EDA POC
Appointment Letter are required. Forms are held
by authority who approves user as defined in the
organizations C/S/A structure. - EDA POC Responsibilities
- Responsible for servicing an organizations
user community EDA registration and access
requests - EDA POC Assignment within their authority as
defined by the C/S/A in the EDA C/S/A
authorization structure - Assignment and management of CDR Organizations
within their assigned authority
40Apply EDA POC Role
EDA POC Role Establishment DD 2875, ROB/AUP
Signature page EDA Appointment Forms are
REQUIRED Once FORMS are Received Toggle
EDA POC role The EDA POC has NO authority until
Assigned to the C/S/A structure as defined in
EDA. Assignment is described later.
41EDA POC C/S/A Authority
What level within the organization will the EDA
POC perform access authorization?
To Change Organizational Level
Check Organizational level before processing
registration
Click Select a CSA
42Verify C/S/A on EDA POC
Select appropriate level for authority
User Selected during Registration
Moving up the organization chain opens more
authority to the EDA POC. Their community of
users responsibility expands to the selected
organization level and BELOW.
The ability to move UP the C/S/A chain is based
on the level of your authority. A higher
authority may need to assist if outside YOUR
realm of authority.
Lets move it UP a few levels
43Change C/S/A
EDA POC selects appropriate level
Example shows Moved from a base DoDAAC level
(FA1111) to Command level (ACC). EDA POC User
now has authority at the Command level and below
44Approve/Update Account
Select Active
Error Messages are displayed if problems with
data. fields are REQUIRED
EDA automatically notifies user of approval
Click Add This Account
45Approved Registration Queue
Registrations Approved / Waiting User Logon ()
After APPROVAL of the Registration, EDA sends an
e-mail notification to the user with log on
instructions. If Username/password credentials,
EDA places the approved request into a separate
queue Approved / Waiting User Logon
(). Approvals are valid for 7 Days. A password
reset is required if approval expired.
Once the user activates their Username/password
account by logging into EDA, the request is
automatically cleared from the approved
queue. DO NOT Delete from the Approved queue.
46Approval Notification to User
Directions Link for account activation
Approval expires if not activated by DATE
Identification of EDA POC to User
NextTo Change C/S/A and Delegate
47Change C/S/A Delegate
Select Action Change CSA and Delegate
Click Submit
- Possible Reasons
- Contacted User and determined a different C/S/A
- User did not choose the correct C/S/A during
registration - User has moved locations
- A re-organization occurred within the Community
- User no longer belongs under EDA POC
responsibility - Other
Confirm Change C/S/A and Delegate
48Change C/S/A Confirmation
Change the C/S/A on the registration to delegate
to another organization within your realm of
responsibility
If you are unable to select the NEW C/S/A, USE
Mark Registration Misaligned option. (movement is
outside your authority). The Help Desk will
assist the User.
Click Select New C/S/A Select C/S/A and sublevel
organization from list to pre-populate screen
Important Info
Enter Comment (optional)
Click Submit
EDA automatically notifies interested parties of
administrative activities
Change C/S/A Complete Next To Misaligned
49Mark Registration Misaligned
Select Action Mark Registration Misaligned
Click Submit
- Possible Reasons
- User is not in area of responsibility
- Unable to select/see appropriate New CSA,
therefore must use misaligned option - Other
Confirm Mark Registration Misaligned
50Misalign Confirmation
Mark Registration Misaligned removes the
registration from your pending queue and
redirects the registration to the EDA Help Desk
for placement assistance.
Important Info
Enter Comment (optional)
Click Submit
EDA automatically notifies interested parties of
administrative activities
Mark Misaligned is Complete Next to Suspend
51Suspend a Registration
Select Action Suspend Registration
Click Submit
- Possible Reasons .
- EDA POC is waiting for DD 2875 form from user
- User has not been authorized access -
verification in progress. - Prevent escalation to the alternate EDA POC due
to wait - Other
Confirm Suspend Registration
52Suspend Confirmation
Suspending a registration prevents the escalation
notification to the alternate EDA POC.
Registration remains pending for action by you.
Pending Registrations are valid for 30 days.
Important Info
Enter Comment (optional)
Click Submit
Suspense Confirmation page is displayed Next to
Delete
53Delete a Registration
Select Action Delete a Registration
Click Submit
- Possible Reasons .
- Invalid Registration
- Registration no longer required
- Duplicate
- Other
Deleting a registration is permanent. No
information is retained.
Another Option to Delete a Registration
54Option - Delete from Pending List
Alphabetical By Name Last, First
Delete from Queue IS Another Option
55Delete Confirmation
Deleting a registration is permanent. No
information is retained.
Choice of notification at time of Delete
Important Info
Click Delete WITH Notification
Deleting WITHOUT Notification simply deletes the
request from the pending queue. No information is
retained. No Notification to user.
56Delete with Notification
Enter Desired Message To User
Click Preview
EDA mirrors exactly what is entered.
Professionalism is expected.
57Preview Delete Notification
Click Submit
Delete is Complete Notification sent
58Account Administration Training
Refer to the Training Material by Function. Each
module provides an overview of an Administrative
function and they contain details on procedures
and use Registration Process Support
Contractor Access Requests Process Password Reset
Process Account Query Maintenance EDA POC and
CDR POC Assignment Process Administration of
Special Roles ------------------------------------
--------------------------- Access EDA Home
Page Click Training Material link on EDA Home
Page Click EDA POC and Executive Training
Modules Click on Function of interest
59EDA Users Guide
Refer to the EDA Users Guide
- STEP-by-STEP Instructions (for all Users)
- Entire section dedicated to the EDA Executive and
the EDA POC and their tasks/activities - Training Material
- Access EDA Home Page
- Click Training Material link on EDA Home Page
- Click EDA POC and EDA Executive Training Module
- Select specific training area of interest
The End