W56JSR17R0005-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

Cost Plus Fixed Fee

0001 2017MAY25

W56JSR

ACC-APG Division E (W56JSR)

6001 Combat Drive

APG, MD 21005-1846

MICHAEL SHERICK

EMAIL: MICHAEL.G.SHERICK.CIV@MAIL.MIL

W56JSR-17-R-0005

2017MAY09

X

X

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 27

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: MICHAEL SHERICK

Buyer Office Symbol/Telephone Number: CCAP CCE/(443)395-1069

Type of Contract 1: Cost Plus Fixed Fee

Type of Contract 2: Cost No Fee

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

1. This amendment 0001 of solicitation W56JSR-17-R-0005 is for the purpose of adding and deleting inadvertently omitted and included information.

2. Software Engineer Senior/Lead minimal qualifications are hereby added to PWS Section C 3.1.6 and are in full force and effect.

3. The BOE reference located in Section L.15 General Instructions are hereby deleted in their entirety.

4. No other changes are made. All other terms and conditions stay the same and are in full force and effect.

*** END OF NARRATIVE A0001 ***

2 27

W56JSR-17-R-0005 0001

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Performance Work Statement (PWS)

For

Software Engineering Center (SEC)

Platform Mission Software Equipment Branch (PMESB)

System and Software Support

1.0 Scope

The extent of this PWS is to provide software and system support services for the Platform Mission Equipment Software Branch (PMESB).

The support services include but are not limited to:

Provide support for Post Deployment and Post Production (PPSS/PDSS) activities for the Platform Mission Equipment Software Branch systems, including but not limited to systems described in Attachment 0004 System Description.

Provide system/software engineering and integration support for aviation systems, tactical Air Traffic Control, Position/Navigation/Terrain systems, and Command and Control systems.

Provide MIL-STD-1553 engineering, validation and testing, and system integration support.

1.1 Background

1.1.1 Organization

The Software Engineering Center (SEC), PMESB is responsible for providing primary system/software engineering support to aviation navigation, communications, ground support avionics, command and control, and tactical air traffic control systems during their development and integration into weapon systems. Also, SEC PMESB is the leading Army Tri-Service organization for MIL-STD-1553 engineering, validation and test, and system integration support.

1.1.2 Mission Areas

1.1.2.1 Post Production/Post Deployment Software Support

SEC PMESB is responsible for the Post Production/Post Deployment Software Support (PPSS/PDSS) of 13 avionics systems. This support is essential in maintaining readiness for todays modern aircraft. The software maintenance entails making changes to software, testing the changes, and releasing the software to the field promptly. SEC PMESB is also responsible for the configuration management of all associated software and documentation for each of these systems. The SEC PMESB provides PPSS/PDSS support to systems sponsored by the following organizations:

Support Systems Organization Sponsors

PEO IEWS, PdM Electro-Optical/Infrared (EO/IR)

PEO GCS, PM Heavy Brigade Combat Team (HBCT)

PEO IEWS, PdM Combat Terrain Information Systems (CTIS)

CECOM Logistics and Readiness Center (LRC) Airborne Battle Command Program Support Office (ABCPS)

SOSE&I/Direct Reporting Program Manager Position, Navigation, and Timing(PNT)

Navy Naval Air Systems Command (NAVAIR)

PEO Aviation, PdM Aviation Mission Equipment (AME)

U.S Coast Guard

PEO Aviation, PdM Air Traffic Control (ATC)

U.S. Marines

PEO Aviation, PD Aviation Network Mission Planning (ANMP)

U.S. Air Force

PEO Solider, PM Air Warrior (AW)

1.1.2.2 System/Software Engineering and Integration

The SEC PMESB is responsible for providing system/software engineering support for avionics systems throughout their life cycle. Upon development, the SEC PMESB is involved with the integration of avionics systems into weapon/aircraft systems, such as the Improved Cargo

3 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Helicopter (ICH), HH-60L (MEDEVAC), RC-12 Guardrail Common Sensor, OH-58D, AH-64A/D and SOA aircraft (MH-47E and MH-60L). Support includes requirements definition, analysis, design, and interface control working groups, technical interchange, test planning, and document generation/review, including the preparation or validation of MIL-STD-1553 Multiplex Interface Control Document (MICD) and

Software/Interface requirements documents.

1.1.2.3 MIL-STD-1553

SEC PMESB provides engineering experience and expertise on all aspects of MIL-STD-1553 matters, ranging from participating in the writing of MIL-STD-1553 requirements to providing avionics maintenance test systems. The Validation and Test Facility (VALFAC) is a test laboratory that provides independent MIL-STD-1553 Validation and Verification test services for DoD MIL-STD-1553 subsystems in accordance with Tri-Service test standards. VALFAC will enable US Army and other DoD components to continue ensuring Contractor

Furnished Equipment (CFE) and Government Furnished Equipment (GFE) meet the requirements of governing communications standards.

1.2 Vision Statement and Objectives

The SEC PMESBs vision is to be the recognized Center of Excellence (CoE) for providing software solutions and services within the Army

C4ISR community and across the DoD Enterprise. With software as the driving force and challenge behind todays Army readiness and tomorrows force transformation, SEC PMESB stands ready to assure that Team C4ISR, the Army, and the DoD community meet that challenge in support of the Warfighter. To that end, SEC PMESB intends for this acquisition to provide outstanding system and software engineering support with cost effectiveness while ensuring reliability, maintainability, interoperability, and configuration integrity.

The following service objectives include, (but are not limited to), the following:

Maintain mission continuity within a changing and dynamic environment.

Sustain a world-class workforce focused on current and future Warfighter requirements and organizational vision.

Be a provider of choice for software solutions and services for present and future customers.

Seize strategic opportunities while ensuring the SEC role as a software leader.

Maintain Army field readiness with PDSS and Post Production Software Support (PPSS).

Meet growing and changing software demand throughout the DoD.

1.3 Limitation of Cost Type Task Orders

All cost type task orders are hereby subject to the following limitations. The Contractor;

a. Shall not submit any billing or claim containing fee or profit based or computed on other direct cost (ODC) CLINs in the contract.

Fee/profit in any form on ODCs is unallowable.

b. All caps, ceiling, or limits negotiated and established throughout section B shall constitute the maximum allowable billing rate.

Thus, the contractor or subcontractors shall not submit billing or claim(s) based on rates in excess.

C. At the time of award all offerors indirect rates shall be agreed upon, identified here, and capped for future ordering needs.

1.4 Ordering Period

The base ordering period during which individual task orders may be awarded under this contract shall be from the effective date of basic contract award through 60 months after that. Orders may be placed unilaterally at the Government's discretion. Orders are considered issued IAW 252.216-7006.

1.5 Place of Performance

1.5.1 Onsite (Government Facility)

The performance of the requirements set forth within this PWS shall be conducted at the Communications-Electronics Command-Life Cycle

Management Command (CECOM-LCMC) SEC facility at Building 6006 Combat Drive, Aberdeen Proving Ground (APG), MD 21005. The contractor in support of this requirement shall utilize these facilities as the primary locations for management, system & software engineering, and software maintenance work. The Government will provide on-site Contractor personnel with adequate workspace and equipment/material (to include desks, chairs, cabinet space, and telephones), and access to printers, FAX machine, scanners and photocopiers at the Government facility where the work will be performed for contractor use on a rent-free basis IAW FAR 52.245-9, attachment 0010.

1.5.2 Offsite (Contractor Facility)

4 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Government laboratory shall be used to optimize productivity. Consequently, all contractor engineers are required to work onsite.

Subsequently, all other administrative performance may be executed offsite.

1.5.3 Supported Systems

Attachment 0004 depicts a representative list of systems that are currently supported by the PMSEB. The list is dynamic in nature and subject to change, systems may be added or deleted based upon technical, organizational, or other managerial considerations. Services supporting other functional areas may be added over time as business goals evolve, new systems are transitioned or as the mission changes.

2.0 Applicable Documents (For reference only)

The following documents and websites are referenced for the performance of this contract. The Government reserves the right to update relevant documents.

Reference Websites http://www.dtic.mil/dtic/ http://www.apd.army.mil/

Governing Documents:

Joint Travel Regulations (JTR) https://www.defensetravel.dod.mil/Docs/perdiem/JTR.pdf

AR 715-9, Operational Contract Support Planning, and Management http://www.apd.army.mil/pdffiles/r715_9.pdf

AR 25-1, Army Information Technology www.apd.army.mil/pdffiles/r25_1.pdf

AR 25-2, Information Assurance http://www.apd.army.mil/pdffiles/r25_2.pdf

AR 735-5, Property Accountability Policies http://www.apd.army.mil/pdffiles/r735_5.pdf

DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology http://www.dtic.mil/whs/directives/corres/pdf/851001_2014.pdf

CNSSI No 1253, Security Categorization, and Control Selection for National Security Systems https://www.cnss.gov/CNSS/issuances/Instructions.cfm (search for No 1253)

NIST 800-53 Rev 4, Security, and Privacy Controls for Federal Information Systems and Organizations http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf

05-PR-M-0002, Army Best Business Practice for Information Assurance Training https://atc.us.army.mil/iastar/docs/Training_BBP.pdf

DoD 8570.01-M, Information Assurance Workforce Improvement Program http://www.dtic.mil/whs/directives/corres/pdf/857001m.pdf

AR-380-67, Personnel Security Program www.apd.army.mil/pdffiles/r380_67.pdf

Reference Documents

CECOM Policy Memo No. 13-11 Information Technology (IT) Strategic Planning, Acquisition, and Accreditation Procedures

Attachment 0006

SEC SOP E-09 22 April 2012

Attachment 0007

5 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

IEWS-CM-202, IEWSD Configuration Management Process Description (CM PD) Document

Attachment 0008

CECOM Pamphlet 25-1 U.S. Army Communications- Electronics Command (CECOM) Standard Operating Procedures (SOP) for Information Technology

(IT) Acquisitions

Attachment 0009

SEC Lab Configuration Control Board (CCB) Configuration Baseline v1.0 August 2012

(To be provided upon award)

AR 73-1 Test and Evaluation Policy https://acc.dau.mil/adl/en-US/649679/file/71925/r73_1%5B1%5D.pdf

AS4111 Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Remote Terminals 1998-10-01 http://standards.sae.org/as4111

AS4112 Production Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Remote Terminals 1989-01-11 http://standards.sae.org/as4112

AS4113 Validation Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Controllers 1989-01-11 http://standards.sae.org/as4113

AS4114 Production Test Plan for the Time Division Command/Response Multiplex Data Bus Controllers 1989-01-11 http://standards.sae.org/as4114

AS4115 Test Plan for the Digital Time Division Command/Response Multiplex Data Bus System 1989-01-11 http://standards.sae.org/as4115

AS4116 Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Monitors 1990-09-10 http://standards.sae.org/as4116

AS4117 Test Plan for the Digital Time Division Command/Response Multiplex Data Bus Couplers, Terminators, and Data Bus Cables 1991-03-19 http://standards.sae.org/as4117

Department of the Army Pamphlet 738-751 Functional Users Manual for the Army Maintenance Management System-Aviation http://www.apd.army.mil/pdffiles/p738_751.pdf

3.0 Requirements

3.1 General

The primary objective of this PWS is to acquire systems and software engineering technical services to support the PMESB activities. It is important to note that the efforts of the contractor(s) are not independent efforts but rather a collaboration between PMESB and the contractor(s) in support of PMESB mission performance. The contractor(s) shall be required to provide Subject Matter Experts (SMEs) and personnel. The SMEs shall have a broad-based range of knowledge, skills, and abilities including but not limited to the following:

knowledgeable and skillful project management; professional and technical support; system and software requirements development and management; software development; software sustainment; software assurance and information assurance; and, administrative support.

Contractor personnel supporting the PWS requirements will need skills and knowledge in software engineering and specific functional areas (e.g., communications, intelligence fusion, avionics, Command and Control (C2), business applications, financial management, and logistics). Contract Line Item (CLIN) lists the Contract Data Requirements Lists (CDRLs) which are found in this PWS. These CDRLs identify overarching requirements. Detailed requirements and deliverables will be specified in separate Task Orders.

3.1.1 Equipment, and Facilities

3.1.1.1 Government Furnished Equipment (GFE)

Government furnished material and equipment may be provided in support of individual Task Orders. In such cases, the GFM and GFE provisions will be included in the corresponding Task Order. The Contractor shall be responsible for preventing damage to all GFM/GFE while moved, handled, disassembled, inspected, repaired, modified, reassembled, and stored. The Contractor shall be responsible for conducting all necessary examinations, inspections, maintenance, and tests. The Contractor shall be responsible for reporting all inspection results, maintenance actions, losses, and damage to the Government. If the Contractor loses or damages the equipment, it will be the Contractors responsibility to replace or repair the equipment to the Governments satisfaction at no additional cost to the

Government. GFM/GFE items, except consumables, shall be returned to the Government in good condition upon termination of the Task

Order. The determination of good condition will be made by the Procuring Contracting Officer (PCO) at the PCOs sole discretion.

6 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

3.1.1.2 Contractor- Acquired/Lease

The Contractor may be required to purchase hardware and software necessary to accomplish an individual Task Order. Any purchased material shall become the property of the Government upon completion of the Task Order. Software integrity shall be maintained by the

Contractor within the licensing agreement of the producer until such software is delivered to the Government, or otherwise disposed of

IAW Government direction. The Contractor shall provide three cost estimates to the PCO or designee for review and approval, before purchase or lease.

3.1.1.3 Accountability

Any loss or damage to GFM/GFE/Contractor Acquired Property (CAP) shall be reported to the PCO or designee within three (3) days of the discovery. A statement explaining the circumstances of the loss/damage shall be submitted on a DA Form 4697, Report of Survey. The

Contractor shall provide a quarterly status report of GFM/GFE IAW the CDRL, Data Item Description DI-MGMT-80269 Status of GFE Report.

3.1.1.4 Laboratories

The Contractor shall maintain, operate, enhance, and develop Laboratories for PMESB Systems. This task may include the tearing down, moving, and setting up of PMESB Laboratories and furniture. The Contractor shall assist the Government to prepare and execute all associated tasks required to obtain and maintain the PMESB System Laboratories Risk Management Framework (RMF) Authorization-To-Operate accreditation.

3.1.2 Security

Prime Contractor Security Requirements. Obtaining the requisite security clearances for all contractor personnel is SOLELY the responsibility of the Prime Contractor. The contractor will be required to have a SECRET facility clearance with NO safeguarding.

The contractor may be required to access Communications Security (COMSEC) information, and For Official Use Only (FOUO) information.

The contractor may also require access to Security/Program Classification Guide(s) (SCG), the SIPRNET, and the NIPRNET at government facilities. Software requirements are identified on the DD Form 254.

The performance of this contract will be APG, MD and other sites as designated by the Contracting Officer Representative (COR).

Administrative duties will not require a clearance but may require an investigation for IT duties. Security requirements shall be outlined within the Department of Defense Contract Security Classification Specification, DD254.

The Contractor shall provide adequate security to safeguard sensitive DoD and Army information. The security may include but is not limited to the control of unclassified information (CUI), such as DoD Freedom of Information Act (FOIA) Program information.

Contractor may serve as a courier. The individual couriers must have the security clearance commensurate with the level of the security classification of the material being carried. Contractor must have documentation to be a courier. The Courier must be briefed on their courier responsibilities.

3.1.3 Antiterrorism/Operations Security

3.1.3.1 Antiterrorism (AT): AT Level I Training. (When Identified in P&A and applicable Dos) Prior to execution of required government installation or facility visits, , all contractor employees, to include subcontractor employees, requiring access to government installations, facilities and controlled access areas shall complete AT Level I awareness training. 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 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://Jkodirect.jten.mil for CAC holders. Non-CAC holders may go to:

http://jko.jten.mil/courses/atl1/launch.html.

3.1.3.2 Access and general protection/security policy and procedures. This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area:

Contractor and all associated sub-contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security

Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity

Verification of Contractor 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.

3.1.3.3 AT Awareness Training for Contractor Personnel Traveling Overseas. US based contractor employees and associated sub-contractor employees shall receive government provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13.

Specific AOR training content is directed by the combatant commander with the unit ATO being the local point of contact. Such training

7 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

will be defined as a requirement in applicable P&A requests and resulting DOs. OCONUS AOR AT awareness training is available from the nearest DoD installation Security and Intelligence Office. US based contractor employees and associated sub-contractor employees will submit an Isolated Personnel Report (ISOPREP) prior to deployment, in accordance with AR 525-28, Personnel Recovery. The contractor is required to fill out the survey on NIPRNET at https://prmsglobal.prms.af.mil/prmsconv/Profile/Survey/start.aspx prior to deployment.

3.1.3.4 Army Training Certification Tracking System (ATCTS) registration for contractor employees who require access to government information systems: All contractor employees with access to a government info system must be registered in the ATCTS (Army Training

Certification Tracking System) at commencement of services, and must successfully complete the DOD Cybersecurity Awareness prior to access to the IS and then annually thereafter.

3.1.3.5 For cybersecurity/information technology (IT) training: All contractor employees and associated sub-contractor employees must complete the DoD Cybersecurity awareness training before issuance of network access and annually thereafter. All contractor employees working Cybersecurity/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 appointment to Cybersecurity/IT functions.

3.1.3.6 For cybersecurity/information technology (IT) certification: Per DoD 8570.01-M , DFARS 252.239.7001 and AR 25-2, the contractor employees supporting Cybersecurity/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.

3.1.3.7 iWATCH The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local 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 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR

NLT 30 calendar days after contract award.

http://www.myarmyonesource.com/familyprogramsandservices/iwatchprogram/default.aspx.

3.1.3.8 Operations Security (OPSEC)

a. For contracts that require a formal OPSEC program:

For contracts that involve sensitive/critical/classified information and require work at a contractor facility, the contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

b. For contracts that involve sensitive/critical/classified information and require work at a government facility, the contractor shall request the organizational OPSEC Plan within seven (7) days of contract award. The OPSEC Plan will include the government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how it shall be protected.

c. For contracts that require OPSEC Training:Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC

Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter. Level I

OPSEC training is available at the following website: http://cdse.edu/catalog/elearning/GS130.html (Duration: 45 minutes).

3.1.3.9 Personnel Security (PERSEC)

a. For Performance or Delivery in a Foreign Country. DFARS 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US. This clause applies to both contingencies and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractors compliance with combatant commander and subordinate task force commander policies and directives.

b. Per AR 381-12, Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a Counter-

Intelligence (CI) agent or other trainer as specified in 2-4b.

3.1.3.10 For contracts that require handling or access to classified information. 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); (2) any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

3.1.3.11 Government Support

The Government COR designated for each Task Order will provide the Contractor access to all available Government furnished information, facilities, material, equipment, services, etc. as required to accomplish each Task Order. The Contractor shall provide the necessary

8 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

documentation to gain access to sensitive or rights guarded data.

3.1.4 Phase-In and Phase-Out

An initial meeting between the Government Contracting and incoming and outgoing Contractor Contract Managers shall be held to address

Phase-In and Phase-Out requirements, to maximize the effectiveness of the transition period. The meeting shall be held no later than seven (7) days into the Phase-In and Phase-Out period.

Phase-In Period: During the phase-in period, the incoming contractor shall observe and receive training from the outgoing contractor on all ongoing work projects being performed. The incoming contractor shall also attend any transition summit meetings scheduled by the outgoing contractor. Also during the Phase-In Period, the incoming contractor shall have 100 percent staff in place at the designated work places identified in IDIQ PWS section 1.5 and the level of effort identified at Task Order 0001 PWS section 3.2, ready to start full performance of work on day 61 of the effective date of Task Order 0001 period of performance. The Phase-In Period will be a total of 60 calendar days from issuance the effective date of the Task Order 0001 period of performance. During the Phase-In Period, the incoming contractor is not responsible for completion of task order requirements.

The incoming contractor shall assume full responsibility for all contract obligations no later 61 days from the effective date of Task

Order 0001 period of performance. Throughout the 60-day transition period, the incumbent contractor shall be responsible for all contract requirements.

Phase-Out: During the Phase-Out Period, the outgoing contractor shall permit key incoming contractor personnel to observe and become familiar with any and all operations under this contract. The outgoing contractor shall remain responsible and liable for the completion of all requirements of this contract until the final day of the Phase-Out Period. The outgoing contractor shall not defer any requirements for the purpose of avoiding responsibility. The outgoing contractor shall brief and train the incoming contractor personnel on all ongoing projects so they are fully capable of performing work on the first day of performance of the base period. The

Phase-Out Period will be a total of 60 calendar days from issuance of the notice to proceed by the Contracting Officer.

The outgoing contractor shall host a task order transition summit meeting with the Government and the incoming contractor to discuss and coordinate the transfer of work requirements. The transition summit meeting shall be held at the outgoing contractor's office nearest to APG, MD. The outgoing contractor shall provide the Contracting Officer with a Phase-Out plan no later than 90 calendar days prior to the end of the last contract period. This plan shall detail disposition action for all government furnished property and equipment, and provide status of all on-going projects outlining the contractor's approach to fulfill the requirements of the contract and its Task

Order(s) and applicable milestones during the last contract period and the 60 day Phase-Out period. The contractor shall prepare and deliver a Phase-Out Plan IAW CDRL F013 (DI-MISC-80508B).

3.1.5 Travel

The contractor shall be required to travel to other Government installations or to contractor facilities within CONUS to observe or conduct tests, ensure compatibility of configuration changes and other integration services, investigate and resolve network issues, and to furnish technical guidance and operational support as required. Trips and numbers and types of personnel will be limited to the minimum required to accomplish work requirements. The contractor will be responsible for arranging all contractor personnel travel at the lowest cost mode of transportation commensurate with mission requirements and sound traffic management principles and in accordance with the applicable C4ISR and local command policies as well at the Joint Travel Regulations (JTR) and AR 715-9. There will be no reimbursement for local travel within 50 miles in and around the place of performance.

A summary of anticipated travel is provided in Attachment 0004

Travel Arrangements: Air travel will be accomplished on regularly scheduled commercial flights in the most economical manner consistent with the successful accomplishment of the mission. Reimbursement for the cost of lodging and incidental expenses will be considered to be reasonable and allowable to the extent that costs submitted for reimbursement do not exceed the rates and amounts allowed by the JTR

(https://www.defensetravel.dod.mil/site/perdiem.cfm), as applies to civilian employees of the United States Government.

All CONUS travel shall be in accordance with the contractual requirements set forth within this PWS. All CONUS and extended CONUS travel details must be provided to the COR and approved by the Contracting Officer before the commencement of travel. The contractor shall perform duties such as Temporary duty (TDY). Locations may include CONUS sites listed in Attachment 0004 of this PWS.

Trips and numbers and types of personnel will be limited to the minimum required to accomplish work requirements. The contractor shall be responsible for arranging all contractor personnel travel at the lowest cost mode of transportation commensurate with mission requirements and sound traffic management principles. All CONUS travel will be on a cost-reimbursement basis.

3.1.6 Personnel Qualifications

The contractor shall employ only personnel who meet the minimum qualifications. The Contractor personnel shall be fully qualified and competent to perform all tasks specified. The Contractor shall ensure all staff id utilized in a manner that maximizes productivity and efficiency. For surveillance, Contractor personnel resumes, (in support of this Contract), are subject to verification, (by the COR).

9 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The COR resume(s) verification shall ensure all support personnel meets or exceed the category description(s), qualification(s), and minimum qualification(s) of this PWS.

There is a total of four critical labor categories, which must be maintained at all times. The essential labor categories are; senior lead engineering supervisor; senior lead software developer; journeyman system administrator; and senior lead system engineer. The

Contractor shall provide the Contracting Officer immediate notification of any critical labor category vacancies, and shall not replace any critical personnel absent the written, (Contracting Officer), approval.

Additionally, before deviating from any personnel changes, the contractor shall provide notification of all proposed changes with the submission of CDRL Data Item E001 entitled critical personnel change DI-MGMT-80269, PWS Attachment 0003. The Government may modify the contract to add or delete key personnel at the request of the contractor or Government. Critical positions shall be filled within thirty (30) calendars days of any vacancy. Non-critical positions shall be filled within forty-five (45) calendar days of any vacancy.

Minimum Personnel Qualifications

Budget Analysis Journeyman (Non-critical position): Bachelors Degree in Business or Accounting with a minimum of seven years of work experience. Three Additional years of applicable experience may be substituted for the degree. Years of experience shall be within the last 10 years of the effective date of basic IDIQ award.

Electronics Technician Intermediate (Non-critical position): Minimum of one year of work experience. Must be capable of constructing breadboard interface circuitry (digital, analog, and hybrid circuits), special cabling, etc. in support of system test bed/development facilities and for special system/software test fixtures. Must possess sufficient technical electronics knowledge and experience to perform above construction from design information furnished by project engineer. Years of experience shall be within the last 3 years of the effective date of basic IDIQ award.

Engineering Supervisor Senior / Lead (Critical position): Masters Degree in Computer Science, Electronics Engineering, or other engineering or technical discipline with a minimum of seven years of experience working in computer systems engineering and/or software development. Must be capable of planning, directing, and coordinating the activity of technical personnel involved in providing life cycle software engineering support of military computer software systems. Must have the ability to understand the technical requirements for software support and be able to develop and maintain realistic work plans, schedules, and controls to establish effective software support of both fielded software and support software of computer based systems. Must have technical expertise to review and evaluate the technical work performed by subordinates. Years of experience shall be within the last 3 years of the effective date of basic IDIQ award.

Program Administrator Journeyman (Non-critical position): Associates Degree in Business Management or related field as well as three years of relevant work experience. Must be able to perform numerous Program Management and Contract Management functions necessary to support administration of the contract. Functions include responsibility for the preparation of Task Execution Plans, budget estimates, travel requests, overtime requests, certificates of service, and contract status reports. Must be experienced in the administration and use of a purchasing system and related policies. Must be capable of establishing a competitive bidding system and assuring that purchasing from vendors is at the lowest possible cost consistent with quality and delivery requirements. Requires a thorough knowledge of company procedures as well as working knowledge of Federal Acquisition Regulations/Defense Federal Acquisition Regulations

(FARs/DFARS), including Cost Accounting Standards. Years of experience shall be within the last 3 years of the effective date of basic

IDIQ award.

Property Management Specialist Journeyman (Non-critical position): Two years of relevant work experience in property management. Must be able to maintain property records, and performs property inventory and property management functions. Must be capable of managing repair and relocation of office equipment and furniture. Knowledge of Army supply/property management policies and procedures is required. Years of experience shall be within the last 3 years of the effective date of basic IDIQ award.

Software Configuration Management Specialist Journeyman (Non-critical position): Bachelors Degree in Computer Science, Electronics

Engineering or other Engineering or Technical discipline and five years of work experience in Software Configuration Management. Must be able to write Configuration Management (CM) Plans and audit software change procedures, software development, software testing, and software documentation to verify compliance with software CM plans and procedures. Must be capable of participating in design reviews, configuration audits, and evaluations of software products to ensure proper identification, control, and status accounting of the software baseline for each system. Years of experience shall be within the last 7 years of the effective date of basic IDIQ award.

Software Developer Entry (Non-critical position): Bachelor degree in Computer Science, Computer Engineering and Software Engineering, and one year of work experience. Two additional year of applicable experience may be substituted for the degree. Must be able to assist in the design, development, and maintenance of software for a variety of engineering applications. Must be able to work with analysts to understand their analytic or interface requirements. Must be able to assist in developing tools and interfaces. Must be able to assist in design, development, and testing of operating systems-level software, compilers, and network distribution software applications. Must be able to assist in setting operational specifications and formulate and analyzing software requirements. Must be able to assist in design embedded systems software. Must be able to analyze user needs; develop and design software solutions. Years of experience shall be within the last 3 years of the effective date of basic IDIQ award.

10 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Software Developer Intermediate (Non-critical position): Bachelor degree in Computer Science, Electronics Engineering or other

Engineering or Technical discipline and three years of work experience. Two additional years of applicable experience may be substituted for the degree. Must be able to design, develop, and maintain software for a variety of engineering applications. Must be able to work with analysts to understand their analytic or interface requirements. Must be able to develop tools and interfaces.

Design, develop, and test operating systems-level software, compilers, and network distribution software applications. Must be able to set operational specifications and formulate and analyze software requirements. Must be able to design embedded systems software.

Years of experience shall be within the last 5 years of the effective date of basic IDIQ award.

Software Developer Journeyman (Non-critical position): Bachelor degree in Computer Science, Electronics Engineering or other Engineering or Technical discipline and five years of work experience. Two additional years of applicable experience may be substituted for the degree. Must be able to design, develop, and maintain software for a variety of engineering applications. Must be able to work with analysts to understand their analytic or interface requirements. Must be able to develop tools and interfaces. Design, develop, and test operating systems-level software, compilers, and network distribution software applications. Must be able to set operational specifications and formulate and analyze software requirements. Must be able to design embedded systems software. Years of experience shall be within the last 7 years of the effective date of basic IDIQ award.

Software Developer Senior / Lead (Critical position): Bachelor degree in Computer Science, Electronics Engineering or other Engineering or Technical discipline and seven years of work experience. Two additional years of applicable experience may be substituted for the degree. Must be able to design, develop, and maintain software for a variety of engineering applications. Must be able to work with analysts to understand their analytic or interface requirements. Must be able to develop tools and interfaces. Design, develop, and test operating systems-level software, compilers, and network distribution software applications. Must be able to set operational specifications and formulate and analyze software requirements. Must be able to design embedded systems software. Years of experience shall be within the last 9 years of the effective date of basic IDIQ award.

Software Engineer Entry (Non-critical position): Bachelor degree in Computer Science, Electronics Engineering or other Engineering or

Technical discipline and three years of work experience. Must be able to provide functional and empirical analysis related to the design, development, and implementation of software systems, including, but not limited to application software, utility software, development software, and diagnostic software. Must be able to participate in the development of test strategies, devices, and systems.

Years of experience shall be within the last 5 years of the effective date of basic IDIQ award.

Software Engineer Intermediate (Non-critical position): Bachelor degree in Computer Science, Electronics Engineering or other

Engineering or Technical discipline and five years of work experience. Must be able to provide functional and empirical analysis related to the design, development, and implementation of software systems, including, but not limited to application software, utility software, development software, and diagnostic software. Must be able to participate in the development of test strategies, devices, and systems. Years of experience shall be within the last 7 years of the effective date of basic IDIQ award.

Software Engineer Journeyman (Non-critical position): Bachelor degree in Computer Science, Electronics Engineering or other Engineering or Technical discipline and seven years of work experience. Must be able to provide functional and empirical analysis related to the design, development, and implementation of software systems, including, but not limited to application software, utility software, development software, and diagnostic software. Must be able to participate in the development of test strategies, devices, and systems.

Must be able to solve engineering problems (or managing the solution of engineering problems) in the functional area to which assigned.

Years of experience shall be within the last 10 years of the effective date of basic IDIQ award.

Software Engineer Senioir Lead (Non-critical position): Bachelor degree in Computer Science, Electronics Engineering or other

Engineering or Technical discipline and nine years of work experience. Must be able to provide functional and empirical analysis related to the design, development, and implementation of software systems, including, but not limited to application software, utility software, development software, and diagnostic software. Must be able to participate in the development of test strategies, devices, and systems. Must be able to solve engineering problems (or managing the solution of engineering problems) in the functional area to which assigned. Years of experience shall be within the last 10 years of the effective date of basic IDIQ award.

System Administrator Journeyman (Critical position): Bachelors degree in Computer Science, or other Engineering or Technical discipline with at least three years of work experience. Two additional years of applicable experience with appropriate certifications may be substituted for the degree. Must have certifications that meet or exceed Army Information Assurance Technical Level II (IAT II) requirements. Must be capable of managing the servers, which typically involves installing, and upgrading the servers, as well as solving any kind of problems with the systems. Must provide the essential software support for the laptops, desktop personal computers, and printers, including the configuration of the hardware devices, testing new software and designing the structure of the network.

Must be capable of monitoring the system configuration, including the server event log. Must be capable of testing the operating system software, the networking software, and also the computer hardware. Must be capable of monitoring and developing the procedures for backups of the servers. Years of experience shall be within the last 5 years of the effective date of basic IDIQ award.

System Engineer Journeyman (Non-critical position): Bachelors Degree in Computer Science, Electronics Engineering or other Engineering or Technical discipline with seven years of work experience. Must be able to interact with users to translate their requirements into system, hardware, and software requirements and design. Must be able to solve engineering problems (or manage the solution of engineering problems) in the functional area to which assigned. Years of experience shall be within the last 8 years of the effective date of basic IDIQ award

11 27

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

System Engineer Senior / Lead (Critical position): Bachelors Degree in Computer Science, Electronics Engineering or other Engineering or

Technical discipline with 9 years of work experience. Must be able to interact with users to translate their requirements into system, hardware, and software requirements and design. Must be able to solve engineering problems (or manage the solution of engineering problems) in the functional area to which assigned. Years of experience shall be within the last 9 years of the effective date of basic

IDIQ award.

Technical Writer/Editor Intermediate (Non-critical position): Associated Degree in English, Communications or related field with two years of work experience. Must be able to write technical specifications, reports, brochures, and/or manuals for internal documentation, customer reference, or publications. Must be able to analyze technical literature available, writes descriptive copy, and verify documentation. Must be able to edit, write, and/or rewrite technical articles, publications, presentations, and other materials to communicate clearly and effectively on research findings, technical developments, and other information to a wide range of external audiences. Years of experience shall be within the last 4 years of the effective date of basic IDIQ award.

Test Engineer Intermediate (Non-critical position): Bachelor Degree in Electronics Engineering or any other Scientific or Technical discipline and two years of relevant work experience.