Attachment 0001_Contractor Overhaul TAV-C Requirements - Copy.pdf

PDF 2 MB Posted

Attached to
Overhaul of the UH-60 Modulating Valve
Solicitation number
W58RGZ-25-B-0008
Issued by

About this file

This file contains three documents: an Army IT User Access Agreement from September 2021, Contractor Overhaul TAV-C Requirements, and a TAV-C Portal Access Standard Operating Procedure for End Users (version 05) from March 2023. Together they outline the requirements and procedures for contractors to access the Army's Total Asset Visibility – Contractor (TAV-C) capability within the Logistics Modernization Program (LMP).

The documents detail two methods for contractors to exchange inventory data with LMP: 1) Defense Logistics Management Standards (DLMS) interface or 2) the Army TAV-C Portal. For portal access, contractors must obtain either a Common Access Card (CAC) or Department of Defense approved ICAM Multi-Factor Authentication certificate. Key requirements include completing cybersecurity training, signing IT user agreements annually, coordinating with Contracting Officer Representatives for system access, and following specific procedures for account creation and authentication. The documents provide detailed technical specifications and step-by-step instructions for contractors to establish and maintain access to manage Government Furnished Equipment/Material/Property inventory records that are subject to Army audits.

View the file

Other files

File Type Posted
Attachment 0003_Document Summary List.pdf PDF
Exhibit A.pdf PDF
W58RGZ25B0008.pdf PDF
Attachment 0005_Government Furnished Property Spreadsheet.xlsx XLSX spreadsheet
Attachment 0004_TDPL.pdf PDF
Attachment 0002_MO Packaging Requirments.pdf PDF
Attachment 0006_Sealed Bidding Pricing Template.xlsx XLSX spreadsheet
Attachment 0007_Form 1379.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Army IT User Access Agreement, SEP 2021

ARMY IT USER ACCESS AGREEMENT

The requirements in this IT User Access Agreement are consistent with the policy established in Army Regulation 25-2, Army Cybersecurity; the proponent agency is OCIO.

PART I

ACKNOWLEDGEMENT AND CONSENT

1. Acknowledgement. By signing the user agreement, the user acknowledges and consents that when they access Department of Defense (DoD) information systems you are accessing a U.S. Government (USG) information system (IS) (which includes any device attached to this information system) that is provided for U.S. Government authorized use only.

2. Consent.

a. You consent to the following conditions:

(1) The U.S. Government routinely intercepts and monitors communications on this information system for purposes including, but not limited to, penetration testing, communications security (COMSEC) monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.

(2) At any time, the U.S. Government may inspect and seize data stored on this information system.

(3) Communications using, or data stored on, this information system are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any U.S. Government authorized purpose.

(4) This information system includes security measures (e.g., authentication and access controls) to protect U.S. Government interests—not for your personal benefit or privacy.

b. Notwithstanding the above, using an information system does not constitute consent to personnel misconduct, law enforcement, or counterintelligence investigative searching or monitoring of the content of privileged communications or data (including work product) that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Under these circumstances, such communications and work product are private and confidential, as further explained below.

(1) Nothing in this User Agreement shall be interpreted to limit the user’s consent to, or in any other way restrict or affect, any U.S. Government actions for purposes of network administration, operation, protection, or defense, or for communications security. This includes all communications and data on an information system, regardless of any applicable privilege or confidentiality.

(2) The user consents to interception, capture, and seizure of ALL communications and data for any authorized purpose (including personnel misconduct, law enforcement, or counterintelligence investigation). However, consent to interception or capture or seizure of communications and data is not consent to the use of privileged communications or data for personnel misconduct, law enforcement, or counterintelligence investigation against any party and does not negate any applicable privilege or confidentiality that otherwise applies.

(3) Whether any particular communication or data qualifies for the protection of a privilege, or is covered by a duty of confidentiality, is determined in accordance with established legal standards and DoD policy. Users are strongly encouraged to seek personal legal counsel on such matters prior to using an information system if the user intends to rely on the protections of a privilege or confidentiality.

(4) Users should take reasonable steps to identify such communications or data that the user asserts are protected by any such privilege or confidentiality. However, the user's identification or assertion of a privilege or confidentiality is not sufficient to create such protection where none exists under established legal standards and DoD policy.

(5) The user’s failure to take reasonable steps to identify such communications or data as privileged or confidential does not waive the privilege or confidentiality if such protections otherwise exist under established legal standards and DoD policy. However, in such cases the U.S. Government is authorized to take reasonable actions to identify such communication or data as being subject to a privilege or confidentiality, and such actions do not negate any applicable privilege or confidentiality.

(6) These conditions preserve the confidentiality of the communication or data, and the legal protections regarding the use and disclosure of privileged information, and thus such communications and data are private and confidential. Further, the U.S.

Government shall take all reasonable measures to protect the content of captured or seized privileged communications and data to ensure they are appropriately protected.

(7) In cases when the user has consented to content searching or monitoring of communications or data for personnel misconduct, law enforcement, or counterintelligence investigative searching, (that is, for all communications and data other than privileged communications or data that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants), the U.S.

Government may, solely at its discretion and in accordance with DoD policy, elect to apply a privilege or other restriction on the U.S. Government’s otherwise-authorized use or disclosure of such information.

(8) All of the above conditions apply regardless of whether the access or use of an information system includes the display of a Notice and Consent Banner (“banner”).

When a banner is used, the banner functions to remind the user of the conditions that are set forth in this User Agreement, regardless of whether the banner describes these conditions in full detail or provides a summary of such conditions, and regardless of whether the banner expressly references this User Agreement.

PART II

INFORMATION SYSTEM ACCESS

1. Understanding. The user understands that they have the primary responsibility to safeguard the information contained on the system being accessed from unauthorized or inadvertent modification, disclosure, destruction, denial of service, and use. Any use of Army Information Technology (IT) is made with the understanding that the user will have no expectation as to the privacy or confidentiality of any electronic communication, including minor incidental personal uses.

2. Access. DoD policy states that Federal Government communication systems and equipment (including Government owned telephones, facsimile machines, electronic mail, internet systems, and commercial systems), when use of such systems and equipment is paid for by the Federal Government, will be for official use and authorized purposes only. Official use includes emergency communications and communications necessary to carry out the business of the Federal Government. Authorized purposes include brief communications by employees while they are traveling on Government business to notify family members of official transportation or schedule changes.

Authorized purposes can also include limited personal use established by appropriate authorities under the guidelines of the DoD Regulation 5500.7-R, para. 2-301 “Joint Ethics Regulation.”

a. Internet Access. Internet access is intended primarily for work related purposes.

(1) The user will not circumvent any filters or blocks to gain access to restricted sites.

(2) If denied access to a particular website, needed for official or authorized use, the user will follow procedures on the “blocked website” notification to request the site be unblocked.

(3) The user will not use Army IS for activities that are illegal, inappropriate, or offensive to fellow employees or the public. Such activities include, but are not limited to: hate speech, or material that ridicules others on the basis of race, creed, religion, color, sex, disability, national origin, or sexual orientation.

(4) The user will not inflict harm through the use of electronic communication – the transfer of information (signs, writing, images, sounds, or data) transmitted by computer, phone, or other electronic device. Examples include harassment, bullying, hazing, stalking, discrimination, retaliation, or any other types of misconduct that undermines dignity and respect.

b. Email.

(1) The user will adhere to the email practices as outlined in AR 25-1 or your local command.

(2) The user will properly report chain email, spam, and virus warnings by following the reporting procedures outlined by your local command.

(3) The user will not provide personal or official information if solicited by email

(4) The user will not use personal, commercial email to conduct official government business.

(5) The user will not auto-forward email from official government email to a commercial or personal email accounts.

3. Revocability. Access to Army resources is a revocable privilege and is subject to content monitoring and security testing. If the user knowingly threatens or damages an Army Information System (IS) or communications system (for example, hacking or inserting malicious code or viruses) or participates in unauthorized use of Army network(s), the user will have their network access suspended or terminated.

4. Secret Classified Information Processing.

a. The SIPRNet is the primary classified IS for the Department of the Army.

SIPRNet is a United States DoD system and approved to process SECRET collateral information.

(1) SIPRNet provides classified communication to external DoD organizations and other U.S. government agencies via electronic mail.

(2) The SIPRNet is authorized for SECRET or lower- level processing in accordance with the DoD Connection Approval Process (CAP).

(3) The classification boundary between SIPRNet, and NIPRNet requires vigilance and attention by all users.

(4) The ultimate responsibility for ensuring the protection of information lies with the user. The release of TOP SECRET information through the SIPRNet is a security violation and will be investigated and handled as a security violation or as a criminal offense.

5. Unclassified Information Processing.

a. The NIPRNet is the primary unclassified information system for the Department of the Army. NIPRNet provides unclassified communication to external DoD and other United States Government organizations. Foreign Nationals may only access the network with authorizing official (AO) approval. Any release of Secret information on NIPRNet is a security violation and will be investigated and handled as a security violation or as a criminal offense.

b. NIPRNet is approved to process CUI, UNCLASSIFIED, SENSITIVE information in accordance with the DoD Connection Approval Process (CAP). It is not authorized to process confidential classification.

c. The NIPRNet and the Internet, as viewed by the Army, are synonymous. Email attachments are vulnerable to interception as they traverse the NIPRNet and Internet.

6. Public Key Infrastructure (PKI) Use.

a. Public Key Infrastructure provides a secure computing environment utilizing encryption algorithms (Public/Private-Keys).

b. Token/Smart Card (or CAC). The Cryptographic Common Access Card Logon (CCL) is now the primary authentication mechanism for all Army users (with very few exceptions). This is a two phase authentication process. First, the CAC is inserted into a middleware (reader), and then a unique user PIN number provides the validation process.

c. Digital Certificates (Private/Public Key). The CAC is used as a means to sending digitally signed e-mail and encrypted e-mail.

d. Private Key (digital signature), should be used whenever e-mail is sent, with the exception when sending to non-government. The digital signature provides assurances that the integrity of the message has remained intact in transit, and provides for the non-repudiation of the message that the sender cannot later deny having originated the e-mail.

e. Public Key is used to encrypt information and verify the origin of the sender of an email. It must be used to send sensitive information, information protected by the Privacy Act of 1974, and Information protected under the Health Insurance Portability and Accountability Act (HIPAA).

7. Minimum Security Rules and Requirements.

a. As an information system user, the following minimum security rules and requirements apply.

(1) The user is not permitted access to an information system unless in complete compliance with the DoD and Army personnel security requirements for operating in a SECRET (SIPRNet) or UNCLASSIFIED (NIPRNet) environment.

(2) The user must complete the approved DoD Cyber Awareness Challenge training at https://cs.signal.army.mil (primary site) or https://jkosupport.jten.mil/Atlas2/page/login/Login.jsf. Large groups can use the DoD Facilitator’s Guide training as a last option, and participate in all training programs as required (inclusive of threat identification, physical security, IT User Access Agreement policies, malicious content and logic identification, and non-standard threats such as social engineering) before receiving system access. The user understands that the initial training certificate will expire one year from the date that the training is successfully completed and that the completion of annual refresher training is required (in accordance with AR 25-2).

(3) The user will use only authorized hardware, firmware, and software. The user will not install or use any personally owned hardware, software, firmware, shareware, or public domain software on Army IT without prior authorization of the AO.

(4) The user will not introduce executable code (such as, but not limited to, .exe, .vbs, or .bat files) to the IS without authorization by the AO, nor will they write malicious code.

(5) The user will use virus-checking procedures before uploading or accessing information from AO authorized removable media (for example, diskette, Universal serial bus [USB] device, compact disk, or secure digital memory card) to an Army IS.

The user will not attempt to access or process data exceeding the authorized IS classification level. Ensure proper classification markings, storing, transportation and destruction of all SIPRNET CDs/DVDs.

(6) The user will not alter, change, configure, or use operating systems or programs, except as specifically authorized.

(7) The user will safeguard and mark with appropriate classification level on all information created, copied, stored, or disseminated from the IS and will not disseminate it to anyone without a specific need to know.

(8) The user is responsible for removing their hardware PKI Token and ensuring that their computer has logged off prior to departing the area.

(9) The user will not utilize ARMY or DoD-provided ISs for commercial financial gain or illegal activities.

(10) Maintenance will be performed by the System Administrator (SA) only.

(11) The user will immediately report any suspicious output, files, or system problems to the information systems security officer (ISSO) and follow local Incident Reporting Plans. All activities will cease on the system.

(12) The user understands that monitoring of an information system will be conducted for various purposes and information captured during monitoring may be used for administrative or disciplinary actions or for criminal prosecution.

(13) The user understands that unauthorized use or abuse of DOD and Army telecommunications, unified capabilities (UC), and computing systems (including telephone, email systems, DOD mobile devices, web services, or other systems) may subject users to administrative, criminal, or other adverse action.

(14) The user understands that Army IT resources will not be used in a manner that would reflect adversely on the Army, such as chain letters; unauthorized advertising, soliciting or selling; uses involving gambling or pornography; uses that violate statute or regulation; or other uses that are incompatible with public service. The user understands that it is their duty to immediately report all Cybersecurity related events, potential threats, vulnerabilities, and compromises or suspected compromises involving Army IT resources to the appropriate ISSO.

(15) The user understands that they are responsible for any activity conducted using their account. The user understands that they may only use the account to which they are assigned and may not allow others to use their account, or permit the use of remote access capabilities through Government provided resources with any unauthorized individual. The user's password or PIN is not to be shared with anyone, including the supervisor. Users are responsible for taking reasonable precautions to maintain the security of their accounts and the data to which they are authorized access.

(16) The user must not directly access, download or view emails and email attachments containing or labeled as classified or unclassified sensitive information (for example, Controlled Unclassified Information) from a device, equipment, system or network (for example, cellphone, tablet, computer) not specifically authorized to process such information – either directly or through a website (for example, webmail) – unless this is done in a formally authorized and secured manner (for example, virtual environment, secure viewing application, sandbox application, secure thin client) that prevents such information from being either temporarily or permanently stored on the device, equipment, system, or network.

b. Users of Army furnished collaboration technology, or with virtual access to official government information, will not conduct official government business, in close proximity to Self-Monitoring, Analysis, and Reporting Technology (SMART) Internet of Things (IoT) devices and Intelligent Personal Virtual Assistant (IPVA) applications, without appropriate security measures in place. Examples of appropriate security measures include turning off SMART IoT devices, disabling the “audio” access and

“recording” functions from SMART IoT devices and IPVAs, or moving far enough away from their listening and viewing range.

8. The user will adhere to the following requirements regarding the use of social media.

a. Users will utilize social media sites only as authorized by job or duty description, for official government purposes, to conduct official business or to release official agency information or other official communication.

b. Users may establish and use personal accounts only within a personal capacity.

Personal accounts must have no connection to official agency sites and must not appear to be, or represent, official opinion or content. Users recognizes that their identity could be misused by the general public’s perception of their acting in official responsibility or openness. Users cannot use personal accounts to conduct official business or release official agency information or any other official communication related to the job or government activities.

c. Users recognize it is their responsibility to ensure that they are not giving the false impression that they are acting in an official capacity when using government office equipment for non-government purposes. If there is expectation that such a personal use could be interpreted to represent an agency, then an adequate disclaimer must be used.

d. Users understand the use of government systems to access and manage personal sites during official duty hours is strictly prohibited.

9. The user will adhere to the following requirements regarding political activism:

a. Users will not use the Army IS to engage in political activity while on duty (on pay status, other than paid leave, or representing the government in an official capacity) or in the workplace.

b. Users will not engage in political activity in an official capacity at any time. This includes using an official email account or a social media account created for use in an official capacity to engage in political activity.

c. Users will not use the Army IS to suggest, solicit or receive political contributions at any time.

d. Users will not use the Army IS to engage in political transmissions, to include transmissions that advocate the election of particular candidates for public office.

10. When a user is issued a mobile device, the issuing officer will provide a separate agreement to sign.

PART III

1. Acknowledgement.

a. I have read, understand, and agree to abide by the responsibilities and requirements for IT usage and information handling in accordance with this agreement.

b. I have read, understand and agree to the notice of privacy rights, and consented to monitoring and searches in accordance with this agreement.

c. I have read, understand, and accept that violations of my responsibilities, unacceptable use of IT, or mishandling of information, may be punishable by administrative or judicial sanctions, may result in revocation or suspension of authorized access, may require remedial training in order to regain access, or may negatively influence adjudication decisions of security clearances.

Organization/Division/Office Symbol Military/civilian/Contractor/FN

Last Name, First, MI Date

Signature

REFERENCES

1. All Army Activities (ALARACT) 014/2017 (Professionalization of Online Conduct), 23

February 2017

(http://www.apd.army.mil)

2. Army Regulation (AR) 25-1 (Army Information Technology), 15 July 2019

3. Army Regulation (AR) 25-2 (Army Cybersecurity), 4 April 2019

4. CNSSI (Committee on National Security Systems Instruction) 1300 (Instruction For

National Security Systems Public Key Infrastructure X.509 Certificate Policy Under

CNSS Policy No. 25), October 2009

(http://www.hsdl.org)

5. CNSSP (Committee on National Security Systems Policy) 25, (National Policy for

Public Key Infrastructure in National Security Systems), 11 December 2017

(http://www.cnss.gov)

6. Department of Defense Chief Information Officer Memorandum (Department of

Defense Commercial Mobile Device Implementation Plan) 15 February 2013

(http://dodcio.defense.gov)

7. DoD 5220.22-M (National Industry Security Program Operating Manual (NISPOM)), February 2006

(http://www.dss.mil)

8. DoD 5500.7-R (The Joint Ethics Regulation), 17 November 2011

(http://www.esd.whs.mil)

9. DoD 8570.01-M (Information Assurance Workforce Improvement Program, Change

4), 10 November 2015

10. DoDD 5205.16 (The DoD Insider Threat Program, Change 2), 28 August 2017

11. DoDD 8140.01 (Cyberspace Workforce Management, Change 1), 31 July 2017

12. DoDI 1020.03 (Harassment Prevention and Response in the Armed Forces), 8 February 2018

13. DoDI 8500.01 (Cybersecurity), 14 March 2014

14. DoDI 8510.01 (Risk Management Framework (RMF) for DoD Information

Technology (IT), Change 2), 28 July 2017

15. DoDI 8530.01 (Cybersecurity Activities Support to DoD Information Network

Operations, Change 1), 25 July 2017

16. National Institute of Standards and Technology (NIST) Special Publication (SP) 800-

53 revision 4 (Security and Privacy Controls for Federal Information Systems and

Organizations), 22 January 2015

(http://csrc.nist.gov/publications)

17. National Institute of Standards and Technology (NIST) Special Publication (SP) 800-

53a (Assessing Security and Privacy Controls for Federal Information Systems and

Organizations: Building Effective Assessment Plans), 18 December 2014

(http://csrc.nist.gov/publications) http://csrc.nist.gov/publications) http://csrc.nist.gov/publications)

Contractor Overhaul TAV-C Requirements

Maintenance, Overhaul and/or Upgrade Requirements

I. INTRODUCTION

A. Army Materiel Command (AMC) and its units use Total Asset Visibility – Contractor (TAV-C) capability in its Logistics Management Program (LMP) to account for Government Furnished Equipment, Materiel, or Property (GFE/M/P) placed in the possession of contractors to support contracts for: 1) Maintenance, overhaul, or upgrade work; 2) materials held for Stock, Store and Issue (SSI), or 3) New Production. Accounting records within LMP for this inventory are subject to verifying physical inventories and audits by the Army to ensure accuracy. This section addresses contractor requirements for maintenance, overhaul and/or upgrade contracts.

II. SYSTEM OVERVIEW AND PORTAL ACCESS REQUIREMENTS

A. To use TAV-C, Contractors shall request one of two TAV-C access methods below to exchange required inventory data with LMP: 1) Defense Logistics Management Standards (DLMS) interface or 2) the Army TAV-C Portal. Approval of the contractor’s access method will be based first on the type of work being performed, second, the sufficiency of the contractor’s existing property accountability and connectivity to LMP, and third, request by the contractor to use the portal based on economic factors.

B. Contractors shall choose between the two methods for accounting for Government property as further described below:

1. DLMS interfaces: Contractors that have accounting systems capable of using a DLMS interface (see: DLM 4000.25, Defense Logistics Management Standards (DLMS) on the Defense Logistics Agency (DLA) website https://www.dla.mil/) shall request to use their accounting system and interface to account for GFE/M/P using DLMS transactions.

NOTE: If a contractor does not currently have an established DLMS interchange with DLA Defense Automated Addressing System (DAAS), the Contractor shall contact DAAS to establish access to DAAS messaging system to support the exchange of DLMS transactions with the Army. DAAS provides a value added service for standard Military Standards (MILS) transactions providing the ability to receive, edit and route logistics transactions for the Military Services and Federal Agencies. Information on DAAS can be found at https://www.dla.mil/HQ/InformationOperations/DAAS/

2. Army TAV-C Portal: Contractors, who, during negotiation with the Government, are determined to be allowed to use the TAV-C Portal, shall comply with prescribed processes to provide qualified workers to access the system to exchange data with LMP.

C. Portal Access Requirements. Contractor personnel, who input data into the TAV-C Portal, shall meet qualification requirements specified in the TAV-C Portal User Access – End User SOP. These requirements include:

1. Contractor provided computer system: The contractor shall provide a computer system and internet connectivity that meets acceptable standards as identified in the TAV-C Portal User Access – End User SOP.

2. Security Requirements.

(a) The Government requires contractor personnel accessing the LMP system to possess either a United States Government Common Access Card (CAC) or a

Contractor Overhaul TAV-C Requirements

Department of the Defense approved ICAM Multi-Factor Authentication (MFA) Certificate.

NOTE: It is the contractors’ responsibility ensure operators accessing the portal have and maintain current credential and to comply with contract requirements.

(b) Contractors will coordinate with the Contracting Officer’s Representative (COR) or designated government sponsor (herein referred to sponsor) to complete required online access registration and MFA process.

3. User Training Requirements: TAV-C Portal user training is Government provided and varies by the function performed. The training is online and completion of the training by each operator is required before accessing and using TAV-C.

4. The on-line training site will be provided by the government after award and access to the system has been granted. Functional training required to begin work should take approximately 1 hour to complete. The following courses are required for contractor overhaul and are listed under the TAV-C Portal User Role to Training Course Matrix section in the TAV-C Portal User Access – End User SOP.

a. LMP_TAVC_EDU_109_WBT

b. LMP_TAVC_DIST_204_WBT

D. Problem Resolution: LMP is a Government owned and maintained system. The contractor shall notify the COR or designated Government point of contact for system related issues and Government resolution.

III. DLMS TRANSACTIONS / PORTAL DATA REQUIREMENTS

A. For maintenance, overhaul and/or upgrade contracts, the contractor shall provide inventory management transactions to the Government by DLMS interface as follows:

1. DLMS 527R Materiel Receipt Acknowledgement (MRA) Transactions (for Government Furnished Material (GFM) expected to be consumed and GFE-R carcasses provided for overhaul).

B. For DLMS Transactions for maintenance, overhaul, and/or upgrade contracts, the material receipt transactions to be provided to the contractor by the Government via the DLMS interface are:

1. DLMS 527D Pre-positioned Material Receipt Document for stock in-transit to vendor.

C. Army TAV-C Portal: Contractors who, during negotiation with the Government, are allowed to use the TAV-C Portal shall exchange required data directly with LMP. Contractors who use the TAV-C Portal shall provide the following information via data inputs to LMP.

1. TAV-C Portal Requirements: Material Receipt Acknowledgment (MRA)

IV. PERFORMANCE REQUIREMENTS

A. The Contractor shall physically confirm material received (MRA) for actual National Item Identification Number (NIIN) and Quantity prior to recording receipt into LMP through DLMS or the TAV-C Portal.

Logistics Modernization Program

Total Asset Visibility – Contractor (TAV-C)

Portal Access Standard Operating

Procedure for End Users (version 05)

Change: User access procedures have been updated; SOP separated by role; added detail regarding annual IA training requirements

LMP’s TAV-C capability extends asset visibility to contractor locations, contributes to bettering the Army’s view of assets, and supports Army Readiness.

March 2023

LMP TAV-C Portal End User Access Procedures

Table of Contents

Introduction

Purpose Statement

TAV-C Portal Access – ICAM Account Process Flow

General Process Information & Assumptions

Process Details – Performed by the End User (without a CAC)

Process Details – End User with CAC

TAV-C Portal User Role to Training Course Matrix

Terms & Acronym List

Appendix A – End User Instructions

Create an Identity Record in (AMID)

Multi-Factor Authentication

HELPFUL LINKS & RESOURCES

Introduction

Logistics Modernization Program’s (LMP) Total Asset Visibility – Contractor (TAV-C) capability was developed to resolve audit findings related to the management of Army property. TAV-C capability extends asset visibility into contractor locations through improved recordkeeping and provides more accurate reports associated with this Government property. Use of TAV-C functionality by contractors is mandatory for Army Working Capital Fund (AWCF) managed property in the possession of contractors. This solution contributes to the management of assets supporting global equipment Readiness through LMP.

Contractors using the TAV-C Portal to input information into LMP will comply with the access processes described in this guide to establish and maintain user accounts, complete access processes, as well as Department of Defense (DoD) approved authentication, to receive access to this capability. The approved authentication is achieved one of two ways: with a Common Access Card (CAC) or via the creation of an Identity, Credential, and Access Management (ICAM) account in conjunction with multi-factor authentication. The ICAM program is designed to provide the mechanism for external entities to securely communicate with the DoD and authenticate to DoD information systems.

It is recommended Contractors carefully review this document and consider the amount of time needed to establish and maintain user security credentials, complete mandatory systems access training, apply for access to the system, and complete task specific user training.

–– Until these requirements are satisfied, portal access will not be granted. ––

The Training to FSR Matrix provides a list of user functional training courses and refer to the solicitation to verify the TAV-C functions needed for the effort.

Purpose Statement

The purpose of this document is to provide an understanding of the process for gaining access to the LMP TAV-C Portal solution for TAV-C Portal Contractors. The TAV-C Portal Contractors include:

1) Stock, Store, and Issue Contractor Portal Users

2) Vendor Proof of Delivery Contractor Portal Users

Please note that the DoD ICAM process illustrated in this document provide instructions on how to request an account and register in through Army Mobile Connect on any device that allows the user to get to the app store for double authentication. (Cellular phone or tablet) etc. Apple Store, Google Store or TRADOC App Gateway.

Internet Access to the LMP TAV-C Portal has been validated using Windows 10 or later, Edge, and Google Chrome browsers. Hardware requirements for LMP TAV-C Portal would be any hardware that can support Windows 10, Edge, and Google Chrome and connect to the Internet.

TAV-C Portal Access – ICAM Account Process Flow

General Process Information & Assumptions

• In accordance with AMC Operations Order 19-229, dated 111810Z Sep 2019, this guide establishes procedures and guidance for users to gain access to the TAV-C Portal.

• The Contracting Officer (KO) works with the requiring activity to establish a Contract Officer’s Representative (COR) (preferrable) to appoint for contract users. If the contract has no COR, the requiring activity shall immediately appoint a DA Civilian to serve as sponsor. The COR/DA Civilian is referred to as the sponsor hereafter.

• The sponsor informs the TAV-C Portal contractor of these procedures and requirements and assists end users with gaining access to the TAV-C Portal.

The sponsor reviews and approves the establishment of LMP end user accounts supporting TAV-C Portal processes. The sponsor functions as the Contractor’s point of contact for LMP systems issues.

• The Sponsor works with the designated Command UAM Administrator to identify TAV-C Portal Functional Security Roles (FSRs) required by the contractor.

• Organizations will follow their documented policy for assigning FSR to Portal end users.

• The COR/Sponsor works with the designated Command UAM Administrator to identify the access required by the contractor.

• The Command UAM will manage the required annual account review, which is required for TAV-C Portal end users.

Process Details – Performed by the End User (without a CAC)

TAV-C Portal users who will not be using a CAC are required to have the following:

- Signed memorandum from the Company stating that the User is an employee of the company and confirm U.S. Citizenship status

- Identify, Credential, and Access Management (ICAM) account

- Identity record in Army Master Identity Directory (AMID)

- Multi-factor authentication (MFA)

The information in this section is for TAV-C users without a CAC. Proceed to the Process Details - Performed by the End User (with CAC) section for CAC-enabled user guidance. The End User will be contacted by the COR/Sponsor to begin the ICAM account creation process. The ICAM account process will result in the User having an account setup in AMID. This is a time-sensitive process. See Appendix A for step-by-step instructions. The End User process steps are as follows:

1. User receives an email application to create their account in AMID via the ICAM Portal.

2. User completes the application information and submits the application, then notifies the Sponsor.

3. User receives a confirmation e-mail that their application has been approved by the Sponsor.

4. User completes the ICAM account setup process, which includes setting a password and setting up security questions.

5. User verifies they can log into the ICAM Portal successfully with their username and password.

6. User sets up multi-factor authentication (MFA) and notifies the Sponsor that their account creation and MFA setup is complete.

7. Non-CAC Users will complete the following requirements:

a. Information Assurance/Cyber Awareness (IA/CA) Training for Non- CAC enabled users @ https://public.cyber.mil/ → Training → Cyber Awareness Challenge.

b. Mandated Army IT User Agreement → the non-CAC user will receive a blank copy of the IT User Agreement to complete and print their full name and sign (with blue or black ink).

c. Non-CAC holder will take the IA training and sign the Army IT User Agreement every year.

8. Once #7 is complete, the User sends the IA Training certificate and signed Army IT User Agreement to their Contracting Officer (KO), COR or Sponsor; these requirements must be completed before submitting any access requests.

a. The Army IT User Agreement will be re-signed annually, and the IA Training will be completed annually.

https://public.cyber.mil/

b. The Army IT User Agreement and IA Training will also be repeated if assigned to another contract. The current Army IT User Agreement is not allowed to roll-over to a new contract.

9. The COR/Sponsor and UAM will continue the process and grant the user the “TAV- C Universal Role” to allow the User access to the TAV-C Training Library via the TAV-C Portal

a. Users must complete appropriate TAV-C functional web-based training courses. See TAV-C Portal User Role to Training Course Matrix for further guidance.

b. User will send their TAV-C training certifications to their COR/Sponsor to be sent to the UAM for final LMP functional security role (FSR) access provisions.

10. Once LMP account is updated and FSRs are assigned, the User can begin using the TAV-C Portal with their ICAM Account Username, Password and MFA.

Process Details – End User with CAC

TAV-C Portal Users who will be getting a CAC, or who have a CAC, should work with their designated UAM for guidance on getting an LMP account. This is an existing process. A signed company memo is still recommended for TAV-C CAC users, if they will only be using LMP for TAV-C purposes.

For initial guidance, refer to the process flow and steps below.

The steps below are needed to complete a System Authorization Access Request (SAAR) to grant LMP access. This is for CAC users only. NOTE: The SAAR form is subject to change; this is based off the form as of May 2022.

• TAV-C Portal CAC end user completes blocks 1 through 16A of the of DD 2875 and submit to user UAM.

• Supervisor for CAC holders completes blocks 17-17e of the DD 2875 and submits to responsible Unit Security Manager.

• Unit Security Manager completes blocks 22-26 of DD 2875 & and return to requester.

• Site Information System Security Officer (ISSO) completes blocks 19 – 19c of DD 2875 and returns to the requester.

• Site UAMs receive the completed SAAR form and add it to the user’s LMP account once the account is created.

Please note that the following requirements will be completed annually:

1. Complete the Information Assurance/Cyber Awareness (IA/CA) Training @ https://cs.signal.army.mil/ → Click on the link to Cyber Awareness Training (CAC login required)

2. Digitally signed Army IT User Agreement @ https://cs.signal.army.mil/ → Click on the link to the Mandated Army IT User Agreement (CAC login required) https://cs.signal.army.mil/ https://cs.signal.army.mil/

TAV-C Portal User Role to Training Course Matrix

Terms & Acronym List

Acronym Name

ACC Army Contracting Command

AMC Army Materiel Command

AMID Army Master Identity Directory

CA Cyber Awareness

CAC Common Access Card

DoD Department of Defense

FSR Functional Security Roles

HQ Headquarters

IA Information Assurance

ICAM Identity, Credential, Access Management

SAAR System Authorization Access Request

SPONSOR Contracting Officer’s Representative or Government Sponsor

TAV-C Total Asset Visibility – Contractor

UAM User Account Manager

Appendix A – End User Instructions

Create an Identity Record in (AMID)

Once the Sponsor has successfully created your sponsored account, you will receive an e-mail to the e-mail address provided during account creation (personal or work e-mail). This will initiate the user’s application to create their identity record in Army Master Identity Directory (AMID).

1. Open the email invitation, then copy and paste the link provided in the email into your browser.

NOTE: Launching the link directly from the email may not work depending on your browser, email and security settings therefore it is recommended you copy and paste the link into the browser manually. If you still get an error using the link, try launching in private or incognito browsing mode.

IMPORTANT: This link expires in 24 hours from the time it was generated; if this link expires, the Sponsor will need to resend it. Therefore, the sponsor shall immediately contact the Invited User by phone or other means to inform them to take immediate action to create an identity account.

Army Master Identity Directory Email Example

Appendix A Cont’d

2. Complete the “Personal Information” fields on the “Enter/Update Account Information” page:

Field Entry Additional Guidance

Title (Optional) Enter a title or leave blank -

First Name (Required) Enter your first name -

Middle Name (Optional) Enter your middle name or leave blank

Last Name (Required) Enter your last name -

Maiden Name (Optional) Enter your maiden name or leave blank

Suffix (Optional) Enter a suffix or leave blank -

Country of Citizenship (Required)

USA -

3. In the “ID Fields” section, select the checkbox for Check if you do not have a FASCN and do not plan to login with a CAC (Optional). This will populate additional ID fields. Complete the fields:

NOTE: You must complete AT LEAST one of the ID fields to be able to submit the application.

Field Entry Additional Guidance

SSN (Optional) Enter your social security number (###-##-####)

- This is the ONLY valid entry for non- CAC TAV-C end users

- System will validate unique SSN entries and will not accept duplicates; must be in the correct format

FIN (Optional) Enter a foreign identification number (must be 9 or 10 digits)

- DO NOT USE: not applicable to LMP TAV-C users

- Duplicate entries are acceptable

EDIPI (Optional) Blank

- DO NOT USE: for CAC users only

- User should not have (or use) the EDIPI field

4. Complete the “Duty Address” and “Contact Info” fields:

Field Entry Additional Guidance

DSN (Optional) Blank -

Organization (Optional) Enter your company name or leave blank

Country (Required) USA -

Street Address (Required) Enter your work street address

City (Required) Enter your work city -

State/Province/Region (Required)

Enter your work state -

ZIP/Postal Code (Required) Enter your work zip/postal code

Official Email (Optional) Blank At least ONE email address is required; use the SECONDARY email field (it should match the email used during account creation)

Secondary Email (Optional) Enter your personal/work email

Primary Phone Number (Required)

Enter your phone number -

Cell Phone Number (Optional) Enter your cell or leave blank -

Fax Number (Optional) Enter a fax or leave blank -

5. Click SUBMIT APPLICATION.

6. You will receive a Thank You confirmation system message and a confirmation email. Notify the Sponsor that the application is complete so they can complete the application approval.

Multi-Factor Authentication

The use of multi-factor authentication is a requirement to access the TAV-C Portal without a CAC.

You will require a personal device with access to download apps from the Apple App Store or Google Play.

1. Go to the Welcome // ICAM Portal (army.mil) and click on MobileConnect.

2. Click Register.

3. On the EAMS-A Login Single Sign-On page, enter your account username and password and click Login.

4. The page will show My Status: Not Registered. Follow the instructions on this page:

https://icamportal.us.army.mil/welcome

a. Download the MobileConnect app on the Apple App Store or Google Play.

b. Launch the app and follow the app instructions to register.

c. Scan the unique QR code on this webpage to complete registration. If needed, you can Refresh code from this webpage to update the unique QR code.

5. That's it. Now just log in to EAMS-A with your username and password. Each time you log in, you will receive a notification on your device asking you to approve or deny the login attempt. Be sure to have your device with MobileConnect installed handy during login.

HELPFUL LINKS & RESOURCES

Helpful Links

• Welcome // ICAM Portal (army.mil)

• ICAM Portal FAQs (army.mil)

• MobileConnect (army.mil)

• Service Portal - Service Portal (army.mil)

ICAM / EAMS-A Documentation

1. Service Portal - Service Portal (army.mil)

2. Click on Knowledge

3. Enter any of the KBA numbers below into the SEARCH field

• KB0012454 - ICAM: Account Types & Sponsorship

• KB0012455 - ICAM: How to Initiate Sponsorship

• KB0012656 - ICAM: How to Transfer a Guest to Another Sponsor

• KB0012451 - How to Reset your Password

Help Desk

• Contact AESD at 1-866-335-ARMY (2769) - for EAMS-A, ICAM, MFA https://icamportal.us.army.mil/welcome https://icamportal.us.army.mil/faq/ICAM_PORTAL_FAQS.pdf https://mobileconnect.us.army.mil/ https://snpro.aesd-w.army.mil/sp/ https://snpro.aesd-w.army.mil/sp/

OrganizationDivisionOffice Symbol:
Last Name First MI:
MilitarycivilianContractorFN:
Date:
undefined:

File details come from the government source that posted it. Updated .