Dear DISS Community, welcome to the new DISS Webinar page where you can find all things DISS JVS Webinar related including upcoming trainings, training materials, and Q&As.
A: With recent update to DISS, the visit must be cancelled before the archive option will become active to select. As a reminder if you cancel a visit, it will send a notification out to the creating SMO notifying them know that the visit was canceled, and it will remove the visit.
A: Until 13.7 is released, recommend adding a word such as "Received" or "Worked" in the Visit Name. This will provide a way to sort your visits by the key word added.
A: This feature allows you to easily copy an existing visit details as well as a quick check box to add all of the existing approved subject (visitors) to the newly cloned visit.
A: Yes, select the full date range from the calendar.
A: No. When a visit request is created, it is created only for a single SMO.
A: Run a visit report (permission based). Use View SMO Visits to view all visits for the selected SMO. Pull up individual subject to view their visits (with Owning Relationship).
A: When you create a visit you can use the “Activate Visit” button to make the visit active prior to adding subjects/visitors to the visit request. Once subjects/visitors are added the option to use the “Activate Visit” button will be grayed out and no longer available for selection. To search for visits that have been created but not activated use the View SMO Visits, find visit status and select “created” then Find Visits and you will see a list meeting that criteria.
A: You will need to manually cancel or archive each visit to move it from the active list.
A: As you are creating a visit request, if you complete it but don’t add subjects as visitors you will still be able to see the Activate request button, once you add subjects the visit becomes Active and the Activate Visit button is unavailable or grayed out.
A: You can use the Activate Visit button to make a visit active without adding subjects. Once you add subjects, the visit is Active and you can no longer access the Activate Visit button, it is grayed out.
A. No, you cannot edit an Archived Visit.
A. No, a visit request should not be Archived before the end date of the visit
A: DCSA is currently working with stakeholders to address this issue; the military will be advised that all visits should remain active in the system.
A: Users with the Update PII permission (must have Security Manager or Officer Role) may update subject last name, birth country, birth state, birth date, and citizenship.
A: DISS allows to transfer individuals and/or multiple subjects using the mass transfer functions unless certain actions on the subjects prevent it. If not working in mass function, debrief and add in new SMO.
A: All required fields are indicated with an asterisk (*). Category Organizations is an optional field.
A: Yes, if you have the proper role and permissions you can create a subject and establish relationship without granting access.
A: You don’t need to terminate the employee, you can add an owning relationship with the individual from the SMO Relationship tab, then delete the servicing relationship.
A: With Trusted Workforce, the hiring of new personnel and initiating an investigation is based on the current eligibility in DISS and the date of last investigation. If no eligibility is showing in DISS, initiate new (initial) investigation. If eligibility is showing in DISS, Security Manager (SM) can brief subject in access based on level supported, then SM should determine need for investigation based on date of last investigation and initiate PR if the investigation is no longer in scope. SM should work with VROC to enroll subject in Continuous Evaluation. Note: Reciprocity can be used if information is provided to VROC and DoD CAF for validation.
A: Yes, the function is available.
A: You cannot change the SMO relationship from servicing to owning. You must add a new relationship and then delete the previous relationship that no longer applies.
A: There is currently no way to add a servicing relationship without a subject first having an owning relationship.
A: You can add an owning relationship to an uncleared person without granting access.
A: If an individual, who only requires suitability or HSPD-12 credentialing, belongs to your organization you should have an owning relationship in JVS with that subject. Defer to your agency policy for this action.
A: Phone Number 1-800-467-5526, Customer Service Hours: 8:00 a.m. – 8:00 p.m. ET, Monday – Friday (excluding Federal Holidays). Security Manager and Security Officer with the Update PII permission can edit subject’s PII.
A: Go to the Subject Details, click the Other Subject Details tab, scroll down to Foreign contacts and relatives information block, find the family members that you need to edit and click the pencil icon under the options, that should allow you to edit the record.
A: Contact Servicing CAF or Component Adjudicator.
A: You must have the appropriate permission(s): Manage SCI Access or View SCI Access
A: The way I have seen a by name look up is if you go to View Subjects, you will see a list of Subjects associated with your agency then type in name and click ‘search’. If you are not associated with the subject, go to search subject to search using only the SSN. DoD ID number is not supported in DISS.
A: In short, you can do the debrief and removing all owning and servicing relationships then that subject won’t show up under your SMO. Please refer to the JVS User Manuel under the help hyperlink in JVS.
A: User complete and submit a CSR/Request Reciprocity in the Subject Action drop down in JVS.
A: DCSA leaves the naming of SMOs to the individual agency. Use the “Search SMO” function to find a particular SMO. Narrow search using drop-down menus.
A: Use the “Mass Subject Transfer” option in the Subject control panel.
A: One SMO doesn’t have multiple owners, however, one subject can be owned by multiple SMOs under the SMO relationship tab, usually if the subject has more than one category (i.e. reserve, industry, civilian employee, etc.).
A: The SMO Name Index is Numeric Characters, where this Code comes from or how a Security Manager or Security Officer is notified of this Code. Reference the JVS User Manual 22.214.171.124 Create SMO, item 5, on page 89.
A: DISS JVS is not set up to show SMO JPAS levels. DISS JVS permission levels provide the users the ability to manage and view specific access levels. All subjects can be managed from one SMO instead of the many levels that were used in JPAS.
A: Send a Hierarchy Change Request (HCR) to the following email address stating the need remove the SMO: email@example.com
A: Please send the information through the help desk and the DISS will research for removal.
A: No, that is incorrect. Provide SMO name and send request to have subjects removed and SMO deleted to the HCR email address: firstname.lastname@example.org
A: Currently, the SMO continues to display in the SMO Tree, but with a red “no” symbol on top that indicates it has been deactivated. As a hierarchy manger you can deactivate SMO within your tree. If unable to deactivate, send a Hierarchy Change Request (HCR) to the following email address stating the need to remove the SMO: email@example.com
A: Submit a Hierarchy Change Request to: firstname.lastname@example.org
A: There is no requirement to submit SF312 for debrief actions.
A: What type of access were you attempting to transfer. Collateral access should be removed at the time the individual out-processes.
A: Yes. You must consult your Agency policy on destroying hardcopy of documents.
A: If there is a date, the information transferred when the individual’s record transferred from JPAS so in theory an NDA was completed previously. A date will also populate when a new Sf312 is uploaded.
A: Submit a ticket with help desk.
A: Select document type which will open a new window. From there click the ‘Add Document’ button at the bottom and it should upload from there.
A: You must have the “View SCI Access” optional permission granted by your Account Manager and given to you as a JVS User (Security Officer/Security Manager Role) within JVS.
A: You must have the “Update PII” optional permission granted by your Account Manager and given to you as a JVS User (Security Officer/Security Manager Role) within JVS.
A: Yes. Please work this process with your supporting government agency.
A: Yes, you will need to submit a PSSAR with the optional permissions of view SCI Access checked (your Account Manager, who must have “Manage SCI DISS User” permissions, will provide you with that permission if your agency policy allows).
A: The Account Manager or Hierarchy Manager who gives access to JVS can grant this permission, however this would be an internal agency policy determining who, within the organization determines who is granted the “manage or view SCI access”.
A: If there is nothing to select from and you have an owning relationship, it is highly likely that the citizenship field is blank. Security Manager and Security with the Update PII permission can update the citizenship. Also check the investigation is scheduled.
A: First consider internal agency rules within your organization. Within JVS go to Access and select Access level from drop down screen to add to the individual.
A: Yes, it has been submitted to VROC.
A: IT levels are no longer supported by policy and not in DISS for use.
A: Servicing CAF or Component Adjudicator with Suitability and HSPD-12 Adjudication permissions grants the Suitability Eligibility.
A: DISS Team is in the process of creating a way to archive the messages while also trying to bring back the message capability to DISS to enhance communication within the system.
A: The red highlight notification is not a feature in DISS. You can refer to the Task Inbox for updates/changes/notifications.
A: Please provide the information to your assigned Industrial Security Representative (ISR), who can notify the DISS Team will collaborate with the NISS and DISS developers for a resolution. Additionally, please include some examples to the help desk so the DISS Team can verify the SMO is tied to your organization as identified in NISS.
A: Subjects owned or serviced by your SMO should populate in the Subject Report, if not please contact the help desk with examples so the DISS Team can troubleshoot.
A: The Account Manager who gives you access to JVS can grant this permission (as long as they also have “Manage SCI DISS User”), however this would be an internal agency policy determining who is granted this permission.
A: Contact help desk. Additionally, confirm that you removed all accesses or relationships from the subject.
A: You must have the manage SCI access or view SCI access permission for the SCI report.
A: Contact your Agency for this policy information.
A: JPAS did not have the capability to upload documents. The annotation that an NDA was completed with the completion date stored in JPAS will eventually be transitioned to DISS. All NDA dates from JPAS will be transferred to DISS – JVS.
A: Yes, you should not print material from DISS for sharing with other parties. Non-DoD agencies can submit a PSSAR to gain access to DISS-JVS to validate a subjects’ eligibility and access to include owning industry SMO.
A: Yes, based on SEAD 3 requirements.
A: You can see the investigating agency now if you own or service the individual and you click on the subject details link, then scroll down to the Investigation History table and click the investigation you are interested in, an Investigation Detail window opens up and shows information about that investigation including the investigating agency. Currently, not visible from the Subject Summary page
A: No, you can only search by SSN/PSSN or within your subject view by Last name and/or First name
A: This is not a report type.
A: There was a mapping issue with data involving eligibility from JPAS to DISS; clean-up was completed. If you continue to identify issues, please send an email to the Vetting Risk Operations Center (VROC) or submit a DISS Customer Service Request (CSR).