IA02 A2SF PWS 20240325_Draft Watermark.pdf

PERFORMANCE WORK STATEMENT (PWS)

ACTIVE ARMY STRENGTH FORECASTER SYSTEM (A2SF) SUPPORT SERVICES

HEADQUARTERS, DEPARTMENT OF THE ARMY,

DEPUTY CHIEF OF STAFF, PERSONNEL (ARMY G-1)

MANAGEMENT SUPPORT OFFICE

PANMCC24P0000004801

PART 1

GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to provide professional operations research and information technology support services to Headquarters, Department of the Army (HQDA), Deputy Chief of Staff (DCS), Personnel (G-1). The Government will not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers must be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1. Description of Services/Introduction: The Contractor must provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform professional operations research and information technology support services as defined in this performance work statement except for those items specified as Government furnished property and services.

The Contractor must perform to the standards in this contract.

1.2. Background: The mission of the G-1’s Military Strength Analysis and Forecasting Division (DAPE-PRS) is to develop personnel forecasts (i.e. the Active Army Military Manpower Program or AAMMP) and conduct analyses to support the seven-year budget process, support policy decisions by the senior leadership, and respond to inquiries from other agencies, including Congress. These forecasts and analyses touch every aspect of the Active Component personnel management system. To accomplish this mission, DAPE-PRS, manned with military and civilian operations research analysts, uses a suite of mathematical models collectively called the Active Army Strength Forecaster (A2SF) that were developed and have been modified and maintained with contracted support. Descriptions of A2SF models are in Technical Exhibit 5 – A2SF System & Model Descriptions.

1.3. Objectives:

1.3.1. Provide professional operations research/data analysis expertise to the analytic efforts of DAPE- PRS analysts.

1.3.2. Perform custom software modification and maintenance for operations-research-focused computer programs that include, but are not limited to, time-series rate-generation programs and large-scale linear programs (optimization).

1.3.3. Perform data processing and database administration, modification and maintenance for DAPE- PRS databases, which currently include mySQL and Oracle databases.

1.3.4. Perform administration, modification, and maintenance of the A2SF system, peripherals and supporting COTS products.

1.3.5. Perform system administration and tasks necessary to maintain compliance with Army Risk Management Framework (RMF) requirements, to include maintaining Enterprise Mission Assurance Support Service (eMASS) records. A2SF currently operates under an access-only, continuous-monitoring authority as information technology below the system level.

1.4. Scope: Provide professional operations research/data analysis expertise to the analytic efforts of DAPE-PRS.

Ensure regulatory compliance, sustainment and continuous operational capability of the A2SF suite of models and DAPE-PRS databases. Provide management, personnel supervision, maintenance, modification, training, and testing of all A2SF application components, peripherals and DAPE-PRS databases. Serve as technical subject matter experts in discussions with stakeholders and outside organizations.

1.5. Section 508 Compliance: All electronic and information technology (EIT) procured through this performance work statement must meet the applicable accessibility standards at 36 CFR 1194, unless an agency exception to this requirement exists. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended in 1998, and is viewable at: https://www.section508.gov/.

1.6. General Information

1.6.1. Quality Control (QC): The Contractor must develop and maintain an effective quality control program (QCP) to ensure services are performed in accordance with this PWS and applicable laws, regulations and policies. The Contractor must develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor’s quality control program is the means by which the Contractor assures that work complies with the requirement of the contract. The QCP must be delivered within 30 days after award. Subsequently, any modifications must be submitted electronically through the contracting officer representative (COR) to the contracting officer (KO) within five working days of the change. After acceptance of the quality control plan the Contractor must receive the KO’s acceptance in writing of any proposed change to his QC system.

1.6.2. Quality Assurance (QA): The Government will evaluate the Contractor’s performance under this contract in accordance with the quality assurance surveillance plan (QASP). This plan is primarily focused on what the Government will do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rates.

1.6.3. Recognized Holidays: The Contractor is not required to perform services on holidays:

New Year’s Day Martin Luther King Jr.’s Birthday President’s Day Memorial Day Juneteenth Independence Day

Labor Day Columbus Day Veterans Day Thanksgiving Christmas

1.6.4. Hours of Operation: The Contractor is responsible for supporting DAPE-PRS operations during all hours of operation. Typical hours of operation are between 7 AM and 5 PM Monday thru Friday, except federal holidays. Weekend, holiday or after-hours support may be required but is not common to meet performance objectives. The Contractor must maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the Contractor must keep in mind that the stability and continuity of the workforce are essential.

1.6.5. Place of Performance: Routine work to be performed under this contract must be performed remotely from facilities provided by the Contractor. Physical access to Army installations, facilities, and controlled-access areas is not required for contract performance.

1.6.6. Type of Contract: The Government will award a firm fixed-price (FFP) contract.

1.6.7. Security Requirements: The contractor does not require access to classified data. If, subsequent to the date of this contract, the security classification or security requirements under this contract are changed by the Government and if the changes cause an increase or decrease in security costs or otherwise affect any other term or condition of this contract, the contract shall be subject to an equitable adjustment as if the changes were directed under the Changes clause of this contract. The Contractor agrees to insert terms that conform substantially to the language of this clause, including this paragraph but excluding any reference to the Changes clause of this contract, in all subcontracts under this contract that involve access to classified information.

1.6.7.1. Physical Security. The contractor must safeguard all government-furnished property/equipment provided for contractor use..

1.6.7.1.1. Systems Security: The contractor must encrypt all contractor-owned laptops or other portable media storage devices that process or store PII, in accordance with NIST Federal Information Processing Standard (FIPS) 140-2 (or successor). The contractor must require FIPS 140-2 (or successor) encryption of any sensitive PII when transmitted electronically across the internet or other public networks.

1.6.7.1.2. Data Security: The contractor, unless otherwise authorized by the Government, must limit access to PII to those employees and subcontractors who require the information in order to perform their official duties under this contract. The contractor, contractor employees, and subcontractors must physically or electronically protect

PII when not in use and/or under the control of an authorized individual. During the course of contract performance, when PII is no longer needed or required to be retained under applicable Government records retention policies, the contractor must coordinate with the contracting officer to either turn over the PII to the Government or destroy it through means that make the PII irretrievable (i.e., permanently unavailable for access by any person). The contractor must only use PII obtained under this contract for purposes contract performance and must not collect or use such information for any other purpose without the prior written approval of the contracting officer. At expiration or termination of this contract, the contractor must coordinate with the contracting officer to either turn over all PII managed under the contract that is in its possession to the Government or successor contractor, or if the Government so directs, destroy the PII. The contractor shall ensure that all data-at-rest and data in-transit is encrypted utilizing NSA-approved encryption.

1.6.7.1.3. Data Breach Response and Notification: The contractor must adhere to the reporting and response requirements for PII set forth in Office of Management and Budget (OMB) Memorandum M-17-12, Subject:

Preparing for and Responding to a Breach of Personally Identifiable Information, January 3, 2017; AR 25-22 The Army Privacy and Civil Liberties Program, DoD 5400.11-R, DoDI 5400.11, DoDM 5400.11 Volume 2, and any amendments. The contractor or its subcontractor(s) must immediately notify the COR or DAPE- PRS Division Chief upon discovery that a suspected or actual breach of PII has occurred. The Government will report the breach to the Army Privacy and Civil Liberties Office within 24 hours of breach discovery. The Government may require the contractor to notify any potentially affected individuals.

1.6.7.2. Personnel. Contractor personnel performing work under this contract must be capable of obtaining a favorable National Agency Check (NAC). Contractor personnel performing work that requires routine physical access to government systems or facilities under this order, requesting routine physical access to government systems or facilities (e.g. to facilitate face-to-face meetings), or having access to PII data must have Tier 3 suitability and must maintain that for the duration of performance under this contract. Within five business days after the receipt of the order, the contractor must submit an OF306 and proof of citizenship (for example: birth certificate or passport) for each employee performing work on this contract and a visit authorization letter for personnel requesting access to government facilities.

1.6.7.3. Common Access Cards (CAC) and Privileged Token Cards: The Contractor must establish and implement methods of making sure all CAC’s and privileged token cards issued to the Contractor by the Government are neither misplaced nor used by unauthorized persons. The Contractor must develop procedures covering card control that must be included in the Quality Control Plan. Such procedures must include the turn-in of any issued cards by personnel who no longer require access/privileges for performance of tasks under this contract.

The Contractor must immediately report any occurrences of lost or duplicate cards to the KO through the COR.

1.6.7.3.1. Contractors requiring Common Access Card (CAC). Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

1.6.7.3.2. Reserved.

1.6.7.4. Reserved.

1.6.7.5. Reserved.

1.6.7.6. Reserved.

1.6.7.7. Pentagon Access: All contractor personnel requesting routine entrance to the Pentagon must process a Visit Authorization Request through the COR to the G-1 Security Office. Contractor personnel visiting the Pentagon must comply with visitor processing procedures identified at https://www.pfpa.mil/Topics/Visiting-the- Pentagon/.

1.6.7.8. Reserved.

1.6.7.9. Contractor Employees Who Require Access to Government Information Systems: All contractor employees, to include subcontractor employees, requiring access to DoD information technology systems must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services (https://atc.us.army.mil/iastar/index.php). Complete the DoD Cyber Awareness (IA) Training and sign the Acceptable-Use Policy before issuance of network access and annually thereafter. Both are located at the following CAC-enabled site: https://cs.signal.army.mil/login.asp . The Acceptable-Use Policy is to be signed on the same day that Cyber Awareness Training is completed.

1.6.7.10. Update their profile and Global Address Listing (GAL) information within 10 working days of being granted access (https://milconnect.dmdc.osd.mil/milconnect)

1.6.7.11. OPSEC Training: Per AR 530-1 Operations Security, contractor employees must complete Level I OPSEC Awareness training within 30 days of contract award and annually thereafter. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter. Training certificates must be provided to the COR.

1.6.7.12. Reserved.

1.6.7.13. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 upon contract award.

1.6.8. Special Qualifications:

1.6.8.1. Information Assurance Technician (IAT) Level II. IAT Level II certifications must be met and maintained by contractor and subcontractor personnel who require privileged access to host environments, the A2SF models/servers or other DoD IT System in accordance with DoD 8570.01-M. Credentials must be submitted through Army's Training Certification Tracking System (ATCTS) to obtain privileged access. At a minimum, two employees must be certified for the hosting environment(s). Submit a copy of each certification with proposal.

1.6.8.2. Privacy Act & Training: Contract employees must comply with the Privacy Act and all applicable agency regulations on individual privacy, to include DoD Directive 5400.11 “Department of Defense Privacy Program” and DoD 5400.11-R, Department of Defense Privacy Program. Employees in contact with raw data containing PII are subject to the Privacy Act (Title 5 of the U.S. Code, Section 552.a) and must complete annual Privacy Awareness Training coordinated through the Army Learning Management System (ALMS). Training certificates must be provided to the COR.

1.6.8.3. Contract personnel must be able to read, write, speak, and understand the English language.

1.6.8.4. Minimum qualifications and experience levels are addressed in Technical Exhibit 4 – Contractor Minimum Personnel Functions/Requirements.

1.6.8.5. If any documentation, certifications or licenses have been revoked, rescinded, or suspended, contractor must:

1.6.8.5.1. Refrain from hiring the person to work under this contract; or

1.6.8.5.2. Replace the employee immediately and notify the COR and KO.

1.6.8.6. Management and Staffing Plan (MSP). Contractor must identify within its proposal’s MSP all contractor personnel by: labor category, education, years of relevant experience, certifications, and security clearance. The MSP must address how education and experience will be met for key personnel and each of the requirements listed in Technical Exhibit 4 – Contractor Minimum Personnel Functions/Requirements. Include type (organic, to-be-hired, subcontract, etc.) and level of effort (dedicated full time, matrixed support, available on staff if needed). The MSP must also include any additional qualifications or resources that would support the contractor’s capability to perform the work specified in this PWS.

1.6.9. Post Award/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer or COR will apprise the contractor of how the government views the contractor's performance, and the contractor must apprise the Government of any challenges. Appropriate action must be taken to resolve outstanding issues. These meetings must be at no additional cost to the government. The contractor must provide written meeting minutes to the COR within three business days of the meeting.

1.6.10. Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11. Key Personnel: The following personnel are considered key personnel by the government: Program Manager (PM), Alternate Program Manager (APM), Chief Operations Research Scientist (CS), and Chief Data Warehouse Administrator (CDW). Resumes for all key personnel must be provided at proposal submission. Qualifications and requirements for all key personnel are listed below:

1.6.11.1. Program Manager (PM): The contractor must provide a PM who must be responsible for the performance of the work and who must serve as the primary point of contact with the COR and KO. The name of this person must be designated in writing to the contracting officer. This does not preclude the PM from fulfilling other roles on this contract, except for APM. The PM must:

1.6.11.1.1. Have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

1.6.11.1.2. Ensure PM or APM is available between 8 AM and 5 PM, Monday through Friday, except Federal holidays or when the Pentagon is closed for administrative reasons and employees are not tele-working.

1.6.11.1.3. Respond to inquiries and requests for information from DAPE-PRS within 2 work hours (carried over to next business day if window extends past 5PM) with a minimum of a proposed course of action and estimated time to delivery.

1.6.11.1.4. Minimum Qualifications for PM:

1.6.11.1.4.1. The PM must be Project Management Professional (PMP) certified.

1.6.11.1.4.2. The PM must and have at least a Master's degree from an accredited academic institution in one of the following: applied mathematics, computer science, economics, engineering management, information technology, operations research, software engineering, statistics, or systems engineering.

1.6.11.1.4.3. The PM must have at least six years of relevant experience delivering operations research solutions or IT solutions supporting operations research efforts.

1.6.11.1.4.4. The PM must have at least four years of experience as PM or APM with at least one project of similar size, scope, and complexity to A2SF (i.e. providing management, maintenance, and modification for a multi-component system that includes a database that interacts with an application that has a graphic-user interface and that supports an operations research effort.)

1.6.11.1.4.5. The PM must have experience as PM or APM for at least one project in each of the following areas:

(1)operations research, (2) database management, and (3) web based applications. One project may cover multiple areas.

1.6.11.1.4.6. The PM must have experience serving as PM or APM on at least one IT project for a DoD client.

1.6.11.2. Alternate Program Manager (APM): The contractor must provide an APM who will be responsible for the performance of the work and act for the contractor when the PM is unavailable. The APM must be designated in writing to the contracting officer. This does not preclude the APM from fulfilling other roles on this contract, except for PM. The APM must:

1.6.11.2.1. Have full authority to act for the contractor on all contract matters relating to daily operation of this contract when the PM is unavailable.

1.6.11.2.2. Be available between 8 AM and 5 PM, Monday through Friday, when the PM is unavailable, as described in PWS 1.6.12.1.2 .

1.6.11.2.3. Minimum Qualifications for APM:

1.6.11.2.3.1. The APM must be Project Management Professional (PMP) certified.

1.6.11.2.3.2. The APM must have at least a Master's degree from an accredited academic institution in one of the following: applied mathematics, computer science, economics, engineering management, information technology, operations research, software engineering, statistics, or systems engineering.

1.6.11.2.3.3. The APM must have at least four years of relevant experience delivering operations research solutions or IT solutions supporting operations research efforts.

1.6.11.2.3.4. The APM must have experience on at least one project with (1) operations research, (2) statistical analysis, or (3) database management. Relevant experience in at least one of the three areas listed should be demonstrated.

1.6.11.3. Chief Operations Research Scientist (CS): The contractor must provide a designated CS who must serve as technical expert overseeing the service support of the forecasting and optimization components of A2SF (primarily the rates/factors development and mathematical programming models). The CS is also responsible for coordinating and conducting experiments and providing technical expertise for analytic efforts conducted by DAPE-PRS. The CS may also serve as the PM or APM, and/or CDW if all requirements are met for each position.

1.6.11.3.1. Minimum qualifications for CS:

1.6.11.3.1.1. Doctoral degree from an accredited academic institution in operations research, applied mathematics, systems engineering, economics, or statistics with a minimum of six credit hours at the graduate level in mathematical programming (e.g. Linear Programming, Integer Programming, etc.) and six credit hours at the graduate level in statistics.

1.6.11.3.1.2. At least five years of relevant experience among the following: mathematical modeling (for optimization or simulation), computer programming for engineering or statistical analysis, data science, and analytic studies.

1.6.11.3.1.3. At least one year of experience operating and tuning an optimization engine such as CPLEX or Gurobi.

1.6.11.3.1.4. At least one year of experience coding mathematical programs in a scripted language (e.g. MPL, AMPL, GAMS).

1.6.11.3.1.5. At least one year of experience developing, using, or analyzing forecasting models.

1.6.11.4. Chief Data Warehouse Administrator (CDW): The contractor must provide a designated CDW, who must serve as technical expert overseeing the service support of data processes, databases and IT systems to the level authorized by the host and coordinating efforts beyond the level of service authorized to perform. The CDW may also serve as the PM or APM, and/or CS if all requirements are met for each position.

1.6.11.4.1. Minimum qualifications for CDW

1.6.11.4.1.1. The CDW must have at least a Master’s Degree from an accredited university in a related IT field such as computer science, computer programming, data base architecture, information systems, information technology, or software engineering.

1.6.11.4.1.2. At least five years of relevant experience among the following: data warehousing, database design and development, and database administration. At least two years of experience implementing data stores on DoD servers subject to DoD security protocols.

1.6.11.4.1.3. At least one year experience providing database administration for an Oracle database.

1.6.11.4.1.4. At least one year experience leading a database support team or project in database design, development, and maintenance.

1.6.11.5. The contractor agrees that such personnel must not be removed or replaced within the performance of this contract unless the following measures are taken:

1.6.11.5.1. If one or more of the key personnel, for any reason, becomes or is expected to become unavailable for work under this contract for a continuous period exceeding 30 work days, or is expected to devote substantially less effort to the work than indicated in the proposal or initially anticipated, the contractor must, subject to the concurrence of the Contracting Officer (KO) or designated Contracting Officer Representative (COR), promptly replace personnel with personnel who possess equal, or better, qualifications as the original employee

1.6.11.5.2. All requests for approval of substitutions hereunder must be in writing and provide a detailed explanation of the circumstances necessitating the proposed substitutions. The request must contain a resume for the proposed substitute, and any other information requested by the KO or designated COR. The KO or designated COR must concur in writing with the change.

1.6.11.5.3. If the KO or designated COR determines that suitable and timely replacement of Key Personnel who have been reassigned, terminated or have otherwise become unavailable for the contract work is not reasonably forthcoming or that the resultant reduction of productive effort would be so substantial as to impair successful completion of the contract, the KO may terminate the contract for default or for the convenience of the Government, as appropriate, or make an equitable adjustment to the contract to compensate the Government for any resultant delay, loss or damage.

1.6.11.6. Other Contractor Personnel Requirements. In addition to the key personnel requirements in PWS 1.6.11 , the government requires several additional qualifications and requirements for the project team that do not need to be possessed by a particular key person or position. Qualifications and experience requirements (e.g.

information assurance certifications and computer languages) that government deems necessary for successful performance, but are not directly tied to key personnel or specific positions, are also listed in Technical Exhibit 4 – Contractor Minimum Personnel Functions/Requirements. This provides the contractor with the maximum flexibility to manage their staff for performance of this contract. Resumes are not required for non-key personnel.

1.6.12. Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.6.13. Contractor Travel: Travel outside the NCR is not expected, and t r avel within the NCR is generally non-reimbursable.

1.6.14. Other Direct Costs: This category includes reproduction and shipping expenses associated with training activities and non-routine expenses associated with migration to and sustainment of operations and services in a new hosting environment. These ODC expenses must be preapproved by the KO.

1.6.15. Data Rights: The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract must be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the contractor without written permission from the Contracting Officer. All materials supplied to the Government will be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.6.16. Organizational Conflict of Interest (OCI): Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor must notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and must promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17. Phase In / Phase Out Periods:

1.6.17.1. During the phase-in period, the Contractor must become familiar with performance requirements in order to commence full performance of services on the contract start date. The contractor must provide its Phase-In Plan at proposal submission. To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor must have personnel on board during the thirty (30) day phase-in periods.

1.6.17.2. The phase-out period occurs at contract’s termination or during the final option period at no additional cost to the government. The written phase-out plan must be submitted to the KO and COR no later than sixty (60) days prior to the end of the contract. The phase-out plan must ensure continuous operations of the A2SF system and minimize interruptions to daily operations.

PART 2

DEFINITIONS & ACRONYMS

2.1. Definitions:

2.1.1. ARMY G-1. Headquarters, Department of the Army, Deputy Chief of Staff, Personnel

2.1.2. CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the government. The term used in this contract refers to the prime.

2.1.3. CONTRACTING OFFICER (KO). A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.4. CONTRACT SPECIALIST. A person that supports the KO and compiles the contract packages for award.

Note: This individual cannot legally bind the government.

2.1.5. CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment must be in writing and must state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.6. DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.7. DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.8. EXPERT / EXPERT-LEVEL. Demonstrating special skill or knowledge obtained through study or experience that represents mastery of a particular subject.

2.1.9. FUNCTIONAL PROPONENT. Army G-1 DAPE-PRS

2.1.10. INDIVIDUALS ACCOUNT (a.k.a. “TTHS”). Soldiers, officers and USMA cadets who are Transient (traveling between assignments) or assigned as Trainees, Holdees (e.g. Patients, Prisoners) or Students. All USMA cadets are in the Individuals Account. Army Strength = TTHS + Operating Strength.

2.1.11. KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS.

2.1.12. LINEAR PROGRAMMING (LP). Specialized case of mathematical programming that is restricted to linear expressions.

2.1.13. MATHEMATICAL PROGRAMMING. An operations research discipline that uses specialized optimization software to solve mathematical models in order to find the best solution and support decision making. The field includes linear programming (LP – most common), integer programming (IP), mixed integer programming (MIP), non-linear programming (NLP), and stochastic programming (SP). Within this PWS, mathematical programming is synonymous with optimization.

2.1.14. MATHEMATICAL MODELING. Abstracting real world phenomena in terms of mathematical expressions. For A2SF this is a system of linear equalities for use in forecasting and analysis.

2.1.15. OPERATING STRENGTH. The count of Soldiers and officers assigned against authorized positions or assigned as excess against authorized positions. Soldiers and officers not in the operating strength are considered in the Individuals Account (a.k.a. “TTHS”). Army Strength = TTHS + Operating Strength.

2.1.16. OPERATING STRENGTH DEVIATION. Difference between the force structure and the operating strength.

2.1.17. OPTIMIZATION. Optimization, as used throughout this PWS, refers to solving a mathematical model (as in a system of inequalities) in order to find the best solution or policy. Generally, optimization may employ a variety of techniques, but within this PWS it is synonymous with mathematical programming.

2.1.18. PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.19. QUALITY ASSURANCE (QA). The government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.20. QUALITY ASSURANCE Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.21. QUALITY CONTROL (QC). All necessary measures taken by the Contractor to assure that the quality of an end product or service must meet contract requirements.

2.1.22. SUBCONTRACTOR. One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.1.23. WORK DAY. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.24. WORK WEEK. Monday through Friday, unless specified otherwise.

2.2. Acronyms:

A2SF Active Army Strength Forecaster

AAMMP Active Army Military Manpower Program

AC Active Component

AFARS Army Federal Acquisition Regulation Supplement

AMPL A Mathematical Programming Language

APM Alternate Program Manager

AR Army Regulation

ASI Additional Skill Identifier

ATTRS Army Training Requirements and Resources System.

BYR Base Year

EG Enlisted Grades Model

C++ Intermediate-level programming language

CA Contract Administration; Contract Administrator

CAC Common Access Card

CCE Contracting Center of Excellence

CDR Contract Discrepancy Report

CFE Contractor-Furnished Equipment

CFI Contractor-Furnished Information

CFP Contractor-Furnished Property

CFR Code of Federal Regulations

CFS Contractor-Furnished Services

CMP Configuration Management Plan

CMR Contractor Manpower Reporting

CONUS Continental United States (excludes Alaska and Hawaii)

COR Contracting Officer’s Representative

COTR Contracting Officer's Technical Representative

COTS Commercial-off-the-shelf

CPLEX IBM’s high-performance mathematical programming solvers

DA Department of the Army

DAPE-PRS Military Strength Analysis and Forecasting Division, Army G-1

DB Database

DCS Deputy Chief of Staff

DD Department of Defense (used to label forms)

DD250 Department of Defense Form 250 (Receiving Report)

DD254 Department of Defense Contract Security Requirement List

DFARS Defense Federal Acquisition Regulation Supplement

DISCO Defense Industrial Security Clearance Office

DMDC Defense Manpower Data Center

DoD Department of Defense

DP Data Processing

DSS Defense Security Service

EST Eastern Standard Time

EDT Eastern Daylight Time

EOM End of Month

ETL Extract, Transfer, Load (data)

FAR Federal Acquisition Regulation

FFP Firm-Fixed-Price

FPCON Force Protection Conditions

FS Force Structure

FSC Federal Service Code

FT First Term Network

FY Fiscal Year (October – September)

G-1 Army Deputy Chief of Staff, Personnel

GAMS General Algebraic Modeling System

GFE Government-furnished Equipment

GFI Government-furnished Information

GFP Government-furnished Property

GFS Government-furnished Services

GSA General Services Administration

GWAC Government-wide Acquisition Contract

HIPAA Health Insurance Portability and Accountability Act of 1996

HRC US Army Human Resources Command

HQDA Headquarters, Department of the Army

IA Individual’s Account Model; Information Assurance

IAW In accordance with

ID Identification Card

IMO Information Management Office

IPPS-A Integrated Pay and Personnel System - Army

IT Information Technology

ITA Information Technology Agency

ITAPDB Integrated Total Army Personnel Database

JER Joint Ethics Regulation

JTR Joint Travel Regulation

KO Contracting Officer

LES Law Enforcement and Security

LP Linear Program (mathematical programming)

LSI Language Skill Identifier

MICC Mission & Installation Contracting Command

MCO—FTK Mission Contracting Office—Fort Knox, KY

MOS Military Occupational Specialty

MPL Mathematical Programming Language from Maximal Software

MS Microsoft

MSV Month-of-Service

NAC National Agency Check

NISA Network Infrastructure Services Agency

NLT No later than

NTE Not-to-exceed

OCI Organizational Conflict of Interest

OCONUS Outside Continental United States (includes Alaska and Hawaii)

ODC Other Direct Costs

OS Operating Strength

PBA Performance-based acquisition

PIP Phase-in Period

PIPO Phase In/Phase Out

PM Program Manager

PMS Personnel Management System

POC Point of Contact

POP Period of Performance

PRS Performance Requirements Summary

PWS Performance Work Statement

QA Quality Assurance

QAP Quality Assurance Program

QASP Quality Assurance Surveillance Plan

QCP Quality Control Plan

QMF Quality Management Framework

REE Re-Enlistee Network

RFP Request for Proposal

RMF Risk Management Framework

SAS Statistical Analysis System

SME Subject Matter Expert

SQL Structured Query Language

SSN Social Security Number

T# Term of Service = T1 (one year), T2 (two years), etc.

TAPDB Total Army Personnel Database

TAF Total Active Force

TBD To be determined

TE Technical Exhibit

TO Task Order

TOS Term of Service

TTHS Trainees, Transients, Holdees and Students (same as IA)

TSS Technical Support Services

US United States

USG US Government

USMA US Military Academy

V&V Validation & Verification

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1. Services:

3.1.1. DAPE-PRS will maintain a hosting agreement with the hosting environment in which all servers reside (currently Amazon Web Services in cArmy). The contractor must coordinate with and adhere to all hosting environment requirements. The A2SF application and/or supporting databases may, at the convenience of the government, be migrated to another service provider. Operations within such environments will be considered government-owned, contractor-operated.

3.1.2. The government will provide the software licenses mandated or required to run the A2SF suite of models and maintain databases (e.g. MPL w/ CPLEX licenses, Fortify for code scanning)

3.2. Facilities: Not applicable.

3.3. Utilities: Not Applicable.

3.4. Equipment: If required, the government will hand-receipt up to six laptop computers configured with standard Army Gold image, including Microsoft Office products and VPN client for remote access to hosting sites from the contractor’s site.

3.5. Materials: The government will provide access to all code, schematics, and documentation for A2SF, the data processing, data ETL process, and the data warehouses that are available.

PART 4

CONTRACTOR FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1. General: The Contractor must furnish all supplies, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2. Secret Facility Clearance: Not applicable.

4.3. Materials:

4.4. Upon request and no later than the completion of this contract, the contractor must furnish all programs, modules, code, and custom software developed or modified in the performance of this contract. Such products will remain property of the government.

4.5. Upon request the contractor must furnish documentation and instructions regarding all programs, modules, code, and custom software developed or modified in the performance of this contract. Such products will remain property of the government.

4.6. Equipment: Not Applicable.

PART 5

SPECIFIC TASKS

5. SPECIFIC TASKS

5.1 Basic Services. The contractor must provide professional operations research/data analysis expertise to the analytic efforts of DAPE-PRS and provide support services to modify and maintain the mathematical models and databases.

5.2 Select Performance Requirements (Standards) are addressed in Technical Exhibit 1 – Performance Requirements Summary.

5.3 Select Deliverables are addressed in Technical Exhibit 2 – Deliverables Schedule.

5.4 Professional Operations Research/Data Analysis Expertise. The contractor must:

5.4.1 Provide expert-level operations research recommendations and support (e.g. guidance related to statistical, optimization, and probability theory) to the analytic efforts of DAPE-PRS analysts.

5.4.2 If requested, the contractor must produce training materials and provide informal training on the operation of the A2SF systems, underlying data and interpretation of model output. This might occur once per year in conjunction with the turn-over of military analysts or quarterly if broken into smaller subjects for training.

5.5 Mathematical Programming Model Modification and Maintenance. The contractor must:

5.5.1 Perform custom software modification and maintenance for operations-research-focused computer programs such as time-series rate-generation programs and large-scale linear programs (optimization). Such efforts would not increase the functional scope of the software but would rather improve algorithms/techniques used within the software.

5.5.2 In coordination with DAPE-PRS analysts, modify optimization models and supporting components/models, to reflect desired modeling changes (e.g. create a new constraint in the optimization program to account for a new personnel policy).

5.5.3 Report, research, and resolve model infeasibility errors (optimization) and anomalous output.

5.5.4 Conduct verification and validation of model modifications prior to implementation.

5.5.5 Conduct ongoing A2SF system analyses to improve efficiency and accuracy, provide recommendations, and implement changes.

5.6 Data Processing and Data Base Administration. The contractor must:

5.6.1 Coordinate, maintain and execute data feeds from external sources (“alien feeds”). This includes the extraction, transformation and loading (ETL) of data and the maintenance/modification of ETL code. Updated data is to be verified and prepared for DAPE-PRS use within one business day of notification of availability from either the data source or from DAPE-PRS.

5.6.2 Perform roles as database administrator including maintenance, repair, access control, and modification of primary databases (currently Oracle databases in a cloud environment). If the hosting environment restricts administrator access/roles, perform roles to the level authorized and coordinate for higher-level support with the hosting environment administrators. Coordinate access permissions for individuals with DAPE-PRS functional lead or COR. A2SF model processes and analysts should have continuous access to properly formatted and complete data within databases.

5.7 System Administration, Modification and Maintenance. The contractor must:

5.7.1 Control access to, maintain, repair, and modify A2SF processing code, interfaces, servers and peripherals to ensure continuous operations and to maintain compliance with applicable DoD IT protocols, policies, and standards.

If the hosting environment restricts administrator access, perform these roles to the level authorized and coordinate for higher-level support with the hosting environment administrators.

5.7.2 The contractor must comply with implementation of the DoD Risk Management Framework (RMF) as governed by DoD Instruction 8510.01, for DoD Information Technology (IT), to include maintaining a current authority to operate (currently A2SF is an “access-only” application). Coordinate as required with host cyber-security personnel. Develop and maintain eMASS records as required for DAPE-PRS systems/applications.

Develop, submit and track Plans of Action and Milestones (POA&M’s) to address non-compliance issues identified as security findings that cannot be immediately remediated.

5.7.3 Maintain monthly backup of A2SF application software and databases with the ability to restore on primary servers within one business day of servers becoming available.

5.7.4 Maintain a test environment as an accurate representation of the current production environment to minimize the impact of testing and experimentation on the operational environment. Conduct verification and validation of modifications, updates, and other system changes using the testing environment prior to implementation on production servers.

5.7.5 Provide Tier III Level IT support for A2SF systems and applications, including COTS products. If the hosting environment restricts privileged access, perform these roles to the level authorized and coordinate for higher-level support with the hosting environment administrators

5.7.6 Develop and maintain an effective quality control program (QCP) to ensure services are performed in accordance with PWS 1.6.1 .

5.7.7 Produce a Monthly Project Summary Report that includes summary data for all tasks completed in the previous month and, as appropriate, records the minutes of any progress meetings.

5.7.8 Maintain a Configuration Management Plan (CMP) to document completed or planned modifications and maintenance repairs. Submit monthly to COR with the Monthly Project Summary Report.

5.7.9 Coordinate and conduct Joint Management Reviews (JMR) at least once per month with COR and other DAPE-PRS personnel to address current issues associated with the execution of this contract, especially those items identified in the CMP. Record minutes of meeting in the Monthly Project Summary Report.

5.7.10 Provide technical information and input for special reports and studies (e.g. Cost-Benefit Analysis for migration to different cloud-hosting environments).

5.7.11 Develop, update and maintain current A2SF system documentation that includes, as a minimum, the following: user manuals/scripts for all models and data processing; data dictionaries and data model documentation;

training materials. Provide copies of all initial documentation within 180 days of contract start and updates after significant system changes within 90 days of change.

5.7.12 Participate in meetings and prepare documentation as required in the roll of technical representative for DAPE-PRS models, data and IT support.

5.8 Data Source Conversions. If additional or new data sources become available, the contractor must:

5.8.1 Support the addition of new data sources and/or the conversion from existing data sources to new data sources. Support includes, but is not limited to, coordinating and establishing interface connections, making modifications to ETL code (primarily written in SAS), A2SF components and databases, and providing technical expertise.

5.8.2 Conduct validation and verification and participate in user-testing to determine if new data sources are acceptable.

5.9 Phase-in Period: The contractor must submit its phase-in plan at proposal submission. To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the contractor must have personnel on board during the phase-in period.