W15QKN18R0033-0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing items 8 and 15, and returning ____________ copies of the amendments: (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting And Appropriation Data (If required)

13. THIS ITEM ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: The Changes Set Forth In Item 14 Are Made In

The Contract/Order No. In Item 10A.

B. The Above Numbered Contract/Order Is Modified To Reflect The Administrative Changes (such as changes in paying office, appropriation data, etc.) Set

Forth In Item 14, Pursuant To The Authority of FAR 43.103(b).

C. This Supplemental Agreement Is Entered Into Pursuant To Authority Of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return _______________ copies to the Issuing Office.

14. Description Of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name And Title Of Signer (Type or print)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

By (Signature of person authorized to sign) (Signature of Contracting Officer)

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0001 2018FEB14

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

NICOLE THALMANN

EMAIL: NICOLE.L.THALMANN.CIV@MAIL.MIL

W15QKN-18-R-0033

2018FEB06

X

X 2018MAR08 04:00pm

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 25

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: NICOLE THALMANN

Buyer Office Symbol/Telephone Number: ACC-NJ-JA/(973)724-8200

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of this amendment is to:

1) Answer questions posed by potential offerors

2) Update sections of the solicitation as indicated

3) Add clause 52.219-9 (ALT II)

4) Update Attachment 0001 Pricing Schedule for Labor Categories

5) Update the Performance Work Statements for Sample Tasks in Functional Area 2 and Functional Area 4

If contractors have already received all of the solicitation attachments they should immediately request the updated Attachments 0001, 0007 and 0009 from "mailto:Nicole.l.thalmann.civ@mail.mil " . (Functional Area 3 attachments will be updated in the next amendment.)

1. Each paragraph for Subfactor 2 (Availability/Expertise of Proper Personnel to Perform the Work) for each subfactor states that

Offerors shall submit resumes for proposed personnel to be assigned to work on the resulting contract". As the scope, statement of work, and period of performance is undefined for any future task that may be awarded under the resulting contract (other than the sample task), it is not possible to know which personnel or specific labor categories might be assigned to a future task. Therefore, is it the governments intention that the resumes requested in these paragraphs be representative of the skills and quality of personnel who may be provided to work on any resulting task, or is it the governments intention that the resumes are specifically for those who will work on the sample task order submitted with this proposal?

ANSWER: Each section referenced says: "For the purposes of this solicitation, the government considers ONLY THE LABOR CATEGORIES DENOTED

WITH ASTERICKS, YELLOW HIGHLIGHTS AND UNDERLINES in Attachment 0011 key for the Technical Factor." So resumes should be submitted for those labor categories for each functional area contractors are submitting a proposal for.

2. As no Section D is found in the solicitation please clarify the reference to: D.3 in paragraph L.2.2 b; D.4.4.5 in paragraph L.4.3.8;

D.4.4.9.1 and D.4.4.10 in paragraph L.4.3.9.2.

ANSWER: Each reference in Section L to a paragraph D should actually be a paragraph L. Solicitation has been updated to reflect the proper references.

3. Section L.3.3.1 instructs that the font used shall not be less than 12 point and font type shall be Times New Roman or Arial. Given the page count restrictions for Volume II: Past Performance and Volume III: Small Business Participation, will a smaller font size (such as 10 point) be acceptable for use in tables/graphics?

Will the Government permit Offerors to use a 10pt Arial Narrow font for graphics and tables?

ANSWER: Yes. L.3.3.1 has been updated

4. In Section L.4, the Government instructs Offerors to place the appropriate PWS number at the beginning of the discussion text. Please clarify whether including the PWS number in the section title would also be acceptable.

ANSWER: Yes. PWS numbers in the section title would be acceptable.

5. L.4.1.1.2 Subfactor 1, this paragraph states that Each offeror and major subcontractor and affiliate under shall describe and demonstrate with detailed examples, how its software development capability was applied successfully to systems/projects similar to this functional Subfactor 2 area. Please clarify that that this should refer to Subfactor 1 rather than Subfactor 2.

ANSWER: The solicitation has been updated to remove the words 'Subfactor 2' at L.4.1.1.2.

6. The Small Business Participation Table and Additional Guidance for particular Business Categories (L.4.3.6.2) include reference to

Historically Black Colleges and Universities (HBCU) and Minority Institutions (MI). FAR clause 52.219-9 was revised on October 14, 2014 to change the reporting requirements for Historically Black Colleges and Universities and Minority Institutions (HBCU/MI) to apply only to NASA contracts.

ANSWER: This is correct. L.4.3.6.2 (d) has been updated.

2 25

W15QKN-18-R-0033 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

7. Given the prior numbering and labeling of factors, please confirm that Volume IV, Price, should be Factor No. 4 and not Factor No. 3 as stated.

ANSWER: L.4.4 Volume IV, Price, has been updated to Factor 4.

8. In Functional Area 4 Sample task section 3.4.1.1 - Location shall be no less than 10 miles from Picatinny Arsenal; Question: Does the contractor need to have a facility prior to award or will the government allow the contractor to secure a facility at the time of

Task Order award?

ANSWER: The contractor does not need to have a facility prior to award but needs to provide evidence that they have a targeted facility address or potential lease agreement identified in their proposal.

9. Per section L4.4.3, page 71 does the government require the prime and subcontractor to provide a cost narrative?

ANSWER: No

10. Attachment 0001 provides LOE for only 15 labor categories in each functional area for each year. Do the Government want the loaded rates for remaining labor categories as well?

ANSWER: Yes. We need loaded labor rates for all labor categories.

11. Attachment 0001 for loaded rates. Are we allowed to add additional columns and/Rows if we have more than one subcontractors?

ANSWER: No. Paragraph L.4.4.3 has been updated. We do not require each individual subcontractor's loaded labor rates. Instead, we require one weighted average fully burdened labor rate for subcontractors.

12. Will resumes and evidence of availability (such as Letters of Commitment) for proposed Task Order personnel be counted toward the

Subfactor 3 Page Limit considering it is 10 pages?

ANSWER: Resumes will be part of the overall proposal submission as Subfactor 2. As part of the sample task proposal (Subfactor 3), we suggest that in order to keep the page limit to 10 pages, offerors clearly reference which personnel in Subfactor 2 would be utilized in which labor category for that task.

13. Attachment 0001 only provides hours for 15 of the 29 Labor Categories. Do you intend to make an evaluation solely based on the hours for these labor categories?

ANSWER: Yes. The price analysis will be completed solely based on labor categories that have associated hours in Attachment 0001.

However, contractors are required to provide fully burdened labor rates for ALL categories, so that they may be included in the base award in case those categories will be utilized in the contractor's price proposals for future tasks.

14. We have noticed that all 4 Functional Area sample task labor categories and hours are the same. Based on the significantly different scope of the four functional areas sample tasks, please clarify and correct the government estimated labor categories and labor hours per each sample task.

ANSWER: The Government does not intend to update the labor categories in the Functional Areas that have associated hours. The hours indicated in Attachment 0001 are not necessarily associated with the sample tasks provided. Contractors should propose hours and rates for each task separate from Attachment 0001. Contractors shall propose rates for all labor categories on Attachment 0001 for the base contract and the price evaluation will take place on the labor categories indicated with hours. Rates for all labor categories will be incorporated on any base contract that is awarded.

15. In the PWS section 3.8.4.4.1 - The contractor shall support and maintain the armament SEC biometrics lab access control system infrastructure. Will the government please identify the types of biometrics systems presently being supported and the vendor name?

ANSWER: PWS section 3.8.4.4.1. updated to read The contractor shall support and maintain the Armament SEC iris scan biometric lab access control system and infrastructure

16. In this functional area for infrastructure support does the government require research and development of new biometric systems or just maintaining the lab access control system?

ANSWER: There will be no research and development of new biometric systems, only maintaining the lab access control system.

3 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

17. Is there a final due date for solicitation questions?

ANSWER: Yes, no questions will be accepted after COB on February 23, 2018.

18. When does the Government anticipate providing answers to questions?

ANSWER: Questions will be provided via amendments no less than weekly from now until February 28, 2018.

19. Section L.2. states: "Each proposal shall include ALL of the following: Part I -Technical Factor, Part II Past Performance Factor, Part III - Small Business Participation Factor, and Part IV Price Factor."

Section L.3 uses "Volume I, Volume II, etc." Please clarify if each proposal volume is to be identified as a "Part" or a "Volume."

ANSWER: Section L.2 has been updated to change "Part" to "Volume"

20. Is the 25 page limit for Volume I: Technical Factor exclusive or inclusive of the page limits for Subfactors 2 and 3?

ANSWER: 25 Pages for Subfactor 1 only.

21. The RFP does not stipulate a file name convention for the proposal volumes/files. Are Offerors free to choose their own naming convention (i.e. "Offeror.VolumeI.pdf")?

ANSWER: The Government will allow contractors to name as they see fit, provided each Volume is separate and referenced in the title.

22. The page limitations identified for Volume I, Technical Subfactor are further broken down to identify page limitations for each subfactor. How does the government want Offerors to define those page sections? Shall each Subsection start with Page 1 or shall the

Page numbering be continuous through Volume I?

ANSWER: The page limitation for Subfactor 1 is 25 pages. The page limitation for Subfactor 2 is a maximum of 2 pages per labor category.

The page limitation for Subfactor 2 is 10 pages. The Government will allow contractors to separate as they deem appropriate.

23. Is an acronym list required?

ANSWER: No. But, if it is necessary to explain acronyms specific to your company or practices, please include one.

24. Is it acceptable for the offeror to provide graphics/illustrations/pictures/tables in landscape format?

ANSWER: Yes, as long as it is included in page limitations.

25. Please confirm that Attachment 11 is the document that provides the Labor Categories and personnel requirements, to include 10 key personnel.

ANSWER: Yes, the Key Personnel are highlighted in Attachment 0011.

26. Attachment 11 does not provide breakdown by Functional Area (FA). Please confirm that the 10 Key Personnel labor categories are the same for each FA and each Sample Task.

ANSWER: Yes, the Key Personnel are the same for each Functional Area.

27. The Solicitation requires Offerors to develop a Work Breakdown Structure (WBS) for each of the Functional Area (FA) Sample Tasks to show how an Offeror intends to organize and perform the work effort. The Government provides its estimated hours for each of the FA

Sample Tasks by year in Attachment 1 Pricing Schedule. Those Government estimated hours are the same for each of the FA Sample Tasks by year.

a) Considering the noticeable difference in tasks for each of the FA Sample Tasks why is the Government estimating the same number of hours by labor category for each of the FA Sample Tasks?

b) The hours by year for each of the FA Sample Tasks varies noticeably by year. What is the rationale for these jumps in hours when there is no indication in the Sample Tasks of an increase of required support?

c) Offerors are required to develop a WBS with the staffing estimated to perform each FA Sample Task. The estimated hours per labor category to perform the tasks are more than likely vary noticeable for the Governments estimated hours and labor category. Are the

Government estimated hours in Attachment 1 Pricing Schedule related in any way to what the Government actually believes is what is required to perform the tasks or are they strictly for evaluation purposes (as stated in the Executive Summary) and not what the

Government believes what is required to perform the tasks?

4 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

ANSWER: The labor hours are not for the sample tasks, necessarily, but the hours that the Government will be using to evaluate base contract awards. This answer is the same for question 27 a, b and c.

28. The government is asking that "Offerors shall submit a list of all recent government contracts" Will the Government accept

Commercial or United Nations past performance?

ANSWER: No, only Government Contracts need to be submitted.

29. Are Offerors to use the "Total Prime & Sub Extended Price" as the amount for each FA Sample Task in its calculation for the percentages anticipated to be subcontracted? If so, are Offerors to us the 2 years extended total price or for the first twelve (12) months only?

ANSWER: No. Your calculations for small business participation should be for overall contract award and not based on any functional area tasks. An offeror's total evaluated price would be computed by adding each of the 15 labor categories that have hours listed x the hourly rate for each Functional Area Separately per year. Then each year is added up to get the contract value. Then that amount is the total evaluated price for that Functional Area. Your subcontracting participation should indicate dollars and percentage of that total evaluated price.

30. The contract labor hours for each labor category provided as an attachment in Section J, Attachment 0001, of this contract are provided for contract award evaluation purposes and are based on expected hourly requirements for each labor category.

a) Are the Government estimated hours for each FA Sample Task for each year in Attachment 1 Pricing Schedule what the Government considers what is required to perform the tasks?

b) In one instance in particular, FA 1 Sample Task PWS states that one position for 3.2.2 states that The contractor shall provide a full time person yet the Government estimate does not show the hours for a full time position.

ANSWER: a) No, they are being used for evaluation purposes. b) The hours for a full time person is entirely up to the contractor to propose. The Government does not intend to direct the contractor as to number of hours needed to complete a task.

31. Please confirm that Offerors are to insert their fully burdened labor rates in the Prime Contractor Hourly Rate or Subcontractor 1

Hourly Rate columns for each labor category even if there are no estimated hours being proposed.

ANSWER: Yes. Every labor category must be proposed whether or not there are hours associated with it in Attachment 0001. Cost proposals for Functional Area tasks (Subfactor 3) should be submitted as entirely separate cost proposals with Volume IV for each Functional Area.

32. The Sample Tasks state that the periods of performance for this effort shall be twelve (12) months from the date of task award, with the option to add an additional year of service. Please confirm that Offerors are only to price the first and second years of Attachment

1 Pricing Schedule.

ANSWER: Offerors are to propose total price for each functional area sample task for two years (base plus option) for those functional areas they are interested in. However, the spreadsheet Attachment 0001 is for the base contract award and labor rates need to be proposed for the entire 5 years.

33. Even though the period of performance for the Sample Tasks is a two year period (one of them being an option), are Offerors to insert their out year rates for each of the labor categories even though Offerors are not to include any hours of support past the second year?

ANSWER: See above. The answer is yes, Attachment 0001 is for the base contract award.

34. The labor categories Engineering Technician I & Engineering Technician II in column A rows 13 & 14 are duplicated in rows 19 & 20.

There are also Total Government Estimated Hours assigned to both Engineering Technician II positions. Please clarify what the difference is between the two duplicated categories and associated hours?

ANSWER: The duplicated categories were added as a mistake. Attachment 0001 has been updated.

35. This Attachment has labor categories IS Security Manager & Data Security Analyst, Sr. and their associated qualifications and yet are not included in Attachment 1 Pricing Schedule. Does the Government intend to amend Attachment 1 to include these labor categories?

ANSWER: Attachment 0001 has been updated to include IS Security Manager and Data Security Analyst, Sr. Please request the attachment if you have already received a copy.

*** END OF NARRATIVE A0003 ***

5 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

6 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Performance Work Statement For Armament Software Engineering Center, Software Engineering Services

1.0 BACKGROUND. The Armament Software Engineering Center (Armament SEC) within the Armament Research, Development and Engineering

Center (ARDEC) structure of the Weapons and Software Engineering Center (WSEC) provides Program Executive Offices (PEOs), Program

Managers (PMs) and other internal and external customers with software engineering and acquisition support throughout the lifecycle of their systems. This life cycle support includes supporting the system throughout the development process and maintaining it following transition to Government control. To accomplish the mission, the Armament SEC requires contractor support to assist in providing high quality services throughout the organization for software engineering, acquisition, process improvement, configuration management, infrastructure, advanced technologies, fielding, and sustainment.

1.1. SCOPE: The US ARMY ARDEC, Picatinny NJ requires engineering support services in weapon system and information system domains: Chemical, Biological, Radiological, Nuclear and Explosives (CBRNE); Conventional Weapon Software Support; Remote

Weapon System Software; Aerial, Robotic, Autonomous Guidance, Navigation & Control System Software; Smart Munition Software;

Networked Munition Software; Embedded software; Military Automation Systems; Military Web and Database Applications; Mobile

Applications; Biometric and Forensics Software; Biometric System and Infrastructure support; Information Systems and

Infrastructure Support; Configuration Management (CM) and Library System Management (LSM); and Software Process Improvement

Support; From Artificial Intelligence (AI) Machine Learning of large-scale (big) data to Virtual/Augmented/Mixed Reality interfacing between man and machine for development of systems that provide various levels of alternate reality. The services required are organized into functional areas. Contractors are expected to respond with proposals in one or more of these functional areas.

2.0 APPLICABLE DOCUMENTS

2.1. CMMI-SE/SW/SS V 1.3 or latest-Capability Maturity Model Integration Training.

2.2. ATS SCG Army Tactical Automated Information Systems Security Classification Guide (SCG), September 2014.

2.3. Stryker SCG Stryker Family of Vehicles Security Classification Guide (SCG), 18 May 2009

2.4. Army Regulation 200-1

2.5. Army Directive 2014-05

2.6. National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (Army

Directive 2014-05/AR 190-13)

2.7. Army Regulation 381-12

2.8. DoDD 8570.01

2.9. DoDD 8570.01-M

2.10. Army Regulation 25-2

2.11. Army Regulation 25-1

2.12. National Industrial Security Program Operating Manual (DoD 5220.22-M)

2.13. DoDD Directive 5230.25

2.14. Army Regulation 530-1

3.0 PERFORMANCE REQUIREMENTS

3.1. The contractor shall provide engineering services to meet the requirements as specified in the task orders to be issued under this contract. The contractor shall not perform any requirement unless specifically assigned in a task order.

3.2. The contractor shall adhere to the Organizational Standard Processes (OSP) of the Armament SEC.

3.3. Location: Unless specifically expressed otherwise, the work to be performed under this contract shall be performed at the

Armament Software Engineering Center, Picatinny Arsenal, NJ. Individual task orders issued under this contract will identify specific work location(s) for the contractor.

3.4. Travel: The contractor shall perform travel as necessary for the individual task orders. Travel may include CONUS.

3.5. Incidental Government Furnished Equipment (GFE)/Government Furnished Material (GFM). The Government shall provide the work space, office, office supplies, computer equipment, telephone, and reproduction facilities for performance at Government locations. Additional GFE/GFM will be determined on a task order basis and will be identified in each task order PWS.

3.6. Data Rights. All reference material, documents, training support material, and other information obtained, produced, or developed by the contractor in support of this effort shall become the property of the Government and shall be delivered to the government at completion or termination of a task order or by Government request. The Government shall have unlimited and unrestricted right to use, modify, reproduce, release, perform, display or disclose all Computer Software, Computer Software

Documentation and technical data that is developed, updated, modified, included, or converted under this contract. The contractor shall not distribute or use the information and data without the express and specific written approval of the

Picatinny Arsenal Public Affairs Office (Form 3002, found in section J).

3.7. Environmental

3.7.1. The contractor shall adhere to all local, county, state, Army and federal policies, directives, executive orders and regulations required including, but not limited to 32 CFR Part 651, AR 200-1 (Environmental Protection and

Enhancement), 40 CFR Code of Federal Regulations, and Picatinny Arsenal local policies/regulations in order to maintain environmental compliance for the duration of the contract. Local policies that must be adhered to include the Picatinny

Environmental Bulletin and the Installation Environmental Policy. These documents can be found on the Picatinny

Environmental Management System website (http s://picac2w5.pica.army.mil/pems) or can be obtained from the contracting officer representative (COR).

3.7.2. The contractor shall be responsible to identify, obtain, and adhere to any required local, state, and federal permits/notifications/certifications/licenses prior to beginning work. The permit applications/submittals/plans shall be made available to the Picatinny Environmental Affairs Division (EAD) for review along with the final permit at the time

7 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

of issuance.

3.7.3. All work performed at Picatinny Arsenal shall obtain specific approval from the EAD and be placed into PEMS projects for the following actions or activities:

a. All fossil-fuel burning equipment brought onto the installation, including generators, stationary engines, etc.

b. The generation of hazardous waste.

c. Work requiring digging, drilling, and movement of soils.

d. Vegetation disturbances, involving any size tree felling or pruning, which is mostly limited to occur between the months of November 16 through March 31.

e. Vegetation disturbances, involving any size shrubs, heavy vines, or thick herbaceous cover, which is mostly limited to occur between the months of August 16 through April 14.

3.7.4. The contractor shall comply with all Affirmative and Green Procurement policies and procedures when ordering materials. Picatinnys Green Procurement Plan is located at https ://picac2w5.pica.army.mil/pems/docs/GPProcedures.pdf or can be obtained from the COR.

3.7.5. The contractor shall report immediately any spills of chemicals (including oils, paints, etc.) to the Picatinny

Arsenal Police Department at 911. Immediately report any noncompliance with applicable Federal, State or Local environmental laws, Army or installation environmental regulations or policies to the COR and EAD.

3.7.6. The contractor shall submit to potential Federal, State, Army and installation work site environmental regulatory inspections and/or investigations into noncompliance, and fully cooperate with such inspections/investigations by providing the appropriate records and documentation. Contractor shall when given a verbal and/or written notice of environmental noncompliance or nonconformance by the COR, take immediate corrective action.

3.8. TECHNICAL REQUIREMENTS

3.8.1. The contractor shall provide engineering support services in one or more of the following weapon system and information system domains: Chemical, Biological, Radiological, Nuclear and Explosives (CBRNE); Conventional Weapon

Software Support; Remote Weapon System Software; Aerial, Robotic, Autonomous Guidance, Navigation & Control System

Software; Smart Munition Software; Networked Munition Software; Embedded software; Military Automation Systems; Military

Web and Database Applications; Mobile Applications; Biometric and Forensics Software; Biometric System and Infrastructure support; Information Systems and Infrastructure Support; Configuration Management (CM) and Library System Management

(LSM); Software Process Improvement Support; Artificial Intelligence (AI); Machine Learning of large-scale (big) data;

Virtual/Augmented/Mixed Reality interfacing between man and machine for development of systems that provide various levels of alternate reality.

3.8.2. The contractor shall provide knowledge and expertise in various software engineering disciplines, including embedded (PICs, ASICs, FPGAs, microprocessors, controllers, DSPs, PISCs), platform based SW Engineering (i.e. PC, Laptop, Handheld, Tablet), Graphical User Interface Development, Real-Time Operating Systems (RTOS), closed loop servo controlled systems, real-time software development, safety critical software development, service-oriented (web services) architectures, web-based applications, artificial intelligence fields such as machine learning and deep learning, and cybersecurity software development.

3.8.3. The servicing contractor(s) shall provide all necessary personnel, supervision, and management to fully support these efforts within the Performance Work Statement (PWS). Specific PWS requirements will be included in the individual task order issued as appropriate and will be written in a performance-based PWS format.

3.8.4. The services required are organized into four (4) functional areas. The contractor shall provide a response in their proposals in one or more of the functional areas:

3.8.4.1. Functional Area 1: Software Development

The contractor shall provide software development activities to include software project planning and management, software cost estimation, requirements development and management, architecture design, software development, engineering verification & validation, engineering test, software configuration management, and software release and fielding, as they relate to engineering domains identified in section 3.8.1.

3.8.4.2. Functional Area 2: Software Sustainment

The contractor shall perform software sustainment engineering to provide post deployment / production support to include analyzing software requirements, software development to maintain operational capability, and software maintenance on existing systems as well as establishing and/or maintaining software support environments/labs.

3.8.4.3. Functional Area 3: Software Process Assurance

The contractor shall provide support for software process assurance to the Armament SEC projects to assure that the process requirements are being implemented using the principles of Capability Maturity Model Integration (CMMI), as per CMMI-

SE/SW/SS V 1.3 or later.

3.8.4.3.1. The contractor shall be able to plan, establish and maintain software technical data repository and software configuration management services for all supported software intensive systems.

3.8.4.3.2. The contractor shall be capable of developing, promulgating and training software engineering processes improvement initiatives throughout the Armament SEC.

3.8.4.4. Functional Area 4: Armament SEC Infrastructure Support

The contractor shall support operations and maintain the infrastructure systems including Armament SEC facilities, laboratories and equipment.

3.8.4.4.1. The contractor shall support and maintain the Armament SEC iris scan biometric lab access control system and infrastructure.

3.8.4.4.2. The contractor shall provide support for maintaining mission servers, applying updates, 8 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

configuration changes, and performing routine data backups.

3.8.4.4.3. The contractor shall provide technical support for the inventory control system and infrastructure.

3.9 Contractor, to meet minimum ordering amount, shall participate in a Government scheduled kickoff meeting and supply meeting minutes in accordance with CDRL A003 (DI-ADMN-81505). Contractors who are awarded a sample task will not be required to submit this report.

4.0 SECURITY REQUIREMENTS

4.1. The highest classification for this effort is SECRET.

A DD254, Contract Security Classification Specification, will be required.

The contractor will be required to obtain and maintain a Facility Clearance from the Defense Security Service for the life of the CONTRACT. The contractor will only receive classified material at the actual performance location(s) as identified in block 8a of the DD254.

4.2. Personnel: Contractor personnel shall have the appropriate level of investigation and/or security clearance for each site of performance of work. The Contractor shall observe and comply with all security provisions in effect at each selected site.

Only U.S. Citizens are authorized to work on this contract. All contractor personnel that require access to classified information and/or material will be required to have a Secret clearance under this contract and must maintain the level of security clearance for the life of this contract. The contractor will notify the COR the same day as an employee receives notice that they will be released, have been fired, or have had their security clearance revoked or suspended.

4.3. Information Disclosure: A Certificate of Non-Disclosure shall be signed by all contractor employees working under this effort and returned to the COR prior to contract award. The contractor shall not release any information or data without the approval of the Government.

4.4. AT Level I Training. All contractor employees, including subcontractor employees, requiring access to Department of

Defense installations, facilities, or controlled access areas shall complete AT Level I awareness training within 45 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies and within 12 months prior to travel outside of the US, then annually thereafter. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR (or to the contracting officer, if a COR is not assigned) within 14 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at http ://jkodirect.jten.mil/ .

4.5. Access and General Protection/Security Policy and Procedures. All contractor employees, including subcontractor employees, shall comply with all installation and facility access and local security policies and procedures (provided by the Government representative), and security/emergency management exercises. The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or Security Office. Contractor workforce must comply with all personal identity verification requirements (CFR clause 52.204-9, Personal Identity Verification of Contract Personnel) as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection

Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes. During FPCONs Charlie and Delta, services/installation access may be discontinued/postponed due to higher threat. Services will resume when FPCON level and or threat is reduced to an acceptable level as determined by the Installation

Commander. Contractor personnel working on an installation are required to participate in the Installation Random Antiterrorism

Measures Program as directed. Contractors may be subject to and must comply with vehicle searches, wearing of ID badges, etc.

4.6. iWATCH (See Something, Say Something) Training. All contractor employees, including subcontractor employees, shall receive training and participate in the local iWATCH program (training standards provided by the requiring activity ATO). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 45 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies, and then annually thereafter. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR (or to the contracting officer, if a COR is not assigned) within 14 calendar days after completion of training by all employees and subcontractor personnel. Slides available to COR at https ://www.milsuite.mil/book/docs/DOC-284984.

4.7. For contractors requiring CAC. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army

Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled National Awareness Check With Inquiries (NACI) at the Office of Personnel Management.

4.8. For contractors that do not require CAC, but require access to a DoD facility or installation. Contractor and all associated subcontractor employees shall comply with adjudication standards and procedures using the National Crime Information

9 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (Army Directive 2014-05/AR 190-13);

applicable installation, facility and area commander installation and facility access and local security policies and procedures (provided by Government representative); or, at OCONUS locations, in accordance with status-of-forces agreements and other theater regulations.

4.9. Threat Awareness Reporting Program. Per AR 381-12, Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a counterintelligence (CI) agent or other trainer as specified in 2-4b. This training shall be completed within 12 months after contract start date or effective date of incorporation of this requirement into the contract, whichever applies, and then annually thereafter. The contractor shall submit documentation of completion for each affected contractor employee and subcontractor employee to the COR (or to the contracting officer, if a COR is not assigned) within 14 calendar days after completion of training by all employees and subcontractor personnel. Training can be executed by a local CI agent, online via the Army Learning Management System at http s://www.lms.army.mil (and search for TARP), or by contacting the 308th Military Intelligence Battalion at usarmy .pica.902-mi-grp.list.308th-picatinnyfo@mail.mil and 973-724-

5446.

4.10. Employees Who Require Access to Government Information Systems. All contractor employees, including subcontractor employees, with access to a government information system must be registered in the Army Training Certification Tracking System

(ATCTS) at commencement of services and must successfully complete the DoD Cyber Awareness training prior to access to the information system and then annually thereafter.

4.11. Contractor employees are required to have access to unclassified/sensitive AIS information. Each contractor employee is required to have a Personnel Security Investigation. Each contractor employee is required to complete a DD Form 398-2, DoD

National Agency Questionnaire (NAQ) and an FD258, Applicant Fingerprint Card, (obtained from the ARDEC Security Office, Bldg.

274, x2925), and upon completion of the forms, returned to the Security Office. A debriefing by the Security Office is a MUST upon completion of contract, upon separation of contractor employee for a 60-day period or more, or termination of a contractor

Employee.

4.12. IA/Information Technology (IT) Training. All contractor employees, including subcontractor employees, employees must complete the DoD Cyber awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within six months of employment.

4.13. IA/Information Technology (IT) certification. Per IA best business practices, DFARS 252.239-7001, Information Assurance

Contractor Training and Certification and AR 25-2, All contractor employees, including subcontractor employees, supporting

IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

4.14. Government Furnished Items. All contractor employees, including subcontractor employees, will return all issued U.S.

Government owned equipment which includes travel laptops, mobile devices, Common Access Cards, installation badges, and/or access passes to the COR when the contract is completed or when a contractor employee no longer requires access to the installation or facility.

4.15. Information Management Army Information Technology /IA. The Contractor shall be capable of accessing, handling, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the applicable standards of FOUO information. Controlled Unclassified Information (documents designated as FOR OFFICIAL USE ONLY and/or LIMITED DISTRIBUTION) shall be submitted by a controlled means using USPS mail, Safe Access File Exchange (SAFE) website and/or DoD Army approved encryption software as per AR 25-1.

4.16. For Contracts That Require Handling or Access to Classified Information. The contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified Confidential, Secret, or Top Secret and requires contractors to comply with (1) the Security Agreement (DD Form 441), including the National Industrial Security Program

Operating Manual (DoD 5220.22-M), and (2) any revisions to DoD 5220.22-M, notice of which has been furnished to the contractor.

4.17. Export Control Laws/International Traffic in Arms Regulation. Information Subject to Export Control Laws/International

Traffic in Arms Regulation (ITAR): Public Law 90-629, Arms Export Control Act, as amended (22 U.S.C 2751 et. Seq.) requires that all unclassified technical data with military application may not be exported lawfully without an approval, authorization, or license under EO 12470 or the Arms Export Control Act and that such data required an approval, authorization, or license for export under EO 12470 or Arms Export Control Act. For purposes of making this determination, the Militarily Critical

Technologies List (MCTL) shall be used as general guidance. All documents determined to contain export controlled technical data will be marked with the following notice: WARNING: - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., App. 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.

4.18. For Official Use Only Information (FOUO) and Controlled Unclassified Information (CUI): Contract personnel shall be capable of accessing, handling, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the

10 25

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

applicable standards of FOUO and CUI. DFARS Clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident

Reporting applies to this effort.

4.19. For Contracts That Require Development of an OPSEC Standing Operating Procedure/Plan. The contractor shall develop an

OPSEC Standing Operating Procedure (SOP)/Plan, in accordance with DI-MGMT-80934C, within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will specify the projects critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor will ensure that this individual becomes OPSEC Level II certified per AR 530-1. ARDEC OPSEC POC email: usarmy .pica.rdecom-ardec.mbx.ardec-opsec@mail.mil .

4.20. For Contracts That Require a Government Provided OPSEC Standing Operating Procedure/Plan. The contractor is subject to compliance with the ARDEC Operations Security Plan, per AR 530-1 (or DoDM 5205.02-M). This SOP/Plan will specify the government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it.

4.21. For Contracts That Require OPSEC Training. Per AR 530-1 (or DoDM 5205.02-M), new contractor employees, including subcontractor employees, must complete initial OPSEC training within 30 calendar days of reporting for duty and must also complete annual OPSEC awareness training as provided by the appropriately designated OPSEC level II trained OPSEC

Officer/Coordinator. The Contracting Officer Representative (COR) or Agreements Officer Representative (AOR) can request ARDEC

OPSEC training from ARDEC OPSEC POC e-mail: usarmy .pica.rdecom-ardec.mbx.ardec-opsec@mail.mil.

4.22. For Contracts that Involve the Public Release of Information: Per AR 530-1 (or DoDM 5205.02-M), an OPSEC review is required prior to all public releases. All government information intended for public release by a contractor will undergo a government OPSEC review prior to release.

4.23. Human Systems Integration (HSI). The contractor shall assess the Human System Integration risks associated with contractor-proposed design and redesign efforts that involve the development, design, modification, test & evaluation, and selection of systems, equipment, and alternative designs for hardware and software that affect the usability and functionality of the system and equipment with regard to operation, maintenance, and sustainment functions. The Human Systems Integration risk shall address risks to the seven domains of Army Human Systems Integration (see AR 602-2 for formal definitions) based on system's benefits and disadvantages regarding manpower (i.e., the quantity of operator, maintainer, and sustainment personnel needed throughout the expected life of the system), personnel (i.e., the skill levels, qualifications, aptitudes, and capabilities of the personnel expected to operate, maintain and sustain the system), training (i.e., the time and resources necessary for operators, maintainers, and sustainment personnel to attain proficiency with the system), Soldier Survivability, Human Factors Engineering, System Safety, and Health Hazards. The contractor shall evaluate trade-offs between the domains with respect to human-system reliability, total system performance, and the impact to life cycle costs associated with the seven domains (especially the potentially high cost drivers of Manpower, Personnel and Training). The contractor may choose

HFAC Data item Description (DIDs) to use as a guidance for the HSI efforts.

5.0 REPORTING:

5.1. Accidents and Incidents. The Contractor shall immediately report any major accident or incident, including fire, which results in any of the following: one or more disabling injuries, damage to Government property exceeding $10,000, disruption of program plans or production schedules, degradation of the safety of equipment under contract such that personal injury or property damage may be involved, or identifies a potential hazard which requires correction action (A001, DI-SAFT-81563).

5.2. Monthly Reports. The Contractor shall deliver monthly reports as specified for specific task orders issued under this contract (A002, DI-MGMT-80227, Tailored).

5.3. Final Technical Report. The Contractor shall deliver a final technical report as specified for specific task orders issued under this contract (A003, DI-ADMN-80447).

5.4. Contractor Administrative Space Report. The Contractor shall deliver the Contractor Administrative Space report for all personnel anticipated to occupy administrative space at Picatinny Arsenal (A004, DI-MGMT-81596, Tailored).

5.5. Additional contract reporting deliverables will be specified for specific task orders issued under this contract, and shall be detailed in the language of the corresponding task PWS.

5.6. PERIOD OF PERFORMANCE. The period of performance for the base contract is five (5) years. Task orders will be awarded for terms of 12 months or less but may include an option year to be evaluated at the time of task order award. The performance of the option shall start during an ordering period on the base.

5.7. Contracting Officers Representative (COR) and Alternate Contracting Officers Representative (ACOR).

5.7.1. COR: To be provided at contract/task award.

ACOR: To be provided at contract/task award for all…