DOCUMENT
2023.02.09 Virtual Industry Day Q&A.pdf
OVERVIEW
Original Source
Contract Opportunity
Related Opportunity
Related Agency
Posted
Feb. 10, 2023
Type
.pdf
Size
0.17MB
DOCUMENT PREVIEW
EXTRACTED TEXT
Virtual Industry Day Q & A
8 February 2023
Are the TFA recommendations and decision memo publicly available?
o The government will not share these artifacts. The decision is primarily because the
artifacts relate to the approval process required through DOD channels. The necessary
artifacts relevant to this acquisition have been shared with industry. As others relevant
to the implementation are identified, the government will share these artifacts as well.
Would USTRANSCOM consider putting all documents onto a reading room and making it
publicly available to industry?
o The government will not share all of the documents as suggested. The decision is
primarily because the artifacts primarily focus on the approval process required through
DOD channels. The necessary artifacts relevant to this acquisition have already been
shared with industry. As others relevant to the implementation are identified, the
government will share these artifacts as well.
Will we be provided a link to the recording and if so, where?
o The government will provide answers to the questions presented during the industry
day and will provide the presentation slides.
Recommend looking at successful ERP Army has a couple (GCSS-A and LMP), and of
course DLA's EBS.
o The government appreciates the recommendation. The JTMS JPO has weekly
engagements with Defense Logistics Agency (DLA), Army, and Navy to sync efforts with
their ongoing ERP initiatives and to leverage lessons learned across the Department. As
this effort moves forward, the JTMS JPO intends to continue those engagements to
ensure all ERP efforts remain aligned to efficiently solve auditability across the
transportation of things environment.
Will this organization be augmented by contract support teams, beyond the larger JTMS
contract?
o Yes, there is currently a program support contract and there will be other contractors
supporting Enterprise Architecture. Program support work and Enterprise architecture is
currently accomplished under other acquisitions within USTRANSCOM and the
government currently does not see program support or enterprise architecture being
included in the JTMS implementation PWS.
Is it the Governments plan for a possibility that the acquisition will be under IDIQ with
various functional areas?
o This is one option the Government is currently considering. The various support that the
JTMS JPO needs will be outlined and mapped in the Program Acquisition Strategy that is
being developed. Once there is a decision on the JTMS acquisition, those opportunities
will be posted for industry.
Is the Government planning on setting up OCI guidance as many firms are involved in helping
with developing SOW?
o Yes, the Government has and is continuing to identify, evaluate, and resolve any OCI.
Because there are so many stakeholders, is USTRANSCOM considered the "owner" of the
functional community for the purpose of this acquisition?
o The functional requirements owner Is OSD (A&S), Mr. David McCovery. USTRANSCOM
has the executive agency responsibility for fielding the materiel solution with the
assistance/partnership of the Air Force, Army, Navy, Marines, Coast Guard, DLA,
Defense Contract Management Agency (DCMA), and Defense Finance and Accounting
Service (DFAS) in their logistics and financial communities.
Will the Government consider leveraging other DoD GOTS ERPs particularly that of ARMY,
NAVY & DLA.
o As part of the Analysis of Potential Pathways (AoPAP), one of the COAs was to
investigate leveraging an existing ERP across the department. The government is
leveraging the market research and additional analysis to help inform whether
leveraging an existing DoD ERP is a viable solution. It is still being determined.
What about the transportation providers as part of the functional community?
o The government recognizes the need to involve commercial carriers that will
use/interface with this solution. Through Organizational Change Management and
communications, the governments intent is to establish recurring engagements to keep
the commercial mission partners involved as the government sees their
contributions/influence critical in moving this effort forward.
USTRANSCOM continues to use POST-P as a frame. Would it make more sense for
USTRANSCOM to use the DoD end-to-end business flows (P2P, D2RR, etc.) so that we are
talking the same language as the IP auditor? Or are these already aligned?
o From an "as-is" perspective, the government has maintained the POST-P concept and
alignment. As the government moves into BPR and developing the "to-be", there will be
alignment to the end-to-end flows, especially as laid out in Business Enterprise
Architecture (BEA). The BEA alignment is required for DODI 5000.75 (which will guide
this acquisition). As part of the market research, the government will look for vendor
inputs as to the best way to field a materiel solution of this magnitude based on the
constraints the government identifies (i.e., do no harm to military operations while
fielding).
As you talk about data, how will JTMS align with USTC's movement to Advana?
o Specific implications in terms of system and data at this point are still to be determined.
The intent is to define the As-is Architecture, accomplish the business process
reengineering (to-be processes) and then conduct systems engineering to determine
data needs. The government recognizes Advana is the data environment that the DoD is
moving to and therefore JTMS will require data/interfaces with Advana.
Are we considering our processes in the BPR review to ensure that they support the right
outcomes and will support the data that is desired?
o The focus is on the processes and data standardization. The government recognizes
there is a problem in the DoD in that many systems and data sources dont have a
defined structure. Currently, the JTMS JPO focus is on defining the as-is processes to be
baseline information for the analysis-level to-be BPR. This is being done in
partnership with ~340 stakeholders across the Air Force, Army, Navy, Marines, Coast
Guard, DLA, DCMA, and DFAS.
Is the intent for the system to come online all at once, or for incremental delivery of
capability?
o The government has thoughts on the implementation strategy but it would be foolish
for the Government to dictate a way without checking with the vendors to find out what
is possible based on commercial best practices. As part of ongoing market research
efforts, the government is asking industry for feedback on the recommended
implementation approach.
Is the intent to move to solicitation in FY24 Q2 to Q3 timeframe?
o The first draft solicitation is anticipated for release Q3 of FY23. It is our intent to conduct
several rounds prior to releasing the final solicitation. The target for final release of the
solicitation Q4 of FY23.
Back in 2003, SDDC attempted to do a contract for commercial replacement of the Ocean and
CONUS freight movement process, relying on a project that was put out. There was a contract
put out. It was awarded and several issues came up. Once it was awarded, it was a firm fixed
price contract. That time it wasnt as broad at what youre doing today, but there were several
issues, and it was eventually cancelled after having already been awarded. Have you looked at
the detailed requirements and the issues that cropped up during that particular effort?
o The government will reach out to SDDC and ask for background on this effort.
Has USTRANSCOM looked at the EBS-C acquisition strategy and considered that as a model?
o The JTMS JPO has weekly engagements with DLA, Army, and Navy to sync our efforts
with their ongoing ERP initiatives and to leverage lessons learned across the
Department. As this effort moves forward, the JTMS JPO intends to continue those
engagements to ensure all ERP efforts remain aligned to solve auditability across the
transportation of things environment efficiently.
How much of the oversight for the implementation will be done by the contractor versus the
Program Management Office?
o The JTMS Joint Program Office will provide oversight on the implementation.
Are you going to require the use and implementation of the full suite of ANSI x12I EDI?
o Yes, the government will have to support both modern APIs and ANSI x12I EDI to some
capacity since, on the transportation service provider side, not all contractors will be
able to communicate through the more modern APIs. This is another example where
JTMS JPO will require engagements with commercial mission partners that move
cargo/personnel under USTRANSCOM missions.
The draft PWS indicates that the contractor would propose and "acquire" the software. Is
that still the plan, or will the s/w solution be purchased separately?
o Market research regarding additional analysis and RFI information that is being
requested will help define that answer.
Will the BPMN maps be published in the bidders library?
o Yes, BPMN process maps (accomplished under the DOD Architecture Framework, or
DODAF) that have been completed will be included in the bidders library.
How will you measure usability from the end user perspective?
o That is a consideration from a BPR perspective. The government fully expects to have
performance parameters and criteria established to measure this. That will also be a
major consideration from an OCM perspective as well.
Could you give an example of a Disconnected Workflow you anticipate the system needing to
support?
o The government experienced disconnect ops during 3/25 prototype, were able to keep
loading convoy information in the TMS, and data updated when we reconnected.
In disconnected operations you
8 February 2023
Are the TFA recommendations and decision memo publicly available?
o The government will not share these artifacts. The decision is primarily because the
artifacts relate to the approval process required through DOD channels. The necessary
artifacts relevant to this acquisition have been shared with industry. As others relevant
to the implementation are identified, the government will share these artifacts as well.
Would USTRANSCOM consider putting all documents onto a reading room and making it
publicly available to industry?
o The government will not share all of the documents as suggested. The decision is
primarily because the artifacts primarily focus on the approval process required through
DOD channels. The necessary artifacts relevant to this acquisition have already been
shared with industry. As others relevant to the implementation are identified, the
government will share these artifacts as well.
Will we be provided a link to the recording and if so, where?
o The government will provide answers to the questions presented during the industry
day and will provide the presentation slides.
Recommend looking at successful ERP Army has a couple (GCSS-A and LMP), and of
course DLA's EBS.
o The government appreciates the recommendation. The JTMS JPO has weekly
engagements with Defense Logistics Agency (DLA), Army, and Navy to sync efforts with
their ongoing ERP initiatives and to leverage lessons learned across the Department. As
this effort moves forward, the JTMS JPO intends to continue those engagements to
ensure all ERP efforts remain aligned to efficiently solve auditability across the
transportation of things environment.
Will this organization be augmented by contract support teams, beyond the larger JTMS
contract?
o Yes, there is currently a program support contract and there will be other contractors
supporting Enterprise Architecture. Program support work and Enterprise architecture is
currently accomplished under other acquisitions within USTRANSCOM and the
government currently does not see program support or enterprise architecture being
included in the JTMS implementation PWS.
Is it the Governments plan for a possibility that the acquisition will be under IDIQ with
various functional areas?
o This is one option the Government is currently considering. The various support that the
JTMS JPO needs will be outlined and mapped in the Program Acquisition Strategy that is
being developed. Once there is a decision on the JTMS acquisition, those opportunities
will be posted for industry.
Is the Government planning on setting up OCI guidance as many firms are involved in helping
with developing SOW?
o Yes, the Government has and is continuing to identify, evaluate, and resolve any OCI.
Because there are so many stakeholders, is USTRANSCOM considered the "owner" of the
functional community for the purpose of this acquisition?
o The functional requirements owner Is OSD (A&S), Mr. David McCovery. USTRANSCOM
has the executive agency responsibility for fielding the materiel solution with the
assistance/partnership of the Air Force, Army, Navy, Marines, Coast Guard, DLA,
Defense Contract Management Agency (DCMA), and Defense Finance and Accounting
Service (DFAS) in their logistics and financial communities.
Will the Government consider leveraging other DoD GOTS ERPs particularly that of ARMY,
NAVY & DLA.
o As part of the Analysis of Potential Pathways (AoPAP), one of the COAs was to
investigate leveraging an existing ERP across the department. The government is
leveraging the market research and additional analysis to help inform whether
leveraging an existing DoD ERP is a viable solution. It is still being determined.
What about the transportation providers as part of the functional community?
o The government recognizes the need to involve commercial carriers that will
use/interface with this solution. Through Organizational Change Management and
communications, the governments intent is to establish recurring engagements to keep
the commercial mission partners involved as the government sees their
contributions/influence critical in moving this effort forward.
USTRANSCOM continues to use POST-P as a frame. Would it make more sense for
USTRANSCOM to use the DoD end-to-end business flows (P2P, D2RR, etc.) so that we are
talking the same language as the IP auditor? Or are these already aligned?
o From an "as-is" perspective, the government has maintained the POST-P concept and
alignment. As the government moves into BPR and developing the "to-be", there will be
alignment to the end-to-end flows, especially as laid out in Business Enterprise
Architecture (BEA). The BEA alignment is required for DODI 5000.75 (which will guide
this acquisition). As part of the market research, the government will look for vendor
inputs as to the best way to field a materiel solution of this magnitude based on the
constraints the government identifies (i.e., do no harm to military operations while
fielding).
As you talk about data, how will JTMS align with USTC's movement to Advana?
o Specific implications in terms of system and data at this point are still to be determined.
The intent is to define the As-is Architecture, accomplish the business process
reengineering (to-be processes) and then conduct systems engineering to determine
data needs. The government recognizes Advana is the data environment that the DoD is
moving to and therefore JTMS will require data/interfaces with Advana.
Are we considering our processes in the BPR review to ensure that they support the right
outcomes and will support the data that is desired?
o The focus is on the processes and data standardization. The government recognizes
there is a problem in the DoD in that many systems and data sources dont have a
defined structure. Currently, the JTMS JPO focus is on defining the as-is processes to be
baseline information for the analysis-level to-be BPR. This is being done in
partnership with ~340 stakeholders across the Air Force, Army, Navy, Marines, Coast
Guard, DLA, DCMA, and DFAS.
Is the intent for the system to come online all at once, or for incremental delivery of
capability?
o The government has thoughts on the implementation strategy but it would be foolish
for the Government to dictate a way without checking with the vendors to find out what
is possible based on commercial best practices. As part of ongoing market research
efforts, the government is asking industry for feedback on the recommended
implementation approach.
Is the intent to move to solicitation in FY24 Q2 to Q3 timeframe?
o The first draft solicitation is anticipated for release Q3 of FY23. It is our intent to conduct
several rounds prior to releasing the final solicitation. The target for final release of the
solicitation Q4 of FY23.
Back in 2003, SDDC attempted to do a contract for commercial replacement of the Ocean and
CONUS freight movement process, relying on a project that was put out. There was a contract
put out. It was awarded and several issues came up. Once it was awarded, it was a firm fixed
price contract. That time it wasnt as broad at what youre doing today, but there were several
issues, and it was eventually cancelled after having already been awarded. Have you looked at
the detailed requirements and the issues that cropped up during that particular effort?
o The government will reach out to SDDC and ask for background on this effort.
Has USTRANSCOM looked at the EBS-C acquisition strategy and considered that as a model?
o The JTMS JPO has weekly engagements with DLA, Army, and Navy to sync our efforts
with their ongoing ERP initiatives and to leverage lessons learned across the
Department. As this effort moves forward, the JTMS JPO intends to continue those
engagements to ensure all ERP efforts remain aligned to solve auditability across the
transportation of things environment efficiently.
How much of the oversight for the implementation will be done by the contractor versus the
Program Management Office?
o The JTMS Joint Program Office will provide oversight on the implementation.
Are you going to require the use and implementation of the full suite of ANSI x12I EDI?
o Yes, the government will have to support both modern APIs and ANSI x12I EDI to some
capacity since, on the transportation service provider side, not all contractors will be
able to communicate through the more modern APIs. This is another example where
JTMS JPO will require engagements with commercial mission partners that move
cargo/personnel under USTRANSCOM missions.
The draft PWS indicates that the contractor would propose and "acquire" the software. Is
that still the plan, or will the s/w solution be purchased separately?
o Market research regarding additional analysis and RFI information that is being
requested will help define that answer.
Will the BPMN maps be published in the bidders library?
o Yes, BPMN process maps (accomplished under the DOD Architecture Framework, or
DODAF) that have been completed will be included in the bidders library.
How will you measure usability from the end user perspective?
o That is a consideration from a BPR perspective. The government fully expects to have
performance parameters and criteria established to measure this. That will also be a
major consideration from an OCM perspective as well.
Could you give an example of a Disconnected Workflow you anticipate the system needing to
support?
o The government experienced disconnect ops during 3/25 prototype, were able to keep
loading convoy information in the TMS, and data updated when we reconnected.
In disconnected operations you
Show All