GETS - Laserfiche WebLink

New Search

Importance of GETS card validations Understanding GETS passwords It is imperative that your GETS POC and user Each GETS card has an assigned password. The information be reviewed and validated annually. We password is established on the initial request form for must be able to contact the POCs and maintain each individual GETS card. This password is not the proper accountability for GETS cards. The validation same as the one used to log into POC accounts, but request will be sent to both the primary and alternate may be needed when calling User Assistance to open POC via a-mail. Please review the spreadsheet trouble tickets or request other assistance. attached to the e-mail and make the necessary updates through your online POC account. If the POCs should make sure all GETS users are aware of spreadsheet is correct, we still need to receive a their password. A POC can obtain assigned response as soon as possible confirming that there passwords through the GETS online G-WIDS are no changes. Please send your replies to system. The POC would log-onto the G-WIDS gwids ,saic.com. homepage, choose "Account Admin," followed by "POC Data Management App," and then click on Repeated failure to respond to the validation request "POC Data Set Request." In the comment box inside will result in cancellation of all GETS cards in the the application, state, "passwords to be included" and POC's account. then click "submit." You will receive an e-mail with your user information. The POC can also call GETS Requesting an updated GETS card User Assistance at 1-800-818 GETS (4387). Please note that GETS cards requested before 1999 Tell us your success story! do not have current information printed on them, including ~ = The spotlight is on you! Has GETS or alternate ~ WPS helped your organization in an i7iid 1~714~NCS{~ET~ (&87H1387} j aer~r~m~x~,s~y~e~zre,.;~arm~y~~,ee~p calling ~ emergency. We want to hear about it. "~`~`'`~'"~~n,~xads%~reralogcXn"s~xac,c methods and Please send us our stogy/ and ou could ATST: 1.ff9° "b$~A99J ~4P <"'4 r X~9 ~ y y M:G 1.$C„GpdS#P -a• .,b+X12 t1.716SY713H7 ,.~.~~Pb .,r g„b>,,,~ test call phone be featured in a future article. ~ ~ ~ numbers. If ~R ~ ~ ~ you would NewsNotes belongs to you! We are always looking - ry, , like an for ways to improve our service to you. If you have updated any topics you would like addressed in this GETS card for anyone in your organization, please newsletter or suggestions about how we can better log onto your POC account and use a "Change assist you, please submit your ideas to Form" to request a reprint of the card. gwids(a~saiacom. Sub-organization naming convention The purpose ofthe sub-organization name is to help G G~CS/«'YS Contact lnformation: POCs and alternates locate GETS and WPS users within their organizations. We recommend that sub- E-mail: ~~wid~~~~i5aic.com organizations be as general as possible. Normally lnformation Hclp llesk: 866-NCS-CALL they should have no fewer than five users. For DC Metro Area: 70 5-676-CALL smaller organizations, a single sub-organization is Trouble .Help Desk: 800-R 1 ~-GF I~S usually sufficient since users are likely to know each 'Fax: 70 ~-848-0299 other personally. Larger organizations often benefit NCS wehsitc: ~~~~~~w.ncs.~ov from assigning users to different sub-organizations based on their department or geographical location. E'TS website: ~~t~,ncs.~~ov When doing so, the sub-organization name should be W'P5 wcbsite: w ~s.ncs.~ov no more specific than necessary (e.g., do not use an immediate office symbol if a higher-level department name is sufficient).