DWSS Portal Structure

1. The DWSS TOMS requires individuals to execute certain responsibilities within the system to create legally binding Task Orders for services. These responsibilities are defined as 'Roles'. The main Roles are the Ordering Officer (or PCO), the 1102 (Contract Specialist) the Originator (requirements generator), the Task Order Manager (TOM or COR) and the Field User Administrator (FUA). The persons who are assigned these Roles, through the registration process except for the FUA, must be members of an entity which has already been incorporated into the DWSS Portal through the Portal system administrator.
2. The entity can be as large or small as it wishes. Generally the entity is identified by their UIC. A number of UICs can be aggregated for reporting purposes into a Command. For example within the Navy, NAVSUPSYSCOM is the overarching Command for a dozen or so sub Echelon Activities which may get registered in the Portal by their own UIC.
3. One or more UICs within a Command can be identified as a Superactivity. A user within a Superactivity with appropriate roles gains visibility and access into the other UICs within their Command. Having a Superactivity is not required; all UICs can have equal status within a Command.
4. Users of appropriate level of access can be appointed to be Activity (UIC) Superusers, Command Superusers, or Program (overall DWSS) Superusers. These users get higher level of access than the rest of the users, for example they can gain visibility to an Award Determination process without having to be appointed as Advisors on a package. Having Superusers is not required.

REGISTRATION PROCESS

DOD Organizational Entities (UIC): A few entities from the various Branches of the Service have already been loaded into the Portal. Additional entities who wish to become Ordering Offices must contact their respective Service Action Office to affect the Registration process. Each activity shall also appoint a Primary and Alternate Local Field User Administrator who will be responsible for approval and management of user accounts, including disabling accounts upon a user's departure from government service. These Local Administrators will be responsible only for management of user accounts and will not be required to perform any other function of DCSC system administration. Guidance will be provided by the DCSC program office to aid in the technical management of user accounts if necessary.

Individuals (Roles): Personnel belonging to registered entities can self registration at the Portal. The Field User Administrator for the entity will approve the registration and notify the applicant.

NOTE: The physical location of the Contracting Office as well as the Requirements Office is immaterial. The Portal only requires that the services themselves must be performed in the designated areas due to the applicability of the Service Contract Act.

There may also be some circumstances where the Requirements entity does not have Ordering Officer authority or the entity does not wish to become an Ordering Office in the Portal (this may be the only requirement they have). Individuals with Originator/Task Order Manager Roles can be registered as part of an Ordering Organization already in the system and thus will be able to have their requirements met. If this is the case, contact the Ordering Office you wish to utilize before attempting to register individual personnel.

NOTIFICATION OF PROBLEMS

Day to day portal issues shall be addressed to the Local Administrator. The Local Administrator can do the following:

• Reset passwords
• Unlock/lock account access
• Establish and modify system roles

Unresolved issues shall be referred to the DCSC Help Desk support provided by Aquilent. The SAO shall be the primary collection point for the identification of desired Portal modifications or chronic problems.