draft pws tops om engineering_30 june 2022v2 (1).pdf

TOPS O&M Engineering Support Services

PERFORMANCE WORK STATEMENT

Performance Work Statement LIS (TOPS) O&M Engineering Support Services

30 June 2022

Prepared by Logistics Information Systems (LIS) 441 1st Street

Fort Lee., VA 23831

Contents

1. PURPOSE

2. BACKGROUND

3. SCOPE

4. PLACE OF PERFORMANCE

5. PERIOD OF PERFORMANCE

6. GENERAL

7. GENERAL REQUIREMENTS

7.1 MAINTAIN AND ENHANCE TOPS

7.2 CUSTOMER SUPPORT

7.3 SOFTWARE MODIFICATIONS

7.4 MAINTAIN DOCUMENTATION

7.5 BASELINE INTEGRITY

7.6 INTEGRATION ACTIVITIES

7.7 ONSITE SUPPORT

7.8 APPTRICITY LICENSE MAINTENANCE

8. MANAGEMENT

8.1 MEETINGS

8.2 IN-PROGRESS REVIEW (IPR)

8.3 WORKING GROUPS (WG) / INTEGRATED PRODUCT TEAMS (IPT) / TECHNICAL

EXCHANGE MEETINGS (TEM)

8.4 STRATEGIC MANAGEMENT MEETING

9. TECHNICAL

9.1 APPLICATION SOFTWARE MAINTENANCE/ENHANCEMENT

9.2 TEST AND EVALUATION

9.3 REQUIREMENTS PROCESS

10. KEY POSITIONS

11. SPECIAL PROJECTS

12. OTHER DIRECT COSTS

13. GOVERNMENT FURNISHED EQUIPMENT (GFE) / GOVERNMENT

FURNISHED PROPERTY (GFP)

14. QUALITY ASSURANCE

14.1 QUALITY CONTROL GATES

14.2 QUALITY DOCUMENTATION

14.3 REVIEWS AND AUDITS

14.4 CONDUCT QUALITY AUDITS

14.5 UNIT AND CODE INSPECTION

15. CONFIGURATION MANAGEMENT (CM)

15.1 CM MONITORING

16. DELIVERABLES

16.1 WEEKLY STATUS REPORTS

16.2 TEST CASES AND RESULTS

16.3 RELEASE NOTES

16.4 INTEGRATED MASTER SCHEDULE

16.5 SOFTWARE DELIVERY

16.6 SOFTWARE AND DATA RIGHTS

16.7 SCHEDULE, DATA ITEMS, OTHER DELIVERABLES

17. PERFORMANCE CRITERIA

17.1 EVALUATION RATINGS

17.2 PERFORMANCE REQUIREMENTS

18. CONTRACT ADMINISTRATION AND MANAGEMENT

18.1 CONTRACT MANAGEMENT

18.2 CONTRACT ADMINISTRATION

18.3 PERSONNEL QUALIFICATIONS

18.4 PERSONNEL SECURITY REQUIREMENTS

18.5 INFORMATION ASSURANCE TRAINING AND CERTIFICATION REQUIREMENTS

18.6 SECURITY

19. TRUSTED ASSOCIATE SPONSORSHIP SYSTEM (TASS)

20. CONTRACTING OFFICER’S REPRESENTATIVE

21. CONTRACTOR MANPOWER REPORTS (CMR)

22. CONTRACTOR TRAINING

23. ATTACHMENTS

Table 1. Referenced Publications Table 2. Performance Criteria Table 3. Service Level Agreement Appendix 1. Contract Data Requirements List (CDRL) Appendix 2. Government Furnished Equipment

1. PURPOSE

The Performance Work Statement (PWS) establishes the requirements for Contractor provided services to include, operations, maintenance, technology insertion, and integration support of the Logistics Information Systems (LIS) Theater Operations (TOPS) module to be integrated into the Transportation Coordinators’ – Automated Information for Movement System II (TC-AIMS II). Support of TOPS includes ongoing system enhancement, application’s test, documentation, and operating configuration management of the enterprise. The current configurations in production is version 7.0.x.

The Contractor shall furnish expert labor necessary to support the Government’s requirements for operating and maintaining the TOPS System, Interfaces, and end-users.

Objectives:

The contractor is to ensure the software maintenance and sustainment tasks listed are properly managed in accordance with best industry practices and government regulations.

The Contractor shall cultivate a business environment that encourages continuous and measurable process improvements for TOPS.

The Contractor shall recommend appropriate techniques (e.g. Agile development)

The contractor shall ensure system and project documentation is kept current and in a state that permits hand-off to the government or other entity.

2. BACKGROUND

The current Transportation Coordinators’ – Automated Information for Movements System II (TC-AIMS) is used by transportation agents and deploying units to automate the processes of planning, organizing, coordinating, and controlling deployment, redeployment, and sustainment activities worldwide, in peace as well as during contingencies. It provides a modernized, integrated, and easily deployable Automated Information System (AIS) that supports reengineered functional processes throughout DoD. TC-AIMS II will link all DoD component unit movement and Installation Transportation Office/Traffic Management Office (ITO/TMO) functionality into a consolidated, integrated, easily deployable, transportation management system.

The United States Army’s Logistics Information Systems (LIS) has a diverse mission that requires an automated capability to provide accurate and timely requirements and real-time visibility of movements to support deployment, redeployment, and sustainment of U.S. Forces from within, and to, OCONUS installations and overseas theaters of operations. Theater Operations (TOPS) functionality enables movement control elements to manage and coordinate transportation services during Joint Reception, Staging, Onward Movement, and Integration (JRSOI) and sustainment operations.

3. SCOPE

The scope of this contract will be continuation of the technical and engineering support services supporting the commercial TOPS software modules developed by Apptricity and modified by Apptricity to meet the Government’s requirements. LIS requires Post Production Software Support (PPSS), System Enhancement and Technology Insertion of TOPS in order to sustain an automated capability and to provide accurate and timely requirements and real-time visibility of movements to support deployment, redeployment, and sustainment of U.S. Apptricity maintains the TOPS software by conducting the required maintenance as described by LIS in incremental development packages and integrating the functionality into the existing software modules. Support services covers the upgrades to and maintenance of TOPS, which shall encompass problem fixes, upgrade and enhancements to existing capabilities, and build releases required to support changes to the TOPS applications. Maintenance will be coordinated with the LIS TC-AIMS II Program Management Office (PMO) and will include updates to the appropriate documentation. A software maintenance build will not be considered complete until all identified documentation is delivered and approved by the LIS TC- AIMS II PMO, in accordance with the PWS, Contract Data Requirements Lists (CDRLs), and Technical Instructions (TIs).

4. PLACE OF PERFORMANCE

The LIS program office is currently located in Fort Lee, VA. Meetings between the Contractor’s support team, principal staff, and LIS personnel shall be held at this location. Work shall be performed at the contractor’s facility and designated locations as identified by the Contracting Officer.

5. PERIOD OF PERFORMANCE

Requirement Period of Performance Base Period 02 September 2022 – 01 April 2023 Option Period 1 02 April 2023 – 01 July 2023

6. GENERAL

In line with providing PPSS, the Contractor shall provide expert labor necessary to ensure sustainment and documentation for the management, planning, implementation and regulatory compliance of TOPS. Support services provided under this contract shall include, but are not limited to, Software Enhancement and Maintenance, System Engineering, System Planning, System Analysis, Configuration Management, Enterprise Systems Management, Integration Support, Projects, Systems Engineering and Integration, Software and Hardware Test, and help desk, training input, and database administration, management, migration, and conversion. The work requirements shall also include overarching activities related to project management, quality assurance, technical research and analysis, system documentation, and IT Security.

As required the Contractor shall maintain and enhance the TOPS installer to support the TC-AIMS II integrator, which could include complying and keeping current with the appropriate DoD, Services, and Army architectures, programs, policies, standards and guidelines (e.g., Risk Management Framework for Security, Net-Centric Enterprise Services (NCES), Defense and Information Systems Network (DISN)).

The Contractor shall be responsible for its own overall responsiveness, cost control, adherence to schedules, technical quality of work, management of Contractor team’s efforts and commitment, support equipment and productivity tools and equipment, and to achieving customer satisfaction among TC-AIMS/TOPS Stakeholders.

The contractor shall optimize the various development, operations, and maintenance activities for TOPS system. For purposes of this PWS, the term “development” is defined as configuration and coding activities related to the maintenance of TOPS software including bug fixes, and maintenance activity change requests that are not bug fixes e.g., applying Information Assurance Vulnerability Alert(s) TESTs, patches and minor technical mandates (software updates needed to maintain the TOPS module within the TC-AIMS II system as directed by the government). Anything that expands the performance envelope by adding or modifying software capability will be covered under Special Projects (See Section 11. Special Projects) addressed by LIS through contract modifications, if applicable. The covered software activities include not only problem reports but certain change requests that are maintenance activities. The development and covered activities include in addition to bug fixes, maintenance activity change requests; e.g., applying Information Assurance Vulnerability Alert (IAVAs), patches and minor technical mandates (software updates needed to maintain the TC- AIMS II system as directed by the government. All TOPS source code is subject to HP Fortify/Cast Scans and results will be provided back to Apptricity to enhance source code integrity.

7. GENERAL REQUIREMENTS

The Contractor shall design, develop, test and package systems and software changes as well as provide problem resolutions for the existing TOPS system. The Contractor shall maintain the current baseline of the system and provide software change and problem fixes to these baselines as required. The Contractor shall provide to the Government all developed, modified, or converted source modules, processes, programs, scripts, operating instructions, databases, system files, documentation, test files and test conditions used to develop each approved systems change request.

The Contractor shall provide the methodologies, processes, and capabilities that it proposes to use over the life of the contract. (IAW CDRL A005, Quality Assurance Plan) Contractors are encouraged to clearly explain its processes and tools, methods to assure quality, ability to leverage its existing organization and infrastructure (not customize for LIS), and to identify any parameters, limitations, or constraints associated with delivering this functionality.

The proposed methodologies, processes and capabilities should reflect proven-practices and tools, knowledge of Transportation Information Systems, Best Management Practices around Hardware and Software support, Client Relationship Management, Knowledge Management, and Techniques for Continuous Improvement.

The contractor, when required, shall support the TC-AIMS II integrator in the following:

Configuration Management Capacity and Availability Management IT Service Management Incident Management and Problem Management Integrated Project Management Measurement and Analysis Project Planning Resource Management Risk Management Quality Assurance and Testing

The methodologies, processes and capabilities should reflect proven-practices and tools, knowledge of Transportation Information Systems, Best Management Practices around Hardware and Software support, Client Relationship Management, Knowledge Management, and Techniques for Continuous Improvement.

7.1 Maintain and Enhance TOPS

Maintain and Enhance the TOPS application through the correction of software and system defects identified in test readiness reviews, new requirements, change requests, problem reports, trouble tickets, and integrating the functionality into the existing TC- AIMS II system.

7.1.1. The contractor shall meet Global Information Grid (GIG), Internet Protocol version 6 (IPv6), Net-Centric Enterprise Services (NCES), Defense Reform Initiative Directive 54 (DRID-54), Army Knowledge Management, Public Key Infrastructure (PKI), Common Operating Environment, and all applicable current and emerging DoD and Army mandates. The contractor shall identify software maintenance activities that arise due to emerging DoD and Army mandates, including new development efforts or Special Projects which would require a contract modification.

7.1.2. The contractor shall meet DOD information assurance requirements for systems that process “secret,” “sensitive but unclassified” (SBU), and Privacy Act information.

7.1.3. The contractor shall meet the DOD requirement for CAC enabled user login for the TOPS products. The contractor shall identify new software maintenance activities that may be necessary to meet DOD requirement for CAC enabled user login, including new development efforts or Special Projects which would require a contract modification.

7.1.4. The contractor shall maintain all interfaces, to include both interfaces previously developed by the contractor and interfaces developed pursuant to a special project, between Theater Operations (TOPS) and other TC-AIMS II components/modules, as well as development needed to remain compatible with updates to embedded commercial software.

7.1.5. The contractor shall provide all cyber security support for the TOPS environment;

Network certification and accreditation activities will be coordinated with other government agencies by a LIS cyber security professional;

7.1.6. The contractor shall design, develop, test and package systems and software changes to support enterprise configurations and may be necessary to support standalone configurations.

7.1.7. The contractor shall provide IT support as required to assist with the operational management of the TOPS integration environment;

7.1.8. The contractor shall utilize the Government provided AGM/UGM for the contractor hosted test system so that a TOPS production environment is available for support activities;

7.1.9. The contractor shall identify new software maintenance activities that arise due to emerging DoD and privacy requirements, including new development efforts or Special Projects which would require a contract modification.

7.2 Customer Support

LIS is responsible for providing support to users of TOPS application. TOPS users experiencing problems will first contact the LIS Service Desk (ASD)Tier 1 Help Desk, (available 24x7x365). The Tier I Help Desk provides support that includes receipt and logging of all customer trouble tickets, educating customers on known problems and associated workarounds, handling the majority of requests for creating TC-AIMS II accounts, account management support (e.g., reset passwords, unlock of accounts, modifications to accounts), identifying problem trends, and documenting knowledge of problem resolutions.

LIS Service Desk (ASD) Levels of Support (Tier 1is 24/7)

Tier 1 – Account Creation o Password Reset o Account Adjustments o Software Requests o Escalation to Tier 2 support o Assign Ticket Priority

Tier 1 Tickets o Priority 1 is critical – ability to conduct business or service has stopped.

Ex. Network/Server/Database/Application down ASD will immediately assign a ticket to LIS and LIS will notify Contractor.

o Priority 2 is major – Service is seriously degraded but can continue via workarounds or incremental resource for a short period of time before business stops.

ASD will immediately assign a ticket to LIS and LIS will notify Contractor.

o – Priority 3 is medium – Service lost by a single User or small number of

Users affecting significant business functionality.

ASD will attempt to resolve issue Priority 4 is low – A call from a single User or site groups are requesting a new service or clarification ASD will attempt to resolve issue.

The contractor shall provide a single point of contact for technical support for tier 2, 4 and 5 (normal business hours) for LIS

7.3 Software Modifications

The contractor shall submit software corrections to the LIS government-designated configuration management system based on Configuration Control Board (CCB) designated build or patch schedules.

7.4 Maintain Documentation

The contractor shall submit documentation to accompany all software corrections and code submission. Documentation shall identify the software product, build, and version, and the referenced Problem Report(s) (PR) or Change Request(s) (CR) in addition to the Fortify and CAST Scan documentation on all submitted software. The submission shall also include all Design Documents, TOPS Software User Manual (SUM), and TOPS Software Installation Procedures (SIP) updates. (IAW CDRL A010, Configuration Management)

7.5 Baseline Integrity

The contractor shall maintain the current TOPS baseline of the system and provide software change and problem fixes to these baselines as required.

The Contractor shall ensure that the any upgrades or addition of software developed to support TOPS specific requirements under this PWS does not compromise the security posture of the TC-AIMS II system.

7.6 Integration Activities

The Contractor shall provide operations and maintenance support of the TOPS software to support integration with the Enterprise Unit Move application.

7.7 Onsite Support

The contractor will provide onsite support at the TC-AIMS II integration facility to assist the program office with advanced technical and functional skills and expertise to assist operations and maintenance support of the TOPS software and integration support for Enterprise Unit Move application. The following summarizes the contractor technical support activities:

Resolve or route user issues and Help Desk Tickets;

Troubleshoot/diagnose TOPS application issues;

Collaborate with Unit Move support staff on integration and operational issues;

Participate in technical planning meetings with LIS and Unit Move;

Debug/modify TOPS JAVA code;

Provide knowledge of TOPS DB structures, tables, and operations; and Test TOPS software following the application of patches or maintenance The contractor onsite support shall have the following minimum qualifications:

Knowledge of SSL, operation of https, CAC enablement, and web server operation within a DOD environment;

CAC card or ability to quickly obtain a CAC;

Security+ Certification; and

Secret Clearance (or ability to obtain).

7.8 Apptricity License Maintenance

The contractor will provide Apptricity License Maintenance support to TC-AIMS II per the Settlement Agreement executed on October 24, 2013.

Apptricity Standalone Client Device License for TC-AIMS II means a license to the Apptricity System identified by product code APS002 for an unlimited number of user accounts per device and which is utilizable for, but not limited to routine use, production, training, testing, engineering, and/or development software. (Quantity – 150)

TOPS Enterprise Server License for TC-AIMS II means a license to the Apptricity System identified by product code APM026 for up to 25,000 connected network client users per license and which is utilizable for, but not limited to routine use, production, training, testing, engineering, and/or development software. (Quantity – 5)

8. MANAGEMENT

The Contractor shall be responsible for Management of the Contract and any associated tasks, Projects, and Performance. Below is a list of some of the common management tasks expected to be performed on this contract:

Initial response to LIS on program issues and problems associated with the execution of the contract during core hours within 60 minutes after receipt of a verbal or written request;

Support by means of Electronic Commerce/Electronic Document Interchange (EC/EDI), web access for Contractor-provided information and data;

Maintain accurate records;

Provide information to various Services and Agencies with the approval of LIS;

Develop and execute a management plan that incorporates configuration and risk management, and provide an approved Management Plan;

Report Contractor Manpower Information in accordance with the paragraph entitled “Contractor Manpower Reporting” in this PWS; and Develop and maintain a program management process documented in a formal program management plan.

8.1 Meetings

The Contractor shall be required to attend meetings and coordinate with Government personnel stationed in and near Fort Lee, Virginia, on a regular basis (historically weekly). Often, attendance for face-to-face meetings will be required within 45 minutes of meeting notification. The In-Progress Reviews (IPR) slides shall be submitted to COR three (3) days prior to the reviews. Any other meeting slides shall be provided to the COR one (1) day prior to the meeting. When required, the Contractor shall participate in Technical Exchange Meetings (TEMs) and other working groups established by the Government. The Contractor’s participation in TEMs within the National Capital Region (NCR) including travel to LIS NCR facilities shall be covered within the Contractor’s overhead (historically monthly). Any long distance travel required will require prior approval from PL/DPL LIS. Below is a list of some of the common tasks expected to be performed on this contract:

Support Ad Hoc Teams;

Technical Working Group (TWG) support;

Schedule project reviews, internal seminars and conferences, and the presentation of the Contractor’s vision for creating efficiencies and inserting new technologies;

Conduct IPR at Government site;

Provide weekly status updates

8.2 In-Progress Review (IPR)

In accordance with CDRL A002, Integrated Progress Review (IPR), the Contractor shall include in each review, a current organizational chart with the names and telephone numbers of all key personnel, and highlight any key personnel changes. The key positions for this Contract are: Project Manager. The Contractor shall prepare and coordinate with the COR, an agenda for all IPRs at least five (5) workdays before a scheduled IPR. The Contractor shall provide the briefing charts to the COR electronically three (3) workdays prior to the day of the IPR. The Contractor shall prepare and coordinate minutes of the IPRs with LIS no later than 48 hours after the IPR. Coordination shall be accomplished through electronic mail. Below is a list of the minimum slides required for the IPR:

a) Status of configuration and risk management activities;

b) Status of Special Projects;

c) Significant trends (e.g., system reliability, problems, and recommended solutions);

d) Minutes from the previous IPR;

e) Activities determined to be of importance to the Government, such as unanticipated problems, future schedule delays, and high visibility issues identified by the Government;

f) Status of significant program events;

g) Identification of potential risks and proposed risk mitigation strategies1;

h) Customer feedback;

i) List of Meetings conducted with LIS or other Government agencies;

and

j) Reason for any schedule delays.

8.3 Working Groups (WG) / Integrated Product Teams (IPT) / Technical Exchange Meetings (TEM)

The Contractor shall participate with the Government in multiple teams on an as-required basis. IPTs will be composed of representatives from all functional disciplines, working together to identify and resolve issues. IPTs will also make sound and timely decisions, build a successful and balanced program, and make maximum use of timely input from the entire Team, including customers and suppliers. The Contractor shall participate on TEMs as required to support Theater Operations Integration. Unless agreed to by the Government in advance, all Contractor costs incurred by participation in TEMs shall be the sole responsibility of the Contractor.

8.4 Strategic Management Meeting

The Contractor shall meet with the Government to prioritize requirements from the product backlog to align with strategic plan. The Contractor shall conduct a sprint review with the Government to focus on demonstrating what the development team has done.

Periodic sprint reviews meetings review and demonstrate the user stories that the development team completed during the sprint. For the development team to demonstrate the product in the sprint review, it must be complete: Developed, Tested, Integrated, and Documented.

9. TECHNICAL

The Contractor shall be responsible through its performance to address and support the technical aspects of the Contract and associated tasks, projects, and performance.

Technical activities include the coordinated sustainment of the existing applications, enhancement of system to meet new and emerging requirements, and the development of special project requirements to support the LIS and the Government’s transportation management mission. This includes typical software sustainment activities such as application design, development, testing, documentation, and implementation of software releases associated with lifecycle activities. Technical activities address the infrastructural network, hardware, and facility support (as applicable) with full coordination to ensure all levels of information security, reliability, and availability, are met and are in compliance with Government regulatory requirements.

9.1 Application Software Maintenance/Enhancement

The Contractor shall maintain and enhance the existing TOPS application. The contractor shall perform in-depth requirements analysis and decomposition of all requirements by maintaining a liaison with system stakeholders and users. The contractor shall maintain the existing TOPS modules.

9.1.1. Software Updates. The contractor shall develop bug fixes associated with problem reports and software changes associated with maintenance change requests as identified by LIS Configuration Control Board (CCB). The contractor shall utilize the priority and severity rankings as assigned by the LIS CCB to develop schedules.

9.1.2. Database Maintenance. The contractor, when required, shall support the TC- AIMS II integrator in database maintenance activities. These activities shall include performance tuning, incremental software updates, backup and recovery, archiving, control of access permissions and privileges, data security, monitoring disk usage and database performance, reviewing database system logs, problem resolutions, and IAVA compliant patching. The contractor shall perform the database corrections associated with problem reports and maintenance change requests as identified by the CCB and directed by the Government. The contractor shall provide database scripts to perform modifications to the database and resolve problem reports and maintenance change requests as well as to maintain and optimize the database for the system. The contractor shall utilize the priority and severity rankings as assigned by the LIS CCB to develop schedules. Additionally, systems maintenance activities, specifically IAVAs, shall be coordinated with LIS to the TC-AIMS II integration environment. At no time shall database maintenance/backup activities preclude user access to the system.

9.1.3. Software Installation. The contractor shall develop and maintain automated install and de-install capabilities for TOPS that can be used when installing on the enterprise and may be necessary to support standalone configurations. The install/de-install capabilities for TOPS must install/update/de-install the TOPS module from an existing Enterprise TC-AIMS II installation without degradation to the existing TC-AIMS II system other than removal of the TOPS module in the case of de-installation. The contractor shall provide instructions to perform the install update and de-install processes, and the contractor must strictly limit the amount of manual editing of configuration text files required.

9.1.4. Software Documentation. The Contractor shall create and maintain all required technical documentation as well as online help files. This includes, but is not limited to, software design, interface design, system design, Department of Defense Risk Management Framework (RMF) artifacts, system installation instructions, system user manuals, etc. The Contractor shall provide/update bi-weekly, an Integrated Master Schedule (IMS). All documentation shall be updated and validated with each deliverable to ensure accuracy, relevance and format.

9.1.5. Government Acceptance Testing. Technical support is required to support the installation, maintenance, problem resolution of software during Government Acceptance Testing (GAT).

9.2 Test and Evaluation

The contractor shall provide and identify all developed, modified, or converted source modules, processes, programs, scripts, operating instructions, databases, system files, documentation, test files and test conditions used to develop each approved change requests or problem reports.

The Contractor shall be responsible for reviewing Government lab tested and approved interoperability test plans and test results for new products or changes to existing products introduced by Government or 3rd parties into the LIS environment. The Contractor shall inform the government COR of any problems encountered with implementation of new or changed existing products.

9.2.1. The contractor shall assess the incremental improvements in capabilities for each software update/release and employ regression testing (automated and manual) as necessary for each subsequent update/release. The contractor shall ensure that the testing objectives and success criteria of each Test and Evaluation (T&E) event are completed before progressing to the next event. , The contractor shall identify any deficiencies in the software operation and performance within the detailed status report (IAW CDR A003, Weekly Status Report (WSR)).

9.2.2. The contractor shall develop processes and procedures for test documentation and verification activities during product testing.

9.2.3. The contractor shall identify the system changes and develop software test scripts, system installation procedures, testing and maintenance of the software prior to build delivery. A test script/test verifies or identifies if the software change, installation procedures actually work or break something in the code.

9.2.4. The contractor shall coordinate with the LIS Government Acceptance Test Lab Lead (GAT) to verify the following objectives:

9.2.4.1. Identification of the activities required to prepare for and to conduct the product test.

9.2.4.2. Identification of the parties required and responsible for the installation of the product (at a minimum the government will have a representative present during all installation activities).

9.2.4.3. Identification of the environment(s) in which the product will be tested.

9.2.4.4. Identification of the equipment required to conduct the product test.

9.2.5. The Contractor shall conduct component and regression testing for new and current functionality of the TOPS module of the Transportation Coordinators’ – Automated Information for Movement System II (TC-AIMS II) specified in this PWS.

The Contractor shall test and evaluate IAVA, service packs, and patches to servers for compatibility with TC-AIMS II.

9.3 Requirements Process

The development and management of new requirements is the sole responsibility of the LIS CCB. The requirement process begins with the identification of business needs and project objectives. The government will provide the requirements identified by the CCB in the form of PRs and CRs and then captured in Serena Business Manager.

9.3.1. Requirements Management. Requirements Management is the sole responsibility of the Government Requirements team; however the contractor shall maintain a matrix that illustrates traceability between requirements validated through the LIS CCB and the contractor deliveries. The LIS requirements management process involves establishing, protecting, controlling, and maintaining the approved baseline requirements. The contractor shall track and report changes of these baselines throughout the analysis, design, build, and test phases.

9.3.2. Requirements Allocation. The contractor shall provide a Level of Effort (LOE) for the development and implementation of a requirement (s) based on the analysis.

LIS will use this analysis for the allocation of requirement (s) while planning future releases.

9.3.3. Requirements Traceability. The contractor shall provide requirement traceability of the disposition of a requirement throughout the development process: (1) inception activity, (2) corresponding design, (3) code implementation to meet the design and requirements, (4) development of test case(s) necessary for validating the requirement, and (5) implementation. The contractor shall include verification activities and traceability in test plans and test results.

10. KEY POSITIONS

This Section contains information concerning Key personnel resources to successfully perform the work requirements. Minimum levels of experience, expertise and educational requirements are specified below. The Contractor shall provide staff members who meet the minimum skills sets specified below. However, due to the magnitude of effort planned for this PWS, and the specialized technical disciplines involved, the Contractor shall ensure that non-Key Positions proposed adhere to the specialized requirements identified within this PWS. Contractor shall include in each IPR, a current organizational chart that includes the names and rolls of all personnel with any key personnel changes highlighted.

The Contractor shall provide personnel who are:

Qualified, experienced and suitable;

Accountable for overall performance within the scope of their area of responsibility;

Accountable for delivery, operations, and management within the scope of their area of responsibility; and Accountable for contractual and financial matters within the scope of their area of responsibility.

The Contractor must have:

Demonstrated depth and breadth of personnel who can be applied across all of the TOPS Business Processes and functional areas (e.g., O&M, Application Development & Maintenance, etc.); and

Key Personnel who demonstrate an understanding of Federal, DoD, and Army regulations within the scope of their area of responsibility.

The following roles are the suggested minimum personnel who shall be designated as “key”. The Contractor shall propose appropriate labor categories for these positions.

The implication of “suggested” is that the Government does not intend to dictate the composition of the ideal team to perform this PWS.

Project Manager

The key personnel specified are considered to be essential to work performance. For this Contract, Key Personnel shall be assigned for the life of the contract barring circumstances outside the control of the Contractor, (e.g., death, disability, etc.).

At least 30 days prior to diverting any of the specified individuals to other programs or contracts (or as soon as possible, if an individual must be replaced, for example, as a result of leaving the employ of the Contractor), the Contractor shall notify the Contracting Officer and shall submit comprehensive justification for the diversion or replacement request (including proposed substitutions for key personnel) to permit evaluation by the Government of the impact on performance under this Task Order.

The Contractor shall not divert or otherwise replace any key personnel without the written consent of the Contracting Officer. The Government may modify the contract to add or delete key personnel at the request of the Contractor or Government.

Specialized Disciplines – In addition to the personnel requirements set forth in the paragraph below. The Government expects certain specialized experience for this project as further described below. The Government considers the personnel identified below as the minimum requirement for designation as “Key Personnel”.

The specialized experience listed below is desirable. All experience will be evaluated based on relevance to this PWS.

Project Manager – The Contractor shall identify a Project Manager (PM) to serve as the Government’s primary point-of-contact and to provide supervision and guidance for all Contractor personnel assigned to the PWS. The PM is ultimately responsible for the quality and efficiency of the TOPS effort to include both technical issues and business processes. The PM shall be an employee of the prime Contractor. The PM shall assign tasking to Contractor personnel, supervise on-going technical efforts, and manage overall performance. The PM shall be:

Qualified, experienced, and accountable for overall program performance;

Accountable for delivery, key operations, and technical management of the contract;

Accountable for contractual and financial matters of the entire contract;

Demonstrate an understanding of Federal, DoD, and Army regulations within the scope of this requirement;

Supervise the administrative effort required:

o Administer employee relocation and security matters;

o Process appropriate security clearances; and o Provide general administrative support to Contractors

Conduct cost and risk analyses, including Rough Order of Magnitude (ROM) pricing for new (Special Projects), as requested; and

The PM shall understand LIS operational and technical requirements as described in the PWS.

11. SPECIAL PROJECTS

At the option of the Government, the Government may require supplemental special projects outside the technical baseline. Special projects shall not commence without proper authorization to proceed from the Government, and shall require a detailed proposal showing an outline of development activities and Rough Order of Magnitude (ROM) estimates.

A “Special Project” is defined as a directed, funded effort that provides a new or improved service capability in response to an approved Army requirement.

The Contractor shall be responsible for providing all resources (i.e., personnel, partners, Subcontractors, infrastructure, etc.) necessary to manage, monitor, and perform all activities associated with special projects on a Firm Fixed Price basis according to the Government’s requirements.

For each proposed special project, the Contracting Officer will complete a thorough assessment to determine if the project is within the scope of the PWS, or outside the scope of the PWS.

a) If the proposed special project is already a requirement within the scope of the PWS (e.g., the sustainment of existing applications), the proposed activity is enforceable under the existing contract.

b) For purposes of this paragraph, the development of application interfaces that directly interact with TOPS will be considered to be within the scope of the PWS;

however, the contractor will be required to submit a detailed proposal and ROM estimate, and the interface development project will be implemented in a bilateral contract modification.

c) If the proposed special project is for a requirement that is not within the scope of the PWS, the Contracting Officer and contractor shall come to a consensus as to whether the desired support should be provided as a special project. A special project that is not within scope of the PWS, such as a new development effort not included in subparagraph b, above, will also require the contractor to submit a detailed proposal and ROM estimate, and will also be implemented in a bilateral contract modification.

12. OTHER DIRECT COSTS

Other Direct Costs (ODC’s) when approved by the Government and incurred by the Contractor in performance of tasks will be reimbursed by the government. The contractor shall obtain prior approval from the COR for micro purchases (< $3K) and the Contracting Officer approval for all purchases over the micro purchase level. ODC’s include storage, travel, materials, supplies and other supported direct costs. Only actual costs for ODCs that are supported with detail sufficient for the Government to verify that costs are reasonable and in performance of tasks will be reimbursed.

13. GOVERNMENT FURNISHED EQUIPMENT (GFE) / GOVERNMENT FURNISHED

PROPERTY (GFP)

The Government will furnish the necessary hardware to perform the required integration and component testing of TOPS. See Appendix 2. Contractors shall provide their own systems, tools and software necessary to perform administrative and office functions.

Other than GFE, the Contractor shall provide all resources necessary to sustain TOPS operations and maintenance (O&M), practices, service assurance, and management.

The Contractor shall be responsible for providing all resources necessary to provide the full range of activities related to Operations and Maintenance of the TOPS Infrastructure.

14. QUALITY ASSURANCE

14.1 Quality Control Gates

The Contractor shall provide quality control gates starting with the System Design Document, through software development process, which includes processes such as software design, coding, source code control, code reviews, change management, configuration management, and release management.

14.2 Quality Documentation

The Contractor shall provide quality documentation standards specifying form and content for planning, control, and product documentation that provides consistency throughout the product. Ensure design standards by specifying the form and content of the design product in accordance with the rules and methods for translating the software requirements into the software design and for representing it in the design documentation.

14.3 Reviews and Audits

The Contractor shall support Government reviews and audits of all services and support provided under this contract. The Government reserves the right to authorize an Independent Verification and Validation (IV&V) of the Contractor’s procedures, methods, data, equipment, and other services provided at any time during the performance of this contract. At Government’s discretion, registered ANSI/ANSQ Q9000 series suppliers may not be subjected to audit/assessment by Government if they provide the Government with a copy of their registration certification issued by an approved ISO registrar.

14.4 Conduct Quality Audits

Provide product evaluation and process monitoring that assures the software development, control processes described in the project’s plans, and that the project's procedures and standards are followed. Products are monitored for conformance to standards, and processes are monitored for conformance to procedures.

14.5 Unit and Code Inspection

The Contractor shall establish checklist and standards for Unit and Code Inspection and conduct and document compliance. An inspection or walkthrough is a detailed examination of a product on a step-by-step or line-of-code by line-of-code basis to find errors. For inspections and walkthroughs, Contractor assures, at a minimum that the process is properly completed and that needed follow-up is done. The inspection process shall be used to measure compliance to standards.

15. CONFIGURATION MANAGEMENT (CM)

The Contractor will work with LIS Configuration Management to utilize Serena Business Manager as a configuration management tool. Serena Business Manager is a commercial application provided under license to the federal government. The government will provide the Contractor with access and ability to make administrative and configuration changes. Contractor activities include coordinating with the requirements team concerning changes to software features and developing release plans in association with configuration management, and testing activities. The Contractor shall have subject matter expertise in the Serena Business Manager toolset with the expertise to manage, maintain and update the software.

Using MIL HDBK 61A, ISO 12207, EIA 649 guidance, and best commercial practices, the Contractor shall institute and maintain a Configuration Management Plan to ensure engineering and administrative disciplines (which include configuration identification, configuration control, status accounting, and auditing) are implemented for all development activities. The Contractor shall provide a Configuration Management Plan (see CDRL A006, Configuration Management) detailing how it shall identify and maintain the configuration of all work products (to mean baselines as well as other supporting work products); systematically control changes, and maintains the integrity and traceability of all work products throughout their lifecycle. The Contractor shall ensure configuration is identified, reliable, traceable, and repeatable, and that all relationships among work products, versions of work products, as well as auditing and reporting on the changes that are made are implemented throughout the development process. The Contractor designated personnel assures that software Configuration Management (CM) activities are performed in accordance with the Configuration Management Plan (CMP), standards, and procedures.

15.1 CM Monitoring

The CM activities monitored and audited by the Contractor designated key personnel (CM manger) include baseline control, configuration identification, configuration control, configuration status accounting, and configuration authentication. The designated CM manger also monitors and audits the software library. The Contractor CM manager shall assure the following:

The Enterprise baseline are established and consistently maintained for use in subsequent baseline development and version control.

Software configuration identification is consistent and accurate with respect to the numbering or naming of computer programs, software modules, software units, and associated software documents.

Configuration control is maintained such that the software configuration used in critical phases of testing, acceptance, and delivery is compatible with the associated documentation.

Configuration status accounting is performed accurately including the recording and reporting of data reflecting the software's configuration identification, proposed changes to the configuration identification, and the implementation status of approved changes.

The Contractor shall provide traceability of all Change Requests, Problem Reports, and New Requirements through the system lifecycle via a requirement traceability tracking tool.

Software configuration authentication is established by a series of configuration reviews and audits that exhibit the performance required by the software requirements specification and the configuration of the software is accurately reflected in the software design documents.

Software development libraries provide for proper handling of compilable software source code, executable files, documentation, media, and related data in their various forms and versions from the time of their initial approval or acceptance until they have been incorporated into the final media.

In accordance with the LIS CMP; approved changes to baseline software are made properly and consistently in all products, and no unauthorized changes are made.

Software release candidate numbering shall follow the LIS Release Standards and Definitions.

16. DELIVERABLES

Deliverables include, but are not limited to, software updates, software components, software code, and product documentation to include but not limited to (software user manual, software installation procedures, software administrator guide, software center operations manual).

16.1 Weekly Status Reports

On a weekly basis, the Contractor shall deliver a Weekly Status Report (WSR) that briefly discusses upcoming meetings, deliveries, travel, activities accomplished, plan for the next week, new issues, and current issues. The Contractor should highlight those items that are new additions over the previous week’s WSR. The report should also include Transportation Movement Request) TMR Tracker and Weekly TOPS IAVA Activity charts. The Contractor shall provide the following deliverable:

CDRL A003: Weekly Status Review (WSR)

16.2 Test Cases and Results

Test Cases and their derivatives (results, remarks, etc.) shall be documented by the contractor and submitted to LIS Configuration Management. These test cases include a set of conditions or variables that a tester shall use to determine whether software is working correctly or whether it is not.

Test cases shall be reviewed by LIS and shall also be integrated into an appropriate artifacts. Test cases shall, minimally, include the following:

• Test case description,

• Test steps,

• Expected results (pass/fail criteria)

• Actual results from test, and

• Remarks\

The Contractor shall document all test results based on the written and approved test plan. For any tests that fail, contractor shall provide documentation describing the failure and the fix in detail. All failed tests shall be fixed before accepted delivery of the software.

16.3 Release Notes

Release notes are required with each deliverable. The release notes shall provide details about the delivered software and validate that the contractor has delivered the expected software to properly deploy and test the software.

16.4 Integrated Master Schedule

The Contractor shall develop, maintain, and submit a weekly Integrated Master Schedule (IMS) that reflects TOPS inputs to the Program Integrated Master Schedule (PIMS). Subsequent deliveries shall consist of updates to the Contractor’s schedule to maintain the accuracy of the schedule and to track the status and progress of project tasks. If the Government determines that the TOPS IMS requires baseline or milestone date adjustments, the Government will provide the Contractor with notice of these changes if such changes would impact the Contractor’s tasks. If such a situation arises and notice is provided, the Contractor shall ensure that its subsequent monthly IMS update under this CDRL reflects the Government baseline or milestone date adjustment. The Contractor shall provide the following deliverable:

CDRL A007: Integrated Master Schedule (IMS)

16.5 Software Delivery

All deliverables such as but not limited to software updates, software components, and software code shall be ready for compilation and building into the final software products and also include the required script(s) and instructions for building the delivery into the final software products. Deliverables shall include the component or end-product in its entirety.