DRAFT_IDIQ__Base_PWS_Platform_Mission_Equipment_Software_Branch_(PMESB)_06_Feb_2017.doc

Performance Work Statement (PWS)

For Software Engineering Center (SEC) Platform Mission Software Equipment Branch (PMESB)

System and Software Support

Solicitation Number: W56JSR-17-R-0005

06 February 2017 Table of Contents

1Performance Work Statement (PWS)

1Solicitation Number: W56JSR-17-R-0005

41.0 Scope

41.1 Background

41.1.1 Organization

41.1.2 Mission Areas

41.1.2.1 Post Production/Post Deployment Software Support

51.1.2.2 System/Software Engineering and Integration

51.1.2.3 MIL-STD-1553

61.2 Vision Statement and Objectives

61.3 Contract Type

61.4 Order Types

61.5 Period of Performance

71.6 Place of Performance

71.6.1 Onsite (Government Facility)

71.6.2 Offsite (Contractor Facility)

71.6.3 Supported Systems

72.0 Applicable Documents (For reference only)

7Reference Websites

8Reference Documents

93.0 Requirements

93.1 General

103.1.1 Materials, Equipment, and Facilities

103.1.1.1 Government Furnished Material and Equipment (GFM) (GFE)

103.1.1.2 Contractor- Acquired/Lease

113.1.1.3 Accountability

113.1.1.4 Laboratories

113.1.2 Security

123.1.3 Task Orders

123.1.3.1 Task Order Performance Work Statements

123.1.3.2 RTEP Response Time

133.1.3.3 Government Support

133.1.4 Phase In and Phase Out

143.1.5 Travel

153.1.6 Personnel Qualifications

153.1.6.1 Domain Knowledge

163.1.6.2 Technical Skills

163.1.6.3 Work Hours

163.1.6.4 Contractor Manpower Reporting (CMR)

173.1.6.5 Contractor Mandatory Training

183.1.6.6 Employment of Foreign Nationals

183.2 Performance

193.2.1 Contract Management

193.2.2 System(s) Engineer Support

203.2.3 Software Engineer Support

223.2.4 Post Deployment and Post Production (PPSS/PDSS) support services

244.0 Quality Assurance Surveillance Plan (QASP)

255.0 Deliverables

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 Appendix C 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 today’s 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 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 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 requirement’s 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 PMESB’s 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 today’s Army readiness and tomorrow’s 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 Contract Type

The contract type shall be a single award, Indefinite Delivery Indefinite Quantity (IDIQ) contract.

1.4 Order Types

Task order award types may include any of the contract types identified within Federal Acquisition Regulation (FAR) Part 16. Subsequently, all task orders shall be placed in accordance with the procedures outlined in FAR Subpart 16.505 entitled Ordering.

1.5 Period of Performance

The IDIQ period of performance shall be for a total period of 60 months from the date of award. All Task Orders periods of performance shall be IAW DFARS clause 252.216-7006.

1.6 Place of Performance

1.6.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.

1.6.2 Offsite (Contractor Facility)

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.6.3 Supported Systems

Appendix C 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 PWS Attachment 1

SEC SOP E-09 22 April 2012 PWS Attachment 2

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

PWS Attachment 3

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

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 User’s 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). Appendix D 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 Materials, Equipment, and Facilities

3.1.1.1 Government Furnished Material and Equipment (GFM) (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 Contractor’s responsibility to replace or repair the equipment to the Government’s 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 PCO’s sole discretion.

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 may be required to access Communications Security (COMSEC) information, Sensitive Compartmented Information (SCI) and NonSCI Intelligence information, North American Treaty Organization (NATO), Foreign Government Information and For Official Use Only (FOUO) information. The contractor may also require access to Security/Program Classification Guide(s) (SCG) and the SIPRNET, Joint Worldwide Intelligence Communications System (JWICS), NIPRNET and National Security Agency Network (NSANET) may be required. Software requirements are additional and will be identified on the Task Order DD Form 254, as required.

In performing this contract, the contractor may receive and generate classified material and fabricate/modify/store classified hardware. Software requirements are additional and will be identified on DD Form 254. The Contractor may have access to classified information overseas and will be authorized to use the Defense Technical Information Center (DTIC). A COMSEC account will be required, and there will be a TEMPEST requirement. Use of the Defense Courier Service is authorized. 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. All task orders shall outline all security requirements specific to individual task orders. 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.

3.1.3 Task Orders

Before the award of a Task Order, the designated PCO will issue a Request for Task Execution Plan (RTEP) to the Contractor. The Contractor shall only respond to RTEPs published by the appointed PCO. The RTEP does NOT constitute an authorization to start work, the Government is not required to approve a task execution plan, nor award a Task Order, but may do so at their sole discretion.

3.1.3.1 Task Order Performance Work Statements

It is the Government’s intent to issue RTEPs reflecting a performance-based contracting approach. That is, the Government intends on specifying requirements regarding performance objectives, and the Contractor will propose “how to” best satisfy those objectives.

3.1.3.2 RTEP Response Time

The response time for the delivery of a task execution plan will be based on the nature and complexity of the requirements and will be identified in the RTEP. The Government reserves the right to limit task execution plans total page count. The following information may be required for each TEP:

Summary including:

· Task number

· Date submitted

· Contractor’s name

· Contractor task leader contact information

· All subcontractor(s) (as applicable)

· Proposed start and finish dates

· Proposed total cost with separate option or Contract Line Item Number (CLIN) pricing, as applicable

· Reference to any unique terms or conditions, or any requests to deviate from standard contract terms and conditions

· Deliverables and Schedules

· Complete description of the technical approach for satisfying task requirements with a start and completion date for all tasks and scheduled deliverables for each task.

3.1.3.3 Government Support

The Government PM 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 documentation to gain access to sensitive or “rights guarded” data.

3.1.4 Phase In and Phase Out

A transition period is scheduled for a sixty (60) day period immediately following the contract start date (phase-in) and a sixty (60) day before contract end date (phase-out) to allow for orderly contract transition. An initial meeting between the Government's Contracting Officer’s Representative 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/phase out period. As determined by the PCO and when required, subsequent meetings may be held.

Phase-In: During the phase-in period, personnel incoming will be permitted to observe the operations of the outgoing contractor and Government personnel. The incoming contractor shall ensure that its phase-in operations do not hinder or interfere with normal operations of the phase out contractor and do not result in loss of productivity. During the phase-in period, the outgoing contractor will transfer all work to the incoming contractor.

Phase-Out: Before the end of contract performance the contractor shall permit an incoming contractor to observe all operations under this contract. The Contractor shall remain responsible and liable for all obligations until the end of the period of performance for this and all task order contracts. The Contractor shall fully cooperate with an incoming Contractor and the Government.

Phase-Out Plan: The Contractor shall provide the Contracting Officer with a phase-out plan no later than 90 days before the contract end date, IAW CDRL Data Item F013, Phase Out Plan DI-MISC-80508B, PWS Appendix D. This plan shall detail disposition action for all furnishings, equipment, and documentation with moderate Government input, outlining the Contractor’s approach to fulfilling the requirements of this Contract and applying all relevant factors and information gathered throughout the performance of the contract.

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 Appendix E

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 Appendix E 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). 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 Appendix D. 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): Bachelor’s 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.

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.

Engineering Supervisor Senior / Lead (Critical position): Master’s 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.

Program Administrator Journeyman (Non-critical position): Associate’s 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.

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.

Software Configuration Management Specialist Journeyman (Non-critical position): Bachelor’s 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.

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.

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.

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.

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.

Software Engineer - Entry 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.

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.

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.

System Administrator Journeyman (Critical position): Bachelor’s 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.

System Engineer Journeyman (Non-critical position): Bachelor’s 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.

System Engineer Senior / Lead (Critical position): Bachelor’s 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.

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.

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. Must be able to define, document, analyze, perform, and interpret developmental tests for new and/or modified products or product components. Must be able to investigate and resolve operational problems in conjunction with other engineering and technical personnel.

Test Engineer Journeyman (Non-critical position): Bachelor Degree in Electronics Engineering or any other Scientific or Technical discipline and five years of relevant work experience. Must be able to define, document, analyze, perform, and interpret developmental tests for new and/or modified products or product components. Must be able to investigate and resolve operational problems in conjunction with other engineering and technical personnel.

3.1.6.1 Domain Knowledge

The contractor shall provide qualified personnel. The staff qualifications shall be demonstrated with successful performance activities associated with this PWS. The areas of expertise include, but are not limited to; Engineering knowledge and experience related to Aviation and Avionics Systems, Air Traffic Control; Command and Control (C2); and aircraft/LRU maintenance. Consequently, the Aviation and Avionics System experience shall relate to data bus network/interface MIL-STD-1553, ARINC 429, RS-232, RS-422, RS-423, and Ethernet

3.1.6.2 Technical Skills

The contractor shall provide qualified personnel who demonstrate via the successful performance of the tasks within this PWS, engineering and development capabilities with

· C# in .NET Runtime Environments

· Visual Basic 6

· C++

· Microsoft Access

· Software Product Line Methodology & Development

· Microsoft Server

· Microsoft Visio

Additionally, contractor personnel shall be proficient in the utilization of electronic and software tools including but not limited to Microsoft Office, Project, and SharePoint.

3.1.6.3 Work Hours

The contractor is responsible for conducting business, between the hours of 0800 and 1700 Monday thru Friday except for Federal holidays. When the Government facility is closed due to local or national emergencies, administrative closings or similar Government directed facility closings; contractor personnel who normally work in the closed Government facility are not responsible for conducting business. The Contractor shall not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is open for operations.

3.1.6.4 Contractor Manpower Reporting (CMR)

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor shall report ALL contractor manpower (including subcontractor manpower) required for the performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address https://cmra.army.mil/ The required information includes:

1. Contracting Office, Contracting Officer, Administrative Contracting Officer;

2. Contract Number;

3. Beginning and ending dates covered by reporting period;

4. Contractor name, address, phone number, email address, identity of contractor employee entering data;

5. Estimated direct labor hours (including sub-contractors);

6. Estimated direct labor dollars (including sub-contractors);

7. Total payments (including sub-contractors);

8. Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor, if different);

9. Estimated data collections cost;

10. Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information);

11. Locations where contractor and subcontractor perform the work (specified by zip code in the United States or nearest city, country when in an overseas location, using standardized nomenclature provided on website);

12. Presence of deployment or contingency contract language; and

13. Number of contractor and sub-contractor employees deployed in theater during this reporting period (by country).

As part of its submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending September 30 of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor's systems to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website. The Contractor shall NOT mark any data provided to the USG under this contract as proprietary; this includes records, files, memoranda, reports, listings, SOPs, plans, programs, studies, tests, property listings, etc., or any other data acquired or produced by the Contractor in support of this contract.

3.1.6.5 Mandatory Contractor Training

In discharging its responsibility under the contract, the Contractor shall only use fully trained, experienced, appropriately certified, and technically proficient personnel. Consistent with the Defense Federal Acquisition Regulation Supplement (DFARS) 252.239-7001, Information Assurance Contractor Training and Certification, the contractor shall ensure that the staff accessing information systems have the proper and current IA certification required to perform IA functions IAW DoD 8570.01-M, Information Assurance Workforce Improvement Program.

The Contractor shall meet the applicable IA certification requirements, including DoD-approved IA workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and appropriate operating system certification for IA technical positions as required by DoD 8570.01-M.

Upon request by the Government, the Contractor shall provide documentation supporting the IA certification status of personnel performing IA functions. Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing IA functions. The Army’s implementation of the above requirements for IA Training, Certification, and Workforce Management, are found in AR 25-2, Information Assurance, and the associated Army Best Business Practice for Information Assurance Training, 05-PR-M-0002.

The contractor shall complete all government mandated training requirements as determined by CECOM SEC PMESB Branch for contractor employees that occur during the period of performance for this contract. Contractors shall track Mandatory Training compliance using their resources and provide a report of status to the Government. Evidence of compliance shall be presented upon Government request.

3.1.6.6 Employment of Foreign Nationals

All contractor personnel, including subcontractors and consultants, must satisfy certain personnel security standards whether or not the information processed by the Automated Information System (AIS) on which they are working is classified. Contractors working with unclassified AIS documents will have their positions designated Automatic Data Processing (ADP) I, II or III by the Government. Foreign nationals should not be allowed to perform work on contracts that would allow them access to unclassified sensitive information, and they will not be employed in positions that meet the definition of ADP I or II unless specifically approved by HQ AMC. Definitions of ADP I, II and III are located in AR 380-67, Personnel Security Program paragraph 3-614.

3.2 Performance

The contractor is responsible for the performance of the requirements as identified below, to the extent those requirements are cited in any task order resulting from this contract.

3.2.1 Contract Management

The contractor shall provide the necessary program management services to include, but not limited to, administrative and clerical support, cost control, cost reporting, technical status reporting, program reviews, and other ancillary support such as quality assurance, and data management. The management services shall support all of the technical efforts of this contract and task orders. The Contractor shall perform project management activities utilizing industry best project management practices, for example, the PMBOK® Guide, while conducting the services contained within this PWS. These project management activities include all of the tasks required to assist SEC to initiate, plan, manage, control, close-out, and report on projects. The Contractor shall provide courses of action to SEC for established planning criteria to control, lead, organize, plan, maintain, and set performance standards for the tasks associated with this effort. The Contractor may participate in IPT and develop project plans, WBS, activity schedules, GANTT charts, and project status reports as required for the efficient execution and performance of awarded task orders under the contract. The contractor will provide actual cost reports, IAW CDRLs C001 and C002.

Contract Cost Containment: The contractor will utilize best practices and principles of cost management such as Cost as an Independent Variable (CAIV). Principles of Cost as an Independent Variable will be used to the maximum extent possible at the Task Order level in order to contain cost while meeting technical requirements.

Management and Cost Status Reviews: Program management reviews will be conducted at the Government's request. Management reviews may be held at either the Government facilities or a mutually agreed upon location, as specified during a request. These reviews do not relieve the contractor from its ongoing responsibility to promptly inform the Government of problematic issues that affect or may affect performance, cost, or schedule.

3.2.2 System(s) Engineer Support

The SEC PMESB is responsible for providing DoD system engineering support for a multitude of systems. These systems are in various stages of their life cycle. System engineering support is required in areas of; functional requirements; conception of operations; computer resource management; technical documentations; technical reviews; evaluation of test plans; system and integration testing; applicability studies; and analysis of common software.

The Contractor system(s) engineer support services shall support, (but is not limited to), the following areas:

· Prepare, update, and review system-level documents.

· Review and evaluate system specifications to ensure completeness and sustainability of system software.

· Review and evaluate software requirements to ensure traceability to system requirements.

· Perform validation of systems and mission application software for conformance to both Army and DoD IA requirements and software assurance requirements to support both certification and accreditation and Networthiness.

· Perform services to assure that government systems are compliant with Army and DoD policy, Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGS), and Army and DoD Best Business Practices (BBP).

· Perform certification and accreditation validation testing, interoperability testing and system-of-system cross-functional software engineering testing, as required.

3.2.3 Software Engineer Support

The SEC PMESB is responsible for providing software engineering support to a multitude of DoD agencies in support of a vast amount of software products. These software items are in various stages of their life cycle. Software engineering support is required in areas of; functional requirements; conception of operations; computer resource management; technical documentations; technical reviews; evaluation of test plans; system and integration testing; applicability studies; and analysis of standard software.

The Contractor system(s) engineer support services shall support, (but is not limited to), the following areas:

· Provide software engineering support and technical consultation to system developers to develop a software architecture and to assist in development and…