Attachment_003_PWS.docx
DOCX document 62 KB Posted
- Attached to
- Program Management Tracking System (PMTS) Federal contract opportunity
- Solicitation number
- N0060418Q4046
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Attachment_001_52.212-3.docx | DOCX document | |
| Attachment_002_DD254.pdf | ||
| Attachment_004_Sole_Source_Justification.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT (PWS)
United States Indo-Pacific Command Commander’s Action Group (J00CAG) Program Management and Tracking System (PMTS) Activation
1.0 BACKGROUND
The United States Indo-Pacific Command (USINDOPACOM) is a unified combatant command of the United States armed forces responsible for the Indo-Asia Pacific region. It is the oldest and largest of the unified combatant commands. Its Commander, the senior U.S. military officer in the Pacific, is responsible for military operations in an area which encompasses more than 100 million square miles, or roughly 52 percent of the Earth’s surface, stretching from the waters off the west coast of the United States to the west coast of India, and from the Arctic to the Antarctic.
The Commander’s Action Group (CAG), J00CAG, USINDOPACOM is a professional staff group that is responsible for communicating truthful, timely and factual unclassified and classified information about USINDOPACOM activities to national, allied, international and internal military and civilian audiences. J00 develops and provides agile, innovative solutions to the Commander’s toughest challenges and provides advice in all aspects of global engagement, including the development and dissemination of consistent, credible, reliable, accurate and current command information to target audiences.
2.0 SCOPE
This Performance Work Statement (PWS) is for the establishment and maintenance of a Program Management and Tracking System (PMTS) for use by J00CAG. The contractor shall provide services to establish PMTS modules, provide PMTS technical support, and provide PMTS training. This system will improve performance, and accelerate transformation by providing timely and accurate information at incredible speed thus enhancing USINDOPACOM’s decision making.
A persistent challenge for USINDOPACOM is effective coordination of critical initiatives in a rapid pace environment. Current management systems are insufficient for today’s operational tempo and multi-time zone collaboration. Paper, spreadsheets, localized databases, and task management systems are burdensome. Miscommunication and information lost to static documents can be measured in delays, inefficiency, and additive program costs.
Enhancing current collaboration and coordination practices present multiple opportunities to optimize regional warfighting priorities. A critical element of success for USINDOPACOM is the access to an overarching knowledge management tool that enhances command and control, leverages and reduces programmatic costs; automates core business processes; simplifies the work of staff members, directorates, and commanders; and creates a data set of transactional data that can be used for operational purposes.
3.0 TASKS
The PMTS tool will include activation of selected PMTS modules on a Federal Risk and Authorization Management Program (FedRAMP) certified infrastructure. FedRAMP is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services.
The Contractor shall perform the following tasks:
| Task Area 1: Establish PMTS Modules |
| Task Area 2: PMTS Technical Support |
| Task Area 3: PMTS Training |
3.1 Task Area 1: PMTS Modules
3.1.1 In accordance with the Contractor’s standard master subscription agreement, provide access to selected PMTS modules. Selected modules shall automate core business processes such as orchestration, scheduling, and preparation for the Commander’s engagements including: presentations, meeting agendas, talking points, trip reports, and follow on actions; streamline selected work tasks of staff members such as preparation of trip material including talking points, information papers, presentation, engagement recommendations, speeches, and research material on strategic initiatives, department heads, and commanders; and create a data set of transactional data including engagement planning, trip reports, presentations, talking points, speeches, trip calendars, and research associated with the Commander’s engagements that is currently lost in every similar type of organization – military, public sector, and private. Adopting PMTS sets the stage for a model that is useful across the Command.
3.1.2 A 90-day phase in period consisting of 45 days for configuration and report development shall be provided to the Contracting Officer’s Representative (COR); and 45 days for use, evaluation, and feedback as reported to the COR.
3.1.3. Provide PMTS functionality via a zero footprint, browser-based solution (e.g., Internet Explorer 8, no Active-x, no Java applets, or other browser plug-ins) that automates core business processes, simplifies the work of staff members, department heads, and commanders, and creates a data set of transactional data.
3.1.4 Access shall be given to designated J00CAG personnel for adding and deleting personnel as directed by the assigned J00CAG Government Point of Contact (POC).
3.1.5. Within 7 days of contract award, the contractor shall conduct a virtual kickoff meeting that includes J00CAG Government POC, contractor program lead, and contractor technical team lead. Purpose is to ascertain initial needs from J00CAG.
3.1.6. Within 14 days of the virtual kickoff meeting, provide a Plan of Action and Milestones (POA&M) that includes setup, orientation, and training for initial PMTS government users.
3.1.7. Within 60 days of contract award, complete the setup of selected PMTS modules as agreed to between J00CAG and contractor representatives. During the setup period, provide a selection of representative reports for evaluation and feedback that guides the initial module selection and activation.
3.1.8. Conduct Headquarters site visit either physically or virtually to ascertain the specific needs and design of J00CAG.
3.2 Task Area 2: PMTS Technical Support
3.2.1. The contractor shall provide technical support (i.e. provide help and advice) to the specified PMTS modules/applications via an outcome-oriented approach that will provide for maximum government-industry collaboration.
3.2.2. PMTS modules will be tailored to support and align USINDOPACOM missions with the policy directives outlined by the Office of the Secretary of Defense (OSD). The primary areas of OSD policy directives that will be covered include: National Security Strategy and National Defense Strategy implementation, integration and assessment of PACOM's efforts.
3.2.3. Ingest selected J00CAG spreadsheet data to demonstrate PMTS functionality and reporting features. Ingesting data refers to the selection and input of data from calendars, spreadsheets, trip reports, and presentations that can be used to demonstrate PACOM's efforts in accordance with the National Security Strategy and National Defense Strategy.
3.2.4. Provide hosting and maintenance support of the PMTS system with 99% functional availability. The contractor will notify the J00CAG when planned maintenance outages are scheduled to occur to include an estimated system restoration time.
3.2.5. Provide selective upgrades and enhancements of activated PMTS functional and reporting capabilities based on user experience and feedback. Functional input is consolidated and delivered to the contractor by the J00CAG COR.
3.2.6. Conduct program and functional reviews as required. Standard review items shall include:
· PMTS functional review and updates
· Government approval of status regarding open items
· Highlights since the previous review
· User access review (read/write profiles)
· POA&M updates
3.2.7. Provide access to the tool to allow the government to download existing government data.
3.3 Task Area 3: PMTS Training
3.3.1. Training and Orientation: During the set up period, at a time to be determined by the COR and contractor representatives, conduct an orientation and training session for initial users. Training will be either onsite or virtual. Additionally, as determined by the J00CAG COR, the contractor shall conduct other virtual orientation and training sessions in conjunction with new users or new functionality. Training topics shall include at the minimum:
· Discussion of functionality and business rules, reporting, document sharing, and use of information templates
· Definition of key system elements and follow-on layers (e.g. ability to conduct "deeper information dives")
· Confirmation of personnel using system or accessing reports
4.0 DELIVERABLES
All deliverables shall meet the requirements set forth in contractual documentation. The contractor shall provide all written deliverables (e.g., schedules, reports) electronically in Microsoft Office (Word, Excel, PowerPoint, Project, Visio,) and other recognized applications available to USINDOPACOM in formats pursuant to the following schedule.
PWS Section
Deliverable Dates
| Task # |
| Deliverable Title |
| Draft |
| Final |
| Frequency |
| 3.1.1 |
| Phase-in Period |
| N/A |
| Final Report, 90 Days after award |
| Once |
| 3.1.4 |
| Virtual Kickoff Meeting |
| N/A |
| 7 Days after award |
| Once |
| 3.1.5 |
| POA&M |
| N/A |
| 14 Days after Virtual Kickoff Meeting |
| Once; then update as changes are required |
| 3.1.6 |
| PMTS Module Setup |
| N/A |
| 60 Days after award |
| Once |
| 3.2.6 |
| Functional Review Meeting Summaries |
| Within 7 days after functional review meeting |
| Within 14 days after functional review meeting |
| After each functional review meeting |
| 3.3.1 |
| Training Attendee Summary |
| Within 7 days after training event |
| Within 14 days after training event |
| After each training event |
5.0 SERVICE DELIVERY SUMMARY
The Services Delivery Summary (SDS) represents the most important contract objective that, when met, will ensure contract performance is satisfactory. Although not all Performance Work Statement (PWS) requirements are listed in the SDS, the contractor is fully expected to comply with all requirements in the PWS.
| Task |
| Performance Objective |
| Performance Threshold |
| 3.1.1 |
| Operational System |
| 100% inspection. System up and operational per POA&M |
| 3.2.1 |
| Technical support |
| 24 hour response to inquiries via email or phone 99% of the time |
| 3.2.3 |
| Data ingestion |
| 100% inspection. Data ingested per established plan |
| 3.2.4 |
| Hosting and maintenance |
| 24 hour response to outages 99% of the time; with govt concurrence of issue resolution as available |
| 3.3.1 |
| Training |
| 100% inspection. All J00CAG desired users oriented to system per their availability |
6.0 QUALITY ASSURANCE
6.1. The Contractor is responsible for implementing and maintaining a Quality Control Program (QCP) to ensure that the work performed meets or exceeds contract requirements and results in the correction of potential and actual problems. The QCP shall be implemented on the first day of contract performance. The Government will provide the Contractor with a copy of the Government’s Quality Assurance Surveillance Program (QASP). Notwithstanding the Government’s QASP, the Contractor is not relieved from having their own QCP program to address quality issues during the contract award period.
6.2. The Government’s QASP will address what deliverables are identified for surveillance and the method and surveillance periodicity to ensure the quality of deliverables as outlined in this PWS. The QASP addresses what will be reviewed and will outline actions to be taken by the Contractor, should review(s) and/or inspections identify areas requiring remedial action. Of special interest to the Government are performance standards or metrics that address productivity, and completion times.
6.3. Periodic Progress Meetings: The Contractor shall participate in periodic progress meetings. At these meetings, the Contracting Officer’s Representative (COR) and Contracting Officer, if requested, will apprise the Contractor of how the Government views the Contractor's performance and the Contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government and may be in the form of telephone or video-conferencing and/or on-site meetings mutually agreed by both parties.
7.0 GENERAL INFORMATION
7.1 Place of Performance
The primary place of performance will be at contractor’s facilities. Task performance may occur at Government locations, as necessary.
7.2 Period of Performance
The period of performance will be for a twelve-month base period and six-month extension under FAR 52.217-8.
7.3 Security
7.3.1. Facility Clearance Level (FCL). The contractor must have a valid FCL at the SECRET level. Interim FCLs are acceptable provided they are not expired. FCL procedures and security guidelines for adjudicative requirements are outlined in Department of Defense (DOD) 5220.22-M and DOD 5200.2-R. FCLs and Interim FCLs must be awarded by the Defense Security Service (DSS) Facility Clearance Branch.
7.3.2. Personnel. All positions on this contract require a minimum of a SECRET clearance. Upon contract award, the contactor shall submit the names of contractor personnel to the USINDOPACOM Security Manager for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. This shall be completed before the COR/Trusted Agent (TA) accesses the DOD Trusted Associate Sponsorship System (TASS) and submits a request for issuance of the CAC to the contractor’s personnel. If a contractor’s employee does not have the required investigative or security clearance level based on the Government’s determination, the contractor’s employee will be denied the ability to work in support of this contract and the employee’s information will not be loaded into TASS.
8.0 PERSONNEL
8.1 The contractor shall provide sufficient personnel to satisfy the requirements of this PWS. In addition to the qualifications and requirements outlined in the basic PWS, the following are supplemental requirements associated with this PWS. Contractor is required to comply with Public Law 105-270, Section 5(2)(A). This law states that contractors will not perform inherently governmental functions. Section 5(2)(A) of this Public Law defines the term “inherently governmental function” as “a function that is so intimately related to the public interest as to require performance by Federal Government employees.” Per Section 5(2)(B), inherently governmental functions include management of Government programs requiring value judgments, conduct of foreign relations, selection of program priorities, and the direction of intelligence and counter-intelligence operations. Per Section 5(2)(C), inherently governmental functions DO NOT include, (i) gathering information for or providing advice, opinions, recommendations, or ideas to Federal Government officials; or (ii) any function that is primarily ministerial and internal in nature.”
8.2 USINDOPACOM Policies on Contractors. Government Rights: As specified in DFARS clause 252.227-7020, “The Government shall have unlimited rights in works first produced, created, or generated and required to be delivered under this contract.” The Government retains the right to all items produced in relation to their duties by personnel working under this contract.
8.2.1 Data Rights: All documents and materials produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. All materials/data supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.
8.2.2 Training of foreign personnel is prohibited under this PWS.
8.2.3 When performing the tasks associated with this PWS, contractor personnel shall make clear to all individuals they deal with that they are contractor employees and not DOD employees. When participating and introducing themselves during official events wherein DOD, non-DoD, or foreign officials are present, contractor personnel shall identify themselves as employees of the Contractor.
8.2.4 Contractor personnel may not manage, supervise or task DOD civilian employees or military personnel while performing the tasks within this PWS.
8.2.5 Contractor personnel may not make any commitment to non-DoD personnel, including a foreign official that commits the expenditure of US Government resources, unless specifically authorized.
8.2.6 Contractor employees performing services shall be required to comply with all HQ USINDOPACOM and installation rules and installation applicable to conduct, safety, security, and procedures governing site entry and exit.
8.2.7 Contractor personnel shall be required to safeguard data files and output products, regardless of format or medium, in accordance with appropriate security measures for classification of data being handled within HQ USINDOPACOM (see DOD Regulation 5200.1, OPNAVINST 5500.2). Contractor personnel shall also safeguard Privacy Act Information in accordance with existing regulations.
8.2.8 Contractor personnel shall not establish an employee-employer relationship with HQ USINDOPACOM under this PWS. Contractor personnel shall not provide personal services to HQ USINDOPACOM under this PWS.
9.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR)
9.1 Contracting Officer Representative (COR): The COR will be appointed by a separate letter and identified in the contract award. The COR will monitor all technical aspects of the contract and assists in contract oversight.
10.0 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)
10.1 The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for USINDOPACOM via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:
| • | W, Lease/Rental of Equipment; |
| • | X, Lease/Rental of Facilities; |
| • | Y, Construction of Structures and Facilities; |
| • | D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY; |
| • | S, Utilities ONLY; |
| • | V, Freight and Shipping ONLY. |
10.2. The contractor is required to completely fill in all required data fields using the following web address https://www.ecmra.mil .
10.3. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://www.ecmra.mil.
11.0 Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information Technology (IT) Systems or Protected Health Information (Jan 2017)
Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The Deputy Secretary of Defense Directive-Type Memorandum (DTM) 08-006 – “DoD Implementation of Homeland Security Presidential Directive – 12 (HSPD- 12)” dated November 26, 2008 (or its subsequent DoD instruction) directs implementation of HSPD-12. This clause is in accordance with HSPD-12 and its implementing directives.
· APPLICABILITY
This clause applies to contractor employees requiring physical access to any area of a federally controlled base, facility or activity and/or requiring access to a DoN or DoD computer/network/system to perform certain unclassified sensitive duties. This clause also applies to contractor employees who access Privacy Act and Protected Health Information, provide support associated with fiduciary duties, or perform duties that have been identified as National Security Position, as advised by the command security manager. It is the responsibility of the responsible security officer of the command/facility where the work is performed to ensure compliance.
Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.
· ACCESS TO FEDERAL FACILITIES
Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command’s Security Manager upon arrival to the Command and shall out-process prior to their departure at the completion of the individual’s performance under the contract.
· ACCESS TO DOD IT SYSTEMS
In accordance with SECNAV M-5510.30, contractor employees who require access to DoN or DoD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions which require access to information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity’s Command Information Assurance Manager.
Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) or T5 or T5R equivalent investigation, which is a higher level investigation than the National Agency Check with Law and Credit (NACLC)/T3/T3R described below. Due to the privileged system access, an investigation suitable for High Risk national security positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.
Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the “supervisor”.
The SAAR-N shall be forwarded to the Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.
When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.
· INTERIM ACCESS
The Command's Security Manager may authorize issuance of a DoD CAC and interim access to a DoN or DoD unclassified computer/network upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.
· DENIAL OR TERMINATION OF ACCESS
The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.
· CONTRACTOR’S SECURITY REPRESENTATIVE
The contractor shall designate an employee to serve as the Contractor’s Security Representative. Within three work days after contract award, the contractor shall provide to the requiring activity’s Security Manager and the Contracting Officer, in writing, the name, title, address and phone number for the Contractor’s Security Representative. The Contractor’s Security Representative shall be the primary point of contact on any security matter. The Contractor’s Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.
· BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVE DUTIES Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Contractor employees under this contract are recognized as Non- Critical Sensitive [ADP/IT-II] positions when the contract scope of work require physical access to a federally controlled base, facility or activity and/or requiring access to a DoD computer/network, to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC or T3 or T3R equivalent investigation to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The investigation consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a non-critical sensitive or IT-II position is required to complete:
· SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)
· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)
· Original Signed Release Statements
Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date. Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The
Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.
Regardless of their duties or IT access requirements ALL contractor employees shall in-process with the Command’s Security Manager upon arrival to the command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Employees requiring IT access shall also check-in and check-out with the Navy Command’s Information Assurance Manager. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The SAAR-N shall be forwarded to the Navy Command’s Security Manager at least 30 days prior to the individual’s start date. Failure to provide the required documentation at least 30 days prior to the individual’s start date shall result in delaying the individual’s start date.
The contractor shall ensure that each contract employee requiring access to IT systems or networks complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. Contractor employees shall accurately complete the required investigative forms prior to submission to the Command Security Manager. The Command’s Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM); Potential suitability or security issues identified may render the contractor employee ineligible for the assignment. An unfavorable determination is final (subject to SF- 86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Command’s Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DoD Central Adjudication Facility (CAF) for a determination.
If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the Joint Personnel Adjudication System (JPAS) or a hard copy VAR directly from the contractor’s Security Representative. Although the contractor will take JPAS “Owning” role over the contractor employee, the Navy Command will take JPAS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee’s performance under the contract.
· BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR CONTRACTORS ASSIGNED TO OR PERFORMING NON-SENSITIVE DUTIES Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc. ...) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements:
· Must be either a US citizen or a US permanent resident with a minimum of 3 years legal residency in the United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DoD instruction) and
· Must have a favorably completed National Agency Check with Written Inquiries (NACI) or T1 investigation equivalent including a FBI fingerprint check prior to installation access.
To be considered for a favorable trustworthiness determination, the Contractor’s Security Representative must submit for all employees each of the following:
· SF-85 Questionnaire for Non-Sensitive Positions
· Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)
· Original Signed Release Statements
The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or T1 equivalent investigation, or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM
Failure to provide the required documentation at least 30 days prior to the individual’s start date may result in delaying the individual’s start date.
* Consult with your Command Security Manager and Information Assurance Manager for local policy when IT-III (non-sensitive) access is required for non-US citizens outside the United States.
File details come from the government source that posted it.