PWS MEDX AFCENT 08062024 22_Nov_1014.pdf

Solicitation Number / Contract Number TBD 5 July 2024

PERFORMANCE WORK STATEMENT

for

Medical Expeditionary Systems (MEDXS) and Air Force Central Command (AFCENT) Solicitation/Contract Number TBD

(Version Control Date: 22 Jun 22)

Table of Contents Section Page Number

1. DESCRIPTION OF SERVICES

1.1. Background

1.2. Scope

2. GENERAL INFORMATION

2.1. Contractor Identification

2.2. Contractor Training

Table 1

2.3. Contractor/Government Communication

2.4. Monthly Status/Financial Report. The Contractor shall prepare and submit a monthly status/financial report identifying all tasks performed, status, issues, and anticipated actions consistent with the performance work statement (PWS) each month. The Contractor shall provide the Monthly Status/Financial Report IAW Contract Data Requirement List (CDRL) A003 and associated DID

Place of Performance

2.6. Travel Requirements

2.7. Mission/Emergency Essential

2.8. Duty Hours

2.9. Telecommuting

2.10. Federal Holidays

2.11. Facility Closures

2.12. Conduct of Contractor Personnel

2.13. Controlled Unclassified Information (CUI)

2.14. Personnel Staffing:

3. CONTRACT REQUIREMENTS

3.2. Minimum Qualifications

3.3. Security Requirements. (For Unclassified Contracts)

3.4. Service Contract Reporting (SCR)

3.5. Post-Award and Initial Contract Performance Meeting

4. PERFORMANCE OBJECTIVES

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

Update, page #s not correct

Ladson, Rosanna CTR (USA) Updated

4.1. Services Summary (SS)

5. GOVERNMENT FURNISHED PROPERTY (GFP). N/A

6. DELIVERABLES

Appendix A

ACRONYMS

Appendix B

DOCUMENTS

PERFORMANCE WORK STATEMENT (PWS)

Medical Expeditionary Systems (MEDXS) and Air Force Central Command

(AFCENT)

1. DESCRIPTION OF SERVICES

1.1. Background. Air Combat Command/Surgeon General (ACC/SG) provides a set of enterprise Information Management /Information Technology (IM/IT) solutions that support the unique mission of expeditionary medical support, Electronic Health Records (EHR), Public Health and Aeromedical Evacuation (AE) activities. The U.S. Air Force Medical Agency (AFMED) SG6X - Air Force Operational Medicine Information Systems (AFOMIS) Program Office is responsible for health-related IM/IT services support to deployed Airmen and collocated personnel within all Theaters of Operations. This support includes Medical Expeditionary Systems (MEDXS), medical waivers workflow management, Expeditionary Health Data Store (EHDS), medical analytics dashboards, integrated IM/IT testing capability, medical operations; expeditionary deployment operations and installation contingency response;

planning; training; and readiness support functions. Components of this global system are integrated, with forward-deployed medical support, and en-route care, providing comprehensive and definitive medical specialty care. The Joint Operational Medicine Information Systems (JOMIS) Program Management Office (PMO) is responsible for development and sustainment of the Theater Medical Information Program - Joint (TMIP-J) legacy family of systems, and the Healthcare Delivery (HCD) Modernized family of systems. AFOMIS Program Office has the responsibility to provide pre-deployment training and to provide follow on support of the implementation and usage of the JOMIS Operational Medicine (OpMed) IM/IT solutions.

The JOMIS PMO provides IT solutions that support the missions of Expeditionary Medical Support (EMEDS) and AE (also known as en route care) and other deployed healthcare IM/IM systems throughout all Combatant Commands (COCOMs). The AFCENT/SG also supports the deployed IM/IT mission by ensuring deployed medical sites maintain operational capability in theater and garrison. This mission includes all EMEDS ground support IM/IT applications currently used throughout supported theaters of operations. AFCENT/SG also has the responsibility to ensure the appropriate support for EMEDS personnel in their daily activities associated with the use of all IM/IT in terms of ensuring that they are continually in a state of readiness. The Air Force Medical Service (AFMS) in some cases has unique missions and therefore ACC/SG and AFOMIS program office must also support these for both Joint and Service unique needs, to include all facets and sizes of the ACC/SG War Readiness Material (WRM) requirements across the globe.

1.2. Scope. This is a performance based non-personal services requirement to enable AFOMIS to provide full systems life-cycle support to rapidly deliver and support solutions that enable information dominance for USAF, Joint, National and Coalition Warfighters. These services provide technical support for the MEDXS portfolio of capabilities and life-cycle support to all

OpMed IM/IT systems used in support of the AFMS. It requires experienced individuals that possess the specific technical and functional understanding of the unique AF configuration of Operational Medicine (OpMed) IM/IT as well as MEDXS integrated applications. Support services include both in-theater and garrison location support, availability 24x7x365 and other unique qualifications to meet requirements and provide support of OpMed IM/IT systems and requirements. Support includes strategic planning, design, development, engineering, test and evaluation, deployment, installation, operation and maintenance, logistics, sustainment, and program management for IM/IT solutions. All decisions relative to programs supported by the Contractor shall be the sole responsibility of the Government.

2. GENERAL INFORMATION

2.1. Contractor Identification. All Contractor/Subcontractor personnel shall identify themselves as Government Contractor personnel during all forms of communications such as business meetings, telephone conversations, electronic mail, attendance sheets, coordination documentations, reports, and the signature blocks utilized in all correspondence. If a contract requires Government workspace, the Contractor/Subcontractor personnel shall wear a picture identification badge and identify their workspace area with their name and company affiliation.

2.2. Contractor Training.

Table 1

Training Contractor Personnel Applicability Active Shooter, Level 1 All contractors Operations Security (OPSEC) All contractors

Antiterrorism Training, Level 1 Contractors requiring routine physical access to federally controlled facilities or military installations (DFARS 252.204-7004)

Annual Security Refresher All fulltime/partial, onsite contractors Suicide Prevention Training (Suicide Awareness) All fulltime, onsite contractors

DoD Cyber Awareness Challenge

All contractors Health.mil account holders and Personnel accessing CAC-enabled gov't sites - Authorized users of DOD information systems and networks

Privacy and Personally Identifiable Information (PII) Awareness Training

All contractors with access to PII

Health Insurance Portability and Accountability Act (HIPAA) All contractors with access to PHI

2.2.1. Contractor personnel requiring elevated permissions to perform System Administration functions shall meet all Cyber Security Workforce requirements for certification and tracking prior to accessing DoD information systems.

2.2.2. Contractor personnel shall complete the mandatory Cybersecurity Awareness training and submit a signed System Authorization Access Request (SAAR) form to the specified COR.

Note: In order for personnel to maintain a CAC with PKI, each contractor employee shall complete annual cybersecurity training. Contractors shall seek latest guidance from their appointed company Security Officer and the AFMED Information Systems Security Management (ISSM) office.

2.2.3. In addition to training requirements and certifications required for a specific labor category, certain contractor personnel (including subcontractors) regardless of security classification shall complete required mandatory training in accordance with AFMED policy (need citation) The following table is a sample of contractor mandatory training that is subject to change in accordance with AFMED policy.

2.3. Contractor/Government Communication.

2.3.1. The Contractor shall designate a Focal Point to be the single point of contact for all Contractor and Government correspondence. The Focal Point shall provide clear and consistent written and verbal response to Government within 12 hours of Government initiated communication (e.g., return phone calls, emails, or other communication).

2.3.2. The Contractor’s Focal Point shall meet with the Government team at least quarterly.

Additional meetings may be requested by the Government or the Contractor as necessary. The Contracting Officer (CO), Contractor focal point, CORs and/or other designated representative Contractor shall provide an agenda and minutes IAW Contract Data Requirements List (CDRL) A001, A002 and corresponding DIDs.

2.4. Monthly Status/Financial Report. The Contractor shall prepare and submit a monthly status/financial report identifying all tasks performed, status, issues, and anticipated actions consistent with the performance work statement (PWS) each month. The Contractor shall provide the Monthly Status/Financial Report IAW Contract Data Requirement List (CDRL) A003 and associated DID.

2.5. Place of Performance. The work to be performed under this contract will be performed at AFOMIS Offices, AFCENT Headquarters, AFCENT Network Operations Support Center, AFCENT OpMed Sites, Fed-Ramp approved hosting facilities, Defense Health Agency (DHA) facilities, contractor facilities and remote work locations as required. Place of performance may also require support at other Air Force Medicine (AFMEDCOM), Army Medicine (AMED), and Navy Medicine (BUMED) sites worldwide, as well as other locations requested by ACC/SG or AFOMIS program manager. Known performance locations include National Capital Region, Charleston, South Carolina, immediate surrounding areas of South Carolina for remote positions within and Air Force sites outside the continental United States (OCONUS) such as Kuwait, Doha-Qatar, Riyhadh Saudi Arabia, Amman-Jordan, etc…

2.6. Travel Requirements.

2.6.1. Contractor personnel may periodically be required to travel as described in PWS Travel Table. Exact dates and destinations are not available at this time.

2.6.2. The COR will notify the Contractor no later than 14 calendar days in advance of any scheduled travel requirements. Contractor shall not travel until authorization from COR is received. The Contractor shall be responsible for obtaining all passenger transportation, lodging, and subsistence at the best value for the Government. Reimbursement of travel costs shall be IAW FAR 31.205-46, Travel Costs.

Ladson, Rosanna CTR (USA) Per Justin Ashley’s comment:

This says that performance takes place in Charleston and other location around CONUS and OCONUS. Locations need to be listed as an attachment of not spelled out here so that contactor can propose accurately. Otherwise the Government will end up drastically overpaying.

**Ed, please address comment**

Bein, Edwin CIV USN NIWC ATLANTIC VA (USA) Several places of performance have been listed. However much of the work is currently being done remotely. I’m not sure how we can be more specific. IMHO - Gov will be at more risk if this is FFP - Seems like CPF might be better.

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

Why are we using Washington DC as location for IGCE

Bein, Edwin CIV USN NIWC ATLANTIC VA (USA) IGCE was updated to more accurately reflect locations

2.6.3. The Contractor shall send an email to the COR with a written travel itinerary, meeting Government parameters, along with a written request to proceed no later than 10 calendar days prior to the travel start date. For urgent unscheduled travel requirements, the Contractor shall send an email with the itinerary and request to proceed no later than four (4) calendar days prior to travel.

2.6.4. Travel Reports shall be submitted to the COR five (5) calendar days after trip completion. Travel Report format shall include at a minimum the following: dates of travel, destination, purpose, individuals contacted, brief synopsis, issues & challenges, recommendations, and a signature. The Contractor shall provide the Travel Report IAW (CDRL) A004 and associated DID.

2.6.5. Letter of Authorization. The contractor shall have a LOA signed by the designated Contracting Officer for any and all OCONUS Travel. An OCONUS Travel Form is required for all travel locations OCONUS to include Alaska, Guam, Hawaii, Kwajalein Atoll, Johnston Atoll, Midway Islands/Atoll, Puerto Rico, US Virgin Islands, Wake Island, etc. If the travel location is not in "the lower 48"/CONUS, then an OCONUS Travel Form is required prior to the LOA being Government Authorized by AFOMIS COR in order for the Contracting Officer to approve.

The LOA identifies any additional authorizations, privileges, or Government support that contractor personnel are entitled to under contract and task order, if applicable. The contractor shall initiate a LOA for each prospective traveler. The contractor shall use SPOT or its successor, at https://spot.dmdc.mil/privacy.aspx, to enter and maintain data with respect to traveling/deployed personnel, and to generate LOAs. When necessary and if in the Government’s interest, the contractor may also initiate a LOA request to provide an official traveler access to Government facilities and to take advantage of travel discount rates in accordance with Government contracts and/or agreements. All privileges, services, and travel rate discount access are subject to availability and vendor acceptance. LOAs are required to be signed and approved by the Contracting Officer of this task order. Contractor personnel traveling in support of AFOMIS shall travel with a hardcopy approved LOA in their possession.

Travel Table

Trip Purpose Q1 Q2 Q3 Q4

System Upgrade Trip

30 Days 4 System Administrators 1 Operations Supporter

30 Days 4 System Administrators 1 Operations Supporter

Force Pivot Training/Support

30 Days 3 Operations Supporters

60 Days 1 Operations Supporter

30 Days 3 Operations Supporters

60 Days 1 Operations Supporter

On-Site Embedded Support

90 Days 1 System Administrator

90 Days 1 System Administrator

90 Days 1 System Administrator

90 Days 1 System Administrator

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

list

Added to CDRL list

Quick Response Support

30 Days 1 Operations Supporter

90 Days 1 System Administrator

30 Days 1 Operations Supporter

90 Days 1 System Administrator

2.7. Mission/Emergency Essential. None of the services listed in this PWS are mission/emergency essential.

2.8. Duty Hours. All or a portion of the effort under this task order will be performed on a government installation. The contractor shall provide support services corresponding to Government workweek and core hours. Normal workweek is Monday through Friday. Normal business hours occur 0730-1600, core hours are 0900-1500 local standard time (LST) based on location of work. (Excluding Federal Holidays).

2.9. Telecommuting

2.9.1. Telecommuting is authorized on an ad-hoc or situational basis for this contract. Routine (3 or less days per week) telecommuting and/or full-time (5 days per week) remote work may be authorized upon the written approval of the COR. The COR shall have final approval of telecommuting/remote work schedules. In the event telecommuting is authorized, a laptop with a Virtual Private Network account and Common Access Card (CAC) accessibility shall also be provided and supported by the government in locations referenced in Section 2.5. In the event of unplanned closure of the facility due to natural disasters, military emergency or severe weather, the contractor may propose an alternate work location subject to the prior coordination of the contractor’s focal point and COR. Contractors shall complete the telework training course, and a signed agreement shall be in place and provided to the COR/PM prior to telecommute. The contract personnel telecommuting will ensure continuity and timeliness in completing tasks.

2.9.2. While telecommuting, contractor personnel must respond to any inquiries from the COR or designated government official within 2 hours. In the event the contractor personnel are unable to log onto their laptop due to VPN or CAC issues, the contractor employee shall either take leave following company policies, or report to an alternate location where meaningful work can be accomplished. The contractor may not charge the Government for work not performed or travel time a contractor employee may require locating a suitable alternative location.

Teleworking arrangements may be revoked by the Contracting Officer through written correspondence; contract personnel will be required to return to work on the next business day.

2.10. Federal Holidays. Federal offices are closed on federal holidays as established by Federal law (5 U.S.C. 6103) and any other holidays declared by executive order. Holidays are documented by year on the Office of Personnel Management website for Federal employees located at: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview. Federal holidays: New Year’s Day, Martin Luther King Jr. Day, Washington’s Birthday, Memorial Day, Juneteenth, Independence Day, Labor Day, Veterans Day, Thanksgiving, and Christmas.

2.11. Facility Closures. The Government will notify the Contractor of anticipated closure of the facility, (i.e., training, holidays, administrative leave granted to the entire staff, or other closure https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=Overview

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

Define core hours 0900-1500

Ladson, Rosanna CTR (USA) Completed by COR

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

Recommend listing the holidays in the event the site is no longer available

U.S. Federal Holidays added.

including down days) five (5) business days in advance or as soon as possible. A down day is a day that the United States Air Force (USAF) leadership designates as a minimal manning/liberal leave day. The employee may take leave following their company’s policies or work from an alternate location. In the event of unplanned closure of the facility due to natural disasters, military emergency or severe weather, the Government will notify the Contractor in the same manner as the Government notifies Joint Base San Antonio area civilian personnel.

2.12. Conduct of Contractor Personnel.

2.12.1. Reference FAR 3.1002(a) The CO or designated Government representative may require Contractor personnel working under this contract be removed from the job site. Removal from the job site or dismissal from the premises shall not relieve the Contractor of the contract requirements.

2.12.2. Contractor personnel shall observe Government facility parking, safety and traffic regulations that apply to all facility employees.

2.12.3. Alcoholic beverages on the job are prohibited.

2.12.4. There shall be no loud, profane or abusive language used on the job.

2.12.5. Contractor personnel shall present a neat well-groomed appearance. Neat, clean, business casual or business attire clothing shall be worn.

2.13. Controlled Unclassified Information (CUI).

2.13.1. CUI is Government created or owned UNCLASSIFIED information that must be safeguarded from unauthorized disclosure.

2.13.2. Information requiring specific security measures indexed under one system across the Federal Government DoD Instruction 5200.48, “Controlled Unclassified Information,” established DoD CUI policy on March 6, 2020.

2.13.3. All information produced as a result of contract performance shall be reviewed prior to dissemination to determine if CUI is identified, and if so refer to DoDI 5200.48 for additional instructions regarding designation, handling, and decontrolling of CUI (including CUI identification, sharing, marking, safeguarding, storage, dissemination, destruction, and records management).

2.14. Personnel Staffing:

2.14.1. The Contractor shall accomplish, at a minimum, the following personnel staffing performance management outcomes:

2.14.1.1. Ensure positions are filled 50% and are present for duty within 10 business days after the start of the POP in the contract. Ensure 100% of positions are filled within 30 business days from the start of the POP.

2.14.1.2. Ensure continuation of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that impact to the Government is minimal and position vacancies do not exceed 30 business days. In instances where the Contractor projects vacancies exceeding 30 business days, the Contractor shall promptly provide a notification to the CO/COR within 10 business days of any projected vacancies exceeding 30 business days. In order for man-hours to be billed on this requirement deliverable services must have been performed in direct support of a requirement in the PWS. The Contractors shall maintain an overall filled rate of 85%, averaged across any given 3-month period.

2.14.1.3. The substitute/replacement personnel shall begin work immediately after departure of the incumbent personnel, or no later than 30 business days after the notification to COR.

2.14.1.4. Provide a stable workforce with less than 30% turnover across all contracted positions.

A turnover is recorded when a worker leaves a position for any reason and the Government still has a requirement for that position.

3. CONTRACT REQUIREMENTS

3.1. Project Management, Functional and Technical Tasks: This tasking is for engineering support, application sustainment, integration support, planning, release management, user training and reporting.

3.1.1. Project Management, Functional and Technical Analysis. The Contractor shall work closely with the AFOMIS COR, Chief Technology Officer, and Portfolio Manager to ensure that

a) the Government’s requirements are met, b) on schedule, and c) within budget and deliver a Project Management Plan (CDRL) A005 that shall identify the Contractor’s processes and procedures. The plan also contains the relevant information defined by Institute of Electrical and Electronics Engineers (IEEE)/Electronic Industries Alliance (EIA) Std. 12207.1, section 6.11 and supports the lifecycle characteristics from Life Cycle Data objectives as cited in IEEE/EIA Std.

12207.0, Support all AFMRA/SG3I (AFMED’SG6X) Stakeholders such as: ) AFOMIS Program Office (Defense Health Headquarters (DHHQ), Falls Church, VA/Hansen Hall, San Antonio, TX), ACC/SGX (Langley AFB, VA) AFCENT SG Chief Information Officer (CIO) (Shaw AFB, SC), ACC/SGX (Langley AFB, VA), Air Mobility Command (AMC) SG CIO (Scott AFB, IL), Air Force Special Operations Command (AFSOC) CIO (Hurlburt Field, FL) according to the requirements of this task.

3.1.2. Assist the AFMRA/SG3I in reviewing, recommending and developing policies, procedures and system requirements for the JOMIS PMO as they relate to AFOMIS, Manpower and Equipment Force Packaging Systems (MEFPAKs), and all COCOMs mission requirements.

3.1.3. Research and analyze technical and management information and data, costs, performance trends, and program/project progress.

3.1.4. Track and report on progress, milestones, open issues, and action items, in the Monthly Status Report (CDRL) A003.

3.1.5. Identify deficiencies and recommendations for their remediation. The Project Manager/Subject Matter Expert (SME) shall develop strategies; resolve issues and concerns; and ensure that the requirements of this PWS are met.

3.1.6. Meeting, Working Group, User Engagement Support.

3.1.6.1. Assist AFOMIS stakeholders in preparing for analysis, briefings, interviews, conferences and other JOMIS meetings.

3.1.6.2. Develop and maintain briefings and presentations.

3.1.6.3. Develop, prepare, distribute and maintain meeting agendas and record and track action items to completion.

3.1.6.4. Attend JOMIS support meetings and provide technical, engineering, functional, and administrative support at those meetings, as required.

3.1.6.5. Provide demonstrations and technology briefings for leadership and training purposes.

3.1.6.6. Develop, prepare, distribute and maintain notes, attendance lists, reports, and recommendations.

Ladson, Rosanna CTR (USA) Per Justin Ashley’s comment:

Suggest looking at this percentage. Does 95% allow for even one departure? Might be better to consider 85%-90%.

**Ed, please address this comment**

I Agree . I also think 20 days is very aggressive for finding qualified replacements.

3.1.7. Technical Support: Engineering, Operations, System Administrator, Developer, NOSC Support.

3.1.7.1. This task provides the MEDXS system implementation, sustainment, testing, integration, configuration management, and release management services. This includes pre-deployment testing, reach back development, configuration management, development of remote updates, on call support, and the development and maintenance of automated testing capabilities at several locations. As updates of MEDXS capabilities are developed, all engineering integration work must be supported in preparation for enterprise deployment. The engineering and integration requirements are dynamic, can support secret missions, and have a high degree of variability depending upon evolving cybersecurity requirements. Given the complexity of these requirements, a primary objective of the Engineering and Integration Support task is to ensure the MEDXS capability functions as expected for end users.

3.1.7.2. Configuration Management.

3.1.7.3. Utilize a configuration management (CM) process to identify, document, and verify the functional, performance, and physical characteristics of MEDXS capabilities, TMIP-AF software and future Health Care Delivery (HCD) Systems, to control releases from the JOMIS PMO, and to track actual configurations of the AFOMIS IM/IT portfolio as it is modernized and integrated with components and accessory software.

3.1.7.4. Accumulate, update, file, store, retrieve and maintain MEDXS Application, TMIP-AF and HCD software details.

3.1.7.5. Identify, analyze, assess, and document CM requirements for software, hardware, infrastructure and all documentation as it relates to the support of MEDXS, TMIP-AF and HCD systems.

3.1.7.6. Develop, prepare and maintain CM methods, policies, processes and procedures.

3.1.7.7. Develop, review and/or maintain MEDXS, TMIP-AF and HCD CM Plans.

3.1.7.8. Develop, review and/or maintain Functional, Physical, and Allocated unique configuration baselines of MEDXS capabilities and TMIP-AF software.

3.1.7.9. Perform configuration audits of MEDXS capability and TMIP-AF software baselines.

The Contractor shall define MEDXS capability and TMIP-AF Software Configuration Items (CIs).

3.1.8. System Engineering and Integration.

3.1.8.1. Support the MEDXS enterprise hosting environment.

3.1.8.2. Support System Administration, security certification and other requirements. The AFMED CMIO requires continued support including system engineers for remote support of MEDXS capability.

3.1.8.3. Establish and operate a OpMed Integrated Test Environment (ITE) within the MEDXS architecture, for testing system updates prior to deployment of software to the operational environment. A deep understanding and practical experience with OpMed IM/IT operating systems and testing is required.

3.1.9. MEDXS Operations Support.

3.1.9.1. Install, scan, report on and administer MEDXS software.

3.1.9.2. Conduct audits, transaction logging and recovery.

3.1.9.3. Analyze MEDXS software trouble reports.

3.1.9.4. Troubleshoot MEDXS software problems in all environments.

3.1.9.5. Provide MEDXS software maintenance support services.

3.1.9.6. Provide functional and technical expertise for the sustainment and maintenance of the MEDXS portal (https://www.medxs.af.mil/public/en/). The MEDXS web portal hosts multiple document libraries, web-based applications, and provides the Waiver Management System for deploying AF personnel:

3.1.9.7. Perform system administration services for the MEDXS portal.

3.1.9.8. Perform the integration and testing of patches and software updates.

3.1.9.9. Report the results of integration and testing of patches and software updates.

3.1.9.10. Monitor and maintain the associated software licensing.

3.1.9.11. Conduct quarterly scans.

3.1.9.12. Integrate software patches.

3.1.9.13. Maintain the DIACAP/RMF documentation for quarterly/annual reviews of the MEDXS Authority to Operate (ATO) and Authority to Connect (ATC).

3.1.10. AFOMIS IM/IT Systems Sustainment.

3.1.10.1. Expertise is required to directly manage and support AFOMIS Program office.

3.1.10.2. Provide AFOMIS with expertise in TMIP and JOMIS HCD deployment, training and sustainment for the AFCENT Office of the Surgeon General (SG).

3.1.10.3. Develop, review and/or maintain correspondence, theater posture plans, program plans, schedules and requirements.

3.1.10.4. Research and analyze technical and management information and data, costs, performance trends, and program/project progress.

3.1.10.5. Track and report on progress, milestones, open issues, and action items, in the Monthly Status Report (CDRL) A003.

3.1.10.6. Identify deficiencies and recommendations for their remediation.

3.1.10.7. Develop strategies, resolve issues and concerns, and ensure that the requirements of this PWS are met.

3.1.10.8. Support AFOMIS by coordinating with the Air Force Medical Command (AFMEDCOM) Medical Systems office leveraging resources, policies and programs in order to best support theater operations and schedule system upgrades in the Monthly Status Report

(CDRL) A003.

3.1.10.9. Provide AFOMIS and AFCENT SG Office updates to ensure the garrison and theater programs are synchronized to the extent necessary/possible.

3.1.11. Information Management and Training.

3.1.11.1. This task shall include IM support for the development of computer based or remote training materials with a continuous focus on documenting AFOMIS OpMed IM/IT business processes in the areas of reporting, business process improvement and clinical policy establishment.

3.1.11.2. Information managers shall be expected to support improved AFOMIS OpMed IM/IT business processes and subsequently produce detailed task inputs and outputs based upon extensive practical experience in the AFOMIS OpMed IM/IT domain.

3.1.11.3. Develop and maintain AFOMIS OpMed IM/IT training and information management requirements.

3.1.11.4. Provide technical and engineering training support plans that include quality and business process improvements.

3.1.11.5. Document and implement MEDXS training.

3.1.11.6. Attend training meetings and reviews of training materials.

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

list

Ladson, Rosanna CTR (USA) Added to CDRL list

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

list

Ladson, Rosanna CTR (USA) Ed, is this supposed to be a CDRL? And if so, what kind of reports are you receiving for this CDRL? (Ex: Presentation report? Material report? Travel report?) Also, is there a specific timeframe that these reports need to be submitted by?

The Upgrade Schedule is a living document, that is dynamic based on needs and priorities of AFCENT sites. Thes schedule itself is maintained by the PM and team, the latest schedule updates and projections should be included in the monthly status report

3.1.11.7. Provide component support and training in the areas rapidly proliferating technologies as required.

3.1.12. AFOMIS Software and Engineering Implementation Support.

3.1.12.1. Software engineering includes the design, development, and documentation of software to support MEDXS application requirements.

3.1.12.2. Define a software development approach appropriate for the computer software effort to be performed under each task.

3.1.12.3. Document the approach in a Software Development Plan (SDP) (CDRL) A006 NLT 2 business days after request.

3.1.12.4. Follow this SDP for all computer software to be developed or maintained under this effort.

3.1.12.5. Develop one (1) SDP to support the unique task order software requirements. Ensure the SDP meets the criteria specified in ISO/IEC/IEEE 12207:2017 and the PWS tasking.

3.1.12.6. Provide systems engineering support of the AFOMIS OpMed IM/IT application suite requirements, programs, and projects.

3.1.12.7. Engineering expertise to analyze system concept, system design, and interoperability, and provide recommendations for optimization including enterprise system engineering and Agile development support.

3.1.12.8. Provide software sustainment and modernization of Medical Expeditionary Systems

(MEDX).

3.1.12.9. This task requires end-to-end product from requirements elicitation through product fielding and sustainment.

3.1.12.10. Follow best practices and Defense Acquisition University (DAU) Software Engineering Life Cycle.

3.1.12.11. Assure software meets documented requirements.

3.1.12.12. Assure the software works as designed with zero (0) Priority 1 or 2 defects and an acceptable workaround for Priority 3 defects.

3.1.12.13. Integrate and validate commercial off-the-shelf (COTS)/Government off-the-shelf (GOTS) software products, methods, procedures, and decision support tools in order to enable system implementation.

3.1.12.14. Perform system engineering services for requirements including engineering, design engineering, technical studies and evaluations, prototype development, application design, configuration, development, engineering and technical documentation, technology refreshment, and technology demonstration and transition.

3.1.12.15. Provide software and engineering support for AFOMIS OpMed IM/IT installations globally.

3.1.12.16. Transport equipment and/or material to and from installation sites as required in support of this task.

3.1.12.17. Provide material and supplies as required to complete the implementation for technical, functional, and integration support.

3.1.12.18. Collect data and assess installation status through trouble reports and user feedback collation.

3.1.12.19. Conduct analysis of the installation process and its effectiveness as part of COCOM requirements and facilitate Stakeholder inspection of installation progress as directed.

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

list

Added to CDRL list

3.1.12.20. Recommend solutions for resolving any documented technical, functional or integration deficiencies as a result of such inspections.

3.1.13. AFOMIS OpMed IM/IT Software Operations Support.

3.1.13.1. Install, scan, report on and administer AFOMIS OpMed IM/IT software.

3.1.13.2. Conduct audits, transaction logging and recovery.

3.1.13.3. Analyze AFOMIS OpMed IM/IT software trouble reports.

3.1.13.4. Troubleshoot AFOMIS OpMed IM/IT software problems in all environments. Provide AFOMIS OpMed IM/IT software maintenance support services. AFOMIS OpMed IM/IT expertise is required to directly manage and support both the AFCENT/SG CIO and AFOMIS Program Office with the AFOMIS OpMed IM/IT Software Operations Task.

3.1.13.5. Conduct, assess, and deliver site surveys at different sites to determine the sites readiness for software implementation and execute upgrades and installations.

3.1.13.6. Brief site leadership and coordinate deployment plans, installation schedules or the implementation schedule.

3.1.13.7. Complete pre- and post- installation testing to include software integration, configuration, and IA testing.

3.1.13.8. Provide data and advice concerning Air Force training programs in Garrison.

3.1.13.9. Maintain configuration management and status over all installations in theater, and

CONUS/OCONUS.

3.1.13.10. Complete various software upgrades to all sites in theater, and CONUS/OCONUS.

3.1.13.11. Provide functional and systems administration training for personnel assigned to sites in receipt of software in theater and CONUS/OCONUS and develop/tailor training curriculum as appropriate for the install in theater, and CONUS/OCONUS environments.

3.1.13.12. Document lessons learned for future installations, training and Concept of Operations (CONOPS) in theater and CONUS/OCONUS.

3.1.14. Field Services, Systems Administration and Mobile Training.

3.1.14.1. This task encompasses all deployed software and includes information management services in the areas of quality improvement planning and business process improvement. The overarching systems strategy for operational readiness IM/IT training is to embed systems training into the organic readiness training programs.

3.1.14.2. Support improved business processes and subsequently produce detailed task inputs and outputs based upon a deep experience foundation in the systems domain.

3.1.15. Logistics Support and Material Movement.

3.1.15.1. Provide logistics support that includes material tracking, receiving, shipping and handling, inventory and storage management, and procurement of hardware and software.

Logistics support includes travel to support integration, test, training, or fielding events.

3.1.15.2. Maintain a log of all material transactions and acceptance records using a Configuration Management Database.

3.1.15.3. Monitor procurement of software licenses and warranties that have not been covered by the Program Office or a DoD Enterprise License.

3.1.15.4. Facilitate and coordinate the receipt and acceptance of systems hardware and software with the receiving command/unit and, in the event of hardware-related issues, shall locate warranty information and coordinate shipment for repair or replacement.

3.1.16. Material Tracking.

3.1.16.1. Provide the appropriate shipping documents (DD-1149), receipts, or tracking numbers to the receiving command/unit to assist with material acceptance and the induction of the material into the command’s property accounts.

3.1.16.2. Ensure all systems assets are securely packaged and prepared for shipment to the receiving command/unit.

3.1.16.3. Logistician shall employ logistics management tools available to monitor material shipments, weight of shipments, and cost of shipments.

3.1.17. Inventory Management.

3.1.17.1. Perform monthly 100% inventory on Government Furnished Property (GFP) and Contractor Acquired Property (CAP). Inventory findings shall be reported on a monthly basis to the AFOMIS COR in the Government Furnished Property (CDRL) A007.

3.1.18. Warranty Management.

3.1.18.1. Serve as the warranty manager by tracking the applicable government acceptance dates/receipt dates against the serial number of equipment or the lowest replaceable unit (LRU) of a system. If no compatible Government database to maintain and track warranty life spans for the GFP and/or CAP under task order, the contractor shall internally track items by task order, serial numbers, and the information shall be updated monthly to identify the time left on the original warranty. Create, maintain and provide the government a copy of the warranty information on a monthly basis in the Warranty Matrix Report (CDRL) A008.

3.1.19. Acquisition of Commercial Software Products, Hardware, and Related Services.

Contractors recommending or purchasing commercial software products, hardware, and related services that support AFOMIS programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoD policies.

3.1.20. Cybersecurity Workforce (CSWF) Designation.

3.1.20.1. In accordance with DFARS 252.239-7001 and DoD 8570.01-M, the contractor shall identify cybersecurity personnel, also known as CSWF and Cyber IT workforce personnel. The contractor shall develop, maintain, and submit a monthly CSWF Report (CDRL A009) identifying CSWF individuals who are IA trained and certified. Utilizing the format provided in Attachment 1 of Exhibit A, the prime contractor shall be responsible for collecting, integrating, and reporting all subcontractor personnel. See applicable DD Form 1423 for additional reporting details and distribution instructions. Although the minimum frequency of reporting is monthly, the COR can require additional updates at any time.

3.1.20.2. Verify with the COR or other Government representative the proper labor category CSWF designation and certification requirements. The primary point of contact (POC) for all related CSWF questions is the Command CSWF Program Manager (PM) in the office of the NIWC Atlantic Information Systems Security Manager (ISSM).

3.2. Minimum Qualifications:

3.2.1. Project managers shall have 10 years of experience in managing the development and sustainment of the following capabilities: medical waivers workflow systems and medical analytics dashboards in an enterprise environment; integrated IM/IT testing capability in physical and virtual environments; and on-site and remote medical operations support for TMIP systems at deployed locations.

3.2.2. System engineers shall have 10 years of experience in the Implementation, configuration and sustainment of the following capabilities: TMIP-J applications, USAF standard server and

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

CDRL should be listed

Ladson, Rosanna CTR (USA) Added to CDRL list

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

CDRL should be listed

Ladson, Rosanna CTR (USA) Added to CDRL list

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

Labor category?

COR updated minimum qualifications.

workstation baseline images, : medical waivers workflow systems and medical analytics dashboards in an enterprise environment; integrated IM/IT testing capability in physical and virtual environments.

3.2.3. System administrators shall have 5 years of experience in implementing and maintaining TMIP-J applications, USAF standard server and workstation baseline images and/or enterprise workflow and data analytics applications.

3.2.4. NOSC support personnel will have 5 years of experience providing network administration and remote application support for TMIP or similar operational systems at deployed locations.

3.2.5. Information managers shall have 5 years of experience in providing operations support for the Air Force deployed military healthcare domain and have an ability to quickly adapt to new applications and capabilities in order to successfully support complex health force protection domains. Information managers must have experience in theater continuity of care processes combined with the latest AFOMIS OpMed IM/IT technologies to effectively support this business area.

3.2.6. The AFOMIS Software and Engineering Implementation Support shall utilize HAF/A6 approved baselines, JOMIS or AFOMIS approved software applications and CSWF credentialed computer personnel.

3.2.7. The Data Base Administrator shall have 10 years of experience configuring and maintaining Oracle, SQL and other databases in cloud-based, web-based, Windows server-based and Windows client applications.

3.3. Security Requirements. (For Unclassified Contracts)

3.3.1. Personnel Clearance. A Contractor’s “Facility Clearance” is required in accordance with DoD 5220.22-M, Incorporating Change 2_May 18, 2016, National Industrial Security Program Operating Manual. Contractor must have an active Facility Clearance at the time of proposal and maintain it throughout the contract’s period of performance. The Government will not pay for nor sponsor any Contractor's attempt to obtain a Facility Clearance. The Contractor’s Facility Security Officer (FSO) is responsible for ensuring that all Contractor personnel assigned to this contract have the appropriate clearance as stated in this PWS. The Contractor shall request personnel security clearances, at the company’s expense, for employees requiring a Tier 3 (T3) clearance (the ISSO and ISSE) within 15 business days after receiving a facility clearance or, if the Contractor is already cleared, within 15 business days after service award. Due to costs involved with security investigations, requests for personnel security clearances shall be kept to the minimum amount employees are required to perform contract requirements.

3.3.2. List of Contractor Personnel. The Contractor shall maintain a current listing of Contractor Personnel. The list shall include Contractor Personnel’s name, social security number, and level of security clearance. The list shall be validated and signed by the company FSO and provided to the CO and Information Protection Office prior to the service start date.

Updated listings shall be provided when Contractor personnel’s status or information changes. A Visit Request for all Contractor personnel with security clearances is required to be sent through the Defense Information for Security (DISS) and must be updated at least annually. The Contractor shall notify the Information Protection Office at each operating location 30 business days before on-base performance of the service. The notification shall include.

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

Requires a DD254

Ladson, Rosanna CTR (USA) DD254 currently with COR to complete with Security Team.

LOPEZ, KRISTI J CIV USAF AFMC AFICC/773 ESS/PKM

TASS/ ICAM information for Contractors to get CAC cards/do they require installation access?

Contractors will require CACs for base access and digital access to various DoD online resources

3.3.2.1. Name, address, and telephone number of the company key management representatives. The contract number and contracting agency.

3.3.2.2. The highest level of classified information to which personnel require access.

3.3.2.3. The location(s) of service performance and future performance, if known.

3.3.2.4. The date service performance begins.

3.3.2.5. Any change to information previously provided under this paragraph.

3.3.3. Security Requirements for Contractor Personnel Requiring Access to Classified Information. Contractor personnel shall require view access to and/or be involved in discussions concerning classified information. A contractor’s “Facility Clearance” is required in accordance with DoD 5220.22-M Incorporating Change 2_May 18, 2016, National Industrial Security Program Operating Manual. Contractor must have an active Facility Clearance at the time of proposal. The Government will not pay for nor sponsor any Contractor's attempt to obtain a Facility Clearance. The Contractor’s FSO is responsible for ensuring that all Contractor personnel assigned to this contract have the appropriate clearance as stated in this PWS. The Contractor shall be responsible for any and all costs associated with security clearances. The Contractor shall provide personnel with the required clearance at the time of award.

3.3.4. A DoD Contract Security Classification Specifications T3 is required.

3.3.5. Contractor personnel requiring a T3 Clearance must be able to work in an environment applicable to classified and unclassified DoD information systems. These Contractor personnel shall access and analyze Controlled Unclassified Information (CUI) and OPSEC required to execute the responsibilities of this position. These Contractor personnel shall have access and analyze to CUI and OPSEC required to execute the responsibilities of this position. This designator is based on the potential for an individual assigned to this position to adversely impact DoD missions or functions. The position categories on this contract include Limited Privileged and Non-Privileged, as defined in DoDM 5200.2 Procedures For The DoD Personnel Security Program (PSP). Investigative requirements for each category vary. Tier 1(T1) = Non-sensitive.

Non-Sensitive positions are those which include mostly low risk, non-sensitive, and non-national security program responsibilities. T3 = Non-critical sensitive (Secret). National Security positions are those in which there is a need for a security clearance to access classified, national security information.

3.3.6. Visitor Group Security Agreement (VGSA): The Contractor shall enter a long- term VGSA if service performance is on base. This agreement shall outline how the Contractor integrates security requirements for service operations with the AF to ensure effective and economical operation on the installation. The agreement shall include:

3.3.6.1. Security support provided by the AF to the Contractor, shall include storage containers for classified information or material, use of base destruction facilities, classified reproduction facilities, use of base classified mail services, security badging, base visitor control, investigation of security incidents, base traffic regulations and the use of security forms and conducting inspections required by DoDM 5220.22 Volume 2, National Industrial Security Program:

Industrial Security Procedures For Government Activities, Air Force Policy Directive 16-14, Security Enterprise Governance, and Air Force Instruction 16-1406, Air Force Industrial Security Program.

3.3.6.2. Security support requiring joint AF and Contractor coordination includes packaging classified information, mailing and receiving classified materials, implementing emergency procedures for protection of classified information, security checks and internal security controls for protection of classified material and high-value pilferable property.

3.3.6.3. On base, the long-term VGSA may take the place of a Standard Practice Procedure.

3.3.7. Pass and Identification Items: The Contractor shall ensure the following pass and identification items required for service performance are obtained for personnel.

3.3.7.1. Installation Access Pass Defense Biometric Identification System (DBIDS), Visitor/Vehicle Pass (DoDM5200.08V3_AFMAN31-101V3 (FOUO)), used for contracts for less than six months to include one-day visits (i.e., warranty work).

3.3.7.2. Installation Access Card DBIDS (DoDM5200.08V3_AFMAN31-101V3 (FOUO)), used for contracts for six (6) months or more.

3.3.7.3. DoD CAC, (AFI 36-3026V2), used for contracts for more than six (6) months and requirement exists for access to the Government computer systems and software. CAC applications are accomplished by Trusted Agents via the Trusted Agent Sponsorship System.

3.3.8. Suitability Investigations. Contractor personnel not requiring privileged IT access and/or access to classified shall successfully complete, as a minimum, a Tier 1, before operating Government…